PF2 and WP2

Extraction of the Sender Credit values from settlement that uses primary cost elements for settlement (Table COSP)

PF2 and WP2

Refer to links below to get the corresponding Offsetting GL accounts for each AUC class
PF2_ANKA_AUC Classes.xlsx - Google Sheets
WP2_ANKA_AUC Classes.xlsx - Google Sheets

Note:

There are 3 take-on accounts for Fixed Asset and AUC:

• 1199999 Fixed Asset Take-on Account - Intangibles
• 1299999 Goodwill - Take-on Account
• 1399999 Fixed Asset Tangibles (PP&E) - Take-on Account

Mandatory

Mandatory

Posting Date in the document

Syniti to advise:

Migration Cockpit GL Balance does not have field "Posting Date".

There are 2 options:

1. Syniti to add field "Posting date"
2. Before loading, Posting Date will be maintained in the view FINSV_MIG_CTRL_1

RWCUR

FINS_VWCUR12

RHCUR

Company Code Currency

FINS_VHCUR12

Amount in Company Code Currency

RKCUR

FINS_CURRK

Global Currency (Curr type 30)

Amount in Global Currency (Curr type 30)

ROCUR

FINS_CURR1

Freely Defined Currency 1 (Curr type 31)

OSL

FINS_VOCUR12

Amount in Global Currency (Curr type 31)

Mandatory

Mandatory

Mandatory

Mandatory

Total Value in Transaction Currency

Mandatory

Mandatory

Mandatory

System generated

System generated

System generated

System generated

System generated

System generated

System generated

Settlement rule with field "Account Assignment Category" = G/L with the GL account (which is mapped to Reconciliation Account type A) must be cleansed by Business.

Action item:

Instead of settled to the Balance Sheet GL account (which is FXA Reconciliation Account), business must settle to AUC number

Extract table COBRB:

Company codes in scope

Object Number: PR*

Field KONTY (Acct Assignment Category) = G/L

Field HKONT (G/L account) = 21900100

List of WBS that is settled to GL 21900100 (FA recon account)

Review of assets under construction (AUC) older than 6 months (over 500k €) and older 1 year. The aim is to detect if there is any AUC without any new costs for the last 6 months without capitalization to the fixed asset (FXA). This is the existing process that is happening in PF2 and WP2

WW - FXA.01.08 - Review of assets under construction (AUC) older than 6 months - Sleeping AUC - Finance Service Line - Syensqo - Wiki knowledge base

PF2 - Z1A_AUC_SLEEP

WP2 - ZWFA81B

• Report

PF2 - Use layout /I&D S AUC

WP2 - Use layout /I&D S AUC 2

Identify the WBS items that are in scope to get the asset number for AUC and Final Asset (if any)

a. Get the list of WBS in scope from object 1026.

b. Extract table PRPS by identifying the WBS elements from Step a to get the corresponding object numbers.

c. Extract table COBRB by identifying the object numbers (from Step b) and specify 'FXA' into field "Account Assignment Category" to filter the object numbers belong to CAPEX.

System will provide a report as below that will include the following fields:

Result: Get the AUC and Final Asset (if any) numbers from this report.

Identify Asset Classes for AUC and Final Asset

Extract table ANLA by identifying AUC/Final Asset number from Step 1c to get the corresponding asset classes for AUC and Final Asset.

Identify Asset Classes for AUC and G/L take-on account to be used for posting based on AUC Asset Classes

Extract table ANKA by identifying Asset Classes from Step 2 and number range = 01 to get the asset classes for AUC.

Refer to links below to get the corresponding GL take-on account for each AUC class:

PF2_ANKA_AUC Classes.xlsx - Google Sheets

WP2_ANKA_AUC Classes.xlsx - Google Sheets

There are 3 take-on accounts for Fixed Asset and AUC:

• 1199999 Fixed Asset Take-on Account - Intangibles
• 1299999 Goodwill - Take-on Account
• 1399999 Fixed Asset Tangibles (PP&E) - Take-on Account

Identify Asset Number for AUC

Extract table ANLA by identifying asset classes for AUC and get the asset number for AUC

Identify settlement posting for AUC

The following tables will be used to extract the settlement amount for the object numbers from Step 1

• Primary Cost Total (COSP) table
• Secondary Cost Total (COSS) table 

Go to source systems (PF2 and WP2) Primary Costs Total (Table COSP)

 Go to source systems (PF2 and WP2) Secondary Costs Total (Table COSS) 

From the above, system will generate report as below.

The report will need to be summarized by object number, by original G/L, by extraction as below:

Group 1 Go live (1 July 2028):

• Accumulated balances up to 31 Dec 2026 (Life to Date)
• Accumulated balances 1 Jan - 31 Dec 2027
• Monthly balance from 1 Jan 2028 till 30 June 2028

Group 2 Go live (1 Jan 2029):

• Accumulated balances up to 31 Dec 2026 (Life to Date)
• Accumulated balances up to 1 Jan - 31 Dec 2027
• Monthly balance from 1 Jan 2028 till 31 Dec 2028

Step #4 provides what needs to be posted for each WBS Element. These must be posted by using the original cost element (which will be mapped to S/4HANA cost element). 

To ensure settlement amount is the same as the actual posting

To ensure that all settlement costs have been collected via these tables (COSP & COSS), run a report (transaction code CJI3) to extract all the costs (by excluding Dr/Cr indicator "O") posted to the WBS Element/s to reconcile against the totals extracted from table COSP & COSS. Compare and agree the reconciliation values before progressing further to the next steps.

For each WBS in scope, confirm that the final balance is zero which will ensure that the settlement costs represent all the postings (debit and credit) by WBS Element.

To get the AUC balance

Extract the fixed asset values from table ANEP in source systems (PF2 and WP2) to check what has been posted to the Asset under Construction (AUC) and Final Asset.

 System will generate as below:

This report will need to be summarized by asset number as below:

Group 1 Go live (1 July 2028):

• Accumulated balances up to 31 Dec 2026 (Life to Date)
• Accumulated balances 1 Jan-31 Dec 2027
• Monthly balance from 1 Jan 2028 till 30 June 2028

Group 2 Go live (1 Jan 2029):

• Accumulated balances up to 31 Dec 2026 (Life to Date)
• Accumulated balances 1 Jan-31 Dec 2027
• Monthly balance from 1 Jan 2028 till 31 Dec 2028

Check against the WBS Element postings (CJI3) before loading into S/4HANA.

Run transaction code S_ALR_87011963 (Asset Balances report) for all AUC assets within the relevant company code. Check each individual asset balance before making any posting to a WBS Element.

Post expense with WBS then execute settlement to AUC as below:

Group 1 Go live (1 July 2028):

• Accumulated balances up to 31 Dec 2026 (Life to Date)

Once the AUC balance up to 31 Dec 2026 has been agreed, a statistical posting will be required by WBS and by original G/L account. No settlement is required.

• Accumulated balances 1 Jan-31 Dec 2027

Once the AUC balance up to 31 Dec 2027 has been agreed:

• • • a real posting will be required (document type 9A) by WBS and by original G/L account and run settlement (CJ8G) 
    • reverse the above statistical posting

Please refer to Accounting Journal CS 9031.xlsx - Google Sheets

• Monthly balance from 1 Jan 2028 till 30 June 2028

Once the AUC monthly balance from 1 Jan 2028-30 Jun 2028 has been agreed, a real posting will be required (document type 9A) by month, by WBS and by original G/L account and run settlement (CJ8G)

Note: We need to run settlement for January before doing the February expense posting, etc.

Group 2 Go live (1 Jan 2029):

• Accumulated balances up to 31 Dec 2026 (Life to Date)

Once the AUC balance up to 31 Dec 2026 has been agreed, a statistical posting will be required by WBS and by original G/L account. No settlement is required.

• Accumulated balances up to 31 Dec 2027 (Prior Year)

Once the AUC balance up to 31 Dec 2027 has been agreed:

• • • a real posting will be required (document type 9A) by WBS and by original G/L account and run settlement (CJ8G)
    • reverse the above statistical posting
• Monthly balance from 1 Jan 2028 till 31 Dec 2028 (Prior Year)

Once the AUC monthly balance up from 1 Jan 2028-31 Dec 2028 has been agreed, a posting will be required (document type 9A) by WBS and by original G/L and run settlement (CJ8G)

Note: We need to run settlement for January before doing the February expense posting, etc.

To get the asset classes for Final Asset:

Extract table ANKA by identifying Asset Classes from Step 2 (Section A) and specify number range = 02 

To get the asset numbers for Final Asset:

Extract table ANLA by identifying Asset Classes from Step 1 (Section B)

To get the balance of Final Asset:

Extract the fixed asset values from table ANEP in source systems (PF2 and WP2) to check what has been posted to the Final Asset.

System will generate as below:

This report will need to be summarized by asset number as below:

Group 1 Go live (1 July 2028):

• Accumulated balances up to 31 Dec 2026 (Life to Date)
• Accumulated balances 1 Jan-31 Dec 2027
• Monthly balance from 1 Jan 2028 till 30 June 2028

Group 2 Go live (1 Jan 2029):

• Accumulated balances up to 31 Dec 2026 (Life to Date)
• Accumulated balances 1 Jan-31 Dec 2027
• Monthly balance from 1 Jan 2028 till 31 Dec 2028

 Post statistical posting (T.code KAFD) for the Final Asset based on the balance from Step#5

In ADMM, select Object 9031 and launch this to execute transformation

Syniti Team

Perform transformation for all relevant WBS Elements.

Legacy WBS Element is mapped to S/4HANA WBS elements in mapping table.

Syniti Team

Generate Pre-Load reports in ADMM for the extracted WBS Element amounts.

Syniti Team

Validate the transformed file as part of pre-load validation, raise data defects or provide the pre-load sign-off.

Business

Analyze and resolve any pre-load defects logged by business.

Data Team

Conversion specs mapping "Company Code" (BUKRS: Old Company Code to New Company Code)

Conversion specs mapping "Company Code" (BUKRS: Old Company Code to New Company Code)

 Please refer to Accounting Journal CS 9031.xlsx - Google Sheets where Posting date is specified for each extraction.

 Document date would be the same as Posting Date.

Default to “Data Object 9031”

Specify legacy WBS Element

RWCUR

Transaction Currency

RWCUR

Transaction Currency

RHCUR

RHCUR

RKCUR

Global Currency

ROCUR

Freely Defined Currency 1

Automatic, to be kept blank in load template. This is currency type 31.

Currently legacy does not have group currency amount, this is yet to be confirmed as to how this will be derived

COSP Object Number will identify the WBS Element from PF2 and WP2 (PRPS table) which will map to the S/4HANA WBS Element identified in

WBS mapping table. This mapping will be provided by conversion object 1026 (WBS - CAPEX, OPEX, Statistical).

COSS Object Number will identify the WBS Element from PF2 and WP2 (PRPS table) which will map to the S/4HANA WBS Element identified in

WBS mapping table. This mapping will be provided by conversion object 1026 (WBS - CAPEX, OPEX, Statistical).

The COSP source table stores period-based data in a columnar format, where each period is represented by an amount column suffixed with values such as 001,

002, and so on. To prepare the data for each period, these columns must be pivoted using the remaining attribute columns as qualifiers. The corresponding

period numbers will also be derived during this pivoting process. 

The COSS source table stores period-based data in a columnar format, where each period is represented by an amount column suffixed with values such as 001,

002, and so on. To prepare the data for each period, these columns must be pivoted using the remaining attribute columns as qualifiers. The corresponding

period numbers will also be derived during this pivoting process. 

The COSP source table stores period-based data in a columnar format, where each period is represented by an amount column suffixed with values such as 001, 002, and so on. To prepare the data for each period, these columns must be pivoted using the remaining attribute columns as qualifiers. The corresponding period numbers will also be derived during this pivoting process. 

The COSS source tables store period-based data in a columnar format, where each period is represented by an Amount column suffixed with values such as 001, 002, and so on. To prepare the data for each period, these columns must be pivoted using the remaining attribute columns as qualifiers. The corresponding period numbers will also be derived during this pivoting process. 

Value in Transaction Curr for relevant period

Note:

xxx represent the period

xx represents all periods for previous years. Value type (COSS-WRTTP) must be “4” and Dr/Cr Indicator (COSP-BEKNZ) set to “O - Special: Sender credit from settlement”.

Once the data is collected, the signage must be changed prior to posting. As most of the settlement amounts will be a negative amount, this value must be changed to a positive amount before posting back to the S/4HANA WBS Element. If the settlement amount is a positive value, it must be changed to a negative value.

Logic will be required to determine the posting period from the field name WTGxxx, with xx being the posting month. E.g. 001,002,003, etc.

The extraction must refer as below:

Group 1 go live (1 July 2028) to migrate the above WBS for:

• • Accumulated balance up to 31 Dec 2026 (Life to Date)
  • Accumulated balance from 1 Jan 2027-31 Dec 2027
  • Monthly balance from 1 Jan 2028 till 30 June 2028

Group 2 go live (1 Jan 2029) to migrate the above WBS for:

• • Accumulated balance up to 31 Dec 2026 (Life to Date)
  • Accumulated balance from 1 Jan 2027-31 Dec 2027
  • Monthly balance from 1 Jan 2028 till 31 Dec 2028

Please consider Currency Adjustment During Migration (TCURX Consideration) as described in Appendix B.

Value in Transaction Curr for relevant period

Note:

xxx represent the period

Company code

BUKRS: Old Company Code to New Company Code

GL Accounts

HKONT: Old GL Accounts to New GL Accounts

Profit Centre

PRCTR: Old Profit Centre to New Profit Centre

Asset Number

ANLN1: Old Asset number to New Asset number

WBS Elements

POSID: Old WBS Elements to New WBS Elements

Verify Counts

Data team to verify the load count is the same as per identified data from Primary Cost Total COSP file and Secondary Cost Total COSS file.

Validate

Validate that the extracted values from both tables agree with the total transaction costs excluding settlement for each individual WBS Element

Total by Asset number to compare to the WBS Element value to be posted. The value to be posted against the WBS Element must agree with the value shown for the relevant Asset Under Construction. See section "Extraction run sheet for legacy WBS element settling to AUCs.

Business will use the preload report to validate the number of WBS Elements that will migrate values. 

Validate that the extracted values are identical to those values posted to the WBS Element

Asset Classes

WBS - CAPEX, OPEX, Statistical

GL Account Operational CoA (incl. secondary CE)

Data team to verify the load count is the same as per identified data from Pre Load file

Ensure the Pre-Load report values are the same as in the Post Load Report. These values have to be verified before settling the costs to the AUCs.

Verify Counts

Business to verify the load count is the same as per identified data from Post Load Report.

Ensure the Post Load report values are exactly the same as in the Pre Load report. These values have to be verified before settling the costs to the AUCs.