Clarity

  • 1.  Charge Codes vs Input Type Codes

    Posted Sep 17, 2012 08:39 AM
    Dear all,

    I am trying to understand the difference between Charge Codes and Input Type Codes. I read the help docs and gather that Charge Codes represent breakdown of work, and Input Type Codes represent the work assigned / done by a resource, but somehow I am not able to visualize the same in a project / investment scenario, as in how to decide on Charge codes and Input type codes, are there any best practices involved?

    Could you please help me understand this with an example scenario.

    Thanks in advance.

    Best regards,
    msastri


  • 2.  RE: Charge Codes vs Input Type Codes

    Posted Sep 17, 2012 08:51 AM
    Typically charge codes are used to indicate if a task (or a project) is billable/chargeable and if it is whether it is capital expenditure or operational expense.

    Input code is somewhat similar, but looking at it from the resource side is it normal work hours, overtime hours, time off, sick time, training time etc.

    In order to have timeentries financially processed after posting and the go all the way to WIP the time entries must have valid charge codes and input codes (either inherited from tasks and resources) or entered on the time sheet.
    Then in order to be financially processed there must be matching matrix rows (though the rate and cost can be 0 if it not billable work).

    Martti K.


  • 3.  RE: Charge Codes vs Input Type Codes

    Posted Sep 17, 2012 09:10 AM
    Thanks very much Martti K. That helps.

    Just to confirm my understanding;

    So, If we consider,let's say Training as an operational expenditure, then typically for a Resource who has spent effort in training; his timesheet would have a "Training" code against the Input Type Code field and an "Operational expenditure" code against the Charge code field. Is that right.

    Best regards,
    msastri


  • 4.  RE: Charge Codes vs Input Type Codes
    Best Answer

    Posted Sep 17, 2012 12:05 PM
    Yes.

    Martti K.