Datasheet

Release Notes - New Features included in Release 2.4.0
Page 33 of 89
outstanding TPS can be scheduled from the start of next week with no need to consider the resource
requirements of the current week’s production orders.
Production orders are excluded from a schedule by selecting new value ‘I’gnore for existing
parameter ‘MPS Schedule Mode’. Existing values for this parameter are ‘A’ctual, ‘H’istoric and
‘P’lanned. A default value is defined via SHMG, Scheduling Management. The dataname is
SCHSTIND.
The ‘MPS Schedule Mode’ parameter is defined for a schedule when it is created by the SHAD
transaction, and applies for the life of the schedule.
If ‘MPS Schedule Mode’ of ‘I’gnore is selected, then associated parameter ‘MPS Resources’,
dataname MPSRESORIG, is no longer relevant and is defaulted to space.
Netting off MPS that falls within the schedule freeze against TPS on the schedule still takes place
for new option ‘I’gnore. For further details on netting off MPS, refer to Help on SHMN, Schedule
Management.
Further MPS can be added at line loading via the SLLD transaction if the schedule is for a specific
item, product group or controller. Refer to Help on SLLD for full details. As for SHAD, if the
schedule has an ‘MPS Schedule Mode’ of ‘I’gnore, then SLLD does not copy any further MPS to
the schedule. Progression of a schedule with ‘MPS Schedule Mode’ of ‘I’gnore is no different to
that of the other values of ‘MPS Schedule Mode’. The schedule freeze still applies in the same way,
for example SPPL defaults to start scheduling the outstanding TPS demand from the schedule
freeze date, i.e. not within the freeze.
Prior to this enhancement, production orders that fell within the schedule freeze were always
automatically copied to a plant schedule as MPS. These production orders were scheduled by SPPL,
Plant Scheduling, consuming resource.
4.2.8 Scheduling Link (SLNK)
4.2.8.1 S-Plan Ad-hoc Messages (New SPAM Transaction) (SR4230)
TROPOS interfaces with Greycon’s S-Plan Schedule Manager by writing messages to a table,
which are then processed via Greycon’s Integration Manager. These messages are produced via
SPSE (Static Data Extract) and SPDE (Dynamic Data Extract) which also maintains a history of
what messages have been sent to allow subsequent processing to control whether add or modify
messages should be sent.
This transaction has been provided to allow the ad-hoc generation of messages that are not
produced via the normal extract transactions. It is envisaged that this transaction will generally be
used via SDK programs which will format the messages according to the individual requirements.
The format of allowed messages and the mandatory date for each message are described in the
Integration Manager User Guide. This transaction can be used to format the messages contained
within the Specific Table Operations section of this document.
To allow easier use by SDK programs there is 1000 character end of template field to negate the
need to split the required message into the 100 character screen fields.