Transferred records and added records

in Cube manager, I see the number of transferred records and added records in each request are always different.
what's the exactly means of those two field ? I guess added records is record loaded into cube without any duplicated, right?

Hi Jie,
Refer these links:
Re: difference i transfered records and added records
Re: manage infocube
Bye
Dinesh

Similar Messages

What's the difference between Transferred Records and Added Records?

When right click an ODS or a cube to select Manage, then under the 3rd tab called Requests, there are two columns called Transferred Records and Added Records, what's the difference between these two?
Thanks

Hello KeLviN,
How r u ?
Consider a realtime example.
Assume a transfer of Transactional Data from R/3(with PSA) which is having Unit values in it.
Now, I found in RSA3 2844168 of records. In BW I saw one Data Packet with 306 error records(because of a UNIT value is not available in BW T006 table, Eg. YDD) which are automatically collected in PSA. Now in the Monitor screen you could see 2 Monitor status with GREEN Signals for 2 set of data.
1. with 2843862 records
2. with 306 records
Now, if u manage the Data Target you will get 2844168 in the Transferred Records & 2843862 in the Added Records. and the 306 error records are in the PSA.
Hope this is clear.
Best Regards....
Sankar Kumar
+91 98403 47141

Whats the diff between Transfered Records and Added Records

Hi
whats the diff between Transfered Records and Added Records in any data target Request Tab.
Regards
ll

Hi.......
Check this.......
What's the difference between Transferred Records and Added Records?
Manage ODS : Difference of Transferred Records and Added Records
Regards,
Debjani......

Manage ODS : Difference of Transferred Records and Added Records

Hi there,
When I click on Manage ODS , I have the following fields
Transferred Records and Added Records.
Please advice the difference

Hi,
Transferred Record coloumn indicated how many records were tranferred from the source system to BW,means how many records were extracted at that point of time and another Column indicates that the total number of records added to your data target.these two cloumn vales may not be same for all the time,becoz if you have filters at the update rule level....in this case numbers records tranfered and numbers records added might be different.......
Transferred refers to the number of records that are transferred from the datasource (arrive in BW). Added is the number records inserted into the ODS. Both can be different numbers, like due to any processing of the data.
Added records refer to which is really inserted in ODS (your start routine, for example, can reduce the number of transferred records by deleting something!)
Ex
transferred records means the total records from source e.g ods. say data coming from ods
docnumber docitem customer qty
001 1 x 10
001 2 y 20
002 1 x 30 (3 records)
and your infocube has char customer and keyfigure qty, so
record added
customer qty
x 40
y 20 (2 records)
so here you have transferred records = 3 and added records = 2
Refer these posts:
Re: transferred records and added records
Re: Transfered and Added Records
Re: Clarification about ODS - Transferred & Added records
-Shreya

Difference i transfered records and added records

Hi friends,
I have loaded data into ODS and it was succesful,but when i check in the Requests tab in mangae i found that number of records transferd is 4000 but number of records added is just 1401. can anyone please advise me where ami going wrong.
Regards
Ananth

Hi,
The reason they could be different for an ODS is because in an ODS the record is identified based on the key fields.
For example
If I have GL posting document wherein the Posting document no. is the key field in the ODS. I may have modified the same GL posting document in R/3 for 6 times but wben it is uploaded into an ODS it will just contain one record for the final staus of the GL posting document.
So in this case even if 6 records are transferred, only one record will be added to the ODS.
As a result it is not always necessary that there might always be something wrong when the transferred and added records are different.
But for ODS it is important that the key field is correctly identified, if that is not the case you might have records being overwritten (transferred records more than added records) which might be wrong.
So I would suggest you to check the Key fields, and if your totals match with R/3 or the source data.
Hope it helps
Cheers
Anurag

Why can I have a difference between Transferred Records and Added Records

Hello gurus,
What could be the reason for the difference between the Transferred records and the added records in the request for an InfoObjects?
I have in RSA3 6452 Records and in the Manage-InfoObject 1002 Records.
thanks for your help

- already existing master data (changed but not new)
- start routine with deletion
- duplicate records (with error handling activated)
- end routine

Difference between Transferred Records and Added records

Hi,
I am loading data into infocube ZPT_C01, a copy of 0PT_C01. In the "Manage function", under "Requests", I see two columns. One that says Transferred Records: 271370 and the other Added records: 30320.
I understand that 271370 is the number of records in the PSA. Is 30320 the number of records added to the Infocube?
Why aren't those two numbers identical? Are records lost? Can someone explain to me why the two record numers aren't the same?
Thanks in advance
Michalis

Hi,
the collapsing of a request is usually done when its data has been judged "correct" since a collapsed request cannot be deleted from an InfoCube.
Now in your case, it seems that you are always having one request in your ICube and you systematically delete the datatarget content prior loading it; you could collapse your request or not. If you collapse it you might get less records in your E fact table with the corresponding increase of query runtime; however if the ratio #records collapsed (in E table) / #records collapsed (in F table) is close to 100%, you most probably don't need to collapse this request.
In your scenario you have to be careful with the dimension tables; indeed when you delete the cube content via a chain, the dimension tables won't be deleted (that's good since when the next request will come the system won't have to recreate all the DIMIDs already present) and after a while many of these DIMIDs will perhaps not be used (you can run the corresponding RSRV check to verify this)...
hope this helps...
Olivier.

Difference in Transfered Records and Added Records

Hello All,
I did the delta load of my Sales Orders and Items for the first time. The load is successful but when I see in the Manage Screen of the ODS, I noticed that the number of the Transfered records and the Added Records are different i.e for ex: the Transfered records are 4 and the added records are 2.
Why is this happening? Is this because I miss something?
Rgds,
Sharath.

Hi Sharath,
As manga said it might due to transformations - update / tranfer rules.
Another reason would be the key of ODS for eg: if the extractor is pulling based on say three key fields from the base table say A B C and if you defined only A B as the key in ODS then these gets overritten
Hope this helps
Thanks,
Raj

Transfered and Added Records

Hi friends,
I know that the added records can be less than the transfered records. A substantiated discussion was found in one of the earlier threads. But, I have a situation where added records are more than the transfered records. RSA3 shows me 1000 records but, added records in the cube shows 1032 records.
1. Under what circumstances can this happen?
2. How to check where the problem is in this case?
Thanks in advance
Subray Hegde

Hi,
Probably the records are split in your case in the update rules and hence more no. of added records.
Check this:
Re: transferred records and added records
Re: difference i transfered records and added records
Re: manage infocube
Bye
Dinesh

Transferred records vs Added records

Hi all,
i've understood the differences between two fields shown in "Manage Data Target", then TAB "Request.These are the fields:
- "transferred records";
- "added records".
Could you please help me on this?
Thanks in advance,
Federico

Hi Federico,
Please try to search the forums:
Transferred and Added records
transferred records and added records
Hope this helps...

Transfered and Added records at DSO level

Hello Experts,
I am always confused about Transfered and Added records at DSO level. While I was testing DSO data I observed that, Transferred records are after Transformation before End routine. Added records are after End routine added to the New data table. Can u please put some light on this.
Many thanks,
Zakir Khan.

Hi
The Transferred Records column displays the number of records transferred to the BI system. The records are usually written to the PSA first of all.
The Added Records column displays the number of records that were written into the InfoProvider. This number can differ from the number of transferred records if records were filtered out or added during the transformation
Please Refer Below Link
Re: added records and transferred records
Thanks

DB Connect DataSource PSA records and DSO records are not matching...

Dear All,
I'm working with SAP NetWeaver BW 7.3 and for the first time, I have loaded from Source System DB Connect. I have created a DataSource and pulled all records and found 8,136,559 records in PSA. When I designed and created DSO with Key Fields 0CALDAY, Item No and Company Code, it has transferred records about 8,136,559 and added records about 12,534 only. Similarly following InfoCube has about 12,534 records into its Fact table. When I tried to reconcile the data/records with source DBMS for a month, the records/data could not matched?
1. What could be the reason behind the issue? why I am unable to load the records/data correctly?
2. Have I not mentioned the Key Fields of DSO in a correct manner?
3. Is it possible to load the records/data into DSO without giving any field as Key Fields?
4. How should I resolve this issue?
5. Is it could be of DSO Overwrite and summation function utilization if yes, then how to utilize it?
Many thanks,
Tariq Ashraf

Dear Tariq,
1. What could be the reason behind the issue? why I am unable to load the records/data correctly?
Ans: Check transformation once. Is there any start routine you have used or direct assignments. What kind of DTP settings you have done.
Check the messages at the DTP monitor. You will surely find some clue. Any duplicate records are being detected or not check once if you are using semantic keys in your DTP.
2. Have I not mentioned the Key Fields of DSO in a correct manner?
Ans: The transformation key and the DSo key are they same in your case?
What kind of DSO is it? Like for sales order DSO you take Order number as a key field., So you have to define the key fields according to business semantics I suppose. Do you agree?
3. Is it possible to load the records/data into DSO without giving any field as Key Fields?
Ans: I dont think so as the keys you defined will help in having unique data records isnot it?
4. How should I resolve this issue?
Ans: Please check the above as in Ans:1 please share your observation.
5. Is it could be of DSO Overwrite and summation function utilization if yes, then how to utilize it?
Ans: DSO overwriting of key figures is useful when you have full loads in picture. Are you always going to perform full loads ?
For reference would you like to check this thread: Data fileds and key fields in DSO
Lets see what experts give their inputs.
Thank You...

Missing "Add Records" and "Refresh Records" options for data sets post domain re-import

We recently had to re-install the Endeca server and as part of which had to export and re-import the data domains. Everything went fine except for the fact that newly re-imported data sets showcase just the "Manage Attributes" and the "Delete Data Set" options for an administrator login in. The previously available options to "Add Records" and "Refresh Records" beyond manage attributes/Delete Data Set are missing.
Thoughts? Is there a security setting to enable these?

So are you talking about the Add Records and Reload Records options for a data set in Studio?
There are no separate security settings for these options. If a user is an application administrator (is able to edit the application), then they should have access to these options.
The options are only available for data domains created using the Provisioning Service (created by uploading a file or from the JDBC or BI Server data source from the Data Source Library).
I don't know if the process of exporting and re-importing the data domains (not sure how you did that) could somehow cause the data sets to no longer know that they were created by the Provisioning Service, in which case those options would not be enabled.

IDoc Control Record and Status Record Code, where is it!!!

Hi,
Where can i see the code for generation of control record and status record of IDoc.
   Thanks in advance for your answers

hi ,
1.first create an segment with the fields u want tcode we31 relase it .
2. create an idoc and assign segment to it tcode we30.
3.crate a message type tcode we81
4.assign that message to idoc tcode we 82.
do the ale configarations .
now u can write the code in our sender system
*1.     Create parameters/select-options for input data. i.e., message type, logical system.
parameters : p_mestyp like edmsg-msgtyp default 'ZKKUMSG',
             p_logsys like tbdlst-logsys obligatory.
*2.     Create Data objects for control record, data record and database table.
data : c_segment like edidd-segnam value 'ZKKUSEG',        "Data record (IDoc)-Segment type
       c_idoctp like edidc-idoctp value 'ZKKUIDOC'.            "Control record (IDoc)-Basic type
data : begin of i_tab occurs 0,
          ZKSNO   like ZKSTD-ZKSNO,
          ZKSNAME like ZKSTD-ZKSNAME,
       end of i_tab.
data : w_itab like i_tab.
data : s_segment like ZKKUSEG.
data : i_edidd like edidd occurs 0 with header line.
data : i_control_record like edidc.
data : i_comm_idoc like edidc occurs 0 with header line.
*3.     Select the data from responding tables into internal table for a defined condition.
here you have take ur internal table
*select single zsno zsname from zkiran into corresponding fields of itab where zsno = p_sno.
*4.     create control record into internal table.
i_control_record-mestyp = p_mestyp.         "Message Type
i_control_record-idoctp = c_idoctp.         "Basic type
i_control_record-rcvprt = 'LS'.             "Partner Type of Receiver
i_control_record-rcvprn = p_logsys.         "Partner Number of Recipient
*5.     create data record into internal table.
*i_edidd-segnam =   c_segment.
loop at i_tab into w_itab.
s_segment-zksno    = w_itab-ZKSNO.                     "Application Data
s_segment-zksname = w_itab-ZKSNAME.
i_edidd-sdata     = s_segment.
i_edidd-segnam    = c_segment.
clear w_itab.
append i_edidd.
endloop.
*6.     Process ALE Service Layer using the function module MASTER_IDOC_DISTRIBUTE. It returns the corresponding IDoc No.s.
call function 'MASTER_IDOC_DISTRIBUTE'
exporting
    master_idoc_control            = i_control_record
tables
    communication_idoc_control     = i_comm_idoc
    master_idoc_data               = i_edidd
exceptions
    error_in_idoc_control          = 1
    error_writing_idoc_status      = 2
    error_in_idoc_data             = 3
    sending_logical_system_unknown = 4
    others                         = 5.
if sy-subrc <> 0.
message id sy-msgid type sy-msgty number sy-msgno
          with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
*7.     Display Communication IDocs.
loop at i_comm_idoc.
write : / 'Communication IDoc No. is : ', i_comm_idoc-docnum.
endloop.
*8.     Commit Work.
commit work.
i hope this sample code help u .
thanks

How to print the error records and success records in bdc

how to print the number of error records and success records in bdc

hai,
plz refer this program,
Z_130399130271_A
REPORT Z_130399130271_A
       NO STANDARD PAGE HEADING LINE-SIZE 325.
*INCLUDE YVALIDATE.
*include bdcrecx1.
INCLUDE YINCLUDE399.
DATA ITAB LIKE TABLE OF FILE_TABLE WITH HEADER LINE.
PARAMETERS: DATASET(132) LOWER CASE.
DATA : RC TYPE I,
ERR(40) TYPE C,
SUCCESSCNT TYPE I VALUE 0,
FAILCOUNT TYPE I VALUE 0.
   DO NOT CHANGE - the generated data section - DO NOT CHANGE    ***
If it is nessesary to change the data section use the rules:
1.) Each definition of a field exists of two lines
2.) The first line shows exactly the comment
      '* data element: ' followed with the data element
      which describes the field.
      If you don't have a data element use the
      comment without a data element name
3.) The second line shows the fieldname of the
      structure, the fieldname must consist of
      a fieldname and optional the character '_' and
      three numbers and the field length in brackets
4.) Each field must be type C.
Generated data section with specific formatting - DO NOT CHANGE ***
DATA: BEGIN OF RECORD OCCURS 0,
data element: LIF16
        LIFNR_001(016),
data element: KTOKK
        KTOKK_002(004),
data element: ANRED
        ANRED_003(015),
data element: NAME1_GP
        NAME1_004(035),
data element: SORTL
        SORTL_005(010),
data element: STRAS_GP
        STRAS_006(035),
data element: PFACH
        PFACH_007(010),
data element: ORT01_GP
        ORT01_008(035),
data element: ORT02_GP
        ORT02_009(035),
data element: LAND1_GP
        LAND1_010(003),
data element: REGIO
        REGIO_011(003),
data element: SPRAS
        SPRAS_012(002),
data element: TELF1
        TELF1_013(016),
data element: TELF2
        TELF2_014(016),
data element: BANKS
        BANKS_01_015(003),
data element: BANKK
        BANKL_01_016(015),
data element: BANKN
        BANKN_01_017(018),
      END OF RECORD.
DATA:   BEGIN OF ERRORITAB OCCURS 0,
        LIFNR_001 LIKE LFA1-LIFNR,
        KTOKK_002 LIKE LFA1-KTOKK,
        ANRED_003 LIKE LFA1-ANRED,
        NAME1_004 LIKE LFA1-NAME1,
        SORTL_005 LIKE LFA1-SORTL,
        STRAS_006 LIKE LFA1-STRAS,
        PFACH_007 LIKE LFA1-PFACH,
        ORT01_008 LIKE LFA1-ORT01,
        ORT02_009 LIKE LFA1-ORT02,
        LAND1_010 LIKE LFA1-LAND1,
        REGIO_011 LIKE LFA1-REGIO,
        SPRAS_012 LIKE LFA1-SPRAS,
        TELF1_013 LIKE LFA1-TELF1,
        TELF2_014 LIKE LFA1-TELF2,
        BANKS_01_015 LIKE LFBK-BANKS,
        BANKL_01_016 LIKE LFBK-BANKL,
        BANKN_01_017 LIKE LFBK-BANKN,
        ERRORMSG(60) TYPE C,
        SERIAL TYPE I VALUE '1',
    END OF ERRORITAB.
End generated data section ***
AT SELECTION-SCREEN ON VALUE-REQUEST FOR DATASET.
CALL FUNCTION 'TMP_GUI_FILE_OPEN_DIALOG'
EXPORTING
    WINDOW_TITLE            = 'select a file '
    DEFAULT_EXTENSION       = 'TXT'
    DEFAULT_FILENAME        = 'ASSIGN5.TXT'
FILE_FILTER             =
INIT_DIRECTORY          =
MULTISELECTION          =
IMPORTING
RC                      =
    TABLES
      FILE_TABLE              = ITAB
