Anda di halaman 1dari 8

A Guide to Using the Open Routing and Resource Interface

This paper serves as a reference when using the Open Routing and
Resource
Interface. It defines the tables used in importing routing information
and
provides information about mandatory, derived and optional column names.
Refer to the Oracle Manufacturing, Distribution, Sales and Service Open
Interfaces Manual (A-57332) for a complete set of instructions.
1.

TABLES.

You need to populate the following interface tables with data from your
legacy system before you use the Bill and Routing Interface program.
BOM_OP_ROUTINGS_INTERFACE
BOM_OP_SEQUENCES_INTERFACE
BOM_OP_RESOURCES_INTERFACE
BOM_OP_INSTRUCTIONS_INTERFACE
MTL_RTG_ITEM_INTERFACE
Once you load the data into the interface tables, you can launch the
Bill and Routing Interface program (BMCOIN) from the Import Bills and
Routings form in Oracle Bills of Material or Oracle Engineering. This
program assigns values, validates the data you include, and then imports
the new routings.
You can optionally create an item revision when you import a bill of
material
(BOM) by inserting a value for a revision at the same time you insert
your
BOM data. If you enter a value in the REVISION column of the
BOM_BILL_OF_MTLS_INTERFACE table, the Bill and Routing Interface program
inserts a row into the MTL_ITEM_REVISIONS_INTERFACE table. In order to
assign
multiple item revisions, it is better to insert data directly into the
MTL_ITEM_REVISIONS_INTERFACE table.
To import a routing with operations and resources, you need to populate
the following tables:
BOM_OP_ROUTINGS_INTERFACE
BOM_OP_SEQUENCES_INTERFACE
BOM_OP_RESOURCES_INTERFACE
With these three tables, you can create routing header information and
assign
operation and resource details. If you want to assign standard
instructions
to your routings, then you populate the BOM_OP_INSTRUCTIONS_INTERFACE
table.
You can optionally create a routing revision when you import a routing
by

inserting a revision at the same time you insert your routing data. If
you
enter a value in the PROCESS_REVISION column of the
BOM_OP_ROUTINGS_INTERFACE
table, the Bill and Routing Interface program inserts a row in the
MTL_RTG_ITEM_REVISIONS table. To insert multiple routing revisions, you
can
insert data directly into the BOM_RTG_REVS_INTERFACE table. If the
validation
is successful, the program then imports the data into
MTL_RTG_ITEM_REVISIONS.
2.

PROCESS_FLAG.

The column PROCESS_FLAG indicates the current state of processing for a


row
in the interface table. All inserted rows must have the PROCESS_FLAG
set to 1.
After populating the data into the interface tables, run the Bill and
Routing Interface program. The program assigns and validates all rows
with a status of 1 (Pending), and then imports them into the production
tables.
If the assign or validate procedure fails for a row, the program sets
the
PROCESS_FLAG to 3 (Assign/Validation Failed) for that row. The
successful rows
continue through the process of importing into the production tables.
If a row
fails on import, the program assigns a value of 4 (Import Failed) to the
PROCESS_FLAG. Successfully imported rows have a PROCESS_FLAG value of 7
(Import Succeeded).
3.

TRANSACTION AND REQUEST ID'S.

The Bill and Routing Interface program automatically updates the


TRANSACTION_ID
and REQUEST_ID columns in each of the interface tables. The column
TRANSACTION_ID stores a unique id for each row in the interface table
and
the REQUEST_ID column stores the concurrent request id number.
4.

BOM_OP_ROUTINGS_INTERFACE TABLE.
a.

REQUIRED COLUMNS FOR THE BOM_OP_ROUTINGS_INTERFACE TABLE.


You must always enter values for the following required columns

when

you insert rows into the BOM_OP_ROUTINGS_INTERFACE table.


PROCESS_FLAG
ASSEMBLY_ITEM_ID
ORGANIZATION_ID
ROUTING_TYPE

