The authorizations are built via the SAP authorization concept. In addition to authorizations for transactions and reports, QPPD is coming with its own authorization objects.
Transactions
Transactions are mapped with the naming convention /SCT/QP*. The most important transactions are:
Transaction | Text |
|---|---|
/SCT/QPPD | QPPD Cockpit |
/SCT/QPPD_ARC | QPPD Archive Cockpit |
/SCT/QP_CUST | QPPD Customizing |
/SCT/QP_CUSTRPT | QPPD Customizing Analysis |
/SCT/QP_COPY | Copy of specifications |
Specification
There are two authorization objects for creating, changing, deleting, and displaying specifications. In the application, it must be decided which authorization object is to be used. The authorization roles must then use the respective authorization object. The authorization class is /SCT.
Authorization object /SCT/QPPD (standard)
Fields | Text |
|---|---|
/SCT/VART | specification type |
/SCT/VTYP | specification item |
/SCT/AG | authority group |
ACTVT | activity (create, change, delete, display) |
Authorization object /SCT/QPPD2 with factory (alternative from release 2203)
Fields | Text |
|---|---|
/SCT/VART | specification type |
/SCT/VTYP | specification item |
/SCT/AG | authority group |
WERKS | plant |
ACTVT | activity (create, change, delete, display) |
The authorization object /SCT/QPPD2 offers individual possibilities to assign the authorization especially if several plants are active. If there are no authorization profiles yet, it is recommended to create the profiles with this object.
Object type maintenance of variants
Data is displayed in tabular form on the tabs. The display for filtering, sorting, and column orders can be configured via table variants. The default settings for all users can also be customized. To maintain these variants, the authorization object in the authorization profile is required.
Authorization object /SCT/QP_VA QPPD Object type maintenance of standard variants
Fields | Text |
|---|---|
ACTVT | Activity 01 : Create |
Authorization groups for reports
Correction reports are delivered for mass correction of data and Customizing settings. These reports are provided with the authorization group /SCT/ADM. In the respective authorization profiles, corresponding authorizations can be assigned here.
Customer enhancements
If there are individual requirements regarding the authorization check, the authorization check can be adapted via ABAP programming. The authorization checks are implemented via the classes /SCT/QP_CL_AUTHORITY and /SCT/QP_CL_AUTHORITY2.
By calling the methods /sct/qp_if_authority~activate_check and /sct/qp_if_authority~deactivate_check the check can be activated or deactivated. It is also possible to redefine the relevant classes with individual logic by specifying them in Customizing->Basic Settings→ClassFactory.
SAP Standard Authority BDS Business Document Service
When using the Business Document Service, the authorization object S_BDS_DS is also required.