Use this function to customize the Planning workbench (FUNDBENCH/FUNDBENCHA) function to the needs of your organization and your processes. 

Your system is provided with a standard or master Planning workbench 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 Planning workbench 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 Planning workbench 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 Planning workbench 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 projections.
  • 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 Planning workbench function is selected from the menu.

Planning workbench

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 Parameters

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

  • The target user role
  • The projected stock movements and areas of functionality to be searched

 You must 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

    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.

    Parameters entered

    PAC modifiable (field UOMSAI)

    Use this field to permit (check box=selected) or prevent (check box=clear) modification of the release unit where the displayed unit is different from the stock unit.

    Formula

    Selection formula (field DEFFOR)

    The formula code that will be applied by default.

    Tab Selections

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

    Grid

    Code (field CODWIP)

    This code is associated with the type of operation.

    Type (field LIBWIP)

    This field specifies the type of operation to be processed.

    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.

    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

    Field (field INTIT)

    This column lists the fields that are available for display.
    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.

    Block number 4

    Forecast offset (field HORDEM)

    Select this check box if any sales forecast adjustments must be within the demand horizon. This only concerns products for which a request horizon has been defined at the site level.

    The adjustment for the planning calculations is based on the following principle:

    • Within the demand horizon, forecasts are ignored.
    • Beyond the demand horizon, the maximum anticipated quantity is considered. This equates to the difference between actual orders (from planned and firm sales orders (SOP / SOF)) and the forecast quantities (from sales order suggestions (SOS)).
    Include/Exclude

    Click Include/Exclude from the Actions icon to select (include) or clear (exclude) this field.

     A newly included field is positioned last. Check the Order
    Classification

    Click Classification from the Actions icon to sort the fields into ascending order. 
    Renumber

    Click Renumber from the Actions icon to sort the fields into ascending order and renumber them in increments of 5.

    Action panel

    Validation

    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.

    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.