BEFWRISUG: Before writing suggestion

Use this entry point before the write of a work order or purchase order suggestion.

Context and operating mode

Transaction

There is one transaction in progress.

Log file

There is an open log file.

Available variables and masks

The ORD class is loaded in full for the write and contains the order type.

Open tables

All the requirement calculation tables are open.

Miscellaneous

The suggestion is not written if the GPOINT variable is forced to an empty value.

BEFWRIORD: Before writing MWS requirement

Use this entry point before the write of a log file for the work order suggestion (MWS).

Context and operating mode

Transaction

There is one transaction in progress.

Log file

There is an open log file.

Available variables and masks

The ORD class is loaded in full for the write.

Open tables

All the requirement calculation tables are open.

Miscellaneous

The suggestion log is not written if the GPOINT variable is forced to an empty value.

MRPSCHDAT: Before scheduling suggestion

Use this entry point before the generation of the load and scheduling of a work order suggestion in order to act on the start and/or end dates.

Context and operating mode

Transaction

There is one transaction in progress.

Log file

There is an open log file.

Available variables and masks

The [OPSS] mask is loaded.

Sage recommends that you only intervene in the start and end dates (STRDAT and ENDDAT), and the reference date (TRTDAT).

The [CBH] class is loaded.

You can use this entry point to force a forward scheduling from the suggestion start date (calculated from the production lead time of the product-site record). To do this, the automatic forward rescheduling must be active, and the TRTDAT variable of the class forced to the suggestion start date.

Open tables

All the requirement calculation tables are open.

MRPWRITRC: Before writing MWS log files

Use this entry point before the write to the log files (MWS material requirements) following the calculation of a work order suggestion.

Context and operating mode

Transaction

There is one transaction in progress.

Log file

There is an open log file.

Available variables and masks

The [F:CBD1] class is loaded with the information corresponding to the MWS log file.

To prevent the standard write to the log file the GPE global variable can be set to 1.

You can use this entry point to split the requirement in order to implement a sequencing of supply.

Open tables

All the requirement calculation tables are open.

REPLANNING: Before replanning suggestion

Use this entry point before the replanning of a work order suggestion in order to act on the start and/or end dates.

Context and operating mode

Transaction

There is one transaction in progress.

Log file

There is an open log file.

Available variables and masks

The [OPSS] mask is loaded. The [CBH] variable is loaded. The GREPLANNING variable contains "RPL_PROCESS". 

Messages on resources in the firm horizon can be deleted by setting the XRPLNOMESS variable to 2.

The CTLSPE entry point on each resource can be triggered for replanning in $PROCESS_RESS by setting the XRPLCTLSPE variable to 2.

The CTLSPE

Open tables

All the requirement calculation tables are open.

CUSSELFLT: Inserting additional filters

Use this entry point to take over during the creation of selection filters in the replanning process.

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

The filter can be applied to the load WIP file (CBNDET [F:CBD] class).

Context and operating mode

Transaction

There is one transaction in progress.

Log file

There is an open log file.

Available variables and masks

The [OPSS] mask is loaded. The [CBH] variable is loaded. The GREPLANNING variable contains "RPL_PROCESS". 

Open tables

All the requirement calculation tables are open.

CTLBOMALT: BOM modification

Use this entry point to take over before the read of the components in order to change the bill of materials (BOM), if necessary, according to the requirement date or quantity.

Context and operating mode

Transaction

There is one transaction in progress.

Log file

There is an open log file.

Available variables and masks

The [CBH] class is loaded.

The BOM code to read is located on [F:CBH]BOMALT and [F:CBH]BOMALTTYP. These values can be replaced by the components loading time. In standard mode, this information will be copied to the [CBD] detail table where it will be added (ITMREFORI + BOMALT + BOMALTTYP will be used to locate the BOM which was used to generate the material requirement).

The requirement date has been copied to WDAT = [F:CBD]REQDAT.

The requirement quantity has been copied to WBES = [F:CBD]REQQTY.

The GPE variable is set to 0. If the loop on [F:BOD] must not be triggered change the GPE variable to a value different from 0.

Open tables

All the requirement calculation tables are open.

CTLSPE: Specific control on replanning resources

Use this entry point to take over before the replanning of each selected resource.

Context and operating mode

Transaction

There is one transaction in progress.

Log file

There is an open log file.

Available variables and masks

The [OPSS] mask is loaded. The [CBH] and [CBD] classes are loaded. The GREPLANNING variable contains "RPL_PROCESS". 

Set the GPE variable to a value different from 0 if the resource does not need replanning.

For the CTLSPE entry point to be triggered, the XRPLCTLSPE variable must have been set to 2 by the REPLANNING entry point.

The CTLSPE

Open tables

All the requirement calculation tables are open.

BEFREWORD: Before rewriting WOS WIP

Use this entry point after the scheduling in order to trigger an update of the WOS WIP or an impact on the child WIPs (MWS requirements).

Context and operating mode

Transaction

There is one transaction in progress.

Log file

There is an open log file.

Available variables and masks

The ORD class is loaded in full for the write.

Open tables

All the requirement calculation tables are open.

Miscellaneous

An update of the [F:ORD] WIP can be triggered on which the STRDAT and ENDDAT dates are updated by the [M:OPSS] data upon exiting the scheduling, if the GPE variable is forced to a value greater than zero.

BEFREWCBD: Before rewriting MRP result

Use this entry point after the scheduling in order to prevent an update of the WOS result, or an impact on the induced MWS requirements.

Context and operating mode

Transaction

There is one transaction in progress.

Log file

There is an open log file.

Available variables and masks

The CBD class is loaded in full for the write.

Open tables

All the requirement calculation tables are open.

Miscellaneous

An update of the CBN [F:CBD] result can be prevented after the scheduling, if the GPE variable is forced to a value different from zero.

RPREWRICBD: Rewriting MRP result

Use this entry point after the resource replanning to modify the MRP result.

Context and operating mode

Transaction

There is one transaction in progress.

Log file

There is an open log file.

Available variables and masks

The CBD class is loaded in full for the write.

Open tables

All the requirement calculation tables are open.

Miscellaneous

To prevent the CBN [F:CBD] class from being rewritten, set the GPE variable to a value greater than zero. If the standard rewrite is required, do not modify the GPE variable or keep it as zero.