EDI - IDOC  mapping question

Dear Experts,
For transformations between EDI and basic IDOC types, are there any off-the shelf  (ready to use) options? If yes what are they? If not, what is the easiest way of mapping in between these structures?
Our setup involves Seeburger's AS2 adapter.
Thanks

Hi Aamir,
Thank you for your response.
We are working in an environment where we do not have any control over the setup. So I have a few follow up questions, answers to which would help me immensely.
1. I saw that there are a"few" mappings available for which both the EDI and IDOC versions differ from what we need. So, is there anyway to get an actual listing of all supplied mappings?
2. In case you have worked for a similar scenario, is it possible for you to share a sample mapping spreadsheet ?
Thank you,
N

Similar Messages

  • EDI IDOC mapping design

    Hi all,
    I was supposed to program a report to generate IDOCs. The EDI file format was given.
    The segments in the IDOCs should be in the sequence of A, B, C. How can I map them into the sequence of B, C, A?
    Is it mapped by the external software?
    Thanks

    IDoc-to-EDI mapping is usually handled by external software such as Sterling Commerce Gentran or GXS Application Integrator. Check with your company EDI folks they should churn this work in no time for you.

  • EDI Idoc Mapping  For Apparel and footwear Solutions (AFS)

    Hello Gurus
    I am trying to map Orders sent thru EDI using message type Orders and Idoc type /AFS/ORDERS06 and process code J3AA.
    I am running into problems like no item category could be found and other errors which stops me proceeding further. I have worked with after market EDI and when I use message Orders and Orders 05 Idoc. I do not run inot these issues.
    Is there any specific doumentationavailable for processing AFS EDI?. Any help would be appreciated and points will be awarded.
    Thanks a lot for your help in advance.
    Sunny

    hi,
    If you want to make huge volume of updation then you should go for idoc.
    otherwise you go for Bapi call from xi or RFC.
    regards,
    ujjwal kumar

  • IDoc Mapping Question

    Hello all,
    i have the mapping of an iDoc relevant to Inbound deliveries (Inbound Delivery for Purchase order).
    in the mapping i see /E1EDK08/E1EDP07/E1EDP09/VRKME for 'unit of measure' or /E1EDK08/E1EDP07/BSTNK for 'PO Number this shipment links to'.
    What I dont understand is how 2 segments can be relevant to one field i.e. VRKME.
    In other mappings i.e. /E1EDP01/NETWR for P.O line item value in P.O creation iDoc is very clear.
    I would be greatful if someone could explain the other cases
    Thanks

    Hi Ioannis,
    the mapping represents the hierarchical structure of the IDOC: E1EDK08 header segment may have one or more E1EDP07 item segments with one or more E1EDP09 subsegments.
    Where di you find those mappings? (never saw it in that way)
    Regards,
    Clemens

  • SAP R/3 Mapping with EDI IDOC's 846 and 852 (Outbound)

    Hi:
    How are the following EDI IDOC Types mapped in SAP - R/3?
    1. Inventory Inquiry / Advice (846)
    2. Product Activity Data (852)
    What is the basic type, message type, idoc type that has to be used
    in both the cases - outbound based ones.
    This is a consumer products industry and not a retail industry. This
    is a hypothetical scenario where the end customer would like to see
    the price and the stock from all the plants and then place an order
    (846); and also see what is being planned in aparticaular plant for
    a planning period (852). The cycle countings are carried out based
    on the type of product in question and SAP-R/3 has been set up for
    this. What is the trigger point for the enitre activitiy to take
    place. Any valuable suggestions or guidelines are most welcome.
    Regards
    Rohit

    Check this link and see if it leads you somewhere.
    http://sap.ittoolbox.com/groups/technical-functional/sap-interfaces/information-on-the-edi-idoc-types-1739410
    http://www.jt77.com/CRM/related-discussion-1111.html
    Regards,
    Ravi Kanth Talagana

  • IDOC,  EDI (Very basic question)

    Dear All,
    I am very new to EDI/IDOC, 
    where do I change the logic or setting on generating an IDOC.
    I need to change the contents of a PO   IDOC. I saw segments with different fields and content, but where are to logics to populate those?
    Is that a program ? Configurations? Where is it ?
    For example , i want the footer notes of the IDoc to be change, where to change that ?
    Thank you .
    Message was edited by:
            Kokwei Wong

    hi
    good
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/ale/configuration.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapdevelopment.co.uk/training
    And also u can get lots of inof from the below link.
    http://www.sapgenie.com/ale/why_ale.htm
    thanks
    mrutyun^

  • EDI IDOC generation for interface with Vendor software help needed.

    EDI IDOC help needed.
    We are NOT an EDI shop, but have a project to output data to Sales Force.com
    Sales Force requests IDOC output - eg. 810 Outbound Invoice.
    We will need to do a historical load of Orders/Quotes/Invoices from the past 2 years.
    Is there a function module or series of FM's that are used to generate the E2EDKxxxxx type segments?
    I have been testing using the IDOC_OUTPUT_INVOIC and IDOC_OUTPUT_ORDRSP FM's, but they generate segments begining with E1EDKxxxxx.
    Basicall we have a report program that the user enteres in the date range of Order/Quotes/Invoices they wish to extract, the the program needs to output a flat file (.txt) on the server which is then picked up by Sales Force.com.
    Also, is there a way to have in the Partner Profile a generic Partner under the "Type KU" that can be used for all orders/invoices so I don't have to create a KU Partner Type for each and every Sold-To customer we have?
    I am very new to EDI so any help would be greatly appreciated.
    Thanks.
    Scott.

    Hi Scott,
    We will need to do a historical load of Orders/Quotes/Invoices from the past 2 years.
    I know it's very tempting to use an interface for such loads if you anyhow have to create one. However, often the volume alone speaks against interface usage for such scenarios.
    Is there a function module or series of FM's that are used to generate the E2EDKxxxxx type segments? I have been testing using the IDOC_OUTPUT_INVOIC and IDOC_OUTPUT_ORDRSP FM's, but they generate segments begining with E1EDKxxxxx.
    Well, the E2* segments basically reflect the external name of the IDoc segment, whereas the function modules you're referring to basically just create an internal version of the IDoc. Once the IDoc framework then passes the IDocs to the partner, the segment names usually (depends on how the IDocs are passed on) get converted to their external name. If there are multiple versions of a segment, then the version number will be appended to the segment name.
    Note that IDoc segment definitions are only partially stored in the data dictionary. If you want to see all versions you should always use transaction WE31 to look at segments. There you can also see for example for E1EDK01 the several versions and when you then use in SE37 function module SEGMENT_EXTERNAL_NAME_GET you will see what SAP produces as the external name for segment E1EDK01. This function module is basically the one that handles the segment name translations.
    Ignore the comments for subsystem, this is basically an option in SAP to possibly trigger further external tools (e.g. mapping etc.) for handling the outbound IDocs.
    Again, the funny thing is that via the WE30 transaction, if i put in INVOIC02 as the Obj. name and see the segments, i can see that E2EDK01 there is a version 005, but if i go to SE11 and put in E2EDK01005 structure line and i get a "not found". We just have up to E2EDK01002.
    In the old days SAP used to generate E1, E2 and E3* structures in the data dictionary (SE11). The E1* structure reflected the character type representation of an IDoc segment, whereas the other two (definition and documentation) contained actual references to data elements (e.g. if you used a quantity field). However, in newer releases those dictionary structures (E2* & E3*) are no longer generated, because they're superfluous (meta data defined via WE31 is sufficient).
    Cheers, harald

  • EDI/ IDOC

    Gurus
    Can somebody answer my querries
    1. What exactly is gapping and mapping in EDI/IDOC
    2. Can anybody send me the functional specifications and test development  for EDI! Meaning any specs as a functional consultant we provide EDI team for mapping .
    My email ID is [email protected]
    Thanks

    Dear Brendon,
    what you map in IDOC depends on the IDOC message type.
    ORDERS - creation of a sales order
    ORDCHG - change of an existing sales order
    ORDRSP - confirmation/replication of the sales order
    DELINS - creation of a delivery schedule in scheduling agreement
    DELORD - creation of a delivery order to the scheduling agreement
    EDLNOT - creation of an external agent delivery to the scheduling agreement
    GSVERF - creation of a credit advice
    SBINV - creation of the invoice
    SBWAP - creation of debit/credit memo(requests)
    INVOIC - sending the invoice
    In the transaction WE60 you can see the fields to every basic IDOC type. Not all fields which could be mapped via IDOC will be transfered automatically (only some ones). All other fields can be mapped to the application with the help of numerous user-exits provided.
    The most important transactions:
    BD87 - to apply the incoming IDOC
    WE19 - to copy / to edit the IDOC and apply this copy
    WE02 - to display the IDOC
    WE05 - to select IDOCs
    WE60 - to see the declared IDOC fields
    And here is a general information about IDOC concept in SD:
    The EDI concept is intended to realize the sales and distribution process completely automatically with the help of electronical documents. These documents are sent from one customer to another, are processed mostly on the background and give a possibility to realize the sales process extremely efficiently.
    If MM-customer would like to purchase the goods then he creates the IDOC of type ORDERS and send it to SD-customer. On the SD-side the IDOC is processed via the function module IDOC_INPUT_ORDERS and creates the sales order. As confirmation the SD-side can send to MM-side the Order-Response IDOC (function IDOC_OUTPUT_ORDERS). The MM-customer can every thime send a change to the existiong order, then on SD side the ORDCHG IDOC will be processed. It can change the order like in VA02. The creation of the invoice can be made via IDOC of message type INVOIC (function IDOC_OUTPUT_INVOIC).
    So, the process can be realized completely automatically between SD and MM partners with the help of IDOCs: ORDERS, ORDCHG, ORDRSP, INVOIC.
    That's all concerning the SD-EDI.
    Additional processes in SD, where EDI are used:
    1) application of delivery schedules to the scheduling agreement: IDOC of type DELINS
    2) creation of a delivery order to the scheduling agreement: IDOC of type DELORD
    3) creation of external agent service delivery to scheduling agreement: IDOC of type EDLNOT
    4) creation of credit advice / credit memo in the frames of self-billing: IDOCs of type GSVERF, SBWAP and for external invoice creation SBINV.
    It is all processes which are realized in the SD module via EDI.
    There is not so much Customizing for EDI. The most entries are required by EDI for the scheduling agreement processing (DELINS, EDLNOT, SBINV). The Customizing of these processes is located in the Customizing of scheduling agreements: SPRO => Sales and Distribution => Sales => Sales Documents => Scheduling agreements with delivery schedules => Control EDI Inbound processing.
    General EDI Customizing in SD is available under: SPRO => Sales and Distribution => Electronic Data Interchange => EDI messages => ...
    I hope this info helps.
    Kind regards,
    Akmal Vakhidov
    Development Support SAP, Walldorf/Germany

  • IDoc mapping for VMI

    Hello,
    We'd like to store the idoc data extracted from EDI 852 inbound transaction in an infocube for DP. SAP Note 154604 suggests that trx <b>/sapapo/map_tser</b> can be used for specifying the infocube.
    However, in SCM 4.1, this trx has a field for PA only, not infocube. I was wondering how to pull the data into infocube.
    Any suggestions would be appreciated.
    Thank you,
    Malli

    Hello,
         I'm afraid that i can not help you.
          I am witting you because i am trying to get information about VMI/ SMI implementation, for ex. IDOC mapping, best practices, etc.
          I will be appreciate if you can provide me this information.
    Thanks&Rgds
    Angélica

  • Payment throught EDI IDoc to Bank

    Hi,
    I have created a new payment method to pay customer credit through EDI IDoc. I have tested in F110 (APP), document getting cleared and IDoc also getting created. After this I'm not sure what I need to do.
    Kindly tell me the action points with Tcode (if possible). And also please let me know how to make sure the Idocs are reaching the Bank system for payment.
    Thanks
    Inba

    Hi,
    The receiver port of the IDOC can be mapped to bank site.
    You BASIS team should be able to help you to make this connection.
    Regards,
    SDNer

  • EDI Message Mapping Names

    Hi All,
    Can I please have the EDI message mapping names for the following:
    1)Tradacoms versions 8 and 9
    Inbound:Source message type ORDHDR and the target is IDOC structure ORDERS05(Sales Order)
    outbound: Source message Invoic02 Idoc and the target message type INVFIL
    2)EDIFACT D96A:
    Outbound:Source message Invoic02 Idoc and the target message type INVOIC
    3)ENACOM:
    Outbound: For Source message Invoic02 Idoc and the target message type INVOIC
    Your help is much appreciated.
    Cheers,
    Smith

    Hi,
    DO u have BIC installed on ur PC. if u have then u could find out the mapping name for the BIC itself.
    Mapping program name for example:
    See_E2X_ORDERS_D9A is the mapping name for ORDERS message type.
    Chirag

  • What is Ale, Edi,IDoc tech for sap

    Hi all,
    What is Ale, Edi,IDoc tech for sap?
    Thanks.

    hi deniz,
    <b>ALE</b>
    ALE
    Triggering OB via Change Pointers:
          When an application make a changes in any object an entry is made in CDHDR and CDPOS tables. When any change is made the SMD(Shared Master Data) Tool checks that ALE setting and create a change pointer in the BDCP table that will point to CDHDR table. A standard program RBDMIDOC is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process to distribute to the appropriate destinations. The program will read the table TBDME to determine the IDoc selection program it is MASTERIDOC_CREATE_SMD_MATMAS in the case of MATMAS.
    Outbound Process:
    When the stand-alone program or the Transaction(BD10) is run, it calls the Idoc
    Selection program MASTERIDOC_CREATE_REQ_MATCOR in the case of MATMAS, which is hard coded in the program. The Idoc Selection program reads the master data and create a master Idoc and stores it in the memory. The function module then calls ALE layer by using another function module MASTER_IDOC_DISTRIBUTE which is invoked inside it. Then Idoc filtering, Segment filtering etc.. are done in the ALE layer.
         To dispatch the Idoc to the destination system, the system reads the partner profile to determine the destination system. Then the sending system calls the function module INBOUND_IDOC_PROCESS asynchronously on the remote system and passes the Idoc via memory buffer.
    Asynchronous Communication:
    The data  that is IDocs and the function module are  stored in ARFCDATA and ARFCSSTATE tables. The function module ARFC_DEST_SHIP will transports data to target System and the program ARFC_EXCUTE will execute the stored function Module. If communication problem occurs RSARFCSE program is automatically scheduled., if successful, entries in the tables ARFCSSTATE and ARFCDATA will be deleted.
    Inbound Process:
    The INBOUND_IDOC_PROCESS program is triggered as a result of RFC from the Sending System, the Idoc to be sent is passed as parameter for the function module
    In the partner profile if Process immediately is selected then RBDAPP01 program is executed. It will read the process code(MATM) from the Partner profile, which in turn invoke the function module IDOC_INPUT_MATMAS for MATMAS
         Function module will call the corresponding SAP transaction using call transaction or uses direct programs to convert the Idoc to Application document .
    In the table TBD51 there will be entries to find which option is used.
    Transactions:
    SALE - IMG ALE Configuration root
    •     WE20 - Manually maintain partner profiles
    •     BD64 - Maintain customer distribution model
    •     BD71 - Distribute customer distribution model
    •     SM59 - Create RFC Destinations
    •     BDM5 - Consistency check (Transaction scenarios)
    •     BD82 – Generate Partner Profiles
    •     BD61 – Activate Change Pointers - Globally
    •     BD50 – Activate Change Pointer for Msg Type
    •     BD52 – Activate change pointer per change.doc object
    •     BD59 – Allocation object type -> IDOC type
    •     BD56 – Maintain IDOC Segment Filters
    •     BD53 – Reduction of Message Types
    •     BD21 – Select Change Pointer
    •     BD87 – Status Monitor for ALE Messages
    •     SALE – Display ALE Customizing     WEDI - ALE IDoc Administration
    •     WE60 - IDoc documentation
    •     SARA - IDoc archiving (Object type IDOC)
    •     WE47 - IDoc status maintenance
    •     WE07 - IDoc statistics
    BALE - ALE Distribution Administration
    •     WE05 - IDoc overview
    •     BD87 - Inbound IDoc reprocessing
    •     BD88 - Outbound IDoc reprocessing
    •     BDM2 - IDoc Trace
    •     BDM7 - IDoc Audit Analysis
    •     BD21 - Create IDocs from change pointers
    •     SM58 - Schedule RFC Failures
    <b>EDI</b>
    EDI(Electronic Data Interchange )
    RFC DESTINATION:
                           A logical name used to identify the remote system on which a function needs to be executed.
    Partner Profile:
          It defines the characteristics of data being exchanged with the business partner.
    Partner Function:
         Role of the partner Eg:Ship-to-party,bill-to-party,etc in EDI and in ALE legacy system or remote SAP system.
    Partner type:
              The type of your business partner .
         EDI        – KU/LI
         ALE     --  LS.
    Archiving:
         -Need to archive the important transmitted document
    -Created in SARA
         -Assigned in WE20.
    PartnerProfile Tips:
    •     RSECHK07- Consistency check for Partner Profile.
    •     If you want to modify partner profile; copy it and then modify. If you can’t modify it , u have  to delete it.
    •     To move partner profile to production system choose Partner ->  Transport
    Port defintion:
         It defines the medium through which data is exchanged between systems.
    •     tRFC    -   Used by ALE
    •     FILe     -   Used by EDI
    •     R/2 system system port  – For R/2 system
    •     Internet port           - to connect with internet applications
    •     It also depends on the  receiving side. If the receiving subsystem accepts tRFC, EDI also can use tRFC.
    Remote Function modules required by Subsystem to send status and inbound idoc to SAP:
    Startrfc                                         -   Program to execute RFC – enabled Fun.mod. in SAP
    EDI_DATA_INCOMING             -   To send data as inbound
    EDI_STATUS_INCOMING         -   To send status to SAP
    RSPARAM               -   To know the gateway service of the SAP system.
    Message Control:
    •     Output controller
    •     A service program for determining the output type
    •     To generate and manage various outputs from an application and control their medium and timing of exchange.
    •     To retransmit the document without duplicating it
    Procedure:
    •     A procedure defines a set of possible outputs for an application
    •     There may be more than one procedure but only one can be active
    •     Requirement field in procedure specifies the condition which the sales docu. should reach,for sending the sales order response.
    Output type:
    Defines the characteristics and attributes of the output.
    Access Sequence :
    Defines  a sequence in which the business rules are checked using condition record of the condition table for proposing output type.
    Sapfans Q & A
    SREL_GET_NEXT_RELATIONS   -
    Function Module that will provide me the number of the document that was created by an IDoc
    RLSUB020
    Program which uses the above function module.
    Upgradation problem
    When the old version program is upgraded in to newer version(4.0b &#61664; 4.6c) the SE38 editor won’t allow u get thru’ the programs normally to get rid of this.
    Solution:
    EDIT > MODIFICATION OPERATIONS > SWITCH OFF ASSISTANT. Hit Enter on the subsequently shown Warnings window. You should now be able to maintain the code as before.
    When transporting the dialog program sometimes the links may be missing in the testing and production area. To overcome just check u have properly save your all includes and other stuff in the same request if not, do so. Other options In ver 4.6c -> Within ABAP editor try utilities/Update navigation index
    this fixes the links
    ALE( Application Link Enabling )
    Disk Mirroring:
    Changes occurring in the database should reflected to another disk that maintains a mirror image of the main disk’s contents.
    Replicas:
    Maintaining redundant data across multiple systems.
    ALE:
      It provides distributed environment to integrate non-SAP systems
      Provides guaranteed delivery of data regardless of network problem to application.
    Logical system :
         The systems involved in distributed environment  are assigned a logical name which uniquely identifies a system in a distributed  environment.
    Data Mapping:
         Conversion of a business document in IDoc format to an EDI format (and vice versa) which is performed in the subsystem.
    Message Types:
    •     Represents a business function
    •     Technical structure is the IDoc type
    •     Or can say an instance of IDoc.
    <b>IDoc  :</b>
         They are containers used to exchange data between any two process.
         It represents an IDoc type and IDoc data
         IDoc type is structure and IDoc data is an instance of it.
    <b>Pls reward if helpful.</b>

  • CRMXIF_REL_SAVE_M01 - Mapping Question

    Hello All,
    I have a mapping question, hope some one can answer my question. Please see the link first and the see my question
    http://www.flickr.com/photos/8764045@N06/4265246260/sizes/o/
    I'm mapping the CRM IDOC to the JDBC Call. I have small problem here. All the target fields are Mandatory 1..1 .
    I will explain with an example:
    I have field from source E102BUS_EI_STRUC_TEL_DATA/COUNTRY mapped to target field.
    I used Map With Default so that even if the values are not there frm the source the target field will be mapped with blank.
    But the problem is the parent node for E102BUS_EI_STRUC_TEL_DATA is E102BUS_EI_BUPA_TELEPHONE is 0.999999 , so sometimes that segment is not coming. In this case Map with Default won't work. Map with Default willl work only if the Parent node is present.
    If you ask me to do Exists node function on E102BUS_EI_BUPA_TELEPHONE and then apply Map with Default, then even this won't work.
    Apologize if I confused you guys. Please let me know if you need more clarification.
    Thanks!
    Raj.

    Hi Raj,
    Try to do a mapping like this
    E102BUS_EI_STRUC_TEL_DATA(context E102S_EI_BUPA_TELEPHONE_CON)--mapwithdefault-->then
    E102BUS_EI_BUPA_TELEPHONE-->exists------------------------------------------------------------------>if---->splitbyValue
    let us say this output (the output of splitbyvalue) as 'VALUE'
    VALUE-----------------------------------------------> then
    VALUE|-->count--->greater----------------------->if----->targetField                            
          Constant(0)---->              Constant(blank)-->else
    Regards
    Suraj

  • Interface between sap to non sap using edi idoc

    hello abaper's,
                         i have requirment on creating Interface program for downloading files(PO)  from Non-sap system  to sap system using EDI Idoc techniques.pls give me a good tips for this requirment..
    With Regards
    MurugeshRajeev

    Hello,
            First of all, we'll need to identify as to what we want to do with the PO Data. For example, If we want to Create Sales Order, there is already a Posting Program available with the Name IDOC_INPUT_ORDERS (FM). This is useful for Creating a Sales Order automatically whenever a PO IDoc is received.
    Here is the Information for processing Standard IDoc.
    1. WE30 - ORDERS05 - IDoc  Type
    2. WE31 - Segment Definition for the IDoc Type
    3. WE81 - Logical Message Types (ORDERS)
    4. WE82 - Assigning the Message Type to IDoc Type
    5. WE42 - Define Process Code
    6. BD51 - If you want to Code a Custom Function Module,
                  then after creating it, you need to register the same
                  Function Module in this Transaction Code.
    7. WE57 - Assign Message Type / IDoc Type / FM group.
    8. WE20 - Partner Profiles
    9. WE21 - Port Definitions
    Hope this information was helpful.
    Thanks and Regards,
    Venkat Phani Prasad Konduri

  • Find status of a sales order created using EDI IDOC

    Hello everyone,
       I have IDOC created for incoming sales order using FM 'IDOC_INPUT_ORDERS'.
    When a sales order is created manually iva VA01, it prevents the order from being saved when a specific error is hit unless user resolved it first.   However, when the order is created via EDI IDOC, the error is hit and it cannot be created.  In the sapmv45a program, i will to say that if it is an EDI IDoc transacion for the order, let it bypass the error and create the order.  
         Can anyone pls tell me how to check the status of a sales order being created using EDI IDOC ?
    Sy-batch does not work.
    Thank you in advance.
    Joyce

    Joyce,
    If you pay attention the code in FM it is exporting value of da_edi_sign to memory id "SD_EDI_ACTIVE" stored in constant "da_memory_id". ('CONSTANTS: da_memory_id(13) VALUE 'SD_EDI_ACTIVE'.)
    In your program you have two you have two options.
    1. Declare a constant as in the FM and use that as mentioned below:  
    CONSTANTS: da_memory_id(13) VALUE 'SD_EDI_ACTIVE'.
    IMPORT v_memid FROM MEMORY ID da_memory_id.
    2. Hardcode memory id as below:
    IMPORT v_memid FROM MEMORY ID 'SD_EDI_ACTIVE'.
    Hope this resolves your problem.
    Gajendra

Maybe you are looking for