Restrict purch reqrel at Plant- Mfg Plant

Hi,
I have a scenario to take care of distribution demand at plant to take care of transportation arrangement for 2 days. i.e. Plant needs 2 days to arrange for the trucks.
In given setting we have maintained stock transfer horizon at DC. Given case is if you maintain Stock transfer horizon at DC as 4 days, now if you have forecast coming on the 5th day and also the transportation time between the DC and Plant is 5 days in that case the distribution demand at the plant will come on the 1st day i.e. Today. We cant ship the material today, since we require 2 days of Lead time to arrange for the truck.
Tried with GI time, Stock transfer horizon in Plants but didnt work out. Can any one guide me with the settings .
Thanks and Reg
Jignesh

I dont think there are standard ways to deal with Staging time in APO if that is what you are looking for. One thing that sounds close to what you can do is to define an MRP area in that location or define a proxy location that has a transportation lead time of two days to the normal location. This way you do not have to maintain lesser redundant master data. There is a relative advantage to using MRP area or a location than other solutions as well. It will be easier for anyone to do reporting on the quantity of products that are in a state of being arranged to be shipped. I can easily see the business requests evolving into such reporting requirements.

Similar Messages

Restrict CO Report by Plant

Dear gurus,
Is there a way to restrict CO tcode with Plant?
For example, in tcode KB01, i've enabled check for Plant in SU24, but it's not working.
How do I link the plant restriction in that tcode?
thanks for your help.
Best regards,

Gurus,
That note doesn't contain KOB1.
We want to restrict the plant in KOB1. Is that possible?
Thanks for your help.
Best Regards,

Want to restrict the vendor at plant level

Hi Experts,
As per standard SAP, once the vendor is extended to comapny code then buyer can place order in any plant of same company code. My client wants to restrict the use of vendor at plant and after some business approval, will allow to use the vendor for specifc that plant. Could you please help me, how can I acheive this ?
Thanks in advance,
Regards,
Ajit

There is no solution for you in standard you have to develop something yourself.
It is even possible to create purchase orders before a company code view is created for a vendor master, hence it cannot be controlled via company code blocks. The block at company code will have an effect on goods receipt and invoice receipt, which is too late.
Purchasing blocks can only be set at purchasing organisation level. Even you can create a vendor with a plant level , it is not possible to set a block at this level. If this purchasing organisation serves many plants then a block will affect all plants.
only with a purchasing organization specific responsible for a single plant you can meet your requirement in standard with a procurement block at purchasing org level.

Restricting access to certain plants - any suggestions welcome

Hi,
I have been asked to create a small number of new plants for our business which are only to be viewed by a small number of people. Now the plants will have the same initial letter as a number of existing plants (this can't be changed).
For example, the new plants might be AB01, AB02. The existing plants are A001, A002, A003.
Many of our authorisations at plant level reference this first letter:
i.e. The user can see all the plants beginning with the letter A*.
Can anyone think of a way whereby I can restrict the access to the new plants without having to change all the existing authorisations?
Thanks,
Steph.

Without authorization you can go for customized developement,
search for standard user exit & take help of abaper to complete it.

Restricting SPRO for a Plant

Hello,
My objective is to restrict SPRO to a specific plant.
I have seen SU24 & it is just proposing 9 out of 136 auth objects when I add SPRO to a role.
Is there any auth object in SPRO that can be manually added its usage to a specific Plant?
Thanks,

Your main problem is that much of SPRO is table maintenance and the plant is just a field within the table.
There is an optional object called S_TABU_LIN which can be used for this (defining the WERKS field as an org. criteria in the views) but it is not really suitable for splitting the whole of SPRO based on plant access.
Anyway, why do you want to do this?
Cheers,
Julius

Un-restricted total stock for Plant/Material/StLoc combo, Split-val & WBS

Hi
Users need Un-restricted total stock for combination Plant/Material/StLoc combination ; we have MARD-LABST.
Further, needs WBS & split -Valuation materials stock in the same report or SQVI. I tried to create SQVI, but it`s giving WBS stock as multiple times for SLocs.
I`m using tables QBEW,MSPR,MCHB in the table join.
Pls advise me suitable solution as Std SAP report or SQVI.
Thanks,
Ganesh

Thanks for reply.
But, I need unstricted stock for Mat/Plant/StLoc also to be displayed in the same report .i.e. MARD-LABST.
The MBBS gives stock at Plant level for WBS.
Can both be clubbed? Or need to get from separate reports?
Rgds,
Ganesh

Object Restriction / User exit in Plant Maintenance Module

Dear experts,
Can anyone guide me if i want to put certain restrictions like :
1. other Department will not be able to create Order using other dptt. Maintenance work center, equipment etc.
2. user should not be able to cancel TECO status of order, or not allowed to to put deletion flag on order or notification.
3. Order Release retriction.
4. Should not be able to release/operate other dptt order.
How can i find Object where i can restrict or user exits related to all this.
Thanks
DM

Hi,
1--You can use field exit for checking and validate the workcenter and equipment, but abaper only can do that.
This user exit also u can use "IWO10009 Maintenance order: Customer check for "Saving""
2--please test below user exit can use "IWO10026 User check when setting status "Do not perform""
3-- Use below user exit for validate before release order.
IWO10002 Maintenance order: Customer check for order release
Regards
Sen.

SRM recipient role restricted to plants

Hi
In SRM the organizational levels available in authorizations to the 'Recipient role' consist of 'Purch.org' and 'Purch.grp'.
How do I restrict the role to certain plants?
I tried adding the authorization object M_BBP_IM_1 to restrict actions according to plant but anyone with the recipient role can still see all purch.orders.

Hi
Sorry for the delay - I had to get back to my costumer to try out your suggestion.
Unfortunately it does not solve the problem. The goods recipient role does not automatically check for Plant. - then I would have to use the BADI too - and it would take a lot of maintenance, since we eventually will have 12 different hospitals with each 3 plants.
I need to create som recipientroles, that can be restricted to different plants.
Do you or anyone?? have guidelines to creating an authorization object, that restricts that role to certain plants?
BR
Astrid

Restrict PO creation for multiple plants for same company code

Hi Gurus,
We want to restrict PO creation for multiple plants in the same company code. Based on Standard SAP settings for Purchasing organization assignment with multiple Plant and multiple Plant assignment with single company code, this is happening. Is there a way that we can restrict by doing some customization change.
Any thoughts or ideas will be highly appreciating.
Thanks and Best regards,
Karun Kumar

Hi,
Said functionality is not available in SAP standard.
To avoid the same ,i can suggest implement release strategy for PO,and then higher authority / commercial team can check created PO,if multiple plants available in single po then they have the option of rejection for the same.
Or else check BADI-ME_PROCESS_PO_CUST,take the help from abapor and apply the restriction to select multiple plant in PO.
Hope this will resolve your query,
Thanks & Regards,
Sandesh Sawant

Authorisation to be restrict to plant level for VA01

hi experts,
is it possible to restrict the user to plant level for the transaction VA01.
if possible authorization object for the same or some other process

I think you can maintain the same through MV45AFZZ by linking with the User name & Plant itself.
Otherwise you can maintain your own Authorization Object and assign it to User Name Profile ( through BASIS Constnt) by mentioning Plant & Activity in an Authorization Object.
Best Regards,
Ankur

Inforecord - plant and purch org. assignment

Hi Experts,
I would like to have some support / good ideas on following issue:
we have a plant assigned to purchasing organisation 1:1, and only one (standard) inforecord should exist plant / purch organisation related, because I based my calculation on the inforecord price (through calculation variant / valuation variant). But buyes, who are responsible to create the inforecords frequently make mistakes and create inforecord with no plant, only purch org assignment than make a new one with plant and purch org assignment, which sometimes gives us difficulties - especially on price handling during Po creation and calculation.
Could You, pls advise me, which is the easiest way to stop this kind of duplication, and also delete the only purch org. related inforecords - I want to have only the purch org. and plant related inforecords in future.
Thanks in advance

SAP made the customizing for this control a kind of hidden.
instead of putting it into the info record section in IMG, they have this in Conditions section.
OLME > Conditions > Define Condition Control at Plant Level.
here enter a minus for No plant-related conditions allowed
If conditions are not allowed at plant level, you may not create any purchasing info records or contract items relating specifically to the plant.
you can set a deleition indicator in ME15, and then archive the info record with SARA object MM_EINA

Authorization for Plant in component overview in CO02

HI
I would like to know how I can restrict access to the plant of a component in CO02 ?
thanks
martine

Hi
The user exit PPCO0008 ( Enhancement in the adding and changing of components) can help you restrict any changes of the component in CO02, please go to the SMOD to read its documentations. This is called befor saving the production order then you can check if any changes happened in the component, if yes, you can reject the changes through your own shource code there.
Regards.
Leon.

Maintaining Documents in plant level

Daer Folks,
Is there any possibility maintaining document at plant level without using LAB/OFFICE ? we have WERK(Plant) field in DRAW table but we are not assigning plant anywhere while creating document. is there any work around so that we can make use of plant field of DRAW to tale to restrict our document at plant level.
Bhuwan Tiwari

Hi,
regarding the field 'Plant' I have to inform you that this could not be filled duing the document creation process via transaction CV01N or the BAPI. So I would recommend you to use the field 'authorization group' for your requirement. This field can be filled with a specific value for each plant.
As soon as this field is filled you can define an authorization concept which only allows user to enter documents which have only a specific value in this field and so restrict all other user from entering. For further information on all existing authorization objects for DMS and also regarding the field Authorization Group please see the following link too:
http://wiki.sdn.sap.com/wiki/display/PLM/AuthorizationObjectsin+DMS
Best regards,
Christoph

Classification at Plant Level

Hy,
I want to make some restriction in Bacth Classification, but this is only for some selected Plants only.So is it possible to restrict the classification at plant level insted of client level?
Recently I have read about Class type 022 (batch Class)which seems to be Plant level, but when I am going to create new Batch Class with this 022 Class type , system throws an error
"Internal class type 022 cannot be used in class maintenance
Message no. CL089"
Pls Guide,
Dhaval

Hy,
My requirement is,
We have just started Batch Determination strategy, for which we have marked one characterstic as a Entry required.So that user gets an massage at the time of GR if he fails to maintain the value of characterstic in Bacth Classification.
Now situation is this,
We are plan to convert that warning massage in to Error but, problem is that it refelcts in all the other plants, where there is no such kind of reuirement and Batch class is commonly for all the plants.
Thats why I am thinks about Classification at Plant level.I know it is now too dificule or almost imposible to change the whole data, but we can plan better for our upcoming Manufactring Plants where system is still not implimented.
Thanks for all of your kind guidence.
Dhaval

Inforecord - only plant relevant conditions

Hi Experts,
could any of You pls help me with an inforecord condition issue?
I would like to use plant AND purchasing organisational relevant inforecord - both are necessary. I have configured the V_001W_K table (Activate condition Maintenance for Plant), but somehow i did not end up at the desired state:
if I set to a plant - no Plant relevant conditions are allowed - I can not create an inforecord assigned to a plant - which is OK But if I added - only plant relevant conditions are allowed - I was still able to create an inforecord with price conditions with no plant - I expected, this would be forbidden as well. (purch organisation : plant - N:1 - so plant could be mandantory).
Now users keep creating inforecords with and without plant - which should be stopped, preferably to create only purch org AND plant relevant data.
Could any of You pls tell me, what I miss: setting or misunderstanding the configuration possibilities.
Answers will be appreciated

This bit of config (help text below) ? If so then a misunderstanding. The setting relates to Conditions, not whether the PIR are set per Plant in themselves.
Indicator: Conditions at plant level
Determines how prices and conditions are stored for the relevant plant.
Use
If conditions are allowed at plant level, you must create purchasing info records and contract items relating to the plant. Centrally agreed contracts cannot then be created.
If conditions are not allowed at plant level, you may not create any purchasing info records or contract items relating specifically to the plant.
If conditions are allowed with or without a plant, you can create purchasing info records that either do or do not relate specifically to the plant.

Restrict purch reqrel at Plant- Mfg Plant

Similar Messages

Maybe you are looking for