Conference acadmy::tpas_notes

Eric,

TPAS_XCLDD.EXE reads the TPAS$DB. The error is returned when the 'SET
TRANSACTION' fails or in the SQL fetch, an SQL error other than 100 (record 
not found) or 0 success, is returned.

Does the process running  have the correct ACLs (TPAS$DB_READ, 
TPAS_STKRM$DB_READ, TPAS_XCLDD$DB_WRITE). Can you run SQL on the TPAS$DB from
the account that is getting the error ? Are you running V4 of RDB? If so
check note 18.33 on priviledge in RDB database os DISTRIBTRAN. 

Let me know,
Lois

    Lois,

    The account that we are using can fully access all the TPAS database.  
    It have all the identifier, even TPAS$DB_OWNER, TPAS_XCLDD$DB_OWNER & 
    TPAS_STKRM$DB_OWNER.
   
    The TPAS_XCLDD.EXE that we executed can get data from TPAS$DB, the 
    error occured when we finished enter the new discount percentage and
    select ADD at the bottom of the screen.  The error message appeared
    right after the message "INSERT DISCOUNT data in process...". 
   
    I think we got the error when TPAS_XCLDD.EXE tried to insert the
    discount data into TPAS$XCLDD_DB.

    Any idea?
 
    Best regards,
    Eric Y.
    
    P.S. We are using RDB V4.1.

Eric,

I cannot re-produce it here could you send what data (Ship From, Ship To, 
Part ID, Part Type, dates, uplift and discount) you are adding. And if this 
occures after adding one or more records, what they were. Any other information
will be helpful. I will try it here. 

The only errors I get are "(EFF.END DATE within the ACTIVE PERIOD found in 
EXCLUDED TPAS Db.) " and "SUCCESS"

have you tried selecting the MODIFY icon ? 
Can you get into the TPAS$DB and TPAS$XCLDD_DB from SQL at VMS level ?

Lois 

Eric,

What about you TPAS$DB and TPAS$XLDD_DB logicals - are they set up alright ?

   
   Lois,

   I have already tried to select the MODIFY option and got the same 
   error.  Also, I do have TPAS$DB and TPAS$XCLDD_DB logicals defined
   in our system and can access TPAS$DB and TPAS$XCLDD_DB from SQL at
   VMS level.

   Here below is the data we want to add:-

	Ship From    : HKO
	Ship To      : SZN
	Part Class   : **
        Part Type    : ***
        Eff. Date    : 21-Feb-93
	Eff. End Date: 27-Mar-93
        Uplift       : 0
        Discount     : .53

   Best regards,
   Eric Y.

Eric,


Thank you for the data - it helped me nail down the problem immediately.
We are passing back the wrong error message. The data you gave, the 
record 

	Ship From    : HKO
	Ship To      : SZN
	Part Class   : **
        Part Type    : ***
        Eff. Date    : 30-Aug-92 
	Eff. End Date: null
        Uplift       : 0.05
        Discount     : .53



is in TPAS$DB. So when you tried to add in the other one to TPAS$XCLDD_DB -
the program won't let you. The above record is active and the 
TPAS_CALC_TRNSFR_PRC will never look into TPAS$XCLDD_DB, so why bother adding
it. The error messsage -

      (Overlap when Eff End date is Null found in TPAS Db.)

should have been returned. We will add this to the next release.
Thanks,
Lois

    Lois,
    
    When we called the TPAS_LOGIC module with a part with a unknown
    parttype in the TPAS pricing table, we expected that the system would
    try to get the pricing record from the TPAS_XCLDD pricing table.
    Problably it tried to fetch the record from TPAS_XCLDD but the result
    was the following SQL error:
    
    %SQL-F-ARGCOUNT, Procedure GET_XCLDD_PRICING_PN_MATCH expected 11 param
    
    It looks like a bug in the SQLMOD's. Could you please check this out
    and let us know a.s.a.p. please, because we are running out of time to
    get everything tested.
    
    Regards Rinus Jansen

Rinus,
Thank you for finding this. I have correct the TPAS_CALC_TRNSFR_PRC.COB
program and created a new kit release V1.1.
For those sites (HKO,TAO and KBO) who have V1.0 - they will be sent a new
kit. For those who have not yet requested V1.0 whey they request the TPAS
kit through ACADMY::QCA_ADMIN they will get the corrected object library.

regards,
Lois

    Lois,
    
    It seems that the index of the STOCKROOM table has been removed from
    the corporate TPAS_STKRM.RDB database. Because this will impact the
    performance I have created the index on out local database.
    Probably this index is still needed and it should be defined on the
    corporate table.
    
    Regards Rinus Jansen

Rinus,

That was an error here. Next month's stockroom RBR file (March 27) will
have the index in it.
Lois