Idoc to file scenario - collect idocs

Hi experts,
I need help regarding collecting the idocs as per the reciver id available in idoc.
After collecting these idocs at XI, the data of all idocs should be transferred in one text file.
How I can do this ?
Give me complete solution with example scenario ?
Please do not give any example in standards scenarios as given in SAP BASIS Patterns.
Regards,
Study SAP

Hi,
Plz do refer the following links:
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm - Collection of IDoc to Single File
/people/stefan.grube/blog/2006/09/18/collecting-idocs-without-using-bpm - collecting IDocs without BPM
/people/daniel.graversen/blog/2006/09/07/using-a-bpm-to-collect-messages-for-a-set-interval-of-time
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30ea2fdf-f047-2a10-d3a2-955a634bde6b
Also this link,
http://help.sap.com/saphelp_nw04/helpdata/en/08/16163ff8519a06e10000000a114084/content.htm
Regards,
Vinod.
Edited by: Vinod Reddy on Jun 26, 2008 9:23 AM

Similar Messages

IDOC to FILE Scenario-Error in defining Adapter specific Identfier

Hi All,
I am configuring IDOC to FILE scenario where IDOC will be send from ECC to PI System.I did following configuration
I created RFC,PORT,LS and Partner Profile on R/3 System. I had maintained SLD and IR. In ID I created Configuration scenario and business system.When I click on menu->Adapter specific Identfier where I want to specify IDOC Adapter and RFC Adapter. But it is not allowing to edit it is not editable. As we provide LOGICAL SYSTEM,sender system ID and client number of the sender system.

Hi Kavi,
I assume you correctly filled the Logical System of your Business System in the SLD...
Then in Integration Direction, use menu "SLD clear cache".
Always in Integration Direction, open your Business System, go to menu "adapter specific identifier", and... close to button "close", you should have another button like something ''check'' or "compare to SLD' or ''retreive SDL data'' (I have not an openned PI to check the right term). Use this button to get value stored in SLD to this local definition.
Mickael

Problem IDOC to File scenario: No service for system SAPIDC, clnt in ID

in IDOC to File scenario, when IDOCis triggered from R/3 to XI, it gives error in SM58 transaction
"No service for system SAPIDC, client 800 in Integration Directory"

In a scenario, i have a BPM which has a transformation step which contains a mutimapping ...means 2 messages mapped to 1 messgaes, here in the mapping i m using an UDF and written code to extract the file name from dynamic configuration.....
the problem is ...the same BPM contains another transformation step which contains a message mapping (which is not multi mapping), and here the code (UDF) works to fetch the file name...
the code is all correct....and it looks like
DynamicConfiguration conf = (DynamicConfiguration)
container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");
String sourceFileName = conf.get(key);
if (sourceFileName == null ){
sourceFileName = "ErrorFile.xml";}
return sourceFileName;

IDOC to File scenario info

Hi Experts,
What all the important information we have to gather from client to do the IDOC to File(SML) scenario?
Thanks & Regards
Sara

Hii
Check this blog on IDOC to File. It states step by steps procedure for IDOC-File scenario:
Introduction to IDoc-XI-File scenario and complete walk through for starters.
In this blog u ll get information.
For troubleshooting of IDOC-File check this blog:
Troubleshooting File-to-IDOC Scenario in XI.
also for sending Collection of IDoc to Single File
IDOCs (Multiple Types) Collection in BPM
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
Regards

Idoc to file scenario doc

Hi,
Can anybody share the document of IDOC to File Scenario for Vendor Master.
Regards,
Balaji

Hi Balaji Permi ,
Check these websites which wil answer u'r question:
A Step-by-Step Guide on IDoc-to-File Using Business Service in the XI Integration Directory
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
How to convert an IDoc-XML structure to a flat file and vice-versa in XI 3.0
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
Introduction to IDoc-XI-File scenario and complete walk through for starters.
Introduction to IDoc-XI-File scenario and complete walk through for starters.
IDOCs (Multiple Types) Collection in BPM
IDOCs (Multiple Types) Collection in BPM
cheers!
gyanaraj
<removed by moderator>
Edited by: Mike Pokraka on Aug 12, 2008 3:07 PM

Which all configurations you need to do in R/3 for an Idoc to file scenario

which all configurations you need to do in R/3 for an Idoc to file scenario?
Rgds
Ruchitha

Hi ruchitha thakur ,
A Summary of the Steps to be carried out to enable a SAP R/3 System send Idocs to SAP Exchange Infrastructure.
First - Maintain the Sender R/3 System:
SM59 : Create a RFC destination to XI
WE21 : Create a TRFC Port ->Specify the RFC Destination Created
BD54 : Create a Logical System for the Idoc Receiver
WE20 : Create Partner Profile ->Maintain Outbound and the Inbound Parameters
Second - Log on to XI System:
SM59 : RFC Destination for Sender System
IDX1 : Create the port to get Idoc Metadata from Sender System ( The Port Name must match the port name in the idoc header - Usually in format SAP<System ID>. eg. SAPID1 [Optional Step. Not mandatory]
IDX2 : Maintain the Idoc Metadata. This is needed only by XI, and not by other SAP systems. IDX2 is needed because XI needs to construct IDoc-XML from the IDoc. No other SAP system needs to do that.
To Enable Acknowledgement:
SXMB_ADM ->Integration Engine Configuration ->Specific Configuration ->Add New entry -> Select parameters as:
Category: RUNTIME
Parameters: ACK_SYSTEM_FAILURE
Current Value: 1
GO TO SLD:
Create Technical System: Choose WEB AS ABAP if the system is R/3 -> Define SAP SID, Installation Number and Database Host Name a Maintain message Server Details according to Sender System -> Maintain Client Details of Sender System ->Select a Installed Product for Sender System
Create Business System: Choose WEB AS ABAP if the system is R/3 -> Choose the Technical System and the client Created Before -> Choose the Installed Product -> Set:
Business System Role: Application System
Related Integration Server: Integration Server
Integration Builder
Integration Directory:
Add Business System: Adapter Specific Identifiers -> 'Logical System' identical to the 'Logical System Name' in the SLD Business System
IDoc Receiver Communication Channel: port the same as XI System IDX1
The following web-sites give u step-by-step solution to configure R/3 :
ALE configuration for pushing idocs from SAP to XI
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
How to convert an IDoc-XML structure to a flat file and vice-versa in XI 3.0
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
Introduction to IDoc-XI-File scenario and complete walk through for starters.
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
IDOCs (Multiple Types) Collection in BPM
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
Step by Step Procedure of IDOC to File Scenario using BPM
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/main&
cheers!
gyanaraj
****Pls reward points if u find this useful

Idoc-xi-file scenario. how to display file in html format

I am not sure whether this is a valid question.........but want to confirm as it was asked by somebody
In idoc-xi-file scenario....... how to display file in html format ??
Thanks in advance
Kumar

Hi Vijayakumar,
Thanks for your reply !! You mean to say I got to use XSLT mapping and also .htm and .html extension together to produce the html file ?? or it is sufficient to use any one of them to produce the html file ??
Regards
Kumar

In idoc to file scenario, if XI system is down where do idocs pile up?

In idoc to file scenario, if XI system is down where do idocs pile up (get stuck)
what tcode can I use to reprocess it?

Sender System ,Check BD87 .. you will see alll the IDOCs in Yellow state ..
You can reprocess all the IDOCs in go from there .. if only they are in yellow state ...
regards
PS

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

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 .

Integration server as logical system in IDoc to file scenario

Hi,
Will we configure integration server as logical system in IDoc to file scenario or the RFC destination related to the port will be suffice?
For which logical system will the outbound partner profile configured?
Regards,
Gajendra.

Hello,
I feel that the RFC destination linked to the port is the key here.
Because the scenario (IDoc to File) works in both the cases:
Case 1: Used the logical system as Integration server
Case 2: Used the logical system related to the file (third party) in the SLD.
In both the above cases the RFC destination points to the integration server.
Is this the case that in the XI scenarios (where IDoc are sent) the logical system name in the partner profile is just dummy and has not much significance??
It is the port that matters and once the Idoc reaches XI the routing takes place based on the configuration in ID.
Thanks.
Regards,
Gajendra.

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

Hi Experts,
In IDOC to file scenario i did in this way.
1)created logical system.
2)Using SALE tcode I assign logical system to client ,created RFC destination,Port and Partner's profile.
It is showing all the thing correct.
3) In XI system , I configured using IDX1 and IDX2.
Then I created the material and checked the status which is green in we05.
But in tcode IDX5, the material is not coming.
Here I am confused that why data is not coming to XI system.
can anyone help me?
Thanks
Rabi

