How To Fix AJ731 - Access date for customer-defined access procedure is missing

SAP Error Message - Details

• Message type: E = Error

• Message class: AJ - Billing program

• Message number: 731

• Message text: Access date for customer-defined access procedure is missing

What causes this issue?

In operand &v1&, <DS:DE.SELCONTROL>access control</> for the
customer-defined access date was selected. However, a valid date could
not be determined that can be used with operand access. The BAdI was
either not activated or an error has occurred in the BAdI specification.

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

System Response

How to fix this error?

Check that the BAdI ISU_BI_SELCONTROL has been correctly implemented and
activated.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message AJ731 - Access date for customer-defined access procedure is missing ?

  The SAP error message AJ731, which states "Access date for customer-defined access procedure is missing," typically occurs in the context of SAP's pricing and access sequence configuration. This error indicates that the system is unable to find a valid access date for a custom access procedure that has been defined in the pricing configuration.
  Cause:
  
  Missing Access Date: The primary cause of this error is that the access date for the custom access procedure has not been defined or is missing in the configuration.
  Incorrect Configuration: There may be an issue with how the access sequence or condition records are set up, leading to the system not being able to retrieve the necessary access date.
  Data Inconsistency: There could be inconsistencies in the data related to the condition records or the access sequence that prevent the system from determining the access date.
  
  Solution:
  
  
  Check Access Sequence Configuration:
  
  Go to the transaction code V/07 (Access Sequences) and verify the configuration of the access sequence associated with the pricing procedure.
  Ensure that the access sequence includes the necessary fields and that the access date is properly defined.
  
  
  
  Review Condition Records:
  
  Use transaction code VK11 (Create Condition) or VK12 (Change Condition) to check the condition records related to the custom access procedure.
  Ensure that the condition records have valid access dates and that they are active.
  
  
  
  Maintain Access Date:
  
  If the access date is missing, you may need to create or update the condition records to include the appropriate access date.
  Ensure that the access date is set correctly in the condition records to avoid this error.
  
  
  
  Check for Custom Enhancements:
  
  If there are any custom enhancements or modifications in the pricing logic, review them to ensure they are not interfering with the access date retrieval.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to pricing procedures and access sequences for any additional guidance or known issues.
  
  
  
  Testing:
  
  After making the necessary changes, perform tests to ensure that the error no longer occurs and that the pricing is calculated correctly.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  V/07: Access Sequences
  VK11: Create Condition
  VK12: Change Condition
  VK13: Display Condition
  
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered and resolved similar issues.
  
  By following these steps, you should be able to identify the cause of the AJ731 error and implement a solution to resolve it.