CRM_WEBREQ_CUST - Request Category Customizing and Associated Views
The following messages are stored in message class CRM_WEBREQ_CUST: Request Category Customizing and Associated Views.
It is part of development package CRM_SERVICE_WEBREQUEST_CUST in software component CRM-ISE-WBF. This development package consists of objects that can be grouped under "Customizing of Web Forms (Request Categories)".
It is part of development package CRM_SERVICE_WEBREQUEST_CUST in software component CRM-ISE-WBF. This development package consists of objects that can be grouped under "Customizing of Web Forms (Request Categories)".
Message Nr ▲ | Message Text |
---|---|
000 | * Messages when maintaining request categories |
001 | Transaction type &1 is already used in request category &2 |
002 | Request category cannot be used without request data structure |
003 | Product assignment could not be read for request category &1 |
005 | Usage "&1" is already set in view &2 |
006 | Several products are assigned to request category &1 |
007 | Caution: Changing the transaction type makes Web requests inaccessible |
008 | Error occurred when saving objects in Web Form Framework |
009 | Save before going to product maintenance |
010 | Still no BSP application or initial page assigned |
011 | First enter a BSP application and an initial page |
012 | BSP application &1 and initial page &2 could not be assigned |
013 | Save before the test |
014 | You must enter a BSP application and an initial page |
015 | No implementation available for request category &1 |
016 | Error occurred during generation of BSP application |
017 | Error occurred during copying of objects |
018 | Error occurred when deleting objects of the Web Form Framework |
019 | XML data is incorrect and cannot be read |
020 | * Messages for importing Customizing data for Web Service Request |
021 | Request category &1 does not exist |
022 | No text types found for request category &1 |
023 | No views defined for request category &1 |
024 | Transaction type &1 is not assigned to a request category |
025 | No request categories found |
026 | No processor view defined for request category &1 for entry date &2 |
027 | Enter a request category |
028 | No Web form framework service data for request category &1 |
029 | Save before generation |
030 | No valid view &3 defined for request category &1 for date &2 |
031 | No valid view exists for request category &1 for creation date &2 |
032 | No authorization for the valid views of request category &1 |
033 | Request category group &1 does not exist |
034 | View &1 determined by business add-in is not valid; standard view is used |
035 | No transaction types found |
036 | View &2 for request category &1 not found |
040 | * Additional messages Customizing request category |
041 | BSP application &2 generated successfully with initial page &3 |
042 | Generation of BSP application not possible for view &1 |
043 | Creation of views not possible for request category &1 |
044 | BSP appplication &1 does not exist |
045 | Generation did not occur, or only partially occurred due to user action |
046 | Active request categories may not be determined in the past |
047 | Active request categories may not be determined in the past |
048 | Error occurred when locking objects for request category &1; display only |
049 | Active request category is restricted; select a relevant start date |
050 | Error during transport connection for dependent obj.; transport not pos. |
051 | Error during transport connection for dependent obj.; transport not pos. |
052 | Code & from code group & and ctlg & cannot be selected for trans type & |
053 | Code & from code group & and catalog & entered are not permitted |
054 | Start page &2 does not exist in BSP application &1 |
060 | * Messages Customizing ADOBE |
061 | Form &1, interface &2, and Web Dynpro appl.&3 could not be assigned |
062 | You must enter a form and an interface |
063 | ADOBE processing not available in this system |
064 | Form &1 does not exist |
065 | Form interface &1 does not exist |
066 | Form &1 is not applicable with interface &2 |
067 | Web Dynpro application &1 does not exist |
068 | Form &1 and form interface &2 do not match |
069 | Another form interface is assigned to form &1 |
070 | Form is not filled |
071 | Form, interface, and Web Dynpro application must be filled |
072 | No Web Dynpro application assigned |
100 | *** Messages relating to the migration of WFF from UWS/UXP *** |
101 | Service &1 is already available in the UWS/UXP display |
102 | Service &1 converted to UWS/UXP display |
103 | Conversion of metadata from WFF to UWS/UXP; date: &1 |
104 | Log file unuseable; see long text or select a different file |
105 | OPEN error CONVT_CODEPAGE_INIT occurred for log file specified |
106 | No request categories (services) to be converted to UWS/UXP display |
107 | Test run: &1 request categories to be converted |
108 | &1 request categories (services) successfully converted |
109 | &1 request categories (services) converted incorrectly |
110 | Enter a valid log file for the conversion update run |
111 | Update run: &1 request categories to be converted |
112 | &1 request categories (services) not converted due to serious error |
113 | Conversion of BSP link IDs for request categories; date: &1 |
116 | Error when reading links; document &1 not converted |
117 | Test run: &1 documents to be converted |
118 | &1 documents successfully converted |
119 | &1 documents converted incorrectly |
120 | Update run: &1 documents to be converted |
121 | &1 documents not converted due to serious error |
122 | No documents to be converted to UWS/UXP namespace |
123 | Enter a value for the commit counter |
124 | &1 documents not to be converted since they are not linked to an order |
130 | Migration of link type for Web requests; date: &1 |
131 | Test run: &1 links to be migrated |
132 | &1 links have been migrated successully |
133 | &1 links have been migrated with errors |
134 | Production run: &1 links were to be migrated |
135 | No links to be migrated |
136 | Enter a value for creation date |
137 | No requests in system |
899 | Report has been deactivated; contact SAP to reactivate it |