Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Status

Page Status

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 four (34) 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 Four (34) 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 4 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 4 years Process order History, define the Resource by Plant
  4. For WP2, we are only going to be running Cleansing reports for 2 plants, Plants 8430 and 8628.
  5. For reports we should only use 0008 as the Work Centre Category.

Material Plant Active with three Four 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

Additional Information

Multi-language Requirement

English , French, ChineseMandarin, Spanish, German,  Italian, Brazilian Portuguese
        

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
Copy from Legacy
9CRHDVGWTSVORGSCHLStandard Value KeyCHAR4R

TBDSAP9
10CRHDVGM01AP_VGW_MESRule for standard value maintenanceCHAR1CValue taken from STD Value Key SAP9 - value entered should be 2 
11CRHDVGM0211CRHDVGM02AP_VGW_MESRule for standard value maintenanceCHAR1CValue taken from STD Value Key SAP9 - value entered should be 2
12CRHDVGM03AP_VGW_MESRule for standard value maintenanceCHAR1CValue taken from STD Value Key SAP9 - value entered should be 2
13CRHDVGM04AP_VGW_MESRule for standard value maintenanceCHAR1C
Value taken from STD Value Key SAP9 - value entered should be 2
14CRHDVGM05AP_VGW_MESRule for standard value maintenanceCHAR1CNU
15CRHDVGM06AP_VGW_MESRule for standard value maintenanceCHAR1CNU
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
Value taken from STD Value Key SAP9
26CRHDVGE02VGWRTEHUnit of measure for the standard valueUNIT3C
Value taken from STD Value Key SAP9
27CRHDVGE03VGWRTEHUnit of measure for the standard valueUNIT3C
Value taken from STD Value Key SAP9
28CRHDVGE04VGWRTEHUnit of measure for the standard valueUNIT3C
Value taken from STD Value Key SAP9
29CRHDVGE05VGWRTEHUnit of measure for the standard valueUNIT3CNU
30CRHDVGE06VGWRTEHUnit of measure for the standard valueUNIT3CNU

31CRHDFORT1AP_FORM_T1Formula for setup timeCHAR6C



32CRHDFORT2AP_FORM_T2Formula for the duration of processing timeCHAR6R



33CRHDFORT3AP_FORM_T3Formula for teardown timeCHAR6C



34CRHDFORTNAP_FORM_TNFormula for the duration of other types of int. processingCHAR6NU



35CRTXOBJTYCR_OBJTYObject typeCHAR2S

36CRTXOBJIDCR_OBJIDObject IDNUMC8S

37CRTXSPRASSPRASLanguageCHAR1R

38CRTXKTEXTCR_KTEXTShort descriptionCHAR40R

39CRCAOBJTYCR_OBJTYObject TypeCHAR2S

40CRCAOBJIDCR_OBJIDObject IDNUMC8S

41CRCACANUMCR_CAPNUMCapacity allocation numberCHARNUMC64S


TBD
42CRCAFORK1AP_FORM_K1Formula for Setup Capacity RequirementsCHAR6NUR

43CRCAFORK2AP_FORM_K2Formula for Processing Capacity RequirementsCHAR6NUR

44CRCAFORK3AP_FORM_K3Formula for Teardown Capacity RequirementsCHAR6NU

45CRCAFORKNAP_FORM_KNFormula for Other Capacity RequirementsCHAR6NU

46CRCAKAPIDKAPIDCapacity IDNUMC8S

47KAKTKAPIDKAPIDCapacity IDNUMC8S

48KAKTSPRASSPRASLanguageCHAR1R

49KAKTKTEXTCR_KTEXTCapacity TextCHAR40R

50CRCOOBJTYCR_OBJTYObject typeCHAR2S

51CRCOOBJIDCR_OBJIDObject IDNUMC8S

52CRCOLASET#N/AActivity Type SetCHAR6S

53CRCOENDDAENDDATUMEnd DateDATS8R


31/12/9999
54CRCOBEGDABEGDATUMStart DateDATS8R

55CRCOKOKRSKOKRSCO AreaCHAR4R

56CRCOKOSTLKOSTLCost CenterCHAR10R

57CRCOLSTAR1LSTARActivity TypeCHAR6C

58CRCOLEINH1LEINHActivity UnitUNIT3C

59CRCOFORML1FORMLFormula key for costingCHAR6R
Value taken from STD Value Key SAP9
60CRCOLSTAR2LSTARActivity TypeCHAR6C
61CRCOLEINH2LEINHActivity UnitUNIT3C

62CRCOFORML2FORMLFormula key for costingCHAR6R
Value taken from STD Value Key SAP9
63CRCOLSTAR3LSTARActivity TypeCHAR6C
64CRCOLEINH3LEINHActivity UnitUNIT3C

65CRCOFORML3FORMLFormula key for costingCHAR6R
Value taken from STD Value Key SAP9
66CRCOLSTAR4LSTARActivity TypeCHAR6C
67CRCOLEINH4LEINHActivity UnitUNIT3C

68CRCOFORML4FORMLFormula key for costingCHAR6R
Value taken from STD Value Key SAP9
69CRCOLSTAR5LSTARActivity TypeCHAR6CNU
70CRCOLEINH5LEINHActivity UnitUNIT3CNU

71CRCOFORML5FORMLFormula key for costingCHAR6RNU

72CRCOLSTAR6LSTARActivity TypeCHAR6CNU

73CRCOLEINH6LEINHActivity UnitUNIT3CNU

74CRCOFORML6FORMLFormula key for costingCHAR6RNU

75CRCOLANUMCR_LANUMActivity type number within a setNUMC4NU

76KAKOKAPIDKAPIDCapacity IDNUMC8S

7677KAKOAZMAXKAPANZAHLNo. Ind. CapacitiesINT25NU

7778KAKOAZNORKAPANZAHLNo. Ind. CapacitiesINT25R

7879KAKOBASNEKAPBASNENDenominator base capDEC5S

7980KAKOBASZLKAPBASZHLNumerator base cap.DEC5S

8081KAKOBEGZTKAPBEGZTStart TimeINT410R

8182KAKOENDZTKAPENDZTEnd TimeINT410R

8283KAKOKALIDCR_WFCIDFactory CalendarCHAR2C

8384KAKOKAPARKAPARTCapacity categoryCHAR3R

8485KAKOMEINSKAPBASISCapacity Base UnitUNIT3R

8586KAKOMOSIDSCHGRUPShift GroupingCHAR2C

8687KAKONAMEKAPNAMECapacityCHAR8NU

8788KAKONGRADNUTZGRADCapacity UtilizationNUMC3R

8889KAKOPAUSEKAPPAUSEBreak DurationINT410R

8990KAKOPLANRKAPPLANERCapacity Responsible PlannerCHAR3R

9091KAKOPOOLKKAP_KZPOOLPooled Capacity IndicatorCHAR1C

9192KAKOREFANKAPREFANZNNumber (ref. cap.)INT13C
Not used because it is only used if you are going to do a new creation once we are live
9392KAKOREFAZKAPREFANZZNumber (capacity)INT13C
Not used because it is only used if you are going to do a new creation once we are live
9493KAKOREFIDKAPIDCapacity IDNUMC8C
Not used because it is only used if you are going to do a new creation once we are live
9594KAKOSUPPKKAP_SUPPLYAvail. cap. limitsCHAR1C (if not entered, 100% will be the default)

9596KAKOVERSAKAPVERSAKTActive VersionNUMC2R

9697KAKOWERKSWERKS_DPlantCHAR4NU

9798KAKOKAPIEKAPIDCapacity IDNUMC8NU

9899KAKOKAPTERKAP_KZTERRelevant to Finite SchedulingCHAR1C

99100KAKOKAPAVOKAP_KZAVOCan be used by several operationsCHAR1C

100101KAKOUEBERLASTUEBERLASTOverload (%)NUMC3C

101102KAKOKAPLPLKAP_KZLPLNo Long-Term PlanningCHAR1C

102103KAKOKAPEHCR_KAPEHCapacity UnitUNIT3C (if PP/DS is used)NU

104103KAKOMEHRKAP_MEHRHas Individual CapacitiesCHAR1C (if PP/DS is used)NU

105104KAKOANG_UNITKAPAZIT_VM_UNITAv. cap. unitUNIT3C (if PP/DS is used)
NU - CFC9 manages it through APO without the need to update manually the fields are not required for ADM
106105KAKOANG_MINKAPAZIT_VM_MINMinimum capacityQUAN13C (if PP/DS is used)
NU - CFC9 manages it through APO without the need to update manually the fields are not required for ADM
107106KAKOANG_MAXKAPAZIT_VM_MAXMax. capacityQUAN13C (if PP/DS is used)
NU - CFC9 manages it through APO without the need to update manually the fields are not required for ADM


Data 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 4 yearsAll Resources not used for the last 3 4 years, won't be migratedActive Resources during the last 3 4 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.

The Data Collection Template (DCT) will not be applicable in this case. If there is a need to create  new Master Data (MD) for Resource object, the business must perform this activity in the source system. The newly created object will then be captured and migrated as part of the standard migration process.DCT1 - 1056 Resource Header Page

Field Name

Field description

Rule

Extraction Dependencies

Item #Step DescriptionTeam Responsible1

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

Mappings

CRHD-KAPIDCapacity IDID to identify the capacity headerSystem Generated Field
Data Type: Numeric
Length: 8
CRHD-ARBPLWork CenterRepresents a machine, group of machines, production line or a person assigned to an operationValue Mapping from A to B for Resource ID by plant
Data Type: Character
Length: 8
CRHD-WERKSPlantKey uniquely identifying a plantMap from Old Plants to New Plants
Data Type: Character
Length: 4
CRHD-VERWEWork Center CategoryKey differentiating resources according to their category (e.g. resource network, process unit)Default Value - 0008
Data Type: Character
Length: 4
CRHD-PLANVKey for task list usageControls which type of tasks list are allowed to use this resourceCopy from DCT
Data Type: Character
Length: 3
CRHD-STANDWork center locationRepresents the physical location of the resourceCopy from DCT
Data Type: Character
Length: 10
CRHD-VERANPerson Responsible for the Work CenterThe person or group of people who are responsible for the maintenance of the resource - Useful for Reporting purposesCopy from DCT
Data Type: Character
Length: 3
CRHD-VGWTSStandard Value KeyThe system uses standard values as parameters with origin "standard value" in formulas to calculate execution time, capacity requirements and costsDefault Value - SAP9
Data Type: Character
Length: 4
CRHD-VGM01Rule for standard value maintenanceDetermines 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)Default Value - 2
Data Type: Character
Length: 1
CRHD-VGM02Rule for standard value maintenanceDetermines 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)Default Value - 2
Data Type: Character
Length: 1
CRHD-VGM03Rule for standard value maintenanceDetermines 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)Default Value - 2
Data Type: Character
Length: 1
CRHD-VGM04Rule for standard value maintenanceDetermines 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)Default Value - 2
Data Type: Character
Length: 1
CRHD-PRVBEProduction Supply AreaServes as a place for interim storage on the shop floor and is used to make material directly available for production purposesBecause the warehouse can support holding stock that belongs to more than one plant, the PP PSA is replicated to EWM by adding the plant number preceded by a "/" to be able to tell in the warehouse to which plant the original PSA belongs. - Value Mapping
 Will be used for EWM flows
Data Type: Character
Length: 10
CRHD-RGEKZIndicator: BackflushingIndicates that material components allocated to the operation are backflushedCopy from DCT
Data Type: Character
Length: 1
CRHD-STEUSControl KeyDetermines which business transactions should be executed for the object that belongs to the task list or order (for example scheduling or costing).Copy from DCT
Data Type: Character
Length: 4
CRHD-VGE01Unit of measure for the standard valueUnit of the standard value. If you have specified a unit in the work center, your entry is taken as the default valueValue automatically to be taken from VGWTS - STD value key 
Data Type: Unit
Length: 3
CRHD-VGE02Unit of measure for the standard valueUnit of the standard value. If you have specified a unit in the work center, your entry is taken as the default valueValue automatically to be taken from VGWTS - STD value key 
Data Type: Unit
Length: 3
CRHD-VGE03Unit of measure for the standard valueUnit of the standard value. If you have specified a unit in the work center, your entry is taken as the default valueValue automatically to be taken from VGWTS - STD value key 
Data Type: Unit
Length: 3
CRHD-VGE04Unit of measure for the standard valueUnit of the standard value. If you have specified a unit in the work center, your entry is taken as the default valueValue automatically to be taken from VGWTS - STD value key 
Data Type: Unit
Length: 3
CRHD-FORT1Formula for setup timeFormula used in scheduling to calculate the setup time of an operationDefault Value - SAP001
Data Type: Character
Length: 6
CRHD-FORT2Formula for the duration of processing timeFormula used in scheduling to determine the operation processing timeDefault Value - SAP002
Data Type: Character
Length: 6
CRHD-FORT3Formula for teardown timeFormula used in scheduling to determine teardown time in an operationDefault Value - SAP010
Data Type: Character
Length: 6

DCT2 - 1056 Resource Description

 

 

 

Field Name

Field description

Rule

Mappings

CRHD-ARBPLWork CenterRepresents a machine, group of machines, production line or a person assigned to an operationValue Mapping from A to B for Resource ID by plant
Data Type: Character
Length: 8
CRTX-KTEXTShort descriptionContains a brief description of the resourceCopy from DCT
Data Type: Character
Length: 40
CRTX-SPRASLanguageLanguageCopy from DCT
Data Type: Character
Length: 1

DCT3 - 1056 Resource Cost Center

 

 

 

Field Name

Field description

Rule

Mappings

CRHD-ARBPLWork CenterRepresents a machine, group of machines, production line or a person assigned to an operationValue Mapping from A to B for Resource ID by plant
Data Type: Character
Length: 8
CRCO-ENDDAEnd Datedate that identifies the end of the validity periodDefault Value - 31/12/9999 
Data Type: Date Field
Length: 8 DD/MM/YYYY
CRCO-BEGDAStart Datedate that identifies the start of a validity periodCopy from DCT
Data Type: Date Field
Length: 8 DD/MM/YYYY
CRCO-LASETActivity Type SetActivity Type SetSystem Generated Field
Data Type: Character
Length: 6
CRCO-KOKRSCO AreaAn organizational unit within an enterprise for which a complete cost accounting can be performed within a closed systemThis is Part of DCT in the Cost centre Conversion Spec - Value Mapping
Data Type: Character
Length: 4
CRCO-KOSTLCost CenterRepresents a delimited location where costs occurThis is Part of DCT in the Cost centre Conversion Spec - Value Mapping
Data Type: Character
Length: 10
CRCO-LSTARActivity TypeActivity types describe the activity produced by a cost center and are measured in units of time or quantityThis is Part of DCT in the Cost centre Conversion Spec - Value Mapping
Data Type: Character
Length: 6
CRCO-LEINHActivity UnitThe activity unit is either the time or quantity unit used to post the consumed activity quantitiesThis is Part of DCT in the Cost centre Conversion Spec - Value Mapping
Data Type: Unit
Length: 3
CRCO-FORMLFormula key for costingRefers to the formula used for Calculation of costs of a work center's activity type

