Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: ISSR_TP - Message Class for Statutory Reporting
Message number: 723
Message text: No record exists in table &3 for company code &1, SR variant &2
The entry that you have selected for deletion usually corresponds to an
entry in system table &V3& that the system deletes automatically if it
exists. However, the corresponding data record for company code &V1& and
SR variant &V2& does not exist in system table &V3&.
You might have generated the Customizing table entries automatically in
the past, by copying an existing company code. In such cases, the system
does not generate entries in system table &V3&, and your system's
Customizing data is no longer consistent.
The data records that you have selected for deletion for company code
&V1& and SR variant &V2& are deleted.
Check the consistency of the Customizing settings.
To ensure data consistency, after copying a company code you should save
the Customizing settings again for the combination of company code/SR
variant in Customizing activity <DS:SIMG.ISSR_VC_MAACRE>Define
Identification Number Assignment</> or <DS:SIMG.ISSR_MAIN_05C>Activate
Statutory Reporting for Company Code</>: the system then generates
entries automatically in system table &V3& for the combination of
company code/SR variant created by copying the company code.
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.
ISSR_TP723
- No record exists in table &3 for company code &1, SR variant &2 ?The SAP error message ISSR_TP723 indicates that there is no record found in a specific table for the given company code and service request (SR) variant. This error typically arises in the context of SAP's Industry Solution for Service Management or similar modules where specific configurations or data entries are required.
Cause:
- Missing Configuration: The most common cause is that the necessary configuration for the specified company code and service request variant has not been set up in the system.
- Data Deletion: Records may have been deleted or not created due to a data migration issue or incorrect data entry.
- Incorrect Parameters: The parameters being used (company code, SR variant) may be incorrect or not matching the existing records in the database.
- Transport Issues: If the configuration was transported from another system, it may not have been transported correctly, leading to missing entries.
Solution:
Check Configuration:
- Go to the relevant configuration transaction (e.g., SPRO) and verify that the necessary entries exist for the specified company code and service request variant.
- Ensure that all required settings are properly configured.
Create Missing Records:
- If records are indeed missing, you may need to create them manually. This can often be done through the relevant transaction codes or configuration screens.
Verify Input Parameters:
- Double-check the parameters being used in the transaction or report that triggered the error. Ensure that the company code and SR variant are correct.
Transport Validation:
- If the configuration was recently transported, check the transport logs to ensure that all necessary objects were included and that there were no errors during the transport process.
Consult Documentation:
- Review SAP documentation or notes related to the specific module you are working with to ensure that all prerequisites and configurations are met.
Seek Help from SAP Support:
- If the issue persists after checking the above points, consider reaching out to SAP support for further assistance. They may provide insights based on the specific version and configuration of your SAP system.
Related Information:
By following these steps, you should be able to diagnose and resolve the error message ISSR_TP723 effectively.
Get instant SAP help. Sign up for our Free Essentials Plan.
ISSR_TP722
SR variant &1: closing date &2 is not permitted
What causes this issue? The period-end closing date &V2& that you assigned to SR variant &V1& is not valid: The new period-end closin...
ISSR_TP721
Fixed period-end closing could not be deleted
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
ISSR_TP724
Specified assignment of SR prod. cat. to PRFL subsection is not possible
What causes this issue? You have not specified a value for the <DS:DE.ISSR_UA>subsection</> of the premium reserve fund list.System Respo...
ISSR_TP725
Selected validity date & is within period-end closing
What causes this issue? The validity date &V1& that you have selected for transfer posting of statutory reporting data is within the last val...
Click on this link to search all SAP messages.