Kontakt

Ansicht
Dokumentation

PRP_BEFORE_DATA_SAVE - BAdI: PPR Checks Before PPR Object Data Is Saved

PRP_BEFORE_DATA_SAVE - BAdI: PPR Checks Before PPR Object Data Is Saved

PERFORM Short Reference   General Data in Customer Master  
This documentation is copyright by SAP AG.
SAP E-Book

This Business Add-In (BAdI) is used in the component Partner/Product Range (CRM-MD-PPR).

This BAdI offers you read access to newly created, modified, and to be deleted entries for the following PPR objects before they are saved to the database (read access means that you cannot change the data within the BAdI implementation):

  • PRPADM_H: PPR header
  • PRP_DESCR_H: PPR header description
  • PRP_ORG_H: PPR organizational data
  • PRP_EXT_H: extension fields for PPR organizational data
  • PRPADM_I: PPR item
  • PPR_DESCR_I: PPR item description
  • PRP_BUPA_I: PPR business partner references
  • PRP_PROD_I: PPR product references
  • PRP_TS_I: PPR validity periods
  • PRP_PAR_I: PPR rule parameters
  • PRP_EXT_I: extension fields for business partners/products/validity periods in the PPR.

If active implementations of the BAdI exist, the BAdI method CRM_PRP_BEFORE_DATA_SAVE is called for each PPR object and the newly created, modified, and to be deleted object entries are transferred.

Within the method, you have read access to the table, and can update data to customer tables, for example.

Before the method CRM_PRP_BEFORE_DATA_SAVE is called, the function module CRM_PRP_READ_BADI_CHECK_IMPL is used to check whether at least one implementation with status Active exists for the BAdI.

This BAdI has the following properties:

  • filter-independent
  • default status Inactive
  • multiple-use-enabled
    This means there can be more than one active BAdI implementation. When the BAdI is called, all implementations are called in unsorted sequence.

In transaction SE19 you can copy the implementation PRP_BEFDBSAVE_SAMPLE as a template.

After you have called the IMG activity, proceed as follows:

  1. In the following dialog box, enter in the field "Implementation" a name for the BAdI implementation and choose Copy.
If implementations have already been created for the BAdI, a dialog box with the existing implementations will be displayed. In this dialog box, choose Create.
  1. In the corresponding field, enter a short text for implementation .
  2. In the tab Propertiesenter filter properties - if this is a filter-dependent BAdI.
  3. Choose the tab Interface.
The name of the implementing class is generated by the system based on the name of your impmlementation. You can change the name.
If the BAdI is a menu exit, the tab FCodes also appears.Enter a function here and, if necessary, additional data.
  1. Save your entries and assign a package.
  2. Position the cursor on a method. Call up the Class Builder by double-clicking it.
  3. Between the statements method <Interface-Name>~<Name of Method>. and endmethod, enter the coding you request for the implementation.
  4. Save and activate your coding, and navigate back to the screen Change Implementation.
  5. Save on the screen Change Implementation.
Note: You can first create an implementation for the BAdI and then activate this later on. In this case, close the processing function at this time.
  1. Choose Activate.
When the application program is executed, the coding you have created will be run.

Method User-Defined Checks Before PPR Object Data Is Saved to Database.






ROGBILLS - Synchronize billing plans   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 4646 Date: 20240523 Time: 190313     sap01-206 ( 61 ms )