Search This Blog

Wednesday, January 5, 2011

SAP Note 1422843 - Wrong deletion date in spool request

Version: 31
Validity: Valid Since 03.02.2010

Symptom
Newly created spool requests have a deletion date of 2099/12/31 or 2100/01/01 regardless of the retention period specified during creation.
This happens as soon as the deletion date exceeds 2010/01/01, which is usually the case with spool requests created after 2009/12/23.
The same wrong deletion date is shown after a spool request with a correct date was reprinted. This happens in all SAP releases independent of support package or kernel patch level.

These spool requests will not be deleted if the spool reorg job RSPO0041 or RSPO1041 is run with a variant that selects requests only according to their deletion data, not according to their minimum age.
Other symptoms of the underlying error are described in note 1423484.

More Terms
Deletion date, SP01, 2100/01/01, expiry date, spool full, spool overflow, SPOOL_INTERNAL_ERROR, ZREPAIR_SPOOL_DATE

Cause and Prerequisites
Programming error in kernel

Solution

For releases 3.1, 4.0B and 4.5B:

1. Increase the upper value of the spool number range to 99,999 to make a spool overflow less likely. See note 48284 for more details. This is a general recommendation by SAP.

2. Apply the following kernel patch (disp + work):
Release 3.1I: (31I_EXT) 781
Release 4.0B: (40B_EXT) 1072
Release 4.5B: (45B_EXT) 1002

3. Create report RSPO2010 with transaction SE38 in package SPOO. Apply note 1422843 using transaction SNOTE. Run report RSPO2010 once without changing any parameters after restarting the system with the new kernel.The report will modify the delete date of all spool requests created between December 23rd 2009 and the current day. The new delete
date will be calculated from the creation date plus the default retention time (profile parameter rspo/req_lifetime).

For releases 4.6B, 4.6C, 4.6D:

1. Increase the upper value of the spool number range to 99,999 to make a spool overflow less likely. See note 48284 for more details. This is a general recommendation by SAP.

2. Use transaction SP01 to find all spool requests created between December 23rd 2009 and the current day that should not been deleted after 8 days. Archive these requests or change the deletion date to e.g. 31.12.2070.

3. Create report RSPO2010 with transaction SE38 in development class SPOO. Apply note 1422843 using transaction SNOTE. Run report RSPO2010 once without changing any parameters after restarting the system with the new kernel. The report will modify the delete date of all spool requests created between December 23rd 2009 and the current day. The new delete date will be calculated from the creation date plus the default retention time (profile parameter rspo/req_lifetime). Please note that RSPO2010 cannot distinguish between requests that have been created with the deletion date 2100/01/01 deliberately or accidentally (caused by the kernel error).

4. Apply the correct kernel patch for your SAP release from the download area of this note.

5. If you cannot apply the new kernel shortly, run RSPO2010 and RSPO0041/RSPO1041 as a daily job. In that case, you will also have to perform step 3 daily.

For Basis Release 6.20 and higher:

1. Increase the upper value of the spool number range to 999,999 to make a spool overflow less likely. See note 48284 for more details. This is a general recommendation by SAP.

2. Use transaction SP01 to find all spool requests created between December 23rd 2009 and the current day that should not been deleted after 8 days. Archive these requests or change the deletion date to e.g. 31.12.2070.

3. Apply note 1422843 via SNOTE to obtain report RSPO2010. In release 620 and 640, it might be necessary to create the report first via transaction SE38 in package SPOO depending on the SNOTE version. Run this report once without changing any parameters after restarting the system with the new kernel. The report will correct the delete date of all spool requests created between December 23rd 2009 and the current day. The new delete date will be calculated from the creation date plus the default retention time (profile parameter rspo/req_lifetime).
Please note that RSPO2010 cannot distinguish between requests that have been created with deletion date 2100/01/01 deliberately oraccidentally (caused by the kernel error).

4. Apply the correct kernel patch (disp + work) for your SAP release from the download area of note 1425811.

5. If you cannot apply the new kernel shortly, run RSPO2010 and RSPO0041/RSPO1041 as a daily job. In that case, you will also have to perform step 3 daily.
Customers who have intentionally been creating spool request with a retention time of '9' can use RSPO2010 to identify spool requests with indefinite delete day created BEFORE December 23rd 2009. These requests can then be excluded from the automatic change by using the selection options of the report. You can find a more detailed documentation of this report attached to this note.

