Hierarchy
EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services⤷
IS-B-RA-CL (Application Component) Default Risk and Limit System⤷
FTLM (Package) Financial Services: Limit Management
Basic Data
| Data Element | TB_TMAX |
| Short Description | Posting Deadl. |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | UZEIT | |
| Data Type | TIMS | Time field (hhmmss), stored as char(6) |
| Length | 6 | |
| Decimal Places | 0 | |
| Output Length | 8 | |
| 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 | Post.Dead. |
| Medium | 20 | Posting Deadl. |
| Long | 27 | Posting Deadl. |
| Heading | 27 | Posting Deadl. |
Documentation
Definition
The posting deadline is the time limit after which risk amounts are attributed to the following day.
From this point in time, single transaction checks and reservations are used for checking the newly generated data from end-of-day-processing. You should select a posting deadline that allows enough time to ensure that end-of-day processing (including the post-run update) has finished by this point in time. End-of-day processing is always kept active up to the posting deadline.
If you do not specify a posting deadline (you make no entry), end-of-day processing carries out a maximum of one post-run update step. Then the new data is checked by means of single transaction checks and reservations.
The posting deadline is only relevant if you are using 24-hour capability.
History
| Last changed by/on | SAP | 20020219 |
| SAP Release Created in | 463_20 |
