Codeunit 960 "Posting Group Change"

Base Application · Microsoft.Finance.ReceivablesPayables · BC23-30 · source at ea08af5e · facts from BC29

Events published

• OnAfterChangePostingGroup(SourceRecordRef: RecordRef; NewPostingGroup: Code[20]; OldPostingGroup: Code[20]) + BC25 (integration): Integration event raised after changing posting group to allow custom processing.
  • subscribers: Codeunit 5959 “Serv. Posting Group Change” OnAfterChangePostingGroup

Procedures

• ChangePostingGroup(NewPostingGroup: Code[20]; OldPostingGroup: Code[20]; SourceRecordVar: Variant): Changes posting group with validation based on document type and substitute posting group setup.
• CheckCustomerPostingGroupSubstSetup(NewPostingGroup: Code[20]; OldPostingGroup: Code[20]) Δ BC27
• CheckVendorPostingGroupSubstSetup(NewPostingGroup: Code[20]; OldPostingGroup: Code[20]): Checks vendor posting group substitute setup before allowing posting group change.
• CheckEmployeePostingGroupSubstSetup(NewPostingGroup: Code[20]; OldPostingGroup: Code[20]) + BC27: Checks employee posting group substitute setup before allowing posting group change.
• CheckAllowChangeSalesSetup(): Checks if sales and receivables setup allows multiple posting groups before changing customer posting groups.
• CheckAllowChangePurchaseSetup(): Checks if purchases and payables setup allows multiple posting groups before changing vendor posting groups.
• CheckAllowChangeHRSetup() + BC27: Checks if human resources setup allows multiple posting groups before changing employee posting groups.
• HasCustomerSamePostingGroup(NewPostingGroup: Code[20]; CustomerNo: Code[20]): Boolean: Checks if a customer already has the same posting group to avoid unnecessary validation.
• HasVendorSamePostingGroup(NewPostingGroup: Code[20]; VendorNo: Code[20]): Boolean: Checks if a vendor already has the same posting group to avoid unnecessary validation.
• HasEmployeeSamePostingGroup(NewPostingGroup: Code[20]; EmployeeNo: Code[20]): Boolean + BC27: Checks if an employee already has the same posting group to avoid unnecessary validation.

Plus 9 local procedures.

Implements

• Enum 960 “Posting Group Change Method”

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: "Posting Group Change"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.