codeunitHuman Resourcesofficial - Microsoftderived - from the source, no model text

Codeunit 114 "Empl. Entry-Edit"

Base Application · Microsoft.HumanResources.Payables

Across versions

  1. BC23-30present

Neighbourhood 9 connected objects and pages

Table 5222 "Employee Ledger Entry" (relates to)Employee Ledger EntryPage 234 "Apply Employee Entries" (calls, 3 links)Apply Employee EntriesCodeunit 370 "Bank Acc. Reconciliation Post" (calls, 2 links)Bank Acc. Reconciliation PostTable 81 "Gen. Journal Line" (calls, 2 links)Gen. Journal LineCodeunit 1255 "Match Bank Payments" (calls)Codeunit 224 "EmplEntry-Apply Posted Entries" (calls)EmplEntry-Apply Posted EntriesPage 1191 "Create Employee Payment" (calls)Create Employee PaymentReport 394 "Suggest Employee Payments" (calls)Suggest Employee PaymentsTable 1294 "Applied Payment Entry" (calls)Applied Payment Entry

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

Base Application · Microsoft.HumanResources.Payables · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
TableNo Employee Ledger Entry
Permissions TableData “Employee Ledger Entry” = rm, TableData “Detailed Employee Ledger Entry” = rm

Events published

  • OnBeforeEmplLedgEntryModify(var EmplLedgEntry: Record "Employee Ledger Entry"; FromEmplLedgEntry: Record "Employee Ledger Entry") (integration)

Triggers

OnRun

Relations

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.

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-Edit"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources