In PDP cycle is it possible to pull back transfered PR (from SRM to ECC)?

[Former Member]

Dear Friends,

We are working on PDP cycle where backend ECC Purchase Requisition is transferred to SRM client via program BBP_EXTREQ_TRANSFER so that the procurement activity is carried out in SRM.

Now business decides to discontinue the procurement activity from SRM and continue in R/3 only. Which mean business would like to create Purchase Order in R/3 with reference to PR.

So we delete the shopping cart created in SRM and tried to change the Purchasing group so that system removed the procurement profile tag from PR. But system does not allow.

My question is, is it possible to pull back the PR from SRM to ECC after it has been transferred to SRM?

Or in standard process there is no provision to reverse the situation after a PR is transferred from ECC to SRM.

Can anyone through some light on this?

Regards,

Sandeep Parab

[Former Member · Accepted solution]

Hi Sandeep,

by standard there is no option to send Reqs back to ECC. A moved Req is

blocked in ECC with a flag in EBAN, that sourcing is carried out externally. This

block is removed, when the PO is created. I implemented a push back mechanism

with an extra button in the sourcing cockpit within a classic environment. The

button first takes the SC information and identifies the Req in ECC, sets the

status on blank and releases the Req for sourcing. Finally the SC is deleted from

the sourcing cockpit. With a good programmer the story can be quickly done.

Cheers,

Claudia

Please reward points for useful answers.

[Former Member · Accepted solution]

Dear Claudia,

Thanks for your valuable inputs.

I am happy to hear that it is possible. Meanwhile can you talk to your technical person and share the funtion module or program to blank the PR profile from ECC. As we were unable to blank PR profile.

Regards,

Sandeep

[Former Member · Accepted solution]

Hi Sandeep,

the profile (T160PR / T160EX) does not need to be deleted. When a Req is pushed,

in EBAN table the flag is set for EBAN-EPROFILE = X. This is the flag, which

prevents the Req to be sourced in ECC. FM ME_UPDATE_REQUISITION

can be used.

Cheers,

Claudia

[yann_bouillut · Accepted solution]

Hi Claudia,

One question : ones the flag resetted in the PR, how do you do to exclude this PR from being collected for the next push to SRM ?

Kind regards,

Yann

[Former Member · Accepted solution]

Hi Yann,

it depends on the schedule of the automatic report for MRP Reqs. In such an

MRP environment a Req is taken back from SRM and then directly sourced in

ECC when there is a real reason for it. They do not sit there long.

I also enhanced EBAN with an extra field to manage an additional status as the

standard status management is not enough.

Cheers,

Claudia

[yann_bouillut · Accepted solution]

Hi Claudia,

Thanks for the clarrifications

Thus, if i understand it correctly, you update the CUF on EBAN while resetting the profile flag ?

Kind regards,

Yann

[Former Member · Accepted solution]

Hi Yann,

yes, and delete the SC in SRM from Sourcing Cockpit.

Cheers,

Claudia

[Former Member · Accepted solution]

Hi Claudia

Could you please help me, i have the same requirement and have a doubt.

As you described you created a button in sourcing cockpit that is used to rum a program that delete shopping cart from sourcing cockpit and with an RFC calls the FM ME_UPDATE_REQUISITION in ECC and change EBAN-EPROFILE and so requisition can be processed in ECC agaim.

My doubt Iis do you clear EBAN-EPROFILE or insert some other information.?

Thanks in advance.

Nilson

[Former Member]

Friends,

Can any one through some light on this issue?

Sandeep