Codeunit 112 "Empl. Entry-SetAppl.ID"
Base Application · Microsoft.HumanResources.Payables
Across versions
- BC23-30present
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.HumanResources.Payables · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Permissions | TableData “Employee Ledger Entry” = rimd |
Events published
OnSetApplIdOnAfterEmplLedgEntryToUpdateModify(var EmplLedgerEntry: Record "Employee Ledger Entry"; var TempEmplLedgEntry: Record "Employee Ledger Entry" temporary; ApplyingEmplLedgEntry: Record "Employee Ledger Entry"; AppliesToID: Code[50])(integration)
Procedures
SetApplId(var EmplLedgEntry: Record "Employee Ledger Entry"; ApplyingEmplLedgEntry: Record "Employee Ledger Entry"; AppliesToID: Code[50])
Triggers
OnRun
Called by
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 367 “CheckManagement” (1 call:
ClearApplnEmployeeLedgerEntries → SetApplId) - Page 234 “Apply Employee Entries” (1 call:
SetEmplApplId → SetApplId) - Table 81 “Gen. Journal Line” (1 call:
ClearCustVendApplnEntry → SetApplId)
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: "Empl. Entry-SetAppl.ID"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.