Setup >  Manufacturing >  Entry transactions >  Work orders  

Display all Hide all

Use this function to customize the Work order (GESMFG) function to the needs of your organization and your processes.

Your system is provided with a standard or master Work order entry transaction definition. You can modify the master or create new entry definitions to suit your processes, your users or just to make your system more convenient to use. Each entry definition affects the way in which information is entered, and what information is displayed and printed. 

You create each entry definition as a 'Transaction'. Each transaction you define is available for selection when the Work order function is loaded, either from the menu or from an action in a linked function. The default entry screen will be displayed and a choice will not be offered if you do not define additional transactions to the standard or master Work order entry definition.

 You are advised to get a basic understanding of how your system works before changing the master entry definition.

Prerequisites

SEEREFERTTO Refer to documentation Implementation

Screen management

The Work orders Entry transactions function contains a header information section and one tab per feature of the functionality:

  • Header information. The header information contains the code and name for this entry transaction, and the user access code.
  • Parameters. Use this tab to describe the functional characteristics of this entry transaction.
  • Input. Use this tab to provide default entry, and display, fields and values.
  • Analytical. Use this tab to define the default analytical dimensions applicable to this entry transaction.
  • Documents. Use this tab to define which printed documents are required for this entry transaction.

Header

Presentation

The header information provides key tracking and access information. The header information is displayed with each tab.

Each transaction code you define is available for selection when the Work order function is loaded, either from the menu or an action that accesses the Work order function.

 You must define at least one entry transaction which is dedicated to the automatic work order generation functions (to support the release of order plans). Please refer to the Parameters tab for further information.

Close

 

Fields

The following fields are present on this tab :

Work order

  • Transaction (field MTSNUM)

Code used to identify the transaction set up.
The setup of the entry transaction is used to make the entry screens associated with a processing (release, tracking etc.) fully parameterizable by the user.
For each document or stock transaction type, it is possible to define as many entry transactions as necessary identified by a code.
Each transaction is used to define, both for fields located in the document header and fields entered in the lines, whether the latter must be entered, simply displayed or hidden.
Upon validation of this setup, dedicated entry screens are created, and then they can be used by any user having been granted rights on the access code defined in this setup header.
If a given user has the right to use several transactions of a given type, the choice is presented to the user when entering the function. If the user is only authorized one transaction, this transaction is automatically taken into account when entering the function.

  • field DESAXX

Transaction description.

  • Active (field ENAFLG)

This flag is used to activate or deactivate a transaction.
The inactive transactions are not presented in the transaction selection window.

Access code that is used to restrict access to data by user or group of users.
If this field is assigned, only users with this access code in their profile can use this transaction.
If several transactions are set up for a function, and the user only has access to one of them because of the access codes, the selection window is no longer suggested: the access is by direct entry. 

This field is used to allow access to the transaction to a limited group of companies.

Close

 

Tab Parameters

Presentation

You use this tab to define functional characteristics for this entry transaction. This includes the following information:

  • The default status for the work orders.
  • The ability to manage multiple product releases.
  • Whether work orders can be partially released.
    For a partial release, you should define whether the production folder can be printed or if the work order must be completed before production folder is printed. You must also define an entry transaction which authorizes a full release so that a partial work order can be completed. This is fundamental to the operation of the transaction.
  • The default entry processes to be available to the user such as material allocations (global or detailed) and operation scheduling.

 You must define at least one entry transaction which is dedicated to the automatic work order generation functions (to support the release of order plans). The transaction code must be attached to the general stock parameter MFGMTSNUM - Automatic WO transaction (chapter STO, group MIS).

Close

 

Fields

The following fields are present on this tab :

Use

  • Transaction reserved for automatic generation (field TRSAUTO)

Click this check box if this entry transaction code is dedicated to the automatic work order generation functions (to support the release of order plans).

For example: Enterprise Workbench, Workbench, Groupings and Automatic releases.

 This transaction code must be attached to the general stock parameter MFGMTSNUM - Automatic WO transaction (chapter STO, group MIS).

Authorized statuses

  • Authorization (field MFGSTA)

To set up the authorized statuses.

Grouping

  • Multiple products allowed (field ITMMULT)

Grouping upon release.
Used to authorize or not multi-product releases.

Release mode

  • Full (field MFGMODC)

This field defines the release mode for a work order.

  • Click this check box if both components and routing operations are mandatory. The list of components from the defined bill of materials (BOM) record and the operations in the defined routing will be loaded to the work order automatically. The default order for the list of components reflects the order of the components in the BOM, but can be amended.
  • Leave clear if a work order can initially be raised with only components or routing operations defined.
  • Materials only (field MFGMODM)

This field defines the release mode for a work order.

  • Click this check box if components are mandatory. The list of components from the defined bill of materials (BOM) record will be loaded to the work order automatically. The default order for the list of components reflects the order of the components in the BOM, but can be amended.
  • Leave clear if both components and routing operations are mandatory for a work order, or a work order can initially be raised with only routing operations defined.
  • field TYPMODM

This field is used in conjunction with the Materials only (field MFGMODM) release mode, as follows:

  • To be completed. Initially, only components are mandatory for a work order. A routing number must be defined before a work order can be tracked.
  • Complete. A work order can be released without routing information.
  • Operations only (field MFGMODO)

This field defines the release mode for a work order.

  • Click this check box if routing operations are mandatory. The operations in the defined routing will be loaded to the work order automatically.
  • Leave clear if both components and routing operations are mandatory for a work order, or a work order can initially be raised with only components defined.
  • field TYPMODO

This field is used in conjunction with the Operations only (field MFGMODO) release mode, as follows:

  • To be completed. Initially, only routing operations are mandatory for a work order. Material (component) requirements must be defined before a work order can be tracked.
  • Complete. A work order can be released without material requirements.

Allocations

  • Allocation method (field MODALL)

Assignment method:
- Manual: allocations are carried out solely upon request.
- Automatic: Global allocations are created automatically in creation, modification and deletion mode.

  • Scheduling mode (field MODJAL)

Scheduling mode:

  • Manual: operation scheduling is carried out solely upon request.
  • Automatic: Scheduling is managed automatically.

  • Production Scheduler mode (field MODOPT)

Are work orders submitted for scheduling manually or automatically?

 This field is only available for selection if the Scheduling mode (field MODJAL) is set to 'Automatic'.

  • Print documents (field MODDOS)

Printing mode of the production folder:
- Manual: the folder printing is carried out solely upon request.
- Automatic: printing is carried out automatically upon creation.

Close

 

Tab Input

Presentation

You use this tab to apply default entry, and display, fields and values to this entry transaction. The help for a field in this section might prompt you to think about the effect of selecting the option (check box). For example, whether the first date of availability of a component should be calculated by your system as many factors such as demand, replenishments, free stock and lead times can affect the calculation, potentially leading to a loss in performance.

Where fields can be entered or displayed you can select from the following values:

Entered
The associated field is to enable data entry.

Displayed
The associated field is to be displayed. It is not to be available for data entry.

Hidden
The associated field is not to be displayed and where appropriate, not calculated.

Close

 

Fields

The following fields are present on this tab :

Entry parameters

  • Change release units (field UOMSAI)

Unit entry management flag (where the unit is different from the stock unit).

  • Routing modifiable (field ROUSAI)

Production routing management flag

  • Default quantity (field QTYSAI)

The default release/tracking quantity.

Entry mode

  • Lot (field LOTAFF)

Lot management flag

  • Description (field DESAFF)

Description management flag

  • Destination (field DENAFF)

Ship-to management flag.

  • Project (field PJTAFF)

Project management flag

  • % LT reduction (field REDAFF)

Compression percentage management flag

  • Priority code (field PIOAFF)

Priority code management flag

  • Change request (field CRAFF)

Change request in progress management flag.

  • First availability (field FDMA)

Do you want your system to calculate (suggest) the First Date of Material Availability for components?

 Component availability

Scheduling mode

  • field FIL3

 

  • Scheduling mode (field SCDMODSAI)

This parameter is used to define the scheduling mode: backward/forward/by selection.

  • A transaction dedicated to the automatic release must decide on a scheduling mode.
    SEEINFOThe setup of the automatic scheduling mode of the transaction dedicated to the automatic release applies to:
    - the creation of new WOs,
    - the modification of already scheduled WOs,
    - the modification of WOs that have never been scheduled, set to the "Firm" status during the modification.
     
  • A transaction dedicated to the manual release can leave to the user the choice of the scheduling mode, on a case-by-case basis. The scheduling mode chosen is stored in WO creation for later scheduling,

Materials entry

  • Major version (field ECCCOD)

This parameter is used to define, for this entry transaction, whether the Major version numbermust be:

  • Hidden: the field is not displayed in the entry screen
  • Displayed: The value is displayed but cannot be modified

The management of the version numbers is only carried out at the Lot complement window level.

  • field ECCSCR

Product version location management flag.

  • Minor version (field ECCCODMIN)

This parameter is used to define, for this entry transaction, whether the Minor version number must be:

  • Hidden: the field is not displayed in the entry screen.
  • Displayed: The value is displayed but cannot be modified

The management of the version numbers is only carried out at the Lot complement window level.

  • field ECCSCRMIN

Product version location management flag.

Close

 

Tab Analytical

Presentation

You use this tab to allocate default analytical dimensions to this entry transaction.

Close

 

Fields

The following fields are present on this tab :

Block number 1

  • Header dimensions (field HEACCECOD)

Parameter invisible and not used.

  • Distribution line (field DSPCOD)

 

  • field DSPSCR

 

  • Stock movement dimensions (field STOCCECOD)

Specify for this transaction if the analytical dimension fields related to stock movements must be:

  • Hidden
  • Displayed: The menu Analytical sections, accessible from the menu in the movement detail window, will be available. The fields are displayed but cannot be accessed.
  • Entered: The Analytical dimensions menu, accessible from the menu in the movement detail window, will be available. The fields are displayed and can be accessed.
This screen is common to the entry transactions for the orders and open orders. In the open orders entry transaction, this field is not available.

Released product entry

  • Input (field CCESCR)

Parameter invisible and not used.

Material entry

  • Input (field CCESCR2)

Parameter invisible and not used.

Grid Released product

You can enter an analytical dimension type code on each table line.
Use the function available from the Actions icon to preload all the dimension types defined for the sites of a given group of sites.

  • Method (field CCECOD)

Parameter used to define, for this entry transaction, if the analytical dimension must be:

  • Hidden: The field is not displayed in the entry screen. However, it is possible to initialize this field with a default section code.
  • Displayed: The default value is assigned to the field and displayed but the value is non-modifiable.
  • Entered: The default value is assigned to the field and displayed. It can be modified, and, in that case, the entered value is checked in the analytical dimension table.
    The default value assigned to the analytical dimension is based on the dimension setup performed.

Grid Materials

You can enter an analytical dimension type code on each table line.
Use the function available from the Actions icon to preload all the dimension types defined for the sites of a given group of sites.

  • Method (field CCECOD2)

Parameter used to define, for this entry transaction, if the analytical dimension must be:

  • Hidden: The field is not displayed in the entry screen. However, it is possible to initialize this field with a default section code.
  • Displayed: The default value is assigned to the field and displayed but the value is non-modifiable.
  • Entered: The default value is assigned to the field and displayed. It can be modified, and, in that case, the entered value is checked in the analytical dimension table.
    The default value assigned to the analytical dimension is based on the dimension setup performed.

Operation entry

  • Input (field CCESCR3)

Parameter invisible and not used.

Grid Operations

You can enter an analytical dimension type code on each table line.
Use the function available from the Actions icon to preload all the dimension types defined for the sites of a given group of sites.

  • Method (field CCECOD3)

Parameter used to define, for this entry transaction, if the analytical dimension must be:

  • Hidden: The field is not displayed in the entry screen. However, it is possible to initialize this field with a default section code.
  • Displayed: The default value is assigned to the field and displayed but the value is non-modifiable.
  • Entered: The default value is assigned to the field and displayed. It can be modified, and, in that case, the entered value is checked in the analytical dimension table.
    The default value assigned to the analytical dimension is based on the dimension setup performed.

Close

 

Action icon

Pre-loading dimensions

Click the Preload dimensions action to load the default dimensions defined for a selected group of sites or companies.

 

Close

 

Tab Documents

Presentation

You use this tab to define the documents to print with each work order and the number of copies required.

Close

 

Fields

The following fields are present on this tab :

WO documents

  • Material issue slip (field PICLIS)

When checked, this indicator is used to print out automatically the material issue slip.

Code of the standard document printed during an automatic printing at the end of entry.

Formula used to calculate the number of copies to be printed.

  • Routing sheet (field ROUSHE)

Routing sheet activation flag.


Code of the standard document printed during an automatic printing at the end of entry.

Formula used to calculate the number of copies to be printed.

  • Job ticket (field LABTIK)

When checked, this indicator is used to print out automatically the job ticket.

Code of the standard document printed during an automatic printing at the end of entry.

Formula used to calculate the number of copies to be printed.

  • Production slip (field MFGTIK)

Production slip activation flag.

Code of the standard document printed during an automatic printing at the end of entry.

Formula used to calculate the number of copies to be printed.

  • Technical sheet (field TECCRD)

This checked flag is used to print out automatically the technical records.

Code of the standard document printed during an automatic printing at the end of entry.

Formula used to calculate the number of copies to be printed.

Labeling

  • Labeling (field LBEMOD)

Label management method:

  • manual (print on demand),
  • automatic (automatic print on production reporting)

This automatic functioning is only effective if the production reporting is carried out via the production tracking function.
It is inactive if the production reporting is made via the sub-contracting receipts, the plans or the imports.

Provisional cost documents

  • Provisional cost (field MCCIMPMOD)

The provisional cost calculation is launched at the end of creation or modification of a work order.
It is possible to manage the printing of documents linked to this calculation in the following way:

  • No. No print-out.
  • Report. Print of the summary report on the cost calculation.
  • Trace. Print of the summary log file for the provisional cost calculation.
  • Report and trace. Print of both the report and the log file.

Weighing stations

  • Weighing plan (field MWLFLG)

Selection mode in the weighing plan: - manual (It will be necessary to enter the "weighing plan" function to select the WO) - automatic (The Work Order will be automatically selected in the weighing plan upon creation).

Close

 

Action panel

Click the Validation action to save this entry transaction definition. This triggers the corresponding screens to be generated.

You should view your results to check the display is as you expected. Should you need to make further adjustments you can adjust your definition and revalidate until the results you require are displayed.

The following fields are included on the window opened through this button :

Block number 1

  • field OBJET

 

  • field CLES

 

Block number 2

  • From folder (field DOSORG)

Use this field to define the folder from which the record will be copied. The possible syntaxes are described in the Dedicated appendix.

  • All folders (field TOUDOS)

Use this option to copy the record to all the folders defined in the dictionary (ADOSSIER table of the current solution).

  • To folder (field DOSDES)

Use this field to define the folder to which the record will be copied. The possible syntaxes are described in the Dedicated appendix.

Close

Click the Copy action to copy this entry transaction to a different folder.

Error messages

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

You do not have the access rights for this code

This message is displayed if the access code defined does not exist in the user profile. Select a different access code or (provided you have the authorization) add the requested access code to the user profile.

Report dictionary: XX Record does not exist

You have entered a report reference (in the tab Documents) that does not exist in the Report dictionary.

Tables used

SEEREFERTTO Refer to documentation Implementation