SoftTech AI Registry
Oracle · Oracle Fusion Cloud Maintenance

Postmaintenance Work Recorder

Oracle AI Agent Studio agent template introduced in Update 25D under the Maintenance module. A technician who has already completed an unplanned or informal repair uses the Report Orderless Work button on the My Maintenance Work page to describe the completed work. The agent validates the asset, creates a maintenance work order with a single Orderless Reporting operation in the maintenance organization, records the material transactions and labour/resource transactions the technician reports, and Oracle states the work order is created, released and marked as complete with material and resource transactions but not automatically closed. The physical repair has already happened; the agent creates the retrospective digital record of it.

Recorded characteristics

Function
Oracle Update 25D documents the Postmaintenance Work Recorder AI Agent template as available to record completed repair activities by creating a maintenance work order and logging the associated materials and labor, using the Report Orderless Work button on the My Maintenance Work page. Oracle's own agent description is: record maintenance activity by creating a maintenance work order based on technician prompts to record operation, materials issued, labor charged after the work has been completed. Documented flow: (1) the technician must provide a valid asset number, and Oracle states the system will validate the asset and ensure it is enabled for maintenance transactions; if the asset is not valid the agent prompts the user to enter a correct asset number. Asset detail retrieval is documented as a deterministic business-object tool (Maintenance Asset Tool, SCM_MNT_MAINTENANCE_ASSET_TOOL) that, given an asset number, returns AssetId, ItemNumber, ItemId, default work order type, default work order subtype and default work center code. (2) The maintenance organization is required and defaults from the My Maintenance Work organization selector; to create the work order in a different organization the user must explicitly enter that organization. (3) The technician describes the repair activity or provides a work order description; if no description is entered the system generates one from user input, excluding asset, organization and work center, limited to 220 characters. (4) The agent creates a single Orderless Reporting operation using the work center specified by the user. (5) If parts were used the user must provide the item and quantity; the subinventory may default from organization parameters but Oracle states it is the user's responsibility to ensure the correct subinventory is selected or provided, and materials cannot be issued without these values. Serial and lot-controlled items are supported, and the user must provide the serial and lot number when transacting serialized or lot-controlled materials. The user must explicitly specify if no materials were issued for the work order. (6) If the technician reports time spent they must include the duration; if time is mentioned the agent requires a corresponding resource code and prompts for it when missing. The resource code defaults from the logged-in user where the user profile has a designated resource and is used automatically when time is recorded. The user must explicitly mention if no labour charges are reported. (7) Oracle states the work order is created, released and marked as complete with material and resource transactions but not automatically closed. The registry attributes to the agent only what Oracle documents it doing through its tools: work order creation, the single Orderless Reporting operation, material transactions, resource transactions, operation completion and the released/complete status transitions Oracle describes. Downstream deterministic Oracle processing - inventory on-hand effects of an issue, maintenance cost accumulation, costing and accounting posting, and work order closure - is ordinary Oracle Maintenance processing and is not attributed to the agent.
Data access
Oracle documents the agent operating through business-object tools over maintenance data: the Maintenance Work Order Tool (MNT_WO_TOOL) to retrieve and manipulate maintenance work orders; the Maintenance Asset Tool (SCM_MNT_MAINTENANCE_ASSET_TOOL), which given an asset number returns AssetId, ItemNumber, ItemId, default work order type, default work order subtype and default work center code; the Maintenance Work Order Material Transaction Tool (SCM_MNT_WO_MATL_TRANSACT_TOOL), which creates a material transaction recording consumption of spare parts or materials against a specific work order operation, with material identified by item or part number and, if applicable, serial number or lot number, issued from an identified subinventory; the Maintenance Work Order Operation Soft Completion Tool (SCM_MNT_WO_OP_SOFTCOMPLETE_TOOL); the Maintenance Work Order Operation Transaction Tool (SCM_MNT_WO_OP_TRANSACT_TOOL); and the Maintenance Work Order Resource Transaction Tool (SCM_MNT_WO_RESC_TRANSACT_TOOL), which creates a resource transaction recording usage of labour or equipment resources against a specific work order operation. The agent also reads the maintenance organization defaulted from the My Maintenance Work organization selector, the work center supplied by the user, item/quantity/subinventory and serial or lot values supplied by the user, duration and resource code, and the resource designated on the logged-in user's profile where one exists. Access to wider SCM, procurement, costing, financial, HR or payroll data is not established.
Actions
Can take actions
External actions
Unknown
Human confirmation
Not established
Permission basis
Not established
Administrative control
Oracle documents the feature with an Action to Enable of Setup Required and describes explicit deployment steps: use AI Agent Studio to Use Template or Copy Template from the preconfigured agent template to create agents for the business process; then enable the Report Orderless Work button on the My Maintenance Work page by opening the page's Settings and Actions menu, selecting Edit Page in Visual Builder Studio, setting the showOrderlessReportingAction attribute to true in the Work Assignments Review pane, entering the postMaintenanceWorkReportingAgentCode of the agent team created from the template in AI Agent Studio, and publishing the changes, after which the Report Orderless Work button appears as a page-level button on My Maintenance Work. Access requirements are documented: to access Oracle AI Agent Studio for Fusion Applications and manage SCM AI agents, users must have a configured job role containing the SCM Intelligent Agent Management Duty (ORA_RCS_SCM_AI_AGENT_MANAGEMENT_DUTY and ORA_RCS_SCM_AI_AGENT_MANAGEMENT_DUTY_HCM, both required) and the Fai Genai Agent SCM Administrator Duty (ORA_DR_FAI_GENERATIVE_AI_AGENT_SCM_ADMINISTRATOR_DUTY); to interact with AI agents in product pages users must have a configured job role containing the Fai Genai Agent Runtime Duty (ORA_DR_FAI_GENERATIVE_AI_AGENT_RUNTIME_DUTY), permission groups must be enabled in the Security Console on those users' configured job roles, and those job roles must also contain privileges that allow access to the pages where AI agents are enabled. Organization scope is influenced by the My Maintenance Work organization selector, and the resource code default derives from the logged-in user's profile. Oracle does not document a per-transaction approval control for this agent.
Default state
Disabled
Availability
Documented in the Oracle Fusion Cloud SCM Update 25D Maintenance readiness material, added to Update 25D on 26 September 2025 per the revision history, and still listed in Oracle's current Supply Chain & Manufacturing features with AI catalogue as AI Agent: Postmaintenance Work Recorder, Update 25D, type AI agent. The 25D Feature Summary lists it under the Maintenance module with Impact to Existing Processes of None and Action to Enable of Setup Required. Oracle does not state GA, preview, regional or language restrictions for this agent in the reviewed material, so those are not established.
Licensing
Not established. Oracle documents AI Agent Studio and the required duty roles but states no separate licensing terms for this agent in the reviewed material.
External model or provider
Not established
Limitations and uncertainty
Boundaries and open questions. (1) Retrospective only: the physical repair has already been performed by a human; the agent creates the digital record afterwards. Oracle does not document the agent performing maintenance, controlling or communicating with equipment, diagnosing faults, dispatching technicians or scheduling repairs. (2) Naming: Oracle uses both Postmaintenance Work Recorder (feature title, catalogue entry) and Post Maintenance Work Recorder (the Agent Name field on the same feature page). These are treated as naming variants of one capability; a single capability is recorded. (3) Invocation: the technician starts each recording session using the Report Orderless Work button on My Maintenance Work; Oracle documents no scheduled, event-driven or background execution. Oracle recommends performing only one work order transaction per session. (4) Asset validation: Oracle states the system validates the asset and ensures it is enabled for maintenance transactions, and documents a deterministic Maintenance Asset Tool that returns asset details and defaults; whether validation logic is performed by the model or by that tool is not separately stated, and behaviour is recorded as deterministic tool-supported validation rather than model reasoning. (5) Work order fields: Oracle documents asset, organization, description (user-supplied or system-generated up to 220 characters), work center, and a single Orderless Reporting operation for this agent. Default work order type, subtype and work center code are returned by the asset tool; whether the agent sets priority, planned dates or other header fields is not documented for this agent and is not established. (6) Operation completion: Oracle lists both a Soft Completion Tool and an Operation Transaction Tool (operation transaction or operation hard completion transaction) among the agent's tools but does not state which is used in which circumstance, so the exact completion mechanism is not established. (7) Status transitions: Oracle states the work order is created, released and marked as complete but not automatically closed. Oracle's general Maintenance documentation describes Released as the transition from scheduling to execution, states that upon executing the work order the work order is automatically updated to a Completed status when the last operation is completed, and states that you then update the status to Closed. Whether each transition here is invoked by the agent or produced by deterministic Oracle processing after the agent's transactions is not separately established. (8) Closure and costing: Oracle affirmatively states the work order is not automatically closed by this flow, and its general Maintenance documentation states that closing prevents further updates and that the costing and variances of the work order are posted upon closing, via the Close action in Maintenance Work Orders or the Mass Close Maintenance Work Orders scheduled process. Closure is therefore performed later by a human or a scheduled process, not by this agent. (9) Financial boundary: the highest authority established for the agent is creating maintenance material and resource transactions against a work order operation. Oracle's benefit statement about accurate labour and material costing does not itself establish that the agent creates costing transactions, accounting distributions or general ledger postings, and no payroll, timecard, compensation or payment authority is documented or implied; maintenance resource costing is distinct from payroll. (10) Inventory effect: the material transaction records consumption issued from an identified subinventory; the resulting on-hand, serial/lot state and costing effects are ordinary Oracle inventory and costing processing and are not attributed to the agent. (11) Human confirmation: the technician initiates the session and supplies every transaction value, and the agent prompts for missing asset numbers, resource codes and explicit statements that no materials or no labour were used, but Oracle documents no review or confirmation step before work order creation, material transactions, resource transactions or completion, so confirmation is recorded as not established rather than not required. (12) Permission basis: the Fai Genai Agent Runtime Duty and page privileges are required for users to interact with agents, but Oracle does not state the identity under which the business-object tools execute the maintenance transactions, so runtime permission basis is not established. (13) External action: no emailing, external system invocation, external asset update, connected-equipment communication or external service request is documented for this agent; because a definite negative is not affirmatively stated, external action capability is recorded as unknown. (14) Session limitation: Oracle states that when prompted for missing information users should rephrase their entire request with the new detail included, because the agent does not retain memory of prior message fragments in updates, and recommends clearing the session context and restarting the agent if unexpected results occur. (15) Model/provider: not established. (16) Maintenance Work Order Builder, documented separately in the same Update 25D material as a conversational agent for creating, updating and retrieving maintenance work orders, is a different capability and is not recorded here.

Evidence