Monthly Archives: June 2011

Adding a Child Warehouse

This is a checklist for adding a new CHILD warehouse to an existing environment. A child warehouse is one assumed to be directly affiliated with an existing PARENT warehouse. Although the child warehouse’s inventory will be visible as a separate location, it will be included in the parent warehouse’s inventory value for general ledger purposes.

 

In the codes file:

 

    Add a record for the “Warehouses” codes record. Field 5 should be the same division code as that of the child’s parent warehouse. Field 11 should be the same G.L. account number as that of the child’s parent warehouse. Field 15 will be the field number in the product file that this warehouse cost will come from and will most likely be “22”. Field 16 should be set to “C” for child warehouse. Field 19 should be set to ‘3’.

 


 

    Add a record for the “Warehouse Options” codes record. This record will look like the record for the parent warehouse except for the “Whse code” field, #2. Enter the child warehouse code in field #2.

 


 

 

 

    Add records for the “Ticket Number Counters” codes records for Invoice and Orders. Make sure the counters do not conflict with counters of other warehouses. Since the ticket counters will only be used for moving merchandise “from” the child warehouse back to the parent warehouse the ticket number range can be small compared to the range of the parent warehouse. Usually a range of no more than a few thousand will suffice.

 


 

    Add records for the “Mailing Address” codes records for “state”. Even though this won’t be used, the statement program requires it be added.

 


 

    Add records for the “Printers” codes records for the Default printer. We recommend the default printer NOT be the same as your normal default ticket printer.

 


 

Add each new printer to BATCOM:PRINTERS.COM and BATCOM:KILLPRINT.COM.

Setup a customer record for each “transfer” account needed. You will need an account to and from child warehouse. A simple rule to follow when setting up the transfer accounts is to use the warehouse code and territory number is the naming convention, i.e. W2S01 would be for a transfer from parent warehouse 2 (W2) to child warehouse S01 (S01) and S01W2 for a transfer from child warehouse S01 (S01) to parent warehouse 2 (W2).

 


Persona Users View of Supersedure Information

When a “Persona” user inquires on the availability of an item in Product Stock Inquiry and that item has been superseded then the user may or may not be able to see all supersedure information.  For example – the user is assigned to shipping warehouse 1 and warehouse 1 is “out of stock” on an item that has been superseded BUT warehouse 2 does have stock in the original item.  By default, the user will be shown the supersedure information relating the original item and it’s superseding number.  The intent is to NOT show supersedure information as long as the item is in stock at any warehouse.  This practice may not be suitable for every user, therefore we’ve made a change to “show all” supersedure information to Persona users that is controlled by the ‘DU’ (dialup parameters) codes record.  Control can be enforced at the default, warehouse, or customer level.  Here’s how – in the respective ‘DU’ codes record, place “/R,” in field #25 of the record.

Flagging a Part – Superseded, Synonymed, Substituted, NLA, etc.

The screen appearance and function of flagging an item as superseded, synonymed, substituted, NLA, etc. has changed. The new process was necessary to provide a standard that will also be incorporated into the new receiving module that is forthcoming.

Here’s an example of the screen.

The top portion of the work area displays the flag functions you can perform.

Select the item flag function you want to perform.

When you’ve select the flag function you want to perform the top portion of the work area displays the history of your session. In the example below, we’ve just superseded BS,27355 to BS,27355S.

Type a period or backslash to display the flag functions menu and perform another flag function.

In the following example, we’ve just added a special message (flag function #5) for BS,399671.