IDoc to File interface

Hi Experts Team,
My scenario is IDoc to File interface. I need to create 12 different files based on the Plant code (WERKS). At the end of the day, i need to ftp the file to different locations. How can I do the design and is there any need for BPM here?
Please explain..
Thanks & Regards,
Kanda

Hi S.P ,
You may use the variable substitution functionality of receiver file adapter and can generate the file based on the xml payload content which contains your WERKS field.
You may refer the following blogs for the understanding of the concept.
An interesting usage of Variable Substitution in XI
Thanks & Regards
Prabhat

Similar Messages

Need help on IDOC to file interface.

Hi Folks,
I am working on IDOC to file Interface. We are pushing 15 Idocs from SAP R/3 system to SAP PI. Idocs in R/3 system are in correct order. When it comes nto PI system IDOC order is diffrent.
For Example : I am sending 6 idocs 1000, 1001,1002,1003,1004,1005 from R/3 system. WHen these idocs coming into PI its order is changing so in PI system IDOCS order is 1000, 1004,1001,1005,1002. But, I want IDOCS are should be same as R/3 system.
For handling this issue, what are the necessary steps I need to follow in PI?
Thanks,
Enivass

Hi Enivas,
Check this link regarding serialing IDOC: http://help.sap.com/saphelp_nw04/helpdata/en/bd/277264c3ddd44ea429af5e7d2c6e69/content.htm
http://www.saptechnical .com/Tutorials/ALE/Serialization/page1.htm
Thanks,

No service for system ECC R/3 , for IDOC to file interface in SM58

Hi all,
I am geting a error No service for system XXXXX, client 100 iIntegration Directory,
when i go to IIDX2 and Updating the IDOC type , i am not able to add it is give me a error 100
please help me in this
thanking you

Hi,
Check the threads Idoc adapter - No service for a system in Integration directory
No service for system ... in Integration Directory
Thanks!

Error in IDOC ststus , for interface IDOC to File

Hi All,
iI am doing IDOC to file interface , in which i am using IDOC Orders05, we are using the same IDOC for other interface to connect with DOTNET connectors , when i trigger the IDOC ORDERS05 for my interface when i check the ststus , in which it is pointing the to partner No and Port to that dontnet, not to my Iterface for SAP XI , anyone there to help me in this isssue
Thanking you
Sridhar

Hello,
While sending Idoc you will be providing the Port which in turn needs RFC Destination and this is one which takes the document to External system configured in RFC.
If you need to send the idoc to External Systems other than R/3 then you need to use T type connection which uses JCO for estblishing session. if it is R/3 then requires logon credentails and type 3 for configuring RFC.
HTH
Rajesh

IDOC to File : "no interface found"

Hi all,
I have an IDOC to file scenario and I'm getting the error "no interface found" at sxmb_moni. The scenario is only for test purposes, very simple, using the IDOC /ISDFPS/T01./ISDFPS/T0101. I have configured
-> receiver and interface determination
-> receiver agreement with the receiver channel for file output.
Receiver interface (sender) is /ISDFPS/T01./ISDFPS/T0101 and receiver agreement I configured the inbound interface to /ISDFPS/T01./ISDFPS/T0101 (same interface, no mapping needed).
I don't know why I'm getting "no interface found" error... Some tips?
thanks!
roberti

Yes, Bhavesh, I think the same. But all of it seems to be ok, lets see...
Rec. Determination
Sender
Service: ED0
Interface: /ISDFPS/T01./ISDFPS/T0101
Namespace: urn:sap-com:document:sap:idoc:messages
Receiver
Party:*
Service:*
Type: Standard
Configured Receivers: Service: SAE_NAS (no conditions or partys)
Interface Determination
Sender
Service: ED0
Interface: /ISDFPS/T01./ISDFPS/T0101
Namespace: urn:sap-com:document:sap:idoc:messages
Receiver
Service: SAE_NAS
Type: Standard
Configured Inbound Interfaces
Inbound Interface
Name: /ISDFPS/T01./ISDFPS/T0101
Namespace:urn:sap-com:document:sap:idoc:messages
No mapping (are the same messages, but I have already tried with mapping)
Rec. Agreement
Sender
Service: ED0
Receiver
Service: SAE_NAS
Interface: /ISDFPS/T01./ISDFPS/T0101
Namespace: urn:sap-com:document:sap:idoc:messages
Receiver com. channel: CHN_RCV
I think the problem is in a little bit detail... but I couldn't find it. Some tip?
thanks!
roberti

Receiver Business System Connot find Inbound Interface - IDoc to File

Hi Everyone,
I am doing IDoc to File Scenario.....Idoc got triggered from SAP system and successfully posted to SAP PI.
Now when I check in T-Code IDX5 in PI, I got one message. When I double click that I am getting following error:
<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:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Also When I am selecting Receiving Inbound interface for Receiver system, I am not getting any interface by default.
Please help me out.
Thanks & Regards,
Sudheer

Hi everyone,
Thanks for your quick responses.
Actually I am doing IDoc to File Scenario from blog which consists of Conditional Receiver Determination
"SNDPFC"
Here is the Explanation given in that blog:
In most instances, a new Receiver Determination would be created. However, given that in this scenario the combination of the sender service (i.e. u201CGL1u201D) and interface (i.e. u201CMATMAS.MATMAS04u201D) will be used by every student, each student will instead be adding their receiver service to an existing Receiver Determination
11. In the Condition column on that same line, left click on the question mark help icon
12. In the following Condition Editor pop-up window, left click on the help icon in the u201CLeft Operandu201D field
13. In the following Expression Editor pop-up window, select the u201CContext Objectu201D radio button
14. Use the drop drown to locate and select the u201CSNDPFCu201D field and u201COKu201D
15. Back in the Expression Editor, leave the u201C=u201D Operand as is
16. Enter your group number in the u201CRight Operandu201D and u201COKu201D
17. u201CSaveu201D and validate your u201CConfigured Receiversu201D as seen below:
I did not understood this Conditional RD.
Apart from this all configuration are correct.
Thanks,
Sudheer

IDoc to file- How to include conditions in Interface determinations

Hi,
In interface Determination i am trying to add the conditions based on IDoc structure field value. But when i clicked on Condition editor i don't find Idoc stucture in editor XPath.
Please suggest me how i can add the condtions in the Interface determination in IDoc to file Senario.
Thanks in Advance...
Regards
Sreeni

Hi Sudhir,
I have tried as you mentioned, but still its not working. Below i am providing my inbound payload.
Could please let me know how i have to mention in condition editor to refer the IDoc field
ZGHIER01/IDOC/Z1GLHIERH/SETNAME
<?xml version="1.0" encoding="UTF-8" ?>
- <ZGHIER01>
- <IDOC BEGIN="1">
 + <EDI_DC40 SEGMENT="1">
 - <Z1GLHIERH SEGMENT="1">
 <CATEGORY>GLHIER</CATEGORY>
 <SETNAME>PEGPL_AG</SETNAME>
 + <Z1GLHIERD SEGMENT="1">
 + <Z1GLHIERI SEGMENT="1">
 + <Z1GLHIERI SEGMENT="1">
 + <Z1GLHIERI SEGMENT="1">
 + <Z1GLHIERI SEGMENT="1">
 </Z1GLHIERH>
</IDOC>
</ZGHIER01>
Thanks & Regards
Sreeni
Edited by: Sreenivasulu Reddy jonnavarapu on Dec 12, 2008 10:39 PM

Difference between file interface Idoc & Structure Interface Idoc?

Hi,
an any one tell me Difference between file interface Idoc & Structure Interface Idoc?
Thanks In Advance.

Hi
[IDOC Structure|http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b824843d711d1893e0000e8323c4f/content.htm]
[File Interface|http://help.sap.com/saphelp_di46c2/helpdata/EN/dc/6b7f6343d711d1893e0000e8323c4f/content.htm]
Regards
Pavan

Help needed in Idoc To File Scenario

Hi Experts,
My scenario is Idoc to File.
Here my job is to convert the purchase order idoc into xml file.
In this there are three conditions.
                   converting the standard PO into xml file
(ii)                 converting the PO with serial number into xml file
(iii)                converting the PO using serial number with subcontracting into xml file
so what I feel is I need to create one scenario and based on the condition that particular PO will convert into xml file.
Conditions:
                   if no condition is specified then it is standard PO first case
(ii)                 if field tdline ne space then it is PO with serial number second case
(iii)                if field pstyp eq 3 then it is PO using serial number with    subcontracting third case.
Please guide how to do this scenario.
IR:
1)       how many data types I need to create
2)       how many message types I need to create
3)       how many message interfaces I need to create
4)       how many message mappings I need to create
5)       how many message interfaces I need to create
ID:
1)       how many receiver determinations I need to create
2)       how many interface determinations I need create
3)       how many receiver agreements I need to create
And where to write the conditions at message mapping level or at receiver determination level.
Kindly provide solution to every point.
Regards,
Venkat.

1) if no condition is specified then it is standard PO first case
2) if field tdline ne space then it is PO with serial number second case
3) if field pstyp eq 3 then it is PO using serial number with subcontracting third case.
you have to create
1. outbound ( IDOC)
2. 3 Inbound (same MT)
create 3 mapping program each for 1 condition
create 3 interface mappings
ID:
1 reveri BS.
3 Interface determinations, so 3 receiver agrement.......
you can put the condition on the mapping or in the condition tab of the interface determinations.

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.

Problem in idoc to file scenario

hi
while creating the idoc to file scenario i am facing few problems.
1) My design time objects are working fine. i have checked my message mapping, message interface etc.. (all design time objects are in active mode).
2) In ID, i have tested my configuration in test configuration, its working fine there as well (in ID i am using 2 business service one for sender, one for receiver)
3) i am using my ecc6 training server as my sender and using my XI server as receiver.
4) i am sending idoc from ecc6 and converting it to file in XI server and saving it in XI server itself(my receiver in this case).
my error:
i send my idoc from we19 transaction, and i see a error message stating
that 'RCVR_DETERMINATION.NO_RECEIVER_CASE_ASYNC'
my doubts.
1) while sending the idoc from ecc6, is it mandatory to give process code in partner profile ( that is, assign an outbound function module to push the created idoc to the mentioned destination).
2) also is it mandatory to have a partner profile on the receiver side( XI in this case) along with inbound process code.
3) in my receiver adapter ( file adatper in this case ) i have used NFS protocal. is it rite?
kindly help me with this issue.
regards
manoharan

>
manoj murugesan wrote:
> 1) while sending the idoc from ecc6, is it mandatory to give process code in partner profile ( that is, assign an outbound function module to push the created idoc to the mentioned destination).
>
> 2) also is it mandatory to have a partner profile on the receiver side( XI in this case) along with inbound process code.
>
> 3) in my receiver adapter ( file adatper in this case ) i have used NFS protocal. is it rite?
>
>
> kindly help me with this issue.
>
>
> regards
> manoharan
and to 1 & 2 ref. below,
Configuration steps required for posting idoc's(XI) -
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
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
3. NFS protocol is used to read/write files to the XI server itself. If you have to write to a local machine then use FTP

Alerts when the acknowledgement fails in IDOC to File Scenario

Hi All,
could you let me know how to handle Alerts for Idoc to File scenario.
My Scenario uses BPM as well.
Thanks,
Srini

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.

Acknowledgements IDOC - XI - File

Hi all,
I'm facing the following problem...
There was a scenario IDOC - XI - FILE (lets say from system A to MDM) that was working properly for a while but when we implemented a new IDOC to file from a new system to MDM then the already existing interfaces from A to MDM stopped, all of them were stocked into queues.
In SXMB_MONI all the messages were marked as successfully processed but they weren't delivered, the comm. channel is active and there are not errors but the Queues show this one:
" CO_TXT_ROUTING_BACK_ERROR "
So we have gone thru all the threads related with this error and we have updated the IDXNOALE table to see if this will solve the further message processing but the thing is, why XI did not deliver the processed messages if they were marked with the success status? How can you retrieve/reprocess all those messages stocked into queues?
Why DEV and QAS were Ok but then PRD started failling? We never updated those tables... but now in PRD we have to.. I don't understand why...
This topic is very confusing for me and for all of us that are facing this problem, so if someone has a very good answer, please post it...
Thanks for your help...
-- Jerry

HI Jerry
Refer these links
http://help.sap.com/saphelp_nw04/helpdata/en/42/c8f66bc7a56bb0e10000000a1553f6/frameset.htm
Check this document on handling IDOC acknowledgements. This might give you some pointers.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
for this error
CO_TXT_ROUTING_BACK_ERROR
If you want to suppress acknowledgements please check this thread:
JDBC Adapter / Acknowledgements
Check out SAP Note 832965
This could help u,
JDBC Adapter / Acknowledgements
Thanks !!!

Idoc to file scenario error

Hell Experts,
I have done desgin and configuration from Idoc to File Scenario in XI Intergration server.
Source is R/3 and Target system is File. I have successfully configured each and every step. Send Idoc from R/3 to Intergration server and run sxi_cache. But I didn't get successful results, always the error message shows in SXMB_MONI as follows:
Ackn Status contains system error
During the application mapping com/sap/xi/tf/_CUST_MMAP_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: RuntimeExcep
tion in Message-Mapping transformatio~
Exception of class CX_XMS_SYSERR_MAPPING
My system Patche level as follows:
SAP_BASIS     640        0012        SAPKB64012
SAP_ABA     640     0012                SAPKA64012
PI_BASIS     2004_1_640 0009        SAPKIPYI69
SAP_BW     350     0009                SAPKW35009
The above error is related to patches problems or any Mapping problems ?
Please help me.
Advanced Thanks.
Regards,
Chandra

Hi,
This may be a mapping issue, try this:
a)in interface mapping see if grids are formed at source and target after executing the test option,
b)also take the xml of the idoc from sxmb_moni , copy it and paste it at the source of the mapping ( use the src tab now) and execute the mapping, is your file structute formed?
i am not sure of the patch levels.
Regards,
Anirban.

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 interface

Similar Messages

Maybe you are looking for