MFGALL processing: WO allocation
MFMALL: Inserting additional filters
This entry point is used to insert additional logic in the allocation of each component linked to the production. It is called in all allocation cases (WO management, planning workbench, automatic processings, etc.) and is used in particular to activate/deactivate the allocation of a component matching certain criteria.
Context and operating mode
Transaction
There is one transaction in progress.
Log file
There is no open log file.
Available screens and file classes
The MFGMAT ([F :MFM ], ITMMASTER ([F :ITM]) and ITMFACILIT ([F :ITF]) tables are loaded when calling the entry point.
Use
This entry point has been designed so that the allocation of components matching certain criteria can be deactivated. This deactivation is possible by setting the WRET variable to 9. Leave the WRET variable to its current value if the component must be assigned.
Open tables
In the table below, the significant content flag indicates that the content is in phase with the context.
Table | Significant content | Table Title |
MFGMAT | Yes | Materials |
ITMMASTER | Yes | Products |
ITMFACILIT | Yes | Products-sites |
ALLCHO: Modifying the value of the allocation mask fields
This entry point is used to take control immediately after loading the WO allocation mask. It is used to modify the content of allocation mask fields.
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 MFMALL mask is loaded when calling the entry point.
Use
This entry point has been designed so that the value of the MFGALL mask fields can be modified. For example, it can be used to modify the [M :MFA]TALL field, so as to suggest by default a detailed allocation rather than a global allocation.
Open tables
In the table below, the significant content flag indicates that the content is in phase with the context.
Table | Significant content | Table Title |
MFGHEAD | Yes | WO-Header |
ALLCHOMAT: Possibility to allocate specific components of WOs
Use this entry point to take over right before the WO component allocation. It is used to short-circuit the standard allocation in order 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 screens and file classes
The MFMALL mask is loaded when calling the entry point.
The MFGHEAD [F:MFG] and MFGMAT [F:MFM] tables are loaded when calling the entry point.
Use
This entry point has been designed to allow the taking over in the WO component allocation loop.
It is used to short-circuit the standard allocation in order to carry out an allocation based on specific criteria. For instance, it can be a specific field linked to each material that indicates the allocation type (global, detailed, etc.) that must be applied to allocate the material.
The GPE variable is used. It is set to the value 0 by default. It must be set to 1 to short-circuit the standard processing allocation.
Open tables
In the table below, the significant content flag indicates that the content is in phase with the context.
Table | Significant content | Table Title |
ORDERS | No | Product WIP |
MFGHEAD | Yes | WO header |
MFGMAT | Yes | WO components |
MFMMAJ: Specific update of the MFGMAT WO materials file
This entry point is used to take over during the update of the WO material allocation, right before the MFGMAT table is updated.
Context and operating mode
Transaction
There is one transaction in progress.
Log file
There is no open log file.
Available screens and file classes
The [F:MFG] and [F:MFM] buffers are loaded when the entry point is called.
Use
This entry point is used to take over when updating a WO material allocation (ALLOC_MAT sub-program) or all the materials of a WO (ALLOC_OF sub-program). It is used to intervene right before updating the allocation of each component, in other words before updating the MFGMAT table.
it is possible to know the call context of each allocation sub-program by querying the value of the LTRT variable.
Possible values of LTRT:
. LTRT = "C": creation,
. LTRT = "M": modification,
. LTRT = "A": cancellation,
. LTRT = "E": switch from a global allocation to a detailed allocation.
Open tables
In the table below, the significant content flag indicates that the content is in phase with the context.
Table | Significant content | Table Title |
ORDERS | No | Product WIP |
MFGHEAD | No | WO header |
MFGMAT | Yes | WO components |
MODALLMAT: modification of the material allocations
This entry point is used to take control if the WO component allocations is modified. It is used to short-circuit the standard processing in which the quantity shortage was allocated in order to replace it by a specific processing, for example in order to comply with a single lot allocation rule.
Context and operating mode
Transaction
There is one transaction in progress.
Log file
There is no open log file.
Available screens and file classes
The ALLPAR screen class is loaded when calling the entry point, as well as the MFGMAT ([F :MFM]), ITMMASTER ([F :ITM]) and ITMFACILIT ([F :ITF]) tables.
Use
This entry point is used to short-circuit the allocation of WO components when allocations are modified in order to replace it with a specific allocation.The GPE variable is used.It is set to the value 0 by default.It must be set to 1 to short-circuit the standard processing allocation.
Open tables
In the table below, the significant content flag indicates that the content is in phase with the context.
Table | Significant content | Table Title |
MFGMAT | Yes | Materials |
ITMMASTER | Yes | Products |
ITMFACILIT | Yes | Products-Sites |
CTLSHTMAT: control of shortages on materials allocations
Use this entry point to take over in case of shortages on WO components. It is used to complete the standard processing and potentially reallocate to another location all or part of the required quantity.
Context and operating mode
Transaction
There is one transaction in progress.
Log file
There is no open log file.
Available screens and file classes
The ALLPAR screen class is loaded when calling the entry point, as well as the MFGMAT ([F :MFM]), ITMMASTER ([F :ITM]) and ITMFACILIT ([F :ITF]) tables.
Use
This entry point has been designed to complete or replace the allocation of WO components in case of shortage (LSHT>0) in order to replace it with a specific allocation.
The parameters LALL="allocated qty" and LSHT="shortage qty" must be replaced with new allocated and shortage quantities on this component.
Open tables
In the table below, the significant content flag indicates that the content is in phase with the context.
Table | Significant content | Table Title |
MFGMAT | Yes | Materials |
ITMMASTER | Yes | Products |
ITMFACILIT | Yes | Products-Sites |
ALLMATMAJ: update of specific fields of the WO material table
Use this entry point to take over during the update of the WO material table following manual allocations, right before the MFGMAT table is updated.
Context and operating mode
Transaction
There is one transaction in progress.
Log file
There is no open log file.
Available screens and file classes
The [F:MFM] buffer is loaded when calling the entry point.
Use
Use this entry point to take over during the update of the WO material table following manual allocations.It is used to intervene right before updating the allocation of the current component, in other words just before updating the MFGMAT table.
Open tables
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 |
MFGMAT | Yes | WO components |