E1: 53: Invalid Account Selection Error - Billing Commit Xref
(Doc ID 2758278.1)
Last updated on MARCH 05, 2021
Applies to:JD Edwards EnterpriseOne Project Costing - Version 9.2 and later
Information in this document applies to any platform.
When performing multiple Billing Commits for Unit Type Change Requests, the user is unable to perform the commit after the initial record has been committed. The root cause appears to be related to the creation of the x-ref record, although the Processing option for P5310 is set to not create the x-ref record. Only once the initial record is committed, and the user navigates to the Billing Line to remove the x-ref, can they commit the next change request record.
Upon testing, it was identified that the issue is specific to Unit Type Billing / Pricing Lines. A lump Sum Type Change Request will not create ax-ref record.
It was identified that the issue is specific to Unit Type Billing / Pricing Lines. A lump Sum Type Change Request will not create a x-ref record. The Billing Commit process should be corrected to not create the x-ref based on the Processing Options setting within P5310. As of note: it appears that the validation is being based on the Billing Change Order Number, and xref record. Assign the Change Request against a separate Billing Change Order 3, it will allow the user to perform the commit.
1. Set the PO on the P310 so that it should NOT Update the Cross Reference:
2. Review the BC AAIs: Added Company # 00050
3. Company Names and Numbers:
4. Create a Job
5. Add the Revenue Accounts:c
6. Create a Contract using the P5201: Contract # will update. i.e. 474
7. Add some Contract Billing Lines:
8. Enter a Change Request against the Contract using the P5310:
9. Enter a SECOND Change Request against the Contract using the P5310:
10. Commit the first line:
11. Then go back to the detail lines and review that it has been cross referenced:
12. Commit the second line: (See Step # 10)
13. See Error Message:
14. Delete the First Line that was Cross Referenced. Works again to Commit.
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