You are on page 1of 50

Oracle Work in Process

Component Pick Release


An Oracle White Paper
April 2011
V2 : Modified Aug 2014

Table of Contents
1. OVERVIEW ............................................................................................................................................................................................................................... 1
2. WHAT IS COMPONENT PICK RELEASE ? ............................................................................................................................................................................ 1
3. SETUP REQUIREMENTS FOR COMPONENT PICK RELEASE ........................................................................................................................................... 3
4. STEP BY STEP PROCESSING OF COMPONENT PICK RELEASE ....................................................................................................................................... 7
5. EXAMPLE DEMONSTRATION OF COMPONENT PICK RELEASE ................................................................................................................................17
6. WHAT HAPPENS IF I RUN COMPONENT PICK RELEASE AGAIN FOR THE SAME JOB OR SCHEDULE ? ................................................................25
7. WHAT HAPPENS WHEN A JOB OR SCHEDULE IS CANCELLED? ...................................................................................................................................25
8. COMPONENT PICK RELEASE CONCURRENT PROGRAM : .............................................................................................................................................25
9. ADVANTAGES OF COMPONENT PICK RELEASE..............................................................................................................................................................27
10. WHICH API CAN BE USED TO CREATE A COMPONENT PICK RELEASE?..................................................................................................................28
11. DEBUGGING COMPONENT PICK RELEASE ...................................................................................................................................................................29
12. DIFFERENCES IN COMPONENT PICK RELEASE FUNCTIONALITY BETWEEN RELEASE 11 AND RELEASE 12 (MODIFIED AUG 2014).....30
13. IMPORTANT NEW FUNCTIONALITY IN 12.1.3 : EAM WORK ORDERS COMPONENT PICK RELEASE CONC PROGRAM (AUG 2014) ..........30
14. NEW R12 FUNCTIONALITY FOR SERIALISED JOBS FOR COMPONENTS WITH NO SUBINVENTORY DEFINED (AUG 2014) .........................32
15. COMMON ISSUES/ERRORS IN COMPONENT PICK RELEASE ..................................................................................................................................33

1. OVERVIEW
The objectives of this white paper are to discuss component pick release in
particular to understand the functionality, the required setups , the step by
step business process and the common issues seen in this area. There is no
existing document which collates all the relevant topics together. This white
paper will aim to fulfill this need and discuss the following in detail :

To explain what component pick release is


To give a high level overview of setup requirements for component
pick release (the actual details are documented in the appropriate
implementation guides so there is no need for detail)
To explain the component pick release process in step by step format
Include a step by step example of running component pick release
Looks at the api which can be used to create a component pick
release and includes a sample script.
Looks at the tables used in the component pick release process and
includes some sample queries for troubleshooting.
To explain the differences in functionality for component pick release
in R11 and R12
To discuss the common issues/errors seen in the component pick
release process and look at how to correct these.

2. WHAT IS COMPONENT PICK RELEASE ?


Component picking is the process of
establishing the component
requirements for jobs and schedules and then moving the component items
from the source location to the specified destination ( which could be a
staging area or the actual job/schedule itself).
The functionality of component pick release is as follows :

Component Pick Release is used to select requirements for discrete


jobs, lot based jobs, repetitive schedules, and flow schedules.

Component Pick Release then creates move orders for the picked
items. Move orders are requests for the movement of material within
an organization. They enable the replenishment of material within a
warehouse or manufacturing shop floor.

The source for the material picked is based on Oracle Inventory


allocation rules entered on the Inventory Picking Rules window.
However, if Warehouse Management is installed, rules based picking
can also be used.

Grouping rules are used to control how the picking tasks are grouped
for picking.

The destination for picked material depends on the supply type for
the material. It can be a staging area, or directly to a job or schedule.

The two step material issue process seen in Enterprise Asset


Management mimics Component Pick Release.

In summary component pick release can be defined as the process of


selecting the material requirements for discrete jobs, lot based jobs,
repetitive schedules, and flow schedules and then creating the move orders
for the picked material to enable the movement of the material from the
source location to the work order.
3. SETUP REQUIREMENTS FOR COMPONENT PICK RELEASE :
The following setups are required for Component Pick Release (the detail for
setting these up can be found in the WIP/Inventory/Warehouse Management
implementation/user guides and is not necessary to indlude here) :
1. Ensure that the standard setups for WIP, Inventory are done. This is a prerequisite step.
2. A BOM for the assembly specifying the required components with the
appropriate supply types (Push, Assembly Pull, Operation Pull) needs to
be defined.
3. Set the Release Backflush Components parameter as required.
Component pick release ONLY considers wip components of supply type
push. However, if this parameter is enabled, then components of supply
type assembly pull and operation pull will also be considered. Setting
this parameter will impact Kanban components since these are normally
defined as assembly pull components.
This is set using :
WIP>Setup>Wip Parameters>Material Parameters> Release Backflush
Components parameter.
4. Define the Source Subinventory. This is the subinventory in which the onhand stock is available or the subinventory from which the components
are to be picked. This should be defined as reservable - this means that
items can be reserved in the subinventory. Inventory Picking Rules will
contain the sourcing information that decide which source
subinventories to pick the material from. The source subinventory will
obviously require the appropriate components to be on-hand for picking.
5. Define the Supply Subinventory. The supply subinventory is the staging
subinventory or the subinventory which receives the components from
the source subinventory through the move order (the destination
2

subinventory). This should NOT be reservable. If the organization is


WMS enabled organization, the supply subinventory should also NOT be
LPN controlled.
6. Assigning supply subinventory for pull components. Assembly pull and
operation pull components are moved to a staging area destination when
the move order is processed. The staging area is the supply subinventory
and locator (if applicable). The staging area can be considered as a
temporary location where you are gathering materials for use in work
orders. The staging area is defined in the following location :
Bill of Materials Form> Material Control Tab. Enter Supply Subinventory
field and locator. (If you have set the profile BOM: Default WIP Supply
Values for Components to Yes, these values default from the item
master)
If this information is not defined, the default values are taken from the
WIP Parameters form.
7. Push components supply subinventory. The following important points
should be noted about push components :
Push Components are AUTOMATICALLY supplied directly to the
job or schedule when component pick release is run and
therefore do not need the staging information.
BUT if you do NOT want push components to be supplied directly
to the job or schedule, then you need to define the supply
subinventory/locator staging area as for pull components. These
components will then be treated in the same way as pull
components. This means that the push components will need to
be manually processed via the move order and will end up in the
staging area and not the job/schedule.
8. Link the supply subinventory and locator to a machine resource. Linking
this subinventory to a resource enables backflush components required
on operations to have the specified subinventory as their supply
subinventory. This setup is defined in the following place :
Bill of Materials > Resources. Enter Supply Subinventory field and locator
(if appropriate). This is only valid for machine resources.
9. Define the Inventory Picking Rule. The inventory picking rule will be used
to define the criteria for sorting the picks for the work orders/schedules
selected during component pick release. It is the criteria used for
allocating the material.

The default picking rule for the organization is set on the Organization
Setup screen (ATP, Pick, Item-Sourcing tab > Pick defaults region > Rule.
Enter the inventory picking rule here).

The picking rule is defined using the Inventory Picking Rule Window in
the Inventory responsibility.
For component pick release the Applicable to restriction field is set to
Work in Process.
If the single lot allocation flag is checked, only a single lot is allocated for
this rule the flag decides if multiple lots are allowed.
The Partial lot allocation flag controls whether the system can allocate
quantities of a lot which are less than the total lot quantity available if it
is not checked, then the rule allocates the whole lot quantity.
The customer spec match flag is checked if the rule requires quality
specification matching.
The sort criteria can be selected and ranked and include : Lot, revision,
subinventory and locator. The sort criteria are used to decide THE ORDER
in which lots, revisions, subinventories and locators are picked for the
work orders in component pick release.
The rule in the above window will work as follows :
It will look at lots first as this is rank 1. It will select lots using FIFO
(first in first out). The other lot criteria that are available to use
apart from FIFO are : a. FEFO (first expired, first out), b. Lot no
asc (ascending lot number), c. Lot no desc (descending lot num).
It will then look at revision rank 2. It will sort based on the
revision effective date in descending order. The other revision
criteria are : a. revision effective date in descending order, b.
revision in ascending order, c. revision in descending order.
Next is subinventory rank 3. It will sort based on the
subinventory receipt date in ascending order. The other
subinventory criteria are : a. subinventory receipt date in
4

