Transaction variant MD61

[former_member2091]

Hello Folks,

I am trying to create a transaction variant for MD61 and would really appreciate if you can comment on some points,

1. No matter what I am putting in user parameters, system does not consider in variant (it does in MD61 std.)

What I actually need is input get Daily PIR but in config we have saved monthly and system always consider that not user parameters.

2. Which package should we save it in? package of T code MD61 ?

[former_member2091]

Hi All,

Would really appreciate if you guys can comment on this query

Whenever I save PIRs in variant(ZMD61) system takes me back to MD61 t code screen only and I am not able to stop that, which we cant have as users will not have access to MD61. Also, anytime I hit back in variant screen system takes me back to standard MD61 screen.

[ninad_narad]

Hi Akash,

Can you please check if the transaction variant is active in SHD0?

If you are transporting these changes from the golden client, the transaction variants need to be activated in individual systems.

Regards,

Ninad

[former_member2091]

Hi Ninad,

I am not exactly sure how to activate variant. I made it in DEV client, assigned it a tcode and is working just fine.

Only issue is when user hits back or at final saving system goes to standard screen.

[lingaiahvanam]

Hi Akash,

You can define standard parameters in the configuration OMPD based on your requirement for MD61, MD62 and MD63 transaction codes. The default parameter will update when you access the transactions. I would suggest choosing the below options to update the planning period.

1. Update standard parameter for each transaction code in configuration and do not select any user parameters (by default all users use standard parameter).

2. Maintain the data type blank in configuration and control via transactions (users get a benefit based on user selection).

ompd-md61.png

md61-user-parameter.png

md61.png

Please note that if you maintain in configuration data type to W (week) and your user parameter maintain as D (Day) then user parameter is the highest priority.

Best Regards,

Lingaiah

[former_member2091]

Hello Lingaiah / Brahmankar,

Thank you for your inputs.

Actually, I knew about the settings in config and user parameter but still system was behaving abnormally. Although I observed that when I save variant in SHD0 and then re run the variant it behaves normally and issue is solved.

But, I am facing another challenge as soon as I save my variant(ZMD61) system takes me back to MD61 t code only and I am not able to stop that, which we cant have as users will not have access to MD61.

[former_member2091]

Update

I ran multiple times but as soon as I save or get back from transaction variants screen, system takes me to standard T code. How can I control it?

[rupesh_brahmankar3]

Hello,

In MD61 user parameter Period ind. = D should work with period split.

Please try this for your user id in MD61 as well as for MD62 and then check it.

Best Regards,

R.Brahmankar