Outlining Basic Cash Operations (BFB)

Basic Cash Operations helps you to manage daily cash operations and provides general information of your current cash position and liquidity forecast. You can get a midterm liquidity forecast based on the projected incoming and outgoing payments and manually entered planning items.

Payment medium files can either be downloaded and sent to the banks manually or automatically sent to the banks via Multi-Bank Connectivity.  This scope item also supports handling bank statement manually or via Multi-Bank Connectivity.

In the SAP S/4HANA Cloud system, you can create memo records centrally for expected cash flows that are not yet generated in the system. The memo records are then displayed in the cash management apps, such as Cash Flow Analyzer and Check Cash Flow Items.

The master data of a memo record in SAP S/4HANA Cloud consists mainly of three parts.

The tile setup is made up from three main parts:

• Header Data
• General Data
• Additional Info

The Manage Memo Records app provides the functionality to create, delete, archive, or reactivate memo records centrally.

Using the app, you have the possibility to search for specific memo record items by utilizing the filter bar at the top. Furthermore, you can sort the search results according to your needs, or download the complete table.

Key features of the app are as follows:

• Display a list of memo records with active or inactive status
• Create memo records manually
• Create multiple memo records in one go by copying or distributing a memo record
• Convert the status between active and inactive
• Active memo records can be converted into archived records, which are then no longer displayed in cash management reports
• Delete memo records that are no longer valid. The deleted records are no longer displayed in cash management reports
• Auto expire memo records when the expiration date arrives
• Store the memo record data in One Exposure from Operations, which will be consumed in other cash management apps, such as Cash Flow Analyzer and Check Cash Flow Items

The memo record item screen holds detailed data about the memo record. Set the data as per your requirement in terms of amount, company code, value dates, or currency.

Depending on the type of memo record you are creating, there are certain mandatory fields required before you can activate the item.

The planning level is one of the mandatory fields of a new memo record to be created.

You use planning levels to reflect typical financial transactions.

• Levels with the source symbol BNK show transactions from bank accounts and bank clearing accounts to represent payment advice notes or planned items
• Levels with the source symbol PSK represent payment flows for planning purposes

You manage these planning levels in the Manage your Solutions app.

You can set an expiration date for memo records that need to be automatically expired.

In case you create a memo record for an outgoing payment, set the payment date as the expiration date. After this date, the memo record is automatically expired. The status is then changed from active to inactive.

Note

You cannot activate memo records that have already expired. If you do need to activate an expired memo record, you can change the expiration date to a future date and then you can activate the memo record.

Because the memo records are directly stored in One Exposure, other cash management apps, such as the Cash Flow Analyzer and Check Cash Flow Items, can consume the information generated in the Manage Memo Records app.

The information is displayed according to the previously set account and value date and is shown as cash flow in the Cash Flow Analyzer, for example. This ensures that all items are correctly reflected to make up your final balance.

Payment transactions in the USA are often made in the form of checks. In order to process these payments quickly, banks offer lockbox services where customers can send their payments directly to the bank (lockbox). The bank scans the checks and sends the check information in batches to the payee as a data file.

A lockbox is created with the lockbox number, destination, origin and valid customer invoices.

The upload file requires a specific BAI2 format. If the BAI2 format received from the issuing bank does not match the SAP BAI2 format, the file can not be processed.

For more information, see the Steps to Create the BAI2 File document, provided on the SAP Support Portal.

After having uploaded the Lockbox files you can schedule an Accounts Receivable Jobs for the automatic Lockbox Processing.

Note

Automatic Lockbox Reprocessing is optional because it requires you have implemented SAP Cash Applications, which requires a separate, additional license.

When implemented, automatic reprocessing is applied to certain business scenarios. Currently, Automatic Lockbox Reprocessing can only be used for Unprocessed or Posted on acct business scenarios.

Lockbox processing creates payment advices for any payment that can not be applied fully. These payment advices are stored and post processing uses these advices to correctly make payments to the customer. Use this process for Unprocessed, Posted on Acct, or Part. applied business scenarios.

Lockbox processing has been performed and lockbox data exists to be reprocessed. There are three scenarios requiring reprocessing of incoming checks:

• Scenario 1: Unprocessed - Neither the customer account nor the invoice could be found in the system. Create a new file with an incorrect invoice number and an incorrect customer number (MICR number).
• Scenario 2: Posted on acct. - The customer account was found but not the invoice. Create a new file with the correct customer number (MICR number) and the incorrect invoice number.
• Scenario 3: Part. Applied - The customer was found but one invoice was correct and the other was incorrect. Create a new file with the correct customer (MICR number) and one with the correct invoice number, and another with an incorrect invoice number.

Run the Upload Lockbox Files (FLB2) app to execute the step. Depending on which of the three scenarios applies, the Items list and Log gives you additional details that let you compare to the information available in the Lockbox: process checks view.

The Bank Statement Processing consists mainly of three parts. There are the statement formats which need to be considered when importing information to the SAP S/4HANA Cloud applications. For the import itself, there are mainly three options available in the Basic Cash Operations scope item.

After the import, there is the possibility to monitor all of the imported information and in case reprocessing is needed this is also highly integrated.

Use the interactive graphic to learn more about the different bank statement formats around the globe.

With the implementation of the SEPA not only the outgoing payments were standardized but new file formats also for the electronic bank statement have been introduced.

New bank statement formats, mainly introduced along with the SEPA implementation are as follows:

• CAMT.052 Bank to Customer Account Report
• CAMT.053 Bank to Customer Statement
• CAMT.054 Bank to Customer Debit Credit Notification
• A comparison between the SWIFT message and the XML based provided by the European Payments Council standard is shown on the slide.

The section describes how to handle the bank statement in SAP S/4HANA Cloud applications. There are three means to import Bank Statements to SAP S/4HANA Cloud:

1. Import electronic bank statement file using SAP Multi-Bank Connectivity (MBC).
2. If the system is connected to SAP Multi-Bank Connectivity (MBC), the electronic bank statement file provided by bank is stored in an SFTP folder, MBC retrieves the electronic bank statement file from SFTP, and then does validation and mapping. This process integrates with the scope item Bank Integration with SAP Multi-Bank Connectivity (16R).
3. For banks with a Multi-Bank Connectivity (MBC) connection, bank statements are handled by MBC. MBC maps from the local bank statement format to an ISO CAMT.053 format, and SAP S/4HANA Cloud pulls the ISO CAMT.053 bank statement from MBC and imports it automatically. The SAP S/4HANA Cloud software schedules a background job every 10 minutes to retrieve the bank statement file from MBC, and the file is automatically imported into the SAP S/4HANA Cloud system.

After the CAMT.053 bank statement is pulled from Multi-Bank Connectivity (MBC), the postings in bank accounting and subledger accounting are be performed. Since MBC maps the local bank statement formats to a CAMT.053 format, there is only one set of posting rules for the electronic bank statement.

When importing bank statements to SAP S/4HANA Cloud, several programs are used to read out statement information, to interpret this information, and finally come to a conclusion on how to post the interpreted data.

Fundamentally, the steps are similar for the bank statement import via SAP Multi-Bank Connectivity and the electronic bank statement version. Depending on the import method of the manual process there could be a difference in the interpretation and posting logic.

At this point in time, the electronic bank statement reaches SAP S/4HANA Cloud, the note to payee information is analyzed. Here the customer would normally provide some kind of reference information about the invoice, customer number, and so on. In the system configuration, the interpretation algorithm is defined. Based on that, the system uses no algorithm a standard algorithm or, for example, the document number to assign the note to payee information to internal business partner related transactions.

If the system is able to find a match - for example, based on the document number provided in the bank statement - it performs the subledger accounting posting and thereby clears the open item of the business partner. If there is no match possible the reprocessing of items is needed.

You can use the app Manage Bank Statements to manage manual and electronic bank statements. The app provides an overview of all bank statements for all house bank accounts. You can also view detailed information for each bank statement.

Set the filter value to electronic bank statement items to see all the automatically imported statement items. Search for bank statements using search criteria, such as house bank account, bank statement date, bank statement status, and bank statement number. From the app, you also see the details of a bank statement such as line items, dates and processing status.

From the app Manage Bank Statements, it is also feasible to delete a bank statement. However, only bank statements in status Received, Saved, or Aborted can be deleted. An already completed item can not be deleted from the system anymore. In such a case, you need to reverse the transaction.

By contrast, a Saved item is not yet posted to the database. Since there is no document flow associated this statement, it can be deleted.

You can reverse imported, or manually created, bank statements in SAP S/4HANA Cloud applications. In order to do this, go to the app Manage Bank Statements. Pick the item to be reversed to see the details of the transaction.

After clicking the Reverse button you are prompted for the reversal reason and the posting date. After the confirmation, you can see from the reversal log which bankledger and subledger items are reversed, meaning the clearing of the open item is taken back and the posting on the bank account as well. After that you might want to check the statement content and re-import the statement or clear the items manually.

Import electronic bank statement file manually.

You get the electronic bank statement file from bank, and import it into SAP S/4HANA Cloud applications manually. This process integrates with the scope item Bank Integration with File Interface (1EG).

If there is no connection to the SAP Multi-Bank Connectivity you have the option to import this electronic bank statement file in SAP S/4HANA Cloud system manually. This procedure can be used for different files formats, for example, the BAI formats in the United States or the more general CAMT.053 format.

In the case of the manual upload of electronic bank statements to the SAP S/4HANA Cloud system several programs are used to read out statement information, to interpret this information and finally come to a conclusion on how to post the interpreted data.

The app Manage Incoming Payment Files facilitates the manual upload of electronic bank statements. Here again, the note to payee information plays a vital role in the matching of bank statement items to transactions in the system. The customer would normally provide some kind of reference information about the invoice, customer number, and so on. In the system configuration, the interpretation algorithm is defined per external transaction type. Based on that, the system uses no algorithm, a standard algorithm, or for example, the document number to assign the note to payee information to internal business partner related transactions.

If the system is able to find a match, for example, based on the document number provided in the bank statement, it performs the subledger accounting posting and thereby clears the open item of the business partner. If there is no match possible, the reprocessing of items is needed.

The app Manage Incoming Payment Files facilitates the manual import of bank statements and lockbox batches using electronic payment files. For the import of bank statements you can select from a wide array of formats, for example, the Bank Administration Institute (BAI) in the US, MT940 Germany, CAMT.053.001.02, and a number of further country-specific formats.

After the bank statements and lockbox batches are imported and posted, you will find them in the overview table of the app Manage Incoming Payment Files. Apply the filter criteria you need to find and track the items for which you are responsible.

In case you want to follow up on the statement items, you can use the Manage Bank Statements and Manage Lockbox Batches apps.

The app, Manage Incoming Payment Files, provides the option to directly reprocess files containing records that previously failed to be imported. There could be, for example, a missing account in the system. As shown in the previous figure, the system is unable to match the statement against any account. You need to create the account in the SAP S/4HANA Cloud application first. After resolving the problems that caused the original import failure, the files can be reprocessed.

In addition, you must mark files as obsolete if they contain records that failed to be imported and must be disregarded.

Create a manual bank statement. To manually enter a bank statement into the SAP S/4HANA Cloud system, use the app Manage Bank Statements. There are two options on how to key in the data:

1. Use manual transactions to create a manual bank statement.
2. Use external transactions to create a manual bank statement.

In the case of the manual input of bank statement information to the SAP S/4HANA Cloud application, the manually entered in the memo line or the customer reference information field is used for the interpretation on how to post the bank statement data.

The app Manage Bank Statements offers two possibilities on how to enter data from the statement - either with Payment Transaction Type Group or without as manual transaction. If the Payment Transaction Type Group is used and the external transaction types indicate which logical business transaction is associated with the entered item the system behavior is much the same as with the upload of the electronic bank statement. The note to payee information plays a vital role in the matching of bank statement items to transactions in the system. The customer would normally provide some kind of reference information about the invoice, customer number, and so on. In the system configuration the interpretation algorithm is defined per external transaction type. Based on that, the system uses no algorithm a standard algorithm or, for example, the document number to assign the note to payee information to internal business partner related transactions.

If the system is able to find a match, for example, based on the document number provided in the bank statement, it performs the subledger accounting posting and thereby clear the open item of the business partner. If there is no match possible the reprocessing of items is needed.

In case no Payment Transaction Type Group is used at entering bank statement information the posting rule is not derived from the external business transaction code but directly selected by the statement processor. Still, the interpretation and posting logic in the bank ledger and subledger remains the same.

For manual transaction, just leave the Payment Transaction Type Group blank. No external transaction can be used in this type of bank statement. If you are clearing open items with the bank statement go to the detail screen of the line item and enter the customer reference number.

When you maintain a Payment Transaction Type Group - for example, MT940, you can use the external transactions configured in the system later. You can not use any manual transaction in such a bank statement.

In the manual bank statement processing, you work with a two-step approach to complete the task. When you enter the transaction details, you are saving this information in the system. At this point in time, no posting on any account has happened yet. Due to this fact, such items are open for further processing or can even be deleted.

The second step is to post these transactions to the system. Consequently, the general ledger postings are done and the open items for the customer or vendor are cleared. At this point, the statement cannot be deleted anymore and only the reversal of the created postings is possible.

There are basically two apps, which help you to manage and monitor the bank statements for the end-of-day process. It is the Manage Bank Statements which lists all the uploaded statements to the system with its line item details.

There is also the app, Monitor Bank Statements, which gives are broader view of the current bank statements in SAP S/4HANA Cloud.

Next to these two apps, there is also the app called Bank Statement Monitor - Intraday. This is specifically designed to monitor the import status of intraday bank statements for the bank accounts that have been selected. The Intraday statement processing is nevertheless only available with the scope item J78 - Advanced Cash Operations.

You can use the app, Bank Statement Monitor, to monitor the import status of end-of-day bank statements for all the bank accounts that have been selected for monitoring. This app provides you with an overall status of the monitored bank accounts and also allows you to identify bank accounts with statement import errors. When this is done, you can communicate the issue to the responsible person using emails directly from this app.

There are plenty of options in the Bank Statement Monitor that clarify the display of data and sort the information available. The color coding gives you a crisp idea of the import status for the bank statements. This information can be grouped in several different ways - for example, by Bank and Company, by Country, and so on.

Toggle between the chart view and a table view for a different perspective on the numbers.

The Bank Statement Monitor also acts as a hub for further processing on bank statement items. From the app you can navigate, for example, to the Cash Flow Analyzer or the Manage Bank Statements app.

This features ensures efficient processing of bank statements throughout the value chain.

You are importing bank statements to your system, especially for incoming customer payments, you want a high automation rate for the open item clearing. This can be achieved in three ways.

1. There is either the standard interpretation algorithm, which reads the external note to payee information and searches for this info in the system to find a match.
2. In a case where there are regular incoming payments where a dedicated rule can be applied (for example, monthly rent payments), you can create a reprocessing rule directly in the application. The Manage Bank Statement Reprocessing Rules app facilitates this process.
3. The third option is to enrich and enhance this process with the SAP Cash Application (1MV). Machine learning is helping with the matching and is clearing items automatically or is making proposal what the best match would be.

If there is still no match found between an item in the bank statement and an open item in the system manual reprocessing is needed.

A good point to start the reprocessing of bank statement items is the Manage Bank Statements app. You get a first impression on the bank statements status and can decide to follow up with these items.

You take this information to use in the Reprocess Bank Statement Items app where you actually reprocess the statement items that were not matched automatically by the system.

Just to be sure, the Intraday Bank Statement processing and reprocessing is not part of the scope item BFB - Basic Cash Operations. It can only be used with the Advanced Version of item J78.

SAP Cash Application is a cloud-based solution that leverages machine learning technology to provide matching prediction result based on historical data.

The solution intends to improve the cash application process by automating the labor-intense activity of clearing incoming bank payments with corresponding receivable invoices with the help of he SAP Cash Application Solution.

In SAP S/4HANA, the integration process can be scheduled to extract historical data and replicate to the Machine Learning Platform as machine training data. Afterwards, it can be scheduled to extract open receivable items and replicate to the Machine Learning Platform for scoring. The prediction result from Machine Learning is proposed when the customer reprocesses the bank statement items.

Using SAP Leonardo Machine Learning capabilities, the matching engine learns from accountants' past manual actions, capturing much richer detail of customer- and country-specific behavior, without the costs of manually defining detailed rules.

The Bank Statement Reprocessing Rules app helps you to create and manage bank statement reprocessing rules. This allows you to automate the reprocessing of bank statement items, which enables you to spend more time on critical tasks.

You can use this app to do the following:

• Create new bank statement reprocessing rules.
• Define conditions and actions for the reprocessing rules.
• Select open bank statement items by reprocessing rule.
• Check for which open bank statement items to which the rules applies.
• Select bank statement items that should be handled with the reprocessing rule.
• Apply the reprocessing rule to the selected bank statement items.

Every time a new statement is imported and an item does fulfill the rule criteria, it is routed through this procedure and posted accordingly. This ways the automatic matching and posting rate is greatly increased.

In the example, we are setting the condition for all statements of company code 1010, that run with a memo line that contains the word RENT and external business transaction code 153. In that case, the account 63005000 and cost center 10101302 should be posted.

If no match is found between the incoming payment and systems internal information, the Cash Specialist is needed to perform a manual reprocessing. You can use the Reprocess Bank Statement Items app to reprocess bank statement information that were not processed automatically. In this app, you can reprocess a bank statement item, mark it as reprocessed, and enter a reason for reprocessing. You can also add attachments to bank statement items.

