MM03 - Annex List

Hello, I need help for the following problem.
In MM03, you can view a list of annex. Also you can visualize a list of Notes or attachments for the material.
I need to retrieve from a material number all the titles and texts, from only the notes (RAW), to display it in a Smartform.
There's any function, table or any way to retrieve this data?
Thanks in advance

Thanks for the answer, but I think is more complicated than using READ_TEXT.
I find out that MF GOS_EXECUTE_SERVICE shows the popup of MM03, even the attch. but still my problem is access to data.

Similar Messages

Restoring keywords, part 4

I feel like I've sunk into a saga with no end and no one to help me except dear Curt Y. But here's what I'm concluding. The restoring or reactivation of keywords is a haphazard process at best and hardly documented, if at all. And yet maintaining your keywords is so important and takes such an investment of time! TO have this feature fail you, means that you are not going to have a very high opinion of Bridge, which is where I stand right now.
My keywords are slowly reappearing in the master list in the keywords panel without any discernible rhyme or reason, not by me anyway. Sometimes they reappear because I remembered the keyword and did a search for it. Sometimes they seem to reappear on their own (my theory is that if there was more than one keyword on an image and I searched for one of the keywords, I would get the other keywords as well. But this is only a hunch.)
If I have to bring all the keywords back into the list by searching for them, I'm in for a laborious process. I have a couple hundred keywords and I'm sure I can't remember them all.
I am currently without the ability to assign new keywords or old keywords to new images. If the keyword doesn't appear in the list, the documentation tells me that I can type the word into the box at the bottom of the keyword panel instead of checking the box next to the keyword in the list. But this does NOT connect to the keywords already established. For example, I have a keyword for "yellow," but it wasn't back in my list yet. I typed in "yellow" in the box and watched Bridge create an annexed list at the bottom of my truncated original list called "other keywords." So I now have a yellow in the first list and a yellow in the second list and not a clue on how to merge them.
Would I be correct in saying that Bridge is the ugly stepchild of Photoshop and that it suffers from neglect? It seems a rather unstable program to me, crashing out more often than Photoshop ever does. And there seems to be no documentation of the complicated but critically important business of getting your keywords up to speed after a clean install.
All help will be most gratefully received.

Cheska,
If I'm reading your plight correctly I may have found a solution to your problem.
I recently upgraded from Windows XP Pro SP3 x86 to Windows 7 Pro x64. After reinstalling the Adobe suite I found that my keyword check boxes were lost. I had spent much time setting up keywords for various groups that I shoot for. To restore them would take a lot of time. After some poking and prodding and testing I found a solution that works for me. I have CS3, hopefully this will work for you.
On the XP computer open Windows Explorer and locate the keywords file. The file that contains the keywords is:
Adobe Bridge Keywords.xml
Mine was located in:
C:\Documents and Settings\Steve\Application Data\Adobe\Bridge CS3
Copy the file so that you may put it on the new computer.
On the new computer locate the keyword file. Mine was in:
C:\Users\Steve\AppData\Roaming\Adobe\Bridge CS3
Rename the keyword file to:
Adobe Bridge Keywords.BAK
This is so that if something goes wrong you can restore it.
Copy the keyword file from the old computer to the folder that has it on the new one.
Open Bridge and VOILA! there they are!

Display MM03 screen with out selecting views using interactive list.

Hi Experts,
I have one query, I am displaying material data in a list. when i click on material number in the list it should show material data i.e should call MM03 with all the view data .
When i am using call transaction 'MM03' skip first screen. I am able to call MM03 screen but unable to skip the View Pop up screen it should be selected default and the veiw data should be displayed.
Ex: when i am clicking on materil number from the list it will directly take to the Basic data1 screen with out the pop up screen for selecting views.
hope this is clear...
Thanks
Sunil kairam.

Hi Dzed Maroz ,
Thanks for the quick reply... its works.. !
Can you please tell me the methodology behind SET PARAMETER ID 'MXX' FIELD 'K'.
I was trying using below code earlier was showing the pop up screen.
SET PARAMETER ID 'MAT' FIELD P_MATNR. "
CALL TRANSACTION 'MM03' AND SKIP FIRST SCREEN.
but now it works... thanks..
kindly explain SET PARAMETER ID 'MXX' FIELD 'K'. hw it works... which filed parmeter id is MXX and y we have choosen 'K' ??
Thanks & Regards
Sunil kairam

Option disabled Insert in personal list in MM03 search

Hi All,
I am trying to get the option of "Insert in Personal list" while doing material search in MM03 and it is not enabled for me. But the same is enabled for my colleague. We both are using same GUI version 720 and same user settings but still that option does not works for me.
Can you please help with some thoughts?
Regards,
Karun

Hi,
   You may check the below options:
   1. Check whether any user specific transaction variant has been created for MM03 in SHD0 transaction. If so, deactivate it and test the scenario again.
   2. Insert /nSU53 from the MM03 screen and check whether any authorization is missing.
   3. Check whether any development is altering the standard behavior.
Regards,
AKPT

What is the reason for stock/requirements list disabled in MM03

Hi,
I hv a problem where display a material in MM03, the stock/requirements list is disable. When run in MD04, error date comes after end of valid factory calendar. (Please correct)
I hv corrected the PO delivery date but still the same, wht shld I check now ?
Thanks in advance for anyone reply my question.

extend your factory calendar using transaction SCAL
What you described has probably to do with some field values entered in the material master like delivery days, planning time fence ....
which make the planning determine a date for that you dont have a factory calendar.

How to include a Header in Hierarchy List (ALV)?

Hi Gurus,
If we need to include any header in ALV Grid, then we generate an event and pass that header to TOP_OF_PAGE event. We do have I_CALLBACK_TOP_OF_PAGE parameter for the REUSE_ALV_GRID_DISPLAY function module.
But how do I generate a Header for a Hierarchy List? I do not find any parameter for TOP_OF_PAGE event. Please help with inputs.
Regards,
Kiran

Hi Kiran,
            The following codes are very useful to you...
If any problem let me know...
REPORT zxxxxxxxxxxxxxx    LINE-SIZE 220
                           LINE-COUNT 50(5).
*&                       DATA DECLARATION                              *
TABLES: MARA,                      "GENERAL MASTER DATA
        MARC,                      "PLANT DATA FOR MATERIAL
        MARD,                      "STORAGE LOCATION DATA FOR MATERIAL
        MBEW,                      "MATERIAL VALUATION
        MVKE,                      "SALES DATA FOR MATERIAL
        MAKT,                      "MATERIAL DESCRIPTION
        EKKO,                      "PURCHASING DOCUMENT HEADER
        EKPO,                      "PURCHASING DOCUMENT ITEM
        VBAK,                      "SALES DOCUMENT HEADER DATA
        VBAP.                      "SALES DOCUMENT ITEM DATA
TYPE-POOLS : SLIS.
DATA: VT_FIELDCAT1 TYPE SLIS_T_FIELDCAT_ALV,
      V_FIELDCAT TYPE SLIS_FIELDCAT_ALV,
      V_LAYOUT TYPE SLIS_LAYOUT_ALV,
      BDCDATA LIKE BDCDATA OCCURS 0 WITH HEADER LINE,
      BEGIN OF I_MARA OCCURS 0,
         MATNR LIKE MARA-MATNR, "MATERIAL NUMBER
         MBRSH LIKE MARA-MBRSH, "INDUSTRY SECTOR
         MEINS LIKE MARA-MEINS, "BASE UNIT OF MEASURE
         MATKL LIKE MARA-MATKL, "MATERIAL GROUP
      END OF I_MARA,
      BEGIN OF I_MARC OCCURS 0,
         MATNR LIKE MARC-MATNR, "MATERIAL NUMBER
         WERKS LIKE MARC-WERKS, "PLANT
         LVORM LIKE MARC-LVORM, "FLAG MATERIAL FOR DELETION AT PLANT
                                  "LEVEL
         DISPO LIKE MARC-DISPO, "MRP CONTROLLER
      END OF I_MARC,
      BEGIN OF I_MAKT OCCURS 0,
         MATNR LIKE MAKT-MATNR, "MATERIAL NUMBER
         MAKTX LIKE MAKT-MAKTX, "MATERIAL DESCRIPTION
         SPRAS LIKE MAKT-SPRAS, "LANGUAGE KEY
      END OF I_MAKT,
      BEGIN OF I_MVKE OCCURS 0,
         MATNR LIKE MVKE-MATNR, "MATERIAL NUMBER
         VKORG LIKE MVKE-VKORG, "SALES ORGANIZATION
         VTWEG LIKE MVKE-VTWEG, "DISTRIBUTION CHANNEL
      END OF I_MVKE,
      BEGIN OF I_MARD OCCURS 0,
        MATNR LIKE MARD-MATNR, "MATERIAL NUMBER
        LGORT LIKE MARD-LGORT, "STORAGE LOCATION
        LABST LIKE MARD-LABST, "VALUATED STOCK WITH UNRESTRICTED USE
      END OF I_MARD,
      BEGIN OF I_EKPO OCCURS 0,
        EBELN LIKE EKPO-EBELN, "PURCHASING DOCUMENT NUMBER
        EBELP LIKE EKPO-EBELP, "ITEM NUMBER OF PURCHASING DOCUMENT
        MATNR LIKE EKPO-MATNR, "MATERIAL NUMBER
      END OF I_EKPO,
      BEGIN OF I_VBAP OCCURS 0,
        VBELN LIKE VBAP-VBELN, "SALES DOCUMENT
        POSNR LIKE VBAP-POSNR, "SALES DOCUMENT ITEM
        MATNR LIKE VBAP-MATNR, "MATERIAL NUMBER
      END OF I_VBAP,
      BEGIN OF I_OUT OCCURS 0,
        MATNR LIKE MARC-MATNR,
        WERKS LIKE MARC-WERKS,
        LVORM LIKE MARC-LVORM,
        DISPO LIKE MARC-DISPO,
        MBRSH LIKE MARA-MBRSH,
        MEINS LIKE MARA-MEINS,
        MATKL LIKE MARA-MATKL,
        VKORG LIKE MVKE-VKORG,
        VTWEG LIKE MVKE-VTWEG,
        SPRAS LIKE MAKT-SPRAS,
        MAKTX LIKE MAKT-MAKTX,
        LGORT LIKE MARD-LGORT,
        LABST LIKE MARD-LABST,
        EBELN LIKE EKPO-EBELN,
        EBELP LIKE EKPO-EBELP,
        VBELN LIKE VBAP-VBELN,
        POSNR LIKE VBAP-POSNR,
      END OF I_OUT,
      BEGIN OF I_HEADING OCCURS 0,
        TEXT1(20),
        TEXT2(20),
        TEXT3(20),
        TEXT4(20),
        TEXT5(20),
        TEXT6(20),
        TEXT7(20),
        TEXT8(20),
        TEXT9(20),
        TEXT10(20),
        TEXT11(40),
        TEXT12(20),
        TEXT13(20),
        TEXT14(20),
        TEXT15(20),
        TEXT16(20),
        TEXT17(20),
      END OF I_HEADING.
*&                   S E L E C T I O N - S C R E E N                   *
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-100.
SELECT-OPTIONS: S_MATNR FOR MARA-MATNR. "OBLIGATORY.
PARAMETERS: P_WERKS LIKE MARC-WERKS. "OBLIGATORY.
SELECT-OPTIONS: S_LGORT FOR MARD-LGORT,
                S_DISPO FOR MARC-DISPO,
                S_EBELN FOR EKPO-EBELN .
SELECTION-SCREEN END OF BLOCK B1.
SELECTION-SCREEN BEGIN OF BLOCK B2 WITH FRAME TITLE TEXT-101.
PARAMETERS : RB1 RADIOBUTTON GROUP G1,
             RB2 RADIOBUTTON GROUP G1,
             RB3 RADIOBUTTON GROUP G1.
SELECTION-SCREEN END OF BLOCK B2.
*&             S T A R T - O F - S E L E C T I O N                     *
START-OF-SELECTION.
SELECT MATNR WERKS LVORM DISPO FROM MARC
INTO CORRESPONDING FIELDS OF TABLE I_MARC
                      WHERE MATNR IN S_MATNR
                      AND DISPO IN S_DISPO
                      AND WERKS = P_WERKS.
IF I_MARC[] IS INITIAL.
    WRITE:/ 'NO MATCHING DATA AVAILABLE FROM MARC'.
    EXIT.
ENDIF.
PERFORM PURCHASEDATA_VALIDATION.
PERFORM SALESDATA_VALIDATION.
SELECT MATNR LGORT LABST FROM MARD INTO TABLE I_MARD
                      FOR ALL ENTRIES IN I_MARC
                      WHERE MATNR = I_MARC-MATNR
                      AND WERKS EQ P_WERKS
                      AND LGORT IN S_LGORT.
IF I_MARD[] IS INITIAL.
    WRITE:/ 'NO MATCHING DATA AVAILABLE FROM MARD'.
    EXIT.
ENDIF.
SELECT MATNR VKORG VTWEG FROM MVKE INTO TABLE I_MVKE
                      FOR ALL ENTRIES IN I_MARC
                      WHERE MATNR = I_MARC-MATNR.
IF I_MVKE[] IS INITIAL.
    WRITE:/ 'NO MATCHING DATA AVAILABLE FROM MVKE'.
    EXIT.
ENDIF.
LOOP AT I_MARC.
    MOVE-CORRESPONDING I_MARC TO I_OUT.
    CLEAR MARC.
    SELECT SINGLE MATNR MBRSH MEINS MATKL FROM MARA
                      INTO CORRESPONDING FIELDS OF MARA
                      WHERE MATNR = I_OUT-MATNR.
    IF SY-SUBRC = 0.
      MOVE: MARA-MBRSH TO I_OUT-MBRSH,
            MARA-MEINS TO I_OUT-MEINS,
            MARA-MATKL TO I_OUT-MATKL.
    ELSE.
      CONTINUE.
    ENDIF.
    SELECT SINGLE MATNR MAKTX SPRAS FROM MAKT
                    INTO CORRESPONDING FIELDS OF MAKT
                    WHERE MATNR = I_OUT-MATNR.
    IF SY-SUBRC = 0.
      MOVE: MAKT-MAKTX TO I_OUT-MAKTX,
            MAKT-SPRAS TO I_OUT-SPRAS.
    ELSE.
      CONTINUE.
    ENDIF.
    LOOP AT I_EKPO WHERE MATNR = I_MARC-MATNR.
      MOVE: I_EKPO-EBELN TO I_OUT-EBELN,
            I_EKPO-EBELP TO I_OUT-EBELP.
    ENDLOOP.
    LOOP AT I_VBAP WHERE MATNR = I_MARC-MATNR.
      MOVE: I_VBAP-VBELN TO I_OUT-VBELN,
            I_VBAP-POSNR TO I_OUT-POSNR.
    ENDLOOP.
    LOOP AT I_MARD WHERE MATNR = I_MARC-MATNR.
      MOVE: I_MARD-LABST TO I_OUT-LABST,
            I_MARD-LGORT TO I_OUT-LGORT.
    ENDLOOP.
    LOOP AT I_MVKE WHERE MATNR = I_MARC-MATNR.
      MOVE: I_MVKE-VKORG TO I_OUT-VKORG,
            I_MVKE-VTWEG TO I_OUT-VTWEG.
      APPEND I_OUT.
    ENDLOOP.
    CLEAR I_OUT.
ENDLOOP.
PERFORM OPTIONS.
                     FORM OPTIONS                                *
FORM OPTIONS.
IF RB2 = 'X'.
    PERFORM FIELDCAT.
    PERFORM OUTPUT.
ELSE.
    IF RB1 = 'X'.
      PERFORM HEADINGS.
      PERFORM DLOAD.
    ELSE.
      IF RB3 = 'X'.
        PERFORM HEADINGS.
        PERFORM DLOAD.
        PERFORM FIELDCAT.
        PERFORM OUTPUT.
      ENDIF.
    ENDIF.
ENDIF.
ENDFORM.                    "OPTIONS
                     FORM HEADINGS                               *
FORM HEADINGS.
I_HEADING-TEXT1 = 'MATNR'.
I_HEADING-TEXT2 = 'WERKS'.
I_HEADING-TEXT3 = 'LVORM'.
I_HEADING-TEXT4 = 'DISPO'.
I_HEADING-TEXT5 = 'MBRSH'.
I_HEADING-TEXT6 = 'MEINS'.
I_HEADING-TEXT7 = 'MATKL'.
I_HEADING-TEXT8 = 'VKORG'.
I_HEADING-TEXT9 = 'VTWEG'.
I_HEADING-TEXT10 = 'SPRAS'.
I_HEADING-TEXT11 = 'MAKTX'.
I_HEADING-TEXT12 = 'LGORT'.
I_HEADING-TEXT13 = 'LABST'.
I_HEADING-TEXT14 = 'EBELN'.
I_HEADING-TEXT15 = 'EBELP'.
I_HEADING-TEXT16 = 'VBELN'.
I_HEADING-TEXT17 = 'POSNR'.
APPEND I_HEADING.
ENDFORM.                    "HEADINGS
                     FORM DLOAD                                  *
FORM DLOAD.
CALL FUNCTION 'GUI_DOWNLOAD'
    EXPORTING
      FILENAME              = 'C:\MATSTK.XLS'
      FILETYPE              = 'DAT'
      WRITE_FIELD_SEPARATOR = 'X'
    TABLES
      DATA_TAB              = I_HEADING
    EXCEPTIONS
      FILE_WRITE_ERROR      = 1.
CALL FUNCTION 'GUI_DOWNLOAD'
    EXPORTING
      FILENAME              = 'C:\MATSTK.XLS'
      FILETYPE              = 'DAT'
      APPEND                = 'X'
      WRITE_FIELD_SEPARATOR = 'X'
    TABLES
      DATA_TAB              = I_OUT.
ENDFORM.                    "DLOAD
                          FORM FIELDCAT                          *
FORM FIELDCAT.
V_FIELDCAT-COL_POS = '1'.
V_FIELDCAT-FIELDNAME     = 'MATNR'.
V_FIELDCAT-TABNAME = 'I_OUT'.
V_FIELDCAT-HOTSPOT = 'X'.
V_FIELDCAT-REF_FIELDNAME = 'MATNR'.
V_FIELDCAT-REF_TABNAME   = 'MARC'.
APPEND V_FIELDCAT TO VT_FIELDCAT1.
CLEAR V_FIELDCAT.
V_FIELDCAT-COL_POS = '2'.
V_FIELDCAT-FIELDNAME     = 'WERKS'.
V_FIELDCAT-TABNAME = 'I_OUT'.
V_FIELDCAT-REF_FIELDNAME = 'WERKS'.
V_FIELDCAT-REF_TABNAME   = 'MARC'.
APPEND V_FIELDCAT TO VT_FIELDCAT1.
CLEAR V_FIELDCAT.
V_FIELDCAT-COL_POS = '3'.
V_FIELDCAT-FIELDNAME     = 'LVORM'.
V_FIELDCAT-TABNAME = 'I_OUT'.
V_FIELDCAT-REF_FIELDNAME = 'LVORM'.
V_FIELDCAT-REF_TABNAME   = 'MARC'.
APPEND V_FIELDCAT TO VT_FIELDCAT1.
CLEAR V_FIELDCAT.
V_FIELDCAT-COL_POS = '4'.
V_FIELDCAT-FIELDNAME     = 'DISPO'.
V_FIELDCAT-TABNAME = 'I_OUT'.
V_FIELDCAT-REF_FIELDNAME = 'DISPO'.
V_FIELDCAT-REF_TABNAME   = 'MARC'.
APPEND V_FIELDCAT TO VT_FIELDCAT1.
CLEAR V_FIELDCAT.
V_FIELDCAT-COL_POS = '5'.
V_FIELDCAT-FIELDNAME     = 'MBRSH'.
V_FIELDCAT-TABNAME = 'I_OUT'.
V_FIELDCAT-REF_FIELDNAME = 'MBRSH'.
V_FIELDCAT-REF_TABNAME   = 'MARA'.
APPEND V_FIELDCAT TO VT_FIELDCAT1.
CLEAR V_FIELDCAT.
V_FIELDCAT-COL_POS = '6'.
V_FIELDCAT-FIELDNAME     = 'MEINS'.
V_FIELDCAT-TABNAME = 'I_OUT'.
V_FIELDCAT-REF_FIELDNAME = 'MEINS'.
V_FIELDCAT-REF_TABNAME   = 'MARA'.
APPEND V_FIELDCAT TO VT_FIELDCAT1.
CLEAR V_FIELDCAT.
V_FIELDCAT-COL_POS = '7'.
V_FIELDCAT-FIELDNAME     = 'MATKL'.
V_FIELDCAT-TABNAME = 'I_OUT'.
V_FIELDCAT-REF_FIELDNAME = 'MATKL'.
V_FIELDCAT-REF_TABNAME   = 'MARA'.
APPEND V_FIELDCAT TO VT_FIELDCAT1.
CLEAR V_FIELDCAT.
V_FIELDCAT-COL_POS = '8'.
V_FIELDCAT-FIELDNAME     = 'VKORG'.
V_FIELDCAT-TABNAME = 'I_OUT'.
V_FIELDCAT-REF_FIELDNAME = 'VKORG'.
V_FIELDCAT-REF_TABNAME   = 'MVKE'.
APPEND V_FIELDCAT TO VT_FIELDCAT1.
CLEAR V_FIELDCAT.
V_FIELDCAT-COL_POS = '9'.
V_FIELDCAT-FIELDNAME     = 'VTWEG'.
V_FIELDCAT-TABNAME = 'I_OUT'.
V_FIELDCAT-REF_FIELDNAME = 'VTWEG'.
V_FIELDCAT-REF_TABNAME   = 'MVKE'.
APPEND V_FIELDCAT TO VT_FIELDCAT1.
CLEAR V_FIELDCAT.
V_FIELDCAT-COL_POS = '10'.
V_FIELDCAT-FIELDNAME     = 'SPRAS'.
V_FIELDCAT-TABNAME = 'I_OUT'.
V_FIELDCAT-REF_FIELDNAME = 'SPRAS'.
V_FIELDCAT-REF_TABNAME   = 'MAKT'.
APPEND V_FIELDCAT TO VT_FIELDCAT1.
CLEAR V_FIELDCAT.
V_FIELDCAT-COL_POS = '11'.
V_FIELDCAT-FIELDNAME     = 'MAKTX'.
V_FIELDCAT-TABNAME = 'I_OUT'.
V_FIELDCAT-REF_FIELDNAME = 'MAKTX'.
V_FIELDCAT-REF_TABNAME   = 'MAKT'.
APPEND V_FIELDCAT TO VT_FIELDCAT1.
CLEAR V_FIELDCAT.
V_FIELDCAT-COL_POS = '12'.
V_FIELDCAT-FIELDNAME     = 'LGORT'.
V_FIELDCAT-TABNAME = 'I_OUT'.
V_FIELDCAT-REF_FIELDNAME = 'LGORT'.
V_FIELDCAT-REF_TABNAME   = 'MARD'.
V_FIELDCAT-SELTEXT_L = 'STRG LOCT'.
V_FIELDCAT-OUTPUTLEN = 10.
APPEND V_FIELDCAT TO VT_FIELDCAT1.
CLEAR V_FIELDCAT.
V_FIELDCAT-COL_POS = '13'.
V_FIELDCAT-FIELDNAME     = 'LABST'.
V_FIELDCAT-TABNAME = 'I_OUT'.
V_FIELDCAT-SELTEXT_M = 'STOCK'.
V_FIELDCAT-OUTPUTLEN = 15.
V_FIELDCAT-REF_FIELDNAME = 'LABST'.
V_FIELDCAT-REF_TABNAME   = 'MARD'.
V_FIELDCAT-DO_SUM = 'X'.
V_LAYOUT-TOTALS_TEXT = 'TOTAL STOCK:'.
V_FIELDCAT-HOTSPOT = 'X'.
APPEND V_FIELDCAT TO VT_FIELDCAT1.
CLEAR V_FIELDCAT.
V_FIELDCAT-COL_POS = '14'.
V_FIELDCAT-FIELDNAME     = 'EBELN'.
V_FIELDCAT-TABNAME = 'I_OUT'.
V_FIELDCAT-HOTSPOT = 'X'.
V_FIELDCAT-REF_FIELDNAME = 'EBELN'.
V_FIELDCAT-REF_TABNAME   = 'EKPO'.
APPEND V_FIELDCAT TO VT_FIELDCAT1.
CLEAR V_FIELDCAT.
V_FIELDCAT-COL_POS = '15'.
V_FIELDCAT-FIELDNAME     = 'EBELP'.
V_FIELDCAT-TABNAME = 'I_OUT'.
V_FIELDCAT-REF_FIELDNAME = 'EBELP'.
V_FIELDCAT-REF_TABNAME   = 'EKPO'.
APPEND V_FIELDCAT TO VT_FIELDCAT1.
CLEAR V_FIELDCAT.
V_FIELDCAT-COL_POS = '16'.
V_FIELDCAT-FIELDNAME     = 'VBELN'.
V_FIELDCAT-TABNAME = 'I_OUT'.
V_FIELDCAT-HOTSPOT = 'X'.
V_FIELDCAT-REF_FIELDNAME = 'VBELN'.
V_FIELDCAT-REF_TABNAME   = 'VBAP'.
APPEND V_FIELDCAT TO VT_FIELDCAT1.
CLEAR V_FIELDCAT.
V_FIELDCAT-COL_POS = '17'.
V_FIELDCAT-FIELDNAME     = 'POSNR'.
V_FIELDCAT-TABNAME = 'I_OUT'.
V_FIELDCAT-REF_FIELDNAME = 'POSNR'.
V_FIELDCAT-REF_TABNAME   = 'VBAP'.
APPEND V_FIELDCAT TO VT_FIELDCAT1.
CLEAR V_FIELDCAT.
ENDFORM.                      "FIELDCAT
                          FORM OUTPUT                            *
FORM OUTPUT.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
      I_CALLBACK_PROGRAM      = SY-REPID
      I_CALLBACK_TOP_OF_PAGE = 'TOP-OF-PAGE'
      I_GRID_TITLE = 'CLICK ON MATERIAL/PURDOC/SALESDOC FOR DETAILS'
      I_CALLBACK_USER_COMMAND = 'DISPLAYDETAILS'
      IS_LAYOUT               = V_LAYOUT
      IT_FIELDCAT             = VT_FIELDCAT1
    TABLES
      T_OUTTAB                = I_OUT.
IF SY-SUBRC <> 0.
ENDIF.
ENDFORM.                    "OUTPUT
                        FORM TOP-OF-PAGE                         *
FORM TOP-OF-PAGE.
DATA: T_HEADER TYPE SLIS_T_LISTHEADER,
        WA_HEADER TYPE SLIS_LISTHEADER.
WA_HEADER-TYP = 'H'.
WA_HEADER-INFO = 'REPORT FOR : '.
APPEND WA_HEADER TO T_HEADER.
CLEAR WA_HEADER.
WA_HEADER-TYP = 'S'.
WA_HEADER-INFO = 'MATERIAL DETAILS'.
APPEND WA_HEADER TO T_HEADER.
CLEAR WA_HEADER.
WA_HEADER-TYP = 'S'.
WA_HEADER-INFO = 'PURCHASE ORDER DETAILS'.
APPEND WA_HEADER TO T_HEADER.
CLEAR WA_HEADER.
WA_HEADER-TYP = 'S'.
WA_HEADER-INFO = 'SALES ORDER DETAILS'.
APPEND WA_HEADER TO T_HEADER.
CLEAR WA_HEADER.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
    EXPORTING
      I_LOGO             = 'GEAR'
      IT_LIST_COMMENTARY = T_HEADER.
ENDFORM.                    "TOP-OF-PAGE
*&                       FORM DISPLAYDETAILS                          *
FORM DISPLAYDETAILS USING UCOMM LIKE SY-UCOMM
      SELFIELD TYPE SLIS_SELFIELD.
IF SELFIELD-FIELDNAME = 'EBELN'.
    IF UCOMM = '&IC1'.
      READ TABLE I_OUT INDEX SELFIELD-TABINDEX.
      PERFORM PORECDNG.
      CLEAR BDCDATA[].
    ENDIF.
ELSE.
    IF SELFIELD-FIELDNAME = 'MATNR'.
      IF UCOMM = '&IC1'.
        READ TABLE I_OUT INDEX SELFIELD-TABINDEX.
        PERFORM MMRECDNG.
        CLEAR BDCDATA[].
      ENDIF.
    ELSE.
      IF SELFIELD-FIELDNAME = 'VBELN'.
        IF UCOMM = '&IC1'.
          READ TABLE I_OUT INDEX SELFIELD-TABINDEX.
          PERFORM SALESRECDNG.
          CLEAR BDCDATA[].
        ENDIF.
      ENDIF.
    ENDIF.
ENDIF.
ENDFORM.                    "DISPLAYDETAILS
                    FORM PORECDNG                                   *
FORM PORECDNG.
perform bdc_dynpro      using 'SAPMM06E' '0105'.
perform bdc_field       using 'BDC_CURSOR'
                              'RM06E-BSTNR'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'RM06E-BSTNR'
                              I_OUT-EBELN.
perform bdc_dynpro      using 'SAPMM06E' '0120'.
perform bdc_field       using 'BDC_CURSOR'
                              'RM06E-BSTPO(01)'.
perform bdc_field       using 'BDC_OKCODE'
                              '=AH'.
perform bdc_field       using 'RM06E-EBELP'
                              I_OUT-EBELP.
perform bdc_field       using 'RM06E-TCSELFLAG(01)'
                              'X'.
perform bdc_transaction using 'ME23'.
ENDFORM.                    "PORECDNG
                    FORM MMRECDNG                                   *
FORM MMRECDNG.
PERFORM BDC_DYNPRO      USING 'SAPLMGMM' '0060'.
PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                                'RMMG1-MATNR'.
PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                                '/00'.
PERFORM BDC_FIELD       USING 'RMMG1-MATNR'
                                I_OUT-MATNR.
