MFIMAJ: Updating the specific fields in the released product line file

Use this entry point to take over in work order creation just before creating the released product lines (this allows, for example, the initialization of specific fields).

Context and operating mode

Transaction

There is one transaction in progress.

To cancel the transaction if there is a problem, the GOK variable must be set to 0.

Log file

There is no open log file.

Available screen and file classes

The [F :MFI] buffer is loaded when calling the entry point.

The screen classes linked to the MFG object are open and loaded.

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

MFGITM

Yes

Released products

MFGOPE

No

Operations

MFGMAT

No

Materials

MFGPRN

No

Documents

ORDERS

No

WIPs

SCHEDULING

No

Scheduling

OPERATIONS

No

Loading

ROUTING

Yes

Routing header

ROUOPE

No

Routing operations

ROUSCD

Yes

Route - Scheduling

BOM

No

BOMs

BOMD

No

BOM lines

FACILITY

No

Site

 

RECUP_NOF: Imposing WO number

Use this entry point to take over the work order creation "INICRE" action just before the WO sequence number counter is retrieved (this enables, for example, to give a specific value to the WO number). When resuming the execution of the processing, the [M :MFG0]MFGNUM field value is tested. If this value is "  ", the system will automatically assign the WO number by retrieving the associated sequence number.

Context and operating mode

Transaction

There is one transaction in progress.

To cancel the transaction if there is a problem, the GOK variable must be set to 0.

Log file

There is no open log file.

Available screen and file classes

The [F :MFG] buffer is loaded when calling the entry point.

 

The screen class linked to the WO object is loaded. [M :MFG0] is loaded with the WO header data, [M :MFG1] with the released product lines, [M :MFG2] with the component lines, [M :MFG3] with the operation lines and [M :MFG4] with the data concerning the documents.

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

MFGITM

No

Released products

MFGOPE

No

Operations

MFGMAT

No

Materials

MFGPRN

No

Documents

ORDERS

No

WIPs

SCHEDULING

No

Scheduling

OPERATIONS

No

Loading

TABROUALT

Yes

Alternative routes

ROUTING

Yes

Routing header

ROUOPE

No

Routing operations

ROUSCD

Yes

Route - Scheduling

ITMMASTER

No

Product

ITMFACILIT

No

Product-site

TABBOMALT

No

BOM alternatives

BOM

No

BOMs

BOMD

No

BOM lines

FACILITY

No

Site

BPARTNER

Yes

A/P - A/R Accounting

BPCUSTOMER

Yes

Customer

TABUNAVAIL

No

 

ITMMVT

No

Product-site totals

WORKSTATIO

No

Work center

TABWRKCTR

No

Work center group

WORKCOST

No

Costing dimensions

ROUOPESTD

No

Standard operations

ROHMAJ: Updating the specific fields in the ROUTING file (routing header)

Use this entry point to take over:

-         in WO creation just before rewriting the routing header (this is used, for example, to modify specific fields).

-         in WO modification just before the rewriting the routing header (this is used, for example, to modify specific fields).

Context and operating mode

Transaction

There is one transaction in progress.

To cancel the transaction if there is a problem, the GOK variable must be set to 0.

Log file

There is no open log file.

Available screen and file classes

The [F :MFG] buffer is loaded when calling the entry point.

The screen classes linked to the MFG object are open and loaded.

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

MFGITM

Yes

Released products

MFGOPE

Yes

Operations

MFGMAT

Yes

Materials

MFGPRN

No

Documents

ORDERS

Yes

WIPs

SCHEDULING

No

Scheduling

OPERATIONS

No

Loading

ROUTING

Yes

Routing header

ROUOPE

No

Routing operations

ROUSCD

Yes

Route - Scheduling

BOM

No

BOMs

BOMD

No

BOM lines

FACILITY

No

Site

 

OPTSCDRAZ: preventing the descheduling of optimized WOs

Use this entry point to prohibit the descheduling/rescheduling of optimized work orders (managed by an external detailed scheduling: see Connectors).

See also OPTSCDRAZ in JALLIBA and UPDSCD in SUBMTKC.

Context and operating mode

When validating a WO update.

Available screen and file classes

The [M:MFG*] screens are on line.

Use

This entry point was designed in order to prevent the descheduling/rescheduling of WOs with an Optimized scheduling status. To do so, the GPE variable must be activated.


The EP code is the following:

#---------------------------------------------------------------

# Processing: ZMFGLIBA

# Entry point: OPTSCDRAZ Issue 104504

# Not descheduling optimized WOs (External detailed scheduling)

#---------------------------------------------------------------

$ACTION

Case ACTION

When "OPTSCDRAZ": Gosub OPTSCDRAZ

Endcase

Return

#---------

$OPTSCDRAZ

GPE=1

Return

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

OF

MFGOPE

No

WO operations

SCHEDULING

No

WO scheduling data

ITMFACILIT

Yes

Product-site

FACILITY

Yes

Sites