codeunitFinanceofficial - Microsoftderived - from the source, no model text

Codeunit 5286 "Data Check Mgt. SAF-T"

SAF-T · Microsoft.Finance.AuditFileExport

Across versions

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

Neighbourhood 6 connected objects and pages

Table 5265 "Audit File Export Header" (relates to)Audit File Export HeaderCodeunit 5285 "Audit Data Check SAF-T" (calls, 9 links)Audit Data Check SAF-TCodeunit 28 "Error Message Management" (calls, 4 links)Error Message ManagementCodeunit 29 "Error Message Handler" (calls, 2 links)Error Message HandlerCodeunit 10 "Type Helper" (calls)Type HelperCodeunit 5280 "SAF-T Data Mgt." (calls)SAF-T Data Mgt.

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.

SAF-T · Microsoft.Finance.AuditFileExport · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Access Internal
TableNo Audit File Export Header

Events published

  • OnCollectErrors(var ErrorMessageMgt: Codeunit "Error Message Management") (integration)

Procedures

  • ThrowNotificationIfCustomerDataMissed(Rec: Record Customer): Boolean
  • ThrowNotificationIfVendorDataMissed(Rec: Record Vendor): Boolean
  • ThrowNotificationIfCompanyInformationDataMissed(Rec: Record "Company Information"): Boolean
  • ThrowNotificationIfBankAccountDataMissed(Rec: Record "Bank Account"): Boolean
  • ThrowNotificationIfCustomerBankAccountDataMissed(Rec: Record "Customer Bank Account"): Boolean
  • ThrowNotificationIfVendorBankAccountDataMissed(Rec: Record "Vendor Bank Account"): Boolean
  • VerifySourceCodesHasSAFTCodes()
  • VerifyDimensionsHaveAnalysisCode()

Plus 28 local procedures.

Triggers

OnRun

Relations

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.

Called by

  • Codeunit 5285 “Audit Data Check SAF-T” (9 calls: CheckAuditDocReadyToExport → VerifyDimensionsHaveAnalysisCode, CheckAuditDocReadyToExport → VerifySourceCodesHasSAFTCodes, CheckDataToExport → (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: "Data Check Mgt. SAF-T"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources