Skip to Content
0
Former Member
Feb 18, 2006 at 01:31 PM

call transaction vs. batch input directly in VA01 (SAPLSTXX)

348 Views

Dear experts,

I create a sales order (VA01) with an z-program using either call transaction or batch input map. In case call transaction returns with sy-subrc NE 0 the bdc-data will

be sent to a batch input map.

If I send the bdc-data to the batch input map directly and start the map everything will be ok.

If I want to make call transaction the program stops when creating the material sales text for an item in program SAPLSTXX. I give the information to use dynpro no. 1100.

But via call transaction the system uses the dynpro no. 2101. That's why the text got lost because RSTXT-TXLINE is not defined at this dynpro.

Some code below:

*Steploop in SAPLSTXX via OSS-note 159738

PERFORM bdc_dynpr USING 'SAPLSTXX' '1100'.

PERFORM bdc_field USING 'RSTXT-TXPARGRAPH(02)' '*'.

PERFORM bdc_field USING 'RSTXT-TXLINE(02)' wa_inp-text.

PERFORM bdc_field USING 'RSTXT-TXPARGRAPH(03)' '*'.

PERFORM bdc_field USING 'RSTXT-TXLINE(03)' wa_inp-text2.

PERFORM bdc_field USING 'BDC_CURSOR' 'RSTXT-TXPARGRAPH(03)'.

PERFORM bdc_field USING 'BDC_OKCODE' 'EDFM'.

I use the parameter OPTIONS from l_opt at call transaction:

l_opt-dismode = 'E'.

l_opt-updmode = 'S'.

l_opt-cattmode = ' '.

l_opt-nobinpt = 'X'.

l_opt-nobiend = 'X'.

Other combinations for the parameters nobinpt and nobiend bring other symptoms and errors which are not desired.

Does anybody can give a hint why call transaction uses another dynpro than batch input?

Thanks