ADP RPG problem of the month

[robc]

I am by far not a RPG/RPX expert, but I am trying to get more accustomed to the system. One thing I have not tried to do is work with multiple files at once - or if it is possible. What I need to do is generate a report of every part billed on every repair for a month. I normally use the service history file and just do a month date range and pick the fields I want like RO#, RO date, Ops, Op descriptions, part sales, cost, tech id, etc. I need all that -- plus the actual part numbers and amounts (qty, cost, sale). Any thoughts?

== Rob ==

[jazdale]

That's a pretty complex RPG.

Unless others have other ideas, I think the best way would be to use PDA (parts document archiving) in the parts logon and use the report generator in that for a list of all parts sales.

Labor could be pulled from several files - I'm guessing HISTORY in the service logon.

From here, you may need to match them up by RO number in Excel or Access.

Whats the situation that needs this? Maybe there's a different way to skin this cat.

[cantfind12]

Here is my understanding and I could easily be wrong. PDA and RDH are CarInk programs and are "extra added attractions" which do wonderful things, however, they are not canned items from the provider. RPG can only access one file at a time and the dictionary items have a hard time "crossing" applications without some assitance with of a knowledgeable programing component like CarInk. Some "dictionary" items can be copied but there are limitations to how they will work with certain files since records do not always contain the same cross information. In short, you need to get with someone who understands this a lot better than me but I think it requires the ability to "pull" across the file structure and needs some special attention.

[robc]

After fooling around for a while, you are probably right and I'll have to marry to excel outputs from RPX together. That's no big deal if I can get the parts data table I need.

I am used to using service HISTORY for all my RPG stuff because it is the most complete. But I just can't find the part sales data. I believe I found a similar file for counter tickets, but nothing as it related to ROs. Maybe it is because this data is not stored in a working file that RPG can access. I have top level access (CFO's login) so it shouldn't be an issue of access ... at least I hope not.

I have not looked at PDA, but if that is like the RDH isn't that just a raw output of the individual ROs. Generally I will pull out all the ROs from DSDA (if the store has it) so I can reference them, but you can't pull data off the pdf images.

Plus, not being in parts, I have never run any of the canned reports like RTH or RTR to see what level of detail you can get out of the system.

== Rob ==

[jazdale]

Rob,
I'll think you'll get what you want.

Mosey on over to PDA in the inventory logon. If the store is current with software, they will have a report-generator as a function. Not identical to the RPG you've used, but same idea with selection, sorting, output criteria. I think it also has an excel dump. The Parts-sales and/or transaction files contains most of the parts detail that you're looking for.

[cantfind12]

Your assement sounds very logical. I have seen "procs" that I believe cross the file boundary but I am not sure. I know DMP's can but I don't know what level programming they are. I use the word programming losely because none of this is written in what I understand as common code. Since I believe ADP uses multiple platforms with a translator I'm not sure what language it is if in fact it is a "common" language (and good for them if it is not). It is way past my knowledge level but I am always curious so if you find out more please share it.

[jazdale]

Rob? Any luck?

[robc]

Of course not

The dealership I was in either had nothing turned on for me for parts (less likely) or apparently has purchased no options under Car!nk. When I go there I see nothing. So I played around with the Parts file under the XXX-I login under RPX. While this apparently just covers counter tickets or something like that, I was able to at least begin to structure a report.

My other issue is unfortunately working with individual lines, which RPX doesn't handles well. For example, if the RO had 8 lines the parts sale will report as something like, "0.00 0.00 3.43 0.00 23.21 0.00 12.11 0.00"

That is easy enough to break up using excels text to column tool but it take some effort to try to get those lines to make sense. The parts cost line for the same RO above would show "1.12 15.10 8.23" - so it omits the lines without a cost (the 0.00 amounts). That would be fine, other than I have to match up each line with it's labor type ... so my Excel nightmare right now is trying to marry each line's labor type and part sale (easy) with the part cost - which would only appear when there is one.

In the last dealership I was working with they did 3500 RO's in February - some with a full 26 lines. It was just too much to try to get your arms around. But with enough Excel macros and passes, after 7-8 hours I was able to whittle the data down to something more usable.

To answer an earlier question about what I am doing ... I need to make a report showing me the gross profit on every part sold, on every line, on every repair order. We are looking for needles in a haystack of consistent issues beyond the standard variance or exception report can give us. For example, one of the issues we are trying to resolve is the accuracy/effectiveness of the dealership's "family" pricing of filters, etc.

[drapp]

robc

If you are looking at family pricing issues have you used function PAR. I realize you are way ahead of my ADP knowledge but I use PAR for family cost / pricing issues.

[This message has been edited by drapp (edited 03-12-2008).]

[jjones]

Rob,
The parts data you are looking for is in the
WIP-HISTORY file. How much data is there is
determined by the IFR setup on the Parts account. The problem is I don't believe that
WIP-HISTORY is accessible via RPG. The file
is a little bit difficult to work with, but
if the store has User-Programming, the data
can be retrieved. Every piece of data in every RO or parts ticket closed goes to WIP-HISTORY.
JJ