Last updated on DECEMBER 20, 2016
Applies to:Oracle iProcurement - Version 11.5.10 to 12.2.4 [Release 11.5 to 12.2]
Information in this document applies to any platform.
Requisition charge account defaults to the employee default favorite charge account in iProcurement rather than to a project based charge account. The charge account defaults correctly in Core Applications Purchasing to the project based charge account using the logic in the customized
account generator workflow, but does not default correctly in iProcurement based on the project details entered.
Steps To Reproduce
1. Implement customizations in requisition account generator workflow to default charge accounts based on project details entered.
2. Create a project based requisition in Core Apps Purchasing and verify that the charge account is generated based on the customized account generator logic.
3. Create a project based requisition including Descriptive Flex Field on split account in iProcurement and observe that the charge account is not generated on the split accounts based on the customized account generator logic. Instead, the iProcurement charge account defaults from the employee preferences, default favorite charge account.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms