Setup >  Sales >  Document types >  Order types  

Display all Hide all

The order types are used to define the order typologies and associate them with a functional category and if required to assign a different sequence number counter. An order category is used to define a group of functional rules.

In customer order or contract order entry, it is mandatory to specify the order type in the header. It is this type that will define the processing applied to the order that is entered.

Prerequisite

SEEREFERTTO Refer to documentation Implementation

Screen management

An order type is defined by an alphanumeric code of three characters. It is this code that will be called on entry of the customer order.

Entry screen

Fields

The following fields are present on this tab :

Header

Alphanumeric code used to identify the order type.

In creation mode, the legislation code can be initialized via the user parameter LEGFIL - Legislation (selection filter) (SUP chapter, INT group). This parameter is also used to filter the list left in order to present only the codes defined for this legislation and those defined at the "All legislations" level.
The legislation code is not mandatory. It is used to limit the use of an order type to companies liable to a given legislation.

Reminder of the main principles relating to the use of data or a setup element defined by legislation, when the company context is known (record, flow, etc.) 

  • When a setup element is defined for a legislation, it can be used only 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 legislation (that is to say : "All legislations"), this element can be used in every record, without any consideration of the legislation, unless there is a setup element with the same code, defined for the company legislation. In that case, only the setup element defined for the company legislation is suggested for the selection and accepted for the entry (as long as it is "Active").
    SEEWARNING If the setup element defined for the company is not "Active" and the setup element defined at the "All legislations" level is "Active", this setup element cannot be used.
     
  • 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 to which the record is associated, belongs to this company group.

Example 1:
Setup of invoice type as follows:

Invoice types 

Legislation

 FAF

Blank = all legislations

 FAF

FRA

 CTD

 Blank = all legislations

 BEF

FRA

 CVC

POR


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

Invoice types

Legislation

FAF

FRA

CTD

Blank = all legislations

BEF

FRA

SEEINFOAn additional filter is applied depending on the company group entered.
If, in the example above, a company group is also specified at the level of the FAF invoice type setup with the FRA legislation, this invoice type is suggested for selection only if the company belongs to the company group entered.

Example 2:
Setup of invoice type as follows:

Invoice types

 Legislation

Group of companies

FAF

 Blank = all legislations

Blank = all groups

FAF

 FRA

GRP

CTD

 Blank = all legislations

Blank = all groups 

BEF

 FRA

Blank = all groups

CVC

 POR

Blank = all groups


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

Invoice types

 Legislation

Group of companies

 CTD

 All legislations

All groups

BEF

 FRA

All groups


SEEINFO The FAF invoice type cannot be used because, for the FRA legislation, it is defined for the GRP company group.

  • Description (field DESAXX)

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/update) in the connection language of the user.
You can add your translation in another language using the Translation function:

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

A user who logs on with this language will view the short description, long description or column header in their connection language if a translation exists. Otherwise, these descriptions will be available in the folder language.

SEEINFO The connection language must be defined as a default language for the folder.

  • Short description (field SHOAXX)

Short title used in the screens and reports. This title is recorded in your connection language.

By default the short title, the long title or the column header of a data are recorded (on creation/update) in the connection language of the user.
You can add your translation in another language using the Translation function:

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

A user who logs on with this language will view the short description, long description or column header in their connection language if a translation exists. Otherwise, these descriptions will be available in the folder language.

SEEINFO The connection language must be defined as a default language for the folder.

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/group of the document type and the legislation/group of the document.

SEEREFERTTO For further information click here.

General

  • Order category (field SOHCAT)

Order category.

- Standard:

Classic order: order, shipment with stock issue on validation, invoicing of the shipment.

- Loan:

Order concerning a loan of goods: order, shipment with transfer of stock to a business partner location on the validation,

return with the return to stock in the original location. No invoicing (except if the return date is exceeded).

- Direct invoicing:

order, invoicing of the order with stock issue on validation of the invoice.

- Open:

Within the framework of a contract, management of shipment requests.

  • Manual sequence no. (field MANCOU)

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 will be assigned automatically by the counter upon creating the document.
  • Normal (field FILNOR)

 

  • Final (field FILDEF)

 

It is mandatory that the code a sequence number counter associated with the defined order type be entered, whether the number assignment is automatic or manual.
It is therefore recommended to have first defined a sequence number counter in the Sequence Numbers table (that can be accessed by tunnel from this field).

 

This is the delivery type associated with the order type when the delivery is created from the order using the [Delivery] button.
A control is used to check that these types belong to the same category and that they are consistent with the legislation and company/site group.

When it is not entered, the default delivery type used in the order delivery ([Delivery] button) is the one specified for the following parameters (VEN chapter, SSD group):

These parameters are also used as default values in the launching screens of the Automatic Delivery of orders or in the Delivery of picking tickets. The delivery import also uses these general parameters.

Electronic signature

  • Record type (field RECTYP)

 

Close

 

Specific Buttons

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

Document sequence number counter: XXX. Record does not exist

This message appears when an attempt has been made to allocate a non-existent sequence number counter to the order type.

Tables used

SEEREFERTTO Refer to documentation Implementation