Maintain plant wise purchase document type

[Former Member]

Hi,

I want to know that is there any way where I can able to maintain plant wise purchase document type.

Thanks.

[sjeevan · Accepted solution]

Please make the following settings

Scenario:

Plant 0001 Should create only PO type NB and PR type NB

Plant 0002 Should create only PO type ZNB and PR type ZNB

TCode : OLME

Create new PR type by copying NB (all dependencies): ZNB <<<Separate number range can be used

Create new PO type by copying NB (all dependencies) : ZNB <<< Separate number range can be used

To avoid accidental assignment of (by users)

Remove linkage of NB PO type to ZNB PR type

Remove linkage of ZNB PO type to NB PR type

TCode: OMDT

Assign PR type per plant per MRP Group for MRP generated PR's

Once MRP is run for materials PRs are created as follows plant 0001 type NB and plant 0002 type ZNB, when they run ME57 to create POs from PRs, ZNB PO type will default to PR types ZNB and NB type to NB.

Authorization objects to be changed for each plant respectively (go to SU21 to look up)

Users of Plant 0001 can only create NB type PR and NB type PO

Purchase Order:

M_BEST_BSA ACTVT=01; BSART=NB;

Purchase Requisition:

M_BANF_BSA ACTVT=01;BSART= NB;

M_BANF_WRK ACTVT=01;WERKS= 0001 ;

Users of Plant 0002 can only create ZNB type PR and ZNB type PO

Purchase Order:

M_BEST_BSA ACTVT=01; BSART=ZNB;

Purchase Requisition:

M_BANF_BSA ACTVT=01;BSART= ZNB;

M_BANF_WRK ACTVT=01;WERKS= 0002 ;

Ofcourse you need to create output message config for each PO type.

Edited by: Jeevan Sagar on Feb 13, 2012 11:16 PM

[Former Member]

hi

You can not maintain plant wise document type , but you can control plant wise purchase document , please ask to basis person for authorization control through role maintenance

Regards

ragini

[Former Member]

Hi,

Document type should be maintained at client level.So it would be applicable to all the plants and whenever if you want to define your own document type,you can go with that document.

Best regards,

Sridhar G

[BijayKumarBarik]

Hi,

When procurement processes are different, then you can use document type concept to differentiate all procurement process.

So you have different STD. document types are:

NB,

UB,

FO etc....

As needed you can use User Exit M06B0003 & M06B0004 which will allow PO number range based on Company Code. But restricting PO document type and Number ranges Plant wise not advisable.

Regards,

Biju K

[Former Member]

This is not an ideal process but it can be achieved through enhancement.

Use BADI ME_PROCESS_PO_CUST and write your logic such that for a perticular plant only a perticular document should be

allowed.

Remember by implementing this you need to define lot of document types..accommodate for all plants

[Former Member]

Hi Abhishek,

I dont think it to be a good Idea to maintain the Document type at the plant level.

that should be maintained as the last Resort, as said in the above thread that the Document are mainatained at the Client level.

in addition to the same there are Technical Issues as the nor of Document Type will increase to huge amount and will not be easy to controle the same.

you maintain the Common Document types and make sure that different activities are using different Document type. that would be far much better...

Hope it helps you.

regards,

Yawar Khan

[former_member197616]

Hi,

The Configuration part of the purchasing document will be at Global so that any plant can utilize that.However you can resrtict the usage through user exit coding adding to the standard PO functionality.

In the coding you can write if the X document type used for pr and if the PR plant is y other than the stipulated , you can put a error message to stop furthur processing of the document.

Regards,

[tejyadav]

Purchase document type are maintained at client level & not Plant level.