LOOKUP-Master Data Attribute (ABAP Code)

Hi,
My requirment
ZCOMPANY is an attribute of ZCostcenter
ZCost center is an attribute ZEMPLOYEE
zcomp is an attribute of employee
While Loading attribute data to employee i need to write Lookup/routine in transformations that will
Based on ZCOSTCENTER data of an employee i has to read setup tables in BW and update ZCOMP of an employee(attribute) from ZCOMPANY of ZCostcenter
Please update me with the ABAP Code
Thanks in advance

Hi,
This is the routine written in transformations.
My requirment is to modify this a bit to include following conditions
1)source_fields-costcenter
(It needs to be converted to CAPS)(Bcaz ZCOSTCENTER consists all the caps)
2)I want to include 'OBJVERS'='A' in the code
Please update me with the code
select /bic/zcompany from /bic/mzcostcenter
into result
where zcostcenter = source_fields-costcenter.
end select.
Thanks

Similar Messages

Map My Update Rule from a Master Data Attribute

Hello experts,
I haven't tried this scenario yet, hope you can help me, the Issue is this
I have 2 InfoObjects ZPSCHRCHY and 0PROFIT_CTR from InfoCube WBS cost and allocations I want both the InfoObjects to be mapped to 0PROFIT_CTR attribute of 0WBS_ELEMT master data object, I have tried the Master Data Attribute but only 0PROFIT_CTR is an attribute of the Master Data.how can I mapped ZPSCHRCHY and 0PROFIT_CTR to 0PROFIT_CTR?, Is creating a start routine for it must be used? Thank you very much
Regards and Thanks
Chris

PROGRAM UPDATE_ROUTINE.
$$ begin of global - insert your declaration only below this line -
TYPES:
BEGIN OF r_MD_WBS_ELEMENT,
 WBS_ELEMT like /BI0/PWBS_ELEMT-WBS_ELEMT,
 OBJVERS like /BI0/PWBS_ELEMT-OBJVERS,
 PROFIT_CTR like /BI0/PWBS_ELEMT-PROFIT_CTR,
END of r_MD_WBS_ELEMENT.
DATA: t_MD_WBS_ELEMENT TYPE STANDARD TABLE OF r_MD_WBS_ELEMENT,
 wa_MD_WBS_ELEMENT TYPE r_MD_WBS_ELEMENT.
$$ end of global - insert your declaration only before this line -
The follow definition is new in the BW3.x
TYPES:
BEGIN OF DATA_PACKAGE_STRUCTURE.
 INCLUDE STRUCTURE /BIC/CS8ZPSG030.
TYPES:
 RECNO LIKE sy-tabix,
END OF DATA_PACKAGE_STRUCTURE.
DATA:
DATA_PACKAGE TYPE STANDARD TABLE OF DATA_PACKAGE_STRUCTURE
 WITH HEADER LINE
 WITH NON-UNIQUE DEFAULT KEY INITIAL SIZE 0.
FORM startup
TABLES MONITOR STRUCTURE RSMONITOR "user defined monitoring
 MONITOR_RECNO STRUCTURE RSMONITORS " monitoring with record n
 DATA_PACKAGE STRUCTURE DATA_PACKAGE
USING RECORD_ALL LIKE SY-TABIX
 SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS
CHANGING ABORT LIKE SY-SUBRC. "set ABORT <> 0 to cancel update
$$ begin of routine - insert your code only below this line -
fill the internal tables "MONITOR" and/or "MONITOR_RECNO",
to make monitor entries
REFRESH: t_MD_WBS_ELEMENT.
 SELECT WBS_ELEMT
 OBJVERS
 PROFIT_CTR
 INTO TABLE t_MD_WBS_ELEMENT
 FROM /BI0/PWBS_ELEMT
 FOR ALL ENTRIES IN DATA_PACKAGE
 WHERE WBS_ELEMT = DATA_PACKAGE-WBS_ELEMT.
 IF sy-subrc EQ 0.
 Do nothing
 ENDIF.
if abort is not equal zero, the update process will be canceled
ABORT = 0.
$$ end of routine - insert your code only before this line -
ENDFORM.

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

Read from master data attribute

Hi BI experts,
Here is a challenging question.
One of the FIGL infoprovider do not have infoobject 0company. Added 0company and set up update type 'overwrite'. Update method 'Master data attribute'. So 0company should read from the master data attribute of 0Comp_code.
Master data attribute loaded for 0comp_code. Did transaction data load for FIGL infoprovider.
But 0company is blank in FIGL ODS.
Any thoughts..
Thanks in advance

