Page 102 "Item Journal Templates"
Base Application · Microsoft.Inventory.Journal
Across versions
- BC23-30present
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.Inventory.Journal · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Item Journal Templates |
| SourceTable | Item Journal Template |
| PageType | List |
| UsageCategory | Lists |
| ApplicationArea | Basic, Suite |
Fields on this page
Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).
| Group | Control | Shows | ToolTip |
|---|---|---|---|
| Control1 | Name | Name | Specifies the name of the item journal you are creating. from the table field |
| Description | Description | Specifies a brief description of the item journal template you are creating. from the table field | |
| Type | Type | Specifies the type of transaction that will be used with this item journal template. from the table field | |
| Recurring | Recurring | Specifies whether the item journal template will be a recurring journal. from the table field | |
| No. Series | No. Series | Specifies the number series from which entry or record numbers are assigned to new entries or records. from the table field | |
| Posting No. Series | Posting No. Series | Specifies the number series code used to assign document numbers to ledger entries that are posted from journals using this template. from the table field | |
| Source Code | Source Code | Specifies the source code that specifies where the entry was created. from the table field | |
| Reason Code | Reason Code | Specifies the reason code, a supplementary source code that enables you to trace the entry. from the table field | |
| Increment Batch Name | Increment Batch Name | Specifies if batch names using this template are automatically incremented. Example: The posting following BATCH001 is automatically named BATCH002. from the table field | |
| Page ID | Page ID | Specifies the number of the page that is used to show the journal or worksheet that uses the template. from the table field | |
| Page Caption | Page Caption | Specifies the displayed name of the journal or worksheet that uses the template. from the table field | |
| Test Report ID | Test Report ID | Specifies the test report that is printed when you click Actions, point to Posting, and then click Test Report. from the table field | |
| Test Report Caption | Test Report Caption | Specifies the name of the test report that is printed when you print the item journal. from the table field | |
| Posting Report ID | Posting Report ID | Specifies the posting report that is printed when you click Post and Print. from the table field | |
| Posting Report Caption | Posting Report Caption | Specifies the name of the report that is printed when you print the item journal. from the table field | |
| Whse. Register Report ID | Whse. Register Report ID | Specifies the ID assigned to the Whse. Register Report. from the table field | |
| Whse. Register Report Caption | Whse. Register Report Caption | Specifies the name of the report that is printed when you print the item journal. from the table field | |
| Force Posting Report | Force Posting Report | Specifies whether a report is printed automatically when you post. from the table field |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Template | Batches | View or edit multiple journals for a specific template. You can use batches when you need multiple journals of a certain type. | Page 262 “Item Journal Batches” |
Relations
- source table Table 82 “Item Journal Template”
Documented on Microsoft Learn
Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).
Ask your agent
Procedure bodies are not stored here (D10). For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "page", object_name: "Item Journal Templates"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.