re_fx master data tables

SAP Note

Header Data

Symptom

You prepare the upgrade to Release ERP 2004, ERP 2005 or a subsequent release. This SAP Note is also relevant if you perform enhancements or customer developments in the Release R/3 Enterprise Extension 2.0 (for example, if you use API function modules, implement Business Add-Ins, or copy and adjust Smart Forms). This SAP Note helps you to estimate and minimize any subsequent effort for the upgrade. This SAP Note is not relevant for customers who start using RE-FX with Release ERP 2004.

Other Terms

Migration

Reason and Prerequisites

In Releases R/3 Enterprise Extension 1.1 and R/3 Enterprise Extension 2.0, some of the real estate master data is stored in tables that belong to Classic Real Estate. To enable a manageable migration to the new real estate solution (RE-FX) for customers of Classic RE, new master data tables and transaction data tables are used as of Release ERP 2004. This change affects all customers with Releases Enterprise Extension 1.1 and Enterprise Extension 2.0. As of Release ERP 2004, Classic RE and RE-FX no longer use master data tables and transaction data tables together. As of Release ERP 2004, we provide an upgrade program (see SAP Note 734981), which copies the data from the previously used tables into the new tables. Neither the definition of the previously used tables nor the data itself are changed or deleted. This means that no data is lost. Since all standard programs access the new tables as of Release ERP 2004, additional effort is required by you only if you access these tables as part of the customer developments mentioned above. No incompatible changes were made to Business Add-In definitions during the table change. However, as an exception, incompatible changes were made to the interface of the BAPI function modules and API function modules. The adjustment effort for these changes is minimal. However, if you want to access the standard data from within customer-specific enhancements, we recommend that you use the API modules.

What are the differences between the new tables and the old tables?

General changes for all new tables are as follows:

l The primary key is INTRENO instead of the semantic key.

l The standard field name for the object number is OBJNR (incompatible change of the ABAP Dictionary structure for parameters of the API modules).

l The standard field name for the authorization group is AUTHGRP (incompatible change of the ABAP Dictionary structure for parameters of the API modules).

l The name of the real estate object now has the standard length 60 (the field extension also applies for BAPI structures, API structures, and screens).

l Unnecessary fields from the Classic RE tables are not copied to the RE-FX tables.

l Various data elements, in particular for the semantic key fields (for example, number of the business entity), are replaced by new data elements. The underlying technical data type and the field length remain unchanged in each case.

The following overview contains the new tables with the changed field names. However, only the fields from the Classic RE tables that are actually used in RE-FX are listed.

l Business entity: Old table name: VIOB01 => new: VIBDBE

The current number levels for each business entity for the assigned buildings, properties, and rental objects are maintained in the table VIBDSUBOBJNUM.

l Property: Old table name: VIOB02 => new: VIBDPR

681951 - New master data tables as of ERP 2004 & subsequent releases

Version 10 Validity: 03.09.2012 - active Language angielski

Released On 03.09.2012 11:17:35

Release Status Released for Customer

Component RE-FX Flexible Real Estate Management

BW-BCT-RE-REFX Flexible Real Estate Management

Priority Recommendations / Additional Info

Category Upgrade information

Old New Short Description

J_OBJNR OBJNR Object Number

BERGRP AUTHGRP Authorization Group

SMIETSP RLRA Representative List of Rents

NUMKIGE (separate tab.) Building number range

NUMKIGR (separate tab.) Number range property

NUMKIME (separate tab.) Number range rental object




Other Components

l Building: Old table name: VIOB03 => new: VIBDBU

l Rental object: Old table name: VIMI01 => new: VIBDRO

l Real estate contract: Old table name: VICN01 => new: VICNCN

l Contract objects: Old table name: VIOBOV => new: VIBDOBJASS

The table VIBDOBJASS is also used for other assignment types, for example, for the assets, functional locations, and so on, for a real estate object. The assignment type is stored in the field OBJASSTYPE. The assignment type for contract -> object or object group is '10', and the assignment type for object group -> object is '11'.

l Asset assignment: Old table name: VIOB37 => new: VIBDOBJASS

The link to the asset is made using the field OBJNRTRG instead of using the fields BUKRS, ANLA1, and ANL2. The object number for the field OBJNRTRG is generated by concatenating the values of BUKRS (4 characters), ANLA1 (12 characters), and ANL2 (4 characters).

l Secondary key: Old table name: VIZNRN => new: VICAINTRENO

No field names have been changed. The primary key is now INTRENO instead of IMKEY. The keys of all real estate objects are now saved redundantly in the table. Up to now, an entry was written in the table VIZNRN only if the IMKEY was generated (in other words, only when the real estate object was released). When creating the real estate object, the entry is immediately written into the table VICAINTRENO.

l Settlement unit: Old table name: VIAK03 => new: VISCSU

l Settlement variant for each SU: Old table name: VIAK04 => new: VISCSURH

Instead of the fields BUKRS, SWENR, SNKSL and SEMPSL, the field INTRENO is now used as a reference to the settlement unit.

l Cost collector: Old table name: VIAK25 => new: VISCCC

Instead of the fields BUKRS, SWENR, SNKSL and SEMPSL, the field INTRENO is now used as a reference to the relevant settlement unit.

l Settlement units for each master settlement unit: Old: VIAK26 => new: VISCSUREL




SLAGK RLRALOC Location Class


SNKS OBJNR Object Number


ROTYPEEX (obsolete) Type of Rental Object (External)

XLAGE RLRALOC Location Class

XAUSTKL RLRAFIXFITCATE Fixtures and Fittings Category


RECNOBJNR OBJNR Object Number

RECNAUTHGR AUTHGRP Authorization Group

RECNEND RECNEND1ST Date of First Contract End


FOR_OBJNR OBJNRSRC Initial object

RE_OBJNR OBJNRTRG Assigned object

DATGAB VALIDFROM Assignment from

DATBIS VALIDTO Assignment to


RE_OBJNR OBJNRSRC Real estate object

DATGAB VALIDFROM Assignment from

DATBIS VALIDTO Assignment to

XUNUTZA ISMAINASSET Asset Is Leading Asset


SNKS OBJNR Object Number


DAEEND VALIDTO Valid To

XTEXTAE XSU Name

SMIETR TENANCYLAW Tenancy law

HAS_COSTOBJECT HASCOSTOBJECT Has Cost Object SUs

JNOTAXCORR NOTAXCORR No Input Tax Adjustment

UEBERAE see SUTYPE Actual Master Settlement Unit


DGULTAB VALIDFROM Valid From

ABRVAR SETTLVARIANT Settlement Variant


DPERBEG VALIDFROM Start of Settlement Period

DPEREND VALIDTO End of Settlement Period

ABRVAR SETTLVARIANT Settlement Variant

DPEROEFF RELEASEDON Opened on

DPERSCHL CLOSEDON Closed on

DABRECHN SETTLEDON Settled on

VVABBLN PROCESSID Settlement ID


DGUELEMP VALIDFROM Valid from

EQUINUM EQUIVNUM Equivalence Number

Instead of the fields BUKRS, SWENR, SNKSL and SEMPSL, the field INTRENOSRC is now used as a reference to the master settlement unit. Instead of the fields TBUKRS, TSWENR, TSNKSL and TSEMPSL, the field INTRENOTRG is now used as a reference to the assigned settlement units.

Removed table from flexible Real Estate Management

l Assignment of functional locations: Old table name: VIBDPMFL => new: VIBDOBJASS

Instead of INTRENO, the real estate object is now stored in the field OBJNRSRC with its object number. Instead of using TPLNR, the reference to the functional location is now made using the relevant object number in the field OBJNRTRG. The assignment type for the functional locations is '61' (field OBJASSTYPE).

Further changes

The example function module RECN_NUMBER_GENERATE_DEFAULT for determining the contract number is now provided as an API module under the name API_RE_CN_NUM_GENERATE_BY_OBJ. The Business Transaction Event (BTE) 00708001 is no longer executed to determine the contract number using a user exit. Use the method GET_NUMBER of the Business Add-In RECN_CONTRACT instead. For more information, see SAP Note 747506. Redundant function modules have been deleted in the function groups for the Business Data Toolset (BDT) applications. This change is relevant for you only if you have made own enhancements on the user interface for the real estate master data. According to the example from SAP Note 690900, only the use of the function module RExx_GET_BUSOBJ of the relevant function group RExx is required and allowed. In particular, direct access to the basic data using the BDT modules is no longer supported. The module RExx_GET_BUSOBJ with the subsequent call of API_RE_xx_GET_DETAIL should be used instead (see example function groups RExx_EXT_EXAMPLE according to SAP Note 690900).

Solution

What must be taken into account for customer developments?

Do not access tables directly using SELECT. To read data, use the "GET_DETAIL" BAPI function module or API function module for the relevant object type instead. As of Release ERP 2004 with Support Package 2, the "GET_LIST" BAPI function modules or API function modules for mass access are also available. To obtain an overview of all BAPI function modules for RE-FX, search for function modules with the name BAPI_RE_* in the Function Builder (transaction SE37) or in the Repository Information System (transaction SE15) . For API modules, use the search variant API_RE_*. If you use direct SELECTs, the business logic, which specifically formats the data if necessary, is not executed. If there are changes to the table design - as in this case - the expected data is no longer found in this table. For the object selection within your reports, you can use one of the following logical databases:

l REAO - Architectural Object

l REBD - master data of usage view

l REBP - business partner for real estate objects

l RECN - real estate contracts

Do not change table data directly using INSERT, UPDATE or DELETE, but use the "CREATE" and "CHANGE" BAPI function modules or API function modules for the relevant object type. If direct changes are made, the business logic is not executed, which means that there may be inconsistent data or additional data may be missing (for example, change documents). For data declarations and for the parameterization of methods, function modules, form routines, and so on, do not use the table reference or the data element, but use the structure reference instead. Example for number of business entity: DATA: ld_swenr TYPE bapi_re_bus_entity_int-swenr. "korrekt DATA: ld_swenr TYPE vibdbe-swenr. "falsch DATA: ld_swenr TYPE swenr. "falsch

Which subfunctions that are relevant for customer-specific enhancements are affected by the changes?

User-defined fields

Before executing the migration program, you must insert all user fields that exist in the old tables into the new tables. The migration program checks whether all required fields exist in the new tables and terminates the migration in the case of an error. For the definition of user fields, we recommend the following structuring: First create a separate ABAP Dictionary structure for the user fields of an object type (using transaction SE11). In this ABAP Dictionary structure, define all user fields and then activate the structure. Display the new database table in transaction SE11 and double-click the entry .INCLUDE CI_VI... in the field overview. Create the relevant CI include structure and insert the separate ABAP Dictionary structure with the user fields using .INCLUDE. Activate the CI include structure. As a result, the user fields are part of the master data table.

Customer-specific reports

If you have already created your own reports (or similar), check whether you are using the tables specified above directly. To do this, use the where-used list for the relevant tables. In the dialog box for the where-used list, restrict the search range as required, for example, to the packages Y* and Z*. Replace the usages as described above (for example, by calling an API module or adjusting the data declaration).

Use of API function modules

Some field names of the basic data structure for the relevant object type have been changed, for example, the field names for the object number and authorization group. This incompatible change affects, for example, the parameter ES_BUS_ENTITY of the module API_RE_BE_GET_DETAIL for reading the data of a business entity. If you previously used the field ES_BUS_ENTITY-J_OBJNR, the source code must be changed to the field ES_BUS_ENTITY-OBJNR. You can easily identify all relevant parts of the source code by executing a mass syntax check for the customer-specific source code. To do this, call transaction REDSRS01 and enter the customer-specific packages (for example, Y* and Z*) instead of the package RE_*. If errors are found, you can display the relevant program by double-clicking. Correct the syntax errors by adjusting the field names in the source code and then activate the program. For this reason, implementations of Business Add-Ins may also have syntax errors. These errors are displayed in the implementing class using the mass syntax check. The field names are adjusted in the same way as for other callpoints of the API modules that are outside the Business Add-In implementations.

Correspondence with Smart Forms

During the setup of the Smart Form correspondence, the required forms are usually copied into the customer namespace and these copies are then adjusted. We recommend that you regenerate the copied forms after upgrading to ERP 2004 or a subsequent release. The report RFRECPSFTLGEN is available for this. Execute the report using transaction SE38 and enter the customer-specific forms for RE-FX (for example, Y* and Z*) in the "Form Name" field. Any generation errors that occur are due to changed field names, which are listed in the following overview. Use the Form Builder (transaction SMARTFORMS) to change the field names. Switch to change mode of the relevant form and choose "Check". From the error messages, click the "Node" field to navigate directly to the incorrect text element. Correct the field names (always use uppercase letters) and then activate the form.

l Master data summary - business entity, copies of the form RE_BE_010

KBRART FUELTYPE Fuel type

Field: Description of Representative List of Rents

Old: BUSINESS_ENTITY-XMIETSP

New: BUSINESS_ENTITY-XRLRA

l Master data summary - contract, copies of the form RE_CN_010

l Service charge settlement, copies of the form RE_CN_150

Further interface changes to BAPIs and API modules

Release ERP 2004 Support Package 2 supports new compatible parameters and new data fields in existing parameters. For more information, see SAP Note 741557. The following incompatible change was also required for this: For the BAPI modules and API modules for all master data objects, access to assigned objects such as functional locations and assets is now executed using the common parameter OBJ_ASSIGN (object assignment). The previous separate parameters ASSET (assigned assets) and FUNC_LOC (assigned functional locations) do not apply. Change any calls for these modules accordingly.

New Customizing tables

In the same way as for application data, we do not recommend accessing Customizing tables directly. Unlike application data, Customizing data is rarely required within enhancements. For this reason, only the table names are mentioned in the following overview. Check whether you use tables from the column "Old" in your source code and replace any usages accordingly.

l New Customizing tables

Validity

References

This document refers to:

SAP Notes

This document is referenced by:

Field: Date of First Contract End

Old: TERM_PERIOD-RECNEND

New: TERM_PERIOD-RECNEND1ST

Field: Name of Service Charge Key

Old: SETTL_CNPART_DETAIL-XTEXTSCKS

New: SETTL_CNPART_DETAIL-XSCKEY

In each case, field: Name of Service Charge Key

Old: SCR_RESULT-XTEXTSCKL

New: SCR_RESULT-XSCKEY

Old: SCR_MSU-XTEXTSCKL

New: SCR_MSU-XSCKEY

In each case, field: Name of settlement unit

Old: SCR_MSU-XTEXTSU

New: SCR_MSU-XSU

Old: SCR_AJROSU-XTEXTSU

New: SCR_AJROSU-XSU


TPR5/TPR9 TIVBPOBJROLE Assignment of Role to Object Type

TIVCNCCTBPROLE TIVBPOBJROLE Assignment of Role to Object Type

TIPZZ TIVCACLSET Client-specific settings

TIPZB TIVCACCSET Company Code-Dependent Settings

TIVCNOBJ TIVBDOBJASS Allowed Assignment Objects per Object Type

TIV71 TIVBDCHARACT Fixtures and Fittings Characteristic

TIV7A TIVBDCHARACTT Fixtures and Fittings Characteristic (Text)

TIVAJMAXINC TIVAJMINMAXINC Capping Provisions

TIV05 TIVSCSCKEY Service Charge Keys

TIVT5 TIVSCSCKEYT Service Charge Key (Text)

Software Component From Rel. To Rel. And Subsequent

EA-APPL 500 500

1548018 DMS document links to REFX lost

1670535 RES and REfx - facts and updates

517673 Flexible Real Estate: Features and release restrictions

688527 Adjustments to new master data tables for RE-FX

734981 RE-FX upgrade from 470x200 to ERP 2004 or a subsequent relea

747506 User exit for the determination of the contract number

761835 Conversion program: Change documents - dump field symbol

764532 Conversion program: Change documents - PM - missing objects

764539 Conversn progrm: Change documents - OBJASS - missing objects

765144 Conversion program: Change docs. depend. data (missing obj.)

771505 Conversion program: STORAGE_PARAMETERS_WRONG_SET

782947 Programming interfaces for RE-FX

870859 Homebuilding Real Estate Sales - Classical v.s. RE-FX

SAP Notes (13)

688527 Adjustments to new master data tables for RE-FX

761835 Conversion program: Change documents - dump field symbol

764532 Conversion program: Change documents - PM - missing objects

764539 Conversn progrm: Change documents - OBJASS - missing objects

765144 Conversion program: Change docs. depend. data (missing obj.)

771505 Conversion program: STORAGE_PARAMETERS_WRONG_SET

1670535 RES and REfx - facts and updates

1548018 DMS document links to REFX lost

517673 Flexible Real Estate: Features and release restrictions

734981 RE-FX upgrade from 470x200 to ERP 2004 or a subsequent relea

870859 Homebuilding Real Estate Sales - Classical v.s. RE-FX

747506 User exit for the determination of the contract number

782947 Programming interfaces for RE-FX

re_fx master data tables

Documents