Orders

• Transaction (field STRNUM)

Code used to identify the transaction set up.

The setup of the entry transactions enables the user to fully set up the entry screens associated with a document (quote, invoice order, request for quotes etc.) or with a stock transaction type (receipt, issue etc.).

For each document or stock transaction type, it is possible to define as many entry transactions as necessary, each one being identified by a code.

Each transaction is used to define, both for fields located in the document header and fields entered in the lines, whether they must be:

• entered,
• only displayed,
• or hidden.

Upon validation of this setup, dedicated entry screens are created, and then can be used by any user having been granted rights on the access code defined in this setup header.

• If a given user has the right to use several transactions of a given type, the choice is presented to the user when entering the function.
• If the user is only authorized one transaction, this transaction is automatically taken into account when entering the function.

• Description (field DESAXX)

Transaction description.

• Active (field ENAFLG)

This flag is used to activate or deactivate a transaction.
The inactive transactions are not presented in the transaction selection window.

• Access code (field ACSCOD)

Access code that is used to restrict access to data by user or group of users.
If this field is assigned, only users with this access code in their profile can use this transaction.
If several transactions are set up for a function, and the user only has access to one of them because of the access codes, the selection window is no longer suggested: the access is by direct entry. 

• Group (field GFY)

The group of companies or sites entered here is used to filter the records.
These records will be accessible during the transaction.

• Document (field DOCNAM)

Code of the standard document printed during an automatic printing at the end of entry.

• Auto print (field DOCFLG)

Select this check box to automatically launch the printing of the document on entry completion.

The automatic printing only takes place in creation mode.

• Elements (field INVDTACOD)

This table contains the document invoicing elements (quote, order, shipment, invoice).

• Document (field SNSNAM)

Code of the standard document printed during an automatic printing at the end of entry.

• Auto print (field SNSFLG)

Automatic print flag used to define whether or not the Prepayment document should be automatically printed at the end of entry.

• Order category (field ORDCAT)

This is the order category.

• Normal (standard order): order, shipment with stock issue on validation, invoicing of the shipment,
• Loan (order concerning a loan of goods): order, shipment with transfer of the stock to a BP location on validation, return of the stock to the source location.
  No invoicing (except if the return date is exceeded).
• Direct invoice: order, invoicing of the order with stock issue on validation of the invoice.

• Closing reason (field CCLRENCOD)

Parameter that is used to define, for this entry transaction, whether the order closing reason must be displayed or not.

The cancellation reason for an order is entered during the closing of an order (if the order cancellation reasons management parameter is active).

• Order state (field STACOD)

Various statuses of the document linked to the order (acknowledgement printed and Status of balance, allocation, delivery, order, invoice and credit).

• Last delivery (field LASDLVCOD)

Latest delivery number for the order.

• Intersite (field BETFCYCOD)

Help common to all transactions related to sales documents.

Use this parameter to define if the inter-site nature of the document must be displayed or not.
Inter-site documents are used for exchanges between different sites. These sites can belong to different legal companies, but only if the documents are also defined as ‘inter-company’.
Reminders:

• A document is considered as an inter-site document when the recipient business partner is defined as a site: this BP is set to inter-site at the level of the BP record and linked to a site.

• An inter-company document is always an inter-site document as well.

• An inter-site order is an order that is delivered but not invoiced.

• Intercompany (field BETCPYCOD)

Use this parameter to define if the inter-company nature of the document must be displayed or not.
Inter-company documents are used for exchanges between sites belonging to different legal companies.
Reminder:

A inter-company document is considered as such if it meets the following criteria:

• The recipient business partner is defined as a site: this BP is set to inter-site at the level of the BP record and linked to a site.

• This site linked to the recipient BP belongs to a different legal company than the original site of the document.

• Delivery type (field SDHTYPCOD)

This check box is used to specify whether, for this entry transaction, the delivery type must be displayed or not.

• Quote no. (field SQHNUMCOD)

The quote number allows the quote to be identified in a unique way. This number is automatically assigned or entered upon each creation of a quote following the counter parameterization defined for the quotes.

If the quote counter is defined with automatic allocation, the quote number field is not accessible and the counter is assigned to the quote creation. Conversely, if the quote counter is defined with manual allocation, it is possible to enter it manually. If it is not entered at the moment of creation, the system will automatically assign a quote number according to the counter.

• Proforma invoice no. (field PRFNUMCOD)

This is the number of the pro forma invoice associated with the document. The generated pro forma number is displayed if a pro forma invoice is created from this document. A tunnel then makes is possible to access the invoice.

• Last invoice (field LASINVCOD)

Latest invoice number for the order.

• Order amount (field AMTCOD)

Select this check box to display the various amounts of the document linked to the order.
The following amounts are concerned: Ex-tax amount to be delivered, Ex-tax amount to be invoiced, Ex-tax order amount, Tax incl. order amount, Total margin.

• Margin (field PFMCOD)

This parameter is used to define, for this entry transaction, whether the margin must be displayed or not.

This concerns the display of the margin on the line, and of the document total margin.

• field PFMSCR

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Block status (field HLDCOD)

This field displays the manual order hold reason, entered to hold the order.

To enter this code, open the Order hold/release screen by clicking the lock icon Hold status lock.
In this screen, click Jump to from the Hold code field to modify or enter a new code in miscellaneous table 204 dedicated to Manual hold reasons. In this table, three settings determine the allocation status, the back-to-back order creation, and the access codes for higher security:

• Enter No in the Allocation field to deallocate the quantities when the hold reason code is selected.
• Enter Yes in the Back-to-back order hold field to hold the creation of the back-to-back order.
• Enter an access code to give the authorization to release the order only to the user profiles attached to this code.

• Credit release (field CDTBTNCOD)

• Availability of product (field AVASTOCOD)

Availability.

This is used to know the date of the first availability of a product if it is unavailable.

If this information is requested, it appears on the ordered quantity in the status bar. The date of first availability is accompanied by the first available quantity.

• Stock unit (field STUCOD)

Product storage unit.

• field STUSCR

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Allocated quantity (field ALLQTYCOD)

This field displays the quantity allocated to the order line.

• field ALLQTYSCR

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Shortage (field SHTQTYCOD)

This field indicates the shortage quantity.

• field SHTQTYSCR

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Net price (field NETPRICOD)

Net price.
It is the net price for the line. It is calculated from the gross price and the various charges/discounts.
This field cannot be modidfed.

• field NETPRISCR

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Line amount (field LINAMTCOD)

Parameter that is used to define, for this entry transaction, if the ex-tax and tax-incl. amounts on the document lines must be displayed or not.

• field LINAMTSCR

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Back-to-back order no. (field FMINUMCOD)

This field contains the direct order number depending on the shipping method code.
If it concerns a PO Direct to customer or Received and shipped, the direct order number corresponds to the number of the purchase order generated.
If it concerns a work order, the direct order number corresponds to the number of the
WO generated.

• field FMINUMSCR

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Quote no. (field SQHNUMCODD)

Quote nb at the origin of the order line.

• field SQHNUMSCRD

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Line type (field LINTYPCOD)

Field that cannot be entered and that defines the line.
The line can have the following values:

• Normal,
• Kit parent product,
• Kit component,
• Kit option,
• Kit variant,
• BOM parent product,
• BOM component,
• BOM option,
• BOM variant,
• Subcontracted,
• Service,
• Supplied material.

• field LINTYPSCR

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Free (field FOCFLGCOD)

Non-enterable field defining the free item characteristics.
The values can be:
- No: This line mentions a price and has not delivered any free items
- Origin: Line mentioning a price and giving rise to free items
- Free item: Free line.

• field FOCFLGSCR

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Closed (field CFMFLGCOD)

This field indicates the line status and cannot be entered.
In a normal order the line can be pending or closed, in a contract it can be pending, late or closed.

• field CFMFLGSCR

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Closing reason (field CCLRENCODD)

Parameter that is used to define, for this entry transaction, whether the order closing reason must be displayed or not.

The cancellation reason for an order is entered during the closing of an order (if the order cancellation reasons management parameter is active).

• field CCLRENSCRD

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Bill-to customer (field BPCINVCOD)

The bill-to customer code must be active. In all cases, it is initialized by the bill-to customer code associated with the sold-to customer in the latter's record. These is the possibility to modify the bill-to customer if necessary. From this field, it is possible to select a customer or access customer management by tunnel if the user's authorizations allow it. Once the order is partly delivered, this information will no longer be accessible.

Special features linked to the inter-company: In the case of an inter-company order automatically generated from a purchase order, the bill-to customer corresponds to the customer associated with the invoicing site entered in the purchase order. This information is not modifiable in this context.

• Pay-by (field BPCPYRCOD)

The Pay-by BP is initialized by default by the pay-by BP associated with the sold-to customer in the latter's record in the case of a direct delivery. Otherwise, the pay-by BP of the original order is used.

It is possible to:   

• modify the pay-by BP if necessary,
• select a BP or access BP management by tunnel if user authorizations allow it.

 Special features linked to the inter-company: in the case of an inter-company order automatically generated from a purchase order, the pay-by BP corresponds to the customer associated with the invoicing site entered in the purchase order. It cannot be modified in this context.

• Group customer (field BPCGRUCOD)

The group customer is initialized by the group customer code associated to the sold-to customer in the latter's record. This information is used for the generation of statistics. It is also involved in the grouping of invoices during the automatic generation of invoices. There is the possibility to modify the group customer if necessary.
From this field, it is possible to select a customer or access customer management by tunnel if the user's authorizations allow it.

It is possible to search a customer or several customer grouped under the same criteria by selecting "Quick customer search". A list of matching items is generated on tabulating to the next field.
For a more advanced search, all fields present in the block can be entered. The list of matches is narrowed down with each tabulation.

• Delivery address (field BPAADDCOD)

This field indicates the code of the address to ship to.
You can view the detailed address information by clicking Address from the Actionsicon.

• On creation, this field is no longer accessible when a delivery line is created.
  
• Once the delivery has been created, this field can no longer be modified, but you can still display the detailed address information.
  You can modify the address by clicking Address/Delivery in the action panel.

• Project (field PJTCOD)

This parameter used to define, for this entry transaction, whether the project must be:

• Hidden:
  The field is not displayed in the entry screen and thus it remains empty.
• Displayed:
  The field is displayed empty and cannot be modified.
• Entered:
  The field is displayed empty but can be modified.
  The control of the entered value is based on the parameter CTLOPPCOD - Operator code control (pur/sal)

• Sales reps (field REPCOD)

The sales reps are initialized by the customer sales reps, then by those of the ship-to customer, if no sales rep exists in the customer record. In the case of a prospect, the representatives of the prospect are not considered. These sales rep codes are copied to the document lines. If a representative is modified in the document header upon creation or when lines exist in the document, the system suggests to copy the modification to all the lines that already exist.

• Loan return date (field LNDRTNCOD)

The planned loan return date is accessible if it is a loan order. It is initialized with the order date plus a month. This date cannot be prior to the order date.

• Tax rule (field VACBPRCOD)

This information is used to indicate the tax rule for the document. This code is controlled in the tax rule table and is initialized by the corresponding code in the BP record. It can be modified.
This information is mandatory and remains accessible provided the delivery has not been confirmed.
Only a tax rule with a legislation and group that are consistent with those of the document can be entered.
The general principles linked to the multi-legislation setup are detailed here.

• Currency (field CURCOD)

This parameter is used to define, for this entry transaction, whether the Currency code field must be:

• Hidden: the field does not appear on the entry screen but the default value is attributed to it,
• Displayed: the default value is allocated to the field and displayed but the value cannot be modified,
• Entered: the default value can be modified and when it is the case, it will be checked in the currency table.

