Search Results problem_summary

Overview

CS_MFS_INTERFACE is a Service (CS) module view in Oracle E-Business Suite 12.1.1 and 12.2.2 that presents field service incident and dispatch data flowing through the Mobile Field Service (MFS) interface. The view consolidates incident, task, resource, customer, product, and appointment attributes into a single denormalized row per field service interface record, identified by FIELD_SERVICE_INTERFACE_ID. It is used by integrations that stage, transform, or synchronize field service transactions between external systems (such as mobile devices or third-party dispatch applications) and the Oracle EBS Service foundation tables.

In the ETRM metadata for 12.2.2, the view is documented as "Not implemented in this database," indicating that the object itself exists as a definition but holds no data in the reference environment. Its role is structural and integration-oriented: it provides a read interface over the underlying MFS staging table without requiring consumers to join the normalized Service entities directly.

Underlying Base Objects

The view is defined over a single base object, CS_MFS_INTERFACE_ALL, according to the documented view text. No other referenced base objects are recorded in the ETRM metadata. All columns projected by the view—including INCIDENT_NUMBER, ACTION_NUM, STATUS_FLAG, ORG_ID, PROBLEM_CODE, RESOLUTION_CODE, EMPLOYEE_ID, CUSTOMER_ID, INVENTORY_ITEM_ID, and the fifteen descriptive ATTRIBUTE columns—originate from this table.

The WHERE clause implements multi-org security by comparing the row's ORG_ID against the organization identifier derived from USERENV('CLIENT_INFO'). Rows with a NULL ORG_ID are matched using a sentinel value of -99, ensuring that global or unassigned records remain accessible regardless of the current operating unit context. Because the view filters on ORG_ID, query results are automatically restricted to the responsibilities' accessible organizations.

Key Columns

• FIELD_SERVICE_INTERFACE_ID — Primary identifier for the interface row.
• STATUS_FLAG — Processing status of the interface record, used to select unprocessed, in-progress, or completed transactions.
• ORG_ID — Operating unit identifier driving multi-org access control through the view's WHERE clause.
• INCIDENT_NUMBER, ACTION_NUM, INCIDENT_DATE — Incident identifier, task (action) number, and incident date for the field service request.
• PROBLEM_CODE, PROBLEM_DESCRIPTION, RESOLUTION_CODE, RESOLUTION_DESCRIPTION — Codes and text describing the reported problem and its resolution. Extended fields SR_PROBLEM_DESCRIPTION, SR_RESOLUTION_DESCRIPTION, and INC_PROB_DESCRIPTION provide additional descriptive variants.
• INCIDENT_URGENCY_ID, URGENCY, INCIDENT_STATUS_ID, STATUS_CODE, INCIDENT_TYPE, INCIDENT_SEVERITY_NAME — Classification and priority attributes of the incident.
• DISPATCHER_ID, DISPATCHER_NAME, EMPLOYEE_ID, EMPLOYEE_NAME — Dispatcher and assigned field service technician.
• CUSTOMER_ID, CUSTOMER_NUMBER, CUSTOMER_NAME — Customer account reference.
• CURRENT_CONTACT_* — Contact name, telephone, fax, and email details for the incident.
• SHIP_TO_ADDRESS_LINE1/LINE2, CITY, STATE, POSTAL_CODE, COUNTRY — Service location address.
• START_TIME, END_TIME, EARLIEST_START_TIME, LATEST_FINISH_TIME, APPOINTMENT, REQUEST_DURATION — Appointment and scheduling window attributes.
• INVENTORY_ITEM_ID, PRODUCT, PRODUCT_DESCRIPTION, CURRENT_SERIAL_NUMBER, INSTALLATION_DATE — Installed base product and serial information.
• COVERED_BY_CONTRACT, REFERENCE_NUMBER — Contract coverage indicator and external reference.
• ATTRIBUTE1–ATTRIBUTE15, CONTEXT — Descriptive flexfield columns for customer-specific extensions.

Common Use Cases and Queries

Typical uses include monitoring unprocessed interface records, validating dispatch data before loading into Service Request tables, and reconciling mobile-collected field data with EBS incidents. A representative query to list pending records for the current organization is:

SELECT FIELD_SERVICE_INTERFACE_ID, INCIDENT_NUMBER, ACTION_NUM,
       STATUS_FLAG, PROBLEM_CODE, CUSTOMER_NAME,
       EMPLOYEE_NAME, START_TIME
FROM   CS_MFS_INTERFACE
WHERE  STATUS_FLAG = 'N';

To review scheduling details for a specific incident, the view can be filtered by incident number without joining any base table:

SELECT INCIDENT_NUMBER, ACTION_NUM, PROBLEM_DESCRIPTION,
       DISPATCHER_NAME, EARLIEST_START_TIME, LATEST_FINISH_TIME,
       APPOINTMENT, REQUEST_DURATION
FROM   CS_MFS_INTERFACE
WHERE  INCIDENT_NUMBER = :incident_number;

Because multi-org filtering is embedded in the view definition, queries execute under the caller's operating unit context; no explicit ORG_ID predicate is required, simplifying integration and reporting logic across Service responsibilities.