|
Modified use of the Ship Purchased Non-Maintain on Hand flag. Non-maintain on hand items are shipped according to the order line plant instead of the order header plant. For example, suppose that the sales order plant is plant 10 and the sales order line for the non-maintain on hand item should be shipping from plant 20. Plant 10 is set up with the Ship Purchased Non-Maintain on Hand flag set to off in program ILPM, Plant Code Maintenance, and plant 20 has the flag set to on. Since the sales order line for the non-maintain on hand item is assigned plant 20, the item will be shipped by program OESB, Sales Order Batch Shipping. Added new parameters for UPC/GTIN item code generation: In the UCC Mfg ID field, enter the unique manufacturer ID assigned to plant/enterprise by UCC for use in generating UPC/GTIN numbers for items in program ICMM, Inventory Master Maintenance. Set the GTIN Generation pop-list to the desired setting. The setting of this pop-list determines when GTIN numbers will be assigned to items. Choices are: Automatic: Assign a GTIN number to each item upon new item creation. Manual: GTIN numbers will be assigned manually to items in program ICMM, Inventory Master Maintenance. On Demand: Assign a GTIN number to an item when the [Generate GTIN] button is pressed in program ICMM, Inventory Master Maintenance, for that item. Set the GTIN Format pop-list to the desired setting. The setting of this pop-list determines the length of the standard GTIN code when GTIN numbers are generated for items. UCC-12 - generate the GTIN number as the UCC manufacturing ID followed by a twelve digit code. Set the Synchronize GTIN and Item No where possible flag to the desired setting. When this flag is set to on, when creating items, the item number and GTIN will be the same if the item number is not specified during item creation.
|
|
|
New Repeat Until field on the second page. Enter the date and time on or before which the last running of this job will occur. This field is used in conjunction with the interval. Format is MM-DD-YYY hh24:mm. For example, July 13th 2006 at three pm would be 07-13-2006 15:00. See Also: Background Batch Shipping with program JOBQ, NDS Job Queue Management |
|
|
If the WEB_PRINT_BATCH_SELECTION parameter in program MURM, Initialization Parameter Maintenance, is set to MUJM, the printer entered in the Ovrd Printer field will override the defined web batch printer when running NDS Applications in web mode. If no printer is entered, here, the web batch printer defined in program MURM, Initialization Parameter Maintenance, will be used. |
|
|
Added a new pop-up screen that displays a comment to describe the usage of the parameter. To view/maintain all comments for all COMMON parameters, click on the [Comments] To view/maintain comments for the currently selected parameter, click on the [Zoom] Accounts Payable Payment Selection DefaultsDetermines the default value for the sorting of invoice on the third page of program APPS, Payment Selection of Invoices by Range. If nothing is assigned to this parameter, the default is Vendor ID. APPS_PG3_SORT: Valid values include: DD - Discount Due Date ID - Invoice Due Date IN - Invoice Number PA - Payment Amount VN - Voucher Number N - Vendor Name VI - Vendor ID Accounts Receivable Inter-Company InvoicesDetermines whether invoices from financial enterprises other than the logged in financial enterprise will be displayed for payments and adjustments in program ARPE, Cash Receipts Entry and program ARAD, Accounts Receivable Adjustments Entry. Enter a record for the COMMON user for the following key. SHOW_INTER_COMPANY_INVOICES_AR: Y or N. When set to Y, invoices for all financial enterprises can be displayed in program ARPE, Cash Receipts Entry, and program ARAD, Accounts Receivable Adjustments Entry, for payment and adjustment. When set to N, only invoices for the current logged in enterprise will be displayed in the programs for payment or adjustment. Accounts Receivable Posting Date for Sales Order Processing with program OESJ, Sales Order End of Day and Journals.Determines whether the posting date for the invoices processed through program OESJ, Sales Order End of Day and Journals, will be the invoice date or the date on which program OESJ, Sales Order End of Day and Journals, was run. AR_POSTING_DT_SOURCE: INV or POST. When set to INV, the posting date for the invoices is the invoice date. When set to POST, the posting date for the invoices is the date entered in program OESJ, Sales Order End of Day and Journals. Accounts Receivable Record Archive SetupDetermines whether accounts receivable records will be deleted or archived when program ARPG, AR Posted Journal Purge, is run. ARPG_ARCHIVE_RECORDS: Y or N. When set to Y, the purged accounts receivable records will be moved to the arpost_detail_hist table instead of being deleted. When set to N, or non-existent, the records are deleted when program ARPG, AR Posted Journal Purge, is run. Autocommit Message LevelDetermines the commit level for the nds_autocommit functionality. AUTOCOMMIT_MESSAGE_LEVEL: default 20. This is the commit level for the nds_autocommit functionality. Automatic Backorders for Shipping AllocationsDetermines the default setting of the Auto Backorder flag in the sales order header. When the flag is set to on and shipping is initialized, the ordered amounts will be defaulted into the Backorder field for the sales order line. This retains sales allocations for the sales order line until shipping is completed. If the customer does not allow backorders, the Remove Backorders flag will be set to on automatically as well, so that the backorders are removed automatically when shipping is complete. When the flag is set to off, and shipping is initialized, the ordered quantities will not be defaulted into the backordered field. OESHIP_AUTO_BACKORDER: Y or N. When set to Y, the Auto Backorder flag in the sales order header will be set to on automatically. When set to N, the Auto Backorder flag in the sales order header will be set to off automatically. Automatic Catalog Assignation for Contacts Entered for Mail To AddressesDetermines whether a catalog ID will be assigned to the contact record regardless of the setting of the Catalog Ok flag in program MTMM, Mail To/Prospect Input for Catalogs, for the contact record. This parameter is location specific. AUTO_CREATE_CONTACT_CAT_LLL: Y or N. (LLL = sales location code) When set to Y, the catalog will be assigned to the contact created in program MTMM, Mail To/Prospect Input for Catalogs, regardless of the setting of the Catalog Ok flag for the contact. When set to N, the catalog will be assigned to the contact according to the setting of the Catalog Ok flag for the contact. Automatic Freight Credit Charges DeterminationDetermines whether the automatic freight credit charges for a sales order will be taken from the shipping sales location or the customer sales location when the Price From pop-list for the sales location is set to Price Based on Customer Location. AFC_FROM_PRICING_LOC: Y or N. When set to Y and the Price From pop-list for the sales order sales location is set to Price Based on Customer Location, the automatic freight credit (AFC) charges settings in the customer's sales location will be used to determine the AFC charges for the sales order. Otherwise, the settings from the shipping sales location are used. Automatic Mail To Address Creation for ContactsDetermines whether a mail to address should be created when a new address and contact are entered for a customer during sales order entry. These parameters are set up by sales order location and are used in conjunction with the Auto Contact pop-lists in program ARLM, Location Maintenance, for the location. These parameters are set up for the COMMON user. AUTO_CREATE_SOLD_ADDR_LLL: Y or N. (LLL = sales location code) When set to Y, and the Sold To Auto Contact pop-list is set to Always or Exclude Drop Ships and a new sold to address or contact is entered for a sales order, the contact and mail to address will be created automatically for the sold to address. When set to N, and the pop-list is set to Always or Exclude Drop Ships and a new sold to address is entered, a mail to address will not be created. However, if a new contact is entered, the contact record will still be created for the customer. AUTO_CREATE_SHIP_ADDR_LLL: Y or N. (LLL = sales location code) When set to Y, and the Ship To Auto Contact pop-list is set to Always or Exclude Drop Ships and a new ship to address or contact is entered for a sales order, the contact and mail to address will be created automatically for the ship to address. When set to N, and the pop-list is set to Always or Exclude Drop Ships and a new ship to address is entered, a mail to address will not be created. However, if a new contact is entered, the contact record will still be created for the customer. AUTO_CREATE_INV_ADDR_LLL: Y or N. (LLL = sales location code) When set to Y, and the Invoice To Auto Contact pop-list is set to Always or Exclude Drop Ships and a new invoice to address or contact is entered for a sales order, the contact and mail to address will be created automatically for the invoice to address. When set to N, and the pop-list is set to Always or Exclude Drop Ships and a new invoice to address is entered, a mail to address will not be created. However, if a new contact is entered, the contact record will still be created for the customer. AUTO_CREATE_BILL_ADDR_LLL: Y or N. (LLL = sales location code) When set to Y, and the Bill To Auto Contact pop-list is set to Always or Exclude Drop Ships and a new bill to address or contact is entered for a sales order, the contact and mail to address will be created automatically for the bill to address. When set to N, and the pop-list is set to Always or Exclude Drop Ships and a new bill to address is entered, a mail to address will not be created. However, if a new contact is entered, the contact record will still be created for the customer. AUTO_CONTACT_MAIL_ID: Y or N. When set to N, the mail address pop-up window is displayed in program OEXP, Fast Order Entry, and can be used to override the standard logic and assign new contacts to a different mail to address. The [Mail Addresses] Automatic Mail To Address Creation for CustomersDetermines whether when a customer is created in program CMMM, Customer Master Maintenance, a mail to address will be created automatically. Mail to addresses may still be created when new contacts are created during sales order entry. The Automatic Mail To Address Creation for Contacts section discusses this. AUTO_CREATE_CUST_ADDR: Y or N. Y indicates that when a new customer is created, a mail to address record will be created in program MTMM, Mail To/Prospect Input for Catalogs, for the sold to address. N indicates that when a new customer is created, a mail to address will not be created automatically. Available to Promise Inventory CalculationDetermines number of future days used by the available to promise calculation in program OESP, Soft Pegging, and all sales order entry programs. This parameter is entered by plant code. Replace the PP in the parameter with the desired plant code. ATP_HORIZON_DAYS_PP: the number of future days used by the available to promise calculation for this plant. The default horizon date setting is 42 days (six weeks). If the parameter has not been entered for the plant, or if the parameter value is blank, the system will calculate the available to promise using all types of orders up to 42 days in the future. Backorder Notification MethodNew parameters added: BONO_CRDR_CODE: The reason code used on sales orders when re-ordering items from customer responses to notifications sent out with program BONO, Back Order Notify. BONO_REPRICE_OE: Y or N. When set to Y, when the notification is sent, the item price is recalculated. If the new price is not zero, and is different than the current price for the sales order line, the price is changed and the override flag is set to on for the sales order line. You cannot preserve override pricing on backorders when this feature is active. BONO_NOTIFY_EXPIRE: the number of calendar days in the expiration period. Replies received after the expiration date will not be processed. The expiration date is determined by adding the calendar days entered for this parameter to the notification date. This feature is only valid if you are using the API to accept responses from your customers and generate reorders using the notification ID. BONO_BRAND_NAME: Enter the desired brand name to this parameter. When the notification is sent, the brand name will be included in the notification. BONO_RUN_MODE: B or N. When set to B, the default operation mode for program BONO, Back Order Notify, is Backorders. When set to N, the default operation mode is No Backorders. DEF_BO_NOTIFY_PCT: Default percentage of the item's safety stock for which backorder notifications will be sent. This value is used as the default value in program ICMM, Inventory Master Maintenance, for new items and in program BONO, Back Order Notify, if an item does not have a percentage entered in program ICMM, Inventory Master Maintenance. DEF_BO_NOTIFY_DAYS: Default number of days for which a sales order will be considered for backorder notification if one of the sales order lines is for this item. This value is used as the default value in program ICMM, Inventory Master Maintenance, for new items and in program BONO, Back Order Notify, if an item does not have a value entered in program ICMM, Inventory Master Maintenance. Backorder Reservations RetentionDetermines whether reservations for backordered items will be retained after the original sales order is processed through program OESJ, Sales Order End of Day and Journals. This parameter is set up for the COMMON user only. OE_RESV_NO_BO: YES or NO. When set to YES, the reservations are preserved and attached to the backorder. When set to NO, reservations are cleared. Batch Report PrintingThe jobstream specified printer can override the default printer. WEB_PRINT_BATCH_SELECTION: MURM or MUJM. Capacity Planning SuppressionDetermines whether the WIP data load will be bypassed when calculating capacity planning for work orders and production schedules. SKIP_LOAD_WC: YES or NO. When set to YES, regardless of the capacity settings in program SPMM, System Parameters/Default Maintenance, bypass the WIP data load when calculating capacity planning. When set to NO, the settings in program SPMM, System Parameters/Default Maintenance, will be used. Comment Lists of Values in Sales Order EntryDetermines whether double-clicking in the comment text field opens a list of values or an editor in the following programs: ARIE, One-Step Invoice Entry OEDI, Sales Order Detail Inquiry OEOE, Sales Order Entry/Maintenance OESC, Shipping Confirmation OESX, Shipping Director OEXP, Fast Order Entry OQEM, Sales Order Quotation Entry/Maintenance SVMM, Service Master Maintenance For the desired application ID, Oracle user ID, or the COMMON user, enter a record for the following keys. COMMENT_LOV_ARIE: EDIT or LOV COMMENT_LOV_OEDI: EDIT or LOV COMMENT_LOV_OEOE: EDIT or LOV COMMENT_LOV_OESC: EDIT or LOV COMMENT_LOV_OESX: EDIT or LOV COMMENT_LOV_OEXP: EDIT or LOV COMMENT_LOV_OQEM: EDIT or LOV COMMENT_LOV_SVMM: EDIT or LOV When set to EDIT, an editor will be displayed. When set to LOV, the boilerplate text lists of values will be displayed. Containerizing Staged Sales OrdersThis parameter determines how staged sales order lines will be containerized when the [Containerize] button is pressed in program OSEM, Stage Sales Order for Shipping. AUTO_CONTAINERIZE: O, S, or P When set to 'O', all of the staged lines are put into one container. When set to 'S', one container is created per staging line, regardless of the case quantity or case per pallet quantity in program ICPM, Inventory Planning Data Maintenance, or program ICRM, Item/Plant Planning Maintenance. When set to 'P', when containerizing the order, the program will go through all of the staged lines on the order. For items with a case per pallet value of 0 or 1 in program ICPM, Inventory Planning Data Maintenance, or program ICRM, Item/Plant Planning Maintenance, the program will create one container record for each staging line. If the case per pallet for an item is greater than 1, the program will ask whether you want to create the containers as one per staging line or one per pallet. If one per staging line is chosen, one container per staging line will be created. If one per pallet is chosen, one container per pallet will be created. Cost/Price Update for Shipped Sales Order LinesDetermines whether the sales order cost and prices for margin priced customers are recalculated during shipping. In addition to the setting of this parameter, the following conditions must be met: The S type cost is set up to be Actual or Average cost. Sales order status is S - Confirmed Complete. There is a pullcard assigned to the sales order line in program ICKM, Inventory Pull Card Moves. The actual transfer is done in program ICKM, Inventory Pull Card Moves, after shipping. ICKM_RECOST_ORDER_LINE: Y or N. When set to Y, the pricing and cost will be recalculated when all other conditions are met as well. When set to N, the pricing and cost will not be recalculated. Counter Sales Shipping SetupAdded new parameter for use with new Amount Tendered field in program OEPX, Counter Sales Shipping. OE_DEF_CASH_PAYTYPE: This is the default pay type from program SPPT, Payment Type Maintenance, for payments entered in program OEPX, Counter Sales Shipping. When the process order button is pressed, and amount has been entered in the Amount Tendered field, this is the payment type that will be used for the payment record created. Custom Popup Screen in program OEXP, Fast Order EntryDetermines the title and column headings on the popup screen accessed with the custom popup OEXP_USER_VW_TITLE: Title for the pop-up screen. OEXP_USER_VW_FIELD1: Label for Field 1 on the pop-up screen. OEXP_USER_VW_FIELD2: Label for Field 2 on the pop-up screen. Customer / Item Cross Reference Creation in Sales Order EntryDetermines whether the customer/item cross reference will be created automatically in program ICCR, Customer / Item Cross Reference Maintenance, when a customer item number is entered in the customer item field during sales order entry. CREATE_CUST_ITEMS_ON_FLY: YES or NO. Set to NO to prevent customer / item cross reference records from being created. Set to YES to allow automatic creation of customer/item cross reference records when a customer item number is entered in the customer item field during sales order entry. Customer Parent Removal on DeletionDetermines whether the parent customer will be removed from its child customers if the parent customer is deleted. AUTO_REMOVE_CUST_PARENT_LINK: Y or N. When set to Y, the Parent Cust No field will be set to null if the parent customer number is deleted. If the parameter is set to N, customers that are assigned child customers cannot be deleted Customer Phone Lookup Performance OptionsIn some cases in sales order entry, when the phone number is being used to look up the customer (such as in program OEXP, Fast Order Entry), if there are a large number of contact phone records, the search may be slow. In order to increase the speed of customer lookups, the standard view can be replaced by a materialized view. The following set up must be completed. In SQL*Plus, run the following scripts: As the SYSTEM user, run the nds_mvw_grants script. This script grants the CREATE MATERIALIZED VIEW privilege to the application owner, which is an optional privilege not granted by program MUNU, Maintain Oracle Users. As the table owner, run the makemvw script to create the materialized views. This script is currently setting the refresh option to COMPLETE. To change to a fast refresh, logs would need to be built on the underlying tables. At the moment, the system is using a periodic refresh using the mvw_refresh script. As the table owner, run the make_refresh script to refresh all materialized views owned by the user. This script needs to be run periodically to rebuild the materialized views. In this program, enter the following parameter. PHONE_LOOKUP_MVW_ACTIVE: Y or N. Y: The materialized views will be used for phone lookups. N: Standard views will be used for phone lookups. Customer Quick Search SetupIn the sales order entry programs, an additional quick search button can be included on the customer search screen, if desired. When this button is pressed, the search results will contain only customers that have placed an order in the last three years. This parameter determines whether the button will be displayed or not when performing customer searches. CUST_QUICK_SEARCH_BUTTON: YES or NO. Set to NO to have the button hidden or YES to have it displayed. Customer Sales Order HoldDetermines whether all sales orders will be placed on hold using the R - Management Review hold code for a customer if that customer has a hold order balance in program CMCM, Customer Credit Maintenance. Only sales orders with the Do No Hold Order flag set to on in the sales order header will not be placed on hold. CUST_ORDER_AUTO_HOLD: Y or N. Set to Y to have all sales order placed on hold when a customer has a hold order balance. Customer Search Default Flag SettingsDetermines the default settings of the Bill To, Mail To, Ship To, and All flags for the customer search screen in the sales order entry programs. SEARCH_CB_MAIL_BILL_SHIP_ALL: series of four Y and N characters. The order in which the characters are entered determines the default settings for the flags. The first character is the default for the Mail To flag. The second character is the default for the Bill To flag. The third character is the default for the Ship To flag. The last character is the default for the All flag. So, a setting of NNNY would default the Mail To, Bill To, and Ship To flags to off and the All flag to on. Cycle Count SettingsDetermines whether during cycle counting, if the system inventory and the counted inventory amounts match, an item transaction log entry should be written for the zero quantity to preserve the correct population of counts in the item transaction log for statistical purposes. The parameter is created for the COMMON user only. PH_POST_ALL_COUNTS: Y or N. When set to Y, an item transaction log record will be written for all counted items, including those for which the system quantity and the inventory quantity are equal. When set to N, item transaction log records will only be written for items for which an adjustment is required. Default Item Location Warning through Item Location Bulk MoveDetermines whether a warning will be displayed when the 'from location' is not the item's current default location and the 'to location' is marked as being the item's new default location. This setting affects bulk moves by location with program ICLM, Inventory Bulk Move by Location. ICLM_DEFAULT_WARN: YES or NO. YES indicates that a warning will be displayed. NO indicates that a warning will not be displayed. Default Item Location when Disassembling ItemsDetermines whether the Loc Rule pop-list will be displayed in program ICDM, Inventory Disassembly Management. This pop-list determines whether the item's default location will be used as the default when disassembling items, or if a user-defined set of rules from the user's procuser file will determine the default location. ICDM_CUSTOM_LOC: Y or N. Y indicates that the pop-list will be displayed in program ICDM, Inventory Disassembly Management. Any other entry indicates that the pop-list will not be displayed, and the item's default location from program ICEM, Item Plant Maintenance, will be used as the default. Default Revenue Level for Customer Revenue PricingDetermines the default value for the Revenue Level field in program CMMM, Customer Master Maintenance, when the customer's Price Method is set to Revenue. Revenue priced customers will receive the best price from program CMPC, Price Matrix Maintenance, regardless of quantity for the items on their sales orders when the sales order gross unit price reaches the revenue level set for the customer in program CMMM, Customer Master Maintenance. For more information on Revenue Pricing, see the Pricing section. CMMM_DEF_REVENUE_LEVEL: the default dollar value for customers with the Revenue Price Method in program CMMM, Customer Master Maintenance. The dollar value can be changed for each customer, but this is the initial value assigned. Default Settings and Set Up for program CMSU, Mail Label SelectorDetermines various settings and behaviors in program CMSU, Mail Label Selector. The following programs are included when referring to master programs in this section. CMMM, Customer Master Maintenance MTMM, Mail To/Prospect Input for Catalogs SPWM, System Contacts Maintenance PRMM, Prospect Master Maintenance For the COMMON user, enter records for the following keys. CMSU_AUTO_SYNC_MAIL: YES or NO. When set to YES, the settings for the Mass Mail flag will be updated in the search table when program CMSU, Mail Label Selector, is opened to match the setting of the Send Mass Mail flag in the master programs. Whether or not synchronization is performed is also dependent on the CMSU_DAILY_EXPORT_LL parameter. CMSU_AUTO_SYNC_SEL: YES or NO. When set to YES, the settings for the Selected flag will be updated in the search table when program CMSU, Mail Label Selector, is opened to match the setting of the Selected flag in the master programs. Synchronization of the Selected flag includes pulling in the Catalog ID from the master programs and the mail class from the contact records. Whether or not synchronization is performed is also dependent on the CMSU_DAILY_EXPORT_LL parameter. CMSU_ACTIVE: YES or NO. When set to YES, changes to the Catalog Ok, Selected, and Send Mass Mail flags in the master programs will also update the search table in program CMSU, Mail Label Selector. CMSU_EXPORT_DIR: the path to the default export directory for export files created from program CMSU, Mail Label Selector. For example, c:\temp\ CMMM_CMSU_CASCADE_NY: YES or NO. Catalog Ok flag changed from off to on in program CMMM, Customer Master Maintenance, then set the Catalog Ok flag to on in program MTMM, Mail To/Prospect Input for Catalogs and program SPWM, System Contacts Maintenance, for all mail to addresses and contacts for the customer. CMMM_CMSU_CASCADE_YN: YES or NO. Catalog Ok flag changed from on to off in program CMMM, Customer Master Maintenance, then set the Catalog Ok flag to off in program MTMM, Mail To/Prospect Input for Catalogs and program SPWM, System Contacts Maintenance, for all mail to addresses and contacts for the customer. MTMM_CMSU_CASCADE_NY: YES or NO. Catalog Ok flag changed from off to on in program MTMM, Mail To/Prospect Input for Catalogs, then set the Catalog Ok flag to on in program SPWM, System Contacts Maintenance, for all contacts for the mail to address. MTMM_CMSU_CASCADE_YN: YES or NO. Catalog Ok flag changed from on to off in program MTMM, Mail To/Prospect Input for Catalogs, then set the Catalog Ok flag to off in program SPWM, System Contacts Maintenance, for all contacts for the mail to address PRMM_CMSU_CASCADE_NY: YES or NO. Catalog Ok flag changed from off to on in program PRMM, Prospect Master Maintenance, then set the Catalog Ok flag to on in program MTMM, Mail To/Prospect Input for Catalogs and program SPWM, System Contacts Maintenance, for all mail to addresses and contacts for the prospect. PRMM_CMSU_CASCADE_YN: YES or NO. Catalog Ok flag changed from on to off in program PRMM, Prospect Master Maintenance, then set the Catalog Ok flag to off in program MTMM, Mail To/Prospect Input for Catalogs and program SPWM, System Contacts Maintenance, for all mail to addresses and contacts for the prospect. CMSU_DAILY_EXPORT_LL: YES or NO. LL is the location code. When set to YES, the location is exported daily and the settings for the automatic synchronization of the selected and mass mail flags will be performed. Otherwise, automatic synchronization will not be performed for the location, regardless of the setting of the auto-sync parameters. CMSU_CSV_HEADER: YES or NO. When set to YES, the column headers will be written to the remarks line in the csv file. The column headers will overwrite any remarks entered on the export screen. You cannot have both remarks and column headers in the same csv file. CMSU_USE_STD_CSV_HDR: YES or NO. When set to YES, uses the standard column list for the columns being exported. When set to NO, uses the custom column header list created in the procuser.sql file. Default Settings for program POIK, PO / Item KioskDetermines the default values for the Service Z Factor and Horizon fields in program POIK, PO / Item Kiosk. POIK_SERVICE_Z: the default value for the Service Z factor in program POIK, PO / Item Kiosk. Generally, values between 1 and 3 are used. POIK_STAT_HORIZON: the default number of days before the current system date for which the shipments will be analyzed. Editable Fields in Sales Order Entry HeaderDetermines whether the Src Doc Type and Src Doc ID fields are editable on the Order Codes screen in the sales order entry programs. Enter the following key for the desired application ID, Oracle User ID, or the COMMON user. OE_VAL_SRC_DOC: Y or N. When set to N, the Src Doc Type and Src Doc ID fields are editable. When set to Y, the fields are not editable. Email Determination for Sales Order Acknowledgement Automatic TransmissionDetermines which email address will be used as the From email address when automatically transmitting sales order acknowledgements from sales order entry. BACKGROUND_TRANSMIT: Y or N. This should be set up as an application ID specific setting. When set to Y, the employee number from the sales order entry program is used to determine the From email. When set to anything else or if the parameter does not exist, the logged in employee is used to determine the From email. Forecast Filtering ActivationDetermines whether the Statistical Forecast flag for items will be changed automatically when the sample population of the item exceeds the minimum population for the forecast group. The Statistical Forecast flag must be set to Track, and when the population exceeds the minimum population for the forecast group, the flag setting will be changed to Yes if the Filter Enabled flag is set to on for the item's forecast group. This allows the forecasting for new items to be set to Track initially, and have the forecasting be automatically activated when enough data exists. FCCX_AUTO_FC_ACTIVATE: Y or N. Y indicates that the Statistical Forecast flag should be changed from Track to Yes automatically. General Ledger Account Ranges for ReportsDetermines whether ranges entered in program GLRPT, GL Reports Segment Selector, previously will be retained the next time the program is opened for a general ledger report. KEEP_GLRPT_ACCT_RANGES: Y or N. When set to Y, the ranges entered in this program will be retained for the next time a report with this parameter form is run. When set to N, the ranges entered in this program will not be retained. General Ledger Balance Record CreationDetermines whether general ledger balance records will be created when program GLJP, General Ledger Journal Transaction Posting, is run. If you are using automatic account segments for your general ledger accounts, it is highly recommended that this parameter be set to NO. GLBAL_CREATE_DEFERRED: YES or NO. Inventory Replenishment Moves HandlingDetermines whether all moves are processed in program ICRC, Inventory Replenishment, or if you can select the moves to complete. ICRC_AUTO_SELECT: Y or N. When set to Y, when the [Complete Open Moves] button is pressed, all move tickets are processed. When set to N, when the [Complete Open Moves] button is pressed, a pop-up screen is displayed to allow you to select the moves to be completed. Inventory Replenishment Trigger Quantity on Hand DeterminationDetermines whether the replenishment trigger in program IPSM, Inventory Pull Card Definition, should consider the quantity on hand in the plant or in the item location when creating inventory replenishment move tickets. This parameter is plant-specific. When setting up the parameter, replace the PC with the appropriate plant code. This parameter is set up for the COMMON user... IPSM_QOH_SOURCE_PC: PLANT or LOCATION. When set to PLANT, the quantity on hand at the plant level will be considered when determining whether a move ticket should be created to replenish inventory. The sum of the trigger values in program IPSM, Inventory Pull Card Definition, for the plant will be compared against the quantity on hand. If a move ticket is created, it will be generated based on the first replenishment trigger found for the item in the plant. Using this parameter works best when there is only one trigger per item. When set to LOCATION (or anything besides PLANT), the quantity on hand in the defined item location will be used to determine if a move ticket should be created. Item Description Synchronization for Vendor QuotesDetermines whether the item description will be updated in program VEQM, Vendor Quote Maintenance, when item descriptions are changed in program ICMM, Inventory Master Maintenance. VEQM_ITEM_DESC_SYNC: Y or N. When set to Y, when the item description is changed in program ICMM, Inventory Master Maintenance, any vendor quotes with that item will also be updated with the new description. When set to N, item descriptions in program VEQM, Vendor Quote Maintenance, are not affected by changes in program ICMM, Inventory Master Maintenance. Determines whether a warning will be displayed when an item entered in program OEOE, Sales Order Entry/Maintenance, program OQEM, Sales Order Quotation Entry/Maintenance, or program CMPV, Price Verification, already exists on another quote or order for the same customer. WARN_ITEM_ON_QUOTE: YES or NO. When set to YES, and an item is entered on a sales order line or in program CMPV, Price Verification, that already exists on another open or incomplete sales order or quotation, a warning will be displayed including the quotation or sales order number on which it has been entered. When set to NO, no warning is displayed. List of Values Validation for Src Doc ID field in program OEXP, Fast Order EntryDetermines whether the values entered in the Src Doc ID field on the Customer Tab in program OEXP, Fast Order Entry, will be validated against the user defined list of values for that field. The list of values for the field is defined in program UTLV, LOV Configuration, as the OEXPSRCDOC list of values ID. OEXP_VALIDATE_SRCDOCID: Y or N. When set to Y, the value entered in the Src Doc ID field in program OEXP, Fast Order Entry, will be validated against the list of values. When set to N, the value will not be validated against the list. List Price Warning in Sales Order EntryDetermines whether a warning will be displayed when the list price is lower than the unit price when sales order lines are entered during sales order entry. OE_LIST_PRICE_WARN: Y or N. When set to Y, if a sales order line's list price is lower than the unit price when the sales order line is entered, a warning will be displayed. Otherwise, a warning will not be displayed. Materialized Views in MRP and MPS SettingsIf you have a large number of sales order entry lines records to be considered when MRP or MPS is run, then you have the option of using a materialized view to increase the performance of the MRP or MPS run. MRP_USE_FAST_OE: Y or N. When set to Y, the MRP process and MPS process will use a materialized view for performance reasons. This requires that the materialized view has been refreshed and analyzed immediately prior to running MRP or MPS so the data is fresh. Model Item Work Order Cost DeterminationDetermines how work order cost is calculated for non-maintain on hand model items when the sales order for the model item is processed through program OESJ, Sales Order End of Day and Journals. COGSMODELWOCOST: Y or N. When set to Y, sales orders for model items are updated during program OESJ, Sales Order End of Day and Journals, with the model costs recalculated from the work order. If the Second Manufacturing Cost flag in program PCTM, Cost Type Maintenance, is set to on for the S type cost type, the actual cost is used. If the Second Manufacturing Cost flag in program PCTM, Cost Type Maintenance, is set to off, the setting of the COGSMODELWOCOST_OVERRIDE parameter determines the update. COGSMODELWOCOST_OVERRIDE: N (none), S (standard), or A(actual). Overrides the setting for the update of the model cost in program OESJ, Sales Order End of Day and Journals, when the Second Manufacturing Cost flag in program PCTM, Cost Type Maintenance, is not set to on for cost type S. NDS Cash Drawer Opener ParametersIf the NDS Cash Drawer Opener is installed, determines the address to engage the serial port and open the cash drawer. The NDS Cash Drawer will be opened if a payment record is entered on a sales order for a payment type for which the Cash Drawer flag is set to on in program SPPT, Payment Type Maintenance. For more information, see program OEPX, Counter Sales Shipping. CASH_DRAWER_URL: The web address to engage the serial port and open the cash drawer. Order Level Discount ParametersThese parameters determine how order level discounts are applied to sales orders. Many of these sales orders have fields in program CMDM, Discount Level Maintenance, that control the values assigned to them. If the parameter is changed here, the change will be reflected in program CMDM, Discount Level Maintenance, and vice versa. CMDM_USE_GROSS_ORD_VALUE: Y or N. Determines how the sales order amount will be calculated when determining eligibility for order level discounts. Corresponds to the Order Value Based On radio buttons in program CMDM, Discount Level Maintenance. CMDM_AUTO_APPLY: Y or N. Determines whether discounts will be automatically applied or a pop-up message will be displayed to the user for confirmation before applying the discounts. Corresponds to the Auto apply discounts instead of popup alert flag in program CMDM, Discount Level Maintenance. CMDM_NONSTKS: Y or N. Determines whether order level discounts will be applied to non-stock sales order lines when the price override flag is set to on. Corresponds to the Apply discounts to Nonstocks if price override is on flag in program CMDM, Discount Level Maintenance. CMDM_DISC_OVERRIDES_LINE_DISC: Y or N. Determines whether the initial application of the order level discount to the sales order lines will overwrite existing discounts or whether the [Calc Discount] button must be pressed for that to happen. CMDM_QUOTES_GET_DISCOUNT: Y or N. Determines whether order level discounts are used on sales quotations. Protecting Plant Level DifferencesDetermines whether the buttons in the following programs are disabled so that plant-specific values are not pushed to other plants accidentally: ICMM, Inventory Master Maintenance - [Push $] button ICSM, Inventory Sales Data Maintenance - [Push to Other Plants] button ICCM, Inventory Cost Data Maintenance - [Push to Other Plants] button BMMM, Bill of Material Maintenance - [Make ECL Current] button RTMM, Routing Master Maintenance - [Make Current Rev] button PLANT_PROTECT: Y or N. When set to N, the buttons are enabled. When set to Y, the buttons are disabled. Prevent Credit Card Payment Reauthorization for Point of Sale ordersThis parameter defines the default sales reason code for sales orders entered through point of sale. Sales orders with this sales reason code will not have their credit card payments recalculated when processed through program OESJ, Sales Order End of Day and Journals. POS_CRDR_CODE: Sales reason code from program ARRM, Maintain Sales Reason Codes. Sales orders assigned this sales reason code will not have their credit card payments reauthorized when processed through program OESJ, Sales Order End of Day and Journals. Prospect Deletion in program PRMM, Prospect Master MaintenanceThis parameter determines whether a user is allowed to delete prospect records in program PRMM, Prospect Master Maintenance. For the COMMON user, the application ID, or the Oracle User ID, enter a record for the following key. PRMM_ALLOW_DELETE: Y or N. When set to Y, the user can delete prospect records in program PRMM, Prospect Master Maintenance. When set to N, the user cannot delete prospect records. Purchase Order Price Updates Sales Order Cost OptionsDetermines whether an update to the price of a purchase order line that is assigned to a sales order will also update the sales order line cost. PO_COST_UPDATE_ALLOWED: STANDARD, ALWAYS, NEVER. STANDARD: the sales order cost will be updated according to the standard cost update rules in the Cost Overrides and Updates section. ALWAYS: the sales order cost will always be updated with the purchase order price. NEVER: the sales order cost will never be updated with the purchase order price. Quick Labor Entry SettingsDetermines whether the Actual Hours, Good, and Scrap fields are displayed in program LRQE, Quick Labor Entry and whether the employee number will default to the logged in employee number. These parameters are set up by plant code. LRQE_DEFAULT_EMPNO_pp:Y or N, (where pp is the plant code). For each plant, when set to Y, the employee number from program MUSC, User Security Maintenance, for the logged in user will be entered in the Employee No field. LRQE_HIDE_FIELDS_pp: any combination of ACT_HOUR, UNITS_GOOD, and UNITS_SCRAPPED. Pp is the plant code for the parameter. When ACT_HOUR is entered, the Actual Hours field will not be displayed in program LRQE, Quick Labor Entry. When UNITS_GOOD is entered, the Good field will not be displayed. When UNITS_SCRAPPED is entered, the Scrap field will not be displayed. Reorder Point Allocations CalculationDetermines whether allocations for reorder point will be calculated from the detail records or will be taken from the item plant quantity record. IMRC_SIMPLE_ALLOC: 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. |
|
|
MURM, Initialization Parameter Maintenance Continued |
Reorder Point by Buyer or PlannerDetermines whether the reorder point calculation in program IMRC, Re-Order Point Calculation Management, is calculated by buyer code or planner code. IMRC_PLANNER_BUYER: 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. Reorder Point Including Non-Nettable, Quarantine, and Consigned LocationsNew parameter for new consigned location types. IMRC_INCL_CONSIGNED_LOC: YES or NO. When set to YES, quantity in consigned locations will be considered when calculating reorder point. When set to NO, 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. Reorder Point LoggingThis parameter determines how many days of reorder point records are stored for items processed previously by program IMRC, Re-Order Point Calculation Management. IMRC_LOG_RETAIN_DAYS: the number of work days of past reorder point records that should be retained when program IMRC, Re-Order Point Calculation Management, is run. Required Margin WarningThis parameter determines whether a message will be displayed when the margin for a sales order line falls below a specified margin percentage. This parameter is set up by sales location. OE_REQ_MARGIN_LLL: (LLL = sales location code) Enter the required margin percentage here. This value defaults to 0. When a sales order line item's calculated margin falls below this percentage, a warning will be displayed in the sales order entry program. Return to Vendor ParametersThese parameters determine the functionality of program RTVM, Return to Vendor Maintenance. For the COMMON user, enter a record for the following keys. These parameters are plant code specific. Replace the _PC with the appropriate plant code when setting up these records. ALLOW_RTV_INSERT: Y or N When set to Y, discontinued items can be inserted into return to vendor transactions without moving them to a quarantine location. When set to N, discontinued items must be moved into a quarantine location before they can be inserted into a return to vendor transaction. RTV_HOLD_INSPECT_PC: Y or N When set to Y, the general ledger journal is not created when the return to vendor transaction status changes to Picked. If credit is to be received after the vendor inspects the material, the credit journal entries get written when the Inspect Only flag is set to off. When set to N, the general ledger journal is created when the return to vendor transaction status is changed to Picked. RTV_AUTO_CLOSE_PC: Y or N When set to Y, the return to vendor status changes to Closed after the [Voucher] button is pressed. When set to N, the return to vendor status must be changed to Closed manually. RTV_AUTO_PACK_PRINT_PC: Y or N When set to Y, the return to vendor packing list will be printed automatically from the drill down. When set to N, the return to vendor packing list must be printed manually. RTVM_DEFAULT_REASON_CODE: Reason code from program RERM, Reject/Scrap Reason Code Maintenance. This is the reason code that is used when inserting discontinued items into return to vendor transactions without moving them to a quarantine location. This parameter is only used when the ALLOW_RTV_INSERT parameter is set to Y. RTVM_INSPECT_REASON: The reason code from program RERM, Reject/Scrap Reason Code Maintenance, that indicates that the item needs to be inspected. When entering return to vendor lines in program RTVM, Return to Vendor Maintenance, if the line is assigned the reason code defined here, the Inspect flag will be set to on during the pick cycle. Routing Operations and Engineering SpecificationsThis parameter determines whether engineering specifications assigned to the operations and tools assigned to routings are routing-specific or global. The parameter only affect engineering specification templates assigned to routings in program RTMM, Routing Master Maintenance. RT_TEMPLATE_VALS_FROM_MASTER: Y or N When set to Y, engineering specification templates assigned to routings are global. When a change is made to an engineering specification template on a routing, the change is actually made to the master template definition in program ESTM, Engineering Template Maintenance, thus all routings that are assigned that template are also changed to match. This includes templates assigned to the operations and tools assigned to the routing. When set to N, engineering specification templates assigned to routings are routing specific. When a template is assigned to the routing, the variables and values are copied from the master template to the routing itself. Changes that are made to the routing's template do not affect the master template from which the variables and values were copied. Later changes to the master template are not copied to the routings that were previously assigned that template. This includes templates assigned to the operations and tools assigned to the routing. Sales Location Updates during Sales Order EntryDetermines whether the sales location can be manually changed during sales order entry when the Default Location Rule in program SPON, Order and Invoice Number Control, is set to Login. OE_LOCATION_UPD_ALLOWED: Y or N. When this parameter is set to N, users cannot manually change the location during sales order entry, although the location may change during processing, such as if the ship to location changes and the default shipping location is derived from the ship to location. When this parameter is set to Y, then users can manually change the sales location during sales order entry. Sales Order Copy - Automatic Debit Memo/Credit Memo ConfirmationDetermines whether debit memos and credit memos created from program OECO, Sales Order Copy, will be automatically confirmed upon creation. Debit and credit notes are always confirmed on creation from program OECO, Sales Order Copy. This is a sales location specific parameter. OECO_AUTO_CONFIRM_LLL: Y or N. This is a sales location specific parameter. Replace the LLL with the desired sales location code. Sales Order Batch Shipping ParametersDetermines the default settings of parameters for the background batch shipping process that can be set up in program JOBQ, NDS Job Queue Management. OESB_BG_MAIL_TO: the email address to which failures will be sent for background batch shipping job in program JOBQ, NDS Job Queue Management. OESB_BG_COPY_TO: the email address to which failures will be copied for the background batch shipping job in program JOBQ, NDS Job Queue Management. WEB_PRINT_PREFIX: the missing specification required to change a printed into something reachable from the reports server for printing reports from the background batch shipping job job. This parameter allows us to get the entire name for the printer. For example, \\SERVER\ Sales Order Comment Print Flag DefaultsDetermines the default print flag setting for the sales order header and line comments for newly entered sales orders. OE_LINE_COMMENTS_PRINT_FLAG: Y or N. The setting of this parameter determines the default setting of the print flag for new sales order line comments in the sales order entry programs. OEHEAD_COMMENTS_PRINT_FLAG: Y or N. The setting of this parameter determines the default setting of the print flag for new sales order header comments in the sales order entry programs. Sales Quote to Order Conversion OptionsDetermines whether the estimated ship date, request date, and initials will be recalculated when a sales quotation is converted to a sales order. QUOTE_CONVERT_RECALC_DATES: Y or N. When set to Y, the request date and estimated ship date will be recalculated according to the sales order date, and the initials will be changed to that of the user who converted the quote to the sales order. When set to N, all values will remain as they were entered on the original quote. Service Warranty ParametersThese parameters affect the functionality of program SVMM, Service Master Maintenance. SVMM_SYNC_COMMENTS: Y or N. When set to Y, if the service warranty transaction is created from a sales order, comment changes or additional comments added to the transaction can be updated to the original sales order when the change is saved in program SVMM, Service Master Maintenance. When set to N, the comment will only be written when a sales order or invoice is created from the service warranty transaction. SVMM_AUTO_CONFIRM_XX: Y or N where XX is the sales location code. When set to Y, invoices created in program ARIE, One-Step Invoice Entry, from service warranty transactions entered in this location will be created as confirmed and ready to be processed. When set to N, the invoice must be confirmed in program ARIE, One-Step Invoice Entry, before being processed through OESJ, Sales Order End of Day and Journals. SVMM_START_IN: INVOICE or CUSTOMER. When set to INVOICE, the cursor will start in the Invoice No field when program SVMM, Service Master Maintenance, is run. The sales location and sales reason code cannot be changed when this parameter is set to INVOICE. When set to CUSTOMER, the cursor will start in the Customer No field when program SVMM, Service Master Maintenance, is run. SVMM_LOCS_SYNCH: Y or N. When the SVMM_START_IN parameter is set to CUSTOMER, this parameter determines whether the sales location in the header can be changed, or must be kept in synch with the customer's sales location from program CMMM, Customer Master Maintenance. When set to Y, the sales location cannot be changed. When set to N, the sales location can be changed. SVMM_DEFAULT_RETURN_TO_TECH: Y or N. When set to Y, the Return to Tech flag on the Failed/Return tab in program SVMM, Service Master Maintenance, is set to on automatically. When set to N, the Return to Tech flag on the Failed/Return tab in program SVMM, Service Master Maintenance, is set to off automatically. SVMM_ALLOW_REOPEN: Y or N. When set to Y, if an invoice has not been created on the Failed/Return tab for the service warranty transaction, and the transaction status is Closed, the [Re-open Service] button will be displayed in the header that will reopen the transaction. When set to N, service warranty transactions that have been closed cannot be reopened. SVMM_RTN_MORETHAN_ORIGQTY_SOLD: Y or N. When set to N, the quantity failed, expected, and returned cannot be greater than the original quantity sold for the sales order for that item. When set to Y, the quantity failed, expected, and returned can be greater than the original quantity sold for the sales order for that item. Sales Order Batch Shipping ParametersDetermines the default settings of parameters in program OESB, Sales Order Batch Shipping. BATCH_SHIP_EVAL_INTERVAL_PC: numeric value. This is the default by plant for the Order Eval Interval field in program OESB, Sales Order Batch Shipping. The PC in the parameter above should be replaced with the plant code when setting up this variable. When set to a positive number, this is the number of minutes that a given order will be suspended for shipping evaluation following a failed evaluation. With this feature active, if an inventory transaction occurs which adds inventory, any open sales orders for that item will have their evaluation timers reset so they become available for shipment. When set to a negative number, the feature is disabled. OESB_BG_SEND_TO: the email address to which failures will be sent for background batch shipping job in program JOBQ, NDS Job Queue Management. OESB_BG_COPY_TO: the email address to which failures will be copied for the background batch shipping job in program JOBQ, NDS Job Queue Management. WEB_PRINT_PREFIX: the missing specification required to change a printed into something reachable from the reports server for printing reports from the background batch shipping job job. This parameter allows us to get the entire name for the printer. For example, \\SERVER\ Sarbanes-Oxley (SOX) Password Compliance SetupDetermines whether passwords set up for users in program MUSC, User Security Maintenance, must comply with the Sarbanes-Oxley (SOX) requirements. SOX_PASSWORD_COMPLIANCE: Set to Yes to use the SOX compliance features. When set to anything other than Yes, SOX compliance will not be enforced. SOX_PASSWORD_COUNTDOWN: number of days before the password expiration date for which the user receives a warning that the password will expire. This number should be less than the Password is valid for X days value in program MUSC, User Security Maintenance. Ship To Attn DefaultsDetermines whether during sales order entry, the ship to attention field value will always default from the ship to record's attn field, regardless of the value. SHIP_ATTN_DEFAULT: Y or N. When set to Y, the ship to attn value will always default to the one in assigned to the ship to code, regardless of the value. If the ship to code's attn field is null, it will retrieve the null from the ship to code. When set to N, if the ship to attn is entered in the form, the ship to attn will not be retrieved from the ship to code. Shipping Confirmation ParametersDetermines parameters for the functionality of program OESC, Shipping Confirmation. OESC_BO_RED: Y or N. Determines whether non-zero backorder quantities are displayed in red on the order lines. When set to Y, they are displayed in red. When set to N, they are not. OESC_LINE_SORT: This parameter determines the default setting for the Line Sort field in program OESC, Shipping Confirmation. Choices are: OESC_DISPLAY_MODE: N or O. This parameter determines the default setting for the Display Mode field in program OESC, Shipping Confirmation. When set to N, the pop-list will default to Normal. When set to O, the pop-list will default to Operational. OESC_OPER_DISPLAY_ONLY: Y or N. Determines whether the user can only run program MURM, Initialization Parameter Maintenance, in the Operational Display Mode. Shipping Container Segregation by PlantDetermines the default setting of the Comingle Pallets flag in the sales order header. When the flag is set to on, shipping can be done in any container for an order, regardless of the sales order line plant. When the flag is set to off, a plant cannot ship in containers that are already in use on a sales order line by another plant. COMINGLE_PALLETS: Y or N. When set to Y, the Comingle Pallets flag in the sales order header will be set to on automatically. When set to N, the Comingle Pallets flag in the sales order header will be set to off automatically. Shipping Director SetupNew parameter to determine functionality of the F8 key in OESX, Shipping Director. OESX_F8_MODE: ON or OFF: When set to OFF, F8 will only execute query if the program is in 'enter-query' mode so that if F8 is pressed and the order is in normal mode nothing will happen. When set to on, F8 will execute query when in either normal mode or enter query mode. Tax Exemption Expiration Date DefaultDetermines the default number of days after the system date on which the tax exemption number expires. This parameter is used to calculate the tax exempt expiration date in program CMMM, Customer Master Maintenance, when no date is entered. TAX_EXEMPT_EXPIRE_DAYS: the number of days that will be added to the system date to calculate the default expiration date for tax exemption numbers. Third Party Account Retention from program OEXP, Fast Order EntryDetermines whether third party accounts entered in program OEXP, Fast Order Entry, will be added to the customer master record in program CMMM, Customer Master Maintenance, when a sales order or quotation is created, and the third party account does not already exist. OEXP_SAVE_THP_ACCT: YES or NO. When set to YES, the third party account will be added to the customer master record, with the following requirements: If the ship to is SAME or DROP, the third party account is entered with a null ship to code. If no carrier vendor is entered on the Summary tab, then the account will not be added to program CMMM, Customer Master Maintenance. If the vendor entered does not match the vendor assigned to the ship via code in program SPSF, Ship Via Code Maintenance, then the user will be notified and the account will not be saved. Tool Availability WarningDetermines whether a warning will be displayed when a work order is opened in program WOEM, Work Order Entry/Maintenance, and any tool on the work order's routing does not have the status 'In Plant' in program TLMM, Tool Master Maintenance. WOEM_TOOL_WARN: Y or N. When set to Y, the warning will be displayed in program WOEM, Work Order Entry/Maintenance. When set to N, the warning will not be displayed. Unship DefaultsDetermines the settings of the pick list flag and the order status when a sales order is unshipped in program OESC, Shipping Confirmation. UNSHIP_PICK_PRINT: Y or N. When set to Y or null, the pick print flag for the sales order will be reset to on when the sales order is unshipped. Otherwise, the pick print flag for the sales order will not be reset when the sales order is unshipped. UNSHIP_ORDER_STATUS: O or I. When set to O, the sales order status will be changed to O - Complete when the sales order is unshipped. When set to I, the sales order status will be changed to I- Incomplete when the sales order is unshipped. If the value is not I or O, the status in the Initial Order Status pop-list in program ARLM, Location Maintenance, for the sales location will be used. Vendor Upload Parameter SetupNew parameters for uploading items with program VUTM, Vendor Upload. VUTM_ONE_MFG_PER_ITEM: N or Y. When set to Y, then when items are maintained with program VUTM, Vendor Upload, a relationship of one manufacturer per item is maintained for the manufacturer part record in program ICMX, Mfgr Item / NDS Item Cross Reference. If a new manufacturer ID is on the item record, it will replace any existing manufacturer part record for any other vendor for that item in program ICMX, Mfgr Item / NDS Item Cross Reference. When set to N, new manufacturer/item records are inserted for the new manufacturer. VUTM_MAX_ITEM_LENGTH: The value entered here is used by the upload process to determine whether the incoming item number is too long. If the item number length exceeds the length here, the upload process calls the custom procuser.cfunc8 procedure to determine how to handle the item. If it is still too long after the procuser call, then the item will not be processed. VUTM_UTL_DIR: When uploading files over a web connection, since there is no browse button, this is the directory on the server from which the file will be uploaded. The File Location pop-list must be set to Database. If this parameter is null, the UTL_FILE_DIR parameter is used. VeriSign™ Variable Set upAdded CVV Processing. VERISIGN_CVV_RESPONSE_TYPE_PC: 0 or 1. When set to 0, VeriSign™ should return only the normal response code. When set to 1VeriSign™ will return both the normal response code and a CVV Result Code. VeriSign™ 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 Virtual Private Database SetupDetermines whether a user is using a virtual private database. FF_VPD: Y or N. When set to Y, the user is using a virtual private database. VisaNet™ VariablesAdded new VisaNet™ variables: WFLW_VISA_SETTLE_DAILY_PC: YES or NO. Determines whether a workflow will be sent to the employee set up to receive the NDSVISASET workflow record in program WFWM, Workflow Template Maintenance, when the VisaNet™ batch is settled. When set to YES, a workflow will be sent every time a batch is settled. When set to NO, a workflow will only be sent if the settlement appears to be out of balance with what NDS Applications has calculated that the settlement amount should be, either in regard to the number of payment lines or the total payment amount. VISANET_CVV_RESPONSE_TYPE_PC: 0 or 1. When set to 0, VisaNet™ should return only the normal response code. When set to 1, VisaNet™ will return both the normal response code and a CVV Result Code. VisaNet™ 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 Visa encryption keys VISANET_USE_CVV_PC: Y or N. When set to Y, VisaNet™ will perform a card verification code value check (3-4 digit check on the back of the card). Web Mail Server Interface UsageForces report transmission via email through the database server's SMTP when running in client-server mode, allowing the email to overcome message length limitations or other restrictions posed by the client based mail tools and interface. USE_WEB_MAIL: Y or N. When set to Y, the transmissions will be sent through the database server's SMTP rather than using the client based mail tools. When set to any other value, the client based mail tools will be used. Web Sales Order DeterminationThis parameter determines which sales orders are considered web sales orders. WEB_CRDR_CODE: Sales reason code from program ARRM, Maintain Sales Reason Codes, that indicates the sales order is a web sales order. Will Call Hold SetupDetermines whether the will call hold feature is activated from sales orders shipping. WILL_CALL_HOLD: Y or N. When set to Y, sales orders with the sales reason code of W - Will Call Hold will be placed on will call hold in program OESC, Shipping Confirmation. When set to N or missing, sales orders with the sales reason code W - Will Call Hold will not be placed on hold during shipping. Work Order Creation Status for Model Items on Sales OrdersDetermines whether work orders created for model items on sales orders are created with the status Released or Pending. Enter a record for the following key. AUTO_RELEASE_MODULAR_WO: Y or N. When set to Y, work orders created for modular items on sales orders will be created with status Released. When set to N, work orders created for modular items on sales orders will be created with status Pending. Work Order Inventory Picking ParametersAdditional parameters added. The Auto Pick flag in program MRPE, Work Order Pick List Entry, can be defaulted to on when the [Start Pick] button is pressed, and a warning can be displayed if not all items have been picked when the [Process Pick] button is pressed. MRPE_DEF_AUTO_PICK: YES or NO. The setting of this parameter determines whether when the Start Pick button is pressed in program MRPE, Work Order Pick List Entry, the Auto Pick flag will be set to on for all components. When set to YES, the flag is set to on. MRPE_AUTO_PICK_WARN: YES or NO. The setting of this parameter determines whether when the Process Pick button is pressed, the user will be warned if any required components have not been picked, and allowed to cancel the process to correct it. When set to YES, the warning is displayed. Work Order Optional Control Item Receipt without Control NumbersDetermines whether control number entry is required when receiving to or adjusting a controlled item in a non-controlled location with program MRFE, Finished Goods Receipts Entry. WO_CONTROL_OPTIONAL: Y or N. When set to N, a control number must be entered for the item when it is received. 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. Workflow Variable SetupAdded new workflow parameter. WFLOW_EMAIL_RECIPIENT: Y or N. Setting of this parameter determines whether the default setting of the Email Recipient flag is on or off for manually created workflows. Zip Code ValidationDetermines whether a warning or an error is displayed when an invalid zip code is entered during sales order entry for a country with the Validate Zip Code checkbox set to on in program SPNM, Country Code Maintenance. For the COMMON user, enter the following key: OE_ZIP_WARN_ONLY: Y or N.
|
|
Added Personal Permissions flag to page 2 and 3. When set to on, and the user's security group is updated, entries with this flag set to on will not be overwritten. Sarbanes-Oxley (SOX) Compliance Features for Password ManagementWhen using the Sarbanes-Oxley (SOX) Compliance Features, when logging into NDS Applications, the system checks to see if the user's password is expired or will expire in a set number of days. If it is, then a message is displayed: "Your password expires on mm-dd-yyyy at hh24:mi". The user can select Change Now to change the password or Change Later to change it at a future time before their password expires. If Change Later is chosen, the menu is displayed. The SOX_PASSWORD_COUNTDOWN parameter in program MURM, Initialization Parameter Maintenance, must be greater than 0. The message will only be displayed if the password expiration date/time is within SOX_PASSWORD_COUNTDOWN days of the expiration date. When the user is changing the password, the new password must be the minimum length defined in program MUSC, User Security Maintenance, for the user. The new password must be different than the previous password and must contain at least one character from each of the four groups: capital letters, lowercase letters, numbers, and special characters. For all users, verify the following: Password Minimum Length value is set to 8 or higher. Password is valid for X days value is greater than 0. Allow User to Change Password flag is set to on. Each user password contains at least one character from each of the four groups: capital letters, lowercase letters, numbers, and special characters. When the Expire Password Now button is pressed, the Change Login screen is displayed to allow you to change the user's password and maintain the Force password change at next login flag. On Change Login screen, the Force password change at next login flag is set to on automatically and cannot be modified if the SOX_PASSWORD_COMPLIANCE parameter is set to Yes in program MURM, Initialization Parameter Maintenance. When this flag is set to on, the expiration date is set 10,000 days before the current date. The user is then forced to change their password on the next log in. |
|
|
For more detailed information, see the program documentation. Split program into tabs. The Current Definition tab contains the current definition for each ID Class. The Possible Additions tab includes the table and column combinations that contain the current set of column names in the NDS ID cross reference table, but do not exist in the table because they have been added to the database since the last update or they should not be updated as part of this ID class. The list may not be complete for new ID classes. The Possible Deletions tab includes the table and column combinations that exist in the NDS ID cross reference table, but no longer exist in the database and should probably be removed. The ? - Quick Help - tab includes some quick help information on running this program. |
|
|
Added new sequence - IAL_BATCH_SEQ for the automatic generation of inventory adjustment batch numbers. Added new sequence LABOR_DETAIL_PK for the automatic generation of the primary key for labor entries. Added a new pop-up screen that displays a comment to describe the usage of the record type. To view/maintain all comments for all record types, click on the [Comments] To view/maintain comments for the currently selected record type, click on the [Zoom] |
|
|
Added Remit to Zip by Length to Check Sort options. When this selection is chosen, checks are printed in order by the length of the zip code on the vendor's remit to addresses first, and then by zip code. |
|
|
Added Location, Mail Class, and Primary Catalog for Location fields for each catalog. |
|
|
Increased number of characters allowed for miscellaneous codes to ten. Added two new miscellaneous code types. User Calculated. Codes with this value call the custom procedure procuser to determine what the miscellaneous amount should be. Promo Code. Codes with this value were created automatically when a promotion was added to a sales order in a sales order entry program. Settings for these codes are generated based on the promotional code settings in program OEPM, Sales Order Promotions Maintenance.
|
|
|
Modified for rewrite of the Forecast Filter for Large Sales Spikes feature. Removed the Min Large Sales Qty and Large Sales Limit Pct fields as they are no longer used in the calculations. Modified the functionality of the Models are Treated as Kits for OE Allocation flag. This flag now determines the default setting of the Treat Model as Kit flag for new models in program MOTM, Modular Bill Maintenance. The Treat Model as Kit flag determines how sales allocations are created and inventory is relieved for a model. For more information, see Model Treatment for Allocations and Shipping. Added tabs for the different setup groups. |
|
|
Zip code formatting and validation for sales order entry is set up by country code in this program. When a zip format mask is entered for a country code, the zip or postal code entered during sales order entry will be formatted as follows: When the zip code is entered on the sales order address, any separators that were entered are removed. The format mask is applied to the entered zip code. If characters in the resulting formatted zip code violate restrictions imposed in the format mask, the zip code format is invalid. The sales order entry programs will return an error message if the format is violated, and entry cannot continue until the zip code format is corrected. The [Reformat Existing Zip Codes] button should be used when the format mask is changed, as changing the format mask can invalidate existing zip codes. When pressed, this button will mass change all zip codes to use the new format in open sales orders, customer records, dealer records, prospect records, mailing addresses, and tax rates. When the country has the Validate Zip Code checkbox set to on, the zip codes entered during sales order entry are validated against the zip codes entered in program SPZM, Zip Code Maintenance. If there are separators in the entered zip code, validation is applied to all portions of the zip code. If a zip code entered on a sales order does not exist in program SPZM, Zip Code Maintenance, the program will return either an error or a warning, based on the setting of the OE_ZIP_WARN_ONLY parameter in program MURM, Initialization Parameter Maintenance. When the OE_ZIP_WARN_ONLY parameter is set to Y, a warning will be displayed. When the OE_ZIP_WARN_ONLY parameter is set to N, an error will be displayed, and the zip code must be corrected before the sales order can be saved. In the Zip Format Mask field, enter the format mask for zip codes entered for this country during sales order entry. The following entries are valid. A Alpha characters (A-Z) only in this position. 9 Numeric characters (1-9) only in this position. X Alpha or numeric characters allowed in this position. - , + : ; / . <space> The entered separator character should be inserted in this position. Set the Validate Zip Code checkbox to the desired setting. When set to on, zip codes entered on sales orders will be validated against zip codes defined in program SPZM, Zip Code Maintenance. When set to off, zip codes entered on sales orders will not be validated against existing zip codes.
|
|
|
New Default Location Rule pop-list by financial enterprise. Default Sales Location DerivationThe sales location for sales orders can be derived from three locations: The customer shipping record. The customer master record. The plant assigned to the logged in user. Each financial enterprise can be set up differently. 1. In the middle block, for the desired enterprise, set the Default Location Rule as desired. Customer: sales order sales locations will be defined by the sales location assigned to the customer in program CMMM, Customer Master Maintenance. Login: sales order sales locations will be defined as the first sales location in program ARLM, Location Maintenance, that is assigned the same plant as the plant assigned to the logged in user. When this option is selected and the OE_LOCATION_UPD_ALLOWED parameter in program MURM, Initialization Parameter Maintenance, is set to N, users cannot manually change the location during sales order entry, although the location may change during processing, such as if the ship to location changes and the default shipping location is derived from the ship to location. Shipping: sales order sales locations will be defined by the ship to record assigned to the sales order. The sales location will be taken from the customer ship to record in program CMMM, Customer Master Maintenance. If the ship to record is SAME, the sales location for the customer will be used. 2. Press [Commit}. |
|
|
Added ability to create PPH charges for negative gross order amounts and negative miscellaneous values. To create a negative PPH charge for a credit memo, set up a negative gross order amount (e.g. -9999999) along with a negative miscellaneous value for the desired catalog ID. Be sure that there is a gross amount record for the same catalog ID and miscellaneous code so that positive invoices will not be assigned the negative charge. |
|
|
Added special actions to print in a list for each payment type. Special actions include VeriSign Processed, Recalculation Required, or Open Cash Drawer. |
|
|
Added Cash Drawer flag which determines whether the cash drawer will be opened in program SPPT, Payment Type Maintenance, when payment records with this payment type exist on the sales order. When this flag is set to on, if there is a payment record with this pay type when the sales order is processed through OEPX, Counter Sales Shipping, the cash drawer will be opened at the end of the transaction. You must have the NDS Cash Drawer Opener feature installed for the cash drawer to open. |
|
|
New column added, Preauthorization Allowance. For each ship via code, the user can specify an arbitrary estimated freight allowance, which is added to all VisaNet™ authorizations for orders with that ship via code. This ensures that settlements will not end up being greater than authorizations due to variances in freight amounts. This value is added even when a freight amount is entered on the sales order. New WorldEase flag added to indicate that the ship via code is used by the Connectship / WorldEase Interface. When this flag is set to off for a ship via code, sales orders to which the ship via code is assigned cannot be sent to the Connectship / WorldEase Interface when shipping the sales order with program OESC, Shipping Confirmation, or program OESX, Shipping Director. For more information, see the Clippership Interface and Connectship / WorldEase Interface section. |
|
|
Modified terms code calculation for D type discounts and due dates. When the type of discount is D - Day of the Month, the entry in the Days field is the day of the month on which the discount is due. The date is determined by the cutoff date. If the invoice date is before the cutoff day, the discount due date will be on this day of the month in the current month. If the invoice date is on or after the cutoff day, the discount due date will be on this day of the month in the next month after the invoice date. For example, if the cutoff day is 10, the discount day is 25, and the invoice date is between 03-01-04 and 03-09-04, the discount due date will be 03-25-04. If the invoice date is 03-10-04 through 03-31-04, the discount due date will be 04-25-04. When the type of discount is D - Day of the Month, the entry in the Cutoff field is the day of the month that is used to determine whether the discount will be in the current month or the next month after the invoice date. For example, if the cutoff day is 10, the discount day is 25, and the invoice date is between 03-01-04 and 03-09-04, the discount due date will be 03-25-04. If the invoice date is 03-10-04 through 03-31-04, the discount due date will be 04-25-04. When the net due type is D - Day of the Month, the entry in the Days field is the day of the month on which the invoice is due. The date is determined by the cutoff date. If the invoice date is before the cutoff day, the invoice due date will be on this day of the month in the current month. If the invoice date is on or after the cutoff day, the invoice due date will be on this day of the month in the next month after the invoice date. For example, if the cutoff day is 10, the net due day is 25, and the invoice date is between 03-01-04 and 03-09-04, the invoice due date will be 03-25-04. If the invoice date is 03-10-04 through 03-31-04, the invoice due date will be 04-25-04. When the net due type is D - Day of the Month, the entry in the Cutoff field is the day of the month that is used to determine whether the invoice will be due in the current month or in the next month after the invoice date. For example, if the cutoff day is 10, the net due day is 25, and the invoice date is between 03-01-04 and 03-09-04, the invoice due date will be 03-25-04. If the invoice date is 03-10-04 through 03-31-04, the invoice due date will be 04-25-04. |
|
|
Added Catalogs Tab to allow catalogs to be assigned to a contact. |
|
|
Added Latitude and Longitude fields for the Assigning Dealers to Leads using Proximity feature. Added Area Code field. |
|
|
Added ability to import and export server side files from this program regardless of whether you are running in web mode or client server mode. Added File located on pop-list to indicate from where the file will be obtained. |
|
|
Set the Limit Output to the Selected Oracle User checkbox to the desired setting. When set to on, only debug messages generated for the logged in user will be displayed. This facilitates running in debug mode for a specific activity on a large system where many users are active at the same time. |
|
|
Added new list of values definition to this program - OEXPSRCDOC- used for the Src Doc ID field in program OEXP, Fast Order Entry. |
|
|
Made Version History text updateable. |