Requisition confirmed turns into a Purchase Order; where does the PO order date come from?

(0) Share

Report

Posted on by Ian Waring

436

We have a workflow where a requisition submitted to workflow aims out to Power Automate, which gets approval and then confirms its conversion into a purchase order.

Today (17th March 2021), we created a brand new requisition. Got it approved. Requisition confirmed and PO duly generated - but with different dates output to SSRS. The PO delivery date is set correctly to 17th March 2021, but the PO date in the PO header is set to 18th December 2020 (btw, in the example XML generated, the dates are UK way around - dd/mm/yyyy).

Looking at the req, Requested Date, Accounting date, Created Date, Modified Date, Submitted Date are all 17/03/2021. Similarly line Requested Date, Accounting Date both 17/03/2021

On the resulting PO:

<Field_DeliveryDate>17/03/2021</Field_DeliveryDate>

but

<Field_PurchOrderDate>18/12/2020</Field_PurchOrderDate>

Any idea where the 18th December 2020 date could be coming from?

Ian W.

I have the same question (0)

All responses (5)

Answers (1)

Sort by

Ian Waring 436 on at

Like (0)

Report
Copy link

Link copied!

FWIW, we're seeing:

<Field_PurchaseOrderId>PC003155</Field_PurchaseOrderId>

<Field_PurchId>PO1000192</Field_PurchId>

<Field_PurchOrderDate>18/12/2020</Field_PurchOrderDate>

<Field_PurchOrderDocNum>PO1000192-1</Field_PurchOrderDocNum>

Where the PO generated is PO1000192 - but we don't know where PC003155 nor 18/12/2020 are coming from....

Was this reply helpful? Yes No
Ian Waring 436 on at

Like (0)

Report
Copy link

Link copied!

The next PO generated:

It’s almost like it’s a Req to PO Creation number sequence – incrementing but using the same date of 18/12/2020.

<Field_PurchaseOrderId>PC003156</Field_PurchaseOrderId>

<Field_PurchId>PO1000193</Field_PurchId>

<Field_PurchOrderDate>18/12/2020</Field_PurchOrderDate>

<Field_PurchOrderDocNum>PO1000193-1</Field_PurchOrderDocNum>

<Field_ReqAttention />

Any ideas how to leave that off so the correct PO number and PO date gets used instead?

Ian W.

Was this reply helpful? Yes No
Allen Dejoux Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!

It maybe easier to take a trace and analyze to determine where the data is being pulled from, this may be a set up/mapping issue.

Was this reply helpful? Yes No
Verified answer

Ian Waring 436 on at

Like (0)

Report
Copy link

Link copied!

Hiya,

The issue was date value text being embedded in the purchase order date field in a customised purchase order SSRS template. Hence the mystery of why that date got put into every PO run off on our Production system (but not on an identical configuration on our staging server). All fixed now.

Ian W.

Was this reply helpful? Yes No
André Arnaud de Cal... 304,688 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi Ian,

Thanks for providing your update with the resolution and confirmation it is working correctly now. I have marked your reply to set the status of this question to answered.

Was this reply helpful? Yes No