Kontakt

Ansicht
Dokumentation

BBP_CTR_INIT_UP_PI - BAdI for Initial Upload of R/3 Contracts to SRM

BBP_CTR_INIT_UP_PI - BAdI for Initial Upload of R/3 Contracts to SRM

BAL_S_LOG - Application Log: Log header data   ABAP Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

Using Business Add-In BBP_CTR, you can change the IDoc data and the structure for the contract and the related conditions.

You have set up the IDoc communication completely.

The method MODIFY_DATA _CTR of the BADI is called up before the mapping to the IDoc structures. This method take all the data that has reached R/3 and handles it as changeable parameters. You can only change this data before it is mapped to the IDoc structures.

The methods MODIFY_IDOC_DATA_CTR and MODIFY_IDOC_DATA_CND of the BADI are called up after all mappings to the IDoc structures have been made. These methods take all the data that has reached R/3 and handles it as non-changeable input parameters. In addition, the final result of the mappings is transferred to the IDoc structures. You can only modify this result before the IDoc is updated to the database.

The system uses

  • IDoc BLAORD03 for the contract data
  • IDoc COND_A02 for the conditions

The BAdI methods are described here in detail:

MODIFY_DATA_CTR

Serves for changing contract data in the IDoc and provides the following parameters:

Importing

  • IV_USER ,,,,
    R/3 System, User's log-on name
  • IV_LANGU
    R/3-System (log-on language)
  • IV_CALLING_LOGSYS
    Logical system
    Changing
  • CS_HEADER
    Contract communication structure: Header/Org./Partner
  • CT_ITEMS ,,
    Contract communication structure: Items/Partners
  • CT_TEXT ,,,,
    Contract communication structure: Texts
  • CT_CND_CT,,,,
    BAPI Structure for condition tables (corresponds to COND_RECS)
  • CT_CND_HD,,,,
  • CT_CND_HD,,,,
    BAPI Structure KONH,,
  • CT_CND_IT,,,,
    BAPI Structure KONP
  • CT_CND_QS,,,,
    BAPI Structure KONM
  • CT_CND_VS
    BAPI Structure KONW,,

MODIFY_IDOC_DATA_CTR

Serves for changing contract data in the IDoc and provides the following parameters:

Importing

  • IV_USER ,,,,
    R/3-System, user's log-on name
  • IV_LANGU
    R/3-System (log-on language)
  • IV_CALLING_LOGSYS
    Logical system
  • IS_HEADER
    Contract communication structure: Header/Org./Partner
  • IT_ITEMS ,,
    Contract communication structure: Items/Partners
  • IT_TEXT ,,,,
    Contract communication structure: Texts

Changing

  • CT_BLAORD
    Enterprise Buyer Contract (IDoc data EDIDD)

MODIFY_IDOC_DATA_CND

Serves for changing condition data in the IDoc and provides the following parameters:

Importing

  • IV_USER ,,,,
    R/3 System, User's logon name
  • IV_LANGU
    R/3 System (logon language)
  • IV_CALLING_LOGSYS
    Logical system
  • IS_HEADER
    Contract communication structure: Header/Org./Partner
  • IT_CND_CT,,,,
    BAPI Structure for condition tables (corresponds to COND_RECS)
  • IT_CND_HD,,,,
    BAPI Structure KONH,,
  • IT_CND_IT,,,,
    BAPI Structure KONP
  • IT_CND_QS,,,,
    BAPI Structure KONM
  • IT_CND_VS
    BAPI Structure KONW,,

Changing

  • CT_DATA_CONDA ,,,,
    Contract conditions (IDoc data EDIDD)

Ensure that the Idoc is consistent and syntactically correct after the modifications. You could perform a test run to check.

Implement the BAdI if you wish to change the contract data to be transferred via IDoc and the contract structure.

  • BAdI Implementation
  • For more information, see the Business Scenario Configuration Guide of the Sourcing scenario in the SAP Service Marketplace under <http://service.sap.com/ibc> -> for mySAP SRM -> Strategic Sourcing
  • For more information on the IDoc interface, see the SAP Help Portalunder <http://help.sap.com> -> SAP R/3 Release 4.6B -> Basis-> Basis Services-> IDoc Interface





BAL_S_LOG - Application Log: Log header data   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 5507 Date: 20240524 Time: 014433     sap01-206 ( 62 ms )