Shipments
Use this function to manage the settings for the customization of the delivery entry screens.
A standard shipment entry transaction is initialized upon software installation. It can be modified or deleted using this option, which can also be used to create new ones.
You can set up several transactions for deliveries. Each transaction, identified by a code and a text description, appears in a selection window when calling the Deliveries function.
Prerequisite
Refer to documentation Implementation
Screen management
Header
The transaction header allows the user to create new transaction codes or to look for existing transactions to be modified or deleted.
Delivery transaction
| 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 on the document header and fields entered in the lines, whether they must be:
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 on this setup header.
|
| Description (field DESAXX) |
|
Transaction description. |
| Active (field ENAFLG) |
|
Use this field to activate or deactivate a transaction. |
| Access code (field ACSCOD) |
|
This access code is used to restrict access to data by user or group of users. |
| Group (field GFY) |
|
The group of companies or sites entered here is used to filter the records. |
Tab Setup Definitions
In this tab, define several elements, such as the automatic printing of the packing slip and of the pick ticket, the display of specific fields along with the document type to be managed with this transaction.
Picking ticket
| 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. |
Packing slip
| 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. Note:
The automatic printing only takes place in creation mode. |
Miscellaneous
| Delivery category (field DLVTYP) | ||||||||||||
|
In this field, specify the delivery category. When creating a delivery by picking orders, the selection lists available in the selection panel depend on the transaction delivery category:
|
||||||||||||
|
||||||||||||
|
This parameter is used to define, for this transaction, a default transaction group code. |
||||||||||||
|
||||||||||||
|
The presence or absence of this option is subject to the activity code WRH.
Note:
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. |
||||||||||||
|
||||||||||||
|
The presence of this check box is subject to the WRH activity code.
|
Invoicing elements
| Elements (field INVDTACOD) |
|
This table contains the document invoicing elements (quote, order, shipment, invoice). |
Stock
| 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. |
| Automatic journal (field ENTCOD) |
|
This field is used for this transaction to specify the code of the accounting automatic journal used to generate, via the stock accounting interface, the accounting entries with respect to the stock movements created with this transaction. |
Stock issue
Packing
| Packing type (field PKGTYP) |
| Transaction (field PKTNUM) |
Tab Display
From this tab, select the columns that will be displayed on the packing slip.
Header
Line
Tab Header
In this tab, specify the management mode of specific sections in your entry screen on the delivery header.
Entry
| 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:
|
| 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 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:
Note:
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. 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. |
| 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:
The access to the freight terms code and city/town is also carried out via the menu Options / Customs information. Note:
The assigned default value is the Incoterm code associated with the ship-to customer in its record. |
| Bill of lading (field BOLCOD) |
|
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 (progressive) number will display on the delivery. |
Entry
| Payment term (field PTECOD) |
|
Payment condition code. This code defines the payment code and the distribution rules of the various pre-payments and open items. It is possible to simulate a distribution thanks to the "Simulation" button. In order management, creation mode, the pre-payments corresponding to the payment condition are automatically created. The 'payment terms' code can be modified as long as no pre-payment has been made and the order has not been invoiced. Such a modification would then trigger the deletion of the already existing pre-payments followed by the creation of the pre-payments related to the new payment condition. |
| Settlement discount (field DEPCOD) |
|
Parameter used to define, for this entry transaction, if the discount must be:
|
| 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. |
| 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. |
| 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. Statistical information used in the stock transactions associated with the shipment. This value is fixed if the original document does not reference a movement group. Otherwise, the movement group of the document at the origin of the quality control is suggested in priority. |
| 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) |
Tab Line 1
In this tab, specify the management mode for particular sections in the entry screen at the level of each delivery line by deciding for each of the submitted section whether they should be hidden, displayed or entered according to the same principles as for the sections set up at delivery header level.
Product lines grid
| No. of fixed columns (field NBRCOL) |
|
The first N columns specified in this field remain visible on the screen when scrolling. |
Entry
| 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. Note:
The product record can be accessed from this field using a tunnel. |
| field ITMDESSCR |
|
Specify, for this entry transaction, if the field must be present in:
|
| 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 |
|
Specify, for this entry transaction, if the field must be present in:
|
| Major version (field ECCCOD) |
|
Use this field to control entry or modification of the Major version number for a product. You can set this field to one of the following values:
|
| field ECCSCR |
|
Specify, for this entry transaction, if the field must be present in:
|
| Minor version (field ECCCODMIN) |
|
Use this field to control entry or modification of the Minor version number for a product. You can set this field to one of the following values:
|
| field ECCSCRMIN |
|
Specify, for this entry transaction, if the field must be present in:
|
| Sales unit (field SAUCOD) |
|
The sales unit is initialized by the sales unit defined in the Product-customer record, if it exists, if not, it will be initialized by the sales unit of the product. Entry of another unit is possible in a selection window. The suggested units, 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 you have been granted the appropriate authorizations, you can access the units table. Once the line is entered, you can no longer modify the sales unit. You must delete the line and recreate it to be able to modify the unit. |
| field SAUSCR |
|
Specify, for this entry transaction, if the field must be present in:
|
| 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. Note:
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 |
|
Specify, for this entry transaction, if the field must be present in:
|
| 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:
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:
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 |
|
Specify, for this entry transaction, if the field must be present in:
|
| Cost price (field CPRPRICOD) |
|
The 'cost price' is populated by default with 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 preload this information according to the document transaction used. Still, during the following events, the entered value is systematically replaced by the value originating 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):
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 |
|
Specify, for this entry transaction, if the field must be present in:
|
| Tax level (field VACITMCOD) |
|
This field indicates the tax level applied to the selected product. There are several tax levels for a document line:
The tax levels for the document line will be loaded by default with the values associated with the product record ("Accounting" tab). |
| field VACITMSCR |
|
Specify, for this entry transaction, if the field must be present in:
|
| Packaging/Capacity (field PCKCOD) |
|
This code is controlled in the packaging table. It specifies the number of products, expressed in sales units, that the packaging can contain. It is initialized once the product has been entered, based on the sales unit used and the shipping site:
This information can be modified. This information and the packaging capacity are used upon preparation or shipment to carry out the packaging. If you are granted the proper authorizations, you can access the packaging record. |
| field PCKSCR |
|
Specify, for this entry transaction, if the field must be present in:
|
| Weight (field WEICODD) |
|
Gross weight and net weight of the line. |
| field WEISCRD |
|
Specify, for this entry transaction, if the field must be present in:
|
| 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. Note:
Inter-company specificities: for inter-company or inter-site orders, the consumption location is transferred to the generated sales order line. |
| field USEPLCSCR |
|
Specify, for this entry transaction, if the field must be present in:
|
| Project (field PJTCODD) |
|
This parameter is used to define, for this particular entry transaction, if the Project field must be:
Note:
Even if the project code can be entered using this setup, its entry is still prohibited if the document management is single-project (the PJTSNGDOC - Single-project documentparameter is set to Yes): in that case, the project code of the line automatically uses the value of the project code in the header. |
| field PJTSCRD |
Tab Line 2
In this tab, define the management mode for the 'Discounts/Charges' sections in the entry screen at the level of each contract line by deciding for each of the submitted sections whether they should be hidden, displayed or entered according to the same principles as for the sections set up at delivery header level.
Entry
| Discount/Charge 1 (field DISCRGCOD1) |
|
Help common to the Sales and Purchase modules. The displayed discount and cost columns are linked to the setup of the price lists structure code associated with the supplier in said supplier's record. Access to these columns can depend on the setup of the reasons associated with the price lists as well as the value of the reason given to the
These discounts or costs 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. From the Actions icon, you can:
|
| field DISCRGSCR1 |
|
Specify, for this entry transaction, if the field must be present in:
|
| 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 |
Tab Line 3
Entry
| 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'. |
| field LOTSCR |
|
Specify, for this entry transaction, if the field must be present in:
|
| Sublot (field SLOCOD) |
|
Indicates the sub-lot to be issued. It is not necessary to enter it in the following cases:
If the product is managed with serial numbers, only this number is necessary to determine the stock to issue. |
| field SLOSCR |
|
Specify, for this entry transaction, if the field must be present in:
|
| 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. |
| field AQRSCR |
|
Specify, for this entry transaction, if the field must be present in:
|
| 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 |
|
Specify, for this entry transaction, if the field must be present in:
|
| 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.
|
| field SERSCR |
|
Specify, for this entry transaction, if the field must be present in:
|
| Ending serial number (field SERECOD) |
|
This is the end serial number automatically calculated using the start serial number. |
| field SERESCR |
|
Specify, for this entry transaction, if the field must be present in:
|
| Identifier 1 (field IDECOD01) |
| field IDESCR01 |
|
Specify, for this entry transaction, if the field must be present in:
|
| Identifier 2 (field IDECOD02) |
| field IDESCR02 |
| Movement description (field MVTDESCOD) |
|
Enter a free description that will be registered in all the stock transactions associated with the delivery line. |
| field MVTDESSCR |
|
Specify, for this entry transaction, if the field must be present in:
|
| Warehouse (field WRHCOD1) |
|
The presence or absence of this option is subject to the activity code WRH.
|
| field WRHSCR1 |
|
Specify, for this entry transaction, if the field must be present in:
|
| Container (field LPNCOD) |
|
This field is subject to the LPN - License plate no. management activity code. For this entry transaction, specify if the container and license plate number on the document line must be:
|
| field LPNSCR |
|
Specify, for this entry transaction, if the field must be present in:
|
Tab Analytical
In this function, the Distribution line field is hidden.
Block number 1
Entry
| field CCESCR |
Grid Dimension line
| Dimension type (field DIE) |
|
You can enter an analytical dimension type code on each table line. |
| Method (field CCECOD) |
|
Parameter used to define, for this entry transaction, if the analytical dimension must be:
|
| Preloading dimensions |
|
Click the Preload dimensions action to load the default dimensions defined for a selected group of sites or companies. |
Specific Buttons
|
Copy
This button is used to copy the record definition from or to another folder. Block number 1
Block number 2
|
If the order (or purchase) unit is different from that of the price list line: