SA Table Code Value Setup field descriptions

These fields are listed alphabetically for each table type.

Intrastat Terms of Delivery

Delivery: If you use the Value Added Tax (VAT) integration, delivery terms can be tracked for all customers and vendors in EU member states. Delivery terms indicate what part of the costs and risks the buyer or seller of goods has agreed to take on as part of the contract of purchase or sale. You may be required to provide delivery terms information based on the total value of dispatches and arrivals. Delivery terms codes are defined in SA Table Code Value Setup and assigned to your customers and vendors in Customer Setup and Vendor Setup. These codes must be mapped to their corresponding Delivery Terms code in the Tax Interface.

ION GL Account Conversion

You can cross-reference the values used for GL account code titles in Distribution SX.e with values that you want to include in BODs that are sent to ION. When a BOD is generated, the ION value in the table replaces the value used in Distribution SX.e.

For example, if the title for a GL account code varies in Distribution SX.e, you can set up cross-reference records that convert the different titles to one value. For example, if Accounts Payable and AcctsPay are specified as titles in GL Account Setup, you can convert these values to AP for ION.

GL Account: Specify a value from the Title field in GL Accounts Setup-General.
ION GL Account: Specify a replacement value for the value specified in the GL Account field.

ION Unit Conversion

You can cross-reference the values used for units of measure in Distribution SX.e with values you want to include in BODs sent to ION.

For example, if you do not use units of measure that are compliant with ISO (International Organization for Standardization) in Distribution SX.e, you can set up cross-references to ISO-compliant units of measure for ION. When a BOD is generated, the ION value in the table replaces the value used in Distribution SX.e.

Unit: Specify a value from the Unit of Measure field in SA Table Code Value Setup-Unit of Measure.
ION Unit of Measure: Specify a replacement value for the value specified in the Unit field.

Languages

Language: Distribution SX.e supports multilingual functionality. You can define one or more languages in SA Table Code Value Setup. To activate translation for reports, the language code you define must correspond to the language code in the OpenEdge Translation Manager System database (https://www.progress.com). Supported language codes are French and ES (Spanish). If you are generating your forms, such as invoices and delivery notes, using Print Format 4, you must specify FR or ES.
Translation Language: If you are doing business with Canadian customers, specify French in this field. If you specify any other value, you receive a message: Invalid Language - See System Administrator (4150). Contact your Infor account manager for more information.

LIFO Category

Category: LIFO (last in, first out) is an inventory valuation method that measures inventory changes from the beginning to the end of the year in terms of equivalent amounts so you can identify the net amount change. You can set up LIFO categories and use the amount-based valuation to include products in a particular LIFO category. Product Extended LIFO Valuation Setup uses the LIFO categories you set up.

Merchant ID Credit Cards

Merchant: If you accept credit cards as a method of payment, your Merchant ID may be part of the payment processing network. An "acquiring bank" is the financial institution where the merchant’s bank account is set up for receiving credit card payments. The “Merchant” receives a merchant ID from the bank. You may have separate merchant IDs for various locations, warehouses, or divisions. However, if you are integrated with CenPOS, the merchant ID used defaults from the Processor setup, or is set up in Product Warehouse Description Payment Type Setup. The Processor Vendor ID is the default merchant ID assigned and provided by CenPOS. Contact your CenPOS representative.
If you are going to use multiple-merchant processing with CenPOS, complete your standard integration, then a) define the merchant IDs to be used by your warehouses in SA Table Code Value Setup-Merchant ID Credit Cards, and b) associate the warehouses with the merchant IDs in Warehouse Description Payment Type Setup. You must work with your CenPOS representative, who provides you with Merchant User IDs and passwords and enables token sharing (allows a token to be shared at the warehouse level).

Non Taxable Reason

Reason: User-defined and used for reporting of nontaxable sales. You must set up the codes as 1-99. The code prints on the SM Government Tax Register Report. Several system functions use non taxable reasons, such as Customer Setup, Customer Ship To Setup, Product Warehouse Product Setup, and Sales Order Entry.
If you are integrated with AvaTax, the reason must match each AvaTax Entity Use Code. If you have previously used these one-character reasons for other than Entity Use Codes, we recommend you redefine the previously used characters. See the Infor Distribution SX.e Integration Guide for AvaTax for a table listing the valid Entity Use Codes in AvaTax.

Order Type Display

Order Type: Use this option to define the display name for Counter Sale (CS) and Stock Order (SO) order types. Changing the name of the CS or SO order type does not change the functionality of the system. The name you specify for each order type shows for all order types in error messages and fields and on reports.

Origin Code

Allow Editing in Order Entry

Select this option to allow users to change the Origin Code field in Sales Order Entry. Only users with Yes selected in the Allow Change of Order Origin Code field on their SA Operator Setup record can change the code. To prevent users from changing the code, regardless of their operator security, ensure that this option is clear. You may want to prevent users from changing the Origin Code on orders that are created by a background process.

Background Function

Select the background function that you are setting the origin code for. This is the function that was used to create the order in Distribution SX.e. This table shows the values that are available in the field:


Background Function	Internal Identifier
SX.api	API
CPQ configurator	CFG
Consolidated Invoice	CNI
Tool Crib	CRB
Counter Sales	CSO
EDI Import	EDI
Excel Import	EXL
Fulfillment Order	OFO
Job Management	JMO
Receive On Account	ROA
Storefront	STF
Storeroom	STR
Service Warranty	SWO
Other	OTH
User Selection	USR

All orders that are manually specified in Sales Order Entry should default with an origin code with a background function of User Selection, with the exception of Counter Sales orders and Received On Account transactions. Those automatically default with the origin code that you define with a Counter Sale (CSO) or Receive On Account (ROA) Background Function.

The origin code for the fulfillment order background process is added to the tied fulfillment orders that are created after the original fulfillment order is submitted.

Only one origin code should be assigned to each true background function. Multiple origin codes can be assigned to the User Selection background function.

Note: If a background function does not pass an internal identifier, the Default Order Origin Code defined in SA Administrator Options-Documents-Sales Order is used. For example, if you use a third-party application to create orders using API Full Order Maintenance (the SX.api Background Function) and you want to identify all orders created by this application with a unique code, you must pass the identifier in the API call. Otherwise, the origin code defined as the Default Order Origin Code is used.

Display in Order Entry Lookup

Indicate whether to display the order origin code in Sales Order Entry or Sales Order Entry-Copy Order Origin lookup. This prevents users from inadvertantly selecting certain codes from the lookup. Generally, codes are defined for background functions.

This selection applies to the origin code lookup grid only. If you maintain an order that was created by a background function with an origin code that is set up not to display in the lookup, the origin code still shows in the Order Origin field. If the origin code is also set up with Allow Editing in Order Entry option selected, you can override the defaulted code.

Note: Because a code does not show in the lookup does not mean the code cannot be specified in the Order Origin field. Any origin code set up in the SA Table Code Value Setup can be specified in Sales Order Entry.

Origin Code

Specify an order origin code using a maximum of four characters. This code is used to populate the Order Origin field in Sales Order Entry for orders created from outside of Sales Order Entry using background functions such as EDI, Storeroom, and Storefront, and for Counter Sale and Received On Account orders.

It also populates the Origin Code lookup table when a customer sales rep creates an order in Sales Order Entry, based on additional options in the Extended section. If the code is defined with a background function of User Selection and you also select to Display in Order Entry Lookup, the code can be selected from the Origin Code lookup in Sales Order Entry. If you require order origin codes for every sales order in SA Administrator Options-Documents-Sales Orders, this field is required in Sales Order Entry.

A unique order origin code should be created for each background and user entry function in the Extended section.

Sort Order Priority

Specify the order in which the origin code shows in the lookup on the Origin Code field in Sales Order Entry. Each code can be assigned a priority between 1 and 99. Multiple codes can have the same priority number. If you have selected the option, Display in Order Entry Lookup, order origin codes are displayed in the lookup based upon the priority sort order number, with priority 1 codes showing first, and priority 99 codes showing last. This allows you to set the most frequently used codes to show at the top of the lookup list.

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 pertain 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: 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, 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 system uses the average cost from Product Warehouse Product Setup to calculate the minimum margin. If average cost is zero, the system does not check the minimum profit margin 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.
See Personalizing the UI.

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

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: on theThe 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, the system does not use this account code. 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 system uses the account code specified in Uninvoiced Addons account code from the SA Operator Setup-Other Options record. 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. You can also specify rebate sub types for Vendor Product Groups in SA Table Code Value Setup if the group type is Rebate Type.

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. You can also specify rebate types for Vendor Product Groups in SA Table Code Value Setup if the group type is Rebate Type.

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.

Return Adjust Reason

Return reasons are user-defined and used in Sales Order Entry and Purchase Order Entry. The system uses the additional information you set up for this table type to control all returns from customers or to vendors. Set up these return/adjust reasons when your company uses standard reasons to explain why a customer is being issued a credit memo or returning merchandise. For example, you could set up codes for return of goods or exchange of goods. These user-defined reasons are displayed in Sales Order Entry when you enter a Return Merchandise (RM) order. Use the SM Return/Adjustment Analysis Report to print reports based on these return reasons.

If you are integrated with AvaTax or Vertex Cloud and use restocking fees, set these up in the Return Adjust Reason table. If you are integrated with Sovos GTD and use restocking fees, set these up in with a Restock Charge value.

Charge

Indicate if the Restock Charge value is an Amount or Percentage.

Credit Authorization Required

Select this option if you require credit authorizations to use specific reasons. Authorization security is defined for operators in SA Administration Authorization Security Setup. If an operator does not have authorization for specific credit reasons, the operator must seek assistance from a supervisor who can grant them the appropriate authorization to continue.

Credit/Rebill

Select this option to process the Correction order as a credit and rebill transaction when this Return Adjust Reason is specified on the order.

Include Rebates

Select this option to include vendor rebates on Correction orders when this Return Adjust Reason is specified on the order. Rebates can only be processed in credit and rebill transactions on CRs.

Include Serials

Select this option to include serial numbers on Correction orders when this Return Adjust Reason is specified on the order. Serial numbers can only be processed in credit and rebill transactions on CRs.

Reason

In the General section, the reason is a unique value that identifies this table value.

In the Extended section, you must have set up the Reason Unavailable in SA Table Code Value Setup before you can specify the reason here. Use the Reason field when the stock item returned is going back to the vendor or cannot be returned to inventory because it is covered by a warranty, it was a special order, or the item is damaged.

Require Invoice # on CR

Select this option to require an invoice on Corrections orders that are processed as credit and rebill transactions or net transactions. This option is automatically selected if you select the Credit/Rebill option.

This option is further controlled for individual operators using Authorization Security. The security level for the authorization point, reqinvcrfl, can be set in SA Authorization Security Administration for one or a group of operators. You can set their Security Level to Not Authorized, Authorized, or Grant Authority. For example, if a user's Security Level is Not Authorized, and a return reason requires an invoice number, but that information is not available, they are not permitted to enter the Correction unless a supervisor with Grant Authority temporarily overrides the requirement.

This value is used by Sales Order Entry, including Shopping List functionality, and the Sales Order Batch Update Report.

Require Invoice # on RM

Select this option to require an invoice number on Return Merchandise orders. Each return stores the original invoice number upon which the return is based. The billed price and cost are also included on the return to provide an audit trail of how and where returns originated.

This option is further controlled for individual operators using Authorization Security. The security level for the authorization point, reqinvfl, can be set in SA Authorization Security Administration for one or a group of operators. You can set their Security Level to Not Authorized, Authorized, or Grant Authority. For example, if a user's Security Level is Not Authorized, and a return reason requires an invoice number, but that information is not available, they are not permitted to enter the Return Merchandise order unless a supervisor with Grant Authority temporarily overrides the requirement.

Restock Charge

Handling the return transaction is costly. Processing returns must either be recovered from the customer or vendor, or taken from profit. You can specify a return reason that includes a restocking charge to be subtracted from the customer’s credit. The restocking charge value can be a amount or percentage. The restock charge defaults in Sales Order Entry-Totals when you are entering the return order. You cannot override a restocking charge that is part of the return reason. If you use restocking charges, indicate the corresponding General Ledger account in SA Operator Setup or Product General Ledger Distribution Setup. If the system cannot locate the restocking account, the suspense accounts indicated on your SA Company Setup record are used, and you must make manual adjustments to correctly distribute the charge.

Return Type

Determines the disposition of the return. Valid return types are return to vendor, return to stock, unavailable, partial unavailable, and scrap.

