This entry point is used to insert additional logic in the work order management at the time of the operation list generation. It makes it possible to replace the standard algorithm, in order to load the data from a specific source.
There is one transaction in progress.
To cancel the transaction if there is a problem, the GOK variable must be set to 0.
There is no open log file
The [M :MFG0] and [M:MFG1] screen classes are loaded at the time of the call to the entry point.
This entry point has been designed to enable a complete custom/specific loading of the operations grid (MFG3).
The operations are inserted in the [M:MFG3] mask.
At the time of the call, the following parameters are available:
Value Date CDAT reference date
Value Integer CALT route alternative
Integer LRET Return code
If this entry point takes control of the list generation, the return code LRET must IMPERATIVELY 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)
In the table below, the significant content flag indicates that the content is in phase with the context (…).
Table | Significant content | Table Title |
MFGHEAD | No | WO header |
MFGITM | No | Released products |
MFGOPE | No | Operations |
MFGMAT | No | Materials |
MFGPRN | No | Documents |
ORDERS | No | WIPs |
SCHEDULING | No | Scheduling |
OPERATIONS | No | Loading |
ROUTING | No | Routing header |
ROUOPE | No | Routing operations |
ROUSCD | No | Route - Scheduling |
BOM | No | BOMs |
BOMD | No | BOM lines |
FACILITY | No | Site |
This entry point is used to insert additional logic into the management of works orders at the moment where, for each operation, the materials associated with a de-stocking location linked to a work center are updated.
There is no transaction in progress.
There is no open log file
The [M :MFG0], [M:MFG1] and [M :MFG2] screen classes are loaded at the time of the call to the entry point.
The [M :MFG3] screen is in the process of being loaded.
This entry point was designed to allow a specific/custom loading of the storage location (LOC field) in the component grid (MFG2), as well as the initialization of additional fields.
At the time of the call, the following parameters are available:
Value integer LOPENUM operation
Value Integer LLIG current index in the operations grid (in process of being loaded).
Value Char LWST Work centre
Value Char LFCY production site
In the table below, the significant content flag indicates that the content is in phase with the context (…).
Table | Significant content | Table Title |
MFGHEAD | No | WO header |
MFGITM | No | Released products |
MFGOPE | No | Operations |
MFGMAT | No | Materials |
MFGPRN | No | Documents |
ORDERS | No | WIPs |
SCHEDULING | No | Scheduling |
OPERATIONS | No | Loading |
ROUTING | No | Routing header |
ROUOPE | No | Routing operations |
ROUSCD | No | Route - Scheduling |
BOM | No | BOMs |
BOMD | No | BOM lines |
FACILITY | No | Site |
This entry point is used to insert additional logic:
- in work order management when generating the list of operations,
- in case of occasional sub-contracting planned on the operation, when deciding to sub-contract the operation,
°just before integrating the loss percentage into the calculation of quantities and operating time.
There is one transaction in progress.
To cancel the transaction if there is a problem, the GOK variable must be set to 0.
There is no open log file
The [F :ROO] table is loaded at the moment of the entry point call.
The [M :MFO1] and [M :MFG3] screens are being loaded.
The GPE variable is used. It is set to the value 0 by default. It will have to be positioned to 1 in the specific process linked to the entry point if the loss percentage is to be ignored in the quantity calculation. On returning to the standard processing, the GPE value is tested. If it is different from 0, the line where the quantity is weighted with the loss percentage is short-circuited.
In the table below, the significant content flag indicates that the content is in phase with the context (…).
Table | Significant content | Table Title |
MFGHEAD | No | WO header |
MFGITM | No | Released products |
MFGOPE | No | Operations |
MFGMAT | No | Materials |
MFGPRN | No | Documents |
ORDERS | No | WIPs |
SCHEDULING | No | Scheduling |
OPERATIONS | No | Loading |
ROUTING | No | Routing header |
ROUOPE | No | Routing operations |
ROUSCD | No | Route - Scheduling |
BOM | No | BOMs |
BOMD | No | BOM lines |
FACILITY | No | Site |
This entry point is used to insert additional logic into the management of work orders when the operations list is generated, immediately before moving to the next operation, at the end of the loading of the current operation in the [M:MFG3] table.
There is one transaction in progress.
To cancel the transaction if there is a problem, the GOK variable must be set to 0.
There is no open log file
The [F :ROO] table is loaded at the moment of the entry point call.
The [M :MFO1] and [M :MFG3] screens are being loaded.
The GPE variable is used. It is set to the value 0 by default. It will have to be positioned to 1 in the specific process linked to the entry point if the loss percentage is to be ignored in the quantity calculation. On returning to the standard processing, the GPE value is tested. If it is different from 0, the line where the quantity is weighted with the loss percentage is short-circuited.
In the table below, the significant content flag indicates that the content is in phase with the context (…).
Table | Significant content | Table Title |
MFGHEAD | No | WO header |
MFGITM | No | Released products |
MFGOPE | No | Operations |
MFGMAT | No | Materials |
MFGPRN | No | Documents |
ORDERS | No | WIPs |
SCHEDULING | No | Scheduling |
OPERATIONS | No | Loading |
ROUTING | No | Routing header |
ROUOPE | No | Routing operations |
ROUSCD | No | Route - Scheduling |
BOM | No | BOMs |
BOMD | No | BOM lines |
FACILITY | No | Site |