PAIGEN: PRC: Generate Draft Invoice for a Range of Projects Not Finding Projects Because of the Billing Cycle. How Can a Billing Cycle Be Setup to Not Require the Use of the Client Extension? (Doc ID 3062173.1)

Oracle Project Billing User Guide

https://docs.oracle.com/cd/E26401_01/doc.122/e49079/T178714T178721.htm#2299411

Selection Criteria

Projects: Oracle Projects first determines if a project is eligible for invoice generation using the following criteria:

Must be a contract project

Must have a status that allows invoice generation. For more information, see: Project Statuses, Oracle Projects Implementation Guide.

Must have a baseline budget and funding

Must have expenditure items or events that are eligible for invoice generation or transaction-independent billing extensions that are assigned at the project type, project, or top task level

If you submit the process for all projects, it checks the eligibility of each project to bill according to its billing cycle. A project must meet the following billing cycle criteria before it can generate an invoice:

Must not have any pending invoices (Unreleased)

At least one bill cycle past the bill through date (or creation date if no bill through date exists) of the last non-crediting invoice

At least first bill offset days past the project start date (or project creation date if no start date exists) if you have not yet invoiced a particular project

If the billing date is calculated by a client extension, and the client extension returns a null value for the billing date, then the process will not pick up the project.

To generate retention invoices, the project must be eligible to bill retention.

When submitted for a single project, the Generate Draft Invoices process ignores billing cycle. Also, if you have any unreleased draft invoices, they are deleted and a new draft invoice is created.