MFGBENCH: Inserting additional filters

This entry point is used to insert additional logic within the preparation of the filter on the selection of works orders to be displayed in the global planning. It is used notably to add additional selections.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log file.

Available screen and file classes

The BENCHTRS ([F :BTS]) table and loaded with the current transaction.

 Use

This entry point has been designed to make it possible to add selections within global planning.

The context (transaction orientated to Purchasing or Production) depends on the setup of the transaction used. This transaction is accessible via the class [F :BTS].

Version 1.2.x :           The tables available for selection are : product on-hand orders [F :ORD] and product/site [F :ITF]

Version 1.3.x :           The tables available for selection are : product on-hand orders [F :ORD], product/site [F :ITF] and product [F :ITM]

To dynamically add selections, it is necessary to enter the variable FORMULE1 (255).

In version 1.2.x, this variable is completely available.

In version 1.3.x , this variable can contain a formula (maximum size = 70), so only about 185 characters can be used for the additional selections.  The entry point is called before the inclusion of any selection formula. If the variable FORMULE1 contains the additional selections inserted within the entry point, the selection formula is added at the end of the FORMULE1 variable preceded by an AND (ET) logic.

 Open tables

In the table below, the significant content flag indicates that the content is in phase with the context (…).

CUSSELFLT: Inserting additional filters

This entry point is used to insert additional logic during the creation of selection filters in the processing of global planning (FUNGBENCH function).

The CUSFLT variable (255 characters) is used to set filters on the fields in the additional files.

The filter can be applied to the product on-hand orders file (ORDERS  class [F :ORD] ), the products (ITMMASTER class [F :ITM]) as well as the product--sites (ITMFACILIT class [F :ITF]).

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log file

Available screen and file classes

The MFGBENCH mask is open and the different selections are loaded.

Open tables

In the table below, the significant content flag indicates that the content is in phase with the context (…).

CUSSRT: Additional classification

This entry point is used to insert additional logic on the sort of the entries in the grid in the global planning process (FUNGBENCH process).

The WTRI variable (integer type) is used to de-activate the standard sort if a specific sort has been included. To do this, the WTRI value is set to 1.

This entry point being common to the Global planning, workbench and grouping function, the specific/custom processing is unique and the context can be determined via a test on the transaction type:

[F :BTS] BTSTYP = 51 for global planning

[F :BTS] BTSTYP = 52 for the workbench

[F :BTS] BTSTYP = 53 for grouping

Specific/custom processing example:

$ACTION

ACTION example

 When "CUSSRT"      : Gosub CUSSRT

Endcase

Return

 $CUSSRT

Case [F:BTS]BTSTYP

When 51: Sorta [M:MGB]NBLIG [M:MGB]NBLIG Order By [M:MGB]BPRNUM(index)

When 52: Sorta [M:MGD]NBLIG [M:MGD]NBLIG Order By [M:MGD]BPRNUM(index)

    When 53: Sorta [M:MGP]NBLIG [M:MGP]NBLIG Order By [M:MGP]BPRNUM(index)

Endcase   

WTRI = 1

Return

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log file

Available screen and file classes

The MFGBENCH mask is open and the different selections are loaded.

Open tables

In the table below, the significant content flag indicates that the content is in phase with the context (…).

ADDLIN: Specific/custom field assignment

This entry point is used to enter the specific/custom fields in the global planning.

It is called in the FUNGBENCH process.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log file.

Different call cases - Available variables and masks

The entry point is called in order to complete the loading of the lines in the grid.

It is used to insert additional logic in order to load the specific/custom fields in the grid.

The MFGBENCH screen class is open at the moment of the entry point call.

Open tables

In the table below, the significant content flag indicates that the content is in phase with the context.

CHECKORD: Choice in the display of selected orders

This entry point is used to choose the orders to be displayed in the global planning from amongst those that have already been the subject of a previous selection.

It is called in the FUNGBENCH process.

Context and operating mode

Transaction

Log file

Different call cases

Available variables and masks

Open tables

PRTGBENCH: Launch of a specific/custom print.

This entry point is used to insert additional logic in order to launch a specific/custom print in the place of the standard screen print.

It is called in the FUNGBENCH process.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log file.

Different call cases

This entry point is called after the selection of the "print" function in the "file" menu.

The MFGBENCH mask is open at the time of the call to the entry point.

Available variables and masks

The GPE variable is used. It is set to the value 0 by default. It will need to be set to 1 in the specific/custom process linked to the entry point if the standard print must not be launched.  On returning to the standard processing, the GPE value is tested. If it is not equal to 0, the launch of the standard print is short-circuited.

Open tables

In the table below, the significant content flag indicates that the content is in phase with the context.

NOHINT: Optimization mode

This entry point is used to add the "With Nohint" instruction when performance problems occur on the Link instruction between the [F:ITM] and [F:ITF] tables.

It is called in the FUNGBENCH process.

Context and operating method

Transaction

There is no transaction in progress.

Log file

There is no open log file.

Different call cases

This entry point is called after the selection of the "print" function in the "file" menu.

The MFGBENCH mask is open at the time of the call to the entry point.

Available variables and masks

The GPE variable is used. It is set to the value 0 by default. It will need to be set to 1 in the specific/custom process linked to the entry point if the user wants to add this instruction in the used query.

Open tables

In the table below, the significant content flag indicates that the content is in phase with the context.

STYLE : Styles of the grid's lines

This entry point is used to take control on the display style of a grid line.

Context and operating method

Use

The [M:HLIK]LINNUM variable contains the index of the grid's line.

The [M:HLIK]STYLE variable contains the standard style to be applied to this line (no style if [M:HLIK]STYLE = blank).

By reassigning [M:HLIK]STYLE, the standard style can be replaced by another or can be disabled.