Org. structure in EBP and R/3

Patrick Green patrick.d.green at us.pwcglobal.com
Fri Nov 16 14:37:42 EST 2001


A colleague asked that I post a follow-on to Christine's question on his
behalf:
 
 
Hi Patrick -
Thanks for getting our question addressed by the SAP workflow community.
As mentioned the R/3 Reporting Structure is directly maintained in R/3 and
then ALE'd to EBP.  Here's an overview of what we have configured:
 
In R/3:
The personnel id (P) is linked to the user ID (US) via the infotype 105.
The personnel ID(P) is then assigned to a position (S).  The reporting
structure has orgs(O) with links to the positions(S).  Positions(S) are
also tied to responsibility(RY) for the authorization levels.
 
In EBP:  (Before ALE load)
A procurement organization(O) must be created as well as shopping cart
users must be defined.  To define a user as a shopping cart user, the
function module BBP_CREATE_USER can be executed, where the pre-defined user
id and existing Organizational Unit (Procurement Org) must be entered.
Upon execution, the following objects and relationships are created:
 
- A central person (CP) is created for the userID [establishing a similar
relationship in R/3 and mimicking 105 infotype;  however, no PA105 table
exists in EBP]  This CP record is linked:
     Holder(B008) to position (S)
     Identical (B207) to business partner(BP)
     Identical (B207) to user ID (US)
 
-  A position(S) for that userid is created which:
     belongs(A003) to the org unit(O)specified
     holder (A008) a central person(CP)
     holder (A008) a userid (US)
 
When the R/3 Reporting structure, with all the necessary relationships and
infotypes(including 105), is loaded to EBP, EBP reacts to the infotype 105
by creating a CP record for the P record from R/3; thus creating all the
relationships normally created when a shopper is defined.  With the rule
that a user can only be assigned to  one personnel number; the PA105
relationship from R/3 overlays the existing CP relationships in EBP; hence
the shopping cart user's definition is partially obliterated to the point
that the user can no longer create a shopping cart.
 
One way to solve this is to allow multiple user assignment to a personnel
id.  Is this possible?
 
Any insights will be greatly appreciated.
 
 
 
 
 
 
"Wennerbo, Christine" <christine.wennerbo at sap.com>@MITVMA.MIT.EDU> on
11/16/2001 07:47:57 AM
 
Please respond to SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
 
Sent by:  SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
 
To:   SAP-WUG at MITVMA.MIT.EDU
cc:
Subject:  Org. structure in EBP and R/3
 
Hi,
I am wondering if you have any experience regarding the approach of the
org.
structure in EBP(20C) and R/3 Backend (46C). Do you know if there is any
program available that updates the org. structure in EBP from the one in
R/3
Backend? If there is, do you have any experience with this solution?
Regards
Christine Wennerbo
 
----------------------------------------------------------------
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material.  Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited.   If you received
this in error, please contact the sender and delete the material from any
computer.
 


More information about the SAP-WUG mailing list