28 Importing Real Estate Management Data (Release 9.2 Update)

This chapter discusses:

28.1 Understanding the Real Estate Management Data Import Process

Several programs are available to facilitate the import of real estate management data into the EnterpriseOne system. These programs use the standard EDI process, which involves these steps:

  1. Create flat files that are formatted using the same layout as their associated Z tables, and populate those flat files with your business data. Be aware that the first column in your flat file must include the Record Type value, and that you must use the delimiter and text qualifiers that are defined in the processing options of the associated version of the Inbound Flat File Conversion program (R47002C) you are using.

    Required fields for each flat file are provided later in this chapter.

    See Understanding Flat File Data Formatting in the JD Edwards EnterpriseOne Applications Data Interface for EDI Implementation Guide for additional information.

  2. Set up real estate transaction types (UDC 00/TT) and identify the name and location of your flat files using the Flat File Cross Reference program (P47002).

    See Defining the Flat File Cross Reference Table in the JD Edwards EnterpriseOne Tools Interoperability Guide.

  3. Run the specific version of the Inbound Flat File Conversion program (R47002C) to populate the specified Z table with the data from the flat file.

    Note that you can set up this program to automatically upload the data from the Z table into the EnterpriseOne table if there are no errors during processing. To do this, specify the inbound processor program and version in the processing options. If there are errors when processing the flat file conversion, the system does not run the inbound processor.

    See Processing EDI Documents in the JD Edwards EnterpriseOne Applications Data Interface for EDI Implementation Guide for additional information.

  4. Review and update the data in the Z tables.

  5. Upload edited data from the Z tables into the target EnterpriseOne tables using the specific inbound processor program.

This table describes the transaction types, tables, and associated programs that are available to facilitate the import of real estate data. Oracle recommends you import data in the order listed here to accommodate data dependencies:

Transaction Type (00/TT) R47002C Version and Z Table Review Program Inbound Processor and Target E1 Table
JDEBC Run version XJDE0051 to populate the F1512Z1 table. Review Unedited Bill Code Transactions (P1512Z1) Run the Inbound Bill Code Transaction Processor (R1512Z1I) to populate the Billing Code Extension table (F1512).
JDEUM Run version XJDE0056 to populate the F1507Z1 table. Review Unedited Unit Master Transactions (P1507Z1) Run the Inbound Unit Master Transaction Processor (R1507Z1I) to populate the Unit Master table (F1507).
JDEAM Run version XJDE0050 to populate the F1514Z1 table. Review Unedited Area Master Transactions (P1514Z1) Run the Inbound Area Master Transaction Processor (R1514Z1I) to populate the Area Master table (F1514).
JDELM Run version XJDE0052 to populate the F1501BZ1 table. Review Unedited Lease Master Transactions (P1501BZ1) Run the Inbound Lease Master Transaction Processor (R1501BZ1I) to populate the Lease Master Header table (F1501B).
JDELD Run version XJDE0053 to populate the F15017Z1 table. Review Unedited Lease Master Detail Transactions (P15017Z1) Run the Inbound Lease Master Detail Transaction Processor (R15017Z1I) to populate the Lease Master Detail table (F15017).
JDEMB Run version XJDE0054 to populate the F1511BZ1 table. Review Unedited Manual Billing Transactions (P1511BZ1) Run the Inbound Manual Billing Transaction Processor (R1511BZ1I) to populate the Lease Billings Master table (F1511B).
JDERB Run version XJDE0055 to populate the F1502BZ1 table. Review Recurring Billing Transactions (P1502BZ1) Run the Inbound Recurring Billing Transaction Processor (R1502BZ1I) to populate the Recurring Billings Master table (F1502B).

Note:

Once you have imported unit, area, bill code, lease master, and lease detail information, the order in which you import billing records (either manual or recurring) does not matter.

To assist you with importing lease data, sample .csv and .txt files are available for reference in the following My Oracle Support document:

https://support.oracle.com/epmos/faces/DocumentDisplay?id=2451522.1

28.2 Required Fields for Real Estate Management Data Upload Programs

