| Yan Noi,
If this requirement is for the TPAS then please send two datafiles, as
described below, to ACADMY:: and send a mail message to me. We have a
process for comparing the Part Type, MLP and Standard Cost.
Lois
Attached please find the required filenames, file layouts and resultant
report layout for the Part File reconcilliation process.
The File Names
===============
We will use the following Layout
TPAS_xxx_RCNCLTN_####.DAT - The data file
TPAS_xxx_RCNCLTN_####.CTRL_DAT - The Control File
Where xxx is the site code and #### is a serial number.
Example: TPAS_GAO_RCNCLTN_0001.DAT
TPAS_GAO_RCNCLTN_0001.CTRL_DAT
The file Layout for TPAS_xxx_RCNCLTN_####.DAT is:
================================================
RCNC_PART_ID PIC X(9). - class/basic/variant
RCNC_PART_UOM PIC X(2).
RCNC_PART_TYPE PIC X(3).
RCNC_STD_COST COMP-2.
RCNC_MLP COMP-2.
* RCNC_BUSINESS_SOURCE PIC X(03) - Specific for MIFBOM Data
* RCNC_ORDER_SOURCE PIC X(03) - Specific for MIFBOM Data
* --> CAN LEAVE BLANK
The file layout for TPAS_xxx_RCNCLTN_####.CTRL_DAT is:
=======================================================
TPAS_CTRL_RCRD. Example
CTRL_RCRD_FILENAME. -------
CTRL_RCNCLTN_SYS_NAME PIC X(05). TPAS_
CTRL_RCNCLTN_SITE PIC X(03). GAO
CTRL_RCNCLTN_FILENAME PIC X(09). _RCNCLTN_
CTRL_RCRD_SERIALNO PIC 9(04). 0001
CTRL_RCRD_TOTAL_RCRDS PIC 9(10). 0000067932
CTRL_RCRD_CREATE_DATE PIC 9(12). 199212011220
We will then validate the information as follows:
1. find the part number on the MPF
If not found
then re-format via DECSTD 12
find the part number on the MPF
if not found then
populate error record with RCNC
data. Move '56' into ERROR_CODE1.
(Part not found on MFP)
Write error record.
goto read next record
end if
end if
2. Compare Part Type
If different populate error record with APPIX data and RCNC
data. Move '7' into ERROR_CODE1.
(Invalid Part Type)
3. Compare STD Cost
Multiply RCNC_STD_COST by 1 giving WS_RCNC_STD_COST 9(8)v9(4)
defined with appropriate field size prior to comparison.
Round APPIX_STD_COST 9(8)v9(6) to APPIX_STD_COST_RND 9(8)v9(4)
before comparision.
If the difference between the two fields is < 0.01 then
it is NOT in error.
If different populate error record with APPIX data and RCNC
data. Move '159' into ERROR_CODE2.
(APPIX Std Cost different from RCNC Std Cost)
4. Compare MLP
Multiply RCNC_MLP by 1 giving WS_RCNC_MLP 9(8)v9(4)
defined with appropriate field size prior to comparison.
Round WS_RCNC_MLP 9(7)v9(4) to WS_RCNC_MLP_RND 9(16)v9(2)
before comparision.
If the difference between the two fields is < 0.01 then
it is NOT in error.
If different populate error record with APPIX data and RCNC
data. Move '160' into ERROR_CODE3.
(APPIX MLP different from RCNC MLP)
5. If error_found then Write Error record.
6. Reset switches and clear error record.
Read Next Record
Then we will create the following report:
The REPORT Layout is attached.
===============================================
The fields are
--------------
Header Information:
SERIAL NUMBER: #### - File's serial Number
SITE: xxx - File's site code
dd-mmm-yy - Run Date
Detail Line Information:
Source 'APPIX' - for APPIX Record
xxx - Site code from file name
Part Number - APPIX_PRT_ID
- RCNC_PART_ID
Unit Of Measure - APPIX_UOM
- RCNC_PART_UOM
Part Type - APPIX_PART_TYPE
- RCNC_PART_TYPE
Standard Cost - APPIX_STD_CST_RND
- RCNC_STD_COST
MLP - APPIX_MLP
- RCNC_MLP_RND
Error - Error Messages from SOC$DB
The following two fields/literals will be printed ONLY if there is data
conatined in the fields.
BUSINESS SOURCE - BUSINESS_SOURCE
ORDER SOURCE - ORDER_SOURCE
TPAS_MPF_DB_RCNCLTN.RPT APPIX MPF Database Reconciliation Report PAGE: 1
SERIAL NUMBER: #### SITE: xxx dd-mmm-yy
PART Unit of Part Standard MLP
Source Number Measure Type Cost Error
====== ============= ======= ==== =============== ======================== ========================================
BUSINESS SOURCE: xxx
APPIX xx-xxxxx-xx xx xxx 99,999,999.9999 9,999,999,999,999,999.99 x(40)
xxx xx-xxxxx-xx xx xxx 99,999,999.9999 9,999,999,999,999,999.99 x(40)
ORDER SOURCE: xxx ^^^ ^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^ x(40)
APPIX xx-xxxxx-xx xx xxx 99,999,999.9999 9,999,999,999,999,999.99 x(40)
xxx xx-xxxxx-xx xx xxx 99,999,999.9999 9,999,999,999,999,999.99 x(40)
ORDER SOURCE: xxx ^^^ ^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^ x(40)
APPIX xx-xxxxx-xx xx xxx 99,999,999.9999 9,999,999,999,999,999.99 x(40)
xxx xx-xxxxx-xx xx xxx 99,999,999.9999 9,999,999,999,999,999.99 x(40)
ORDER SOURCE: xxx ^^^ ^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^ x(40)
APPIX xx-xxxxx-xx xx xxx 99,999,999.9999 9,999,999,999,999,999.99 x(40)
xxx xx-xxxxx-xx xx xxx 99,999,999.9999 9,999,999,999,999,999.99 x(40)
ORDER SOURCE: xxx ^^^ ^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^ x(40)
Sub Total Number of Invalid Records: 99999
Sub Total Number of Records Missing On MPF: 99999
Sub Total Number of Part Type Differences: 99999
Sub Total Number of Standard Cost Differences: 99999
Sub Total Number of MLP Differences: 99999
TPAS_MPF_DB_RCNCLTN.RPT APPIX MPF Database Reconciliation Report PAGE: 2
SERIAL NUMBER: #### SITE: xxx dd-mmm-yy
Total Number of Records Validated: 9999999
Total Number of Invalid Records: 9999999
Total Number of Valid Records: 9999999
Total Number of Records Missing On MPF: 9999999
Total Number of Part Type Differences: 9999999
Total Number of Standard Cost Differences: 9999999
Total Number of MLP Differences: 9999999
|
| Lois,
Thanks for your quick response. Actually the cost comparison is
not a requirement for TPAS, it's just a request from my Finance user
some months ago for std setting before TPAS was known to us.
Corporate Cost Accounting sent a mail telling us to feed some files
(INPMS, INCMS and INSSS) to them in order to allow them to compare
the std cost of our plant and that of APPIX. To date, we have also
written a program to extract inhouse data in the format they needed
and sent these feed to them. Yet we have not received the comparison
report from them. I wonder if other plants also faced this problem or
not?
Since TPAS requires the local APPIX_MPS.DAT to be installed, in
order to expedite the use of this database, ZGO MIS wants to look
into using the local APPIX_MPS.DAT to do std cost comparison. In this
way, we are not dependent on a third party for the result. We can run
the reporting as and when we like.
Not to offence you, I am curious why TPAS is duplicating effort for
this report comparison, in that sense that CORPORATE COST
ACCOUNTING has already done it. Please read the mail attached.
I do hope to run the cost comparison ourself and to do that, we need
a TPAS routine to just return the std unit cost. I wonder if the
TPAS development group can look into this request. Otherwise, I hope
MPO can write a program to generate the two datafiles that you have
mentioned in note 20.1 as I am sure it should be useful for those
interested in std cost comparison.
I am sure other plants like TAO, HKO may need this cost comparison
too. I wonder what they think of this ??
Rgds,
Yan Noi
From: MEMIT::NICKSON "A SMILE A DAY KEEPS THE DOCTOR AWAY" 11-DEC-1991 09:49:52.21
To: GIAMEM::TOMAIOLO,GIAMEM::BJOHNSON,GIADEV::FALK
CC: NICKSON
Subj: bridge document
From: MEMIT::NICKSON "A SMILE A DAY KEEPS THE DOCTOR AWAY" 13-MAR-1991 16:16:17.39
To: NICKSON
CC: NICKSON
Subj: MASTER PARTS FILE BRIDGE DOCUMENT
MASTER PARTS FILES COMPARISON SYSTEM
MAXCIM Bridge Documentation
June 24,1987
INTRODUCTION
------------
The Master Parts File Comparison System (MPF) compares what a
plant has on it's master parts file and what is on file at corporate,
as administered by APPIX (formally EPLS).
Because manufacturing plants are using different systems to collect
and store their data, corporate manufacturing has developed "bridge" software
which will reduce these different formats to a single file description for
ease of processing at corporate.
BRIDGE SOFTWARE
---------------
The bridge software for plants using the VAX and the MAXCIM system
consists of three pieces:
1. MPFMAXV30.BAS
2. MPFMAXV40.BAS
3. MPFMAXV00.DOC
The bridge software may be copied from:
**************************************************************************
Copy from: MILPND::GRO7:[060TRANS.MPFPLANTS]
**************************************************************************
The use of either MPFMAXV30.BAS and MPFMAXV40.BAS is dependent upon
the version of MAXCIM being utilized at your site. MPFMAXV30 is for those
plants running under version 3 of MAXCIM, and MPFMAXV40 is for those plants
running under version 4 of MAXCIM.
MPFMAXV00.DOC is this document.
The need for "bridge" software for MAXCIM is because individual plants
have determined that they have need of special fields within certain files.
The result is no standard files can be assumed for the MAXCIM system.
The bridge software serves two purposes. The first is to create
standard files that will be incorporated into the MASTER PARTS FILES COMPARISON
SYSTEM (MPF) for analysis. The second reason is that to use the MPF system,
part numbers must conform to DEC STD 12 format specifications. The bridge
software does this conversion.
PLANT RESPONSIBILITY
--------------------
Either of the two bridge programs serve as a starting point for an
individual plant. These programs give you the format for the output files
however, what are called input files within these programs and their associated
fields must be reviewed by the plant. The plant may have to make changes in the
input structure of these programs and/or the code transferring data from the
input files to the output files, if necessary. As always, ME Finance DIS is
willing to help any plant to accomplish this goal.
The plant, perhaps in concert with ME Finance, should decide how the
three output files, ZZISSS.DS12,ZZICMS.DS12, and ZZIPMS.DS12 are to be trans-
mitted to corporate. Either a network transfer of the disk files or the sending
of a magnetic tape is acceptable.
If sending files, they files should be networked to:
****************************************************************************
Send to: MILPND::GRO7:[060TRANS.MPFINBOUND]
****************************************************************************
Please be aware that the MPF creates reports for use by the corporate
finance community. You, of course, are welcome to these reports, however an
extract output file is also created during the execution of the MPF with
plant specific part numbers and their associated data. This file could be used
by an individual plant to create its own report.
CONTACT:
--------
Finance - Diane Nickson
ML01-4/F31
DTN 223-3701
MEMIT::NICKSON
|