Production Support Issues in BW

Production Support Errors :
1) Invalid characters while loading: When you are loading data then you may get some special characters like @#$%...e.t.c.then BW will throw an error like Invalid characters then you need to go through this RSKC transaction and enter all the Invalid chars and execute. It will store this data in RSALLOWEDCHAR table. Then reload the data. You won't get any error because now these are eligible chars done by RSKC
2) IDOC Or TRFC Error:
We can see the following error at “Status” Screen:
Sending packages from OLTP to BW lead to errors
Diagnosis
No IDocs could be sent to the SAP BW using RFC.
System response
There are IDocs in the source system ALE outbox that did not arrive in the ALE inbox of the SAP BW.
Further analysis:
Check the TRFC log.
You can get to this log using the wizard or the menu path "Environment -> Transact. RFC -> In source system".
Removing errors:
If the TRFC is incorrect, check whether the source system is completely connected to the SAP BW. Check especially the authorizations of the background user in the source system.
Action to be taken:
If Source System connection is OK Reload the Data.
3)PROCESSING IS OVERDUE FOR PROCESSED IDOCs
Diagnosis
IDocs were found in the ALE inbox for Source System that is not updated.
Processing is overdue.
Error correction:
Attempt to process the IDocs manually. You can process the IDocs
manually using the Wizard or by selecting the IDocs with incorrect
status and processing them manually.
Analysis:
After looking at all the above error messages we find that the IDocs are found in the ALE inbox for Source System that are not Updated.
Action to be taken:
We can process the IDocs manually via RSMO -> Header Tab -> Click on Process manually
4) LOCK NOT SET FOR LOADING MASTER DATA ( TEXT / ATTRIBUE / HIERARCHY )
Diagnosis
User ALEREMOTE is preventing you from loading texts to characteristic
0COSTCENTER . The lock was set by a master data loading process with the
request number.
System response
For reasons of consistency, the system cannot allow the update to continue, and it has terminated the process.
Procedure
Wait until the process that is causing the lock is complete. You can call transaction SM12 to display a list of the locks.
If a process terminates, the locks that have been set by this process are reset automatically.
Analysis:
After looking at all the above error messages we find that the user is “Locked”.
Action to be taken:
Wait for sometime & try reloading the Master Data manually from Info-package at RSA1.
5) Flat File Loading Error
Detail Error Message
Diagnosis
Data records were marked as incorrect in the PSA.
System response
The data package was not updated.
Procedure
Correct the incorrect data records in the data package (for example by manually editing them in PSA maintenance). You can find the error message for each record in the PSA by double-clicking on the record status.
Analysis:
After looking at all the above error messages we find that the PSA contains incorrect record.
Action to be taken:
To resolve this issue there are two methods:-
i) We can rectify the data at the source system & then load the data.
ii) We can correct the incorrect record in the PSA & then upload the data into the data target from here.

6) Object requested is currently locked by user ALEREMOTE
Detail Error Message.
Diagnosis
An error occurred in BI while processing the data. The error is documented in an error message.Object requested is currently locked by user ALEREMOTE
Procedure
Look in the lock table to establish which user or transaction is using the requested lock (Tools -> Administration -> Monitor -> Lock entries).
Analysis:
After looking at all the above error messages we find that the Object is “Locked. This must have happened since there might be some other back ground process running
Action to Be taken :
Delete the error request. Wait for some time and Repeat the chain.