descending order, b. subinventory picking order flag ascending


order, c. subinventory picking order flag descending order.
Final sort criteria is locator rank 4. It will sort based on the
locator receipt date in ascending order. The other locator criteria
are : a. locator receipt date in descending order, b. locator in
ascending order, c. locator in descending order.
Once the rule is defined, it is assigned using the assignments window (by
selecting the assignment button on the inventory picking rules window).

The assignment window can be used to assign multiple picking rules. The
sequence number, return type, return values type and org are defaulted
(the sequence number can be subsequently changed to change the
sequence in which the rule is executed). The rule is assigned using the
following criteria :

Customer
Item
Item Category
Item Type
Assignment Group
Source Subinventory
Supplier
Order Type
Freight Code
Project
Task
Transaction Action
Destination Subinventory
Transaction Reason
Transaction Source
Transaction Type
UOM Class
Date Type
Date From
Date To
5

For example, if you create a picking rule that allocates material by lot number
in ascending order followed by locator in ascending order, you can assign it to
a particular item in the Rules Workbench. This means for picking, the system
allocates the lowest lot number of the item in the lowest locator number
where the item resides. Another example - if you created a rule that
allocates lots based on FIFO and assign the rule to a particular customer
the material you pick for that customer is allocated based on FIFO. It should
be noted that the assignments window shown above in not available in
release 11i it is a release 12 feature.
10. Define the Pick Slip Grouping Rules. Grouping rules allow you to specify
the criteria by which released picking lines are grouped on the pick slip.
You can select from the following criteria: order number, carrier,
subinventory, shipment priority, customer, departure, ship to, and
delivery. If you select subinventory, for example, all picking lines with the
same subinventory are grouped on the same pick slip. If you pick Carrier
and Customer, all picking lines with the same freight carrier and
customer are grouped on the same pick slip.
Pick Slip Grouping rules are defined from the Pick Slip Grouping Rules
window in Order Management.
11. If Warehouse Management is installed, you can define Rules Based
Picking criteria. Rules based picking uses the Warehouse Management
Rules engine. This employs user defined rules to recommend locations to
pick from, and specific items to pick.
The WMS Rules window is shown below.

4. STEP BY STEP PROCESSING OF COMPONENT PICK RELEASE :


In this section, each stage of the component pick release will be discussed in
detail. The assumption for this section is that all required setups have been
done.
A. STEP 1 : ELIGIBILITY CRITERIA
The first thing to establish before running component release is to
understand the criteria required for jobs and schedules to be picked up
by component pick release :
DISCRETE JOBS : Discrete jobs will be available for selection by
component pick release only if the following criteria are met :

The status must be Released or Complete Charges Allowed.


There is an operation on the job which has material on it.
The operation against which the material is defined has the
autocharge option on.
The materials on the job are transactable (inventory item attribute).

LOT BASED JOBS : The following criteria must be met :


The job Status must be Released or Complete - Charges Allowed
Components are picked based on the network routing for the assembly
The materials on the job are transactable (inventory item attribute).
FLOW SCHEDULES : The following criteria must be met :
Material must be defined at a valid line operation. In flow schedules,
material and resources are specified in the events associated with the
line operation. If components are not assigned to specific events, or
events are not assigned to line operations - the value in the Line
Operation field is 1. This value indicates an unassigned line operation for
that material requirement.
The status must be open.
The materials are transactable (inventory item attribute).
Components must be a supply type of Push
ALL the components for the flow schedule need to be available
otherwise move orders will not be generated.
REPETITIVE SCHEDULES : The following criteria must be met :
Status must be Released or Complete - Charges Allowed
Material is defined at the operation and autocharge is enabled
The materials are transactable (inventory item attribute).
7

B. STEP 2: THE FIND WINDOW /OPERATING MODES


We have now established the setup requirements and we know the
requirements for jobs and schedules to be considered for component
pick release. We will now look at how to use the Component Pick Release
Form. The first aspect of this form is the Find Window.
The first thing to understand about the Component Pick Release Form is
that it will present FOUR different find windows and four different
summary screens (the main screen showing the results of the search).
This depends on the application being used and the type of job or
schedule being used. The underlying form used is the same in all four
cases the form is called WIPCMPPK. The search and summary fields for
the form are displayed appropriate to the application/type of job or
schedule.
Let us look at these 4 search screens :
1. Discrete Jobs :
Navigation : Work in Process>Discrete>Component
Release>Component Pick Release (Form)

Pick

Key Points :

If Project Manufacturing is used, you can search by Project


Number/Task Number.
There is a very useful facility to search by a single operation
or a range of operations in one job or a range of jobs. This is
crucial in environments where operation start times are
unpredictable.
The Material Requirement Date searches for dates based on
the dates entered on the Material Requirements window for
the discrete job (so if there were material requirements for
March but you entered a February date in the above search
criteria, then the March material requirements would be
ignored). Material requirements and lead times should be
considered when using this date.
8

When the find button is clicked, the main summary screen is


returned based on the selected criteria. The summary screen
is configured to display fields which are appropriate to
discrete jobs.

2. Lot Based Jobs :


Navigation : Shop Floor Manager>Lot Transactions>Component Pick
Release

Key Points :

You can search by job, assembly, schedule group and


production line.
The Material Requirement Cutoff Date works in the same
way as the Material Requirement Date for discrete jobs.
When the find button is clicked, the main summary screen is
returned based on the selected criteria. The summary screen
is configured to display fields which are appropriate to lot
based jobs.
Move order quantities are calculated as assemblies per
operation x components per assembly, or the sum of all the
quantities in each intraoperation step (Queue, Run, To Move,
Reject and Scrap) x the component's quantity per assembly.

3. Repetitive Schedules :
Navigation : Work in Process>Repetitive>Component
Release>Component Pick Release (Form)

Pick

Key Points :

You can search by assembly and production line.


The Material Requirement Cutoff Date works in the same
way as the Material Requirement Date for discrete jobs.
The Days of Supply value is multiplied by the daily production
rate and component quantity per assembly to calculate the
pick quantity. If the open quantity is less than the value
entered here, the open quantity is used instead.
When the find button is clicked, the main summary screen is
returned based on the selected criteria. The summary screen
is configured to display fields which are appropriate to
repetitive schedules.

4. Flow Schedules :
Navigation : Flow Manufacturing>Production>Component Pick
Release>Component Pick Release (Form)

Key Points :

You can search by flow line, schedule group, build


sequence,and sales order.
If Project Manufacturing is used, you can search by Project
Number/Task Number.
When the find button is clicked, the main summary screen is
returned based on the selected criteria. The summary screen
is configured to display fields which are appropriate to flow
schedules.

There are two operating modes in which Component Pick Release works
based on the four different combinations of application/type of job or
schedule that we have seen in this step :
Discrete Manufacturing Mode (The Discrete Job, Repetetive
Schedule, Lot Based Jobs - operate in this mode)
10

Flow Manufacturing Mode (The Flow Schedule operates in this


mode)

C. STEP 3: THE SUMMARY SCREEN AND DETAIL SCREEN :


We have now established that the Component Pick Release form shows a
different find window and summary window based on the
application/type of job or schedule. We have also established that there
are two operating modes for component pick release.
Next we will look at the summary screen itself and also look at the detail
screens. We will focus on Discrete Jobs only and will highlight any
operational differences for the other types of job/schedule.
1. Summary Screen : (using Discrete Job example) :
Once the search criteria are entered on the Component Pick Release
form (for Discrete Jobs), the following summary screen is shown :

