| Status | Revision under Review |
| Owner | Soumen 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.
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
| PF2 | Activity Type | S4HANA | ||
| WP2 | Activity Type | S4HANA | ||
| PI2 | Activity Type | S4HANA |
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 |
| KOKRS | Controlling Area | CHAR | 80 | |||
| LSTAR | Activity Type | CHAR | 80 | |||
| DATAB | Valid-from Date | Date | ||||
| DATBI | Valid-to Date | Date | ||||
| LANGU | Language in Which Texts Are Saved | CHAR | 80 | |||
| NAME | Name | CHAR | 20 | |||
| LTEXT | Description | CHAR | 40 | |||
| LEINH_ISO | Activity Unit (ISO Format) | CHAR | 3 | |||
| LATYP | Activity Type Category | CHAR | 80 | |||
| LATYPI | Variant Activity Type Category | CHAR | 80 | |||
| KSTTY | Valid Cost Center Categories | CHAR | 8 | |||
| AUSEH_ISO | Output Unit (ISO Format) | CHAR | 3 | |||
| AUSFK | Output Factor | Number | 5 | |||
| VKSTA | Allocation Cost Element | CHAR | 10 | |||
| SPRKZ | Lock Indicator | CHAR | 1 | |||
| FIXVO | Redistribution of Fixed Costs | CHAR | 1 | |||
| TARKZ | Price Indicator | CHAR | 3 | |||
| YRATE | Price Calc. w. Period-Based Avg. Prices | CHAR | 1 | |||
| TARKZ_I | Actual Price Indicator | CHAR | 3 | |||
| MANIST | Actual Quantity Set | CHAR | 1 | |||
| MANPLAN | Plan Quantity Set | CHAR | 1 |
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
| Selection Ref Screen | Parameter Name | Selection Type | Requirement | Value to be entered/set |
|---|---|---|---|---|
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 |
| 1 | ECC | CEPC | KOKRS | Controlling Area* The controlling area is the highest organizational unit in Controlling. Type: Text Length: 80 | S/4HANA | CEPC | KOKRS | Controlling Area* The controlling area is the highest organizational unit in Controlling. Type: Text Length: 80 | Default to Controlling Area XXXX |
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 commence| Item # | Step Description | Team Responsible |
|---|---|---|
| 1 | Ensure all the fields that require value mapping, as stipulated. Mapping tables, have the correct values mapped and imported into tool. | Data Team |
| 2 | Ensure Activity Type hierarchies are loaded into target S/4HANA | Data Team |
Pre-Load Validation
Project Team
Completeness
Task | Action |
Generation of | Mandatory field check. 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. |
Business
Completeness
| Task | Action |
|---|---|
| Verify record count in Pre-load reports by region | Confirm the Preload File contains all the records in scope of migration ( Based on list of Activity Types mapped from old to new ) |
Accuracy
| Task | Action |
|---|---|
| Conversion 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 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
| Object # | Preceding Object Conversion Approach |
|---|---|
| N/A |
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
| Task | Action |
|---|---|
| Reconciliation of Record Count | 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 |
Accuracy
| Task | Action |
|---|---|
| Check values in key fields for 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
| Task | Action |
|---|---|
| Record Count Check | 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 |
Accuracy
| Task | Action |
|---|---|
| Spot check | Business should choose some Activity Type and perform comprehensive check of the fields in S4 |
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.
Change log
Workflow history
| Title | Last Updated By | Updated | Status | |
|---|---|---|---|---|
| There are no pages at the moment. | ||||