Annex : the GIMP variables
Standard import/export template
The import processings that use the GIMP(*) variable are:
IMPITM: Products
The variables are used when Importing/Exporting texts of product management. Each text depends on the imported table. Thus, a single variable number can be found several times in a template but for the management of different texts.
Variable | Description | Import | Export |
*71 to *78 | ITMMASTER (products): Lines 1 to 8 of the purchase text | Yes | Yes |
*81 to *88 | ITMMASTER (products): Lines 1 to 8 of the manufacturing text | Yes | Yes |
*71 to *78 | ITMSALES (products-sales): Lines 1 to 8 of the sales text | Yes | Yes |
*81 to *88 | ITMSALES (products-sales): Lines 1 to 8 of the preparation text | Yes | Yes |
*71 to *78 | ITMBPS (products-suppliers): Lines 1 to 8 of the text | Yes | Yes |
*71 to *78 | ITMBPC (products-customers): Lines 1 to 8 of the sales text | Yes | Yes |
*81 to *88 | ITMBPC (products-customers): Lines 1 to 8 of the preparation text | Yes | Yes |
IMPPPL: Purchase prices
In the PPRICLIST record, criteria are groupes based on one piece of data PLI but they must be defined individually in the template.
Variable | Description | Import | Export |
*1 | Criterion 1 of the price list | Yes | Yes |
*2 | Criterion 2 of the price list | Yes | Yes |
*3 | Criterion 3 of the price list | Yes | Yes |
*4 | Criterion 4 of the price list | Yes | Yes |
*5 | Criterion 5 of the price list | Yes | Yes |
IMPPTH: Purchase receipts
Variables used when importing/exporting texts.
Variable | Description | Import | Export |
*71 to *78 | Lines 1 to 8 of the header text | Yes | Yes |
*81 to 88 | Lines 1 to 8 of the footer text | Yes | Yes |
*91 to *98 | Lines 1 to 8 of the line text | Yes | Yes |
IMPPTHS: Purchase receipts (specific import)
Variables used when importing/exporting texts.
Variable | Description | Import | Export |
*60 | No of sales delivery (only for inter-site receipts) | Yes |
|
*61 | No of sales delivery line (only for inter-site receipts) | Yes |
|
*65 | Complete flag | Yes |
|
*71 to *78 | Lines 1 to 8 of the header text | Yes |
|
*81 to 88 | Lines 1 to 8 of the footer text | Yes |
|
*91 to *98 | Lines 1 to 8 of the line text | Yes |
|
IMPROT: Standard operations
Variables used when importing/exporting texts.
Variable | Description | Import | Export |
*71 to *78 | Lines 1 to 8 of the operation text | Yes | Yes |
IMPROU: Routings
Variables used when importing/exporting texts.
Variable | Description | Import | Export |
*71 to *78 | Lines 1 to 8 of the routing header text | Yes | Yes |
*91 to *98 | Lines 1 to 8 of the operation text | Yes | Yes |
IMPSDH: Sales delivery
The variables are used in Import/Export of the delivery note texts. The preparation note texts are not managed. With respect to the EDI exchange management, the variables are defined to trigger the read of the [F] classes that are not directly accessible by a link; these variables will only be used in export.
Variable | Description | Import | Export |
*3 | Company: loading of the classes [F:FCY] for the sales site, [F: CPY] company and [F:BPA] company address |
| Yes |
*4 | Shipment site: loading of the classes [F:FCY] shipment site and [F:BPA] delivery address |
| Yes |
*5 | Bill-to customer: loading of the classes [F:BPR] business partners, [F:BPC] bill-to customer and [F:BPA] bill-to customer address |
| Yes |
*6 | Sold-to customer: loading of the classes [F:BPR] business partners, [F:BPC] sold-to customer and [F:BPA] sold-to customer address |
| Yes |
*7 | Paying customer: loading of the classes [F:BPR] business partners, [F:BPC] paying customer and [F:BPA] paying customer address |
| Yes |
*8 | Ship-to customer: loading of the classes [F:BPD] ship-to customer and [F:BPA] ship-to address customer |
| Yes |
*9 | Carrier: loading of the classes [F:BPT] carried and [F:BPA] carrier address |
| Yes |
*15 | Order: loading of the class [F:SOH] If the export of the header (EXPFIC="SDH"), loading of the order in the first line of the shipment. If the export of the line (EXPFIC="SDD"), loading of the order for the shipment line. |
| Yes |
*21 | Coefficient multiplier for the header weight In EDI the weight must be in KG, if the weight unit is not in KG, it is necessary to provide a coefficient (from the units conversion table) which will be used to convert to KG. Beware of the usage of the storage variable GIMP(21), which gives an alpha result |
| Yes |
*52 | Product: Product: loading of the classes [F:ITM] product, [F:ITS] product-sales and [F:ITU] product-customer |
| Yes |
*53 | Multiplier coefficient for the line weight (see description *21). |
| Yes |
*71 to *78 | Lines 1 to 8 for the delivery note header text | Yes | Yes |
*81 to 88 | Lines 1 to 8 for the delivery note footer text | Yes | Yes |
*91 to *98 | Lines 1 to 8 for the delivery note line text | Yes | Yes |
IMPSDHS: Sales shipments (specific import)
The variables are used in Import of the delivery note texts. The preparation note texts are not managed.
Variable | Description | Import | Export |
*71 to *78 | Lines 1 to 8 for the delivery note header text | Yes |
|
*81 to 88 | Lines 1 to 8 for the delivery note footer text | Yes |
|
*91 to *98 | Lines 1 to 8 for the delivery note line text | Yes |
|
IMPSIH: Sales invoices
Variables used when importing/exporting texts. With respect to the EDI exchange management, the variables are defined to trigger the read of the [F] classes that are not directly accessible by a link; these variables will only be used in export.
Variable | Description | Import | Export |
*3 | Company: loading of the classes [F: CPY] company and [F:BPA] company address |
| Yes |
*4 | Sales site: loading of the classes [F:FCY] sales site and [F:BPA] sales site address |
| Yes |
*5 | Bill-to customer: loading of the classes [F:BPR] business partners, [F:BPC] bill-to customer and [F:BPA] bill-to customer address |
| Yes |
*6 | Sold-to customer: loading of the classes [F:BPR] business partners, [F:BPC] sold-to customer and [F:BPA] sold-to customer address |
| Yes |
*7 | Paying customer: loading of the classes [F:BPR] business partners, [F:BPC] paying customer and [F:BPA] paying customer address |
| Yes |
*8 | Ship-to customer: loading of the classes [F:BPD] ship-to customer and [F:BPA] ship-to address customer |
| Yes |
*9 | Carrier: loading of the classes [F:SDH] shipment (from the shipment number of the first invoice line), [F:BPT] carrier and [F:BPA] carrier address |
| Yes |
*10 | Document type: test in the action EXPORT to recover GIMP(10)="04" credit memo or GIMP(10)="05" invoice |
| Yes |
*15 | Order: loading of the class [F:SOH] order. If export of the header (EXPFIC="SIH" or "SIV") loading of the order for the first line of the invoice. If export of a line (EXPFIC="SID") loading of the order for the line in the invoice. |
| Yes |
*16 | Shipment: loading of the class [F:SDH] shipment. If export of the header (EXPFIC="SIH" or "SIV") loading of the shipment for the first line of the invoice. If export of a line (EXPFIC="SID") loading of the shipment for the line in the invoice. |
| Yes |
*31 | Tax 1: loading of the [F:TVT] taxes table. The tax rate [F:TVT]VATRAT is loaded from what is in [F:SIV]VATRAT(x) or [F:SIV]DTAVATRAT. The rate that must be used is stored in SINVOICEV in order to have the actual rate used (the search in the rates table can give a rate modified since the invoice calculation). |
| Yes |
*32 | Tax 2: loading of the [F:TVT] taxes table (process identical to Tax 1) |
| Yes |
*33 | Tax 3: loading of the [F:TVT] taxes table (process identical to Tax 1) |
| Yes |
*34 | Tax 4: loading of the [F:TVT] taxes table (process identical to Tax 1) |
| Yes |
*35 | Tax 5: loading of the [F:TVT] taxes table (process identical to Tax 1) |
| Yes |
*41 | Open item 1: loading of [F:DUD] open item table GACCDUDATE with the first open item in the invoice. |
| Yes |
*42 | Open item 2: loading of [F:DUD] open item table GACCDUDATE with the second open item in the invoice. |
| Yes |
*43 | Open item 3: loading of [F:DUD] open item table GACCDUDATE with the third open item in the invoice. |
| Yes |
*44 | Open item 4: loading of [F:DUD] open item table GACCDUDATE with the fourth open item in the invoice. |
| Yes |
*45 | Open item 5: loading of [F:DUD] open item table GACCDUDATE with the fifth open item in the invoice. |
| Yes |
*52 | Product: Product: loading of the classes [F:ITM] product, [F:ITS] product-sales and [F:ITU] product-customer |
| Yes |
*61 to *70 | Invoicing element 1: corresponds to the rank (from 1 to 10) in the invoicing elements grid (and not to the number of the element). For example if the payment is for line 1 in the grid, it is necessary to use variable *61; if it is in 5, it is necessary to use the variable *65. Warning: the invoicing elements cannot be grouped nor grouped in the invoice valuation. This action recovers the global variable to be included in the template parameterization - [V]DTAAMTbase(% or amount) - [V]DTANOTEx tax amount - [V]DTAVATRAT tax rate - [V]DTAVATAMT tax amount |
| Yes |
*71 to *78 | Lines 1 to 8 for the invoice header text | Yes | Yes |
*81 to 88 | Lines 1 to 8 for the invoice footer text | Yes | Yes |
*91 to *98 | Lines 1 to 8 for the invoice line text | Yes | Yes |
IMPSOH: Sales orders
Variables used when importing/exporting texts. With respect to the EDI exchange management, the variables are defined to trigger the read of the [F] classes that are not directly accessible by a link; these variables will only be used in export.
In import, the variables that are used to manage the EDI identifiers for the customers and the carrier. In the EDI files, there is an order identifier and a shipment identifier (with the same structure as the order identifier). On the other hand in X3 the shipment address is an address code linked to the sold-to customer code. Thus in EDI it is often the case that there is the same identifier for the order as the shipment; outside of X3 2 items of information must be recovered. The software package EDI_Appli uses a correspondence table and for a given EDI identifier it delivers in the file to be imported, a single data grouping the customer code and the address code separated by a ~ (tilde).
093195450607700237;AIRFRANCE~RSY (093195450607700237 = EDI identifier / AIRFRANCE = X3 customer code / RSY = shipment address code). Thus the data AIRFRANCE~RSY is delivered in the pivot file; only the value before the~ (tilde) is taken into account as the customer code.
Variable | Description | Import | Export |
*3 | Company: loading of the classes [F: CPY] company and [F:BPA] company address |
| Yes |
*4 | Sales site: loading of the classes [F:FCY] sales site and [F:BPA] sales site address |
| Yes |
*5 | Bill-to customer: loading of the classes [F:BPR] business partners, [F:BPC] bill-to customer and [F:BPA] bill-to customer address. |
| Yes |
*6 | Sold to customer (EDI specificity): The value before the ~ (tilde) recovers the customer code. | Yes |
|
*6 | Sold-to customer: loading of the classes [F:BPR] business partners, [F:BPC] sold-to customer and [F:BPA] sold-to customer address |
| Yes |
*7 | Paying customer (EDI specificity): The value before the ~ (tilde) recovers the customer code. | Yes |
|
*7 | Paying customer: loading of the classes [F:BPR] business partners, [F:BPC] paying customer and [F:BPA] paying customer address |
| Yes |
*8 | Ship-to customer (EDI specificity): The value after the ~ (tilde) loads the address code. | Yes |
|
*8 | Ship-to customer: loading of the classes [F:BPD] ship-to customer and [F:BPA] ship-to address customer |
| Yes |
*9 | Carrier (EDI specificity): The value before the ~ (tilde) loads the carrier code. | Yes |
|
*9 | Carrier: loading of the classes [F:SDH] shipment (from the shipment number of the first invoice line), [F:BPT] carrier and [F:BPA] carrier address |
| Yes |
*15 | Order: loading of the classes [F:SOP] and [F:SOQ] of the first line in the order. This action is necessary if the data stored in the lines must appear in the export of the header record. |
| Yes |
*52 | Product: Product: loading of the classes [F:ITM] product, [F:ITS] product-sales and [F:ITU] product-customer |
| Yes |
*71 to *78 | Lines 1 to 8 for the order header text | Yes | Yes |
*81 to 88 | Lines 1 to 8 for the order footer text | Yes | Yes |
*91 to *98 | Lines 1 to 8 of the line text | Yes | Yes |
IMPSOQ: Sales shipment requests
The variables are used in the Import of the texts.
In import, the variables that are used to manage the EDI identifiers for the customers and the carrier. In the EDI files, there is an order identifier and a shipment identifier (with the same structure as the order identifier). On the other hand in X3 the shipment address is an address code linked to the sold-to customer code. Thus in EDI it is often the case that there is the same identifier for the order as the shipment; outside of X3 2 items of information must be recovered. The software package EDI_Appli uses a correspondence table and for a given EDI identifier it delivers in the file to be imported, a single data grouping the customer code and the address code separated by a ~ (tilde).
093195450607700237;AIRFRANCE~RSY (093195450607700237 = EDI identifier / AIRFRANCE = X3 customer code / RSY = shipment address code). Thus the data AIRFRANCE~RSY is delivered in the pivot file; only the value before the~ (tilde) is taken into account as the customer code.
Variable | Description | Import | Export |
*6 | Sold to customer (EDI specificity): The value before the ~ (tilde) recovers the customer code. | Yes |
|
*8 | Ship-to customer (EDI specificity): The value after the ~ (tilde) loads the address code. | Yes |
|
*71 to *78 | Lines 1 to 8 of the header text | Yes |
|
*81 to 88 | Lines 1 to 8 of the footer text | Yes |
|
*91 to *98 | Lines 1 to 8 of the line text | Yes |
|
IMPSPL: Sales price lists
In the PPRICLIST record, criteria are groupes based on one piece of data PLI but they must be defined individually in the template.
Variable | Description | Import | Export |
*1 | Criterion 1 of the price list | Yes | Yes |
*2 | Criterion 2 of the price list | Yes | Yes |
*3 | Criterion 3 of the price list | Yes | Yes |
*4 | Criterion 4 of the price list | Yes | Yes |
*5 | Criterion 5 of the price list | Yes | Yes |