A vendor return type causes the unavailable balance for the item to increase. It displays on the Sales Warranty Returns Report as a reminder to enter it on a vendor return.
A stock return type causes the item’s Product Warehouse Product Setup On Hand balance to increase during Sales Entry Invoice Processing Report.
An unavailable return type increases the item’s Product Warehouse Product Setup unavailable balance, but the item is not displayed on the Sales Warranty Returns Report.
A partial return type allows you to enter a quantity to be returned to stock and a quantity to be entered as unavailable.
A scrap return type indicates that returns assigned to this return/reason code will not be brought back to on hand or unavailable inventory. You must specify the Scrap Account number to associate the GL account number for the scrap write off. This effects both stock and nonstock returns.

Scrap Account

During invoice processing, if a scrap return type is found on a return line, then the item is written off and inventory is not updated. The write off posts to the GL account.

Tax Group

Ensure a Return Adjust Reason is set up for tax corrections.

Usage

Product usage is the core element of all inventory ordering controls. This usage determines when to order and how much to order, which has a direct effect on your customer service and stocking levels. The handling of usage as it relates to returns is critical to all aspects of inventory management. If returns never affect usage, you will probably be overstocked in certain situations. If they always affect usage, your customer service level may suffer. To help keep usage correct, you can indicate if each return reason affects usage. This gives you the capability to alter return usage requirements. When entering a return in Sales Order Entry, the Usage option is selected, but you can override it. If the customer has returned the product, you want this return to affect usage.

Warranty Exchange

Select this option if the return reason is a warranty exchange return reason. A warranty exchange is two transactions that occur simultaneously. The first transaction is for the return, and the second is for an exchange of the same item. Any return reason marked as a warranty exchange automatically generates both line items for the order. Cost and price are zeroed on each to allow the return to be invoiced without a false credit showing on the customer’s account and causing discrepancies in sales analysis. This functionality is designed to be used as an exchange, not a warranty service, which is why cost and price are zeroed out. Service Warranty is designed to specifically handle warranty servicing transactions.

Warranty Tag Required

Select this option if you require a warranty tag. The system does not validate the warranty tag, but you must specify a warranty tag during entry of the return before you can proceed.

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.

See Setting up WM table values.

Size Type Value: If you use Warehouse Manager, you must set up user-defined 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-Taxes 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.

Terms

Each customer carries a default payment terms code that describes the basic guidelines for discount, discount date calculation, and due date calculation. You can specify this information for each customer on the Customer Setup record and for each ship to on the Customer Ship To Setup record. It is important to be able to offer a variety of payment terms, so set up an applicable variety. During invoice processing, the system checks the terms and calculates these items:

Any applicable discount and the date through which the discount is offered (Discount % and Date).
The date by which remittance must be made in order to avoid service charges and possible credit ramifications (Due Date).
Whether the invoice can be split into several payments, each with a different due date (Split Payments).
Whether the cash discount can be overridden through Price and Discounting or Sales Order Entry.

# of Payments

If the Split Pay field is set to Yes, specify the number of payments the invoice should be split into.

C.O.D

Select this option to automatically select the COD option in Sales Order Entry. This does not affect the setting in Purchase Order Entry and Vendor functions.

Credit Card Only

Select the Credit Card Only option to enable entering credit card information on orders with zero lines to ship and the order is a hold transaction. Credit card transactions will be created as order lines begin to fill and ship. You must then select the Credit Card Type, as set up in SA Table Code Value Setup-Terms, that this option is associated with on the header of the sales order. You can also use Credit Card Only terms when tendering against an order with a shipped quantity.

SeeTendering zero quantity shipped orders.

Date

If the Discount Type field is set to Date, specify the date through which the cash discount is offered. This date establishes the date the discount period is over.

Date

If the Due Type field is set to Date, specify the due date of the invoice in this field.

Days

The length of your discount period. Specify the number of days from the invoice date that the discount is in effect. For example, for the terms of 2%/10, n30, specify 10 in this field.

Days

The length of your billing period in days. The number of days before the invoice becomes past due. For example, terms of 2%/10, n30 require you to specify 30 in this field.

Discount Type

Select Days if the terms are based on a specific number of days from the invoice or billing date. Select Prox if you will use the proximity method. Select Date if the discount type is based on a specific date. Select None if a discount type is not allowed. If you select None, the system sets the discount date to the invoice date.

DNBi Credit Limit

If you are integrated with Dun & Bradstreet web services (DNBi), use this field to optionally assign a default credit limit to be used in the SXAPIARCustomerMnt call. This limit defaults to zero. The terms default credit limit overrides the SA Administrator Options-Default credit limit if that default is not zero.

DNBi Interface

If you are integrated with Dun & Bradstreet web services (DNBi), use this option to indicate which terms determine whether a call is made to the DNBi credit check. This option is used in conjunction with other settings, such as the Country table type, SA Administrator Options-Integrations-DNBi Integration Options, and Customer Setup.

Due Type

Select Days to calculate the due date using a number of days from the invoice date. Select Prox to use the proximity method. Select Date to base the due date on a specific date.

EDI Date Code

If you use Electronic Data Interchange (EDI), specify the Terms Date Code as defined in the element table (Element 333) of the ANSI X12 Standards manual for EDI. This is a specific date code that describes the Terms Basis Date Code for orders that are transmitted to your customers or vendors through EDI.

EDI Terms Code

Specify the Terms Type Code as defined in the element table (Element 336) of the ANSI X12 Standards manual for EDI. This describes the Terms Type Code for orders that are transmitted through EDI.

Else Discount Through

If the Discount Type field is set to Prox, specify the day of the month this invoice is due if it has been invoiced after the cut-off day specified in the In By field. This is not required if the day specified is the same as the day specified in the Then Discount Through field, only one month later. Prox terms always work in one-month intervals. For example:

If invoiced by the 10th, discount is available through the 25th; otherwise, discount is available through the 10th. Specify 10 in the In By field. Specify 25 in Then Discount Through. Specify 10 in Else Discount Through.

In this example, no entry is made to the Else Discount Through field:

If invoiced by the 25th, the discount is available through the 10th. Otherwise, the discount is available through the following 10th. Specify 25 in the In By field. Specify 10 in Then Discount Through.

Else Due On

If the Due Type field is set to Prox, specify the day of the month this invoice is due if it has been invoiced after the cutoff day entered in the In By field.

Gross

This field is valid in Sales Order Entry only and allows you to calculate the terms discount based on a gross or net amount. If you leave this blank, the discount is calculated from line amounts and does not include addons or taxes. If you select Gross, the discount is calculated from the total invoice amount and includes taxes but not addons. So, if there is a taxable addon, the tax on the addon is included, but not the addon amount itself.

This field works in conjunction with the terms Override field which allows a different terms discount on each Sales Order Entry line. If both the Override and Gross options are selected, the discount amount is calculated on each line individually using the line discount percentage and the discount amount on the addons. Taxes are calculated using the terms discount percentage. The discount amount prints on the invoice and flows to Accounts Receivable. This field is not used in Customer Transaction Entry when invoices are entered.

Hold

Applies to vendor AP invoices only. Select Yes to hold all invoices with these terms. If an invoice is placed on hold in this manner, you must release it in Vendor Maintain Transaction Entry. If you use floor planning as a method to finance invoices from your vendors, you must set up specific terms that are used in these cases. If this terms type is for a floor plan, select Floor Plan in the Hold field to treat the discount date as the expiration date and the due date as the maturity date.

In By

If the Discount Type field is set to Prox, specify the monthly cutoff day for the terms discount. The system compares the day you specify to the invoice date. Only invoices posted through this day are included in this discount period. For example, if this field is set to 10, all invoices entered between the 1st and 10th day of the month are included in the discount period. Invoices specified on the 11th and all subsequent days in the month are not considered for the discount.

If the Due Type field is set to Prox, specify the day of the month (1-31), based on the invoice date for the invoice to be included in the due date period. The day specified here becomes the cutoff day for posting invoices each month to be included in this due date period.

Months

If the Discount Type field is set to Prox, use this field to add a number of months to the proximity calculations. Use this field to offer terms extended past a one month window.

If the Due Type field is set to Prox, specify the number of months to add to the calculation of the due date. This is used to offer terms extended as a one month window. For example, an invoice with prox 45 terms is due the 15th of the subsequent month.

Override

