SAC_TOOLS - Message Class for ABAP Channels tools
The following messages are stored in message class SAC_TOOLS: Message Class for ABAP Channels tools.
It is part of development package SAC_TOOLS in software component BC-MID-AC. This development package consists of objects that can be grouped under "ABAP Channels tools, e.g. logging, tracing, etc.".
It is part of development package SAC_TOOLS in software component BC-MID-AC. This development package consists of objects that can be grouped under "ABAP Channels tools, e.g. logging, tracing, etc.".
Message Nr ▲ | Message Text |
---|---|
000 | Background &1, job count &2, scheduled successfully |
001 | Exception '&1' caught for function module '&2' |
002 | Background job currently running with program '&1' |
003 | RC '&1' for FM '&2' received from background job '&3'(job count '&4') |
004 | Please check the entered timestamp |
005 | Entered APC application ID "&1" does not exist. |
006 | No data found |
007 | No authorization to read stat. data records of other users |
008 | No authorization to start transaction '&1'. |
009 | No authorization to start function module '&1'. |
010 | &1 &2 &3 &4 |
011 | No authorization to start program '&1'. |
012 | Function module '&1' not found. |
013 | Authority check for execution of transaction '&1' has failed. |
014 | Transaction '&1' not found. |
015 | Transaction '&1' is an area menu. (Analysis is not possible) |
016 | Program '&1' not found. |
017 | Current setting for stat profile parameters could not be saved. |
018 | Current setting for stat profile parameters could not be changed. |
019 | User '&1' has no authorization to read stat profile parameters. |
020 | &1&2&3&4 |
021 | Scenario has to be recorded first. |
022 | Scenario has been recorded successfully. |
023 | No data found. |
024 | Input field for object name is initial! |
025 | Pattern is initial. |
026 | EPP Root Context ID coud not be reset. |
027 | Start wirh 'Preparation' phase to have complete data records. |
028 | Input fields for date/time and backwards time must not be initial. |
029 | Select one line from output result. |
030 | Multi selection is not supported. |
031 | Navigation not possible for selected APC application. |
032 | No authorization to schedule ABAP channels reorganisation batchjob. |
033 | Rejected lock object is &1. Conflict with user &2 detected |
034 | System failure occurred while accessing enqueue service |
035 | Detach Client scenario has been detected. Output list is incomplete! |
036 | Required reset action has failed for servers: |
037 | Selected Root Context ID must not be initial! |
038 | No inconsistency found |
039 | No log found in the database |
040 | Wait for 5 seconds to collect statistic records completly |
041 | Output list can be incomplete! For more detail see long text. |
042 | Use RFC type "Client" for Navigation to calling point. |
043 | Use HTTP type "Client" for Navigation to calling point. |
044 | Use APC type "Client" for Navigation to calling point. |
045 | Navigation to calling port not possible. |
046 | No authorization to read "ABAP Daemon" log entries |
047 | Process Chain data will be collected |
048 | Process Chain Reconstruction is not supported for "Event" Subrecords |
049 | Process Chain Reconstruction is not supported for "Batch" Subrecords |
050 | Process Chain Reconstruction is not supported for "Update" Subrecords |
100 | Function call was successfully. |
101 | Internal error: An invalid parameter was passed when calling a function. |
102 | Internal error in APC kernel |
103 | Internal error: Memory could not be allocated. |
104 | Incoming path was not found in the stored data of application. |
105 | Template not found when trying to parse and send an error message. |
106 | Internal error: handle for this APC session was not found. |
107 | Internal error: Informations for this APC connection could not be found. |
108 | Message too big, can not be sent. |
109 | Sending an error page was not allowed in this system. |
110 | |
201 | Taskhandler returned error when trying to get the outgoing buffer. |
202 | Taskhandler returned error when trying to set application data. |
203 | Taskhandler returned error when trying to get application data. |
204 | Taskhandler returned error when trying to get the incoming buffer. |
205 | The connection was closed. |
206 | |
300 | ICT layer returned error when trying to create a message. |
301 | ICT layer returned error when trying to initialize a message. |
302 | ICT layer returned error when processing data. |
303 | ICT layer returned connection closed. |