Import of Purchase order headers failed with error message Number sequence does not allow change to a lower number

(0) Share

Report

Posted on by pli

We are using the Data Management framework. here are what we did:

Via Data Management Export, date for Purchase Order Headers are saved
now the record is lost ( in testing, we just deleted the record at the front end GUI)
use the data exported at step 2 to constructed a Data Management Import package
import is failed with error message:
Results. Field 'Purchase order' does not allow editing.

Results. Invalid specification of Purchase order

Results. Number sequence Purc_102 does not allow change to a lower number.

Results. Validations failed

here is the screen shot:

One thing we found out that if we allow to "a lower number" for that particular NumberSeq, we would be able to import successfully. Since this is backup data, it seems reasonable to allow at least temporally during import. One thing is how to modify this via X++ code. Could we do the following:

find all the NumberSeq on the current Entity (or all tables for current entity?)
then modify the AllowChangeDown (https://technet.microsoft.com/en-us/systemcenter/numbersequencetable(v=ax.50)) to allow importing and then restore the setting.

Just wonder if there are any sample codes around any of this. I did some search over internet and did find various ways to get the NumberSeq (not sure if we could enumerate all the NumberSeq on a table or entity or not) although didn't see a method to set AllowChangeDown.

Thanks very much and any insights are really appreciated.

Categories:

Data Integration

Development / Customization / SDK

Other

I have the same question (0)

All responses (5)

Answers (1)

Community Member on at

Like (0)

Report
Copy link

Link copied!

Hello pli,

Did you success for importation ? I've found this issue with the same error log. Could you share me how to solve this ?

Was this reply helpful? Yes No
Paul Sinnott 90 User Group Leader on at

Like (0)

Report
Copy link

Link copied!

Could you add a bit more information as to the background of this export/import? Why are you looking to reimport data if it has been deleted? Is this testing data that you are trying to recreate?

I would advise against regularly changing the parameters of the number sequences, but depending on why this is being done and where (e.g. sandbox) it may make sense.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Hello Paul,

I'm trying to migrate opening purchase orders from old environment (PROD) to new environment (DEV). The PO number sequence has the same format, so I don't understand the issue as it notice

Results. Field 'Purchase order' does not allow editing. - What should I do ?

Results. Invalid specification of Purchase order - Which field has invalid specification ?

Results. Number sequence PS-PO does not allow change to a higher number. - What is the reason about this infolog ?

Was this reply helpful? Yes No
Verified answer

Paul Sinnott 90 User Group Leader on at

Like (0)

Report
Copy link

Link copied!

Hi Asba,

It looks as though all your issues are related to you number sequence here, which is not a problem, we just need to setup the import to allow you to achieve what you want. I believe you have 2 options:

If you are simply recreating transactions for your dev environment then you could set the PO number to auto-generate on import in your DMF mapping e.g. see below:

Doing this method. however, would require a bit more work when it comes to importing the PO lines as you would need to map the lines to the headers in your source document before import so I'm guessing this wouldn't work for you.

If you are wanting to maintain the numbering of the POs then you need to amend your purchase order number sequence to set it as 'manual' during the import.

You can then change it back and update the 'next' number to maintain the integrity going forward.

Hope this helps

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Hello Paul,

I have done as you suggested. It's worked, thank you.

Was this reply helpful? Yes No