Validation rules: CSOS duplicate orders tab
If your user license enables the CSOS functionality, the CSOS duplicate orders tab is displayed.
CSOS duplicate checking is done for CSOS purchase orders your community receives from partners. If the community is a WebTrader sponsor, documents received from its WebTrader partners also are checked. Duplicate checking is not done for orders picked up from integration, unless the community that picks up the order is the named receiver (a rare case).
If your community only sends signed orders but does not receive any, duplicate checking is not applicable and you can ignore this tab.
The target documents are the EDI or XML documents defined on the order identification tab of the identify CSOS purchase orders page.
To configure validation on CSOS duplicate orders, select an option:
- Reject duplicate CSOS purchase orders (default) – Select this option if you want Activator to check whether an order duplicates a previously received order in the following ways:
- Duplicate order number
- Duplicate DEA registration number
- Duplicate sender name
- Duplicate receiver name
- If all of these values are the same as those in a previously received order, the document is given a failed status. You can search for failed documents in Message Tracker.
- If you also have configured Activator to check for duplicate EDI documents, checking for duplicate CSOS orders is performed in addition to the duplicate EDI checking.
- The CSOS duplicate order tabs can be found on two pages in the user interface. One location is the identify CSOS purchase orders page at CSOS > Configure CSOS. The other is the message validation rules page, which is opened by clicking Message validation on the navigation graphic at the top of a community summary page. To configure CSOS duplicate checking, you only need to use one of these pages.
- Allow duplicate CSOS purchase orders – Select this option to let Activator accept duplicate orders.
Whether you choose to reject or accept duplicate CSOS purchase orders, the choice applies to all messages received for the community, unless you define exceptions. You can set up the following exceptions to the message signing option:
- Click Add an exception for a partner to create a partner-specific exception.
- Click Add an exception for a category to create an exception for a partner collaboration category. A collaboration category is a group of partners who have common collaboration settings.
- Click Add an exception for a trading pickup to create an exception for messages received by the community through a specific community trading pickup.
You can add multiple partners, categories or trading pickups to the exceptions lists. Activator applies the opposite of the selected behavior to any partners, collaboration categories, or trading pickups that display in the exceptions lists.
Related topics