Codeunit 6251 "Sust. Gen. Journal Subscriber"
Sustainability · Microsoft.Sustainability.Journal
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 3 connected objects and pages
Sustainability · Microsoft.Sustainability.Journal · BC29-30 · source at ea08af5e · facts from BC29
Event subscriptions
- OnAfterUpdateSalesPurchLCY subscribes to Table “Gen. Journal Line” OnAfterUpdateSalesPurchLCY
- OnAfterAccountNoOnValidateGetGLAccount subscribes to Table “Gen. Journal Line” OnAfterAccountNoOnValidateGetGLAccount
- OnAfterAccountNoOnValidateGetGLBalAccount subscribes to Table “Gen. Journal Line” OnAfterAccountNoOnValidateGetGLBalAccount
- OnAfterCleanLine subscribes to Table “Gen. Journal Line” OnAfterCleanLine
- OnAfterValidateEvent subscribes to Table “Gen. Journal Line” OnAfterValidateEvent (Job Quantity)
- OnAfterPostGenJnlLine subscribes to Codeunit “Gen. Jnl.-Post Line” OnCodeOnAfterStartOrContinuePosting
Procedures
3 local procedures, no public ones.
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 6212 “Sustainability Post Mgt” (3 calls:
PostSustainabilityLine → InsertLedgerEntry,PostSustainabilityLine → SetNextGLEntryNo,PostSustainabilityLine → SetSkipUpdateCarbonEmissionValue) - Codeunit 6283 “Sust. FA Journal Subscriber” (1 call:
PostSustainabilityLine → GetPostingSign) - Codeunit 6284 “Sust. FA Post Subscriber” (1 call:
PostSustainabilityLine → CheckSustainabilityFALine)
Recent changes
- 2026-09-01 #10613 [Master] - Slice 640775: [Sustainability] Reverse Sustainability part when reverse in GL Entries (main, BC30, feature)
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: "Sust. Gen. Journal Subscriber"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.