Sales Orders

Use the order import to create orders or to import modifications on an existing order.
You can also delete specific lines without deleting the order itself, if required. This means that there must always be at least one order line.

The import of open orders is not supported in standard mode.

A sales order is comprised of a header and one or several lines. The main file to set up is always SORDER (order header) as this is the file linked to the SOH object.

In order creation, you thus need to set up two identifiers:

• one for the header file SORDER,
• one for the detail file SORDERQ.

During the import in modification mode, the existence of the main object is acknowledged automatically with the main key that is the order number (SOHNUM). The existence of the detail lines is acknowledged in three ways depending on whether or not the order line number is included in the import template:

• Search with the line number (SOPLIN) if it is set up and assigned. If there is such a line, it is modified, otherwise it is created.
• Search with the product reference and the shipment date if these two fields are set up and entered. If there is such a line, it is modified, otherwise it is created.
• Search with the product reference if the field is set up and assigned. If there is such a line, it is modified, otherwise it is created.

If two lines have the same product reference (and the same shipment date), the line number must be redefined in order to differentiate them. Otherwise, the first line corresponding to the search criteria is always the one to be processed.

The order import processes the deletion of a line detail. An order line will be deleted if it is imported with a blank order quantity. An order cannot be completely deleted. There must always be at least one line.

During an import, you can also specify if the order line must be closed or not. You must then add the SOQSTA field to the template.

When the import impacts a large number of records, the process duration can be quite long.
Implementing solutions to improve performances can reduce the process duration.
These solutions can consist in:

• Implementing a mechanism to disable the management of fields that are not contained in the import template.
  For additional information on this mechanism, see section: Import performance improvement.
• Creating the multilegislation records for each legislation of the folder.
  Example: The FRA, POR and USA legislations are used in a folder. If the FRA and POR legislations have the same setup, it is recommended to create a record for the FRA legislation and a record for the POR legislation, instead of having a single record for all legislations.
  To view more information on the multilegislation performance improvement principle and obtain the list of objects that you can create by legislation, refer to the document:Performance improvement: List of the multilegislation objects.

Import of invoicing terms

If an invoicing term is included in the import template on the header or on a line, this term is used to calculate the scheduled invoices of lines related to non deliverable products. This rule only applies to orders of the normal category.

Import of kits and BOMs

There are two methods to import kits and BOMs.

• The LINTYP field is not included in the template. In this case, it will be necessary to only import the parent product (as the components are not considered as belonging to the kit or the BOM but they are processed like standard products). Importing the parent product leads to the automatic generation of all the components defined by the first BOM code. The components with the Option or Variant type are also generated for the first option and the first variant.
• The LINTYP field is included in the template. In this case, importing the parent product does not trigger the automatic generation of the components. The component lines must be imported by specifying the value of the corresponding LINTYP. You can thus specify the selected components for kits or BOMs containing options or variants.

Import of plain texts

When required, you can import texts into the order headers, order footers and order lines. Set this up in the import template using the GIMP global variable (in the template, *71... fields are included).

• The GIMP(71..78) fields are used to import the texts linked to the order header. You can thus import a text of 8*100 characters, in other words 800 characters.
• The GIMP(81..88) fields are used to import the texts linked to the order footer.
• The GIMP(91..98) fields are used to import the texts linked to the order lines.

Import of dimension types on the line

See the SOHFL import template.

Import of invoicing elements

The value entered for the invoicing elements can be imported into the different documents using the INVDTAAMT fields. (SQH, SOH, SDH).

Project code import and impact on prices and discounts

• Project code management:
  
  For documents, single project and multi-project management must be distinguished. This management mode is determined by the PJTNSGDOC - One project by document parameter (TC chapter, PRP group).
  
  1/ Single-project management of documents:
  
  

  Import template with The project code ...		Management of the project code on the order
  ... in the header	... on the line	In creation mode	In modification mode
  YES	NO	Header = Value of the header import file Line = Header value
  YES	YES	Header = Value of the header import file Line = Value of the line import file, or header value if the line value is different from the header + information message
  NO	YES	Header = Blank value Line = Blank value (+ information message if attempt to import a not blank project code)	Header = Non modified value Line = Non modified value (+ information message if attempt to import a different project code)

  
  
  2/ Multi-project management for documents:
  
  

  Import template with The project code ...		Management of the project code on the order
  ... in the header	... on the line	In creation mode	In modification mode
  YES	NO	Header = Value of the header import file Line = Header value	Header = Value of the header import file Header = Non modified value
  YES	YES	Header = Value of the header import file Line = Value of the line import file
  NO	YES	Header = Blank value Line = Value of the line import file	Header = Non modified value Line = Value of the line import file

  
  
• Impact on prices and discounts
  
  No re-calculation of prices and discounts is carried out on import. However, the behavior can change whether the price is entered or not in the import file:
  
  1/ The price is not specified on the file:
  - In creation mode the price results from the price list search based on the project code of the quote.
  - In modification mode, the price is not recalculated.
  
  2/ If the price is specified on the import file: in creation and in modification, the price corresponds to the one of the import file.