How to achieve tote to carton mapping?

Resolving The Problem

Following is from the DCS documentation (Outbound_configuration_guide) :
Carton to Tote # Mapping
Tote# is a bar-coded number applied to a container onto which you can pick loose units. A tote is typically used in a pick-to-light/put-to-light system, but can be used in parts warehouses as well. The tote is used instead of an empty carton to pick into. These containers are frequently recycled. To support this scenario, DCS 6.0 (and higher versions) provides the ability to record mapping between the tote number and carton number and subsequently allows you to scan the tote number instead of the carton number in all transactions.

Configuration Changes Required
This feature is enabled through a serious of configuration steps.

Message File Setup
You can record the mapping between a DCS entity (such as Ship Label #) and an external entity (such as Tote #) by pressing CTRL+T on any screen. CTRL+T brings up another window that allows you to record the mapping. For CTRL+T to work, you need to ensure that yntrvt100keys.bin is copied from the DCS 6.0 CD.

Once you have this file in place, you still need to go through the setup described below to be able to invoke the screen when you press CTRL+T.

Warehouse Parameter Setup (09289)
Add the following warehouse parameter. Whenever a barcode is scanned in any field, the system will try to translate the barcode into DCS data based on other setup.
Parm Type 1 PCK
Parm Type 2 AUTOBTREQD
Description - Automatic Barcode Translation Required
Field Value Y

Also, you can record the mapping between a DCS entity and an external entity through CTRL+T. But the system can also force you to record the mapping through Batch Pick - Carton. To turn this feature on, setup the following warehouse parameter:

Field Value
Parm Type 1 PCK
Parm Type 2 LDTRSLNLPP
Description Load Translation in Batch Pick Carton
Field Value Y

Bar Code Types Setup (09307)
For each mapping, you need to setup two bar code types. One is for the DCS entity and one is for the external entity. For instance, SH could be the bar code type for Ship Label # and XT could be the bar code type for Tote #. Bar Code Types that start with an X support extensibility.

First, setup the external entity barcode type as follows:
Field Value
Bar Code Type XT (user defined)
Description Tote # (user defined)
Ref Bar Code Type
Variable Length N
Bar Code Len 4 (length of external entity)
From Position 1
To Position 4
Default Qty Type 00 (=None)
Default Qty 0
Validation Source 01 (= Validate From Bar Code Translation Setup)
Allow Pick Qty Mod N

Second, setup the DCS entity barcode type as follows:
Field Value
Bar Code Type SH (user defined)
Description Ship Label # (should be consistent with DCS terminology)
Ref Bar Code Type XT (user defined, external entity bar code type)
Variable Length N
Bar Code Len 11 (length of DCS entity)
From Position 1
To Position 11
Default Qty Type 00 (=None)
Default Qty 0
Validation Source 00 (=None)
Allow Pick Qty Mod N

Warehouse Many To Many Cross Reference Setup (Z9329)
The 'Z9329' function ID may not be a valid function at your installation. If the function does not exist, go to Function Profile Setup (09753). Copy/add the function '09329' to 'Z9329.' Change the description to "Whse Many to Many X Ref Setup". Blank out the Rec Type field. Give access to the user group YANTRA through User Function Setup (09754).
Through the function 'Z9329', setup fields that need translation are:

Field Value
Reference Type BTS
In Reference Field 1 Repository Field Name (Valid repository field name or NOREPOS)
In Reference Field 2 Field Name (optional)
In Reference Field 3 Form Name (optional)
In Reference Field 4
Priority 1
Out Reference Field 1 External Value Bar Code Type
Out Reference Field 2 Base Value Bar Code Type
Out Reference Field 3 Base Value Label On Screen
Out Reference Field 4 External Value Label On Screen


Here is a simple setup wherein there is only one entity that needs translation. Whenever you scan Tote # in Ship Label # field, the system should translate Tote # into the Ship Label #.

In order to invoke the mapping screen from anywhere in the application, setup the following cross reference record through 'Z9329':

Field Value
Reference Type BTS
In Reference Field 1 NOREPOS
In Reference Field 2
In Reference Field 3
In Reference Field 4
Priority 1
Out Reference Field 1 XT
Out Reference Field 2 SH
Out Reference Field 3 Ship Label #
Out Reference Field 4 Tote #

Identify all the different repository field names that you need. This is done by searching for the literal "Ship Label #" in the ASCII forms provided as part of the DCS 6.0 CD. The forms are available along with support utilities.

Typically, there would be only two or three repository field names for one DCS entity. One would be for the CRT screens, and one for RF screens. The Manifesting System does not have repository field names. (Field names in the Manifesting System are not available on the DCS 6.0 CD.)

For each repository field name, set up a record through Z9329 as follows:

Field Value
Reference Type BTS
In Reference Field 1 Repos!FldCrtnNo
In Reference Field 2
In Reference Field 3
In Reference Field 4
Priority 1
Out Reference Field 1 XT
Out Reference Field 2 SH
Out Reference Field 3 Ship Label #
Out Reference Field 4 Tote #

Field Value
Reference Type BTS
In Reference Field 1 Repos!FldCrtnNoOrScmRF
In Reference Field 2
In Reference Field 3
In Reference Field 4
Priority 1
Out Reference Field 1 XT
Out Reference Field 2 SH
Out Reference Field 3 Ship Label #
Out Reference Field 4 Tote #

Field Value
Reference Type BTS
In Reference Field 1 Repos!FldCrtnNoRF
In Reference Field 2
In Reference Field 3
In Reference Field 4
Priority 1
Out Reference Field 1 XT
Out Reference Field 2 SH
Out Reference Field 3 Ship Label #
Out Reference Field 4 Tote #

Field Value
Reference Type BTS
In Reference Field 1 Repos!FldSCMRF
In Reference Field 2
In Reference Field 3
In Reference Field 4
Priority 1
Out Reference Field 1 XT
Out Reference Field 2 SH
Out Reference Field 3 Ship Label #
Out Reference Field 4 Tote #

Field Value
Reference Type BTS
In Reference Field 1 Repos!FldShipLabelNo
In Reference Field 2
In Reference Field 3
In Reference Field 4
Priority 1
Out Reference Field 1 XT
Out Reference Field 2 SH
Out Reference Field 3 Ship Label #
Out Reference Field 4 Tote #

And for the Manifesting System:

Field Value
Reference Type BTS
In Reference Field 1 NOREPOS
In Reference Field 2 txtCartonNo
In Reference Field 3 frmCartonNo
In Reference Field 4
Priority 1
Out Reference Field 1 XT
Out Reference Field 2 SH
Out Reference Field 3 Ship Label #
Out Reference Field 4 Tote

Set up a tote bar code as below:
09307 03 W34 Bar Code Types Setup yantra 09/26 13:13
Inquire

Bar Code Type : TO

Description : Tote Ref Bar Code Type :
Variable Length : N (Y/N) Bar Code Len : 5
From Position : 1 To Position : 5
Default Qty Type : 00 None Default Qty : 1
Val Source : 01 Bar Codes Allow Pick Qty Mod : N (Y/N)

Set up the carton bar code as follows:
09307 03 W34 Bar Code Types Setup yantra 09/26 14:08
Inquire

Bar Code Type : SH

Description : Carton No Ref Bar Code Type : TO Tote
Variable Length : N (Y/N) Bar Code Len : 11
From Position : 1 To Position : 11
Default Qty Type : 00 None Default Qty :
Val Source : 05 None Allow Pick Qty Mod : N (Y/N)


The tote validation comes from bar code translation (Can be viewed in 09309 ) so the bar_code_trsln record should be as follows:
whse = corp whse
bar_code_type = the bar code for tote such as TO
bar_code = tote # such as T2048
reference_field1 = shipping lablel such as 0168290001

i.e. the carton_no should be in the reference_1 field corresponding to the tote. (this record may be inserted using some triggers after carton creation when mapping it to the tote)