Report 317 "Vendor Pre-Payment Journal"

Base Application · Microsoft.Purchases.Reports · BC23-30 · source at ea08af5e · facts from BC29

Properties

Procedures

• CheckICPartner(var GenJnlLine: Record "Gen. Journal Line"; var AccName: Text[100])
• TestPostingType()
• CheckICDocument()

Plus 36 local procedures.

Triggers

OnPreReport

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” (5 calls: CheckGenJnlLineErrors → CheckDimIDComb, CheckGenJnlLineErrors → CheckDimValuePosting, CheckGenJnlLineErrors → GetDimCombErr, …)
• Codeunit 1312 “Vendor Mgt.” (1 call: CheckVend → SetFilterForExternalDocNo)
• Codeunit 366 “Exchange Acc. G/L Journal Line” (1 call: CheckGenJnlLineErrors → (object))
• Codeunit 5700 “User Setup Management” (1 call: CheckNonZeroPostingDate → TestAllowedPostingDate)

Documented on Microsoft Learn

• Accounts payables analytics
• Vendor Pre-Payment Journal (report)

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: "report", object_name: "Vendor Pre-Payment Journal"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.