SAP ABAP IMG Activity REFXREBUPA_TB003 (Define BP Roles)
Hierarchy
EA-FIN (Software Component) EA-FIN
   RE-FX (Application Component) Flexible Real Estate Management
     RE_CA_CU (Package) RE: Customizing (IMG) and Area Menu
IMG Activity
ID REFXREBUPA_TB003 Define BP Roles  
Transaction Code S_ALN_01002432   (empty) 
Created on 20031119    
Customizing Attributes REFXREBUPA_TB003   Define BP Roles 
Customizing Activity REFXREBUPA_TB003   Define BP Roles 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name REFXREBUPA_TB003    

Context

The central business partner is also used in Flexible Real Estate Management (RE-FX). Here you define which roles the business partner is allowed to have.

Use

In this IMG activity you define the business partner roles and their attributes.

You also define the role categories with other relevant data.

The BP role categories are stored in a table that has the delivery class E.

Requirements

Standard settings

The following business partner roles are delivered by SAP:

  • 000000
  • BUP001
  • BUP002
  • BUP003
  • BUP004
  • BUP005
  • FS0000

The following role categories are delivered by SAP:

  • BUP001
  • BUP002
  • BUP003
  • BUP004
  • BUP005

The following BP views are delivered by SAP:

  • 000000
  • BUP001
  • BUP002
  • BUP003
  • BUP004
  • BUP005
  • FS0001

Do not modify these settings.

You should modify these entries only if, for example, you

  • Want to use a completely different screen sequence
  • Need additional screen sequences for your own role categories
  • Have defined your own processes that should be programmed on role categories.

Attention

You should not, in particular, modify the role categories delivered by SAP because SAP programs may access them directly.

Activities

First make the following settings for the business partner role:

  1. Attributes of the Role
    1. Enter an alphanumeric, six-character key for the BP role.
    2. Enter a title as the short form and a description as the long form for the role's text.
    3. Set the Hide flag if the role should not appear in the dropdown list box of the role selection in the dialog.
  2. Attributes of the Role Category
    1. Select a role category if the role should serve as a basis for programming.
    2. Several roles can be assigned to a role category. The assigned roles are displayed in the overview. You can navigate to the respective role by double clicking.
    3. Determine which role should be assigned as the standard role.
    4. The indicator is set automatically when a new role is created, provided the role category in question has not already had other roles assigned to it.
      The indicator ensures that only one role can be read when the role category is used as a basis for programming.

      Assigning a role category allows you to ensure that the role is updated in the table for the roles (BUT100).

  3. Settings for the Interface Control
    1. Assign a BP view.
    2. Define the BP view in the area menu of the Business Partner in the SAP Easy Access Menu under Business Partner -> Control -> Divisibility -> BP View (transaction BUSD).
      If a BP view is not assigned, the settings for the BP view 000000 (General BP) are used in the dialog.
    3. Enter the position in which the role should appear in the dropdown box of the role selection in the dialog.
    4. If you do not make an entry for the roles, they are sorted in alphabetical order.
  4. Save the data.

Define your own role categories, if necessary:

  1. Enter a six-character key for the role category in the customer namespace (Y* und ZÜ*).
  2. Enter a title as the short form and a description as the long form for the text of the role category.
  3. Enter a differentiation type (required entry).
  4. Specify for which business partner categories the role category can apply.
  5. Assign a business transaction to the role category, if necessary, and establish the influence on the transaction.

Example

Standard settings

The roles that are provided specifically for RE have names beginning with TR06 or TR08. In the standard system, there are the following business partner views:

  • FS001, FS002:
    Normal external role (such as architect, property developer, and so on). FS001 stands for the maximum possible values, that is, basically all fields can be maintained, and field status control is used to specify any fields that might not be needed. FS002 stands for the minimum possible values. Here only selected fields are available.
  • FLCU01:
    Business partner with customer account (such as, tenant)
  • FLVN01:
    Business partner with vendor account (such as, landlord)
  • BUP003:
    Employee (such as, real estate specialist)

For the first data transfer, the business partner view FS0005 is also available. At the time of the data transfer, assign this view to the role to which you want to transfer the partner. The view allows you to make entries for all fields of the business partner.

Note

The concept for the role has changed in RE-FX. In Classic RE, payment by means of a different account was dependent only on the existence of a business partner in the Alternative Payer role. This role is no longer used in RE-FX. If you want to (completely or partially) post receivables from conditions of the real estate contract to a different customer account, then use a partner with customer account with the role of Subsidizer.

Business Attributes
ASAP Roadmap ID 203   Establish Master Data 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG REFXREBUPA_TB003 0 ALN0000035 Business Partner 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
BUPA_TB003 C - View cluster SM34  
History
Last changed by/on SAP  20031119 
SAP Release Created in 500