Reg: Idoc edit

Hi All
How cen we edit the Idoc .After edit the status becomes 32
Is there any standard programme for editing idoc.
could some ls help me.
Regards
Raj

IDOC Status
Reward Points..

Similar Messages

  • Reg: IDOC Purchase Order

    Hi All,
    I have a requirement to trigger a Purchase Order from Stock Transport Order (STO).
    So whenever the STO is created, IDOC needs to be triggered & create a auto PO in the same client.
    I tried with some examples from forum thread, but all goes in vain.
    Could you please advice, what are all the steps needed to achieve this with in a same client. I have created a dummy logical system for Inbound processing with tRFC. Could you please advice this step is really needed.
    Thanks & Regards,
    Uswin
    Edited by: Uswin B on Nov 21, 2011 11:40 AM

    1. You need to setup output determination on the STO (transaction NACE, Application EF). You can create output type similar to NEU and assign it to o/p determination procedure linked to your STO document type. You can't use NEU though as it is configured to create ORDERS message type IDoc. To create PO you need message type PORDCR1.
    2. You have to write your own function module to output IDoc of message type PORDCR1 and call MASTER_IDOC_DISTRIBUTE to trigger it. It is easy if you only map the minimum required fields so that the IDoc doesn't fail in syntax and take it from there. There are no standard functions that I know that created PORDCR1 message type IDoc (others chip in if you know). You need to create your own outbound process code with ALE processing as medium in the output type.
    3. You can set the IDoc from the output type with direct 2 (as inbound) and set up partner profile in the output condition record to point to your inbound LS partner profile
    4. You need to assign inbound message type:PORDCR1, IDOC type PORDCR101 and Process code: BAPI to your receiving LS partner profile
    Those are the settings you need to do. I can't elaborate as there are many things specific to your implementation

  • Reg: IDOC

    Moderator message: please use a meaningful subject in future.
    Hi,
      I created an IDOC to transfer data between clients, same server.
    Here I defined the port , partner functions , in both clients. but still i am getting that 'ALE LINK ERROR'.
    If anybody knows guide me.
    -Thanks .
    Balajee Jeyaraj
    Edited by: Matt on Nov 19, 2008 11:30 AM

    Please check  ALE configuration.huge number of threads available on this topic please search

  • Reg:IDOC Sender side settings

    Dear All,
    My scenario is IDOCPIMDM
    I have created all the basic ALE settings and they are,
    SAP R/3:
    1)RFC Destination (SM59)
    2)Logical system
    2)Port (We21)
    3)Partner Profile (WE20) name same as logical system
    SAP XI:
    1) RFC Destination (SM59)
    2) Create Port (IDX1)
    3) Load Meta Data for IDOC (IDX2) 
    In Integration Directory,Adapter-Specific identifiers,its shows the logical system that was created in R/3 server.
    Could anyone suggest me on the following queries,
    1)Whether I have to create anymore steps other than this.
    2)Should I need to create Logical system in PI
    3)Should I need to create a distribution model.
    4)What are the details ,I should enter in sender/receiver details ,while we use WE19 transaction code for triggering the idoc.
    Thanks in Advance,
    Lavanya.B

    Hi Lavanya,
    The steps are the standard steps.
    I hope it should work.
    In PI, you need to create on LS (Business Service) or Business System.
    If you are creating Business Service, it would be mapped via SLD otherwise the Business service needs to be mapped to the indoc(Go to Business Service--> Edit to add Outbound interface as Idoc name)
    Regarding Triggering Idoc,
    You need to provide the sender and receiver details
      Receiver Port
      Receiver Partner no
      Partner Type
    Sender Port  
    Sender Partner no
    Part type
    Hope this helps you.
    Regards,
    Sushama

  • Idoc edited with new values

    Hi,
       I have an idoc with no 32945925 which is in green with status 70 but this idoc is edited and a new idoc 33010450 has been generated but this idoc is in yellow with status 69.
       How far I can assure that idoc 33010450 has been successfully processed and it has been posted Or do i need to do anything manually  because it is in yellow status.
    Regards,
    Karthik.k

    Hi,
    Normally the idoc will not be processed.It depends on the partner profile configuration.If it is set that it should be processed immediately it will be done automatically.But normally it is set as collect idocs,In that case we have to process them separately.
    Regards,
    Sasi

  • Azhar--azhar :) reg. idoc

    Hi azhar,
    I did ALE-IDOC with the help of ur document yaar. It beyond expression....thing is outbound process for message type MATMAS  is fine...but when i go to other client....i m not able to see the data in MM03...
    I shall be thankful to u yaar...i've give me ur gmail Id. pleas..
    Regards,
    [email protected]

    http://www.thespot4sap.com/Articles/SAP_ALE_Introduction.asp
    hi,
    steps for ALE IDOC is ::
    ALE IDOC Steps
    Sending System(Outbound ALE Process)
    Tcode SALE ?3 for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 !V Create Model View
    Tcode BD82 !V Generate partner Profiles & Create Ports
    Tcode BD64 !V Distribute the Model view
    This is Receiving system Settings
    Receiving System(Inbound ALE )
    Tcode SALE ?3 for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 !V Check for Model view whether it has distributed or not
    Tcode BD82 -- Generate partner Profiles & Create Ports
    Tcode BD11 Getting Material Data
    Tcode WE05 !V Idoc List for inbound status codes
    Message Type MATMAS
    Tcode BD10 !V Send Material Data
    Tcode WE05 !V Idoc List for watching any Errors
    1)a Goto Tcode SALE
    Click on Sending & Receiving Systems-->Select Logical Systems
    Here Define Logical Systems---> Click on Execute Button
    go for new entries
    1) System Name : ERP000
    Description : Sending System
    2) System Name : ERP800
    Description : Receiving System
    press Enter & Save
    it will ask Request
    if you want new request create new Request orpress continue for transfering the objects
    B) goto Tcode SALE
    Select Assign Client to Logical Systems-->Execute
    000--> Double click on this
    Give the following Information
    Client : ERP 000
    City :
    Logical System
    Currency
    Client role
    Save this Data
    Step 2) For RFC Creation
    Goto Tcode SM59-->Select R/3 Connects
    Click on Create Button
    RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
    give the information for required fields
    RFC Destination : ERP800
    Connection type: 3
    Description
    Target Host : ERP000
    System No:000
    lan : EN
    Client : 800
    User : Login User Name
    Password:
    save this & Test it & RemortLogin
    3)
    Goto Tcode BD64 -- click on Change mode button
    click on create moduleview
    short text : xxxxxxxxxxxxxx
    Technical Neme : MODEL_ALV
    save this & Press ok
    select your just created modelview Name :'MODEL_ALV'.
    goto add message type
    Model Name : MODEL_ALV
    sender : ERP000
    Receiver : ERP800
    Message type :MATMAS
    save & Press Enter
    4) Goto Tcode BD82
    Give Model View : MODEL_ALV
    Partner system : ERP800
    execute this by press F8 Button
    it will gives you sending system port No :A000000015(Like)
    5) Goto Tcode BD64
    seelct the modelview
    goto >edit>modelview-->distribute
    press ok & Press enter
    6)goto Tcode : BD10 for Material sending
    Material : mat_001
    Message Type : MATMAS
    Logical System : ERP800
    and Execute
    7)goto Tcode : BD11 for Material Receiving
    Material : mat_001
    Message Type : MATMAS
    and Execute --> 1 request idoc created for message type Matmas
    press enter
    Here Master Idoc set for Messge type MATMAS-->press Enter
    1 Communication Idoc generated for Message Type
    this is your IDOC

  • Reg:IDOC -sales order creation

    Hi All,
         I am trying  to create sales order through IDOCS.Basic type is SALESORDER_CREATEFROMDAT201.
    My requirement is to know any user-exits where in I need to add to my code to hardstop sales order creation if the storage location which I am passing is marked for deletion.
    Kindly reply as soon as possible.
    Regards,
    Kaveri

    Hi,
    Check this one it will help u how to enhance the idocs.
    If we wnat to extend the idoc use the segments for adding the fields. use the tcode WE30 and we31.
    Please reward points if it is useful.
    Go through the following Steps For ALE/IDOC
    ALE IDOC
    Sending System(Outbound ALE Process)
    Tcode SALE ? for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 ? Create Model View
    Tcode BD82 ? Generate partner Profiles & Create Ports
    Tcode BD64 ? Distribute the Model view
    Message Type MATMAS
    Tcode BD10 ? Send Material Data
    Tcode WE05 ? Idoc List for watching any Errors
    Receiving System(Inbound ALE )
    Tcode SALE ? for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 ? Check for Model view whether it has distributed or not
    Tcode BD82 -- Generate partner Profiles & Create Ports
    Tcode BD11 Getting Material Data
    Tcode WE05 ? Idoc List for inbound status codes
    ALE IDOC Steps
    Sending System(Outbound ALE Process)
    Tcode SALE ?3 for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 !V Create Model View
    Tcode BD82 !V Generate partner Profiles & Create Ports
    Tcode BD64 !V Distribute the Model view
    This is Receiving system Settings
    Receiving System(Inbound ALE )
    Tcode SALE ?3 for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 !V Check for Model view whether it has distributed or not
    Tcode BD82 -- Generate partner Profiles & Create Ports
    Tcode BD11 Getting Material Data
    Tcode WE05 !V Idoc List for inbound status codes
    Message Type MATMAS
    Tcode BD10 !V Send Material Data
    Tcode WE05 !V Idoc List for watching any Errors
    1)a Goto Tcode SALE
    Click on Sending & Receiving Systems-->Select Logical Systems
    Here Define Logical Systems---> Click on Execute Button
    go for new entries
    1) System Name : ERP000
    Description : Sending System
    2) System Name : ERP800
    Description : Receiving System
    press Enter & Save
    it will ask Request
    if you want new request create new Request orpress continue for transfering the objects
    B) goto Tcode SALE
    Select Assign Client to Logical Systems-->Execute
    000--> Double click on this
    Give the following Information
    Client : ERP 000
    City :
    Logical System
    Currency
    Client role
    Save this Data
    Step 2) For RFC Creation
    Goto Tcode SM59-->Select R/3 Connects
    Click on Create Button
    RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
    give the information for required fields
    RFC Destination : ERP800
    Connection type: 3
    Description
    Target Host : ERP000
    System No:000
    lan : EN
    Client : 800
    User : Login User Name
    Password:
    save this & Test it & RemortLogin
    3)
    Goto Tcode BD64 -- click on Change mode button
    click on create moduleview
    short text : xxxxxxxxxxxxxx
    Technical Neme : MODEL_ALV
    save this & Press ok
    select your just created modelview Name :'MODEL_ALV'.
    goto add message type
    Model Name : MODEL_ALV
    sender : ERP000
    Receiver : ERP800
    Message type :MATMAS
    save & Press Enter
    4) Goto Tcode BD82
    Give Model View : MODEL_ALV
    Partner system : ERP800
    execute this by press F8 Button
    it will gives you sending system port No :A000000015(Like)
    5) Goto Tcode BD64
    seelct the modelview
    goto >edit>modelview-->distribute
    press ok & Press enter
    6)goto Tcode : BD10 for Material sending
    Material : mat_001
    Message Type : MATMAS
    Logical System : ERP800
    and Execute
    7)goto Tcode : BD11 for Material Receiving
    Material : mat_001
    Message Type : MATMAS
    and Execute --> 1 request idoc created for message type Matmas
    press enter
    Here Master Idoc set for Messge type MATMAS-->press Enter
    1 Communication Idoc generated for Message Type
    this is your IDOC
    Change Pointers
    I know how to change the description of a material using ALE Change Pointers.
    I will give the following few steps
    1) Tcode BD61---> check the change pointers activated check box
    save and goback.
    2) Tcode BD50---> check the MATMAS check box save and comeback.
    3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
    4) Tcode BD52---> give message type : matmas press ok button.
    select all what ever you want and delete remaining fields.
    save & come back.
    5) 5) go to Tcode MM02 select one material and try to change the description and save it
    it will effects the target systems material desciption will also changes
    6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
    give Message type : MATMAS and Executte
    ALE/IDOC Status Codes/Messages
    01 Error --> Idoc Added
    30 Error --> Idoc ready for dispatch(ALE Service)
    then goto SE38 --> Execute the Program RBDMIDOC
    29 Error --> ALE Service Layer
    then goto SE38 --> Execute the Program RSEOUT00
    03 Error --> Data Passed to Port ok
    then goto SE38 --> Execute the Program RBDMOIND
    12 Error --> Dispatch ok
    Inbound Status Codes
    50 Error --> It will go for ALE Service Layer
    56 Error --> Idoc with Errors added
    51 Error --> Application Document not posted
    65 Error --> Error in ALE Service Layer
    for 51 or 56 Errors do the following steps
    goto WE19 > give the IDOC Number and Execute>
    Press on Inbound function Module
    for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
    regards,
    satish.

  • REG: IDOC  Acknowledgement

    Hi all,
             I have a scenario where my idoc has to reach the receivers end. After every  sucessful transaction ,my XI is sending an acknowledgement to the sender.  Actullay I dont  want any acknowledgement from XI. So please tell me method by which i can disable this acknowlegement settings.
    Thanks,
    Siva.
    Edited by: siva krishna on Jul 31, 2008 6:44 AM

    Hi Siva,
    do chk this links
    Configuration Tips for a Business Service/Integration Process to send back ALE audit IDOC
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb
    Thanx
    Sampath

  • Reg: Idoc  generation

    Hi All,
    AS per my understanding for SPEC2K idoc generation, SAP generates two IDOCS. one of standard SAP message type and another is of SPEC2K type .
    <b>My requirement</b> : if the customer requested items are not available then both the SAP message IDOC and SPEC2K idocs should be generated.
    If the customer requested items are available then only SAP message type idoc should be triggered and <b>SPEC2K idoc should not be triggered</b>.
    Is there any settings by which I can achive this.
    Thanks in Advance.
    Vijay.

    Go through the following Steps
    Try with the follwoing steps
    Sending System(Outbound ALE Process)
    Tcode SALE „³ for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 ¡V Create Model View
    Tcode BD82 ¡V Generate partner Profiles & Create Ports
    Tcode BD64 ¡V Distribute the Model view
    This is Receiving system Settings
    Receiving System(Inbound ALE )
    Tcode SALE „³ for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 ¡V Check for Model view whether it has distributed or not
    Tcode BD82 -- Generate partner Profiles & Create Ports
    Tcode BD11 Getting Material Data
    Tcode WE05 ¡V Idoc List for inbound status codes
    Message Type MATMAS
    Tcode BD10 ¡V Send Material Data
    Tcode WE05 ¡V Idoc List for watching any Errors
    1)a Goto Tcode SALE
    Click on Sending & Receiving Systems-->Select Logical Systems
    Here Define Logical Systems---> Click on Execute Button
    go for new entries
    1) System Name : ERP000
    Description : Sending System
    2) System Name : ERP800
    Description : Receiving System
    press Enter & Save
    it will ask Request
    if you want new request create new Request orpress continue for transfering the objects
    B) goto Tcode SALE
    Select Assign Client to Logical Systems-->Execute
    000--> Double click on this
    Give the following Information
    Client : ERP 000
    City :
    Logical System
    Currency
    Client role
    Save this Data
    Step 2) For RFC Creation
    Goto Tcode SM59-->Select R/3 Connects
    Click on Create Button
    RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
    give the information for required fields
    RFC Destination : ERP800
    Connection type: 3
    Description
    Target Host : ERP000
    System No:000
    lan : EN
    Client : 800
    User : Login User Name
    Password:
    save this & Test it & RemortLogin
    3)
    Goto Tcode BD64 -- click on Change mode button
    click on create moduleview
    short text : xxxxxxxxxxxxxx
    Technical Neme : MODEL_ALV
    save this & Press ok
    select your just created modelview Name :'MODEL_ALV'.
    goto add message type
    Model Name : MODEL_ALV
    sender : ERP000
    Receiver : ERP800
    Message type :MATMAS
    save & Press Enter
    4) Goto Tcode BD82
    Give Model View : MODEL_ALV
    Partner system : ERP800
    execute this by press F8 Button
    it will gives you sending system port No :A000000015(Like)
    5) Goto Tcode BD64
    seelct the modelview
    goto >edit>modelview-->distribute
    press ok & Press enter
    6)goto Tcode : BD10 for Material sending
    Material : mat_001
    Message Type : MATMAS
    Logical System : ERP800
    and Execute
    7)goto Tcode : BD11 for Material Receiving
    Material : mat_001
    Message Type : MATMAS
    and Execute --> 1 request idoc created for message type Matmas
    press enter
    Thanks & regards
    Sreenivas
    Here Master Idoc set for Messge type MATMAS-->press Enter
    1 Communication Idoc generated for Message Type
    this is your IDOC
    Thanks & Regards
    Abhay.
    rewards point

  • 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

  • Reg idoc for purchase order

    Dear  Friends,
    I am trying to transfer data of purhcase order (ME21) (with header and item details) from one client to another client.
    I am using idoc ORDERS05 for updating the data.
    But i am unable to map the fields of the ME21 to the fields of segments of the idoc ORDERS05.
    Note:  I am using these fields of me21.
    *header details
        ekko-ebeln.                             "Purchasing document
        ekko-bukrs.                             "company code
        ekko-bsart.                             " Purchasing Document Type
        ekko-ekgrp.                             " Purchasing Group
        ekko-ekorg .                             " Purchasing Organization
        ekko-lifnr.                              " Vendor Account Number
        ekko-aedat.                            "date on Which Record Was Created
        ekko-pincr.                            "Item Number Interval
        ekko-spras.                            "language
        ekko-zterm.                             "Terms of Payment Key
        ekko-waers.                              "Currency Key
    *item fields
        ekpo-ebelp.                             "Item Number of Purchasing Document
        ekpo-ematn.                            " Material Number
        ekpo-txz01.                            " Long Material Number for MATERIAL Field
        ekpo-werks.                          "Plant
        ekpo-lgort.                           " Storage Location
        ekpo-matkl.                          " Material Group
        ekpo-menge.                         " Purchase Order Quantity
        ekpo-meins.                           " Purchase Order Unit of Measure
        ekpo-netpr.                         "Currency amount
    pls help.
    Regards,
    Vinod Kumar.

    Hi
    chek with currect version of Message  type,if it's not in message type do customise segement's.
    cheers
    venu

  • Reg : Idoc Transfer From SAP R/3 to Gentran

    Hi Floks /
    Any body can transfer SAP R/3 idoc to external Sterling Gentran intgration suite . what are process steps required to sending and what are the transaction codes are available in Gentran and Sap .
    can u please help me out.
    thanks
    suresh

    HI,
    See the below links
    In Gentran
    XI with Gentran
    XI vs Gentran for EDI
    SAP ECC 5.0 Upgrade questions with Gentran, BDC, screens
    Gentran EDI ?
    Interuppting/debugging response from Gentran
    Gentran and XI 3.0 question
    Interuppting/debugging response from Gentran
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d53af8ca-0801-0010-08b0-dce9e02130a8
    In R3 IDocs
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
    IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
    /people/ravikumar.allampallam/blog/2005/06/24/convert-any-flat-file-to-any-idoc-java-mapping - Any flat file to any Idoc
    /people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm - Collection of IDoc to Single File
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
    File-XI-IDoc Scenario - File to Idoc
    idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
    idoc erros - http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
    idocs - /people/sravya.talanki2/blog/2005/08/24/do-you-like-to-understand-147correlation148-in-xi
    idoc mapping - /people/james.guanzon/blog/2006/03/23/how-to-support-industry-standards-in-xi-part-ii-of-iii--mapping
    IDoc erros troubleshooting - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
    /people/sravya.talanki2/blog/2006/12/27/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-iii
    see the below links to get more details about IDocs
    ALE/ IDOC/ XML
    Troubleshooting of ALE Process - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
    http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
    IDOC Convertion
    /people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
    Please check this online document for ALE and IDoc.
    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
    serialization /people/alessandro.guarneri/blog/2006/11/26/content-based-serialization-dynamic-queue-name-in-xi
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://www.henrikfrank.dk/abapexamples/IDOC/gl_postings2.htm
    http://searchsap.techtarget.com/ sDefinition/0,,sid21_gci852485,00.html - 45k - Cached - Similar pages
    Process codes in IDOC
    http://help.sap.com/saphelp_erp2005/helpdata/en/dc/6b806743d711d1893e0000e8323c4f/frameset.htm
    http://edi.stylusstudio.com/msg04418.htm
    Check this link to find out the difference b/w ALE,IDOC and BAPI
    http://www.sap-img.com/abap/ale-bapi.htm
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    ---Split messages :
    /people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
    /people/sudharshan.aravamudan/blog/2005/12/01/illustration-of-multi-mapping-and-message-split-using-bpm-in-sap-exchange-infrastructure
    Regards
    Chilla

  • Reg : IDOC data mapping

    Hi All,
    Which is the function module which Extracts the data from the application document ( Sales order or quotes ) and populates to the SAP message type Idoc segments.
    what are the SAP table involved in doing this mapping.
    Thanks & Regards.
    vijay

    Unfortunately the mapping is not in any table but in the source code as extracted here:
    e1cuins-class_type        cuins-class_type
    e1cuins-inst_id           cuins-inst_id
    e1cuins-obj_key           cuins-obj_key
    e1cuins-obj_txt           cuins-obj_txt
    e1cuins-obj_type          cuins-obj_type
    e1cuins-quantity          cuins-quantity
    e1cuprt-class_type        cuprt-class_type
    e1cuprt-inst_id           cuprt-inst_id
    e1cuprt-obj_key           cuprt-obj_key
    e1cuprt-obj_type          cuprt-obj_type
    e1cuprt-parent_id         cuprt-parent_id
    e1cuprt-part_of_no        cuprt-part_of_no
    e1cuval-author            cuval-author
    e1cuval-charc             cuval-charc
    e1cuval-charc_txt         cuval-charc_txt
    e1cuval-inst_id           cuval-inst_id
    e1cuval-value             cuval-value
    e1cuval-value_txt         cuval-value_txt
    e1edk01-autlf             xvbak-autlf
    e1edk01-belnr             ekko-ebeln
    e1edk01-bsart             ekko-bsart
    e1edk01-curcy             iso_waers
    e1edk01-kzabs             pekko-kzabs
    e1edk01-kzazu             xvbkd-kzazu
    e1edk01-lifsk             xvbak-lifsk
    e1edk01-recipnt_no        ekko-lifnr
    e1edk01-vsart             xvbak-vsbed
    e1edk01-zterm             ekko-zterm
    e1edk02-belnr             ekko-angnr
    e1edk02-belnr             ekko-ebeln
    e1edk02-belnr             ekko-konnr
    e1edk02-belnr             ekko-submi
    e1edk02-belnr             pekko-labnr
    e1edk02-datum             ekko-bedat
    e1edk02-uzeit             sy-uzeit
    e1edk03-datum             ekko-angdt
    e1edk03-datum             ekko-bedat
    e1edk03-datum             ekko-bnddt
    e1edk03-datum             ekko-bwbdt
    e1edk03-datum             ekko-ihran
    e1edk03-datum             ekko-kdatb
    e1edk03-datum             ekko-kdate
    e1edk03-datum             pekko-eindt
    e1edk03-datum             sy-datlo
    e1edk14-orgid             ekko-bsart
    e1edk14-orgid             ekko-bukrs
    e1edk14-orgid             ekko-ekgrp
    e1edk14-orgid             ekko-ekorg
    e1edk17-lkond             ekko-inco1
    e1edk17-lkond             xvbkd-inco1
    e1edk17-lktext            ekko-inco2
    e1edk17-lktext            xvbkd-inco2
    e1edk18-prznt             ekko-zbd1p
    e1edk18-prznt             ekko-zbd2p
    e1edk18-tage              ekko-zbd1t
    e1edk18-tage              ekko-zbd2t
    e1edk18-tage              ekko-zbd3t
    e1edka1-bname             ekko-verkf
    e1edka1-bname             t024-eknam
    e1edka1-ihrez             ekko-ihrez
    e1edka1-ihrez             ekko-unsez
    e1edka1-ilnnr             h_iln_vendor
    e1edka1-lifnr             h_pekko_werks
    e1edka1-lifnr             pekko-werks
    e1edka1-orgtx             t024e-ekotx
    e1edka1-pagru             ekko-ekgrp
    e1edka1-paorg             ekko-ekorg
    e1edka1-partn             ekko-lifnr
    e1edka1-partn             ekko-logsy
    e1edka1-partn             lfa1-lifnr
    e1edka1-partn             lfb1-eikto
    e1edka1-partn             pekko-kunnr
    e1edka1-partn             t000-logsys
    e1edka1-partn             xvbpa_we-kunnr
    e1edka1-parvw             'EZ'
    e1edka1-parvw             h_parvw
    e1edka1-parvw             'LF'
    e1edka1-parvw             'WE'
    e1edka1-spras             ekko-spras
    e1edka1-telf1             ekko-telf1
    e1edka1-telf1             t024-ektel
    e1edka1-telfx             t024-telfx
    e1edkd1-ekgrp             ekko-ekgrp
    e1edkd1-ekorg             ekko-ekorg
    e1edkp1-defpa             xekpa-defpa
    e1edkp1-ekorg             xekpa-ekorg
    e1edkp1-lifn2             xekpa-lifn2
    e1edkp1-ltsnr             xekpa-ltsnr
    e1edkp1-parvw             xekpa-parvw
    e1edkp1-werks             xekpa-werks
    e1edkt1-tdid              xt166a_del-tdid
    e1edkt1-tdid              xt166k_del-tdid
    e1edkt1-tsspras           ekko-spras
    e1edp01-abftz             ekpo-abftz
    e1edp01-antlf             xvbap-antlf
    e1edp01-bmng2             ekpo-ktmng
    e1edp01-bmng2             ekpo-menge
    e1edp01-bpumn             ekpo-bpumn
    e1edp01-bpumz             ekpo-bpumz
    e1edp01-brgew             e1edp01-menge*ekpo-brgew
    e1edp01-evers             ekpo-evers
    e1edp01-gewei             ekpo-gewei
    e1edp01-kzabs             ekpo-kzabs
    e1edp01-lgort             ekpo-lgort
    e1edp01-matkl             ekpo-matkl
    e1edp01-matnr             ekpo-matnr
    e1edp01-menee             ekpo-meins
    e1edp01-menge             ekpo-ktmng
    e1edp01-menge             ekpo-menge
    e1edp01-netwr             ekpo-netwr*cur_factor
    e1edp01-ntgew             e1edp01-menge*ekpo-ntgew
    e1edp01-peinh             ekpo-peinh
    e1edp01-pmene             ekpo-bprme
    e1edp01-posex             ekpo-ebelp
    e1edp01-posguid           xvbap-posguid
    e1edp01-pstyp             ekpo-pstyp
    e1edp01-uepos             ekpo-uebpo
    e1edp01-vprei             ekpo-netpr*cur_factor
    e1edp01-werks             ekpo-werks
    e1edp02-belnr             ekpo-aktnr
    e1edp02-belnr             ekpo-konnr
    e1edp02-belnr             ekpo-labnr
    e1edp02-belnr             h_xvbkd-bstkd_e
    e1edp02-belnr             xvbap-werks_ext
    e1edp02-belnr             xvbkd-bstkd_e
    e1edp02-bsark             h_xvbkd-bsark_e
    e1edp02-bsark             xvbkd-bsark_e
    e1edp02-ihrez             h_xvbkd-ihrez_e
    e1edp02-ihrez             xvbkd-ihrez_e
    e1edp02-zeile             ekpo-ktpnr
    e1edp02-zeile             h_xvbkd-posex_e
    e1edp02-zeile             xvbkd-posex_e
    e1edp03-datum             ekpo-abdat
    e1edp03-datum             ekpo-agdat
    e1edp17-lkond             ekpo-inco1
    e1edp17-lkond             xvbkd-inco1
    e1edp17-lktext            ekpo-inco2
    e1edp17-lktext            xvbkd-inco2
    e1edp19-idtnr             ekpo-ematn
    e1edp19-idtnr             ekpo-idnlf
    e1edp19-idtnr             ekpo-matnr
    e1edp19-ktext             ekpo-txz01
    e1edp20-ameng             xeket-ameng
    e1edp20-ameng             xeket-wemng
    e1edp20-edatu             xeket-eindt
    e1edp20-ezeit             xeket-uzeit
    e1edp20-wmeng             xeket-menge
    e1edpa1-partn             ekpo-kunnr
    e1edpa1-partn             xvbpa_we-kunnr
    e1edpd1-bednr             xekpo-bednr
    e1edpd1-bstae             xekpo-bstae
    e1edpd1-insmk             xekpo-insmk
    e1edpd1-knttp             xekpo-knttp
    e1edpd1-kzabs             xekpo-kzabs
    e1edpd1-labnr             xekpo-labnr
    e1edpd1-lgort             xekpo-lgort
    e1edpd1-mahn1             xekpo-mahn1
    e1edpd1-mahn2             xekpo-mahn2
    e1edpd1-mahn3             xekpo-mahn3
    e1edpd1-mwskz             xekpo-mwskz
    e1edpd1-prsdr             xekpo-prsdr
    e1edpd1-schpr             xekpo-schpr
    e1edpd1-spinf             xekpo-spinf
    e1edpd1-uebtk             xekpo-uebtk
    e1edpd1-uebto             xekpo-uebto
    e1edpd1-untto             xekpo-untto
    e1edpd1-webre             xekpo-webre
    e1edpd1-werks             xekpo-werks
    e1edpt1-tdid              xt166p_del-tdid
    e1edpt1-tsspras           ekko-spras
    e1eds01-summe             ekko-ktwrt*cur_factor
    e1eds01-summe             pekko-netwr*cur_factor
    e1eds01-sunit             iso_waers
    Whenever you have qualifiers, the segments appear multiple with diefferent fields.
    Regards,
    Clemens

  • Reg: IDOC Schema

    Hi Guys,
    My Basis team imported the MATMAS03 IDOC.
    When trying to access that IDOC in my mapping, it is showing that IDOC schema doesnot exist.
    my R/3 version is 4.5.
    Can any one guess what should be the problem.
    Thanks,
    M.S

    Were the changes activated after importing the idoc....
    Please check your Change List......
    BR,
    Sushil.

  • Reg: IDOC Status Info Report

    Hi Experts
    I am trying to posting the products/internal orders data via IDOC/ALE.
    After the Data loaded into the target system,I required to display the below info:
    Initial Data Load Results Report Layout:
    Totals
    Total number of records read:
    Total number of records processed:
    Total number of internal orders created
    Total number of records in error
    Records Created
    Material XXXXXX created
    Extended to Plant 9999
    Extended to sales organization 9999
    Characteristic xxxxxxxxxxxxxx created
    Records in error
    Line 12 Plant 9999 does not exist
    Line 13 Sales organization 9999 does not exist
    My concern here is as we were loading the data from source to target here via IDOC/ALE.So once the Idoc processed , control won't comes to the developer's view .Then how I can able to publish the above info?
    As I am new to ALE/IDOCS can someone throw some light on this.
    Thanks for your cooperation in advance.
    Regards,
    Sreeram Kumar.Madisetty

    Hi
    So finally you want log of updated records rite ?
    Are you Using FM or stand alone program to process the IDOC ?
    Standard IDOC or Custom ?
    Inbound or outbound ?
    For inbound if you are using standard Fm  find exit for that Fm and in that  u can develope the code like in report .
    Finally count the number of records updated .
    You are getting some errors records so pass the all error recors into internal table and count the records in that internal table ..
    or
    IF you are using custom fm u can directly code the requiremtn in Fm like validations .
    if you are not clear  please revert back and mention ur  IDOC and processing Fm so that i can help you more ..