for LANUM 001 Then -> Default Value - SAP001
for LANUM 002 Then -> Default Value - SAP002
for LANUM 003 Then -> Default Value - SAP003
for LANUM 004 Then -> Default Value - SAP010

Data Type: Character
Length: 6
CRCO-LANUMActivity type number within a setActivity type number within a setNU not used (Value to be entered into the DCT)
Data Type: NUMC
Length: 4

DCT4 - 1056 Resource Capacity Header Segment

 

 

 

Field Name

Field description

Rule

Mappings

CRHD-ARBPLWork CenterRepresents a machine, group of machines, production line or a person assigned to an operationValue Mapping from A to B for Resource ID by plant
Data Type: Character
Length: 8
KAKO-KAPIDCapacity IDID to identify the capacity headerSystem Generated Field
Data Type: Numeric
Length: 8
KAKO-AZNORNo. Ind. CapacitiesNumber of individual capacitiesCopy from DCT
Data Type: Decimal
Length: 5
KAKO-BEGZTStart TimeStart time in seconds (internal)Copy from DCT
Data Type: Integer 4
Length: 10
KAKO-ENDZTEnd TimeFinish time in seconds (internal)Copy from DCT
Data Type: Integer 4
Length: 10
KAKO-KALIDFactory CalendarFactory calendar IDThe calendar used is the one assigned to the plant or it's a calendar defined in the same country - Factory Calendar under TM team to define the values, Value Mapping table from A to B Copy from DCT
Data Type: Character 
Length: 2
KAKO-KAPARCapacity categoryCapacity categoryCopy from DCT
Data Type: Character 
Length: 3
KAKO-KAPAVOCan be used by several operationsIndicator: Several operations can use capacityDefault Value - X
Data Type: Character 
Length: 1
KAKO-KAPLPLNo Long-Term PlanningIndicator: Capacity excluded from long-term planningDefault Value - X
Data Type: Character 
Length: 1
KAKO-KAPTERRelevant to Finite SchedulingIndicator: Capacity relevant to finite schedulingDefault Value - X
Data Type: Character 
Length: 1
KAKO-MEINSCapacity Base UnitBase Unit of Measurement for CapacityCopy from DCT
Data Type: Unit
Length: 3
KAKO-MOSIDShift GroupingGrouping for Shift Definitions and Shift SequencesCopy from DCT
Data Type: Character 
Length: 2
KAKO-NGRADCapacity UtilizationCapacity utilization rate (percent)Copy from DCT
Data Type: Numeric
Length: 3
KAKO-PAUSEBreak DurationCumulative break time in seconds (internal)Copy from DCT
Data Type: Integer 4
Length: 10
KAKO-PLANRCapacity Responsible PlannerCapacity planner groupCopy from DCT
Data Type: Character 
Length: 3
KAKO-SUPPKAvail. cap. limitsAvailable capacity limitsCopy from DCT
Data Type: Character 
Length: 1
KAKO-UEBERLASTOverload (%)Overload CapacityCopy from DCT
Data Type: Numeric
Length: 3
KAKO-VERSAActive VersionActive version of available capacityCopy from DCT
Data Type: Numeric
Length: 2

DCT5 - 1056 Resource Description

 

 

 

Field Name

Field description

Rule

Mappings

KAKT-KAPIDCapacity IDID to identify the capacity headerSystem Generated Field
Data Type: Numeric
Length: 8
KAKT-SPRASLanguageLanguage of the text displayedCopy from DCT
Data Type: Character
Length: 1
KAKT-KTEXTCapacity TextDescription of CapacityCopy from DCT
Data Type: Character
Length: 40

DCT6 - 1056 Resource Capacity Allocation

 

 

 

Field Name

Field description

Rule

Mappings

CRCA-KAPIDCapacity IDID to identify the capacity headerSystem Generated Field
Data Type: Numeric
Length: 8


CRCA-CANUMCapacity allocation numberCapacity allocation numberSystem Generated Field
Data Type: Numeric
Length: 4


CRCA-FORK1Formula for Setup Capacity RequirementsFormula for Setup Capacity Requirements
Data Type: Character
Length: 6


CRCA-FORK2Formula for Processing Capacity RequirementsFormula for Processing Capacity Requirements
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

Value Mapping from A to B for Resource ID by plant

4PF2/WP2CRHDWERKSPlantS4 HANACRHDWERKSPlant

Map from Old Plants to New Plants

5PF2/WP2CRHDVERWEWork Center CategoryS4 HANACRHDVERWEWork Center Category

VALUE 0008

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

Value Direct from the current system

7PF2/WP2CRHDSTANDWork Center locationS4 HANACRHDSTANDWork Center location

Copy from Legacy

8PF2/WP2CRHDVERANPerson Responsible for the Work CenterS4 HANACRHDVERAN

Copy from Legacy, if blank please populate with 001

9PF2/WP2CRHDVGWTSStandard Value KeyS4 HANACRHDVGWTSStandard Value KeyFollow Mfg Execution Config book (one standard value key for all resources / all GBUs) Value - SAP9
10PF2/WP2CRHDVGM01Rule for standard value maintenanceS4 HANACRHDVGM01Rule for standard value maintenanceValue automatically to be taken from VGWTS - STD value key (Value entered should be 2)
11PF2/WP2CRHDVGM02Rule for standard value maintenanceS4 HANACRHDVGM02Rule for standard value maintenanceValue automatically to be taken from VGWTS - STD value key (Value entered should be 2)
12PF2/WP2CRHDVGM03Rule for standard value maintenanceS4 HANACRHDVGM03Rule for standard value maintenanceValue automatically to be taken from VGWTS - STD value key (Value entered should be 2)
13PF2/WP2CRHDVGM04Rule for standard value maintenanceS4 HANACRHDVGM04Rule for standard value maintenanceValue automatically to be taken from VGWTS - STD value key (Value entered should be 2)
14PF2/WP2CRHDPRVBEProduction Supply AreaS4 HANACRHDPRVBEProduction Supply Area

Business Rule
This field will be populated if relevant for EWM based on the plant (this has not been completely defined yet) MDS for EWM           DD-FUN-050 Master Data  Standard_1180-PSA (EWM)

Because the warehouse can support holding stock that belongs to more than one plant, the PP PSA is replicated to EWM by adding the plant number preceded by a "/" to be able to tell in the warehouse to which plant the original PSA belongs. - Value Mapping

15PF2/WP2CRHDRGEKZIndicator: BackflushingS4 HANACRHDRGEKZIndicator: BackflushingBusiness Rule
If all components used at a machine/line should be automatically issued at confirmation - Copy from Legacy
16PF2/WP2CRHDSTEUSControl KeyS4 HANACRHDSTEUSControl KeyMandatory Direct from the current system
17PF2/WP2CRHDVGE01Unit of measure for the standard valueS4 HANACRHDVGE01Unit of measure for the standard valueR - Value automatically to be taken from VGWTS - STD value key 
18PF2/WP2CRHDVGE02Unit of measure for the standard valueS4 HANACRHDVGE02Unit of measure for the standard valueR - Value automatically to be taken from VGWTS - STD value key 
19PF2/WP2CRHDVGE03Unit of measure for the standard valueS4 HANACRHDVGE03Unit of measure for the standard valueR - Value automatically to be taken from VGWTS - STD value key 
20PF2/WP2CRHDVGE04Unit of measure for the standard valueS4 HANACRHDVGE04Unit of measure for the standard valueR - Value automatically to be taken from VGWTS - STD value key 
21PF2/WP2CRHDFORT1Formula for setup timeS4 HANACRHDFORT1Formula for setup timeStandard Formula SAP001
22PF2/WP2CRHDFORT2Formula for the duration of processing timeS4 HANACRHDFORT2Formula for the duration of processing timeStandard Formula SAP002
23PF2/WP2CRHDFORT3Formula for teardown timeS4 HANACRHDFORT3Formula for teardown timeStandard Formula SAP010
24PF2/WP2CRTXOBJTYObject typeS4 HANACRTXOBJTYObject typeSystem Generated Field
25PF2/WP2CRTXOBJIDObject IDS4 HANACRTXOBJIDObject IDSystem Generated Field
26PF2/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) 
27PF2/WP2CRTXKTEXTShort descriptionS4 HANACRTXKTEXTShort descriptionCopy from Legacy
28PF2/WP2CRCAOBJTYObject TypeS4 HANACRCAOBJTYObject TypeSystem Generated Field
29PF2/WP2CRCAOBJIDObject IDS4 HANACRCAOBJIDObject IDSystem Generated Field
30PF2/WP2CRCACANUMCapacity allocation numberS4 HANACRCACANUMCapacity allocation numberSystem Generated Field
31PF2/WP2CRCAKAPIDCapacity IDS4 HANACRCAKAPIDCapacity IDSystem Generated Field
32PF2/WP2CRCAFORK1Formula for Processing Capacity RequirementsS4 HANACRCAFORK1Formula for Processing Capacity Requirementscan be set to Blank (Waiting for functional to advise)
33PF2/WP2CRCAFORK2Formula for Teardown Capacity RequirementsS4 HANACRCAFORK2Formula for Teardown Capacity Requirementscan be set to Blank (Waiting for functional to advise)

34

