=====================================================================
1: INSTALLATION NOTES
=====================================================================
DataStage products include a simple installation program. Procedures
differ slightly based upon the product being installed and the
platform being used. However, specific instructions in the
installation program lead you through the details of the
installation.
NOTE Before installing a DataStage product, close any other
programs that may be running on your computer. Having other
programs running may cause installation errors.
UNICODE STATEMENT
-----------------
This release of the IBM WebSphere DataStage Pack for SAP R/3 is
designed to communicate with both SAP R/3 Unicode systems and SAP R/3
non-Unicode systems with respect to both inbound and outbound calls
for single-byte and multi-byte data.
INSTALLATION PREREQUISITES
--------------------------
DataStage Product Requirements
----------------------------------------
A full installation of the following valid products is required.
o IBM WebSphere DataStage Pack for SAP R/3
o IBM WebSphere DataStage version 7.5.2 with NLS installed
The IBM WebSphere DataStage Pack for SAP R/3 supports:
o Operating Systems:
- Microsoft Windows 2000 Service Pack 4
- Microsoft Windows Server 2003 Service Pack 1 (Standard, Enterprise)
DataStage Server only. Pack does not support DataStage Enterprise
Edition on Microsoft Windows platforms.
o DataStage version 7.5.2 with NLS installed
o SAP R/3 4.6C, R/3 Enterprise (Unicode), mySAP ERP ECC version
5.0 (Web AS 6.4) and ECC version 6.0 (Web AS 7.0)
Note: The IBM WebSphere DataStage Pack for SAP R/3 no longer supports
SAP R/3 versions 4.6B and 4.0B.
=====================================================================
2: UPGRADING FROM AN EARLIER VERSION
=====================================================================
An upgrade from an earlier release of the Pack is supported but in
certain situations the metadata may need to be refreshed. For example,
when upgrading your jobs from a non-Unicode SAP system to a Unicode SAP
system, you will need to refresh the metadata by selecting the
components (ABAP tables, IDocs or BAPIs) from the new SAP system.
=====================================================================
3: NEW OR CHANGED BEHAVIOR
=====================================================================
Support for all DataStage platforms.
Full Unicode support is included in this version of the IBM WebSphere
DataStage Pack for SAP R/3. The Pack has been tested to work for all
supported SAP versions, including both non-Unicode and Unicode SAP
versions.
In addition to adding Unicode support, other issues found in version
5.2 have been addressed in this release.
=====================================================================
4: KNOWN ISSUES
=====================================================================
The Pack plug-ins have not been optimized for parallel processing.
The following is a list of known issues that exist for this release:
PX Environment
------------------
All plug-in components may be freely used in the Enterprise (PX)
environment. The functionality is the same as the traditional
DataStage server environment, except as described below.
IMPORTANT!
The exception is the ability to launch IDoc extract jobs
automatically after a specified IDoc threshold is reached. This
feature of the IDoc Extract plug-in component is NOT available if the
plug-in is used in the PX (Enterprise) environment. Please configure
all IDoc Extract jobs to be scheduled and run directly via the
DataStage Director.
ecase 89923 Numeric SQL type on PX canvas may need to be set to
VarChar. If the SQL type is set as Numeric this results
in a date output of " 19960205." The date should be
"19960205", without the leading space and trailing '.'.
Changing the SQL type to VarChar results in the correct
format.
ABAP Extract
------------
ecase 18940 Generated ABAP program not inserted in the SAP
repository.
IDoc Extract
------------
ecase 66869 Unable to set "Automatic Cleanup and Archiving of IDoc
Files" option on DataStage Administrator for SAP.
Workaround: The PATH variable in the DataStage Windows
Server environment needs to be modified to put the MKS
Tool Kit path after the Windows path:
1. Right-click "My Computer" and select "Properties".
2. Click the "Advanced" tab.
3. Click "Environment Variables".
4. Select the "Path" variable from the System Variables
section.
5. Click "Edit".
6. Cut the MKS Tool Kit path from the beginning of the
entry, C:\PROGRA~1\MKSTOO~1\mksnt;
and paste it at the end of the path.
7. Click OK in three separate windows and reboot the
machine.
All Components
--------------
This issue is generic and applies to all the components contained
in this release:
ecase 71193/39547 For additional information on IDOC and BAPI
authorizations and profiles contact your BASIS
administrator.
=====================================================================
5: LEGAL NOTICES
=====================================================================