Google Apps Account Migration Import Upload Template

The post-obit blog will focus on the process of creation and massive import of Bank Accounts to an S/4 HANA system, every bit part of a migration activeness needed during a Greenfield transition to S/four scenario and via the tool "Import and Export Bank Accounts". This is because that the creation of Business firm Depository financial institution/ Bank Accounts in Due south/iv HANA has been split between customizing and Chief Data activities.

Configuration and testing will be shared in this mail.

While referring to an S/four HANA environment, the discussion "Southward/4" volition be used, and for a non-Southward/4, "ECC".

Main transactions in Due south/4

Transaction FI12 or FI12_HBANK
Transaction NWBC + Tool "Import and Export Bank Accounts"

Previous transactions in ECC

Transaction FI12

Screens in transaction FI12

(S/4 organisation on the LEFT | ECC on the RIGHT)

Creating a House Bank remained the same. The change is in the creation of a Depository financial institution Account:

Only visualization in S/four. Creation via Fiori or NetWeaver/WebDynpro.

WebDynpros – create Banking company Account / maintain Bank Account

As a upshot, Business firm Banks in S/4 are inside a Ship Asking but not the Depository financial institution Accounts, which are actress steps in comparing to the process in ECC.

Screens in transaction FI12_HBANK

Transaction FI12_HBANK has a mandatory selection of Company Code and no option to display Bank Accounts.

---

Business/ general context

From the introduction of S/4, the cosmos of Bank Accounts is:

a) a Master Data activity no longer transportable
b) only possible via the Fiori app "Manage Banks" or WebDynpro with the same name. Transaction FI12 is only for visualization.

Therefore in case of massive migrations from an ECC to an S/4 organization, and without the possibility of using an LSMW or a batch recording considering the activeness being based on Fiori/ WebDynpro, an option such equally the tool"Import and Export Bank Accounts" becomes useful.

---

Configuration steps

Main customizing activities

SPRO path:

one. Define Basic Settings

Financial Supply Concatenation Management > Greenbacks and Liquidity Management > General Settings > Define Basic Settings

Bank Acct Revision as "01 Actuate Directly".

Generally speaking:
01 Activate Directly = direct creation of Bank Account
02 Dual Control = i user creates, another approves
03 Workflow = one user creates, a corresponding user approves

2. Define Number Ranges for Alter Requests

Financial Supply Chain Management > Cash and Liquidity Management > Bank Account Management > Ascertain Number Ranges for Modify Requests

3. Define Number Ranges for Bank Business relationship Technical IDs

Financial Supply Chain Management > Cash and Liquidity Management > Depository financial institution Business relationship Management > Define Number Ranges for Banking company Account Technical IDs

This technical ID is later used inside table FCLM_BAM_AMD (table in S/4) – Bank Account Master Data and also visible in sure Fiori apps such as "Manage Bank Accounts" for tracking purposes.

4. Assign Number Ranges

Financial Supply Chain Management > Cash and Liquidity Management > Banking concern Account Management > Assign Number Ranges

Assign the number range to exist used for Change Requests and Bank Account Technical ID.

5. Define Settings for Banking company Account Master Information

Financial Supply Concatenation Management > Cash and Liquidity Management > Depository financial institution Account Management > Define Settings for Bank Business relationship Master Data

No changes from standard. Relevant since the field "Account Blazon" is required while creating Banking company Accounts.

Boosted customizing checks

a) Define ICF Services | Activate ICF Services

SAP NetWeaver > UI Technologies > SAP Fiori > Initial Setup > Initial Launchpad Configuration > Service Maintenance of Internet Communication Framework (ICF)

Transaction SICF

Check that these 3 ICF services are active:

• WDA_FCLM_BAM_ACC_MASTER
• WDA_FCLM_BAM_HIERARCHY
• WDA_FCLM_UPLOAD_DOWNLOAD

To activate a service, printing right click on it and and then "activate service":

Case inactive vs active ICF

b) Check user roles

Transaction SU01

The user should take the part 'SAP_SFIN_CASH_MANAGER' assigned that will let the access to the needed WebDynpro in transaction NWBC.

c) Microsoft Excel > Enable Developer tab

Inside Microsoft Excel: choose 'File' > 'Options' > 'Customize Ribbon' > 'Developer'

The tab 'Programmer' appears:

---

Testing important of Bank Accounts

1. Create Firm Banking company – Transaction FI12 or FI12_HBANK

Information coming from transaction FI12 / table T012 + T012D from the legacy arrangement. The Bank Account that will be created via the import tool has a House Bank that should be ready in South/4.

two. Download template for Bank Business relationship upload – Transaction NWBC

Transaction NWBC to launch the NetWeaver Business organization Customer.

Select office 'SAP_SFIN_CASH_MANAGER':

Depository financial institution Business relationship Direction > Tool > Import and Export Banking concern Accounts > Download XML Spreadsheet Template

Chief tabs in the Excel are 'General And Additional Data' which the information in table FCLM_BAM_AMD and 'Connectivity Path' working as the link betwixt the House Bank and the Depository financial institution Account nether creation.

3. Upload file – Transaction NWBC

Consummate the tab 'General And Boosted Data' with the data from the Bank Account from transaction FI12 or table T012K in ECC.

All values, including engagement fields, should accept the format "General".

Later, complete the tab "Connectivity Path" which lines are associated to the previous tab via the field "Technical ID" (not to confuse this field with the Technical ID within table FCLM_BAM_AMD. In this case, it is only used inside the file to connect records)

Export the file.

Dorsum in transaction NWBC, select the file for upload.

In this example, a test run upload is performed via 'Import with Test Run'.

So, a real run upload is performed via 'Import'.

Results are visible inside S/iv.

---

Comments

• Every bit mentioned above, all fields filled should have the format "General" (including dates)
• Practice not delete rows inside the template file. Delete or replace values. Copy and pasting via "Paste Values" and not direct paste. These principles are the aforementioned every bit when using transaction LTMC – SAP Migration Cockpit.
• Potential errors:

a) "Invalid file. Employ the downloaded template or enhanced template."

A row was deleted. A value was copied from another file without "Paste Value".

          b) "403 Forbidden " while trying to access the tool

Missing configuration in transaction SICF. Data under "Additional customizing checks > a) Define ICF Services | Activate ICF Services" in this blog.

          c) No results in S/4 fifty-fifty that the upload was successful

Both tab "General And Additional Information" + "Connectivity Path" should be filled. Otherwise, no real results will appear in S/four even that the tool is confirming the upload as successful.

Thank you for your time. Please feel free to comment and add any information or impressions you might have.

Cristian Cafure

---

Useful links

• SAP OSS notes

https://launchpad.support.sap.com/#/notes/2111290

https://launchpad.support.sap.com/#/notes/2437574

• SAP help

https://assistance.sap.com/saphelp_sfin200/helpdata/en/3e/99cf54e81e6374e10000000a44538d/content.htm?no_cache=true

quinthantivane.blogspot.com

Source: https://blogs.sap.com/2019/05/13/s4-hana-finance-bank-account-import-to-s4-transaction-fi12_hbank-nbwc-import-and-export-bank-accounts/

Bagikan Artikel ini