The assigned default value is the currency code associated with the BP in the latter's record.

• Price - / +tax (field PRITYPCOD)

The value of this field (Ex-tax or Tax-incl.) is defined by the general parameter SALPRITYP - Price/Amount type (TC chapter, INV group).

When the general parameter NOTATI - Ex-tax and tax-incl. amount/price (TC chapter, INV group) is set to No you cannot modify this information.

• Entity/Use (field SSTENTCOD)

• Shipment site (field STOFCYCOD)

Shipment site By default it is initialized with the shipment site of the ship-to customer. The site must be defined with the Warehouse flag set to the value "YES".

• Delivery priority (field DLVPIOCOD)

In this field, specify the delivery priority (Normal, Urgent, Very urgent). The priority is used to classify orders during the delivery preparations.
It is initialized by the customer delivery address. It is used on the order lines by default where it can be modified if the delivery method for the order is not Complete. If you modify this information and order lines already exist, the system will suggest that you apply this modification to the order lines.
This information is used in the automatic allocation processing of orders to determine the priority of the orders.

The order lines applying to non-deliverable products are not impacted by this information.

• Electronic signature (field ELESGNCOD)

• Requested delivery date (field DEMDLVCOD)

The requested delivery date corresponds to the date requested by the customer. It is initialized by the shipment date (itself initialized by the order date) increased by the delivery lead time associated with the delivery address. This date is recovered by default on the order lines when products are deliverable products. If this date is modified, it will be used to recalculate the shipment date. If the order contains lines, a message suggests that you update the requested delivery date and the maximum delivery date (if the entered date is greater) and the new shipment date on the order lines.

A control is applied to this date based on the ship-to customer's working days and their unavailability calendar. If the requested delivery date corresponds to a non-working day for the customer, the date will be automatically moved to a date that is later than the initial date. If the requested delivery date corresponds to a day that falls into the unavailability calendar of the customer, then a warning message is displayed suggesting that you modify the date or continue.

Inter-company specificities: In the case of an inter-company or inter-site order generated from a purchase order, the requested delivery date will be initialized to the earliest date in the planned receipt dates entered on the purchase order lines.

• Delivery LT in days (field DAYLTICOD)

The delivery lead time is initialized by default:

• according to the ship-to customer record (in the case of a direct shipment)
• or by the lead time entered on the order. The latter can be modified and is used to recalculate the 'delivery date' with respect to the 'shipment date'.

• Shipment date (field SHIDATCOD)

The shipment date is initialized to the order date or the current date (if the order date is earlier than the current date). This date is controlled with respect the working days at the shipment site and with respect to the unavailability calendar for this site. If the calculated shipment date corresponds to a non-working day at the site, then the system will move the shipment date (earlier) to the first working day. If the date corresponds to an unavailable day at the site, a blocking control is used to make the user enter a new shipment date.

A warning message can also be returned when the shipment date entered is greater than the requested delivery date.

Modification of the shipment date never updates the requested delivery date.

• Exp. delivery time (field DEMDLVHCOD)

For this entry transaction, specify if the expected delivery time must be:

Hidden

The field is not displayed on the entry screen.

Displayed

The field is displayed but disabled.

Entry

The field is available for entry.

• Route no. (field DRNCOD)

This code, which is controlled by a local menu, is used to generate the delivery notes according to the route code defining for example, a geographic zone. This information is defined by the customer delivery address.

• Delivery mode (field MDLCOD)

This code is used to define the information related to the transport and delivery. It is managed in the Delivery Method table. It is initialized from the ship-to customer.

• Carrier (field BPTNUMCOD)

This field indicates the code that identifies the Carrier liable for the transportation of the goods.

• Incoterm (field EECICTCOD)

This setup is used to define, for this entry transaction, whether the Incoterm code field must be:

• hidden: the field does not appear in the entry screen but a default value is assigned to it.
• displayed: The default value is assigned to the field and displayed but the value cannot be modified.
• entered: the default value can be modified and when it is the case, it will be checked in the currency table no. 5.

The access to the freight terms code and city/town is also carried out via the menu Options / Customs information.

 The assigned default value is the Incoterm code associated with the ship-to customer in its record.

• Close unfilled lines (field ORDCLECOD)

This information, initialized by the sold-to customer, is used to authorize or not the closure of a line or the order. This information is modifiable on order entry if the transaction allows it.

• One order per delivery (field ODLCOD)

This information, initialised by the sold-to customer, is used to prohibit the grouping of several orders in the same shipment. This information is modifiable on order entry if the transaction allows it.

• Partial delivery (field DMECOD)

These options are initialized by the sold-to customer to specify how the order is shipped. There are three possible values:

• Authorized means that the order can be partially shipped. 
• Full delivery line means that the order can be partially shipped if the whole line is shipped.
• Full order line means that the whole order must be shipped (a single delivery). 

This also means that a partial allocation cannot be performed on an order line or order if the stock is insufficient to cover the full line or order: the Allocate partially option must be displayed on the order or in the mass allocation options. When entering the quantity to be allocated to the line or when performing a Manual allocation on the line, a warning message displays if the delivery is partial.

Note: When you select Full delivery line or Full order line, you can ignore this warning message and force the partial delivery.

• Allocation type (field ALLTYPCOD)

The allocation type (global/detailed) is initialized to the value of general parameter ALLTYP - Allocation type (VEN chapter, SAL group). It can be modified depending on the entry transaction used. The allocation type specified in this tab serves as the default value for the order lines created later.

This information can no longer be modified once the order has allocations.

The global allocation reserves the goods without distinction by applying a global total, whilst the detailed allocation reserves specific stock objects (lot, serial number...). An order can be allocated from the order (entry of the quantity to be allocated or using the Actions icon of the line to select stock lines in detailed allocation or using the allocation button) or from the Automatic allocation or Allocation by product functions.

