| Status | Revision in Progress |
|---|---|
| Owner | Maytingsari Tjahjo |
| Stakeholders |
Purpose
The purpose of this document is to define the conversion approach to migrate asset master (main and sub asset) and group asset from legacy systems to the S/4HANA.
Group asset in SAP is utilized to meet certain tax requirements of some countries (i.e. India), which require depreciation calculation on a higher asset level than the individual asset level. The depreciation rate is applied to the group asset value rather than individual asset value. Group asset is almost like a normal asset with Group Asset indicator and only tax depreciation area assigned.
This document consists of links to other documents that support conversion process such as Master Data Standard for Asset master.
050 - Master Data Standard - ERP Rebuild Implementation - Google Drive
Asset master consists of information of Fixed Assets Register including:
- General information such as asset description name, asset class, account determination, capitalization date, etc.
- Time Dependent data – Assignment of related data by validity period (such as cost center, plant, location, etc)
- Depreciation terms data - Depreciation keys, useful life and depreciation areas
Note:
Alex suggested to remove relevant sub-asset as all sub-assets will be migrated as main asset. This needs to be discussed again with Pedro. (One of the reasons we use this approach if some of the sub-assets in legacy system have main assets already retired.
Conversion Scope
The scope of this document covers the approach for converting active main and sub asset and group assets from Legacy Source Systems (PF2 and WP2) into S/4HANA following the Fixed Asset MDS (Master Data Standard).
Company code 5955 (India) is the only company code that have Group assets (There are 11 Group assets) These will be in scope for migration? (TBC).
In the to-be solution, it is not planned to use group assets. Awaiting Mohamed A to advise on how we handle the 11 Group Assets (co code 5955 (India) if the to be solution we don't use Group Assets?
The data from legacy system includes:
Relevancy rule:
- Main and sub assets with all rules to be met:
- Company code is in scope (Enterprise Structure Catalog - Google Sheets, worksheet "10. Company Code") AND
- Non-AuC (Asset under Construction) AND
- Non-RoU (Right-of-Use) asset AND
- Plant is in scope if not Blank AND
- Deactivation date is blank or current year AND
- Indicator Asset is a group asset (ANLA-XANLGR) is NOT “X” AND
- One of the 2 following criteria must be met:
- Posted with values in one of the depreciation areas OR
- Unposted in all depreciation areas and
- Appeared in the settlement rules of CAPEX Projects or
- Appeared in the account assignment category “A” in Open Purchase orders which are deemed relevant for migration
Fully depreciated asset will be in scope for migration as the asset register may be retained for insurance purposes or tax depreciation purposes.
Time dependent data in main and sub assets and group assets have specific validity period. Only the current validity period of the time dependent data will be migrated
Group assets with: (To be confirmed whether Group Asset is in scope or not)
- Company codes in scope (Enterprise Structure Catalog - Google Sheets, worksheet "10. Company Code") AND
- Active asset (field "Deactivation date" is blank) or asset that are deactivated in current year (field "Deactivation date" is current year)
- Indicator Asset is a group asset (ANLA-XANLGR) is set to “X”
The data from legacy system excludes:
- Assets under construction (AUC)
- RoU (Right-of-Use) Assets
- Group Assets
- Asset under Asset Class Shares (Shares will no longer be managed via FI-AA in S/4).
Below is the list of Asset Class Shares in PF2. Asset Class Shares in WP2 will be listed down once my access is fixed in WP2
| Class | Short Text | Asset class description |
| ZARFIN01 | Shares- Conso | Shares - Consolidated |
| ZARFIN02 | Shares- Non conso | Shares - Non consolidated |
| ZARFIN03 | Shares- Equity based | Shares - Invest. in equity based value |
| ZARFIN04 | Shares- Cies linked | Shares - Invest. in cies linked by part. Interest |
| ZARFIN05 | Shares - Others | Shares - Others |
| ZBEFIN01 | Shares- Conso | Shares - Consolidated |
| ZBEFIN02 | Shares- Non conso | Shares - Non consolidated |
| ZBEFIN03 | Shares- Equity based | Shares - Invest. in equity based value |
| ZBEFIN04 | Shares- Cies linked | Shares - Invest. in cies linked by part. Interest |
| ZBEFIN05 | Shares - Others | Shares - Others |
| ZBEFIN06 | Shares - AFS | Shares - AFS |
| ZBGFIN01 | Shares- Conso | Shares - Consolidated |
| ZBGFIN02 | Shares- Non conso | Shares - Non consolidated |
| ZBGFIN03 | Shares- Equity based | Shares - Invest. in equity based value |
| ZBGFIN04 | Shares- Cies linked | Shares - Invest. in cies linked by part. Interest |
| ZBGFIN05 | Shares - Others | Shares - Others |
| ZBRFIN01 | Shares- Conso | Shares - Consolidated |
| ZBRFIN02 | Shares- Non conso | Shares - Non consolidated |
| ZBRFIN03 | Shares- Equity based | Shares - Invest. in equity based value |
| ZBRFIN04 | Shares- Cies linked | Shares - Invest. in cies linked by part. Interest |
| ZBRFIN05 | Shares - Others | Shares - Others |
| ZBRFIN12 | Investment and share | Investment and shares-n/conso affiliates |
| ZCHFIN01 | Shares- Conso | Shares - Consolidated |
| ZCHFIN02 | Shares- Non conso | Shares - Non consolidated |
| ZCHFIN03 | Shares- Equity based | Shares - Invest. in equity based value |
| ZCLFIN01 | Shares- Conso | Shares - Consolidated |
| ZCLFIN02 | Shares- Non conso | Shares - Non consolidated |
| ZCLFIN03 | Shares- Equity based | Shares - Invest. in equity based value |
| ZCLFIN04 | Shares- Cies linked | Shares - Invest. in cies linked by part. Interest |
| ZCLFIN05 | Shares - Others | Shares - Others |
| ZCNFIN01 | Shares- Conso | Shares - Consolidated |
| ZCNFIN02 | Shares- Non conso | Shares - Non consolidated |
| ZCNFIN03 | Shares- Equity based | Shares - Invest. in equity based value |
| ZCNFIN04 | Shares- Cies linked | Shares - Invest. in cies linked by part. Interest |
| ZCNFIN05 | Shares - Others | Shares - Others |
| ZCNFIN06 | Shares - AFS | Shares - AFS |
| ZDEFIN01 | Shares - Consolidate | Shares - Consolidated |
| ZDEFIN02 | Shares - Non consoli | Shares - Non consolidated |
| ZDEFIN03 | Shares -Equity based | Shares -Equity based |
| ZDEFIN04 | Shares -Cies linked | Shares -Cies linked by part.interest |
| ZDEFIN05 | Shares -Others | Shares -Others |
| ZDEFIN11 | Investment and share | Investment and shares-conso affiliates |
| ZDEFIN12 | Investment and share | Investment and shares-n/conso affiliates |
| ZDEFIN13 | Investment and share | Investment and shares-n/conso affiliates |
| ZDEFIN15 | Investment and share | Investment and shares-n/conso affiliates |
| ZEGFIN01 | Shares-Consolidated | Shares-Consolidated |
| ZEGFIN02 | Shares-Non Consolida | Shares-Non Consolidated |
| ZEGFIN03 | Shares-Invest in Equ | Shares-Invest in Equity Based Value |
| ZEGFIN04 | Shares-Invest in Com | Shares-Invest in Comp linked by Part. Interest |
| ZEGFIN05 | Shares-Others Alloca | Shares-Others Allocation to FPDIR |
| ZESFIN01 | Shares- Conso | Shares - Consolidated |
| ZESFIN02 | Shares- Non conso | Shares - Non consolidated |
| ZESFIN03 | Shares- Equity based | Shares - Invest. in equity based value |
| ZESFIN04 | Shares- Cies linked | Shares - Invest. in cies linked by part. Interest |
| ZESFIN05 | Shares - Others | Shares - Others |
| ZFIFIN01 | Shares- Conso | Shares - Consolidated |
| ZFIFIN02 | Shares- Non conso | Shares - Non consolidated |
| ZFIFIN03 | Shares- Equity based | Shares - Invest. in equity based value |
| ZFIFIN04 | Shares- Cies linked | Shares - Invest. in cies linked by part. Interest |
| ZFIFIN05 | Shares - Others | Shares - Others |
| ZFRFIN01 | Shares- Conso | Shares - Consolidated |
| ZFRFIN02 | Shares- Non conso | Shares - Non consolidated |
| ZFRFIN03 | Shares- Equity based | Shares - Invest. in equity based value |
| ZFRFIN04 | Shares- Cies linked | Shares - Invest. in cies linked by part. Interest |
| ZFRFIN05 | Shares- Others | Shares - Others |
| ZGBFIN01 | Shares- Conso | Shares - Consolidated |
| ZGBFIN02 | Shares- Non conso | Shares - Non consolidated |
| ZGBFIN03 | Shares- Equity based | Shares - Invest. in equity based value |
| ZGBFIN04 | Shares- Cies linked | Shares - Invest. in cies linked by part. Interest |
| ZGBFIN05 | Shares - Others | Shares - Others |
| ZINFIN05 | Shares - Others | Shares - Others |
| ZITFIN01 | Shares- Conso | Shares - Consolidated |
| ZITFIN02 | Shares- Non conso | Shares - Non consolidated |
| ZITFIN03 | Shares- Equity based | Shares - Invest. in equity based value |
| ZITFIN04 | Shares- Cies linked | Shares - Invest. in cies linked by part. Interest |
| ZITFIN05 | Shares - Others | Shares - Others |
| ZITFIN06 | Shares - AFS | Shares - AFS |
| ZJPFIN01 | Shares- Conso | Shares - Consolidated |
| ZJPFIN02 | Shares- Non conso | Shares - Non consolidated |
| ZJPFIN03 | Shares- Equity based | Shares - Invest. in equity based value |
| ZJPFIN04 | Shares- Cies linked | Shares - Invest. in cies linked by part. Interest |
| ZJPFIN05 | Shares - Others | Shares - Others |
| ZLUFIN01 | Shares- Conso | Shares - Consolidated |
| ZLUFIN02 | Shares- Non conso | Shares - Non consolidated |
| ZLUFIN03 | Shares- Equity based | Shares - Invest. in equity based value |
| ZLUFIN04 | Shares- Cies linked | Shares - Invest. in cies linked by part. Interest |
| ZLUFIN05 | Shares - Others | Shares - Others |
| ZMXFIN01 | Shares - Consolidate | Shares - Consolidated |
| ZMXFIN02 | Shares - Non consoli | Shares - Non consolidated |
| ZMXFIN03 | Shares - Inv. in equ | Shares - Invest. in equity based value |
| ZMXFIN04 | Shares- Cies linked | Shares - Invest. in cies linked by part. Interest |
| ZMXFIN05 | Shares - Others | Shares - Others |
| ZNLFIN01 | Shares- Conso | Shares - Consolidated |
| ZNLFIN02 | Shares- Non conso | Shares - Non consolidated |
| ZNLFIN03 | Shares- Equity based | Shares - Invest. in equity based value |
| ZNLFIN04 | Shares- Cies linked | Shares - Invest. in cies linked by part. Interest |
| ZNLFIN05 | Shares - Others | Shares - Others |
| ZNLFIN13 | Investment and share | Investment and shares-n/conso affiliates |
| ZPTFIN01 | Shares - Consolidate | Shares - Consolidated |
| ZPTFIN02 | Shares - Non consoli | Shares - Non consolidated |
| ZPTFIN03 | Shares - Invest. in | Shares - Invest. in equity based value |
| ZPTFIN04 | Shares - Invest. in | Shares - Invest. in cies linked by part. Interest |
| ZPTFIN05 | Shares - Others | Shares - Others |
| ZSGFIN01 | Shares- Conso | Shares - Consolidated |
| ZSGFIN02 | Shares- Non conso | Shares - Non consolidated |
| ZSGFIN03 | Shares- Equity based | Shares - Invest. in equity based value |
| ZSGFIN04 | Shares- Cies linked | Shares - Invest. in cies linked by part. Interest |
| ZSGFIN05 | Shares - Others | Shares - Others |
| ZSGFIN06 | Shares - AFS | Shares - AFS |
| ZTHFIN01 | Shares- Conso | Shares - Consolidated |
| ZTHFIN02 | Shares- Non conso | Shares - Non consolidated |
| ZTHFIN03 | Shares- Equity based | Shares - Invest. in equity based value |
| ZTHFIN04 | Shares- Cies linked | Shares - Invest. in cies linked by part. Interest |
| ZTHFIN05 | Shares - Others | Shares - Others |
| ZTWFIN01 | Shares- Conso | Shares - Consolidated |
| ZTWFIN02 | Shares- Non conso | Shares - Non consolidated |
| ZTWFIN03 | Shares- Equity based | Shares - Invest. in equity based value |
| ZTWFIN04 | Shares- Cies linked | Shares - Invest. in cies linked by part. Interest |
| ZTWFIN05 | Shares - Others | Shares - Others |
| ZUSFIN01 | Shares-Consolidated | Shares-Consolidated |
| ZUSFIN02 | Shares-Non Consolidt | Shares-Non Consolidated |
| ZUSFIN03 | Shares-Equity Based | Shares-Invest in Equity Based Value |
| ZUSFIN04 | Shares-Comp Linked | Shares-Invest in Comp linked by Part. Interest |
| ZUSFIN05 | Shares-Others-FPDIR | Shares-Others Allocation to FPDIR |
| ZUSFIN33 | Shares-EquityBas.NoC | Shares-Invest in Equity Based Value (non-consolid) |
| ZUSFIN34 | Shares-equi earn aff | Shares-Invest in Equity earn affiliates |
| ZUSFIN35 | Shares-Invest AFS | Shares-Invest AFS |
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
PF2 | Relevant fixed asset master records extracted from the source system and transformed according to the target data into a pre-load reports. | 140.300 | S/4HANA | 140.300 |
WP2 | Relevant fixed asset master records extracted from the source system and transformed according to the target data into a pre-load reports. | 143.098 | S/4HANA | 143.098 |
There will be 3 SAP boxes
a. CUI box (US, GB, DE)
b. China box (CN)
c. ROW (Rest of the World) box
Please refer to file "Enterprise Structure Catalog" (worksheet "10. Company code") to see which company codes belongs to which SAP boxes.
Enterprise Structure Catalog - Google Sheets
In terms of data migration, below is the guideline:
a. Non-CUI objects : Migration to CUI box by Syniti.
b. CUI objects : Manual cleansing/separate migration cockpit (Syniti is not certified)
Fixed asset is non CUI object hence migration to 3 SAP boxes are all done by Syniti.
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 (To be confirmed). In PF2 and WP2, the field "Description Line 2" is used to add information on the description of the asset when the Line 1 is not enough.
PF2:
Total active assets 140.092
- Desc Line 2 which is empty = 95.618
- Desc Line 2 which is not empty = 44.474
WP2:
Total active assets 142.669
- Desc Line 2 which is empty = 63.524
- Desc Line 2 which is not empty = 79.145
As currently many assets have field "Desc Line 2" is not equal to empty, hence to store the translation in English, instead of using Field "Description Line 2" (ANLA-TXA50), it's better to use field "Asset main no.text" (ANLH-ANLHTXT). To be confirmed by Functional Team.
Note: Currently the value of field "Description Line 1" and field "Asset main no. text" are majority the same. Ony for few assets, they are different.
- Field "Asset main no.text" (ANLH-ANLHTXT) must be in English (To be confirmed which field to be used to store description in English)
Document Management
N/A
Legal Requirement
N/A
Special Requirements
Target Design
The technical design of the target for this conversion approach:
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement | Note |
|---|---|---|---|---|---|---|---|
ANLA | BUKRS | BUKRS | Company Code | CHAR | 4 | Mandatory | Must be valid company code in company code configuration (table T001) |
ANLA | ANLKL | ANLKL | Asset Class | CHAR | 8 | Mandatory | Must be valid in asset class configuration (table ANKA). Please refer to file below for To-Be Asset Classes: SyWay_asset_classes&fields - Google Sheets |
ANLA | ANLN1 | ANLN1 | Main Asset number | CHAR | 12 | System generated number | |
ANLA | ANLN2 | ANLN2 | Asset sub-number | CHAR | 4 | 0 (for main number) | The system automatically assigns sub-asset number 0 by default to every asset created which won't be prevented. However, the creation of additional sub-assets/child assets is not permitted in the global process designs for S/4 HANA. |
ANLA | TXT50 | TXA50_ANLT | Asset description | CHAR | 50 | Mandatory | For migrated assets, this field will be migrated as it is. |
ANLA | TXA50 | TXA50_MORE | Additional asset description | CHAR | 50 | Conditional | For migrated assets, this field will be migrated as it is. |
ANLH | ANLHTXT | ANLHTXT | Asset main no. text | CHAR | 50 | Mandatory | For migrated assets, this field shall be used to capture the English translation of the asset description |
ANLA | XLTXID | XLTXID | Indicator: Long text active | CHAR | 1 | Not used | |
ANLA | SERNR | AM_SERNR | Serial number | CHAR | 18 | Conditional | For migrated assets, this field will be migrated as it is (under the assumption as part of cleansing activities, business maintain a unique number in this field in ECC for capital spares that is equal to the serial number we maintain in the equipment) |
ANLA | MENGE | AM_MENGE | Quantity | QUAN | 13 | Conditional | For migrated assets, quantities captured in the legacy systems shall be retained. |
ANLA | MEINS | MEINS | Base unit of measure | UNIT | 3 | Conditional | Must be populated if Quantity is populated The unit of measure shall be set to 'EA' to facilitate quantity tracking on Fixed Assets for all assets except for - Intangbile Assets For assets of type 'Land and Building' an alternate unit of measure 'M2' can be maintained to track and use the size of the property for subsequent processes. |
ANLA | INVNR | INVNR_ANLA | Inventory Number | CHAR | 25 | Conditional | For migrated assets, the inventory number from the legacy systems shall be adopted for all assets except for capital spare Fixed Assets. For capital spares, the new equipment number from S/4 HANA on which the Fixed Asset is installed must be maintained in this field. Below are the steps in sequence:
|
RA02S | XHIST | XHIST_AM | Manage historically | CHAR | 1 | Optional | ???? |
ANLA | IVDAT | IVDAT_ANLA | Last Inventory on | DATS | 8 | Conditional | Must be in date format. Migrate as it is. |
ANLA | INKEN | INKEN | Include asset in inventory list | CHAR | 1 | Conditional | Checkbox (Defaulted to “X”) Set this indicator if you want the asset to be counted in a physical inventory. |
ANLA | INVZU | INVZU_ANLA | Inventory Note | CHAR | 15 | Conditional | It captures the user ID of the person who last confirmed the physical existence of the Fixed Asset as part of the physical inventory count process. For migrated assets, this field will be migrated as it is. This will be updated with the new target values as per S/4 design after the first inventory count cycle. |
ANLA | AKTIV | AKTIVD | Capitalization date | DATS | 8 | Optional | For migrated assets, the values from the legacy system shall be adopted. Must be in date format |
ANLA | ZUPER | DZUPER | First Acquisition Date | NUMC | 3 | Optional | For migrated assets, the values from the legacy system shall be adopted. Must be in date format |
ANLA | DEAKT | DEAKT | Deactivation on | DATS | 8 | Optional | For migrated assets retired in the fiscal year of a mid-year go-live (Group 1 Go live), the values from the legacy system shall be adopted. |
ANLZ | KOSTL | KOSTL | Cost Centre | CHAR | 10 | Mandatory | Must be valid cost center |
ANLZ | PRCTR | PRCTR | Profit Centre | CHAR | 10 | Mandatory | The profit centre is derived from the cost centre maintained in the asset master record. The reason why this field is shown in asset master because segment reporting in FI-AA is activated as some new features in S/4 are only available if this feature is on. With this feature switched on, we need to maintain the profit centre in the Fixed Asset master. And also want to be able to report Fixed Asset registers by profit centre going forward. Must be valid profit center. |
ANLZ | WERKS | WERKS_D | Plant | CHAR | 4 | Conditional | Must be valid in plant assigned to the company code configuration (Table T001K) Plant is a mandatory reporting attribute maintained in the Fixed Asset master for all tangible assets to facilitate the physical inventory count process which is usually performed by plant. The following exceptions apply as the below types of assets do not form part of the physical inventory count process: - RoU assets (exempted from pyhical inventory counts) |
ANLZ | STORT | STORT | Location | CHAR | 10 | Optional | Must be valid Location (T499S-STAND) assigned to plant above in configuration (Table T499S) |
ANLZ | RAUMN | RAUMNR | Room | CHAR | 8 | Optional | |
ANLZ | KFZKZ | AM_KFZKZ | License Plate No. of Vehicle | CHAR | 15 | Optional | |
ANLZ | XSTIL | XSTIL | Asset shutdown indicator | CHAR | 1 | Optional | |
ANLA | ORD41 | ORD41 | Evaluation group 1 | CHAR | 4 | Optional | Must be valid in Evaluation group 1 in configuration (Tables T087) and Text (Table T087T) |
ANLA | ORD42 | ORD42 | Evaluation group 2 | CHAR | 4 | Optional | |
ANLA | ORD43 | ORD43 | Evaluation group 3 | CHAR | 4 | Optional | |
ANLA | ORD44 | ORD44 | Evaluation group 4 | CHAR | 4 | Optional | |
| ANLA | GDLGRP | GDLGRP | Evaluation group 5 | CHAR | 8 | Optional | |
ANLA | IZWEK | IZWEK | Investment reason | CHAR | 2 | Optional | |
ANLA | ANLUE | ANLUE | Asset Super Number | CHAR | 12 | Optional | |
ANLA | AIBN1 | AIBN1 | Original asset number or Original Group Asset number | CHAR | 12 | Mandatory | If not blank, must be a valid combination of legacy company code and Asset no. in legacy system. |
ANLA | AIBN2 | AIBN2 | Original Sub-Asset | CHAR | 4 | Mandatory | |
ANLA | AIBDT | AIBDT | Original Acquisition Date of AuC/ Transferred Asset | DATS | 8 | Optional | |
ANLA | URJHR | URJHR | Fiscal Year of Original Acquisition | NUMC | 4 | Optional | |
ANLA | URWRT | URWRT | Original Acquisition Value | CURR | 13 | Optional | |
ANLA | POSNR | AM_POSNR | WBS element | NUMC | 8 | Optional | |
ANLA-? | Equipment | There won't be any synchronization switched on between Fixed Assets and Equipments or the other way around. There would be a soft link between equipments and Fixed Assets where the equipment should store the asset ID for plant assets. There won't be a link from Fixed Assets to the equipment hence this has been descoped. (Awaiting Alex for the final decision on this) | |||||
ANLA | VMGLI | VMGLI | Classification Key | CHAR | 4 | Optional | |
ANLV | VSART | VSART_ANLA | Insurance type | CHAR | 2 | Optional | |
ANLV | VSIND | VSIND | Index series | CHAR | 5 | Optional | |
ANLB | AFABE | AFABE_D | Depreciation area | NUMC | 2 | Mandatory | |
ANLB | AFASL | AFASL | Depreciation Key | CHAR | 4 | Mandatory | |
ANLB | NDJAR | NDJAR | Useful Life | NUMC | 3 | Mandatory | Numeric value less than 999 |
ANLB | NDPER | NDPER | Useful Life (Period) | NUMC | 4 | Mandatory | Numeric value (1-12) |
ANLB | AFABG | AFABG | Depreciation Start date | DATS | 8 | Optional | Valid date format |
ANLB | SCHRW_PROZ | SCHRW_PROZ | Scrap value % | DEC | 14 | Optional | Numeric value less than 100 |
ANLB | ANLGR | ANLGR | Group asset | CHAR | 12 | Optional | If populated, must be valid Group Asset. |
ANLB | INBDA | INBDA | Operating Readiness | DATS | 8 | Optional |
Below is the Migration Cockpit Template for Fixed Asset (Master Data and Balance):
Source data for Fixed asset (incl. balances and transactions).xlsx
Data Cleansing
| ID | Criticality | Error Message/Report Description | Rule | Output | Source System |
|---|---|---|---|---|---|
| 1 | C3 (Can load but does not comply data standard) | Report "Unposted asset without any linked object" Action item: Business to review this list and take necessary action accordingly. | Rule 1: Company codes must be in scope. Rule 2: Asset class is not Asset under Construction class. Rule 3: Has Deactivation date = BLANK or current year. Rule 4A: Has capitalization date = BLANK or Rule 4B: Has capitalization date populated but no entry is found in ANLC (Asset Value Fields) table for the asset in all depreciation areas. Rule 5: Does not appear in the settlement rule of any relevant cost objects1. or Line-item settlement type of Asset Under Construction (AUC) or assigned to any relevant open Purchase Orders.2. Refer to following data objects:
| Country Company code Asset number Asset Sub-Number Asset Class Description Deactivation date GL Account Capitalization date Current NBV Open PO flag Projects/WBS/IO | PF2 and WP2 |
| 2 | C3 (Can load but does not comply data standard) | Any assets with an inventory date less than 5 years ago should be checked and potentially retired as part of the data cleansing exercise. The field "Last Inventory on" date can be used for data cleansing prior to migration to identify aged assets that may no longer exist but haven't been written off. Action item: Business to review and retire obsolete Fixed Asset Report for Assets (Main and Sub-assets) with "Last Inventory on Date" as Blank or less than 5 years ago. Cleansing report is created for businesses to do cleansing on a regular basis. As the physical count date will always be 31 Oct, For PF2: For WP2: | Rule 1: Company must be in scope Rule 2: Plant must be in scope Rule 3: Asset class is not Asset under Construction and is not RoU asset and is not Group Asset Rule 4: Has Deactivation date = BLANK. Rule 5: Has Last Inventory on Date = BLANK or less than 5 years ago from Mock Conversion/Actual Cutover.
| Region Company code Asset number Sub-Number Description Last Inventory on Inventory Note Cost Centre Cost center category Profit center Asset Class GL Account Capitalization Date | PF2 and WP2 |
| 3 | Report "Fixed Assets with negative net book value" | Rule 1: Company codes must be in scope. Rule 2: Asset class is not Asset under Construction class. Rule 3: Has Deactivation date = BLANK or current year. | Country Company code Asset number Asset Sub-Number Asset Class Description Deactivation date Capitalization date Current NBV for each depreciation areas | PF2 and WP2 | |
| 4 | Report that shows Asset balance booked directly to GL (without posting to Fixed Asset subledger) (Transaction code ABST2) | Action item:
| PF2 and WP2 | ||
| 5 | A soft link is required between equipment and Fixed Assets for capital spare parts. For Fixed Assets which represent capital spare parts, the ones that are in use in the plant will be linked to an equipment. For to-be design, we will not have dedicated asset class for “Capital Spares” As part of cleansing activities, Business must identify manually which asset master which represent “Capital Spares”, after that for these assets, business must assign: a. New S/4HANA equipment number into field "Inventory Number" in S/4HANA b. Serial number of equipment number into field "Serial Number" in ECC (This is as preparation to migrate to S/4HANA) Note: A2D team does not need to assign Fixed Asset number into Equipment master. | PF2 and WP2 | |||
| 6 | Extract the asset description of field ANLA-TXT50 and ANLA-TXA50 for business to translate it into English | Action item:
|
Fixed Asset Verification
This refers to Data Cleansing Report "Relevant assets (main and sub-assets) with "Last Inventory on Date" as Blank or <=DD.MM.YYYY"
To adhere to SyWay Accounting Policy for managing fixed asset and eliminate unused data, all assets migrated from legacy system to S/4HANA must have evidence of asset verification recorded in the "Last Inventory On date" field in Asset master.
Any assets to be migrated to S/4HANA without such evidence recorded will require business approvals.
Conversion Process
The high-level process is represented by the diagram below:
Process | Activity |
Extract | Extract involves collecting data from the source. If the source is a system, Extract means to pull the required data from source systems into repository using ADMM. There are 2 steps for this method: a. Perform full data extraction from relevant asset tables in the source system(s). b. Apply Relevancy criteria for filtering the data that will be applicable according to Target Design. |
Transform | There are 2 steps of Transform activities that can happen in ADMM: 1. Perform mapping and data transformation rules. Some data will need to be mapped to the to-be values and/or updated according to the rules as per design requirement in target system. 2. Prepare load-ready data in the structure and format that is required for loading via standard Load Tool. This step also produces the load data ready for business to perform Pre-load Data Validation. |
Load | This process includes: 1. Execute the automated data load into target system using load tool. Note: There may be some cases where the load is done manually as part of business activities. If there is any, the load steps will be specified in section "Load Run Sheet" 2. Once the data is loaded to target system, it will be extracted out and prepared for Post Load Data Validation. |
Delta Data Management
Any main assets created in the legacy systems (PF2 and WP2) after the full extraction for Mock conversion will be re-extracted again from legacy systems (PF2 and WP2) for each mock or cutover rehearsals.
As data cleansing is performed in PF2 and WP2 to meet SYWAY design standard, each extraction will re-transform extracted data with on-going new unmapped legacy values discovered and mapped.
The transformed fixed assets will be combined with any other assets maintained in the Fixed Asset DCT (Data Collection Template) into the pre-load file for validation.
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. | Extract all main assets from ANLA table in PF2 and WP2, | Data team |
2. | Apply Asset Relevancy criteria on the extracted records. | Data team |
3. | Extract Asset long text from STXH and STXL tables of asset master records in Req#2 in PF2 and WP2. | Data team |
4. | Extract time dependent data of asset master records in Req#2 above from ANLZ table in PF2 and WP2. | Data team |
5. | Extract depreciation terms data of the asset master in Req#2 from ANLB table in PF2 and WP2. | 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 data with exception of some fields which require transformation as mentioned in the transformation rule.
DCT Rules
N/A
Extraction Dependencies
| Item # | Step Description | Team Responsible |
|---|---|---|
| 1. | Data cleansing of legacy main assets in the source system to adhere to target design is completed. | Business |
| 2. | Data cleansing of legacy assets where assets that are no longer physically exist will be assessed for retirement is accomplished | 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 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
- 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 in Section "Mapping tables", have the latest signed-off mapping files imported into Syniti Migrate. | Data team |
2. | Go to Process Area Launch and Process the Object – Fixed Asset | Data team |
3. | Launch the Objects to execute transformation. | Data team |
4. | Perform transformation for Group Assets and Main Assets extracted from PF2 and WP2 where target values will be derived from mapping tables. | Data team |
5. | Combine the transformed data of extracted main-asset (section "Extraction run sheet") and lease plan main assets populated in DCT (section "Data Collection Template") | Data team |
6. | Generate Pre-Load reports in Syniti Migrate. | Data team |
7. | Generate data load count in Syniti Migrate. | 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 5 to 10 if necessary | Data team |
Transformation Rules
List of all fields in the Target table field to be populated with values according to the Fixed Asset Master Data Standard to facilitate loading into target system.
Business rule in S4/HANA:
All asset sub numbers will be migrated as a regular asset number. System validation is created to prevent the use of sub-assets in S/4HANA.
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
1. | PF2 and WP2 | ANLA-BUKRS | Company Code | S/4HANA | ANLA-BUKRS | Company Code | Map from source to target by using company code mapping table | ||
2. | PF2 and WP2 | ANLA-ANLKL | Asset Class | S/4HANA | ANLA-ANLKL | Asset Class | Map from source to target via Asset Class mapping table | ||
3. | PF2 and WP2 | ANLA-ANLN1 | Asset number | S/4HANA | ANLA-ANLN1 | Asset number | System generated number | ||
4. | PF2 and WP2 | ANLA-ANLN2 | Asset sub-number | S/4HANA | ANLA-ANLN2 | Asset sub-number | |||
5. | PF2 and WP2 | ANLA-TXT50 | Description 1 | S/4HANA | ANLA-TXT50 | Description 1 | Copy value from source to target system | ||
6. | PF2 and WP2 | ANLA-TXA50 | Description 2 | S/4HANA | ANLA-TXA50 | Description 2 | Copy value from source to target system. | ||
7. | PF2 and WP2 | STXH-SPRAS | Language Key for Asset Long text | S/4HANA | STXH-SPRAS | Language Key for Asset Long text | Target Language Key as per Logon language. | ||
8. | PF2 and WP2 | ANLA-XLTXID | General long text | S/4HANA | ANLA-XLTXID | General long text | Copy value from source to target system. | ||
9. | PF2 and WP2 | ANLA-SERNR | Serial number | S/4HANA | ANLA-SERNR | Serial number | Copy value from source to target system. | ||
10. | PF2 and WP2 | ANLA-MENGE | Quantity | S/4HANA | ANLA-MENGE | Quantity | Copy value from source to target system. | ||
11. | PF2 and WP2 | ANLA-MEINS | Base unit of measure | S/4HANA | ANLA-MEINS | Base unit of measure | Copy value from source to target system. | ||
12. | DCT or PF2 and WP2? | ANLA-INVNR | Inventory Number | S/4HANA | ANLA-INVNR | Inventory Number | |||
13. | PF2 and WP2 | ANLA-XHIST | Manage historically | S/4HANA | ANLA-XHIST | Manage historically | Default “X” for all assets. | ||
14. | PF2 and WP2 | ANLA-IVDAT | Last Inventory On | S/4HANA | ANLA-IVDAT | Last Inventory On | |||
15. | PF2 and WP2 | ANLA-INKEN | Include asset in inventory list | S/4HANA | ANLA-INKEN | Include asset in inventory list | Extract indicator (INKEN) from table ANKA in target system based on target asset class (ANLKL). | ||
16. | DCT or PF2 and WP2? | ANLA-INVZU | Inventory Note | S/4HANA | ANLA-INVZU | Inventory Note | Copy values from source to target system if maintained in DCT. | ||
17. | PF2 and WP2 | ANLA-AKTIV | Capitalization date | S/4HANA | ANLA-AKTIV | Capitalization date | Copy values from source to target system. | ||
18. | PF2 and WP2 | ANLA-ZUPER | First Acquisition Date | S/4HANA | ANLA-ZUPER | First Acquisition Date | First Acquisition Date – This will be defaulted with Capitalization date. | ||
19. | PF2 and WP2 | ANLA-DEAKT | Deactivation Date | S/4HANA | ANLA-DEAKT | Deactivation Date | Leave as Blank. | ||
20. | PF2 and WP2 | ANLZ-KOSTL | Cost Centre | S/4HANA | ANLZ-KOSTL | Cost Centre | Map from source (latest validity date) to target via Cost Centre mapping table. | ||
21. | PF2 and WP2 | ANLZ-WERKS | Plant | S/4HANA | ANLZ-WERKS | Plant | Map from source (latest validity date) to target via Plant mapping table. | ||
22. | PF2 and WP2 | ANLZ-STORT | Asset location | S/4HANA | ANLZ-STORT | Asset location | Map from source (latest validity date) to target via Location mapping table. | ||
23. | PF2 and WP2 | ANLZ-RAUMN | Room | S/4HANA | ANLZ-RAUMN | Room | Copy value from source (latest validity date) to target system. | ||
24. | PF2 and WP2 | ANLZ-KFZKZ | License Plate No. of Vehicle | S/4HANA | ANLZ-KFZKZ | License Plate No. of Vehicle | Copy value from source to target system. | ||
25. | PF2 and WP2 | ANLZ-XSTIL | Shutdown indicator | S/4HANA | ANLZ-XSTIL | Shutdown indicator | Copy value from source (latest validity date) to target system. | ||
26. | PF2 and WP2 | ANLA-ORD41 | Evaluation group 1 | S/4HANA | ANLA-ORD41 | Evaluation group 1 | Map from source (asset class) to target system via Evaluation Group 1 mapping table | ||
| PF2 and WP2 | ANLA-ORD42 | Evaluation group 2 | S/4HANA | ANLA-ORD42 | Evaluation group 2 | Map from source (asset class) to target system via Evaluation Group 2 mapping table | |||
| PF2 and WP2 | ANLA-ORD42 | Evaluation group 3 | S/4HANA | ANLA-ORD43 | Evaluation group 3 | Map from source (asset class) to target system via Evaluation Group 3 mapping table | ||
| PF2 and WP2 | ANLA-ORD44 | Evaluation group 4 | S/4HANA | ANLA-ORD44 | Evaluation group 4 | Map from source (asset class) to target system via Evaluation Group 4 mapping table | ||
27. | PF2 and WP2 | ANLA-ANLUE | Asset Super Number | S/4HANA | ANLA-ANLUE | Asset Super Number | |||
28. | PF2 and WP2 | ANLA-ANLN1 | Asset Number | S/4HANA | ANLA-AIBN1
| Original asset number or Original Group Asset number | |||
29. | PF2 and WP2 | ANLA-ANLN2 | Asset Sub-Number | S/4HANA | ANLA-AIBN2 | Original Sub-Asset | Original Asset sub-number – Populate this field with the legacy PF2 and WP2 Asset sub-number.
| ||
30. | PF2 and WP2 | ANLA-AIBDT | Original Acquisition Date of AuC/ Transferred Asset | S/4HANA | ANLA-AIBDT | Original Acquisition Date of AuC/ Transferred Asset | Copy value from source to target system. | ||
31. | PF2 and WP2 | ANLA-URJHR | Fiscal Year of Original Acquisition | S/4HANA | ANLA-URJHR | Fiscal Year of Original Acquisition | Copy value from source to target system. | ||
32. | PF2 and WP2 | ANLA-URWRT | Original Acquisition Value | S/4HANA | ANLA-URWRT | Original Acquisition Value | Copy value from source to target system. | ||
33. | DCT | ANLA-POSNR | WBS element | S/4HANA | ANLA-POSNR | WBS element | Copy values from source to target system (Lease asset class). | ||
34. | PF2 and WP2 | ANLB-AFABE | Depreciation area | S/4HANA | ANLB-AFABE | Depreciation area | Map from source to target via Depreciation area mapping table. | ||
35. | PF2 and WP2 | ANLB-AFASL | Depreciation Key | S/4HANA | ANLB-AFASL | Depreciation Key | Map from source to target via Depreciation Key mapping table. | ||
36. | PF2 and WP2 | ANLB- NDJAR | Useful Life | S/4HANA | ANLB- NDJAR | Useful Life | Useful life (Years) defaulted from the new asset class will be overwritten with the useful life from legacy system. | ||
37. | PF2 and WP2 | ANLB- NDPER | Useful Life (Period) | S/4HANA | ANLB- NDPER | Useful Life (Period) | Useful life (Period) defaulted from the new asset class will be overwritten with the useful life from legacy system. | ||
38. | PF2 and WP2 | ANLB- AFABG | Depreciation Start date | S/4HANA | ANLB- AFABG | Depreciation Start date | Depreciation start date defaulted from the Capitalization start date will be overwritten with depreciation start date from legacy system. | ||
39. | PF2 and WP2 | ANLB-SCHRW_PROZ | Scrap value % | S/4HANA | ANLB-SCHRW_PROZ | Scrap value % | Copy value from source to target system. | ||
40. | PF2 and WP2 | ANLB-ANLGR | Group asset | S/4HANA | ANLB- ANLGR | Group asset | Map from source to target via Group asset mapping table. | ||
41. | PF2 and WP2 | ANLB-INBDA | Operating Readiness | S/4HANA | ANLB- INBDA | Operating Readiness | Copy value from source to target system. |
List of Custom Target Reports for this object is maintained here: Conversion Specification - Custom Reports Register.
Transformation Mapping
List of mapping tables where the legacy values will have to SyWay values.
| Mapping Table Name | Mapping Table Description |
|---|---|
Company code | Mapping of legacy company code to SyWay company code |
Asset Class | Mapping of legacy asset Class to SyWay asset class List of SyWay Asset Classes to be is stored in link below: |
Cost center | Mapping of legacy cost centre to SyWay cost centre |
Profit centre | 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 |
Room | Mapping of legacy room to SyWay room |
Evaluation group 1 | Mapping of legacy EG1 to SyWay EG1 |
Evaluation group 2 | Mapping of legacy EG2 to SyWay EG2 |
Evaluation group 3 | Mapping of legacy EG3 to SyWay EG3 |
Evaluation group 4 | Mapping of legacy EG4 to SyWay EG4 |
Investment Reason | Mapping of legacy investment reason codes to SyWay investment reason codes |
Insurance Type | Mapping of legacy insurance type to SyWay insurance type |
Insurance Index Series | Mapping of legacy insurance index series to SyWay insurance index series |
Depreciation area | Mapping of legacy depreciation areas to SyWay depreciation areas |
Depreciation key | Mapping of legacy depreciation key to SyWay depreciation key |
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 in Section "Mapping tables", have the correct values mapped and imported into ADMM. | Data team |
Pre-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
Generation of Pre-load reports | Pre-load reports will have same structure as of load file with additional columns/attributes if required by business to facilitate validations. Main Assets: There will be 3 Pre-load reports generated: 1. Asset Master Main data (General, Time-dependent, Allocations) 2. Asset Depreciation terms data (Depreciation areas, Useful life by Depreciation area and Depreciation Keys) 3. Asset Long Text (if any asset has relevant long text to be migrated) in logon languages |
Reconciliation of record count | Main Assets Total number of main Assets in the extract is compared against total number of main assets in the legacy system. Less: 1. All main assets under companies and plant or cost centre NOT in Scope. 2. Total number of AUCs in the legacy system. 3. Non-Relevant records (Deactivated Main Assets, Main assets dropped via Relevancy criteria -refer section 2 Conversion Scope). 4. Other constraints/errors. Add: New main assets populated in DCT Total Number of Records to load: 1. Asset Master Main data : 2. Asset Depreciation terms data: Total number of records for Main assets multiply by the number of depreciation areas defined in the Chart of Depreciation. |
Compliance check | ??? |
Accuracy
| Task | Action |
|---|---|
Mandatory field mapping and transformation
| Obtain a list of the fields to be populated with values from mapping files (Refer to section "Mapping tables") and ensure all these fields contain S/4HANA values. Review the data report to ensure mapping value is not missing in ADMM. Capture errors in the Data Error report. |
Business
Completeness
| Task | Action |
|---|---|
Verify record count in Pre-load reports by region
| In legacy system, execute Asset Balances report (S_ALR_87011963 – Asset Balances - by Asset Number) and ensure “Current book value” is selected to obtain a list of active posted assets to be migrated for the companies in scope for each region. Compare the count in this report and assets populated in DCT against the count of main assets to be loaded in Pre-load. |
Verify Relevancy rules applied
| In Legacy system, execute Unposted Asset report (S_ALR_87012056 - Directory of Unposted Assets) to retrieve the list of unposted assets with deactivation date = Blank. These assets should not appear in the Pre-load report. Leverage the List of Unposted Assets relevant for migration in ADMM for any unposted asset flagged as relevant for migration as the asset fulfils the Relevancy criteria. (Section "Conversion Scope"). |
Accuracy
| Task | Action |
|---|---|
Conversion accuracy | Verify all main assets are transformed accurately as per endorsed transformation/mapping rules. Review List of Error reports in ADMM for any mismatch or missing transformed values. |
Load
Data Loading will be done using the migration cockpit object and format of which is attached here:
Source data for Fixed asset (incl. balances and transactions).xml
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 the load tools are transported into the correct ADMM instance. | Data team |
2. | Ensure Pre-load sign-offs are obtained. | Data team |
3. | Load main assets with capitalization date. | |
4. | Load main assets without any capitalization date as it requires a separate load tool. | |
5. | Import the main asset numbers created in S/4HANA and use the original asset number and sub-number =’0’ to link the general long text in the load files to the correct asset number in S/4 HANA. | Data team |
6. | Load asset Long text using main asset number in S/4HANA. | Data team |
7. | Load asset Super number using main asset number in S/4HANA | Data team |
8. | Generate the post load reports in ADMM. | Data team |
9. | Log errors as defects, if any and address resolutions. Close defects. | Data team |
10. | Resolve defects via data update or upload and re-generate post load reports if necessary. | Data team |
11. | Business to validate the post load files as part of post-load validation, raise data defects or provide the post-load sign-off. | Data team |
12. | Repeat steps 8 to 10 if necessary. | Data team |
Load Phase and Dependencies
Pre Cutover is the phase as to when the load for this object will occur.
Configuration
| Item # | Configuration Item |
|---|---|
1. | Company code-related configuration (Chart of Depreciation per country, Plant, Location, Asset Class, Depreciation areas, Depreciation keys, Asset Number Range Interval). |
2.
| Asset Data Transfer Configuration · Transfer date – Last day of the month prior to go-live · Legacy Data Transfer Status = In Preparation · Document type – “UE” |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
| list the exact title of the conversion object of only the immediate predecessor – this will then confirm the DDD (Data Dependency Diagram) | |
| 1074 | Cost Centre Master |
Error Handling
| Error Type | Error Description | Action Taken |
|---|---|---|
Configuration | Revaluation values in Depreciation area XX is not allowed. | Engage functional team to expedite and fix the error in the system by allowing Revaluations (Acquisition/Ord.Depreciation) to be posted to the impacted depreciation area/chart of depreciation in transaction code OADB |
Invalid Data | Relevant cost centre is not valid in the validity of time dependent data in the Asset master to be loaded. | Check whether the validity of time dependent data in cost centre needs to be changed. |
Post-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
Reconciliation of Total Record Count | Total number of records loaded for (Main Assets, Depreciation terms) will be generated in the Post-load reports in ADMM. Main Assets Total no. of Main assets in the Post Load report is compared against total number of main assets in the pre-load reports by region. Less: Any errors during load. |
Mandatory fields check | Review the post load file and note the records that failed the mandatory fields check. Below are the mandatory fields: · Asset Class · Company Code · Description · Serial Number (for assets of certain classes) TBC · Cost Centre · Plant Depreciation terms · Depreciation Key · Useful Life Year (except for keys *000) and Period (except for keys *0000) · Ordinary Depreciation Start Date |
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 ADMM 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. Main Assets: There will be 3 post load reports generated in ADMM for key fields comparison: 1. Asset Master data (General, Time-dependent, Allocations) 2. Asset Depreciation terms data (Depreciation areas, Useful life and Depreciation Keys by Depreciation area) 3. Asset Long Text (if any asset has relevant long text to be migrated) in logon languages 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 |
|---|---|
Check accuracy of field values | Based on the field checks report from the Data Team, conduct a sample check to prove accuracy of the values in S/4 HANA against the source (Pre-load report or PF2 and WP2 system). Suggested sample size is 1 per company code, per asset class. |
Key Assumptions
- Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
- Fixed Asset is in scope based on data design and any exception requested by business.
- Asset Master cleansing task is completed.
- All assets flagged for deletion must be deactivated (i.e. populate the deactivation date field).
See also
Change log
Workflow history
| Title | Last Updated By | Updated | Status | |
|---|---|---|---|---|
| There are no pages at the moment. | ||||