This function is used to manage the personalization setup for the grouping screens.

At least one standard grouping transaction is delivered with the installation of the software. It can either be modified or deleted with this function, which is also used to create new ones.

It is possible to set up several different transactions for grouping. Each transaction, identified by a code and a description, appears in a selection window upon calling the "Grouping" option.

The essential role of the grouping transaction personalization is to be able to define :

  • the user profile (planner, material buyer, buyer) as well as the authorized actions,
  • the data to be displayed for each of these events.

The Grouping setup is accessible from the transaction setup in the Purchase and Manufacturing modules.

Prerequisite

SEEREFERTTO Refer to documentation Implementation

Screen management

The entry of the setup is carried out by entering information into the header and two tabs.

Header

The transaction header allows the user to create new transaction codes or to look for existing transactions to be modified or deleted. It is comprised of two sections:

Transaction

This is the code identifying the grouping transaction setup. A description is assigned to each setup transaction code. These two items of information appear in the selection window proposed when the grouping function is requested (see the Grouping documentation).

Access code

Transactions can be filtered according to the users, thanks to the introduction of this access code: if the field is assigned, only the users who have this access code in their profile will be able to access the transaction.

If several transactions are setup for a function, and the user only has access to one of them because of the access codes, the selection window is no longer proposed: access is by direct entry.

Grouping

Transaction (field BTSNUM)

This field indicates the code of the setup transaction.
Description (field DESAXX)

Transaction description.
Active (field ENAFLG)

Use this field to activate or deactivate a transaction.
Inactive transactions are not displayed in the transaction selection window.
Access code (field ACSCOD)

This access code is used to restrict access to data by user or group of users.
If this field is entered, only users with this access code in their profile can use this transaction.
If several transactions are available, you can choose the transaction you want to use to open the function. If only one transaction is available, there is no selection to be made: the default entry screen opens directly.
Group (field GFY)

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

Tab Parameter Definitions

This function offers the possibility to group the requirements for the same product-site in a given horizon.

Some transactions can be reserved for use solely in inquiry mode.

The transaction user role is defined: the user can be Planner, Material buyer or Buyer, or finally Sub-contracting planner, in an exclusive and non-cumulative way.

The choice of a role allows the default activation of the corresponding "Manufacturing planning access" "Reorder" or Sub-contracting planning access check boxes.

It is possible to associate a Grouping transaction with a launch transaction dedicated to the automatic launch from the grouping function. If no transaction is planned, the system uses the automatic launch transaction provided by the following general parameters (chapter STO, group MIS):

A selection formula can be entered to filter the WIPs that should be displayed with the transaction.

In the specific case of inter-company orders, the choice is either to display all, only the inter-company orders, or to not display the inter-company orders.

Block number 1

Transaction reserved for inquiry only (field TRSCNL)

This flag is used to specify that the transaction is reserved for inquiry mode only.

Box checked: inquiry mode (no actions possible).

User role

field USRPRF

User profile choice.

User

User (field GESAFF)

Administrator management flag.

Access production plan

Work order planned (field PLNPLN)

The planner's role implies access to various actions.
It is possible to restrict this access via authorization levels by status.
One or several actions correspond to each level:

  • Suggested production
    Deletion of production suggestions.
  • Planned production
    Creation, modification and deletion of planned work orders
  • Firm production
    Creation, modification and deletion of firm work orders
Work order firm (field PLNLAN)
Automatic WO transaction (field MFGTRS)

Code of the release transaction used in work order generation.

This field is optional. If blank, the transaction code attached to the general stock parameter MFGMTSNUM - Automatic WO transaction (chapter STO, group MIS) is used.

Supply

field APPPRF

This setup is used to define the intervention area for a supplier by distinguishing the internal and external supply.

Access subcontract plan

Subcontract planned (field SCOPLN)

The planner's role implies access to various actions.
It is possible to restrict this access via authorization levels by status.
One or several actions correspond to each level:

  • Sub-contracting suggestion
    Deletion of the sub-contracting suggestions
  • Planned sub-contracting
    Creation, modification and deletion of planned sub-contracting orders
  • Firmsub-contracting
    Creation, modification and deletion of firm sub-contracting orders
Subcontract firm (field SCOLAN)
Automatic EO transaction (field SCOTRS)

Code of the release transaction used in subcontract order generation.

This field is optional. If blank, the transaction code attached to the general stock parameter SCOPTRNUM - Automatic EO transaction (chapter STO, group MIS) is used.

Formula

Selection formula (field DEFFOR)

The formula code that will be applied by default.

Intercompany (PO/SO)

field ICPYFLG

This setup is used to distinguish the classic SO/PO orders from the inter-company SO/PO orders.
It is also possible to display dedicated transactions.

Suggestion filter

field MRPFLG

This flag is used to filter the suggestions based on their origin.

Tab Display

It is necessary in the transaction setup to choose which information will be displayed on the screen according to the requirements and the user authorizations for whom the transaction is destined.

This information will be sorted in ascending order of the number that has been entered in the "Entry" column.

Block number 1

Number of lines (field NBRLIG)

This field indicates the maximum number of lines in the grid.
Number of fixed columns (field NBRCOL)

The first N columns specified in this field remain visible on the screen when scrolling.

Grid

Field (field INTIT)
Order (field DAC)

Use this column to define which fields are to be displayed and the order in which those fields are displayed.

 

Block number 3

Update summary log (field TRACE)

Check to obtain a summary log file for the updates.

Specific Buttons

Posting

It is used to validate the screen by generating the corresponding code. This validation is automatic on creation or modification; the button is thus only really useful when deleting a screen file on the application server, or in the case of a copy from one folder to another (the validation is not in this case carried out automatically in the target folder).

This button is used to copy the record definition from or to another folder.

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.