APOC_OR_UI_MESSAGES -

The following messages are stored in message class APOC_OR_UI_MESSAGES: .
It is part of development package APOC_OUTPUT_CONTROL_UI in software component CA-GTF-OC. This development package consists of objects that can be grouped under "Application Output Control - UI Objects".
Message Nr
Message Text
000***General
001Output request can't be maintained in document creation screen
002Output request is not available for object "&1", with object key "&2"
003No issues found
004Output request item &1 is not available for object "&2", with key "&3"
050***Actions
052Error when loading PDF data
053Error when showing PDF data
200***WebDynpro
201No determinations (decision tables) were found
202Please select an application first.
203Refresh of Condition Parameters succeeded.
204Application not found in registry table.
205A technical error occured when reading the application.
206A technical error occured when reading the data structure.
207A technical error occured when creating the data structure instance.
208A technical error occured when reading the data structure instance.
209Data binding should only be refreshed when there were recent updates.
210Do you want to proceed and update data binding for CDS View &1?
211A technical error occured when reading the data type name.
212Condition Parameters of Application are technically bound to CDS view &1.
213CDS View &1 can be extended.
214CDS View &1 cannot be extended.
215The current version of determination step '&1' is not active (&2&3).
216Refresh of Condition Params rejected (as not yet possible for CDS views).
217No update possible as no customizing request for user &1 exists.
218Update recorded for customizing request &2 of user &1.
219No update possible as several customizing requests exist for user &1.
220Condition Parameters of Application are bound to structure &1.
221Refresh of Condition Parameters not supported.
300*** Fiori
301Output Item &1 - &2 was updated. Please execute the action again.
400App cannot be edited while a ZDM update is in progress. Plese try later.
Privacy Policy