Enterprise Resource Planning Blogs by SAP
Get insights and updates about cloud ERP and RISE with SAP, SAP S/4HANA and SAP S/4HANA Cloud, and more enterprise management capabilities with SAP blog posts.
cancel
Showing results for 
Search instead for 
Did you mean: 
Hongjun_Qian
Product and Topic Expert
Product and Topic Expert
3,179
My previous posts for Flow Builder Plus:

Within this post, I would like to take a deep dive into the concept Classification of GL account and how it impact Flow Builder Plus from business perspectives.

 

Old Flow Builder, a.k.a. Flow Builder 1.0, using Debit/Credit to do the pairing when tracing through the document chain. The pairing logic applies on document as well as the clearing.
One typical example when performing pairing inside one document:



























Item G/L Account Debite/Credit Amount (Currency)
1 (cleared) Bank Clearing Account Debit 100 (EUR)
2 Bank Account Credit 20 (EUR)
3 Credit 80 (EUR)

 

With the Debit/Credit pairing, we have two sides:

  • Left (Debit) side. Include item 1.

  • Right (Credit) side. Include Item 2 and Item 3.


The left side and the right side are matched. Then pairing taken place to split the amount, and with respect to the fact only line 2 is Cash Relevant (line item 1 was cleared):

  • From Item 2 to Item 1, -20 EUR


Results into the flows part could be:

  • Flow with amount -20 EUR;


 

Flow Builder Plus chose a different way to choose the side. It is more like Liquidity Planner and it relies on the GL Account: the Classification of GL account.

There are pre-defined four sets of Classification of GL accounts:

  • Bank Account

  • Bank Clearing Account

  • Intermediate Info Account

  • Info Account


The Side of the document line item decided by the Classification of GL account, and the priority is from the top to bottom. The logic is as following:

  • If there are document line item which post to 'Bank Account',

    • If the summarization of amount large than 0, document items which posted to bank account and with a positive amount go to Left side, all others go to the Right side.

    • If the summarization of amount smaller than 0, document items which posted to bank account with a negative amount go to Right side, all others go to the Left side.



  • If there is no document line item to 'Bank Account', similar rule applies to 'Bank Clearing Account'.

  • If there is no document line item to 'Bank Account' or 'Bank Clearing Account', similar rule applies to 'Intermediate Info Account'

  • If there is no document line item to 'Bank Account' or 'Bank Clearing Account' or 'Intermediate Info Account', similar rule applies to 'Info Account',

  • If all rules above not working, then Debit/Credit policy applies.


Take the example above but adding Classification of GL account info:



























Item Classification of GL Debite/Credit Amount (Currency)
1 (cleared) Bank Clearing Account Debit 100 (EUR)
2 Bank Account Credit 20 (EUR)
3 Credit 80 (EUR)

 

Within Flow Builder Plus, we have two sides:

  • Left side. Including Line 1 and Line 3;

  • Right side. Line 2.


Flow Builder Plus choose the same splitting logic as old Flow Builder within the Pairing. But the differences of side picking will result in different result.

The Flow Builder Plus generate flows for the example document above as:

  • Flow with amount -100 EUR;

  • Flow with amount 80 EUR;


From the difference between old Flow Builder and Flow Builder Plus for the example above, the Flow Builder Plus provides the functionality to handle 'netting' case, including the Credit Memo case.

 

Besides the influence of Classifications of GL account in Pairing logic above, the Classification of GL will also impact the chain tracing. Normally the Info Account will stop the chain tracing because it reach the origin of the document chain tracing.

Though the Classification of GL account will be detected automatically from Flow Type concept in Accounting document, Flow Builder Plus provides much flexibilities via BADI to let customer control:

  • Classification of GL accounts;

  • Side picking;

  • Final decision whether stop the chain tracing


 
2 Comments