Bank Communication Management (BCM) – Collective Payment Order Notification In (CPON) mapping

Introduction

When working with Bank Communication Management (BCM) you want to efficiently handle the confirmations for your payments. It’s vital to have up to date information about the status of your payment at various steps of it’s processing as quickly as possible. And usually you’ll receive multiple status updates. Was it processed correctly? Has its delivery failed or maybe it was rejected by the bank for some other reason? That’s where the BCM payment confirmations come into play. SAP offers two ways to handle confirmations listed below – you can decide to use only one approach or a combination of the two, depending on the requirement.

a) PROS:

– No PI/PO involvement needed

– PAIN.002 (v2 & v3) format works out-of-the-box

b) CONS:

– Dedicated file system storage required

– Runs as background job

– XSLT transformation development required for non-PAIN.002 formats

a) PROS:

– No background job – quicker execution

– No dedicated storage space required

– More flexibility with mapping (e.g. from legacy formats)

b) CONS:

– PI/PO required for mapping

– No pre-delivered mapping

As you can see, both solutions have their pros and cons. The RBNK_IMPORT_PAYM_STATUS_REPORT report is potentially easier to get it running. However, it is better to put the initial effort into setting up the CollectivePaymentOrderNotification_In for quicker status updates and a more streamlined message flow based on proxy engine processing.

I present below a simple mapping that will help you quickly start off with your interface. For the PAIN.002 format you could reuse pre-delivered transformation PAIN002_V2_TO_CPON or PAIN002_V3_TO_CPON however that’s not the scope of this article.

Important elements:

– Data medium reference number

– General batch execution status

– General batch execution note

– General batch rejection reason

– Document Number of the Payment Document

– Payment item execution status code

– Payment item execution note

– Payment item rejection code

– Payment item rejection reason (text description)

– Document Number of the Payment Document

The status code and note elements are being concatenated and mapped using the table  TBNK_XST_2_IST to Payment business transaction (e.g. “Accepted by Bank”).

Example message:

Summary

Although the message structure for CollectivePaymentOrderNotification_In is pretty complex only a few elements are actually required to start using this enterprise service. Some specifics (like status mappings) will of course differ from case to case, but I hope the general approach is clear now.

Read also

1. PGP (Pretty Good Privacy) in SAP PI/PO using Secure Connectivity Add-on