Incident management and Critical Master data table change management.

Dears,
I need to configure Incident management and Critical Master data table change management on our solman 7.0 server.
I want to know how many days should be required for this activity and please share documents.
Shivam

Hi,
I faced a similar situation,
I tried all the possible ways like activating InfoObject manually, Through an activation program of aggregates,
Also ran RSRV check which was showing no negative results.
I raised an OSS note for the same but after that when SAP returned back the process chian ran again as it is a daily load which activated the record in 'M'.
I ask you to wait till the next process chian run, and try all possible ways to activate.
If it is not corrected then raise an oss to SAP.
Thanks & Regards,
Vishnu

Similar Messages

How are attribute and text master data tables linked in SAP R/3?

Hello,
how are attribute and text master data tables linked in SAP R/3?
Most tables with attribute master data like T001 for company codes,
have a text master data table T001T (add "T" to table name).
When looking at the content of table T001 via transaction se11,
the text are automatically joined.
But for some tables there is no "T"-table (e.g. table TVBUR for sales offices
has no text table TVBURT), but in se11 you get texts. There is an address
link in TVBUR, but the Name1, etc. are empty.
a) Where are the text stored?
b) How does the system know of the link?
Hope someone can help!
Best regards
Thomas

Hi Thomas
The master and text table are not linked by name, of course, if you see the text table, it has the same key fields of master table, only it has the field key spras and the field for description.
The link beetween the tables is done by foreign key: if you check the text table TVKBT u need to see how the foreign key for field VKBUR is done:
-> Foreing key with table TVBUR
-> Foreing key field type -> KEY FIELD FOR A TEXT TABLE
->Cardinality-> 1-:CN
It's very important the attribute sets for Foreing key field type, if it's KEY FIELD FOR A TEXT TABLE, it'll mean the table is a text table: i.e. that mean the master table is a check table for the text table, where the foreign key type is for text table.
U can find out the text table of master table by SE11: GoTo->Text Table
U can fined some information in table DD08L.
Max

Material Master Data and PO Master Data Table

Dear SAP Gurus and Expert,
Currently user is having a new integration system which link to SAP, and they require the migration of Material MAster Data and PO master data.
As a result of that, what table can be accessed in SE16 in order to get all the material master data and PO master data to be exported to excel fil format.
Thank you
Regards

Hi,
For material master data
MARA                           General Material Data
MARC                           Plant Data for Material
MAKT                           Material Descriptions
MARD                           Storage Location Data for Material
You can enter MA* in SE16 and press F4 too get all the tables according to the views.
For Purchase order
EKKO
EKPO
EKBE
EKKN
Search for EK* in SE16.

Mismatch between Master data table /BIC/P and SID table /BIC/S

Hello All,
in our master data table we have logsys in key
after a system copy we had a problem with logsys name, when we have copied our bw prod system in test system we find prod logsys like value, the BDLS doesn't change all values for all structures and some master data table still have prod logsys instead of test logsys but some records have test logsys values
for example:
our production logsys is: BIP300 and our test logsys is BIT300
in our master data test table we find had some records logsys value like BIP300 and others with BIT300
all our ODS and CUBE have the right logsys value in test "BIT300"
we have developed an ABAP report to execute on selected tables to change logsys from BIP300 to BIT300
we execute the report on only P master data table like /BIC/PZCOOR and it's work fine and has changed all the records values
from BIP300 to BIT300 and this program has eliminated all duplicate records
the problem is when on our master data try to view data we find that bw return data from SID table /BIC/SZCOOR
in fact if we go to control data on /BIC/SZCOOR table we find that there still are records with logsys BIP300 and BIT300
and the same if we execute our query on ZCOOR we have values with BIP300 and BIT300
how should we fix this problem?
if we execute our ABAP report on /BIC/SZCOOR to change logsysname we can fix that or we could have problem?
please can give me some useful help
thanks a lot
Bilal

Hi ,
Follow the sequence of deletion .
1.Delete data from cube YMM_*
2.Delete data from 0pur_c*
3.Delete data from 0material .
4.Delete data from info_rec .
Best option would be do selective deletion for these four materials and run a repair request then after to update into data target.
Hope that helps.
Regards
Mr Kapadia

