File to idoc interface

Hi SAP-Xi guru,
can u explain the purpose of FILE TO IDOC ,IDOC TO FILE scenario.

Hi Kavitha,
In addition to above...
check my post in wiki for File to IDOc
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/fileToIDOC&
and for IDOC to file check these:
Introduction to IDoc-XI-File scenario and complete walk through for starters.
ALE configuration for pushing idocs from SAP to XI
Sachin

Similar Messages

Suggessions required for File----XI----Idoc Interface

Dear All,
I have developed File-XIIdoc Interface and works fine.
Query: When the Source application is trying to write the data into file, XI needs to wait until it completes
Once the writing is completed then only XI has to pickup the file from Source location.
If XI is not checking this check point, File adapter is picking up the file in the middle of the data writing itself.
Please suggest me your thoughts and experience on this
REgards
Suman

Hi Suman,
For writing a module please check the blog and articles in SDN.
The module logic should be as follows:
1. it should read and store intermeidiately the size & filenam of all files present in the folder.
2. do a wait of say 30 sec in the module (by sleep or any other such waiting command of java).
3. Then recheck the size of only those files read in step one (don;t read entire files present in folder now as some new files may have been created in this 30 seconds sleep time)
4. If the file size changes don't do anything else send the content to PI and /archivethe file (should be done inside the module code)
5. Keep the file sender channel in Test mode (as the module will do the necessary archival/deletion)
PS: This blog can be a starting point for you /people/sandeep.jaiswal/blog/2008/05/13/adapter-module-to-stop-processing-of-duplicate-file-ftp-location
Regards
Suraj

Is Confirmation Message possible in case of File to IDOC

Hi Friends,
Its a File (sender) to IDOC (receiver) interface. Once the IDOC is posted correctly in SAP, is it possible to generate a confirmation message back to sender file?
I want to know if there is any way to inform the sender system that the transaction was successfully created.
Thanks in advance.
Regards,
Meghna.
Edited by: meghna swaraj on Mar 27, 2008 1:53 PM

Hi Friends,
Its a FILE to IDOC interface. confirmation message back is needed to sender file, for that I followed the below link for Configuring the IDOC acknowledgment ALEAUD.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
As specified in point 7 and 8, used the transaction RBDSTATE & created the variant SAP_AUDIT_SEND for report RBDSTATE and scheduled a background job at receiver system.
Here the problem is, acknowledgment for ALEAUD getting scheduled twice, as a result two IDOCs ALEAUD is generated.Instead it should get scheduled only once.
Can any one tell me why the job is getting scheduled twice.
Thanks in advance.
Regards,
Meghna.

File to Idoc -- Unable to interpret IDoc interface mi_Orders05_In_Asyn..??

Hi All,
Im trying the File to Idoc scenario.. and im getting the following error in SXMB_MONI,
Anyidea what might have gone wrong??
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
<SAP:P1>mi_Orders05_In_Asyn</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
+<SAP:Stack>Unable to interpret IDoc interface mi_Orders05_In_Asyn</SAP:Stack>+
<SAP:Retry>M</SAP:Retry>
Waiting for your answers.
Thank You.
Seema.

Hi Seema,
I think you are using mi_Orders05_In_Asyn as the IDOC interface.
Use the imported idoc as the interface. i.e you dont need to create Inbound Message interface for IDOC. You can use the imported idoc structure as interface.
Let us know if that doesnt solve your problem.
Regards,
Sumit

XI unable to post IDOC to ECC the interface is FILE-to-IDOC scenario

Hi All,
The XI interface is a FILE-2-IDOC scenario and some times IDOC's in the receiver system are not posted. I did see successfully message for that particular messages but the IDOC's were not created in the ECC. If the messages is reprocessed then IDOC's are posted successfully to the ECC system. The message has checkered flag in the SXMB_MONI tcode.
This issue is occurring intermittently so could some point me in the right direction how to trouble shoot the issue.
Thanks,
Sarvesh

Hi,
Interesting problem...since its intermittant..
You cannot use any of the traditional RWB or message monitoring or cc chanel monitoring here as the error is in the ecc system, so from an XI standpoint it has left XI succssfully..that explains all the chequered flags..indicating success.
we19, we12, we14(process all idocs) test out the whole process with a load..use transaction we46..this can tell you why it is failing....in r/3
from the ecc system to check inbound queue monitoring.
from there you can select the IDocs or queues which you want to monitor, using the specified selection parameters available.
Look at the status record for the idoc that should give you more information, processing status of the idoc...that should tell you the status code assigned to it..
There is one other option here....if you can figure out what sequence they need to be posted in...that might be the reason for the failure..you can specify the sequence to post the idocs in, use qRfc ..
Hope that helps
Regards
Ravi Raman

File-IDOC, idoc interface error

Hi,
Scenario: File-IDOC (Multiple records in source file to be mapped to multiple CREMAS IDOCs) without BPM.
Modified the occurance(maxOccurs = 'unbounded') in XSD structure of IDOC(CREMAS) and saved it as external definition.
I have used this external definition in message mapping and interface mapping.
In configuration, i have used the same message interface (corresponding to external definition) as inbound interface.
Now, I get 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>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
<SAP:P1>MI_Cremas04_multi_external</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to interpret IDoc interface MI_Cremas04_multi_external</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please help.

Hi,
>>I have used this external definition in message mapping and interface mapping.
In interface mapping you need to use Imported IDOC not External definition
This solves your problem.
let me know if you have any issues still.
Cheers,
Jag

Help in creation of XML file for IDOC postings

Hi All,
Need help if anyone has knowledge/experience in creating XML files for IDOC processing.
We need to design an input file (in XML format) for creation of IDOCu2019s for purchase Invoices through Interface.
We have an existing input file, which is working correctly. We are trying to modify this existing input file for a new Tax Code (Non-deductible inverse tax liability). This tax code is working fine for manual postings. But, through IDOC, tax postings are not correctly triggering.
Could you please confirm if any one has experience on this, so that I can share more details for resolving.
Thanks & Regards,
Srini

Hello,
you can use CALL TRANSFORMATION id, which will create a exact "print" of the ABAP data into the XML.
If you need to change the structure of XML, you can alter your ABAP structure to match the requirements.
Of course you can create your own XSLT but that is not that easy to describe and nobody will do that for you around here. If you would like to start with XSLT, you´d better start the search.
Regards Otto

XI 3 File to IDoc scenario - Still referencing Old Logical system

Hi
Dont know if you can help. I have a file to idoc scenario using XI 3 to R/3 4.6c system.
I had the interface working from a third party system XMLHUB to SAP R/3. The Logical system name for the XMLHUB was XMLHUB01 in the SLD which I have set up as a partner profile in R/3. I have recently changed the logical system name to XMLHUBDEV01 in the SLD and created that logical system in R/3 and changed the partner profile to XMLHUBDEV01.
Unfortunately in the sender information of the IDoc the partner number is still XMLHUB01 and not XMLHUBDEV01. I don't understand where this partner is sent from to get into the control record of the IDoc.
I have cleared the SLD cache in both the Repository and the directory. Is there somewhere else I should be looking? Any help would be appreciated.
Regards
Daniel

hi daniel...
this thread wud answer ur query....
Re: IDOC Payload
regards..
vishal

File-to-Idoc error (using business sender service)

Hello,
My scenario is Flat file to IDoc. I am using a business service as my sender system. I did put in a logical system name in the business service and I have added the logical system in SALE.
The error I am getting is <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>MSGGUID 526719BA7E874E3906EEF45B43806D5C: Tag CULL_GR_RECORD found instead of tag IDOC BEGIN=</SAP:P1>
This is confusing to me because the CULL_GR_RECORD is the name of my data record of the file that is converted into an idoc within XI.
Can someone please help me with this? I would really appreciate it. I need to solve this tonight.
Thank you.

Hi,
>> I am using a business service as my sender system.
This is fine as ur sender is file.
I suggest deleting the matadata in IDX2 and then rerun the entire interface.
Make sure ur IDoc is imported properly to the IR. If yes, test ur mapping locally once.
Regards,
Divija.

Problem with Sender service in File to IDOC scenario

