PREACTOR parameters @ L.V. Expertise X3

Prerequisite

SEEREFERTTO Refer to documentation Implementation

Screen management

Entry screen

Presentation

The setup consists in indicating:

The pivot references giving the description of .csv files to export.
The destination directory where the files designed to PREACTOR are indicated.
The directory to check where the files to import coming from PREACTOR will be read.
The storage directory where the processed files will be converted, after import.

Fields

The following fields are present on this tab :

Block number 1

Identifier (field ID)

Identification code of the interface setup.

field INTIT

Pivots for export

Operations (field OPEPIT)

Enter the pivot code describing the file lines of the Operations/WOs to export: EXPOF.csv.
By default this is the PREOPE pivot.

Products (field ITMPIT)

Enter the pivot code describing the file lines of the Products to export: EXPITEM.csv.
By default this is the PREITM pivot.

Customers (field BPCPIT)

Enter the pivot code describing the file lines of the Customersto export: EXPCLI.csv.
By default, this is the pivot: PREBPC

Projects (field PJTPIT)

Enter the pivot code describing the file lines of the Projectsto export: EXPAFF.csv.
By default, this is the pivot: PREPJT.

Orders (field ORDPIT)

Enter the pivot code describing the file lines of the Orders to export: EXPCOM.csv.
By default this is the PREORD pivot.

BOMs (field BOMPIT)

Enter the pivot code describing the file lines of the BOMs to export: EXPBOM.csv.
By default this is the code of the PREBOM pivot.

Grouping (field GRUBOMFLG)

This indicator is activated to specify that all material requirements of a WO must be grouped by product: the quantities required for all the WO operations will be added to the first operation of the WO requiring this product.

Purchasing (field POFPIT)

Enter the pivot code describing the file lines of the Purchasing to export: EXPACH.csv.
By default this is the PREACH pivot.

Stock (field STOPIT)

Enter the pivot code describing the file lines of the Stocks to export: EXPSTOCK.csv.
By default this is the PRSTO pivot.

Work center groups (field TWCPIT)

Enter the pivot code describing the file lines of the work centers to export: EXPGRRES.csv
By default this is the PRECDC pivot.

Work centers (field MWSPIT)

Enter the pivot code describing the file lines of the work centers to export: EXPRES.csv.
By default this is the PREWST pivot.

Work centers by group (field WSTPIT)

Enter the pivot code describing the file lines of the work centers to export: EXPGRRESMatrix.csv
By default this is the PRECWST pivot.

Alternate work centers (field RPLPIT)

Enter the pivot code describing the file lines of the replacement work centers to be exported: EXPALTER.csv.
By default this is the PRERWST pivot.

Secondary resources (field RSSPIT)

Enter the pivot code describing the file lines of the Secondary resources to export: EXPRESSEC.csv.
By default, it is the code of the PRERSS pivot.

Directories

Destination type (field TYPEXP)

Directory to be scanned (field VOLFILRCP)

Storage directory (field VOLFILSTO)

Index destination (field VOLFILISS)

Export flow: X3 --- PREACTOR
Import flows: PREACTOR --- X3
Entry points

Principles of the functioning

The interface processing is carried out via the .csv files.

General information on the files

