codeunitIntegration & APIsofficial - Microsoftderived - from the source, no model text

Codeunit 6536 "E-Doc. Payment Occurrence Mgt."

EDocument · Microsoft.eServices.EDocument.Processing.Message

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 1 connected objects and pages

Table 472 "Job Queue Entry" (relates to)Job Queue 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.

EDocument · Microsoft.eServices.EDocument.Processing.Message · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Access Public
TableNo Job Queue Entry
Permissions tabledata “Cust. Ledger Entry” = r, tabledata “Detailed Cust. Ledg. Entry” = r, tabledata “E-Document” = r, tabledata “E-Doc. Payment Occurrence” = rim, tabledata “Sales Invoice Header” = r

Events published

  • OnAfterCreatePaymentOccurrence(var EDocPaymentOccurrence: Record "E-Doc. Payment Occurrence") (integration): Notifies localization and format apps after a payment occurrence has been persisted.

Event subscriptions

  • OnAfterInsertDtldCustLedgEntry subscribes to Codeunit “Gen. Jnl.-Post Line” OnAfterInsertDtldCustLedgEntry
  • OnAfterInsertDtldCustLedgEntryUnapply subscribes to Codeunit “Gen. Jnl.-Post Line” OnAfterInsertDtldCustLedgEntryUnapply

Procedures

  • ProcessApplication(DetailedCustLedgEntry: Record "Detailed Cust. Ledg. Entry"): Captures an invoice payment application for every matching outgoing E-Document.
  • ProcessUnapplication(OldDetailedCustLedgEntry: Record "Detailed Cust. Ledg. Entry"; NewDetailedCustLedgEntry: Record "Detailed Cust. Ledg. Entry"): Captures the reversal of each payment occurrence created from the original application entry.
  • ProcessPaymentOccurrence(var EDocPaymentOccurrence: Record "E-Doc. Payment Occurrence") (internal)
  • NotifyPaymentOccurrence(var EDocPaymentOccurrence: Record "E-Doc. Payment Occurrence") (internal)

Plus 4 local procedures.

Triggers

OnRun

Relations

Recent changes

Ask your agent

Procedure bodies are not stored here (D10). 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: "E-Doc. Payment Occurrence Mgt."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources