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

Similar Messages

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

How to send workitem to dynamic agents

Hi all,
This is my problem, I have to send workitem to dynamic agents (number of agents vary).
I have the approver details in the workflow container, now i have to send the workitem to the apporvers, since the number of approver varies i am using while loop and i am doing container opreration for each loop. I have the apporvers details in a multiline container based upon this i have to send workitem to the first approver and after his decision i have send workitem to second approver and it goes on.
Regards
Balaji E.

Hi all,
After struggling for 2 day i found the solution for my problem.
My Problem:
I get the approver details from a function module and i call this function module in a method and through a task i pass the multiline container element (which is holding approvers details) to my workflow container. My problem is i dont know how to loop this multiline container element in my loop (while).
Solution:
There is a macro to copy one container element to another container element it may a multiline container too.
SWC_COPY_ELEMENT <SourceContainer> <SourceElement> <TargetContainer> <TargetElement>.
i used this macro while i run the method at first time and i copy this value to another container (multiline) element at this step itself.
In my next step i pass only the loop number (i have a workflow container element. and i increment this container element for each loop) to the method and in that method i read the multiline container element based on this loop number and i pass the result value to task-->workflow.
From here i proceed further.
Thanks all of you.
SDN Forum helped me a lot in this issue.
Regards,
Balaji E.

QM:Maximum skip duration in dynamic modification rule

Hi
Can anybody explain how the system behaves with
QM:Maximum skip duration in dynamic modification rule.
Gobinathan G

Hi,
In dynamic modification rule you maintain the inspection modification based on the quality level. You mention the maximum skip duration for resting the skip status if the inspection lot is not created during the specified period after creation of last inspection lot. That means the Skip status will be reset to Inspection status if the lot is not created during the specified period & you will have to inspection the lot instead of skipping. If the lot is generated within the period, then you will be able to skip the inspection.
Regards,
Prashant

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

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

Dynamic type conflict during the assignment of references. - Error while generating proxy in the backend

Hi All,
I get a short dump while generating a proxy in the backend.I give the package and the prefix and end up with a short dump.
Does any one know why this mught come up
"Dynamic type conflict during the assignment of references."
background: I imported a WSDl provided by legacy into PI and created service interfaces and then trying to generate a proxy class while i get this error.
Thanks.

Hi Shyamsundar,
I will explain a problem that I usually see in some developments:
XSD originally:                                  XSD transformed:
Root                                                     -> Root
Tag 1 type int                                    -> Tag 1 type int
Tag2 type string                               -> Tag2 type string
Tag3 type any                                  - Tag3 type string
Normally the tag3 should have a XML inside. Then the ABAPers have to construct the tag3 with a CDATA structure (CDATA is used to put in an XML tag more XML tags inside like a text and no to be interpreted).
Later in SAP PI you can extract the cdata with an XSL, you can find some examples in the SCN.
I don’t like to convert the whole XML in only one string tag, because this makes difficult the develop for the ABAPers, although the work inside the PI is very easy because with an XSL you can extract the whole message easily. (You can find some examples in the SCN)
Regards.

How to debug a transfer rule during data load?

I am conducting a flat file (excel sheet saved as a CSV file) data load. The flat file contains a date field and the value is '12/18/1988'. In transfer rule for this field, I use a function call to transfer this value to '19881218' which corresponds to BW DATS format, but the monitor of the InfoPackage shows red error:
"Value '1981218' of characteristic 0DATE is not a number with 000008 spaces".
Somehow, the last digit or character of the year 1988 was cut and the year grabbed is 198 other than 1988. The function code is (see below in between two * lines):
FUNCTION ZDM_CONVERT_DATE.
""Local Interface:
*" IMPORTING
*"     REFERENCE(CHARDATE) TYPE STRING
*" EXPORTING
*"     REFERENCE(DATE) TYPE D
DATA:
c_date(2) TYPE c,
c_month(2) TYPE c,
c_year(4) TYPE c,
c_date_combined(8) TYPE c.
data: text(10).
text = chardate.
search text for '/'.
if sy-fdpos = 1.
concatenate '0' text into text.
endif.
c_month = text(2).
c_date = text+3(2).
c_year = text+6(4).
CONCATENATE c_year c_month c_date INTO c_date_combined.
date = c_date_combined.
ENDFUNCTION.
Could experts here tell me what's wrong and also tell me on how to debug a transfer rule during data load?
Thanks

hey Bhanu/AHP,
I find the reason. Originally, I set the character length for the date InfoObject ZCHARDAT1 to 9, then I find the date field value (12/18/1988)length is 10. Then I modified the InfoObject ZCHARDAT1 length from 9 to 10 and activated it already. But when defining the transfer rule for this field, before the code screen, click the radio button "Selected Fields" and pick the filed /BIC/ZCHARDAT1, then continue to go to the transfer rule code screen, but find the declaration lines for the infoObject /BIC/ZCHARDAT1 is as following:
InfoObject ZCHARDAT1: CHAR - 000009
    /BIC/ZCHARDAT1(000009) TYPE C,
That means even if I've modified the length to 10 for the InfoObject and activated it, but somehow the transfer rule code screen always takes the old length 9. Any idea to have it fixed to take the length 10 in the transfer rule code screen defination?
Thanks

IDM : How to get the Resource name in Exclude Rule during Reconciliation?

Hi
Problem Statement => How to get the Resource name in Exclude Rule during Reconciliation.
Problem Description => Apparently, we use exclude rule for not consider some account during reconciliation.
I need the resource name in exculde rule during reconciliation. I tried with getResources() method which is an inbuilt method.But it gives all the resources are aviablable in the repository (IDM). I need only the current reconcilied resource name instead of fetching all the resouce.
Can any one please help how to get the resource name in exclude rule during reconciliation?
Thanks in advance for you help.
Thanks,
Chellappan

Hi,
Thanks for your reply.
I have 50 resouces and these resouces using the same kind of exclude rules. In the exclude rule, i am using resource name to do some work. If i get the resouce name in exclude rule, then i can use the same exculde rule for 50 resources. This will minimise the rule count from 50 to 1. For that, i need resouce name.
Thanks,
Chellappan Sampath.

Why doesn't Mail apply rules during sleep?

I often wake up the MBP in the morning to find that Apple Mail has not applied any rules to incoming mail. I can fix it easily by selecting all the new mail and applying rules. In normal, waking operation it applies rules automatically. But past versions of Mail always applied rules during sleep, too. Why now? Is there some way to make it apply rules?

Exact same problem, only since switch from SL to ML. Have to tell the machine to never sleep???

Does the "The Project Owner has the same RBS value as the User" dynamic category rule include Status Managers?

I tested the following scenario in Project Server 2010 and 2013:
Assume you have three users: User1, User2, and User3.
User1 has RBS value Org.UnitA
User2 and User3 both have RBS value Org.UnitB
User3 belongs to a group that gets permissions to view projects from a category with "The Project Owner has the same RBS value as the User" setting enabled.
User2 creates ProjectABC and by default becomes the project Owner. User2 creates a task in the project, and by default becomes the Status Manager of the task.
User2 then changes the project owner to User1 and republishes the project. User2 remains the Status Manager in the project task.
User3 can still see ProjectABC. Apparently this is because User2, who has the same RBS value as User3, is still a Status Manager of project tasks.
If I change User2 RBS value to Org.UnitA, then User3 can no longer see ProjectABC. Note that User2 is not the project Owner at this stage, but the change in User2's RBS still affects the visibility of the project.
It seems to me that in "The Project Owner has the same RBS value as the User" dynamic category rule, the "Owner" should be "Owner or Status Manager".
Is this a bug or by design?

Hi Barbara,
Thanks for going through the trouble of reproducing the behaviour. It's interesting to know that Effective Rights in Project Online displays different results.
The system in which I tested this scenario is updated with the December CU, so I'm guessing you'll still get the same result after updating your environment.
In my usage scenario, a user needs to create projects on behalf of other users, and then change the Owner. Unfortunately this doesn't change the Status Manager of tasks, and consequently the visibility of the project is not what was expected.
The user who creates the project can change the Owner, but can't change the Status Manager. The new owner would have to open the project for editing in Project Pro, change the Status Manager value of every task, and republish. Precisely the sort of extra
work that the users want to avoid.
Using delegation might be a workaround, but opens up a whole new can of worms in terms of information security. It's unfortunate that the "The Project Owner has the same RBS value as the User" setting doesn't do what it says, but potentially
opens up visibility of projects to a wider audience than intended.

Update was terminated when Dynamic modification rule is changed

Hi Gurus,
When short text is changed manually in Dynamic modification rules (QDR2), I saved it "Dynamic modification rule xxx was changed". Next I got the error message: "Update was terminated".
Detail:
System ID....   xxx
Client.......   xxx
User.....   xxxxxxx
Transaction..   QDR2
Update key...   xxxxxx
Generated....   06.11.2009, 11:54:46
Completed....   06.11.2009, 11:54:47
Error Info...   Processeur ABAP : RAISE_EXCEPTION
I think there is an incoherence in between tables QDDR & QDDRT.
How can we fix this error?
Thanks.
Stéphane

Hi
sometimes it happens that system takes some time to save & update the data in the background.
so wait for some time & again check .It will work.
The data which if changes do not have any repercation on existing system can be changed at any time.
check the tables
QDDR & QDDRT again
Regards'
Sujit

Dynamic modification rule

Hi, what is dynamic modification rue functionality in qm? pls explain with one example how to use the same.

DMR: simple words means when you dynamicall want to change the stages of the inspection.that means you want to reduce the inspection or skip the lots or tighten the inspection.
DMR mainly used for reducing the cost of inspection.
There are many links which are available with example for the same.
Re: DM rule
DMR
Re: Dynamic modification
Dynamic Modification Rule (DMR) at lot creation
DMR - QUALITY LEVEL
Re: DMR @ Char level
DMR inspection stage

Dynamic Modification Rule (At Lot Level) In Quality

Dear All
Please explain me in detail how to use Dynamic Modification Rule (At Lot Level) In quality Module.
Thanks & Regards
Rahul Bhardwaj

Dear,
In material master under (QM view) active "Skip allow" indicator.
Skip lotting in SAP is some what different. SAP does not actual prevent the creation of the inspection lot. It simply sets a status of SKIP on the inspection lot. The lot is still there and if desired, it can be used. Once a characteristic is accessed in the lot, it becomes a normal inspection lot.
You need to setup an auto UD batch job for processing the skip lots and closing them. Skip lots have their own "wait" time defined in plant QM config settings.
That means by DMR you can not stop the inspection lot generation.
Hope clear to you.
Regards,
R.Brahmankar

Dynamic Modification Rule In Quality Module

Dear All
Please explain me in detail how to use Dynamic Modification Rule (At Lot Level) In quality Module.
Thanks & Regards
Rahul Bhardwaj

Hi,
Dynamic Modification Rule
Definition
The basic data record contains the definition of the inspection stages, the dynamic modification time (at lot creation or after the usage decision has been made), and the conditions for the inspection stage change. Inspection stage changes occur on the basis of the inspection results that are recorded for inspection lots and inspection characteristics (that is, on the basis of their acceptance or rejection).
Use
You can vary the inspection scope using dynamic modification rules. You can store a dynamic modification rule in one of the following places:
In the inspection plan at the header level
In the inspection plan at the characteristic level
In the inspection setup of the material master record at the inspection type level
Structure
A dynamic modification rule contains the definition of the inspection stages, the dynamic modification time, and the conditions that lead to an inspection stage change.
There are always two options that apply to the conditions for an inspection stage change: An acceptance (OK) and rejection (not OK). The system uses these conditions to update the quality level, which always reflects the current status.
The functions for maintaining and displaying dynamic modification rules are primarily contained on three screens:
On the initial screen, you enter the identifier for the dynamic modification rule.
On the header data screen, you maintain a short text and the blocking indicator, and define the time of dynamic modification (at lot creation or when the usage decision is made) and the reset period.
The reset period defines the period of time, which must elapse before the quality level again uses the initial inspection stage specified in the dynamic modification rule as the current inspection stage.
On the inspection stages screen, you edit the inspection stage data (inspection severity, skip, initial inspection stage, and short text). You create the rules for the inspection stage change on this screen.
In QM, the inspection stage describes a test or inspection status that is based on the inspection history and predefined rules. Different inspection stages mean that there are also different inspection scopes and/or inspection severities.
Creating a Dynamic Modification Rule
1.Choose Logistics ® Quality management ® Quality planning ® Basic data ® Sample ® Dynamic modification rule ® Create.
2.Enter the identifier for the dynamic modification rule on the initial screen or choose Copy to use an existing dynamic modification rule as a copy model.
3.Choose Dynamic modification rule to carry out the following activities on the header data screen:
Edit the short text for the dynamic modification rule.
Define the time of dynamic modification (at lot creation or usage decision).
Define the reset period.
Set the blocking indicator if you want to prevent the dynamic modification rule from being used in an inspection plan.
4.Choose Next screen to carry out the following activities on the inspection stages screen:
Define inspection stages.
Define inspection severities for individual inspection stages.
Identify skips.
Identify the initial inspection stage.
Maintain short texts for the inspection stages.
5.Choose Stage change to carry out the following activities on the screen for creating the inspection stage change:
Define the specifications for a stage change for an acceptance (OK)
Define the specifications for a stage change for a rejection (Not OK)
6.Choose Next screen to return to the inspection stages screen and save your entries.
When you save the data, the system prompts you for a confirmation. If you want to include the dynamic modification rule in the allowed relationships for sampling procedures and dynamic modification rules (this is only necessary if a sampling procedure is used in a sampling scheme), you can switch directly to the assignment transaction by confirming this prompt. You define the assignment of sampling procedures and dynamic modification rules in this screen.
If you do not confirm the prompt, the system returns directly to the initial screen and confirms that it has created the dynamic modification rule.
Hope this helps.
Award points if useful.
Regards,
Tejas

Dynamic agent rule during approval

Similar Messages

Maybe you are looking for