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...
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:
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.
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:
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...
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:
That's it! Now your new relationship should be fully functional in the Master Data Catalog.
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:
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
2 | |
2 | |
2 | |
2 | |
2 | |
2 | |
2 | |
2 | |
1 | |
1 |