CRM Rules

[Kris WUG]

Hi Dart,
 
That's awesome...It does work fine with the evaluation paths you mentioned
below.
I will put the OSS note in regards to SAP_TAGT evaluation path to extend for
CP.
 
Regards,
Kris.
 
 
 
 
----- Original Message -----
From: "Dart, Jocelyn" <jocelyn.dart at sap.com>
To: <SAP-WUG at MITVMA.MIT.EDU>
Sent: Monday, February 16, 2004 6:40 PM
Subject: Re: CRM Rules
 
 
> Hi Kris,
> There are some special evaluation paths in a EBP/CRM system.
> Some of these include the CP level.
> E.g. BP_US which goes from the business partner to the user via the
contact person.
> Some others are OO-S-CP1/2/3
>
> Report RHWEGID0 is useful to find relevant evaluation paths in any system.
>
> Must be a CRM problem as SWX_GET_MANAGER works fine for SRM - in our EEBP
org plan both
> relationship S-CP-US and S-US are set up automatically.
>
> Suggest you put a query into OSS to ask the developers what eval paths you
can safely
> use.  Might also suggest to them that they extend SAP_TAGT to include the
CP level.
> Wouldn't hurt SRM and would make your life easier in CRM.
> Regards,
> Jocelyn
>
>
>
>
>
> -----Original Message-----
>> From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of Kris
WUG
> Sent: Tuesday,17 February 2004 11:55 AM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Re: CRM Rules
>
>
> Abby,
>
> Thank you for the fast response. I really appreciate it.
> Yes I agree, infact I implemented the same since our testing people were
> waiting for it.
> My rule is working after this special code what you mentioned.
>
> But, I want to know if SAP has done any thing about this agent
determination
> fm RH_STRU_GET.
> Which used to work fine in HR but not in CRM when we use SAP_TAGT as
> evaluation path .
>
> May be I am posing a wrong question. Because the above FM retrieves CP as
an
> agent when we pass position
> but the workflow rule donot understand CP as an agent. It will not
determine
> the users from CP.
>
> Can Workflow rule functionality in CRM understand "CP" as an agent ?
>
> Regards,
> Kris.
>
>
> ----- Original Message -----
>> From: "Dywan, Abby" <adywan at clarkstonconsulting.com>
> To: <SAP-WUG at MITVMA.MIT.EDU>
> Sent: Monday, February 16, 2004 5:34 PM
> Subject: Re: CRM Rules
>
>
> Hi Kris -
>
> You're going to have better luck using a different function module:
> RH_READ_INFTY.  Use this function module to get both from BP -> CP and
CP ->
> US.
>
> You're going to read infotype 1001.  The eval path for CP -> BP is 'B207'
> and for CP -> US 'B208'.  In my experience, your best results will be to
> send either to a BP or a US, NOT a CP.
>
> To get the manager, make sure you are passing in the CP (which has worked
> for me) or the BP - the username won't work.
>
> I do not know of any program to run to make sure that all the agent
> determination modules work properly in CRM - but please keep in mind, the
> org structure in CRM sits a little differently - a position is attached to
a
> business partner, and from the BP the personnel number and the userid are
> attached at the same place.
>
> In R/3, the position is attached to an employee, which attaches to a user
> id.
>
> Hope that helps -
> Abby  :)
>
> -----Original Message-----
>> From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]On Behalf Of
> Kris WUG
> Sent: Monday, February 16, 2004 4:20 PM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: CRM Rules
>
>
> Dear workflowers,
>
> When I use RH_STRUC_GET function module to find agents by passing position
> to the import parameters.
> It is not determining the users/agents. It gives me a CP number as an
agent
> but workflow workitem donot understand the
> CP object as an agent.  Also I tested the rule 168 to find the superior
> manager. This rule is not working
> either in CRM.  "I assume this is especially because Business Partners(BP)
> are assigned to Position instead of users".
>
> Here is the question.
> Is there any program that we need to run to make sure all the SAP agent
> determination function modules work properly in CRM?
>
> I appreciate any of your help if you already encountered this issue.
>
>
> Kris.
>