Removed the [Load Zip Table] button. Use program UTCV, Delimited File Manager, to load zip code / customer cross references from a csv file.
Reports can also be sent to a specific email address from the jobstream set in program MUJM, Menu and Job Parameter Maintenance. For more information, see Emailing Reports from the Jobstream.
When reports that are assigned to report class POP are transmitted, a comment is written to the purchase order regarding who, how and when the purchase order was transmitted.
Added the ability to determine the fax number and email address to which sales order forms, such as the sales order acknowledgment and invoice, will be sent from the customer's ship to code. Set up is required for the ship to code in program CMMM, Customer Master Maintenance, and for the drill down record for the report.
Printing by Ship To Code
1. In the fourth key field, enter quote S quote for ship to code, i.e. 'S'.
The fax number and/or email address will be taken from the ship to address information.
2. In the first key field, enter the block and field from which the order number is obtained. You can use the list of values to select the block and field in the program in which this information in contained.
3. In the second key field, enter the block and field from which the suffix number is obtained. You can use the list of values.
4. Press [Commit].
5. Press [Return].
6. On the Drill Down Destinations screen, double-click on the record that you just entered.
7. The report will print. If you had the Show Mail Form flag set to on, the email will pop-up on your screen for review.
The value for the "from" email address is determined as follows:
The From value entered for the report class in program MURC, Report Class Definitions.
If there is no From value for the report class, the employee's email address is used.
If there is no employee email address, the email address in the MAIL_FROM parameter in program MURM, Initialization Parameter Maintenance, will be used.
Modified program to have tabs. General Tab contains general plant code information and Batch Shipping Tab contains batch shipping information. New Batch Shipping Parameters and Background Shipping parameters added. Also added Shipment Statistics for the last batch shipment.
New program type - 60 Xephr Application. The program name string is a URL to the Xephr application, including the two tokens, ^LOGIN^ and ^PASSWORD^. At run time, the ^LOGIN^ token is replaced with the operating system login, and the ^PASSWORD^ token is replaced with the hash of the NDS application log in.
Added the ability to email reports from the jobstream. For more information, see Emailing Reports from the Jobstream.
Removed Third Party Account Restriction for Customers parameter RESTRICT_CMMM_THP_ACCTS. Entry of third party accounts in program CMMM, Customer Master Maintenance, no longer requires a duplicate entry in program VESM, Third Party Vendor Maintenance.
Removed ICRC_SCAVENGE. Replaced with the Scavenge Mode flag on the new Parameters tab in program ICRC, Inventory Replenishment.
Modified program to add tabs and categories for ease of parameter maintenance.
Alternate Material Overhead Calculation
MATL_OVHD_MULTIPLY: This parameter determines how material overhead will be calculated when program PCIC, Incremental Cost Calculation, is run.
* Valid values are Y or N. When set to Y, material overhead calculation will multiply overhead rates together instead of adding them.
For example, rates of 40% and 15% would yield 61% instead of 55%.
If any flat amount is specified rather than a rate, the amount is included as the basis for rate calculation for any corresponding fixed or variable rate.
For example, if the material cost = 100, the flat fixed overhead is 50 and the flat overhead rate is 30%, the fixed overhead is 50 + (.3*(100+50)) = 95.
Automatic Window Resize
AUTO_RESIZE_MDI_WINDOW: This parameter determines whether when entering a new form, the system will resize the outer window large enough to accommodate the new form if it is not large enough already.
* Valid values are Y or N. When set to Y, when entering a new form, the system will resize the outer window large enough to accommodate the new form if it is not large enough already. When set to N, the window will not be resized automatically.
Automatically Save Credit Card Information on Authorization
AUTOSAVE_CC_INFO: This parameter determines whether the credit card information on sales orders is updated automatically when the authorization is done.
* Valid values are Y or N. When set to Y, the credit card code is set to the pay type and the address is set to the payment values or the order header information. When set to N, the credit card information is saved when the payment is processed with program OESJ, Sales Order End of Day and Journals.
Comment Sort in Customer Programs
CUST_COMMENT_SORT: This parameter determines how the customer comments will be sorted in program CMCM, Customer Credit Maintenance.
* Valid values are: T, S, or D. When set to T, the comments are sorted in comment type and then comment sequence order. When set to S, the comments are sorted by descending comment sequence. When set to D, the comments are sorted by descending date sequence and then descending comment sequence.
Comment Sort in Sales Order Programs
OE_COMMENT_SORT: This parameter determines how the sales order comments will be sorted in program OEXP, Fast Order Entry.
* Valid values are: T, S, or D. When set to T, the comments are sorted in comment type and then comment sequence order. When set to S, the comments are sorted by descending comment sequence. When set to D, the comments are sorted by descending date sequence and then descending comment sequence.
Common Customer for Item Configuration String Cross Reference
ICCR_COMMON_CUST_NO: This parameter specifies the common customer number used when setting up and querying cross references for configuration items in program ICCR, Customer / Item Cross Reference Maintenance. The customer number should not exist in program CMMM, Customer Master Maintenance. If you have items that are now configurable model items, you can set a cross reference in program ICCR, Customer / Item Cross Reference Maintenance, to connect the item number to the new configuration string. When the item is entered in the sales order entries program, the item number will be replaced with the new model item and its new configuration string.
* The valid value for this parameter is a customer number that does NOT exist in program CMMM, Customer Master Maintenance.
Controlling Item Price Group Modifications
ICSM_DISALLOW_IPG_UPDATE: This parameter determines whether the item price group for an item can be updated or maintained in program ICSM, Inventory Sales Data Maintenance and whether the Item Price Groups tab can be maintained. The value set up for this parameter is the default if no plant-specific parameter exists for a plant.
* Valid values are Y or N. When set to Y, the item's default item price group cannot be edited and the item price groups tab cannot be maintained.
ICSM_DISALLOW_IPG_UPDATE_PP: This parameter determines whether the item price group for an item can be updated or maintained in program ICSM, Inventory Sales Data Maintenance and whether the Item Price Groups tab can be maintained in this plant. The PP should be replaced with the plant code.
* Valid values are Y or N. When set to Y, the item's default item price group cannot be edited and the item price groups tab cannot be maintained.
Credit Card Payment Reauthorization for Point of Sale orders
POS_CRDR_CODE: This parameter specifies the default sales reason code for sales orders entered through point of sale.
* Valid values are any sales reason code from program ARRM, Maintain Sales Reason Codes.
OESJ_RECALC_POS_CC: This parameter determines whether those orders will have their credit card payments reauthorized.
* Valid values are Y or N. When set to Y, sales orders with the POS sales reason code will have their credit card payments reauthorized when processed through program OESJ, Sales Order End of Day and Journals. Otherwise, sales orders assigned the POS sales reason code will not have their credit card payments reauthorized when processed through program OESJ, Sales Order End of Day and Journals.
Customer Send To Information Update in program OEDI, Sales Order Detail Inquiry
OEDI_SENDTO_CHECKBOX: This parameter determines whether users can update the send to information for customers from sales orders queried in program OEDI, Sales Order Detail Inquiry. This parameter also determines the default value for the Add to Customer Master flag for new send to records entered in program OEDI, Sales Order Detail Inquiry.
* Valid values are Y or N. When set to Y, the user can set the Add to Customer Master flag to on in program OEDI, Sales Order Detail Inquiry, for a sales order and update the send to information for the customer. In addition, when entering new send to records in program OEDI, the setting of this flag determines the default value for the new send to records.
Customer Statement Batch Transmit Report
ARSS_BATCH_XMIT_RPT: This parameter determines the report that will be run when transmitting customer statements. The default is ARSS.
* The valid value is the report name for the report to run for batch transmitting customer statements from program ARRS, Review Statements or a job stream. Drilldown keys with report parameters must be specified in program UTKM, Maintain Drill Down Keys, for the report entered here.
Default Settings for Item Plant Control
ICEM_SHIPPABLE_DEF: This parameter determines the default value of the Shippable flag in program ICEM, Item Plant Maintenance, for new items when the plant parameter does not exist.
* Valid values are Y or N.
ICEM_SHIPPABLE_DEF_PP: This parameter determines the default value of the Shippable flag in program ICEM, Item Plant Maintenance, for new items in this plant. PP should be replaced by the plant code for which you are defining the default.
* Valid values are Y or N.
ICEM_STOCKED_DEF: This parameter determines the default value of the Stocked flag in program ICEM, Item Plant Maintenance, for new items when the plant parameter does not exist.
* Valid values are Y or N.
ICEM_STOCKED_DEF_PP: Y or N. This parameter determines the default value of the Stocked flag in program ICEM, Item Plant Maintenance, for new items entered in this plant. PP should be replaced by the plant code for which you are defining the default.
* Valid values are Y or N.
Exclude Credit Balances when Selecting Customers in program ARRS, Review Statements
ARRS_EXCLUDE_CREDIT_BAL: This parameter determines the default setting of the Exclude Credit Balances when Selecting All flag in program ARRS, Review Statements.
* Valid values are Y or N. When the parameter is set to Y, the flag will default to on. When the parameter is set to N, the flag will default to off.
Hold Codes Unreleasable in program OEHR, Credit Hold Release
OEHR_EXCLUDE_HOLD: This parameter determines the list of hold codes that will not be displayed for release in program OEHR, Credit Hold Release, and corresponds with the Exclude Hold Codes field in program OEHR, Credit Hold Release. If an entry is made for this parameter, those entries will be displayed in the Exclude Hold Codes field in program OEHR, Credit Hold Release, and that field will not allow updates. If this parameter's value is left blank, then entries can be made in program OEHR, Credit Hold Release, in the Exclude Hold Codes field.
* Valid values are any of the valid hold codes entered in program CMHM, Hold Code Maintenance, separated by commas.
OEHR_INCLUDE_HOLD: This parameter determines the list of hold codes that will be displayed for release in program OEHR Credit Hold Release, and corresponds with the Query List of Hold Codes field in program OEHR, Credit Hold Release. If an entry is made for this parameter, those entries will be displayed in the Query List of Hold Codes field in program OEHR, Credit Hold release, and that field will not allow updates. If this parameter's value is left blank, then entries can be made in program OEHR, Credit Hold Release, in the Query List of Hold Codes field.
* Valid values are any of the valid hold codes entered in program CMHM, Hold Code Maintenance, separated by commas.
ICMI - Inventory Item Inquiry Mode Setting
ICMI_MODE: This parameter determines whether maintenance screens accessed through the buttons program ICMI, Inventory Master Inquiry, will be in query-only or maintenance mode.
* Valid values are Q or M. When set to Q, the maintenance screens will be in query-only mode. When set to M, the maintenance screens will be in maintenance mode. Inquiry screens will always be in query only mode.
Internal Supplier Settings
These parameters determine the functionality of the Internal Suppliers features.
INT_SUPPLY_PRICE_OVRD: This parameter determines the pricing on the sales order line for internally supply purchase orders.
* Valid values include: N, C, or anything else.
N - the unit price on the sales order will be 0.
C - the unit price on the sales order will match the unit price on the purchase orders.
Any other setting indicates that standard pricing will be used on the sales order.
INTERNAL_SUPPLY_NOHIST: Sales analysis and item history are recorded for internal supply transactions, but they can be suppressed. This parameter determines whether or not the sales analysis and item history is recorded for the internal supply sales orders and purchase orders. This parameter has the category INVENTORY.
* Valid values are Y or N. When set to Y, the information is recorded. When set to N, the information is not recorded.
POEM_INTERCO_WARN: This parameter determines whether a warning will be displayed in program POEM, PO Entry/Maintenance, when a user queries an internal purchase order, only one sales order is associated with the purchase order, the sales order is not open, and there are no open back orders for the sales order.
* Valid values are Y or N. When set to Y, the warning will be displayed.
REOM_INT_SO_REQD: This parameter determines whether receipt of internal supply purchase orders requires receipt of entire sales order shipment. This parameter has the category RECEIVING.
* Valid values are Y or N. When set to Y, receipt of internal supply purchase orders requires receipt of entire sales order shipment.
Invoice Batch Transmit Report
ARPF_BATCH_XMIT_RPT: This parameter determines the report that will be run when transmitting invoices for sales orders. The default is ARIPX.
* The valid value is the report name for the report to run for batch transmitting sales order invoices from program ARPX, Cash Receipts Entry Reversal, or a job stream. Drilldown keys with report parameters must be specified in program UTKM, Maintain Drill Down Keys, for the report entered here.
Limiting Query Results
LIMIT_QUERY_ROWS: When you are executing a query in some programs in NDS Applications, the program will warn you if the query results will exceed a specific number and allow you to select whether or not to continue with the query. This parameter determines whether that warning will be displayed and sets the number of rows that the query must reach or exceed before displaying the warning.
* Valid value is the number of rows that the query must reach or exceed before displaying the warning. You can enter 0 or leave the value blank to skip the query count altogether.
Locking the NDS Log In Locations for Users
NDS_LOCK_LOGIN: This parameter determines whether or not the financial enterprise, manufacturing enterprise, and plant code can be changed on the menu for a specific Oracle User ID or Application ID. This is useful for users for batch jobs or other processes that require the location to remain static.
* Valid values are Y or N. When set to Y, the user can change the logged in location on the menu, provided the [Lock] 
button is green. When set to N, the user can never change the logged in location on the menu, regardless of the color of the button.
Master Production Scheduling (MPS) Forecast Calculation Record Suppression
MPS_SUPPRESS_FD: This parameter determines whether the creation of type FD forecast calculation records will be suppressed during master production schedule (MPS) runs. This parameter is provided mainly for situations where large numbers of FD records slow the performance of MPS run and forecast calculations are not being used.
* Valid values are Y or N. When set to Y, the creation of type FD forecast calculation records will be suppressed. This parameter is provided mainly for situations where large numbers of FD records slow the performance of MPS run and forecast calculations are not being used. When this parameter is set to Y, the projected on hand calculation will not be accurate, and users will need to interpret projected on hand values as projected available to promise values instead.
Master Schedule Authorization Settings
MSSX_SR_NO_UPDATE: This parameter determines whether existing authorized schedules will be added to or if new schedules will be planned when transferring Master Schedules to the live system with program MSSX, Master Schedule Authorization.
* Valid values are Y or N. When set to Y, instead of adding to existing authorized schedules, a new schedule will be planned on the next available date that has no schedule for the item. When set to N or if no value is assigned, quantities will be added to existing authorized schedules for the item.
* Note: Resulting schedules may not match Master Scheduling plan displays. This option is NOT compatible with lot or serial control.
Material Requirements Planning (MRP) Authorization Settings
MPPX_SR_NO_UPDATE: This parameter determines whether existing authorized schedules will be added to or if new schedules will be planned when transferring MRP Planned Orders to the live system with program MPPX, MRP Planned Order Transfer.
* Valid values are Y or N. When set to Y, instead of adding to existing authorized schedules, a new schedule will be planned on the next available date that has no schedule for the item. When set to N or if no value is assigned, quantities will be added to existing authorized schedules for the item.
* Note: Resulting schedules may not match MRP plan displays. This option is NOT compatible with lot or serial control.
Model Item Creation Defaults
The MOTM_KIT_PRICING_DEFAULT and MOTM_MODEL_PRICING_DEFAULT parameters have been replaced by fields in program MOPM, Modular Parameter Maintenance.
Order Level Discount Parameters
New parameter added.
CMDM_CONTRACTS_GET_DISCOUNT: This parameter determines whether order level discounts are used on sales contracts.
* Valid values are Y or N. When set to Y, order level discounts are applied to sales contracts. When set to N, order level discounts are not applied to sales contracts.
Physical Inventory/General Ledger Post Date
PIUP_POSTING_DATE: This parameter determines whether the physical inventory transactions will be posted to the general ledger using the snapshot date from program PIWW, Physical Inventory Control, or the transaction date.
* Valid values are S or blank. When set to S, the snapshot date from program PIWW, Physical Inventory Control, is used for the physical inventory general ledger postings. When set to blank or anything besides S, the transaction date is used.
Pricing Changes in program OESC, Shipping Confirmation
OESC_ALLOW_PRICE_CHANGES: This parameter determines whether or not unit prices can be modified for sales order line items during shipping with program OESC, Shipping Confirmation.
* Valid values are Y or N. When set to Y, the user can set to Override flag to the desired setting and change the unit price, or modify the extended price to force a flat discount. When set to N, no price changes are allowed.
Protected Sales Order Line Allocations in Background Batch Shipping
PROTECTED_ALLOC_WARN_DAYS: This parameter determines how many days before the protected allocation expiration date the expiration workflow will be sent. The expiration date is based off of the estimated ship date for the sales order. The parameter is only valid for background batch shipping.
* Valid value is the number of days before the estimated ship date of the sales order that the expiration workflow will be sent for the protected allocations.
Purchase Order Cost Variance Options
PO_COST_VARIANCE_ALLOWED: This parameter determines whether the price on the purchase order will be compared against the purchase order unit cost for maintain on hand items to see if it is within tolerance levels. This parameter is used as the default for new plants or if the parameter doesn't exist for a specific plant.
* Valid value is the variance by which the price can differ from the cost on the purchase order for maintain on hand items for the plant. If no value is entered, the purchase price and cost will not be compared.
PO_COST_VARIANCE_ALLOWED_PP: This parameter determines whether the price on the purchase order will be compared against the purchase order unit cost for maintain on hand items to see if it is within tolerance levels for this plant.
* Valid value is the variance by which the price can differ from the cost on the purchase order for maintain on hand items for the plant. If no value is entered, the purchase price and cost will not be compared. The PP should be replaced with the plant code for which the variance applies.
Quick Labor Entry Settings
New parameter added.
RTG_AUTO_BEHAVIOR: This parameter determines whether only one labor entry will be allowed in program LRQE, Quick Labor Entry, for automatic routing operations or whether multiple entries can be made updating the automatic operations with each transaction.
* Valid values are F or A. When set to F, only one labor reporting transaction is allowed for automatic routing operations on work orders. When set to A, automatic operations will be updated with each labor reporting transaction, provided that no later pay point or finished goods receipt transaction (with program MRFE, Finished Goods Receipts Entry) reports a greater good + scrap quantity for the work order.
Reorder Point Parameters
Modified program documentation to include all reorder point parameters in the same section.
IMRC_INCL_CONSIGNED_LOC: This parameter determines whether quantities in consigned locations will be considered when calculating reorder point.
* Valid values are Y or N. When set to Y, quantities in consigned locations will be considered when calculating reorder point. When set to N, quantities in consigned locations will be excluded when calculating reorder point. Consigned locations have the Consigned flag set to on in program ILMM, Location Master Maintenance.
IMRC_INCL_NON_NET: This parameter determines whether quantities in non-nettable locations will be considered when calculating reorder point.
* Valid values are Y or N. When set to Y, quantities in non-nettable locations will be considered when calculating reorder point. When set to N, quantities in non-nettable locations will be excluded when calculating reorder point. Non-nettable locations have the Nettable flag set to off in program ILMM, Location Master Maintenance.
IMRC_INCL_QUARANTINE: This parameter determines whether quantities in quarantine locations will be considered when calculating reorder point.
* Valid values are Y or N. When set to Y, quantities in quarantine locations will be considered when calculating reorder point. When set to N, quantities in quarantine locations will be excluded when calculating reorder point. Quarantine locations have the Quarantine flag set to on in program ILMM, Location Master Maintenance.
IMRC_LOG_RETAIN_DAYS: This parameter determines the number of work days of past reorder point records that should be retained when program IMRC, Re-Order Point Calculation Management, is run.
* Valid value is the number of work days.
IMRC_PLANNER_BUYER: This parameter determines whether the reorder point calculation in program IMRC, Re-Order Point Calculation Management, is calculated by buyer code or planner code.
* Valid values are BUYER or PLANNER. When set to BUYER, a Buyer Code field is displayed in program IMRC, Re-Order Point Calculation Management, and the calculation is made by buyer code. When set to PLANNER, a Planner Code field is displayed in program IMRC, Re-Order Point Calculation Management, and the calculation is made be planner code.
IMRC_SIMPLE_ALLOC: This parameter determines whether allocations for reorder point will be calculated from the detail records or will be taken from the item plant quantity record.
* Valid values are Y or N. When set to N, the allocations are calculated from the order detail records during reorder point calculation. When set to Y, the quantity available from the item plant quantity record is used.
Note: when set to Y, the demand horizon feature cannot be used because all allocations are considered. Use of this feature reduced reorder point runtime dramatically for larger databases.
IMRC_TRUSTS_POSE: This parameter determines whether the reorder point calculation will look for and plan items that are excluded from program POSE, Create Purchase Orders from Sales, according to the settings for program POSE, Create Purchase Orders from Sales.
* Valid values are Y or N. When set to Y, program IMRC, Re-Order Point Calculation Management, will look for and plan items that are excluded from program POSE, Create Purchase Orders from Sales, according to the settings for program POSE, Create Purchase Orders from Sales.
Sales Commission Settings
OE_EXCLUDE_ZERO_COMM: This parameter determines whether sales representatives with a zero percent commission will be included in the sales order header.
* Valid values are Y or N. When set to Y, then sales representatives will not be included in the sales order header if the sales commission percentage is zero. When set to N, they will be included in the sales order header.
Sales Order Batch Invoicing Parameters
OESJ_BATCH_DATE_OFFSET: This parameter determines the default settings for batch invoicing that can be set up using a batch file in your scheduled tasks on your operating system. For more information, see the Batch Invoicing documentation. If no plant parameter is found, this parameter is used as the default value.
* Valid value is the number of days to subtract from the system date to get the cutoff ship date for the batch run. Default is 1 if no value is entered or the parameter does not exist.
OESJ_BATCH_DATE_OFFSET_PP: This parameter determines the default settings for this plant for batch invoicing that can be set up using a batch file in your scheduled tasks on your operating system. For more information, see the Batch Invoicing documentation. The PP should be replaced with the plant code as these parameters are defined by plant. If no parameter exists for the plant, the OESJ_BATCH_DATE_OFFSET parameter value is used.
* Valid value is the number of days to subtract from the system date to get the cutoff ship date for the batch run for this plant.
Sales Order Batch Shipping Parameters
Added two new parameters that will limit the background process either by time limit or number of orders limit.
OESB_BG_ORDER_LIMIT: This parameter determines the number of orders to process before exiting. Once this number of orders has been processed, the background cycle will exist regardless of the amount of time that has passed. This parameter can be used in conjunction with the OESB_BG_TIME_LIMIT parameter. If left blank, then the limit will not be tested. This parameter is used as the default for new plants or if the parameter doesn't exist for a specific plant.
* Valid value is numeric.
OESB_BG_ORDER_LIMIT_PP: This parameter determines the number of orders to process before exiting when running background batch shipping for this plant. Once this number of orders has been processed, the background cycle will exist regardless of the amount of time that has passed. This parameter can be used in conjunction with the OESB_BG_TIME_LIMIT parameter. If left blank, then the limit will not be tested. This parameter is used as the default for new plants or if the parameter doesn't exist for a specific plant.
* Valid value is numeric. The PP in the parameter above should be replaced with the plant code when setting up this variable.
OESB_BG_TIME_LIMIT: This parameter determines the maximum time to spend in a cycle. Once this amount of time has passed, the background cycle will exit regardless of number of orders processed. This parameter can be used in conjunction with the OESB_BG_ORDER_LIMIT parameter. If left blank, then the limit will not be tested. This parameter is used as the default for new plants or if the parameter doesn't exist for a specific plant.
* Valid value is numeric.
OESB_BG_TIME_LIMIT_PP: This parameter determines the maximum time to spend in a cycle when running background batch shipping in this plant. Once this amount of time has passed, the background cycle will exit regardless of number of orders processed. This parameter can be used in conjunction with the OESB_BG_ORDER_LIMIT parameter. If left blank, then the limit will not be tested. This parameter is used as the default for new plants or if the parameter doesn't exist for a specific plant.
* Valid value is numeric. The PP in the parameter above should be replaced with the plant code when setting up this variable.
Sales Order Cost Change
OE_ANY_COST_CHANGE: This parameter determines whether unit cost change is allowed on sales orders entered in program OEOE, Sales Order Entry/Maintenance, regardless of the standard rules.
* Valid values are Y or N. When this parameter is set to Y, unit cost change is allowed on sales orders entered in program OEOE, Sales Order Entry/Maintenance, regardless of the standard cost rules. When this parameter is set to N, standard cost rules are followed.
Sales Order Default Sort
OE_DEFAULT_SORT: This parameter determines the default order in which sales orders will be listed when queried in sales order entry programs.
* Valid values are O, L, or D.
O - Sales orders will be listed in order by descending order number when queried in the sales order entry programs.
L - Sales orders will be listed in order by ascending sales location code, and then by descending order number when queried in the sales order entry programs.
D - Sales orders will be listed in order by order date and then by descending order number when queried in the sales order entry programs.
Sales Order Merge Settings
OECH_CUST_PO_TEXT: This parameter determines whether the customer purchase order and purchase order line on the primary sales order will be copied to the primary sales order lines, replaced by the text entered for this parameter. When a value is entered for this parameter and a primary sales order with values in the Cust PO and Cust PO Line fields is merged, the values will be transferred to the line items for the primary sales order, and the value for the parameter will be entered in the Cust PO field for the primary sales order.
* Valid value is up to 30 characters of text.
Sales Order Price Group Display
OEOE_SHOW_PRICE_GROUP: This parameter determines whether the customer price group and description are displayed in program OEOE, Sales Order Entry/Maintenance, to the right of the sales location.
* Valid values are Y or N. When set to Y, then the customer price group and price group description are to the right of the Loc field during sales order entry in program OEOE, Sales Order Entry/Maintenance. When set to N, the price group information is not displayed.
Sales Order Revenue Pricing Options
OE_QUICK_PRICE: This parameter determines whether pricing will be delayed for sales orders for customers with the Revenue Pricing Method until the status of the sales order or quotation changes or until the summary screen is opened during sales order with program OQEM, Sales Order Quotation Entry/Maintenance, and program OEOE, Sales Order Entry/Maintenance.
* Valid values are Y or N. When set to N, the pricing will occur as the sales order lines are entered for customers with Revenue Pricing. When set to Y, sales order lines for customers with Revenue Pricing will not be priced until the following parameters are met:
In program OQEM, Sales Order Quotation Entry/Maintenance, the sales order status changes from Q - Quotation to O - Open Order.
In program OEOE, Sales Order Entry/Maintenance, the sales order status changes from I - Incomplete to O - Open Order.
In both programs, the summary screen is opened.
In addition, this parameter determines when order level discounts are calculated when entering sales orders in program OEXP, Fast Order Entry
* When set to N, the order level discounts are calculated when you navigate between tabs in program OEXP, Fast Order Entry. When set to Y, the order level discounts are calculated when the order is generated or when the commit is forced with the [Commit] 
button on the item tab.
Sales Quotation Drop Ship Purchase Orders
OQEM_DROP_SHIP_PO: This parameter determines whether the Create PO flag will be set to on automatically for drop ship items.
* Valid values are Y or N. When set to Y, the Create PO flag will be set to on for drop ship items entered on sales order quotations. When set to N, the Create PO flag will be set to off for drop ship items entered on sales order quotations.
Settings for program ICSS, Stock Status Inquiry
ICSS_MODE: This parameter determines the setting for program ICSS, Stock Status Inquiry, to limit the information available for a user.
* Valid values are P, O, or A.
P - Plant: the user can only see default plant quantities, no costs, no values, and no drill down to program ICPI, Perpetual Inventory Inquiry.
O - Operator: the user can see all plant quantities, but no costs, no values, and no drill down to program ICPI, Perpetual Inventory Inquiry.
A - Administrator: Can view all information.
Settings for program OEXP, Fast Order Entry
Combined all settings for program OEXP, Fast Order Entry, under this section in the help for program MURM, Initialization Parameter Maintenance.
New parameters include:
OEXP_AUTOSAVE_LOST_QUOTES: This parameter determines whether sales orders cancelled in program OEXP, Fast Order Entry, will be saved as lost quotes. This parameter is used as the default for new sales locations or if the parameter doesn't exist for a specific sales location.
* Valid values are Y or N. When set to Y, all cancelled sales orders will be saved as lost quotes. When canceling the sales order in program OEXP, Fast Order Entry, there are only two buttons - [Return] and [Clear and Save as Lost Quote]. When set to N, users can elect to save the cancelled orders as a lost quote or simply clear the order. When canceling the sales order in program OEXP, Fast Order Entry, there are three buttons - [Return], [Clear], and [Save as Lost Quote].
OEXP_AUTOSAVE_LOST_QUOTES _LLL: This parameter determines whether sales orders cancelled in program OEXP, Fast Order Entry, will be saved as lost quotes for this sales location. Replace the LLL with the desired sales location code.
* Valid values are Y or N. When set to Y, all cancelled sales orders will be saved as lost quotes. When canceling the sales order in program OEXP, Fast Order Entry, there are only two buttons - [Return] and [Clear and Save as Lost Quote]. When set to N, users can elect to save the cancelled orders as a lost quote or simply clear the order. When canceling the sales order in program OEXP, Fast Order Entry, there are three buttons - [Return], [Clear], and [Save as Lost Quote].
OEXP_LOST_QUOTE_REASON: This parameter determines whether a reason code must be entered when a quote is saved as a lost quote from program OEXP, Fast Order Entry. Reason codes for lost quotes are set up in program CMRC, Complaint Reason Codes Maintenance and are stored in the quote header.
* Valid values are Y or N. When set to Y and a quote is saved as a lost quote from program OEXP, Fast Order Entry, the user is alerted to enter a reason.
OEXP_VALIDATE_CONTACT: This parameter determines whether contacts are validated against a list of contacts for the customer when sales orders are entered in program OEXP, Fast Order Entry.
* Valid values are Y or N. When set to Y, the user is forced to choose from the list of values when entering a contact. If the contact does not exist, the user must create one through a drill down to program SPWM, System Contacts Maintenance, before entering the sales order. When set to N, the contact is not validated when the order is entered.
Service Warranty Parameters
SVMM_RTV: This parameter determines whether program SVMM, Service Master Maintenance, will create return to vendor transactions when items are returned to a quarantine location from program SVMM, Service Master Maintenance.
* Valid values are Y or N. When set to Y, program SVMM, Service Master Maintenance, will create return to vendor transactions when items are returned to a quarantine location from program SVMM, Service Master Maintenance. When set to N, the items returned to the quarantine location will be added to the appropriate tab in program RTVM, Return to Vendor Maintenance, but a return to vendor transaction will not be automatically created.
Ship To Address Creation for Sales Orders
OE_ALLOW_SHIPTO_CREATE: This parameter determines whether users can create new ship to addresses or update existing addresses for customers in program ARIE, One-Step Invoice Entry, program OQEM, Sales Order Quotation Entry/Maintenance, and program OEOE, Sales Order Entry/Maintenance.
* Valid values are Y or N. When set to Y, users can create new ship to addresses and update existing ship to addresses when entering sales orders for existing customers. When set to N, users cannot create new ship to addresses or update existing ship to addresses when entering sales orders for existing customers.
Supersede Item Comments
OE_ADD_SUPERSEDE_COMMENTS: This parameter determines whether a comment will be written to the line item comments when an item is superseded on a sales order line.
* Valid values are Y or N. When this parameter is set to N, supersede comments will not be entered on the sales order line when the item is superseded.
Utl File Directory
UTL_FILE_DIR: This is the Oracle named directory that the Oracle utl file calls can read and write to for the system. It is used by applications reading and writing files using procedure calls as opposed to reading and writing from within a form.
Oracle named directories provide an alias for the path on the server to the directory so that users don't have to know the actual path to the files. You can have as many Oracle directories as you need. They simply need to be created by the database administrator and have access granted to the users.
Oracle named directories replace the use of the utl_file_dir parameter in the init.ora file.
At minimum, installations should have an Oracle directory named UTL_FILE_DIR as some applications expect to find this. The load_utl_file_dir.sql script sets the directory name to 'UTL_FILE_DIR' for any mappings in this program that have the File Located On pop-list set to Database Server. This script must be run by the database administrator as SYSTEM to create the 'UTL_FILE_DIR' directory. If any additional directories are required, the database administrator can create them using the create_oracle_dir.sql script.
* Valid value is the network path to the directory that the oracle utl file calls can read and write to for the system.
VeriSign™ Variable Setup
You can set up VeriSignTM variables for each plant code or sales location in which sales orders are entered. In the example below, the PP should be replaced with the plant code or sales location. VeriSignTM will look for a parameter with the plant code or sales location first, and if one does not exist, it will use the parameter without one. The CC_BY_SALES_LOCATION parameter indicates whether the PP indicates plant code or sales location.
All steps in the Setting up the Servlets on an Oracle Web Server section should have been completed before you complete these steps.
These parameters should be set up for the COMMON user.
* CC_BY_SALES_LOCATION: This parameter determines whether or not the parameters in program MURM, Initialization Parameter Maintenance, are organized by plant code or sales location.
Valid values are Y or N. When set to Y, the PP in the below parameters indicates sales location. When set to N, the PP in the below parameters indicates plant code.
New parameters added:
VERISIGN_AVS_CVV_HOLD: This parameter determines what hold code the sales order will be placed on if when you are using VeriSignTM address verification or CVV code process, the verification fails for the CVV code or address check. The value set up for this parameter is the default for new plants or sales locations or if no parameter exists for a specific plant or sales location.
Valid values are any hold code from program CMHM, Hold Code Maintenance.
VERISIGN_AVS_CVV_HOLD_PP: This parameter determines what hold code the sales order will be placed on in this sales location or plant if when you are using VeriSignTM address verification or CVV code process, the verification fails for the CVV code or address check. The PP should be replaced with the desired plant code or sales location code.
Valid values are any hold code from program CMHM, Hold Code Maintenance.
VERISIGN_CVV_RESPONSE_TYPE: This parameter determines whether VeriSignTM will return only the normal response code or the normal response code and a CVV Result code. The value set up for this parameter is the default for new plants or sales locations or if no parameter exists for a specific plant or sales location.
Valid values are 0 or 1. When set to 0, VeriSignTM should return only the normal response code. When set to 1VeriSignTM will return both the normal response code and a CVV Result Code.
VeriSignTM CVV Result Codes
M: Match
N: No Match
P: Not Processed
S: Merchant indicated CVV code not present on card
U: Issuer is not certified and/or has not provided encryption keys
VERISIGN_CVV_RESPONSE_TYPE_PP: This parameter determines whether VeriSignTM will return only the normal response code or the normal response code and a CVV Result code for this plant or sales location. The PP should be replaced with the desired plant code or sales location code.
Valid values are 0 or 1. When set to 0, VeriSignTM should return only the normal response code. When set to 1VeriSignTM will return both the normal response code and a CVV Result Code.
VeriSignTM CVV Result Codes
M: Match
N: No Match
P: Not Processed
S: Merchant indicated CVV code not present on card
U: Issuer is not certified and/or has not provided encryption keys
VERISIGN_CVV_WARNING: This parameter determines whether the warning message from the credit card processor will be displayed if the VERISIGN_CVV_RESPONSE_TYPE is set to 1. The value set up for this parameter is the default for new plants or sales locations or if no parameter exists for a specific plant or sales location.
Valid values are Y or N. When set to Y, the warning message from the credit card processor will be displayed. When set to N, the warning message will not be displayed.
VERISIGN_CVV_WARNING_PP: This parameter determines whether the warning message from the credit card processor will be displayed for this plant or sales location if the VERISIGN_CVV_RESPONSE_TYPE is set to 1 The PP should be replaced with the desired plant code or sales location code.
Valid values are Y or N. When set to Y, the warning message from the credit card processor will be displayed. When set to N, the warning message will not be displayed.
VERISIGN_OESJ_HOLD: This parameter determines the hold code that is used when sales orders are put on credit hold during processing with program OESJ, Sales Order End of Day and Journals, because they potentially need authorizing or reauthorizing. If program ARLM, Location Maintenance, has an entry in the Hold Code for Backorders field, that value will override the value here. The value set up for this parameter is the default for new plants or sales locations or if no parameter exists for a specific plant or sales location.
Valid values are any hold code from program CMHM, Hold Code Maintenance.
VERISIGN_OESJ_HOLD_PP: This parameter determines the hold code that is used when sales orders are put on credit hold for this plant or sales location during processing with program OESJ, Sales Order End of Day and Journals, because they potentially need authorizing or reauthorizing. If program ARLM, Location Maintenance, has an entry in the Hold Code for Backorders field, that value will override the value here. The PP should be replaced with the desired plant code or sales location code.
Valid values are any hold code from program CMHM, Hold Code Maintenance.
VERISIGN_AVS_WARNING: This parameter determines whether when you are using VeriSignTM address verification, the order should be put on hold when the verification fails. The value set up for this parameter is the default for new plants or sales locations or if no parameter exists for a specific plant or sales location.
Valid values are Y or N. When set to Y, the order will be put on hold. When set to N, a warning will be displayed to the user, but the order will not be placed on hold.
VERISIGN_AVS_WARNING_PP: This parameter determines whether when you are using VeriSignTM address verification, the order should be put on hold when the verification fails for this plant or sales location. The PP should be replaced with the desired plant code or sales location code.
Valid values are Y or N. When set to Y, the order will be put on hold. When set to N, a warning will be displayed to the user, but the order will not be placed on hold.
VisaNetTM Variable Setup - OBSOLETE
New parameters added.
As of Version 7.5.3, NDS Applications no longer supports some areas of VisaNetTM Payment Processing. Contact your NDS project manager about current support levels for this feature.
VisaNetTM variables should generally be set up for the COMMON user. If other users have different settings or you are restricting access to certain users, be sure to enter the settings separately for those users.
You can set up VisaNetTM variables for each plant code in which sales orders are entered. In the example below, the PP should be replaced with the plant code. Values for these variables should be provided by your bank. VisaNetTM will look for a parameter with the plant code first, and if one does not exist, it will use the parameter without a plant code.
VISANET_AVS_CVV_HOLD: This parameter determines what hold code the sales order will be placed on if when you are using VisaNetTM address verification or CVV code process, the verification fails for the CVV code or address check. The value set up for this parameter is the default for new plants or if no parameter exists for a specific plant.
Valid values are any hold code from program CMHM, Hold Code Maintenance.
VISANET_AVS_CVV_HOLD_PP: This parameter determines what hold code the sales order will be placed on in this sales location or plant if when you are using VisaNetTM address verification or CVV code process, the verification fails for the CVV code or address check. The PP should be replaced with the desired plant code.
Valid values are any hold code from program CMHM, Hold Code Maintenance.
VISANET_CVV_RESPONSE_TYPE: This parameter determines whether VisaNetTM will return only the normal response code or the normal response code and a CVV Result code. The value set up for this parameter is the default for new plants or if no parameter exists for a specific plant.
Valid values are 0 or 1. When set to 0, VisaNetTM should return only the normal response code. When set to 1VisaNetTM will return both the normal response code and a CVV Result Code.
VisaNetTM CVV Result Codes
M: Match
N: No Match
P: Not Processed
S: Merchant indicated CVV code not present on card
U: Issuer is not certified and/or has not provided encryption keys
VISANET_CVV_RESPONSE_TYPE_PP: This parameter determines whether VisaNetTM will return only the normal response code or the normal response code and a CVV Result code for this plant. The PP should be replaced with the desired plant code.
Valid values are 0 or 1. When set to 0, VisaNetTM should return only the normal response code. When set to 1VisaNetTM will return both the normal response code and a CVV Result Code.
VisaNetTM CVV Result Codes
M: Match
N: No Match
P: Not Processed
S: Merchant indicated CVV code not present on card
U: Issuer is not certified and/or has not provided encryption keys
VISANET_CVV_WARNING: This parameter determines whether the warning message from the credit card processor will be displayed if the VISANET_CVV_RESPONSE_TYPE is set to 1. The value set up for this parameter is the default for new plants or if no parameter exists for a specific plant.
Valid values are Y or N. When set to Y, the warning message from the credit card processor will be displayed. When set to N, the warning message will not be displayed.
VISANET_CVV_WARNING_PP: This parameter determines whether the warning message from the credit card processor will be displayed for this plant if the VISANET_CVV_RESPONSE_TYPE is set to 1 The PP should be replaced with the desired plant code.
Valid values are Y or N. When set to Y, the warning message from the credit card processor will be displayed. When set to N, the warning message will not be displayed.
VISANET_OESJ_HOLD: This parameter determines the hold code that is used when sales orders are put on credit hold during processing with program OESJ, Sales Order End of Day and Journals, because they potentially need authorizing or reauthorizing. If program ARLM, Location Maintenance, has an entry in the Hold Code for Backorders field, that value will override the value here.
Valid values are any hold code from program CMHM, Hold Code Maintenance.
VISANET_AVS_WARNING: This parameter determines whether when you are using VisaNetTM address verification, the order should be put on hold when the verification fails. The value set up for this parameter is the default for new plants or if no parameter exists for a specific plant.
Valid values are Y or N. When set to Y, the order will be put on hold. When set to N, a warning will be displayed to the user, but the order will not be placed on hold.
VISANET_AVS_WARNING_PP: This parameter determines whether when you are using VisaNetTM address verification, the order should be put on hold when the verification fails for this plant. The PP should be replaced with the desired plant code.
Valid values are Y or N. When set to Y, the order will be put on hold. When set to N, a warning will be displayed to the user, but the order will not be placed on hold.
Work Order Optional Control Item Issue or Receipt without Control Numbers
Expanded the meaning of this parameter to include work order component issues with program MRPE, Work Order Pick List Entry. This parameter also determines whether control number entry is required when issuing an optional controlled item from a non-controlled location in program MRPE, Work Order Pick List Entry.
WO_CONTROL_OPTIONAL: Y or N.
When set to N, a control number must be entered for the item when it is received or issued.
When set to Y, you can receive work orders for optionally controlled items without entering a control number when the following conditions are true for the item:
Item is flagged as optional controlled in ICEM.
The receiving location is not controlled.
No control number has been entered into program MRFE, Finished Goods Receipts Entry.
No control numbers have been assigned to the item in program WOAC, Work Order Assign Control Number.
When set to Y, you can issue optionally controlled items without entering a control number in program MRPE, Work Order Pick List Entry, if the item is being picked from a non-controlled location.
Added a Xephr Roles section. If you are using Xephr for some of your database applications, and you are using external authentication, these are the Xephr Roles that this user is assigned for the Xephr applications.
Custom tables, which are tables that do not exist in the nds_tables table, are displayed in blue.
Before running the upgrade script for version 7.5.3, use Oracle Enterprise Manager to add the system privilege Create User to your table owners. If you do not, the upgrade will fail.
Instructions have changed for the installation of:
Emailing and Faxing Reports
VeriSign™ Payment Processing
VisaNet™ Payment Processing
WFLOW_HIST sequence changed to WFLOW_HIST_SEQ.
Added new [Remove Sequence] button. Press this button to remove the sequence from the database.
Added new Used for Pricing flag. If the catalog is used for pricing in program CMPC, Price Matrix Maintenance, and sales order entry, set the Used for Pricing flag to on.
Modified name of Primary Catalog for Location flag to Primary Mailing. If the catalog is the should be displayed when this location is selected in program MTMM, Mail To/Prospect Input for Catalogs, for new mail to records, set the flag to on.
Added Misc Group field. This is a user-defined field used for custom reporting purposes.
New Invoice Ship Via field added. In this field, enter the ship via code that will be used to charge the customer for freight during invoicing. The vendor for the invoice ship via must be the same as the vendor for this ship via code.
For example, if the customer on the sales order will be charged for ground rate, but the sales order is actually being shipped 2nd day air, then the ship via code for the ground rate for this vendor would be entered in this field.
New Preauth Allowance is % of Gross flag. When set to on, the authorization amount is calculated as (payment amount + round(gross order value * preauthorization amount/100)). When set to off, the authorization amount is calculated as (payment amount + preauthorization amount).
Set up for Delimited Files in Web NDS
When using program UTCV, Delimited File Manager, on the web version of NDS Applications, files are imported from and exported to a directory on the web server or client machine.
For files imported from the server, this directory corresponds to the name of an Oracle named directory and is entered in the Directory Name field. A list of values of all Oracle directories is provided. The File Name field in this case should not contain the directory path information, only the file name and extension. Be sure to set the File Located On pop-list to Database Server.
* Oracle named directories provide an alias for the path on the server to the directory so that users don't have to know the actual path to the files. You can have as many Oracle directories as you need. They simply need to be created by the database administrator and have access granted to the users.
* Oracle named directories replace the use of the utl_file_dir parameter in the init.ora file.
* At minimum, installations should have an Oracle directory named UTL_FILE_DIR as some applications expect to find this. The load_utl_file_dir.sql script sets the directory name to 'UTL_FILE_DIR' for any mappings in this program that have the File Located On pop-list set to Database Server. This script must be run by the database administrator as SYSTEM to create the 'UTL_FILE_DIR' directory. If any additional directories are required, the database administrator can create them using the create_oracle_dir.sql script.
For files imported from the client machine, the Directory Name field should remain blank, and the path to the file should be entered in the File Name field, along with the file name and extension. Be sure to set the File Located On pop-list to Client Machine.
New program used to query and refresh materialized views in the system. The program displays the materialized view name, the last refresh date, and the materialized view definition. Before materialized views can be refreshed in this program, they must be created. NDS Standard materialized views are created using the makemvw.sql file in your NDS Applications Home sql directory.
Materialized views physically exist in a database, containing joins and/or aggregates. They are used when there is a large amount of data to process for query results and performance time needs to be improved. Since materialized views are physical views, they need to be refreshed periodically so that the data contained within is up to date and accurate.
New program used to view the Oracle named directories that have been created for use when importing or exporting data from the database. The directories displayed in this program are those that were created by the database administrator using the load_utl_file_dir.sql or the create_oracle_dir.sql script. These are the directories that are displayed in the Directory Name list of values in program UTCV, Delimited File Manager, and program VUTM, Vendor Upload.
* Oracle named directories provide an alias for the path on the server to the directory so that users don't have to know the actual path to the files. You can have as many Oracle directories as you need. They simply need to be created by the database administrator and have access granted to the users.
* Oracle named directories replace the use of the utl_file_dir parameter in the init.ora file.
* At minimum, installations should have an Oracle directory named UTL_FILE_DIR as some applications expect to find this. The load_utl_file_dir.sql script sets the directory name to 'UTL_FILE_DIR' for any mappings in program UTCV, Delimited File Manager, that have the File Located On pop-list set to Database Server. This script must be run by the database administrator as SYSTEM to create the 'UTL_FILE_DIR' directory. If any additional directories are required, the database administrator can create them using the create_oracle_dir.sql script.
New program used to track the changes made each time an upgrade is performed or a patch set is applied. Each time a change is made to a procedure, form, trigger, or updateable view, the build number is updated. This program keeps track of the build numbers for the objects that are loaded, and updates them each time the load is performed. This allows you to tell which programs have been changed after an update.