Applicable to Sales Order Entry and Price and Discounting. Select this option to allow a discount override by line item in Sales Order Entry, by PD Pricing Setup record, or by product in Product Setup if a pricing record does not exist. The override can be made at any time before invoice processing in Sales Entry Invoice Processing Report. Operators must have correct security in SA Operator Setup to override the discount.

Percent

The percentage of discount offered. The percentage range can be from 0.00% to 99.99%.

Split Discount

If you set the Split Pay option to Yes, select this option to split the discount available equally between the payments. If this field is cleared, the discount is eligible to be deducted from the first remittance only.

Split Pay

Select Yes to automatically split invoices into multiple payments.

Then Discount Through

If the Discount Type field is set to Prox, specify the day of the month through which this invoice is eligible for a discount. For example, if the In By field is set to 10, and you specify 25 in the Then Discount Through field, all invoices entered between days 1-10 of the month are eligible for the discount if fully paid before the 25th of the month.

Then Due On

If the Due Type field is set to Prox, specify the day of the month (1-31) this invoice is due.

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 Price Groups

Frequently a vendor’s price type is different from a Distribution SX.e price type and the record can exceed the system's price type length. Use this option to create a cross-reference record that allows a vendor to send a rebate using their own price type grouping (maximum of 10 characters), although still linking to a Distribution SX.e product price type (maximum of 4 characters), allowing the system to create or update the rebate record with the Distribution SX.e price type.

In Sales Order Entry, the system looks for rebates (Product Price Type-Rebate Level 3) based on the Price Type designated in Product Warehouse Product Setup-General. This cross reference is used when running EDI Entry Processing Contract Pricing Report in update mode.

If the vendor uses the same price type values that are stored in the system for the product price type, a vendor price groups cross reference entry is not required. EDI Entry Processing Contract Pricing Report looks for a match in the SA Table Code Value Setup-Product Price Type value if an entry is not found in the Vendor Price Group cross reference setup.

Price Group: Specify the vendor's price group.
Price Type: The price type associated with the Vendor field and Price Group field is used as a cross-reference when running EDI Entry Processing Contract Pricing Report in update mode. This field must be a valid SA Table Code Value Setup-Product Price Type value. If the vendor uses the same price type values that are stored in the product record in Product Warehouse Product Setup-General for the product price type, a vendor price groups cross-reference entry is not required.
Vendor: Specify the vendor's number.

Vendor Product Group

As part of the EDI 845 inbound (Price Authorization Acknowledgment/Status), if your vendor uses rebates in conjunction with product groups, allows you to create and use Vendor Product Groups to accommodate this data and help streamline processing. In SA Table Code Value Setup, if you are setting up a Vendor Product Group, specify a vendor and select or create a Product Group.

Description

The description displays the values you have selected in the additional fields that are displayed with the Vendor Product Group Type that you selected. For example, if you select a Vendor Product Group Type of Rebate Type, the additional fields of Rebate Type and Rebate Sub Type are displayed. The values you select in these fields become the description.

Operand | Modifier Amount

Optionally, you can use the Stock Pricing Adjustment section to apply a modifier to an existing rebate for a Vendor Product Group, using a rebate calculation type of Percent or Net. The available operands allow you to, for example, combine an additional rebate with an existing rebate or calculate the net of two rebates. Select the appropriate operand, then specify a number in the Modifier Amount field. The system calculates the total rebate amount or percentage based on the incoming data in the EDI 845in file when the EDI Entry Processing Contract Pricing Report is run. If the report is run in update mode, the totaled rebate displays in the specific rebate record's PD Pricing Setup-Required view. That rebate is applied whenever that product is sold.

Product Group

Specify the group code. The group code must match your vendor's group code being sent in the 845in document.

The fields that are displayed depend on the Vendor Product Group Type value. Use these fields to further define the group.

Vendor

Specify a vendor ID number. This associates the Vendor Product Group with this vendor. All of the existing Vendor Product Groups show in the list area, unless you have specified a vendor ID number, in which case only the Vendor Product Groups existing for that vendor are listed.

Vendor Product Group Type

The list contains the types which are used to associate the Group Code and Vendor to a specific rebate record type that is used in PD Pricing Setup.

Based on your selection, additional fields are displayed, allowing you assign the specific values set up in the system in SA Table Code Value Setup.

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.

SeeSet up a warehouse 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.