Create a new view in Material Master

Hi All,
I need to create a new view in the Material Master (Tcode - MM*)
Can anyone let me know how can this be attained. Can this be attained by configuration.
Regards
Simin.R

you have to use the MM01 tocde and enter the mateial you want extend for new view. system will propose the view and select the new view.
Or use MM50 for mass

Similar Messages

What is procedure for creating new vendor and material master data in ABAP

What is procedure for creating new vendor and material master data in ABAP .

see below code which is used for creation of vendor master as well as extension...
*& Report ZFC_VENDOR_CREATE *
REPORT ZFC_VENDOR_CREATE LINE-SIZE 100
 NO STANDARD PAGE HEADING
 MESSAGE-ID ZZ.
 TABLES
TABLES : SSCRFIELDS. " Fields on selection screens
 CONSTANTS
DATA : C_SPLIT TYPE C VALUE '#'. " Used for Has Separator in GUI_UPLAOD
 TYPES
Int'table to hold Vendor Master Data
TYPES : BEGIN OF TY_VENDOR_MASTER,
 FLAG TYPE C, " Update Flag
 LIFNR TYPE LIFNR, " Vendor Number
 BUKRS TYPE BUKRS, " Company Code
 KTOKK TYPE KTOKK, " Account Group
 ANRED TYPE ANRED, " Title
 NAME1 TYPE NAME1_GP, " Name1
 NAME2 TYPE NAME2_GP, " Name2
 SORTL TYPE SORTL, " Search Term 1
 SORT2 TYPE AD_SORT2UL, " Search Term 2
 STRAS TYPE STRAS_GP, " Street
 PSTLZ TYPE PSTLZ, " Postal Code
 ORT01 TYPE ORT01_GP, " City
 REGIO TYPE REGIO, " Region
 LAND1 TYPE LAND1_GP, " Country
 SPRAS TYPE SPRAS, " Language
 VBUND TYPE RASSC, " Trading Partner
 BANKS TYPE BANKS, " Country
 BANKL TYPE BANKK, " Bank Key
 BANKN TYPE BANKN, " Bank Account
 BKONT TYPE BKONT, " Bank Control Key
 BANKA TYPE BANKA, " Name of Bank
 AKONT TYPE AKONT, " Reconciliation Account
 FDGRV TYPE FDGRV, " Cash Management Group
 ZTERM TYPE DZTERM, " Payment Terms
 REPRF TYPE REPRF, " Check Double Invoice
 ZWELS TYPE DZWELS, " Payment Methods
 XPORE TYPE XPORE, " Pay all items separately
 END OF TY_VENDOR_MASTER,
Int'table to hold Vendor Extend Data
 BEGIN OF TY_VENDOR_EXTEND,
 FLAG TYPE C, " Update Flag
 LIFNR TYPE LIFNR, " Vendor Number
 BUKRS TYPE BUKRS, " Company Code
 KTOKK TYPE KTOKK, " Account Group
 REF_LIFNR TYPE LIFNR, " Reference Vendor Number
 REF_BUKRS TYPE BUKRS, " Reference Company Code
 AKONT TYPE AKONT, " Reconciliation Account
 FDGRV TYPE FDGRV, " Cash Management Group
 ZTERM TYPE DZTERM, " Payment Terms
 REPRF TYPE REPRF, " Check Double Invoice
 ZWELS TYPE DZWELS, " Payment Methods
 XPORE TYPE XPORE, " Pay all items separately
 END OF TY_VENDOR_EXTEND,
Int'table to hold Error Records Data
 BEGIN OF TY_ERROR,
 MSG(200) TYPE C, " To hold Message
 LIFNR TYPE LIFNR, " Vendor Number
 BUKRS TYPE BUKRS, " Company Code
 END OF TY_ERROR.
 DATA (Simple Fields)
DATA : W_COUNT TYPE I, " Variable to hold count of Records
 W_SUCC_REC TYPE I, " No. of Success Records
 W_SUCC_REC1 TYPE I, " No. of Updated Records
 W_ERR_REC TYPE I, " No. of Error Records
 w_noupdate_rec type i. " No. of Records not Changed
 INTERNAL TABLES
Int'table to hold uploaded data from File
DATA : IT_VENDOR_MASTER TYPE STANDARD TABLE OF TY_VENDOR_MASTER,
 WA_IT_VENDOR_MASTER TYPE TY_VENDOR_MASTER,
 IT_VENDOR_EXTEND TYPE STANDARD TABLE OF TY_VENDOR_EXTEND,
 WA_IT_VENDOR_EXTEND TYPE TY_VENDOR_EXTEND,
 WA_IT_BDCDATA TYPE BDCDATA,
 IT_BDCDATA TYPE STANDARD TABLE OF BDCDATA,
 WA_IT_MESSTAB TYPE BDCMSGCOLL,
 IT_MESSTAB TYPE STANDARD TABLE OF BDCMSGCOLL,
 IT_ERROR TYPE STANDARD TABLE OF TY_ERROR,
 WA_IT_ERROR TYPE TY_ERROR,
 it_error_fk01 type standard table of ty_error,
 wa_it_error_fk01 type ty_error,
 it_error_fk02 type standard table of ty_error,
 wa_it_error_fk02 type ty_error,
 it_succ_rec1 type standard table of ty_error,
 wa_it_succ_rec1 type ty_error,
 it_noupdate type standard table of ty_error,
 wa_it_noupdate type ty_error.
 FLAGS
DATA : FL_FLAG1 TYPE C, " Flag to check error upload file
 FL_FLAG2 TYPE C, " Flag to hold value
 FL_FLAG3 TYPE C, " Flag to hold value
 FL_FLAG4 TYPE C. " Flag to hold value
 SELECTION-SCREEN
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001.
SELECTION-SCREEN : BEGIN OF LINE,
 COMMENT 1(30) TEXT-001,
 POSITION POS_LOW.
PARAMETERS : P_FILE(128) DEFAULT 'C:\UPLOAD.TXT' OBLIGATORY.
SELECTION-SCREEN : END OF LINE.
SELECTION-SCREEN : BEGIN OF LINE,
 COMMENT 1(30) TEXT-002,
 POSITION POS_LOW.
PARAMETERS : P_VENMAS RADIOBUTTON GROUP R1 DEFAULT 'X'.
SELECTION-SCREEN : END OF LINE.
SELECTION-SCREEN : BEGIN OF LINE,
 COMMENT 1(30) TEXT-003,
 POSITION POS_LOW.
PARAMETERS : P_VENEXT RADIOBUTTON GROUP R1.
SELECTION-SCREEN : END OF LINE.
SELECTION-SCREEN SKIP 2.
SELECTION-SCREEN : BEGIN OF LINE,
 COMMENT 1(30) TEXT-004,
 POSITION POS_LOW.
PARAMETERS : P_MODE(1) DEFAULT 'N'.
SELECTION-SCREEN : END OF LINE.
SELECTION-SCREEN : BEGIN OF LINE,
 COMMENT 1(30) TEXT-005,
 POSITION POS_LOW.
PARAMETERS : P_GROUP(12) DEFAULT 'ZFC_VENDOR_C' OBLIGATORY.
SELECTION-SCREEN : END OF LINE.
SELECTION-SCREEN : BEGIN OF LINE,
 COMMENT 1(30) TEXT-016,
 POSITION POS_LOW.
PARAMETERS : P_GROUP1(12) DEFAULT 'ZFC_VENDOR_U' OBLIGATORY.
SELECTION-SCREEN : END OF LINE.
SELECTION-SCREEN END OF BLOCK B1.
 AT SELECTION-SCREEN ON
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FILE.
Form to get file path for upload of data
PERFORM GET_FILE_PATH.
AT SELECTION-SCREEN ON BLOCK B1.
Form to Validate data specified on Selection Screen
CHECK SSCRFIELDS-UCOMM EQ 'ONLI'.
PERFORM VALIDATE_DATA.
 START - OF - SELECTION
START-OF-SELECTION.
IF P_VENMAS = 'X'.
Form to upload data from Presentation Server for Vendor Master
 PERFORM UPLOAD_DATA TABLES IT_VENDOR_MASTER.
 IF FL_FLAG1 NE 'X'.
 SORT IT_VENDOR_MASTER BY LIFNR BUKRS KTOKK.
 DELETE IT_VENDOR_MASTER WHERE LIFNR = ' '
 AND BUKRS = ' '
 AND KTOKK = ' '.
Form to process data for Vendor Master
 PERFORM INSERT_VENDOR_MASTER_DATA.
 ENDIF.
ELSEIF P_VENEXT = 'X'.
Form to upload data from Presentation Server for Vendor Extend
 PERFORM UPLOAD_DATA TABLES IT_VENDOR_EXTEND.
 IF FL_FLAG1 NE 'X'.
 SORT IT_VENDOR_EXTEND BY LIFNR BUKRS KTOKK.
 DELETE IT_VENDOR_EXTEND WHERE LIFNR = ' '
 AND BUKRS = ' '
 AND KTOKK = ' '.
Form to process data for Vendor Master
 PERFORM CHK_AND_INS_VENDOR_EXTEND_DATA.
 ENDIF.
ENDIF.
 END - OF - SELECTION
END-OF-SELECTION.
IF FL_FLAG1 NE 'X'.
 FORMAT COLOR 7.
 WRITE:/2 TEXT-O01. " Total Number of records read :
 FORMAT COLOR OFF.
 WRITE:40 W_COUNT.
 FORMAT COLOR 7.
 WRITE:/2 TEXT-O02. " Total Number of Success records :
 FORMAT COLOR OFF.
 WRITE:40 W_SUCC_REC.
 FORMAT COLOR 7.
 WRITE:/2 TEXT-O07. " Total Number of Updated records :
 FORMAT COLOR OFF.
 WRITE:40 W_SUCC_REC1.
 FORMAT COLOR 7.
 WRITE:/2 TEXT-O08. " Total Number of Unchanged records :
 FORMAT COLOR OFF.
 WRITE:40 W_noupdate_REC.
 FORMAT COLOR 7.
 WRITE:/2 TEXT-O03. " Total Number of Error records :
 FORMAT COLOR OFF.
 WRITE:40 W_ERR_REC.
 if not it_succ_rec1 is initial.
 skip 1.
 perform display_changed_report.
 endif.
 if not it_noupdate is initial.
 skip 1.
 perform display_nochange_report.
 endif.
 IF NOT IT_ERROR IS INITIAL.
 SKIP 3.
Form to display error data
 PERFORM DISPLAY_ERROR_REPORT.
 ENDIF.
 IF FL_FLAG2 = 'X'.
 SKIP 2.
 FORMAT COLOR 4.
 WRITE:/2 TEXT-O04. " BDC Session Name for Creation (FK01) :
 FORMAT COLOR OFF.
 WRITE:40 P_GROUP.
 perform display_error_report_fk01.
 ENDIF.
 IF FL_FLAG3 = 'X'.
 SKIP 2.
 FORMAT COLOR 4.
 WRITE:/2 TEXT-O09. " BDC Session Name for Updation (FK02) :
 FORMAT COLOR OFF.
 WRITE:40 P_GROUP1.
 perform display_error_report_fk02.
 ENDIF.
ENDIF.
*& Form GET_FILE_PATH
This form is used to get the specified path for uploading of data from
flat file with the help of F4 function key
FORM GET_FILE_PATH .
CALL FUNCTION 'F4_FILENAME'
 EXPORTING
 PROGRAM_NAME = SYST-CPROG
 DYNPRO_NUMBER = SYST-DYNNR
 FIELD_NAME = ' '
 IMPORTING
 FILE_NAME = P_FILE.
ENDFORM. " GET_FILE_PATH
*& Form VALIDATE_DATA
This form is used to validate the data given by user on the Selection
Screen and the appropriate message is been displayed when an wrong
entry is inputted
FORM VALIDATE_DATA .
IF SY-BATCH EQ 'X'.
 CLEAR SSCRFIELDS-UCOMM.
 MESSAGE E001(ZZ) WITH TEXT-011.
 " Excel file not to be used in Batch Mode
ENDIF.
IF P_MODE NE 'A' AND P_MODE NE 'N' AND P_MODE NE 'E'.
 MESSAGE E001(ZZ) WITH TEXT-012.
 " Session Mode should be either A or N or E
ENDIF.
ENDFORM. " VALIDATE_DATA
*& Form UPLOAD_DATA
This form is used to upload data from Presentation Server for either
Vendor Master or Vendor Extend
FORM UPLOAD_DATA TABLES P_IT_VENDOR.
DATA : L_FILENAME TYPE STRING,
 L_FILETYPE TYPE CHAR10 VALUE 'ASC',
 L_HEADER_LENGTH TYPE I VALUE 0,
 L_READ_BY_LINE TYPE CHAR01 VALUE 'X'.
MOVE P_FILE TO L_FILENAME.
CALL FUNCTION 'GUI_UPLOAD'
 EXPORTING
 FILENAME = L_FILENAME
 FILETYPE = L_FILETYPE
 HEADER_LENGTH = L_HEADER_LENGTH
 READ_BY_LINE = L_READ_BY_LINE
 HAS_FIELD_SEPARATOR = C_SPLIT
 TABLES
 DATA_TAB = P_IT_VENDOR
 EXCEPTIONS
 FILE_OPEN_ERROR = 1
 FILE_READ_ERROR = 2
 NO_BATCH = 3
 GUI_REFUSE_FILETRANSFER = 4
 INVALID_TYPE = 5
 NO_AUTHORITY = 6
 UNKNOWN_ERROR = 7
 BAD_DATA_FORMAT = 8
 HEADER_NOT_ALLOWED = 9
 SEPARATOR_NOT_ALLOWED = 10
 HEADER_TOO_LONG = 11
 UNKNOWN_DP_ERROR = 12
 ACCESS_DENIED = 13
 DP_OUT_OF_MEMORY = 14
 DISK_FULL = 15
 DP_TIMEOUT = 16
 OTHERS = 17.
IF SY-SUBRC <> 0.
 MESSAGE I001(ZZ) WITH TEXT-006 L_FILENAME.
MESSAGE ID SY-MSGID TYPE 'I' NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 FL_FLAG1 = 'X'.
ELSEIF P_IT_VENDOR[] IS INITIAL.
 MESSAGE I001(ZZ) WITH TEXT-014. " Uploaded File contains no data
 FL_FLAG1 = 'X'.
ENDIF.
ENDFORM. " UPLOAD_DATA
*& Form INSERT_VENDOR_MASTER_DATA
This form is used to process BDC data for Vendor Master
FORM INSERT_VENDOR_MASTER_DATA .
DATA : L_LIFNR TYPE LIFNR.
CLEAR : L_LIFNR.
sort it_vendor_master by flag.
LOOP AT IT_VENDOR_MASTER INTO WA_IT_VENDOR_MASTER.
 W_COUNT = W_COUNT + 1.
 CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 INPUT = WA_IT_VENDOR_MASTER-LIFNR
 IMPORTING
 OUTPUT = WA_IT_VENDOR_MASTER-LIFNR.
 if wa_it_vendor_master-flag = 'A'.
 SELECT SINGLE LIFNR
 FROM LFB1
 INTO L_LIFNR
 WHERE LIFNR = WA_IT_VENDOR_MASTER-LIFNR
 AND BUKRS = WA_IT_VENDOR_MASTER-BUKRS.
 IF SY-SUBRC EQ 0.
 WA_IT_ERROR-LIFNR = WA_IT_VENDOR_MASTER-LIFNR.
 WA_IT_ERROR-BUKRS = WA_IT_VENDOR_MASTER-BUKRS.
 WA_IT_ERROR-MSG = TEXT-015.
 APPEND WA_IT_ERROR TO IT_ERROR.
 W_ERR_REC = W_ERR_REC + 1.
 CLEAR : WA_IT_ERROR, L_LIFNR.
 ELSE.
 REFRESH IT_BDCDATA.
 CLEAR IT_BDCDATA.
 PERFORM POPULATE_BDC_DATA_VEN_MASTER.
 PERFORM CALL_TRANSACTION.
 ENDIF.
 CLEAR : WA_IT_VENDOR_MASTER.
 elseif wa_it_vendor_master-flag = 'C'.
 IF FL_FLAG2 = 'X' and fl_flag4 ne 'X'.
 PERFORM CLOSE_BDC_SESSION.
 fl_flag4 = 'X'.
 ENDIF.
 REFRESH IT_BDCDATA.
 CLEAR IT_BDCDATA.
 PERFORM POPULATE_BDC_DATA_VEN_MASTER.
 PERFORM CALL_TRANSACTION_FK02.
 CLEAR : WA_IT_VENDOR_MASTER.
 elseif wa_it_vendor_master-flag = 'N'.
 WA_IT_noupdate-LIFNR = WA_IT_VENDOR_MASTER-LIFNR.
 WA_IT_noupdate-BUKRS = WA_IT_VENDOR_MASTER-BUKRS.
 WA_IT_noupdate-MSG = TEXT-018.
 APPEND WA_IT_noupdate TO IT_noupdate.
 W_noupdate_REC = W_noupdate_REC + 1.
 CLEAR : WA_IT_noupdate, WA_IT_VENDOR_MASTER.
 endif.
ENDLOOP.
IF FL_FLAG3 = 'X'.
 PERFORM CLOSE_BDC_SESSION.
ENDIF.
ENDFORM. " INSERT_VENDOR_MASTER_DATA
*& Form POPULATE_BDC_DATA_VEN_MASTER
This form is used to populate BDC data of Vendor Master
FORM POPULATE_BDC_DATA_VEN_MASTER .
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 INPUT = WA_IT_VENDOR_MASTER-ZTERM
 IMPORTING
 OUTPUT = WA_IT_VENDOR_MASTER-ZTERM.
IF WA_IT_VENDOR_MASTER-REPRF = 'Y'.
 WA_IT_VENDOR_MASTER-REPRF = 'X'.
ENDIF.
IF WA_IT_VENDOR_MASTER-XPORE = 'Y'.
 WA_IT_VENDOR_MASTER-XPORE = 'X'.
ENDIF.
if wa_it_vendor_master-flag = 'A'.
PERFORM :BDC_DYNPRO USING 'SAPMF02K' '0105',
 BDC_FIELD USING 'RF02K-LIFNR' WA_IT_VENDOR_MASTER-LIFNR,
 BDC_FIELD USING 'RF02K-BUKRS' WA_IT_VENDOR_MASTER-BUKRS,
 BDC_FIELD USING 'RF02K-KTOKK' WA_IT_VENDOR_MASTER-KTOKK,
 BDC_FIELD USING 'BDC_OKCODE' '/00'.
elseif wa_it_vendor_master-flag = 'C'.
PERFORM :BDC_DYNPRO USING 'SAPMF02K' '0106',
 BDC_FIELD USING 'RF02K-LIFNR' WA_IT_VENDOR_MASTER-LIFNR,
 BDC_FIELD USING 'RF02K-BUKRS' WA_IT_VENDOR_MASTER-BUKRS,
 BDC_FIELD USING 'BDC_OKCODE' '=MALL',
 BDC_DYNPRO USING 'SAPMF02K' '0106',
 BDC_FIELD USING 'RF02K-D0110' 'X',
 BDC_FIELD USING 'RF02K-D0120' 'X',
 BDC_FIELD USING 'RF02K-D0130' 'X',
 BDC_FIELD USING 'RF02K-D0210' 'X',
 BDC_FIELD USING 'RF02K-D0215' 'X',
 BDC_FIELD USING 'RF02K-D0220' 'X',
 BDC_FIELD USING 'BDC_OKCODE' '/00'.
endif.
perform :BDC_DYNPRO USING 'SAPMF02K' '0110',
 BDC_FIELD USING 'LFA1-ANRED' WA_IT_VENDOR_MASTER-ANRED,
 BDC_FIELD USING 'LFA1-NAME1' WA_IT_VENDOR_MASTER-NAME1,
 BDC_FIELD USING 'LFA1-NAME2' WA_IT_VENDOR_MASTER-NAME2,
 BDC_FIELD USING 'LFA1-SORTL' WA_IT_VENDOR_MASTER-SORTL,
 BDC_FIELD USING 'LFA1-STRAS' WA_IT_VENDOR_MASTER-STRAS,
 BDC_FIELD USING 'LFA1-ORT01' WA_IT_VENDOR_MASTER-ORT01,
 BDC_FIELD USING 'LFA1-PSTLZ' WA_IT_VENDOR_MASTER-PSTLZ,
 BDC_FIELD USING 'LFA1-LAND1' WA_IT_VENDOR_MASTER-LAND1,
 BDC_FIELD USING 'LFA1-REGIO' WA_IT_VENDOR_MASTER-REGIO,
 BDC_FIELD USING 'LFA1-SPRAS' WA_IT_VENDOR_MASTER-SPRAS,
 BDC_FIELD USING 'BDC_OKCODE' '/00',
 BDC_DYNPRO USING 'SAPMF02K' '0120',
 BDC_FIELD USING 'LFA1-VBUND' WA_IT_VENDOR_MASTER-VBUND,
 BDC_FIELD USING 'BDC_OKCODE' '/00',
 BDC_DYNPRO USING 'SAPMF02K' '0130',
 BDC_FIELD USING 'LFBK-BANKS(01)' WA_IT_VENDOR_MASTER-BANKS,
 BDC_FIELD USING 'LFBK-BANKL(01)' WA_IT_VENDOR_MASTER-BANKL,
 BDC_FIELD USING 'LFBK-BANKN(01)' WA_IT_VENDOR_MASTER-BANKN,
 BDC_FIELD USING 'BDC_OKCODE' '=BANK',
 BDC_DYNPRO USING 'SAPLBANK' '0100',
 BDC_FIELD USING 'BNKA-BANKA' WA_IT_VENDOR_MASTER-BANKA,
 BDC_FIELD USING 'BDC_OKCODE' '=ENTR',
 BDC_DYNPRO USING 'SAPMF02K' '0130',
 BDC_FIELD USING 'BDC_OKCODE' '=ENTR',
 BDC_DYNPRO USING 'SAPMF02K' '0210',
 BDC_FIELD USING 'LFB1-AKONT' WA_IT_VENDOR_MASTER-AKONT,
 BDC_FIELD USING 'LFB1-FDGRV' WA_IT_VENDOR_MASTER-FDGRV,
 BDC_FIELD USING 'BDC_OKCODE' '=/00',
 BDC_DYNPRO USING 'SAPMF02K' '0215',
 BDC_FIELD USING 'LFB1-ZTERM' WA_IT_VENDOR_MASTER-ZTERM,
 BDC_FIELD USING 'LFB1-REPRF' WA_IT_VENDOR_MASTER-REPRF,
 BDC_FIELD USING 'LFB1-ZWELS' WA_IT_VENDOR_MASTER-ZWELS,
 BDC_FIELD USING 'LFB1-XPORE' WA_IT_VENDOR_MASTER-XPORE,
 BDC_FIELD USING 'BDC_OKCODE' '=UPDA'.
ENDFORM. " POPULATE_BDC_DATA_VEN_MASTER
*& Form BDC_DYNPRO
This form is used to move data to BDCDATA int'table
FORM BDC_DYNPRO USING PROGRAM TYPE BDC_PROG
 DYNPRO TYPE BDC_DYNR.
CLEAR WA_IT_BDCDATA.
WA_IT_BDCDATA-PROGRAM = PROGRAM.
WA_IT_BDCDATA-DYNPRO = DYNPRO.
WA_IT_BDCDATA-DYNBEGIN = 'X'.
APPEND WA_IT_BDCDATA TO IT_BDCDATA.
ENDFORM. " BDC_DYNPRO
*& Form BDC_FIELD
This form is used to move data to BDCDATA int'table
FORM BDC_FIELD USING FNAM TYPE ANY
 FVAL TYPE ANY.
CLEAR WA_IT_BDCDATA.
WA_IT_BDCDATA-FNAM = FNAM.
WA_IT_BDCDATA-FVAL = FVAL.
APPEND WA_IT_BDCDATA TO IT_BDCDATA.
ENDFORM. " BDC_FIELD
*& Form CALL_TRANSACTION
This form is used to Call FK01 for processing of data either for
Vendor Master or Vendor Extend. The error records are inserted to
Session which can be processed using SM35
FORM CALL_TRANSACTION .
DATA : L_OPTION TYPE CTU_PARAMS,
 L_SUBRC TYPE SYSUBRC.
REFRESH IT_MESSTAB.
CLEAR IT_MESSTAB.
L_OPTION-DEFSIZE = 'X'.
L_OPTION-DISMODE = P_MODE.
L_OPTION-UPDMODE = 'S'.
CALL TRANSACTION 'FK01'
 USING IT_BDCDATA
 MESSAGES INTO IT_MESSTAB
 OPTIONS FROM L_OPTION.
L_SUBRC = SY-SUBRC.
IF L_SUBRC = 0.
 W_SUCC_REC = W_SUCC_REC + 1.
ELSE.
 IF FL_FLAG2 NE 'X'.
 PERFORM OPEN_BDC_SESSION.
 FL_FLAG2 = 'X'.
 ENDIF.
 PERFORM BDC_INSERT.
 W_ERR_REC = W_ERR_REC + 1.
 PERFORM ERROR_RECORD_DATA.
ENDIF.
ENDFORM. " CALL_TRANSACTION
*& Form OPEN_BDC_SESSION
Form used to open session for Error out Records
FORM OPEN_BDC_SESSION .
DATA : L_USERID TYPE APQ_MAPN, " Variable to hold user-id
 L_GROUP TYPE APQ_GRPN. " Variable to hold value
MOVE P_GROUP TO L_GROUP.
MOVE SY-UNAME TO L_USERID.
CALL FUNCTION 'BDC_OPEN_GROUP'
 EXPORTING
 CLIENT = SY-MANDT
 GROUP = L_GROUP
 KEEP = SPACE
 USER = L_USERID
 EXCEPTIONS
 CLIENT_INVALID = 1
 DESTINATION_INVALID = 2
 GROUP_INVALID = 3
 GROUP_IS_LOCKED = 4
 HOLDDATE_INVALID = 5
 INTERNAL_ERROR = 6
 QUEUE_ERROR = 7
 RUNNING = 8
 SYSTEM_LOCK_ERROR = 9
 USER_INVALID = 10
 OTHERS = 11.
IF SY-SUBRC <> 0.
 WRITE:/ TEXT-008. " Unable to open BDC Session
ENDIF.
ENDFORM. " OPEN_BDC_SESSION
*& Form BDC_INSERT
This form is used to insert error records to a Session method
FORM BDC_INSERT .
CALL FUNCTION 'BDC_INSERT'
 EXPORTING
 TCODE = 'FK01'
 TABLES
 DYNPROTAB = IT_BDCDATA
 EXCEPTIONS
 INTERNAL_ERROR = 1
 NOT_OPEN = 2
 QUEUE_ERROR = 3
 TCODE_INVALID = 4
 PRINTING_INVALID = 5
 POSTING_INVALID = 6
 OTHERS = 7.
IF SY-SUBRC <> 0.
 WRITE:/ TEXT-009. " Unable to Insert Data to BDC Session
ENDIF.
ENDFORM. " BDC_INSERT
*& Form ERROR_RECORD_DATA
This form is used to process the messages for the error records which
will be displayed on the output report
FORM ERROR_RECORD_DATA .
DATA : L_LINES TYPE I,
 L_MSG(200) TYPE C.
DESCRIBE TABLE IT_MESSTAB LINES L_LINES.
READ TABLE IT_MESSTAB INTO WA_IT_MESSTAB INDEX L_LINES.
IF SY-SUBRC = 0.
 CLEAR L_MSG.
 CALL FUNCTION 'FORMAT_MESSAGE'
 EXPORTING
 ID = WA_IT_MESSTAB-MSGID
 LANG = SY-LANGU
 NO = WA_IT_MESSTAB-MSGNR
 V1 = WA_IT_MESSTAB-MSGV1
 V2 = WA_IT_MESSTAB-MSGV2
 V3 = WA_IT_MESSTAB-MSGV3
 V4 = WA_IT_MESSTAB-MSGV4
 IMPORTING
 MSG = L_MSG
 EXCEPTIONS
 NOT_FOUND = 1
 OTHERS = 2.
 IF SY-SUBRC = 0.
 WA_IT_ERROR_fk01-MSG = L_MSG.
 ENDIF.
 IF P_VENMAS = 'X'.
 WA_IT_ERROR_fk01-LIFNR = WA_IT_VENDOR_MASTER-LIFNR.
 WA_IT_ERROR_fk01-BUKRS = WA_IT_VENDOR_MASTER-BUKRS.
 ELSEIF P_VENEXT = 'X'.
 WA_IT_ERROR_fk01-LIFNR = WA_IT_VENDOR_EXTEND-LIFNR.
 WA_IT_ERROR_fk01-BUKRS = WA_IT_VENDOR_EXTEND-BUKRS.
 ENDIF.
 APPEND WA_IT_ERROR_fk01 TO IT_ERROR_fk01.
 CLEAR WA_IT_ERROR_fk01.
ENDIF.
ENDFORM. " ERROR_RECORD_DATA
*& Form CLOSE_BDC_SESSION
Form used to close session of the Error Records
FORM CLOSE_BDC_SESSION .
CALL FUNCTION 'BDC_CLOSE_GROUP'
 EXCEPTIONS
 NOT_OPEN = 1
 QUEUE_ERROR = 2
 OTHERS = 3.
IF SY-SUBRC <> 0.
 WRITE:/ TEXT-010. " Unable to Close BDC Session
ENDIF.
ENDFORM. " CLOSE_BDC_SESSION
*& Form CHK_AND_INS_VENDOR_EXTEND_DATA
This form is used to process BDC data for Vendor Extend
FORM CHK_AND_INS_VENDOR_EXTEND_DATA .
DATA : L_LIFNR TYPE LIFNR.
CLEAR : L_LIFNR, fl_flag4.
sort it_vendor_extend by flag.
LOOP AT IT_VENDOR_EXTEND INTO WA_IT_VENDOR_EXTEND.
 W_COUNT = W_COUNT + 1.
 CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 INPUT = WA_IT_VENDOR_EXTEND-REF_LIFNR
 IMPORTING
 OUTPUT = WA_IT_VENDOR_EXTEND-REF_LIFNR.
 if wa_it_vendor_extend-flag = 'A'.
 SELECT SINGLE LIFNR
 FROM LFB1
 INTO L_LIFNR
 WHERE LIFNR = WA_IT_VENDOR_EXTEND-REF_LIFNR
 AND BUKRS = WA_IT_VENDOR_EXTEND-REF_BUKRS.
 IF SY-SUBRC NE 0.
 WA_IT_ERROR-LIFNR = WA_IT_VENDOR_EXTEND-REF_LIFNR.
 WA_IT_ERROR-BUKRS = WA_IT_VENDOR_EXTEND-REF_BUKRS.
 WA_IT_ERROR-MSG = TEXT-007.
 APPEND WA_IT_ERROR TO IT_ERROR.
 W_ERR_REC = W_ERR_REC + 1.
 CLEAR : WA_IT_ERROR, L_LIFNR.
 ELSE.
 CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 INPUT = WA_IT_VENDOR_EXTEND-LIFNR
 IMPORTING
 OUTPUT = WA_IT_VENDOR_EXTEND-LIFNR.
 SELECT SINGLE LIFNR
 FROM LFB1
 INTO L_LIFNR
 WHERE LIFNR = WA_IT_VENDOR_EXTEND-LIFNR
 AND BUKRS = WA_IT_VENDOR_EXTEND-BUKRS.
 IF SY-SUBRC EQ 0.
 WA_IT_ERROR-LIFNR = WA_IT_VENDOR_EXTEND-LIFNR.
 WA_IT_ERROR-BUKRS = WA_IT_VENDOR_EXTEND-BUKRS.
 WA_IT_ERROR-MSG = TEXT-015.
 APPEND WA_IT_ERROR TO IT_ERROR.
 W_ERR_REC = W_ERR_REC + 1.
 CLEAR : WA_IT_ERROR, L_LIFNR.
 ELSE.
 REFRESH IT_BDCDATA.
 CLEAR IT_BDCDATA.
 PERFORM POPULATE_BDC_DATA_VEN_EXTEND.
 PERFORM CALL_TRANSACTION.
 ENDIF.
 ENDIF.
 CLEAR : WA_IT_VENDOR_EXTEND.
 elseif wa_it_vendor_extend-flag = 'C'.
 IF FL_FLAG2 = 'X' and fl_flag4 ne 'X'.
 PERFORM CLOSE_BDC_SESSION.
 fl_flag4 = 'X'.
 ENDIF.
 REFRESH IT_BDCDATA.
 CLEAR IT_BDCDATA.
 PERFORM POPULATE_BDC_DATA_VEN_extend.
 PERFORM CALL_TRANSACTION_FK02.
 CLEAR : WA_IT_VENDOR_EXTEND.
 elseif wa_it_vendor_extend-flag = 'N'.
 WA_IT_noupdate-LIFNR = WA_IT_VENDOR_extend-LIFNR.
 WA_IT_noupdate-BUKRS = WA_IT_VENDOR_extend-BUKRS.
 WA_IT_noupdate-MSG = TEXT-019.
 APPEND WA_IT_noupdate TO IT_noupdate.
 W_noupdate_REC = W_noupdate_REC + 1.
 CLEAR : WA_IT_noupdate, WA_IT_VENDOR_EXTEND.
 endif.
ENDLOOP.
IF FL_FLAG2 = 'X'.
 PERFORM CLOSE_BDC_SESSION.
ENDIF.
if fl_flag3 = 'X'.
 PERFORM CLOSE_BDC_SESSION.
ENDIF.
ENDFORM. " CHK_AND_INS_VENDOR_EXTEND_DATA
*& Form POPULATE_BDC_DATA_VEN_EXTEND
This form is used to populate BDC data of Vendor Extend
FORM POPULATE_BDC_DATA_VEN_EXTEND .
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 INPUT = WA_IT_VENDOR_EXTEND-ZTERM
 IMPORTING
 OUTPUT = WA_IT_VENDOR_EXTEND-ZTERM.
IF WA_IT_VENDOR_EXTEND-REPRF = 'Y'.
 WA_IT_VENDOR_EXTEND-REPRF = 'X'.
ENDIF.
IF WA_IT_VENDOR_extend-XPORE = 'Y'.
 WA_IT_VENDOR_extend-XPORE = 'X'.
ENDIF.
if wa_it_vendor_extend-flag = 'A'.
PERFORM :BDC_DYNPRO USING 'SAPMF02K' '0105',
 BDC_FIELD USING 'RF02K-LIFNR' WA_IT_VENDOR_EXTEND-LIFNR,
 BDC_FIELD USING 'RF02K-BUKRS' WA_IT_VENDOR_EXTEND-BUKRS,
 BDC_FIELD USING 'RF02K-KTOKK' WA_IT_VENDOR_EXTEND-KTOKK,
 BDC_FIELD USING 'RF02K-REF_LIFNR'
 WA_IT_VENDOR_EXTEND-REF_LIFNR,
 BDC_FIELD USING 'RF02K-REF_BUKRS'
 WA_IT_VENDOR_EXTEND-REF_BUKRS,
 BDC_FIELD USING 'BDC_OKCODE' '/00'.
elseif wa_it_vendor_extend-flag = 'C'.
PERFORM :BDC_DYNPRO USING 'SAPMF02K' '0106',
 BDC_FIELD USING 'RF02K-LIFNR' WA_IT_VENDOR_extend-LIFNR,
 BDC_FIELD USING 'RF02K-BUKRS' WA_IT_VENDOR_extend-BUKRS,
 BDC_FIELD USING 'RF02K-D0210' 'X',
 BDC_FIELD USING 'RF02K-D0215' 'X',
 BDC_FIELD USING 'BDC_OKCODE' '/00'.
endif.
perform :BDC_DYNPRO USING 'SAPMF02K' '0210',
 BDC_FIELD USING 'LFB1-AKONT' WA_IT_VENDOR_EXTEND-AKONT,
 BDC_FIELD USING 'LFB1-FDGRV' WA_IT_VENDOR_EXTEND-FDGRV,
 BDC_FIELD USING 'BDC_OKCODE' '=/00',
 BDC_DYNPRO USING 'SAPMF02K' '0215',
 BDC_FIELD USING 'LFB1-ZTERM' WA_IT_VENDOR_EXTEND-ZTERM,
 BDC_FIELD USING 'LFB1-REPRF' WA_IT_VENDOR_EXTEND-REPRF,
 BDC_FIELD USING 'LFB1-ZWELS' WA_IT_VENDOR_EXTEND-ZWELS,
 BDC_FIELD USING 'LFB1-XPORE' WA_IT_VENDOR_extend-XPORE,
 BDC_FIELD USING 'BDC_OKCODE' '=UPDA'.
ENDFORM. " POPULATE_BDC_DATA_VEN_EXTEND
*& Form DISPLAY_ERROR_REPORT
This form is used to display the error records on the output screen
FORM DISPLAY_ERROR_REPORT .
IF P_VENMAS = 'X'.
 WRITE:/ TEXT-O05. " Error List for Vendor Master
ELSEIF P_VENEXT = 'X'.
 WRITE:/ TEXT-O06. " Error List for Vendor Master Extended
ENDIF.
WRITE:/ SY-ULINE(100).
FORMAT COLOR 1.
WRITE:/1 SY-VLINE,
 2 TEXT-H01, " Vendor Number
 17 SY-VLINE,
 18 TEXT-H02, " Company Code
 31 SY-VLINE,
 32 TEXT-H03, " Error Message
 100 SY-VLINE.
FORMAT COLOR OFF.
WRITE:/ SY-ULINE(100).
LOOP AT IT_ERROR INTO WA_IT_ERROR.
 FORMAT COLOR 2.
 WRITE:/1 SY-VLINE,
 2 WA_IT_ERROR-LIFNR,
 17 SY-VLINE,
 18 WA_IT_ERROR-BUKRS,
 31 SY-VLINE,
 32 WA_IT_ERROR-MSG,
 100 SY-VLINE.
 CLEAR : WA_IT_ERROR.
 FORMAT COLOR OFF.
ENDLOOP.
WRITE:/ SY-ULINE(100).
ENDFORM. " DISPLAY_ERROR_REPORT
*& Form CALL_TRANSACTION_FK02
Form used to Call Transaction FK02
form CALL_TRANSACTION_FK02 .
DATA : L_OPTION TYPE CTU_PARAMS,
 L_SUBRC TYPE SYSUBRC.
REFRESH IT_MESSTAB.
CLEAR IT_MESSTAB.
L_OPTION-DEFSIZE = 'X'.
L_OPTION-DISMODE = P_MODE.
L_OPTION-UPDMODE = 'S'.
CALL TRANSACTION 'FK02'
 USING IT_BDCDATA
 MESSAGES INTO IT_MESSTAB
 OPTIONS FROM L_OPTION.
L_SUBRC = SY-SUBRC.
IF L_SUBRC = 0.
 W_SUCC_REC1 = W_SUCC_REC1 + 1.
 WA_IT_succ_rec1-MSG = Text-017.
 IF P_VENMAS = 'X'.
 WA_IT_succ_rec1-LIFNR = WA_IT_VENDOR_MASTER-LIFNR.
 WA_IT_succ_rec1-BUKRS = WA_IT_VENDOR_MASTER-BUKRS.
 ELSEIF P_VENEXT = 'X'.
 WA_IT_succ_rec1-LIFNR = WA_IT_VENDOR_EXTEND-LIFNR.
 WA_IT_succ_rec1-BUKRS = WA_IT_VENDOR_EXTEND-BUKRS.
 ENDIF.
 APPEND WA_IT_succ_rec1 TO IT_succ_rec1.
ELSE.
 IF FL_FLAG3 NE 'X'.
 PERFORM OPEN_BDC_SESSION_fk02.
 FL_FLAG3 = 'X'.
 ENDIF.
 PERFORM BDC_INSERT_fk02.
 W_ERR_REC = W_ERR_REC + 1.
 PERFORM ERROR_RECORD_DATA1.
ENDIF.
endform. " CALL_TRANSACTION_FK02
*& Form OPEN_BDC_SESSION_fk02
Form used to Open session for FK02
form OPEN_BDC_SESSION_fk02 .
DATA : L_USERID TYPE APQ_MAPN, " Variable to hold user-id
 L_GROUP TYPE APQ_GRPN. " Variable to hold value
MOVE P_GROUP1 TO L_GROUP.
MOVE SY-UNAME TO L_USERID.
CALL FUNCTION 'BDC_OPEN_GROUP'
 EXPORTING
 CLIENT = SY-MANDT
 GROUP = L_GROUP
 KEEP = SPACE
 USER = L_USERID
 EXCEPTIONS
 CLIENT_INVALID = 1
 DESTINATION_INVALID = 2
 GROUP_INVALID = 3
 GROUP_IS_LOCKED = 4
 HOLDDATE_INVALID = 5
 INTERNAL_ERROR = 6
 QUEUE_ERROR = 7
 RUNNING = 8
 SYSTEM_LOCK_ERROR = 9
 USER_INVALID = 10
 OTHERS = 11.
IF SY-SUBRC <> 0.
 WRITE:/ TEXT-008. " Unable to open BDC Session
ENDIF.
endform. " OPEN_BDC_SESSION_fk02
*& Form BDC_INSERT_fk02
Form used to insert data into BDC session using FK02
form BDC_INSERT_fk02 .
CALL FUNCTION 'BDC_INSERT'
 EXPORTING
 TCODE = 'FK02'
 TABLES
 DYNPROTAB = IT_BDCDATA
 EXCEPTIONS
 INTERNAL_ERROR = 1
 NOT_OPEN = 2
 QUEUE_ERROR = 3
 TCODE_INVALID = 4
 PRINTING_INVALID = 5
 POSTING_INVALID = 6
 OTHERS = 7.
IF SY-SUBRC <> 0.
 WRITE:/ TEXT-009. " Unable to Insert Data to BDC Session
ENDIF.
endform. " BDC_INSERT_fk02
*& Form display_changed_report
Form to display Updated Vendor data
form display_changed_report .
IF P_VENMAS = 'X'.
 WRITE:/ TEXT-O10. " Updated List for Vendor Master
ELSEIF P_VENEXT = 'X'.
 WRITE:/ TEXT-O11. " Updated List for Vendor Master Extended
ENDIF.
WRITE:/ SY-ULINE(100).
FORMAT COLOR 1.
WRITE:/1 SY-VLINE,
 2 TEXT-H01, " Vendor Number
 17 SY-VLINE,
 18 TEXT-H02, " Company Code
 31 SY-VLINE,
 32 TEXT-H04, " Message
 100 SY-VLINE.
FORMAT COLOR OFF.
WRITE:/ SY-ULINE(100).
LOOP AT IT_succ_rec1 INTO WA_IT_succ_rec1.
 FORMAT COLOR 2.
 WRITE:/1 SY-VLINE,
 2 WA_IT_succ_rec1-LIFNR,
 17 SY-VLINE,
 18 WA_IT_succ_rec1-BUKRS,
 31 SY-VLINE,
 32 WA_IT_succ_rec1-MSG,
 100 SY-VLINE.
 CLEAR : WA_IT_succ_rec1.
 FORMAT COLOR OFF.
ENDLOOP.
WRITE:/ SY-ULINE(100).
endform. " display_changed_report
*& Form display_nochange_report
Form to display No Changed data for Vendors
form display_nochange_report .
IF P_VENMAS = 'X'.
 WRITE:/ TEXT-O12. " No Changes List for Vendor Master
ELSEIF P_VENEXT = 'X'.
 WRITE:/ TEXT-O13. " No Changes List for Vendor Master Extended
ENDIF.
WRITE:/ SY-ULINE(100).
FORMAT COLOR 1.
WRITE:/1 SY-VLINE,
 2 TEXT-H01, " Vendor Number
 17 SY-VLINE,
 18 TEXT-H02, " Company Code
 31 SY-VLINE,
 32 TEXT-H04, " Message
 100 SY-VLINE.
FORMAT COLOR OFF.
WRITE:/ SY-ULINE(100).
LOOP AT IT_noupdate INTO WA_IT_noupdate.
 FORMAT COLOR 2.
 WRITE:/1 SY-VLINE,
 2 WA_IT_noupdate-LIFNR,
 17 SY-VLINE,
 18 WA_IT_noupdate-BUKRS,
 31 SY-VLINE,
 32 WA_IT_noupdate-MSG,
 100 SY-VLINE.
 CLEAR : WA_IT_noupdate.
 FORMAT COLOR OFF.
ENDLOOP.
WRITE:/ SY-ULINE(100).
endform. " display_nochange_report
*& Form ERROR_RECORD_DATA1
Form to get Error Message for Changed Vendors
form ERROR_RECORD_DATA1 .
DATA : L_LINES TYPE I,
 L_MSG(200) TYPE C.
DESCRIBE TABLE IT_MESSTAB LINES L_LINES.
READ TABLE IT_MESSTAB INTO WA_IT_MESSTAB INDEX L_LINES.
IF SY-SUBRC = 0.
 CLEAR L_MSG.
 CALL FUNCTION 'FORMAT_MESSAGE'
 EXPORTING
 ID = WA_IT_MESSTAB-MSGID
 LANG = SY-LANGU
 NO = WA_IT_MESSTAB-MSGNR
 V1 = WA_IT_MESSTAB-MSGV1
 V2 = WA_IT_MESSTAB-MSGV2
 V3 = WA_IT_MESSTAB-MSGV3
 V4 = WA_IT_MESSTAB-MSGV4
 IMPORTING
 MSG = L_MSG
 EXCEPTIONS
 NOT_FOUND = 1
 OTHERS = 2.
 IF SY-SUBRC = 0.
 WA_IT_ERROR_fk02-MSG = L_MSG.
 ENDIF.
 IF P_VENMAS = 'X'.
 WA_IT_ERROR_fk02-LIFNR = WA_IT_VENDOR_MASTER-LIFNR.
 WA_IT_ERROR_fk02-BUKRS = WA_IT_VENDOR_MASTER-BUKRS.
 ELSEIF P_VENEXT = 'X'.
 WA_IT_ERROR_fk02-LIFNR = WA_IT_VENDOR_EXTEND-LIFNR.
 WA_IT_ERROR_fk02-BUKRS = WA_IT_VENDOR_EXTEND-BUKRS.
 ENDIF.
 APPEND WA_IT_ERROR_fk02 TO IT_ERROR_fk02.
 CLEAR WA_IT_ERROR_fk02.
ENDIF.
endform. " ERROR_RECORD_DATA1
*& Form display_error_report_fk01
Form to display Error Report for Master Vendors (FK01)
form display_error_report_fk01 .
IF P_VENMAS = 'X'.
 WRITE:/ TEXT-O05. " Error List for Vendor Master (FK01)
ELSEIF P_VENEXT = 'X'.
 WRITE:/ TEXT-O06. " Error List for Vendor Master Extended (FK01)
ENDIF.
WRITE:/ SY-ULINE(100).
FORMAT COLOR 1.
WRITE:/1 SY-VLINE,
 2 TEXT-H01, " Vendor Number
 17 SY-VLINE,
 18 TEXT-H02, " Company Code
 31 SY-VLINE,
 32 TEXT-H04, " Message
 100 SY-VLINE.
FORMAT COLOR OFF.
WRITE:/ SY-ULINE(100).
LOOP AT IT_ERROR_fk01 INTO WA_IT_ERROR_fk01.
 FORMAT COLOR 2.
 WRITE:/1 SY-VLINE,
 2 WA_IT_ERROR_fk01-LIFNR,
 17 SY-VLINE,
 18 WA_IT_ERROR_fk01-BUKRS,
 31 SY-VLINE,
 32 WA_IT_ERROR_fk01-MSG,
 100 SY-VLINE.
 CLEAR : WA_IT_ERROR_fk01.
 FORMAT COLOR OFF.
ENDLOOP.
WRITE:/ SY-ULINE(100).
endform. " display_error_report_fk01
*& Form display_error_report_fk02
Form to display Error Report for changed Vendors (FK02)
form display_error_report_fk02 .
IF P_VENMAS = 'X'.
 WRITE:/ TEXT-O14. " Error List for Vendor Master (FK02)
ELSEIF P_VENEXT = 'X'.
 WRITE:/ TEXT-O15. " Error List for Vendor Master Extended (FK02)
ENDIF.
WRITE:/ SY-ULINE(100).
FORMAT COLOR 1.
WRITE:/1 SY-VLINE,
 2 TEXT-H01, " Vendor Number

Current period in Accounting 1 view of Material Master

Dear Experts,
In Accounting 1 view of Material Master there is a current period, now it is 12 2009.
Is it possible to make it 11 2009, if yes how to do it.
Please help if you have solution. it is very crucial for me.
Thank you for your support.
Regards,
Zusen

Hi,
Please read the Solution part of note 487381. There is still a few things need to be carry out before you can proceed
with the initialization :
Bear in mind that the initialization of a posting period has the
following effects concerning the period stocks:
    o The initialization of the posting period to a previous or to any
       posting period may lead to the loss of the information of the
       inventory balances of the previous periods.The book value of the
       current posting period is taken as the basis also for values of
       the previous period in this case.
       If you want to continue working with this new posting period, in
       addition you should execute report Z_DEL_HIST_ENTRIES attached so
       that history entries greater or equal to the new posting period
       will be deleted.
    o If you have to briefly reset the posting period by one period
       (for example, postings must still be posted in a certain period)
       just to make a correction (and for a small number of postings),
       you should initialize the posting period back again to the old
       value so that the values of the previous period will not be lost
       (you should forbid postings when carrying out corrections).
       However, afterwards the values of the previous period or the
       history records (as of Release 4.5) of the materials posted in
       this case are inaccurate.
       You should NOT execute report Z_DEL_HIST_ENTRIES in this case.
    o However, if the posting period is generally reset again to a
       previous posting period and if postings were made during this
       time, all information on the inventory balance of the previous
       periods is lost.
       As of Release 4.5a, you should use the cited correction report
    Z_DEL_HIST_ENTRIES in order to delete history records that are
    more current than the current posting period.Otherwise, it can
    result in deviations (inconsistencies) for the update of the
    history records.
o Important! If there are open physical inventory documents that
    have status 'counted' or for which indicator 'Freeze inventory
    balance' has been set, you should reject these if they refer to a
    previous period or have been created in the former previous
    period.The inventory difference to be posted can be determined
    from the current book value of the previous period and the book
    quantity frozen in the physical inventory document (ISEG-BUCHM)
    and does not match the inventory balance of the previous period
    that is currently valid.

How to activate the new fields on material master(MM01/MM02/MM03) for existing Materials

Hi,
We have a requirement to add some custom fields as a new tab in additional data option(Descriptions, Unit of measure, etc.) in Basic data of Material master (MM01/MM02/MM03). I have successfully added and these custom fields and they are not part of standard(MARA, MARC) but a custom table and the updates are also done in custom table.
For new materials, I can see the new tab in additional data screens of basic data view and I could successfully create/change/display using MM01/MM02/MM03. However I cannot see the new tab/fields for existing materials in the system in all 3 tcodes (MM01/MM02/MM03). This is not a main view in material master so that I can extend it by MM01.
Is there any setting or mass generation program I have top perform so that I can see and maintain these new fields for existing materials. Appreciate any leads or help on this.
Thanks,
Harry

Hello Harry,
Goto t.code SPRO ---> Display IMG ---> Logistics - General --> Material master --> Configuring the material master --> Create program for customized screens
Use the above path and create the screen and assign it to the sequence using the below link as reference.
**************** - Tips - Implementing screen exits for MM01/MM02/MM03
Regards,
Thanga

Extending a material view in Material Master

Hi
I have created a Material without a sales view.Now I wnt to add sales view in the existing Material Master. How to do this.
Regards
venkat

Hi Garapati,
Pleas read the answers of experts.
You have to use MM01 (create) transaction if you want to extend your material master record since you create new records in material master tables.
So you have to use MM01 if you create a brand new mmr and you have to use the same if you want to extend your mmr.
BR
Csaba

How to remove any view from material master

Hello guys,
   Actually we can attach the view to material master by MM01 and also by MM50.
   Now,consider this, in my company even we sale the semifinished material along with the finished material.So we have attached the sales view to semifinished material and finished material.Now my company has decided to not to sale the semifinished material.So there is no sense in keeping the sales view in material master of semifinished material.So we want to remove the sales view from the material master of semifinished material.
     So could you guys help me out to do this?

Hi
From the config for Material type attributes you can change the views relevant to Material type means you can unselect the sales views - that will definately take care of the new materials that will be created. But for the existing one's and the data is something you need to see and investigate
I would advice you to check all the aspects in dev client and then take a decision.
Thanks

New fiel in material master data

Hello,
We need a new field in material master data, Can I define a new append in mara table?.
Then, we are thinking in modify screen of basis data?
Anybody know if this is posible?
Thanks.

Hi Rafael Murillo,
New field Custom field can be created and added to existing SAP STD Tables like MARA, MARC,MVKE etc..
All depend updates upon the exact Business requirement.
If the new filed is applicable for a specific sales org. specific, then you new to insert that filed in sales View 1/2,,,
In that case new filed should be insearted at MVKE level.
And you to use any of the Sub screens at sales level..need to to the IMG changes also.
For ex. you have material group 1, material group 1 ..this full sub screen is useful for most of the client..
you can replase this sub screen..
create your sub screen with your custom field using z program and replace the program in IMG.
Thanks,
Kumar Arcot

Adding fields in costing view of material master

Hi gurus,
I need to add 4 fields in costing view of material master. I have followed the steps in SPRO, for configuring customized screen in material master.
1) Created a function group YMMCO and copied the screen 2904 from program SAPLMGD1.
2) Added 4 fields in my customized screen.
3) Created copy of 01 ( Screen reference ) to z1 in OMT3B.
Since 2904 is not there in the sequence . I changed one 0001 sequence at the end to 2904 . I also assigned my program
SAPLYMMCO to it. I can see the changed fields in data screen and subscreen.
4) Then I assigned the SSq to z1 in transaction OMT3E.
But unfortunately, when I go to MM01 to create a material , I am not able to view the fields I added in costing view.
I have checked the screen for the previous field, it shows 2904 only.
Two days back, I did the same thing in basic data view 1 , it was working properly. As per client's suggestion I put it in
costing view, it is not working . Please give me suitable suggestions.
Thanks in advance.
D. Mallick

Hi,
I also need to add custom fields to Basic data view. After copying & changing the screen sequence in Config, I could able to see the custom fields in Basic Data view.
I have appended structure with custom fields to MARA table.
But the values I enter in the screen is not getting updated to the table MARA.
Can you please let me know the code, I should have have in PAI (Process After Input) module in the Sub Screen to update the values?
Thanks,
Dasa

PO creation without Purchasing view in material master

Hi
i am using 4.6 version
system is allowing to create PO without purchasing view in material master.
how it would be possible ?
Regards
Rahul

Hi,
i have checked with MARA for that material PSTAT value it is showing there "KDALBPCGV"
please suggest
regards
rahul

What is the concept of view in material master?

Hello sap gurus
Some quetions regarding Material Master
what is the concept of views in material master ?
what is determined by specifying industry sector in material master ?
To sell material which views are material are maintened in Material master?
Regards
Amit

Hi,
Material master for finished ggods is related with SD, MM & PP departments. If you carefully go through the various screens in MM record you will realize the importance of the respective fields and the department to which they belong.
1.Suppose Base unit of measure in Basic data 1 screen. The production people will keep the stock of the item using this UOM.
2. In Sales:Sales Org.1 screen we have sales unit in which we will sell the material.
3. Then we have the plant data in which we enter the delivering plant. Also the taxes are determined from the plant so we have the settings for taxes also - whether this material is fully taxable/50% tax/Tax exempted.
4. Then we have purchasing screen in which the data like the purchasing group, variable units,etc are entered. This will effect the purchasing cycle when we are procuring a material from outside. This is related to MM.
5. The we have MRP, this is related to PP as to how to manufacture the product, the MRP type, the strategy group - whether it is MTO/MTS like that.
5. Sales:Sales Org.2 screen - Here we mainatin the account assignment group which is very important as far as the generation of the accounting document is concerned. This triggers the system where to post the value in which G/L account. Accounting document is generated when we create the invoice in VF01 & save it.
6. Work scheduling - Related with the sceduling of the production as to whether underdelivery or overdelivery is allowed, the storage location
7. Quality - Here you can select for a particular finished item where where it has to be checked for quality during its journey from the raw material stage to the finished goods store as a finished item.
8. Accounting - Related to accounting, product costing, total value of the stock in hand, etc. Also related with FI & PP
So all the screens have data which effects one or more modules for the proper functioning of the system to give the optimum results.
Industry Sector:
Key that specifies the branch of industry to which the material is assigned.
Use
When you create a material master record, the industry sector you specify determines
1. which screens appear and in what order
2. which industry-specific fields appear on the individual screens
Screens for Sales:
Sales:Sales Org.1, Sales:Sales Org.2. But other screens also have data which is related to sales. You cannot just maintain the sales views and save the master. It has to be properly linked with the other modules also for the proper functioning of the system. That is why the system is called as "Enterprise Resource Planning" You have to paln the resources of your company and these resources are related with all the modules.
Reward points if solution helps.
Regards,
Allabaqsh G. Patil

Control inspection lot in QM view of material master

Hi
this is regarding the setting for control inspection in QM view of material master.
can anyone give me a prictical example of
1. 'X' An inspection lot for each purchase order item/order item
2. '1' An inspection lot for each material document and material
3. '2' An inspection lot for each material and batch
If my requirement is to create one inspection lot out of several batches made from a production order( eg, 10 batches are created, only 1st one needed for RR and UD), which one should I use?

Hi,
the concept of batch comes when there are some property changes (property in terms of business, that may be quality or something else). if you are confirming production order partially, it means there is something that changes with batches. that's why std sap does not allow to create single lot though all those batches have been created from same production order.
and henceforth, your requirement cannot be fulfilled by any config. you can try for development.
partha

View using Material master,Vendor master and PO tables

Hello folks.
There is a requirement to create view using material master tables ( MARA,MARC,MARD,MAKT & MBEW ) , vendor master tables ( LFA1 & LFB1) and
Purchase order tables ( EKKO & EKPO tables).
I have created the attribute views for material and vendor master tables separately.Now I am thinking about the following design pattern.
1. Join the material master master attribute view to EKPO table using the inner join to create a analytic view1.
2. Join the material vendor master attribute view to EKKO table using the inner join to create a analytic view2.
3. Now create calculate view using join to combine analyticalview1 & analyticalview2.
Please suggest me the best optimize pattern and am strange to SAP HANA. Please also clarify the following doubts.
1. What is the role of system supplied default aggregation node?
2. How can I use Union node in the calculation view in the current requirement because people/documentation always suggesting using of Union than Join?
Thanks & Regards,
Suresh Kuturu

I have managed to create the Analytic view as per my requirement.. No need to use calculation view in this case..

Extend Classification View for Material Master

Hello, How do I extend classificiation view for Material Master? Is there any BAPI or FM to do that?
I cant find any place to extend it with BAPI_MATERIAL_SAVEDATA

Hi,
Use this FM to create Classfiaction view BAPI_OBJCL_CREATE
Regards,
Shan

Create a new view in a enhance component

Hi All,
I want to create a new view for sales order and quatation in a component BP_factsheet.When i craete new view ,it is asking about some value like model node, bol entity, higher level, bol realtion.after that is is asking context node ,bsp application ,custome controller and view type.How can i get these value .when i create a new view then have to add these view in run time repositry under a window or not?
Thanks in advance....
Vishwas

Hello Vishwas,
You might be interested in knowing how to customise the new UI to add a new view using the enhancement concept.
Please refer to the published document on the service marketplace:
http://help.sap.com/saphelp_crm60/helpdata/en/1a/023d63b8387c4a8dfea6592f3a23a7/frameset.htm
refers to the link at
service.sap.com/okp
Inside this go to:
SAP CRM 2006s: Learning Map for Technology Consultants
wherein you can find the cookbook to perform similar operation in detail.
SAP CRM UI Cookbook
I hope this helps.

Creating a new view in a component

HI,
I am trying to create a new view in a BSP component using the wizard. But the context nodes are not getting created. Its throwing up an error - "View not copied with wizard; processing not possible".
What could be the problem ? Pls help.
Regards,
Aravind.

Hi Arvind,
Before posting error, please search for it.
Here is what i found here in 2007 forum itself.
I guess you have not enhanced your component and your view.
Without enhancing the component it is not possible to add a new context node.
Here is a very helpful, follow it and the the other link within this thread,
both are very useful in this regard.
Web Client Context Node Enhancement
Thanks & Regards
Shiven

Create a new view in Material Master

Similar Messages

Maybe you are looking for