PF2

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

WP2

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

ANLA

BUKRS

Company Code

ANLA

Main Asset number

ANLA

Asset sub-number

System generated number and mandatory

ANLA

ANLKL

Asset Class

ANLA

Fiscal year in which first acquisition was posted

ANLA

Period in which first acquisition was posted

ANLA

Asset value date of the first posting

ANLA

Asset capitalization date

ANLA

Deactivation on

ANLA

Evaluation group 1

ANLA

Evaluation group 2

ANLA

Evaluation group 3

ANLA

Evaluation group 4

ANLA

Account number of vendor (other key word)

ANLA

Manufacturer of asset

ANLA

Property Classification Key

ANLA

Original asset number or Original Group Asset number

ANLA

Original Sub-Asset

ANLA

Original Acquisition Date of AuC/ Transferred Asset

ANLA

Quantity

ANLA

Base unit of measure

ANLA

Include asset in inventory list

ANLA

Last Inventory on

ANLA

Inventory Note

ANLA

Inventory Number

ANLA

Company ID of Trading Partner

ANLA

Asset description

ANLA

Additional asset description

ANLA

Evaluation group 5

ANLA

Serial number

ANLA

Reason for Environmental Investment

ANLB

Depreciation area

ANLB

Depreciation Start date

ANLB

Depreciation Key

ANLB

Useful Life

ANLB

Useful Life (Period)

ANLB

Asset scrap value

ANLB

Scrap value %

ANLB

Group asset

ANLZ

Cost Centre

ANLZ

Profit Centre

ANLZ

Plant

ANLZ

Location

ANLZ

Room

ANLZ

License Plate No. of Vehicle

ANLV

Insurance type

ANLV

Index series

ANLV

Base insurable value

ANLH

Asset main no. text

ANLZ

Asset shutdown indicator

C2 (Data can be loaded into SAP but not Business Ready)

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 and is not RoU asset class and is not asset class Shares

Rule 3: Has Deactivation date = BLANK

Rule 4: Has Creation date > 12 months ago from extraction date.

Rule 5a: Has capitalization date = BLANK or

Rule 5b:  Has capitalization date populated but no entry is found in ANLC (Asset Value Fields) table for the asset in all depreciation areas.

Rule 6: Does not appear in the settlement rule of any relevant cost objects. 

Region

Country

Company code

Asset number

Asset Sub-Number

Asset Class

Description

Deactivation date

GL Account

Capitalization date

Current NBV

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: Asset class is not Asset under Construction and is not RoU asset and is not asset class Shares

Rule 3: Has Deactivation date = BLANK.

Rule 4: Has Last Inventory on Date = BLANK or less than 1 Nov 2023 for PF2 and 1 Nov 2024 for WP2

Region

Country

Company code

Asset number

Sub-Number

Description

Asset Class

Last Inventory on

Inventory Note

Cost Centre

Profit center

Capitalization Date

Report "Fixed Assets with negative net book value in real depreciation areas and relevant for S/4HANA migration"

Action item:

• Business must review these assets whether to retire the assets or transferred to an asset with a positive amount linked to the same project

Rule 1: Company codes must be in scope.

Rule 2: Asset class is not Asset under Construction and is not RoU asset and is not asset class Shares

Rule 3: Has Deactivation date = blank or current year

Rule 4: Table ANLC is showing negative NBV in real depreciation area

Region

Country

Company code

Asset number

Asset Sub-Number

Asset Class

Description

Deactivation date

Deprecation area

Current NBV for real depreciation areas

Extract Table ANLA to list down the assets in scope for this object 1070 so business can identify manually which assets that represent capital spart parts or not.

Rule 1: Company codes must be in scope.

Rule 2: Asset class is not Asset under Construction and is not RoU asset and is not asset class Shares

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

Region

Country

Company code

Asset number

Asset Sub-Number

Asset Class

Description

Inventory Number

Asset Super Number

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.

Rule 1: Company codes must be in scope.

Rule 2: Asset class is not Asset under Construction and is not RoU asset and is not asset class Shares

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

Region

Country

Company code

Asset number

Asset Sub-Number

Asset Class

Description

Asset Main Number Text

Scrap values must not be used for the S/4HANA leading corporate (IFRS) depreciation areas (i.e. depreciation areas 01-04 and 99)

Note:

99 is a technical depreciation area, wouldn't have a depreciation area equivalent in ECC.

