Symptom
Using the Migration Cockpit (APP Migrate your Data) 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 Public Edition
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 the external numbering defined in the upload file is expected to be used, external numbering specifically in the migration tool should be chosen, via Control Parameter 'Purchase Orders, internal or external numbering (00002)
*Note: Even if the external numbering is intended to be used only for migrated purchase orders, both an internal and external number range must be defined 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-2CL , BAPIs - Purchase order (Public Cloud) , CA-GTF-MIG , SAP S/4HANA Data Migration Cockpit Content , How To
SAP Knowledge Base Article - Public