Skip to main content

Overview

The Data Search feature enables operators to quickly retrieve production information from the Oracle Support Dashboard by entering a serial number. This integration eliminates manual data entry and ensures accuracy when logging label printing incidents.

Search Workflow

1

Enter Serial Number

Type the serial number of the affected unit into the Serial Number field on the incident logging form.
2

Click Search

Click the “Search” button to query the Oracle Support Dashboard for related production data.
3

Review Retrieved Data

The system automatically populates all available fields with data from Oracle, including job number, item description, order information, and shipping details.
4

Adjust if Needed

Review the autofilled data and make any necessary corrections before submitting the incident.

Search Parameters

The search functionality uses a simple parameter model:
public class SearchParameters
{
    public string SerialNumber { get; set; }
}
Only the serial number is required to retrieve comprehensive production data from Oracle Support Dashboard.

GetReportData Endpoint

The GetReportData endpoint handles communication with the Oracle Support Dashboard:
[HttpPost]
public async Task<IActionResult> GetReportData([FromBody] SearchParameters parameters)
{
    try
    {
        var requestUrl = $"{BaseUrl}GetReportData?id=2154&parameters={{\"serial_number\":\"{parameters.SerialNumber}\"}}";
        var response = await _httpClient.PostAsync(requestUrl, null);

        if (response.IsSuccessStatusCode)
        {
            var jsonResult = await response.Content.ReadAsStringAsync();
            return Json(jsonResult);
        }

        var errorContent = await response.Content.ReadAsStringAsync();
        return Json(new { error = $"Error al obtener datos. Status: {response.StatusCode}, Content: {errorContent}" });
    }
    catch (Exception ex)
    {
        return Json(new { error = $"Error detallado: {ex.Message}" });
    }
}

Endpoint Configuration

The Oracle Support Dashboard base URL is configured in the controller:
private const string BaseUrl = "https://azuappsrvuat01v.mcquay.com/SupportDashboard/Home/";

Request Format

The endpoint constructs a GET request with query parameters:
  • id=2154: Report identifier for the label data report
  • parameters: JSON object containing the serial number to search

Response Handling

  • Success: Returns the JSON data from Oracle Support Dashboard, which contains all production information for the serial number
  • Failure: Returns an error object with status code and error details for troubleshooting
  • Exception: Returns detailed exception message for technical diagnosis

Oracle Support Dashboard Integration

The search functionality integrates with Daikin’s Oracle Support Dashboard, which serves as the central repository for production data. This integration:
  • Provides real-time access to Oracle ERP data
  • Ensures data consistency between systems
  • Reduces manual data entry errors
  • Accelerates incident logging process
The integration uses report ID 2154, which is specifically configured to return label-related production data including job numbers, order details, and shipping information.

Retrieved Data Fields

When a search is successful, the Oracle Support Dashboard returns data that populates these form fields:
FieldDescriptionSource System
JobJob number from production orderOracle ERP
ItemItem code or part numberOracle ERP
DescriptionProduct descriptionOracle ERP
OrderNumberProduction order numberOracle ERP
OrderLineOrder line item numberOracle ERP
LPNLicense Plate NumberOracle WMS
TagNumberPhysical tag identifierOracle WMS
ShipCodeShip-to destination codeOracle ERP
IRNOInternal Receipt NumberOracle ERP
SubinvSubinventory locationOracle WMS
AddressFull shipping addressOracle ERP

Error Handling

The search endpoint includes comprehensive error handling:

HTTP Errors

If the Oracle Support Dashboard returns a non-success status code, the endpoint returns:
{
  "error": "Error al obtener datos. Status: [StatusCode], Content: [ErrorDetails]"
}

Network Errors

If a network exception occurs (timeout, connection failure, etc.), the endpoint returns:
{
  "error": "Error detallado: [ExceptionMessage]"
}

Client-Side Handling

The front-end JavaScript handles these error responses and displays appropriate messages to the operator, allowing them to:
  • Retry the search
  • Manually enter the data
  • Report connectivity issues to IT support

Performance Considerations

The search uses asynchronous HTTP calls (async/await) to prevent blocking the application while waiting for Oracle Support Dashboard responses. This ensures the UI remains responsive even during slow network conditions.

Use Cases

Primary Use Case: Incident Logging

When logging a label printing error, operators can search by serial number to quickly populate all production details, ensuring complete and accurate incident records.

Secondary Use Case: Data Verification

Operators can use the search feature to verify production data before creating labels, helping prevent errors before they occur.

Support Use Case: Troubleshooting

Support teams can search historical data to investigate patterns in label printing errors and identify root causes related to specific jobs, items, or production lines.

Build docs developers (and LLMs) love