Configuring IDOC to file Scenario in PI 7

Hello All,
I am doing an IDOC to file scenario, all the configuration is done. When i trigger the outbound IDOC, I can see in SXMB_MONI the sender component, sender Namespace, sender interface and reciever component are coming up correctly as configured.
1. But the reciever namespace and Reciever Interface are having the same values as the sender namespace and sender interface interface respectively. I am sure they have to be as per the config in ID.
2. Also on further going into the error message
SAP:Code area="OUTBINDING">CO_TXT_OUTBINDING_ERROR</SAP:Code
SAP:AdditionalText>No standard agreement found for , DEV400, ANZ, BC_RECV_PAYM_ORD, urn:sap-com:document:sap:idoc:messages, PAYEXT.PEXR2002</SAP:AdditionalText>
Can anyone please suggest , what is it that I am doing wrong.
---Prashanth

Hi,
Please delete the Receiver determination and try creating again. refresh cache.
Can you please have a look at the sap notes if of any use .. i think its a different case altogether , but pls have a look.
SAP Notes 1278244- https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1278244
SAP Note 1284103 -https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1284103
Regards,
Srinivas

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

Idoc to File scenario using Party

Hi All,
I have to configure Idoc to File scenario .This file needs to be posted in EDI Subsystem .My receiver partner type is LI.That means i need to use Party here.So please let me know the step by step solution to do this.Specially i want to know the configuration in Party Identifier and Receiver Communication channel Identifiers.
How the control record values from idoc are transferred to EDI File structure and how will XI identify one of the many customers to post the file.
All valuable suggestions will be rewarded the points.
Please send me the documents for such scenario with screen shots.

Hi,
Let me see if I had you requirement correct.
When the Idoc is sent from R3, sender partner type is LS and Receiver Partner Type is LI.
If yes,
1. Create a Party in ID.
2. The Agency , Scheme and Identifier will have values,
Agency --> Receiver Business System name or Business Service Name to be used for File.
Scheme --> ALE#LI
Identiier --> Value of the RCVPRN field in the idoc control Record. Basically the Receiver Partner Name.
All the Configuration In ID will use this Party as the Receiver Party and the corresponding Service asthe Receiver service.
No need for a sender party as sender partner is LS.
Regards
Bhavesh

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

How To Test Idoc To File Scenario in ID From Tools- Test Configuration

Hi All,
Can any body help me in step by step process including screenshots for testing Idoc to file scenario in integration directory from tools->test configuration.
My scenario is passing the PO Idoc data from R/3 into a file using XI.
i have processed the idoc from R/3 and now i went to sxmb_moni in XI system and took the payload xml data.
In ID I have navigated to test configuration from tools then i have provided the following information.
Sender Service : Business system of R/3 b'coz here R/3 is the sender.
Sender Interface : ORDERS.ORDERS6
Receiver Service : Business system of XI b'coz here XI receives the data and         places it into a file
In payload text box i have copied the xml code which i have taken from sxmb_moni and clicked the run button. then i got the following error:
Sender Agreement
Internal Error
                 HTTP connection to ABAP Runtime failed.
                 Error: 403 Forbidden
                 URL: http://bxdci.boewe.custservice.de:8093/sap/xi/simulation?sap-client=100
                 User: PIDIRUSER
Kindly look into it and correct me if iam wrong or is there any other way to test this scenario in ID please suggest.
Thanks & Regards,
Venkat

Hi Venkat,
Specify the test confisuration as follows.
<b>Sender</b>
Service   : Business System of SAP R/3 System
Interface : The outbound message interface name of type the IDOC.
Namespace : will automatically loaded when u select the Interface. Check if it the correct namespace.
<b>Receiver:</b>
Service : Business System name for the Fle system.
Paste the payload that u copied from the sxmb_moni.
Now click on Run and test ur Scenario.
Was the scenario sucessfull in the Message Monitor.
Regards
Santhosh

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

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.

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.

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

Issues in IDOC to File scenario using bussiness service

Hi Team
I found a blog which explains about the IDOC to FILE scenario by using bussinss services. I followed the steps and finally i am getting a error message while posting an idoc in we19 (ie IDOC 09878 was saved but cannot or should not be sent). The setting which have done on SAP side are as below
SAP SIDE CONFIGURATIONS
1. Created RFC destination : RFC_XI_SYSTEM
2. Created port : PORT_TEST
3. created logical system: IDOC2FILE
4. created partner profiles: IDOC2FILE
XI side configurations
1. Created RFC destination: RFC_SAP_SYSTEM
2. Created port : by using IDX1 t-code
DOUBT: here it is asking for PORT, CLIENT,Description and RFC destination, please let me know what values i need to put here, please find the SAP and XI system details below and suggest accordingly.
3. metadata: by using idx2.
DOUBT: here it is asking for IDOC type and source port, i can give the idoc name but i am not getting what i need to give to source prort field, please check and let me know, please find the SAP and XI system details below and suggest accordingly.
SAP system details
Client: 800
User name: sapuser
system id: DEV
system number:10
XI system details
Client:100
username:xisuper
system id: SXI
system numebr: 00
I request you to please check and help to successfullly completion of this scenario. I request you to please provide me the screen shots of the pre-requiste settings and suggest me the steps to debug the scenario.
Thanks in advance.
Raju

To complete your scenario successfully with better understanding of Idoc adapter
read http://help.sap.com/saphelp_nw70/helpdata/en/ab/bdb13b00ae793be10000000a11402f/content.htm.
for troubleshooting refer http://help.sap.com/saphelp_nw70/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm

Issues in SAP(Idoc)-XI-File scenario

Dear All,
I am working on SAP(Idoc)-XI-File scenario. But in the Receiver agreement i am not able to see the idoc in order to specify some conditions there.
Please suggest if I have to do any settings in order to specify some conditions in the idoc.
Warm Regards,
N.Jain

Hi nishu jain ,
U can specify the conditions in Reciever Determination.
1.Go to Scenarios
2.Choose your business scenario
3.Click Service without party
4.Double click Reciever Determination
5.U wil get screen in which there is a option called Configured Recievers.
6.Click there.then u wil get the screen with
Left Operand Op Right Operand
7.There u can specify the condition.
Reward points if u find this useful.......
Regards,
gyanaraj

Idoc to file scenario general query

Hi All,
I know about the basic settings needed for the Idoc to file scenario.
My query is related the idoc /ALE settings.
I have a scenatio wrking in my system where we have configured the port for B type partner and also the port as XML-HTTP
I can not see any DM(BD64) created for it basically.I want to know that in what scenarios the BD64 configuration is required.
Or it is the case that if we define the BD64 then we do not need to configure we20 and we21, it will be auto configured?
Please let me know the use cases for these different configurations if any.
Thanks in advance.
Regards,
Rahul Kulkarni

Hi Rahul,
BD64 uses mostly IDoc to IDoc scenarios because the IDoc consults the distribution model and determines whether any filter objects are specified for a receiver.
WE20 and WE21 (Partner Profile,Port Definition) we have to define in any scenarios where ECC included.
Thanks,
Seshu.

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.

Configuring IDOC to file Scenario in PI 7

Similar Messages

Maybe you are looking for