Hello All,
Am doing a file to IDOC scenario.
I have configured the sending system as a party and added a business component, to the BC attached the service interface and also configured the sender Communication channel(CC) as file.
On the receiving end configured the R/3 system from SLD as the business system and configured the receiver CCl. Can see the R/3 logical system in the Adapter specific identifiers at business system.
Pushing the file get an error "Unable to convert the sender service to an ALE Logical System". But choosing "Take sender from Payload" in the receiver CC is resolving the problem, however the sender partner number remains the same as what I have mapped to the control record in message mapping (which is like hard coding).
My questions are:
1. Am I doing the correct config in terms of the scenario. (like using "Take sender from Payload")
2. I tried using identifiers at the party level to convert the sending system, but nothing seems to work. But sending system remains the same as the constant from mapping.
Suggestions would be very much helpful..
--Prashanth
PS: Have gone through many blogs and posts on the forums, but may be I did not see the correct thread. Apologies if I am asking this again.

Hi Prashanth,
refer the below discussion i think it will solve your problem.
File To Idoc scenario
Thanks

Receive acknowledgement in file-to-idoc scenario

Hello!
I'm using guide "How to handle acknowledgement for IDOC", and for the first time I want to see an acknowledgement status in sxmb_moni.
I have passed all steps:
In CRM I have logical system P1DFILE, this is the system that sends an idoc to CRM.
Also, I have logical system C2DCLNT100 - this is CRM system.
First, I go to BD64, create new model view XI_CRM. Then, add message type:
Sender system - C2DCLNT100
Receiver system - P1DFILE
Message type - ALEAUD.
Then I create RFC destination P1D_001 to my PI server.
Then I create port SAPP1D using WE21
Then I go to WE20, choose my Logical System - P1DFILE. I already have the inbound message types (CRMXIF_PARTNER_SAVE and CRMXIF_PARTNER_SAVE_M). I add new outbound message - ALEAUD with receiver port SAPP1D.
Then I go to RBDSTATE, create variant SAP_AUDIT_SEND and enter:
Confirmation to system: P1DFILE
Message type: CRMXIF_PARTNER_SAVE and CRMXIF_PARTNER_SAVE_M
Then, in SM36 I shedule SAP_AUDIT_SEND as a hourly job (does this mean, that I will receive confirmations only every hour?)
So, what should I do to see ack in sxmb_moni?

Dear All,
For file to idoc scenario is there any possibility to get line items details or xml details i.e the segments and its related field details using reference id, transaction id or interface name or message id in SAP PI 7.0. I know we need to click each and every message in sxi_monitor and look for details.
For SAP(R3 System) I can create a report and set the job for specific time period so automatically it throws the details(like reference no, document date, invoice no from) in ftp path as .csv file. The same ftp path is maintained in program.
I wanted to check FTP--->PI postings and I have set the job at r3 system it is working fine and Im monitoring it too.
Now the end to end scenario is FTP--->PI--->ECC(R3 system). Please help.Many Thanks.

System Level Acknowledgement in File to IDOC Scenario

Hi All,
I have the File-> IDOC Scenario. Once the IDOC is successfully sent to R/3, PI should send a acknowlement file back to the sender system.
Could someone suggest how to design this scenario?
Should I use IDOC Acknowledgement. As it is a existing scenario, I dont want much change in r/3 side.

Dear All,
For file to idoc scenario is there any possibility to get line items details or xml details i.e the segments and its related field details using reference id, transaction id or interface name or message id in SAP PI 7.0. I know we need to click each and every message in sxi_monitor and look for details.
For SAP(R3 System) I can create a report and set the job for specific time period so automatically it throws the details(like reference no, document date, invoice no from) in ftp path as .csv file. The same ftp path is maintained in program.
I wanted to check FTP--->PI postings and I have set the job at r3 system it is working fine and Im monitoring it too.
Now the end to end scenario is FTP--->PI--->ECC(R3 system). Please help.Many Thanks.

File to IDoc scenario in SRM

Hello All,
I am executing a scenario involving File to IDoc using an XSLT interface mapping.
I am getting an error with error text "Tag ORDERHEADER found instead of tag IDOC BEGIN"
Here is the error message:
<?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="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>MSGGUID 1C28075F1E109C479C1A25BA068CC74D: Tag ORDERHEADER found instead of tag IDOC BEGIN=</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: MSGGUID 1C28075F1E109C479C1A25BA068CC74D: Tag ORDERHEADER found instead of tag IDOC BEGIN=</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I tested the XSLT mapping alone in Repository and it is working fine.
Please suggest on this issue.
Regards, Namadev

Hi Namdev,
//Tag ORDERHEADER found instead of tag IDOC BEGIN"
I think this error is due to a problem either in your source file or your mapping. When the IDOC is to be sent to the destination system, it expects the first tag to be <IDOC begin = > , but I dont think that is happening in your mapping.
As you are doing XSLT mapping, I would suggest you test your mapping and check if the destination Message that is created matches with the IDOC structure.
Regards,
bhavesh

File to idoc scenario in pi 7.1

Hi All,
I am testing file to Idoc scenario.
I have few queries. I am using PI 7.1
1) in Message mapping - I import the receiver idoc metadata. and doing mapping.
So there are couple of mandatory fields over there. Please let me know how to treat them. Do I need to diable them or put some value. for exp Direct, Segment. SNDPRN RECPRN all these madatory fields are there. Please advice.
2) When I am creating communication component for sender side(File system) then should I assign the logical port and if then what name it can be . Is there any other place we need to maintain this entry. I remember in PI 7.0 I dont need to assign the local name. But here i see I need to do. if I am not putting the name over there then it throw error message "Unable to convert the sender service <Business Compoenetname> to an ALE logical system.
Please advice how to overcome
3) now any how I am able to process the idoc from PI and its coming to ECC system. but it showing failed over there and giving me error message.
"EDI: Partner profile inbound not available"
I checked all the relevent partner prfile configuration is already there"
I have already used all the forums , I did these scenario in past in PI 7.0 and never faced much issue . but doing first in PI 7.1 after a long time, so I might be possible, I am missing some thing. Please advice and help. thank
Ram

Hi Ram,
There is nothing new in PI7.1 which can cause these errors.. it is because the interface is configured wrongly
>>1) in Message mapping - I import the receiver idoc metadata. and doing mapping.So there are couple of mandatory fields over there. Please let me know how to treat them. Do I need to diable them or put some value. for exp Direct, Segment. SNDPRN RECPRN all these madatory fields are there. Please advice.
If you know the value the you can create the control record during mapping and the fields which you don;t required you can map it co constant. It is using this control record the partner profile entries are found and if there is a mismatch then the idoc will fail with the error which you mentioned in point 3
>>2) When I am creating communication component for sender side(File system) then should I assign the logical port and if then what name it can be . Is there any other place we need to maintain this entry. I remember in PI 7.0 I dont need to assign the local name. But here i see I need to do. if I am not putting the name over there then it throw error message "Unable to convert the sender service <Business Compoenetname> to an ALE logical system.
No in 7.1 also we dont have to do anything like that. There is a blog on this error from Michael, please go through it and understand why and how this error occurs. May be in PI7.0 you were lucky enough for not getting this error
>>3) now any how I am able to process the idoc from PI and its coming to ECC system. but it showing failed over there and giving me error message. "EDI: Partner profile inbound not available"I checked all the relevent partner prfile configuration is already there"
Check the control record of the generated idoc and see whether you have a partner profile entry for the parameters mentioned in it. If not then you need to correct them in PI
Regards
Suraj

IDOC creation issue at XI side - File to IDOC

Hi Everybody,
I am working on a File to IDOC scenario (XI 3.0).
We have to create Orders in the R/3 System using this Interface.
Mapping used is Java.
I am using 2 Classes : Group and SendIdoc one below the other in the Interface Mapping:
Firstly by using Group Class I am Grouping the Records in the file and then creating the IDOCs by using the next class(SendIdoc).
In the production environment if we drop like 20 files at a time in the source NFS folder the number of IDOCs created are wrong.
Say for example, for the first file dropped expected IDOCs are 10 but only 8 are created in SXMB_MONI .However in the input payload (in SXMB_MONI) the entire text file is read.
When we put the files sequentially say one after the other is processed, the number of IDOCs created are fine.
This is very strange problem.
I tried changing the polling interval of the channel but was of no help.
Any parameters we need to set in the channel or XI system to overcome this issue?
Can someone help me out on this?
Helpful answers will be rewarded points.
Thanks & Regards,
RK

Hi ,
When you placing files sequentially its working fine menas there is no problem with Java Code,one morething use synchronize methods or thread programming in Java maps is not advisable.
as per my knowledge File adapter picking up the recodrs when its giving inout to Java map some thing misisng....
for one file you need to create multiple IDocs try use QOS EOIO or if its not working then try to use record set per message one like that,let me know.
Regards,
Raj

File to idoc interface

Similar Messages

Maybe you are looking for