OPM Organizations

Organizational Structure Overview

Organization structure defines the reporting hierarchy for Operating units, Plants and Warehouses.
An organization is an accounting structure. It can be a manufacturing plant, a corporate office, or
just a convenient shell within which figures from lower-level reporting structures can accumulate.
There can be several parent/child organizations within a single structure.
A top-level organization must be defined as a "company" to indicate that it is an end level
reporting structure with or without sharing a single set of books. It is important to define top-level
organizations (companies) first and then define the lower-level organizations (plants and
warehouses) beneath each of the organizations.
The actual plants are directly assigned to the respective parent organizations. This allows the
individual plants to consume and replenish from the same warehouse that belongs to the parent
company and allows an efficient way of mapping transactional cost through to the parent company
(and eventually to the company itself).

Company
Organizations
Warehouse
Locations

Warehouses Overview
Generally, a Warehouse is defined as an area or building in which you stock inventory (bulk
materials, containers, finished goods, and packaged items).
Warehouses are Process-Enabled Inventory Organizations. You will use the Warehouses window to
query each Process-Enabled Inventory Organization (previously created in OPM System
Administration), then enter and save additional warehouse information.
Path: System Admin>OPM System Admin>Setup>HR Organizations

Location Controlled Warehouses

You can indicate whether a warehouse is location controlled. Items flagged as location controlled in
the Item Master must have a warehouse location assigned to them.
Prior to creating Organizations/Warehouses, you will need to establish addresses in Oracle to detail
ship-to, receiving, or billing addresses.

Default Sub-inventory
In order to add Stock Locators (or OPM warehouse locations), a sub-inventory must be defined for
each inventory organization.

To assign a default sub-inventory follow the following path:

Responsibility: Inventory > Menu: Setup > Organization > Subinventories.

Stock Locations Overview

You have the option of dividing your warehouses into areas called locations. A location can be an
area of the warehouse (row, aisle, bin, a group of shelves, a pallet, or anything you choose).
Locations allow you to store units of an item in the same (or different) warehouse, but still remain
unique as items within the warehouse since they reside in different locations. Locations can be
made to represent stock received on different dates, stock with different degrees of quality, or
whatever you wish.
Items may also be flagged as location controlled. If both an item and the warehouse in which it is
stocked are location controlled, a location code must be entered whenever the item number is
entered on data entry windows or transaction windows.

Varying Location Control

OPM offers various degrees of location control. Validated location control requires that valid
locations be specified on data entry windows whenever you enter an item or warehouse code. You
define and maintain locations on the Locations window. Non-validated location control requires
that location codes be entered for the items and warehouses, but they do not have to be
established (valid) locations. Location control is contingent on how both the items and warehouses
are flagged. In order for validated location control to be in effect, both the item and the warehouse
must be flagged for validated location control.
Path: Inventory>OPM Inventory Control>Setup>Stock Locator

Recipes
Recipe Overview
Use the Formulator or Process Engineer responsibilities to define the formulas and routings that
drive your manufacturing process. Formulas are lists of ingredients and products, and their
associated quantities. In some cases, you may refer to formulas as the bill of material (BOM).
Every batch in the Production Management application is based on a formula defined in the
Formula Management application.
A Formula defines the ingredients and their attributes used to manufacture a product.
A Routing defines the method or steps that are taken to manufacture that product. Routings
consist of operation steps. Operation steps are made up of activities and associated resources.
Here are the steps you need to take to create routings:
Define the resources. A resource is what is used to perform the activity. A resource could be a
person (labor) or a machine (equipment). For example, a mixer (resource) could be associated
with
mixing (activity) to define the mixing operation. Resources are defined in the Capacity
Requirements
Planning (CRP) application.
Define the activities. These are the actions taken during production, such as mixing, heating or
cooling. Activities should be divided by logical breakpoints, such as where measurements are
taken.
Activities can then be associated with resources to form operations.
Define the operations, which contain the activities. Operations are steps in the routing. The
different
operations you define are linked to define a routing.
A visual representation of the Recipe structured relationship follows:

OPM APIs
As usual APIs facilitate integration with complementary third party , in-house developed, or legacy
applications. These APIs are standard in Oracle Process Manufacturing in various releases.
The benefits of OPM APIs are same usual:

Automate data collection from plant devices

Reduce custom interface code
Provide easier software upgrades
Allow connection to legacy systems
Eliminate manual data entry and errors

So here are the List of APIs for Integration in OPM (Adopted)

