| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 56.1 | Error Message Library Text not perfect | AWARD::MAGNI | IM&T - 223-9837 | Mon Jan 09 1995 13:15 | 26 |
| George,
>> %APPIX-I-PARTREFORM, Part ID has been reformatted and found on file
>> How can the part be 'found on file' if there is no file?
The TPAS software utilizes the APPIX Message file that was created for PPCS.
As you can see the message text is not 100% perfect.
What happened here was that the part was re-formated into DECSTD 12, giving
the above error message. The part was not found on APPIX, but because the
receiving site was coded as "DB_FOUND_PART_INDCR = 'N'" the part need not be
on APPIX to be priced. Therefore when looking to price that part a standard
cost had to be found from the local database, thus the second message about
'-W-SCMLPFROMLOCAL'. As the part was not found on APPIX the TPAS_PRODT_TYPE
defaults to "***" and then the pricing table is searched for the correct
record. As the prcing table does not contain a record with PRODT_TYPE = ***
and Part CLass = "**" or the part class of the part you sent in, the error,
"%APPIX-F-PTICMMSELECT," is returned. This is the Fatal error that caused the
price not to be calculated.
If a record is put on on the TPAS$XCLDD_DB Pricing Table using TPAS_XCLDD.EXE
and the transaction is run through again, then the part will be priced. Using
the TPAS_XCLDD.EXE will notify Corporate Tax that a record was added and that
they should add a records for the "***" Prodt Type and Part Class for the rest
of the world.
|
| 56.2 | 'APPIX file not found' different to 'Part not found' | FUTURS::TON | | Tue Jan 10 1995 05:46 | 10 |
| Thanks for the explanation, Lois. I was just about to ask why this
behaviour also occurred when I entered a part that was not on APPIX.
I think that I need to be able to tell the difference between 'APPIX file
not available', 'Part not found on APPIX', and PTICMMSELECT. Is this
possible?
DB_FOUND_PART_INDCR sounds interesting. Is it explained in one of the TPAS
documents? why is it set to N? and is it something I can mess around with?
|
| 56.3 | Sales said they don't alway receive Corp Part #s | AWARD::MAGNI | IM&T - 223-9837 | Wed Jan 11 1995 09:44 | 34 |
|
>I think that I need to be able to tell the difference between 'APPIX file
>not available', 'Part not found on APPIX', and PTICMMSELECT. Is this
>possible?
The difference is:
for 'APPIX file not available' you will get the following errors:
If using PPCS -
%SPWY -F-NOSERVER, connection to remote server not available
If using AMPS
%APPIX-F-AMPSFILENOF,AMPS2 SATELLITE FILE NOT FOUND
BUT - Those two Fatal Errors ONLY occur when the SHIP/BILL_TO
location has the DB_FOUND_PART_INDCR = 'Y'
If the TPAS_PRODT_TYPE field is "" and a transfer price
has been calculated you can safely assume the part was
not found or APPIX could not be accessed, as no -F-
error will be returned.
>DB_FOUND_PART_INDCR sounds interesting. Is it explained in one of the TPAS
>documents? why is it set to N? and is it something I can mess around with?
You will find a definition for this in the user doc, physical and
functional designs. The TPAS_II_LOGIC_FLOW_DGRM.PS also shows the
use.
Basically, this is a field set on the TRNSFR_AREA_TABLE by
Corporate Tax to indicate if this area receiving material needs to
receive only parts found on the Corporate Parts Master (APPIX).
During the preliminary analysis for TPAS II the sales organizations
said that all their parts numbers they received were not on the
Corporate Parts Master. The manufacturing organizations must have
the parts they receive on APPIX. Therefore, Tax added this switch,
so that the transfer price will be calculated even if the part is
not on APPIX for areas not needing Corporate identified parts.
|