If you are creating an alternate routing, you must also enter a


value

in the ALTERNATE_ROUTING_DESIGNATOR column.


If the routing you import references a common routing, you must

enter a

value in the COMMON_ASSEMBLY_ITEM_ID or the


COMMON_ROUTING_SEQUENCE_ID
columns. Routings can only reference common routings that
belong to the
same organization. If the routing does not reference a common
routing,
the Bill and Routing Interface program defaults the value of the
ROUTING_SEQUENCE_ID for the COMMON_ROUTING_SEQUENCE_ID.
You can specify, in the ROUTING_TYPE column, whether the routing

is a
include
value
create

manufacturing routing or an engineering routing.

If you do not

a value for this column, Oracle Bills of Material defaults a


of 1 (manufacturing), and creates a manufacturing routing.

To

an engineering routing, you must enter a value of 2


(engineering) for
the ROUTING_TYPE column.
table,

For each new row you insert into the BOM_OP_ROUTINGS_INTERFACE


you should set the PROCESS_FLAG to 1 (Pending).

b.

DERIVED/DEFAULTED VALUES FOR BOM_OP_ROUTINGS_INTERFACE.


The Bill and Routing Interface program derives or defaults most

of the
columns

data required to create a manufacturing or engineering routing.


The Bill and Routing Interface program derives or defaults the

using the same logic as the Define Routing form or the Define
Engineering Routing form. When you populate a column in the
interface
table, the program imports the row with the data you included
and does
not default a value.
If you enter a value for the ASSEMBLY_ITEM_NUMBER or
COMMON_ITEM_NUMBER
column, you must insert the system item flexfield separator
between each
segment of your item number.
5.

BOM_OP_SEQUENCES_INTERFACE TABLE.
a.

REQUIRED COLUMNS FOR THE BOM_OP_SEQUENCES_INTERFACE TABLE

Each imported record must have a value for the following


columns:
PROCESS_FLAG
ROUTING_SEQUENCE_ID
OPERATION_SEQ_NUM
DEPARTMENT_ID
EFFECTIVITY_DATE
You must also specify a value in the
ALTERNATE_ROUTING_DESIGNATOR column
if you assign an operation to an alternate routing and have not
entered
a value for the ROUTING_SEQUENCE_ID column.
set the
program

When you insert rows into BOM_OP_SEQUENCES_INTERFACE, you must


PROCESS_FLAG to 1 (Pending) for the Bill and Routing Interface
to process the record.

b.

DERIVED/DEFAULTED COLUMN VALUES FOR BOM_OP_SEQUENCES_INTERFACE.


The Bill and Routing Interface program derives or defaults most

of the

data required to assign operations to a routing. You can


optionally
include a value for derived or defaulted columns, as well as
data for
any of the other columns in the interface. The interface
program uses
the same logic to derive or default column values in the
BOM_OP_SEQUENCES_INTERFACE table as in the
BOM_OP_ROUTINGS_INTERFACE
table. When you populate a column in the interface table, the
program
imports the row with the data you included and does not default
a
value. However, if you do not enter data in a derived or
defaulted
column, the program automatically imports the row with the
derived or
defaulted value.
BOM_OP_SEQUENCES_INTERFACE
OPERATION_SEQUENCE_ID
BOM_OPERATIONAL_SEQUENCES_S
ROUTING_SEQUENCE_ID
LAST_UPDATE_DATE
LAST_UPDATE_BY
CREATION_DATE
CREATED_BY
STANDARD_OPERATION_ID
DEPARTMENT_ID

Derived or Defaulted Value


Sequence
From BOM_OP_ROUTINGS_INTERFACE or
BOM_OPERATIONAL_ROUTINGS
System Date
Userid
System Date
Userid
From OPERATION_CODE
From DEPARTMENT_CODE