Production / POC
Start Resource Usage
End Resource Usage
Close Batch
Cancel Batch
Release, Certify, and Close Step
Post Resource Transaction
Incremental Resource Transaction
Timed Resource Transaction
Costing
Item Cost
Resource Cost
Allocation Definition
Burden Details
Formula
Create Formula
Insert Ingredients, (By)Products
Create Formula Usage Rules
Inventory
Create Item
Create Lot
Create Item/Lot UOM Conversion
Create, Adjust, or Move Inventory
Change Lot Status or QC Grade
Quality
Assays
Specifications
Samples
Sample Labels
Results

As far as APIs are concerned, it depends on what you want to do. Oracle forms are full function as
delivered. APIs get involved when you want to integrate with non-OPM applications. For instance, I

just finished a PL/SQL packed method that reads a CSV file containing recipe, formula and routing
information and calls several APIs to populate OPM recipes, formulas, routings and operations. Our
engineers felt Oracle is too complicated to use the forms. Being an Oracle-phile I disagreed but we
aim to please and
the recipe generator was created.
I wrote another routine to integrate our laboratory information management system (LIMS) from
Applied Biosystems (formerly Perkin Elmer-Nelson) with OPM quality. That involved the tables
GMD_SAMPLES and GMD_RESULTS.
So, to the point, what specifically do you want to integrate via APIs, batches, recipes, inventory?
Your reference to ASCP tables leads me to believe you also want to know about OPM's item master
tables IC_ITEM_MST_B and IC_ITEM_MST_TL as well as the lot master table IC_LOTS_MST. See
IC_LOCT_INV to determine how much of what is stored where.
It's important to remember that Oracle lots are uniquely defined by item number, lot number and
sublot number. Item number (item_no) is defined in IC_ITEM_MST_B. Lot number (lot_no) and Sub
Lot number (sublot_no) are defined in IC_LOTS_MST.

BATCHES
The primary table is GME_BATCH_HEADER. It contains basic information regarding the batch such
as plant_code, batch_number, batch_type (0 for normal batches or 10 for firm planned orders), and
batch_status.
Note: batch_status translations are to be found in GEM_LOOKUPS.
Batches have many steps which are found in GME_BATCH_STEPS. It's not in the example query;
but, the operation name can be found in GMD_OPERATIONS_B which is linked by oprn_id.
Steps have many activities which are found in GME_BATCH_STEP_ACTIVITIES.
Activities have many resources which are found in GME_BATCH_STEP_RESOURCES.
Resources have many process parameters which are found in GME_PROCESS_PARAMETERS.
Process parameters is OPM's way of letting the customer easily store information not designed into
the GME schema. Think of it like a descriptive flex field (not on steroids).
The name of the process parameter can be found in GMP_PROCESS_PARAMETERS.
Note that I haven't mention ingredients, products and byproducts yet.
This is merely the basic batch structure. Refer to the eTRM in MetaLink to determine the purpose
of the columns in the tables. Also, remember you can perform a "Help > Examine" from the Batch
form to see the name of the column as used in the form. Oracle hasn't owned OPM long enough to
make it truly complicated so it's not a difficult research project.
/*-------------------------- Sample Query --------------------*/
SELECT 'gme_batch_header', gbh.*,
'gme_batch_steps', gbs.*,
'gme_batch_step_activities', gbsa.*,
'gme_batch_step_resources', gbsr.*,
'gmp_process_parameters', gppp.*,
'gme_process_parameters', gpp.*
FROM gmp_process_parameters gppp,
gme_process_parameters gpp,
gme_batch_step_resources gbsr,
gme_batch_step_activities gbsa,
gme_batch_steps gbs,
gme_batch_header gbh
WHERE gbh.batch_id = gbs.batch_id
AND gbs.batchstep_id = gbsa.batchstep_id

AND
AND
AND
AND
AND
AND

gbsa.batchstep_activity_id = gbsr.batchstep_activity_id
gbh.batch_id = gpp.batch_id
gbs.batchstep_id = gpp.batchstep_id
gbsa.batchstep_activity_id = gpp.batchstep_activity_id
gbsr.batchstep_resource_id = gpp.batchstep_resource_id
gpp.parameter_id = gppp.parameter_id

OPM Tables
GMD_SAMPLES
GMD_RESULTS
GMD_OPERATIONS_B
GME_BATCH_HEADER
GME_BATCH_STEPS
GME_BATCH_STEP_ACTIVITIES
GME_BATCH_STEP_RESOURCES
GME_MATERIAL_DETAILS
GME_PROCESS_PARAMETERS
GMP_PROCESS_PARAMETERS
GEM_LOOKUPS
IC_ITEM_MST_B
IC_ITEM_MST_TL
IC_LOTS_MST
IC_LOCT_INV