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
- Load & Sync
- Call Center
- Web Store
|1||Web Server||Used for deploying WAR or EAR file. Web Server can be configured as cluster server. Example : Weblogic / JBoss / Web Sphere|
|2||Agent Server||Background java Process running with own JVM used for processing tasks which does not need manual intervention.
a) Task Q Based ( Schedule Agent)
2) Non Task Q Based (inbox purge)
|3||Integration Server||Configured under Service Definition Framework (SDF)
Used for external integration
All the Async services are configured with Integration Server
Example : LoadSync
|4||Standard API||All the API given out of the box (OOB) called as standard API
Example : createOrder
|5||Extended Service||Service 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|
|6||Extended Database Service||Service created with API component using Extended Database service. Mainly used when custom table created with API Required flag as Y.|
|7||Service||Service 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
|8||Transaction||For 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
|9||CDT||Configuration Deployment Tool|
|10||OOB||Out 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.
|11||Load & Sync||The process of loading inventory from external/backend system to OMS. Effective way of loading inventory into OMS.|
|12||RTAM||Real Time Availability Monitor
Process of reporting OMS inventory picture to external order capture systems.
a) Activity Based - yfs_inventory_activity
b) Delta Sync - yfs_inventory_alerts
c) Full Sync - yfs_inventory_item
|13||GIV||Global 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
When you purchase an product and return this module comes handy.
|15||User Exit||User 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.|
|16||Call Center||Module/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
|17||Web Store||Module/Add-on written on top of OMS to help store users. This is web based application with customization. Used for store activities
|18||SBC||Sterling Business Center
This is web based application created for managing the business configuration.
Module which helps to maintain product/item information. Product information will be loaded from backend MDM (Master Data Management) system using ASync Integration Server.
|20||Sourcing||Process of identifying store/warehouse from which product can be shipped from. Factors which affects sourcing
Requested Delivery Date
Shift End Time
Carrier Pickup Time
and many more
If you have any question or suggestion please email to : firstname.lastname@example.org
Happy Learning !!!