IDoc and Message Mapping

Hi,
I have a question.
In a idoc to file scenario,idoc as a sender,.If the idoc is updated in r/3 system due to some change request after we finish the mesage mapping,what steps need to be followed to ensure the correct mapping.
Do we need to change the mapping.
Regards,
Haritha

Hello,
if just the values of your IDoc changed you don't have to change
your message mapping.
If the structure has changed you have to reload the metadata (idx2)
and the IDoc in your Repository and then update your message mapping with reloading your IDoc.
Regards
Patrick

Similar Messages

  • XI 7.0 passing attributes between java mapping and message mapping

    Hi all,
    Here's a newbie question. There is a scenario where an interface mapping has several stages of java mapping and message mapping
    I would like to know how to set attributes in the java mapping so that it can be accessed in a message map (or vice versa). What I intend to do is pass some information from one mapping to the other so that action can be taken based on the values passed.
    Thank you!

    Another option is storing the values in the message header in the same way as the Adapter-Specific Message Attributes:
    http://help.sap.com/saphelp_nw04/helpdata/en/43/09b16006526e72e10000000a422035/frameset.htm
    Just use your own name/namespace combination, which is not used in any adapter.
    If possible use the way that Sandro proposed and add the information which you need to additional tags in the payload.
    Regards
    Stefan

  • Diff bet IDOC and Message Types.

    What are the difference between IDOC and Message types.
    Diff between MATMAS01 ,MATMAS02 and MATMAS03

    IDOCs:
    - IDOC is an Intermediate Document. It is simply a data container used to exchange information between any two processes  that can understand the syntax and semantics of the data.
    An IDOC is created as a result of executing an Outbound ALE or EDI process.
    In an inbound ALE or EDI process, an IDOC serves as input to create an application document. When an IDOC is created in the system , an unique number(16 Digits) is assigned to it.IDOC will wait until the Remote System is Active.
    Basic Idoc Type: Basic Idoc type defines the structure and format of the business document
    that is to be exchanged between  two systems. Basic Idoc type can refer to an SAP provided
    basic IDOC type or a customer developed basic IDOC type.
    - A basic IDOC type has the following characteristics:
    Name : A basic Idoc type can be assigned upto a thirty character name.
    List of permitted segments: The segments make up the IDOC structure.
    Hierarchy of segments : The hierarchy of segments specifies the physical sequence and any parent - child relationship in the segments.
    Mandatory Vs Optional Segments : When used in the IDOC type, each segment has an attribute that defines whether the segment  is option or mandatory. Minimum/Maximum range for each segment: It defines the maximum and minimum number of timesa data record corresponding to a segment cn exist in an IDOC.
    -Segments : A segment defines the format and structure of a data record. Segments are reusable componets. A segment consists of various fields that represent data in data record.
    IDOC Record Types:
    1. Control Record : The control record contains all of the control information about an IDOC, this information basically includes the IDOC number, sender and receiver information, and information such as the message type it represents and the IDOC type. 
    - there is only one control record per IDOC.
    - The stucture of the control record is the same for all the IDOCs and is defined by SAP.
    - The structure of the control record is defined by the data dictionary structure EDI_DC40. The control record is stored in the EDIDC table.
    2. Data Record : Data records contain the application data. A data record has two sections
    Administrative Section and a Data section.
    - The Administrative section cotain the segment name, client, IDOC number, segment number, hierarchy level information.
    - The Data section of a data record is a stram of 1000 bytes where the actual data resides.
    - The data record is defined by the data dictionary structure EDI_DD40.
    - Data records for IDOCs stored in the EDID4 table.
    3. Status Record : Status records are attaced to an IDOC throughout the process as the IDOC achieves different milestones or encounters an error. At every milestone a statu code, date and time are assigned.
    - Status codes 01 to 49 are reserved for OUtbound process, 50 and above are reserved for inbound processes.
    <u><b>IDOC TYPE IS AN INSTANCE OF IDOC</b></u>
    Message Type: Identifies what type of information transformed between logical systems or partners.Message type is not   a   local object type , it is transportable.
    For different applicatons we have different MESSAGETYPE.
    example:
    <u>APPLICATION</u>                <u>  MESSAGETYPE</u>
    MATERIAL MASTER                       MATMAS
    VENDOR MASTER                          CREMAS
    CUSTOMER MASTER                      DEBMAS
    MATMAS01, MATMAS02, MATMAS03, MATMAS04, MATMAS05 are all MESSAGETYPES  ... FOR NEW VERSIONS LIKE SAP 4.7EE, SAP ECC5.0....we have to use MATMAS05 message type. for older versions like SAP R/3 we have to use MATMAS01.
    REWARD ME IF THIS IS HELPFUL

  • Hi , friends pls explain abap mapping and message mapping

    1) pls explain abap mapping and message mapping
       send me screen shorts also.

    Hi
    Mapping Techniques
    XI provides 3 standard ways of interface mapping between source and target.
    Graphical mapping
    Java Mapping
    XSLT Mapping
    Two more additional mapping types can be activated in XI by making changes to the exchange profile. Those two mappings are
    ABAP mapping
    XSLT mapping with ABAP Extensions
    Graphical Mapping
    Graphical mapping is a common approach followed by everyone for generating desired target structure. It involves simple drag-n-drop to correlate respective nodes (fields) from source and target structure. It hardly involves coding. (Exception - User defined functions). But sometimes with graphical mapping it is difficult to produce required output. For example ... text/html output, namespace change, sorting or grouping of records etc.
    ABAP Mapping
    A person comfortable with Object Oriented ABAP can go for ABAP mapping instead.
    Java Mapping
    Java Mapping uses 2 types of parsers. DOM and SAX. DOM is easier to use with lots of classes to help you create nodes and elements, but , DOM is very processor intensive.
    SAX parser is something that parses your XML one after the other, and so is not processor intensive. But, it is not exaclty easy to develop either.
    XSLT Mapping
    One can also think of Java mapping as another option but it is a bit complex and required knowledge of Java. In such cases, XSLT mapping can be the best approach to meet the requirements.
    A few example cases in which an XSLT mapping can be used:-
    When the required output is other than XML like Text, Html or XHTML (html displayed as XML)
    When default namespace coming from graphical mapping is not required or is to be changed as per requirements.
    When data is to be filtered based on certain fields (considering File as source)
    When data is to be sorted based on certain field (considering File as source)
    When data is to be grouped based on certain field (considering File as source)\
    Advantages of using XSLT mapping
    XSLT program itself defines its own target structure.
    XSLT programs can be imported into SAP XI. Message mapping step can be avoided. One can directly go for interface mapping once message interfaces are created and mapping is imported.
    XSLT provides use of number of standard XPath functions that can replaces graphical mapping involving user defined java functions easily.
    File content conversion at receiver side can be avoided in case of text or html output.
    Multiple occurrences of node within tree (source XML) can be handled easily.
    XSLT can be used in combination with graphical mapping.
    Multi-mapping is also possible using xslt.
    XSLT can be used with ABAP and JAVA Extensions.
    Disadvantages of using XSLT mapping
    Resultant XML payload can not be viewed in SXMB_MONI if not in XML format (for service packs < SP14).
    Interface mapping testing does not show proper error description. So errors in XSLT programs are difficult to trace in XI but can be easily identified outside XI using browser.
    XSLT mapping requires more memory than mapping classes generated in Java.
    XSLT program become lengthier as source structure fields grows in numbers.
    XSLT program sometimes become complex to meet desired functionality.
    Some XSL functions are dependent on version of browser.
    Different types of Mappings
    MAPPING SUPPORTED BY XI
    Message Mapping -> Graphical Design and testing environment. Default Provided By XI. Queue based modelling allow handling or large documents. Extensible via user defined functions
    XSLT Mapping - > Based on openstandard, Portable across application platform, Extensible using user defined functions kewl but disadvantage is Memory overload while handling large documents.
    SAX -> Simple Api For XML. -> Allows you to parse through a XML document. Doesn't consume any memory. But the message can be parsed only once from top to bottom. It Has evolved by contributions made by group of ppl itz a open architecture.
    DOM -> Document Object Model -> Itz designed by W3C. Consumes Memory as the message will be loaded. Allows parsing of document in both way top down and bottom up.
    Send me your email id.Shall send you very good docs for both ABAP Mapping and message mapping.
    Thanks

  • ISU Billing/Invoicing IDOCS and Message Type

    Hi,
    Could any body provide me the list of IDOCS and Message types for Billing and Invocing Module. I was unable find the list across web.

    To get the idoc list , u should go to the transaction WE02, and give the search parameter as the  basic type of the above said message types..

  • ABAP Mapping  and Message Mapping

    Hello
    I want to do the followig mapping
    File - > IDOC
    field1  ->field_idoc1
    field2  ->field_idoc2
    field3  ->field_idoc3
    field4  -> (based on an dictionary table in the R/3)
    For the first 3 fields I will use message-mapping.
    For field4 I heard about ABAP Mapping. Select with the value of field4 in an ABAP Table and response the new value to the mapping back.
    Would both mappings in one Interface-Mapping work?
    Regards
    Christoph

    Christoph, There was an article previously available in articles section, now i dont find the link.
    I have given a sample code below. You can find lot of sample JCO code provided along with the JCO library that can be downloaded from service.sap.com.
    JCO.Repository mRepository;
    JCO.Client mConnection = JCO.createClient(
                   sapClient,
                   userName,
                   password,
                   language,
                   hostName,
                   systemNumber );
    // connect to SAP
    mConnection.connect();
    // create repository
    mRepository = new JCO.Repository( "sample", mConnection );
    // Create function
    JCO.Function function = null;
    IFunctionTemplate ft = mRepository.getFunctionTemplate("Z_TEST");
    function = ft.getFunction();
    // Obtain parameter list for function
    JCO.ParameterList input = function.getImportParameterList();
    // Pass function parameters
    input.setValue( param1_value , "P_PARM1");
    input.setValue( param2_value , "P_PARM2");
    JCO.ParameterList tabInput = function.getTableParameterList();
    JCO.Table inputTable = tabInput.getTable("T_PARM3");
    inputTable.appendRow();
    inputTable.setValue("test" , "IDOC");
    mConnection.execute( function );
    String ret = function.getExportParameterList().getString( "P_GEN_NUM" );
    mConnection.disconnect();
    return ret ;
    Regds
    Saravana

  • IDOC in Message mapping

    Hi folks,
    I am working on file to idoc scenario.   I Imported the IDOC to my scenario. In Messaga Mapping IDOC structure displaying fields as a documention. but i need techincal names of those fields.
    for Example:   In my IDOC 1 field is showing companycode but I want to see that field as a BUKRS.
    How to see the technical names of IDOC fields in Message Mapping.
    Your help is highly appreciated.
    Thanks,
    Anitha.

    Hi bavesh...
    thank you so much for very your quick responses..
    i got xsd as source..based on xsd i created external definition for source xsd  and  i created outbound interface based on source external deifinition <b>MI_OUT_WearUnits</b>.
    and i imported Idoc and exported as xsd and changed occurance to unbounded and again imported as external definition.
    i did mapping between these two external definitions.
    and i selected standard idoc for source and target interface for interface mapping  and given message mapping of previous step.
    In ID
    sender agreement :
                    sender service :BS_external
                    sender interface :<b>MI_OUT_WearUnits</b>
    receiver agreement:
                  receiver service :R/3
                  receiver interface :  standard Idoc
    Interface determination:
    sender service :BS_external
    sender interface :<b>MI_OUT_WearUnits</b>
    reciever service :R/3
    and clicked create
    inbound interface : Standard IDOc
    i am not getting Interface mapping which i created in IR.
    i tried Enhance interface determination also..
    please guide me....
    waiting for your help.
    regards
    ram

  • File to IDOC Senario (Message Mapping)

    Hi Experts,
    I am a fresher.
    This is "  File to IDOC Senario  ".
    I have Doubt on  this: ( In Message Mapping)
    Source field : MSG
    Length : 1/264
    Taget field : E1EDKT2 - TDLINE
    Legth : CHAR/70
    Mapping Condition :
    Note: TDFORMAT =  ‘=’ (Long Line), until next line of MSG. When new line occurs in MSG, then use TDFORMAT = ‘/’
    How to Make the Mapping for this?
    Anyone Can help me to get it Quickly.
    give your Suggestions and Show some Example Mappings......

    Hi ,
    Below is the generic sol for your problem .Graphical mappings wont workout for your problem while using sub string .
    Input -->Input string
    Length -->length of TDLINE
    MESSAGE_V1,V2,V3,V4....depends on how many TDLINES you expect .Here I have taken 4 .
    public void SplitbyLength(String[] Input, String[] Length, ResultList MESSAGE_V1, ResultList MESSAGE_V2, ResultList MESSAGE_V3, ResultList MESSAGE_V4, Container container) throws StreamTransformationException{
    int lengthVal = Integer.parseInt(Length[0]);
    int InpLenVal ;
    for(int i=0;i<Input.length;i++)
    InpLenVal  =Input[i].length() ;
    if (InpLenVal<=lengthVal)
    MESSAGE_V1.addValue(Input[i].substring(0));
    MESSAGE_V2.addValue(ResultList.SUPPRESS); 
    MESSAGE_V3.addValue(ResultList.SUPPRESS); 
    MESSAGE_V4.addValue(ResultList.SUPPRESS); 
    else if ((InpLenVal>lengthVal) && (InpLenVal <= (lengthVal*2)))
    MESSAGE_V1.addValue(Input[i].substring(0,lengthVal));
    MESSAGE_V2.addValue(Input[i].substring(lengthVal,InpLenVal));
    MESSAGE_V3.addValue(ResultList.SUPPRESS); 
    MESSAGE_V4.addValue(ResultList.SUPPRESS); 
    else if ((InpLenVal>(lengthVal*2)) && (InpLenVal <= (lengthVal*3)))
    MESSAGE_V1.addValue(Input[i].substring(0,lengthVal));
    MESSAGE_V2.addValue(Input[i].substring(lengthVal,(lengthVal*2)));
    MESSAGE_V3.addValue(Input[i].substring((lengthVal*2),InpLenVal));
    MESSAGE_V4.addValue(ResultList.SUPPRESS); 
    else if (Input[i].length()>(lengthVal*3)  && (InpLenVal <= (lengthVal*4)))
    MESSAGE_V1.addValue(Input[i].substring(0,lengthVal));
    MESSAGE_V2.addValue(Input[i].substring(lengthVal,(lengthVal*2)));
    MESSAGE_V3.addValue(Input[i].substring((lengthVal*2),(lengthVal*3)));
    MESSAGE_V4.addValue(Input[i].substring((lengthVal*3),InpLenVal));
    else if (Input[i].length()>(lengthVal*4) )
    MESSAGE_V1.addValue(Input[i].substring(0,lengthVal));
    MESSAGE_V2.addValue(Input[i].substring(lengthVal,(lengthVal*2)));
    MESSAGE_V3.addValue(Input[i].substring((lengthVal*2),(lengthVal*3)));
    MESSAGE_V4.addValue(Input[i].substring((lengthVal*3),(lengthVal*4)));
    Regards
    Venkat

  • Idoc and message type not getting replicated in the receiver system

    Hi
    i have created a Z Idoc and didtributed the mode from system A ....I can see the distribution model in system B
    However i cannot see the custom zidoc / message type in sys B.. Do i need to create the zidoc again in sys B

    Hi Tarang,
    at least ou need the required partner agreements and you should have a processing function for inbound IDoc. To implement this, the full definition of IDoc including Segment definition should be present in receiving system.
    Just look at standard IDocs and do as they do.
    Regards,
    Clemens

  • Test XML file and Message Mapping test tab not compatible

    Hi all,
    I need help in testing in message mapping test tab.
    I have a xml data taken from SXMB_MONI which looks lik below
    &?xml version='1.0' encoding='UTF-8'?>
    -&ns0:MT_Order xmlns:ns0="http://test.com/xi/test">
    -<Header>
          <fld1>
          <fld2>      
        -<Line>
            <line1>
    and in message mapping multimapping is used,so it looks like
    ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
       <ns0:Message1>
          <ns1:KVNR_Senden_MT xmlns:ns1="urn:lsv.de/SENDER">
             <Inhalt>
                <KE/>
                <VF/>
                <BBNRAB/>
                <BBNREP/>
    how can test this xml in message mapping test tab?please don't consider the structure .I don't have them.So,i have pasted some dummy structure

    Try like this,
    ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
    <ns0:Message1>
    <&ns1:MT_Order xmlns:ns0="http://test.com/xi/test">
    <Header>
          <fld1>
          <fld2>      
        -<Line>
            <line1>

  • Reg: JDBC to IDOC Scenario Message Mapping

    hi Friends
    i am designing a Scenario JDBC - IDOC for accounting document interface using ACC_DOCUMENT03 idoc.
    i need the mapping program for that to map the JDBC fields with the IDOC fields, so can anyone help me the mandatory fields and the constant values for the IDOC which has to be mapped.Along with this can i know why the constants will be assigned to the fields like Begin =1 , MSGFN = 009 etc how these constants are defined.
    Thanks&Regards
    suman.

    Hi,
    for mapping constants in graphical msg mapping, select your target IDOC field..........then you have a constant in the below screen.........click it and then double-click on constant to change the value of the constant field.........then map this constant to your target IDOC field.
    for knowing which are the mandatory fields, ask your functional guys to tell you the mandatory fields in data segment of your IDOC and regarding Control segment EDIDC, you have to map fields which have sender and reciever system details.
    Regards,
    Rajeev Gupta
    Edited by: RAJEEV GUPTA on Feb 2, 2009 7:55 AM

  • Exchanging data between interface mapping and message mapping possible?

    Hi,
    please have a look at my interface mapping:
    source message -
    >
    mapping programs
    1. Java mapping
    2. XSL mapping
    3. message mapping
    > target message
    in my scenario a Java Class (1) is called for the interface mapping. There, some information ist read from the xml structure. Next, a xslt mapping (2) takes place that strips some information. The remaining data is passed to the message mapping (3)
    The reason for this is that the source message consists of a xml message inside an xml message.
    I am looking for a way to access the informationen gained in step 1 (Java class) in the message mapping (step 3). I was hoping that the global container (used by user-defined function within message mapping) is accessible from the java mapping, but I could not find out how.
    Anybody with some ideas how to pass information from step 1 to step 3? I cannot put the Information in the xml that is passed to the message mapping, because the schema of the inner xml cannot be changed.
    Thanks very much, best regards,
    Wolfgang

    Hi Wolfgang!
    I have used the "Dynamic Configuration" section in the XI Message header for this issue. You could write something into the Dynamic Configuration Section in step 1 (Java-Mapping) and read it out again in steps 2 or 3. You could use a section for a adapter you are not using in your interface for the real receiver. So if you have a File-Receiver Adapter at the "end" you could use some section of the e.g. SOAP adapter not to interfere with your receiver-adapter when using Dynamic Configuration Settings there ...
    See also: http://help.sap.com/saphelp_nw04/helpdata/de/43/09b16006526e72e10000000a422035/content.htm
    or
    http://help.sap.com/saphelp_nw04/helpdata/de/43/0a7d1be4e622f3e10000000a1553f7/content.htm
    Best regards,
    Andi

  • Proforma Invoice - IDoc and message type

    Hi,
    The requirement is to send proforma invoice to legacy system upon creation. We use PI as middleware.
    Is it possible to send to proforma invoice data using IDoc?
    If IDoc then we have to use message control? Am i right?
    What is the process code and what is the basic IDoc type/message type to be used for this?
    Thanks for any help.
    Cheers,
    Srini

    Hi Srinivasan
    Basic type           INVOIC01  Invoice/Billing document
    Message type                   INVOIC     Invoice / Billing document
    Process code         SD09
    Description          INVOIC: Invoice
    Function module      IDOC_OUTPUT_INVOIC
    best of lucks and Happy Diwali
    Nandu

  • File to idoc and no mapping?

    Hi
    We are using PI 7.0
    IDOCFileSender->PI7.0->ALERECEIVER
    we have a file in the "native" file format for an idoc, we now would like to process this file through PI and sending it to our SAP systems ALE layer. We are not allowed to call the ALE adapter directly in our SAP system from the system generating the native idoc format - it must be done only through PI !
    My question is if it is possible using the fileadapter to read this file and with pass it throug PI to IDOC receiver adapter without any mapping? In that case what should the Message Type we are using in the file-sender adapter look like?
    Hope for some help.
    Thx

    Hi,
    >is possible using the fileadapter to read this file and with pass it throug PI to IDOC receiver adapter without any mapping?
    yes
    >In that case what should the Message Type we are using in the file-sender adapter look like?
    If you have no mapping it doesnt matter, the message type will not be validated during runtime. You can take the IDoc type imported from the SAP system
    Regards,
    Udo

  • Idoc and order mapping

    Hi,
       How to find the relationship between the order and idoc in crm.
    I have a sceneraio like if i give the idoc number it has to display the corresponding order number. Where can i find the link between this..
    link between crm order and idoc.
    Regards
    Srinu
    Message was edited by:
            sreenivasulareddy eragamreddy

    Hi,
    IDOC for sales order is ORDERS05. Segment E1EDKA1, for field go to SE11 and enter E1EDKA1 to find field for sales order.
    Cheers.
    ...Reward if useful.

Maybe you are looking for