Adding a segment to a Basic IDOC type

Hi every one,
How do i add a segment that I have created to an existing Basic Idoc type ?.
Can some one give me a solution for this.
Thanks,
Arul.

hi ,
Idoc extension can be done with 4 steps
1. creation of new extension type and a new segment
2. creation of a idoc type
3. link idoc type to message type
4. check the idoc type.
1. creation of new extension type and a new segment
we30--idoc typesobject name-extension type-create-create new-create-place the cursor on the location
2. step:
we30----
3. we82 or we 30
4. WEDI
If you find it useful plz mark the points
Regards,
Naveen

Similar Messages

  • Restructuring the basic IDoc type DELVRY03

    Hi experts,
    My rek  is to restructure the Basic Idoc type DELVRY03 for outbound delivery.
    I am using IDOC_OUTPUT_DELVRY.
    Is there any exit or badi for this.
    Thanks

    we31:
    Create your new segment.
    Save and remember release (edit-set release)
    we30:
    Create your new idoc type. Create like extension.
    In your linked idoc type fill your standard idoc type.
    Press create new sement button for add segments and put your Z segment created in we31 with min and max quantity.
    Save and release the idoc type
    Regards

  • Hi gurus what is basic IDOC type

    hi gurus what is basic IDOC type

    Basic Type:
    Basic IDoc type defines the structure and format of the business document that is to be exchanged between two systems.
    Segments:
    Segments form the basic building blocks of an IDoc type and are used to store the actual datta. A segment type is the name of a segment and is independent of the SAP elease. A segment definition is the release-specific name of a segment.
    Steps in creating Segments:
    T.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 and Go back.
    Go to Edit -> Set Release.
    Repeat the steps to create more segments.
    IDOC TYPE:
    Business data is exchanged with an external system using the IDoc Interface.
    IDoc types (Special Structures) An IDoc type is defined through its permitted segments. Segments can be dependent on each other (parent and child segments). The IDoc interface can check for each IDoc whether thhe segments contained are compatible with thhe definitiion of its type. This systax check is activated or deactivated in the Partner Profiles.
    Steps in creating IDoc Type:
    T.Code WE30 to create IDoc Type.
    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.
    Message Type:
    Steps in Creating Message Type:
    T.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:
    T.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.
    Reward Points if useful.

  • 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.

  • Port &1 segment defn &2 in IDoc type &3 CIM type &4 do not exist

    Hello,
    I've a question. We would send an standard IDOC from the 4.6C System to our SAP Xi 3.0. I customized the XI with TA IDX1 and IDX2. If we trigger the IDOC to XI I get the follow error message back:
    Port SAPQ73 segment defn E2EDL20002 in IDoc type DELVRY03 CIM type &4 do not exist.
    The IDOC Vers. is 4.6. In another system with IDOC Vers. 6.20 isn't a problem. So I think its a problem of the IDOC Version, or? So I checked the forum about this topic but I didn't find anything. So, I hope you can help me. Kind Regards Stephan

    Hello,
    I have exactly the same issue... We're currently upgrading our SAP system 4.7 to ECC6.0. We're also upgraded the system to an unicode system.
    Before those change, the interface between SAP and Xi worked well. Since the upgrade, those idocs don't pass any more and get the same error message than Stephan.
    I've checked the authorization of the RFC user and he has SAP_ALL and SAP_NEW. Partner profile, RFC connection, port and distribution model didn't changed.
    Do someone have an idea why this can appear ?
    Thanks in advance.

  • Basic IDOC types

    what are these  ORDERS05, DELIVERY03 & WMMBID02
    i found that these are basic idoc types. what does it mean?
    Regards,
    pandu.

    Some IDoc types are supplied by SAP in the standard system,
    these are the basic types. Other IDoc types are customer
    extensions. In these cases, a basic type is combined with
    an extension which is created by the customer, according to
    certain rules. Unlike customer extensions , these extended
    basic types are upward compatible.
    regards,
    srinivas
    <b>*reward for useful answers*</b>

  • Segment definition in an IDOC type

    Hi,
    What does Maximum number and Minimum number stand for in an segment definition within an IDOC type? I think there are two options.
    1. the occurence number of the segment type in an IDOC type defintion
    2. the occurence number of the segment data of a special IDOC
    1 or 2. Please suggest ... It will better if there is any example for me to understand it. Thanks.
    Regards

    Option 2 is correct from my observation.

  • How to Create IDOCs for a Custom Basic IDOC Type

    Hi friends,
    I Have a Custom Basic IDOC Type.
    For that IDOC Type i need to Create an IDOC for every Header Item.
    The Header Item may have variation (Different) number of Line Items.
    in this case can i Use
    MASTER_IDOC_DISTRIBUTE and create the Idoc for each Header Item.
    or is there any way to create the IDOCs
    Thanks in Advance.
    Ganesh.

    Hi ,
    If I am not wrong you need to pass data via fm "MASTER_IDOC_DISTRIBUTE".
    So you can transfer row by row data into SDATA filed of structure type :EDID ,
    by concatenating the data into one field of type sdata. and passing it into the fm.
    I.e defining a internal table of type EDIDD.
    Try this :
    DATA : itab TYPE TABLE OF edid,
           itab1 TYPE TABLE OF edidc.
    LOOP AT itab2 INTO wa_itab2.
    CONCATENATE wa_itab2-t1 wa_itab2-t2 wa_itab2-t3 wa_itab2-t4 wa_itab2-t5
      INTO result.
      itab-sdata = result.
      APPEND itab.
      all function 'MASTER_IDOC_DISTRIBUTE'
       exporting
         master_idoc_control                  =itab1
      OBJ_TYPE                             = ''
      CHNUM                                = ''
       tables
         communication_idoc_control           =
         master_idoc_data                     =itab.
    EXCEPTIONS
      ERROR_IN_IDOC_CONTROL                = 1
      ERROR_WRITING_IDOC_STATUS            = 2
      ERROR_IN_IDOC_DATA                   = 3
      SENDING_LOGICAL_SYSTEM_UNKNOWN       = 4
      OTHERS                               = 5
      IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.

  • Basic IDoc type ORDLGT01 is unknown

    Hi All,
    When I test run to execute  business object from BUS2032 from SWO1,
    I got the following message:  "Basic IDoc type ORDLGT01 is unknown".
    Please let me know why its so happening.
    Regards
    Bhaskar

    PLEASE SEARCH SDN before posting ([rules of engagement|https://wiki.sdn.sap.com/wiki/display/HOME/RulesofEngagement])
    [SAP Note 607330 ALE: Basic type ORDLGT01 unknown|http://service.sap.com/sap/support/notes/607330]

  • EDI 821 and EDI 823 field mapping file and basic IDOC type and message type

    Hi All,
    We are facing some issues regarding EDI 821 and EDI 823 file mappings.
    We are mapping EDI 821 and EDI 823 transactions into SAP using IDOCs. Currently we are using the below entries
    EDI 823 - Lock Box
    Basic IDOC type - FINSTA01
    Message type - FINSTA
    Process Code  - FINS
    The problem is we are able to get the IDOC into SAP with status red and the various errors were due to not able to create the lockbox entry in SAP and once we got yellow status also but the lock box entry was not created and the errors are like No Conversions,no header etc.
    EDI 821 -
    Basic IDOC type - PEXR2002
    Message type - PAYEXT OR REMADV
    Process Code  - PEXC OR REMA
    We are facing the same problem here also and the internal payment order is not creating in SAP and IDOC was generated with yellow status and red status.
    We are trying different combinations but nothing is working so far.
    I need the following things to proceed furthur.
    1)Are the IDOC , Message and process codes are correct that I am using now for both EDI 821 and EDI 823
    2)If those are not correct, can you please let me know the correct entries
    3) Please provide me the field mapping if any one of you have worked earlier for both the above IDOC and message type or new ones and we have one field mapping now but if you can send it to me then  I can re check it.
    4) Do we have to create any configuraion or customizing in SAP to create the IDOC in green status and if so please let me know the customizing steps and procedures for both EDI 821 and EDI 823.
    thanks in advance for all your help.
    Please let me know if my question is not clear.
    Thanks,
    Ramesh.

    Hi Ramesh,
    I believe you are using those interfaces with the business partner type as Bank, Whatever idoc type, message type and process code you have used are perfectly correct.
    First of all did you enable your bank for EDI, the house bank has to be EDI enabled first then only your idoc's can be processed, talk to your fi functional consultant and he might help you.
    Are you can give me the exact error and i can help you as well.
    Thanks,
    Mahesh.

  • I am receiving Basic Idoc Type error while I am executing SWO1 for BKPF

    Hi
    I am receiving Basic Idoc type error message while I am trying to test BKPF object. Please note that the Business Object is delegated to a custom BO. Can anyone tell me where the linkage is established between IDOC type and BO.
    Thanks
    Arghadip

    Arghadip,
      Can you check the transaction WE57?
    Thanks

  • EDISDEF:Port sid segment defn Z2Q0015000  in idoc type... CIM

    Hi Experts,
    I am getting the error "EDISDEF:Port <sid> segment defn Z2Q0015000  in idoc type..YHRMD. CIM"
    in sm58 of sender sap system. I thought it would be the metadata issue and tried to search the segment 'Z2Q0015000' but unable to find any thing in sender sap.
    Even i have tried in idx2. in xi
    Please help !!
    Regards,
    Suresh.

    Hi Michal,
    Many thanks for your input. The issue is coz the metadata in IDX2 is not updated. The sender system was trying to post the data from the segment which XI doesnt have.
    I just tracked the segment from we60 based on the error message and checked the idoc structure in IDX2.Then imported the idoc into IDX2 from sender sap.
    once again thanks a lot !!
    Regards,
    Suresh.

  • Basic idoc type for asset creatioon and asset acquisition

    Hi
    Please can anybody tell me the basic IDOC type provided by SAP for
    - Asset creation
    - Asset acquisition.
    Thanx in advance....

    Hi,
    Go through this link
    http://www.sap-basis-abap.com/fico/configuration-in-asset-accounting.htm
    help.sap.com/bestpractices/BBLibrary/documentation/B44_BB_ConfigGuide_EN_Nordics.doc
    Reward points if found helpful...
    Cheers,
    Chandra Sekhar.

  • Diff between IDOC TYPE & Basic IDOC TYPE ?

    what is the Diff between IDOC TYPE & Basic IDOC TYPE ?

    Hi,
    IDoc type contains basic IDoc type and extension.
    Extension is a sub-object which extends an existing basic IDoc type. Extension types are not delivered by SAP. They can be created by the customer.
    Regards,
    Ferry Lianto

  • Custom segments to basic IDOC type without extension

    Hi,
    Is it possible that an IDOC has custom segments which are getting populated and the basic type does not have any custom segments.
    How should we find from where the custom segments are getting populated and displayed?
    Regards,
    Subhashini

    Hello,
              Lets say in DELVRY05 Idoc Type, we have a Segment Called E1EDL20 and since this is a Standard SAP Provided Basic Type, it will not have any Custom Segments ( Z-Segments). Now, If I want some additional Information to be populated as part of a Custom Segment, what I would do is to Create an IDoc Extension ZDELVRY05 with reference to the Basic Type DELVRY05 and Create a Custom Segment Z1EDL20 (Per Say) in which I'll populate the Custom Data Fields using an Exit. So, unless we create an IDoc Extension for a Basic Type, the Standard SAP Basic Type will not have any Custom Segments-Fields (Z-Segments).
    Thanks,
    Venkata Phani Prasad K

Maybe you are looking for