Financial Management Blog Posts by Members
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

Key Insights on Flow Builder Plus: Lessons Learned and Future Perspectives

Josemar-Mendes
Explorer
‎2025 Mar 04 7:45 AM
817

Key Insights on Flow Builder Plus: Lessons Learned and Future Perspectives

Introduction

I would like to share a recent experience with Flow Builder Plus. I participated in Brownfield Migration Projects where companies already had a consolidated cash management process using previous versions of the Liquidity Planner, along with customized reports that were incompatible with S/4HANA 2023.
The project involved detailed mapping of source flows, applying all available SAP Notes until the go-live date, and recovering business-consolidated rules and derivations to ensure the correct classification of cash flows. Additionally, we conducted workshops to define new indicators aligned with business needs.
It was a challenging yet rewarding experience that gave us the chance to explore the full potential of the tool, delivering a fully standard solution that's still evolving to meet the client's needs.

Project Scope

  • Migration to SAP S/4HANA 2023 and scope Advanced Cash Operations (J78_BR)
  • Review of cash flows from the old Liquidity Planner to Flow Builder Plus.
  • Mapping of derivation rules and application of SAP Notes.
  • Ensuring correct classification of cash flows with a 100% standard solution and defining new indicators and reports.

Resources Used

  • SAP Knowledge Base Articles (KBA) as the primary resource for research and troubleshooting.
  • Important Tip: SAP KBA offers solutions to many known Cash Management issues.
  • Highlighted Note: 3454172 - Central KBA for Flow Builder Plus (S/4 HANA Cash Management 2021), which centralizes fixes for various issues.

https://userapps.support.sap.com/sap/support/knowledge/en/3454172

Implementation Strategy

  • Activated the Business Function FIN_FSCM_CLM (Full Scope) to integrate liquidity hierarchy with the F2332 (Cash Flow Analyzer) and F0735 (Check Cash Flow Item) apps. (Ensure the client has the compatible license).

Josemar_mendes_0-1741051967463.png

  • Applied all available updates to FQM/CLM components, minimizing and restricting future issues.
  • Notable Notes: 3487144, 3359859, 3386510, 3390990, 3394746, 3397150, and many more addressing specific issues.
  • Adjusted configurations to ensure compatibility with Flow Builder Plus.

Reference: https://community.sap.com/t5/enterprise-resource-planning-blogs-by-sap/flow-builder-plus-benefits-ba...

  • Reviewed and validated all derivation criteria for liquidity items (FQLINFACC and Queries).

Steps

  1. Bank Account Management
    Some internal management bank accounts were handled via client-customized reports and lacked an Account ID in the system. For these accounts, we configured a Technical Bank using transaction FITE and the app F1366A (Manage Bank Accounts) to ensure the initial balance reflected the defined hierarchies.
  2. Bank Hierarchy Loading
    We loaded the defined bank hierarchy during the project through the Manage Global Hierarchies app - F4973.
  3. Liquidity Hierarchy Loading
    We loaded the defined liquidity hierarchy during the project through the Manage Global Hierarchies app - F4966.
  4. Master Data
    During the project, we identified inconsistencies in data related to the G/L account view (TCODE: FS00 or APP - F0731A).
  5. Rebuild Flow Types in Accounting Documents (BSEG)
    To display and load items in the FQM* tables, the flow type needed to be correctly established for the document items. We executed a full run of transaction TCODE: FQM_UPD_FLOW_TYPE.
  6. Insert Company Bank (BSEG)
    We performed a full load via transaction: FQM_UPD_HBK_HKT to ensure the correct Account ID was populated for document items.
  7. Treasury Level Update
    A treasury level update was performed. The transaction used was: FQM_FD_DPU.
  8. Initial Balance
    Defined the start date for "One Exposure" operations using the VFQM_ACT_STARTDT view, ensuring no "ACTUAL" records before 31/08/2024 were loaded into table FQM_FLOW. From this date onwards, only items created through transaction FQM_INTBAL_AUTOCRT were considered "ACTUAL" during the data process in Flow Builder 2.0.
    Josemar_mendes_1-1741051967464.png
  9. Rebuild Liquidity Items in Accounting Documents
    We updated the liquidity item with transaction: FQM_UPD_LITEM to ensure proper derivation of liquidity items along with relevant G/L lines.
    Josemar_mendes_2-1741051967467.png
  10. Flow Builder 2.0
    Finally, we ran the report: FCLM_FLOW_BUILDER_2 to load the records created post-go live and completed the process by activating the job delta triggered by the necessary events.


Conclusion
The goal of this blog was not to detail the step-by-step implementation but to highlight the key points for effective planning and avoiding data issues during the early stages of using the tool.

In future posts, I will detail how we worked on the composition of initial bank balances in conjunction with the liquidity hierarchy to present the medium-term cash forecast.

References

  • SAP Help Portal
  • SAP Knowledge Base Articles (KBAs)
  • SAP Community

 

 

Labels