Ok, You asked for you, so here it is...
I know that SB is a receipt code for a supplemental backorder on the ERA system. However, SP is a status code that David has identified correctly. Using status code SP for special order parts on the ADP system will not test any phase in criteria and when the part has an on order of zero and an on hand quantity of zero, the part drops at month end. I would reserve this status for make trim parts that you will never stock, or for aftermarket part numbers you have added to your system for different make models other than your own franchise.
ADP SOR, as I have written about and mention in this forum, has three different metholds of implementation.
1) There is the manual method.
This is nothing more than a glorified way of putting your special order parts on the computer but it will not utilize your service file or name file in parts. Basically, you go into SOR and created a "manual" SOR number but you continue to use the manual method of posting and tracking them once they have arrived.
2) There is the Automated / Manual Method
This is the method most commonly used by the few parts managers who brave to understand this feature. With this option, you can now create a special order in the invoicing function (function "I") screen or the service invoicing screen (function ROA or PRO depending on the software release you are using) and it will now track both the wholesale and retail customer along with the SOR information. You still have to manually receipt the parts and fill the SOR requests, but now your service department and parts department can track the SOR through function SPI on the system. This is a very powerful and easy way to communicate special order information to the entire fixed operation.
3) The Automated / Automated Method.
This has all the features of the above process but has on enhanced feature that is wonderful if you have a handle on your service department repair orders. This feature of SOR will automatically fill an open counter tickets and repair orders the instant you receipt your special orders in function RA. The backlash of this approach is if a repair order is left open and the customer has left the dealership, you now have a filled special order request and it drops out of the outstanding special order reports and SPI. Thus, you have a customer's part on the shelf and the system says you gave it to the customer. This can cause chaos in the warranty repair order area if you leave WRO's open after the customer leaves. The next thing you know, your warranty clerk books the WRO and closes it with the part on the repair order and the repair was not fulfilled. Hence, I would suggest that if you are just starting out that you use Option #2 to begin with and once you master this, move to this option.
You can find these options under the submenu SPM (Special order maintainence) under the function code SOS.
It is really important to remember to spend some time learning this feature of your system. It took four months and a lot of trial and error before we got it perfected. Very few individuals at ADP really understand the interaction between your PART-NO. file and your SOR-LINES file. This is because only about 15% of the ADP Clients are using the ADP Automated SOR program. This is certainly a case where I would highly suggest that you load the ADEPT training tape on SOR available from ADP to learn how to use this system properly. I set up a fake parts department over several months and played with it, then trained my employees on it over a two week period before 'turning it on'.
Once you turn it on, if you want to go backwards, you have to call ADP to turn it off for you. I know this because I turned it on and off several times before finally diving into it and learning it.
Reynolds offers a more 'user friendly' SOR program up front, but if you can take the time to work with the ADP program it is by far the better of the two when it comes to information sharing and reliability.
Chuck Hartle'
[This message has been edited by Chuck Hartle (edited 04-10-2001).]