Impacts in COPA of changing material and customer master data

Dear experts,
In my company we are considering following scenario:
Currently mySAPerp 6.0 is implemented for all modules for the mother company.
We have developed a new global template where there are significant changes versus the existing system, especially in the SD processes. Material and customer master also change significantly in terms of content in the tables/fields and/or values in the fields.
The idea was to build the template from scratch in a new machine and roll-out all group affiliates, but now we are considering the possibility of making an evolutionary of the current system and try to stretch it to the processes defined in the global template.
The scenario we want to analyze is: Keeping same organizational structure in terms of Company code, CO area and Operating Concern in existing SAP client and make an evolutionary of the existing settings to the global template processes.
The doubts we are having are the following:
Changing material & customer master data: Impact in COPA
Option 1: Material master data and customer master data codes are maintained but content in the tables/fields is changed substantially, both in terms of logical content of specific fields and/or the values in the specific fields. We have following examples of changes.
Case 1: source field in material master changes logical content. E.g. Material master field MVGR1 is currently used for product series (design line) and the content changes to be the Market Segment. The product series will be moved to a classification field. At least 5 other fields are affected by this. How can data in terms of COPA line items be converted so that they are aligned at time of reporting?
Case 2: the source field is not changed so that the logical content of the field remains but the values change, i.e. for the same concept there will be different codifications. How can data in terms of COPA line items be converted so that they are aligned at time of reporting?
Case 3: Characteristics where currently the source material master field is a Z field and the derivation is via table look up and where the Z field changes to a classification field. How can you convert the existing COPA line items to ensure that attributes are aligned? Should new characteristics be created or just change the derivation logic of the characteristic?
Option 2: Material master data and customer data codes are re-created (codification of records is changed), meaning that new material and customer codes will exist and content in tables/fields is changed (as in option 1)
Case: material and customer codes are changed. How can data in terms of COPA line items be converted so that they are aligned at time of reporting?
Iu2019ve never phased a similar scenario and I fear that maintaining operating concern while changing source master data and also SD flows (we have new billing types, item categories, sales doc. Types, order reasons) may lead to inconsistencies and problems in COPA.
I would like to ask you experts if you have come across a similar scenario and if from your experience, it is something feasible to do or there are many risks involved. What can be the impact of this scenario in existing Operating Concern for both option 1 and 2 and what would be the key activities to perform to adapt the existing operating concern. What will be the impact of the needed conversions on P&L reporting?
Sorry for the long story. I hope you can help me out.
Thanks and Regards,
Eric

Hi,
First i think you will need to test if it works for new COPA documents created via billing.
If it works fine then the issue is if you wish to apply these changes to the historical data already posted.
Normally there are transactions like KE4S where you can repost the billing document to COPA
However this may not be viable for bulk postings
You can perform realignment (KEND) but this only works at the PA segment level (table CE4XXXX)
regards
Waman

Web report data provider change from Master data table to InfoCube

hi Experts,
I have created one report on top of multiprovider but in the selection screen when i check the values for a variable I came to know that data is coming from master data table and not from data provider(InfoCube).Can any one help to change the data selection from master data table to data provider(InfoCube) and i am sure that there is no ODS involved in the multiprovider.
Thanks in advance
With Regards,
Bala

Hello,
If u are using Analyser then just put a Analysis Grid on the output of the query(should cover all the rows and column) , click on the grid and put the dataprovider. and do auto fit.
Rohit

Changing Master data table keys

Hello,
I have a custom extractor (built by someone else)on R/3 that gets data from table HRP1001. This extractor contains data I need to implement "job relationships" for HR in BW.
I am trying to extract the data into a master data object on BW. One job in the HRP1001 table (OBJID on R/3) can have multiple relationships (or object types, OTYPE on R/3). However, since the key of the master data for 0JOB is just JOB, OBJVERS, and DATETO (and does not include OTYPE), the load fails due to duplicate records.
Since to modify the master data table for 0JOB would be an SAP mod, I created my own "Z" object from 0JOB. I have been manipulating the /BIC/M, /BIC/P and BIC/Q tables to try to adjust the key to include at least the OTYPE. I can successfully change the key of the Z object's master data to appear as I want it, but the new objects I added as keys are "flagged" after the load fails due to duplicate records. (Checks of each /BIC table are okay and activated changes. Also performed SE14 adjustment of each table)
So my questions are 1) does anyone know of a business content item that for storing this type of data that I have missed? and 2) If not, can anyone recommend how I can correctly modify the key fields of a master data object?
Any assistance is greatly appreciated.
Thank you,
Kelley

Hello Kelley,
If you want to enhance the key of your master data table, include the infoobject in compounding. All the infoobjects included in compounding will be included in the key of master data table.
Hope it helps.
Regards,
Praveen

Deleted and adjusted the Master data table, sid table and text table

Deleted and adjusted the master data table, sid table and text table of an zinfoobject after removing and adding attributes to that zinfoobject and was trying to activate it and system was giving me messages that cannot activate infoobject something like this.
So, i deleted and adjusted the master data table, sid table and text table. Since then getting messages right after executing the query because in that query that infoobject is getting used.
So the messages i am getting is:
SID 9 for characteristic Zinfoobject could not be converted CL_RSDM_READ_MASTER_DATA->_SIDVAL_DIRECT_READ2
System error in program SAPLRRK0 and form MEGA_SORT_M_02-02- (see long text)
Please help me in fixing this whole thing.
Thanks
SAPBW

SAP BW,
After adjusting your Master Data IOBJ and deleting and reloading the data - run a change run to adjust the references to the SIDs and then see if your query runs - run program RSDDS_AGGREGATES_MAINTAIN from se38 and select your IOBJ in the next screen..
Arun
Assign points if useful
P.S I did notice that in your earlier post for the same topic - you have had 12 answers / suggestions Please maintain only one thread as previously suggested..
My 0.02
Message was edited by:
Arun Varadarajan

Join between fact table and master data table

Is it posible to join a Cube with a Characteristic? This is exactly what i need:
- In my cube i have date (0CALDAY) and (among others) a characteristic (ZCHAR) and a key figure (ZKEYF).
- I added a key figure (ZKFAT) as an attribute to ZCHAR. So the tables look something like this:
Fact table:
0CALDAY | ZCHAR | ZKEYF
12.10.2006 | CHAR1 | 10
12.10.2006 | CHAR2 | 20
12.10.2006 | CHAR3 | 30
Master data table for ZCHAR:
ZCHAR | ZKFAT
CHAR1 | 1000
CHAR2 | 2000
CHAR3 | 1500
I need to make a query with a table that looks like this:
0CALDAY | ZCHAR | ZKEYF | ZKFAT
12.10.2006 | CHAR1 | 10 | 1000
12.10.2006 | CHAR2 | 20 | 2000
12.10.2006 | CHAR3 | 30 | 1500
Finally, the query should result in something like this:
0CALDAY | ZKEYF | ZKFAT
12.10.2006 | 10 | 1000
12.10.2006 | 20 | 2000
12.10.2006 | 30 | 1500
Adding KFAT to the fact table is not an option, i need to read this information directly from ZCHAR.
I've tried using MultiProviders but didn't get the result i need.
Is there any way to achieve this? Please advice.
Thank you,

Thank you Ram C. i've tried your solution and it may be it, but i'm having one problem:
Since i'm reporting in web, i used the second solution you offered and almost got the desiered result. The problem is that some entries are correct but others ar duplicated! Using same example, my result table looks something like this:
0CALDAY | ZKEYF | Calculated KF (from ZKFAT)
12.10.2006 | 10 | 1000
12.10.2006 | 20 | 4000
12.10.2006 | 30 | 1500
Second row should be 2000, but instead it shows 4000. I added ZCHAR's attribute ZKFAT as a display attribute in order to compare the results. I found that the display attribute is correct (2000) but the Calculated KF still showed duplicated data (4000).
By the way, when i execute the query, i get this warning message:
"Calculated key figure ZRT_C02_2_CKF004 is not defined correctly"
Any ideas why this could be happening?
Thank you for your help.
Message was edited by: Gerardo Gaona

Hi,master data tables and SID's

Hi,
Where and how we will find the master data tables and SID tables?I am going to se16 and checking there but i am not able to see there in which table these are located or stored?
Thank you,
Sekhar..

>
chandra sekhar wrote:
> Hi,
> Where and how we will find the master data tables and SID tables?I am going to se16 and checking there but i am not able to see there in which table these are located or stored?
> Thank you,
> Sekhar..
Assuming the infoObject name is ZINFOOBJECT.
The tables are :-
/BIC/MZINFOOBJECT       View of Master Data Tables: Characteristic
/BIC/PZINFOOBJECT       Master Data (Time-Ind.): Characteristic
/BIC/RZINFOOBJECT        View SIDs and Char. Values: Characteristic
/BIC/SZINFOOBJECT       Master Data IDs: InfoObject
/BI0/HZINFOOBJECT                 Hierarchy: InfoObject
/BI0/IZINFOOBJECT                 SID Structure of Hierarchies: InfoObject
/BI0/KZINFOOBJECT        Conversion of Hierarchy Nodes - SID: InfoObject
/BI0/TZINFOOBJECT        Texts: Char.
/BI0/XZINFOOBJECT       Attribute SID Table: InfoObject
/BI0/ZZINFOOBJECT       View Hierarchy SIDs and Nodes: Char.

Master data tables and Transaction data Tables

Hello Gurus,
Please let me know how to know which table belongs to master data and which table belongs to transaction data.
for FICO module.
Does any one have specific material relating to master data table and transaction data tables.
Thanks
Edited by: Manu Rathore on Jan 18, 2012 4:38 AM

Hi Manu,
Find attached table relation diagram by Christopher Solomon. It is one of the very comprehensive chart on this topic.
deleted
Warm regards,
Murukan Arunachalam

How to create time dependant master data table in R/3?

Hi gurus,
I am new to BW.I try to execute the 'Time dependant Attribute' into BW.in my scenario my source system must give me the data like "salesrep ID,Manager ID,Date to,Date from,Sales region". I like to know how to define this master data in SAP R/3(Source system)?. Give me the steps to create master data table in R/3.
Manager may change periodically.even i need to maintain all the changes in R/3.
Thanks & Regards,
Bharath

built-in type method means.,
there is no need to create data element and domain objects seperately for each and every field of the table which ever you are creating, system will implicitly fix the size based on the data type you selected....

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

How to find the number of entries in a master data table

Hi Experts,
I am trying to find the entries in 0CUSTOMER master data.
BW>LISTCUBE>Data target: 0CUSTOMER and selected the fields that I need.
I would like to know how to find the "number of entrees". I tried to run the SUM for a count field, but it is taking forever as there are huge number of records .

Hi Dev,
Go to the change/display mode of the info object (0CUSTOMER) in your case. Go to the Master data/Text tab. Here you will find the master data tables according to your settings (P orQ or X or Y). Double click on the table name and it will take you to the SE11 display. From there, you can check the number of records as you do in any transparent table.
Hope this helps.
Thanks and Regards
Subray Hegde

Error while realigning aggregates through master data attr. change run

Hi all,
We are using Sales Overview cube (SD_C03) on which we have built aggregates. now during the master data attribute change run it tries to realign the aggregate once the master data is loaded via Process chain. In this step we are facing an error:
"Error while procesing aggregate <aggregate technical name>"
From ST22 we can find
Database error text........: "ORA-14400: inserted partition key does not map to any partition"
Internal call code.........: "[RSQL/INSR//BIC/F200009 ]".
Whereas from SM21 we can find out:
Database error 14400 at INS access to table /BIC/F200009.
/BIC/F200009 is the fact table of one of the aggreates we have. really looking forward to your valuable suggestion.
Thnaks,
Abhishek.

Hi Jogeswara Rao Kavala,
When I am pressing back or NO option it is showing error like this
What is this OK- Code means?
how can I resume this process, even it was not going to back screen also and only one option is available for exit from this is by going into MENU-SYSTEM-SERVICES-BATCH INPUT-CANCEL.
Sunil Boya

Incident management and Critical Master data table change management.

Similar Messages

Maybe you are looking for