[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference acadmy::tpas_notes

Title:	Transfer Price Administration System
Notice:	Conference has moved to ACADMY::TPAS_NOTES
Moderator:	ACADMY::MAGNI

Created:	Wed Jul 01 1992
Last Modified:	Fri Mar 21 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	102
Total number of notes:	459

88.0. "Question on TPAS logical table" by PASM07::ANDREWKAN () Thu May 04 1995 06:26

    
    Lois,
    
    I have the following questions to ask:
    
    1.  When will TPAS Inquiry function be available?
    
    2.  When we upgraded to TPAS V3.2, we encounter the following TPAS
    	error:
    
    PART NO           :QL-111AB-AA         PARSED PART NO =
    SHIPMENT  TYP CD  :01
    FROM STOCKROOM    :964  BILL_FROM TYP CD: S    LOCAL STD COST:
    TO STOCKROOM      :2495 BILL_TO   TYP CD: B    ORDER MLP     :
    FROM AREA CODE    :USA  STD COST TYPE CD: C    STD COST      :       
    0.000000
    TO AREA CODE      :KRS  PRODT TYPE CODE :      CORP. MLP     :             
    0.00
    FROM BUSNS TYPE CD:MFG  PRICE TYPE CODE :      BASE PRICE    :         
    0.000
    TO BUSNS TYPE CD  :SAL  CURRENCY        : USD  TRANSFER PRC  :         
    0.000
                            XCHNG RATE      :      0.00000000
    CMM               :0.00                    RBILL TRN PRC($)  :         
    0.000
    STD_COST UPLIFT   : 0.00                   RBILL DISC% TO MLP:      
    .00
    DISCOUNT PERCENT  : .00
    NOR DISCOUNT %    : .00
    RBILL DISCOUNT %  : .00
                                                MORE PARTS, PRESS 'Y' OR 'N'
    TPAS TRANS STATUS : 000000000
    %APPIX-F-NOAMPSAVAILOG, TPAS$AMPS_AVAILABLE Logical not defined
              WARNING :
    
    
    
    
    TPAS logical table is defined as follows in our environment.  I double
    check that AMPS$DATA has the APPIX satellite file. 
    
    
    (LNM$TPAS)
    
      "TPAS$AMPS" = "AMPS$DATA:APPIX_MPS.DAT"
      "TPAS$AMPS_AVAILABLE" = "N"
      "TPAS$BACKUP" = "TPAS$ROOT:[BACKUP]"
      "TPAS$BILL_FROM_TYPE_CD" = "S"
      "TPAS$BILL_TO_TYPE_CD" = "S"
      "TPAS$COM" = "TPAS$ROOT:[COM]"
      "TPAS$CREATE_AUDIT_TRAIL" = "N"
      "TPAS$CREATE_STDCST_TRAIL" = "N"
      "TPAS$DATA" = "TPAS$ROOT:[DATA]"
      "TPAS$DB" = "TPAS$ROOT:[DATA]TPAS.RDB"
      "TPAS$DISPLAY_I_ERRORS" = "N"
      "TPAS$DISPLAY_W_ERRORS" = "N"
      "TPAS$EXE" = "TPAS$ROOT:[EXE]"
      "TPAS$LIBRARY" = "TPAS$ROOT:[LIBRARY]"
      "TPAS$MAIL" = "TPAS$ROOT:[MAIL]"
      "TPAS$NOR$DB" = "TPAS$ROOT:[DATA]TPAS_NOR.RDB"
      "TPAS$ROOT" = "TPAS$DISK:[TPAS.]"
      "TPAS$SEND_LOCAL_STD" = "Y"
      "TPAS$SEPARATE_OPEN" = "Y"
      "TPAS$STKRM_DB" = "TPAS$ROOT:[DATA]TPAS_STKRM.RDB"
      "TPAS$TEMP" = "TPAS$ROOT:[TEMP]"
      "TPAS$USE_AMPS" = "Y"
      "TPAS$XCLDD_DB" = "TPAS$ROOT:[DATA]TPAS_XCLDD.RDB"
    
    
    
    Regards,                                          
    Andy

T.R	Title	User	Personal Name	Date	Lines
88.1	Can't re-produce error	AWARD::MAGNI	Lois, 237-5548	`Fri May 05 1995 17:39`	26
	Andrew, > 1. When will TPAS Inquiry function be available? I am finishing testing on the last screen of the TPAS Inquiry module. I will then be building and testing the VMS Install kit. The release of this will be the end of this month. It has to be timed with my moving the TPAS II to the ACADMY Cluster and TPAS I to the AWARD cluster. I will be posting a note when available. > 2. When we upgraded to TPAS V3.2, we encounter the following TPAS > error: I have tried to re-produce this error unsuccessfully. I have set all my logicals the same. You showed the LNM$TPAS logicals. Are those the only logicals set for TPAS ? This is the last table to be translated and it may be that a process, group, job or system logical is set and therefore causing this error. Are you sure that the area where you are processing from can get to the TPAS$AMPS file and it can open and read that file ? Any other info to help me re-produce the error will be useful. regards, Lois
88.2		PASM07::ANDREWKAN		`Mon May 08 1995 00:38`	30
	Lois, Only when we included TPAS table in the process table (LNM$PROCESS_TABLE) then we do not encounter the problem. Is that means we have to include TPAS table into process table everytime we call TPAS? My the other questions are: 1. When will monthly feed files be available to copy to local site? 2. After we copy the monthly feed files to local environment, do we have to run the following commands to rebuild TPAS databases? TPAS_SITE_IMPORT_DB.COM TPAS_SITE_IMPORT_STKRM_DB.COM TPAS_SITE_LOAD_NOR_DB.COM 3. I notice that when we were testing TPAS-II Ver3.0, most billing codes (SUBSID_BILLG_CD) with pattern '000%' have the field DB_FOUND_PART_INDCR in TRNSFR_AREA_TABLE in TPAS$DB set to 'Y' value. But after we upgraded to V3.2 and rebuilt TPAS databases, the DB_FOUND_PART_INDCR have set to 'N'. What is the reason for the change? Regards, Andy
88.3	Check you processes rights ids	AWARD::MAGNI	Lois, 237-5548	`Mon May 08 1995 17:22`	52
	Andrew, > Only when we included TPAS table in the process table (LNM$PROCESS_TABLE) > then we do not encounter the problem. Is that means we have to include > TPAS table into process table everytime we call TPAS? Have you tried running with the logicals set at GROUP, JOB or SYSTEM ? Did any of these cause you any problem ? I have tested the code with logicals set at all levels and have not been able to reproduce. Does you process have the TPAS Rights id TPAS$SUPPORT, TPAS$DB_ONWER or TPAS$DB_READ ? If it doen't then it cannot access the LNM$TPAS logical name table. > My the other questions are: > 1. When will monthly feed files be available to copy to local site? The TPAS_DB and TPAS_NOR_DB files will be ready by the last fiscal Thursday (AM) of the month. The TPAS_STKRM_DB will be ready the last fiscal Saturday of the month (night). The exact times should be listed in the installation instructions and note 22.4. > 2. After we copy the monthly feed files to local environment, do we > have to run the following commands to rebuild TPAS databases? > > TPAS_SITE_IMPORT_DB.COM > TPAS_SITE_IMPORT_STKRM_DB.COM > TPAS_SITE_LOAD_NOR_DB.COM These command stream are to be run just prior to opening up your system after month end. These command streams load the new databases for the new fiscla month. >> 3. I notice that when we were testing TPAS-II Ver3.0, most billing codes > (SUBSID_BILLG_CD) with pattern '000%' have the field > DB_FOUND_PART_INDCR in TRNSFR_AREA_TABLE in TPAS$DB set to 'Y' value. > But after we upgraded to V3.2 and rebuilt TPAS databases, the > DB_FOUND_PART_INDCR have set to 'N'. What is the reason for the change? The reason was because the test database was not yet complete. The Sales Subsidiaries (000%) do not need the part number on the Corporate Parts Master File. This was done for sales configurations, and other such things. That is why Order MLP and NOR is important to the TPAS II software for shipments to subsidiaries. Lois