RIMODGEN and RIMODAC2

[former_member205751]

Dear all,

a small favor please , RIMODGEN report needs to run at 11 PM every day , Can you help me with t code where i can set this time factor, now for Go Live sake I have asked my users to do it manually with CFM!, and CFM2.

In days to come this RIMODGEN and RIMODAC2 will run as auto matic job at 11 PM.

Guess this time should be integrated within the report ...rite !!

Regards

OHIO

[RahulHanda · Accepted solution]

Rahul,

Create a job in SM36 with same name. Put the program and variant. Thereafter you have option for start condition, click on the same. Then click on date/time icon. put schedule start date and time. Click on periodic job and period values.In period values click on daily. Save the condition and job. Check in SM37 you will see the same.

If already answered follow

Regards

Rahul

[former_member205751 · Accepted solution]

Got it ...SM36. and 37  thats what i was looking for..thanks rahul ji

Nice of you. my deliverables  are product planning table,production planning run ,DS planning board and CIF ( me the only resource for  this plant),if my client asks me how much time you need to set right all, what would be the timeline you can think off.  shall i say 3 months,??? However only when the users start using it,i will come to know about the volume of errors,that too has to factored in ,but given your experience what is the approximate time length,could you suggest. rahul ji please throw some insight on that.

regards,

Ohio

[RahulHanda · Accepted solution]

Rahul,

All of it depends upon solution implemented as per business needs, plus the training which you need to give to the users which has to be part of your scope before go-live. This will make sure that most of the hiccups are already handled in UAT. Of course after go-live you have stabilizing process but that again depends upon scenarios, volume of data etc. and understanding of the user. So can't judge on the basis of certain areas as they are also linked to complete solution plus master data etc..

I would suggest you to have complete understanding of the solution you are implementing along with scenario's which you need to cover while testing (from the inputs of end-users and blue-print document/as-is document) and decide on the basis of the same the timeline.

Regards

Rahul

[former_member205751 · Accepted solution]

Rahul I found users were APO novice,and also the top level management,so i asked my client  to GO LIVE first and later on post implementation I will take responsibility to set it rite,

it would be nice if you give me a point blank  timeline ,shall i say 6 months or 8 months,

Client knows PPDS is toughest module,and he also knows that i am not an expert,he also knows rahul speaks point blank,and outspoken to the core,so credibility is the only linking factor between me and client and not APO,so whatever timeline i will give they will   accept ,but it has to be backed by adequate reasoning, so i will carry your line of reasoning ,a print out of it(the one above) and say 8 months,Hope you will agree with me.

[RahulHanda · Accepted solution]

So be it, a wild guess from me (without knowing details) to cover you.

Rest I hope you will deliver.

Regards

Rahul

[former_member205751 · Accepted solution]

yup thanks rahul, it is decided as 5 months,system hiccups will be dealt by me and training alone by another APO resource chosen by me. Then again finding a suitable APO resource to train users is a challenge,so far I have interviewed 20 people none fits the job, is that finding an APO resource difficult or what ?? but I could see lots of ECC resources,available in short notice  ..

[RahulHanda · Accepted solution]

Totally depends upon availability. Anyways if above has answered your initial question let's close the thread as usual.

regards

Rahul