sap許可權管理技術架構分析
General Authorization Object for Internal Orders
Definition
The general authorization object for Internal Orders (K_ORDER), allows you to issue authorizations for CO-OM responsibility areas in the Internal Orders component CO-OM-OPA.
Use
This authorization object lets you issue authorizations for the following actions within a CO-OM responsibility area for Internal Orders:
Maintain order master data
Manual order planning
Budget orders
Actions in the information system
You can issue each of the authorizations for one CO-OM responsibility area. If the order has a responsible cost center, the CO-OM responsibility area can be the order, the responsible cost center or a node of the standard hierarchy for Cost Center Accounting. If the order does not have a responsible cost center, the CO-OM responsibility area covers only the order itself.
Structure
The authorization object consists of the following fields:
Actions for the CO-OM authorization check
Order type
Internal order authorization: Authorization phase
Cost element
CO-OM responsibility area for authorizations
You can protect one or more of the following actions:
0001: Create master data
0002: Change master data
0003: Display master data
0008: Display change documents
0011: Release
0012: Undo release
0013: Complete technically
0014: Close
0015: Lock
0016: Unlock
0017: Set deletion flag
0018: Undo deletion flag
0019: Set deletion indicator
0020: Change user status
0030: Maintain settlement rule
0031: Maintain settlement parameters
1002: Create/change planning data
1003: Display planning data
1502: Change budget
1503: Display budget
3027: Select totals records
3028: Select line items
3029: Display extracts
If required, you can use authorization object K_ORDER as well as the other authorization objects for Internal Orders.
For more information, see the system documentation for authorization object K_ORDER.
[@more@]Authorizations
Use
In Work Clearance Management, various authorization objects and authorization profiles are required.
For more information on the SAP authorization concept, see Users and Roles (BC-SEC-USR).
Features
The following table shows you the authorization objects and authorization profiles that are used in Work Clearance Management.
Authorization Objects
Authorization Object
Description
Authorization Field
(see also Legend)
Use
S_TCODE
Transaction code
(TCODE)
All transactions
I_BEGRP
Authorization group
(TCODE, BEGRP)
All WCM objects
I_INGRP
Planner group
(TCODE, IWERK, INGRP)
All WCM objects
I_IWERK
Planning plant
(TCODE, IWERK)
All WCM objects
I_SOGEN
Approvals
(SWERK, PMSOG)
All WCM objects
I_CONFLICT
Checks/Simulations
(IWERK, WC_CONFTYP)
Operational WCDs
I_WCUSE
Uses
(IWERK, OBJART, OBJTYP, WCUSE, AKTTYP)
All WCM objects
I_FCODE
Function codes
(IWERK, OBJART, OBJTYP, WC_FCODE)
All WCM objects
I_VAL
Valuation
(IWERK, VAL)
Order
Legend for the Authorization Fields
Authorization Field
Description
AKTTYP
Activity type (Create, change, display)
BEGRP
Authorization group
INGRP
Planner group
IWERK
Planning plant
OBJART
Object type (Work approval, Application, Work clearance document)
OBJTY
Object category (Work clearance application, additional application, WCD template, Operational WCD)
PMSOG
Approval
TCODE
Transaction code
VAL
Valuation
WC_CONFTYP
Conflict category
WC_FCODE
Function code
WCUSE
Use of WCM objects
Authorization Profiles
Authorization Profile
Description
I_WCM_ALL
All authorizations for Work Clearance Management
I_CONF_ALL
All authorizations for checks and simulations
I_FCODE_ALL
All authorizations for function codes
I_WCUSE_ALL
All authorizations for uses
I_VAL_ALL
All authorizations for the valuation
I_PM_ALL
All authorizations for Plant Maintenance (PM)
See also:
Electronic Signature
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/7868752/viewspace-1060674/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 使用者角色許可權管理架構架構
- 資料許可權技術驗證
- PostgreSQL技術大講堂 - Part 8:PG物件許可權管理SQL物件
- 4、許可權管理
- sql許可權管理SQL
- RBAC許可權管理
- MySQL許可權管理MySql
- 許可權管理策略
- PostgreSQL:許可權管理SQL
- Odoo許可權管理Odoo
- 特殊許可權管理
- django開發之許可權管理(一)——許可權管理詳解(許可權管理原理以及方案)、不使用許可權框架的原始授權方式詳解Django框架
- Security 10:許可權管理
- casbin-許可權管理
- 許可權系統的基本概念和架構架構
- Android6.0------許可權申請管理(單個許可權和多個許可權申請)Android
- DRF內建許可權元件之自定義許可權管理類元件
- Django(63)drf許可權原始碼分析與自定義許可權Django原始碼
- Spring security(五)-完美許可權管理系統(授權過程分析)Spring
- 基於全流量許可權漏洞檢測技術
- 「Android6.0許可權適配| 掘金技術徵文 」Android
- Windows 反除錯技術——OpenProcess 許可權過濾Windows除錯
- 賬號和許可權管理
- 關於mysql許可權管理MySql
- Linux 下許可權的管理Linux
- 1.6.1. 管理員許可權
- Linux 中的許可權管理Linux
- ThinkPHP5+許可權管理PHP
- ubuntu 許可權管理設定Ubuntu
- fastadmin的許可權管理authAST
- MySQL許可權管理實戰MySql
- SAP Business Application Studio的許可權控制APP
- Confluence6對比系統管理員許可權和Confluence管理員許可權
- 『學了就忘』Linux許可權管理 — 55、檔案特殊許可權Linux
- 美顏SDK架構技術分析架構
- 今日頭條技術架構分析架構
- 如何獲取最高管理員許可權 win10教育版最高管理員許可權Win10
- Vue2.0 + ElementUI 手寫許可權管理系統後臺模板(二)——許可權管理VueUI
- 許可權之選單許可權