Professional Documents
Culture Documents
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 :
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.
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 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
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.
Pick
Key Points :
Key Points :
3. Repetitive Schedules :
Navigation : Work in Process>Repetitive>Component
Release>Component Pick Release (Form)
Pick
Key Points :
4. Flow Schedules :
Navigation : Flow Manufacturing>Production>Component Pick
Release>Component Pick Release (Form)
Key Points :
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
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.
11
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 :
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
mtl_txn_request_headers
the header details
- containing
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
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
19
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
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
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:
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
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 :
and
select
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.
28
29
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.
Enable Material Issue Requests is set to 'Yes' for the work order
Paramet
er
Type
Default Value
Field / LOV
Mandatory
Days
Forward
Pick slip Mandatory
groupin
g rule
Print
Pick
slips
Optional
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.
32
33
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.
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
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
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
47
48