Fallback logical port for MDG BusinessPartnerSUITEBulkReplicateConfirmation_Out is not working

Hello experts, Need assistance connected MDG SOAMANAGER Logical larboard setup for aggregate people systems for Business Partner replications.

We are utilizing MDG (S4 Private Cloud) SAP S/4HANA 2021 version, MDG_FND 806 for your notation and beneath are 2 main scenarios successful scope.

1. ECC --> CPI <--> MDG <---> CFIN. (Existing Process)

This lawsuit ECC nonstop BP petition to MDG via CPI and aft BP instauration request, the confirmation connection is sent backmost to CPI utilizing CONFIRMATION_OUT. For this successful MDG manual logical larboard is created which was moving fine.

2. ARIBA SLP <---> MDG (New process successful setup)

This lawsuit ARIBA Sends petition to MDG, and related mistake confirmations/success connection of BP# are sent backmost to ARIBA. For this process we person created logical larboard to ARIBA based connected profile/provider system/DRF/WSDL process without utilizing immoderate default logical ports.

Now the contented comes with Confirmation_Out connection wherever without mounting the default logical larboard the connection is not generating successful srt_moni.

Recently we updated authentication to Certificate based for each outbound interfaces from MDG to ARIBA and Request_out connection is moving good with Fallback logical larboard and for Confirmation_Out adjacent with Fallback logical larboard , its not moving and failing with archetypal logical larboard and not utilizing Fallback.

Fallback logical ports are created to negociate connection protocals similar RM, Message id suppression etc.

Question1: For Confirmation_Out without marking default port, the interface is not generating and processing. Is determination immoderate solution if MDG wants to sent confirmations to aggregate systems without utilizing default port. Already checked the Receiver strategy and supplier strategy names are matching.

Question 2: For Confirmation_Out , wherefore Fallback logical larboard is not being utilized adjacent though we created based connected Service radical and each parameters seems good.

FYI: SAP Confirmed that Confirmation_Out interface is not supported betwixt MDG and ARIBA (works lone for MDG and S4), but with interior enhancement we enabled this interface and moving good with id pwd authentication erstwhile mounting default port.

SOAMANAGER screenshots are attached for references.