Message Number list used by SAP ABAP Program RWWBID01 (Batch input program for plant master data (main program))
SAP ABAP Program RWWBID01 (Batch input program for plant master data (main program)) is using
# | Object Type | Object Name | Object Description | Note |
---|---|---|---|---|
1 | Message Number | FB - 119 | ... Country key & is not defined in table T005 | |
2 | Message Number | FB - 131 | Trans. &: Message FB & given with var.1 & var.2 & | |
3 | Message Number | FB - 130 | Trans. &1: &2&3&4 | |
4 | Message Number | FB - 125 | ... Data in table & cannot be processed | |
5 | Message Number | FB - 124 | ... Bank name & | |
6 | Message Number | FB - 123 | Trans. & Tcode &: Only delete flags are being processed | |
7 | Message Number | FB - 122 | Trans. & Tcode &: Block data are being processed | |
8 | Message Number | FB - 121 | Trans. & &: Sales org.not entered; sales area is not being processed | |
9 | Message Number | FB - 120 | Trans. & bank details & & &: ... | |
10 | Message Number | FB - 133 | Trans. &: Record end ind. in table & is not supplied with & | |
11 | Message Number | FB - 118 | ... Country key was not transferred | |
12 | Message Number | FB - 117 | ... Bank master records & & already exist | |
13 | Message Number | FB - 116 | ... Bank master records are not being transferred | |
14 | Message Number | FB - 115 | ... Bank details are to be deleted | |
15 | Message Number | FB - 114 | Trans. & &: Cost control area was not specified in header record | |
16 | Message Number | FB - 113 | Trans. &: Transaction code is & | |
17 | Message Number | FB - 112 | Trans. &: No transaction code was transferred | |
18 | Message Number | FB - 191 | Customer &: For tax data & & there is no tax category ... | |
19 | Message Number | FB - 420 | & | |
20 | Message Number | FB - 198 | ... Detailed data, visiting hours etc. are not transferred | |
21 | Message Number | FB - 197 | Partner & is to be deleted ... | |
22 | Message Number | FB - 196 | ... & & & are not copied | |
23 | Message Number | FB - 195 | Incomplete license data & & & ... | |
24 | Message Number | FB - 194 | Customer &: | |
25 | Message Number | FB - 193 | ... Tax data is therefore not copied | |
26 | Message Number | FB - 192 | Customer &: For tax data & & there is no code ... | |
27 | Message Number | FB - 003 | No batch input records exist in file & | |
28 | Message Number | FB - 190 | Customer &: For tax data & & there is no country ... | |
29 | Message Number | FB - 188 | ... are copied from table & ... | |
30 | Message Number | FB - 184 | ... Alternative times given are therefore not transferred | |
31 | Message Number | FB - 183 | Unloading point &: Times for ID & ... | |
32 | Message Number | FB - 182 | Unloading point &: Goods receiving times ID is not in table & | |
33 | Message Number | FB - 181 | ... Goods receiving times will not be transferred | |
34 | Message Number | FB - 180 | Unloading point & is to be deleted | |
35 | Message Number | FB - 010 | Session &: Character & not a permitted character for 'empty field' | |
36 | Message Number | FB - 018 | File & is being checked | |
37 | Message Number | FB - 017 | ... Last data record ... | |
38 | Message Number | FB - 016 | ... Last header record ... | |
39 | Message Number | FB - 015 | ... Session record ... | |
40 | Message Number | FB - 014 | ... & & | |
41 | Message Number | FB - 013 | ....Editing was terminated | |
42 | Message Number | FB - 012 | Session &: Special character for 'empty field' is & | |
43 | Message Number | FB - 011 | Session &: Session record does not contain any session names | |
44 | Message Number | FB - 110 | Trans. &: Data for table & cannot be processed | |
45 | Message Number | FB - 009 | Session &: Session record does not contain a user name | |
46 | Message Number | FB - 008 | Session & session name & was created | |
47 | Message Number | FB - 007 | Session & session name & was opened | |
48 | Message Number | FB - 006 | Session &: Transferred client & differs from system client & | |
49 | Message Number | FB - 005 | Session &: Session record does not contain a client | |
50 | Message Number | FB - 004 | First record in file & is not a session record (type 0) | |
51 | Message Number | FB - 002 | File & could not be opened | |
52 | Message Number | FB - 021 | To initiate processing, enter 'Call Transaction .. Using ..' | |
53 | Message Number | FB - 111 | Trans. & record &: Table & is not supported | |
54 | Message Number | FB - 109 | Trans. &: Transaction & is not supported | |
55 | Message Number | FB - 108 | Trans. &: Transaction code & is not defined in table T020 | |
56 | Message Number | FB - 107 | Trans. & record &: Table & was transfered more than once | |
57 | Message Number | FB - 105 | Trans. & &: CoCde not entered; company code area not being edited | |
58 | Message Number | FB - 104 | Trans. & &: Acct already exists; general area not being processed | |
59 | Message Number | FB - 103 | Trans. & record &: Table name was not specified | |
60 | Message Number | FB - 102 | Trans. & record &: Data record is not flagged as record type 2 | |
61 | Message Number | FB - 101 | Session &: First trans. does not begin with a header record (type 1) | |
62 | Message Number | FB - 026 | Trans.& & : As from Put 1.3A, use transaction FD32 --> Long text | |
63 | Message Number | FB - 025 | ... also maintain the new fields in table & | |
64 | Message Number | FB - 024 | ... Before the next put, | |
65 | Message Number | FB - 023 | ... Table & was extended | |
66 | Message Number | FB - 022 | The parameter 'Call transaction .. Using ..' has been ignored | |
67 | Message Number | FB - 019 | Session & session name &: No terminations have been found | |
68 | Message Number | WN - 073 | Receiving point & not defined | |
69 | Message Number | WN - 081 | Departments have been assigned to receiving point &. Deletion not allowed | |
70 | Message Number | WX - 890 | & & |