EBDR - Message class for External Billing Document Requests

The following messages are stored in message class EBDR: Message class for External Billing Document Requests.
It is part of development package VF in software component SD-BIL. This development package consists of objects that can be grouped under "Application development R/3 invoice".
Message Nr
Message Text
001BDR &1 without item ID does not exist. Unable to update.
002The inbound data for reference &1/&2 is inconsistent.
003Billing document request &1 created successfully.
004The creation of test data in productive systems is disabled.
005BDR &1 cannot be deleted because it has already been invoiced.
006BDR &1 cannot be deleted because it is locked by another process.
007BDR &1 cannot be deleted because it is already in process.
008Rejected BDR &1 cannot be deleted because it has already been invoiced.
009OBSOLETE
010BDR &1 cannot be rejected because it is locked by another process.
011BDR &1 cannot be rejected while it has the invoiced status.
012BDR &1 cannot be rejected. It has already been rejected.
013Billing document request cannot be created. &1
014Billing document request could not be created due to item errors.
015Document &1 is not a billing document request. It will remain unchanged.
016BDR with preceding document &1 has not been created due to item errors.
017Billing document request &1 rejected successfully.
018Billing document request &1 can not be rejected. &2.
019There is more than 1 entry in input data of preceding document &1 item &2
020Billing document request &1 for reference &2 (&3) already exists.
021Billing document request &1 deleted successfully.
022Billing document request &1 could not be deleted. &2.
023Internal error during import of sheet: &1.
024Error on sheet &1, column &2: field name &3 for structure &4 is invalid.
025Error on sheet &1, row &2, field &3. Value &4 is too long.
026Error on sheet &1, row &2, field &3. Cannot convert &4 to date.
027Error on sheet &1, row &2, field &3. Value &4 is invalid.
028Unexpected error while importing sheet &1, row &2, field &3, value &4.
029There is no document data in the selected file.
030Error on sheet &1, row &2, field &3. &4
031Condition input data for preceding document &1 item &2 can't be assigned.
032Text input data for preceding document &1 item &2 can't be assigned.
033Payment card input data for preceding document &1 can't be assigned.
034BDR &1 can't be deleted: Associated prelim. billing doc. already exists.
035Rejected BDR &1 can't be deleted: Prelim. billing doc. already exists.
036Billing document request &1 was created for reference document &2.
037Unable to create billing document requests for reference document &1.
038BDRs could only be created for some items of reference document &1.
039Billing document request &1 rejected successfully.
040Document &1 not found.
041No BDR found for reference document &1 and source system &2.
042IV_SENDERLOGICALSYSTEM must not be initial.
043SENDERLOGICALSYSTEM must not be initial.
044LOGSYS must be filled for all items.
045Document numbers or preceding document numbers must be filled.
046Billing document request &1 deleted successfully.
047Transaction VFR2 is not released and cannot be used.
048Quantity cannot have a negative value.
049
050Customizing for condition type &1 can't be determined.
051Condition currency &1 (&2) does not match condition calculation type &3.
052Overflow in conversion of condition rate value &1 (&2).
053Overflow in conversion of payment card authorization amount &1 (&2).
054Arithmetic error in conversion of payment card auth. amount &1 (&2).
060Content of reference document &1 item &2 is erroneous.
061Text content of reference document &1 is erroneous.
062Payment card content of reference document &1 is erroneous.
063Text content of reference document &1 item &2 is erroneous.
064Pricing element content of reference document &1 item &2 is erroneous.
070Error in account determination for reference document &1, item &2.
081Billing document request &1 is not in the database.
082Error in custom field mapping. Please contact customer support.
100Feature has not been implemented yet.
150Partner input data for preceding document &1, item &2 can't be assigned.
301Payment service provider (PSP) &1 is not valid. Provide a valid PSP.
302For &1 (&2), payment service &3 (&4), the payment ID was not provided.
303For &1 (&2), payment service &3 (&4), transaction ID was not provided.
304For &1 (&2), payment serv. &3 (&4), authorization data was not provided.
399&1
400An error occurred during creation of the billing document request.
410Current billing doc. request status doesn't allow account determination.
411Error in account determination.
Privacy Policy