SAP ABAP Data Element JBDKGUEL (Validity Date for Determining Costing Rule)
Hierarchy
☛
EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services
⤷ IS-B-DP (Application Component) Transaction Data Pool
⤷ JBD (Package) Application development IS-B Data Pool
⤷ IS-B-DP (Application Component) Transaction Data Pool
⤷ JBD (Package) Application development IS-B Data Pool
Basic Data
Data Element | JBDKGUEL |
Short Description | Validity Date for Determining Costing Rule |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | DATUM | |
Data Type | DATS | Date field (YYYYMMDD) stored as char(8) |
Length | 8 | |
Decimal Places | 0 | |
Output Length | 10 | |
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 | CR Val.Dte |
Medium | 15 | Co.Rule Val.Dte |
Long | 20 | Cost.Rule.Valid Date |
Heading | 0 |
Documentation
Definition
Date used to determine the costing rule for a transaction.
Use
A bank product may be assigned various costing rules in different time periods. Via the validity date for costing rule determination you define, per transaction, which validity date is used to determine the costing rule. The date is filled in the process of data transfer i.e. the default value is the entry date (CPU date).
Example
Within the framework of data transfer, you could determine that transactions for certain bank products are costed using the costing rule valid at the start of the transaction, while transactions for other bank products are costed based on the costing rule valid at the time of data transfer.
History
Last changed by/on | SAP | 20011002 |
SAP Release Created in |