PF2

Relevant fixed asset master records extracted from the source system and transformed according to the target data into a pre-load reports.

WP2

Relevant fixed asset master records extracted from the source system and transformed according to the target data into a pre-load reports.

ANLA

BUKRS

Company Code

Must be valid company code in company code configuration (table T001)

ANLA

ANLKL

Asset Class

Must be valid in asset class configuration (table ANKA). 

ANLA

Main Asset number

ANLA

Asset sub-number

System generated number

The system automatically assigns sub-asset number 0 by default to every asset created. However, the creation of additional sub-assets/child assets is not permitted in the global process designs for S/4HANA.

All sub-assets will be migrated as main asset.

ANLA

Asset description

ANLA

Additional asset description

For migrated assets, this field will be migrated as it is.

This field is only required if a meaningful description of the asset's nature goes beyond 50 chars and hence can't be captured in its full length in field ANLT-TXT50 due to field length constraints.

ANLH

Asset main no. text

ANLA

Indicator: Long text active

ANLA

Serial number

ANLA

Quantity

ANLA

Base unit of measure

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:

- Intangible Assets
- AuC Assets
- RoU 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

Inventory Number

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/4HANA on which the Fixed Asset is installed must be maintained in this field. (This will be finalized by 24 Oct)

Below are the steps in sequence:

1. Load Fixed Asset Master
2. Load Equipment master
3. For Capital Spares, assign Equipment number into field "Inventory Number" 

ANLA

Last Inventory on

This field is only relevant for all Fixed Assets except for:

- RoU Assets (exempted from physical inventory counts)
- AuC assets (exempted from physical inventory counts)

It captures the date of the last asset sighting as part of the physical inventory count process.

For migrated assets, the date from the legacy systems shall be adopted.

ANLA

Include asset in inventory list

For migrated assets, Checkbox (Defaulted to “X”)

This indicator shall be set by default for all Fixed Assets except for:

- RoU Assets (exempted from pyhical inventory counts)
- AuC assets (exempted from pyhical inventory counts)

All tangible Fixed Assets may be subjected to physical inventory counts. By setting this indicator, they will be included in SAP standard reports specifically designed for the physical inventory count process.

ANLA

Inventory Note

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

Capitalization date

For migrated assets, the values from the legacy system shall be adopted.

Must be in date format

ANLA

First Acquisition Date

For migrated assets, the values from the legacy system shall be adopted.

Must be in date format

ANLA

Deactivation on

ANLZ

Cost Centre

ANLZ

Profit Centre

The profit center is derived from the cost center 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, the profit center must be maintained in the Fixed Asset master. And also, to be able to report Fixed Asset registers by profit center going forward.

Must be valid profit center.

ANLZ

Plant

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 assets to facilitate the physical inventory count and tax determination processes. The following exceptions apply as the below types of assets do not form part of the physical inventory count process and do not require plant-based tax determination procedures:

- RoU assets (exempted from physical inventory counts)
- AuC assets (exempted from physical inventory counts)

ANLZ

Location

For migrated asset, location must be done based on a mapping table (old value in ECC to new value in S4). 

Must be valid Location (T499S-STAND) assigned to plant above in configuration (Table T499S)

ANLZ

Room

ANLZ

License Plate No. of Vehicle

ANLZ

Asset shutdown indicator

ANLA

Evaluation group 1

Must be valid in Evaluation group 1 in configuration (Tables T087)

It will be migrated based on a mapping table of Evaluation Group 1

ANLA

Evaluation group 2

Must be valid in Evaluation group 2 in configuration (Tables T087)

It will be migrated based on a mapping table of Evaluation Group 2

ANLA

Evaluation group 3

Must be valid in Evaluation group 3 in configuration (Tables T087)

It will be migrated based on a mapping table of Evaluation Group 3

ANLA

Evaluation group 4

Must be valid in Evaluation group 4 in configuration (Tables T087)

It will be migrated based on a mapping table of Evaluation Group 4

ANLA

Investment reason

No business requirement identified to use this field in S/4 HANA.

ANLA

Asset Super Number

ANLA

Key for sorting according to assignment numbers

No business requirement identified at Syensqo to use this field.

ANLA

Indicator: Historical management

No business requirement identified at Syensqo to use this field.

ANLA

Account number of vendor (other key word)

It will be migrated based on a mapping table of Vendor, provided that the vendor is relevant for BP master creation in S/4HANA.

ANLA

Original asset number or Original Group Asset number

For migrated assets, the legacy asset number is captured in this field.

ANLA

Original Sub-Asset

For migrated assets, the legacy asset sub-number is captured in this field.

ANLA

Original Acquisition Date of AuC/ Transferred Asset

Migrate as it is 

ANLA

Fiscal Year of Original Acquisition

ANLA

Original Acquisition Value

ANLA 

WBS element

This field is not used due to reasons below:

a. It will lead to inconsistencies in terms of data governance as some Fixed Assets have it and others don't.

