Incorrect format when printing lists

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

Symptom
The system uses an incorrect format when printing ABAP lists:
In the print dialog, the system proposes a format for an output device, which is not defined for the relevant device type.In the background, the system generates a spool request that cannot be printed because the format is not defined for the relevant device type. [...]

SP_CALL_GET returns incorrect values when called second time

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

Symptom
If you call SP_CALL_GET twice in succession, the second time it is called, a leading zero is truncated in the return parameter CALLSTATE-PARTY.
For example:
After the first call of the parameter SP_CALL_GET, the return parameter CALLSTATE-PARTY has the value ‘00123456789′. After the second call, it has the value ‘0123456789′.
Other terms
SP_REMOTE_PARTY_IDENTIFY, Snapware, IDENTIFY_PARTY,
Remove leading zero
Reason [...]

Where-used list incorrect after renaming methods

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

Symptom
The navigation index is incorrect after you rename methods.
The system does not find the new method in the where-used list.
Other terms
Where-used list, renaming methods, refactoring
Reason and Prerequisites
This error occurs only if you first insert and then inactively save the new method name for the usage locations, and you then rename the method itself.
Solution
Implement the [...]

TROYMICR: Incorrect print output with 701/711/720 kernel

[] [] [] [] []

Symptom
When printing with device type TROYMICR, the printer commands for the printer initialization are not sent correctly and thus check printing with the Troy printer fails.
Other terms
TROYMICR
Reason and Prerequisites
This is a bug in the SAP kernel which has the following effect:
In device type TROYMICR, format LETTER, action SETUP, the INCLUDE command to device [...]

NR: Number from incorrect year is used

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

Symptom
You create an interval in a year-dependent number range, and an interval for a later year already existed before. For the interval that already existed before, a buffer was created in the main memory because numbers were already used from the interval. If a number from the newly created interval is [...]

BWA 7.00: Incorrect result for some FEMS queries

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

Symptom
You encounter incorrect results for a BW query using FEMS logic
Other terms
BIA, BWA, Accelerator, wrong data, different result
Reason and Prerequisites
Prerequisites:
SAP NetWeaver BW Accelerator Revision 51 or previousThe index for the F-table is not splitThe BWA OLAP index is located on a different TREX index server than the F-table indexYou are running a query that uses [...]

BWA 7.00: Incorrect result for some FEMS queries

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

Symptom
You encounter incorrect results for a BW query using FEMS logic
Other terms
BIA, BWA, Accelerator, wrong data, different result
Reason and Prerequisites
Prerequisites:
SAP NetWeaver BW Accelerator Revision 51 or previousThe index for the F-table is not splitThe BWA OLAP index is located on a different TREX index server than the F-table indexYou are running a query that uses [...]

Developer traces analysis in MMC Snap-In is incorrect

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

Symptom
For “All Tasks -> Analyse Developer traces…”, SAP MMC Snap-In terminates at system node level or returns incorrect results.
Other terms
Microsoft Management Console, MMC, SAP Developer Network, SDN
Reason and Prerequisites
This is due to a program error in the SAP MMC Snap-In.
Solution
The error in the SAP MMC Snap-In is corrected as of Release 7.11 patch [...]

Next Page »