Enabling Multiple Instances (Bulk) processing on a custom Migration Object

[afordham]

Hi,

I have created a custom Migration Object in txn LTMOM (using the Staging Tables approach) and selected the "Process Multiple Instances at Once" checkbox for my object.  Looking at standard templates with this enabled, I can see that the input tables contain a field called SENDER_TECHNICAL_ID (data element FS4MIG_SENDER_TECHNICAL_ID) and the return table also has a special type (table type FS4MIG_T_BAPIRET2) which also contains this field.  So far, so good!

I have looked at the code in "Includes for Handling the Result Parameter" of standard bulk-enabled templates and they share some common processing, particularly the use of standard include DMC_PLV_OLO_BULK.  Following these examples, I have written my own include for my object which also has DMC_PLV_OLO_BULK included at the end.

The problem comes when I try to generate my object.  I get the error message:
FORM "_RULE_IS_S4H_CLOUD_P" does not exist.
Further investigation shows that this subroutine is called from the standard DMC_PLV_OLO_BULK include.

Looking at the function groups that have been generated for objects from standard templates, I can see that this subroutine, along with many others, can be found in the ...FI4 include (named "IL - RULE CODE").  Although a ...FI4 include appears in the function group generated from my custom object, it does not contain any of the subroutines that are called from the standard DMC_PLV_OLO_BULK include.  I have compared the set up of my custom object with some of the standard objects but I can't find any setting or code that would lead to these additional subroutines being put in the ...FI4 include.

Does anyone know what triggers these standard subroutines being included in the generated function group?  Has anyone managed to bulk-enable a custom migration object using  the common includes found in the standard objects?

Many thanks in advance,

Andrew

[FrankFinkbohner]

Hello Andrew,

RULE_IS_S4H_CLOUD_P is a project rule (suffix _P). Subproject (_S) and Project rules will only be copied from original delivery project into the Z-project if a migration object that uses this rule (mainly in object or sub project rules) is added to the project.

What SAP S/4HANA release are you running?
This rule is marked OBSOLETE with 2025 release and will only be used in retired objects. Means the status is invalid and cannot be used anymore within objects.
Within 2023 it is still available. Try to add one of the following objects to your Z-Project: SIF_PRODUCT, SIF VENDOR_2, SIF_INTORDER_2.
That may help.

Another question. Does your API support bulk processing and handles the specific error message for bulk? Is it an own function module or an SAP function module?

Your FM must be compatible with the bulk handling of the migration cockpit.

BR

Frank

[DhananjayS]

Hi I am trying the same for a custom object did it work? I tried adding the sif_product object as well but the global data is not generated properly receiving error for _var_plv_active_p.Any workaround for this?