Reply from Hilik49 on Nov 24 at 5:47 AM Changing Logical System Name with BDLS
updated Jun 21, 2011 3:04 am | 4,587 views
*Introduction*
*As of NetWeaver 6.20, SAP provides the option to convert logical systems
using a new transaction that is more transparent and easier to use.
Transaction BDLS has been used for this purpose until now. This transaction
remains unchanged, and is enhanced by the new transaction BDLSS. In
contrast to BDLS, in BDLSS logical systems can also be converted remotely
in all partner systems.*
More information about the transaction can be found at the following
website:
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/3 3/c823dbaea911d6b29500508b6b8a93/frameset.htm
*[Source: SAP Library]*
The conversion process could save you up to hours of waiting for the
conversion to end. Usually, when converting logical system name, this will
take hours for larger SAP systems. The process takes a huge amount of e.g.
a system copy routine, which shouldn't be the case. For that, this document
provides a good and safe way to speed up the conversion process using
simple steps.
Obviously, we did some tests with large tables before publishing this
tutorial online. The results were overwhelming: normally, a test run on
table GLPCA (in a WAS 620/ 4.7 system) took us 4,5 hours to complete. With
an index on the key fields (RCLNT, AWSYS and LOGSYS), the process was
shortened to an amazing time of only 6,5 minutes.
Also, tests have shown that large tables that contain the LOGSYS (or
similar) field but no records also take a long time to process. Therefore,
these tables also need to have an index.
Examples of tables that might need special attention could be: ARIX_BKPF,
BKPF, EDIDC, LIPS, MKPF, MLHD, RBKP, SMPARAM, , SMSELKRIT, SWW_CONTOB,
GLPCA, VBAK, VBAP, VBFA, COEP, COBK, STXH, VBRK, VBRP, LIKP and ZARIXFI1.
Tables that contain a LOGSYS (or similar) field(s), can be looked up using
a former BDLSS log.
Before creating the actual indexes, note them down on paper on use them in
a custom SQL script. You will need to drop them afterwards.
*Creating the indexes*
| | | ---------------Original Message---------------
From: Antonio Bonillo
Sent: Friday, November 22, 2013 9:16 AM
Subject: BDLS Performance
Hi experts,
BDLS needs currently 3 weeks for 7.5 TB in our ERP
do you have any recommendation to speed this up?
thanks ,
Tony |
| Reply to this email to post your response. __.____._ | In the Spotlight Become a blogger at Toolbox.com and share your expertise with the community. Start today.   _.____.__ |
