SAP ABAP Data Element FNO (JIT: No Past Dates/Times)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ SRM-EBP (Application Component) Enterprise Buyer
⤷ BBP_APPLICATION (Package) Structure Package EBP
⤷ ME (Package) Application development R/3 Purchasing
⤷ SRM-EBP (Application Component) Enterprise Buyer
⤷ BBP_APPLICATION (Package) Structure Package EBP
⤷ ME (Package) Application development R/3 Purchasing
Basic Data
Data Element | FNO |
Short Description | JIT: No Past Dates/Times |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | XFELD | |
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 | 0 | |
Medium | 20 | JIT: No Past D/T |
Long | 40 | JIT: No Past Dates/Times |
Heading | 0 |
Documentation
Definition
Use
If you set this indicator, the system will not create a JIT delivery schedule the next time the function Scheduling agreement -> Generate release is performed.
Dependencies
The creation strategy of the profile takes precedence over the creation strategy that you specify when you generate a release.
You will normally choose the strategy Changed or next date when you generate a release. This results in the selection of all scheduling agreements whose schedule lines have been changed or whose next transmission date is earlier than or the same as the current date.
The creation strategy of the profile then determines for each scheduling agreement whether (and, if so, on the basis of which event) a forecast delivery schedule or a JIT schedule is generated.
History
Last changed by/on | SAP | 20050219 |
SAP Release Created in |