MMS setup
This function is used to set up the interface to the MMS software: AXEL from the company DIMO Gestion.
This interface is used to manage, using data files in the .csv format, the flows coming from and going to AXEL-GMAO.
These flows can be summarized as follows:
- Sending of Purchase Requests (PR) from AXEL-GMAO to Sage X3 as PR or as order.
- Depending on the actions in Sage X3, update of the PR report in AXEL-GMAO:
- Conversion into an order
- Expected delivery date
- Complete or partial receipt
- Stock synchronization from Sage X3 to AXEL-GMAO
- Sending of the stock issues performed in AXEL-GMAO to Sage X3
- Ledger synchronization:
- Products identified as "Maintenance" from Sage X3 to AXEL-GMAO
- Cost centers from X3 to the budget dimensions in AXEL-GMAO
- Suppliers from Sage X3 to the AXEL-GMAO partners
Once the setup is done, the processing can be launched using the following function: MMS interface launch
Prerequisite
Refer to documentation Implementation
Screen management
Entry screen
The setup consists in indicating:
- The default work directory where the files to import must be searched and the files to export must be generated.
- The default storage directory of the processed files.
- The references of the export and import pivots describing the .csv files to process, specifying:
- for the Analytical dimensions: the dimension type of the cost center,
- for the Products: a selection formula,
- for theStock journal: whether the movements from the MMS and previously imported are taken into account (see below),
- for the Suppliers, a selection formula.
- The default value of the different headings loaded by the interface file.
Block number 1
| Identifier (field ID) |
|
Identification code of the interface setup. |
| field INTIT |
Block number 2
| Destination type (field TYPEXP) |
| Work directory (field VOLFILWRK) |
| Storage directory (field VOLFILSTO) |
Imports
| Purchase requests (field PSHPIT) |
|
Enter the pivot code describing the file lines of the Purchase request to import: MMSPSH.csv. |
| Movements (field MVTPIT) |
|
Enter the pivot code describing the file lines of the Stock issue movementsto export: MMSMVT.csv. |
| Dimension type (field DIEIMP) |
|
Specify the analytical dimension type for which a dimension will be imported by the stock transactions. |
Exports
| Analytical dimensions (field CCEPIT) |
|
Enter the pivot code describing the file lines of the Analytical dimensionsto export: MMSCCE.csv. |
| Dimension type (field DIE) |
|
Enter the dimension type for the cost center. |
| Sites (field FCYPIT) |
|
Renseignez le code du pivot décrivant les lignes du fichier des Sites de stockage à exporter : MMSFCY.csv. |
| Products (field ITMPIT) |
|
Enter the pivot code describing the file lines of the Productsto export: MMSITM.csv. |
| Selection formula (field ITMFOR) |
|
This field is used to specify a products selection reference, which will be suggested, by default, when launching the interface processing. |
| Product-site stock (field ITVPIT) |
|
Enter the pivot code describing the file lines of the Product stock - siteto export: MMSITV.csv. |
| Stock journal (field STJPIT) |
|
Enter the pivot code describing the file lines of the Stock journal to export: MMSSTJ.csv. |
| With MMS movement (field STJMMSFLG) |
|
When activated, this box indicates that during the stock journal export, the movements coming from the MMS (previously imported) have to be exported. |
| Suppliers (field BPSPIT) |
|
Enter the pivot code describing the file lines of the Customersto export: MMSBPS.csv. |
| Selection formula (field BPSFOR) |
|
This field is used to specify a supplier selection formula, which will be suggested, by default, when launching the interface processing. |
| Supplier contact (field CNTBPSPIT) |
|
Enter the pivot code describing the file lines of the ContactsSuppliersto export: MMSCNTBPS.csv. |
| Supp. classification (field CLSBPSPIT) |
|
Enter the pivot code describing the file lines of the Classification Suppliersto export: MMSCLSBPS.csv. |
| Supplier product (field ITMBPSPIT) |
|
Enter the pivot code describing the file lines of the ProductsSuppliers to export: MMSITMBPS.csv. |
| Projects (field PJTPIT) |
|
Enter the pivot code describing the file lines of the Projectsto export: MMSPJT.csv. |
| Units of measure (field STUPIT) |
|
Enter the pivot code describing the file lines of the Customersto export: MMSBPS.csv. |
| UOM conversion (field TCOPIT) |
|
Enter the pivot code describing the file lines of the Units conversion file to export: MMSTCO.csv. |
| Users (field USRPIT) |
|
Enter the pivot code describing the lines of the Users file to export: MMSUSR.csv. |
| Status of requests (field STAPSHPIT) |
|
Enter the pivot code describing the file lines of the Requests progress to export: MMSSTAPSH.csv. |
| Table code (field CODFIC) |
|
Code of the table to which belongs the heading for which a default value has been defined. |
| Field code (field CODZONE) |
|
Code of the heading for which a default value has been defined. |
| Description (field COM) |
|
Commission rate of the Sales rep entered in the first invoice row. |
| Default value (field VALDEF) |
|
It is possible to specify here an expression which will be suggested by default for the field. A selection can be suggested depending on the field code chosen. |
Principles of the function
The processing by the interface is carried out using .csv files.
General information on the files
- Format: .csv
- Type: UTF8 (can be modified by entry point, see below)
- The fields have a variable length and are separated by ";" (this can be modified by entry point, see below)
- For numbers, the decimal mark is the point.
- For dates, the format is "YYYYMMDDHHmm" or "YYYYMMDD"
- Durations are expressed in hours
- Booleans can take either the value 0 (false) or 1 (true)
- Files have headers.
The description of the lines of each file is given by a Pivot which specifies the order of the fields, their size and describes how they are loaded (directly via table fields or via functions).
The file names, their description and the pivots used by default are indicated below.
Export flow: X3 --- AXEL-GMAO
|
Expected files |
|
Pivots |
|
Products / Spare parts |
MMSITM |
|
|
Cost centers / Analytical dimensions |
MMSCCE |
|
|
Storage sites |
MMSFCY |
|
|
Product stock / site |
MMSITV |
|
|
Stock journal |
MMSSTJ |
|
|
Suppliers |
MMSBPS |
|
|
Supplier contacts |
MMSCNTBPS |
|
|
Supplier classifications |
MMSCLSBPS |
|
|
Product suppliers |
MMSITMBPS |
|
|
Purchase request progress |
MMSSTAPSH |
|
|
Projects |
MMSPJT |
|
|
Units |
MMSTUN |
|
|
Unit conversions |
MMSTCO |
|
|
Users |
MMSUSR |
Import flows: AXEL-GMAO --- X3
Expected files |
|
Pivots |
|
Stock issue movements |
MMSMVT |
|
|
Purchase requests |
MMSPSH |
Entry points
The PIVOTSFILE entry point of the CONNECTFCT processing can be used to modify the coding type of the files and the column separator.
Description of the files exported from Sage X3
- Products / Spare parts: MMSITM.csv
- Cost centers / Analytical dimensions: MMSCCE.csv
- Storage sites: MMSFCY.csv
- Product stock / site MMSITV.csv
- Stock journal: MMSSTJ.csv
- Suppliers: MMSBPS.csv
- Supplier contacts: MMSCNTBPS.csv
- Supplier classifications: MMSCLSBPS.csv
- Supplier products: MMSITMBPS.csv
- Purchase request progress: MMSSTAPSH.csv
- Projects: MMSPJT.csv
- Units: MMSTUN.csv
- Unit conversions: MMSTCO.csv
- Users MMSUSR.csv
Products / Spare parts: MMSITM.csv
Pivot: MMSITM
|
File |
No. |
Title |
Type |
Optional |
Pivot |
Code |
Code |
Description
|
Field |
|
|
1 |
Product |
A |
No |
|
ITMMASTER |
ITMREF |
Product |
No |
|
|
2 |
Product title |
A |
No |
|
ITMMASTER |
ITMDES1 |
Description 1 |
No |
|
|
3 |
Entry unit |
A |
No |
|
ITMMASTER |
PUU |
Purchase unit |
No |
|
|
4 |
Issue unit |
A |
No |
|
ITMMASTER |
STU |
Stock unit |
|
|
|
5 |
Conversion coefficient (1) |
N |
No |
|
ITMMASTER |
PUUSTUCOE |
PUR - STK coef |
No |
|
|
6 |
Category |
A |
No |
|
ITMMASTER |
TCLCOD |
Category |
No |
|
|
7 |
Average cost (2) |
N |
No |
|
ITMMASTER |
WPMP |
|
No |
|
|
8 |
DPA (3) |
N |
No |
|
ITMMASTER |
WDPA |
|
No |
|
|
9 |
UPC code |
A |
Yes |
|
ITMMASTER |
EANCOD |
UPC code |
No |
|
|
10 |
Packing unit 1 |
A |
Yes |
|
ITMMASTER |
WPCU0 |
|
No |
|
|
11 |
Conversion coefficient (1) |
N |
Yes |
|
ITMMASTER |
WPCU0STUCOE |
|
No |
|
|
12 |
Packing unit 2 |
A |
Yes |
|
ITMMASTER |
WPCU1 |
|
No |
|
|
13 |
Conversion coefficient (1) |
N |
Yes |
|
ITMMASTER |
WPCU1STUCOE |
|
No |
|
|
14 |
Packing unit 3 |
A |
Yes |
|
ITMMASTER |
WPCU2 |
|
No |
|
|
15 |
Conversion coefficient (1) |
N |
Yes |
|
ITMMASTER |
WPCU2STUCOE |
|
No |
|
|
16 |
Packing unit 4 |
A |
Yes |
|
ITMMASTER |
WPCU3 |
|
No |
|
|
17 |
Conversion coefficient (1) |
N |
Yes |
|
ITMMASTER |
WPCU3STUCOE |
|
No |
(1) Conversion coefficient: if the value = 5, 1 unit will correspond to 5 stock units.
(2) Average cost: Unit price used if global price for all the sites: this information is not available in Sage X3, so the value 0 is exported.
(3) DPA: Last unit price used if globally price for all the sites: this information is not available in Sage X3, so the value 0 is used instead?
Notes:
- Only the products of the "Maintenance" category are exported.
Cost centers / Analytical dimensions: MMSCCE.csv
Pivot: MMSCCE
|
File |
No. |
Description |
Type |
Optional |
Pivot |
Table code |
Field code |
Description |
Field not managed |
|
|
1 |
Posting code (1) |
A |
No |
|
CACCE |
CCE |
Dimension |
No |
|
|
2 |
Title |
A |
Yes |
|
CACCE |
DES |
Title |
No |
|
|
3 |
Site (1) |
A |
No |
|
FACILITY |
FCY |
Site |
No |
|
|
4 |
Validity start date (2) |
A |
Yes |
|
CACCE |
VLYSTR |
Validity start date |
No |
|
|
5 |
Validity end date (2) |
A |
Yes |
|
CACCE |
VLYEND |
Validity end date |
No |
(1) Each dimension is authorized for a site, a group of sites or for all the sites.
The file contains a dimension code for all the sites on which it is authorized.
(2) A dimension can be valid from a date onwards, up to a date, or during a given period.
It is possible to either have a validity start date, a validity end date, or both dates (thus corresponding to a range).
Notes:
- The values of the analytical dimensions are recovered in Sage X3 from the dimension type indicated in the setup.
Storage sites: MMSFCY.csv
Pivot: MMSFCY
|
File |
No. |
Title |
Type |
Optional |
Pivot |
Table code |
Field code |
Description |
Field not managed |
|
|
1 |
Site code |
A |
No |
|
FACILITY |
FCY |
Site |
No |
|
|
2 |
Description |
A |
Yes |
|
FACILITY |
FCYNAM |
Name |
No |
Notes:
- Only the warehouse sites are exported.
Product stock / site MMSITV.csv
Pivot: MMSITV
|
File |
No. |
Title |
Type |
Optional |
Pivot |
Table code |
Field code |
Description |
Field not managed |
|
|
1 |
Product code |
A |
No |
|
ITMMVT |
ITMREF |
Product |
No |
|
|
2 |
Site code |
A |
No |
|
ITMMVT |
STOFCY |
Storage site |
No |
|
|
3 |
Average cost |
N |
No |
|
ITMMVT |
AVC |
Average cost |
No |
|
|
4 |
Quantity in stock (1) |
N |
No |
|
ITMMVT |
PHYSTO |
Internal stock 'A' |
No |
|
|
5 |
Quantity in order |
N |
No |
|
ITMMVT |
ORDSTO |
On reorder |
No |
|
|
6 |
Quantity reserved (2) |
N |
No |
|
ITMMVT |
WRESERVE |
|
No |
(1) Quantity in stock: only the stock with an "A" status It is the quantity "internal stock + stock" which is taken into account.
(2) Quantity reserved: this data is specific to AXEL, so the 0 value is exported.
Notes:
- Only the information concerning the "Maintenance" category of products and the storage sites are exported.
- The quantities indicated take into account all the movements carried out in Sage X3 up to the extraction.
- This file is used to load the STOCK table in AXEL.
Stock journal: MMSSTJ.csv
Pivot: MMSSTJ
|
File |
No. |
Title |
Type |
Optional |
Pivot |
Table code |
Field code |
Description |
Field not managed |
|
|
1 |
Movement date |
D |
No |
|
STOJOU |
IPTDAT |
Allocation date |
No |
|
|
2 |
Product code |
A |
No |
|
STOJOU |
ITMREF |
Product |
No |
|
|
3 |
Site code |
A |
No |
|
STOJOU |
STOFCY |
Storage site |
No |
|
|
4 |
Stock unit |
A |
No |
|
STOJOU |
STU |
Stock unit |
No |
|
|
5 |
Quantity (1) |
N |
No |
|
STOJOU |
QTYSTU |
STK quantity |
No |
|
|
6 |
Global price |
N |
No |
|
STOJOU |
PRIORD |
Order price |
No |
|
|
7 |
Lot (2) |
A |
Yes |
|
STOJOU |
LOT |
Lot |
No |
|
|
8 |
Expiry date |
D |
Yes |
|
STOJOU |
SHLDAT |
Expiry date |
No |
|
|
9 |
Movement type (3) |
A |
No |
|
STOJOU |
TRSTYP |
Transaction type |
No |
|
|
10 |
Unique identifier of the movement |
A (70) |
No |
|
STOJOU |
WID |
|
No |
|
|
11 |
Movement indicator from the MMS (4) |
B |
No |
|
STOJOU |
WMMS |
|
No |
(1) Quantity: this can be positive or negative depending on the movement type.
(2) Lot: lot management is optional. The lot represents a group of entries. Several issues can be carried out on a same lot.
(3) Movement type: the possible values are defined in the local menu 704: Stock Transaction Type.
(4) The movement indicator from the MMS takes the value 1 if it comes from movement imports performed via this connector (MMSMVT.csv file: Stock issue movements); otherwise, it takes the value 0. When launching the interface processing, it is possible to specify whether the movements from the MMS and previously exported must be extracted.
Notes:
- This file contains the detail of the movements (entry, issue, change, etc.) carried out on the stock for the "A" status between the 2 given dates.
- The movements extracted in this file have already been taken into account in the quantities in stock given in the "Product stock / site" file: MMSITV.csv.
- In Sage X3, it is not possible to differentiate the movements already exported via this connector. All the movements in the requested period are therefore exported with a unique identifier, so that AXEL can check whether the movement has already been imported.
- This file is used to load the LOT table in AXEL.
Suppliers: MMSBPS.csv
Pivot: MMSBPS
|
File |
No. |
Title |
Type |
Optional |
Pivot |
Table code |
Field code |
Description |
Field not managed |
|
|
1 |
Supplier code |
A |
No |
|
BPSUPPLIER |
BPSNUM |
Supplier |
No |
|
|
2 |
Company name |
A |
No |
|
BPSUPPLIER |
BPSNAM |
Company name |
No |
|
|
3 |
Classification (1) |
A |
Yes |
|
BPSUPPLIER |
WCLASS |
|
No |
|
|
4 |
Address |
A |
Yes |
|
BPSUPPLIER |
BPAADDLIG |
Address line |
No |
|
|
5 |
Postal code |
A |
Yes |
|
BPSUPPLIER |
POSCOD |
Postal code |
No |
|
|
6 |
City |
A |
Yes |
|
BPSUPPLIER |
CTY |
City |
No |
|
|
7 |
Country |
A |
Yes |
|
BPSUPPLIER |
CRY |
Country |
No |
|
|
8 |
Fax |
A |
Yes |
|
BPSUPPLIER |
FAX |
Fax |
No |
|
|
9 |
Telephone |
A |
Yes |
|
BPSUPPLIER |
TEL |
Telephone |
No |
|
|
10 |
Lead time rank |
N |
Yes |
|
BPSUPPLIER |
LTIMRK |
Lead time rank |
No |
|
|
11 |
Price rank |
N |
Yes |
|
BPSUPPLIER |
PRIMRK |
Price rank |
No |
|
|
12 |
Quality rank |
N |
Yes |
|
BPSUPPLIER |
QLYMRK |
Quality rank |
No |
|
|
13 |
Lead-time weight |
N |
Yes |
|
BPSUPPLIER |
LTIMRKCOE |
Lead-time coefficient |
No |
|
|
14 |
Price weight |
N |
Yes |
|
BPSUPPLIER |
PRIMRKCOE |
Price factor |
No |
|
|
15 |
Quality weight |
N |
Yes |
|
BPSUPPLIER |
QLYMRKCOE |
Quality factor |
No |
this concept does not exist in Sage X3. It is then a field that can be loaded freely by setting up a pivot. If loaded, the values will be used to produce the "Supplier classifications" file.
Supplier contacts: MMSCNTBPS.csv
Pivot: MMSCNTBPS
|
File |
No. |
Title |
Type |
Optional |
Pivot |
Table code |
Field code |
Title |
Field not managed |
|
|
1 |
Supplier code |
A |
No |
|
BPSUPPLIER |
BPSNUM |
Supplier |
No |
|
|
2 |
Contact code |
A |
No |
|
CONTACT |
CCNCRM |
Code |
No |
|
|
3 |
Contact name (1) |
A |
Yes |
|
CONTACTCRM |
WNOM |
|
No |
|
|
4 |
Telephone |
A |
Yes |
|
CONTACT |
TEL |
Telephone |
No |
|
|
5 |
Fax |
A |
Yes |
|
CONTACT |
FAX |
Fax |
No |
|
|
6 |
|
A |
Yes |
|
CONTACT |
WEB |
|
No |
(1) Contact name: the name is composed of a family name + first name.
Supplier classifications: MMSCLSBPS.csv
Pivot: MMSCLSBPS
|
File |
No. |
Title |
Type |
Optional |
Pivot |
Table code |
Field code |
Title |
Field not managed |
|
|
1 |
Classification code (1) |
A |
No |
|
BPSUPPLIER |
WCOD |
|
No |
|
|
2 |
Classification title (2) |
A |
Yes |
|
BPSUPPLIER |
WDES |
|
No |
(1) Classification code: it is the code obtained from the values found for the WCLASS variable of the suppliers file.
(2) Classification title: no title is defined. It can be defined by setting up a pivot.
Notes:
- The codes are entered from the values obtained for the WCLASS variable of the suppliers file.
Supplier products: MMSITMBPS.csv
Pivot: MMSITMBPS
|
File |
No. |
Title |
Type |
Optional |
Pivot |
Table code |
Field code |
Title |
Field not managed |
|
|
1 |
Supplier code |
A |
No |
|
ITMBPS |
BPSNUM |
Supplier |
No |
|
|
2 |
Product code |
A |
No |
|
ITMBPS |
ITMREF |
Product |
No |
|
|
3 |
Purchase minimum quantity |
N |
Yes |
|
PPRICLIST |
MINQTY |
Minimum quantity |
No |
|
|
4 |
Delivery lead-time (1) |
N |
Yes |
|
PPRICLIST |
LTI |
Lead-time |
No |
|
|
5 |
Purchase unit |
A |
Yes |
|
PPRICLIST |
UOM |
Unit |
No |
|
|
6 |
Unit price |
N |
Yes |
|
PPRICLIST |
PRI |
Prices |
No |
|
|
7 |
Supplier product reference |
A |
Yes |
|
ITMBPS |
ITMREFBPS |
Supplier product |
No |
|
|
8 |
Priority |
N |
Yes |
|
ITMBPS |
PIO |
Priority |
No |
Purchase request progress: MMSSTAPSH.csv
Pivot: MMSSTAPSH
File | No. | Title | Type | Optional | Pivot | Table code | Field code | Title | Field not managed |
| 1 | Line identifier | A | No |
| PREQUISD | PSDNUMMMS | Maintenance line id | No |
| 2 | Line status (1) | A | No |
| PREQUIS | WSTA |
| No |
| 3 | Received quantity (2) | N | Yes |
| PREQUIS | WQTYR |
| No |
(1) Line status: the possible values are: 0 - On hold / 1 - Refused / 2 - Paid / 3 - Approved /(2) 4 - Ordered.
(2) Received quantity: if there ahas been receipts, the value will be larger than zero.
Notes:
- This file contains the progress status of the MMS requests (which has the MMS identifier: PSHNUMMS No maintenance)
Projects: MMSPJT.csv
Pivot: MMSPJT
File | No. | Title | Type | Optional | Pivot | Table code | Field code | Title | Field not managed |
| 1 | Project code | A | No |
| OPPOR | OPPNUM | Project chrono | No |
Units: MMSTUN.csv
Pivot: MMSTUN
File | No. | Title | Type | Optional | Pivot | Table code | Field code | Title | Field not managed |
| 1 | Unit code | A | No |
| TABUNIT | UOM | Unit | No |
| 2 | Description | A | Yes |
| TABUNIT | DES | Title | No |
Unit conversions: MMSTCO.csv
Pivot: MMSTCO
File | No. | Title | Type | Optional | Pivot | Table code | Field code | Title | Field not managed |
| 1 | Unit 1 | A | No |
| TABCOEFF | UOM1 | Unit 1 | No |
| 2 | Unit 2 | A | No |
| TABCOEFF | UOM2 | Unit 2 | No |
| 3 | Coefficient | N | No |
| TABCOEFF | COEUOM | Coefficient | No |
Users MMSUSR.csv
Pivot: MMSUSR
File | No. | Title | Type | Optional | Pivot | Table code | Field code | Description | Field not managed |
| 1 | User code | A | No |
| AUTILIS | USR | Code | No |
| 2 | Username | A | No |
| AUTILIS | WNOM |
| No |
| 3 | User login | A | No |
| AUTILIS | LOGIN | Login | No |
Notes:
- All users from the Sage X3 folder are exported.
Description of the files imported from Sage X3
Stock issue movements: MMSMVT.csv
Pivot: MMSMVT
|
File |
No. |
Title |
Type |
Optional |
Pivot |
Table code |
Field code |
Description |
Field not managed |
|
|
1 |
Product code |
A |
No |
|
SMVTD |
ITMREF |
Product |
No |
|
|
2 |
Site code |
A |
No |
|
SMVTH |
STOFCY |
Storage site |
No |
|
|
3 |
Quantity entered (1) (2) |
N |
No |
|
SMVTD |
WQTYRCP |
|
Yes |
|
|
4 |
Quantity issued (1) (2) |
N |
No |
|
SMVTD |
WQTYISS |
|
Yes |
|
|
5 |
Unit (3) |
A |
No |
|
SMVTD |
PCU |
Unit |
No |
|
|
6 |
Unit price |
A |
No |
|
SMVTD |
WPRIUNT |
|
Yes |
|
|
7 |
Analytical dimension (4) |
A |
Yes |
|
SMVTD |
WCCE |
|
Yes |
|
|
8 |
Movement date |
D |
No |
|
SMVTH |
IPTDAT |
Allocation date |
No |
|
|
9 |
Job ticket code |
A |
Yes |
|
SMVTH |
WBON |
|
Yes |
|
|
10 |
Project code |
A |
Yes |
|
SMVTH |
PJT |
Project |
No |
(1) The quantity passed must be null, set to 0 or positive but cannot have a sign.
(2) It is a stock entry or a stock issue depending on whether the quantity is larger than zero or not. On each line, only one of the 2 quantities can be larger than zero.
(3) Unit code: the unit passed must correspond to a valid unit for the product, that is, one of the units passed in the Products file: purchase unit, storage unit, or one of the 4 packing units.
(4) Dimension: the goal is to potentially specify an analytical dimension for a given dimension type. The field can be left empty or filled with a dimension of the dimension type set up in the "Dimension type" field next to the MMSMVT pivot in the MMS setup.
Notes:
- These are movements performed in AXEL.
- The imported movements are only carried out on the "A" status stock.
Purchase requests: MMSPSH.csv
Pivot: MMSPSH
|
File |
No. |
Title |
Type |
Optional |
Pivot |
Table code |
Field code |
Description |
Field not managed |
|
|
1 |
Maintenance identifier |
A |
No |
|
PREQUIS |
PSHNUMMMS |
No maintenance |
No |
|
|
2 |
Line identifier |
A |
No |
|
PREQUISD |
PSDNUMMMS |
Maintenance line id |
No |
|
|
3 |
Product code |
A |
No |
|
PREQUISD |
ITMREF |
Product |
No |
|
|
4 |
Product title |
A |
No |
|
PREQUISD |
ITMDES |
Description |
No |
|
|
5 |
Quantity |
N |
No |
|
PREQUISD |
QTYPUU |
PUR Quantity |
No |
|
|
6 |
Unit code (1) |
A |
No |
|
PREQUISD |
PUU |
Purchase unit |
No |
|
|
7 |
Project code |
A |
Yes |
|
PREQUISD |
PJT |
Project |
No |
|
|
8 |
Analytical dimension (2) |
A |
Yes |
|
PREQUISD |
WSEC |
|
Yes |
|
|
9 |
Requester |
A |
No |
|
PREQUIS |
REQUSR |
Requester |
No |
|
|
10 |
Storage site |
A |
No |
|
PREQUIS |
PSHFCY |
Request site |
No |
|
|
11 |
Provisional delivery date (3) |
D |
Yes |
|
PREQUISD |
EXTRCPDAT |
Requested date |
No |
|
|
12 |
Supplier code (4) |
A |
Yes |
|
PREQUISD |
BPSNUM |
Supplier |
No |
|
|
13 |
Date of the request |
D |
No |
|
PREQUIS |
PRQDAT |
Request date |
No |
|
|
14 |
URL coming from AXEL (5) |
A (250) |
Yes |
|
PREQUIS |
MMSURL |
URL maintenance |
No |
(1) Unit code: the unit passed must correspond to a valid unit for the product, that is, one of the units passed in the Products file: purchase unit, storage unit, or one of the 4 packing units.
(2) Supplier code: it is not possible to directly assign the fields of a table; therefore, the WSEC variable is used.
(3) Provisional delivery date: if this date is earlier than the current date, a non blocking warning message is displayed.
(4) Supplier code: if the supplier does not correspond to one of the suppliers known for the product, a non blocking warning message is displayed.
(5) URL: the file imported in the X3 can provide an URL for each purchase request, leading to a web page that suggests suggestig. These URLs will be used to open an Internet browser session of the client workstation from the Purchase requests management X3 screens in order to access the documents.
Notes:
- These purchase requests are carried out in AXEL.