Blog from April, 2019

From version 3.90 of LLSHMNT the program can use specific screen depending on area and type.
Please see the documentation for more information.

(info) This time in German as it concerns the German customs communication only!

am Sonntag, dem 15. Februar 2009, wird das Atlas-Clearing-Center auf ein anderes System migriert. Die Umstellung wird ca. zwischen 18 und 21 Uhr vorgenommen. Zu diesem Zeitpunkt wird keine Kommunikation mit dem Zollsystem ATLAS möglich sein.

The Compliance Check module has been enhanced.
A new Parameter (LRN 035/253) has been created, which holds the number of days where no compliance check shall be started.
This is calculated "Today plus number of days".

The Compliance Check programs evaluate the parameter. When an address is entered in operations, the programs check the date of last check in address maintenance and calculate whether the address needs to be checked again.

Change in SHPM

The field "Auftraggeber" (Field #241) is now obsolete and not filled by shpmsngl from version 3.82.
The value of this field is already covered in field "orderer address no. in shpmbra" (Field #145).

Please change your templates using program SHPMCONF accordingly.

From version 2.29 on, program rsiprtq3 requires a slay screen. The slay screen can be created using program 'slayprtq'.

Change in SLAYINC

With freshly compiled versions of programs using SLAY-Screens, a new warning can appear.
This warning states:

Attention: @ truncated!

The warning indicates which @number is truncated.
The warning appears only for @numbers whose value is numeric, i.e. weight, pieces, nad-numbers.

The action necessary is to adapt the corresponding SLAY-Screen,
so that the value of the @number can be displayed completely without cutting off the value.

EXPINF3L Datarange

Hardcoded settings per customer company number have been removed.
Please set LRN 100/093 to enable/disable today´s date in @7.

This change takes affect from versions:
expinf3 3.69
expinf3l 4.73


We have made a change to include SNDMGR3.
This change prompts programs to use the file extension chosen by the creating program to use the same extension for the output file. Previously, during copying to scratch files, the extension (i.e. xml) could be lost and the output file had the wrong extension.

Please report any problems with Procars output by creating a ticket to

The following essential rule has been changed in all Procars event creation.

The following programs are affected.

Affected Programs






Rel I+J



Rel I+J



Rel I+J



Rel I only



Rel I only

Automatic Manifest Event Generation

Automatic Manifest Event Generation has been changed from hardcoded generation of IMAN/TMAN event to a configurable generation via TRKPAR3 (use TRKPAR3 settings for new group Air Export / MAWB Print - Events for HAWBs).
Configure a automated event for manifest event generation in TRKPAR3 in order to conserve the previous behaviour.

Event Insertion Rule Amendment

The behaviour for automatic insertion/update of tracking events has been changed substantially:

Former versions of TRKINS prevented the insertion/update of any tracking event if it already existed but only differed in the date/time, for all tracking events and independently TRKPAR3 settings.

This general rule has been removed. Event will always be inserted or updated, depending upon single/multipe settings from TPTMNT. Special rules only apply when TRKINS is invoked with special commandline option "-NOUPDT".

Note: The change makes correct "Update/Write-Only" settings in TRKPAR3 even more important. If one wishes to conserve the "old" behaviour, one should ensure that the "W" (=Update/Write-Only) column in TRKPAR3 contains a '*' character. If the '*' character is configured, the commandline option "-NOUPDT" is used which prevents updates. The following examples only apply for TRKPAR3 setting allowing upate ("W" column contains a space):

Example 1
AWB FRA 01.08.2009 15:29 AWB PRINTED
exists and the event
AWB FRA 02.08.2009 09:29 AWB PRINTED
should be generated (triggered e.g. by TRKPAR3 settings, automated on AWB printing).

Former implementation prevented the event to be inserted and kept the event dated 01.08.2009 15:29.
The new implementation will overwrite the event if "AWB" is configured to be Single or Single-per-Location in TPTMNT (so the date of the first AWB print will be lost) or will insert the new event additionally to the existing one (in case of multiple configuration from TPTMNT).

Example 2
AWB FRA 01.08.2009 15:29 AWB PRINTED 01.08. 15:29
exists and the event
AWB FRA 02.08.2009 09:29 AWB PRINTED 02.08. 09:29
should be generated (triggered e.g. by TRKPAR3 settings, automated on AWB printing).

Behaviour did not changed since the events differ in the remarks. The event is inserted/updated applying TPTMNT3 single/multiple configuration.

We have enhanced the field "telephone-no" in SEKMNT3 and SIKMNT3 to 20 digits (same record length like in NADMNT3, AEKMNT3 and IMKMNT3).
If you require the corresponding program update, please contact the customer support ( with the reference "Ticket 211198".

Air France / KLM have changed the method of calculation of the fuel surcharge as from
September 1st 2008. Part of the fuel surcharges are incorporated into the net rates.
Air France / KLM also introduced the calculation of fuel surcharges on a regional basis
dividing the globe into three regions for the calculation of fuel surcharges.
The storage of these regional surcharges can be managed in PROCARS
through the AREAMNT file. Please contact your system administrator
or RSI for details.
ETIHAD Crystal Cargo has informed their customers that it will be integrating part
of the fuel surcharges into the freight charges. According to Frank Schlund from
ETIHAD Frankfurt there will be no regional tariffs for the fuel surcharge.

There has been a new function/Change for Slay-Screens: the display of variables (=@-fields) will be auto-formated to a corresponding length, so nothing will be overwritten. This means, that the label will remain even when fields are set too close together. This auto-format will include a "space" for separation, if the following character is a letter, a digit or a "@"-sign. Other characters (eg. "/", "^") will be excluded from this routine.

Example: in the screen you insert variable @A, which has a default length of 50 digits. However after 20 digits you insert a text (eg. KGS). Even though you can insert the total of 50 digits, in the display the system will only show 19 digits of @A, then have a "space" and then KGS. If you inserted a "/" instead of the text, the system would show 20 digits of @A and then "/".

This feature has been implemented to give more space and options to include more input/variables in one screen. Again, this feature is only restricted to the display of the values. The user is still able to insert the total length for each variable given in SLAYMNT3.

With new compiled program-versions, which use the include "SLAYINC" (eg. AIMNT), this feature will be available.

New program PAR_CUR

A new tool-program "PAR_CUR" has been implemented to display all corresponding parameters regarding currencies.
For more details please check its documentation.

Die Zertifizierungsphase 1 und 2 für die Zollsoftwarelösung AT-aes für PROCARS.classic zur Teilnahme am ATLAS Ausfuhrverfahren (Nachrichtengruppen EXP und EXT) wurde am 8. September 2006 erfolgreich abgeschlossen! Die Pilotphase beginnt in Kürze.
Weitere Details zum ATLAS Verfahren stehen in der am 20. Juli 2006 veröffentlichten Verfahrensanweisung:

Verfahrensanweisung zum IT-Verfahren ATLAS
PDF, Stand: Juli 2006

We have created the following documentation regarding parameter setting for 2007.