Incoming Customer Order in Cloud

Hi ​@TecSoniaG ,

If your XML is reaching IFS Cloud and an Application Message is created, but it is not processed further, then the issue is typically in the IFS Connect / message processing pipeline after reception.

 What your situation tells us

• ✔️ Projection SalesMessageService.ReceiveCustomerOrder is working
• ✔️ Message is received and stored (Application Message created)
• ❌ Processing is NOT happening

 So the problem is NOT inbound communication, but post-receipt processing

 What to Check (Step-by-step)

 1. Application Message Status

Go to:
Application Messages

Check:

• Status:
  • Received
  • Waiting
  • Failed
  • Processed

 If stuck in:

• Received / Waiting → routing/processing issue
• Failed → check error details

 2. Routing Rules (IMPORTANT)

Go to:
IFS Connect → Routing Rules

Check:

• Route exists for:
  • Message Type = Customer Order
• Condition matches your XML
• Destination is correct

 If no matching route → message will stay unprocessed

 3. Queue Configuration

From your setup:

• Check queue (e.g., IN1, DEFAULT, etc.)

Go to:
IFS Connect → Queues

Verify:

• Queue is:
  • Started / Active
• No backlog / stuck messages

 If queue is stopped → messages won’t process

 4. Routing Address

Check:
Routing Address

Ensure:

• Destination type is correct:
  • PL/SQL / Projection / Service
• Address is valid

 5. Background Jobs / Message Processor

Check:
Background Jobs / Connect Reader

Ensure:

• Jobs responsible for:
  • Message processing
    are running

 If stopped → no processing

 6. Error Details (Very Important)

Open the Application Message:

• Check:
  • Error text
  • Payload
  • Processing log

 This often directly shows root cause

 Common Causes

• ❌ No matching routing rule
• ❌ Queue not started
• ❌ Incorrect message type
• ❌ Missing processing job
• ❌ Payload structure mismatch

 Quick Test

Try:

• Manually reprocess message
   If it fails → error will show clearly

Can you please clarify, how the projection can process the incoming XML from the application message. What is the correct routing address configuration? What is the required and valid format for the XML.?

​@JohannesWittwer ,

1. How does the projection process incoming XML?

The projection:

SalesMessageService.ReceiveCustomerOrder

is exposed as a service endpoint (SOAP/REST).

When you send XML via:

/int/soapgateway

the flow is:

SOAP Gateway → Application Message → Routing Rule → Routing Address → Projection → Business Logic

 Important:

The projection itself does NOT read directly from Application Message
It is invoked via routing configuration

 2. Correct Routing Address Configuration

For projection-based processing, your Routing Address should NOT be PL/SQL.

 Instead, configure:

• Destination Type: Projection

• Address: Projection name

  SalesMessageService

• Method:

  ReceiveCustomerOrder

 So routing becomes:

Message → Routing Rule → Projection (SalesMessageService.ReceiveCustomerOrder)

 Common mistake (based on earlier setup)

You were using:

Destination Type: PL/SQL ❌

 That bypasses the projection completely

 3. Required XML Format

The XML must match the projection input structure, not a custom format.

 Key points:

• Root element must match expected request
• Structure must follow:
  • Customer order header
  • Order lines
• Field names must match projection schema

Example (simplified)

<CustomerOrder><CustomerId>...</CustomerId><OrderDate>...</OrderDate><OrderLines><OrderLine><PartNo>...</PartNo><Quantity>...</Quantity></OrderLine></OrderLines></CustomerOrder>

 How to get exact XML format

Best way:

 Call metadata:

.../projection/v1/SalesMessageService/$metadata

or:

 Use Swagger / API Explorer

 This gives:

• Exact structure
• Required fields
• Data types

 4. Key Checks

Make sure:

• ✔️ Routing Rule matches message type
• ✔️ Routing Address = Projection
• ✔️ Queue is active
• ✔️ XML matches projection schema

If an Application Message was generated, this means that your file was picked up but failed during routing.  Can you share the error message from your Application Message? 

Is your inbound file an XML or JSON?

Which Cloud release are you using?