Human Capital Management Blog Posts by Members
cancel
Showing results for 
Search instead for 
Did you mean: 
SumithaRD
Explorer
522

To overcome this issue HANA models can be built on Payroll posting tables as described in below steps:

  • It would be right to start this model from the posting table in Finance so the Finance team can use the same model to understand the actual postings into different GL accounts
  • Create a projection of BKPF table from Finance system the AWSYS = <HANA Fin Sys> and the BKTXT = ‘PP’ posted documents
  • Create a projection of the Document header table PPDHD from the HCM system
  • SumithaRD_0-1729665589448.png

     

    Join BKPF and PPDHD with join on

BKRF.BLART = PPDHD.BLART

BKPF.XBLNR = PPDHD.XBLNR

BKPF.BUKRS = PPDHD.BUKRS

BKPF.CPUDT = PPDHD.DOCNUM

  • Get the line items from PPDIT for the Document:

JOIN PPDHD with PPDIT with condition PPDHD.DOCNUM = PPDIT.DOCNUM

Fetch DOCLIN, HKONT, KOSTL, PRCTR with 1: n cardinality

SumithaRD_1-1729665589449.png

 

 

  • Fetch RUNID and LINUM from PPDIX table. Create projection on PPDIX with below condition

SumithaRD_2-1729665589452.png

 

JOIN PPDIT with above projection with condition on DOCNUM and DOCLIN and fetch the RUNID and LINUM

SumithaRD_3-1729665589453.png

 

  • Create projection on PPOIX with Sum on BETRG by PERNR, SEQNR

SumithaRD_4-1729665589456.png

 

 

SumithaRD_5-1729665589458.png

 

                        Get the sum of BETRG by PERNR SEQNR in aggregation

SumithaRD_6-1729665589461.png

 

 

  •    JOIN PPDIT output with PPOIX                                                                                                                               SumithaRD_7-1729665589463.png

     

                                                             

      

                                                                                                                                                             

  • To check reversals PPOPX - join RUNID TSLIN of PPOPX with RUNID LINUM from PPDIT                                                                                                                                                                                    

SumithaRD_8-1729665589464.png

 

                                                                                                                                                                                          

  • If record exists in PPOPX then again query back the posting lines reversed from PPOIX again join with PPOIX from Join to fetch RUNID                                                                                                     SumithaRD_9-1729665589466.png

     

                 SumithaRD_10-1729665589470.png

     

                                                               

                                                                                                                                                                                          

  • Filter condition on PPOIX_SID 

 

SumithaRD_11-1729665589470.png

 

                                                                                                                                                                                          

  • When ACTISIGN is P subtract the records else add the records                                                                                                                                                                                                        

SumithaRD_12-1729665589477.png

 

 

  • Now to fetch Org details join with Payroll cluster table WPBP with RUNID and SEQNR

SumithaRD_13-1729665589484.png

 

 

 

 

  • Join the PERNR Details with Org Infotype to fetch further details

SumithaRD_14-1729665589490.png

Now the model can be used to find the total spend across the employee groups and organizational objects. In the Semantics layer we do not include Employee level details as this report would be shared by the finance or reporting and analytics team