Navigation profile in MD04 to call VA06

[Former Member]

Hi All,

i have a question regarding the navigation profile and parameters in transaction md04.

i've created a new navigation profile (Z000000001) with this values to jump to transaction VA06:

In MD04, the navigation profile is there..

when i clicked navigation profile, it goes to VA06 which is correct, but it "forgets" the parameter for the Material Number (MAT).

has anyone an idea for this issue?

thanks and regards,

juli.

[former_member452116]

Hello Juli

In the custom navigation profile, did you enter a specific material value or material parameter ID or did you leave it blank and copied it via the code you displayed.

[Former Member · Accepted solution]

Hi,

Why have you entered sequence no. as 1. In Standard SAP Sequence 1 is for MD03. Plz check in general trasaction cals. In our system when i link to MD03 then system open it with the material. Do not enter any parameter ID.

Also, have a look at this manual

MD04-NAVIGATION PROFILE - ERP Operations - SCN Wiki

Regards,

Priti.

[Former Member · Accepted solution]

Hi Priti,

Actually I created customised navigation profile Z000000001 (as per my first screen shot above) and I choose that navigation profile.. material did not get transferred to VA06..

/juli.

[Former Member · Accepted solution]

Hi,

Have you checked manual?

Can you try in existing navigation profile and check if it is working with standard profile. It is explained in manual. I doubt abot VA06 as it is just a list.

Regards,

Priti

[Former Member · Accepted solution]

Hi Priti,

I've tried with existing navigation profile and it's working.. but it's not working for VA06.. is this mean listing reporting tcode cannot be call from navigation profile?

regards,

juli.

[JL23 · Accepted solution]

Have a look into OSS note 395673 - MD04: No parameter passing during branch operation , it explains reasons and a possible solution in a similar case with calling MIGO and other transactions

[Former Member · Accepted solution]

Thanks Jurgen.. thank you so much.. It's working now..

What I did is create customised program calling VA06.

create implementation in VA06 (include SD_OSO_MONITOR_INI) to grab material number.

and it's working..

[Caetano]

Hello

When the value of a parameter is set on transaction MD04, the ABAP command "SET PARAMETER" is called. After the next transaction is called, the ABAP command "GET PARAMETER" must be also called, in order to get the value sent from transaction MD04.

It means that, if there is no GET PARAMETER on MD04, system will not read the value sent from MD04. You can easily check that setting break points for the mentioned ABAP commands.

If there is no command GET PARAMETER for the material on VA06, you can try the approach mentioned by Jürgen on the previous reply.

BR
Caetano

[Former Member]

thanks Caetano.. it's working now.. I follow OSS Note 395673 suggested by Jurgen..