cancel
Showing results for 
Search instead for 
Did you mean: 

Effective way to chain multiple logic/DM packages?

Former Member
0 Kudos

Has any one had the need to chain together multiple logic statements and/or data manager packages that cross different applications?

It seems the *RUNLOGIC keyword is not supported (we're on SP02), so I'm looking for ideas.

One thought is to create a process chain that has additional Run Logic steps with the desired parameters actually stored in the chain definition.

Other thoughts?

Thanks.

-Amy

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Amy,

You can try using *RUNLOGIC within BADI. This should work.

Hope this helps.

Former Member
0 Kudos

Do you have syntax example of how you would run logic from another app in the badi?

Former Member
0 Kudos

Hi AStine,

As per my understanding from your post you want to run different logic files. If that is the case you can include the required logic file name at the end of the logic file which will be executed first.

Hope this helps.

Regards,

G.Vijaya Kumar

Former Member
0 Kudos

Hi,

Sorry i didnt notify that your requirement is to run logic across application.

Regards,

G.Vijaya Kumar

Former Member
0 Kudos

Hi Astine,

I am able to run a logic in different application by changing the application name in the dynamic script and the name of the script to be executed in that application.

PROMPT(SELECTINPUT,,,,"%CATEGORY_DIM%,%TIME_DIM%")

TASK(/CPMB/FX_RESTATMENT_LOGIC,SUSER,%USER%)

TASK(/CPMB/FX_RESTATMENT_LOGIC,SAPPSET,%APPSET%)

TASK(/CPMB/FX_RESTATMENT_LOGIC,SAPP,<Name of the required Application>)

TASK(/CPMB/FX_RESTATMENT_LOGIC,SELECTION,%SELECTION%)

TASK(/CPMB/FX_RESTATMENT_LOGIC,LOGICFILENAME,<Name of the script in that application>)

Hope this helps,

Regards,

G.Vijaya Kumar

esjewett
Active Contributor
0 Kudos

Amy,

I think you're on the right track with the process chain with additional runlogic steps. This will work within a single application.

Across multiple applications or appsets, you are going to have issues because the BPC process types seem to pick up the application set and the application based on the data manager parameters passed to the Modify Dynamically process type. The upshot is that you can't call script logic in two different applications from within the same BPC process chain.

However, you can theoretically simulate calling multiple BPC process chains from data manager using the approach outlined by Pravin Datar in his blog [Running BPC process chains within non-BPC process chains|http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/12929] [original link is broken] [original link is broken] [original link is broken];. You would call the UJD_TEST_PACKAGE program multiple times in a process chain using different prompts.

I would not describe this solution as particularly robust, but it looks workable.

Ethan

Former Member
0 Kudos

I am transferring data from one application to another via default logic, and I need to be able to trigger the destination application's default logic. Has anyone done something similar in NW? It appears that *RUNLOGIC is not supported in NW.

Regards,

Karen