PAXTRAPE: Contingent Worker Accrue on Receipt Purchase Orders Not Associated With an Employee Show an Employee in the 'Employee/Supplier' Field in the Expenditure Inquiry Form.
(Doc ID 2985759.1)
Last updated on DECEMBER 12, 2023
Applies to:Oracle Project Costing - Version 12.2.10 and later
Information in this document applies to any platform.
The customer is reviewing expenditure items in the Expenditure Inquiry| All form. Contingent Worker expenditures associated with Purchasing (PO) Receipts show an Employee in the field 'Employee/Supplier' when there is NO employee associated with the PO. Expected functionality would be for POs that are NOT employee related to show the Supplier versus the Employee in this field. It is very confusing to users when the PO that has no employee appears in the Expenditure Inquiry showing one.
Steps to Reproduce:
1. 11i and R12 - What Is The Contingent Worker Flow? (Doc ID 1558513.1) - Setup Sharon Stone as a Projects Contingent Worker.
2. How to Add PO_CWK_ASSOCIATIONS Function to Taskflow for Purchase Order to the PO CWK Association Page (Doc ID 1141005.1) to add the "Associate Purchase Order With Contingent Worker" page.
3. Create a rate based PO for 'Sharon Stone'. Be sure she is the only employee associated with supplier 'United Parcel Service'.
4. Add this PO to her HR assignment using the 'PO CWK Association Page' added above.
5. Go back into Purchasing (accrue on receipt) and create a PO using the supplier 'United Parcel Service'. This time give it a project 'Work/Work'. Approve and prepare the receipt to come to PA.
6. Bring receipt into PA using PRC: Interface Supplier Cost for project 'Work/Work'.
7. Note the Expenditure item brought in, shows 'Sharon Stone' as the 'Employee/Supplier' but this PO had no employee. It only had a Supplier.
In the steps to reproduce above, user details / company name / address / email / telephone number represent a fictitious sample (based upon made up data used in the Oracle Demo Vision instance).
Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document