Create an utility field in Syniti ADMM to collect 'CONTRACT_OBJECT_TYPE'

Terminated or concluded lease contracts must be closed and all related postings need to be posted and deactivated.

Rule: 

1. Get contract numbers from VICNCN-BUKRS where BUKRS represents company codes in scope. and VICNCN-RECNENDABS is greater than or equal to 'Cutover date'

2. From the output in step-1, pass VICNCN-INTERNO to VICERULE-INTERNO and VICERULE-VALIDTO is equal to blank or converted value to '99991231' or Blank (or converted value 99991231 / 00000000) to get active record where VICERULE-CONSBEG is latest time internal for all the valuation rules VICERULE-CERULE where VICERULE-CESLTYPE is 'A'. After this, pass asset numbers from VICERULE-ASSETOBJNUMBER into ANLA where ANLA-DEACT is equal to blank. Finally, pass VICNCN-INTERNO and check VICNCN-RECNENDABS is less than or equal to 'Cutover date' or 'Blank (or converted value 99991231)'. and VICERULE-PROBABLEEND is less than or equal to 'Cutover date' to get active record where VICERULE-CONSBEG is latest time internal and VICERULE-PROBABLEEND is NE to blank for all the valuation rules VICERULE-CERULE.

Review all Lease POs against active IFRS 16 Lease Contracts that they match the commitments in source system. Otherwise, correct the incorrect values i.e., PO values, Qty, Lease dates and so on.

Rule:

Get contract numbers from VICNCN-BUKRS where BUKRS represents company codes in scope and VICNCN-RECNENDABS is greater than  or equal to 'Cutover date' or  'Blank' to get source PO numbers VICNCN-ZZVEND where PO number is numerical but not consistent at source as below.

1) PO number with no line item specified: Check all the line items of PO where KNTTP is 'L' or 'H and highlight in comments as per below findings:
1.1. If all Line items are flagged for Deletion (EKPO-LOEKZ <>Blank) then report shows "PO has deletion flag for all line items where AAC is L or H"
1.2. If PO has any of the active line (EKPO-LOEKZ =Blank) then report shows 'PO has active line item where AAC is L or H'

2) PO number with specific line item:
If ZZVEND contains PO number and that PO number with specific line item should not have block/delete indicator EKPO-LOKEZ is equal to 'Blank' where that PO line item is EKPO-KNTTP is 'L' or 'H' then report shows "PO and Line Item - Deletion Flag". Else, report shows "PO and Line Item - Active"

3) PO number is available but none of the line item belongs to Leases:
If ZZVEND contains PO number and that PO number having multiple lines where EKPO-KNTTP is not equal to 'L' or 'H' then report shows "PO active but none of the line item belongs to L or H"

4) Alpha / Alpha Numeric:
If ZZVEND contains Alpha or Alpha Numeric then report show "Alpha / Alpha Numeric"

5) PO number is blank (No Data):
If ZZVEND is BLANK then report show "PO number is blank (No Data)"

6) PO - Not Found:
If ZZVEND contains Numeric but PO Number is not available in EKKO then report shows "PO - Not Found".

1. Get contract numbers from VICNCN-BUKRS where BUKRS represents company codes in scope and VICNCN-RECNENDABS is greater than or equal to 'Cutover date' to get source PO numbers VICNCN-ZZVEND where PO number is numerical but not consistent at source as below.

i) If ZZVEND contains 4513261339/40 - in this case, there are two PO's. 4513261339 and 4513261340. These POs should not have any block/delte indicator EKPO-LOEKZ is equal to blank. This needs to be reported if an associated contract is active from step-1
ii) If ZZVEND contains 4512363924/130 - in this case, the PO number 4512363924 and PO Item No. 130. These POs should not have any block/delete indicator EKPO-LOEKZ is equal to blank. This needs to be reported if an associated contract is active from step-1
iii) If ZZVEND contains 'Alpha numeric' and this is not present in table EKPO-EBELN. This needs to be reported if an associated contract is active from step-1
iv) If ZZVEND contains no details - This needs to be reported if an associated contract is active from step-1

