Restricting Users At Operation Levels In SOAP Scenario

Hi Experts,
I have a SOAP scenario where the target WSDL contains multiple operations like 1,2,3. We have two users, User 1 should have access to operation 1 and 2 only, user 2 should have permissions for all the three operations. How can we achive this functionality.
We are using PI7.1 EHP 1
Any suugestions ...
Regards,
Prasanna

What is the access that you are referring to?
One WSDL is going to have all the operations and hence restricting access to individual operations wont be possible in SAP XI/ PI.
If it is about which user should execute which operation then it should be restricted in the end-system.
There is one option available of Edit Authorizations available...check if it helps in defining access in your case.
Regards,
Abhishek.

Similar Messages

Restrict Users to specified Operating Unit

Hi all
can any one tell me how can restrict users to specified operating unit
Regards
Thanks

To do this, we create new responsibilities for the Operating unit, and we define the operating unit by setting profile option 'MO: Operating Unit' at responsibility level.
Then , we assign responsibility to users according to the operating unit they are allowed to access.
I don't know if there are other solutions ?

User status at operation level

Hi,
I have created one user status profile and attached in order type. In this profile I have included Operation and Order header as an "Allowed object type"
My problem is when I am changing user status at order level , it is not getting changed automatically at operation level.
Pls suggest me the solution.
Thanks

Hi,
I dont think it is possible .
A suggestion not sure if it works .
Assign user status profile operation wise and then have some development to check the operation status and
then update production order status with same user status you mentioned in operation.
FM: STATUS_CHANGE_EXTERN will help you to change the user status of order.
Regards,
Vishal

!!!How to restrict user for making changes in Sales order , partner level

Hi all,
Can anybody tell me how to restrict user for making changes in Sales order at partner level, is it through user exit?

Hi Ruchi
I hope u had gone to the screen fields which u want them not to be editable. So there u select all the fields contents which u do not want to to be changed and check the boxes with W.content and Display and save it. Once evrything is done u have to activate the particular transcation going in to the standard variants and put the name and click the activate button.
Hope its clear
Reward if help ful
Sri

Web Service Proxy error: "No operation found using soap keys"

