SA Table Code Value Setup field descriptions

These fields are listed alphabetically for each table type.

Petty Cash Transactions

Use this table type if you have activated the cash drawer management feature in SA Administration-Administrator Options-Documents-Sales Orders-Entry Settings. You can set up transaction type records for petty cash deposits and withdrawals common to your warehouse, such as Deposit, Lunch, Adjustment Out. These Petty Cash Transaction types are required for Sales Drawer Transaction Entry. These fields honor Division and warehouse security.

Bank

You should only specify a Bank value for a petty cash transaction type that withdraws money from the drawer for a bank deposit. For example, the drawer has accumulated $2000 during the morning. At 12:00 PM, you remove $1800 to deposit in the bank. You record this withdrawal in Sales Drawer Transaction Entry with a withdrawal transaction type. The $1800 is deposited in the bank specified in the withdrawal transaction type. This transaction type must have the option, Put Money In, cleared; that is, money is taken out of petty cash and moved to a bank. The option, Post to G/L, must be selected. This field honors Division and warehouse security.

Note: Specify either a Bank value or a General Ledger Account value. If you try to specify both, an error is displayed: Cannot Set Both G/L Account and Bank (7169). If you specify a Bank value, a general ledger account was likely specified when that bank was set up.

Description

Specify a descriptive name for the transaction type. The field limit is 24 characters. Duplicates are not permitted.

General Ledger Account

Select the appropriate account for this transaction type. Use this field in conjunction with the option, Post to G/L, which must be selected. The account must be a valid account set up in GL Account Setup. This field honors Division and warehouse security.

Note: Specify either a Bank value or a General Ledger Account value. If you try to specify both, an error is displayed: Cannot Set Both G/L Account and Bank (7169).

Post to G/L

Use this option to designate whether the transaction type should post to the General Ledger. We recommend that you select this option for every transaction type you create so you can track your cash.

Put Money In

Use this option to designate whether the transaction type puts money into the cash drawer or takes money out of the cash drawer.

If you select this option, then, in Sales Drawer Transaction Entry, the Direction value is displayed in the grid as “Cash In”. If you clear this option, then, in Sales Drawer Transaction Entry, the Direction value is displayed in the grid as “Cash Out”.
If you select this option, then, in Sales Drawer Reconciliation Entry, the Amount value is displayed in the grid as a positive number. If you clear this option, then, in Sales Drawer Reconciliation Entry, the Amount value is displayed in the grid as a negative number.

Transaction Type

Specify one or more transaction type records for petty cash deposits and withdrawals common to your warehouse. For example, Deposit, Lunch, Adjustment Out.

Price/Cost Units

EDI Unit of Measure: This value is required if you use Electronic Data Interchange (EDI). Specify the unit of measurement code as defined in the element table (Element 355) in the ANSI X12 Standard manual.
Price/Cost Units per Stock Unit: The price/cost based on the special price/cost unit you specified in the Special Price/Cost Unit field.
Special Price/Cost: A special price/cost refers to a product that is billed from the vendor in terms of a unit that is not a simple multiple of the selling unit. The product could optionally have no special price/costing, special price/cost determined by you, special costing per thousand (.001), or special costing per hundred (.01).
Special Price/Cost Unit: This is the actual special unit for a product. The unit provides a label for the special unit conversion which is specified in a Price/Cost Units per Stk Unit field.

Pricing/Rebate Region

Pricing/Rebate Region

Specify up to a four-character ID for a pricing region, rebate region, or both. This value defines a region under which pricing and rebate records can be created in PD Pricing Setup and PD Pricing Sheet Setup. If you specify a pricing/rebate region on a Product Warehouse Description Setup record, pricing and rebate records for that region are applied to the warehouse in functions throughout Distribution SX.e.

The prefix, ‘RGN-’, is added to the pricing/rebate ID so if you also create pricing and rebate records by warehouse, you can determine if an existing record is by region or warehouse. For example, suppose your company identifies both regions and warehouses numerically. If RGN-0008 is displayed in PD Pricing Setup or PD Pricing Sheet Setup, the pricing record is region-based. If 0008 is displayed, the pricing record is warehouse-based.

To enable the pricing and rebate records by regions functionality, select Pricing by Region and Rebate by Region in the Pricing and Rebates sections of SA Administrator Options-Products.

Product Category

Category

Product categories are a method of grouping products together for reporting and distribution. This method represents a selling perspective. Most sales and inventory control reports allow you to enter a product category option or range. You can set up an unlimited number of product categories, each with individual General Ledger account codes. These functions use the product categories:

Product Setup
Product GL Distribution Setup
Sales Order Entry

Category List

Select Non-Stock if the product category pertains to nonstocks. This additional categorization enables you to efficiently search for nonstock product categories using the Category field lookup when adding a nonstock to an order in Sales Order Entry, including nonstocks that are part of a kit, Purchase Order Entry, Transfer Entry, and VA Order Entry. If you do not want to designate a product category as a nonstock product category, you can leave this field blank.

Product Model Number

If you have activated the National Program functionality, and you participate in National Programs that use product model numbers, you can set up those numbers here. For example, some Manufacturers require a specific model number for a claim to be submitted and reimbursed; or, a specific model number has one price and another model number has a different price. You can specify an 18-character product model number, with an associated description of up to 100 characters. Data is stored with an identifier of PM. This table type works similar to groups. Optionally, you can associate a product or catalog product with the model number by selecting the valid product model number from the Model field in Product Setup-General, or in Product Catalog Setup-General. The SA Table Values Report lists Product Model Number codes and descriptions.

Product Preference

Preference: A preference is a priority attribute, such as choice of warehouse, used in conjunction with a tier and a tier group. A tier is a product attribute, such as quality, availability, location, or price, used in conjunction with a tier group and a preference. You can classify SKUs (stock keeping units) based on product tiers [quality: Good, Better, Best] or preferences [location priority: 1st-Main whse, 2nd-South whse, 3rd-North whse]. We recommend limiting tiers and preferences to three or four categories with meaningful and discernible levels.
Priority: Product categories are a method of grouping products together. To enable usage and replenishment for a tiered and preferred product, select Product Preference, select the highest preferred product you want to apply usage and replenishment to, and click Edit. In the Extended section, specify the number 1. This priority must be set in conjunction with selecting the Allow Usage Move option in Product Warehouse Description Setup, and clearing the Exclude Usage Move in Product Warehouse Product Setup. Ensure that the numeric priority is associated with only one product preference in a tier group. For example, for the Tier, Best: drill bit, in Tier group 09876, only product A is assigned the Preference numeric priority of 1.

Product Price Type

Margin Percent - Minimum: The minimum acceptable profit margin percentage for all products contained in the specified product price type. If the product is sold at a lower profit margin, the Sales Exceptions Report prints this exception on the report. Sales Order Entry also displays a message when this occurs. This is useful in determining a product frequency pattern if the company is losing profit. The average cost from Product Warehouse Product Setup is used to calculate the minimum margin. If average cost is zero, the minimum profit margin is not checked for this price type. If you use the minimum or maximum profit margin controls, make certain that average cost is calculated for each product. You can leave this field blank.
Margin Percent - Maximum: The maximum acceptable profit margin percentage for all products contained in the specified product price type. If the product is sold at a higher profit margin, the Sales Exceptions Report prints this exception on the report. Sales Order Entry also displays a message when this occurs. This is useful in determining if specific products are making an exceptional profit margin and the consequences of those results. You can leave this field blank.
Price Type: Set up a specific product price type or a blank type. Use specific price types to group certain products together for pricing purposes. You can then enter the default product price types on Pricing and Discounting records, which are then used in Sales Order Entry. You could use a blank product price type to ensure a minimum or maximum margin is maintained for all products, including nonstock items that cannot be set up with a price type.
Unit: Select the unit of measure, if applicable.

Product Restrictions

Restriction Code: Specify an alphanumeric code to set up the product restriction codes that are then assigned to Product Restriction Setup and Product Certification/License Setup records. To view the product restriction codes and their descriptions, run the SA Table Values Report. They are listed under the type ‘RC’.

Product Tier

Tier: A preference is a priority attribute, such as choice of warehouse, used in conjunction with a tier and a tier group. A tier is a product attribute, such as quality, availability, location, or price, used in conjunction with a tier group and a preference. You can classify SKUs (stock keeping units) based on product tiers [quality: Good, Better, Best] or preferences [location priority: 1st-Main whse, 2nd-South whse, 3rd-North whse]. We recommend limiting tiers and preferences to three or four categories with meaningful and discernible levels.

Profile Name

Profile: To support personalization of the user interface, you can create profiles for specific job functions such as customer service representatives or warehouse personnel in SA Table Code Value Setup. A profile can be assigned to an operator in SA Operator Setup-Static Information.

Prospect Activity Code

Prospect Activity Code values identify and categorize job tasks. Activity codes may include administrative meetings, customer collections. The values you specify are displayed in SW Enter Job Times in the Activity field and in SW Setup Job Types in the TQM Activity Code field.

Identifier

A unique value that identifies this table value.

Unique To Sales Rep

Select this option if this table value is unique to the sales representative that is specified on your SA Operator Setup record. If you leave this option blank, the table value is available to all sales representatives.

If you select this option when you conduct a search, only the records that match the sales rep on you operator record are displayed in the grid. You cannot use a different sales rep value to conduct a search.

Prospect Activity Result

Identifier

A unique value that identifies this table value.

Unique To Sales Rep

Select this option if this table value is unique to the sales representative that is specified on your SA Operator Setup record. If you leave this option blank, the table value is available to all sales representatives.

If you select this option when you conduct a search, only the records that match the sales rep on you operator record are displayed in the grid. You cannot use a different sales rep value to conduct a search.

Prospect Company Size

Identifier

A unique value that identifies this table value.

Unique To Sales Rep

Select this option if this table value is unique to the sales representative that is specified on your SA Operator Setup record. If you leave this option blank, the table value is available to all sales representatives.

If you select this option when you conduct a search, only the records that match the sales rep on you operator record are displayed in the grid. You cannot use a different sales rep value to conduct a search.

Prospect Rating

Identifier

A unique value that identifies this table value.

Unique To Sales Rep

Select this option if this table value is unique to the sales representative that is specified on your SA Operator Setup record. If you leave this option blank, the table value is available to all sales representatives.

If you select this option when you conduct a search, only the records that match the sales rep on you operator record are displayed in the grid. You cannot use a different sales rep value to conduct a search.

Prospect Source Code

Identifier

A unique value that identifies this table value.

Unique To Sales Rep

Select this option if this table value is unique to the sales representative that is specified on your SA Operator Setup record. If you leave this option blank, the table value is available to all sales representatives.

If you select this option when you conduct a search, only the records that match the sales rep on you operator record are displayed in the grid. You cannot use a different sales rep value to conduct a search.

Prospect Type

You must set up at least one prospect type before you can set up a prospect in Sales Prospect Setup. Prospect types are a method of categorizing prospects into unique groupings. When you set up a prospect type, you define labels for the four user fields in Sales Prospect Setup.

Identifier: A unique value that identifies this table value.
Field 1-4 Side Label: The field label that is displayed for the User Settings fields in Sales Prospect Setup when you select the prospect type. The side label for the first two fields can be 30 characters in length. These fields are generally used for extra descriptions, comments, or any lengthy information you feel must be stored with the record.

Note: The side label for fields 3 and 4 are validated against the Prospect User codes 1 and 2 defined in SA Table Code Value Setup. The user codes are user defined for your own use and are limited to 4 characters.
Field 1-4 Column Heading: Column headings are not used at this time.

Prospect User Code 1

On each prospect record, you can specify two user-defined codes. These codes can be set up for anything you want.

Identifier

A unique value that identifies this table value.

Unique To Sales Rep

Select this option if this table value is unique to the sales representative that is specified on your SA Operator Setup record. If you leave this option blank, the table value is available to all sales representatives.

