Ansicht
Dokumentation

/FRE/FU_SCHEDULING - Scheduling

/FRE/FU_SCHEDULING - Scheduling

BAL_S_LOG - Application Log: Log header data   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.
SAP E-Book

Functionality

Scheduling calculates planning dates, order dates, order release dates, delivery dates, availability dates, and replenishment lead times for the target location, and goods issue dates for the source location, depending on the start date entered.

The function module needs the regular source of supply data per location product, imported using IT_SOS_DATA. It must be read via function module /FRE/DB_SOS_DETERMINATION, with parameter I_ONLY_REGULAR set to X .

The calculation of the required dates depends on the master data:

  • If procurement cycles are maintained, the dates are calculated based on these cycles.
  • If no procurement cycles are maintained, but constant periods for the different processes (such as release periods) are maintained, the dates are calculated based on these constant periods.

Thus, the module first tries to read procurement cycle data.

The order time stream contains possible order dates; the delivery time streams contains possible delivery dates.

If procurement cycles data is found,the dates are computed as follows:

Module /FRE/DB_PROCYC_ARRAY_READ provides the required order dates and delivery dates. Depending on those dates, other dates are calculated:

Order date Returned by function module /FRE/DB_PROCYC_ARRAY_READ
Planning date Order date - Order processing time
Release date Planning date + Order proposal release time
Goods issue date Order date + Goods issue time
Delivery date Returned by function module /FRE/DB_PROCYC_ARRAY_READ
Availability date Delivery date + Goods receipt processing time

(Availability date = goods receipt date)

The order dates must be checked against the order time stream of the target location. The delivery dates are checked against the goods receipt time stream of the target location. If a date is invalid, it must be corrected in accordance with the returned correction method of function module /FRE/DB_PROCYC_ARRAY_READ.

If scheduling is not based on procurement cycles, the dates are calculated as follows:

The first possible order date is read by means of the order time stream. The imported date I_DATFR is checked. If it is not an order date, the date is incremented by a day until a valid order date is found.

Planning date Order date - Order processing time

Order date read from order time stream

Release date Order date - Order processing time + Order proposal release time
Goods issue date Order date + Goods issue time
Delivery date Order date + Planned delivery time
Availability date Delivery date + Goods receipt processing time

The calculated order dates are checked against the order time stream of the target location. The delivery dates are checked against the goods receipt time stream of the target location. If a date is invalid, the next valid date is returned.

If several sets of dates need to be calculated, the calculation of the successive dates starts one day after the order date of the predecessor. In the order time stream, the next valid order date is read again by incrementing the date by one day until a valid order date is found, on which the calculation of the other dates is based.

The replenishment lead time is calculated as follows (whether or not procurement cycles are maintained):

Replenishment lead time Availability date - Planning date

Non-working days of the target location are subtracted from the RLT.

Example

Notes

Hint: The system does not check whether a lane is valid until the end of the schedule periods, because it is sufficient for the subsequent process that the lane is valid for the first order date.

Further information





Parameters

CT_SOS_LOOK_AHEAD
ET_SOS_WITHOUT_LISTING
ET_SOS_WITH_DATES
IT_SOS_DATA
I_DATFR
I_DATTO
I_DATTO_MIN
I_NUM_SCHEDULE
I_NUM_WITHOUT_LISTING

Exceptions

/FRE/CX_DB
/FRE/CX_FU
/FRE/CX_FU_ERROR_IN_BADI
/FRE/CX_FU_WRONG_PARAM
CX_STATIC_CHECK

Function Group

/SAPLFU_SCHED

General Material Data   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 5737 Date: 20240329 Time: 155959     sap01-206 ( 85 ms )