In case of any doubts or further questions please contact SAP support!
------------------------------------------------------------------------
|Manual Post-Implement. |
------------------------------------------------------------------------
|VALID FOR |
|Software Component SAP_BASIS SAP Basis compo...|
| Release 46C Until SAPKB46C59 |
| Release 46D All Support Package Levels |
| Release 620 Until SAPKB62067 |
| Release 640 Until SAPKB64025 |
| Release 700 Until SAPKB70021 |
| Release 710 Until SAPKB71009 |
| Release 701 Until SAPKB70106 |


Use SE38 to add the following text elements for report RSPO2010:
Text symbols:
100 Make sure to read note 1422843 before executing the report
Selection texts:
Name: CHECKJOB - Text: 'Check delete date in jobs'
Name: CRETIME1 - (Mark field 'dictionary')
Name: NEW - Text: 'Requests after 2009-12-23'
Name: OLD - Text: 'Requests before 2009-12-23'
Name: PRINTER - (Mark field 'dictionary')
Name: SHOW - Text: 'Show only'
Name: SUFFIX0 - (Mark field 'dictionary')
Name: SUFFIX1 - (Mark field 'dictionary')
Name: SUFFIX2 - (Mark field 'dictionary')
Name: TITLE - (Mark field 'dictionary')
Name: UNAME - (Mark field 'dictionary')


Software Component Release From Release To Release
SAP_APPL 30 31H 31I
SAP_APPL 40 40B 40B
SAP_APPL 45 45B 45B
SAP_APPL 46 46B 46B
SAP_APPL 46C 46C 46C
SAP_BASIS 46 46A 46D
SAP_BASIS 60 610 640
SAP_BASIS 70 700 702
SAP_BASIS 71 710 720

Support Packages
Support Packages Release Package Name
SAP_BASIS 46C SAPKB46C60
SAP_BASIS 620 SAPKB62068
SAP_BASIS 640 SAPKB64026
SAP_BASIS 700 SAPKB70022
SAP_BASIS 701 SAPKB70107
SAP_BASIS 702 SAPKB70204
SAP_BASIS 710 SAPKB71010
SAP_BASIS 711 SAPKB71105
SAP_BASIS 720 SAPKB72003

Related Notes
Number Short Text
1427188 Converter problems after applying new kernel (note 1422843)
1425811 Dialog work process crashes for spool display
1423484 Wrong date on cover page for spool requests
1299738 Various problems with spool requests in Unicode systems
48284 System can no longer create spool requests

Attachments
File Type File Name Language Size
ZIP Spool_reorg_variants.zip E 91 KB
ZIP How_to_use_RSPO2010.zip E 234 KB 



SP Patch Level
Software Component Version Support Package SP Patch Level
SAP KERNEL 6.40 32-BIT UNICODE SP315 000315
SAP KERNEL 6.40 64-BIT UNICODE SP315 000315
SAP KERNEL 7.00 32-BIT SP238 000238
SAP KERNEL 7.10 32-BIT SP183 000183
SAP KERNEL 7.00 32-BIT UNICODE SP238 000238
SAP KERNEL 7.00 64-BIT SP238 000238
SAP KERNEL 7.00 64-BIT UNICODE SP238 000238
SAP KERNEL 7.10 64-BIT UNICODE SP183 000183
SAP KERNEL 7.10 64-BIT SP183 000183
SAP KERNEL 7.10 32-BIT UNICODE SP183 000183
SAP KERNEL 6.40 32-BIT SP315 000315
SAP KERNEL 6.40 64-BIT SP315 000315
SAP KERNEL 4.6D_EXT 32-BIT SP500 002500
SAP KERNEL 4.6D_EXT 64-BIT SP500 002500
SAP KERNEL 4.6D_EX2 32-BIT SP500 002500
SAP KERNEL 6.40_EX2 32-BIT SP315 000315
SAP KERNEL 6.40_EX2 32-BIT UC SP315 000315
SAP KERNEL 4.6D_EX2 64-BIT SP500 002500
SAP KERNEL 6.40_EX2 64-BIT SP315 000315
SAP KERNEL 6.40_EX2 64-BIT UC SP315 000315
SAP KERNEL 7.01 32-BIT SP075 000075
SAP KERNEL 7.01 32-BIT UNICODE SP075 000075
SAP KERNEL 7.01 64-BIT SP075 000075
SAP KERNEL 7.01 64-BIT UNICODE SP075 000075
SAP KERNEL 7.11 32-BIT SP069 000069
SAP KERNEL 7.11 32-BIT UNICODE SP069 000069
SAP KERNEL 7.11 64-BIT SP069 000069
SAP KERNEL 7.11 64-BIT UNICODE SP069 000069


Download complete note from http://service.sap.com/notes

No comments:

Post a Comment