b. The asset could point to WBS elements that weren't migrated across to S/4 HANA as they are from closed projects. 

ANLA

Classification Key

ANLV

Insurance type

ANLV

Index series

ANLB

Depreciation area

ANLB

Depreciation Key

ANLB

Useful Life

ANLB

Useful Life (Period)

ANLB

Depreciation Start date

ANLB

Scrap value %

For legacy assets, scrap value percentages shall be adopted unless they are related to corporate (IFRS) depreciation areas. Scrap value percentages must not be used for the leading corporate (IFRS) depreciation areas (areas 01-04 and 99)

ANLB

Group asset

No business requirement identified to use group assets in S/4 HANA.

Note: Legacy group assets will be split proportionally into the child asset's tax GAAP depreciation areas in ECC before migration to S/4HANA.

ANLB

Operating Readiness

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 objects^1. or Line-item settlement type of Asset Under Construction (AUC) or assigned to any relevant open Purchase Orders.^2.

Refer to following data objects:

1. Object 1027 (WBS - CAPEX/OPEX Settlement Rule)
2. Object 9045 (Open Purchase Orders)

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

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, 
cleansing report will be created to list down assets that have an inventory date less than 1 Nov 2023 for PF2 and 1 Nov 2024 for WP2

For PF2:
Any assets with an inventory date less than 1 Nov 2023 should be checked and potentially retired as part of the data cleansing exercise

For WP2:
Any assets with an inventory date less than 1 Nov 2024 should be checked and potentially retired as part of the data cleansing exercise

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

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

Action item:

• Business must review these assets whether to retire the assets or post the debit memo to bring it at least to zero

Report that shows Asset balance booked directly to GL (without posting to Fixed Asset subledger) (Transaction code ABST2)

Action item:

• Create asset master and post asset acquisition or scrap the balance from GL.

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.

Extract the asset description of field ANLA-TXT50 and ANLA-TXA50 for business to translate it into English

Action item:

• Business to translate asset description into English.

Scrap values must not be used for the leading corporate (IFRS) depreciation areas (depreciation area 01-04 and 99)

For legacy assets, scrap values shall be adopted unless they are related to corporate (IFRS) depreciation areas.

Action item:

• Business to cleanse assets that have Scrap Value in S4/HANA target depreciation area 01-04 and 99

Report to list down the group assets with the underlying active assets 

Rule 1: Company codes must be in scope.

Rule 2: Indicator Asset is a group asset (ANLA-XANLGR) is “X”

Rule 3: Has Deactivation date = BLANK or current year.

Result: List of group assets.

Extract the underlying assets by specifying the list of group assets in table ANLB

Action item:

• Business to embed the tax depreciation values of the group asset proportionally across all underlying individual assets which make up the group assets.

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

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

1.      

PF2 and WP2

ANLA

Company Code

S/4HANA

ANLA

Company Code

Map from source to target by using company code mapping table

2.      

PF2 and WP2

ANLA

Asset Class

S/4HANA

ANLA

Asset Class

Map from source to target via Asset Class mapping table

3.      

PF2 and WP2

ANLA

Asset number

S/4HANA

ANLA

Asset number

System generated number

4.      

PF2 and WP2

ANLA

Asset sub-number

S/4HANA

ANLA

ANLN2

5.      

PF2 and WP2

ANLA

Description 1

S/4HANA

ANLA

Description 1

Copy value from source to target system

6.      

PF2 and WP2

ANLA

Description 2

S/4HANA

ANLA

Description 2

Copy value from source to target system.

7.      

PF2 and WP2

STXH

Language Key for Asset Long text

S/4HANA

STXH

Language Key for Asset Long text

Target Language Key as per Logon language.

8.      

PF2 and WP2

ANLA

General long text

S/4HANA

ANLA

General long text

Copy value from source to target system.

9.      

PF2 and WP2

ANLA

Serial number

S/4HANA

ANLA

Serial number

Copy value from source to target system.

10.   

PF2 and WP2

ANLA

Quantity

S/4HANA

ANLA

Quantity

Copy value from source to target system.

11.   

PF2 and WP2

ANLA

Base unit of measure

S/4HANA

ANLA

Base unit of measure

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:

- Intangible Assets
- AuC Assets
- RoU Assets

For assets of type 'Land and Building' an alternate unit of measure 'M2' can be maintained.

Map from source to target via unit of measure mapping table

12.   

PF2 and WP2

ANLA

Inventory Number

S/4HANA

ANLA

INVNR

Inventory Number

Copy value from source to target system 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. This is still subject to DA review and endorsement. which will be finalized by 24 Oct.

Hence, object 1002 must be loaded first then this field will be updated with equipment number for capital spares.

14.   

PF2 and WP2

ANLA

Last Inventory On

S/4HANA

ANLA

IVDAT

Last Inventory On

15.   

 PF2 and WP2

ANLA

Include asset in inventory list

S/4HANA

ANLA

Include asset in inventory list

Checkbox (Defaulted to “X”)

