Last updated on APRIL 07, 2016
Applies to:PeopleSoft Enterprise FIN Project Costing - Version 8.4 to 9.2 [Release 8.4 to 9]
Information in this document applies to any platform.
Enterprise, Project Costing, 8.4, 8.8, 8.9, 9.0, 9.1
This document was previously published as Customer Connection Solution 201068181
1)As I understand the process, each time the app engine is executed to bring in estimates from Time & Labor (or the publish process is run in Time & Labor), the first thing that occurs (or closely thereto) is that all existing TLA rows in the PROJ_RESOURCE table are deleted. Subsequent to this deletion, all TLA rows from Time & Labor are then posted to the PROJ_RESOURCE table.
2) Given the preceding understanding, allow me to use an illustration to further explain my understanding. In a perfect world a mistake would never be made and all of the TLA rows would be confirmed and therefore, would turn into PAY rows. At this point in time then, there would be zero TLA rows. Thus, TLA rows always represent labor 'in the pipeline'. Is this right?
3) If so, is there any way to strand a TLA row? For instance, could you have a situation where a TLA row is never confirmed nor deleted in Time & Labor and therefore this process would delete it but keep bringing it back even though it is for a period no longer current?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms