Display approved PR lines in Release approved purchase requisitions even if Purchase requisition header status remains In Review in D365 F&O

(0) Share

Report

Posted on by Rhushikesh R

758

Hi Everyone,

If we navigate to below path on the dashboard,

Procurement and sourcing > Purchase requisitions > Approved purchase requisition processing > Release approved purchase requisitions

a List page gets opened which shows all the Purchase requisition lines which have been Approved through workflow.

The observation here is, when we have Purchase Requisition line workflow activated and if we have one Purchase requisition which has multiple lines, then until and unless we don't approve all PR lines, none of the lines get displayed in the Release approved purchase requisitions

My client has requirement as below,

Whatever approved lines are there from the multiple lines, even though PR header status remains In Review, the approved lines should be displayed on Release approved purchase requisitions.

I observed form at the backend and found one query called PurchReqCreatePurch added into the form.

Is it feasible to achieve the requirement mentioned above? If yes, can anyone please suggest an approach needs to be follow?

All responses (3)

Answers (2)

Sort by

Verified answer

Rhushikesh R 758 on at

Like (1)

Report
Copy link

Link copied!
Well, I found one similar thread and the requirement is something which should not be taken as a customization.

community.dynamics.com/.../how-to-add-purchase-requisition-lines-in-released-approved-purchase-requisitions-by-approving-in-one-line-and-not-all-the-lines

Also below is my observation,

Business requirement:

Though purchase requisition (PR) header status remains ‘In review’, approved purchase requisition lines should be available in Procurement and sourcing > Purchase requisitions > Approved purchase requisition processing > Release approved purchase requisitions for creating new purchase orders.

Observations:

Release approved purchase requisitions form does not filter the PR lines based on header status but based on below fields of PR line,

RequisitionStatus (must be Approved)

IsPreEncumbranceRequired (must not be Unknown)

RequisitionPurpose (must be Consumption)

IsPreEncumbranceRequired flag gets set to Yes or No from default Unknown value during execution of Budget fund reservation process.

Additionally, it looks for linked records into Budget source table (Field: Check result) and Source document line table (Field: Source document line status)

Until Source document line status does not change to Completed or Finalized, the record won’t appear in Release approved purchase requisitions.

When individual PR line has been approved, the standard logic does not run any logic related to Budget fund reservation.

The logic to run budget fund reservation only gets triggered when all lines have been approved and workflow gets completed for the PR record.

The standard classes being used for budget fund reservation process uses the input as Purchase requisition header and updates the all source document lines (changes Source document line status field value to Completed or Finalized) and IsPreEncumbranceRequired field(set to Yes/No from Unknown) for all purchase requisition lines.

Conclusion:

Updating the fields individually for source document lines after each line approval is not possible because of the standard hierarchy of classes.

Also, if we just update the fields from individual table related to each line, without using standard classes of budget fund reservation, after each line approval, may result into inconsistencies and can cause Budgeting issues.

Hence, the requirement stands to be not feasible from technical perspective and should be avoided.

Classes gets triggered: PurchReqPreEncumber
Table method: PurchReqTable.recordBudgetFundReservation()
Verified answer

huijij 19,813 on at

Like (0)

Report
Copy link

Link copied!

Thanks for your sharing.
ThangNguyen 184 on at

Like (0)

Report
Copy link

Link copied!

Very helpful. Thank you very much, Rhushikesh