Hierarchy
ECC-DIMP (Software Component) DIMP⤷
IS-A-EMM (Application Component) Enhancements to scheduling agreements MM (Outbound)⤷
ISAUTO_ME (Package) ISAUTO: Purchasing
Basic Data
| Data Element | BRSVZ |
| Short Description | Backlog/Immediate Requirement Brought Forward |
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 | 10 | B/IRqt BF |
| Medium | 0 | |
| Long | 29 | Backlog/Imm. Req. Br. Forward |
| Heading | 0 |
Documentation
Definition
Indicator to mark whether the backlog/immediate requirement applies to the SA release date or to the day before (the SA release date).
Use
Usually, the backlog/immediate requirement in the SA release applies to the SA release date, meaning that planned schedule lines with a date earlier than/equal to the SA release date on creation of the SA release are identified as a backlog or an immediate requirement in the SA release.
Dependencies
By using an indicator in the creation profile, you can deviate from the above procedure and use the day prior to the SA release date as the reference date for the backlog/immediate requirement.
If the date is brought forward in the profile as a result, this indicator is set in the SA release header, and you can see that the reference date for the backlog and immediate requirement is the day prior to the SA release date.
Example
History
| Last changed by/on | SAP | 20050301 |
| SAP Release Created in |
