Financial Management Blogs by Members
Dive into a treasure trove of SAP financial management wisdom shared by a vibrant community of bloggers. Submit a blog post of your own to share knowledge.
cancel
Showing results for 
Search instead for 
Did you mean: 
GOWRESHANHARAN
Explorer

Payment batch Introduction :

A business object containing multiple payment items based on the settings of the underlying payment agreement. All payment transactions share common attributes, defined as grouping characteristics. Different combinations of attributes result in the creation of a new payment batch.

Uses payment batches:

You use payment batches to bundle payment items for collective processing. A single outgoing payment order will be generated containing all payment items and an offsetting clearing item. The payment order will be passed to the File Handler component for payment media creation. The resulting payment message can be used internally as a payment advice or is sent to your house bank for processing. The payment items are posted as one total sum.

You activate the creation of payment batches and its grouping characteristics in the payment agreement. The system will apply some default grouping characteristics automatically. The posting is done with a corresponding clearing item that covers the total amount of payment items in the payment batch.

SAP Bank Communication Management:

SAP Bank Communication Management (BCM) is a component within SAP S/4HANA that facilitates seamless communication and integration between your organization and its banks. It is designed to enhance and automate the exchange of financial information between the company and its banking partners. SAP BCM helps streamline various banking communication processes, including payments, statements, and other related activities. SAP BCM allows you to set up and manage communication users, providing the necessary security and authentication mechanisms for secure communication with banks.

Setting Up Payment Batches :

Prerequisites: 

The following pre-requisites are required to go ahead with the configuration for payment Batch approval

1.Business Function FIN_FSCM_CLM is active

Depending on your license, you can use a basic scope of  Cash and Liquidity Management  or  or a full scope of this solution capability. This business function must be activated in order to switch on the full scope of this solution capability.

 

Technical Name Technical Name of Business Function FIN_FSCM_CLM
 

Type of Business Function

Enterprise BF

Available From

SAP S/4HANA, on-premise edition 1511

Application Component

FIN-FSCM-CLM

Required Business Function

Not relevant

 

Transaction CodeSFW5

 

HARAN_0-1712668992359.png

 

HARAN_1-1712668992215.png
 
2.In the General settings for cash management Cash scope should be Full Scope.
Transaction Code SM30
HARAN_2-1712668992173.png

Table/View

FCLM_CONFIG2

Click On New Entries :

HARAN_3-1712668991937.png
 
Activate Full Scope
 
HARAN_4-1712668992013.png
3.Payment Medium Workbench

The Payment Medium Workbench is a tool within SAP BCM that supports the creation and management of payment files. It allows you to generate payment files in different formats according to the requirements of your banks. The configuration for Payment Medium Workbench is in place which includes Configuration in the following Transaction Code.

  1. FBZP
  2. OBPM1
  3. OBPM2
  4. OBPM3
  5. OBPM4
  6. DMEEX
4.BCM module is activated in the system.
Transaction Code SFW5 

 

 
HARAN_5-1712668992554.png

HARAN_6-1712668992766.png
5. User ID => SAP_WFRT 

SAP_WFRT user ID is created. The user ID should have the “SAP All or All RFC authorizations” role assigned.

 

Transaction CodeSU01

 

HARAN_7-1712668992812.png
6.Workflows

Workflows are activated :

Transaction CodeSWU3

 

HARAN_8-1712668993138.png

Define Settings for Bank Account Master Data

Go to SPRO >Financial Supply Chain Management > Cash and Liquidity Management > Bank Account Management > Basic Settings > Define Settings for Bank Account Master Data

 

HARAN_9-1712668993130.png

Account Type Definition:

This setting is required for the migration of house bank accounts .Define different types of accounts to suit different business purposes. Account types can be used as an analysis dimension in reporting and planning. If the bank account contract type is enabled, you must specify a bank account contract type for each account type. Unlike account types which can be defined freely by users, bank account contract types are predefined by SAP. You can define one or more account types for each bank account contract type.

To add a new bank account type, choose New Entries and then specify the following:

  1. Type: Enter a unique type ID no longer than 10 characters.
  2. Description: Enter a short description for the account type, for example, current account.
  3. Attribute: Specifies whether the bank account is an operating account or a functional account.
  4. Operating accounts are bank accounts that are used for daily business transactions, such as receiving incoming payments and issuing outgoing payments.-
  5. Functional accounts are bank accounts that are used in other financial activities, such as loan, investment, and fund raising.

Here we have to create the Bank Account types, by default there are account types. This account type would be used in the bank account master.

 

HARAN_10-1712668993144.png

Define Payment Approval Groups:

Define different groups of authorized payment approvers to suit different business purposes. To do so, you need to have enabled the payment approval function in the Customizing activity Enable Payment Approval

 

HARAN_11-1712668993158.png

