cancel
Showing results for 
Search instead for 
Did you mean: 

xi is not picking up file

Former Member
0 Kudos

Hello all,

file is not able to picking by sender adapter. i am sending payload through component monitoring Test Message. i am getting following errow.

Error while sending message: com.sap.aii.af.ra.ms.api.ConfigException: ConfigException in XI protocol handler. Failed to determine a receiver agreement for the given message. Root cause: com.sap.aii.af.service.cpa.impl.exception.CPALookupException: Couldn't retrieve outbound binding for the given P/S/A values: FP=;TP=;FS=ximbbussys;TS=;AN=source_MI;ANS=urn://filetofile;

what is the problem can anybody sugest how to resolve this problem

Thanks

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

>>Couldn't retrieve outbound binding

this means there is something wrong in the binding between the sender or receiver.

check your pipeline steps specially receiver agreement and receiver determination.

the pairing of sender and receiver has not been done correctly

Thanx

Aamir

Answers (3)

Answers (3)

nisarkhan_n
Active Contributor
0 Kudos

the problem might be one of the following

1. Make sure the folder from whcih you are acessing the file has full access (modification rights)

2. Make sure the filename is same as in the Fileadapter you have mentioend.

3. make sure the file adapter is Active...

4. Make sure this CC with File adapter is in teh Sender agrement else it will not pick the data

all these things you can check in the CC monitoring in the RWB.........

your FCC parameter if exist might be wrong.....

check the CC monitoring then you will ge the error what exactly accordingly you can solve

Former Member
0 Kudos

Possible reasons

1. Your communication channels are not working, check their status through RWB monitor

2. Your configuration scenario do not have all necessary entities inside the run time CACHE.

From the error I think second point is more correct.

So once you have checked the first option

Check whether you have tested the scenario using configuration tool.

Update the cache in ABAP and JAVA side

Check all the configuration entities such as interface determination, sender/receiver agreement, mapping etc are inside the run time cache.

If you are cleared all, it will work.

If not working, increase the trace level to 3 from default one

Run the scenario again

You will see more detailed error in TRACE.

Thanks

If you like the answer please make sure point is rewarded.

Former Member
0 Kudos

Hi,

Check your communication channels to see if the Integration Engine field is not set.

If it is missing, add it, activate it and try again.

Also, try a full cache refresh in transaction SXI_CACHE.

Thanks

Colin.