Subcontracting in Sage X3: Setup, Flow, Packing and What MFGM Means
subcontracting in sage x3
Also searched as
- sage x3 packing process
- mfgm in sage x3
- sage x3 subcontract purchase order
Short answer
In Sage X3, subcontracting means an outside supplier performs one or more operations on your material. You flag the operation as subcontracted in the routing, the work order drives a purchase document to the subcontractor, components are sent, and the processed goods are received back into stock. MFGM is generally how people refer to the manufacturing module and its records, not a separate feature.
Applies to: Sage X3 Manufacturing, Purchasing and Stock modules, V7 and later; menu names vary by version and activity codes
A typical subcontracting flow
- 1Create the subcontractor as a supplier (or a BP with supplier role), with purchasing terms, currency and tax settings.
- 2Define the subcontracted operation in the routing, mark it as subcontracted and link the supplier and the service or processing item used for pricing.
- 3Set up the BOM so the components needed by that operation are tied to it and the operation output is the semi-finished or finished item.
- 4Create the work order, which generates a subcontracting need for the flagged operation.
- 5Create the subcontract purchase order from the need, with the processing price and the quantities to be processed.
- 6Send the components to the subcontractor with a stock issue or transfer to the supplier location, so material at the vendor stays visible.
- 7Receive the processed goods against the purchase order, which updates stock and the work order progress.
- 8Match the supplier invoice to the receipt and review variances on the processing cost.
How the pieces connect
Subcontracting in X3 sits at the junction of manufacturing, purchasing and stock. The routing says which operation is outsourced, the work order schedules it, the purchase order commits the service, and stock movements show component transfer and receipt. If any link is missing, you see material that disappears or work orders that never advance.
The most important control is knowing where inventory is. Components sitting at a subcontractor are still your assets. Use a dedicated supplier or subcontract stock location so quantities, costs and ageing stay visible and can be counted.
Packing process
Packing in X3 is handled in the sales and stock flow: after picking and delivery preparation, products are grouped into packages or containers and documented on the delivery and packing documents. Your version and configuration decide how detailed packing is, for example package types, weights and serial or lot content.
For subcontracting, packing is relevant when you ship goods to the subcontractor or return finished goods to customers. Keep package and lot information consistent, otherwise traceability breaks at the handoff.
What MFGM means
MFGM is commonly used shorthand for the manufacturing module and the objects that belong to it, such as manufacturing headers, material and operation records. It is not a separate subcontracting feature. If a document or support case says MFGM, read it as manufacturing, and confirm the exact object name in the data dictionary of your folder.
When people ask about manufacturing tables for reports, point them to the dictionary in the development tools rather than guessing names, because custom and version differences are common.
Try it here, free
Sage X3 Import Template Worksheet
An editable import tracker for Sage X3: which object, which import template, source file, records loaded, errors and owner, with error rates calculated.
Common pitfalls
- !Not tracking components at the subcontractor, so inventory is wrong and counts do not tie.
- !Pricing the processing service outside the PO, so cost cannot be matched to the invoice.
- !Receiving without linking to the work order, so progress is not updated.
- !Lot and serial numbers lost between shipment and receipt.
- !No lead time for the outsourced step, so scheduling dates are unrealistic.
How an ERP-grounded AI assistant handles this
Subcontract chains are hard to see because the data spans work orders, POs and stock locations. A private AI layer such as ERPray can answer questions like which components are at which subcontractor and which processed goods are overdue, showing the underlying query, read-only and inside your network.
Frequently asked questions
Do I need a separate item for the subcontracted service?
Often yes, because a service item gives you a price, a cost account and a clean invoice match. The exact approach depends on your configuration and costing setup, so agree it with your implementation partner before building the routing.
How do I see stock held at a subcontractor?
Use a dedicated stock location or supplier-owned location for subcontract material and report on it by supplier. Without it, quantities vanish from stock reports until the processed goods return.
What does MFGM stand for in X3?
It is generally used for the manufacturing module and its records. Check the exact table and object names in the data dictionary of your own folder, because names can differ across versions and customizations.
Can subcontracting be handled with a plain purchase order?
For simple outside processing, some companies do. But linking the operation to the work order gives scheduling, cost roll-up and material tracking. A plain PO is weaker for traceability when components are sent out.
Related
Sage X3 Production Planning, Scheduling and Tracking
Sage X3 plans production from master data (items, BOMs, routings, work centers) through MRP or manual work orders, schedules operations against work center capacity, then records progress with production tracking. Setup quality in the BOM, routing and work center calendar decides whether the plan is believable.
How-toHow to Run a Physical Inventory Count in Sage X3
Sage X3 physical counts run through Stock > Counts: create a count session scoped to a site, category, or zone, generate the count sheet to freeze theoretical quantities, enter counted quantities, review the variance report, then validate to post stock and valuation adjustments. Blocking movements against the counted locations during the window keeps the variance meaningful.
Error fixDivision by 0 Error in Sage X3: Find the Cause and Fix It
A division by 0 error in Sage X3 means a calculation divided by a field that was zero or empty at runtime. Typical sources are a zero unit-of-measure coefficient, a zero quantity or base quantity on a BOM or routing, a zero price or rate, or custom 4GL or report code that never guards the denominator. Find the script and line from the error, then fix the data or guard the calculation.
How-toSage X3 Developer Studio: What It Does and How to Track Versions and Release Notes
Sage X3 Developer Studio is the development environment for building and changing X3 solution code and web pages, working with the Adonix 4GL scripts and the Syracuse web layer. To track versions, read the release notes and compatibility guides that Sage publishes for each version and patch rather than relying on remembered dates.
How-toSage X3 API Documentation: REST (Syracuse), SOAP Web Services and Where to Find Docs
Sage X3 exposes data and business logic in two main ways: REST-style SData services through Syracuse, which read and write business objects as JSON or XML, and SOAP web services that publish X3 subprograms and objects. Official documentation is in Sage's online help and developer resources for your version.
How-toSage X3 Table Dictionary: How to Browse Tables and What PAYMENTD Holds
Sage X3 keeps its table definitions in a data dictionary you browse from the development area of the application. Tables are named in short uppercase codes, live in the folder's schema (often a schema named like the folder, such as SEED), and columns carry a numeric suffix like _0. PAYMENTD holds the line-level detail of payment entries, paired with a header table.
AI for ERPAI for Sage X3, Grounded in Your Own Ledgers and Stock Data
Add AI to Sage X3 finance and stock data without exporting it to a public model. On-prem and private-cloud LLMs for Sage X3 in the UK and France.
Stuck on Sage X3?
Talk to engineers who work inside Sage X3 every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- Sage X3 Import Template WorksheetAn editable import tracker for Sage X3: which object, which import template, source file, records loaded, errors and owner, with error rates calculated.
- Sage X3 Database Tables ReferenceKey Sage X3 tables by module with what they store, typical key columns and naming conventions for SQL and reporting.
- Sage X3 Maintenance Checklist and ScheduleA tick-box routine maintenance plan for Sage X3: database, batch server, Syracuse, backups, patches, security and testing.
ERP fixes and how-tos
- Sage X3 Production Planning, Scheduling and TrackingHow Sage X3 production planning works: master data, MRP, work orders, scheduling and shop floor tracking, and what to set up first. Practical overview.
- Sage X3 production and warehouse management: how the setup fits togetherHow Sage X3 production and warehouse management fit together: master data, work orders, locations, stock movements and the order to set them up in.
- How to set up Sage X3 mobile automation for the warehouse and shop floorHow to plan and set up Sage X3 mobile automation: prerequisites, devices, server and network checks, process scope and testing for warehouse and shop floor.
AI on your ERP
- AI for Sage X3 Purchasing and Stock: Orders, Receipts and LotsAI for Sage X3 purchasing and stock: PO review, supplier delivery analysis, stock status and lot questions over X3 data using GraphQL, SOAP and private models.
- AI for Sage X3, Grounded in Your Own Ledgers and Stock DataAdd AI to Sage X3 finance and stock data without exporting it to a public model. On-prem and private-cloud LLMs for Sage X3 in the UK and France.
Integrations
- How to add document OCR to Sage X3Capture supplier invoices, packing slips and certificates into Sage X3 with OCR, confidence thresholds, PO matching and human review. On-prem options covered.
- How to add AI agents to Sage X3How to add AI agents to Sage X3: a tool layer over SData and web services, read-first design, human approval on writes, and on-prem models for MRP and POs.