Regarding Agent Rule GRAC_REQ_MITIG_MONITOR_AGENT

Can anyone help me in determining if i can make use of agent rule GRAC_REQ_MITIG_MONITOR_AGENT to look for the approver at mitigation monitor stage under process ID SAP_GRAC_ACCESS_REQUEST_HR ??
SAP has suggested that this agent rule is only specific to process ID SAP_GRAC_ACCESS_REQUEST.. but when i checked in MSMP workflow process ID list, it is very much present in Step 2 - Maintain rules ....
Also kindly guide me with the steps i should follw to create custom agent rule for the same ....

Hello,
This is because agents, rules etc are tagged to "Process Type". Both process IDs SAP_GRAC_ACCESS_REQUEST and SAP_GRAC_ACCESS_REQUEST_HR belong to the same Process Type SAP_GRAC_AR. Thus, the agents that are available for one ideally should be available for the other too. This is not true for other processes as the process type there are different.
For BRFplus agent rule look at the document below, by Madhu Babu :
BRF+ Agent Rule based on Role Functional Area field using TABLE OPERATION and LOOP
Regards,
Sammukh

Similar Messages

Error in Generating GRC BRF Agent Rule

Hello Gurus,
I am atrying to generate a BRF Agent Rule but am aaunable to activate MSMP workflow corresponding to that:
Error in MSMP Workflow while activation:
1) MSMP process SAP_GRAC_ACCESS_REQUEST_HR version IMG Configuration Tables contains errors
2) abap dictionary data object binding is out of synchronization
Below are the screen shots of my BRF Rule configuration. I have created a procedure call which is tied to function module

Hello,
I assume you have already checked the below document where it is explained the procedure call and Function
cross check your settings with below document
AC10.0/10.1: Create Rule Based on Risk Violation in Request, Using BRF+ Procedure Calls
if everything is fine provide the MSMP error screen shot.
Regards
Baithi

Issue Regarding Transfer Rules

Hi All,
We have an issue regarding Transfer Rules. We are loading Data using 0FI_GL_4 into ZFIGL_A01. It is a periodic load of data.
Last month due to some issue in R/3 we have to replicate the Data Sources and retransport the Transfer Rules from BW Dev to BW Production. Next we loaded data into the InfoCube. Now when we execute the report for the current period I am not getting Master Data Values. All are coming as Not Assigned.
We have tracked down the issue and found that the issue may be incorrect mapping of Tranfer Rules. Is there any way in Prd where we can revert back to old version of Transfer Rules or can find the old mappings in Transfer Rules.
Regards
Jay

Hi Jay,
The only way you can find your old transfer rules mapping is to goto RSA1 -
> Infosource -> Tools -> Program and compare the versions .
Bye
Dinesh

Question regarding the rule of thumb regarding Exchange proc cores ratio to GC proc cores

Hi all,
I am studying towards my MSCE Messaging for Exchange 2013 and came across on CBT nuggets a statement regarding a rule of thumb when it comes to processor cores on Exchange 2013 server to GC
so Greg Shields from CBT nuggets says that the ratio should be
4:1 on x86 domain controllers
8:1 on x64 domain controllers.
So is he talking about 1 mailbox server role with 8 processor cores to 1 processor core on a x64 domain controller? what if there is already a heap of servers using that GC? In our datacentre we have 2 x64 domain controllers but also a whole range of servers
on that server network.
Also what if you have 2 mailbox server roles? are we then talking 16 : 2 ?
Hope someone can help clarify this.
Regards
ronnie.jorgensen systems engineer
My blog

Does this help explain it better?
http://blogs.technet.com/b/exchange/archive/2013/05/06/ask-the-perf-guy-sizing-exchange-2013-deployments.aspx
Active Directory sizing remains the same as it was for Exchange 2010. As we gain more experience with production deployments we may adjust this in the future. For Exchange 2013, we recommend deploying a ratio of 1 Active Directory global catalog processor
core for every 8 Mailbox role processor cores handling active load, assuming 64-bit global catalog servers:
If we revisit our example scenario, we can easily calculate the required number of GC cores required.
Assuming that my Active Directory GCs are also deployed on the same server hardware configuration as my CAS & Mailbox role servers in the example scenario with 12 processor cores, then my GC server count would be:
In order to sustain double failures, we would need to add 2 more GCs to this calculation, which would take us to 7 GC servers for the deployment.
As a best practice, we recommend sizing memory on the global catalog servers such that the entire NTDS.DIT database file can be contained in RAM. This will provide optimal query performance and a much better end-user experience for Exchange workloads.
and of course use the latest calculator version to determine your required specs:
http://blogs.technet.com/b/exchange/archive/2013/05/14/released-exchange-2013-server-role-requirements-calculator.aspx
When you calculate required GC cores, the ratio 1:8 applies to the cores required to support active mailboxes ("Mailbox role processor cores handling active load") and not to all cores physically available on Exchange server.
So, for example, if you have 32 total cores on an Exchange server but only 16 of them are actually needed to support active mailboxes (as determined by the calculator), you will need only 16/8=2 GC cores to support this Exchange server's AD queries.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Dynamic agent rule during approval

Hi gurus,
my question is based on a customer requirement.
they want a n-step approval with dynamic agent determination: fine.
then they want to maintain the substitutes: fine as well.
But what they want to do is to change the workflow path based on the substitute.
I mean: if the first aprover has set a substitute the first task goes to the substitute, but the following tasks have to follow the substitute hierarchy and not the original workflow path.
So we don't think the standard system way to use the substitute is not enough, but we need to determinate in the beginning if a substitute was set for some approvers.
The thing is that the substitute record is dynamic and has a validity end, and could be set after the workflow is started.
Is it possible at every step recalculate the workflow path and the next approvers (so to discover if a substitute rule has be changed or created or deleted)?
PS: we are using SRM 7.0 and the process controlled workflow.
Thank you very much in advance!
Regards,
Maria

Hi,
Yes. Agent is determined in each step right after previous step is completed in SRM70 Process-Controlled Workflow.
Please check following workflow objects.
WS40000016
TS40007943
Rule 40000138
FM /SAPSRM/WF_CORE_RESP_RESOLVER
Regards,
Masa

Dynamic agent rule changement during approval steps

Hi gurus,
my question is based on a customer requirement.
they want a n-step approval with dynamic agent determination: fine.
then they want to maintain the substitutes: fine as well.
But what they want to do is to change the workflow path based on the substitute.
I mean: if the first aprover has set a substitute the first task goes to the substitute, but the following tasks have to follow the substitute hierarchy and not the original workflow path.
So we don't think the standard system way to use the substitute is not enough, but we need to determinate in the beginning if a substitute was set for some approvers.
The thing is that the substitute record is dynamic and has a validity end, and could be set after the workflow is started.
Is it possible at every step recalculate the workflow path and the next approvers (so to discover if a substitute rule has be changed or created or deleted)?
PS: we are using SRM 7.0 and the process controlled workflow.
Thank you very much in advance!
Regards,
Maria

Hi Maria
I mean today the workflow starts and the system calculates the path based on the substitute rules active.
OK with that.
But what if the substitute rule change tomorrow?
How you are saying the substitute rule change tomorrow?. You should not assume it. You should confirm it. You cannot implement a work flow for tomorrow's requirement. Always there will be a change even if you implement for tomorrows change. Never do that. Do only for today's requirement.
My question is if it's possible to every step of the work flow change the agents.
I feel that this approach is wrong. simple view i will give u to thing. take only 2 steps
loop.
1) for determining the approver based on business logic in one method.
2) use the expression in the user decision step and send the work item for approval
endloop.
This i have explained for simple logic, create you own logic and apply on loop and endloop. It will work.
Regards
vijay

Question regarding Business Rule

Hi,
If I updated the business rule by updating any parameter in the Dev environment, do I need to export this business rule into Prod environment or Can I directly change the code in the production environment.
Please advice me on this.
Regards,
Upendra.

John:
Thanks alot for your quick response. And I have very silly question here. I am not sure how to import the file from dev to production.
I checked in the EAS console,there is Export option is there. After saving that rules in xml format, how to import into prod environment. I know, this is a simple question but as I don't know about this, this being a major question for me.
Thanks,
Upendra.

Regarding Agent Commission

Hai...
Does anybody have notes on Agent Commission..
with some detailed description.

Hi:
Refer to this documentation for Agent Commission
http://www.sap-img.com/sap-sd/steps-to-create-commission-for-agent.htm
Please let me know if you need more information.
Assign points if useful.
Regards
Sridhar M

Regarding rounding rule in condition

hi all,
i am facing an issue related pricing condition,
i have created one condition type- ZROU(round off rule).
this means supoose, i have net price in the PO is 23.60. if i put this condition and i put .40, then total price should be 24. and its comming while creating the Po.
but when iam creating Migo, in accounting document, the price should be taken as 24 but it is taking 23.60. why this condition type effect is not reflecting to MIGO & MIRO.
i need the solution urgently, pls help.
regards,
susanta

Hi,
Create Condition Type "ZROU" as a Positive discount condition. In M/06 keep
Cond. class - A (Discount or surcharge)
Calculat.type - B (Fixed amount)
Use it with Base Price in Pricing
For e.g. In MM Pricing (M/08)
Step 10 - PB00 (Base Price) = 23.60 INR
Step 20 - ZROU (Rounding Value) = 0.40 INR
Step 30 - Net Value = 24.00 INR (From 10 To 30)
If you donot want it as Discount condition then use it as delivery cost condition and mark "Accrual" and do posting to a separate GL. by creating and assigning a new A/c key under Accrual column of Pricing (M/08)
Ans in OBYC > Assign GL as "Rounding Off Difference" for that new A/c Key

Issue regarding update rules--Table RSUPDKEY

Hi Friends..
Can anyone please tell me something about the table RSUPDKEY?
I knw the use of this table.......but how the fields are getting updated.......how the value in the filed BOOLEAN getting populated?
I am facing a strange problem...
In Production system.....For one keyfigure....one characteristic is not mapped...initial value option is selected.But in the field Source Characteristic that charecteristic name is selected but that option is not selected.......it means the field is not blank......
For Prod......in the table RSUPDKEY.........for this rule......in the Source Infoobject field that infoobject name is coming and Boolean field = X
When I am trying to do the same thing in the development box............i.e. in the Source Characteristic field I have selected the infoobject and i have selected the Initial value option............after that when I am saving it.......the Source characteristic field remains blank......
In Dev box in this table both the fields are blank.
Thanks and Regards,
Debjani.....

Hi,
You can check End Routine .
An end routine is a routine with a table in the target structure format as input and output parameters. You can use an end routine to postprocess data after transformation on a package-by-package basis
http://help.sap.com/saphelp_nw70/helpdata/EN/43/bcdc6001344defe10000000a422035/content.htm.
Below is the lSAP help link for migration of 3.x update rules & transfer rules.
http://help.sap.com/saphelp_nw70/helpdata/EN/43/f00e2696d24c5fe10000000a155369/frameset.htm
Hope this helps!
Edited by: Meera Murali on Mar 4, 2009 9:52 AM

Regarding update rules activation in inventory management(2LIS_03_BF)

Hellow gurus,
i am working on inventory management with snap shot scenario for that we are using 3 business content datasources they are (2LIS_03_BX, 2LIS_03_BF, 2LIS_03_UM), now i want to activate the update rules for infosource(2LIS_03_BF) & cube, when i check the update rules it shows every thing is ok, but not activating ,please could you give me the suggestions
Regards,
Chandra.

bf setuptable filling based on posting date
give the posting date and give the name of job run
give the termination date and time
execute in background.you you can start the more jobs
depending on your data.you have bulk data you can divide the
jobs in based on posting date.
after that check the status in sm37.

Regarding Agent

Hi Experts ,
i am new to ODI can we have more than one MASTER_REPOSITORY, in which situation we go for more than one master_repo,what is the advantage
please help me
regards
ksbabu

In 11g odi agent can be connected to only one master repository. Please refer to Setting-up the Topology - 11g Release 1 (11.1.1)

Regarding Business Rule Framework

Hi,
Could u please explain the process of Business Rule Framework(BRF)
and how to create this Business Rule Framework(BRF)
explain with step by step process.

Hi,
To have a BRF object, you should have BRF Application Class.
to do this -
1. go to tcode - BRFAPL01, create one.
2. then go to tcode BRF- create object with the same name as Application class.
3. Now run the program CRM_BRF_COPY_IMPL_CLASSES , and give your brf object name which you created in above steps.
4. now your BRF object is created with standard implementation classes.
5. Go to tcode BRF, in All Groups folder, you can now create actions, events, rules using the standard implementation classes.
6. If you want to create your own implementation classes, go to tcode BRFIMC01 and create new ones.
refer to http://help.sap.com/saphelp_erp2004/helpdata/en/dc/38bb4006d9cc38e10000000a155106/frameset.htm
for more information
Reward points if found helpful
Seema

Query regarding Overtime Rules for India

Hi,
I am not clear about how to configure the statutory overtime rules (as per Overtime act) for India. I am not sure how many OT hours per week/month/quarter is allowed. Also, I am aware that some of the extra hours worked by the workmen can be considered as "Additional Hours", but not sure how exactly these things are computed. Can anyone help me please?
-Shambvi

Generally according to factories act, the max no of working hours per week is 48, with a max working time of 9hrs per day. Any thing above this is treated as overtime. This over time should not exceed 50 hrs per quarter, and can be extended to 72 hrs with a written permission of the factories inspector.
The rate at which over time is paid is twice the normal daily wage of the employee.
Hope this helps
Raghu

Regarding agent running

Hi,
I am starting the agent on the server by the command line :
. agentscheduler.sh -name=<Physical_Agent_Name>
But if i close the Unixbox the agent is getting killed and the scheduling process stops. So how do i overcome this in production environment?
Thanks,
Vikram

Hi Vikram,
You are starting a OS command that exists while the window is opened.
To have the agent working all the time you need to install it as a service. Take a look in the user manual about how to do.

Regarding Agent Rule GRAC_REQ_MITIG_MONITOR_AGENT

Similar Messages

Maybe you are looking for