Move Subcontracting Setup Fields To Manufacturing Setup (except wizard setup)#7100
Conversation
|
@stevengrossGOB please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
1 similar comment
|
@stevengrossGOB please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
Summary
This pull request refactors the subcontracting setup logic to use the
Manufacturing Setuptable instead of theSubc. Management Setuptable for storing and retrieving most subcontracting-related configuration. This change centralizes subcontracting configuration, updates initialization routines, and modifies how various processes access setup data throughout the application.Centralization of Subcontracting Configuration:
Subc. Management SetupwithManufacturing Setupfor storing and retrieving most subcontracting-related fields, such as template names, batch names, routing link codes, and handling times, across codeunits including initialization, purchase order creation, and process wizards. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12]Initialization and Setup Logic:
Subcontracting Comp. Init.to create and configure theManufacturing Setuprecord instead ofSubc. Management Setup, and adjusted related helper procedures accordingly.Process and Helper Function Updates:
GetManufacturingSetuphelper procedures and corresponding boolean flags in affected codeunits to cache and retrieve theManufacturing Setuprecord, replacing previous logic that usedSubc. Management Setup. [1] [2] [3] [4]Field and TestField Adjustments:
TestFieldand field access calls to reference fields inManufacturing Setup(e.g.,"Subcontracting Template Name","Subc. Inb. Whse. Handling Time","Rtng. Link Code Purch. Prov.","Subc. Comp. at Location", etc.), and adjusted logic for handling missing or required configuration. [1] [2] [3] [4]Namespace and Dependency Updates:
using/importstatements to includeMicrosoft.Manufacturing.Setupin all affected files to ensure access to the new centralized setup table. [1] [2] [3]These changes collectively improve maintainability and consistency by consolidating subcontracting configuration into a single setup table.y
Work Item(s)
Fixes # AB#618366