topic Re: error in call transaction in Application Development and Automation Discussions

error in call transaction

Former Member — Tue, 15 Nov 2005 17:08:10 GMT

i am trying to set parameter id and then pass those values to a qdl2 with call transaction skip first screen and end up with this error.

can anyone let me know why this error could occur.

Flow control: Entry SAPMQDQL, NEXT, * , 100 , , * is missing in T185

Message no. V0102

thanks

Re: error in call transaction

Former Member — Tue, 15 Nov 2005 17:16:13 GMT

are u populating all the require dfields in the first screen ??

set parameter if 'WRK' value 'the requiredval'.

call transaction 'VDL2' and skip first screen.

Re: error in call transaction

Former Member — Tue, 15 Nov 2005 17:19:22 GMT

yes all the req are passed. i can see them on the qdl2 screen and it gives the error here on the screen.

Re: error in call transaction

Former Member — Tue, 15 Nov 2005 17:25:54 GMT

Try the transaction first online and see if giving the plant and material number are sufficient for you to go to the next screen. If it is not working then something is not correct.

The message seems to be more like a missing configuration. T185 controls the screen sequence and so system is unable to find the next screen in the sequence after skipping the initial screen. This may also be caused by an error message. That is why test it online first and then set the parameters.

Are you setting the parameters WRK for plant and QLM for material?

Srinivas

Re: error in call transaction

Former Member — Tue, 15 Nov 2005 17:30:52 GMT

yes it works manually and depending on that i set the parameters. and it gives the error.

Re: error in call transaction

Former Member — Tue, 15 Nov 2005 17:35:02 GMT

Deepali,

Fill all the following Parameter IDs:

Plant : WRK

Material: QLM

Customer : QLK

Deepali, Check the Material that u r using the BDC. There can be more than one Inspection Plan. This may the problem.

This is the complete list of the parameters:

set parameter id 'QLD' field waQdqlsel-dynhead.

set parameter id 'WRK' field waQdqlsel-werks.

set parameter id 'QLM' field waQdqlsel-matnr.

set parameter id 'QLT' field waQdqlsel-plnty.

set parameter id 'QLN' field waQdqlsel-plnnr.

set parameter id 'QLZ' field waQdqlsel-plnal.

set parameter id 'QLF' field waQdqlsel-plnfl.

set parameter id 'QLV' field waQdqlsel-plnkn.

set parameter id 'QLL' field waQdqlsel-lifnr.

set parameter id 'QLK' field waQdqlsel-kunnr.

set parameter id 'QLH' field waQdqlsel-hersteller.

Thanks

Kam

Note: Allot points for all worthful postings

Message was edited by: Kam

Re: error in call transaction

Former Member — Tue, 15 Nov 2005 17:36:57 GMT

You may need Param id for Vendor too,if you are maintaining the material for different vendors.There is a popup with this combination coming up,if you dont specify the vendor & may be you are missing this.

Re: error in call transaction

RichHeilman — Tue, 15 Nov 2005 17:41:05 GMT

This is weird. I'm seeing the same.

Regards,

Rich Heilman

Re: error in call transaction

Former Member — Tue, 15 Nov 2005 17:44:05 GMT

do u get the same message after setting all the params.

Re: error in call transaction

Former Member — Tue, 15 Nov 2005 17:45:39 GMT

Hi Deepali,

See if you can configure V_T185 to have this entry. When you do a SKIP INITIAL SCREEN, system should know what is the next screen and that is what is missing in this case. If you don't want to do this, then you can prepare a simple BDCDATA table with the values of the initial screen and okcode to go to next screen and do a CALL TRANSACTION USING bdcdata MODE 'E'.

Srinivas

Re: error in call transaction

Former Member — Tue, 15 Nov 2005 17:47:49 GMT

Deepali,

I have used the all the Parameter Ids mentioned in the previous postings for the QDL2/3. I hope using the same in the your program may resolve the error.

Thanks

Kam

Note: Allot points for all the worthful postings

Re: error in call transaction

Former Member — Tue, 15 Nov 2005 17:52:15 GMT

Transaction VFBS will allow you to maintain the table.

Re: error in call transaction

RichHeilman — Tue, 15 Nov 2005 17:59:10 GMT

Ok, here ya go. Please add this line of code before the call transaction.

set parameter id 'QLD' field 'X'.

This worked in my system. I debugged the program and found that if it was begin called via call transaction that it branched off into a different form. It was checking for a value in this parameter id. This should work for you.

Here is my test program.

report zrich_0001.



set parameter id 'QLM' field '60001265'.
set parameter id 'WRK' field '0006'.
set parameter id 'QLD' field 'X'.

call transaction 'QDL2' and skip first screen.

Regards,

Rich HEilman

Message was edited by: Rich Heilman

Re: error in call transaction

Former Member — Mon, 21 Nov 2005 17:11:55 GMT

set parameter id 'qdl' solved the problem . But i get the same error when trying to do a BDC to QDL2. I am not able to record the transaction in SHDB as it gives out this error. Is there a work around for bdc also.

thanks in advance

Re: error in call transaction

RichHeilman — Mon, 21 Nov 2005 17:17:35 GMT

USe this program to start doing your recording. Once the recording is done, make sure to remove the SHDB part of the generated code.




report zrich_0001
       no standard page heading.

set parameter id 'QLD' field 'X'.
call transaction 'SHDB'.

Please award points for helpful answers. Thanks.

Regards,

Rich Heilman