Approval Procedure determination via Multi Level Categorization
Document describes configuration of having automatic approval procedure determination depending Multi Level Categorization schema values.
First you need create Service Manager Profile Search SPRO for “Define Service Manager Profiles”
There is a nice blogpost created by Boris Milosevic for this Step3 – Rule Modeler Profile Creation (CRM_IC_55 spro)
Example Scenario: Automatic determination of Approval Procedure depending of the Categories values,
if category value equals BCT then set approval procedure ZMCR_01
elseif category level equals ATH then set approval procedure ZMCR_02
and automatic filling of the approval steps .
Steps:
- Assign Rule modeler to Categorization schema
- Create Rule Policy with same Rule modeler
- Release Rule policy, check approval settings
- Create Request for Change test and see results
1. Assign Rule modeler to Categorization schema
Launch transaction SM_CRM, Service operations – Caregorization Schema. Open categorization schema and insert Rule Modeler in Application Areas like on screenshot
Do not forget to activate your schema
***************************************************************************************************************************************
*TIP wait a while, Categorization Schema will be shown in Rule policy, you need to wait even after *
*Categorization Schema is Activated *
***************************************************************************************************************************************
2. Create Rule Policy with same Rule modeler
Service Operations – Rule Policy – Create
First Condition check transaction type is ZMCR and User status = Validation and Category have value BCT
Press add entry and choose Order Category, here example category value must contain BCT
Action set approval procedure = CT-CAB(example) ZMCR_01
On second level condition check approval procedure = CT-CAB(example) and approval step ZMCR_01
Action set partner BP number 279 for approval step ZMCR_01
***************************************************************************************************************************************
Now create separate conditions for category equals ATH
Order Category, here example category value must contain ATH
Action set approval procedure = CT-CAB(example) ZMCR_02
On second level condition check approval procedure = CT-CAB(example) and approval step ZMCR_99
Action set partner BP number 279 for approval step ZMCR_99
* I have similiar naming for approval procedures and steps not the best example soz for that
3. Release Rule policy, check approval settings
Release Draft Rules and Save
Find in SPRO Define Approval Settings
Set Rule modeler profile to steps and approval determination procedures
Check again SPRO Define Service Manager Profiles Your Rule policy is assigned
4. Create Request for Change test and see results
Simply Create Request for change type ZMCR and change user status to validation, by choosing appropriate action.
Change Category between ATH and BCT and see that approval will get filled automatically
The end.
Dan,
Thanks for putting this info together. It would be helpful for many here, as there is no single piece of document available here on this topic. Great effort.
Thanks,
Vivek
True words.
Thanks Vivek !
Many Thanks.
Now i am using in our organization the same method many thanks again
Regards
Mohammed
Nice one Dan...keep posting 🙂
Thanks Dan
Question : Would you be able to list any guidelines on when to use rule policies vs BRF+ for auto determinations ( I have read other blog of yours where you show how a developer can be populated in CHARM using BRF+) ?
Hi, unfortunatly i have not seen such guidlines yet.
Just my recommendation use BRF+ if it's available by stanard.
To decide which technology to use need to sit and think 🙂
Cheers