On the ESS timesheet, we have been facing a recurring Error message saying: "System error: No receiver could be determined".
I've been looking over the whole web, found some hints about how to make this message disappear, and it seems that the key transaction is SOAMANAGER.
Unfortunately, after loads of test configuring Service definitions and Consumer proxies i can't make it go away.
I'm not sure i'm using the right Service definition and Consumer Proxies, I've did my tests on the followings:
Service --> EETMECAL_WTS_EE_QR
Consumer --> CO_CATS_EMPLOYEE_TIME_CALENDAR
Does anyone already did this configuration and could lead me to a solution?
Just a quick recall, this message appeared after checking the foloowing checkbox in CAC1:
Thanks in advance for any kind of help you could provide me.
Thanks for your quick answer.
We are not using XI as Middleware, and the role of our Business system is time management.
We did try to bind the following services in SOAMANAGER:
I guess we did something wrong...
Did you also get the same error message before your configuration?
We got this message because our binding service was inactive but there could be some other reasons for your issue.
Ok another questions your HR & CATS are going to share same server?
Few tasks for troubleshooting.
1. Check service binding
2. Check SXMB_ADMIN for role of business system ( Should be local )
3. Check SICF if service is active.
Let me know if all above are there then we 'll check some parts of it.
When role of business system is 'APPLICATION SYSTEM' . We received an system error message : SYSTEM ERROR : NO RECEIVER COULD BE DETERMINED.
By changing the role of business system to 'NOT YET CONFIGURED' (as you suggested), We received the system error : SYSTEM NOT CONFIGURED AS XI INTEGRATION ENGINE.
The URL path for CO_CATSEMPLOYEE_TIME_AGREEMENT is configured as : sap/bc/srt/wsdl?wsdl&mode=sap_wsdl&style=document
By having style=document at end of URL path. We did not observe any change in the behavior.
It is good that you got this message. We have got this one too.
"By changing the role of business system to 'NOT YET CONFIGURED' (as you suggested), We received the system error : SYSTEM NOT CONFIGURED AS XI INTEGRATION ENGINE."
I think your URL access path under port for Consumer Proxy (CO_CATSEMPLOYEE_TIME_AGREEMENT) is incorrect.
Let me know what settings you have under port "Transport Settings" & other details.
Thanks again for your answer. Yes, i think my problem is the URL. But i don't how to obtain the right one. Do you have any idea ?. I've tried few combinaisons without succeed.
Here is an exemple, how i got the URL:
By doing a test connection on the service /sap/bc/srt/wsil. I got the following WSDL URL
In my 'Transport Settings' tab of the proxy CO_CATSEMPLOYEE_TIME_AGREEMENT. I've used the same url
Computer name of Access URL : http://<hostname>
Port Number of Access URL: 80
URL Protocol Information : HTTP
Logon Language : Language of User Context
Make Local Call : Local System Call
Transport Binding Type : SOAP 1.1
Maximun Wait for WS Consumer : 0
Optimimized XML Transfer : None
Comprress HTTP Message : Inactive
Comprerss Response : True
Please let me know if this is the proper way to obtain the URL.
You are using local system with out PI so no need to use WSDL URL in consumer proxy. The Concept behind is your consumer proxy will call service back in local system hence just use your SICF URL for service "eetmeagr_pwtp_ee_qr" with client info. Do not put anything under Company Name because it is local.
I've replaced WSDL URL of CO_CATSEMPLOYEE_TIME_AGREEMENT by the SICF URL of the service 'eetmeagr_pwtp_ee_qr'. http://<hostname>:8036/sap/bc/srt/xip/sap3eetneagr_pwtp_ee_qr/335/eetmeagr_pwtp_ee_pr?sap-client=335
The new URL configured in the cosumer proxy is
Do i have to specify the host name and port number in this url ?
The field Computer Name is equal to blank now.
Role of Business System should be set to 'NOT YET COINFIGURED' or 'APPLICATION SYSTEM'.
Added service binding in URL http://:8036/sap/bc/srt/xip/sap3eetneagr_pwtp_ee_qr/335/eetmeagr_pwtp_ee_pr?sap-client=335/service/binding.. Role of Business system just keey NOT YET CONFIGURED.
I still have the same error message ' System error : system not configured as XI intergration engine'
The URL Access Path is now
The role of business has been set to Not yet configured.
Any configuration is missing ?
Ok try this.. 1. Under service use "None" (http) 2. Remove entry from "Corresponding Integ. Server" 3. I think link is correct http://hsape06ci.hydro.qc.ca:8036/sap/bc/srt/xip/sap/eetmeagr_pwtp_ee_qr/335/eetmeagr_pwtp_ee_qr/eetmeagr_pwtp_ee_qr_binding Did you ping it?
I've removed the entry from Corresponding Integration Server. I was abled to ping the URL and as you noticed we added the binding at the end of the URL.
We continued to receive the same errors when invoking the record working time WDA application. Here are they based on value used in Role of Business
System NOt yet configured : System error: System not configured as XI Integration Engine
Application system : System error: URL to call the Integration Server is missing on t
Integration Server :System error: Proxy calls are not permitted on sender or receiver
Please note that we successfully tested both Provider and Consumer services in SE80 after specifying generic sap userid passwd for authentification
Thx, Nhan Nguyen
Nhan, Definitely option 1 is correct for local call. System Not yet configured : System error: System not configured as XI Integration Engine Now I think, we need to check SLD settings. Can u run "SLDCHECK" in ur ECC system. Specify the SLD ID, the Business System ID of the connected system and the connection data. Thanks, Arpit
Do you still have an issue with this? If not never mind.
I happened to read this to configure our own scenario. I am able to get this resolved. We are not using PI so it was easier. But if you are then I see couple of issues.
In the above image, set the role to Application System. Create a HTTP type RFC connection and name it as INTEGRATION_SERVER. In the RFC the path prefix should be "/sap/xi/engine?type=entry".
To answer your error messages below
System NOt yet configured : System error: System not configured as XI Integration Engine - NA
Application system : System error: URL to call the Integration Server is missing on t - see below
Integration Server :System error: Proxy calls are not permitted on sender or receiver - NA
In the Configuration URL enter http://hsape06db:8006. System error "URL to call" error will be gone.
There might be more issues depending on whether you have all the PI configuration in place.
Thank you for the information. Yes, i still have the same issue.
We are not using PI neither for this solution, But we already have a connection names INTEGRATION_SERVER with the path /sap/xi/engine?type=entry.
Concerning the URL configuration, can you tell me where exactly i should do this configuration ?
Is in In Consumer proxy or in Consumer service ?
If you are not using PI then we dont have to worry about Int serv settings etc. You may have already done most of it.
This is a Basis activity.
You have to configure the following web services using SOAMANAGER tcode on the ERP system. After launching this, click Webservices configuration. In the search pattern for Service Definition, enter "EET*" and click go. You will see the following two Services.
Make sure that in the transport settings tab, you select "Local System Call". This is the key as we are not using PI. This setting should be done in all web services and the proxies.
After creating the services, we have to create the Proxies. For this change the "Search by" to "Consumer Proxy" and search for "CO_CATS*Employ*" You will see the following two
1.CO_CATSEMPLOYEE_TIME_AGREEMENT (corresponds to first WebService)
2.CO_CATS_EMPLOYEE_TIME_CALENDAR (corresponds to second WebService)
Create the proxies.
For all these to work, you have to set Web Services Navigator (name of the tab too) enter the SLD server name and after this enter this ERP server name in the SLDs white list. (open SLDServerHost/nwa -> SOA Management tab -> SOA Middleware Global Settings -> WS Navigaror)