You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

Status

  Update in progress

OwnerCASTRO MONCAYO-ext, Jose Luis 
Stakeholders

Purpose

The purpose of this document is to define the conversion approach to create 1056 - Resources in S/4 HANA.

Resources are used to identify the production lines, equipment and all the machines related to the production execution process. Resources are the main data to be used to design the Master Recipes for all the Syensqo plants. 



Conversion Scope

The scope of this document covers the approach for converting active 1056- Resources from Legacy Source Systems into S/4HANA following the Resource Master Data Design Standard.


The data from legacy system includes:

  1. Active Resources as of > three (3) years with history and/or included in active Recipes / Process Orders
  2. Resources W/O Deletion Flag
  3. Resources that will be migrated to the To-Be Plant Mapping (Take in consideration the To-Be definition of Plants

The data from legacy system excludes:

  1. Inactive Resources with more than three (3) years.
  2. Resources marked for deletion
  3. Resources belonging to Deleted plants (New plant Definition according with the To-Be Plant mapping)


List of source systems and approximate number of records
SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

PF2, WP2

Production Versions will be extracted from PF2 and WP2  

15,000S/4 HANA15,000
DCTProduction Versions for Plant / Material combination which do not have data existing from PF2 and PF2TBDS/4 HANATBD










Additional Information

Multi-language Requirement

English , French, Chinese, Spanish

Document Management

Legal Requirement

N/A

Special Requirements

N/a

N/a




Target Design

The technical design of the target for this conversion approach.


TableFieldData ElementField DescriptionData TypeLengthRequirement

MDS Field Mapping in Scope


Field Value in MDS

1CHRDOBJTYCR_OBJTYObject typeCHAR2SIn Scope
2CHRDOBJIDCR_OBJIDObject IDNUMC8S
3CHRDARBPLARBPLWork CenterCHAR8RTBD
4CHRDWERKSWERKS_DPlantCHAR4RTBD
5CHRDVERWEAP_VERWEWork Center CategoryCHAR4R

0008 Processing Unit
6CHRDPLANVAP_PLANVKey for task list usageCHAR3R

0008 Master Recipe + Process Order
7CHRDSTANDAP_STANDWork center locationCHAR10C

MFG Execution Config Register
8CHRDVERANAP_VERANPerson Responsible for the Work CenterCHAR3C

MFG Execution Config Register
9CHRDVGWTSVORGSCHLStandard Value KeyCHAR4R

TBD
10CHRDVGM01AP_VGW_MESRule for standard value maintenanceCHAR1C
11CHRDVGM02AP_VGW_MESRule for standard value maintenanceCHAR1C
12CHRDVGM03AP_VGW_MESRule for standard value maintenanceCHAR1C
13CHRDVGM04AP_VGW_MESRule for standard value maintenanceCHAR1CIn Scope
14CHRDVGM05AP_VGW_MESRule for standard value maintenanceCHAR1C
15CHRDVGM06AP_VGW_MESRule for standard value maintenanceCHAR1C
16CHRDZGR01IDZEITGRADKey for performance efficiency rateCHAR3NU
17CHRDZGR02IDZEITGRADKey for performance efficiency rateCHAR3NU

18CHRDZGR03IDZEITGRADKey for performance efficiency rateCHAR3NU

19CHRDZGR04IDZEITGRADKey for performance efficiency rateCHAR3NU

20CHRDZGR05IDZEITGRADKey for performance efficiency rateCHAR3NU

21CHRDZGR06IDZEITGRADKey for performance efficiency rateCHAR3NU

22CHRDPRVBEPRVBEProduction Supply AreaCHAR10C

23CHRDRGEKZRGEKZAPIndicator: BackflushingCHAR1C

24CHRDSTEUSSTEUSControl KeyCHAR4R

25CHRDVGE01VGWRTEHUnit of measure for the standard valueUNIT3C

26CHRDVGE02VGWRTEHUnit of measure for the standard valueUNIT3C

27CHRDVGE03VGWRTEHUnit of measure for the standard valueUNIT3C

28CHRDVGE04VGWRTEHUnit of measure for the standard valueUNIT3C

29CHRDVGE05VGWRTEHUnit of measure for the standard valueUNIT3C

30CHRDVGE06VGWRTEHUnit of measure for the standard valueUNIT3C

31CHRDKAPARKAPARTCapacity categoryCHAR3C

32CHRDKAPNAMEKAPNAMECapacity nameCHAR8C

33CHRDFORT1AP_FORM_T1Formula for setup timeCHAR6NU


TBD

34CHRDFORT2AP_FORM_T2Formula for the duration of processing timeCHAR6NU


TBD
35CHRDFORT3AP_FORM_T3Formula for teardown timeCHAR6NU


TBD
36CHRDFORTNAP_FORM_TNFormula for the duration of other types of int. processingCHAR6NU


TBD
37CRTXOBJTYCR_OBJTYObject typeCHAR2S

38CRTXOBJIDCR_OBJIDObject IDNUMC8S

39CRTXSPRASSPRASLanguageCHAR1R

40CRTXKTEXTCR_KTEXTShort descriptionCHAR40R

41CRCAOBJTYCR_OBJTYObject TypeCHAR2S

42CRCAOBJIDCR_OBJIDObject IDNUMC8S

43CRCACANUMCR_CAPNUMCapacity allocation numberCHAR6S


TBD
44CRCAFORK1AP_FORM_K1Formula for Setup Capacity RequirementsCHAR6NU

45CRCAFORK2AP_FORM_K2Formula for Processing Capacity RequirementsCHAR6NU

46CRCAFORK3AP_FORM_K3Formula for Teardown Capacity RequirementsCHAR6NU

47CRCAFORKNAP_FORM_KNFormula for Other Capacity RequirementsCHAR6NU

48CRCAKAPIDKAPIDCapacity IDNUMC8S

49KAKTKAPIDKAPIDCapacity IDNUMC8S

50KAKTSPRASSPRASLanguageCHAR1C

51KAKTKTEXTCR_KTEXTCapacity TextCHAR40C

52CRCOOBJTYCR_OBJTYObject typeCHAR2S

53CRCOOBJIDCR_OBJIDObject IDNUMC8S

54CRCOLASET#N/AActivity Type SetCHAR6S

55CRCOENDDAENDDATUMEnd DateDATS8C



56CRCOBEGDABEGDATUMStart DateDATS8C

57CRCOKOKRSKOKRSCO AreaCHAR4R

58CRCOKOSTLKOSTLCost CenterCHAR10R

59CRCOLSTAR1LSTARActivity TypeCHAR6R

60CRCOLEINH1LEINHActivity UnitUNIT3C

61CRCOFORML1FORMLFormula key for costingCHAR6R

62CRCOLSTAR2LSTARActivity TypeCHAR6R

63CRCOLEINH2LEINHActivity UnitUNIT3C

64CRCOFORML2FORMLFormula key for costingCHAR6R

65CRCOLSTAR3LSTARActivity TypeCHAR6R

66CRCOLEINH3LEINHActivity UnitUNIT3C

67CRCOFORML3FORMLFormula key for costingCHAR6R

68CRCOLSTAR4LSTARActivity TypeCHAR6R

69CRCOLEINH4LEINHActivity UnitUNIT3C

70CRCOFORML4FORMLFormula key for costingCHAR6R

71CRCOLSTAR5LSTARActivity TypeCHAR6R

72CRCOLEINH5LEINHActivity UnitUNIT3C

73CRCOFORML5FORMLFormula key for costingCHAR6R

74CRCOLSTAR6LSTARActivity TypeCHAR6R

75CRCOLEINH6LEINHActivity UnitUNIT3C

76CRCOFORML6FORMLFormula key for costingCHAR6R


Data Cleansing

IDCriticalityError Message/Report DescriptionRuleOutputSource System
1056-1C1Resource is not used for the last 3 yearsAll Resources not used for the last 3 years, won't be migratedActive Resources during the last 3 yearsPF2 /WP2
1056-2C1Resource is flagged for deletionAll Resources flagged for deletion won't be migratedResources with NO flag for deletionPF2/WP2
1056-3C1Resources in Plants that are Out of ScopeResources created in Plants Out of Scope won't be migratedResources valid in Active plants (To Be mapping)PF2/WP2
1056-4C1Resources with No formulas for capacity, scheduling or costingResources with missing capacity, Scheduling and costing formulas won't be migrated Only Resources with all formulas will be migratedPF2/WP2
1056-5C1





Conversion Process

The high-level process is represented by the diagram below:


Data Privacy and Sensitivity


Extraction

Extract data from a source into . There are 2 possibilities:

  1. The data exists. connects to the source and loads the data into . There are 3 methods:
    1. Perform full data extraction from relevant tables in the source system(s).
    2. Perform extraction through the application layer.
    3. Only if ; cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
  2. The data does not exist (or cannot be converted from its current state). The data is manually collected by the business directly in . This is to be conducted using DCT (Data Collection Template) in

The agreed Relevancy criteria is applied to the extracted records to identify the records that are applicable for the Target loads

Extraction Run Sheet

Req #Requirement DescriptionTeam Responsible
1Extract data from source system based on relevancy ruleSyWay Data Team
2Google Sheet report pre-populated with PF2 and WP2 information to be generated based on relevancy criteria. SyWay Data Team
3Sinity will extract data and convert it into SQL data base ad share with the teamSinity team




Selection Screen

Selection Ref ScreenParameter NameSelection TypeRequirementValue to be entered/set





















Data Collection Template (DCT)

Target Ready Data Collection Template will be created for data with exception of some fields which require transformation as mentioned in the transformation rule.

DCT Rules

Field NameField DescriptionRule
ARBPLWork CenterTBD - Work Center maybe part of transformation and mapping 
WERKSPlantTBD - Plant maybe part of transformation and mapping
VERWEWork Center CategoryValue set to a default value - 0008 Processing Unit
PLANVKey for task list usage

Value set to a default value - 0008 Master Recipe + Process Order

STANDWork center location

Value set based upon MFG Execution Config Register

VERANPerson Responsible for the Work Center

Value set based upon MFG Execution Config Register

VGWTSStandard Value Key

TBD - Plant maybe part of transformation and mapping

VGM01Rule for standard value maintenance

Value Direct from the current system

VGM02Rule for standard value maintenance

Value Direct from the current system

VGM03Rule for standard value maintenance

Value Direct from the current system

VGM04Rule for standard value maintenance

Value Direct from the current system

VGM05Rule for standard value maintenance

Value Direct from the current system

VGM06Rule for standard value maintenance

Value Direct from the current system

PRVBEProduction Supply Area

Value Direct from the current system

RGEKZIndicator: Backflushing

Value is 'X' or 'Null'

STEUSControl Key

Mandatory Direct from the current system? 

VGE01Unit of measure for the standard value

Value Direct from the current system

VGE02Unit of measure for the standard value

Value Direct from the current system

VGE03Unit of measure for the standard value

Value Direct from the current system

VGE04Unit of measure for the standard value

Value Direct from the current system

VGE05Unit of measure for the standard value

Value Direct from the current system

VGE06Unit of measure for the standard value

Value Direct from the current system

KAPARTCapacity category

Value Direct from the current system

KAPNAMECapacity name

Value Direct from the current system

FORT1Formula for setup time

Registered as Not used, but this is to be decided, current SAP has values

FORT2Formula for the duration of processing time

Registered as Not used, but this is to be decided, current SAP has values

FORT3Formula for teardown time

Registered as Not used, but this is to be decided, current SAP has values

FORTNFormula for the duration of other types of int. processing

Registered as Not used, but this is to be decided, current SAP has values

SPRASLanguage

Value direct from the current SAP system, Languages will need to be configured, mostly set as EN (Language which the Resource is maintained)

KTEXTShort description

Value direct from current SAP system, free text field, brief description of the Resource
















Extraction Dependencies

Item #Step DescriptionTeam Responsible













Transformation

The Target fields are mapped to the applicable Legacy field that will be its source, this is a 3-way activity involving the Business, Functional team and Data team. This identifies the transformation activity required to allow to make the data Target ready:

  1. Perform value mapping and data transformation rules.
    1. Legacy values are mapped to the to-be values (this could include a default value)
    2. Values are transformed according to the rules defined in
  2. Prepare target-ready data in the structure and format that is required for loading via prescribed Load Tool. This step also produces the load data ready for business to perform Pre-load Data Validation

Transformation Run Sheet

Item #Step DescriptionTeam Responsible
1Obtain DCT Sign-off from BusinessSyWay S2P Data Team
2<Add steps from Syniti Migrate here>SyWay S2P Data Team
3Review and Validate Error and Preload ReportsSyWay S2P Data Team
4Generate Load FilesSyWay S2P Data Team


Transformation Rules

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1PF2CRHDARBPLResource IDS4 HANACRHDARBPLResource ID

Look at the file Resources equivalent for Plant - Resource Name as

Existing Plant-New Plant mapping Check Resource name.
































Transformation Mapping

Mapping Table NameMapping Table Description








Transformation Dependencies

List the steps that need to occur before transformation can commence
Item #Step DescriptionTeam Responsible













Pre-Load Validation

Project Team

Completeness

TaskAction
Verify Record CountBusiness Data Owner/s to verify that the total number of relevant records from the the DCT is equal to the total number of records in the Preload and Load Sheets.





Accuracy

TaskAction
Conversion Accuracy

SyWay S2P Data Team to verify that all fields below meet pass the checks:

  1. Mandatory Fields
  2. Field and Value Mapping Correctness
  3. Null Checks
  4. Text Length Checks
Review Error ReportsReview and correct the errors.  Achieve a zero-error record count as much as possible. Raise defects for data remediated and requiring a correction in the source data.



Business

Completeness

TaskAction
Verify Record CountBusiness Data Owner/s to verify that the total number of relevant records from the the DCT is equal to the total number of records in the Preload and Load Sheets.





Accuracy

TaskAction
Conversion AccuracyBusiness Data Owner/s to verify that all the data in the load table/file is accurate as per endorsed transformation/mapping rules (and signed-off DCT data).





Load

The load process includes:

  1. Execute the automated data load into target system using load tool or product the load file if the load must be done manually
  2. Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation

Load Run Sheet

Item #Step DescriptionTeam Responsible
1Go to <Load Tool>SyWay S2P Data Team
2Load 3 records for < > to validate if data is loaded successfully without errorsSyWay S2P Data Team
3

Load 3 records for < > to validate if data is loaded successfully without errors

SyWay S2P Data Team
4Proceed with full load if steps 2 and 3 are validatedSyWay S2P Data Team
5Validate few records loaded by accessing standard transactions from S/4HNA eg. MM03SyWay S2P Data Team
6Generate post load report if step 5 is validatedSyWay S2P Data Team


Load Phase and Dependencies

Configuration

Item #Configuration Item






Conversion Objects

Object #Preceding Object Conversion Approach

list the exact title of the conversion object of only the immediate predecessor – this will then confirm the DDD (Data Dependency Diagram)




Error Handling

Error TypeError DescriptionAction Taken










Post-Load Validation

Project Team

Completeness

TaskAction
Verify CountSyWay S2P Data Team to verify the record count created in target S/4 HANA by accessing post load reports in dspMigrate or standard reports from S/4 HANA.





Accuracy

TaskAction
Verify LogsCheck if there is data that failed to load and perform the necessary actions (e.g. register as post load issue or attempt to load the record again, etc.).





Business

Completeness

TaskAction
Verify CountDownload Post Load Reports from dspMigrate and verify that the record count loaded in the target S/4 HANA is the same count as of the endorsed load file.





Accuracy

TaskAction
Conversion AccuracyVerify that the Material data in target S/4 HANA were loaded correctly via dspMigrate post load reports or standard reports from S/4 HANA.





Key Assumptions

  • Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
  • is in scope based on data design and any exception requested by business.


See also

Change log

Version Published Changed By Comment
CURRENT (v. 14) Apr 29, 2026 14:24 ULLAH-ext, Colin
v. 114 Apr 28, 2026 08:50 ULLAH-ext, Colin
v. 113 Apr 17, 2026 15:50 ULLAH-ext, Colin
v. 112 Apr 17, 2026 14:38 ULLAH-ext, Colin
v. 111 Apr 02, 2026 13:57 ULLAH-ext, Colin
v. 110 Apr 02, 2026 13:25 ULLAH-ext, Colin
v. 109 Apr 02, 2026 12:51 ULLAH-ext, Colin
v. 108 Mar 12, 2026 15:35 ULLAH-ext, Colin
v. 107 Mar 12, 2026 14:56 ULLAH-ext, Colin ADDED OBJTY AND OBJID to DCT for KAKO and KAKT
v. 106 Mar 02, 2026 15:51 ULLAH-ext, Colin

Go to Page History

Workflow history

Title Last Updated By Updated Status  
There are no pages at the moment.

  • No labels