Can't find 0FYTLFP OLAP Variable in InfoPackage Data Selection tab on 3.5

[Former Member]

On BW 3.5, when generating an InfoPackage with the datasource as Purchasing Data(80PUR_C01), under Data Selection tab, for the InfoObject 0FISCPER, I selected 7 (OLAP variables)for the Type column, then click the button next to it and under the column of Details for Type to bring up a window, but when expending the OLAP Variable field list, can't find the following value in the list which shows up on BW 3.1:

0FYTLFP 0FISCPER Cumulated to Last Fiscal Year/Period (SAP Exit)

How to make the above value show up in the OLAP Variable list? I thought maybe the variable 0FYTLFP needs to be installed in Business Contents, but there is no variable object type in Business Content. It sounds like a SAP Exit, but how to make the SAP Exit value show up on BW 3.5?

Thanks for everyone's input!

[Former Member · Accepted solution]

Hi Kevin,

Use 0FPER OR 0P_FPER instead.

For details see OSS Note #199014 - "Tips & tricks with variables II".

A note #121291 - "Tips and tricks for the use of variables" may be helpful also.

Best regards,

Eugene

[Former Member · Accepted solution]

hey Eugene,

I am not sure you are using what version of BW? On BW 3.5, there are three variable list:

1. 0CMONTH 0CALMONTH Current Calendar Month

2. 0CML12LM 0CALMONTH Last 12 Months Excluding the Current Month

3. 0S_RQMRC 0REQUID Most Current Data

There is no either 0FPER OR 0P_FPER which you specified. I think 2nd one 0CML12LM would be my choice and I've selected it already. But tell you one strang thing that for this OLAP Variable field, I can still type in the variable 0FYTLFP into this field even if it doesn't exist in the list on BW 3.5 and I can save the InfoPackage, when I come back to open it, 0FYTLFP is still there! Do you think that would work on BW 3.5 that if this variable I typed in does NOT exist in the available list?

Thanks

Message was edited by: Kevin Smith

[Former Member · Accepted solution]

Hi Kevin,

These vars are for fiscal period, not 0CALMONTH. What you choose is your preference. Restricting month is easy. For fiscal periods it's a little trickier.

Have you read the first note, the part of defining cumulative values?

Best regards,

Eugene

[Former Member · Accepted solution]

hey Eugene,

Wow, your response is so fast when I modified my previoius post! Please read my previous post with what I modified. Also btw, I have read the OSS Note you mentioned. I'd be appreicated if you can give me an example on how to use this to reflect the following:

0FYTLFP 0FISCPER Cumulated to Last Fiscal Year/Period (SAP Exit)

This variable sounds like a all the previous periods until last period. But tell you one strang thing that for this OLAP Variable field, I can still type in the variable 0FYTLFP into this field even if it doesn't exist in the list on BW 3.5 and I can save the InfoPackage, when I come back to open it, 0FYTLFP is still there! Do you think that would work on BW 3.5 that if this variable I typed in does NOT exist in the available list?

Thanks

Message was edited by: Kevin Smith

[Former Member · Accepted solution]

Kevin,

I cannot give you an example because fisc periods depend on fiscal year variants.

About 0FYTLFP and 0FPER - I see them in the list when try to choose variables in the infopackage.

Whether it is in the system or not you can check in BEx. Open/create a query on the infoprovider where fiscal period exists. In the left part of the dimensions find 0FISCPER and look for existing variables for it.

Best regards,

Eugene

[Former Member · Accepted solution]

hey Eugene,

You didn't answer my question that what version of BW are you using to see the list. I can see 0FYTLFP and 0FPER on BW 3.1, but not in the list of BW 3.5. But even if they are not in the list, but I can still type these two variables into this OLAP Variable field and save the InfoPackage, and whenever I get back, I can still see these two variables in this field even if they are not listed in the keyword list, do you think that will work?

Thanks

[Former Member · Accepted solution]

Hi Kevin,

I can see these vars in two 3.5 systems.

Any chance that you just didn't find them?

When you choose a var in a scheduler, it accepts any name.

Just try to see it in BEx, as I wrote.

Or execute infopackage. If there is no such a var in the system, you'll get an error message "BEx variable XXXXX could not be evaluated".

Best regards,

Eugene

[Former Member · Accepted solution]

hey Eugene,

No, Can't find 0FYTLFP on BW 3.5 in the list, but can still type in and save it though.

Thanks

[Former Member · Accepted solution]

Hi Kevin,

Eugene is right. We are on BW3.5 and both variables exist in our system. You can verify the variable by any of the two ways Eugene has stated i.e. either using BEx or executing the variable. The other best way is goto infopack give the 7 for OLAP Variable, Now write the variable name and Fiscal Year Variant Name and Press Check (F6). If the variable exist in the system it will display its value in the table below else it will throw an error as "BEx variable var_name could not be evaluated - No error message".

If you could not find this variable then you can define your own variable for the same thing.

Regards,

Rohit

[Former Member · Accepted solution]

hey Rohit,

Besides the three variable values in the list on BW 3.5, now I find a new one in the list, called "0E_ROLE 0SR_ROLE Role (SAP Exit)", I have no idea why this one shows up now. Now all the four variables in the list are:

1. 0CML12LM 0CALMONTH Last 12 Months Excluding the Current Month

2. 0CMONTH 0CALMONTH Current Calendar Month

3. 0E_ROLE 0SR_ROLE Role (SAP Exit)

4. 0S_RQMRC 0REQUID Most Current Data

0FYTLFP is still not in the list! We can't try to create BEx query since our BW 3.5 system is just installed and we have not got to the step to ceate a query. I try the 2nd way you suggested by pressing F6 on this variable with the typed in value 0FYTLFP, get the following msg "BEx variable 0FYTLFP could not be evaluated - No error message", that means it would not work on BEx query as well, right?

What could be the reason that we can't see 0FYTLFP variable in our new installed BW 3.5? Do you think our BASIS missed installing sth?

Thanks

Message was edited by: Kevin Smith

[Former Member · Accepted solution]

Hi Kevin,

As you said that message means this variable is not in the system.

Also you are saying now the fourth variable is visible, this means either some process of installation is still going on or BASIS missed something. Check on the OSS if they have something more on this.

I forgot to ask, on which service pack you are? Also is the BEx working properly.

Regards,

Rohit

Message was edited by: Rohit Bhargava