Kontakt

Ansicht
Dokumentation

SIMG_CFMENUOFDIBEREC - Authorizations

SIMG_CFMENUOFDIBEREC - Authorizations

Addresses (Business Address Services)   Vendor Master (General Section)  
This documentation is copyright by SAP AG.
SAP E-Book

This is only an overview of the function. The actual settings have to be made in Basis Customizing.

Please note the following changes:Including profiles in roles

Exception: Maintenance of authorization groups (Authorization object F_RE_BRGRP) is carried out in Real Estate Customizing.

To make the setting for authorizations, see the 'Basis Components' Implementation Guide, chapter 'Authorization management'.

The composite profile "F_ISRE_ALL" is delivered as samples for the Real Estate authorizations. This profile contains all application and Customizing authorizations

  • required for the use of the Real Estate Management (RE) component

  • as well as the authorizations for processing loans and securities.

F_DARL_ALL All authorizations for Loans Management

F_DTFEED_ALL All authorizations for the asynchronous datafeed

F_IMMO_ALL All authorizations for Real Estate Management

F_IMMO_LIS MM Logistics Information System - all functions

F_PART_ALL Treasury business partner: All authorizations

F_TEXT_ALL Authorizations Maintenance Word processing

F_WERTP_ALL All authorizations for Securities Management

F_ZFREI_ALL All authorizations for the release

F_ZPART_ALL All authorizations for partner management

G_SETS_ALL Special Purpose Ledger - Sets: All authorizations

S_A.USER Administrator (Basis authorization)
  1. Master data maintenance of the real estate objects
The authorization object
  • 'FI_WEI_BUK' controls the access to the business entity maintenance.

  • 'FI_GEB_BUK' checks in which company code and for which business entities a user may maintain buildings.

  • 'FI_GBU_ACT' checks the access to land register data maintenance.

  • 'FI_GRU_BUK' checks in which company code and for which business entities a user may maintain properties.

  • 'FI_ME1_BUK' checks in which company codes and for which rental units a user may maintain business entities.

  • 'FI_RAU_BUK' checks in which company codes and for which business entities a user can maintain rooms.

  • 'F_RE_BRGRP' checks if the user has authorization for this group of objects by means of an application-defined authorization group that is defined in the master data. (Maintain Authorization Group)

  1. Rental agreement management
The authorization object
  • 'FI_BEW_ACT' checks whether a user may maintain applications.

  • 'FI_ZUO_ACT' checks whether a user may assign applications and/or a rental unit.

  • 'FI_MIE_BUK' determines in which company codes and for which business entities rental agreements can be edited.

  • 'F_RNT_OFF' determines in which company codes and for which business entitites offers can be processed.

  • 'FI_KUE_BUK' checks in which company codes and for which business entities notices for rental agreements can be processed.

  • 'F_RE_BRGRP' checks, on the base of an application-defined authorization group that is defined in the master data (offer, application, rental agreement), if the user has the authorization for this group of objects. (Maintain Authorization Group)

  1. Conditions
The authorization object
  • 'F_MIE_SKO' determines if a user can create, display, change conditions of a rental agreement.

  • 'FI_MIE_ALL' allows you to check the change authorization for rental agreement conditions. If required, authorization can be restricted to company code and business entity.

  1. Rental accounting
The new authorization object in 4.5A
  • 'F_PMT_TRNS' controls centrally in which company code which transactions for payment transactions (RA debit position/RU debit position) which user can carry out.

For compatibility reasons, the authorization object used before 4.5A 'FI_ZAH_BUK' is still used.
For new installations, you only choose the new object since the old object will not be used in future releases.
  • Rent adjustment
Rent adjustment master data
The authorization object
  • 'FI_MIS_ACT' determines if the user can display and/or maintain representative rent lists.

  • 'FI_VBE_BUK' determines in which company codes comparative groups can be maintained and rental units assigned.

Adjustment procedure
The new authorization object in release 4.5A
  • 'F_RNT_ADJ' controls centrally for each adjustment mode (adjustment method) if a user can simulate and/or calculate adjustments of condition types for rental agreements or rental units in a certain company code.

For compatibility reasons, the authorization objects used before 4.5A are still used.
For new installations, you only choose the new object since the old objects will not be used in future releases.
Consequently you should mark all old authorization objects with * authorizations.
The old authorization object
  • 'FI_GAR_BUK' checks if a user can simulate and/or calculate adjustments for garage rent in a certain company code.

  • 'FI_MOD_BUK' checks in which company code a user can carry out rent adjustment resulting from modernizations.

  • 'FI_ZLG_BUK' checks if a user can simulate and/or calculate adjustments for surcharges in a particular company code.

  • 'FI_FAG_BUK' checks if a user can simulate and/or calculate free rent adjustments for commercial agreements.

  • 'FI_FAW_BUK' checks if a user can simulate and/or calculate free rent adjustments for residential rental agreements in a particular company code.

  • 'F_ZIND_ACT' checks the access to the Real Estate function "Maintain/display index data" as well as the Securities function "Maintain/display securities index".

  • 'FI_IND_BUK' checks in which company codes a user can carry out index-linked rent adjustments.

  • 'FI_MIS_BUK' checks in which company codes a user can simulate and/or calculate adjustments to the representative list of rents.

  • 'FI_VWO_BUK' checks in which company codes a user can maintain/ display comparative apartments and/or adjustments.

  • 'F_UMV_BUK' checks in which company codes a user can carry out sales settlements and sales-based rent adjustments.

  1. Service charge settlement
