CUSSELFLT: Inserting additional filters

Use this entry point to take over during the creation of selection filters in the time tracking plan processing (FUNBENCHO function).

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

The filter can be applied to the WO operation file (MFGOPE class [F :MFO]) or the routing detail file (ROUOPE class [F :ROO]) according to whether the operations are to be selected for the WO or the routing.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log file.

Available screens and file classes

The MTKBENCHO 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.

AFFTRA: Possibility not to display the log file

Use this entry point to delete the display of the generated log file on time tracking plan validation.

The GPOINT variable must be reset to prevent the display.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is an open log file.

Available screens and file classes

The MTKBENCHO 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.

BENMTKMAJ: Update of the specific fields in the MFGHEADTRK file

Use this entry point to take over in time tracking creation in order to update the specific tables linked to the tracking header.

This entry point is called just before the "Write [F:MTK]" instruction.

Context and operating mode

Transaction

There is one transaction in progress.

If a problem arises, set the GOK global variable to 0.

Log file

There is an open log file.

Available screens and file classes

The MTKBENCHO mask is open and loaded.

The MTOK invisible mask is open and loaded with the information of the last operation processed.

Open tables

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

CUSCTRL: Additional controls before the launch of the database update.

Use this entry point to take over just after the use of the "Validation" button in order to carry out additional controls and potentially prevent the creation.

On leaving this entry point, the GPOINT variable is tested and the database update is only carried out if this variable is not empty. If these additional controls are not satisfying, it is necessary to empty this variable (GPOINT = "").

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log file.

Available screens and file classes

The MTKBENCHO mask is open and loaded.

Open tables

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

CUSSELENR: Controls on the operation record being analyzed

Use this entry point to take over in the read loop for the operation records to be taken into account in the time tracking plan processing (FUNBENCHO function), thus allowing to exclude an operation or to add another.

Deactivating the GPE variable (value=0) is used to avoid the loading of the [MFO] current line in the grid.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log file.

Available screens and file classes

The MTKBENCHO mask is open and the different selections are loaded. The operations grid is being loaded and a recording of the [MFO] file is being analyzed check whther all the criteria are met in order to load it in the grid.

Deactivating the GPE variable (value=0) is used to avoid the loading of the [MFO] current line in the grid.

Open tables

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

CUSTRTSUP: Possibility to launch an additional processing at the end of executio

Use this entry point to take over upon exiting the time tracking plan in order to carry out a specific processing, such as launching a print.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is an open log file.

Available variables and masks

Open tables

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

LOAMSKMBO: Specific loading of the operation tracking plan lines.

Use this entry point to take over before the display of the time tracking plan grid (FUNBENCHO function) in order to load it in a specific way.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log file.

Available screens and file classes

The FUNBENCHO 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.

 CTLFICTEC : Checking the answers to the technical sheets.

Use this entry point to take over just before sending a warning or error message when responses to technical sheets have not been provided.

For instance, it allows to check if another tracking has already been carried out on this WO operation, in order to stop sending the message.

When resuming the execution of the processing, the value of the GPE variable is tested.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log file.

Available screens and file classes

The MTKBENCHO mask is open and loaded.

The GCTLFICTEC global variable contains the value of the CTLFICTEC general setup (Check of the technical sheets). It is necessary to test the value of this variable in order to know the call context.

The GPE variable is loaded with the value 0 before calling the entry point.

To prevent the message from displaying, set the variable to 1.

Open tables

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

UPDSCD: Scheduling update

Use this entry point to authorize (or not) the scheduling recalculation following an operation tracking creation from the time tracking plan or ADCs.

Context and operating mode

Transaction

There is one transaction in progress.

Log file

There is an open log file.

 Usage

Set GPE to 1 to prevent a re-calculation of the scheduling. 

Open tables

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

BEFVALID: Before validation

Use this entry point to authorize or not the validation after specific controls.

Context and operating mode

Transaction

There is one transaction in progress.

Log file

There is an open log file.

 Usage

Activating the GPE variable (value=1) is used to stop the validation.

Available screens and file classes

The MTKBENCHO mask is open and loaded.

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

MBOTRKCRE: Tracking creation order

Use this entry point to take over after the controls authorizing the creation of trackings have been performed.

The standard will sort the grid lines according to IPTDAT, TIMTYP, MFGNUM, OPENUM and CLEFLG. It is then possible to perform a personalized sort. The value 1 must then be added to the WCRETRK variable.

It it also possible for the user to indicate that they want to use the EP according to MBOTRKLIN by adding the value 2 to the WCRETRK variable.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is an open log file.

Available screens and file classes

The MTKBENCHO mask is open and loaded.

Open tables

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

MBOTRKLIN: Force the creation of a new tracking number

This entry point is triggered only if the value 2 has been added to the WCRETRK variable (WCRETRK=2 or 3) in the MBOTRKCRE entry point. It it used to force the creation of a new tracking and thus avoid the accumulation of different plan lines into a signle tracking by assigning the value 1 to the WNEW variable.

The standard will always create a new tracking when loading the allocation date.

For example, to force the creation of a new tracking when loading the WO number:

If WWMFGNUM<>[M:MBO]MFGNUM(nolign-1)

WNEW=1

Endif

Context and operating mode

Transaction

There is one transaction in progress.

Log file

There is an open log file.

Available screens and file classes

The MTKBENCHO mask is open and loaded.

Available variables

WNEW: 0 by default Change to 1 to create a new tracking

WWMFGNUM: WO number of the tracking line that has just been created

nolign: line number being processed

Open tables

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