What is SAP basis BDLS?
BDLS is a transaction code used for Convert Logical System Names in SAP. It comes under the package SALE. When we execute this transaction code, RBDLSMAP is the normal standard SAP program that is being executed in background.
How do I run BDLS in SAP?
Step 2.1: Start transaction code BDLS and enter the required old/new logical system names and unselect other options “Test Run” and “Existence Check on new names in tables”. Please enter tables to be converted choice as A* and execute the BDLS run in the background.
What will BDLS do for SAP system?
Transaction code BDLS is a Tool: Conversion of Logical System Names. This program is used to convert a logical system name, which has already been defined or used in this system, to a new name. The program determines all the relevant tables and converts the corresponding entries.
How do I check my BDLS status in SAP?
For BDLS logs, you can use transaction code SLG1. Fill the Object as CALE and Subobject as LOGSYSTEM*. Enter the time restriction as per needed and press execute.
Why do we run BDLS?
BDLS is used for LOGICAL System Name conversion after System Refresh activity. When we refresh our quality system (QAS) from Production system (PRD) then in Quality system production system entries come in database that need to changed with Quality system’s entry in order to Quality system work properly .
Is BDLS required after system copy?
As such if you are doing a system copy, you should run BDLS as part of the post-system copy steps. It does take a long time.
Is BDLS client dependent?
When I execute BDLS, there are two options there, one is conversion of client dependent and independent tables and the second is conversion of client dependent only.
Do we need to run BDLS after a local or remote client copy?
You do not need to run BDLS after client copies, but only after system copies.
Do we need to run BDLS after local client copy?
How do I run BDLS after client copy?
Local client copy steps :
- Log on to the target system.
- Create an entry for your new target client using scc4.
- Log on to this new target client with user SAP* and default password pass.
- Start the client copy using transaction sccl.
- Select the source client and the copy profile.
- Schedule the client copy in bacground.
Is BDLS client specific?
It depends on the type of system copy you want to do. The SAP note 886102 is useful here. If you want to copy a single BW client (scenario B4) or a single source system client (scenario C4) you have to convert the client-specific tables only.