🆃🅴🅲🅷 🆂🅾🆄🅻 🆅🅸🅱🅴🆂 🌈: How to Bypass Sourcing or Scheduling in Sterling OMS

How to Bypass Sourcing or Scheduling in Sterling OMS

Are you struggling with Sterling OMS sourcing and scheduling during special order scenarios like pre-orders, backorders, or dropshipping?

You're not alone.

In this post, I'll walk you through practical methods to bypass sourcing and scheduling in IBM Sterling Order Management System (OMS). These tips are especially useful in cases where flexibility is more important than real-time inventory validation.

🤔 Why Would You Bypass Sourcing or Scheduling?

Have you ever needed to skip sourcing or scheduling for a custom or exception-based order flow?

                    Common scenarios include:
                    Pre-orders or backorders
Dropshipping from external vendors
Manual or offline fulfillment
External warehouse integration
Development or testing environments

                

🔧 Methods to Bypass Sourcing or Scheduling in IBM Sterling OMS

✅ 1. Use Standard Flags in API Input

Bypass Scheduling:

ignoreSchedulingRules="Y"

Bypass Availability Check (Sourcing):

ignoreAvailabilityCheck="Y"

These are official Sterling OMS flags, supported in APIs like createOrder and scheduleOrder.

When to use:

When fulfillment is handled externally or manually
When Sterling shouldn't override external availability
During system integration, testing, or POCs

✅ 2. Customize Sourcing Rule Logic

Want to avoid sourcing for specific items or fulfillment paths?

Use exception-based conditions in sourcing rules
Create dummy sourcing rules (e.g., with zero priority or no eligible nodes)

Ask yourself: Can sourcing be bypassed based on item type, node, or order type?

✅ 3. Use Scheduling Overrides or Service Definitions

Within custom flows or user exits, you can manipulate scheduling logic like this:

// Custom scheduling override logic
if (orderType.equals("EXTERNAL_FULFILLMENT")) {
    skipScheduling = true;
}
                    

This allows more dynamic behavior depending on order contents or conditions.

✅ 4. Skip Steps via Custom Transaction Flows (User Exits)

Use YFSCreateOrderUE or other exits to control logic dynamically.

Examples:

Skip scheduling for certain order types
Bypass sourcing for items flagged as "external fulfillment"

✅ 5. Use Scheduling APIs With Flags

If you manually call scheduling APIs, just pass the flags:

scheduleOrder with ignoreSchedulingRules="Y"
findInventory with adjusted node priorities or dummy sourcing behavior

✅ 6. Configure Order-Type Specific Logic

Use order type configurations to:

Bypass sourcing and scheduling for specific flows
Redirect fulfillment to external services or manual steps
Avoid unnecessary ATP checks

🧪 Sample createOrder Input (Bypassing Sourcing & Scheduling)

Here's a sample XML you can use:

<Order ignoreSchedulingRules="Y" ignoreAvailabilityCheck="Y">
    <OrderLines>
        <OrderLine>
            <Item ItemID="SAMPLE_ITEM"/>
            <OrderedQty Quantity="1"/>
        </OrderLine>
    </OrderLines>
</Order>
                

                    🔍 Key Flags Used:
                    ignoreSchedulingRules="Y" → skips scheduling logic
ignoreAvailabilityCheck="Y" → skips sourcing/ATP check

                

⚠️ Important Notes

Bypassing sourcing or scheduling should be done carefully, as it may affect:

Inventory allocation
Promising logic
Fulfillment timelines

These techniques are best used for:

Pre-booking/pre-sale models
Manual fulfillment
Integrations with third-party logistics

⚠️ Caution: Use With Purpose

Bypassing these steps removes standard checks from the flow. Make sure your downstream processes handle:

Inventory allocation
Delivery date estimation
Fulfillment accuracy

✅ Best used in:

Pre-booking and pre-sales campaigns
External partner fulfillment
Order orchestration with advanced customization

🙋♂️ Let's Discuss!

Have you used these techniques in your OMS environment?

What challenges did you face customizing scheduling or sourcing?
Are there unique flows where you had to bypass these steps?

👉 Share your experiences or questions in the comments below!

💬 Found This Helpful?

If this helped you:

Leave a comment with your thoughts or tips
Share the post with your team or network
Follow the blog for more IBM Sterling OMS content and tech tips

Thanks for reading and supporting the community! 🙏

📢 Want More?

Would you like a deep-dive post on:

Custom User Exits for Order Processing?
Pipeline configuration for sourcing logic?

Let me know in the comments, and I'll create a follow-up!

📢 Bonus Tip:

If you want a deep-dive post on custom User Exits or pipeline-based sourcing control, let me know in the comments!

🆃🅴🅲🅷 🆂🅾🆄🅻 🆅🅸🅱🅴🆂 🌈

Pages

Monday, May 26, 2025