If you select this option when you conduct a search, only the records that match the sales rep on you operator record are displayed in the grid. You cannot use a different sales rep value to conduct a search.

Prospect User Code 2

On each prospect record, you can specify two user-defined codes. These codes can be set up for anything you want.

Identifier

A unique value that identifies this table value.

Unique To Sales Rep

Select this option if this table value is unique to the sales representative that is specified on your SA Operator Setup record. If you leave this option blank, the table value is available to all sales representatives.

If you select this option when you conduct a search, only the records that match the sales rep on you operator record are displayed in the grid. You cannot use a different sales rep value to conduct a search.

Prospect/Proposal Stage

The prospect/proposal stage generally refers to the various business stages, such as prop for proposal, demo for demonstration, ngtn for negotiation, or fcnt for final contract.

Identifier

A unique value that identifies this table value.

Unique To Sales Rep

Select this option if this table value is unique to the sales representative that is specified on your SA Operator Setup record. If you leave this option blank, the table value is available to all sales representatives.

If you select this option when you conduct a search, only the records that match the sales rep on you operator record are displayed in the grid. You cannot use a different sales rep value to conduct a search.

Purchase Order Addons

You can set up a maximum of 99 purchase order addons. Addons are costs that are added to purchase orders, for example, freight, premium freight, and handling. You can select the purchase order addons established here on the vendor record in Vendor Setup so the addon defaults each time a purchase order is entered for the vendor.

If you are integrated with AvaTax and use purchase order addons, set these up in SA Table Code Value Setup-Purchase Order Addons.

Addon: The PO Addon ID specified when the addon was initially created in SA Table Code Value Setup. This four-character ID cannot be edited.
Default Allocation Type: The default allocation type defaults when you create a purchase order during Purchase Order Entry or during Purchase Receipt of Inventory Entry on the Addons view. You can override the allocation type. You can assign a standard purchase order addon for each vendor in Vendor Setup, which will default during Vendor Invoice Center Entry
G/L Exp Addon: The General Ledger account code associated with this addon. Each addon can have an individual account code or all addons can update the same account code. Purchase Receipt of Inventory Entry and Vendor Invoice Center Entry use this account code to update General Ledger for expensed addons. If Purchase Order and Accounts Payable addons are established as capitalized through the individual Vendor Setup records, this account code is not used. The account code must already exist in GL Account Setup.
G/L Uninvoiced: The General Ledger account code to be used for capitalized addons that are posted during Purchase Receipt of Inventory Entry and Vendor Invoice Center Entry. If you leave this field blank, the account code specified as the Uninvoiced Addons account code from the operator's SA Operator Setup-Other Options record is used. The Uninvoiced Addons account is credited during Purchase Receipt of Inventory Entry .
EDI Addon Code: Specify the three character EDI Addon Code. This is necessary to provide a cross-reference between the system Addon and the ANSI X12 three-character code representing that same addon.
Freight: If this option is selected, this PO Addon is considered freight. EDI 810 incoming invoices for vendors, with the FOB Destination option selected in the PO header, will be suspended in Vendor Entry Group EDI Invoice Processing Report if there are any addons that are considered freight. If the PO header FOB Destination option is cleared, the invoice will not be suspended. If you bill your customers for Direct Order purchase order freight charges, you can designate whether only freight charges are passed back to sales orders, if all charges (freight and non-freight) are passed back, or only non-freight charges are passed back. This designation is specified in Customer Setup using the value in the Bill Direct Purchase Order Addons field.
Order Entry Addon: Select the sales order addon to tie to this PO addon. If you pass Direct Order PO addons back to the tied sales order, you must associate each PO addon with a sales order addon. This process is controlled by the option, Bill Direct PO Addons To Sales Orders, in SA Administrator Options-Documents-Sales Orders-Back Orders. When a DO PO is received and the sales order is filled, the system applies direct PO addons to sales orders that are either DO sales orders or regular sales orders with direct sales order lines. The PO addon is “passed back” to the sales order addon that is specified here. Sales order addons are set up in SA Order Entry Addon Setup.

Reason Unavailable

Set up types of reason codes and descriptions that can be assigned to products when they become unavailable for sale. The codes are used during transaction entry and receiving functions. If you frequently use reasons in a transaction entry or receiving function, you should set it up in this table. Examples include damaged, incomplete, recalled, and obsolete. You can set up 99 reason codes.

Reason: A unique value that identifies this table value.
EDI Unavailable Type: Allows the system to cross-reference between the system Reason Unavailable code and the standard EDI codes for Receiving Condition as defined in the element table (Element 412) of the ANSI X12 Standards manual.
Unavailable Reason Type: Select Inspection to designate this unavailable reason as due to requiring an inspection of the product before it is available for sale. Storeroom-managed products can be defined as receive as unavailable in Product Warehouse Product Setup. In Purchase Receipt of Inventory Entry and Transfer Receipt of Inventory Entry, these products are automatically received with their quantity designated as unavailable, with a reason of Inspection. After the items are inspected, warehouse personnel can use Storeroom to move the quantity from unavailable to available. You can also use Product Unavailable Inventory Entry to move the unavailable amounts to On Hand. This updates On Hand and Unavailable quantities in Product Warehouse Product Setup.

Rebates (Customer Type)

Use this option to set up a customer rebate type. You use customer rebate types in PD Pricing Setup when you group rebate types and subtypes. You assign a rebate type to customers in Customer Setup.

Type: A unique value that identifies this table value.

Rebates (Product Sub Type)

Rebate sub types are used to identify subgroups of rebate types for products. You can specify rebate sub types on Rebate Type records in PD Pricing Setup. You can assign rebate sub types to products in Product Warehouse Product Setup or Product Catalog Setup.

Sub Type

A unique value that identifies this table value.

If the Rebate by Contract Line Number option in SA Administrator Options-Products is selected, you cannot create a rebate sub type that starts with LN#-. When you create a Rebate Type Rebate as a manual rebate, you must use either a rebate sub type or a contract line number. Both values are saved to the same field in the same system table. Contract line numbers are prefaced with LN#- to differentiate them from a rebate sub type.

Vendor

You can limit a rebate sub type to a specific vendor. If you specify a vendor in this field, specify the same vendor in PD Pricing Setup.

Rebates (Product Type)

Rebate types identify rebates for products. You can specify rebate types on Rebate Type records in PD Pricing Setup. You can assign rebate types to products in Product Warehouse Product Setup and Product Catalog Setup.

Type: A unique value that identifies this table value.
Vendor: You can limit a rebate type to a specific vendor. If you specify a vendor in this field, specify the same vendor in PD Pricing Setup.

Reference

Reference codes are used to set up a description for standard references that occur during setups and transaction entry functions, such as:

Customer Cash Receipt Entry
Sales Order Entry
Sales Commission Setup
Purchase Order Entry
Purchase Demand Center Entry
Transfer Entry
Transfer Shipping Entry

If you frequently use certain references for a setup or transaction entry function, use the Reference table type to specify a user-defined reference code that will enforce consistency for repetitive transactions or setup functions.

Report Schedules

Report Schedule types are based on the values you specify in SA Table Code Value Setup. When you set up a new stored report, you must select from the schedule and time types you set up here. These Report Schedule types allow you to automatically run stored reports at predetermined intervals. Create your Report Schedules types using either Date Repetition or Time Repetition, or a combination. The schedule name and description you specify should provide a meaningful and discernible type; for example, ID=15th, Description=15th of the Month.

Day

The date the report will run. Specify an asterisk (*) to indicate all days. The days must be specified by their number. For example, 16 for the sixteenth day of the month. You can also specify la for the last day of the month. If you specify more than one day, separate them with a comma, without spaces following the comma.

If you also make an entry in the Weekday field, the weekday entry and any day entry made here must both be true if your report is going to print.

End Time

