Sales Order Types

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

See also 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

Field descriptions

Block number 1

  • 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.

    The connection language must be defined as a default language for thefolder.

    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.

    The connection language must be defined as a default language for thefolder.

    Order type (field SOHTYP)

    Alphanumeric code used to identify the order type.
    Legislation (field LEG)

    In creation mode, the legislation code can be initialized via the user parameter LEGFIL - Legislation (selection filter) (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 legislations’.
    The legislation code is not mandatory. When the code is entered, you can only use the order type for companies subject to this 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 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 (provided it is ‘Active’).
      Warning Notes:
          • If the setup element defined for the company is not ‘Active’ and the setup element defined at the "All legislations" level is, this setup element cannot be used.
          • To reduce the processing time and thus improve performances, we recommend not to create multilegislation records and instead create records for each legislation of the folder.
            For further information, refer to the documentation on Performance improvement: List of the multilegislation objects.
    • 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 type

    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 type

    Legislation

    FAF

    FRA

    CTD

    Blank = all legislations

    BEF

    FRA

    An 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 type

    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 submitted for selection:

    Invoice type

    Legislation

    Group of companies

    CTD

    All legislations

    All groups

    BEF

    FRA

    All groups


    Note The FAF invoice type cannot be used because it is defined for the GRP company group for the FRA legislation.
    • 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:
    • Short description (field SHOAXX)

    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.

    See also For further information, click here.

    General

    Order category (field SOHCAT)

    It is the category for the order type, to be chosen amog the following categories:

    • Classic
      This category follows the classic cycle for an order: order, delivery, invoicing. The delivery can be replaced by a direct back-to-back order. The stocks are adjusted upon delivery.
       
    • Loan
      This order category deals with a loan of goods: order, delivery with stock transfer on an BP location upon validation: the stock of loaned products must necessarily be managed on locations.
      It involves the management of a return date with reset of the stock on the original location and does not lead to the invoicing (unless the expected return date is overdue). 
       
    • Direct invoicing
      This order category follows the Order, Invoicing cycle.
      The stocks, if managed, are adjusted upon the validation of the invoice.
       
    • Open order
      This order category is used to plan and schedule the delivery requests for a customer within the framework of a contract.
    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.
    Sequence number (field CODNUM)

    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.
    Is it recommended to first define a sequence number counter in the Sequence number definition table. You can access this table by clicking the Actions icon on this field.
    Final sequence no. (field CODNUMEND)
    Delivery type (field SDHTYP)

    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 a default value in the launching screens of the Automatic delivery of orders or the Delivery of picking tickets functions. The delivery import also uses these general parameters.

    Electronic signature

    Record type (field RECTYP)

    Specific Buttons

    Copy

    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

    See also Refer to documentation Implementation