Inquiry Regarding System Archive Configuration and Activation

Dear CSO Team,

We would like to inquire about the current status of the system archive functionality in our WMS. Based on our current understanding, it seems that this functionality may not be enabled yet. Could you please help us confirm its current status?

If it is not currently enabled, we would like to explore the possibility of activating it to help manage historical data and maintain system performance.

Could you please provide more information regarding the following points?

1. Current Status: Is the archive functionality currently enabled in our system? If not, is there any specific reason why it has not been activated?
2. Scope of Archiving: Which types of data or transactions can be archived, such as completed orders, shipment orders, wave plans, or other historical records?
3. Archiving Process: How does the archiving process work? Is it performed automatically based on a retention period, or does it require manual execution?
4. Configuration and Requirements: What configurations, prerequisites, or preparations are needed to enable this functionality?
5. System Impact: Would enabling the archive functionality help improve system performance or database efficiency? Are there any potential impacts or risks during activation?
6. Data Accessibility: Once data is archived, can users still access or retrieve it when needed for operational purposes, reporting, or auditing?
7. Implementation Plan: What are the recommended steps to activate this functionality, including any required downtime, estimated implementation timeline, and testing requirements?

We have also CC'd @Wibenson  and pak @Wiguno  for their awareness.

We would appreciate your recommendation on the best approach for enabling this functionality in our environment, including any considerations we should review before proceeding.

Thank you for your support. We look forward to your guidance.

1. Current Status: Is the archive functionality currently enabled in our system? If not, is there any specific reason why it has not been activated?

Yes. It was enabled in the PROD environment with default setting.

1. Scope of Archiving: Which types of data or transactions can be archived, such as completed orders, shipment orders, wave plans, or other historical records?

The target data for archiving consists of orders that have been completed or cancelled and have reached the configured retention period. Please refer to the screenshot below for details.

Basic Data: This refers to master data. The data will only be synchronized to the archive database and will not be archived or removed from the production database.

Inbound, Outbound, Inventory, and Other: These are the target categories for data archiving.

Example: DOC_ORDER_HEADER

Only records with `soStatus >= 90` will be eligible for archiving, provided they have also reached the configured retention period.

When a `DOC_ORDER_HEADER` record is archived, its associated detail records and related transaction logs will also be archived together to maintain data consistency.

1. Archiving Process: How does the archiving process work? Is it performed automatically based on a retention period, or does it require manual execution?

Archive Process is executing by timer.Called asDATA_TRANS

1. Configuration and Requirements: What configurations, prerequisites, or preparations are needed to enable this functionality?

The archive setup is already in PROD environment; there are no need preparation to enable this.

1. System Impact: Would enabling the archive functionality help improve system performance or database efficiency? Are there any potential impacts or risks during activation?

Yes, enabling the archiving functionality helps manage the growing data volume in the main database, which may improve system performance and database efficiency.

However, the archiving process consumes database resources and may temporarily affect system performance.

To minimize the impact on daily operations, recommend running the process during low-traffic periods and monitoring database performance to ensure data consistency and successful archiving.

1. Data Accessibility: Once data is archived, can users still access or retrieve it when needed for operational purposes, reporting, or auditing?

Yes. You will still able to retrieve the records thru WMS or database.

Example:

1. Implementation Plan: What are the recommended steps to activate this functionality, including any required downtime, estimated implementation timeline, and testing requirements?

The archive setup is already in PROD environment,