Skip to Content
author's profile photo Former Member
Former Member

Contract CUF from SRM to Backend

Hi Guys,

in SRM 5.0 we have some customer fields in GOA contract header .

The same Customer fields exist in the backend (ECC 6).

How can I pass customer fields from SRM to ECC6?

It seems that IDOC (BLAORD03) is not ready to do that.

Thanks.

Paolo Bitta

The man called agreement.

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Nov 20, 2007 at 06:30 PM

    Hi,

    Try using the BADI " BBP_CTR ".

    Here is the documentation of this BADI.

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

    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.

    BR,

    Disha.

    <b>Pls reward points for useful answers.</b>

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 21, 2007 at 10:33 AM

    Hi

    <u>Try the SRM CUF BADIs -></u>

    BBP_BUPA_GET_CUF

    BBP_CUF_BADI

    BBP_CUF_BADI_2

    BBP_CTR

    <b>Please read the relevant SAP documentation using SE18 transaction.</b>

    Do let me know.

    Regards

    - Atul

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      We need to save CUF field from SRM (include CI_BBP_HDR_CTR) to CUF field on backend (include CI_EKKODB).

      Unfortunately IDOC BLAORD03 does not contains this fields, and so BADI's cannot solve my trouble.

      Paolo Bitta

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.