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?

Similar Messages

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

Error while creating enhancement section

Hi,
I am trying to create a enhancement section in my ABAP program, but i am getting a message 'Defines an enhancement sppot in another object'.
Here is the process i followed.
I have created a enhancement spot in my package zkk_pkg in se80 and activated.
i have created a program in se38 editor. In that program i am selecting a section of code and then right-click -> enhancements -> create .
Then i am getting create enhancement option where i am selecting enhancement section and giving a new name ZKK_ES1. Also in the enhancement spot section i am giving the enhancement spot i created earlier and the package name as an enhancement section should be assigned to a spot.
When i give these parameters and click OK , it shows the message 'Defines an enhancement sppot in another object'.
Can anyone let me know where i am going wrong.
Thanks in advance
Kamal

hai kamal,
u can follow this procedure for creating enhancement spot,
instead of creatign enhancement spot in se80
just select the code
right click and do create enhancement
and u give the name of the enhancement section and also the enhancement spot iand also the package where u want to save in the pop up window
it will create u the spot and point of enhahcnement
and save , it will create the enhancement spots for ur code
hope it will solve ur prob

Error While creating enhancement Spot

Hello all,
I am doing some enhancement code using new enhancement framework for SAP HR infotype 0002 and 0006. I am searching the enhancement spot in relevant program screen, but while enhancing (Shift+F4), it is showing me a message saying "Object still in upgrade mode. Finish the upgrade first".
My basic requirement is to change the screen values before display.
Is anybody gone through such error?? Please help.
Thanks,
Prashant

Please Share the answer.
Regards.
Mariano Billinghurst

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.

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.

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.

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.

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

Error while creating absence record in PA30 using 2001 infotype

Hi all,
iam getting an error while creating absence record for infotype 2001for LOP(unpaid)
error : No quota available for att./abs. 6000 for pers. no. 61000052 between 31.12.2009 and 31.12.2009
i have did
Create a absence type LOP
Determine Entry Screens and Time Constraint Classes
Define Counting Rules
Assign Counting Rules to Absence Types
Payroll: India>>Absences>Describe Absence Valuation Rules 01 Unpaid Leave
Group Absences for Absence Valuation>>Absence valuation rule>>F4 country grouping 40>> assign 01Unpaid Leave
please solve this

Actually I don't know how your system is configured.
However, the error you're receiving seems you have assigned the absence type to a quota type.
Please go to your counting rule and check whether Deduction rule - absence quotas - within entitlement field is filled.
If yes, get the deduction rule value and go to
SPRO Time man- Time data rec - Absences - Absence Cat - Abs counting - rules for counting (new) - deduction rules for abs quotas and check the quota type in here.
If there is a quota assignment in place, before creating an IT2001 you need to create a IT2006 for that specific time period.
Or, you need to delete the quota assignment via two config steps mentioned above.
Regards,
Dilek

Recieving ORA-01722 invalid number error while creating a materialized view

