CIO Document1 Page 1 / 7

Functional Specification

Document Summary
Document Name MM_E_417_FS_Automatic UD.docx

Type of Request Automation

Team Responsible MM

Business Process & Automating the usage decision process in New Buy Procurement
Scenario
CIO Document1 Page 2 / 7

Table of Contents
Document Summary ............................................................................................................................................................... 1
Table of Contents .................................................................................................................................................................... 2
Document History .................................................................................................................................................................... 3
Detailed Functional Specification ............................................................................................................................................ 4
Business Description ........................................................................................................................................................... 4
Business Case ..................................................................................................................................................................... 4
Functional Requirements..................................................................................................................................................... 4
Process Flow ....................................................................................................................................................................... 5
Unit Test Indicators .............................................................................................................................................................. 6
Dependencies ...................................................................................................................................................................... 6
Target Stakeholders ............................................................................................................................................................ 6
Performance Expectations .................................................................................................................................................. 7
Legal, Audit and Regulatory Requirements ......................................................................................................................... 7
Exception Requirements ..................................................................................................................................................... 7
CIO Document1 Page 3 / 7

Document History

Table 1 – Revisions and Approvals

Version Date Name Role Location of Change Changes Made Approvals

1.0 [Insert [Insert name [Insert role of [Insert document [Insert description of [Insert approver name
date] of person person who made section where change change] and date]
who made the change] was made]
the change]
1.0 Oct. 25/16 Gagandeep MM Consultant Document creation
Singh
CIO Document1 Page 4 / 7

Detailed Functional Specification

Business Description
‘Automatic Usage Decision’ is an implicit enhancement of existing Results recording (QE51N) functionality
to make the Usage decision automatic. This will reduce the manual work of the Quality inspector who
takes the usage decision very often.

‘Automatic Usage Decision’ will happen for the Inspection Lot, If all the inspection characteristics are
passed in Quality verification. If any of the inspection characteristics failed during Quality verification,
automatic Usage Decision won’t happen, User has to resolve the discrepancy before making the Usage
Decision.

Business Process Impacted: Automatic Usage Decision will happen only for Serialized CTE
materials. The existing Business Process will remain the same for non-Serialized CTE materials.

Frequency: Whenever the Quality Manager/ Inspector records the results for the Inspection Lot,
enhancement runs in the background executes Automatic UD based on the Inspection characteristics
results.

Business Case
Whenever procurement of material happens through ‘NB’ Purchase Order, During Goods Receipt
‘1xxxxxxxxx’ inspection lot will be created. After Quality Inspection, if all the Quality characteristics are
passed Program runs in the background and picks the inspection lot and makes the ‘Usage Decision’
automatically.

The same process will be followed for making the ’Usage Decision’ of ‘4xxxxxxxxx’ series inspection lot,
that will be created during goods receipt of ‘External Repair’.

Automatic UD is restricted to CTE Material Type (CSPR) in pilot phase. This enhancement is a part of
approved project requirement for sterilization and tracking of CTE materials.

Functional Requirements

Automatic Usage Decision will be implemented for all Canada Gas operation Business Units, for Serialized
CTE materials only.

Catalog Type 3 and selected sets under it will be used to select the Usage Decision Codes.

At the end of Quality results recording Automatic Usage decision will happen and at the bottom of the
screen it should display the message ‘Usage Decision has been made for inspection Lot 1XXXXXXXXX’

The following changes are required for developing this Form:

 Master data
o Usage Decision Codes
CIO Document1 Page 5 / 7

 Triggers
o At the end of result recording implicit enhancement calls the QA11 transaction and save the
Usage Decision, If all the characteristics are passed in Quality Inspection.

Process Flow

Role Measurement Procurement Warehouse Quality Department

Engineering Department Handler

A
START

Results Recording

Goods
Material Receipt with
Request Create PO Certificate
from Order check
Accept Reject

Purchase Update Create

Release Equipment Notificati
Requisition PO
from MRP Master on

Usage Resolve
Decision Notificati
on

End Complete
Notificatio
n

Automatic Usage Decision

CIO Document1 Page 6 / 7

Unit Test Indicators

The preliminary unit testing includes:

 Security roles/ authorization groups

o TBD
 Master data to be used
o Usage Decision Codes

 Data exceptions
o Automatic UD will happen only for CTE serialized materials

 Risks or other considerations such as

o NA

Dependencies
The label has following dependencies:
 Configuration
o NA

 Interfaces
o NA
 Conversions
o NA
 Historical data
o NA
 Workflows
o NA
 BW reports
o NA
 Portal changes
o NA
 Security roles
o NA
 Batch jobs
o NA
 Transactions
o QE51N (Implicit Enhancement done in QE51N to enable Automatic UD)

Target Stakeholders
Following list of stakeholders will be using these forms:

 Type of stakeholders and their business functions

o Quality Inspectors/ Managers records the Quality results and after that Usage Decision
happens automatically.

 Location of stakeholders
o Warehouse
CIO Document1 Page 7 / 7

 Intended use for the change

o Improve in work efficiencies and reduce manual effort

 Number of stakeholders
o TBD
 Frequency of use
o TBD

Performance Expectations
 Expectations of data volumes
o TBD
 Background/foreground processing
o Both
 Batch jobs outputs
o NA
 Timing (i.e., time of day or calendar date)
o Real time
 Complexity
o Medium
 Network traffic
o TBD
 Proactive monitoring that should be done once in production
o Medium

Legal, Audit and Regulatory Requirements

NA
Exception Requirements
NA