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
Showing results for 
Search instead for 
Did you mean: 
Read only

MM06E005 functional exit

Former Member
0 Likes
7,354

Can anybody tell me what is the purpose of MM06E005 functional exit?

Regards,

pandu.

Can anybody tell me what is the purpose of MM06E005 functional exit?

Regards,

pandu.

1 REPLY 1
Read only

Former Member
0 Likes
3,746

This is an Enhancement package which has options to enhance functions and screens of some bussiness transaction which you can check from transaction SMOD.

Provide the name of the enhancement and press F8.

The programs, in which calls are made to these customer function modules which are there in this enhancement can be enhanced using this Customer exit.

The include tables are there so that the fields which you add in enhanced screen can be stored in system tables as enhancements.

This Enhancement MM06E005 Contains Some FM exits and Screen Exits to Enhance the Purchasing Transactions ME21(P.O), ME31 (Contracts) ME41( RFQ).

We can use this enhancement to Integrate Customer subscreens using the Screen Exits and Process the Logic using FM Exits.

The Fucntional Exit MM06E005 is the Enhancement for Customer fields in Purchasing document.

With this Enhancement ,

You can,

- Maintain/Supply your own Customer Fields in the Headers & Items of all Purchasing documents except Purchase Requisitions

- Update your own Customer-Specific Tables

You cannot,

- Change Standard Fields

- Change Data that depends on the Document Header in the Items

- Change Data that depends on an Item in the Document Header

INCLUDES

You incorporate your customer fields for the Document Header in the INCLUDE CI_EKKODB (in table EKKO).

You incorporate your customer fields for the Document Item in the INCLUDE CI_EKPODB (in table EKPO).

Dynpro Areas

If you use the Enhancement,U must create & generate the following dynpros (even if the dynpros are not going to be used):

- SAPLXM06 0101 Subscreen Header Purchase Order

- SAPLXM06 0201 Subscreen Header Outline Agreement

- SAPLXM06 0301 Subscreen Header RFQ

- SAPLXM06 0111 Subscreen Item Purchase Order

- SAPLXM06 0211 Subscreen Item Outline Agreement

- SAPLXM06 0311 Subscreen Item RFQ

You must identify all dynpros as subscreens. It is not necessary that they contain fields, but it is essential that they exist in order that no program abend occurs.

Functional Exits

The Dynpros are linked to the Standard Program via Function Modules.There are Function Modules that provide your subscreen with data (Export) and Function Modules that fetch data from your subscreens (Import).

-> Header Screens :

- 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 Header

-> Item Screens :

- EXIT_SAPMM06E_016 - Export Data to Customer Subscreen for Item (PBO)

- EXIT_SAPMM06E_017 - Export Data to Customer Subscreen for Item (PAI)

- EXIT_SAPMM06E_018 - Import Data from Customer Subscreen for Item

You can set or supply ur own data fields in the PBO Function Modules.

You receive the current (possibly changed viz a viz the PBO call) data of the standard program in the PAI Function Module.

You can return ur fields to the standard program in the Import Function Modules.

if you use the SMOD and activate the MM06E005

using SE80 you can add your fields with subscreens

SAPLXM06 0101 for Headerfields

SAPLXM06 0111 for Items.

This will add a tab in ME2..N.

if you want your own Text on the tabstrip just edit the Textsymbols

101 and 111 from SAPLXM06.

At output you have to open a module asking the gl_aktyp to switch edit/display mode.

then you must code the Exits to import/export values

***********************************

EXIT_SAPMM06E_006

***********************************

*

  • store transaction type for later modification of screen attributes

*

gl_aktyp = i_trtyp.

gl_no_screen = i_no_screen.

*

  • store current state of customer data in ekko_ci (structure for screen)

*

ekko_ci = i_ci_ekko.

*

  • store reference document

*

if i_rekko-ebeln ne gl_rekko-ebeln and

not i_rekko-ebeln is initial and

gl_rekko-ebeln is initial.

ekko_ci-zzemail = i_rekko-zzemail.

gl_rekko = i_rekko.

endif.

***********************************

EXIT_SAPMM06E_007

***********************************

move-corresponding i_ekko to gl_ekko_ci.

***********************************

EXIT_SAPMM06E_008

***********************************

e_ci_ekko = gl_ekko_ci.

*

  • ekko_ci contains the actual values of the Dynpro fields

  • e_ci_update is only set if you really want the fields

  • on the Dynpro to be saved. You must set it then to 'X'

  • the field ekko_ci-zzflag will here only be saved if there

  • was a change and the transaction is not in display mode

*

if gl_ekko_ci-zzemail ne ekko_ci-zzemail.

e_ci_ekko-zzemail = ekko_ci-zzemail.

if gl_aktyp ne 'A'.

e_ci_update = 'X'.

endif.

endif.

Rewards if useful...............

Minal