Process Pending and In-Error Genealogy and Installed Base Transactions
Use this scheduled process to perform various data processing and reprocessing tasks.
The tasks the process performs include:
- Process pending (or deferred) inventory, manufacturing, installed base, receiving, and order management genealogy and asset tracking transactions or transactions that have failed in the integration process.
- Reprocess fulfillments from an order for debugging and analysis purposes. This ad hoc job processes fulfillments that didn't have the asset management node in the orchestration process.
- Process specific data fixes for any known generic problems that were encountered in the past.
You can access this process from the Scheduled Processes work area.
When to Use
If previous runs of genealogy data capture fail due to errors, then you can reprocess them after the setup data has been fixed.
To defer certain transaction until this process is run, then there are a couple of profile options that will put source application transactions in a deferred processing mode, regarding genealogy and asset updates. These are the profile options.
- ORA_WIE_DEFER_GENEALOGY_BUILD - Genealogy Build Deferred During Execution.
- This profile defers all the manufacturing and maintenance execution transactions to Genealogy and Asset.
- ORA_CSE_IB_INTERFACE_DEFERRED - Installed Base Asset Interface Deferred.
- This profile defers all updates to Genealogy and Asset from source application transactions.
If a unique sales order requires reprocessing due to failure, setup, or data issues.
If a customer requires a specific data fix that could apply to other customers in the future, then it is added as a capability of this process.
Privileges Required
- Process Product Genealogy Transactions (CSE_PROCESS_PRODUCT_GENEALOGY_TRANSACTIONS_PRIV)
Specifications
Use these specifications when you run the scheduled process.
Specification | Description |
---|---|
Job Type | Run at any time as an ad hoc job. |
Frequency | As needed to reprocess the transactions, sales orders, or data fixes. |
Time of Day | Any time. |
Duration | Typically, it will take several minutes, depending on the volume of data being processed. |
Compatibility | There should be only one instance of the job running at any one time. |
Parameters
You must define at least a range of Work Order numbers or dates to process the report.
Parameter | Optional or Required | Description | Parameter Value | Special Combinations Required |
---|---|---|---|---|
Resubmit | Optional |
The resubmit drop-down provides three different processing options:
|
The LOV will provide the three options. | If the option Pending and failed transactions is selected, then
it can also be combined with the checkbox to Ignore Failed
Transactions, thus only processing Pending transactions. If the option Sales order by Number is selected, you must define the number. |
Sales Order Number | Conditional | The number of the sales order that requires reprocessing. | The Sales Order Number LOV will provide a list of sales order numbers | None |
Ignore Failed Transactions | Conditional | Check box option to ignore all failed transactions and only process the pending transactions that are in a deferred state. | The option can be selected. The default value is No. | None |
Troubleshooting Information
- Once submitted, you can view the status of the process in the Scheduled Processes work area. A successfully completed process, as well as any child processes, will end in Succeeded status.
- If issues are encountered, the process or any of its subprocesses may be Warning or Error. The specific validation errors and warning messages that prevented the process from completing successfully are displayed in the error log(s).
- Any interactive warning validations are NOT performed.
- When the process is submitted, you can Resubmit, Put on Hold, Cancel Process, Release Process as provided by the Scheduled Processes work area.