02 and 03 are newly introduced and wouldn't have an equivalent in ECC

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 legacy depreciation area mapped to depreciation area 01 in S/4.

Note:

Depreciation area 50 (PF2) must be mapped to area 01 (S/4).

Depreciation area 01 (WP2) must be mapped to area 01 (S/4).

Rule 1: Company codes must be in scope.

Rule 2: Asset class is not Asset under Construction and is not RoU asset and is not asset class Shares

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

Rule 4:  Legacy depreciation area 50 (PF2) and 01 (WP2) is mapped to S/4 depreciation area 01

Region

Country

Company code

Asset number

Asset Sub-Number

Asset Class

Description

Asset Main Number Text

Scrap value in legacy depreciation area 50 (PF2) and 01 (WP2)

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

Action item:

In ECC, business to assign the information below for depreciation area 15:

• depreciation key
• useful life (year and month)
• deprecation start date
• expired useful life (year and month)

This is as preparation to migrate to S/4HANA

Rule 1: Company code 5955

Rule 2: In table ANLB, specify group asset is not equal to blank.

Result: List of underlying assets for each group asset.

Rule 3: Table ANLA, list the down the underlying assets from rule 2 and filter only the active assets (i.e. deactivation date is blank)

Result:

List of group assets with the underlying active assets 

Populate information below for each group asset:

• depreciation key
• useful life (year and month)
• deprecation start date
• expired useful life (year and month)

1.      

Extract all main 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 asset master records in Req#2 above from ANLZ table in PF2 and WP2.

Syniti team

4.

Extract Depreciation Terms Data of the asset master in Req#2 from ANLB table in PF2 and WP2.

Syniti team

5.

Extract Asset Main Number Text of asset master records in Req#2 above from ANLH table in PF2 and WP2.

Syniti 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 main assets and sub numbers 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

1.      

PF2 and WP2

ANLA

Company Code

S/4HANA

ANLA

Company Code

Value Mapping.

Map from source to target by using company code mapping table.

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

2.

PF2 and WP2

ANLA

Asset number

S/4HANA

ANLA

Asset number

System generated number.

3.

PF2 and WP2

ANLA

Asset sub-number

S/4HANA

ANLA

ANLN2

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.

Note: All sub-assets (with sub number 1,2,3, etc) will be migrated as main asset with sub number 0

4.

PF2 and WP2

ANLA

Asset Class

S/4HANA

ANLA

Asset Class

Value Mapping.

Map from source to target via Asset Class mapping table.

Must be valid in asset class configuration (Table ANKA (Asset Class: General Data) and ANKB (Asset Class: Depreciation area))

5.

Copy from legacy.

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

Note: This field is not listed in LTMC template

6.

Copy from legacy

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

Note: This field is not listed in LTMC template

7.

PF2 and WP2

ANLA

Asset value date of the first posting

S/4HANA

ANLA

Asset value date of the first posting

Copy from legacy.

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

Note: This field is not listed in LTMC template

8.

PF2 and WP2

ANLA

Capitalization date

S/4HANA

Capitalization date

Copy from legacy.

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

9.

PF2 and WP2

ANLA

Deactivation Date

S/4HANA

ANLA

Deactivation Date

Copy from legacy.

Assets that are deactivated in the current year will be migrated. Therefore, this field is only applicable for company codes which are in Group 1 go live.

Group 1 go live date is 1 July 2028

Group 2 go live date is 1 Jan 2029

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.

10.

PF2 and WP2

ANLA

Evaluation group 1

S/4HANA

ANLA

Evaluation group 1

Value mapping.

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

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

11.

Value mapping.

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

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

12.

PF2 and WP2

ANLA

Evaluation group 3

S/4HANA

ANLA

Evaluation group 3

Value mapping.

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

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

13.

PF2 and WP2

ANLA

Evaluation group 4

S/4HANA

ANLA

Evaluation group 4

Value mapping.

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

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

14.

PF2 and WP2

ANLA

Account number of vendor (other key word)

S/4HANA

ANLA

Account number of vendor (other key word)

Value mapping.

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

15.

PF2 and WP2

ANLA

Manufacturer of asset

S/4HANA

ANLA

HERST

Manufacturer of asset

Rule.

This field is only required for assets that have value in field "Trading Partner" in ECC.

This field shall be used to capture additional free-text information on the asset's origin required for tax or other types of audits where tracing of an asset's origin is a crucial piece of information.