16.   

PF2 and WP2

ANLA

Inventory Note

S/4HANA

Inventory Note

Migrate with the existing values in the legacy system. This will be updated with the new target values as per S/4 design after the first inventory count cycle after go live.

17.   

PF2 and WP2

ANLA

Capitalization date

S/4HANA

Capitalization date

Copy values from source to target system.

18.   

PF2 and WP2

ANLA

First Acquisition Date

S/4HANA

First Acquisition Date

First Acquisition Date – This will be defaulted with Capitalization date.

19.   

PF2 and WP2

ANLA

Deactivation Date

S/4HANA

ANLA

Deactivation Date

Copy value from source to target system.

20.   

PF2 and WP2

ANLZ

Cost Centre

S/4HANA

ANLZ

Cost Centre

Map from source (latest validity date) to target via Cost Centre mapping table.

21.   

PF2 and WP2

ANLZ

Plant

S/4HANA

ANLZ

Plant

Map from source (latest validity date) to target via Plant mapping table.

22.   

PF2 and WP2

ANLZ

Asset location

S/4HANA

ANLZ

Asset location

Map from source (latest validity date) to target via Location mapping table.

23.   

PF2 and WP2

ANLZ

Room

S/4HANA

ANLZ

Room

Copy value from source (latest validity date) to target system.

24.   

PF2 and WP2

ANLZ

License Plate No. of Vehicle

S/4HANA

ANLZ

License Plate No. of Vehicle

Copy value from source to target system.

25.   

PF2 and WP2

ANLZ

Shutdown indicator

S/4HANA

ANLZ

Shutdown indicator

Copy value from source (latest validity date) to target system.

26.   

PF2 and WP2

ANLA

Evaluation group 1

S/4HANA

ANLA

Evaluation group 1

Map from source to target system via Evaluation Group 1 mapping table

 28.

PF2 and WP2

ANLA

Evaluation group 3

S/4HANA

ANLA

Evaluation group 3

Map from source to target system via Evaluation Group 3 mapping table

 29.

PF2 and WP2

ANLA

Evaluation group 4

S/4HANA

ANLA

Evaluation group 4

Map from source to target system via Evaluation Group 4 mapping table

30.

PF2 and WP2

ANLA

Asset Number

S/4HANA

ANLA

AIBN1

Original asset number

31.

PF2 and WP2

ANLA

Asset Sub-Number

S/4HANA

ANLA

Original Sub-Asset

Original Asset sub-number – Populate this field with the legacy PF2 and WP2 Asset sub-number. 

32.

PF2 and WP2

ANLA

Original Acquisition Date of AuC/ Transferred Asset

S/4HANA

ANLA

Original Acquisition Date of AuC/ Transferred Asset

Copy value from source to target system.

33.

PF2 and WP2

ANLA

Fiscal Year of Original Acquisition

S/4HANA

ANLA

Fiscal Year of Original Acquisition

Copy value from source to target system.

34.

PF2 and WP2

ANLA

Original Acquisition Value

S/4HANA

ANLA

Original Acquisition Value

Copy value from source to target system.

35.

PF2 and WP2

ANLB

Depreciation area

S/4HANA

ANLB

Depreciation area

Map from source to target via Depreciation area mapping table.

36.

PF2 and WP2

ANLB

Depreciation Key

S/4HANA

ANLB

Depreciation Key

Map from source to target via Depreciation Key mapping table.

37.

PF2 and WP2

ANLB

Useful Life

S/4HANA

ANLB

Useful Life

Useful life (Years) defaulted from the new asset class will be overwritten with the useful life from legacy system.

38.

PF2 and WP2

ANLB

Useful Life (Period)

S/4HANA

ANLB

Useful Life (Period)

Useful life (Period) defaulted from the new asset class will be overwritten with the useful life from legacy system.

39.

PF2 and WP2

ANLB

Depreciation Start date

S/4HANA

ANLB

Depreciation start date defaulted from the Capitalization start date will be overwritten with depreciation start date from legacy system.

PF2 and WP2

ANLB

Asset scrap value

S/4HANA

ANLB

Asset scrap value

Copy value from source to target system unless they are related to corporate (IFRS) depreciation areas.

41.

PF2 and WP2

ANLB

Scrap value %

S/4HANA

ANLB

Scrap value %

Copy value from source to target system unless they are related to corporate (IFRS) depreciation areas.

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:

SyWay_asset_classes&fields - Google Sheets

Unit of measure

Mapping of legacy unit of measure to SyWay unit of measure

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 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

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

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

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 2 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)

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

???

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.

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").

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.

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

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 9A  

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.

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:

·       Company Code

·       Asset Class

·       Asset Description

·       Asset Main Number Text

·       Cost Centre

·       Profit Centre

Depreciation terms

·       Depreciation Key 

·       Useful Life Year (except for keys *000) and Period (except for keys *0000)

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 2 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)

Any mismatch will be reported under the Post Load – Error report.

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.

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.