How to resolve “BPC 10.1 – Cannot perform Write ILLEGAL_INPUT”
While writing in BPC model, an error is thrown as shown in screenshot below “Cannot perform write (ILLEGAL_INPUT)”
Initial analysis was performed from BPC and BW administration to check all dimensions and models were active. We had then sent these table names to DB team to find the logs on these tables for last 10 days. From the logs, it was discovered that during the DB conversion, partitions from BPC tables were dropped but were never recreated due to errors during conversion.
Hence, table inconsistency was caused because of data conversions which happened at the database level and was not fixed. As the data conversion was not successfully completed, table partitions were not created and hence BPC model was unable to save any data as there were no partitions on BPC table in DB.
Hence, we ran below consistency checks in BW system and repaired partitions with the help of DB logs as per the steps explained below.
Note: If any DB level changes are done, then it is always useful to run this program to check for any DB inconsistency with various options given in this table.
Steps to fix this issue:
Step 1: Execute report RSDU_TABLE_CONSISTENCY
Go to SE38 in your BW system and run the program named “RSDU_TABLE_CONSISTENCY” and click on execute.
Enter parameters as below:
- Tables name: /B28/*<<F table of your BPC cube>>
- Check “store issue”
- Select “CL_ “Available Consistency Checks”: “CL_SCEN_PRIMARY_KEY” and “CL_SCEN_PARTITION_SPEC”
Execute this report in the background and then proceed to step 2 to view all the results.
Step 2: Show results from consistency checks:
Once these results are saved, proceed to show results by checking:
Operational modes option as – “Show issues in GUI”
Click on “Show” Issues from previous checks
This will show results of consistency checks:
Click on each item and click on “Save” to save the checks so that you can run a repair.
Step 3: Run Repair on erroneous partitions
Once you have saved all the consistency details, then go back to the initial screen and click on “Repair” as shown below:
It is recommended to run “Repair” in the background as it can take a long time depending upon the inconsistencies identified.