Usage > Interfaces > Inquiry 

This function is used to read the data stored in the interface table (INTERLOT).

A first screen provides an overview of the interfaces (no. of lots by interface and by report) which can be filtered by Site, Depositor and date range.

Using the "Detail" button, you can access a new screen used to view these interfaces sorted by site, depositor, interface and status. You can view the details of interfaces grouped by lot and then by interface line. A lot is a homogeneous set of interface lines (e.g.: Header + DO lines).

From this inquiry, you can also view error messages generated by the processing (INTERMES table).

A a given point in time, lots (header and corresponding lines) can have one of the four following status:
To process:
On import, the technical loading of the lot has been completed but the lot has not been integrated yet (the INTIMPORT processing will update it).
On export, the lot has not generated a file yet or must not generate a file (the INTERFIC processing will update it).

Processed:
On import, the functional integration of the lot is complete and the object has been created in Warehousing.
On export, the lot generated a file or has been processed for L3.

On error:
On import, the lot has not been functionally integrated in Warehousing.
On export, the lot could not generate a file.

On processed error:
On import, lots presenting errors have been updated manually in this function so that they are no longer considered during further integrations.

Prerequisites

SEEREFERTTO Refer to documentation Implementation

Screen management

The first screen:
after entry of a site (or no site), of a depositor and/or of a date range, existing data is displayed in a grid and chart.

The second screen:
Using the results of the first screen, you can access a detailed view where existing data are displayed in a grid with 3 tabs detailing the following:
- The Interface tab display a line by Interface and Status code. This makes it possible to quickly view any errors (especially concerning the imports).
- The Batches tab lists the corresponding batches/lots for the previously mentioned interface.
- The Lines tab lists the fields of a previously selected lot.
- The Numbering tab displays a summary of exchanged flows.

Header

Presentation

When selecting a recording in the Interfaces tab, data is displayed in the header. This information relates to the first lot record of the line; other information can then be viewed on the Batches tab.

Interface

The site, depositor, interface code and setup name are displayed. The interface status is also displayed.

Lot

The reference is the lot identifier; as a general rule, this is the expected input reference, the direct input reference, the delivery order reference, the product code.

The number corresponds to the ID of each recording. The file corresponds to the generated or integrated file. If it is not specified, the recording is considered as "To be processed".

The date and time of creation relate to the date of data integration into the interface table. The date and time of modification relate to the date of data integration into the live tables.

Close

 

Fields

The following fields are present on this tab :

Interface

 

 

 

 

  • Status (field ITLSTA)

 

Lot

  • Reference (field LOTREF)

 

  • Number (field LOTSEQ)

 

  • Created (field CREDAT)

 

  • field CRETIM

 

  • File (field FILNAM)

 

  • Modified (field UPDDAT)

 

  • field UPDTIM

 

Block number 3

Close

 

Tab Interfaces

Presentation

Recordings are grouped by Site, Depositor, Setup and status code.

Status can have the following values:

Status

Value

Next status

To be processed

1

Import

Export

2, 5, 3, 7

2, 6, 7

Processed

2

-

Integration error

3

1, 4

Error processed

4

-

Import error

5

1, 4

Export error

6

1, 4

Blocked

7

1

Using the action menu of a line, you can force the status to move from

To be processed to Blocked.
Integration error to To be processed or Processed error.
Integration error to To be processed or Error processed.
Export error to To be processed or Error processed.
Blocked to To be processed.

For example, with the DO interface of a specific depositor presenting errors.

Close

 

Fields

The following fields are present on this tab :

Grid

  • field CUT

 

 

 

 

  • Status (field ITLSTA)

 

Block number 2

  • field PREICO

No help linked to this field.

  • field NEXICO

 

Close

 

Action icon

To be processed -> Blocked
Blocked -> To be processed
Error -> To be processed
Error -> Error processed
Blocked -> Error processed

 

Close

 

Tab Batches

Presentation

Batches

From a recording selected in the Interfaces tab, the Batches tab displays all the lines of this recording.

Errors

From a recording of the Batches section, the corresponding error (if any) is displayed.

For example, viewing the generic integration error for a DO with 3 lines.

Close

 

Fields

The following fields are present on this tab :

Grid Batches

  • field CUT

 

  • Number (field LOTSEQ)

 

  • Reference (field LOTREF)

 

  • File (field FILNAM)

 

  • Log file (field FILTRC)

 

  • Created (field CREDAT)

 

  • Time (field CRETIM)

 

  • Modified (field UPDDAT)

 

  • Time (field UPDTIM)

 

