Introduction to Product Maintenance
Product Maintenance
The Product Maintenance helps you to maintain your system robust and make the transaction process smooth.
Why Product Maintenance is required?
Your system data grows for each and every transaction when you take the backup. For large number of transaction, the data stored becomes huge which consume your disk space and it affects your system performance.
Product Maintenance is integrated with RPOS6.5 that makes your product smooth by different product maintenance process. You can use product maintenance process like Archive Data to migrate existing data to new database with read-only permission. Product maintenance process like Data Purge helps you by deleting the unwanted data. You can get better experience of your item list when its reaches above 10,000 through the Cache LOV. To restore the default layout definition of table you can use ReIndex.
The performance of the product is maintain through option given below
- Archive Data - move existing data to new database but with read-only permissions. To get more detail on archive data click Archive Data
- Data Purge - complete Deletion of data. To get more detail on data purge click Data Purge
- Cache LOV - use Cache LOV screen to get a better experience of Product List screen. To get more detail on cache LOV click Cache LOV
- ReIndex - use to restore the default table layout definition from your existing table layout. To get more detail on re-index click ReIndex
Important Notes:
- Before starting any of the system performance enhancement,
- it is recommended to check all the hardware checklist. To refer the system requirement click System Requirements
- it is recommended that please take the backup of the server machine data.
- It is recommended that before starting the archive data process, check your data size and disk space where the data is stored. It is recommended that free space on disk should be twice of data size.
When to use Archive Data and Data Purge?
Problem: Consider a situation, a customer is using RPOS6.5 product from previous 8 year. He had huge transaction data and he is facing performance issue due to data load. He wants to maintain archival records of transaction data for previous 5 year without making any changes in previous 3 months data.
Solution: In above situation, it is recommended to the user to go with Split Archive Process excluding the starting three months. For the rest of remaining transaction, go with the permanent delete option that is Data Purge.
Related Articles
Product Delivery "On Hold"
What does "On Hold" mean? When an order is marked as "on hold," it means the progress has been temporarily paused. This can happen for various reasons, usually related to preparation or readiness issues on the customer's side or specific ...
Introduction to Supermarket POS system
What is Supermarket? A supermarket is a large retail store offering a wide variety of FMCG Products, Fruits & Vegetables, beverages, and household products, organized into sections. This kind of store is larger and has a wider selection than earlier ...
Do you know how to create a new Item Hierarchy level in RetailEasy?
What is Item Hierarchy Level? The Item Hierarchy Level is used in Categorizing the items for better understanding, accessibility, and navigation. This can also help you for the Online website or Mobile App category structural designing. What are the ...
Introduction to Restaurant - Touch POS
Touch POS The touch POS is a display device which allows the user to interact with a computer and performs task by touching/tapping areas on the screen. Benefits of the Touch POS: Easy to operate More Interactive and user friendly Quicker and faster ...
Do you know how to purchase deactivate a product or set of products in the Item master
Purpose If any business owner wants to stop the purchase of the selected items for any of the following reasons: The stock of those items has crossed the maximum limits. The item is not available in market currently etc. Then in this case you can use ...