Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
FVVW (Package) Treasury Management: Securities
Basic Data
| Data Element | TPM_SEC_ACC_STATUS_TEXT |
| Short Description | Status of a Security Account as a Text Field |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR20 | |
| Data Type | CHAR | Character String |
| Length | 20 | |
| Decimal Places | 0 | |
| Output Length | 20 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Status |
| Medium | 15 | Status |
| Long | 20 | Status |
| Heading | 20 | Status |
Documentation
Definition
The status of a securities account determines whether you can make position changes in the account.
Use
The following status entries are possible:
1. Active: Position changes can be made
2. Locked: No position changes can be made in a locked securities account
Dependencies
When you create a securities account it is given the status 'active'.
You can then only set the status of a securities account to 'locked' if the following conditions are fulfilled:
1. All items in the account have a nominal or unit value equal to zero. Here, the system date is the relevant date for determining the position.
2. No 'planned' status flows exist on the account. If planned flows exist, all the flows must be fixed first before the account can be 'locked'.
Example
Set the status to 'locked' if the corresponding physical bank securities account is to be locked.
History
| Last changed by/on | SAP | 20040819 |
| SAP Release Created in | 500 |