Note the Two Pane Layout. The left pane is the navigation
tree showing the records which meet the criteria on the find
window. The right pane shows the fields for the hierarchy
selected.
As previously mentioned, the summary screen will be
formatted dependent on the type of job/schedule and the
application. We are looking at discrete jobs.

2. Detail screen : At the Job Level :


If a particular job is selected from the tree, then the right hand will
now show the detail screen for the job :

11

3. Detail screen : At the Component Level :


If a particular component is selected from the tree, the detail screen
for the component is shown :

Important point : Selecting the release button from the detail screen
will NOT release JUST the selected component. The release button
releases the components selected on the summary screen whether it
is pressed from the summary screen or the detail screen.
D. STEP 4: RELEASING COMPONENTS FOR PICK RELEASE AND WHAT
HAPPENS AS A RESULT:
We will now discuss how the component pick release form is used to
actually release the components for picking. For this, let us refer once
more to the summary form :

12

The component pick release form is used to pick release the components
for the selected jobs. Here is how the options on the form work :

The Include (include in release) check box defaults as


checked for all the records in the tree. Uncheck records you
do not want to release. Or clear a record from the Edit menu
(Highlight a record. Then select Edit from the menubar >
clear - this removes the record from the tree).

If the Pickset checkbox is selected, then ALL of the


components have to be available for the job. If there is
insufficient quantity for ANY component on that job, then
NONE of the components for that job are pick released. The
Pickset check box is in both the summary and detail
windows.

The Pickset checkbox can ONLY be selected in Discrete


Manufacturing mode. For the Flow manufacturing mode, this
feature is always enforced and is not displayed,

The Select All For Pickset box enables you to select, or


deselect all the Pickset checkboxes for the hierarchy.

The Pick Slip Grouping Rule can either be manually entered


or can default from the WIP Parameters window for the
current organization. It is used to group picking lines based
on the criteria selected on the rule. For example, if you select
a rule which uses subinventory as a criteria then all the
picking lines with the same subinventory will be on the SAME
pick-slip. Rules are defined on the Pick Slip Grouping Rules
window in Oracle Inventory.

The Print Pick Slips box is used to enable or disable the


printing of the Move Order Pick Slip Report as part of the
13

current component pick release.

The Plan Tasks checkbox defaults from the current


organizations WIP Parameters or can be changed. This
checkbox is only applicable for
Oracle Warehouse
Management enabled organizations. (tasks are similar to
move order lines)
o

If this check box is enabled, the system creates pick


tasks in an Unreleased status. This option is used if
you want to create the allocations, but postpone the
dispatching. The task can be released when you are
ready to dispatch.
If this check box is not checked, tasks are created in a
Pending status and are immediately eligible for
dispatching.

Select Release to release the components for pick


release.The release button is available on both the summary
and detail windows (it will release the same components
from both windows) .

Now lets consider the following question - What happens when the
release button is clicked in Component Pick Release?
A MOVE ORDER is created for the components that are released. As
a result of the move order, the components are ALLOCATED to the
job. Let us briefly look at the definition of move orders and
allocations before we proceed further :
Move Orders : A Move order is simply a request for the movement of
material within a single organization. A move order is made up of a
header and multiple move order lines. Each line is a single request for
the movement of material (separate line for each material).
Normally, a move order goes through 3 stages after it is created :
stage 1: approval of the move order, stage 2: allocation of the
materials on the move order, stage 3: transacting the move order to
actually move the requested materials.
Allocations : An allocation is a soft reservation it is simply a
suggestion by the system that the component is available and the
source where it is available from. Move orders use Inventory picking
rules to suggest source location, lot numbers, and revisions for the
material to be picked. The allocating process fills in the move order
line details with the actual transactions to be performed and allocates
the material to the move order.
14

We will now go back to the move order created as a result of


releasing from Component Pick Release bearing in mind the above
definitions. The following points should be noted :

The move order type created from component pick release is


called Manufacturing Component Pick.

The move order created as a result of component pick


release is already approved so does not require the approval
process. The line status is pre-approved.
The move orders populates the mtl_txn_request_headers
and mtl_txn_request_lines tables :

mtl_txn_request_headers
the header details

mtl_txn_request_lines containing the


move order lines

- containing

The move order created as a result of component pick


release has already created the allocation lines based on the
inventory picking rule i.e the move orders created from
component pick release are auto-allocated. So there is no
manual allocation required. However, the allocations can be
updated from the following navigation :
Inventory>Move Orders>Transact Move Orders
Query the move order. Select the move order line. Then click
the View/Update Allocations button to view or amend the
allocations.
This over issuing of allocated move order quantities is an
important feature to understand. In some situations,
material may not be able to be split as assigned by the
allocation (because of boxed quantity, pallet quantity etc).
The move order functionality , therefore, allows for these
allocated quantities to be changed accordingly.

The outcome of the allocations is as follows :


1. A pending transaction is created. This is created in the
Mtl_Material_transactions_temp table (MMTT) and it
represents the allocation. This pending transaction will
15

be executed once you transact the move order.


2. The available quantity for the material is decremented.

Backordering : If the pick-set checkbox is not selected for a job, then


components which are available for a job will be released. If a
component was NOT available or PARTIALLY available, the system
will backorder the unavailable quantity :

If none of the quantity was available, the whole quantity


would be backordered and a message would be displayed
specifying this action.
For partial allocations, the backordered quantity can be seen
in the component detail window.
Backorders are not generated for flow schedules because all
the components have to be available for flow schedules
otherwise no move orders are generated.
If you are using Rules Based Picking in WMS, and the
warehouse is enabled for cross docking, the WMS Rules
engine checks for backorders and creates move orders to put
material directly into the staging area.

E. STEP 6: TRANSACTING THE MOVE ORDER :


The next step involves transacting the move order. This simply means
that the material is actually moved to the specified location.
It is done as follows :
Inventory>Move Orders>Transact Move Orders
Query the move order. Select the move order line. Then click the
Transact button to transact the lines.
The following happens when the move order is transacted :
Pull components are moved to the specified staging area
Push components are moved either directly to the
job/schedule automatically (if the staging fields are left blank
on the BOM) OR they are moved to a specified staging area if
this was defined on the BOM.
A transaction is created in the history table,
MTL_MATERIAL_TRANSACTIONS
(and
the
pending
transaction from the MMTT table is removed).
Please note the following :
You cannot cancel a move order line you can cancel it. The move
order line that is backordered goes into status 5 / closed and the
16

pending transactions related to the allocated quantity in the table,


MTL_MATERIAL_TRANSACTIONS_TEMP, are removed. Then you can
amend the work order quantity to reflect the change in requirement.
Note: If the organization is enabled for Oracle Warehouse Management, then
move orders cannot be transacted on the desktop Transact Move Orders
form. Rather, the move orders are transacted as tasks on mobile devices.
However, the Transact Move Order from can be used to view the allocations,
so long as LPNs have not been allocated. The allocations can still be manually
updated from this form, but the Transact button is not available for
move orders in a WMS enabled organization.
F. STEP 7: ISSUING THE REMAINING MATERIAL :
The last step involves issuing the material to the job/schedule. Push
components will not require this step if no staging area was defined for the
component on the BOM they will be automatically issued to the
job/schedule when the move order is transacted.
The pull components are usually automatically backflushed when move and
complete transactions take place. Pull components are backflushed when :

Completing assemblies at operations using the Move Transactions


window
Moving and completing assemblies into inventory using the Move
Transactions window

This is now the end of the business process.


5. EXAMPLE DEMONSTRATION OF COMPONENT PICK RELEASE:
In the above section, we discussed in detail each step of the component
pick release process. We will now illustrate all of the steps discussed
above using an actual example :
STAGE 1 : BASIC SETUPS AND ELIGIBILITY :

