2017619 OpenTextVIM:Rolescreation|SAPBlogs

Products
Products Industries
Industries Support
Support Training
Training Community
Community Developer
Developer Partner
Partner

About
About

Home / Community / Blogs + Actions

OpenTextVIM:Rolescreation
April19,2016 | 1,440Views |
PankajPareek
morebythisauthor

FIN(Finance)
opentextvendorinvoicemanagement | vimroles

share
0 share
0 tweet share
0

Follow

RolesinVIMisdifferentfromSAPworkflowroles.RoleinVIMisusedto
classifytheusersbasedonthebusinessactivitytheyareinvolvedin.In
VIMrolesarebasedontheproductcode.VIMoffersfollowingproduct
codes:

1.005:ProductcodeforDocumentProcessing(DP)based
activities

https://blogs.sap.com/2016/04/19/opentextvimrolescreation/ 1/7
2017619 OpenTextVIM:Rolescreation|SAPBlogs

2.LIX:ProductcodeforLogisticInvoiceVerification(LIV)
process(POparkingorPOblocking)
3.PIR:ProductcodeforNonPurchaseOrderparkingworkflow

Belowarethescenariosforthebetterunderstandingoftherelationship
betweenrolesandproductcodes.

Scenario1:Thedocumentshouldgetblockedifthereispricediscrepancy
forPObasedDPdocument.ThedocumentshouldgotoAccountPayables
Processor(RolewillbeAP_PROC)toreviewandapprovetheprice
discrepancy.Whichproductcodewillbeusedinthisscenario?

Solution:RoleAP_PROCwillbecreatedagainstproductcodeLIXasLIXis
forPOblocking.

Scenario2:IfthereareanyissueswithDPdocumentwhereitviolatesany
businessrule(saycurrencymismatch)thenthedocumentshouldgoto
AccountPayablesProcessor(RolewillbeAP_PROC)forfurther
processing.Whichproductcodewillbeusedinthisscenario?

Solution:RoleAP_PROCwillbecreatedagainstproductcode005as005
isforDPprocessing.

Followingstepsareinvolvedinrolecreation:

DefineRoles:RolescanbedefinedbyusingTCode/n/OPT/CP_9CX5and
byprovidingfollowinginputs:

1.ProductCode:005orLIXorPIR
2.Role:Itistheresponsiblepartyorrolethatwewanttocreate.
3.Description:Itisthedescriptionoftherole.
4.FunctionModule:IfanyFMisapplicable
5.KeyDetermination:Uncheckitiftherolewillbebasedon
organizationdatasuchasCompanyCode,Plantetc.
6.ObjectType

FM,KeyDetermination,andObjectTypeareusedbasedonthetemplate.
PleasereferRoleTemplateformoredetailsonthem.

https://blogs.sap.com/2016/04/19/opentextvimrolescreation/ 2/7
2017619 OpenTextVIM:Rolescreation|SAPBlogs

DefineRoleTemplates:Templatehelpstodeterminetheroleapplicablein
aworkflow.RolescanbeStatic,SemiDynamicorDynamic.Iftheroleis
determinedonlyonthebasisofcertainparameterslikeCompanyCodeor
PlantthenthetemplateisStatic.Ifitisdeterminedbasedonacertain
structurelikeOrganizationHierarchythenitisSemiDynamicandifitis
determinedbasedonfunctionmodulethenitisDynamic.Roletemplatecan
bemaintainedbyusingTCode/n/OPT/CP_9CX2.

Followingparametersareprovided:

1.TemplateID:IDofthetemplatethatyouwishtocreate
2.Description:Descriptionofthetemplate
3.Type(Static,SemiDynamicorDynamic).Basedonthetype
weselectKeyDetermination(forStatic),OrgUnit(forSemi
Dynamic)andFM(forDynamic).
4.AllowOrg:
5.AgentType
6.AgentID
7.FunctionModule

Templatefieldsarethenmaintainedsothatsystemcandeterminethe
rolebasedinruntimeonthefieldsmentionedinthetemplate.
Followingparametersareprovided:

1.FieldID:Fieldsthatwillbeusedtodeterminetherole
2.Ref.Table:Tablewhichwillbereferredforfetchingthefield
3.Ref.Field:TechnicalnameofthefieldintheRef.Table
4.SearchHelp
5.AllowRange
6.WildCard

https://blogs.sap.com/2016/04/19/opentextvimrolescreation/ 3/7
2017619 OpenTextVIM:Rolescreation|SAPBlogs

