TO ADD TAB AT HEADER LEVEL IN ME21N

Question

Hi guys
I have to add a tab at header level of ME21N using BADI ME_GUI_PO_CUST and ME_PROCESS_PO_CUST
can someone guide me how to do this?
Thanks

Answer 1

Hi,
Try with SMOD enhancement MM06E005. I know this works well for adding a tab in PO header or item level . Read OSS 407975 for implementing this screen exit
here i am pasting OSS Notes and if you need clearly then login into service.sap.com
Symptom
You are using SAP customer enhancement MM06E005. There is no sample source code for this enhancement.
Other terms
User exit, customer enhancement, MM06E005, example, sample
Reason and Prerequisites
You want to activate user exit MM06E005. Note that this is a consulting note and not a correction of the user exit.
Solution
You can use the sample source code attached here to recognize the basic functions of the exit. This example is, however, only one of many options that are offered by the customer enhancement.
The sample source code includes the following functions:
Supply of an additional field on header level
Supply of an additional field on item level
Derivation of a field on item level from the copied reference document
Now, in order to be able to use the sample source code, you must create field ZZFLAG on the header level of the document and field ZZFIELD on the item level.
Double-click on Include table CI_EKKODB
Enter the following values:
Name    Component type DType Length DecPlace Short text
ZZFLAG  CHAR1          CHAR  1      0        1-digit indicator
Save and activate the include table.
Double-click on Include table CI_EKPODB
Enter the following values:
Name    Component type DType Length DecPlace Short Text
ZZFIELD CHAR1          CHAR  1      0        1-digit indicator
Save and activate the include table.
In order to activate the sample source code, you additionally have to carry out the following changes on screens 0101 and 0111.
1. Screen 0101: Create the following fields:
              "Checkbox"            Name: EKKO_CI-ZZFLAG
2. Screen 0111: Create the following fields:
              "Input/output field"  Name: EKPO_CI-ZZFIELD
              "Pushbutton"          Name: BUTTON
                                    FctCode: ZZDETERMINE
The following assignments apply to the sample source code:
EXIT_SAPMM06E_006  -->  LXM06F36
EXIT_SAPMM06E_007  -->  LXM06F38
EXIT_SAPMM06E_008  -->  LXM06F37
EXIT_SAPMM06E_009  -->  LXM06F39
EXIT_SAPMM06E_016  -->  LXM06F41
EXIT_SAPMM06E_017  -->  LXM06F42
EXIT_SAPMM06E_018  -->  LXM06F40
Copy the source code from the attachment and insert it into the corresponding function modules. Save and activate the function modules.
Create the following variables in the corresponding TOP include in order not to get any syntax errors:
  INCLUDE ZXM06TOP
data: gl_aktyp type c,
      gl_no_screen type c,
      gl_rekko like ekko,
      gl_ekko_ci like ekko_ci,
      gl_ekpo_ci like ekpo_ci,
      gl_ekpo like ekpo,
      gl_ucomm like sy-ucomm.
types: begin of ekpo_tab,
          ebeln like ekpo-ebeln,
          ebelp like ekpo-ebelp,
          ekpo like ekpo,
       end of ekpo_tab.
data:  gt_ref_ekpo_tab type table of ekpo_tab.
Save and activate the TOP include.
On header level, you can now store a character, X or space, via field ZZFLAG on the database with the document and read it also again.
On item level, you can fill field ZZFIELD with a one-digit value and save it with the document. If you copy this document, the system displays an additional function button on tab page "Customer data". If you press this button, the value of the reference document is copied to field ZZFIELD.
If you want to store the source code as sample source code in your system, start Transaction SMOD. Enter MM06E005 as an enhancement. Select "Components". Press "Change". Position the cursor on the corresponding module and choose "Sample code". Create the corresponding include and copy the source code from the note. Save the include. Note that, of course, syntax errors may occur when you check components. This is because the includes of the sample code are not integrated into a program but rather are completely independent and, therefore, do not have any relationship to each other either. For this reason, only save the include and do not activate or check it. The sample code has to be copied into the corresponding function modules in order to become active.
If you use the user exit in the new purchase order, it is not guaranteed that the customer screen is always processed. To make sure that possible required fields are checked, include a corresponding message into the EXIT_SAPMM06E_012. This screen is always processed.
Header Data
Release Status: Released for Customer
Released on: 07.09.2006  13:07:34
Priority: Recommendations/additional info
Category: Consulting
Primary Component: MM-PUR-PO Purchase Orders
Secondary Components: MM-PUR-GF-CE Customer Enhancements
I have not done BADI for PO,so i am not sure that whether BADI will work for Screen exit or not
Thanks
Seshu