The Release Backflush Components Wip Parameter has been checked


so pull components will be picked.
The inventory picking rule has been defined and is a simple one it
will pick items based on ascending subinventory order (by looking at
the picking order field on the appropriate source subinventories
where the stock is held).
The BOM for the assembly is shown below :

17

The quantities required for each of these components is 1. Note that the
push component (ZA-Component-4) does not have a supply subinventory
specified. This means that it will be supplied directly to the job and not to a
staging area when component pick release is run.

Here are the current quantity details for the components before
component pick release is run (from the inventory on hand screen):

Name
Za-Component-4
Za-Component-5
Za-Component-6

On-Hand
25
35
5

Avail-To-Reserve Avail-to-Transact
25
25
35
35
10
10

STAGE 2 : RAISE DISCRETE JOB :


A discrete job is now raised. The details are shown below :
Navigation : WIP> Discrete> Discrete Jobs

The discrete job is in a released status and has an operation with transactable
materials against it therefore it is eligible for component pick release.

18

STAGE 3 : USE FIND WINDOW TO QUERY DISCRETE JOB :


We are discussing the find window. In our example, we are using the find
window to search for the job we created specifically :
Navigation : WIP> Discrete>Component Pick Release> Component Pick
Release (Form)

STAGE 4 : COMPONENT PICK RELEASE - SUMMARY AND DETAIL SCREEN :


Now lets look at the summary and detail windows to illustrate the step we
are currently discussing :
Navigation : WIP> Discrete>Component Pick Release> Component Pick
Release (Form)
The summary screen shows a line summary of the main fields for the discrete
job. Since we selected one job, only line shows on the summary screen (the
summary window screenshot can be seen in the next stage example 5).
The screenshot below is showing the detail window for our discrete job
ZA605

19

If we select a component, the detail window is displayed for the component as


shown below :

STAGE 5 : RELEASING THE COMPONENTS


The Release button has been clicked on the summary window. Note the
dialogue box which gives the details of the move order and pick slip report.

So as a result of Component Pick Release running for the job, the following
has happened :

The pick slip has been printed for the picked components because we
selected the option to print pick slips. This will list the components
that have selected for picking.
A Move order has been generated. This will be in an approved state
and will already have allocated the components that have been
picked i.e it is auto-allocated.
Note that the pick set option was not selected this means that any
unavailable component quantities will have been backordered. It will
allow the release of components that are available for the job.
The move orders populates the mtl_txn_request_headers table
(move order header details)
and mtl_txn_request_lines table
(allocated move order lines).
20

A pending transaction will be created in the MMTT


(mtl_material_transactions_temp) table for each component.
Here is a useful query linking the move order to the MMTT table :
SELECT mmtt.transaction_temp_id,
tol.organization_id,
toh.request_number,
toh.header_id,
tol.line_number,
tol.line_id,
tol.inventory_item_id,
toh.description,
toh.move_order_type,
tol.line_status,
tol.quantity,
tol.quantity_delivered,
tol.quantity_detailed
FROM mtl_txn_request_headers toh,
mtl_txn_request_lines tol,
mtl_material_transactions_temp mmtt
WHERE toh.header_id = tol.header_id
AND toh.organization_id = tol.organization_id
AND tol.line_id = mmtt.move_order_line_id
AND toh.request_number = '&EnterMOnumber'
/
The move order table (MTL_TXN_REQUEST_LINES) provides the status of the
move order in the LINE_STATUS column as a numeric. The following lists the
various statuses :
1 Incomplete
2 Pending Approval
3 Approved
4 Not Approved
5 Closed
6 Canceled
7 Pre Approved
8 Partially Approved
9 Canceled by Source

As a result of the allocated material, the component quantities now


show as follows : (15 of each are required for the job). Note that the
available-to-reserve and available-to-transact values have been
decremented. The on-hand values are untouched at this stage.
Name
On-Hand
Za-Component-4 25
Za-Component-5 35
Za-Component-6
5

Avail-To-Reserve Avail-to-Transact
10
10
20
20
0
0

In the above example, the system did a PARTIAL ALLOCATION for ZAComponent-6 and backordered the quantity that is not available. A
quantity of 15 was required for each component. Since only 10 of ZAComponent-6 were available to transact, the remaining 5 have been
21

backordered.
STAGE 6 : TRANSACTING THE MOVE ORDER
Now lets illustrate the transaction of the move order :

To transact the move order, the lines are selected as above and the transact
button clicked. This then results is a message saying that the transactions
have been completed.

Note that the transaction type for the push component is Wip
Component Issue. This is because no staging details were entered.
This means the components are issued directly to the job.
The pull components have a transaction type of Backflush Transfer.
The pending transaction in the MMTT table is processed and deleted
and
a
record
is
created
in
the
MMT
table
(mtl_material_transactions).
The move order header and line records are updated to reflect the
transactions.
Here is a useful query which links the move order to the MMT table :
SELECT mmt.transaction_id,
tol.organization_id,
toh.request_number,
toh.header_id,
tol.line_number,
tol.line_id,
tol.inventory_item_id,
toh.description,
toh.move_order_type,
tol.line_status,
tol.quantity,
tol.quantity_delivered,
tol.quantity_detailed
FROM mtl_txn_request_headers toh,
mtl_txn_request_lines tol,
mtl_material_transactions mmt
WHERE toh.header_id = tol.header_id
AND toh.organization_id = tol.organization_id

22

AND tol.line_id = mmt.move_order_line_id


AND toh.request_number = '&EnterMOnumber'
/

The on hand quantities (in on hand inventory screen) now show as


follows at this stage :

Name
Za-Component-4
Za-Component-5
Za-Component-6

On-Hand
10
35
5

Avail-To-Reserve Avail-to-Transact
10
10
20
35
0
5

The actual on-hand quantity for the push component (ZA-Component-4) has
been reduced because the component has been actually issued to the job.
The two pull components have simply been transferred to a staging
subinventory so the actual on-hand is not reduced. As a result, the
Available-to-Transact value has been increased to reflect the fact that the
components in the staging area can be issued.
STAGE 7 : BACKFLUSH OF REMAINING COMPONENTS
Now lets illustrate the backflush of the pull components.
The only components left to issue are ZA-Component-5 and ZA-Component6. These are pull components. The push component has already been issued
to the job.
Here is the current state of the discrete job
components have not yet been issued:

which shows the pull

A completion transaction is now done to complete some assemblies for the


job :

23

This will result in the backflush of the pull components. The discrete job will
now have all the components issued. A record will be created in the MMT
table for each backflushed component.

The on hand quantities (in on hand inventory screen) now show as follows
now:
Name
Za-Component-4
Za-Component-5
Za-Component-6

On-Hand
10
20
-10

Avail-To-Reserve Avail-to-Transact
10
10
20
20
0
-10

The on-hand and available to transact quantities for the pull components are
updated as above.
This concludes our example and the end of the scenario.

24

6. WHAT HAPPENS IF I RUN COMPONENT PICK RELEASE AGAIN FOR THE


SAME JOB OR SCHEDULE ?
The following should be noted :
If you re-run Component Pick Release for a discrete job, lot based
job or repetitive schedule, only OPEN requirements, backordered
quantities or new requirements are considered. The system will
not look at components already released.
You can run component pick release for flow schedules as many
times as required until all the quantities for the flow schedule are
available. Flow schedules which have had their components
released are not then re-considered if component pick release is
run again.
7. WHAT HAPPENS WHEN A JOB OR SCHEDULE IS CANCELLED?
If a job or schedule is cancelled, all untransacted tasks and move orders
associated with those work orders are also cancelled. An API,
WIP_PICKING_PVT.CANCEL_ALLOCATIONS, is used to select all open move
orders to update their allocated and backflushed quantities. This procedure
calls the INV_MO_Cancel_PVT.Cancel_Move_Order_Line procedure to cancel
the corresponding move order lines. Material requirements and move orders
are synchronized to account for move order line cancellations.
8. COMPONENT PICK RELEASE CONCURRENT PROGRAM :
Component Pick Release can also be run using a concurrent request rather
then a form. The advantage of this option is that it can be scheduled to run
automatically at specific times/periods.
There are three different concurrent programs for Component Pick release
depending on the application/type of job/schedule. There is NO concurrent
program for Flow Schedules. The available programs are :
Discrete Job Component Pick Release (SRS)
Repetitive Schedule Component Pick Release (SRS)
Lot Based Job Component Pick Release (SRS)

25

The above screenshot shows the Discrete Job Component Pick Release (SRS).
The parameters shown above also apply if Lot Based Component Pick Release
(SRS) is run.
If Repetitive Schedule Component Pick Release (SRS) is run, then Days of
Supply is one of the parameters required (as well as the ones shown for
Discrete jobs above).
Note the following :

Days Forward Parameter : The number of days forward that the


system will look at to consider requirements. So if you enter a value
of 2, then any materials required in 3 days times will be ignored.
Pick Slip Grouping, Print Pickslips, Pick Tasks : these parameters work
as in the forms (see section 4, Step D above).
The Days of Supply parameter is used for repetitive schedules only.
The value is multiplied by the daily production rate and component
quantity per assembly to calculate the pick quantity.
Clicking Submit will pick release the components in the same way as
the release button in forms. If any components fail, the program will
still run for other components and end in a warning. Failed
components will be displayed in the request output.
Customers have sometimes asked why the Pickset parameter is not
available on the concurrent program.
The answer is that this is a hidden parameter. It can be made
available as follows :
Go to System Administrator>Concurrent>Program>Define
Query Back : Discrete Job Component Pick Release (SRS)
Click parameters button
p_use_pickset_indicator

and

select

Click the display flag to display the parameter.


26

the

parameter

Job Type :
The SRS concurrent program has a parameter to allow the user to
select the job types (non-standard jobs, standard jobs, all jobs).
Sometimes, this is not visible it is hidden. To enable it :
Go to System Administrator>Concurrent>Program>Define
Query Back : Discrete Job Component Pick Release (SRS)
Click parameters button and select the parameter : p_job_type
Click the display flag to display the parameter.

9. THE ADVANTAGES OF COMPONENT PICK RELEASE :


It is relevant to ask at this stage : Why do we need to run component pick
release? What are the options if we dont run it? What advantages does it
offer?
Lets now answer these questions.
First of all, it is important to understand that using component pick release in
your business process for issuing materials to jobs and schedules is NOT
mandatory. If you did not use Component Pick Release, then components can
be issued manually to jobs/schedules (for example - using the Wip Material
Transactions window transaction type of wip component issue or via onestep issue option for EAM jobs). Both push and pull components can be
issued in this way. However, usually, only push components would be issued
manually - Pull components are normally backflushed in the way already
discussed (as a result of move/completion transactions).
So why run component pick release? Here are the advantages it offers :

Allows for a controlled approach to issuing materials to


jobs/schedules.
You can select and prioritise which jobs/schedules are to be pick
released.
Reduces the possibility of components not being available for jobs
because you are carrying out a planned release of components
rather then multiple ad-hoc component issue transactions. The adhoc approach would allow users to issue materials to specific jobs
(some of which may be of lower priority).
Importantly, component pick release imposes control regarding
where the material is to be sourced from (by using inventory picking
rules). Manual transactions would allow the material to be picked
from different sources.
27

10. WHICH API CAN BE USED TO CREATE A COMPONENT PICK RELEASE?


There is an API which can be used to mimic component pick release and
create the move orders for jobs/schedules. The API is called :
wip_picking_pub.allocate.
Here is some sample code which can be used to create the move orders :
DECLARE
p_alloc_tbl1 wip_picking_pub.allocate_tbl_t;
l_conc_req_id NUMBER;
l_mo_req_number VARCHAR2(1000);
l_return_status VARCHAR2(1000);
l_msg_data VARCHAR2(1000);
i number:=0;
CURSOR c_mypickrelease(v_myrid NUMBER)
IS
SELECT
we.wip_entity_id g_wid
FROM
wip.wip_entities we
WHERE
we.wip_entity_name=TO_CHAR(v_myrid);
BEGIN
i:=0;
FOR f_wipcmppk IN c_mypickrelease(702)
LOOP
i:= i+1;
p_alloc_tbl1(i).wip_entity_id := f_wipcmppk.g_wid;
p_alloc_tbl1(i).repetitive_schedule_id := NULL;
p_alloc_tbl1(i).use_pickset_flag := 'Y';
p_alloc_tbl1(i).project_id := NULL;
p_alloc_tbl1(i).task_id := NULL;
p_alloc_tbl1(i).bill_seq_id := NULL;
p_alloc_tbl1(i).bill_org_id := NULL;
p_alloc_tbl1(i).required_date := SYSDATE;
p_alloc_tbl1(i).alt_rtg_dsg := NULL;
END LOOP;
DBMS_OUTPUT.PUT_LINE(p_alloc_tbl1(i).wip_entity_id);
wip_picking_pub.allocate
(p_alloc_tbl => p_alloc_tbl1,
p_days_to_alloc => NULL,
p_auto_detail_flag => 'T',
p_start_date => TRUNC(SYSDATE-1),
p_cutoff_date => TRUNC(SYSDATE+1),
p_operation_seq_num_low => NULL,
p_operation_seq_num_high => NULL,
p_wip_entity_type => 1,
p_organization_id => 104,
p_pick_grouping_rule_id => 1050,
p_print_pick_slip => 'F',
p_plan_tasks => NULL,
x_conc_req_id => l_conc_req_id,
x_mo_req_number => l_mo_req_number,
x_return_status => l_return_status,
x_msg_data => l_msg_data);
dbms_output.put_line('PICK RELEASE REQ ID: '||l_conc_req_id);

28

IF (l_return_status = fnd_api.g_ret_sts_success) THEN


dbms_output.put_line('Success- '||l_msg_data);
dbms_output.put_line('Success- '||l_mo_req_number);
ELSE
dbms_output.put_line('Not Success- '||l_msg_data);
dbms_output.put_line('Success- '||l_mo_req_number);
END IF;
END;

11. DEBUGGING COMPONENT PICK RELEASE


For debugging Component Pick Release in R12 and higher, use the FND
Debug settings as follows:
a. Using System Administrator responsibility, set profile options at the user
level:
FND: Debug Log Enabled : Yes
FND: Debug Log Filename : leave it as null
FND: Debug Log Level : Statement
FND: Debug Log Module : wip%
INV: Debug Trace = Yes
INV: Debug Level = 11
INV: Debug File = /tmp/invdbg.db
* Use a "valid directory from v$parameter" and filename.
select value from v$parameter where name=utl_file_dir;
b. Check the maximum log sequence from fnd_log_messages executing:
SQL> select max(log_sequence) from fnd_log_messages;
c. Reproduce the issue
d. Retrieve the log messages executing the below statement. Upload the
results in a spreadsheet format.
* Replace max_log_sequence with the result from previous sql in step2
SQL> select * from fnd_log_messages where log_sequence >
&max_log_sequence;
e. Also retrieve the inventory debug log file (/tmp/invdbg.db in the example).
Trace Settings :
Enable trace to track the Component Pick Release down to the SQL calls.
Open the component pick release form. Enable Trace using Toolbar Menu:
Help > Diagnostic > Trace > Trace with Binds
This will give a note saying You have enabled SQL tracing for this form. Note
the trace file name (including complete location) so you can retrieve the
trace file later.

29

12. DIFFERENCES BETWEEN R11 AND R12 FUNCTIONALITY FOR COMPONENT


PICK RELEASE :
In this section, the differences between the component pick release
functionality in release 11 and release 12 will be briefly discussed :

Inventory picking rule enhancement access has been provide to a


striped down version of the WMS rules workbench in order to allow
the assignment of picking rules to objects. In release 11, this rules
workbench is not available for the inventory picking rule.

New Objects and Parameters have been added to the WMS Rules
workbench to allows WMS users to define picking rules that replicate
those supported in process manufacturing environments.

Refer to the functionality provided in R12 that is mentioned in


sections 13 and 14. These are both specific to R12 and not available
in 11i.

13. IMPORTANT NEW FUNCTIONALITY AVAILABILITY IN 12.1.3 : EAM Work


Orders Component Pick Release Concurrent program :
The next 2 sections (13 and 14) were added to the white paper due to new
functionalities being made available in 12.1.3. These sections describe the
new functionalities.
Firstly, to provide the ability of performing material allocation for a group of
work orders with open material requirements, a new concurrent program
'EAM Work orders Component Pick Release' was provided in 12.1.3.
This new functionality is available on top of release 12.1.3, by application of
Patch 14271223:R12.EAM.B.
Patch 13608137 will add the new concurrent program 'EAM Work orders
Component Pick Release' to the EAM menu.
The request can be launched from the menu path:
Enterprise Asset Management -> Work Orders -> Work Order Component Pick
Release
Using the concurrent request , the material allocation can be done for work
orders in statuses Released with open material requirements :
Required qty > Issued +Allocated qty
30

Selecting Work order material requirements for material allocation


The concurrent request will select material requirements from work orders
that meet the following criteria:
Work order is in status 'Released' (includes user-defined Released
status also)
-

Enable Material Issue Requests is set to 'Yes' for the work order

Select material requirements if there is Open Quantity (Required


quantity > Issued + Allocated Quantity)
Select material requirement lines from work orders that have Auto
Request Material Yes (Excludes the Auto Request Material No lines)
The following list of parameters will be provided to select work orders for
performing the allocation for their material requirements :

Paramet
er

Type

Default Value

Field / LOV

To enter Number of days

Mandatory
Days
Forward
Pick slip Mandatory
groupin
g rule

Print
Pick
slips

Optional

Default rule specified Pickslip grouping rules LOV (PICK_SLIP_RULES in


in WIP parameters
WSH_PICK_GROUPING_RULES)
(PICKSLIP_GROUPING_
RULE_NAME in
WIP_PARAMETERS_V)
Yes

LOV values Yes and No

*Days forward : The number of days in to future to consider material


requirements for the pick release
For Example: If the 'Days forward' is entered as 3,then the program selects
WO material lines whose 'Date Required' is less than or equal to 'sys date +
3'

31

Using this concurrent program EAM users will be able to perform material
allocation for work orders that were released earlier with insufficient onhand material and now have sufficient on-hand for the material allocation.

14. NEW R12 FUNCTIONALITY FOR SERIALISED JOBS FOR COMPONENTS


WITH NO SUBINVENTORY DEFINED
A patch was released in R12 (for 12.1.X), that changes the way component
pick release for serialised jobs when components dont have a subinventory
defined.
The required patch for this functionality is 14050050:R12.WIP.B.
Prior to this patch, Push type components without subinventory defined
were issued to the job directly after component pick release even for
serialized job and serialized operations.
The patch provides the following new behavior :
Push type component without subinventory defined for serialized jobs and
serialized operations , will be excluded from component pick release to avoid
them being issued to the job without assembly serial number.
What does this mean?
If a push requirement is at an operation before the start serialization
operation of a serial tracked job, Component Pick Release will pick it, as
before
If a push requirement is at or after the start serialization operation of a serial
tracked job , Pick Release will ignore it - unless it has a Supply Subinventory
(non-reservable)/locator , in which case it will pick it for a 'Backflush Transfer'.
This makes sense - the Storeman at the time of picking will not know which
serial number component will be used on which serial number assembly; the
operator will be the person who knows that and so will have to do the WIP
issue from the supply subinv/locator to the assembly serial number.

32

15. COMMON ISSUES/ERRORS IN COMPONENT PICK RELEASE


In this section, the common issues seen in component pick release will be
discussed. To allow the reader to quickly see if a specific issue is discussed, I
will first of all list all the issues that are considered in the section these will
then be explained in the detail :
Questions :
1. While Performing Component Pick Release the Following Error Message
Occurs "None of the material requirements for the selected components
could be allocated..."
2. When running component pick release, only push components are picked.
Assemby Pull and Operation Pull components are being ignored.
3. Push Components are not being issued directly to the job or schedule.
They are being moved to a staging subinventory.
4. Cannot Cancel or Close Move Order Lines For Component Pick Release.
5. When run Component Pick release for a flow schedule get message:
"None of the Material Requirements for the selected components could be
allocated. Please re-query to view the open requirements" (for release 12
and later)
6. Get the following error when running component pick release : Error in
component pick release. Job/schedule number XXX has a reservable supply
subinventory
(XXX) for component XXXXXXXX.
7. Component Pick Release does not select the source subinventory defined
for the particular subinventory in the subinventory summary window
8. Get the following error when running component pick release :
Job/schedule number <> has a reservable supply subiventory (<>) for
component <>
9. When releasing a WIP component pick release the system creates move
order headers with no associated move order lines.
10. Why isn't the Component Pick Release (SRS) program releasing all eligible
jobs?

33

11. Component Pick Release Form Gives WIP_PICKING_NO_JOBS Error When


Querying for Released Jobs (release 11 error).
12. Can Not Do Component Pick Release Across Tasks On The Same Project.
13. Component Pick Release Generates Move Order for an Item with Two
Different Revisions - Is Also Considering Older Revision
14. Component Pick Release Not Creating Tasks For Correct Qty (release 12.1
and later)
15. WIP Component Issue Stuck In Pending Transactions (release 11i)
16. Cannot over-pick for the move order created from component pick
release why is this?
17. Kanban Items are released via Component Pick Release. How do we stop
this?
18. Cannot run component pick release (SRS) concurrent program to pick
release by operation.
19. How to Customize the Pick Slip Report on Print Pick Slip Button On
Transact Move Order Line Allocations Form ?
20. The component pick release (SRS) concurrent program is not showing the
parameter to select by pickset this is available in the forms (apart from flow
manufacturing).
21. The discrete job component pick release (SRS) concurrent program is not
showing the parameter to select by job type (standard jobs, non-standard
jobs).
22. Why cant we make the supply subinventory reservable?
23. The system cannot allocate from source subinventories which are
reservable.
24. Component pick release is not releasing items even though stock is
available. Why ?
25.Why cant bulk items be automatically issued to WIP jobs using
component pick release?
26. Cannot find a certain job or schedule from the component pick release
find window.
34

27. The system is not allowing the creation of a rule which picks a particular
item from a particular source subinventory only.
Answers :
1. While Performing Component Pick Release the Following Error Message
Occurs "None of the material requirements for the selected components
could be allocated..."
Solution :
This is the most common type of issue that is reported for component pick
release.
There are different causes for this :
A Subinventory setup
a. The source sub inventory (from which the material is allocated) should be
reservable.
b. The supply sub inventory (to which the material is supplied the
staging/destination subinventroy) should NOT be reservable.
When pickset is turned on, if any one of the component does not have qty,
you will get the appropriate error meessage.
a. Go into the responsibility: <Inventory>.
b. Navigate to setup > Organization > subinventory.
c. Query for the sub inventory name.
d. Change the reservation flag as mentioned in Clause 1 for source sub
inventory to reservable.
e. Change the LPN Controlled flag for the supply sub inventory as mentioned
in Clause 2 above to non-reservable.

B. Lot control item issue


If "Single lot allocation" is checked then there should be a lot in inventory
which can fulfill the complete requested quantity.
This is applicable whether "Partial allocation" is checked or not.
To un-check "Singe lot allocation" go to:
Inventory>Setup>Rules>Picking
C. Discrete job linked to Project :
35

