[Master] - Sustainability: Specific Carbon Tracking, Item Charge emissions & setup fixes (Bugs 641051, 641486, 641487, 641049, 641222, 641055, 641289, 641224, 641309)

[v-rohangarg20]

PR description
Sustainability – Fixes for Specific Carbon Tracking, Item Charge emissions, value‑chain posting & setup

Fixes AB#641051, AB#641486, AB#641487, AB#641049, AB#641222, AB#641055, AB#641289, AB#641224, AB#641309

This PR groups related fixes around Specific carbon tracking, item‑charge emission posting, value‑chain (purchase/sales/service/undo) emission handling, and Sustainability Setup.

Bug 641051 – Item Charge CO2e not distributed across received/applied quantity

Issue: Posting a purchase Item Charge assigned the full "CO2e to Assign" to one item journal line; for charges applied to split item ledger entries emissions weren't spread proportionally.
Solution: Added split detection (GetDistributeItemCharge via SplitItemLedgerEntriesExist) and proportional allocation CO2e to Assign × ChargeQtyToPostBase / ItemChargeTotalQty, plus OnPostItemTrackingItemChargePerOrderOnAfterCalcFactor to split remaining CO2e per tracking specification. Also skips GetTotalCO2eAmount for purchase item‑charge value entries.

Bug 641486 – Wrong sign on Total CO2e when splitting from applied‑from entries

Issue: Emissions derived from an "Applies‑from Entry" (returns/negative adjustments) could post with the wrong sign.
Solution: Derived explicit Sign from Total CO2e and used Sign * Abs(CO2eAmount/CO2eQuantity) * Abs(Quantity); prorated the non‑split branch by quantity.

Bug 641487 – Missing/incorrect value entries for Undo Purchase Receipt & Service documents

Issue: Undo purchase receipt didn't reverse/recreate value entries; service documents didn't post emissions; service‑shipment positive adjustments wrongly inherited Correction.
Solution: Added undo subscribers (Undo Purchase Receipt Line, Undo Posting Management) recomputing emissions via UpdateSustainabilityItemJournalLine; added Sales/Service subscriber support; guarded the Correction assignment for Service Shipment positive adjustments.

Bug 641049 – No warning to enable Item Tracking when Carbon Tracking Method = Specific

Issue: Setting Specific was allowed with no serial/lot‑specific tracking and no feedback.
Solution: Added WarnIfSpecificCarbonTrackingLacksItemTracking, invoked from "Carbon Tracking Method" OnValidate and "Item Tracking Code" OnAfterValidate; shows a message when the tracking code is missing or not IsSpecific().

Bug 641222 – CO2e per Unit not visible/editable on Item Journal

Issue: Item Journal showed only "Total CO2e"; "CO2e per Unit" required Page Inspector.
Solution: Added a "CO2e per Unit" control before "Total CO2e" on the "Sust. Item Journal" page extension.

Bug 641055 – Scope 3 Distance: Installation Multiplier defaults to 0 in purchase documents (0 emissions)

Issue: On distance‑based Scope 3 purchase lines, Installation Multiplier defaulted to 0, so Distance × Factor × Multiplier = 0 — while the journal (InitValue = 1) worked.
Solution: Set InitValue = 1 on the purchase line "Installation Multiplier" field to mirror the journal, and removed Installation Multiplier from the formula zero‑checks (ClearEmissionInformation, CheckEmissionMustBeZeroWhenFormulaIsUpdated, CheckSustainabilityFormula) and gated recalculation via IsSustainabilityFormulaPurchaseLine(), so per‑unit/Fuel/Custom lines are unaffected.

Bug 641289 – Item Charge Emissions: wrong tooltip & not activated with Value Chain Tracking

Issue: Tooltip said "(currently not operating)"; enabling Value Chain Tracking didn't turn on Item Charge Emissions.
Solution: Added Rec.Validate("Item Charge Emissions", true) to the auto‑enable routine, corrected the Item Charge tooltip, and clarified the Enable Value Chain Tracking tooltip to list all auto‑enabled options.

