LSTAR_CREATE
LARU
Adjusted Scope
LARU
20250614
LARU
SLO
CO - Activity type
S4CORE 108 - Adjusted Scope - 05.09.2025
A4H / 100
E
15
#BFBFBF
14385
18960
120
120
0
False
False
| Introduction to Data Migration Templates |
| Version S4CORE 108 - Adjusted 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: CO - Activity type |
| Version S4CORE 108 - Adjusted Scope - 05.09.2025 © Copyright SAP SE. All rights reserved. |
|
| Sheet Name |
Group Name |
Field Description |
Importance |
Type |
Length |
Decimal |
SAP Structure |
SAP Field |
| Activity Master (mandatory) |
|
Main data |
Controlling Area |
mandatory for sheet |
Text |
80 |
|
S_CSLA |
KOKRS |
| Activity Type |
mandatory for sheet |
Text |
80 |
|
S_CSLA |
LSTAR |
| Valid-from Date |
mandatory for sheet |
Date |
|
|
S_CSLA |
DATAB |
| Valid-to Date |
mandatory for sheet |
Date |
|
|
S_CSLA |
DATBI |
| Basic data |
Language in Which Texts Are Saved |
|
Text |
80 |
|
S_CSLA |
LANGU |
| Name |
mandatory for sheet |
Text |
20 |
|
S_CSLA |
NAME |
| Description |
|
Text |
40 |
|
S_CSLA |
LTEXT |
| Activity Unit (ISO Format) |
mandatory for sheet |
Text |
3 |
|
S_CSLA |
LEINH_ISO |
| Activity Type Category |
mandatory for sheet |
Text |
80 |
|
S_CSLA |
LATYP |
| Variant Activity Type Category |
|
Text |
80 |
|
S_CSLA |
LATYPI |
| Valid Cost Center Categories |
mandatory for sheet |
Text |
8 |
|
S_CSLA |
KSTTY |
| Output |
Output Unit (ISO Format) |
|
Text |
3 |
|
S_CSLA |
AUSEH_ISO |
| Output Factor |
|
Number |
5 |
2 |
S_CSLA |
AUSFK |
| Basic data |
Allocation Cost Element |
|
Text |
10 |
|
S_CSLA |
VKSTA |
| Indiactors |
Lock Indicator |
|
Text |
1 |
|
S_CSLA |
SPRKZ |
| Predistribution of Fixed Costs |
|
Text |
1 |
|
S_CSLA |
FIXVO |
| Price Indicator |
|
Text |
3 |
|
S_CSLA |
TARKZ |
| Price Calc. w. Period-Based Avg. Prices |
|
Text |
1 |
|
S_CSLA |
YRATE |
| Actual Price Indicator |
|
Text |
3 |
|
S_CSLA |
TARKZ_I |
| Actual Quantity Set |
|
Text |
1 |
|
S_CSLA |
MANIST |
| Plan Quantity Set |
|
Text |
1 |
|
S_CSLA |
MANPLAN |
99
9
600
600
9
4
4
2
3
2
2
True
True
|
Source Data for Migration Object: CO - Activity type
|
|
Version S4CORE 108 - Adjusted Scope - 05.09.2025 © Copyright SAP SE. All rights reserved.
|
|
|
S_CSLA
|
|
|
|
|
| KOKRS |
LSTAR |
DATAB |
DATBI |
LANGU |
NAME |
LTEXT |
LEINH_ISO |
LATYP |
LATYPI |
KSTTY |
AUSEH_ISO |
AUSFK |
VKSTA |
SPRKZ |
FIXVO |
TARKZ |
YRATE |
TARKZ_I |
MANIST |
MANPLAN |
| ETE;80;0;C;80;0 |
ETE;80;0;C;80;0 |
EDA;8;0;D;8;0 |
EDA;8;0;D;8;0 |
ETE;80;0;C;80;0 |
ETE;20;0;C;20;0 |
ETE;40;0;C;40;0 |
ETE;3;0;C;3;0 |
ETE;80;0;C;80;0 |
ETE;80;0;C;80;0 |
ETE;8;0;C;8;0 |
ETE;3;0;C;3;0 |
ENU;5;2;P;5;2 |
ETE;10;0;C;10;0 |
ETE;1;0;C;1;0 |
ETE;1;0;C;1;0 |
ETE;3;0;C;3;0 |
ETE;1;0;C;1;0 |
ETE;3;0;C;3;0 |
ETE;1;0;C;1;0 |
ETE;1;0;C;1;0 |
| Main data |
Basic data |
Output |
Basic data |
Indiactors |
| Controlling Area*
The controlling area is the highest organizational unit in Controlling.
Type: Text
Length: 80 |
Activity Type*
Activity types describe the activity produced by a cost center and are measured in units of time or quantity.
Type: Text
Length: 80 |
Valid-from Date*
When you create an object, the beginning date to which object is valid is defined here.
Type: Date |
Valid-to Date*
When you create an object, you use the ending date to define as of when the object is valid.
Type: Date |
Language in Which Texts Are Saved
Language in which activity type texts are saved. If the language is not filled, logon language is used as default to save the activity type text.
Type: Text
Length: 80 |
Name*
Name of the object.
Type: Text
Length: 20 |
Description
The activity type description is used for online displays and evaluations which have sufficient space.
Type: Text
Length: 40 |
Activity Unit (ISO Format)*
The activity unit is either the time or quantity unit used to post the consumed activity quantities.
Type: Text
Length: 3 |
Activity Type Category*
You can save a default value in the master data for an activity type or a business process for allocatable activity type categories or allocation categories (category 1, 2 or 3).
You can change the default value within planning to a different allocatable activity type category or allocation category if you are planning for the first time.
Type: Text
Length: 80 |
Variant Activity Type Category
Indicator determining the method of actual activity allocation.
•Activity type category 1 (Manual entry, manual allocation)
•Activity type category 2 (Indirect calculation, indirect allocation)
•Activity type category 3 (Manual entry, indirect allocation)
•Activity type category 4 (Manual entry, no allocation)
•Activity type category 5 (Calculation and allocation via target=actual activity allocation)
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 80 |
Valid Cost Center Categories*
Indicator determining for which cost center types an activity type is allowed for planning and as a sender in internal activity allocation.
Example:
• Activity type: PCC
• Cost center types: P, S
If you enter "PS" in this field, the activity type can be planned only for cost centers of types P (production cost center) and S (service cost center) and can be drawn upon for use in actual activity allocation.
Type: Text
Length: 8 |
Output Unit (ISO Format)
Unit of measure for measuring the output of an activity type or business process (unit of alternative output).
An alternative output unit can be specified if the output of the activity type or business process is measured in a unit different to the one specified for the activity quantity.
You can also use the alternative output unit with Direct Internal Activity Allocation and when you create cycles (Indirect Internal Activity Allocation).
Type: Text
Length: 3 |
Output Factor
Factor describing the relationship between activity quantity and output quantity, expressed by the formula:
- Output quantity = Activity quantity * Output factor
In planning you can calculate the output quantity from the activity quantity and output factor. In the planning transaction, choose "Edit -> Activity -> Output".
Type: Number
Length: 5
Decimal: 2 |
Allocation Cost Element
Please note: Leading zeros must be supplied in the migration template, for example 0094310000.
The allocation cost element is a secondary cost element, under which the activity type or business process is allocated. It is mandatory to fill the value if the activity type category is used.
1. Manual entry, manual allocation
2. Indirect determination, indirect allocation
3. Manual entry, indirect allocation
Type: Text
Length: 10 |
Lock Indicator
Indicator determining whether an activity type is locked for activity input planning.
If the indicator is active, the affected activity type cannot be included.
Type: Text
Length: 1 |
Predistribution of Fixed Costs
Indicator for allowing the activity type or business process to be used in fixed cost predistribution.
You can store a default value in the master data of an activity type or a business process.
You can overwrite the default value within planning if you are planning for the first time.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 1 |
Price Indicator
Plan price indicator is showing how the system calculates the price of a business process or activity type for a cost center.
You can enter "001", "002" or "003". If your input is "004", you have selected "Purely iterative Prices" indicator.
Note: If you do not set a price indicator, the system uses the plan price.
Note: For "001" or "002" the system calculates new prices when determining the plan prices.
Type: Text
Length: 3 |
Price Calc. w. Period-Based Avg. Prices
Indicator determining that activity prices for cost centers/activity types remain constant for the entire fiscal year.
You can store a default value in the master data of an activity type or a business process.
You can overwrite the default value within planning if you are planning for the first time.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 1 |
Actual Price Indicator
Indicator: Actual Allocation Price
For actual allocation you can specify an indicator that varies from the plan, "005" and "006".
The actual price indicator can also have the value "008". This occurs when you select the "Purely iterative price" indicator in the version maintenance of customizing.
Type: Text
Length: 3 |
Actual Quantity Set
If this indicator is set, you must post a manual quantity, in addition to the quantity with which the object is credited. This makes sense especially when the quantity leading to the credit of the object is to be determined indirectly, but the actual quantity from the sender view is already known.
You can store a default value in the master data of an activity type or a business process.
You can overwrite the default value within planning if you are planning for the first time.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 1 |
Plan Quantity Set
X - Set
' ' - Not set
If you set this indicator, the planned activity quantity is not changed by plan reconciliation, even if planning is not to be reconciled for the object.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 1 |
9
600
600
51
8
8
4
4
0
3
1
2
0
7
0
False
False