Specify the stop time of a time frame to create a report schedule type that runs within or outside of business hours. For example, set a report to run every Wednesday, every 10 minutes, between 6:00 AM and 7:00 PM. Use the time chooser to select the time from the drop-down fields. If you are operating in the United States, specify the time in 12-hour increments and use the am or pm designation.

Minutes

If you select Minutes in the Time Repetition field, specify the minute interval in this field. For example, if you want the report to run every 10 minutes, specify 10.

Month

The months the report will run. Specify an asterisk (*) to indicate all months. The months must be entered by their number (for example: March = 3). Enter multiple months by entering their numbers followed by a comma (do not include a space after the comma). This allows the report to run only in the months specified.

Schedule and Description

A unique value that identifies this table value. The Schedule name and description you specify should provide a meaningful and discernable type. For example, ID=15th, Description=15th of the Month.

Start Time

Specify the start time of a time frame to create a report-schedule type that runs within or outside of business hours. For example, to set a report to run every Wednesday, every 10 minutes, between 6:00 AM and 7:00 PM, use the time chooser to select the time from the drop-down fields. If you are operating in the United States, specify the time in 12-hour increments and use the am or pm designation.

Time Repetition

Indicate the frequency with which you want the report to print on the days you have specified. Indicate if you want the report to print every x Minutes, Quarter Hour, Half Hour, Hour, or Bi-Hour on the days you have specified. Select None to have the report print only after on the days specified.

Weekday

The days of the week the report will run, using the first two letters of each weekday as the code; for example: Monday = mo, Tuesday = tu, Wednesday = we, Thursday = th. A comma is used to separate multiple days (without spaces). Specify an asterisk to indicate all weekdays. For example, to run the report Monday through Friday, specify mo,tu,we,th,fr. Remember, if you have entries in both this field and the Day field, they must both be true for your report to print.

Year

The year the report will run. Specify an asterisk to indicate all years. To specify exact years, you can enter either the four digit or two digit year designation; for example: 2016 or 16. To enter multiple years, you must separate them with commas, without spaces.

Size Type

If you use Warehouse Manager, set up table values after you set up the SA Administrator Options. Table values are required when setting up bin locations and cross-references by size type. Table values help categorize and organize the bins.

Size Type Value: If you use Warehouse Manager, you must set up user-defined bin size types. In Product Warehouse Product Setup, this size type can be used to restrict the size of bin type this product can be stored in. Restrictions keep processing timely using the Purchase Pre-Receiving Report. In the SA Table Code Value Setup function, select Size Type. Click Create. Specify a size type value and a short description. The value is alphanumeric and is used in conjunction with WM Bin Location and Product Setup, WM Cross Reference by Size Type Setup, and Product Warehouse Product Setup. Common examples of size types are Drawer, Standard, 8x12, 3"peg, 40x48 pallet.

Storefront Corporate Group

Storefront Corporate Group

Create a Storefront Corporate Group to associate a set of customers with a larger entity (corporate group). For example, if you have branches of a company set up as distinct customers in Distribution SX.e and want to associate the branches with the main customer record.

See the Infor Distribution SX.e Integration Guide for Storefront.

Supplier Group

If you use the Product Import module, and specifically PI Price Cost Multiplier Setup, you must set up one or more supplier groups. PI Price Cost Multiplier Setup is used to set up specific calculation styles based on supplier group and, optionally, warehouse. The supplier group is used during the import process to calculate new prices and costs, and to determine how records are updated.

Suppler Group

A supplier group may encompass several price types and categories, or may be set up as a different subset of price/cost information altogether. This means you may have to set up a PI Price Cost Multiplier Setup record for each supplier group, resulting in several price/cost multiplier records for one import type. Supplier groups are user-defined values, so the setup is not controlled by Distribution SX.e, nor are they table-driven.

The supplier group record that is used depends on the Product Catalog Setup or Product Setup records. When an item is imported, Distribution SX.e checks for an existing product record. Based on the supplier group defined on that product or catalog record, the PI Price Cost Multiplier Setup record is validated and its price/cost multipliers are applied. If a product record is not found, and Distribution SX.e determines the line item is a new product, the supplier group defined on the PI New Item Default Setup record is used. If no supplier group is defined on either the Product Catalog Setup or Product Setup record, the line item will not be imported and the product will not be updated by Product Import.

