cancel
Showing results for 
Search instead for 
Did you mean: 

Call inbound Proxy error in ERP/SRM and PI

Former Member
0 Kudos

Hi guys

I am trying to transfer PR from ERP6.0 EHP4 to SRM7.0 using CPPR scenario.

I configured ERP/SRM and PI configuration in Integration directory.

I get below error in XML at ERP/SRM AND PI

RCVR_DETERMINATION">NO_RECEIVER_CASE_BE

Error Text: No receiver could be determined

In SRM, Inbound Message(reciever) is green but Call Inbound Proxy is giving below error.

<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing! <Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>

<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>

I tested configuration in Integration directory.

Sender aggreeemnt is green

Reciever determination is red and giving below error.

Internal Error : You do not have sufficient authorization for this operation.

Can you please tell me what authorization is required in this case.

How to debug it.

Regards

Chandra

Edited by: princeck on Dec 19, 2010 3:41 PM

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Dear Chandra,

In your Scenario Sender Agreement is not required, as it is Proxy (XI ) based scenario. For this you need to create a RFC Destination of type H and maintain the same in the SXMB_ADMN of the Sender system that is ERP 6.0.

Regarding the internal error:

In the RFC Destination of type H pointing from ERP to PI you should use user credentials to pass the XML message to PI Integration Engine. For the user which you are using in RFC Destination please check the roles/authorizations similar to the User roles and Authorization for PIAPPLUSER in PI.

Some time even though PIAPPLUSER is created in PI you need to check the Authorization profile for this user.

Please take the help of you Basis consultant if required.

Regards

Praveen K

Former Member
0 Kudos

Hi Praveen

Thanks for your reply.

->In ERP RFC dest://XI_INTEGXXXX_CON is created and assigned in tr-cd sxmb_adm.

Path Prefix is set as /sap/xi/engine?type_entry.

->In PI sxmb_adm, i assigned http://hostfqn:port/sap/xi/engine?type=entry to IS_URL.

Pls correct me if anything wrong above.

In PI user PIAPPLUSER i have below roles

SAP_BC_WEBSERVICE_PI_CFG_SRV

SAP_XI_APPL_SERV_USER

Z:AAES_XI_APPL_SERV_USER

and profiles

T-SI560008 Profile for role Z:AAES_XI_APPL_SERV_USER

T_BI560033 Central webservice configuration

T_YB250030 Process integration:Service user for Application Systems.

In ERP user PIAPPLUSER i have below roles

SAP_BC_WEBSERVICE_CONFIGURATOR

SAP_XI_APPL_SERV_USER

and Profiles

T_YB250030 Profile for Role SAP_XI_APPL_SERV_USER

Can you pls advice exactly what should be done.

i am logged with C_user and executing the PR transfer. any role/profile has to be given for my user also?

Pls suggest.

Regards

Chandra

Former Member
0 Kudos

Hi Chandra,

You have created every thing what is supposed to be created.

But to make sure parameters/authorizations, please check the following:

1. RFC Destination XI_INTEGXXXX_CON in ERP

Please check User you are using in this RFC Destination: whether C_User/PIAPPLUSER

(Note: This user must be available in PI)

If you are using PIAPPLUSER then check point no 2.

If you are using C_User (Dialog user) then this user must be available in PI and corresponding roles/Authorizations (similar to PIAPPLUSER).

2. I think you have sufficient Authorizations generated for user either C_user/PIAPPLUSER,

Please double click each Role like SAP_XI_APPL_SERV_USER and check authorization tab. (You should see gree color for this)

In the next tab Assigned User either C_user/PIAPPLUSER should be available for this Role.

Let me know if you still face difficulty.

Regards

Praveen K

Former Member
0 Kudos

Hi

1) ST22 shortdump occurred in ERP

CALL_FUNCTION_NOT_FOUND.

Error analysis

The program SAPMSSY1 contains the CALL FUNCTION Statement.

The name of the function maodule to be called is "BBP_GET_SWITCH_STATE_RFC"

No function module exists with name "BBP_GET_SWITCH_STATE_RFC"

Information on where terminated

Termination occurred in ABAP program SAPMSSY1 in REMOTE_FUNCTION_CALL

The main program was SAPMSSY1.

