topic Re: Transaction help. in Application Development and Automation Discussions

Transaction help.

Former Member — Tue, 29 Nov 2005 17:02:05 GMT

I all.

I have a problem with a custom transaction that is a copy of standard transaction md04. the problem is:

first screen, I put data and press enter, and leave transaction. I debug the original trax,perform the last module in 'PROCESS AFTER INPUT' and go to other dynpro. the custom trax perform the last module in 'PROCESS AFTER INPUT' and leave transaction. Where i can check for resolve this problem? thank you.

Re: Transaction help.

Former Member — Tue, 29 Nov 2005 17:05:50 GMT

Fabrizio Ballante

1. Check whether u have correct PF Status defined????

2. Make sure of the OkCodes for the Buttons?????

Thanks

Kam

Re: Transaction help.

Former Member — Tue, 29 Nov 2005 17:07:04 GMT

Hi Check the PAI in debug mode, any checks they are performing.

regards

vijay

Re: Transaction help.

Former Member — Tue, 29 Nov 2005 17:08:42 GMT

Did you copy the Full transaction .

Check it once.

regards

vijay

Re: Transaction help.

Former Member — Tue, 29 Nov 2005 17:10:26 GMT

In the PAI the program might check if the current programn is in fact the standard one.

Re: Transaction help.

Former Member — Tue, 29 Nov 2005 17:12:42 GMT

for the ps status i have copied the status that worked fine in standard trax.

for the ok code, there is ok code in the element list:

OK-CODE OK 0 0 20 20 1 OK.

Re: Transaction help.

Former Member — Tue, 29 Nov 2005 17:29:07 GMT

The PAI modules(and I think the entire trax) is the same in old system 4.5 and the new system 4.7 but it work fine in the old system, I wrong previously, not is a copy of standard trax, but is a copy of custom trax of old system in a new system.

Re: Transaction help.

Former Member — Tue, 29 Nov 2005 17:30:48 GMT

md04 calls screen 300, it contains subscreens

it contains calls to subscreens like:

CALL SUBSCREEN include300 INCLUDING 'SAPMM61R' sub300.

refering to the standard programs, you got to have in account this kind of modifications, if they are needed or not

Re: Transaction help.

Former Member — Tue, 29 Nov 2005 17:36:24 GMT

Yes Martins, i seen them, but there isn't in the trax in old system, but work fine, I dont think that the problem is this call subscreen.

Re: Transaction help.

Former Member — Tue, 29 Nov 2005 17:41:23 GMT

In the PAI logic of the screen 300 of program SAPMM61R, there is a module SET_TABNR. Here is the code from it.


module set_tabnr input.

  case sy-tcode.
    when 'MD04'.
      move tabnr300 to tab_nr.
    when 'MD07'.
      move tabnr210 to tab_nr.
    when 'MS04'.
      move tabnr600 to tab_nr.
    when 'MS07'.
      move tabnr620 to tab_nr.
    when 'MD05'.
      move tabnr300 to tab_nr.
    when 'MD06'.
      move tabnr200 to tab_nr.
    when 'MS05'.
      move tabnr600 to tab_nr.
    when 'MS06'.
      move tabnr610 to tab_nr.
  endcase.

endmodule.                             " SET_TABNR  INPUT

You have to change the MD04 to your transaction code.

Srinivas

Re: Transaction help.

Former Member — Tue, 29 Nov 2005 17:41:36 GMT

PROCESS BEFORE OUTPUT.

*--> PBO-Module

MODULE SHOW_MRP_AREA.

MODULE CHECK_TRANS.

MODULE SETZEN_STATUS.

PROCESS AFTER INPUT.

*--> PAI-Module

*--> Exit Module

MODULE EXIT AT EXIT-COMMAND.

CHAIN.

FIELD RM61R-MATNR.

FIELD RM61R-WERKS.

FIELD RM61R-BERID.

FIELD RM61R-PRGKZ.

MODULE MRP_AREA_PLANT_CHECK. MODULE CHECK_MATNR.

MODULE CHECK_PRGKZ.

MODULE CHECK_WERKS.

MODULE CHECK_STATUS.

ENDCHAIN.

MODULE SORT_MDEZX.

MODULE READ_TEXT.

MODULE MARD_READ.

MODULE ZM_MCH1SP_READ.

MODULE CHECK_FCODE.

My dinpro 300, perform the module 'MODULE CHECK_FCODE' and leave trax, instead of pass to next dympro

Re: Transaction help.

Former Member — Tue, 29 Nov 2005 17:45:09 GMT

Also check what value you have for am61r-xcode in the exit module.

MD04 is not easy to replicate just by copying it. There are too many checks made, that make almost impossible to trace. Any reason why you wanted to do this?

Srinivas