| Status |
| ||||||||
| OwnerSoumen Laru | |||||||||
| Stakeholders |
Purpose
The purpose of this document is to define the conversion approach of activity types into S4HANA
The document details out the field list, extraction criteria, scoping, mapping of activity type object
Conversion Scope
Activity Types which will be listed as part of scope list with new numbering will be in scope of migration.
List of source systems and approximate number of recordsSource Approx No. of Records
No. of Records
Additional Information
Multi-language Requirement
Document Management
Legal Requirement
Special Requirements
Target Design
The technical design of the target for this conversion approach.
Table
Field
Data Element
Field Description
Data Type
Length (Decimals)
Requirement
Data Cleansing
ID
Criticality
Error Message/Report Description
Rule
Output
Source System
1.
Can load, but business process will fail
Lock any Activity Type not being used for last 5 years
TBD
Report
PF2 / PI2 / WP2
Conversion Process
The high-level process is represented by the diagram below:
Data Privacy and Sensitivity
Extraction
Extract data from a source into . There are 2 possibilities:
- The data exists. connects to the source and loads the data into . There are 3 methods:
- Perform full data extraction from relevant tables in the source system(s).
- Perform extraction through the application layer.
- Only if ; cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
- The data does not exist (or cannot be converted from its current state). The data is manually collected by the business directly in . This is to be conducted using DCT (Data Collection Template) in
The agreed Relevancy criteria is applied to the extracted records to identify the records that are applicable for the Target loads
Extraction Run Sheet
Req #
Requirement description
Team responsible
1.
Ensure source tables CEPC and CEPCT are extracted in tool according to the agreed cut-off date in the project plan
Ensure DCT is collected for the Activity Types based on the collection template
Data team
2.
Perform preliminary completeness check documented in section 5.2.8.1.1
Data team
3.
Raise issues as defects if Req # 1 to 2 are not met
Data team
4.
Repeat Req # 1 to 3 if required
Data team
5.
Report extraction result to person in charge of APOI conversion
Data team
Selection Screen
Data Collection Template (DCT)
Target Ready Data Collection Template will be created for data with exception of some fields which require transformation as mentioned in the transformation rule.DCT Rules
Field Name | Field description | Rule |
CEPC-PRCTR | Activity Type | Business to enter content as per data type and length permitted |
Suggestion to add:
Decimal validation - Check table TCURX for the document currency key and if Decimals (TCURX-CURRDEC) is ‘0’, validate that no decimal value is populated.
Extraction Dependencies
Item # | Step description | Team responsible |
1. | Any period / year end close activities have been fully completed | Business |
2. | Reconciliation for intercompany payables have been completed, and adjustment made in legacy SAP system | Business |
3. | Reconciliation of migrated Purchase Order is completed before the extraction of Accounts Payable Open Items | Business and Data |
Transformation
The Target fields are mapped to the applicable ECC field that will be its source, this is a 3-way activity involving the Business, Functional team and Data team. This identifies the transformation activity required to allow to make the data Target ready:
- Perform value mapping and data transformation rules.
- ECC values are mapped to the to-be values (this could include a default value)
- Values are transformed according to the rules defined in
- Prepare target-ready data in the structure and format that is required for loading via prescribed Load Tool. This step also produces the load data ready for business to perform Pre-load Data Validation
Transformation Run Sheet
Item # | Step description | Team responsible |
1. | Ensure all the fields that require value mapping, as stipulated Mapping tables, have the latest signed-off mapping files imported into toolMigrate. | Data team |
2. | In tool, select the Trial Balance object PY. | Data team |
3. | Go to Process Area Launch and Process the Object - Trial Balance object - R4 Trial Balance PY. | Data team |
4. | Launch the Objects to execute transformation. | Data team |
5. | Monitor the transformation progress and ensure performance and completion is within allowed timeframe | Data team |
6. | Generate Pre-Load reports . | Data team |
7. | Generate data load count. | Data team |
8. | Log errors as defects, if any and address resolutions. Close defects. | Data team |
9. | Re-transform and re-validate the Pre-load reports if necessary. | Data team |
10. | Validate the transformed file as part of pre-load validation, raise data defects or provide the pre-load sign-off. | Business |
11. | Analyse and resolve any pre-load defects logged by business. | Data team |
12. | Repeat steps 6 to 11 if necessary | Data team |
13. | Proceed to pre-load validations | Data team |
Transformation Rules
Rule #
Source system
Source Table
Source Field
Source description
Target system
Target Table
Target Field
Target description
Transformation logic
The controlling area is the highest organizational unit in Controlling.
Type: Text
Length: 80
The controlling area is the highest organizational unit in Controlling.
Type: Text
Length: 80
Key which together with the controlling area uniquely identifies a profit center.
Use
You can make an organizational assignment of a profit center to a controlling object (an order, cost center,…). The system posts automatically on the profit center when you make a posting on controlling object (an order, cost center,…).
Type: Text
Length: 80
Key which together with the controlling area uniquely identifies a profit center.
Use
You can make an organizational assignment of a profit center to a controlling object (an order, cost center,…). The system posts automatically on the profit center when you make a posting on controlling object (an order, cost center,…).
Type: Text
Length: 80
When you create an object, the beginning date to which object is valid is defined here.
Type: Date
When you create an object, the beginning date to which object is valid is defined here.
Type: Date
When you create an object, you use the ending date to define as of when the object is valid.
Type: 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 profit center texts are saved. If the language is not filled, logon language is used as default to save the profit center text.
Type: Text
Length: 80
Language in which profit center texts are saved. If the language is not filled, logon language is used as default to save the profit center text.
Type: Text
Length: 80
General description of the object. The profit center name is used for online displays and evaluations that do not have enough space for the profit center description.
Type: Text
Length: 20
General description of the object. The profit center name is used for online displays and evaluations that do not have enough space for the profit center description.
Type: Text
Length: 20
A text that describes the profit center to which it refers in greater detail.
Type: Text
Length: 40
A text that describes the profit center to which it refers in greater detail.
Type: Text
Length: 40
Name of the person in charge of the profit center.
Type: Text
Length: 20
Name of the person in charge of the profit center.
Type: Text
Length: 20
In this field, you can enter the user ID of the person responsible for the profit center. This user ID is stored in the SAP user master record.
Type: Text
Length: 80
In this field, you can enter the user ID of the person responsible for the profit center. This user ID is stored in the SAP user master record.
Type: Text
Length: 80
Each profit center must be assigned to a node in the standard hierarchy for its controlling area. This ensures that the standard hierarchy contains all the profit centers in the controlling area.
Type: Text
Length: 12
Each profit center must be assigned to a node in the standard hierarchy for its controlling area. This ensures that the standard hierarchy contains all the profit centers in the controlling area.
Type: Text
Length: 12
This field contains the name of the department to which the profit center belongs.
Type: Text
Length: 12
This field contains the name of the department to which the profit center belongs.
Type: Text
Length: 12
Segment for Segmental Reporting.
Note: Field Segment must be filled with leading zeros if it is numeric data. Example: if the segment value is 9999, enter 0000009999 in the XML file.
Type: Text
Length: 10
Segment for Segmental Reporting.
Note: Field Segment must be filled with leading zeros if it is numeric data. Example: if the segment value is 9999, enter 0000009999 in the XML file.
Type: Text
Length: 10
Title for Address data.
Type: Text
Length: 15
Title for Address data.
Type: Text
Length: 15
Name 1 of the customer/supplier address.
Type: Text
Length: 35
Name 1 of the customer/supplier address.
Type: Text
Length: 35
Name 2 of the customer/supplier address.
Type: Text
Length: 35
Name 2 of the customer/supplier address.
Type: Text
Length: 35
Name 3 of the customer/supplier address.
Type: Text
Length: 35
Name 3 of the customer/supplier address.
Type: Text
Length: 35
Name 4 of the customer/supplier address.
Type: Text
Length: 35
Name 4 of the customer/supplier address.
Type: Text
Length: 35
Street and house number as part of the address.
Type: Text
Length: 35
Street and house number as part of the address.
Type: Text
Length: 35
Name of the city as a part of the address.
Type: Text
Length: 35
Name of the city as a part of the address.
Type: Text
Length: 35
Supplement to city name or district.
Use
The entry is appended to the city name with a hyphen by the automatic address formatting function.
(Exceptions: Germany, United Kingdom/Ireland and Japan)
Type: Text
Length: 35
Supplement to city name or district.
Use
The entry is appended to the city name with a hyphen by the automatic address formatting function.
(Exceptions: Germany, United Kingdom/Ireland and Japan)
Type: Text
Length: 35
The country/region key contains information which the system uses to check entries such as the length of the postal code or bank account number.
The two-character ISO code in accordance with ISO 3166, which is delivered by SAP as a default, is usually used.
Type: Text
Length: 80
The country/region key contains information which the system uses to check entries such as the length of the postal code or bank account number.
The two-character ISO code in accordance with ISO 3166, which is delivered by SAP as a default, is usually used.
Type: Text
Length: 80
Number of telebox for electronic mail.
Type: Text
Length: 15
Number of telebox for electronic mail.
Type: Text
Length: 15
First telephone number
Type: Text
Length: 16
First telephone number
Type: Text
Length: 16
Second telephone number for communication.
Type: Text
Length: 16
Second telephone number for communication.
Type: Text
Length: 16
Number under which a business partner's telefax machine can be reached.
Use
The number is used by the system if you send a message by telefax to your business partner from within an SAP transaction.
Type: Text
Length: 31
Number under which a business partner's telefax machine can be reached.
Use
The number is used by the system if you send a message by telefax to your business partner from within an SAP transaction.
Type: Text
Length: 31
Number under which a business partner's teletex machine can be reached.
Teletex is a service for the transmission of text and data. In comparison with a telex, however, the transmission times of teletex messages are shorter and the range of characters available is greater.
Use
The number is determined by the SAP system if you send a teletex message to your business partner from within an SAP transaction.
Type: Text
Length: 30
Number under which a business partner's teletex machine can be reached.
Teletex is a service for the transmission of text and data. In comparison with a telex, however, the transmission times of teletex messages are shorter and the range of characters available is greater.
Use
The number is determined by the SAP system if you send a teletex message to your business partner from within an SAP transaction.
Type: Text
Length: 30
Number under which the telex machine can be reached.
Teletex is a service for the transmission of text and data. In comparison with a telex, however, the transmission times of teletex messages are shorter and the range of characters available is greater.
Type: Text
Length: 30
Number under which the telex machine can be reached.
Teletex is a service for the transmission of text and data. In comparison with a telex, however, the transmission times of teletex messages are shorter and the range of characters available is greater.
Type: Text
Length: 30
Data communication line no.
Line number (telephone line). Dialing this number enables you to establish a link with another computer at a different location.
Type: Text
Length: 14
Data communication line no.
Line number (telephone line). Dialing this number enables you to establish a link with another computer at a different location.
Type: Text
Length: 14
Printer name for profit center
Type: Text
Length: 4
Printer name for profit center
Type: Text
Length: 4
Max. length of input must not exceed 15 digits.
The tax jurisdiction is used for determining the tax rate. It defines to which tax authorities you must pay your taxes. It is always the city to which the goods are supplied.
If Vertex is activated (esp. on US
. Activity types describe the activity produced in a cost centre within a controlling area. At SyWay, activity types are used to quantify the cost of the services that a department provides to other areas or to production orders, projects or activities in manufacturing, research and development, IT projects etc.
The scope of this conversion spec refers to the migration of Activity types into S/4HANA system.
Conversion Scope
The scope of this document covers the approach for creating a new Activity Types into S/4HANA following the MDS DD-FUN-050 Master Data Standard_1071-Activity Types, which will be listed as part of scope list with new numbering will be in scope of migration. This object's conversion from source to target is an approved DCT document. Therefore, relevancy rules are not applicable for this object as it uses DCT approach with full construct design.
List of source systems and approximate number of records. Note: Target records are expected to be lower after finalization of the design.
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
| PF2 | Activity Types | 8994 | S/4HANA | ~ 2570 ~ |
| WP2 | Activity Types | 1099 | S/4HANA | ~ 350 ~ |
Additional Information
Multi-language Requirement
Activity Types will primarily be managed in English. However, according to KDD055, this master data standard will be implemented in 4 core languages.
- English (EN)
- French (FR)
- Italian (IT)
- Chinese (ZN)
Note: Other language requirements were not finalized while developing this document, refer to Jira ID # PDM 604.
Document Management
N/A
Legal Requirement
N/A
Special Requirements
N/A
Target Design
The technical design of the target for this conversion approach.
Table | Field | Data Element | Field Description | Data Type | Length | Requirement R = Required : Mandatory field O = Optional: Not mandatory. If a value is entered it doesn't impact Business Process. C = Conditional: Not mandatory. If a value is entered it impacts Business Process or Reporting. |
| CSLA | KOKRS | KOKRS | Controlling Area | CHAR | 4 | R |
| CSLA | LSTAR | LSTAR | Activity Type | CHAR | 6 | R |
| CSLA | DATAB | DATAB | Valid-from Date | DATE | 8 | R |
| CSLA | DATBI | DATBI | Valid-to Date | DATE | 8 | R |
| CSLA | LANGU | LANGU | Language in Which Texts Are Saved | CHAR | 80 | O |
| CSLT | KTEXT | KTEXT | Name | CHAR | 20 | R |
| CSLT | LTEXT | LTEXT | Description | CHAR | 40 | R |
| CSLA | LEINH | LEINH | Activity Unit (ISO Format) | UNIT | 3 | R |
| CSLA | LATYP | LATYP | Activity Type Category | CHAR | 1 | R |
| CSLA | LATYPI | LATYPI | Variant Activity Type Category | CHAR | 1 | O |
| CSLA | KSTTY | KSTTY | Valid Cost Centre Categories | CHAR | 8 | R |
| CSLA | AUSEH | AUSEH | Output Unit (ISO Format) | UNIT | 3 | O |
| CSLA | AUSFK | AUSFK | Output Factor | DEC | 5 | O |
| CSLA | VKSTA | VKSTA | Allocation Cost Element | CHAR | 10 | C |
| CSLA | SPRKZ | SPRKZ | Lock Indicator | CHAR | 1 | O |
| CSLA | FIXVO | FIXVO | Predistribution of Fixed Costs | CHAR | 1 | O |
| CSLA | TARKZ | TARKZ | Price Indicator | CHAR | 3 | O |
| CSLA | YRATE | YRATE | Price Calc. w. Period-Based Avg. Prices | CHAR | 1 | O |
| CSLA | TARKZ_I | CO_TARKZ_I | Actual Price Indicator | CHAR | 3 | O |
| CSLA | MANIST | CO_MANIST | Actual Quantity Set | CHAR | 1 | O |
| CSLA | MANPLAN | CO_MANPLAN | Plan Quantity Set | CHAR | 1 | O |
Data Cleansing
Data Cleansing is not relevant for this object because the entire Activity types will be afresh designed in S/4HANA. If any cleansing is deemed necessary, it will be performed outside of the system, as a result, the cleansed Activity Types will be populated directly in the Data Collection Template (DCT).
ID | Criticality | Error Message/Report Description | Rule | Output | Source System |
N/A |
Conversion Process
Although source extraction is planned, no relevancy or extraction rules are implemented. The Data team will collect the new Activity Types manually in the DCT to support the To-Be design, and an ETL process will be followed to the Target loads.
Data Privacy and Sensitivity
N/AExtraction
Perform full data extraction from relevant tables in the source systems into Syniti Migrate. There will be no relevancy criteria is applied to the extracted records, The DCT is applicable for the Target loads.
- Syniti Migrate connects to the sources.
- An initial extract of the relevant Activity Types will be made available to assist business with any standardization.
Extraction Run Sheet
Req # | Requirement description | Team responsible |
1. | The new Activity Types will be collected using the Data Collection Template (DCT) | R2R Data Team |
Selection Screen
| Selection Ref Screen | Parameter Name | Selection Type | Requirement | Value to be entered/set |
|---|---|---|---|---|
| N/A |
Data Collection Template (DCT)
Target Ready Data Collection Template will be created for Activity Types with exception of some fields which require transformation as mentioned in the transformation rule.DCT - 1 for Activity Types with English language
Table & Field Name | Field description | Rule |
| CSLA - KOKRS | Controlling Area | Defaults to 'XXXX' (XXXX will be finalized after config item) |
| CSLA - LSTAR | Activity Types | |
| CSLA - DATAB | Valid-from Date | First Day of fiscal period when the activity type is created |
| CSLA - DATBI | Valid-to Date | Set to be '31.12.9999' |
| CSLA - LANGU | Language in Which Texts Are Saved | |
| CSLT - KTEXT | Name | |
| CSLT - LTEXT | Description | |
| CSLA - LEINH | Activity Unit (ISO Format) | |
| CSLA - LATYP | Activity Type Category | Set to be '3' |
| CSLA - LATYPI | Variant Activity Type Category | Set to be '2' |
| CSLA - KSTTY | Valid Cost Centre Categories | |
| CSLA - AUSEH | Output Unit (ISO Format) | |
| CSLA - AUSFK | Output Factor | |
| CSLA - VKSTA | Allocation Cost Element | Choose an appropriate secondary cost element, there will be a relationship of 1:1 in between the activity type and the secondary cost element |
| CSLA - SPRKZ | Lock Indicator | |
| CSLA - FIXVO | Predistribution of Fixed Costs | |
| CSLA - TARKZ | Price Indicator | Set to be '1' |
| CSLA - YRATE | Price Calc. w. Period-Based Avg. Prices | |
| CSLA - TARKZ_I | Actual Price Indicator | Set to be '5' |
| CSLA - MANIST | Actual Quantity Set | |
| CSLA - MANPLAN | Plan Quantity Set |
DCT - 2 for Activity Types that use a language other than English. Activity types with Descriptions will be collected in multiple languages, hence a separate DCT will be used
Field Name | Field description | Rule |
| CSLT-KOKRS | Controlling Area | Defaults to 'XXXX' (XXXX will be finalized after config item) |
| CSLT - LSTAR | Activity Types | |
| CSLT - SPRAS | Language Key | Input Language Key, ex: If Chinese, CN |
| CSLT-DATBI | Valid to | Set to be '31.12.9999' |
| CSLT - KTEXT | Name | Enter content as per data type and length permitted |
| CSLT - LTEXT | Description | Enter content as per data type and length permitted |
Extraction Dependencies
Item # | Step description | Team responsible |
N/A |
Transformation
To prepare the data for Target, the Target fields are mapped to the corresponding Legacy field (DCT will be the source for this object)
- Perform value mapping and data transformation rules.
- Legacy values are mapped to the to-be values (this could include a default value)
- Prepare target-ready data in the structure and format that is required for loading via prescribed Load Tool. This step also produces the load data ready for business to perform Pre-load Data Validation
Transformation Run Sheet
Item # | Step description | Team responsible |
1. | Obtain DCT Sign-off from Business | R2R Data Team |
2. | Generate Load Files | R2R Data Team |
3. | Monitor the transformation progress and ensure that performance and completion are within the allowed timelines | R2R Data Team |
4. | Review and Validate Error and Preload Reports | R2R Data Team |
5. | Log defects for any kind of errors and address resolution | R2R Data Team |
6. | Re-transform the pre-load files, validate and ready for load (This step is applicable If step 5 is active, else No) | R2R Data Team |
7. | Proceed for final loads | R2R Data Team |
Transformation Rules
| Rule # | Source system | Source Table | Source Field | Source description | Target system | Target Table | Target Field | Target description | Transformation logic |
| 1 | DCT | CSLA | KOKRS | Controlling Area | S/4HANA | CSLA | KOKRS | Controlling Area | Default to 'XXXX' |
| 2 | DCT | CSLA | LSTAR | Activity Type | S/4HANA | CSLA | LSTAR | Activity Type | Direct mapping from DCT |
| 3 | DCT | CSLA | DATAB | Valid-from Date | S/4HANA | CSLA | DATAB | Valid-from Date | Direct mapping from DCT |
| 4 | DCT | CSLA | DATBI | Valid-to Date | S/4HANA | CSLA | DATBI | Valid-to Date | Set to '31.12.9999' |
| 5 | DCT | CSLA | LANGU | Language in Which Texts Are Saved | S/4HANA | CSLA | LANGU | Language in Which Texts Are Saved | Direct mapping from DCT |
| 6 | DCT | CSLT | KTEXT | Name | S/4HANA | CSLT | NAME | Name | Direct mapping from DCT |
| 7 | DCT | CSLT | LTEXT | Description | S/4HANA | CSLT | LTEXT | Description | Direct mapping from DCT |
| 8 | DCT | CSLA | LEINH | Activity Unit (ISO Format) | S/4HANA | CSLA | LEINH | Activity Unit (ISO Format) | Direct mapping from DCT |
| 9 | DCT | CSLA | LATYP | Activity Type Category | S/4HANA | CSLA | LATYP | Activity Type Category | Direct mapping from DCT |
| 10 | DCT | CSLA | LATYPI | Variant Activity Type Category | S/4HANA | CSLA | LATYPI | Variant Activity Type Category | Direct mapping from DCT |
| 11 | DCT | CSLA | KSTTY | Valid Cost Center Categories | S/4HANA | CSLA | KSTTY | Valid Cost Center Categories | Direct mapping from DCT |
| 12 | DCT | CSLA | AUSEH | Output Unit (ISO Format) | S/4HANA | CSLA | AUSEH | Output Unit (ISO Format) | Direct mapping from DCT |
| 13 | DCT | CSLA | AUSFK | Output Factor | S/4HANA | CSLA | AUSFK | Output Factor | Direct mapping from DCT |
| 14 | DCT | CSLA | VKSTA | Allocation Cost Element | S/4HANA | CSLA | VKSTA | Allocation Cost Element | Direct mapping from DCT |
| 15 | DCT | CSLA | SPRKZ | Lock Indicator | S/4HANA | CSLA | SPRKZ | Lock Indicator | Direct mapping from DCT |
| 16 | DCT | CSLA | FIXVO | Redistribution of Fixed Costs | S/4HANA | CSLA | FIXVO | Redistribution of Fixed Costs | Direct mapping from DCT |
| 17 | DCT | CSLA | TARKZ | Price Indicator | S/4HANA | CSLA | TARKZ | Price Indicator | Direct mapping from DCT |
| 18 | DCT | CSLA | YRATE | Price Calc. w. Period-Based Avg. Prices | S/4HANA | CSLA | YRATE | Price Calc. w. Period-Based Avg. Prices | Direct mapping from DCT |
| 19 | DCT | CSLA | TARKZ_I | Actual Price Indicator | S/4HANA | CSLA | TARKZ_I | Actual Price Indicator | Direct mapping from DCT |
| 20 | DCT | CSLA | MANIST | Actual Quantity Set | S/4HANA | CSLA | MANIST | Actual Quantity Set | Direct mapping from DCT |
| 21 | DCT | CSLA | MANPLAN | Plan Quantity Set | S/4HANA | CSLA | MANPLAN | Plan Quantity Set | Direct mapping from DCT |
Transformation Mapping
Mapping Table Name | Mapping Table Description |
Activity Types | Old to New Activity Types |
Transformation Dependencies
List the steps that need to occur before transformation can commence| Item # | Step Description | Team Responsible |
|---|---|---|
| 1 | Ensure DCT completeness | R2R Data Team |
| 2 | Value Mappings are according to the target design in S/4HANA | R2R Data Team |
Pre-Load Validation
Project Team
Completeness
Task | Action |
| Verify Record Count | R2R Data Team to verify that the total number of relevant records from the DCT is equal to the total number of records in the Preload and Load Sheets. |
Accuracy
Task | Action |
| Conversion Accuracy | R2R Data Team to ensure that all fields listed below pass the checks:
|
| Review Error Reports | Review and correct the errors. Achieve a zero-error record count as much as possible. Raise defects for data remediated and requiring a correction in the source DCT. |
Business
Completeness
| Task | Action |
|---|---|
| Verify Record Count | Business Data Owner/s to verify that the total number of relevant records from the DCT is equal to the total number of records in the Preload and Load Sheets. |
Accuracy
| Task | Action |
|---|---|
| Conversion Accuracy | Business Data Owner/s to verify that all the data in the load table/file is accurate as per endorsed transformation / mapping rules (and signed-off DCT data). |
Load
Activity types will be migrated using the SAP tool 'Migration Cockpit', Object: Activity Type used for this specific import. Migration template is attached as a reference.
1071_Source data for CO - Activity type.xml
| View file | ||||
|---|---|---|---|---|
|
The load process includes:
- Execute the automated data load into target system using load tool i.e., SAP Migration Cockpit.
- Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation
Load Run Sheet
Item | Step description | Team responsible |
1 | Ensure Pre-load sign-offs are obtained | R2R Data team |
2 | Ensure the load tools are transported into the correct tool instance | R2R Data team |
3 | Go to <Load tool> | R2R Data team |
4 | Load 1 or 2 records for "Activity Types" to validate if data is loaded successfully without errors | R2R Data team |
5 | Proceed with full load if step 4 is successful and validated | R2R Data team |
6 | Validate few records loaded by accessing standard transactions or tables from S/4HNA E.g. KL03 or FIORI: Manage Activity Types | R2R Data team |
7 | Generate post load report if step 4 is validated | R2R Data team |
Load Phase and Dependencies
Pre-Cut over
Configuration
Item # | Configuration item |
1. | Controlling Area |
2. | Secondary Cost Elements |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
| 1067 | GL Account Operational COA (Incl. Secondary CE) |
Error Handling
Error type | Error description | Action taken |
Configuration | Invalid Secondary Cost Element System provides opportunity to review the incorrectly populated data and these need to be analysed and corrected | Consult Functional team to expedite and fix the error in the system |
Configuration | Invalid Cost Centre Categories System provides opportunity to review the incorrectly populated data and these need to be analysed and corrected | Consult Functional team to expedite and fix the error in the system |
Configuration | Invalid Activity Type Categories System provides opportunity to review the incorrectly populated data and these need to be analysed and corrected | Consult Functional team to expedite and fix the error in the system |
Post-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
Verify Count | R2R Data Team to verify the record count created in target S/4 HANA by accessing post load reports using standard reports from S/4 HANA. |
Verify Logs | Check if there is data that failed to load and perform the necessary actions (e.g. register as post load issue or attempt to load the record again, etc.). |
Accuracy
| Task | Action |
|---|---|
| Conversion Accuracy | Verify that the Activity Types in target S/4 HANA are loaded correctly via load program and validate post load reports using standard t.code KL03 / KL13 or database tables CSLA from S/4 HANA. |
Business
Completeness
| Task | Action |
|---|---|
Verify Count | Download Post Load Reports from load program and verify that the record count loaded in the target S/4 HANA is the same count as of the approved load file. |
Accuracy
| Task | Action |
|---|---|
| Spot checks | Business should choose some Activity Types and perform comprehensive check of the fields in S/4 HANA |
| Conversion Accuracy | Verify that the Activity Types in target S/4 HANA are loaded correctly via load program and validate post load reports using standard t.code KL03 / KL13 or database tables CSLA / CSLT from S/4 HANA |
Type: Text
Length: 15
Max. length of input must not exceed 15 digits.
The tax jurisdiction is used for determining the tax rate. It defines to which tax authorities you must pay your taxes. It is always the city to which the goods are supplied.
If Vertex is activated (esp. on US installations) the tax jurisdiction code will be determined by the business object's address. If the given postal code/Zip code is not accurate as possible, Vertex will determine more than one tax jurisdiction code for one record, the migration of this record will fail. You will then get the error message "No unique jurisdiction code can be determined".
Type: Text
Length: 15
PO Box for address.
Type: Text
Length: 10
PO Box for address.
Type: Text
Length: 10
This field contains the postal (zip) code for the house address (street and city).
Type: Text
Length: 10
This field contains the postal (zip) code for the house address (street and city).
Type: Text
Length: 10
Postal code needed to allocate the P.O. Box.
Use
This field is used for a country/region where:
- the postal code (zip code) used to send letters to a customer's/vendor's P.O. Box is different to that used to send letters to a customer's/vendor's company address.
- large companies have their own postal code and no P.O. Box.
Type: Text
Length: 10
Postal code needed to allocate the P.O. Box.
Use
This field is used for a country/region where:
- the postal code (zip code) used to send letters to a customer's/vendor's P.O. Box is different to that used to send letters to a customer's/vendor's company address.
- large companies have their own postal code and no P.O. Box.
Type: Text
Length: 10
In some countries/regions, the region forms part of the address. The meaning depends on the country/region.
Type: Text
Length: 80
In some countries/regions, the region forms part of the address. The meaning depends on the country/region.
Type: Text
Length: 80
You can use the lock indicator to lock a profit center for postings. The lock only applies to the selected time interval. If the profit center is assigned to an object that receives a posting, the system displays an error message and the data is not posted.
This is an indicator field. If the criterion is met, enter X. If not, leave the field empty.
Type: Text
Length: 1
You can use the lock indicator to lock a profit center for postings. The lock only applies to the selected time interval. If the profit center is assigned to an object that receives a posting, the system displays an error message and the data is not posted.
This is an indicator field. If the criterion is met, enter X. If not, leave the field empty.
Type: Text
Length: 1
Template for Formula Planning in Profit Centers
Contains functions, which are used to find plan values using formula planning.
A template is assigned to the profit centers for which it is to be valid, in master data maintenance. It can be used for more than one profit center.
Type: Text
Length: 10
Template for Formula Planning in Profit Centers
Contains functions, which are used to find plan values using formula planning.
A template is assigned to the profit centers for which it is to be valid, in master data maintenance. It can be used for more than one profit center.
Type: Text
Length: 10
Transformation Mapping
Mapping Table Name | Mapping Table Description |
Activity Type | Mapping of ECC Profit Center to target system value |
Person Responsible | Mapping of ECC Person Responsible to New Person Responsible |
User ID | Mapping of ECC User ID |
Hierarchy Group | Mapping of ECC Hierarchy Group to Hierarchy Group |
Transformation Dependencies
List the steps that need to occur before transformation can commenceEnsure Activity Type hierarchies are loaded into target S/4HANA
Pre-Load Validation
Project Team
Completeness
Task
Action
Generation of
Pre-load reports
Mandatory field check.
Activity Types are mapped to new values
Activity Type Hierarchy Mapped to new values
Person Responsible / HR positions mapped to new values
Record Count
Confirm the record counts in preload summary report
Total Records:
Valid Records:
Invalid Records:
Accuracy
Task
Action
Mandatory field mapping and transformation
Obtain a list of the fields to be populated with values from mapping files and ensure all these fields contain S/4HANA values.
Review the data report to ensure mapping value is not missing in tool.
Capture errors in the Data Error report.
Business
Completeness
Confirm the Preload File contains all the records in scope of migration ( Based on list of Activity Types mapped from old to new )
Accuracy
Verify Activity Types are transformed accurately as per endorsed transformation/mapping rules.
Review error reports in tool for any mismatch or missing transformed values.
In ECC system, execute ECC tcode SE16N to display table CEPC to confirm copied fields are accurately copied.
If any of the sum is different, raise defect and flag the relevant record as error.Load
The load process includes:
- Execute the automated data load into target system using load tool or produce the load file if the loading of records to be done using LTMC cockpit object of Activity Type.
- Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation with side by side check of each fields in scope of the objects with fields to be displayed as XXXX_ECC, XXXX_S4HANA, XXXX_MATCH ( As TRUE or FALSE) with an additional column denoting fields not matching and status of loading in S/4HANA as LOADED_IN_S4HANA ( As TRUE or FALSE)
Load Run Sheet
Item
Step description
Team responsible
1
Ensure the load tools are transported into the correct tool instance.
Data team
2
Ensure DCTs and all required mappings are submitted and complete
Data team
3
Ensure Pre-load sign-offs are obtained.
Data team
4
Execute upload of Activity Type Object using Migration Cockpit Object for Activity Type Upload
Data team
5
Generate the post load reports in tool.
Data team
6
Log errors as defects, if any and address resolutions. Close defects.
Data team
7
Resolve defects by reupload and re-generate post load reports if necessary.
Data team
8
Business to validate the post load files as part of post-load validation, raise data defects or provide the post-load sign-off.
Business
9
Repeat steps 5 to 7 if necessary.
Data team
Load Phase and Dependencies
Configuration
Item # | Configuration item |
1. | Controlling Area |
2. | Standard Hierarchy is Maintained |
3. | Currencies (currency keys, decimal places in currencies) |
Conversion Objects
Error Handling
Error type | Error description | Action taken |
P | Posting period is blocked for posting | Review project / cutover plan and ensure posting periods can be opened for postings |
Activity Type does not exist | Activity Type does not exist in company code | Ensure the Activity Type mapping is correct and or create the Activity Type if it is valid |
Post-Load Validation
Project Team
Completeness
Total number of records loaded for TB Balance ( PY ) will be generated in the Post-load reports in tool based on the target table and fields mentioned in section 3.
The reconciliation needs to be executed on the total number of ‘valid’ records and currency amount per company code in the source compared to total number of records and currency amount in S/4HANA
Record Count
Check the sum of record count of the open items in the load file is the same as S/4HANA. The record count for TB Balance ( PY ) will be done on the group basis. The fields in the group are consist of: Company Code, Vendor Account
Check Amount in Document Currency and Local Currency
Check on line item level that the sum of the amount in Document Currency and Local Currency in the load file is the same as posted in S/4HANA. If any of the sum is different, flag the record as error.
Accuracy
Post-load reports will have the same structure as the load file and some additional columns as required to facilitate the post load validation.
Leverage on tool to create a Post Load report that reports S/4HANA loaded records along with the ECC values side-by-side to allow for 100% check of all these fields in the shortest possible time.
Any mismatch will be reported under the Post Load - Error report.
Business
Completeness
Review the record count report from the Data Team and ensure it is correct by cross-checking with the record count confirmed during Pre-load Business Validations
Business may also run transaction code FS10N – Vendor Line Item Display or equivalent report in Fiori App to display loaded TB Balance ( PY ) in S/4HANA and compare results against the pre-load reports generated from tool.Accuracy
| . |
Key Assumptions
- Master Data Standard is up to date as on the date of documenting this conversion approach and data load. is in scope based on data design and any exception requested by business.
- Data values in DCT are target ready data unless a specific transformation rule is stated for that field in the transformation rules
- Basic required configuration to be completed prior to this conversation
Change log
| Change History | ||
|---|---|---|
|
Workflow history
| Workflow Report | ||||||
|---|---|---|---|---|---|---|
|