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

Purpose

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

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

In Syensqo’s SAP S/4HANA landscape a work permit template provides a predesigned structure that can be used to create work permits in a consistent format. Creating work permits using a template allows you to simplify and streamline the work permit generation process.

The governance of this object shall be managed through tier 2.

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 Permit to Work 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.	300	S/4 HANA	300

Additional Information

Multi-language Requirement

Based on the plant the language will be localized.

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.General information

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
ISFTYCERTTMPL	SAFETYCERTIFICATEINTERNALID	J_OBJNR	Number	CHAR	22	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
PTWSFTYRQMTGRP	PTWSFTYRQMTGRP	PTWSFTYRQMTGRP	Safety Precautions Category	CHAR	3	Mandatory
PTWSFTYRQMTTXT	PTWSFTYRQMTTXT	PTWSFTYRQMTTXT	Safety Precautions Description	CHAR	100	Mandatory

3.Approvals

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
ISFCMAPPROVAL	SFTYCERTIFICATESUBOBJECTTYPE	WCETYP	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 Permit to Work Template information follows the Master Data Standard document that is located here.

Data Cleansing

Safety Certificate Template 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.General information DCT Rules

Field Name	Field Description	Rule
SAFETYCERTIFICATEINTERNALID	Number	Mandatory. Staging identifier used to uniquely define a Permit to Work Template.
SFTYCERTDESC	Description	Mandatory. 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. - AAA - Safety certificate  - NNN should be running number - All Letters must be Uppercase - There should be no duplicate descriptions within the same plant. -Example: CON-001, CON-002, etc.
MAINTENANCEPLANNINGPLANT	Maintenance Planning Plant	Mandatory. Allowed values: List from Value Mapping - Plant where Maintenance Plant = Yes
SAFETYCERTIFICATETYPE	Safety Certificate Template type	Mandatory.
SFTYCERTVALIDFRMDATE	Valid From	Mandatory. Must be current or future date. No date in past. Must be in DDMMYYYY format
SFTYCERTVALIDFRMTIME	Valid-From Time	Mandatory. Must be in HHMMSS format
SFTYCERTVALIDTODATE	Valid to	Mandatory. Must be a date in future and later than the Valid From date. Must be in DDMMYYYY format
SFTYCERTVALIDTOTIME	Valid-To Time	Mandatory. Must be in HHMMSS format
WORKCENTER	Main Work Center	Mandatory.
WORKCENTERPLANT	Main Work Center Plant	Mandatory.

 2.Safety Precautions DCT Rules

Field Name	Field Description	Rule
PTWSFTYRQMTGRP	Safety Precautions Category	Mandatory.
PTWSFTYRQMTTXT	Safety Precautions Description	Mandatory. PTWSFTYRQMTGRP

 3.Approvals DCT Rules

Field Name	Field Description	Rule
SFTYCERTIFICATESUBOBJECTTYPE	Approval type	Mandatory. Note: Must be a valid value as per Safety Certifcate type. Multiple Approval types may be assigned (T357G)
SFTYCERTIFICATEAPPROVALSTATUS	Approval status	Mandatory. Note: To use the permit template in the process the final status must be A - Approved

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 Syniti Migrate 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 Syniti Migrate
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

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic

Transformation Mapping

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

Mapping Table Name	Mapping Table Description

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible

Pre-Load Validation

Project Team

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

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Business

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

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

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 Description	Team Responsible

Load Phase and Dependencies

Identify the phase as to “when” the load for this object will occur. <Pre-Cutover, Cutover, Post Cutover> and list the steps that need to occur before the load can commence

Configuration

List the Configurations required before loading can commence

Item #	Configuration Item

Conversion Objects

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

Error Handling

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

Post-Load Validation

Project Team

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

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Business

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

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Key Assumptions

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

Any additional key assumptions.

See also

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log