2) My SLDCHECK is successfull in ERP.

3) Pls find how i have done setting in ID>

Go to Business system setting.1.Selected Business System BC_MM_MXX_594

2.Create communication channel(Gen_Rec_xi) as Receiver

for above Business system BC_MM_MXX_594.

-Use adapter type XI, http://sap.com/xi/XI/System SAP Basis7.xx and RFC MXX_Integration,

1.Selected Business System BC_SRM_SXX_300

2.Create communication channel(Gen_Rec_xi) as Receiver

for above Business system BC_SRM_SXX_300.

-Use adapter type XI, http://sap.com/xi/XI/System SAP Basis7.xx and RFC SXX_Integration.

-->>one doubt here? Should i have to create Comm channel for sender type also from ERP and SRM? pls confirm.

I created object in Integration directory as follows.

Create Object by selecting Business System BC_MM_MXX_594.

1)Selected Internal communication

2)Reciever Determination : BC_MM_MXX_594 PurchaseRequestERPSourcingRequest_Out

3)Specified Interface determination : BC_MM_MXX_594 PurchaseRequestERPSourcingRequest_Out BC_SRM_SXX_300.

4)Specified Reciever agreement BC_MM_MXX_594 BC_SRM_SXX_300 PurchaseRequestERPSourcingRequest_in(communication channel selected is Gen_Rec_xi)

5)Generated Objects and saved as CPPR_scenario.

6)Activated all objects created in CPPR_Scenario.

>> I think i did not use Process integration model using ESR. I selected

Can i delete this scenario and create new one using Process integration model?

4)I got 3 xml messages each created in ERP.

Inbound Message(Sender) is green, But we have two other messages which is red and gives

RECV_Determined error.

In SRM, i get one Inbound message(reciever) and call inbound Proxy is giving application error (Application-Error exception return from pipeline processing).

Looks like XML with PR Data from ERP is sent to SRM XML message. but gives error.

I can see the PR datas in SRM at XML having Inbound message(Reciver) -> Payloads(application/xml)

Regards

Chandra

Former Member
0 Kudos

Hi Chandra,

It looks you are clubbing all your erros and getting confused with Integration (sorry to say this)

let me help you out step by step.

1. Configuration of Objects in PI

Go to Business system setting._1.Selected Business System BC_MM_MXX_594

2.Create communication channel(Gen_Rec_xi) as Receiver

for above Business system BC_MM_MXX_594.

-Use adapter type XI, http://sap.com/xi/XI/System SAP Basis7.xx and RFC MXX_Integration,

1.Selected Business System BC_SRM_SXX_300

2.Create communication channel(Gen_Rec_xi) as Receiver

for above Business system BC_SRM_SXX_300.

-Use adapter type XI, http://sap.com/xi/XI/System SAP Basis7.xx and RFC SXX_Integration.

With this I can understand that you are configuring two Interfaces as follows :

a. BC_MM_MXX_594 To SAP PI To BC_SRM_SXX_300.

b. BC_SRM_SXX_300 To SAP PI to BC_MM_MXX_594.

If this is correct then you should have Two receiver determinations and Two interface determinations and Two receiver agreements.

If this is incorrect then you must be configuring only one scenario BC_MM_MXX_594 To SAP PI To BC_SRM_SXX_300.

In this case you don't need Create communication channel(Gen_Rec_xi) as Receiver

for above Business system BC_MM_MXX_594.

Just reply which one is true then we can proceed.

Regards

Praveen K

Former Member
0 Kudos

Hi Praveen.

Thanks for your reply.

Yes i am really confused.

Actually my requirement is to check only one scenario(sending PR from ERP to SRM using sourcingrequest)

->configuring only one scenario BC_MM_MXX_594 To SAP PI To BC_SRM_SXX_300.

I checked the PI user, PIAPPLUSER is used for RFC and having authorization green.

But in SMR to PI RFC is having different user PIISUSER. Pls let me know if wrong.

In SXMB_Moni, I get three messages in ERP.

2-Red xml message saying RECV_DETERMINATION/NO_RECEIVER_CASE_BE error

1 Message says processes successfully with black and white flag.

In PI i get 2 messages

1-Red xml message RCVR_DETERMINATION">NO_RECEIVER_CASE_BE error

