codeunitSales & Receivablesofficial - Microsoftderived - from the source, no model text

Codeunit 103 "Cust. Entry-Edit"

Base Application · Microsoft.Sales.Receivables

Across versions

  1. BC23present
  2. BC242 procedures added, 1 procedures changed
  3. BC25-26unchanged
  4. BC271 events added
  5. BC28-30unchanged

Neighbourhood 19 connected objects and pages

Table 21 "Cust. Ledger Entry" (relates to)Cust. Ledger EntryCodeunit 980 "Payment Registration Mgt." (calls, 3 links)Payment Registration Mgt.Page 232 "Apply Customer Entries" (calls, 3 links)Apply Customer EntriesTable 81 "Gen. Journal Line" (calls, 3 links)Gen. Journal LineCodeunit 1409 "Sales Inv. Header - Edit" (calls, 2 links)Sales Inv. Header - EditCodeunit 370 "Bank Acc. Reconciliation Post" (calls, 2 links)Bank Acc. Reconciliation PostPage 5939 "Serv. Apply Customer Entries" (calls, 2 links)Codeunit 108 "Net Cust/Vend Balances Mgt." (calls)Net Cust/Vend Balances Mgt.Codeunit 1208 "Pmt Export Mgt Cust Ledg Entry" (calls)Pmt Export Mgt Cust Ledg EntryCodeunit 1250 "Match General Journal Lines" (calls)Match General Journal LinesCodeunit 1255 "Match Bank Payments" (calls)Match Bank PaymentsCodeunit 1278 "Exp. User Feedback Gen. Jnl." (calls)Codeunit 1408 "Sales Credit Memo Hdr. - Edit" (calls)Sales Credit Memo Hdr. - EditCodeunit 20111 "AMC Bank Exp. CT Feedback" (calls)AMC Bank Exp. CT FeedbackCodeunit 226 "CustEntry-Apply Posted Entries" (calls)CustEntry-Apply Posted EntriesCodeunit 6620 "Copy Document Mgt." (calls)Copy Document Mgt.Page 25 "Customer Ledger Entries" (calls)Table 1294 "Applied Payment Entry" (calls)Table 21 "Cust. Ledger Entry" (calls)

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.Sales.Receivables · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
TableNo Cust. Ledger Entry
Permissions TableData “Cust. Ledger Entry” = m, TableData “Detailed Cust. Ledg. Entry” = m, tabledata “Sales Invoice Header” = m

Events published

  • OnBeforeCustLedgEntryModify(var CustLedgEntry: Record "Cust. Ledger Entry"; FromCustLedgEntry: Record "Cust. Ledger Entry") (integration): Raised before the customer ledger entry is modified.
  • OnBeforeOnRun(var CustLedgerEntryRec: Record "Cust. Ledger Entry"; var CustLedgerEntry: Record "Cust. Ledger Entry"; var DetailedCustLedgEntry: Record "Detailed Cust. Ledg. Entry"; var IsHandled: Boolean) (integration): Raised before the OnRun trigger executes to allow custom processing.
  • OnRunOnAfterCustLedgEntryModify(var CustLedgerEntryRec: Record "Cust. Ledger Entry"; var CustLedgerEntry: Record "Cust. Ledger Entry") (integration): Raised after the customer ledger entry has been modified.
  • OnAfterLogFieldChanged(CurrCustLedgerEntry: Record "Cust. Ledger Entry"; NewCustLedgerEntry: Record "Cust. Ledger Entry"; var Changed: Boolean) (integration): Raised after determining if fields have changed to allow additional change tracking.
  • OnBeforeUpdateSalesInvoiceHeader(var UpdateSalesInvoiceCustLedgerEntry: Record "Cust. Ledger Entry"; CalledFromSalesInvEdit: Boolean; var IsHandled: Boolean) + BC27 (integration): Raised before updating the sales invoice header with customer ledger entry changes.

Procedures

  • SetOnHold(var OnHoldCustLedgEntry: Record "Cust. Ledger Entry"; NewOnHold: Code[3]) Δ BC24: Sets the On Hold status of a customer ledger entry.
  • SetCalledFromSalesInvoice(CalledFromSalesInvEditSet: Boolean) + BC24: Sets a flag indicating whether the codeunit is called from a sales invoice edit operation.

Plus 2 local procedures.

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.

Recent changes

Countries that replace it

AU, IT, NZ

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

Evidence 1 sources