Connection coversion rules - segment types in IDocs

Hi everyone.
Could anyone tell me if there is a way (a table for example) to connect the conversion rules of the IDocs a type of segment?
Thank you.

Create Segment at We31 transaction and once you done then set release.
if you want to set Mandatory,Min ,max then use We30 Transaction
Thanks
seshu

Similar Messages

  • Problem with creation of IDOC Segment Type

    Hi,
    I tried to create IDOC Segment Type Z1LFA1 but error
    prompted "Structure Z1LFA1 already exist.".
    I tried deleting it at se11  but prompted
    "You cannot edit object R3TR TABL Z1LFA1 with the
    standard editor"                          
    and at sm30-TADIR, but prompted
    with "Cannot delete object directory entry, object exists."
    How will go about this??
    Please help!
    Thanks!

    hi,
    yup, tried doing that on we31 but the segment does not exist yet.
    we're currently upgrading from 4.6 to ecc, I think the structure
    was tranferred to our ecc client but the idoc segment and idoc type were not. I'll just have to transport it then.
    Thanks!

  • IDOCS: Segment Definition and Segment Type

    Hi Gurus,
    We are working on IDOCs and trying to send a Location Master IDOCs to Third party system.
    1. In the IDOC print preview we are in a position to see the IDOC segment type Ex: E1TPLOC but customer is asking for Segment definition E2TPLOC.
    When we go through the documentation:
    u2022     Segment Type consists of Segment definition with Version and Release.
    u2022     Segment Definition will contain the Field names
    u2022     E1TPLOC, E1TPDLH, E1KNVAM, E1TPTRM & E1TPSHH Segment types with concerned Segment definitions are
                         E2TPLOC,E2TPDLH, E2KNVAM
    How to see the Segment definition types?

    Hi,
    You can see the documentation in the transaction WE60 by giving the IDOC Basic type and extension if you have any.
    E1 and E2 are the same, when you see the definition of the segment the naming convention will be E2 and when populating the data it will be E1.
    I believe he is asking the segment definition alone, you go to WE60 transaction and give the inputs and click the parser button and that will give you the definition of the idoc and which you can share it with your partner.
    Thanks,
    Mahesh.

  • IDOC Segment Definition received instead of Segment type

    Hello Folks,
    When i send a Z Idoc Segment from A to B System, It is successfull from A System, but in B System sometimes its erroringout because in the inbound idoc Segment Definition is coming instead of Segment type.
    For Example
    From A System I have sent Z1P0002 segment
            B System I have received Z2P0002000(Which is the segment definition for Segment type Z1P0002)
    Any inputs to above problem?

    Hi,
    The problem may be due to system B using a older release version of the IDoc. In those scenarios, even though your IDoc type is recognized, it may not be possible for the reciever to determine the right segment version of the reciever.
    There are options in the WE20 partner profile configuration, Field Segment release in IDoc type and Segment Appl. rel. which enable the partner system preventing from erroring out.
    BR/Yogesh
    Edited by: Yogesh Surender on Jun 1, 2009 12:34 PM

  • Split Single IDOC into Multiple IDOC's Based on Segment Type

    Hi Experts,
    I have a scenario IDOC to FILE ,  Split Single IDOC into Multiple IDOC's based on Segment Type
    Outbound:
    ZIdocName
    Control Record
    Data Record
    Segment 1
    Segment 2
    Segment 3
    Status Record
    I should get output like below
    Inbound:
    ZIdocName
    Control Record
    Data Record
    Segment 1
    Status Record
    ZIdocName
    Control Record
    Data Record
    Segment 2
    Status Record
    ZIdocName
    Control Record
    Data Record
    Segment 3
    Status Record
    Please suggest me step by step process to achieve this task.
    Thanks.

    Thanks a lot Harish for reply.
    I have small doubt. According to your reply , If we have N number of segments in single IDOC with same fields in all segments then for splitting Single IDOC into Multiple IDOC's based on Segment Type we need to duplicate N number of target IDOC tree structure.
    Is that possible to Split single IDOC into Multiple IDOC's based on Segment Type using only one Target IDOC structure without duplicating the Target IDOC structure tree.

  • Create Individual Idocs Based on Parent and Child Segment type

    Hi Experts,
    I have a scenario IDOC to FILE ,  Split Single IDOC into Multiple IDOC's based on parent and child Segment Type
    For example If 3 child segments are same and 1 segment is different under parent segment then 3 same child segments are clubbed and create single idoc under parent segments and 1 different child should create in individual idoc under parent segment.
    Note : Same logic should work for N number of Parent Segments and Child Segments.
    Outbound:
    ZIdocName
    Control Record
    Data Record
    Parent Segment A
       Child Segment 1
       Child Segment 1
       Child Segment 1
       Child Segment 2
    Parent segment  B
       Child Segment 3
    Status Record
    I should get output like below
    Inbound:
    ZIdocName
    Control Record
    Data Record
    Parent segment A
      Child Segment 1
      Child Segment 1
      Child Segment 1
    Status Record
    ZIdocName
    Control Record
    Data Record
    Parent segment A
      Child Segment 2
    Status Record
    ZIdocName
    Control Record
    Data Record
    Parent Segment B
      Child Segment 3
    Status Record
    Please suggest me step by step process to achieve this task.
    Thanks.
    Ram

    Hello,
    Segment won't hold any value, so filter criteria should be there on some field wich exist in Parent node and chile node?
    Paste ur XML?
    Try this(Assuming u have some fields in parent/child segment on which u want to define filter criteria):
    Parent Field--UseOneAsMany----RC----
                                      ------------------Concat ----splitbyvalue(value change)--collapse context --- ZIdoc
    Child field-- RC----------
    Child field--RC--splitbyvalue(valuechange)--CC -Splitbyvalue(each value) -- ParentSegment
    Child field--RC--splitbyvalue(valuechange)--- ChildSegment
    RC -> Remove Context
    CC - Collapse Context
    Note - i haven't tested ur mapping, so make sure to adjust context in mapping
    Thanks
    Amit Srivastava
    Message was edited by: Amit Srivastava

  • Inbound side idoc segment defination is showing instead of segment type

    Dear all,
                 i created z idoc ZMIGO961 and  z segment ZJ1IW in both source and destination, when i send the idoc from the source to destination, in destination it is showing the segment defination i.e ZJ1IW000 in idoc instead of segment type ZJ1IW in  my idoc.
    plz help .
    regards,
    Edited by: manoj kv on Apr 4, 2010 9:18 PM

    Hi manoj kv 
    segment defination :  ZJ1IW000  indicates segment is ZJ1IW & version is 000
    Go to T code we31  in Destination System
    Enter the Segment Name and Check Defination Screen.....then you will see the segment defination :  ZJ1IW000
    Hope above info helps... you..
    Thanks
    Ramesh

  • Idoc segment version in idoc type

    hi,
    we have just upgraded our R/3 system from 4.6c to SAP ECC 6.0. We then tried to send idocs to SAP XI 3.0 SP 20. However the idocs failed due to wrong segment version of idoc. It did not match the loaded metadata in XI. I know that in WE20 you can control the segment version used to send to XI. In the communication channel in XI you can also set the segment version.
    So my question is: Is the correct way to handle sytems requiring diffenrent verions to import the newest metadat in idx2 and then  control the versions asper the above paragraph?
    Any comments are apreciated.
    kr Rasmus

    Hi,
    for sending IDocs to XI no adapter is necessary. It should be enough to reload the metadata in idx2:
    http://help.sap.com/saphelp_nw04/helpdata/en/ab/bdb13b00ae793be10000000a11402f/frameset.htm
    Regards
    Patrick

  • How to add a custom segment in standard IDoc?

    Hi,
    I want to add a custom segment in stanard IDoc type (eg. MATMAS). I don't want to go for extended idoc (copying stanard idoc into zidoc and adding custom segment).
    Please tell me.

    Hello
    Transaction BD10 uses fm MASTERIDOC_CREATE_REQ_MATMAS which in turn uses MASTERIDOC_CREATE_MATMAS to create and distribute material master IDocs.
    Fm MASTERIDOC_CREATE_MATMAS belongs to function group MV01 in package MGV. Here you will find the user-exit function group XMGV.
    Perhaps EXIT_SAPLMV01_002 might be useful for you.
    Regards
      Uwe

  • Get the value of a particular field in a segment of an Idoc

    Hi All,
    I have a requirement where I need to write a report which will fetch the value of a particular field in a segment of an idoc.
    I have the idoc number segment and field name as input parameters by which I can fetch Sdata from EDID4 but the confusion is how to find the exact field value from that Sdata. How to Map the SDATA to the segment structure.
    Please advice...

    Hi,
    I have one last doubt that may be you people can help with... The user will be giving the segment name and field name as input. So by following Kesav's code while i can get all the values in the segment structure at runtime please suggest how to display any one field from that structure given that that particular field will come at runtime.
    EX: user gives an idoc number 123 (say belonging to Orders basic type)
                                 segment E1EDK01
                                 field  BELNR.
    So i need to display the value of E1EDK01-BELNR of idoc number 123.
    Please suggest how to achieve this....

  • Error when Adding a segment to an IDOC

    Hi I have added one segment to an IDOC through one user exit and it is giving the error with status 26.
    Here I am pasting the error details,
    The segment E1IDT02 does not occur at the current level of the basic type PEXR2001 (extension ).
    This error can have several reasons:
    The segment E1IDT02 is assigned to a group whose header segment does not occur.
    The segment E1IDT02 does not exist in the syntax description of the basic type PEXR2001 (extension ).
    The sequence of segments in the group in which the segment appears is incorrect.
    Previous errors ('mandatory' segment or group missing) may be due to this error.
    Can any body help me, and let me know what can I do to avoid this.
    Thanks,
    Deepak.

    Actually in the basic type of IDOC, there is no segment with this name. But I am adding this directly in an user exit. Can you tell me what is the actual procedure to add a new segment to the basic type of IDOC
    Thanks
    ravi

  • How to include segments to  standard idoc PEXR2002 ..

    How to include the below segments to the standard  idoc PEXR2002 ..
    E2EDK02
    E2EDK12
    I want to map the check number to E2EDK12-BELNR depending on the document number.
    I have a recording in shdb..but my real question is it where to have this logic..
    Any suggestion would be highly appreciated.
    Thanks,

    U will have to create IDoc Extension for this.
    Goto WE30 select the Radio button Extension.
    Link it with the basic Idoc Type.
    Then attach the new segments in the IDoc.

  • Use of segment E1KONP in IDOC COND_A01

    We are today using the VARKEY field in segment E1KOMG in IDOC COND_A01 with all the fields in the spesified condition table for a condition type.
    Instead of generating X quantity of IDOC´s we would like to repeat the segment E1KONP with different customers. All the other fields in the condition table have the same values.
    The field customer is available in segment E1KONP.
    What can we do with the IDOC or other configuration to tell the IDOC using customer from segment E1KONP and not from field VARKEY in segment E1KOMG? We still need to use VARKEY for the other fields in the condition table, since we use som Z fields in our condition table.
    I am struggling findig documentation according to our problem.
    Best regards,
    Terje

    Hi Terje Pedersen,
    Did you get a solution to your problem?? I too am facing similar kind of problem. Instead of multiple IDOCS for COND_A01, I need to create only one.
    Please suggest.
    Thanks & Regards,
    Abhishek

  • Why message type if  idoc type or idoc is already there.

    Experts.
    this has been posted several times and i gone through so many threads but stil some confusion . So anyone can tell in simple terms what is the difference and why sap has given this two instead of one.
    Diff. with IDOC type
    An IDoc type specifies the structure of the data.
    A message type specifies the meaning of the data
    *****from the above statements , by seeing the name of the idoc type ex matmas01 also we ca n say that it is used for material data, then why message type matmas needed?

    Hi,
    Idoc type means combination of segements
    Message type means Combination of idoc type
                              or
    Message type mean combination of Idoc type + Extension idoc type( Custom segments added to idoc type)..
    Example:-
    If you want to fill the data to custom segment which is available at exension idoc ...
    then first check the message type then check basic idoc type then check it contains exetension idoc type ..then fill the segment
    Generally the communication occurs between system through message type...
    Prabhudas

  • Problem in viewing a field in Segment type

    Hi All,
              I have added a field to an existing segment type . Now the problem is that I am not able to see the field when an Idoc is created.I am able to see the fields that was previously added, but  not the one which I have added..Can you plese suggest me how can I rectify that...
    It will be very helpful if you can send me steps of doing it..
    Thanks in advance.
    Regards,
    Asish Dash

    If your other two checks are correct and only if you want to
    know the program or function module please check following things.
    1. Each Message type will having a posting program, genarally it will be a function module.
    2. This function module will be attached to a Process code.
    3. You can check the the process code name in the Partner profiles.
    4. After knowing your process code, please check WE41 and WE 42 for the function module name.
    5. From this you can debug and find out.
    Points please if this info is helpful..............
    Thanks,

Maybe you are looking for