Scribd
Upload
20 views9 pages

Role Creation Guide Vim

Role Creation guide VIM SAP

Uploaded by

Er Ravi Arya
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
20 views9 pages

Role Creation Guide Vim

Role Creation guide VIM SAP

Uploaded by

Er Ravi Arya
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
You are on page 1/ 9
415724, 1:55 PM OpenText VIM: Roles creation - SAP Community SAP Community > Products and Technology > Enterprise Resource Planning > ERP Blogs by Members > OpenText VIM: Roles creation Enterprise Resource Planning Blogs by Members Gain new perspectives and knowledge about enterprise resource planning in blog posts from community members. Share your own comments and ERP insights today! All community ¥ What are you looking for today? Opentext VIM: Roles creation PankajPareek Active Participant 9° 04-19-2016 4:24 PM 15 Kudos Roles in VIM is different from SAP workflow roles. Role in VIM is used to classify the users based on the business activity they are involved in. In VIM roles are based on the product code. VIM offers following product codes: 1, 005: Product code for Document Processing (DP) based activities 0085: 2, LIX: Product code for Logistic Invoice Verification (LIV) process (PO parking or PO blocking) PIR: Product code for Non Purchase-Order parking workflow Below are the scenarios for the better understanding of the relationship between roles and product codes. ntps: community sap.comSlenterpse-resource-planning-blogs-by-memberslopentext-vin-toles- Bi Pempite Fata | imloes ‘AE_PROCESSOR _COMPAITYCODE o 005 ‘AB PROCESSGR _DPDOCTYEE o | 008 ‘AP_PROCESSOR ‘ORGUNIT y Maintain Role Determination Settings: We have now mapped roles and template but we still need to define the values that will be used in runtime for role determination. This is carried out by using transaction In [OPTICP_9CX4, For each role under a product code, we need to maintain the values of the fields or (Org unit or FM (depending upon if they are Static, Semi-Dynamic or Dynamic type) which are defined in the template. Display Role / User Management - Template based °y Dispay / Change Product Roks with Actve Tempiates a aes OPENTEXT | Vencor invoice Management” terse Sours |AE_ PROCESSOR + Goemen Buyer + Beow_ceck —Duplicat® | Function Module 7 + BEDUE CHECK = ~Duplicate + Gower indexer — + [Elio sRovineR —tnfoamac; | FUNC Module ‘OPT NOW APEROVER + (EDREQUISITIONER -Requistic + Barescan Maintain Chart of Authority (CoA): | have given a brief explanation on CoA in my previous document (please refer: http://sen.sap.com/docs/DOC-57917). In version 7 invoice approver can be determined based on two logics: 1. Simple approval: It is same as the old version Le. gross amount and managers information, 2. Level based approval: Approvers are determined based on levels and packs. Levels are defined for approval limits ie. each level will have different amount range that can be approved by that level. For example: We can have different set of approvers for amount ranges: $0 - $5000, $5000 - $10,000, $10,000 - $20,000 and so forth. Also, they can be further divided based on cost center. For example: for the amount range level of $10,000 to $20,000 we can have different approvers for different cost centers. ntps:/oommuniy sap.comSlenterpse-resource-planning-blogs-by-memberslopentext-vin-toles

You might also like