BDLS Monitoring Tools in SAP

Monitor the BDLS statastic with table BDLSPOS
Monitor using TCodes BDLSS 
Monitor TCode SLG1 Object CALE 




Tags: How to monitor BDLS process

0 comments

How to enhance SAP BDLS runtime performance

Prerequisites before running BDLS on SAP System

1. Switch off the Archive log mode of database. During BDLS lots of archive logs get generated, to switching to noarchive mode always make it faster.

2. Create index on some large table where I think it could take much time.




tags: sap running bdls faster, How to enhance SAP BDLS runtime performance,

0 comments

When to run BDLS in SAP System Copy ?

When you perform a system copy from Production (PRD) to a Non production System(QAS)
we run a BDLS to convert the SID from PRD to QAS for example.

BDLS usually takes long time
Ex., 1.2 TB database, it lasts about 12 hours


Check related posts on BDLS Performance tuning steps


Note: When not to run BDLS in SAP System Copy ?
If you don't change the SID and you use the same client, you should not need to run BDLS.




tags:BDLS runtime performance, When to run BDLS in SAP System Copy , what is SAP BDLS, SAP logical system conversion, t-code BDLS,

0 comments

What is SAP Logical System means?

Logical system enables the system to recognize the target system as an RFC destination. Logical system is required for communication between systems within the landscape. You need a logical system when you create a new client in SAP

T-Code to create Logical System in SAP is BD54
Logical System is transportable.



Tags: SAP logical system, BD54, BDLS,What is SAP Logical System means,

0 comments

15 Steps to do a SAP System Copy

1. Create Java Export files from the source system:
2. Stop the target SAP system with the SAP Management Console
3. Make a copy of all the files in the \QAS\SYS\profile\ directory
4. Create a new backup of the source SAP system database
5. Restore the target SAP system database from the backup created in step 4.
6. Run the SAP-provided system copy tool
7. Stop the target SAP system using the SAP Management Console
8. Restore the files copied in step 3
9. Start the target SAP system
10. Cancel any production batch jobs:
11. Delete Source System profiles and Import the correct SAP profiles
12. Delete Source System Licenses and install the new Licenses
13. Reinitialize in the transport domain
14. Change the Logical System
15. Lock/Unlock users as necessary, using Transaction SU01
a) Stop and restart the SAP system
b). Run SGEN to recompile programs and reports
c). Run BDLS to change logical system







Tags: 15 Steps to do a SAP System Copy, BDLS, License, Profiles, STMS, Logon groups, RFC, SAP system copy steps

0 comments

SAP Basis Questions for Interview

Explain why  BDLS used during System refresh ?

SAP system is Slow How do you troubleshoot?

What does memory entered PRIV mode mean ?   Click for Answer

Difference between Configtool & NWA?

What tools did you use to upgrade NW Portal?

How do you perform a Java System Copy?

Explain SAP SSO steps?

Can you tell BW System Copy Post processing Steps?

Basis Interview Questions on Transports?  click for Answer
Do you like to share your Basis Interview Questions with our Readers? Please comment!





Tags: sap basis interview questions pdf,  BASIS Interview Questions, ANSWERS, ibm interview questions sap basis, FAQ, sap basis interview questions 2010, 2014, sap bw basis interview questions, sap basis interview questions capgemini, deloitte sap basis interview questions, sap basis interview questions with answers, sap basis interview questions with answers pdf, accenture sap basis interview questions, walmart sap bsis interview questions, basis, basis materials, interview, interview questions, netweaver, sap, sap ag, sap basis, sap interview, sap interview questions, sap netweaver

0 comments

Note 932032 - BDLS: Special conversion for large tables

Symptom
You are in transaction BDLS and you want to execute the conversion of logical system names in a test run or a productive run. When you do this, very long runtimes occur for certain tables.
Other terms
BDLS, COEP
Reason and Prerequisites
In a test run, transaction BDLS checks whether the new logical system name already exists in the table. In addition to this, the number of entries to be converted is determined for statistical purposes. Since the checked fields are normally not included in an index, these checks are usually performed as a "full table scan", which results in very long runtimes for large tables that contain a very large number of entries. In principle, you can exclude tables from the conversion that use the checked domains, but in which the relevant fields are not filled.
Solution
The solution describes how the exception table BDLSEXZ can be used to perform an own conversion routine for these tables. You can use transaction SM30 to maintain the table. The table COEP (which as a special case contains two fields to be converted) serves as an example here. For tables in which the relevant fields (typed with the domains 'LOGSYS' or 'EDI_PARNUM') are not filled, it is sufficient to exclude them from the conversion.
The solution consists of several steps.

Excluding the table from the standard conversion

To exclude a table, make the following entries in the table 'BDLSEXZ':

Class      (OBJCLS): T (Excluded Table)
Object name (OBJKEY): COEP

Activating a special conversion

To activate a special conversion, make the following table entry:

Class      (OBJCLS): X (Objects for Specific Treatment)
Object name (OBJKEY): COEP_XXX   (any)
Program    (PROGRAM): Z_BDLS_COEP  (own program)
Routine    (SUBROUTINE): TABLE_CHANGE (subroutine (FORM))

In this case, you can choose an object name of your choice. The 'Routine' parameter describes a subroutine (FORM) in the program, which is called with certain parameters using transaction BDLS.

Program attributes.

Define the subroutine (FORM) as follows:

FORM table_change  TABLES i_protocols
              USING  s_extparam TYPE bdi_lsext.

The following data declarations are required for this in the program:

DATA: i_protocols TYPE TABLE OF edimessage WITH HEADER LINE,
      s_extparam TYPE bdi_lsext,
      wa_prot LIKE edimessage.

Due to entries in the table i_protocols , log information can be transferred to the calling program:

wa_prot-msgid = 'B1'.
wa_prot-msgty = 'I'.
wa_prot-msgno = '999'.
wa_prot-msgv1 = 'Test run table COEP'.
wa_prot-msgv2 = 'with/without Existence check'.
wa_prot-msgv3 = 'is unsupported'.
wa_prot-msgv4 = '!'.
INSERT wa_prot INTO TABLE i_protocols.

The routine is also called in the test run; therefore, the actual conversion must be encapsulated by a query of the s_extparam-test indicator.


The programs of the objects to be handled separately are generally executed. Therefore, you must check in the program whether the current table is to be converted. To do this, see the program lines after the comment
* check whether used table is part of selection
in the sample source code.

The correction instructions contain the source code for the conversion of the table COEP using the "OPEN CURSOR" technique.
Use the Note Assistant to implement the corrections after you have created the (empty) report Z_BDLS_COEP.

tags: Note 932032 - BDLS: Special conversion for large tables

0 comments