ALE HR box to FI/LO box for Organizational Plan

Soady, Phil phil.soady at sap.com
Thu Mar 20 23:31:17 EST 2003


Good input Greg,
this topic could blow out into a blue print design.
Such good feedback ;-)
 
In line with Gregs input,
safe to say that is some key HR customizing is not consistent
across the boxes, expect issues !
 
 
Phil Soady
Senior Consultant
Business Technologies
SAP Australia
* : 0412 213 079
* : phil.soady at sap.com
 
 
 
 
-----Original Message-----
From: Brehm, Gregory (GBrehm) [mailto:GBrehm at chevrontexaco.com]
Sent: Friday, 21 March 2003 2:50 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: ALE HR box to FI/LO box for Organizational Plan
 
Along with Phil's suggestions,
 
You will definitely need some config data from HR on the FI/GL side to
ensure data integrity.  We have had experience with HRMD_A for 4.6b HR
to 4.6b FI/GL/CO/AM environment.
 
So we started with data for the following views/tables/objects
(consultant setup and I oversaw process).
 
R3TR TABU T500P
 
 R3TR TABU T503T
 
 R3TR TABU T526
 
 R3TR TABU T501T
 
 R3TR TABU T588Z
 
 R3TR TABU T77INT
 
 R3TR TABU T501
 
 R3TR TABU T503K
 
 R3TR TABU T529A
 
 R3TR VDAT V_T001P                                               K
 
 R3TR TABU T529T
 
 R3TR VDAT V_T503Z                                               K
 
 R3TR VDAT V_T549A_2                                             K
 
 R3TR VDAT V_T500P                                               K
 
 R3TR VDAT V_T549A                                               K
 
R3TR VDAT V_T591A                                               K
 
R3TR VDAT V_T530                                                K
 
R3TR TABU NRIV                                                  K
 
R3TR PMKC PLOGI
 
R3TR PMKC ABKRS
 
R3TR PMKC PINCH
 
R3TR PMKC IGMOD
 
R3TR VDAT V_T588D                                               K
 
R3TR VDAT V_T530                                                K
 
R3TR VDAT V_T588C                                               K
 
You may want to discuss "sensitive fields" that may not be needed for
the HR data (SSN, Birthdate, etc) on FI side and choose conversion
routines to "BLANK" out fields.  There is generally a lot of sensitivity
around certain HR data and it is important to discuss with data owner's.
 
Additionally around ALE distribution for initial conversion (before you
setup change pointers) there is a note in OSS that talks about movement
of data in a certain fashion to limit 52 status's (OSS note 363187).
You definitely want to review.
 
Finally, you may want to run changepointer cleanup for HRMD_A objects as
you go(1 month only lag of data perhaps).  The HRMD_A object seems to
have issues with too many obsolete or old change pointers.
 
Hope this helps...Greg
 
-----Original Message-----
From: Soady, Phil [mailto:phil.soady at sap.com]
Sent: Thursday, March 20, 2003 7:02 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: ALE HR box to FI/LO box for Organizational Plan
 
 
See the HELP CD, ALE Scenarios HR Master data.
 
Basically one must:
        Define Distribution model in BD64. Use Message type HRMD_A
        Add the Object types and Infotypes required to the filter in
BD64.
        Eg S,O,C, 1000, 1001 and perhaps even P (0000,0001,0002,....)
 
Use PFAL to send them over initially.
Activate change pointers to send deltas. See BD61 and BD50.
 
Then schedule RBDMIDOC to run periodically to send of changes.
 
(NOTE this is for 2 standard SAP systems, not WP or CRM etc)
A slight variation HRMD_ABA is needed when talking to non core ERP
systems.
 
hth
 
 
Phil Soady
Senior Consultant
Business Technologies
SAP Australia
* : 0412 213 079
* : phil.soady at sap.com
 
 
 
 
-----Original Message-----
From: Graeme Jones [mailto:Graeme.Jones at eu.tenneco-automotive.com]
Sent: Wednesday, 19 March 2003 7:59 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: ALE HR box to FI/LO box for Organizational Plan
 
Hi
 
We have x2 SAP landscapes, one for HR and another for FI/LO.
 
The organizational structure is maintained only on the HR box.
 
Does anyone have experience of ALE'ing that data between two landscapes
....... what data needs to be syncronized between the landscapes ?
 
Thanks
Graeme.
 


More information about the SAP-WUG mailing list