topic Re: call transaction in Application Development and Automation Discussions

call transaction

Former Member — Thu, 22 Feb 2007 17:00:23 GMT

Hi guys,

I have developed a dialog prog to ease user from inputs to transaction VA41. Now I have header data in Itab_1 and Position Data (only material number and supply quantity) in Itab_2.

see Itabs below:

Itab 1:

*Kopf data Struktur / interne Tabelle----

TYPES: BEGIN OF KOPF_DATA

,T_AUART LIKE VBAK-AUART "Verkaufsbelegart

,T_VKORG LIKE VBAK-VKORG "Verkaufsorganisation

,T_VTWEG LIKE VBAK-VTWEG "Vertriebsweg

,T_SPART LIKE VBAK-SPART "Sparte

,T_VSBED LIKE VBAK-VSBED "Versandbedingung

,T_WERKS LIKE T320-WERKS "Werke

,T_LGORT LIKE T320-LGORT "Lagerort

,T_VKBUR LIKE VBAK-VKBUR "Verkausbüro

,T_KUNNR LIKE VBAK-KUNNR "Kunden nummer (Debitor)

,T_BSTNK LIKE VBKD-BSTKD "Bestellnummer

,END OF KOPF_DATA

DATA: XT_KOPF_DATA TYPE STANDARD TABLE OF KOPF_DATA

,XH_KOPF_DATA LIKE LINE OF XT_KOPF_DATA

Itab_2:

*Position data Struktur / interne Tabelle----

TYPES:: BEGIN OF ITAB_POS "Tabelle zum Step-Loop

,MATNR LIKE VBAP-MATNR "Material

,KWMENG LIKE VBAP-KWMENG "zurueckgelieferte Menge

,END OF ITAB_POS

DATA: XT_POS TYPE STANDARD TABLE OF ITAB_POS.

DATA: XH_XTPOS LIKE LINE OF XT_POS.

I am not sure on how to get these datas into TA:VA41. Thinking of looping both tabs and then update or modify Database. Then call transaction 'VA41' and skip first screen.

Help

Black

Re: call transaction

Former Member — Thu, 22 Feb 2007 17:03:25 GMT

Hi,

I would suggest you could go for a transaction variant, instead of creating a brand new dialog program....

Then suppress the fields that you don't want to show..

And then create a transaction code with the transaction variant..

Check the transaction SHD0 for creating transaction variant.

Thanks

Naren

Re: call transaction

Former Member — Thu, 22 Feb 2007 17:14:09 GMT

Thanks Naren.

But my BOSS Wants it as Dialog !

Black

Re: call transaction

Former Member — Thu, 22 Feb 2007 19:21:40 GMT

you can try to use GuiXT to build easier transacitons,

OR you can build your own transaciton and then call VA41 using batch-input (call VA41 using bdcdata.), to do that run recording for VA41 first (SHDB transaction) it can help to determine proper sequence of screens & fields & it can generate a sample program.

Re: call transaction

Former Member — Thu, 22 Feb 2007 20:15:56 GMT

Hi,

One Option I can think is Calling at TCODe by skipping 1st window.. To do that set all mandatory fields of Tcode in PARAMETER ID set it and it will be available to Next screen

Hope this is what u want