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.

Similar Messages

FIle Adapter Receiver - Content Conversion

I have a xml file as below that I am trying to convert to a simple csv file. All I get is a blank csv file at the ouptput. I tried different setting for the file conversion in the reveiver file adapter. No luck yet. I could write to an output XML file with no problem, so my interface is working!
The SAP Help doesn't provide much info on this. Your help is highly appreciated.
Thnaks.
?xml version="1.0" encoding="UTF-8" ?>
- <ns:PlantMaintenanceMessageType xmlns:ns="http://cs.par/demo/plantmaintenance">
<EquipmentID>10005661</EquipmentID>
<FunctionalLocation>KB</FunctionalLocation>
<Date />
<Time />
</ns:PlantMaintenanceMessageType>

What is your root node ?
For your content conversion you need to specify the Recordset Structure but in your case i dont find an entry for the same.
If your XML had an extra tag like
xml version="1.0" encoding="UTF-8" ?>
- <ns:PlantMaintenanceMessageType xmlns:ns="http://cs.par/demo/plantmaintenance">
<details>
<EquipmentID>10005661</EquipmentID>
<FunctionalLocation>KB</FunctionalLocation>
<Date />
<Time />
</details></ns:PlantMaintenanceMessageType>
then your record set structure wud be details
and in you content conversion parameters you cud say
details.fieldSeparator -> ,
details.endSeparator 'nl'
I guess you are on sp13 or above hence there even if you content conversion fails a blank file will be created (thats what i have experienced).
Reagrds,
ShaBZ

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 %store_code%_%current_date%_sitemaster.xml , I have completed the dynamic generation successfully .
Now there is slight change in the requirement ,we have to suppress the current_date node of the xml content . i have tried to suppress the current_date using these DATE.fieldFixedLengths 0 , Date.fixedLengthTooShortHandling Cut , 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

FCC in receiver side in idoc to file scenario

Hi all,
           I am doing an idoc to file scenario using FCC .I am using FCC in receiver side ,but i am getting my output file in only one line while i want structre to be seprated by new line.for more information i am giving muy file structre.
Record
    header(1to1)
    data    (0 to unbounded)
    footer (1to 1)          header, data, footer are three structre which contain various fields.I have to use fieldFixedLengths as filed separator. I am also using endseperator as 'nl' but its not coming in new line.Please share ur views on this issue.
Regards
Neha

hi neha,
In your scenario
Recordset Structure header,data,footer
header.fieldFixedLengths    = 1,2,3, whatever it is
data.fieldFixedLengths      = similar to header
footer.fieldFixedLengths    = similar to header
header.endSeparator = 'nl'
data.endSeparator = 'nl'
footer.endSeparator = 'nl'
I guess you dont have to do any thing else.
Regards
Pushkar
Message was edited by:
        Pushkar Anand

Getting Receiver Agreement issue in IDOC to File scenario

Hi Gurus,
 Need your help. I'm working on a IDOC to File scenario. I'm using CREMDM.CREMDM04 as outbound Interface & small structure VEND_FILE_IN_MI as Inbound Interface. Though I've configured the receiver Communication Channel as a File Adapter with proper Inbound Interface I'm seeing the message getting failed which is showing CREMDM.CREMDM04 as both Outbound & Inbound interface and pointing a Receiver Agreement issue . The Receiver service is coming Properly, only the Interface is coming wrong as the sender interface. I've checked both Receiver Agreement & Receiver determination and found the Receiver Service, Communication Channel & Interface are perfectly mapped there, I cross checked the same Configurations in IE via SXI_CACHE after full Cache copy.
Error Message:
No receiver agreement found for sender -SAPERP to receiver -IDOC2FileReceiver,urn:sap-com:document:sap:idoc:messages
Error Category : Outbounding
Error ID : CO_TXT_OUTBINDING_NOT_FOUND
My IR design:
Sender:
 Interface : VEND_IDOC_OUT_MI
 Message Type : CREMDM.CREMDM04
Receiver:
 Interface : VEND_FILE_IN_MI
 Message Type : VEND_IN_MT , Data Type VEND_FILE_DT
My ID Config:
1. Sender / Outbound Message: Service Type --> Business System
 Service ---> SAPERP
 Interface--> VEND_IDOC_OUT_MI
 Adapter Type : IDOC
2. Receiver / Inbound Message: Service Type --> Business Service
 Service --> IDOC2FileReceiver
 Interface ---> VEND_FILE_IN_MI
 Adapter Type--> File
3. In Sender Agreement : Specified the Sender Communication Channel
 VEND_IDOC_OUT_Channel
4. In Receiver Agreement Configured the receiver service IDOC2FileReceiver aging sender service SAPERP & Interface VEND_IDOC_OUT_MI.
5. In Interface Determination Specified the Inbound Interface VEND_FILE_IN_MI and Interface Mapping VEND_IDOC_FILE_IMAP
6. In Receiver Agreement specified the receiver communication Channel IDOC2FileChannel against Receiver Service & Interface.
I used the Configuration wizard in my second attempt to make sure the sequence of configuration.
Can anyone help me identifying what's going wrong. I'm very new to XI and basically this is the first assignment I'm working on.
Regards,
Subhadip

Hi Babu,
 In the Inbound data type all the fields have MinOccurance = 0 and MaxOccurances unbounded.
Please find the XSD:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://adc.com/poc/sample" targetNamespace="http://adc.com/poc/sample">
 <xsd:complexType name="VEND_FILE_DT">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 8f584d80456311dccd680018fe79f69b
 </xsd:appinfo>
 </xsd:annotation>
 <xsd:sequence>
 <xsd:element name="VENDCODE" minOccurs="0" maxOccurs="unbounded">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 a8653cb0390c11dc843000188bd09370
 </xsd:appinfo>
 <xsd:documentation xml:lang="EN">
 Vendor Code
 </xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:minLength value="0" />
 <xsd:maxLength value="50" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="VENDNAME1" minOccurs="0" maxOccurs="unbounded">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 a8653cb4390c11dc84e800188bd09370
 </xsd:appinfo>
 <xsd:documentation xml:lang="EN">
 Vendor name4
 </xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:minLength value="0" />
 <xsd:maxLength value="50" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="ORT01" minOccurs="0" maxOccurs="unbounded">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 a8653cb5390c11dcbe3400188bd09370
 </xsd:appinfo>
 <xsd:documentation xml:lang="EN">
 Vendor City
 </xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:minLength value="0" />
 <xsd:maxLength value="50" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="PFACH" minOccurs="0" maxOccurs="unbounded">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 a8653cb6390c11dc896100188bd09370
 </xsd:appinfo>
 <xsd:documentation xml:lang="EN">
 Vendor PO Box
 </xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:minLength value="0" />
 <xsd:maxLength value="50" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="STRAS" minOccurs="0" maxOccurs="unbounded">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 4811db0335fd11dc9e9600188bd09370
 </xsd:appinfo>
 <xsd:documentation xml:lang="EN">
 Vendor House No & Street
 </xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:minLength value="0" />
 <xsd:maxLength value="50" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="PSTLZ" minOccurs="0" maxOccurs="unbounded">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 4811db0435fd11dc98b000188bd09370
 </xsd:appinfo>
 <xsd:documentation xml:lang="EN">
 Vendor Postal Code
 </xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:minLength value="0" />
 <xsd:maxLength value="50" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="LAND1" minOccurs="0" maxOccurs="unbounded">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 4811db0535fd11dc870500188bd09370
 </xsd:appinfo>
 <xsd:documentation xml:lang="EN">
 Vendor Country
 </xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:minLength value="0" />
 <xsd:maxLength value="50" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="STCD1" minOccurs="0" maxOccurs="unbounded">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 7ca8d600403b11dcc9bd00188bd09370
 </xsd:appinfo>
 <xsd:documentation xml:lang="EN">
 Tax Number 1
 </xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:minLength value="0" />
 <xsd:maxLength value="50" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="TELF1" minOccurs="0" maxOccurs="unbounded">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 9abaee7040e611dcce4300188bd09370
 </xsd:appinfo>
 <xsd:documentation xml:lang="EN">
 Telephone number
 </xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:minLength value="0" />
 <xsd:maxLength value="50" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="STCEG" minOccurs="0" maxOccurs="unbounded">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 9abaee7140e611dc8f3900188bd09370
 </xsd:appinfo>
 <xsd:documentation xml:lang="EN">
 VAT Registration Number
 </xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:minLength value="0" />
 <xsd:maxLength value="50" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="LIFNR" minOccurs="0" maxOccurs="unbounded">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 9abaee7240e611dccef700188bd09370
 </xsd:appinfo>
 <xsd:documentation xml:lang="EN">
 Account Number of Vendor or Creditor
 </xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:minLength value="0" />
 <xsd:maxLength value="50" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="ALTKN" minOccurs="0" maxOccurs="unbounded">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 9abaee7340e611dcb3bc00188bd09370
 </xsd:appinfo>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:minLength value="0" />
 <xsd:maxLength value="50" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 </xsd:sequence>
 </xsd:complexType>
</xsd:schema>

Complex file receiver content conversion

Hi
My challenge is to change this xml structure to a flat file structure using content conversion in a file receiver adapter. My problem is, that I have a record within a record and both records can occur multiple times:
<statusUpdate_response>
 <ProcessID/>
 <SenderSystem/>
 <Results>
 <ResultList> (0..unbound)
 <OKKode/>
 <Reference/>
 <Result/>
 <ResultDetail> (0..unbound)
 <TYPE/>
 <ID/>
 <NUMBER/>
 </ResultDetail>
 </ResultList>
 </Results>
</statusUpdate_response>
Any suggestions?
Maybe some sort of xml flattener before doing the content conversion would do the trick, but then again how is that to be done?
BR MIkael

a small trick might help - /people/shabarish.vijayakumar/blog/2010/01/14/file-conversion-using-nodeception
Also do read - /people/shabarish.vijayakumar/blog/2007/08/03/file-adapter-receiver--are-we-really-sure-about-the-concepts

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

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 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>

IDOC to File Scenario - Configuration steps need to be done in R3 and XI

Hi Experts,
I am working with IDoc to File scenario. Can someone please explain, what are the steps or configuration things need to be done in R3 and as well as in XI too.
Thanks in advance.
Regards,
Sree

Hi Sree,
I thought i will just share a few basic thoughts that you need to take care while doing an IDOC to File Scenario. Just see if it helps you in anyways.
While doing an IDOC -> XI -> File scenario, The Points to noted are:
1. You dont need a DT, MT or a message interface for the IDOC as it itself acts as the Message Interface.
2. You import the IDOC and use the same in your mapping.
3. In this configuration note that you dont have a sender agreement as you dont have a sender IDOC adapter.
If it is that you wanted to send an IDOC from XI (File to IDOC) , then in this case:
points 1 and 2 will remain, but the 3 will not. You will need a sender agreement for the file and a receiver agreement for the IDOC.
IDOC -> File scenario ref:
<a href="/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters scenario</a>
File -> IDOC ref:
<a href="/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping to IDOC</a>
To be able to trigger your IDOC from the SAP ISU system, you will have to set the partner profile in we20. Select your Business System (mostly under Logical system) and then create Outbound entries for whichever IDOC you want to trigger.
You define your basic type also in your partner profile settings, Please go thru the following links to get a better idea about partner profile:
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b833243d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7cd343d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/32/692037b1f10709e10000009b38f839/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5e/b8f8bf356dc84096e4fedc2cd71426/frameset.htm
Also, I would suggest that you go through this blog by michal if any issue arises,
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
Also have a look at these forum threads...
IDOC TO FILE SCENARIO
idoc to file scenario
I hope this answers your query.
Regards,
Abhy Thomas

Setup for IDoc-XI-File scenario

Hi All,
Please provide info where can I find, step by step documentation for the basic setup on R/3 and XI areas, before start developing IDoc-XI-File or File-XI-IDoc scenarios.
Thank you,
Sree

Hi,
While doing an IDOC -> XI -> File scenario, The Points to noted are:
1. You dont need a DT, MT or a message interface for the IDOC as it itself acts as the Message Interface.
2. You import the IDOC and use the same in your mapping.
3. In this configuration note that you dont have a sender agreement as you dont have a sender IDOC adapter.
If it is that you wanted to send an IDOC from XI (File to IDOC) , then in this case:
points 1 and 2 will remain, but the 3 will not. You will need a sender agreement for the file and a receiver agreement for the IDOC.
IDOC -> File scenario ref:
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
File -> IDOC ->
/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
(It concentrates on XSLT mapping but also gives an idea about the configuration part. Do go thru that, it might help you.)
To be able to trigger your IDOC from the SAP ISU system, you will have to set the partner profile in we20. Select your Business System (mostly under Logical system) and then create Outbound entries for whichever IDOC you want to trigger.
You define your basic type also in your partner profile settings, Please go thru the following links to get a better idea about partner profile:
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b833243d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7cd343d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/32/692037b1f10709e10000009b38f839/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5e/b8f8bf356dc84096e4fedc2cd71426/frameset.htm
Also, I would suggest that you go through this blog by michal if any issue arises,
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
I hope I have answered your query.
Regards,
Abhy
PS: AWARD POINTS FOR HELPFUL ANSWERS.

Doubt in idoc 2 file scenario

Hi,
I want to create idoc 2 file scenario with out any Transformation.
In that case how/what to create Data type for receiver.
I want to receive the same idoc in the receiver folder/Directory (like XML file) with out any transformation.
Thanks
Ruban

Hi,
For this scenario you need to create the Data type structures as similar to IDOC type and just have to transfer to file without FCC.
It will transfer the IDOC data as it is in XML format
refer
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/error%2bhandling%2bin%2bfile-idoc%2bscenario
(Just avoid using FCC conversions on receiver file adapter in above scenarios)
Thanks
Swarup
Edited by: Swarup Sawant on Mar 24, 2008 6:15 PM

No message in found in XI in IDOC to FILE scenario

Hi everybody,
I am working on a scenario idoc to file. The idoc is sent sucessfully from R/3 , but I am not getting any message in message monitoring in XI.Can anybody help me on this?

Hi Bhagyashree,
Just see if the file is generated at the specified destination....
Meanwhile please go through the info below and cross check with what you have done...
i will just share a few basic thoughts that you need to take care while doing an IDOC to File Scenario. Just see if it helps you in anyways.
While doing an IDOC -> XI -> File scenario, The Points to noted are:
1. You dont need a DT, MT or a message interface for the IDOC as it itself acts as the Message Interface.
2. You import the IDOC and use the same in your mapping.
3. In this configuration note that you dont have a sender agreement as you dont have a sender IDOC adapter.
If it is that you wanted to send an IDOC from XI (File to IDOC) , then in this case:
points 1 and 2 will remain, but the 3 will not. You will need a sender agreement for the file and a receiver agreement for the IDOC.
IDOC -> File scenario ref:
<a href="/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters scenario</a>
File -> IDOC ref:
<a href="/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping to IDOC</a>
To be able to trigger your IDOC from the SAP ISU system, you will have to set the partner profile in we20. Select your Business System (mostly under Logical system) and then create Outbound entries for whichever IDOC you want to trigger.
You define your basic type also in your partner profile settings, Please go thru the following links to get a better idea about partner profile:
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b833243d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7cd343d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/32/692037b1f10709e10000009b38f839/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5e/b8f8bf356dc84096e4fedc2cd71426/frameset.htm
Also, I would suggest that you go through this blog by michal if any issue arises,
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
I hope this answers your query.
Regards,
Abhy

Context handling in message mapping for an IDoc to File Scenario

Hi,
Can somebody help me with this issue. I have an Idoc to file scenario. heres my idoc structure. Its a custom Idoc
Header (1..1)
Detail (0..Unbounded)
         DependentDetail (0...Unbounded)              Note: This dependentdetail is a subelement of Detail
Trailer(1...1)
I created my target structrure the same way as the Idoc structure.
My output is a simple text file. I need the output in this format
Header
Detail1
   Dependentdetail1
   DependentDetail2
   DependentDetail3
Detail2
   DependentDetail1
   Dependentdetail2
Detail3
Detail4
Trailer
Since the Detail and Dependent Detail records are unbounded .
But right now i m getting my output like this:
Header
Detail1
Detail2
Detail3
Detail4
Trailer
But the DependentDetail record in not showing up in the output file. I didnot do any context change in my mapping. So do I need to do any context handling??...If so can somebody explain me with this.
Thanks,
Adam
Edited by: hymanroth on Apr 29, 2011 11:11 PM

Thanks Kenneth foryour quick reply,
Yes, I see the payload for Dependent detail in SXMB_MONI. So as you said earlier there's a problem with my content conversion.
my content conversion is as follows:
Header.fieldNames
Header.fieldFixedLengths
Header.endSeparator
Detail.fieldNames
Detail.fieldFixedLengths
Detail.endSeparator
DependentDetail.fieldNames
DependentDetail.fieldFixedLengths
DependentDetail.endSeparator
Trailer.fieldNames
Trailer.fieldFixedLengths
Trailer.endSeparator
So As I told earlier. With the above content conversion. I am not able to get the Dependent detail record in my output file. So If there is a change in my content conversion can u check it and tell me where I went wrong.
Thanks,
Harsh
Edited by: hymanroth on May 2, 2011 7:03 PM

IDOC to FILE scenario With Screen shots

CAN YOU PLEASE SEND US THE DETAILS OF IDOC to FILE scenario With Screen shots and do the needful for me

Hi Surya,
I thought i will just share a few basic thoughts that you need to take care while doing an IDOC to File Scenario. Just see if it helps you in anyways.
While doing an IDOC -> XI -> File scenario, The Points to noted are:
1. You dont need a DT, MT or a message interface for the IDOC as it itself acts as the Message Interface.
2. You import the IDOC and use the same in your mapping.
3. In this configuration note that you dont have a sender agreement as you dont have a sender IDOC adapter.
If it is that you wanted to send an IDOC from XI (File to IDOC) , then in this case:
points 1 and 2 will remain, but the 3 will not. You will need a sender agreement for the file and a receiver agreement for the IDOC.
IDOC -> File scenario ref:
<a href="/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters scenario</a>
File -> IDOC ref:
<a href="/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping to IDOC</a>
To be able to trigger your IDOC from the SAP ISU system, you will have to set the partner profile in we20. Select your Business System (mostly under Logical system) and then create Outbound entries for whichever IDOC you want to trigger.
You define your basic type also in your partner profile settings, Please go thru the following links to get a better idea about partner profile:
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b833243d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7cd343d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/32/692037b1f10709e10000009b38f839/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5e/b8f8bf356dc84096e4fedc2cd71426/frameset.htm
Also, I would suggest that you go through this blog by michal if any issue arises,
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
Also have a look at these forum threads...
IDOC TO FILE SCENARIO
idoc to file scenario
I hope this helps.
Regards,
Abhy Thomas

Idoc to File scenario: receiver content conversion

Similar Messages

Maybe you are looking for