From the overall bank statement list it is possible to directly assign a reprocessing rule for a certain set of items. In order to do so select the statement items and choose Apply Rule. On the prompt, you find the already created rules from the Manage Bank Statement Reprocessing Rules app.

In order to administer statement items, use Reprocess on the overview page. You are directed to the item details. From here you have several options on how to process and post the statement item.

At the top of the screen, the general bank statement information displays. That is the company code, house bank or external transaction, for example. The details below contain all the information that is available from the individual item.

The Account Type describes mainly the object you are trying to post this item against. If you are clearing an customer open item with a line item select this option here for a more streamlined process also the customer number.

The reprocessing reason holds information that shows the reason why you are working on this item. For example, this can be missing configuration, missing master data, or tolerance limits.

A menu bar in the lower part of the screen provides you with the posting options. You can either post the item against AP/AR items, post it on account, or against a G/L item. You are also able to add attachments or to see already created documents, probably that the bank ledger in case of an incoming payment.

The figure, Allocating Accounts Receivables Items, shows a possible allocation of an incoming payment. Let us assume that our customer has payed 1345€, as shown on the top, but did not specify which items to be paid via an payment advice. Providing the customer number as the account type, the cash specialist is able to obtain all the open items of that account. The specialist is now able to manually assign the items by moving them to the Items to be cleared area.

Posting the entries will clear the open items and complete the reprocessing for this bank statement item.

If no open items are found or the amount paid is too low the accounting clerk or cash specialist is also able to directly create a dispute case from the app.

To bring the payment processing of the Basic Cash Operation into a broader context, the complete purchase-to pay-process is shown in the following figure.

The figure focuses on the integration between the Best Practice Scope items from several areas - for example, with the item J45 - Procurement of Direct Materials the purchase process is started. A seamless integration is incorporated and ensures a stable and efficient process including all steps from the initial creation of a purchase requisition to the invoice creation and handling. That process is covered with J60 - Accounts Payable.

In the scope item BFB - Basic Cash Operations, we have a closer look at the payments and payment integration. In SAP S/4HANA Cloud, there are two scope items linked to the BFB - Cash Operations. This is Bank Integration with File Interface (1EG) and Bank Integration with SAP Multi-Bank Connectivity (16R).

Looking into more detail at the payment section of the overall process we can distinguish two forms for the outgoing payments.

1) There is the highly integrated and automated SAP Multi-Bank Connectivity. SAP Multi-Bank Connectivity is an on-demand solution that connects financial institutions and other financial service providers with their corporate customers on a secure network owned and managed by SAP.

SAP Multi-Bank Connectivity is based on integration services deployed in the SAP Cloud that enable the integration of business processes spanning different departments, organizations, or companies.

2) On the other hand there is file download option. Here you download the payment files for outgoing payments, which have been generated by SAP S/4HANA Cloud applications, to your computer. You can then upload these payment files to your banking portal or treasury workstation for payment processing.

These payment scenarios are not directly covered with the BFB - Basic Cash Operations scope item. The SAP Multi-Bank Connectivity (MBC) connectivity and the specific integration setup needed for that is covered with the item Bank Integration with SAP Multi-Bank Connectivity (16R). The handle the file download please refer to the Bank Integration with File Interface (1EG) Best Practice Scope item.

SAP establishes connections with your banks to automatically send payment instructions, receive status notifications, receive bank statements, and receive lockbox messages with SAP Multi-Bank Connectivity (MBC). Leveraging the monitoring capabilities, you can supervise the status of all payment instructions and see which bank statements are received and which expected bank statements are still missing. The monitoring is only available in combination with Advanced Cash Operations (J78).

Connectivity between your financial system and banking institutions is essential for daily financial operations. However, when you deal with a multitude of banks using different standards to exchange information, establishing and maintaining proprietary connections becomes complex and time-consuming. With the SAP Multi-Bank Connectivity solution, featuring native integration to the SWIFT network, you have a single point of connection to all the banks you use.

The solution is comprised of two elements. The first is your digital core, SAP S/4HANA Cloud, where a payment is triggered. This is where you manage your bank account, manage your payment with approval workflows, monitor the payment end-to-end, and can detect fraud. Fully integrated to it, SAP Multi-Bank Connectivity provides additional messaging management and transaction routing capabilities using the highest security standards. The connection between the two is based on web services. Thanks to the global reach of the SWIFT network, via Alliance Lite connectivity, you can connect with over 11,000 financial institutions. And as onboarding new banks is simplified and accelerated, you can choose the banks that meet your changing needs, without being held back by lengthy integration processes.

