Codeunit 5285 "Audit Data Check SAF-T"

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

Properties

Procedures

• CheckDataToExport(var AuditFileExportHeader: Record "Audit File Export Header"): enum "Audit Data Check status"
• CheckAuditDocReadyToExport(var AuditFileExportHeader: Record "Audit File Export Header"): enum "Audit Data Check Status"
• TestRequiredFields(var RecRef: RecordRef): enum "Audit Data Check status"

Plus 1 local procedures.

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 5286 “Data Check Mgt. SAF-T” (9 calls: CheckAuditDocReadyToExport → VerifyDimensionsHaveAnalysisCode, CheckAuditDocReadyToExport → VerifySourceCodesHasSAFTCodes, CheckDataToExport → (object), …)
• Codeunit 28 “Error Message Management” (2 calls: CheckAuditDocReadyToExport → GetLastErrorID, CheckAuditDocReadyToExport → LogErrorMessage)
• Codeunit 5260 “Audit Mapping Helper” (1 call: CheckAuditDocReadyToExport → VerifyMappingIsDone)

Implements

• Interface “Audit File Export Data Check”

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: "Audit Data Check SAF-T"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.