BEx Transport request xxxxxxx is not available

While editing or saving a query on Query Designer, you experience the error below


Open a query with Query Designer
Edit the query 
Save the query

Error: BEx Transport request 'xxxxxxx' is not available or not suitable
Error: Request/task xxxxxxx does not exist



Solution:

Access follow the process below:

Access transaction RSA1
Click on Transport Connection
Click on BEx button (Shift + Ctrl + 0)
Click on Assing/Delete
Select a new transport request (you can create a new one).

 After this process, the issue will be solved.

RSA1: Environment not visible after transport - BPC NW

After transport, the ENVIRONMENT transported is not visible on the backend of the traget system

Run transport of the ENVIRONMENT from the source system to the target system.
Run the t-code RSA1.

ENVIRONMENT is not visible.


Solution:

Activate the ENVIRONMENT in target system:

• Connect to BW system with a user account having SAP_ALL profile.
• Run T_code SE38.
• Run UJS_ACTIVATE_CONTENT program.
• As Environment ID, enter the ID of the ENVIRONMENT transported
• Check only "Activate environment".

If employee leaves and user deleted Change Broadcast Setting Owner

When an employee leaves the company, its broadcast settings remains on BW system.

Since his user will be deleted, some of his broadcast settings are still relevant for other users.


Solutions:

Recreate the Broadcast Settings with a valid user. 

Transaction RSRD_ADMIN

Select the broadcast setting technical name ,
Execute
Click on Edit button

RSA1:Entry in inbound table already exists

While execute transaction RSA1

Message Error follows
Entry in inbound table already exists
Message no. E0412

Inbound parameters already exist in the partner profile under the
following key:

/DBW100/LS//RSSEND////

This relates to the key fields in table EDP21:

SNDPRN  Partner number
SNDPRT  Partner type
SNDPFC  Partner function
MESTYP  Message type
MESCOD  Message code
MESFCT  Message function
TEST    Test indicator

Solution:

This issue uses to be really related to the self system. The system is created the first time you call the AWB (RSA1). Because of this, the system tries to create entries in certain tables (e.g. table
EDP21) but if there were already entries concerning the partner profile, this results in errors such as E0412.

Delete the entries for RSSEND and RSINFO in table EDP21 and the entries for RSRQST in table EDP13 related to RWD300. You have to delete just the entries with the same name as the BW system
itself.

When the entries are cleared, only calling the AWB again via RSA1 should create all entries for the self system correctly and in the right order.

Runtime error "IF_RSBK_REQUEST~GET_TGTTP" occurs when start DTP(Data Transfer Process) running in T-code RSA1.

• Go to T-code RSA1.
• Click the InfoProvider catalog in the left "Modeling" panel.
• Click "Find" tool button, input the DTP technical name.
• Double click the DTP, go to "Execute" tab.
• Click "Execute" button.
• Click "Yes" in the pop up "The request generated by the DTP will now be processed. Do you want to display the request monitor?".
• Click the button besides the error information displayed in the screen "Monitor: Data Transfer Process XXXX".
• Short Dump "IF_RSBK_REQUEST~GET_TGTTP" occurs.

Solution:

It a cause of program error,


Apply the SAP Note 1627025 to prevent such issue happening again in the future. We will have to delete the error request XXXX to make sure the next loading run successfully.

• Go to T-code SE16, input the RSBKREQUEST as table name.
• Press <Enter> key.
• Input XXXX as REQUID.
• Click "Execute" (F8) button.
• You will find both fields TSTMP_H and DTP are empty.
• Click "Back" (F3) button.
• Delete the REQUID value, and input the DTP technical name as DTP field value.
• Click "Execute" (F8) button.
• Record the field TSTMP_H value which is not empty, it should have the same value as the other field which has value.
• Click "Back" (F3) button.
• Delete the DTP technical name as DTP field value.
• Input XXXX as REQUID.
• Click "Execute" (F8) button.
• Set the DTP technical name as DTP field value, set the recorded TSTMP_H value in step 11 as field TSTMP_H value.
• Go to T-code RSRQ.
• Input request XXXX as "GUID or SID of Request" value.
• Click "Execute" (F8) button.
• Set the request status to be Red.
• Click "Delete" button to delete the request XXXX.
• Start the DTP and monitor the loading request status.

** Note: in case you couldn't change the value in T-code SE16 directly, there is alternative method to update the value:

Debug mode in T-code SE16.
Run the SQL statement in database.

RSA1 hangs for specific user

While Starting RSA1 hangs on methode GET_ROOT of class CL_RSAWBN_TREE_MODEL and terminates with below dumps for specific user and user can start RSA1 without any error.

"TIME_OUT"
"CL_RSAWBN_TREE_MODEL==========CP"
"CL_RSAWBN_TREE_MODEL==========CM00D"
"GET_ROOT"

This problem belongs to a specific user only and caused by an inconsistency in table SPERS_OBJ.

Solution

• Go to transaction SU01 and enter the userid of the user that can not execute the favorites anymore.
• Enter the maintenance in change mode.
• Then go to the TAB Personalization and double click on RS_BI_DWB_FAVORITES 'Favorites in the BI Data Warehousing Workbench'
• Then you see a table with all favorites. Verify the entries in the table. NodeID and NextID must be different for each entries.
• If you find such entry where NodeID and NextID are the same, you have to delete it from the table.

Afterwards the user can use RSA1 again without any issues.

Runtime "ASSERTION_FAILED" Error when opening RSA1/RSPC

Due to an infinite loop a TIME_OUT dump in CL_RSAWBN_TREE_VIEW or in CL_RSAWBN_TREE_MODEL_FOLDER in method ADD_T_TREE is triggered
Runtime Error ASSERTION_FAILED in ABAP Program CL_RSAWBN_TREE_VIEW is generated
Implement Notes 1585456 and 1618577 and call the transaction again.

Only if point 1 does not help

Remove the entries from table RSCOMPTLOGOT where
APPLNM = 'HYBR' or
APPLNM = 'NODESNOTCONNECTED'

Test again RSA1 or RSPC, if dump persists delete the contents of table RSCOMPTLOGO
Another option is to transport object RSDC with key RSPC from dev/test to move the tree structure into the system.

Obs.: The entries from tables RSCOMPTLOGO/RSCOMPTLOGOT are representing the folder structure of process chains (RSA1/RSPC).  This has no functional influence and the chains, loads etc will still work properly.

If this linked list becomes inconsistent, the only solution is to drop the content of the mentioned tables.

After the entries are deleted, the next call of RSPC will rebuild the list. As the hierarchy structure itself is lost, the newly created folder list will be a flat structure. To return to the desired hierarchical structure, the folders are to be manually positioned to the desired place.

RSA1: Logical system name has been changed for this system

When you execute transaction code RSA1 and below dialog box will prompt.

RSA1 - Logical system name has been changed for this system

If you click on the help icon, the following explanations will appear,

Logical system name has been changed for this system

Message no. R3206

Diagnosis
The logical system name of this system is NEW-LOGICAL-SYSTEM. However, this system was originally created with the logical system name OLD-LOGICAL-SYSTEM. It is not permitted to change the logical system name, as connections to other systems will be damaged beyond repair.
System Response
The transaction is canceled.
Procedure
Change the name of the logical system (table T000) for client back to OLD-LOGICAL-SYSTEM . This enables you to continue working with the system.
Note: If you really want to change the logical name, read the information in SAP Note 886102.

Solution
You must run the logical system name conversion using the transaction BDLS or RBDLS2LS. The transaction will convert the old logical system name to a new logical system name. 

BRTOOLS & ERRORS

1. Tablespace over flow (ORA-1653, 1654
2. BR0301E SQL error -1031 at location BrInitOraCreate-2
3. BRBACKUP/BRARCHIVE failed with warning ORA-28011: the account will expire soon
4. ORA-01031 with error "SAP_MLICHECK WHERE EXPIRATION_DATE
5. ORA-01031:'SELECT TABART FROM "SAPR3".DDART ORDER BY TABART

6. Max Extents reached  (ORA-1631, 1632)
7. Archive Stuck (ORA-255, ORA-272)
8. Datablock corruption (ORA-1578)... restore from old backup
9. Missing end backup while performing a backup
10. stats out dated - run brconnect -f stats
11. Oracle listener, Tnsnames port issues
12. Oracle DLL Compatibility issues (Patch Oracle)
13. International hardware errors ORA-600 (Refer to SAP and Oracle)
14. OPS$ issues related to authentication while logging
15. Connection issues between R/3 WP: Oracle Shadow with error ORA-12560
16. Oracle is corrupted or Disk corrupted, External disk not available, datafile missing, Space issues.
17. Missing Indexes in DB02
18. Database backup not successful due to space issues, tape issues
19. Control file missing - Recreate control file
20. Oracle shared memory not available issue with SGA
21. If buffer hit ration below 94% (Increase block buffer size)

Messages and Return Codes for BR*Tools:


BR*Tools issues messages in the following form:

BR<NNNN><X> Message text

NNNN: sequential number of the message

X: type of message:

I: information
W: warning
E: error message
The text of the message contains the following variables:

%s: string
%d: integer
%f: real number in floating-point format

Return Codes:

The following return codes are possible:

Code

Meaning

0: Successful

1: Successful with warnings - all files were processed (for example, backed up or restored)

2: Canceled during the initialization phase by a user or other signal

3: Errors occurred during the initialization phase, processing was not started

4: Canceled by a user or other signal during processing

5: Failed because errors occurred during processing

6: Internal termination

9: Successful but not finished yet (can be seen in summary logs copied to backup media)