Account Closure
Business object in Account Management (FS-AM) that maps the closure of the account contract between the account holder and the contract-managing organizational unit (such as bank).
The account closure is managed in Account Management (FS-AM)
as an order by Order Management (FS-AM-OM). Notice on the account is mapped when you activate the order and the actual closure is mapped when you execute the order. The account closure carries out all the required functions, such as clearing the remaining balance and the account settlement, to set the contract status on the account to Closed
.
You can also simulate the account closure if you would like to know what data the account closure would lead to, such as the amount of incurred interest.
For more information, see the transaction FS_AM_TECH_DOC
(Technical Documentation for Account Management (FS-AM)
) in the system.
The structure definition for account closure comprises attributes, methods, and customer enhancements. Everything described in the Order Management section also applies to the account closure.
Attributes of Order Management
Notice/cancellation reason
Date of receipt of notice
Planned closure date
Actual closure date
Immediate closure
Cash settlement
Manual processing
Value date
Correspondence
Activate
Deactivate
Execute
Reverse
Reactivation reason
Deactivation reason
Settlement reversal
Actual reactivation date
Reference attributes
The reference attributes refer to other objects (such as account, notice on amount) in Account Management (FS-AM)
. See the documentation linked to below in the Integration
section.
In Account Management (FS-AM)
, you can use one of the following channels for processing objects:
Dialog
Business Application Programming Interface (BAPI)
Direct Input
Enterprise Services
The account closure function can use the Entry Origin or Processing Origin field to identify the channel used to process it.
Entry Origin, Processing Origin | Short Description | Channel |
|---|---|---|
| Order for account closure (dialog) | Dialog |
| Order for account closure (mass processing) | Dialog |
| Order for account closure (BAPI) | BAPI |
| Order for account closure (EDT) | BAPI |
The following overview shows which methods of account closure can be called up via which channel:
Method | Channel | ||
|---|---|---|---|
Dialog | BAPI | DI | |
Create and enter | x | ||
Create and activate | x | x | |
Create and activate and execute immediately | x | x | |
Change and enter | x | ||
Change and delete | x | ||
Change and activate | x | x | |
Change and activate and execute immediately | x | x | |
Change and execute in mass run | x | ||
Change and partially execute in mass run | x | ||
Change and deactivate | x | x | |
Change and reverse | x | x | |
Display | x | ||
Read | x | ||
Read current account closure of an account | x | ||
Simulate account closure | x | x | |
Display simulated settlement data | x | x | |
The methods can change the order status of the account closures. On this subject, see the Order Status of Account Closure section.
You can call up the following transactions in dialog mode:
Transaction Code | Short Description |
|---|---|
| |
| |
|
You can call the following methods using BAPI Explorer:
Method* | Short Description |
|---|---|
AccountClosureAM.ChangeAndCancel | Reverse account closure |
AccountClosureAM.ChangeAndDeactivate | Deactivate account closure |
AccountClosureAM.CreateAndActivate | Create and activate account closure |
AccountClosureAM.ChangeAndActivate | Change and activate account closure |
AccountClosureAM.GetActiveByAccount | Read the order number of the current account closure of an account |
AccountClosureAM.GetDetail | Read account closure |
AccountClosureAM.Inquire | Execute information about account closure |
* You can also execute all the methods in a test run.
Direct Input
is not implemented for account closure. You can make external data transfers (EDT) by means of the BAPIs that have entry origin and processing origin BDTTOC
.
You can use enterprise services of the business object Current Account Contract Cancel Request
. For more information, see SAP Help Portal under http://help.sap.com/
The following business transaction events (BTEs) are available to you for account closures: For an overview of the BTEs, use transaction FIBF
(Business Transaction Events
):
P&S BTE | Short Description |
|---|---|
| Account closure (CHECK) |
| Account closure (OPEN) |
| Account closure (SET) |
| Account closure (SAVE) |
| Account closure (CLOSE) |
| Authorization Object |
| Authorization Object |
| Authorization Object |
| Account closure (CREATE) |
| Account closure (PREPARE) |
| Account closure (CHECK CHANGED) |
| Account closure (ACTIVATE) |
| Account closure (EXECUTE) |
| Account closure (DELETE) |
| Account closure (DEACTIVATE) |
| Account closure (REVERSE) |
| Authorization Object |
| Account closure (RESET ACTIVITY) |
| Counter for settlement |
| Authorization Object |
| Account closure (RESET) |
| Account closure (INQUIRE), information |
Process BTE | Short Description |
|---|---|
| Account closure (CHECK) |
| Payment details for cash settlement |
| Payment details for payment order |
| Print correspondence type BA02 |
| Request for correspondence type BA02 |
| Print correspondence type BA03 |
| Request for correspondence type BA03 |
| Print correspondence type BA04 |
| Request for correspondence type BA04 |
| Print correspondence type BA05 |
| Request for correspondence type BA05 |
You make the settings for account closures in Customizing for Account Management (FS-AM)
in the following Customizing activities:
Define Number Range Interval for Account Closure
Define Notice Reasons for Account Closure
Assign Notice on Amount Reason to an Account Closure Reason
Define Reactivation Reasons for Account Closure
Define Deactivation Reasons for Account Closure
Define Payment Details for Cash Settlement
Define Display of Change Documents
Change Message Control
Release
Assign Release Procedure to Release Object
Assign Rules to Release Steps
Assign Release WF and Release Procedure WF to Release Procedures
Payment Details
Notice Rules
Reactivation Rules
Order Attributes
In addition, you must make the settings for the objects the system generates when processing account closures in Customizing for Account Management (FS-AM)
.
When you are processing account closures, the corresponding release object and the various authorization objects have a controlling function for the program flow. For more information, see Authorization Administration in Account Management. The system calls up and processes the following objects in Account Management (FS-AM)
when processing account closures.
The system checks whether there are direct debit orders for the account to be closed and displays messages accordingly if this is the case.
The system checks whether there are posting control orders for the account to be closed and displays messages accordingly if this is the case.
The system checks whether there are information items for the account to be closed and displays messages accordingly if this is the case.
The system checks the account and displays messages accordingly if one or more of the following requirements have not been met:
The account exists.
The contract status of the account is Active, NotYet Used or Active, Used.
The account is not in the release process.
The account has the 0004 Account Closure
feature, the traffic light is green, and this feature is not locked.
For more information, see the Editing Features section.
The account is not part of a master contract.
No product change (account) is scheduled for the account.
Payment details exist for the account closure or the cash settlement.
The date of receipt of notice is compatible with the account event dates, such as event 0004 Account Contract Start Date
.
The notice reason is permitted.
The reactivation reason is permitted.
Items in Future
The system checks whether there are items in the future for the account to be closed and displays messages accordingly if this is the case.
The system checks whether there are subject to final payment balances or value date balances for the account to be closed and displays messages accordingly if this is the case.
The system checks whether there are prenotes for the account to be closed and displays messages accordingly if this is the case.
The system checks whether there are payment items in postprocessing or in the release process for the account to be closed. The system displays messages accordingly if this is the case.
Payment Details
The system checks whether the account to be closed is entered as payment details for cards and accounts that are managed inAccount Management (FS-AM)
. The system displays messages accordingly if this is the case.
The system checks whether there are payment forms for the account to be closed and displays messages accordingly if this is the case.
When executing the account closure, the system checks whether standing orders exist for the account being closed and deactivates them.
If the entry origin or processing origin is BDTTOC
, the system does not check the standing order.
The system changes the following data on the account:
Date of event 0005 Planned Account Closure
when the account closure is activated
Date of event 0011 Actual Account Closure
when the account closure is executed
Contract status (Being Closed
or Closed
)
Payment details for the account closure
Date of event 0003 Last Account Change
When executing the account closure, the system checks whether PLM documents exist for the account being closed and deactivates them.
If the entry origin or processing origin is BDTTOC
, the system does not check the PLM document.
The system generates a change document that meets auditing requirements.
Depending on the setting for the product attribute SAPKBI500 003761 (notice on remaining amount through account closure only), the system generates a notice on amount for the amount remaining on the account.
The system carries out the account settlement and can reverse the account settlement if the reversal operation runs successfully for the account closure itself.
If the entry origin or processing origin is BDTTOC, the system does not carry out an account settlement.
The system generates a closing bank statement.
If the entry origin or processing origin is BDTTOC
, the system does not generate a bank statement.
The system generates a correspondence request for the following operations, if necessary:
When you activate an account closure, if the Immediate Closure
indicator is not set, the system generates a flag for mass processing.
Work Item
The system generates a work item for the release process, if required on the basis of the Customizing settings.
For more information, see Release Object: OR_TOC (Account Closure).
If the entry origin or processing origin is BDTTOC
, the system does not generate a work item.
The system generates a payment order in the following two cases:
Settlement of the remaining balance to the payment details specified by the customer.
Settlement of the remaining balance to an internal clearing account if the Cash Settlement
indicator is set.
Note
You can set the internal clearing account in Customizing for Account Management (FS-AM)
under . SAP also provides you with the BTE 0BCA2001 Payment Details
for changing the internal clearing account.
If the entry origin or processing origin is BDTTOC
, the system does not generate a payment order.
The system generates payment items in the following cases:
Settlement payment item
Account closure charges
The system generates a payment item for posting the account closure charges.
Trivial amount
If the remaining balance is less than or equal to the trivial amount, the system generates a payment item to settle this remaining balance.
If the entry origin or processing origin is BDTTOC
, the system does not generate any payment items.