BMRUSRKEY : Use of a specific access index to the BOMRET table

This entry point is used to take control of the read instruction of the BOMRET [BMR] table.

Context and operating method

Transaction

There is one transaction in progress.

Log file                        

None.

Variables, available screens and file classes

The [F:BOD] , [F :BOH] and [F :ITM] buffers are loaded at the time of the call to the entry point.

The GPE variable must be set to 1 to inhibit the standard read.

Open tables

In the table below, the significant content flag indicates that the content is coherent with the context (...).

Table

Significant content

Table Title

BOM

Yes

BOM header

BOMD

Yes

BOM detail

ITMMASTER

Yes

Product

 

BMRUSRDATA: Addition of specific information into the BOMRET table

This entry point is used to take control before update of the BOMRET [BMR] table in order to add specific information.

Context and operating method

Transaction

There is one transaction in progress.

Log file                        

None.

Variables, available screens and file classes

The [F :BMR],  [F:BOD] , [F :BOH] and [F :ITM] buffers are loaded at the time of the call to the entry point.

Open tables

In the table below, the significant content flag indicates that the content is coherent with the context (...).

Table

Significant content

Table Title

BMR

Yes

Work table of the component requirements

BOM

Yes

BOM header

BOMD

Yes

BOM detail

ITMMASTER

Yes

Product

 

CHECK_ITMSTA: Additional checks in the ITMMASTER table

This entry point is used to carry out additional checks in the product table (ITMMASTER) on the current component, in order to display or not this component.

Context and operating method

Transaction

There is no transaction in process.

Log file                        

There is an open log file.

Different call cases

This entry point is called inside the read loop of the BOM components (BOMD table), right after the read of the component on the ITMMASTER table.

Variables, available screens and file classes

The [F :BOD] et [F :ITM] buffers are loaded at the moment of the entry point call.

The GPE variable is used. It is set to the value 0 by default. It must be set to 1 in the specific/custom process linked to the entry point if the current component should not be displayed in the list.

On returning to the standard processing, the GPE variable is tested. If it is different from 0, the component will be read according to the BOM.

Open tables

In the table below, the significant content flag indicates that the content is coherent with the context (...).

Table

Significant content

Table Title

BOM

No

BOM header

BOMD

Yes

BOM detail

ITMMASTER

Yes

Product

BOMRET

No

Components requirements

 

CHECK_BOHSTA: Additional checks in the BOM table

This entry point is used to carry out additional checks in the header BOM table (BOM) on the current BOM, in order to display or not its components.

Context and operating method

Transaction

There is no transaction in process.

Log file                        

There is an open log file.

Different call cases

This entry point is called inside the read loop of the BOM components (BOMD table), right after the read of the BOM header on the BOM table.

Available variables and masks

The [[F :BOD], [F :ITM] and [F :BOH] buffers are loaded at the time of the call to the entry point.

The GPE variable is used. It is set to the value 0 by default. It must be set to 1 in the specific/custom process linked to the entry point if the BOM components should not be displayed in the list. For instance, if the BOM is being developped.

On returning to the standard processing, the GPE variable is tested. If it is different from 0, the read loop of the compoenents of the current BOM is exited.

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

BOMD

Yes

BOM detail

ITMMASTER

Yes

Product

BOM

Yes

BOM header

BOMRET

No

Components requirements