Events Setup

Events setup defines the rules for the operational activities users can record. Administrators should configure event types before operators start using the Events workspace.

This setup is shared. A domain such as Agriculture, Production, Inventory, or Assets narrows the business meaning of the event type, but it does not create a separate service-owned event engine.

Open Events -> Setup.

Workspace Reference

Workspace	Open From	Main Create Button	Main Record
Event Types	Events -> Setup -> Event Types	New Event Type	Reusable operational activity contract.
Document Transaction Types	Events -> Setup -> Document Transaction Types	New Document Transaction Type	Reusable structured document type for document workflows.

Event setup should be owned by administrators who understand the operational workflow and finance implications. A weak event type can make later events hard to price, approve, inspect, bill, or report.

Event Types

An event type describes the business activity being recorded. It controls how the event behaves in the UI and how it interacts with other parts of Pinkapple ERP.

Click New Event Type.

The event type list shows useful review columns such as code, name, domain, charge policy, GL rule, duration, billable status, item count, observation count, active status, and approval status.

Use New Event Type only when the organization needs a reusable event contract. Avoid creating duplicate event types for the same activity because that fragments reporting, billing, and workflow rules.

Event Type Form Sections

The event type form is split into sections. Complete them in order.

Event Type Details

Field	Required	Meaning
Code	Generated	Visible code used after the event type is saved. Users normally do not type it on create.
Name	Yes	User-facing name operators select when recording an event.
Domain	Yes	Business area where the event belongs, such as General, Production, Inventory, Assets, Loans, Driving, or Agriculture.
Default Duration	No	Expected event duration in minutes. Useful for planning, resource scheduling, or expectation setting.
Description	No	Explains when users should select this event type and what the activity means.

Use names that describe the real activity, such as Vehicle Inspection, Produce Intake Visit, Production Rework Request, or Training Follow-Up, rather than generic names like Service or Activity.

Capabilities

Capability switches decide which shared primitives the event can use.

Field	Meaning
Billable	Allows the event to carry charge behavior. When enabled, pricing and charge-accounting setup becomes important.
Consumes Items	Indicates that the event may consume stock or item quantities. Use this for activities that use materials or stock.
Produces Items	Indicates that the event may produce stock or output quantities. Use this where event completion creates operational output.
Requires Resource	Indicates that the event needs a resource such as a person, vehicle, machine, room, workstation, or other capacity item.
Has Observations	Allows structured observations such as readings, measurements, notes, findings, or abnormal flags.
Active	Controls whether the event type is available for new activity.

Switch on only the behavior that the event really needs. Extra capabilities make the form heavier and can confuse users.

Charge Pricing Policy

This section appears when Billable is enabled.

Field	Required	Meaning
Default Pricing Profile	Required when no linked product/service is selected	Pricing setup used to calculate event charges.
Linked Product / Service	Required when no pricing profile is selected	Shared operational product or service used when pricing should resolve through product-level pricing.
Pricing Trigger Event	No	Specific pricing trigger to use. If blank, pricing can fall back to the event type code where setup supports it.

Use a pricing profile when pricing is driven by a reusable price list or rate model. Use a linked product/service when the event is essentially selling or charging for a known service item.

Event Charge Accounting

This section appears when Billable is enabled.

Field	Required	Meaning
Charge Posting Rule	Yes for billable event types	GL posting rule used when approved event charges are submitted for accounting.

The charge posting rule should be reviewed by finance. It controls how direct event charges resolve receivable, revenue, tax, and other configured accounting lines. It should not be used to override downstream inventory, payment, or settlement posting that belongs to those shared primitives.

Billable Events

When an event type is billable, users can capture charges against events of that type. The configured accounting behavior should be reviewed carefully because it determines how approved charges are recognized when downstream posting is performed.

Administrators should only enable billable behavior when the event represents a chargeable service or activity.

Important billable-event setup includes:

• pricing trigger or pricing line behavior;
• whether charges can be generated automatically;
• whether manual charges are allowed;
• charge posting rule;
• approval behavior before finance submission;
• whether the event should create or link to invoice activity after posting.

If the charge posting rule is missing, users may be able to capture event data but charges will be blocked from finance submission until setup is corrected.

Event Items, Resources, And Observations

Event types can define whether operators may add item lines, resource bookings, or observations.

Item lines should use execution-ready stock items and approved UOMs. Use them for stock-affecting event activity, consumed materials, delivered goods, or operational quantities where configured.

Resource lines connect the event to operational resources and capacity slots. Use them when the activity consumes people, machines, rooms, vehicles, or other scheduled capacity.

Observation lines capture measurements, readings, notes, reference ranges, abnormal flags, and other structured findings.

Document Transaction Types

Document transaction types define the business documents that may be created from or linked to events. These can represent operational forms, delivery records, service records, confirmations, internal documents, or other evidence.

Use them when an event needs a structured document trail rather than only notes and attachments. The linked document still follows shared document-type numbering, approval, and side-effect rules from the Document Transactions primitive.

Document transaction setup should define the domain, document family, expected lines, approval behavior, and whether the document can be used for downstream follow-up.

Inspection Linkage

Event types can be linked to inspection templates or inspection requirements. Use this when the event should trigger quality review, service checks, field verification, asset checks, or other structured evidence.

If the event belongs to Agriculture, that means Agriculture may originate the activity context while the shared Inspections primitive still owns the grading/checklist truth.

Do not make inspections mandatory unless operators can realistically complete them during the event workflow.

Setup Checklist

Before publishing event setup to users:

• Confirm each event type has a clear business purpose.
• Confirm billable event types have the correct charge and accounting behavior.
• Confirm item, observation, resource, document, and inspection behavior matches the real process.
• Confirm required approvals match internal controls.
• Confirm linked inspection or document requirements are practical for operators.
• Test one event from draft through completion, including charges and inspections where enabled, before enabling broad access.