1. Real Estate Management Implementation Guide
  2. Understanding the Real Estate Management Data Import Process

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 Electornic Data Interchange 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 Electornic Data Interchange 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