EXCEPTIONS
   CNTL_ERROR              = 1
   OTHERS                  = 2
IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
READ TABLE ITAB INDEX 1.
DATASET = ITAB-FILENAME.
WRITE DATASET.
START-OF-SELECTION.
*perform open_dataset using dataset.
*perform open_group.
DATA T TYPE STRING.
T = DATASET.
IF T EQ ' '.
    MESSAGE E110(ZX).
ENDIF.
CALL FUNCTION 'GUI_UPLOAD'
    EXPORTING
      FILENAME                      = T
FILETYPE                      = 'ASC'
      HAS_FIELD_SEPARATOR           = 'X'
HEADER_LENGTH                 = 0
READ_BY_LINE                  = 'X'
DAT_MODE                      = ' '
CODEPAGE                      = ' '
IGNORE_CERR                   = ABAP_TRUE
REPLACEMENT                   = '#'
CHECK_BOM                     = ' '
IMPORTING
FILELENGTH                    =
HEADER                        =
    TABLES
      DATA_TAB                      = RECORD
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 ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
           WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
LOOP AT RECORD.
    CLEAR RC.
    CLEAR ERR.
*read dataset dataset into record.
    IF SY-SUBRC <> 0. EXIT. ENDIF.
    RECORD-KTOKK_002 = '0001'.
    PERFORM BDC_DYNPRO      USING 'SAPMF02K' '0100'.
    PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                                  'RF02K-KTOKK'.
    PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                                  '/00'.
    PERFORM BDC_FIELD       USING 'RF02K-LIFNR'
                                  RECORD-LIFNR_001.
    PERFORM BDC_FIELD       USING 'RF02K-KTOKK'
                                  RECORD-KTOKK_002.
    PERFORM BDC_DYNPRO      USING 'SAPMF02K' '0110'.
    PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                                  'LFA1-TELX1'.
    PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                                  '/00'.
    PERFORM BDC_FIELD       USING 'LFA1-ANRED'
                                  RECORD-ANRED_003.
    PERFORM BDC_FIELD       USING 'LFA1-NAME1'
                                  RECORD-NAME1_004.
    PERFORM BDC_FIELD       USING 'LFA1-SORTL'
                                  RECORD-SORTL_005.
    PERFORM BDC_FIELD       USING 'LFA1-STRAS'
                                  RECORD-STRAS_006.
    PERFORM BDC_FIELD       USING 'LFA1-PFACH'
                                  RECORD-PFACH_007.
    PERFORM BDC_FIELD       USING 'LFA1-ORT01'
                                  RECORD-ORT01_008.
    PERFORM BDC_FIELD       USING 'LFA1-ORT02'
                                  RECORD-ORT02_009.
    PERFORM BDC_FIELD       USING 'LFA1-LAND1'
                                  RECORD-LAND1_010.
    PERFORM BDC_FIELD       USING 'LFA1-REGIO'
                                  RECORD-REGIO_011.
    PERFORM BDC_FIELD       USING 'LFA1-SPRAS'
                                  RECORD-SPRAS_012.
    PERFORM BDC_FIELD       USING 'LFA1-TELF1'
                                  RECORD-TELF1_013.
    PERFORM BDC_FIELD       USING 'LFA1-TELF2'
                                  RECORD-TELF2_014.
    PERFORM BDC_DYNPRO      USING 'SAPMF02K' '0120'.
    PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                                  'LFA1-KUNNR'.
    PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                                  '=VW'.
    PERFORM BDC_DYNPRO      USING 'SAPMF02K' '0130'.
    PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                                  'LFBK-BANKN(01)'.
    PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                                  '=ENTR'.
    PERFORM BDC_FIELD       USING 'LFBK-BANKS(01)'
                                  RECORD-BANKS_01_015.
    PERFORM BDC_FIELD       USING 'LFBK-BANKL(01)'
                                  RECORD-BANKL_01_016.
    PERFORM BDC_FIELD       USING 'LFBK-BANKN(01)'
                                  RECORD-BANKN_01_017.
    PERFORM BDC_DYNPRO      USING 'SAPMF02K' '0130'.
    PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                                  'LFBK-BANKS(01)'.
    PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                                  '=UPDA'.
    PERFORM BDC_TRANSACTION USING 'XK01' CHANGING ERR RC.
    DATA: SERIAL TYPE I VALUE 1.
    IF RC <> 0.
      FAILCOUNT = FAILCOUNT + 1.
      CLEAR ERRORITAB.
      ERRORITAB-SERIAL = SERIAL.
      ERRORITAB-LIFNR_001 = RECORD-LIFNR_001.
      ERRORITAB-KTOKK_002 = RECORD-KTOKK_002.
      ERRORITAB-ANRED_003 = RECORD-ANRED_003.
      ERRORITAB-NAME1_004 = RECORD-NAME1_004.
      ERRORITAB-SORTL_005 = RECORD-SORTL_005.
      ERRORITAB-STRAS_006 = RECORD-STRAS_006.
      ERRORITAB-PFACH_007 = RECORD-PFACH_007.
      ERRORITAB-ORT01_008 = RECORD-ORT01_008.
      ERRORITAB-ORT02_009 = RECORD-ORT02_009.
      ERRORITAB-LAND1_010 = RECORD-LAND1_010.
      ERRORITAB-REGIO_011 = RECORD-REGIO_011.
      ERRORITAB-SPRAS_012 = RECORD-SPRAS_012.
      ERRORITAB-TELF1_013 = RECORD-TELF1_013.
      ERRORITAB-TELF2_014 = RECORD-TELF2_014.
      ERRORITAB-BANKS_01_015 = RECORD-BANKS_01_015.
      ERRORITAB-BANKL_01_016 = RECORD-BANKL_01_016.
      ERRORITAB-BANKN_01_017 = RECORD-BANKN_01_017.
      ERRORITAB-ERRORMSG = ERR.
      SERIAL = SERIAL + 1.
      APPEND ERRORITAB.
      MODIFY RECORD TRANSPORTING KTOKK_002.
      DELETE RECORD WHERE KTOKK_002 = '0001'.
    ELSE.
      SUCCESSCNT = SUCCESSCNT + 1.
    ENDIF.
