Kontakt

Ansicht
Dokumentation

EHPRC_SCC_OD_INTEGRA - BAdI: Supply Chain On-Demand Integration

EHPRC_SCC_OD_INTEGRA - BAdI: Supply Chain On-Demand Integration

Fill RESBD Structure from EBP Component Structure   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.
SAP E-Book

This Business Add-In (BAdI) is used in Product Compliance for Discrete Industries. You can use this BAdI to exchange data with the SAP Product Stewardship Network. You have to decide how this BAdI deals with manufacturer part numbers.

  1. You have checked if you use multiple manufacturer parts (MPN) for one material.
  2. You have configured and activated the Web service for the communication with the SAP Product Stewardship Network, as described in the Specify SAP Product Stewardship Network Integration Customizing activity.

This BAdI definition is not active in the standard system. It contains the following methods:

  • GET_SUPPLIER_CONNECTION_STATUS
    Use this method to determine the status of the connection between your company and one or more suppliers. It shows whether each supplier has already been invited or not. If a supplier has been invited (yes), it shows whether the supplier has accepted or rejected the invitation.
  • GET_SUPPLIER_PART_STATUS
    Use this method to determine detailed status information about one or more supplier parts. If an assigned declaration exists, you also can view the status of this declaration for each supplier part.
  • GET_EXTERNAL_PAGE_URL
    Use this method when you want to process a supplier part in the SAP Product Stewardship Network to get an external URL to this network.
  • INTEGRATION_ENABLED
    Use this method to verify if the integration of the SAP Product Stewardship Network is available.
  • GET_DECLARATION
    Use this method to get declaration data for a component from the SAP Product Stewardship Network for one supplier part.
  • PROCESS_COMPONENTS
    Use this method to navigate to the SAP Product Stewardship Network and process one or more selected supplier parts.
  • GET_STATUS_CHANGES
    Use this method to synchronize all suppliers and supplier parts that have been changed on the SAP Product Stewardship Network.
  • ACKNOWLEDGE_STATUS_CHANGES
    Use this method to send an acknowledgement to the SAP Product Stewardship Network for each supplier, for each supplier part, or for either that have been successfully synchronized using the method GET_STATUS_CHANGES. This causes the SAP Product Stewardship Network to remove the supplier or supplier part from the list of changed objects accordingly.
  • ACKNOWLEDGE_ALL_STATUS_CHANGES
    Use this method to send an acknowledgement to the SAP Product Stewardship Network after a successful full synchronization. This causes the SAP Product Stewardship Network to remove all suppliers and supplier parts from the list of changed objects.
  • CONVERT_PRCDATA_TO_PSN_COMP_ID
    Use this method to create a unique identifier for the supplier part on the SAP Product Stewardship Network. This identifier is used and displayed as a product identifier in the SAP Product Stewardship Network. By default, it contains the material number and, only in case there are multiple manufacturer parts for one material, the MPN.
For more information about the standard settings, such as filters, single use, or multiple uses, see the Enhancement Spot Element Definitions tab in the BadI Builder (SE18).
  • You need the default implementation BADI_EHPRC_SCC_OD_MPN, if you use multiple manufacturer parts for one material and you want to use the supply chain on-demand integration with MPN handling.
  • You need the fallback class CL_EHPRC_SCC_OD_INTEGRATION_FB, if you do not use multiple manufacturer parts.
  1. Decide how the BADI_EHPRC_SCC_OD_INTEGRATION BAdI should work:
  • ,,If you use multiple MPNs, activate the default implementation BADI_EHPRC_SCC_OD_MPN.

  • ,,If you do not use multiple MPNs, leave the standard implementation as deactivated. The system uses the fallback class CL_EHPRC_SCC_OD_INTEGRATION_FB.

  1. If you activate the default implementation, run a full synchronization by using the R_EHPRC_SCC_OD_STATUS_SYN report.
  2. If you want to adapt the standard functionality, create a new BAdI implementation. This BAdI is not "multiple use" and for this reason, only one implementation can be active at the same time.






ROGBILLS - Synchronize billing plans   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 5062 Date: 20240523 Time: 152255     sap01-206 ( 120 ms )