Procurement profile canont be changed

[Former Member]

Hi SRM gurus,

We are working on a PDP scenario where the PR is transfered from R/3 to EBP as shopping cart through the standard BBP_EXTREQ_TRANSFER and we are getting the following error :

"Procurement profile cannot be changed " Message no. 6Q 204.

we are not able to transfer PR to SRM because of this error.

Our SRM is 5.0 and our backend is ECC 6.0 which was upgraded from 4.7 recently.

Could there be any config missing?

The idoc shows green though in R/3

Any suggestions.

Best regards,

Sridhar.

[khan_voyalpadusman · Accepted solution]

this message is thrown from the R/3 System and not from the SRM System.

please have a look at the function module

BBP_EPROFILE_REQ_CHANGE in the R/3 System..

this is the place where the above mentioned error message is handled.

-

---

>

profile cannot be changed, because it is already transfered

<profile_n> = <profile_o>.

MOVE im_eban_old-ekgrp TO ch_eban_new-ekgrp.

MESSAGE E204(6Q) WITH <PROFILE_O>.

RAISE error_message.

-

---

>

are you transfering the PR first time (or) second time , let me know

[Former Member · Accepted solution]

Hi Khan,

The error is thrown in R/3 only and it comes exactly from the same code where you have pointed out. But our abaper says that the code is changed automatically after the upgrade from 4.7 to 6.0. Will it happen like this ?????

I suspect there are OSS notest to be implemented for this but whatever I search is throwing me the older notes.

Can you please guide us more on this ???

We are not transferring the PR for the first time.

Best regards,

Sridhar.

[khan_voyalpadusman · Accepted solution]

Hi,

It is possible that the code migh have been added in the new release.

Problem here looks like this.

1) you are creating a purchase requisition --> to which profile will be attached , you are transfering the PR to SRM.

2)you are then chaging the purchase requisition ---> to which profile attached is different from the first one.

this is causing problem ---> when the PR is changed , ensure that profile remains the same , looks like the system does not allow the profile to be changed.

[Former Member · Accepted solution]

Hi,

But in V_T160EX and V_T160PR we have only one profile attached with which is supposed to be searched/attached.

I agree your view but what is the solution for this ?

Best regards,

Sridhar

[Former Member · Accepted solution]

Hi,

We have a combination of Material group * and the respective purchasing group combination in the V_T160PR table.

We are getting this error for all the PR's which is created already and we are trying to delete for few purchasing groups.

We dont have an EPROFILE entry in the EBAN table as this is purely from R/3 and not from SRM.

Can anyone please suggest the way out ??

I am struck.

Best regards,

Sridhar.

[Ramki · Accepted solution]

Hi Sridhar

This is my understanding. Pl correct me, if I am wrong:

1) You have some PRs in the system

2) You have updated V_T160EX and V_T160PR tables.

3) Now, when you try to change any of these PRs, system gives you an error message because the system is trying to change Eprofile field in EBAN table from 'Blank' to 'New value' as per your V_T160EX setting for matgroup/pur.grp.

Solution :

Try this for one PR, test it and if successful, use it for other PRs.

1) Write an update program which directly updates the EPROFILE field in EBAN for a sample PR.

2) Execute the above zprogram & update a PR. Test changing this PR.

3) If it works, do it for all required PRs.

4) be very careful as you are directly updating EBAN table.

Best regards

Ramki

[Former Member · Accepted solution]

Hi Sridhar,

Ramki is right.You need to reset the profile indicator once the PR is transferred to the SRM system in the BADI BBP_BADI_EXTREQ_OUT in R/3.

BR,

Disha.

Pls reward points for useful answers.

[Former Member · Accepted solution]

Hi Disha,

We applied the OSS note 1067274 ( the previous one for this is 845916) and changed the code, but the problem still exists.

Any suggestions.

We have ECC6.0 and SRM 5.0 as the systems.

Best regards,

Sridhar.

[Ramki · Accepted solution]

Hi Sridhar

This note will not work for already released PRs. It only works for PRs which are not yet released.

Try the approach given by me in previous post.

Best regards

Ramki

[ravindra_mantri2]

Hi Sridhar,

This error is in R/3 only.

Possibly there can be one of the following mismatch appeared.

1) I would suggest you to first check in table V_160EX about matl grp and pur grp combination with profile.

If table entry is missing for specific matl grp and pur grp, which you actually used in creation of PR, then also this sort of error appears.

2) Once PR is created, check the entry in EBAN table and make sure that EPROFILE (external procurement profile) is ticked.

rgds,

Ravi

Do reward points for useful answers.