on 2025 Mar 04 3:04 PM
We have installed all known applicable notes to enable RTI from our ECC system to IBP, and have configured everything in ECC and IBP per the help documentation. Data seems to flow after activating the model in ECC, and the data shows in the "Monitor bgRFC Queues" app within IBP, but the the queues show with a queue status of "Queue is locked". We can process records by starting the queue within the app, but this only processes a single unit, then goes to status "Queue is locked" again. We have to do this over and over for every unit of data.
Are we missing something to automatically trigger the starting of the bgRFC queues?
Request clarification before answering.
I created an OSS note, and they promptly found the solution to the problem. The settings in transaction CFC2 within ECC, for setting the parameters for the CIF users, had the debug setting of "R" set. This setting had been previously created from an APO implementation several years ago, that subsequently was abandoned, presumably set this way for troubleshooting purposes. When configuring for RTI, since the record already existed, the settings were not changed. Changing the value to blank, deleting open Queues in IBP, then reactivating the model in ECC, fixed the problem.
We we were not aware, nor was there any documentation stating that all queues would be blocked, and require manual triggering because of this setting.
Hopefully, if anyone else encounters this problem, they find this answer, and can solve their issue without all the trouble we were encountering!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi again @NodnarbG ,
In IBP (BGRFC queue) just click on the locked queue -> open it -> browse the IBP Application Log. There should be a clue of why the queue is getting blocked
(posting as answer in order to attach the snip).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi again @Andrei_Lupu,
Since the unit is not yet processed because of the "Unit locked" status, there is no information in the application log. It actually gives an error that the unit ID cannot be found.
Hi @NodnarbG, do you get the same error when trying to browse the first unit from the top of the queue (the one that has Unit Blocked status?). Usually this error is displayed to the ones that are under Unit Locked status (2nd+ unit from the queue). If yes, then I would suggest you raise an OSS note for SAP to have a look at your system setup.
| User | Count |
|---|---|
| 6 | |
| 5 | |
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.