MINIMUM_TRANSFER_QUANTITY
COUNT_POINT_TYPE
EFFECTIVITY_DATE
BACKFLUSH_FLAG
REQUEST_ID
ASSEMBLY_ITEM_ID
OPTION_DEPENDENT_FLAG
ORGANIZATION_ID
RESOURCE_ID1
RESOURCE_ID2
RESOURCE_ID3
6.

0
1
System Date
1
From FND_CONCURRENT_REQUESTS
From ASSEMBLY_ITEM_NUMBER
2
From ORGANIZATION_CODE
From RESOURCE_CODE1
From RESOURCE_CODE2
From RESOURCE_CODE3

BOM_OP_RESOURCES_INTERFACE TABLE.
a.

REQUIRED COLUMNS FOR THE BOM_OP_RESOURCES_INTERFACE TABLE.


You must always enter values for the following required columns

when

you insert rows into the BOM_OP_RESOURCES_INTERFACE table:


PROCESS_FLAG
RESOURCE_SEQ_NUM
RESOURCE_ID
OPERATION_SEQUENCE_ID

You must specify a value in the ALTERNATE_ROUTING_DESIGNATOR


column if
you assign resources to an alternate routing and have not
entered a
value for the ROUTING_SEQUENCE_ID or the OPERATION_SEQUENCE_ID
column.
When you insert a row into the BOM_OP_RESOURCES_INTERFACE table,
you

must set the PROCESS_FLAG to 1 (Pending) for the Bill and

Routing

b.
of the

Interface program to process the record.


DERIVED/DEFAULTED COLUMN VALUES FOR BOM_OP_RESOURCES_INTERFACE.
The Bill and Routing Interface program derives or defaults most

data required to assign a resource to an operation. You can


optionally
include a value for derived or defaulted columns, as well as
data for
any of the other columns in the interface. The interface
program uses
the same logic to derive or default column values in the
BOM_OP_RESOURCES_INTERFACE table as in the
BOM_OP_ROUTINGS_INTERFACE
table and BOM_OP_SEQUENCES_INTERFACE tables. When you populate
a
column in the interface table, the program imports the row with
the

do not

data you included and does not default a value.

However, if you

enter data in a derived or defaulted column, the program


automatically
imports the row with the derived or defaulted value.
BOM_OP_RESOURCES_INTERFACE
OPERATION_SEQUENCE_ID
BOM_OP_SEQUENCES_INTERFACE or
RESOURCE_ID
ACTIVITY_ID
STATDARD_RATE_FLAG
BOM_RESOURCES.STANDARD_RATE_FLAG
ASSIGNED UNITS
USAGE_RATE_OR_AMOUNT
USAGE_RATE_OR_AMOUNT_INVERSE
BASIS_TYPE
SCHEDULE_FLAG
LAST_UPDATE_DATE
LAST_UPDATED_BY
CREATION_DATE
CREATED_BY
AUTOCHARGE_TYPE
BOM_RESOURCES.AUTOCHARGE_TYPE
REQUEST_ID
ASSEMBLY_ITEM_ID
ORGANIZATION_ID
ROUTING_SEQUENCE_ID

7.

Derived or Defaulted Value


Sequence
BOM_OPERATION_SEQUENCES_S
From RESOURCE_CODE
From ACTIVITY
From
1
1
1
From BOM_RESOURCES.DEFAULT_BASIS
2
System Date
Userid
System Date
Userid
From
From FND_CONCURRENT_REQUESTS
From ASSEMBLY_ITEM_NUMBER
From ORGANIZATION_CODE
From BOM_OP_ROUTINGS_INTERFACE or
BOM_OPERATIONAL_ROUTINGS

IMPORTING ADDITIONAL BILL INFORMATION.

When you create routings using the Bill and Routing Interface
program,
you can also assign standard instructions using the
BOM_OP_INSTRUCTIONS_INTERFACE table and insert multiple routing
revisions
using the MTL_RTG_ITEM_REVS_INTERFACE table. To import multiple
routing
revisions, you must insert the data directly into the
MTL_RTG_REVS_REVISIONS table. You can import standard comments for
each
BOM using the MTL_RTG_ITEM_REVS_INTERFACE table.
8.

BOM_OP_INSTRUCTIONS_INTERFACE TABLE.
a.

REQUIRED COLUMNS FOR THE BOM_OP_INSTRUCTIONS_INTERFACE TABLE.


To import data into the BOM_OP_INSTRUCTIONS_INTERFACE table, you

must

assign a value to the following columns:


OPERATION_SEQUENCE_ID
OPERATION_DESCRIPTION_CODE

PROCESS_FLAG
b. DERIVED/DEFAULTED COLUMN VALUES FOR
BOM_OP_INSTRUCTIONS_INTERFACE.
After inserting data into the BOM_OP_INSTRUCTIONS_INTERFACE
table, the
Bill and Routing Interface program derives the value for the
OPERATION_SEQUENCE_ID column if you populate the following
columns:
OPERATION_SEQ_NUM
EFFECTIVITY_DATE
ROUTING_SEQUENCE_ID
The program derives a value for the ROUTING_SEQUENCE_ID column
if

you populate the following columns:


ASSEMBLY_ITEM_ID
ALTERNATE_ROUTING_DESIGNATOR
ORGANIZATION_ID

9.

BOM_REF_DESGS_INTERFACE TABLE.
a.

REQUIRED COLUMNS FOR THE BOM_REF_DESGS_INTERFACE TABLE.


To import data into the MTL_RTG_ITEM_REVS_INTERFACE table you

must

assign values to the following columns:


PROCESS_REVISION
ORGANIZATION_ID
INVENTORY_ITEM_ID
PROCESS_FLAG
10. VALIDATING INTERFACE TABLE ROWS.
After you load the BOM and component data, the Bill and Routing
Interface
program validates the required data for the six interface tables.
BOM validation insures that each row has an included or defaulted
value
for all the required columns and verifies the information the same
way as
the Define Bill of Material and the Define Engineering Bill of
Material
forms validate manually entered bills. For example, you cannot
import a
standard bill and assign a model, option class, or planning item as
components.
If the Bill and Routing Interface program cannot assign a value to a

row or validate that row, the program sets the PROCESS_FLAG to 3


(Assign/
Validation Failed) and inserts a row into the MTL_INTERFACE_ERRORS
table.
To identify the error message for a failed row, the program
automatically
populates the UNIQUE_ID column in the error interface table with the
same
value as the TRANSACTION_ID value. Each error has a value for the
MESSAGE_NAME and REQUEST_ID columns in the error interface table.
The
MESSAGE_NAME column corresponds to messages stored in the Oracle
Application Message Dictionary and the REQUEST_ID column stores the
concurrent request id.
If the program detects any internal database error, the program
stores the
internal error in the MESSAGE_NAME column and stores the specific
database
error message in the ERROR_MESSAGE column.
If you import a bill of material with multiple components and one of
the components fails validation, then the bill will be created
without
the failed component. If however, the row in the
BOM_BILL_OF_MTLS_INTERFACE table fails, the bill of material and all
of its details are not imported.
11. CORRECTING FAILED ROWS.
You can review and report rows in the interface tables using
SQL*Plus
or any custom report you develop. Since all rows in the interface
table have a value for PROCESS_FLAG, you can easily identify records
that are successfully imported into Oracle Bills of Material and
Oracle
Engineering, or records that failed validation or import. You can
also identify individual records by the unique value for the
TRANSACTION_ID column. You can update any row from the interface
tables
using SQL*Plus. If you update a row to resolve invalid data, you
must set
the PROCESS_FLAG to 1 (Pending) for that row. If you delete a
failed row
and insert a replacement row, you should set the PROCESS_FLAG to 1
(Pending)
for the new row. When you resubmit the Bill and Routing Interface
program
all rows pending validation are processed.