Script MFGAUTLIB: Library of automatic scripts linked to work orders
MFIMAJ: Updating specific/custom fields in the released products file MFGITM
Use this entry point to insert additional logic in the creation of a work order immediately before creating the released product lines. You can then initialize specific fields, for example.
Context and operating mode
Transaction
There is one transaction in progress.
The GOK variable must be set to 0 to cancel the transaction if there is a problem.
Log file
There is an open log file.
Available variables and masks
The [F:MFI] buffer is loaded when calling the entry point.
The [M:MFGK] screen class linked to the automatic creation of the work order is loaded.
Depending on the context, the [M:MBW1], [M:MBW3] or [M:MBW4] screen classes linked to the consideration of work in progress are loaded.
Open tables
In the following table, the Significant content value indicates that the content matches the context.
| Table | Significant content | Table title |
|
MFGHEAD |
Yes |
Work order - header |
|
MFGITM |
Yes |
Work orders - products |
|
MFGOPE |
No |
Work order - operations |
|
MFGMAT |
No |
Work order - materials |
|
MFGPRN |
No |
Work orders - documents |
|
ORDERS |
No |
WIP |
|
SCHEDULING |
No |
Work order scheduling |
|
OPERATIONS |
No |
Load in progress |
|
ROUTING |
Yes |
Routings - header |
|
ROUOPE |
No |
Routing - operations |
|
ROUSCD |
Yes |
Routing - scheduling operation |
|
BOM |
No |
Header BOMs |
|
BOMD |
No |
Detail BOMs |
|
FACILITY |
No |
Sites |
AUTLIBMAJ: Updating specific/custom fields in the work order header file MFGHEAD
Use this entry point to insert additional logic in the following:
- Automatic work order creation immediately before creating the work order header. You can then initialize specific fields, for example.
- Automatic work order modification immediately before modifying the work order header. You can then modify specific fields, for example.
Context and operating mode
Transaction
There is one transaction in progress.
The GOK variable must be set to 0 to cancel the transaction if there is a problem.
Log file
There is an open log file in work order header creation.
There is no open log file in work order header modification.
Available variables and masks
This entry point is common to the creation and modification of the work order header. The specific script is unique. The context can be determined by testing the CODMAJ variable:
- Work order header creation: [M:MFGK]CODMAJ="C"
- Work order header modification: [M:MFGK]CODMAJ="M"
The [F:MFG] buffer is loaded when calling the entry point.
The [M:MFGK] screen class linked to the automatic creation or modification of the work order is loaded.
Depending on the context, the [M:MBW1], [M:MBW3] or [M:MBW4] screen classes linked to the consideration of work in progress are loaded.
Open tables
In the following tables, the Significant content value indicates that the content matches the context.
In work order header creation:
| Table | Significant content | Table title |
|
MFGHEAD |
Yes |
Work order - header |
|
MFGITM |
Yes |
Work orders - products |
|
MFGOPE |
No |
Work order - operations |
|
MFGMAT |
No |
Work order - materials |
|
MFGPRN |
No |
Work orders - documents |
|
ORDERS |
No |
WIP |
|
SCHEDULING |
No |
Work order scheduling |
|
OPERATIONS |
No |
Load in progress |
|
ROUTING |
Yes |
Routings - header |
|
ROUOPE |
No |
Routing - operations |
|
ROUSCD |
Yes |
Routing - scheduling operation |
|
BOM |
No |
Header BOMs |
|
BOMD |
No |
Detail BOMs |
|
FACILITY |
No |
Sites |
In work order header modification:
| Table | Significant content | Table title |
|
MFGHEAD |
Yes |
Work order - header |
|
MFGITM |
Yes |
Work orders - products |
|
MFGOPE |
Yes |
Work order - operations |
|
MFGMAT |
Yes |
Work order - materials |
|
ITMMVT |
Yes |
Product-site totals |
|
WORKSTATIO |
Yes |
Work centers |
MFMCRE: Adding a component
Use this entry point to insert additional logic in the generation of the list of components or by-products associated with a work order.
This entry point is called at the end of the insertion of each component or by-product belonging to the reference BOM.
Additionally, you can use this entry point to modify the last line inserted in the standard.
Context and operating mode
Transaction
There is one transaction in progress.
The GOK variable must be set to 0 to cancel the transaction if there is a problem.
Log file
There is an open log file.
Available variables and masks
The [F:MFG] buffer is loaded when calling the entry point.
The [F:MFI] buffer is loaded when calling the entry point.
The [F:MFM] buffer corresponding to the previously created component is loaded when calling the entry point.
The [M:MFGX] screen class is loaded with the previous components when calling the entry point.
The [M:ORDK] screen class is loaded with the previous by-product when calling the entry point.
The [M:MFGK] screen class linked to the automatic creation of the work order is loaded.
Use
This entry point has been designed to enable a component or sub-component to be added dynamically to the list of components for the reference BOM. The call is carried out after the addition of each component to the BOM.
The type of link being inserted, component or by-product, is recognized by the [F:BOD]CPNTYP field.
The components are generated directly into the MFGMAT table. At the time of the call, the [MFM] class contains the previous component.
- The addition is carried out by loading the [MFM] class, entry of the [MFM] record, generation of the WIP by loading the [ORDK] mask and calling the TRTWIP script.
- The component sequence number must be incremented [F:MFG]MATLINNBR.
- The by-products are generated directly into the MFGITM table. Upon calling, the [MFI] class contains the previously loaded by-product.
The GMFMORI global variable is used to identify the source function (MFGAUTLIB).
Open tables
In the following table, the Significant content value indicates that the content matches the context.
| Table | Significant content | Table title |
|
MFGTRS |
Yes |
Production entry transaction |
|
MFGHEAD |
Yes |
Work order - header |
|
MFGITM |
Yes |
Work orders - products |
|
MFGMAT |
No |
Work order - materials |
|
ITMMASTER |
Yes |
Products |
|
MFGOPE |
No |
Work order - operations |
|
SCHEDULING |
No |
Work order scheduling |
|
MFGPRN |
No |
Work orders - documents |
|
ITMMVT |
No |
Product-site totals |
|
WORKSTATIO |
No |
Work centers |
|
BOM |
No |
Header BOMS |
|
BOMD |
No |
Detail BOMs |
|
ROUTING |
No |
Routings - header |
|
ROUOPE |
No |
Routing - operations |
|
ROUSCD |
No |
Routing - scheduling operation |
|
FACILITY |
Yes |
Sites |
|
ORDERS |
No |
WIP |
|
OPERATIONS |
No |
Load in progress |
MFMMAJ: Updating specific/custom fields in the work order materials file MFGMAT
Use this entry point to insert additional logic in the creation of a work order immediately before creating the component lines. You can then initialize specific fields, for example.
Context and operating mode
Transaction
There is one transaction in progress.
The GOK variable must be set to 0 to cancel the transaction if there is a problem.
Log file
There is an open log file.
Available variables and masks
The [F:MFM] buffer is loaded when calling the entry point.
The [M:MFGK] screen class linked to the automatic creation of the work order is loaded.
Depending on the context, the [M:MBW1], [M:MBW3] or [M:MBW4] screen classes linked to the consideration of work in progress are loaded.
Open tables
In the following table, the Significant content value indicates that the content matches the context.
| Table | Significant content | Table title |
|
MFGHEAD |
Yes |
Work order - header |
|
MFGITM |
No |
Work orders - products |
|
MFGOPE |
No |
Work order - operations |
|
MFGMAT |
Yes |
Work order - materials |
|
MFGPRN |
No |
Work orders - documents |
|
ORDERS |
Yes |
WIP |
|
SCHEDULING |
No |
Work order scheduling |
|
OPERATIONS |
No |
Load in progress |
|
ROUTING |
Yes |
Routings - header |
|
ROUOPE |
No |
Routing - operations |
|
ROUSCD |
No |
Routing - scheduling operation |
|
BOM |
Yes |
Header BOMs |
|
BOMD |
No |
Detail BOMs |
|
FACILITY |
No |
Sites |
MFOMAJ: Updating specific/custom fields in the work order operations file MFGOPE
Use this entry point to insert additional logic in the creation of a work order immediately before creating the operation lines. You can then initialize specific fields, for example.
Context and operating mode
Transaction
There is one transaction in progress.
The GOK variable must be set to 0 to cancel the transaction if there is a problem.
Log file
There is an open log file.
Available variables and masks
The [F:MFO] buffer is loaded when calling the entry point.
The [M:MFGK] screen class linked to the automatic creation of the work order is loaded.
Depending on the context, the [M:MBW1], [M:MBW3] or [M:MBW4] screen classes linked to the consideration of work in progress are loaded.
Open tables
In the following table, the Significant content value indicates that the content matches the context.
| Table | Significant content | Table title |
|
MFGHEAD |
Yes |
Work order - header |
|
MFGITM |
No |
Work orders - products |
|
MFGOPE |
Yes |
Work order - operations |
|
MFGMAT |
No |
Work order - materials |
|
MFGPRN |
No |
Work orders - documents |
|
ORDERS |
No |
WIP |
|
SCHEDULING |
No |
Work order scheduling |
|
OPERATIONS |
Yes |
Load in progress |
|
ROUTING |
Yes |
Routings - header |
|
ROUOPE |
Yes |
Routing - operations |
|
ROUSCD |
Yes |
Routing - scheduling operation |
|
BOM |
No |
Header BOMs |
|
BOMD |
No |
Detail BOMs |
|
FACILITY |
No |
Sites |
BOMDET: Generating the component list
Use this entry point to insert additional logic in the management of a work order when generating the list of components.
You can use it to replace the standard algorithm in order to load the data from a specific source.
Context and operating mode
Transaction
There is one transaction in progress.
The GOK variable must be set to 0 to cancel the transaction if there is a problem.
Log file
There is no open log file.
Available variables and masks
The [F:MFG] buffer is loaded when calling the entry point.
The [F:MFI] buffer is loaded when calling the entry point.
The [M:MFGK] screen class linked to the automatic creation of the work order is loaded.
Use
This entry point has been designed to enable a complete specific or custom loading of the component grid (MFGX).
The components are inserted in the [M:MFGX] mask.
At the time of the call, the following parameters are available:
- 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
The writing of the [M:MFGX] grid contents to the [F:MFM] table is carried out by the standard.
The GMFMORI global variable is used to identify the source function (MFGAUTLIB).
Open tables
In the following table, the Significant content value indicates that the content matches the context.
| Table | Significant content | Table title |
|
MFGHEAD |
No |
Work order - header |
|
MFGITM |
No |
Work orders - products |
|
MFGOPE |
No |
Work order - operations |
|
MFGMAT |
No |
Work order - materials |
|
MFGPRN |
No |
Work orders - documents |
|
ORDERS |
No |
WIP |
|
SCHEDULING |
No |
Work order scheduling |
|
OPERATIONS |
No |
Load in progress |
|
ROUTING |
No |
Routings - header |
|
ROUOPE |
No |
Routing - operations |
|
ROUSCD |
No |
Routing - scheduling operation |
|
BOM |
No |
Header BOMs |
|
BOMD |
No |
Detail BOMs |
|
FACILITY |
No |
Sites |
ROUDET: Generating the operations list
Use this entry point to insert additional logic in the management of a work order when generating the list of operations.
You can use it to replace the standard algorithm in order to load the data from a specific source.
Context and operating mode
Transaction
There is one transaction in progress.
The GOK variable must be set to 0 to cancel the transaction if there is a problem.
Log file
There is no open log file.
Available variables and masks
The [F:MFG] buffer is loaded when calling the entry point.
The [F:MFI] buffer is loaded when calling the entry point.
The [M:MFGK] screen class linked to the automatic creation of the work order is loaded.
Use
This entry point has been designed to enable a complete specific or custom loading of the operations table ([F:MFO]).
Upon calling, the following parameters are available:
- Value Date CDAT Reference date
- Value Integer CALT Route alternative
- Integer LRET Return code
The GMFMORI global variable is used to identify the source function (MFGAUTLIB).
Open tables
In the following table, the Significant content value indicates that the content matches the context.
| Table | Significant content | Table title |
|
MFGHEAD |
No |
Work order - header |
|
MFGITM |
No |
Work orders - products |
|
MFGOPE |
No |
Work order - operations |
|
MFGMAT |
No |
Work order - materials |
|
MFGPRN |
No |
Work orders - documents |
|
ORDERS |
No |
WIP |
|
SCHEDULING |
No |
Work order scheduling |
|
OPERATIONS |
No |
Load in progress |
|
ROUTING |
No |
Routings - header |
|
ROUOPE |
No |
Routing - operations |
|
ROUSCD |
No |
Routing - scheduling operation |
|
BOM |
No |
Header BOMs |
|
BOMD |
No |
Detail BOMs |
|
FACILITY |
No |
Sites |
UPDMFIMAJ: Updating specific/custom fields during modification of products
Use this entry point to insert additional logic in the management of a work order immediately before rewriting the released product lines. You can then initialize specific fields, for example.
Context and operating mode
Transaction
There is one transaction in progress.
The GOK variable must be set to 0 to cancel the transaction if there is a problem.
Log file
There is an open log file.
Available variables and masks
The [F:MFI] buffer is loaded when calling the entry point.
The [M:MFGK] screen class linked to the automatic creation of the work order is loaded.
Open tables
In the following table, the Significant content value indicates that the content matches the context.
| Table | Significant content | Table title |
|
MFGHEAD |
Yes |
Work order - header |
|
MFGITM |
Yes |
Work orders - products |
|
MFGOPE |
No |
Work order - operations |
|
MFGMAT |
No |
Work order - materials |
|
MFGPRN |
No |
Work orders - documents |
|
ORDERS |
No |
WIP |
|
SCHEDULING |
No |
Work order scheduling |
|
OPERATIONS |
No |
Load in progress |
|
ROUTING |
No |
Routings - header |
|
ROUOPE |
No |
Routing - operations |
|
ROUSCD |
No |
Routing - scheduling operation |
|
BOM |
No |
Header BOMs |
|
BOMD |
No |
Detail BOMs |
|
FACILITY |
No |
Sites |
UPDMFMMAJ: Updating of specific/custom fields during modification of components
Use this entry point to insert additional logic in the modification of a work order immediately before rewriting the component lines. You can then initialize specific fields, for example.
Context and operating mode
Transaction
There is one transaction in progress.
The GOK variable must be set to 0 to cancel the transaction if there is a problem.
Log file
There is an open log file.
Available variables and masks
The [F:MFM] buffer is loaded when calling the entry point.
The [M:MFGK] screen class linked to the automatic creation of the work order is loaded.
Open tables
In the following table, the Significant content value indicates that the content matches the context.
| Table | Significant content | Table title |
|
MFGHEAD |
Yes |
Work order - header |
|
MFGITM |
No |
Work orders - products |
|
MFGOPE |
No |
Work order - operations |
|
MFGMAT |
Yes |
Work order - materials |
|
MFGPRN |
No |
Work orders - documents |
|
ORDERS |
Yes |
WIP |
|
SCHEDULING |
No |
Work order scheduling |
|
OPERATIONS |
No |
Load in progress |
|
ROUTING |
No |
Routings - header |
|
ROUOPE |
No |
Routing - operations |
|
ROUSCD |
No |
Routing - scheduling operation |
|
BOM |
No |
Header BOMs |
|
BOMD |
No |
Detail BOMs |
|
FACILITY |
No |
Sites |
UPDMFOMAJ: Updating specific/custom fields during modification of operations
Use this entry point to insert additional logic in the modification of a work order immediately before rewriting the operation lines. You can then initialize specific fields, for example.
Context and operating mode
Transaction
There is one transaction in progress.
The GOK variable must be set to 0 to cancel the transaction if there is a problem.
Log file
There is an open log file.
Available variables and masks
The [F:MFO] buffer is loaded when calling the entry point.
The [M:MFGK] screen class linked to the automatic creation of the work order is loaded.
Open tables
In the following table, the Significant content value indicates that the content matches the context.
| Table | Significant content | Table title |
|
MFGHEAD |
Yes |
Work order - header |
|
MFGITM |
No |
Work orders - products |
|
MFGOPE |
Yes |
Work order - operations |
|
MFGMAT |
No |
Work order - materials |
|
MFGPRN |
No |
Work orders - documents |
|
ORDERS |
No |
WIP |
|
SCHEDULING |
No |
Work order scheduling |
|
OPERATIONS |
Yes |
Load in progress |
|
ROUTING |
No |
Routings - header |
|
ROUOPE |
No |
Routing - operations |
|
ROUSCD |
No |
Routing - scheduling operation |
|
BOM |
No |
Header BOMs |
|
BOMD |
No |
Detail BOMs |
|
FACILITY |
No |
Sites |
CROSSTEST: Passing through a product category other than Phantom
Use this entry point to insert additional logic in the creation or modification of a work order when generating or modifying the list of components, in order to pass to products in a category other than Phantom.
Context and operating mode
The WORITRT local variable of Integer type identifies the call context.
- WORITRT = 1 - Context is the initial generation of the list of components.
- WORITRT = 2 - Context is modification.
According to the value of WORITRT the following actions are available:
WORITRT = 1 - Component list generation:
Set the GPE variable to 1 to force the transfer systematically.
Set the GPE variable to 2 and the LGHOST local variable to 1 to enable an identical functioning to the phantom script. That is, a transfer if the available quantity is less than the requirements with a confirmation message and summary window.
WORITRT = 2 - List modification:
Set the GPE variable to a value other than 0 and the WVISUGHOST local variable to 1 to enable an identical functioning to the phantom script. That is, with a message informing you of the requirement for manual intervention and summary window.
Example of the specific process for a functioning identical to the phantom functioning:
$ACTION
Case ACTION
When "CROSSTEST": Gosub ZCROSS
When Default:
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 # 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 one transaction in progress.
The GOK variable must be set to 0 to cancel the transaction if there is a problem.
Log file
There is no open log file.
Available variables and masks
The [F:MFG] buffer is loaded when calling the entry point.
The [F:MFI] buffer is loaded when calling the entry point.
The [M:MFGK] screen class linked to the automatic creation of the work order is loaded.
In creation (WORITRT = 1), the [F:BOD] buffer is loaded in phase with the context.
In modification (WORITRT = 2), the [F:MFM] buffer is loaded in phase with the context.
Open tables
In the following table, the Significant content value indicates that the content matches the context.
| Table | Significant content | Table title |
|
MFGHEAD |
Yes |
Work order - header |
|
MFGITM |
Yes |
Work orders - products |
|
MFGOPE |
No |
Work order - operations |
|
MFGMAT |
No |
Work order - materials |
|
MFGPRN |
No |
Work orders - documents |
|
ORDERS |
No |
WIP |
|
BOM |
No |
Header BOMs |
|
BOMD |
No |
Detail BOMs |
|
FACILITY |
Yes |
Sites |
|
ITMMASTER |
Yes |
Products |
|
ITMFACILIT |
Yes |
Products-sites |
SHOWBOX: Hiding the list of components of a phantom product
Use this entry point to insert additional logic when creating or releasing a work order to block the list of components of a phantom product from being displayed.
Context and operating mode
Transaction
There is one transaction in progress.
The GOK variable must be set to 0 to cancel the transaction if there is a problem.
Log file
There is no open log file.
Available variables and masks
The [F:MFG], [F:MFI], [F:MFO] and [F:MFM] buffers are loaded when calling the entry point.
The [M:MFGK] screen class linked to the automatic creation of the work order is loaded.
Open tables
In the following table, the Significant content value indicates that the content matches the context.
| Table | Significant content | Table title |
|
MFGHEAD |
Yes |
Work order - header |
|
MFGITM |
Yes |
Work orders - products |
|
MFGOPE |
Yes |
Work order - operations |
|
MFGMAT |
Yes |
Work order - materials |
|
MFGPRN |
No |
Work orders - documents |
|
ORDERS |
Yes |
WIP |
|
BOM |
No |
Header BOMs |
|
BOMD |
No |
Detail BOMs |
|
FACILITY |
Yes |
Sites |
|
ITMMASTER |
Yes |
Products |
|
ITMFACILIT |
Yes |
Products-sites |
ROHMAJ: Updating specific/custom fields in the routings header file ROUTING
Use this entry point to insert additional logic in the following:
- Automatic work order creation immediately before rewriting the routing header. You can then modify specific fields, for example.
- Automatic modification of suggested work orders immediately before rewriting the routing header. You can then modify specific fields, for example.
Context and operating mode
Transaction
There is one transaction in progress.
The GOK variable must be set to 0 to cancel the transaction if there is a problem.
Log file
There is an open log file in work order creation.
There is no open log file in work order suggestion modification.
Available variables and masks - Different call cases
This entry point is common to the creation and modification of a work order. The specific script is unique. The context can be determined by testing the CODMAJ variable:
- [M:MFGK]CODMAJ = "C" - Work order creation.
- [M:MFGK]CODMAJ = "P" - Creation of the work order linked to the consideration of the work in progress.
- [M:MFGK]CODMAJ = "M" - Suggested work order modification.
The [F:MFG] buffer is loaded when calling the entry point.
The [M:MFGK] screen class linked to the automatic creation of the work order is loaded.
Depending on the context, the [M:MBW1], [M:MBW3] or [M:MBW4] screen classes linked to the consideration of work in progress are loaded.
Open tables
In the following tables, the Significant content value indicates that the content matches the context.
In work order creation:
| Table | Significant content | Table title |
|
MFGHEAD |
Yes |
Work order - header |
|
MFGITM |
Yes |
Work orders - products |
|
MFGOPE |
Yes |
Work order - operations |
|
MFGMAT |
Yes |
Work order - materials |
|
ORDERS |
No |
WIP |
In work order modification:
| Table | Significant content | Table title |
|
MFGHEAD |
Yes |
Work order - header |
|
MFGOPE |
Yes |
Work order - operations |
|
MFGMAT |
Yes |
Work order - materials |
|
ORDERS |
No |
WIP |
|
OPERATIONS |
No |
Load in progress |
WITHSHR: Ignoring the production loss percentage
Use this entry point to insert additional logic in the following immediately before integrating the production loss percentage into the calculation of quantities and operating time:
- The creation of a firm or planned work order.
- The modification of a firm or planned work order.
- The planning and release of a suggested order.
Context and operating mode
Transaction
There is one transaction in progress.
The GOK variable must be set to 0 to cancel the transaction if there is a problem.
Log file
There is no open log file.
Available variables and masks
The [F:MFO] and [F:ROO] buffers are loaded when calling the entry point.
The GPE variable is used.
By default, GPE is set to 0. It must be set to 1 in the specific script linked to the entry point to ignore the loss percentage in the quantity calculation.
When returning to the standard script, the GPE value is tested. If it is different from 0, the line where the quantity is weighted with the loss percentage is bypassed.
Open tables
In the following table, the Significant content value indicates that the content matches the context.
| Table | Significant content | Table title |
|
MFGOPE |
No |
Work order - operations |
|
WORKSTATIO |
No |
Work centers |
|
CPTANALIN |
No |
Analytical accounting lines |
|
SCHEDULING |
No |
Work order scheduling |
DELREC: Deleting recordings from specific/custom tables
Use this entry point to insert additional logic in the deletion of work orders from the Enterprise planning workbench and the Planning workbench.
Context and operating mode
Transaction
There is one transaction in progress.
The GOK variable must be set to 0 to cancel the transaction if there is a problem.
Log file
There is no open log file.
Available variables and masks
The [M:MFGK] screen class linked to the automatic deletion of work orders is loaded when calling the entry point.
Open tables
In the following table, the Significant content value indicates that the content matches the context.
| Table | Significant content | Table title |
|
MFGHEAD |
Yes |
Work order - header |
|
MFGITM |
Yes |
Work orders - products |
|
MFGOPE |
Yes |
Work order - operations |
|
MFGMAT |
Yes |
Work order - materials |
|
WORKSTATIO |
Yes |
Work centers |
ALLCHOMAT: Creating a specific work order component allocation
Use this entry point to insert additional logic immediately before creating the work order component allocations in order to bypass the standard allocation to carry out an allocation based on specific criteria.
Context and operating mode
Transaction
There is one transaction in progress.
Log file
There is no open log file.
Available variables and masks
The [M:MFGK] mask is loaded when calling the entry point.
The [M:MFGMAT] ([F:MFM]) table is loaded when calling the entry point.
Use
This entry point has been designed to only take control during the creation of the work order component allocations.
It is used to bypass the standard allocation in order to carry out an allocation based on specific criteria. For example, a specific field linked to each component can indicate the allocation type to be applied to allocate the component, such as global, detailed, and so on.
The GPE variable is used. By default, it is set to 0. It must be set to 1 to bypass the standard processing allocation.
Open tables
In the following table, the Significant content value indicates that the content matches the context.
| Table | Significant content | Table title |
|
MFGHEAD |
Yes |
Work order - header |
|
MFGITM |
Yes |
Work orders - products |
UPDMFILOT: Updating LOT on the generated MFI lines
Use this entry point to insert additional logic at the LOT number calculation level in order to replace the LOT sequence number calculation and/or manage the error message differently.
Context and operating mode
Transaction
There is one transaction in progress.
The GOK variable must be set to 0 to cancel the transaction if there is a problem.
Log file
There is an open log file.
Available variables and masks
The [F:MFI] buffer is loaded when calling the entry point. If the script must be different for a by-product, the control of [F:MFI]ITMTYP must be planned in the specific script.
The [M:MFGK] screen class linked to the automatic creation of the work order is loaded.
The GPE variable must be set to 1 to avoid overwriting the [F:MFI]LOT calculated by the specific script.
Example of a script
Call NUMERO(WLOTCOU, [M:MFGK]MFGFCY, [M:MFGK]STRDAT, [F:MFI]ITMREF, [F:MFI]LOT, WIND) From SUBANM
If WIND
Case WIND
When 1: GMESSAGE = WLOTCOU-":"-mess(12,114,1): # Non-existent sequence number counter
When 2: GMESSAGE = WLOTCOU-":"-mess(13,114,1): # Sequence number counter exceeded
When 3: GMESSAGE = WLOTCOU-":"-mess(20,101,1): # Fiscal Year Not Open
When 4: GMESSAGE = WLOTCOU-":"-mess(111,123,1): # Incorrect length
When 99: GMESSAGE = WLOTCOU-":"-mess(135,133,1): # Locked counter
Endcase
If [M:MFGK]AUTOTRT <> 2
Call ERREUR(GMESSAGE) From GESECRAN
Endif
Endif
Open tables
In the following table, the Significant content value indicates that the content matches the context.
| Table | Significant content | Table title |
|
MFGHEAD |
Yes |
Work order - header |
|
MFGITM |
Yes |
Work orders - products |
|
MFGOPE |
No |
Work order - operations |
|
MFGMAT |
No |
Work order - materials |
|
MFGPRN |
No |
Work orders - documents |
|
ORDERS |
No |
WIP |
|
SCHEDULING |
No |
Work order scheduling |
|
OPERATIONS |
No |
Load in progress |
|
ROUTING |
No |
Routings - header |
|
ROUOPE |
No |
Routing - operations |
|
ROUSCD |
No |
Routing - scheduling operation |
|
BOM |
No |
Header BOMs |
|
BOMD |
No |
Detail BOMs |
|
FACILITY |
No |
Sites |
BOMDATCTL: Generating the component list using work order start date
Use this entry point to insert additional logic in the management of a work order when generating the list of components to replace the standard algorithm that selects components according to the work order start date compared with the component validity dates.
Context and operating mode
Conditions depend on the function used.
This entry point is triggered in MRP from the automatic generation of a work order from the Planning workbench or from the work order creation screen.
Use
By default, the GPE variable is set to 0. Changing its value replaces the value of the variable used (WBOMDATCTL).
The value 2 corresponds to the standard script, that is the selection of components according to the calculated start date.
Open tables
In the following table, the Significant content value indicates that the content matches the context.
| Table | Significant content | Table title |
|
MFGHEAD |
Yes |
Work order - header |
|
MFGITM |
Yes |
Work orders - products |
|
MFGOPE |
No |
Work order - operations |
|
MFGMAT |
No |
Work order - materials |
|
MFGPRN |
No |
Work orders - documents |
|
ORDERS |
No |
WIP |
|
SCHEDULING |
No |
Work order scheduling |
|
OPERATIONS |
No |
Load in progress |
|
ROUTING |
No |
Routings - header |
|
ROUOPE |
No |
Routing - operations |
|
ROUSCD |
No |
Routing - scheduling operation |
|
BOM |
No |
Header BOMs |
|
BOMD |
No |
Detail BOMs |
|
FACILITY |
No |
Sites |
ROUDATCTL: Generating the operation list using work order start date
Use this entry point to insert additional logic in the management of a work order when generating the list of routing operations to replace the standard algorithm that selects operations according to the work order start date compared with the component validity dates.
Context and operating mode
Conditions depend on the function used.
This entry point is triggered from the automatic generation of a work order from the Planning workbench or from the work order creation screen.
Use
By default, the GPE variable is set to 0. Changing its value replaces the value of the variable used (WROUDATCTL).
The value 2 corresponds to the standard script, that is the selection of operations according to the calculated start date.
Open tables
In the following table, the Significant content value indicates that the content matches the context.
| Table | Significant content | Table title |
|
MFGHEAD |
Yes |
Work order - header |
|
MFGITM |
Yes |
Work orders - products |
|
MFGOPE |
No |
Work order - operations |
|
MFGMAT |
No |
Work order - materials |
|
MFGPRN |
No |
Work orders - documents |
|
ORDERS |
No |
WIP |
|
SCHEDULING |
No |
Work order scheduling |
|
OPERATIONS |
No |
Load in progress |
|
ROUTING |
No |
Routings - header |
|
ROUOPE |
No |
Routing - operations |
|
ROUSCD |
No |
Routing - scheduling operation |
|
BOM |
No |
Header BOMs |
|
BOMD |
No |
Detail BOMs |
|
FACILITY |
No |
Sites |
RPLMAT: Blocking component reload
This entry point is called when the RELSTRDAT - Level on WO start date change parameter (GPA chapter, WOM group) is set to Yes.
Use this entry point to block the list of components from being reloaded from the BOM that is valid on the start date of the work order when the work order start date is different from [M:MFGK]STRDAT.
Context and operating mode
Conditions depend on the function used.
This entry point is triggered from the automatic generation of a work order from the Assignment workbench, Planning workbench, Enterprise planning, and so on, when the work order start date is changed.
Transaction
There is one transaction in progress.
Use
The GPE variable is set to 0 by default. Modifying the variable value prevents the leveling of work order components based on the production BOM of the released product.
Available variables and masks
The [M:MFGK] screen class linked to the automatic creation of the work order is loaded.
Open tables
In the following table the Significant content value indicates that the content matches the context.
| Table | Significant content | Table title |
|
MFGHEAD |
Yes |
Work order - header |
|
MFGITM |
Yes |
Work orders - products |
|
MFGOPE |
No |
Work order - operations |
|
MFGMAT |
No |
Work order - materials |
|
MFGPRN |
No |
Work orders - documents |
|
ORDERS |
No |
WIP |
|
SCHEDULING |
No |
Work order scheduling |
|
OPERATIONS |
No |
Load in progress |
|
ROUTING |
No |
Routings - header |
|
ROUOPE |
No |
Routing - operations |
|
ROUSCD |
No |
Routing - scheduling operation |
|
BOM |
No |
Header BOMs |
|
BOMD |
No |
Detail BOMs |
|
FACILITY |
No |
Sites |
MPECBESOINS: Modifying the quantities to be considered
This entry point consider the requirements for the workbenches, such as Enterprise planning workbench, Planning workbench and Grouping, and generates an action called MPECBESOIN. The goal of the MPECBESOINS action is to convert the requirement quantity into physical units.
Context and operating mode
Transaction
There is no transaction in process.
Log file
There is an open log file.
Different call cases
The call is made for each requirement line considered in the workbenches.
Available variables and masks
The following variables are loaded at the time of the call to the MPECBESOINS action:
- ABREV: Abbreviation for the screen mask used (MFGK).
- [M:MFGK]WIPTYP
- Order type 5 = WO (Work order)
The [M:MFGK] screen mask is usable.
The variable and class given above must not be modified.
The following variable must be modified to influence the requirement selection process:
- RMNQTY: Quantity for the requirement to be considered.
AFTRCREOF: Allowing order modification immediately before modifying the work order
Use this entry point to insert additional logic in the automatic work order creation immediately before creating the work order header. You can then initialize specific fields, for example.
Context and operating mode
This entry point is called immediately before the sub-routine VISUGHOST.
GETMFGLIN: Opening transactions
Context and operating method
Transaction
Open transaction for [MFI], [MFG], and [ORD].
Code context
This entry point can be found in the this script, before assigning MFGLIN to [F:MFI] in the subprogram CREMFI, and before assigning MFGLIN to the [M:MFGK] work order update buffer in $REL_OFS_GEN and $CRE_OFFP.
The records are retrieved from the ORDERS table based on the entered criteria.
You can use this entry point to assign multiple released products (MFGLIN values) to each work order. By default, in the standard, the line number is set to 1000 for a single released product.
The script must fill the following values:
- [F:MFGK]MFGLIN: Valid work order product line number
- GPE: Common entry point flag
The GPE must be set to 1 if the MFGLIN value is set for multi-product.
This function overwrites the value of MFGLIN to 1000 if GPE value is 0 and has not been set to 1.
Available variables and masks
- [F:MFI]: File class for Work order detail - Item.
- [F:MFG]: File class for Work order header.
- [F:ORD]: File class for ORDERS table.
- GPE: To use results of the entry point script if set to 1, or 0 if the standard function needs to be called.
Open tables
| Table | Significant content | Table title |
| MFGITM | No | Work order Item |
| MFGHEAD | No | Work order header |
| ORDERS | No | Work in progress |
AFTRCREOFSUG: After initiating a suggested order
Context and operating method
Code context
This entry point is located in the treatment of this script after initiating a suggested order.