Basic parameters > Outputs > Configurations 

This table is used to set up the general management rules linked to the outputs for each depositor of a site.

Other more detailed setups are also used, such as the DO preparation mode, the output mode of the product or the storage type of the location.

Prerequisite

SEEREFERTTO Refer to documentation Implementation

Screen management

To create the output configuration, a depositor must be selected, then the tabs dedicated to each flow must be completed.

Header

Presentation

Entry of the depositor code.

Close

 

Fields

The following fields are present on this tab :

Code representing the depositor. In logistics terms, the concept of depositor makes it possible to process separate flows or traffics within the same site. It covers the notion of order giving customer for the service provisions.
After the site, the depositor is the second access key to the Product, Input and Delivery Order files.
Concerning the location, the depositor code is entered if the location is assigned to the depositor or the product, and if the location is single-depositor or single-product and it is not empty.

 

  • Description (field NAM)

 

Close

 

Tab Delivery Orders

Presentation

The setups of this tab are linked to the management of the delivery orders of the current depositor. Some values can be transferred at the level of each DO header.

Delivery note

Inter-site printing: report code of the "inter-site" DN used for the shipment of an inter-site round. The load preparation list follows this print-out if the DO preparation mode is of load preparation type. If it is not entered, the "inter-site" DN will not be printed. The "normal" DN will be the one to be printed according to the set-up of the DO header ("Transport" tab).

These setups apply to all the DOs of the depositor shipped within the framework of an "inter-site" round.

Close

 

Fields

The following fields are present on this tab :

Rules

  • Flow control (field OFLCTL)

Flow control. This parameter is linked to the parameter of the product record called "Output locking".
If it is active, when "issuing" a product whose output is locked, the system performs a control and refuses to issue the product.
If it is inactive, irrespective of the value of the "Output locking", the product output from stock can be completed.
Output controls are carried out during the following transactions:
- entry of the DO lines
- search for stock objects on output
- adjustment on deletion or quantity decrease
Transfer movements remain possible irrespective of the parameter value.

  • Output shortage management (field SHRMGT)

If the box is not checked, a DO partly covered or not covered at all is automatically closed further to the moving to status 9.
If the box is checked, all those lines that are not covered are kept in the portfolio.

A DO is fully kept (moving to status 2-Pending nth preparation) if:
- the DO is in partial or total shortage upon wave launching,
- picking orders are cancelled or partly cancelled,
- the shipment cancellation is used.

To finally close it, it then becomes necessary to go to each DO and close each one in turn.

  • Mvt in superior cntr. (field SUPCTR)

This parameter is connected with the "higher container" parameter of a picking location.
If it is checked without packing, it is used to express the output movement in the higher container set up in the location (if possible) or in one of the containers defined for the higher container of the picking location.
If it is checked with packing, the product modulo is considered and the movement is then expressed in one of the product modulos.

If it is not checked, the movement is then expressed according to the reference container of the picking location.

  • Generic round management (field GDRMGT)

If the box is not checked, the management of generic rounds is not activated. Rounds can be created without round code or with a generic round code.

If the box is checked, the management of generic rounds is activated.
The shipping rounds thus created refer then to the Generic Round table.
Then, the DOs can have the same generic round code via the customer table. Consistency checks are carried out upon creation of the generic round on the basis of the maximum values stipulated for the generic round.

  • Initialize carrier information (field CRRDFT)

If the box is checked, the DO portfolio can be accessed in the carrier calculation function.
If the box is not checked, this parameter makes it possible not to take into account the DOs of the depositor for the automatic or interactive calculation of transport information.
Upon launching of the interactive or batch calculation, the program tries to calculate a carrier and a transport mode, including for those with the shipment management set to no.

 

  • Wave initialization (field INIWAVFLG)

If checked, the depositor is taken into account when submitting an automatic wave creation recurring task.

  • Unique reference (field UNQORF)

Used to check on entry or via an interface the entry of several DO entities with the same document reference.
No. There is no checking active at DO reference level
Yes. A unicity checking of the DO reference is carried out, irrespective of the status of the existing DOs for the depositor. The checking does not take the historical basis into account.
Yes, if not closed. A DO reference can appear several times, in the portfolio, provided that the previous references have the status 9-Shipped/Closed. The checking does not take the historical basis into account.

  • Customer control (field FLGDLVCLT)

This is used to indicate the management rule applied to the data of the "ship-to customer" in a DO.

