Skip to Content
avatar image
Former Member

Custom fields at header and item level for Idoc of Basic Type: MBGMCR03

Hi Experts,

I have a requirement of passing some extra fields at header and item level, and as you know MBGMCR03 can not be extended. Please help me get a solution for those custom fields.

Standard Message Type: MBGMCR

Standard Basic Type: MBGMCR03


Process Code: BAPI

Thanks for your help,


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Feb 08, 2018 at 12:44 PM

    Hi Sombunath shaw,

    Actually the credit goes to my technicla team if is really useful to you..

    We cannot add custom field to the standard IDOC type. I would recommend you to create an extended IDOC for your Std. IDOC and add the new field into the extended IDOC type. This can be done thru tcode WE30.

    yes very true MBGMCR03 is not extendable but we can go for fields, which are not available in standard IDOC, extend the IDOC and write user-exit to populate corresponding fields.

    We need to go for a Customer Exit by writing the code for handling the requirement.

    To the external idoc(if it is a standard one ) get the customer functions available and check the fields or tables available where u can get the actual parameters/values that can be used to get the solution.

    I have checked with my ABAP Team and got intput on below things...

    you can get the customer functions by opening the IDOC_INPUT_XXX

    Goto SE37 and make a search on Customer functions .

    WE31 --> To Create a Custom Segment

    WE30 --> To extend the basic Idoc type

    WE82 --> Assigning the extended to Message type

    WE57 --> Assigning FM to Extended Idoc type

    WE41 or WE42 --> Write the code in userexit in FM to populate the data in Custom Segments.

    but problem is we need to take more care on extendign the segment..hope it is useful to some extent. whatever my technical guys explained here.



    Add comment
    10|10000 characters needed characters exceeded

    • I'm getting more and more confused by this thread. OP claims this "can not be extended" (not sure why - there was no response to my comment above). You're saying "very true [...] is not extendable" but then you proceed to provide general information about the IDoc extension. What is a train of thought here? I'm lost, sorry...

  • Feb 09, 2018 at 03:55 AM

    Hi Jelena,

    I got information from ABAP friends that we cannot extend the IDOC as a whole as we are doing for other IDOC example SHP* and others..but in MBGMCR03 we can extend segment wise..

    Reason behind MBGMCR03 not getting extended is -it plays a very important function and if alters then the functionality will change completely. I hope this is my assumption..might be experts can advise more..

    Thanking you.



    Add comment
    10|10000 characters needed characters exceeded

  • Feb 09, 2018 at 06:24 AM

    Check OSS note 913901 - WE30: Rejecting extensions for generated IDoc types

    Add comment
    10|10000 characters needed characters exceeded