3791134 - Debit Memo Manual Request Always Results in the Creation of an Invoice as the Follow-up Document Instead of a Debit Memo - SAP S/4HANA Cloud Public Edition

In the Project Billing scenario, a manually created Debit Memo Manual Request always results in the creation of an Invoice as the follow-up document.

 SAP S/4HANA Cloud Public Edition

1. Go to the eDocument Cockpit app.
2. In the Source Document field, enter ABC (where ABC represents the Source Document ID).
3. Open the Source Document ABC.

The eDocument is displayed as an Invoice.

Specifically, within Project Billing, whenever a Debit Memo Manual Request (DRM4) is created, the system generates an Invoice as the follow-up document. In contrast, in standard sales scenarios, a Debit Memo Request (DR) typically results in the creation of a Debit Memo as the follow-up document.

According to the DIANs requirement, a Debit Memo Manual Request should generate a Debit Memo instead of a Invoice Document in a Project Billing scenario.

In this scenario, Debit Memo Requests with type 'DR' should be used, despite the scope item of Project Billing requests to use the type 'DRM4'.

Refer to the Scope Item 1F1 (Debit Memo Processing (1F1) – Scope Item Process Description) as reference.

SAP Documentation: Debit Memo Processing (1F1) – Scope Item Process Description
SAP Help Portal: Colombia

edocument cockpit, colombia, debit note, debit memo, project billing, dmr4, ci01, shows as invoice, type description, l2, dr, copy control, flexible formulas, dian compliance , KBA , CA-GTF-CSC-EDO-CO , Colombia , Problem