Status	Approved
Owner	ERGUIZA-ext, Pinky Love
Stakeholders	LEIGHTON-ext, Dean PUN-ext, Eddy JOSHI-ext, Aditya TEE-ext, Paul MOUSSA-ext, Eva STEFANESCU-ext, Aurelia DUNNE-ext, Al KOK-ext, Marcel

Purpose

The purpose of this document is to define the conversion approach to create Permit to Work in S/4 HANA.

Permit to Work in Work Clearance Management (WCM) provides a systematic approach in controlling and executing the operational and maintenance activities safely and efficiently in a worksite. The Permit to Work solution helps to manage the risks inherent to hazardous tasks and ensure that the necessary precautions are put in place to improve the safety of personnel, plant, and the environment.

To provide authorization for jobs that require high-risk activities, Permit to Work provides Work Permit, a formal printed document with the description of the work, the requirements to be fulfilled, and the safety measures to be followed. A work permit authorizes the receiver to carry out the specified work at the specified time and acts as an agreement between the issuer and the receiver about the conditions, risks, and precautions involved.

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.

Conversion Scope

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

All Data for Permit to Work - Work Permit Template will be build in the DCT.

The data from legacy system includes:

Not applicable

The data from legacy system excludes:

Not applicable

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 system and represents a new design in the to-be Syensqo landscape.	200	S/4 HANA	200

Additional Information

Multi-language Requirement

Permit to Work Template does not have multi language support. Permit to Work Template text will be migrated using EN logon.

Document Management

Not Applicable

Legal Requirement

Not Applicable

Special Requirements

Not Applicable

Target Design

1. Permit to Work Template

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
IWRKPMTTEMPLATE	WORKPERMIT	WCEWAPINR	Application	CHAR	12	Mandatory
IWRKPMTTEMPLATE	WORKPERMITTYPE	WCEUSAGE	Usage of WCM Object	CHAR	3	Mandatory
IWRKPMTTEMPLATE	WRKPERMITDESC	WCESTXT	Descriptive Short Text	CHAR	40	Mandatory
IWRKPMTTEMPLATE	MAINTENANCEPLANNINGPLANT	IWERK	Maintenance Planning Plant	CHAR	4	Mandatory
IWRKPMTTEMPLATE	OPERATIONWORKCENTERINTERNALID	CR_OBJID	Object ID of the resource	NUMC	8	Mandatory
IWRKPMTTEMPLATE	WRKPERMITVALIDFRMDATE	WCEDATEFR	Valid-From Date for WCM Object	DATS	8	Mandatory
IWRKPMTTEMPLATE	WRKPERMITVALIDFRMTIME	WCETIMEFR	Valid-From Time for WCM Object	TIMS	6	Mandatory
IWRKPMTTEMPLATE	WRKPERMITVALIDTODATE	WCEDATETO	Valid-To Date for WCM Object	DATS	8	Mandatory
IWRKPMTTEMPLATE	WRKPERMITVALIDTOTIME	WCETIMETO	Valid-To Time for WCM Object	TIMS	6	Mandatory
IWRKPMTTEMPLATE	WORKCENTER	PPH_ARBPL	Work Center	CHAR	8	Mandatory
IWRKPMTTEMPLATE	WORKCENTERPLANT	WERKS_D	Plant	CHAR	4	Mandatory

2. Approvals

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
IWPMAPPROVAL	WORKPERMIT	WCEWAPINR	Application	CHAR	12	Mandatory
IWPMAPPROVAL	WORKPERMITAPPROVAL	PMSOG	Permit Key	CHAR	10	Mandatory
IWPMAPPROVAL	WORKPERMITAPPROVALSTATUS	PTWEWORKPERMITAPPROVALSTATUS	Work Permit Approval Status	CHAR	1	Mandatory
IWPMAPPROVAL	WORKPERMITAPPROVALDESCRIPTION	GNTXT	Permit Text	CHAR	30	Mandatory
IWPMAPPROVAL	WRKPMTMGMTOBJSUBTYPE	WCETYP	Type of WCM Object	CHAR	1	Mandatory

Permit to Work 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

Work Permit Template doesn't exist in legacy and therefore data cleansing is not applicable.

Data for Work Permit Template will be populated directly in the Data Collection Template (DCT) and any data refinement required will be performed as part of the construction activity.

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
NA