For the bank integration with file interface the following process steps will be run through in principal at the outbound sector:

1. Business partner payables or receivables are posted in the system.
2. These payable or receivables items will be cleared using the Manage Automatic Payments functionality in SAP Fiori. According to the payment method and the assigned Payment Medium Format the Payment Medium Workbench is creating the Payment Medium file.
3. This Payment Medium file can now either be saved on the SAP file system or is directly downloaded to the local computer for further processing.
4. The actual file transfer from the local computer to the external bank can be achieved through various means. This could be done via file transfer, online banking
5. The external bank is accepting the payment medium and is processing the payments contained.

The Cash Flow Analyzer app is the central entity to analyze cash flows over days, weeks, months, quarters, or years for all bank accounts and liquidity items.

Using the Cash Flow Analyzer, you can monitor the cash position, liquidity forecast in your company, and analyze the details with the following advantages:

• Various dimensions and filters
• Hierarchical structures for Bank Account Group and Liquidity Item with amounts for a specific time period
• Currency comparison between Display currency and Transaction currency (or Account currency)
• Integrate dynamic data sources from memo records, payment orders, payment requests and some of the source applications that are stored in One Exposure from Operations
• Switch between the balance view and delta (cash flows only) view

Finally, the Cash Flow Analyzer gives you a combination of "Cash Position Details", "Liquidity Forecast Detail," and "Actual Cash Flow" functions.

The Cash Flow Analyzer app comes with three predefined variants. Since the Cash Flow Analyzer app is providing functionality in terms of the Cash Position Details, Liquidity Forecast, and the Actual Cash Flow for all of these scenarios a variant is shipped.

These variants in the Cash Flow Analyzer enable you to display the cash position, liquidity forecast and actual cash flows with more organizational units, in addition to the company code. These are as follows:

• Business Area
• Segment
• Profit Center
• Trading Partner

A different set of information is presented depending on which certainty level is set in the Cash Flow Analyzer app.

The Certainty Level describes the reliability and therefore the likelihood of a flow in One Exposure. The certainty level "ACTUAL" is the most reliable one and is used to represent a fact, this means an event that has actually happened.

Good examples for actual cash flows that happened would be Accounting Line Items from Bank Statements or Accounting Line Items with G/L Accounts representing cash.

If the variant Actual Cash Flows is picked only this sub-set of information is considered for the output.

The Cash Position Details variant contains the certainty levels that make up the Cash Position of the day. These include Actual Cash Flows, Self-initiated Cash in Transit or values from Distributed Cash Management. Picking the Cash Position variant all of the required certainty levels required are already pre-set.

If the certainty level field is blank this means that the Liquidity Forecast is output. All of the information from the different sources, for example, Finance, Material Management, or Sales or taken into account when calculating the Liquidity Forecast.

One Exposure collects information from various source applications. It mainly collects information related to the future. The purpose of storing historic data (meaning flows with certainty level ACTUAL) is to have a basis for extrapolating the future; for this purpose, only data with coarse granularity from the last 1 - 2 years is needed.

The Aggregate Flows (FQM_AGGREGATE_FLOWS) app serves a data privacy protection purpose. To simplify the blocking and deletion of personal data, you can delete flows in One Exposure from Operations. You can delete flows with ACTUAL certainty level in One Exposure and substitute them with aggregation flows that do not contain any person-related information. In addition, you can also physically delete all flows that are marked as deleted (FQM_FLOW-DELETED ='X'). As a result, the data volume in One Exposure is further reduced.

The system creates the aggregation flows for the transaction date given on the selection screen. They do not contain any person-related information; this means the following fields are empty in the aggregation flows:

• PARTNER
• CUSTOMER
• VENDOR
• MATERIAL
• PROJECT
• PROFIT CENTER

The Schedule Cash Management Jobs app helps you to run the health checks of data that are consumed by cash management applications. You can then get a list of logs that shows the validation result of the configuration data, master data, and transaction data.

The Schedule Cash Management Jobs (F3030) app can be used to schedule applications jobs based on the job template. For Cash Management, several check-points are enabled in this application, including the following:

• Check Point 1: Planning level and group checks in configurations
• Check Point 2: Planning level and group checks in master data
• Check Point 3: Bank account checks in One Exposure
• Check Point 4: Bank account checks in G/L accounts
• Check Point 5: Bank account checks in bank statements