cancel
Showing results for 
Search instead for 
Did you mean: 

RSARCH_CONVERT_TO_ILM - No matching rule found for audit area bupa_dp

morten_nielsen
Active Contributor
0 Kudos

Hi

We are setting up ILM to control our data archiving in relation to the GDPR rule set.

Our current archive is placed in an SAP content server, and we will like to convert the archive to our ILM store using the RSARCH_CONVERT_TO_ILM report.

However, it seems that the conversion program can't find a matching rule in BUPA_DP for ILM object FI_ACCRECV - I keep getting the error "No matching rule found for audit area BUPA_DP of ILM object FI_ACCRECV".

I have gone through our ILM rules several times, and to me, they seem to be fine, and in accordance with the data we have in the Archive files.

So any ideas on how I can investigate this further would be very welcome, as will any remarks/question on how the rules have been customized.

All help/input on this issue will be very appreciated

Kind regards

Morten Hjorth Nielsen

Accepted Solutions (0)

Answers (9)

Answers (9)

morten_nielsen
Active Contributor

Hi

I raised an OSS message for this.

It seems that the reason the Company Code isn't working as a condition field because the table CVP_SORT isn't included in our archive files.

This is important because of the Customising in IRM_CUST_BS - "Value Determination f. Conditions Fields (indirect)" - where the condition field BUKRS is mapped to this table.

The field BS_COUNTRY_OF_BUKRS is working fine - at least for the FI portion of the archiving files, the problem is now how to handle the archived General and SD part of the Archiving object?

I guess we will have to change our rules so that we focus on Country, not Company code.

Regards

Morten

revathimp
Advisor
Advisor
0 Kudos

Hello Morten,

The value determination of condition fields and time reference is indirect way via the badi.

Check the badi implementation and see how the values are determined. The rules should have matching condition field values, else it will say not valid rule found.

Regards,

Revathi

morten_nielsen
Active Contributor
0 Kudos

Hi Revathi

Thanks for your input - and yes it sounds like the data doesn't match the conditions. I have tried to create a rule without any condition fields, this one works fine, and as soon as I add a condition on e.g. company code I get this error, even if I add a range that covers all of our company codes.

I have checked in ILMSIM as well, and here I'm getting a weird result - it seems to find a valid policy/rule - but the end result stays the same "no valid rule exist".

Regards

Morten

revathimp
Advisor
Advisor
0 Kudos

Hello Morten,

The reason for the error could be that the condition fields value does not match with the data set you are processing from the archive files.

Try to maintain a rule without any condition field value and only with retention periods, time reference, store value and check.

You can also check via simulation in transaction ILMSIM for the rules you have maintained.

Regards,
Revathi

morten_nielsen
Active Contributor
0 Kudos

Hi Chad, and thanks for the input

We are running on ECC 7.50 SP 13 (basis), and we are currently experiencing the issue in our test and Sandbox system.

When it comes to customizing, then not a lot, the only thing in this project was that we specified that we use a local ILM store service.

I have taken a look at the note - it seems quite relevant. I have forwarded it to our basis team and asked them to implement it - I will test it when I am back Monday

Regards

Morten

chad_sanders
Explorer
0 Kudos

Hi, Morten ... I found this note, 2634635, that may apply in this situation. Disregard if you have already seen/read it.

https://launchpad.support.sap.com/#/notes/2634635

chad_sanders
Explorer
0 Kudos

Hi, Morten:

Couple of questions that come to mind after reading this post ...

  1. What ECC version are you running?
  2. In which environment is this issue occurring?
  3. Was there any customizing done for this AO in SARA?
morten_nielsen
Active Contributor
0 Kudos

Thanks, Satya

I just tried - unfortunately with the same result - there must be something else wrong also

Regards

Morten

veesatya1975
Participant
0 Kudos

Hi,

From the picture, the time ref is mentioned as "End of retention".

it should be "Start of retention". you can change this & recheck.

Regards,

Satya