(Bug 618119): [Subcontracting] Subcontracting App has folder structure that needs to be aligned with other 1st party apps

[alexei-dobriansky]

Summary

Realigns the Subcontracting app's folder layout (src/Apps/W1/Subcontracting/) to match the convention used by Quality Management and other W1 1st-party apps: feature folders at the top level, all AL object types coexisting flat inside each feature.

This is a file-move refactor. The only content edits are two report layout-path corrections (see below) — no object renames, no logic changes. The AL compiler discovers files via app.json's glob, so source paths are not otherwise referenced and moves do not affect compilation.

This branch has been merged with the latest main. The folder counts below reflect the current state, which differs from the original branch point: main has since removed the Prod Order Creation Wizard and Profiles areas and added a WIP Item area. Those upstream content changes are not part of this refactor — this PR only determines where the current set of files lives.

What changed

Before

App/src/Process/{Codeunits,Pages,Pageextensions,Tableextensions,Enumerations,Tables,Reports,...}/... — a Process/ umbrella with type-subfolders, plus inconsistent sub-domain folders (Manufacturing/, Purchase/, Transfer/, etc.) only inside the extension type-folders.

After — App/src/

Folder	Files
General/	9
Manufacturing/	43
MasterData/	8
Purchase/	27
Setup/	4
Transfer/	33
Warehouse/	12
WIPItem/	12
Worksheet/	3
Install/	4 (unchanged)
Permissions/	6 (unchanged)
RoleCenters/	10 (unchanged)
Total	171

After — Test/

The Test/src/Codeunits/ wrapper has been removed. Test layout:

• Test/Tests/ — 22 test codeunits
• Test/Libraries/ — 8 helpers (includes one PageExt previously misfiled under src/Codeunits/General/)
• Test/DisabledTests/ — unchanged

Top-level App/app.json, Test/app.json, the extension logos, and SubcontractingWorkspace.code-workspace are unchanged. Total objects: 207 — identical set to main, only reorganized.

Naming conventions adopted (from Quality Management)

• Feature folders at top level; all object types coexist inside each feature folder
• No type-subfolders (no Codeunits/, Pages/, Enums/ inside features)
• Sub-features are flattened (the WIP Item/Posting Preview/ sub-area folds into WIPItem/)
• "Infrastructure" folders (Permissions/, RoleCenters/, Install/) stay flat

Report layouts (the only content edits)

Reports move into their feature folder together with their layout files, and the layout-path properties — which hardcode the file path — are updated to match:

• SubcDetailedCalculation.Report.al + Rep99001500.SubcDetailedCalculation.rdl → Purchase/
  RDLCLayout = 'src\Purchase\Rep99001500.SubcDetailedCalculation.rdl'
• SubcDispatchingList.Report.al + SubcDispatchingList.docx → Manufacturing/
  WordLayout = '.\src\Manufacturing\SubcDispatchingList.docx'

These are the only two files with line-level changes; every other file is a pure move (verified: 181 renames, 0 additions/removals relative to main).

Notable file classifications

• SubcontractorPrice.Table.al + SubcontractorPrices.Page.al + SubcPriceManagement.Codeunit.al → Purchase/ (subc-purchase pricing, used at PO creation)
• SubcILEntries.PageExt.al + SubcItemLedgerEntry.TableExt.al → General/ (ILE is cross-cutting inventory, not warehouse-specific)
• SubcCapLEntries.PageExt.al → Manufacturing/ (capacity entries are produced from prod order routing)
• SubcTransferManagement.Codeunit.al → Transfer/
• ComponentSupplyMethod.Enum.al → Manufacturing/ (alongside ComponentsatLocation.Enum.al)
• WIP Item area (incl. the Posting Preview sub-area) → flat WIPItem/ feature folder
• Setup/{Pages,Tables,ApplicationAreas}/... → flat Setup/
• Process/Codeunits/Extensions/{Manufacturing,MasterData,Purchase,Transfer,Warehouse}/ codeunit extensions → distributed to their respective feature folders

Fixes AB#618119

[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.

[SPinkow]

I have a question at this point.
We’re continuing to work on the current subcontracting app, adding and modifying objects and adding functionality. If all objects are moved throughout the entire app now, this will certainly lead to merge conflicts. I understand that this work needs to be done, and I definitely support a better folder structure, but changes and code moves often make our pull requests more complicated than necessary and we have to run through more iterations than needed.
I therefore suggest that cleanups and code moves (single functions or complete objects) be done only after the functional changes have been merged. That would make our work easier and reduce errors during subsequent merges.

I'll copy this over to Teams as well so we can discuss the topic more effectively. Thank you very much for your understanding.

[ChethanT]

We will wait for the bigger tasks to be done

[ChethanT]

Block to make way for #8436