Status
Owner	TEE-ext, Paul
Stakeholders	ERGUIZA-ext, Pinky Love PUN-ext, Eddy JOSHI-ext, Aditya VILARES, ines LEIGHTON-ext, Dean HEARD-ext, Kevin MOUSSA-ext, Eva STEFANESCU-ext, Aurelia

Purpose

The purpose of this document is to define the conversion approach to create Safety Certificate Template in S/4 HANA.

To enhance the level of safety, an additional safety component - Safety Certificate - can be assigned to work permit. A safety certificate represents the formal safety document that contains the safety protocols for effectively managing the risks associated with certain equipment and sites.

SAP Safety Certificate Templates are standardized forms used in SAP S/4HANA to manage workplace safety requirements. They allow planners to define safety precautions, link certificates to work permits, and ensure compliance with plant safety regulations. Templates streamline certificate creation by providing reusable structures tailored to specific activities or plants.

Conversion Scope

The scope of this document covers the approach for creating Safety Certificate Template into S/4HANA following the Safety Certificate Template Master Data Design Standard. 

All Data for Safety Certificate Template are fully construted in the DCT.

The data from legacy system includes:

1. Not applicable

The data from legacy system excludes:

1. Not applicable

Note: There are no tables to extract from the source systems

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
DCT	All Safety Certificate Template data will be fully constructed, as it does not currently exist in the source systems and represents a new design in the to-be Syensqo landscape.	400	S/4 HANA	400

Additional Information

Multi-language Requirement

Safety Certificate Template does not have multi language support. Safety Certificate Template text will be migrated using EN logon.

Document Management

Not Applicable

Legal Requirement

Not Applicable

Special Requirements

Not Applicable

Target Design

With Functional input, document the technical design of the target fields that are in the scope of this document.

The technical design of the target for this conversion approach.

 1. Safety Certificate Template

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
ISFTYCERTTMPL	SAFETYCERTIFICATE	SAFETYCERTIFICATE	Number	CHAR	12	Mandatory
ISFTYCERTTMPL	SFTYCERTDESC	WCESTXT	Description	CHAR	40	Mandatory
ISFTYCERTTMPL	MAINTENANCEPLANNINGPLANT	IWERK	Maintenance Planning Plant	CHAR	4	Mandatory
ISFTYCERTTMPL	SAFETYCERTIFICATETYPE	WCEUSAGE	Safety Certificate Template type	CHAR	3	Mandatory
ISFTYCERTTMPL	SFTYCERTVALIDFRMDATE	WCEDATEFR	Valid From	DATS	8	Mandatory
ISFTYCERTTMPL	SFTYCERTVALIDFRMTIME	WCETIMEFR	Valid-From Time	TIMS	6	Mandatory
ISFTYCERTTMPL	SFTYCERTVALIDTODATE	WCEDATETO	Valid to	DATS	8	Mandatory
ISFTYCERTTMPL	SFTYCERTVALIDTOTIME	WCETIMETO	Valid-To Time	TIMS	6	Mandatory
ISFTYCERTTMPL	WORKCENTER	PPH_ARBPL	Main Work Center	CHAR	8	Mandatory
ISFTYCERTTMPL	WORKCENTERPLANT	WERKS_D	Main Work Center Plant	CHAR	4	Mandatory

 2. Safety Precautions

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
ISFTYCERTTMPL	SAFETYCERTIFICATE	SAFETYCERTIFICATE	Number	CHAR	12	Mandatory
ISFTYCERTPRC	SFTYCERTSAFETYPRECAUTIONGROUP	PTWESFTYRQMTGRP	Safety Requirement Group	CHAR	3	Mandatory
ISFTYCERTPRC	SFTYCERTSAFETYPRECAUTION	PTWESFTYRQMT	Safety Requirement	CHAR	3	Mandatory

 3. Approvals

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
ISFTYCERTTMPL	SAFETYCERTIFICATE	SAFETYCERTIFICATE	Number	CHAR	12	Mandatory
ISFCMAPPROVAL	SAFETYCERTIFICATEAPPROVALCODE	PMSOG	Approval type	CHAR	10	Mandatory
ISFCMAPPROVAL	SFTYCERTIFICATEAPPROVALSTATUS	PTWEWORKPERMITAPPROVALSTATUS	Approval status	CHAR	1	Mandatory

Safety Certificate Template Data strictly adheres to the Master Data Standard. The complete information of the key fields that hold the Safety Certificate Template information follows the Master Data Standard document that is located here.

Data Cleansing

Safety Certificate Template does not exist in the legacy system. Therefore, data cleansing is not applicable.

