Professional Documents
Culture Documents
PUBLIC
Table of Contents
1 Purpose
2 Prerequisites
2.1 System Access
2.2 Roles
2.3 Master Data, Organizational Data, and Other Data
2.4 Preliminary Steps
2.4.1 G/L Account Created for Bank Account
2.4.2 Basic Settings
2.4.3 Define Account Type (Optional)
2.4.4 Change Message Control (Optional)
2.4.5 Create Business Partners for Bank Account Management
2.4.6 Manage Field Status Groups for Bank Account Master Data (Optional)
2.4.7 Define Settings for Bank Statements
2.4.8 Define Bank Account Settings - Bank Statements
3 Overview Table
4 Test Procedures
4.1 Bank Account Master Data Processing with Basic Bank Account Management
4.1.1 Using Direct Revision Activate
4.1.1.1 Create Bank Account
4.1.1.1.1 Open Bank Account
4.1.1.1.2 Create Bank Master Data
4.1.1.1.3 Edit Bank Master Data
4.1.1.1.4 Create Bank G/L Account
4.1.1.1.5 Manage Banks Cash Management Data
4.1.1.1.6 Create Bank Account
4.1.1.1.7 Export Bank Accounts
4.1.1.1.8 Import Bank Accounts
4.1.1.2 Change Bank Account
4.1.1.2.1 Notify Bank to Change
4.1.1.2.2 Update Bank G/L Account
4.1.1.2.3 Change Bank Account
4.1.1.3 Close Bank Account and Cancel Closing
4.1.1.3.1 Notify Bank to Close Account
4.1.1.3.2 Close Bank Account and Cancel Closing
4.1.1.4 Delete Bank Account (Optional)
4.1.2 Import Bank Data
4.1.3 Fields Enhancement for Bank Account Master Data
4.2 Maintain Bank Chain
4.2.1 Create Bank Chain
4.2.2 Change Bank Chain
4.2.3 Delete Bank Chain
4.2.4 Check Bank Chain Information In Business Partner (Optional)
4.2.5 Schedule Delete Bank Chain Jobs
5 Appendix
5.1 Remove Inconsistent Data after Closing a Bank Account (Optional)
5.2 GL Account Reduction (Optional)
Overview
With Basic Bank Account Management, cash managers and bank accountants can centralize the management of bank accounts using bank account master data, using a table view of banks and bank
accounts.
Bank account master processing includes:
• Creating a bank account
• Changing a bank account
• Closing an obsolete bank account
• Reopening a closed bank account
This document provides a detailed procedure for testing this scope item after solution activation, reflecting the predefined scope of the solution. Each process step, report, or item is covered in its
own section, providing the system interactions (test steps) in a table view. Steps that are not in scope of the process but are needed for testing are marked accordingly. Project-specific steps must be
added.
Note Values in this test script (decimal notation, date formats, and so on) are presented in U.S. standard notation. If your test system is set up to use a different notation, enter values as appropri-
ate.
This section summarizes all the prerequisites for conducting the test in terms of systems, users, master data, organizational data, other test data and business conditions.
System Details
System Accessible via SAP Fiori launchpad. Your system administrator provides you with the URL to access the various apps assigned to your role.
2.2 Roles
Create business roles using the following business role templates delivered by SAP and assign them to your individual test users.
Alternatively, if available, you can use the following spaces delivered by SAP. You create a space with pages containing predefined essential apps and assign it to the business role. You then assign
this business role to your individual users.
For more information, refer to How to Create a Business Role from a Template in the product assistance for SAP S/4HANA Cloud.
Name (Role ID (Role Template) Name (Launchpad Space) ID (Launchpad Space) Log
Template) On
Configuration SAP_BR_BPC_EXPERT Business Process Configuration / Business Configuration - Feature Manage- SAP_BR_BPC_EXPERT / SAP_CA_SPT_BPC_FM_PC /
Expert ment / Business Process Configuration - Workflow / Manage your SAP_CA_SPT_BPC_WORKFLOW_PC / SAP_CA_SPT_IC_LND_BASE_PC /
Solution / Business Process Configuration - Extensibility Explorer / Busi- SAP_EI_SPT_BPC_EXT_PC / SAP_FIN_SPT_BPC_EXPERT_PC /
ness Process Configuration - Finance / Business Process Configuration - SAP_MM_SPT_BIZ_PROC_CONFIGN_PC / SAP_TM_SPT_TRANSPCFG_PC
Procurement / Business Configuration - Transportation
Note During testing, cash management specialist and configuration expert can share the same user ID, but cash manager and cash management specialist must be separate user IDs due to segre-
gation of duty: cash management specialist creates the change request, cash manager approves it, the creator could not be the approver.
Caution The following Sample Values assume that you are only implementing one of the four Basic Account Master Data Procedures described in the Preliminary Steps [page ] 6 section. If
you are implementing and testing more than one, especially in a single environment, you cannot use the same Master Data values for more than one procedure type. You must create additional
Master Data values, such as bank account numbers, bank keys, and so on, and then use these different values in each procedure type.
For more information on creating these master data objects, see the following Master Data Scripts (MDS)
Table 1: Master Data Script Reference
Master Data Script ID Description
Caution Instructions provided assume that you are only implementing one of the four Bank Account Master Data Procedures described in the Purpose [page ] 3 section. If you are implement-
ing and testing more than one procedure, especially in a single environment, you cannot use the same Master Data values for more than one procedure type. You must have additional Master
Data values created, for example G/L account numbers, bank keys, and so on, and then use these different values in each procedure.
Test Administration
Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>
Context
Within this Basic Bank Account Management scope item, the following Bank Account Master Data Procedure is documented:
Bank Account Master Data Processing with Basic Cash Management and Direct Revision Activate
If Full Cash Management has been configured, you can follow below procedures:
● Bank Account Master Data Processing with Full Cash Management and Direct Revision Activate
● Bank Account Master Data Processing with Full Cash Management and Dual Control Revision Activate
● Bank Account Master Data Processing with Full Cash Management and Two-Person Revision Activate
● Bank Account Master Data Processing with Full Cash Management and Workflow Revision Activate
In this preliminary step, you choose which one of these four Bank Account Master Data Processing Procedures to use for your implementation:
1. To use , use the following settings:
• Cash Management Scope = 01
• Basic Scope & Bank Account Revision = 01 Activate Directly
2. To use , use the following settings:
Procedure
Depending on your configuration environment for SAP S/4HANA Cloud, choose one of the following options:
Configure Your Solution:
Test Step Test Step Name Instruction Expected Result Pass / Fail / Com-
# ment
1 Log on Log on to the SAP Fiori launchpad as a Configuration Expert - Business Process Configuration.
2 Access the SAP Fiori Open Manage Your Solution(F1241). The Basic Settings screen dis-
app Open Configure Your Solution. plays.
Note If the client is maintained as a customer system, the Basic Settings app is available; otherwise, the app is not available.
3 Define Basic Settings Verify your choices for Cash Management Scope and Bank Account Revision for your implementation based on the previously de-
scribed procedures.
1 Log on Log on to the project experience in SAP Central Business Configuration. The SAP Fiori launchpad
displays.
2 Open General Settings for In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To locate the activity in the tree view, The Basic Settings screen
Cash Management search for the following activity: General Settings for Cash Management. displays.
Choose Open Documentation for the found line item to see more details about this configuration activity.
Choose the link to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP Fiori launchpad as a Configuration Ex-
pert - Business Process Configuration.
3 General Settings for Cash Verify your choices for Cash Management Scope and Bank Account Revision for your implementation based on the previously de-
Management scribed procedures.
The check box Enable Snapshot is used for the snapshot of historic cash report. This check box can only be selected and saved when cash value is Full Scope. If the value of cash scope is Basic
Scope, it can’t be saved once the check box of Enable Snapshot is selected. Once the check box of Enable Snapshot is selected and saved, the function of snapshot of historic cash report is activated.
Remember Basic Settings must be reviewed following any system upgrade or improvement before continuing any business operation in the system. When differences are found from previous ac-
tivations, you must correct in the SSCUI Define Basic Settings.
Purpose
Depending on your configuration environment for SAP S/4HANA Cloud, choose one of the following options:
Configure Your Solution:
Test Step Test Step Name Instruction Expected Result Pass / Fail / Com-
# ment
1 Log On Log on to the SAP Fiori launchpad as a Configuration Expert - Business Process Configura- The SAP Fiori launchpad is displayed.
tion.
2 Access the SAP Fiori App Open Manage Your Solution (F1241). The Change View "Account Type Definition": Overview
Choose Configure Your Solution. screen is displayed.
Search for and choose Define Settings for Bank Account Master Data or SSCUI ID 102336
on the search filter.
Choose Configure for the Define Settings for Bank Account Master Data Step Name.
1 Log On Log on to the project experience in SAP Central Business Configuration. The SAP Fiori launchpad displays.
2 Open Define Settings for Bank In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To locate the activity in the The Define Settings for Bank Account
Account Master Data tree view, search for the following activity: Define Settings for Bank Account Master Data. Master Data screen is displayed.
Choose Open Documentation for the found line item to see more details about this configuration activity.
Choose the link to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP Fiori launchpad as a
Configuration Expert - Business Process Configuration.
Type: 10
Account Type Description: Current Account
Purpose
In general, a bank account with multiple house bank accounts and a different company code between bank account and house bank account are forbidden and an error message is raised when saving
the bank account. But in some special case, if you want to maintain multiple house bank accounts or a different company code between bank account and house bank account, you can follow this in-
struction to customize the message from error to warning.
Procedure
Depending on your configuration environment for SAP S/4HANA Cloud, choose one of the following options:
Configure Your Solution:
2 Access the SAP Fiori app Open Manage Your Solution(F1241). The Change View "Message Control by User": Overview screen dis-
Open Configure Your Solution. plays.
3 Work Area Enter FCLM_BAM_MAINT in the Area field, then choose Save.
4 Change Message Status for Multiple House Bank Make the following entries: You can create multiple house bank account connectivity with warning
Accounts MsgNo: 537 message displays.
5 Change Message Status for Different Company Make the following entries: You can create different company codes between bank account general
Codes between Bank Account and House Bank Ac- MsgNo: 466 data and house bank account connectivity with warning message dis-
count plays.
Message Text: Company code &1 is inconsistent
with company code &2 of bank account.
User Name: (Blank)
*Online: W
*Batch Input: W
Standard: E
6 Change Message Status for Bank Account Descrip- Make the following entries: Warning message displays if the bank account’s description is missing
tions in Different Language Environments MsgNo: 522 in different language environments.
7 Change Message Status for Non-Existing Payment Make the following entries: If non-existing user is maintained as the payment approver, you will
Approver MsgNo: 187 only receive warning message for the following operation of the bank
account.
Message Text: Payment approver & does not exist.
User Name: (Blank)
*Online: W
*Batch Input: W
Standard: E
1 Log On Log on to the project experience in SAP Central Business Configuration. The SAP Fiori launchpad displays.
2 Open Change Message Control In the Product-Specific Configuration phase, navigate to the Configuration Activities The Change Message Control screen displays.
tab. To locate the activity in the tree view, search for the following activity: Change
Message Control.
Choose Open Documentation for the found line item to see more details about this
configuration activity.
Choose the link to navigate directly to the SAP S/4HANA Cloud system. Log on to
the SAP Fiori launchpad as a Configuration Expert - Business Process Configuration.
3 Work Area Enter FCLM_BAM_MAINT in the Application Area field, then choose Continue. The Change View “Message Control by User”: Overview
screen displays.
4 Change Message Status for Multiple House Make the following entries: You can create multiple house bank account connectivity with
Bank Accounts MsgNo: 537 warning message displays.
Message Text: You can link only one central house bank ac-
count to a bank account.
User Name: (Blank)
*Online: W
*Batch Input: W
Standard: E
5 Change Message Status for Different Com- Make the following entries: You can create different company codes between bank account
pany Codes between Bank Account and MsgNo: 466 general data and house bank account connectivity with warning
House Bank Account message displays.
Message Text: Company code &1 is inconsistent with company
code &2 of bank account.
6 Change Message Status for Bank Account Make the following entries: Warning message appears if the bank account’s description is
Descriptions in Different Language Environ- MsgNo: 522 missing in different language environments.
ments
Message Text: Description in language &1 is not maintained
User Name: (Blank)
*Online: W
*Batch Input: W
Standard: E
7 Change Message Status for Non-Existing Make the following entries: If non-existing user is maintained as the payment approver, you
Payment Approver MsgNo: 187 will only receive warning message for the following operation
of the bank account.
Message Text: Payment approver & does not exist.
User Name: (Blank)
*Online: W
*Batch Input: W
Standard: E
Purpose
This step describes how to create Bank and Authorized Representative business partner master data for Bank Account Management. A bank is associated with a Risk Business Partner, Defaultable
Business Partner and Bank Contact Person. Risk Business Partner and Defaultable Business Partner is represented with the BP role TR0703. Bank Contact Persons are external to the company and is
represented by BP role BUP001. Authorized Representative is represented by BP role TR1000.
1 Log On Log on to the SAP Fiori launchpad as a Master Data Specialist - Business Partner Data.
2 Access the SAP Open Manage Business Partner Master Data (F3163). The Manage Business Partner view displays.
Fiori App
3 Create Business Choose Create. The Create Organization dialog box displays.
Partner Choose Person/ Organization/ Group.
Note If you are creating BP Role TR0703 Bank, please choose Organization. If you are creating BP Role
TR1000 Authorized Representative, please choose Person.
4 Enter Data Make the following entries: A New Business Partner is created and displayed in the
Business Partner : 55555 Business Partner view.
2.4.6 Manage Field Status Groups for Bank Account Master Data (Optional)
Purpose
With this Customizing SSCUI, you can define field status groups and special rules to control the appearance and status of the fields on the user interface (UI) screens of the Manage Bank Accounts
app. For example, you may define a field to be mandatory, hidden, editable, or read-only.
Procedure
Depending on your configuration environment for SAP S/4HANA Cloud, choose one of the following options:
Configure Your Solution:
1 Log On Log on to the SAP Fiori launchpad as a Configuration Expert - Business Process Configuration. The SAP Fiori launchpad is
displayed.
2 Access the SAP Fiori App Open Manage Your Solution(F1241). The Manage Field Status
Choose Configure Your Solution. Groups screen is displayed.
Search and choose either Manage Field Status Groups or SSCUI ID 104059 in the search filter.
Choose Configure for the Manage Field Status Groups Step Name.
3 Maintain Field Status In the Dialog Structure panel, choose the Define Field Status Groups folder.
Groups Choose New Entries.
Make the following entries and choose Save:
Field Group: ZBAMACT
Description: BAM Activate Testing Mode.
Select the check box of ZBAMACT.
In the Dialog Structure panel, double-click the Define UI Field Status subfolder.
Choose New Entries.
Make the following entries:
Object: BAM
Press Enter.
Note It is critical to press Enter after object input. You must press Enter before you can use the search help in the Field name
panel. The search help function is linked to an object. Only after the object is confirmed may the search help value be populated in
the Field name.
Field Status: C
Choose Save.
4 Assign Field Status Groups Choose Assign Field Status Grps to Bank Acct Master Data.
to Bank Acct Master Data
Note The field status assignment applies to non-workflow scenario. For workflow scenario, the field status group assignment is
hard coded.
Locate to Scenario Activate Inactive Bank Accounts, update the Field Group to ZBAMACT.
Choose Save.
1 Log on Log on to the project experience in SAP Central Business Configuration. The SAP Fiori launchpad dis-
plays.
2 Open Manage Field Status In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To locate the activity in the tree view, search The Manage Field Status
Groups for the following activity: Manage Field Status Groups. Groups screen is displayed.
Choose Open Documentation for the found line item to see more details about this configuration activity.
Choose the link to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP Fiori launchpad as a Configuration Ex-
pert - Business Process Configuration.
Note It is critical to press Enter after object input. You must press Enter before you can use the search help in the Field name
panel. The search help function is linked to an object. Only after the object is confirmed may the search help value be populated
in the Field name.
4 Assign Field Status Groups Choose Assign Field Status Grps to Bank Acct Master Data.
to Bank Acct Master Data
Note The field status assignment applies to non-workflow scenario. For workflow scenario, the field status group assignment is
hard coded.
Locate to Scenario Activate Inactive Bank Accounts, update the Field Group to ZBAMACT.
Choose Save.
Test Administration
Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>
Purpose
With this Customizing SSCUI, you can define Bank Statement and Cash Balance Integration Configuration at company code level.
1 Log On Log on to the SAP Fiori launchpad as a Configuration Expert - Business Process Configuration. The SAP Fiori launchpad is displayed.
2 Access the SAP Fiori app Make the following entries: The Configure Your Solution – Bank Account
Application Area: Finance Management screen is displayed.
3 Configuration From the Configuration Steps area, select the Define Settings for Bank Statements step, choose Config-
ure.
4 Define Bank Statement and Cash Choose New Entries. Make the following entries and choose Save:
Balance Integration Configuration Company Code: 1010
Valid From: <current date>
Posting Category: posting to be processed
Note If you choose no posting processing for a specific company code, then no FI posting document is
generated during uploading bank statement for all bank accounts under the specific company code.
5 Back Choose Back. The Change View "Bank Statement and Cash Bal-
ance Integration Configuration view displays.
1 Log on Log on to the project experience in SAP Central Business Configuration. The SAP Fiori launchpad displays.
2 Open Settings for Integrate with In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To locate the The Integrate with End-of-Day Bank Statements
End-of-Day Bank Statements activity in the tree view, search for the following activity: Define Settings for Bank Statements. screen is displayed.
Choose Open Documentation for the found line item to see more details about this configuration activity.
Choose the link to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP Fiori
launchpad as a Configuration Expert - Business Process Configuration.
3 Define Bank Statement and Cash Choose Integrate with End-of-Day Bank Statements.
Balance Integration Configuration Choose New Entries. Make the following entries and choose Save:
Company Code: 1010
Valid From: <current date>
Posting Category: posting to be processed
Note If you choose no posting processing for a specific company code, then no FI posting document is
generated during uploading bank statement for all bank account under the specific company code.
4 Back Choose Back. The Change View "Bank Statement and Cash Bal-
ance Integration Configuration view displays.
Test Administration
Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>
Purpose
You can define settings for integrating end-of-day electronic bank statements with cash management for individual bank accounts.
Procedure
2 Access the SAP Fiori App Open Define Bank Account Settings - Bank Statements (F5488).
3 Define Bank Account Setting Choose Create. The Define Bank Account Settings – Bank
for Bank Statement Make the following entries and choose Create: Statements view displays.
Note If field Technical ID is not visible, select Adapt Filters to include the field into the Filter bar.
Note
1. If you choose no posting processing for a specific bank account, then no FI posting document is gener-
ated during uploading bank statement for the bank account.
2. The setting you defined in this step has higher priority than the setting you defined in previous step De-
fine Settings for Bank Statements [page ] 18.
The Basic Bank Account Management (BFA) scope item consists of process steps in the table below, depending upon the which of the four procedures you will implement.
Note If your system administrator has enabled spaces and pages on the SAP Fiori launchpad, the homepage will only contain the essential apps for performing the typical tasks of a business
role.
You can find all other (searchable) apps not included on the homepage using the search bar (2434549).
If you want to personalize the homepage and include the hidden apps, navigate to your user profile and choose App Finder.
Caution Instructions provided assume that you are only implementing one of the four Bank Account Master Data Procedures. If you are implementing and testing more than one procedure, es-
pecially in a single environment, you cannot use the same Master Data values for more than one procedure type. You must have additional Master Data values created, for example bank account
numbers, bank keys, and so on, and then use these different values in each procedure.
Table 2: Bank Account Master Data Processing With Basic Cash Management and Direct Revision Activate
Process Step, Report or Item Business Role App/Transaction Expected Results
Open Bank Account [page ] 25 Cash Management The bank accountant goes to the bank and opens a new bank account in this bank. This step does not occur in the sys-
Specialist tem.
Create Bank Master Data [page ] 26 Cash Management Manage Banks A bank key that does not exist in production system is created. If the bank key already exists, skip this step.
Specialist
Edit Bank Master Data [page ] 27 Cash Management Manage Banks More bank information is input in production system.
Specialist
Create Bank G/L Account [page ] 28 General Ledger Ac- Manage G/L Account Master FIN master data key user may create the G/L accounts of newly created bank account.
countant Data (F0731A)
Manage Banks Cash Management Data Cash Management Manage Banks The bank accountant creates the house bank. If a new bank account is opened in an existing house bank in your sys-
[page ] 29 Specialist tem, skip this step.
Create Bank Account [page ] 30 Cash Management Manage Bank Accounts A new bank account that does not exist in production system is created.
Specialist (F1366A)
Export Bank Accounts [page ] 33 Cash Management Manage Bank Accounts Bank accounts are exported from production system.
Specialist (F1366A)
Import Bank Accounts [page ] 35 Cash Management Manage Bank Accounts Bank accounts are imported into development system and consolidation system.
Specialist (F1366A)
Notify Bank to Change [page ] 36 Cash Management The bank accountant goes to the bank and asks the bank employee to change the attributes of this bank account. This
Specialist step does not occur in the system.
Update Bank G/L Account [page ] 37 General Ledger Ac- Manage G/L Account Master FIN master data key user updates the G/L account of bank only when it is necessary. However, modification of bank
countant Data (F0731A) account does not result in G/L account modification every time.
Change Bank Account [page ] 40 Cash Management Manage Bank Accounts The bank accountant changes the attributes of this bank account in system.
Specialist (F1366A)
Notify Bank to Close Account [page ] 41 Cash Management The bank accountant goes to the bank and asks the bank employee to close this bank account. This step does not occur
Specialist in the system.
Close Bank Account and Cancel Closing Cash Management Manage Bank Accounts The redundant bank account is closed in system.
[page ] 42 Specialist (F1366A)
Delete Bank Account (Optional) [page ] Cash Management Manage Bank Accounts GL Accounts are reduced and migrated.
44 Specialist (F1366A)
Import Bank Data [page ] 45 Cash Management Transfer BIC Data (BIC2) The bank data is imported.
Specialist
Fields Enhancement for Bank Account Administrator Custom Logic (F1481) Fields are added.
Master Data [page ] 47
Create Bank Chain [page ] 49 Accounts Payable Accountant Manage Bank Chains (F4004) Bank chain created.
Change Bank Chain [page ] 50 Accounts Payable Accountant Manage Bank Chains (F4004) Bank chain changed.
Delete Bank Chain [page ] 51 Accounts Payable Accountant Manage Bank Chains (F4004) Bank chain deleted.
Check Bank Chain Information In Business Partner (Optional) [page ] 52 Accounts Payable Accountant. Maintain Business Partner (BP) Bank chain information checked in business partner.
Schedule Delete Bank Chain Jobs [page ] 54 Accounts Payable Accountant Schedule Bank Chain Jobs (F4503) Bank chain information checked in business partner.
These sections describe the test procedures for each process step that belongs to this scope item.
Follow the procedures in the Bank Account Master Data Processing With Basic Cash Management and Direct Revision Activate section when you use Basic Cash Management without an ad-
ditional license for SAP Cash Management powered by SAP HANA.
When you have Full Cash Management, which requires an additional license for SAP Cash Management powered by SAP HANA, follow the procedures that apply to your implementation: Bank
Account Master Data Processing With Full Cash Management and Direct Revision Activate, or Bank Account Master Data Processing With Full Cash Management and Dual Control Revision Acti-
vate, or Bank Account Master Data Processing With Full Cash Management and Workflow Revision Activate.
Caution Instructions provided assume that you are only implementing one of the four Bank Account Master Data Procedures described in the Purpose [page ] 3 section. If you are implementing
and testing more than one procedure, especially in a single environment, you cannot use the same Master Data values for more than one procedure type. You must have additional Master Data
values created, such as bank account numbers, bank keys, and so on, and then use these different values in each procedure.
4.1 Bank Account Master Data Processing with Basic Bank Account Management
SAP has predelivered bank and bank account master data as demo data in START system. If you are using Solution Builder for activation, please don't copy these SAP predelivered master data from
START system to Q or P system. Because ID Clash will not triggered, you may not be able to delete these entries in Q or P. But If you use SAP Central Business Configuration as your configuration
environment, whether it is for 2 System Landscape or 3 System Landscape, you won't get such issue.
Purpose
The bank accountant (Cash Management Specialist) goes to the bank and opens a new bank account in this bank. This step does not occur in the system.
Test Administration
Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>
Purpose
In this step, you can create standard banks and internal banks master data with general information. For physical banks you should create it as standard banks, and for others you should create it as
internal banks.
Note The app Manage Banks and Manage Banks Basic will be replaced by app Manage Banks - Master Data (F6437) and Manage Banks - Cash Management (F1574A) on CE2308.
Note The bank key is created in the production system, development system, and consolidation test system.
Procedure
3 Choose Create Choose Go for the banks to display in a list and choose Create. The Create Bank
Bank view displays.
Bank Country/Region: DE
Bank Key: 50070011
Choose Create.
6 Create Internal Go to the initial page of app Manage Banks - Master Data (F6437).
Banks Choose the triangle button beside the Create.
Choose Create Internal Bank.
Note If the bank key created is used for an internal virtual bank, for example, PayPal,
● which is used as House Bank, please select Internal - Payment Service Provider.
● which is used to enable the maintenance of the business partner bank details with alias, please select the Payment system. For more details,
please refer to SSCUIs 105361 - Define Alias Types and 105362 - Define Payment Systems.
Choose Create.
Test Administration
Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>
Purpose
The purpose of this step is to edit bank and input more bank information in production system.
Procedure
Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment
2 Access the SAP Fiori App Open Manage Banks - Master Data (F6437).
3 Filter the Bank Make the following entry in the filter and choose Go.
Bank Key: 50070011
Purpose
The General Ledger Accountant may create the G/L accounts for a new bank account.
Note If you want to create a new G/L account for a new bank account, execute the following steps. Create the G/L accounts in production system, development system, and consolidation test
system.
Note This procedure is mentioned in the Accounting and Financial Close (J58) test script. You can refer to the Manage G/L Account Master Data step and copy an existing G/L account to a
new one (for example, copy 11001000 to 11003000).
Test Administration
Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>
Purpose
In this step, you can input banks data that is used for cash management.
Procedure
Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment
2 Access the SAP Fiori App Open Manage Banks - Cash Management (F1574A).
3 Enter Search Criteria Make the following entries: The Display Bank view appears.
● Bank Country/Region: DE
● Bank Key: 50070011
If the Bank Key field is not visible, choose Filters to unhide it.
Choose Go.
Go into the detail of the bank.
4 Enter Control Data Choose Edit. The Manage Banks view displays.
Make the following entry:
Risk Business Partner: for example, 55555
5 Enter House Bank Data Go to House Banks tab and choose Create.
Make the following entries:
Company Code: 1010
House Bank: DEBK3
Choose Continue.
Choose Apply.
6 Enter Netting Business Partner Go to Netting Business Partner tab and choose Create.
Make the following entries:
Valid From: <Current Date>.
Valid To: <Futrue Date>.
Business Partner: <Choose one by using search help>.
Choose Continue.
Test Administration
Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>
Purpose
This step describes how to create a new bank account by a bank accountant (Cash Management Specialist).
Note Please note that the bank account must be created manually in the Production system, because this kind of master data can not be transport from the Q system to the P system.
Procedure
2 Access the SAP Fiori Open Manage Bank Accounts (F1366A). The Manage Bank
App Account view dis-
plays.
Note To maintain the bank key in this step, the bank key must already exist in the system.
Note Only perform this step if the country is using IBAN; if you do not use IBAN in your process, just skip this step.
Note Bank Control Key is only used in some countries like France, Spain, Italy. If you don't use Bank Control Key, you should leave this field
blank.
Note The field Transaction Type is not available for on premise. To assign the Transaction Type to your Bank Account use the IMG Menu
Path: Financial Accounting > Bank Accounting > Business Transactions > Payment Transactions > Electronic Bank Statement > Make Global
Settings for Electronic Bank Statements
6 Generate IBAN Note Only perform this step if this country is using IBAN. If you do not use IBAN in your process, you can skip this step.
Choose IBAN.
When the warning dialog box appears, choose OK.
The proposed IBAN is automatically entered.
7 Choose House Bank Choose House Bank Account Connectivity. The Connectivity
Account Connectivity Path tab appears.
9 Save and Activate Ensure all necessary data have been entered and choose Save as Inactive. A new bank account
Bank Account Choose Activate. is created.
10 Review History and Select the newly created bank account, and on the Bank Account view, the new bank account is active in the display mode. No revision button ex-
Revision ists.
Choose Account Histories and a history dialog box displays with the history list of the current bank account: Revision 1, activated.
Test Administration
Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>
Purpose
The new bank account (including house bank account) creation in production system is completed in the previous procedure. Some system configuration is based on the house bank and the house
bank account. Because configuration is done in the development system, you must export the bank accounts from that system to the development and consolidation test system.
Prerequisites
Note
● You use Microsoft Office 2010 or higher that contains Microsoft Excel.
Procedure
2 Access the SAP Open Manage Bank Accounts (F1366A). The Manage Bank Accounts view displays.
Fiori App
3 Import and Export Choose Import and Export Bank Accounts. The Import and Export Bank Accounts view displays.
Accounts
4 Export Data In the Bank Accounts Export section, enter company code and choose Go. Select the The Bank_Accounts.xml file saved to the location you indicated.
check box of the bank accounts, and choose Export Bank Accounts to an XML File. The file contains all the existing bank account master data in your system in XML for-
In the File Download dialog box, choose Save As. mat.
In the Save As dialog box, identify a location to save the XML file.
Choose Save.
Note Download processing steps varies on different browser, above steps apply to
IE. If you are using Chrome, the file will be directly saved in C:\Users\[your user
ID]\Downloads
5 Download the In the Bank Accounts Export section, choose Download XML Spreadsheet Template. The XML_Spreadsheet_Template.xml file is saved to the location you indi-
Spreadsheet Tem- In the File Download dialog box, choose Save As cated
plate
In the Save As dialog box, identify a location to save the XML spreadsheet template.
Choose Save.
Note Download processing steps varies on different browser, above steps apply to
IE. If you are using Chrome, the file will be directly saved in C:\Users\[your user
ID]\Downloads
6 Import Use Microsoft Excel to open XML_Spreadsheet_Template.xml. Bank accounts master data has been imported into the XML spreadsheet template.
Using the Developer tab in Excel, choose Import, and then choose the Bank_Ac- If message XML import error - Failed schema validation displays,
counts.xml file in the Import XML dialog box and Import. but data has been imported from Bank_Accounts.xml, ignore this message by
choosing OK.
7 Export Data to a From the Developer tab in Microsoft Excel, choose Export, and enter the file name Bank accounts master data has been saved in the Bank_Account_Export.xml
New File Bank_Accounts_Export.xml. file.
Choose Export.
Test Administration
Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>
Purpose
This instruction guides you how to import the bank accounts into the target system. If you use Solution Builder environment with 2 system landscape, or use SAP Central Business Configuration
with 2 system landscape, you may use this functinality to update your test system. If you use On-Premise system or use SAP Central Business Configuration with 3 system landscape, the develop-
ment system can also be updated besides the test system.
Note You may only have one client for testing. You can test the function Export and Import the bank accounts in the same client.
Procedure
2 Access the SAP Open Manage Bank Accounts (F1366A). The Manage Bank Accounts view dis-
Fiori app plays.
3 Import and Ex- Choose Import and Export Bank Accounts. The Import and Export Bank Ac-
port Accounts counts view displays.
5 Import with Test Choose Import with Test Run, and verify the validation results.
Run
Note If the Bank Account "XXXXXXXXXX" is already in approval process notification displays, we recom-
mend that you import the bank accounts at a different time, since those bank accounts are in process workflow.
When the message displays, only execute a test run, or complete the workflow, before the production run.
When the status of all validation results is OK, you can import bank accounts into production system.
6 Import with Pro- Choose Select File again. Bank accounts are successfully im-
duction Run In the Open dialog box, identify the XML (Bank_Accounts.xml) to be uploaded ported into development system.
Choose Open.
Choose Import and check the validation results.
7 Import to Test Repeat the preceding steps to import bank accounts into consolidation test system.
System
Procedure
The bank accountant (Cash Management Specialist) goes to the bank and asks the bank employee to change the attributes of this bank account. This step does not occur in the system.
Test Administration
Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>
Purpose
The key user updates the G/L account of the bank only when updating is required. For example, if the currency key of the bank account is changed, the user updates the currency of the G/L account.
Not all bank account modifications result in a G/L account modification.
Note Update the G/L accounts in the production, development, and consolidation test systems.
Procedure
Depending on your configuration environment for SAP S/4HANA Cloud, choose one of the following options:
Configure Your Solution:
2 Access the SAP Fiori app Open Manage Your Solution (F1241).
3 Search Configuration Open Configure Your Solution. The Configure Your Solution: Realize Phase screen displays.
6 Open Choose the arrow at the right of the column with the Chart of Accounts item.
7 Select Configuration Step For the Manage G/L Account Master Data SSCUI 150001 step, choose Configure.
9 Choose Company Code If prompted, choose the company code 1010 in which to change the G/L account. The Manage G/L Account Master Data screen displays.
10 Search for Your Account Make the following entries and choose Go: Relevant bank subaccounts are updated.
Chart of Accounts: YCOA
G/L Account: For example, 11001000
View: Chart of Accounts View
11 Choose the G/L Account Choose the triangle button on the right of the target G/L Account.
13 Choose Company Code Choose the company code 1010 in which to change the G/L account. A screen showing the account parameters at the company code
level displays.
15 Save the G/L Account Choose Save. The G/L account is updated successfully.
16 Update Bank Subaccount Repeat the preceding steps to change bank subaccounts. Relevant bank subaccounts are updated.
For example, from 11001010 to 11001099.
1 Log on Log on to the project experience in SAP Central Business Configuration. The SAP Fiori launchpad displays.
2 Open Manage G/L Account In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To locate The Manage G/L Account Master Data screen displays.
Master Data the activity in the tree view, search for the following activity: Manage G/L Account Master Data.
Choose Open Documentation for the found line item to see more details about this configuration ac-
tivity.
Choose the link to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP Fiori
launchpad as a Configuration Expert - Business Process Configuration.
4 Choose Company Code If prompted, choose the company code 1010 in which to change the G/L account. Note You can also complete the test by logging on as Gen-
eral Ledger Accountant and use Manage G/L Account Mas-
ter Data (F0731A).
5 Search for Your Account Make the following entries and choose Go: Relevant bank subaccounts are updated.
Chart of Accounts: YCOA
G/L Account: For example, 11001000
View: Chart of Accounts View
6 Choose the G/L Account Choose the triangle button on the right of the target G/L Account.
8 Choose Company Code Choose the company code 1010 in which to change the G/L account. A screen showing the account parameters at the company code
level displays.
10 Save the G/L Account Choose Save. The G/L account is updated successfully.
11 Update Bank Subaccount Repeat the preceding steps to change bank subaccounts. Relevant bank subaccounts are updated.
For example, from 11001010 to 11001099.
Note Changing the currency is not possible when there is an existing balance for the G/L account.
Test Administration
Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>
Purpose
This step describes how to change a bank account by bank accountant (Cash Management Specialist).
Test Step Test Step Name Instruction Expected Result Pass / Fail / Com-
# ment
2 Access the SAP Fiori Open Manage Bank Accounts (F1366A). The Manage Bank Accounts (F1366A) view displays.
App
3 Choose Account to Choose the bank account to be changed from the account list A new view displays.
Change view.
For example, account 1133681 in DEBK3.
Enter the filter and choose Go.
5 Save Choose Save to save the changes. The bank account changes (updated) and a warning notification displays about bank state-
ments.
Procedure
The bank accountant (Cash Management Specialist) goes to the bank and asks the bank employee to close the bank account. This step does not occur in the system.
Test Administration
Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>
Purpose
This step describes how to close an obsolete bank account by bank accountant (Cash Management Specialist) and the process of canceling the closing if you want to reactivate it.
Prerequisite
Status Comment
Active This status indicates bank account is successfully created in sap system and can be normally used.
Inactive This status displayed in full cash management, it indicates bank account is initially created without being approved.
Closing Request This status indicates you have planned and informed the bank to close the bank account in a future date. After initial closing button is triggered and approved, the bank account status will be display as
Sent to Bank Closing Request Sent to Bank. The function of bank account in status Closing Request Sent to Bank is the same with bank account status active, for example, you can still normally use it as review bank
account, make bank transfer, run payment, posting etc.
Closed at Bank This status indicates the bank account has been closed by the bank. You can’t make bank transfer, run payment, review bank account, maintain payment approver, import signatory cards, monitor intra-
day/end of day bank statement and being displayed in bank relationship overview in this status. But posting is still allowed in Closed at Bank.
Closed This status indicates the bank account is completely closed in sap system, posting is also banned when comparing with status Closed at Bank.
Caution Don't close sample bank accounts that are connected to house bank DEBK1/DEAC1 and DEBK2/DEAC2 in the Connectivity Path tab for the bank master data (bank account 1133698
Procedure
Test Test Step Name Instruction Expected Result Pass / Fail / Comment
Step #
3 Choose the Bank Choose the triangle button of the bank account
Account to Close to be closed
For example, account 1133681 in DEBK3.
4 Bank Account Ini- Choose Send Closing Request to Bank. The Initiate Closing dialog box is
tial Closing displayed.
5 Start to Initial Make the following entries in the dialog box The bank account’s status is
Closing and choose Send Closing Request to Bank: changed to Closing Request Sent to
Planned Closing Date: for example, <cur- Bank.
rent date>+2days
6 Confirm Closing at Choose Confirm Closing at Bank. The Confirm Closing at Bank dia-
Bank log box is displayed.
7 Start to Confirm Make the following entries in the dialog box The bank account’s status is You can choose confirm closing at bank without bank account initial closing. If you bypassing the ini-
Closing at Bank and choose Confirm Closing at Bank. changed to Closed at Bank. tial closing procedure and choose confirm closing at bank, the bank account status will be changed to
Closing Date: for example, <current Closed at Bank directly.
date>
8 Complete Closing Choose Complete Closing. The Complete Closing dialog box
is displayed.
Bank.
11 Revert to Active Choose Change Back to Activate. The bank account’s status is You can choose Revert to Active directly in bank account status Close at Bank, after which bank ac-
changed to Active. count status will be changed to Active.
Test Administration
Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>
Purpose
This step describes how to delete bank account by bank accountant (Cash Management Specialist).
Note Only the bank accounts in inactive status or active bank accounts that never involved in any business transaction or used in any configuration can be deleted.
Procedure
Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment
2 Access the SAP Fiori app Open Manage Bank Accounts (F1366A).
3 Choose the Bank Account to Delete Select the checkbox on the left of the bank account to be deleted The Bank Account is deleted.
For example, account 1133681 in DEBK3.
Choose Delete.
Choose Delete on the pop up window.
Test Administration
Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>
Purpose
In this activity, you import bank master data into the SAP S/4HANA system.
Prerequisites
Download a copy of the linked bank data template file. You can also get it from the SWIFT website.
1 Log On Log onto the SAP Fiori launchpad as a Cash Management Specialist.
3 Import In the Open dialog box, browse to the location of the bank data text file, and choose Open.
Bank Data
4 Enter Data Make the following entries and choose Execute: The Import and Ex-
File Structure: Bank Directory SAP (swiftrefdata.com), BDE port Bank Accounts
screen displays.
Country/Region Key: <bank country>, for example, DE
Test Run: Select (for test run), or Deselect (for actual run)
Note
● The Bank country selection option restricts the quantity of data imported from the file to the countries that you specify. For example you can use this to
split the countries into groups for processing in multiple program runs with different import parameters. If you do not specify a country, the system pro-
cesses all the data records from the file whose ISO country code matches the two-character ISO country code of a country set up in the SAP system.
● Test Run checkbox: If you select this checkbox, the system does not update the data in the database when you execute the report. In a test run, the system
processes the data and displays the planned changes in a list. The database is not updated.
● Delta Upload checkbox: If you select this checkbox, the system imports only the delta file instead of the full file.
● The Bank Key in Type 4 parameter controls which data (fields) is used from the file as the bank key if the bank key type 4 (assigned externally) is set for
the relevant country in the country-specific checks
● SEPA mode (IBAN BIC) check box: Select this checkbox if you plan to transfer funds to a country as a SEPA payment only.
● Use IBAN Country Code checkbox: If you select this checkbox, the system uses the IBAN country code for the bank assignment.
● Branch Code XXX for HQ checkbox: If you select this checkbox, the system uses the dummy branch code XXX from the file to increase the 8-character
BIC to the full 11 characters, for example: NDEASESSXXX. If you do not select this checkbox, the system transfers the BIC without the branch identifier,
for example, NDEASESS. This parameter does not affect the full 11-character BICs. These are always transferred in full, for example, NDEASESSA21.
You can use this parameter, for example, to also import a national bank directory where the dummy ID XXX is not used. This avoids duplicate entries
where one has the XXX ID and the other does not.
● Mark for Deletion checkbox: If you select this checkbox, the system flags banks for deletion that are no longer valid in the SAP system.
● For Own Data Records Only (BDE) checkbox: If you select this checkbox, you restrict the quantity of banks flagged for deletion to those that were created
with this program and file format.
Test Administration
Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>
Prerequisite
Purpose
A BADI is provided to implement definition of custom fields and its default value. You can use this function to define your field and set its default value through BADI coding, implementation tuto-
rial is attached on the online document help of Cash & Liquidity Management.
Procedure
5 Publish Fields Log on to the SAP Fiori launchpad as a Cash Management Specialist.
Note You need to assign Administrator Role to User Cash Management Specialist, otherwise you won't see Adapt UI option.
Test Administration
Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>
Prerequisite
The recipient’s bank key and recipient’s bank account number of the bank chain is maintained in the Maintain Business Partner app not Manage Bank Account app. The sender’s bank key is main-
tained in Manage Bank Account app, and the sender’s bank account is the house bank account you maintained for the bank key. Make sure you have created the business partner and maintained cor-
responding bank key and bank account before testing.
Procedure
Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment
2 Access the SAP Fiori app Open Manage Bank Chains (F4004).
3 Create Bank Chain Choose Create. The Create Bank screen displays.
6 Enter Intermediary Bank Data Make the following entries and choose Create.
Type of Bank in Bank Chain: for example, 2 (Intermediary bank)
Country Key of a Correspondent Bank: DE
Bank Key of a Correspondent Bank: 82080000
Account Number of a Correspondent Bank: 2580061
Test Administration
Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>
Purpose
Procedure
Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment
2 Access the SAP Fiori app Open Manage Bank Chains (F4004).
Test Administration
Purpose
Procedure
Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment
2 Access the SAP Fiori app Open Manage Bank Chains (F4004).
3 Delete Bank Chain (Option 1) Input the filter and choose Go。 The selected object has been deleted.
Select the check box of the bank chain.
Choose Delete.
Choose Delete.
Test Administration
Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>
The receiver’s bank account is associated with the business partner, you can find the bank chain information via business partner.
Procedure
3 Search Busi- Choose Open BP. The Create Bank screen displays.
ness Partner Press F4.
Note In the dialog box select the value help (F4) for the Business Partner. If you can´t see the below mentioned fields, select the Change
search criteria category and choose Partner by bank details by selecting the little downside arrow next to the displayed search criteria cate-
gory. Then you get all search criteria categories displayed.
Note If you can't find the business partner, you can refer to Preliminary Steps Create Business Partners for Bank Account Management
[page ] 14 section to create one.
4 Recipient Make the following entry: The selection area displays the
Bank Chain Display in BP role: Financial Services BP sender’s bank information.
5 Bank Chain Choose the check box of one line item in the selection area. Bank chain assignment area dis-
Assignment Double click Bank Chain Assignment. plays the intermediary bank infor-
mation.
Test Administration
Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>
Purpose
Prerequisite
Schedule Delete Bank Chain Jobs is only used for deleting unused bank chain, which means the recipient bank account of the bank chain are no longer related to any business partner. In addition, the
intermediary banks data should exist before using this job.
2 Access the SAP Fiori app Open Schedule Bank Chain Jobs (F4503).
3 Start Schedule Delete Bank Choose Create. The New Job: Delete Bank Chains
Chain Jobs screen displays.
Note If below mentioned data don't work, you can leave all General Selection Criteria empty, which means the delete
job will apply to all the unused bank chain.
Test Administration
Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>
Purpose
There might be some inconsistent data for a closed bank account. These data includes, bank determination data for payment, account determination data for bank transfer, Clearing account for re-
ceiving banks and the remaining house bank account data in G/L account, which can cause inconsistent check error. You can fulfill this step to check and remove the inconsistent data.
Procedure
Depending on your configuration environment for SAP S/4HANA Cloud, choose one of the following options:
Configure Your Solution:
Test Step Test Step Name Instruction Expected Re- Pass / Fail / Com-
# sult ment
1 Log on Log onto the SAP Fiori launchpad as a Configuration Expert - Business Process Configuration.
3 Remove Bank Determination Data Select the check box of the company code that the closed bank account belongs to.
Choose Bank Accounts Tab.
Select the check box of the inconsistent bank determination data.
Choose Delete.
Choose Save.
5 Remove Account Determination Data Input the company code that the closed bank account belongs to.
Choose Enter.
Select the check box of the inconsistent account determination data.
Choose Delete.
Choose Save.
6 Access Acct Transfer: Determing Receiving Bank’s Clearing Ac- Open Manage Your Solution (F1241).
count SSCUI Choose Configure Your Solution.
Make the following entries:
Application Area: Finance
Sub Application Area: Accounts Payable
In the General Payment Settings row, choose the arrow button at the right of the row.
In the right pane, for the Define Clearing Accts for Receiving Bank for Acct. Transfer row, choose
Configure.
7 Remove Receiving Bank’s Clearing Account Select the check box of the inconsistent clearing account data.
Choose Delete.
Choose Save.
1 Log on Log on to the project experience in SAP Central Business Configuration. The SAP Fiori launchpad displays.
2 Open Set Up Bank Determination for In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To locate the activity in The Document Types Purchase or-
Payment Transactions the tree view, search for the following activity: Set Up Bank Determination for Payment Transactions. der Change screen displays.
Choose Open Documentation for the found line item to see more details about this configuration activity.
Choose the link to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP Fiori launchpad as a
Configuration Expert - Business Process Configuration.
3 Remove Bank Determination Data Select the check box of the company code that the closed bank account belongs to.
Choose Bank Accounts Tab.
Select the check box of the inconsistent bank determination data.
Choose Delete.
Choose Save.
4 Open Define Account Determination In the Product-Specific Configuration phase, navigate to the Configuration Activities tab and search for the follow-
ing activity: Define Account Determination.
Choose Open Documentation for the found line item to see more details about this configuration activity.
Choose the link to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP Fiori launchpad as a
Configuration Expert - Business Process Configuration.
5 Remove Account Determination Data Input the company code that the closed bank account belongs to.
Choose Enter.
Select the check box of the inconsistent account determination data.
Choose Delete.
Choose Save.
6 Open Define Define Clearing Accts for On the Configuration Activities tab, search for the following activity: Define Clearing Accts for Receiving Bank
Receiving Bank for Acct. Transfer for Acct. Transfer.
Choose the link to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP Fiori launchpad as a
Configuration Expert - Business Process Configuration.
7 Remove Receiving Bank’s Clearing Select the check box of the inconsistent clearing account data.
Account Choose Delete.
Choose Save.
Test Administration
Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>
Purpose
You can reduce your GL account by using the reconciliation account and migrate your old GL account data to it.
Caution The following section is ONLY relevant for the on-premise version of SAP S/4HANA. Cloud version of SAP S/4HANA support G/L reduction, but not G/L migration. If you want to
do G/L reduction on the cloud, you can replace the house bank account connectivity with a new bank reconciliation account.
Procedure
Test Step Test Step Name Instruction Expected Result Pass / Fail / Com-
# ment
2 Access the SAP Fiori App Open Manage Bank Accounts (F1366A).
3 Choose the Bank Account to Choose the bank account to be changed from the account list view. A new window displays.
Change For example, account 1133698 in DEBK1.
Enter the filter and choose Go.
4 Start to Edit Choose the triangle button of account 1133698. House Bank Account Connectivity screen
Choose Edit. displays.
5 Reduce and Migrate G/L Ac- Choose Migrate G/L Account, and the Target Bank Reconciliation Account field displays.
count Choose the target bank reconciliation account through search help.
Note If no old GL account exist, or you don’t have to migrate the data, you don’t have to use Migrate
G/L Account button.
Choose Apply.
Example Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names,
menu paths, and menu options.
Textual cross-references to other documents.
EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, table names, and
key concepts of a programming language when they are surrounded by body text, for example, SELECT and IN-
CLUDE.
Example Output on the screen. This includes file and directory names and their paths, messages, names of variables and parame-
ters, source text, and names of installation, upgrade and database tools.
Example Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documenta-
tion.
<Example> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to
make entries in the system.