Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: VT - Vertriebstabellen
Message number: 619
Message text: Only characteristic ' ' and G can be used as price source
In the copying controls for copying billing document (F2) from credit
memo (CR) or debit memo (DR), the price source field should be blank or
contain G.
This message appears if VBTYP for the source billing document is 'M'
and the VBTYP for the target billing document 'O' or 'P'.
Using this copy control, a credit or debit memo is created directly
from the billing document.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Leave the field blank or enter 'G'.
Error message extract from SAP system. Copyright SAP SE.
VT619
- Only characteristic ' ' and G can be used as price source ?The SAP error message VT619, which states "Only characteristic ' ' and G can be used as price source," typically occurs in the context of pricing and condition records in SAP, particularly when dealing with pricing procedures in the Sales and Distribution (SD) module or in the Material Management (MM) module.
Cause:
This error usually arises when there is an attempt to use a characteristic that is not allowed as a price source in the pricing procedure. The message indicates that only specific characteristics (often 'G' for gross price) can be utilized for pricing calculations. The characteristic that is being referenced in the error message is likely either missing or incorrectly configured.
Solution:
To resolve this error, you can take the following steps:
Check Pricing Procedure Configuration:
- Go to the transaction code
V/08
(for pricing procedures) and review the pricing procedure that is being used.- Ensure that the correct characteristics are defined for the pricing condition types.
Review Condition Types:
- Check the condition types that are being used in the pricing procedure. Make sure that they are set up correctly and that they are compatible with the pricing procedure.
Verify Condition Records:
- Use transaction code
VK11
orVK12
to check the condition records for the relevant condition types. Ensure that the records are correctly maintained and that the required characteristics are populated.Check for Customizations:
- If there are any custom developments or enhancements in your SAP system, review them to ensure they are not interfering with the standard pricing logic.
Consult Documentation:
- Refer to SAP documentation or help files for more details on the specific characteristics that can be used as price sources.
Testing:
- After making the necessary changes, perform a test transaction to ensure that the error no longer occurs.
Related Information:
Transaction Codes:
V/08
: Pricing Procedure ConfigurationVK11
: Create Condition RecordVK12
: Change Condition RecordVK13
: Display Condition RecordSAP Notes:
SAP Community:
By following these steps, you should be able to identify the root cause of the VT619 error and implement a solution to resolve it.
Get instant SAP help. Sign up for our Free Essentials Plan.
VT618
During inv. correction requests, first item must be a credit memo item
What causes this issue? With an <GL:invoice_correction_request>invoice correction request</>, the first item must have a credit memo item...
VT617
Inv. corr. requests with sls doc cat L must have pricing det. type 'F'
What causes this issue? If an <GL:invoice_correction_request>invoice correction request</> has sales document category <LB>L </&...
VT620
Quantity/value pos/neg field must be ' ' for credit memos to billing docs
What causes this issue? In the controls for copying billing document (F2) from credit memo (CR) or debit memo (DR), the quantity/field value must be ...
VT621
The assignment and reference number fields must be ' ' or E
What causes this issue? In the controls for copying billing document (F2) from credit memo (CR) or debit memo (DR) the assignment number and referenc...
Click on this link to search all SAP messages.