Sunday, February 21, 2016
OSP Reference from Oracle support
BUG:5891903 - THERE'S DIFFERENCE BETWEEN QTY OF WIP JOB AND BLANKET RELEASE IN CASE OF OSP.
OSP FAQ from Oracle support
QUESTIONS AND ANSWERS
1. Why PR or PO or release of BPA is not created?
Possible causes:
- The Line Type "Outside Processing" is end dated, so invalid Transaction Type error occurs in the Requisitions interface.
How to check:
Go Purchasing > Setup > Purchasing > Line Types > go to Name= Outside Processing
press pencil icon to Update > Page will open and will display the End Date field >>> IT SHOULD BE null
Same can be verified using: select * from po_line_types
- WIP applications must be fully installed mode for OSP to work correctly
Purchasing does not automatically default accounts unless WIP is fully installed.
Script to check that WIP is installed:
select distinct fpg.release_name "Apps Level"
, fpi.patch_level "Family Pack"
, fat.application_name "Application"
, fpi.application_id "ID"
, decode(fpi.status,'I','Installed','S','Shared','N/A') "Status"
from apps.fnd_application_tl fat
, apps.fnd_product_installations fpi
, apps.fnd_product_groups fpg
where fat.application_id(+) = fpi.application_id
and fpi.patch_level like '%'||upper('WIP')||'%'
order by 1, 2;
- The system will not create requisitions unless the job/work order is 'Released': requisition creation time is dictated by WIP parameter "Requisition Creation Time"
Values can be:
"At Job/Schedule release" – requisition is created when job is released
"At Operation" - requisition is created when qty is moved in the Queue of the OSP Operation
Manufacturing and Distribution Manager>Setup>WIP Parameters
- OSP resource charge type should not be "Manual" for OSP resources: valid charge types for OSP resources are "PO Receipt" and "PO Move" (for EAM only "PO Receipt" is valid, as EAM is not using move transactions)
Bills of Materials>Routings>Resources
- Department which is linked to an OSP resource should have a Location being linked to it. OSP department should have deliver to location, otherwise apps will not know where the material should be delivered to (deliver to location is mandatory for SHOP FLOOR destination )
Bills of Materials>Routings>Departments
- OSP Item should have a List Price Defined in Item master form
Inventory>Items>Master Items>Purchasing TAB
- Profile option WIP:Enable Outside Processing Workflows is set to “No” (in this case program Requisition import program is not getting automatically launched when job is released. But if you manually launch Requisition import program, then PR is getting created). Profile option “WIP:Enable Outside Processing Workflows” needs to be set to "Yes" in order that requisition import to be launched.
- OSP item is not linked to the OSP resource: Bills of Materials>Routings>Resources
- OSP resource is not linked to the OSP operation : Bills of Materials>Routings>Departments
- When the quantity involved for OSP is large the cause may be that Organization calendar does not have a long period defined. This is an issue when the item has a large lead time and for WIP to schedule large OSP quantities according to their lead time may exceed the calendar defined for the organization.
- In EAM: when in Purchasing > Set purchasing Options> Set Requisition Import Group-By was not set (value was null) – requisition is not created (see Document 866980.1)
- sometimes The 'Requisition Import' is automatically triggered when the work order is released from EAM and this program completes successfully without any errors but PR is not created . This is because 'Requisition Import' concurrent program picks the records from the 'po_requistions_interface_all' based on the value of the profile 'MO: Operating Unit'.
We need to value of the profile 'MO: Operating Unit' to the operating unit where the requisitions will be released (see Document 458866.1)
- Can happen because implementation includes multiple inventory organizations each processing OSFM work orders under different operating units. (see more in Document 1100223.1)
- Can happen if "WIP:Purchasing By Revision" profile option was set to NO and the Blanket PO is revision controlled. (Then the create releases concurrent request would not create a release) – see more in Document 266013.1
- Can happen in release 11i when attempting to do Move Transactions and Scrap Transactions simultaneously through the interface table WIP_MOVE_TXN_INTERFACE – then the following error is given:
„Requisition is in a pending status and cannot be updated or canceled. Cause: Requisition is still in an interface table.” – this is because of Bug:5460322 and was solved in wipospvb.pls version 115.76.11510.14 or higher (see more in Document 405535.1)
- in case user who release the job/WO is not a buyer/requestor, the job will not be release, user will receive a meaningful error . To set the user as buyer Navigate to Purchasing responsibility > Setup > Personnel > Buyers (see more about setup in Document 1179771.1)
- Can happen because of profile option WIP:Launch Requisition Import for PO Receipt having value N, if OSP resource having charge type= PO Receipt (see more in Document 1460246.1)
- Can happen if Resource Charge Type is 'WIP Move' or 'Manual' in the job. The only OSP accepted Resource charge types are: "PO Move" or "PO Receipt". Please check in Discrete Job > Operations > Resource > Costing tab
2. Why OSP Job Gets Completed Without Backflush Components Issue?
This is the current functionality (behavior was changed after Patch:4504810 - See more and also some workarounds in Document 554132.1)
Move /Completion transaction and Material transactions are two different processes
Move/Completion transaction will occur based on operations and Material transaction will occur based on onhand availability.
If charge type or the OSP resource is PO Move, the system should perform an automatic move transaction against OSP operation, and if the OSP operation is the last operation, whenever you perform a receipt/delivery transaction, the system will automatically perform move and completion transactions for this job. As all the operations are completed, the job status will change to Complete.
With respect to the backflush of component at OSP operation, if there is sufficient onhand quantity, then all the components will be issued. If there is not a sufficient onhand quantity, then the system will show pending move transactions at Backflush Phase (it is showing under pending move transaction because IF supply type for components is Operation/Assembly Pull and it is dependent on move transaction only) with appropriate error message.
WIP_MOVE_TRANSACTIONS_INTERFACE (WMTI):
a) Once the record is populated in WMTI for move and complete, the move worker would process this transaction.
b) Completion transaction will be processed first and then the backflush transactions (PULL components).
c) If completion is successful, the job is completed.
d) If backflush fails for any reason, WMTI record is updated to process phase "Backflush setup" and status="error". It will also populate the reason why the backflush failed.
e) User needs to resubmit the WMTI record after correcting the error.
MTL_TRANSACTIONS_INTERFACE (MTI): Completion fails if backflush fails.
3. Why getting error: WIP_BATCH_MOVE_ERROR Transaction quantity must be less than or equal to quantity available
ERROR:
WIP_BATCH_MOVE_ERROR Transaction quantity must be less than or equal to quantity available
or in some cases, the error is:
XXXX.Quantity must be less than or equal to Available to transact
(XXXX is the component number)
WIP_BATCH_MOVE_ERROR Transaction quantity must be less than or equal to quantity available
or in some cases, the error is:
XXXX.Quantity must be less than or equal to Available to transact
(XXXX is the component number)
Causes:
1. If Move manager has not been running and in the meantime a new move/completion transaction was done, this will created an over-completion and caused the error – see more in Document 755396.1
1. If Move manager has not been running and in the meantime a new move/completion transaction was done, this will created an over-completion and caused the error – see more in Document 755396.1
2. The job is awaiting a receipt, but a receipt is made for a Quantity greater than the job Quantity. In this case solution is to reduce the Transaction Quantity so that it equals the job Quantity, and resubmit the Transaction.
4. Why Requisition Import Request For OSP Items Is Creating Requisitions in Approved Status?
In 11.5.10.2 Requisitions created by sources such as WIP, EAM, and MRP modules would have status of APPROVED.
Enhancement Request Bug:4276433 is logged for this feature and in R12.1 patch 4276433:R12.WIP.B was released, solving the ER.
The patch is only valid for R12.1.X. Some extra patches are necessary after application of patch 4276433:R12.WIP.B - complete solution is formed of:
Patch 4276433:R12.WIP.B
Patch 12783535:R12.FND.B
Patch 16689986:R12.PO.B
Patch 17269099:R12.EAM.B - see more in Document 1584936.1
Patch 12783535:R12.FND.B
Patch 16689986:R12.PO.B
Patch 17269099:R12.EAM.B - see more in Document 1584936.1
There are some workarounds to emulate the requirement that PR will be included in approver workflow: Workarounds for 11i and R12 are presented in Document 787761.1
5. Why receive error: The transaction quantity exceeds the overcompletion tolerance set for the Job, Repetitive Line/Assembly, or the Organization
ERROR: The transaction quantity exceeds the overcompletion tolerance set for the Job, Repetitive Line/Assembly, or the Organization
This may happen because of 3 causes:
5.1 User has already done a manual move and there is NO quantity in Queue of OSP Operation when performing the OSP receiving
Make sure you do not do any move past the queue of the OSP operation prior to the receipt or make sure you have moved to the queue of the OSP operation
5.2 User has intentionally received a quantity which is higher that the PO quantity, and there overcompletion tolerance was not set, neither at Org level or at Discrete Job Level. Make sure you setup a value for overcompletion tolerance in the Discrete Job > tab More - see more in < Document 1496210.1>
5.2 This is happening when performing multiple receive/deliver transactions - it is because of 11i BUG:5768720 or Bug:4232649 and it is solved by upgrading to WIPDSFMB.pls to version 115.24.11510.6 and WIPDSFMS.pls 115.8.11510.1
5.2 This is happening when performing multiple receive/deliver transactions - it is because of 11i BUG:5768720 or Bug:4232649 and it is solved by upgrading to WIPDSFMB.pls to version 115.24.11510.6 and WIPDSFMS.pls 115.8.11510.1
6. What happens if user is adding OSP operations to a WIP Job AFTER the PR was created?
If WIP Parameter is set to OSP Requisition “at Job Release” then when adding a OSP resource after job was released, the PR will not be created any more.
Workaround: Manually create the purchase requisition and link it to the Job. (see <Document1172973.1>)
7. Why OSP resource remain in error during resource validation: “The value for ORGANIZATION_ID either does not correspond to the value for ORGANIZATION_CODE or does not uniquely specify a value for ORGANIZATION_CODE. Please change ORGANIZATION_ID or ORGANIZATION_CODE. “
ERROR
The value for ORGANIZATION_ID either does not correspond to the value for ORGANIZATION_CODE or does not uniquely specify a value for ORGANIZATION_CODE. Please change ORGANIZATION_ID or ORGANIZATION_CODE.
The value for ORGANIZATION_ID either does not correspond to the value for ORGANIZATION_CODE or does not uniquely specify a value for ORGANIZATION_CODE. Please change ORGANIZATION_ID or ORGANIZATION_CODE.
This is because of 11i Bug:9955109 - Move Manager didn't honor profile HR: Cross Business Group so that when it set to No, Move manager will pick up the records for other business group which cause inventory validation error out with "Organization ID is either blank or invalid.
This is solved in wictms.ppc version 115.11.11510.3
8. Why getting error when trying to create purchase order (PO) and manually add OSP job the following error is returned: FRM-40212 Invalid value for field WIP_ENTITY_NAME
ERROR: FRM-40212 Invalid value for field WIP_ENTITY_NAME
This is because in LOV when choosing the job (to be linked to the PO) apps was showing also non eligible jobs. This is explained in Document 1207773.1 and was corrected in file wiposp.odf in version 120.5.12010000.5
9. Why for single Job/WO with 2 OSP items, system creates 2 separate PR/PO's even if they have same supplier.
For WIP module Requisition Import launched by WIP automatically always groups the requisition by 'Item'. If Discrete Job has 2 OSP items, It creates 2 PR and 2 POs.
This is because group-by parameter for the Requisition Import concurrent request call was hard coded to "Item". Issue was solved by upgrading to following file versions:
wipishpw.wft 115.9.11510.3
wipmovpb.pls 115.55.11510.46
wipmovps.pls 115.7.11510.4
wiposhib.pls 115.24.11510.5
wiposhis.pls 115.12.11510.1
wipospvb.pls 115.76.11510.25
wipospvs.pls 15.18.11510.6
wipmovpb.pls 115.55.11510.46
wipmovps.pls 115.7.11510.4
wiposhib.pls 115.24.11510.5
wiposhis.pls 115.12.11510.1
wipospvb.pls 115.76.11510.25
wipospvs.pls 15.18.11510.6
The fixed files are available via <Patch:13872017> – see more in Document 1462055.1
As workaround, is you want default group-by option set in PO to be honored, you need to manually launch the Requisition Import (change WIP parameter 'Requisition Creation Time' to Manual and then make sure that 'Requisition Import Group-By' is set as 'Vendor')
For EAM, the Group By parameter for the requisition import program which was hardcoded to 'Item' was changed as follows:
For OSP items issue has been fixed in the file EAMVWOSB.pls 115.38.11510.13.
For Direct Items issue has been fixed in file EAMVPWUB.pls 115.9.11510.9
You find more in Document 748623.1
For EAM, the Group By parameter for the requisition import program which was hardcoded to 'Item' was changed as follows:
For OSP items issue has been fixed in the file EAMVWOSB.pls 115.38.11510.13.
For Direct Items issue has been fixed in file EAMVPWUB.pls 115.9.11510.9
You find more in Document 748623.1
10. Why in EAM WIP Outside Processing Account is not being used as specified in WIP setup ("Material" account is being used instead)?
The cost of Direct/OSP items goes to the WIP Material Account. This is the expected default behavior. If a customer wants to change this behavior, they can set up category defaults which will send costs to another account based on the purchasing category used – see more in Document 1056158.1
11. How to see the job number when query a Requisition for an OSP item in Autocreate form? Why 'Job' column in Autocreated form is not showing the OSP job number?
As part of the Enhancements done in 11.5.10, autocreate 'Job' column will now show the 'Job Name' Related Services Procurement. And the Job/Work Order of the Outside Processing Items is Now displayed Under the Prompt 'Work Order'. he job column in Autocreate form is meant for Services Procurement Job Name in 11.5.10.
So you will need to use filed with Prompt 'Work Order' instead. (see more in Document 332940.1)
So you will need to use filed with Prompt 'Work Order' instead. (see more in Document 332940.1)
12. Why move transaction goes into error with following message: "THIS OPERATION IS NOT DEFINED IN THE ROUTING"?
In Oracle Work in Process, when the OSP operation is the last operation and there is no completion Subinventory mentioned on the Job, the receiving of the PO will get stuck in the Move interface because of Bug:6808384
ERROR: This Operation is NOT Defined in the Routing
Issue is solved in WIPDSFMB.pls 115.24.11510.15 and WIPDSFMS.pls 115.8.11510.1 and the new behaviors is like this: when the OSP operation is the last operation and there is no completion Subinventory mentioned on the Job, the receiving of the PO would get processed from Move interface and apps will populate the OSP operation's To move Intraoperation step.
13. How to avoid balance in Receiving Inventory Account: for OSP item the Absorption Account should be the same as Receiving Inventory Account
For RECEIVE transaction, the following accounting takes place for OSP item(Shop floor destination):
Receiving Inventory Account Debit (DR )
Accrual account Credit ( CR )
For DELIVER transaction, the following accounting takes place :
Absorption Account Credit (CR)
Outside processing Account Debit (DR)
To offset the Receiving Inventory Account , both the accounts should be same, else there will be a balance in Receiving Inventory Account. See more in Document 783623.1
14. Why OSP Purchase Orders will be auto created if job status is changed from Unreleased to On HOLD?
This is as per design, please see explanation and workaround in Document 1248745.1
15. Why OSP Purchase Orders will be auto created if job status is changed from Unreleased to Canceled ?
This issue is fixed starting with WIP RUP Patch:6024871 and above.
16. Why during costing process, resource transactions are going into error without any error message?
This can be because of 11i Bug:7184023 or R12 BUG:7344829
Cost manager is changing OSP Resource charge type from "PO Move" To "Manual" After Performing OSP Receipts.
In 11i this is solved in file wiltvr.ppc in version 115.18.11510.6 or higher .
In R12 issue is solved in wiltvr.ppc version 120.7 ( see more in Document 755125.1)
In R12 issue is solved in wiltvr.ppc version 120.7 ( see more in Document 755125.1)
17. Why when last operation is OSP, the job is not getting completed after receiving the OSP item?
This is because of 11i Bug:4024987 - UNABLE TO AUTO COMPLETE NON STANDARD JOBS WITH OSP and issue is solved by upgrading to file WIPDSFMB.pls 115.24.11510.2 or higher. (see more in Document 361361.1)
18. Why in OSFM (Shop Floor Management), the OSP requisition show quantity = 0 instead of the OSP item required quantity?
This is because of 11i BUG:4949404 - REQUISITION/RELEASE NOT CREATED FOR OSP ITEM WHEN SCHEDULED and is solved in WSMVIFSB.pls 115.23.11510.2 or higher (see more in Document 363225.1)
19. How Can We Restrict a Manual Move Transaction Against OSP Operation Before Receiving The Material: Shop Floor Status
This can be done by defining a specific shop floor status for which users will not be able to manually create move transactions (see details in Document 458806.1)
20. Why in OSFM when create PR for lot based jobs having an OSP operation as their first operation, the "Please enter a quantity greater than zero" error is coming
Complete error displayed by the Requisitions Import program is:
ERROR
Error Message: Please enter a quantity greater than zero (0)
Cause: You entered a quantity that was either missing or less than 0.
Action: Enter a non-zero quantity.
Error Message: Please enter a quantity greater than zero (0)
Cause: You entered a quantity that was either missing or less than 0.
Action: Enter a non-zero quantity.
This is only happening only for lot-based jobs imported through the WSMPLBJI.launch_worker API (the ones created manually via forms are creating requisition without any issue)
This is happening because of Bug:7033447 REQ'S ARE NOT CREATED FOR LBJ THROUGH WSM_LOT_JOB_INTERFACE, and issue has been fixed in the fileWSMOPRNB.pls 115.86.11510.4 or higher (see details in Document 780266.1)
21. Is system allowing to Close the Job if the PO Receipt of the Outside Processing (OSP) service of the Job is not yet complete?
If a receiving transaction is performed for OSP item after related job was closed, resource transaction will go into error:
ERROR: No charges allowed for this job/schedule
In case job was closed and also period was closed, the only fix is that user can delete the erred resource transaction from pending Transaction form (WIP>Resource Transactions > pending Resource Transactions). This will not charge the job with the OSP cost because pending resource transactions are not yet costed (costing is performed when resource transaction is moved from WIP_COST_TXN_INTERFACE table to WIP_TRANSACTION base table).
In order to avoid this error, please see workaround in Document 1279878.1
22. Why When changing the job start quantity, the related PO quantity is not changed even if the WIP parameter 'Propagate Job Change to Purchasing' is set to Automatic?
a. If this is only happening if OSP is NOT THE FIRST OPERATION, then it is as per design.
Propagate Job Change to PO feature will update PO/requisition quantity if job quantity change only if Requisition Creation time is set “At Job/Schedule
Release” or the first operation is OSP. If Requisition Creation time is set to “At Operation” and the first operation is not OSP, PO/requisition qty will not be updated because user cannot reduce job qty unless they move backward (which is not likely to happen).
Moreover, additional quantity will result in a new requisition once user move that additional quantity to the queue of OSP operation, so there is no need to sync anything for job quantity increase. We need this feature for At Release and the first operation is OSP because PO/requisition will be created after job is released. See more in Document 1062600.1
b. In case this is happening when OSP operation IS THE FIRST OPERATION then the cause is 11i Bug:5891903 THERE'S DIFFERENCE BETWEEN QTY OF WIP JOB AND BLANKET RELEASE IN CASE OF OSP and it is solved by upgrading to WIPDJMDF.fmb 115.289.11510.33 and WIPDJCOM.pld 115.87.11510.6 or higher ( see more in Document 781020.1)
23. Why in EAM, an extra PR is getting creating every time when WO status is changed from Released to Hold and back to Released (system is creating duplicate purchase requisitions)
This is because of R12 Bug:8594830 - OSP ITEMS ON EAM WORK ORDERS ARE TRIGGERING DUPLICATE PURCHASE REQUISITIONS and it is solved in EAMVWOSB.pls 120.23.12000000.13 or higher (see more in Document 871017.1)
24. How to setup for OSP resource costing
Standard rate box for an OSP resource (or any resource for that matter) is just a means to decide the way it is going to be charged to the job ( i.e. Value being added to the job, NOT about value being relieved).
If Standard rate box is checked, cost processor would look for the standard rate defined and use it.
Else, (if standard rate box is not checked) it will expect an actual resource rate with the resource transaction. This is true all costing methods.
When it comes to relieving OSP cost, based on costing method the behavior is as follows:
a. Standard costing: OSP cost will be relieved based on the assembly cost i.e. Assembly should have an OSP cost in its rolled cost in cost type = "Frozen". If it doesn't have OSP cost, it will not relieve. When the job is close, remaining value in the job will be relieved as variance.
If Standard rate box is checked, cost processor would look for the standard rate defined and use it.
Else, (if standard rate box is not checked) it will expect an actual resource rate with the resource transaction. This is true all costing methods.
When it comes to relieving OSP cost, based on costing method the behavior is as follows:
a. Standard costing: OSP cost will be relieved based on the assembly cost i.e. Assembly should have an OSP cost in its rolled cost in cost type = "Frozen". If it doesn't have OSP cost, it will not relieve. When the job is close, remaining value in the job will be relieved as variance.
b. Actual costing (Average/FIFO/LIFO): In these costing methods, there are lots of cases possible. But, the most common situation is whatever is charged to the job, will be relieved. If the OSP cost were not yet charged to the job, it wouldn't be relieved with the assembly cost.
25. Why Purchase Requisition is created only for single supplier for whole Outside Processing (OSP) job quantity, even if sourcing Rule exist for this item with two supplier having 60-40% allocation?
This is as per the current intended functionality only. For any item ( normal and OSP ), although the same ranks are defined at sourcing rule level with different allocation percentages, always the first supplier/supplier site combination will get picked up and requisition/PO are created. See more in Document 791406.1
26. Why in EAM only one Purchase Requisition is created for 3 OSP resources associated with one Operation (Expect a Purchase Requisition for each one of the resources.)
This is because of 11i Bug:5245343 and it is solved in
- EAMVWOSB.pls 115.38.11510.7
- EAMVWOVB.pls 115.57.11510.16
- EAMVWOSB.pls 115.38.11510.7
- EAMVWOVB.pls 115.57.11510.16
27. Why when OSFM OSP Job is splitted the corresponding OSP PO released is not getting splitted ?
Performing WIP lot transactions that have new resulting jobs,such as split or merge, would mean that PR or PO for the starting jobs would need to be cancelled manually. Note that instead of canceling all PR or PO for starting jobs and creating new PR for resulting jobs, you can keep existing PR or PO by updating only their distribution. Also if a PR/PO is kept because a starting job retained quantity and became a resulting job, then the quantity listed on that PR/PO would need to be updated manually.
28. Why get "ORA-06502: PL/SQL: numeric or value error: character string buffer too small" when release an OSP job?
Complete error is
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
ORA-06512: at "APPS.WIP_OSP_SHP_I_WF", line 229
ORA-06512: at "APPS.WIP_OSP", line 162
FRM-40735: POST-UPDATE trigger raised unhandled exception ORA-06502
ORA-06512: at "APPS.WIP_OSP_SHP_I_WF", line 229
ORA-06512: at "APPS.WIP_OSP", line 162
FRM-40735: POST-UPDATE trigger raised unhandled exception ORA-06502
This is a R12 bug, it is happening when assembly/OSP item name is longer than 40 characters and was solved in wiposhib.pls 120.2.12000000.4 and wiposhis.pls 120.0.12000000.1 or higher ( see Document 753169.1)
29. Why user is not able to see and select EAM Work Order in PO ENTRY form (POXPOEPO)?
When creating a Purchase Order, selecting an Item which is set for Outside Processing (OSP), then going to Distribution level and selecting outside processing, in Outside Processing window see that the LOV from the Job field has no value.
This is because no OSP resource was attached to the WO in EAM (Work Order => Operations => Resources)
see more in Document 412964.1
This is because no OSP resource was attached to the WO in EAM (Work Order => Operations => Resources)
see more in Document 412964.1
30. After receiving OSP item for last operation, completion transaction is not done automatically, Why?
This can be because Completion Subinventory was not set in the routing.
While receiving the PO, the system moves the quantities to the To Move intra operation step.
Since there is no Completion Subinventory mentioned, it cannot perform the Completion and it is up to the user to perform the completion to the required subinventory manually using Completion Transaction form. This was intended by development as a flexibility to complete into any subinventory user prefers.- see more in Document 743850.1
While receiving the PO, the system moves the quantities to the To Move intra operation step.
Since there is no Completion Subinventory mentioned, it cannot perform the Completion and it is up to the user to perform the completion to the required subinventory manually using Completion Transaction form. This was intended by development as a flexibility to complete into any subinventory user prefers.- see more in Document 743850.1
31. How to use outside processing functionality in a flow environment
In Discrete Manufacturing we generally attach the OSP resource in the routing so that once the assemblies are moved to the OSP operation the PO requisition is triggered.
In Flow Manufacturing we do not follow the same process as in Discrete but the same could be achieved as per workaround described in Document 732866.1.
In Flow Manufacturing we do not follow the same process as in Discrete but the same could be achieved as per workaround described in Document 732866.1.
32. How to generate PR/PO for two different vendors in the same WO
For a given Work order - operation combination, Items referenced should be unique. There is one way out however: You can split the non-stock material requirement in Purchasing module. This can be done in Purchasing by splitting Purchase Requisition quantities into two separate purchase orders ordered on separate vendors. In such a scenario, eAM will display the views of Material Requirement/PR/PO correctly in the Work order details page. (see Document 1296210.1)
33. Why PR/PO show NEED-By Date in the past?
For discrete and repetitive jobs, the need-by-date is the first unit start date of the operation, following the outside processing operation. If the outside processing operation is the last operation, then the need-by-date is the last unit complete date of that operation. This is the intended functionality. (Work in Process Users Guide, Chapter 11: Outside Processing, Section: Changing the need-by-date )
If the move transaction date is later than the next operation start date, the need-by-date will be a past date. (Even if Lead times functionality is used)
See solutions in Document 556661.1
34. Why Cost Relieved is NULL For OSP in WIP Value Summary Form
There are 3 possible causes for this issue:
1. The PO has been received, but qty not yet delivered to subinventory
2. The OSP resource transaction was not yet costed when WIP Assembly completion was done
3. The OSP cost was not included in the rolled assembly cost
For more details see Document 1318788.1
1. The PO has been received, but qty not yet delivered to subinventory
2. The OSP resource transaction was not yet costed when WIP Assembly completion was done
3. The OSP cost was not included in the rolled assembly cost
For more details see Document 1318788.1
35. Error <<You must define a deliver-to location for the PO Move/PO Receipt resource>> when creating EAM Work Order with OSP
Symptom:
When creating a maintenance work order for outside services in Oracle enterprise Asset Management. On Releasing our work order we are getting the below error message.
Error
You must define a deliver-to location for the PO Move/PO Receipt resource Cause: You tried to release a job with a PO Move/PO Receipt resource in one of the operations. For PO Move resource, the department of the next operation or, if this is the last operation, this operation, has no location. For PO Receipt resource, the department of this operation has no location. Action: Assign a location to the respective department in the Define Departments form. This will be used as the deliver-to location on the purchase order.
ORA-20001: in Package EAM_WO_CHANGE_STATUS_PVT Procedure change_status
Error
You must define a deliver-to location for the PO Move/PO Receipt resource Cause: You tried to release a job with a PO Move/PO Receipt resource in one of the operations. For PO Move resource, the department of the next operation or, if this is the last operation, this operation, has no location. For PO Receipt resource, the department of this operation has no location. Action: Assign a location to the respective department in the Define Departments form. This will be used as the deliver-to location on the purchase order.
ORA-20001: in Package EAM_WO_CHANGE_STATUS_PVT Procedure change_status
Solution:
Th error is misleading. In fact the cause is not about the Department Location, but it is the fact that user who created and released the work order (or the approver in case you are using work order release approver workflow) is not a valid employee.
Go to System Administrator > Security > Users > query for the user > change the Employee with a valid employee.
TECHNICAL TIPS:
For both cases, EAM or WIP, the preparer of the PR is the Employee who creates the Requisition. This is identified by the following (in order).
- PO_REQUISITIONS_INTERFACE_ALL.PREPARER_ID
- PO_REQUISITIONS_INTERFACE_ALL.PREPARER_NAME
- The user who submits the REQUISITION IMPORT concurrent request.
So, if the above said values are populated with correct employee id, then requisition import should be able to import (wipospvb.pls)
Notes about WIP - PO integration
- PO Created will have DESTINATION as SHOPFLOOR, LINE TYPE as OSP Line Type.
- PO RECEIPT of an OSP Item populates WIP_MOVE_TXN_INTERFACE and WIP_COST_TXN_INTERFACE tables independently.
Hence, if the cost manager alone is running and MOVE manager is Inactive, The JOB can be charged for the OSP receipt but MOVE might not happen.
- PO RECEIPT of an OSP Item populates WIP_MOVE_TXN_INTERFACE and WIP_COST_TXN_INTERFACE tables independently.
Hence, if the cost manager alone is running and MOVE manager is Inactive, The JOB can be charged for the OSP receipt but MOVE might not happen.
- PO Receipt of the OSP item - Does NOT charge the MATERIAL Element of JOB.
- PO Receipt of the OSP Item - Does charge the OSP Element of JOB at the Resource Rate.
- If OSP operation is the last operation in the Routing, then the deliver to location in the requisition will be the location assigned to the department for that outside processing operation. However, if the outside processing operation is not the last step in the Routing, then the deliver to location will be the location assigned to the department for the operation immediately following in the Routing.
- When outside processing items are returned to the shop floor they are returned to the queue step of the operation immediately following the outside processing operation, However if the outside processing operation is the last step in the Routing then the items are returned to the last step of the outside processing operation. Therefore, the deliver to location that gets populated in the requisition depends on where the outside processing operation exists in the Routing.
- If OSP operation is the last operation in the Routing, then the deliver to location in the requisition will be the location assigned to the department for that outside processing operation. However, if the outside processing operation is not the last step in the Routing, then the deliver to location will be the location assigned to the department for the operation immediately following in the Routing.
- When outside processing items are returned to the shop floor they are returned to the queue step of the operation immediately following the outside processing operation, However if the outside processing operation is the last step in the Routing then the items are returned to the last step of the outside processing operation. Therefore, the deliver to location that gets populated in the requisition depends on where the outside processing operation exists in the Routing.
- table PO_REQUISITIONS_INTERFACE_ALL - contains requisition information from other applications. Each row includes the information needed to create approved or
unapproved requisitions in Oracle Purchasing. Oracle Work in Process populates this interface when a User performs a Move into the Queue of an Outside Processing Operation.
- table CST_COST_ELEMENTS - It stores the cost element information. It is seeded with five cost elements: Material, Material Overhead, Resource, Outside Processing, and Overhead.
- table CST_RESOURCE_COSTS - It stores Resource and Outside Processing Resource unit costs (RESOURCE_RATE) by cost type.
unapproved requisitions in Oracle Purchasing. Oracle Work in Process populates this interface when a User performs a Move into the Queue of an Outside Processing Operation.
- table CST_COST_ELEMENTS - It stores the cost element information. It is seeded with five cost elements: Material, Material Overhead, Resource, Outside Processing, and Overhead.
- table CST_RESOURCE_COSTS - It stores Resource and Outside Processing Resource unit costs (RESOURCE_RATE) by cost type.
How OSP Requisition Need by date defaults
OSP Requisition need by date generates based on OSP item lead time setup.
OSP Items can be planned with Fixed & Variable lead times, asper this setup OSP Requisitions need by date varies.
Lets say OSP Item unit type is Assembly in item master
Now lets see how these Lead times would work..
Scenario-1 : Irrespective of OSP item quantity on OSP Requisition/po , vendor processing time must be 15 days
Setup :-
Fixed Lead time @ Org is 15,
Variable lead time setup as Zero
When requisition created for lets say 30 qty..rule will be applied like this
Need by date = Operation start time + [Fixed lead time + (Variable lead time * OSP Item qty)]
so Need by date = Op start time + 15 + (0*30) = OSP op start time + 15 days
Scenario-2 : Irrespective of OSP item quantity on OSP Requisition/po , vendor processing time must be as SETUP TIME 10 days & 2 days PROCESSING TIME per unit.
Setup :-
Fixed Lead time @ Org is 10,
Variable lead time setup as 2
When requisition created for lets say 20 qty..rule will be applied like this
Need by date = Operation start time + [Fixed lead time + (Variable lead time * OSP Item qty)]
so Need by date = Op start time + 10 + (2*20) = OSP op start time + 50 days
Hope this helps.
OSP Items can be planned with Fixed & Variable lead times, asper this setup OSP Requisitions need by date varies.
Lets say OSP Item unit type is Assembly in item master
Now lets see how these Lead times would work..
Scenario-1 : Irrespective of OSP item quantity on OSP Requisition/po , vendor processing time must be 15 days
Setup :-
Fixed Lead time @ Org is 15,
Variable lead time setup as Zero
When requisition created for lets say 30 qty..rule will be applied like this
Need by date = Operation start time + [Fixed lead time + (Variable lead time * OSP Item qty)]
so Need by date = Op start time + 15 + (0*30) = OSP op start time + 15 days
Scenario-2 : Irrespective of OSP item quantity on OSP Requisition/po , vendor processing time must be as SETUP TIME 10 days & 2 days PROCESSING TIME per unit.
Setup :-
Fixed Lead time @ Org is 10,
Variable lead time setup as 2
When requisition created for lets say 20 qty..rule will be applied like this
Need by date = Operation start time + [Fixed lead time + (Variable lead time * OSP Item qty)]
so Need by date = Op start time + 10 + (2*20) = OSP op start time + 50 days
How OSP Items Lead times works ?
OSP Items can be planned with Fixed & Variable lead times, asper this setup OSP Requisitions need by date varies.
Lets say OSP Item unit type is Assembly in item master
Now lets see how these Lead times would work..
Scenario-1 : Irrespective of OSP item quantity on OSP Requisition/po , vendor processing time must be 15 days
Setup :-
Fixed Lead time @ Org is 15,
Variable lead time setup as Zero
When requisition created for lets say 30 qty..rule will be applied like this
Need by date = Operation start time + [Fixed lead time + (Variable lead time * OSP Item qty)]
so Need by date = Op start time + 15 + (0*30) = OSP op start time + 15 days
Scenario-2 : Irrespective of OSP item quantity on OSP Requisition/po , vendor processing time must be as SETUP TIME 10 days & 2 days PROCESSING TIME per unit.
Setup :-
Fixed Lead time @ Org is 10,
Variable lead time setup as 2
When requisition created for lets say 20 qty..rule will be applied like this
Need by date = Operation start time + [Fixed lead time + (Variable lead time * OSP Item qty)]
so Need by date = Op start time + 10 + (2*20) = OSP op start time + 50 days
Hope this helps.
Lets say OSP Item unit type is Assembly in item master
Now lets see how these Lead times would work..
Scenario-1 : Irrespective of OSP item quantity on OSP Requisition/po , vendor processing time must be 15 days
Setup :-
Fixed Lead time @ Org is 15,
Variable lead time setup as Zero
When requisition created for lets say 30 qty..rule will be applied like this
Need by date = Operation start time + [Fixed lead time + (Variable lead time * OSP Item qty)]
so Need by date = Op start time + 15 + (0*30) = OSP op start time + 15 days
Scenario-2 : Irrespective of OSP item quantity on OSP Requisition/po , vendor processing time must be as SETUP TIME 10 days & 2 days PROCESSING TIME per unit.
Setup :-
Fixed Lead time @ Org is 10,
Variable lead time setup as 2
When requisition created for lets say 20 qty..rule will be applied like this
Need by date = Operation start time + [Fixed lead time + (Variable lead time * OSP Item qty)]
so Need by date = Op start time + 10 + (2*20) = OSP op start time + 50 days
How to Plan or forecast OSP item demand in Oracle ?
Oracle OSP items are Work in Process driven, hence there is no direct demand can be seen from ASCP.
Its always challenging task to Buyers to establish Pricing for Parts / services sourcing from vendors. All regular parts demand can be driven from ASCP / Inventory Planning but OSP Parts demand needs to be established from Parent items.
Solution Approach :
So to meet this requirement, we created one report to capture all Planned orders thats been generated for Parent items. This Planned Order report gives the visibility on Future requirements of parent item.
This list gives indirectly Future demand requirements for OSP items.
When Buyer establishing the pricing for OSP Item/services, share this info (tsp demand requirements) to vendors thru RFQ. Vendor plans accordingly his capacity & ensure onetime deliveries.
I have taken the above approach, that fulfilled business requirement. If you have any thought/ made any development, pls share. Appreciate your inputs.
Why OSP Requisition not generated ?
Why Oracle OSP Requisition not generated ?
Following are possible causes which needs to be ensured and validated.
Following are possible causes which needs to be ensured and validated.
- There is no List Price defined for the OSP item in the Item Master.
- List price defined must be greater than Zero..example: 0.01
- OSP Resource Charge type is not set as PO Move / PO Receipt.
- Check for WIP Parameters setup for Requisition release time
- OSP item is not linked to the OSP resource.
- OSP resource is not linked to the OSP operation.
- There is no Location defined for the Department for which the OSP resource is linked.
- When the quantity involved for OSP is large. you see no requisitions being created for the quantity (Cause: Organization calender does not have a long period defined. This is an issue when the item has a large lead time and for WIP to schedule large OSP quantities according to their lead time may exceed the calender defined for the organization.)
Above are from various learnings and personal experience. All above are standard causes, if still all these are appearing correct and requisition did not generate, i suggest log SR with oracle.
Subscribe to:
Posts (Atom)