• Invoicing mode (field IMECOD)

This information is initialized by the sold-to customer and is used to define the customer's invoicing mode. This invoicing mode is used subsequently to invoice the delivery notes or the direct invoicing orders by regrouping or splitting them. This information is used in the automatic invoicing processes and in the manual invoicing function (where a check is performed with respect to this information).

The available invoicing modes and their impact on the delivery invoicing are as follows:

• 1 invoice / DN: This invoicing mode requires the existence of a separate invoice for each delivery created.
• 1 invoice / completed order: This invoicing mode only authorizes the invoicing of the deliveries associated with an order if said order is completed and all the invoices associated with this order are validated and all the deliveries belong to the automatic invoicing selection. A single invoice will then be generated grouping all the deliveries for the order.
• 1 invoice / order: This invoicing mode is used to create an invoice for all the deliveries of the order that are validated when the invoicing process is run. A single invoice will be generated grouping all these deliveries.
• 1 invoice / ship-to customer: This invoicing mode is used to create an invoice for all the deliveries concerning the same ship-to customer on a single invoice when the automatic invoicing process is run. There also is a check performed upon manual invoicing of the deliveries.
• 1 invoice / period: This invoicing mode is used to create an invoice for all the deliveries based on the invoicing frequency defined by the customer. For instance, if the frequency is weekly, all the deliveries during week 32 (relating to the shipment date or delivery date based on the INVREFDAT parameter) are grouped on a single invoice. There is a specific feature linked to the invoicing frequency when the chosen value is upon request. Deliveries with this kind of frequency will be grouped together. A check is also carried out in manual delivery invoicing mode to only enable the grouping together of deliveries with an invoicing mode by period and a manual invoicing mode.
• Manual invoice: This invoicing mode is not considered in the automatic invoicing processes. Invoicing will be manual on invoice entry.

Impact of the invoicing mode on delivery generation: orders with an invoicing mode 1 invoice/order or 1 invoice/completed order will never be grouped on a same delivery.

Beside these invoicing modes, there are pieces of information that, if varying from one delivery to the next, prohibit the grouping together of two deliveries. Please refer to the automatic delivery invoicing.

The impact of the invocing modes on the direct invoicing orders is as follows:

• 1 invoice / DN: This invoicing mode requires the existence of a separate invoice for each direct invoicing delivery. On the other hand, an order can be only partly invoiced by the automatic invoicing function from the moment that the order delivery mode is not Complete order. If the order delivery mode is Complete order, all the order lines will need to be invoiced (the stock-managed order lines will need to be allocated), otherwise the invoice will not be generated. On manual invoicing of an order of this type, there are no constraints with respect to the delivery mode, and it will be possible to draw up a partial invoice even if the delivery mode is Complete order.
• 1 invoice / completed order: This invoicing mode requires the existence of a separate invoice for each direct invoicing delivery. An order will have however to be fully handled in order to be invoiced using the automatic invoicing function. There will thus be only one invoice for this order. In manual invoicing it isn't necessary to follow this rule; it is possible to partially invoice an order of this type.
• 1 invoice / order: For the orders with direct invoicing, this invoicing mode corresponds to the invoicing mode previously described: 1 invoice / DN.
• 1 invoice / ship-to customer: This invoicing mode is used to create an invoice for all the orders with direct invoicing concerning the same ship-to customer on a single invoice when the invoicing process is run. If order lines concern various ship-to customers within a single order there will be as many invoices as there are delivery addresses on the lines. There also is a check performed upon manual invoicing of the orders.
• 1 invoice / period: This invoicing mode is used to create an invoice for all the orders based on the invoicing frequency defined by the customer. For instance, if the frequency is weekly, all the orders during week 32 (relating to the requested delivery date in the order header) are grouped on a single invoice. There is a specific feature linked to the invoicing frequency when the chosen value is upon request. The orders with this kind of frequency will be grouped together.
• Manual invoice: This invoicing mode is not considered in the automatic invoicing processes. Invoicing will be manual on invoice entry.

Beside these invoicing modes, there are pieces of information that, if varying from one order to the next, prohibit the grouping together of two deliveries. Please refer to the automatic order invoicing.

• Invoicing term (field INVCNDCOD)

For this entry transaction, specify if the invoicing term and start date of open items must be:

Hidden

The fields are not displayed on the entry screen.

Displayed

The fields are displayed but cannot be modified.

Entered

The fields can be entered.

• Payment term (field PTECOD)

Code of the payment condition. This code defined the payment code as well as the distribution rules of the various prepayments and open items.
It is initialized by the bill-to BP and controlled in the table of payment conditions.
Only a payment method consistent with the legislation and company group of the document site can be entered.
The general principles linked to the multi-legislation setup are detailed here.

It is possible to simulate a distribution using the button [Simul]. As far as order management goes, in creation mode the prepayments corresponding to the payment condition are automatically created. The 'payment condition' code can be modified as long as no prepayment request has been made and the order has not been invoiced. The modification leads to the deletion of existing prepayments and then to the creation of prepayments linked to the new payment condition.

• Settlement discount (field DEPCOD)

Parameter used to define, for this entry transaction, if the discount must be:

• Hidden:
  The field does not appear on the entry screen but it is assigned a default value.
• Displayed:
  The default value is assigned to the field and displayed but the value cannot be modified.
• Entered:
  The default value is assigned to the field and displayed. It can be modified.

• No. of fixed columns (field NBRCOL)

The first N columns specified in this field remain visible on the screen when scrolling.

• Translated description (field ITMDESCOD)

This is the product description translated into the customer language. This description is the one that will be printed on the document. If the translation does not exist in the customer language, the un-translated product description is used. This description is also transferred to the next document.

The product record can be accessed from this field using a tunnel.

• field ITMDESSCR

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Standard description (field ITMDES1COD)

This is the description entered on the product record. This description is transferred from the sales invoice to the purchase invoice in case of inter-company invoicing. When the invoice stems from another document, the standard description is inherited from the source line.

• field ITMDES1SCR

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Major version (field ECCCOD)

Use this parameter to define, for this entry transaction, whether the Major version number is displayed. You can set this field to one of the following values:

• Hidden:
  The Major version field is not displayed on the entry screen
• Displayed
  The version number is loaded automatically if the product is version managed. It cannot be modified.
• Entered
  The version number can be entered. The version number is loaded automatically if the product is version managed but can be modified.

• field ECCSCR

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Minor version (field ECCCODMIN)

Use this parameter to define, for this entry transaction, whether the Minor version number is displayed. You can set this field to one of the following values:

• Hidden
  The Minor version field is not displayed on the entry screen.
  The minor version is always hidden if the major version is hidden.
• Displayed
  The version number is loaded automatically if the product is version managed. It cannot be modified.
• Entered
  The version number can be entered. The version number is loaded automatically when the product is version managed but it can be modified.
  The Minor version parameter can only have the 'Entered' value when the Major version also has the 'Entered' value.

• field ECCSCRMIN

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Sales unit (field SAUCOD)

The sales unit is initialized by the sales unit defined in the Product-customer record, if it exists, otherwise it will be initialized by the sales unit of the product. It is possible to enter another unit using a selection window. The units proposed other than those mentioned previously, are the packing units for the product and the packing units defined in the "Product-customer" record. When necessary and if the user has the appropriate authorizations, it is possible to access the units table.

Once the line is entered, it is no longer possible to modify the sales unit. It is necessary to delete the line and to recreate it to modify the unit.

• field SAUSCR

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• SAL-STK conversion (field SAUCOECOD)

This is the conversion factor between the sales unit and the stock unit. This coefficient can be modified in certain cases. It can be edited if the sales unit of the product has been specified as 'editable', or if the chosen packing unit has also been specified as 'Editable' (See Product record). It cannot be edited if the unit used is a unit defined for the customer. If units are used where the factor is modifiable, it is necessary to define for the product concerned, only prices expressed in stock unit. In addition, if a basic price list has been defined for the sales unit, the modification of the conversion factor for the sales unit does not trigger a recalculation of the unit gross price.

 Once the line entered, it is no longer possible to modify the conversion factor. The line must be deleted and recreated so as to modify the factor.

• field SAUCOESCR

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Allocate/Deliver qty. (field WALLQTYCOD)

Quantity that you want to allocate to the order line.

When the transaction authorizes it, you can enter the quantity to allocate on the order line. This quantity is always equal to the quantity already allocated to the order line (Allocated quantity + Shortage quantity). To increase or decrease the quantity to be allocated, simply increase or decrease this quantity. If the INIALLORD - Init qty to allocate to order parameter (VEN chapter, SAL group) has the value Yes, the quantity to be allocated will always be initialized by the total quantity that must be allocated to the order line (if the ordered quantity for the order must be modified, the quantity to be allocated will then be automatically recalculated).

The quantity entered can be greater than the ordered quantity. A warning message will identify this (this quantity will be shipped). The allocation will be carried out during the saving of the order.

If customer reservations exist on this product and if the USERERBPC - Include customer allocations parameter (VEN chapter, SAL group) is set to Yes, reservations made by the customer are automatically consumed during the allocation process.

If the customer credit is blocked, this field will not be available. You cannot allocate an order when the customer credit is blocked (except if the order has been unlocked manually).

If the customer has exceeded their credit, a warning message will ask for entry confirmation if the SCDTUNL - Order unblocking authorization user parameter allows it, otherwise the information will not be available.

If the order status is Pre-payment not made, a warning message requests the confirmation of the entry.

During the entry of the quantity to be allocated, a warning message will systematically be displayed if shortage quantities already exist in other discussions for the product currently being processed.

In the specific case of order lines generated by back-to-back order on receipt or back-to-back production order. When the order line is associated with this type of back-to-back order, the automatic allocation processes do not allow the allocation of this type of line. In fact, the order line will be automatically allocated at the time of the associated purchase order receipt or at the moment of the production reporting for the associated production order. To manage unexpected events (production delay or supplier shipment...) you will still be able to manually allocate (or de-allocate) these lines if the stock is available. This type of allocation never generates shortages irrespective of the value of the GENSHT - Shortage generation parameter (STO chapter, MIS group). You can enter a quantity to be allocated in the order line linked to a back-to-back order even if the back-to-back order has been generated (at the time of the back-to-back generation, if the line is partially allocated, the quantity calculated for the back-to-back order will be equal to the ordered quantity - allocated quantity). During the production reporting or at the time of the purchase order receipt, if the quantity remaining to be allocated in the order is less than the quantity booked into stock, only the part remaining to be allocated will be allocated, the balance of the goods will be booked to stock in the same way as all stock receipts and will be available for the other orders.

It will never be possible to allocate an order line managed with direct orders. In effect, stock never transits by the site in this case.

From this field several different functions are accessible :

• Stock by site. This function is used to access the Stock inquiry at the shipping site.
• Allocations filter This option can be used to specify the information that will be used by the detailed allocation or at the time of shipment if the line has Global allocation. Two exclusive filters can be entered: the lot and a combination of statuses (the combination of statuses entered must be included in the Issue rule associated to the delivery transaction). A preferential filter can be assigned to a location that is used to orientate the allocation. You can also use wildcards (* , ?) for this data in order to extend filters.
• Allocation detail. This function is only available if allocated quantities already exists in the order. This function is used to view the stock lines that have been reserved. See Allocation detail that can be accessed from the Actions icon on the line.
• Available stock This function is used to access the Stock available on a date inquiry.

• field WALLQTYSCR

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Gross price (field GROPRICOD)

Help common to the Order and Buyer plan functions.