Hi,
The Following are the Possible checks
1) Check in R/3 side SMQ1 & SMQ2
2) Check in R/3 side SM58
   In R/3 system, Goto SM58 tcode and see if the IDOC have stuck up in Queue.
   If the entry is available then select it and press F6, to push it manually.
    This happens normally if IDOC stuck up in queues.
3) Check in PI SMQ2 and IDX5
regards,
ganesh.

PI 7.1 scenario -- File to File , File to IDOC and IDoc to File Scenario

Hi All,
*I have PI 7.0 . I have in that File to File , File to IDOC and IDoc to File Scenarios*
File to File -- This scenario is working fine.
File to IDOC -- Setting done in PI 7.0 like SM59, IDXI, IDX2 and in R/3 like SALE (logical system)--- This scenario is working fine.
IDoc to File -- Seeting done in R/3 like SALE (Logical system, Distrubtion Model (Port, Partner Profile)) -- This scenario is working fine.
Now I need to move to PI 7.1 -- for File to File , File to IDOC and IDoc to File Scenarios.
Please let me know do I require to make any changes in Design and Configuration and settings in PI 7.1 and R/3 for above scenarios or it will work fine as it is already working for PI 7.0
If changes are required please let me know what changes to do for each scaenario and pls also send blogs for that.
Regards

>
Rickkk wrote:
> Hi,
>
> Idoc metadeta is updated through idx2?
>
> Regards
If there is no metadata maintained for an idoc type, the metadata for that idoc type gets loaded when an idoc of that type is received by PI for the first time. If you are looking at loading metadata of all idoc types before the first run, its really not required. Just make sure that the port is configured properly. Although, there is no harm in preloading the metadata using IDX2.
You need to use IDX2 mandatorily when the the metadata changes and the metadata in ECC and PI is different. In that case, you need to delete metadata for the changed IDoc type and then either you can update the metada through IDX2 or let the system take care of.

Why we dont need sender agreement and comm channel in IDOC to file scenario

Hi,
there are 2 queries:
first query :
Scenario is "Idoc to file transfer"
why we dont need sender agreement and communication channel for IDOC to file ,while we do need
both of these for "File to RFC "
Answer : which i got is because IDOC sits at ABAP stack but same is valid for RFC also.
Then why For "IDOC to file" we dont need that.
Second query:
Also when i did scenario for File1-RFC-File2 scenario using BPM i have created a interface
between XI-RFC synchronous to send data which we got from file1 in XI to RFC importing parameter
and getting data from RFC back to File2.
Here in IDOC to file scenario why we dont need any interfface for IDOC-XI Asynchronous.
Regards,
Mayank
Edited by: mayank verdia on Jan 13, 2009 11:49 AM
Edited by: mayank verdia on Jan 13, 2009 11:50 AM

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.

Idoc to file scenario - collect idocs

Similar Messages

Maybe you are looking for