Shipments

• 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 NPRNAM)

This is the code of the picking note automatically printed at end of entry.

• Auto print (field NPRFLG)

The automatic print flag is used to automatically launch a print of the document upon entry end.

• Elements (field INVDTACOD)

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

• Document (field DOCNAM)

This is the code of the delivery note automatically printed at 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.

• Movement code (field TRSCOD)

This setup is used to define for this entry transaction a movement code used to specify rules for a specific type of movements.
These codes must be created in the miscellaneous table number 14.

• Automatic journal (field ENTCOD)

This field is used to specify, for this transaction, the code of the accounting automatic journal used to generate, via the stock accounting interface, the accounting postings along with the stock movements created with this transaction.
This field can only be accessed if the SCOIFA - Accounting interface WO in process setup is set to No.

• Delivery category (field DLVTYP)

In this field, specify the delivery category.
When directly creating a delivery, the Delivery type selection is filtered according to the specified category.

When creating a delivery by picking orders, the selection lists available in the selection panel depend on the transaction delivery category:

• Stock movement group (field TRSFAM)

This parameter is used to define, for this transaction, a default transaction group code.

• Warehouse (field WRHCOD)

The presence of this field is subject to activity code WRH.
It is used to define, for this entry transaction, whether the header warehouse must be:

• Hidden:
  The field is not displayed in the entry screen.
• Displayed:
  The field is displayed empty and cannot be modified.
• Entered:
  The field is displayed but can be modified.

 If the Single-warehouse box is checked, this field automatically takes the value Entered. It is indeed mandatory to specify the warehouse in the document header.

• Single warehouse (field WRHOBY)

The presence of this box is subject to activity code WRH.

• If this box is checked, it will be mandatory to enter the warehouse in the entry screen header. As far as the document line parameter is concerned, it cannot be defined as Entered, but only as Hidden or Displayed.
   
• If this box is not checked, the warehouse will not be a mandatory criterion of the documents. As far as the document line parameter is concerned, it will be possible to define it such that it allows them as being possible to enter, thus authorizing the management of multi-warehouse entriyelines

• Automatic determination (field STKFLG)

This setup is used to define, for this transaction, whether the stock issue must be automatically determined or must be chosen manually.
When the entry transaction only takes into account the 'Consumption areas' reorders, this flag can not be accessed. 

• Packing type (field PKGTYP)

• Transaction (field PKTNUM)

• 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 status (field STACOD)

These are the various statuses of the document linked to the delivery (PN printed, DN printed, Delivery report, Delivery invoice report).

• Invoice number (field INVNUMCOD)

Invoice number linked to the delivery.

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

• Delivery amount (field AMTCOD)

These are the various amounts of the document linked to the delivery (PN printed, DN printed, Delivery report, Delivery invoice report).

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

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

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

• Return quantity (field RTNQTYCOD)

Quantity returned for this line and updated by the return management.

• field RTNQTYSCR

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

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

• Order detail no. (field ORDCODD)

This number is initialized if the delivery is related to an order (traditional order or contract order). This information is not entered in the case of a multi-order delivery.

• field ORDSCRD

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

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

• Subcontract document no. (field VCRNUMOCOD)

Journal number at the origin of the delivery line.

This only concerns the sub-contracting deliveries.

The original journal can be a work order or a sub-contracting order.

• field VCRNUMOSCR

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 SHIDATCOD)

This field contains the delivery shipment date. It is initialized with the current date and helps determine the delivery date at the customer's.

this date will be used as posting date in the stock journal.

