About an Idoc

Hello,
       Could you give me clarity whe ever we are sending the Idoc at sender system to reciever system, how can we identify the DT and MT and MI for this as sender system. Because we dont create it.
Thank you

Hi,
When u do message mapping u directly use the IDOC strucutre. so no need to define the DT,MT,MI for IDOC.
For IDOC interface we have to perfom certain configuration on R3 as well as on XI side.
configuration like:
RFC destination which points to XI if ur scenario is R3 to XI.
port
reverse case XI to R3.
RFC destination pointing to R3
port using IDX1 tcode.
just refer the below link which will give u more idea.
ALE configuration for pushing idocs from SAP to XI
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
IDOC testing using WE19
/people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi
File To IDOC - Part1 (SLD and Design):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
File To IDOC - Part2 (Configuration):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
File To IDOC - Part3 (Steps required in XI and R3):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
chirag

Similar Messages

  • Integration strategies - Questions about using IDOC XML?

    Hello. First time poster here.  I am looking for some information for a project for a client and I am hoping someone can give me a pointer to where to start.
    I need to connect my clients SAP system to an XML based software package.  I have heard about IDOC XML and I hope I can use this technology to do the following:
    1. Extract PO's from SAP
    2. Insert PO changes to SAP (Price, Delivery, Quantity, etc.)
    3. Extract RFQ information from SAP
    4. Insert vendor quotations for those RFQ's
    Are there existing IDOC XML document types for these transactions?
    Does SAP have a tool that generates the IDOC XML and makes the data available as a disk file?
    Does SAP have a tool that can read an IDOC XML from a disk file and submit it for insertion into SAP?
    Would I need to do any programming on the SAP side to accept the data into SAP or are there, for instance, specific IDOC XML documents for uploading changes to existing PO's?
    Is there documentation avaialble that will answer these kinds of questions?
    Thank you in advance
    David Kuehner

    >
    dkuehner wrote:
    > Hello. First time poster here.  I am looking for some information for a project for a client and I am hoping someone can give me a pointer to where to start.
    >
    > I need to connect my clients SAP system to an XML based software package.  I have heard about IDOC XML and I hope I can use this technology to do the following:
    >
    > 1. Extract PO's from SAP
    > 2. Insert PO changes to SAP (Price, Delivery, Quantity, etc.)
    > 3. Extract RFQ information from SAP
    > 4. Insert vendor quotations for those RFQ's
    >
    > Are there existing IDOC XML document types for these transactions?
    > Does SAP have a tool that generates the IDOC XML and makes the data available as a disk file?
    > Does SAP have a tool that can read an IDOC XML from a disk file and submit it for insertion into SAP?
    > Would I need to do any programming on the SAP side to accept the data into SAP or are there, for instance, specific IDOC XML documents for uploading changes to existing PO's?
    >
    > Is there documentation avaialble that will answer these kinds of questions?
    >
    > Thank you in advance
    >
    > David Kuehner
    You can use XML port for IDOC xml output to file disk or XML-HTTP port to send and receive message through HTTP protocol.
    Search for SAP Help ALE

  • About sending idoc

    hi,
    How to send control data with doing any mapping functionality?
    How can i send header data of an i doc to sap sys without mapping ?
    pls give full details on this.
    ravi

    *Like Mahesh said about the ale settings u need to do the  following  ....
    To Configure the IDOC SCENARIOS ,PROCEED AS FOLLOWS
    STEP 1:ALE SETTINGS TO POST IDOC INTO SAP R/3
    We need to do the following settings in XI
    1)   Create an RFC Destination to the Receiving System in transaction code (SM59)
    a)   Choose create
    b)   Specify the name of the RFC destination
    c)   Select connection type as 3 and save
    d)   In the technical settings tab enter the details SAP SID/URL and system number#
    e)   Enter the Gateway host as same details above SID/URL
    f)   Gateway service is 3300+system number#
    g)   In the Logon /Security tab, enter the client, user & Password details of Destination system
    h) Test the connection and remote logon.Both should be succesful
    2) Create Port Using Transaction Code  IDX1
    a)   Select Create New button
    b)   Enter the port name as SAP+SID (The starting char should be SAP)
    c)   Enter the destination client
    d)   Enter the RFC Destination created in XI towards R/3
    e)   Save
    3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
    a)  Create new
    b)  IDOC Message Type
    c)  Enter port created in IDX1
                        SETTINGS IN SAP R/3
         We need to do the following settings in R/3
         Logon to Sap R/3 System
    1)   Create an RFC Destination to XI in transaction code  (SM59)
    a)   Choose create
    b)   Specify the name of the RFC destination
    c)   Select connection type as 3 and save
    d)   In the technical settings tab enter the details SAP SID/URL and system number#
    e)   Enter the Gateway host as same details above SID/URL
    f)   Gateway service is 3300+system number#
    g)   In the Logon /Security tab, enter the client, user & Password details of Destination system
    h)   Test the connection and remote logon.Both must be succesful
    2)   Create communication Port for Idoc processing Using Transaction(We21)
    a)   First Select Transactional RFC and then click create button
    b)   Enter the destination port name as SAP+SID (The starting char should be SAP)
    d)   Enter the RFC Destination created in SAP R/3 towards other system.
    e)   Save
    3)   Create Partner Profile with Inbound Parameters (WE20)
    a)   Create New
    b)   Create the Partner no. name as same the logical system name of the destination system
    c)   Select Partner type LS
    d)   Enter details for Type: US/USER, Agent, and Lang
         Then Save
    e)   Select Partner no. and LS which were create above
    f)   Now we have to give some Inbound Parameters.So click on ADD TO Create Inbound Parameter
    g)   Select Message type
    h)   Double click on Message Type and Then Enter the details  for Message Type and Process Code.
    I)   save
    4)   In Transaction SALE, Create Logical System
    a).  Go to Basic Settings-> First Define logical systems
         and then assign logical systems
    b)   Double click on Define the logical systems
    c)   Give data for your Logicaal System and Name
    d)   Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
    e)   Assign the logical system name to the client
    I think these steps will help
    Edited by: Tom  Jose on Jan 22, 2008 9:36 AM

  • About the idoc(DEBMAS) inbound, contact info, need help!

    Hi everyone,
    we have SAP and SIEBEL system, and crate/update customer info(or say account) at SIEBEL first, then send account info to SAP via IDOC, message type is DEBMAS06.
    Now there is a bug. create/update contact info at siebel, it always create new contact at SAP when inbound to SAP system.
    Is there anyone can give me any advice about how to fix this bug?
    Thanks & best regards.

    Hi Sir,
    First thanks very much for your reply.
    I known the MSGFN field, segment E1KNVKM(contact info) has MSGFN field too. but there is a still some issues. I found you must pass the PARNR field to SAP if want to update info(If not, even I set the MSGFN as Deleted or UPDATE, it not works). PARNR is the only key for table KNVK. but you know, PARNR is created at SAP when create this contact info, I need create/update contact at SIEBEL, that's not easy to know what's the value of PARNR will be created.
    Is that possible too pass PARNR value to SAP? I know a little about the SAP BASIS Setting.
    Thanks again.

  • Ergent help about inbound IDoc for Goods Receipts

    Dear friends
    We have an ergent issue needing your help.
    It is about DEVRY03.
    Senarios is as following:
    When we create a delivery by using VL31n, system try the IDoc and transfer to XI.
    This is ok.After external warehouse system processes the IDoc,a message is sent back to SAP to post the goods receipts for the delivery.
    Inbound IDoc type is DEVRY03. Is it right?
    Which function module or which process ok is used for this senario?
    Can anyone suggest how to do it?
    Minghan

    Hi !
    Here comes some information for the INBOUND idocs....
    There is a IDOC for transmitting goods movements from a legacy system.
    It's message-type is: WMMBXY
    IDOC-Type is: WMMBID02 (See we60 for it's pretty good docu....)
    Prcoess-Code is :WMMB
    The function that processes the data is: L_IDOC_INPUT_WMMBXY
    Hope that helped a bit (for inbound)....
    Regards
    Rainer
    Some points would be nice if that helped.

  • About ALE,Idoc, EDI

    sir,
    what is the purpose of ALE,Idoc and EDI, what is the difference and how they will useful for sap
    suggest me

    Hi
    can anyone send me the good links for EDI concepts.explain me a bit about the creation process .
    EDI is described as the interchange of structured data according to agreed message standards between computer systems, by electronic means. Structured data equates to a simple and direct method of presenting the data content of a document. The method of ensuring the correct interpretation of the information by the computer system is defined by the EDI standard."
    EDI is a technique used to communicate business transactions between computer systems of different companies and organizations. Note that sometimes the EDI mechanism deployed at a company is often used to interface to other systems within the same organization."
    www.sapgenie.com/sapedi/edi_sap_training.htm
    www.sap-img.com/basis/ difference-between-edi-and-idoc.htm
    help.sap.com/saphelp_nw04/helpdata/ en/35/26b592afab52b9e10000009b38f974/content.htm
    help.sap.com/saphelp_nw04/helpdata/ en/35/26b594afab52b9e10000009b38f974/content.htm
    http://www.onestopsap.com/interview-Question/edi/
    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
    Links
    IDOC
    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://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    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://www.allsaplinks.com/idoc_sample.html
    IDOCS
    http://www.sappro.com/downloads/OneClientDistribution.pdf
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    ALE/ IDOC
    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://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    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://www.allsaplinks.com/idoc_sample.html
    Have a look at these good links-
    EDI
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    www.sapgenie.com/sapedi/edi_sap_training.htm
    www.sap-img.com/basis/ difference-between-edi-and-idoc.htm
    help.sap.com/saphelp_nw04/helpdata/ en/35/26b592afab52b9e10000009b38f974/content.htm
    help.sap.com/saphelp_nw04/helpdata/ en/35/26b594afab52b9e10000009b38f974/content.htm
    http://www.onestopsap.com/interview-Question/edi/
    http://www.intelligententerprise.com/channels/applications/feature/archive/kasturi2.jhtml
    http://www.sapgenie.com/sapgenie/docs/i830v3020.xls
    http://help.sap.com/saphelp_46c/helpdata/en/0b/2a655d507d11d18ee90000e8366fc2/frameset.htm
    http://www.hud.gov/offices/hsg/comp/edi/0306sec1.cfm
    http://www.sapgenie.com/sapedi/index.htm
    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.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sap-img.com/abap/ale-bapi.htm
    http://www.sap-img.com/basis/difference-between-edi-and-idoc.htm
    http://www.sappro.com/downloads/OneClientDistribution.pdf
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2004/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b828943d711d1893e0000e8323c4f/frameset.htm
    http://www.sapgenie.com/ale/whitepaper.htm
    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
    ALE/ IDOC
    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://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    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://www.allsaplinks.com/idoc_sample.html
    ALE/ IDOC/ XML
    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
    EDI
    EDI interface is used to link/communicate SAP system to some external system. like .NET application. IDOC's are used for communication purpose.
    <u>
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/SDEDI/SDEDI.pdf</u>
    <u>http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf</u>
    ALE/IDOC
    ALE interface is mostly used for communication within different R/3 SAP systems. like you have a distributed environment and you need to share data between two SAP systems then you will use ALE/IDOC technique.
    <u>http://www.sapgenie.com/whitepapers/ale.htm</u>
    http://www.sapgenie.com/ale/index.htm
    http://www.sappoint.com/abap.html
    http://www.sapbrain.com/TUTORIALS/TECHNICAL/ALE_tutorial.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
    check these links.....
    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
    <u>http://www.onestopsap.com/interview-Question/ale/</u>
    http://www.onestopsap.com/interview-Question/edi/
    http://www.allsaplinks.com/idoc_sample.html
    <u>http://www.sap-img.com/abap/ale-bapi.htm</u>
    <u>http://www.sap-img.com/basis/difference-between-edi-and-idoc.htm</u><u><u>http://www.sappro.com/downloads/OneClientDistribution.pdf
    <u></u></u>http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc</u>Please check this link for EDI/ALE/IDoc online documentation.
    <u>
    http://www.easymarketplace.de/online-pdfs.php</u>
    Thanks
    Mohan
    Award points if it adds information.

  • Problem about extended IDOC(urgent)

    Hi experts,
    i have idoctype,extended idoc,and one include.. i need modify that according to the requirement.. here i will give the idoctype and extended idoc type and include program .. please help me where exactly i need to do the change and what are the steps required for the requirement..
    Exact Requirement: Modify the program which populates the idoctype invoice02 and extension zinvoice02 , if netvalue is zero(vbrp-netwr = 0) then populate the idoc segment E1EDP01.E1EDP26 , BETRG WITH QUALF = # 011' WITH ZERO VALUE. curently segment is not populated.
    Please help me in this and explain the steps required for this.
    idoctype:invoice02
    extended idoc:zinvoice02
    include:ZXEDFU02
                                   Here i am giving the include program
    CASE dobject-kschl.
      WHEN 'ZGRI' OR 'ZGDF' OR 'ZGRN' OR 'ZGAE'.
        t_int_edidd[] = int_edidd[].
        t_xtvbdpr[] = xtvbdpr[].
        ta_xvbdkr = xvbdkr.
        CASE int_edidd-segnam.
          WHEN 'E1EDK01'.
            ta_e1edk01 = int_edidd-sdata.
            PERFORM get_shipment_data.
            PERFORM get_route_data.
            int_edidd[] = t_int_edidd[].
          WHEN 'E1EDP01'.
    Update segment E1EDP01
    1. Update field E1EDP01-PSTYP
    2. Accumulated net weight & quantity of batch split items against
    E1EDP01 segment of the main invoice item.
            ta_e1edp01 = int_edidd-sdata.
            i_tabix = sy-tabix.
            CLEAR: ta_e1edp02.                                  "DIAG01+
            PERFORM update_segment_e1edp01.
            MOVE ta_e1edp01 TO t_int_edidd-sdata.
            MODIFY t_int_edidd INDEX i_tabix TRANSPORTING sdata.
    Populate segment Z1EDP08
    Fields: ZZDESPACTY_A, ZZACTYUOM
            PERFORM validate_segment USING control_record_out-idoctp
                                      control_record_out-cimtyp
                                      'Z1EDP08'
                                CHANGING n_subrc.
            CHECK n_subrc EQ 0.
            PERFORM calc_invoice_item_zzdespacty_a.             "DIAG02+
            int_edidd[] = t_int_edidd[].                        "DIAG02+
          WHEN 'E1EDP02'.                                       "DIAG01+
            IF int_edidd-sdata(3) = '016'.                      "DIAG01+
              ta_e1edp02 = int_edidd-sdata.                     "DIAG01+
            ENDIF.                                              "DIAG01+
          WHEN 'E1EDP19'.
    Populate segment Z1EDL24
    Fields: Material Characteristics or Material Class '001'.
            PERFORM validate_segment USING control_record_out-idoctp
                                     control_record_out-cimtyp
                                     'Z1EDL24'
                                     CHANGING n_subrc.
            IF n_subrc EQ 0.
              ta_e1edp19 = int_edidd-sdata.
              CASE ta_e1edp19-qualf.
                WHEN '002'.
                  PERFORM get_mat_characteristic USING ta_e1edp19-idtnr.
                  PERFORM fill_segment_z1edl24.
                  int_edidd[] = t_int_edidd[].
                WHEN OTHERS.
              ENDCASE.
            ENDIF.
          WHEN 'E1EDP26'.
    Populate segment E1EDP26
    Fields: BETRG
            i_tabix = sy-tabix.
            ta_e1edp26 = int_edidd-sdata.
           IF ta_e1edp26-qualf = '001'. "Gross Price which is always present
              PERFORM fill_segment_e1edp26.
              int_edidd[] = t_int_edidd[].
            ENDIF.
          WHEN 'E1EDP08'.
    Populate Segment Z1EDL37                                             *
    Fields: Bespoke fields from Handling Unit (VEKP)
            PERFORM validate_segment USING control_record_out-idoctp
                                      control_record_out-cimtyp
                                      'Z1EDL37'
                                CHANGING n_subrc.
            CHECK n_subrc EQ 0.
            ta_e1edp08 = int_edidd-sdata.
            PERFORM fill_segment_z1edl37.
    Populate Segment Z1EDP08                                             *
    Fields: Total Despatch Activity                                      *
           PERFORM validate_segment USING control_record_out-idoctp
                                     control_record_out-cimtyp
                                     'Z1EDP08'
                               CHANGING n_subrc.
           CHECK n_subrc EQ 0.
           PERFORM calc_invoice_item_acty_total.
            int_edidd[] = t_int_edidd[].
          WHEN OTHERS.
        ENDCASE.
      WHEN 'ZGDW'.
    Line above added line below removed - Assyst 73789
    WHEN 'ZGIN'.
        t_int_edidd[] = int_edidd[].
        t_xtvbdpr[] = xtvbdpr[].
        ta_xvbdkr = xvbdkr.
        CASE int_edidd-segnam.
    Start SU02
          WHEN 'E1EDK01'.
            ta_e1edk01 = int_edidd-sdata.
            i_tabix = sy-tabix.
    Get the conversion factor
            PERFORM modify_exchange_rate.
            MOVE ta_e1edk01 TO t_int_edidd-sdata.
            MODIFY t_int_edidd INDEX i_tabix TRANSPORTING sdata.
            int_edidd[] = t_int_edidd[].
    End SU02
    *************************************************************SAM01 START
          WHEN 'E1EDP02'.
    Populate segment Z1EDP02
    Fields: Reason code for sales order
            ta_e1edp02 = int_edidd-sdata.
            CASE ta_e1edp02-qualf.
              WHEN '002'.
                PERFORM fill_segment_z1edp02.
                PERFORM append_int_edidd TABLES t_int_edidd
                                         USING  'Z1EDP02'
                                                ta_z1edp02.
                int_edidd[] = t_int_edidd[].
              WHEN OTHERS.
            ENDCASE.
    ***************************************************************SAM01 END
        ENDCASE.
    Start of JvdM01
      WHEN 'ZGII'.                                              "JvdM01
        t_int_edidd[] = int_edidd[].
        t_xtvbdpr[] = xtvbdpr[].
        ta_xvbdkr = xvbdkr.
        CASE int_edidd-segnam.
          WHEN 'E1EDK01'.
    Populate segment Z1EDKSH and Z1REM_STE_CDE
    Fields: Shipment Number for Invoice
            Reason code for sales order
            ta_e1edk01 = int_edidd-sdata.
            PERFORM fill_segment_z1edksh_ds.
            PERFORM append_int_edidd TABLES t_int_edidd
                                     USING 'Z1EDKSH'
                                            ta_z1edksh.
            PERFORM fill_segment_z1rem_ste_cde.
            PERFORM append_int_edidd TABLES t_int_edidd
                                     USING  'Z1REM_STE_CDE'
                                            ta_z1rem_ste_cde.
            int_edidd[] = t_int_edidd[].
          WHEN 'E1EDKA1'.
    Populate segment Z1EDKA1
    Fields: Customer Account Group
            ta_e1edka1 = int_edidd-sdata.
            CASE ta_e1edka1-parvw.
              WHEN 'RE'.   "Bill To Party
                PERFORM fill_segment_z1edka1.
                PERFORM append_int_edidd TABLES t_int_edidd
                                         USING 'Z1EDKA1'
                                                ta_Z1EDKA1.
                int_edidd[] = t_int_edidd[].
            ENDCASE.
          WHEN 'E1EDP01'.
    Read segment E1EDP01 for use later                  "JVDM02
            ta_e1edp01 = int_edidd-sdata.
          WHEN 'E1EDP02'.
    Populate segment Z1EDP02
    Fields: Reason code for sales order
            ta_e1edp02 = int_edidd-sdata.
            CASE ta_e1edp02-qualf.
              WHEN '002'.
                PERFORM fill_segment_z1edp02.
                PERFORM append_int_edidd TABLES t_int_edidd
                                         USING  'Z1EDP02'
                                                ta_z1edp02.
                int_edidd[] = t_int_edidd[].
              WHEN OTHERS.
            ENDCASE.
          WHEN 'E1EDP19'.
    Populate segment Z1EDL24 and Z1EDP01                  "JVDM02
    Fields: Pack Size Activity for Material
            Total Activity for Invoice Item
            ta_e1edp19 = int_edidd-sdata.
            CASE ta_e1edp19-qualf.
              WHEN '002'.
                PERFORM fill_segm_z1edl24_and_z1edp01.
                PERFORM append_int_edidd TABLES t_int_edidd
                                         USING  'Z1EDL24'
                                                ta_z1edl24.
                PERFORM append_int_edidd TABLES t_int_edidd
                                         USING  'Z1EDP01'
                                                ta_z1edp01.
                int_edidd[] = t_int_edidd[].
              WHEN OTHERS.
            ENDCASE.
        ENDCASE.
    End JvdM01
    ENDCASE.
    Start SU02 Code Comment for implementing IR 340
    **mpc01 - start of insert
    start assyst 73789
    *IF dobject-kschl = 'ZGDW'."amersham invoices
    **IF dobject-kschl = 'ZGIN'."amersham invoices
    end assyst 73789
    CASE int_edidd-segnam.
      for the organisation data header
       WHEN 'E1EDK14'.
         MOVE int_edidd-sdata TO ta_e2edk14.
        where is qualifying organisation = 003 (delivering company code).
         IF ta_e2edk14-qualf = '003' AND ta_e2edk14-orgid NE space.
           SELECT SINGLE waers
             INTO t001-waers
             FROM t001
            WHERE bukrs = ta_e2edk14-orgid.
           IF sy-subrc = 0.
             t_int_edidd[] = int_edidd[].
            get the billing date for the invoice
             LOOP AT t_int_edidd WHERE segnam = 'E1EDK02'.
               MOVE t_int_edidd-sdata TO ta_e1edk02.
               IF ta_e1edk02-qualf = '009'."billing date
                 w_fkdat = ta_e1edk02-datum.
                 EXIT.
               ENDIF.
             ENDLOOP.
            if no invoice date use current date
             IF w_fkdat IS INITIAL.
               w_fkdat = sy-datum.
             ENDIF.
            change the general document header
             LOOP AT t_int_edidd WHERE segnam = 'E1EDK01'.
               i_tabix = sy-tabix.
               MOVE t_int_edidd-sdata TO ta_e1edk01.
              set the field to the default currency code for the company
               ta_e1edk01-hwaer = t001-waers.
              if the default value equals the idoc currency then exit
               IF t001-waers = ta_e1edk01-curcy.
                 EXIT.
               ENDIF.
              get the exchange rates
               SELECT *
                 INTO TABLE t_tcurr
                 FROM tcurr
                WHERE kurst = 'NYB1'                 " SU01
                 WHERE KURST = 'GEBU'                 " SU01
                  AND fcurr = ta_e1edk01-curcy
                  AND tcurr = t001-waers.
               IF sy-subrc NE 0."no values found
                error the idoc
                 MESSAGE e400(vf) WITH c_exchange_rate_error
                         RAISING error_message_received.
                 EXIT.
               ENDIF.
               LOOP AT t_tcurr.
                convert to date from inverted date to normal date format.
                 CALL FUNCTION 'CONVERSION_EXIT_INVDT_OUTPUT'
                      EXPORTING
                           input  = t_tcurr-gdatu
                      IMPORTING
                           output = w_datum.
                 CONCATENATE w_datum+6(4)
                             w_datum+3(2)
                             w_datum(2)
                        INTO t_tcurr-datum.
                 MODIFY t_tcurr.
               ENDLOOP.
              sort the exchange rates with the newest first.
               SORT t_tcurr BY datum DESCENDING.
              read the first value in the table ie the newest.
               LOOP AT t_tcurr WHERE datum <= w_fkdat.
                 EXIT.
               ENDLOOP.
               IF sy-subrc NE 0."no values found
                error the idoc
                 MESSAGE e400(vf) WITH c_exchange_rate_error
                         RAISING error_message_received.
                 EXIT.
               ENDIF.
    Start SU01
    Get the Exchange rate from the function module and populate
    E1EDK01 TABLE
               w_fcurr = ta_e1edk01-curcy.
               call function 'CONVERT_TO_LOCAL_CURRENCY'
                    exporting
                         date             = w_fkdat
                         foreign_amount   = '0'
                         foreign_currency = w_fcurr
                         local_currency   = t001-waers
                         type_of_rate     = 'GEBU'
                    importing
                         exchange_rate    = t_tcurr-ukurs
                    exceptions
                         no_rate_found    = 1
                         overflow         = 2
                         no_factors_found = 3
                         no_spread_found  = 4
                         derived_2_times  = 5
                         others           = 6.
    End SU01
               ta_e1edk01-wkurs = t_tcurr-ukurs.
              change the header data in segment
               MOVE ta_e1edk01 TO t_int_edidd-sdata.
              update the current idoc segment
               MODIFY t_int_edidd INDEX i_tabix TRANSPORTING sdata.
               EXIT.
             ENDLOOP.
            update all of the idoc segments
             int_edidd[] = t_int_edidd[].
           ENDIF.
         ENDIF.
    ENDCASE.
    *ENDIF.
    **mpc01 - end of insert
    End SU02 Code Comment for implementing IR 340

    Hi Venu,
      Try with this code.
      If vbrp-netwr = 0.
    <b>  WHEN 'E1EDP26.
      CASE ta_e1edp26-qualf.
    ta_e1edp26 = int_edidd-sdata.
    WHEN '011'.
    PERFORM append_int_edidd TABLES t_int_edidd
    USING 'e1edp26'
    ta_e1edp26.
    int_edidd[] = t_int_edidd[].
    ENDCASE.</b>
    ENDIF.
    Thanks
    Manju.

  • About triggering Idocs and RFC methodology

    Created FM to trigger the IDOCu2019S, to the requesting legacy systems, which has triggered this before by the RFC methodology
    from above question exactly can u tell what is process going on over there.
    what is RFC methodology,how can we create RFC function module.how it will trigger  idocs
    pls explain this, i am totally confused regarding this

    You are right we use RBDAPP01 for inbound processing. To process IDOCs that haven't been sent and are waiting as tRFCs in SM58, we use program RSARFCEX. You can also schedule this job periodically to send any waiting IDOCs. See note 161527 for information on running the program as a batch job.
    As for monitoring for waiting IDOCs, you can use CCMS monitoring. There is already a monitor for IDOC monitoring. Do the following to get to the monitor.
    1. Go to tcode RZ20.
    2. Expand node "SAP CCMS Monitors for Optional Components"
    3. Open monitor set "ALE/EDI" by double clicking on it.
    4. You will see client specific nodes. Expand the client you are interested in.
    5. Expand node "SAP: All/ 1 hour waited"
    6. Expand node "tRFC Queue SAP: All/ 1 hour waited"
    Also node "Outbound IDoc SAP: All/ 1 hour waited" has usefull monitoring attributes.
    If CCMS has already been configured for sending alerts, you can have alerts sent if the number of waiting IDOCs exceeds a certain value. To configure this choose the a node and click on the properties button.
    Please award points if helpful.
    Tarkesh

  • About Importing IDOC.

    Hi Guy's,
                         When we are Importing IDOC from SAP side after adding a extra field to IDOC, Its not visible at XI side aftr Import. How we  wil  find that Field ?

    Hi kumar chaluvadi 
    if you want to add more fields in your idoc then you have to go for the idoc enhancement.
    steps for the iodc enhancement
    1. create the segment using the transactionwe31
    2. create the enhanced idoc type using the transaction we30
    3. link the msg type and the idoc type using the transaction we82.
    if you still need clarification please reply me back.
    Thanks
    Rinku

  • About the idocs

    hi,
          i need the  standard idocs with the relation between employee data and org. data? and message type also,.

    thanks for ur answer? for the message type but i need the basic type and idoc type can u provide it?
    or
    with the help of  message type how to see the  basic type ?

  • About ale/idocs

    hello experts..
    1..can u tell me what is idoc tables..
    2.. ale what is message functions..what is functionalty of message functions..
      and where u can find message function and tell me which tr.code

    Hi,
    The message function is an optional parameter. If several IDoc types belong to the same message type, the unique assignments can be ensured via the message code and message function. Alternatively, the inbound processing type for IDocs from a certain partner can be defined differently via the fields for message type, message code and message function.
    You can specify the message function when you create an inbound or an outbound partner profile (WE20). The table is EDIDC and field is MESFCT.
    Regards,
    Ferry Lianto

  • About ALE/IDOC

    1. could anybody please send me the ALE/IDOC real time scenario pr technical spec(on which u had an experience)  to my mail
    ID: [email protected]
    or
    could u provide ur 'contact number' so that i could give a call to u .
    please help me na.

    Hi,
    Few examples of real time scenarios are
    1. Outputting Purchase Orders as IDOCs on saving the PO
    2. Outputting Inbound Delivery on receipt of ASNs
    3. Processing Goods Receipt from a third party system
    For this You need to Activate the Change Pointer through IMG SALE...for the repective MESSAGE TYPE say Material Master MATMAS
    After That creat Material (MM01)
    After that go to SE38 Run the Report programm RBDCPMIG to created Master IDOC and Communication IDOC...And if All Your ALE Settings are correct .. it will transfer the IDOC to Other Client....or R/3
    YOu can also try
    Creation of purchase Order what has been explained in above reply..
    You can also try out this scenario instructed in this Quick refrance Guide.....
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
    You can also check out this very useful link for newbie
    http://www.allsaplinks.com/idoc_sample.html
    ALE/ IDOC
    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://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    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://www.allsaplinks.com/idoc_sample.html

  • Question about ALE/IDoc

    I try to generate partner profile with transaction BD82.I input the model view name,partner system and execute. It says No message have been defined for the selection conditions in the model.So what is the problem.And how to handle it.
    Thanks.

    Hi Alex,
    Just make sure you have given the name of sender, receiver system and message type correctly and you have maintained this data in tcode - BD64.
    check this blog as well..
    ALE configuration for pushing idocs from SAP to XI
    You can use we20 to maintain partner profile as well.
    Regards,
    Sachin

  • About accessing IDoc structure

    Hi Experts,
    I'm creating a SHPMNT04-IDoc for deliveries. For each position in the delivery, I want to modify the position no. (E1EDL24-POSNR) when the position type (E1EDL26-PSTYV) is eq "ZHUM".
    I 'm editing a segment like this:
    DESCRIBE TABLE idoc_data  LINES lc_va_line.
    READ TABLE idoc_data      INDEX lc_va_line.
    MOVE idoc_data-sdata      TO lc_wa_e1edl24.
    MOVE lc_wa_e1edl24        TO idoc_data-sdata.
    MODIFY idoc_data          INDEX lc_va_line.
    CLEAR idoc_data.
    ... but how can I test a value in the substructure E1EDL26 and modify a value in the upper-structure E1EDL24 ?
    Thanks a lot for support.
    Regards,
    David.

    Hi guys,
    thank you for your answers.
    @ Alexander :
    I used your coding like this:
    IF segment_name EQ 'E1EDL24'.
            DESCRIBE TABLE idoc_data  LINES lc_va_line.
            READ TABLE idoc_data      INDEX lc_va_line.
            MOVE idoc_data-sdata       TO    lc_wa_e1edl24.
            READ TABLE      idoc_data WITH  KEY segnam = 'E1EDL26'.
            IF sy-subrc = 0.
              MOVE idoc_data-sdata TO       lc_wa_e1edl26.
              IF lc_wa_e1edl26-pstyv =      'ZHUM'.
                 lc_wa_e1edl24-posnr = lc_wa_e1edl24-posnr + 9010.
              ENDIF.
            ENDIF.
            MOVE lc_wa_e1edl24    TO    idoc_data-sdata.
            MODIFY idoc_data          INDEX lc_va_line.
            CLEAR idoc_data.
          ENDIF.
    ... I think there is a problem when I update de internal table "idoc_data" with "MOVE lc_wa_e1edl24    TO    idoc_data-sdata" because after reading the E1EDL26 segment, I've got another index. What do you think ?
    Regards,
    David

  • About an IDoc Error, who help me  solve it?

    Hi, all
    Some credit orders come into sap from external system.The docs for these orders appear complete, but the orders are lack of target quantity values in line items > 10(except the first item). Configure info as below:
    Message Type: orders
    Basic Type: orders04
    extension: zorders9
    why? Look forward to your reply and any tips.whick abap program should i track for testing?
    Best wishes.
    -Daniel

    Hi, my friend:
    List the materials in the sales order
    Item    Material                         Order quanity     Description
    10      23703-301452-9700                 2               CIV3D 2006 KJ CDSL EDU
    20      23703-301452-9F00A              0                FG:CIVIL 3D 2006 KJ CDSL
    30      23703-301452-9F00B              0               3D 2006 KJ CDSofe
    According to the below table, you will find the values are 0 when item > 10.
    Only first recode  is imported sucessfully, others are incorrect.
    Thank you for everything.

Maybe you are looking for