Saturday, December 3
RfcException: message: 'user' missing Return code: RFC_INVALID_PARAMETER
The above shown error will appear when the type of JCO destinations is SSO.
With SSO JCOs, the requests raised from the dynpro application will be executed in the backend with the same user ID as used during logging in to the frontend dynpro allication.
Now in order for this request to be completed succcessfully, the user ID should be available in the backend system. If the user ID is not created in the backend SAP system, above error will appear.
The other type of JCO is called the UserID/Pwd JCO where a specific user ID is defined at the JCO level by the portal adminstrator. Now any request coming from the frontend dynpro allication is executed using that specific ID in the backend SAP system. So here in this case, it is sufficient to define this ID in the backend system.
So there are 2 solutions to the above error :
1) create the User(using which the user has logged in to dynpro application) in the Backend SAO system
This is in the case of SSO type of JCO. This type of JCOs should be used in the cases when we know that the application will be used only a particular set of users whose IDs will always be available in the Backend SAP system.
2) Change the type of JCO to UserID/PWD JCO.
This is useful when we dont know the strength of users who will be using this application. For Example, the dynpro application created for customer to raise a saled agreement request. Here in this case, anonymous customers(whose IDs are not created in the SAP R/3 system) will interact with the SAP R/3 system through dynpro application.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment
You are welcome to express your views here...