Processing TRTBBYBOM: Assembly components

BOMDETBY: generation of the component grid

This entry point is used to take over on assembly and disassembly management at the time of generation of the component table. It makes it possible to replace the standard algorithm.

Context and operating method

Transaction

There is no transaction in process.

Log file                        

There is no open log file.

Available screen and file classes

The FUNCTION section (Integer) makes it possible to draw the difference between assembly and disassembly.

If FUNCTION = 1 :  Assembly

If FUNCTION = 2 Disassembly

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

 In assembly       the [M :BBY0]  screen class is loaded.

 In disassembly, the [M :DBY0] screen class is loaded.

Different call cases - Significant variables

This entry point has been designed to enable a fully specific read of the BOMD file in order to generate the component table.

This entry point replaces the read loop of the BOMD file, therefore it is imperative to include the following instruction in the specific loop:

   GOSUB INSERE   after loading of the BOMD buffer

The "GOSUB INSERE" instruction checks and inserts the BOMD components:

           In assembly       in the [M :BBY1] screen class.

           In disassembly in the [M :DBY1] screen class.

At the time of the call, the following setups are available:

       Char    M         : Compose

       Integer ALT       : Alternative

       Integer TYP       : Code type

       Date    DAT       : Reference date (loaded with date$)

       Integer FUNCTION  : Function 1 Assembly / 2 disassembly

       Char    LABR      : parent product screen

If this entry point carries out the table generation, a value different from 0 MUST be returned in the GPE section, thus short-circuiting the standard processing.

Skeleton of the entry point:

              For [BOD]BOD0 Where (specific filters)  

                    Gosub INSERE

Next

Open tables

In the table below, the significant content flag indicates that the content is in phase with the context (the current customer is loaded...).

BOMPHABY: enables a management of the phantom components different from the stan

This entry point is used to take control in the assembly and disassembly management at the time of the taking into account of a phantom.component. It makes it possible to replace the standard algorithm.

Context and operating method

Transaction

There is no transaction in process.

Log file                        

There is no open log file.

Available screen and file classes

The FUNCTION (integer) section makes it possible to draw the difference between assembly and disassembly.

If FUNCTION = 1 :  Assembly

If FUNCTION = 2 Disassembly

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

In assembly       the [M :BBY0] screen class is loaded.

                                 The phantom component is loaded into the [M :BBY1] screen.

In disassembly, the [M :DBY0] screen class is loaded.

                                 The phantom component is loaded into the [M :DBY1] screen.

Different call cases - Significant variables

This entry point has been designed to enable a management different from the standard one.

If this entry point carries out the table generation, a value different from 0 MUST be returned in the GPE section, thus short-circuiting the standard processing.

Open tables

In the table below, the significant content flag indicates that the content is in phase with the context (the current customer is loaded...).