Codeunit 211 "Res. Jnl.-Check Line"
Base Application · Microsoft.Projects.Resources.Journal
Across versions
- BC23-30present
Neighbourhood 7 connected objects and pages
Base Application · Microsoft.Projects.Resources.Journal · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| TableNo | Res. Journal Line |
Events published
OnAfterRunCheck(var ResJournalLine: Record "Res. Journal Line")(integration)OnBeforeCheckDimensions(var ResJournalLine: Record "Res. Journal Line"; var IsHandled: Boolean)(integration)OnBeforeRunCheck(var ResJournalLine: Record "Res. Journal Line"; var IsHandled: Boolean)(integration)OnCheckPostingDateOnBeforeCheckAllowedPostingDate(PostingDate: Date; var IsHandled: Boolean)(integration)OnCheckDimensionsOnAfterAssignDimTableIDs(var ResJnlLine: Record "Res. Journal Line"; var TableID: array[10] of Integer; var No: array[10] of Code[20])(integration)
Procedures
RunCheck(var ResJnlLine: Record "Res. Journal Line")
Plus 2 local procedures.
Triggers
OnRun
Relations
- runs on Table 207 “Res. 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 408 “DimensionManagement” (4 calls:
CheckDimensions → CheckDimIDComb,CheckDimensions → CheckDimValuePosting,CheckDimensions → GetDimCombErr, …) - Codeunit 5700 “User Setup Management” (1 call:
CheckPostingDate → CheckAllowedPostingDate) - Codeunit 950 “Time Sheet Management” (1 call:
RunCheck → CheckResJnlLine)
Called by
- Codeunit 212 “Res. Jnl.-Post Line” (1 call:
Code → RunCheck) - Codeunit 213 “Res. Jnl.-Post Batch” (1 call:
Code → RunCheck) - Codeunit 9075 “Check Res. Jnl. Line. Backgr.” (1 call:
RunResJnlCheckLineCodeunit → (object))
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: "codeunit", object_name: "Res. Jnl.-Check Line"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.