SAP ABAP IMG Activity BBP_CTR_INIT_UP_PI (BAdI for Initial Upload of R/3 Contracts to SRM)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ SRM-EBP (Application Component) Enterprise Buyer
     ⤷ BBP_ADDON_46B (Package) Add-Ons for BBP from 4.6b
IMG Activity
ID BBP_CTR_INIT_UP_PI BAdI for Initial Upload of R/3 Contracts to SRM  
Transaction Code     (empty) 
Created on 20050407    
Customizing Attributes BBP_CTR_INIT_UP_PI   BAdI for Initial Upload of R/3 Contracts to SRM 
Customizing Activity BBP_CTR_INIT_UP_PI   BAdI for Initial Upload of R/3 Contracts to SRM 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name BBP_CTR_INIT_UP_PI    

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

Example

Requirements

You have set up the IDoc communication completely.

Standard settings

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)

Recommendation

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

Activities

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

Further notes

  • 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 Portal under <http://help.sap.com> -> SAP R/3 Release 4.6B -> Basis -> Basis Services -> IDoc Interface

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG BBP_CTR_INIT_UP_PI 0 HLA0009510 Materials Management 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20050407 
SAP Release Created in 600