IDoc to File - Error in Content Convertion?

Hi Guys!!
I am facing a problem.
I used to have an interfase working well, until i had to do a modification.
Scenario is iDoc to File
Header
num
Position
- - - - A
- - - - B
- - - - C
- - - - D
And now is
Header
- - - - num
Position
- - - - A
- - - - B
- - - - C (C is 1:unbound )
- - - - - - - C1
- - - - - - - C2
- - - - - - - C3
- - - - D
Since that, interfase does not workk anymore.
Any suggestion? Please!!
Thanks
Edited by: ademiv on Feb 9, 2012 1:03 PM

I am not facing mapping errors. Look!
http://img715.imageshack.us/img715/5932/20120209093317.png
With this before it was working
Header
num
Position
- - - - A
- - - - B
- - - - C
- - - - D
But now, with this structure is not working. Maaping is ok, i have already checked it.
Header
- - - - num
Position
- - - - A
- - - - B
- - - - C (C is 1:unbound )
- - - - - - - C1
- - - - - - - C2
- - - - - - - C3
- - - - D
Idea?

Similar Messages

IDOC to FIle Error

Hi,
IDOC to File Scenario
Sender 1 IDOC, Receiver 3 Interfaces ( Munti mapping)
Then iam getting this error in MONI
<SAP:Code area="IF_DETERMINATION">NO_IIF_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to find an inbound interface</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Regards,
Rok

Hi Rakesh,
Possibly i think solution for this would be :
Go to SLD >>administration>>Content Maintainance and link the correct software component to the businesas system .
Then refresh the SLD cache this will automatically reflect there.
Also check the following thread it will help u:
Error in interface determination wiht condition
Regards,
Vinod.

IDOC to File --- Error occurred during back-routing Error in communication

Hi All,
I am doing a IDOC to File (File Content Conversion) Scenario in which I have mentioned the field separator and end separator.. When i trigger the IDOC, i am only getting the first field value in the output. I am getting the following error
"- <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="OUTBINDING">CO_TXT_ROUTING_BACK_ERROR</SAP:Code>
<SAP:P1>,IHS_BS</SAP:P1>
<SAP:P2>,com_IHS_B07_BS,,</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error occurred during back-routing Error in communication channel</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>"
My port and receiver are mentioned in "IDXNOALE" so that I can ignore the Acknowledgments. Please help as the error still persists..
Thanks
Anju

Try this thread:
ALEAUD not coming to SAP from XI & u0093Acknowledgment not possible" in idx5

Idoc to File scenario: receiver content conversion

Hi,
I have a Idoc to file scenario in which each segment is to be sent in a new line.
Also, even if the segment is not present in Idoc, comma separated blank values are to be sent.
Till now I have been fllowing this blog
File Content Conversion for Multi Hierarchical Structure
But in this case, blank values csv line are not created.
When I used mapWithDefault for parent WPA12 then only 1 instance is created.
For eg.
WPA01
-WPA02
--WPA12
WPA01
-WPA02
--WPA12
There are no values in WPA12 segment
Output
WPA01,a,a,a,a
WPA02,b,b,b,b
WPA12,,,,,
WPA01,c,c,c,c
WPA02,d,d,d,d
Can I make any change in the approach as in the blog to get the desired output?
Regards,
Anirudh.

Hi,
To explain more a bit..
My requirement is to create a flat file from multiple hierarchical xml structure.
Additionally, if the values are not present for some nodes then also I have to send the blank values in flat files. If entire segment is not present then also blank csvs needed to be sent.
regards, Anirudh.

IDOC to FILE-Error during STOR/APPE epilogue

Hi all
I am doing IDOC to File scenario. When trying to save the file in FTP path it throwing error like
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error occurred while connecting to the FTP server java.lang.IllegalStateException: Error during STOR/APPE epilogue: com.sap.aii.adapter.file.ftp.FTPEx: 221 Scanning for virus Transfer complete.

s i can able to connect FTP server from PI server...But it showing some message like
GSSAPI error minor: Unknown code krb5 195
GSSAPI error: initializing context
GSSAPI authentication failed
504 AUTH KERBEROS_V4 not supported.
KERBEROS_V4 rejected as an authentication type
But its getting connected..
Regards
Sathish

IDoc to File - error code 56

Hello,
I have configured the scenario for IDoc XI File. The IDoc from SAP system is triggered out properly, but at XI side by using we05 t-code i found that the IDoc received doesnot contain any data at all. The segment names have been changed and the error code is 56 and 60
56 status message is: External segment name & cannot be interpreted
60 status message is: Basic Type is missing.
I have checked the in idx2 the meta data have been imported properly and also verified the partner profile also both seems to fine.
Has anyone come across this situation, please do guide me to solve the issue.
Warm Regards
Ramesh P
Edited by: Ramesh P on Jul 17, 2008 6:43 PM

Thanks prateek for quick response!
The IDoc used is standard idoc WPDBBY.WPDBBY01.
and the cancel processing flag has been checked..
But still it error persists.. i am still able to see inbound idocs in we05 XI side, most of them told that in this scenario you wont be able to see it in we05 XI side. Then how to go about...
Edited by: Ramesh P on Jul 18, 2008 11:32 AM

File adapter sender content Convertion

Hi all,
I need to read a flat file and convert it,
The file structure is a long row with different types of segments:
For example:
AA111222333BB4455
where AA - the first segment and BB the second segemnt,
I want to convert this string to -
<AA>
<first>111<first/>
<second>222<second/>
<third>333<third/>
<AA/>
<BB>
<first>44<first/>
<second>55<second/>
<BB/>
I tried impliment this by using endSeparator and beginSeparator as AA,BB, but I get an error -
Conversion of file content to XML failed at position 0: java.lang.Exception: ERROR consistency check in recordset structure validation (line no. 1: missing structure(s) in last recordse
anyone????????
Thanks,
Naama

hi,
Declare the message type as:
mt
*record
    **AA      1
      ***key 0..1
      ***first
      ***second
      ***third
   **BB      1
     ***key 0..1
     ***first
     ***second
content conversion parameters:
Document Name: mt
Document Namespace:http://xxxxx
Document Offset:
Recordset Name: record
Recordset Namespace:
Recordset Structure:AA,1,BB,1
Recordset Sequence:Ascending
Recordsets per Message:1
KeyField Name:key
KeyField Type:String(Case-Sensitive)
Additional Parameters:
AA.fieldFixedLengths 1,3,3,3
AA.fieldnames key,first,second,third
AA.keyFieldValue 1
AA.keyFieldinStructure ignore
ignorerecordsetname true
BB.fieldFixedLengths 1,2,2
BB.fieldnames key,first,second
BB.keyFieldValue 2
BB.keyFieldinStructure ignore
Thanks,
Durga
Edited by: NagaDurga Nannapaneni on Sep 8, 2008 1:11 PM
Edited by: NagaDurga Nannapaneni on Sep 8, 2008 1:15 PM

Receiver Determination error - IDOC TO FILE

Hi ,
    Scenario : IDOC TO File
     Error generated while iam doing this scenario. Please help me.
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Regards,
Venubabu.

Hi
Check for sender details . Sender interface must be the IDOC.
Open SXMB_MONI and check your msg fro the sender system details. They match exactly the details in Receiver Determination.
Check the Receiver Determination is configured correctly. i.e R/3
Verify all the configurations like SM59, Partner Profile/Logical systems. etc. Also check in SM58 of R/3 system.Make sure that All the objects are activated in the Directory.Refresh the cache.Verify is the business system is pointing to correct R/3 system . Go to Business system/Service->Menu->Adapter specific identifiers in the directory
You can test your configuration with sample
payload.
In ID goto to TOOLS -
> Test Configuration for testing.
Hope in this way you can still find at which point the interface goes wrong

Error/Doubts in Idoc-XI-File scenario

Dear All,
I am doing one scenario in which DELIVERY idoc is posted from R/3 to XI and then from XI that idoc is to be sent as flat file to one local folder.
For this scenario, I have done all ALE settings and I am able to see the idoc in XI in cXML format.Now I want to sent it as flat file.
Now, for doing this I created 2 BS & 2 TS. 1 BS & TS of type Third Party for receiver & 1 BS & TS are of type Web as ABAP for sender. Then I have created one namespace in IR. I have not created any DT, MT, MI, MM becoz the structure of source and target file are same. Now, I created one IM in which I specified specified Type as "ABAP Class" & Mapping program name as one of the Z function module as specified in one of the SAP Guides.
Then in ID, I created 2 Parties ie. one for Sender & one for receiver. Sender is having a communication channel of type Idoc & receiver is having communication channel of type File. And thn further Receiver Agreement, Inetrface Determination, Sender Agreement & Receiver Agreement are configured.
In my system there is one scenario already configured which is using Delivery idoc so I have used party in my scenario for both sender & receiver.
Now, when I am sending the idoc from R/3, I am able to see cXML in SXMB_MONI but it is taking receiver as the one which is defined for the already existing scenario but not the receiver defined by me.
Can anybody guide if I have followed the correct steps & where I am doing the error.
Warm Regards,
N.Jain

Hi ,
Plese refer the following blogs ,
IDoc to File
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
You have to do all this settings mentioned in the docuemnt:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&
Also can you check this weblogs on the same:
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
Thanks ,
Suvarna
Award pts if it helps .

How to suppress the Acknowledgement Error in IDOC to File scenario?

Hi -
I got the status in SXMB_MONI as 'Processed Successfully' for the IDOC to File scenario but the Acknoledgement status throws an error saying 'Acknowledgement not possible'.
I read one of the documents in the forums on how to suppress the acknowledgement using a table on R/3 side using IDXNOALE,
i tried that option but i still get the 'Acknowledgement not possible' error.
Is there any other way to suppress this error?
Thanks,
Tirumal

Hi Tirumal,
Receiver adapters that run on the Adapter Engine support system acknowledgments if they are requested by the sender. Acknowledgements are triggered when a message is successfully processed by the adapter or if an error occurs while it is being processed. Receiver adapters do not support application acknowledgments. The RNIF and CIDX adapters are exceptions to this rule, since they also support scenario-dependent application acknowledgments. Sender adapters of the Adapter Engine do not request any acknowledgments.
This means, JDBC adapter does only send system acks, however IDoc adapter is requesting application acks. Therefore as mentioned by the previous poster, you have to disable acks for this scenario using report IDX_NOALE.
Also go through these documents for any further help:
http://sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how to handle acknowledgments for idoc.pdf
http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
Regards,
abhy

IDoc to File, SM58 shows error, ST22 short dump - Runtime error

Hi friends,
I am doing a simple IDoc to file scenario using the EVMSTA01 IDoc. My XI is running on client 100 and I am trying to send the IDoc from the client 200 on the same machine. I have completed the design and configuration steps required and also performed the required steps in Sender client (Sm59, we21 and BD54) and receiver client (Sm59, IDX1 and IDX2).
When I tried sending the IDoc from WE19, status meesage says that, the IDoc has been successfully sent to the receiver but SM58 shows error "IDOC_ERROR_WORKFLOW_START_R". When I looked in to ST22, there was a short dump with the below message -
Runtime Errors         MESSAGE_TYPE_X
Date and Time          18.10.2008 23:24:29
ShrtText
     The current application triggered a termination with a short dump.
What happened?
     The current application program detected a situation which really
     should not occur. Therefore, a termination with a short dump was
     triggered on purpose by the key word MESSAGE (type X).
Error analysis
     Short text of error message:
     Unable to read RFC destination WORKFLOW_LOCAL_200
     Technical information about the message:
     Message classe...... "SWF_RUN"
     Number.............. 617
     Variable 1.......... "WORKFLOW_LOCAL_200"
     Variable 2.......... "RFC_READ_DESTINATION_TYPE"
     Variable 3.......... "DESTINATION_NOT_EXIST"
     Variable 4.......... " "
     Variable 3.......... "DESTINATION_NOT_EXIST"
     Variable 4.......... " "
Trigger Location of Runtime Error
     Program                                 CL_SWF_RUN_WIM_LOCAL==========CP
     Include                                 CL_SWF_RUN_WIM_LOCAL==========CM07Z
     Row                                     10
Module type                             (METHOD)
Module Name                             IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER
rce Code Extract
e SourceCde
1 METHOD if_swf_run_wim_utl_internal~get_system_user .
2   DATA: l_excp TYPE REF TO cx_swf_run_wim.
3
4   TRY.
5       IF me->m_int_state-system_user IS INITIAL.
6         me->m_int_state-system_user = cl_swf_run_workflow_properties=>get_rfc_destination_us
7       ENDIF.
8       re_user = me->m_int_state-system_user.
9     CATCH cx_swf_run_wim INTO l_excp.
>>       MESSAGE ID     l_excp->t100_msg-msgid
11               TYPE   'X'
12               NUMBER l_excp->t100_msg-msgno
13               WITH   l_excp->t100_msg-msgv1 l_excp->t100_msg-msgv2
14                      l_excp->t100_msg-msgv3 l_excp->t100_msg-msgv4.
15   ENDTRY.
16
17 ENDMETHOD.                    "
Any help would be appreciated..!!
PS: Points would be assigned to all the helpful replys without fail

Hi,
See check for RFC destination and it is working as per your configuration or not , i mean , it is trying to locate remote server.. , so try to check in sm59, remote login and the respective result is going to your required client or not ??
Also see the further errors while doing Idoc related scenarios..
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133 - Idocs not reaching XI. Not posted in the receiver SAP
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
idoc erros - http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
idoc mapping - /people/james.guanzon/blog/2006/03/23/how-to-support-industry-standards-in-xi-part-ii-of-iii--mapping
IDoc erros troubleshooting - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
Regards
Chilla

Idoc-to-File Scenario ATTRIBUTE_INV_SND_SERV Error

Hi All,
I am working on PI 7.1. I have an Idoc-to-File scenario. The scenario is working fine, but there is an error
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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>FILE_BC</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Unable to convert the sender service FILE_BC to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
PI is trying to send an acknowledgment back to the Sender ECC system. But in the IDX_NOALE, 'Do not request acknowledgement' is already checked. Still there is this error. It doesnt show up in MONI unless the Acknowledgement message is clicked, but alerts are getting triggered for these cases. Can anybody please help me in resolving this? I do not want the acknowledgements to be sent back to the ECC system.
Thanks,
Geetha

Thanks everybody! It has got fixed. I just requested No acknowledgements.
Geetha
Edited by: Geetha on Nov 11, 2009 5:45 PM

IDOC to file scenario testing error --

Hi experts ,
When doing an IDOC to file scenario the status of the IDOC in XI (the Trace section @ SXMB_MONITOR) shows that
PARTY &SERVICE NOT DEFINED
the failure occurs at message splitting stage .
more details :
the sender is represented as a business system
the receiver has no party and has only a business service
By chance when i tried to check message status in INTEGRATION ENGINE @ RWB
i was able to find that XI is trying to send the mesasage to Receiver with party name 12345 this 12345 is the same which i gave in we20 as the partner number .
What could be the reason ?

This is the error
Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="1" type="T">...There is no Interface Determination configured for receiver party 0000002569 and receiver service</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) 0000002569 DELINS.DELFOR01</Trace>

