Maintain the Search Data Up to Date
For most modules in SCM, after the functional indexes are created, to ensure that your data remains up to date in your search system, the ESS job to run Bulk ingest to OSCS scheduled process runs in the background automatically as part of your application.
This process doesn't clear the index, but only updates the existing index with the changes from any recent create or update transactions.
However, for certain modules, you must run module-specific bulk ingest jobs as listed below:
| Product | Job Name | Usage |
|---|---|---|
| Receiving | Ingest Receiving Search Indexes | Ingest receipts performed outside of the Responsive Self-Service Receiving application. |
| Order Management | Update Sales Order Search Indexes | Keeps your sales order data synchronized between Oracle Order Management and Oracle search systems. |
| Self Service Procurement | ESS job to run Bulk ingest to OSCS Note: Set the value of the Program Name to run Bulk Ingest parameter to prc_por_downstream. |
Ensures that all the requisition lines display the accurate status owing to downstream events postapproval. |
Supply Chain Planning (fa-scm-msc-plan-members and
fa-scm-msc-supplies-demands indexes) |
Don't run any scheduled process. Instead, run the related supply plan or replenishment plan for these indexes. |
Refreshes the |
Except for Supply Chain Planning, it is recommended that you run these jobs at least once a day or as often as your business requires (for example, every 30 mins or an hour) to keep the index current.