PERFORM BDC_DYNPRO      USING 'SAPLMGMM' '0070'.
PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                                'MSICHTAUSW-DYTXT(01)'.
PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                                '=ENTR'.
PERFORM BDC_FIELD       USING 'MSICHTAUSW-KZSEL(01)'
                                'X'.
PERFORM BDC_TRANSACTION USING 'MM03'.
ENDFORM.                    "MMRECDNG
                    FORM SALESRECDNG                                *
FORM SALESRECDNG.
PERFORM BDC_DYNPRO      USING 'SAPMV45A' '0102'.
PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                                'VBAK-VBELN'.
PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                                '/00'.
PERFORM BDC_FIELD       USING 'VBAK-VBELN'
                                I_OUT-VBELN.
PERFORM BDC_TRANSACTION USING 'VA03'.
ENDFORM.                    "SALESRECDNG
                 FORM BDC_TRANSACTION                               *
FORM BDC_TRANSACTION USING TCODE.
CALL TRANSACTION TCODE USING BDCDATA MODE 'E'.
ENDFORM.                    "BDC_TRANSACTION
                       FORM BDC_DYNPRO                              *
FORM BDC_DYNPRO USING PROGRAM DYNPRO.
CLEAR BDCDATA.
BDCDATA-PROGRAM = PROGRAM.
BDCDATA-DYNPRO = DYNPRO.
BDCDATA-DYNBEGIN = 'X'.
APPEND BDCDATA.
ENDFORM.                    "BDC_DYNPRO
                       INSERT FIELD                                  *
FORM BDC_FIELD USING FNAM FVAL.
CLEAR BDCDATA.
BDCDATA-FNAM = FNAM.
BDCDATA-FVAL = FVAL.
APPEND BDCDATA.
ENDFORM.                    "BDC_FIELD
*&                  FORM PURCHASEDATA_VALIDATION                      *
FORM PURCHASEDATA_VALIDATION.
SELECT EBELN EBELP MATNR
             FROM EKPO
             INTO TABLE I_EKPO
             FOR ALL ENTRIES IN I_MARC
             WHERE MATNR = I_MARC-MATNR
             AND EBELN IN S_EBELN
             AND WERKS EQ P_WERKS.
IF I_EKPO[] IS INITIAL.
    WRITE:/ 'NO MATCHING DATA IS SELECTED FROM TABLE EKPO'.
    EXIT.
ENDIF.
DATA: T_EKPO LIKE I_EKPO OCCURS 0 WITH HEADER LINE.
T_EKPO[] = I_EKPO[].
REFRESH I_EKPO.
FREE I_EKPO.
LOOP AT T_EKPO.
    SELECT SINGLE EBELN FROM EKKO INTO EKPO-EBELN
    WHERE EBELN = T_EKPO-EBELN.
    IF SY-SUBRC = 0.
      MOVE-CORRESPONDING T_EKPO TO I_EKPO.
      APPEND I_EKPO.
      CLEAR I_EKPO.
    ELSE.
      CONTINUE.
    ENDIF.
ENDLOOP.
SORT I_EKPO.
ENDFORM.                    "PURCHASEDATA_VALIDATION
*&                  FORM SALESDATA_VALIDATION                         *
FORM SALESDATA_VALIDATION.
SELECT VBELN POSNR MATNR
          FROM VBAP
          INTO CORRESPONDING FIELDS OF TABLE
          I_VBAP FOR ALL ENTRIES IN I_MARC
          WHERE MATNR = I_MARC-MATNR.
DATA: T_VBAP LIKE I_VBAP OCCURS 0 WITH HEADER LINE.
T_VBAP[] = I_VBAP[].
REFRESH I_VBAP.
FREE I_VBAP.
LOOP AT T_VBAP.
    SELECT SINGLE VBELN FROM VBAK INTO VBAK-VBELN
    WHERE VBELN = T_VBAP-VBELN.
    IF SY-SUBRC = 0.
      MOVE-CORRESPONDING T_VBAP TO I_VBAP.
      APPEND I_VBAP.
      CLEAR I_VBAP.
    ELSE.
      CONTINUE.
    ENDIF.
ENDLOOP.
SORT I_VBAP.
ENDFORM.                    "SALESDATA_VALIDATION
..........................FOr Hierarchy List...................
REPORT Zxxxxxxxxxx NO STANDARD PAGE HEADING.
**********DECLARING TABLES********************************************
TYPE-POOLS: slis.
TABLES: EKKO, "PO HEADER
        EKPO. "PO ITEM
**********DECLARING DATA**********************************************
DATA: ET_EKKO TYPE EKKO OCCURS 0 WITH HEADER LINE,
      ET_EKPO TYPE EKPO OCCURS 0 WITH HEADER LINE,
      ET_SORT TYPE SLIS_T_SORTINFO_ALV WITH HEADER LINE,
      ET_LAYOUT TYPE SLIS_LAYOUT_ALV,
      ET_KEYINFO TYPE SLIS_KEYINFO_ALV,
      ET_REPID LIKE SY-REPID.
DATA: ET_FIELDCAT TYPE SLIS_T_FIELDCAT_ALV WITH HEADER LINE.
DATA: ET_EVENTS TYPE SLIS_T_EVENT.
**********SELECTION CRITERIA****************************************
SELECTION-SCREEN BEGIN OF BLOCK RAD1 WITH FRAME TITLE TEXT-003.
SELECT-OPTIONS: S_EBELN FOR ET_EKPO-EBELN OBLIGATORY.
SELECTION-SCREEN END OF BLOCK RAD1.
INITIALIZATION.
ET_KEYINFO-HEADER01 = 'EBELN'.
ET_KEYINFO-ITEM01   = 'EBELN'.
ET_SORT-FIELDNAME = 'EBELN'.
ET_SORT-TABNAME     = '2'.
ET_SORT-SPOS        = 1.
ET_SORT-UP         = 'X'.
ET_SORT-SUBTOT     = 'X'.
APPEND ET_SORT.
ET_SORT-FIELDNAME = 'EBELP'.
ET_SORT-TABNAME     = '2'.
ET_SORT-SPOS        = 1.
APPEND ET_SORT.
ET_FIELDCAT-FIELDNAME   = 'NETWR'.
ET_FIELDCAT-TABNAME       = '2'.
ET_FIELDCAT-OUTPUTLEN = 8.
ET_FIELDCAT-DO_SUM       = 'X'.
ET_FIELDCAT-HOTSPOT       = 'X'.
APPEND ET_FIELDCAT.
START-OF-SELECTION.
SELECT EBELN BUKRS AEDAT ERNAM FROM EKKO INTO CORRESPONDING
         FIELDS OF TABLE ET_EKKO
         WHERE EBELN IN S_EBELN.
SELECT * FROM EKPO INTO CORRESPONDING FIELDS
           OF TABLE ET_EKPO FOR ALL ENTRIES IN
           ET_EKKO WHERE EBELN = ET_EKKO-EBELN.
CALL FUNCTION 'REUSE_ALV_HIERSEQ_LIST_DISPLAY'
    EXPORTING
      I_STRUCTURE_NAME_HEADER = 'EKKO'
      I_STRUCTURE_NAME_ITEM   = 'EKPO'
      IS_KEYINFO              = ET_KEYINFO " The structure contains the
                                           " header and item table
                                           " field names which links the
                                           " the two tables(shared key)
      IS_LAYOUT               = ET_LAYOUT
      IT_FIELDCAT             = ET_FIELDCAT[]
      I_TABNAME_HEADER        = '1' " Name of the internal table in the
                                    " program containing the output data
                                    " of the highest hierarchy level
      I_TABNAME_ITEM          = '2' " Name of the internal table in the
                                    " program containing the output data
                                    " of the highest hierarchy level
      IT_EVENTS               = ET_EVENTS[]
      IT_SORT                 = ET_SORT[]
    TABLES
      T_OUTTAB_HEADER         = ET_EKKO " Header table with data to be
                                         " output
      T_OUTTAB_ITEM           = ET_EKPO. " Name of the internal table in
                                         " the program containing the
                                         " output data of the lowest
                                         "hierarchy level.
Regards,,
Satya Kumar..

Hyperlink on field in Basic list of ABAP Query

Dear All,
Could somebody tell me, if its possible to have a hyperlink on a field in the Basic list of ABAP Query (SQ01,SQ02).
Example :- There is a basic list which has the field MARA-MATNR displayed.There should be a hyperlink on this field, such that when the user clicks on it , the transaction MM03 is called.
Thanking You.
Ranu

Hi,
Loop at itab.
write:/ itab-matnr hotspot,
          itab-maktx.
hide: itab-matnr.
endloop.
data: c_field(16).
at line-selection.
get cursor field c_field.
if c_field = 'ITAB-MATNR'.
    check not itab-matnr is initial.
    set parameter id 'MAT' field itab-matnr.
    call transaction 'MM03' and skip first screen.
endif.
This is one example to call the transaction.
If this helps you award points.
Thanks,
Deepak.

Report for list of materials supplying by particular vendor

How to find vendorwise list of materials supplying by him.

Hi
Go to MM03 and in the selection crieteria select MATERIAL BY VENDORS MATERIAL NUMBER and there you give the vendor and the list of materials will be displayed.
This information will be available once you have any purchasing doucments like inforecords, source list, PO, Contracts, SA etc. because you will no where give the vendor while you create a material master. Other way is to link vendor material number to sap generated material number.
You can use ME1M, ME2L
Thanks & Regards,
Kiran.

Problem in custom fields in mm02/mm03

Hi folks,
i want to add the custom fields in mm01.iam able to add and update database.but iam facing problem in when iam checking the particular material in mm02/mm03.the custom field data is not correctly.for every material the last custom field data is showing. in database it is updating correctly but in mm02/mm03 it is displaying incorrectly.
By the following code i can able to display the data in mm02/mm03.but my problem is the last created custom field(model) data is showing for all the materials when iam checking in mm02/mm03.
here my custom field is "MODEL"
for eg matnr-10 model -xx.
matnr-20 model-yy.
if iam checking in mm02/mm03 for matnr-10 model-yy it is displaying.in database it is updating correctly.
can u please tell me how can i write a code to select the custom data(model data) for that particular material.
Module get_data.
if sy-tcode = 'MM02'.
select single model into mara-model from mara
where matnr = mara-matnr.
elseif sy-tcode = 'MM03'.
select single model into mara-model from mara
where matnr = mara-matnr.
loop at screen.
if screen-name = 'MARA-MODEL'.
screen-input = 0.
modify screen.
ENDIF.
endloop.
endmodule.
Thanks in advance,
Neelu.

Just read the OSS note mentioned earlier.
Symptom
You want to integrate customer-specific fields in material master maintenance.
Other terms
SAPLMGMM, RMDATIND, ALE, CI_MMH1, EXIT_SAPLMGMU_001
Solution
To add customer-specific fields to an existing material master table (such as MARA or MARC) , you can proceed as follows as of Release 3.0C:
      1. Use an append structure to add the fields to the required table in the Dictionary (this is not a modification; for details, see the SAP document "ABAP/4 Dictionary"). In Release 3.x, the length of the field names must be the same as the standard five character fields. This is necessary because of dynamic assignments. As of Release 4.0A, the lengths of the field names can be longer than five characters. If the changes of the fields should be recorded in the change document and taken into account during ALE distribution, set the 'Change document-relevant' indicator for the corresponding data elements. For table MARA in Release 3.x, you must also enhance the database view MARU because the database changes are carried out using this view. This small modification is no longer necessary as of Release 4.0A because the database view MARU is enhanced automatically when you enhance table MARA or the include EMARA (which is the data part of table MARA).
      2. Enhancing online maintenance in customized material master maintenance:
      Define a subscreen with your customer-specific fields in a customer-specific function group created as a copy of the standard function group MGD1.
      In Customizing, assign this subscreen to a maintenance screen using the "Copy customized material master" function. For details, see the Implementation Guide (IMG). As of Release 4.0A, program COPYMGD1 is available. You can use this program to create customer-specific function groups as required. This program is also incorporated in the Customizing function 'Configure customized material master'. Ensure that each field of the subscreen has a field statement in the flow logic, otherwise the data is not transported correctly. You can use subscreen SAPLMGD1 2002 as an example.
      If you want these fields to be subject to standard field selection, you must add new entries for them to the central field table for material master maintenance (T130F):
      Application examples for standard field selection:
      The field is mandatory and is to be flagged with a "?".
      The field belongs exclusively to the purchasing user department. Purchasing data and MRP data are both contained on one screen. However, the MRP controller is not to see the purchasing data.
      The following data is required for each field:
            a) Field name        (T130F-FNAME)
            b) Field selection group (T130F-FGRUP)
            Here, you should use a standard field group if the customer field is subject to the same field selection as the standard fields of the standard field group. If it is not, use a customer-specific field group.
            You must then check and, if necessary, modify the attribute of the field group using the function "Maintain field selection for data screens" in Customizing under "Logistics Basic Data -> Material Master".
            Field groups 111 through 120 that are not used in the standard system are reserved as customer-specific field groups. As of Release 3.0F, additional customer field groups are available. (For details, see the IMG).
            c) Maintenance status (T130F-PSTAT)
            List of the user departments that may maintain the field. You can display possible values by using the input help for the maintenance status field in the Customizing activity "Configure Material Master" when maintaining logical screens.
            d) Reference        (T130F-KZREF)
            This indicator must be set if the field from the reference material should be proposed during creation with reference.
Note: You cannot yet use Customizing to enhance table T130F; you can use only transaction SE16 (Data Browser) or transaction SM31. Future releases will include a separate Customizing function for maintaining customer-specific fields. See Note 306966. By implementing this note you can add entries to table T130F within Customizing. This type of maintenance is possible as of Release 4.5B.
You may change the entries for standard fields only with regard to the reference data and field selection group. Changing other data for standard fields constitutes a modification. Therefore, you cannot use the Customizing function "Assign Fields to Field Groups" to change this data.
In addition, you must not add new standard fields to table T130F.
      3. If you want to maintain customer-specific fields using data transfer by direct input or via ALE distribution, proceed as follows:
      Add the fields to central field table T130F (see above).
      Add the customer-specific fields to the data structures for the data transfer (for example, BMMH1 for the main data).
      Also, add the customer-specific fields to the tables in which the incorrect data is stored during direct input. These tables have the same name as the corresponding master data table and also have the suffix _TMP.
      For example: If you add customer-specific fields to table MARA, you should add the same fields to table MARA_TMP.
      If you use ALE, you must also add fields to the IDoc. To process enhanced IDocs, you can use enhancement MGV00001 with customer exit EXIT_SAPLMV01_002 for creating the IDocs and customer exit EXIT_SAPLMV02_002 for posting the IDocs.
      Prior to Release 3.0E, enhancing structure BMMH1 constitutes a modification. In this case, you must add the new fields tot the end of the structure before the last field (SENDE = record end indicator).
      As of Release 3.0F, structure BMMH1 contains the customer include CI_MMH1, which is part of the enhancement MGA0001. Here, you must proceed as follows:
            a) Add the customer-specific fields to include CI_MMH1.
            The names of the fields in CI_MMH1 must be identical to those of the corresponding fields in material master tables MARA, MARC and so on.
            Important: The fields must be CHAR type fields. Therefore, create CHAR type data elements whose lengths are identical to the output length of your fields in table MARA and so on. Use these data elements in include CI_MMH1, but use the field names from table MARA and so on.
            b) Activate include CI_MMH1.
            c) If you have not used customer structure ZMMH1 before, create it as a copy of structure BMMH1 and delete the standard fields that you do not require. You are not permitted to delete field STYPE and include CI_MMH1 when doing this. If you have already used structure ZMMH1, add include CI_MMH1 to it.
            d) Activate structure ZMMH1. This also adds the customer-specific fields to ZMMH1.
Run program RMDATING. This program generates routines which are supplied to your customer-specific fields from the input file. As of Release 4.5A, you also need to activate the routines/function modules generated by program RMDATING (especially, the MAT_MOVE_BMMH1_XXXX modules). Details about this subject (especially the procedure when using customer structure ZMMH1) are described in the IMG for transferring the material data under item 'Maintain Transfer Structure'. Also, check the declaration of structure WA in program RMMMBIMC to see whether it is declared with sufficient length. If necessary, enhance the declaration (for the time being, this still constitutes a minor modification).
In addition, lengthen domain DI_DATA with CHAR 5000. As of Release 3.1H, this has already been done.
Important: When using customer-specific fields, you can use only structure ZMMH1 to transfer the data. Otherwise, after the next SAP upgrade which contains new standard fields in structure BMMH1, the input files no longer match. If you want these new standard fields to be transferred, add them after your customer-specific fields (the order of the fields in structure ZMMH1 does not need to be the same as the order of the fields in BMMH1).
If you want foreign key dependencies or fixed domain values to be checked, or another check for a customer field, this is possible up to and including Release 3.0D only by modifying the corresponding check function modules. As of Release 3.0E, you can use function exit EXIT_SAPLMGMU_001 (SAP enhancement MGA00001) for these purposes.
If you want to use engineering change management to schedule future changes for your customer-specific fields or you want to use the 'Display at Key Date' function, execute program GENERATE in addition. This program generates the necessary assignments for interpreting the change documents. With regard to engineering change management, you must read Notes 60281, 60973, and 48962.
To date, it is not possible to integrate customer-specific tables in material master maintenance without making a modification. However, you can create customer-specific development objects containing the essential additional logic. You can then integrate these development objects in your system as part of only a minor modification.
Regards

Material group search list

Hi Expert,
I have a very simple problem but i cannot find the solution.
When we go to MM03, we are able to search material code by material description for eg: place your cursor on the material code field, press F4 and enter " jett ", list of description with JETT will come out regardless it is capital or small letter.
But however, if you search for material group list, for eg: place your cursor on the material group field,press F4 and enter " raff ", it will only list out the material group and description with "raff" . Other material group desc which also contains of raff but with capital letter will not come out. Means it is a case sensitive. Is this standard or we can set it somewhere so that it can ignore case sensitive, just like material code and material description?
Thanks,
Crystal

Hi Crystal,
The behaviour you are seeing is per standard design.
For the Material Group, the standard generated search help H_T023
is used. You may see this in transaction SE12.
H_T023 browses through table T023 where all the Material groups are
kept. The Search Help automaiticaly inherits the attributes of the
fields in it from the Data Dictionary.
The Material Group Description Example (WGBEZ) which belongs to Domain
TEXT20, inherits the Case-sensitivty flag from TEXT20 which is set.
The options which exist are as follows: (None of which are Supported
by SAP as standard
- You could change all descriptions for all you material groups to be
Uppercase. To facilitate this, a small ABAP could be written.
- You could create your own Search Help for Material Group, using its
own view, and here specify that you do not want case sensitivity.
BR
Nadia Orlandi

Function module to get list from CDHDR for MATERIAL

Hello,
I am searching for the function to get a list of CDHDR-entries for a material in transaction MM03.
My debugging was not successful. So I hope someone here has the answer.
What is the name of the function that SAP uses in TA MM02/MM03 to get the list of CDHDR-entries for a material number and from where (include) is it called?
I found already the function to get the related CDPOS entries, starting from the list with CDHDR entries in the transaction.
This is CHANGEDOCUMENT_READ_POSITIONS.
But here I am definitely too late, because I am searching for the reasn why one of my changes entered in CDHDR is not selected!
Thank you in advance for the answer!
Best regards
Dirk

Hello Suhas,
yeah, I used MM04 from your answer and found the same!
Thank you! This will help me!
It is PERFORM relevanz_pruefen
called after the FM which kills some of my entries.
Now I can find a solution for my issue!
Best regards
Dirk

Purchase group list

Dear Gurus,
I need to get the list of purchase groups with details. This is required for User, SO it can not be from SPRO. Also not from MM03 OR XK03 which will show drop down list on purchase group field.
Is there any way I can get list of purchase groups with details from user perspective.

As per I know there is no such report to only display purchase group.
Many reports have drop down option to choose it.
you can make simple query to display only purchase group

Industry Sector and Material Type list of values in cFolders

Hi,
How to transfer the List of Values for Industry Sector & Material Type from R/3 to cFolders system?
We have R/3 Production system running for the past 3 years. We are implementing cFolders now. While Material creation in cFolders, the List of Values listed for above mentioned fields are not as per R/3 values. Hence we need to change the same LOV in cFolders as per R/3. How to do it?
Prasanna
9036129381.

Hi,
The parameters material type and industry sector are used
to classify a material. They define its possible uses.
For example if you selct indutsry type as retail or mechanical it will classssify the material accordingly. again material type is semifinished then this you can also use as a raw material. In mm02 or MM03 u cant see it.
If you want to see these you can go to SE16 and put table name MARA and can see it.
Hope this will help.
Reward point if helpful.
Thanks,
Raja

Material stock doesn't appear in Material dcument list

Hi Guys,
please chk the below case.
We have a material 1234 for which stock exists in unrestricted use. In mm03 system shows stock as 25k. When checked the material document list in MB51 for existing stock there it shows no movements have happened for this material 1234.
How can this happen?
Stock is reflecting in master
Stock is not reflecting in material document list / no movements happened.
Regards,
Suresh

Hi Guys,
Thanks for all your responses.
Here the problem is i'm able to see the stocks in MMBE and material master.
If the stock is there in Unrestricted use there should be some movements happened against this.
Here it's peculiar case. where these materials doesn't have any material documents for this.
How can this be possible? I have checked MB51 if there exists any material documents posted for this material. There exists nothing. it shows empty. where can i find material docuemts and / or any movement happened for this material.
without happening a movement against a material how does the stock gets updated with qty?
Regards,
Suresh

Add a custom-field in the table MARC and manage it in MM01/MM02/MM03

Good day to all of you!
I have this task: To add a custom-field to the table MARC. This custom-field will be managed through the MM01/MM02/MM03 transaction as follows:
In the Basic Data 1 or Basic Data 2 the custom-field data will be added. Let's say the field is MATNR OBSOLETE.
I have searched and implemented the things in customizing: Made a copy of function group MGD1, added the field on the screen.
MY PROBLEM! How to manage it??? When the user enters MM01/MM02/MM03 and update this field, the field should be updated in MARC.
1. I am not sure that this custom-field should be on Basic Data1 or Basic Data2.They want it at plant level.
2. How to manage the data transfer from SAP Standard Program and my Custom Function Group.
PLs: Do not paste me link to sap technical site with that example, because there takes the custom fields and UPDATE a CUSTOM TABLE. I need to update MARC!
All the documentations i have read until now tell you how to add the field, ONLY the first part of the SOLUTION.
Any help, pls?
Good day and thank you!

Hi Alex,
In which way you are trying to update that custom filed. Have you written any logic in EXITS/BADIS?
http://pavelgk.pbworks.com/f/6729224-Implement-Screen-Exit-for-MM01-Adding-New-Fields-in-Screen.pdf
and
Just read the OSS note mentioned earlier.
Symptom
You want to integrate customer-specific fields in material master maintenance.
Other terms
SAPLMGMM, RMDATIND, ALE, CI_MMH1, EXIT_SAPLMGMU_001
Solution
To add customer-specific fields to an existing material master table (such as MARA or MARC) , you can proceed as follows as of Release 3.0C:
      1. Use an append structure to add the fields to the required table in the Dictionary (this is not a modification; for details, see the SAP document "ABAP/4 Dictionary"). In Release 3.x, the length of the field names must be the same as the standard five character fields. This is necessary because of dynamic assignments. As of Release 4.0A, the lengths of the field names can be longer than five characters. If the changes of the fields should be recorded in the change document and taken into account during ALE distribution, set the 'Change document-relevant' indicator for the corresponding data elements. For table MARA in Release 3.x, you must also enhance the database view MARU because the database changes are carried out using this view. This small modification is no longer necessary as of Release 4.0A because the database view MARU is enhanced automatically when you enhance table MARA or the include EMARA (which is the data part of table MARA).
      2. Enhancing online maintenance in customized material master maintenance:
      Define a subscreen with your customer-specific fields in a customer-specific function group created as a copy of the standard function group MGD1.
      In Customizing, assign this subscreen to a maintenance screen using the "Copy customized material master" function. For details, see the Implementation Guide (IMG). As of Release 4.0A, program COPYMGD1 is available. You can use this program to create customer-specific function groups as required. This program is also incorporated in the Customizing function 'Configure customized material master'. Ensure that each field of the subscreen has a field statement in the flow logic, otherwise the data is not transported correctly. You can use subscreen SAPLMGD1 2002 as an example.
      If you want these fields to be subject to standard field selection, you must add new entries for them to the central field table for material master maintenance (T130F):
      Application examples for standard field selection:
      The field is mandatory and is to be flagged with a "?".
      The field belongs exclusively to the purchasing user department. Purchasing data and MRP data are both contained on one screen. However, the MRP controller is not to see the purchasing data.
      The following data is required for each field:
            a) Field name        (T130F-FNAME)
            b) Field selection group (T130F-FGRUP)
            Here, you should use a standard field group if the customer field is subject to the same field selection as the standard fields of the standard field group. If it is not, use a customer-specific field group.
            You must then check and, if necessary, modify the attribute of the field group using the function "Maintain field selection for data screens" in Customizing under "Logistics Basic Data -> Material Master".
            Field groups 111 through 120 that are not used in the standard system are reserved as customer-specific field groups. As of Release 3.0F, additional customer field groups are available. (For details, see the IMG).
            c) Maintenance status (T130F-PSTAT)
            List of the user departments that may maintain the field. You can display possible values by using the input help for the maintenance status field in the Customizing activity "Configure Material Master" when maintaining logical screens.
            d) Reference        (T130F-KZREF)
            This indicator must be set if the field from the reference material should be proposed during creation with reference.
