ICR - No data selected according to the specified restrictions - FBICS3

[Former Member]

I am getting the above message when selecting open items. I know there are a lot of open items on the inter-company vendors and customers. Yesterday, seems things to be working fine. Not sure what has changed. Have you seen this? I am working in a sandbox environment so am not sure what else is going on that could impact this.

Edited by: Carol McChesney on Nov 4, 2008 1:21 PM

[Former Member · Accepted solution]

Thanks, Ralph.

After getting no results I tried everything I could.

Yes, I re-configured and even went as far as to use the deletes in the auxiliary programs. What exactly are these? is there any way to bring back the data at this point in a sandbox environment?

Many thanks,

Carol

[former_member572578 · Accepted solution]

Hello Carol,

I am afraid that there is no backup and restore functionality included...

Based on the information you have provided there is really nothing else I can think of. Please check whether you are up-to-date on the notes that are available at this point. Please note that some corrections also resolve issues that are not explicitly described as symptoms. Sometimes fixing one issue simply resolves others as well.

If things are still not working after applying the available corrections you should create a service ticket and we will help you through that channel...

Best regards,

Ralph

[Former Member · Accepted solution]

Thanks, Ralph.

I have requested Basis apply all notes in Support Pack 20 pertaining to ICR but there are 20 or more so they are balking. Not sure when they will complete. Many thanks.

Carol

[Former Member · Accepted solution]

Hi Ralph,

Basis only applied the following notes to our Rd2 client:

1242222

1165474 (pulls in 1071510)

1161993 (Also pulled in note 1151931)

1162287

1172591

1159776 (Also pulled in note 1078228 and 1138225)

1230649

1238735

1259675

And I have followed your steps for config from thread ICR Process 003 functionality.

However I am still getting message "No data selected according to the specified restrictions". Any suggestions, recommendations? I have again asked Basis to apply all the related notes from Support pack 20, but am not sure they will do.

Yes, FBIC032 indicates "Documents of Current Process." Table FBICRC003A has no entries after running FBICS3 and FBICA3.

Many thnaks,

Carol

[former_member572578 · Accepted solution]

Hello Carol,

Without looking at your system there is really nothing else I can think of. Please create a service ticket.

Best regards,

Ralph

[Former Member · Accepted solution]

Thanks, Ralph.

I created message 1028071 2008.

[Former Member · Accepted solution]

OSS confirmed notes had not been applied correctly. Once they were re-applied, working as expected. Many thanks,

Carol

[former_member572578]

Hello Carol,

As long as the customer/vendor open items are still open they should be selected. When you check FBIC032 is data source still *Documents of current process"? Was assignment of company code to company changed? Was the assignment of trading partner to the accounts deleted?

Best regards,

Ralph

[Former Member]

FYI ... I went through config steps again and get the following short-dump:

Interface "IF_EX_FB_ICRC_001" was changed at runtime.

What happened?

Error in ABAP application program.

The current ABAP program "CL_FBICRC_SERVICES============CP" had to be

terminated because one of the

statements could not be executed.

This is probably due to an error in the ABAP program.

Error analysis

Interface "IF_EX_FB_ICRC_001" was changed while the program was running.

Consequently,

inconsistencies occurred at runtime.

Program "SAPLFB_ICRC_SERVICES" uses the interface version 20081104182100.

Program "CL_FBICRC_SERVICES============CP" uses the interface version

20081104181659.

The internal session was started at 20081104182045.

Trigger Location of Runtime Error

Program CL_FBICRC_SERVICES============CP

Module type (METHOD)

Module Name SET_STATUS

[former_member572578]

Hello Carol,

This sometimes happens when something in customizing has changed. Usually it will not happen if you simply run the program again.

Best regards,

Ralph