IBM Support

Carton Number to Tote Number Mapping/Scan Field Translation Setup

Troubleshooting


Problem

Carton Number to Tote Number Mapping/Scan Field Translation Setup

Symptom

Tote Number is a bar-coded number applied to a container into which loose units are picked. A tote is typically used in a pick to light/put to light system, but can be used in parts warehouses as well. Where it is used, a tote is used instead of an empty carton to pick into. (These containers are frequently recycled.)

To support this type of scenario, DCS 6.0 provides the ability to record mapping between tote number and carton number, and subsequently allows scanning the tote number instead of carton number in all transactions.

Configuration changes required:

Message File Setup:
The mapping between a DCS entity (such as Ship Label #) and an external entity (such as Tote #) can be recorded by pressing CTRL-T on any screen. CTRL-T opens another window which allows recording the mapping.

Note: For CTRL-T to work, ensure that yntrvt100keys.bin is taken from the DCS 6.0 distribution CD.

Once this file is in place, use 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, DCS will try to translate the barcode into DCS data based on other setup.

Field Value
Parm Type 1 PCK
Parm Type 2 AUTOBTREQD
Description Automatic Barcode Translation Required
Field Value Y


As mentioned, the mapping between DCS and external entities can be done through CTRL-T, but the system may force the recording through Batch Pick - Carton. To turn this feature on, set up 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 two bar code types need to be set up: One for the DCS entity and one for the external entity.

For example: SH could be the bar code type for Ship Label Number, and XT could be the bar code type for Tote Number. (Note: Bar Code Types that start with an X support Extensibility.)

First, set up the external entity barcode type

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

Secondly, set up the DCS entity barcode type:

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 a given installation. If the function does not exist, select function profile setup (function ID 09753). Copy/Add the function 09329 to Z9329, and change the description to Whse Many 2 Many X Ref Setup. Blank out the Rec Type field, and allow access to the user group YANTRA by using User Function Setup (function ID 09754).

Use the function Z9329, to set up fields which need translation:

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

This is a simple setup, in which there is only one entity that needs translation: whenever a Tote Number is scanned in the Ship Label # field, DCS will translate Tote Number into the Ship Label Number.

To invoke the mapping screen from anywhere in the application, set up the following cross-reference record using function ID 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
xOut Reference Field 3 Ship Label #
Out Reference Field 4 Tote #

Identify all the different necessary repository field names. (This can be done by searching for the literal Ship Label # in the ASCII forms provided as part of DCS 6.0 distribution CD. The forms are available along with support utilities.)

Typically, there will be only 2 - 3 repository field names for one DCS entity, such as one for CRT screens and one for RF screens.

(Note: The Manifesting system does not have repository field names; the list of field names in the Manifesting system is not available on the DCS 6.0 distribution CD.)

For each repository field name, set up a record using function ID 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 #

Cause

Resolving The Problem

Tote Number is a bar-coded number applied to a container into which loose units are picked. A tote is typically used in a pick to light/put to light system, but can be used in parts warehouses as well. Where it is used, a tote is used instead of an empty carton to pick into. (These containers are frequently recycled.)

To support this type of scenario, DCS 6.0 provides the ability to record mapping between tote number and carton number, and subsequently allows scanning the tote number instead of carton number in all transactions.

Configuration changes required:

Message File Setup:
The mapping between a DCS entity (such as Ship Label #) and an external entity (such as Tote #) can be recorded by pressing CTRL-T on any screen. CTRL-T opens another window which allows recording the mapping.

Note: For CTRL-T to work, ensure that yntrvt100keys.bin is taken from the DCS 6.0 distribution CD.

Once this file is in place, use 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, DCS will try to translate the barcode into DCS data based on other setup.

Field Value
Parm Type 1 PCK
Parm Type 2 AUTOBTREQD
Description Automatic Barcode Translation Required
Field Value Y


As mentioned, the mapping between DCS and external entities can be done through CTRL-T, but the system may force the recording through Batch Pick - Carton. To turn this feature on, set up 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 two bar code types need to be set up: One for the DCS entity and one for the external entity.

For example: SH could be the bar code type for Ship Label Number, and XT could be the bar code type for Tote Number. (Note: Bar Code Types that start with an X support Extensibility.)

First, set up the external entity barcode type

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

Secondly, set up the DCS entity barcode type:

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 a given installation. If the function does not exist, select function profile setup (function ID 09753). Copy/Add the function 09329 to Z9329, and change the description to Whse Many 2 Many X Ref Setup. Blank out the Rec Type field, and allow access to the user group YANTRA by using User Function Setup (function ID 09754).

Use the function Z9329, to set up fields which need translation:

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

This is a simple setup, in which there is only one entity that needs translation: whenever a Tote Number is scanned in the Ship Label # field, DCS will translate Tote Number into the Ship Label Number.

To invoke the mapping screen from anywhere in the application, set up the following cross-reference record using function ID 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
xOut Reference Field 3 Ship Label #
Out Reference Field 4 Tote #

Identify all the different necessary repository field names. (This can be done by searching for the literal Ship Label # in the ASCII forms provided as part of DCS 6.0 distribution CD. The forms are available along with support utilities.)

Typically, there will be only 2 - 3 repository field names for one DCS entity, such as one for CRT screens and one for RF screens.

(Note: The Manifesting system does not have repository field names; the list of field names in the Manifesting system is not available on the DCS 6.0 distribution CD.)

For each repository field name, set up a record using function ID 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 #

[{"Product":{"code":"SS6PEW","label":"IBM Sterling Order Management"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Not Applicable","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Historical Number

PRI48204

Product Synonym

[<p><b>]Fact[</b><p>];

Document Information

Modified date:
16 June 2018

UID

swg21541846