Sterling OMS Common Terminologies

By | 08/18/2018

Sterling OMS Common Terminologies

Sterling OMS Common Terminologies

In this post we are going to learn about few commonly used terminologies. Will be useful for the beginners.

  • Web Server
  • Agent Server
  • Integration Server
  • Standard API
  • Extended Service
  • Extended Database Service
  • Service and Flows
  • Transaction
  • CDT
  • OOB
  • Load & Sync
  • RTAM
  • GIV
  • RL
  • UserExit
  • Call Center
  • Web Store
  • SBC
  • CM
  • Sourcing
1Web ServerUsed for deploying WAR or EAR file. Web Server can be configured as cluster server. Example : Weblogic / JBoss / Web Sphere
2Agent ServerBackground java Process running with own JVM used for processing tasks which does not need manual intervention.
2 Types
a) Task Q Based ( Schedule Agent)
2) Non Task Q Based (inbox purge)
3Integration ServerConfigured under Service Definition Framework (SDF)
Used for external integration
All the Async services are configured with Integration Server
Example : LoadSync
4Standard APIAll the API given out of the box (OOB) called as standard API
Example : createOrder
5Extended ServiceService created with API component using Extended Service option. User has to give full path of Java Class Name and method name when this option selected
6Extended Database ServiceService created with API component using Extended Database service. Mainly used when custom table created with API Required flag as Y.
7ServiceService can be configured under Service Def Framework (SDF).
2 type of service
1) Sync Service : Returns response immediately
2) Async Service : Reads message from database or queue or file (Async component) and process. Mainly used for external integration
8TransactionFor every activity there will be defined transaction.
Transactions can have pickup and drop status
Can be derived from base transaction
For Example : createOrder API is associated with CREATE_ORDER transaction
9CDTConfiguration Deployment Tool
10OOBOut of the box
This is commonly used word in Sterling OMS. Any service/api given by product with out any change called as out of the box.
11Load & SyncThe process of loading inventory from external/backend system to OMS. Effective way of loading inventory into OMS.
12RTAMReal Time Availability Monitor
Process of reporting OMS inventory picture to external order capture systems.
3 Types
a) Activity Based - yfs_inventory_activity
b) Delta Sync - yfs_inventory_alerts
c) Full Sync - yfs_inventory_item
13GIVGlobal Inventory Visibility
This is one of core module of OMS. This module can show inventory for particular item at country level / state level / Distribution Group level. Makes it more powerful from inventory point of view
14RLReverse Logistics
When you purchase an product and return this module comes handy.
15User ExitUser Exit configured under transaction. Allows user to write java code and call before executing the particular api. Used for validating input xml (BeforeCreateOrder) or calling external system to get more information (External Inventory). YFSUserExitException to be used when validation fails.
16Call CenterModule/Add-on written on top of OMS to help customer representative. This is web based application used for most of the activities related to order
Where is my order ?
Creating New order
Cancel line
Cancel order
Change Qty
17Web StoreModule/Add-on written on top of OMS to help store users. This is web based application with customization. Used for store activities
18SBCSterling Business Center
This is web based application created for managing the business configuration.
Item Creation
Catalog Management
19CMCatalog Management

Module which helps to maintain product/item information. Product information will be loaded from backend MDM (Master Data Management) system using ASync Integration Server.
20SourcingProcess of identifying store/warehouse from which product can be shipped from. Factors which affects sourcing
Requested Delivery Date
Warehouse Schedule
Shift End Time
Carrier Pickup Time
and many more

If you have any question or suggestion please email to :

Happy Learning !!!

Register with us to get more updates

Sterling OMS Forum : Ask Questions

Join our channel for updates


11 thoughts on “Sterling OMS Common Terminologies

  1. Ankit

    Could you please define scheduling as well with difference between sourcing and scheduling.


    1. lpsarathy76

      To simply put it, Sourcing is to find where the inventory is available for fulfillment, in a optimal way and Scheduling is to earmark the Inventory to meet the demand. Scheduling process soft-allocates the Inventory, which means, the same inventory can be re-allocated for other demands depending on scenarios.

      Sourcing considers the Requested Shipdate, Customer’s Delivery Location, Fulfilment conditions (Part/full), Lead-time, etc in addition to the optimization parameters such as Date, shipment cost.

      Hope the above clarifies your query.

  2. Sairam

    Can i get any information on Dirty Node configuration.
    Ex: Once an order from a node is back-ordered, then how to mark that Node as Dirty node so that no orders will be scheduled to that Node until we remove it from Dirty Node.

    1. admin Post author

      There could be different option to do this. But in my view we can write custom code which deactive the node when back-order happens. yfs_ship_node has active_flag. if we set active_flag= false node considered not available. Still looking for more options ….

      1. Satheeshkumar Thangaraj

        Another alternative (standard way to do it at an item level I suppose) it to do it via Inventory node control.

        Example Scenario: An item in an order is released to a store which had inventory available in system. But when the store associate try to pick the order , he realizes that there is no real/physical inventory in the store. He will have no other choice but to null pick the item. In this case, the node in question (i.e., the store) should be marked as dirty for this item and no more order should be sourced/released to this store.

        To achieve this, manageInventoryNodeControl API can be used which sets a configurable time in future until which the node remains dirty for the item (won’t be considered for sourcing that item) . YFS_INVENTORY_NODE_CONTROL.INV_PIC_CORRECT_TILL_DATE has this information.

        Whenever a inventory adjustment happens for the item on that dirty node, the time stamp (INV_PIC_CORRECT_TILL_DATE ) can be reset to clear the dirty node. For this, in adjustInventory input, RemoveInventoryNodeControl should be passed as Y.

  3. Ravi Ranjan

    Order sourcing process finds the optimal node from which order can be sourced; whereas scheduling determines when the order can be shipped or delivered. Order release process releases the order to warehouse management application in order to allow its processing in warehouse. In other words, order release process transfers order control from order management system to warehouse management system. Hence, timing the release process astutely, is extremely important. A mistimed release process can lead to undesirable outcomes and may prevent realization full OMS implementation benefits.


Leave a Reply

Your email address will not be published. Required fields are marked *