Use this field to determine the gross and excluding tax unit price of the product. This price is expressed in order unit if the Unit field is declared as accessible at the time of entry in the transaction, if not, it is expressed in purchase unit.

When the main information for the line has been given, a price list search process is automatically carried out. The objective of this search is to recover:

• The gross price and the associated reason.
  If the order (or purchase) unit is different from that of the price list line:
  - The price list amount is converted if the value of the Unit conversion is set to 'Yes' at the Pricing parameters level. This conversion is based on the unit conversion coefficient table. If no conversion is set up between these units, the price list amounts are those that are considered by applying a 1 conversion rate.
  - The price list is not used if the value of the Unit conversion is set to 'No' at the Pricing parameters level The value of the gross price is set to '0'.
• The charges and discounts in percentages or in amounts to be applied to the line level as well as the associated reasons.

When the entered price is null, a message appears to request confirmation from the user.

In the Price field, you can use the Actions icon to:

• View and modify the Discount and Cost fields defined using the structure code associated with the supplier. The values contained in these fields come from the price list search and can be modified if the associated reason allows it.
• View the reasons associated with the price as well as the different discounts and charges fields
• View the price lists
• Re-initialize the price, as well as the discounts and costs, by requesting a new price list search.

The entry of other data on the line depends on the selected transaction. This is the case for example for the Site information, Quality control code, etc.

Inter-company specificities: Within the framework of an inter-site or inter-company order, if the inter-company price lists have been set up, they will be used in the same way as normal price lists. When the sales order is generated, the prices and the discounts calculated for the reciprocal sales order will be determined from the inter-company price lists or the normal price lists. In no case will the prices and discounts entered in the purchase order be transferred to the sales order. The prices between the sales and purchasing documents can change independently. The reconciliation is made at the time of invoicing.

• field GROPRISCR

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Cost price (field CPRPRICOD)

The 'cost price' is loaded by default by the valuation of the product chosen for the margin calculation (see the valuation methods defined for the Product-Site record) at the time of the creation of the document line and is expressed in sales unit. The various possible choices for the cost price valuation are: Standard price, Revised standard price, Last price, Weighed average price, FIFO price, Lot average price and LIFO price. If the valuation method happened to return a zero value, a default value is used by specifying another valuation method contained in the list previously described. This value is stored in the "document" line.

It is possible to pre-load this information as a function of the document transaction used. Still, during the following events, the entered value is systematically replaced by the value that comes from the setup of the valuation method for the product, except if this setup determines a null value (in which case the change is saved.)

• turning a quote into an order,
• delivering an order, 
• validating a delivery,
• invoicing an order. The cost price is fixed when invoicing a delivery

In quote management, the 'lot average price' always returns a null value. A default value is used. During the delivery validation, the 'Lot average price' is used to recalculate the margin and obtain a real margin depending on the shipped lot(s).

• field CPRPRISCR

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Tax level (field VACITMCOD)

This field indicates the tax level applied to the selected product.
The tax level, when crossed with the document tax rule, is used to determine the tax rate to be applied on the document line.

There are several tax levels for a document line:

• The first level is mandatory. It corresponds to the VAT,
• The two other levels correspond to additional or special taxes which may:
• be liable to VAT,
• be applied on ex-tax basis or other valuated formula.

The tax levels for the document line will be loaded by default with the values associated with the product record ("Accounting" tab).
These values can be modified depending on the transaction.
Provided the user has the corresponding authorizations, he can access the tax level management.

• field VACITMSCR

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Invoicing term (field INVCNDCODD)

The invoicing term loaded is the one of the document header.
For this entry transaction, specify if the invoicing term on the document line must be:

Hidden

The field is not displayed on the entry screen.

Displayed

The field is displayed but disabled.

Entered

The field is available for entry.

• field INVCNDSCRD

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Rep commission rate (field REPCODD)

The sales reps on the document line are initialized by the sales reps entered in the document header. If the latter are not entered, the sales reps in the line are initialized by the sales reps for the customer, by those for the ship-to customer if there are no sales reps in the customer record.

If the parameter LINREP - Sales rep on detail allows it (chapter VEN, group MIS), the sales reps can be modified on the document line. It is possible, based on the user's authorizations, to access the sales representative record.

• field REPSCRD

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Requested delivery date (field DEMDLVCODD)

This is the delivery date requested by the customer. This date is initially by the requested delivery date entered in the order header. The modification of this date will trigger the recalculation of the shipment date (Shipment date = Requested delivery date - Delivery lead-time) and will recalculate the planned delivery date (Planned delivery date = Shipment date + Delivery lead-time).

During the modification of this date, the system controls that this date does not correspond to a non-working day or an unavailable day for the shipment date. If this is a non-working day, the date will automatically be moved to a later date, in the other case a warning message is displayed.

Special features linked to the inter-company : In the case of an inter-company or inter-site order generated from a purchase order, the requested delivery date will be initialised by the planned receipt date entered in the purchase order line.

• field DEMDLVSCRD

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Delivery LT detail (field DAYLTICODD)

Delivery date. This is the delivery lead-time in number of days associated with the ship-to customer. It is initialized by the lead-time entered in the header. It is modifiable and it is used to calculate the shipment date and/or the planned delivery date.

• field DAYLTISCRD

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Shipment date (field SHIDATCODD)

The shipment date of the order line is calculated as follows:

Request delivery date - Delivery lead time

A control checks that the calculated date corresponds to a working day and that it does not belong to an unavailability period of the shipment site:

• If the date is a non-working day, it is shifted backward (e.g. moved to Friday if it falls on a Saturday, which is not a working day).
• If it belongs to an unavailability period, the following error message will be displayed: "Non available period from 99/99/99 to 99/99/99".

You can then pick the date of your choice.

This date is used to calculate the planned delivery date: Shipment date + Delivery lead time

• field SHIDATSCRD

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Expected delivery date (field EXTDLVCOD)

This is the delivery date calculated by the system taking into account the shipment date and delivery lead-time.  If the planned delivery date is modified, the system will suggest that the user modifies the shipment date as a function of the delivery lead-time.

During the modification of this date, the system controls that this date does not correspond to a non-working day or an unavailable day for the shipment date. If this is a non-working day, the date is postponed, otherwise a warning message is displayed.

• field EXTDLVSCR

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Consumer sales price (field BPCSALPRIC)

For this entry transaction, specify if the consumer price must be:

Hidden

The field is not displayed on the entry screen.

Displayed

The field is displayed but disabled.

Entry

The field is available for entry.

• field BPCSALPRIS

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Use-by date (field USELIMDCOD)

For this entry transaction, specify if the use-by date must be:

Hidden

The field is not displayed on the entry screen.

Displayed

The field is displayed but disabled.

Entry

The field is available for entry.

• field USELIMDSCR

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Delivery address (field BPAADDCODD)

Delivery address
It is initialized to the delivery address contained in the order header.
It is modifiable if the address management site parameter for the line is set to 'yes' and if partial deliveries are authorized for the order. In this case, the address is controlled in the ship-to customer table.
Its modification causes the realignment of the lead-time, priority, delivery method and carrier. If the lead-time is modified, the dates are recalculated.

• field BPAADDSCRD

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Delivery contact (field CNDNAMCOD)

This is the name of the contact associated with the delivery address. If the delivery address corresponds to the delivery address in the document header, the contract proposed by default in the line will be the contact entered in the delivery address in the header. If the delivery address does not match the delivery address mentioned in the document header, then the contact proposed by default will be the business partner default contact if it corresponds to this delivery address, otherwise the system will propose the first contact of this address by alphabetical order on the contact code.

The contextual button is used to select another contact if required.

• field CNDNAMSCR

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Location reference (field USEPLCCOD)

Use this field to specify the consumption place for the carrier or to define an address complement.

Examples: Dock xx or Hall yy.

The place of consumption is written on the order document.

Inter-company specificities: for inter-company or inter-site orders, the consumption location is transferred to the generated sales order line.

• field USEPLCSCR

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Shipment site (field STOFCYCODD)

Shipment site. It is initialized with the shipment site of the document header. The shipment site is modifiable. In the orders, this information is modifiable as long as there is no allocation on the line. Moreover it is only modifiable if partial shipment is authorized. The product reference associated with this site must exist in the product-site table if the product is managed in stock. The site must be defined with the Warehouse flag set to the value "YES".

• field STOFCYSCRD

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Delivery priority (field DLVPIOCODD)

In this field, specify the delivery priority (Normal, Urgent, Very urgent). The priority is used to classify orders during the delivery preparations.
It is initialized by the customer delivery address. It is used on the order lines by default where it can be modified if the delivery method for the order is not Complete. If you modify this information and order lines already exist, the system will suggest that you apply this modification to the order lines.
This information is used in the automatic allocation processing of orders to determine the priority of the orders.

The order lines applying to non-deliverable products are not impacted by this information.

• field DLVPIOSCRD

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Route no. detail (field DRNCODD)

This code, which is controlled by a local menu, is used to generate the delivery notes according to the route code defining for example, a geographic zone. This information is defined by the customer delivery address.

• field DRNSCRD

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Delivery mode (field MDLCODD)

Code checked in the Delivery modes table, and used to define the information related to the transport and delivery.

• field MDLSCRD

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Carrier detail (field BPTNUMCODD)

This field indicates the code that identifies the Carrier liable for the transportation of the goods.

• field BPTNUMSCRD

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Preparation code (field PRECODCOD)

This field includes the preparation code. You can select this code from the Actions icon or enter it if it has not been set up.

• field PRECODSCR

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Packaging/Capacity (field PCKCOD)

This code is controlled in the packaging table and initialized by default by the corresponding code from the product-site record. 
It indicates the number of products, expressed in sales units, that the package can contain. The packaging code comes from the Product-Site record depending on the sales unit chosen. In the case of a line creation, if the unit chosen does not correspond to the sales unit of the product or to the customer sales unit, the packaging code and the capacity are not initialized. In this case, it is then necessary to manually enter them. This information remains modifiable and is used upon preparation or shipment of the product to carry out the packaging.
Upon declared packing, this code is specified only if it is present in the original document Deliveries or Picking tickets.
If granted the proper authorizations, the user can access the packaging record.

• field PCKSCR

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Order type (field DEMSTACOD)

This indicator is used to define the status of the order line that can be Firm or Planned. The Planned status is used to anticipate the firm orders to come because this information is used in terms of the requirements in the MRP calculation. This indicator is no longer modifiable once the order line has been allocated, shipped or invoiced. It is not modifiable if the line is managed by back-to-back order.

If the order line has the status Firm (default value), there is the possibility to allocate it and ship it. Conversely, if the order line has the status Planned, it can be neither allocated nor shipped (it will be necessary to manually modify its status to pass to Firm).

• field DEMSTASCR

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Product source (field FMICOD)

The method used for the delivery makes it possible to choose how to cover the need expresses by the order line. This need can be covered by the stock, a receipt direct order, a direct order or a production direct order.

Based on the parameterization of the product record (Sales tab), this field will be initialized in the following way:

• If the product is not managed with direct orders, the delivery method will be initialized to the value On stock. It is then possible to directly ship the order line from the available stock.
• If the product is managed with direct order, the direct order proposed by default depends on the category of the product.

Thus, if a product belongs to the category Purchased, and not to the category Manufactured, the direct order proposed by default will be a receipt direct order, except if the Direct quantity (Sales tab in the product record) is loaded, in which case the direct order type proposed by default will be a direct order if the ordered quantity is greater than or equal to the direct quantity.

In the same way, if a product belongs to the Manufactured category, but not to the Purchased category, the back-to-back proposed by default will be a production back-to-back order.

If the product belongs both to the Manufactured and Purchased categories, the type of direct order proposed will depend on the Reorder suggestion type specified on the Product//Site record (Planning tab). If the suggestion is of type Purchase, the direct order proposed will be a purchase direct order. If the suggestion is of type Manufacture, the direct order proposed will be a production direct order.

It is possible to select another delivery method to the one initialized by default, provided it is compatible with the product management and the order line is not allocated or a direct order has not been generated.

• field FMISCR

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Allocation type (field ALLTYPCODD)

The allocation type for an order line has as its default value the allocation type defined in the order header. It is however possible to modify the allocation type (Global/Detailed) in the line on the condition that the selected order transaction authorises it. A global allocation is carried out as a function of the total stock available. A detailed allocation reserved the stock objects (Lot - Serial number - Status - Location).

If the order line is allocated, this information is no longer accessible.

• field ALLTYPSCRD

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Project (field PJTCODD)

This parameter is used to define, for this entry transaction, whether the Project field must be:

• Hidden :
  The field is not displayed on the entry screen.
• Displayed :
  The field is displayed and cannot be modified.
• Entered: :
  The field is displayed but can be modified.
  The control on the entered value is based on the CTLOPPCOD - Mandatory project code parameter (TC chapter, MIS group).

Even if this setup makes this project code available for entry, entering the field is prohibited when a single-project management of documents is used (parameter PJTSNGDOC - One project per document set to Yes): in this case, the project code of the line automatically takes the value of the header code.

• field PJTSCRD

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Exp. delivery time (field DEMDLVLCOD)

For this entry transaction, specify if the expected delivery time must be:

Hidden

The field is not displayed on the entry screen.

Displayed

The field is displayed but disabled.

Entry

The field is available for entry.

• field DEMDLVLSCR

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Max delivery time (field MAXDLVHCOD)

For this entry transaction, specify if maximum delivery time must be:

Hidden

The field is not displayed on the entry screen.

Displayed

The field is displayed but disabled.

Entry

The field is available for entry.

• field MAXDLVHSCR

• Max delivery date (field MAXDLVDCOD)

For this entry transaction, specify if the maximum delivery date must be:

Hidden

The field is not displayed on the entry screen.

Displayed

The field is displayed but disabled.

Entry

The field is available for entry.

• field MAXDLVDSCR

• Discount/Charge 1 (field DISCRGCOD1)

Discounts and charges columns are displayed.
They depend on the setup of the Price list structure code associated with the supplier in the supplier record (see documentation Price list structure).

They can be initialized by the use of the price lists (see the Price list setups and Price list entry documentations). Access to these columns can depend on the setups of the reasons associated with the price lists as well as the value of the reason given to the UPDPRISAL setup for Sales and to the UPDPRIPUR setup for Purchase.

These discounts or charges are defined in amount or in percentage and they are applied with a totaling or cascading method to the gross price to determine the net price of the document line.

The contextual button is used to:

• view the reasons associated with the price as well as the different discounts and charges fields,
• modify, if necessary, the reasons allocated to each column.

• field DISCRGSCR1

Setup used to define, for this entry transaction, if the field must be present in:

• Form + Table mode,
• Form mode,
• Table mode.

• Discount/Charge 2 (field DISCRGCOD2)

• field DISCRGSCR2

• Discount/Charge 3 (field DISCRGCOD3)

• field DISCRGSCR3

• Discount/Charge 4 (field DISCRGCOD4)

• field DISCRGSCR4

• Discount/Charge 5 (field DISCRGCOD5)

• field DISCRGSCR5

• Discount/Charge 6 (field DISCRGCOD6)

• field DISCRGSCR6

• Discount/Charge 7 (field DISCRGCOD7)

• field DISCRGSCR7

• Discount/Charge 8 (field DISCRGCOD8)

• field DISCRGSCR8

• Discount/Charge 9 (field DISCRGCOD9)

• field DISCRGSCR9

• Header dimensions (field HEACCECOD)

Parameter used to define if, for this transaction, the analytical dimensions fields of the document header must be:

• Hidden: The options/analytical dimensions menu of the main window will be hidden.
• Displayed: It will be possible to access the options/analytical dimensions menu of the main window, the fields will appear but it will not be possible to access them.
• Entered: It will be possible to access the options/analytical dimensions menu of the main window, the fields will appear and it will be possible to access them.

• Distribution line (field DSPCOD)

This setup is used to define, for this entry transaction, if the analytical distribution key at line and invoicing element level must be:

• Hidden: the field does not appear on the entry screen but the default value is attributed to it,
• Displayed: The default value is assigned to the field and displayed but the value cannot be modified.
• Entry: The default value is assigned to the field and displayed. It can be modified.

• field DSPSCR

Parameter used to define, for this entry transaction, if the field must be present in:

• Record + Table modes,
• Record mode,
• Table mode.

• Stock movement dimensions (field STOCCECOD)

Specify for this transaction if the analytical dimension fields related to stock movements must be:

• Hidden
• Displayed: The menu Analytical sections, accessible from the menu in the movement detail window, will be available. The fields are displayed but cannot be accessed.
• Entered: The Analytical dimensions menu, accessible from the menu in the movement detail window, will be available. The fields are displayed and can be accessed.

• Input (field CCESCR)

• Dimension type (field DIE)

You can enter an analytical dimension type code on each table line.
Use the function available from the Actions icon to preload all the dimension types defined for the sites of a given group of sites.

• Method (field CCECOD)

Parameter used to define, for this entry transaction, if the analytical dimension must be:

• Hidden: The field is not displayed in the entry screen. However, it is possible to initialize this field with a default section code.
  
• Displayed: The default value is assigned to the field and displayed but the value is non-modifiable.
  
• Entered: The default value is assigned to the field and displayed. It can be modified, and, in that case, the entered value is checked in the analytical dimension table.
  The default value assigned to the analytical dimension is based on the dimension setup performed.