BCM Payment Cockpit

2 Minute Read

Share Post:

SAP BCM solutions
This is a technical blog to speak about the payment cockpit functionality in BCM 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 Banking and treasury automation, Payment Centralization, SAP FSN Connector, Corporate connectivity and treasury management.

Three-Level Structured Message

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

  • Group level
  • Payment ID level
  • Instruction level

Features of Payment Cockpit

The payment cockpit will help in maintaining the records of credits and direct-debit instructions sent to the bank. It also the process status of those records.

Payment cockpit in SAP BCM helps in tracking and retracing the detailed status-change history along with process log for every payment made via direct-debit or payment instruction.


The payment cockpit consists of the following statuses to track the payments

  • 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 <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 post the payment run program and approvals will aid in documentation of the workflow’s history. A detailed step by step response for the payment medium acknowledgement and the sequence the messages are sent by the bank is given below in the diagram.

  • The bank sends a status message for each of the three-level messages namely Group level, Payment ID level, Instruction level.
Get The Latest Updates

Subscribe to our Blog Posts

Notifications only about new new blog post updates.

  • The bank uses pain.002 message for acknowledgement and status updates and these messages are read by the monitor database and mapped as a status update in the SAP system.


The below table lists statuses that can be sent by the bank, their corresponding SAP statuses, and their descriptions:

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


For a payment group, the report generated by this program offers drill-down capability to view payment information IDs (PmtInf) as well as individual instruction details (CdtTrfInf for credit and Dbr\tTrfInf for debits). The report also provides links to the related payment documents for each instruction issued by you to the bank.



Data that can be displayed on the report after successful creation of 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, that is, at the Payment-Group-Level, Payment-Information level, and at each individual 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 documentation history of workflow, you can get the required information with BCM Payment cockpit. All you need to do is follow simple steps to make the most out of payment cockpit to maintain the bank records. Be it Automated payments or Multicash payment factory, iQuantM can explain more about everything related to Financial services network.

Connect with iQuantM to know more about ERP Bank Connectivity and Bank integration.

Share Post:

Similar Topics

More Blogs