Account Closure 
Definition
A business object in the Account Management (FS-AM) system that depicts closure of the account contract between the account holder and the contract-managing organizational unit (for example, bank).
In the Account Management (FS-AM) system, account closure is managed as an order by Order Management (FS-AM-OM). When you activate the order, notice on the account is depicted and when you execute it, the actual account closure is depicted. An account closure covers all the functions required to set the contract status on the account to Closed, such as settling the remaining balance and the account settlement.
You can also simulate the account closure so that you know what data will result from the closure, such as the amount of interest incurring.
There is more information in the system. Use transaction fs_am_tech_doc (Technical Documentation for Account Management (FS-AM)).
Structure
The structure definition for account closure is divided into attributes, methods and customer enhancements. Everything in the Order Management section also applies to account closure.
Attributes
· Order Managementattributes
· Notice reason
· Date of receipt of notice
· Planned closure date
· Actual closure date
· Immediate closure
· Cash settlement
· Manual processing
· Value date specification
· Correspondence
¡ Activate
¡ Deactivate
¡ Execute
¡ Reverse
· Reactivation reason
· Deactivation reason
· Settlement reversal
· Actual date of reactivation
· Reference attributes
Reference attributes refer to other Account Management (FS-AM) objects, (account, notice on amount and so on) whose documentation is referred to below in the “Integration” section.
Methods
In Account Management (FS-AM), you can use one of the following three channels to process objects:
· Dialog
· Business Application Programming Interface (BAPI)
The account closure function can use the entry origin or processing origin fields to identify the channel used to process it.
Entry
Origin |
Short Description |
Channel |
BOTOC |
Order for closing an account (online) |
Dialog |
TOCPP |
Order for closing an account (mass processing) |
Dialog |
BAPTOC |
Order for closing an account (BAPI) |
BAPI |
BDTTOC |
Order for closing an account (external data transfer) |
BAPI |
The following overview shows which methods of closing an account can be called up via which channel:
Method |
Channel |
||
Dialog |
BAPI |
DI |
|
Create and enter |
x |
|
|
Create and activate |
x |
x |
|
Create, activate and execute immediately |
x |
x |
|
Change and enter |
x |
|
|
Change and delete |
x |
|
|
Change and activate |
x |
x |
|
Change, 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 |
|
|
|
Simulate account closures |
x |
x |
|
Display simulated settlement data |
x |
x |
|
The methods can change the order status of account closures. On this subject, see the Order Status for Account Closure section.
Dialog
You can call up the following transactions in dialog mode:
Transaction Code |
Short Description |
BCA_OR_TOC |
|
BCA_OR_TOC_PP_BOTC |
|
BCA_OR_TOC_PP_AL |
Business Application Programming Interface
You can call up the following methods using the BAPI Explorer:
Method* |
Short Description |
AccountClosureAM.ChangeAndCancel |
Reverse account closure |
AccountClosureAM.ChangeAndDeactivate |
Deactivate acount cosure |
AccountClosureAM.CreateAndActivate |
Create and activate account closure |
AccountClosureAM.ChangeAndActivate |
Change and activate account closure |
AccountClosureAM.GetActiveByAccount |
Read order number of current account closure |
AccountClosureAM.GetDetail |
Read account closure |
AccountClosureAM.Inquire |
Make inquiries about account closure |
* You can also execute all methods as a test run.
Direct Input
Direct input is not implemented for account closure. You can make external data transfers (EDT) via the BAPIs that have entry origin and processing origin BDTTOC.
Customer Enhancements
The following business transaction events (BTEs) are available to you for closing accounts. You can find the overview of the BTEs with transaction fibf (Business Transaction Events).
Publish&Subscribe BTEs
P&S BTE |
Short Description |
0BCA2000 |
Account closure (CHECK) |
0BCA2001 |
Account closure (OPEN) |
0BCA2002 |
Account closure (SET) |
0BCA2003 |
Account closure (SAVE) |
0BCA2004 |
Account closure (CLOSE) |
0BCA2005 |
Authorization object F_BOTC_FPH |
0BCA2006 |
Authorization object F_BOTC_ORG |
0BCA2007 |
Authorization object F_BOTC_RSN |
0BCA2008 |
Account closure (CREATE) |
0BCA2009 |
Account closure (PREPARE) |
0BCA2010 |
Account closure (CHECK CHANGED) |
0BCA2011 |
Account closure (ACTIVATE) |
0BCA2012 |
Account closure (EXECUTE) |
0BCA2013 |
Account closure (DELETE) |
0BCA2014 |
Account closure (DEACTIVATE) |
0BCA2015 |
Account closure (REVERSE) |
0BCA2016 |
Authorization object F_BOTC_ACT |
0BCA2017 |
Account closure (RESET ACTIVITY) |
0BCA2018 |
Counter for settlement |
0BCA2019 |
Authorization object F_BOTC_FPH |
0BCA2033 |
Account closure (RESET) |
0BCA2034 |
Account closure (INQUIRE), information |
Process Business Transaction Events
Process BTE |
Short Description |
0BCA2000 |
Account closure (CHECK) |
0BCA2001 |
Payment details for cash settlement |
0BCA2002 |
Payment details for payment order |
0BCAA020 |
Print correspondence type BA02 |
0BCAA021 |
Request for correspondence type BA02 |
0BCAA030 |
Print correspondence type BA03 |
0BCAA031 |
Request for correspondence type BA03 |
0BCAA040 |
Print correspondence type BA04 |
0BCAA041 |
Request for correspondence type BA04 |
0BCAA050 |
Print correspondence type BA05 |
0BCAA051 |
Request for correspondence type BA05 |
Integration
You make the settings for closing an account in the Account Management (FS-AM) Customizing settings in the following IMG activities:
· Basic Settings ® Business Transaction Categories ® Edit Descriptions of SAP Business Transaction Categories
· Order Management ® Basic Settings ® Configure Order Category
· Order Management ® Account Closure
® 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 Object to Release Procedure
® Release ® Assign Rule to Release Steps
® Release ® Assign Release WF and Release Procedure WF to Release Procedures
· Product Management ® Product Definition ® Account Products ® Create Account Product / Change Account Product ® Next Screen ® Used Attributes ® Account Closure.
® Payment Details
® Notice Rules
® Reactivation Rules
® Order Attributes
You also have to make the settings for objects generated by the system during the processing of account closure. You do this in the Account Management (FS-AM) Customizing settings.
During the processing of account closures, the related release objects and different authorization objects have controlling functions for the program process flow. The system calls up and edits the following Account Management (FS-AM) objects when processing account closures.
Objects Checked by the System
The system checks whether direct debit orders exist for the account that is to be closed. If this is the case, it outputs messages.
Posting Control
OrderThe system checks whether posting control orders exist for the account that is to be closed. If this is the case, it outputs messages.
The system checks whether information items exist for the account that is to be closed. If this is the case, it outputs messages.
· Account
The system checks the account and outputs messages accordingly if one or more of the following requirements have not been met:
¡ The account exists.
¡ The account has the contract statusActive, Not Yet Used or Active, Used.
¡ The account is not in the release process.
¡ The account has the 0004 Account Closure feature, the traffic light symbol 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 account closure or cash settlement.
¡ The date of receipt of notice is compatible with the account eventdata, such as event 0004 Account Contract Start Date.
¡ The notice reason is permitted.
¡ The reactivation reason is permitted
The system checks whether future items exist for the account that is to be closed. If this is the case, it outputs messages.
· Balance
The system checks whether balances subject to final payment or value date-based balances exist for the account that is to be closed. If this is the case, it outputs messages.
· Prenote
The system checks whether prenotes exist for the account that is to be closed. If this is the case, it outputs messages.
The system checks whether there are payment items in postprocessing or in the release process for the account you want to close. If this is the case, it outputs messages.
The system checks whether the account you want to close is entered as payment details for cards and accounts managed in the Account Management (FS-AM) system. If this is the case, it outputs messages.
The system checks whether payment forms exist for the account that is to be closed. If this is the case, it outputs messages.
Objects Changed by the System
When closing an account, the system checks whether standing orders exist for that account and deactivates them, if applicable.
If the entry origin or processing origin is BDTTOC, the system does not check the standing order.
· Account
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 Change to Account
When executing account closure, the system checks whether PLM documents exist for that account and deactivates them, if applicable.
If the entry origin or processing origin is BDTTOC, the system does not check the PLM document.
Objects Generated by the System
The system generates a change document that meets auditing requirements.
Depending on the setting of product attribute SAPKB1500 003761 (notice on remaining amount through account closure only), the system generates a notice on amount for the remaining amount on the account.
The system executes account settlement and can reverse it if the account closure function successfully completes the reverse operation.
If the entry origin or processing origin is BDTTOC, the system does not execute 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 required:
If the Immediate Closure indicator is not set for an account closure, the system generates a flag for mass processing when you activate the account closure.
The system generates a work item for the release process, if required on the basis of the Customizing settings.
For more information, see the Release Object OR_TOC (Account Closure) section.
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:
¡ Settling the remaining balance using payment detailsspecified by the customer.
¡ Settling the remaining balance on an internal clearing account, if the Cash Settlement indicator is set.
You can make settings for internal clearing accounts in the Account Management (FS-AM) Customizing settings by choosing Order Management ® Account Closure ® Maintain Payment Details for Cash Settlement. SAP also provides you with 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 account closure charges.
¡ Trivial amount
If the remaining balance is lower than or the same as 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.