Hierarchy
BBPCRM (Software Component) BBPCRM⤷
SRM-EBP (Application Component) Enterprise Buyer⤷
BBP_APPLICATION (Package) Structure Package EBP⤷
ME (Package) Application development R/3 Purchasing
Basic Data
| Data Element | FTAGG |
| Short Description | JIT Delivery Schedule Creation with Daily Aggregation |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ANZTA | |
| 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 | 10 | Daily |
| Medium | 20 | Daily Aggregation |
| Long | 40 | JIT Schedule with Daily Aggregation |
| Heading | 25 | Daily Aggregation |
Documentation
Definition
In the case of daily aggregation, several lines from your overall delivery schedule are totaled for each day and shown in the JIT schedule transmitted to the vendor as the daily required quantity in each case.
Use
Enter the number of workdays for which the individual scheduled quantities are to be aggregated.
Examples
You have specified daily aggregation for 10 workdays. On 05.13, you generate a JIT delivery schedule. Your current overall schedule shows that you need 50 tons of Steel 1 on each of the following dates and times: 05.13., 05.14., 05.15. and 05.16. at 9:00 hrs and 14:00 hrs in each case.
When you create the JIT delivery schedule and transmit it to your vendor, it will show the latter that you require 100 tons of Steel 1 on each of the dates 05.14., 05.15, and 05.16.
Note:
The schedule lines for 05.13. will not be aggregated but shown in the JIT schedule as immediate requirements.
History
| Last changed by/on | SAP | 19990412 |
| SAP Release Created in |
