Transportation note type

Alphanumeric code used to identify the type of delivery.

In creation mode, the legislation code can be initialized via the LEGFIL - Legislation (selection filter) parameter (SUP chapter, INT group). You can also use this parameter to filter the selection panel and only display the codes defined for this legislation and those defined for All legislation.

The legislation code is not mandatory. When the code is entered, you can only use the delivery type for companies subject to this legislation.

The main principles relating to the use of data or a setup element defined by legislation, when the company context is known, such as record, flow, and so on:

• When a setup element is defined for a legislation, it can only be used when the legislation of the context is identical. It cannot be used in a record set up with another legislation.
• When a setup element is defined without a legislation (All legislations level), it is considered as having a multilegislation nature. This element can be used in every record, irrespective of the legislation, unless there is a setup element with the same code, defined for the company legislation. In that case, the setup element defined for the company legislation is the only one submitted for selection and accepted on entry, if active.

• An additional filter is applied on the setup element depending on the company group defined. This setup element can only be used and is only suggested for selection if the company associated to the record, belongs to this company group.

Example 1 - Setup of invoice type as follows:

When entering an invoice for a company with a FRA legislation, only the following invoice types are suggested for selection:

Example 2 - Setup of invoice type as follows:

When entering an invoice for a FRA legislation company, belonging only to the NOR group, only the following invoice types are submitted for selection:

This long description is used as a title in screens and reports.

By default, the short title, the long title or the column header of a data are recorded, on creation or update, in your connection language.

You can add your translation in another language using the Translation function:

• Select Translation from the Actions icon in the corresponding field.
• In the Translation window, add a new language code with the translation in this language.

When you log on with this language, you see the short description, long description or column header in your connection language if a translation exists. Otherwise, these descriptions are available in the folder language.

This short title is used as a title in screens and reports. It can be translated. It is recorded in your connection language.

If you want to translate it into another language:

• Select Translation from the Actions icon in the related field.
• In the Translation window, add a new language code with the translation in this language.

By entering a company group, you can limit the scope to companies in the selected group only.

When this data is used for another record or with a setup element also defined in the group, a control checks that the groups have at least one company in common when the groups are different.

In addition, a consistency check is performed for the legislations of the companies in the selected group. At least one of these companies must have the same legislation as the one entered in the Legislation field. If not, a warning message displays.

When using the document type, a consistency check is also performed between the legislation or group of the document type and the legislation or group of the document.

This information is used to specify whether the document number can be entered manually.

• If this field is set to No, the number can only be assigned automatically.
• If it is set to Yes, the number can also be entered. If it is not entered, a number is assigned automatically by the counter upon creating the document.

If Update document date is set to Yes or if the record type is set to Normal, Sage X3 compares the Shipment date (SHIDAT) with the current date.

If the dates are different, it updates the SHIDAT field to the current date, which is the validation date. It then performs an additional check:

• If the Departure date (DPEDAT) becomes earlier than SHIDAT after this update, Sage X3 raises an error and rolls back the validation.
• If the Departure date (DPEDAT) remains later than the validation date, it calculates a new delivery date.

The field has an impact when the record type is not set to Normal, which is the most common scenario.

For example, if it is an external document, it is advisable to set Update document date to Yes to ensure these shipment dates are updated.

The counter code associated to the defined type of delivery must be entered, whether the number allocation is automatic or manual. It is recommended to have previously defined a sequence number counter in the Sequence Numbers table, that can be accessed by tunnel from this field.

When the counter is used for the Portuguese legislation, the sequential number is applied to the document when it is subject to the electronic signature and SAFT-PT (Standard Audit File-Tax) payment processes.

Set the PORDKS - Electronic signature Portugal parameter (LOC chapter, POR group) to Yes and activate the DKS - Electronic signature. The counter needs to have the following structure:

• The first component needs to be a constant component type. Its value needs to be equal to:
  • The code of the Sequential number code that may contain or not the PT abbreviation.
  • The value of the original type of document. This value needs to match with the constant one, the - character is optional.

Example: Invoice type FCL has associated the PTFCL counter and the FCL constant.

• The second component needs to be the company code or the code site, if the counter is defined at the company level or at the site level.
• The third component should correspond to the year or the fiscal year, if the counter is set at the year or fiscal year level. It is strongly recommended that you do not use the month or the period within the framework of the electronic signature.
• The fourth component must be a constant type with the / value.
• The fifth component must be a sequential type one.

Between the first and the penultimate component, the complement can be used as an option. The complement is mandatory for purchase auto-invoices. If the structure is not properly defined, a blocking error occurs once the document is validated or signed.

This field can only be viewed if the following conditions are met:

• The KPO - Portuguese localization activity code is active.
• The legislation code of the return type is empty or is set to POR.

You can indicate here a final sequence number that has to be different from the main sequence number. This sequence number is used upon delivery validation to assign a new number to the delivery.

Set the SDHENDNBR - Final delivery sequence No. parameter (VEN chapter, SSD group) to Yes. If this parameter is set to Yes but no final sequence number is specified, the final sequence number specified in the Sequence number assignments table for Final deliveries is considered. The former number is no longer displayed but it is still recorded in a specific field (TMPSDHNUM) in the delivery table.

When the counter is used for the Portuguese legislation, the sequential number is applied to the document when it is subject to the electronic signature and SAFT-PT (Standard Audit File-Tax) payment processes.

Set the PORDKS - Electronic signature Portugal parameter (LOC chapter, POR group) to Yes and activate the DKS - Electronic signature. The counter must have the following structure:

• The first component needs to be a constant component type. Its value needs to be equal to:
  • The code of the Sequential number code that may contain or not the PT abbreviation.
  • The value of the original type of document. This value must match with the constant one, the - character is optional.

Example: Invoice type FCL has associated the PTFCL counter and the FCL constant.

• The second component needs to be the company code or the code site, if the counter is defined at the company level or at the site level.
• The third component should correspond to the year or the fiscal year, if the counter is set at the year or fiscal year level. It is strongly recommended that you do not use the month or the period within the framework of the electronic signature.
• The fourth component must be a constant type with the / value.
• The fifth component must be a sequential type one.

Between the first and the penultimate component, the complement can be used as an option. Although, the complement is mandatory for purchase auto-invoices. If the structure is not properly defined, a blocking error occurs once the document is validated or signed.

This field is displayed only when the KPO activity code is active.

The type of document is necessary so that you can assign a dedicated sequence number to it. It can take the following values:

• Normal
• Manual document recovery: The source document has been generated manually in paper form, as the system was unavailable.
• Backup document recovery: Already recorded documents have been lost due to the restoring of a backup. These are documents recorded between the time when the backup has been performed and the time when the backup has been restored. It is necessary to create them again manually.

• External document: The document was originally created in another software, which has provided the electronic signature. No electronic signature is generated by Sage X3 for this document type.

This field determines the available document type in order to distinguish the several document types allowed by SAFT.