SAP ABAP Message Class RMSFRMCST (RMS-FRM: Message Package RMSFRMCST - Customizing)
Basic Data
Hierarchy
☛
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
⤷
PLM-RM (Application Component) Recipe Management
⤷
RMSFRMCST (Package) RMS-FRM: RMS Formula - Customizing

⤷

⤷

Attributes
Message class | ![]() |
RMSFRMCST |
Short Description | ![]() |
RMS-FRM: Message Package RMSFRMCST - Customizing |
Changed On | ![]() |
20100310 |
Last Changed At | ![]() |
132048 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | ![]() |
Customizing messages for the formula object in main package RMSFRM | Space: object requires documentation | |
2 | ![]() |
Messages are valid from Release 2.0 | Space: object requires documentation | |
3 | ![]() |
************************************************************************* | Space: object requires documentation | |
4 | ![]() |
Other message classes - Release 1.0 | Space: object requires documentation | |
5 | ![]() |
*) FRMLALL -> General messages | Space: object requires documentation | |
6 | ![]() |
*) FRMLDLG -> Dialog messages | Space: object requires documentation | |
7 | ![]() |
*) FRMLPVS -> Messages for PVS integration | Space: object requires documentation | |
8 | ![]() |
*) FRMLINF -> Info system messages (search and output functions only) | Space: object requires documentation | |
9 | ![]() |
*) FRMLMSC -> Miscellaneous | Space: object requires documentation | |
10 | ![]() |
The messages are divided up into the following areas: | Space: object requires documentation | |
11 | ![]() |
Message no. Usage | Space: object requires documentation | |
12 | ![]() |
020-299 General messages (called in various components) | Space: object requires documentation | |
13 | ![]() |
880-899 Test messages (deleted before delivery) | Space: object requires documentation | |
14 | ![]() |
900-999 User-Defined Messages | Space: object requires documentation | |
15 | ![]() |
---------------------Read access database------------------------------ | Space: object requires documentation | |
16 | ![]() |
System could not read formula views (table FRMLC01) | Space: object requires documentation | |
17 | ![]() |
Table FRMLC_CPT_KIND could not be read or is empty | Space: object requires documentation | |
18 | ![]() |
Component types assigned to explosion scopes do not exist | Space: object requires documentation | |
19 | ![]() |
Table FRMLT_EXSC could not be read or is empty | Space: object requires documentation | |
20 | ![]() |
No entries exist in Customizing for events and component types | Space: object requires documentation | |
21 | ![]() |
No events were defined in Customizing | Space: object requires documentation | |
22 | ![]() |
No events have been assigned to explosion scopes in Customizing | Space: object requires documentation | |
23 | ![]() |
No parameters were defined for explosion scopes in Customizing | Space: object requires documentation | |
24 | ![]() |
No views have been assigned to the explosion scopes in Customizing | Space: object requires documentation | |
25 | ![]() |
Description for explosion scope & does not exist | Space: object requires documentation | |
26 | ![]() |
Customizing entry with usage is missing for view &1 | Space: object requires documentation | |
27 | ![]() |
Explosion scope &1: Explosion using substances/materials is not defined | Space: object requires documentation | |
28 | ![]() |
Event &1: Comp. type &2 is relevant for function, not for calculation | Space: object requires documentation | |
29 | ![]() |
Specification type &1 of &2 is not permitted for tab page &3 | Space: object requires documentation | |
30 | ![]() |
Entry &1 is not permitted as pushbutton | Space: object requires documentation | |
31 | ![]() |
Internal error in &1 after reading &2 at index &4, subrc: &3 | The short text describes the object sufficiently | |
32 | ![]() |
Environment parameter &1 is obsolete | The short text describes the object sufficiently | |
33 | ![]() |
Environment parameter &1 was not assigned value | The short text describes the object sufficiently | |
34 | ![]() |
Value of environment parameter &1 has different dimension to &2 | The short text describes the object sufficiently | |
35 | ![]() |
Value of environment parameter &1 has illegal dimension | The short text describes the object sufficiently | |
36 | ![]() |
Dimension mass is recommended for value of FRML_DEF_UNIT_FLOAT_STORE | The short text describes the object sufficiently | |
37 | ![]() |
Relevant for consistency check indicator has no effect for view &1 | The short text describes the object sufficiently | |
38 | ![]() |
View &1: Function group &2 is obsolete | The short text describes the object sufficiently | |
39 | ![]() |
Whether view &1 can be edited is not dependent on reaction | The short text describes the object sufficiently | |
40 | ![]() |
Explosion scope &2 must be assigned to view &1 | The short text describes the object sufficiently | |
41 | ![]() |
No explosion scope can be assigned to view &1 | The short text describes the object sufficiently | |
42 | ![]() |
Event &1 was not defined for component type &2 | The short text describes the object sufficiently | |
43 | ![]() |
Event &1 component type &2 is relev. for calculation but not for function | The short text describes the object sufficiently | |
44 | ![]() |
Component type &1 has different settings in different events | The short text describes the object sufficiently | |
45 | ![]() |
No losses are calculated for logistical explosion scope &1 | The short text describes the object sufficiently | |
46 | ![]() |
Losses are taken into account for analytical explosion scope &1 | The short text describes the object sufficiently | |
47 | ![]() |
Single-level explosion does not make sense for explosion scope &1 | The short text describes the object sufficiently | |
48 | ![]() |
Single-level explosion of &1 requires that view &2 can be changed | The short text describes the object sufficiently | |
49 | ![]() |
Explosion scope &1 can only explode via LoM or LoRS | The short text describes the object sufficiently | |
50 | ![]() |
Parameters for explosion scope &1 are not taken into account | The short text describes the object sufficiently | |
51 | ![]() |
Composition data indicator is relevant for explosion scope CMP only | The short text describes the object sufficiently | |
52 | ![]() |
&1: We recommend you always read composition data from EH&S | The short text describes the object sufficiently | |
53 | ![]() |
With reaction, we recommend that you enter data manually for ingredients | The short text describes the object sufficiently | |
54 | ![]() |
Only values OOP_S/NTR_CMP are permitted for nutrients in std. reaction | The short text describes the object sufficiently | |
55 | ![]() |
Only &1 is permitted as a value for composition data for expl. scope &1 | The short text describes the object sufficiently | |
56 | ![]() |
Explos. scope &1: View &2 cannot be changed for specified reaction categ. | The short text describes the object sufficiently | |
57 | ![]() |
Specification type &1 is permitted for I/O view but not for ingredients | The short text describes the object sufficiently | |
58 | ![]() |
Spec. type &1 can be transferred to CMP; &1 is not permitted for view | The short text describes the object sufficiently | |
59 | ![]() |
If parameter &1 has value &2, value &3 is not permitted for parameter &4 | The short text describes the object sufficiently | |
60 | ![]() |
No conversion is allowed for dimension &1 | The short text describes the object sufficiently |
History
Last changed on/by | ![]() |
20100310 | SAP |
SAP Release Created in | 471 |