Tax Groups

Tax groups 1-5 are set up in SA Company Setup. Expanded tax groups 6-99 can be set up here. Typically expanded tax groups are used for industry taxes. When enabled, industry taxes are calculated during sales order entry. You must enable the use of the expanded tax groups by selecting the Allow Expanded Tax Groups option in SA Setup Company-Taxes. Typically, the company setting for Tax Interface must be set to System Rates. The Tax Method must be set to Sales Use Tax (SUT).

Tax Override

Reason

Use this type to set up tax override reasons. Examples might include Resale, Nonprofit, or Tribal Government. Depending on operator security set up in SA Operator Setup, you can override taxes that default on an order by selecting the Tax Override option in Sales Order Entry-Taxes and Totals and specifying the tax override value in the adjacent Reason field.

Overriding taxes on orders should occur infrequently, and you must use caution when overriding the Taxable option on the Taxes and Totals view. Changes to the taxable type roll to all previously entered lines, and taxes are recalculated. The new taxes also apply to new lines entered. Changes to any values on the Taxes and Totals view automatically change the Taxable type to manual. If you select the Tax Override option, then no taxes are calculated thereafter. You can view any tax exceptions on the Sales Exceptions Report.

Territories

Territory: A territory is a user-defined value that is used to further classify a customer geographically. Specify a unique value that identifies a territory. The value can be can be numeric or alphanumeric.

Unit of Measure

Note: If you use the Product Import module, use the Unit of Measure table type, instead of the Unit Conversion table type. For Product Import, the EDI Unit of Measure and the Unit Conversion Type values are used in conjunction with the stocking unit from the import file on the Product Extended Unit Conversion Setup record. During Product Warehouse Product Setup processing, the system validates whether a Product Extended Unit Conversion Setup record exists for the current product and the standard pack unit imported from the flat file. If no Product Extended Unit Conversion Setup record exists, then one is created using the standard pack unit and the multiplier imported from the flat file, and the EDI unit of measure and conversion type you set up in this SA Table Code Value Setup table type for that unit.

EDI Unit of Measure

This field is required if you use Electronic Data Interchange (EDI). Specify the Unit of Measurement Code as defined in the element table (Element 355) in the ANSI X12 Standard manual.

Unit Conversion Type

The unit conversion type defines how the unit conversion is applied to the selling unit during Sales Order Entry or Purchase Order Entry.

If you select Multiple, specify a decimal value for the Stocking Units in This Unit field. The system multiplies the amount you enter in the Stocking Units in This Unit field by the stocking unit to determine the selling unit. For example, if you stock an item by the board feet, but sell it in one unit made up of 10.5 board feet, your unit conversion factor would be 10.5.
If you select Fraction, the system multiplies the stocking unit by the fractional unit of measure to determine the selling unit. For example, if your stocking unit is a case of 12 items which you sell individually, your Units in a Stocking Unit would be 12.

You can only specify a decimal value if you select a multiple unit conversion type.

Unit of Measure

A unique value that identifies this table value. Examples are Each, Case, or Pkg. Six types of units are relevant in Distribution SX.e: stocking unit, standard pack, selling unit, counting unit, buying unit, and transfer unit.

Usage/Order Qty Override

User-defined codes used in Product Warehouse Product Setup. Product Administration Month End Processing Report fills the Product Warehouse Product Setup record with product usage information. If those usage figures must be overridden on the warehouse product record, a usage override code can be associated with it. Reasons to override may include sales, closeouts, stockouts, or single buys. Possible usage/order quantity override codes you can define are:


Code	Description
12	The order quantity has been reduced to a one year supply. You cannot enter more than a one year supply.
W	The order quantity has been increased to a two week supply. You cannot order less than a two week supply.
3S	For seasonal products, you can order a maximum of a three month supply.
R	The order quantity is too small to be included in the next replenishment cycle and will be stocked out; therefore, the order quantity is increased to be included.
UR	The calculated order quantity is less than the usage used during the review cycle and will be set to the usage quantity used during the review cycle.
ST	If a standard pack unit exists, the order quantity is rounded up or down to the nearest standard pack. If the order quantity is less than ½ of a standard pack, no rounding is done.
BY	If a buying unit exists (instead of a standard pack), the order quantity is rounded up or down to the nearest buying unit. If the order quantity is less than ½ of a buying unit, no rounding is done.
O	The order quantity has been manually overridden.
SO	The product has been out of stock for a total of more than 15 days in the month. The override usage defaults to the average monthly usage as calculated by Product Administration Month End Processing Report.
US	There is an unusual sale, so this transaction is not included in the usage calculation.

Reason: A unique value that identifies this table value.

User Group

Use this table to create user groups that you can assign operators to. User groups are assigned in SA Operator Setup and are used to clear multiple operator sessions in SA Connection Inquiry. This user group is different than event manger user groups.

Note: This functionality is part of an approval process that helps to meet some of the requirements of the Sarbanes-Oxley Act.

Group: A unique value that identifies this table value.

VA External Processes

The Value Add (VA) module interfaces with Total Warehouse Logistics (TWL) and lets you track your work-in-process inventory, and the time and cost of labor used in producing the finished item. You must define sections for VA orders before you can set up product defaults and enter the finished product in a transaction entry function.

External

A unique value that identifies this table value.

External Vendor #

The vendor you specify in this field is the external service vendor that you are shipping components to for processing. A record can be set up for each service vendor you use or you can set up a generic record by leaving this field blank. The vendor must be set up in Vendor Setup.

Or Warehouse

If you are shipping components to another internal fabrication warehouse, specify that warehouse in this field.

Ship From

In the Extended section, specify the external service vendor ship from that you are shipping components to for processing.

In the Destination section, specify the destination vendor’s ship from, if applicable.

Vendor

This is the destination vendor number.

VA Inspection

Inspection: A unique value that identifies this table value.
Inspection Warehouse: Specify the warehouse that is performing the inspection. This section is not applicable to a TWL warehouse.

VA Internal Processes

Internal: A unique value that identifies this table value.
Internal Processing Warehouse: This is the internal fabrication warehouse that components will be sent to. You can create a generic record by leaving this field blank.
Or Warehouse: If you are shipping components to another internal fabrication warehouse, specify that warehouse in this field.
Ship From: This is the destination vendor’s ship from, if applicable.
Vendor: This is the destination vendor number if the fabrication is sent to a service provider for an external processing section.

VA Inventory Components

Components: A unique value that identifies this table value.
Or Warehouse: If you will be shipping components to another internal fabrication warehouse, specify that warehouse in this field.
Ship From: This is the destination vendor’s ship from, if applicable.
Vendor: This is the destination vendor number that the inventory components are shipped to if an external (EX) section must be processed.

VA Inventory Returned

This refers to product put back in to inventory when it is not used in the inventory process (surplus).

Inventory IN: A unique value that identifies this table value.

VA Specifications/Instructions

Free-form text that can be included and printed for the external service vendor or the internal fabrication department, or both.

Specifications: A unique value that identifies this table value.

Vendor Type

Type: This table populates a field that is available on each Vendor Setup record. You can use this table-driven field to tie similar vendors together for reporting purposes. Vendor Entry Pay Invoices Due Report and Vendor Cash Requirements Report contain a vendor type range that you can use.

Warehouse Group

A warehouse group can be assigned to an operator in SA Operator Setup-Static Information. The warehouse group determines which warehouses an operator can view and select inventory in Sales Order Entry, Job Management, and Transfer Entry. You can set up a warehouse group by creating a group and selecting one or more warehouses to the group.

Available Warehouse: Lists all warehouses created in Product Warehouse Description Setup. The list includes the warehouse code and name.
Group: A unique value that identifies this table value.
Selected Warehouse: Lists all warehouses you have added to this warehouse group. The list includes the warehouse code and name.