Input variables not available in i_step = 2

Hi Experts,
In my filter in the planning modeller I have three variables. 1. ZSY(Source Year) 2. ZTY(Target Year) and 3. ZCNO(Customer number). All three variables are input ready variables ie. Manual entry/Default value.
For a customer exit variable I need to read version using a fm. Here I need values inputted for all three variables in i_step = 2. In planning modeller I gave values for all three variables. But in i_step = 2 I only got ZSY and ZTY. I did not get ZCNO. Is there anything wrong in the way I did or is there any ohter alternative.
Please help.
Thanks in advance.
Jerry.

Hi Durgesh,
Thanks for the reply. I already checked that table in debugging mode. It contains only two variables.
The flow is like:- At first it enters i_step = 2 there are only ZSY and ZTY and after that when it enters in i_step = 3 it jumps automatically to i_step = 2 and now it contains ZCNO with its value. That is
1st time. i_step = 2 - ZCNO is not there in i_t_var_range
1st time. i_step = 3 - it jumps back to i_step = 2
2nd time i_step = 2(jumped from i_step = 3) now it contains ZCNO in i_t_var_range.
I would like to get the ZCNO in i_t_var_range when the first time i_step = 2 is called.
Thanking you,
Jerry
Edited by: jerryabap on Aug 3, 2011 7:00 AM

Similar Messages

Input variables not displayed in bex analyzer

Hello Experts ,
I am facing a problem .I am displaying a report on bex analyser 7.0 and i am entering some input variables.
But my problem is when the result is displayed in the analyser and i am trying to take a print out everythg is coming in the print preview except the input variable values which i have used.
And i have to show this printout to the client and i am clueless how to make those variables visible in my analyser so that i can take printouts.
Pls help me on this.
I will be greatfull.
Regards,
Suyash
Edited by: sarang bhalerao on Mar 20, 2009 11:05 AM
Edited by: sarang bhalerao on Mar 20, 2009 11:05 AM
Edited by: sarang bhalerao on Mar 20, 2009 11:05 AM

Please do not raise same posts across forums..
/thread/1278673 [original link is broken]
The above post is being deleted as duplicate..

JAVA_HOME Environment Variable "Not Available"

I have installed j2sdk 1.4.2_17 for Windows Server 2008 64 bit for an installation of ERP 6.0. I have installed this in the following directory:
C:\j2sdk14217x64
- I have the JAVA_HOME variable (User variable for Administrator and System variable) set to: C:\j2sdk14217x64
- I have the PATH system variable (System variable) set to: C:\j2sdk14217x64\bin
When running the prerequisite checker I get the following error:
"It is not recommended to use JDK version 1.4.2_10. Current version: JAVA_HOME not available."
When I run %JAVA_HOME% from the command line the system finds it. I'm not sure what the issue is here.

Hello,
Best to unistall JDK and reinstall latest one
There is a download page solely for SAP customers:
http://www.sun.com/software/javaforbusiness/sap_download.jsp
See notes
709140 Recommended JDK and VM Settings for the WebAS630/640/7.0
Note 716604 for the Sun JDK (Windows, Linux, Solaris)
regards,
John Feely

Process - xfaForm variable not available

Hi all,
I have a bit of a newbie problem. We have Livecycle (8.0.1) deployed and I'm trying to get up to speed on things so am working through the "Creating Your First LiveCycle ES Application" found in the Workbench help. I'm running into a problem defining variables for the process in that I don't seem to have the xfaForm variable type available.
Apparently I need to get the adobe-taskmanager-dsc component installed? However I can't seem to locate it - I understand the jar should be in the /deploy/ folder but isn't. Another thread on this forum suggests that it may be due to not having Process Management installed: http://forums.adobe.com/message/1366637 I do have a "LiveCycle Process Management ES" item in the "Services" section of the admin console yet the about page only lists
"LiveCycle Rights Management ES" under installed components.
Any ideas?
Thanks,
Andrew

Andrew,
Indeed, you do not have Process Management installed. The reason that you see this option in the Admin console is because the process engine is actually part of the foundation of LC ES used to execute service orchestrations as opposed to human-based workflows.
You need to install LC Process Management to get the bits you need. If you are licensed for the Process Management solution component, it would have been installed to your server. However, you need to make sure that Process Management is selected when you run Configuration Manager to ensure that the bits are deployed into the server runtime environment.

Standard Query Variables not available in Q

Hi All,
We are not planning to transport the queries from DEV but create them in directly in Q and P. But I am unable to see any of the standard variables in Q or P. Do we need to transport the variables from DEV(even the standard ones)? If so, can we transport all the available standard variables into Q as a set or do I need to collect all of them in the transport connection and follow thw same process which we use to transport the normal objects?
Best Rgds,
Nene.

Nene,
If you have authorization you can do that in P or Q. Well, asking for a request can be suppressed by basis team. But the best practice to activate them in dev and transport them to QA and prod. And still if the prod and QA systems are opened and client has no problem you can do that in respective systems. Basis people can make it not to ask for transport request and can make it save by default as a local object.
Activating and transporting them to target systems will no lead to inconsistencies in future transports related to these objects. Now its up to you to decide the mode....

Query Designer: "Set Offset For Variable" not available

Hi,
I want to restrict a character by using a variable with offset, but the needed function is disabled in context menu for different variables (customer exit, single value, multiple values, etc.). I have found a hint here, that this function only works with interval variables. Is this correct?

Hi,
1) For Customer Exit Variable: Offset Functionality will not work,
2) For Manual input Interval Varable: you can have the Offset, but the offset will work on upper limit only
Ex: if u execute the quey by giving the interval like 2 - 4; then in the report output u can see only 2, 3 months data means the offset is working on 4 i.e upperlimit,
3) For Multiple Single Values: No offset Functionalty
Thanks,
Regards
ReddYA

Entry Variable not available in Free char in Query?

Hi
I have to remove one of the entry variable in a query, its costing date and is mandatory variable; but it is not visible in Free characteristic to remove it.
Its one of the factory reports.
Any idea how to remove it?
Thanks in advance
Ishi

Hi Anup
The InfoObject Costing date is used in column in one of the KF. But the variable is not used anywhere.
I tried to create the same report in Query designer, and noticed that after creating the query, system automatically picks the variable as mandatory entry variable
Regards
Priti

Substituion variable not available as data source in "Open SQL"

Setup as follows:
right-click on server name->Edit->Variables:
all apps, all dbs, SQL_SOURCE, 3G.DEV
In app_A, if I open a rules file, then File-Open SQL, I can select SQL_SOURCE as a substitution variable.
In app_B, if I open a rules file, then File-Open SQL, substitution variables is greyed out and can't be selected.
Does anyone have any clues or hints on whats wrong? I have set both rules files the same as far as I can see.

That was my first thought, rebooted machine to no avail.
If in the server variables section, I explicitly define a variable for that app/database it's OK. So:
all apps,all dbs,SQL_SOURCE,3G.DEV
Only works for db_1 in the app. If I go:
app_1,db_1,SQL_SOURCE,3G.DEV
app_1,db_2,SQL_SOURCE,3G.DEV
That works.
My only solution therefore it would seem is to define the variable per db per app where needed?

Bind variables not available when overriding criteria item clause

