Basis Errors and Solutions

SOAP fault after RABAX has an incorrect syntax

July 7, 2009 at 2:39 am

[incorrect] [incorrect close] [incorrect version] [login incorrect]

1. BWA 7.00: Incorrect result if query runs during commitSymptom You obtain incorrect query results but if you execute the query again the result is correct. Other terms BIA, BWA, Accelerator, wrong result, different, rollup, commit, changerun Reason and Prerequisites Prerequisites:...
2. NR: Number from incorrect year is usedSymptom 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...
3. Where-used list incorrect after renaming methodsSymptom 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...
4. Incorrect R3 user and Default receiver for pager.Symptom Pager data not being updated correctly in certain Data Exchange scenarios. Other terms BAS_COMMUNICATION, PAGER, TELEPHONE, SMS ENABLED, ADR2, ADR13, ADDR_COMM_MAINTAIN, ADDR_COMM_MAINTAIN_INTERNAL, COMMSYNC_SYNCHRONIZE_SMS_PAGER, LSZA0F65, LSZA0F76 Reason and Prerequisites When an user...
5. WDA: DateNavigator returns incorrect valuesSymptom The DateNavigator user interface (UI) element returns incorrect data. Year, month, and day are swapped. Reason and Prerequisites This problem is caused by a programming error. This occurs in Release 7.01,...
6. SP_CALL_GET returns incorrect values when called second timeSymptom 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...
7. ST02/ST03N: Values displayed in incorrect columnsSymptom 1. In transaction ST02, the system displays the value for the maximum heap memory consumption in the column “In Mem [KB]” instead of in the column “MaxUse [KB]“. 2. In the...
8. DOKIL / DOKHL / DOKTL: Incorrect usage – Primary indexSymptom The primary index incorrectly uses the following tables: DOKILDOKHLDOKTL Other terms SE61, F1 help, message long text, F1 documentation Reason and Prerequisites The primary index for these tables consists of the...

Symptom

After a RABAX (short dump) occurs in the provider when a Web service is called, a (Simple Object Access Protocol) SOAP fault is triggered after an error page that is stored in the ICF node “/sap/bc/srt”. In this process, an incorrect fault code is created, which may result in XML parsing errors for some third-party products. In the following, first the correct and then the incorrect fragment for the fault code is listed:
soap:Server
soap:Server

Solution

Implement Note 1272381, and follow the instructions in that note to correct the following text:
Text type “Long text”, concept “A69F3BE81C85914B9B4CFDBB3D8DBEE6″

Permalink