Codeunit 5651 "Insurance Jnl.-Check Line"
Base Application · Microsoft.FixedAssets.Insurance
Across versions
- BC23-30present
Neighbourhood 4 connected objects and pages
Base Application · Microsoft.FixedAssets.Insurance · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| TableNo | Insurance Journal Line |
Events published
OnRunCheckOnBeforeCheckDimIDComb(var InsuranceJnlLine: Record "Insurance Journal Line")(integration)
Procedures
RunCheck(var InsuranceJnlLine: Record "Insurance Journal Line")
Triggers
OnRun
Relations
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:
RunCheck → CheckDimIDComb,RunCheck → CheckDimValuePosting,RunCheck → GetDimCombErr, …)
Called by
- Codeunit 5652 “Insurance Jnl.-Post Line” (1 call:
Code → RunCheck) - Codeunit 5653 “Insurance Jnl.-Post Batch” (1 call:
Code → RunCheck)
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: "Insurance Jnl.-Check Line"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.