AckRequestNotSupported error in IDoc to file scenario

Hi,
I have a scenario from IDoc to file adatper, when i try to run this scenario, every thing is ok except there is a error in message monitor.
This error is regarding the Acknowledgment("Acknowledgment not possible"), But the ALEAUD IDoc have been sent to the orignal sender (IDoc side) with the empty content except the Header segment such as sender name, receiver name etc.
And when i tracted the detail information in message monitor, i got the following error information.
*<SAP:Status>AckRequestNotSupported</SAP:Status>*
*<SAP:Category>permanent</SAP:Category>*
I also went through some weblog and artical, i didn't got the solution.
If some body also have this error?
thanks & Best regards
Rocky
Following is My acknowledgment error information: FYI
*<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>*
*- 
- <SAP:Ack xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1" applicationAckNotSupported="true" applicationErrorAckNotSupported="true">
<SAP:Status>AckRequestNotSupported</SAP:Status>
<SAP:Category>permanent</SAP:Category>
</SAP:Ack>
Outbound Acknowledgment content:
- <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>030</SAP:MANDT>
<SAP:DOCREL>700</SAP:DOCREL>
<SAP:DOCNUM>0000000000036022</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>ALEAUD01</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>ALEAUD</SAP:MESTYP>
<SAP:MESCOD />
<SAP:MESFCT />
<SAP:SNDPOR>SAPO01</SAP:SNDPOR>
<SAP:SNDPRN>A01CLNT030</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:SNDPFC />
<SAP:RCVPOR>SAPO05</SAP:RCVPOR>
<SAP:RCVPRN>A05CLNT231</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
<SAP:RCVPFC />
<SAP:TEST />
<SAP:SERIAL />
<SAP:EXPRSS />
<SAP:STD />
<SAP:STDVRS />
<SAP:STATUS>03</SAP:STATUS>
<SAP:OUTMOD />
<SAP:SNDSAD />
<SAP:SNDLAD />
<SAP:RCVSAD />
<SAP:RCVLAD />
<SAP:STDMES />
<SAP:REFINT />
<SAP:REFGRP />
<SAP:REFMES />
<SAP:CREDAT>0000-00-00</SAP:CREDAT>
<SAP:CRETIM>00:00:00</SAP:CRETIM>
<SAP:ARCKEY />
</SAP:IDocOutbound>

Hi Rocky,
Check the below links of setting up of ALEAUDUT RESPONSE:
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
Check this document on handling IDOC acknowledgements. This might give you some idea.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
Please check the above two links if u have missed anything in setting up the acknowledgement.Let me know if u need furthur information
Thanks,
Bhargav.
Note:Award points if found useful.

Seeburger IDOC-to-File scenario: Error using Classifier module

Hello,
I am running the following scenario: ORDERS.ORDERS05 IDOC -> XI -> X12 850 4010 File.
In the file receiver channel, I am using Seeburger's Classifier and BIC modules as follows:
localejbs/SeeClassifier        classifier
localejbs/CallBicXIRaBean      bic
CallSapAdapter                 0
classifier   attID             classifierAtt
classifier   destSourceMsg     MainDocument
classifier   showInAuditLog    true
bic          classifierAttID   classifierAtt
bic          destEncoding      UTF8
bic          destSourceMsg     MainDocument
bic          destTargetMsg     MainDocument
bic          mappingName       AUTO
bic          newLine           true
bic          srcEncoding       UTF8
After conversion in XI, the file fails to write to the folder because of this error:
Message processing failed. Cause: javax.resource.ResourceException: ---
Conversion of synchronous request from module chain ended with errors
---Error: [Error:ID=1010;LEVEL=1] BICMapping runMapping() The mapping:
See_XML_AnsiX12 you are trying to load cannot be found in the classpath!
Maybe you forgot to compile or to activate the mapping! DESCRIPTION:
BICMapping Error: The mapping [not specified] you are trying to load cannot
be found in the right path! Maybe you forgot to compile or to activate the
mapping!
When I set the mapping directly to See_X2E_AnsiX12_850_V4010 instead of using the Classifier module, the configuration works fine. But I want to design the receiver channel to be able to receive all types of EDI messages coming from XI.
I am only facing this problem for the IDOC-to-File scenario. Somehow the same configuration works for a File-to-IDOC scenario.
I talked to our Basis team and they said that the map See_XML_AnsiX12 does not exist in Seeburger's delivered content, although I believe that it should be. Has anyone encountered this problem before?
Any suggestions would be appreciated.
Thanks,
Arianne

Hi Yomesh,
Here is the payload.
<?xml version="1.0" encoding="UTF-8"?>
<LIST>
<S_ISA>
    <D_I01>00</D_I01>
    <D_I02/>
    <D_I03>00</D_I03>
    <D_I04/>
    <D_I05>ZZ</D_I05>
    <D_I06>CELORGS01</D_I06>
    <D_I05_2>ZZ</D_I05_2>
    <D_I07>AVX</D_I07>
    <D_I08>032008</D_I08>
    <D_I09>1718</D_I09>
    <D_I10>X</D_I10>
    <D_I11>00401</D_I11>
    <D_I12>000000008</D_I12>
    <D_I13>0</D_I13>
    <D_I14>T</D_I14>
    <D_I15>^</D_I15>
    <S_GS>
      <D_479>PO</D_479>
      <D_142>CLS01</D_142>
      <D_124>058895921</D_124>
      <D_373>20080320</D_373>
      <D_337>1718</D_337>
      <D_28>8</D_28>
      <D_455>X</D_455>
      <D_480>004010</D_480>
      <S_ST>
        <D_143>850</D_143>
        <D_329>800001</D_329>
        <S_BEG>
          <D_353>00</D_353>
          <D_92>SA</D_92>
          <D_324>4500005037</D_324>
          <D_373>20051110</D_373>
        </S_BEG>
        <S_CUR>
          <D_98>BY</D_98>
          <D_100>USD</D_100>
        </S_CUR>
        <S_FOB>
          <D_146>CC</D_146>
          <D_309>OR</D_309>
          <D_352>FREE CARRIER</D_352>
          <D_334>02</D_334>
          <D_335>FOB</D_335>
          <D_309_2>DE</D_309_2>
        </S_FOB>
        <S_ITD>
          <D_336>01</D_336>
          <D_333>3</D_333>
          <D_351>45</D_351>
        </S_ITD>
        <G_SN9>
          <S_N9>
            <D_128>L1</D_128>
            <D_369>GEN</D_369>
            <S_MSG>
              <D_933>TEST</D_933>
            </S_MSG>
            <S_MSG>
              <D_933>MESSAGE</D_933>
            </S_MSG>
          </S_N9>
        </G_SN9>
        <G_SN1>
          <S_N1>
            <D_98>BY</D_98>
            <D_66>92</D_66>
            <D_67>6310</D_67>
            <S_PER>
              <D_366>BD</D_366>
              <D_93>Graham Crawford</D_93>
            </S_PER>
          </S_N1>
        </G_SN1>
        <G_SN1>
          <S_N1>
            <D_98>BT</D_98>
            <D_66>92</D_66>
            <D_67>6310</D_67>
          </S_N1>
        </G_SN1>
        <G_SN1>
          <S_N1>
            <D_98>SE</D_98>
            <D_93>3M COMPANY</D_93>
            <D_66>92</D_66>
            <D_67>0000019591</D_67>
          </S_N1>
        </G_SN1>
        <G_SN1>
          <S_N1>
            <D_98>ST</D_98>
            <D_93>SAMPLE</D_93>
            <D_66>92</D_66>
            <D_67>6310</D_67>
          </S_N1>
        </G_SN1>
        <G_SPO1>
          <S_PO1>
            <D_350>00010</D_350>
            <D_330>10.000</D_330>
            <D_355>EA</D_355>
            <D_212>10</D_212>
            <D_639>PE</D_639>
            <D_235>BP</D_235>
            <D_234>230-1812-01JDS</D_234>
            <D_235_2>EC</D_235_2>
            <D_234_2>A00000000000002</D_234_2>
            <G_SPID>
              <S_PID>
                <D_349>F</D_349>
                <D_352>TIE WRAP,LOCKING,PANDUIT-PLASTIC PART C</D_352>
              </S_PID>
            </G_SPID>
            <S_REF>
              <D_128>CO</D_128>
              <D_127>4500005037-00010</D_127>
            </S_REF>
            <G_SSCH>
              <S_SCH>
                <D_380>10.000</D_380>
                <D_355>EA</D_355>
                <D_374>002</D_374>
                <D_373>20051208</D_373>
              </S_SCH>
            </G_SSCH>
          </S_PO1>
        </G_SPO1>
        <G_SCTT>
          <S_CTT>
            <D_354>1</D_354>
          </S_CTT>
        </G_SCTT>
        <S_SE>
          <D_96/>
          <D_329>800001</D_329>
        </S_SE>
      </S_ST>
      <S_GE>
        <D_97>1</D_97>
        <D_28>8</D_28>
      </S_GE>
    </S_GS>
    <S_IEA>
      <D_I16>1</D_I16>
      <D_I12>000000008</D_I12>
    </S_IEA>
</S_ISA>
</LIST>
Thanks,
Arianne

IDoc to File - Error in Content Convertion?

Similar Messages

Maybe you are looking for