KM Folders are utilized as the base platform in which KM Documents are stored.  For example through KM End-Users can access, obtain, manage and review data information through documents sourced from the business  intranets, external WWW feeds, and file servers. The KM Documentsthemselves are presented in the standard formats of PPT, excel, word documents and html.

Attempting to Delete entries within BEX Portfolio

While attempting to delete an Entry within a BEX Portfolio setup through a Portal enviornment on ocassion I have seen end-users come across the following error exception reference:

  • You do not have access permission for item “.~system~”

From a high level perspective such an occurrence can be confusing and identifying the root cause should be done through default trace analysis.

Capture a trace & Analyze (SAP KBA: 1596214)

From a KM perspective if you encounter such an error occurrence the first point of analysis should be to check if the KM Setup is working correctly (all services running).

In this instance we can see error’s pertaining to the current status of the Wastebasket Service:

#2.16:06:07:189#+0200#Error#com.sapportals.wcm.command.DeleteResourceToWastebasketCommand# #EP-KM- 8 b960000300ce9ca#0#Thread[HTTP Worker [@1517785032],5,Dedicated_Application_Thread]#Plain## Permission denied: uri=/documents/.~system~, permission=node_write_properties, user=USER.R3_DATASOURCE.ABCXYZ#

Wastebasket Service?

Within all standard KM setups the Wastebasket Service is pre-configured by default. In terms of underlying operations the Wastebasket service acts as a means of fail-safe deletion i.e. users can be moved (deleted) to the wastebasket and restored/recovered from this point of call if required.

Resolving Exceptions, Troubleshooting & Checking Permission Setups:

If you are attempting to delete the KM folder object with a user who has not created the KM resource, you should proceed to check if the original resource creator can perform the delete command.

The WIKI outlined below covers permission inheritance across the KM Landscape within the Enterprise Portal and is a key source of reference here (File System Repository – Step by Step Guide and common problems):

Also an additional point to highlight surrounding the Wastebasket Service is to check the current persistence mode e.g. rusext_wcm_conten RM i.e. (DB,FSDB,DBFS) or is it a File System RM?

The point behind this highlight is that using the wastebasket functionality in FSDB repositories is not supported by SAP.

It is true in theory that it ‘should’ work provided the repository supports the ‘move’ functionality and the user has the appropriate authorizations on the filesystem as well as within the portal. However, using it on such a repository is quite dangerous and can result in a loss of Metadata and in some cases complete corruption of data. See the following help documentation for further details of this –

Starting the Wastebasket Service

The recommended procedure is to ensure the Wastebasket Service is running by checking the Component Monitor. From this point you will need to remove any prior configuration that was causing the WasteBasket Service to fail. After making the required corrections a restart of the system should be performed so the service can start up accordingly.

Once the wastebasket service is running it should then be possible to delete the resource as desired.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply