SOE COST General Control Maintenance Records

The following control maintenance records belong to the COST area within the SOE (Sales Order Entry) category. COST should not be confused with pricing. For pricing control maintenance records, see SOE PRICE General.

Always Log The First Non-Zero Cost For Products

New in Release 9.0.3

Indicate if you want to log the first non-zero cost for products. ClosedMore:

Options

Yes - When a product and branch price is updated without actually changing the value, such as an old price at $1.25 and the new price is $1.25, then the product and branch history is checked for price activity. If there is no price history, then a price change for the current price is recorded. For example, if the product inherited the price from another branch, then the current price is recorded.

Note: If the product histories are long and the price updates are infrequent, then this check for past price changes can take several minutes for a single product. This check may slow RF processing.

No -  This is the default. No logging occurs for this product cost change. All standard cost-change updates are still logged. We recommend leaving the default setting unless instructed by Eclipse Support.

Default Value(s)

No

Action if set to Null

None.

Additional Information

None.

Apply Rebates From Sell Group Rebate Table

Use this record if your company applies rebates for sell groups. When a customer orders a product, the price is typically derived from the item's price sheet and the active sell matrix. However, you can set up rebate tables at the sell group level to apply rebates to products in a sell group.

The system checks the sell matrix for active sell group rebates, then checks for defined rebate tables for the product's sell group. If the product's sell group has defined rebate tables, the system uses the most recent table relative to the order's pricing date to apply the rebate. ClosedMore:

Options

Indicate whether the system should check the sell matrix for active sell group rebates and recalculate COGS when a user updates a price on a sales order generation.

  • Yes - The system checks for active sell group rebates.

  • No - The system does not check for active sell group rebate, even if rebate tables are set up.

Outcome of setting this control record

When a rebate applies, then the system does the following:

  • Subtracts the rebate amount from the item's cost of goods sold (COGS) and commission cost (COMM).

  • Displays R as a suffix to any costs in order entry modified by a sell group rebate.

  • Adds a line to the Order Change Log stating a sell group rebate was applied to the product and the order generation affected.

For more information, see Defining Sell Group Rebates in Price Management.

Default Value(s)

No

Examples

For example, use this control maintenance record if you require a method of applying rebate amounts across an entire sell group. The functionality must have effective dates per sell group for the rebate tables so when one rebate table expires, the new rebate table activates automatically.

As a function of these newly required rebate tables, the customer requires ability to set different rebate amounts for different selling prices across sell groups.

Dependencies

  • Sell Group Maintenance - Set up the rebate tale for each sell group using this rebate logic. For more information, see Creating Buy and Sell Groups in Price Management.

  • Sell Matrix Maintenance - For each rebate matrix that is teid to the sell group you need to set the Check Sell Group Rebates flag to Yes. For more information, see Defining Sell Group Rebates in Price Management.

Action if set to Null

The same as if set to No.

Additional Information

None

Average Cost Settings

Options

  • Recalc Avg Cost as of Original Receipt Date - Indicate if you want to use the original receipt date on an order when recalculating average cost. The system takes the Previous On Hand and the Previous Cost from the original receipt date of the order. If set to No, the system gets the Previous On Hand cost in real time.

    Note: If set to Yes, the system adds an asterisk to the order ID number in the Branch Cost Inquiry Screen when average cost is updated.

  • User To Be Messaged When Average Cost Is Modified - Select which user in the system to alert when the average cost has changed on an order.

Outcome of setting this control record

See above

Default Value(s)

Yes

Action if set to Null

Same as No.

Additional Information

None.

Base Minimum GP% Price Check Off COMM-COST

Use this record if you have overrides in either Price Line Maintenance, Product Maintenance, or User Maintenance that limit a user’s ability to lower a price on an order based on a gross profit percent (GP%). You can have the system use commissions cost (COMM-COST) instead of the cost of goods sold (COGS) value. ClosedMore:

Options

  • Yes - The system bases the price check off COMM-COST.

