Custom IDOC type Segment-field length change

Hello,
We have a custom segment developed for triggering Outbouds. I'm tring to change the Field length of a deta element used for one of the fields in the segment.
But after chaning the data element and activating it also, the changes are not effecting in WE31/ in the structure of the segment.
Process I'm following:
we31 <segment>
......cancel release
Change data element and activate
....set release.
Please suggest if something else can be done
Thanks,
Lucky.

> @Sarvesh: The IDOC segment has been released.  I also re-imported the IDOC into XI - is that what you mean by 'reloaded'?
No, re-importing in XI is different from reloading the metadata into ABAP stack of XI using IDX2 transaction. So if you have not done this, then this could be the main reason of truncating the length.
Regards,
Sarvesh

Similar Messages

  • Idoc segment field length changes

    Hi friends,,
    I am new to idoc.
    My requirement is in my segment
    i am having 5 fields and also this segment is already realeased one.
    i wnat to change the field length from 10 to 20 . how to do this ?
    actually what i did is
    1. i cancel the release for that segment.
    2. in that field inside the dataelement i changed the field length from 10 to 20.
    3. data elemnt get chaged from 10 to 20 but Export length for that field in Idoc segment still retain the 10 only
    can you plz how to resolve this
    deva

    Hi,
    The way you used is right. ( cancel release or create a new segment )
    After you cancel release, try delete that field, and insert a new one.
    If it isn't valid still,  create a new segment instead.
    Regards
    Sam

  • Adding fields to custom idoc type

    Hi,
    i have a query regarding adding fields to custom idoc type.
    To add fields to custom idoc type we are trying to cancel the release from we30, but we are facing error that 'The release of basis type cannot be reset'
    When we are trying to cancel release from we31we are facing error 'Error while ressting release of segment z type'.
    Kindly suggest the solution to add fields in basic idoc type.
    Thanks & regards,
    Farheen.

    Reason that you are getting these errors is that you cannot cancel
    the release of an extension made in previous version . Instead you have to create a new extension.
    1.It is not possible to change a segment definition which is released in a
    lower release.
    2.You must create a new segment definition for the new release e.g. 620 with a new segment
    field with the appropriate length.
    In transaction WE20, outbound parameters, you can specify
    the "segment release in IDoc type" for the communication.
    Please read the F1 help of this field for further information.
    3.For your own segments you can define a new version of the segment
    tcode  WE31 -> Add Version
    Thanks!

  • 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

  • When do we ceate custom messagae type apart for custom idocs type

    Hi all.
        Can u pls let me know when do we create custom message type in ALE/IDOCS. what I know is we can create a custom message when we create custom idoc type & when we have reduced idoc type.Pls let me what are other cases in which I need to create a custom message type.Thanks in advance.
    Kind regards,
    sami.

    I think these are the only cases where we need to create. Its basically when we dont have standard SAP message type available.

  • Custom IDoc Type missing segment parent/child relationships

    Hi.
    I copied the standard ORDERS05 IDoc type to a custom type and cut out quite a few segments.  My new IDoc type is setup with parent/child segment relationships, similar to many of the original relationships in ORDERS05. 
    When I use the standard FM IDOC_OUTPUT_ORDRSP to generate an IDoc, it's not creating with parent/child segment relationships.  It's placing the children at the same level as the parent. 
    Anyone know what I'm doing wrong?
    Thanks!
    Cal

    figured out the problem.  was missing a required segment used to establish the parent/child relationship.

  • 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 nested segment fields update

    Hi all,
    I have a requirement like this
    I have an IDOC say DOC1
    DOC1 has a segment say SEG1
    SEG1 has a child segment say CLD1
    CLD1 has a filed  say FLD1 .
    i need to update the data in field FLD1.
    can any one  please tel me how to read data in the FLD1 and how can I update that.

    Hi Vijay,
    Basically, it is used the same approach to update parent/child segment(s). You need to loop at internal table EDIDD and find the corresponding segment. Then you move to work area, do the modification and lastly update the internal table EDIDD with new value(s).
    Please follow step 2 to read and update the child segment field.
    DATA: wa_cld1 like CLD1.
    LOOP AT itab_edidd WHERE segnam = 'CLD1'.
      wa_cld1 = itab_edidd-sdata.
      IF wa_cld1-field1 = <the condition>.
        wa_cld1-field1 = <new value>.
        itab_edidd-sdata = wa_cld1.
        MODIFY itab_edidd.
        EXIT.
      ENDIF.
    ENDLOOP.
    Regards,
    Ferry Lianto

  • Task Name - Field length Change

    Can we change the task name length for team members when adding a new task?
    Regards, Syed Faizan ur Rehman, CBPM®,PRINCE2®, MCTS

    Hi Syed,
    If you want to change the task field length, it is not possible. It is a native field which is predefined in the system.
    But if you want to change the length of the task name itself (for example "design" by "system design"), then it it possible since what matters is the task UID and not the task name.
    Hope this helps,
    Guillaume Rouyre, MBA, MCP, MCTS |

  • Field length change in Web Dynpro Components iView

    Hi,
    We are using SAP MDM Web Dynpro Components - Configuration Manager (NW7.3) to develop the UI. One of the issue while disply field is, Though field maintained in MDM has only 2 charaters UI that displays a full-screen-width field.
    I would like to display actual field length maintained in reposiroy for each field. Is it possible??
    Cheers,
    Rc

    This is closed.
    By mistake Raised Twice....I guess I need break

  • Custom idoc segment fields not populated

    Way back in 1999 someone create a custom Idoc type with custom Idoc segments in it.  Unfortunately, they forgot to release one of the segments.
    Recently a change was request to add new fields to this custom segment.  In order to get the fields transported the segment had to be released.
    All worked fine in Dev and the new Idoc segments were populated as expected.  However when the idoc segment was moved to the test system all visually appears to be fine but when the idoc is created (status 50) the new fields are not popultated. 
    In 40B the start of the inbound process was IDOC_INBOUND_DATA.  Does anyone know what the new starting point is in 4.7??
    I beleive the error is actually that SData is not reading all the input values and stopping right where the old fields end in teh custom segment.
    Thanks,
    Anthony

    additionally,
    SAP will not allow us to release the basic idoc type because it was released in 40B.  It also will not allow us to cancel the release since we are now in 620.  So, unless anyone has input for this I think the only solution will be to create a successor IDoc type and change our apps to use the new IDoc type with it's enhancements.

  • Custom IDOC changes in the IDoc structure

    HI experts,
    I have made some changes in the Custom IDoc Structure
    But when I have transported the changes like I have 5 fields in the custom IDoc I changed the data type of field 2 changing the length of that field to 132 but when i am executing that all the other remaining fields getting populated in that 2nd field. Is there any way this problem can be resolved
    early answer is appreciated.......
    advance thanks
    srini

    Hi Srinivas,
    I would like to confirm some things. First your IDoc struc had field2 which is of length less than 132 and then you increased it to 132. Now you are now using <b>WE19</b> to test your IDoc. The reference IDoc no. that you gave was the IDoc that had been generated while the length was less than 132.
    If this is what you have done, then you will have this issue. I will tell you why. When you created the IDocs, this field was less than 132, then in the EDIDD-SDATA which is a character field of length 1000 bytes would have got filled with a different position.
    Say for example you have two fields in a segmentthey are A(of lenght 10) and B(of length 20). When you create IDoc, EDIDD-SDATA(which actually contains data would have been like the following:
    Say if A = 'ABC', B = 'DEF'
    EDIDD-SDATA = 'ABC       DEF                 '
    If you see it carefully it is a string of charachter where A starts at 1st and B starts at 11th position of the string. Now you changed length of A to 15. Then A would start from 1st Position upto 15th position while B starts from 16th upto 35. Hence when the WE19 tool extracts data from EDIDD, it extracts it as:
    A = 'ABC       DEF  '
    B = space
    Hope this answers your question.
    Regards,
    Srikanth
    PS: Same will be the case with WE09 as well. The IDocs which was created before changing the length will still look distorted.
    Message was edited by: Srikanth Lodd
    Message was edited by: Srikanth Lodd

  • EDI Outbound IDOC Remove unused fields from segment

    Hi All,
    I am configuring a outbound idoc scenario for Message type ORDERS. The basic type for this message type is ORDERS05.
    The segment E1EDKA1 has 44 fields, I need only the first field and the last field of this segment.
    How do I remove the unused fields in this segment ?  I Tried BD56 and BD32 But they are for removing the complete segment and so does not serve my purpose.
    Any pointers to this issue is appreciable .
    Regards,

    Hi,
    Segmetns of standard message types can be deleted from BD53. But I don't think deleting fields would be possible from segments of standard idoc type. What you can do is you can create your own custom idoc type with the fields you want and allign it with the standard message type ORDERS. This should solve your purpose.
    BR,
    Atanu Mukherjee

  • Custom Idoc-segments

    Hi,
    I am working on inbound processing of idocs. The issue is to post production confirmations into SAP using idocs sent by the middleware. I have to create a custom idoc for this purpose. I know the steps for creating a custom idoc type and message type.
    The problem is that the number of segments of each idoc sent by the middleware is not fixed. They wanted the idoc to be setup in such a way that each time they send an idoc they want segments repeated based on the entries in the flat file.
    Please help me out.Thanks

    HI,
    For this i have a solution.
    you can make two segments one is header and other is item.
    in Header segment only setno field ocours. and in item segment all three fields will be there. like this.
    HEADER INFORMATION:
    1
    ITEM INFORMATION:
    1 a i
    1 b o
    i c o
    Now you fill your each idoc for each setno. and distribute it. and in receving system you will got a IDOC for each SETNO. Then you can loop in header segment and find all its items from item segment.
    Regards,
    HRA
    <b>Reward points if my post helps you.</b>

  • Idoc segment for shpmnt notification for idoc type shpmnt02

    Hi gurus,
               I have to find the idoc segment for shipment notification,idoc  type which we are going to use is shpmnt02 or shpmnt01,Can any one of you please tell me the idoc segments for this idoc type with fields and table name?.Thanks in  advance.

    Hi Nagarathinam
    You can use transaction WE60 for documentation on IDOCs
    Best regards,
    Chris

Maybe you are looking for