SAP ABAP IMG Activity W_STW_WE_B004N (BAdI for PDC Outbound/Reference Documents for GR and Customizing Data)
Hierarchy
☛ EA-RETAIL (Software Component) SAP Enterprise Extension Retail
   ⤷ LO-SRS (Application Component) SAP Retail Store
     ⤷ WOST_CUST (Package) Retail Store: Customizing
IMG Activity
ID W_STW_WE_B004N BAdI for PDC Outbound/Reference Documents for GR and Customizing Data  
Transaction Code S_PLN_16000315   (empty) 
Created on 20020506    
Customizing Attributes W_STW_BADI   Attribute BAdIs in SAP Retail Store 
Customizing Activity W_STW_WE_B004N   BAdI for PDC Outbound/Reference Documents for GR and Customizing Data 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SRS_PDC_GR_OUTBOUND    

Use

This BAdI is used in SAP Retail Store in the function, PDC goods receipt.

You can tailor the interface to suit the customer's needs when preparing and sending the data needed for PDC goods receipt creation. Additional data can be read using the methods grouped together in this BAdI and sent to the interface in the PDC outbound.

  • The method, CUST_GR_PREP, is called once the Customizing data has been prepared for the outbound processing in SAP Retail Store goods receipt.
  • The method, PURORDER_GR_PREP, is called once the purchase orders have been prepared for the outbound processing of SAP Retail Store goods receipt.
  • The method, MATDOC_GR_PREP, is called once the material documents have been prepared for the outbound processing of the SAP Retail Store goods receipt.
  • The method, DELIVERY_GR_PREP, is called once the deliveries have been prepared for the outbound processing of the SAP Retail Store goods receipt.
  • The method, HU_GR_PREP, is called once the handling units have been prepared for the outbound processing of the SAP Retail Store goods receipt.

The methods named here are used to enhance data for outbound processing. For more details, 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:

  1. 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.

  2. Enter a short text for the implementation in the Short text for implementation field.
  3. 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.

  4. Save your entries, and assign the implementation to a development class.
  5. Place the cursor on the method, and double-click to enter method processing.
  6. Enter the code for the implementation between the statements method <Interface name> ~ <Name of method> and endmethod.
  7. Save and implement your code. Return to the Edit Implementation screen.
  8. 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.

  9. 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

Documentation on interface method enhancement for purchase orders

Documentation on interface method enhancement for material documents

Documentation on interface method enhancement for deliveries

Documentaion on interface method enhancement for handling units

Close documentation on interface method outbound processing

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