Appendix: GIMP variables
Standard import/export templates
The import scripts that use the GIMP(*) variable are shown below.
The import/export only works properly if the texts are in plain text mode. The rich text mode is not supported.
IMPITM: Products
Variables are used for importing/exporting product management texts. Each text is linked to the imported table. The same variable number can be found several times in a template, but for the management of a different text.
|
Variable |
Post |
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 Production 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 Picking text |
Yes |
Yes |
|
*71 to *78 |
ITMBPS (Product-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 Picking text |
Yes |
Yes |
IMPPPL: PO pricing
In the PPRICLIST record, the criteria are grouped as a single piece of PLI data, but they must be defined separately in the template.
|
Variable |
Description |
Import |
Export |
|
*1 |
Criteria 1 for the price list |
Yes |
Yes |
|
*2 |
Criteria 2 for the price list |
Yes |
Yes |
|
*3 |
Criteria 3 for the price list |
Yes |
Yes |
|
*4 |
Criteria 4 for the price list |
Yes |
Yes |
|
*5 |
Criteria 5 for the price list |
Yes |
Yes |
IMPPTH: Purchase receipts
Variables are used for 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 are used for importing/exporting texts.
|
Variable |
Description |
Import |
Export |
|
*60 |
Sales delivery no. (only for inter-site receipts) |
Yes |
|
|
*61 |
Sales delivery line no. (only for inter-site receipts) |
Yes |
|
|
*65 |
Closing 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 are used for importing/exporting texts.
|
Variable |
Description |
Import |
Export |
|
*71 to *78 |
Lines 1 to 8 of the operation text |
Yes |
Yes |
IMPROU: Routings
Variables are used for 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 deliveries
The variables are used for import/exporting the packing slip texts. The picking note texts are not managed. In the framework of EDI exchanges, variables are defined in order to trigger the reading of [F] classes that cannot be accessed by a direct link. These variables can only be used for exports.
|
Variable |
Description |
Import |
Export |
|
*3 |
Company: loading [F:FCY] sales site classes, [F: CPY] company and [F:BPA] company address |
Yes |
|
|
*4 |
Delivery site: loading [F:FCY] delivery site and [F:BPA] delivery address classes |
Yes |
|
|
*5 |
Bill-to customer: loading the [F:BPR] BP, [F:BPC] bill-to customer and [F:BPA] bill-to customer address classes |
Yes |
|
|
*6 |
Sold-to customer: loading the [F:BPR] BP, [F:BPC] sold-to customer and [F:BPA] sold-to customer classes |
Yes |
|
|
*7 |
Pay-by customer: loading the [F:BPR] BP, [F:BPC] pay-by customer and [F:BPA] pay-by customer address classes |
Yes |
|
|
*8 |
Ship-to customer: loading the [F:BPD] ship-to customer and [F:BPA] ship-to customer address classes |
Yes |
|
|
*9 |
Carrier: loading the [F:BPT] carrier and [F:BPA] carrier address classes |
Yes |
|
|
*15 |
Order: loading the [F:SOH] class. If the header is exported (EXPFIC="SDH"), loading the order on the first delivery line. If the line is exported (EXPFIC="SDD"), loading the order on the delivery line. |
Yes |
|
|
*21 |
Multiplier coefficient for the header weight. In the EDI context, weights must be in KG, if the unit of weight is not KG, a coefficient should be used (from unit conversion table), to switch to KG. Be careful when using the storing variable GIMP(21), which is alphanumeric. |
Yes |
|
|
*52 |
Product: Loading the [F:ITM] product, [F:ITS] product-sales and [F:ITU] product-customer classes |
Yes |
|
|
*53 |
Multiplier coefficient of the line weight (see description *21). |
Yes |
|
|
*71 to *78 |
Lines 1 to 8 of the packing slip header text |
Yes |
Yes |
|
*81 to 88 |
Lines 1 to 8 of the packing slip footer text |
Yes |
Yes |
|
*91 to *98 |
Lines 1 to 8 of the packing slip line text |
Yes |
Yes |
IMPSDHS: Sales deliveries (specific import)
The variables are used for importing the packing slip texts. The picking note texts are not managed.
|
Variable |
Description |
Import |
Export |
|
*71 to *78 |
Lines 1 to 8 of the packing slip header text |
Yes |
|
|
*81 to 88 |
Lines 1 to 8 of the packing slip footer text |
Yes |
|
|
*91 to *98 |
Lines 1 to 8 of the packing slip line text |
Yes |
IMPSIH: Sales invoices
Variables are used for importing/exporting texts. In the framework of EDI exchanges, variables are defined in order to trigger the reading of [F] classes that cannot be accessed by a direct link; these variables can only be used for exports.
|
Variable |
Description |
Import |
Export |
|
*3 |
Company: loading classes [F: CPY] company and [F:BPA] company address |
Yes |
|
|
*4 |
Sales site: loading the [F:FCY] sales site and [F:BPA] sales site address classes |
Yes |
|
|
*5 |
Bill-to customer: loading the [F:BPR] BP, [F:BPC] bill-to customer and [F:BPA] bill-to customer address classes |
Yes |
|
|
*6 |
Sold-to customer: loading the [F:BPR] BP, [F:BPC] sold-to customer and [F:BPA] sold-to customer classes |
Yes |
|
|
*7 |
Pay-by customer: loading the [F:BPR] BP, [F:BPC] pay-by customer and [F:BPA] pay-by customer address classes |
Yes |
|
|
*8 |
Ship-to customer: loading the [F:BPD] ship-to customer and [F:BPA] ship-to customer address classes |
Yes |
|
|
*9 |
Carrier: loading the [F:SDH] delivery class (from the delivery no. of the first invoice line), [F:BPT] carrier class and [F:BPA] carrier address class |
Yes |
|
|
*10 |
Document type: test in the EXPORT action to get GIMP(10)="04" credit memo, or GIMP(10)="05" invoice |
Yes |
|
|
*15 |
Order: loading the [F:SOH] order class. If the header is exported (EXPFIC="SIH" or "SIV"), loading the order on the first invoice line. If the line is exported (EXPFIC="SID"), loading the order on the invoice line. |
Yes |
|
|
*16 |
Delivery: loading the [F:SDH] Delivery class. If the header is exported (EXPFIC="SIH" or "SIV"), loading the delivery on the first invoice line. If the line is exported (EXPFIC="SID"), loading the delivery on the invoice line. |
Yes |
|
|
*31 |
Tax 1: loading the [F:TVT] tax table. The tax rate is loaded [F:TVT]VATRAT using the data in [F:SIV]VATRAT(x) or [F:SIV]DTAVATRAT. The rate stored in SINVOICEV must be used to get the actual rate used (the search in the rates table could recover the rate modified by the invoice calculation). |
Yes |
|
|
*32 |
Tax 2: loading the [F:TVT] tax table (same as Tax 1) |
Yes |
|
|
*33 |
Tax 3: loading the [F:TVT] tax table (same as Tax 1) |
Yes |
|
|
*34 |
Tax 4: loading the [F:TVT] tax table (same as Tax 1) |
Yes |
|
|
*35 |
Tax 5: loading the [F:TVT] tax table (same as Tax 1) |
Yes |
|
|
*41 |
Open item 1: loading [F:DUD], open item table (GACCDUDATE), with the first open item of the invoice. |
Yes |
|
|
*42 |
Open item 2: loading [F:DUD], open item table (GACCDUDATE), with the second open item of the invoice. |
Yes |
|
|
*43 |
Open item 3: loading [F:DUD], open item table (GACCDUDATE) with the third open item of the invoice. |
Yes |
|
|
*44 |
Open item 4: loading [F:DUD], open item table (GACCDUDATE) with the fourth open item of the invoice. |
Yes |
|
|
*45 |
Open item 5: loading [F:DUD], open item table (GACCDUDATE) with the fifth open item of the invoice. |
Yes |
|
|
*52 |
Product: Loading the [F:ITM] product, [F:ITS] product-sales and [F:ITU] product-customer classes |
Yes |
|
|
*61 to *70 |
Invoicing element 1: corresponds to the invoicing elements table row (1 to 10), and not to the element number. For example, if the discount applies to line 1 in the table, use the *61 variable. If it applies to line 5, use the *65 variable. Caution: the invoicing elements must not be grouped in this context. They must not be grouped in invoice valuation either. This action loads the global variables to be included in the template setup - [V]DTAAMT basis(% or amount) - [V]DTANOT ex-tax amount - [V]DTAVATRAT tax rate - [V]DTAVATAMT tax amount |
Yes |
|
|
*71 to *78 |
Lines 1 to 8 of the invoice header text |
Yes |
Yes |
|
*81 to 88 |
Lines 1 to 8 of the invoice footer text |
Yes |
Yes |
|
*91 to *98 |
Lines 1 to 8 of the invoice line text |
Yes |
Yes |
IMPSOH: Sales orders
Variables are used for importing/exporting texts. In the framework of EDI exchanges, variables are defined in order to trigger the reading of [F] classes that cannot be accessed by a direct link; these variables can only be used for exports.
During an import, variables are used to manage the EDI identifiers for the customers and the carrier. EDI files contain an order (sold-to) identifier and a delivery identifier (with the same structure as the order identifier). In the application, the delivery address is an address code linked to the sold-to customer. In the EDI context, the same identifier is often used for the order and delivery. However, in the application, this represents two pieces of information. The EDI-Appli software refers to a table of correspondences and, for an EDI identifier, delivers one piece of data composed of the customer code and the address code separated by a ‘~’ character in the file to import.
093195450607700237;AIRFRANCE~RSY (093195450607700237 = EDI identifier / AIRFRANCE = X3 customer code RSY = delivery address code). The AIRFRANCE~RSY information is delivered in the pivot file; only the value before the ‘~’ character is used as the customer code.
|
Variable |
Description |
Import |
Export |
|
*3 |
Company: loading classes [F: CPY] company and [F:BPA] company address |
Yes |
|
|
*4 |
Sales site: loading the [F:FCY] sales site and [F:BPA] sales site address classes |
Yes |
|
|
*5 |
Bill-to customer: loading the [F:BPR] BP, [F:BPC] bill-to customer and [F:BPA] bill-to customer address classes |
Yes |
|
|
*6 |
Sold-to customer (EDI specificity): The value before ‘~’ is loaded as the customer code. |
Yes |
|
|
*6 |
Sold-to customer: loading the [F:BPR] BP, [F:BPC] sold-to customer and [F:BPA] sold-to customer classes |
Yes |
|
|
*7 |
Pay-by customer (EDI specificity): The value before ‘~’ loads the customer code. |
Yes |
|
|
*7 |
Pay-by customer: loading the [F:BPR] BP, [F:BPC] pay-by customer and [F:BPA] pay-by customer address classes |
Yes |
|
|
*8 |
Ship-to customer (EDI specificity): The value after ‘~’ loads the Address code. |
Yes |
|
|
*8 |
Ship-to customer: loading the [F:BPD] ship-to customer and [F:BPA] ship-to customer address classes |
Yes |
|
|
*9 |
Carrier (EDI specificity): The value before ‘~’ loads the carrier code. |
Yes |
|
|
*9 |
Carrier: loading the [F:SDH] delivery class (from the delivery no. of the first invoice line), [F:BPT] carrier class and [F:BPA] carrier address class |
Yes |
|
|
*15 |
Order: loading the [F:SOP] and [F:SOQ] classes on the first order line. This action is required when the data stored on the lines must be displayed in the header record export file. |
Yes |
|
|
*52 |
Product: Loading the [F:ITM] product, [F:ITS] product-sales and [F:ITU] product-customer classes |
Yes |
|
|
*71 to *78 |
Lines 1 to 8 of the order header text |
Yes |
Yes |
|
*81 to 88 |
Lines 1 to 8 of the order footer text |
Yes |
Yes |
|
*91 to *98 |
Lines 1 to 8 of the line text |
Yes |
Yes |
IMPSOQ: Sales delivery requests
Variables are used in Text import.
During an import, variables are used to manage the EDI identifiers for the customers and the carrier. EDI files contain an order (sold-to) identifier and a delivery identifier (with the same structure as the order identifier). In the application, the delivery address is an address code linked to the sold-to customer. In the EDI context, the same identifier is often used for the order and delivery. However, in the application, this represents two pieces of information. The EDI-Appli software refers to a table of correspondences and, for an EDI identifier, delivers one piece of data composed of the customer code and the address code separated by a ‘~’ character in the file to import.
093195450607700237;AIRFRANCE~RSY (093195450607700237 = EDI identifier / AIRFRANCE = X3 customer code RSY = delivery address code). The AIRFRANCE~RSY information is delivered in the pivot file; only the value before the ‘~’ character is used as the customer code.
|
Variable |
Description |
Import |
Export |
|
*6 |
Sold-to customer (EDI specificity): The value before ‘~’ loads the customer code. |
Yes |
|
|
*8 |
Ship-to customer (EDI specificity): The value after ‘~’ 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: SO pricing
In the SPRICLIST record, the criteria are grouped as a single piece of PLI data, but they must be defined separately in the template.
|
Variable |
Description |
Import |
Export |
|
*1 |
Criteria 1 for the price list |
Yes |
Yes |
|
*2 |
Criteria 2 for the price list |
Yes |
Yes |
|
*3 |
Criteria 3 for the price list |
Yes |
Yes |
|
*4 |
Criteria 4 for the price list |
Yes |
Yes |
|
*5 |
Criteria 5 for the price list |
Yes |
Yes |