BCM Payment Cockpit

2 Minute Read

Share Post:

SAP BCM solutions

This technical blog speaks about the payment cockpit functionality in BCM Payment Cockpit, which enables the Payment Medium File generation and helps in documentation history maintenance with the workflows.  

We will now look at the technicality of the message instruction used by the payment cockpit topics such as SAP BCM, Banking, and treasury automation, Payment Centralization, SAP FSN Connector, Corporate connectivity, and treasury management. 

Three-Level Structured Message 

The message delivered to the bank has a three-level structure maintained when the Automatic Payment Transaction program generates it (T-code F110) and converts it to an ISO20022-based XML message. The three levels are: 

  • Group level 
  • Payment ID level 
  • Instruction level 

Features of Payment Cockpit  

 The SAP BCM payment cockpit will help maintain the credit records and direct-debit instructions sent to the bank. It also the process status of those records. 

Payment cockpit in SAP BCM payment Integration services helps track and retrace the detailed status-change history and a process log for every payment made via direct debit or payment instruction. 

The payment cockpit consists of the following statuses to track the payments through SAP BCM payment Integration in the UK. 

  • Pending for Approval – When payment run (transaction <F110>) is executed, the payment awaits approval in the workflow. The payment can be sent to the bank after the approval. 
  • Payment Approved – The payment has been approved using the workflow. This payment can be sent to the bank using the <Send to Bank>button if the <Payment Group Status> is Payment Medium Created. 
  • Payment Rejected – The payment has been rejected and cannot be sent to the bank.  

The report created to post the payment run program and approvals will aid in the documentation of the workflow’s history. A detailed step-by-step response for the payment medium acknowledgement and the sequence of the messages sent by the bank is given below in the diagram. 

  • The bank sends a status message for each level: Group level, Payment ID level, and, Instruction level. 
  • The bank uses pain.002 messages for acknowledgement and status updates are read by the monitor database and mapped as a status update in the SAP ERP system. 


The below table lists statuses that the bank can send, their corresponding SAP statuses, and their descriptions related to SAP BCM Payment Integration.

There is a re-send instruction option for which there was no acknowledgement received from the bank, thus enabling the re-sending of the payment medium file to the bank (here, the instruction status is Payment Medium Created). 

For a payment group, the report generated by this program offers a drill-down capability to view payment information IDs (PmtInf) and individual instruction details (CdtTrfInf for credit and Dbr\tTrfInf for debits). In addition, the report also links the related payment documents for each instruction issued by you to the SAP BCM payment Implementation services in USA. 

Data that can be displayed on the report after the successful creation of the Payment Medium File 

  1. Details of payment group, payment information ID, and payment instructions sent to the bank 
  2. Status-change history at all message levels, at the Payment Group Level, Payment-Information level, and at each Payment-Instruction level. 
  3. Detailed application log for both outbound and inbound messages 
  4. Individual encrypted XML messages containing your instructions 


The search options used for viewing the documentation history of workflow can be done via the following selection fields  

  • Payment Group ID: Run identification from the payment run program (transaction /F110) 
  • Payment Information ID: An internally generated number from F110, which represents a batch 
  • Instruction ID: An internally generated number from F110 that represents an individual payment in a batch 
  • Run Date: The date of the payment run 
  • Business Transaction: The F4 values under Business Transaction are: 
  1. Payment Medium Created 
  2. Payment Sent to Bank 
  3. Received by Bank 
  4. Accepted by Bank 
  5. Rejected by Bank 
  6. Partially Accepted by Bank 
  7. Payment Statement Received 


With options such as viewing the documentation history of workflow, you can get the required information with the BCM Payment cockpit. First, however, you must follow simple steps to make the most out of the payment cockpit to maintain the bank records with the help of SAP BCM Payment Integration services in the UK. 

Be it Automated payments or a Multicash payment factory, iQuantM, an SAP BCM payment Implementation partner in USA, can explain more about everything related to the Financial services network. 


Connect with iQuantM, an SAP BCM payment Implementation partner in the UK, to learn more about ERP Bank Connectivity and Bank integration.

Get The Latest Updates

Subscribe to our Blog Posts

Notifications only about new new blog post updates.

Share Post:

Similar Topics

More Blogs

Overview of SAP Bank Communication Management

Automate Bank Payment Processing with SAP Bank Communication Management

SAP Multibank Connectivity is a SaaS product that helps establish connection between the various banks and organizations that make payments to them. The payments are tracked automatically with their transfer status to provide notification on its success. It helps connect the financial institutions with the corporate through secure network with the support of SWIFT.

Explore more »