Purchasing Group – Mass Configuration tool
Concept
This tool enables the user to perform mass configuration of Purchasing Group. The user can download the template in the form of excel sheet, enter the values and upload the same in the selection screen. The user executes the program/transaction in test run to validate the values entered in the excel sheet. Once verified, the user can execute the program/ transaction in production run mode to update the table T024 with Purchasing Group. The result of this program will when executed either in test run or production run is the ALV display of successful entries and detailed description of errors.
Business perspective
This tool can be implemented in both pre implementation/ rollout and post implementation/ production support scenarios. This tool can be used to introduce one or more Purchasing Groups.
Screen Layout and Execution steps
User will check the radio button “Download the template” and enter the destination path and execute the transaction
Selection Screen:
Template format:
User will enter the respective values in the template as shown below
|
Purchasing
Group
|
Description p. group |
Tel.no. purch. group |
Output Device | Fax Number | Telephone | Extension |
Address |
Transport Request |
|---|---|---|---|---|---|---|---|---|
Output screen:
User then run the transaction in “Test run” mode
If any of the entered values is incorrect then error message will pop up.
If all the input parameters are correct in the template then below screen will come upon execution
Once the “Test run” mode is successful then execute it in Production mode.
Upon execution, go to T024 table and check for entries.
Note:
Test run is a must before production run. This is to ensure only correct entries will move to Config table. Transport Request task must be assigned to the person who is executing the tool. This ensures the SOX compliance.
This tool should be designed to accommodate one Transport Request per run.
What is the name of this tool, what the transaction?
Is it standard (where to find) or selfdeveloped?
It may be a nice tool, but what do you want to tell the community with this document in case it is own developed?
This is self developed tool (not a std too) and wanted to share my idea with SCN community so they can also use it to develop same tool or similar tool.
do you create such document for each table now?
you have already the same document for MRP controller, for scheduling margin key, production scheduler. Just exchanged the screen shots and table names, all the rest is equal.
Somnath Manna had already recommended you should just merge everything into one document. So why you are continuing with separate documents?
This does not really add any value to SCN.