Extracting Authorization Data (R/3 Systems Only) 
To subject the search results to an authorization check, the user data and authorization data must be extracted from the back-end system. However, user data and authorization data are not extracted using BI extractors. Instead, the extraction is triggered by a report.
You run the report on the back-end system, which then transfers the data to SAP NetWeaver Enterprise Search. The report is write-protected and does not change any data in the back-end system.
You have created at least one search object connector for this back-end system.
There is a functioning RFC destination from the back-end system to SAP NetWeaver Enterprise Search.
Perform the following steps:
Log on to the SAP system from SAP NetWeaver Enterprise Search and start transaction SE38. In the Program field, enter the name of the report: ESH_AU_UPLOAD_AUTH_RFC, choose Display. Copy the program code of the report.
Log on to the back-end system that contains the data to be searched and call transaction SE38 again. In the Program field, specify a name for the ABAP report to be copied, for example Z_ESH_AU_UPLOAD_AUTH and choose Create. Copy the code from step one to this new report. Save and activate the new report.
Run the new report on the back-end system and enter the system ID in the syst_id parameter and the client of the Enterprise Search system in the client parameter.
Note
The report searches for a functioning RFC destination for the SAP NetWeaver Enterprise Search system specified to extract user data and authorization data from the back-end system. If the report runs successfully, it displays the RFC destination used. If the report does not run successfully, it lists all RFC destinations with errors that it examined.
Note
The data is indexed after the extraction. Therefore it can take several minutes until the data is active and available.