Interfaces IF_EDOC_SOURCE_EXTENSION & IF_EDOC_SOURCE_PROCESS_EXT for DRC in SAP Public Cloud

[Vynerfes]

Objective:

To manually create eDocument for CLM invoices in eDocument Cockpit as it’s not supported, and Relevant indicator is set to false. Therefore, we want to manipulate the Relevant indicator through standard interfaces; IF_EDOC_SOURCE_EXTENSION and IF_EDOC_SOURCE_PROCESS_EXT. These interfaces are provided by SAP in document- Enabling a Source Type for a Process | SAP Help Portal.

Please note that, testing is done in Customizing Demo but actual Customizing system screenshots are just for reference.

Problem:

1) Source Ext. Active checkbox is not available in SSCUI ID 102190 - Activate Source Type Documents for Company Code (pre-requisite 4).

2) Standard class CL_EDOCUMENT which is also used to generate the XML is not released (pre-requisite 1).

3) The extension classes have been created and all pre-requisites for these interfaces, but they’re not called/triggered (probably bcus of problem 1).

Question:

1) Is there a configuration to enable the column “Source Ext. Active”?

2) Since it’s a standard object, does this need to be released as well for the extension to work?

3) At which point will the standard process call below methods, or did we miss something?
    a) IF_EDOC_SOURCE_EXTENSION~IS_RELEVANT

    b) IF_EDOC_SOURCE_PROCESS_EXT~ CHECK_RELEVANCE

These are all the 4 pre-requisites that are identified based on the documentation.

NOTE: Pre-requisites 1 and 4 are not met due to standard error.

1) The development objects needed to generate XML are already released except for CL_EDOCUMENT which is the standard object.

CL_EDOCUMENT in both Customizing (Actual & Demo) systems are not released yet:

But for custom extension classes for IF_EDOC_SOURCE_EXTENSION & IF_EDOC_SOURCE_PROCESS_EXT they have been set to release:

NOTE: For testing purpose, we maintained both FI_INVOICE, RE_INVOICE & RE_DOC:

2) The source extension class has been implemented for the interface IF_EDOC_SOURCE_EXTENSION:

3) The source process extension class has implemented for the interface IF_EDOC_SOURCE_PROCESS_EXT.

The edoc_Process is MYINV as it’s part of the Customer Invoice.

4) The combination of company code and source type have been set to Active and you've selected the Active and Source Ext. Active:

[Chuma]

Hello @Vynerfes 

In SAP S/4HANA Public Cloud Edition, you cannot flip the Relevant flag or force manual creation for a delivered source type through your own classes. The two interfaces, IF_EDOC_SOURCE_EXTENSION and IF_EDOC_SOURCE_PROCESS_EXT, are only acknowledged by the framework when the source type is explicitly enabled for customer extension by SAP. In Public Cloud, that switch Source Ext. Active in SSCUI 102190 is not exposed to customers, which is why your classes are not being called.

A few points to clarify what you are seeing.

SSCUI 102190 – Source Ext. Active missing
In Public Cloud, this checkbox isn’t available to customers. Activation is managed by SAP. If it is not active for the source type, such as RE_INVOICE, RE_DOC, etc., the extension callbacks won’t be triggered.

CL_EDOCUMENT not released
Correct. That’s another sign the core generation class isn’t open for customer enhancement in Public Cloud. You can register your own classes in “Register Handling Classes for Source Extensions”, but unless the source type is whitelisted and “Source Ext. Active” is on, the framework will not dispatch to them.

Relevant indicator
In Public Cloud, relevance is determined by SAP’s delivered relevance logic for each supported process and country. It is not intended to be overridden to make an unsupported object, like CLM invoices, an eDocument capable.

• Why your classes aren’t called. Although you set API state C1 (Use System-Internally) and registered the classes.
• The dispatcher verifies the activation flag based on source type or company code. Since that flag isn’t customer-configurable in Public Cloud, your implementations are skipped.

What you should do (Recommendation)

• Use a supported source or process for customer billing, like SD billing or FI-AR invoice, and let DRC generate the eDocument from that standard object. If CLM produces the commercial invoice, route it to a supported billing object that DRC understands.
• If there is a genuine legal requirement for CLM as a source, open an incident with SAP, commonly used component: LO-GLO-EDOC or country-specific component, requesting enablement or a roadmap. That is currently the only way to activate Source Ext. Active for a delivered source type in Public Cloud

SAP Help Portal – Enabling a Source Type for a Process

SAP Help – App Extensibility: eDocument Cockpit and Manage Electronic Documents

Let me know if you need further support

With regards

Chuma