on 09-24-2013 7:27 AM
Hi All,
My client requirement is when ever they are creating PO with ref to contract the PO Doc type must be ZW or ZB and it should not allow NB doc type to the user to create the PO.how can we restrict this PO doc type.
Please let me know if any standard settings available for this requirement.
Thanks
kiran
I actually think your requirement can be met with customizing.
You actually have several field selection keys, e.g. for the transaction, for the document type, for item, for the activity... They all interact.
The principles are explained in the docu.
execute OLME and go to the purchase order > Field selection
Here click the documentation icon next to the execution icon.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
This cant be happens by any type of configuration.
You have to do a user exit for this.
If it po will be created through a particular user then you can use ROLL.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Kiran,
You can use authorization object for document type M_BEST_BSA. Get the help of the Basis to configure this.
Refer below as well.
http://scn.sap.com/thread/3381119
Regards,
Jeewana
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm really sorry I didn't notice 'contract' part in your early post. There is no standard link in PO type and contract type in SAP as I'm aware. This has to be handled in some other way. I found belowe threads which are slightly similar. May be you can have some idea.
http://scn.sap.com/thread/2077624
PO should not go for approval if it is from a contracthttp://www.sapfans.com/forums/viewtopic.php?f=3&t=297345
Hey Kiran,
I don't think this is possible through configuration. You may need to code a line in an user-exit to restrict creation to contract-po document type pairs.
Another alternative may be to suppress the agreement number and agreement item fields in the document types which should NOT use the contracts. Will need to test this to ensure it works with automatic source assignment scenarios also.
If you consider how the contract behaves when creating a PO, it almost acts more as a master data than as a reference document.
Thanks,
Saurav
User | Count |
---|---|
99 | |
11 | |
10 | |
6 | |
5 | |
5 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.