Note: Salespeople who can see the COGS value may question why they cannot enter a unit price that is within the percentage override designated in Price Line, Product, or User Maintenance.

  • No - The system bases the price check off COGS cost. This is the default.

Outcome of setting this control record

If set to Yes, the system bases the minimum GP% price check in Sales Order Entry on COMM-COST for an item, otherwise, the system uses the COGS value.

Default Value(s)

No

Action if set to Null

The same as if set to No.

Additional Information

Best Cost Check Through All Matrix Cells For Sales Orders

Use this record to have the system check the entire pricing hierarchy for the best cost override to determine the cost on a sales order. This record applies to both commissions costs (COMM-COST) and cost of goods sold (COGS). This control maintenance record does not apply to direct sales orders and does not change pricing. ClosedMore:

Options

  • Yes - Searches through the entire hierarchy to find and uses the cost override with the lowest cost. When set toYes, this record overrides any value entered in theBest Cost Checkfield in Sell Matrix Maintenance.

  • No - Uses the first cost override found to determine the cost on the sales order. When set to No, the system checks the value entered in the Best Cost Check field in Sell Matrix Maintenance.

Outcome of setting this control record

If there are no cost overrides found through the entire pricing hierarchy, then the system uses the standard default cost on the order.

Default Value(s)

No

Dependencies

If the Best Price Check Through Matrix Cellscontrol maintenance record is set to No, then the system respects the standard pricing hierarchy for pricing, even if the cost continues to search through the hierarchy.

Action if set to Null

The same as if set to No.

Additional Information

For information about the pricing hierarchy, see Pricing Matrix Hierarchy Details in Pricing Management.

Copy COST To COGS For IAO Items In SOE

Use this record to indicate if you want the system to copy the COST value to the cost of goods sold (COGS) value when a user adds an inventory account override (IAO) item to a sales order. This record only applies to adding an item to a sales order not orders in Purchase or Transfer Order Entry. You must set up an IAO cost for each branch. An IAO item is a stock or nonstock product that has been assigned an Inventory Account Override. ClosedMore:

Options

Select from the following:

  • Yes - Copies the COST value of the IAO item to the COGS value.

  • No - Does not copy the COST value of the IAO item to the COGS value.

Outcome of setting this control record

If set to Yes, the system copies the COST value of an item that has an inventory account override when it is added to a sales order.

Default Value(s)

No

Examples

 

Dependencies

The system respects all other control maintenance records related to copying COGS and COST, such as Change Both COGS And COMM-COST On Override.

Users must be authorized to manually override COST, COGS or PRICE values of an IAO item on a sales order.

Action if set to Null

The same as if set to No.

Additional Information

For information about assigning override accounts, see Step 8 in Creating Price Lines in Pricing Management.

Direct COGS Always Vendor Price

Use this record to indicate if the system should use vendor costs on the sales order side of a direct order. ClosedMore:

Options

For each branch, indicate whether the system uses vendor costs on the sales order side and purchase order side of a direct sale.

Note: We recommend using option B.

The purchase order COGS and sales order COGS are always the same when you use options N or Y. They may be the same or different when you use options R or B.

N - Uses the vendor cost, unless a sell matrix override exists. ClosedConditions for using No:

  • If a sell matrix cost override exists, the system uses the override as the cost on both the sales and purchase order sides of a direct sale.

  • If a sell matrix cost override does not exist and a vendor buy matrix does exist, the system uses the cost from the buy matrix as the cost on both the sales and purchase order sides of a direct sale.

  • If a sell matrix cost override and a vendor buy matrix do not exist, the system uses the value assigned to the local basis name that is mapped to the global DFLT-COST basis name (from the All/All Buy Matrix) on the price line as the cost on both the sales and purchase order sides of a direct sale.

Y - Always uses the vendor cost. ClosedConditions for using Yes:

  • If a vendor buy matrix exists, the system uses the cost from the buy matrix as the cost on both the sales and purchase order sides of a direct sale.

  • If a vendor buy matrix does not exist, the system uses the value assigned to the local basis name that is mapped to the global DFLT-COST basis name (from the All/All Buy Matrix) on the price line as the cost on both the sales and purchase order sides of a direct sale.

R - Uses the vendor REP-COST, unless a sell matrix override exists. ClosedConditions for using R:

  • If a sell matrix cost override exists, the system uses the override as the cost on the sales side of a direct sale and the value assigned to the local basis name that is mapped to the global REP-COST basis name on the price sheet as the cost on the purchase order side of the direct.

  • If a sell matrix cost override does not exist, the system uses the value assigned to the local basis name that is mapped to the global REP-COST basis name on the price sheet as the cost on both the sales and purchase order sides of a direct sale.

B - (Recommended) Uses different costs, depending on whether rebate information exists. ClosedConditions for using B:

  • If a sell matrix cost override and rebate information exist, the system uses the override for the sales order side and the cost from the vendor buy matrix, if one exists, or the value assigned to the local basis name that is mapped to the global DFLT-COST basis name (from the All/All Buy Matrix) on the price line on the purchase order side of a direct.

  • If a sell matrix override exists but rebate information does not exist, the system uses the override as the cost on both the sales and purchase order sides of a direct sale.

  • If a sell matrix override does not exist, the system uses the cost from the vendor buy matrix, if one exists, or the value assigned to the local basis name that is mapped to the global DFLT-COST basis name (from the All/All Buy Matrix) on the price line as the cost on both the sales and purchase order sides of a direct sale.

Outcome of setting this control record

See condition descriptions above.

Examples

None.

Dependencies

  • If this control maintenance record is set to R (REP-COST), then the Change Both COGS And COMM-COST On Overridecontrol maintenance record is ignored on direct sales orders.

  • For the R setting in this control maintenance record to work, then the Change Both COGS And COMM-COST On Overridecontrol maintenance record must be set to 0 (No) so costs on the sales order side and purchase order side of a direct are not made to be the same.

  • If this control maintenance record is set to R, then the Update Generic Cost During Processingcontrol maintenance record must be set to No or Exclude Directs for the system to process correctly.

Default Value(s)

No

Action if set to Null

The same as if set to No.

Additional Information

This control maintenance record does not apply to junior orders created from a master job bid order. If you need to change the COGS cost on a junior order, you need to do so manually.

Disallow Copying Of COGS Or Cost To A New Sales Order Bid

Use this record to restrict users from copying cost of goods sold (COGS) or Cost information from an existing sales order to a new sales order bid regardless of their permissions. ClosedMore:

Options

  • Yes - Does not allow users to copy COGS or Cost information from an existing sales order to a new sales order bid regardless of their authorizations on the COGS.EDIT and SOE.COST.EDIT authorization keys.

  • No - Allows users to copy COGS and Cost information from an existing sales order to a new sales order bid. User may select to copy Cost/COGS if the following required authorization keys are assigned: SOE.COST.EDIT and COGS.EDIT.

  • Default - Allows users to copy COGS and Cost information from an existing sales order to a new sales order bid, regardless of their authorization settings.

Outcome of setting this control record

If you select the Yes option, the following fields on the Copy to Sales Order Bid default to N:

  • Copy Original Prices? (Y/N)

  • Copy Original Costs? (Y/N)

  • Copy Original COGS? (Y/N)

Default Value(s)

No

Action if set to Null

The same as if set to No.

Additional Information

For more information, see Creating and Copying Bids.

Global Basis Used For In-Stock Cost Calculation on Rebates

New in Release 8.7.9

Select the global basis you want to use to calculate cost comparisons for rebates as follows. Eclipse calculates COST using this basis compared to the cost calculated by the override, if the Best Cost Check flag is set to All in Price Maintenance. If the Best Cost Check flag is set to All and this control maintenance record contains a selection, then Eclipse checks if the stock cost is lower, meaning better, than the override entry. The system then ignores the cost overrides in the hierarchy and the stock cost is used.

