SAP ABAP Data Element TPERI (Period of route allocation)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ VL (Package) WS-SHP: General Processing for Shipping
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ VL (Package) WS-SHP: General Processing for Shipping
Basic Data
Data Element | TPERI |
Short Description | Period of route allocation |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | TPERI | |
Data Type | NUMC | Character string with only digits |
Length | 3 | |
Decimal Places | 0 | |
Output Length | 3 | |
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 | 7 | Period |
Medium | 7 | Period |
Long | 7 | Period |
Heading | 2 | Pe |
Documentation
Definition
Period in which the route schedule search is taken into consideration.
Dependencies
The evaluation takes place in connection with the field "Year":
- If this field is empty, the field "year" is also empty.
The period defines a calendar week of the year.
This is an entry that is valid on a general basis. - If the field is filled, the field "year" is also filled.
This is then a specific entry.
Use
The following situations are now possible:
- Stuation 1:
For each influencing factor in the route schedule search there is exactly one generally valid entry.
This entry is then used at each time for the search.
- Situation 2:
For each influencing factor in the route schedule search, there is exactly one generally valid entry and a specific entry.
The specific entry is used exactly for the specified calendar week for the search. In other periods, the generally valid entry is used.
History
Last changed by/on | SAP | 19971006 |
SAP Release Created in |