Global official numbering: Input parameter incomplete Message no. 8A770

Dear Sir,
the following error is showing "Global official numbering: Input parameter incomplete Message no. 8A770" during the depot Billing.
even i created J1Ij which is working properply.
Moreover tht i have done a scenario with same material and same customer in excisbale plant where no error are throwing.
Thanks
Shibu Chandran

Check this thread
[error when creating delivery referenced by STO doc. from vl10b|error when creating delivery referenced by STO doc. from vl10b;
G. Lakshmipathi

Similar Messages

GLOBAL OFFICIAL NUMBERING INPUT PARAMETER INCOMPLETE

Hi Guru,
When i am trying to save the rush order(order type-SO) using transaction VA01 system giving message:
Global official numbering: Input parameter incomplete
Message no. ICC_NUMBERING770
Diagnosis
The system has discovered a statement which cannot be executed with the parameters defined for general document numbering.
This could be caused by any of the following:
1. Customizing for general document numbering is not complete.
2. There is a program error.
System Response
The transaction is terminated.
Procedure
Check Customizing for general document numbering.
Please help to resolve this issue.
Regards
Sandip

Which countries are implemented in your system?
Go to SPRO > Cross application components > General application functions > Cross application documnet numbering > ...
Here there are config for country specific requirements for official document numbering. You are missing something here. Again, this will be triggered only for the countries that you find in this menu.
Praveen.

ERROR:GLOBAL OFFICIAL NUMBERING INPUT PARAMETER INCOMPLETE

HI,
I FACED THIS ERROR WHILE IWAS DELIVERING A STOCK TRANSPORT ORDER THRU VL10D
PLEASE TELL ME THE COUNTER
I HAVE ALSO TRIED OFFICIAL DOCUMENT NUMBER RANGE BUT IT DIDN'T WORKED

hello
what is the relation between bi monitor and global indexing parameter as we here don't have bi accelerator
as my basis consultant is not able to figure out and if u could please ellaborate on this issue it would of immense help
bye n take care
mohit

Official Global Numbering Input Parameter Incomplete.

Dear all,
While creating Billing Document (with ref. Sale Order) there is error Message that " Official Global Numbering Input Parameter Incomplete" and screen terminated. Due to this problem, we unable to create the Invoice.
Kindly advise to sort out this issue.
Thanks & Regards,
Satyanarayana

Hi
Ashok, Thanks for the message number.
Thsi message appears when the
if i_BuKrs eq space or i_BuPla eq space or i_PostDate eq space.
i.e Compnay code or Posting date ro Business Place is Blank.
or
IF NOT i_bukrs IS INITIAL AND vbrk-bukrs <> i_bukrs
MESSAGE e770(8a) RAISING wrong_input_parameter.
i.e Compnay code is blank.
If you have done any changes or Enhancements in the Billing Document creation program , please check if the Program is correct or any values are not being transferred properly.
Please Take help of ABAPEr to resolve the isssue
Thanks & Regards
Kishore

Input-Parameter to message mapping missing

Hi,
I have an interface on 7.1 where i use a RFC lookup, and sets the channel using the parameter functionality. After upgrading to EHP 1, the parameter has gone missing on the production system. It is on Dev, but when I try to transport it again, it still does not appear. I get this error in SXMB_MONI: UndefinedParameterException: The input-parameter RFCChannel does not exist
Any ideas?
Kind regards
Mikkel

Check this SAP note 1307777.

Is the task-flow input parameter class value being ignored by the framework

hi
Although I don't remember where, I think I read or heard about the task-flow input parameter class value that it is "being ignored by the framework".
One example of this could be what is currently in the UI Shell sample application available
at http://www.oracle.com/technetwork/developer-tools/adf/uishellapp-134633.zip
It has in its task-flow in "flows\second.xml" an input parameter configured like
<task-flow-definition id="second">
    
    <input-parameter-definition id="__3">
      <name id="__2">tabContext</name>
      <value>#{pageFlowScope.tabContext}</value>
      <class>oracle.ui.pattern.dynamicShell.TabContex</class>
      <required/>
    </input-parameter-definition>
    
</task-flow-definition>Notice the missing "t" at the end of the class name "oracle.ui.pattern.dynamicShell.TabContex".
Still this task-flow configuration does allow to use expressions like "#{pageFlowScope.tabContext.selectedTabIndex}", which suggests that the class value is indeed "being ignored by the framework".
(see also forum thread "does the UI Shell sample break encapsulation in its task-flows"
at does the UI Shell sample break encapsulation in its task-flows )
All relevant references (bug numbers, documentation, blogs) explaining about this task-flow input parameter class value are welcome.
If no such references exist, maybe someone from Oracle can give some feedback.
many thanks
Jan Vervecken

fyi
The feedback below was posted in the forum message
at Re: does the UI Shell sample break encapsulation in its task-flows
Richard Wright wrote:
That appears to be a bug for which I am seeking confirmation.There is an enhancement request (i.e., 9377487) submitted over a year ago, that describes this behavior. It is listed as an ER as our documentation (e.g., Fusion Developer's Guide for Oracle ADF, online help ) does not specifically state that Java class for the input parameter definition is checked for type. Further anything using EL is untyped. So the expectation that types are enforced is somewhat puzzling to the development team.
However, there is an acknowledgment within circles of the development organization, that some might come to have this expectation. One trigger might be the definition itself. The other is the existence of a design time audit on the definition. For example, if the class is specified inaccurately (e.g., typo), there is an audit warning to report "not found."
Under consideration are a number of framework proposals to check for type without breaking backward compatibility or adding overhead to the production environment.
In the interim, the following recommendations are given.
Unless this breaks or can break your app in some way, no need exist for change. Nevertheless, if this is a real concern, write a test or consider a java assertion. By default, assertions are disabled at runtime. There is no need to override that default.I have been able to find enhancement request 9377487, "TASK FLOW PARAMETER VALUES NOT VALIDATED ACCORDING TO CLASS", on My Oracle Support. It currently has "Status 15 - To Internal (Oracle) Review" and "Updated 16-Dec-2010".
In the context of service request 3-4185839067 recently bug 12838099, "THE TASK-FLOW INPUT PARAMETER CLASS VALUE BEING IGNORED BY THE FRAMEWORK", has been filed and it currently still has "Status 16 - Bug Screening/Triage".
- about "... the expectation that types are enforced is somewhat puzzling to the development team ..."
Hmm, strange ... so what are people supposed to expect when there is an option to configure a class name for a task-flow input parameter?
regards
Jan

Log Error : Invalid Input Parameter %s for every SAP B1 Client

Hi Everybody,
in my company we have performed SAP B1 upgrade from 2007A to 8.81 PL07, in two steps upgrading first to PL04.
Everything is working fine for all our clients, we are able to post and work normally with the system.
The only annoying problem is an error message coming up every minute for every client in the log:
SQLMessage Error I Technical Invalid input parameter: %s # # MID=-1 BOID=-1 BO= UserID=manager C:\Program Files (x86)\SAP\SAP Business One\SAP Business One.exe Version=8.81.315 Area= PID=1316 TID=4340 D:\depot\BUSMB_B1\8.8_SP1_REL\SBO\8.8_SP1_REL\Application\__Engines\DBM\__DBMC_DataBase.cpp 9547
I couldn't find anything regarding this topic in the forum, only one similar post but unanswered.
We are using two server: one for the licence server and one for the database (the database server is clustered)
Does anyone have any idea about this? Has it ever happened to anybody?
Thanks for your help

Hi Julie,
it must be a triggered action from the system. The only problem is that log files grow very big, few mb every day, and it is a situation that's not very ideal. And also i don't want to turn them off because it is always a good resource for other errors.
It is very strange that SAP hasn't noticed this behaviour and there isn't any note available for the purpose.
Thanks for your help

Can I use Bulk Collect results as input parameter for another cursor

MUSIC            ==> remote MUSIC_DB database, MUSIC table has 60 million rows
PRICE_DATA ==> remote PRICING_DB database, PRICE_DATE table has 1 billion rows
These two table once existed in same database, but size of database exceeded available hardware size and hardware budget, so the PRICE_DATA table was moved to another Oracle database. I need to create a single report that combines data from both of these tables, and a distributed join with DRIVING_SITE hint will not work because the size of both table is too large to push to one DRIVING_SITE location, so I wrote this PLSQL block to process in small blocks.
QUESTION: how can use bulk collect from one cursor and pass that bulk collected information as input to second cursor without specifically listing each cell of the PLSQL bulk collection? See sample pseudo-code below, I am trying to determine more efficient way to code than hard-coding 100 parameter names into 2nd cursor.
NOTE: below is truly pseudo-code, I had to change the names of everything to adhere to NDA, but below works and is fast enough for my purposes, but if I want to change from 100 input parameters to 200, I have to add more hard-coded values. There has got to be a better way.
DECLARE
     -- define cursor that retrieves distinct SONG_IDs from MUSIC table in remote music database
     CURSOR C_CURRENT_MUSIC
     IS
    select distinct SONG_ID
    from MUSIC@MUSIC_DB
    where PRODUCTION_RELEASE=1
     /* define a parameterized cursor that accepts 100 SONG_IDs and retrieves
          required pricing information
     CURSOR C_get_music_price_data
               P_SONG_ID_001 NUMBER, P_SONG_ID_002 NUMBER, P_SONG_ID_003 NUMBER, P_SONG_ID_004 NUMBER, P_SONG_ID_005 NUMBER, P_SONG_ID_006 NUMBER, P_SONG_ID_007 NUMBER, P_SONG_ID_008 NUMBER, P_SONG_ID_009 NUMBER, P_SONG_ID_010 NUMBER,
               P_SONG_ID_011 NUMBER, P_SONG_ID_012 NUMBER, P_SONG_ID_013 NUMBER, P_SONG_ID_014 NUMBER, P_SONG_ID_015 NUMBER, P_SONG_ID_016 NUMBER, P_SONG_ID_017 NUMBER, P_SONG_ID_018 NUMBER, P_SONG_ID_019 NUMBER, P_SONG_ID_020 NUMBER,
               P_SONG_ID_021 NUMBER, P_SONG_ID_022 NUMBER, P_SONG_ID_023 NUMBER, P_SONG_ID_024 NUMBER, P_SONG_ID_025 NUMBER, P_SONG_ID_026 NUMBER, P_SONG_ID_027 NUMBER, P_SONG_ID_028 NUMBER, P_SONG_ID_029 NUMBER, P_SONG_ID_030 NUMBER,
               P_SONG_ID_031 NUMBER, P_SONG_ID_032 NUMBER, P_SONG_ID_033 NUMBER, P_SONG_ID_034 NUMBER, P_SONG_ID_035 NUMBER, P_SONG_ID_036 NUMBER, P_SONG_ID_037 NUMBER, P_SONG_ID_038 NUMBER, P_SONG_ID_039 NUMBER, P_SONG_ID_040 NUMBER,
               P_SONG_ID_041 NUMBER, P_SONG_ID_042 NUMBER, P_SONG_ID_043 NUMBER, P_SONG_ID_044 NUMBER, P_SONG_ID_045 NUMBER, P_SONG_ID_046 NUMBER, P_SONG_ID_047 NUMBER, P_SONG_ID_048 NUMBER, P_SONG_ID_049 NUMBER, P_SONG_ID_050 NUMBER,
               P_SONG_ID_051 NUMBER, P_SONG_ID_052 NUMBER, P_SONG_ID_053 NUMBER, P_SONG_ID_054 NUMBER, P_SONG_ID_055 NUMBER, P_SONG_ID_056 NUMBER, P_SONG_ID_057 NUMBER, P_SONG_ID_058 NUMBER, P_SONG_ID_059 NUMBER, P_SONG_ID_060 NUMBER,
               P_SONG_ID_061 NUMBER, P_SONG_ID_062 NUMBER, P_SONG_ID_063 NUMBER, P_SONG_ID_064 NUMBER, P_SONG_ID_065 NUMBER, P_SONG_ID_066 NUMBER, P_SONG_ID_067 NUMBER, P_SONG_ID_068 NUMBER, P_SONG_ID_069 NUMBER, P_SONG_ID_070 NUMBER,
               P_SONG_ID_071 NUMBER, P_SONG_ID_072 NUMBER, P_SONG_ID_073 NUMBER, P_SONG_ID_074 NUMBER, P_SONG_ID_075 NUMBER, P_SONG_ID_076 NUMBER, P_SONG_ID_077 NUMBER, P_SONG_ID_078 NUMBER, P_SONG_ID_079 NUMBER, P_SONG_ID_080 NUMBER,
               P_SONG_ID_081 NUMBER, P_SONG_ID_082 NUMBER, P_SONG_ID_083 NUMBER, P_SONG_ID_084 NUMBER, P_SONG_ID_085 NUMBER, P_SONG_ID_086 NUMBER, P_SONG_ID_087 NUMBER, P_SONG_ID_088 NUMBER, P_SONG_ID_089 NUMBER, P_SONG_ID_090 NUMBER,
               P_SONG_ID_091 NUMBER, P_SONG_ID_092 NUMBER, P_SONG_ID_093 NUMBER, P_SONG_ID_094 NUMBER, P_SONG_ID_095 NUMBER, P_SONG_ID_096 NUMBER, P_SONG_ID_097 NUMBER, P_SONG_ID_098 NUMBER, P_SONG_ID_099 NUMBER, P_SONG_ID_100 NUMBER
     IS
     select
     from PRICE_DATA@PRICING_DB
     where COUNTRY = 'USA'
     and START_DATE <= sysdate
     and END_DATE > sysdate
     and vpc.SONG_ID IN
               P_SONG_ID_001 ,P_SONG_ID_002 ,P_SONG_ID_003 ,P_SONG_ID_004 ,P_SONG_ID_005 ,P_SONG_ID_006 ,P_SONG_ID_007 ,P_SONG_ID_008 ,P_SONG_ID_009 ,P_SONG_ID_010,
               P_SONG_ID_011 ,P_SONG_ID_012 ,P_SONG_ID_013 ,P_SONG_ID_014 ,P_SONG_ID_015 ,P_SONG_ID_016 ,P_SONG_ID_017 ,P_SONG_ID_018 ,P_SONG_ID_019 ,P_SONG_ID_020,
               P_SONG_ID_021 ,P_SONG_ID_022 ,P_SONG_ID_023 ,P_SONG_ID_024 ,P_SONG_ID_025 ,P_SONG_ID_026 ,P_SONG_ID_027 ,P_SONG_ID_028 ,P_SONG_ID_029 ,P_SONG_ID_030,
               P_SONG_ID_031 ,P_SONG_ID_032 ,P_SONG_ID_033 ,P_SONG_ID_034 ,P_SONG_ID_035 ,P_SONG_ID_036 ,P_SONG_ID_037 ,P_SONG_ID_038 ,P_SONG_ID_039 ,P_SONG_ID_040,
               P_SONG_ID_041 ,P_SONG_ID_042 ,P_SONG_ID_043 ,P_SONG_ID_044 ,P_SONG_ID_045 ,P_SONG_ID_046 ,P_SONG_ID_047 ,P_SONG_ID_048 ,P_SONG_ID_049 ,P_SONG_ID_050,
               P_SONG_ID_051 ,P_SONG_ID_052 ,P_SONG_ID_053 ,P_SONG_ID_054 ,P_SONG_ID_055 ,P_SONG_ID_056 ,P_SONG_ID_057 ,P_SONG_ID_058 ,P_SONG_ID_059 ,P_SONG_ID_060,
               P_SONG_ID_061 ,P_SONG_ID_062 ,P_SONG_ID_063 ,P_SONG_ID_064 ,P_SONG_ID_065 ,P_SONG_ID_066 ,P_SONG_ID_067 ,P_SONG_ID_068 ,P_SONG_ID_069 ,P_SONG_ID_070,
               P_SONG_ID_071 ,P_SONG_ID_072 ,P_SONG_ID_073 ,P_SONG_ID_074 ,P_SONG_ID_075 ,P_SONG_ID_076 ,P_SONG_ID_077 ,P_SONG_ID_078 ,P_SONG_ID_079 ,P_SONG_ID_080,
               P_SONG_ID_081 ,P_SONG_ID_082 ,P_SONG_ID_083 ,P_SONG_ID_084 ,P_SONG_ID_085 ,P_SONG_ID_086 ,P_SONG_ID_087 ,P_SONG_ID_088 ,P_SONG_ID_089 ,P_SONG_ID_090,
               P_SONG_ID_091 ,P_SONG_ID_092 ,P_SONG_ID_093 ,P_SONG_ID_094 ,P_SONG_ID_095 ,P_SONG_ID_096 ,P_SONG_ID_097 ,P_SONG_ID_098 ,P_SONG_ID_099 ,P_SONG_ID_100
     group by
           vpc.SONG_ID
          ,vpc.STOREFRONT_ID
     TYPE SONG_ID_TYPE IS TABLE OF MUSIC@MUSIC_DB%TYPE INDEX BY BINARY_INTEGER;
     V_SONG_ID_ARRAY                         SONG_ID_TYPE                     ;
     v_commit_counter           NUMBER := 0;
BEGIN
     /* open cursor you intent to bulk collect from */
     OPEN C_CURRENT_MUSIC;
     LOOP
          /* in batches of 100, bulk collect ADAM_ID mapped TMS_IDENTIFIER into PLSQL table or records */
          FETCH C_CURRENT_MUSIC BULK COLLECT INTO V_SONG_ID_ARRAY LIMIT 100;
               EXIT WHEN V_SONG_ID_ARRAY.COUNT = 0;
               /* to avoid NO DATA FOUND error when pass 100 parameters to OPEN cursor, if the arrary
                  is not fully populated to 100, pad the array with nulls to fill up to 100 cells. */
               IF (V_SONG_ID_ARRAY.COUNT >=1 and V_SONG_ID_ARRAY.COUNT <> 100) THEN
                    FOR j IN V_SONG_ID_ARRAY.COUNT+1..100 LOOP
                         V_SONG_ID_ARRAY(j) := null;
                    END LOOP;
               END IF;
          /* pass a batch of 100 to cursor that get price information per SONG_ID and STOREFRONT_ID */
          FOR j IN C_get_music_price_data
                    V_SONG_ID_ARRAY(1) ,V_SONG_ID_ARRAY(2) ,V_SONG_ID_ARRAY(3) ,V_SONG_ID_ARRAY(4) ,V_SONG_ID_ARRAY(5) ,V_SONG_ID_ARRAY(6) ,V_SONG_ID_ARRAY(7) ,V_SONG_ID_ARRAY(8) ,V_SONG_ID_ARRAY(9) ,V_SONG_ID_ARRAY(10) ,
                    V_SONG_ID_ARRAY(11) ,V_SONG_ID_ARRAY(12) ,V_SONG_ID_ARRAY(13) ,V_SONG_ID_ARRAY(14) ,V_SONG_ID_ARRAY(15) ,V_SONG_ID_ARRAY(16) ,V_SONG_ID_ARRAY(17) ,V_SONG_ID_ARRAY(18) ,V_SONG_ID_ARRAY(19) ,V_SONG_ID_ARRAY(20) ,
                    V_SONG_ID_ARRAY(21) ,V_SONG_ID_ARRAY(22) ,V_SONG_ID_ARRAY(23) ,V_SONG_ID_ARRAY(24) ,V_SONG_ID_ARRAY(25) ,V_SONG_ID_ARRAY(26) ,V_SONG_ID_ARRAY(27) ,V_SONG_ID_ARRAY(28) ,V_SONG_ID_ARRAY(29) ,V_SONG_ID_ARRAY(30) ,
                    V_SONG_ID_ARRAY(31) ,V_SONG_ID_ARRAY(32) ,V_SONG_ID_ARRAY(33) ,V_SONG_ID_ARRAY(34) ,V_SONG_ID_ARRAY(35) ,V_SONG_ID_ARRAY(36) ,V_SONG_ID_ARRAY(37) ,V_SONG_ID_ARRAY(38) ,V_SONG_ID_ARRAY(39) ,V_SONG_ID_ARRAY(40) ,
                    V_SONG_ID_ARRAY(41) ,V_SONG_ID_ARRAY(42) ,V_SONG_ID_ARRAY(43) ,V_SONG_ID_ARRAY(44) ,V_SONG_ID_ARRAY(45) ,V_SONG_ID_ARRAY(46) ,V_SONG_ID_ARRAY(47) ,V_SONG_ID_ARRAY(48) ,V_SONG_ID_ARRAY(49) ,V_SONG_ID_ARRAY(50) ,
                    V_SONG_ID_ARRAY(51) ,V_SONG_ID_ARRAY(52) ,V_SONG_ID_ARRAY(53) ,V_SONG_ID_ARRAY(54) ,V_SONG_ID_ARRAY(55) ,V_SONG_ID_ARRAY(56) ,V_SONG_ID_ARRAY(57) ,V_SONG_ID_ARRAY(58) ,V_SONG_ID_ARRAY(59) ,V_SONG_ID_ARRAY(60) ,
                    V_SONG_ID_ARRAY(61) ,V_SONG_ID_ARRAY(62) ,V_SONG_ID_ARRAY(63) ,V_SONG_ID_ARRAY(64) ,V_SONG_ID_ARRAY(65) ,V_SONG_ID_ARRAY(66) ,V_SONG_ID_ARRAY(67) ,V_SONG_ID_ARRAY(68) ,V_SONG_ID_ARRAY(69) ,V_SONG_ID_ARRAY(70) ,
                    V_SONG_ID_ARRAY(71) ,V_SONG_ID_ARRAY(72) ,V_SONG_ID_ARRAY(73) ,V_SONG_ID_ARRAY(74) ,V_SONG_ID_ARRAY(75) ,V_SONG_ID_ARRAY(76) ,V_SONG_ID_ARRAY(77) ,V_SONG_ID_ARRAY(78) ,V_SONG_ID_ARRAY(79) ,V_SONG_ID_ARRAY(80) ,
                    V_SONG_ID_ARRAY(81) ,V_SONG_ID_ARRAY(82) ,V_SONG_ID_ARRAY(83) ,V_SONG_ID_ARRAY(84) ,V_SONG_ID_ARRAY(85) ,V_SONG_ID_ARRAY(86) ,V_SONG_ID_ARRAY(87) ,V_SONG_ID_ARRAY(88) ,V_SONG_ID_ARRAY(89) ,V_SONG_ID_ARRAY(90) ,
                    V_SONG_ID_ARRAY(91) ,V_SONG_ID_ARRAY(92) ,V_SONG_ID_ARRAY(93) ,V_SONG_ID_ARRAY(94) ,V_SONG_ID_ARRAY(95) ,V_SONG_ID_ARRAY(96) ,V_SONG_ID_ARRAY(97) ,V_SONG_ID_ARRAY(98) ,V_SONG_ID_ARRAY(99) ,V_SONG_ID_ARRAY(100)
          LOOP
               /* do stuff with data from Song and Pricing Database coming from the two
                    separate cursors, then continue processing more rows...
          END LOOP;
          /* commit after each batch of 100 SONG_IDs is processed */
          COMMIT;
          EXIT WHEN C_CURRENT_MUSIC%NOTFOUND; -- exit when there are no more rows to fetch from cursor
     END LOOP; -- bulk fetching loop
     CLOSE C_CURRENT_MUSIC; -- close cursor that was used in bulk collection
     /* commit rows */
     COMMIT; -- commit any remaining uncommitted data.
END;

I've got a problem when using passing VARRAY of numbers as parameter to remote cursor: it takes a super long time to run, sometimes doesn't finish even after an hour as passed.
Continuing with my example in original entry, I replaced the bulk collect into PLSQL table collection with a VARRAY and i bulk collect into the VARRAY, this is fast and I know it works because I can DBMS_OUTPUT.PUT_LINE cells of VARRAY so I know it is getting populated correctly. However, when I pass the VARRAY containing 100 cells populated with SONG_IDs as parameter to cursor, execution time is over an hour and when I am expecting a few seconds.
Below code example strips the problem down to it's raw details, I skip the bulk collect and just manually populate a VARRAY with 100 SONG_ID values, then try to pass to as parameter to a cursor, but the execution time of cursor is unexpectedly long, over 30 minutes, sometime longer, when I am expecting seconds.
IMPORTANT: If I take the same 100 SONG_IDs and place them directly in the cursor query's where IN clause, the SQL runs in under 5 seconds and returns result. Also, if I pass the 100 SONG_IDs as individual cells of a PLSQL table collection, then it also runs fast.
I thought that since the VARRAY is used via select subquery that is it queried locally, but the cursor is remote, and that I had a distribute problem on my hands, so I put in the DRIVING_SITE hint to attempt to force the result of query against VARRAY to go to remote server and rest of query will run there before returning result, but that didn't work either, still got slow response.
Is something wrong with my code, or I am running into a Oracle problem that may require support to resolve?
DECLARE
     /* define a parameterized cursor that accepts XXX number of in SONG_IDs and
      retrieves required pricing information
     CURSOR C_get_music_price_data
p_array_song_ids SYS.ODCInumberList
     IS
     select /*+DRIVING_SITE(pd) */
count(distinct s.EVE_ID)
     from PRICE_DATA@PRICING_DB pd
     where pd.COUNTRY = 'USA'
     and pd.START_DATE <= sysdate
     and pd.END_DATE > sysdate
     and pd.SONG_ID IN
          select column_value from table(p_array_song_ids)
     group by
           pd.SONG_ID
          ,pd.STOREFRONT_ID
V_ARRAY_SONG_IDS SYS.ODCInumberList := SYS.ODCInumberList();
BEGIN
V_ARRAY_SONG_IDS.EXTEND(100);
V_ARRAY_SONG_IDS( 1 ) := 31135 ;
V_ARRAY_SONG_IDS( 2 ) := 31140   ;
V_ARRAY_SONG_IDS( 3 ) := 31142   ;
V_ARRAY_SONG_IDS( 4 ) := 31144   ;
V_ARRAY_SONG_IDS( 5 ) := 31146   ;
V_ARRAY_SONG_IDS( 6 ) := 31148   ;
V_ARRAY_SONG_IDS( 7 ) := 31150   ;
V_ARRAY_SONG_IDS( 8 ) := 31152   ;
V_ARRAY_SONG_IDS( 9 ) := 31154   ;
V_ARRAY_SONG_IDS( 10 ) := 31156   ;
V_ARRAY_SONG_IDS( 11 ) := 31158   ;
V_ARRAY_SONG_IDS( 12 ) := 31160   ;
V_ARRAY_SONG_IDS( 13 ) := 33598   ;
V_ARRAY_SONG_IDS( 14 ) := 33603   ;
V_ARRAY_SONG_IDS( 15 ) := 33605   ;
V_ARRAY_SONG_IDS( 16 ) := 33607   ;
V_ARRAY_SONG_IDS( 17 ) := 33609   ;
V_ARRAY_SONG_IDS( 18 ) := 33611   ;
V_ARRAY_SONG_IDS( 19 ) := 33613   ;
V_ARRAY_SONG_IDS( 20 ) := 33615   ;
V_ARRAY_SONG_IDS( 21 ) := 33617   ;
V_ARRAY_SONG_IDS( 22 ) := 33630   ;
V_ARRAY_SONG_IDS( 23 ) := 33632   ;
V_ARRAY_SONG_IDS( 24 ) := 33636   ;
V_ARRAY_SONG_IDS( 25 ) := 33638   ;
V_ARRAY_SONG_IDS( 26 ) := 33640   ;
V_ARRAY_SONG_IDS( 27 ) := 33642   ;
V_ARRAY_SONG_IDS( 28 ) := 33644   ;
V_ARRAY_SONG_IDS( 29 ) := 33646   ;
V_ARRAY_SONG_IDS( 30 ) := 33648   ;
V_ARRAY_SONG_IDS( 31 ) := 33662   ;
V_ARRAY_SONG_IDS( 32 ) := 33667   ;
V_ARRAY_SONG_IDS( 33 ) := 33669   ;
V_ARRAY_SONG_IDS( 34 ) := 33671   ;
V_ARRAY_SONG_IDS( 35 ) := 33673   ;
V_ARRAY_SONG_IDS( 36 ) := 33675   ;
V_ARRAY_SONG_IDS( 37 ) := 33677   ;
V_ARRAY_SONG_IDS( 38 ) := 33679   ;
V_ARRAY_SONG_IDS( 39 ) := 33681   ;
V_ARRAY_SONG_IDS( 40 ) := 33683   ;
V_ARRAY_SONG_IDS( 41 ) := 33685   ;
V_ARRAY_SONG_IDS( 42 ) := 33700   ;
V_ARRAY_SONG_IDS( 43 ) := 33702   ;
V_ARRAY_SONG_IDS( 44 ) := 33704   ;
V_ARRAY_SONG_IDS( 45 ) := 33706   ;
V_ARRAY_SONG_IDS( 46 ) := 33708   ;
V_ARRAY_SONG_IDS( 47 ) := 33710   ;
V_ARRAY_SONG_IDS( 48 ) := 33712   ;
V_ARRAY_SONG_IDS( 49 ) := 33723   ;
V_ARRAY_SONG_IDS( 50 ) := 33725   ;
V_ARRAY_SONG_IDS( 51 ) := 33727   ;
V_ARRAY_SONG_IDS( 52 ) := 33729   ;
V_ARRAY_SONG_IDS( 53 ) := 33731   ;
V_ARRAY_SONG_IDS( 54 ) := 33733   ;
V_ARRAY_SONG_IDS( 55 ) := 33735   ;
V_ARRAY_SONG_IDS( 56 ) := 33737   ;
V_ARRAY_SONG_IDS( 57 ) := 33749   ;
V_ARRAY_SONG_IDS( 58 ) := 33751   ;
V_ARRAY_SONG_IDS( 59 ) := 33753   ;
V_ARRAY_SONG_IDS( 60 ) := 33755   ;
V_ARRAY_SONG_IDS( 61 ) := 33757   ;
V_ARRAY_SONG_IDS( 62 ) := 33759   ;
V_ARRAY_SONG_IDS( 63 ) := 33761   ;
V_ARRAY_SONG_IDS( 64 ) := 33763   ;
V_ARRAY_SONG_IDS( 65 ) := 33775   ;
V_ARRAY_SONG_IDS( 66 ) := 33777   ;
V_ARRAY_SONG_IDS( 67 ) := 33779   ;
V_ARRAY_SONG_IDS( 68 ) := 33781   ;
V_ARRAY_SONG_IDS( 69 ) := 33783   ;
V_ARRAY_SONG_IDS( 70 ) := 33785   ;
V_ARRAY_SONG_IDS( 71 ) := 33787   ;
V_ARRAY_SONG_IDS( 72 ) := 33789   ;
V_ARRAY_SONG_IDS( 73 ) := 33791   ;
V_ARRAY_SONG_IDS( 74 ) := 33793   ;
V_ARRAY_SONG_IDS( 75 ) := 33807   ;
V_ARRAY_SONG_IDS( 76 ) := 33809   ;
V_ARRAY_SONG_IDS( 77 ) := 33811   ;
V_ARRAY_SONG_IDS( 78 ) := 33813   ;
V_ARRAY_SONG_IDS( 79 ) := 33815   ;
V_ARRAY_SONG_IDS( 80 ) := 33817   ;
V_ARRAY_SONG_IDS( 81 ) := 33819   ;
V_ARRAY_SONG_IDS( 82 ) := 33821   ;
V_ARRAY_SONG_IDS( 83 ) := 33823   ;
V_ARRAY_SONG_IDS( 84 ) := 33825   ;
V_ARRAY_SONG_IDS( 85 ) := 33839   ;
V_ARRAY_SONG_IDS( 86 ) := 33844   ;
V_ARRAY_SONG_IDS( 87 ) := 33846   ;
V_ARRAY_SONG_IDS( 88 ) := 33848   ;
V_ARRAY_SONG_IDS( 89 ) := 33850   ;
V_ARRAY_SONG_IDS( 90 ) := 33852   ;
V_ARRAY_SONG_IDS( 91 ) := 33854   ;
V_ARRAY_SONG_IDS( 92 ) := 33856   ;
V_ARRAY_SONG_IDS( 93 ) := 33858   ;
V_ARRAY_SONG_IDS( 94 ) := 33860   ;
V_ARRAY_SONG_IDS( 95 ) := 33874   ;
V_ARRAY_SONG_IDS( 96 ) := 33879   ;
V_ARRAY_SONG_IDS( 97 ) := 33881   ;
V_ARRAY_SONG_IDS( 98 ) := 33883   ;
V_ARRAY_SONG_IDS( 99 ) := 33885   ;
V_ARRAY_SONG_IDS(100 ) := 33889 ;
    /* do stuff with data from Song and Pricing Database coming from the two
separate cursors, then continue processing more rows...
FOR i IN C_get_music_price_data( v_array_song_ids ) LOOP
. (this is the loop where I pass in v_array_song_ids
. populated with only 100 cells and it runs forever)
END LOOP;
END;

Build error: an input parameter is invalid

I am looking for help with a build error. I am getting the following error message when I try to build a project in 8.5.1:
Error 1 occurred at Open VI Reference in AB_Source_VI.lvclasspen_Reference.vi->AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.
=========================
NI-488: Command requires GPIB Controller to be Controller-In-Charge.
VI Path:
Tom Rhoads
Goodrich FUS
Vergennes, Vermont

Arducopter:
Did you check to see if the KB Hunter posted resolves the issue?
If you're opening a project in a newer version of LabVIEW, then there's a chance the mass compile tool might work. It will open and save all of the VIs within a specified folder. The tool is fairly self-explanatory, and you can access it from within LabVIEW by going to "Tools --> Advanced --> Mass Compile..."
Good luck!
Caleb Harris
National Instruments | Mechanical Engineer | http://www.ni.com/support

How can i dynamically select columns based on the input parameter?

I have an input parameter which takes single numeric value.
Based on this value i have to dynamically select table-columns .
For eg: if i have following fields in my table :
SEM_1
SEM_2
SEM_3 and SEM_4.
And if i give numeric input as 2 , then i have to select "SEM_2" column only.
if the input is 3 then i have to select "SEM_3" only and leave the rest of the columns.
how do i achieve this dynamic feature in the "Select ..... From...... table...." statement in the ABAP??

Hi,
you should try something like this.
TYPES: cond(72) TYPE c.
data: condtab TYPE TABLE OF cond,
condw type cond.
data: lv_field(30) type c value 'SEM_'.
write p_num to lv_field+4(1).
condw = lv_field.
append condw to condtab.
SELECT (CONDTAB) FROM table INTO.....
Kostas
Message was edited by:
Kostas Tsioubris

How to change data type of input parameter

Hi
In my procedure i declared the data type of "Value Date" Input parameter as Date where as in CR it is showing data type as "Date Time". Can any one please specify how to change to Date.
While prompting for input parameter in description it is showing message as
Please enter Date time in format"yyy-mm-dd hh:mm:ss" . To change the content selected "format field" option. But is there any way to change input parameter data type.
Please suggest how to change.
Thanks Sruthi

Hi Sruthi,
all you need to do on this is open the report go to the parameters, select the parameter that you wish to change and click "Edit". This will allow you to change thefield to a date rather than a date time.
Regards,
Noel

Regarding" Material PO text " with input parameter is PR requisition

Hi Experts,
I need to develop a ALV report in which the input parameter is PR requisition, Requisition date, Plant ,Purchase Group, Purchase organization
And I needed to get its corresponding u201Cmaterial PO Textu201D.
I am using the function module READ_TEXT with
goto me53n( purchase requisition) -
> text----->item_text->doubleclick->goto->header
id = 'B04'.
tname = '100000166000010'.
tdobject = 'EBAN'.
How do i display all the text in alv against the PR requisition, Requisition date, Plant ,Purchase Group, Purchase organization, PR item number PO number , Po date , PO item number
thanx.
Moderator message: please open only one thread per issue.
Edited by: Thomas Zloch on Jan 17, 2012 10:42 PM

lets say item text is 8-10 lines, you want to display that as well in the output? how much the user have to scroll for 10 PRs just think..
rather give them the report output without the item text and give them a hotspot. once they click hotspot, show them a popup for item text

How Insert the input parameter to database through Java Bean

Hello To All..
I want to store the input parameter through Standard Action <jsp:useBean>.
jsp:useBean call a property IssueData. this property exist in
SimpleBean which create a connection from DB and insert the data.
At run time when I click on submit button servlet and server also show that loggging are saved in DB.
But when I open the table in Access. Its empty.
Ms-Access have two fields- User, Pass both are text type.
Please review these code:
login.html:
<html>
<head>
<title>A simple JSP application</title>
<script language=javascript>
function f(k)
document.forms['frm'].mykey.value=k;
document.forms['frm'].submit();
</script>
<head>
<body>
<form method="get" action="tmp" name="frm">
Name: <input type="text" name="User">
Password: <input type="password" name="Pass">
<input type=hidden name="mykey" value="">
<input type="button" value="Submit" onclick="f('submit.jsp')">
<input type="button" value="Issue" onclick="f('issue.jsp')">
</form>
</body>
</html>LoginServlet.java:import javax.servlet.*;
import javax.servlet.http.*;
public class LoginServlet extends HttpServlet{
public void doGet(HttpServletRequest request, HttpServletResponse response)
throws ServletException{
try
String User=request.getParameter("User");
String Pass=request.getParameter("Pass");
co.SimpleBean st = new co.SimpleBean();
st.setUser(User);
st.setPass(Pass);
request.setAttribute("User",st);
request.setAttribute("Pass",st);
RequestDispatcher dispatcher1 =request.getRequestDispatcher("/"+request.getParameter("mykey"));
dispatcher1.forward(request,response);
catch(Exception e)
e.printStackTrace();
}SimpleBean.java:package co;
import java.util.*;
import java.io.*;
import javax.servlet.*;
import javax.servlet.http.*;
import java.sql.*;
import java.util.*;
public class SimpleBean
private String User="";
private String Pass="";
private String s="";
public SimpleBean(){}
public String getUser() {
return User;
public void setUser(String User) {
this.User = User;
public String getPass() {
return Pass;
public void setPass(String Pass) {
this.Pass = Pass;
public String getissueData() //method that create connection with database
try
System.out.println("Printed*************************************************************");
getUser();
getPass();
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
System.out.println("Loading....");
Connection con=DriverManager.getConnection("jdbc:odbc:simple");
System.out.println("Connected....");
PreparedStatement st=con.prepareStatement("insert into Table1 values(?,?)");
System.out.println("~~~~~~~~~~~~~~~~~~~~");
String User=getUser();
st.setString(1,User);
String Pass=getPass();
st.setString(2,Pass);
int y= st.executeUpdate();
System.out.println(y);
System.out.println("Query Executed");
con.commit();
con.close();
s= "Your logging is saved in DB ";
System.out.println("Your logging is saved in DB *****************");
return this.s;
catch(Exception e)
e.printStackTrace();
return "failed";
}submit.jsp:
This is Submit page
<html><body>
Hello
Student Name: <%= ((co.SimpleBean)request.getAttribute("User")).getUser() %>
<br>
Password: <%= ((co.SimpleBean)request.getAttribute("Pass")).getPass() %>
<br>
<jsp:useBean id="st" class="co.SimpleBean" scope="request"/>
<jsp:setProperty name="st" property="User" value="request.getParamaeter("Pass")"/>
<jsp:setProperty name="st" property="Pass" value="request.getParamaeter("Pass")"/>
<jsp:getProperty name="st" property="issueData"/>
<% st.getissueData(); %>
</body></html>web.xml:<web-app>
<servlet>
<servlet-name>one</servlet-name>
<servlet-class>LoginServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>one</servlet-name>
<url-pattern>/tmp</url-pattern>
</servlet-mapping>
<jsp-file>issue.jsp</jsp-file>
<jsp-file>submit.jsp</jsp-file>
<url-pattern>*.do</url-pattern>
<welcome-file-list>
<welcome-file>Login.html</welcome-file>
</welcome-file-list>
</web-app>Please Help me..

Dear Sir,
Accordingly your suggestion I check the SimpleBean class putting the constant values in this bean class.That is Sucessfully Inserted constant values in database.
Like for example..
myfirstjavabean.java:
package myfirstjava;
import java.io.*;
import java.sql.*;
public class myfirstjavabean
private String firstMsg="Hello world";
private String s="";
public myfirstjavabean()
public String getfirstMsg()
return firstMsg;
public void setfirstMsg(String firstMsg)
this.firstMsg=firstMsg;
public String getissueData() //method that create connection with database
try
System.out.println("Printed*************************************************************");
getfirstMsg();
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
System.out.println("Loading....");
Connection con=DriverManager.getConnection("jdbc:odbc:sampleMsg");
System.out.println("Connected....");
PreparedStatement st=con.prepareStatement("insert into Table1 values(?)");
System.out.println("~~~~~~~~~~~~~~~~~~~~");
String Msg=getfirstMsg();
st.setString(1,Msg);
int y= st.executeUpdate();
System.out.println(y);
System.out.println("Query Executed");
con.commit();
con.close();
s= "Your logging is saved in DB ";
System.out.println("Your logging is saved in DB *****************");
return this.s;
catch(Exception e)
e.printStackTrace();
return "failed";
}Vij.jsp:
<html>
<body>
<jsp:useBean id="st" class="myfirstjava.myfirstjavabean" scope="request" />
<jsp:getProperty name="st" property="firstMsg" />
<jsp:getProperty name="st" property="issueData" />
</body>
</html>These above example sucessfully inserted the Hello World message in database.
But which value I put user input at run time Its not inserted in database.
Which is my previous problem that is persist.
Please Help..

Input parameter setting when calling a DLL(Built from LabVIEW and a kind of VISA communication driver) in Teststand.

In labVIEW7.1 I wrote a COM port communications driver by using "VISA Write/Read". I put a string as the input of "VISA Write" and made it the input of the whole vi. Then I converted the vi into a DLL, which is called in Teststand3.1 by specifying DLL adapter. In "Edit C/C++ DLL Call" dialog, I pass a message of "60 6A 94 80 86 81" as the input parameter. My problem is I tried three kinds of methods to pass the message, see attached 1.jpg,2.jpg and 3.jpg. and found the first one sometimes doesn't work, the second work fine and the last doesn't work all time. I don't know why the first one and last one don't work well.
Thanks!
Jacky
Attachments:
31.jpg ‏38 KB
11.jpg ‏36 KB
21.jpg ‏49 KB

Hi Srinivas,
Just another note, I noticed that the Math Interface Toolkit version (MIT) 1.0 is not compatible with LabVIEW 7.1. You’ll need version 1.0.1. of the MIT toolkit in order for it to work with LabVIEW 7.1.
The LabVIEW 7.0 lvanlys.dll is also attached. I had to rename it with a .txt extension, so you’ll want to delete the extension.
Kileen
Attachments:
lvanlys.dll.txt ‏516 KB

Mapping Input Parameter renders mapping unable to be compiled or deployed

Hi there. I have an interesting issue I have not encountered before.
I can create a new mapping with a Mapping Input Parameter (just one parameter of type Integer), map this to a table column of the same type and the mapping compiles and deploys without any issues.
However, if I take an existing mapping (which already compiles and deploys without issues), add a Mapping Input Parameter to it (just one parameter of type Integer) and map this parameter through to a table column of the same type, when I compile the mapping I get a pop-up "Warehouse Builder Error" with a number 56 and a red cross. The mapping cannot generate any code and gives no explaination. Trying this on a different mapping causes the same issue but with a different number in the pop-up.
I have tried changing the parameter from integer to another data type and this makes no difference.
Removing the Mapping Input Parameter makes the mapping compilable and deployable again.
Am I missing something here ?
Thanks
Paul

Ok... this could be a bug, but I worked out how to resolve the issue.
To get the issue:-
1. Open a mapping which does not have a Mapping Input Parameter and compiles and deploys happily
2. Add a Mapping Input Parameter object, add an output attribute to it and map it to a table column.
3. Compile the mapping and you get a "Warehouse Builder Error" pop-up with a number, then a Validation Completed Successfully message. But no code can be generated and the mapping
cannot be deployed.
4. Slap your forehead and say "Doh!"
To fix the issue :-
1. Open the same mapping
2. Resynch the tables you mapped the Mapping Input Parameter to. The mapping now compiles and deploys ok.
3. Pat yourself on the back
cheers
Paul

Global official numbering: Input parameter incomplete Message no. 8A770

Similar Messages

Maybe you are looking for