A set that is used to define the structure of a schedule. A segment set consists of a number of segments.
The segment set is used for schedule regeneration and for clustering schedule lines. No segment sets are used for pull call-off schedules.
Segment Set - Segments (tdipu0114m000)Use this session to maintain segments by segment set. You can define segment codes in the Schedule Segments (tdipu0115m000) session. You can define segment sets in the Schedule Segment Sets (tdipu0113m000) session. If you use nonreferenced schedules, segment sets are used to:
If you use referenced schedules, no segment sets are used because these schedules are immediately put into a purchase release with the status Scheduled. Consequently, the requirement type is always Firm.
Segment Set A set that is used to define the structure of a schedule. A segment set consists of a number of segments. The segment set is used for schedule regeneration and for clustering schedule lines. No segment sets are used for pull call-off schedules. Segment Description The description or name of the code. Requirement Type The requirement type linked to the segment (code). Allowed values Segment Time Unit The time unit in which the segment is expressed, for example days, weeks, months, and so on. Allowed values Segment Length The period that is assigned to the segment. The period is expressed in the segment time unit. Sequence Number The number that identifies a data record or a step in a sequence of activities. Sequence numbers are used in many contexts. Usually LN generates the sequence number for the next item or step. Depending on the context, you can overwrite this number. You can sometimes influence the numbering by setting the corresponding parameters. Note This number is automatically assigned by LN, based on the following procedure:
| |||