There are three possible values:

  • "No": the ship-to customer code is not mandatory in the DO. When it is not present, the customer characteristics sent by the interface are loaded. When it is present, the customer characteristics are loaded from the Geode "Customer" table and completed by the data sent by the interface.
  • "Yes": the ship-to customer code is mandatory. The customer characteristics are loaded from the Geode "Customer table only.
  • "Additional": the ship-to customer code is mandatory. The customer characteristics are loaded from the Geode "Customer" table and completed by the data sent by the interface.

Addressing priority

  • Addressing priority (field FLCPIO)

Upon wave launching, used to provide the system with the most important criterion in the choice of the DOs to be dealt with. The 2 fields "Service priority" and "Partial delivery" are 2 fields of the DO header.

Picking addressing

  • Unavailable pending input (field PCKPDI)

 

Validation

  • PO/parcel operator code (field PKOOPE)

If the box is checked, this means that an operator code is necessary to validate the pickings, the parcels (prepacking) or the SUs (prepalletization).

  • Declarative packing operator code (field DPKOPE)

If the box is checked, this means that an operator code is necessary to validate the parcels created upon DO declarative packing.

  • SU operator code (field SHPOPE)

If the box is checked, this means that an operator code is necessary to validate the palletization orders (PAO).

  • Ctrl code in output (field OUTCTL)

If the box is checked, this means that a control has been carried out to ensure that the operator has removed the stock object from the proper location. This set-up is combined with that of the store, the location and the product record.

Prints

  • Partials by product (field SSHITM)

Stipulates if the system must print the shortage report by product at the end of the wave.

  • Shortage by DO (field SSHDLO)

Stipulates if the system must print the list of shortages by DO at the end of the wave.

  • Preparation load (field WAVSTT)

Stipulates if the system must print the list of the preparation loads at the end of the wave.

  • Temporary DN (field TDN)

If the box is checked, the temporary DN is systematically created and printed upon wave launching. The DN no. is assigned to the output movements.
Upon shipment, the DN no. of the deferred movements is reset to zero and a new DN no. will be calculated upon shipment.

  • field TDNSTA
  • Final DN (field DLN)

If the box is checked, the final DN is systematically created and printed upon shipment confirmation.
If the box is not checked, the final DN is created, but not printed.

  • Differential DN (field DDN)

If the box is checked, the differing DNs are printed only if changes have been introduced to the temporary DNs, upon shipment confirmation. The DN no. assigned to the movements remains the temporary DN no.

Delivery note

Name of the report for the print-out of the DN and packing list, jointly printed if the DN is in the packing stage. The name set up here is used as the default value of the corresponding DO header field.

Report code of the Delivery Note to be printed during the shipment of an "inter-site" type round.

Close

 

Tab Merging of flows

Presentation

These setups are used within the framework of the DO wave launching with a merging of flows type preparation mode.

Close

 

Fields

The following fields are present on this tab :

Rules

  • Group merging of flows (field GRUCOD)

The grouping code is used for the merging of flows.

  • Small/big parcels mgmt (field VOLMGT)

This flag must be taken into account within the framework of the activation of the merging of flows. When the box is checked, the movements will be processed according to the parameters on small and large volumes.

TO setting up

  • Pick mono prep. zone (field FLCPKZPIK)

These parameters are used within the framework of the creation of TOs during the first phase.

If the box is checked, the system will create removal preparation single area TOs.

  • Deposit mono prep. zone (field FLCPKZDPS)

If the box is checked, the system will create removal preparation single area TOs.

  • Dividing of load (field FLCWKL)

If the box is checked, it means that the TOs will be sub-divided so as to comply with the load delimitations defined in the preparation area.

The load calculation will always be carried out in the removal preparation area. In the case of removal preparation multi-area TOs, it is mandatory to specify the preparation area to be considered for the calculation in the "Prepa Area" field.

Stipulates the preparation area to be used for the load splitting in the the case of multiple removal preparation area TOs.

Transfer validation

  • field FLCVLD

If the box is activated, then the transfers of flow merging type will be validated automatically. Otherwise, a user will have to manually validate the transfers.

If the validation is automatic, entry of the operator code and location control key will be prohibited irrespective of the setup.

Launch step 2

  • field FLCSTA2

Manual, Automatic. These options are only available if transfer validation is automatic. In that case, the 2nd preparation phase can be performed automatically, depending on the selected parameter.

Prints

  • Transfer list (field FLCLST)

Triggers the printing of the transfer orders at the end of the wave.

  • Transfer label (field FLCLBL)

Triggers the printing of the transfer labels at the end of the wave.

Close

 

Tab Packaging

Presentation

