SAP ABAP Data Element UBC_DT_CESTATE (Status of a Cost Event)
Hierarchy
☛
FINBASIS (Software Component) Fin. Basis
⤷ FIN-FB (Application Component) Financials Basis
⤷ UBC_BASIS (Package) FSCM Biller Consolidator - Basis Functions
⤷ FIN-FB (Application Component) Financials Basis
⤷ UBC_BASIS (Package) FSCM Biller Consolidator - Basis Functions
Basic Data
Data Element | UBC_DT_CESTATE |
Short Description | Status of a Cost Event |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | UBC_DO_CESTATE | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
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 | 6 | Status |
Documentation
Definition
The status of a cost event defines its processing status. There are two types of status:
- New (N)
The cost event has been successfully created. A cost event is either created by the transfer of a cost event from a file or it is directly created in the system.
When cost events are sent to the billing system, only the cost events with status "new" are processed.
- Processed (P)
Once the cost event is successfully transferred to the billing system, the status of the cost event changes from "new" to "processed."
When cost events are deleted, only those with status "processed" are eligible for deletion.
Use
Dependencies
Example
History
Last changed by/on | SAP | 20041006 |
SAP Release Created in | 200 |