Idoc-extend custom idoc orders05

I have to extend standard custom idoc orders05 with one zsegment having 6 fields,so i have to write the code for extending it in the userexit,so only forzsegemnts?is it like that.What is the approach of writing it.

" 1.You must first have to create a custom segemnt with all the necessary fields in WE31.
" 2.Then goto transaction WE30 and extend the basic idoc type ORDERS05 to the required idoc typea  "and add the custome segemnt at the correct hierarchy level.
" 3.Now you need to go the enhancement and populate the fields of the custom segment work area first  "and then pass the work area data with segemnt name to a
SE37-->IDOC_OUTPUT_ORDERS-->DOuble click(PERFORM FUELLEN_IDOC_INTTAB)-->
double click on the ( PERFORM customer_function) after you segment which you want to fill
-->Nex write below code..
Loop at int_edidd.
CASE int_edidd-segnam.    
  WHEN 'E1EDK01'.                       "Read your Segment..if you are using read extension segment.
                                                    "remember always ZSEGMENT is atchild level
                                                    "so read parent segment and add you code at child segment
IF  control_record_out-cimtyp EQ 'ZORDCMPT'.       "check your idoc extension then appen data to segmeny
"add your code and append to zsegment with index captured from parent segment
ENDIF
ENDLOOP.
next activate the segment in SMOD..
Regards,
Prabhudas
Edited by: Prabhu Das on Apr 20, 2009 7:19 PM
Edited by: Prabhu Das on Apr 20, 2009 7:21 PM

Similar Messages

  • Error when trying to extend custom idoc

    Hi ladies and gentlemen,
    I am experiencing problems when I try to extand a custom idoc segment.
    I created a custom idoc (ZBEVINBDEL) with 3 segments, generated it and have tested it successfully.  Now the users have come back and requested additional fields.  When I tried to modify the custom segment (after cancelling the segment and idoc status' from released status, I got the message 'Segment type Zxxxxx.. cannot be changed'  (this is because the idoc segment type has been flagged as generated).
    So I thought I'll create an extension to the corresponding segment.  I've created the extension segment in WE31, but when I try to create the extension (ZBEVINBDELX02), and try to create as new to the linked type ZBEVINBDEL, I get another error message 'Action is not possible for generated idoctypes'.
    Has anybody experienced this problem before, and could you give me an explanation on how to get around these problems, either for changing the segment or extending one.  If the answer lies within BDBG, please explain in detail.
    Cheers,
    Steve

    Reuben,
    In the end, I didn't need to touch the extension.  I was able to achieve my goal by adding the new fields in  my custom structure in SE11, and the new fields came into the idoc automatically.  Then I just had to add code to handle the new fields in my Function module.
    Good Luck,
    Steve

  • [IDOC] Test customized IDOC

    Hey,
    created a customized IDOC in system A and added an inbound
    process code.
    Now I would like to test the IDOC in we19 from system B, but the customized
    IDOC doesn't exist (of course) there.
    How to test this IDOC? Do I have to transport this in system B?
    Can I test IDOC also in system A himself? I just want to test if the configuration
    of process code works.
    In system A I can use we19 with standard inbound, but which receiver port do
    I have to use? I just have created a port to system B. For testing IDOC in just
    one system, do I have to create also a port/logical system to system A?
    thanks
    chris
    Edited by: Christian Riekenberg on Jul 8, 2008 4:18 PM

    I think you want to test only the process code calling the IDoc inbound function module correctly or not?
    If you have RFC connection between B to A. then go to WE19 create a dummy entry giving all the following details
    Receiver                            Sender
    Port                                Port                
    Partner No.                         Partner No.         
    Part. Type                          Part. Type          
    Partner Role                        Partner Role
    Message Type        
    and check in system A that IDoc you got received. It will show as an error , but that errors should shows it getting created in the inbound function module call

  • Extending an IDoc Type or Creating Custom IDoc type

    Hi Experts,
    We need to modify IDoc Type "DESADV01" for adding extra fields. Should I extend this IDoc Type or Create a new Custom IDoc type with the extra fields? Which is the best practice? This is my first time with IDoc functionality. Please let me know.
    Thanks for the help.

    Hi Dev,
    Simple solution man.
    Try to create an extension for the Idoc you wanted to extend.
    Steps would be as follows: -
    1) Go to WE31, create the z-segments and make them ready
    2) Go to WE30, give some name for the extension and select the radio button extension and click on create button
    3) It will ask you necessary details like which idoc you wanted to extend...Give the details and add the z-segments and save it.
    4) Release it
    Thats it.
    Hope this solves your problem.
    Thanks,
    Babu Kilari

  • Regarding Creation of Custom IDOC

    Hi,
    This is Abdullah Shaik. I want to create an IDOC from the existing IDOC. Some times I need to add some segments to the existing IDOC. Can anybody plz let me know the process how to create the Customized IDOC from the Standard IDOC?
    Thanks & Regards,
    Abdullah shaik.

    Hi Abdullah,
    There are basically two types of IDOCs:-
    Basic IDOCs and Extended IDOCs
    Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
    Extending the functionality by adding more segments to existing Basic IDOCs.
    Creation of IDOC
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30)
    Create Message Type ( WE81)
    Assign Idoc Type to Message Type ( WE82)
    Creating a Segment
    Go to transaction code WE31
    Enter the name for your segment type and click on the Create icon
    Type the short text
    Enter the variable names and data elements
    Save it and go back
    Go to Edit -> Set Release
    Go thro' this link:-
    http://help.sap.com/saphelp_46c/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    I hope this provides you a solution.
    Regards.
    Praveen

  • Devloping the Custom IDoc - Integration sceanarios with Peoplesoft

    HI All,
    We are on mySAP ERP 2005 with SAP HR on the same instance box,  PI 7.0 on other instance, and need to integrate for getting the employee data from Peoplesoft into SAP HR.
    I suspect that, this requirement can be fullfilled via Custom Idoc. Correct if I am wrong. plz...need ur expertise inputs for the same.
    In SAP HR we are having some Infotypes. While developing the custome Idoc, each Infotype should  be added as a segment.
    We are having the Standard Idoc for SAP HRMS is  HRMD_A.HRMD_A06.
    In this case how to develop the custom Idoc to include all Infotypes?
    Should I write the code to insert the dato from that Idoc to tables.
    Please suggest me the procedure.
    Regards
    Sridhar Goli

    And you said they are sening IDOC_XML to you through http, then how it is having namespace, it should be plain Idoc_xml
    like
    <?xml version="1.0" encoding="UTF-8" ?>
    - <ORDERS05>
    - <IDOC BEGIN="1">
    - <EDI_DC40 SEGMENT="1">
      <TABNAM>EDI_DC40</TABNAM>
    Can you explain or give the format to better understand.

  • Custom IDOCS and ALE config

    Hi All!
    I am extending a basic IDoc and adding custom segments to it.I will be using change pointers to automatically initiate the ALE process when there are changes in the Master document.
    Please anybody give me the process to follow.Is programming necessary for the extended IDoc to retrieve data.If so please guide me with any pseudo code.
    Thanks in advance
    Prasanna Kumar

    Hi
    Choose SAP Menu ® Tools ® Business Communications ® IDoc Basis ® Development ® IDoc types . The IDoc type editor is displayed.
    If you have not already done so, create a transport request for your development objects (extension segments, extension, function exit and so on). You can access the Workbench Organizer from the editor by selecting Requests (Organizer). From there, select Request ® Create and reply to the questions which appear on screen. By selecting you can return to the IDoc type editor.
    Name your extension in accordance with the customer namespace and choose Extension as the development object. Choose .
    The name of your extension should be no more than 8 characters if you wish to use the extension to communicate with partners who are using SAP Releases prior to 4.0. You can only use extension names with more than 8 characters from Release 4.0 onwards.
    Choose one of the following options:
    Create New: Create the extension without a reference.
    Create copy, which you can then change if necessary
    Create as successor: Note that only one successor is allowed per release for each extension.
    Select the basic type which is to be combined with your extension. Confirm your entries.
    The basic type is displayed as a tree structure. See the color legend (Utilities ® Color legend).
    Position the cursor on the segment where you wish to append the extension segments (the reference segment). Choose . You must now assign attributes for these child segments:
    Mandatory segment (indicator): Must data be written to this segment in the IDoc?
    Maximum and minimum frequency of use: How often may/must a segment occur in the IDoc?
    You can add further children or "grandchildren" to this or any other reference segment in the basic type.
    When the new extension is complete, you can save your entry.
    You should keep the following factors in mind when dealing with extensions:
    Segments must not explicitly occur more than once in the IDoc type - this means that the extension cannot have any segments which already exist in the basic type. This also means that a successor must not have any segments which already exist in the predecessor.
    Parent segments of predecessors must remain parent segments in the case of successors.
    Extension segments cannot be created from reference segments using the Cut and Paste functions and vice versa.
    In the example call your extension Z1ORDERS . Append Z1TEST1 child segment to E1EDP19 reference segment in ORDERS01 basic type. The child segment can be used only once.
    regards
    Prashant

  • How can I split an Orders05 iDoc into multiple iDocs?

    Hello,
    Can one of you experts please tell me how I can split an ORDERS05 iDoc into multiple iDocs based upon Delivery addresses? 
    For example, if the iDoc contains 3 different Delivery Addresses then I need to split it into 3 iDocs.
    It has been suggested to me that I can Create a custom function module. In this custom fm split the idoc into 3 based on the delivery address and create it using the FM MASTER_IDOC_DISTRIBUTE.
    Problem is I don't know how to do this.  Any help is greatly appreciated.  Thanks.
    Dan

    Hi Dan Avis
    Write a Custom  Z program .
    1 get order05 idoc number....
    2 get the segment details...(Based on you condition...)
    3 In a loop  send the data to the FM MASTER_IDOC_DISTRIBUTE  (Based on you condition...)
    4 IDOC will generated,,,every loop and
    5 Change the status of original idoc .
    or
    Create Function module and use the FM as process code to create 3 idocs...and processs...new generated idoc and block original idocs...
    Call me if you have questions  @ 302 290 5677
    Thanks
    Ramesh

  • Creating custome idocs

    hi all
    I am XI consultant
    i want to send IDOC to XI server using ALE..but the IDOC is not present ....the master data is stored in standard sap tables but for them idoc is not present ...so i want to create custom idoc and using change pointer i can send it across ...is this a write approach...? Also please give me the procedure for the above approach as i dont have idea about how to create  custome idoc and send it using change pointer
    thanks
    Sheetal

    Hi
    Data Creation in Idoc
    IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
    asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
    While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
    IDoc is a intermediate document to exchange data between two SAP Systems.
    *IDocs are structured ASCII files (or a virtual equivalent).
    *Electronic Interchange Document
    *They are the file format used by SAP R/3 to exchange data with foreign systems.
    *Data Is transmitted in ASCII format, i.e. human readable form
    *IDocs exchange messages
    *IDocs are used like classical interface files
    IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    FOr testing you can use WE19.
    How to create idoc?
    *WE30 - you can create a IDOC type
    For more information in details on the same along with the examples can be viewed on:
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
    http://www.sappoint.com/presentation.html
    http://www.allsaplinks.com/idoc_search.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://www.erpgenie.com/sapedi/idoc_abap.htm
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30 )
    Create Message Type ( WE81 )
    Assign Idoc Type to Message Type ( WE82 )
    Creating a Segment
    Go to transaction code WE31
    Enter the name for your segment type and click on the Create icon
    Type the short text
    Enter the variable names and data elements
    Save it and go back
    Go to Edit -> Set Release
    Follow steps to create more number of segments
    Create IDOC Type
    Go to transaction code WE30
    Enter the Object Name, select Basic type and click Create icon
    Select the create new option and enter a description for your basic IDOC type and press enter
    Select the IDOC Name and click Create icon
    The system prompts us to enter a segment type and its attributes
    Choose the appropriate values and press Enter
    The system transfers the name of the segment type to the IDOC editor.
    Follow these steps to add more number of segments to Parent or as Parent-child relation
    Save it and go back
    Go to Edit -> Set release
    Create Message Type
    Go to transaction code WE81
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter
    Click New Entries to create new Message Type
    Fill details
    Save it and go back
    Assign Message Type to IDoc Type
    Go to transaction code WE82
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.
    Click New Entries to create new Message Type.
    Fill details
    Save it and go back
    Check these out..
    Re: How to create IDOC
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    ALE/ IDOC
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    go trough these links.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
    1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
    2.IDOCs are independent of the sending and receiving systems.
    3.IDOCs are independent of the direction of data exchange.
    The two available process for IDOCs are
    Outbound Process
    Inbound Process
    AND There are basically two types of IDOCs.
    Basic IDOCs
    Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
    Extended IDOCs
    Extending the functionality by adding more segments to existing Basic IDOCs.
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30)
    Create Message Type ( WE81)
    Assign Idoc Type to Message Type ( WE82)
    imp links
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    www.sappoint.com
    --here u can find the ppts and basic seetings for ALE
    http://sappoint.com/presentation.html
    www.sapgenie.com
    http://www.sapgenie.com/ale/index.htm
    Reward points if useful
    Regards
    Anji

  • Step by step custom IDOC creation

    Hi,
    Can someone give me step by step to create a custom IDOC completely from scratch along with its real tim scenarion ?

    hi Tushar,
    check it out
    There are basically two types of IDOCs.
    Basic IDOCs
    Extended IDOCs
    Idoc Components
    Basic Idoc
    Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
    Extension Idoc
    Extending the functionality by adding more segments to existing Basic IDOCs.
    Creation of IDoc
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30)
    Create Message Type ( WE81)
    Assign Idoc Type to Message Type ( WE82)
    Creating a Segment
    Go to transaction code WE31
    Enter the name for your segment type and click on the Create icon
    Type the short text
    Enter the variable names and data elements
    Save it and go back
    Go to Edit -> Set Release
    Follow steps to create more number of segments
    Create IDOC Type
    Go to transaction code WE30
    Enter the Object Name, select Basic type and click Create icon
    Select the create new option and enter a description for your basic IDOC type and press enter
    Select the IDOC Name and click Create icon
    The system prompts us to enter a segment type and its attributes
    Choose the appropriate values and press Enter
    The system transfers the name of the segment type to the IDOC editor.
    Create IDOC Type
    Follow these steps to add more number of segments to Parent or as Parent-child relation
    Save it and go back
    Go to Edit -> Set release
    Create Message Type
    Go to transaction code WE81
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter
    Click New Entries to create new Message Type
    Fill details
    Save it and go back
    Assign Message Type to IDoc Type
    Go to transaction code WE82
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.
    Click New Entries to create new Message Type.
    Fill details
    Save it and go back
    u can also check all these links related to  idocs
    http://www.allsaplinks.com/idoc_sample.html
    http://www.allsaplinks.com/
    http://www.sap-img.com/
    http://www.sappoint.com/abap.html
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://expertanswercenter.techtarget.com/eac/knowledgebaseCategory/0,295197,sid63_tax296858_idx0_off50,00.html
    http://sap.ittoolbox.com/documents/popular-q-and-a/extending-a-basic-idoc-type-2358
    http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b7eee43d711d1893e0000e8323c4f/frameset.htm
    Regards,
    Naveen

  • Populating custom idoc thro user exit.

    Hi friends,
              How can i populate an custom idoc thro user exit?.I haven't done user exit earlier.So Pls let me know in detail.
    Thanks and regards.
    tharun

    Which standard Idoc did you extend? Is it outbound or inbound? Find out what the processing function module is. WEDI is the area menu transaction for all the IDoc related activities.
    Once you know the function module, you can then find out what the user exit that is there in it. Then you can go to CMOD and in the menu, click on SAP Enhancements and then click on more options in the selection screen. Enter your function module name in the component there and execute the report. See which enhancement it is included in. You can then create a project in CMOD, assign this enhacement and select the user exit and activate the project.
    Next within the function module, in the user exit function module, there will be an include. Double click on it and create upon prompt. After that, it is just your code to fill in the new segment and add it to EDIDD internal table of your function module.
    Srinivas

  • Extend a IDOC

    Hi,
    I need to extend an IDOC, how to get proceed
    Regards
    Ajay

    Write your code in customer exit EXIT_CUSTOMER_FIELDS_FILL in MASTERIDOC_CREATE_COSMAS function module. You can use this exit to fill customer fields.
    You will have to write a badi implementation for gd_user_exit->customer_fields_fill.
    This function module is internally call in transaction BD16.

  • Customized IDOC Issue

    Hi,
    Upto now we worked on standard IDOC's. so no issues upto now.
    Now we are dealing with the customized idoc's. we have one standard idoc in R/3 200 client an we customized that idoc according to our requirement.
    Now we transfered and released that IDOC from 200 client to 300 client for XI use.
    When we are trying to Import the IDOC into IR we are unable to see that Z IDOC( Customized) in the IDOC list.
    We have provided the SAP R/3  300 client user logon details only.
    What may be the Issue
    Regards
    Suman

    Hi,
    You need to add Mesage Type to the Extended IDoc.
    Add message Type to the Extended IDoc in Transaction WE82.
    Please follow steps in Transaction WEDI to extended the IDoc.
    In WEDI  Transaction --> Go to DEVELOPMENT
    and follow all the below steps:
       IDOC Segemnts   -- WE31
       IDOC Types       -
      WE30
       Message Types  -
    WE81
       IDOCType/Message Types  --- WE82
    For Outbound Processing
        Create Process Code --- WE41
    For Inbound Processing
         Register Function Module  --- BD51
         Assign Function Module,Message Type to IDOC Type -- WE57
      Create Inbound Process Code --- WE42.
      Please follow above mentioned Steps.
    Now IDOC will be available in XI to import.
    Thanks,
    Kishore.

  • Extending an IDOC

    Hi All,
    I want to extend an IDOC, which is getting generated while executing the transaction BD16.
    Details of the IDOC are given below:
    Message Type = COSMAS
    Basic type  = COSMAS01
    Basically a new custom field "ZZMFG_RLVNT" was added in the table CSKS. Requirement is to add this field in the new segment of IDOC which gets generated while executing the transaction BD16. I was able to make the neccessary configurations in WE31, WE30, WE81 and WE80.
    Now i am struck at finding suitable user exit for writing code to support IDoc extension.
    Please provide me ur inputs.
    Regards,
    Rajesh

    Hi suresh,
    According to my knowledge userexit is coomks01.
    But badi is available in kbas package K_CCA_CUSTOMER_FIELD.
    check above two options.
    *reward points.

  • Extending Basic Idoc's

    Hi,
       Please provide Step by step procedure to extend Basic Idoc's.
    With Regards,
    Nelson

    Choose SAP Menu ® Tools ® Business Communications ® IDoc Basis ® Development ® IDoc types . The IDoc type editor is displayed.
    If you have not already done so, create a transport request for your development objects (extension segments, extension, function exit and so on). You can access the Workbench Organizer from the editor by selecting Requests (Organizer). From there, select Request ® Create and reply to the questions which appear on screen. By selecting  you can return to the IDoc type editor.
    Name your extension in accordance with the customer namespace and choose Extension as the development object. Choose .
    The name of your extension should be no more than 8 characters if you wish to use the extension to communicate with partners who are using SAP Releases prior to 4.0. You can only use extension names with more than 8 characters from Release 4.0 onwards.
    Choose one of the following options:
    Create New: Create the extension without a reference.
    Create copy, which you can then change if necessary
    Create as successor: Note that only one successor is allowed per release for each extension.
    Select the basic type which is to be combined with your extension. Confirm your entries.
    The basic type is displayed as a tree structure. See the color legend (Utilities ® Color legend).
    Position the cursor on the segment where you wish to append the extension segments (the reference segment). Choose . You must now assign attributes for these child segments:
    Mandatory segment (indicator): Must data be written to this segment in the IDoc?
    Maximum and minimum frequency of use: How often may/must a segment occur in the IDoc?
    You can add further children or "grandchildren" to this or any other reference segment in the basic type.
    When the new extension is complete, you can save your entry.
    You should keep the following factors in mind when dealing with extensions:
    Segments must not explicitly occur more than once in the IDoc type - this means that the extension cannot have any segments which already exist in the basic type. This also means that a successor must not have any segments which already exist in the predecessor.
    Parent segments of predecessors must remain parent segments in the case of successors.
    Extension segments cannot be created from reference segments using the Cut and Paste functions and vice versa.
    In the example call your extension Z1ORDERS . Append Z1TEST1 child segment to E1EDP19 reference segment in ORDERS01 basic type. The child segment can be used only once.

Maybe you are looking for