Modified to allow the customer to be charged for a different ship via code than the company is charged. When an invoice ship via code is assigned to the sales order's ship via code in program SPSF, Ship Via Code Maintenance, the invoice ship via code is also passed in. The rate charged to the company shipping the order is returned as the fright amount, and the amount to be charged to the customer is the returned as the alternate freight amount. For more information, see program SPSF, Ship Via Code Maintenance.
Credit card information from program CMCM, Customer Credit Maintenance, has been moved into a separate form in order to prevent access to credit card information by unauthorized users. As a separate form, it can be protected using the security features in program MUSC, User Security Maintenance.
Moved the credit card information into a separate form (CCCM) in order to prevent access to credit card information by unauthorized users. As a separate form, it can be protected using the security features in program MUSC, User Security Maintenance.
Added Billing Address Line 1 and Billing Zip Code to Credit Card Information.
Comments displayed here are sorted according to the CUST_COMMENT_SORT parameter in program MURM, Initialization Parameter Maintenance.
Added functionality to define pricing contracts for item price groups. Contract pricing by discount can be defined on the Quantity Breaks screen.
Added a Reference field to the contract item record to allow a note to be entered by the user.
Program CMCP, Customer Contract Maintenance, allows you to create multiple contracts for the same item for a customer. If an order is placed for an item for which more than one contract is effective, the system selects the firm contract price first, and if no firm price exists, it will select the lowest contract price.
New field added. Set the Discounts will be applied to Contracts flag to the desired setting. This field sets the value of the CMDM_CONTRACTS_GET_DISCOUNT parameter in program MURM, Initialization Parameter Maintenance.
Set this flag to on if the order level discounts will be applied to sales contracts.
Set this flag to off if the order level discounts will not be applied to sales contracts.
Changed Additive to CMPC% field label to be Additive to List Discount. Modified functionality as follows:
Checkbox set to on or off determines how the order level discount will be applied to the sales order lines for this customer.
If this flag is set to on, the order level discount will be applied to all lines on the customer order. If the sales order line has a previous discount entered by a user or from a price matrix entry in program CMPC, Price Matrix Maintenance, the order level discount will be added to the sales order line discount.
If this flag is set to off, the order level discount will be applied to all lines on the customer order, overriding any discounts applied from price matrix entries in program CMPC, Price Matrix Maintenance, or entered by users
Split program into tabs. Added Items Tab.
Items Tab
The Items tab displays a list of the items sold to this customer. The information includes the financial enterprise, period in which the item was sold, item number and description, quantity shipped, extended price and extended cost. The total extended price, extended cost, margin, and margin percentage for the customer is displayed at the top of the tab.
You can sort the items displayed using the Sort By pop-list at the top of the tab. Choices are by item and year month or by year month and item.
Values displayed are initially those for the current logged in financial enterprise. To view discount summary information for all enterprises, press the [Show Summary Across Enterprises] button.
Added minimum order value by location to the Enterprise tab. In the Location Overrides section, you can set up minimum order values for this customer by sales location. The entries here override the setting for the sales location in program ARLM, Location Maintenance.
The minimum order value can be set up by location and by customer. To set up the minimum order value for the location, go to program ARLM, Location Maintenance. To set up the minimum order value for a customer, go to program CMMM, Customer Master Maintenance.
If the gross order value of the sales order is equal to or less than the amount entered for the location or customer, the miscellaneous code assigned in the MOV Misc Cd field in program ARLM, Location Maintenance will be applied to the sales order.
See the Minimum Order Value for Sales Orders section of the Sales Order Entry Features for more information.
Modifications for ship to enterprise record creation. The ship to enterprise record will not be created automatically. You should only enter information for the ship to enterprise record if it is different than the default customer information.
If a customer has the Status pop-list set to Inactive on the Attributes tab, the customer name in the header will be displayed in red.
Removed Third Party Account Restriction for Customers parameter RESTRICT_CMMM_THP_ACCTS in program CMMM, Customer Master Maintenance. Entry of third party accounts in program CMMM, Customer Master Maintenance, no longer requires a duplicate entry in program VESM, Third Party Vendor Maintenance.
Added the Shipping Mail/Fax Tab to set up Printing Reports for Customers to Email and Printing Reports for Customers to Fax for specific ship to codes. For more information, see those sections of the Help.
On the Addresses tab, added the Electronic Invoicing section of this tab, in which there are four radio buttons, which can not be modified. Whether or not the customer receives invoices electronically is determined by the ARINVOICE document type on the customer's Mail/Fax tab. This information can also be updated in program OEXP, Fast Order Entry, when a sales order is being entered for the customer.
Email: The Send Type pop-list for the ARINVOICE document type for this customer is set to eMail.
Fax: The Send Type pop-list for the ARINVOICE document type for this customer is set to Fax.
Mail: The Send Type pop-list for the ARINVOICE document type for this customer is set to Printed.
Unsure: The Send Type pop-list for the ARINVOICE document type for this customer is set to Printed, and the Person's Name field is set to Unsure.
On the Mail/Fax tab, added the Person's Name field and the Date Activity Last field to support the electronic invoicing section on the Addresses Tab.
Added new Marketing Tab, on which users can enter and maintain marketing data for customers. Once this data has been entered for customers, it can be analyzed by custom reports to help direct product marketing to the customers that can benefit the most from those products. Although this tab was originally intended to contain Dunn & Bradstreet marketing information, it's not required.
Added Fax No on Address Tab to contain the customer's main fax number.
Only catalogs with the Used for Pricing flag set to on in program SPCG, Catalog ID Maintenance, are displayed in the Catalog pop-list.
Added new tab to contain NAICS codes for the Marketing Tab in program CMMM, Customer Master Maintenance.
Clarification on default directories. In the File Name field, enter the directory and file name that will be exported. To use the default directory, enter only the file name in the File Name field.
* The default directory for exports to the Client Server is defined by the CMSU_EXPORT_DIR parameter in program MURM, Initialization Parameter Maintenance. Client Server is no longer an option in NDS Version 8 on Oracle 10g.
* The default directory for exports to the Database Server is defined by the UTL_FILE_DIR parameter in program MURM, Initialization Parameter Maintenance.
Added Default Catalog pop-list to allow the user to define the catalog ID that will be put on the exported records.
Clarification on default directories. In the File Name field, enter the directory and file name that will be exported. To use the default directory, enter only the file name in the File Name field.
* The default directory for exports to the Client Server is defined by the CMSU_EXPORT_DIR parameter in program MURM, Initialization Parameter Maintenance. Client Server is no longer an option in NDS Version 8 on Oracle 10g.
* The default directory for exports to the Database Server is defined by the UTL_FILE_DIR parameter in program MURM, Initialization Parameter Maintenance.
If the OE_ANY_COST_CHANGE parameter in program MUJM, Menu and Job Parameter Maintenance, is set to Y, then the cost may be changed on sales orders entered in program OEOE, Sales Order Entry/Maintenance, regardless of the rules defined here.
When the S type cost is non-dynamic, i.e. is not average or actual cost, users cannot modify the unit cost for drop shipped non maintain on hand items in program POSE, Create Purchase Orders from Sales, unless the Include Drop Ship Lines flag is set to on in program POPM, PO / Receiving Parameter Maintenance.
Modified to allow rebate frequency to be Annual, Quarterly, or Monthly. Added period number to the form.
Modified to allow the entry of user discounts, additional discounts, and flat discounts when verifying item prices.
When the extended price has a surcharge added to it, it is displayed in purple.
Added ability to batch transmit sales acknowledgements in the background using program JOBQ, NDS Job Queue Management, Windows Scheduler, or another job scheduler such as Cron. For more information, see the program documentation.
Added protected allocations quantity and quantity on order.
Modified screen so that backorders are displayed in the lower block for the item selected in the upper block. Added protected allocations and quantity on order. Added additional order information for the back orders.
Backordered items are now colored as follows:
* Red: Kit and Model as Kit items.
* Blue: Non-stocked items
* Green: Model items.
* Purple: Component items.
* Brick Red: Non-maintain on hand items.
New program in which users view, reauthorize, and reconcile credit card payments for sales orders. This program has four tabs:
Open Tab: This tab displays all credit card payments on open/un-invoiced sales orders, and allows the user to reauthorize the payments.
Posted - OESJ Tab: This tab displays credit card payments that have been processed through program OESJ, Sales Order End of Day and Journals, but have not been reconciled with a bank statement. Users can assign a bank receipt date to the payments on this tab.
Posted - Bank Tab: This tab displays credit card payments that have been processed through program OESJ, Sales Order End of Day and Journals, and have been reconciled with a bank statement through the assignment of a bank receipt date. Users can remove bank receipt dates from payments on this tab.
Tracking Tab: This tab displays the sales order tracking information for the selected sales order.
Added new parameter OECH_CUST_PO_TEXT in program MURM, Initialization Parameter Maintenance. If a value is entered for this parameter, when 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. The value entered for the parameter should not be greater than 30 characters.
When reversing payments the last four digits of the credit card will be stored in the Driver's License/Authorization field. At this time, the sales order system is not then validating a user entered credit card number against it.
Restrictions on copying between order types and statuses have been removed. The following restrictions still apply:
* If copying to an new order type of ORD, then the new status must be Incomplete, Open Order, Quote, or Template.
* If copying to a new order type of anything but ORD, the new status must be Fully Shipped.
Added missing order discount, pricing, and backorder ship complete fields.
On the Order Tracking screen, added the Show Only Track Code pop-list. To view a single tracking code, select the tracking code that you wish to view. The records will be re-queried with only the records for that tracking code displayed. To view all tracking codes, select All in the pop-list.
On the Addresses screen, if the OEDI_SENDTO_CHECKBOX parameter in program MURM, Initialization Parameter Maintenance, is set to Y for the user, the customer fax and email send to information can be changed for a sales order here. This information can also be added to the customer master record from the sales order, if desired. For more information, see the Fax / Email Override section of the Sales Order Entry Features.
Changes to Credit Card Handling:
After credit cards are authorized, the credit card number is hidden, and only the last four digits are displayed.
The CVV code is not stored in the database. Storing of the CVV code can be a custom.
Added ability to update the credit card information in program CMCM, Customer Credit Maintenance, from the Payflow Pro Response screen.
Added Alloc Protection pop-list under Order Codes button in the header and the Protect Allocation flag to the General tab under the Other Details button for the line items. These flags are used in conjunction with the Protected Allocations for Background Batch Shipping feature.
The extended price is displayed in purple when a customer/item surcharge has been added to it.
OEHP, Order History Purge by Date
Added Archive Purged Records flag, which when set to on will store the purged records in the archiving tables. Added [Show Archive Log] button for users to view the archive log, which includes the information about when the records were last archived/purged. Added [Show Analyze Dates] button. Press this button before the purge to determine the most recent and oldest analyze dates of the tables involved in the purge. You should not run the purge unless the analyze is very recent and all tables have been analyzed. Contact your system administrator if this is not the case.
Restricting Releaseable Hold Codes
There are four ways to control the hold codes that can be queried and released in this program.
In the header of the program, in the Query List of Hold Codes, before querying the sales orders you can enter a list of hold codes that you want to view. Separate the hold codes with a comma.
In the header of the program, in the Exclude Hold Codes field, before querying the hold codes, you can enter a list of hold codes that you do not want to view. Separate the hold code with a comma.
In program MURM, Initialization Parameter Maintenance, for the OEHR_EXCLUDE_HOLD parameter, you can enter a list of hold codes, separated by commas, that will not be displayed in this program for release. This parameter corresponds with the Exclude Hold Codes field. If an entry is made for this parameter, those entries will be displayed in the Exclude Hold Codes field that field will not allow updates. If this parameter's value is left blank, then entries can be made in the Exclude Hold Codes field.
In program MURM, Initialization Parameter Maintenance, for the OEHR_INCLUDE_HOLD parameter, you can enter a list of hold codes, separated by commas, that will be displayed in this program for release. This parameter corresponds with the Query List of Hold Codes field. If an entry is made for this parameter, those entries will be displayed in the Query List of Hold Codes field and that field will not allow updates. If this parameter's value is left blank, then entries can be made in the Query List of Hold Codes field.
New program in which users can record the shipment of items on inter-company sales orders. In this program, the sales orders are picked by item. When the item number and quantity is entered, the program determines which sales order is being shipped. If there are multiple sales orders for the item, the sales order with the oldest due date will be selected, although this can be overridden by the user.
Added the plant associated with the sales order line, sort by pop-list and the Exclude Invoiced flag, which prevents invoiced orders from being displayed when set to on.
Added the B/O Ship Complete flag to the Order Codes screen. When the B/O Ship Complete flag is set to on for a sales order, the backorder for the sales order will have the Ship Complete flag set to on automatically when it is generated during sales order processing with program OESJ, Sales Order End of Day and Journals. The default value for this flag comes from the Make BO Ship Complete flag for the sales location record in program ARLM, Location Maintenance.
Added functionality for new fields in program ARLM, Location Maintenance. Added display of the discounts on the sales order line. Added Eff Disc % field to the sales order line. Added new Pricing Tab to Other Details popup screen.
If an item is entered for which the Shippable from plant XX flag is set to off for the plant on the sales order line, a warning will be displayed.
The Customer Price Group and Description can be displayed in the header to the right of the Loc field. If the OEOE_SHOW_PRICE_GROUP parameter is set to Y in program MURM, Initialization Parameter Maintenance, the price group and description are displayed.
For customers with the Revenue Pricing method, if the OE_QUICK_PRICE parameter in program MURM, Initialization Parameter Maintenance, is set to Y, then pricing will not occur until the sales order is opened, or until the user navigates to the Summary screen.
The order in which sales orders will be listed in this program is determined by the OE_DEFAULT_SORT parameter in program MURM, Initialization Parameter Maintenance.
On the Item Search screen, inactive and discontinued items are displayed as grayed out, but they can still be selected, if desired.
Modified the Substitutes screen to include the unit and plant fields for which the substitute item is valid.
When the unit price is green, the price is an override price or a contract price.
On the Order Tracking screen, added the Show Only Track Code pop-list. To view a single tracking code, select the tracking code that you wish to view. The records will be re-queried with only the records for that tracking code displayed. To view all tracking codes, select All in the pop-list.
Changes to Credit Card Handling:
After credit cards are authorized, the credit card number is hidden, and only the last four digits are displayed.
The CVV code is not stored in the database. Storing of the CVV code can be a custom.
Added ability to update the credit card information in program CMCM, Customer Credit Maintenance, from the VeriSign™ Response screen.
When payments are saved or when the [Payflow Pro] 
button is pressed, credit card payments will be automatically calculated, including surcharges and payment amounts.
Modified so that when the Print Pick List and Print Pack List flags are changed in the header, the user is asked if they wish to update the appropriate line item flags as well.
Added Alloc Protection pop-list under Order Codes button in the header and the Protect Allocation flag to the General tab under the Other Details button for the line items. These flags are used in conjunction with the Protected Allocations for Background Batch Shipping feature.
The extended price is displayed in purple when a customer/item surcharge has been added to it.
New [Update Existing Orders] button on the Promotional Items - Item and Promotional Items - Cust tabs. Press this button to update existing open orders and back orders that meet the criteria for the promotion.
If a sales order is a web order (determined by the WEB_CRDR_CODE parameter in program MURM, Initialization Parameter Maintenance), the promotions are included as a line item discount, and the calculation of the miscellaneous amount for the miscellaneous charges section of the order will not include it.
Changes to Credit Card Handling:
After credit cards are authorized, the credit card number is hidden, and only the last four digits are displayed.
The CVV code is not stored in the database. Storing of the CVV code can be a custom.
Added ability to update the credit card information in program CMCM, Customer Credit Maintenance, from the Payflow Pro Response screen.
When payments are saved or when the [Payflow Pro] button is pressed, credit card payments will be automatically calculated, including surcharges and payment amounts.
New parameters added to program ILPM, Plant Code Maintenance, affect batch ship processing, background batch shipments, and move ticket creation.
Protected Allocations in Background Batch Shipping
This feature is only applicable to background batch shipping and will not have any effect when program OESB, Sales Order Batch Shipping, is run from the menu. Quantities for sales order line items with this feature activated are protected from being shipped on other sales orders. When the background batch shipping process is run, protected inventory is not included in the calculations for quantity available for other sales order lines for the same item.
Allocations are only protected up until the estimated ship date for the sales order. Once the estimated ship date has passed, the background batch shipping process will remove the protection. If the user changes the estimated ship date for the sales order, the allocations will remain protected until the new estimated ship date passes. When the expiration date is about to pass, the Alloc Protection pop-list in the header of the sales order displays Expires Soon.
The ALLOCEXPIR workflow can be set up in program WFWM, Workflow Template Maintenance, to send a warning when protected allocations are about to expire. The PROTECTED_ALLOC_WARN_DAYS parameter in program MURM, Initialization Parameter Maintenance, determines the number of days before the estimated ship date that the workflow will be sent. The background batch shipping process triggers the workflow. If the workflow and parameter have not been set up, the workflow notification will not be set, but the protected allocations will still be expired when appropriate by the background shipping process.
Protected allocations for an item can be viewed in program ICSS, Stock Status Inquiry.
There are two ways to activate this feature for sales order line items.
* You can set the Alloc Protection pop-list to Protected under the Order Codes button in program OEOE, Sales Order Entry/Maintenance, for the order. When this pop-list is set to Protected, the Protect Allocation flag is set to on for all line items on the sales order.
* You can set the Protect Allocation flag is set to on for a specific line item on the General Tab of the Other Details button. This will set the Alloc Protection pop-list to Protected in the sales order header.
Limitations
Protected allocations are only applicable to background batch shipping and will not prevent shipment of the protected inventory from program OESC, Shipping Confirmation, or program ARIE, One-Step Invoice Entry.
Protection settings are not carried to backorders
Protection settings are not copied when copying orders with program OECO, Sales Order Copy.
Protection settings are not reset when an order is unshipped.
Added Ship Plant field. Enter the plant for which you are shipping sales order lines. The default is the user's logged in plant. When the [Ship Order] button is pressed, the user can select from only the entered plant, all plants, or abort shipping.
Changes to Credit Card Handling:
After credit cards are authorized, the credit card number is hidden, and only the last four digits are displayed.
The CVV code is not stored in the database. Storing of the CVV code can be a custom.
Added ability to update the credit card information in program CMCM, Customer Credit Maintenance, from the Payflow Pro Response screen.
When payments are saved or when the [Payflow Pro] button is pressed, credit card payments will be automatically calculated, including surcharges and payment amounts.
Added [Packing Docs] button to allow users to print the packing documents for a sales order, similar to program OESX, Shipping Director. Packing documents include labels, license plates, packing lists, NAFTA documents, AIAG labels, MSDS Sheets, and invoices.
The OESC_ALLOW_PRICE_CHANGES parameter in program MURM, Initialization Parameter Maintenance, determines whether or not sales order line items can have their prices modified during shipping with this program.
When the parameter is set to Y, users can set the Override flag to the desired setting and modify the unit price, or they can change the extended price to force a flat discount for the line item
When the parameter is set to N, no changes can be made to the line item pricing.
The extended price is displayed in purple when a customer/item surcharge has been added to it.
Batch Invoicing
Sales order end of day processing with program OESJ, Sales Order End of Day and Journals, can be run using a batch file in your scheduled tasks on your operating system. Some custom settings are required, but this is one of the ways that you can automatically run sales order processing.
Users will need to write their own scripts to call the batch invoicing process. For assistance, contact NDS Technical Support or NDS Professional Services.
The script needs to call procoesj.batch_oesj. Parameters that can be passed in include:
Sales order number
Manufacturing Enterprise Code
Plant Code
Login string (required if running reports)
Run Reports Y/N
Post to GL Y/N
The batch file calls up to four different SQL files for the four steps of the process.
The first file processes the sales orders based on the enterprise for the oracle user, using the system date as the batch date. The OESJ_BATCH_DATE_OFFSET parameter in program MURM, Initialization Parameter Maintenance, determines the number of days to subtract from the system date to get the cutoff ship date for the batch run.
The second file clears the detail table.
The third file posts the sales journal to the general ledger.
The fourth file completes final processing tasks.
Even though the process is run through your operating system's scheduled tasks, you can view the batch information later in program OESJ, Sales Order End of Day and Journals, including:
The status message from the sales processing run.
The accounts receivable batch number for running program OESJH, Sales Order Journal History.
The first and last journal created for the batch for running program GLPLJ, GL Journal Transactions Posted by Journal Report.
Uses the LIMIT_QUERY_ROWS parameter from program MURM, Initialization Parameter Maintenance, to warn the user if too many rows are being queried.
The F4 key on the keyboard processes the shipment as if the [Process Shipment] button was pressed.
Modified tracking to include the name of the employee in the notes field for automatically generated tracking records.
Added the B/O Ship Complete flag to the Customer Tab. When the B/O Ship Complete flag is set to on for a sales order, the backorder for the sales order will have the Ship Complete flag set to on automatically when it is generated during sales order processing with program OESJ, Sales Order End of Day and Journals. The default value for this flag comes from the Make BO Ship Complete flag for the sales location record in program ARLM, Location Maintenance.
If an item is entered for which the Shippable from plant XX flag is set to off for the plant on the sales order line, a warning will be displayed.
On the Item Search screen, inactive and discontinued items are displayed as grayed out, but they can still be selected, if desired.
Added additional discount and contract fields to Items Tab. Added new buttons to the Items tab. Changed the look of the Custom Popup button.
Custom Pop-Up 
- Display the information custom popup screen.
Re-query Line Items 
: Press this button to force an automatic query of the sales order lines.
Save Changes 
: Press this button to save the changes to the current order.
Modified the Items Pg2 tab to include the unit and plant fields for which the substitute item is valid.
Changes to Credit Card Handling:
After credit cards are authorized, the credit card number is hidden, and only the last four digits are displayed.
The CVV code is not stored in the database. Storing of the CVV code can be a custom.
Added ability to update the credit card information in program CMCM, Customer Credit Maintenance, from the Payflow Pro Response screen.
When payments are saved or when the [Payflow Pro] button is pressed, credit card payments will be automatically calculated, including surcharges and payment amounts.
If you enter the phone number and press the new [Return Customer] 
button, the customer associated with the phone number is returned to the Customer field and the primary contact is entered in the Contact field. You can still access the list of values by pressing F9 instead of the button.
Added Lost Quote button. User can press shift-F3 from anywhere in the form to create a lost quote for the order being entered. Lost quotes are sales orders with the order status L - Lost. They can be viewed in program OEDI, Sales Order Detail Inquiry.
Lost quotes do not do the following:
Create ship to addresses.
Check for zero quantity order lines.
Add send to records to the customer records.
Have sales representatives assigned.
Require release authorization or letters of credit.
Allow counter sale processing.
Update the customer's toll free number.
Maintain contact information.
Save third party shipping accounts.
Modified functionality for the F1 Cancel button. Users can save the cancelled orders as a lost quote or simply clear the order. When canceling the sales order, there are three buttons - [Return], [Clear], and [Save as Lost Quote]. If the OEXP_AUTOSAVE_LOST_QUOTES parameter for the sales location is set to Y in program MURM, Initialization Parameter Maintenance, all cancelled sales orders will be saved as lost quotes. When canceling the sales order, there are only two buttons - [Return] and [Clear and Save as Lost Quote]
On the Customer Tab, added the Electronic Invoicing section, which contains four radio buttons. The setting of these radio buttons determines how the customer will receive invoices. The text is displayed in red if the customer needs to be asked how they would like to receive invoices.
Whether or not the customer receives invoices electronically is determined by the ARINVOICE document type on the customer's Mail/Fax tab in program CMMM, Customer Master Maintenance.
If no ARINVOICE document type exists, or if the date last activity for the record is blank, the text here is displayed in red to indicate to the user that the customer needs to be asked how they would like to receive invoices.
The radio buttons include the following choices:
Email: The Send Type pop-list for the ARINVOICE document type for this customer is set to eMail.
Fax: The Send Type pop-list for the ARINVOICE document type for this customer is set to Fax.
Mail: The Send Type pop-list for the ARINVOICE document type for this customer is set to Printed.
Unsure: The Send Type pop-list for the ARINVOICE document type for this customer is set to Printed, and the Person's Name field is set to Unsure.
New Update Shipto Shipvia flag. When this flag is set to on, and the Ship Via code is changed, the ship via code for the ship to address in program CMMM, Customer Master Maintenance, will be changed to the one entered for the order.
Added Sales Representative maintenance for the order.
If the OEXP_VALIDATE_CONTACT parameter is set to Y in program MURM, Initialization Parameter Maintenance, 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.
If the OEXP_LOST_QUOTE_REASON parameter is set to Y in program MURM, Initialization Parameter Maintenance, and a quote is saved as a lost quote from program OEXP, Fast Order Entry, the user is alerted to enter a reason. Reason codes for lost quotes are set up in program CMRC, Complaint Reason Codes Maintenance and are stored in the quote header.
When the OEXP_ROLLOUT_MODE parameter is set to Y in program MURM, Initialization Parameter Maintenance, the message field will read '*** ROLLOUT Mode ***' when you enter the form. When in rollout mode, orders and quotes will be created using the template customer instead of creating a new customer. This allows sales orders and quotes to be shipped to people without setting them up as separate customers.
The extended price is displayed in purple when a customer/item surcharge has been added to it.
Order level discounts are applied to the sales order line according to the OE_QUICK_PRICE parameter in program MURM, Initialization Parameter Maintenance. 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. Order level discounts are always calculated when the commit is forced with the [Commit] button on the item tab.
Comments displayed here are sorted according to the OE_COMMENT_SORT parameter in program MURM, Initialization Parameter Maintenance.
New report listing sales order lines for which the allocation protection will expire soon. For more information, see the Protected Allocations for Background Batch Shipping feature.
Added ability to batch transmit sales quotations in the background using program JOBQ, NDS Job Queue Management, Windows Scheduler, or another job scheduler such as Cron. For more information, see the program documentation.
Added the B/O Ship Complete flag to the Order Codes screen. When the B/O Ship Complete flag is set to on for a sales order, the backorder for the sales order will have the Ship Complete flag set to on automatically when it is generated during sales order processing with program OESJ, Sales Order End of Day and Journals. The default value for this flag comes from the Make BO Ship Complete flag for the sales location record in program ARLM, Location Maintenance.
Added functionality for new fields in program ARLM, Location Maintenance. Added display of the discounts on the sales order line. Added Eff Disc % field to the sales order line. Added new Pricing Tab to Other Details popup screen.
If an item is entered for which the Shippable from plant XX flag is set to off for the plant on the sales order line, a warning will be displayed.
For customers with the Revenue Pricing method, if the OE_QUICK_PRICE parameter in program MURM, Initialization Parameter Maintenance, is set to Y, then pricing will not occur until the sales quotation is converted to an order, or until the user navigates to the Summary screen.
The order in which sales orders will be listed in this program is determined by the OE_DEFAULT_SORT parameter in program MURM, Initialization Parameter Maintenance.
On the Item Search screen, inactive and discontinued items are displayed as grayed out, but they can still be selected, if desired.
Modified the Substitutes screen to include the unit and plant fields for which the substitute item is valid.
Changes to Credit Card Handling:
After credit cards are authorized, the credit card number is hidden, and only the last four digits are displayed.
The CVV code is not stored in the database. Storing of the CVV code can be a custom.
Added ability to update the credit card information in program CMCM, Customer Credit Maintenance, from the Payflow Pro Response screen.
Credit cards cannot be maintained for prospects who are not also customers.
When payments are saved or when the [Payflow Pro] button is pressed, credit card payments will be automatically calculated, including surcharges and payment amounts.
On the Order Tracking screen, added the Show Only Track Code pop-list. To view a single tracking code, select the tracking code that you wish to view. The records will be re-queried with only the records for that tracking code displayed. To view all tracking codes, select All in the pop-list.
When the OQEM_DROP_SHIP_PO parameter is set to Y in program MURM, Initialization Parameter Maintenance, Create PO flag will be set to on automatically for drop ship items.
The extended price is displayed in purple when a customer/item surcharge has been added to it.
Fax/Email Overrides
Multiple email addresses can now be entered in the Copy To field, separated by commas ( , ) or semi-colons ( ; ).
Minimum Order Value for Sales Orders
The minimum order value for sales orders can be set up by location and by customer. To set up the minimum order value for the location, go to program ARLM, Location Maintenance. To set up the minimum order value for a customer, go to program CMMM, Customer Master Maintenance.
If the gross order value of the sales order is equal to or less than the amount entered for the location or customer, the miscellaneous code assigned will be applied to the sales order. The minimum order value for the customer overrides the minimum order value for the location, if the value for the customer is greater than zero.
Ship Complete Only
Added a B/O Ship Complete flag in the sales order entry programs. The default setting for this flag comes from the Make BO Ship Complete flag setting for the sales location record in program ARLM, Location Maintenance, but it can be overridden at the sales order level.
When the B/O Ship Complete flag is set to on for a sales order, the backorder for the sales order will have the Ship Complete flag set to on automatically when it is generated during sales order processing with program OESJ, Sales Order End of Day and Journals.
Ship To Code Updates
If the OE_ALLOW_SHIPTO_CREATE parameter in program MURM, Initialization Parameter Maintenance, is set to N, then new ship to codes cannot be created in program ARIE, One-Step Invoice Entry, program OQEM, Sales Order Quotation Entry/Maintenance, and program OEOE, Sales Order Entry/Maintenance.
Removed obsolete Commiss GL A/C field and Expense GL A/C field.
Removed Third Party Account Restriction for Customers parameter RESTRICT_CMMM_THP_ACCTS in program MURM, Initialization Parameter Maintenance. Entry of third party accounts in program CMMM, Customer Master Maintenance, no longer requires a duplicate entry in program VESM, Third Party Vendor Maintenance.
Vendor shipping accounts entered in program VESM, Third Party Vendor Maintenance, are no longer tied to the shipping accounts entered in program CMMM, Customer Master Maintenance for customers. Modified the program so that it can be used to allow vendors other than shipping vendors to have third party accounts that can be used when returning products to vendors using program RTVM, Return to Vendor Maintenance.
For more information on how Third Party Shipping Accounts for Shipping Interfaces works, see the feature documentation.
You can set up VeriSign™ 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. VeriSign™ 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_LOC parameter indicates whether the PP indicates plant code or sales location.
CC_BY_SALES_LOC: Y or N. Determines whether or not the parameters in program MURM, Initialization Parameter Maintenance, are organized by plant code or sales location. 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.
VisaNet™ Payment Processing
NDS Applications no longer supports some areas of VisaNetTM Payment Processing. Contact your NDS project manager about current support levels for this feature.
New parameters added:
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.