BANK_2
LARU
Standard Scope
LARU
20250614
LARU
SLO
Bank
S4CORE 108 - Standard Scope - 05.09.2025
A4H / 100
E
15
#BFBFBF
14385
18960
120
120
0
False
False
| Introduction to Data Migration Templates |
| Version S4CORE 108 - Standard Scope - 05.09.2025 © Copyright SAP SE. All rights reserved. |
|
| | | |
|
Overview
| |
|
| |
|
A migration template (Microsoft Excel XML Spreadsheet 2003 file)
consists of different sheets which are visible at the bottom of the
migration template. You use the different sheets to specify the data
that belongs to different data structures. For example the migration
template for the migration object 'Product', contains a sheet for basic
data, a sheet for plant data, and so on. Some sheets are mandatory, and
some are optional.
| |
|
A migration template is based on the active view of the relevant
migration object. You can find information about the active view in the
Microsoft Excel XML file. In the file, navigate to File ->
Info. You can find the active view name under Properties
-> Tags.
| |
|
| |
|
Prerequisites
| |
|
In the Microsoft Excel XML Spreadsheet 2003 file, navigate to 'File' ->
'Options' -> 'Advanced'. Under the option 'When calculating this
workbook:', ensure that the option 'Set precision as displayed' is
selected.
| |
|
Information about File Sizes
| |
|
SAP S/4HANA Cloud
| |
|
If you are migrating data to SAP S/4HANA Cloud, the default size limit
for each uploaded XML file is 100MB. If required, you can zip several
files together. Note that the combined size of all the XML files you
want to add to the zip file must not exceed 160MB. The limit for zip
file is still 100MB.
| |
|
SAP S/4HANA On-Premise
| |
|
If you are migrating data to SAP S/4HANA, the default size limit for
each uploaded XML file is 100MB.
| |
|
You can increase the size limit for each uploaded XML file to 160MB by
changing the system parameter (icm/HTTP/max_request_size_KB). If
required, you can zip several files together. Note that the combined
size of all the XML files you want to add to the zip file must not
exceed 160MB. The limit for the zip file is still 160 MB with the
adjusted system parameter.
| |
|
The Field List Sheet
| |
|
The 'Field List' sheet is one of the first sheets in the migration
template. You use this sheet to get an overview of the expected data in
one central location.
| |
|
It contains information about the mandatory and optional sheets, as well
as detailed information for each sheet (for example the expected data
type and length for the fields in each sheet).
| |
|
On the 'Field List' sheet, you can view the following information for
each field in the migration template:
| |
|
• | The name of the sheet, and whether it is mandatory or optional. Only
mandatory sheets have the suffix 'Mandatory', for example 'Basic Data
(Mandatory)'. All other sheets are optional.
| |
|
| |
|
Note:
| |
|
You can quickly get an overview of the mandatory and optional sheets by
looking at the color of the sheet names at the bottom of the migration
template. The name of the mandatory sheets have the color orange, while
the optional sheets have the color blue.
| |
|
• | The group name for the fields in a sheet.
| |
|
• | The individual fields in each sheet, as well as whether fields are
mandatory for a sheet.
| |
|
• | Information about the expected format of the individual fields, for
example the data type and length.
| |
|
| |
|
Note:
| |
|
In the field list sheet, certain technical information about the fields
is hidden by default. The columns 'SAP Structure' and 'SAP Field'
(columns 8 and 9) are hidden by default. The column 'SAP Structure' is
the technical name of the structure that the field belongs to. The
column 'SAP Field' is the technical name of the field. To unhide these
columns, select the columns adjacent to either side of the columns that
you want to unhide. Right-click your selection, and choose 'Unhide'.
| |
|
If you want to extract data from SAP ERP, the technical name of
structure and the technical name of the field often corresponds to the
SAP ERP table name and field name. Also, the SAP Release Note (2568909)
for SAP S/4HANA Cloud data migration content uses the technical names of
the structures and fields.
| |
|
| |
|
Working with Sheets
| |
|
For each migration template, you need to specify data for the mandatory
sheets, and for the optional sheets that are relevant for your project:
| |
|
• | Mandatory sheets (orange)
| |
|
Mandatory sheets represent the minimum set of data you must provide for
data migration. Fill in all mandatory fields.
| |
|
• | Optional sheets (blue)
| |
|
Use optional sheets depending on your migration scope and available
legacy data.
| |
|
| |
|
Viewing Additional Information for Each Column
| |
|
In row 8, you can view the field names in SAP S/4HANA, as well as
additional information such as the expected format (for example the data
type and length). Note that you must expand the row to view this
additional information.
| |
|
Some fields are mandatory, and some are optional. The wildcard character
(‘*’) beside the name of a field indicates that the field is mandatory.
| |
|
| |
|
Note:
| |
|
Although an optional sheet may contain mandatory columns, if the sheet
is not relevant for your project, there is no need to fill the mandatory
columns in the sheet with data.
| |
|
| |
|
Note:
| |
|
Rows 4, 5, and 6 are hidden by default. Row 4 is the technical name of
the structure (corresponds to the sheet name). Row 5 is the technical
name of the field (corresponds to row 8 - the field description). Row 6
contains technical information such as the data type and length.
| |
|
To unhide these rows, select the rows adjacent to either side of the
rows that you want to unhide. Right-click your selection, and choose
'Unhide'.
| |
|
Working with Different Data Types
| |
|
You can view the data type for a field in row 8 (see 'Viewing Additional
Information for Each Column' above). Depending on the field, one of the
following data types may be required:
| |
|
• | Text
| |
|
Letters, numbers, and special characters are permitted. In the SAP
S/4HANA migration cockpit, you can map the values of certain fields with
the data type text (usually those fields with Length: 80) to their
correct SAP S/4HANA target values. You can do this value mapping in the
SAP S/4HANA migration cockpit when you start the transfer (in the step
'Convert Values').
| |
|
• | Number
| |
|
Enter numbers with decimals in the relevant country-specific format, for
example 12.34 (United States) or 12,34 (Germany). For fields with
decimals, the declared length includes decimals (if required), for
example if the information for the column states: Length: 8, Decimals:
3, then a number such as 12345.678 is permitted. Note that decimal
places are not mandatory. In this example, you can specify a whole
number up to length 8 without decimal places, for example ‘1’. This
number would be set to ‘1.000’ internally. For negative numbers, ensure
that a minus sign ('-') directly precedes the number, for example
'-100'. Note that currencies with more than 3 decimal places are not
supported.
| |
|
Note that the maximum field length supported by Microsoft Excel is 15
digits (including decimals). If you have longer numbers, use the option
for transferring data to S/4HANA using staging tables.
| |
|
• | Date
| |
|
Enter the date in your country-specific format, for example 12/31/1998
(United States) or 31.12.1998 (Germany). Note that Microsoft Excel
automatically recognizes different date formats and transforms them
automatically to the correct XML format.
| |
|
• | Time
| |
|
Enter the time in the format HH:MM:SS, for example 02:52:40
| |
|
| |
|
Copying Data to a Sheet
| |
|
When copying data to a sheet from Microsoft Excel, always right-click
the relevant cell and choose the paste option 'Values (V)'. Avoid
pasting data that includes formatting and formulas into the migration
template, as this will corrupt the structure of the XML migration
template.
| |
|
| |
|
Using the Find and Replace Function
| |
|
Do not use the Microsoft Excel function 'Find and Replace'. If you
change data by using this function, you may also unintentionally change
the field names and corrupt the structure of the XML migration template.
| |
|
| |
|
Saving the Migration Template
| |
|
Ensure that you only save the migration template as a Microsoft Excel
XML Spreadsheet 2003 file. Other file types are not supported by the SAP
S/4HANA migration cockpit.
| |
|
| |
|
Important Information
| |
|
| |
|
Do not make any changes to the structure of the migration template,
specifically:
| |
|
• | Do not delete, rename or change the order of any sheet in the migration
template.
| |
|
• | Do not change the formatting of any cells.
| |
|
• | Do not use formulas.
| |
|
• | Do not hide, remove, or change the order of any of the columns in the
migration template.
| |
|
| |
|
Note:
| |
|
Any changes to the sheets will result in a corrupted XML structure. Such
modified migration templates are not supported by the SAP S/4HANA
migration cockpit.
| |
|
| |
| | | |
99
9
600
600
9
3
3
2
3
2
2
True
True
| Field List for Migration Object: Bank |
| Version S4CORE 108 - Standard Scope - 05.09.2025 © Copyright SAP SE. All rights reserved. |
|
| Sheet Name |
Group Name |
Field Description |
Importance |
Type |
Length |
Decimal |
SAP Structure |
SAP Field |
| Bank Master (mandatory) |
|
Key |
Bank Country/Region Key |
mandatory for sheet |
Text |
80 |
|
S_BNKA |
BANKS |
| Bank Key |
mandatory for sheet |
Text |
80 |
|
S_BNKA |
BANKL |
| Address |
Name of Bank |
mandatory for sheet |
Text |
60 |
|
S_BNKA |
BANKA |
| Region (State, Province, Country) |
|
Text |
80 |
|
S_BNKA |
PROVZ |
| House Number and Street |
|
Text |
35 |
|
S_BNKA |
STRAS |
| City |
|
Text |
35 |
|
S_BNKA |
ORT01 |
| Bank Branch |
|
Text |
40 |
|
S_BNKA |
BRNCH |
| Control Data |
SWIFT Code for International Payments |
|
Text |
11 |
|
S_BNKA |
SWIFT |
| Post Office Bank Current Account |
|
Text |
1 |
|
S_BNKA |
XPGRO |
| Bank Number |
|
Text |
15 |
|
S_BNKA |
BNKLZ |
| Bank Group (Bank Network) |
|
Text |
2 |
|
S_BNKA |
BGRUP |
| Control Indicator |
Do Not Overwrite Existing Data |
|
Text |
1 |
|
S_BNKA |
ISNOTOVERWRITE |
99
9
600
600
9
4
4
2
3
2
2
True
True
|
Source Data for Migration Object: Bank
|
|
Version S4CORE 108 - Standard Scope - 05.09.2025 © Copyright SAP SE. All rights reserved.
|
|
|
S_BNKA
|
|
|
|
|
| BANKS |
BANKL |
BANKA |
PROVZ |
STRAS |
ORT01 |
BRNCH |
SWIFT |
XPGRO |
BNKLZ |
BGRUP |
ISNOTOVERWRITE |
| ETE;80;0;C;80;0 |
ETE;80;0;C;80;0 |
ETE;60;0;C;60;0 |
ETE;80;0;C;80;0 |
ETE;35;0;C;35;0 |
ETE;35;0;C;35;0 |
ETE;40;0;C;40;0 |
ETE;11;0;C;11;0 |
ETE;1;0;C;1;0 |
ETE;15;0;C;15;0 |
ETE;2;0;C;2;0 |
ETE;1;0;C;1;0 |
| Key |
Address |
Control Data |
Control Indicator |
| Bank Country/Region Key*
Identifies the country/region in which the bank is located.
The country/region key defines the rules according to which bank data, such as the bank and account number, is to be validated.
Type: Text
Length: 80 |
Bank Key*
In this field, you specify the bank key under which bank data from the respective country/region is stored.
The length of bank key is decided on bank country/region. For example, if bank country/region is DE, length of bank key must have length 8; if bank country/region is IT, length of bank key must have length 10.
Type: Text
Length: 80 |
Name of Bank*
The name under which the bank operates.
Type: Text
Length: 60 |
Region (State, Province, Country)
In some countries/regions, the region forms part of the address. The meaning depends on the country/region.
Type: Text
Length: 80 |
House Number and Street
Street and house number as part of the address.
Type: Text
Length: 35 |
City
Name of the city as a part of the address.
Type: Text
Length: 35 |
Bank Branch
This field contains the branch name of the financial institution.
Type: Text
Length: 40 |
SWIFT Code for International Payments
Uniquely identifies a bank throughout the world. SWIFT stands for Society for Worldwide Interbank Financial Telecommunication. BIC stands for Bank Identifier Code.
Type: Text
Length: 11 |
Post Office Bank Current Account
This indicator causes the account to be treated as a post office bank current account.
Type: Text
Length: 1 |
Bank Number
This field contains the bank number or the bank code.
Check value BNKEY in table T005 to decide if the column is filled.
1. Bank number
2. Obsolete
3. Assign internally
4. Assign externally
It makes no sense for customer to fill the value for bank number if bnkey is not '4'.
Type: Text
Length: 15 |
Bank Group (Bank Network)
Serves to classify banks in such a way that payment transactions within a group are processed as quickly as possible (bank chain optimization).
Type: Text
Length: 2 |
Do Not Overwrite Existing Data
This is an indicator field to determine whether or not to overwrite an existing bank.
If the indicator field is empty, the system overwrites an existing bank. If you don’t want to overwrite an existing bank, enter X.
Note:
If you enter X and a bank exists in the system, an error message is issued.
Type: Text
Length: 1 |
9
600
600
51
8
8
2
2
0
3
1
2
0
7
0
False
False