Transaction Log

When to Use This Form

• When there is a Transaction Log activity that needs to be officially recorded in the application.
• When transaction data needs to become the basis for reports, audits, and follow-up processes.
• When the user needs to make sure the amounts, dates, related parties, and transaction details are saved correctly.

Before You Start

• Make sure reference data such as User Code and From Transaction has been created and is still active.
• Prepare supporting documents such as receipts, orders, proof of payment, or internal memos before entry.

Workflow

1. Open Settings / Maintenance / Transaction Log.
2. Fill in the date, transaction number, division, department, or related party if those fields are available.
3. Complete the transaction details. Check the quantities, prices, amounts, tax, discounts, accounts, or products according to the form.
4. Check the amount summary and transaction status before saving.
5. Click Save, then read the validation message if the application rejects the data.

Key Fields

Details and Relations

• This form has no detail table. The data is saved directly from the main fields.

What Happens After Saving

• The transaction data is saved as the basis for reports and audits.
• If any data is not valid, the application rejects the save and shows a validation message.

Common Problems

• Data cannot be saved: check the required fields, number and date formats, and the validation message shown.
• Data does not appear when searched: check the active status, user access rights, division/department filters, and the search keyword.
• Total or status is wrong: re-check the line details, discounts, tax, payment, and transaction references.

Available Fields

The following list summarizes the fields available on the form. Rarely used fields are still listed so they are easy to look up during training or support.

User Checklist

Menu Location

• Settings / Maintenance / Transaction Log
  /form/logtransactions