These setups are used within the framework of the DO wave launching with a load preparation mode, be it a declarative or pre-packing mode, with or without merging of flows.
The Shipment confirmation setup is also used for DOs without load preparation.

Close

 

Fields

The following fields are present on this tab :

Evolution status

  • field W3TIT0

 

  • field W3TIT1

 

  • field W3

 

  • field W3TIT2

 

  • Parcel Validation (field PRCVLD)

 

  • field INISTAVLD

 

  • field ICOA1

 

  • field LASSTAVLD

 

  • Parcel palletisation (field PRCPLZ)

Specifies if the parcel palletization phase is active for the current depositor.
If the box is not checked, parcel palletization is not managed.
If the box is checked, parcel palletization is managed. Each parcel of the DO must be palletized.

  • field INISTAPLZ

 

  • field ICOA2

 

  • field LASSTAPLZ

 

  • Control loading of parcel (field LODCTL)

Specifies if a unitary parcel loading declaration must be carried out.
At this stage, "unitary" refers to: the parcel, if palletization is not managed, or the SU if palletization is managed.
If the box is not checked, the parcel loading declaration is not used.
If the box is checked, the parcel loading declaration is used.

  • field INISTALOD

 

  • field ICOA3

 

  • field LASSTALOD

 

  • Shpiping confirmation (field DSPMGT)

Informs the system on the use of the "Shipment confirmation" function for a DO, packed or not.
If the box is not checked, the shipment confirmation is not used. The system takes the DO status to 9, shipped, closed, to the final phase before shipment.
If the box is checked, the shipment confirmation is used according to two possible modes, by DO or by shipment round.

Note: it is not necessary for all the pickings (parcels/P.O.) of a DO to be validated for the shipment of a DO (partial shipment) to be confirmed, if shipment deferments are used.

  • field INISTADSP

 

  • field ICOA4

 

  • field LASSTADSP

 

Prepacking

  • Single parcel item (field SPAITM)

Forcing the system to create a single-parcel movement makes it possible to minimize the splitting of references in the parcels.
If the box is not checked, the system does not necessarily create single-reference parcels.
If the box is checked, the system creates in priority single-reference parcels.

It opens a new parcel when it is not able to prepack a whole movement inside the same parcel. The movement is single-parcel if there is a parcel with a sufficiently large size to pack it.

Using this parameter can only increase the number of constituted parcels.

  • Strict sequentiality (field SEQPKO)

This parameter tells the system if the prepacking must be carried out in strict compliance with thesequencing of the picking addresses.
If the box is not checked, the system does not comply with the sequencing of the picking addresses.
If the box is checked, the system considers that there is only one parcel available for the packing, that which is being constituted.

Using this parameter can only increase the number of constituted parcels.

Actual parcel weight entry

  • field PRCINF

This specifies whether the actual weight of a parcel must be entered in the parcel validation program:

  • No: the actual weight is neither entered nor calculated.
  • By default + modifiable: the actual weight is calculated from the theoretical weight and cannot be modified.
  • By default + modifiable: the theoretical weight is pre-loaded in the actual weight field that remains modifiable.
  • Modifiable: the actual weight is necessarily entered without pre-loading.

Packing

Parcel range used by default to pack a product.
This default range will be used if:
- The product group does not impose any parcel range,
- The product line of the DO does not mention any parcel range.

Parcel range and type used by default to package a product container as is, often referred to as 'ET'.

Type of parcel used by the prepacking algorithm to package the stock objects that can be shipped as is.

  • field PTYDESAXX

 

Prepalletization

SU type used by default to palletize a parcel as is during prepalletization.

  • Parcel validation: closing SU authorized (field FLGCLOSHP)

This flag is used to choose whether to close:

  • a prepalletized SU just validated in the package and SU validation functions,
  • an auto palletized SU just validated in the SU validation functions (unit and mass) dedicated to the auto palletization procedure.

Key in real SU weight

  • Enter SU info (field SHPINF)

This specifies whether the actual weight of a SU must be entered in the SU validation programs.

  • By default + modifiable: the actual weight is calculated from the theoretical weight and cannot be modified.
  • By default + modifiable: the theoretical weight is pre-loaded in the actual weight field that remains modifiable.
  • Modifiable: the actual weight is necessarily entered without pre-loading.

Palletisation

  • Single DO SU (field SHPSNGDLO)

If it is checked, it is possible to only regroup parcels from the same DO into a SU.

  • Big parcel auto palletization (field SHPAUT)

Stipulates if the system must automatically assign a SU number to a large parcel when the latter is validated.
If the box is not checked, the palletization declaration will have to be used for all the parcels.
If the box is checked, the palletization of the large parcels is automatically performed upon parcel validation.

  • Single consignee SU (field SHPSNGDLV)

It will be possible to regroup in one SU parcels belonging to the same CR, i.e. parcels with identical information (round, carrier, transport mode, ship-to customer code, company name (1st line), delivery postal code, Incoterm code and location).

SU type used by default during automatic palletization and specified upon creation of a SU.

Prints

  • Packing labels (field PRCLBL)

Specifies if a parcel label must be printed upon wave launching of the parcels or during the declarative packing of the DO.

  • Grouped labels (field FLGLBL1)

This option applies to the SU label and PO prepal only parcel printing.

If the option is ticked, upon launch of a prepal PO in picking, SU labels and parcels are printed with the same thermal printer no. 2 of the picking area.
The interest here is that the labels and parcels of an SU are grouped (printed in a row), which facilitates the picking.
However, this option has a restriction: SU labels and parcels are printed with the same printer, thus they must have the same label format.

If the option is not ticked, the SU labels and parcels are printed separately:
- SU labels with thermal printer no. 2 of the picking area.
- Parcel labels with thermal printer no. 1 of the picking area.
only so the restriction on the SU and parcel label format is no monger a problem. Yet, there will be a loss in productivity since SU/parcel labels are printed on different printers: there will be additional work to gather afterwards SU labels and the parcel labels associated with them.

  • SU labels (field SHPLBL)

This indicates whether a SU label must be printed on SU wave launch or on auto palletization (PAO)

  • APO (field OPALBL)

This indicates whether the PAO print must be printed upon creation of a palletization order (PAO).

SSCC management

  • SSCC on output (field SSCFLG)

If it is checked, the generation of the SSCC codes is activated for the parcels.

  • SSCC SU on output (field SSCUMFLG)

If it is checked, the generation of the SSCC codes is activated for the SUs. This flag can only be activated if the SSCC management is activated for the parcels (previous flag checked).

Stock on dock

  • Parcel management (field QATFLGPRC)

if it is checked, on-quay localization of parcels is managed for the depositor.

  • Operator code (field QATOPE)

If it is checked, the entry of an operator code will be requested for the validation of any parcel/SU stock on quay.

  • SU management (field QATFLGSHP)

If it is checked, SU localization on quay in managed.

  • Automatic update validation (field QATVLDAUT)

If it is checked, the parcel/SU transfer operations will be automatically validated. If it is not checked, the parcels/SUs will keep their status "Pending transfer" and the stock on quay will have to be validated manually.

Close

 

Tab Cross-docking

Presentation

These setups are used for Cross-Docking management.

Close

 

Fields

The following fields are present on this tab :

Cross Docking

  • Cross docking (field CDKMGT)

If the parameter is set to Yes, Cross-Docking is managed on output. Otherwise, it is not managed.

Control level

  • Locking level (field CDKLVLCTL)

Specifies the last phase that can be crossed by the DO lines as long as the Cross-Docking requirements are under process for the DO.

Output addressing

  • CDK store stock (field STKCDK)

If this parameter is checked, the output addressing takes account of the available stock (and not the current stock) of the Cross-Docking store. Otherwise this stock is ignored.

  • CDK store stock not available (field STKCDKPDI)

If this parameter is checked, the output addressing takes account of the unavailable stock (and not the stock pending input) of the Cross-Docking store. Otherwise this stock is ignored.

  • Reserve stock not available (field STKPDI)

If this parameter is checked, the output addressing takes account of the stock pending input into the reserve locations. Otherwise this stock is ignored.

Requirement expression

  • DI mvt not addressed (field NEDINPMVT)

If the parameter is checked, the non-addressed input movements are taken into account for the requirement expression during output addressing (a requirement will be created if at least one input movement is destined for the Cross-Docking).

  • EI under receipt (field NEDEINRCP)

If the parameter is checked, the expected inputs pending receipt (status 2, 3 or 4) are taken into account for the requirement expression during output addressing (a requirement will be created if at least one expected input line is destined for Cross-Docking).

  • Always express the requirement (field NEDALW)

If the parameter is checked, the requirements will always be expressed (created Cross-Docking PO) even if there are no expected or direct inputs to be dealt with by Cross-Docking.

Grid Priority

  • Criteria (field CDKPIO)

Specifies the order of priority of the checked criteria.

Close

 

Error messages

The only error messages are the generic ones.

Tables used

SEEREFERTTO Refer to documentation Implementation