I'm trying to use the new tools, and having a little trouble. Not many results when searching for this error message.
I have developed and deployed a new Java web service proxy using the outside-in approach according to the [help docs|http://help.sap.com/saphelp_nwpi71/helpdata/EN/46/7f2fef88190ad3e10000000a11466f/frameset.htm] (PI 7.1 SP07, NWDS 7.1 CE SP09 PAT0000). Started with a Service interface in ESR, then generated a java bean skeleton into a new EJB project in NWDS, then wrote business logic and deployed.
When I test the web service (with 3 different SOAP test clients) I get the same error, below:
     <faultstring>com.sap.engine.services.webservices.espbase.server.additions.exceptions.ProcessException:
No operation found using soap keys [], [spmat_jdbc_receiver_proxy]. InterfaceMapping Object class:
com.sap.engine.services.webservices.espbase.mappings.InterfaceMapping mappings: {BindingQName=
{urn:nexeninc:pi:ll:spmat:100}SI_I_Sync_SPMAT_JDBC_Receiver_ProxyBinding, BindingType=Soap, PortTypeQName=
{urn:nexeninc:pi:ll:spmat:100}SI_I_Sync_SPMAT_JDBC_Receiver_Proxy, JAXWSInterface=true, InterfaceMappingID=-
27e4d529:127632b5c52:-7ebb}.</faultstring>
My service endpoint interface looks like this (unimportant lines removed):
package nexeninc.pi.ll.spmat._100;
@javax.jws.WebService(name = "SI_I_Sync_SPMAT_JDBC_Receiver_Proxy", targetNamespace = "urn:nexeninc:pi:ll:spmat:100")
@javax.jws.soap.SOAPBinding(parameterStyle = javax.jws.soap.SOAPBinding.ParameterStyle.BARE, style = javax.jws.soap.SOAPBinding.Style.DOCUMENT, use = javax.jws.soap.SOAPBinding.Use.LITERAL)
public interface SIISyncSPMATJDBCReceiverProxy {
@javax.jws.WebMethod(operationName = "SI_I_Sync_SPMAT_JDBC_Receiver_Proxy", action = "http://sap.com/xi/WebService/soap1.1")
@javax.jws.WebResult(name = "spmat_jdbc_receiver_proxy_response", targetNamespace = "", partName = "spmat_jdbc_receiver_proxy_response")
public generated.SpmatJdbcReceiverProxyResponse siISyncSPMATJDBCReceiverProxy(@javax.jws.WebParam(name = "spmat_jdbc_receiver_proxy", targetNamespace = "", partName = "spmat_jdbc_receiver_proxy") generated.SpmatJdbcReceiverProxy spmat_jdbc_receiver_proxy);

(continued from above post)
And my implementation bean looks like this (unimportant lines removed):
package nexeninc.pi.ll.spmat._100;
@SessionHandlingDT(enableSession = false)
@AuthenticationDT(authenticationLevel = AuthenticationEnumsAuthenticationLevel.BASIC)
@TransportGuaranteeDT(level = TransportGuaranteeEnumsLevel.NONE)
@WebService(serviceName = "SI_I_Sync_SPMAT_JDBC_Receiver_Proxy_Service", portName
= "SI_I_Sync_SPMAT_JDBC_Receiver_Proxy_Port", endpointInterface
= "nexeninc.pi.ll.spmat._100.SIISyncSPMATJDBCReceiverProxy", targetNamespace = "urn:nexeninc:pi:ll:spmat:100", wsdlLocation
= "META-
INF/wsdl/nexeninc/pi/ll/spmat/_100/SI_I_Sync_SPMAT_JDBC_Receiver_Proxy/SI_I_Sync_SPMAT_JDBC_Receiver_Proxy.wsdl")
@Stateless
public class SIISyncSPMATJDBCReceiverProxyImplBean {
     @RelMessagingNW05DTOperation(enableWSRM = false)
     public generated.SpmatJdbcReceiverProxyResponse siISyncSPMATJDBCReceiverProxy(
               generated.SpmatJdbcReceiverProxy spmat_jdbc_receiver_proxy) {
          System.out.println("Starting siISyncSPMATJDBCReceiverProxy.");
When we first created the new endpoint in NWA, we tried asigning a new name for both "Service Endpoint Name" and "In New Service", and we received this error.
We then deleted the endpoint and created another new one, setting "Service Endpoint Name" to match the portName in the implementation bean: "SI_I_Sync_SPMAT_JDBC_Receiver_Proxy_Port", but that didn't work either. The only option we enabled in the endpoint was HTTP authentication: User ID/Password.
My ejb-j2ee-engine.xml and application-j2ee-engine.xml are both empty (but they exist).
I am new to EJBs and JAX-WS so hopefully it's something simple. All help appreciated!
Apologies for the long (and wide) post.
- Rob

Error handling in File - XI - SOAP scenario without BPM

Hello!
We have a File -> XI -> SOAP scenario without BPM. The problem is that if the Web Service sends back an error XI tries to reprocess the same message again and again instead of taking the next one.
We do not want set the retry interval to NULL because most error cases are temporary connection problems and then also those messages would not automatically be reprocessed any more.
We also have to use BE instead of EO, otherwise the Web Service will not return a response. But we need the response to be sure that the processing was successful. The message volume in this scenario is quite high and we do not want to use BPM only for the error handling.
I know that from SP19 some additional adapter modules are available for async - sync scenarios without BPM. I tried to configure it like described in File - RFC - File without a BPM - Possible from SP 19. but it did not solve the problem. Does anybody have any other ideas? Thanks.
Regards, Tanja

Hi Tanja,
>>>The volume is 3000 messages/day on business days and 700 messages/day during weekends but the traffic will increase in the future
I think, you should check that out. It is assumedly only 2 days work to build a scenario:
IDoc -> BP
BP <-> SOAP/HTTP
BP -> IDoc (Acknowledgement)
In the process you need a condition branch, where you decide success or not. You need 2 Interface Mappings for filling the ALEAUD.
Just send 1000 IDocs to the Test-XI and look to performance monitoring at Runtime Workbench, to find out, how many message will be processed in one hour. Assumedly 3000 and more per day should be possible. The advantage would be to reduce number of systems (no file system) and messages (better monitoring) and using the standard (better maintenance).
>>>So you are suggesting I should use HTTP adapter and then add the SOAP header manually in a mapping?
Yes, build the SOAP envelop during the mapping. Most easy is to use XSL or, if your mapping is ready, an additionsal XSL. You can put the error into the Acknowledgement to see it in ERP transaction WE02.
Filling of ALEAUD fields:
E1ADHDR/MESTYP: original message type
E1ADHDR/E1STATE/DOCNUM: original IDoc number
E1ADHDR/E1STATE/STATUS: 68 in case of error, 53 in case of success
E1ADHDR/E1STATE/STATXT: Short description for R/3 user what has happend
I ve done such a scenario several times. That works without any problems.
Regards,
Udo

File name to be read in mapping - File to SOAP Scenario

Hi all,
its a file to soap scenario. i need to send the file name also to target system. how can i get the file name in the mapping? is there a way to read the header information in mapping?
Regards,
Rashmi

You need to check for Adapeter specific Message Attributes of your File adapter.Then write user defined function to set Dynamic_configuration. So that you can get the file name in the header(u can chk this in SXMB_MONI after implementing the UDF, it will create one section for dynamic_configuration.)
Manisha

IDoc to SOAP scenario is showing error

Dear Experts,
We were trying a scenario which is IDoc-XI 3.0->SOAP and where the WebService is situated outside our office network. Our network team have bypassed proxy for accessing that WebService URL and the same is accessible from our XI3.0 application server from browser. We have configured the scenario and when we have tested the scenario from RWB->Component M onitoring->Integration Engine->Test and this has worked fine. But when we have tested the scenario by triggering IDoc from the R/3 system, it is throwing the below mentioned error in both at the comm chanel and at the SXMB_MONI acknowledgement.
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 403 Service Error
points to be noted here:
1. Business Service has been configured correctly for triggering ALEAUD messages and ALEAUD messages are reaching R/3 successfully.
2. We have chosen option Keep Headers and Do not use SOAP header options.
3. We are passing some values to the SOAP Header from SOAP channel.
Please could somebody help us on the root cause of the error message.
We have run report IDX_NOALE for that particular IDoc so that it doesn't return any acknowledgement back to the R/3 system.
Thanks and regards,
Sugata
Edited by: Sugata Basu on Nov 19, 2011 12:40 PM

Dear,
IDoc to Soap scenario we have to import wsdl at receiver end and map the field from the mapping document but some times receiver end some changes may happen. if it is correct only your mapping we have to conclude from the below points.
1. Check the mapping in Message Mapping and Operation Mapping Test and conclude.
2. you should check url from receiver that is correct or wrong.
3. ask the wsdl from receiver end.
the given ED and receiver side application is same this type of error will not come.
Please check at receiver application or else what ever new fields are added in reciver may be miss mach of ED.
Regards,
Kiran Polani

Restrict Authorization at Material level during production confirmation

Hi SAP Gurus,
I would like to ask if its possible to restrict authorization at Material Level during production confirmation.
Our scenario is we have SFG and FG which are handled by different group of people but it has the same Order Type. Now we want to restrict authorization such as one department can only confirm SFG and the other department can confirm FG only.
Is it possible to set authorization at material type or production scheduler level. IF not possible, is there other way except creation of new Order Type?
Thanks,
Raymond

Hi Raymond,
DO you mean I should create a customized table for this?
Yes
Are there no standard way?
As per my knowledge, you can control through production order type, so you need to create seprate order type for this
Thanks,
Sankaran

Idoc to soap scenario - soap response error

hi
i am using pi 731 single stack.
the scenario is idoc to soap. the message mapping is working fine and output is generated successfully.
the message is failing in mesage monitor and communication channel monitor. error is -
Exception caught by adapter framework: SOAP: Response message contains an errorXIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: VEN-OMI-1007:
This scenario is async scenario. How to soap remove this response message error.
rgds

Dear,
IDoc to Soap scenario we have to import wsdl at receiver end and map the field from the mapping document but some times receiver end some changes may happen. if it is correct only your mapping we have to conclude from the below points.
1. Check the mapping in Message Mapping and Operation Mapping Test and conclude.
2. you should check url from receiver that is correct or wrong.
3. ask the wsdl from receiver end.
the given ED and receiver side application is same this type of error will not come.
Please check at receiver application or else what ever new fields are added in reciver may be miss mach of ED.
Regards,
Kiran Polani

File to SOAP scenario question???

Hi,experts
let's take source system is A,target system is B.
I have a File to soap scenario using BPM,the scenario is send file request(from A) to PI,PI will be communicating target system(B) with soap(syn).After that, PI receives the soap response and send the response data to A.
Now the requirement is, we need to archive the file request msg(before sending to B) to a folder and archive the response msg(response from B) to a folder as well.how could it be achived?
any help will be much appreciated!
Thanks

Hello Rajesh_V2009 ,
I am trying to implement exactly the same pi scenario, but having some problems :
File -> file adapter -> ccBPM -> soap receiver adapter -> web service request -> web service response -> ccBPM -> output file adapter.
The web service that I call works file from wsnavigator. I have created all the design and configuration objects
needed for the scenario.
I place a file with following contents:
<?xml version="1.0" encoding="utf-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body>
<pns:GetSetNameWS xmlns:pns="urn:file2soap2fileWSVi">
<pns:name1>ajeet</pns:name1>
<pns:name2>phadnis</pns:name2>
</pns:GetSetNameWS>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
When I look at the process monitor I get this:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">CX_RD_PLSRV</SAP:Code>
<SAP:P1>Problem while determining receivers using interface mapping: No operation with XML root tag http://schemas.xmlsoap.org/soap/envelope/.Envelope exists.</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error when determining the receiver: Problem while determining receivers using interface mapping: No operation with XML root tag http://schemas.xmlsoap.org/soap/envelope/.Envelope exists. Problem while determining receivers using interface mapping: No operation with XML root tag http://schemas.xmlsoap.org/soap/envelope/.Envelope exists. No operation with XML root tag http://schemas.xmlsoap.org/soap/envelope/.Envelope exists.</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have no clue about this error. Can you help me with this ?
If yes I can send you more details, if you liked 
Hoping to get help from you,
Cheers,
Ajeet Phadnis

SOAP to SOAP scenario

Hi Experts,
Could you please tell me, how to do SOAP to SOAP scenario?
Mainly need info for Receiver SOAP Adapter...
Any document for the same?
Regards
Sara

Hi,
Receiver SOAP Adapter
The receiver SOAP adapter connects XI with an external Web service. To call the Web
service, you need to define a message interface that represents the structure of the
request and response of the Web service. You can create this message interface easily
with the help of a WSDL file that represents the Web service. If this is not possible, you must create the message interface based on data types.
- Uploading the WSDL
Since the WSDL describes the message interface, you upload the WSDL into the
Integration Repository. Go to your Software Component Version and open the required
Namespace. Create an External Definition.
In the external definition object, choose Category wsdl and click Import external
definitions.After importing the WSDL file, you can view the included messages on the Messages tab page:
The namespaces of the messages are part of the WSDL description and can
differ from the namespace of the external definition object.
Now you can create a message interface corresponding to the message types from the external definition. You need the message interface for routing the message to the Web service.
In the message interface object, select the message types of the external definition
object by using the input help.
After assigning the output and input message, save and activate your work. Now you can use the message interface for routing and mapping.
Creating a Message Interface Without WSDL
For some scenarios it is not possible to provide a WSDL file. In this case you need to create a message interface according to the message structure of the server. The best way to achieve this is by using an example SOAP message for the request and the response message.
Since the SOAP adapter creates the SOAP envelope you have to extract the SOAP
body. Usually, Web services ignore declarative attributes (xsi:type), therefore you can delete them. The namespace declaration of the root tag must be applied. The XI
message payload should be the following message.
Create a data type, message type, and message interface according to this structure. In the message type, apply the correct name and namespace of the message.
Creating a SOAP Receiver Channel
To call the Web service, you create a communication channel with type SOAP and
direction receiver in the Integration Directory. The obligatory parameters in the
configuration are Target URL and SOAP action. You get the values you have to enter
here from the WSDL file.
You find the target URL at the tag soap:address and the SOAP action at the tag
soap:operation.
If more than one message type is described in the WSDL, several SOAP actions
might also be defined. Check for the correct operation name. If no SOAP action is
defined in the WSDL, you can leave the parameter in the receiver channel empty.
For the receiver SOAP adapter you need at least the following parameters.
If the Web service is outside your system landscape and you need to address a proxy server, select the Configure Proxy checkbox and fill in the corresponding fields.
Hope this will help you.
Regards
Aashish Sinha
PS : reward points if helpful

In process inspection - Rejection Booking at operations level

Hi All,
Need some help regarding inporcess inspection.
As we aware about '03' insp type is not stock relevant
The requirement is , i having operations are like 0010 ,0020 ,0030 ,0040,0050 in Production order in Routing
Now while operation wise confirmation i want to book the rejection and that needs to get effect on further operation confirmation.
For example : Suppose I have confirmed 50 TON against operation 0020 , hence at the time of confirmation 0020 i want to book the rejection 2 TON
Hence while confirming 0030 system should not allow to cofirm 50 TON , system should allow to confirm only 48 TON through CO11N and Some where that rejection has to be display in report.
Is there any provision in standard to enter rejection at operations level.
Stock posting not required , Only qty tracking required like operation wise confirmation.
Please advise to make this scenario success.
Thanks,
Abhishek

Hi Abhishake,
As in inspection type 03 lot you dont have stock posting option, you can scrap the rejected material operation wise in CO11N at the time of confirmation (Mov Type 551).
As scraped material will no more in system, you can also look forward for bi-product assignment in bom if you don't want to go with first option.
Also you can check for early lot creation if can solve the purpose, as in this case you will get inspection lot of inspection type 04 at the time of release of production order and stock will be adde to quality inspection as you do confirmations operation wise.
Regards/Rohit

Problem with SOAP Scenario

Hi,
I am trying a http to soap scenario.
In the receiver soap adapter, I have specified the following:
Target url: http://test.abc.com/
Action: handleLogin()
When I send the request, I get a "time out error" as the response in the http client tool.
However, in sxi_monitor, I get a webpage as the response(A web page is being displayed in the monitor).
What I was expecting is a response message that matches the wsdl.
I have tried using "" and a blank value for the Action field in the soap adapter, but no luck.
Any help would be appreciated.
Thanks,
Smitha.

Hi Shabarish,
Thanks for your response.
I provided the operation name in the soap adapter as specified in the blog, but I am getting a http_adapter exception. (500 internal server error)
Any clues?
Thanks,
Smitha.

HTTP 401 Unauthorized, error in proxy to SOAP Scenario

Hi all,
We got the below error in our proxy to SOAP Scenario.
com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized
We configured User Authentication,Proxy and Proxy User Authentication for the Receiver Communication Channel correctly still we are getting this error.
So please let me know what could be the possible reasons behind it and how to resolve it.
Waiting for your valuable response.

Hi,
Consider the parameters connection pool size and connection wait time:
ume.r3.connection.master.poolmaxsize
ume.r3.connection.master.poolmaxwait
These parameters are described in the note below:
#821026 - AdapterEngine messaging URL returns HTTP 401 under high load
Also, ensure you have maintained the correct password, which MUST be the same, for all the service users
on XI. You may check all the places it should be maintained, such as Exchange Profile, SU01, SLDAPICUST, etc..
Please kindly check the note below:
PI 7.1:
#999962 - PI 7.10: Change passwords of PI service users
XI 7.0
#936093 - XI 7.0: Changing the passwords of XI service users
XI 3.0
#721548 - XI 3.0: Changing the passwords of the XI service users
And ensure that the user has the correct role as per link below:
http://help.sap.com/saphelp_nwpi71/helpdata/en/9f/d12940cbf2195de10000000a1550b0/frameset.htm
Regards,
Caio Cagnani

Restricting Users At Operation Levels In SOAP Scenario

Similar Messages

Maybe you are looking for