OM CUSTOM RELATIONSHIPS

9

Click here to load reader

description

ORGANIZATIONLA MANAGEMENT CUSTOM RELATIONSHIP MATERIAL

Transcript of OM CUSTOM RELATIONSHIPS

Page 1: OM CUSTOM RELATIONSHIPS

Creating Custom RelationshipsRelationships are special subtypes of infotype 1001. Each relationship has two relationship types, A (bottom up) & B (top down). For each relationship created (A or B), the corresponding inverse relationship is automatically set up.

Steps involved with creating custom relationships:

1. Create subtype of infotype 1001 "Relationships" in the step "Maintain subtypes"Where in IMG to configure - where to begin:SE11 - HRP1001

SM30 - T778VCustomizing button

 

Page 2: OM CUSTOM RELATIONSHIPS

Dialog for which project to choose - Skip buttonThen choose one of the various places this table shows up in config. If the first choice doesn't take you to an area that makes sense, choose another one until you find yourself here (this was using table T778U (subtypes) & T778V (relationships)): 

 IMG->Personnel Management->Organizational Management->Basic Settings->Data Model Enhancement->Infotype Maintenance->Maintain Subtypes The subtypes should be combo of AXXX (bottom up) & BXXX (top down) XXX should be 3 characters EHA - BEHA is EHS Primary PI for & AEHA has EHS Primary PIEHB - BEHB is EHS Primary Contact for & AEHB has EHS Primary ContactEHC - BEHC is EHS Secondary PI for & AEHC has EHS Secondary PIsEHD - BEHD is EHS Secondary Contact for & AEHD has EHS Secondary Contacts EHE - BEHE is EHS Rep for & AEHE has EHS RepsEHF - BEHF is EHS Coordinator for & AEHF has EHS Coordinators This step is confusing. Documentation in "Maintain Relationships" says that before we create a new relationship, we should create the subytpe of infotype 1001 via "Maintain subtypes". But the documentation in "Maintain subtypes" says that relationships are special subtypes of infotype "Relationship". "This function is dealt with separately since there are a number of special points to note when setting up these subtypes. For this reason, you should create relationships in the step "Maintain relationships"! Kyriakos created 8 new subtypes

Page 3: OM CUSTOM RELATIONSHIPS

with time constraints for each:

 

2. Create new relationshipsIMG->Personnel Management->Organizational Management->Basic Settings->Data Model Enhancement->Relationship Maintenance->Maintain RelationshipsI created EHA

 (notice it is backwards from SAP standard - Kyriakos created standard)

3. Specify whether an error message, a warning or an information message should be issued when a weighted relationship exceeds 100%.

4. Specifiy whether the weighting percentage of a relationship should be displayed or hidden in the Relationship infotype.

5. Deactivate the recursiveness check, if necessary. I'm pretty sure these 3 steps are accomplished via Relationship Characteristics & Additional Data on Relationships, but I left them alone because I wasn't sure

Page 4: OM CUSTOM RELATIONSHIPS

what their impact was. 

6. Specify which relationships should be allowed for which object types. This is done through the "Allowed Relationships" (see above)

 (notice it is backwards compared to Kyriakos's)

7. Even though WA is an external object type, we do not have to create the required external relationship

8. Enter a time constraint for each relationship and inverse relationship (This was done earlier when I maintained subtypes - step 1). But it is wrong. I should have had a P objtype. 

 I deleted these and created generic * objtype rows, which allowed for both P & WA:

 

 This worked but the more accurate entries are the ones we did with Kyriakos's relationships:

 

 

Page 5: OM CUSTOM RELATIONSHIPS

9. I'm assuming that I need to Maintain Evaluation Paths also? 

 Yep! The "Check Organizational Management Customizing says "Maintain Evaluation Paths" & Environment Parameters Transaction PPSS, Display structures (evaluation path for work area org management) F1 (help) F9 (tech info) on Eval field:

SM30 for table T778A (evaluation paths) & press Customizing button:

10.Created Evaluation Path (wrong)

This caused a problem. P was within WA within P within WA,infinite loop! Corrected: 

 Evaluation Path for relationships created by Kyriakos (by the way, ignore eval

Page 6: OM CUSTOM RELATIONSHIPS

path text - SAP bug):

11. Specify Environment Parameter

 But something is missing. See step 8 - I corrected and created time constraint for Objtype P (actually *) 

Page 7: OM CUSTOM RELATIONSHIPS

 Finished product - Specified Env param using Kyriakos's eval path:

 Work area org managment link: