Do you have any question about this error?
Message type: E = Error
Message class: REORPO - Messages for Continuous Occupancy and Move Planning
Message number: 067
Message text: &1 - price factor is zero
The price factor for entry &V1& is not defined or it is zero.
The result of using this price factor is that the occupancy is not
billed in posting for continuous occupancy, or the value of zero is used
in the calculation. If this is the result you want, you can ignore this
message.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
INCLUDE RECA_CUSTOMIZED_MESSAGE_INFO OBJECT DOKU ID TX
Error message extract from SAP system. Copyright SAP SE.
REORPO067
- &1 - price factor is zero ?The SAP error message REORPO067 indicates that there is an issue with the price factor being zero in the context of a pricing procedure or condition record. This error typically arises in scenarios involving pricing in sales orders, purchase orders, or other financial transactions where pricing conditions are applied.
Cause:
Zero Price Factor: The most direct cause of this error is that the price factor for a specific condition record is set to zero. This can happen if:
- The condition record was incorrectly maintained.
- The pricing procedure is not set up correctly.
- There are missing or incorrect entries in the master data (e.g., material master, customer master).
Condition Type Configuration: The condition type associated with the pricing procedure may not be configured properly, leading to a situation where the price factor is calculated as zero.
Data Inconsistencies: There may be inconsistencies in the data being used for pricing, such as missing or incorrect entries in the relevant tables.
Solution:
Check Condition Records:
- Go to the transaction code
VK13
(Display Condition) orVK11
(Create Condition) to check the condition records for the relevant pricing condition.- Ensure that the price factor is set correctly and is not zero.
Review Pricing Procedure:
- Use transaction code
V/08
to review the pricing procedure configuration.- Ensure that the condition types are correctly defined and that the calculation schema is appropriate for your business needs.
Master Data Verification:
- Check the relevant master data (material master, customer master) to ensure that all necessary fields are filled out correctly and that there are no missing entries that could affect pricing.
Consult Documentation:
- Review SAP documentation or help files related to pricing procedures and condition records for additional insights on how to configure them correctly.
Testing:
- After making changes, perform tests to ensure that the pricing is calculated correctly and that the error does not reoccur.
Related Information:
Transaction Codes:
VK11
- Create ConditionVK12
- Change ConditionVK13
- Display ConditionV/08
- Maintain Pricing ProceduresSAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search for the error message number in the SAP Support Portal.
User Forums: Consider checking SAP community forums or user groups for discussions related to this error, as other users may have encountered and resolved similar issues.
By following these steps, you should be able to identify the root cause of the REORPO067 error and implement a solution to resolve it.
Get instant SAP help. Start your 7-day free trial now.
REORPO066
Entry &1 - reservation object is already billed up to &2
What causes this issue? The reservation object was already billed up to &V2&. It is no longer possible to change the occupancy before this da...
REORPO065
Reservation object still used in move plan &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
REORPO068
&1 - price factor is negative (&2)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
REORPO069
Reservation object &1 was already billed for &2
What causes this issue? Reservation object <ZH>&V1&</> was already billed for the period up to &V2&. You entered new occu...
Click on this link to search all SAP messages.