NSCTLMN5 Global Setup Change Quote to Order 6
Purge Posted Invoice
Application Overview
The purpose of this feature is to automate the purge process via Deferred Processing without losing the time window of history that you wish to keep. To make this possible, we allow you to define a time window for history to keep.
Run Instructions
Purge Posted Invoices Setup Screen
Field Entry Descriptions
1. Reserved for future use.
2. How Many Days To Keep When Purging Posted Invoices?
With the purpose of this feature being to automate the purge process via Deferred Processing without losing the time window of history that you wish to keep, we make it possible by allowing you to define a time window for history to keep. For Example:
a. Define the numbers of days to keep history when you purge, (90 Days).
b. Purge Process, (recurring daily, weekly, monthly, or quarterly) is set up for Deferred Processing with a purge cut-off date well set into the future, 12/31/30.
c. The process would normally purge all posted invoices through 12/31/30 but since we made the 90 “Days To Keep” a condition, it will keep all history for 90 days prior to the system date and purge everything else.
Future Price Screen
Application Overview
Future Price function is used to update the price, standard cost and user-amount fields in the item master file. By using this function, the user can enter a date when the item price, cost, and user-amount will become effective without immediately impacting the item file. On the effective date, the user can post the future price transactions and make them effective.
The future price function allows the user to enter future price transactions well in advance of the effective date. You can make the posting of future price a Deferred Processing procedure, recurring on a daily basis, to further automate this process. This way you do not have to manually post Future Price transactions on, (or if you forget), after the effective date.
The Future Price function does not update price codes. If you are using the price code function with discount and markup methods, the future price function will be a useful tool to you. However, if you use price codes with a set price then the Future Price function may not be as valuable to you.
Future price is a very helpful function if the user has thousands of items to update in a short period of time. For example; if new pricing will be effective for 5,000 items at the beginning of a new year, there is simply not enough time to make all the changes in just a few days with the traditional method. You cannot make changes to the item file well in advance because any changes immediately update the item price and cost. This is why user may need to use this Future Price function.
If you can use the “Mass Price Change” function to update your price by a fixed percentage, then you do not need to use the Future Price function. If you only have less than a few hundred items’ price to update, you may not need to use the future price function since you can probably take care of the changes in a day, or maybe even a few hours.
Run Instructions
Setup of Future Price
Before using this function, you must define and enable your default parameters in the setup process. To do this, go to: Main Menu -> Util Setup -> Global setup à Cop-Func -> Future Price. The following screen will appear:
Future Price Screen Setup
Entry Field Description
NAME | DESCRIPTION |
1. Maintain Primary Cost of Both? | Elliott maintains both FOB and Landed Cost, and these are your Primary and Secondary Costs. Whichever is the Primary or Secondary cost is dependent upon how you have setup the Landed Cost function. For these costs you have an Average Cost, Last Cost, and Standard Cost. This enhancement will only update the Standard cost. Select “P” for Primary, Select “B” for Both, or “N” for None if you do not need to maintain future standard costs. |
2. Maintain Item Price? | Select “Y” to maintain the future price. On the specified date, the new price becomes effective after posting. |
3. Maintain Item User Amount? | The Item User Amount is a user definable field. If you need to update this field on a future date, select “Y” to include this field for maintenance in the future price function. Refer to the System Manager Manual on how to use Item User Amount. |
4. Default Import File Path/Name |
|
5. Does Import file With Header row |
|