Community
Application Development and Automation 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
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

User exit for Delivery Module

Former Member

‎2008 Jan 18 7:00 AM

0 Likes
2,266

Hi ,

I had a include program in Development for Delivery module, "MV50AFZ1" in program "SAPMV50A", which is supposed to be a user exit. So I transported that to production on clients requirement, but then its creating some problems for client, so he wants his previous program to be back. But I can't change this "MV50AFZ1" program in development nor in Production. So how could I bring that previous code in production.

Plz help, and if possible tell me how can I change "MV50AFZ1" program code.

Thanks.

Shailesh.

Hi ,

I had a include program in Development for Delivery module, "MV50AFZ1" in program "SAPMV50A", which is supposed to be a user exit. So I transported that to production on clients requirement, but then its creating some problems for client, so he wants his previous program to be back. But I can't change this "MV50AFZ1" program in development nor in Production. So how could I bring that previous code in production.

Plz help, and if possible tell me how can I change "MV50AFZ1" program code.

Thanks.

Shailesh.

Reply
5 REPLIES 5
Read only

Former Member

‎2008 Jan 18 7:17 AM

0 Likes
1,472

Hi,

Just deactivate your enhancement in transaction CMOD.

Regards,

Renjith Michael.

Read only

Former Member
In response to Former Member

‎2008 Jan 18 7:25 AM

0 Likes
1,472

Thanks for your reply.

But I havent created this user exit through enhancement CMOD.

Can it still be deactivated. Since this is an include program in standard program, how can I deactivate it.

Plz reply.

Read only

Former Member
In response to Former Member

‎2008 Jan 18 7:33 AM

0 Likes
1,472

Hi,

Take the 'Z' include in transaction SE38 of your development system.

Comment the code. Save it in a transport request. Then transport it to the other servers.

You can also edit the Z include from SMOD also.

Regards,

Renjith Michael.

Read only

Former Member
In response to Former Member

‎2008 Jan 18 7:39 AM

0 Likes
1,472

Hi Ranjit,

Thanks for your efforts for me. But I know that we can edit Z includes from SE38. But my problem is I want *"MV50AFZP" * of "SAPMV50A" to be edited. Since both the copies of development and production were different. I think its possible to change the code, but whenever I try to edit , it asks for key. What should I do.

May be It sounds silly, but its requirement.

Plz help.

Read only

Former Member

‎2008 Jan 18 7:41 AM

0 Likes
1,472

check the below link for user exits in SD

http://help.sap.com/saphelp_46c/helpdata/en/1c/f62c7dd435d1118b3f0060b03ca329/content.htm

Some more links r here....

User Exits In Sales Document Processing

http://help.sap.com/saphelp_46c/helpdata/en/1c/f62c7dd435d1118b3f0060b03ca329/content.htm

Get the access key from basis for the program SAPMV45A. And change the screen.

First create a subscreen with that two fields, call that subscreen in the screen 8309.

call subscreen s2 including 'SAPMV45A' '9002'.

Here are the user exits available for creating PO.

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

EXIT_SAPMM06E_001 Other Number Range or Own Document Number

EXIT_SAPMM06E_004 User Exit for Cust.-Specific Control of Import Data Screens in Purchasing

EXIT_SAPMM06E_005 Field Selection Control: Vendor Address Screen

EXIT_SAPMM06E_006 Export Data to Customer Subscreen for Purchasing Document Header (PBO)

EXIT_SAPMM06E_007 Export Data to Customer Subscreen for Purchasing Document Header (PAI)

EXIT_SAPMM06E_008 Import Data from Customer Subscreen for Purchasing Document Header

EXIT_SAPMM06E_009 Reset Customer Data at Beginning of New Document (Without Dialog)

EXIT_SAPMM06E_010 Export of Service RFQ Data

EXIT_SAPMM06E_011 Import Service Prices for Quotation

EXIT_SAPMM06E_012 Check Customer-Specific Data Before Saving

EXIT_SAPMM06E_013 Update Customer-Specific Data in Purchasing Document

EXIT_SAPMM06E_014 Read Customer-Specific Data when Importing Purchasing Document

EXIT_SAPMM06E_016 Export Data to Customer Subscreen for Purchasing Document Item (PBO)

EXIT_SAPMM06E_017 Export Data to Customer Subscreen for Purchasing Document Item (PAI)

EXIT_SAPMM06E_018 Import Data from Customer Subscreen for Purchasing Document Item

EXIT_SAPMM06E_020 User Exit: Change Document for Requisitions (Conversion into PO)

EXIT_SAPMM06E_021 Fulfillment of Target Value: Release Orders Against a Contract

EXIT_SAPMM06E_022 Relevant Texts for "Texts Exist" Indicator

EXIT_SAPMM06E_023 Definition of Relevant Texts for "Texts Exist" Indicator

EXIT_SAPMM06E_024 Customer Enhancement: Activate PReq Block

Regards.