cancel
Showing results for 
Search instead for 
Did you mean: 

USER_CATALOGS table not filled

0 Kudos
614

Hello SAP Experts,

I have followed the following steps and also referred to the SSP cookbook
1) Create employee using TCode PA30 and with communication (0105 infotype) user as user system ID.

2) Based on employee creation system should create through background program employee (person) BP with BP roles as employee, General, Fi Vendor.

3) With Tcode PPOMA - proper organization structure to be created. i.e. Company > Position as catalog manager

4) Assign BP to catalog manager.

5) define attributes at company level in Tcode PPOMA. These attributes should be inherited for position created under it.

6) Now most important part is > one of the attribute entered for company and inherited to position should auto flow in table "USER_CATALOGS" with an information a. Employee id b. web service id (web service has catalog URL)


BUT STILL , the table USER_CATALOGS is not being filled. It comes up empty.Could anyone help , thank you.

Julie

Accepted Solutions (1)

Accepted Solutions (1)

laurent_burtaire
Active Contributor
0 Kudos

Hello Julie,

if you did not find any OSS notes dealing with your issue, i advise you to open an OSS message.

Regards.

Laurent.

Answers (2)

Answers (2)

turkaj
Active Participant
0 Kudos

The table/CDS view can be filled as follows:

  1. Enterprise Resource Planning Blogs by SAP (This blog describes the approach very well)
    https://community.sap.com/t5/enterprise-resource-planning-blogs-by-sap/how-to-create-business-users-...
  2. Once created, you can now find the user in the ‘Default Settings for Users - Purchase Requisitions’ app
    In the lower ‘Assigned Catalogs’ area, you can now fill in the USER_CATALOGS table/CDS view.
brahms86
Active Contributor
0 Kudos

Refers to 1909:

1) 1st misunderstanding: Values maintained for users/business partners/positions/org units in PPOMA do not flow to table USER_CATALOGS.

2) But if there is an entry in table USER_CATALOGS for a user, then this user also has access to the catalog.

3) You maintain table USER_CATALOGS directly using the "Default settings for user - Procurement" app for Admins(!) and not the default settings of the user. Both look identical, except in the app the catalog entries become editable (for admins).

I got with to work with PPOMA as well as with the app.