Hierarchy
⤷ LO-SRS (Application Component) SAP Retail Store
⤷ WOST_CUST (Package) Retail Store: Customizing
IMG Activity
ID | W_STW_WE_B003N | BAdI for PDC Outbound/Vendors, Plants and Customizing Data |
Transaction Code | S_PLN_16000314 | (empty) |
Created on | 20020506 | |
Customizing Attributes | W_STW_BADI | Attribute BAdIs in SAP Retail Store |
Customizing Activity | W_STW_WE_B003N | BAdI for PDC Outbound/Vendors, Plants and Customizing Data |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SRS_PDC_GM_OUTBOUND |
Use
This BAdI is used in SAP Retail Store for the function, PDC goods movement/goods receipt.
You can tailor the interface to suit the customer's needs when preparing and sending the data needed for PDC goods movements/goods receipt. Additional data can be read using the methods that are grouped together in this BAdI and then sent to the interface in the PDC outbound.
- The method, CUSTOMIZING_PREP, is called once the Customizing data and business transactions have been prepared for the outbound processing of goods movement in SAP Retail Store.
- The method, VENDOR_PREP, is called once the vendors have been prepared for the goods movement/goods receipt outbound processing in SAP Retail Store.
- The method, PLANT_PREP, is called once the plants have been prepared for the goods movement/goods receipt outbound processing in SAP Retail Store.
The methods named here are used for enhancing outbound data. For more information, see the documentation on the individual methods.
Requirements
Standard settings
This BAdI is not active in the standard system.
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
See also
Documentation on interface method enhancement customizing/business transactions
Business Attributes
ASAP Roadmap ID | 257 | Create User Exits |
Mandatory / Optional | 3 | Nonrequired activity |
Critical / Non-Critical | 1 | Critical |
Country-Dependency | A | Valid for all countries |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20020506 |
SAP Release Created in | 110 |