• Table of contents
• Wiki
  • Specification
  • Description
  • SCM
    • Batch
    • Web Service

Wiki¶

Specification¶

See Batch
See WebService

Description¶

RP 2023 - expiry on 31 Dec 2024
RP Jan - Jun 2024 - expiry on 31 Dec 2025 (period 1.5 years)
RP Jul - Dec 2024 - expiry on 30 Jun 2026 (period 1.5 years)
RP Jan - Jun 2025 - expiry on 31 Dec 2026 (period 1.5 years)

============================================================
    In the backend, we need to prepare 3 separate pieces of code for these changes because each condition is different:
        Starting from 1st Nov 2023, the current balance should be updated to December 31, 2024.

    On 4 Jan 2024, the balance for 2023 should be adjusted by subtracting the earnings and utilization for January 2024.
        The reason for updating only on January 4, 2024, is that POS sales data is imported daily, and in case of any late imports, we need to deduct the utilization and account for returns related to December 2023 sales that were imported in January 2024.

    The program will run by transaction for six months:
        RP from January to June 2024 will expire on December 31, 2025 (a period of 1.5 years).
        RP from July to December 2024 will expire on June 30, 2026 (a period of 1.5 years).
        RP from January to June 2025 will expire on December 31, 2026 (a period of 1.5 years).

SCM¶

Batch¶

Host: svn+ssh://192.168.2.66/svn/ecosway-batch
Path: /ecosway-batch/src-ecos
Class: ECpurgeRP , GenHKRPDaily
Tag: HEAD

Web Service¶

Host: svn+ssh://192.168.2.66/svn/OnlineControllerDaoService
Path: /OnlineControllerDaoService
Tag: HEAD