PF2/WP2KAKTKAPIDCapacity IDS4 HANAKAKTKAPIDCapacity IDSystem Generated Field
35PF2/WP2KAKTSPRASLanguageS4 HANAKAKTSPRASLanguageValue direct from the current SAP system, Languages will need to be configured, mostly set as EN (Language which the Capacity is maintained) 
36PF2/WP2KAKTKTEXTCapacity TextS4 HANAKAKTKTEXTCapacity TextCopy From Legacy
37PF2/WP2CRCOOBJTYObject typeS4 HANACRCOOBJTYObject typeSystem Generated Field
38PF2/WP2CRCOOBJIDObject IDS4 HANACRCOOBJIDObject IDSystem Generated Field
39PF2/WP2CRCOLASETActivity Type SetS4 HANACRCOLASETActivity Type SetSystem Generated Field
40PF2/WP2CRCOENDDAEnd DateS4 HANACRCOENDDAEnd DateEnd date has value set to 31/12/9999 
41PF2/WP2CRCOBEGDAStart DateS4 HANACRCOBEGDAStart DateDate value setting DD.MM.YYYY Copy from current system
42PF2/WP2CRCOKOKRSCO AreaS4 HANACRCOKOKRSCO Area

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 Responsible1Obtain DCT Sign-off from BusinessSyWay Data Team2<Add steps from Syniti Migrate here>SyWay Data Team3Review and Validate Error and Preload ReportsSyWay Data Team4Generate 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,

Copy from current, or if they are not there, it will be config if they are going to use it

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

Value set based upon MFG Execution Config Register

C : Business Rule

From the Configuration work book and be a generic entry for all plants

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 to be taken from VGWTS - STD value key
11PF2/WP2CRHDVGM02Rule for standard value maintenanceS4 HANACHRDVGM02Rule for standard value maintenanceIf the standard value is pulled and used then this field is required. Value to be taken from VGWTS - STD value key
12PF2/WP2CRHDVGM03Rule for standard value maintenanceS4 HANACHRDVGM03Rule for standard value maintenanceIf the standard value is pulled and used then this field is required. Value to be taken from VGWTS - STD value key
13PF2/WP2CRHDVGM04Rule for standard value maintenanceS4 HANACHRDVGM04Rule for standard value maintenanceIIf the standard value is pulled and used then this field is required. Value to be taken from VGWTS - STD value key
14PF2/WP2CRHDVGM05Rule for standard value maintenanceS4 HANACHRDVGM05Rule for standard value maintenanceIf the standard value is pulled and used then this field is required. Value to be taken from VGWTS - STD value key
15PF2/WP2CRHDVGM06Rule for standard value maintenanceS4 HANACHRDVGM06Rule for standard value maintenanceIf the standard value is pulled and used then this field is required. Value to be taken from VGWTS - STD value key
16PF2/WP2CRHDPRVBEProduction Supply AreaS4 HANACHRDPRVBEProduction Supply Area

Business Rule
If the WC always gets its raw materials staged to a fixed area / integration with WM to determine destination bin.

This field will be populated if relevant for EWM based on the plant (this has not been completely defined yet)

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. Value to be taken from VGWTS - STD value key
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. Value to be taken from VGWTS - STD value key
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. Value to be taken from VGWTS - STD value key
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. Value to be taken from VGWTS - STD value key
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. Value to be taken from VGWTS - STD value key
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. Value to be taken from VGWTS - STD value key
27PF2/WP2CRHDFORT1Formula for setup timeS4 HANACHRDFORT1Formula for setup timeConditional:  Formula used in scheduling to calculate the setup time of an operation. Value to be taken from VGWTS - STD value key
28PF2/WP2CRHDFORT2Formula for the duration of processing timeS4 HANACHRDFORT2Formula for the duration of processing timeValue to be taken from VGWTS - STD value key
29PF2/WP2CRHDFORT3Formula for teardown timeS4 HANACHRDFORT3Formula for teardown timeConditional: Formula used in scheduling to determine teardown time in an operation. Value to be taken from VGWTS - STD value key
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
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 , Process orders, when they are created are we going to create them with days in the past? needs to be confirmed
47PF2/WP2CRCOKOKRSCO AreaS4 HANACRCOKOKRSCO AreaThis is Part of DCT in the Cost centre Conversion Spec 
48PF2/WP2CRCOKOSTLCost CenterS4 HANACRCOKOSTLCost CenterThis is Part of DCT in the Cost centre Conversion Spec 
49PF2/WP2CRCOLSTAR1Activity TypeS4 HANACRCOLSTAR1Activity TypeThis is Part of DCT in the Cost centre Conversion Spec 
50PF2/WP2CRCOLEINH1Activity UnitS4 HANACRCOLEINH1Activity UnitThis is Part of DCT in the Cost centre Conversion Spec 
51PF2/WP2CRCOFORML1Formula key for costingS4 HANACRCOFORML1Formula key for costingValue to be taken from VGWTS - STD value key
52PF2/WP2CRCOLSTAR2Activity TypeS4 HANACRCOLSTAR2Activity TypeThis is Part of DCT in the Cost centre Conversion Spec 
53PF2/WP2CRCOLEINH2Activity UnitS4 HANACRCOLEINH2Activity UnitThis is Part of DCT in the Cost centre Conversion Spec Spec - Value Mapping
4354PF2/WP2CRCOFORML2KOSTLCost CenterFormula key for costingS4 HANACRCOFORML2Formula key for costingValue to be taken from VGWTS - STD value keyKOSTLCost CenterThis is Part of DCT in the Cost centre Conversion Spec - Value Mapping
4455PF2/WP2CRCOLSTAR3LSTAR1Activity TypeS4 HANACRCOLSTAR3LSTAR1Activity TypeThis is Part of DCT in the Cost centre Conversion Spec Spec - Value Mapping
4556PF2/WP2CRCOLEINH3LEINH1Activity UnitS4 HANACRCOLEINH3LEINH1Activity UnitThis is Part of DCT in the Cost centre Conversion Spec Spec - Value Mapping
4657PF2/WP2CRCOFORML3FORML1Formula key for costingS4 HANACRCOFORML3FORML1Formula key for costing

