Query on SAP PaPM Y Tables

[vishalghag]

Hi Experts,

We are executing a join function in SAP PaPM and have noticed that all these functions are storing data in Y tables in the backend post execution. We would like to know if this is a temporary storage or a permanent one? Is this behaviour different for executable & sub-function?

Also what is the duration for which this data resides? Is there a way to delete this data permanently using a process activity and not through the 'Delete Data' option.

Regards,

Vishal

join1.png

join2.png

join3.png

[Rainier_Orduna]

Hi vishalghag

To begin with, almost all functions store data in Y tables. To give you an idea, if you select a function from your environment and click on the Function Attributes button (just to the right of the Edit button) and go to Runtime Attributes, the functions I am talking about (which includes Join, Allocation, View among others) all have their generated DDIC Table created and assigned when a function is activated.

When it comes to the question of behaviors, let us have the following scenarios.

Scenario 1:

• Model Table (source: Environment) which is an input function of View 1 (Executable)
• View 1 is an input function of the next function View 2 (Sub-Function)

When View 2 is executed, run of View will also be triggered since View 1 is Executable. This would in turn make these 2 functions have their generated Result Data which can be easily verified again from the Show button of each function and their respective data will in turn be stored in their corresponding Y-Tables. The same goes if you execute View 1 (Executable) first then execute View 2 (Sub-Function), each of these executions will render stored data and show the Result Data when displayed.

Scenario 2:

• Model Table (source: Environment) which is an input function of View 1 (Executable)
• View 1 (Executable) is an input function of the next function View 2 (Sub-Function)
• View 2 (Sub-Function) is an input function of the next function View 3 (Executable)

When View 3 is executed, View 3 and View 1 will have their individual generated Result Data as well as their corresponding data stored in their respective Y-tables. As for View 2, it will have neither of these - but to recap, View 2 (Sub-Function) is the input function of View 3. The next question would be how come View 3 was able to generate its Result Data? That is because View 2 has what we call its "buffered' results (instead of stored data in its Y-Table) derived from View 1. This is made possible by the generated stored procedure linking these 3 functions together along a process chain.

As for the duration, as long as you do not delete the function the stored data stays along with the Y-table. Deletion aside from the Delete Data option directly in the function itself is by way of transaction /NXI/P1_FW_DEL_TDATA. Related information is found in the Administration Guide - Operations Information via this link: https://help.sap.com/docs/SAP_PROFITABILITY_PERFORMANCE_MANAGEMENT/a8068ea2f9ba403aa6d8bda3abcdbecd/...

I hope this clarifies your concern.

Best regards,
Rainier