Kontakt

Ansicht
Dokumentation

EHPRC_IMDS_BADI_2 - BAdI: Customer IMDS Communication

EHPRC_IMDS_BADI_2 - BAdI: Customer IMDS Communication

Vendor Master (General Section)   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.
SAP E-Book

This Business Add-In (BAdI) is used for Product Compliance in Discrete Industries. This BAdI enables you to adapt the IMDS communication for the customer MDS center. It is called when IMDS communication is triggered within the customer MDS center.

You have noted the important information given in SAP Note 3133253.

In the standard system, the Business Add-In is activated. The default code is executed automatically. If you activate your own implementation, the default code is deactivated automatically. The BAdI is not filter-dependent.

CL_DEF_IM_EHPRC_CP_IMDS_BADI_2 (Default implementation)
A default implementation is supplied for the following methods. In all cases, these methods comprise "only" the upload using the IMDS Advanced Interface and not the download of the result file:

PROPOSE
Encompasses the implementation for proposing a material data sheet (MDS) to a customer.

PUBLISH
Encompasses the implementation for publishing an MDS.

SEND_EDIT
Encompasses the implementation for sending an MDS to a customer in edit mode.

SEND_CUSTOMER
Encompasses the implementation for sending an MDS to a customer.

INTERNAL_RELEASE
Encompasses the implementation for releasing an MDS internally.

DELETE_RECIPIENT
Encompasses the implementation for removing one or more recipients from an MDS.

Each of these methods has a parameter that distinguishes the execution in dialog mode from the background execution.

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.





rdisp/max_wprun_time - Maximum work process run time   General Material Data  
This documentation is copyright by SAP AG.

Length: 3789 Date: 20240523 Time: 164625     sap01-206 ( 52 ms )