Prompts in Package Link

[Former Member]

Hi experts,

I have this package link with 2 tasks.

The first prompts the user for a source and destination version:

The second package runs logic in another application, it also prompts the user for a version:

As you can see from my label text, the Version in the second prompt MUST be the same as the Destination from the first prompt.

Is it possible to pass the selection from the first prompt to the second package? The existing arrangement is confusing to users, and allows the user to make an error by selecting a different version.

[former_member186338 · Accepted solution]

Not possible!

But if your package link is executing 2 logic files you can combine 2 into single logic file with common prompts.

If you want to execute logic in the different model you can use RUNLOGIC_PH badi.

Vadim

P.S. Please, show scripts!

[Former Member · Accepted solution]

Thanks Vadim,

I can't combine the logic in a single LGF because they reside in different applications.

I didn't need the BAdi. I can run the LGF in the other application by replacing %APP% in the dynamic variables with the name of the other application.

I looked into RUNLOGIC_PH, but it doesn't exist in our system and I don't have a developer key. So I came up with this workaround.

It would be best if I didn't have to ask the users for the same thing twice, but they'll survive.

Paul

[former_member186338 · Accepted solution]

"I can't combine the logic in a single LGF because they reside in different applications." - RUNLOGIC badi was developed exactly for this case!

Also, if you use DESTINATION_APP in scripts this badi is also must have...

"I don't have a developer key" - just ask basis to import transport (the version check has to be ignored!). 5 minutes job and you will have this badi We use this badi for about 5 years with excellent results.

"So I came up with this workaround." - everything can be done manually

Vadim

[Former Member · Accepted solution]

Thanks again. A question about RUNLOGIC_PH. After reading the documentation I was unsure about its purpose. Does it run the logic from the other application in THIS application, or does it just run the logic in the other application. I thought it must have been the former since I can do the latter without calling the BAdi.

[former_member186338 · Accepted solution]

With runlogic_ph you can:

In the script in one model launch the script in another model on the data of another model. And you can pass scope and $$ parameters to this script.

Hope it's clear

[Former Member · Accepted solution]

Hi Paul,

You can't run logic written in one Model in anther Model because most probably syntax will be incorrect. So, RUNLOGIC implements the second case. In some instances you really can achieve same result just by renaming Model in the DMP, but you can't pass parameters used in one Model to another Model. And that's what RUNLOGIC allows to resolve.

Please let me know if you have additional concerns.

Regards,

Gersh