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

Compare with Current View Page History

« Previous Version 42 Next »

Status

  Update in progress

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

Stand alone rules

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)

Relevancy rule

  1. Material/Plant with history and include active process orders - Materials defined via Status at global and Plant level (MARC/MARA)
  2. Defined materials which are recognised as active and contain 3 years process order history, these are then checked against active BOMS to define Master Recipe at Plant level
  3. Master Recipes defined as per the Material Master containing 3 years Process order History, define the Resource by Plant

Material Plant Active with three years Process order History Red Arrow defines Active BOMS by Plant Red Arrow defines Active Master Recipe by Plant Red Arrow Defines the Resource by Plant.

Plant Merging

Plants will be defined accordingly as some plants will be merged into one plant. Plants will be defined as NEW plant codes and be transformed via a transformation table, which will be contained in Syniti.


List of source systems and approximate number of records
SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

PF2, WP2

Resources will be extracted from PF2 and WP2  

PF2 - 6096 WP2 - 9077

S/4 HANAPF2 - 6096 WP2 - 9077
DCTResources for Plant / Resources combination which do not have data existing from PF2 and WP2
S/4 HANA

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

1CRHDOBJTYCR_OBJTYObject typeCHAR2SIn Scope
2CRHDOBJIDCR_OBJIDObject IDNUMC8S
3CRHDARBPLARBPLWork CenterCHAR8RTBD
4CRHDWERKSWERKS_DPlantCHAR4RTBD
5CRHDVERWEAP_VERWEWork Center CategoryCHAR4R

0008 Processing Unit
6CRHDPLANVAP_PLANVKey for task list usageCHAR3R

0008 Master Recipe + Process Order
7CRHDSTANDAP_STANDWork center locationCHAR10C

MFG Execution Config Register
8CRHDVERANAP_VERANPerson Responsible for the Work CenterCHAR3C

MFG Execution Config Register
9CRHDVGWTSVORGSCHLStandard Value KeyCHAR4R

TBD
10CRHDVGM01AP_VGW_MESRule for standard value maintenanceCHAR1C
11CRHDVGM02AP_VGW_MESRule for standard value maintenanceCHAR1C
12CRHDVGM03AP_VGW_MESRule for standard value maintenanceCHAR1C
13CRHDVGM04AP_VGW_MESRule for standard value maintenanceCHAR1CIn Scope
14CRHDVGM05AP_VGW_MESRule for standard value maintenanceCHAR1C
15CRHDVGM06AP_VGW_MESRule for standard value maintenanceCHAR1C
16CRHDZGR01IDZEITGRADKey for performance efficiency rateCHAR3NU
17CRHDZGR02IDZEITGRADKey for performance efficiency rateCHAR3NU

18CRHDZGR03IDZEITGRADKey for performance efficiency rateCHAR3NU

19CRHDZGR04IDZEITGRADKey for performance efficiency rateCHAR3NU

20CRHDZGR05IDZEITGRADKey for performance efficiency rateCHAR3NU

21CRHDZGR06IDZEITGRADKey for performance efficiency rateCHAR3NU

22CRHDPRVBEPRVBEProduction Supply AreaCHAR10C

23CRHDRGEKZRGEKZAPIndicator: BackflushingCHAR1C

24CRHDSTEUSSTEUSControl KeyCHAR4R

25CRHDVGE01VGWRTEHUnit of measure for the standard valueUNIT3C

26CRHDVGE02VGWRTEHUnit of measure for the standard valueUNIT3C

27CRHDVGE03VGWRTEHUnit of measure for the standard valueUNIT3C

28CRHDVGE04VGWRTEHUnit of measure for the standard valueUNIT3C

29CRHDVGE05VGWRTEHUnit of measure for the standard valueUNIT3C

30CRHDVGE06VGWRTEHUnit of measure for the standard valueUNIT3C

31CRHDKAPARKAPARTCapacity categoryCHAR3R

32CRHDKAPNAMEKAPNAMECapacity nameCHAR8R

33CRHDFORT1AP_FORM_T1Formula for setup timeCHAR6NU


TBD

34CRHDFORT2AP_FORM_T2Formula for the duration of processing timeCHAR6NU


TBD
35CRHDFORT3AP_FORM_T3Formula for teardown timeCHAR6NU


TBD
36CRHDFORTNAP_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

50KAKTSPRASSPRASLanguageCHAR1R

51KAKTKTEXTCR_KTEXTCapacity TextCHAR40R

52CRCOOBJTYCR_OBJTYObject typeCHAR2S

53CRCOOBJIDCR_OBJIDObject IDNUMC8S

54CRCOLASET#N/AActivity Type SetCHAR6S

55CRCOENDDAENDDATUMEnd DateDATS8R


31/12/9999
56CRCOBEGDABEGDATUMStart DateDATS8R

57CRCOKOKRSKOKRSCO AreaCHAR4R

58CRCOKOSTLKOSTLCost CenterCHAR10R

59CRCOLSTAR1LSTARActivity TypeCHAR6C

60CRCOLEINH1LEINHActivity UnitUNIT3C

61CRCOFORML1FORMLFormula key for costingCHAR6R

62CRCOLSTAR2LSTARActivity TypeCHAR6C

63CRCOLEINH2LEINHActivity UnitUNIT3C

64CRCOFORML2FORMLFormula key for costingCHAR6R

65CRCOLSTAR3LSTARActivity TypeCHAR6C

66CRCOLEINH3LEINHActivity UnitUNIT3C

67CRCOFORML3FORMLFormula key for costingCHAR6R

68CRCOLSTAR4LSTARActivity TypeCHAR6C

69CRCOLEINH4LEINHActivity UnitUNIT3C

70CRCOFORML4FORMLFormula key for costingCHAR6R

71CRCOLSTAR5LSTARActivity TypeCHAR6C

72CRCOLEINH5LEINHActivity UnitUNIT3C

73CRCOFORML5FORMLFormula key for costingCHAR6R

74CRCOLSTAR6LSTARActivity TypeCHAR6C

75CRCOLEINH6LEINHActivity UnitUNIT3C

76CRCOFORML6FORMLFormula key for costingCHAR6R

77KAKOKAPIDKAPIDCapacity IDNUMC8S

78KAKOAZMAXKAPANZAHLNo. Ind. CapacitiesINT25NU

79KAKOAZNORKAPANZAHLNo. Ind. CapacitiesINT25R

80KAKOBASNEKAPBASNENDenominator base capDEC5S

81KAKOBASZLKAPBASZHLNumerator base cap.DEC5S

82KAKOBEGZTKAPBEGZTStart TimeINT410R

83KAKOENDZTKAPENDZTEnd TimeINT410R

84KAKOKALIDCR_WFCIDFactory CalendarCHAR2C

85KAKOKAPARKAPARTCapacity categoryCHAR3R

86KAKOMEINSKAPBASISCapacity Base UnitUNIT3R

87KAKOMOSIDSCHGRUPShift GroupingCHAR2C

88KAKONAMEKAPNAMECapacityCHAR8NU

89KAKONGRADNUTZGRADCapacity UtilizationNUMC3R

90KAKOPAUSEKAPPAUSEBreak DurationINT410R

91KAKOPLANRKAPPLANERCapacity Responsible PlannerCHAR3R

92KAKOPOOLKKAP_KZPOOLPooled Capacity IndicatorCHAR1C

93KAKOREFANKAPREFANZNNumber (ref. cap.)INT13C

94KAKOREFAZKAPREFANZZNumber (capacity)INT13C

95KAKOREFIDKAPIDCapacity IDNUMC8C

96KAKOSUPPKKAP_SUPPLYAvail. cap. limitsCHAR1C (if not entered, 100% will be the default)

97KAKOVERSAKAPVERSAKTActive VersionNUMC2R

98KAKOWERKSWERKS_DPlantCHAR4NU

99KAKOKAPIEKAPIDCapacity IDNUMC8NU

