Today, i found one strange thing in the system. the user pick item for wip, the wip with project and task. but the item can be picked from the same project but different task.

As for non-wms org, usually, the item can be picked from the same project, same task. or from the common locator(which means without project, task).

For the hard pegging item(END_ASSEMBLY_PEGGING_FLAG=X), the item can only picked from the same project, same task. (non-wms org).

For the soft pegging item(END_ASSEMBLY_PEGGING_FLAG=B), the item can pick from the same project, same task, also can picked from common locator(which don’t contain project task). but the item can’t picked from different task.

As for wms org, we can set the pick rule, usually the rule will set, the job can be picked only the same project, no limit for the task.

Also checked the information in metalink, found the following explain (there is no explain, if there wms impletation for the org):

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 we do not want to allow the transactions between projects. The issue is a warranty and repair tasks on the project and must do manual transactions between these tasks and the production material task in order to issue material. This happens frequently and need a way to avoid the manual transactions. Is there anyway to allow cross task (same project) issues but not cross project issues?
Is there anyway to allow cross task (same project) issues but not cross project issues?

Solution

IT is the standard functionality. Enhancement requested has been logged bug 8763203
### Workaround ###
Set the PJM parameter: Allow Cross Project Issues to Yes in the PJM Organization Parameters form.

After i checked for a long time, i realized, the org acutually, there is no wms install, but we don't know when, who set the parameter wms enabled as yes, then we use the following script. to check if there have relation wms transaction happened:

How to Enable/Disable WMS Enabled Flag Check Box for New or Existing Inventory Organization (Doc ID 1364172.1)

a) Select organization_id,Organization_code,wms_enabled_flag
from mtl_parameters where organization_code = '&org_code';

To Check LPN Details
=======================
b) select count(wlpn.license_plate_number) from wms_license_plate_numbers wlpn, mtl_parameters mp
where mp.organization_id = wlpn.organization_id
and mp.organization_code = '&org_code';

c) select count (wlc.parent_lpn_id) from wms_lpn_contents wlc, mtl_parameters mp
where mp.organization_id = wlc.organization_id
and mp.organization_code = '&org_code';

d) select count(wlh.lpn_id) from wms_lpn_histories wlh, mtl_parameters mp
Where Mp.Organization_Id = Wlh.Organization_Id
and mp.organization_code = '&org_code';

To Check Pending PO details
==============================
e) Select count(Ms.Supply_Source_Id) From Mtl_Supply Ms, Mtl_Parameters Mp
Where Ms.To_Organization_Id = Mp.Organization_Id
and mp.organization_code ='&org_code';

f) Select count(Ms.Supply_Source_Id) From rcv_supply Ms, Mtl_Parameters Mp
Where Ms.To_Organization_Id = Mp.Organization_Id
and mp.organization_code ='&org_code';

To Check Pending SO details
============================
g) Select Wdd.Source_Code, Wdd.Released_Status, Wdd.Oe_Interfaced_Flag,Wdd.Inv_Interfaced_Flag,Count(Wdd.Delivery_Detail_Id)
From Wsh_Delivery_Details Wdd, Mtl_Parameters Mp
Where Wdd.Organization_Id = Mp.Organization_Id
And Mp.Organization_Code = '&org_code'
group by wdd.source_code, Wdd.Released_Status,Wdd.Oe_Interfaced_Flag,Wdd.Inv_Interfaced_Flag;

To check Pending Transactions and Uncosted Records
===================================================
h) Select Count(Transaction_Temp_Id) From Mtl_Material_Transactions_Temp Mmtt, Mtl_Parameters Mp
Where Mp.Organization_Id = Mmtt.Organization_Id
And Mp.Organization_Code ='&org_code';

i) Select Count(Transaction_Interface_Id) From Mtl_Transactions_Interface Mti, Mtl_Parameters Mp
Where Mp.Organization_Id = Mti.Organization_Id
And Mp.Organization_Code ='&org_code';

j) Select Count(Transaction_id) From Mtl_Material_Transactions Mmt, Mtl_Parameters Mp
Where Mp.Organization_Id = Mmt.Organization_Id
and mmt.costed_flag is not null
And Mp.Organization_Code ='&org_code';

To check transaction history with LPN reference
================================================
k) Select Count(Transaction_Id) From Mtl_Material_Transactions Mmt, Mtl_Parameters Mp
Where Mp.Organization_Id = Mmt.Organization_Id
And Mp.Organization_Code ='&org_code'
And( Mmt.Lpn_Id Is Not Null
Or Mmt.Transfer_Lpn_Id Is Not Null
or mmt.content_lpn_id is not null);

To check the Rule details
============================
l) Select R.Organization_Id, R.Type_Code,R.Wms_Enabled_Flag ,Count(R.Rule_Id)
From Wms_Rules_B R , Mtl_Parameters Mp
Where MP.organization_code = '&org_code'
And (R.Organization_Id = Mp.Organization_Id
Or R.Organization_Id = -1)
Group By R.Organization_Id, R.Type_Code,R.Wms_Enabled_Flag
order by R.Organization_Id, R.Type_Code;

if there is no record return for all these query, we can use datafix to update (make sure backup) :

update mtl_parameters
set wms_enabled_flag = 'N'
where organization_code = '&ORG_CODE' and wms_enabled_flag = 'Y' ;

i guess the user pick from task A to task B, must because there have miss setup for the wms_enabled_flag.

i tried set the flag as Yes, then picked successful. when i update the flag as No, we can't pick from task A to task B.

note:

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.

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).

Question:

While Performing Component Pick Release the Following Error Message Occurs "None of the material requirements for the selected components could be allocated..."

Answer:

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: .
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 :
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.

ITPub博客

wip component pick release

最新文章