NU - Value automatically to be taken from VGWTS - STD value

key

Value - SAP001

4758PF2/WP2CRCOLSTAR4LSTAR2Activity TypeS4 HANACRCOLSTAR4LSTAR2Activity TypeThis is Part of DCT in the Cost centre Conversion Spec Conversion Spec - Value Mapping
4859PF2/WP2CRCOLEINH4LEINH2Activity UnitS4 HANACRCOLEINH4LEINH2Activity UnitThis is Part of DCT in the Cost centre Conversion Spec Spec - Value Mapping
4960PF2/WP2CRCOFORML4FORML2Formula key for costingS4 HANACRCOFORML4FORML2Formula key for costingNU - Value automatically to be taken from VGWTS - STD value keyValue - SAP002
5061PF2/WP2CRCOLSTAR5LSTAR3Activity TypeS4 HANACRCOLSTAR5LSTAR3Activity TypeThis is Part of DCT in the Cost centre Conversion Spec Spec - Value Mapping
5162PF2/WP2CRCOLEINH5LEINH3Activity UnitS4 HANACRCOLEINH5LEINH3Activity UnitThis is Part of DCT in the Cost centre Conversion Spec Spec - Value Mapping
5263PF2/WP2CRCOFORML5FORML3Formula key for costingS4 HANACRCOFORML5FORML3Formula key for costingNU - Value automatically to be taken from VGWTS - STD value keyValue - SAP003
5364PF2/WP2CRCOLSTAR6LSTAR4Activity TypeS4 HANACRCOLSTAR6LSTAR4Activity TypeThis is Part of DCT in the Cost centre Conversion Spec Spec - Value Mapping
5465PF2/WP2CRCOLEINH6LEINH4Activity UnitS4 HANACRCOLEINH6LEINH4Activity UnitThis is Part of DCT in the Cost centre Conversion Spec Spec - Value Mapping
5566PF2/WP2CRCOFORML6FORML4Formula key for costingS4 HANACRCOFORML6FORML4Formula key for costingNU - Value automatically to be taken from VGWTS - STD value keyValue - SAP010
5667PF2/WP2KAKOKAPIDCapacity IDS4 HANAKAKOKAPIDCapacity ID

System Generated

6857PF2/WP2KAKOAZNORNo. Ind. CapacitiesS4 HANAKAKOAZNORNo. Ind. CapacitiesCopy From ECC
6958PF2/WP2KAKOBASNEDenominator base capS4 HANAKAKOBASNEDenominator base capSystem Generated
70PF2/WP2KAKOBASZLNumerator base cap.S4 HANAKAKOBASZLNumerator base cap.System Generated
71PF2/WP2KAKOBEGZTStart TimeS4 HANAKAKOBEGZTStart TimeCopy From ECC
72PF2/WP2KAKOENDZTEnd Timebase capS4 HANAKAKOENDZTEnd TimeCopy From ECCBASNEDenominator base capSystem Generated
5973PF2/WP2KAKOKALIDBASZLNumerator base cap.Factory CalendarS4 HANAKAKOKALIDFactory CalendarConditional : Business Rule
Assign the correct Factory Calendar to the resource. If left blank, the system will use directly the plant factory calendar by default
The calendar used is the one assigned to the plant or it's a calendar defined in the same country
BASZLNumerator base cap.System Generated
6074PF2/WP2KAKOKAPARBEGZTCapacity categoryStart TimeS4 HANAKAKOKAPARBEGZTCapacity categoryStart TimeCopy From ECC
7561PF2/WP2KAKOMEINSENDZTEnd TimeCapacity Base UnitS4 HANAKAKOMEINSENDZTEnd TimeCapacity Base UnitCopy From ECC
7662PF2/WP2KAKOMOSIDKALIDShift GroupingFactory CalendarS4 HANAKAKOMOSIDKALIDShift GroupingFactory CalendarConditional : Business rule TBD, this will be discussed in the deliverable review sessionRule
Assign the correct Factory Calendar to the resource. If left blank, the system will use directly the plant factory calendar by default
The calendar used is the one assigned to the plant or it's a calendar defined in the same country -Factory Calendar under TM team to define the values, Value Mapping table from A to B
6377PF2/WP2KAKONGRADKAPARCapacity UtilizationcategoryS4 HANAKAKONGRADKAPARCapacity UtilizationcategoryCopy From ECC
7864PF2/WP2KAKOPAUSEMEINSCapacity Base UnitBreak DurationS4 HANAKAKOPAUSEMEINSCapacity Base UnitBreak DurationCopy From ECC
7965PF2/WP2KAKOPLANRMOSIDShift GroupingCapacity Responsible PlannerS4 HANAKAKOPLANRMOSIDShift GroupingCopy values by plant from Legacy
66Capacity Responsible PlannerCopy From ECC80PF2/WP2KAKOPOOLKNGRADPooled Capacity IndicatorUtilizationS4 HANAKAKOPOOLKNGRADPooled Capacity IndicatorSystem GeneratedUtilizationCopy From ECC
6781PF2/WP2KAKOREFANPAUSEBreak DurationNumber (ref. cap.)S4 HANAKAKOREFANNumber (ref. cap.)Not used because it is only used if you are going to do a new creation once we are livePAUSEBreak DurationCopy From ECC
6882PF2/WP2KAKOREFAZPLANRCapacity Responsible PlannerNumber (capacity)S4 HANAKAKOREFAZNumber (capacity)Not used because it is only used if you are going to do a new creation once we are livePLANRCapacity Responsible PlannerCopy From ECC
6983PF2/WP2KAKOREFIDPOOLKPooled Capacity IDIndicatorS4 HANAKAKOREFIDPOOLKPooled Capacity IDNot used because it is only used if you are going to do a new creation once we are liveIndicatorSystem Generated
7084PF2/WP2KAKOSUPPKAvail. cap. limitsS4 HANAKAKOSUPPKAvail. cap. limitsConditional: Business Rule
If not entered 100% capacity will be used by default in the system - Copy from ECC
8571PF2/WP2KAKOVERSAActive VersionS4 HANAKAKOVERSAActive VersionCopy From ECC
8672PF2/WP2KAKOKAPTERRelevant to Finite SchedulingS4 HANAKAKOKAPTERRelevant to Finite SchedulingAlways set to X
8773PF2/WP2KAKOKAPAVOCan be used by several operationsS4 HANAKAKOKAPAVOCan be used by several operationsAlways set to X
8874PF2/WP2KAKOUEBERLASTOverload (%)S4 HANAKAKOUEBERLASTOverload (%)Copy from ECC
8975PF2/WP2KAKOKAPLPLNo Long-Term PlanningS4 HANAKAKOKAPLPLNo Long-Term PlanningAlways set to X
90PF2/WP2KAKOKAPEHCapacity UnitS4 HANAKAKOKAPEHCapacity UnitNot known if we are going to use PP/DS in the resource, so there is no values at the moment
91PF2/WP2KAKOMEHRHas Individual CapacitiesS4 HANAKAKOMEHRHas Individual CapacitiesNot known if we are going to use PP/DS in the resource, so there is no values at the moment
Term PlanningAlways set to X
7692PF2/WP2KAKOANG_UNITAv. cap. unitS4 HANAKAKOANG_UNITAv. cap. unitNot known if we are going to use PP/DS in the resource, so there is no values at the moment

NU - CFC9 manages it through APO without the need to update manually the fields are not required for ADM

7793PF2/WP2KAKOANG_MINMinimum capacityS4 HANAKAKOANG_MINMinimum capacityNot known if we are going to use PP/DS in the resource, so there is no values at the momentNU -CFC9 manages it through APO without the need to update manually the fields are not required for ADM
7894PF2/WP2KAKOANG_MAXMax. capacityS4 HANAKAKOANG_MAXMax. capacityNot known if we are going to use PP/DS in the resource, so there is no values at the momentNU -CFC9 manages it through APO without the need to update manually the fields are not required for ADM


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
13TFACD-Factory Calendar
14TC39A-Shifting Group
15TC27-Capacity Responsible Planner
16TC36-Active Version

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
2Configuration is missing

Verify that all configuration exists and reprocess when they are available (See configuration in Spec)


Post-Load Validation

Project Team

Completeness

TaskAction
Verify CountSyWay S2P P2F 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.
Validation Reports

Google Drive Live Link
urlhttps://docs.google.com/spreadsheets/d/1hNY2Vk_q3VWNbZHsvoX1C4aHUpkpFndX0RLyKCOUTWs/edit?gid=1447265869#gid=1447265869


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

Change History
limit10

Workflow history

Workflow Report
parent@self
hideheadertrue
typeapprovals