OELINAUD action codes 2

[kmonte]

I have a simple application that reads order data from the OELINAUD table. I need to find out what the ACTION codes stand for in the records. We have records with 'A', 'B', 'C', 'D', and every once in a while we get an 'E' or an 'F'. Can anyone tell me what these codes stand for? I think this table has what I need but I can't do much without knowing this information

Any help is greatly appreciated
Karen

 

[Macoladownunder]

From expereience of creating some crystal reports from this table, it is my understanding the action codes are as follows:
A= Add record
B= Before change of record
C= After Change of record
D= Delete record

I am yet to come across an E or an F. Hope this helps a little.

MacolaDownUnder
Aussies using Macola

 

[dgillz]

Karen,

What are you trying to do? If you tell us we may be able to make it easy on you.

Software Sales, Training, Implementation and Support for Exact Macola, eSynergy, and Crystal Reports

http://www.trianglepartners.com

 

[kmonte]

We have an application for our sales force to show them the order history for their customers. When an order is loaded into macola, we also load it into this application (this is where we are reading OELINAUD. The order then makes its way through all the processes we have, different people adding information into the order history, etc...

As you can imagine, when orders are modified in macola we have to reload them into the order history application...preserving all of the manual entry details. Once all of the data is in the OELINHST table (I believe this is done after invoicing), I don't run in to any problems with figuring out which records I need, but there are issues with the data that is still 'in process'and all I have is the OELINAUD data. Things are getting messed up in the case that we have a line item with a quantity > 1 and they ship and invoice some of the items but not all.

I did not write the original application but am now trying to put out some fires and am trying to figure out how to read the records I need...the first source of confusion being the action codes. My next task is to figure out if I have to look at both OELINHST and OELINAUD for orders that are partially invoiced but still have pending items when reloading the macola records and what the logic for doing this would be. I am definately open to suggestions and direction!!!!

 

[MacolaHelp]

oelinaud only tracks what is happening to active orders (unshipped items). Once invoiced, they go to oehdrhst & oelinhst. If you are trying to do "bookings" that include shipped & unshipped items that you might be calling "history", there are ways to do this. However, the dilemma resides in the fact that active orders are in oeordhdr & oeordlin, while shipments are in the history files noted above. To report off these tables simultaneously, you must first start with a file that sees both sets of tables such as iminvtrx or oeordinq. The audit files are really ugly & poorly indexed. I would avoid them wherever possible.

 

[kscheeler]

Karen,

If you are using Macola SQL, you can create views in Enterprise Manager that use a UNION query to combine fields from OEORDHDR_SQL and OEHDRHST_SQL and another one for OEORDLIN_SQL and OELINHST_SQL which would give you one place to see things that are both open and shipped. From Crystal, you would use the two views for the header and line information and then link into it the item, customer and any other relevant information you would want.

If you are using Btrieve, you can start a crystal report with the customer table ARCUSFIL_SQL and from that link to the OEORDHDR_SQL and OEHDRHST_SQL at the same time. If you check the Options of one of the links, you'll have a checkbox that says "Look up all of one, then all of others". You would then create a formula for each field that you want on the report. The formula for the item number would be like the following:

if isnull({OELINHST_SQL.Item_No}) then {OEORDLIN_SQL.Item_No} else
{OELINHST_SQL.Item_No}

The Btrieve bookings report will take some time to run because it reads all of your open order data and all of the order history data as well but both have worked for getting the information onto one report.

Kevin Scheeler

 

[MacolaHelp]

Karen: any reason why you don't put your comments in macola's order header or line comments? That way, you don't need to maintain another db. You could then generate a crystal or access report if the sales people only want to look at certain fields from the sales orders.

 

[kmonte]

One of the reasons we don't do this is that our financial guy does not want anyone but him putting information into macola in any way shape or form (he has fits over the fact that we are reading the data!). The second reason is that there is quite a bit of manual entry information that goes along with each order which doesn't really lend itself to being put into comments storage. Over time we could end up with 50-100 records in a 'detail' table that we need to maintain and display.