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
⤷
⤷
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 | Importing parameter has incompatible type at message call &1 &2 | The short text describes the object sufficiently | ||
| 2 | Importing parameter has incompatible type at message call &1 &2 | The short text describes the object sufficiently | ||
| 3 | No result for test scenario &1. | The short text describes the object sufficiently | ||
| 4 | Test scenario with message-id &1 finished successfully. | The short text describes the object sufficiently | ||
| 5 | Test scenario with message-id &1 failed. | The short text describes the object sufficiently | ||
| 6 | Data inconsistency: Entity already exists, CREATE not possible | The short text describes the object sufficiently | ||
| 7 | Unable to Create Application log. | The short text describes the object sufficiently | ||
| 8 | Addition of exception/message to the application log failed. | The short text describes the object sufficiently | ||
| 9 | Unable to save Application log to the DB. | The short text describes the object sufficiently | ||
| 10 | Content &1 in proxy field &2 is not supported | The short text describes the object sufficiently | ||
| 11 | Item ID cannot be kept null. Enter value for ID | The short text describes the object sufficiently | ||
| 12 | Error creating data of type &1 | The short text describes the object sufficiently | ||
| 13 | Service interface &1 is not maintained in table OPS_SE_CNTRPT | Space: object requires documentation | ||
| 14 | Size &1 of input file is too big. Maximal size: &2 | The short text describes the object sufficiently | ||
| 15 | Input file contains no data | The short text describes the object sufficiently | ||
| 16 | Error &1 occurred while reading the input file | The short text describes the object sufficiently | ||
| 17 | Test Case &1 is not maintained in table OPS_SE_CNTRPT_TC | Space: object requires documentation | ||
| 18 | Error while converting the XML input file into data type &1 | Space: object requires documentation | ||
| 19 | Error creating object of class &1 | The short text describes the object sufficiently | ||
| 20 | Error in method &1->start_test() | The short text describes the object sufficiently | ||
| 21 | Counterpart test successfully completed | The short text describes the object sufficiently | ||
| 22 | Counterpart test ended with errors | The short text describes the object sufficiently | ||
| 23 | Counterpart test still running. Try again and increase waiting time. | The short text describes the object sufficiently | ||
| 24 | & | The short text describes the object sufficiently | ||
| 25 | No test cases found for service &1 | The short text describes the object sufficiently | ||
| 26 | No input file specified | The short text describes the object sufficiently | ||
| 27 | Select a service interface | The short text describes the object sufficiently | ||
| 28 | Testcase &1 for service interface &2 not found in database | The short text describes the object sufficiently | ||
| 29 | Content of proxy field &1 is too long for the backend field &2 | The short text describes the object sufficiently | ||
| 30 | Result could not be checked due to missing MessageID | The short text describes the object sufficiently | ||
| 31 | Message status for MessageID &1 could not be retrieved | The short text describes the object sufficiently | ||
| 32 | Message with MessageID &1 successfully sent. For details use tx SXMB_MONI | The short text describes the object sufficiently | ||
| 33 | No or invalid RFC-destination for receiver-system | The short text describes the object sufficiently | ||
| 34 | Message has not reached receiver-system yet or wrong reveiver system | The short text describes the object sufficiently | ||
| 35 | Message with MessageID &1 not sent. For details use tx SXMB_MONI | The short text describes the object sufficiently | ||
| 36 | Test with MessageID &1 has been corrupted. For details use tx SXMB_MONI | The short text describes the object sufficiently | ||
| 37 | Message with MessageID &1 is in processing. For details use tx SXMB_MONI | The short text describes the object sufficiently | ||
| 38 | FEH-Test failed: no message was saved in FEH persistency | The short text describes the object sufficiently | ||
| 39 | Testcase to test FEH makes no sense: FEH is not active | The short text describes the object sufficiently | ||
| 40 | Scenario test class &1 does not exist | The short text describes the object sufficiently | ||
| 41 | Error reading scenario test class &1 | The short text describes the object sufficiently | ||
| 42 | Invalid inheritance of scenario test class &1 | Space: object requires documentation | ||
| 43 | Entry Sheet not Created | The short text describes the object sufficiently | ||
| 44 | No Authorization for Purchase Order | The short text describes the object sufficiently | ||
| 45 | Item type Code cannot be kept null. Enter value for Type Code. | The short text describes the object sufficiently | ||
| 46 | Ordinal Number cannot be kept null. enter value for this field. | The short text describes the object sufficiently | ||
| 47 | Specify Accounting block type code. Type &1 cannot be entered here | The short text describes the object sufficiently | ||
| 48 | Accounting Block type cannot be changed. Correct value is &1. | The short text describes the object sufficiently | ||
| 49 | Item ID(s) &1 is not unique. Enter unique value for item ID(s). | The short text describes the object sufficiently | ||
| 50 | Type code &1 is not valid for root item. Enter value 21. | The short text describes the object sufficiently | ||
| 51 | Type code &1 is not valid.The supported values are 21,19,301,302,303,305. | The short text describes the object sufficiently | ||
| 52 | Wrong type code &1. Hierarchy relationship type code value should be 007. | The short text describes the object sufficiently | ||
| 53 | Hierarchy relationship node should be initial for root item. | The short text describes the object sufficiently | ||
| 54 | Processing Type Code &1 is not valid for service items. Enter value 09. | The short text describes the object sufficiently | ||
| 55 | HeirarchyRelationship ParentItemID and Parent Item ID do not match. | The short text describes the object sufficiently | ||
| 56 | Project Element ID &1 is not valid. Enter value: 6 , 7 or 8. | The short text describes the object sufficiently | ||
| 57 | Child hierarchy relationship Item ID &1 do not match the parent Item ID. | The short text describes the object sufficiently | ||
| 58 | Ordinal Number Value &1 is not unique. | The short text describes the object sufficiently | ||
| 59 | Element &1 not supported for Hierarchy Item &2. | The short text describes the object sufficiently | ||
| 60 | Purchase Order Item ID &1 for Item ID &2 is not correct. | The short text describes the object sufficiently | ||
| 61 | Purchasing Contract Item ID &1 for Item ID &2 is not correct. | The short text describes the object sufficiently | ||
| 62 | Account Assignment data is not entered for all service item(s). | The short text describes the object sufficiently | ||
| 63 | Ordinal Number Value &1 does not exist for the PO Item &2. | The short text describes the object sufficiently | ||
| 64 | Ordinal Number Value &1 does not exist. | The short text describes the object sufficiently | ||
| 65 | Currency Key &1 does not exist for PO &2. Enter currency key &3. | The short text describes the object sufficiently | ||
| 66 | Hierarchy relationship maintained in Item ID &1 is incorrect. | The short text describes the object sufficiently | ||
| 67 | &1 should be same in all the account assignment specification. | The short text describes the object sufficiently | ||
| 68 | Hierarchy relationship node should not be initial for child item. | The short text describes the object sufficiently | ||
| 69 | Element Base Quantity Type Code is not used. | The short text describes the object sufficiently | ||
| 70 | No description found for internal value of code GDT &1. | The short text describes the object sufficiently | ||
| 71 | Field symbol &1 is not assigned. | The short text describes the object sufficiently | ||
| 72 | The types of the constant &1 and of the internal table &2 doesn't fit. | The short text describes the object sufficiently | ||
| 73 | The Attribute &1 is no constant. | The short text describes the object sufficiently | ||
| 74 | &1 &2 is not supported. | The short text describes the object sufficiently | ||
| 75 | &1 &2 &3 &4 | The short text describes the object sufficiently | ||
| 76 | Import parameter &1 is required for determining code description/name | The short text describes the object sufficiently | ||
| 77 | Supplementary components are only required for value mapping and ignored | The short text describes the object sufficiently | ||
| 78 | 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 |