The files are DOS files (end of line characters: \013\010 or \r\n).
Format: .csv
Type : ASCII (can be modified by entry point, see below)
The fields have a variable length with separators ";" (can be modified by entry point, see below)
The numbers have as decimal separator: the point.
The dates are entered under the "YYYYMMDDHHmm" or "YYYYMMDD" forms
The durations are expressed in hours
The Booleans can either take the value: 0 (false, or 1 (true)
The files have headers.

- For the Sage X3 to PREACTOR, the description of each file line is given by a Pivot specifying the fields orders, their size and describing their loading (directly via table fields or via functions).
The files name, their description and the pivots used by default are indicated below.

- For the PREACTOR flows to Sage X3, the import is carried out by reading a fixed file that cannot be set up.

Export flow: X3 --- PREACTOR

Expected files		Default pivots
EXPOF.csv.	Work orders/operations	PREOPE
EXPITEM.csv.	Products	PREITM
EXPCLI.csv	Customers	PREBPC
EXPAFF.csv	Projects	PREPJT
EXPCOM.csv.	Orders	PREORD
	Material tracking files:
EXPBOM.csv.	BOMs	PREBOM
EXPSTOCK.csv	Stocks	PRESTO
EXPACH.csv.	Purchasing	PREACH
	Resource files:
EXPRES.csv.	Work stations	PREWST
EXPGRRES.csv	Work centers	PRECDC
EXPGRRESMatrix.csv	Work centers by work center (resources matrix)	PRECWST
EXPALTER.csv	Replacement work centers	PRERWST
	Secondary resource files:
EXPRESSEC.csv	Secondary resources	PRERSS

Import flows: PREACTOR --- X3

Expected files		Pivot
OrdersOut.csv	Planning results	No pivot

This file is fixed and cannot be set up via a pivot. It contains the planning results, i.e. the start and end dates of each operation.

Entry points

The PIVOTSFILE entry point of the CONNECTFCT processing is used to modify the files coding and the column separator.

WO/Operations: EXPOF.csv
Products: EXPITEM.csv
Customers: EXPCLI.csv
Affaires : EXPAFF.csv
Orders: EXPCOM.csv
BOMs: EXPBOM.csv
Stock: EXPSTOCK.csv
Purchasing: EXPACH.csv
Work stations: EXPRES.csv
Load centers: EXPGRRES.csv
Resources matrix: EXPGRRESMatrix.csv
Replacement work stations: EXPALTER.csv
Secondary resources: EXPRESSEC.csv

Description of the exported files from Sage X3

WO/Operations: EXPOF.csv

Pivot: PREOPE

File	No.	Title	Type	Optional	Pivot	Table code	Field code	Title	Field not managed
	1	WO number	A	No		OPERATIONS	MFGNUM	Order no.	No
	2	WO description	A	Yes		MFGITM	MFGDES	WO description	No
	3	WO status (1)	N	Yes		OPERATIONS	OPSSTA	Order status	No
	4	Priority (2):	N	Yes		MFGHEAD	MFGPIO	Priority	No
	5	Product code	A	No		MFGITM	ITMREF	Product	No
	6	Quantity	N	No		MFGOPE	EXTQTY	Planned quantity	No
	7	Operation status (3)	N	No		OPERATIONS	OPESTA	Operation status	No
						OPERATIONS	WFICTRTDAT		Yes
	8	Reconciliation date (file extraction)	DH	No		OPERATIONS	WDHFIC		No
	9	Unit	A	Yes		ITMMASTER	STU	Stock unit	No
	10	WO end lead-times	D	No		MFGHEAD	OBJDAT	Initial objective	No
	11	Customer code	A	Yes		OPERATIONS	WCLI		No
	12	Project code	A	Yes		MFGITM	PJT	Project	No
	13	Order code	A	Yes		MFGITM	VCRNUMORI	Original journal	No
	14	Operation number	N	No		OPERATIONS	OPENUM	Operation	No
	15	Operation title	A	Yes		OPERATIONS	WDES		No
	16	Work center (Workshop)	A	No		OPERATIONS	WCR		No
	17	Main work center (4)	A	No		OPERATIONS	EXTWST	Planned work station	No
	18	Type of Process Time (5)	N	No		OPERATIONS	PROTIMTYP		No
	19	Process time	N	No		OPERATIONS	EXTOPETIM	Planned op. time	No
	20	X3 setting time (6)	N	Yes		OPERATIONS	EXTSETTIM	Planned setting time	No
	21	Preparation time (7)	N	Yes		OPERATIONS	PRPTIM	Picking time	No
	22	Wait times	N	Yes		OPERATIONS	PSPTIM	Post operating time	No
	23	Overlapping in % (8)	N	No		OPERATIONS	WLNKTIM		No
	24	Overlapping code (9)	N	No		OPERATIONS	WLNKTYP		No
	25	Grouping time	A	Yes		OPERATIONS	SCHGRP	Grouping criteria	No
	26	Operator secondary Constraint	A	Yes		MFGOPE	EXTLAB	Planned M-O work center	No
	27	Operators No.	N	Yes		MFGOPE	EXTLABNBR	Planned mo number	No
	28	% operator use	N	Yes		MFGOPE	OPELABCOE	Operation m-o time coefficients	No
	29	Tool secondary constraint	A	Yes		MFGOPE	EQUNUM	Tools	No
	30	Tools no.	N	Yes		MFGOPE	WEQUNBR		No
	31	% tools use	N	Yes		MFGOPE	WEQUPER		No

(1) 1 = Firm, 2 = Planned, 3 = Suggested
(2) 1 = Normal, 2 = Urgent, 3 = Very urgent.
(3) 1 = Pending, 2 = Previous in progress, 3 = Previous paid, 4 = Pending, 5 = Paid
(4) the alternative work centers are given via the alternative work centers file.
(5) 1 = unitary time, 2 = global time.
(6) Can be disconnected by a "Toogle" field in the resource groups table.
(7) Added to the previous operation wait time.
(8) 100% = no overlapping
(9) 1 = start - start = synchro at start, 2 = successor = no overlapping, 3 = end - end = synchro at the end, 4 = WO synchro
The overlapping code and the overlapping % on an operation indicate the position of the next operation. So the overlapped operation has the code 1 and the overlapping %.
The overlapping code 4 is contained in the concerned operation, it indicates that the operation has to start at the same moment as the WO first operation.

Notes:

All the times are expressed in hours.
All the operations are exported even though they are paid (quantity = 0).
The WOs are not exported if all the WO operations are paid.

Products: EXPITEM.csv

Pivot: PREITM

File	No.	Title	Type	Optional	Pivot	Table code	Field code	Title	Field not managed
	1	Product code	A	No		MFGITM	ITMREF	Product	No
	2	Description 1	A	Yes		ITMMASTER	ITMDES1	Description 1	No
	3	Description 2	A	Yes		ITMMASTER	ITMDES2	Description 2	No
	4	Description 3	A	Yes		ITMMASTER	ITMDES3	Description 3	No
	5	Product category	A	Yes		ITMMASTER	TCLCOD	Category	No
	6	Attribute 1	A	Yes		ITMMASTER	ATT1		No
	7	Attribute 2	A	Yes		ITMMASTER	ATT2		No
	8	Attribute 3	A	Yes		ITMMASTER	ATT3		No
	9	Attribute 4	A	Yes		ITMMASTER	ATT4		No
	10	Attribute 5	A	Yes		ITMMASTER	ATT5		No

Customers: EXPCLI.csv

Pivot: PREBPC

File	No.	Title	Type	Optional	Pivot	Table code	Field code	Title	Field not managed
	1	Customer code	A	No		BPCUSTOMER	BPCNUM	Customer	No
	2	Customer name	A	Yes		BPCUSTOMER	BPCNAM	Corporate name	No
	3	Postcode	A	Yes		BPADDRESS	POSCOD	Postcode	No
	4	Town/city	A	Yes		BPADDRESS	CTY	Town/city	No
	5	Contact number	A	Yes		BPCUSTOMER	CNTNAM	Default contact	No
	6	Contact's phone no.	A	Yes		CONTACT	TEL	Telephone	No
	7	Email address	A	Yes		CONTACT	WEB	E-mail	No

Affaires : EXPAFF.csv

Pivot: PREPJT

File	No.	Title	Type	Optional	Pivot	Table code	Field code	Title	Field not managed
	1	Project code	A	No		OPPOR	OPPNUM	Project chrono	No
	2	Project description	A	Yes		OPPOR	OPPDES	Project description	No

Orders: EXPCOM.csv

Pivot: PREORD

File	No.	Title	Type	Optional	Pivot	Table code	Field code	Title	Field not managed
	1	Order code	A	No		SORDER	SOHNUM	Order no.	No
	2	Order description	A	Yes		SORDER	WDES		No

BOMs: EXPBOM.csv

Pivot: PREBOM

File	No.	Title	Type	Optional	Pivot	Table code	Field code	Title	Field not managed
	1	WO number	A	No		ORDERS	VCRNUM	Journal	No
	2	Product reference	A	No		ORDERS	ITMREF	Product	No
	3	Quantity	N	No		ORDERS	RMNEXTQTY	Remaining quantity	No
	4	Operation (not used)	N	No		ORDERS	VCRSEQ	Document sequence no.	No

Notes:

It is possible that the same product is necessary for different operations. The duplicates on WO/Product are not managed in PREACTOR, a flag in the setup is used to group all the material needs of a WO by product: the quantities required for all the WO operations will be added to the first operation of the WO requiring this product.

Stock: EXPSTOCK.csv

Pivot: PRESTO

File	No.	Title	Type	Optional	Pivot	Table code	Field code	Title	Field not managed
	1	Product code	A	No		ITMMVT	ITMREF	Product	No
	2	Stock date	D	Yes		ITMMVT	WDATSTO		No
	3	Quantity in stock	N	Yes		ITMMVT	PHYSTO	'A' internal stock	No

Purchasing: EXPACH.csv

Pivot: PREACH

File	No.	Title	Type	Optional	Pivot	Table code	Field code	Title	Field not managed
	1	Purchase order no.	A	No		ORDERS	VCRNUM	Journal	No
	2	Product reference	A	No		ORDERS	ITMREF	Product	No
	3	Ordered quantity	N	No		ORDERS	RMNEXTQTY	Remaining quantity	No
	4	Planned due date.	D	No		ORDERS	ENDDAT	End date	No

Work stations: EXPRES.csv

Pivot: PREWST

File	No.	Title	Type	Optional	Pivot	Table code	Field code	Title	Field not managed
	1	Code	A	No		WORKSTATIO	WST	Work centre	No
	2	Description	A	Yes		WORKSTATIO	WSTDES	chge work center title	No
	3	Type (1)	A	Yes		WORKSTATIO	WSTTYP	Work center type	No
	4	Efficiency (2)	N	Yes		WORKSTATIO	EFF	Efficiency in %	No
	5	Finished or Infinite? (3)	N	Yes		WORKSTATIO	WCONSTRAINT	Valuation dimension	No
	6	Dimension	A	Yes		WORKSTATIO	VLTCCE		No

(1) 1 = Machine, 2 = MO, 3 = SC Sub-contracting.
(2) If not entered, the value is set by default on 100%.
(3) If this value is not entered in the file, it should be done manually in the PREACTOR table; it must follow the rule: 0 = Infinite, 1 = Finished.
N.B.: by default, PREACTOR does not take into account the value passed by Sage X3.

Load centers: EXPGRRES.csv

Pivot: PRECDC

File	No.	Title	Type	Optional	Pivot	Table code	Field code	Title	Field not managed
	1	Code	A	No		TABWRKCTR	WCR	Work centre group	No
	2	Description	A	Yes		TABWRKCTR	WCRDES	Center title	No

Notes:

This file contains the list of work center groups.
The work center groups all the resources belonging to the same workshop. However, it has no technical meaning. In order to determine the list of possible resources for a given operation, PREACTOR uses the main work center of the range and alternative work centers included in the Work stations file.

Resources matrix: EXPGRRESMatrix.csv

Pivot: PRECWST

File	No.	Title	Type	Optional	Pivot	Table code	Field code	Title	Field not managed
	1	Work center code	A	No		WORKSTATIO	WCR	Work centre	No
	2	Work station code	A	No		WORKSTATIO	WST	Work centre	No

Notes:

This file contains the list of resources by work center.
Each work center is duplicated for each workstation belonging to it. A work station can belong to several work centers.
The header cannot be modified and must have the following value: Name|Match|String;Resources|Data|String

Replacement work stations: EXPALTER.csv

Pivot: PRERWST

File	No.	Title	Type	Optional	Pivot	Table code	Field code	Title	Field not managed
	1	Main work station code	A	No		RPLWST	WST	Work centre	No
						RPLWST	I		Yes
	2	Alternative work station code	A	Yes		RPLWST	RPLWST	Replacement work center	No

Secondary resources: EXPRESSEC.csv

Pivot: PRERSS

File	No.	Title	Type	Optional	Pivot	Table code	Field code	Title	Field not managed
	1	Code	A	No		WORKSTATIO	WST	Work centre	No
	2	Description	A	Yes		WORKSTATIO	WSTDES	chge work center title	No
	3	Type (1)	A	No		WORKSTATIO	WSTTYP	Work center type	No

(1) Resource type: 2 = Operator, 3 = Tools

Description of the file imported in Sage X3

Planning results: OrdersOut.csv

No.	Title	Type	Optional
1	WO number	A	No
2	Operation number	N	No
3	Work station	A	No
4	Picking start date	DH	No
5	Setup start date	DH	No
6	Process end date	DH	No
7	Wait end date	DH	No

Note: this file is a fixed .csv file, that cannot be setup via a pivot.

Generic messages

Error messages

The only error messages are the generic ones.

Tables used

SEEREFERTTO Refer to documentation Implementation