Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

How to modify fields EKPO for RFQ on SAVE?

johndeconinck
Participant
0 Kudos
878

Dear Gurus,

We are trying to value/modify the fields of the EKPO table during the saving of an RFQ (transaction ME41, ME42 and ME47) according to certain rules. Unfortunately we cannot find the correct user exit that allows modifying the RFQ on position level during save. We already tried to look at enhancement MM06E005 and Badi ME_PURCHDOC_POSTED, but without result. Can anybody help?

Many thanks and kind regards,

John.

1 ACCEPTED SOLUTION

Sijin_Chandran
Active Contributor
0 Kudos
346

Hi John ,

I guess PO is created with reference to a RFQ.

So you can try creating a check while creating a PO with respect to a  RFQ .

Try with BADI ME_PROCESS_PO_CUST and while processing fetch RFQ details and Process accordingly.

5 REPLIES 5

Sijin_Chandran
Active Contributor
0 Kudos
347

Hi John ,

I guess PO is created with reference to a RFQ.

So you can try creating a check while creating a PO with respect to a  RFQ .

Try with BADI ME_PROCESS_PO_CUST and while processing fetch RFQ details and Process accordingly.

0 Kudos
346

Dear Sijin,

Thanks for your reply. It correct that we create a PO, but unfortunately we need the information before, during the printout of the RFQ. Any suggestions?

Many thanks,

John.

0 Kudos
346

Hi John ,

but unfortunately we need the information before, during the printout of the RFQ. Any suggestions?

You just need the information of PO while printing RFQ.

Then for that use the below link table link ,

EKPO-ANFNR = RFQ number.

EKPO is table for PO line item.

0 Kudos
346

Dear Sijin,

Thanks again for your prompt reply. We are not creating immediately the PO, since the RFQ has to go through a negotation/approval procedure first using SAP Workflow. The information on item level has to be therefore already available beforehand. If there's no user exit available, we'll have to settle with the implementation of an implicit enhancement spot before transaction ME41 calls the function module that updates the DB. If you have any other suggetions they would be most welcome and will be awarded.

Many thanks,

John De Coninck.

0 Kudos
346

Hi John ,

If you have got the option of Implicit Enhancement for ME41 then go with that .

Its one and the same , either you do it with a BADI / Customer Exit / User Exit.