Carbon Copy feature of Information Exchange

• EDI carbon copy relationships support partner criteria (X12 and UCS relationships only)
• EDI carbon copy relationships allow the recipient to be determined based on values found in the inner or outer envelope
• Use of BG01 and BG02 elements instead of BG03 and BG04 elements allowed for UCS EDI carbon copy relationships
• EDI carbon copy relationships "last changed" fields added

Information Exchange Administration Services for the Web

• Support for the date format preference found in a user's Information Exchange profile added
• Support for carbon copy partner audits added
• Enhanced support for a user ID of "?" added to list of audit records and list of traces
• Several additional minor enhancements (refer to Description of Changes)

Note: Information Exchange Administration Services for the Web can be reached via the following URL: http://ieas.services.ibm.com/

• Carbon Copy feature of Information Exchange
• Information Exchange Administration Services for the Web

EDI carbon copy relationships support partner criteria (X12 and UCS relationships only)
Prior to this enhancement, EDI carbon copy relationships for X12 and UCS data types could contain only transaction set criteria. A new type of criteria, called partner criteria, has been added.

For both X12 and UCS data types, the values specified for partner criteria are compared to the values in one of the following fields found in the GS segment:

• For receive carbon copy relationships, the "Application sender's code" field is checked
• For send carbon copy relationships, the "Application receiver's code" field is checked.

A relationship may contain transaction criteria or partner criteria, but not both. The data type and partner in the outer envelope of the message must match the data type and partner in the carbon copy relationship before any transaction or partner criteria is checked. If criteria exists for a relationship, it must match the corresponding fields in the data exactly for a carbon copy to occur.

When a message is candidate for carbon copy and a relationship contains partner criteria, each GS segment in the message is checked for the value of the first specified entry in the partner criteria. If no match is found, each GS segment in the message is checked for the value of the second specified entry in the partner criteria. This checking continues until either all values of the specified partner criteria are checked or a match is found. The entries are checked in the exact order entered in the relationship.

Partner criteria is defined by entering Y in the "Specify criteria field" and P in the "Criteria type" field on the Add / Browse/Change a Carbon Copy Relationship panel (M3820). When these values are specified and Enter is pressed, the Add / Change EDI Criteria panel (M3824) is displayed. On the Add / Change EDI Criteria panel (M3824) the user can enter a maximum of 15 characters for each partner criteria for X12 relationships and a maximum of 12 characters for each partner criteria for UCS relationships. The entries are stored and later checked in the order entered.

Once partner criteria has been added to a relationship, the value "P" is displayed in the "Criteria type" field. If a relationship contains transaction criteria, the value "T" is displayed in the "Criteria type" field. For all X12 and UCS relationships containing criteria prior to the implementation of this enhancement, the "Criteria type" field is set to T.

The value in the "Criteria type" field is protected and the criteria contained in a relationship can not be changed from one type of criteria to the other. If a user wishes to remove criteria from a relationship, each value in the partner criteria or transaction criteria must be removed and the relationship saved.

EDI carbon copy relationships allow the recipient to be determined based on values found in the inner or outer envelope
Prior to this enhancement, all four types of EDI carbon copy relationships (EDIFACT, UCS, UN/TDI, X12) required a specific recipient EDI ID to be provided when adding or copying a relationship. A recipient's mailbox ID or alias was also required for routing of the carbon copy.

This enhancement gives the user the ability to define an EDI relationship without naming a specific EDI recipient ID or recipient mailbox. The user must provide an alias table type and table name that will be used to determine the recipient's mailbox. When a message arrives that is a candidate for carbon copy, the receiver's EDI ID from the outer envelope, or from the inner envelope for X12 and UCS relationships that contain partner criteria, is used as an alias name in the alias table provided to resolve to the recipient's mailbox.

The Receiver ID in the outer envelope is used for mailbox resolution for all relationships except X12 and UCS relationships that contain partner criteria. For these relationships, the "Application receiver's code" field from the GS segment that contains the first match for the specified partner criteria will be used for mailbox resolution. This value will also be used for outer envelope and/or inner envelope replacement, if requested. The partner criteria is checked in the order entered in the relationship and must match exactly the contents of the data for a carbon copy to occur.

To use this feature, the "Recipient from header" field must be set to Y in the following situations:

• When adding a relationship on the Work with Carbon Copy Relationships for EDI Data Types panel (M3840)
• When copying a relationship on the Copy a Carbon Copy Relationship panel (M3860).

A relationship cannot be changed to take advantage of this feature. It must be requested at the time the relationship is created.

Note: The Copy a Carbon Copy Relationship panel (M3860) was redesigned to allow for the selection of this option and the specification of either:

• the recipient mailbox when "Recipient from header" is set to N
  or
• the alias table type and table name needed for mailbox resolution when "Recipient from header" is set to Y.

To allow for the new fields on this panel, the "Always purge original msg?" and "Archive original msg?" fields were removed. The value of these fields will be copied from the original relationship to the new relationship. The user can select to change the new relationship once it is added, if the value of these fields needs to be changed.

Use of BG01 and BG02 elements instead of BG03 and BG04 elements allowed for UCS EDI carbon copy relationships
Prior to this enhancement, all partner comparison and outer envelope replacement for UCS EDI carbon copy relationships used the BG03 and BG04 elements of the BG segment. This change gives the user the ability to specify that the BG01 and BG02 elements be used instead.

Using the BG01/BG02 elements, instead of the BG03/BG04 elements, is based on the setting of the "Use alternate element BG01/BG02" field in the carbon copy relationship. This field will only display for UCS EDI relationships on the Add / Browse / Change a Carbon Copy Relationship panel (M3820).

If the "Use alternate element BG01/BG02" field is set to Y:

• For send carbon copy relationships, the BG02 element will be used for partner comparison with the partner specified in the carbon copy relationship
   
• For receive carbon copy relationships, the BG01 element will be used for partner comparison with the partner specified in the carbon copy relationship
   
• For both send and receive carbon copy relationships, if the "Put recipient in outer envelope" field is set to Y, a maximum of 10 characters of the recipient EDI ID will be replaced in the BG02 element.

The maximum length of the BG03 and BG04 elements is 12 characters and the maximum length of the BG01 and BG02 elements is 10 characters. When the "Use alternate element BG01/BG02" field is set to Y, the following rules apply:

• If more than 10 characters are specified for the partner, recipient, or both, only the first 10 characters will be used for comparison and outer envelope replacement, if requested.
   
• If more than 10 characters are specified for partner criteria, only the first 10 characters will be used for outer envelope replacement. The entire specified partner criteria will be used for inner envelope replacement.
   
• If "Resolve from header" is set to Y and partner criteria exists, the value of the application receiver's code from the GS that matches the criteria will be used as the alias name in the specified alias table to determine the recipient's mailbox. If this field is greater than 10 characters, the entire value from the GS will be used for resolution even though only the first 10 characters will be used for replacement in the BG02 element.

For all UCS relationships existing prior to the implementation of this enhancement, the "Use alternate element BG01/BG02" is set to N. A relationship can be changed to take advantage of this feature.

EDI carbon copy relationships "last changed" fields added
Two new fields have been added to the following panels:

• Browse/Change a Carbon Copy Relationship (M3820) - EDI data types
• Browse/Change a Carbon Copy Relationship (M3822) - All data types.

These fields are "display only" fields and are named "Last changed on" and "Last changed by".

The value of the "Last changed on" field will be adjusted to the date format preference found in the user's Information Exchange profile. The field will contain either:

• The date the carbon copy relationship was last changed
• The date the carbon copy relationship was added, if the relationship has not been changed since it was added.

The value of the "Last changed by" field will contain one of the following:

• The last user to change the carbon copy relationship
• The user that added the carbon copy relationship, if the relationship has not been changed since it was added and it was added after implementation of this enhancement
• "** Not available **", if the relationship was added before implementation of this enhancement and has not been changed since implementation of this enhancement.

http://ieas.services.ibm.com/

Support for the date format preference found in a user's Information Exchange profile added
Prior to this enhancement, input dates on search pages were always in the format DD / MM / YYYY and display dates (list pages, information pages, etc.) were always in the format YYYY / MM / DD. This enhancement allows for all dates to be entered and displayed based on the value found in the date format field of the user's Information Exchange profile.

Support for carbon copy partner audits added
In addition to listing inbound and outbound audits, users can now list carbon copy partner audits as well. An option has been added to the Audits menu page to List Carbon Copy Partner Audits. An associated search page has also been added.

Enhanced support for a user ID of "?" added to list of audit records and list of trace records
A user with service administrator authority has the ability to list any of the three types of audit records (inbound, outbound, carbon copy partner) or session trace records for all users in their account by specifying a "?" in the user ID field of the appropriate search criteria page. Prior to this enhancement, the records for all users in the account were displayed, but the user ID of the record owner was not shown on the list page. With this enhancement, the format of the list was changed so that the resulting list is displayed with the user ID of the user whose audit or trace records follow. After all the records for a user have been displayed, the user ID of the next user in the account with qualifying records is displayed followed by all the audit or trace records for that user.

Show current search criteria on all menu pages
Prior to this enhancement, the name of each search criteria field was displayed on each of the main menu pages but only one field's value was displayed at a time in a box above the search field names. Each of the main menu pages have been enhanced to show the value for each of the search criteria field immediately to the right of the field name.

No longer show message in the process of being received on the List Outbox page
Prior to this change, messages in the process of being received were visible via the List Outbox page. These messages will no longer be displayed in the list, making this function consistent with the existing Information Exchange Administration Services List Outbound Messages panel.

Addition of processing confirmation pages to the add a trading partner and update a trading partner functions
Prior to this enhancement, when a trading partner entry was added or updated, the list of trading partners with the new or updated entry was displayed upon completion of the action. With this enhancement, a processing confirmation page is displayed upon completion of the add or update.

Split the search page for the list alias tables and view an alias table functions into two search pages
Prior to this enhancement, the search criteria for the List alias tables and View an alias table functions was on one page with instructions for the user as to which fields were required for each of the two functions. With this enhancement, the search page was split into two separate pages. No change to function has been implemented, just a simplification of presentation to the end user.

Reset session removed from the Password menu
Prior to this enhancement, the reset session function was available from both the Session menu and the Password menu. The option was removed from the Password menu and is now only available from the Session menu.

Minor changes made to improve consistency and usability
Several minor changes have been made to many of the application pages. The changes listed below are all cosmetic in nature. These changes do not affect the function of the pages.

• Several functions contained the same information with different field names or labels. Many field names / labels on several Web pages have been renamed to improve consistency between functions.
   
• Many field names have been changed to more accurately represent the field contents. For example, on the List Traces page, the column title "Function" has been changed to "Trace type".
   
• The wording of some menu options has been changed to add clarity to the function being performed. For example, "Show Inbox" is now "List Inbox".
   
• The labels of many buttons have been changed from "OK" to values such as "Update", "Add", or "Retrieve", which more accurately represent the function being performed.