SAP ABAP Message Class >9 (Contract A/R and A/P: Customizing)
Basic Data
Hierarchy
☛
FI-CA (Software Component) FI-CA
⤷ FI-CA (Application Component) Contract Accounts Receivable and Payable
⤷ FKKB (Package) Contract A/R & A/P: Central Objects
⤷ FI-CA (Application Component) Contract Accounts Receivable and Payable
⤷ FKKB (Package) Contract A/R & A/P: Central Objects
Attributes
Message class | >9 | |
Short Description | Contract A/R and A/P: Customizing | |
Changed On | 20080505 | |
Last Changed At | 145641 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 001 | User &1 does not exist | Space: object requires documentation | |
2 | 002 | Withholding tax code &1 is not intended for country &2 | The short text describes the object sufficiently | |
3 | 100 | **** 100-199 reserved for FI-CA payment customizing ******************* | ||
4 | 101 | Payment method & is still used company code & | ||
5 | 102 | Check and euro transfer cancel each other out | Space: object requires documentation | |
6 | 103 | Check/euro transfer and incoming payment cancel each other out | ||
7 | 104 | Check/euro transfer/post bank and internal clearing cancel each other out | ||
8 | 105 | Post office account and bank account are mutually exclusive | Space: object requires documentation | |
9 | 106 | Paymnt card and check/EU int. transf./post office are mutually exclusive | Space: object requires documentation | |
10 | 107 | Should payment card be used for outgoing payments? | Space: object requires documentation | |
11 | 108 | Street required and address not required exclude each other | Space: object requires documentation | |
12 | 109 | Payment order and Boleto exclude each other | Space: object requires documentation | |
13 | 110 | Payment card and payment order exclude each other | The short text describes the object sufficiently | |
14 | 111 | Payment order and check exclude each other | The short text describes the object sufficiently | |
15 | 112 | Attributes specified exclude each other | Space: object requires documentation | |
16 | 113 | Bank details, IBAN and SWIFT code are required for SEPA payment method | The short text describes the object sufficiently | |
17 | 114 | SEPA mandates are required only for incoming payments | The short text describes the object sufficiently | |
18 | 200 | ****** 200-300 reserved for FI-CA dunning customizing ******************* | ||
19 | 201 | There still are entries with higher dunning levels | ||
20 | 202 | Dunning level & cannot be assigned | ||
21 | 203 | You have reached the maximum number of dunning levels | ||
22 | 204 | There are entries marked for deletion | ||
23 | 205 | Days in arrears and dunning interval cannot be simultaneously left blank | Space: object requires documentation | |
24 | 206 | Days in arrears of dunning level & : & days more than level & : & days | Space: object requires documentation | |
25 | 207 | You have not specified a dunning charges schema for the charge types | Space: object requires documentation | |
26 | 208 | No dunning charge types exist for the dunning charges schema specified | Space: object requires documentation | |
27 | 209 | Maximum of 3 charge categories allowed for each dunning charge schema | Space: object requires documentation | |
28 | 300 | *********300-310****Customizing TFK001B | ||
29 | 301 | Company codes &1 and &2 have different currencies | Space: object requires documentation | |
30 | 302 | Number range interval &1 is not defined | Space: object requires documentation | |
31 | 303 | The number range object &1 does not exist | Space: object requires documentation | |
32 | 304 | &1 has external number assignment, choose another number range | The short text describes the object sufficiently | |
33 | 311 | Select an entry | Space: object requires documentation | |
34 | 312 | You cannot define a customer function module for this event | Space: object requires documentation | |
35 | 313 | Mulitple modules permitted - the consecutive number must not equal 0 | Space: object requires documentation | |
36 | 314 | Event &: Consecutive number must be a 0 | Space: object requires documentation | |
37 | 315 | You can only define one customer function module for event & | Space: object requires documentation | |
38 | 316 | Transaction &1 not deleted since the transaction is still being used | Space: object requires documentation | |
39 | 317 | Main transaction &1/partial transaction &2 not deleted | Space: object requires documentation | |
40 | 320 | **** 320-325 reserved for Customizing payment/return lots ****** | Space: object requires documentation | |
41 | 321 | Enter processes for which clearing account &1 / &2 is valid | Space: object requires documentation | |
42 | 890 | Internal error: Callup of function module ICON_CREATE | Space: object requires documentation |
History
Last changed on/by | 20080505 | SAP | |
SAP Release Created in |