Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
LO-MDS-AL (Application Component) Allocation⤷
WCA3 (Package) IS-R: Allocation table (Customizing)
IMG Activity
| ID | W_ZF_VK_0475 | BAdI for Determining Follow-On Doc. Cat. per Plant (PO/Sales Order) |
| Transaction Code | S_PL0_09000380 | (empty) |
| Created on | 20020502 | |
| Customizing Attributes | W_ZF_VK_0475 | BAdI to Change End Date of Listing from Allocation Table |
| Customizing Activity | W_ZF_VK_0475 | BAdI for Determining Follow-On Doc. Cat. per Plant (PO/Sales Order) |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | RAT_PROCUREMENT_TYPE |
Use
You can use this Business Add-In (BAdI) to determine which follow-on document category should be used to define the follow-on documents that should be used - for example, for franchisers sales orders or purchase orders in your own stores.
As there is no general indicator in the master data that is suitable for such cases, you use the BAdI 'Procurement Document Determination (Purchase Order/Sales Order)' as a customer-specific solution option. The BAdI determines whether a purchase order or a sales order should be generated for a plant.
If you do not want the BAdI to return a follow-on document category for a plant, any subsequent processing for this plant is carried out on the basis of a purchase order follow-on document category.
Requirements
The BAdI is only called if the 'Stock Transfer' indicator in the item category for the allocation table item is set for the stock transfer from the distribution center to recipient '5' 'Customers: Sales Order; Plants: User Exit Purchase Order or Sales Order'.
The BAdI is only called for plants. Sales orders are always created for customers.
Standard settings
The BAdI is not active in the standard system and there is no default coding.
The BAdI can only be used once and is not filter-dependent.
Activities
After calling up the IMG activity, a dialog box appears, in which you can enter a name for the implementation.
If you have already made other implementations for this BAdI, another dialog box appears, in which the existing implementations are displayed. In this case, choose Create, and proceed as follows:
- In the dialog box, enter a name for the BAdI implementation in the Implementation field, and choose Create.
The screen for creating BAdI implementations is now displayed.
- Enter a short text for the implementation in the Short text for implementation field.
- From the tab index, choose Interface.
The Name of implemented class field is already filled on the tab page, as a class name was automatically assigned to the implementation when you named it.
- Save your entries, and assign the implementation to a development class.
- Place the cursor on the method, and double-click to enter method processing.
- Enter the code for the implementation between the statements
method <Interface name> ~ <Name of method>andendmethod. - Save and implement your code. Return to the Edit Implementation screen.
- Save the entries on the Edit Implementation screen.
Note: You can also create an implementation, and then activate it at a later time. In such a case, end the processing stage at this point.
- Choose Activate
The code you stored in the method will be run when the application program is executed.
Example
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20020502 |
| SAP Release Created in | 470 |
