3630644 - Missing Dunning related fields in migration object 'FI - accounts receivable open item' template

Fields like 'Dunning Level' and 'Last Dunned' are missing from migration object 'FI - Accounts receivable open item' template.

SAP S/4HANA Cloud Public Edition

1. Open the Migration Cockpit app
2. Create or select a migration project containing the 'FI - Accounts receivable open item' migration object
3. Download the XML or CSV template file
4. Search for Dunning related fields

The underlying API (DMC_MIG_ACC_DOCUMENT_POST) of migration object 'FI - Accounts receivable open item', currently doesn't support the mentioned Fields 'Last Dunned' or 'Dunning Level'.

• Consult SAP Note 2999428 to find out which additional standard fields (if any) are offered by your desired migration object.
• At SAP Online Help documentation about available migration objects, check whether or not the desired migration object supports custom fields via key user extensibility. In case it does, follow the "Custom Fields" section, within the MO's documentation on how to implement this.
• Post-Migration Dunning Run (Recommended and Most Standard Approach): This is the most common and SAP-recommended approach for managing dunning after a migration.
• Configure Dunning in SAP S/4HANA Cloud Public Edition: Before migrating, ensure the dunning procedures (transaction FBMP in traditional SAP, or the equivalent Fiori apps for configuration) are fully set up in the SAP S/4HANA Cloud Public Edition system. This includes defining dunning levels, dunning intervals, grace periods, charges, and dunning texts.
• Migrate Open Items Without Dunning Data: Proceed with the migration of the 'FI - Accounts receivable open item' using the standard template, leaving the dunning-related fields blank (as they won't be available).
• Execute Initial Dunning Run: After all open items are successfully migrated, perform a full dunning run in the SAP S/4HANA Cloud Public Edition system (using Fiori App "Create Dunning Notices" / transaction F150). This will evaluate all open items based on their due dates and the configured dunning procedures and automatically assign the correct 'Dunning Level' and update 'Last Dunned' for each relevant open item. This process ensures data integrity and consistency with the new system's dunning logic.
• Consider "Always Dun": In the dunning configuration, it is possible to set the "Always Dun?" flag at the dunning level if a dunning notice is required to be printed even if no change has been made to the dunning proposal since the last dunning run. This might be relevant for the initial run to ensure all overdue items are processed as expected.

• Refer to: 2515151 - SAP S/4HANA Migration Cockpit: Migration objects or fields which you want to migrate cannot be found - SAP for Me
• Refer to: Add dunning level in Migration Template - open items accounts receivable
• Refer to: 2999428 - Collective Note for extensions via Model Your Migration Objects - Migration Object Modeler App in SA

missing fields, FI accounts receivable open item, migration object, SAP S/4HANA Cloud Public Edition, dunning data, API support, custom fields, standard fields, feature request, post-migration dunning run, SAP Note 2999428, SAP Note 2515151, dunning level, DMC_MIG_ACC_DOCUMENT_POST, Last Dunned , KBA , CA-GTF-MIG , SAP S/4HANA Data Migration Cockpit Content , Problem