| Status | |
|---|---|
| Owner | |
| Stakeholders |
Purpose
The purpose of this document outlines the conversion process for Right of Use (ROU) assets Master and Transactional data in SyWay S/4 HANA. The ROU Assets migration will move both the master and transactional data in a single step and there will be only one SAP standard template that will be utilized for both Master and Transactional data migrations. Syniti ADMM tool organises the execution of data extraction, transformation & mapping, loading and data quality (ETL).
ROU Asset master primarily contains of the following information:
- General information: Asset description, asset class, account determination, capitalization date etc.
- Time Dependent data: Cost Center, Plant, Location etc.,
- Depreciation terms data: Depreciation keys, Useful life and Depreciation areas
Note: This conversion specification will only include to ROU assets that were created from underlying RE-FX contracts from object 1076. All other fixed assets (non ROU) will be managed using objects 1070, 9022 and 9028.
Conversion Scope
The scope of this document is to define a data upload approach for active ROU Assets from legacy systems into S/4HANA following the Master Data Design Standard DD-FUN-050 Master Data Standard_1070-Fixed Assets (incl. Sub Assets)
Relevancy rule:
The data from legacy system includes:
- Company code is in scope
- All active ROU Assets
The data from legacy system excludes:
- All non-ROU assets
Relevancy rule for Extraction: The following relevancy criteria to be considered for extracting active ROU Assets from both WP2 and PF2. Note: PI2 does not have ROU Assets
- Go to table ANLA and filter based on company code (BUKRS) that are in scope and asset class (ANLKL) that are relevant to ROU. Ensure that that deactivation date (DEAKT) is blank.
- Based on the result from step-1, go to table ANLZ (Time dependent terms). Filter the details based on company code (BUKRS), asset number (ANLN1) and asset sub-number (ANLN2)
- Based on the result from step-1, go to table ANLB (Depreciation area terms). Filter the details based on company code (BUKRS), asset number (ANLN1) and asset sub-number (ANLN2). Note: One asset will consist of more than one line item depending on the number of depreciation areas that is set up in the legacy system
- Based on the result from step 1 and 3, go to table ANLC (Asset values). Filter based on company code (BUKRS), asset number (ANLN1), asset sub-number (ANLN2), fiscal year (GJAHR) and Depreciation areas (AFABE). For filtering on Fiscal year (GJAHR), this will depend on whether it is year end or mid-year migration.
- Year end migration: This will depend on the data transfer date. Ex: If the data transfer date is 31.12.2027, then fiscal year (GJAHR) will be 2027
- Mid year migration: This will depend on the data transfer date. Ex: If the data transfer date is 30.06.2028, then fiscal year (GJAHR) will be 2028
After this, retrieve the asset cumulative values.
i) ROU asset cumulative values KANSW
ii) ROU asset accumulated depreciation KNAFA. Note: For year end migration, the accumulated migration will equals to KNAFA + NAFAG as the accumulated depreciation
iii) ROU asset cumulative Unplanned depreciation KAAFA
iv) ROU asset ordinary depreciation posted in the current migration year NAFAG
v) ROU asset posted unplanned depreciation in the current migration year AAFAG
- Go to table ANEP (Asset line item postings), filter based on company code (BUKRS), ROU asset number (ANLN1), ROU asset sub number (ANLN2), fiscal year (GJAHR) and accounting document number (BELNR). Then, retrieve the following:
- Go to table ANLV (Insurance data), filter based on company code (BUKRS), ROU asset number (ANLN1) and ROU asset sub number (ANLN2). Then, retrieve the data for ROU asset insurance information.
- Go to table ANLU (Asset master: user fields), filter based on company code (BUKRS), ROU asset number (ANLN1) and ROU asset sub number (ANLN2). Then, retrieve the user fields data for ROU assets
There are 2 group go-live as below:
- Group 1 go-live is planned for 1 July 2028
- Group 2 go-live is planned for 1 Jan 2029
If the currency of the depreciation area in the target S4 system is the same as the currency of the mapped depreciation area in the source system, the ROU asset balances will be copied from the mapped depreciation area of the source system. Otherwise, the asset balances will be converted from the asset balances of the depreciation area of the source system as per the mapping table by using the exchange rates for conversion as below:
- For Group 1 Go live: B/S spot rate as of 30 June 2028 will be used for Group Depreciation Areas
- For Group 2 Go live: B/S spot rate as of 31 Dec 2028 will be used for Group Depreciation Areas
Note: If company codes (where local currency is not EUR) have depreciation area in EUR, this EUR depreciation area is currently not used anymore. (In the past, these EUR depreciation areas were used when BFC was not the consolidation tool).
ROU Assets will be migrated to respective group go live as described in Enterprise Structure Catalog - Google Sheets (worksheet 10. Company code).
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
| PF2 | ROU Assets | 3,270 | S/4 HANA | Will be same as Source, unless any new Assets and/or deactivation of assets before Go-live |
| WP2 | ROU Assets | 1,044 | S/4 HANA | Will be same as Source, unless any new Assets and/or deactivation of assets before Go-live |
Additional Information
Multi-language Requirement
It was decided to apply approach below:
- Field “Description Line1” (ANLA-TXT50) = Migrate as it is from legacy system to S/4HANA. The description could be any languages (not only the 4 core languages but also any other non-core languages.
- Field “Description Line2” (ANLA-TXA50) = Migrate as it is from legacy system to S/4HANA. The description line 2 is used to add information on the description of the asset when the line 1 length is not enough.
- Field "Asset main no.text" (ANLH-ANLHTXT) must be in English
Document Management
N/A
Legal Requirement
There are no legal requirements relevant to data migration of ROU Assets
Special Requirements
N/A
Target Design
The technical design of the target for this conversion approach.
| Load Sheet Name | Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|---|
| Master details | ANLA | BUKRS | BUKRS | Company Code | CHAR | 4 | Required |
| Master details | ANLA / ACDOCA | ANLN1 | ANLN1 | External/Legacy ROU Asset Number | CHAR | 12 | Required |
| Master details | ANLA / ACDOCA | ANLN2 | ANLN2 | ROU Asset Sub number | CHAR | 4 | Optional |
| Master details | ANLA / ACDOCA | ANLKL | ANLKL | ROU Asset Class | CHAR | 8 | Required |
| Master details | ANLA | TXT50 | TXA50_ANLT | ROU Asset Description | CHAR | 50 | Required |
| Master details | ANLA | TXA50 | TXA50_MORE | ROU Asset Description 2 | CHAR | 50 | Conditional |
| Master details | ANLA | SERNR | AM_SERNR | Serial Number | CHAR | 18 | Optional |
| Master details | ANLA | INVNR | INVNR_ANLA | Inventory Number | CHAR | 25 | Optional |
| Master details | ANLA / ACDOCA | MENGE | AM_MENGE | Quantity | QUAN | 13 with Decimal 3 | Optional |
| Master details | ANLA / ACDOCA | MEINS | MEINS | Base Unit of Measure | UNIT | 3 | Conditional |
| Master details | ANLA | ANEQK | ANEQK | Asset is managed historically | NUMC | 1 | Optional |
| Master details | ANLH | ANLHTXT | ANLHTXT | Asset Main Number Text | CHAR | 50 | Optional |
| Inventory | ANLA | IVDAT | IVDAT_ANLA | Last inventory date | DATS | 8 | Optional |
| Inventory | ANLA | INKEN | INKEN | Inventory indicator | CHAR | 1 | Optional |
| Posting Information | ANLA | AKTIV | AKTIVD | Asset Capitalization Date | DATS | 8 | Required |
| Time Dependent Data | ANLZ / ACDOCA | GSBER | GSBER | Business Area | CHAR | 4 | Optional |
| Time Dependent Data | ANLZ / ACDOCA | KOSTL | KOSTL | Cost Center | CHAR | 10 | Required |
| Time Dependent Data | ANLZ / ACDOCA | WERKS | WERKS_D | Plant | CHAR | 4 | Optional |
| Time Dependent Data | ANLZ | STORT | STORT | Asset Location | CHAR | 10 | Optional |
| Time Dependent Data | ANLZ | FKBER | FKBER | Functional Area | CHAR | 16 | Optional |
| Time Dependent Data | ANLZ / ACDOCA | PRCTR | PRCTR | Profit Center | CHAR | 10 | Optional |
| Allocations | ANLA | ORD41 | ORD41 | Evaluation Group 1 | CHAR | 4 | Optional |
| Allocations | ANLA | ORD44 | ORD44 | Evaluation Group 4 | CHAR | 4 | Optional |
| Allocations | ANLA | GDLGRP | GDLGRP | Evaluation Group 5 | CHAR | 8 | Optional |
| Origin | ANLA | LIFNR | AM_LIFNR | Account Number of Supplier | CHAR | 10 | Optional |
| Origin | ANLA | HERST | HERST | Manufacturer of Asset | CHAR | 30 | Optional |
| Origin | ANLA | VBUND | RASSC | Company ID of Trading Partner | CHAR | 6 | Optional |
| Net Worth Valuation | ANLA | VMGLI | VMGLI | Property Classification Key | CHAR | 4 | Optional |
| Net Worth Valuation | ANLA | EIGKZ | EIGKZ | Property Indicator | CHAR | 1 | Optional |
| Depreciation Areas | ANLB / ACDOCA | AFABE | AFABE_D | Depreciation Area | NUMC | 2 | Required |
| Depreciation Areas | ANLB | AFASL | AFASL | Depreciation Key | CHAR | 4 | Required |
| Depreciation Areas | ANLB | NDJAR | NDJAR | Useful Life (in Years) | NUMC | 3 | Optional |
| Depreciation Areas | ANLB | NDPER | NDPER | Useful Life (in Periods) | NUMC | 3 | Optional |
| Cumulative Values | ANLC | AFABE | AFABE_D | Depreciation Area | NUMC | 2 | Required |
| Cumulative Values | ANLC / ACDOCA | GJAHR | GJAHR | Current Fiscal Year | NUMC | 4 | Required |
| Cumulative Values | ANLC | KANSW | KANSW | Cumulated Acquisition Value | CURR | 23 with Decimal 2 | Required |
| Cumulative Values | ANLC | KNAFA | KNAFA | Accumulated Ordinary Depreciation | CURR | 23 with Decimal 2 | Required |
| Cumulative Values | ANLC | KSAFA | KSAFA | Cumulative Special Depreciation | CURR | 23 with Decimal 2 | Optional |
| Cumulative Values | ANLC | KAAFA | KAAFA | Cumulative Unplanned Depreciation | CURR | 23 with Decimal 2 | Optional |
| Cumulative Values | T093B | WAERS | WAERS | Currency Key | CUKY | 5 | Required |
| Posted Values | ANLC | AFABE | AFABE_D | Depreciation Area | NUMC | 2 | Required |
| Posted Values | ANLC / ACDOCA | GJAHR | GJAHR | Current Fiscal Year | NUMC | 4 | Required |
| Posted Values | ANLC | NAFAG | NAFAG | Posted Ordinary Deprec. for the Year | CURR | 23 with Decimal 2 | Required |
| Posted Values | ANLC | SAFAG | SAFAG | Posted Special Depreciation for the Year | CURR | 23 with Decimal 2 | Optional |
| Posted Values | ANLC | AAFAG | AAFAG | Posted Unplanned Deprec. for the Year | CURR | 23 with Decimal 2 | Optional |
| Posted Values | T093B | WAERS | WAERS | Currency Key | CUKY | 5 | Required |
| Posted Values | ANLC | PSTEND | PSTEND | Depr. Posted Until (Including Period) | NUMC | 3 | Required |
| Transactions (Tranf.Dur.FY) | ANLC | AFABE | AFABE_D | Depreciation Area | NUMC | 2 | Required |
| Transactions (Tranf.Dur.FY) | ANEP | BWASL | BWASL | Asset Transaction Type | CHAR | 3 | Conditional |
| Transactions (Tranf.Dur.FY) | ANEP | GJAHR | GJAHR | Current Fiscal Year | NUMC | 4 | Optional |
| Transactions (Tranf.Dur.FY) | ANEP | LNRAN | LNRAN | Sequence No. of Asset Line Items in FY | NUMC | 5 | Conditional |
| Transactions (Tranf.Dur.FY) | ANEP | BZDAT | BZDAT | Reference Date | DATS | 8 | Optional |
| Transactions (Tranf.Dur.FY) | ANEP | ANBTR | ANBTR | Amount Posted | CURR | 23 with Decimal 2 | Optional |
| Transactions (Tranf.Dur.FY) | T093B | WAERS | WAERS | Currency Key | CUKY | 5 | Required |
Data Cleansing
| ID | Criticality | Error Message/Report Description | Rule | Output | Source System |
|---|---|---|---|---|---|
| 1 | Low | If ROU asset is active but underlying RE-FX contract is concluded then the ROU asset will be cleansed through deactivation. | 1. Get contract numbers from VICNCN-BUKRS where BUKRS represents company codes in scope and VICNCN-RECNENDABS is greater than or equal to 'Cutover date' 2. From step-1, get RE-FX contract numbers and verify VICNCN-RECNENDABS is greater than or equal to 'Cutover date' and Probable end date VICERULE-PROBABLEEND is less than or equal to 'Cutover date' 3. From step-1 and 2, identify associated ROU assets and see if ROU asset is deactivated ANLA-DEAKT. If not deactivated, cleansing to be performed | After cleansing, those ROU assets will become deactivate | PF2 and WP2 |
Conversion Process
The high-level process is represented by the diagram below. Note: DCT is not required for this object 9108. DCT is shown in table below for reference only, just in case in the future data migration, DCT may be required.
The conversion process will be largely automated using Syniti ADMM as the conversion tool:
Process | Activity |
Extract | Extract involves collecting data from the source. The source is a SAP system, Extract means to pull the required data from source systems into repository using Syniti ADMM. There are 2 steps for this method:
|
Transform | There are 2 steps of Transform activities that can happen in ADMM:
|
Load | This process includes:
|
Data Privacy and Sensitivity
N/AExtraction
The ROU Assets shall be extracted from SAP ECC and migrated using the Syniti Migrate. There are 2 possibilities:
- The data exists. Syniti Migrate connects to the source and loads the data into Syniti Migrate. 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 Syniti Migrate. This is to be conducted using DCT (Data Collection Template) in Syniti Migrate. Note: DCT is not applicable for this object 9108
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. | Extract ROU assets from ANLA table in PF2 and WP2 | Syniti team |
2. | Apply Asset Relevancy criteria on the extracted records. | Syniti team |
3. | Extract Time Dependent Data of ROU asset master records from ANLZ table in PF2 and WP2. | Syniti team |
4. | Extract Depreciation Terms Data of the ROU asset master from ANLB table in PF2 and WP2. | Syniti team |
5. | Extract ROU Asset master text from ANLH table in PF2 and WP2. | Syniti team |
| 6. | Extract Insurance Data of ROU asset master records from ANLV table in PF2 and WP2. | Syniti team |
Selection Screen
| Selection Ref Screen | Parameter Name | Selection Type | Requirement | Value to be entered/set |
|---|---|---|---|---|
| N/A |
Data Collection Template (DCT)
| Field Name | Field Description | Rule |
|---|---|---|
| N/A |
Extraction Dependencies
| Item # | Step Description | Team Responsible |
|---|---|---|
| 1. | Data cleansing of legacy ROU assets where associated RE-FX contracts are no longer available for valuation. | Business |
| 2. | Data cleansing of legacy ROU assets where ROU assets are still exist though RE-FX contracts are expired, in this instance, ROU assets might require to transfer to normal asset. | Business |
Transformation
The Target fields are mapped to the applicable Legacy 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 Syniti Migrate to make the data Target ready:
- Perform value mapping and data transformation rules.
- Legacy values are mapped to the to-be values (this could include a default value)
- Values are transformed according to the rules defined in Syniti Migrate
- 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 that all of the fields that require value mapping have the latest signed-off and imported into Syniti Migrate. | Data team |
2. | Go to Process Area Launch and Process the Object – ROU Asset | Data team |
3. | Launch the Objects to execute transformation. | Data team |
4. | Perform transformation ROU Assets extracted from PF2 and WP2 where target values will be derived from mapping tables. | Data team |
5. | Generate Pre-Load reports in Syniti Migrate. | Data team |
6. | Generate data load count in Syniti Migrate. | Data team |
7. | Log errors as defects, if any and address resolutions. Close defects. | Data team |
8. | Re-transform and re-validate the Pre-load reports if necessary. | Data team |
9. | Validate the transformed file as part of pre-load validation, raise data defects or provide the pre-load sign-off. | Business |
10. | Analyze and resolve any pre-load defects logged by business. | Data team |
Transformation Rules
The ROU asset takeover values will be based on the currency of the target depreciation area as depreciation areas are defaulted from the chart of depreciation assigned to the company code in the target system. Thus, depreciation area/chart of depreciation in the target system will be mapped to the depreciation area/chart of depreciation in the legacy system if the currency is the same.
- If the target depreciation area is found in the mapping table, the takeover values will be copied from the source depreciation area.
- Otherwise, will be translated from the gross values found in the Book Depreciation area, refer to section "Depreciation area in Foreign Currency".
Depreciation area in Foreign Currency:
Asset Balances in Group Currency depreciation area will not be migrated as per values Group depreciation areas in the legacy system. If the target depreciation area/chart of depreciation is not found in the mapping table, the corresponding balances for the depreciation area will be derived from the Book Depreciation area i.e. 01-Leading.
For conversion, the exchange rate would be as below:
- For Group 1 Go live: B/S spot rate as of 30 June 2028 will be used for Group Depreciation Areas
- For Group 2 Go live: B/S spot rate as of 31 Dec 2028 will be used for Group Depreciation Areas
The translation will be done in ADMM and align to the Trial Balance Conversion.
Translation logic to determine the balance:
In SAP, currencies (data type CURR) are stored with 2 decimal number but can be configured to display with different number of decimals (Table TCURX)
The logic to determine the balance (this logic should apply to all currencies):
- Check table T093B in legacy system to retrieve the currency for the company code and depreciation area.
- Check table TCURX in legacy system to find the number of decimal places for the currency. If '0', multiply the amounts by 100, else (including no entry found in TCURX), no action
Currency Adjustment During Migration (TCURX Consideration):
In SAP, the TCURX table defines the number of decimal places used for each currency. This impacts how amounts are stored internally in database tables versus how they are displayed externally in user interfaces or reports.
Currencies such as JPY (Japanese Yen), KRW (Korean Won), or VND (Vietnamese Dong) are typically configured with no decimal places (TCURX-CURRDEC = 0).
Understanding and correctly applying the TCURX rules is essential during data migration to ensure financial consistency between ECC and S/4HANA. Internal vs External Currency Representation example:
Internal Vs External Currency Amount Representation:
The amount value as displayed to users in SAP screens and reports is 96015 JPY (external), whereas, the amount value stored in database tables for computation is 960.15 JPY (internal).
During data migration, these internal (technical) amounts must be converted to external amounts to ensure accuracy and consistency in the target S/4HANA system through multiplied by factor = 10² if target has 2 decimals
Conversion Formula: External Amount = Internal Amount * 10 to the power (2 - Number of decimal for the currency in TCURX table)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
Transformation Mapping
The following legacy values have to be transformed to target SyWay values.| Mapping Table Name | Mapping Table Description |
|---|---|
Company code | Mapping of legacy company code to SyWay company code |
Asset Class | Mapping of legacy ROU asset Class to SyWay ROU asset class |
Cost center | Mapping of legacy cost centre to SyWay cost centre |
Profit center | Mapping of legacy profit centre to SyWay profit centre |
Plant | Mapping of legacy plant code to SyWay plant code |
Location | Mapping of legacy location to SyWay location |
Evaluation group 1 | Mapping of legacy EG1 to SyWay EG1 |
Evaluation group 5 | Mapping of legacy EG5 to SyWay EG5 |
Depreciation area | Mapping of legacy depreciation areas to SyWay depreciation areas |
Depreciation key | Mapping of legacy depreciation key to SyWay depreciation key |
Classification Key | Mapping of legacy Classification Key to SyWay Classification Key |
Trading Partner | Mapping of legacy Trading Partner to SyWay Trading Partner |
Transformation Dependencies
List the steps that need to occur before transformation can commence| Item # | Step Description | Team Responsible |
|---|---|---|
| 1 | Ensure that all of the fields that require value mapping, as specified in section "Mapping tables", have the appropriate values mapped and imported into ADMM. | Data team |
Pre-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
| Pre-load reports | Check that the number of ROU Assets in the upload file are the same as the number of contracts in the ETL file |
| Pre-load reports | Reconciliation of record count: Total number of ROU Assets in the extraction is compared against the total number of ROU Assets in the legacy system. |
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 ETL. |
Business
Completeness
| Task | Action |
|---|---|
| Verify record count | Business Data Owner/s to verify that the total number of relevant records from the source 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 ROU assets are transformed accurately as per the ETL rules. Review List of Error reports in ADMM for any mismatch or missing transformed values. |
Load
ROU Assets will be migrated using the SAP tool 'Migration Cockpit' and 'Object: Fixed asset (incl. balances and transactions)'. Migration template is attached as a reference.
The load process includes:
- Execute the automated data load into target system using load tool or product the load file if the load must be done manually
- 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 "ROU Assets" to validate if data is loaded successfully without errors. If errors, log defects and obtain resolution | 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. AS03, AW01N, AR01 etc., | R2R Data team |
7 | Generate post load report if step 6 is validated | R2R Data team |
Load Phase and Dependencies
The load phase for this object is Pre Cutover and this object will be loaded before RE-FX Contracts (object 9108) is loaded.
Configuration
The table below shows a key configuration elements
| Item # | Configuration Item |
|---|---|
1. | Company Code |
2 | Chart of Depreciation |
3 | Asset Class |
4 | Depreciation Areas |
5 | Depreciation Key |
6 | GL Account determination |
7 | i) Soft Config - ROU Asset number ranges ii) Soft Config - Asset Data Transfer Configuration · Transfer date – Last day of the month prior to go-live · Legacy Data Transfer Status = In Preparation · Document type 9A |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
| CNV-1073 | Profit Centre |
| CNV-1074 | Cost Centre |
Error Handling
The table below shows some possible system errors for this data object during data load. All data load error is to be logged as defect and managed within the Defect Management
| Error Type | Error Description | Action Taken |
|---|---|---|
Invalid Data | Relevant cost center is not valid in the validity of time dependent data in the ROU Asset master to be loaded. | Check whether the validity of time dependent data in cost center needs to be changed. |
Post-Load Validation
Project Team
The following post load validations will be performed by the project team.
Completeness
| Task | Action |
|---|---|
| Reconciliation of Total Record Count | Total number of records loaded for ROU Assets and Depreciation terms will be generated in the Post-load reports in ADMM. ROU Assets in the Post Load report is compared against total number of ROU assets in the pre-load reports by company code, Asset class, cost center, depreciation key etc., |
| Mandatory fields check | Review the post load file and note the records that failed the mandatory fields check and fix the errors |
| Post-load activity | Recalculate ROU Asset values using t.code AFAR |
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 the Syniti ADMM tool to create a Post load report that reports S/4 HANA loaded records along with the legacy values side-by-side to allow for 100% check of all these fields in the shortest possible time. If any mismatch, they will report under 'Error' for corrective action. |
Business
The following post load validations will be performed by the 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 checks | Business should choose some ROU Assets and perform comprehensive checks of the fields in S/4 HANA. Recommended to verify sample data per company code and Asset class combination. |
| Conversion Accuracy | Verify that the ROU Assets in target S/4 HANA are loaded correctly via load program and validate post load reports using standard t.code AR01 from S/4 HANA. |
Key Assumptions
- Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
- ROU Assets are in scope based on data design and any exception requested by business.
- ROU asset master cleansing is completed.
- All ROU assets (associated with RE-FX contracts) must be deactivated (i.e. populate the deactivation date field).
See also
Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.