Hello -
Using jdev 11.1.1.3.0. Using ADFBC.
In a view object I am overriding getCriteriaItemClause in order to produce a clause for a view criteria of the form
my_column in ( select a_column from a_table where a_field = :MyBindVariable )I have created the bind variable ("MyBindVariable") for my view object and checked the "Include bind variable accessors" box in the Java options panel for the view object. When I use the view object I call the setMyBindVariable method with a value before I call the execute method. However, when
I call the execute method it gives a JBO-27122 error.
oracle.jbo.SQLStmtException) JBO-27122: SQL error during statement preparation. Statement: << query here, with the appropriate where clause that refers to the bind variable >>
----- Level 1: Detail 0 -----
(java.sql.SQLException) Missing IN or OUT parameter at index:: 1I have tested this code by running the application module tester. With it I am:
1. Right-clicking on my view object and selecting "Operations"
2. Choosing the setMyBindVariable operation, providing a parameter value, and hitting the "Execute" button.
3. Choosing the getMyBindVariable operation, hitting the "Execute" button and verifying that I get the right value back.
4. Right-clicking on my view object and selecting "Re-execute query". I get the JBO-27122 error as described above.
2nd approach (this also didn't work): I have additionally tried creating the clause above using the bind variable value instead of the reference. In getCriteriaItemClause, I would call getMyBindVariable to get the bind variable value and construct the above clause this way:
my_column in ( select a_column from a_table where a_field = literal_value_stored_in_view_object_bind_variable )However, when I tried this approach, getMyBindVariable always returned null.
Is there some reason why the bind variable isn't "available" when executing the query even though I specifically set it?
Thank you for reading my question.

Have you seen this blog http://jobinesh.blogspot.com/2010/12/using-oraclejbodomainarray-with.html ?
And my extension to it http://tompeez.wordpress.com/2011/08/21/extending-viewcriteria-to-use-sql-contains-4 ?
Timo

Object variable not set (Error 91) in Input Enabled query

Hello,
I'm having the following issue. I have created an input enabled query and included it in a planning workbook. Every time I open the workbook or query, and I got to an input enabled cell, I get the error below:
Object variable not set (Error 91)
This client has not used planning workbooks before. The system is on 7.10 SP10 for Bex Analyzer and SAP Gui 7.10 Patch Level 13.
I'm not finding any relevant so far in SDN. Any help anyone can provide is greatly appreciated.
Thanks,
Senthil

Hello,
Just wanted to let you all know that this issue has been resolved after updating my SAP Gui to 7.2 Patch Level 4 (Patch Level 5 was causing some other issues so I decided to stay at Level 4).
Thanks,
Senthil

Contract Currency Field not available for input

Dear experts,
I am configuring RE-FX in SAP ECC 6.0 and when i try to create a contract with a currency different from the company code local currency, the contract currency field is not available for input even though in the field status, it is checked as available for input. I want to be able to use a currency for my contracts different from my local currency. Also, havent yet made any changes to the standard field status settings.
Any kind of advice would be appreciated
Many thanks

Hi Severina,
different currencies for RE-FX are introduced with Enhancement Package 2. Therefore you have to implement this enhancement package and activate the business function for Real Estate and the appropriate subfunction to be able to use different currencies.
Hope that this information is helpful for you.
Regards, Franz

Use of Input Variables in SQL-Queries Sometimes Not Possible

Only in simple SELECT-statements the use of input variables ([%0], [%1], etc.) work without problems.
In more complex queries the use of these variables is not possible (e.g. SELECT-statements with sub-queries, sometimes when UNION is used - but I couldn't find any general rule when the problems will arise; sometimes two different queries with the same query-structure behave in different ways when these variables are used).
In these cases the query is not executed - not even the input-window to enter values into the input variables is displayed. The query stops with some strange error-messages in the status line. These error-messages doesn't have any relation to the actual query - sometimes it refers to field-names never used in the query or refers to syntax error which do not exist.
If the input variables are replaced by constant values there are no problems so there can't be any syntax errors - the only difference is the presence or absence of input variables.
Example:
provided that the queries have a certain complexity
SELECT ...
FROM ... OINV Tx ...
WHERE ... Tx.DocDate >= [%0] ...
does not work,
SELECT ...
FROM ... OINV Tx ...
WHERE ... Tx.DocDate >= '1.1.2007' ...
works!
Does anybody have run into the same problem and now if it is a bug of SAP-BO or an error on behalf of the user? Does anybody know a way to correct the problem?
Thanks in advance!
Frank
By the way: Are there any rules where exactly input variables can be used in a query?
Only in SELECT-statements? Where there exactly?
In statements outside of SELECT?

Only SAP Partners Can access service.sap.com/notes, but I think it is possible to search in them from the customer portal as well.
Here are summary of the two notes mentioned before this:
730960:
<i>
The following query is an example for how to define variables in long
queries rather than using "Fixed Declares".
You need to use exactly the same template as follows, do not delete
"comments" from this query.
The only changes you need to do :
1. In the first and in the fifth rows you need to select the table to which you would like to relate the variable e.g. in this example, the variable is related to the table VPM1 - 'Payments to Vendors - Rows'.
2. In the fourth and in the eighth rows you need to select the field to which you would like to define the variables e.g. in this example, the variable is the field 'DueDate'.
/SELECT FROM [dbo].[VPM1] T0/
declare @fromdate as datetime
/* WHERE */
set @fromdate = /* T0.DueDate */ '[%0]'
/SELECT FROM [dbo].[VPM1] T1/
declare @tilldate as datetime
/* WHERE */
set @tilldate = /* T0.DueDate */ '[%1]'
select OVPM.docnum, VPM1.dueDate,VPM1.CheckNum, VPM1.Branch,
VPM1.BankCode, VPM1.CheckSum, OVPM.CardName,
case
when OPCH.docnum is null then VPM2.docEntry
else OPCH.docnum
end as 'docnum'
from OVPM INNER join VPM1 on OVPM.docnum = VPM1.docnum
left join VPM2 LEFT JOIN OPCH ON VPM2.DocEntry = OPCH.DocEntry
on OVPM.docnum = VPM2.docnum
where OVPM.Canceled = 'N' AND VPM1.DueDate >=@fromdate AND
VPM1.DueDate <=@tilldate
</i>
955295:
<i>
Using SAP Business One Survey Variables (parameters) in a 'Set' SQL Statement can give an error in the Query Generator.
For Example:
Declare @Num as numeric(2)
Set @Num = [%0]
Select T0.DocNum
From ORDR T0
Where DocNum = @Num
Other terms
query, SQL, parameter, survey, variable, query generator, set, declare, [%0], table, error, SAP Business One
Reason and Prerequisites
FAQ
Solution
In such cases you need to put in an SQL remark statement a reference field in the DB for the Survey Variable (any field).
For Example: (to make the above query work)
Declare @Num as numeric(2)
Set @Num = /* T0.DocNum */ [%0]
Select T0.DocNum
From ORDR T0
Where docnum = @Num
</i>

Japanese characters alone are not passing correctly (passing like ??? or some unreadable characters) to Adobe application when we create input variable as XML data type. The same solution works fine if we change input variable data type to document type a

Dear Team,
Japanese characters alone are not passing correctly (passing like ??? or some unreadable characters) to Adobe application when we create input variable as XML data type. The same solution works fine if we change input variable data type to document type. Could you please do needful. Thank you

Hello,
most recent patches for IGS and kernel installed. Now it works.

Logic Pro 9 - MOTU MK II inputs not available in channel strip

I usually use a MOTU 24 i/o as my main Logic Pro 9.1.5 audio interface. I'm trying to use a MOTU MK II and it is connected via firewire. It shows up fine in the Logic > Audio > core audio driver preference and is checked on. However the MKII in/outs are not available on Logic's channel strip inputs and outputs. Logic still shows the 24 i/o's even though the 24 i/o is not selected in audio preferences and is not even turned on.
I've reinstalled the latest MOTU drivers, trashed Logic's preferences and restarted my MacPro but it is still the same. Only the 24 i/o available in the channel strip input and output.
Is there a second audio i/o setting that I'm missing?
My Mic is registering OK in the MKII so I know it is getting a signal.
Thanks,
Richard

For some reason Logic is listing the 24 i/o inputs.
I've renamed the 828 Mk2 1 & 2 inputs to Vox 1 and Vox 2. The MK2 has 8 analog inputs plus two mic/line inputs for a total of ten audio inputs, not 14 as listed in the channel strip input drop down.
Audio registers in and out of the Mk2 but does not register in Logic's channel strip input. I just switched back to the 24 i/o to test and audio registers fine in Logic's channel strip input with the 24 i/o. Just not with the MK2 selected as the audio source.
I'm curious if anyone else has had this problem or if I'm missing an audio input setting somewhere.
Thanks,
Richard

Variable 4MKTHI01 (Planning area 4CRM0001) is not available

Hi All,
I have activated planning profiles and level from 000 client.
Now, when I try to open the planning level it says "Variable 4MKTHI01 (Planning area 4CRM0001) is not available"
Please reply, how to activate this variable 4MKTHI01 under the planning level 4MP70000 of planning area 4CRM001
Thanks
Santosh

Hi,
take a look into note 886388 and 1083129.
kind regards Michael

Input variables not available in i_step = 2

Similar Messages

Maybe you are looking for