SCM AZAP setup

This function is used to set up the interface with the product dedicated to the Supply Chain Management:  AZAP.
This setup is used to manage, through data files in the .csv format, the flows coming from and designed for AZAP.

This flows, concerning the Inventory module, are the following:

Flow X3 to AZAP :

• Products/Products
• Conversion of product units
• Product criteria
• Customer/Sites
• Site criteria/customers
• Sales history
• Orders WIPs

Flow AZAP to X3 :

• Sales forecasts

Prerequisite

Screen management

Entry screen

Principles of functioning

The processing by the interface is carried out using .csv files.

General information on the files

• Format: .csv
• Type: ASCII (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)
• The files are DOS files (end of line characters: \013\010 or \r\n).
• 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.

• Valuation: they are not managed in this interface. Any information concerning the amounts, the currencies (on the products as well as on the sales) will be transmitted in standard, via this interface.
• The exceptional events, i.e. the non-systematic phenomena that interfere with sales (example: promotions).

Export flow: X3 --- AZAP

Import flows: AZAP --- X3

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: products.csv

Pivot: SCMAITM

Notes :

• The file header is made up with the codes of the columns set up on the pivot.
• Only the products of "Sold" type (information contained in the product category) are exported.
• The setup authorizes the entry of a product selection: for the selected products, conversion information as well as criteria are exported in separate files: conversion.csv and critstr.csv.

Products / Conversions: conversion.csv

Pivot: SCMAITMTCO

Notes :

• The file header is made up with the codes of the columns set up on the pivot.
• For each product, the file contains: 
   
  - a first line with the conversion information between the sales unit and the stock unit. This line is always displayed even though the sales and stock units are the same. 
   
  - Optional lines on the conversions between the 4 packing units and the stock unit, according to the setup carried out.

Products / Criteria: critstr.csv

Pivot: SCMAITMCRI

Notes :

• The file header is made up with the titles of the columns set up on the pivot. The titles cannot have more than 15 characters.
• According to the setup carried out, it is possible, for each criterion, to have the code or the title only, or both: code and title.
• The criteria 4 to 11 can be exported or not, according to the setup carried out. When not exported, the columns are not displayed in the file.

Sites: sites.csv

Pivot: SCMAFCY

Notes :

• The file header is made up with the codes of the columns set up on the pivot.
• For AZAP, the sites are clients or warehouses. All the clients and storage sites are then exported via this file. The difference will be made in AZAP.
• The sites criteria will be exported in a separated file: critstrsite.csv

Sites / Criteria: critstrsite.csv

Pivot: SCMACRIFCY

Notes :

• The file header is made up with the titles of the columns set up on the pivot. These titles cannot have more than 15 characters. 
• For AZAP, the sites are clients or warehouses. All the clients and storage sites are then exported via this file. The difference will be made in AZAP.
• According to the setup carried out, it is possible, for each criterion, to have the code or the title only, or both: code and title.
• The criteria 2 to 10 can be exported or not, according to the setup carried out. When not exported, the columns are not displayed in the file.

Sales history: ventes.csv

Pivot: SCMAHSOH

Notes :

• The file header is made up with the codes of the columns set up on the pivot. 
• If the history comes from paid orders, the export concerns the paid order lines which quantity has been delivered or invoiced. The setup authorizes the entry of a selection of orders.
• If the history is coming from deliveries/invoices, the export concerns the actual flows:
  + validated deliveries
  + validated direct invoices with stock movement
  + validated "order" invoices with stock movement
  + validated "delivery" invoice lines with stock movement and no delivery number
  - delivery returns
  - validated direct credit memos with stock movement
  - validated credit memos on invoices with stock movement
  The setup authorizes the entry of a selection of deliveries/invoices.

Order WIPs: carnet.csv

Pivot: SCMASOH

(1) for the open orders, it is the required delivery date: DEMDLVDAT
(2) According to the aggregation level selected, the effective date or the start date of the period (week or month) is taken into account for the data grouping.
(3) the quantity must be expressed in SAU: sales unit.
(4) An unpaid order (from the order book) can already have a delivery quantity (taken into account in the history), so the quantity taken into account in the order book is the quantity remaining to be delivered.

Notes :

• The file header is made up with the codes of the columns set up on the pivot.  
• The export concerns the unpaid order lines.
• The setup authorizes the entry of a selection of orders.

Description of the files imported from Sage X3

Sales forecasts: previsions.csv

Pivot: SCMASOS

(1)  According to the level of aggregation selected in AZAP, it will be the effective date or the period end date.
(2) the quantity must be expressed in STK: stock unit.

Notes :

• The import concerns the sales forecasts carried out in AZAP.
• The expected file must have a header.  
• It is possible to setup the deletion:
  - either of former forecasts of each imported file product, before importing the new ones,
  - or of all the forecasts, before the file processing.

Error messages

The only error messages are the generic ones.

Tables used