Bug 641224 – Fixed Asset emissions posted for non‑Acquisition Cost FA lines

Issue: A purchase FA line with "FA Posting Type" ≠ Acquisition Cost (e.g. Maintenance) could still post sustainability entries, which isn't valid.
Solution: Restricted sustainability value‑entry posting to Acquisition Cost FA lines; posting with another FA posting type now errors ("It is only allowed to post Sustainability Entry for Acquisition Cost.") and creates no Sustainability Ledger Entry. Covered by new test TestSustValueChainFixedAssetForPurchaseInvoiceWithoutAcqCost.

Bug 641309 – Item Reclassification uses averaged emissions instead of Specific (lot/serial) carbon tracking

Issue: When an item uses Carbon Tracking Method = Specific, an item reclassification (location move) transferred cost correctly per tracked lots/serials, but emissions were calculated from an averaged CO2e per unit × quantity, ignoring the specific per‑lot/serial CO2e.
Solution: In GetTotalCO2eAmount (Sustainability Post Mgt), run the applied‑entries lookup first and, for Transfer entries, derive TotalCO2e from the specific applied CO2e (AppliedAmount / AppliedQuantity × Quantity), falling back to the averaged CO2e per unit only when no specific applied data exists — so emissions follow the moved lots/serials, mirroring how cost is transferred.
Files changed (14): SustItem.TableExt.al, SustItemJournal.PageExt.al, SustItemPostSubscriber.Codeunit.al, SustainabilityPostMgt.Codeunit.al, SustPurchaseSubscriber.Codeunit.al, SustainabilityPurchLine.TableExt.al, SustSalesSubscriber.Codeunit.al, SustServiceSubscriber.Codeunit.al, SustainabilitySetup.Page.al, SustainabilitySetup.Table.al, plus tests SustItemChrgAssignTest.Codeunit.al, SustValueChainFixedAsset.Codeunit.al, SustValueEntryTest.Codeunit.al, SustainabilityServiceTests.Codeunit.al.

Risk & compatibility: Scoped to the Sustainability app (posting subscribers, purchase line defaults, setup UI). Existing averaged/non‑item‑charge flows preserved; Transfer/specific paths only change when specific applied data exists. No schema/breaking changes.

[github-actions]

$\textbf{🟠\ High\ Severity\ —\ Performance}$

Both OnPostItemChargePerOrderOnAfterCopyToItemJnlLine and OnPostItemJnlLineJobConsumption call PurchaseHeader.Get(...) before checking whether the item journal line actually has quantity to post. When that quantity guard fails, the header lookup is wasted on a posting hot path; move the guard ahead of Get in both procedures.

Knowledge:

• microsoft/knowledge/performance/apply-guards-before-get.md

Line mapping was unavailable, so this was posted as an issue comment.

_{👍 useful · ❤️ especially valuable · 👎 wrong - reply with why · AL review agent v1.12.4}

[github-actions]

$\textbf{🟠\ High\ Severity\ —\ Style}$

The subscriber for Undo Service Shipment Line's OnAfterCopyItemJnlLineFromServShpt takes ServiceShipmentLine as its second parameter, but the publisher's second parameter is ServiceShipmentHeader. Subscriber parameters must follow the publisher signature exactly, so ServiceShipmentHeader needs to be inserted before ServiceShipmentLine.

Suggested fix (apply manually — could not be anchored as a one-click suggestion):

    local procedure OnAfterCopyItemJnlLineFromServShptForUndoServiceShipment(var ItemJournalLine: Record "Item Journal Line"; ServiceShipmentHeader: Record "Service Shipment Header"; ServiceShipmentLine: Record "Service Shipment Line")

Knowledge:

• microsoft/knowledge/style/event-subscriber-param-names-match-publisher.md

Line mapping was unavailable, so this was posted as an issue comment.

_{👍 useful · ❤️ especially valuable · 👎 wrong - reply with why · AL review agent v1.12.4}

[github-actions]

$\textbf{🟠\ High\ Severity\ —\ Style}$

The subscriber for Undo Service Consumption Line's OnAfterCopyItemJnlLineFromServShpt also skips the publisher's ServiceShipmentHeader parameter and declares ServiceShipmentLine second instead. Subscriber parameters must match the publisher signature verbatim, so this declaration needs the header parameter inserted before the line parameter.

Suggested fix (apply manually — could not be anchored as a one-click suggestion):

    local procedure OnAfterCopyItemJnlLineFromServShptForUndoServiceConsumption(var ItemJournalLine: Record "Item Journal Line"; ServiceShipmentHeader: Record "Service Shipment Header"; ServiceShipmentLine: Record "Service Shipment Line")

Knowledge:

• microsoft/knowledge/style/event-subscriber-param-names-match-publisher.md

Line mapping was unavailable, so this was posted as an issue comment.

_{👍 useful · ❤️ especially valuable · 👎 wrong - reply with why · AL review agent v1.12.4}

[microsoft-github-policy-service]

@v-rohangarg20 please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

• (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

• (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

Contribution License Agreement

This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.

1. Definitions.
   “Code” means the computer software code, whether in human-readable or machine-executable form,
   that is delivered by You to Microsoft under this Agreement.
   “Project” means any of the projects owned or managed by Microsoft and offered under a license
   approved by the Open Source Initiative (www.opensource.org).
   “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
   Project, including but not limited to communication on electronic mailing lists, source code control
   systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
   discussing and improving that Project, but excluding communication that is conspicuously marked or
   otherwise designated in writing by You as “Not a Submission.”
   “Submission” means the Code and any other copyrightable material Submitted by You, including any
   associated comments and documentation.
2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
   Project. This Agreement covers any and all Submissions that You, now or in the future (except as
   described in Section 4 below), Submit to any Project.
3. Originality of Work. You represent that each of Your Submissions is entirely Your original work.
   Should You wish to Submit materials that are not Your original work, You may Submit them separately
   to the Project if You (a) retain all copyright and license information that was in the materials as You
   received them, (b) in the description accompanying Your Submission, include the phrase “Submission
   containing materials of a third party:” followed by the names of the third party and any licenses or other
   restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
   guidelines concerning Submissions.
4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else
   for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
   Submission is made in the course of Your work for an employer or Your employer has intellectual
   property rights in Your Submission by contract or applicable law, You must secure permission from Your
   employer to make the Submission before signing this Agreement. In that case, the term “You” in this
   Agreement will refer to You and the employer collectively. If You change employers in the future and
   desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
   and secure permission from the new employer before Submitting those Submissions.
5. Licenses.

• Copyright License. You grant Microsoft, and those who receive the Submission directly or
  indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
  Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
  the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
  parties.
• Patent License. You grant Microsoft, and those who receive the Submission directly or
  indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
  Your patent claims that are necessarily infringed by the Submission or the combination of the
  Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
  import or otherwise dispose of the Submission alone or with the Project.
• Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
  No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
  granted by implication, exhaustion, estoppel or otherwise.

6. Representations and Warranties. You represent that You are legally entitled to grant the above
   licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
   have disclosed under Section 3). You represent that You have secured permission from Your employer to
   make the Submission in cases where Your Submission is made in the course of Your work for Your
   employer or Your employer has intellectual property rights in Your Submission by contract or applicable
   law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
   have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
   You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
   REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
   EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
   PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
   NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
7. Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
   You later become aware that would make Your representations in this Agreement inaccurate in any
   respect.
8. Information about Submissions. You agree that contributions to Projects and information about
   contributions may be maintained indefinitely and disclosed publicly, including Your name and other
   information that You submit with Your Submission.
9. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
   the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
   Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
   exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
   defenses of lack of personal jurisdiction and forum non-conveniens.
10. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
    supersedes any and all prior agreements, understandings or communications, written or oral, between
    the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.