Codeunit 1395 "Cancel Issued Fin. Charge Memo"

Base Application · Microsoft.Sales.FinanceCharge · BC23-30 · source at ea08af5e · facts from BC29

Properties

Events published

• OnAfterInitGenJnlLine(var GenJournalLine: Record "Gen. Journal Line"; IssuedFinChargeMemoHeader: Record "Issued Fin. Charge Memo Header") (integration): Raised after a general journal line is initialized for posting the cancellation entry.
• OnAfterCancelIssuedFinChargeMemo(var IssuedFinChargeMemoHeader: Record "Issued Fin. Charge Memo Header") (integration): Raised after the issued finance charge memo cancellation completes successfully.
• OnBeforeCancelIssuedFinChargeMemo(var IssuedFinChargeMemoHeader: Record "Issued Fin. Charge Memo Header") (integration): Raised before the issued finance charge memo cancellation process begins.
• OnCheckAppliedFinChargeMemoCustLedgerEntryOnAfterCalcAmounts(var CustLedgerEntry: Record "Cust. Ledger Entry") + BC25 (integration): Raised after calculating amount fields on the customer ledger entry during applied entry check.

Procedures

• GetAppliedCustomerLedgerEntryNotificationId(): Guid: Gets the unique identifier for the applied customer ledger entry notification.
• GetErrorMessages(var TempErrorMessageResult: Record "Error Message" temporary): Boolean: Retrieves accumulated error messages from the cancellation process.
• SetParameters(NewUseSameDocumentNo: Boolean; NewUseSamePostingDate: Boolean; PostingDate: Date; NewSkipShowNotification: Boolean): Sets the parameters used when canceling an issued finance charge memo.
• SetGenJnlBatch(NewGenJnlBatch: Record "Gen. Journal Batch"): Sets the general journal batch to use when posting the cancellation entries.
• ShowCustomerLedgerEntry(Notification: Notification): Opens the Customer Ledger Entries page filtered to the entry specified in the notification.

Plus 14 local procedures.

Triggers

OnRun

Relations

• runs on Table 304 “Issued Fin. Charge Memo Header”

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” (2 calls: SetDimensions → AddDimSource, SetDimensions → GetRecDefaultDimID)
• Codeunit 12 “Gen. Jnl.-Post Line” (1 call: PostGenJnlLines → RunWithCheck)
• Codeunit 1511 “Notification Lifecycle Mgt.” (1 call: ShowAppliedCustomerLedgerEntryNotification → SendNotificationWithAdditionalContext)
• Page 25 “Customer Ledger Entries” (1 call: ShowCustomerLedgerEntry → (object))
• Page 456 “No. Series” (1 call: GetDocumentNoAndPostingDate → (object))

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: "Cancel Issued Fin. Charge Memo"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.