Purchase order number sequence - manual and automatic

(0) Share

Report

Posted on by Conswello

The customer has a 3rd party manufacturing / inventory software solution where POs originate and will be interfaced into D365 so the PO number sequence needs to the manual in D365 for this scenario...but all non-inventory POs will originate in D365 so these PO number sequences need to be automatically created in D365. Is there a setup in D365 to accomplish this dual PO number sequence requirement? There have been rumors that Microsoft is considering a feature to 'extend' the number sequence functionality but I could not find anything in the current version of D365.

Assistance, insights, suggestions and/or ideas would be greatly appreciated!

I have the same question (0)

All responses (6)

Answers (2)

Verified answer

André Arnaud de Cal... 299,056 Super User 2025 Season 2 on at

Like (0)

Report

RE: Purchase order number sequence - manual and automatic

Hi Conswello,

You can actually have the number sequence setup automatic. When importing the purchase orders from another system, you can define your own PO number and in this way bypass the Dynamics 365 business logic to generate a new number.

You only have to ensure that your automatic numbering will not have an overlap with the PO from the 3rd party software.

Was this reply helpful? Yes No
Conswello 5 on at

Like (0)

Report

RE: Purchase order number sequence - manual and automatic

Thanks...that is perfect!

Was this reply helpful? Yes No
Conswello 5 on at

Like (0)

Report

RE: Purchase order number sequence - manual and automatic

I ran some tests on this concept using data management...but was not able to achieve success. Any add'l thoughts?

PO number sequence setup: Constant = PO / Alphanumeric = ######## (8); Next number = 254; Manual = No & Continuous = No

Scenario 1: . Import file PO number = PO99999990. Error: Number sequence PO_NUM does not allow change to a higher number.

Scenario 2: . Import file PO number = PO1. Error: Number PO1 does not match format PO########.

Scenario 3: . Import file PO number = BC1. Error: Number BC1 does not match format PO########.

Was this reply helpful? Yes No
Verified answer

Satish Panwar 14,671 Moderator on at

Like (0)

Report

RE: Purchase order number sequence - manual and automatic

Hi Conswello,

You need to make sure the options under 'Allow user changes' are marked. What this does is allow you to enter a different PO number that exists outside the series. The catch is that it has to match in length but you can use a different sequence.

This also open up user to change the PO number on the AX UI.. but that can be left as is and you should be good. Give this a try.

My regular PO number

Once option set as above, then PO can be updated.

Was this reply helpful? Yes No
Conswello 5 on at

Like (3)

Report

RE: Purchase order number sequence - manual and automatic

I successfully tested...so to use this approach, this appears to be how the whole process would flow...

This PO number issue becomes an issue if one is importing a unique PO number from a 3rd party system and also is generating different unique PO numbers in D365.

PO number sequence setup:

1> Should be alphanumeric only; no constants or other added segments; only max characters of 9 were allowed.

2> Under the Fast tab: General - Manual = No; Continuous = No and Allow user changes-to a lower & higher number = both Yes.

3> Suggest the number sequence smallest set 100000000 and largest 999999999...D365 will use this number sequence setup for the PO numbers generated in D365. (I hate leading zeros if you start at 1.)

4> Suggest the imported PO numbers begin with a leading 'alpha' F00000001...to ensure that your automatic numbering does not overlap with the PO from the 3rd party software. Also the max of 9 characters is still validated.

Thanks for pointing in the right direction.

Was this reply helpful? Yes No
Conswello 5 on at

Like (0)

Report

RE: Purchase order number sequence - manual and automatic

Perfecto...thanks!

Was this reply helpful? Yes No