APOC_OR_MESSAGES - Messages for Output Control
The following messages are stored in message class APOC_OR_MESSAGES: Messages for Output Control.
It is part of development package APOC_OUTPUT_CONTROL_IMPL in software component CA-GTF-OC. This development package consists of objects that can be grouped under "Application Output Control - Implementation Objects".
It is part of development package APOC_OUTPUT_CONTROL_IMPL in software component CA-GTF-OC. This development package consists of objects that can be grouped under "Application Output Control - Implementation Objects".
Message Nr ▲ | Message Text |
|---|---|
| 000 | *** Messages for ROOT |
| 001 | No output parameters could be determined for document &1. |
| 002 | Mandatory action parameter &1 missing. |
| 003 | Application object type is not valid. |
| 004 | Application object type must not be initial. |
| 005 | Output type is not valid. |
| 006 | Output type must not be initial. |
| 007 | Application object ID cannot be changed for saved documents. |
| 008 | Action parameters contain invalid application object type and/or ID. |
| 009 | Application log handle must not be initial. |
| 010 | Application object ID contains invalid characters. |
| 011 | Output request cannot be created as application object &1 is not active. |
| 012 | Application log of output request &1 &2 with handle &3 does not exist. |
| 013 | OR root &1 has an item &2 with different log_handle |
| 014 | &1 is not a valid view because it has no fields. |
| 015 | There is no entity assigned to view &1. |
| 050 | *** Generics and common messages |
| 051 | &1&2&3&4 |
| 052 | No logical system for client &1 has been maintained. |
| 053 | You are not authorized to perform this action. |
| 054 | You are not authorized to view the data (receiver is blocked). |
| 100 | *** Messages for ITEM |
| 101 | Output channel can't be initial. |
| 102 | Sender information is missing (&1). |
| 103 | Action &1 is not available for the current item status &2. |
| 104 | No output data available for saving. |
| 105 | Email address &1 is not valid. |
| 106 | Cancellation of XI message &1 failed. |
| 107 | Item is not relevant for output. |
| 108 | Print queue name can't be initial. |
| 109 | No sender data found. |
| 110 | Recipient can't be initial. |
| 111 | Form template name can't be initial. |
| 112 | Form language can't be initial. |
| 113 | Form country/region can't be initial. |
| 114 | Sender country/region can't be initial. |
| 115 | Type of organization must be specified. |
| 116 | Type of organizational unit must be specified. |
| 117 | Print queue &1 is not valid. |
| 118 | Sender email address can't be initial. |
| 119 | Sender organization type is not valid. |
| 120 | Sender organization unit type is not valid. |
| 121 | Form rendering was stopped due to the following messages: |
| 122 | Output channel &1 is not supported. |
| 123 | Dispatch time can't be initial. |
| 124 | No output device has been set. |
| 125 | An error occured when converting spool request to PDF (error code &1). |
| 126 | Output device &1 is not valid. |
| 127 | You are not authorized to use output device &1. |
| 129 | Form template name &1 is not valid. |
| 130 | The printer &1 is with a PDL type &2 that cannot be used. |
| 131 | Spool request could not be created. |
| 132 | Output data could not be written to spool request. |
| 133 | Error(s) occurred when confirming the spool request. |
| 134 | There is no field &1 in structure APOC_S_OR_ITEM that can be changed. |
| 135 | No Form Service is available. |
| 136 | An error occured while processing XML output. |
| 137 | Email body is empty for Output Request Item &1. |
| 138 | No email recipient has been maintained. |
| 139 | Modification of Output Request Item &1 of &2 &3 failed. |
| 140 | Conversion error: number of copies &1 cannot be handled. |
| 141 | PDF could not be created from spool. |
| 142 | No OR item found for BO of node &2 and key &1 . |
| 143 | The number of copies must not be negative or zero. |
| 144 | Please fill in an email template. |
| 145 | Spool request could not be found. |
| 146 | Device type could not be found. |
| 147 | Action &1 is not available for channel &2 and item status &3. |
| 148 | Email template &1 is not valid. |
| 149 | Action "&1" is not available for channel "&2". |
| 150 | Completed output items without a stored document cannot be previewed. |
| 151 | Completed output items without a stored document cannot be duplicated. |
| 152 | The selected output device &1 does not support PDF files. |
| 153 | The number of copies must not exceed &1 for sender country/region &2. |
| 154 | NrOf email recipients must not exceed &1 for sender country/region &2. |
| 155 | Format (&1) of selected print queue doesn't match format of document (&2) |
| 156 | Please deselect the PDF attachments which are not supported by the spool. |
| 157 | Error(s) occurred when protecting PDF. |
| 158 | Output item &1 contains an empty email recipient address. |
| 159 | Rendering runtime (in micro seconds): &1 |
| 160 | Rendering runtime for duplicate (in micro seconds): &1 |
| 161 | Runtime for Channel &1 processing (in micro seconds): &2 |
| 162 | Item has been set from Status '&1' to Status '&2'. |
| 163 | Item could not be changed from Status '&1' to Status '&2'. |
| 164 | Only up to &1 document instances are supported in one render request. |
| 165 | Multi document instances exist: Duplicate handling is not supported. |
| 166 | User &1 downloaded form data XML of the business document &2 at &3 &4. |
| 167 | The download of form data XML of the business document &1 failed. |
| 168 | Action &1 is only available for node item |
| 169 | Print queue &1 of item &2 is not valid. |
| 170 | Output device &1 of item &2 is not valid. |
| 171 | The status of print queue item &1 in queue &2 changed from "&3" to "&4". |
| 172 | Multiple documents are to be rendered: Only PDF print queues can be used. |
| 173 | Item &1: No new attachments allowed in status '&2'. |
| 174 | Item &1: No attachments allowed for empty channel. |
| 175 | Item &1: No attachments allowed for channel '&2'. |
| 176 | Item &1: No attachments allowed for empty print queue. |
| 177 | Item &1: No attachments allowed as print queue '&2' does not support PDF. |
| 178 | Calling document rendering service &1. |
| 179 | Document rendering via service &1 successfully finished. |
| 180 | Document rendering via service &1 failed. |
| 181 | Item &1: No valid attachments apply. |
| 200 | *** Messages for BRFplus |
| 201 | BRFplus application not found. |
| 202 | BRFplus metadata not found. |
| 203 | Output types could not be determined. |
| 204 | Recipients could not be determined. |
| 205 | Output channel could not be determined. |
| 206 | Print queue parameters could not be determined. |
| 207 | Email parameters could not be determined. |
| 208 | Form template could not be determined. |
| 209 | The following BRFplus exception occurred: &1. |
| 210 | No data found for recipient with role &1. |
| 211 | Output item &1 may not use channel &2. |
| 212 | As a resend of item &3, item &1 cannot use channel &2. |
| 213 | XML file uploaded for application &1. |
| 214 | No XML file found for application &1. |
| 215 | Error during XML import of application &1: &2. |
| 250 | *** General Messages |
| 251 | No application metadata found for application type &1 and output type &2. |
| 252 | Callback to application failed. |
| 253 | A technical error occurred when saving the output document. |
| 254 | Output data could not be removed from content repository. |
| 255 | A technical error occurred when saving the output document to DMS. |
| 256 | The action could not be performed due to errors. |
| 257 | The form services cannot be instantiated. |
| 258 | No key was provided while saving the rendered PDF to the storage system. |
| 259 | The action &1 could not be performed on item &2. |
| 260 | No output possible for output item &1 due to inconsistencies. |
| 300 | *** Form Master Determination |
| 301 | Company ID &1 does not exist. |
| 302 | Organisation unit &1 does not exist. |
| 303 | ISO Country code &1 does not exist. |
| 304 | Form template &1 does not exist. |
| 305 | Form master template cannot be determined. |
| 306 | No Data Provider for Form Template &1 |
| 307 | Watermark text for master form template &1 not available. |
| 350 | *** Application Log |
| 351 | Start processing of output for user &1 at &2 &3 (&4). |
| 352 | Error(s) occurred when checking the output item. |
| 353 | Error(s) occurred when changing the status of the output item. |
| 354 | Error(s) occurred when rendering the output item. |
| 355 | Error(s) occurred when saving the document to KPRO. |
| 356 | Error(s) occurred when creating the print queue item. |
| 357 | Error(s) occurred when loading the document from KPRO. |
| 358 | A technical error occured when creating the email. |
| 359 | A technical error occured when sending the email. |
| 360 | A technical error occured when updating the output items. |
| 361 | Output item &1 has been successfully forwarded to output channel &2. |
| 362 | Processing of output item &1 with ID &2. |
| 363 | Processing of output item with technical ID &1 using channel &2. |
| 364 | Form rendering was stopped intentionally by the application. |
| 365 | There are detailed messages available. |
| 366 | Messages have been generated during form rendering. |
| 367 | Error(s) occurred when deleting the print queue item. |
| 368 | No output data available. |
| 369 | The following message was generated when sending the email to &1. |
| 370 | Processing triggered via background RFC queue &1. |
| 371 | Could not lock all output request items. |
| 372 | Unable to find output request(s). |
| 373 | Unable to find output request item email node(s). |
| 374 | Unable to update output request item(s). |
| 375 | Unable to set status of output request item(s) to 'Pending'. |
| 376 | Unable to set status of output request item(s) to 'Completed'. |
| 377 | Error(s) occurred while saving output request(s). |
| 378 | A technical error has occured. |
| 379 | Legacy form rendering failed for OR item &1 of Application Doc &2 &3. |
| 380 | KPro Document of Appl. Doc. &1 ID &2 for OR Item &3 could not be deleted. |
| 381 | Print Queue Item Appl. Doc. &1 ID &2 for OR Item &3 could not be deleted. |
| 382 | Printing method &1 of output item &2 is unknown. |
| 383 | A technical error occured when attaching files to email. |
| 384 | Messages have been generated when loading attachments. |
| 385 | One or more attachments no longer available, please check selected ones. |
| 386 | Attachment &1 is being used for output. Deletion not allowed. |
| 387 | Application Log of context &1 could not be saved. |
| 388 | Start of resending for output items |
| 389 | Start of preparing items to be output |
| 390 | The saved document is not a PDF file. Display is not possible. |
| 391 | The item &1 has been added to bundle &2. |
| 392 | The bundle &1 could not be opened. |
| 393 | The item &1 could not be added to the bundle &2. |
| 394 | The bundle &1 was sent using channel PRINT. |
| 395 | The bundle &1 has failed using channel PRINT. |
| 396 | The watermark &1 in language &2 is not available. |
| 397 | Error(s) occurred when merging the document. The return code is &1. |
| 398 | Output item &1 &2 got ignored, because it has been output already. |
| 399 | Output item &1 &2 got ignored, because it has not been scheduled. |
| 400 | A technical error has occured for &1 ('&2'). Please retry. |
| 401 | A technical error occured while calling B2B integration services. |
| 402 | No outbound service interface assigned to output type &1. |
| 403 | A technical error occured while calling B2B integration services. |
| 404 | No active outbound service could be found. |
| 405 | Multiple active outbound services were found, but only one is expected. |
| 406 | Error(s) occurred when sending the outbound message via CA &1. |
| 407 | No communication arrangement could be found for business partner &1. |
| 408 | Multiple communication arrangements found for business partner &1. |
| 409 | Outbound service &1 is not valid for appl. object &2 and output type &3. |
| 410 | No B2B integration services are available |
| 450 | *** Legacy Frameworks |
| 451 | Print program cannot be found. |
| 452 | *** Generic Sorting *** |
| 453 | Sorting could not be applied due to technical error. |
| 463 | Application Object Type does not match Sorting Variant |
| 464 | Creation of result table for sorting failed |
| 470 | &1 Start: &2 |
| 471 | &1 Finish: &2 |
| 472 | Document Rendering |
| 473 | Output To Channel |
| 474 | Duplicate Rendering |
| 500 | *** Output Channels *** |
| 501 | The selected IDoc version is not supported. |
| 550 | *** Bundling *** |
| 551 | Output items in a bundle should all have the same print queue name. |
| 552 | Output items in a bundle should all have "PRINT" as output channel. |
| 553 | Output items in a bundle should all have "1" as number of copies. |
| 554 | Error(s) occurred when creating the bundle print item. |
| 555 | Invalid bundle description. |
| 556 | Bundle has not been opened |
| 557 | Print bundling is only supported for print queues with format PDF |
| 558 | Print bundling is not supported for sender country/region &1. |
| 600 | *** Attachments *** |
| 601 | New attachments can not be merged with a duplicated item. |
| 602 | Attachments for duplicate PDF are for internal usage and can't be merged. |
| 603 | The selected channel &1 support PDF files only. |
| 604 | Required parameter &1 is initial. |
| 605 | No document types found for Appl. Object Type &1 and Output Type &2. |
| 650 | *** Key user messages *** |
| 651 | Application document read attempt by &1 at &2 &3 (&4). |
| 652 | Read attempt of Appl. Doc. &1 ID &2 for OR Item &3 in UI. |
| 653 | Document has been read successfully. |
| 654 | Document read attempt failed due to missing authorization. |
| 655 | Document read attempt failed due to rendering errors. |