• Delivery lead time (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'.

• Delivery date (field DLVDATCOD)

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.

• Loan return date (field LNDRTNCOD)

The 'loan return' date is initialized by the 'loan return' date defined in the order if it is a delivery coming from an order. Otherwise, it is not initialized and must be entered manually. This date is used if required, to invoice a loan delivery from the moment the 'loan date' is exceeded and the loaned goods have still not been returned by the customer. This date must be greater than or equal to the 'delivery date'.

• Currency (field CURCOD)

This is corresponds to the currency of the order, delivery or invoice.
It is initialized by default with the bill-to customer currency and can be modified. In this case, it can only be modified in creation and duplication modes and is controlled in the currency table.

It is possible to choose the currency for the delivery transaction as well as to define (depending on the value of the 'Excl. tax and Incl. tax Prices' parameter - TC Chapter / INV/NOTATI group) if the prices are expressed excluding tax or including tax. When the delivery comes from an order, this information is automatically loaded and cannot be modified. When it is a direct delivery, this information is no longer modifiable once at least one delivery line is entered. It is inherited in this case from the invoiced customer information.

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

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

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

• Bill of lading (field BOLCOD)

Update 8.0.0 and higher:

Select this option to define whether the bill of lading fields in the Deliveries function are displayed. If the activity code KUS - USA Localization and the USABOL - Bill of Lading parameter are set to "Yes", then the SCAC (Standard Carrier Alpha Code) code and PRO number will display on the delivery.

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

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

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

• Project (field PJTCOD)

• Number of packages (field PACNBRCOD)

This concerns the total number of packages in the delivery. This information is automatically calculated by the packaging function, but can still be modified.

• Weight (field WEICOD)

Gross weight and net weight of the delivery.
This information is loaded by default with the total line weights.

• Volume (field VOLCOD)

Delivery volume.

• Registration (field LICPLATCOD)

License plate of the vehicle carrying goods.

• Trailer license plate (field TRAPLTCOD)

• Departure date (field DPEDATCOD)

• Arrival date (field ARVDATCOD)

• Departure time (field ETDCOD)

Delivery departure time.

• Arrival time (field ETACOD)

Delivery arrival time.

• Transaction group (field TRSFAMCOD)

Movement group, initialized by the movement group of the transaction being used.

• Location (field BPCLOCCOD)

This information can only be entered in case of a shipment of sub-contractor type and, in this case, it is mandatory. It corresponds to the sub-contractor location that must be reordered in case of sub-contractor shortages. This location is initialized by default by the sub-contractor location defined in the ship-to customer record, then by the location defined in the supplier record if the location is not entered in the shipment address (on the condition that the location specified in the supplier exists in the shipment site). This location can however be modified from the moment the chosen location is of the sub-contractor type and belongs to the shipment site.

• Entity/Use (field SSTENTCOD)

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

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

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

• Weight (field WEICODD)

Gross weight and net weight of the line.
This information is initialized from the unit weights of the product record.

• field WEISCRD

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.

• 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

• 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

• Lot (field LOTCOD)

If the product is managed by lot then, on manual creation of the delivery line or when the stock to be issued has not been determined, it possible to enter a lot existing in the 'shipment site'.
A selection window accessed by right click on the field is used to select a lot number. 
It is also possible to enter a lot number which does not exist in stocks.
A message then informs the user that no lot exists. This alternative is provided so it is possible to record a lot number that has never been entered even though the goods are physically available. This method can only be applied when negative stock is authorized for the product and when the delivery transaction is set up with no stock determination. In the case of a delivery transaction with stock determination, this lot is only considered if the product if in complete shortage (the detailed allocation algorithm will attempt to allocate stock first).

• field LOTSCR

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

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

• Sublot (field SLOCOD)

Indicates the sub-lot to be issued.

It is not necessary to enter it in the following cases:

• the issue is a multi-lot one
• all characteristics of the stock to be issued are not entered (lot, sub-lot, serial no., location)

If the product is managed with serial numbers, only this number is necessary to determine the stock to issue.
If this is not the case, the lot, sub-lot and location (depending on the management method for the product) are necessary.
There is no selection window for this field. The selection window is available on the lot field and makes it possible to choose the requested lot and sub-lot. When the lot is selected, the sub-lot it instantly initialized. Otherwise, it is also possible to enter a sub-lot number which does not exist. An information message will report it. Same remarks as for the lot number in this context.

• field SLOSCR

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

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

• Status (field AQRCOD)

Irrespective of the product used, there is the possibility, during manual creation of the delivery line or when the stock to be issued has not been determined, to enter a status for the stock to be issued.
A selection window accessed by right click on the field is used to select any status that has been defined.

• field AQRSCR

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

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

• Location (field LOCCOD)

If the product is managed by location at the 'shipment site' then, on manual creation of the delivery line or when the stock to be issued has not been determined, it possible to enter a location existing in the 'shipment site'. A selection window accessed by right click on the field is used to select a location.

• field LOCSCR

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

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

• Starting serial number (field SERCOD)

This field is used to enter the first serial number (Start) to issue. The last serial number (End) will be automatically calculated.

• It is not necessary to enter the start serial number when the serial numbers to issue are not in a row.
• If the product is managed with serial numbers, only this number is necessary to determine the stock to issue.
• If this is not the case, the lot, sub-lot and location (depending on the management method for the product) are necessary.

• field SERSCR

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

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

• Ending serial number (field SERECOD)

This is the end serial number automatically calculated using the start serial number.
This field is never enterable.

• field SERESCR

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

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

• Identifier 1 (field IDECOD01)

• field IDESCR01

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

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

• Identifier 2 (field IDECOD02)

• field IDESCR02

• Movement description (field MVTDESCOD)

A free description is entered in this field that will be registered in all the stock transactions associated with the shipment line.
This description is also accessible from the stock issue detail window. If it has been modified by this function, it will be automatically recovered and registered on the shipment line in this field.

• field MVTDESSCR

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

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

• Warehouse (field WRHCOD1)

The presence or absence of this option is subject to the activity code WRH.
It is used to define, for this entry transaction, whether the warehouse on the document line must be:

• Hidden: The field is not displayed. This will be single-warehouse managed.
• Displayed: The field is loaded with the warehouse entered in the header, and cannot be modified. This will be single-warehouse managed.
• Entered: The field is displayed but can be modified. This setup allows a multi-warehouse management.
  This value cannot be selected if single-warehouse management has been activated in the transaction header.

• field WRHSCR1

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

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

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