SAP ABAP Message Class UBC_CSP (CSP Customer Service Provider)
Basic Data
Hierarchy
☛
FINBASIS (Software Component) Fin. Basis
⤷
FIN-FB (Application Component) Financials Basis
⤷
UBC_CSP (Package) FSCM Biller Consolidator-Prototype for CSP with Acct.Assgnmt
⤷
⤷
Attributes
| Message class | UBC_CSP | |
| Short Description | CSP Customer Service Provider | |
| Changed On | 20041006 | |
| Last Changed At | 145624 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | Customer &1 does not exist | Space: object requires documentation | ||
| 2 | No relationship exists between biller &1 and customer &2 | Space: object requires documentation | ||
| 3 | For customer &1, no bill item types created for biller &2 | Space: object requires documentation | ||
| 4 | XML bill &2 for customer &1 not found | Space: object requires documentation | ||
| 5 | PDF bill &2 for customer &1 not found | Space: object requires documentation | ||
| 6 | BI session &2 for customer &1 not found | Space: object requires documentation | ||
| 7 | Bill &1 does not exist | Space: object requires documentation | ||
| 8 | No default value exists for accnt assignment &1 for Org &2 (Customizing) | The short text describes the object sufficiently | ||
| 9 | Account assignment field &1 missing on header level | The short text describes the object sufficiently | ||
| 10 | Enter a value for account assignment field &2 on header level | The short text describes the object sufficiently | ||
| 11 | Enter a value for account assignment field &2 on item level | The short text describes the object sufficiently | ||
| 12 | Value &1 is not permitted for account assignment field &2 | Space: object requires documentation | ||
| 13 | Value &1 is not permitted for account assignment field &2 (item &3) | Space: object requires documentation | ||
| 14 | Transmission error (customer: &1) | Space: object requires documentation | ||
| 15 | Error in sender address | Space: object requires documentation | ||
| 16 | Incorrect IDoc message type | Space: object requires documentation | ||
| 17 | No user determined for e-mail address &1 | The short text describes the object sufficiently | ||
| 18 | Organization &1 / biller &2: Error control missing for reason &3 | The short text describes the object sufficiently | ||
| 19 | Bill was rejected | The short text describes the object sufficiently | ||
| 20 | No escalation user defined for organization &1 | The short text describes the object sufficiently | ||
| 21 | Organization &1 / biller &2: bill type &3 not permitted | The short text describes the object sufficiently | ||
| 22 | Organization &1 / biller &2: bill item type &3 not permitted | The short text describes the object sufficiently | ||
| 23 | This action cannot be performed for bill &1 (status &2) | The short text describes the object sufficiently | ||
| 24 | This bill is being forwarded for escalation | The short text describes the object sufficiently | ||
| 25 | Duplicate bill entry: &1 from &2 (TRX-Ref: &3) | The short text describes the object sufficiently | ||
| 26 | Preliminary record generated | The short text describes the object sufficiently | ||
| 27 | Batch input session with ID &1 generated | Space: object requires documentation | ||
| 28 | Batch input session from org. &1 with ID &2 does not exist | The short text describes the object sufficiently | ||
| 29 | No released bills exist for customer &1 | The short text describes the object sufficiently | ||
| 30 | No batch input session created | The short text describes the object sufficiently | ||
| 31 | The Customizing for creating batch input sessions is incomplete | Space: object requires documentation | ||
| 32 | Dear Sir/Madam, | Space: object requires documentation | ||
| 33 | You bill &1 of &2 has been rejected by us. | Space: object requires documentation | ||
| 34 | Reason for Rejection: | Space: object requires documentation | ||
| 35 | Either no bill type or invalid type &1 was specified. | Space: object requires documentation | ||
| 36 | Either no bill item types or invalid ones were specified. | Space: object requires documentation | ||
| 37 | The specified ordering party &1 does not exist. | Space: object requires documentation | ||
| 38 | Kind regards, | Space: object requires documentation | ||
| 39 | &1 | Space: object requires documentation | ||
| 40 | File &1 could not be opened | Space: object requires documentation | ||
| 41 | Error while starting workflow for bill &1 | The short text describes the object sufficiently | ||
| 42 | Bill number &1 was saved in the system | The short text describes the object sufficiently | ||
| 43 | Undefined error occurred calling &1 | Space: object requires documentation | ||
| 44 | Update error: Table &1 | Space: object requires documentation | ||
| 45 | &1 | Space: object requires documentation |
History
| Last changed on/by | 20041006 | SAP | |
| SAP Release Created in | 200 |