Process

Activity

Extract

Extract involves collecting data from the source.

The source is a SAP system, Extract means to pull the required data from source systems into repository using Syniti ADMM.  There are 2 steps for this method:

1. Perform full data extraction from relevant RE-FX tables in the source system(s).
2. 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 SAP Data Migration Cockpit or any other standard 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 S4HANA system using load tool. 
2. Once the data is loaded to target system, it will be extracted and prepared for Post Load Data Validation.

Extract all active and released RE-FX Lease Contracts from table VICNCN in PF2 and WP2.

Extract Object data of RE-FX Lease Contracts from table VIBDOBJASS / VIBDCNSUBJECT in PF2 and WP2

Extract Posting Terms data of RE-FX Lease Contracts from table VITMPY in PF2 and WP2

Extract Frequency Terms data of RE-FX Lease Contracts from table VITMRH in PF2 and WP2

Extract Business Partner (aka Vendors/Customers) data of RE-FX Lease Contracts from table VIBPOBJREL in PF2 and WP2

Extract Conditions data of RE-FX Lease Contracts from table VICDCOND in PF2 and WP2

Extract Valuation Rules data of RE-FX Lease Contracts from table VICERULE in PF2 and WP2

Contracts which are already concluded and no longer valuated shall not be migrated

Data cleansing of legacy RE-FX lease contracts where contracts that are no longer active will be concluded / deactivated 

All active IFRS 16 lease contracts will include associated Lease POs. This has been included in the cleansing report since there are no lease POs for the Transport lease category in legacy

The Purchase Orders for RE-FX Lease Contracts will be reviewed to ensure that the PO commitments match the lease contracts data for the remaining lease duration at a given mock cut-off date.

1 

Data team

2      

Data team

3      

Syniti team

4      

Syniti team

5      

Syniti team

6      

Data team

7

Syniti team

8      

Syniti team

9

Syniti team

The contract end date must be the same as legacy PF2 and WP2
Rule: Copy from field End of Term VICNCN-RECNENDABS. If End of Term VICNCN-RECNENDABS is equal to blank, go to table RETM_PERIOD_S-RNENDNEW to get contract end date

Note: RETM_PERIOD_S is SAP structure and unable to get SAP table for this field. However, this will be checked during the design phase to see if any suitable table is available.

Custom field: Map this field based on legacy Vendor Contract ID
Go to table VICNCN-BUKRS where BUKRS is the company code in scope VICNCN-BUKRS where BUKRS represents company codes in scope and VICNCN-RECNENDABS is greater than or equal to 'Cutover date' and get convergence ID VICNCN-ZZVENDID

Copy from the source as-is and if vendor contract id is equal to PO number and if that PO number is available in value mapping table obtained from the 'Open PO Migration' then update converted PO number in the target else, source value as-is.

Note: This custom field will be added to the LTMC migration template via Configuration throughout the functional design as it's not available while designing this specification

Value Mapping from legacy PO and Item number to target PO and Item number. Custom field: Map this field based on legacy PO number and update with converted target PO number. 

If source PO number is not available in value mapping table obtained from the 'Open PO Migration' then blank.

Note:
 - This custom field will be added to the LTMC migration template via Configuration throughout the functional design as it's not available while designing this specification
 - For each active lease contract, an associated lease PO and item number (assumed 1 PO with 1 line item number) will be available from source to target as per the target design.
 - Open PO's managed via object 9045

Value Mapping from legacy PO and Item number to target PO and Item number. Custom field: Map this field based on legacy PO item number and update with converted target PO item number.

Copy from the source as-is and if vendor contract id is equal to PO number and that if that PO number is available in value mapping table then update converted PO number in the target else, source value as-is. 
Note:
 - This custom field will be added to the LTMC migration template via Configuration throughout the functional design as it's not available while designing this specification
 - For each active lease contract, an associated lease PO and item (assumed 1 PO with 1 line item number) will be available from source to target as per the target design.
 - Open PO's managed via object 9045

