Professional Documents
Culture Documents
1. OVERVIEW ............................................................................................................................................................................................................................... 1
6. WHAT HAPPENS IF I RUN COMPONENT PICK RELEASE AGAIN FOR THE SAME JOB OR SCHEDULE ? ................................................................25
12. DIFFERENCES IN COMPONENT PICK RELEASE FUNCTIONALITY BETWEEN RELEASE 11 AND RELEASE 12 ................................................30
The objectives of this white paper are to discuss component pick release – I
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 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
pre-requisite 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.
4. Define the Source Subinventory. This is the subinventory in which the on-
hand 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.
If this information is not defined, the default values are taken from the
WIP Parameters form.
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.
3
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.
• 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).
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.
6
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.
7
• The materials are transactable (inventory item attribute).
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.
1. Discrete Jobs :
Key Points :
Key Points :
3. Repetitive Schedules :
9
Key Points :
4. Flow Schedules :
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)
• Flow Manufacturing Mode (The Flow Schedule operates in this
mode)
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.
• 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.
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.
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 :
13
current component pick release.
Now lets consider the following question - What happens when the
release button is clicked in Component Pick Release?
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 :
o mtl_txn_request_headers - containing
the header details
Query the move order. Select the move order line. Then click
the View/Update Allocations button to view or amend the
allocations.
15
be executed once you transact 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 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 :
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):
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 :
Now let’s look at the summary and detail windows to illustrate the step we
are currently discussing :
19
If we select a component, the detail window is displayed for the component as
shown below :
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'
/
1 Incomplete
2 Pending Approval
3 Approved
4 Not Approved
5 Closed
6 Canceled
7 Pre Approved
8 Partially Approved
9 Canceled by Source
In the above example, the system did a PARTIAL ALLOCATION for ZA-
Component-6 and backordered the quantity that is not available. A
quantity of 15 was required for each component. Since only 10 of ZA-
Component-6 were available to transact, the remaining 5 have been
21
backordered.
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 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.
Here is the current state of the discrete job which shows the pull
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:
The on-hand and available to transact quantities for the pull components are
updated as above.
24
6. WHAT HAPPENS IF I RUN COMPONENT PICK RELEASE AGAIN FOR THE
SAME JOB OR SCHEDULE ?
• 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.
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 :
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.
Go to System Administrator>Concurrent>Program>Define
Query Back : Discrete Job Component Pick Release (SRS)
26
• Job Type :
Go to System Administrator>Concurrent>Program>Define
Query Back : Discrete Job Component Pick Release (SRS)
So why run component pick release? Here are the advantages it offers :
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;
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);
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;
For debugging Component Pick Release in R12 and higher, use the FND
Debug settings as follows:
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
In this section, the differences between the component pick release
functionality in release 11 and release 12 will be briefly discussed :
• 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.
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 :
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:
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
30
8. Get the following error when running component pick release :
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?
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)
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).
31
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 ?
26. Cannot find a certain job or schedule from the component pick release
find window.
27. The system is not allowing the creation of a rule which picks a particular
item from a particular source subinventory only.
Answers :
Solution :
This is the most common type of issue that is reported for component pick
release.
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.
32
B. Lot control item issue
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 :
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.
Backordering acts like cancelling. The move order line that is backordered
33
goes into status 5 / closed and the pending transactions related to the
allocated quantity in the table, MTL_MATERIAL_TRANSACTIONS_TEMP, are
removed.
5. When run Component Pick release for a flow schedule get message:
Solution :
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)
34
)
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')
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.
7. Component Pick Release does not select the source subinventory defined
for the particular subinventory in the subinventory summary window.
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.
35
8. Get the following error when running component pick release :
Solution :
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:
OR
b. Via SQL:
36
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.
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.
Solution :
37
12. Cannot Do Component Pick Release Across Tasks On The Same Project.
Issue clarification :
Solution :
This is standard functionality. You have to set the following profile :
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 :
Solution :
38
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)
Solution :
"Include Component Yield" under Material Tab of WIP parameters was not
checked.
Issue Clarification :
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
39
TRANSACTION_SOURCE_TYPE_ID = 5
Solution :
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.
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 :
40
backflushed
• Supply type pull components are considered in the pick release and are
Backflushed
18. Cannot run componeht pick release (SRS) concurrent program to pick
release by operation.
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 :
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 :
41
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 :
Go to System Administrator>Concurrent>Program>Define
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 :
Go to System Administrator>Concurrent>Program>Define
Click parameters button and select the parameter : p_job_type. Click display
and then save.
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
42
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.
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.
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.
It can also be specified at item level (item parameter – Item Master > Order
Management tab).
Solution :
43
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
item from a particular source subinventory only.
Solution:
44
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
45