Data for the Safety Certificate Templat  will be captured directly in the Data Collection Template (DCT) and any required refinement will be carried out during the data construction activity.

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
		Not Applicable

Note: List of Cleansing is maintained here: Conversion Specs Register (DCT & Cleansing Report)

Conversion Process

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

Collection will be done manually in the Data Collection Template for the following scenarios:

• For all A2D In-scope Planning Plants.

Data Privacy and Sensitivity

Not Applicable

Extraction

Data extraction is not applicable, as no corresponding data exists in the legacy system.

Extraction Run Sheet

Req #	Requirement Description	Team Responsible
	Not Applicable

Selection Screen

If applicable, this section will give the details on any selection screen parameters, including the parameter type, that are required to be entered to ensure consistent data extracts.

Selection Ref Screen	Parameter Name	Selection Type	Requirement	Value to be entered/set
	Not Applicable

Data Collection Template (DCT)

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

Note: All rules specified below should be documented as a tooltip in the DC Page.

Format:

• Line 1: Mandatory / Conditional
• Line 2: Remaining text

 1. Safety Certificate Template DCT Rules

Field Name	Field Description	Rule
zSAFETYCERTIFICATE	Number	Mandatory. Staging identifier used to uniquely define a Safety Certificate Template.
SFTYCERTDESC	Description	Mandatory. Format: AAA-NNN AAA - Safety certificate NNN - running number All Letters must be Uppercase There should be no duplicate descriptions within the same plant. Example: CON-001, CON-002, etc. Note: Template will start with three letters, which will be a prefix for the type of safety certificate (e.g. CON for Confined Space, HOT for hot work, etc). This is followed by a running number. The prefix for the description must be aligned with the safety certificate template type setup in the configuration, e.g. the description of a confined space certificate can only be created for a confined space certificate template type.
MAINTENANCEPLANNINGPLANT	Maintenance Planning Plant	Mandatory. Allowed values: List from Value Mapping - Plant where Maintenance Plant = Yes
SAFETYCERTIFICATETYPE	Safety Certificate Template type	Mandatory. Must be a valid Safety Certificate Template Type (ISFTYCERTTMPLTYP).
SFTYCERTVALIDFRMDATE	Valid From	Mandatory. Start date of validity of template Must be current date or future date. No date in past Must be in DDMMYYYY format Note: During mocks and at go-live, "Current Date" should be treated as the "go-live" date. If a past date is provided, this will be set to the "go-live" date.
SFTYCERTVALIDFRMTIME	Valid-From Time	Mandatory. Start time of validity of template Must be in HHMMSS format  If the user does not provide a value, this will be set to 000000.
SFTYCERTVALIDTODATE	Valid To	Mandatory. End date of validity of template Must be a date in future and later than the Valid From date. Must be in DDMMYYYY format Note: Referring to the note in Valid From, if a past date is provided, this will be set to the "go-live" date plus the difference between the originally provided Valid To date and Valid From date.
SFTYCERTVALIDTOTIME	Valid-To Time	Mandatory. End time of validity of template Must be in HHMMSS format  If the user does not provide a value, this will be set to 235959.
WORKCENTER	Main Work Centre	Mandatory. Responsible work center for template Should exist in Work Centre DCT

 2. Safety Precautions DCT Rules

Field Name	Field Description	Rule
zSAFETYCERTIFICATE	Number	Mandatory. Staging identifier used to uniquely define a Safety Certificate Template.
SFTYCERTSAFETYPRECAUTIONGROUP	Safety Requirement Group	Mandatory. Must be a valid Safety Precautions Category (VPTWSFTCERTASGMT)
SFTYCERTSAFETYPRECAUTION	Safety Requirement	Mandatory. Must be a valid Safety Requirement (VPTWSFTCERTASGMT)

Note: Multiple Safety Precautions may be assigned to each Safety Certificate Template

  3. Approvals  DCT Rules

Field Name	Field Description	Rule
zSAFETYCERTIFICATE	Number	Mandatory. Staging identifier used to uniquely define a Safety Certificate Template.
SAFETYCERTIFICATEAPPROVALCODE	Approval type	Mandatory. Must be a valid value as per Safety Certifcate type (T357G)

Note: Multiple Approvals may be assigned to each Safety Certificate

Note: List of DCTs is maintained here: Conversion Specs Register (DCT & Cleansing Report)

Extraction Dependencies

List the steps that need to occur before extraction can commence

Item #	Step Description	Team Responsible
	Not Applicable

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 ADMM 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 Advanced Data Migration and Management (ADMM)
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 Description	Team Responsible
1	Obtain DCT Sign-off from Business.	SyWay Data Team
2	In dspMigrate, select the wave –R3 S4/HANA – Plant Maintenance	Syniti
3	Go to Process Area Launch and Process the Object – Safety Certificate Template	Syniti
4	Review and Validate Error and Preload Reports	Syniti
5	Execute the transformation to prepare the target tables	Syniti
6	Validate data from pre-load and error reports	Business/Data owner
7	Generate load files	SyWay Data Team

Transformation Rules

 1. General information

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	-	-	-	-	S/4 HANA	ISFTYCERTTMPL	SAFETYCERTIFICATE	Number	System Generated Note: To be created using the Custom Load Program. Leave this field blank in the Preload file
2	DCT	ISFTYCERTTMPL	SFTYCERTDESC	Description	S/4 HANA	ISFTYCERTTMPL	SFTYCERTDESC	Description	Direct Mapping
3	DCT	ISFTYCERTTMPL	MAINTENANCEPLANNINGPLANT	Maintenance Planning Plant	S/4 HANA	ISFTYCERTTMPL	MAINTENANCEPLANNINGPLANT	Maintenance Planning Plant	Direct Mapping
4	DCT	ISFTYCERTTMPL	SAFETYCERTIFICATETYPE	Safety Certificate Template type	S/4 HANA	ISFTYCERTTMPL	SAFETYCERTIFICATETYPE	Safety Certificate Template type	Direct Mapping
5	DCT	ISFTYCERTTMPL	SFTYCERTVALIDFRMDATE	Valid From	S/4 HANA	ISFTYCERTTMPL	SFTYCERTVALIDFRMDATE	Valid From	Direct Mapping. If the Valid From date is earlier than the value specified in Value Mapping: OTH_Migration_Date Relevant Values A2D (using Object ID "1206" and Field Name "ISFTYCERTTMPL-SFTYCERTVALIDFRMDATE"), replace it with the Value from OTH_Migration_Date Relevant Values A2D.
6	DCT	ISFTYCERTTMPL	SFTYCERTVALIDFRMTIME	Valid-From Time	S/4 HANA	ISFTYCERTTMPL	SFTYCERTVALIDFRMTIME	Valid-From Time	Direct Mapping. If blank, default  to "000000"
7	DCT	ISFTYCERTTMPL	SFTYCERTVALIDTODATE	Valid to		ISFTYCERTTMPL	SFTYCERTVALIDTODATE	Valid to	Direct Mapping. If the Valid From date is earlier than the value specified in Value Mapping: OTH_Migration_Date Relevant Values A2D (using Object ID "1206" and Field Name "ISFTYCERTTMPL-SFTYCERTVALIDFRMDATE"), replace it with the Value from OTH_Migration_Date Relevant Values A2D + (Valid to - Valid From)
8	DCT	ISFTYCERTTMPL	SFTYCERTVALIDTOTIME	Valid-To Time	S/4 HANA	ISFTYCERTTMPL	SFTYCERTVALIDTOTIME	Valid-To Time	Direct Mapping If blank, default  to "235959"
9	DCT	ISFTYCERTTMPL	WORKCENTER	Main Work Center	S/4 HANA	ISFTYCERTTMPL	WORKCENTER	Main Work Center	Direct Mapping
10	DCT	ISFTYCERTTMPL	MAINTENANCEPLANNINGPLANT	Maintenance Planning Plant	S/4 HANA	ISFTYCERTTMPL	WORKCENTERPLANT	Main Work Center Plant	Direct Mapping

 2. Safety Precautions

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	-	-	-	-	S/4 HANA	ISFTYCERTTMPL	SAFETYCERTIFICATE	Number	System Generated
2	DCT	ISFTYCERTPRC	SFTYCERTSAFETYPRECAUTIONGROUP	Safety Requirement Group	S/4 HANA	ISFTYCERTPRC	SFTYCERTSAFETYPRECAUTIONGROUP	Safety Requirement Group	Direct Mapping
3	DCT	ISFTYCERTPRC	SFTYCERTSAFETYPRECAUTION	Safety Requirement	S/4 HANA	ISFTYCERTPRC	SFTYCERTSAFETYPRECAUTION	Safety Requirement	Direct Mapping

  3. Approvals

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	-	-	-	-	S/4 HANA	ISFTYCERTTMPL	SAFETYCERTIFICATE	Number	System Generated
2	DCT	ISFCMAPPROVAL	SFTYCERTIFICATESUBOBJECTTYPE	Approval type	S/4 HANA	ISFCMAPPROVAL	SFTYCERTIFICATESUBOBJECTTYPE	Approval type	Direct Mapping
3	DCT	ISFCMAPPROVAL	SFTYCERTIFICATEAPPROVALSTATUS	Approval status	S/4 HANA	ISFCMAPPROVAL	SFTYCERTIFICATEAPPROVALSTATUS	Approval status	Default to "A"

