Lawson and EPIC Optestia

We have an SQL going through our IT JAMS (no idea what that is - they make things talk to each other! ). We have a query running to calculate actual cost per EA based on the buy cost of PO25.6 and that's what's populating Optime and Epic's EAP looks at it as well. Same process is going to feed Epic's Cupid and Radiant eventually.

We've noticed the same thing here with our Cerner item master interface. We are using IC527, but I wrote a Perl script to take that file that IC527 produces and manipulate the cost and put it back in the correct location.
Contact me off-line if you'd like more details. I'd be happy to share my Perl script as well, so you'd have a place to look anyway!

We use a customized IC527 for our interface to Optime. It was a little painful at first to get the cost correct, but after many cases with Lawson, it is working correctly. That was not the part we customized. I will look back at my notes and see if I can find the details. It had to do with certain forms having to be populated.

Thank you Kat ! I wrote a SQL query that captures all the data they would like however they need an incremental running every hour and I am struggling with the numeric "Time" field on ICAUDIT - did you have this issue?

No - but we're running that interface only once daily. The time field is in a very bizarre format - I would basically make IT do it. But icaudit.R-TIME >= '9000000' get you everything after 9am, >='13000000' gets you every thing after 1pm. It's military hhmm with FOUR zeros trailing.

Thanks! 

I want to create one script that runs hourly rather than having to schedule different scripts all day, I will keep looking - thanks!

We use a modified IC527, and have had the same experience as many on this thread - after many CTP's stabilizing the IC527, I modified price to STOCK UOM and also included several user fields for EAPID, HCPCS, etc for driving Optime Patient Charge Markup. This runs 3x daily and has been very stable but is succeptable to CTP/MSP code changes. Currently working incident with GSC regarding defaulting - Lawson MAY have changed the rules for IC52x programs to depart from cost defaulting used in PO20 and RQ10 which I am taking an issue with,

We had the same issue - apparently a Gold Partner requested it and I protested that the field values are set by international standards - not a user preference - and they were changed back with a ctp. Then we every upgrade we had to change the IC527 - so we went with SQL.