Hi,
I am receiving a ORA-01722 invalid number error while creating a materialized view. when run the select statement of the view i don't get any error, but when i use the same select statement to create a materialized view i receive this error. Could any please help in resolving this error. Here is the code i am using to create a materialized view.
CREATE MATERIALIZED VIEW MV_EBS_CH_CLOSED
REFRESH FORCE ON DEMAND
AS
SELECT DISTINCT kr.request_id, org.org_unit_name,
ebs_ch_ticket_type (kr.request_id) ticket_type,
DECODE
(kr.status_code,
'CLOSED_SUCCESS', kr.last_update_date,
'IN_PROGRESS', (SELECT MAX (start_time)
FROM ebs_ch_datastore ecd1
WHERE kr.request_id = ecd1.request_id
AND workflow_step_name =
'Final BA Review and Deployment Exit Criteria')
) closed_date,
substr(krhd.visible_parameter12,1,10) siebel_start_date,
kr.creation_date itg_start_date
FROM kcrt_requests kr,
kcrt_request_types krt,
kcrt_req_header_details krhd, kcrt_request_details krd1,
(SELECT koum.user_id user_id,
DECODE (koup.org_unit_name,
'IT Implementations', 'CHS - Service Management BA',
koup.org_unit_name
) org_unit_name
FROM krsc_org_unit_members koum, krsc_org_units koup
WHERE 1 = 1
AND 'Y' = koup.enabled_flag
AND koum.org_unit_id = koup.org_unit_id
AND EXISTS (
SELECT 'X'
FROM krsc_org_units kouc
WHERE koup.org_unit_id = kouc.org_unit_id
START WITH kouc.parent_org_unit_id =
ANY (SELECT org_unit_id
FROM krsc_org_units krsc_org_units1
WHERE 'Clearinghouse' =
org_unit_name)
CONNECT BY kouc.parent_org_unit_id =
PRIOR kouc.org_unit_id)
UNION
SELECT kou.manager_id user_id,
DECODE
(kou.org_unit_name,
'IT Implementations', 'CHS - Service Management BA',
kou.org_unit_name
) org_unit_name
FROM krsc_org_units kou
WHERE 'Y' = kou.enabled_flag
START WITH kou.parent_org_unit_id =
(SELECT org_unit_id
FROM krsc_org_units krsc_org_units2
WHERE 'Clearinghouse' = org_unit_name)
CONNECT BY kou.parent_org_unit_id = PRIOR kou.org_unit_id) org
WHERE krt.request_type_id = kr.request_type_id
AND krt.request_type_name IN ('Bug Fix', 'IT Enhancement')
and kr.REQUEST_ID = krd1.request_id
and krd1.batch_number = 1
AND kr.request_id = krhd.request_id
AND org.user_id in (krd1.parameter4, krd1.parameter5, krd1.parameter7)
AND ( 'CLOSED_SUCCESS' = kr.status_code
OR 'IN_PROGRESS' = kr.status_code
AND kr.request_id IN (
SELECT request_id
FROM (SELECT DISTINCT request_id,
MAX
(start_time)
closed_date
FROM ebs_ch_datastore
WHERE 'Final BA Review and Deployment Exit Criteria' =
workflow_step_name
GROUP BY request_id))
Thanks,
Shaik Mohiuddin

This error occurs when you try to create a materialized view , but if you run the sql the results are perfectly fine. Well it happend to me also and to fix this I made sure all the coulmns have the same data type which are used in joins or in where clause.
use
where
to_number(col1)=to_number(col2) and to_number(col3)=to_number(col4)
hope this helps..

Error while creating document numbering series via SDK add on

Dear Experts,
We receive the following error while creating the document numbering series through the SDK add on
[Microsoft][SQL Server Native Client 10.0][SQL Server]The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Too many parameters were provided in this RPC request. The maximum is 2100.
From the above error message I can suspect the following possibilities
1. The limit for the document numbering must be less or equal to 2100.
2. There is a problem in the coding in SDK where it does not allow more than 2100 lines in the database.
We tried to create manually for the same fiscal year and period indicator disconnecting the add on, the same error occured.
Then we created a seried for a single document with the period indicator for the next fiscal year, it allowed.
After creating the document numbering for the next fiscal year, we were able to create the numbering for the previous year also.
Kindly help us on how to solve the same.
With regards,
Yeshwanth Prakash

Hi
You have, as far as i can determine without seeing the template,defined no Part Appraiser Column (PAPP) in your template. But you have defined a function on the template to automaticly default the part appraisers.
On the Appraisal document persons (appraiser / appraisee) are getting defaulted as part-appraisers although no part appraisal column excist,and therefor 00 Part Appraisers are allowed. This gives the error. Remove the Part Appraisers default functionality from the template and this problem will be solved.
FYI: The reason why this doesn't give a business check error is that the functions to default participants are BAdI's and we have no means of determining wether or not a BAdI implentation will create an inconsistency on the appraisal document.
Also, the reason that it occurs as a S message and not as E or W is because of programming restrictions in combination with messages. All errors on the Appraisal Document will come as 'S' messages.

Error while creating delivery with reference to STO

Hi,
I am getting the following error while creating the delivery with reference to STO
Document is incomplete: You cannot save the delivery
Diagnosis:
When the system checked whether saving delivery was
permitted, it determined that the requirements stored in
Define Incompletion Procedures for this document do not
allow this subsequent function.
I have checked the following already:
1. Maintained shipping data for both the supplying and receiving plants.
2. Shipping tab exists in the PO
3. Shipping point determination is checked.
4. Customer masters created for both supplying plants and receiving plant for the sales area created for STO
5. Material master is available in both receiving and supplying plants.
It is working fine in one client. and giving a problem only in the other.not able to figure out where the error is. appreciate your suggestions
regards
joe

Hi Joseph,
First go to transaction "VUA4" and see what is the incompletion procedure asigned to your delivery type. Then go to
"OVA2" and see what are the fileds maintained in incompletion procedure of the delivery type and the status groups assigned to them. Now you go to "OVA0(ZERO) and see whether the status group allows to save the delivery. If it doesn't you can untick that check box. But if this is a live system , i doubt if you would be bale to do that. Any way one of the possible causes is storgae location missing. Kindly pelase let me know If you need any more infromation on this.
Regards,
Ram Pedarla

Enhanced Receiver Determination for synchronous interface.

Hello!
Was anyone faced with the Enhanced Receiver Determination? When I try to create
the definition of the Interface Mapping, I get the error:
"Interface modi are different. Source interface Message Interface MI_My_sync_iface | urn:my is synchronous. Target interface Message Interface ReceiverDetermination | http://sap.com/xi/XI/System is asynchronous"
Thank you.

Hi ,
U can go through below limks :
Illustration of Enhanced Receiver Determination - SP16
SAP NetWeaver Process Integration: Enhanced Receiver Determination for Synchronous Scenarios
Enhanced Receiver Determination in SAP XI - Exchange Infrastructure - Wiki
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/enhanced%2breceiver%2bdetermination%2bin%2bsap%2bxi
Thanks

Error while creating Enhanced Receiver Determination

Similar Messages

Maybe you are looking for