Description

Currently, when using the Get Order Line function on Purchase Invoices for G/L Account purchase lines, the system does not transfer project-related fields such as: Project No., Project Task No., Project Line Type from the source Purchase Order to the Purchase Invoice.

This behavior leads to inconsistencies, as users are unable to post the Purchase Invoice without manually re-entering these values, even when the source Purchase Order line already contains the required project information.

Business Impact

- Prevents users from posting Purchase Invoices directly after using Get Order Line, due to missing mandatory project fields.

- The system also does not allow users to manually enter or correct these project fields after retrieval, leaving the invoice incomplete and blocking the posting process entirely.

- Requires manual re-keying of invoice lines, significantly increasing the risk of data inconsistency and human error.

- Creates operational inefficiencies, especially for organizations heavily relying on project/job-based purchasing workflows, where accurate project data propagation is critical.

- Forces users to adopt an alternative process (posting the receipt first and using Get Receipt Lines), which deviates from the intended or preferred business workflow and may not be suitable for all operational scenarios.

Expected Behavior

When users run Get Order Line on a Purchase Invoice:

The system should copy all relevant data from the Purchase Order line, including project-related fields (Project No., Project Task No., Project Line Type), similar to how other fields (e.g., dimensions, quantities, costs) are transferred.

Current Workaround

To proceed with invoice processing, users must follow an alternative process:

1. Open the Purchase Order and post the receipt first.

2. From the Purchase Invoice, use the Get Receipt Lines function instead of Get Order Line.

3. Retrieve the lines from the posted receipt.

4. Validate totals and proceed with posting.

While this workaround allows processing to continue, it introduces additional steps and does not align with the expected or intended workflow when using Get Order Line.

Additional Context

This scenario is particularly important for customers integrating purchasing with project/job tracking, where accurate and consistent propagation of project-related data across documents is critical.