MFMCRE: Add a component

This entry point is used to insert additional logic in the management of works orders on loading on the screen each component/sub-product. This entry point is used, for example, to insert a component or sub-product not present in the reference BOM. It is in addition used to modify the last line inserted in the standard.

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 [M :MFG0] and [M:MFG1] screen classes are loaded at the time of the call to the entry point.

 Use

This entry point has been designed to make it possible to dynamically add a component or sub-component to the list coming from the reference BOM. The call is carried out after the loading to the screen of each component or sub-product from the BOM.

The type of link in the insertion process (component or sub-component) is known by the [F :BOD]CPNTYP field.

The components are inserted in the [M:MFG2] mask. At the time of the call, the LIG variable points to the next line in the grid. After having loaded the grid line, it is absolutely necessary to increment the LIG, [M:MFG2]NBLIG and [M :MFG1]DMATNBR variables.

The sub-products are inserted in the mask [M:MFG1]. At the time of the call, the LIG variable points to the next line in the grid. After having loaded the grid line, it is necessary to increment the LIG and [M:MFG1]NBLIG variables.

The GMFMORI global variable makes it possible to know the original function (GESMFG)

Open tables

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

BOMDET: Generation of the component list

This entry point is used to insert additional logic in the works order management at the time of the component list generation. It makes it possible to replace the standard algorithm, in order to load the data from a specific source.

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 [M :MFG0] and [M:MFG1] screen classes are loaded at the time of the call to the entry point.

 Use

This entry point has been designed to enable a complete custom/specific loading of the component grid (MFG2).

The components are inserted in the [M:MFG2] mask.

At the time of the call, the following parameters are available:

            Integer  L          Released product line number

            Integer  LLIG       Grid size [MFG2] (= [M:MFG2]NBLIG)

            Char     LFCY       Production site

            Char     LITM       Released product

            Integer  LALT       BOM alternative

            Date     LDAT       WO start date

            Decimal  LQTY       Released quantity

            Char     LLOT       Released Lot

            Integer  LOPE       Operation number linked to the attached material (propagated via the phantom)

            Integer  LOFS       Usage lead-time                    (propagation via the phantom)

            Integer  LRET       Return code

 If this entry point takes control of the list generation, the return code LRET must IMPERITIVELY have the value 9, in order to short-circuit the standard processing.

The display of the grid is taken in hand by the standard.

The GMFMORI global variable makes it possible to know the original function (GESMFG)

Open tables

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

CROSSTEST: Possibility to pass through the product category other than phantom

This entry point is used to insert additional logic in the management of works orders at the time of generation or modification of the component list in order to pass to products in a category other than "phantom".

Context and operating mode

The local variable WORITRT (integer) is used to identify the call context.

           WORITRT = 1 : The context here is the initial generation of the component list.

           WORITRT = 2 : The status changes to Modification once a released quantity is changed.

According to the WORITRT value, the following actions are possible:

WORITRT = 1 : Component list generation:

The setting the "GPE" variable to a value of 1 is used to force this transfer in a systematic way.

The setting of the "GPE" variable to a value of 2 and the local variable "LGHOST" to a value of 1 allows an identical functioning to the phantom process, that is to say a transfer if the available quantity is less than the requirements with a confirmation message and summary window.

WORITRT = 2 : Modification of the list following the modification of the released quantity:

The setting of the "GPE" variable to a value other than 0 and the local variable "WVISUGHOST" to a value of 1 allows an identical functioning to the phantom process, that is to say with a message informing the user of the manual intervention requirement and summary window.

Example of the specific process for a functioning identical to the phantom functioning:

$ACTION

ACTION example

 When "CROSSTEST" :    Gosub ZCROSS

Endcase

Return

##################################################################################### 

$ZCROSS

If [F:ITM]TCLCOD= "xxx"                             # Example of condition: that the product category should be xxx 

  GPE = 2

  Case WORITRT:                                        # The call context is tested

             When 1: LGHOST          =  1           # The context is creation of a component line

             When 2: WVISUGHOST = 1             # The context is the modification of the quantity of a component line

  Endcase

Endif

Return

Transaction

There is no transaction in progress.

Log file

There is no open log file

Available screen and file classes

The [M :MFG0] and [M:MFG1] screen classes are loaded at the time of the call to the entry point.

Open tables

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

DELMESS: deletion of the message display during product checking

This entry point is used to insert additional logic in the work order management at the time of the component list generation in order to short-circuit the message "the product is not referenced on the production site".

Context and operating method

Transaction

There is no transaction in progress.

Log file

There is no open log file

Available screen and file classes

The [M :MFG0] and [M:MFG1] screen classes are loaded at the time of the call to the entry point, as well as the [ITM] and [ITF] buffers.

Use

This entry point is designed to be used to insert additional logic within the loading of the component grid sub-program. It allows to short-circuit the message "the product is not referenced on the production site" of the standard processing.

The GPE variable is used. It is set to the value 0 by default. It will have to be set to 1 to short-circuit the error message of the standard processing. On returning to the standard processing, the GPE variable is tested. If it is different from 0, the error message is short-circuited.

Open tables

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

SHOWBOX: canceling the display of the dialog box

This entry point is used to insert additional logic in the work order management at the time of the component list generation in order to short-circuit the display of the "A phantom component is present" dialog box. \Display of a list of components involved in the verification?".

Context and operating method

Transaction

There is no transaction in progress.

Log file

There is no open log file

Available screen and file classes

The [M :MFG0] and [M:MFG1] screen classes are loaded at the time of the call to the entry point, as well as the [ITM] and [ITF] buffers.

Use

The GPE variable is used. It is set to 1 by default. It will have to be set to 0 to short-circuit the display of the dialog box.

Open tables

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