cancel
Showing results for 
Search instead for 
Did you mean: 

Bex exit variable problem..

Former Member
0 Kudos

the issue is that whenever iam executing the query , iam getting the following message.

@0A@ No value could be determined for variable ZVAR4. BRAIN 632

where zvar4 is my bex exit variable ..

I checked in RSRT , not able to understand any thing ..

I checked in some notes saying that we need toload and activate the 0comp_code and 0co_area . I have done that also but still facing the same problem ..

Can anybody please help me ..

Thanks in advance..

Accepted Solutions (0)

Answers (7)

Answers (7)

Former Member
0 Kudos

HI guys the problem is still there ,one thing is whenever iam executing the tcode CMOD --> components , i can see some RED LEDs in front of

Bex Variable Exit Coding

BI: Enhancements for Global Variables in Reporting

Might this be a problem ..

Thanks in advance..

Former Member
0 Kudos

HI

Have solved this problem? Can you post the solution to me?I'm having the same problem

thanks so much

regards

Scott

dkle
Participant
0 Kudos

This thread is old, but maybe this will still help users:

          The longtext of message BRAIN 632 does not always apply, because it refers to SAP Exit-Variables that aren't even used in most querys.

          Only the short text applies ("No value could be determined for variable &1").

This error occurs under the following two circumstances:

  1. The SAP Exit-variables are used in the query
  2. A customer Exit-variable is used, E_T_RANGE is returned empty and the variable is set to 'obligatory'.

If case no. 2 applies to you, possible solutions are

  1. ensure that E_T_RANGE is not returned empty or
  2. in the query designer, change variable setting to 'optional'
Former Member
0 Kudos

HI , tried debugging also , the code itself in not calling , before calling only it is creating problem . Iam giving the complete error message ..

No value could be determined for variable ZVAR4.

Message no. BRAIN632

Diagnosis

This error diagnosis is specific only to the variables 0P_FVAEX or

0P_CTPCA !

Termination message BRAIN 632 appears:

Could not determine value for variable 0P_FVAEX (or 0P_CTPCA).

System Response

1. Operation method of SAP-Exit-Variables 0P_FVAEX or 0P_CTPCA

With queries from the CO application, both SAP-Exit-Variables look for

an entry for 'controlling area'. With this controlling area from the

selection screen, the SAP-Exit-Variables program reads the attributes

for InfoObject 0CO_AREA (controlling area).

With queries from the FI application, the SAP Exit Variable 0P_FVAEX

looks for an entry for 'company code'. With this company code from the

selection screen, the SAP Exit Variables program reads the attributes

for InfoObject 0COMP_CODE (Company Code).

0P_FVAEX determines the fiscal year variant (attribute 0FISCVARNT) from

the attributes for 0CO_AREA (CO queries) or 0COMP_CODE (FI queries).

0P_CTPCA determines the currency type of the profit center local

currency (attribute 0CURTP_PCA) from the attributes for 0CO_AREA.

2. Cause of Error

The attributes for the controlling area (InfoObject 0CO_AREA) or company

code (InfoObject 0COMP_CODE) were not loaded into the BW system, or the

attributes for the controlling area are not active in the BW system.

Check whether this is the cause of the error in your BW system. the contents of table /bi0/mco_area or /bi0/mcomp_code using transaction

se16.

Application CO:

Check whether the attributes 'fiscal year variant' (field FISCVARNT) and

'profit center local currency currency type' (field CURTP_PCA) are

filled in the 'A' version (field OBJVERS) for the selected controlling

area. If the fiscal year variant in the OBJVERS = 'A' is empty, then the

error is with variable 0P_FVAEX. If the currency type of the profit

center's local currency in OBJVERS = 'A' is empty, then the error is

with variable 0P_CTPCA.

Application FI:

Check whether or not the attribute 'fiscal year variant' (field

FISCVARNT) is filled in the 'A' version (field OBJVERS) for the selected

controlling area. If the fiscal year variant is empty in OBJVERS= 'A',

then the error is with variable 0P_FVAEX.

Procedure

Using InfoSource 0CO_AREA, load the attributes for the controlling area

or company code into your BW system.

Afterwards, activate the attribute changes in your BW system. To do

this, use transaction rsa1, path 'Tools > Hierarchy/Attribute changes',

functions button 'InfoObject list'. Choose InfoObject 0CO_AREA or

0COMP_CODE from this list, and activate the attribute changes.

But i have already loaded the 0comp_code and oco_area and also activated.

Former Member
0 Kudos

Hi Alessandro

can u explain a bit on what u said , i dind't get that ..

Thanks..

Former Member
0 Kudos

Akash

insert in your customer exit code:

data flag.....

run the query.

the program is in loop until you don't fill your variable flag = x in debug mode

search the process in sm50, go to progam (window) and debug

alessandro

Former Member
0 Kudos

Hi guys iam putting the code ..

CASE I_VNAM.

WHEN 'ZVAR4'.

IF I_STEP = 2.

CLEAR L_S_RANGE.

LOOP AT I_T_VAR_RANGE INTO LOC_VAR_RANGE

WHERE VNAM = '0P_KEYDT'.

key_date = LOC_VAR_RANGE-LOW.

EXIT.

ENDLOOP.

LOOP AT I_T_VAR_RANGE INTO LOC_VAR_RANGE

WHERE VNAM = 'ZDAY'.

offset = LOC_VAR_RANGE-LOW.

offset = offset - 1.

EXIT.

ENDLOOP.

key_date = key_date - offset.

L_S_RANGE-LOW = key_date.

L_S_RANGE-SIGN = 'I'.

L_S_RANGE-OPT = 'EQ'.

APPEND L_S_RANGE TO E_T_RANGE.

ENDIF.

endcase.

Former Member
0 Kudos

akash,

try to debug your customer exit.

after when 'zvar4' insert:

data flag.

do.

if flag = 'x'.

exit.

endif.

enddo.

in sm50 for your process go to program debugg and post flag = x.

and see if your offset is correctly filled.

alessandro

Former Member
0 Kudos

Hi ,

I have written the code in cmod using enhance ment rsr00001 for my bex variable ZVAR4.

In the report i created the customer exit variable on Net due date and in the keyfigure problem i have restricted one keyfigure with this variable..

Former Member
0 Kudos

Hi Akash,

Can you please put the code here and also a brief explanation about the variable.

Former Member
0 Kudos

akash

how have you create your customer exit?

alessandro