Sincetemplatescanbereusedfordifferentproductcodesorroles
hencetemplatefielddetailsaremaintainedbyprovidingproductcode,
objecttype,andAttribute.

AssignTemplatestoRole:Wehavenowdefinedrolesandtemplates.We
nowhavetoassigntemplatestotherolesothattherolecanbedetermined
basedonthetemplatewhichisassignedtoit.Arolecanbeassignedwith
morethanonetemplatehoweveratatimeonlyonetemplatecanbeactive.
ThiscanbedonebyusingTCode/n/OPT/CP_9CX2andmaintaining
valuesforfollowing:

1.ProductCode:Either005,LIXorPIR
2.ResponsibleParty:Thesearetheroleswhatwehavedefined.
3.KeyDetermination:TemplateID
4.Active:CheckingthisboxwillmakethetemplateIDactive.

MaintainRoleDeterminationSettings:Wehavenowmappedrolesand
templatebutwestillneedtodefinethevaluesthatwillbeusedinruntime
forroledetermination.Thisiscarriedoutbyusingtransaction/n
/OPT/CP_9CX4.Foreachroleunderaproductcode,weneedtomaintain
thevaluesofthefieldsorOrgunitorFM(dependinguponiftheyareStatic,
SemiDynamicorDynamictype)whicharedefinedinthetemplate.
https://blogs.sap.com/2016/04/19/opentextvimrolescreation/ 4/7
2017619 OpenTextVIM:Rolescreation|SAPBlogs

MaintainChartofAuthority(CoA):Ihavegivenabriefexplanationon
CoAinmypreviousdocument(pleaserefer:http://scn.sap.com/docs/DOC
57917).Inversion7invoiceapprovercanbedeterminedbasedontwo
logics:

1.Simpleapproval:Itissameastheoldversioni.e.gross
amountandmanagersinformation.
2.Levelbasedapproval:Approversaredeterminedbasedon
levelsandpacks.Levelsaredefinedforapprovallimitsi.e.
eachlevelwillhavedifferentamountrangethatcanbe
approvedbythatlevel.Forexample:Wecanhavedifferentset
ofapproversforamountranges:$0$5000,$5000$10,000,
$10,000$20,000andsoforth.Also,theycanbefurther
dividedbasedoncostcenter.Forexample:fortheamount
rangelevelof$10,000to$20,000wecanhavedifferent
approversfordifferentcostcenters.

NOTE:

1.CoAisusedforNonPOscenarios.ForPOscenarios,CoAis
notused.Theapprover(firstandonly)inPOscenariois
determinedbasedonbaselineimplementation.
2.CoAcanbeconfiguredtoincludecomplexitieslikeapprovers
canbedeterminedbasedonamountlimit,companycode,cost
centeretc.
3.OnecanonlydefinetheuserdetailsinCoAanduseacustom
logictodeterminetheapprover.Insuchascenarioallthe
approversshouldbemaintainedasusersinCoAandother
tabsinCoA(CoderandCoAdetails)canbeleftempty.

Prerequisite:Costobjectsaremaintainedforview/OPT/BL_T401Vand
fieldsforview/OPT/BL_T402V

https://blogs.sap.com/2016/04/19/opentextvimrolescreation/ 5/7
2017619 OpenTextVIM:Rolescreation|SAPBlogs

TcodetoaccessoldCoAis/n/OPT/VIM_7CX1andtoaccessnewCoAis
/n/OPT/VIM_APPR_COA.InnewCoA,thereisatabforapprovallimit.In
thistab,wecanmaintainlevelbasedapprovalconfiguration.

AbovescreenshotisoftheoldCoA.Tcode/n/OPT/VIM_7CX1

AbovescreenshotisofthenewCoA.TCode/n/OPT/VIM_APPR_COA

Substitutesetup:VIMallowssettingupofsubstituteforotherusersby
executingTCode/n/ORS/MAIN_SUBS

Ihopethisdocumentwillbeusefulforbasicunderstandingandworkingof
rolesinOpenTextVIM

AlertModerator

Bethefirsttoleaveacomment
YoumustbeLoggedontocommentorreplytoapost.

https://blogs.sap.com/2016/04/19/opentextvimrolescreation/ 6/7
2017619 OpenTextVIM:Rolescreation|SAPBlogs

Share&Follow
Privacy TermsofUse LegalDisclosure Copyright Trademark Sitemap Newsletter

https://blogs.sap.com/2016/04/19/opentextvimrolescreation/ 7/7