You’re offline. This is a read only version of the page.
894
This is an interesting one. Using the Project Closing window, anytime I select a particular contract, the prompt "Please close the Project Closing window first to complete the closing process" appears.
It's just this contract
I've cleared all activity tables (including PA000001) & cannot for the life of me figure out what's stuck with this project.
Any $.02 would be much appreciated.
Hi Kyle,
it might not be an open Project window that's causing the message to pop up, but an actual record that is locked in a table.. could you please check if there is anything in the Dex_lck table ?
When looking up the contract number in the PA Closing window, GP goes thru quite a range of SP's to do validation, and it seems to fail at one of them..
Before you even get a chance to list the contracts, this is what runs in the background:
/* Date: 04/14/2021 Time: 14:20:47
stmt(149028504):*/
{ CALL DYNAMICS.dbo.zDP_SY01600SS_1 ( 'sa', 'Fabrikam, Ltd.', 'PA_Contract_Lookup', 'Contract_Lookup' ) }
/* Date: 04/14/2021 Time: 14:20:47
stmt(148976944):*/
{ CALL TWO.dbo.zDP_SY00700SS_1 ( 'Contract Lookup' ) }
/* Date: 04/14/2021 Time: 14:20:47
stmt(149022176):*/
SELECT COUNT(PACONTNUMBER) FROM TWO.dbo.PA01101
/* Date: 04/14/2021 Time: 14:20:47
stmt(148959160):*/
{CALL TWO.dbo.zDP_PA01101F_1(NULL,NULL)}
Then comes a huge SELECT query that ends with :
SELECT TOP 25 * FROM TWO.dbo.PA01101 WHERE PACONTNUMBER = 'ADAMPHOTEL' ORDER BY PACONTNUMBER ASC
Followed by another one with :
FROM TWO.dbo.PA01101 WHERE PACONTNUMBER = 'COHONET' ORDER BY PACONTNUMBER ASC
As next comes several validations which might be one of the culprit to your pop-up:
/* Date: 04/14/2021 Time: 14:20:49
stmt(148929688):*/
{ CALL TWO.dbo.zDP_PA000001SS_1 ( 7, 'COHONET' ) }
/* Date: 04/14/2021 Time: 14:20:49
stmt(149021272):*/
BEGIN DECLARE @num int EXEC TWO.dbo.zDP_PA000001SI 'sa', 7, 'COHONET', 7, 0, @num OUT SELECT @num END
/* Date: 04/14/2021 Time: 14:20:49
stmt(149027600):*/
{ CALL DYNAMICS.dbo.zDP_SY02100SS_1 ( -1, 258, 6, 0 ) }
/* Date: 04/14/2021 Time: 14:20:49
stmt(149032120):*/
{CALL TWO.dbo.zDP_PA11900F_1(NULL,NULL,NULL,NULL)}
/* Date: 04/14/2021 Time: 14:20:49
stmt(148959160):*/
{ CALL TWO.dbo.zDP_PA01101SS_1 ( 'COHONET' ) }
/* Date: 04/14/2021 Time: 14:20:49
stmt(148926976):*/
{CALL TWO.dbo.zDP_PA01201F_9('COHONET','','COHONET','ÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞ')}
/* Date: 04/14/2021 Time: 14:20:49
stmt(148955544):*/
{ CALL TWO.dbo.zDP_RM00101SS_1 ( 'COHOWINE0001' ) }
I'd check the PA11900 table to see if there is any previou left over records, as this is the PA Project Closing HDR Work table, or by that matter, any PA1190x tables, as they are all linked to the PA closing process and should be empty in normal time.
You could also run some checklinks across the PA module to see if there are any inconsistencies.. of course after full backup :-)
PS: if you have GPPT, enable DEXSQL trace right before opening the lookup for the Contract #.
Share
Report
All responses (
Answers (
