BAPI

[Former Member]

I cant find any exits that satisfy my need i.e : i need to modify the exit upon release/reset of release strategy of PR using ME55 , is there any way i can use BAPI? and how does it work

[Former Member]

Hi,

What exactly you want to do?? explain the requirement briefly

[Former Member]

upon release/reset PR , i need to update the PR amount to my customised table so i was thinking that user exit might be the fastest way.

But the user exit is triggered only by ME54N(individual release) not in ME55(collective release) , whereas users use both tcodes for release.

I have searched BADI but there isnt any definition related for ME55, would BAPI be the solution for this problem

[Former Member]

Hi ester,

1. BAPI_PO_RELEASE

The above bapi is there for release.

2. But i don't think it will solve

your problem.

3. Because,

you want some TRIGGER

like user-exit so that

your code gets automatically exected

every time a po is released.

Wait for other answers till then.

regards,

amit m.

[Former Member]

Hi Ester ,

BAPI are like functiona modules.

They don't get triggerred.

One possible solution to your problem is to create a workflow.

That is after you release PR the PR table gets updated , then on updation trigger a workflow event.

Read the following thread on how to implement the logic.

[Former Member]

Dear Ester,

You are probably talking of BADI I suppose. Please go to tcode 'SPRO' and under 'Material Management' -> 'Purchasing' -> 'BADI' find the BADI's which suits you.

As such I'm enlisting all the exits for you, in case if you have missed anyone :-

Transaction Code - ME55 Collective Release of Purchase Reqs.

-

---

Exit Name

Description

-

---

AMPL0001	User subscreen for additional data on AMPL
LMEDR001	Enhancements to print program
LMELA002	Adopt batch no. from shipping notification when posting a GR
LMELA010	Inbound shipping notification: Transfer item data from IDOC
LMEQR001	User exit for source determination
LMEXF001	Conditions in Purchasing Documents Without Invoice Receipt
LWSUS001	Customer-Specific Source Determination in Retail
M06B0001	Role determination for purchase requisition release
M06B0002	Changes to comm. structure for purchase requisition release
M06B0003	Number range and document number
M06B0004	Number range and document number
M06B0005	Changes to comm. structure for overall release of requisn.
M06E0004	Changes to communication structure for release purch. doc.
M06E0005	Role determination for release of purchasing documents
ME590001	Grouping of requsitions for PO split in ME59
MEETA001	Define schedule line type (backlog, immed. req., preview)
MEFLD004	Determine earliest delivery date f. check w. GR (only PO)
MELAB001	Gen. forecast delivery schedules: Transfer schedule implem.
MEQUERY1	Enhancement to Document Overview ME21N/ME51N
MEVME001	WE default quantity calc. and over/ underdelivery tolerance
MM06E001	User exits for EDI inbound and outbound purchasing documents
MM06E003	Number range and document number
MM06E004	Control import data screens in purchase order
MM06E005	Customer fields in purchasing document
MM06E007	Change document for requisitions upon conversion into PO
MM06E008	Monitoring of contr. target value in case of release orders
MM06E009	Relevant texts for "Texts exist" indicator
MM06E010	Field selection for vendor address
MMAL0001	ALE source list distribution: Outbound processing
MMAL0002	ALE source list distribution: Inbound processing
MMAL0003	ALE purcasing info record distribution: Outbound processing
MMAL0004	ALE purchasing info record distribution: Inbound processing
MMDA0001	Default delivery addresses
MMFAB001	User exit for generation of release order
MRFLB001	Control Items for Contract Release Order

-

---

No of Exits: 35

Regards,

Deva.

[Former Member]

Hi Ester.

Read the following for the work flow related to release ofPR

http://help.sap.com/saphelp_47x200/helpdata/en/33/4c9a34272a5f2ee10000009b38f83b/frameset.htm