BADI for CPPR to SRM sourcing

[Former Member]

Hello SRM Guru's

I have a requirement that I need to validate Purchase Organization Value when PReq is transfer from CPPR to SRM sourcing.

Is there any BADI available to validate the Preq document when it is being transferred from CPPR to SRM sourcing?

Because i need to transfer only the PReq which has Purchasing Organization number 'XXXX'. Others should spot transferring to SRM and write a error message.

In which system the BADI needs to be implemented (ECC or SRM)?

Expecting the BADI when

clicking the "Start collecting process" button of POWL applicatio

or

When clicking "transfer to central system " button .

Kindly advice me ...

Thanks.

Regards,

Magesh Basavaraj.

Edited by: mageshB on Feb 15, 2011 9:35 PM

[former_member183819]

Hi

In the Purchase request , there may not be purchase organisation data ..

[Former Member]

To transfer the PReqs from ECC to SRM, you might want to configure the ECC system, e.g. table T160EX, where you can specify the combination of material group and purchasing group for manual or automatic transfer. In your case, you might want to insert entries in that table with all purchasing groups which belong to the purchasing org you want and set them to EPROFILE = SR and MANUAL = space. I am not aware of any BADI that helps filter the REQs to be transferred to SRM. If any BADI, it has to be in ECC system.

[Former Member]

Hello Jay,

That verymuch for the help.

Could you please furnish me some more details below my doubts?

Wha t is the use of this table?

What does Manual and Automatic transfer?

Is there any impact in ECC (other process then CPPR) when maintaining data?

Is there any configuration to maitain data in to this table?

Right now in my table (T160EX) no entries are there . So what does it mean...

I would be great if you could furnish some more information, So That i can speak to business..

Thanks.

Regards,

Magesh.

[Former Member]

T160EX table etc is what was used in the pre-SRM7.0 releases for transferring ECC purchase requisition to SRM, the infrastructure of which is RFC. I am not entirely sure if CPPR has changed the framework in addition to using PI, but I suggest that you take a look at this Wiki posting for proper CPPR configuration:

http://wiki.sdn.sap.com/wiki/display/SRM/CPPR+Configuration

[Former Member]

Thanks to everyone..

We had resolved this issue by enhanced CPPR webDynpro component.

-Magesh