Symptom
The ABAP GCP is implemented using ESF LCP. Due to this implementation many ECO functionalities are not working correctly. e.g. in some cases the messages were not displayed properly.
So a new implementation of the ABAP GCP using ESF RCP is provided.
It is possible to configure GCP to work either using LCP or using RCP. [...]
Symptom
If you process a QuickView in basis mode, various errors may occur:
List fields are displayed several times.Deleted list fields reappear in the display list.Selected list fields reappear in the field pool.The dump MESSAGE_TYPE_X occurs in the form SYNCHRONISE_LISTFIELDS_FROM_TC.
Reason and Prerequisites
This problem is caused by a program error.
Solution
Implement the correction instructions using the Note Assistant or [...]
Symptom
You use the LSMW main program /SAPDMC/SAP_LSMW_INTERFACE for the periodic scheduling of LSMW runs in the background. If you let a very large number of jobs run in parallel, you notice performance problems due to work processes that are waiting. In the overview of the database locks, you find [...]
Symptom
The system calls the function module GET_PRINT_PARAMETERS incorrectly in the following situation:
If NO_DIALOG = SPACE, MODE = BATCH, and ARCHIVE_REPORT = report, the system does not copy the transferred report to the archive parameter.
Other terms
ABAP, lists, print lists
GET_ARCHIVE_PARAMETERS, GET_ARCHIVE_PARAMS_NODIALOG
ArchiveLink, archive run, SARA
Background processing, job
Reason and Prerequisites
This problem is due to a program error.
Solution
Import the [...]
Symptom
While upgrading, during after import processing for BRFplus, the check for application name might return error messages of the following kind:
Invalid or no namespace in application name: &1SAP object &1 cannot be assigned to package &2
These messages should only be warnings during the after import processing.
Other terms
CL_FDT_APPLICATION, CHECK_NAME, FDT, BRFplus, FDT_AFTER_IMPORT, FDT_CORE212, TO142
Reason and [...]
Symptom
WS Security has the following processing issues:
1) Timestamps in the wsse:Security header containig milliseconds are sporadically rejected due to rounding errors.
2) Secure Conversation fails sporadically, as the system could not connect to shared memory in a timely fashon.
3) Unsufficient error messages, when signature verification failed.
4) X.509 XML Signature: In addition to a BinarySecurityToken, a [...]