Rename Fields for integration into Italy

[SPinkow]

What & why

This pull request standardizes and updates the naming of fields related to subcontracting throughout the manufacturing and purchasing extension codeunits. The changes focus on consistently using the "Subc." prefix for all relevant fields, replacing older or inconsistent names (such as "Orig." or "Subcontr.") with the new convention. This improves code clarity, maintainability, and reduces the risk of confusion or errors.

The most important changes are:

Field Renaming and Standardization (Subcontracting):

• Replaced all occurrences of "Orig. Location Code" and "Orig. Bin Code" with "Subc. Original Location Code" and "Subc. Orig. Bin Code" in procedures transferring data between production BOM lines, planning components, and production order components. [1] [2] [3] [4] [5]
• Changed all references from "Subcontr. Location Code" to "Subc. Location Code" when copying vendor fields to purchase headers and when retrieving subcontractor locations. [1] [2]

Transfer and Posting Line Updates:

• Updated all transfer shipment and transfer line field names to use the "Subc." prefix (e.g., "Subc. Prod. Order No.", "Subc. Prod. Order Line No.", "Subc. Prod. Ord. Comp Line No.") instead of the previous naming convention. [1] [2] [3]
• Modified direct transfer line copying to use the new "Subc."-prefixed field names for all relevant fields (purchase order, production order, routing, etc.).

Journal and Ledger Entry Consistency:

• Updated item journal line and ledger entry field assignments to use "Subc."-prefixed fields, ensuring consistency in how subcontracting-related data is stored and processed. [1] [2]
• Renamed "Item Charge Sub. Assign." to "Subc. Item Charge Assign." for clarity and consistency in item journal and value entry logic. [1] [2]

These changes collectively ensure that all subcontracting-related data is handled using a unified and clear naming convention, reducing ambiguity and supporting future maintenance and development.

Linked work

Fixes AB#406123

How I validated this

• I read the full diff and it contains only changes I intended.
• I built the affected app(s) locally with no new analyzer warnings.
• I ran the change in Business Central and confirmed it behaves as expected.
• I added or updated tests for the new behavior, or explained below why none are needed.

What I tested and the outcome (required — be specific: scenarios, commands, screenshots for UI changes)

Risk & compatibility

None

[SPinkow]

@ChethanT
This is the PR for renaming the fields in Subcontracting App so that this APP will compile with italian base app, too.
For the moment it is just for information. Let's discuss the right time for merging this at our next status meeting.