The source package enumerates a functional scope that stops at Inventory and Purchasing, so this module states what that silence means, what carries over from the inventory and costing evidence, and what must be scoped independently if production is in play.
The source package for PeopleSoft FSCM enumerates its functional scope explicitly: General Ledger, Payables, Receivables and Billing, Purchasing, Inventory, Project Costing and Asset Management, together with ChartFields, trees, combo-edit rules, SetID and tableset sharing, Journal Generator, feeder-accounting patterns and the…
It is worth being precise about what the package covers, because "manufacturing is out of scope" is a sentence people hear as "manufacturing does not matter".
Three areas of evidence apply to production even though production itself is uncovered.
The customisation register describes twelve surfaces generically — PeopleCode, Application Engine, Application Designer modifications, Component Interfaces, Integration Broker service operations, Voucher Build and Billing Interface extensions, SQR, BI Publisher, AWE, the configurable PeopleTools surfaces, and Excel-to-Component-Interface…
If the answer to the scoping question is anything other than a clean "no production modules are in use", this is the discovery that produces a defensible scope. None of it can be answered from this path.
Leaving this domain unscoped produces one of two outcomes, and both are avoidable by asking the question early.
Where the estate genuinely does not run production modules, this domain closes quickly, but not silently. Record three things:
This module is short because the evidence is thin, and it says so rather than filling the space.