100KAKOKAPTERKAP_KZTERRelevant to Finite SchedulingCHAR1C

101KAKOKAPAVOKAP_KZAVOCan be used by several operationsCHAR1C

102KAKOUEBERLASTUEBERLASTOverload (%)NUMC3C

103KAKOKAPLPLKAP_KZLPLNo Long-Term PlanningCHAR1C

104KAKOKAPEHCR_KAPEHCapacity UnitUNIT3C (if PP/DS is used)

105KAKOMEHRKAP_MEHRHas Individual CapacitiesCHAR1C (if PP/DS is used)

106KAKOANG_UNITKAPAZIT_VM_UNITAv. cap. unitUNIT3C (if PP/DS is used)

107KAKOANG_MINKAPAZIT_VM_MINMinimum capacityQUAN13C (if PP/DS is used)

108KAKOANG_MAXKAPAZIT_VM_MAXMax. capacityQUAN13C (if PP/DS is used)


Data Cleansing

Business will perform data cleansing in the current ECC system. This means ECC will serve as the single source of truth for Manufacturing Data prior to the migration to S/4HANA.

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



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/ MS Excel/ SQL 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 Name

Field description

Rule

CRHD-ARBPLWork Center

Represents a machine, group of machines, production line or a person assigned to an operation

Data Type: Character

Length: 8

CRHD-WERKSPlant

Key uniquely identifying a plant

Data Type: Character

Length: 4

CRHD-VERWEWork Center Category

Key differentiating resources according to their category (e.g. resource network, process unit)

Data Type: Character

Length: 4

CRHD-PLANVKey for task list usage

Controls which type of tasks list are allowed to use this resource

Data Type: Character

Length: 3

CRHD-STANDWork center location

Represents the physical location of the resource

Data Type: Character

Length: 10

CRHD-VERANPerson Responsible for the Work Center

The person or group of people who are responsible for the maintenance of the resource - Useful for Reporting purposes

Data Type: Character

Length: 3

CRHD-VGWTSStandard Value Key

The system uses standard values as parameters with origin "standard value" in formulas to calculate execution time, capacity requirements and costs

Data Type: Character

Length: 4

CRHD-VGM01Rule for standard value maintenance

Determines how the system reacts when you enter or do not enter a standard value in an operation of a Master Recipe (must be entered, should be entered, should not be entered, cannot be entered)

Data Type: Character

Length: 1

CRHD-VGM02Rule for standard value maintenance

Determines how the system reacts when you enter or do not enter a standard value in an operation of a Master Recipe (must be entered, should be entered, should not be entered, cannot be entered)

Data Type: Character

Length: 1

CRHD-VGM03Rule for standard value maintenance

Determines how the system reacts when you enter or do not enter a standard value in an operation of a Master Recipe (must be entered, should be entered, should not be entered, cannot be entered)

Data Type: Character

Length: 1

CRHD-VGM04Rule for standard value maintenance

Determines how the system reacts when you enter or do not enter a standard value in an operation of a Master Recipe (must be entered, should be entered, should not be entered, cannot be entered)

Data Type: Character

Length: 1

CRHD-VGM05Rule for standard value maintenance

Determines how the system reacts when you enter or do not enter a standard value in an operation of a Master Recipe (must be entered, should be entered, should not be entered, cannot be entered)

Data Type: Character

Length: 1

CRHD-VGM06Rule for standard value maintenance

Determines how the system reacts when you enter or do not enter a standard value in an operation of a Master Recipe (must be entered, should be entered, should not be entered, cannot be entered)

Data Type: Character

Length: 1

CRHD-PRVBEProduction Supply Area

Serves as a place for interim storage on the shop floor and is used to make material directly available for production purposes
 Will be used for EWM flows

Data Type: Character

Length: 10

CRHD-RGEKZIndicator: Backflushing

Indicates that material components allocated to the operation are backflushed

Data Type: Character

Length: 1

CRHD-STEUSControl Key

Determines which business transactions should be executed for the object that belongs to the task list or order (for example scheduling or costing).

Data Type: Character

Length: 4

CRHD-VGE01Unit of measure for the standard value

Unit of the standard value. If you have specified a unit in the work center, your entry is taken as the default value

Data Type: Unit

Length: 3

CRHD-VGE02Unit of measure for the standard value

Unit of the standard value. If you have specified a unit in the work center, your entry is taken as the default value

Data Type: Unit

Length: 3

CRHD-VGE03Unit of measure for the standard value

Unit of the standard value. If you have specified a unit in the work center, your entry is taken as the default value

Data Type: Unit

Length: 3

CRHD-VGE04Unit of measure for the standard value

Unit of the standard value. If you have specified a unit in the work center, your entry is taken as the default value

Data Type: Unit

Length: 3

CRHD-VGE05Unit of measure for the standard value

Unit of the standard value. If you have specified a unit in the work center, your entry is taken as the default value

Data Type: Unit

Length: 3

CRHD-VGE06Unit of measure for the standard value

Unit of the standard value. If you have specified a unit in the work center, your entry is taken as the default value

Data Type: Unit

Length: 3

CRHD-KAPARTCapacity category

Field Categorizes the Capacity of a Work Center

Data Type: Character

Length: 3

CRHD-KAPNAMECapacity name

Capacity Name or Capacity Description 

Data Type: Character

Length: 4

CRHD-FORT1Formula for setup time

Formula used in scheduling to calculate the setup time of an operation

Data Type: Character

Length: 6

TBD not sure if this will be used - Functional to advise

CRHD-FORT2Formula for the duration of processing time

Formula used in scheduling to determine the operation processing time

Data Type: Character

Length: 6

TBD not sure if this will be used - Functional to advise

CRHD-FORT3Formula for teardown time

Formula used in scheduling to determine teardown time in an operation

Data Type: Character

Length: 6

TBD not sure if this will be used - Functional to advise

CRHD-FORTNFormula for the duration of other types of int. processing

Formula for calculating the duration times of other types of internal processing in scheduling

Data Type: Character

Length: 6

TBD not sure if this will be used - Functional to advise

CRTX-SPRASLanguage

Language in which the resource description is maintained

Data Type: Character

Length: 1

CRTX-KTEXTShort description

Contains a brief description of the resource

Data Type: Character

Length: 40

KAKT-SPRASLanguage

Language of the text displayed

Data Type: Character

Length: 1

KAKT-KTEXTCapacity Text

Description of Capacity

Data Type: Character

Length: 40

CRCO-LASETActivity Type Set

Represents the assignment number of an activity type within a work center's costing data

Data Type: Character

Length: 6

CRCO-ENDDAEnd Date

date that identifies the end of the validity period

Data Type: Date Field

Length: 8 DD/MM/YYYY

CRCO-BEGDAStart Date

date that identifies the start of a validity period

Data Type: Date Field

Length: 8 DD/MM/YYYY


CRCO-KOKRSCO Area

An organizational unit within an enterprise for which a complete cost accounting can be performed within a closed system

Data Type: Character

Length: 4

CRCO-KOSTLCost Center

Represents a delimited location where costs occur

Data Type: Character

Length: 10

CRCO-LSTAR1Activity Type

Activity types describe the activity produced by a cost center and are measured in units of time or quantity

Data Type: Character

Length: 6

CRCO-LEINH1Activity Unit

The activity unit is either the time or quantity unit used to post the consumed activity quantities

Data Type: Unit

Length: 3

CRCO-FORML1Formula key for costing

Refers to the formula used for Calculation of costs of a work center's activity type

Data Type: Character

Length: 6

CRCO-LSTAR2Activity Type

Activity types describe the activity produced by a cost center and are measured in units of time or quantity

Data Type: Character

Length: 6

CRCO-LEINH2Activity Unit

The activity unit is either the time or quantity unit used to post the consumed activity quantities

Data Type: Unit

Length: 3

CRCO-FORML2Formula key for costing

Refers to the formula used for Calculation of costs of a work center's activity type

Data Type: Character

Length: 6

CRCO-LSTAR3Activity Type

Activity types describe the activity produced by a cost center and are measured in units of time or quantity

Data Type: Character

Length: 6

CRCO-LEINH3Activity Unit

The activity unit is either the time or quantity unit used to post the consumed activity quantities

Data Type: Unit

Length: 3

CRCO-FORML3Formula key for costing

Refers to the formula used for Calculation of costs of a work center's activity type

Data Type: Character

Length: 6

CRCO-LSTAR4Activity Type

Activity types describe the activity produced by a cost center and are measured in units of time or quantity

Data Type: Character

Length: 6

CRCO-LEINH4Activity Unit

The activity unit is either the time or quantity unit used to post the consumed activity quantities

Data Type: Unit

Length: 3

CRCO-FORML4Formula key for costing

Refers to the formula used for Calculation of costs of a work center's activity type

Data Type: Character

Length: 6

CRCO-LSTAR5Activity Type

Activity types describe the activity produced by a cost center and are measured in units of time or quantity

Data Type: Character

Length: 6

CRCO-LEINH5Activity Unit

The activity unit is either the time or quantity unit used to post the consumed activity quantities

Data Type: Unit

Length: 3

CRCO-FORML5Formula key for costing

refers to the formula used for Calculation of costs of a work center's activity type

Data Type: Character

Length: 6

CRCO-LSTAR6Activity Type

Activity types describe the activity produced by a cost center and are measured in units of time or quantity

Data Type: Character

Length: 6

CRCO-LEINH6Activity Unit

The activity unit is either the time or quantity unit used to post the consumed activity quantities

Data Type: Unit

Length: 3

CRCO-FORML6Formula key for costing

refers to the formula used for Calculation of costs of a work center's activity type

Data Type: Character

Length: 6

Extraction Dependencies

Item #Step DescriptionTeam Responsible
1

Source System Availability

  • Ensure that the source database or application is accessible.
  • Confirm that necessary credentials and permissions are granted

Syensqo IT

2

Data Structure

  • Identify relationships between tables, views, and stored procedures.

Syniti

3

Referential Integrity

  • Ensure dependent records are extracted together.

Syniti

4

Extraction Methodology

  • Define whether extraction is full, incremental, or delta-based.
  • Establish batch processing schedules for large datasets.

Syniti


5

Performance and Scalability Considerations

  • Optimize extraction queries to prevent system overload.
  • Ensure network bandwidth supports data transfer volumes.

Syniti

6

Security and Compliance

  • Adhere to regulatory standards for sensitive information if applicable

Syniti

7

Data cleansing of legacy Resource -

If standardization within the DCT begins using relevant data from PF2 and WP2 before the cleansing is finalized, it is understood that the business will take due diligence to ensure any subsequent delta cleansing is verified and aligned within the DCT.

Business


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 Data Team
2<Add steps from Syniti Migrate here>SyWay Data Team
3Review and Validate Error and Preload ReportsSyWay Data Team
4Generate Load FilesSyWay Data Team


Transformation Rules

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1PF2/WP2CRHDOBJTYObject typeS4 HANACRHDOBJTYObject type

System Generated Field

2PF2/WP2CRHDOBJIDObject IDS4 HANACRHDOBJIDObject IDSystem Generated Field
3PF2/WP2CRHDARBPLResource IDS4 HANACRHDARBPLResource ID

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

Existing Plant-New Plant mapping Check Resource name.

4PF2/WP2CRHDWERKSPlantS4 HANACRHDWERKSPlant

Map from Old Plants to New Plants

5PF2/WP2CRHDVERWEWork Center CategoryS4 HANACHRDVERWEWork Center Category

VALUE 0008

6PF2/WP2CRHDPLANVKey for task list usageS4 HANACHRDPLANVKey for task list usage

Value Direct from the current system

7PF2/WP2CRHDSTANDWork center locationS4 HANACHRDSTANDWork center location

Value set based upon MFG Execution Config Register

C : Business Rule

8PF2/WP2CRHDVERANPerson Responsible for the Work CenterS4 HANACHRDVERANPerson Responsible for the Work Center

Value set based upon MFG Execution Config Register

C : Business Rule

9PF2/WP2CRHDVGWTSStandard Value KeyS4 HANACHRDVGWTSStandard Value KeyTBD - STD Value Key maybe part of transformation and mapping
10PF2/WP2CRHDVGM01Rule for standard value maintenanceS4 HANACHRDVGM01Rule for standard value maintenanceIf the standard value is pulled and used then this field is required. Value Direct from the current system
11PF2/WP2CRHDVGM02Rule for standard value maintenanceS4 HANACHRDVGM02Rule for standard value maintenanceIf the standard value is pulled and used then this field is required. Value Direct from the current system
12PF2/WP2CRHDVGM03Rule for standard value maintenanceS4 HANACHRDVGM03Rule for standard value maintenanceIf the standard value is pulled and used then this field is required. Value Direct from the current system
13PF2/WP2CRHDVGM04Rule for standard value maintenanceS4 HANACHRDVGM04Rule for standard value maintenanceIf the standard value is pulled and used then this field is required. Value Direct from the current system
14PF2/WP2CRHDVGM05Rule for standard value maintenanceS4 HANACHRDVGM05Rule for standard value maintenanceIf the standard value is pulled and used then this field is required. Value Direct from the current system
15PF2/WP2CRHDVGM06Rule for standard value maintenanceS4 HANACHRDVGM06Rule for standard value maintenanceIf the standard value is pulled and used then this field is required. Value Direct from the current system
16PF2/WP2CRHDPRVBEProduction Supply AreaS4 HANACHRDPRVBEProduction Supply AreaBusiness Rule
If the WC always gets its raw materials staged to a fixed area / integration with WM to determine destination bin
17PF2/WP2CRHDRGEKZIndicator: BackflushingS4 HANACHRDRGEKZIndicator: BackflushingBusiness Rule
If all components used at a machine/line should be automatically issued at confirmation
18PF2/WP2CRHDSTEUSControl KeyS4 HANACHRDSTEUSControl KeyMandatory Direct from the current system
19PF2/WP2CRHDVGE01Unit of measure for the standard valueS4 HANACHRDVGE01Unit of measure for the standard valueIf the rule of the corresponding standard Value is used then this unit should be filled
20PF2/WP2CRHDVGE02Unit of measure for the standard valueS4 HANACHRDVGE02Unit of measure for the standard valueIf the rule of the corresponding standard Value is used then this unit should be filled
21PF2/WP2CRHDVGE03Unit of measure for the standard valueS4 HANACHRDVGE03Unit of measure for the standard valueIf the rule of the corresponding standard Value is used then this unit should be filled
22PF2/WP2CRHDVGE04Unit of measure for the standard valueS4 HANACHRDVGE04Unit of measure for the standard valueIf the rule of the corresponding standard Value is used then this unit should be filled
23PF2/WP2CRHDVGE05Unit of measure for the standard valueS4 HANACHRDVGE05Unit of measure for the standard valueIf the rule of the corresponding standard Value is used then this unit should be filled
24PF2/WP2CRHDVGE06Unit of measure for the standard valueS4 HANACHRDVGE06Unit of measure for the standard valueIf the rule of the corresponding standard Value is used then this unit should be filled
25PF2/WP2CRHDKAPARTCapacity categoryS4 HANACHRDKAPARTCapacity categoryValue Direct from the current system
26PF2/WP2CRHDKAPNAMECapacity nameS4 HANACHRDKAPNAMECapacity nameValue Direct from the current system
27PF2/WP2CRHDFORT1Formula for setup timeS4 HANACHRDFORT1Formula for setup timeRegistered as Not used, but this is to be decided, current SAP has values
28PF2/WP2CRHDFORT2Formula for the duration of processing timeS4 HANACHRDFORT2Formula for the duration of processing timeRegistered as Not used, but this is to be decided, current SAP has values
29PF2/WP2CRHDFORT3Formula for teardown timeS4 HANACHRDFORT3Formula for teardown timeRegistered as Not used, but this is to be decided, current SAP has values
30PF2/WP2CRHDFORTNFormula for the duration of other types of int. processingS4 HANACHRDFORTNFormula for the duration of other types of int. processingRegistered as Not used, but this is to be decided, current SAP has values
31PF2/WP2CRTXOBJTYObject typeS4 HANACRTXOBJTYObject typeSystem Generated Field
32PF2/WP2CRTXOBJIDObject IDS4 HANACRTXOBJIDObject IDSystem Generated Field
33PF2/WP2CRTXSPRASLanguage S4 HANACRTXSPRASLanguage Value direct from the current SAP system, Languages will need to be configured, mostly set as EN (Language which the Resource is maintained) 
34PF2/WP2CRTXKTEXTShort descriptionS4 HANACRTXKTEXTShort descriptionValue direct from current SAP system, free text field, brief description of the Resource SPRAS Language
35PF2/WP2CRCAOBJTYObject TypeS4 HANACRCAOBJTYObject TypeSystem Generated Field
36PF2/WP2CRCAOBJIDObject IDS4 HANACRCAOBJIDObject IDSystem Generated Field
37PF2/WP2CRCACANUMCapacity allocation numberS4 HANACRCACANUMCapacity allocation numberSystem Generated Field, The data value is TBD
38PF2/WP2CRCAKAPIDCapacity IDS4 HANACRCAKAPIDCapacity IDSystem Generated Field
39PF2/WP2KAKTKAPIDCapacity IDS4 HANAKAKTKAPIDCapacity IDSystem Generated Field
40PF2/WP2KAKTSPRASLanguageS4 HANAKAKTSPRASLanguageValue direct from the current SAP system, Languages will need to be configured, mostly set as EN (Language which the Capacity is maintained) 
41PF2/WP2KAKTKTEXTCapacity TextS4 HANAKAKTKTEXTCapacity TextValue direct from current SAP system, free text field, brief description of the Capacity SPRAS Language
42PF2/WP2CRCOOBJTYObject typeS4 HANACRCOOBJTYObject typeSystem Generated Field
43PF2/WP2CRCOOBJIDObject IDS4 HANACRCOOBJIDObject IDSystem Generated Field
44PF2/WP2CRCOLASETActivity Type SetS4 HANACRCOLASETActivity Type SetSystem Generated Field
45PF2/WP2CRCOENDDAEnd DateS4 HANACRCOENDDAEnd DateEnd date has value set to 31/12/9999 
46PF2/WP2CRCOBEGDAStart DateS4 HANACRCOBEGDAStart DateDate value setting DD.MM.YYYY 
47PF2/WP2CRCOKOKRSCO AreaS4 HANACRCOKOKRSCO AreaMandatory Value direct from current SAP system
48PF2/WP2CRCOKOSTLCost CenterS4 HANACRCOKOSTLCost CenterMandatory Value direct from current SAP system
49PF2/WP2CRCOLSTAR1Activity TypeS4 HANACRCOLSTAR1Activity TypeBusiness Rule
Assign the correct activity type to the corresponding activity
50PF2/WP2CRCOLEINH1Activity UnitS4 HANACRCOLEINH1Activity UnitIf the corresponding standard value is assigned to the activity then the unit should be entered 
51PF2/WP2CRCOFORML1Formula key for costingS4 HANACRCOFORML1Formula key for costingMandatory Value direct from current SAP system - Formula used to calculate cost of a work centers activity
52PF2/WP2CRCOLSTAR2Activity TypeS4 HANACRCOLSTAR2Activity TypeBusiness Rule
Assign the correct activity type to the corresponding activity
53PF2/WP2CRCOLEINH2Activity UnitS4 HANACRCOLEINH2Activity UnitIf the corresponding standard value is assigned to the activity then the unit should be entered  
54PF2/WP2CRCOFORML2Formula key for costingS4 HANACRCOFORML2Formula key for costingMandatory Value direct from current SAP system - Formula used to calculate cost of a work centers activity
55PF2/WP2CRCOLSTAR3Activity TypeS4 HANACRCOLSTAR3Activity TypeBusiness Rule
Assign the correct activity type to the corresponding activity
56PF2/WP2CRCOLEINH3Activity UnitS4 HANACRCOLEINH3Activity UnitIf the corresponding standard value is assigned to the activity then the unit should be entered  
57PF2/WP2CRCOFORML3Formula key for costingS4 HANACRCOFORML3Formula key for costingMandatory Value direct from current SAP system - Formula used to calculate cost of a work centers activity
58PF2/WP2CRCOLSTAR4Activity TypeS4 HANACRCOLSTAR4Activity TypeBusiness Rule
Assign the correct activity type to the corresponding activity
59PF2/WP2CRCOLEINH4Activity UnitS4 HANACRCOLEINH4Activity UnitIf the corresponding standard value is assigned to the activity then the unit should be entered   
60PF2/WP2CRCOFORML4Formula key for costingS4 HANACRCOFORML4Formula key for costingMandatory Value direct from current SAP system - Formula used to calculate cost of a work centers activity
61PF2/WP2CRCOLSTAR5Activity TypeS4 HANACRCOLSTAR5Activity TypeBusiness Rule
Assign the correct activity type to the corresponding activity
62PF2/WP2CRCOLEINH5Activity UnitS4 HANACRCOLEINH5Activity UnitIf the corresponding standard value is assigned to the activity then the unit should be entered  
63PF2/WP2CRCOFORML5Formula key for costingS4 HANACRCOFORML5Formula key for costingMandatory Value direct from current SAP system - Formula used to calculate cost of a work centers activity
64PF2/WP2CRCOLSTAR6Activity TypeS4 HANACRCOLSTAR6Activity TypeBusiness Rule
Assign the correct activity type to the corresponding activity
65PF2/WP2CRCOLEINH6Activity UnitS4 HANACRCOLEINH6Activity UnitIf the corresponding standard value is assigned to the activity then the unit should be entered  
66PF2/WP2CRCOFORML6Formula key for costingS4 HANACRCOFORML6Formula key for costing

Mandatory Value direct from current SAP system - Formula used to calculate cost of a work centers activity












Transformation Mapping

Mapping Table NameMapping Table Description
Work CentreMapping of legacy Work Center to new Work Centers to target system value
PlantMapping of legacy Plants to new Plants to target system value
Standard Value KeyMapping of legacy Standard Value Key  to new Standard Value Key to target system value


Transformation Dependencies

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

1

Ensure DCT tables completeness

SyWay Data Team

2

Value Mappings are according to the latest design - <List of Value Mappings>

SyWay Data Team


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 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 Data Team
2Load 3 records for < > to validate if data is loaded successfully without errorsSyWay Data Team
3Proceed with full load if steps 2 and 3 are validatedSyWay Data Team
4Validate few records loaded by accessing standard transactions from S/4HNA eg. CS04SyWay Data Team
5Generate post load report if step 5 is validatedSyWay Data Team


Load Phase and Dependencies

Configuration

Item #Configuration Item
1T001W-Plants/Branches
2TC30-Work Centre Category
3TC23-Key for use of the work center in the task lists
4T499S-Work Centre Location
5TC24-Person responsible for the work center
6TC21-Standard Value Key
7PVKT-Production Supply Area
8T430-Control Key
9T006-Units of Measurement
10TC26-Capacity Category
11TKA01-Controlling Areas
12OP54-Formula key for costing

Conversion Objects

Object #Preceding Object Conversion Approach
1071Activity Type
1074Cost Centre

Error Handling

Error TypeError DescriptionAction Taken
1Work Centre has not been created in a PlantEnsure the Work centre mapping is correct and or create the Work centre if it is valid
2Mapping conversion errors with new data

Ensure the collection file includes any new data values and mapping is correct


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 Resource data in target S/4 HANA were loaded correctly via DSP Migrate 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. 42) 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