Codeunit 2674 "Alloc. Acc. Handle Doc. Post"
Base Application · Microsoft.Finance.AllocationAccount
Across versions
- BC23present
- BC241 procedures added
- BC25unchanged
- BC26declaration changed
- BC27-30unchanged
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.Finance.AllocationAccount · BC23-30 · source at ea08af5e · facts from BC29
Event subscriptions
- SalesBeforeValidateVATProdPostingGroup subscribes to Table “Sales Line” OnBeforeValidateVATProdPostingGroup
- SalesBeforeValidateVATProdPostingGroupTrigger subscribes to Table “Sales Line” OnBeforeValidateVATProdPostingGroupTrigger
- PurchaseBeforeValidateVATProdPostingGroup subscribes to Table “Purchase Line” OnBeforeValidateVATProdPostingGroup
- BeforeValidateVATProdPostingGroupTrigger subscribes to Table “Purchase Line” OnValidateVATProdPostingGroupOnAfterTestStatusOpen
- OnBeforeCreateDeferralSchedule subscribes to Codeunit “Deferral Utilities” OnBeforeCreateDeferralSchedule
Procedures
SetVATBusPostingGroupCode(NewVATBusPostingGroupCode: Code[20]): Sets the VAT business posting group code for document line processing.SetVATProdPostingGroupCode(NewVATProdPostingGroupCode: Code[20]): Sets the VAT product posting group code for document line processing.
Called by
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 2678 “Sales Alloc. Acc. Mgt.” (2 calls:
CreateSalesLine → SetVATBusPostingGroupCode,CreateSalesLine → SetVATProdPostingGroupCode) - Codeunit 2679 “Purchase Alloc. Acc. Mgt.” (2 calls:
CreatePurchaseLine → SetVATBusPostingGroupCode,CreatePurchaseLine → SetVATProdPostingGroupCode)
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: "Alloc. Acc. Handle Doc. Post"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.