SAP ABAP Message Class OPS_SE_GEN (Service enabling generic functionality)
Basic Data
Hierarchy
☛
SAP_APPL (Software Component) Logistics and Accounting
⤷ MM (Application Component) Materials Management
⤷ OPS_SE_COMMON_FUNCTIONALITIES (Package) Functions for Cross-Component Use
⤷ MM (Application Component) Materials Management
⤷ OPS_SE_COMMON_FUNCTIONALITIES (Package) Functions for Cross-Component Use
Attributes
Message class | OPS_SE_GEN | |
Short Description | Service enabling generic functionality | |
Changed On | 20110908 | |
Last Changed At | 171755 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | Importing parameter has incompatible type at message call &1 &2 | The short text describes the object sufficiently | |
2 | 001 | Importing parameter has incompatible type at message call &1 &2 | The short text describes the object sufficiently | |
3 | 002 | No result for test scenario &1. | The short text describes the object sufficiently | |
4 | 003 | Test scenario with message-id &1 finished successfully. | The short text describes the object sufficiently | |
5 | 004 | Test scenario with message-id &1 failed. | The short text describes the object sufficiently | |
6 | 005 | Data inconsistency: Entity already exists, CREATE not possible | The short text describes the object sufficiently | |
7 | 006 | Unable to Create Application log. | The short text describes the object sufficiently | |
8 | 007 | Addition of exception/message to the application log failed. | The short text describes the object sufficiently | |
9 | 008 | Unable to save Application log to the DB. | The short text describes the object sufficiently | |
10 | 009 | Content &1 in proxy field &2 is not supported | The short text describes the object sufficiently | |
11 | 010 | Item ID cannot be kept null. Enter value for ID | The short text describes the object sufficiently | |
12 | 038 | Error creating data of type &1 | The short text describes the object sufficiently | |
13 | 039 | Service interface &1 is not maintained in table OPS_SE_CNTRPT | Space: object requires documentation | |
14 | 040 | Size &1 of input file is too big. Maximal size: &2 | The short text describes the object sufficiently | |
15 | 041 | Input file contains no data | The short text describes the object sufficiently | |
16 | 042 | Error &1 occurred while reading the input file | The short text describes the object sufficiently | |
17 | 043 | Test Case &1 is not maintained in table OPS_SE_CNTRPT_TC | Space: object requires documentation | |
18 | 044 | Error while converting the XML input file into data type &1 | Space: object requires documentation | |
19 | 045 | Error creating object of class &1 | The short text describes the object sufficiently | |
20 | 046 | Error in method &1->start_test() | The short text describes the object sufficiently | |
21 | 047 | Counterpart test successfully completed | The short text describes the object sufficiently | |
22 | 048 | Counterpart test ended with errors | The short text describes the object sufficiently | |
23 | 049 | Counterpart test still running. Try again and increase waiting time. | The short text describes the object sufficiently | |
24 | 050 | & | The short text describes the object sufficiently | |
25 | 051 | No test cases found for service &1 | The short text describes the object sufficiently | |
26 | 052 | No input file specified | The short text describes the object sufficiently | |
27 | 053 | Select a service interface | The short text describes the object sufficiently | |
28 | 054 | Testcase &1 for service interface &2 not found in database | The short text describes the object sufficiently | |
29 | 055 | Content of proxy field &1 is too long for the backend field &2 | The short text describes the object sufficiently | |
30 | 057 | Result could not be checked due to missing MessageID | The short text describes the object sufficiently | |
31 | 058 | Message status for MessageID &1 could not be retrieved | The short text describes the object sufficiently | |
32 | 059 | Message with MessageID &1 successfully sent. For details use tx SXMB_MONI | The short text describes the object sufficiently | |
33 | 060 | No or invalid RFC-destination for receiver-system | The short text describes the object sufficiently | |
34 | 061 | Message has not reached receiver-system yet or wrong reveiver system | The short text describes the object sufficiently | |
35 | 062 | Message with MessageID &1 not sent. For details use tx SXMB_MONI | The short text describes the object sufficiently | |
36 | 063 | Test with MessageID &1 has been corrupted. For details use tx SXMB_MONI | The short text describes the object sufficiently | |
37 | 064 | Message with MessageID &1 is in processing. For details use tx SXMB_MONI | The short text describes the object sufficiently | |
38 | 065 | FEH-Test failed: no message was saved in FEH persistency | The short text describes the object sufficiently | |
39 | 066 | Testcase to test FEH makes no sense: FEH is not active | The short text describes the object sufficiently | |
40 | 067 | Scenario test class &1 does not exist | The short text describes the object sufficiently | |
41 | 068 | Error reading scenario test class &1 | The short text describes the object sufficiently | |
42 | 069 | Invalid inheritance of scenario test class &1 | Space: object requires documentation | |
43 | 070 | Entry Sheet not Created | The short text describes the object sufficiently | |
44 | 071 | No Authorization for Purchase Order | The short text describes the object sufficiently | |
45 | 072 | Item type Code cannot be kept null. Enter value for Type Code. | The short text describes the object sufficiently | |
46 | 073 | Ordinal Number cannot be kept null. enter value for this field. | The short text describes the object sufficiently | |
47 | 074 | Specify Accounting block type code. Type &1 cannot be entered here | The short text describes the object sufficiently | |
48 | 075 | Accounting Block type cannot be changed. Correct value is &1. | The short text describes the object sufficiently | |
49 | 076 | Item ID(s) &1 is not unique. Enter unique value for item ID(s). | The short text describes the object sufficiently | |
50 | 077 | Type code &1 is not valid for root item. Enter value 21. | The short text describes the object sufficiently | |
51 | 078 | Type code &1 is not valid.The supported values are 21,19,301,302,303,305. | The short text describes the object sufficiently | |
52 | 079 | Wrong type code &1. Hierarchy relationship type code value should be 007. | The short text describes the object sufficiently | |
53 | 080 | Hierarchy relationship node should be initial for root item. | The short text describes the object sufficiently | |
54 | 081 | Processing Type Code &1 is not valid for service items. Enter value 09. | The short text describes the object sufficiently | |
55 | 082 | HeirarchyRelationship ParentItemID and Parent Item ID do not match. | The short text describes the object sufficiently | |
56 | 083 | Project Element ID &1 is not valid. Enter value: 6 , 7 or 8. | The short text describes the object sufficiently | |
57 | 084 | Child hierarchy relationship Item ID &1 do not match the parent Item ID. | The short text describes the object sufficiently | |
58 | 085 | Ordinal Number Value &1 is not unique. | The short text describes the object sufficiently | |
59 | 086 | Element &1 not supported for Hierarchy Item &2. | The short text describes the object sufficiently | |
60 | 087 | Purchase Order Item ID &1 for Item ID &2 is not correct. | The short text describes the object sufficiently | |
61 | 088 | Purchasing Contract Item ID &1 for Item ID &2 is not correct. | The short text describes the object sufficiently | |
62 | 089 | Account Assignment data is not entered for all service item(s). | The short text describes the object sufficiently | |
63 | 090 | Ordinal Number Value &1 does not exist for the PO Item &2. | The short text describes the object sufficiently | |
64 | 091 | Ordinal Number Value &1 does not exist. | The short text describes the object sufficiently | |
65 | 092 | Currency Key &1 does not exist for PO &2. Enter currency key &3. | The short text describes the object sufficiently | |
66 | 093 | Hierarchy relationship maintained in Item ID &1 is incorrect. | The short text describes the object sufficiently | |
67 | 094 | &1 should be same in all the account assignment specification. | The short text describes the object sufficiently | |
68 | 095 | Hierarchy relationship node should not be initial for child item. | The short text describes the object sufficiently | |
69 | 096 | Element Base Quantity Type Code is not used. | The short text describes the object sufficiently | |
70 | 097 | No description found for internal value of code GDT &1. | The short text describes the object sufficiently | |
71 | 098 | Field symbol &1 is not assigned. | The short text describes the object sufficiently | |
72 | 099 | The types of the constant &1 and of the internal table &2 doesn't fit. | The short text describes the object sufficiently | |
73 | 100 | The Attribute &1 is no constant. | The short text describes the object sufficiently | |
74 | 101 | &1 &2 is not supported. | The short text describes the object sufficiently | |
75 | 102 | &1 &2 &3 &4 | The short text describes the object sufficiently | |
76 | 103 | Import parameter &1 is required for determining code description/name | The short text describes the object sufficiently | |
77 | 104 | Supplementary components are only required for value mapping and ignored | The short text describes the object sufficiently | |
78 | 105 | For search criteria &1 no internal value exists | The short text describes the object sufficiently |
History
Last changed on/by | 20110908 | SAP | |
SAP Release Created in | 603 |