What's New
5/4/2012
ICBS BR 1.3.0.5 was successfully deployed on Monday April 23rd
- This Business Release includes two changes. Neither change requires any change in how the ICBS user interacts with the ICBS application:
- On ICBS-initiated orders in which no default financial code has been designated in ROSS, the interface was preventing ICBS from sending the create/fill message to ROSS. It was also preventing any further orders to be processed against the incident. This has been fixed
- This change puts in place a purging schedule for audit data. Any audit data older than 3 years will be purged for the following audits:
- Inventory Audit
- Item Audit
- Organization audit
- The final version of the release notes is posted on the “User Support & Quick Reference Guides” page (see list of links at left)
- The next ICBS deployment is tentatively scheduled for early July
User Tip: ROSS-ICBS interface problem with the “¿” special character
- This bug, uncovered during the 2011 field season, is once again creating problems for users. ICBS users can keep this in mind if ROSS users have placed requests to the cache and the user can’t see the items in ICBS:
- When a space dash space (“ – “) are copied from a Microsoft Word document and pasted into the ROSS Shipping Instructions or Special Needs fields, ICBS users are unable to view the items requested
- ROSS users should avoid copying this combination into these ROSS fields
- When this happens, an inverted question mark (¿) appears in the Shipping Instructions in ICBS where the space dash space was copied
For example, this set of Shipping Instructions in ROSS:
TO APACHE PASS ROAD - ENTRANCE TO FORT
appears like this in ICBS:
TO APACHE PASS ROAD ¿ ENTRANCE TO FORT
This will result in the ICBS user being unable to view the requests.
- Work-around: If the ICBS user encounters this problem, they should contact the ROSS user and have them retrieve the request, remove those characters (it might be advisable for the ROSS user to type in the desired text, or copy it from a WordPad file) and re-place the request with the cache.