When uploading data from a flat file to a Z table, all of the required fields must contain values. These fields are required in all inbound flat files:

  • User Id

  • Batch Number

  • Transaction Number

  • Line Number

  • Direction Indicator must be set to 1.

Additionally, you must ensure that the required fields for the table you are importing data into contain values. These sections list the required fields for importing real estate data.

Bill Code Required Fields

These are the required fields for importing bill code data:

  • Bill Code

Unit Master Required Fields

These are the required fields for importing unit master data:

  • Building

  • Unit

  • Unit Description

    This field is not required. However, if you are automatically creating assets when you import these unit records, Oracle recommends populating this field, as the value in this field is used to populate the Asset Description field. If you automatically create assets for the units you are importing, and this field is not populated, the system populates the Asset Description field with Unit NNNN, where NNNN is the unit number.

Area Master Required Fields

These are the required fields for importing area master data:

  • Building

  • Unit

  • Area Type must be populated with a valid value from UDC table 15/AR.

  • Area Level must be populated with a valid value from UDC table 15/AL.

  • Units (Indicating the amount of area in the unit.)

  • UM (Indicating the unit of measure of the area.)

Lease Master Required Fields

These are the required fields for importing lease master data:

  • Tenant

  • Lease Begin Date

  • Lease End Date (unless it is an open ended lease)

  • Lease Manager (if required by the processing options.

  • Lease Classification

    If you are importing lessor leases, set this field to blank as it has no impact on lessor leases. If you are importing lessee leases, assign one of the following valid values:

    • Blank: Not on balance sheet

    • 1: Operating lease

    • 2: Finance lease

  • Borrowing Rate (Required for lessee leases only.)

Lease Detail Required Fields

These are the required fields for importing lease detail data:

  • Lease Number or Old Lease Number

  • Building

  • Unit Number

    This field is required for lessor leases. If you are importing lessee leases, this field is required for property assets. Lessee lease detail lines must have either a Unit Number or an Asset Number.

  • Asset Number

    This field is not required for lessor leases. If you are importing lessee leases, this field is required for non-property assets. Lessee lease detail lines must have either a Unit Number or an Asset Number.

  • Lease Classification

    If you are importing lessor leases, set this field to blank as it has no impact on lessor leases. If you are importing lessee leases, assign one of the following valid values:

    • Blank: Not on balance sheet

    • 1: Operating lease

    • 2: Finance lease

Manual Billing Required Fields

Note:

This inbound processor is intended to be used only for importing initial lessee lease billing information, which is used to create amortization schedules.

These are the required fields for importing manual billing data:

  • Lease Number (or Old Lease Number)

  • Generation Type must be set to 7.

  • Building

  • Bill Code

  • Batch Number

    A valid batch must exist in the F0011 table and be posted. Be aware that the system uses the batch number that you enter in combination with the batch type value you specify in the processing options to validate that a batch exists.

  • Invoice Date

  • Suffix (Pay Item)

  • Document Number (Invoice/Voucher Number)

    The Document Number must exist in the F03B11 table for lessor leases, or the F0411 table for lessee leases, and must exist within batch.

  • Unit Number

    This field is required for lessor leases. If you are importing lessee leases, this field is required for property assets. Manual billing records associated with lessee lease detail lines must have either a Unit Number or an Asset Number.

  • Asset Number

    This field is not required for lessor leases. If you are importing lessee leases, this field is required for non-property assets. Manual billing records associated with lessee lease detail lines must have either a Unit Number or an Asset Number.

  • Gross Amount or Taxable Amount (for domestic transactions)

  • Currency Amount or Foreign Taxable Amount (for foreign transactions)

  • Effect on ROUA

    If you are importing lessor leases, set this field to blank as it has no impact on lessor leases. If you are importing lessee leases, assign one of the following valid values:

    • Blank: No

    • 1: Lease Incentive

    • 2: Initial Direct Cost

    • 3: Lease Payment

Recurring Billing Required Fields

These are the required fields for importing recurring billing data:

  • Lease Number (or Old Lease Number)

  • Bill Code

  • Billing Frequency

  • Line Number

  • Starting Date (When the Effect on Lease Liability field is set to 1 (Yes) or 2 (Guaranteed Residual Value)

  • Ending Date (When the Effect on Lease Liability field is set to 1 (Yes) or 2 (Guaranteed Residual Value)

  • Gross Amount, Taxable Amount, or Annual Rate Per Square Foot

  • Building

  • Unit Number

    This field is required for lessor leases. If you are importing lessee leases, this field is required for property assets. Recurring billing records associated with lessee lease detail lines must have either a Unit Number or an Asset Number.

  • Asset Number

    This field is not required for lessor leases. If you are importing lessee leases, this field is required for non-property assets. Recurring billing records associated with lessee lease detail lines must have either a Unit Number or an Asset Number.

  • Effect on Lease Liability

    If you are importing lessor leases, set this field to blank as it has no impact on lessor leases. If you are importing lessee leases, assign one of the following valid values:

    • Blank: No

    • 1: Yes

    • 2: Guaranteed Residual Value

Asset Master Required Fields

Note:

This section describes the fields that are required for the Asset Master Inbound Processor program (R1201Z1I). This program is not a Real Estate Management program, however, for the purposes of importing asset leases, the fields listed in this section are required.

For additional information about this program, see Processing Interoperability for Fixed Assets.

  • User ID

  • Batch Number

  • Transaction Number

  • Line Number

  • Direction indicator must be set to 1

  • Transaction Type must equal JDEFA

  • Transaction Action must equal A

  • Company

  • Business Unit

  • Asset Description

28.3 Importing Data into the Real Estate Management System

This section discusses the process for importing real estate management data after you have created your flat files and updated the flat file cross reference.

The process is the same for all of the different types of real estate management data. You should fully process one type of data before processing the next type. For example, you should complete the data import process for unit master data before you begin processing area master data.

  1. From the Inbound Flat File Conversions menu (G153141), run one of these versions of the Inbound Flat File Conversion program (R47002C):

    • Inbound Bill Code File Conversion (XJDE0051)

    • Inbound Unit Master File Conversion (XJDE0056)

    • Inbound Area Master File Conversion (XJDE0050)

    • Inbound Lease Master File Conversion (XJDE0052)

    • Inbound Lease Detail File Conversion (XJDE0053)

    • Inbound Recurring Billing File Conversion (XJDE0055)

    • Inbound Manual Billing File Conversion (XJDE0054)

  2. From the Review Unedited Transactions menu (G153142), select one of these options to review the data in the associated Z table:

    • Review Unedited Bill Code Transactions (P1512Z1)

    • Review Unedited Unit Master Transactions (P1507Z1)

    • Review Unedited Area Master Transactions (P1514Z1)

    • Review Unedited Lease Master Transactions (P1501BZ1)

    • Review Unedited Lease Master Detail Transactions (P15017Z1)

    • Review Unedited Recurring Billing Transactions (P1502BZ1)

    • Review Unedited Manual Billing Transactions (P1511BZ1)

  3. On the Work With Unedited Transactions form, use the radio buttons in the Transactions Displayed section to specify which type of records you want to review.

  4. To review and update data, select the row and then click Select. Review and update data as necessary, and then click OK to return to the Work With Unedited Transactions form.

  5. Select the row you want to process, and then select Inbound Processor from the Row menu to move the data from the Z table to the EnterpriseOne table.

    Alternatively, you can select one of these options from the Inbound Processors menu (G153143):

    • Inbound Bill Code Processor (R1512Z1I)

    • Inbound Unit Master Processor (R1507Z1I)

    • Inbound Area Master Processor (R1514Z1I)

    • Inbound Lease Master Processor (R1501BZ1I)

    • Inbound Lease Detail Processor (R15017Z1I)

    • Inbound Recurring Billing Processor (R1502BZ1I)

    • Inbound Manual Billing Processor (R1511BZ1I)

  6. When the inbound processor finishes processing, you can perform a new search to identify any unsuccessfully processed records to ensure that your batch processed successfully.

    Be aware that you can set up the inbound processor programs to automatically purge successfully processed records, so when you search over the records, successfully processed records might not display, as they might already have been purged. If you have unsuccessfully processed records, review the errors in the work center, and then complete steps 4 and 5 again until the data is successfully processed.