| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 33.1 | | NLFDC::HOOG | Veni, vidi, victim..... | Fri Jun 04 1993 05:50 | 4 |
|
Is TPAS V2.0 (including the new database) already available for testing
by local sites?
|
| 33.2 | Release date change ... | AWARD::MAGNI | IM&T - 223-9837 | Fri Jun 04 1993 13:39 | 10 |
| Hot off the Press ...
TPAS V2.0 will not be made available until August and will not need to be
installed until the 1st of fiscal month 3. This is due to business needs
not having to change for July.
A formal announcement will be forthcoming.
Lois Magni
|
| 33.3 | V2.0 - Summary of changes/site IM&T work required | AWARD::MAGNI | IM&T - 223-9837 | Wed Jun 16 1993 10:34 | 120 |
| =========
TPAS V2.0
=========
SCHEDULED DATE FOR DELIVERY TO SITE: 29 JULY 1993
====================================
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.
Any other changes done will be added to the release notes. If there are any
questions contact either:
Lois Magni, WW M&L P&P IM&T AWARD::MAGNI
Paul Cantin, WW M&L P&P IM&T AYRPLN::CANTIN
Barbara Wilfand, Corporate Tax @MSO
Tracy Walker, Corporate Tax POWDML::WALKER
|
| 33.4 | Functional Spec TPAS I V2.0 | AWARD::MAGNI | IM&T - 223-9837 | Tue Jun 22 1993 09:22 | 5 |
| The final version of the TPAS I V2.0 functional specification is available on
AWARD::TPAS$PUBLIC:FUNC-DESIGN-RELEASE-2.PS
|
| 33.5 | AMPS Changes to support TPAS V2.0 | AWARD::MAGNI | IM&T - 223-9837 | Fri Jul 23 1993 12:56 | 88 |
| From: ACADMY::QCA_ADMIN "M&L IM&T Application Support Admin Services 22-Jul-1993 1559" 22-JUL-1993 16:03:32.32
To: @AMP
CC: LIZ,LOIS,AYRPLN::CANTIN,QCA_ADMIN
Subj: *** Upcoming APPIX changes *** Plse forward to your technical contact.
****** PLEASE FORWARD THIS MESSAGE TO YOUR TECHNICAL CONTACT******
Attached is a notice to all APPIX Users concerning changes in:
ECCN code
TPAS Product Type Code
AMPs
Please read thoroughly to understand the changes being implemented
through the next several weeks.
Contact ACADMY::QCA_ADMIN with any questions or concerns.
********************************************************************************
NOTICE TO USERS - ECCN ASSIGNMENT CHANGES
*****************************************
The Corporate Export group has requested changes to the logic which assigns
ECCN codes.
In the current implementation, the ECCN assignment is based on the harmonized
code and other information. When the harmonized code is blank for a
particular part number, then, the ECCN code is also left blank. In the
modifications which will be implemented on July 30, the ECCN could be assigned
a non-blank code even if the harmonized code is blank.
Users of the ECCN codes are urged to review their application programs to make
sure the programs do not assume that the ECCN will be blank when the
harmonized code is blank.
********************************************************************************
NOTICE TO TPAS USERS
********************
In support of TPAS V2.0 release for the end of August a data field has been
added to the APPIX Database. This field, TPAS_PRODT_TYPE_CD, will be used
for calculating the Transfer Price in place of the Part Type Code. This
data will be supplied to the TPAS software via PPCS and the AMPs data file. It
will be sourced from the Corporate Tax Organization.
Over the next several weeks this field will be populated and distributed to
AMPs users via the nightly AMPS feed field.
********************************************************************************
NOTICE TO AMPS USERS
********************
On August 1, the ECCN codes will be loaded into the APPIX Database.
Due to the large number of ECCN changes that are expected, an unusually
large AMPS file will be produced. The file, which will be distributed on
Tuesday, August 3, is expected to contain approximately 150,000 records and
be approximately 75,000 blocks.
On August 3 through August 14 the TPAS Product Type Code will be gradually
populated via specific part classes. The AMPS files, which will be distributed
August 4 through August 15, are also expected to be larger than normal. The
files sent over this 2 week period will contain approximately 130,000 records,
and will be approximately 75,000 blocks each. Assuming no problems with
production occur, the files will be 5619AP.MPS - 5628AP.MPS.
AMPS users are encouraged to ensure there is sufficient space allocated
on their disks to accommodate these files. The updates should be completed
on August 15'th.
Also, NEW AMPS Software is being provided by the APPIX organization. The
AMPS_ONL_PRCDR program will now display the new TPAS Product Type Code.
The AMPS_UPDT_PRCDR.COM, AMPS_UPDT_PRCDR.EXE, AMPS_ONL_PRCDR.EXE,
MPF_AMPS_ONL_PRCDR_2.EXE and SERIAL_CTRL.EXE have been updated to use
logicals for accessing files. This enhancement will allow sites to separate
the data files from the executable.
*******************************************************************************
*** *** NOTE - BY AUGUST 3 *** ***
*** ***
*** The above programs WILL BE SENT to your site by July 27 and placed ***
*** into the same area that the AMPS Data files are sent. Please copy the ***
*** AMPS_UPDT_PRCDR.COM and *.EXE files to the appropriate location on ***
*** your system. ***
*** ***
*** Also, modify AMPS_UPDT_PRCDR.COM. Changing the new logicals, ***
*** AMPS$EXE and AMPS$DATA to point to the correct local directories. ***
*******************************************************************************
|
| 33.6 | TPAS V2.0 schedule/release notes | AWARD::MAGNI | IM&T - 223-9837 | Fri Jul 23 1993 14:50 | 202 |
|
TRANSFER PRICE ADMINISTRATION SYSTEM V2.0
The TPAS V2.0 software changes are in the process of being tested and released.
The TPAS V2.0 software is scheduled to be in place at the sites August 28th.
Attached is the schedule of release of software. Please take time to review
this, create your site's implementation schedule and send a copy to me at
AWARD::MAGNI.
If you have any questions or concerns please let me know.
ATTACHEMENTS:
TPAS V2.0 Release Schedule
TPAS V2.0 Release Notes
The following is the schedule of activities that will be done for the
implementation of TPAS V2.0.
20 Jul 1993 - PPCS changes implemented
** no effect at sites
23 Jul 1993 - AMPs changes implemented
** Sites to ensure new AMPs software in place AND
AMPs command Streams Logicals set.
(see next mail message)
30 Jul 1993 - Release TPAS V2.0 VMS Install to sites for implementation
on 29 August 1993. The following sites have registered
for TPAS V1.0 and will be sent V2.0 install kit.
JGO - Hoog, Eijkhout
ZGOV05 - YNTan, Leannelai, Shirley Quah
STARGL - Moriarty
TANAMI - Tsang KC
POLAR - Terpstra
BBQ - Shastri
GIADEV - Godsay
ESSB - G Conway
HKOVC - Eric Yuen, Kim
KBOMFG - Henderson
TAOVC - David Chien
If you site is not represented on this list please
conact me so we can get the registration process in
place.
Sites to modify local code that call TPAS to
capture new data elements and if needed to direct
code flow, new errors.
03 Aug 1993 - Updates to TPAS_PRODT_TYPE_CD on APPIX
14 Aug 1993 Expect large AMPS Feed.
(see next mail message)
26 Aug 1993 - New TPAS$DB Data files ready for sites to pull.
28 Aug 1993 - TPAS V2.0 running live at all sites
=============
TPAS V2.0
RELEASE NOTES
=============
DEVELOPMENT PLATFORM:
=====================
VMS - V5.5-2
COBOL - V5.0
DECforms - V1.4
RDB/SQL - V4.0B
nMAIL - V9.3
ACMS - V3.2
SCHEDULED DATE FOR DELIVERY TO SITE: 30 JULY 1993
====================================
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
Modify Code calling TPAS to accept new data element.
(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.
Modify Code calling TPAS to accept new data elements and capture errors.
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 will be changed to remove COBOL V5.0 function
UPPER_CASE.
Any other changes done will be added to the release notes. If there are any
questions contact either:
Lois Magni, WW M&L P&P IM&T AWARD::MAGNI
Paul Cantin, WW M&L P&P IM&T AYRPLN::CANTIN
Barbara Wilfand, Corporate Tax @MSO
Tracy Walker, Corporate Tax POWDML::WALKER
|
| 33.7 | template for site implentation for TPAS V2.0 | AWARD::MAGNI | IM&T - 223-9837 | Fri Jul 23 1993 14:51 | 33 |
|
I have been queried on the schedule for the new TPAS V2.0. I have put
together a schedule template that your sites can work from to set up their
implementation schedule.
Schedule your work something like this;
27 July - Put new AMPS software in PRODUCTION. Move new EXEs
and modify AMPS_UPDT_PRCDR.COM to set the AMPS$DATA and
AMPS$EXE logicals.
03 Aug - Provide space to start receiving large AMPS files,
####MPS.DAT, that will be used by update your local
APPIX_MPS.DAT
04 Aug - Put new TPAS V2.0 kit into DEVELOPMENT.
- Start modifing and testing local code that calls
TPAS_CALC_TRSNFR_PRC. Receive the three new fields and
if your local site handles each of the fatal errors
in different ways then adjust for the new fatal errors.
26 Aug - Pull TPAS*.RBR files from ACADMY use TPAS_COPY_MNTHLY.COM
29 Aug - Move TPAS*.RBR into PRODUCTION use TPAS_SITE_IMPORT_DB.COM
- Move modifed local code and TPAS V2.0 into PRODUCTION.
Any questions let me know,
Regards,
Lois Magni
|
| 33.8 | TPAS V2.0 Call | AWARD::MAGNI | IM&T - 223-9837 | Mon Jul 26 1993 11:08 | 30 |
| This is the new call and receiving parameter for TPAS V2.0:
01 SEND_TPAS_REQUEST.
05 SEND_TPAS_REQUEST_PART PIC X(30).
05 SEND_TPAS_REQ_SHIP_FROM_STKRM PIC X(03).
05 SEND_TPAS_REQ_SHIP_TO_STKRM PIC X(03).
******************* RECEIVE PARAMETERS **************************
05 TPAS_RTN_FROM_SITE_CODE PIC X(03).
05 TPAS_RTN_TO_SITE_CODE PIC X(03).
05 TPAS_RTN_TO_PLNT_PNEMNC PIC X(02).
05 TPAS_RTN_FROM_PLNT_PNEMNC PIC X(02).
05 TPAS_RTN_TPAS_PRODT_TYPE_CD PIC X(03). <--Name
05 TPAS_RTN_STD_COST COMP-2. Change
05 TPAS_RTN_MLP COMP-2.
05 TPAS_RTN_CMM COMP-1.
05 TPAS_RTN_BASE_PRICE COMP-2.
05 TPAS_RTN_PRICE_TYPE_IND PIC X(01).
05 TPAS_RTN_DISCOUNT_PERCENT COMP-1.
05 TPAS_RTN_STD_COST_UPLIFT COMP-1.
05 TPAS_RTN_TRANSFER_PRICE COMP-2.
05 TPAS_RTN_STATUS.
10 TPAS_RTN_FACILITY_MSG PIC X(7).
10 TPAS_RTN_PART_STATUS_CODE PIC X(1).
10 TPAS_RTN_ERROR_MESSAGE PIC X(72).
05 TPAS_RTN_STD_CST_TYPE_CD PIC X(01). <--New Field
05 TPAS_RTN_BUSNS_FROM_TYPE_CD PIC X(03). <--New Field
05 TPAS_RTN_BUSNS_TO_TYPE_CD PIC X(03). <--New Field
|
| 33.9 | TPAS V2.0 - 2 new fatal errors | AWARD::MAGNI | IM&T - 223-9837 | Mon Jul 26 1993 11:44 | 17 |
|
The following two new FATAL errors can be returned from TPAS_CALC_TRSNFR_PRC.
They indicate that the TPAS$DB TRNSFR_AREA_TABLE is in error. This problem
will only occur if the TPAS$DB is modified at the site, as a pre-validation
program will ensure the accuracy of the TRNSFR_AREA_TABLE prior to making
it available to sites.
MISSNGBUSTYP <Business Type Code for Ship To location is Blank>
ACTION: Check the BUSNS_TYPE_CD field on TPAS$DB:TRNSFR_AREA_TABLE
for Transfer Area Code in question. This field should not
be blank. Contact ACADMY::QCA_ADMIN
NOTUNQBUSTYP <Business Type Code is not unique for Ship to Location>
ACTION: Check the BUSNS_TYPE_CD field on TPAS$DB:TRNSFR_AREA_TABLE
for Transfer Area Code in question. This field should be
unique for the TRNSFR_AREA_CD field. Contact ACADMY::QCA_ADMIN
|
| 33.10 | TPAS V2.0 has been released | AWARD::MAGNI | IM&T - 223-9837 | Mon Aug 09 1993 23:11 | 21 |
| By now you should have all received the TPAS V2.0 kit (TPAS020.A).
If not please send mail to AWARD::MAGNI,ACADMY::QCA_ADMIN indicating
where you want the new kit sent. Remember this new software MUST be
installed to work with the new TPAS Data File scheduled for Aug 29
implementation.
A test RBR file is available to pull. You can obtain it by
$ COPY AWARD::TPAS$PUBLIC:TPAS_DB_0058.RBR *
Copy this file over and load it into your TEST TPAS.RDB database by using
the TPAS_SITE_IMPORT_DB.COM.
I have only heard back from one site on their implementation schedule.
Please send your schedule letting me know if you will be making the Aug 29th
implementation date. If you foresee any problems please let me know
immediately.
|