Page 289 "Recurring Job Jnl."
Base Application · Microsoft.Projects.Project.Journal
Across versions
- BC23present
- BC24declaration changed
- BC25-30unchanged
Neighbourhood 5 connected objects and pages
Base Application · Microsoft.Projects.Project.Journal · captioned “Recurring Project Journal” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Recurring Project Journal |
| SourceTable | Job Journal Line |
| PageType | Worksheet |
| UsageCategory | Tasks |
| ApplicationArea | Jobs |
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 |
|---|---|---|---|
| Content | Batch Name | CurrentJnlBatchName |
Specifies the name of the journal batch, a personalized journal layout, that the journal is based on. |
| Control1 | Recurring Method | Recurring Method | Specifies the recurring method. The recurring method determines what happens to the quantity on the journal line after posting. For example, if you use the same quantity each time you post the line, you can reuse the same quantity after posting. from the table field |
| Recurring Frequency | Recurring Frequency | Specifies a recurring frequency if you have indicated in the Recurring field in the project journal template that the journal is a recurring journal. from the table field | |
| Line Type | Line Type | Specifies the type of planning line to create when a project ledger entry is posted. If the field is empty, no planning lines are created. from the table field | |
| Posting Date | Posting Date | Specifies the posting date you want to assign to each journal line. For more information, see Entering Dates and Times. from the table field | |
| Document Date | Document Date | Specifies the date when the related document was created. from the table field | |
| Document No. | Document No. | Specifies a document number for the journal line. from the table field | |
| External Document No. | External Document No. | Specifies a document number that refers to the customer’s or vendor’s numbering system. from the table field | |
| Job No. | Job No. | Specifies the number of the related project. | |
| Job Task No. | Job Task No. | Specifies the number of the related project task. from the table field | |
| Type | Type | Specifies an account type for project usage to be posted in the project journal. You can choose from the following options: from the table field | |
| No. | No. | Specifies the number of the involved entry or record, according to the specified number series. from the table field | |
| Description | Description | Specifies the name of the resource, item, or general ledger account to which this entry applies. You can change the description. from the table field | |
| Gen. Bus. Posting Group | Gen. Bus. Posting Group | Specifies the vendor’s or customer’s trade type to link transactions made for this business partner with the appropriate general ledger account according to the general posting setup. from the table field | |
| Gen. Prod. Posting Group | Gen. Prod. Posting Group | Specifies the item’s product type to link transactions made for this item with the appropriate general ledger account according to the general posting setup. from the table field | |
| Variant Code | Variant Code | Specifies the variant of the item on the line. from the table field | |
| Shortcut Dimension 1 Code | Shortcut Dimension 1 Code | Specifies the code for Shortcut Dimension 1, which is one of two global dimension codes that you set up in the General Ledger Setup window. from the table field | |
| Shortcut Dimension 2 Code | Shortcut Dimension 2 Code | Specifies the code for Shortcut Dimension 2, which is one of two global dimension codes that you set up in the General Ledger Setup window. from the table field | |
| ShortcutDimCode[3] | ShortcutDimCode[3] |
— | |
| ShortcutDimCode[4] | ShortcutDimCode[4] |
— | |
| ShortcutDimCode[5] | ShortcutDimCode[5] |
— | |
| ShortcutDimCode[6] | ShortcutDimCode[6] |
— | |
| ShortcutDimCode[7] | ShortcutDimCode[7] |
— | |
| ShortcutDimCode[8] | ShortcutDimCode[8] |
— | |
| Location Code | Location Code | Specifies a location code for an item. from the table field | |
| Work Type Code | Work Type Code | Specifies which work type the resource applies to (when applicable). | |
| Unit of Measure Code | Unit of Measure Code | Specifies how each unit of the item or resource is measured, such as in pieces or hours. By default, the value in the Base Unit of Measure field on the item or resource card is inserted. from the table field | |
| Quantity | Quantity | Specifies the number of units of the project journal’s No. field, that is, either the resource, item, or G/L account number, that applies. If you later change the value in the No. field, the quantity does not change on the journal line. from the table field | |
| Direct Unit Cost (LCY) | Direct Unit Cost (LCY) | Specifies the cost, in the local currency, of one unit of the selected item or resource. | |
| Unit Cost | Unit Cost | Specifies the unit cost for the selected type and number on the journal line. The unit cost is in the project currency, derived from the Currency Code field on the project card. from the table field | |
| Unit Cost (LCY) | Unit Cost (LCY) | Specifies the cost, in LCY, of one unit of the item or resource on the line. | |
| Total Cost | Total Cost | Specifies the total cost for the journal line. The total cost is calculated based on the project currency, which comes from the Currency Code field on the Project card. from the table field | |
| Total Cost (LCY) | Total Cost (LCY) | Specifies the total cost for this journal line. The amount is in the local currency. | |
| Unit Price | Unit Price | Specifies the price of one unit of the item or resource. You can enter a price manually or have it entered according to the Price/Profit Calculation field on the related card. from the table field | |
| Line Amount | Line Amount | Specifies the amount that will be posted to the project ledger. from the table field | |
| Line Discount % | Line Discount % | Specifies the discount percentage that is granted for the item on the line. from the table field | |
| Line Discount Amount | Line Discount Amount | Specifies the discount amount that is granted for the item on the line. from the table field | |
| Total Price | Total Price | Specifies the total price in the project currency on the journal line. from the table field | |
| Unit Price (LCY) | Unit Price (LCY) | Specifies the price, in LCY, of one unit of the item or resource. You can enter a price manually or have it entered according to the Price/Profit Calculation field on the related card. | |
| Total Price (LCY) | Total Price (LCY) | Specifies the total price for the journal line. The amount is in the local currency. | |
| Applies-to Entry | Applies-to Entry | Specifies if the quantity on the journal line must be applied to an already-posted entry. In that case, enter the entry number that the quantity will be applied to. from the table field | |
| Applies-from Entry | Applies-from Entry | Specifies the number of the item ledger entry that the journal line costs have been applied from. This should be done when you reverse the usage of an item in a project and you want to return the item to inventory at the same cost as before it was used in the project. from the table field | |
| Expiration Date | Expiration Date | Specifies the last date on which the recurring journal will be posted if you have indicated in the Recurring field of the project journal template that the journal should be a recurring journal. from the table field | |
| Project Description | JobDescription | JobDescription |
— |
| Account Name | Account Name | AccName |
Specifies the name of the related G/L account. |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Line | Dimensions | View or edit dimensions, such as area, project, or department, that you can assign to sales and purchase documents to distribute costs and analyze transaction history. | |
| Item Tracking Lines | View or edit serial, lot and package numbers that are assigned to the item on the document or journal line. | ||
| Project | Card | View or change detailed information about the record on the document or journal line. | Page 88 “Job Card” |
| Ledger Entries | View the history of transactions that have been posted for the selected record. | Page 92 “Job Ledger Entries” | |
| Functions | Calc. Remaining Usage | Calculate the remaining usage for the project. The batch job calculates, for each project task, the difference between scheduled usage of items, resources, and expenses and actual usage posted in project ledger entries. The remaining usage is then displayed in the project journal from where you can … | |
| Posting | Reconcile | View the balances on bank accounts that are marked for reconciliation, usually liquid accounts. | |
| Test Report | View a test report so that you can find and correct any errors before you perform the actual posting of the journal or document. | ||
| Post | Finalize the document or journal by posting the amounts and quantities to the related accounts in your company books. | ||
| Preview Posting | Review the different types of entries that will be created when you post the document or journal. | ||
| Post and Print | Finalize and prepare to print the document or journal. The values and quantities are posted to the related accounts. A report request window where you can specify what to include on the print-out. |
Procedures
2 local procedures, no public ones.
Triggers
OnAfterGetCurrRecord, OnAfterGetRecord, OnNewRecord, OnOpenPage
Relations
- source table Table 210 “Job Journal Line”
Calls
From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.
- Codeunit 1020 “JobJnlManagement” (4 calls:
CurrentJnlBatchNameOnAfterVali → SetName,OnAfterGetCurrRecord → GetNames,OnOpenPage → OpenJnl, …) - Codeunit 1021 “Job Jnl.-Post” (1 call:
ShowPreview → Preview)
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). The call sections above are our own, per object, from the BC29 call graph. 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: "Recurring Job Jnl."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.