Soft pegged items can be allocated from common locations, but hard pegged
items will have to be allocated only from project locations. So, you should
ensure that for hard pegged items you have on-hand in the respective
project/task referenced in the job.

2. When running component pick release, only push components are picked.
Assemby Pull and Operation Pull components are being ignored.
Solution :
Set the Release Backflush Components wip parameter to enabled.
This is set using :
WIP>Setup>Wip Parameters>Material
Components parameter.

Parameters>

Release

Backflush

3. Push Components are not being issued directly to the job or schedule.
They are being moved to a staging subinventory.
This is a setup issue. Remove the staging location for the push component on
the Bill of Material.
4. Cannot Cancel or Close Move Order Lines For Component Pick Release.
This is an Enhancement Request - BUG:3985920
The workaround is as follows :
a. Backorder the move order line.
Backordering acts like cancelling. The move order line that is backordered
goes into status 5 / closed and the pending transactions related to the
allocated quantity in the table, MTL_MATERIAL_TRANSACTIONS_TEMP, are
removed.
b. Modify the source document (workorder / job) so that the component is
no longer required. For example, set the quantity to 0. You would goto the
workorder information and change the operation related to the component
reducing the quantity as required.
5. When run Component Pick release for a flow schedule get message:
"None of the Material Requirements for the selected components could be
36

allocated. Please re-query to view the open requirements" (for release 12


and later)
Solution :
There are components which do not have enough stock.
Run following scripts to find these components:
a. SELECT primary_item_id, organization_id
FROM wip_flow_schedules WHERE schedule_number = '&Sch Name';
--Enter the Schedule Name for the line.
--Use the value of primary_item_id and organization_id for the below
queries.
b. SELECT bill_sequence_id FROM BOM_BILL_OF_MATERIALS
WHERE assembly_item_id = &item_id AND organization_id =&org_id ;
-- Use the bill_sequence_id in below query.
c. SELECT component_quantity,
component_item_id,
supply_subinventory
FROM bom_inventory_components
WHERE bill_sequence_id = &bill_seq
AND
NOT EXISTS
(SELECT 1
FROM mtl_onhand_quantities_detail
WHERE inventory_item_id = component_item_id
AND organization_id = &orgid
AND((subinventory_code = supply_subinventory) OR(supply_subinventory IS
NULL)
)
AND primary_transaction_quantity >= component_quantity
AND NOT EXISTS
(SELECT 1
FROM mtl_system_items_b
WHERE item_type IN('OC', 'PH')
AND inventory_item_id = component_item_id)
)
AND
EXISTS (SELECT 1
FROM mtl_system_items_b
WHERE item_type NOT IN('OC', 'PH')
37

AND inventory_item_id = component_item_id);


6. Get the following error when running component pick release : Error in
component pick release. Job/schedule number XXX has a reservable supply
subinventory
(XXX) for component XXXXXXXX.
For component pick release to work, source subinventory should be
reservable and destination (or supply) subinventory should be nonreservable.
To implement the solution, please execute the following steps:
Please setup the supply subinventory (destination subinventory) as non
reservable.
7. Component Pick Release does not select the source subinventory defined
for the particular subinventory in the subinventory summary window.

The source subinventory for a particular subinventory is defined for


replenishment and planning purpose.
Whilst allocating the material for the WIP component issue, the source
subinventories are not considered at all while allocating the material for the
job. From the inventory side allocations are always based on the set picking
rules and it does not consider the cascading of source subinventories across
multiple subinventories. It considers the picking order of subinventories if
this is selected as a criteria on the inventory picking rule.
In a WMS enabled organization, user can define the source subinventory via
using the WMS rule which will be picked while performing the pick release.
While defining the WMS rule, user can specify the source subinventory and
the list of items which will always be picked from the specifed source
subinventory while performing the pick release.
8. Get the following error when running component pick release :
Job/schedule number <> has a reservable supply subiventory (<>) for
component <>
Solution :
Item had subinventory/locator associated with the component <>
a. Navigate to WIP > Job/Schedule details > Material requirements
b. Query for the problematic job <> and click find.
38

c. Click on supply tab and delete the supply subinventory/locator associated


with the component <>.
note: subinventory and locator should be blank, save the changes.
d. Go to Component Pick release and perform the component pick release
activity for this job and verify the status.
Note: Please make sure that there is sufficient quantity in the
subinventory/locator <> so as to generate a move order.
9. When releasing a WIP component pick release the system creates move
order headers with no associated move order lines.
This is the current functionality (R12). Component pick release will allocate
the material only from reservable subinventories. The reason for this being
that if it were to pick material from non-reservable subinventories, then it
could pick material already picked for another job, since picked material
resides in supply subinventories which are not reservable.
WIP component Manufacturing move order lines are auto detailed, when
running WIP component pick release. If the detailing process is unable to
allocate the lines, then the lines will get backordered and closed. Hence, if
the pick from subinventory is not reservable, all the move orders lines will get
closed and the components will not get allocated.
To confirm that this is the issue you are seeing, check that the Source
Subinventory is reservable by either:
a. Querying the subinventory in the subinventory screen
OR
b. Via SQL:
select * from mtl_secondary_inventories
where organization_id = &org_id
and SECONDARY_INVENTORY_NAME = '&subinv';
Check reservable_type = 1
Solution:
Change the reservation flag for the source subinventory to reservable.
a. Go into the responsibility: <Inventory>.
b. Navigate to setup > Organization > subinventory.
39

c. Query for the sub inventory name.


d. Check the reservation flag for source sub inventory to reservable.
10. Why isn't the Component Pick Release (SRS) program releasing all eligible
jobs?
In the Days Forward field, enter the number of days in the future to consider
requirements for this pick release."
For example, if this value is 1, and your program is scheduled to run daily - it
will pick up requirements for jobs and schedules up to one day forward. Any
new material requirements added today are picked up by the concurrent
program when it is scheduled to run next.
The Concurrent Pick Release SRS program will only look for requirements one
day into the future when the "Days Forward" value is set to 1.
Any job with a start date more than one day into the future will not be picked
when the "Days Forward" value is 1.
11. Component Pick Release Form Gives WIP_PICKING_NO_JOBS Error When
Querying for Released Jobs (release 11 error).
Solution :
Check the Release Backflush Component checkbox in the WIP Parameters
screen.
a. Navigate to WIP > Setup > Parameters.
b. In the Backflush Defaults tab, check the Release Backflush Component
checkbox.
c. Save.
12. Cannot Do Component Pick Release Across Tasks On The Same Project.
Issue clarification :
Standard functionality prevents material transactions between tasks on the
same projects unless PJM: Allow Cross Project Issues is set to Yes. But setting
Project Manufacturing (PJM): Allow Cross Project Issues to Yes also allows
'unregulated' material transfers between projects and the customer does not
want to allow the transactions between projects. For example, there are
warranty and repair tasks on the project. The client has to do manual
transactions between these tasks and the production material task in order
to issue material. This happens frequently and the customer needs a way to
40

avoid the manual transactions. Is there a way to allow cross task (same
project) component pick release but not cross project component pick
release?
Solution :
This is standard functionality. You have to set the following profile :
Set PJM: Allow Cross Project Issues to Yes
An Enhacement Request has been logged for this however. (bug 8763203)
13. Component Pick Release Generates Move Order for an Item with Two
Different Revisions - Is Also Considering Older Revision
Issue Clarification :
Component Pick Release generates move order to transact an item with 2
different revisions.
If there is no sufficient onhand quantity for the latest revision of the
component, then the system is considering older revisions to fullfill remaining
quantity and generating mover order lines even for the older revisions.
Is this a standard functionality or a Bug?
Solution :
As per the application, this is the standard functionality that if there is no
onhand quantity for the latest revision, then the system will consider older
revisions to fulfill the remaining quantity and generates the move order lines.
This is intended functionality and not a bug.
At the time of transaction, under View/Update Allocations form, the user is
able to update the Revision information and can select the latest revision for
transaction.
Refer to Bug 3590202.
With the new functionality, revision will not be populated in record structure
for mtl_txn_request_lines table even if the item is revision controlled. This
will allow user to choose revision while transacting Move Order. User can use
inventory/wms rule to select revision as per requirement. Prior to this
functionality, WIP always passed latest revision to mtl_txn_request_lines
causing two problems: customers could not pick a back revision, and
inventory would error out if there was not sufficient onhand quantity of the
current revision even if older rev parts were on hand.
14. Component Pick Release Not Creating Tasks For Correct Qty (release 12.1
and later)

41

Solution :
The issue is caused by the following setup:
"Include Component Yield" under Material Tab of WIP parameters was not
checked.
Go into the responsibility: Work in Process.
Navigate to WIP->Setup->Parameters
At "Material Tab", please check the checkbox "Include Component Yield"
15. WIP Component Issue Stuck In Pending Transactions (release 11i)
Issue Clarification :
a.Transactions were showing in Pending Transactions screen and not being
picked up by the Process Transactions Interface INCTCM and passed to
INCTCW for processing.
In the MMTT (mtl_material_transactions_table)
b. The transactions were in TRANSACTION_STATUS = 2 and INCTCM will only
process NULL or 1 status transactions
c. Each transaction had a MOVE_ORDER_LINE_ID associated with the line.
d. The components were issued to the job using the WIP Component Pick
Release Screen.
e. The lines are NOT in error and have the proper settings for all critical fields
PROCESS_FLAG = Y,
LOCK_FLAG = N,
TRANSACTION_MODE = 3,
ERROR_CODE = NULL
TRANSACTION_TYPE_ID = 35
TRANSACTION_ACTION_ID = 1
TRANSACTION_SOURCE_TYPE_ID = 5
5. These lines will NOT be picked up by the BDEproc.sql or other diagnostics
since they are not in error or actually a problem.
Solution :
The application is functioning as designed.
For components that are issued to a job using the Pick Release functionality
you must transact the Move Order in order to complete the process.
42

a. Pick release the components for the job.


b. Transact the move orders to move the picked products out of the sub
inventory and into the job.
Use Inventory Responsibility NAV: / Move Orders / Transact Move Orders
Transact the Move Orders to complete the process and the lines will be
moved from TRANSACTION_STATUS = 2 to the proper status to be picked up
by the Pending Transactions Interface and processed.
16. Cannot over-pick for the move order created from component pick
release why is this?
Solution :
This is a setup issue. As long as you are using 11.5.10 and higher, over-picking
of move orders is allowed.
Set the organization parameter flag "Overpicking for WIP enabled". This will
allow over-picking of move orders.
17. Kanban Items are released via Component Pick Release. How do we stop
this?
Solution :
Please change the components that you want to issue to the job to "push".
Your kanban items and other backflushed items should be defined as
assembly pull components. Then set the Release Backflush Components as
appropriate
In summary :
If Release Backflush Components is enabled:
Supply type push components are considered in the pick release and not
backflushed
Supply type pull components are considered in the pick release and are
Backflushed
If Release Backflush Components is disabled:
Supply type push components are considered in the pick release and not
backflushed
Supply type pull components are not considered in the pick release, but are
backflushed
18. Cannot run componeht pick release (SRS) concurrent program to pick
release by operation.
43

Issue clarification :
Navigate to Work in Process > Discrete > Component Pick Release >
Component Pick Release (Form).
Note that you can pick release by operation.
Navigate to Work in Process > Discrete > Component Pick Release >
Component Pick Release (SRS)
Note that this method does not have the parameters available to pick release
by operation.
Solution :
This is standard functionality.
There is an enhancement request for this - Bug 9412745.
19. How to Customize the Pick Slip Report on Print Pick Slip Button On
Transact Move Order Line Allocations Form ?
Issue Clarification :
On the Transact Move Order Line Allocations form, there is a Print Pick Slip
button. This button submits the seeded Pick Slip Report. Is there anyway to
set this to run a custom pick slip report or to use a different document set
when this button is click on. What user want is whether he can be able to
sumbit a document group or our custom pick slip report when the Print Pick
Slip button is clicked on in the Transact Move Order Line Allocations form.
Can this be done without modifying this form.
Solution :
a. As per the standard functionality in APPS, WSHRDPIK is hardcoded in the
form INVTOTRL.pld - which appears to hardcode the pickslip to WSHRDPIK.
b. You can open this file in Forms Designer and make the change to the
report and save it .
20. The component pick release (SRS) concurrent program is not showing the
parameter to select by pickset this is available in the forms (apart from flow
manufacturing).
Solution :
This is a hidden parameter. Here is how you enable it.

44

Go to System Administrator>Concurrent>Program>Define
Query Back : Discrete Job Component Pick Release (SRS)
Click parameters button and select the parameter : p_use_pickset_indicator.
Click display and then save.
21. The discrete job component pick release (SRS) concurrent program is not
showing the parameter to select by job type (standard jobs, non-standard
jobs).
Solution :
It may be hidden. Here is how you enable it.
Go to System Administrator>Concurrent>Program>Define
Query Back : Discrete Job Component Pick Release (SRS)
Click parameters button and select the parameter : p_job_type. Click display
and then save.
22. Why cant we make the supply subinventory reservable?
Component Pick release will not function if the supply subinventory is set as
reservable. It must be non-reservable. There is a good reason for this.
For example : Assume that there is some material in the supply subinventory
which is to be used in a WIP job.In the meantime your Sales order pick
release reserves material from here.
What happens to the WIP job then? Additional components will have to be
arranged for the WIP job. This wip job may have been planned with
appropriate resources etc. Customer orders will be dependent on ensuring
that wip job is completed. But now you will have to go through the process of
finding components and this will severely delay the job. You may have to
purchase new components or move components from other subinventories
to the supply subinventory. Hence for reasons like this, supply
subinventories should be non-reservable.
23. The system cannot allocate from source subinventories which are
reservable.
Solution : This is the standard functionality.
a. The source sub inventory (from which the material is allocated) should be
reservable.
45

b. The supply sub inventory (to which the material is supplied the
staging/destination subinventroy) should NOT be reservable.
There is an enhancement in place to allow allocation from non-reservable
subinventories :
ER 0104305 - ALLOW COMPONENT PICK RELEASE TO DRAW FROM NONRESERVABLE SUBINV
24. Component pick release is not releasing items even though stock is
available. Why ?
Solution :
The likely cause of this is that an inventory picking rule has NOT been
created.
An inventory picking rule is mandatory. It needs to be assigned at
organization level as follows :
It is an Organization parameter>Inventory Organization - you can specify the
default inventory picking rule for your organization. (Inventory
Information>ATP Pick and Item Sourcing Tab).
It can also be specified at item level (item parameter Item Master > Order
Management tab).
In release 12, inventory picking rules can be assigned to various business
objects such as customer etc.
25.Why cant bulk items be automatically issued to WIP jobs using
component pick release?
Solution :
The answer is no, bulk items can be manually issued to a job but they can not
be automatically backflushed.
26. Cannot find a certain job or schedule from the component pick release
find window.
Solution :
This is because the job or schedule that you are trying to select is not eligible
for component pick release. Read the section 4A Step 1 to check eligibility
criteria.
27. The system is not allowing the creation of a rule which picks a particular
46

item from a particular source subinventory only.


Solution:
This is not possible using standard inventory picking rules.
However, it can be done using WMS rules if the organization is WMS enabled.

Component Pick Release


April 2011
Author: Zar Ahmed
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065
U.S.A.
Worldwide Inquiries:
Phone: +1.650.506.7000
Fax: +1.650.506.7200
www.oracle.com
Oracle is a registered trademark of Oracle Corporation. Various

47

product and service names referenced herein may be trademarks


of Oracle Corporation. All other product and service names
mentioned may be trademarks of their respective owners.
Copyright 2003 Oracle Corporation
All rights reserved.

48

You might also like