Value mapping: Cost Center and WBS mappings from source to target

Rule to cost center: Go to VICNCN-RECNNR and get VICNCN-OBJNR, pass OBJNR onto VIBDOBJASS-OBJNRSRC. From the output, get VIBDOBJASS-OBJNRTRG. Go to table  VIBDCNSUBJECT-OBJNR and get account assignment object VIBDCNSUBJECT-ACCTOBJNR.

Rule to get WBS element:

Go to VICNCN-RECNNR and get VICNCN-OBJNR, pass OBJNR onto VIBDOBJASS-OBJNRSRC. From the output, get VIBDOBJASS-OBJNRTRG. Go to table PRPS and pass OBJNR (from VIBDOBJASS-OBJNRTRG) and get WBS element PRPS-POSNR.

Example: 

WP2:  PR00239343 -  we have to recover the wbs element  with value from PRPS-POSID where PRPS-OBJECT = PR00239343.

For conversion: This filed will be concatenated with controlling area followed by slash i.e. '/'. Ex: CO01/XXXXXX, where XXXXXX is a cost center
Note: Some contracts are assigned to WBS elements besides the cost centers. For Lease contracts, it was decided that the WBS elements are only for Statistical (field VIBDOBJSS-ASSIGNONLYINFO) i.e., informational purpose and Cost centers are real cost object.

Populate this field from the legacy PF2 and WP2. This is applicable to S4 contract type 'ZI04 and ZI05' only.
Rule: Go to VICNCN-BUKRS = Pass company codes that are applicable and get VICNCN-INTERNO, pass INTERNO onto VICNMEASCN-INTERNO to get differing measurement object VICNMEASCN-OBJNRTRG and replace object ID 'J4' with 'COB'. Example: J40010002074, J40020002085 from legacy, the object id is J4 and object number 0010 and this will be replaced in S4 with COB 0010 and so on

Note: This field will be configured and added to the LTMC template during the design as it's currently unavailable.

Value mapping: Measurement Type mappings from source to target
Rule: Go to VICNCN-BUKRS = Pass company codes that are applicable and get VICNCN-INTERNO, pass INTERNO onto VICNMEASCN-INTERNO to get Measurement Type VICNMEASCN-MEAS

Note: This field will be configured and added to the LTMC template during the design as it's currently unavailable.

Populate this field with the legacy PF2 and WP2
Rule: Go to VICNCN-BUKRS = Pass company codes that are applicable and get VICNCN-INTERNO, pass INTERNO onto VICNMEASCN-INTERNO to get amount VICNMEASCN-MEASVALUE

Note: This field will be configured and added to the LTMC template during the design as it's currently unavailable.

Populate this field with the legacy PF2 and WP2
Rule: Go to VICNCN-BUKRS = Pass company codes that are applicable and get VICNCN-INTERNO, pass INTERNO onto VICNMEASCN-INTERNO to get amount VICNMEASCN-MEASUNIT

Note: This field will be configured and added to the LTMC template during the design as it's currently unavailable.

Populate this field with the legacy PF2 and WP2
Rule: Go to VICNCN-BUKRS = Pass company codes that are applicable and get VICNCN-INTERNO, pass INTERNO onto VICNMEASCN-INTERNO to get Measurement valid from VICNMEASCN-VALIDFROM

Note: This field will be configured and added to the LTMC template during the design as it's currently unavailable.

Populate this field with the legacy PF2 and WP2
Rule: Go to VICNCN-BUKRS = Pass company codes that are applicable and get VICNCN-INTERNO, pass INTERNO onto VICNMEASCN-INTERNO to get Measurement valid from VICNMEASCN-VALIDTO

Note: This field will be configured and added to the LTMC template during the design as it's currently unavailable.

Value mapping: Profit Center mappings from source to target
Rule: Go to VICNCN-BUKRS = Pass company codes that are applicable and get VICNCN-INTERNO, pass INTERNO onto VITMOA-INTERNO to get Profit Center VITMOA-PRCTR from the output where Valid To=99991231. 

Validation report for Profit center must be matched with the one assigned in the cost center mentioned in the Tab-Object under 'ID Part of Account Assignment Object'. CSKS-PRCTR.

For conversion - Left with blank for now.

This rule will only apply if TAXJD is applicable in target. Populate this field with the legacy PF2 and WP2 
Rule: Go to VICNCN-BUKRS = Pass company codes that are applicable and get VICNCN-INTERNO, pass INTERNO onto VITMOA-INTERNO to get Tax Jurisdiction  VITMOA-TXJCD from the output.
Note: This is dependant on Functional design in Syway. Therefore, this will be decided at a later state whether to populate or not.

Value mappings: Account Determination Value mapping from source to target

Will be provided with a value mapping table with these fields to get the ACCDETKEY because ACCDETKEY is blank in both PF2 and WP2

1. CONTRACT TYPE
2. CNSUBJECTTYPE (From table VIBDCNSUBJECT)  ACCTDETKEY

Rule: Go to VICNCN-BUKRS = Pass company codes that are applicable and get VICNCN-INTERNO, pass INTERNO onto VITMPY-INTERNO to get Account Determination Value VITMPY-ACCDETKEY from the output.
If this is blank in legacy, will need to follow the value mappings in the combination of Contract Type and Object Type to get Account Determination Value.

For Conversion: Left with blank for now.

Populate this field with the legacy PF2 and WP2 
Rule: Go to VICNCN-BUKRS = Pass company codes that are applicable and get VICNCN-INTERNO, pass INTERNO onto VITMPY-INTERNO to get Tax Jurisdiction  VITMPY-TXJCD from the output.
Note: This is a dependant on Functional design in Syway. Therefore, a final decision will be made at a later state.

Value mappings: Condition Type mappings from source to target
Go to VICNCN-BUKRS = Pass company codes that are applicable and get VICNCN-INTERNO, pass INTERNO onto VICDCOND-INTERNO and VICDCOND-CONDDELETE is NE to 'X' and VICDCOND-CONDTYPE is NE to ''ZDTO-Net Worth Value' to get active condition types from the output.

For conversion: Will need to add extra constant condition type 'Z999 - Net Worth Value' for each IFRS 16 contract and Valid from is to be updated with default to each 'Cutover date' and the unit price will be obtained from the ROU Assets object 9108. Probably, this will qualify for value mapping with the combination of Co Code, Contract number and ROU Asset number to get ROU Asset net book value for constant condition i.e., Z999.

Populate this field with the legacy PF2 and WP2
Go to VICNCN-BUKRS = Pass company codes that are applicable and get VICNCN-INTERNO, pass INTERNO onto VICDCOND-INTERNO and VICDCOND-CONDDELETE is NE to 'X' and VICDCOND-CONDTYPE is NE to 'ZDTO'. From the output get VICDCOND-INTERNO, pass INTERNO onto VICDCONDCALC-INTERNO and VICDCOND-VICDCONDCALC-VALUEVALIDTO is greater than or equal to 'Cutover date' to get condition valid from VICDCONDCALC-CONDVALIDFROM for all active conditions.

For conversion: Will need to add extra constant condition type 'Z999 - Net Worth Value' for each IFRS 16 contract and Valid from is to be updated with default to each 'Cutover date'

Populate this field with the legacy PF2 and WP2
Go to VICNCN-BUKRS = Pass company codes that are applicable and get VICNCN-INTERNO, pass INTERNO onto VICDCOND-INTERNO and VICDCOND-CONDDELETE is NE to 'X' and VICDCOND-CONDTYPE is NE to 'ZDTO'. From the output get VICDCOND-INTERNO, pass INTERNO onto VICDCONDCALC-INTERNO and VICDCOND-VALUEVALIDTO is greater than or equal to 'Cutover date' to get condition unit price from VICDCONDCALC-UNITPRICE CONDVALUE for all active conditions.

Note: Please check SAP table TCURX to apply correct decimal places. Ex: JPY. The amount value as displayed to users in SAP screens and reports 10025 but internal database will store it as 100.25. During data conversion, these internal amounts must be converted to external amounts to ensure accuracy and consistency in the target Syway.

For conversion: Unit price for constant condition type  'Z999 - Net Worth Value' for each IFRS 16 contract will be obtained from the value mapping with the combination of Co Code, Contract number and ROU Asset number to get ROU Asset net book value for constant condition i.e., Z999.

Rule: Get contract numbers from VICNCN-BUKRS where BUKRS represents company codes in scope and VICNCN-RECNENDABS is greater than or equal to 'Cutover date' to get active contract numbers. From the output, go to table VICERULE and pass VICERULE-INTERNO to get Asset object number VICERULE-ASSETOBJNR. The asset object number is a combination of Asset object type + Co Code + Asset number + Sub number
- Asset object type - first 2 char 'AN'
- Co Code - next 4 char XXXX
- Asset Number - next 12 char 280000000003 (This asset number will be managed via object number 9108 and will probably have a construction page or value mapping)
- Asset sub number - last 4 char 0000
Example: ANXXXX2800000000030000

For each valuation rule of the lease contract follows target valuation rule ZIFRS16 and ZLOC_BS_XX will be assigned to the corresponding ROU Asset that will be updated with the combination of 'Co Code (BUKRS) + '/' + ROU Asset + '/' + '0'
 - ROU Asset: Migrating ROU assets will be managed via object # 9108 and the mapping from source to target ROU asset will be available after loading object 9108. So, Lease contracts migration (Object 1076) is a dependent on ROU Assets (Object 9108).

Company code

Mapping of legacy company code to SyWay company code

Lease Contract Type

Mapping of legacy contract type to SyWay contract type

Object Type

Mapping of legacy Object type to SyWay Object type

Account Determination Value

Mapping of legacy Account Determination Value to SyWay Account Determination Value

Cost center

Mapping of legacy cost centre to SyWay cost centre

Profit center

Mapping of legacy profit centre to SyWay profit centre

R2R Data Team to ensure that all fields listed below pass the checks:

1. Mandatory Fields
2. Field and Value Mapping Correctness
3. Null Checks
4. Filed Length Checks
5. All necessary config values
6. Custom fields 

Business Data Owner/s to verify that all the Lease contracts are transformed accurately as per endorsed ETL rules. 

Review List of Error reports for any mismatch or missing transformed values.

1

Ensure Pre-load sign-offs are obtained

2

Ensure the load tools are transported into the correct tool instance

R2R Data team

3

S2P data team to inform R2R data team about the deactivation of RE-FX PO-add on custom table (custom table yet to be developed by the functional team) in S4HANA before loading the Lease related Open PO's (CS # 9045). This will also be required in the cutover activities list.

S2P Data team / R2R Data team

4

Go to <Load tool>

R2R Data team

5

Load 1 or 2 records for "Lease Contracts" to validate if data is loaded successfully without errors. If errors, log defects and obtain resolution 

R2R Data team

6

Proceed with full load if step 4 is successful and validated

R2R Data team

7

Validate few records loaded by accessing standard transactions or tables from S/4HNA E.g. RECISCN or FIORI: Contracts Management

R2R Data team

8

Generate post load report if step 7 is validated

R2R Data team

Configuration

Number ranges for Lease Contracts per company code

Consult Functional team to set up the number ranges using t.code FOIX_NR

Total number of records loaded for Lease contracts and associated Lease PO's will be generated in the Pre and Post-load reports by company code in ADMM. 

Update the following two fields with S4HANA transformed contract number for Lease-out scenario:

1. Main Contract Co code: Update with corresponding S4HANA company code from value mapping
2. Main Contract: Update with S4HANA contract number against corresponding source contract number.

Post-load reports will have the same structure as the load file and some additional columns as required to facilitate the post load validation.

Leverage the Syniti ADMM tool to create a Post load report that reports S/4 HANA loaded records along with the legacy values side-by-side to allow for 100% check of all these fields in the shortest possible time. If any mismatch, they will report under 'Error' for corrective action.