Restricting WBS element to Company Code it was created for.

[Former Member]

Hi.

We are having some trouble at work. We create projects with all the steps needed (CJ01, CJ40, CJ30, IMCCP3, CJ32, CJBV, ME12N and CJ02) and assign each WBS element to ONE company code. However, when employees create a purchase order with ME23N, sometimes they choose one WBS element and choose some other company code. This causes trouble later in the process.

What can I do to restrict the WBS element they choose to the company code with which it was created or do it the other way around; restrict the company code they choose depending on the WBS element (One WBS element is picked, only one option for company code remains).

Examples

Restrict company code depending on WBS element.

They choose WBS element X, they HAVE TO choose company code X.

(Currently they can choose any company code they want)

[sudhir_singh]

Hi Experts,

I have same problem.........please resolve it...!!!

T. & R.,

S.Singh

[sushrut_sheth]

for transaction code ME21N during creation of PO provide the validation or check while carrying out the account assignment.

check shall be made that for the company code X only WBS element With X company code is allowed,Ask your Abaper to add this check

[Former Member]

HI Borja,

Basically while your users select a WBS element with company code X and they try to create PO for company code Y, system checks for indicator Billing in project master data. Try NOT selecting operational indicator "Billing" and then try to create PO.

Thanks and regards,

Narender.

[MTerence]

Hi Borja,

Rather than restricting the WBS element for company code.

Try to change the field validation for company code in ME21N, once the vendor is selected you can make the field greyed out. This will ultimately restrict users editing it.

On the other side, you can try in substitution / validation (not sure how this will work)

Regards

Terence

[Former Member]

Hi,

I agree with Shishir here.

Infact I was also thinking to restrict this on purchasing org. level. Its better to create a role in PFCG.

Regards,

Amit

[Former Member]

Hi Borja,

One more thing, I believe that you have maintained your company code in project profile. Just thinking of other way round that whenever new WBS/Project gets created, it automatically picks assigned company code.

Regards,

Amit

[Former Member]

Hi,

Firstly I want to tell you that in PO creation (ME21N), system will not ask for company code. It's either automatically picked from Vendor or Purchasing organization, not from WBS.

So here what you can do to restrict user's based on Pur. org. That will be more easy by just creating a role using PFCG.

And if you want to restrict WBS only, You can assign different responsible person to all WBS and restrict the users on the basis of responsible person. Use  C_PROJ_VNR AND C_PRPS_VNR authorization objects.

Regards

Shishir         

[Former Member]

Hi Borja,

Well, I am just thinking to restrict this process on Purchasing Organization level. I think that whenever you assign material with account assignment category Q or N, then at that time if you enter purchasing org and afterwards if you create PO by adopting PR then it that case it will automatically fetch the company code as per settings maintained in OX01 and there if you try to change the company code, then system will stop you saying that purchasing org is not defined for this company code.

So I believe that OX01 setting (i.e assigning purchasing org to company code) can play a good role in this.

I feel that you are raising PR not through Project System. (ie. creating separately from me51n). is that so.?

But lets wait for other experts to comment on this. I might be wrong with my advise.

Regards,

Amit Rajoria

[Former Member]

Hi Amit.

I reread my question and I don't think it was clear enough. So you start your PO with the purchasing org and company code. You put in the amount, quantity, vendor number and later you have to type in the WBS element. However you can pick any WBS element from other company codes, regardless of the purchasing org/company code you chose before.

Can you explain a little more in detail what you mean? We already have the settings that pair up company code with purchasing organization in OX01, so how is it supposed to work?

I understand that if I choose purchasing organization X, then SAP will only let me choose company code X. However, when I have to enter a WBS element afterwards the system lets me enter any WBS element from any other company codes. How can I restrict this?

(I did some research later and thought that maybe this could be done through a validation rule in transaction OPSI, any ideas?)

Thanks very much,
Borja.

[Former Member]

Hi Borja,

Few questions I want to ask before I could reply.

1. Are you creating PR before PO.? or you are directly creating PO.?

2. Which account assignment category you are using while creating PO or in PR (in case if you are creating PR) .?

Now, lets focus on what you have written. "So you start your PO with the purchasing org and company code. You put in the amount, quantity, vendor number and later you have to type in the WBS element. However you can pick any WBS element from other company codes, regardless of the purchasing org/company code you chose before."

Now, If I understood it correctly you are saying that you can pick any WBS element regardless of the purchasing org. But, I believe that if you have maintained your settings in OX01 then system will not allow you to pick any WBS element. Because prior to entering WBS element you must have picked up purchasing organization.

Regards,

Amit

[Former Member]

Hi,

Check if you have maintained the company code validation. I have checked in my system, and I am not allowed to use the Pur Org and WBS with different company code in PR/PO creation.Because i have activated the company code validation.

Goto SPRO->Controlling -> General Controlling ->Organization -> Maintain Controlling Area.

Select your controlling area and select Activate components/control indicators.Here projects must me ticked.

Check and try.

Regards

Shishir