Archive for June, 2009

MDI: Method getDescription for data elements terminates

[] [] [] [] [] [] [] [] []

Symptom
Calling the MDI method getDescription() for a data element leads to a NullPointerException.
You receive the following stack traces:
java.lang.NullPointerException at com.sap.mdi.ddtypes.DDDataelement.getDescription(
DDDataelement.java:305)
at com.sap.dictionary.types.mdi.util.TextServices.getDescription(
TextServices.java:165)
or
com.sap.dictionary.types.mdi.util.TextServices.getQuickInfo(
DdDataType.java:219)
or the following SAP Java Connector (JCo) exception:
com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE:
The function module “DD_DTEL_GET” cannot be used for ‘remote’ calls.
In addition, the method getReptext() may also be affected.
Other terms
MetaDataInterface, DDDataelement, Dictionary metadata, getDescription
Reason and Prerequisites
A [...]

Message Overview: redirect to Message Monitoring fails

[] [] [] [] [] [] [] [] [] [] [] []

Symptom
You click on one of the counters in the Message Overview, that shows the number of Messages of a certain scenario and in a certain status. A new window opens that should redirect to Message Monitoring to display the single Messages for the selected counter. Instead of loading the correct page, [...]

Monitored Services do not appear in Monitoring Service/CCMS

[] [] [] [] [] [] [] [] []

Symptom
The Adapter Engine can report the backlog for XI Messages to the Java Monitoring service of the WebAS Java and from there to CCMS. The Monitoring is configured at Service level (header attribute of XI Messages) and can be switched on or off for each Sender and Reciever Service separately. This [...]

ldap_rfc patch level is not output in trace

[] [] [] [] []

Symptom
The current patch level is not apparent in the trace of ldap_rfc. In addition, the trace of ldap_rfc specifies an incorrect release in Releases 701, 711, and 720.
Other terms
LDAP
Reason and Prerequisites
This problem is caused by a program error.
Solution
Install an ldap_rfc whose patch level corresponds to at least the patch level specified on the “SP [...]

Split mapping: Dump SYSTEM_NO_ROLL with many sub-messages

[] [] [] [] [] [] [] [] []

Symptom
You have defined a split mapping for which many messages are created as a result of the mapping. During the processing, the system generates the dump SYSTEM_NO_ROLL, which shows that the main memory is insufficient.
Other terms
Interface collection, MMF, split mapping, trace
Reason and Prerequisites
This is caused by an error in the source code.
Solution
Implement the [...]

Possible loss of data for certain conversions

[] [] [] [] [] [] []

Symptom
Two transparent tables with the following properties are converted one after the other in the same work process:
The tables have names with a length of more than 13 characters.The table names are the same for the first 13 characters.Both tables have the same number of columns.
According to the conversion log, the conversions are successful. [...]

BWA 7.00: Incorrect data for attribute types DATE and TIME

[] [] [] [] [] [] [] [] [] [] [] [] []

Symptom
You receive incorrect data for queries where the F-table has attributes of type DATE or TIME. You find the following entry in the trace of TREXIndexServer: “Attribute engine function not implemented (index attribute flags ) getAggregateMeasures”
Other terms
BWA, BIA, Accelerator, wrong result, date, time, not implemented
Reason and Prerequisites
Prerequisite: SAP NetWeaver [...]

Termination stating that keyword CALL SYSTEM is deactivated

[] [] [] [] [] [] []

Symptom
The activation of an instance profile terminates with a short dump
stating that the keyword CALL SYSTEM is deactivated.
Other terms
Profile maintenance, RZ10
Reason and Prerequisites
You use a UNIX server and have set the profile parameter CALL_SYSTEM to 0.
The check of the shared memory parameter via the program sappfpar executes a CALL ‘SYSTEM’ call.
Solution
Implement the note or import [...]

Next Page »