Conversion Process

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

Data Privacy and Sensitivity

Collection will be done manually in the Data Collection Template for A2D In-scope Planning Plants

Extraction

Data extraction not applicable as data doesn't exist in legacy.

Extraction Run Sheet

Req #	Requirement Description	Team Responsible
NA

Selection Screen

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

Data Collection Template (DCT)

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

Permit to Work Template DCT Rules <To add more info below later>

Field Name	Field Description	Rule

Extraction Dependencies

Item #	Step Description	Team Responsible
NA

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:

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
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 – Work Permit 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

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

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

Transformation Mapping

Mapping Table Name	Mapping Table Description

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

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

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

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

Custom Load tool will be used to upload the Work Permit Template. The load tool should replicate data creation method under class CL_WCM_PTW_HELPER_ROOT to accommodate upload of all the necessary data sets.

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

Item #	Configuration Item
1	Authorisation Groups
2	Nature of Work
3	Personal Protective Equipment
4	Safety Precautions
5	Approval Categories
6	Approval Types
7	Work Permit Type
8	Work Permit Template Types

Conversion Objects

Object #	Preceding Object Conversion Approach
1002	Equipment
1003	Functional Location
1006	Work Center
3001	Business Partner - Employee (BUP003)

Error Handling

Error Type	Error Description	Action Taken

Post-Load Validation

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 Work Permit Template data in target S/4 HANA were loaded correctly via dspMigrate post load reports or standard reports from S/4 HANA.

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 Work Permit 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.
Permit to Work Template is in scope based on data design and any exception requested by business.

Change log

Version	Published	Changed By
CURRENT (v. 16)	Feb 09, 2026 11:20	ERGUIZA-ext, Pinky Love
v. 75	Jan 29, 2026 07:44	ERGUIZA-ext, Pinky Love
v. 74	Jan 28, 2026 06:30	ERGUIZA-ext, Pinky Love
v. 73	Dec 15, 2025 15:21	ERGUIZA-ext, Pinky Love
v. 72	Dec 15, 2025 14:53	ERGUIZA-ext, Pinky Love
v. 71	Dec 15, 2025 14:31	ERGUIZA-ext, Pinky Love
v. 70	Dec 15, 2025 14:23	ERGUIZA-ext, Pinky Love
v. 69	Dec 11, 2025 13:11	ERGUIZA-ext, Pinky Love
v. 68	Dec 11, 2025 12:53	ERGUIZA-ext, Pinky Love
v. 67	Dec 11, 2025 12:50	ERGUIZA-ext, Pinky Love

Go to Page History

May 06, 2026	Actor	Type	Activity	Version
Approved	MOUSSA-ext, Eva	Comment	commented 2:51 pm two rows exist? what is the reason?
Feb 23, 2026
	TAN-ext, Charmaine	State	changed state to Approved at 3:16 pm (State override) [PMO Comments] Conversion Spec completed as per CS register and functional review completed	v76
Lead Approval	TAN-ext, Charmaine	State	gave Minor change approval at 3:16 pm [PMO Comments] Conversion Spec completed as per CS register and functional review completed
Feb 10, 2026
	ERGUIZA-ext, Pinky Love	Comment	commented 12:46 pm Hi MOUSSA-ext, Eva in response to your points above. Please see below: 1. In response to 1st point 2. Any future changes to load process, structure, or requirements will be managed through the CR process
	MOUSSA-ext, Eva	Comment	commented 12:11 pm Please acknowledge: the Development Team will not review this CS, in line with the development process. Our review is strictly from a construct and transformation perspective, with the standard ADMM preload file as the agreed output. Any future changes to load process, structure, or requirements will be managed through the CR process. Ownership of load program build, load execution, and scheduling as indicated in Al's reply remains with the Development/Data teams, and these items sit outside CS scope.
		State	changed expiry date to '17 Feb, 2026 11:49 am' at 11:49 am
		State	changed state to Lead Approval at 11:49 am	v76

Workflow history

Space shortcuts

Page tree

CNV-1004 Permit to Work Template

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

Data Cleansing

Conversion Process

Data Privacy and Sensitivity

Extraction

Data Collection Template (DCT)

Extraction Dependencies

Transformation

Transformation Run Sheet

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

Load Run Sheet

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

See also

Change log