How To Fix CRD_CUST113 - Effective access end time-spot was requested but it is initial

SAP Error Message - Details

• Message type: E = Error

• Message class: CRD_CUST - Credentialing: Messages for Editing Customizing

• Message number: 113

• Message text: Effective access end time-spot was requested but it is initial

What causes this issue?

An effective access end time-spot was supplied in the program, but it is
initial. This procedure is <ZH>not</> anticipated.

System Response

The current program is canceled.

How to fix this error?

Enter an effective access end time-spot.

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 CRD_CUST113 - Effective access end time-spot was requested but it is initial ?

  The SAP error message CRD_CUST113 indicates that there is an issue with the effective access end time for a specific spot (or condition) in the system. This error typically arises in the context of condition records, pricing, or access sequences in SAP, particularly in modules like Sales and Distribution (SD) or Material Management (MM).
  Cause:
  The error message "Effective access end time-spot was requested but it is initial" suggests that the system is trying to access a condition record that has not been properly defined or has an initial (blank) end time. This can occur due to several reasons:
  
  Missing Condition Records: The condition record for the specific pricing or access sequence may not have been created or may have been deleted.
  Incorrect Configuration: The configuration settings for the pricing procedure or access sequence may not be set up correctly.
  Data Inconsistency: There may be inconsistencies in the data, such as missing or incorrect validity dates for the condition records.
  Initial Values: The system is trying to retrieve a value that has not been initialized or set.
  
  Solution:
  To resolve the CRD_CUST113 error, you can take the following steps:
  
  
  Check Condition Records:
  
  Go to the relevant transaction (e.g., VK11 for creating condition records) and verify if the condition records exist for the specific pricing or access sequence.
  Ensure that the validity dates (start and end dates) are correctly set and that the end date is not left blank.
  
  
  
  Review Access Sequences:
  
  Check the access sequence configuration in the pricing procedure to ensure that it is correctly defined and that all necessary condition types are included.
  Make sure that the access sequence is properly assigned to the pricing procedure.
  
  
  
  Data Consistency:
  
  Run consistency checks to ensure that there are no inconsistencies in the condition records or related master data.
  Use transaction codes like SE16 or SE11 to check the relevant database tables for any missing or incorrect entries.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or help notes related to the specific error message for additional insights or specific steps to resolve the issue.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance, especially if this is a production environment.
  
  
  
  Related Information:
  
  Transaction Codes: VK11 (Create Condition), VK12 (Change Condition), VK13 (Display Condition).
  Tables: Check relevant tables such as KONV (Condition Records), Axxx (where xxx is the condition type), and others related to pricing and conditions.
  SAP Notes: Search for SAP Notes related to CRD_CUST113 for any known issues or patches that may address the problem.
  
  By following these steps, you should be able to identify and resolve the cause of the CRD_CUST113 error in your SAP system.