The Processing Options panel allows you to automatically control the flow of documents when you send or receive documents and files with your trading partners. This flexibility allows you to tailor the system to your normal business practices, and not vice versa. Inbox settings control what action is taken on a document when it is being placed in your inbox. Outbox settings control what action is taken on a document when it is being placed in your outbox.
Summary of the Actions:
Read more about each Action below.
NOTE regarding FA Monitoring: The example above is typical of the rules you would need to match Functional Acknowledgments to the Purchase Orders and Advanced Ship Notices you send to your trading partners. Should you wish to use our FA Monitor you need to define OUTBOX rules similar to what you see above for the transactions sets you need to monitor.
If for example you wish for all Functional Acknowledgments [997s] both sent to TP Mailboxes and received from them to be put on hold, you will need two rules; an Outbox rule and Inbox rule.
Note: 'All' can be used for most actions, the exception being 'Immediate'. The 'Immediate' action can only be defined for a specific TP Mailbox to override another rule defined to 'All'.
This field would usually be either a valid X.12 or EDIFACT set type. However since any data format can be sent through the service more flexibility is allowed; use the doc-type/set-type of the transaction that needs special processing as it is displayed in the Document Manger here. Enter a document type (or 'All') when adding or modifying an automatic document processing option.
Select an action when adding or modifying an automatic document processing option.
Immediate is the default action and should only be used as an exception to counteract other actions for specific trading partners. Please note, 'Immediate' cannot be added with the trading partner 'All'. For example, in the above figure on the inbox side, all 852s from all trading partners will be placed on hold except those from ZZ:ICCTEST, which will be processed normally, that is, immediately. Furthermore, on the outbox side, only 837s to ZZ:ICCDH2 will be delivered immediately. All other 837s will be placed on hold and will need to be manually released via the applet to your trading partners.
Hold prevents your trading partner(s) from seeing and downloading the documents you are sending to them (outbox) or prevents you from downloading documents received from your trading partner(s) into your business systems (inbox). All documents held in your mailboxes must be manually released. For example, in the above figure, all 852s from all trading partners will be placed on hold when received into the inbox. This prevents 852s from all trading partners from being downloaded (with the exception of ZZ:ICCTEST, see Immediate above). Furthermore, when any 837s are uploaded for delivery to any trading partner (with the exception of ZZ:ICCDH2, see Immediate above) they will be held in the outbox and not delivered until manually released.
Trash causes any documents of the indicated type from/to the indicated trading partner to be placed in the trash. For example, in the above figure, all 997s for all trading partners on both the inbox and outbox will be placed in the trash.
No Translate (no translation) causes any documents of the indicated type from/to the indicated trading partner to not be translated. This only applies if this mailbox has translation turned on. For example, in the above figure, any 850s sent to any trading partner will not be translate. The trading partner will receive the document in the same format it was sent. Furthermore, on the inbox side, any 837s received from any trading partner will not be translated.
Archive causes any documents of the indicated type from the indicated trading partner to be placed in the archive and therefore available for download only from the inbox archive. For example, in the above figure, all 856s from ZZ:ICCTEST will be automatically placed in the archive. The archive options is not available on the outbox side since documents are, by default, archived on the outbox side as soon as they are delivered to the inbox.
Translate (translation) causes any documents of the indicated type from/to the indicated trading partner to be translated. This only applies if this mailbox has translation turned off. For example, in the above figure, any 836s sent to any trading partner will be translate. The trading partner will receive the document in the post translated format. Furthermore, on the inbox side, any 836s received from any trading partner will be translated. Note: Special processing is required for this service. Please contact support team for system configuration.
Track (translation) causes any documents of the indicated type from/to the indicated trading partner to be set to our value added processing service. This only applies to the direction indicated and needs to be set for both inbound and outbound documents. For example, in the above figure, Any 856 sent will be sent to the tracking service. Any 997s sent from any trading partner will be sent to our tracking service (as well as going to the trash per the trash processing option). The 997's will be matched up to the original 856 and will populate the acknowledged field in the document manager with the time that the 997 was received. Note: Special processing is required for this service. Please contact support team for system configuration.
Immediate FA (Applies to translated files only) causes any 997 documents of the indicated type from/to the indicated trading partner to be translated. This only applies if this mailbox has translation turned off. For example, in the above figure, any 852s sent to any trading partner will be translate. The trading partner will receive the document in the post translated format. Note: Special processing is required for this service. Please contact support team for system configuration.
Pending changes are marked with a red triangle in the upper left-hand corner of any cell with changes; aka the cell and row it is in is "dirty".
IMPORTANT: You must click either "Commit Edits" or "Cancel Edits" if any cell in the grid is marked as "dirty" before you can go to another application window.
For the example above, the rule highlighted in the grid is the only one defined in the service; all the other rules were just added to the grid, but not yet committed.
The expected result of clicking Commit Edits is that all the new records will be dropped, as they are either duplicates, contradictory, or redundant.
Duplicate rules are self-explanitory. In the example, the newly added record with Outbox + ZZ:ICCDH2 + All + Track is a duplicate of the existing rule highlighted.
Redundant rules are those rules defined for a specific TP Mailbox, when another rule is defined for the same direction + doc-type + action and the trading partner is 'All'. That is, if any trading partner is on the list with the document type and action when 'All' is added as the trading partner or doc-type, the rules defined for specific trading partners will be removed from the list and be replaced by the 'All' rule. In the example, the newly added rule for Outbox + ZZ:ICCDH2 + 850 + Track is redundant to the existing rule highlighted.
Contradictory rules are those where the opposite action is requested for the same direction plus TP Mailbox plus doc-type. In the example, the top two rows contradict one another where the actions selected are Translated and No Translate.
As expected, the only record that remains in the example is the original record. The remainder of the records were dropped.
The response returns a formatted message for every rule that failed validation and was skipped. Note that validation messages may be repeated. In the example of the last two images, four records were dropped however there are five messages. There were five records total. The reason a valid record is maintained but a different record is dropped is also noted for the record that is maintained.
If an update action completes with some of the rules skipped from validation failure, the form displays a button titled "View Update Errors". Clicking it will redisplay the last set of validation errors. The button will remain visible until an update is performed where all records pass validation and are committed to the service.