Functional/Technicalspecification Beximco Oracle Implementation - Project Batch Register of Paracetamol (OPM-R-003)

You might also like

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 16

FUNCTIONAL SPECIFICATION

FUNCTIONAL/TECHNICALSPECIFICATION
Beximco Oracle Implementation -Project
Batch Register of Paracetamol (OPM-R-
003)

Document Author Apurba Bhadra


Document Owner Apurba Bhadra
Version Number 1.0
Last Update Date 24-Jul-19
To-Be Doc Ref

Doc Ref: OPM-R-003 Page: 1 of 16


Version: 1.0 Printed Date: 14/07/2020
FUNCTIONAL SPECIFICATION

TABLE OF CONTENTS

1 DOCUMENT CONTROL.............................................................................................................................. 4
1.1 DOCUMENT CONTROL/CHANGE HISTORY.................................................................................4
1.2 DOCUMENT APPROVAL.............................................................................................................4
1.3 RELATED DOCUMENTS..............................................................................................................4
1.4 DISTRIBUTION LIST...................................................................................................................4
2 PURPOSE.................................................................................................................................................... 5
3 FUNCTIONAL OVERVIEW.......................................................................................................................... 6
3.1 SCOPE........................................................................................................................................6
3.2 ORACLE EBS GAP.....................................................................................................................6
3.3 IMPACT TO EXISTING SYSTEMS.................................................................................................6
3.4 IMPACTS TO PROCESSES............................................................................................................6
3.5 BUSINESS REQUIREMENTS........................................................................................................6
4 FUNCTIONAL SPECIFICATION.................................................................................................................. 7
4.1 PROCESS INFORMATION............................................................................................................7
4.2 PROCESS FLOW/CONCEPTUAL SOLUTION DESIGN....................................................................7
4.3 ASSUMPTION.............................................................................................................................7
4.4 COMPONENT OF THE SOLUTION................................................................................................8
4.5 ALL BUSINESS LOGIC, INCLUDING CALCULATIONS...................................................................8
4.6 DATA TRANSFORMATION/TRANSLATION..................................................................................8
5 CUSTOM OBJECTS.................................................................................................................................. 11
5.1 PARAMETERS...........................................................................................................................11
5.2 BUSINESS RULES.....................................................................................................................11
5.3 PROGRAM LOGIC.....................................................................................................................11
5.4 ERROR CONDITIONS:...............................................................................................................11
5.5 WARNING CONDITIONS:..........................................................................................................11
5.6 COLUMN DETAILS – TO BE PROVIDED POST DEVELOPMENT...................................................11
5.7 MAPPING TABLES/LOOK UP STRUCTURE.................................................................................12
6 APPLICATION SETUP.............................................................................................................................. 13
6.1 SYSTEM CONFIGURATION.......................................................................................................13
6.2 TECHNICAL & ARCHITECTURE FLOW DIAGRAM....................................................................13
6.3 PROGRAM LOGIC (PSEUDO CODE) :-ALREADY MENTIONED IN SEC. 5.6.................................13
6.4 SECURITY................................................................................................................................13
6.5 FREQUENCY.............................................................................................................................14
6.6 DEPENDENCIES/PREREQUISITES.............................................................................................14
6.7 SYSTEMCONFIGURATION........................................................................................................14
6.8 VOLUME ESTIMATES...............................................................................................................14
6.9 PERFORMANCE REQUIREMENTS..............................................................................................14
7 TEST PLAN/TEST CASES........................................................................................................................ 15
8 MIGRATION INSTRUCTIONS................................................................................................................... 16
9 ISSUE LOG................................................................................................................................................ 17

Doc Ref: OPM-R-003 Page: 2 of 16


Version: 1.0 Printed Date: 14/07/2020
FUNCTIONAL SPECIFICATION

1 DOCUMENT CONTROL

1.1 Document Control/Change History


Date Author Version Change Reference
DD-MON-YYYY (First Initial. Surname) (Refer to Document (Describe the reason for the change to the
Management Process) document)

24-JUL-2019 A.K. Bhadra 1.0 Base Version

1.2 Document Approval


Position/Title Name Signature Date
(Define the Position/Title of the (First Initial.Surname) DD-MON-YYYY
Approver)

Beximco Project Manager

KPMG Project Manager


Beximco Business Lead

1.3 Related Documents


Title Reference Version
DD-MON-YYYY (Refer to Document Management Process) (Version Number Distributed)

1.4 Distribution List


Date Distribution List Name Version Method
DD-MON-YYYY (Refer to Document Management Process) (Version Number (E-mail; Manual,
Distributed) Web Posting)

0.1 Email

Doc Ref: OPM-R-003 Page: 3 of 16


Version: 1.0 Printed Date: 14/07/2020
FUNCTIONAL SPECIFICATION

2 PURPOSE

The purpose of the document is to provide the specifications for creating the Batch Register Report for
production of Paracetamol.

Doc Ref: OPM-R-003 Page: 4 of 16


Version: 1.0 Printed Date: 14/07/2020
FUNCTIONAL SPECIFICATION

3 FUNCTIONAL OVERVIEW

3.1 Scope
The purpose of the document is to provide the specifications for creating Batch Register
Report for production of Paracetamol. This report would be used to enquire the historical
information of operations of a batch like “When did a particular operation complete” or “In
which resource was a particular operation processed” or “How much of purified yield of 2 nd
and 3rd crop is added back to synthesis of crude”.

3.2 Oracle EBS Gap


Seeded Oracle does not have any such report which would show the historical information of batch operations
and it’s operational yield in the desired format.

3.3 Impact to Existing Systems


There is no impact to any modules of Oracle system apart from OPM in any possible manner.

3.4 Impacts to Processes


This report would be used to carry out an “after the fact” kind of analysis on historical batch information.

3.5 Business Requirements


Below, are the gathered business requirements pertaining to this functionality:

BR # FIRST # Process # Requirement Statement Priority Fulfilment


Description

OUT-PE- User needs to see historical informationof batch


PE-
0001-CUS- operations for production of Paracetamol in excel Important Custom Report
0001
001 format.

Doc Ref: OPM-R-003 Page: 5 of 16


Version: 1.0 Printed Date: 14/07/2020
FUNCTIONAL SPECIFICATION

4 FUNCTIONAL SPECIFICATION

The objective being to create a customreport where users can see historical batch information.

4.1 Process Information


Process Description Inputs Processing Logic Outputs Format
Step

1 Beximco Batch Inventory Based on the Parameters with which As per the The report format
Register for Organization the report is run, the report should format. is shown below:
Paracetamol (M) extract all the eligible rows which the
Department parameter satisfies. Both Operation
(M) Start Date and Operation End Date
Start Date (M) should be evaluated – and if any one Batch Register
Paracetamol.xlsx
End Date (M) satisfies the date range, the record is
Item Code (O) eligible.
The report should be as per the
format attached.

The Organization’s department to be


filtered against lookup
XXBEX_DEPT_SUBDEPT
The value input by the user must be
used to filter batch records against
Segment8 of the organization item
and Segment1 of the Batch DFF.

4.2 Process Flow/Conceptual Solution Design

4.3 Assumption
1. None

Doc Ref: OPM-R-003 Page: 6 of 16


Version: 1.0 Printed Date: 14/07/2020
FUNCTIONAL SPECIFICATION

4.4 Component of the Solution


1. XML Publisher report to display the lines selected for printing.

4.5 All business logic, including calculations


1. Submit report with the following parameters - Inventory Organization (M), Department (M), Start Date
(M), End Date (M), Item Code (O)
2. Based on the Organization, select the batches as per the department stored in the Batch DFF Segment1.
Then use the date to identify the eligible batches which have been - Either Planned Start Date or Planned
Completion Date fall between the dates OR Either Actual Start Date or Actual Completion Date fall between
the dates.

4.6 Data Transformation/Translation


Data Field Meaning On Screen Field/Validation

Organization (P) Inventory Organization Inventory Organization selected by the user.

Department (P) The department of the To be selected from the lookup XXBEX_DEPT_SUBDEPT
batch. based on the organization selected.

Start Date Date range starting Start Date from Calendar


from

End Date (P) Date range ending at End Date from Calendar

Item Code (P) 10 digit item code From Item Master - to be filtered by Department

Item Code 10 Digit Item Code From Batch Item

Item Type Bulk or Finished Goods From Segment2 of Item Category

Receiving Date of BMR Batch start date Actual Start date of the Batch
and BPR

Dispensing date of Raw Dispensing Completion Actual Dispensing Operation Completion Date
Materials Date

Batch Number Batch Number Batch Number

Actual Qty. of Crude Operation Synthesis of Actual Operation Yield of Operation Crude Synthesis
Paracetamol – Weight Crude
(kg)

Actual Qty. of Crude Operation Synthesis of Actual completion date of Operation Crude Synthesis

Doc Ref: OPM-R-003 Page: 7 of 16


Version: 1.0 Printed Date: 14/07/2020
FUNCTIONAL SPECIFICATION

Data Field Meaning On Screen Field/Validation

Paracetamol – Crude
Completion Date

Purified Recovery Addition of Purified Batch Number from which the recovered and pre-
Crude Paracetamol – Recovery treated Paracetamol is added back to crude synthesis.
Sl. No.

Purified Recovery Addition of Purified Quantity of recovered and pre-treated Paracetamol is


Crude Paracetamol – Recovery added back to crude synthesis.
Weight (kg)
Grand Total of Crude Total Crude Sum of Crude Synthesised and Crude added back.
Paracetamol Paracetamol handled

Purified Paracetamol – Operation Purification Operation Completion Date


Completion Date

Purified Paracetamol – Operation Purification Operation Yield


Weight (kg)

Dried Paracetamol – Operation Drying Operation Completion Date


Completion Date

Dried Paracetamol – Operation Drying Operation Yield


Weight (kg)

Milling Paracetamol – Operation Milling Operation Completion Date


Completion Date

Milling Paracetamol – Operation Milling Operation Yield


Weight (kg)

Fluidized Paracetamol Operation Fluidizing Operation Completion Date


– Completion Date

Fluidized Paracetamol Operation Fluidizing Operation Yield


– Weight (kg)

Packing Paracetamol – Operation Packing Operation Completion Date


Completion Date

Packing Paracetamol – Operation Packing Operation Yield


Weight (kg)

Doc Ref: OPM-R-003 Page: 8 of 16


Version: 1.0 Printed Date: 14/07/2020
FUNCTIONAL SPECIFICATION

Data Field Meaning On Screen Field/Validation

Expiry Date Batch Expiry Expiry date of the Batch Yield

Doc Ref: OPM-R-003 Page: 9 of 16


Version: 1.0 Printed Date: 14/07/2020
FUNCTIONAL SPECIFICATION

5 CUSTOM OBJECTS
No Program Name Description Responsibility

1 Beximco Batch Beximco Batch Register of Paracetamol Production Supervisor


Register of (OPM-02)
Paracetamol (OPM-
02)

5.1 Parameters

Report Parameters :

1. Organization:
2. Department:
3. Item:
4. From Date:
5. To Date:

5.2 Business Rules


None

5.3 Program Logic


Joins based on tables mentioned in section 5.6

5.4 Error Conditions:


Any error condition will be handled as per the common error handling framework.

5.5 Warning Conditions:


None.

5.6 Column Details – To be provided post development


Important data fields are provided below:

Screen Attribute Name Database Tables Database Column Name

BATCH NO gme_batch_header BATCH_NO


ITEM TYPE mtl_item_categories_v segment2
RECEIVING DATE gme_batch_header attribute1
DISPENSING DATE OF RAW gme_batch_steps actual_cmplt_date FOR
MATERIAL DISPENSING
Actual Qty. of Crude gme_batch_steps, actual_step_qty OF

Doc Ref: OPM-R-003 Page: 10 of 16


Version: 1.0 Printed Date: 14/07/2020
FUNCTIONAL SPECIFICATION

Paracetamol mtl_transaction_lot_numbers gme_batch_steps OF


‘PAR-CRUDE’
(WEIGHT) OPERATION-
(TRANSACTION_QUAN
TITY OF
mtl_transaction_lot_numb
ers OF 4080000589)
Actual Qty. of Crude gme_batch_steps actual_cmplt_date OF
‘PAR-CRUDE’
Paracetamol
OPERATION
(COMPLETION DATE)
Purified Recovery Crude mtl_transaction_lot_numbers LOT NUMBER OF
4080000589
Paracetamol

(SL NO)
Purified Recovery Crude mtl_transaction_lot_numbers TRANSACTION_QUAN
TITY OF 4080000589
Paracetamol

Weight(Kg)

Grand Total of Crude gme_batch_steps Actual step Qty. of Crude


Paracetamol
Paracetamol

REST ALL OPERATIONS’ gme_batch_steps actual_cmplt_date


COMPLETION DATE
REST ALL OPERATIONS’ WEIGHT gme_batch_steps actual_step_qty

5.7 Mapping tables/Look up structure


TABLES:
Mtl_item_categories_v micv,
mtl_category_sets mcs,
mtl_system_items_b msib,
mtl_categories_kfv mck,
gme_material_details gmd,
gme_batch_header gbh,
gme_batch_steps gbs,
fnd_lookup_values flv,
gmd_operations goa,
mtl_category_sets mcs_fg

LOOKUPS:

XXBEX_OPRN_SEQ%[DEPT]

Text in [DEPT] to be replaced with actual department codes.

Doc Ref: OPM-R-003 Page: 11 of 16


Version: 1.0 Printed Date: 14/07/2020
FUNCTIONAL SPECIFICATION

6 APPLICATION SETUP

6.1 System Configuration

N/A

6.2 Technical & Architecture Flow Diagram

6.3 Program Logic (pseudo code)

Already mentioned in sec. 5.6

6.4 Security

Doc Ref: OPM-R-003 Page: 12 of 16


Version: 1.0 Printed Date: 14/07/2020
FUNCTIONAL SPECIFICATION

As per menu/ request group security

6.5 Frequency

As and when required

6.6 Dependencies/Prerequisites

Lookups and value sets must be setup

6.7 System Configuration

N/A

6.8 Volume Estimates

None

6.9 Performance Requirements

1.The program should be completed in reasonable time

Doc Ref: OPM-R-003 Page: 13 of 16


Version: 1.0 Printed Date: 14/07/2020
FUNCTIONAL SPECIFICATION

7 TEST PLAN/TEST CASES

Test Process Step Condition Description Expected Results


Case

Doc Ref: OPM-R-003 Page: 14 of 16


Version: 1.0 Printed Date: 14/07/2020
FUNCTIONAL SPECIFICATION

8 MIGRATION INSTRUCTIONS
For Oracle technical components, follow the below steps during migration.

 Table creation
 Synonyms, sequence, index migration
 Package spec and body migration
 Concurrent program migration
 Request group assignment

Doc Ref: OPM-R-003 Page: 15 of 16


Version: 1.0 Printed Date: 14/07/2020
FUNCTIONAL SPECIFICATION

9 ISSUE LOG
ID Issue Status Resolution Owner Target Impact
Date Date

Doc Ref: OPM-R-003 Page: 16 of 16


Version: 1.0 Printed Date: 14/07/2020

You might also like