on ‎2012 Nov 06 1:52 PM
Hi
I'm implementing SRM 7.02 with NWBC for HTML.
I've made the followings configurations to use the portal:
-Activate the Portal-independent navigation frame in Customizing for SAP Supplier
Relationship Management
-Define an RFC connection of type H (HTTP) to the SAP ERP back-end system
-Enter the HTTP connection defined above, but without the suffix, in the Customizing activity
Define System Landscape in the System Alias for POWL Navigation field
-Activate the Internet Communication Framework (ICF) service /sap/bc/nwbc/srm in
transaction HTTP Service Hierarchy Maintenance (SICF). Use this service to start NetWeaver Business
Client (NWBC) for HTML.
Roles are also defined for users (with PFCG)
I can access the menu, but when i try to open any transaction that calls master data (supplier master data, material master data) i get an error.
This is clearly the case with data transactions, not so with the document transaction (SC, PO, IN).
This is the description of the error (from ST22)
"An exception occurred which is explained in detail below.
The exception, which is assigned to class 'CX_NWBC', was not caught and therebefore caused a runtime error.
The reason for the exception is:
For the role entry " " (Vendors ), the SM59 alias can't be resolved. Needed is at a minimum one type "3" definition ("SAP_ECC_PROCUREMENT" or "SAP_ECC_PROCUREMENT_RFC") and minimum one type "H" definition ("SAP_ECC_PROCUREMENT" or "SAP_ECC_PROCUREMENT_HTTP" or "SAP_ECC_PROCUREMENT_HTTPS")"
This happens with any role.
The RFC destination is configured for backend.
Any ideas? Please help me! Thanks!
Request clarification before answering.
Hi. Did you ever fix this? We are getting the exact same error now.
My gut feeling is that it needs more services activating in SICF but do you know which?
Regards,
Dave.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
which role throws this error? is this a standard role?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
See if the link below helps
http://help.sap.com/saphelp_srm70/helpdata/en/48/ff4f2d222b3697e10000000a42189b/content.htm
Regards,
Naveen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Naveen:
I checked attributes for Organizational unit (root) at PPOMA_BBP:
-System alias (SYS)
-System alias for accounting systems (ACS)
-System alias for vendor (VENDOR_SYS)
-Accounting system for vendor (VENDOR_ACS)
Also checked attributes for Vendor root (PPOMV_BBP):
-System alias for vendor (VENDOR_SYS)
-Accounting system for vendor (VENDOR_ACS)
They are all set with backend logical system (e.g. ERPCLN100)
Is that right?
Is there another attribute that could be related to this error?
Clara
Hello Clara,
a RFC of type 3 (connection ABAP) to Backend is necessary.
Cristian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.