Database Output

Database output is performed for every row of data that is processed in the detail section. All database operations occur on a record-by-record basis using the standard JDE Base middleware Application Programming Interfaces (APIs).

Defining database output involves defining the output and then overriding the environment, if appropriate. If no override is defined, the database output runs against the default data source.

When you design database mappings in batch applications, RDA determines where the system stores the flat files that are produced by the mapping. You can also define a default destination using the UBEDBOutputLocation setting in the UBE section of the jde.ini file. If no location is defined in RDA or in the jde.ini file, or if the location is invalid, the files are stored in the current working directory.

The first step in defining database output is to select an operation for mapping the targets:

• Insert only

  Can be used for tables, but is the only appropriate option for text files.

• Update

• Insert or update

• Delete

Next, you need to select the type of target that you are using:

• JD Edwards EnterpriseOne table.

• Comma-delimited text file.

• Fixed-record length text file.

You can suppress a defined database output:

• Override the database output in the version, and delete the mapping record to process the database output for a specific version of the report.

• Define the criteria using If statements and then using the Suppress Section Write system function to process the database output for specific rows of data.

  The Suppress Section Write system function suppresses not only printed output but also database mappings.

See also:

• "Designing Tables in JD Edwards EnterpriseOne", "Working with Table Input, Output" in the JD Edwards EnterpriseOne Tools Table Conversion Guide.