SAP Knowledge Base Article - Public

3070856 - PO migration creating PO's using an external numbering

Symptom

Using the Migration Cockpit (APP Migrate your Data) you would like to create Purchase Orders with an external number range but the system always uses the internal number range assigned to the Purchase Order document type.  

Environment

SAP S/4Hana Cloud - All Versions

Reproducing the Issue

Open the App “Migrate Your Data”.
Choose or create a new migration project
Choose the migration object “Purchase Order (Only Open PO)”.
Upload the desired file, confirm the mapping and 'Simulate. 

Cause

In the migration tool the default numbering is internal. 

Resolution

If you want to use the external numbering defined in your upload file, you have to choose external numbering specifically in the migration tool, via Control Parameter 'Purchase Orders, internal or external numbering (00002)

*Note: Even if you intend to use external numbering only for migrated purchase orders, you must define both an internal and external number range for the document type involved if it is not a standard PO type.    

See Also

BAPI_PO_CREATE1, exs_poheader-ebeln, FMMEXE01_PRUEFEN_NUMMER, MAP2I_BAPIHEADER_TO_HEADER, ekko-ebeln, NUMBER_CHECK, t161-numke 

Keywords

KBA , MM-PUR-PO-BAPI , BAPIs - Purchase order , CA-GTF-MIG , SAP S/4HANA Data Migration Cockpit Content , How To

Product

SAP S/4HANA Cloud Public Edition all versions ; SAP S/4HANA Cloud all versions