1Z0-517 practice question 22 of 25

Company Z has implemented Payables, General Ledger, and Project Accounting. Both Transfer to GL and Interface Supplier Costs are processed each…

Company Z has implemented Payables, General Ledger, and Project Accounting. Both Transfer to GL and Interface Supplier Costs are processed each night. A descriptive flexfield called “SAI Value” has been defined on the invoice header to capture additional information, and is used in conjunction with the accounting on the invoices. This is not a required field. There is a corresponding user-defined hold called “SAI Hold”, which is manually applied whenever an invoice is created and the “SAI Value” has not been provided to Company Z by the supplier. During weekly reviews of accounting, users have found that invoice transactions that are on “SAI Hold” are displayed in Project Accounting but not in General Ledger. Select what is causing this issue.

Answer options

A: Invoices have not been validated.

B: The current General Ledger period is closed.

C: The current Project Accounting period is closed.

D: The Payables Accounting process has not been run.

E: Accounting is not being created by the user-defined hold. Correct answer

F: The descriptive flexfield field must be a required field, and not an optional field.

Correct Answer:

E. Accounting is not being created by the user-defined hold.

Explanation

In Oracle Payables, user-defined holds are configured in the Hold and Release Names window, which includes an "Accounting Allowed" checkbox. If this option is disabled for the "SAI Hold," the system explicitly prevents the Create Accounting process from generating subledger accounting entries for any invoice placed on this hold. Because no accounting entries exist in the Subledger Accounting (SLA) tables for these specific invoices, the nightly "Transfer to GL" process has no journal data to transfer. This perfectly isolates the issue to the invoices on the "SAI Hold," explaining why they are missing from the General Ledger despite the nightly transfer processes running successfully for other transactions.

Why Incorrect

A. If the invoices had not been validated, they would not have been successfully picked up by the Interface Supplier Costs process and would not appear in Project Accounting.
B. A closed General Ledger period would cause the GL transfer to fail or require a sweep for all unaccounted invoices, not just those specifically placed on the "SAI Hold."
C. A closed Project Accounting period would only impact the interfacing of costs into the Projects module; it has no bearing on the Payables to General Ledger transfer.
D. The scenario explicitly states that the Transfer to GL process is processed each night. If it simply hadn't run, all recent invoices would be missing from GL, not just the held ones.
F. Making the descriptive flexfield a required field would only prevent users from saving the invoice initially; it does not explain the downstream accounting and GL transfer discrepancy for existing invoices.

References

1. Oracle Payables Implementation Guide, Release 12.1, Part No. E12796-02. Chapter 2: Payables Setup, "Hold and Release Names," p. 2-105. (Details the "Accounting Allowed" checkbox and its impact on subledger accounting generation).

2. Oracle Payables User's Guide, Release 12.1, Part No. E12797-02. Chapter 5: Invoices, "Applying Holds," p. 5-112 to 5-114. (Explains the functional behavior of user-defined holds on invoice processing and accounting).

3. Oracle Project Costing User Guide, Release 12.1, Part No. E13581-02. Chapter 7: Integrating with Other Oracle Applications, "Integrating with Oracle Payables," p. 7-21. (Details the prerequisites for the Interface Supplier Costs process).

Keep practicing

Take the free 1Z0-517 practice test

Ten exam-style questions with answers and explanations, plus the exam facts and study guides.

Start the free practice test