SAP ABAP Message Class WB2B_EXPENSE (Global Trade Expenses)
Basic Data
Hierarchy
☛
EA-GLTRADE (Software Component) SAP Enterprise Extension Global Trade
⤷
LO-GT-TE (Application Component) Expenses
⤷
WB2B_EXPENSE (Package) Trading Expense Handling
⤷
⤷
Attributes
| Message class | WB2B_EXPENSE | |
| Short Description | Global Trade Expenses | |
| Changed On | 20131127 | |
| Last Changed At | 182116 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | The assignement to this document class ( &1 ) is not defined | Space: object requires documentation | ||
| 2 | Internal error occurred | Space: object requires documentation | ||
| 3 | Document flow does not exist | Space: object requires documentation | ||
| 4 | The calculatated line price is zero. Enter a larger value | Space: object requires documentation | ||
| 5 | No expense type exists for this combination | Space: object requires documentation | ||
| 6 | No master conditions are maintained for VBD type &1 | Space: object requires documentation | ||
| 7 | No master conditions were found | Space: object requires documentation | ||
| 8 | Expense class &1 does not exist | Space: object requires documentation | ||
| 9 | Accounting type &1 does not exist | Space: object requires documentation | ||
| 10 | Accounting type &1 cannot be used for expense class &2 | Space: object requires documentation | ||
| 11 | Posting type &1 does not exist | Space: object requires documentation | ||
| 12 | The internal category of posting type &1 has not been maintained | Space: object requires documentation | ||
| 13 | Posting type &1 is not defined for expense class &2 | Space: object requires documentation | ||
| 14 | Enter the TEW type | Space: object requires documentation | ||
| 15 | Enter the accounting type | Space: object requires documentation | ||
| 16 | Enter the posting type | Space: object requires documentation | ||
| 17 | Enter the expense class | Space: object requires documentation | ||
| 18 | Enter the vendor billing document type | Space: object requires documentation | ||
| 19 | Vendor billing document type &1 cannot be used here | Space: object requires documentation | ||
| 20 | Condition &1 is defined as a quantity-dependent condition | Space: object requires documentation | ||
| 21 | The copy control for VBD type &1 does not exist | Space: object requires documentation | ||
| 22 | The schema must have a condition with condition category = 'd' | Space: object requires documentation | ||
| 23 | The planned conditions from the trading contract are used | Space: object requires documentation | ||
| 24 | Data is saved | Space: object requires documentation | ||
| 25 | No Customizing exists in Expense Handling for this condition | Space: object requires documentation | ||
| 26 | Enter the application | Space: object requires documentation | ||
| 27 | Enter the condition key | Space: object requires documentation | ||
| 28 | Expense processing is not possible | Space: object requires documentation | ||
| 29 | Values will be recalculated because the currency was changed | Space: object requires documentation | ||
| 30 | Check the partner input | Space: object requires documentation | ||
| 31 | Enter the step and TEW type | Space: object requires documentation | ||
| 32 | There is no entry for the combination &1, &2 | Space: object requires documentation | ||
| 33 | Vendor billing doc. type &1 does not post to a G/L account (provision) | Space: object requires documentation | ||
| 34 | The G/L account cannot be cleared with this VBD type (posting key) | Space: object requires documentation | ||
| 35 | Set price copy control to D or G | Space: object requires documentation | ||
| 36 | Some documents are currently locked by other users | Space: object requires documentation | ||
| 37 | Condition &2 was not found in document &1 (Customizing error) | Space: object requires documentation | ||
| 38 | The condition was not found (Customizing/pricing error) | Space: object requires documentation | ||
| 39 | No settlement VBD type found for VBD type &1 (settlement type 2) | Space: object requires documentation | ||
| 40 | Document &1 has already been settled | Space: object requires documentation | ||
| 41 | Automatic vendor billing document creation not set | Space: object requires documentation | ||
| 42 | Expense class &1 is not in group &2 | Space: object requires documentation | ||
| 43 | Documents were already saved and can only be cancelled | Space: object requires documentation | ||
| 44 | Error has occurred in the calculation | Space: object requires documentation | ||
| 45 | The total for the entries (&1) is not equal to the basic value (&2) | Space: object requires documentation | ||
| 46 | Enter the tax indicator | Space: object requires documentation | ||
| 47 | Document &1 is not in the document flow for document &2 | Space: object requires documentation | ||
| 48 | Enter a positive value | Space: object requires documentation | ||
| 49 | Not all items are relevant for expense processing | Space: object requires documentation | ||
| 50 | Enter the currency | Space: object requires documentation | ||
| 51 | The specified vendor billing document is not relevant for settlements | Space: object requires documentation | ||
| 52 | The document has already been settled | Space: object requires documentation | ||
| 53 | No settlement vendor billing document type is defined in Customizing | Space: object requires documentation | ||
| 54 | Manual settlement is not possible for expense class two | Space: object requires documentation | ||
| 55 | This FI document was generated in FI (without logistics documents) | Space: object requires documentation | ||
| 56 | This type has already been assigned | Space: object requires documentation | ||
| 57 | No planned delivery costs found for the current document items | The short text describes the object sufficiently | ||
| 58 | Zero not permitted as value for planned expenses - check entry | The short text describes the object sufficiently | ||
| 59 | Expenses class group &1 does not exist | The short text describes the object sufficiently | ||
| 60 | Condition type &1 and table &2 do not exist in CondTypeGroup &3 | The short text describes the object sufficiently | ||
| 61 | Expenses type for application &1 and CondTypeGroup &2 not maintained | The short text describes the object sufficiently | ||
| 62 | Expenses with settlement for CondType &1 and table &2 not planned | The short text describes the object sufficiently | ||
| 63 | Expenses entry for CondType &1 and table &2 not maintained | The short text describes the object sufficiently | ||
| 64 | Condition record for condition type &1 and application &2 already exists | The short text describes the object sufficiently | ||
| 65 | Condition record not present, cond type &1, table &2, key &3 | The short text describes the object sufficiently | ||
| 66 | Condition record not existent in period &1 - &2, cond. type &1, key &4 | The short text describes the object sufficiently | ||
| 67 | Condition type &1 is not assigned to a condition type group | The short text describes the object sufficiently | ||
| 68 | Company Code is not maintained for Purchase Organization &1 or Plant &2 | The short text describes the object sufficiently | ||
| 69 | Accrual account should not be assigned for settlement VBD type &1 | The short text describes the object sufficiently | ||
| 70 | Vendor billing document type &1 does not post to an A/R or A/P account | The short text describes the object sufficiently |
History
| Last changed on/by | 20131127 | SAP | |
| SAP Release Created in |