Setup requirements

********’

EXC-DSC

C1EXCD

Foreign Currency Exchange Codes

********’

PAGE

WKCTD1

Page scrolling keywords

TMSAR

BK-PAYT

R1PAYT

This Control File is used primarily by the Cash/Journal Entry Program (ARE005). It holds up to 100 payment type codes each having a code description and definition.

TMSDS

CM-BR

R1BR

This Control File lists all valid Branch Codes. It lists the branch code short and long name and short description.

TMSDS

CM-CBOA

R1CBOA

This Control File contains the Customer Backorder Acceptance Codes. For each code, a flag determines whether to delete previous backorders for the selected item and customer. This caters for customers who wish to hold backorders once only for any given item. This Control File is used in conjunction with IM-IBOR, B/O-ACPT and the Order Priority field on the order header to define the backorder logic. NOTE: Backorder logic uses the following CM-CBOA, IM-IBOR, OE-SOHA, OE-SOHAV

TMSDS

CM-MJS

R1MJS

This Control File definition is used in conjunction with the “Major Store Group” field on the Customer Masterfile. A Major Store Group code indicates that specific customer accounts belong to a Major Store or Buying Group. A Major Store Number is then usually allocated to each individual account. If the Major Store Group is considered a Buying Group, Control File TMSDS/CC-BG can be setup to default the Major Store code to Buying Group code.

TMSDS

CM-OCON

R1OCON

This control file determines whether to merge orders by billing number or customer number or no merge in order consolidation.

TMSDS

CM-PAYT

R1PYTC

This Control File defines the Customer Payment Terms used in the Customer Masterfile. The Definition is as follows: – number of periods each code covers, – whether the period length is measured in number of days or months – Whether the terms are to be calculated from the date of invoice or from end of month. – to force payment of the invoice amount at order entry, flag this column as ‘1’. Payment is not forced on backorder Titles. Percentage to be deposited by the customer if the item ordered is backordered in POINT OF SALE module. If this column is not blank the minimum amount is the invoice amount and % of the b/o amount.

TMSDS

CM-SLRP

R2SLRP

 User defined sales representatives and Agents used in the Customer Masterfile. Sales Rep/Agent Code: Enter a code to identify the Sales rep or Agent Sales Rep/Agent Name: Enter the name to match to code. Sales Rep Level 1 & 2: prompt to select a valid code from Control Files TMSDS/SLRP-L1 & TMSDS/SLRP-L2 Creditor Number: If interfacing to Accounts Payable, enter a valid Creditor Number. This is used in conjunction with Control file TMSDS/SEQ-SLRP

TMSDS

EDI-AUTH

EASRCT

This control file is used to validate the customers that a nominated EDI trading partner can be authorised to produce orders. This can be achieved either by the customer billing account or by a customer classification table. Only where the trading partner ID is setup as a valid customer and has the same billing number or same customer classification code as the customers for the orders that are being
generated will the authority be granted.

TMSDS

EDI-CTNQ

C1BN

This Control File validates the incoming EDI carton quantity against the Item Masterfile. Enter the Customer or Billing number that requires validation.

TMSDS

EDI-DFLT

ORDP

Uses the order priority

TMSDS

EDI-DFLT

SRCT

Uses the source of transaction EB

TMSDS

EDI-IVCC

EASRCT

This control file manages the processing of an order that has an invalid customer/store code. If an order for a nominated sender is accepted with an invalid customer/store number then that order can also be made “suspended” waiting further processing.

TMSDS

EDI-IVIC

EASRCT

Used by the Order Entry Module for EDI orders. Determines whether or not to allow invalid Items by source of order. If not allowed, the order will not be processed, but held awaiting maintenance. If allowed, the invoice will print the error as a line item with an adjustment item (as entered in this file), the original code of the item that was ordered, and a delivery quantity of zero.

TMSDS

EDI-MPOA

RHSSAN

This Control File determines whether:
1. manual POA selection is allowed for the sender SAN
2. to suspend orders if there is a price difference within EDI

TMSDS

EDI-OVR

The Logical Warehouse is used in this process.
This Control file contains the fields that can be overridden when the user in the DSM380 EDI Order maintenance. This will allow the Warehouse and Customer B/O Accept fields to be replaced with values from this Control file. The status will be updated to ‘I’ if the values in the control file are valid.

TMSDS

EDI-PLCY

EASRCT

This Control File lists the source of each order and states whether a price is allowed In the Allow Price field for each source a 0 = No, meaning the price is not allowed or a 1 = Yes, meaning the price is allowed for the specified source Billing account; Price policy can be defined by source of order and billing account OR source of order only. If not defined default is ‘N'(List price EDI price type: ‘ ‘ as per normal price = leave blank. ‘G’ invoice price including discount and tax ‘N’ List price excluding tax
If not defined the default is ‘N’ (List price)

TMSDS

EDI-RFMT

%SUBST(RHS

This control file determines which start/end positions of the customer reference no. constitutes the common reference portion used to determine the group “direct to store” orders. This applies to customer references that are not entirely the same but are still considered part of a group order. Note: This is only used in the consideration for manual POA purposes.

TMSDS

EDI-STS

R1TSTS

System defined status codes of EDI orders. Each code has a system defined flag which determines whether to allow or disallow maintenance at this stage of processing the order.

TMSDS

EDI-TXT

This control file allows the appended line item text to be switched off when receiving BISAC orders through EDI. This works in conjunction with DSO370B.

TMSDS

EDI-WRNP

C1BN

This Control File gives a warning on price differences for the entered customer (billing) number. The EDI orders with at least one line with a different price will initially be set to a “held” status.      
 Should the order be suspended on a price difference? Suspend Yes the order will go to S status in order processing. Suspend No the order will go through order processing at entered status, then pending if setup then K status through to the warehouse.

TMSDS

IM-UOM

EBUOM

TMSDS

TR-HMVF

This Control File holds the default value for ‘Hold for Minimum Value field on the order header.                      
Enter either Y or N as a default where:              
‘Y’ = the order will be held if its value is below the predefined value.                            
‘N’ = the order will not be checked & held for minimum value.

NOTE: This field may not display for all formats and it can be overwritten at order entry.

TMSDS

TR-SRCT

EASRCT

User defined codes which indicate what external source the orders come from. Is this a sale to a retail customer (if so, tax will be charged on the price file whether or not that price is overridden at time of order entry). This Control File is used in the setup of Order Picking Category Maintenance (WHM090 – Warehouse Database)

TMSDS

TR-TOS

R2TOS

For each user defined type of sales code, the following is defined:-the release priority assigned to an order when it goes to backorder, -whether to update the sales history for transactions with this type of sale code (if set to no, these sales may be viewed from the warehouse detailed stock inquiry),

– whether an item with this code will be sold for zero price and discount.

– for Warranty & Service a TOS code is needed for non-warranty and service. Do not force a nil price for these TOS codes. Used when printing invoices and retrieving the appropriate price code when issuing parts.

TMSDS

TR-TXT

W$TTYP

System defined text types