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 | REFXV_TIVRAOPCCSET | Allow Partly Automatic Creation of Company-Code-Dependent Data |
| Transaction Code | S_AEN_10000247 | (empty) |
| Created on | 20050111 | |
| Customizing Attributes | REFXV_TIVRAOPCCSET | Allow Partly Automatic Creation of Company-Code-Dependent Data |
| Customizing Activity | REFXV_TIVRAOPCCSET | Allow Partly Automatic Creation of Company-Code-Dependent Data |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | REFXV_TIVRAOPCCSET |
Use
In the course of condominium owners' association (COA) management, one vendor can be the business partner of different COAs. To be able to post to this vendor in a COA (that is, in the COA company code, see company code type), the following requirements have to be met:
- The vendor master record has to exist.
- The company-code-dependent data of the vendor has to exist.
Normally this is not the case for the first posting to this vendor in the COA.
During one-time posting, the system checks if the vendor exists in the company code. If this vendor does not exist, and if you set the Create Customer/Vendor? indicator in this activity, then the system displays a pushbutton in the one-time posting transaction in the application. You can choose this pushbutton to create a vendor in the company code.
If the current company code is a mandate company code, then the system first tries to copy the company-code-dependent data of the reference company code. If the vendor also does not exist in the reference company code, then the system creates the vendor using the default values you entered in Customizing.
It is not possible for the system to also create the data of the vendor that is not company-code-dependent from the one-time posting in the application. If you choose, you can create this data in another session.
Requirements
Standard settings
Activities
If you want the system to behave as explained above, then set the indicator in the reference company code and in any existing mandate company codes. The system then copies the indicator for any new mandates you create.
Example
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| 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_TIVRAOPCCSET | 0 | ALN0000042 | Rental Accounting |
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_TIVRAOPCCSET | V - View | SM30 |
History
| Last changed by/on | SAP | 20050111 |
| SAP Release Created in | 600 |