Include Item With Zero Average Cost In Average Cost Calculation

Use this record if your company runs reports using average cost or if your Cost of Goods Sold basis is set to Average Cost. By default, the system includes on-hand items with $0.00 average cost in the average cost calculation when additional inventory is received. This control maintenance record affects average cost and landed average cost. ClosedMore:

Options

  • Y - Includes on-hand items with $0.00 average cost in the average cost calculation. This allows for the current on-hand quantity to offset the new average cost calculated.

  • N - Does not include on-hand quantities with $0.00 average cost in the average cost calculation.

Outcome of setting this control record

 

Examples

Example when set to Yes:

  • On-hand qty = 9 with current average cost = $0.00

  • Receive 1 with $10.00 cost

  • New average cost = $1.00 ($0.00*9 + $10.00*1) / (9 + 1)

Example when set to No:

  • On-hand qty = 1 with current average cost = $0.00

  • Receive 1 with $10.00 cost

  • New average cost = $10.00 (system did not include $0.00 average cost on-hand item)

Dependencies

 

Default Value(s)

No

Action if set to Null

The same as if set to No.

Additional Information

Include Tagged Quantities In Cost Calculation

Use this record if your company runs reports using average cost or if your Cost of Goods Sold basis is set to Average Cost. Indicate which tagged quantities the system includes in the cost calculation. Use this control maintenance record to keep inventory value and your G/L in balance. Click More for more information. ClosedMore:

Options

  • N - None. The system does not include tagged quantities of any kind.

  • T - Tagged quantities from transfers. When transfers are received and tagged to sales orders, the quantities are used to recalculate average cost.

  • P - Tagged quantities from purchase orders. When purchase orders are received and tagged to sales orders, the quantities are used to recalculate average cost.

  • B - Tagged quantities from transfers and purchase orders. When both transfers and purchase orders are tagged to sales orders, the quantities are used to recalculate average cost.

Examples

Assume the following:

  • Update Cost On Sales Order From Tagged Transfer Order control maintenance record is set to No.

  • Branch 2 receives a purchase order for 1 item at $10.00. The average cost is $10.00, G/L is $10.00.

  • Branch 2 creates sales order for 1 item at $10.00, however that item is already committed.

Do the following:

  • Tag the sales order to a transfer and transfer from branch 3 to branch 2 at $100.00.

  • Receive the transfer. G/L is now $110.00

How the system works with these assumptions:

  • Because the control maintenance record does not update cost on the sales order from a transfer when the items ships, the item ships at $10.00.

  • G/L is now $100.00, however inventory value is still $10.00.

  • If the Update Cost On Sales Order From Tagged Transfer Ordercontrol maintenance record is set to Yes, then when the transfer is received, average cost becomes $55.00.

  • When the sales order ships, the system recalculates COGS on the order to $55.00.

  • This set of events makes the G/L $55.00 and the inventory value $55.00.

  • If the Update Cost On Sales Order From Tagged Transfer Ordercontrol maintenance record is set to Yes, you do not need to update average cost because it is already in balance.

To keep inventory value and G/L in balance set the following:

Dependencies

Used in conjunction with average cost, if the Cost of Goods Sold (COGS) cost basis is set to Average Cost.

Default Value(s)

None.

Action if set to Null

None.

Additional Information

None.

Log The First Non-Zero Cost For Products

New in Release 9.0.3

Indicate if you want the system to keep track of when a cost changes from zero to the first non-zero cost. The default is No.

Note: Enabling this control maintenance record may effect the speed at which your system checks costs.

Notify User When COGS Is Changed During Order Processing

Use this record if you want to notify a specific user when the cost of goods sold (COGS) is changed on an order during order processing. ClosedMore:

Options

For each branch in your company, identify the user you want to notify when the Phantom processes an order and changes the cost of goods sold (COGS). Select one of the following:

  • Writer

  • Inside Salesperson

  • Outside Salesperson

  • Message Group

  • User

Outcome of setting this control record

Corresponds with the Notify on COGS Chgfield in Price Line Maintenance.

Examples

A copper wire salesperson writes up a sales order and sends quotes their customers knowing the GP% at that time. However, when the order gets processed a week later, the price of copper went up. The Phantom changes the COGS and the salesperson loses the GP% without notification or warning. This control maintenance record notifies the writers when phantom COGS changes, so the writers have the ability and time to go to the sales orders and adjust the price to retain their GP% before the orders get invoiced to their customers.

Dependencies

For the system to send the notification, also flag the price line to notify a user when the COGS changes for an order in Price Line Branch Data Maintenance.

Default Value(s)

None

Action if set to Null

No notification sent for that branch, unless the Branch/Territory field is set to ALL.

Additional Information

For more information about the Notify on COGS Chg field, see Entering Price Line Branch Data in Pricing Management.

Recalculate COGS And COMM-COST When Changing Bid To Open Order

Use this record if you want the system to recalculate the cost of goods sold (COGS) and the commissions cost (COMM-COST) that were not manually overridden when a bid is changed to an open order generation. Costs that are manually overridden retain their cost calculation if you set this record to K.. ClosedMore:

Options

  • Yes - Recalculates COGS and COMM-COST. All manual overrides are lost.

  • No - Does not recalculate COGS and COMM-COST. All manual overrides are kept.

  • Keep Manual Overrides - Recalculates COGS and COMM-COST only if there is not a manual override. See example below.

  • Stock Items Only (Including Manual Overrides) - Allows you to have the system recalculate the amounts only on stock items. The recalculation includes those with manual overrides.

  • Stock Items Only (Keep Manual Overrides) - Allows you to have the system recalculate the amounts only on stock items. The recalculation keeps the manual overrides for the items.

Outcome of setting this control record

Determines when the system recalculates costs.

Examples

Keep Manual Overrides example: If there is a manual override on COGS but not on COMM-COST, the system recalculates COMM-COST and retains the COGS override. If there is a manual override on COMM-COST but not on COGS, the system recalculates COGS and retains the COMM-COST override.

Default Value(s)

No

Action if set to Null

The same as if set to No.

Additional Information

None

Recalculate COGS And COMM-COST When Recalculating Price On Invoice

Allows Recalculate COGS And COMM-COST when recalculating price on invoice. Options are Yes, No, or O (Only Stock Items).

The O option allows you to have the system recalculate the amounts only on stock items.

Small Project Job Setup

New in Release 9.0, Updates in Release 9.0.1, 9.0.2, 9.0.3, 9.0.4 and 9.1.0.

Use this record to apply or change options for Small Project Jobs (SPJs) transactions. ClosedMore:

Update COMM-COST for SPJ COGS

Use this option to update the cost of goods sold (COGS) on a Small Project Job (SPJ) order for both COGS and COMM-COST on the order.

When special contract costs are applied to an SPJ order through the Small Project Jobs window, the cost updates on the COST column of the order. This record applies that COGS to the COMM-COST as well. This ensures the rebates connected with the order are generated correctly.

Note: Using this option, a red J displays on the COGS and COST column to indicate the COGS from the Small Project Job has been applied. The default is No.

Rebate Inventory Offset Account

New in Release 9.0.1

Select the account from which you want to deduct, or offset, the rebate amount expense for Small Project Job rebates, if any.

Rebate G/L Inventory Account

New in Release 9.0.1

Select the G/L account to which you want to apply the rebate amount for standard Small Project Job rebates.

Default G/L Direct Inventory Account

New in Release 9.0.1

Select the G/L account to which you want to apply the rebate amount for direct Small Project Job rebates.

Default Vendor

New in Release 9.0.2

Select the vendor you want to use by default when creating small project jobs quotes

Default Cost Code

New in Release 9.0.2

Select the cost code you want to use by default when creating small project jobs quotes.

Default Rebate Product

New in Release 9.0.3

Select the product to use when the purchase order is created when processing the contract from the sales order.

Allow SPJ Editing When P/O is Paid or in a Closed Period

New in Release 9.0.3

Indicate if you want users to be able to edit SPJ orders if the purchase order is already paid or if the purchase order is in a closed period.

Print Item Price Default

New in Release 9.0.4

Indicate if you want to print the item price on SPJs.

Note: Any contract created before Release 9.0.4 respects the value set in this option. However, new contracts store the values and are saved as part of the sales order.

The default is Yes.

Display Decimals at GP%

New in Release 9.0.4

Indicate if you want to display the decimal places in the left side panel  GP% field the Contract Totals area.

The default is No.

Update Prices Immediately After Changing Total Cost

New in Release 9.0.4

Indicate if you want prices to automatically update when the Total Contract Cost changes.

The default is No for backward compatibility.

Allow SPJ create new contract if generation is already Invoice

New in Release 9.1.0

Use this option to allow editing the Small Project Job screen from Sales Order Entry, when order generation is already invoiced.

The default is Yes.

Additional Information

If you have the Change Both COGS and COMM on Override control maintenance record set to 1, COMM-COST is always updated when COGS has been changed and you do not need to set this Update COMM-COST for SPJ COGS control maintenance record option. If the Change Both COGS and COMM on Override control maintenance record is set to 0, then this option only updates SPJ sales orders.

After enabling the 9.0.1 functionality a journal entry is created when an SPJ sales order processes.

Important: The system also creates a new journal entry after processing a return order, if the original sales order does not have a G/L entry. This could effect the balance in your accounts.

For more information about applying contract costs, see Applying Contract Totals in the Small Project Jobs documentation.

 

To See Standard Global Basis When Costing, User Must Have Level

Use this record if you want the standard global basis to display when costing. Use the levels set up in the COGS.EDIT authorization key in conjunction with this control maintenance record to assign views. ClosedMore:

Options

Enter the COGS.EDIT authorization key level, 1-9, users must have to view Landed Cost, Average Landed Cost, Order COGS, and Order Comm Cost for a product.

Outcome of setting this control record

Determines if the standard global basis to display when costing

Examples

Add levels to the COST.EDIT authorization key so that if you have the highest level then you can edit cost as it currently allows you. If you have any lower level, then it ties into the View Level of Price Line Maintenance. Here, you can only choose a basis field for changing the Cost to, but no net changes are allowed.                                                                              

For example, the Price Line contains:

Basis

View Level

Rep-Cost

7

Std-Cost

6

 Bid-Cost

5

  • If the user has COST.EDIT authorization key level set to 10, the user can change costs in Sales Order Entry.

  • If the user has COST.EDIT authorization key level set to 7, then user cannot make any changes to actual cost $ amount, but can choose from a selection list of Rep-Cost, STD-Cost, or Bid-Cost, which changes the cost to that dollar amount stored in the chosen basis field.  

  • If the user has COST.EDIT authorization key level set to 6, then only Std-Cost or Bid-Cost is available from the select list.

Default Value(s)

None

Action if set to Null

 

Additional Information

For more information about authorization levels, see Cost of Goods Sold Authorization Keys in the Authorization Keys documentation.

Update Cost On Sales Order From Tagged Purchase Order

Use this record to indicate if the system should update costs on a sales order containing items that are tagged to a purchase order for procurement when a price change is made to the tagged purchase order. ClosedMore:

Options

Select one of the following options:

  • 0 (No update) - The system does not update cost on a sales order containing items that are tagged to a purchase order for procurement when a price change is made to the tagged purchase order.

  • 1 (Update open generations only) - The system copies the price change back to all quantities on the open generation of a sales order tagged to a purchase order to make sure that the cost on the order is the same as the tagged purchase order price. This is only effective when you change the cost on the purchase order itself, and only if the entire quantity for the line item on the generation is tagged to the purchase order.

  • 2 (Update open and closed generations) - The system copies the price change back to all quantities on both open and closed generations of a sales order tagged to a purchase order. The closed generation must still be in an open accounting period.

Outcome of setting this control record

See Option descriptions above.

Default Value(s)

No

Update Cost On Sales Order From Tagged Return Purchase Order

For each branch, indicate whether the system updates the cost on a sales order tagged to a purchase order created from the Return Goods Queue with the cost on the purchase order. Set the control maintenance record for each branch. ClosedMore:

Options

  • Yes - The cost on a return purchase order that is tagged to a sales order transfers to both the COMM-COST and COGS-COST on the sales order, even if the cost on the sales order has been changed.  

  • No or blank - The cost on a return purchase order that is tagged to a sales order does not transfer to the sales order.

Outcome of setting this control record

Determines whether the system updates the cost on a sales order tagged to a purchase order created from the Return Goods Queue.

Default Value(s)

No

Action if set to Null

The same as if set to No.

Additional Information

None

Update Cost On Sales Order From Tagged Transfer Order

Use this record to indicate whether the system updates the cost on a sales order containing items that are tagged to a transfer for procurement when a change is made to the Transfer Received Price of the tagged transfer. ClosedMore:

Options

  • 0 (No update) - The cost on a sales order containing items that are tagged to a transfer for procurement are not updated when a change is made to the Transfer Received Price of the tagged transfer.

  • 1 (Update open Gens) - The system copies the price change back to all quantities on the open generation of a sales order tagged to a transfer to make sure that the cost on the order is the same as the tagged transfer price. This is only effective when you change the Transfer Received Price on the transfer itself, and only if the entire quantity for the line item on the generation is tagged to the transfer.

  • 2 (Update open and closed Gens) - The system copies the price change back to all quantities on both open and closed generations of a sales order tagged to a transfer. The closed generation must still be in an open accounting period.

Outcome of setting this control record

Determines if the system updates the cost on a sales order containing items that are tagged to a transfer for procurement

Dependencies

A change on the transfer affects the order COGS, but a change on the order does not affect the transfer COGS. If the Change Both COGS And COMM-COST On Overridecontrol maintenance record is set to a non-zero value, the system updates the COMM-COST as well as the COGS on the order.

Default Value(s)

1

Action if set to Null

Same as if set to 1.

Additional Information

None

Update Generic Cost During Processing

For each branch, indicate whether the system updates the Generic Cost (formerly labeled COMM-COST) that is filed with each transaction whenever the cost of goods sold cost (COGS-COST) of a transaction is updated in processing. ClosedMore:

Options

  • No - Generic Cost is not updated whenever COGS-COST of a transaction is updated in processing. COGS-COST is always updated.

  • Yes - Transaction profit reporting based on the two costs is identical for both stock sales and direct sales.

  • Exclude Directs - Generic Cost is not updated when COGS-COST is processed for direct sales, but it is updated on all other sales.

Outcome of setting this control record

Determines whether the system updates the Generic Cost  that is filed with each transaction whenever the cost of goods sold cost (COGS-COST) of a transaction is updated in processing.

Dependencies

For the R setting in the Direct COGS Always Vendor Pricecontrol maintenance record to work, this control maintenance record must be set to No or Exclude Directs so that costs on a direct are not updated.

Default Value(s)

Blank

Action if set to Null

The same as if set to No.

Additional Information

None

When Costing, Do Not Show Basis With Level Below

Set the lower boundary for viewing costs based on the view level assigned to each basis in Price Line Maintenance for the products in a price line. ClosedMore:

Options

Enter the view level, 1 through 9, which sets the lower boundary for viewing costs based on the view level (View Level) assigned to each basis in Price Line Maintenance for the products in a price line. Any user assigned a view level less than this value is prevented from seeing a cost basis name.

Outcome of setting this control record

Any user assigned a view level less than this value is prevents from seeing a cost basis name.

Dependencies

Set up the View Level field in the Local Basis area of Price Line Maintenance for whichever Local Basis names your company uses.

Additional Information

For more information about setting view levels, see Restricting User Access to Pricing Information in the Pricing Management documentation.