Question:
Hey Guys,
I modified a particular query in Dev by adding variable ZBLINE_H which is derived from another variable ZNETDT_P (via Customer Exit). The query runs (and provides results) correctly in Dev. I now transported this query in the QA but am now getting the following error when I run the query:
Abort No values could be determined for variable ZBLINE_H.
Error specify a value for variable ZBLINE_H
Abort System error in program SAPLRRK0 and form APPEND_KHANDLE_1-01-
Following is what I compared between Dev and QA:
- I verified the Customer Exit program has been successfully transported to QA
- From the BeX analyzer, both the queries look the same
Any ideas? Where am I going wrong? I even retransported the queries several different times with different settings (In data flow afterwards; only necessary objects; etc.)
Appreciate any ideas at this point?
Sarah.
Answer:
Try debuging the variable in QA environment and see if it is actually getting populated from the other variable.
_________________
Ciao.
AQ
Answer:
Unfortunately we don't have authorization to do debuging in QA.
Sarah
Answer:
Hi,
Question:
whats the varible type it is.
is it missing any default value before its prcess.
why dont u check the Variable properties are matched (or ) not between QA and Developement system.
let us update with detail information
cheers
martin
Answer:
Martin,
Thanks for the reply. They are both char variables. ZBLINE_H is hidden variable based on Baseline date and variable ZNETDT_P is based on Net due date. ZNETDT_P is the driver variable of the query. ZBLINE_H is taking the value from ZNETDT_P to apply further filters. The query works fine in development. It is the problem I am having in QA after transporting it to QA.
TIA.
Sarah.
Answer:
Hi,
if ur version is higher than 3.0b the variable strcture has been changed and we need keep the default values for varible before they processed.
but am not sure this would be ur solution.
coud u please search in OSS with SAPLRRK0 and form APPEND_KHANDLE_1-01-
its showing list of notes for this program.
i dont have enough web access and come back later.
cheers
martin
Answer:
I had something similar and had quite a simple solution.
If you have changed an existing customer-exit then it can happen that the exit is not activated after transport.
Therefore you have to go in QA into transaction CMOD. There you de-activate and then re-activate the enhancement project.
Maybe that helps.
Best regards
Walter
Answer:
Walter,
In QA when I try to deactivate or activate the Project, it gives me a valid error that Changes to repository are not allowed. Did you actually get the system open for you in QA to deactivate and reactivate?
Sarah.
Answer:
Sarah,
I was having the same problem. As Walter mentioned, deactivate and then reactivate the project. For me, even though I got the change to repository not allowed, it still did the trick. Try the process Walter mentioned and then try running the report again. If you are still getting the error message, tell us how you transported the query and what version of BW are you on. Give us as much details as you can.
AQ
_________________
Ciao.
AQ
Answer:
Helo Sarah,
I have never reactivated the project itself but instead regenerated the query in transaction RSRT. You'll surely find the relevant button there.
If there are a lot of queries to be regenerated it may worth setting all the queries to be regenerated in the menu, in the 3rd or 4th column (sorry, I have no BW now).
The above processes are allowed in your system, surely.
Hope this helped,
gerist
Answer:
Thank you for your suggestions everyone. AQ and schoenwalter's suggestion on deactivating and reactivating worked.