!--a11y-->
Card Settlement 
Determines the charges that are to be calculated and posted periodically for cards.
You can call up the following transactions in dialog mode:
· Individual processing
Transaction Code |
Short Description |
BCA_ACBAL_NEXT_DATEC |
|
F996_CARD |
|
BCA_ACBAL_CARD_REV |
|
BCA_CARD_KFG |
· Mass processing
Transaction Code |
Short Description |
F991_CARD |
|
BCA_ACBAL_REVM |
The following Business Transaction Events (BTEs) are available for card settlement. You can find the overview of the BTEs with transaction fibf (Business Transaction Events):
P&S BTE |
Short Description |
0BCA4000 |
Mass run parameters |
0BCA4030 |
Condition differentiation values |
0BCA4040 |
Settlement payment item |
0BCA4050 |
Event-controlled settlement |
0BCA4100 |
Additional information |
0BCA4150 |
BTE: Change settlement postings (credit commission) |
0BCA4180 |
BTE: Customer data in the settlement reversal |
0BCA4250 |
BTE: Checks for card validity |
0BCA4350 |
BTE: Call up postings in GetDetail |
0BCA4470 |
Read/continue processing settlement data |
0BCA4480 |
BTE: Refresh settlement data in the customer table |
0BCA4500 |
BTE: Rounding settlement results |
0BCA4550 |
BTE: Currency conversion of amount limits |
If the settlement date (next due date + shift by x days) specified in the card master data or any closure date is on or before the selection date, a card settlement is carried out by the due date set.

If you want to settle a card that is a participant in a card pool, you receive the default value Settle Card Pool automatically. Participant cards in a card pool cannot be settled outside the card pool. The card pool always has to be settled as one entity.
You also have the option of first simulating the card settlement on the next settlement date. To do this, choose the Simulation on Next Date field. In this field, you can choose between simulation including a check of the posting date for payment transactions and simulation excluding a check of the posting date for payment transactions. No database tables are updated and no postings are made in a simulated settlement run.
The system settles every card of this product in this bank posting area for which the settlement date specified in the card master data (or a possible closure date) is on or before the selection date.
Simulation is also possible.
If errors occur during a card settlement run because individual cards could not be processed, these cards are initially locked for further processing in the context of the settlement tasks (for example, bank statement).
In this case, it is possible to restart the run for the cards with errors.
To do this, proceed as follows:
...
1. Correct the cause of the error.
2. On the SAP Easy Access screen, choose Account Management ® Periodic Tasks ® Card Settlement ® Reset.

If an error occurs when updating the next due date, the whole settlement run is restarted.
Messages that are output frequently (for example, conditions, value date balances, calculation results) are stored in the spool output. In this way, you can decide yourself which information is to be output and which not.
To do this, each mass settlement has the following parameters that you can select:
· Conditions
· Calculation results
· Total calculation results