Enterprise Resource Planning Blogs by Members
Gain new perspectives and knowledge about enterprise resource planning in blog posts from community members. Share your own comments and ERP insights today!
Showing results for 
Search instead for 
Did you mean: 
Former Member

One of my clients had the requirement to add a new custom relationship for their event catalog. Essentially they needed to link event types to each other for specialized reporting needs. They needed to show in the catalog that some event types were actually modules of other event types. So when creating an event, they wanted the option to link the event to another event. This would then allow them to later report at two levels - at the "module" level, and also rolled up statistics at the event level.

For example, there might be an event type called "Leadership Training". That event type actually consists of modules called "Leadership Training - Presentation Skills" and "Leadership Training - Financial Management". In some reports they need to show how many employees are scheduled to attend any of the "Leadership Training" modules (an aggregated value), while in other reports they need to show how many people attended the individual modules.

This post explains the process I followed to achieve what they were looking for...

Create Custom Relationship Type

This first step is to create a custom relationship. A common SAP standard relationship is the "A003" relationship - this denotes "belongs to". Conversely, the "B003" relationship denotes "incorporates". So in training and events, an event type (object type D) "belongs to" (A003) an event group (object type L). Conversely, the event group (object type L) "incorporates" (B003) the event type (object type D).

We want a relationship that denotes that an event type "is a module of" another event type (the "A" relationship). Conversely we can say that one event type "contains module" for another event type (the "B" relationship). To do this we need to create our own relationship in the customer namespace. Remember that the SAP namespace is 000-999 and the customer namespace is AAA-ZZZ. I decided to call our relationship "DMO", so when done we have the "ADMO" (is module of) relationship and the "BDMO" (contains module) relationship.

Follow these steps to get this done:

  1. Go to the IMG (transaction SPRO)
  2. Go to the menu path "Personnel Management->Personnel Development->Basic Settings->Maintain Relationships"
  3. Add a new relationship and fill in the technical code (DMO in this case), as well as the bottom up and top down relationship descriptions.
  4. Now select the newly created relationship and go to the "Allowed Relationships" settings - add two records here to allow the relationship between object type D (event type). This will control which objects can use this relationship. Since we only want to link event types, we will only be working with object type "D". You need to create the relationship in both directions - on for the "A" and one for the "B"...
  5. When done, you need to go to the "Time Constraints" settings, where you can set the behavior of your new relationships. I set both to "3" which means the relationship is very flexible without much limitation.

That's it - you have now created a new relationship which will work in transaction PP01. Go and give it a try - you will be able to create a relationship of ADMO or BDMO between two event types.

Configure Evaluation Path

Even though the relationship now exists and you can maintain these relationships in PP01, it still doesn't work in the Master Data Catalog (transaction OOC3). If you try to maintain the catalog here, there are two areas that show relationships - one is when you try to create a new relationship on an existing event type, and the other area is when you view the details of the event type under the "relationships" tab. Neither of these areas show our new relationship. There are two areas that need to be configured to get this working, and here I will explain the first area. We need to change the evaluation path "SCMCATAL". Here's how we do it:

  1. In the IMG (transaction SPRO), go to menu path "Personnel Management->Personnel Development->Basic Settings->Maintain Evaluation Paths"
  2. Find the "SCMCATAL" evaluation path and select it.
  3. Go to the "Evaluation path (individual)" settings. Here you must create a new record for our new relationship as below...

Once you have saved, you will see that in the Master Data Catalog you will be able to add a new "DMO" relationship, but you still won't see it under the "relationships" tab when viewing the event type details. Continue reading to put the last piece of the puzzle in place...

Configure Personnel Actions

The final missing piece is that the new relationship still won't show under the "relationships" tab when viewing an event type. In order for this to start working, we need to configure the personnel actions. Here's how we do it:

  1. In the IMG (transaction SPRO) go to menu path "Training and Event Management->Basic Settins->Dialog Control->Current Settings->Maintain Personnel Actions"
  2. Select action "D"
  3. Go to the "Actions (individual maintenance)" settings - select an existing 1001 action that you can copy (like A003)
  4. Select the "copy" button on the toolbar
  5. Change the copied record to include the ADMO relationship and for object type D.
  6. Make sure to scroll to the right to make sure that the Function Code is set to "INSE".

That's it! Now your new relationship should be fully functional in the Master Data Catalog.

See It In Action

Now you have configured all that you need to and your new relationship should be fully functional in the Master Data Catalog for Training and Event Management. Here's how to check if all is working:

  1. Go to the Master Data Catalog by using the SAP Easy Access Menu path "Human Resources->Training and Event Management->Settings->Current Settings->Master Data Catalog" or go to transaction OOC3
  2. Now find an event type that you want to create the new relationship for, and either go to Object->Create->Relationship, or click on "Relate" in context menu for the event type. When you do this, a popup window shows the possible relationships you can create - now you will see your new DMO relationship that you can add...
  3. After you have created the new relationship, if you expand the nodes for the event type, then the tree will show the new relationships with "is a module of":
  4. If you double click on the event type, and go to the "Relationships" tab, scroll to the bottom of the relationships and you will now see your new relationship shown. The same applies if you create a new event type, so you can create the relationship at the same time as creating the event type...
  5. If you have created a few of your new relationship links for the same event type, then the "glasses" icon will be show as in the screenshot above. When you click this button, it will show you all the relationships in a popup

As you can see, no modifications or enhancements are needed to get your own custom relationships working in Training and Event Management. Now you will be able to have reports developed based on these new relationships and get more value out of your analytics!

Have a look at my next post on Using a Vendor as the Event Organizer in Training and Event Management.

Let me know if this is useful to you or if you have any suggestions to improve on the solution.

Labels in this area