Authorization Concept in SAP Retail
Store 
You use the following authorization objects to determine the stores in which a user can log on to SAP Retail Store and the IACs and reports the user is allowed to run.
· M_IS_WERKS (LIS standard analysis: info structure/site)
determines the store(s) in which a user can log on.
Name of the information structure: * (as desired)
Site: R310, R320
· S_TCODE(transaction code check when transaction is called up)
contains all transaction codes in the IACs that the user is allowed to start (including WSGM for the full menu). The system only provides links in the full menu for these IACs. Exception: The link to the mail function (BWSP) is always active.
The transaction codes are usually always the same as the service names. Exceptions: Full menu (service WOSM, transaction WSGM), Display site (service WOSW, transaction WSSW), label printing (service WSTL, transaction WTAD_SRS).
Transaction codes: BWSP, WSAU, WSGM, WSSW, WSTA, WSTE
· S_PROGRAM (ABAP: Program run checks)
Before a user can display a report, in the report attributes the Authorization Group field must have a value for which the user has a SUBMIT authorization (see the IMG).
You use report RSCSAUTH to maintain authorization groups for reports (RMCW*, RSTWBFAF, RSTWBFLI, and RWBEST01). For standard analyses (RMCW*), you have to set the authorization group to SWANALYS. On the full menu, the system only displays links for the reports for which the user has authorization for the authorization group.
Standard analyses are a special case: The user can go from the full menu to the reporting tree RSW1 containing the individual LIS reports. The system displays links for the reports for which the user has authorization for SWANALYS.
User action: ABAP program: Execute ABAP Program
Authorization group ABAP program: SWANALYS, SWPURCH
This list only includes authorization checks specifically required for the full menu and reporting. The individual IACs and reports may run other authorization checks specific to the applications.