Supplement for J.D. Edwards SAP BusinessObjects Data Services 4.1 Support Package 1 (14.1.1.

0)

2012-11-22

Copyright

2012 SAP AG. All rights reserved.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company. Crossgate, m@gic EDDY, B2B 360, B2B 360 Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. 2012-11-22

Contents

Chapter 1

Overview.................................................................................................................................5

Chapter 2

System requirements..............................................................................................................7 World.......................................................................................................................................7 OneWorld................................................................................................................................7 Datastores...............................................................................................................................9 Defining a J.D. Edwards World datastore.................................................................................9 ODBC driver............................................................................................................................9 Mainframe interfaces................................................................................................................9 Defining a J.D. Edwards OneWorld datastore........................................................................11 To define a J.D. Edwards OneWorld datastore.......................................................................11 Browsing and importing metadata..........................................................................................13 To browse and import the metadata.......................................................................................13 Extracting data from J.D. Edwards systems...........................................................................14 Reference information...........................................................................................................15 Data types.............................................................................................................................15 Translating decimals...............................................................................................................15 Translating dates....................................................................................................................16 Translating time......................................................................................................................16 Functions...............................................................................................................................17 JDE_Date..............................................................................................................................17 JDE_Time..............................................................................................................................18 19

2.1 2.2
Chapter 3

3.1 3.1.1 3.1.2 3.2 3.2.1 3.3 3.3.1 3.4

Chapter 4

4.1 4.1.1 4.1.2 4.1.3 4.2 4.2.1 4.2.2

Index

2012-11-22

Contents

2012-11-22

Overview

Overview

The SAP BusinessObjects Data Services J.D. Edwards (JDE) interface is a license-controlled feature. With this interface, you can use the Designer to: View modules and tables in a database instance under a specified J.D. Edwards environment Import metadata for tables into SAP BusinessObjects Data Services Create batch data flows that use J.D. Edwards tables as sources

Related Topics System requirements Datastores

2012-11-22

Overview

2012-11-22

System requirements

System requirements

The J.D. Edwards interface allows you to connect SAP BusinessObjects Data Services with two J.D. Edwards applications: World OneWorld

Both of these applications operate on an underlying database. Install the drivers you need to connect J.D. Edwards with SAP BusinessObjects Data Services on the same computers on which you install the Designer and Job Server components.

