How To Fix BOM621 - Reference date &1 exceeded - current date is used

SAP Error Message - Details

• Message type: E = Error

• Message class: BOM - BOMs (2)

• Message number: 621

• Message text: Reference date &1 exceeded - current date is used

What causes this issue?

If you leave the <LS>Valid from</> field empty, then, as a rule, the
system enters the sales order reference date as the default value.
The reference date of sales order &V1& is in the past.
If you go to this date in the navigation, changes that were carried out
after this date are not displayed in the order browser.

System Response

Instead, the system enters the current date in the <LS>Valid from
</> field, as the default value.

How to fix this error?

Use this default value when you want to see all changes with validity
date in the order browser that have been carried out up to the present
date.
If you want to see the development status of a BOM on another date,
overwrite the default value in the <LS>Valid from</> field.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message BOM621 - Reference date &1 exceeded - current date is used ?

  The SAP error message BOM621 ("Reference date &1 exceeded - current date is used") typically occurs in the context of Bill of Materials (BOM) processing. This error indicates that the reference date specified for a BOM is in the past, and as a result, the system defaults to using the current date for processing.
  Cause:
  
  Reference Date Exceeded: The reference date you are trying to use for the BOM is earlier than the current date. This can happen if the BOM is time-dependent and the validity period has expired.
  BOM Validity Period: Each BOM can have a validity period defined by a start and end date. If the current date is beyond the end date, the system will not consider that BOM valid for the current transaction.
  Incorrect Date Entry: The date entered in the transaction might be incorrect or not aligned with the expected date format.
  
  Solution:
  
  
  Check BOM Validity: Review the validity dates of the BOM in question. You can do this by navigating to the BOM in the SAP system and checking the validity period. If the BOM is no longer valid, you may need to create a new BOM or extend the validity of the existing one.
  
  
  Update Reference Date: If you have control over the reference date being used, ensure that it is set to a date that is not in the past. This may involve changing the date in the transaction or configuration settings.
  
  
  Create a New BOM: If the BOM is outdated and no longer relevant, consider creating a new BOM with the correct reference dates.
  
  
  Consult Documentation: Review SAP documentation or help files related to BOM management for additional insights on handling BOM validity and reference dates.
  
  
  System Configuration: If this issue is recurring and affects multiple BOMs, it may be worth checking the system configuration or consulting with your SAP Basis or technical team to ensure that there are no underlying issues with date handling in the system.
  
  
  Related Information:
  
  Transaction Codes: You can use transaction codes like CS03 (Display BOM) or CS02 (Change BOM) to view and modify BOM details.
  BOM Types: Understand the different types of BOMs (e.g., standard BOM, variant BOM) and their specific validity rules.
  SAP Notes: Check for any relevant SAP Notes that might address specific issues or bugs related to BOM processing and date handling.
  
  By following these steps, you should be able to resolve the BOM621 error and ensure that your BOMs are valid for the intended transactions.