Skip to Content
Technical Articles

Writer function – ‘BW write type’: Planning Part 2

Part 2 ‘BW write type’ Planning – An Inside Story

 

Part 1 – ‘BW write type’ Planning of this blog series describes how to create simple planning writer functions and compare the 3 Model write types – Insert, Modify, Delete & Insert.

Writer function -> ACTIVATE:

Part 2 describes the list of the objects that are generated automatically in the background when activating the Planning writer function.

  1. DDIC table
  2. HANA stored procedure
  3. Infoprovider
  4. SAP Business Warehouse (SAP BW) objects – Aggregation level, Filter, Planning function and Planning sequence

Technical information of these objects can be found in the Runtime Attributes of the writer.

The below generated objects which are discussed earlier in the blog post Part 2 of the Loading writer remains relevant for the Planning ‘BW write type’ and are skipped here.

  1. DDIC table
  2. Stored procedure and
  3. Infoprovider

The objects that are specific for Planning ‘BW write type’ are discussed further.

SAP HANA PAK Procedure:

In addition to SAP HANA stored procedure, another PAK procedure is generated with tech. name suffix ‘_PAK’ which is used later in the planning function. These procedures can be accessed in SAP HANA studio under the NXI schema.

 

SAP Business Warehouse (SAP BW) objects

 

When the writer function is activated, it generates the SAP BW Planning objects necessary for writing data to ‘Model BW’ (ADSO) using SAP BW planning Engine.

  • Aggregation level
  • Filter
  • Planning function
  • Planning sequence
  • Process chain

SAP BW planning objects – Technical names:

Planning function technical name found in the runtime attributes can be used to derive other Planning objects technical names. For example, if planning function is YF1004636,

Aggregation level:      YA* (YA1004636)

Filter                   :        YSO* (YSO1004636)

Planning Sequence:    YS* (YS1004636)

 

TCode: RSPLAN

These planning objects can be accessed in the Tcode RSPLAN (both from SAP PaPM client and SAP BW client). To view specific planning objects, select the object type and enter the tech. name.

 

Aggregation level

By default, aggregation level is generated including all the fields/infoobjects of the Model BW(ADSO). Other planning objects such as Filter, planning function and planning sequence are generated on top of this aggregation level.

 

Filter

Default filter is generated with option ‘Standard’ and with no selections assigned.

 

Planning Function

It is generated with custom function type called as ‘Performance Management Planning Function Type’. This function type has the implementation of class /NXI/CL_P1_FW_PLFUNC_TYPE which executes the Y*_PAK stored procedure as per the Model writer type of the writer function.

 

Planning Sequence

Planning sequence is generated with aggregation level, filter & planning function of that writer.

This planning sequence can be executed outside of SAP PaPM client directly in the SAP BW reporting tools such as Analysis for Office, Lumira etc.

Maintain the Callback RFC destination: In the Environment -> Advanced

 

 

Process chain

Process chain is generated to automate & control the data from the Input function to ADSO. These Process chains can be accessed in the Tcode RSPC or RSPC1.

  1. Start process – This is included as first step to trigger the process chain
  2. Run FS-PER Function – This step executes the generated stored procedures which internally writes the data from Input function to the Output Model BW using SAP BW planning Engine.

 

Now you became familiar with

  • Generated SAP BW planning objects
  • Accessing these generated objects in SAP BW and SAP HANA Studio

In the Part 3, we will discuss how to troubleshoot the planning sequence, known issues and solutions

Good luck!

Be the first to leave a comment
You must be Logged on to comment or reply to a post.