2.1 World
The J.D. Edwards interface supports World version A7.3 and later. SAP BusinessObjects Data Services only supports this application when World uses an underlying DB2 database on an AS/400 computer. Use either an ODBC datastore connection (using IBM's iSeries Access driver) or a Detail_DB2 datastore connection. Related Topics Defining a J.D. Edwards World datastore

2.2 OneWorld
The J.D. Edwards interface supports OneWorld version B7.3 and compatible versions, including Xe. SAP BusinessObjects Data Services supports this application if OneWorld uses one of three underlying databases: DB2 for AS/400 (use an ODBC datastore connection using IBM's iSeries Access) Microsoft SQL Server Oracle

2012-11-22

System requirements

J.D. Edwards OneWorld environment data sources include system-control data sources and business data sources. Your J.D. Edwards system-control data sources and your business data sources must reside on the same database instance. If a system control table is not located in the same database instance, you cannot create a datastore for that J.D. Edwards application. Related Topics Defining a J.D. Edwards OneWorld datastore

2012-11-22

Datastores

Datastores

SAP BusinessObjects Data Services uses datastore connections to link with other applications or databases. In a design environment, you use datastores to browse, search, or import metadata that represents external tables, files, messages, and other database objects. When running jobs, the software uses datastore information to move data between source and target databases and applications. After defining a J.D. Edwards datastore in SAP BusinessObjects Data Services, you can browse application modules, tables, table descriptions, and column descriptions. You must define J.D. Edwards datastore connections with accurate J.D. Edwards information to ensure the accessibility of the tables.

3.1 Defining a J.D. Edwards World datastore

You can use two methods to access the J.D. Edwards World application: ODBC driver Mainframe interfaces

Both options access a DB2 for AS/400 database.

3.1.1 ODBC driver

You can access the J.D. Edwards World application using an ODBC driver called iSeries Access. Before creating a datastore using this ODBC driver, you must install and configure the driver on the same computers on which you installed the Designer and Job Server components. Use the ODBC Administration utility to install and configure the driver. In the driver's library list, be sure to list all the libraries needed in your particular J.D. Edwards environment.

3.1.2 Mainframe interfaces

2012-11-22

Datastores

You can access the J.D. Edwards World application using Mainframe interfaces. Refer to the pertinent documentation for installation and setup instructions.

3.1.2.1 To define a J.D. Edwards World datastore

1. In the object library of the Designer, go to the Datastores tab. 2. Right-click inside the object library window and select New. 3. In the Datastore Editor window, enter a name for this datastore (DS_JDEWorld, for example). 4. In the Application type list, select JDE World. 5. In the Database Type list, select ODBC. 6. Enter the connection information. 7. Click the JDE World Properties tab and enter the required information. SAP BusinessObjects Data Services handles J.D. Edwards data in a logical grouping of libraries.
Option Description

Environment

Enter the J.D. Edwards application environment name. Enter the name of the library where SAP BusinessObjects Data Services can find the J.D. Edwards system control table F0005. Enter the name of the library where SAP BusinessObjects Data Services can find the J.D. Edwards data dictionary table F9201. Enter the name of the library where SAP BusinessObjects Data Services can find J.D. Edwards security tables, such as F0094.

Local library

Data dictionary library

Security library

8. Click OK. The J.D. Edwards datastore appears in the object library. Related Topics Reference Guide: Objects, Database datastores

10

2012-11-22

Datastores

3.2 Defining a J.D. Edwards OneWorld datastore

A J.D. Edwards environment uses a logical construct called a data source to associate the J.D. Edwards application layer data with the database layer data (for example, Microsoft SQL Server). J.D. Edwards uses some data sources to associate system-control data and uses other data sources to associate business data. The distributed nature of J.D. Edwards architecture allows an instance of J.D Edwards to have data sources on multiple database servers. For example, a finance data source can be on a Microsoft SQL Server while the system-control data source is on Oracle. Because a SAP BusinessObjects Data Services datastore can only be associated with one database server, you must follow these rules when defining a J.D. Edwards OneWorld datastore connection in SAP BusinessObjects Data Services: The data sources within a J.D. Edwards environment that you want to access must be in the same Microsoft SQL Server, DB2 for AS/400, or Oracle instance. You must specify required system control data sources, and in some cases, you must enter the owner ID of the data source. For Microsoft SQL Server, you must also enter the database name for each, and for DB2 for AS/400, you must enter the library for each. If using Microsoft SQL Server, you must configure a new datastore for each business data source on a unique database even if all databases are on the same Microsoft SQL Server. For example, if you want to extract Human Resource and Finance information from separate databases on the same Microsoft SQL Server instance, you must create two different datastores.

3.2.1 To define a J.D. Edwards OneWorld datastore

1. In the object library of the Designer, go to the Datastores tab. 2. Right-click inside the object library window and select New. 3. In the Datastore Editor window, enter a name for this datastore (DS_JDEOneWorld, for example). 4. In the Application Type list, select JDE_One_World. 5. In the Database Type list, select the database on which your J.D. Edwards application runs.

11

2012-11-22

Datastores

If you choose:

Do this: Enter the database-related information including the user name and password for the database. In the Database server name box, enter the name of the SQL Server instance. In the Database name box, enter the name of the database containing your business data, such as a finance database. If you have more than one database of business data create a separate J.D. Edwards datastore like the first except enter a different database name here. Note: With Microsoft SQL Server as your database, the Job Server must be installed on Windows NT or 2000.

Microsoft SQL Server

Oracle

Enter the information required to connect to the Oracle database.

6. Click the JDE OneWorld Properties tab and enter the required information: the environment name and the databases to which the data sources point. Some J.D. Edwards data sources contain system-control information. SAP BusinessObjects Data Services needs this system-control information to properly translate J.D. Edwards data. Like all data sources, these system-control data sources can be anywhere on the Microsoft SQL Server, DB2 for AS/400, or Oracle instance. Enter the database names for each data source. Option Environment Description Enter the J.D. Edwards application environment name. Enter the name of the database where the tables F986101, F98611, and F00941 are located. This option is available for DB2 and Microsoft SQL Server databases. Enter the owner ID for the system data source. System data source owner This option is available for Microsoft SQL Server and Oracle databases. Enter the name of the database where the tables F9860 and F9861 are located. Object librarian data source This option is available for DB2 and Microsoft SQL Server databases.

System data source

12

2012-11-22

Datastores

Option

Description Enter the name of the database where the table F0005 is located.

Local data source This option is available for DB2 and Microsoft SQL Server databases. Enter the name of the database where the table F9203 is located. Data dictionary data source This option is available for DB2 and Microsoft SQL Server databases.

7. Click OK. The J.D. Edwards OneWorld datastore appears in the object library.

3.3 Browsing and importing metadata

After creating a J.D. Edwards datastore, you can browse and import the metadata from the connected application.

3.3.1 To browse and import the metadata

1. View the modules in the J.D. Edwards application. You can: Right-click the datastore name and select Open Double-click the datastore name The workspace shows the list of application modules. 2. View the tables in a particular module. You can: Expand the module tree Double-click a module (folder) 3. To import table data, right-click a table name and select Import. Note: When you import a table into SAP Data Services via the J.D. Edwards interface, the software does not preserve the table hierarchy. All tables are listed at the same level. You can also import tables using the DesignerImport by Name and Search features.

13

2012-11-22

Datastores

3.4 Extracting data from J.D. Edwards systems

When extracting data from either J.D. Edwards application, SAP BusinessObjects Data Services processes and converts data types appropriately. For example, the software recognizes null values for date columns. J.D. Edwards, on the other hand, does not support null values. Instead, J.D. Edwards stores dates as numeric values. When date data is not present, J.D. Edwards stores the number 0. Therefore, the software automatically translates a value of zero for a date to NULL. If you expect a column to have zeros in it, do not use the date type in the primary key. SAP BusinessObjects Data Services automatically translates most data types. In some cases, you must translate output explicitly. Related Topics Data types

14

2012-11-22

Reference information

Reference information

4.1 Data types

SAP BusinessObjects Data Services uses unique processing to translate some J.D. Edwards data types: Translating decimals Translating dates Translating time

4.1.1 Translating decimals

J.D. Edwards translates decimal values using an additional piece of information from the underlying database: the decimal separator shift integer. This value indicates the number of digits to move left from the end of the value number. For example, to represent a number like 1.23, J.D. Edwards stores the value as "123" with a decimal separator shift of "2" (starting at the end of the number, the decimal shifts two places to the left). To process J.D. Edwards decimal values, the software extracts the numeric value stored in the underlying database and then applies the decimal separator shift to determine where the decimal belongs. The software applies the translation when a decimal column appears in a SQL statement against the database. SAP BusinessObjects Data Services interprets J.D. Edwards currency data types as decimals. The software does not automatically translate decimal data types in three cases: SQL transform sql function pushdown_sql function

In these cases, translate decimals explicitly. To translate decimals explicitly, you must know the decimal shift value for your selected column. Use the shift number to determine the denominator for decimal

15

2012-11-22

Reference information

translation. For example, if column COL26 in table JDETAB is a JDE decimal column and it has a shift value of 2, you would manually modify the SQL statement to say something like SELECT COL26/100 FROM JDETAB. The denominator in this statement has two zeros following the 1. If the shift value was 3, the statement would be SELECT COL26/1000 FROM JDETAB.

4.1.2 Translating dates

J.D. Edwards stores dates as numeric values. The J.D. Edwards date format is similar to Julian date format except the year starts with 1900. SAP BusinessObjects Data Services handles J.D. Edwards numeric values by reading the date information and translating with an internal formula based on the J.D. Edwards start year. For example, the software would handle the date February 18, 1999 as follows: Year = (1999 - 1900) * 1000; Day = 31 + 18; [31 is the # of days in January] The resulting Day value is the number of days since 1/1/1999. The Julian date value is Year + Day = 99049. Like decimal translation, there are three cases when the software does not automatically translate dates: SQL transform sql function pushdown_sql function

In these cases, you must use the JDE_Date function. See JDE_Date for details.

4.1.3 Translating time

SAP BusinessObjects Data Services does not automatically interpret J.D. Edwards time data types. If you need to translate a number to its time value, you can use the JDE_Time function. Related Topics JDE_Time

16

2012-11-22

Reference information

4.2 Functions
When conversion is not automatic, you can use SAP BusinessObjects Data Services functions to convert J.D. Edwards data to internal SAP BusinessObjects Data Services data types: JDE_Date JDE_Time

You can access these functions from the query editor: go to the Mapping or the Where tabs, and click the Functions button. Note: You cannot use the lookup function with a J. D. Edwards datastore. Use the lookup_ext function instead.

4.2.1 JDE_Date
Given a Julian date stored in a J.D. Edwards database, JDE_Date returns the equivalent value as a SAP BusinessObjects Data Services date data type. Syntax
JDE_Date(jde_julian_date)

Return Value date: The SAP BusinessObjects Data Services date data type equivalent to the specified Julian date. Where jde_julian_date : The integer column in the input table that contains a J.D. Edwards Julian date. Example:
Function Results

JDE_Date (99049)

2/18/1999

You can translate J.D. Edwards Julian dates using column mapping. When you input a J.D. Edwards Julian date number (for example, 99049), an SAP BusinessObjects Data Services date type results (for example, 2/18/1999). Enter the function in the Mapping section of the Query transform editor. Use this function when the software does not automatically translate dates.

17

2012-11-22

Reference information

Note: Because this function takes an integer as input, map the incoming column to an integer column before applying the function.

Related Topics Translating dates

4.2.2 JDE_Time
Given a number representing time in J.D. Edwards, JDE_Time returns an SAP BusinessObjects Data Services character value that represents the equivalent military time in HH24:MI:SS format (where HH is hours, MI is minutes, and SS is seconds). Syntax
JDE_Time(time_integer)

Return Value Char(8): The time in HH24: MI : SS format. Where time_integer : An integer column in the input table that represents a J.D. Edwards time. Example: Function JDE_Time(92513) Results 09:25:13

You can translate times from J.D. Edwards formatting into SAP BusinessObjects Data Services formatting using column mapping. For instance, if you input a J.D. Edwards record update time of 92513, the resulting SAP BusinessObjects Data Services time would be 9:25:13. Enter the function in the Mapping section of the Query transform editor.

18

2012-11-22

Index
B
business data sources 7 decimal values converting automatically 15 translating manually 15 defining datastores, J.D. Edwards OneWorld 11 datastores, J.D. Edwards World 10 metadata browsing 13 importing 13 Microsoft SQL Server connecting to, rules for 11 data sources, specifying 11 underlying database for J.D. Edwards 7

C
converting J.D. Edwards data currency 15 dates 16 decimals 15 overview 14 times 16 creating datastores, J.D. Edwards OneWorld 11 datastores, J.D. Edwards World 10 currency 15

F
functions, converting data 17

O
ODBC, accessing J.D. Edwards World with 9 OneWorld. See J.D. Edwards OneWorld 7 Oracle connecting to, rules for 11 data sources, specifying 11 underlying database for J.D. Edwards 7

I
IBM DB2. See DB2 7 importing metadata, J.D. Edwards 13 iSeries Access driver 9

D
data sources defined 11 rules for 11 specifying 11 data types, converting 15 datastores defining, J.D. Edwards OneWorld 11 defining, J.D. Edwards World 10 importing metadata 13 J.D. Edwards OneWorld 11 J.D. Edwards World, accessing 9, 10 date functions, JDE_Date 17 dates converting automatically 16 converting manually 16 converting, function for 17 translating missing values 14 DB2 accessing for J.D. Edwards World 9 connecting to, rules for 11 data sources, specifying 11 underlying database, using as 7

J
J.D. Edwards OneWorld data sources, specifying 11 datastores, defining 11 datastores, rules for 11 properties 11 system requirements 7 J.D. Edwards World accessing 9 datastores, defining 10 libraries, specifying 10 properties 10 system requirements 7 JDE_Date function 17 JDE_Time function 18

P
pushdown_sql function 15, 16

S
sql function 15, 16 SQL transform 15, 16 system control data sources 7

T
time functions 18 time values, converting 18

L
libraries, J.D. Edwards 10

W
World. See J.D. Edwards World 7

M
Mainframe interfaces DETAIL. See DETAIL 10

19

2012-11-22

Index

20

2012-11-22