Page 201 "Job Journal"
Base Application · Microsoft.Projects.Project.Journal
Across versions
- BC23present
- BC24declaration changed
- BC25-26unchanged
- BC27declaration changed
- BC28-30unchanged
Neighbourhood 15 connected objects and pages
Base Application · Microsoft.Projects.Project.Journal · captioned “Project Journals” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Project Journals |
| 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 | 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 project. from the table field | |
| 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 | |
| Price Calculation Method | Price Calculation Method | Specifies the method that will be used for price calculation in the item journal line. from the table field | |
| Cost Calculation Method | Cost Calculation Method | Specifies the method that will be used for cost calculation in the item journal line. 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 | |
| Description 2 | Description 2 | Specifies information in addition to the description. from the table field | |
| Job Planning Line No. | Job Planning Line No. | Specifies the project planning line number that the usage should be linked to when the project journal is posted. You can only link to project planning lines that have the Apply Usage Link option enabled. 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 | |
| Location Code | Location Code | Specifies a location code for an item. from the table field | |
| Bin Code | Bin Code | Specifies the bin where the items are picked or put away. from the table field | |
| Work Type Code | Work Type Code | Specifies which work type the resource applies to. Prices are updated based on this entry. from the table field | |
| Currency Code | Currency Code | Specifies the project’s currency code that listed in the Currency Code field in the Project Card. You can only create a Project Journal using this currency code. from the table field | |
| 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 | |
| Remaining Qty. | Remaining Qty. | Specifies the quantity of the resource or item that remains to complete a project. The remaining quantity is calculated as the difference between Quantity and Qty. Posted. You can modify this field to indicate the quantity you want to remain on the project planning line after you post usage. 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 cost of one unit of the item or resource on the line. | |
| 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 | |
| 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. | |
| Line Amount | Line Amount | Specifies the amount that will be posted to the project ledger. from the table field | |
| Line Amount (LCY) | Line Amount (LCY) | Specifies the amount in the local currency that will be posted to the project ledger. | |
| Line Discount Amount | Line Discount Amount | Specifies the discount amount that is granted for the item on the line. from the table field | |
| Line Discount % | Line Discount % | Specifies the line discount percentage. | |
| Total Price | Total Price | Specifies the total price in the project currency on the journal line. from the table field | |
| 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 project journal line has of type Item and the usage of the item will be applied to an already-posted item ledger entry. If this is the case, enter the entry number that the usage will be applied to. | |
| 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 | |
| Country/Region Code | Country/Region Code | Specifies the country/region of the address. from the table field | |
| Transaction Type | Transaction Type | Specifies the type of transaction that the document represents, for the purpose of reporting to INTRASTAT. from the table field | |
| Transport Method | Transport Method | Specifies the transport method, for the purpose of reporting to INTRASTAT. from the table field | |
| Time Sheet No. | Time Sheet No. | Specifies the number of a time sheet. A number is assigned to each time sheet when it is created. You cannot edit the number. from the table field | |
| Time Sheet Line No. | Time Sheet Line No. | Specifies the line number for a time sheet. from the table field | |
| Time Sheet Date | Time Sheet Date | Specifies the date that a time sheet is created. 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 | |
| ShortcutDimCode3 | ShortcutDimCode[3] |
— | |
| ShortcutDimCode4 | ShortcutDimCode[4] |
— | |
| ShortcutDimCode5 | ShortcutDimCode[5] |
— | |
| ShortcutDimCode6 | ShortcutDimCode[6] |
— | |
| ShortcutDimCode7 | ShortcutDimCode[7] |
— | |
| ShortcutDimCode8 | ShortcutDimCode[8] |
— | |
| Number of Lines | NumberOfJournalRecords | NumberOfRecords |
Specifies the number of lines in the current journal batch. |
| Project Description | JobDescription | JobDescription |
Specifies a description of the project. |
| Account Name | Account Name | AccName |
Specifies the name of the customer or vendor that the project is related to. |
| FactBoxes | JournalErrorsFactBox | part Page 9127 “Job Journal Errors Factbox” | — |
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 | Renumber Document Numbers | Resort the numbers in the Document No. column to avoid posting errors because the document numbers are not in sequence. Entry applications and line groupings are preserved. | |
| 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 … | ||
| Item Availability by | Event | View how the actual and the projected available balance of an item will develop over time according to supply and demand events. | |
| Period | Show the projected quantity of the item over time according to time periods, such as day, week, or month. | ||
| Variant | View or edit the item’s variants. Instead of setting up each color of an item as a separate item, you can set up the various colors as variants of the item. | ||
| Unit of Measure | View the item’s availability by a unit of measure. | ||
| Location | View the actual and projected quantity of the item per location. | ||
| Lot | View the current and projected quantity of the item in each lot. | Page 520 “Item Availability by Lot No.” | |
| BOM Level | View availability figures for items on bills of materials that show how many units of a parent item you can make based on the availability of child items. | ||
| Functions | Suggest Lines from Time Sheets | Fill the journal with lines that exist in the time sheets. | |
| Posting | Reconcile | View what has been reconciled for the project. The window shows the quantity entered on the project journal lines, totaled by unit of measure and by work type. | |
| 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. | ||
| Page | Edit in Excel | Send the data in the journal to an Excel file for analysis or editing. | |
| Issues | Show Lines with Issues | View a list of journal lines that have issues before you post the journal. | |
| Show All Lines | View all journal lines, including lines with and without issues. |
Events published
OnAfterValidateShortcutDimCode(var JobJournalLine: Record "Job Journal Line"; var ShortcutDimCode: array[8] of Code[20]; DimIndex: Integer)(integration)OnBeforeOpenPage(var JobJournalLine: Record "Job Journal Line"; var CurrentJnlBatchName: Code[10])(integration)OnBeforeOpenJournal(var JobJournalLine: Record "Job Journal Line"; var JobJnlManagement: Codeunit JobJnlManagement; CurrentJnlBatchName: Code[10]; var IsHandled: Boolean)(integration)
Trigger event subscribers
- OnDeleteRecordEvent: Codeunit 9074 “Job Journal Errors Mgt.” OnDeleteRecordEventJobJournal
- OnInsertRecordEvent: Codeunit 9074 “Job Journal Errors Mgt.” OnInsertRecordEventJobJournal
- OnModifyRecordEvent: Codeunit 9074 “Job Journal Errors Mgt.” OnModifyRecordEventJobJournal
Procedures
5 local procedures, no public ones.
Triggers
OnAfterGetCurrRecord, OnAfterGetRecord, OnDeleteRecord, OnNewRecord, OnOpenPage
Relations
- source table Table 210 “Job Journal Line”
Extended by
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,OpenJournal → OpenJnl, …) - Codeunit 4030 “Client Type Management” (2 calls:
OnAfterGetCurrRecord → GetCurrentClientType,OnOpenPage → GetCurrentClientType) - Codeunit 99000844 “Job Jnl. Line-Reserve” (2 calls:
OnDeleteRecord → DeleteLine,OnDeleteRecord → DeleteLineConfirm) - Codeunit 1021 “Job Jnl.-Post” (1 call:
ShowPreview → Preview) - Codeunit 408 “DimensionManagement” (1 call:
SetDimensionsVisibility → UseShortcutDims) - Codeunit 6723 “Server Setting” (1 call:
OnOpenPage → GetIsSaasExcelAddinEnabled) - Codeunit 7001 “Price Calculation Mgt.” (1 call:
OnOpenPage → IsExtendedPriceCalculationEnabled) - Codeunit 9074 “Job Journal Errors Mgt.” (1 call:
SetControlAppearanceFromBatch → SetFullBatchCheck) - Codeunit 9079 “Background Error Handling Mgt.” (1 call:
SetControlAppearanceFromBatch → BackgroundValidationFeatureEnabled)
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: "Job Journal"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.