Purge Duplicate Resolution Data
Use the Purge Duplicate Resolution Data scheduled process to purge duplicate resolution data, such as resolution logs and legacy duplicate resolution batches and requests.
When to Use
- Purges duplicate resolution data based on status and date range.
- You can specify the status of the duplicate resolution requests to be purged, such as duplicate resolution requests in Completed, Error, Pending, New, or Rejected status. You can also specify a date range by specifying the start and an end date to select duplicate resolution requests to be purged.
Privileges Required
Verify that you have the following privilege or role:
-
Privileges
- ZCH_REJECT_TRADING_COMMUNITY_DUPLICATE_RESOLUTION_REQUEST_PRIV
- Roles
- Master Data Management Application Administrator
Before You Start
Review the following before scheduling this scheduled process:
-
Compatibility:
-
This scheduled process is incompatible with Request Dispatch job.
- This scheduled process is self incompatible, which means that multiple purge resolution request jobs can't be run at the same time.
-
Parameters
Parameter |
Optional or Mandatory |
Description |
Parameter Values |
Special Combinations |
Notes |
---|---|---|---|---|---|
Purge Request Start Date |
Mandatory |
Specifies the start of the date range when duplicate resolutio requests were created. |
Any date. |
None |
None |
Purge Request End Date |
Mandatory |
Specifies the end of the date range when duplicate resolutio requests were created. |
Any date after the specified start date. |
None |
None |
Resolution Request Status |
Optional |
The status of the duplicate resolution requests that must be purged. |
All, All active, All inactive, Completed, Rejected, Errored, New, Pending |
None |
|
Duplicate Identification Batch |
Optional |
The batch ID of the duplicate resolution requests that must be purged. |
Any batch ID |
None |
None |