E.g. for migrated assets from legacy systems, this field will display the old asset number (ANLA-AIBN1) from the legacy asset in the legacy systems together with trading partner information if the asset was acquired via intercompany transactions in the legacy system and the trading partner relates to an affiliated entity that no longer exists in S/4HANA (e.g. due to divestments). 

Logic:

1.Filter assets that value in field "Trading Partner" in ECC.

2.If the entity doesn't exist in trading partner mapping, concatenate the ECC value of Trading Partner (ANLA-VBUND), ANLA-AIBN1 (Original asset number) and ANLA-AIBN2 (Original Sub-Asset) and store it into this field ANLA-HERST.
3.If the entity exists in trading partner mapping, concatenate the ECC value of ANLA-AIBN1 (Original asset number) and ANLA-AIBN2 (Original Sub-Asset) and stored it into this field ANLA-HERST.

16.

PF2 and WP2

ANLA

Property Classification Key

S/4HANA

ANLA

VMGLI

Property Classification Key

Value mapping.

Map from source to target system via Property Classification Key mapping table. 

The property classification key is required in some countries to perform property tax reporting (e.g. France) to local authorities.

This is only required in some countries as per localization requirements for asset classes related to land and property.

17.

PF2 and WP2

ANLA

Asset Number

S/4HANA

ANLA

AIBN1

Original asset number

Copy from legacy. This is a cross-field copying.

Populate this field with the legacy PF2 and WP2 main asset

18.

PF2 and WP2

ANLA

Asset Sub-Number

S/4HANA

ANLA

Original Sub-Asset

Copy from legacy. This is a cross-field copying.

Populate this field with the legacy PF2 and WP2 asset sub-number. 

19.

PF2 and WP2

ANLA

Original Acquisition Date of AuC/ Transferred Asset

S/4HANA

ANLA

Original Acquisition Date of AuC/ Transferred Asset

Copy from legacy

20.

PF2 and WP2

ANLA

Quantity

S/4HANA

ANLA

Quantity

Copy from legacy.

Quantities captured in the legacy systems shall be retained.

21.

PF2 and WP2

ANLA

Base unit of measure

S/4HANA

ANLA

Base unit of measure

Value mapping.

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

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

22.

 PF2 and WP2

ANLA

Include asset in inventory list

S/4HANA

ANLA

Include asset in inventory list

Defaulted to “X”

All tangible and intangible 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.

23.

PF2 and WP2

ANLA

Last Inventory On

S/4HANA

ANLA

IVDAT

Last Inventory On

Copy from legacy.

The date from the legacy systems shall be adopted. 

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

24.

PF2 and WP2

ANLA

Inventory Note

S/4HANA

Inventory Note

Copy from legacy.

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, which 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.

25.

PF2 and WP2

ANLA

Inventory Number

S/4HANA

ANLA

INVNR

Inventory Number

• For all assets except capital spares, copy from legacy
• For capital spares, the new equipment number from S/4HANA on which the Fixed Asset is installed must be maintained into field "Inventory number" in S/4 Asset master. (Rule and Value mapping)

Note:

For capital spares, the sequence steps are described as below:
1. As part of cleansing activities, business must identify manually by assigning "Capital Spares" into field "Asset Super Number" in ECC for asset master that represent “Capital Spares” 
2. As part of cleansing activities, business must assign the old Equipment number/Functional Location into field "Inventory Number" in asset master in ECC. (In some cases, they don't have equipment currently and can only have Functional Location). For this Functional Location, at least one equipment will be created in S/4 so we would map the old Functional Location to the new equipment.
3. Load object 1002 (equipment master)
4. Load object 1070 (Fixed Asset master) where field "Inventory Number" stores the S/4 equipment number (by using mapping value between old equipment number/Functional Location (ECC) to S/4 equipment number)

26.

PF2 and WP2

ANLA

Trading Partner

S/4HANA

ANLA

Trading Partner

Value mapping

• If the entity exists as a trading partner in S/4, it will be migrated based on a mapping table of Trading Partner.
• if the entity doesn't exist as a trading partner in S/4, this field ANLA-VBUND will be blank.  

27.

PF2 and WP2

ANLA

Asset description

S/4HANA

ANLA

Description 1

Copy from legacy

28.

PF2 and WP2

ANLA

Additional asset description

S/4HANA

ANLA

Description 2

Copy from legacy

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.

29.

PF2 and WP2

ANLA

Evaluation group 5

S/4HANA

ANLA

Evaluation group 5

Value mapping.

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

Must be valid in Evaluation group 5 in configuration (Tables T087G)

30.

PF2 and WP2

ANLA

Serial number

S/4HANA

ANLA

Serial number

31

PF2 and WP2

ANLA

Reason for Environmental Investment

S/4HANA

ANLA

Reason for Environmental Investment

Value mapping.

Map from source to target via Reason for Environmental Investment mapping table.

32.

PF2 and WP2

ANLB

Depreciation area

S/4HANA

ANLB

Depreciation area

Value mapping.

Map from source to target via Depreciation area mapping table.

33

PF2 and WP2

ANLB

Depreciation Start date

S/4HANA

ANLB

Copy from legacy

34,

PF2 and WP2

ANLB

Depreciation Key

S/4HANA

ANLB

Depreciation Key

Value mapping.

It will be migrated based on a mapping table of depreciation key

35.

PF2 and WP2

ANLB

Useful Life

S/4HANA

ANLB

Useful Life

Copy from legacy

36.

PF2 and WP2

ANLB

Useful Life (Period)

S/4HANA

ANLB

Useful Life (Period)

Copy from legacy

37.

PF2 and WP2

ANLB

Asset scrap value

S/4HANA

ANLB

Asset scrap value

Rule and copy from legacy.

Scrap value shall be adopted unless they are related to corporate (IFRS) depreciation areas. Scrap value must not be used for the leading corporate (IFRS) S/4 depreciation areas (areas 01-04 and 99)

38.

PF2 and WP2

ANLB

Scrap value %

S/4HANA

ANLB

Scrap value %

Rule and copy from legacy.

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) S/4 depreciation areas (areas 01-04 and 99)

39.

PF2 and WP2

ANLZ

Cost Centre

S/4HANA

ANLZ

Cost Centre

Value mapping.

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

40.

S/4HANA

ANLZ

Profit Centre

System generated.

The profit center is derived from the cost center maintained in the asset master record. In source systems, Profit center is not populated in asset master.

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.

41.

PF2 and WP2

ANLZ

Plant

S/4HANA

ANLZ

Plant

Value mapping.

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

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. 

42.

PF2 and WP2

ANLZ

Asset location

S/4HANA

ANLZ

Asset location

Value mapping.

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

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

43.

PF2 and WP2

ANLZ

Room

S/4HANA

ANLZ

Room

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

44.

PF2 and WP2

ANLZ

License Plate No. of Vehicle

S/4HANA

ANLZ

License Plate No. of Vehicle

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

45.

Value mapping.

It will be migrated based on a mapping table of insurance type

46.

47.

Copy from legacy, unless we have a change in functional area currency for some entities.

Note: Currently none of the entities in scope swap functional currency

This was more a generic comment to keep in mind in the solution design of the migration tool should we encounter this scenario in the future.

48.

49.

Copy from legacy.

For migrated assets, this field shall be used to capture the English translation of the asset description

50.

PF2 and WP2

ANLZ

Shutdown indicator

S/4HANA

ANLZ

Shutdown indicator

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

Company code

Mapping of legacy company code to SyWay company code

Asset Class

Mapping of legacy asset Class to SyWay asset class

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

Property Classification Key

Mapping of legacy Property Classification Key to SyWay Property Classification Key

Trading Partner

Mapping of legacy Trading Partner to SyWay Trading Partner

Equipment number

Mapping of legacy Equipment number to SyWay Equipment number

Functional Location

Mapping of legacy Functional Location to SyWay Equipment number

Evaluation Group 5

Mapping of legacy Evaluation Group 5 to SyWay Evaluation Group 5

Reason for Environmental Investment

Mapping of legacy Reason for Environmental Investment to SyWay Reason for Environmental Investment

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 company codes not in scope.

2.     Total number of AUCs in the legacy systems

3.     Total number of RoU assets in the legacy systems

4.     Total number of Asset Shares in the legacy systems

5.     Non-Relevant records (Deactivated assets in the previous years, Main assets dropped via Relevancy criteria - refer to Conversion Scope).

6.     Other constraints/errors.

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. 

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 signoffs are obtained.

Data team

3.

Load fixed assets

4.

Generate the post load reports in ADMM.

Data team

5.

Log errors as defects, if any and address resolutions. Close defects.

Data team

6.

Resolve defects via data update or upload and re-generate post load reports if necessary.

Data team

7.

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

8.

Repeat steps 4 to 6 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 center 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 center 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.