Note: You cannot yet use Customizing to enhance table T130F; you can use only transaction SE16 (Data Browser) or transaction SM31. Future releases will include a separate Customizing function for maintaining customer-specific fields. See Note 306966. By implementing this note you can add entries to table T130F within Customizing. This type of maintenance is possible as of Release 4.5B.
You may change the entries for standard fields only with regard to the reference data and field selection group. Changing other data for standard fields constitutes a modification. Therefore, you cannot use the Customizing function "Assign Fields to Field Groups" to change this data.
In addition, you must not add new standard fields to table T130F.
      3. If you want to maintain customer-specific fields using data transfer by direct input or via ALE distribution, proceed as follows:
      Add the fields to central field table T130F (see above).
      Add the customer-specific fields to the data structures for the data transfer (for example, BMMH1 for the main data).
      Also, add the customer-specific fields to the tables in which the incorrect data is stored during direct input. These tables have the same name as the corresponding master data table and also have the suffix _TMP.
      For example: If you add customer-specific fields to table MARA, you should add the same fields to table MARA_TMP.
      If you use ALE, you must also add fields to the IDoc. To process enhanced IDocs, you can use enhancement MGV00001 with customer exit EXIT_SAPLMV01_002 for creating the IDocs and customer exit EXIT_SAPLMV02_002 for posting the IDocs.
      Prior to Release 3.0E, enhancing structure BMMH1 constitutes a modification. In this case, you must add the new fields tot the end of the structure before the last field (SENDE = record end indicator).
      As of Release 3.0F, structure BMMH1 contains the customer include CI_MMH1, which is part of the enhancement MGA0001. Here, you must proceed as follows:
            a) Add the customer-specific fields to include CI_MMH1.
            The names of the fields in CI_MMH1 must be identical to those of the corresponding fields in material master tables MARA, MARC and so on.
            Important: The fields must be CHAR type fields. Therefore, create CHAR type data elements whose lengths are identical to the output length of your fields in table MARA and so on. Use these data elements in include CI_MMH1, but use the field names from table MARA and so on.
            b) Activate include CI_MMH1.
            c) If you have not used customer structure ZMMH1 before, create it as a copy of structure BMMH1 and delete the standard fields that you do not require. You are not permitted to delete field STYPE and include CI_MMH1 when doing this. If you have already used structure ZMMH1, add include CI_MMH1 to it.
            d) Activate structure ZMMH1. This also adds the customer-specific fields to ZMMH1.
Run program RMDATING. This program generates routines which are supplied to your customer-specific fields from the input file. As of Release 4.5A, you also need to activate the routines/function modules generated by program RMDATING (especially, the MAT_MOVE_BMMH1_XXXX modules). Details about this subject (especially the procedure when using customer structure ZMMH1) are described in the IMG for transferring the material data under item 'Maintain Transfer Structure'. Also, check the declaration of structure WA in program RMMMBIMC to see whether it is declared with sufficient length. If necessary, enhance the declaration (for the time being, this still constitutes a minor modification).
In addition, lengthen domain DI_DATA with CHAR 5000. As of Release 3.1H, this has already been done.
Important: When using customer-specific fields, you can use only structure ZMMH1 to transfer the data. Otherwise, after the next SAP upgrade which contains new standard fields in structure BMMH1, the input files no longer match. If you want these new standard fields to be transferred, add them after your customer-specific fields (the order of the fields in structure ZMMH1 does not need to be the same as the order of the fields in BMMH1).
If you want foreign key dependencies or fixed domain values to be checked, or another check for a customer field, this is possible up to and including Release 3.0D only by modifying the corresponding check function modules. As of Release 3.0E, you can use function exit EXIT_SAPLMGMU_001 (SAP enhancement MGA00001) for these purposes.
If you want to use engineering change management to schedule future changes for your customer-specific fields or you want to use the 'Display at Key Date' function, execute program GENERATE in addition. This program generates the necessary assignments for interpreting the change documents. With regard to engineering change management, you must read Notes 60281, 60973, and 48962.
To date, it is not possible to integrate customer-specific tables in material master maintenance without making a modification. However, you can create customer-specific development objects containing the essential additional logic. You can then integrate these development objects in your system as part of only a minor modification.
check this link. It may helps you to solve your issue.
Thanks
Sravan

MM03 - Annex List

Similar Messages

Maybe you are looking for