Global variables

[Former Member]

Hi,

I am trying to load data into SAP BW using Business Objects Data Integrator. I have created batch job with global variable $GB_Name. How can I set value for this variable in SAP BW? Variable $GB_Name may have different values for the same InfoPackage so I can`t set value in batch file.

Thanks in advance.

Lyudmila

[Former Member · Accepted solution]

When you execute the job

- Via Management console

- There is a expandable section for Global Variables. You can enter the value of your choice here.

- Also, if you put the job into different schedules and each schedule having different values for $GB_Name.

- Via Designer

- In the job execution dialog, you should see a global variables tab to enter your values for each run that you instantiate.

Hope this helps!

Thanks & Regards

Tiji

[Former Member · Accepted solution]

Hi, Tiji,

Thank you for response.

I can`t put job in different shedules because the job calls from SAP BW. I have only one InfoPachage in SAP BW in which I can enter only one batch file. I need to set $GB_Name in InfoPachage in SAP BW. Is it possible?

[Former Member · Accepted solution]

I am not very familiar with SAP BW side of the house.

but if you are using a batch job published as webservice, then you can include the global variables in the published web service inputs by enabling the job attributes. Otherwise, We will have to wait for someone else to give the options related to command line arguments.

Hope this helps!

Regards

Tiji

[werner_daehn · Accepted solution]

Right now, you need to have two InfoPackages. One InfoPackage is linked to one batch script, the batch script contains the global variable default values. So if you want to have tow different defaults you need two InfoPackages.

Actually, there is no harm in having two in BW! Or am I missing something.

But you have a different option, you could use a script inside the job and set the global variable there. If you can decide which value to use when.

What you are actually asking for is to specify the parameter in BW, it gets passed down to Data Services and used inside the dataflow. This will be a functionality of DS 12.2 release due in the next weeks. There you do not specify a batch job anymore but provide the job name instead plus job parameters.

[dielom · Accepted solution]

Hi Werner,

Sorry to send the question in another thread, but I need clarification on this issue.

What you mean is that we can't send a parameter from the infopackage to the DI job? The only way to do that is by setting the parameter in the DI data flow?

Thanks,

Cheers,

Diego

[werner_daehn · Accepted solution]

What things can you specify in the InfoPackage of a DI job? The only 3rd party parameter is the "executeable". And this is the batch job that kicks off the DI job.

So all you can do is in the WebAdmin, when creating the "export execution command", specify the value there. Or within the Job, add a first script where you set the variable with some value.

btw, DI 3.2 got released today, there your scenario is fully supported as said.