BDT_CONSISTENCY_CHCK - Messages for BDT_CHECK
The following messages are stored in message class BDT_CONSISTENCY_CHCK: Messages for BDT_CHECK.
It is part of development package BUPA in software component AP-MD-BP. This development package consists of objects that can be grouped under "SAP Business Partner".
It is part of development package BUPA in software component AP-MD-BP. This development package consists of objects that can be grouped under "SAP Business Partner".
Message Nr ▲ | Message Text |
---|---|
000 | Field group &1 is assigned to several views |
001 | Field group &1 is not assigned to any views |
002 | No screen fields are assigned to field group &1 |
003 | No applications are assigned to view &1 |
004 | The stated differentiation type does not exist in view &1 |
005 | There is more than one text object on screen &1 |
006 | View &1 is not assigned to a section |
007 | View &1 is assigned to a nonexistent field group |
008 | No main programs are assigned to view &1 |
009 | Main program &1 is not available for view &2 |
010 | View &1 not active |
011 | Section &1 is not assigned to a screen |
012 | Section &1 is assigned to a nonexistent view |
013 | Screen &1 is not assigned to a screen sequence |
014 | Screen &1 is not assigned to a section |
015 | Screen &1 is assigned to a nonexistent section |
016 | Function module &1 is not available for foreign screen &2 |
017 | A standard screen sequence has not been assigned to application object &1 |
018 | More than one stndrd screen sequence assigned to screen sequence type &1 |
019 | Screen sequence &1 has been assigned to a nonexistent screen |
020 | Screen sequence &1 has not been assigned to an object part |
021 | Function module &1 not active in BDT |
022 | Function module &1 does not exist |
023 | Interface component &1 not planned in the function module &2 |
024 | Function module &1 has been assigned to the event more than once |
025 | Application &1 does not exist for function module &2 |
026 | Application &1 is not active for function module &2 |
027 | Interface category &1 is not planned in the function module &2 |
028 | Standard GUI function TBZ4: &1 is not a valid screen sequence category |
029 | GUI function TBZ4C: &1 is not a valid screen sequence category |
030 | View &1 does not exist in the GUI functions |
031 | View &2, assigned to object part &1, is not available |
032 | Object part &1 is not assigned to an application |
033 | Object part &1 has been assigned to a non-active application |
034 | Object part &1 has been assigned to nonexistent screen sequence &2 |
035 | The differentiation type &2, assigned to object part &1, does not exist |
036 | The data set &2, assigned to object part &1, does not exist |
037 | Object part &2, assigned to data set &1, does not exist |
038 | Invalid object part &1 in object part grouping &2 |
039 | Object part grouping &1 contains ivalid screen sequence &2 |
040 | Invalid object part grouping &1 in application transaction &2 |
041 | Invalid object parts &1 in application transaction &2 |
042 | Transaction code &1 does not exist |
043 | Table &1 is not defined in DDIC |
044 | DI structure &1 is not defined in DDIC |
045 | No DI structures have been assigned to table &1 |
046 | No change document objects have been assigned to table &1 |
047 | Change document object &1 is not defined in DDIC |
048 | DB table field &1 for table &2 is not defined in DDIC |
049 | Screen field &1 for screen table &2 is not stored in BDT table TBZ3R |
050 | Assignment of view &1 for object part &2 is obsolete; use the data sets |
051 | Application &1 is not active |
052 | There is no error message for activity category &1 |
053 | Differentiation type &2, assigned to application obj &1, does not exist |
059 | Section &1 is not assigned to a view |
060 | The function module is missing for the foreign screen &1 |
070 | Function code &1 violates the naming conventions |