The following scenarios are examples of when you might use each of the group edit options.
After reviewing a sample of the specific errors, you realize that your EDI map has generated a series of update actions for items that do not currently exist in Catalogue. You decide to set all actions (regardless of their current action) to add.
|
3
|
Click Save. A success message displays the number of rows that were changed.
|
After reviewing a sample of the specific errors, you realize that all instances of particular action code need to be set to a different action code. You decide that all of the updates need to be adds while the deletes need to remain unchanged.
|
2
|
From the Replace action drop-down list, select Update.
|
|
3
|
From the with action drop-down list, select Add.
|
|
4
|
Click Save. A success message displays the number of rows that were changed.
|
After reviewing a sample of the specific errors, you realize that the same attribute value is in error across all functions within the error document.
In most cases, it is preferable to edit the source data (for example, the item master) used to generate the batch file that you load into Catalogue. However, there may be instances where you need to temporarily fix data already pending at OpenText so that the data being sent to your trading partner is not delayed.
For example, if the country code for the Country of Origin attribute is incorrect in your EDI map, you can change the current value within Error Processing.
|
2
|
From the Attribute drop-down list, select Country of Origin.
|
|
6
|
Click Save. A success message displays the number of rows that were changed.
|
OpenText Active Catalogue Browser Interface User Guide for Vendors PDF
