Job Control - Job Parameters - Not Maintained in LBWE

[Former Member]

Hello Gurus,

in R3 - LBWE for SD Sales for BW, I have maintained the Job Control Parameters, Start Date- Immediate-Periodic Job-Periodic Values-Hourly. But the next day when i check the same, it is in not maintained status.

Any clue to what is to be done.

thanks

[Former Member · Accepted solution]

thanks for the reply Ryan.

the job is running for LIS-BW-VB_APPLICATION_11_400

. but now i noticed again, it has turned to not maintained. i turned it on today morning itself.

is that ok.

thanks

[Former Member · Accepted solution]

bw,

where is it not maintained? LBWE will always say that it isn't, even if there's a job running already - just make sure that the job i mentioned is existing and executing in the system. that's all you need to be concerned about.

ryan.

[Former Member · Accepted solution]

Dear,

as Ryan already said, don't worry about LBWE delta management pop-up and status 'not maintained'...this is a message only valid when you want to schedule something (generally speaking), but it doesn't refer to already scheduled job !!!

Check in SM37 and this is enough !

Bye,

Roberto

[Former Member]

hello Roberto,

following r the steps i m following to transport my objects from dev to production:

1) goto transport connection

2) select the respectiv sales ods and cubes one by one.

3) select "in dataflow before and afterwards"

4) drag and drop on the right hand side. attached them individually to a package and request.

5) do an stms_import in the production.

AM I RIGHT. will all the related infoobjects gets transported.

i m seeing that the infopackage doesnt get transported along with it.

i tried for one cube the above steps it failed with error 8.

thanks

[Former Member]

Pradeep,

open another thread about this issue, so anyone can help you !!!

However,

personally, I follow this procedure:

1) go to transport connection

2) select your flow, but breaking it in these three steps (separately):

- infosource (and a dedicated TR in the following steps)

- dataprovider (and a dedicated TR in the following steps)

- query (and a dedicated TR in the following steps)

3) select "dataflow before"

4) drag and drop on the right hand side. assign to a TR

5) release and stms

This is a little time consuming (rather than collect all with 'before and after'), but gives safety about any interdependencies among the objects: if you start from the bottom you have the possibility to highlight the error and manage it without doing later and with no method...

Anyway, what's your error message ???

Bye,

Roberto

[Former Member]

Roberto, i have assigned. but got a bit delayed.

u can check now

rgs

PRADEEP

[Former Member]

Pradeep...nothing !

Now I see Ryan's points but nothing to me !!!

Probably it's a sync issue...but, again, don't worry and see you next time !!!

Cheers,

Roberto

[Former Member]

Thanks Roberto and Ryan. Have assigned full rewards to you.

TR PRADEEP

[Former Member]

Pradeep,

I think your point assignment doesn't work !!!

However, happy to help you !

Bye,

Roberto

[Former Member]

bw,

if you're checking the job status in LBWE, then you'll likely see the not maintained status. try using SM37 and look for jobs using the filter LIS-BW-VB_APPLICATION_13*.

if you see the job there, then the job is running and collecting. 😃

ryan.