How To Fix O1613 - Source for LIA material price in co. code & was not found in table OI001

SAP Error Message - Details

• Message type: E = Error

• Message class: O1 - IS-Oil : Message pool exchanges

• Message number: 613

• Message text: Source for LIA material price in co. code & was not found in table OI001

What causes this issue?

The source for the LIA material price could not be determined from table
<ZH>OI001</>. Either there is no entry in the table for company code
&V1& or there is no value maintained for field <ZH>LIA-PI</> for this
company code.

System Response

When posting an LIA document for a book receipt or book delivery, the
material price is read from either the Logical Inventory Valuation
Segment (OIA07) or the Material Valuation Record (MBEW). It could not
be determined where to get material prices for company code &V1&.

How to fix this error?

Check that table <ZH>OI001</> contains an entry for company code &V1&
and the field <ZH>LIA-PI</> has a value <ZH>1</> or <ZH>2</>.
1 - LIA material price from Logical Inventory Valuation Segment
2 - LIA material price from Material Valuation Record (MBEW)
If you have proper authority, maintain the following Customizing
activity. Otherwise, contact the system administrator:

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

<ZK>IS-Oil IMG via TDP -> Global Settings -> Parameter Assignments ->
Maintain IS-Oil company code parameters</>

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message O1613 - Source for LIA material price in co. code & was not found in table OI001 ?

  The SAP error message O1613 indicates that the system is unable to find a source for the LIA (Logistics Invoice Verification) material price in the specified company code in the table OI001. This typically occurs during the invoice verification process when the system is trying to determine the price for a material that is being processed.
  Cause:
  
  Missing Data in OI001 Table: The most common cause of this error is that the relevant entry for the material and company code is missing in the OI001 table. This table is used to store information related to the LIA material prices.
  Incorrect Configuration: There may be a configuration issue where the material is not properly set up for the company code in question.
  Material Master Issues: The material master data may not be correctly maintained, leading to discrepancies in pricing information.
  Price Change Not Updated: If there was a recent change in pricing or a new material was created, the necessary updates may not have been made in the OI001 table.
  
  Solution:
  
  Check OI001 Table: Use transaction code SE16 or SE16N to access the OI001 table and verify if the relevant entry for the material and company code exists. If it does not, you may need to create it.
  Maintain Material Master: Ensure that the material master data is correctly maintained. Check the purchasing and accounting views to ensure that all necessary information is filled out.
  Update Pricing: If there have been recent changes to pricing, ensure that these changes are reflected in the system. You may need to run a pricing update or re-evaluate the material pricing.
  Configuration Check: Review the configuration settings related to LIA and ensure that they are set up correctly for the company code and material in question.
  Consult Documentation: Refer to SAP documentation or consult with your SAP support team for specific steps related to your version of SAP and the configuration in your organization.
  
  Related Information:
  
  Transaction Codes: SE16/SE16N (Data Browser), MM03 (Display Material), ME23N (Display Purchase Order).
  Tables: OI001 (LIA Material Prices), MARA (General Material Data), MBEW (Material Valuation).
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  
  If the issue persists after following these steps, it may be beneficial to engage with your SAP support team or consult with an SAP expert for further assistance.