- SAP Managed Tags
Let us talk about SAP PaPM UM and how a tailored finance app such as Profit Allocation can be created.
Customers requirements:
Customer would like to create finance app tailored for their business to capture and allocate profits between legal entities which:
- Integrates with my SAP DataSphere system
Data will be pulled from SAP DataSphere and further processed in SAP PaPM UM so the connection between them needs to be established. - Allows comfortable data input, ensuring data integrity and quality
Parent-childs relation will be built between models so that the data input for two tables can be done from one place to ensure consistency and quality. For more about relations refer to this blogpost. - Provides end-to-end traceability and auditability
It is important to know who did what at what point in time, and this is being logged in SAP PaPM Cloud UM in Event logs and allows complete traceability and supports auditability. - Incorporates workflow and periodic process support
In the created process user should be able to confirm some activities as a prerequisite of others and build a custom workflow for their process as it will be executed by activity users. On activity level user can set selections on Period field and ensure the execution is being done only for this certain period. - Provides a personal dashboard
After the process has been executed and results available it should be visualized with the possibility to completly customize the report dashboard. - Is compliant with SOC2 and ISO 27001
- Can be deployed worldwide
For more information on where the application can be deployed and which hyperscaler is available visit this link.
Chapter 1: Model Overview
Let’s jump into how to create this tailored finance app in SAP PaPM UM. As with any other model this one would also stary from the Modeling section of UM where the modeling of the application will take place.
After the Model has been built in an Environment we can visualize it in Manage Functions screen.
Once on the Manage Functions screen with Environment Filter the Diagram section is available where all of the functions in this specific Environment are represented via icons and how they are connected to each other with arrows.
In Profit Allocation application there are two Model Entities for Currencies and Companies master data.
Model Entity Documents is filled via SAP Datasphere replication flow.
Users can enter additional Document Items per Document with “Other Income” values.
Model View aggregates all “Other Income” values on Documents level. The result is the sender for allocation.
Users can enter ratios for distribution from company to target company. It is the receiver for allocation.
And lastly Model Allocation distributes all profits according to ratios between legal entities.
To visualize the flow better, let’s see an example.
- Documents Show Data link includes the parent child relationship between Documents and Document Items Model Entities created via Composition of many relation.
- Since Records for Documents are coming from Data Sphere Tax Free Income column is populated by replication from Datasphere.
- The other Income either from Donation or Subsidy can be created from the application.
- Information that is of interest is the total of all Other Income.To get this information Model View Document Aggregations is used and it is the Sender of the Model Allocation function.
- Receiver of the Model Allocation is Ratios Model Entity where Ratio is used as Distribution base.
The result of the allocation can be seen in the Show Data link od Allocate Profit Model Allocation. It is important to note that Value Adjustment was used so ‘no cent lost’ principle is followed, which can be seen in the first two records of the result.
Chapter 2: Process overview
After the modeling is done building the process is the next step. In the Process overview it will be shown how the periodic workflow process looks like. As a Process Manager the user needs to have appropriate roles assigned. If that is the case the user can see the Process section.
After clicking on Manage Process and find the created process for Profit Allocation it would lead us to this screen.
The Profit Allocation for 2023 will be done in this process. To see the diagram go to Show Process.
Once the link under Activity column in Activity links is clicked it leads to the specific Activity
There are some information on the Activity screen which is of interest.
Once the link below Reader team is clicked it leads to the Team screen assigned to it.
As a process manager Team screen is available. In Authorizations section a list of users who belong to the team can be found.
Chapter 3: Process activation and usage
Now that the process is built let’s see how to activate and use it and how activity users work with it after activation.
Still as a Process Manager clicking on Activate button will activate the first functions in the chain and in the Profit Allocation process it will be Manage Companies and Manage Ratios. Now in the Activity State of the Activity links Manage Companies and Manage Ratios will have the Active state.
Now Activity user can start working.
Relevant Activity Users receive notifications instantly even if they are working on a Report as shown below from which the Activity user can navigate to the Activity easily through notifications.
Once the Activity user is in the activity the user can notice the Scope for the year is set to 2023 on which the teams can operate. Clicking on Show data link will lead to the screen where records can be seen.
While on Show screen user can create, update or delete the data with the restictions on column Year, where for this one only value 2023 can be maintained.
Additionally user has a full traceability overview and can see who did what and when for the whole dataset or just on a record level. There is also a comment section where a comment can be set on activity level ot on record level.
Inside of a comment a csv file can be attached which can be imported to the activity via Import Data.
Lastly when the activity user is done with the importing of the ratios the activity can be confirmed. A comment can be left before confirming, which can be mandatory or not depending on the configuration made in the process itself.
Chapter 4: Key user extensibility
Another important topic is Key User Extensibility. It will answer the question of how the user can customize lists and pages.
Key user extensibility of the list can be done by clicking on the settings icon on the top right corner.
It will open up a popup where the user can add optional association to the list.
To add value from association to the list the checkbox of the desired field should be checked.
This is how to add the values to the entire dataset. This configuration needs to be saved in the Layouts so the next time the user opens the Show screen it will still remain. The other option is to add this value to the object page, or in other words to add it to the specific records too using AdaptUI functionality. To enter the object page simply click on the record.
Here option AdaptUI can be found in the User Profile by clicking on it.
Once in AdaptUI mode user can do a complete customization of the form.
Chapter 5: Dashboard
In this chapter you will learn how to set up personalized dashboards. This can be done in the outlined section of the application, Report section.
Once the report has been entered it looks like this. User can type text in this section, include images and other elements.
To add the Element follow the procedure:
Once Show Element is added it looks like this:
User can use other options in the tool bar and also add as many Show Elements as needed.
Once satisfied with the report user should click the Save button and the dashboard will be saved.
Chapter 6: Datasphere replication flow
To establish the datasphere replication flow follow the procedure from the blogpost linked above.
I hope this blogpost provided a wider picture on what SAP PaPM Cloud UM can do, and now that you know how to build a simple finance app, you can utilize it and create even more complex ones that fit your use case! Until next time 😊
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
