Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
CA-GTF-PS (Application Component) Cross-Application Objects in Project System⤷
BC (Package) Cross-Application Objects PP/PS
Basic Data
| Data Element | CO_GSTRP |
| Short Description | Basic start date |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | DATUM | |
| Data Type | DATS | Date field (YYYYMMDD) stored as char(8) |
| Length | 8 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | START_DATE | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Bsc start |
| Medium | 15 | Bas. start date |
| Long | 20 | Basic start date |
| Heading | 55 | Basic start date |
Documentation
Definition
Supplementary Documentation - CO_GSTRP 0001
Use
Earliest date for the execution of the production order. This date takes into account the float before production.
- If, on order creation, a planned order exists for the production order or process order, then the order dates are taken from the planned order. When scheduling the production order the system tries to adhere to the order dates (if necessary, with reduction measures).
If it is not possible to adhere to the basic dates and if the control parameter in Customizing allows the basic dates to be adjusted, the system adjusts the basic dates of the order during the scheduling run.
If the control parameter in Customizing does not allow the basic dates to be adjusted, the order keeps the basic dates of the planned order.
- If the production order is created manually, you must enter at least one order date manually.
The scheduling type determines, which order dates you must enter.
Examples
- If the system schedules forwards, you must enter the order start date.
- If the system schedules backwards, you must enter the order finish date.
- If the system does not schedule the order, you must enter both the order start date and the order finish date.
Supplementary Documentation - CO_GSTRP 0002
Use
You enter the basic finish date of the refurbishment order in this field.
Procedure
Examples
Dependencies
Supplementary Documentation - CO_GSTRP 0050
Procedure
Enter here the basic start date of the orders for which the manufacturing instructions are to be selected.
The way in which the value entered is interpreted (for example, as a single value or as an interval limit) depends on
- whether you maintain the field only in the left column or also in the right
- which selection option you choose for the value
Supplementary Documentation - CO_GSTRP 0051
Procedure
Enter here the basic start date of the orders for which manufacturing instructions are to be selected.
Use the selection options to determine how the value entered is to be interpreted (for example, as a single value or as an interval limit).
Supplementary Documentation - CO_GSTRP 2120
Use
Start date used to forward schedule the network.
A network is always forward and backward scheduled.
- Forward scheduling calculates the earliest start and finish dates for the activities and the scheduled finish of the network.
- Backward scheduling calculates the latest start and finish dates for the activities and the scheduled start date of the network.
Dependencies
The scheduling type determines whether the network is scheduled forwards or backwards first.
Supplementary Documentation - CO_GSTRP 3010
Use
For the scheduling of the overall network the system calculates
- from all the networks that are linked to one another or
- from all the orders that are linked to one another
the smallest common basic start date as the default value for scheduling.
You can overwrite the default value.
History
| Last changed by/on | SAP | 19990629 |
| SAP Release Created in |
