3101: Status row for item 'HRSSA/60557', activity
Posted: Wed Jan 02, 2013 5:00 am
Error displayed in the approval notification received by the approver: item 'HRSSA/51689', activity ID '268165' does not exist Error in the notification It is happening for 2 Special Information fired from a custom function: Mission Request and Expenses claim.
Steps:
1/ XX Employee Self-Service (VA Employee Number 3137)
2/ XX Special Information
3/ Create a new record
4/ On the Review Page, See the following Approvers
3 approver HR People type
1. Approver (SKSM)
2. For Your Information (SKSM)
3. For your Information (PPTP)
5/ Submit to Approval
6/ Log in as the approver and see the notification id 4529715 with no error from VA to SKSM
7/ See the same notification witht the error
3101: Status Row for item 'HRSSA/51689', activity ID '268165' does not exist.
Main Information collected:
BC4J: oacorestd.rar
Ame log: AME_EXCEPTION_LOG.XLS
File versions:
$Header pesitapi.pkb 120.0.12000000.2 2007/04/10 06:15:59 pdkundu noship $
$Header pesitapi.pkh 120.1.12000000.2 2007/04/10 06:54:21 pdkundu noship $
$Header pesitasd.sql 120.0.12000000.1 2007/01/22 04:29:06 appldev noship $
/* $Header: otamewkf.pkb 120.1 2005/06/09 04:13 dbatra noship $ */
/* $Header: otwkflss.pkb 120.0 2005/05/29 07:57:55 appldev noship $ */
Please advice how to correct this problem on production
Steps:
1/ XX Employee Self-Service (VA Employee Number 3137)
2/ XX Special Information
3/ Create a new record
4/ On the Review Page, See the following Approvers
3 approver HR People type
1. Approver (SKSM)
2. For Your Information (SKSM)
3. For your Information (PPTP)
5/ Submit to Approval
6/ Log in as the approver and see the notification id 4529715 with no error from VA to SKSM
7/ See the same notification witht the error
3101: Status Row for item 'HRSSA/51689', activity ID '268165' does not exist.
Main Information collected:
BC4J: oacorestd.rar
Ame log: AME_EXCEPTION_LOG.XLS
File versions:
$Header pesitapi.pkb 120.0.12000000.2 2007/04/10 06:15:59 pdkundu noship $
$Header pesitapi.pkh 120.1.12000000.2 2007/04/10 06:54:21 pdkundu noship $
$Header pesitasd.sql 120.0.12000000.1 2007/01/22 04:29:06 appldev noship $
/* $Header: otamewkf.pkb 120.1 2005/06/09 04:13 dbatra noship $ */
/* $Header: otwkflss.pkb 120.0 2005/05/29 07:57:55 appldev noship $ */
Please advice how to correct this problem on production