{"id":2395,"date":"2025-11-18T20:36:20","date_gmt":"2025-11-18T19:36:20","guid":{"rendered":"https:\/\/johannesauer.com\/en\/?p=2395"},"modified":"2025-12-17T07:20:39","modified_gmt":"2025-12-17T06:20:39","slug":"creating-a-role-determination-for-sap-vim-solutions-beyond-invoice-free-template","status":"publish","type":"post","link":"https:\/\/johannesauer.com\/en\/sap-vim-beyond-invoices\/creating-a-role-determination-for-sap-vim-solutions-beyond-invoice-free-template\/","title":{"rendered":"Practical Role Determination for SAP VIM Solutions Beyond Invoice: A Simple Approach + Free Template"},"content":{"rendered":"\n

When you start working with SAP VIM Solutions Beyond Invoice \u2014 whether it\u2019s Incoming Delivery Notes<\/strong>, Sales Orders<\/strong>, Remittance Advices<\/strong>, Order Confirmations<\/strong> or Quotations<\/strong> \u2014 you quickly notice a familiar limitation: the out-of-the-box setup doesn\u2019t provide meaningful role definitions<\/strong>. The delivered BC-Sets rely entirely on SAP\u2019s Organizational Object Assignment<\/strong>, pointing to predefined work centers, rules, jobs, org units, positions, or individual users.<\/p>\n\n\n\n

In real projects, these structures are rarely maintained in a way that supports smooth routing. That\u2019s why, in most implementations, one of the very first tasks is building a practical, maintainable role resolution logic \u2014 one that matches how the organization actually works<\/strong>.<\/p>\n\n\n\n

\"\"
\/otx\/pf00_img > Process Configuration > Profiles<\/figcaption><\/figure>\n\n\n\n

A very minimal role resolution logic which works without creating a table, maintenance view and more is this one: We tap into the existing table of validation agents maintained in Validation Assignment. This is a very simple and very easy solution as you can set up a list of users per ArchiveLink Document Type and this user will then be assigned both for validation and document processing.<\/p>\n\n\n\n

\"\"
\/OTX\/PF00_IMG > Inbound Configuration > Capture > Validation Assignment<\/figcaption><\/figure>\n\n\n\n

The link between ArchiveLink Document Type and User is stored in table \/OTX\/PF01_T_VALR.<\/p>\n\n\n\n

\"\"
SE16N displaying \/OTX\/PF01_T_VALR<\/figcaption><\/figure>\n\n\n\n

The only way to achieve any logic for determining users besides SAP\u2019s Organizational Object Assignment<\/strong> is using the setting Role Resolution Logic which requires an ABAP Class being assigned. <\/p>\n\n\n\n

Create a new class in SE80 using Superclass \/OTX\/PF04_CL_ROLE<\/strong> <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Redefine method \/OTX\/PF04_IF_ROLE~ROLE_LOGIC<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

A minimal version of this method could look like this (simply returning one user with username Alex):<\/p>\n\n\n\n

<\/circle><\/circle><\/circle><\/g><\/svg><\/span>