Error while doing Enhanced Receiver Determination

Hi,
My scenario is Fiel->XI->File with enhaced receiver determination that is i should get the receivers dynamically at runtime.
I gave Operation mapping in Receiver determination and created all other objects.
Even if i check message mapping i am getting multiple receivers but, in SXMB_MONI i am getting the following error
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">CX_RD_PLSRV</SAP:Code>
<SAP:P1>Problem while determining receivers using interface mapping: Error when parsing receiver listLength of XML document 144</SAP:P1>
<SAP:Stack>Error when determining the receiver: Problem while determining receivers using interface mapping: Error when parsing receiver listLength of XML document 144 Problem while determining receivers using interface mapping: Error when parsing receiver listLength of XML document 144 Error when parsing receiver listLength of XML document 144 System expected the element 'Receivers'</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Can anyone suggest
Regards,
Sunitha

Hi,
I am getting error in Receiver Determination step only. so, unable to see the receivers.
Is there any option to check that particular message which conists of receivers in PI.
"In every receiver root node only one receiver can exist.
you have to reapeat the root node for every receiver. "
ya i changed the occurance of the message type. In message mapping i am getting multiple root nodes at target but in SXMB_MONI i got that error.
Regards,
Sunitha

Similar Messages

Error while creating Enhanced Receiver Determination

Hi,
My Scenario is File to File and in my scenario i am using Extended Receiver Determination as per requirement.
In Receiver Determination(Extended) even though i am entering Operation Mapping ..an error occured
Checking advanced receiver determination...
Enter a mapping
I thought it is because of Cache refresh ..and i have done it ..But no use..Gettig the same error...
Can anyone please tell me where i went wrong??and How to fix this issue??

I thought it is because of Cache refresh ..and i have done it ..But no use..Gettig the same error...
did you perform a full cache refresh also? If you have Operation Mapping defined with receiverDetermination as target and if it is activated then there should not be any problem in selecting the same in Receiver Determination?

Problem in enhanced receiver determination

hi all
I was doing enhanced receiver determination in that i got following problem
at first i copied abstract interface ReceiverDetermination from SAP BASIS to my component then i created my mapping program containing one udf related to my scenario.I also created one interface mapping but when i went in the directory then
my this mapping is not coming when i have to choose it after clicking to extended receiver determination in receiver determination.
my objects are already activated in design.the udf is also working properly.
Please reply. This is an urgent issue.

Hi-
Check this link
http://help.sap.com/saphelp_nw04/helpdata/en/43/a5f2066340332de10000000a11466f/content.htm

Problem while determining receivers in enhanced receiver determination

i am doing scenario FILE-TO-FILE (with one sender and 2 receivers, dynamic receiver identification based on mapping)using enhanced receiver determination,
it is giving following error in MONI,
Problem while determining receivers using interface mapping
System expected the element 'Receivers'
pls. help me if anybody experienced this scenario,
i am doing this scenario based on the below blog.
/people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16

Have u properly followed the weblog,
Integration Repository Step No 2 and Step No 5
2. In order to use the enhanced receiver determination, create a message mapping which has the target message as Receiver Determination in the SAP BASIS --> http://sap.com/xi/XI/System.
5. Create the Interface Mapping 
U must have checked that ur Xi is on SP 16 or above )
Regards,
Prateek

Intermittent JDBC error in Enhanced Receiver Determination

Hi,
I have an interface that use Enhanced Receiver Determination in PI 7.1 EHP1.
The database is DB2 on i5/os 6.1
Sometimes message ends in error :Error when determining the receiver: Problem while determining receivers using interface mapping: Runtime exception occurred during application mapping com/sap/xi/tf/_HI01_to_ReceiverDetermination_;
But the same message with same values is successfull earlier.
This is not a design problem; the interface is working well 95% of the time.
I found some JDBC error in NWA java logs:
Error in sax handler parsing request: Error when executing statement for table/stored proc. 'table' (structure 'statement'): java.sql.SQLException: [SQL0104] Token "BUSINESS_SYSTEM" was not valid. Valid tokens: FOR SKIP WITH FETCH ORDER UNION EXCEPT OPTIMIZE.
Error when calling an adapter by using the communication channel CC_RECEIVER_JDBC_PIDB2 (Party: *, Service: INTEGRATION_SERVER_PX1, Object ID: cb7ea38fb2ac3a06b12d79f5ade2bcf7) XI AF API call failed. Module exception: (No information available). Cause Exception: 'Error processing request in sax parser: Error when executing statement for table/stored proc. 'table' (structure 'statement'): java.sql.SQLException: [SQL0104] Token "BUSINESS_SYSTEM" was not valid. Valid tokens: FOR SKIP WITH FETCH ORDER UNION EXCEPT OPTIMIZE.'.
Thrown:
com.sap.aii.af.service.api.AFException: XI AF API call failed. Module exception: (No information available). Cause Exception: 'Error processing request in sax parser: Error when executing statement for table/stored proc. 'table' (structure 'statement'): java.sql.SQLException: [SQL0104] Token "BUSINESS_SYSTEM" was not valid. Valid tokens: FOR SKIP WITH FETCH ORDER UNION EXCEPT OPTIMIZE.'.
at com.sap.aii.af.service.api.AdapterAccess.sendMsg(AdapterAccess.java:214)
at com.sap.aii.af.service.api.AdapterAccess.execute(AdapterAccess.java:283)
at com.sap.aii.ibrun.server.lookup.AdapterProxyLocal.execute(AdapterProxyLocal.java:119)
at com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.execute(SystemAccessorInternal.java:76)
at com.sap.aii.mapping.lookup.DataBaseAccessor.execute(DataBaseAccessor.java:74)
at com.sap.aii.mappingtool.flib7.SelectSingle.selectSingle(SelectSingle.java:54)
at sun.reflect.GeneratedMethodAccessor607.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
Any idea? Can high volume cause the JDBC Receiver to fail?
Martin

hi,
you r trying to impliment Lookup for the file adapter which is not synch in nature and hance u r not getting the responce back.
please find the link which deals with how to impliment lookup for file adapter.
https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/file%252blookup%252bin%252budf.
now once u get rhe runtime receiver u can perform enhanced receiver determination (write a simple UDF)
regards,
navneet.

Error in enhanced receiver determination

Hi Experts,
I am trying to implement a scenario in which i have to get the receivers at run time by doing a lookup to a file which stores the destinations.
i am getting the error that no receivers could be determined.
thanks,
Anika

hi,
you r trying to impliment Lookup for the file adapter which is not synch in nature and hance u r not getting the responce back.
please find the link which deals with how to impliment lookup for file adapter.
https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/file%252blookup%252bin%252budf.
now once u get rhe runtime receiver u can perform enhanced receiver determination (write a simple UDF)
regards,
navneet.

Acccount determination error while doing SES

Hi,
I am getting a error while doing SES i.e.
147 Account determination for entry ICOA FR1 not possible.
Can anybody please guide me how to resolve this.
Thanks in advance.
Regards,
Ashish

Hi,
Use t.code:OBYC, enter chaart of account
Click FR1
In next screen enter Val. Gro. Code, Acct Gro. Code, Valuation class and G/L accounts for Dr & Cr and save.
Note: before that u have save the Rules
How to save Ruls:
OBYC-> enter chart of account-> Click FR1->Click Rules
Select the check box of Debit/Credit in accounts , General modification, Valuation Modification, Valuation class Account are determine based on TAB and save.
Regards,

Iam getting any error in infotype 0002 while doing enhancement ...

Dear all
could any one let me know why iam getting this error ,
" TABL HRTIM00WS_PWS_INFTIES was adjusted
Check table HRTIM00WS_PWS_INFTIES (SFCD07/13.06.07/11:34)
Enhancement category for table missing
Enhancement category for include or subtype missing
Field name TIME is reserved (Do not use structure as include in DB table)
Table HRTIM00WS_PWS_INFTIES was checked with warningsif iam doing
enhancement for infotype 0002 ....
i have just added an one custom field ...(zzname , data element is zzname type char 20)as per the business requirement.
regards
vamsi

Iam getting any error in infotype 0002 while doing enhancement .
" TABL HRTIM00WS_PWS_INFTIES was adjusted
Check table HRTIM00WS_PWS_INFTIES (SFCD07/13.06.07/11:34)
Enhancement category for table missing
Enhancement category for include or subtype missing
Field name TIME is reserved (Do not use structure as include in DB table)
Table HRTIM00WS_PWS_INFTIES was checked with warningsif iam doing
enhancement for infotype 0002 ....
when iam activating .................the structure i got the above error...........please urgent i have just added only one field

Enhanced Receiver determination - Fatal Error.

Hi All,
We are using Enhanced Receiver Determination.
We are getting Fatal error in SXMB_MONI though our Intarface mapping is working correctly but when tried testing from runtime work bench we are getting error.
The error message shows
SAP:Code area="RCVR_DETERMINATION">CX_RD_PLSRV</SAP:Code>
<SAP:P1>Problem when determining the receiver when using the Interface Mapping: During the application mapping com/sap/xi/tf/_Find_Receiver_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: Fatal Error: com.sap.engine.lib.xml.parser.Parser~</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
Please suggest any setting needs to be done.
Thanks
Regards,
Ashwin

Hi Ashwin,
Just check if the condtion is correct. Also, look for some typo error as the name is case sensitive.
Also, trigger a delta cache refresh for this receiver determination object after modifying the object.
This should solve your problem.
Regards, Gaurav.

Problem with Enhanced Receiver Determination

Hi Friends,
I am doing the enhanced receiver determination scenario, But it is giving the
error in SXMB_MONI like this
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">CX_RD_PLSRV</SAP:Code>
<SAP:P1>Problem while determining receivers using interface mapping: Fehler beim Parsen der Empfänger-Liste.Länge des XML-Dokuments 264</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error when determining the receiver: Problem while determining receivers using interface mapping: Fehler beim Parsen der Empfänger-Liste.Länge des XML-Dokuments 264 Problem while determining receivers using interface mapping: Fehler beim Parsen der Empfänger-Liste.Länge des XML-Dokuments 264 Fehler beim Parsen der Empfänger-Liste.Länge des XML-Dokuments 264 System expected the element 'Receivers'</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
this is error is coming in the SXMB_MONI
THE DATA type(Receivers) we create in basis component is comes automatically?
are we have to create?
in my scenario i creted manually,
is it compulsory to specify the properties for the party and agency?
is it compulsory to create 2 Receiver structures in msg structure?
if yes what r those, actually i used from sap.help.com,
Can any body should give me the solution for this, regarding mapping and configuration , if anybody experienced this scenario. Pls . give me the guidelines to do.

Hi,
the mapping creating the receiver list is not producing the required element "Receivers" from Namespace "'http://sap.com/xi/XI/System". Look to the operation mapping given in the enhance Receiver Determination (IB Directory) and detect the corresponding mapping program (ESR). Copy the source payload from MONI, test the mapping program and correct it.
Regards,
Udo

Enhanced Receiver Determination with RFC Lookup

Hi All,
I am building an interface with Enhanced Receiver Determination. Scenario would be that the Receiver Systems would be stored in a Z table in SAP ECC, and in PI Receiver Determination I am doing an RFC look up to find the systems, and using those.
I built the mapping for Receiver Determination, and it tested fine in ESR. But while Creating the Receiver Determination in Integration Directory, After I specify the Receiver mapping name, and put the RFC channel name for the RFC parameter, it doesnt allow me to save the Receiver Agreement with a run time error message
"Link from Receiver Determination | <Sender>| <Interface>| * | * to object type "Channel" with role "122474913b1311deaadb42057dd8b002" is not permitted"
My question is a) if the RFC lookup allowed in the mapping for Receiver Determination?
B) if yes, am I missing someting or is it a system issue?

i have seen Enhanced RD with lookups that work. Have to say it was not a RFC lookup used but rather a DB look in one of the implementations i had worked with. But still I really dont think a RFC lookup should be an issue.
Troubleshoot the lookup mapping to be working other than in the enhanced RD (i.e independently) .
if you head no where, i suggest opening a OSS note.

Error While doing ABT1N transaction

Hi,
I am facing the below error while doing ABT1N in Asset Accounting.Please help me in fixing this Issue.
Error Message -No depreciation area for receiving the revenue
Message no.AAPO149
Diagnosis
You tried to post a retirement on asset 1000 100007-0.You entered transaction type 300,in which the retirement with revenue indicator is not set
You tried to transfer asset 1000 100007-0.According to transfer variant 0001,none of the areas on the asset uses a transaction type for retirement with revenue
In both of these cases, you are not allowed to enter revenue or make specifications for the determination of revenue.
Proceedure
Check the transfer variant and check your entry
please do the needful
Thanks
Supriya

Hello,
You will have a check box for the same.
Double click on transaction type, you will see the check box for revenue.
Otherwise, tomorrow I will get back to you once I am in front of the system.
Regards,
Ravi
Edited by: Ravi Sankar Venna on May 5, 2009 7:53 PM

Enhanced Receiver Determination in PI7.1

Hi,
We have a requirement where in we have to use the Enhanced Receiver Determination for one of our scenarios for choosing the receiver.We are on PI7.1.
As of now,we have mapped a constant rcvr(Test_Supplier) to the Service in the message mapping from our source to the target -Receivers, as we do for Enhanced Receiver determination.The rcvr determination choosing Extended and the correct Operation mapping has been configured.The coresponding Interface determination and Receiver agreements have also been configured.
When trying to test this by posting a payload through RWB,we get the No_Receiver_Case_Async error.
Is it necessary to map the party field also in the message mapping?Am I missing something here?Kindly advise.
Thanks and Regards,
Induja

When trying to test this by posting a payload through RWB,we get the No_Receiver_Case_Async error.
Is the Mapping which you developed to determine the receiver(s) able to give the appropriate output? Apart from cache problem, this can also be the issue when the mapping does not produce i.e. no proper service is populated in the corresponding node....the service must be actually present (and active) in ID
Regards,
Abhishek

Enhanced Receiver Determination in Synchronous Scenario

Hi,
my synch scenario with standard Receiver determination is working fine.
the service interfaces i used are SI_OutSynch_EmpInfo_Request and SI_InbSynch_EmpInfo_Provide.
I am now trying to apply enhanced Receiver determination for the same synch scenario.
For this, in ID, in my Receiver Determination object i selected the radio button Extended, then it is asking for an operation mapping. infact it is asking for an OM with sender Interface=SI_OutSynch_EmpInfo_Request (from my swcv) and Receiver Interface = ReceiverDetermination (from SAP BASIS swcv)..
So I logged into ESR, and created an OM_test_EnhancedRD, with sourceInterface=SI_OutSynch_EmpInfo_Request (from my swcv) and TargetInterface = ReceiverDetermination (from SAP BASIS swcv)
But when i tried to activate the OM_test_EnhancedRD, it is not getting activated, and giving below error:
Interface modi are different. Source interface Operation SI_OutSynch_EmpInfo_Request | http://mycomp.com/myns is synchronous. Target interface Operation ReceiverDetermination | http://sap.com/xi/XI/System is asynchronous
So my queries are:
1. is for synch scenarios, if receiver information is part of the request payload, how can we apply the extended Receiver Determination, so that the Receiver is determined dynamically.
2. or is there any synch version of ReceiverDetermination (from SAP BASIS swcv) available.
thanks in advance.
madhu.

in this case, does SAP provide synch version of ReceiverDetermination SI, so that we can use that in OM for enhanced Receiver Determination.
If you have a look at the blog-reference given by Ravi you will find a way on how to make the ReceiverDetermination Si synchronous or work with the same async SI.....for quick reference below is the way mentioned in the blog:
From the blog:
Option 1:
A quick and easy way to allow for synchronous enhanced receiver determination setup is to circumvent the check that prevents
a synchronous interface to be matched to an asynchronous interface in an interface mapping. This can be done simply by
manually entering the name and namespace of the ReceiverDetermination interface object (e.g. 'ReceiverDetermination'
and 'http://sap.com/xi/XI/System' respectively) for the target/receiver interface in the interface mapping, but leaving the value for
the Software Component Version empty.
Option 2:
Select Modify and then change the mode to synchronous. Since a synchronous interface requires an input message as well, you
can reuse the Receivers message type used in the output message - it doesn't really matter as long as some message type is
used.
Both of the above options are available under the Applying the Workarounds section of the blog
Regards,
Abhishek.

Enhanced Receiver Determination - Hard-coded Receivers??

Hi mates,
I need to implment enhanced receiver determination. I see from the documentation and blogs that I need to hard-code the receiver service i.e. specifying the value in message mapping.
What happens if I transport this mapping program to QA or PROD system? Do I need to take care of the Receiver system names in QA & PROD in the mapping.
Isnt it hard-coding?
Is there any better way of doing this, apart from using the BPM.
I appreciate your inputs.
thx in adv
praveen

Hi,
If you are using enhanced receiver determination, you are going to provide Receiver Details in the Integration Directory right ? If so, anyway while doing Transport from the Dev to QA, you are creating a Transport Target for the business systems.. So here in the configuration it will take care ...
http://help.sap.com/saphelp_nw2004s/helpdata/en/ef/a21e3e0987760be10000000a114084/content.htm
But, I am not sure where are you refering about Hard-Coding ?
Rgds,
moorthy

Error while doing Enhanced Receiver Determination

Similar Messages

Maybe you are looking for