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: 

User exit on saving a scheduling agreement (ME31L)

Former Member
0 Kudos

Hi,

I'm looking for a user exit in transaction ME31L (create scheduling agreement and change) when saving the agreement.

I want to make 2 field mandatory via the userexit when people are saving the agreements.

Can somebody help me ?

thanks,

3 REPLIES 3

Former Member
0 Kudos

Hi,

Can't you write Field exits for those two fields!

Also check the following User Exits related to purchasing:

AMPL0001

User subscreen for additional AMPL data (manufacturer part number)

LMELA002

Adoption of batch number from shipping notification at time of posting of a goods receipt

LMELA010

Incoming shipping notification: adoption of item data from IDoc

LMEQR001

User exit for source determination

M06B0001

Role determination for release of requisitions

M06B0001

Changes to communication structure for release of requisitions

M06B0003

Number range and document number

M06B0004

Number range and document number

M06B0005

Changes to communication structure for overall release of purchase requisitions

M06E0004

Changes to communication structure for release of purchasing document

M06E0005

Role determination for release of purchasing documents

ME590001

Grouping of requisitions for PO split in transaction ME59

MEETA001

Determination of schedule line type (backlog, immediate requirement, forecast)

MEFLD004

Determination of earliest delivery date for checking at time of goods receipt (PO only)

MELAB001

Generation of forecast delivery schedule: realization via creation profile

MEQUERY1

Enhancement for document overview ME21N / ME51N

MEVME001

Calculation of default GR quantity and over/underdelivery tolerances

MM06E001

User exits for inbound EDI messages and outbound purchasing documents

MM06E003

Number range and document number

MM06E004

Control of import data screens in purchase orders

MM06E005

Customer fields in purchasing documents

MEREQ001

Customer's own data in purchase requisitions

MM06E007

Change document for requisitions when converting into POs

MM06E008

Monitoring of contract target value in case of release orders

MM06E009

Relevant texts for "Texts exist" indicator

MM06E010

Field selection for vendor address

MM06E011

Activation of requisition block

MM06L001

Exits for determination of ratings in vendor evaluation

MMAL0001

ALE source list distribution: outbound processing

MMAL0002

ALE source list distribution: inbound processing

MMAL0003

ALE purchasing info record distribution: outbound processing

MMAL0004

ALE purchasing info record distribution: inbound processing

MMDA0001

Default values for delivery addresses

MMFAB001

User exit for generation of releases

MRFLB001

Control items during release creation

LWBON001

Enhancement of LIS update through extension of the communication structure MCKONA (business volumes and rebate income)

LWBON003

Change settlement data for end-of-period rebate settlement before creation of settlement documents

LWSUS001

Customer-specific source determination in Retail

LMEXF001

Conditions in purchasing documents without invoice receipt

LMEKO002

Enhance communication structure KOMP for price determination

Regards,

Anji

Former Member
0 Kudos

Check with any one of the exit:


Transaction Code - ME31L                    Create Scheduling Agreement


 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            Individual customer 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.
 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
 MEQUERY1            Enhancement to Document Overview ME21N/ME51N
 MM06E011            Activate PReq Block
 LMEKO001            Extend communications structure KOMK for pricing
 LMEKO002            Extend communications structure KOMP for pricing


No of Exits:         38

Regards,

Vasanth

Former Member
0 Kudos

Thanks for the quick response. How does a field exit work ?

Do I have to create function module FIELD_EXIT_**** for my field ?

thanks,