sapnote_0000175596
3
31.01.2013 Page 1 of 3 SAP Note 175596 - Conversion to new batch input log Note Language: English Version: 8 Validity: Valid Since 29.06.2004 Summary Symptom When you process a batch input, you note log interface problems. For example: o Symptoms described in Note 18319 often occur in the batch input log file. o The performance is poor in particular when processing large batch input sessions or when processing many sessions in parallel. Other terms Semaphores 22 Reason and Prerequisites Architecture of batch input log procedure is based on the batch input log file. Solution Convert to the new batch input log procedure. As a result, all batch input logs, are stored in TemSe similar as the logs of background processing. To do this, proceed as follows: 1. Use the R/3 kernel with patch level 124 or higher in Release 4.6A. Or use the downward compatible standard 4.6B R/3 kernel. 2. Change parameter bdc/new_protocol. in the default profile Thus: bdc/new_protocol = on Caution: The parameter must be valid for all application servers. A mixed batch input log procedure is not possible. Note: You already find the parameter in Release 4.0 and 4.5 However, it must not be changed there. Remember that this parameter ONLY works with Release 4.6. As of Basis Release 6.10, there is only the new log interface. The parameter then no longer exists. 3. Copy possibly existing batch input logs from the 'old' log interface using program RSBDCLCH. As a result, the logs are converted in the entire system - that is in every client- to the new log interface. The old log file is deleted after successful conversion. To convert the logs from Release 3.0 or 3.1, see Note 303773. Note: o All service programs in the batch input environment, such as Transaction SM35, Transaction SM35P (log overview) or RSBDCREO now display or process the logs as usual. o The logs can also be displayed in the TemSe environemt. For example, via Transaction SP11.
-
Upload
kalyan-chakravarthi -
Category
Documents
-
view
16 -
download
0
description
sapnote_0000175596
Transcript of sapnote_0000175596
31.01.2013 Page 1 of 3
SAP Note 175596 - Conversion to new batch input log
Note Language: English Version: 8 Validity: Valid Since 29.06.2004
Summary
SymptomWhen you process a batch input, you note log interface problems. Forexample:
o Symptoms described in Note 18319 often occur in the batch input logfile.
o The performance is poor in particular when processing large batchinput sessions or when processing many sessions in parallel.
Other termsSemaphores 22
Reason and PrerequisitesArchitecture of batch input log procedure is based on the batch input logfile.
SolutionConvert to the new batch input log procedure. As a result, all batch inputlogs, are stored in TemSe similar as the logs of background processing.To do this, proceed as follows:
1. Use the R/3 kernel with patch level 124 or higher in Release 4.6A. Oruse the downward compatible standard 4.6B R/3 kernel.
2. Change parameter bdc/new_protocol. in the default profile Thus:bdc/new_protocol = on
Caution:The parameter must be valid for all application servers. A mixed batchinput log procedure is not possible.
Note:You already find the parameter in Release 4.0 and 4.5 However, it mustnot be changed there. Remember that this parameter ONLY works withRelease 4.6. As of Basis Release 6.10, there is only the new loginterface. The parameter then no longer exists.
3. Copy possibly existing batch input logs from the 'old' log interfaceusing program RSBDCLCH. As a result, the logs are converted in theentire system - that is in every client- to the new log interface. Theold log file is deleted after successful conversion.To convert the logs from Release 3.0 or 3.1, see Note 303773.
Note:
o All service programs in the batch input environment, such asTransaction SM35, Transaction SM35P (log overview) or RSBDCREO nowdisplay or process the logs as usual.
o The logs can also be displayed in the TemSe environemt. Forexample, via Transaction SP11.
31.01.2013 Page 2 of 3
SAP Note 175596 - Conversion to new batch input log
o Use program RSBDCREO for reorganizing. A reorganization with TemSeshould not be carried out in any case since this may causeinconsistencies between the TemSe environment and the batch inputor other TemSe users.
o With the programs RSBDCCKA and RSBDCCKT, a consistency check can becarried out. Inconsistent entries can also be deleted there. (As of4.6C also available in the batch input log overview SM35P via menuitem Goto|Consistency APQL and Goto|Consistency TemSe.)Technical background:The connection between a TemSe entry and batch input is carried outvia the database table APQL.
RSBDCCKA:The report checks whether the TemSe object is available for everyAPQL entry.
RSBDCCKT:The report checks whether an APQL entry is available for everybatch input TemSe object. In addition it checks the consistencybetween the file length and the length specification in TemSe.
If inconsistencies are found, the logs affected should be deletedin Transaction SM35P.
o The new batch input logs cannot be converted into the old logs.When converting with RSBDCLCH, the old logs are deleted.
o In Release 4.6A and 4.6B, no archiving program is available in theSAP standard for new batch input logs. This is only available withRelease 4.6C.
Note:As of Release 4.6C, only the new batch input log procedure is supported.When using the new TemSe log interface, profile parameters bdc/log file andbdc/altlogfile become obsolete.
Header Data
Release Status: Released for CustomerReleased on: 29.06.2004 11:01:29Master Language: GermanPriority: Recommendations/additional infoCategory: Upgrade informationPrimary Component: BC-ABA-SC UI services, screen, batch input
Valid Releases
Software Component Release FromRelease
ToRelease
andSubsequent
SAP_BASIS 46 46A 46D X
SAP_BASIS 60 610 640 X
31.01.2013 Page 3 of 3
SAP Note 175596 - Conversion to new batch input log
Software Component Release FromRelease
ToRelease
andSubsequent
SAP_BASIS 70 700 700 X
Support Packages
Support Packages Release Package Name
SAP_BASIS 46B SAPKB46B09
SAP_BASIS 46C SAPKB46C01
SAP_BASIS 46D SAPKB46D01
Related Notes
Number Short Text
788797 Batch input: Session multiple selection for reorganization
565713 Batch input log overview: abbreviated host name
356758 Batch input logs with unreadable characters
354649 Batch input logs and 4.6D R/3 kernel
318846 Installing the 4.6D kernel in 4.6A/B/C SAP systems
303773 Transfer of BDC logs from Release 3xx
18319 Difficulties with the batch input log file
Attributes
Attribute Value
Transaction codes SM35
Transaction codes SP11
