> For the complete documentation index, see [llms.txt](https://docs.dynalogic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/stamp-events-6182629.md).

# Stamp Events

This table contains all the *actions* which registrations in [Stamp Journal Line](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/stamp-journal-lines-6182623.md) has resulted in.

Every time a new registration is made, or reporting qty/status, there will be added a line in this table.

Item consumption, which are linked to a [Stamp Journal Line](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/stamp-journal-lines-6182623.md) will also add a line in this table (and later be posted).

Time consumption will also add a line in this table (and later be posted). Howefter, only when the registrations are [Approved](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/general/time-calculation-and-approval-6182701.md). This function must be activated under [setup](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/jobmanager-setup-6182300.md).

It is possible to [setup rounding](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/jobmanager-setup-6182300.md) for the Time consumption.

The hourly rate *can* be overridden per Employee when setting up [Pay Type for posting](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/jobmanager-employee-6182311.md#field-501).

Posting time consumption to **Production** can be limited with [Post time (Flusing Method=Forward)](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/jobmanager-setup-6182300.md#field-2013) and [Post time (Flusing Method=Backward)](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/jobmanager-setup-6182300.md#field-2014).

When posting time consumption to **Job** or **Service**, the resource associated with the NAV/BC *Employee* is used.

If the field *Usage Link* is used on *Job Planning Lines*, the resource from the Job Planning Line is used instead. The hourly rate *can* still be overridden per Employee when setting up [Pay Type for posting](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/jobmanager-employee-6182311.md#field-501).

Lines in this table may later be posted in the relevant NAV/BC modules - according to this [this field](#field-4).

Lines are [posted menually](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/general/stamp-events-6182629.md) or [automatically with Job Queue](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/post-to-nav-bc.md).

| Topic                                     |
| ----------------------------------------- |
| [Sequence](#field-1)                      |
| [Journal Reference](#field-2)             |
| [Timestamp](#field-3)                     |
| [Event](#field-4)                         |
| [Status](#field-8)                        |
| [Registration Source](#field-9)           |
| [Employee](#field-10)                     |
| [Job Id](#field-11)                       |
| [Job Type](#field-12)                     |
| [Stamp Type](#field-13)                   |
| [Work Type](#field-17)                    |
| [Ref. Type](#field-21)                    |
| [Ref. Number](#field-22)                  |
| [Sub. Ref. Number](#field-23)             |
| [Profile date](#field-24)                 |
| [Posting Counter](#field-89)              |
| [Error timestamp](#field-90)              |
| [Posted method](#field-91)                |
| [Posted by](#field-92)                    |
| [Posted timestamp](#field-93)             |
| [Posted Document No.](#field-97)          |
| [Cancel Document No.](#field-98)          |
| [Stop-code](#field-201)                   |
| [Good Qty](#field-202)                    |
| [Scrap Qty](#field-203)                   |
| [Actual Time Comsump](#field-204)         |
| [Scrap Code](#field-205)                  |
| [Serial No. (output)](#field-221)         |
| [Lot No. (output)](#field-222)            |
| [Location Code (output)](#field-231)      |
| [Bin Code (output)](#field-232)           |
| [Item No. (consumption)](#field-301)      |
| [Consump now](#field-302)                 |
| [Reason Code](#field-303)                 |
| [Back](#field-304)                        |
| [Expected Quantity](#field-305)           |
| [Consumped Qty](#field-306)               |
| [Variant Code (consumption)](#field-310)  |
| [Serial No. (consumption)](#field-321)    |
| [Lot No. (consumption)](#field-322)       |
| [Location Code (consumption)](#field-331) |
| [Bin Code (consumption)](#field-332)      |

## See also

[Stamp Events](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/general/stamp-events-6182629.md)\
[Post to NAV/BC](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/post-to-nav-bc.md)

## Reference

\
\\

<details>

<summary>Sequence</summary>

Unique system number which can be used to identify this [Stamp Event](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/stamp-events-6182629.md).

The number is written to **External Document No.** when posting in the NAV standard modules. The number have prefix *Event-* (Applies to **Production** and **Job**).

Also read [this](#field-4).

</details>

<details>

<summary>Journal Reference</summary>

Reference to the [Stamp Journal Line](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/stamp-journal-lines-6182623.md#field-6).

**Related topics**

* [Stamp Journal Lines](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/stamp-journal-lines-6182623.md)

</details>

<details>

<summary>Timestamp</summary>

Time of creation of the line.

</details>

<details>

<summary>Event</summary>

| Event              | Posting in NAV                                              |
| ------------------ | ----------------------------------------------------------- |
| Stamp              | No posting. Indicates that it is a log of the registration. |
| Output Journal     | Posting through Output Journal.                             |
| Production Journal | Posting through Production Journal.                         |
| Job Journal        | Posting through Job Journal                                 |
| Service Line       | Posting direct as Service Line.                             |

Lines are [posted menually](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/general/stamp-events-6182629.md) or [automatically with Job Queue](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/post-to-nav-bc.md).

Postings can be traced back from NAV to JobManager:

* They will have reference to the original *Stamp Journal*. [See how](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/stamp-journal-lines-6182623.md#field-6).
* If posted through **Journals** they will further have reference to the original *Stamp Event*. [See how](#field-1).

**Related topics**

* [Service Line](https://docs.microsoft.com/en-us/dynamics365/business-central/service-how-to-create-service-orders)

</details>

<details>

<summary>Status</summary>

Showing the *Status* for this line.

| Status    | Beskrivelse                                   |
| --------- | --------------------------------------------- |
| Error     | The line has errors and is awaiting action    |
| Queued    | The line is added to the Job Queue            |
| Waiting   | The line awaiting (manual or automatically)   |
| Skip      | Posting excluded (manually changed by a user) |
| OK        | The line is processed                         |
| Postponed | The line awaiting posting of *Assembly Order* |

</details>

<details>

<summary>Registration Source</summary>

The field log information about where the registration were made.

</details>

<details>

<summary>Employee</summary>

No. of the related Employee.

</details>

<details>

<summary>Job Id</summary>

The field is a unique id for the associated job. All jobs are created in [this table](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/jobmanager-job-6182601.md).

**Related topics**

* [Stamp Journal Lines](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/stamp-journal-lines-6182623.md)

</details>

<details>

<summary>Job Type</summary>

Specifies the Job Type for the Job.

| Option                   | [Ref. Type](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/jobmanager-job-6182601.md#field-3) | Value in database (a) |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- |
| Clock-in                 | IPC                                                                                                                                                     | 0                     |
| Clock-out                | IPC                                                                                                                                                     | 1                     |
| Break                    | IPC                                                                                                                                                     | 2                     |
| Trigger                  | IPC                                                                                                                                                     | 3                     |
| Team Start               | IPC                                                                                                                                                     | 4                     |
| Team Stop                | IPC                                                                                                                                                     | 5                     |
| IPO activity             | IPC                                                                                                                                                     | 6                     |
| Production Setup         | Production                                                                                                                                              | 7                     |
| Production Run           | Production                                                                                                                                              | 8                     |
| Production Wait          | Production                                                                                                                                              | 9                     |
| Production Move          | Production                                                                                                                                              | 10                    |
| Job Task                 | Job                                                                                                                                                     | 11                    |
| Service Line             | Service                                                                                                                                                 | 12                    |
| Assembly Line            | Assembly                                                                                                                                                | 13                    |
| Service Order Allocation | Service                                                                                                                                                 | 14                    |

1. This value is used if connection direct to the database - e.g. from Power BI.

**Related topics**

* [Stamp Journal Lines](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/stamp-journal-lines-6182623.md)

</details>

<details>

<summary>Stamp Type</summary>

Type of the related registration:

* Work
* Absence
* Break
* Trigger Code

**Related topics**

* [Stamp Journal Lines](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/stamp-journal-lines-6182623.md)

</details>

<details>

<summary>Work Type</summary>

*Work Type* can be entered when register time using [JobManager - Time Sheet](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/general/jobmanager-time-sheet-6182712.md) and [JobManager - Time Sheet (Week)](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/general/jobmanager-time-sheet-week-6182713.md), and is passed on to the [calculated lines](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/calculated-lines-6182625.md).

Calculation of pay counters, can then be limited to a certain *Work Type*.

Changing a registration from one Job Id to another, with different Work Type, now prompt to confirm overwrite with new value. This applies to "Registration approval" and "Time Calculation and Approval" pages. Before the system only overwrite if value was blank - else nothing overwritten.

For complex setup this [**filter** field](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/agreement-pay-counters-6182511.md#field-91) can be used instead.

</details>

<details>

<summary>Ref. Type</summary>

Specifies the module the Job refers to:

* **IPC** *(0)*
* **Production** *(1)*
* **Job** *(2)*
* **Service** *(3)*
* **Assembly Order** *(4)*

**Related topics**

* [Stamp Journal Lines](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/stamp-journal-lines-6182623.md)

</details>

<details>

<summary>Ref. Number</summary>

Indicates the related number depending on the field **Ref. Type**:

| Ref. Type  | Ref. Number                 |
| ---------- | --------------------------- |
| IPC        | No. of the IPC Category     |
| Production | No. of the Production Order |
| Job        | No. of the Job              |
| Service    | No. of the Service Order    |
| Assembly   | No. of the Assembly Order   |

**Related topics**

* [Stamp Journal Lines](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/stamp-journal-lines-6182623.md)

</details>

<details>

<summary>Sub. Ref. Number</summary>

Indicates the related number depending on the field **Ref. Type**:

| Ref. Type  | Sub. Ref. Number                      |
| ---------- | ------------------------------------- |
| IPC        | No. of the IPC Activity               |
| Production | Item No. of the Production Order Line |
| Job        | No. of the Job Planning Line          |
| Service    | Item No. of the Service Item          |
| Assembly   | Item No. of the Assembly Order        |

**Related topics**

* [Stamp Journal Lines](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/stamp-journal-lines-6182623.md)

</details>

<details>

<summary>Profile date</summary>

Specifies the date to which the line is attached.

</details>

<details>

<summary>Posting Counter</summary>

Shows the number of times this line has been attempted [posted](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/post-to-nav-bc.md).

See also [here](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/jobmanager-setup-6182300.md#field-1000).

</details>

<details>

<summary>Error timestamp</summary>

Shows the time of last attempted [posting](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/post-to-nav-bc.md).

See also [here](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/jobmanager-setup-6182300.md#field-1000).

</details>

<details>

<summary>Posted method</summary>

How is this line posted:

* **Job Queue** if posted on the NAS by the Job Queue.
* **User** if posted manually by a user in page with Stamp Events.
* **User (only journal)** if posted manually to *journal only* by a user.

</details>

<details>

<summary>Posted by</summary>

Indicates the User who has posted this line.

*Will also be set if a User selects **Skip**.*

</details>

<details>

<summary>Posted timestamp</summary>

Indicates the date and time when this line were posted.

*Will also be set if a User selects **Skip**.*

</details>

<details>

<summary>Posted Document No.</summary>

Show **Document No.** from the NAV posting.

**Related topics**

* [Post to NAV/BC](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/post-to-nav-bc.md)

</details>

<details>

<summary>Cancel Document No.</summary>

Show **Document No.** from a reversal of NAV posting.

**Related topics**

* [Post to NAV/BC](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/post-to-nav-bc.md)

</details>

<details>

<summary>Stop-code</summary>

Showing the new status/value, caused by a record in [this table](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/stamp-journal-lines-6182623.md). This status/value will later be posted in the relevant NAV module.

**Related topics**

* [Stamp Journal Lines](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/stamp-journal-lines-6182623.md)

</details>

<details>

<summary>Good Qty</summary>

Showing the new status/value, caused by a record in [this table](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/stamp-journal-lines-6182623.md). This status/value will later be posted in the relevant NAV module.

</details>

<details>

<summary>Scrap Qty</summary>

Showing the new status/value, caused by a record in [this table](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/stamp-journal-lines-6182623.md). This status/value will later be posted in the relevant NAV module.

</details>

<details>

<summary>Actual Time Comsump</summary>

Showing the new status/value, caused by a record in [this table](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/stamp-journal-lines-6182623.md). This status/value will later be posted in the relevant NAV module.

</details>

<details>

<summary>Scrap Code</summary>

Showing the new status/value, caused by a record in [this table](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/stamp-journal-lines-6182623.md). This status/value will later be posted in the relevant NAV module.

</details>

<details>

<summary>Serial No. (output)</summary>

Viser værdien af feltet **Varekladdelinje** i tabellen **Varekladdelinje**.

</details>

<details>

<summary>Lot No. (output)</summary>

Viser værdien af feltet **Varekladdelinje** i tabellen **Varekladdelinje**.

</details>

<details>

<summary>Location Code (output)</summary>

Viser værdien af feltet **Varekladdelinje** i tabellen **Varekladdelinje**.

</details>

<details>

<summary>Bin Code (output)</summary>

Viser værdien af feltet **Varekladdelinje** i tabellen **Varekladdelinje**.

</details>

<details>

<summary>Item No. (consumption)</summary>

Viser værdien af feltet **Varekladdelinje** i tabellen **Varekladdelinje**.

</details>

<details>

<summary>Consump now</summary>

Qty to be pulled from stock.

</details>

<details>

<summary>Reason Code</summary>

Viser værdien af feltet **Varekladdelinje** i tabellen **Varekladdelinje**.

</details>

<details>

<summary>Back</summary>

Qty that remains to be used

</details>

<details>

<summary>Expected Quantity</summary>

Qty expected to be used.

</details>

<details>

<summary>Consumped Qty</summary>

Qty already reported as used

</details>

<details>

<summary>Variant Code (consumption)</summary>

Viser værdien af feltet **Varekladdelinje** i tabellen **Varekladdelinje**.

</details>

<details>

<summary>Serial No. (consumption)</summary>

Viser værdien af feltet **Varekladdelinje** i tabellen **Varekladdelinje**.

</details>

<details>

<summary>Lot No. (consumption)</summary>

Viser værdien af feltet **Varekladdelinje** i tabellen **Varekladdelinje**.

</details>

<details>

<summary>Location Code (consumption)</summary>

Viser værdien af feltet **Varekladdelinje** i tabellen **Varekladdelinje**.

</details>

<details>

<summary>Bin Code (consumption)</summary>

Viser værdien af feltet **Varekladdelinje** i tabellen **Varekladdelinje**.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/stamp-events-6182629.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