Define Approval Patterns

  1. In the Define Payment Approver Groups view, define a payment approver group
  2. In the Define Approval Patterns view, define patterns for payment approvals:

    = > For a sequential pattern, the payment approver groups defined in this pattern approve payments in a sequential order. You can assign up to four payment approver groups for a sequential approval pattern.

    = > For non-sequential patterns, the payment approver groups approve payments regardless of sequential order. You must assign at least two payment approver groups for non-sequential patterns. You can create non-sequential approval patterns by specifying the approval sequence as Non-Sequential.
HARAN_12-1712668992118.png

 

Assign Approval Patterns

In the Assign Approval Patterns view, you can assign patterns to company codes and account types.

The assignment works as follows:

  1. If an approval pattern is assigned to a company code but not to any account type, then the pattern is applicable to all account types under that company code.
  2. If an approval pattern is assigned to an account type but not to any company code, then the pattern is applicable to the account type for all the company codes.
  3. If multiple approval patterns are assigned to an individual account type or company code, approval pattern priority can be defined to determine the sequence of approval patterns.
  4. The priority value 0 has the highest priority.

Here we assign approval patterns to the combination of Company code and Account type. I have assigned below the Pattern ZEU1 to Account type IN&OUT for my company code 7180. In case of multiple Patterns to the same combination, we can set the priority. Priority 0 (blank) takes precedence.

 

HARAN_13-1712668993162.png

Define Automatic  Approval / Rejection.

In this setting you define the automatic actions in Bank Communication Management in case the approval list in Bank Account Management is empty, or the approval pattern cannot be defined.

Possible values:

  1. Auto Rejection when Approval Pattern not Found, or Approval List is Empty: All payment batches will be automatically rejected in case the approval list in Bank Account Management for the house bank account is completely empty or in case the approval pattern cannot be defined.
  2. Auto Rejection when Approval List is Empty: All payment batches will be automatically rejected in case the approval list in Bank Account Management for the house bank account is completely empty.
  3. Auto Approve when Approval List is Empty: All payment batches will be automatically approved in case the approval list in Bank Account Management for the house bank account is completely empty. This is the default value for the Bank Communication Management with Bank Account Management.
 
HARAN_14-1712668993151.png
 
Assign the above type to your company code:

HARAN_15-1712668993164.png

BCM Configuration:

As stated, above BCM is a part pf FSCM module in SAP. Below is the node for BCM.

Go to SPRO >Financial Supply Chain Management >  Bank Commination Management >  Basic Settings

 

HARAN_16-1712668992600.png

Basic settings:

Go to SPRO >Financial Supply Chain Management > Bank Commination Management > Basic Settings > Basic Settings for Approval

Define the default currency and the resubmission date for payments. You can define the default currency, resubmission date, and whether or not a signature is needed for payments.

  1. When a payment batch is evaluated for release (such as dual control, triple control, automatic release, and so on), the total batch amount can be evaluated based on the default currency if the payments in the batch consist of different currencies or different company code (hence different local currency).

Default resubmission date

  1. For resubmission of payments, the resubmission date from the current date can be set.
  2. If the check box is marked, the signature popup appears before the payment batch is approved.

Click On New Entries:

HARAN_17-1712668993152.png

 

HARAN_18-1712668993154.png

Rule Maintenance:

Go to SPRO > Financial Supply Chain Management > Bank Communication Management > Payment Grouping > Rule Maintenance

In this IMG activity, you can define the rules for the kind of grouping you desire for payments. Rules should be prioritized, so that when there is more than one rule satisfying the criteria for grouping, your priorities determine the batching rule. Once a rule is defined, click on the maintain button to specify the criteria for batching rules. Here all attributes of the payment are provided. Only attributes making sense for the batching rule should be double clicked and then maintained.

Example

Suppose you define rule YCHQ_TRNSF priority 0 and YAMNT_MED priority 1. If a payment satisfies the criteria for batching, rule YCHQ_TRNSF is selected because of its higher priority.

These rules are applied to responsibilities created based on priority assigned.

 

HARAN_20-1712668993156.pngSave rule and select the row to maintain the rules
HARAN_21-1712668993169.pngUpdate rule criteria based on your requirement for the rule:
HARAN_22-1712668993173.png
HARAN_23-1712668993175.png
HARAN_24-1712668993177.png
HARAN_25-1712668993180.png

 

Additional Criteria for Payment Grouping

Go to SPRO > Financial Supply Chain Management > Bank Communication Management > Payment Grouping > Additional Criteria for Payment Grouping

In this IMG activity, you can set additional criteria (apart from batching rules) such as requiring all payments of a batching rule to belong to a certain date. Two grouping fields are provided, one of which you select for the batching.

Example

Suppose you select VALUT field for batching rule YCHQ_TRNSF. This means that if a batching rule YCHQ_TRNSF is selected, payments are further batched by the date, so all payments belonging to YCHQ_TRNSF and of the same date will form a batch.

