| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 11.1 | TPAS V1.0 - Available - Request Form | AWARD::MAGNI | IM&T - 223-9837 | Tue Mar 02 1993 13:47 | 366 |
| TRANSFER PRICES ADMINISTRATION SYSTEM
======================================
This is to announce RELEASE 1.0 of the TPAS Software.
Please complete the following information to receive the TPAS V1.0 software.
One request for each site please. Mail the complete information to
EMAIL - ACADMY::QCA_ADMIN or hardcopy to APPIX Support Organization
MSO2/2-H11.
This software is the TPAS LOCAL SYSTEM kit which sites will incorporate into
their shipping, billing, receiving or other process software to calculate
the Transfer Price and return all data to the calling program.
Minor modification have been made to the install kit, the command streams,
the SQL command streams and the user documentation from the field test
release V0.7.
Included in the kit saveset are two documents: TPAS_INSTALLATION_DOC.PS and
TPAS_INSTALL.TXT. Both give complete instructions on the TPAS installation.
Support is available through NOTES AWARD::TPAS and the APPIX Support -
ACADMY::QCA_ADMIN.
TPAS LOCAL SYSTEM KIT
======================
Need RDB/SQL V4.0, PPCS and/or AMP2, COBOL 5.0, and DECforms 1.4
ENET LOCATION TO COPY KIT TO:
* AMP2 NEEDED (Y/N):
* PPCS NEEDED (Y/N):
* -> If either of these are needed please complete the
attached form(s) requesting AMP2 and/or PPCS.
REQUEST FOR PROXY ACCESS TO TPAS$OUTBOUND (TPAS_XFER)
------------------------------------------------------
** THIS INFORMATION WILL BE USED TO SET UP A PROXY FOR YOUR **
** SITE TO COPY THE TPAS DATABASE LOAD FILES. THE CLUSTER AND **
** VAX ACCOUNT SHOULD BE THE ACCOUNTS THAT WILL RUN THE TPAS **
** COMAND STREAMS IN PRODUCTION. **
** THE CONTACT E-MAIL WILL BE USED TO SEND MAIL NOTIFICATION **
** WHEN NEW LOAD FILES ARE MADE AVAILABLE. **
COPYING ACCOUNT INFORMATION
---------------------------
CLUSTER_ALIAS:
VAX ACCOUNT:
SITE CONTACT INFORMATION
-------------------------
SITE:
NAME:
DTN:
BADGE:
CC:
E-MAIL:
MAIL STOP:
Page 1 of 6
Hello,
Attached, you will find an APPIX Registration Form. Please read the
instructions very carefully, and fill out accordingly.
Also included is information on APPIX Training.
The following is information on charges for APPIX Products and Services.
The APPIX Parts and Product Reference organization has been instituting a
high-level charge-out method for services during FY93. The client
currently participating in this high-level charge-out method is
Engineering. We have begun discussions with other organizations to use high
level funding in FY94.
High-level funding involves totalling up the APPIX accounts and products
utilized by each client's cost center, taking the yearly total, dividing by
four, and charging identified higher-level cost centers for the combined
account/product charges. This process is done on a quarterly basis via a
Standard Journal Voucher.
This will alleviate the need for each Part & Product Reference
account/product user to be charged directly, but the function as a whole
will receive the charge.
Manufacturing cost centers are not being charged for the use of APPIX
products and services. These charges are being absorbed by the Part and
Product Reference organization.
For clients not mentioned above individual accounts/products will be
charged directly to the cost center specified on the registration form.
If you have any questions, please send mail to ACADMY::QCA_ADMIN, or call
the Part & Product Reference Support Hotline @ DTN 285-3999, or
from outside Digital (603)894-3999.
Thank you,
Part & Product Reference Support
MSO2-2/H11
Page 2 of 6
APPIX TRAINING
Part and Product Reference Support offers a one day training
class for APPIX clients. The training is free and is held in
the general Maynard area.
The APPIX training class is a one day hands-on workshop for
clients that are interested in building or strengthening their
understanding of the APPIX Inquiry functions and the information
available. The course features graphic presentations,
demonstrations of the inquiry menu functions and lab exercises.
To register and view scheduled training dates:
$ Set Host ACADMY
Username: COURSES
Password: TRAINING
Choose the appropriate options when you are in the COURSES MAIN MENU,
and follow the instructions at the bottom of the screen. Refer all
APPIX training questions to Mary Ellen Parker, DTN 223-9854, or
outside dialin (508)493-9854, or send VAXmail to AWARD::PARKER.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
APPIX REGISTRATION FORM
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Page 3 of 6
PART & PRODUCT REFERENCE APPLICATION SUPPORT
This form is used to register for APPIX services offered by the Part & Product
Reference Application organization. Please complete this form and forward it
to your Cost Center Manager. Your Cost Center Manager should then send the
completed form back to ACADMY::QCA_ADMIN. Upon receipt of your completed
registration form, an account in your name and badge number will be
established. Once the account has been created, we will then send
notification on how to access the account and obtain documentation.
Please be aware that your APPIX account is for your exclusive use, and
your ACADMY password is confidential. Corporate Security guidelines clearly
prohibit "sharing" any VAX account.
Questions? Write to us at ACADMY::QCA_ADMIN or call the Part & Product
Reference Application Hotline at DTN 285-3999, or outside dial-in
(603)894-3999.
-------------------------------------------------------------------------------
CUSTOMER INFORMATION
CORP. BADGE NUMBER:__________________ COST CENTER:________________________
FIRST NAME:__________________________ CC MGR BADGE NUMBER:________________
LAST NAME:___________________________ CC MGR FIRST NAME:__________________
MAILSTOP:____________________________ CC MGR LAST NAME:___________________
PHONE (DTN):_________________________ CC MGR MAILSTOP:____________________
NODE NAME:___________________________ CC MGR PHONE (DTN):_________________
NODE USERNAME:_______________________ CC MGR NODE NAME:___________________
CC MGR NODE USERNAME:_______________
Is your facility in the United States? ___Yes ___No
If no, please enter General Ledger Number & location code here ___________
Is your cost center part of GIA___, Europe___, or U.S.___ ?
All APPIX documentation is in Postscript format. Once your account has been
established we provide you with information on how to copy this documentation.
===============================================================================
AUTHORIZATION:
COST CENTER TO BE BILLED:_____ GROUP NAME:____________________________
ORGANIZATION YOU REPORT INTO:__________________(i.e., Mfg, Eng, D.S., etc.)
CC MANAGER:_________________________________COST CENTER:______DATE:_______
Authorization of CC Manager
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
APPIX REGISTRATION FORM
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Page 4 of 6
=============================================================================
Please return completed form to: | FOR INTERNAL P&P REFERENCE USE ONLY:
|
ELECTRONICALLY |
ACADMY::QCA_ADMIN | Contract Number:________________
OR |
INTERNALLY | Badge Number : _________________
PART & PRODUCT REFERENCE |
APPLICATION SUPPORT | Date Added: ____________________
|
MSO2-2/H11 | Funder: ________________________
|____________________________________
APPIX PRODUCT SELECTION:
PRODUCT DESCRIPTION COST
---------------- -------------------------------------------------------------
___ (100) APPIX APPIX Online Inquiry Account $ 500
___ (105) HSINQ APPIX Harmonized Code Inquiry 120
___ (151) SCIC APPIX Current Standard Cost Inquiry 200
___ (140) SWDIQ APPIX Shipping Weight & Dimension Inquiry 300
___ (424) PROPS Inquiry 1,200
___ KPL* APPIX Distributed Data Link to VAX/KPL (CAP2) 6,000
___ PACE APPIX Distributed Data Link to PACE (CAP2) 6,000
===============================================================================
*In order to receive BOM Audit and BOM Suspense Reports, users subscribing
to KPL provide BOM SYS ID here _______.
Page 5 of 6
The following are Extract or Server Products. In order to receive these
Extract files or reports, you must have your System Manager set up a proxy
for the receiving account.
Where do you want data sent?
NODE:_________ DEVICE:______________________ DIRECTORY:____________________
(System Managers please note -- to comply with Corporate Security mandates,
we cannot send Extract files to DECNET areas.)
Do you have VMS V5.0 or above? ____ If so, will this be the default proxy? ____
All Extract products except "SCOST" will come from Node:ACADMY,Dir:APPIX_PROD.
"SCOST" will come from Node: ACADMY, Dir: STD_SETTING.
Date you want to start receiving data :______________
PRODUCT DESCRIPTION ANNUAL COST
------- --------------------------------------------------------
___ AMP2 APPIX Master Parts Satellite System PER INSTALLATION $10,000
___ PPCS Part and Product Client Server NO CHARGE
PER ACCOUNT
___ BOS1 Bill of Supplier Reporting System (106) 1,500
___ EP83 APPIX Multi-Level Used-On (On line Request)(104) 6,000
___ EP84 APPIX Multi-level Used-On (Remote Request) 12,000
___ EP92 APPIX BOM Explosion (Remote Request) 4,800
___ EP93 APPIX BOM Explosion (On line request) (101) 1,200
___ EP94 APPIX BOM Comparison Extract (102) 1,200
___ HS01 APPIX Harmonized Code Description Extract 120
___ SCOST APPIX Weekly Standard Cost Extract 7,000
===============================================================================
V12.8 (effective 20-Nov-1992)
Page 6 of 6
INFORMATION SECURITY PROGRAM
ACCOUNT OWNERSHIP RESPONSIBILITIES
1) Never use easily guessable passwords such as family members, pets,
hobbies, projects, etc.
2) Your passwords should not be shared with anyone.
3) Passwords should never be transmitted over the network.
4) Users with accounts on multiple systems should ensure that their
password for each account is unique.
5) When logging in, do not let anyone observe you entering your
password.
6) Report any login failure messages you receive that you know you
did not generate. These messages will come up when you enter your
account. Also, be sure to read last login messages. If you feel a
security violation has been committed, please call your system
manager.
7) Do not give dial up access numbers to anybody internal or external
to DIGITAL. If you need dial up numbers for your own use, contact
IM Technical Support HOTLINE @DTN 285-3999.
8) Never leave your terminal logged on when absent from your office.
9) I have, or will, read Personnel Policies and Procedures 6.06
(Confidentiality), 6.24, 6.54 and 8.03.
10) Accessing any account or area without permission is subject to
disciplinary action.
11) If there are no logins to the account for 60 consecutive days at
any time, the account will be disabled. If there is no attempt
to have the account re-established after an additional 30 days,
the account will be removed.
********************************************************************************
To Be Signed by Account Requestor
I have read and understand my responsibilities as an account owner.
....................................... ..........................
NAME DATE
*** DIGITAL INTERNAL USE ONLY***
|
| 11.2 | TPAS V1.1 - release | AWARD::MAGNI | IM&T - 223-9837 | Wed Mar 10 1993 12:47 | 21 |
|
TRANSFER PRICES ADMINISTRATION SYSTEM
======================================
This is to announce RELEASE 1.1 of the TPAS Software.
If you have received V1.0 TPAS Kit through ACADMY::QCA_ADMIN request you
will be receive TPAS011.A kit. If you have not yet requested TPAS V1.0
then when you do you will be sent TPAS V1.1 (TPAS011.A).
Changes:
TPAS_CALC_TRNSFR_PRC - Incorrect number of parameters sent to
SQLMOD for look up on TPAS_XCLDD, would
not perform lookup.
TPAS_XCLDD - Returned incorrect error message.
TPAS_STKRM_TO_AREA - enhancement to change SHIP_TO/FROM to
upper case prior to look up on databases.
|
| 11.3 | TPAS V2.0 | AWARD::MAGNI | IM&T - 223-9837 | Fri Jul 30 1993 17:19 | 124 |
|
TRANSFER PRICES ADMINISTRATION SYSTEM
======================================
This is to announce RELEASE 2.0 of the TPAS Software.
If you have received V1.0 TPAS Kit through ACADMY::QCA_ADMIN you
will be receiving TPAS020.A kit. Contact ACADMY::QCA_ADMIN if you do not
receive the saveset.
If you have not yet requested TPAS V1.0 then when you need to register
with ACADMY::QCA_ADMIN for TPAS V2.0
Within the kit is install instructions and new users guide. These are also
available in AWARD::TPAS$PUBLIC as well as the Functional and Physical
design specifications.
Changes:
=========
TPAS V2.0
=========
SCHEDULED DATE FOR SITE IMPLEMENTATION: 29 AUGUST 1993
======================================
CONTENTS - FUNCTIONAL ENHANCEMENTS:
===================================
(1) If the APPIX standard cost is zero, return the local standard cost even
if not used in the calculation of Transfer Price.
SITE IM&T IMPLICATIONS:
-----------------------
Call to TPAS_CALC_TRNSFR_PRC will return a new data element:
TPAS_STD_CST_TYPE_CD PIC X(1)
Where the returned data in this field is:
L meaning standard cost returned is Local standard cost
C meaning standard cost returned is Corporate standard cost
(2) Incorporate the new TPAS_PRODT_TYPE_CD in place of the PART_TYPE_CD.
This data will be supplied to APPIX from the Corporate Tax Department
and will be used as a key in both the TPAS Pricing and TPAS Discount
Tables.
SITE IM&T IMPLICATIONS:
-----------------------
This enhancement will require the installation of the new
TPAS$XCLDD_DB and TPAS$DB database. The TPAS$XCLDD_DB database will
be supplied with the VMSInstal kit and the TPAS$DB will be supplied
when the TPAS_SITE_IMPORT_DB.COM is run at then end of fiscal August.
It is also recommended that the programs that call TPAS_CALC_TRNSFR_PRC
change the field name from TPAS_RCV_TPAS_PART_TYPE_CD to
TPAS_RCV_TPAS_PRODT_TYPE_CD. And if the PART_TYPE is used in calling
code then that logic be re-visited.
Also, this enhancement is required to change the AMP2 feed and
client code. Sites will be notified shortly as to when the code will
be available.
There will be a short period of time when larger AMP2 feed files will
be sent. These will supply the TPAS_PRODT_TYPE_CD to the AMP2 satellite
file. This will be announced through the normal APPIX communication
channels.
(3) Add BUSNS_TYPE_CD to each Transfer Area to distinguish the correct
pricing rules.
Each Transfer Area on the Transfer Area Table will be associated with
one BUSNS_TYPE_CD (Business Type Code). Each BUSNS_TYPE_CD will
attract a unique set of pricing rules on the TPAS Pricing Table.
This will allow us to apply different transfer pricing rules to
different entities on the interplant system.
SITE IM&T IMPLICATIONS:
-----------------------
The call to TPAS_CALC_TRNSFR_PRC will return two new data elements:
TPAS_BUSNS_FROM_TYPE_CD PIC X(3)
TPAS_BUSNS_TO_TYPE_CD PIC X(3)
Also, two new FATAL errors will be added:
MISSNGBUSTYP <Business Type Code for Ship To location is Blank>
NOTUNQBUSTYP <Business Type Code is not unique for Ship to Location>
These errors will be returned when the Business Type Code cannot
be found and therefore the correct pricing record cannot be retrieved.
This field will be validated prior to making the database available
to the sites, so if these error do come up then it would mean the TPAS$DB
database was changed at the site or the TPAS$XCLDD_DB was modified without
using the TPAS_XCLDD.EXE.
This enhancement will require the installation of the new
TPAS$XCLDD_DB and TPAS$DB database. The TPAS$XCLDD_DB database will
be supplied with the VMSInstal kit and the TPAS$DB will be supplied
when the TPAS_SITE_IMPORT_DB.COM is run at then end of fiscal August.
MINOR ENHANCEMENTS/BUG FIXES:
=============================
(A) VMSINSTALL will be changed to fix the "DUPLICATE RENAMING"
error for the "*.SQLs".
(B) TPAS_COPY*MNTHLY.COMs and TPAS_SITE_IMPORT*_DB.COMs will no longer
execute TPAS$ROOT:[COM]TPAS_LOGICALS.COM. These logicals are
set up /SYSTEM via the install kit.
(C) TPAS_SITE_IMPORT*_DB.COMs will do an SQL DROP SCHEMA prior to the
SQL IMPORT statement so that multiple versions of the database
will not be created.
(D) TPAS_COPY*MNTHLY.COMs will be modified to check the last serial number
file copied. The copy will only occur if the the serial number on
ACADMY is greater than the last once copied.
(E) TPAS_STKRM_TO_AREA>COM - Remove COBOL V5.0 "UPPER_CASE"
|
| 11.4 | TPAS INQUIRY V2.0 Release | AWARD::MAGNI | IM&T - 223-9837 | Mon Oct 04 1993 10:26 | 44 |
|
TRANSFER PRICE INQUIRY SYSTEM
=============================
This is to announce RELEASE 2.0 of the TPAS INQUIRY Software.
TPAS Inquiry V2.0 has been released. This software will provide users with
inquiry access to the TPAS Database, on-line Transfer Price Calculation,
and Report and Data File creations.
To receive the kit contact ACADMY::QCA_ADMIN. You will be sent an APPIX
registration form. Please complete page 3 of the form and on page 5 fill
in where you want the kit sent and check off:
___ Transfer Pricing (TPAS) Inquiry Kit NO CHARGE
Note: ACMS is required for the TPAS Inquiry Kit.
You will only need ACMS V3.2 AND DECforms V1.3 to run the inquiry software.
The kit contains complete installation instructions and user documentation.
These can also be copied from AWARD::TPAS$PUBLIC:TPASINQ_INSTALL_DOC.PS
and TPAS_USER_DOC.PS, respectively.
Once the kit is installed the users will need a password to obtain access
to the TPAS Functions. The users need to complete an APPIX registration
form, page 3 and on page 5 check off:
___ TPA Transfer Pricing (TPAS) Inquiry Access NO CHARGE
Have the signing manager send the completed forms from their account to
ACADMY::QCA_ADMIN.
If you have any questions or problems contact the APPIX Hotline by
phone DTN 285-3999 or mail ADADMY::QCA_ADMIN.
|
| 11.5 | TPAS Inquiry V3.0 Released | AWARD::MAGNI | Lois, 237-5548 | Mon Jun 12 1995 10:21 | 135 |
|
TRANSFER PRICE ADMINISTRATION SYSTEM INQUIRY
=============================================
This is to announce RELEASE 3.0 of the TPAS INQUIRY Software.
TPAS Inquiry V3.0 has been released. This release is for the TPAS II upgrade.
This software will provide users with inquiry access to the TPAS Databases,
on-line Transfer Price Calculation, and Report and Data File creations.
To receive the kit contact ACADMY::QCA_ADMIN. You will be sent an APPIX
registration form. Please complete page 3 of the form and on page 5 fill
in where you want the kit sent and check off:
___ Transfer Pricing (TPAS) Inquiry Kit NO CHARGE
Note: ACMS is required for the TPAS Inquiry Kit.
You will only need ACMS V3.2 AND DECforms V1.3 to run the inquiry software.
The kit contains complete installation instructions and user documentation.
These can also be copied from AWARD::TPAS$PUBLIC:TPASINQ_INSTALL_DOC.PS
and TPAS_II_USER_DOC.PS, respectively.
Once the kit is installed the users will need a password to obtain access
to the TPAS Functions. The users need to complete an APPIX registration
form, page 3 and on page 5 check off:
___ TPA Transfer Pricing (TPAS) Inquiry Access NO CHARGE
Have the signing manager send the completed forms from their account to
ACADMY::QCA_ADMIN.
If you have any questions or problems contact the APPIX Hotline by
phone DTN 297-6100 or mail ADADMY::QCA_ADMIN.
1 RELEASE NOTES FOR TPAS Inquiry V3.0
These notes contain sections covering the following topics:
o Problems fixed in this release
o Known current problems for TPAS Inquiry
o Additional installation considerations
o How to report software problems
TPAS Inquiry V 3.0 requires VMS Version 5.0 or later.
2 PROBLEMS FIXED IN THIS RELEASE
The following problems in previous versions of TPAS Inquiry have been
corrected in TPAS Inquiry Version 3.0:
o Enhanced to display the new data fields and data tables found
in TPAS$DB and TPAS$NOR$DB.
o TPAS LOGIC DATA INQUIRY calculation uses the TPAS_PRODT_TYPE_CD
instead of the PART_TYPE_CD as was the original calculation in
TPAS V1.0.
o TPASINQ$REMOVE has been provided. This command stream deletes the
TPAS*FORM.EXE files, directories, TPAS ACMS Files,
ACMS$DIRECTORY:TPASINQ$STARTUP.COM,
SYS$HELP:TPASINQ$030.RELEASE_NOTES, SYS$UPDATE:TPASINQ$REMOVE.COM
and SYS$TEST:TPASINQ$IVP.COM.
o Release notes were created and placed into SYS$HELP.
o TPASINQ$IVP.COM was updated to not ask for the device, if being run
from KITINSTAL.
Page 2
3 KNOWN PROBLEMS
o KNOWN PROBLEMS IN TPAS Inquiry V3.0
No Known Problems.
4 ADDITIONAL INSTALLATION CONSIDERATIONS
4.1 Installation Procedure Requirements
TPAS Inquiry requires ACMS to be installed. Follow the POST installation
instructions in the installation guide to set up the ACMS environment.
ACMS user accounts must be set up using ACMS User Definition Utility (UDU).
5 REPORTING SOFTWARE PROBLEMS
Complete and concise information will help Digital give accurate and
timely service to software problems. Experience shows that many SPRs
do not contain sufficient information to duplicate or identify the
problem. When you prepare to submit an SPR, please do the following:
o Describe as accurately as possible the state of the system
and the circumstances when the problem occurred. Include in
the description the version number of TPAS being used.
Illustrate the problem with specific examples.
o Reduce the problem to as small a size as possible, preferably
to a program unit of 30 source lines or fewer.
o Remember to include listings of any command files, relevant
data files, CDD record definitions, and so on.
o Place the problem on the notes file, AWARD::TPAS and mail
a copy to ACADMY::QCA_ADMIN.
o Report only one problem per SPR. This will facilitate a
faster response.
|
| 11.6 | TPAS REMOTE MODULE AVAILABLE | AWARD::MAGNI | Lois, 237-5548 | Mon Dec 04 1995 10:47 | 57 |
|
TRANSFER PRICE ADMINISTRATION SYSTEM
REMOTE MODULE
=====================================
This is to announce RELEASE of the TPAS REMOTE Software.
Transfer Price Administration System
Remote Module
Summary:
This module reads a file, sent from the user, of parts with the ship
to and from location. A report or data file of all the TPAS elements
will be created and sent back to the user.
Documentation:
The documentation on how to use this module can be pulled from:
ACADMY::PPR_DOC:TPAS_II_REMOTE_DOC.PS
ACADMY::PPR_DOC:TPAS_II_REMOTE_DOC.TXT
- or -
AWARD::TPAS$PUBLIC:TPAS_II_REMOTE_DOC.PS
AWARD::TPAS$PUBLIC:TPAS_II_REMOTE_DOC.TXT
AWARD::TPAS$PUBLIC:TPAS_II_REMOTE_MOD_DGRM.PS
Input File:
The input file can be created via a program created by the
the developers. The input file can also be created by the users
with any tool of there choice. The file layout expected is found
in the documentation.
The program to create the input file can be pulled from:
ACADMY::PPR_DOC:TPAS_REMOTE_CREATE_INPUT_PRCDR.COB
ACADMY::PPR_DOC:TPAS_REMOTE_CREATE_INPUT_PRCDR.EXE
- or -
AWARD::TPAS$PUBLIC:TPAS_REMOTE_CREATE_INPUT_PRCDR.COB
AWARD::TPAS$PUBLIC:TPAS_REMOTE_CREATE_INPUT_PRCDR.EXE
Obtaining Access:
To obtain access to this functionality, send a registration form
to ACADMY::QCA_ADMIN, checking off the TPRR selection in the form.
The form is available to copy from:
ACADMY::PPR_DOC:APPIX_USER_REGISTRATION.FORM
- or -
ACADMY::PPR_DOC:TPAS_REGISTRATION_FORM.TXT
- or -
AWARD::TPAS$PUBLIC:TPAS_REGISTRATION_FORM.TXT
|
| 11.7 | TPAS INQUIRY V3.1 - JAN 19 to go live | AWARD::MAGNI | Lois, 237-5548 | Fri Dec 29 1995 09:56 | 106 |
|
TPAS INQUIRY V3.1 RELEASE
A new release of TPAS Inquiry is now out. The Server Software on ACADMY
will be installed January 19th. Please have your IM&T support pull
the new client kit from ACADMY::TPAS$KIT:TPASINQ031.A
Your IM&T Support will need to schedule the RE-INSTALL for the weekend
of January 19-21.
-------------
Any questions or problems please contact ACADMY::QCA_ADMIN.
1 RELEASE NOTES FOR TPAS Inquiry V3.1
These notes contain sections covering the following topics:
o Problems fixed in this release
o Known current problems for TPAS Inquiry
o Additional installation considerations
o How to report software problems
TPAS Inquiry V 3.1 requires VMS Version 5.0 or later.
2 PROBLEMS FIXED IN THIS RELEASE
The following problems/enhancements in previous versions of TPAS Inquiry
have been corrected/added in TPAS Inquiry Version 3.1:
o Display of multiple help screens no longer displays the data
screen inbetween.
SPR 95041301
o All displays from the TPAS$DB tables send 1000 records at a time.
The display of the DISCOUNT Table has been changed to allow the
display of 10,000 records in 1000 records at a time.
SPR 95041302
o Data definition help panels have beed created for the Geopolitical
Cross Reference and Exchange Rate tables.
SPR 95041303
o The Geopolitical Country Name is now displayed on the NOR table.
SPR 95041702
o The Logic Report Panel array now resets and accepts 50 parts at a
time with multiple entries.
SPR 95101001
Page 2
3 KNOWN PROBLEMS
o KNOWN PROBLEMS IN TPAS Inquiry V3.1
No Known Problems.
4 ADDITIONAL INSTALLATION CONSIDERATIONS
4.1 Installation Procedure Requirements
TPAS Inquiry requires ACMS to be installed. Follow the POST installation
instructions in the installation guide to set up the ACMS environment.
ACMS user accounts must be set up using ACMS User Definition Utility (UDU).
5 REPORTING SOFTWARE PROBLEMS
Complete and concise information will help Digital give accurate and
timely service to software problems. Experience shows that many SPRs
do not contain sufficient information to duplicate or identify the
problem. When you prepare to submit an SPR, please do the following:
o Describe as accurately as possible the state of the system
and the circumstances when the problem occurred. Include in
the description the version number of TPAS Inquiry being used.
Illustrate the problem with specific examples.
o Reduce the problem to as small a size as possible, preferably
to a program unit of 30 source lines or fewer.
o Remember to include listings of any command files, relevant
data files, CDD record definitions, and so on.
o Place the problem on the notes file, AWARD::TPAS and/or mail
a copy to ACADMY::QCA_ADMIN.
o Report only one problem per SPR. This will facilitate a
faster response.
|
| 11.8 | TPAS V3.3 released | AWARD::MAGNI | Lois, 237-5548 | Mon Feb 26 1996 10:36 | 320 |
| TPAS V3.3 Release
Version 3.3 of TPAS has just been released. This corrects SPR 96020201,
reported in the TPAS Logic Module. This SPR is with pricing RETURNS.
When using SHIPMENT_TYPE_CD = 2,3,4 the TO/FROM codes were not
correctly reversed and the Transfer Price did not reflect the true
return transfer price.
The V3.3 Kit is available to pull in ACADMY::TPAS$KIT:TPAS033.A
This release is ONLY required if you are utilizing TPAS for pricing
RETURNS via SHIPMENT_TYPE_CD. Although, other non-critical SPRs were
also included in this release, see attached release notes.
If there are any questions or concerns contact Lois Magni at
DTN 297-3246 or AWARD::MAGNI
1 RELEASE NOTES FOR TPAS V3.3
These notes contain sections covering the following topics:
o Problems fixed in this release
o Known problems and Change Requests for TPAS
o Additional installation considerations
o How to report software problems
TPAS V 3.3 requires VMS Version 5.0 or later.
2 PROBLEMS FIXED IN THIS RELEASE
The following problems in previous versions of TPAS have been corrected in
TPAS Version 3.3:
o 95013101 - KITINSTALL
P: Error "DCL-W-IVVERB" in VMS install when installing
on a non-cluster.
S: The VMS Install no longer gives a Warning message when installing
on a non-cluster.
o 95020101 - TPAS_COPY_NOR_MNTHLY.COM
P: Use SPOOL COPY instead of just plain COPY.
S: The TPAS Copy Command Streams now utilize FTSV if available on
system for copying over monthly files.
o 95020901 - KITINSTALL RMU/VERIFY needs special ACLS for RDB V6
P: The RMU VERIFY in the TPAS_SITE_IMPORT_DB, TPAS_SITE_IMPORT_STKRM_DB
and TPAS_SITE_LOAD_NOR_DB does not work on RDB V6. The reason
for this is that RMU needs special new (VMS 6) ACLs set up
to run.
S: The VMS Install now adds the BIT identifiers on the DATA
directory as needed by RMU in Version 5 and above of RDB.
o 95030801 - TYPO in release notes
P: TPAS V3.2 release notes has a typo in field size.
S: The typographical error was found in the Users Guide, appendix A,
error message for RBTRNSPROCVRFLO should have been
999,999,999,999.999
o 95031301 - ERROR IDENT 1 character too long
P: Note 49.6
Error IDENT RBTRNSPRCOVRFLOW should be RBTRNSPRCOVRFLO as the
error IDENT size in VMS Messaging is 15 characters.
S: The error ident for RBTRNSPROCVRFLOW has been standardized to
RBTRNSPROCVRFLO.
2 PROBLEMS FIXED IN THIS RELEASE - Continued Page 2
o 95031302 - Always populate the currency code
P: Note 68.*
Always populate the Currency Code field even when the
transfer is an internal transfer thus the price is in USD.
S: The Currency Code and Exchange Rate fields are populated with
the USD currency and exchange rate when the Price Type Code is
equal to 'F', Interplant shipment.
o 95032101 - Ability to use a logical device address for TPAS$ROOT
P: Note 74.1
The VMSInstal.com does not allow the use of a logical device address
for TPAS$ROOT. Check to see if this can be changed.
S: Request to use rooted logicals to define rooted logicals.
Closed. This cannot be done. Must use a non-rooted logical to
define a rooted logical.
o 95042101 - APPIX$MESSAGE text incorrect
P: Note 86.2 86.3
The error message in APPIX$MESSAGES.MSG says 'processing' code
it should say 'pricing' code. This change also has to
be done in the user documentation.
S: The error text for an Invalid Price Type now says 'pricing' instead
of 'processing'.
o 95050501 - KITINSTALL ACLs and Install Kit
P: Notes 74.3,74.4 & 74.5
Need to have ACLs with resource as well as default.
Need to get Correct ACLS on DB.
S: The VMS Install now creates the ACLs as resources as well
as defaults.
o 95103001 - TPAS*COPY*.COM
P: Failed due to PNEWMN down and error when sending mail.
Send mail using NM% or change ON ERROR
S: NM% mail transport in now properly utilized in the Copy Command
streams.
o 96020201 - RETURNS
P: The returns do not properly reverse the ship to/from
data, thus the Transfer Price is not a return transfer price.
S: When SHIP_TYPE_CD equals 2,3,or 4 the plant data is now
reversed properly during and after price calculations.
o Release notes created for V3.3.
o The Kitinstal.com has been update to prompt user to re-install
the whole kit, including database, logicals and ACLs, or to
update only the code.
Page 3
3 KNOWN PROBLEMS and CHANGE REQUESTS
o KNOWN PROBLEMS and CHANGE REQUESTS IN TPAS V3.3
This section summarizes problems in the TPAS
that have not been fixed for this release. When a reference
to a note is made see the TPAS Notes file AWARD::TPAS
95010902 - SQL ERROR and VMS ERROR codes
All programs need to be checked to ensure that the
VMS and SQL error codes are being passed back to
TPAS_CALC_TRNSFR_PRC and these codes are being passed
back to the calling program.
See Note 55, 55.1, 56, 56.1
95012001 - SEPARATE OBJ LIBRARIES
Create two separate object libraries that have
different TPAS_GET_PART.COBs in them. One will
be used when site installing replies to use PPCS.
The other is for sites not using PPCS. This is so that
when linking without PPCS installed on the system the
undefined warning messages will not be seen.
See Note 58.1, 58.2
95020103 - TRANSACTION REFERENCE NUMBER
Add a transaction number to the record layout of the
audit trail file.
In order to find a specific transaction, the following
data need to be combined to find a unique transaction:
* Date
* part number
* ship/bill to code
a) include this 'Local system reference number' in the
call to TPAS
b) write this reference number to the audit trail file.
95031401 - The Discounts stored in the audit trail file are not
correct.
Note 76.*, 77.*
This looks like the discounts are moved into the audit trail
record fields differently than how they are moved into the
data returned to the calling program.
Page 4
3 KNOWN PROBLEMS and CHANGE REQUESTS - Continued
95032301 - Standardize the Database Population Routines
Note 80.*
Use only SQL Imports for loading ALL the databases.
Remove the RMU/VERIFY from the IMPORT Procedure.
Place the RMU/VERIFY into separate Procedures.
95032302 - LOGIC ERROR IN TPAS_CALC_TRNSFR_PRC using TPAS$SEND_LOCAL_STD
Note 81.*
When TPAS$SEND_LOCAL_STD = N and Corporate Std = 0 then the
program automatically (in para C030_GET_PART) goes to get the
local standard cost. If the local standard is zero then and
error occurs EVEN if the calculation doesn't need a standard
cost.
Changes needed in Para - C045-GET-LOCAL-STD-COST,
C030-GET-PART
C044-VALIDATE-PRICING-PTI-CMM
95033102 - Increase Size of CMM
Increase the size of TPAS$DB.PRICING_TABLE.PRCG_MLP_CALCN_FCTR
to 999.99
This is to accommodate software as APPIX only carries the
2-5-2 part # costs and not the 2-5-2.4 part #
95041305 - TPAS Maintenance
I would like to request that we be able to wild card either
character of the part class on the pricing tables to allow
us to distinguish between hardware and software, pc's....
Since the Product type only works on part numbers on APPIX,
it has limited use for TPAS 2 transactions to the sales subs.
95041701 - TPAS_PRODT_TYPE_UPD_MPF_PRCDR
- Increase processing time, decrease CPRS locking.
This procedure is locking up the CPRS and taking an
inordinate amount of time. Look at the way the records
are selected (cursors) and locked. Add in more commits
if needed.
** OR **
- Move the SOC table into the TPAS Database, change the
TPAS_GET_PART to look up the TPAS_PRODT_TYPE on the
TPAS$DB and get the PART_TYPE from APPIX. Remove all
the code to the APPIX programs to populate the APPIX
TPAS_PRODT_TYPE field.
Page 5
3 KNOWN PROBLEMS and CHANGE REQUESTS - Continued
95060703 - Databases
- Create indices for all possible looks up on
TPAS$DB, TPAS$NOR$DB, TPAS$FUTURE$DB, TPAS$NOR_FUTURE$DB
Doing this will increase performance and record locking
in the TPAS Maintenance Program.
- Set defaults internally for fields with defaults.
95081101 - TPAS Inquiry
- Allow the inquiry to use either TPAS$DB or TPAS$FUTURE$DB.
Make this a user choice. Post DB Select on top of panels AND
on reports.
This has to be done with SPR 95092601
95092601 - TPAS Future Database
- Change the TPAS$FUTURE$DB tables to remove the "future" from
the table name. Change all associated sqlmod code.
This will enable the re-use of INQUIRY and MAINTENANCE code
to be used on either database.
This needs to be done for SPR 95081101
95092602 - TPAS Transfer Area Table and Business Type Table.
- Take the following fields from the Transfer Area Table and
Place them on the Business Type Table:
Below_std, Rbill_ind, DB_FND_PRT_IND, Cntry_Area_NOR,
Cntry_cd, Purch_cur
All code access these fields will change.
This will decrease data redundancy and increase the ease of
maintenance.
------------- or ---------------------------
Modify the maintenance module to:
1) If transfer area is changed then update
that records with all the settings of established
records with that transfer area.
2) If the transfer area is not changed then update all
records with the same transfer area with the
new settings.
95111401 - Corporate Parser in TPAS_GET_PART.COB
- When sending in a part with the revision level then the
parser sends back an error. Should just drop the rev level
when looking up on APPIX. Parser should be ok, check the
code written around it.
Page 6
4 ADDITIONAL INSTALLATION CONSIDERATIONS
4.1 Installation Procedure Requirements
Make sure that all questions asked during the install are answered ahead of
time. If any changes to default logicals are required then edit the
TPAS$COM:TPAS_LOGICALS.COM and the SYS$MANAGER:TPAS$STARTUP.COM.
The program translate the logicals using the logical name table in VMS order:
PROCESS, JOB, GROUP, SYSTEM and LNM$TPAS
5 REPORTING SOFTWARE PROBLEMS
Complete and concise information will help Digital give accurate and
timely service to software problems. Experience shows that many SPRs
do not contain sufficient information to duplicate or identify the
problem. When you prepare to submit an SPR, please do the following:
o Describe as accurately as possible the state of the system
and the circumstances when the problem occurred. Include in
the description the version number of TPAS being used.
Illustrate the problem with specific examples.
o Reduce the problem to as small a size as possible, preferably
to a program unit of 30 source lines or fewer.
o Remember to include listings of any command files, relevant
data files, CDD record definitions, and so on.
o Place the problem on the notes file, AWARD::TPAS and mail
a copy to ACADMY::QCA_ADMIN.
o Report only one problem per SPR. This will facilitate a
faster response.
|
| 11.9 | TPAS V3.4 - SEPS 97 | AWARD::MAGNI | Lois, 297-3246 | Tue Dec 03 1996 13:01 | 307 |
|
TPAS V3.4 Release
Version 3.4 of TPAS has just been released. This corrects SPR
96111302 for SQL in SEPS 97.
The V3.4 Kit is available to pull in ACADMY::TPAS$KIT:TPAS034.A
This release is ONLY required if you are upgrading to SEPS 97.
Although, one other non-critical SPR was also included in this
release, see attached release notes.
If there are any questions or concerns contact Lois Magni at
DTN 297-3246 or AWARD::MAGNI
1 RELEASE NOTES FOR TPAS V3.4
These notes contain sections covering the following topics:
o Problems fixed in this release
o Known problems and Change Requests for TPAS
o Additional installation considerations
o How to report software problems
TPAS V 3.4 requires VMS Version 5.0 or later.
2 PROBLEMS FIXED IN THIS RELEASE
This patch release of TPAS is to address the release of SQL V6.0
o 96060601 - KITINSTALL
P: Files moved into System Directories with TPAS$SUPPORT
as owner. Should be [SYSTEM]
S: Files set to [SYSTEM] owner
o 96111302 - SEPS 97
P: Error with KITINSTAL with V6 SQL. The KITINSTALL
exits with error.
S: The VMS Install now check for V3, V4 and V5 specifically.
Any version greater than V5 is accepted.
KITINSTAL.COM
P: The symbol "$SQL:==$SYS$SYSTEM:SQL$" does not work under SEPS 97
S: Change the symbol to "$SQL :== $SQL$"
KITINSTAL.COM
TPAS_SITE_IMPORT_DB.COM
TPAS_SITE_IMPORT_STKRM_DB.COM
TPAS_SITE_LOAD_NOR_DB.COM
P: The image name of FTSV changed
S: Change the image names from FTSV to FTSV$CLI
and FTSVEXEC to FTSV$EXEC
TPAS_COPY_MNTHLY.COM
TPAS_COPY_NOR_MNTHLY.COM
TPAS_COPY_STKRM_MNTHLY.COM
o Release notes created for V3.4.
Page 2
3 KNOWN PROBLEMS and CHANGE REQUESTS
o KNOWN PROBLEMS and CHANGE REQUESTS IN TPAS V3.4
This section summarizes problems in the TPAS
that have not been fixed for this release. When a reference
to a note is made see the TPAS Notes file AWARD::TPAS
95010902 - SQL ERROR and VMS ERROR codes
All programs need to be checked to ensure that the
VMS and SQL error codes are being passed back to
TPAS_CALC_TRNSFR_PRC and these codes are being passed
back to the calling program.
See Note 55, 55.1, 56, 56.1
95012001 - SEPARATE OBJ LIBRARIES
Create two separate object libraries that have
different TPAS_GET_PART.COBs in them. One will
be used when site installing replies to use PPCS.
The other is for sites not using PPCS. This is so that
when linking without PPCS installed on the system the
undefined warning messages will not be seen.
See Note 58.1, 58.2
95020103 - TRANSACTION REFERENCE NUMBER
Add a transaction number to the record layout of the
audit trail file.
In order to find a specific transaction, the following
data need to be combined to find a unique transaction:
* Date
* part number
* ship/bill to code
a) include this 'Local system reference number' in the
call to TPAS
b) write this reference number to the audit trail file.
95031401 - The Discounts stored in the audit trail file are not
correct.
Note 76.*, 77.*
This looks like the discounts are moved into the audit trail
record fields differently than how they are moved into the
data returned to the calling program.
Page 3
3 KNOWN PROBLEMS and CHANGE REQUESTS - Continued
95032301 - Standardize the Database Population Routines
Note 80.*
Use only SQL Imports for loading ALL the databases.
Remove the RMU/VERIFY from the IMPORT Procedure.
Place the RMU/VERIFY into separate Procedures.
95032302 - LOGIC ERROR IN TPAS_CALC_TRNSFR_PRC using TPAS$SEND_LOCAL_STD
Note 81.*
When TPAS$SEND_LOCAL_STD = N and Corporate Std = 0 then the
program automatically (in para C030_GET_PART) goes to get the
local standard cost. If the local standard is zero then and
error occurs EVEN if the calculation doesn't need a standard
cost.
Changes needed in Para - C045-GET-LOCAL-STD-COST,
C030-GET-PART
C044-VALIDATE-PRICING-PTI-CMM
95033102 - Increase Size of CMM
Increase the size of TPAS$DB.PRICING_TABLE.PRCG_MLP_CALCN_FCTR
to 999.99
This is to accommodate software as APPIX only carries the
2-5-2 part # costs and not the 2-5-2.4 part #
95041305 - TPAS Maintenance
I would like to request that we be able to wild card either
character of the part class on the pricing tables to allow
us to distinguish between hardware and software, pc's....
Since the Product type only works on part numbers on APPIX,
it has limited use for TPAS 2 transactions to the sales subs.
95041701 - TPAS_PRODT_TYPE_UPD_MPF_PRCDR
- Increase processing time, decrease CPRS locking.
This procedure is locking up the CPRS and taking an
inordinate amount of time. Look at the way the records
are selected (cursors) and locked. Add in more commits
if needed.
** OR **
- Move the SOC table into the TPAS Database, change the
TPAS_GET_PART to look up the TPAS_PRODT_TYPE on the
TPAS$DB and get the PART_TYPE from APPIX. Remove all
the code to the APPIX programs to populate the APPIX
TPAS_PRODT_TYPE field.
Page 4
3 KNOWN PROBLEMS and CHANGE REQUESTS - Continued
95060703 - Databases
- Create indices for all possible looks up on
TPAS$DB, TPAS$NOR$DB, TPAS$FUTURE$DB, TPAS$NOR_FUTURE$DB
Doing this will increase performance and record locking
in the TPAS Maintenance Program.
- Set defaults internally for fields with defaults.
95081101 - TPAS Inquiry
- Allow the inquiry to use either TPAS$DB or TPAS$FUTURE$DB.
Make this a user choice. Post DB Select on top of panels AND
on reports.
This has to be done with SPR 95092601
95092601 - TPAS Future Database
- Change the TPAS$FUTURE$DB tables to remove the "future" from
the table name. Change all associated sqlmod code.
This will enable the re-use of INQUIRY and MAINTENANCE code
to be used on either database.
This needs to be done for SPR 95081101
95092602 - TPAS Transfer Area Table and Business Type Table.
- Take the following fields from the Transfer Area Table and
Place them on the Business Type Table:
Below_std, Rbill_ind, DB_FND_PRT_IND, Cntry_Area_NOR,
Cntry_cd, Purch_cur
All code access these fields will change.
This will decrease data redundancy and increase the ease of
maintenance.
------------- or ---------------------------
Modify the maintenance module to:
1) If transfer area is changed then update
that records with all the settings of established
records with that transfer area.
2) If the transfer area is not changed then update all
records with the same transfer area with the
new settings.
95111401 - Corporate Parser in TPAS_GET_PART.COB
- When sending in a part with the revision level then the
parser sends back an error. Should just drop the rev level
when looking up on APPIX. Parser should be ok, check the
code written around it.
Page 5
3 KNOWN PROBLEMS and CHANGE REQUESTS - Continued
96052201 - LIB$SPAWN from a Captive Account
- Bill Breen
- LIB$SPAWN needs to be upgrade (with PACE Compliency)
with the switches allowed for doing a LIB$SPAWN from
a captive account.
TARGET Call 204104
TPAS_CALC_TRNSFR_PRCDR.COB
TPAS_ZSC_PART.COB
TPAS_XCLDD.COB
TPAS_CTAX_SCHED_RUN_JOBS_PRCDR.COB
TPAS_CTAX_MAILING_REPORT_PRCDR.COB
96052401 - Year 2000
- Father Time
- Test all programs, especially those that do a SYS$BINTIM or such,
under a VMS machine that has date set into Fiscal Year 2000
(Jul 1, 1999 to Dec 31, 1999) and again in Calendar year 2000.
Change the following programs to test date and use "20" in the
century field if system date is > 31-Dec-1999. If century is
used for a Fiscal Date then the check should be >= 4-Jul-1999
(This is Fiscal Day 1 in FY 2000)
96070202 - Send a status flag back to the command stream from
TPAS_DB_CHNGS_RPT_PRCDR.COB.
Change the TPAS_XPORT_DB_PRCDR.COM to check switch.
- Lois Magni
96071601 - Change the logic to NOT price via Corp MLP
- Corp Tax, Tracy Walker
- Remove the 'M' pricing code from the pricing table as well
as all the pricing logic for pricing from Corp MLP.
That would be TRNSFR_PRCG_CD = M, H, and I
The logic for J and K would become
"If TRNSFR_PRCG_CD = 'O'and Order MLP <= 0" and
"If TRNSFR_PRCG_CD = 'G'and Order MLP <= 0"
respectively.
Page 6
4 ADDITIONAL INSTALLATION CONSIDERATIONS
4.1 Installation Procedure Requirements
Make sure that all questions asked during the install are answered ahead of
time. If any changes to default logicals are required then edit the
TPAS$COM:TPAS_LOGICALS.COM and the SYS$MANAGER:TPAS$STARTUP.COM.
The program translate the logicals using the logical name table in VMS order:
PROCESS, JOB, GROUP, SYSTEM and LNM$TPAS
5 REPORTING SOFTWARE PROBLEMS
Complete and concise information will help Digital give accurate and
timely service to software problems. Experience shows that many SPRs
do not contain sufficient information to duplicate or identify the
problem. When you prepare to submit an SPR, please do the following:
o Describe as accurately as possible the state of the system
and the circumstances when the problem occurred. Include in
the description the version number of TPAS being used.
Illustrate the problem with specific examples.
o Reduce the problem to as small a size as possible, preferably
to a program unit of 30 source lines or fewer.
o Remember to include listings of any command files, relevant
data files, CDD record definitions, and so on.
o Place the problem on the notes file, AWARD::TPAS and mail
a copy to ACADMY::QCA_ADMIN.
o Report only one problem per SPR. This will facilitate a
faster response.
|
| 11.10 | TPAS V3.3a Patch Release | AWARD::MAGNI | Lois, 297-3246 | Tue Jan 14 1997 13:55 | 313 |
| TPAS V3.3a PATCH Release
Version 3.3a of TPAS has just been released. This patch changes the mail
notification from the APPIX IS support to Corporate Tax in the database
COPY and IMPORT command streams. Also, the RMU/VERIFY command is
removed from the IMPORT Streams to a separate stream so sites can run
this as needed.
The V3.3a Kit is available to pull in ACADMY::TPAS$KIT:TPAS033a.A
This patch release is required.
If there are any questions or concerns contact Lois Magni at
DTN 297-3246 or AWARD::MAGNI
1 RELEASE NOTES FOR TPAS V3.3A
These notes contain sections covering the following topics:
o Problems fixed in this release
o Known problems and Change Requests for TPAS
o Additional installation considerations
o How to report software problems
TPAS V 3.3A requires VMS Version 5.0 or later.
2 PROBLEMS FIXED IN THIS RELEASE
This patch release of TPAS is to provide mail feedback to Corporate Tax
for monitoring the distribution and implementation of the 3 TPAS Databases.
Also in this patch three separate command streams have been created to
do RMU/VERIFY on the three databases. The creation of these separate command
streams removed the RMU/VERIFY from the Import and Load command stream.
o 95032301 - Standardize the Database Population Routines
P: Use only SQL Imports for loading ALL the databases.
Remove the RMU/VERIFY from the IMPORT Procedure.
Place the RMU/VERIFY into separate Procedures.
S: Only the RMU/VERIFYs were addressed here with the
creation of three separate command streams and modifications
of the TPAS_SITE_*_DB.COM
o 96121302 - Mail Notification to Corporate Tax
P: Corporate Tax requires notification of sites pulling and
loading the TPAS Databases.
S: Change the TPAS_COPY*MONTHLY.COMs and TPAS_SITE_*_DB.COMs to
mail a success notification to Corporate Tax.
Modified
TPAS_COPY_MNTHLY.COM TPAS_COPY_NOR_MNTHLY.COM
TPAS_COPY_STKRM_MNTHLY.COM
TPAS_SITE_IMPORT_DB.COM TPAS_SITE_IMPORT_STKRM_DB.COM
TPAS_SITE_LOAD_NOR_DB.COM
New
TPAS_RMU_VERIFY_NOR_PRCDR.COM TPAS_RMU_VERIFY_PRCDR.COM
TPAS_RMU_VERIFY_STKRM_PRCDR.COM
o Release notes created for V3.3A.
Page 2
3 KNOWN PROBLEMS and CHANGE REQUESTS
o KNOWN PROBLEMS and CHANGE REQUESTS IN TPAS V3.3A
This section summarizes problems in the TPAS
that have not been fixed for this release. When a reference
to a note is made see the TPAS Notes file AWARD::TPAS
95010902 - SQL ERROR and VMS ERROR codes
All programs need to be checked to ensure that the
VMS and SQL error codes are being passed back to
TPAS_CALC_TRNSFR_PRC and these codes are being passed
back to the calling program.
See Note 55, 55.1, 56, 56.1
95012001 - SEPARATE OBJ LIBRARIES
Create two separate object libraries that have
different TPAS_GET_PART.COBs in them. One will
be used when site installing replies to use PPCS.
The other is for sites not using PPCS. This is so that
when linking without PPCS installed on the system the
undefined warning messages will not be seen.
See Note 58.1, 58.2
95020103 - TRANSACTION REFERENCE NUMBER
Add a transaction number to the record layout of the
audit trail file.
In order to find a specific transaction, the following
data need to be combined to find a unique transaction:
* Date
* part number
* ship/bill to code
a) include this 'Local system reference number' in the
call to TPAS
b) write this reference number to the audit trail file.
95031401 - The Discounts stored in the audit trail file are not
correct.
Note 76.*, 77.*
This looks like the discounts are moved into the audit trail
record fields differently than how they are moved into the
data returned to the calling program.
Page 3
3 KNOWN PROBLEMS and CHANGE REQUESTS - Continued
95032301 - Standardize the Database Population Routines
Note 80.*
Use only SQL Imports for loading ALL the databases.
Remove the RMU/VERIFY from the IMPORT Procedure. - V3.3A
Place the RMU/VERIFY into separate Procedures. - V3.3A
95032302 - LOGIC ERROR IN TPAS_CALC_TRNSFR_PRC using TPAS$SEND_LOCAL_STD
Note 81.*
When TPAS$SEND_LOCAL_STD = N and Corporate Std = 0 then the
program automatically (in para C030_GET_PART) goes to get the
local standard cost. If the local standard is zero then and
error occurs EVEN if the calculation doesn't need a standard
cost.
Changes needed in Para - C045-GET-LOCAL-STD-COST,
C030-GET-PART
C044-VALIDATE-PRICING-PTI-CMM
95033102 - Increase Size of CMM
Increase the size of TPAS$DB.PRICING_TABLE.PRCG_MLP_CALCN_FCTR
to 999.99
This is to accommodate software as APPIX only carries the
2-5-2 part # costs and not the 2-5-2.4 part #
95041305 - TPAS Maintenance
I would like to request that we be able to wild card either
character of the part class on the pricing tables to allow
us to distinguish between hardware and software, pc's....
Since the Product type only works on part numbers on APPIX,
it has limited use for TPAS 2 transactions to the sales subs.
95041701 - TPAS_PRODT_TYPE_UPD_MPF_PRCDR
- Increase processing time, decrease CPRS locking.
This procedure is locking up the CPRS and taking an
inordinate amount of time. Look at the way the records
are selected (cursors) and locked. Add in more commits
if needed.
** OR **
- Move the SOC table into the TPAS Database, change the
TPAS_GET_PART to look up the TPAS_PRODT_TYPE on the
TPAS$DB and get the PART_TYPE from APPIX. Remove all
the code to the APPIX programs to populate the APPIX
TPAS_PRODT_TYPE field.
Page 4
3 KNOWN PROBLEMS and CHANGE REQUESTS - Continued
95060703 - Databases
- Create indices for all possible looks up on
TPAS$DB, TPAS$NOR$DB, TPAS$FUTURE$DB, TPAS$NOR_FUTURE$DB
Doing this will increase performance and record locking
in the TPAS Maintenance Program.
- Set defaults internally for fields with defaults.
95081101 - TPAS Inquiry
- Allow the inquiry to use either TPAS$DB or TPAS$FUTURE$DB.
Make this a user choice. Post DB Select on top of panels AND
on reports.
This has to be done with SPR 95092601
95092601 - TPAS Future Database
- Change the TPAS$FUTURE$DB tables to remove the "future" from
the table name. Change all associated sqlmod code.
This will enable the re-use of INQUIRY and MAINTENANCE code
to be used on either database.
This needs to be done for SPR 95081101
95092602 - TPAS Transfer Area Table and Business Type Table.
- Take the following fields from the Transfer Area Table and
Place them on the Business Type Table:
Below_std, Rbill_ind, DB_FND_PRT_IND, Cntry_Area_NOR,
Cntry_cd, Purch_cur
All code access these fields will change.
This will decrease data redundancy and increase the ease of
maintenance.
------------- or ---------------------------
Modify the maintenance module to:
1) If transfer area is changed then update
that records with all the settings of established
records with that transfer area.
2) If the transfer area is not changed then update all
records with the same transfer area with the
new settings.
95111401 - Corporate Parser in TPAS_GET_PART.COB
- When sending in a part with the revision level then the
parser sends back an error. Should just drop the rev level
when looking up on APPIX. Parser should be ok, check the
code written around it.
Page 5
3 KNOWN PROBLEMS and CHANGE REQUESTS - Continued
96052201 - LIB$SPAWN from a Captive Account
- Bill Breen
- LIB$SPAWN needs to be upgrade (with PACE Compliency)
with the switches allowed for doing a LIB$SPAWN from
a captive account.
TARGET Call 204104
TPAS_CALC_TRNSFR_PRCDR.COB
TPAS_ZSC_PART.COB
TPAS_XCLDD.COB
TPAS_CTAX_SCHED_RUN_JOBS_PRCDR.COB
TPAS_CTAX_MAILING_REPORT_PRCDR.COB
96052401 - Year 2000
- Father Time
- Test all programs, especially those that do a SYS$BINTIM or such,
under a VMS machine that has date set into Fiscal Year 2000
(Jul 1, 1999 to Dec 31, 1999) and again in Calendar year 2000.
Change the following programs to test date and use "20" in the
century field if system date is > 31-Dec-1999. If century is
used for a Fiscal Date then the check should be >= 4-Jul-1999
(This is Fiscal Day 1 in FY 2000)
96070202 - Send a status flag back to the command stream from
TPAS_DB_CHNGS_RPT_PRCDR.COB.
Change the TPAS_XPORT_DB_PRCDR.COM to check switch.
- Lois Magni
96071601 - Change the logic to NOT price via Corp MLP
- Corp Tax, Tracy Walker
- Remove the 'M' pricing code from the pricing table as well
as all the pricing logic for pricing from Corp MLP.
That would be TRNSFR_PRCG_CD = M, H, and I
The logic for J and K would become
"If TRNSFR_PRCG_CD = 'O'and Order MLP <= 0" and
"If TRNSFR_PRCG_CD = 'G'and Order MLP <= 0"
respectively.
96111302 - SEPS 97
Changes needed to command streams for new names on SQL and FTSV
Images.
96121701 - Change the TPAS Maintenance to allow up to 999.99 % on
the PDA.
- Tracy Walker
Page 6
4 ADDITIONAL INSTALLATION CONSIDERATIONS
4.1 Installation Procedure Requirements
Make sure that all questions asked during the install are answered ahead of
time. If any changes to default logicals are required then edit the
TPAS$COM:TPAS_LOGICALS.COM and the SYS$MANAGER:TPAS$STARTUP.COM.
The program translate the logicals using the logical name table in VMS order:
PROCESS, JOB, GROUP, SYSTEM and LNM$TPAS
5 REPORTING SOFTWARE PROBLEMS
Complete and concise information will help Digital give accurate and
timely service to software problems. Experience shows that many SPRs
do not contain sufficient information to duplicate or identify the
problem. When you prepare to submit an SPR, please do the following:
o Describe as accurately as possible the state of the system
and the circumstances when the problem occurred. Include in
the description the version number of TPAS being used.
Illustrate the problem with specific examples.
o Reduce the problem to as small a size as possible, preferably
to a program unit of 30 source lines or fewer.
o Remember to include listings of any command files, relevant
data files, CDD record definitions, and so on.
o Place the problem on the notes file, AWARD::TPAS and mail
a copy to ACADMY::QCA_ADMIN.
o Report only one problem per SPR. This will facilitate a
faster response.
|
| 11.11 | TPAS V3.4a Patch Release | AWARD::MAGNI | Lois, 297-3246 | Tue Jan 14 1997 13:56 | 310 |
| TPAS V3.4a PATCH Release
Version 3.4a of TPAS has just been released. This patch changes the mail
notification from the APPIX IS support to Corporate Tax in the database
COPY and IMPORT command streams. Also, the RMU/VERIFY command is
removed from the IMPORT Streams to a separate stream so sites can run
this as needed.
The V3.4a Kit is available to pull in ACADMY::TPAS$KIT:TPAS034a.A
This patch release is required.
If there are any questions or concerns contact Lois Magni at
DTN 297-3246 or AWARD::MAGNI
1 RELEASE NOTES FOR TPAS V3.4A
These notes contain sections covering the following topics:
o Problems fixed in this release
o Known problems and Change Requests for TPAS
o Additional installation considerations
o How to report software problems
TPAS V 3.4A requires VMS Version 5.0 or later.
2 PROBLEMS FIXED IN THIS RELEASE
This patch release of TPAS is to provide mail feedback to Corporate Tax
for monitoring the distribution and implementation of the 3 TPAS Databases.
Also in this patch three separate command streams have been created to
do RMU/VERIFY on the three databases. The creation of these separate command
streams removed the RMU/VERIFY from the Import and Load command stream.
o 95032301 - Standardize the Database Population Routines
P: Use only SQL Imports for loading ALL the databases.
Remove the RMU/VERIFY from the IMPORT Procedure.
Place the RMU/VERIFY into separate Procedures.
S: Only the RMU/VERIFYs were addressed here with the
creation of three separate command streams and modifications
of the TPAS_SITE_*_DB.COM
o 96121302 - Mail Notification to Corporate Tax
P: Corporate Tax requires notification of sites pulling and
loading the TPAS Databases.
S: Change the TPAS_COPY*MONTHLY.COMs and TPAS_SITE_*_DB.COMs to
mail a success notification to Corporate Tax.
Modified
TPAS_COPY_MNTHLY.COM TPAS_COPY_NOR_MNTHLY.COM
TPAS_COPY_STKRM_MNTHLY.COM
TPAS_SITE_IMPORT_DB.COM TPAS_SITE_IMPORT_STKRM_DB.COM
TPAS_SITE_LOAD_NOR_DB.COM
New
TPAS_RMU_VERIFY_NOR_PRCDR.COM TPAS_RMU_VERIFY_PRCDR.COM
TPAS_RMU_VERIFY_STKRM_PRCDR.COM
o Release notes created for V3.4A.
Page 2
3 KNOWN PROBLEMS and CHANGE REQUESTS
o KNOWN PROBLEMS and CHANGE REQUESTS IN TPAS V3.4A
This section summarizes problems in the TPAS
that have not been fixed for this release. When a reference
to a note is made see the TPAS Notes file AWARD::TPAS
95010902 - SQL ERROR and VMS ERROR codes
All programs need to be checked to ensure that the
VMS and SQL error codes are being passed back to
TPAS_CALC_TRNSFR_PRC and these codes are being passed
back to the calling program.
See Note 55, 55.1, 56, 56.1
95012001 - SEPARATE OBJ LIBRARIES
Create two separate object libraries that have
different TPAS_GET_PART.COBs in them. One will
be used when site installing replies to use PPCS.
The other is for sites not using PPCS. This is so that
when linking without PPCS installed on the system the
undefined warning messages will not be seen.
See Note 58.1, 58.2
95020103 - TRANSACTION REFERENCE NUMBER
Add a transaction number to the record layout of the
audit trail file.
In order to find a specific transaction, the following
data need to be combined to find a unique transaction:
* Date
* part number
* ship/bill to code
a) include this 'Local system reference number' in the
call to TPAS
b) write this reference number to the audit trail file.
95031401 - The Discounts stored in the audit trail file are not
correct.
Note 76.*, 77.*
This looks like the discounts are moved into the audit trail
record fields differently than how they are moved into the
data returned to the calling program.
Page 3
3 KNOWN PROBLEMS and CHANGE REQUESTS - Continued
95032301 - Standardize the Database Population Routines
Note 80.*
Use only SQL Imports for loading ALL the databases.
Remove the RMU/VERIFY from the IMPORT Procedure. - V3.4A
Place the RMU/VERIFY into separate Procedures. - V3.4A
95032302 - LOGIC ERROR IN TPAS_CALC_TRNSFR_PRC using TPAS$SEND_LOCAL_STD
Note 81.*
When TPAS$SEND_LOCAL_STD = N and Corporate Std = 0 then the
program automatically (in para C030_GET_PART) goes to get the
local standard cost. If the local standard is zero then and
error occurs EVEN if the calculation doesn't need a standard
cost.
Changes needed in Para - C045-GET-LOCAL-STD-COST,
C030-GET-PART
C044-VALIDATE-PRICING-PTI-CMM
95033102 - Increase Size of CMM
Increase the size of TPAS$DB.PRICING_TABLE.PRCG_MLP_CALCN_FCTR
to 999.99
This is to accommodate software as APPIX only carries the
2-5-2 part # costs and not the 2-5-2.4 part #
95041305 - TPAS Maintenance
I would like to request that we be able to wild card either
character of the part class on the pricing tables to allow
us to distinguish between hardware and software, pc's....
Since the Product type only works on part numbers on APPIX,
it has limited use for TPAS 2 transactions to the sales subs.
95041701 - TPAS_PRODT_TYPE_UPD_MPF_PRCDR
- Increase processing time, decrease CPRS locking.
This procedure is locking up the CPRS and taking an
inordinate amount of time. Look at the way the records
are selected (cursors) and locked. Add in more commits
if needed.
** OR **
- Move the SOC table into the TPAS Database, change the
TPAS_GET_PART to look up the TPAS_PRODT_TYPE on the
TPAS$DB and get the PART_TYPE from APPIX. Remove all
the code to the APPIX programs to populate the APPIX
TPAS_PRODT_TYPE field.
Page 4
3 KNOWN PROBLEMS and CHANGE REQUESTS - Continued
95060703 - Databases
- Create indices for all possible looks up on
TPAS$DB, TPAS$NOR$DB, TPAS$FUTURE$DB, TPAS$NOR_FUTURE$DB
Doing this will increase performance and record locking
in the TPAS Maintenance Program.
- Set defaults internally for fields with defaults.
95081101 - TPAS Inquiry
- Allow the inquiry to use either TPAS$DB or TPAS$FUTURE$DB.
Make this a user choice. Post DB Select on top of panels AND
on reports.
This has to be done with SPR 95092601
95092601 - TPAS Future Database
- Change the TPAS$FUTURE$DB tables to remove the "future" from
the table name. Change all associated sqlmod code.
This will enable the re-use of INQUIRY and MAINTENANCE code
to be used on either database.
This needs to be done for SPR 95081101
95092602 - TPAS Transfer Area Table and Business Type Table.
- Take the following fields from the Transfer Area Table and
Place them on the Business Type Table:
Below_std, Rbill_ind, DB_FND_PRT_IND, Cntry_Area_NOR,
Cntry_cd, Purch_cur
All code access these fields will change.
This will decrease data redundancy and increase the ease of
maintenance.
------------- or ---------------------------
Modify the maintenance module to:
1) If transfer area is changed then update
that records with all the settings of established
records with that transfer area.
2) If the transfer area is not changed then update all
records with the same transfer area with the
new settings.
95111401 - Corporate Parser in TPAS_GET_PART.COB
- When sending in a part with the revision level then the
parser sends back an error. Should just drop the rev level
when looking up on APPIX. Parser should be ok, check the
code written around it.
Page 5
3 KNOWN PROBLEMS and CHANGE REQUESTS - Continued
96052201 - LIB$SPAWN from a Captive Account
- Bill Breen
- LIB$SPAWN needs to be upgrade (with PACE Compliency)
with the switches allowed for doing a LIB$SPAWN from
a captive account.
TARGET Call 204104
TPAS_CALC_TRNSFR_PRCDR.COB
TPAS_ZSC_PART.COB
TPAS_XCLDD.COB
TPAS_CTAX_SCHED_RUN_JOBS_PRCDR.COB
TPAS_CTAX_MAILING_REPORT_PRCDR.COB
96052401 - Year 2000
- Father Time
- Test all programs, especially those that do a SYS$BINTIM or such,
under a VMS machine that has date set into Fiscal Year 2000
(Jul 1, 1999 to Dec 31, 1999) and again in Calendar year 2000.
Change the following programs to test date and use "20" in the
century field if system date is > 31-Dec-1999. If century is
used for a Fiscal Date then the check should be >= 4-Jul-1999
(This is Fiscal Day 1 in FY 2000)
96070202 - Send a status flag back to the command stream from
TPAS_DB_CHNGS_RPT_PRCDR.COB.
Change the TPAS_XPORT_DB_PRCDR.COM to check switch.
- Lois Magni
96071601 - Change the logic to NOT price via Corp MLP
- Corp Tax, Tracy Walker
- Remove the 'M' pricing code from the pricing table as well
as all the pricing logic for pricing from Corp MLP.
That would be TRNSFR_PRCG_CD = M, H, and I
The logic for J and K would become
"If TRNSFR_PRCG_CD = 'O'and Order MLP <= 0" and
"If TRNSFR_PRCG_CD = 'G'and Order MLP <= 0"
respectively.
96121701 - Change the TPAS Maintenance to allow up to 999.99 % on
the PDA.
- Tracy Walker
Page 6
4 ADDITIONAL INSTALLATION CONSIDERATIONS
4.1 Installation Procedure Requirements
Make sure that all questions asked during the install are answered ahead of
time. If any changes to default logicals are required then edit the
TPAS$COM:TPAS_LOGICALS.COM and the SYS$MANAGER:TPAS$STARTUP.COM.
The program translate the logicals using the logical name table in VMS order:
PROCESS, JOB, GROUP, SYSTEM and LNM$TPAS
5 REPORTING SOFTWARE PROBLEMS
Complete and concise information will help Digital give accurate and
timely service to software problems. Experience shows that many SPRs
do not contain sufficient information to duplicate or identify the
problem. When you prepare to submit an SPR, please do the following:
o Describe as accurately as possible the state of the system
and the circumstances when the problem occurred. Include in
the description the version number of TPAS being used.
Illustrate the problem with specific examples.
o Reduce the problem to as small a size as possible, preferably
to a program unit of 30 source lines or fewer.
o Remember to include listings of any command files, relevant
data files, CDD record definitions, and so on.
o Place the problem on the notes file, AWARD::TPAS and mail
a copy to ACADMY::QCA_ADMIN.
o Report only one problem per SPR. This will facilitate a
faster response.
|