IDoc Editing Segment

Hi all,
  I have a requirement where the field length in one of the fields in the segment (Z1PXXXX) has to be changed. Since the segment definition is in different SAP release, i created a new version and tried to edit it. But all the fields from the older version is grayed out.
Could you please tell me how to change the field length?
Thanks,
Sri

It is always better to use IDOC either by loading the structure as an IDOC or by External Definition.
Loading it as imported message will lead into consistencies for future.
If you are not able to change the field length, try to take care of it during Mapping.
Regards
Krish

Similar Messages

  • Issue:EDI: Syntax error in IDoc (mandatory segment missing):Idoc extention

    Hi all,
    I have extended the the standard IDOC MATMAS05  classification view with structure as below-
    E1MARAM                        Master material general data (MARA)--->Mandatory segment
         Z1KLART                        KLART --->Extended chaild to E1MARAM
             Z1CLASS                        segment for class --->Extended chaild to Z1KLART
             Z1CHARACTERISTIC               CHARACTERISTIC --->Extended chaild to Z1KLART
         E1MARA1                        Additional Fields for E1MARAM
         E1MAKTM                        Master material short texts (MAKT) --->Mandatory segment(Child   to                                                                               
    E1MARAM )
    I am getting an error in IDOC fro material master as:EDI: Syntax error in IDoc (mandatory segment missing ).
    Diagnosys By system is :*The segment E1MAKTM has the attribute 'Mandatory' in the syntax description of the basic type MATMAS05 (customer enhancement ZMATMAS05). However, the segment is missing in the IDoc. The segment number logged in the status record identifies the item before which the segment is missing.
    This error may have been triggered by an unidentifiable segment before the expected mandatory segment.*
    Please help to resolve the issue.
    Thank you.
    Edited by: sanu debu on Apr 30, 2009 11:25 AM
    Edited by: sanu debu on Apr 30, 2009 11:31 AM

    Hi,
       You cannot add an segment in the middle of other segments.
    YOu have to add any segment at the last.
    If you want to add a segment as the child of another segment, it should be added after the last child of the parent segment.
    In you case, you have to add your segment after the E1CUCFG segment.(NOt under that segement)
    Regards,
    Ravi Kanth Talagana

  • How to findout in IDOC whch segment error out

    Hi All,
      If an IDOC error out then how to know which IDOC segment needs to be corrected without going through all the segments. Is there any transaction or table exists to know the status of error segment.
    Thanks in Advance
    Swapna!

    Hi,
    There is no such transaction. Some time in WE02 it shows the errored data segment. To check if i shows the error segment or not,
    - go to WE02 and display your errored idoc.
    - from the menu select "Edit --> Segments with errors".
    If it shows errored segments, you are lucky. Otherwise you will have to figure out which segments is with error.
    Regards,
    RS

  • Creating own IDOC with segments

    can any one let me know the steps to create <b>Z</b> IDOC and segments required  for  it.
    and also the sample code (program) to poplulate the data into those segemnts from a (excel/csv file )or tables.
    Thanks..

    hi Aday,
    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
    Regards,
    Naveen

  • EDI: Syntax error in IDoc (mandatory segment missing)

    HI all,
    Error Message - EDI: Syntax error in IDoc (mandatory segment missing)
    Status ID - E0
    Message No - 072
    Status of the IDoc - 26
    Please help me how to solve this issue?
    Thanks,
    Srini

    Hi,
    This error normally comes up when the sequence of segments has been disturbed.
    For successfully posting an IDOC you need to maintain the sequence of the segments as in WE30.
    You can also check which segments are mandatory in WE30 by clicking on the segment name and the pop up that comes.
    Thanks,
    Manish

  • Determine Partner number based on IDoc Data Segments

    Are there any user exits or BADI, which can be used to determine Control record parameters (Partner), based on IDoc Data segments? This is for an Inbound IDoc, into ECC.
    I found EXIT_SAPLEDI1_001. But, this has only control record. It is used to determine control record parameters, by using control record only.
    Thanks,
    Juwin

    Dear Juwin,
    Could you please provide some info. about what you are trying to achieve by trying to determine the partner dynamically?
    If the scenario is something like 'Partner A should get data related to only plant 1000 and Partner B should get data related to only plant 2000', you could use filters in the Distribution model to achieve this.
    BR,
    Aashrith

  • Idocs n segments

    what are the types of idocs and wat are the types of segments?

    Hi Sunil,
       Idoc type are Two ( Tcode we30 )
    1. Basic Idoc ( Ex: cremas, debmas,matmas, orders01, And Some Z Idocs        (Which you will create )
    2. Extended Idoc : Theses are Generally created when you want to do any modification or enhancements to the existing basic idocs.
    Segments are two
       Parent And Child will attached to parent
    They may be Customised or Standard
    Thanks
    manju
    If you are plesed, Reward points

  • Need IDOC and segment for mappping the sales order number

    Hi,
    we need the IDOC name and segment for mapping the sales order number created by oracle in sap for transaction VA01.
    Whether the sales order number created by Oracle can be used to create the sales order in sap using the idoc ACC_SALES_ORDER01?
    . If we can do,then what is the segment and field for the sales order number in the idoc ?
    Please reply asap it's very urgent
    Thanks
    Edited by: suresh kumar nandhagopal on May 16, 2008 12:07 PM

    Hi,
    IDOC for sales order is ORDERS05. Segment E1EDKA1, for field go to SE11 and enter E1EDKA1 to find field for sales order.
    Cheers.
    ...Reward if useful.

  • IDOC Missing Segment Field

    Hi,
    Some of my outbound IDOC's are missing a particular field in the Segment.....
    This is probably because that Segment field don't have any value and hence missing from IDOC.
    What can be the possible approach for Solving this probelm?

    Hi Abhishek,
    Can you please get the solution for such issue?
    I didnt aware of Enhancement Spot...
    Looking for your reply..
    Regards,
    Raghu
    Edited by: Raghu Raman on Jan 5, 2009 1:27 PM

  • IDoc - Custom segments added?

    Hi,
    I am new to IDOC and working on Sales Order BOM inbound interface. Using BOMORD01 Idoc and filling E1STZUM, E1KDSTM and E1STPON segments. Getting a message saying "Segment cannot be identified" (ZE1FIKP) and also "Custom segments added" but actually my intention is not to add any custom segments, why I am getting this message and how to correct it.
    Thanks in advance.
    Regards,
    Balaji Viswanath.

    Hi,
    Just For your understanding...
    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
    for futher info check the below links
    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
    <b>if u find it useful plz mark the points</b>

  • Outbound idoc: creating segment with name 'BATCHCOLLECTION'

    Hello gurus.
    I'm developing my own idoc outbound xml solution and one of the xml requirement is that the segmentnames and fieldnames is not in the SAP name range (of course).
    I have e.g a segment called BATCHCOLLECTION and when I try to create it in transaction WE31 I receive the following message:
    Error: Name range violation : Name BATCHCOLLECTION not permitted in CUSTOMER system
    Is it possible to map all the names before the outbound xml is created ?
    How ?
    Please advice.
    Edited by: Erik Hoven on Feb 20, 2009 10:01 AM

    Hi,
    You can find information on this post :
    https://www.sdn.sap.com/sdn/collaboration.sdn?node=linkFnode6-1&contenttype=url&content=https://Re: Sending IDoc Batches to SAP: Issue with Header Mapping for SNDPRN
    There is no problem if you send idoc one by one with one EDIDC. But if you want to send Idocs with differents EDIDC, today, there is no way.
    Regards,
    Chris

  • Idoc filetering ,segment filtering

    hi ,
    can any one send me the document to create idoc filtering thru bd53,and segment filtering thru bd56.
    [email protected]
    points are assured!
    thanks
    Ganesh
    Message was edited by:
            ganesh ram

    Hai,
    Segment Filtering:
    Segment filtering can be achieved using T/Code BD56. Here you can suppress a whole segment irrespective of data inside it . You have to give Message Type / Sender Partner / Receiver Partner.
    Data Filtering:
    Data filtering can be done in distribution model where you can restrict whole IDOCS or partials IDOCS to be send based on data in fields inside IDOC depending on whether the segment in which you filter is at the highest level or at a lower level. For example in MATMAS if you put a filter of E1MARCM for a particular plant , only data for this plant will go and other plants will be ignored.
    Pls go thru this Link,
    http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a611c507d11d18ee90000e8366fc2/frameset.htm

  • XI IDOC missing segment definition in type E1LFM1M

    Hi experts,
    we have recently upgraded our ERP system to NW 702 EH5. As aresult a new segment definition was added to our segment type E1LFM1M ( segment def. E2LFM1M007). The problem we are havign is that our XI system is still running on NW700 and it doesnt have this segment defintion. Since the upgrade we are getting an error in transaction RFC complaining about the new segment definition E2LFM1M007 everytime we try to send a vendor from ERP to SUS using BD14. Is there a way we can deactivate the new segment definition E2LFM1M007 in segment type E1LFM1M?
    Thanks,
    Abdul.

    Hi Abdul,
    Actually it does not matter what are your systems' versions, PI can always handle an IDoc properly. All you need to do is perform the following steps in your PI system:
    1. Log on to ABAP stack, go to t-code idx2, find your ECC system and that particular IDoc (I believe this will be CREMAS) and delete its metadata.
    2. Log on to Enterprise Services Repository, find your SWCV where the IDoc definition was loaded, and load it again from your ECC system, then activate the change.
    3. If necessary, also adjust the message mapping to use/not use the new segment. Activate your changes.
    Once you have these steps completed, you are ready to retest your scenario and say goodbye to the error.
    Hope this helps,
    Grzegorz

  • Flat File IDOC - ECC, segment defn x in IDoc type y CIM type do not exist

    Hi,
    I'm working on idoc flat file > sap scenario.  Everything seems to be working up until the point where I get an error message:
    EDISDEF: Port EDIPORT segment defn E2FINBU000 in IDoc type FIDCCP01 CIM type  do not exist
    I've loaded the meta data, and the file structure is fine.  I believe the issue is related to PI not having the idoc I'm interested in listed in WE30.  How do I reference the standard IDOC type FIDCCP01?  Ideas I've had are around SWCV or transport from another system, the first I'm not sure which SWCV, the later seems a bit of a bodge and I dont like the idea.
    Thanks
    James.

    Hmm.. some light for the situation.  Seems that the segments imported are:
    E1FINBU     E2FINBU     31I
    E1FINBU     E2FINBU001     40A
    E1FINBU     E2FINBU002     40B
    E1FINBU     E2FINBU003     45A
    E1FINBU     E2FINBU004     45B
    E1FINBU     E2FINBU005     46A
    E1FINBU     E2FINBU006     46C
    Which indeed does not have E2FINBU000, which the IDOC is most definitely trying to pass.  I can only guess that the middleware producting this IDOC is flawed, and that standard SAP ALE will accept this as E2FINBU (It works into another SAP system without XI).
    Guess I've answered my own question, but feel free to offer light for points
    Thanks,
    James.

  • IDOC ORDERS05: Segment E1EDPA1Doc.item partner information is not filled

    Hello,
    I'm working on the AFS-Retail Interface for Orders.
    In the first step we create a sales contract in AFS with the combined demand from a retail purchase order and in a second step the sales order call-offs which are the Retail orders for the stores (NB; one PO for one store).
    The problem is in the sales order call-off. In the Retail outbound IDOC the information about the  relevant ship-to stands only the header segment E1EDKA1 (PARVW = WE).
    In the AFS IDOC inbound the ship-to is written in the header partners of the sales order. But because the information is missing on item level the information is copied from the sales contract which leads to the wrong ship-to for the items in the sales order.
    For the communication we are using the basic type orders05. Is there a possibility to fill the item partner segments E1EDPA1 out of the standard or do I need to implement an user exit in the Retail IDOC outbound process so that the partner information is filled also on item level?
    Thanks in advance.
    Regards,
    Christine

    Hi Christine
    I am working on SAP AFS 6.0.. I Had same issue.....When sales order ref to a contract....i resoved it
    u need to write user exit for this....
    Ramesh

Maybe you are looking for