on 03-18-2013 8:02 AM
Hi Experts,
My customer has send me a new requirement which is related to Forecast data lock.
Actually they provide us some materials which are coming to their End of Life(i.e. EOL products).
They want us to lock the key figure "FORECAST" only for these materials so the users cannot input the data for these material.
For this i try to use the macro function CELL_INPUT() and ROW_INPUT() which will not allow the users to enter the data, but my problem is that these macros will work only in foreground not through background job.
How to do this activity through background jobs can u please help me on to this.
Hello Panchal,
Can you have a look on these SAP Notes:
1060992
1062873
Might be helpful to you.
Regards,
Anurag
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Thanks to All for your replies !!!
I have seen the list of materials some products EOL is in march 2013,some in november 2013 ,some in march 2014.So i don't think batch job is the solution for this query.
Because have to maintain different selection profiles for all these materials.
Is there any other efficient way so that end of life products can be tracked and users will not able to forecast them after their end of life(means restrict them for forecast) ?
Actually in my scenario customer is doing only Demand planning and transfer back the constrained demand to R/3 sytem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Try options-1 and 2 in field 'SDP Relevance' in product master - /sapapo/mat1.
BR,
Vishal..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
you need a BW characteristic in your MPOS to group these products, then exclude them in all your background selections. As an alternative, with the same BW characteristic use authorizations to block permission somehow, but this seems a lot of work (you don't want permission to your background job user to forecast, for instance, but you may want permission for other things).
Exclusion from background selections is simpler. Authorization may work to prevent that your regular users do forecast during interactive session.
regards,
J.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
9 | |
4 | |
3 | |
3 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.