Account Holder Change 
Definition
A business object in the Account Management (FS-AM system that depicts the transition of an account from one (old) account holder to a new account holder.
In the Account Management (FS-AM) system, the account holder change is a feature of the account. In the Product Configurator, an account holder change is represented by feature attribute SAPKBI500 003193 (Account Holder Change).
The account holder change is managed in the Account Management (FS-AM) system as an order. It uses the structured model of Order Management (FS-AM-OM). The order data is stored in tables BCA_ORDER (general attributes) and BCA_OR_TOC (special attributes).
Before reaching a defined final status, an order has various order statuses. When you enter the order – order status 0100 (entered) – the account holder change is flagged. When you execute it – order status 0120 (executed) – the actual change of account holder is depicted.
For an account holder change, the history and data of the account, such as the account number and the product category, remain the same.
Use
You can create, change, display, execute, save and delete account holder changes in the Account Management system. For more information on creating, changing, displaying, executing, saving and deleting account holder changes, see the Account Holder Change section in the SAP Library.
Structure
The structure definition for an account holder change is divided into attributes, methods and customer enhancements. Everything in the Order Management section also applies to account holder change.
Attributes
· Attributes of Order Management
· Account holder before the account holder change
· Account holder after the account holder change
· Account holder change reason
· Account holder change date
· Correspondence before the account holder change
· Correspondence after the account holder change
· Attributes of the object list
· Method
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 holder change function can use the Entry Origin or Processing Origin fields to identify the channel used to process it.
Entry Origin |
Short Description |
Channel |
BOCAH |
Order for account holder change (dialog) |
Dialog |
BAPCAH |
Order for account holder change (BAPI) |
BAPI |
BDTCAH |
Order for account holder change (EDT) |
BAPI |
The following overview shows which methods you can call up for the account holder change via which methods:
Method |
Channel |
||
Dialog |
BAPI |
DI |
|
Create |
x |
|
|
Change |
x |
|
|
Execute |
x |
|
|
Delete |
x |
|
|
Create and execute immediately |
x |
x |
|
Change and execute immediately |
x |
x |
|
Display |
x |
x |
|
Read Customizing settings of object list |
|
x |
|
Read all account holder changes for an account |
|
x |
|
The methods can change the order status of the account holder change. For detailed information on the order status, see the Order Status of an Account Holder Changesection.
Dialog
You can call up the following transaction in dialog processing:
Transaction Code |
Short Description |
BCA_OR_CAH |
Business Application Programming Interface
You can call up the following methods using the BAPI Explorer:
Method* |
Short Description |
AccountHolderChange.GetOrdersByAccount |
Read all account holder changes for an account |
AccountHolderChange.GetObjectList |
Read Customizing settings of object list |
AccountHolderChange.GetDetail |
Read account holder change |
AccountHolderChange.ChangeAndExecute |
Change and execute account holder change |
AccountHolderChange.CreateAndExecute |
Create and execute account holder change |
Direct Input
Direct input is not implemented for an account holder change. You can make external data transfers (EDT) via the BAPIs that have entry origin and processing origin BDTCAH.
Customer Enhancements
The following Business Transaction Events (BTEs) are available to you for an account holder change: You can find the overview of the BTEs with transaction fibf (Business Transaction Events).
Publish&Subscribe BTEs
P&S BTE |
Short Description |
0BCA2601 |
Account holder change (OPEN) |
0BCA2602 |
Account holder change (CREATE) |
0BCA2603 |
Account holder change (CHECK) |
0BCA2604 |
Account holder change (CHECK CHANGED) |
0BCA2605 |
Account holder change (SET) |
0BCA2606 |
Account holder change (EXECUTE) |
0BCA2607 |
Account holder change (DELETE) |
0BCA2609 |
Account holder change (RESET ACTIVITY) |
0BCA2610 |
Account holder change (PREPARE) |
0BCA2611 |
Account holder change (SAVE) |
0BCA2612 |
Account holder change (CLOSE) |
0BCA2614 |
Authorization object F_BOCA_ACT |
0BCA2616 |
Authorization object F_BOCA_FCT |
0BCA2617 |
Authorization object F_BOCA_ORG |
0BCA2618 |
Authorization object F_BOCA_RSN |
Process Business Transaction Events
Process BTE |
Short Description |
0BCA2620 |
Account holder change: Object list enhancement |
0BCA2621 |
Account holder change: Determine new general ledger group |
0BCAAH10 |
Print correspondence type BAH1 |
0BCAAH11 |
Request for correspondence type BAH1 |
Customizing
You make the settings for account product change in the Account Management (FS-AM) Customizing settings under the following nodes or in the following IMG activities:
· Basic Settings ® Business Transaction Categories
· Order Management ® Basic Settings ® Configure Order Category
· Order Management ® Account Holder Change
Integration
When you are processing account holder changes, the corresponding release object and the various authorization objects have a controlling function for the program flow.
The system checks the following settings and attributes of the products:
· Is changing the account from the old to the new account permitted according to the account holder change Customizing settings? If this is not the case, the system outputs an error message.
· Is the release status of the account holder change In Release on the planned account holder change date when it is being executed? If this is not the case, the system outputs an error message.
· Is the release status of the account holder change In Release on the actual account holder change date when it is being executed? If this is not the case, the system outputs an error message.
Using the object list of the account holder change you control whether the system also changes other objects as a result of the changed account holder. For more information about editing the object list, see the Object List for the Account Holder Change section, and in the Object List for the Account Holder Change documentation using transaction fs_am_tech_doc.
For information on objects in Account Management (FS-AM) that the system calls up and edits when processing an account holder change, see the documentation of Application Programming Interface BCA_API_OR_CAH_EXECUTE_HANDLE (API: Execute Order for Account Holder Change).
Other Objects
Change
DocumentThe system generates a change document that meets auditing requirements.
The system generates correspondence requests for the old and the new account holder.
The system generates a work item for the release process, if required on the basis of the Customizing settings.