Documente Academic
Documente Profesional
Documente Cultură
Contents
Closed Enhancement Requests....................................................................................................................... 1
8.1.1 SP5 Closed Enhancement Requests................................................................................................... 2
Fixed Limitations ........................................................................................................................................... 2
8.1.1 SP5 Fixed Limitations ....................................................................................................................... 2
8.1.1 SP4 Fixed Limitations ....................................................................................................................... 2
8.1.1 SP3 Fixed Limitations ....................................................................................................................... 3
8.1.1 SP1 Fixed Limitations ....................................................................................................................... 3
8.1.1 Fixed Limitations............................................................................................................................... 3
8.1 Fixed Limitations.................................................................................................................................. 4
8.0 Fixed Limitations.................................................................................................................................. 4
Third-Party Limitations .................................................................................................................................. 5
Known Limitations......................................................................................................................................... 6
PowerCenter Connect for SAP NetWeaver mySAP Option....................................................................... 7
PowerCenter Connect for SAP NetWeaver BW Option........................................................................... 13
Installation .................................................................................................................................................... 14
Upgrading..................................................................................................................................................... 15
Contact Information...................................................................................................................................... 15
This document contains important information about installation, fixed limitations, and known limitations
for PowerCenter Connect for SAP NetWeaver. Do not upgrade to this release from a previous version
without carefully reading the relevant sections on upgrading and bug fixes, since bug fixes may change the
behavior of existing sessions. For more information about the product, consult the manual and online help.
You can get updated release notes at http://my.informatica.com/.
Description
134819
Integration Service passes values to the SNDPRN port in the SAP/ALE IDoc Prepare transformation.
Fixed Limitations
This section describes fixed limitations for PowerCenter Connect for SAP NetWeaver.
Description
177648
BCI_Scheduling_Target does receive data when extracting data in full update mode from SAP ECC 6.0.
177415
177252
176485
ABAP session with multiple Application Source Qualifiers fails on PowerCenter 64-bit.
176351
BAPI/RFC session with partitioning fails if the mapping includes multiple Joiner transformations.
175849
SAP function does not appear in the Application Source Qualifier after you check out a mapping.
175678
The Integration Service truncates target data of the datatypes CURR and QUAN in a business content
integration session.
106229
/INFATRAN/ZINFABCI causes ABAP program to crash when you define PowerCenter as a logical
system in SAP ECC 6.0.
Description
136962
Stream-mode sessions only run on the Central Instance on an SAP system with load balancing.
Description
134557
The Designer cannot create a business content integration mapping for DataSources with fields that
start with a slash (/).
132813
Session fails if the Integration Service does not pass data to the SAP/ALE IDoc Prepare transformation.
Description
127617
Import SAP Metadata dialog box does not show type B entries.
127342
Domain Name for DI Service and Data Integration Service Name properties for configuring an
InfoPackage should be optional.
127140
Data overflow error occurs when the Integration Service passes a negative decimal value to an
SAP/ALE IDoc Prepare transformation.
108860
Error occurs when installing an ABAP program for a mapping with a shortcut to an SAP source, and the
Order By option is set to 1 or more.
Description
106819
Outbound IDoc sessions fail when an IDoc segment contains the character /.
106429
Designer shuts down with unexpected condition when you generate an SAP RFC/BAPI mapping from a
UNICODE SAP system using the function BAPI_BUPA_FS_CREATE_FROM_DATA2.
105437
Metadata is omitted from the mapping when you connect to a SAP ECC 6.0 Unicode system to create
an RFC/BAPI mapping.
103926
Session with an SAP/ALE IDoc Interpreter transformation fails when the transformation tries to process
multi-segments IDocs.
103749
The Integration Service writes NULL values for invalid characters in the NUMC field in an SAP R/3
source.
97404
Session to read data from an SAP R/3 source may fail to extract all data from an SAP hierarchy.
Description
101776
RFC/BAPI session fails if the RFC/BAPI function call generates a NOT_FOUND exception.
98374
Data overflow error occurs when running an RFC/BAPI session in high precision mode if the function
input data contains a decimal point or a negative sign.
98032
Session to read data from an SAP R/3 source may fail to extract all data from an SAP hierarchy.
96011
Integration Service cannot call an RFC/BAPI function from a Unicode SAP system.
91307
Designer crashes when you edit an SAP/ALE IDoc Interpreter or SAP/ALE IDoc Prepare transformation
containing Japanese metadata.
89516
Designer shuts down unexpectedly when you edit the Properties tab of an Application Source Qualifier
transformation for an ABAP mapping.
87564
Description
92026
91562
91317
Generate Mapping for BCI Wizard incorrectly formats data extraction parameters entered in Selection
Criteria area.
91235
After upgrade of 6.0 RFC/BAPI mappings, PowerCenter Server does not recognize port names.
91138
91132
91131
See 91132.
91127
IDoc parent segment number does not match child segment number.
91109
SAP/ALE IDoc Prepare and SAP DMI Prepare transformations may fail to prepare IDoc data that
contains a high number of duplicate rows.
91033
Cannot enter a mapping variable for all segment values in an SAP/ALE IDoc Prepare transformation.
91016
SAP/ALE IDoc Interpreter, SAP/ALE IDoc Prepare, and SAP DMI Prepare transformations cannot
contain SAP metadata with special characters / and _.
90544
IDoc session with an IDoc_Writer AEP transformation fails when upgrading from PowerCenter Connect
for SAP R/3 6.2.
90542
90355
ABAP program may not create the staging file in UTF-8 mode for Unicode SAP systems.
90334
RFC/BAPI function mappings cannot contain SAP metadata with special characters.
90075
See 90334.
89619
See 90334.
87814
PowerCenter does not support converting the SAP datatype TIMS to String.
86643
See 90542.
86553
See 90542.
86445
See 90544.
86214
PowerCenter workflows cannot load data of the SAP BW datatype FLTP into BW.
84512
See 91033.
83862
See 91033.
83666
See 91562.
83248
See 91235.
83203
Generate SAP RFC/BAPI Mapping Wizard generates mappings using MS1252 code page only.
83105
PowerCenter does not support converting the SAP datatype ACCP to String.
82483
See 91109.
81913
See 91016.
81679
See 91127.
81084
See 91132.
80928
See 91132.
80174
See 91016.
79410
See 91317.
76942
75939
See 91138.
72745
See 76942.
Third-Party Limitations
You may encounter the following limitations when using PowerCenter Connect for SAP NetWeaver 8.1.1
SP5. If you encounter difficulties or have further questions regarding these limitations, contact Informatica
Global Customer Support.
5
CR 169350: Error occurs on ECC 5.0 when you use logical systems that you created before
you applied the SAP BW patches
When you use logical systems that you created before you applied patch level 20 (SAPKW35020) to write
inbound IDocs, the following message appears in transaction WE02:
Incomplete control parameter for communication with the BW system.
Workaround: Create a logical system after you apply the SAP BW patches and reactivate the DataSource.
CR 106900: IDoc session with partitioning fails to connect to SAP on 32-bit Solaris
An IDoc session with partitioning fails to connect to SAP on 32-bit Solaris when there is in sufficient
memory. The following message appears:
Message = Open file 'saprfc.ini' failed: 'Too many open files'
Known Limitations
You may encounter the following limitations when using PowerCenter Connect for SAP NetWeaver 8.1.1
SP5. If you encounter difficulties or have further questions regarding these limitations, contact Informatica
Global Customer Support.
CR 104055: PowerCenter transport log displays a warning when you install transports on
SAP ECC 6.0
When you import transports on SAP ECC 6.0, the transport log displays the following error message:
Enhancement Category for include or subtype missing
Workaround: Set the enhancement category for the table in SAP system ECC 6.0.
To set the enhancement category in the SAP system:
1.
From the transaction SE11, type the table name and click display.
2.
3.
4.
CR 102105: Error message while installing the ZINFABC run-time transport on SAP version
4.6C
When you install the ZINFABC run-time transport on SAP version 4.6C, the SAP system displays the
following error message:
Key field STRF2 has num type INT4. Buffering not possible, transport
restricted.
Workaround: When you use the SAP system to reinstall the transports, select Import Transport Request
Again from the Options tab in the Import Transport Request dialog box.
CR 101168: ABAP program name generated for an upgraded ABAP mapping does not use
the namespace prefix
When you want to use a namespace prefix for an existing ABAP program generated with an earlier version
of PowerCenter Connect for SAP NetWeaver, you uninstall the existing ABAP program from all the SAP
systems where it was installed. Then, you install the program again using a namespace prefix in the
program name. However, the installed ABAP program does not use the namespace prefix.
Workaround: After uninstalling the ABAP program, close and then reopen the Generate and Install dialog
box. Then install the program again using the namespace prefix.
CR 97868, 12125: ABAP Program Flow dialog box displays an empty Error Message dialog
box when validating a join condition
If you are joining multiple SAP R/3 sources in the Application Source Qualifier, and you validate a join
condition in the ABAP Program Flow dialog box that includes a space between the operator and the
column name, the ABAP Program Flow dialog box displays an empty Error Message dialog box.
Workaround: Remove the space between the operator and the column name.
CR 94964: Integration Service may display an incorrect error message for an outbound
IDoc session that receives duplicate parent rows or orphan rows
If you set the error threshold for an outbound IDoc session to a positive number, and you set the Duplicate
Parent Row Handling and Orphan Row Handling session properties to Error, the Integration Service fails
the session when the error count exceeds the error threshold. The session log displays the following
incorrect error message:
ERROR [22050] in processing Eof for input group 0
The Integration Service should display one of the following error messages:
IDOC_17748 The SAP/ALE IDoc Interpreter transformation received orphan
row <index of the row> in group <group> with primary key <primary key>.
IDOC_17749 <Value> duplicate rows were received by the SAP/ALE IDoc
Interpreter transformation.
CR 90620: Business content integration processing session should not select Extended
Syntax Check session property
When you create a business content integration processing session, the Workflow Manager selects the
Extended Syntax Check session property by default. However, the processing session does not process
invalid outbound IDocs. You can ignore this property.
CR 88130: Incomplete session log for a session containing an SAP/ALE IDoc Prepare or
SAP DMI Prepare transformation when the cache size is more than the available RAM
If a session contains an SAP/ALE IDoc Prepare or SAP DMI Prepare transformation, and the cache size is
more than the available RAM for the system, the Integration Service fails the session and displays the
following messages in the session log:
***********
FATAL ERROR : Failed to allocate memory (out of virtual memory).
***********
***********
FATAL ERROR : Aborting the DTM process due to memory allocation failure.
***********
The log does not explain why the Integration Service failed to allocate memory.
Workaround: In the session properties, decrease the cache size.
CR 78145: Session fails for a mapping with DMI and Sequence Generator transformations
When you run a session for a mapping with a DMI transformation and a Sequence Generator
transformation to populate the DOCNUM column, the session fails and the log file is incomplete.
CR 77325: Designer generates an unexpected condition when the Generate Mapping for
BCI Wizard is open for several minutes
When you leave the Generate Mapping for BCI Wizard open for several minutes, the Designer generates an
unexpected condition.
CR 71098: Integration Service does not display a message when it reaches the Idle Time
session condition during a session to read outbound IDocs using ALE
When you run a session to read outbound IDocs using ALE, and the Integration Service reaches the Idle
Time session condition, the Integration Service does not write the following message to the session log:
17654 "Reader termination condition reached: Packet Count: <packet
count>, Time elapsed: <number> secs. Reader shutting down.
CR 68134: Changing mapping parameters and variables in a mapping with an SAP R/3
source definition in a production environment is not allowed
If a mapping with an SAP R/3 source definition contains mapping parameters and variables in a production
environment, you cannot change the mapping parameters and variables. When you change mapping
parameters and variables, you must regenerate the ABAP program. You cannot regenerate an ABAP
program in a production environment.
CR 65746: Designer does not export the ABAP program for a mapping with versioning
from the Repository > Export Objects menu option
When you export a mapping with versioning that has an ABAP program to XML, the mapping does not
export the ABAP program when you select the mapping and click Repository > Export Objects.
Workaround: Select the mapping. Click Versioning > View History. From the View History dialog box,
click Tools > Export to XML File.
CR 60714: SAP function in an Application Source Qualifier does not refresh properly when
you undo a checkout for a mapping
An SAP function in an Application Source Qualifier for an SAP R/3 source definition does not display
properly under the following conditions:
y You check in a mapping with a function in the Application Source Qualifier.
y You check the mapping out to modify the mapping.
y You undo the checkout.
After you undo the checkout, the function displays on the Properties tab of the Edit Transformations dialog
box of the Application Source Qualifier. However, when you open the ABAP program flow, the function
does not appear. Although the function does not appear, it is not deleted.
Workaround: Close the repository folder. Reopen the repository folder. The function now displays in the
program flow.
CR 57412: ABAP program installation fails for mapping with an SAP R/3 static IDoc source
definition that is a shortcut
When you generate and install an ABAP program for a mapping with an SAP R/3 static IDoc source
definition that is a shortcut, the program installation fails.
Workaround: Remove the shortcuts to the source definition and Application Source Qualifier from the
mapping. In the Source Analyzer, rename the source definition to remove Shortcut_to_ from the name.
Add the renamed source definition to the mapping. Validate the mapping. Generate and install the ABAP
program.
CR 48586: ABAP program installation succeeds for repository folders with read-only
permissions
If a repository folder is read-only, users can successfully generate and install ABAP programs. This should
not occur.
CR 46625: ABAP program fails to install when a static filter condition in the Source
Qualifier is longer than 72 characters
When you enter a static filter condition in a Source Qualifier for an SAP R/3 source in a mapping, and
generate and install an ABAP program for the mapping, the ABAP program installation fails with the
following message:
The file format is incorrect for file <ABAP program filename>. The line
length should not exceed 72 characters.
Program installation for mapping <mapping name> failed.
Workaround: Generate the ABAP program to a local file. Open the file and modify the program to split the
filter condition into multiple rows. Install the program from the modified file.
10
CR 44864: Session reading from an SAP R/3 source does not fail when error threshold is 1
When you run a session with an SAP R/3 source definition in the mapping, and the error threshold is 1, the
session continues to run after reaching the error threshold.
CR 43659: ABAP program fails to install when PowerCenter repository object names
contain SAP reserved words
The ABAP program fails to install on SAP R/3 when PowerCenter repository object names (repository,
folder, or mapping name) contain SAP reserved words like REPORT.
Workaround: Do not name the PowerCenter repository and repository objects with SAP reserved words.
CR 41212: Zero rows extracted when time is not specified for partition based on date field
When you define a partition based on a date field and you do not specify the complete date for the partition,
the Integration Service does not extract any rows for that partition. For example, you have two partitions
based on key EKKO.BEDAT (date field). You define the first partition as 01/18/1896, 01/18/2001, and the
second partition as 01/18/2001, <blank>. When you run the workflow, the Integration Service does not
extract any rows for the second partition.
Workaround: Specify complete date including hours, minutes, and seconds for the partition.
CR 41115: Cannot import a parameter defined with the keyword TYPE for ABAP and
RFC/BAPI mappings
You cannot import a parameter defined with the keyword TYPE for ABAP and RFC/BAPI mappings.
CR 40899: ABAP code generation fails when you use mapplet variables in the program
flow
You create a mapplet and define mapplet variables in the Designer. Create a mapping with this mapplet and
use the mapplet variables in a static filter, dynamic filter, or code-block in the program flow. When you
generate the ABAP program, the code generation fails with an error. This is because the mapplet variables
are not defined in the ABAP program.
CR 38155: Outbound IDoc session in debug mode might hang when you stop the session
before the Integration Service meets session conditions
You execute a debug session for an outbound IDoc mapping that contains session conditions. You then stop
the session before the Integration Service meets the session conditions. The session might hang.
Workaround: Manually abort the session.
CR 37840: Designer might crash when SAP function definition is deleted in the repository
You import an SAP function in the Designer to use in an R/3 mapping. You project the output of the
function parameters from the Application Source Qualifier for the R/3 source. You then delete the SAP
function from the PowerCenter repository. You invoke the program flow dialog box, save the mapping, and
try to generate/install the ABAP program. The Designer might crash.
CR 37414: Integration Service may not write data to relational target when function call
fails in an RFC/BAPI function mapping
You create an RFC/BAPI function mapping to process data in SAP R/3 and write function output to a
relational target. If the function call fails, the Integration Service may not write data returned from previous
function calls to the relational target.
11
CR 37405: Integration Service does not guarantee writing output of multiple RFC/BAPI
functions to targets in a mapping if one function call fails
When using multiple RFC/BAPI functions in the same mapping, if any function call fails, only output data
from the previous function calls for that function are guaranteed to be loaded to the flat file targets.
Previous output data for the other function calls are not guaranteed to be loaded to their targets.
CR 34200: Designer does not guarantee valid metadata import when you import function
signatures with parameter TYPE from SAP R/3
When you import function signatures to use in R/3 mappings that contain the parameter TYPE, the
Designer does not guarantee the validity of the metadata import.
CR 33723: ABAP code generation fails when you use an IDoc source and an EDIDC or
EDIDD table source in the same mapping
You create an SAP R/3 mapping with an IDoc source and an EDIDC or EDIDD table source. When you
generate the ABAP program, the code generation fails.
Workaround: Edit the ABAP code to remove the duplicate declaration of the EDIDC or EDIDD table in the
generated code.
CR 30620: Session produces values from a previous record when ABAP program uses
outer join syntax with a nested loop
When you run a session for a mapping with an SAP R/3 source definition, and the ABAP program uses
outer join syntax with a nested loop, the Integration Service may add values to a record, which are part of
the previous record.
CR 28987: Integration Service does not expand SY variables in function calls
You cannot use RFC/BAPI or custom functions with scalar input parameters that have SY structure fields
with default values such as SY-DATUM in an R/3 mapping.
Workaround: You need to supply the value for the scalar input parameters when you use the RFC function
in the mapping. The values you supply for the scalar input parameters must have valid datatype, precision,
and scale.
CR 28091: No support for TIMS data in the form 240000
When the Integration Service reads TIMS data in the form 240000 from SAP R/3, it produces a data
conversion error.
Workaround: Edit the Application Source Qualifier to change the TIMS datatype to String. Add an
Expression transformation after the Application Source Qualifier to change the value 240000 to 000000.
CR 17485: The Designer does not return an error message when you create output ports
from fields in different table parameters in an SAP function
If you create output ports from fields in a table parameter after you have already created output ports from a
different table parameter and closed the ABAP program flow dialog box, the Designer does not return an
error message when you validate the ABAP program flow. You should only create output ports from fields
in the same table parameter. The SAP function that contains the table parameter should be the last object in
the program flow.
Workaround: Do not create output ports from fields in different table parameters.
12
CR 17395: Workflow fails with data conversion error when datatype length and initial
values for ABAP type variables are different
You create ABAP type variables in the Designer to use in an R/3 mapping. You enter initial values for the
variables that do not conform to the datatype precision and scale for that variable. When you run a
workflow with this mapping, the workflow fails with data conversion error.
Workaround: Make sure the initial value you use for an ABAP type variable conforms to the datatype
precision and scale for that ABAP type variable.
CR 15528: Session fails when you compare a decimal mapping variable to a DEC column
in a dynamic filter condition
Sessions fail if you compare a decimal mapping variable to a DEC datatype column in a dynamic filter
condition.
Workaround: Use the same condition in a static filter.
CR 13344: Session fails when you use Exec SQL to extract a table that contains a forward
slash (/)
When you import an SAP source table that contains a forward slash (/) in the table or column name, the
Designer generates the ABAP program with a forward slash. If you install the ABAP program using Exec
SQL, the Integration Service returns an error when you run a session using the ABAP program.
Workaround: Generate the ABAP program locally and add delimiters around the table or column names
before you install. See your database documentation for valid delimiters.
13
an Oracle database. The MgrName field has a fixed-width of 45 characters. You want to filter data from the
MgrName field according to the following condition:
MgrName = BAILEY
Since the MgrName field in the source system has a fixed-width, any record shorter than 45 characters is
appended with trailing blanks to fit the field length. As a result, when you run the session, the value
BAILEY in the filter condition does not match any value in the MgrName field.
Workaround: Include an Expression transformation in the mapping to trim the trailing blank characters
from the values in a specified source field. Then, use a Filter transformation to select the data to load into
BW.
CR 44819: Incorrect query generated when filter condition has no values
PowerCenter generates an incorrect query when you add filter conditions to a mapping without specifying
the values for the filter.
Workaround: Specify values when adding filter conditions or remove the filter conditions from the
mapping.
CR 40862: The BW writer does not include threshold support
In the session properties, when you enable the Stop On Errors option on the Error Handling settings of the
Config Object tab, the Integration Service does not maintain a count of errors that occur while writing to a
BW target. When you load data into BW, the writer errors are not included in the error count. For example,
you set the Stop On Errors option to three for a session loading data into BW. The session fails only if three
errors occur before the data reaches the BW writer.
Installation
Setting the SIDE_INFO and RFC_INI Environment Variables
Effective in PowerCenter 8.1.1, you no longer need to register the SIDE_INFO and RFC_INI environment
variables before installing PowerCenter.
Renaming the sideinfo and saprfc.ini Files
If you are installing PowerCenter for the first time on Windows, you need to rename the sideinfo.infa_811
and saprfc.ini.infa_811 connection files. If you are upgrading from a previous version, and you want to
overwrite the existing sideinfo and saprfc.ini files, you need to rename the connection files. For more
information, see the PowerCenter Connect for SAP NetWeaver User Guide.
Installing on HP-UX 11i
Install the most recent patch bundle for your operating system. If you are running HP-UX 11i, the patches
you installed must include PHSS_26560.
SAP System Requirements
For PowerCenter installations on 64-bit Linux, the SAP systems to which PowerCenter communicates must
have SAP kernel 6.40. For more information, see SAP Note 803429.
To use PowerCenter Connect for SAP NetWeaver mySAP Option business content integration, you must
have installed the SAP plug-in version 2003_1 or later.
If you install the Informatica transports on an SAP system earlier than version 4.6C, use the transaction
SE80 to verify that the transport process activated all objects. If any objects are not active, use the
transaction SE80 to activate them. Or use transaction SE37 to activate function modules and transaction
SE38 to activate programs.
14
Upgrading
This section contains information about upgrading to PowerCenter Connect for SAP NetWeaver mySAP
Option 8.1.1 SP5.
Validating 6.x inbound IDoc mappings
If you export an inbound IDoc mapping from PowerCenter 6.x and then import it into an 8.1.1 SP5
repository, the mapping loses all links between transformations and becomes invalid. To use a 6.x inbound
IDoc mapping, link the ports and then validate the mapping.
Enabling recovery for a 7.x business content integration listener workflow
When you upgrade from PowerCenter Connect for SAP R/3 7.x and you set the Recovery Strategy session
property to Resume from Last Checkpoint for a business content integration listener workflow, the
Workflow Manager invalidates the session. To enable recovery for the listener workflow, import and use
the listener workflow included in the 8.1.1 SP5 BCI_Mappings.xml file located in the
/sapsolutions/mySAP/BCI directory. Do not configure scheduling.
Contact Information
North America / South America
Asia / Australia
Informatica Corporation
Headquarters
100 Cardinal Way
Redwood City, California
94063
United States
Toll Free
+1 877 463 2435
Toll Free
00 800 4632 4357
Toll Free
Australia: 1 800 151 830
Singapore: 001 800 4632 4357
Standard Rate
Brazil: +55 11 3523 7761
Mexico: +52 55 1168 9763
United States: 650 385 5800
Standard Rate
Belgium: +32 15 281 702
France: +33 1 41 38 92 26
Germany: +49 1805 702 702
Netherlands: +31 306 022 797
United Kingdom: +44 1628 511 445
Standard Rate
India: +91 80 4112 5738
15