Daynote ,Svenson

Sjon
 
-- Home -- Links -- To do -- Calendar -- The Gang -- The Undeniables --

  -- Yesterday -- Week view -- Tomorrow  

MM-xxxiv     Thursday

 

2000-02-03

 

 

There is a little frost on my car this morning, even though the thermometer is not convinced (it says 2C). And later there is some rain.

While Ronny was involved in a meeting with some sales people from Progress I solved the S3 problem that the Americans reported yesterday. As usual testing took more time than actually solving the problem. The problem occurs when more than one order is billed on a single invoice (collective invoicing) which is typically used for billing a client over a period in stead of at each shipment. It is also used when an order gets split up by the logistics module. When a (sub-)order is shipped a record for it is created in the trigger file. Later the trigger file is processed and for each order in it the S3 file is filled with the invoice information. Now you get two orders with the same invoice so that invoice gets added twice.
Easy if you know how it works. The only problem is that in a few opco's that use collective invoicing we never got that problem. That I why I assumed the duplicates were caused by something entirely different. Like the erroneous restore in Spain.

When Ronny came back from the meeting he was fuming with frustration. The Progress sales people had come to explain how, with their tools, we could make our TeleSales programs available trough the Web. As usual it would be easy and everything would go automatic etc. etc. Well the kind of talk aimed at managers that don't understand the technology used. Now it is unlucky that we currently have one manager who doesn't understand the technology at all and the other manager, Theo, is too new on the project to actually grasp the way our programs are interconnected. Now add Ronny who's patience span can be measured in seconds and you get a potent cocktail.

Adding to that we noticed that a change between the old version (8) and the new version (9) of Progress handles case sensitivity in field testing differently. When you had an X and an x in the database scanning for X found both. Now only the exact case is found. This impacts a lot of programs and requires en extraordinary amount of manual scanning (AS400 database fields are handled differently from internal fields.)

I did post yesterday. I really did. See, it is there .
But I actually re-posted the Tuesday pages, so the right page only arrived today.
I maintain the notes on my main system, then copy them to a diskette, climb up to the attic and post from there. Yesterday I took the wrong diskette up.

< !-- check the IMG directory on itool. backgrounds missing in comp section -->

Adios

 
-- Yesterday -- This week -- Tomorrow --

-- Home -- Links -- Calendar -- The Gang -- The Undeniables --
--

Svenson © 1999

Most of them got bored.