Easy Authorization Management for SAP

C_APO_SSA - Authorizatn Obj.: Release Handlg for Sales Schedulg Agreemnt

rdisp/max_wprun_time - Maximum work process run time   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Definition

You use the authorizationobject C_APO_SSA to determine which activities a user can carry out in Release Management for the Sales Scheduling Agreements .
For example, you can control whether a user can create scheduling agreement releases, output confirmations or change master data.

To determine whether a user is allowed to carry out a certain activity the system carries out an authorization check.
The authorization check is successful if the user passes the test for eachauthorization field in theauthorization object.

Defined fields

The authorization object C_APO_SSA contains the following authorization fields:

• APO_LOCFR: Source Location
  You use this authorization field to define for whichsourcelocations (plant locations) the authorization is valid, in other words for which source locations the user is allowed to carry out a certain activity.

• APO_LOCTO: Destination Location
  You use this authorization field to define for whichdestinationlocations (customer location) the authorization is valid, in other words for which destination locations the user is allowed to carry out a certain activity.

• APO_PROD: Product
  You use this authorization field to define for whichproductsthe authorization is valid, in other words for which products the user is allowed to carry out a certain activity.

• APO_PL_PPS: Production Planner
  You use this authorization field to define for whichproduction plannerthe authorization is valid, in other words for which production planner the user is allowed to carry out a certain activity.

• APO_CDSOBJ: Check Object in Release Management for the Sales Scheduling Agreement
  You use this authorization field to define for whichcheck objects the authorization is valid, in other words, on what data a user can carry out a certain activity.

Possible check objects are:

• Master Data for Sales Scheduling Agreement Item [S_SAGR]

• Release for Sales Scheduling Agreement Item [S_DELSCHED]

• Release and Confirmation History for Sales Scheduling Agreement Item [S_HISTORY]

• Output Confirmation for Sales Scheduling Agreement Item(Post Processing Framework Action) [S_PPFCONF]

• Current Status for Sales Scheduling Agreement Item [S_STACUR]

• Fiscal Year for Sales Scheduling Agreement Item [S_FISCYEAR]

• ACTVT: Activity
  You use this authorization field to define for whichactivities the authorizationis valid, in other which activities a user can carry out in Release Management Schedules for Sales Scheduling Agreements.

The following activities are possible:

• Add to or generate [01]

• Change [02]

• Display [03]

• Delete [06]

• Execute [16]

Dependencies

You assign authorizations in user master data maintenance. You must enter exactly which sales scheduling agreement data or check objects the user is allowed to access and which type of access they are allowed.

For example, a user may display the scheduling agreement release for all sales scheduling agreement items, but only change the releases for certain sales scheduling agreement items.

The sales scheduling agreement data or check objects that the user can access is defined using a combinationof the values for the authorization fields APO_LOCFR, APO_LOCTO, APO_PROD, APO_PL_PPS and APO_CDSOB.
The authorization field Activity(ACTVT) controls the type of access to the sales scheduling agreement data or check objects which the user is permitted to access.

In Release Management for Sales Scheduling Agreements a checkis carried out for each authorization check against a combination of the authorization fields Check Object (APO_CDSOBJ) and Activity (ACTVT).
When you are creating authorizations, you should note that not every possible combination is logical.

For example it is not logical to give a user the authorization to change [ACTVT = 02] the release andconfirmation history [APO_CDSOBJ = S_HISTORY], because the release and confirmation history of a sales scheduling agreement item can only be displayed or deleted.

The following table contains the combinations of check objects (APO_CDSOBJ) and activities (ACTVT) that are logical:

Generate	Change	Display	Delete	Execute
Master Data		Change	Display	Delete
Current Status		Change
Fiscal Year Change		Change
Releases	Generate	Change	Display
Confirmations			Execute
Release and Confirmation History		Display	Delete

List of Logical Combinations:

• Master Data for the Sales Scheduling Agreement Item [S_SAGR] - Change [02]
  The user can change the sales scheduling agreement item master data.

• Master Data for Sales Scheduling Agreement Item [S_SAGR] - Display [03]
  The user can display the sales scheduling agreement item master data.

• Master Data for Sales Scheduling Agreement Item [S_SAGR] - Delete [06]
  The user can delete the sales scheduling agreement item master data.

• Release for Sales Scheduling Agreement Item [S_DELSCHED] - Add or Generate [01]
  The user can create manual releases (delivery schedules) for sales scheduling agreement items.

• Release for Sales Scheduling Agreement Item [S_DELSCHED] - Change [02]
  The user can change manual releases (delivery schedules) for sales scheduling agreement items.

• Release for Sales Scheduling Agreement Item [S_DELSCHED] - Display [03]
  The user can display manual releases (delivery schedules) for the sales scheduling agreement item.

• Release and Confirmation History for the Sales Scheduling Agreement Item [S_HISTORY] - Display [03]
  The user can display the release and confirmation history for the sales scheduling agreement item.

• Release and Confirmation History for the Sales Scheduling Agreement [S_HISTORY] - Delete [06]
  The user can delete the release and confirmation history for the sales scheduling agreement item.

• Confirmation for Sales Scheduling Agreement Item (Post Processing Framework Action) [S_PPFCONF] - Execute [16]
  The user can select and process confirmations for the sales scheduling agreement item (Post Processing Framework Actions).

• Current Status of the Sales Scheduling Agreement Item [S_STACUR] - Change [02]
  The user can manually change the current status of the sales scheduling agreement item.

• Fiscal Year of Sales Scheduling Agreement Item [S_FISCYEAR] - Change [02]
  The user can change the fiscal year of the sales scheduling agreement item.
  
  

Further information

For further information on the SAP authorization concept, see the SAP documentation in the SAP Libraryunder mySAP Technology Components -> SAP Web Application Server -> Security (BC-SEC) -> Users and Roles (BC-SEC-USR).

Easy Authorization Management for SAP

ABAP Short Reference   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.


Length: 10662 Date: 20120526 Time: 190044     triton ( 259 ms )