Note: Grpng Field1 should be always HKTID for the workflow to trigger based on the signatories in the Bank Master Fiori app. The Grpng. Field2 can be as required.

 

HARAN_26-1712668993181.png

Mark Rules for Automatic Payments (No Approval)

Go to SPRO > Financial Supply Chain Management > Bank Communication Management > Release Strategy > Mark Rules for Automatic Payments (No Approval)

Incase if we don’t want to trigger the approval process for certain payments, then we can create a separate rule for this purpose and check Auto payment as shown below. Then it will skip the process of batch merging, hence direct file generation.

HARAN_27-1712668993184.png

Release strategy:

IMG > SPRO > Financial Supply Chain Management > Bank Communication Management > Release strategy > Change and release > Assign role to release steps 

In this IMG activity, you can assign a standard role to the individual release steps of the release procedure that applies for a certain release object. Processing (users, workplace, organizational units, positions and so on) is linked to the standard role. The system uses the standard role to find the processors responsible and, through the SAP Business Workflow, forwards the release object as a work item to them for processing further.You have made the settings for the corresponding release object in IMG activity Assign Release Object to Release Procedure.

Standard settings => SAP does not supply any standard roles for Bank Communication Management.

  1. Click on the new entries above and add “BNK_INI” as a release object. This release WF task is activated by basis and is a standard workflow that is delivered with the SAP BCM module.
  2. Select “01” from the drop-down for required release. This is your first-level approval of the dual approval workflow.
  3. Select “1” from the drop-down for the WF release step. As mentioned above this is your first step approval.
  4. Hit enter and save to generate rule number. This rule number is auto-generated in the system. Do not enter rule number manually.
HARAN_28-1712668993187.png

 

HARAN_29-1712668993191.pngcreate responsibility based on rules created for payment grouping above
HARAN_30-1712668993205.png 
HARAN_31-1712668993194.png
HARAN_32-1712668993263.png
HARAN_33-1712668993267.png
HARAN_34-1712668993251.png

Select the responsibility and click on create

HARAN_35-1712668993272.png
HARAN_36-1712668993276.png

Once it's saved, the status of responsibility turns from red to green. Select the responsibility and click on insert agent assignment to add the users responsible for the first level of release of the payment batch.

HARAN_37-1712668993279.png

Additional release steps:

Path: IMG > SPRO > Financial Supply Chain Management > Bank Communication Management > > Additional release steps > Assign roles to release steps:

In this IMG activity, you can make the following basic settings for the release of a particular release object. Since the release of release objects is regulated by the SAP Business Workflow in the group frame release, you must define if and when the system forwards a release object to the release process.

This is the config for 2nd level of approver. Follow the same procedure as it was done for the first-level approver. This time only workflow task changes to “BNK_COM”

HARAN_38-1712668993280.png

Create rule 

HARAN_39-1712668993269.png
HARAN_40-1712668993306.png

 

HARAN_41-1712668993274.png

 

HARAN_42-1712668993311.png

 

HARAN_43-1712668993313.png

 

HARAN_44-1712668993333.png

Once it's saved, the status of responsibility turns from red to green. Select the responsibility and click on insert agent assignment to add the users responsible for the second level of release of the payment batch

HARAN_45-1712668993337.png

Define release procedure:

Path: IMG > SPRO > Financial Supply Chain Management > Bank Communication Management > > Additional release steps > Define Release Procedure:

In this IMG activity, you can make basic settings for the release of a particular release object. Since the release of release objects is regulated by the SAP Business Workflow, in the group frame release you must define if and when the system forwards a release object to the release process.

Prerequisites

You have made the standard settings for the SAP Business Workflow in the Basis Customizing settings by choosing Business Management -> SAP Business Workflow -> Maintain Standard Settings for SAP Business Workflow .

Standard settings

The standard setting supplied for the release objects is no release (radio button is never in the group frame release).

HARAN_46-1712668993340.png

Assign workflow template to release procedure:

Path: IMG > SPRO > Financial Supply Chain Management > Bank Communication Management >  Additional release steps > Assign workflow template to release procedure:

In this IMG activity, you can assign a release workflow and a release procedure workflow to every release procedure of a release object. The release workflow realizes the technical processing of the release in the system. The release procedure workflows realize the technical processing of the various release procedures (such as the principle of treble control) in the system.

Assign the workflow template being used to release procedure.

HARAN_47-1712668993367.png

Call transaction SM30 with view V_TBCA_RTW_LINK and check that the following entries are maintained:

 

BNK_COM015010002450100021
BNK_COM025010002450100022
BNK_COM035010002450100023
BNK_INI015010002431000004

 

HARAN_48-1712668993375.png

