Setup > Manufacturing > Weekly structures 

Use this function to define shift patterns.

Shift patterns are fixed working patterns that include working days and non-working days within a 7-day week. Each weekly structure or shift can consider shift overlap, shift change times and incidents that regularly affect a shift pattern such as training, holidays and machine downtime.

Weekly structures are associated with work centers.

 You must define an 'empty' weekly structure with each day of the week set to blank. The empty structure is used by the system for factory closures.

Prerequisites

SEEREFERTTO Refer to documentation Implementation

Screen management

The Weekly structure function contains a single screen into which you define a shift pattern for a 7-day week.

Entry screen

Presentation

You use this screen to define a single shift pattern. You are advised to give each shift pattern a logical name such as 3-day shift or 24/7 shift. This will make it easier to assign the correct shift to a work center.

Each working day of the week is attributed to a Time table schema. The schema defines the actual start time and actual end time of the working day. The start and end time of breaks such as lunch breaks or machine downtime might be predefined within the schema. The assigned working pattern is defined in the Time table schemas function (GESDIH).

Close

 

Fields

The following fields are present on this tab :

Weekly structure

  • Weekly structure (field TWD)

Use this field to define the code for this weekly structure. For example, the time structure defines a start time at 8 AM and a end time at 5:42 PM (i.e. 7 hours and 42 minutes of work). A suitable structure code for this scenario would be: 7H42.

Calendars are used for calculating the capacity of a work center.
A calendar can be common to multiple work centers or specific to an individual work centre. It is made up of a succession of periods linked to weekly schedules.

  • Description (field TWDDESAXX)

This long description is used as a title in screens and reports. This title can be translated and is recorded in the user's connection language.
You can add your translation in another language using the Translation function.

  • Click Translation from the Actions icon in the field concerned.
  • In the Translation window, add a new language code with the translation in this language.
  • Short description (field TWDSHOAXX)

Short title used in the screens and reports. This title is recorded in your connection language.

By default the short title, the long title or the column header of a data are recorded (on creation/update) in the connection language of the user.
You can add your translation in another language using the Translation function:

  • Click Translation from the Actions icon in the corresponding field.
  • In the Translation window, add a new language code with the translation in this language.

A user who logs on with this language will view the short description, long description or column header in their connection language if a translation exists. Otherwise, these descriptions will be available in the folder language.

SEEINFOThe connection language must be defined as a default language for thefolder.

Normal capacity

  • 1 day (field DAYCAPNOM)

Use this field to define, in hours, the length of a standard working day for the relevant weekly structure. For example, enter 10:00 if the length of the standard working day, or for the team, is ten hours long. You cannot enter a value that is greater than 24 hours.

Daily capacity

  • field DAYCAP

Use this field to define, in hours, the length of the working day for the relevant weekly structure. For example, enter 10:00 if the working time for the day, or for the team, is ten hours. Leave blank if this is a non-working day.

You cannot enter a value that is greater than 24 hours. Each day of the week is populated by default with the same length of day but can be amended.

  • field TIMUOM

This field displays the unit of time in which this figure is expressed.

Use this field to assign a specific time table schema (or a team schema) to a particular day of the week. The time table schema uses the 24 hour clock. It defines the actual start time and actual end time for this working day or shift. The schema might also include predefined breaks between the start end end time of the shift such as lunch breaks, shift change times and incidents that regularly affect a working day such as machine downtime.

You can attribute a single time, as required, to multiple days of a working week. This field is mandatory if you use a scheduling solution such as Production Scheduler or Sage X3 Web Scheduling.

You can leave this field blank for any working day. For each working day with a blank time table schema the scheduling calculation uses the time table schema defined for the parameter DEFDIH – Default schedule (GPA chapter, LOA group). This can result in an incorrect scheduling calculation if the number of hours defined for the parameter time table schema is greater or less than the daily capacity (field 1 day (field DAYCAPNOM)).

Each day of the week is populated by default with the same schema code but can be amended.

You must define a Time table schema for each working day if you use Production Scheduler, Sage X3 Web Scheduling or any web scheduling solution developed by an ISV (independent software vendor).

Weekly cumulative

  • Total capacity (field WEECUM)

This field displays the total duration of the relevant weekly structure.

  • field TIMUOM8

This field displays the unit of time in which this figure is expressed.

Close

 

Reports

By default, the following reports are associated with this function :

 TABWEEDIA : Weekly structure listing

This can be changed using a different setup.

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

The daily capacity must not exceed 24 hours

This message is displayed if the total daily capacity exceeds 24 hours.

Tables used

SEEREFERTTO Refer to documentation Implementation