Use this function to customize the Enterprise planning (FUNGBENCH) function to the needs of your organization and your processes.

Your system is provided with a standard or master Enterprise planning entry format. You can modify the master or create new entry formats to suit your processes, your users or just to make your system more convenient to use. Each format affects the way in which information is entered, displayed and printed.

You create each entry format as a Transaction. Each transaction you define is available for selection when the Enterprise planning function is selected from the menu. You are advised, however, to get a basic understanding of how your system works before changing the master format.

The Enterprise planning Entry transactions will be available for both purchasing planning (function FUNGBENCHA) and production planning (FUNGBENCH).

Prerequisites

SEEREFERTTO Refer to documentation Implementation

Screen management

The Enterprise planning 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.
  • Selections. Use this tab to provide the transactions to be included in the planning.
  • Display. Use this tab to provide the default display fields and layout.

Header

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 Enterprise planning function is selected from the menu.

Enterprise planning

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)

Tab Parameters

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

  • The target user role.
  • The events that can be acted upon by the target user.
    • A 'planner' workbench is largely the reorder events linked to production and subcontract management.
    • A 'buyer' workbench is largely the reorder events linked to purchasing and inter-site transfers.
  • Whether a Planning workbench and site group is to be associated with this entry transaction to enable them to be loaded from within the Enterprise planning (FUNGBENCH) function.
  • The selection formula to be used for filtering on orders in progress.

 You should define at least one entry transaction which is dedicated to the automatic work order generation functions and the subcontract order generation functions. The transaction code must be attached to the general stock parameters MFGMTSNUM - Automatic WO transaction (chapter STO, group MIS) and SCOPTRNUM - Automatic EO transaction (chapter STO, group MIS) respectively.

User role

Planner (field PLANNER)

This flag is used to activate actions on the work orders.
Planner/Buyer (field BUYER)

This flag is used to activate actions on supplier orders.

User

field GESAFF

Administrator management flag.

Planner access

Work order suggestion (field PLNSUG)

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
Subcontract suggestion (field SCOSUG)

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
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
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
Work order firm (field PLNLAN)

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
Subcontract firm (field SCOLAN)

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

Planner/buyer access

PO suggested (field APPSUG)

The material buyer'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:

  • Purchase suggestion
    Deletion of purchase suggestions
  • Planned purchase
    Creation, modification and deletion of planned purchases
  • Firm purchase
    Creation, modification and deletion of firm purchases
  • Inter-site suggestion
    Deletion of inter-site suggestions
  • Planned inter-site order
    Creation, modification and deletion of planned inter-site orders
  • Firm inter-site order
    Creation, modification and deletion of firm inter-site orders

     
 
    Transfer suggested (field INTSUG)
    PO planned (field APPPLN)
    Transfer planned (field INTPLN)
    PO firm (field APPLAN)
    Transfer firm (field INTLAN)

    Associated transactions

    Planning workbench (field DBENCHTRS)

    Number of the associated transaction of "product workbench" type.
    field DBENCHDES
    Grouping (field PICKTRS)

    Number of the associated transaction of "Grouping" type.
    field PICKDES

    Non modifiable field displaying the description of the transaction.
    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.
    field MFGDES

    Non modifiable field displaying the description of the transaction.
    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.
    field SCODES

    Non modifiable field displaying the description of the transaction.

    Formula

    Selection formula (field DEFFOR)

    Enter, select, or build a format calculation expression using the formula editor.
    This formula, created using sections of the WIP, product and product/site tables, is applied within the framework of the search in addition to the entered selections.

    SEEINFO A warning message is displayed if a reference is made to tables not used in the context or to unknown variables.

    Tab Selections

    You use this tab to provide the transactions to be included in the projections. You can select transactions by type, status and by urgency.

    Grid

    Code (field CODWIP)
    Type (field LIBWIP)
    Suggested (field SUG)

    Click this check box to include suggested transactions of this type (for example, suggested orders (types SOS, WOS)) in the projections.
    Planned (field PLN)

    Click this check box to include planned transactions of this type (for example, planned orders (types SOP, WOP)) in the projections.
    Firm (field LAN)

    Click this check box to include firm transactions of this type (for example, firm orders (types SOF, WOF)) in the projections.
    Firm critical (field CRIT)

    Taking into account of the critical WIPs.

    Criticality

    Resources to replan (field RES)

    Taking into account of the orders to be replanned.
    Late requirements (field RET)

    Taking into account of late requests.
    Production requirements (field FMI)

    Taking into account of direct orders.
    Shortage requirements (field RUP)

    Taking into account of shortage requests.

    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

    You use this tab to define which fields to display and the order in which they are to be displayed.

    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 List of fields

    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.

    Action panel

    Validation

    Click the Validation action to save this entry transaction definition. This triggers the corresponding screens to be generated. A warning message is displayed suggesting that you view your results to check the display is as you expected. Should you need to make further adjustments click Cancel, adjust your definition and revalidate until the results you require are displayed.

    Click the Copy action to copy this entry transaction to a different 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.