List of Custom Target Reports for this object is maintained here: Conversion Specification - Custom Reports Register.

Transformation Mapping

Use the exact name and reference this section in the “Transformation rules” above

Mapping Table Name	Mapping Table Description
OTH_Migration_Date Relevant Values A2D	Dates to be defaulted for A2D objects for each Migration Cycle
Plant	Old to New Plant

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
1	Ensure DCT tables completeness	Syniti
2	Ensure all Transformation mappings are up to date.	Syniti

Pre-Load Validation

Project Team

The following pre-load validations will be performed by the Project Team.

Completeness

Task	Action
Verify Record Count	Data team to verify that the total number of relevant records from the source systems is equal to the total number of records in the Preload and Load Sheets.

Accuracy

Task	Action
Conversion Accuracy	SyWay A2D Data Team to verify that all fields below meet pass the checks: Mandatory Fields Field and Value Mapping Correctness Null Checks Text Length Checks
Review Error Reports	Review 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

The following pre-load validations will be performed by the business.

Completeness

Task	Action
Verify Record Count	Business team to verify that the total number of relevant records from the source systems is equal to the total number of records in the Preload and Load Sheets.

Accuracy

Task	Action
Conversion Accuracy	Business  to verify that all the data in the load table/file is accurate as per endorsed transformation/mapping rules (and signed-off 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

Note: A custom load program is required and is to be developed by the SyWay Development Team.

Load Run Sheet

Item #	Step Description	Team Responsible
1	Ensure Pre-load sign-offs are obtained.	SyWay Data team
2	Go to the load tool and select the correct load Program.	SyWay Data team
3	Proceed with Data load.	SyWay Data team
4	Validate few records loaded by accessing standard transactions.	SyWay Data team
5	Generate the post load reports in the tool.	SyWay Data team
6	Log errors as defects, if any and address resolutions. Close defects.	SyWay Data team
7	Resolve defects by re-upload and re-generate post load reports if necessary.	SyWay Data team
8	Business to validate the post load files as part of post-load validation, raise data defects or provide the post-load sign-off.	Business
9	Repeat steps 5 to 7 if necessary.	SyWay Data team

Load Phase and Dependencies

Pre-Cutover

Configuration

List the Configurations required before loading can commence

Item #	Configuration Item
1	T001W-Plants/Branches
2	ISFTYCERTTMPLTYP-Safety Certificate Template type
3	T357G-Permits
4	VPTWSFTCERTASGMT-Assign Safety Certificate

Conversion Objects

Object #	Preceding Object Conversion Approach
1006	Work Centre

Error Handling

The table below depicts some possible system errors for this data object during data load. All data load error is to be logged as defect and managed within the Defect Management

Error Type	Error Description	Action Taken
Configuration	Invalid Plant	Engage Functional team to expedite and fix the error in the system
Configuration	Invalid Safety Certificate Template type	Engage Functional team to expedite and fix the error in the system
Configuration	Invalid Approval type	Engage Functional team to expedite and fix the error in the system
Configuration	Invalid Safety Requirement Group	Engage Functional team to expedite and fix the error in the system
Configuration	Invalid Safety Requirement	Engage Functional team to expedite and fix the error in the system
Invalid Data	Invalid or Inactive Work Centre assigned	Expedite whether the master data is changed in the system

Post-Load Validation

Project Team

The following post-load validations will be performed by the Project Team.

Completeness

Task	Action
Verify Count	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.
Verify Logs	Check 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.).

Accuracy

Task	Action
Conversion Accuracy	Data team to verify that the Safety Certificate Template data in target S/4 HANA were loaded correctly via dspMigrate post load reports or standard reports from S/4 HANA.

Business

The following post-load validations will be performed by the business.

Completeness

Task	Action
Verify Count	Download 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

Task	Action
Conversion Accuracy	Verify that the Safety Certificate Template 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.
• Safety Certificate Template is in scope based on data design and any exception requested by business.
• Planning Plants in A2D scope are the same as Maintenance Plants in A2D scope. As per the SyWay to-be design, the Planning Plant will always correspond to the Maintenance Plant.
• A Safety Certificate Template is required where a Permit to Work Template is set up for the plants (although the Permit and Safety Certificate will not be linked)
• There must be at least one Safety Certificate Template per Planning Plant. Exceptions apply only to plants with local regulatory requirements, where no templates may be expected. 

Any additional key assumptions.

See also

Safety Certificate Template is managed using Fiori Application and the data sits within CDS views.

Since this is a new functionality, references have been included below to support the conversion process.

 1. General Information

 2. Safety Precautions

 3. Approvals

Change log