Overview
Activity Management supports customer-facing activity planning, budget approval, activity application, execution follow-up, payment requests, and reimbursement requests.
Business Purpose
The module separates budget planning from activity execution. Teams first submit an activity budget application, then create an activity application against the approved budget. This keeps budget caps, approval status, used amount, and remaining amount visible throughout the activity lifecycle.
User Roles
| Role | Responsibility |
|---|---|
| Requester | Creates and updates activity requests. |
| Approver | Reviews activity information and approves or rejects requests. |
| Finance Reviewer | Reviews budget, expense, and reimbursement-related information. |
| Activity Owner | Coordinates execution and completion tasks. |
| Budget Owner | Owns the approved activity budget and budget availability. |
| Stakeholder | Participates in follow-up actions such as payment or reimbursement requests. |
| Administrator | Maintains configuration, permissions, and reference data. |
Process Flow
flowchart TD
A[Create Activity Budget Application]
B[Budget Approval]
C[Create Activity Application]
D[Activity Approval]
E[Execution]
F[Payment or Reimbursement]
A --> B
B --> C
C --> D
D --> E
E --> F
Main Menus
| Menu | Purpose |
|---|---|
| Activity Tags | Maintain activity classification tags and tag groups. |
| Strategic Imperative | Maintain strategic priorities by product. |
| Application Form (New Budget For Activity) | Create and submit activity budget applications. |
| Application Form (New Activities) | Create activity applications for C1, C2a, C2b, C3, or Others activities. |
| Market Fee Exceed Apply | Request approval when market fee usage exceeds the planned amount. |
Module Pages
Image Assets
Activity screenshots and exported images should be stored in docs/assets/activity/ and referenced from this section using relative paths, for example: