Problem Note 55246: SAS® Merchandise Data Integration location load fails with "ERROR: ORACLE execute error: ORA-20001: P_GET_TIME_ID: ORA-01403: no data found"
SAS® Merchandise Data Integration location loads might encounter errors similar to the following when new locations are loaded during a change in lv2time:
ERROR: ORACLE execute error: ORA-20001: P_GET_TIME_ID: ORA-01403: no data found
ORA-06512: at "MAXAPP.P_GET_TIME_ID", line 37
ORA-06512: at "MAXDATA.INSERT_LV4_LOC", line 38
ORA-04088: error during execution of trigger 'MAXDATA.INSERT_LV4_LOC'.
The errors are generated because the load runs during a gap in lv2time table and the P_GET_TIME_ID procedure fails. For example, the p_get_time_id procedure generates these errors when the following are true:
- The lv2time_end_date for 2014 is 01/31/2014 12:00:00AM.
- The lv2time_start_date for 2015 is 02/01/2015 12:00:00AM.
- The execution of the location load that contains new locations occurs on 01/31/2014 at 1:00PM.
To prevent this error, do not add new locations to the location input file for a load that occurs during the change in lv2time time.
Operating System and Release Information
| SAS System | SAS Merchandise Financial Planning | Microsoft Windows Server 2003 for x64 | 6.1.3 M6 | | | |
| Microsoft Windows Server 2008 R2 | 6.1.3 M6 | | | |
| Microsoft Windows Server 2008 for x64 | 6.1.3 M6 | | | |
| 64-bit Enabled AIX | 6.1.3 M6 | | | |
| 64-bit Enabled Solaris | 6.1.3 M6 | | | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
A gap might exist between the lv2time_start_date and lv2time_end_date that causes the P_GET_TIME_ID procedure to fail during a location load when a new store is introduced during a load run at lv2time changes.
| Type: | Problem Note |
| Priority: | medium |
| Date Modified: | 2015-03-13 08:59:41 |
| Date Created: | 2015-02-18 09:21:59 |
