Shipment List

Shipment List is used to maintain master data that becomes a reference for transactions, reports, filters, or other settings.

Used By

Administrator or module owner

master data

Code, Name

When users need to create, review, or update Shipment List.
When this data needs to be available as a choice in transactions, reports, filters, or settings.
When existing data needs correction because policies, accounts, prices, contacts, or operating rules have changed.

Make sure the user has access to this menu and the related reference data has already been prepared.
Check required fields first, especially codes, names, dates, accounts, customers, suppliers, products, divisions, or departments.
If the form uses active status, confirm the status before saving so the data appears in the correct selections.

Open Form General / Shipment List.
Create a new record, or select an existing record when the data needs to be corrected.
Fill in the required fields and complete supporting information that helps search, reporting, or transaction processing.
Review the code, name, status, accounts, grouping, and other references before saving.
Click Save. If the application shows a validation message, follow the message until the data is saved successfully.

Field	User Explanation	Status
Code `id`	Unique code used to identify Shipment List. Use a consistent pattern so users can search and sort the data easily.	Required
Name `name`	Name shown in selections, transactions, and reports. Use wording that is clear for daily users.	Required
Last Updated `updatetimestamp`	Audit timestamp filled in automatically by the application.	Optional
Description `description`	Additional explanation for users who need context when reviewing this record.	Optional
Created By `usercreate`	Audit information filled in automatically when the record is created.	Optional
Updated By `useredit`	Audit information filled in automatically when the record is updated.	Optional

Most master-data forms are used as references by other forms. Changes may affect future transactions and reports.
Audit fields are filled in automatically by the application and help support teams trace changes.

Active data can appear as a choice in transactions, reports, filters, or settings that use this reference.
Changes are normally used for new activity. Historical documents remain available for review.
If required data is incomplete or inconsistent, the application rejects the save and shows a validation message.

Data cannot be saved: complete required fields and read the validation message shown by the application.
Data does not appear in selection or search: check active status, access rights, filters, and the search keyword.
Duplicate code or name: use the existing record when it should be corrected, or use a different code for a new record.
Report values do not match: recheck reference data, accounts, dates, transaction status, and related filters.

The list below summarizes the fields available in this form. Field labels follow the English UI language file used by the application.

Field	User Explanation	Status
Code `id`	Unique code used to identify Shipment List. Use a consistent pattern so users can search and sort the data easily.	Required
Name `name`	Name shown in selections, transactions, and reports. Use wording that is clear for daily users.	Required
Last Updated `updatetimestamp`	Audit timestamp filled in automatically by the application.	Optional
Description `description`	Additional explanation for users who need context when reviewing this record.	Optional
Created By `usercreate`	Audit information filled in automatically when the record is created.	Optional
Updated By `useredit`	Audit information filled in automatically when the record is updated.	Optional