Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

call transaction different thatn tcode in gui ?

I have the transaction PV1A

when I call this transaction in the gui I have the GOS object visible and the tcode also has other behaviours.

when I call PV1A from ABAP with bdcdata then the behaviour is quite different, GOS is no longer possible and other things also works differently than normal. anybody got a clue if I can let the tcode run as expected by the user ??

            WHEN 'PV1A'.
              PERFORM bdc_dynpro USING 'SAPLRHVA' '3000'.
              PERFORM bdc_field  USING 'BDC_OKCODE' '/00'.

              PERFORM bdc_field  USING 'HRVPVA-EVSRK' rs_selfield-value.
              PERFORM bdc_field  USING 'BDC_OKCODE' '=AEND'.

          ENDCASE.

          CALL TRANSACTION f_tcode USING bdcdata MODE 'E' UPDATE  'S'.
          COMMIT WORK.

kinnd regards

arthur de smidt

Tags:
replied

Did you consider using OPTIONS when doing the CALL TRANSACTION to set NOBINPT?

Rob

0 View this answer in context
Not what you were looking for? View more on this topic or Ask a question