Professional Documents
Culture Documents
Draft 6
Draft 6
Follow
RSS feed
Like
9 Likes 3,584 Views 5 Comments
Prima facie Migration of House Banks to SAP S/4HANA seems to be simple. Sometimes,
it creates challenging and interesting issues as we go through the Migration
process.
What is New:
To simplify the migration process, as of SAP S/4HANA 1909, following manual steps
are included in Central Migration Cockpit (Start and Monitor Data Migration)
Activities “Fill in Due Dates in FI Document and Display Status of Filling Due
Dates into FI Documents are now executed automatically in the Enrich Transactional
Data (ENR) step of the Start and Monitor Data Migration activity.
Migrate House Bank Accounts now executed automatically in the Migrate House
Bank Account (T012K) to Bank Account (CM1) step of the Start and Monitor Data
Migration Activity
High -level SAP S/4HANA Data Model Changes relating to House Banks:
House bank accounts merged into bank account master data. As a part of
migration, house bank accounts originally stored in database table "T012K" moves
to table "FCLM_BAM_ACLINK2".
After Migration, we can create the House banks using transaction code
FI12_HBANK. This transaction code is only for creating the House bank but not Bank
Accounts for House Banks.
Activation of Business Function FIN_FSCM_CLM is not mandatory for Migration of
House Banks. (Not full scope of CLM used)
Some House Bank Related table names
Table Name
Description
FCLM_BAM_AC_LINK
FCLM_BAM_AC_TYPE
FCLM_BAM_AC_TYPT
FCLM_BAM_ACLINK2
FCLM_BAM_AMD
FCLM_BAM_AMD_T
FCLM_BAM_BKBPHIS
FCLM_BAM_BNKABP2
FCLM_BAM_CONFIG
FCLM_BAM_HIER
FCLM_BAM_HIERBGN
FCLM_BAM_REQ
FCLM_BAM_REQACNT
Change Request:Bank Accounts
The Bank Account Master Data Processing with Full Cash Management versions
including Direct Revision Activate, Dual Control Revision Activate and Workflow
Revision Activate, require an additional license for SAP Cash Management powered by
SAP HANA.
If the errors are relating to pre-delivered content, we can also accept the errors,
if we are convinced about the nature of those errors. If it is relating to the
Business bank data information, further analysis and fix is required.
Based on the errors during Migration Cockpit execution, we can fix the errors
whatever is possible, reset and reexecute the step in Migration Cockpit.
If any errors found during the migration cockpit run, we can also execute the house
bank migration manually using Tcode: FCLM_BAM_MIGRATION. This tcode gives an
opportunity to see the status traffic light. We can re-execute for the red ones to
know any further errors.
After executing the migration, we can also see log in tcode: SLG1 to see the
details of the error.
Most of the errors during House bank migration are self explanatory.
SAP Notes, given under references section gives a good idea about House Banks
related topics.
Please note, we need to document the process steps followed for resolution of the
House bank migration issues and thorough testing is done subsequent to migration.
This helps to have a clarity during the next/subsequent cycle runs before the
Production run of migration.
House Bank Accounts can be accessed either by Fiori Apps or through NWBC.
This is required only to see the house bank after migration or to set up new house
bank accounts for testing.
Set up NWBC
Activate the following Webdynpro using Tcode: SICF
"WDA_FCLM_BAM_HIERARCHY"
"WDA_FCLM_BAM_ACC_MASTER"
"WDA_FCLM_UPLOAD_DOWNLOAD"
Assign PFCG role for example: "SAP_FI_BL_BANK_MASTER_DATA" to required users.
From SAP GUI, use tcode: NWBC
Please refer the below notes and references mentioned within the notes, this helps
to understand any issues during migration/conversion to SAP S/4HANA.
References/SAP Notes:
Alert Moderator
Assigned tags
Related Questions
The Manage House Banks Fiori App does not display the list of banks on the left
side when entering.
By Former Member, Jan 31, 2017
Replicating Bank Data from one system to another system
By Kavya Lakshminarayanasetty, Dec 06, 2018
Manage bank accounts - connecting with house banks
By Fabian Stolz, Sep 07, 2020
5 Comments
You must be Logged on to comment or reply to a post.
Neat and clear flow in good understanding way... Thanks for sharing
Like(1)
Author's profile photo Warren Nash
Warren Nash
May 12, 2020 at 2:38 am
Dear Venkata
You have given very enriched information for house bank migration.
When I migrate it, I have two quesitons which will make me confused.
First, the account id's description which is existed in tabel T012T in orginal
system partly backuped in the proxy oject V_T012T_BAM and I can't find the rule of
backup and un-backup item.
second, why the only item in orginal system have serval different REVISION
Number after migration, and why is the field DELETED_FLAG for some item? which
reasons resulted it?
thank you
Darcy
Like(0)
Author's profile photo Loren Schmidt
Loren Schmidt
July 23, 2020 at 6:21 pm
Good article. I am curious about the reduction of Account Type from multiple
values in earlier versions to the single 01 value in 1909. In prior versions, we
had been doing the manual mapping of our house banks to different account Types for
Current, Payroll, ZBA, Lockbox, etc.. We had concluded that the Account Type does
not necessarily control any SAP functionality; but, it would be helpful if
reporting the different types of accounts in use.
Is there really now a single standard account Type (01) that SAP expects to
be used across all house banks in best practice implementation?
Can the Account Type be changed after migration if we still would like to
have the categorization for reporting?
Find us on
Privacy
Terms of Use
Legal Disclosure
Copyright
Trademark
Cookie