OPS_SE_GEN - Service enabling generic functionality

The following messages are stored in message class OPS_SE_GEN: Service enabling generic functionality.
It is part of development package OPS_SE_COMMON_FUNCTIONALITIES in software component MM. This development package consists of objects that can be grouped under "Functions for Cross-Component Use".

Message Nr ▲	Message Text
000	Importing parameter has incompatible type at message call &1 &2
001	Importing parameter has incompatible type at message call &1 &2
002	No result for test scenario &1.
003	Test scenario with message-id &1 finished successfully.
004	Test scenario with message-id &1 failed.
005	Data inconsistency: Entity already exists, CREATE not possible
006	Unable to Create Application log.
007	Addition of exception/message to the application log failed.
008	Unable to save Application log to the DB.
009	Content &1 in proxy field &2 is not supported
010	Item ID cannot be kept null. Enter value for ID
038	Error creating data of type &1
039	Service interface &1 is not maintained in table OPS_SE_CNTRPT
040	Size &1 of input file is too big. Maximal size: &2
041	Input file contains no data
042	Error &1 occurred while reading the input file
043	Test Case &1 is not maintained in table OPS_SE_CNTRPT_TC
044	Error while converting the XML input file into data type &1
045	Error creating object of class &1
046	Error in method &1->start_test()
047	Counterpart test successfully completed
048	Counterpart test ended with errors
049	Counterpart test still running. Try again and increase waiting time.
050	&
051	No test cases found for service &1
052	No input file specified
053	Select a service interface
054	Testcase &1 for service interface &2 not found in database
055	Content of proxy field &1 is too long for the backend field &2
057	Result could not be checked due to missing MessageID
058	Message status for MessageID &1 could not be retrieved
059	Message with MessageID &1 successfully sent. For details use tx SXMB_MONI
060	No or invalid RFC-destination for receiver-system
061	Message has not reached receiver-system yet or wrong reveiver system
062	Message with MessageID &1 not sent. For details use tx SXMB_MONI
063	Test with MessageID &1 has been corrupted. For details use tx SXMB_MONI
064	Message with MessageID &1 is in processing. For details use tx SXMB_MONI
065	FEH-Test failed: no message was saved in FEH persistency
066	Testcase to test FEH makes no sense: FEH is not active
067	Scenario test class &1 does not exist
068	Error reading scenario test class &1
069	Invalid inheritance of scenario test class &1
070	Entry Sheet not Created
071	No Authorization for Purchase Order
072	Item type Code cannot be kept null. Enter value for Type Code.
073	Ordinal Number cannot be kept null. enter value for this field.
074	Specify Accounting block type code. Type &1 cannot be entered here
075	Accounting Block type cannot be changed. Correct value is &1.
076	Item ID(s) &1 is not unique. Enter unique value for item ID(s).
077	Type code &1 is not valid for root item. Enter value 21.
078	Type code &1 is not valid.The supported values are 21,19,301,302,303,305.
079	Wrong type code &1. Hierarchy relationship type code value should be 007.
080	Hierarchy relationship node should be initial for root item.
081	Processing Type Code &1 is not valid for service items. Enter value 09.
082	HeirarchyRelationship ParentItemID and Parent Item ID do not match.
083	Project Element ID &1 is not valid. Enter value: 6 , 7 or 8.
084	Child hierarchy relationship Item ID &1 do not match the parent Item ID.
085	Ordinal Number Value &1 is not unique.
086	Element &1 not supported for Hierarchy Item &2.
087	Purchase Order Item ID &1 for Item ID &2 is not correct.
088	Purchasing Contract Item ID &1 for Item ID &2 is not correct.
089	Account Assignment data is not entered for all service item(s).
090	Ordinal Number Value &1 does not exist for the PO Item &2.
091	Ordinal Number Value &1 does not exist.
092	Currency Key &1 does not exist for PO &2. Enter currency key &3.
093	Hierarchy relationship maintained in Item ID &1 is incorrect.
094	&1 should be same in all the account assignment specification.
095	Hierarchy relationship node should not be initial for child item.
096	Element Base Quantity Type Code is not used.
097	No description found for internal value of code GDT &1.
098	Field symbol &1 is not assigned.
099	The types of the constant &1 and of the internal table &2 doesn't fit.
100	The Attribute &1 is no constant.
101	&1 &2 is not supported.
102	&1 &2 &3 &4
103	Import parameter &1 is required for determining code description/name
104	Supplementary components are only required for value mapping and ignored
105	For search criteria &1 no internal value exists