Significance of Performing Initial
Ingest in Redwood Receiving Process
Performing an initial ingest in the Redwood Receiving process builds the
essential search indexes for the Oracle Search Cloud Service (OSCS).
It is a vital prerequisite that translates existing back-end data into a format
the modernized, search-driven Redwood pages require to function properly.
Initial Ingest is a one-time (or sometimes occasional) data
synchronization process that populates Redwood Receiving with all eligible open
receipt transactions. It improves performance, enables faster searches,
validates receipt eligibility, and provides the data foundation required for
the modern Redwood Receiving experience in Oracle Fusion.
Key Significance:
Initial Ingest is effectively the "data preparation" step that
allows the Redwood Receiving pages to function efficiently.
Without the ingest, newly created or updated purchasing documents may
not immediately appear in the Redwood Receiving workbench.
- Mandatory
Prerequisite: The new Redwood Self-Service Receiving and
Expected Shipment Lines pages depend entirely on OSCS. Without this
initial step, the pages will appear blank or fail to populate
expected receipts.
- Centralizes
Expected Deliveries: The process gathers and synchronizes
expected receipts across multiple channels, specifically pulling in:
o
Purchase orders
o
Transfer orders
o
Advanced Shipment Notices (ASNs)
o
Return Material Authorizations (RMAs)
- Enables
Global Search: It indexes back-end data so users can leverage
the advanced, type-ahead global search features inherent to the Redwood UI.
When is Initial Ingest Required?
Initial Ingest is typically required:
·
During the first-time setup of Redwood Receiving.
·
After enabling the Redwood Receiving experience.
·
To populate the initial backlog of expected receipts.
·
Whenever historical open receipts need to be made
available to the Redwood receiving interface.
After the initial load, Oracle generally relies on incremental
synchronization so that newly created or updated purchasing documents become
available without requiring another full ingest, depending on the environment
configuration and scheduled synchronization processes.
How to Perform the Ingest?
To generate the index and populate it with data, administrators must run
a specific scheduled process:
A. ESS job to create index definition and perform
initial ingest to OSCS.
1. Log into the
application and navigate to the Tools > Scheduled Processes
menu.
2. Click Schedule
New Process.
3. Search for
the process name: ESS job to create index definition and perform initial
ingest to OSCS.
4. Specify the
required index name in the parameters. Leaving this blank will process all
predefined indexes.
Parameter
values for index name to reingest:
· fa-scm-rcv-expected-po-receipts
· fa-scm-rcv-expected-asn-receipts
· fa-scm-rcv-expected-to-receipts
· fa-scm-rcv-expected-rma-receipts
· fa-scm-rcv-transactions
5. The indexing
job needs to be executed only once during the transition from the classical UI
to the Redwood UI. However, there are several scenarios where re-indexing is
still required.
Once the initial ingest is complete, subsequent receipts processed
through the standard application will ingest automatically, though periodic
bulk runs can be scheduled to maintain data sync.
B. Ingest Receiving Search Indexes:
This
ESS job is needed to ingest receipts performed outside of the Responsive
Self-Service Receiving application.
1. Navigate to
the Tools > Scheduled Processes menu.
2. Click Schedule
New Process.
3. Search for
the process name: Ingest Receiving Search Indexes.
4. The purpose
of the schedule process is to ingest all inbound documents and receiving
transactions that were created outside of Redwood Receiving pages since the
last time this job ran.
5. This job
should be scheduled to run periodically.
6. It's
recommended to schedule this process to run every 30 minutes but can be
scheduled to run more frequent as well.
Important Note:
As part of the transition from the classical Receiving pages to the
Redwood Receiving experience, the initial search indexing process is
expected to be executed only once to populate the Redwood search index with
existing eligible receiving data.
However, there are scenarios in which the search index may require
re-ingestion after the initial migration. These scenarios include, but are not
limited to:
·
Objects created through web service integrations.
·
Objects created using the legacy classical user
interface.
·
Objects created or updated by other SCM applications
or background processes.
·
Data synchronization issues resulting from product
defects or exceptional processing conditions.
When re-indexing is required, run the Ingest Receiving Search Index
ESS job. This job replaces the legacy class-based indexing ESS job for the
Redwood Receiving experience and should be used to refresh the Redwood search
index whenever eligible receiving transactions are not available through the
Redwood Receiving pages.