Block number 3

  • field PREICO2

No help linked to this field.

  • field NEXICO2

 

Grid Errors

  • Line (field LIN)

 

  • Field code (field CODZON)

 

  • Index (field IND)

 

  • Value (field VALZON)

 

  • Error (field ERR)

 

Block number 4

  • field PREICO22

No help linked to this field.

  • field NEXICO22

 

Close

 

Action icon

To be processed -> Blocked
Blocked -> To be processed
Error -> To be processed
Error -> Error processed
Blocked -> Error processed
Log
Read Log File

 

Close

 

Tab Lines

Presentation

Tables

From a recording selected in the Batches tab, the Lines tab displays the details of recordings. For example, header and line, or product and product containers.

Field

From a recording of the Tables section, the value of each field is displayed.
If an error occurs, it is still specified.

Using the action menu, the table can be sorted by filed code or based on the template setup.

For example, viewing that the product code of the second line does not exist for the depositor.

Close

 

Fields

The following fields are present on this tab :

Grid Tables

  • field CUT

 

  • Line (field WWILOTLIN)

 

 

 

  • Description (field TEXTE)

 

  • Action (field WWIACT)

 

Block number 3

  • field PREICO3

 

  • field NEXICO3

 

Grid Fields

  • Field code (field CODZON)

 

  • Index (field IND)

 

  • Value (field VALZON)

 

  • Error (field ERR)

 

  • Model rank (field ROW)

 

Close

 

Action icon

Sorted by model rank
Sorted by alphabetic order

 

Close

 

Tab number 4

Fields

The following fields are included in this window :

Close

Other conditions

The operating process of interfaces is controlled by a unique processing called: INTERFACE. This is the case since patch 5, which corresponds to the interfaces redesign. Before patch 5, two separate processings were used: INTERFIC and INTIMPORT were respectively used to load or generate files and to integrate data.

The following algorithm provides the main actions and controls applied, based on the interface mode:

Import

For each file found in the import directory (IMPREP):

  •  Checking if the file name can be located in the active interface settings

If Yes,

  • Moving the file to the import processing directory (IMPTRTREP)
  • Technical check of each recording field based on the import template of the interface

If check OK,

  • Loading the fields of each file recording into the interface tables (WI*).
  • Moving the file to the end destination directory (IMBAKPREP)
  • Adding a time-stamped line to the log file ("Importing file...") as well as a line for each identified lot ("Processing lot...").
  • Adding a line to the interface lot table (INTERLOT) with the "To be processed" status.

If not

  • Adding a line to the interface lot table (INTERLOT) with the "Import error" status.

If not

  • Moving the file to the error directory (IMPERRREP)

For each interface lot on import with the "To be processed" status:

For each lot line in the interfaces tables:

  • Loading the values into the entered screens for each entered field
  • If in creation mode, assigning default values
  • Functional check of each entered field

If check OK,

  • Transaction validation
  • Update of the interface lot with the "Processed" status
  • Adding a time-stamped line to the log file ("Processing lot...")

If not,

  • Transaction cancellation.
  • Update of the interface lot with the "Integration error" status.
  • Adding a line to the error message table (INTERMES) for each field in error.

Export

Following each processing validation (Input, Output, Transfer, Replenishment,...):

  • Adding a line to the interfaces tables (WI*) for each given recording.
  • Adding a line to the interface lot table (INTERLOT) with the "To be processed" status.

If management with flat files,

  • Incrementing the counter defined at the interface level or by default, the counter attached to the interface lot table.

For each interface lot on export with the "To be processed" status:

For each lot line in the interfaces tables:

  •  Adding a recording to the interface file located in th export processing directory (EXPREP2)

If writing OK,

  • Moving the interface file to the export directory (EXPREP),
  • Copying the file to the backup directory (EXPBAKREP)
  • Updating the interface lot with the "Processed" status.
  • Otherwise, update of the interface lot with the "Export error" status.

Reports

By default, the following reports are associated with this function :

 INTERR : Interfaces in anomaly

This can be changed using a different setup.

Menu Bar

Accessing an entry window with search criteria.

Menu Bar

Viewing the generated log for the selected lot.

Viewing the generated log for the selected lot.

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

Many errors can be generated after standard integrity controls have been implemented; errors also depend on the template setup.

Tables used

SEEREFERTTO Refer to documentation Implementation