Maybe you are looking for

  • First 4 Days: Life With New MacBook Pro Retina (Business Use)

    Wrote a co-worker my early impressions of the new machine a couple of days ago. This is a bit updated. - We are a global organization in 62 countries, so this is written from and for our needs.  The co-worker  does major video work, but I have no ide

  • Is there any other way to  limit the data a user can see

    We are using Discoverer 10.2.xxx We are running it against an Oracle applications database but we do not have Discoverer integrated with the apps. I have created database users for discoverer and granted access to the data at the db level. We have ab

  • N80 Screen Broke plz help

    rite was watching a video on me fone and all of a sudden it apeared to switch off, the screen went black when it lit up again the LCD screen had cracked. I hope u no wat i mean the black liquid crystals sprayed uot up the middle of the screen. Will N

  • Computer crashes after cd is burned

    I have iTunes installed on my Windows XP computer. For some odd reason when I burn a playlist to a disc, my computer will come up with a blue screen soon afterwards telling me that Windows had an error and that a physical memory dump was beginning. I

  • Help reqd on no ranges issue for SD

    Hi experts, After i have loaded my customer master datas(xd01) thru lsmw,im facing a problem in the current number ranges issue...i've uploaded of 1000 records of no range started from 10000 to 11000...but in XDN1(tcode)...it shows the current number