Hierarchy
⤷ RE-FX (Application Component) Flexible Real Estate Management
⤷ RE_CA_CU (Package) RE: Customizing (IMG) and Area Menu
IMG Activity
ID | REFXV_TIVBPGRPCC | Define Company Code-Dependent Number Range (Partner Grouping) |
Transaction Code | S_PLN_06000370 | (empty) |
Created on | 20030704 | |
Customizing Attributes | REFXV_TIVBPGRPCC | Define Company Code-Dependent Number Range (Partner Grouping) |
Customizing Activity | REFXV_TIVBPGRPCC | Define Company Code-Dependent Number Range (Partner Grouping) |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | REFXV_TIVBPGRPCC |
Use
In the Customizing activity Specify Number Range (Grouping) and Address Type you determine for each application (example: real estate contract) and role (example: caretaker) which grouping should be used. Sometimes partners created in different company codes need to use different groupings (and therefore also number ranges). This is especially relevant for customer or vendor roles since the account group of the customer/vendor is determined by the grouping.
Requirements
Standard settings
Activities
You have the option of determining the grouping of each application category, depending on the three attributes:
- Business partner category
- Company code
- Role
It is possible to leave any of these three attributes blank (or two of them, or even all of them) if the grouping is independent of the attribute. When you create a partner, the system first checks all three characteristic values and then searches for generic (blank) key fields, giving priority to the most specific entry. The attribute "role" is more specific that the company code, and the latter is more specific than the business partner category.
Example
All business partners in company code 0001 have to be created for all contracts with grouping A. In company code 0002 the master tenant with customer account TR0600 is to be created with grouping B. The following applies for all other roles in this company code: grouping C is to be used for natural persons (category 1) and grouping D for all other business partner categories.
You should make the following settings (for easy understanding, a blank entry is indicated by "-"):
App. Typ CoCd Role Grouping
0036 - 0001 - A
0036 - 0002 TR0600 B
0036 1 0002 - C
0036 - 0002 - D
If you now try to create a master tenant in company code 003, the system will not find any information in this table. It searches for an entry in the company code-independent table. If there is no entry there, when you try to create the partner the system issues an error message.
If you wish to edit a grouping that is intended to be valid independent of type, company code and role, you should leave these fields blank and make the following entries for the contract:
Appl Typ CoCd Role Grouping
0036 - - - X
The system then uses grouping X for all partners created in contract management and for whom there are no specific entries in the table. The company code-independent table is not read in this case.
Note
It is not possible to determine the grouping to be used without considering the application.
Business Attributes
ASAP Roadmap ID | 250 | Define Number Range and Basic Structures |
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 | REFXV_TIVBPGRPCC | 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 |
V_TIVBPGRPCC | V - View | SM30 |
History
Last changed by/on | SAP | 20030704 |
SAP Release Created in | 200 |