IDOC encoding

Hi all,
I am sending IDOCs from PI 7.0 SP12 to SAP 4.6C. The problem is that some characters are garbled on the backend.
On the PI side (sxmb_moni) I see all characters in the payload correctly. Payload type is application/xml with encoding utf-8.  
But on the backend side some characters in the Idoc are garbled.
It seems that IDOC is not converted from UTF-8 to ISO-8859, which is the code page of 4.6C.
Any suggestion how to solve this?
Thanks, janos

Hi,
Thanks for your answers, but I still didnt solve the problem.
My understanding  is that I must activate the MDMP in the RFC destination for the backend.
The logon language is set correctly.
I have some doubts that MDMP is set correctly, since I see inside something like this.
Lang Local Remote
SR     0000     1500
RO     0000     1401
SL     0000     1401
HR     0000     1401
MS     0000     1100
UK     0000     1500
CS     0000     1401
Is it correct to have zeros for all Local?
If I try to change Local code page to 4110, which I think is the code page of UTF-8,
I got the following pop-up msgs :
Local     Incorrect codepage: 4110. Must be a system codepage and reference to tables TCP00 and TCP0C,
A system codepage is required here.
The table TCP00 contains all the codepages and TCP00-CPISSYSTEM must be activated for one system codepage.
Other criterion: The code page must appear in TCP0C-CHARCO.
(Currently, 2002-7-2, there are system codepages that appear in TCP0C, but for which the attribute CPISSYSTEM is not activated in TCP00 - for example, 1610).
Please advice what needs to be done here. How to sent IDOCs from IE (UTF-8) to backend (iso-8859-2).
Best regards,
Janos

Similar Messages

  • XI 3.0 -    XML - IDOC inbound scenario  via ftp  UTF-8 character encoding

    Hi Everyone,
    I'm having difficulties with a particular scenario. I receive via the ftp adapter xml files which have a header indicating UTF-8 coding. In SXMB_MONI, i see the cyrillic characters and after mapping the target message payload as well have readable cyrillic characters. The problem comes when i have the SAP-side check the idoc that posted in their system. They see gibberish (i.e ##### #### ### #').
    I have already tried changing the XSD definition of the xml to UTF-8 however upon import it automatically changes it to ISO-8859-1. I've tested sending the xml file to XI with an ISO-8859-1 coding header and in SXMB_MONI it's gibberish as well. So i've elminated that from possible problems.
    i have checked SM59 on the receiving system and unicode is checked as well.
    where could the problem possibly be?
    Thank you,
    Kent

    Hi,
    Thank you for the quick reply. however that did not solve it. I believe the Cyrillic character set lies in the UTF-8 set. i mentioned about the ISO to elmiinated its possibility and the problem i face when importing an XSD definition as it automatically changes the encoding to that set. I have confirmed that it should be UTF-8.
    I have isolated the problem to between the XI box and the SAP receiving box. in SXMB_MONI, up to the call adapter part, the payload shows the correct characters. upon checking it in the receiving system at tcode "we02", the value is all gibberish.

  • How do we determine the JVM encoding of an R/3 system sending idoc to EAI?

    Hi experts,
    can you please help me find out the JVM encoding or our R/3 system. We are currently sending an IDOC via RFC connection to webmethods. the recieving side is not able to process special characters like the TradeMark (TM) superscript, and they are suspecting that the JVM encoding is not in sych. I have search already to find this out in the R/3 system but have not found any clue. I am a bit skeptical though, this is the first time i heard that JVM is being used on RFC.
    Thanks in Advance!
    Regards,
    Alden

    Ken, take a look at the value being mapped to the E1EDK01-BSART field.  Is it 'CRME' or 'INVO' or other?  This value controls the setting of the variable 'bsart_cremem' and subsequent debit/credit handling from there in the IDOC process code.

  • Corrupt XML file encoding utf-8 special chars (IDOC - File scenario)

    Dear experts,
    I have a problem with the XML output files of XI and could not find the answer in one of the current posts.
    I'm sending Master Data from R/3 with IDOCs through XI to a FTP directory. These files include characters as Á, Ê, etc.
    The XI server includes the utf-8 encoding in the output XML message. However, when opening these files I receive errors (tried it in multiple programs). It tells me that Á is not utf-8.
    It will not accepts Á. I was under the impression that utf-8 included extended Latin and thus would accept these characters. Thus implying that the message was created wrong. Also importing these files into MDM import manager gives errors.
    All rfc destinations are on Unicode.
    By the way, we experience the same problem when syndicating files from the MDM server.
    Any suggestions?
    Cheers.
    * Will reward points for helpful answers.

    Hi,
    Check out this guide..
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42
    make use of the messagetransformbean - http://help.sap.com/saphelp_nw04/helpdata/en/57/0b2c4142aef623e10000000a155106/content.htm
    Also for further ref: go thru this thread - Change encoding from utf-8 to iso-8859-1 in JMS receiver!
    regards
    sasi.........
    <b>Reward if useful</b>

  • Character Encoding for IDOC to JMS scenario with foreign characters

    Dear Experts,
    The scenario is desribed as follows:
    Issue Description:
    There is an IDOC which is created after extracting data from different countries (but only one country at a time). So, for instance first time the data is picked in Greek and Latin and corresponding IDOC is created and sent to PI, the next time plain English and sent to PI and next Chinese and so on. As of now every time this IDOC reaches PI ,it comes with UTF-8 character encoding as seen in the IDOC XML.
    I am converting this IDOC XML into single string flat file (currently taking the default encoding UTF-8) and sending it to receiver JMS Queue (MQ Series). Now when this data is picked up from the end recepient from the corresponding queue in MQ Series, they see ? wherever there is a Greek/latin characters (may be because that should be having a different encoding like ISO-8859_7). This is causing issues at their end.
    My Understanding
    SAP system should trigger the IDOC with the right code page i.e if the IDOC is sent with Greek/Latin code page should be ISO-8859_7, if this same IDOC is sent with Chinese characters the corresponding code page else UTF-8 or default code page.
    Once this is sent correctly from SAP, Java Mapping should have to use the correct code page when righting the bytes to outputstream and then we would also need to set the right code page as JMS Header before putting the message in the JMS queue so that receiver can interpret it.
    Queries:
    1. Is my approach for the scenario correct, if not please guide me to the right approach.
    2. Does SAP support different code page being picked for the same IDOC based on different data set. If so how is it achieved.
    3. What is the JMS Header property to set the right code page. I think there should be some JMS Header defined by MQ Series for Character Encoding which I should be setting correctly) I find that there is a property to set the CCSID in JMS Receiver Adapter but that only refers to Non-ASCII names and doesn't refer to the payload content.
    I would appreciate if anybody can give me pointers on how to resolve this issue.
    Thanks,
    Pratik

    Hi Pratik,
         http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42?quicklink=index&overridelayout=true
    This link might help.
    regards
    Anupam

  • Idoc inbound error - encoding question

    Hello,
       I receive idoc file from a parnter.
       I create a File Ports(WE21) : Non-unicode format and Checked 'Continue Despite Conversion Error'.
       The partner send to us a file with ASCII-encoding including  German NÄHER .
       In WE02, I found the line with German NÄHER disordered.  ÄH became char  腍 ，but I have set 'Continue Despite Conversion Error'.
       like this:
               PCKAR     SACK NICHT N腍ER SPEZIFIZIERT      0
               PCKNR     000SAC                            8
               ANZAR     00.000        0
               VBELN     301866818                         0
               POSNR     00060                        6
               BTGEW     000.000          0
               NTGEW     .000             1
               TARAG     .000             K
               GEWEI     GM0
               BTVOL     .000             0
       If the parnter don't want to change the encoding, Can I do something to make it worked ?
                                                                                    Thanks.

    I post the same question on Expert Forums » Application Server » Unicode
    It's OK now.
    ======================
    Good way:
    Add this code before CALL FUNCTION 'EDI_DATA_INCOMING'
    SET LOCALE LANGUAGE 'D'. "table t002
    Nils Buerckel's answer :
    Hi Harry,
    this is not a conversion error.
    The file contains Latin-1 data with the special character "Ä".
    Now I assume you use as logon language in the Unicode system ZH (or another Asian language) ... ?
    Then the system evaluates SY-LANGU and converts the Non-Unicode file based on the Asian code page.
    Then ÄH will be interpreted as 腍. Hence the system gets a word with 4 characters instead of 5.
    This can lead to shiftings in the whole idoc and the idoc might be invalid.
    Therefore I would propose to upload the idoc using logon language EN or change it via "setlocale " in abap code.
    Best regards,
    Nils Buerckel
    SAP AG
    Edited by: Harry on Jul 29, 2009 2:38 AM
    Edited by: Harry on Jul 29, 2009 2:39 AM

  • How to encode XML to Idoc and decode Idoc to XML in business connector?

    Hi all,
    first of all: thanks for all, who are reading and perhaps responding this question!
    Here some facts and my question(s):
    The facts:
    - I have the business connector version 4.6!
    - I'm not working with any SAP Netviewer!
    - I have XML files on an FTP-server and Idoc-files on an FTP-server --> so no connection between SAP and business connector, meaning: the files are just on the ftp-server!
    What am i doing and what is working properly:
    - Business connector logs in into the FTP-server (with FTP-service: pub.client.ftp:login)
    - gets the file (with FTP-service: pub.client.ftp:get) (the idoc-file, when i want to convert it into XML or the XML-file, when i want to convert it into idoc-format)
    - puts the file into another place in the server (with service wm.PartnerMgr.gateway.transport.FTPTransport:OutboundProcess)
    !!!So far only getting and putting of the file works!!!
    What is missing between getting the file in one format - for example idoc-format - and putting the file into the server in the other format - for example XML-format is:
    CONVERSION FROM XML INTO IDOC AND VICE VERSA
    My question:
    - which services i have to use between getting and putting the files?
    Thanks to all,
    Tamer

    Hi,
    I have the same problem. I do fix it?
    Thanks
    Wilson Xavier
    Brazil

  • Error Posting IDOC: need help in understanding the following error

    Hi ALL
    Can you please, help me understand the following error encountered while the message was trying to post a IDOC.
    where SAP_050 is the RFC destination created to post IDOCs
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
      <SAP:P1>FM NLS_GET_LANGU_CP_TAB: Could not determine code page with SAP_050 Operation successfully executed FM NLS_GET_LANGU_CP_TAB</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error: FM NLS_GET_LANGU_CP_TAB: Could not determine code page with SAP_050 Operation successfully executed FM NLS_GET_LANGU_CP_TAB</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Your help is greatly appreciated.............Thank you!

    Hi Patrick,
      Check the authorizations assigned to the user which you used in the RFC destinations, If there is no enough authorizations then it is not possible to post the idocs.
    Also Refer this Note 747322
    Regards,
    Prakash

  • Error in creation of  PurOrd IDoc

    Hi All,
    I have set up the output type for PO and created patner profiles and also add the message types ORDER and ORDCHG  but  when I save the PO and check the messages, I get an error: " No recipient found for message type ORDERS in the ALE Model ".
    What could be the possible problem?
    Highly appreciate any kind of help.
    Thanks in advance,
    Shweta
    PS: <b><REMOVED BY MODERATOR></b>
    Message was edited by:
            Alvaro Tejada Galindo

    Hi
    Check the Partner Profile in WE20 correctly
    also see the steps for it as per the doc
    Data Creation in Idoc
    IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
    asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
    While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
    IDoc is a intermediate document to exchange data between two SAP Systems.
    *IDocs are structured ASCII files (or a virtual equivalent).
    *Electronic Interchange Document
    *They are the file format used by SAP R/3 to exchange data with foreign systems.
    *Data Is transmitted in ASCII format, i.e. human readable form
    *IDocs exchange messages
    *IDocs are used like classical interface files
    IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    FOr testing you can use WE19.
    How to create idoc?
    *WE30 - you can create a IDOC type
    For more information in details on the same along with the examples can be viewed on:
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
    http://www.sappoint.com/presentation.html
    http://www.allsaplinks.com/idoc_search.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://www.erpgenie.com/sapedi/idoc_abap.htm
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30 )
    Create Message Type ( WE81 )
    Assign Idoc Type to Message Type ( WE82 )
    Creating a Segment
    Go to transaction code WE31
    Enter the name for your segment type and click on the Create icon
    Type the short text
    Enter the variable names and data elements
    Save it and go back
    Go to Edit -> Set Release
    Follow steps to create more number of segments
    Create IDOC Type
    Go to transaction code WE30
    Enter the Object Name, select Basic type and click Create icon
    Select the create new option and enter a description for your basic IDOC type and press enter
    Select the IDOC Name and click Create icon
    The system prompts us to enter a segment type and its attributes
    Choose the appropriate values and press Enter
    The system transfers the name of the segment type to the IDOC editor.
    Follow these steps to add more number of segments to Parent or as Parent-child relation
    Save it and go back
    Go to Edit -> Set release
    Create Message Type
    Go to transaction code WE81
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter
    Click New Entries to create new Message Type
    Fill details
    Save it and go back
    Assign Message Type to IDoc Type
    Go to transaction code WE82
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.
    Click New Entries to create new Message Type.
    Fill details
    Save it and go back
    Check these out..
    Re: How to create IDOC
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    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
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    go trough 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
    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
    http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
    1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
    2.IDOCs are independent of the sending and receiving systems.
    3.IDOCs are independent of the direction of data exchange.
    The two available process for IDOCs are
    Outbound Process
    Inbound Process
    AND There are basically two types of IDOCs.
    Basic IDOCs
    Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
    Extended IDOCs
    Extending the functionality by adding more segments to existing Basic IDOCs.
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30)
    Create Message Type ( WE81)
    Assign Idoc Type to Message Type ( WE82)
    imp links
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    www.sappoint.com
    --here u can find the ppts and basic seetings for ALE
    http://sappoint.com/presentation.html
    www.sapgenie.com
    http://www.sapgenie.com/ale/index.htm
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    Try this..Hope this will help.
    >>>> SAP ALE & IDOC<<<<
    Steps to configuration(Basis) >>
    1. Create Logical System (LS) for each applicable ALE-enabled client
    2. Link client to Logical System on the respective servers
    3. Create background user, to be used by ALE(with authorizaton for ALE postings)
    4. Create RFC Destinations(SM59)
    5. Ports in Idoc processing(WE21)
    6. Generate partner profiles for sending system
    The functional configuration(Tcode: SALE)
    • Create a Customer Distribution Model (CDM);
    • Add appropriate message types and filters to the CDM;
    • Generate outbound partner profiles;
    • Distribute the CDM to the receiving systems; and
    • Generate inbound partner profiles on each of the clients.
    Steps to customize a new IDoc >>>
    1. Define IDoc Segment (WE31)
    2. Convert Segments into an IDoc type (WE30)
    3. Create a Message Type (WE81)
    4. Create valid Combination of Message & IDoc type(WE82)
    5. Define Processing Code(WE41 for OUT / WE42 for IN)
    6. Define Partner Profile(WE20)
    Important Transaction Codes:
    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
    BDM5 - Consistency check (Transaction scenarios)
    BD62 - Define rules
    BD79 - Maintain rules
    BD55 - Defining settings for IDoc conversion
    WEDI - ALE IDoc Administration
    WE21 - Ports in Idoc processing
    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
    Basic config for Distributed data:
    BD64: Maintain a Distributed Model
    BD82: Generate Partner Profile
    BD64: Distribute the distribution Model
    Programs
    RBDMIDOC – Creating IDoc Type from Change Pointers
    RSEOUT00 – Process all selected IDocs (EDI)
    RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
    RSARFCEX - Execute Calls Not Yet Executed
    RBDMOIND - Status Conversion with Successful tRFC Execution
    RBDMANIN - Start error handling for non-posted IDocs
    RBDSTATE - Send Audit Confirmations
    FOr testing you can use WE19.
    Regards
    Anji

  • Incomplete Idoc received in SAP R/3

    Hi XI Gurus
    I am working on a File to Idoc scenario and stuck because of a strange issue.
    The output Idoc structure sent from XI and as viewed in IDX5 / SXMB_MONI is as below
    <?xml version="1.0" encoding="UTF-8"?>
    <ACC_DOCUMENT01>
         <IDOC BEGIN="1">
              <EDI_DC40 SEGMENT="1">
                   <SNDPRT>LI_SND</SNDPRT>
                   <SNDPFC>LF_SND</SNDPFC>
                   <SNDPRN>0000000100</SNDPRN>
              </EDI_DC40>
              <E1BPACHE09 SEGMENT="1">
                   <OBJ_TYPE>BKPFF</OBJ_TYPE>
                   <OBJ_KEY>PR2000627830002007</OBJ_KEY>
                   <OBJ_SYS>T47CLNT800</OBJ_SYS>
                   <BUS_ACT>RFBU</BUS_ACT>
                   <USERNAME>lovein</USERNAME>
                   <COMP_CODE>3000</COMP_CODE>
                   <DOC_DATE>2007-09-11T05:18:52-07:00</DOC_DATE>
                   <PSTNG_DATE>2007-09-11T05:18:52-07:00</PSTNG_DATE>
                   <DOC_TYPE>SA</DOC_TYPE>
              </E1BPACHE09>
              <E1BPACCAHD/>
              <E1BPACGL09>
                   <ITEMNO_ACC>1</ITEMNO_ACC>
                   <GL_ACCOUNT/>
                   <ACCT_TYPE>S</ACCT_TYPE>
                   <DOC_TYPE>SA</DOC_TYPE>
                   <COMP_CODE>3000</COMP_CODE>
                   <PSTNG_DATE>2007-09-11T05:18:52-07:00</PSTNG_DATE>
                   <VENDOR_NO/>
              </E1BPACGL09>
              <E1BPACAP09>
                   <ITEMNO_ACC>00001</ITEMNO_ACC>
                   <VENDOR_NO/>
                   <COMP_CODE>3000</COMP_CODE>
                   <PYMT_METH>ach</PYMT_METH>
              </E1BPACAP09>
              <E1BPACCR09>
                   <ITEMNO_ACC>1</ITEMNO_ACC>
                   <CURR_TYPE>00</CURR_TYPE>
                   <CURRENCY>USD</CURRENCY>
                   <CURRENCY_ISO>USD</CURRENCY_ISO>
                   <AMT_DOCCUR>-30000</AMT_DOCCUR>
              </E1BPACCR09>
              <E1BPACCR09>
                   <ITEMNO_ACC>Constant</ITEMNO_ACC>
                   <CURR_TYPE>00</CURR_TYPE>
                   <CURRENCY>USD</CURRENCY>
                   <CURRENCY_ISO>USD</CURRENCY_ISO>
                   <AMT_DOCCUR>0</AMT_DOCCUR>
              </E1BPACCR09>
              <E1BPACCR09>
                   <ITEMNO_ACC>Constant</ITEMNO_ACC>
                   <CURR_TYPE>00</CURR_TYPE>
                   <CURRENCY>USD</CURRENCY>
                   <CURRENCY_ISO>USD</CURRENCY_ISO>
                   <AMT_DOCCUR>30000.00</AMT_DOCCUR>
              </E1BPACCR09>
         </IDOC>
    </ACC_DOCUMENT01>
    But the Idoc received in SAP R/3 as viewed in Transaction WE02 or table EDID4 has only one node E1BPACHE09
    and because rest of the nodes are missing SAP R/3 fails to process the Idoc .
    Any help to analyse the issue will be highly appreciated.
    Thanx
    Lovein

    Hi Lovein,
    What you can do is:
    1. Go to SXMB_MONI and take the output xml.
    2. Now go to your mapping under TEST tab and test the above mentioned output xml and see what is the output, i mean are you able to see all the desired output as per you mapping or not.
    3. If not then probabily you will get an error message, then try to find out the solution in your mapping only.
    4. If you are not able to do that, kindly send the error message, which you got in mapping.
    I hope this will solve your issue.
    Regards,
    Sarvesh
    ****Reward points, if found helpful. 

  • Variable substitution in receiver comm channel idoc - file

    Hello all,
    I have a error message in mys sytem XI for creating a file because I would like a file name create dynamically and use an info in this idoc providing system SAP.
    And this variable substitution I put file name schema %var1% and variable substitution
    var1 payload:ZBBPIV01,1,IDOC,1,E1BIVHD,1,IV_ID,1 and I have this message error
    and I set Disable security checks in my communication channel
    <b><?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Inbound Message
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapterFramework</SAP:Category>
      <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.MessagingException: Error during variable substitution: com.sap.aii.adapter.file.varsubst.VariableDataSourceException: The following variable was not found in the message payload: var1: com.sap.aii.adapter.file.configuration.DynamicConfigurationException: Error during variable substitution: com.sap.aii.adapter.file.varsubst.VariableDataSourceException: The following variable was not found in the message payload: var1</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error></b>
    Thanks for your help

    Hi,
    <b>ZBBPIV01,1,IDOC,1,E1BIVHD,1,IV_ID,1</b>
    Check if the target XML Contains a Field called <b>IV_ID</b> and does it have any value?.
    Btter option is to use Adapter Specific Attributes and the code excert in this link,
    http://help.sap.com/saphelp_nw04/helpdata/en/43/03612cdecc6e76e10000000a422035/content.htm
    Regards
    Bhavesh

  • Error in IDOC - File scenario

    Hi Experts,
    This is my error :
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
      <SAP:P1>INTEGRATION_SERVER_XID</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Unable to convert the sender service INTEGRATION_SERVER_XID to an ALE logical system</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    OTHER ERROR  FOR  PAYLOAD OF  SENDER PART IS AS BELOW :
    The XML page cannot be displayed
    Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.
    The character '>' was expected. Error processing resource 'file:///C:/Documents and Settings/ABC/Local Settings/Tempor...
    <?xml version="1.0" encoding="UTF-8" ?><ZZ/AFS/FUNACK><IDOC BEGIN="1"><EDI_DC40 SEGMENT="1"><TABN...
    Please Help,
    Regards,
    Study SAP

    Hi,
    The problem occurs when sender and receiver business system or business service does not have a logical system name.
    ID - Integration Directory
    Posting the IDOC'S into SAP R/3 System, sender and receiver business system or business service requires the logical system name. If the business system (Web As ABAP) does not have the logical system name, then add the logical system for business system.
    In technical system browser
    If business system type = Web AS ABAP, then add the Logical system in Technical System level and Save.
    If business system type = Third-Party, then add the logical system in business system level and Save.
    If the business service does not have the logical system name in ID, it needs to be configured as follows.
    Check the below screen shot which shows how to add the logical system for business service.
    Go to ID and click the Business service -> Services -> Adapter Specific Identifiers. Enter the logical system name and Save.
    Apply and activate.
    Hope this will help you.
    regards
    Aashish Sinha
    PS : reward points if helpful

  • FIle Content Conversion Problem in IDOC-XI-File Scenario

    Dear All,
    I am doing IDOC-XI-FILE scenario.
    I am facing one problem related to File Content Coversion.My requirement was to generate a dynamic file like <b>%store_code%_%current_date%_sitemaster.xml</b> , I have completed the dynamic generation successfully .
    Now there is slight change in the requirement ,<b>we have to suppress the current_date node of the xml content</b> . i have tried to suppress the current_date using these <b>DATE.fieldFixedLengths 0 , Date.fixedLengthTooShortHandling Cut</b> , But I am unable to suppress it Can some body provide me the details on this .
    The output xml version generated by Reciever file adapter is as below :
    <?xml version="1.0" encoding="UTF-8" ?>
    - <ns0:MT_SITE_MASTER xmlns:ns0="http://sample-xitest.com/sitemaster">
    - <SITE_DATA>
    <STORE_CODE>N002</STORE_CODE>
    <TITLE_MEDI>Company</TITLE_MEDI>
    <STORE_NAME>Mount Road</STORE_NAME>
    <STREET>Chennai</STREET>
    <COUNTRY>IN</COUNTRY>
    <SALES_TAX_NO>12345678910</SALES_TAX_NO>
    </SITE_DATA>
    </ns0:MT_SITE_MASTER>
    Plz provide me the code I have to write in the file content conversion .
    Thanks in advance
    Regards
    Prabhat

    If u see my earlier reply, I mentioned that u can not suppress the field from the one node.i.e Form SITE_DATA data type u can not suppress the field called CURRENT_DATE.
    My suggestion is that , modify the Data type in such a way that you will be having two nodes as I have mentioned earlier.  Then use the Suppress Logic for the Current Date.
    So it will look like this-
    <?xml version="1.0" encoding="UTF-8" ?>
    - <ns0:MT_SITE_MASTER xmlns:ns0="http://sample-xitest.com/sitemaster">
    - <SITE_DATA>
    <STORE_CODE>N002</STORE_CODE>
    <TITLE_MEDI>Company</TITLE_MEDI>
    <STORE_NAME>Mount Road</STORE_NAME>
    <STREET>Chennai</STREET>
    <COUNTRY>IN</COUNTRY>
    <SALES_TAX_NO>12345678910</SALES_TAX_NO>
    </SITE_DATA>
    <CURR_DATE>
       <CURRENT_DATE>20051105</CURRENT_DATE>
    </CURR_DATE>
    </ns0:MT_SITE_MASTER>
    So ur SITE_DATA is not having a field called CURRENT_DATE. This field is in separate node (segment ) called CURR_DATE. Now u can use the Suppress Logic for the same like this.
    CURR_DATE.fieldFixedLengths - 0
    CURR_DATE.fixedLengthTooShortHanling - Cut
    And in your Variable Substitution you can use the date from the other segment called CURR_DATE.
    Hope this solves ur problem.
    Regards,
    Moorthy

  • Problem in creatinga sales order idoc into XML file in the same appl server

    Hai....friends....
    I am tring to send an  sales order as iDOC  to a xml port in the same application server....
    1. have created a xml port with path..\usr\sap\RRM\SYS\global\.
    2. assigned it to logical system.
    3.Have a RFC destination of TCP/ip(LOCAL_EXEC)
    but in bd64 after creating  model view when i am generating partner profiles  a tRFC PORT has been automatically created.
    then finally the IDOc has been created but its saying....IDOC CANNOT OR SHOULD NOT BE SENT...
    Pls help me regarding this...
    thx,
    ram

    Hi Thanks for your updates,
    But I got the same error, while pass the data from abap into XML.
    error message,what I am getting is
    The XML page cannot be displayed
    Cannot view XML input using style sheet. Please correct the error and then click the Refresh button, or try again later.
    Invalid at the top level of the document. Error processing resource 'file:///C:/tempcustomers.xml'. Line 1, Position 1
    #<?xml version="1.0" encoding="utf-16"?>
    Thanks
    Gowrishankar

  • Error while ORDERS05 IDoc transfer from R3 - PI - SNC

    Hi Friends,
    I am facing error in PI SXMB_MONI for ORDERS05 IDoc transfer from R3 - PI - SNC.
    I have done all the configuration setup in Integration Directory for the Scenario, I am able to successfully send the IDOC for PO from R3 to PI but faced the following Error in PI.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Message Split According to Receiver List
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">PARTY_SERVICE</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      *<SAP:Stack>Party and service not defined</SAP:Stack>*
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Also I am unable to Configure Sender/Receiver ID in PI > SXMB_ADMIN > Configuration, as while defining Sender/Receiver  unable to add the Interface for Sender(ORDERS.ORDERS05)/Reciever(ReplenishmentOrderNotificatio_Out) although I am able to see the same in Integration Repository.
    Also In Main message(Part of the message) as shown below, I am able to see Vendor in PARTY Element of xml message for which I have created the PO
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Message Split According to Receiver List
      -->
    - <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SOAP:Header>
    - <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
      <SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
      <SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
      <SAP:MessageId>0050568F-24A0-1DDD-B9F5-3F6DD541FF93</SAP:MessageId>
      <SAP:TimeSent>2009-01-21T10:55:20Z</SAP:TimeSent>
    - <SAP:Sender>
      <SAP:Service>SAPECC6</SAP:Service>
      <SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">ORDERS.ORDERS05</SAP:Interface>
      </SAP:Sender>
    - <SAP:Receiver>
      <SAP:Party agency="SAPECC6" scheme="ALE#LI#LF">0000000006</SAP:Party>
      <SAP:Service />
      <SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">ORDERS.ORDERS05</SAP:Interface>
      <SAP:Mapping notRequired="Y" />
      </SAP:Receiver>
    Please Suggest the steps needs to be done for resolving the Issue.
    Thanks all...
    Regards,
    Nitin
    Edited by: Nitin Patil on Jan 21, 2009 12:18 PM

    Hi Nitin,
       I completed the configuraiton but the PO came in PI successfully but stuck in PI with error
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
      <SAP:P1>500</SAP:P1>
      <SAP:P2>Internal Server Error</SAP:P2>
      <SAP:P3>Error during parsing of SOAP header</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>HTTP server code 500 reason Internal Server Error explanation Error during parsing of SOAP header</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    can you please help what is the problem , I am not able to find out.
    Thanks,
    Menaga

Maybe you are looking for