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

Conference acadmy::tpas_notes

Title:Transfer Price Administration System
Notice:Conference has moved to ACADMY::TPAS_NOTES
Moderator:ACADMY::MAGNI
Created:Wed Jul 01 1992
Last Modified:Fri Mar 21 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:102
Total number of notes:459

17.0. "Local Get Part, what is it supposed to look like??????" by NLFDC::HOOG (Errare systemus est.......) Mon Aug 03 1992 13:02

    Paragraph 4.3.1.5 of the Functional Design document states about the
    process TPAS_GET_XCPTN_PART: 'This process will send a call out to a
    locally developed piece of code. This locally developed piece of code
    retrieves the part data from the local data file, EG INCMS in MAXCIM'.

    Could you give some more information on what you expect this locally
    developed piece of code to look like? I'm thinking of details like:
    - should it be a shared image or a linked-in module?
    - should parameters be passed by value, by reference or by descriptor?
    - should the Part Type apply to some kind of standard (for example
      would it be a problem if the returned part type would be 'QQQ', which
      of course isn't a valid value)?
    - is 0.00 a valid value for the returned MLP or standard cost?
    - what kind of error code would you expect?
    - etc.

    I realize that I might be asking for to much detail in this (early?)
    stage of the project, but if the information is available, please give
    it to us!

    Thanks,
	Andr� van 't Hoog (F&D IS, JGO)

T.RTitleUserPersonal
Name
DateLines
17.1Another question on local get partAYOU73::CMCLAUGHLANThu Aug 06 1992 10:3325
    I don't have any answers to your questions but I would also like to
    know them
    since Ayr are currently doing the programming for TPAS.

    Another point I would like to make is that the Part Number which is passed
    to the Local Get Part should be the same one that was input to TPAS
    rather than the DEC Standard 12 Formatted part.  I see the process as:

     1.MAXCIM Format of Part Number passed to TPAS

     2.Part Number converted through DECSTD 12 Parser Software

     3.Call TPAS_GET_PART with DEC STD 12 Format part as input and if
       failure call TPAS_GET_XCPTN_PART and local code passing MAXCIM Format of
       Part Number as input.

    In Ayr I believe the MAXCIM Format to be the Unaligned Part which is
    produced by the Parser so this could possibly be used as input to
    TPAS_GET_XCPTN_PART but using the original Part Number entered would ensure
    that we had the right one.

    Is this acceptable to the TPAS team and other Implementation Sites?

                                Regards
                                     Christine McLaughlan (AYO IM&T)
17.2Good point!NLFDC::HOOGErrare systemus est.......Fri Aug 07 1992 05:0510
>    Another point I would like to make is that the Part Number which is passed
>    to the Local Get Part should be the same one that was input to TPAS
>    rather than the DEC Standard 12 Formatted part.

    I fully support this statement!

Regards,
    Andr� van 't Hoog (F&D IS, JGO)

17.3long overdue responseAWARD::MAGNIEWIS - APPIX/FMAP in MSO2Fri Aug 14 1992 10:3314
The physical design document for the 'logi module' piece of the code 
has been released and is in TPAS$PUBLIC. This document should answer your
questions.

re: .0 -> The TPAS_GET_XCPTN code was remove from the functional design 
	  by the TPAS businees people here in Corp. Instead the parts
	  must be on APPIX. If the part on APPIX has a zero standard cost
	  the TPAS code will call to a local code to obtain the local
	  standard cost.

re: .1/.2 ->  The call to the local code, now TPAS_GET_LOCAL_COST, will
	  send the part number as received by the sites program. It will not
	  send the local code the parsed part number. 
17.4TPAS_GET_LOCAL_COSTAYOV29::JMCDOWALLTue Sep 08 1992 10:1719
    
    The Physical Design document specifies the TPAS_GET_LOCAL_COST should
    open the local file, get thencost and then close the file for each part
    number passed to it.  
    
    The time taken to do this for each part number could be quite a while
    especially if the client server is down and this module is called for
    all part numbers.
    
    Therefore, we are considering opening the local file (INCMS) in our
    top level module which calls TPAS which will open and close INCMS only
    once.
    
    Any comments around this suggestion!
    
    
    Regards
    Josephine (7823 3162)
                                 
17.5Part Must be on APPIX/AMP with zero std costAWARD::MAGNIEWIS - APPIX/FMAP in MSO2Wed Sep 09 1992 13:4815
Josephine,

   The TPAS_GET_LOCAL_COST will only be called if the part IS found
   on APPIX (via Client/server) or AMP2 (local APPIX file) AND is
   using standard cost to calculate the transfer price AND the APPIX/AMP2
   record has a standard cost of zero. 

   If the part is not found on APPIX or AMP2 the TPAS_CALC_TRNSFR_PRC
   returns a fatal error to the calling program.

   In TPAS_GET_LOCAL_COST, however you want to deal with opening and
   closing you data files is fine. The only this the TPAS_ZSC_PART cares
   about is the return of a standard cost.

Lois
17.6What to do if the part doesn't exist on the local parts file?NLFDC::HOOGVeni, vidi, victim.....Tue Oct 27 1992 05:379
    I have another question about TPAS_GET_LOCAL_COST. If it can't find the
    part number in the local parts file, should it return a standard cost
    of zero or is it possible to return something in the fields PART_NUMBER
    or STD_COST indicating that the part could not be found?

    Thanks and regards,
	Andr� van 't Hoog (F&D IS, JGO)

17.7Send back 0 std costAWARD::MAGNIIM&T - 223-9837Tue Oct 27 1992 14:0116
  Andr�,

  If your local parts file doesn't have a standard cost for the part
  then return zero. The TPAS_GET_ZSC program will send back the 
  approriate error message to let you know to populate your local database
  with the standard cost.

  Could you describe the situation that would occur when the part 
  you send into TPAS_CALC_TRNSFR_PRC cannot be found on your own database ?
  Would this be using MAXCIM, having the part on INPMS but not on INCMS.
  If so then, I would definately send back a zero standard cost. Then, when
  your local people go to enter the local standard cost they will find the 
  part not found and add it.

  Regards,
  Lois
17.8If it ever happens, we'll send back zero....NLFDC::HOOGVeni, vidi, victim.....Wed Oct 28 1992 08:2122
    Lois,

    Thank you for your quick response. B.t.w, we are not using MAXCIM! Our
    local parts file is in a system called DMS (Distribution Management
    System).

    In theory it will never happen that we send a part number to TPAS which
    is not known in our own parts file (because it is impossible to enter
    an order with an unknown part number). Therefor in theory the 'local
    get part' can always find something in the local parts file. However, I
    want to be sure that if for some mysterious reason a part is sent to
    TPAS, which is unknown on our local parts file, the 'local get part'
    routine will actually send something back which can be handled properly
    by TPAS. Anyway, according to your statement the best thing to do is to
    let the 'local get part' module send back a standard cost of zero,
    which will cause the main TPAS module to return with an error to the
    calling program(?).

    Regards,
	Andr�

17.9error is sent backAWARD::MAGNIIM&T - 223-9837Wed Oct 28 1992 08:5114
   Andr�

  �  by TPAS. Anyway, according to your statement the best thing to do is to
  �  let the 'local get part' module send back a standard cost of zero,
  �  which will cause the main TPAS module to return with an error to the
  �  calling program(?).

  It does send back a fatal error to the calling program

 %APPIX-F-STDCOSTNOF, STD COST is ZERO, Transfer Price cannot be calculated


 Then in your calling program capture this and exit appropriately.