consolut - /SAPAPO/OM_TIMESTREAM_CHANGE - Create/Change/Delete Time Stream

/SAPAPO/OM_TIMESTREAM_CHANGE - Create/Change/Delete Time Stream

rdisp/max_wprun_time - Maximum work process run time SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up
This documentation is copyright by SAP AG.

Functionality

This function module calls an APO liveCache COM routine that creates, deletes, or changes a time stream in liveCache (depending on the parameter IV_METHOD).

The time stream defines work buckets, breaks, and shifts, as well efficiency and capacity supply in these buckets.

As well as the internal APO timestream ID (as a GUID), this function module also expects the table IT_TIMESTREAM.Each row of this table defines a time interval, which itself contains a work period, such as a shift or part of a shift. This table contains the following fields:

(The following defaults apply outside the periods defined by the table: net = gross; efficiency = 100%; no breaks; capacity supply is 1 (we require another default for multi-activity resources here).)

START_TSTAMP (DEC 15):

Start time of the working time interval (referring to UTC time).

END_TSTAMP (DEC 15):

End time of the working time interval

o,,NETTO_KUM (INT4):

Cumulated net working time (in seconds). This field cumulates the net working times across all preceding working time intervals in the time stream.

Take a table with n rows; in the following, 0<=i<=n-1.

row(i) indicates a working time i that consists of the following:

start(i) indicates START_TSTAMP for working time i

end(i) indicates END_TSTAMP for working time i

break(i) indicates the break between working time i and i+1

net(i) is NETTO_KUM

The following applies:

start(i+1) = end(i) + break(i).

The duration of a scheduled break is specified implicitly by the time gap between two table rows. Abreak can also have a length of 0, for example when a change of shifts happens without a break, or if the efficiency or capacity supply changes.

net(i+1) = net(i) +

(end(i+1) - start(i+1))

* (100 - unscheduled break(i+1)) /100

Remember that the net value already contains unscheduled breaks:

If net(i+1)-net(i) < end(i+1) - start(i+1), then the difference consists of unscheduled breaks.

REAL_KUM (INT4):

Cumulated real (effective) working time (in seconds). Unlike the net time, the efficiency is included in the real time. Real working time = net working time * efficiency / 100;

real(i+1) = real(i) + (end(i+1)-start(i+1)

*(100-unscheduledBreak(i+1))

* efficiency(i+1)/ 10000

TOTAL_KUM (INT4):

Cumulated total working time (in seconds). The total working time includes the preceding break as workingtime, in addition to the real working time of the interval. The break time is modified by the still valid efficiency from the preceding period.

total(i+1) = real(i) + break(i) * efficiency(i)/ 100

CAPACITY (INT4):

The capacity supply that applies for each time in the total working time interval. For example, thesupply for a single activity resource is usually 1, which means that at the most one activity can be processed without overload. You can model downtime with supply of 0.

If you have a group of k machines, a supply value of k would mean that k activities can run in parallel.

This means that the capacity supply for the total period is the following product:

(net(i+1) - net(i)) * capacity(i)

NEW_SHIFT (INT1):

Flag indicating a change in shift. NEW_SHIFT = 0 if the working time interval belongs to the same shift as the preceding interval. NEW_SHIFT = 1 if a new shift starts.

The time stream in liveCache is used primarily to schedule resources efficiently. The NETTO_KUM field is used here.

The field REAL_KUM is used to determine the effective processing time for an activity from its net processing time. The time stream functions always schedule the start times and end times in work buckets.

The field TOTAL_KUM is used to schedule activities in break times or on public holidays, and so on. It also enables activities to start or end in these periods.