ENDLOOP.
display output********************************************************
SKIP.
FORMAT COLOR 5 INTENSIFIED OFF.
WRITE:/ 'No. of records successfully uploaded: '.
FORMAT COLOR 4 INTENSIFIED OFF.
WRITE: SUCCESSCNT.
Displaying the success table******************************************
IF SUCCESSCNT <> 0.
    SKIP.
    FORMAT COLOR 4 INTENSIFIED OFF.
    WRITE:/ 'Successful Records'.
    FORMAT COLOR 7 INTENSIFIED ON.
    WRITE:/(261) SY-ULINE,
          / SY-VLINE,
            'S.NO',                               007 SY-VLINE,
            'VENDOR ACC.NUM',                     023 SY-VLINE,
            'VENDOR ACC GROUP',                   041 SY-VLINE,
            'TITLE',                              048 SY-VLINE,
            'VENDOR NAME',                        064 SY-VLINE,
            'SORT FIELD',                         076 SY-VLINE,
            'HOUSE NO.& STREET',                  101 SY-VLINE,
            'PO.BOX NO',                          116 SY-VLINE,
            'CITY',                               129 SY-VLINE,
            'DISTRICT',                           141 SY-VLINE,
            'COUNTRY KEY',                        156 SY-VLINE,
            'REGION',                             166 SY-VLINE,
            'LANGUAGE KEY',                       180 SY-VLINE,
            'TELEPHONE NO 1',                     196 SY-VLINE,
            'TELEPHONE NO 2',                     213 SY-VLINE,
            'BANK COUNTRY KEY',                   231 SY-VLINE,
            'BANK KEY',                           241 SY-VLINE,
            'BANK ACC.NO',                        261 SY-VLINE,
            /1(261) SY-ULINE.
    FORMAT COLOR 4 INTENSIFIED ON.
    SERIAL = 1.
   SORT RECORD BY LIFNR_001.
    LOOP AT RECORD.
      WRITE:/ SY-VLINE,
      SERIAL LEFT-JUSTIFIED,          007 SY-VLINE,
      RECORD-LIFNR_001(016),          023 SY-VLINE,
      RECORD-KTOKK_002(004),          041 SY-VLINE,
      RECORD-ANRED_003(015),          048 SY-VLINE,
      RECORD-NAME1_004(035),          064 SY-VLINE,
      RECORD-SORTL_005(010),          076 SY-VLINE,
      RECORD-STRAS_006(035),          101 SY-VLINE,
      RECORD-PFACH_007(010),          116 SY-VLINE,
      RECORD-ORT01_008(035),          129 SY-VLINE,
      RECORD-ORT02_009(035),          141 SY-VLINE,
      RECORD-LAND1_010(003),          156 SY-VLINE,
      RECORD-REGIO_011(003),          166 SY-VLINE,
      RECORD-SPRAS_012(002),          180 SY-VLINE,
      RECORD-TELF1_013(016),          196 SY-VLINE,
      RECORD-TELF2_014(016),          213 SY-VLINE,
      RECORD-BANKS_01_015(003),       231 SY-VLINE,
      RECORD-BANKL_01_016(015),       241 SY-VLINE,
      RECORD-BANKN_01_017(018),       261 SY-VLINE.
      WRITE:/(261) SY-ULINE.
      SERIAL = SERIAL + 1.
    ENDLOOP.
    WRITE:/1(261) SY-ULINE.
ENDIF.
SKIP.
FORMAT COLOR 5 INTENSIFIED OFF.
WRITE:/ 'No. of records not uploaded: '.
FORMAT COLOR 4 INTENSIFIED OFF.
WRITE: FAILCOUNT.
*Displaying the error table
IF FAILCOUNT <> 0.
    SKIP.
    FORMAT COLOR 4 INTENSIFIED OFF.
    WRITE:/(320) SY-ULINE,
            'Error Records'.
    FORMAT COLOR 7 INTENSIFIED ON.
    WRITE:/ SY-ULINE, SY-VLINE,
            'S.NO',                               007 SY-VLINE,
            'VENDOR ACC.NUM',                     023 SY-VLINE,
            'VENDOR ACC GROUP',                   041 SY-VLINE,
            'TITLE',                              048 SY-VLINE,
            'VENDOR NAME',                        064 SY-VLINE,
            'SORT FIELD',                         076 SY-VLINE,
            'HOUSE NO.& STREET',                  101 SY-VLINE,
            'PO.BOX NO',                          116 SY-VLINE,
            'CITY',                               129 SY-VLINE,
            'DISTRICT',                           141 SY-VLINE,
            'COUNTRY KEY',                        156 SY-VLINE,
            'REGION',                             166 SY-VLINE,
            'LANGUAGE KEY',                       180 SY-VLINE,
            'TELEPHONE NO 1',                     196 SY-VLINE,
            'TELEPHONE NO 2',                     213 SY-VLINE,
            'BANK COUNTRY KEY',                   231 SY-VLINE,
            'BANK KEY',                           241 SY-VLINE,
            'BANK ACC.NO',                        261 SY-VLINE,
            'ERROR MESSAGE',                      320 SY-VLINE.
    WRITE:/(320) SY-ULINE.
    FORMAT COLOR 4 INTENSIFIED ON.
   SORT ERRORITAB BY LIFNR_001.
    LOOP AT ERRORITAB.
      WRITE:/ SY-VLINE,
            ERRORITAB-SERIAL LEFT-JUSTIFIED,          007 SY-VLINE,
            ERRORITAB-LIFNR_001 ,       023 SY-VLINE,
            ERRORITAB-KTOKK_002,       041 SY-VLINE,
            ERRORITAB-ANRED_003,       048 SY-VLINE,
            ERRORITAB-NAME1_004,       064 SY-VLINE,
            ERRORITAB-SORTL_005,       076 SY-VLINE,
            ERRORITAB-STRAS_006,       101 SY-VLINE,
            ERRORITAB-PFACH_007,       116 SY-VLINE,
            ERRORITAB-ORT01_008,       129 SY-VLINE,
            ERRORITAB-ORT02_009,       141 SY-VLINE,
            ERRORITAB-LAND1_010,       156 SY-VLINE,
            ERRORITAB-REGIO_011,       166 SY-VLINE,
            ERRORITAB-SPRAS_012,       180 SY-VLINE,
            ERRORITAB-TELF1_013,       196 SY-VLINE,
            ERRORITAB-TELF2_014,       213 SY-VLINE,
            ERRORITAB-BANKS_01_015,    231 SY-VLINE,
            ERRORITAB-BANKL_01_016,    241 SY-VLINE,
            ERRORITAB-BANKN_01_017,    261 SY-VLINE,
            ERRORITAB-ERRORMSG,        320 SY-VLINE.
      WRITE:/(320) SY-ULINE.
    ENDLOOP.
    WRITE:/ SY-ULINE.
ENDIF.
hope this ll help you..
regards,
prema.A

Transferred records and added records

Similar Messages

Maybe you are looking for