Scheduled jobs in manufacturing planning not triggering on-premise MES updates

SCM Oracle Fusion Cloud SCM
, , , , , , , ,
1

Manufacturing planning scheduled jobs are not triggering the required updates to our on-premise MES system. The jobs run successfully in Fusion Cloud (we can see completion in Scheduled Processes), but the integration flow that sends production schedules to MES never executes. When checking the integration agent status, it shows connected, but no job trigger events are being received.

Our job definition configuration in manufacturing planning includes:

<jobTrigger>
  <endpoint>MES_PROD_SCHEDULE</endpoint>
  <frequency>HOURLY</frequency>
</jobTrigger>

This is blocking production scheduling since shop floor systems aren’t receiving updated work orders. Has anyone resolved scheduled job trigger issues with on-premise MES connectivity?

2

I’ve implemented this exact pattern for multiple manufacturing clients in 23c. Here’s the comprehensive solution addressing all three focus areas:

Integration Agent Status: First, verify the Connectivity Agent is properly configured and can reach your MES endpoint:

  1. Log into the agent admin console (typically http://agent-host:7101/agent)
  2. Go to Monitoring > Connectivity Tests
  3. Add a new test for your MES endpoint (hostname and port)
  4. Run the test and verify successful connection
  5. Check agent logs for any SSL/TLS handshake failures if MES uses HTTPS

If the agent shows connected to Oracle Cloud but can’t reach MES, you have a network/firewall issue between the agent and MES. Work with your network team to open required ports.

Job Definition Configuration: The key issue is that manufacturing planning scheduled jobs don’t automatically trigger external integrations. You need to configure a business event subscription:

  1. In Integration Cloud, create/modify your integration to use Oracle ERP Cloud adapter as the trigger
  2. Configure the trigger to subscribe to business event: `oracle.apps.scm.planning.scheduleManagement.scheduleGeneration.ScheduleGenerationEvent
  3. Add a filter condition to only trigger for your specific planning jobs
  4. In the integration flow, add the Connectivity Agent connection to invoke your on-premise MES

Alternatively, if business events aren’t available for your specific job type, use this approach:

// Add this as a post-processing step in your planning job
// Use Integration Cloud REST API to trigger the flow
const integrationURL = 'https://your-instance.integration.ocp.oraclecloud.com/ic/api/integration/v1/flows/rest/MES_PROD_SCHEDULE/1.0';
const jobData = {
  scheduleId: $scheduleId,
  planningDate: $planningDate,
  workOrders: $workOrders
};
// Invoke using authenticated REST call

MES Endpoint Connectivity: Configure the on-premise MES connection in Integration Cloud:

  1. Create a REST adapter connection for your MES system
  2. Select “On-Premises” as the connection type
  3. Choose your Connectivity Agent from the agent group dropdown
  4. Configure MES endpoint details (URL, authentication, headers)
  5. Test the connection - it should route through the agent to reach MES

In your integration flow:

  • Map the manufacturing planning data to MES expected format
  • Use the agent-enabled REST connection to invoke MES API
  • Add error handling for MES connectivity failures
  • Implement retry logic for transient network issues

Common gotcha in 23c: The business event subscription doesn’t work reliably if the planning job runs in a different pod than the event publisher. Apply patch 35789432 to fix event delivery issues in distributed environments.

After implementing this pattern, your manufacturing planning jobs will automatically trigger MES updates through the Connectivity Agent whenever schedules are generated. Monitor the Integration Cloud activity stream to verify successful MES updates after each planning job execution.

3

I checked and the integration is using a REST trigger, not scheduled parameters. Should I recreate the integration with a different trigger type? Also, how do I configure the manufacturing planning job to actually call this integration? The documentation mentions using callback URLs but doesn’t provide specific steps for MES integration scenarios.

4

The issue is likely that your scheduled job isn’t configured to invoke the integration endpoint. In manufacturing planning, you need to add a custom job parameter that triggers the Integration Cloud flow. Go to Scheduled Processes > Process Details and add a parameter for INTEGRATION_ENDPOINT with value pointing to your MES integration. Without this explicit parameter, the job completes internally but doesn’t fire the external integration trigger.