The authorization object
  • 'FI_ABR_BUK' checks whether a user may create, change, display and/or delete settlement units.

  • 'FI_HEI_BUK' determines in which company codes a user may edit central heating systems.

  • 'FI_BKA_BUK' checks whether a user may carry out and/or simulate operating costs settlements in a certain company code.

  • 'FI_HKA_BUK' determines in which company codes a user may carry out heating expenses settlements.

  • 'F_RE_BRGRP' checks, by means of an application-defined authorization group defined in the master data of the settlement unit, if the user has the authorization for this group of objects. (Maintain authorization group)

  1. Management contract
The authorization object
  • 'F_MNG_CON' checks access to the maintenance of management contracts.

  • 'F_RE_BRGRP' checks, by means of an application-defined authorization group defined in the master data of the management contract, if the user has the authorization for this group of objects (Maintain Authorization Group)

  1. Information system
The authorization object
  • 'FI_BAV_BUK' controls the access to BAV data from the real estate application.

  • 'FI_NFO_BUK' is provided for the access check for analysis reports of Financial Assets Management.

  1. Further authorizations from other applications (for more information, see the corresponding Implementation Guides)
  • Creating and changing customer master records (direct creation from partner maintenance)

  • Posting documents

  • LIS reporting

  • Word processing: F_ZTXT_ANZ Display text elements

  1. Partner data
The authorizations described below are checked in the Treasury business partner. The authorizations marked with 2.2F are already available for Release 2.2F and are also included in Release 3.0. The authorizations marked with 3.0 are new authorizations introduced in 3.0D.
  1. Maintenance authorization (2.2F)
The authorization for creating, changing and displaying the business partner is checked as transaction authorization when partner management is accessed.
The authorization for releasing business partners is checked separately (see e).
  1. Authorization on role categories (2.2F)
The authorization on a role category, for example, Treasury partner, tenant, borrower is necessary to be able to create, change or display role-specific data of a business partner.
If a system user does not have the authorization of an existing business partner role, this role is not displayed in the role overview of the partner management. Consequently, the user does not obtain any information on whether or not the partner exists.
  1. Authorization group in the business partner (3.0D)
Partners can be grouped together by means of the 'Authorization group' field in the administration data of the business partner, and only certain administrators are allowed to maintain/display this partner. For these administrator, an authorization has to be created in the user master for the authorization group that is entered in the partner master.
Example:
Distinction by domestic and foreign business partners since different administrators maintain these two groups.
For all domestic business partners, "INL" has to be entered in the authorization group, and "AUSL" for all foreign partners.
The "domestic" administrator receives authorization for the "INL" authorization group, and the "foreign" administrator for the "AUSL" authorization group.
In other words, the administrators can only maintain those business partners who are assigned to their authorization group. To maintain an authorization group for the business partner function, the user requires authorization to create the authorization group.
  1. Authorization group for a role of a business partner (3.0D)
By means of the Authorization group field in the business partner role data, you can group partners together in an existing role, and allow only certain administrators to maintain/display this role data of the partner. For these administrators, you have to create an authorization in the user master for the authorization group that is entered in the role data of the partner.
Example:
Distinction between borrowers, who are employees, and external borrowers since different administrators maintain these two groups.
Here, the explanations of c) are also valid at role level.
For all domestic business partners, "INL" has to be entered in the authorization group, and "AUSL" for all foreign partners. The domestic administrator receives authorization for the "INL" authorization group, and the "foreign" administrator for the "AUSL" authorization group. In other words, the administrators can only maintain those business partners who are assigned to their authorization group. To maintain an authorization group for the business partner function, the user requires authorization to create the authorization group.
  1. Authorization on role categories:
Authorization object: F_T_PART_R
Activity:
'01' Create
'02' Change
'03' Display
role category: see table contents TPZ3
Sample authorization: F_T_PARTROLE, F_T_TR_ROLE
  1. Authorization group in the business partner
Authorization object: FZ_PRT_BEG
Activity:
'01' Create = Maintain the authorization group
'02' Change (a partner in the authorization group)
'03' Display (a partner in the authorization group)
Authorization group: freely assignable four-digit text field
Sample authorization: FZ_PRT_ALL, FZ_PRT_ANZ
Information for 2.2 Loans, Securities and Real Estate customers:
This authorization object has already been used in the loans and securities partner for 2.2F and is now checked exactly the same way in the new business partner for 3.0D. Consequently, authorizations already defined can still be used.
  1. Authorization group of a business partner role
Authorization object: F_T_PART_B
Activity:
'01' Create = Maintain the authorization group
'02' Change (a partner in the authorization group)
'03' Display (a partner in the authorization group)
role category: see table contents of table TPZ3
Authorization group: freely assignable four-digit text field
Sample authorization: F_T_GP_B_ALL
  1. Release authorization
Authorization object: FZ_FRG_OST
Authorization object: BPAR
Release status: all statuses except '99' and 2nd position 'x0' are useful:
for example,,'22' = entered, dual control
,,'21' = first release, dual control
,,'33' = entered, triple control
Activity:
,,'43' Release
,,'03' Display
Sample authorization: F_PART_FRG_A





rdisp/max_wprun_time - Maximum work process run time   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 19044 Date: 20240523 Time: 183602     sap01-206 ( 194 ms )