Bug 633674: Subcontracting Type field and enum captions are unclear — rename to Component Supply Method

[ChethanT]

Bug Summary

The Subcontracting Type wording was unclear in Subcontracting pages and enum captions. The labels implied a subcontracting classification instead of the actual intent: how components are supplied to the subcontractor.

Root Cause

User-facing names and captions did not reflect the functional meaning of the field and enum values, which caused confusion in UI interpretation and setup decisions.

Fix

• Renamed enum object from Subcontracting Type to Component Supply Method.
• Updated enum value captions:
  • Purchase with Service -> Vendor-Supplied
  • Inventory by Vendor -> Consignment at Vendor
  • Transfer -> Transfer to Vendor
• Updated related captions/tooltips/messages in Subcontracting App to align terminology.
• Updated references in app/test AL code to the renamed enum object.

Test Added

• Codeunit: 139990 (Subc. Subcontracting UI Test)
• Test function: ComponentSupplyMethodCaptionsAreClear
• Coverage:
  • Verifies field caption is Component Supply Method on Production BOM Line, Planning Component, and Prod. Order Component.
  • Verifies enum value captions are Vendor-Supplied, Consignment at Vendor, and Transfer to Vendor.

Validation

• App compiles and publishes.
• Tests run and pass.

AB#633674

[ChethanT]

@SPinkow

[github-actions]

AL Documentation Audit

Documentation gaps were detected in the following apps:

• Subcontracting-Test: 0% documentation coverage
• Subcontracting: 0% documentation coverage

To generate documentation, run /al-docs init or /al-docs update using GitHub Copilot CLI or Claude Code.
This review is for awareness to help keep documentation in sync with code changes. It is okay to dismiss this request.

[alexei-dobriansky]

I see that this jargon is used by people who work with subcontracting process. It's confusing, though, who owns the stock - we or subcontractor.