How to do Documentation about Oracle Apex Application form with report
Step 1: Navigation to Payment Details Report
● Log in to the Claim Wise
Application using valid user credentials.
●
Upon successful authentication, the system displays the Claims
Dashboard as the landing page.
●
Navigate to the left-side menu panel and locate the Expenses Module.
●
Click on the Expense Category Report option within the module.
●
The system redirects to the Expense Payment , where all existing
expense categories are displayed in a structured tabular format along with
their details.
Step 2:
Payment Details Report Overview
Available
Actions on the Report Page
● Edit Icon
Allows
users to modify existing expense category details.
● Search Bar
Enables
users to enter keywords to filter and locate specific categories.
● Go Button
Executes
the search based on the entered criteria.
● Actions Menu
Provides
additional options such as filtering, sorting, and downloading the report.
● Add Payment Button
Allows
users to add new payment.
Step
3: Creating a New Payment Details
Step 4: Mandatory Fields & Validations – Payment
Details
·
Vendor name must
have some value
·
Transaction
Number must have some value
Step 5: Successful Creation of Payment
Details
● After entering all required details in the Payment Details
Form, click on the Create button.
● The system validates all entered data and checks for
mandatory fields.
● If all validations are successfully passed, the system saves the
expense category record.
● The popup/modal window closes automatically after successful submission.
● The newly created expense category is displayed in the Payment
Details Report list.
● The entered values such as Category Name, Category Code, ERP Type, GL
Account, Limit Amount, and Active status are reflected in the report.
● The system also updates audit details such as Created/Updated
by user and timestamp
Step 6: Successful Adding all valid
information you can add multiple line data
·
It supports entering multiple lines of data in a
single operation, making data entry more efficient and flexible.
·
Users can input complete and accurate details,
ensuring that all records are properly stored and managed.
Step 7: Successful Adding all valid
information you can add additional Info
Step 8: Editing and Updating Expense Category
● From the Payment Header
Report page, click on the Edit icon corresponding to
the required category.
● The system opens the Payment
Detail Form in a popup/modal window with existing category details
pre-filled.
● Modify the required fields such as
Vendor Name, Business unit, Payment Mode, Total Account, Paid Amount.
● After making the necessary
changes, click on the Apply Changes button.
● The system validates the
updated data before saving.
● If all validations are successful,
the updated information is saved in the system.
● The popup/modal window closes
automatically after successful update.
● The updated category details are
reflected in Payment Header Report.
Step 9: Once create send for approval
Workflow
Overview:
The
Payment Approval Workflow (Payment Approval WF) is designed to automate
and streamline the process of reviewing and approving payment requests within
the system. It ensures that all submitted payment requests follow a structured
approval hierarchy, improving accuracy, accountability, and processing efficiency.
The
workflow begins when a payment request is submitted and moves through multiple
validation and approval stages. The system first checks the status of the
request, after which it is routed to the assigned approver. Based on the
approver’s decision, the workflow evaluates conditions such as whether the
request is approved and if the current approver is the final authority.
If
the request is approved and requires additional approvals, it is forwarded to
the next approver in the hierarchy. Once the final approval is completed, the
system updates the status accordingly. If the request is rejected or not
submitted properly, the workflow terminates with the appropriate status.
This
workflow ensures:
- Controlled
approval flow with defined decision points
- Clear tracking
of request status at each stage
- Reduction of
manual intervention and errors
- Improved
transparency and auditability of payment processes
Step 1: Create task Definition
·
Go to Share Component
·
Open task Definition under Workflow and Automation.
·
Create task Definition
·
Fill all information (Name, Static_id , Subject ,Priority and all
mandatory fields)
select
(select USER_NAME from XXEXP_APPROVALS where seq > nvl(LAST_SEQ,0) order by
seq
fetch
first 1 row only) user_name,(select SEQ from XXEXP_APPROVALS
where seq > nvl(LAST_SEQ,0) order by seq
fetch
first 1 row only) CUR_SEQ, e.*
FROM
TMEXP_PAYMENT_TBL e
where
ID = :P_TRX_ID
·
Add Participant
·
Add parameter
·
Add Action
·
Choose Approve or Reject action while create
·
Choose action Type (Execute code, Send Email, Send Push notification, Server-Side
geocoding)
·
Choose on Event from dropdown (Complete, Delegate Update Comment, Update
Priority. Update Parameter, Release, cancel, Request Information, Submit
Information, Before Expire Expire)
·
Add Query in code section
·
Repeat same step with rejection
Step2: Go I
Share Component: Workflow and Automation
·
Create Workflow
·
Create and configure workflow
Step 3: Start Workflow
·
Once User send request for approval from UI
·
The status on UI get change to submitted
·
Once Status get submitted workflow get start
Step
3: After start workflow it check status
·
If not submitted
·
Make condition false
·
Map activity to End
·
If Status is Submitted
·
Make condition True
·
Map Activity
Step
4: Add Human task
·
If Submitted
·
Make Condition True
·
Map the activity
·
Send Next approver
·
Make condition False
·
Map activity to approver
Step5:
isApproved
·
Check status of approval if it is No
Step
6: isFinalApprover
·
If yes make condition True
·
Otherwise send for next approver
make condition false
Step
7: Update Status
·
If Approved update Status
·
If Rejected update status
update TMEXP_PAYMENT_TBL e
set status='APPROVED',
STATUS_DATE=SYSDATE, APPROVED_DATE=SYSDATE, APPROVED_BY=:APP_USER
where
id=:P_TRX_ID;
Comments
Post a Comment