1 message says Processed succesfully with black and white flag.

In SRM i get 1 message

1-red xml message saying Application-Error exception return from pipeline processing

Can we able reduce the error first from ERP to PI?

can you Pls help me the step to check one by one.

Regards

Chandra

Edited by: princeck on Dec 20, 2010 7:48 AM

Edited by: princeck on Dec 20, 2010 8:17 AM

stefan_grube
Active Contributor
0 Kudos

> Can we able reduce the error first from ERP to PI?

There is no error in ERP, there is only an error in PI.

> 1-Red xml message RCVR_DETERMINATION">NO_RECEIVER_CASE_BE error

This means, there is no receiver determination for this message.

Check your entries in Integration Directory

Former Member
0 Kudos

Hi Stefen

Can you pls tell me exactly what has to be checked in Reciever determination.

Ofcourse i have not used any condition.

Regards

Chandra

Former Member
0 Kudos

Hi Chandra,

As per your details:

1. "SMR to PI RFC is having different user PIISUSER. Pls let me know if wrong" This is not required in SRM as your interface is going from PI to SRM.

so you need to create RFC Destination of type H in PI pointing to SRM and in PI ID SRM Receiver Communication Channel give this RFC Destination name.

See you are mixing 3 runtime instances.

1. with 2 Receiver Determination errors, and 2. 1 successfull message in PI.

This is another confusion, If you have Receiver Determination error in PI a Message can't reach to SRM(as it is receiver).

I think your receiver determination is working fine, (if this message is latest in PI) (Sorry to say this: Stefen)

To remove the confusion just execute scenario again in ERP and note the message ID and check the same Message ID status in PI and SRM. In this way you can easily track your error for one Message ID.

So I request you to execute the scenario in ERP and let me know the status:

1. If it is giving Recevier Determination error in PI then look for the solution given by Stefen.

2. If it is successful message in PI then there should be some mistake in SRM end.

Regards

Praveen K

Former Member
0 Kudos

Hi Praveen

I executed again and checked as you said.

First red error in ERP and PI messages ids are same.

ERP - 00188B8B-C3C0-1EE0-8380-ED25017FE4C2

PI - 00188B8B-C3C0-1EE0-8380-ED25017FE4C2

Second red error in ERP and PI message ids are same

ERP- E00C076A-83A3-8FF1-B78E-0024E83A1B0D

PI - E00C076A-83A3-8FF1-B78E-0024E83A1B0D

Above all errors indicate below error message

<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_BE</SAP:Code>

<SAP:Stack>No receiver could be determined</SAP:Stack>

and i can see SRM also having xml message

with error "Application-Error exception return from pipeline processing"

Also I checked in Reciever determination.

Communication component :BC_MM_MXX_594

Interface :purchaseRequestERPSourcingRequest_Out

Namespace: http://sap.com/xi/APPL/GLobal2

Receiver

Communication party and component is *
->Configuration overview->Receiver
Click BC_SRM_SXX_300
Click PurchaseRequestERPSourcingRequest_in
Type 					Object
sender Agreement
Sender Communication channel	
Reciver determination		BC_MM_MXX_594|PurchaseRequestERPSourcingRequest_Out
Interface Determination 	BC_MM_MXX_594|PurchaseRequestERPSourcingRequest_Out|BC_SRM_SXX_300
Reciver Agreement 		BC_MM_MXX_594|BC_SRM_SXX_300|PurchaseRequestERPSourcingRequest_in
Reciever Communication channel |BC_SRM_SXX_300|Generated ReceiverChannel_XI

Pls ask me if any details required.

Pls let me know what do you think of this.

Regards

Chandra

Former Member
0 Kudos

Hi guys

I checked Communication channel "GenReceiverChannel_XI" in Integration directory.

Its set as you explained above.

But the RFC created in PI to SRM has logon setting with user ALEREMOTE.?

Need to be PIAPPLUSER? pls confirm.

Regards

Chandra

Former Member
0 Kudos

Hi Chandra,

Good, Can you check RFC Destination of type H working fine in SAP PI pointing to SRM. Make sure you have used the same RFC Destination in SRM Receiver Communication Channel.

Let me know status.

Regards

Praveen K

Former Member
0 Kudos

Hi Praveen

yes, RFC type H is connecting to SRM from PI.

Giving Status HTTP response 500 &

Status Text Empty HTTP request recieved.

But the user is ALEREMOTE.

Regards

Chandra

Former Member
0 Kudos

Hi Chandra,

Good, Its alright what ever user you are using for this RFC Destination as long as it have the roles and authorizations similar to PIAPPLUSER of PI. Note the User you are using here should be available in SRM.

Next check Receiver Agreement and use Receiver Communication channel in the Receiver Agreement, make sure you use the above RFC Destination in the Receiver Communication Channel.

Let me know the status;

Regards

Praveen K

Former Member
0 Kudos

Hi Praveen

I copied PIAPPLUSER roles and authorization into my C-user used in RFC destination.

Next check Receiver Agreement and use Receiver Communication channel in the Receiver Agreement, make sure you use the above RFC Destination in the Receiver Communication Channel

-->> I found Receiver agreement was already there for ERP(594) to SRM(300), However i have updated the communication channel and activated it.

But still the same error. I think the error is somewhere...

pls advice.

Regards

Chandra

Former Member
0 Kudos

Hi Chandra,

In the RFC Destination created in SAP PI pointing to SRM the path prefix as /sap/xi/engine?type=entry

Please double check.

Regards

Praveen K

stefan_grube
Active Contributor
0 Kudos

Check in SXMB_MONI, if you find the same data in Header part in the message for: Sender, interface, namespace as you have applied in receiver determination.

Check also of cash is up to date.

And it is not an issue between ERP and PI, as you see the same messages in both system.

The issue is inside PI configuration.

Former Member
0 Kudos

Hi Stefan

Thanks for your reply.

Looks like PR data is sent to SRM. because i can see the PR datas in SRM XML payloads.

However the Call inbound proxy error is still exist.

Can you tell me if any SRM setting is required in SRM to clear this error and create PR in SRM shopping cart.

Regards

Chandra

Former Member
0 Kudos

Hi Stefen,

As per his communication he confirmed that, Message reached successfully in SAP SRM.

But he is getting following error:

System-Error Application-Error exception return from pipeline processing in inbound proxy processing.

I hope this could be becuase of application level activity that need to be for this SE_SOURCING_ENCHANCEMENT Interface.

Note: Pipe line URL is also correct in PI RFC Pointing to SRM.

Any other inputs Please...

Regards

Praveen K

stefan_grube
Active Contributor
0 Kudos

You have two messages.

- one is stuck in PI due to missing configuration of receiver determination

- one is failing inside SRM.

For the SRM issue, check error text and trace.

As this is an application error, you might have wrong message data.

Former Member
0 Kudos

Hi Stefan

Thanks for your reply.

I think PI error is irrelevant for my scenario.

But in SRM error, trace says APPLICATION ERROR exception return from pipeline processing.

so do you think its because of PR data problem?

Due to miss of any data this error can occur?

Any clue how to debug or solve this issue.

Regards

Chandra

stefan_grube
Active Contributor
0 Kudos

It is not possible to say anything before you find more detailed error information.

Check SXMB_MONI in SRM system for any hint.

Former Member
0 Kudos

HI Stefan

I tested inbound proxy interface with sample data. It self call is failed.

when i debug its collecting Application error when its triggering mapping methods.

Also when i try to test the transfer from Workbench, i get below error.

<SAP:Code area="ABAP">PARSE_APPLICATION_DATA</SAP:Code> 
  <SAP:P1>Request Message</SAP:P1> 
  <SAP:P2>CX_ST_MATCH_ELEMENT</SAP:P2> 
  <SAP:P3>/1SAI/TXSC3C9ECF070017DAD9ADA Line 7825</SAP:P3> 
  <SAP:P4>System expected the element '{http://sap.com/xi/SAPGlobal20/Global}PurchaseRequestERPSourcingRequest' XML Bytepos.: 45 XML Path:</SAP:P4> 
  <SAP:AdditionalText /> 
  <SAP:ApplicationFaultMessage namespace="" /> 
  <SAP:Stack>Error during XML => ABAP conversion: Request Message; CX_ST_MATCH_ELEMENT in /1SAI/TXSC3C9ECF070017DAD9ADA Line 7825 System expected the element '{http://sap.com/xi/SAPGlobal20/Global}PurchaseRequestERPSourcingRequest' XML Bytepos.: 45 XML Path: System expected the element '{http://sap.com/xi/SAPGlobal20/Global}PurchaseRequestERPSourcingRequest'</SAP:Stack> 
  <SAP:Retry>M</SAP:Retry> 
  </SAP:Error>

Do you think i need to regenerate proxy or check PI configuration.

Also i could not see regenerate button enabled in SRM SPROXY.

Pls advice.

regard

stefan_grube
Active Contributor
0 Kudos

> <SAP:P4>System expected the element 'PurchaseRequestERPSourcingRequest' XML Bytepos.: 45 XML Path:</SAP:P4>

This means tht your payload is not valid.

Check the interface and the expected data structure and compare it with the actual payload.

Former Member
0 Kudos

Hi Stefan

Thanks for your reply.

So you mean to say Payload format data has error and not proxy.

I checked the generated template data which is same structure as Proxy external view.

But it fails to execute, i debuged the proxy and found it fails at below place.

looks like xml parsing or mapping has problem.

----------------------------------------------------------------------------------------------------
|   21|  DATA: lv_timestamp TYPE string.                                                           |
|   22|                                                                                |
|   23|*  Main processing                                                                          |
|   24|                                                                                |
|   25|  SET UPDATE TASK LOCAL.                                                                    |
|   26|                                                                                |
|   27|* Create PurchaseRequest object                                                             |
|   28|  CALL METHOD /sapsrm/cl_soa_factory_pur_req=>/sapsrm/if_soa_factory_pur_req~get_instance   |
|   29|    IMPORTING                                                                               |
|   30|      eo_pur_req = lo_pur_req.                                                              |
|   31|                                                                                |
|   32|  GET REFERENCE OF input INTO lr_input.                                                     |
|   33|  GET REFERENCE OF ls_confirmation_message INTO lr_output_msg.                              |
|   34|                                                                                |
|   35|* Get SenderBusinessID                                                                      |
|   36|  lv_sender_bus_id = input-pur_req_erpsrc_req-message_header-sender_business_system_id.     |
|   37|                                                                                |
|   38|                                                                                |
|   39|* Get CTI from Request_In                                                                   |
|   40|  lv_cti = input-pur_req_erpsrc_req-purchase_request-item_list_complete_transmissio.        |
|   41|                                                                                |
|   42|  TRY .                                                                                |
|   43|      CALL METHOD lo_pur_req->execute                                                       |
|   44|        EXPORTING                                                                           |
|   45|          ir_input_msg     = lr_input                                                       |
|   46|          iv_sender_bus_id = lv_sender_bus_id                                               |
|   47|        CHANGING                                                                            |
|   48|          cr_output_msg    = lr_output_msg.                                                 |
|   49|                                                                                |
|   50|    CATCH cx_srm_exchange_fault_data.                                                       |
|>>>>>|      RAISE EXCEPTION TYPE cx_srm_exchange_fault_data.                                      |
|   52|  ENDTRY.                                                                                |
|   53|

Regards

Chandra

stefan_grube
Active Contributor
0 Kudos

If the proxy does not provide an error message which helps finding the issue and you do not find the error with debugging, then send a ticket to SAP.

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

How did you generated the objects in ID of PI..

By using Process integration model or created individual objects..?

if created using Process integration scenario model you should not get an error stating receiver cannot be determined or you must have generated the different scenario objects...(check this out..)

Regarding the connection as the message is not yet into SRM..

Consider only the connection/data transfer issues of ERP.. for connection test use SLDCHECK.(in ERP).. which should return green..

if not there is some error in the configuraitons..

Also if you have executed the data transfer then go to SXMB_MONI for knowing the status of the transfered/triggered data in ERP.. if it is success there then go to PI then check there the message..using same tcode as above..if everything isfine there then go SRM and check there for messages..

HTH

Rajesh

Former Member
0 Kudos

01 .check the Interface user (Z* is most of the case) which you have created has the authorization to post the document.

Log on type for this user could be System or communication data

02 check out for dump in ST22 any?