Skip to Content

BEx variables accepting invalid values

Mar 16, 2017 at 11:27 AM


avatar image
Former Member


I have created several reports for EMEA and APAC region. I am facing issue with manual input variables in APAC region.

Ideally, if we enter wrong value for variable, check button should throw error/exception.

This exception is working fine in EMEA system but not working for APAC system.

if we click on check button, it doesn't throw any error or exception in APAC region.

Note - no message is suppressed using RSRT.

10 |10000 characters needed characters left characters exceeded
Former Member

Early reply will be appreciated as we need to move our APAC reports to production by end of next week.

* Please Login or Register to Answer, Follow or Comment.

1 Answer

Koen Hesters Mar 17, 2017 at 09:26 AM


When check, the system checks if the entry exist in the system.

When your Infoobject is set to check master data table, he checks if your entry exists in your SID - MD table.So you can try to clean out your MD, another solution is to set check if entry exists in INfoprovider. If it does not exist in the cube(s) it will throw the error.



Show 1 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Hello Koen,

Thanks for replying!

I compared the infoobjects of APAC and EMEA system both the systems have same settings for infoobjects.

e.g. - 0COMP_CODE has same settings in APAC and EMEA systems.Still why issue is there is APAC system?

Also, how to check if entry exist in infoprovider? I think this requires ABAP coding. EMEA system doesn't have any such ABAP logic written to check entry in infoprovider still variables work fine in EMEA.