Workflow templates:

  • Make sure the workflow templates and tasks are assigned as general task. If this is not maintained as general task, you will not be able to see your batch in bank monitor(BNK_MONI/BNK_MONIP). Below is the list of task type which needs to be updated/ checked:
  • In transaction PFTC_CHG, Choose 'Standard task' and for 50100025,50100026,50100066,50100075: In the menu 'Additinal data ->Agent Assignment ->Maintain, Mark as 'General' Task.
HARAN_49-1712668993380.png
HARAN_50-1712668993381.png
HARAN_51-1712668993386.png

 

HARAN_52-1712668993389.png

The following BTE should be maintained for Product BAM

Transaction CodeFIBF
HARAN_53-1712668993429.png
HARAN_54-1712668993449.png

HARAN_55-1712668993453.png
HARAN_56-1712668993455.png

Maintain the Event Type Linkage for Triggering Workflow Processes

Go to SPRO > Financial Supply Chain Management > Cash and Liquidity Management > Bank Account Management > Maintain the Event Type Linkage for Triggering Workflow Processes or Goto to transaction SWETYPV, for object type 'BUSISB001', Activate 'Linkage activated'

Here we assign the Workflow to the Object type and event. This would be default available, just have to confirm if the Type Linkage is active.

HARAN_57-1712668993464.png
HARAN_58-1712668993462.png

Check the settings in transaction OBPM5.

55.png

56.png

Rejection or Resubmit Automation:

The following BADI can be used to reverse original payment documents in case of rejection or resubmit of the batches.

BNK_BADI_ORIG_PAYMT_CHG

Symptom

You use Bank Communication Management and would like to have an automatic Reversal (FBRA) of the Payment Documents when Batch Payments are rejected in TA BNK_APP.

Reason and Prerequisites

BADI (enhancement spot) BNK_BADI_ORIG_PAYMT_CHG; standard in SAP_APPL 604. In 602 and 603 you need to apply note 1302623 first.

Solution

In the correction instruction, you find proposal coding for the interface method IF_EX_BNK_ORIG_PAYMT_CHG~ON_REJECT in a customer class Z_CL_BNK_BADI_PAYMT_CHG that implements the BADI.
Proposal coding updated on 27. August 2010 (Symbol "LG20100827): We now write an application log (Transaction SLG1, object FBPM) in case there are errors (typically due to locking) that prevent the reversal. In such a case, the payment should be reversed later and seperately (TA FBRA).

The code of the note only contains logic for FI payments (payment program F110). If you have activated BCM for Treasury (payment program F111), Travel or Payroll you have to enhance the logic accordingly.

This note is valid also for releases higher than 606.

 

 

*$*$----------------------------------------------------------------$*$* 
*$ Correction Inst.         0120031469 0000753245                     $*
*$--------------------------------------------------------------------$*
*$ Valid for       :                                                  $*
*$ Software Component   SAP_APPL   SAP Application                    $*
*$  Release 602          All Support Package Levels                   $*
*$  Release 603          All Support Package Levels                   $*
*$  Release 604          Fm SAPKH60401                                $*
*$  Release 605          All Support Package Levels                   $*
*$  Release 606          Fm SAPKH60601                                $*
*$--------------------------------------------------------------------$*
*$ Changes/Objects Not Contained in Standard SAP System               $*
*$*$----------------------------------------------------------------$*$*
*&--------------------------------------------------------------------*
*& Object          METH Z_CL_BNK_BADI_PAYMT_CHG
*&                      IF_EX_BNK_ORIG_PAYMT_CHG~ON_RESUBMIT
*& Object Header   CLAS Z_CL_BNK_BADI_PAYMT_CHG
*&--------------------------------------------------------------------*
...
METHOD IF_EX_BNK_ORIG_PAYMT_CHG~ON_RESUBMIT.
*>>>> START OF INSERTION <<<<
** SAP note 1333640 - call standard fallback implementation **
  DATA: FALLBACK TYPE REF TO CL_BNK_BADI_ORIG_PAYMT_CHG.

  CREATE OBJECT FALLBACK.

  CALL METHOD FALLBACK->IF_EX_BNK_ORIG_PAYMT_CHG~ON_RESUBMIT
    EXPORTING
      I_REGUH = I_REGUH.

*>>>> END OF INSERTION <<<<<<
...
*&--------------------------------------------------------------------*
*&--------------------------------------------------------------------*
*& Object          METH Z_CL_BNK_BADI_PAYMT_CHG
*&                      IF_EX_BNK_ORIG_PAYMT_CHG~ON_REJECT
*& Object Header   CLAS Z_CL_BNK_BADI_PAYMT_CHG
*&--------------------------------------------------------------------*
...
METHOD IF_EX_BNK_ORIG_PAYMT_CHG~ON_REJECT.
*>>>> START OF INSERTION <<<<
**----------------------------------------------------------------------------
** SAP note 1333640
** Proposal for automatic system action on batch/payment rejection:
** Reset cleared items and reverse payment documents (F110)
**
** Before applying this automatically, first create a class
** Z_CL_BNK_BADI_PAYMT_CHG that implements interface IF_EX_BNK_ORIG_PAYMT_CHG
**
** Update "LG20100827: Write aplication log (SLG1/FBPM)
**----------------------------------------------------------------------------
  DATA: LF_T001 TYPE T001,
        L_GJAHR TYPE GJAHR,
        L_EXTNUMBER TYPE BALNREXT.                          "LG20100827

  CONCATENATE 'ON_REJECT'
              SY-DATUM SY-UZEIT SY-UNAME INTO L_EXTNUMBER . "LG20100827

*- Get year from posting date
  CALL FUNCTION 'COMPANY_CODE_READ'
    EXPORTING
      I_BUKRS = I_REGUH-ZBUKR
    IMPORTING
      E_T001  = LF_T001
    EXCEPTIONS
      OTHERS  = 5.

  IF SY-SUBRC <> 0.                                         "LG20100827
    CALL FUNCTION 'BNK_UI_LOG_MSG_ADD'                      "LG20100827
      EXPORTING
        I_MSGID     = SY-MSGID
        I_MSGNO     = SY-MSGNO
        I_MSGTY     = 'E'
        I_MSGV1     = SY-MSGV1
        I_MSGV2     = SY-MSGV2
        I_MSGV3     = SY-MSGV3
        I_MSGV4     = SY-MSGV4
        I_EXTNUMBER = L_EXTNUMBER.
    MESSAGE ID SY-MSGID TYPE 'I' NUMBER SY-MSGNO            "LG20100827
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    CALL FUNCTION 'BNK_UI_LOG_SAVE'.
    EXIT.
  ENDIF.

  CALL FUNCTION 'DATE_TO_PERIOD_CONVERT'
    EXPORTING
      I_DATE  = I_REGUH-ZALDT "posting date
      I_PERIV = LF_T001-PERIV
    IMPORTING
      E_GJAHR = L_GJAHR
    EXCEPTIONS
      OTHERS  = 5.

  IF SY-SUBRC <> 0.                                         "LG20100827
    CALL FUNCTION 'BNK_UI_LOG_MSG_ADD'                      "LG20100827
      EXPORTING
        I_MSGID     = SY-MSGID
        I_MSGNO     = SY-MSGNO
        I_MSGTY     = 'E'
        I_MSGV1     = SY-MSGV1
        I_MSGV2     = SY-MSGV2
        I_MSGV3     = SY-MSGV3
        I_MSGV4     = SY-MSGV4
        I_EXTNUMBER = L_EXTNUMBER.
    MESSAGE ID SY-MSGID TYPE 'I' NUMBER SY-MSGNO            "LG20100827
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    CALL FUNCTION 'BNK_UI_LOG_SAVE'.
    EXIT.
  ENDIF.

  CALL FUNCTION 'J_1B_FBRA_POSTING_AUFRUFEN'
    EXPORTING
      I_AUGBL           = I_REGUH-VBLNR
      I_BUKRS           = I_REGUH-ZBUKR
      I_GJAHR           = L_GJAHR "derived from I_REGUH-ZALDT
      I_STGRD           = '01'
    EXCEPTIONS
      NOT_POSSIBLE_FBRA = 1
      NOT_POSSIBLE_FB08 = 2
      OTHERS            = 3.

  IF SY-SUBRC <> 0.
    CALL FUNCTION 'BNK_UI_LOG_MSG_ADD'                      "LG20100827
      EXPORTING
        I_MSGID     = SY-MSGID
        I_MSGNO     = SY-MSGNO
        I_MSGTY     = SY-MSGTY
        I_MSGV1     = SY-MSGV1
        I_MSGV2     = SY-MSGV2
        I_MSGV3     = SY-MSGV3
        I_MSGV4     = SY-MSGV4
        I_EXTNUMBER = L_EXTNUMBER.
    MESSAGE ID SY-MSGID TYPE 'I' NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    CALL FUNCTION 'BNK_UI_LOG_SAVE'.
  ENDIF.

*>>>> END OF INSERTION <<<<<<

*&--------------------------------------------------------------------*

 

SAP Note Reference : https://me.sap.com/notes/1333640 

 BCM: Batch is not created

Resolution

You can use the following transactions to determine the error:

  1. Check the settings in transaction OBPM5.
  2. Has a selection variant been defined in transaction OBPM4?
  3. Use transaction BNK_MONIP to check whether a merge has occurred. Red traffic light: The merge has occurred, but the system did not create a batch.
  4. Use transaction SLG1 and the object 'FBPM' to check the application log.
  5. Use transaction SM37 to check the jobs with the identifier PAY_BTC*.
  6. The system may not have been able to find a rule. In this case, the system issues a message when you execute transaction FBPM1.
    You can use the report RBNK_PAYM_SCHEDULE to trigger the batch creation again after you have changed the Customizing for the rules. Only payments that still have no batch number are processed. As the date, you must enter December 31, 9999 (31.12.9999) to ensure that no payments are excluded. (Only payments with REGUH-AUSFD <= P_EXEDT are selected, which is the date in the report.)
  7.  As long as payment files cannot be created, also the batch cannot be created, BCM simulates the file creation with the format implementation before creating the batch, the batch will be created after the simulation.
       To avoid this unexpected situation we recommend to test a newly implemented payment format carefully without any additional process steps (like BCM approval). If this works fine, you can use the format in BCM properly
       No payment file => No payment batch
  8. Check PAYM* job in transaction SM37:

SAP Note Reference : https://me.sap.com/notes/2775848/E 

Workflow setup in new installations for BCM

Please ensure if all the points mentioned below are complete in the system:

  1. Use transaction BNK_BNK_INI_REL01 and check if, Release procedure 'Dual control' ('01') is marked for 'Always'.
  2. S4HANA on-premise 1610 and lower: User WF-BATCH must exist in the system.S4HANA onPremise 1709 and higher: User SAP_WFRT must exist in the system (see note 2568271).Authorizations of that user should be as mentioned in note 1251255. See also note 73160 if you prefer to give less authorizations to this user.
  3. Go to transaction swu3 and ensure 'RFC destination' is configured
  4. Go to to transaction SWETYPV, for object type 'BUSISB001', Activate 'Linkage activated'.
  5. In transaction PFTC_CHG, Choose 'Standard task' and for 50100025,50100026,50100066,50100075: In the menu 'Additional data ->Agent Assignment ->Maintain, Mark as 'General' Task.
  6. Call transaction SM30 with view V_TBCA_RTW_LINK and check that the following entries are maintained:
    BNK_COM 01 50100024 50100021
    BNK_COM 02 50100024 50100022
    BNK_COM 03 50100024 50100023
    BNK_INI 01 50100024 31000004 
  7. In case still no WF items are being created then try to run report RSWD_REPLICATE_FROM_9999 to re-generate the WF template WS50100024.
  8. In case you get error message 5W023: Prefix number: entry missing for system... when trying to set up the agent assignment rules: Maintain table T78NR in Customizing (via TA sm30) and create an entry for the current system and client.

SAP Note Reference : https://me.sap.com/notes/1041016/E 

Master data requirements:

Fiori Application : Manage Bank Accounts(F1366A)

57.png

Manage Automatic Payments:

Payment run process is an accounts payable process that is used to handle payments to vendors. The process is called automatic payment program.

With the transactional app Manage Automatic Payments, you can schedule payment proposals or schedule payments directly and get an overview of the proposal or payment status. The app identifies the overdue invoices and checks whether all the required payment information is complete.

The Payment Process includes the Following Steps

  • Invoices are Entered
  • Pending Invoices are analysed for due date
  • Invoices due for payment are prepared for review
  • Payments are approved or modified
  • Invoices are paid


Start fiori app “Manage Automatic Payments” and Click Create Parameter.

 

HARAN_0-1712669988696.png

 


On the first screen, you need to enter run date and identification. In the identification field, give a five-characters alphanumeric code that will be used to identify the payment program. A combination of the run date and identification is used to identify the program in SAP system.

Fill the Run date and identification and click Create:

 

HARAN_1-1712669988703.png

 


In the Parameters Tab, We have to define the following and Click Save

  • What is to be paid – Docs. Entered Up to
  • What payment methods will be used – Payment Methods
  • When will the payments be made – Posting Date?
  • Which company codes will be considered – Company Codes?
  • How are they going to be paid – The payment Method Sequence decides the Priority of the Payment Method
  • Enable Additional log – To get some additional log information.

HARAN_2-1712669988704.png

 


You can see the payment parameter created :

 

HARAN_3-1712669988707.png

 


Create Payment Proposal:

Selected the Parameter and click schedule Proposal:

 

HARAN_4-1712669988709.png

 


When you click on Proposal the system is going to ask whether you want to create it immediately or want to schedule it for a time in the future. For this demo, we are going to run it immediately. You should tick the checkbox for creation of payment medium.

Make sure you select “Start Immediately” and then click on Schedule.

 

HARAN_5-1712669988710.png

 


You can see the payment proposal in the respective tab.
A payment proposal is generated based on the parameters.
HARAN_6-1712669988711.png

 


Review Payment Proposal:

  • Click on the arrow button to review the document selected in this run.
  • The system will list all the vendors that have been included in the payment proposal.
  • We can view the Proposal Log for possible errors by Pressing the Proposal Log Button.
  • We can edit the proposal to block the some payments if we want, Press the Edit Proposal Button.

HARAN_7-1712669988713.png

 


Payment Run:

Go to Proposal and click on Schedule Payment to run Payment.

 

HARAN_8-1712669988714.png

 


Check “Start Immediately” to start the payment run instantly and then click on Schedule.

 

HARAN_9-1712669988715.png

 


Go to “Payments Processed” and You can see the payment posted.

We can check the status of the Payment run on the Status Tab.

 

HARAN_10-1712669988715.png

 


You can also select the posted payment to see the log:

 

HARAN_11-1712669988717.png

Payment Batch will get created:

 

70.png
 
Fiori Applications :
 
71.png
 
Batch status in app Monitor Payments:

Following are the payment batch statues in app Monitor Payments:

  • Status All Batches: Displays all the payment batches.
  • Status New (Payment Batch Created): Batch is created and waits for first approval.
  • Status In Approval (In Approval): Batch is approved at least once, though not final approval.
  • Status Approved (Payment Medium Created): Batch successfully completes approval process, and the payment medium is created.
  • Status Sent to Bank (Accepted by Bank): The payment medium has been sent to the bank and the bank sends responds with a payment status message accepting the payment instruction. This can also be fulfilled through Multi-Bank Connectivity (MBC).
  • Status Completed (Stmt. Received): Batch is reconciled by a bank statement.
  • Status Exceptions: Displays batches that were not accepted by bank.

SAP Note Reference : https://me.sap.com/notes/3285645/E 

Payment Status Reports:

 This blog gives the overview and detailed guide on implementing ISO 20022 XML PAIN.002 payment status reports or payment acknowledgement files.

Introduction

Customer Payment Status Reports (ISO 20022 XML – “pain.002.001.03”) gives near real-time actual status updates of payments made from SAP S/4 HANA. It helps to track the end-to-end payment status in the payment lifecycle. These XML files contain group and transaction level status. pain.002.001.03 is a PSR (Payment Status Report) sent from a bank to a customer containing status information regarding a payment order. This can be used to update payment status in the payment status monitor in SAP (BNK_MONI) / Monitor Payment Application.

Levels of Payment Status Reports.

Level 1Validates the file schema or syntax is correct upon receipt of the file.
Level 2Validates each payment transaction in the file and check if all the information needed to process the transaction further downstream is present correctly.
Level 3Validates the payment files have been processed by the bank and confirmation is received at this level. We receive ACSP or ACSC in case of accepted by bank or RJCT in case of rejected by bank as an external status from the bank at this level.
Understanding ISO20022 PAIN.002 XML Schema

ISO20022 XML PAIN.002 file schema is divided into 3 blocks namely.

 

Group HeaderThis block is provided once per PSR and contains fields like Message Id and Id. Message Id is a unique field. (Mandatory Block)
Original Group Information and Status

This block is provided once per PSR and contains values from the outgoing PAIN.001 file, it contains fields like original message ID, original number of transactions, original control sum, and group status. (Mandatory Block)

Original Payment Information and Status

This block is provided multiple times per PSR and contains values from the outgoing PAIN.001 file, it contains important fields like original payment information Id, original instruction Id, original EndtoEnd Id, and reason code. (Optional block)

Map External Status to Internal Status

You can interpret the status codes from the external world. Every incoming status message has a code which can be mapped to an internal status based on a company code and house bank. If an alert needs to be triggered for an external status code, you must define the alert. You can define the alert category using transaction ALRTCATDEF under classification Map External Status to Internal Status.

You can also activate Incomplete Processing of incoming payment files. You use this option when your bank does not provide the complete information about changed statuses of each payment item included in the payment batch.

 

Path – SPRO -> SAP Reference IMG -> Financial Supply Chain Management -> Bank Communication Management -> Payment Status Management -> Map External Status to Internal Status
 1.png

 

Define Logical Directory

In this Customizing activity, you create directories for the following files:

  • Import files
  • Archive files
  • Error files

You need these directories to automatically upload ISO 20022 CustomerPaymentStatusReport XML files from the application server directory to update the status of payment batches that were created in SAP Bank Communication Management.

 

Path – SPRO -> SAP Reference IMG -> Financial Supply Chain Management -> Bank Communication Management -> Payment Status Management -> Define Directories for File Upload

2.png

 

Logical Sequence of Payment Status

SAP accepts logical sequencing of payment statuses while importing the PSR files like Received by Bank followed by Accepted by Bank or Rejected by Bank. SAP will not accept status Accepted by Bank after the batch status has been updated to Rejected by Bank. However, in exceptional scenarios where the bank is sending late rejection, SAP Note 3025112 can be implemented to enable late rejection functionality.

SAP Internal status can be edited or displayed via BS22 transaction. Payment status relevant codes are starting with IBC.

image (10).png

Enable Timeout Notification with Situation Framework

Allows you to enable timeout notifications with the situation framework. You can be informed when no change occurs in the payment batch status during a defined period of time. Use this settings to enable timeout notifications with the situation workflow. You can define that a check is run after the status change of a payment batch in hours and minutes. When there is no change in status, you are informed with notifications by situation framework.

Path – SPRO -> SAP Reference IMG -> Financial Supply Chain Management -> Bank Communication Management -> Payment Status Management -> Enable Timeout Notification with Situation Framework

2.png

Timeout for Batch Status Update

In this IMG activity you can specify a maximum allowed time interval between two status updates. An alert will be triggered after the allowed time elapses.

  • Enter a maximum allowed time for a particular status transition.  You can specify a particular rule ID.

  • You must enter an alert category. The classification of the alert category should be Bank Communication Management: Alerts for Payment Status.

Path – SPRO -> SAP Reference IMG -> Financial Supply Chain Management -> Bank Communication Management -> Payment Status Management ->Timeout for Batch Status Update

Untitled.png

Upload payment status report
Transaction CodeProgram
S_EBJ_98000208RBNK_IMPORT_PAYM_STATUS_REPORT
Screenshot 2024-05-14 184729.png
image (11).png
Payment status update in SAP

image (11).png

List of relevant SAP Notes:

SAP Note Reference : https://me.sap.com/notes/2503973 

SAP Note Reference : https://me.sap.com/notes/2727284 

SAP Note Reference : https://me.sap.com/notes/2930484 

SAP Note Reference : https://me.sap.com/notes/1389302 

SAP Note Reference : https://me.sap.com/notes/2915965 

SAP Note Reference : https://me.sap.com/notes/2975509 

SAP Note Reference : https://me.sap.com/notes/2534292 

 SAP Note Reference : https://me.sap.com/notes/3025112 

SAP Note Reference : https://me.sap.com/notes/1822445 

Payment Batch Status not updating from Sent to Bank to Completed in Monitor Payments app:

Payment Batch Status not updating from Sent to Bank to Completed in Monitor Payments app after payments have been received in bank statements and cleared automatically during the processing of Electronic Bank Statements.

Cause:


App Monitor Payments only displays the status of Payment Batch from CRM. If the status is not updated during the processing of Electronic Bank Statements, there is no update in app Monitor Payments and the Payment Batch stays in it's last status (e.g. Accepted by Bank).

The status of payment batch is not updating from Sent to Bank to Completed because a different interpretation algorithm is used. Hence, no update happens towards BCM (Bank Communication Management) and the batch status remains the same (in most cases Accepted by Bank) in app Monitor Payments.

Resolution:

The payment batch status will only get updated if interpretation algorithm 19 is used. The status of Electronic Bank Statements can be viewed in app Manage Bank Statements.

Interpretation algorithm 19:

You use this algorithm to import those bank statement line items that relate to a previous payment run. All the items for a payment medium generated by the payment program are grouped by means of a DME (data medium exchange) reference number. It can be a primary physical reference number or a secondary logical reference number. Your house bank confirms the overall total for the line items, together with the DME reference number, or the single transactions for the individual invoices with the respective DME reference numbers. In the memo line in the bank statement, the algorithm finds the DME reference number that is used to find and clear all line items in the system.

SAP Note Reference : https://me.sap.com/notes/3136803/E 

Bank Communication Management overview / how to scenarios

  1. General - FAQ
    1577912 FAQ BCM

  2. Customizing Tool: RBNK_ANALYZER
    3292904 BCM Customizing and Data Integrity Analyzer
    3371724 BCM Customizing and Data Integrity Analyzer: Correction pack

  3. Batch
    2775848 BCM: Batch is not created

  4. Approval
    2775947 BCM: Batch is not in Approval List in BNK_APP
    2765633 Workflow-based release of payment proposal and payment approval in BCM

  5. File creation
    2933686 Creation of payment media for payments from financial accounting: overview of possible alternatives
    3286514 BCM - Payment file is generated automatically without approval process
    3299464 BNK_MONI - Attention Batch X: File X not yet created - BNK_GENERAL223
    2415894 SAP BCM: Message F0 386 when creating IDOCs in PMW

  6. Status update
    2534292 Upload a Payment Status Report file using report RBNK_IMPORT_PAYM_STATUS_REPORT
    2727284 During the upload a Payment Status Report file: error BNK_COM_CORE 104 occurs
    2819424 CPON: BCM status update
    2503973 How to reverse the payment document automatically in BCM in the case of rejection
    2414742 BadI BNK_BADI_ORIG_PAYMT_CHG - method ON_REJECT
    2801193 Report RFF110S_REVERSE in case of active BCM and follow on activities in BCM

  7. Inconsistencies
    3374038 BCM: inconsistencies between open work item and payment batch
    3292814 BCM Silent Data Migration is not successfully finished

 

1 Comment
Top kudoed authors