It should ideally pull the 0company, Otherwise try doing it thru Start routine ..
Create an internal table, pull company code and company from the master data table of Company code into this table.
Read from this table in your update routine and corresponding to the company code read the company and populate in your ODS.
It will also be better in performance compared to a master data look up !!!!!!!
Regards.

Using "Master Data Attribute of" in the Update Rule

Hi,
In my update rule of, i want to replace the master data attribute of my characteristic instead of using its source characteristic. For example. InfoObject ZSTORECODE has an attribute ZSTORENAME. My objective is to use the Store Name instead of a Store Code.
I initially thought of using "Master Data Attribute of" in the update rules. However, I always end of with having an error of "No Values."

Hope you guys can help me with this!
Thanks,
Raomon

DATA: V_NSTC_SN2,
V_KFC_COSTC LIKE RSGENERAL-CHAVL.
V_KFC_COSTC = DATA_PACKAGE-KFC_COSTC.
CALL FUNCTION 'RSAU_READ_MASTER_DATA'
 EXPORTING
 I_IOBJNM = 'KFC_COSTC'
 I_CHAVL = V_KFC_COSTC
* I_T_CHAVL =
* I_DATE =
* I_FLG_WHOLE_TABLE =
 I_ATTRNM = 'NSTC_SN2'
IMPORTING
* E_STRUCTURE =
* E_TABLE =
 E_ATTRVAL = V_NSTC_SN2
 EXCEPTIONS
 READ_ERROR = 1
 NO_SUCH_ATTRIBUTE = 2
 WRONG_IMPORT_PARAMETERS = 3
 CHAVL_NOT_FOUND = 4
 OTHERS = 5
RESULT = V_NSTC_SN2.
Another Example Code:
index on infoObject

How to extract master data attribute from r/3 to bw give steps details

how to extract master data attribute from r/3 to bw give steps details screenshots

Hi
Go through the below process to extract Master Data Attribute from R/3
Hi,
Maintaining Generic DataSources
Use
Regardless of the application, you can create and maintain generic DataSources for transaction data, master data attributes or texts from any transparent table, database view or SAP Query InfoSet, or using a function module. This allows you to extract data generically.
Procedure
Creating Generic DataSources
1. Select the DataSource type and specify a technical name.
2. Choose Create.
The screen for creating a generic DataSource appears.
3. Choose the application component to which you want to assign the DataSource.
4. Enter the descriptive texts. You can choose any text.
5. Select the datasets from which you want to fill the generic DataSource.
a. Choose Extraction from View if you want to extract data from a transparent table or a database view. Enter the name of the table or the database view.
After you generate the DataSource, you have a DataSource with an extraction structure that corresponds to the database view or transparent table.
For more information about creating and maintaining database views and tables, see the ABAP Dictionary Documentation.
b. Choose Extraction from Query if you want to use a SAP Query InfoSet as the data source. Select the required InfoSet from the InfoSet catalog.
Notes on Extraction Using SAP Query
After you generate the DataSource, you have a DataSource with an extraction structure that corresponds to the InfoSet.
For more information about maintaining the InfoSet, see the System Administration documentation.
c. Choose Extraction Using FM if you want to extract data using a function module. Enter the function module and extraction structure.
The data must be transferred by the function module in an interface table E_T_DATA.
Interface Description and Extraction Process
For information about the function library, see the ABAP Workbench: Tools documentation.
d. With texts you also have the option of extracting from fixed values for domains.
6. Maintain the settings for delta transfer, as required.
7. Choose Save.
When performing extraction, note SAP Query: Assigning to a User Group.
Note when extracting from a transparent table or view:
If the extraction structure contains a key figure field that references a unit of measure or a currency unit field, this unit field has to be included in the same extraction structure as the key figure field.
A screen appears on which you can edit the fields of the extraction structure.
8. Edit the DataSource:
○ Selection
When you schedule a data request in the BI scheduler, you can enter the selection criteria for the data transfer. For example, you can determine that data requests are only to apply to data from the previous month.
If you set the Selection indicator for a field within the extraction structure, the data for this field is transferred in correspondence with the selection criteria in the scheduler.
○ Hide field
You set this indicator to exclude an extraction structure field from the data transfer. The field is no longer available in BI when you set the transfer rules or generate the transfer structure.
○ Inversion
Reverse postings are possible for customer-defined key figures. Therefore inversion is only active for certain transaction data DataSources. These include DataSources that have a field that is marked as an inversion field, for example, the update mode field in DataSource 0FI_AP_3. If this field has a value, the data records are interpreted as reverse records in BI.
If you want to carry out a reverse posting for a customer-defined field (key figure), set the Inversion indicator. The value of the key figure is transferred to BI in inverted form (multiplied by 1).
○ Field only known in exit
You can enhance data by extending the extraction structure for a DataSource by adding fields in append structures.
The Field Only Known in Exit indicator is set for the fields of an append structure; by default these fields are not passed to the extractor from the field list and selection table.
Deselect the Field Only Known in Exit indicator to enable the Service API to pass on the append structure field to the extractor together with the fields of the delivered extract structures in the field list and in the selection table.
9. Choose DataSource ® Generate.
The DataSource is saved in the source system.
Maintaining Generic DataSources
● Change DataSource
To change a generic DataSource, in the initial screen of DataSource maintenance, enter the name of the DataSource and choose Change.
You can change the assignment of a DataSource to an application component or change the texts of a DataSource. Double-click on the name of the table, view, InfoSet or extraction structure to get to the appropriate maintenance screen. Here you make the changes to add new fields. You can also completely swap transparent tables and database views, though this is not possible with InfoSets. Return to DataSource maintenance and choose Create. The screen for editing a DataSource appears. To save the DataSource in the SAP source system, choose DataSource ® Generate.
If you want to test extraction in the source system independently of a BI system, choose DataSource ® Test Extraction.
● Delta DataSource
On the Change Generic DataSource screen, you can delete any DataSources that are no longer relevant. If you are extracting data from an InfoSet, delete the corresponding query. If you want to delete a DataSource, make sure it is not connected to a BI system.
NR

How to change specified hierachy node to master data attribute automatic?

Dear BW experts:
How to change specified hierachy node to master data attribute automatically? I have a retail business: I have a fixed material group hierachy in R3 Retail ,Now I will extract the material group hierachy ,my goal is that the specified material group hierachy node as dimension in query ,not show hierachy level,So I need change specified material group hierachy node to material group's attribute.
Anybody solve the requests?
Thank you for your help in advance !

If I understand your requirement correctly, you need to have a specific Material Group Hierarchy level (Say Level 2) to be an attribute of Material Group. Usually, this level represents a Brand or Segment, or something with specific meaning.
If this is correct, here are the things you need to do:
1) Create an InfoOnject for this specific attribute representing the specified hierarchy level
2) Add this InfoObject to Material Group as an navigational attribute
3) Select this navigational attribute in your InfoProvider
4) Create a transformation routine for this navigational attribute in Material Group Transformation so that the specified hierarchy level for Material Group will be found and populated. The detail of this routine will depend on your specific requirement. Also, you have to make sure Material Group Hierarchy is updated before Material Group attributes are loaded. If you are not family with ABAP, please ask an ABAPer to help you for the Transformation Routine.
5) Include this navigational attribute in your query along with other required InfoObjects.
Hope this help and good luck!
Bill

Master data attributes declaration in update rules

Hi Everyone,
can any one tell me, How do we use attributes of master data in update rules..need syntax for using attributes of customer.... like comm_structure-/bic/......etc
post code is attribute of customer, How do I use it in update rule
thanks
Siri

Hi!
if you have customer as attribute in your Infosource and Postcode as acharecteristic in your data target then you just need to select ther 3rd type of update rule "MAster data attribute of" and specifxy 0Cusotomer beside
with regards
ashwin

Pupulating Char with Master data attribute

Hi,
I need to populate the characteristic with a master data attribute value at the tranfer rules.
Can anybody send me the code to do so.
If it is at Update rules we have the option of Master data attribute of.
But I need to do it at transfer rules.
Thanks in advance.

Hi Indira,
It is difficult to give the exact code but, here is the pseudo code:
In the start routine:
select * from /bic/m<characteristic>
into itab for all entries in datapak
where ..............
if sy-subrc = 0.
sort itab by....
endif.
In the mapping for the info object, create a routine and the following code goes in there:
read table itab with key ......
if sy-subrc = 0.
result = itab-********
endif.
Make sure you handle time dependencies if the master data attribute is time dependent.
Hope this helps.
Thanks and Regards
Subray Hegde

Updating Master data attributes through BPS

Hi All,
Can we modify master data attributes via BPS? Like we have some Attribute characteristics for 'vendor' say 'class(good/bad/ok)' and we want that to be updated via BPS (not from R/3) then how it can be achived?
Please help by explaining this.

Hi,
Create two variables one for vendor and other for status (variable of type attribute), give both the variables in the folder. User will select the vendor and the attribute status value in selections. Create an exit planning function to update the attribute.
Import parameters
i_area type upc_y_area
i_variable type upc_y_variable
i_chanm type upc_y_chanm
Export parameters
eto_charsel type upc_yto_charsel
tables
i_t_attributes structure rsd_s_iobjnm optional
i_t_data structure rsndi_s_chavl optional
In the code, Read the above two variable values selected by user. Then delete the existing entry of MD by calling the function RSNDI_MD_DELETE.
Now update the master data with the new attribute value selected by the user in the variable by calling the function
RSNDI_MD_ATTRIBUTES_UPDATE. After this activate the master data by calling RSDMD_MD_ACTIVATE.
Hope this solves the issue.
Bindu

Master data attributes with direct update...its very urgent

Hi all,
Could anyone tell me how to laod the master data attributes with direct update in the infopackge..
provide steps to create master data attributes and how to load..
Thanks,
Manjula

Hi Manjula,
Flexible Uploading
Transaction code RSA1LEAD YOU TO MODELLING
1. Creation of Info Objects
In left panel select info object
Create info area
Create info object catalog ( characteristics & Key figures ) by right clicking the created info area
Create new characteristics and key figures under respective catalogs according to the project requirement
Create required info objects and Activate.
2. Creation of Data Source
In the left panel select data sources
Create application component(AC)
Right click AC and create datasource
Specify data source name, source system, and data type ( Transaction data )
In general tab give short, medium, and long description.
In extraction tab specify file path, header rows to be ignored, data format(csv) and data separator( , )
In proposal tab load example data and verify it.
In field tab you can you can give the technical name of info objects in the template and you not have to map during the transformation the server will automatically map accordingly. If you are not mapping in this field tab you have to manually map during the transformation in Info providers.
Activate data source and read preview data under preview tab.
Create info package by right clicking data source and in schedule tab click star to load data to PSA.( make sure to close the flat file during loading )
3. Creation of data targets
In left panel select info provider
Select created info area and right click to create ODS( Data store object ) or Cube.
Specify name fro the ODS or cube and click create
From the template window select the required characteristics and key figures and drag and drop it into the DATA FIELD and KEY FIELDS
Click Activate.
Right click on ODS or Cube and select create transformation.
In source of transformation , select object type( data source) and specify its name and source system Note: Source system will be a temporary folder or package into which data is getting stored
Activate created transformation
Create Data transfer process (DTP) by right clicking the master data attributes
In extraction tab specify extraction mode ( full)
In update tab specify error handling ( request green)
Activate DTP and in execute tab click execute button to load data in data targets.
4. Monitor
Right Click data targets and select manage and in contents tab select contents to view the loaded data. There are two tables in ODS new table and active table to load data from new table to active table you have to activate after selecting the loaded data . Alternatively monitor icon can be used
honor with points if this helps,
Sudhakar

About delta loading for master data attribute

Hi all,
We have a master data attribute loading failed which is a delta loading. I have to fix this problem but I have two questions:
1. how can I find the those delta requests because I need to delete all these failed requests first, am I right ? Master data is not like cube or ods that we can find the requests in Manage, for master data how can we find them ?
2. Could you please let me know the detailed procedures to perform this delta loading again ?
Thanks a lot

Hi...
1. how can I find the those delta requests because I need to delete all these failed requests first, am I right ? Master data is not like cube or ods that we can find the requests in Manage, for master data how can we find them ?
Look.....for master data.....no need to delete request from the target..........just make the status red.......and repeat the load.....But problem is that master data sometimes does'nt support Repeat delta..........if u repeat......then load will again fail with Update mode R.........in that case u hav to do re-init.......
1) delete the init flag.......(In the IP scheduler >> in the top Scheduler tab >> Initialization option for source system)
2) Init with data transfer(if failed load picks some records)..........otherwise .....init without data transfer.....if the last delta failed picking 0 records.......
3) then Delta.......
2. Could you please let me know the detailed procedures to perform this delta loading again ?
1) Make the QM status red.........to set back the init pointer.......
2) Repeat the load.....
After that.........if again load failed with Update mode R.....
1) delete the init flag.......
2) Init with data transfer(if failed load picks some records)..........otherwise init without data transfer.....
3) then Delta.......
Regards,
Debjani.....

Force read/refresh of master data attributes on query

Hi there,
We're having troubles with one input ready query that changes and attribute value (KYF) of one characteristic. That works fines and whe can save changed data on the infoprovider via DTP. Problem is when data is saved we need to refresh query as whe have both values on screen (original value as char attribute on rows) new value as input ready KYF, so after save we would like to see that both values are the same.
Is there any way of force query no to read from caché as whe are changing master data attributes. I read something about IF_RSMD_RS_ACCESS class that can be implemented on Master Data access and force it there but sounds really hard so if this is the way can some of you guys give us some help.
I hope I make myself clear on the explanation...
Thanks in advance,
Regards
Carlos

Dear All,
The recent days that I tried working on changing master data attributes through BPS didn't work out.The Primary reasons was that some of the attributes that I needed to change were not present in the transaction or planning cubes and the characteristics that are not part of your cube on which the planning area is based then you can not do changes on them.
This is my undestanding .Please correct me if I am wrong.
Besides , I was also thinking if we can do the same through portal.i.e retriving the master data infoobject ( based on the value seleceted for that infoobject by the user ) and its attributes in the portal , edit them and save them back so that the updated values goes back to BW master data infoobject data base tables and updates the value.
Eg . I have Natural Account master data infoobject in the BW with attributes fucntional area and expense center.Based on the user selection of any values for the Natural account lets say 01110 , then for 01110 natural account the portal should display the correspoding attributes values of fucntional area and expense center.Lets take this values as 10 , 20 respectively for fucntional area and expense center . What I want to do now is to change these attrbute values to 30 and 40 and I would like to save it back as the changed attribute values for that natural account for 01110 with new attribute values 30 & 40 respectively for fucntional area and expense center .
Is this possible through portal and BW?
Any idea on this would be appriciated.
Regards,
Ankit
Edited by: Ankit Bhandari on Nov 21, 2008 12:21 PM
Edited by: Ankit Bhandari on Nov 21, 2008 12:32 PM

Error while uploading master data attributes thru flat file

while uploading master data attributes thru flat file i am facing the below errow. can nyone let me know plz.
Error 8 when compiling the upload program: row 227, message: Data type /BIC/CCDEIO_MAT5_ATTR was found in a new

This just means that you changed the transfer rules/transfer structure and have not refreshed the workbench yet. The infopackage data hasn't been updated ... this is similar to a datasource update, where you need to replicate to make sure BW knows the latest version.
The best way to correct this error is to reload RSA1. Every time I make a change to the tr/ts, I always run /nrsa1 to refresh the workbench.
Brian

Webi error for master data attributes if universe is on top of BI query

Hi All,
We are using BO XI R2 SP5 integrated with SAP BI 7.0.
We have built a universe on top of a BI query and when we try to build a web intelligence report that includes master data attributes like Customer City,Customer Region etc BO throws the following error:
Error 1:
Database error: [SOFA Driver] : Error getting members for hierarchy (level=ZFI_I03/ZFI_I03_Q0003, member=[ZFI_I03___F172], opcode=[ZFI_I03___F172]) . System error in program CL_RSDM_READ_MASTER_DATA and form VALUEREAD-02- (see long text). Contact your Business Objects administrator or database supplier for more information. (Error: WIS 10901)
For a universe built on a different BI query with master data attributes mentioned above,a different error occuring.
Error 2:
Your Web Intelligence session has timed out. Log out and log in again to InfoView. (Error: WIJ 77778)
We have tried:
1) We have executed the function module BAPI_MDPROVIDER_GET_DIMENSIONS with necessary inputs query/cube and we got correct output, like members, optional properties, selected properties and restrictions.But, still our problem remains same.
2) Transaction u201CRSRTu201D and executed the query,transaction RSRV to check SID-tables and the related masterdata.
Above steps we performed in response to SAP tickets 541052 / 2009,541131 / 2009 based on logs generated,but still the error persists.
What is working:
If a universe is built on top af an infocube directly, then there is no problem with master data attributes in webi report.
Please let us know if you need more details to help us resolve this issue.

Hi Naresh,
based on the MDX you can identify that those are navigational attributes and thats why the issue is not happening when talking to the cube directly because when you connect to the cube directly the navigational attributes are not available.
Take a look at note : 996197
not sure if it will solve the problem because there are other notes when you search for the error message but this was most of the times the one that resolved the issue.
the issue is in the BAPI functions
Ingo

LOOKUP-Master Data Attribute (ABAP Code)

Similar Messages

Maybe you are looking for