Do you have any question about this error?
Message type: E = Error
Message class: LRM_RULE_EXEC - Runtime
Message number: 647
Message text: BOR object Customizing for destroying attachments missing for ILM obj. &1
The BOR object Customizing for determining the object instance keys for
the destruction of attachments is unavailable.
Processing of the current object instance is terminated.
Check the settings in the dialog window <ZK>Mapping BOR Object Type for
Destroying Attachments</> of the <ZH>Object Category-Specific</>
<DS:TRAN.IRM_CUST_BS>Settings</> for ILM object &V1&.
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.
LRM_RULE_EXEC647
- BOR object Customizing for destroying attachments missing for ILM obj. &1 ?The SAP error message LRM_RULE_EXEC647 indicates that there is a missing configuration for the BOR (Business Object Repository) object related to the destruction of attachments in the context of Information Lifecycle Management (ILM). This typically occurs when the system is trying to execute a rule for the destruction of data, but it cannot find the necessary customizing settings for handling attachments associated with the specified ILM object.
Cause:
- Missing Customizing Settings: The error suggests that the necessary customizing for the BOR object related to the destruction of attachments is not defined in the system.
- Incorrect Configuration: There may be an incorrect or incomplete configuration in the ILM settings that prevents the system from processing the destruction of attachments.
- Missing Authorization: Sometimes, the user executing the process may not have the necessary authorizations to access the required customizing settings.
Solution:
Check Customizing Settings:
- Go to the ILM customizing transaction (usually
SIMG
orSPRO
) and navigate to the relevant ILM settings.- Ensure that the BOR object for the destruction of attachments is properly configured. This may involve defining the rules for how attachments should be handled during the destruction process.
Define BOR Object:
- If the BOR object is missing, you may need to create or define it in the system. This can involve specifying how attachments are linked to the ILM object and what actions should be taken during destruction.
Review ILM Rules:
- Check the ILM rules that are set up for the specific object (
&1
in the error message). Ensure that the rules are correctly defined and that they reference the appropriate BOR object for attachments.Authorization Check:
- Verify that the user executing the process has the necessary authorizations to access and modify the ILM customizing settings.
Consult Documentation:
- Refer to SAP documentation or notes related to ILM and BOR objects for specific guidance on how to set up the necessary configurations.
SAP Support:
- If the issue persists after checking the above points, consider reaching out to SAP support for further assistance. They may provide specific notes or patches that address the issue.
Related Information:
SIMG
, SPRO
, and others related to ILM configuration.By following these steps, you should be able to identify and resolve the issue related to the error message LRM_RULE_EXEC647.
Get instant SAP help. Start your 7-day free trial now.
LRM_RULE_EXEC646
Error while determining BOR object instance key for attachments
What causes this issue? An error occurred while determining the BOR object instance key for destroying attachments in ILM object &V1&. The er...
LRM_RULE_EXEC645
Job for session &1 could not be completed
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
LRM_TADIR005
Object &1 is locked in multiple requests &2 and &3
What causes this issue? Object directory entries corresponding to the ILM object are locked in different transport requests. Object directory entries...
LRM_TADIR006
Object &1 is locked in request &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.