Kontakt

Ansicht
Dokumentation

EHPRC_IMDS_BADI_6 - BAdI: Supplier Request Processing

EHPRC_IMDS_BADI_6 - BAdI: Supplier Request Processing

General Data in Customer Master   PERFORM Short Reference  
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 way that requests in the supplier MDS center are processed. It enables you to adapt the data that is automatically written to the customer data of a new supplier material data sheet (MDS) request.

This BAdI is called when the creation of a new supplier MDS request is triggered (in the context menu in the compliance workbench under Create Supplier Request or by choosing Create MDS on the supplier MDS search screen), when a supplier request is to be sent or deleted, and to pre-fill the recipient data when a request is created.

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.

A default implementation is supplied for the following methods.

  • SEND_REQUEST
  • DELETE_REQUEST
  • PREFILL_REQ_CH4 - Pre-fills the part/item number, article name, and supplier number in the recipient data for the newly created request.

The following methods are provided:

Method Description
SEND_REQUEST This method can handle two scenarios: 1) The request does not exist in IMDS yet. It is uploaded to IMDS and then sent to the supplier. 2)The request already exists in IMDS. It is updated and then sent to the supplier.
DELETE_REQUEST This method deletes a request locally in the IMDS. The request is not deleted physically; it is given the request status Deleted.
PREFILL_REQ_CH4 This method prefills the default chapter four data of a request.

These methods comprise only the upload via IMDS Advanced Interface and not the download of the result file.

PREFILL_REQ_CH4

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.





CL_GUI_FRONTEND_SERVICES - Frontend Services   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 4666 Date: 20240523 Time: 171721     sap01-206 ( 70 ms )