Comprehensive and Detailed In-Depth Explanation:
In Oracle Financials Cloud, even when an installment meets the selection criteria of a Payment Process Request (PPR), certain conditions can prevent it from being selected for payment processing. Understanding these conditions is crucial for troubleshooting and ensuring a smooth payment workflow.
Analysis of Each Option:
A . The pay-through date is in a future period.
B . The pay-through date is in a closed Payables period.
C . The invoice needs re-validation.
docs.oracle.com
D . The invoice requires approval.
docs.oracle.com
E . The invoice has not been accounted.
Conclusion:
The two primary reasons an installment, despite meeting selection criteria, might not be selected for payment processing are:
C . The invoice needs re-validation.
D . The invoice requires approval.
Ensuring that all invoices are validated and approved is essential for their inclusion in payment processing.
Reference:
Oracle Financials Cloud Documentation - Why didn't an installment get selected for payment?
https://docs.oracle.com/en/cloud/saas/financials/24d/fappp/why-didn-t-an-installment-get-selected-for-payment.html Oracle Financials Cloud Documentation - Why didn't an installment get selected for payment?
https://docs.oracle.com/en/cloud/saas/financials/24d/fappp/why-didn-t-an-installment-get-selected-for-payment.html

Comprehensive and Detailed In-Depth Explanation:
Closing a Payables period in Oracle Financials Cloud requires that all transactions for the period are fully processed and accounted for. The system enforces certain checks to ensure data integrity and accurate financial reporting. The following are valid reasons that can prevent the closure of a Payables period:
Incomplete Payment Files (Option B):
Suppliers on Payment Holds (Option E):
In summary, to successfully close a Payables period, ensure that all payment files are complete, bills payable are matured and accounted for, and all invoices and payments are fully processed and posted.
Reference:
Bills Payable Requiring Maturity (Option C):
Unaccounted Invoices and Payments (Option D):
Options A and E are not valid reasons for preventing period closure:
Unapplied Prepayments (Option A):

Comprehensive and Detailed In-Depth Explanation:
In Oracle Financials Cloud, the Match in Full feature allows users to create invoices by matching the full amount of a purchase order (PO) efficiently. However, certain conditions can prevent a PO from appearing in the Match in Full search results.
Analysis of Each Option:
A . The match approval level is set to 4-way matching
B . The Supplier or Purchase Order is set up for self-billing
docs.oracle.com
Therefore, if the supplier or PO is configured for self-billing, the PO will not appear in the Match in Full search results.
C . The match approval level is set to 3-way matching
D . The Purchase Order is already partially matched to an invoice
docs.oracle.com
Therefore, a PO that has been partially matched will not appear in the Match in Full search results.
Conclusion:
The two reasons preventing the purchase order from appearing in the Match in Full search results are:
B . The Supplier or Purchase Order is set up for self-billing
D . The Purchase Order is already partially matched to an invoice
These conditions make the Match in Full feature inapplicable, thereby excluding the PO from the search results.
Reference:
Oracle Financials Cloud Documentation - Overview of Creating Invoices Using Match in Full
https://docs.oracle.com/en/cloud/saas/financials/24b/fappp/overview-of-creating-invoices-using-match-in-full.html Oracle Financials Cloud Documentation - Overview of Creating Invoices Using Match in Full
https://docs.oracle.com/en/cloud/saas/financials/24b/fappp/overview-of-creating-invoices-using-match-in-full.html