on 04-10-2007 11:33 PM
I am at a client where they require following:
When creating PO and/ PR for capital assets they would like the system to require mandatory field for- Internal order and G/L account. Also the consumption posting must go to Asset.
How do I configure this for Purchase Req and Purchase Order?
I have not found an account assignment catagory that meets all the requirements - which one ( F or P or A or S) would be best to copy and make changes? Or is there another way of doing this?
Help please- thanks
Raj
Arif:
thanks for the info- can you please clarify the following:
EVO parameter- explain further please
Making Pr field mandatory for PO - where do you configure this?
Any clarification would help. Thanks
Raj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Raj,
EVO parameter is used for defaul values for buyer. The IMG help explains in very good way. SPRO--> Material Management --> Purchasing --> Environment data -> Define Default Values for Buyers.
Here you define values for parameter and assign it to user profile.
PR mandatory field setting depends on the screen setting at doc level. Make the Purchase requistion field as required in "Reference data, item" section in SPRO--> Material Management --> Purchasing --> Purchase order -->
Define Screen Layout at Document Level.
Hope this helps.
Regards
Arif Mansuri
Hello Rajendra,
You make settings for account assignment category in OME9 transaction code.
Make the fields (i.e. Asset no and G/L account) number as required here.
For asset you need to use account assignment category A, I think Internal order means Purchase requision, if so you can always use EVO parameter or you can make purchase requisition field mandatory in purchase order.
Hope this helps.
Regards
Arif Mansuri
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I think the internal orders that Rajenda was referring to are the CO type internal orders that are basically cost collectors, rather than requisitions.
Account assignment category F makes the GL and internal order fields mandatory, would this not suit your requirement?
If this is correct then the EVO parameter does not affect this but it is a very useful parameter and can make the reference to a requisition mandatory (by indicating that POs can only be created with reference to requisitions and then allocating the EVO parameter to the appropriate users).
Steve B
Message was edited by:
Stephen Birchall
User | Count |
---|---|
99 | |
11 | |
11 | |
6 | |
6 | |
4 | |
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.