Easy Authorization Management for SAP

C_APO_EXPR - APO Authorization Object: External Procurement Relationships

RFUMSV00 - Advance Return for Tax on Sales/Purchases   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Definition

You use the authorizationobject C_APO_EXPR to define which activities a user is allowed to carry out for an external procurement relationship.

To determine whether a user is allowed to carry out a certain activity (for example, creating a releaseagainst an APO scheduling agreement), the system carries out an authorization check. To pass the authorization check the user must pass a check for eachauthorization field in theauthorization object

Defined fields

The authorization object C_APO_EXPR contains the following authorization fields:

• APO_LOCFR: Source Location
  You use this authorization field to define for whichsourcelocations the authorization is valid, that is for which source locations a user is allowed to carry out a certain activity for an external procurement relationship.

• APO_LOCTO: Destination Location
  You use this authorization field to define for whichdestinationlocations the authorization is valid, that is for which destination locations a user is allowed to carry out a certain activity for an external procurement relationship.

• APO_PROD: Product
  You use this authorization field to define for whichproductsthe authorization is valid, that is for which products a user is allowed to carry out a certain activity for an external procurement relationship.

• APO_PL_PPS: Production Planner
  You use this authorization field to define for whichproduction plannerthe authorization is valid, that is for which production planners a user is allowed to carry out a certain activity for an external procurement relationship.

• APO_PLANER: SNP Planner
  You use this authorization field to define for whichSNP plannerthe authorization is valid, that is for which SNP planner a user is allowed to carry out a certain activity for an external procurement relationship.

• APO_EXPOBJ: Check Object for External Procurement Relationships
  You use this authorization field to define for whichcheck objects the authorization is valid.
  Allowed Input Values:

• External procurement relationships (master data) [S_EXPR_MAS]

• Scheduling agreement release (operative delivery schedule, forecast/planning delivery schedule, last deliveries, display release history) [S_EXPR_REL]

• Message output (PPF Actions) [S_EXPR_MES]

• External procurement relationship costs [S_EXPR_COS]

• Purchase order history of the external procurement relationship [S_EXPR_HIS]

• Confirmations for the Scheduling Agreement Release [S_EXPR_CNF]

If the external procurement relationship is an APOscheduling agreement, then you can assign authorizations for all the check objects listed.

If the external procurement relationship is an OLTPscheduling agreement, info record or contract, then you can only assign authorizations for the external procurement relationship and the external procurement relationship costs.

• ACTVT: Activity
  You use this authorization field to define for whichactivities the authorizationis valid, that is which activities a user is allowed to carry out within the external procurement relationship.

The following activities are possible:

• Add or Generate [01]

• Change [02]

• Display [03]

• Delete [06]

• Execute [16]

Dependencies

You assign authorizations in user master data maintenance. You must specify exactly which external procurement relationship data or check objects the user is allowed to access and which type of access they are allowed.

For example, a user may be allowed to display all external procurement relationships but only change certain ones.

The system determines which external procurement relationships or check objects the user can accessby using a combination of the values for the authorization fields APO_LOCFR, APO_LOCTO, APO_PROD, APO_PL_PPS, APO_PLANER and APO_EXPOBJ.
The authorization field Activity(ACTVT) is used to control what type of access the user has to those external procurement relationships or check objects that he or she is allowed to access.

For each authorization check the system carries out a check against a combination of the authorizationfields 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 purchase order history for the external procurement relationship [APO_CDSOBJ = S_EXPR_HIS], because this can only be displayed.

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

Generate [01]	Change [02]	Display [03]	Delete [06]	Execute [16]
Master Data [S_EXPR_MAS]		Change	Display	Delete
Scheduling Agreement Release [S_EXPR_REL]	Generate		Display
Messages [S_EXPR_MES]			Execute
Costs [S_EXPR_COS]		Display
Purchase Order History [S_EXPR_HIS]		Display
Confirmation [S_EXPR_CNF]	Generate		Display

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

Fill RESBD Structure from EBP Component Structure   CPI1466 during Backup  
This documentation is copyright by SAP AG.


Length: 8936 Date: 20120526 Time: 185501     triton ( 234 ms )