on 05-23-2008 10:08 AM
Hi All,
I am completeing teh 'File --> XI -->IDOC to R/3' scenario.
Have manged to complete teh IR and ID config as per the various threads in SDN.
I am using FCC in the Sender File adapter (which I assume will read the file data and convert to XML data). When this channel is activated, it gives me the error 'No suitable sender agreement found'.
As per various posts in sdn, this scenaruio may not need sender agreement as XI is finally using IDOC adapter to send data to R/3.
Am I correct in assuming that ??
Could you help point any potential missing config.
For your reference:
The comm Channel used to read file data is using File adapter (marked as SENDER/NFS/FCC/Integration server)
Appreciate your feedback.
Thanks
Shirin
Am I correct in assuming that ??
No
Ur sender is file system and not idoc. Sender agreement is mandatory in ur case
Regards,
Prateek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Shrin,
I am completeing teh 'File --> XI -->IDOC to R/3' scenario.?
You have to create Sender Agreement & Receiver Agreement.
*Sender Agreement: You have to give your
Sender:
Party:...........
Service:.........
Interface name.......
In parameters you have to give:
Sender Communication Channel Name:...........................
Receiver Agreement: In Display receiver Agreement:
You have to give
Sender:
Party :...............
Service:...............
Receiver:
Service:.......
Interface:......
Namespace:....
Receiver Communication Channel:...........
Thanks,
Satya Kumar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
You r working on File to IDoc Scenario..Here sender is the File Sys.. So u shoud create sender Agreement and sender comm channel..
Reward points if helpful..
Regards,
Soumya
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
your sender is file and receiver is idoc.
use file as outbound asyn. and idoc as inbound asy.
Create sender agreement for file.
Create receiver agreement for idoc.
create file sender communication channel
create idoc receiver communication channel.
take help for scenario form these links :
File To IDOC - Part1 (SLD and Design):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
File To IDOC - Part2 (Configuration):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
File To IDOC - Part3 (Steps required in XI and R3):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)
Regards,
Sandeep Kaushik
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Your scenario is File To IDoc,
Then you will need sender agreement that is pointing to sender file communication channel, also receiver agreement for receiver IDoc channel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
As your sender is file you should have a sender agreement.
if your sender system is R/3 then, there is no need of sender agreement..
reward points if it is helpful
Thanks,
Madhu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
chk for ALE settings....
Steps for ALE settings:-
Steps for XI
Step 1)
Goto SM59.
Create new RFC destination of type 3(Abap connection).
Give a suitable name and description.
Give the Ip address of the R3 system.
Give the system number.
Give the gateway host name and gateway service (3300 + system number).
Go to the logon security tab.
Give the lang, client, username and password.
Test connection and remote logon.
Step 2)
Goto IDX1.
Create a new port.
Give the port name.
Give the client number for the R3 system.
Select the created Rfc Destination.
Step 3)
Goto IDX2
Create a new Meta data.
Give the Idoc type.
Select the created port.
Steps for R3.
Step 1)
Goto SM59.
Create new RFC destination of type 3(Abap connection).
Give a suitable name and description.
Give the Ip address of the XI system.
Give the system number.
Give the gateway host name and gateway service (3300 + system number).
Go to the logon security tab.
Give the lang, client, username and password.
Test connection and remote logon.
Step 2)
Goto WE21.
Create a port under transactional RFC.(R3->XI)
Designate the RFC destination created in prev step.
Step 3)
Goto SALE.
Basic settings->Logical Systems->Define logical system.
Create two logical systems(one for XI and the other for R3)
Basic settings->Logical Systems->Assign logical system.
Assign the R3 logical system to respective client.
Step 4)
Goto WE20.
Partner type LS.
Create two partner profile(one for XI the other for R3).
Give the outbound or inbound message type based on the direction.
Step 5)
Not mandatory.
Goto BD64.
Click on Create model view.
Add message type.
Step 6)
Goto WE19
Give the basic type and execute.
fill in the required fields.
Goto IDOC->edit control records.
Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
Click outbound processing.
Step 7)
Go to SM58
if there are any messages then there is some error in execution.
Goto WE02.
Check the status of the IDOC.
Goto WE47.
TO decode the status code.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
Xi
IDx5(Idoc check)
SU53(authorization check)
reward points if helpful...
Prashant
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.