Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Regarding the Data Ownership Authorization and Data Ownership Exceptions

Dear All,

I have one query regarding the Data Ownership Authorizations and Data Ownership Exceptions.

I just want to know what the actual these terms means?

and what is the use of these fields.............

Hope for immediate response.........

Thanks All..........

Former Member
replied
<body><p>Hi,</p><p></p><p>Here is a brief explanation:</p><p></p><pre __jive_macro_name="quote"><p></p><p>Data Ownership enables managers to determine which documents could be viewed and updated by regular users in SAP Business One.</p><p>Data ownership is relevant only for users who are not defined as Super Users in the Define Users window. This way, managers (i.e. super users) can control the data accessible to each of their employees.</p><p>An authorization can be granted for every document type and even at the document row level.</p><p>Data ownership is maintained according to the data defined for your employees in the Human Resources module, therefore it is highly recommended to read the document dealing with Human Resources prior to defining data ownership in your company.</p><p></p><p>Initial Definitions</p><p>1. Initializing Data Ownership in your company.</p><p>2. Defining users.</p><p>3. Assigning a license for every user.</p><p>4. Defining employees in the Human Resources module:</p><p>a. Defining employees in the Employee Master Data window.</p><p>b. Defining users which function as sales employees as Sales Employees</p><p>in the Human Resources module.</p><p>c. Defining a direct manager for every employee.</p><p>d. Linking employees to departments and branches.</p><p>e. Linking employees to teams if required.</p><p>5. Defining general authorizations for every regular user.</p><p>6. Defining relevant data ownership authorizations for every employee.</p><p>7. Defining data ownership exceptions if required.</p><p></p><p>Initializing Data Ownerships</p><p>In order to initialize data ownership in your company, go to Administration --&gt; System</p><p>Initialization --&gt; Authorizations --&gt; Data Ownership Exceptions.</p><p></p><p>In this window, check the box Owner Filtering Active and click on Update.</p><p></p><p>Defining Employees</p><p>Contrary to general authorizations which can be granted at the functional level per user, data ownership authorizations are granted for employees defined in the Human Resources module.</p><p>Human Resources --&gt; Employee Master Data</p><p></p><p>In order to work with data ownership authorizations, it is necessary to define the</p><p>following data for relevant employees:</p><p>u2022 User Code u2013 select a corresponding user code as defined under Definitions &#56256;&#56518;</p><p>General &#56256;&#56518; Define Users. Note that this field is mandatory for working with the</p><p>data ownership.</p><p>u2022 Sales Employee u2013 in case an employee functions as a sales employee in your</p><p>company, you need to specify his corresponding sales employee as defined</p><p>under Definitions &#56256;&#56518; General &#56256;&#56518; Define Sales Employees. Click the drop down</p><p>menu in this field and select the corresponding sales employee or select Define</p><p>New to define a new one. In the above example, the sales employee Ruth</p><p>Jefferson is selected in the Sales Employee field, thus establishing a</p><p>connection between Ruth's employee master data and her sales employee</p><p>name which can be linked to sales and purchasing documents.</p><p>u2022 Manager u2013 select the manager of the current employee. Note that only existing</p><p>employees will be available for selection.</p><p>u2022 Department</p><p>u2022 Branch</p><p>u2022 Teams u2013 you can define employees as team members or team leader under</p><p>the Membership tab page.</p><p></p><p>Authorizations</p><p>General Authorization Before you start defining data ownership authorizations, make sure to grant functional authorizations to the regular users in your company. These functional authorizations</p><p>determine whether a user can open documents, reports and various windows in Read Only or Full modes or not at all.</p><p>These authorizations can be defined under Administration --&gt; System Initialization --&gt; </p><p>Authorizations --&gt; General Authorization</p><p></p><p>Ownership Types</p><p>Data ownership is based on the relationships among the employees in the company.</p><p>The ownership types are:</p><p>1. Peer u2013 this ownership type describes the relationships among all the employees who have the same direct manager. A Peer authorization allows an employee to access documents owned by one of his peers. In the above chart, Bill Levine and Sophie Klogg are peers.</p><p>2. Manager u2013 this ownership type can be defined for the employee's direct manager. A Manager authorization allows an employee to access documents owned by his direct manager. In the above chart, Daniel Jordan is the direct manager of Bill Levine and Sophie Klogg.</p><p>3. Subordinate - this ownership type can be defined for all the employees that work directly under the same employee. A Subordinate authorization allows an employee to access documents owned by all his subordinate employees. In the above chart, Bill Levine and Sophie Klogg are subordinates of Denial Jordan.</p><p>4. Department - this ownership type describes the relations among all the employees that work in the same department. A Department authorization allows an employee to access documents owned by all the employees in his department. In the above chart, Daniel, Bill, Sophie, Barbara, Peter, Ruth and Brad belong to the Sales department.</p><p>5. Branch - this ownership type describes the relationships among all the employees that work in the same branch. A Branch authorization allows an employee to access documents owned by all the employees in his branch. In the above chart, Ron Palmer, Daniel Jordan and Linda Carter belong to the Main branch.</p><p>6. Team - this ownership type describes the relationships among all the employees that belong to the same team. A Team authorization allows an employee to access documents owned by all the employees in his team.</p><p></p><p>Note! It is possible to define several ownership types for every employee, thus causing these ownerships to overlap. Therefore, it is recommended to define the minimal number of data ownership authorizations.</p><p>For example, if you would like Daniel Jordan to be able to access data owned by all of his subordinates (starting from Sophie and Bill and ending with Peter and Ruth) it is recommended to grant Daniel a Department authorization. It is not necessary to grant</p><p>Daniel an additional Subordinate authorization since a Department authorization</p><p>already allows him to access the documents owned by all his subordinates.</p><p>Data Ownership Authorizations</p><p>Administration --&gt; System Initialization --&gt; Authorizations --&gt; Data Ownership Authorizations</p><p>Use this window to define the ownership types relevant for each of your employees.</p><p></p><p></p></pre><p></p><p>there are 10 pages anymore to know more about this. let me know if you need it.</p><p></p><p></p><p>Rgds</p></body>
0 View this answer in context
Not what you were looking for? View more on this topic or Ask a question