DTP - Error Records

Hi All,
Request you to please assist me in handling the error stack.
Here is the scenario..
There were error records in the DTP...i have corrected the errors in the error stack.
Now, i need to know how to go about to post these error records.
Thanks
Hari

Hi
need to perform to handle data records with errors:
Failed status of DTP in DTP Process Monitor because of invalid character in records.
By clicking on Error Stack we can check error records.
Total of 3 records with error in source data.
     correcting erroneous records in Error Stack by clicking edit button on top left.
Creating Error DTP from the update tab of standard DTP.
Once Error DTP gets created, we can check the status of Standard DTP which is changed from create to display, and can also check the Error DTP under the Object for which we created the standard DTP.
Here is Error DTP:
     Schedule the Error DTP from Execute tab.
     In the Error DTP process monitor itu2019s showing 3 records that we corrected in Error Stack in earlier steps.
     We can also check the status of Standard DTP, itu2019s also Green now (without errors).
     You can also check the records updated status of Standard and Error DTP in the manage tab of data target.

Similar Messages

Error Record in report

Hello ,
I have a issue on Report that is Developed on a Multiprovider .
Problem : There is a report on multiprovider . Multiprovider consist of DSO and Infocube .
Before Changes : There is a error record in the CRM tables which is fetched by Infopackage . record was like "Number"
The quotes needs to be removed . Through DTP (FULL) data supplied to DSO .
After Changes : The Error records get corrected .Now till PSA record is fine .DTP is FULL to DSO .
But when i am reporting on that Multiprovider that error record is still there in the report and corrected record is also there .
Please help.
Thanks ,
Rahul

Hi Rahul,
Did you delete your earlier request (the one containing the error record) from the PSA before executing the DTP?
You can follow the below steps now to correct your data ->
1. Delete all data from DSO.
2. Check the PSA, delete all other requests except the latest one.
3. Load data from PSA to DSO by DTP.
Hope this helps!
Regards,
Saurabh

DTP Error when loading Master data from DSO to InfoProvider

Hi Experts,
My DTP is failing when I am running a DELTA load from DSO to the InfoProvider. The errors are either duplicate records or overlap of Dates etc.
Thanks,
SB.

Hi Gopal,
Here is the info on error message.
" There are duplicates of the data record 1 & with the key '00000000038 &' for characteristic EPROPERTY &. "
Hope this helps in understand the DTP error.
Thanks,
SB.

How do I clear or delete the DTP ERROR STACK..?

HI Experts
I have a number of records written to a DTP Error Stack for a Master Data load. Subsequent executions of the DTP result in further records being written to the stack if they have the same semantic key (even if they are not in error).
I know I can execute an Error DTP to clear the stack.
But is there any way to clear the stack rather than running the Error DTP? I don't want the records in error to be processed through to the InfoObject. I only want the subsequent records to go through, without going into the error stack.
tony

Hi Tony,
you have to remove the request from the target to delete the records from the error stack. If you don't want to reprocess them, try to avoid moving them to the error stack. One way is to skip the records without creating a monitor entry, so the system doesn't recognize the error and it's not shifted to the error stack, the other one is to delete the record from the source or result package throug a routine.
Single Record deletion iin the error-stack is not possible. For further information read this thread:
Delete & Automate deletion of Error Stack
Regards Michael
Edited by: Michael Seifert on Nov 20, 2008 4:04 PM

Non error records in error stack

Hi,
I have some error records collected in errorstack I know how to correct and update these error records.
But the problem is there are several other records collected in error stack giving the message filtered in advance as the key is same as error records.
Now my question is why is this happening?
regards,
preethi.

Hi Preethi,
This is happening because of the semantic key. The semantic key will be defined in the DTP.
If any records are having the same semantic key as the error records, these records will also be collected in the error stack with out actually checking data.
Regards,
Srinath.

Error Record with Same Key

Can anyone help me out with a master data load failure.
My request goes off red and the message looks somehow like "Record filtered in advance as error records with the same key exist", "Filter out new records with same key". I have already checked the duplicate handle record setting in DTP. Still why am i getting this error.
Would appreciate if some one could suggest me in this.

Hello Shridevi M ,
When I execute my DTP, I get a master data load failure : "Record filtered in advance as error records with the same key exist" . It's the same as you get. Please tell me how did you solved this probelm?
Thanks in advance,
Abdellatif

REG: Correcting error records which have invalid characters

Hi All,
I had couple of questions regarding DTP.
DTP loads are failing because of the invalid characters, we are correcting the error records from the error stack and then running the Error DTP to process further. now my question is the original DTP is still red, with correct records in the RSMO showing red. Please let me know how to make the red request in to green and maintain the data integrity.
Thanks in advance.

I have corrected the Error stack and updated the corrected records through the Error DTP.
I checked the Number of records which have come to the Table, it is showing correct number of records( i.e error stack data + correct records which loaded in the first shot) but the technical status is still red, so i am curious if i am change the overall status to green manually will that affect the data in any manner?

Edit the error records in error stack

Hi,
I want to edit the error records in error stack. There are around 300 records in error stack . I want to replace the value in one field with blank to correct the records. Can you please help me how to replace the value with blank.
Thanks,
Priya

Hi,
Open the original DTP and click on change.
1) In Update you will find "create error DTP", just click on it system automatically create error DTP for you original DTP.
2) Do not change any thing, just come back to your original DTP and activate your DTP again.
Now come back and refresh the info provider tree.
now execute your DTP, request will be green in target and you will error records in error stack.
How to edit the error records in error DTP
please find the doc.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b0406328-29c7-2e10-5db5-afe9b5695eeb?overridelayout=t…
Thanks,
Phani.

Query on DTP error

Hi BW Experts,
I am loading data to master data infoobject from ECC 6.0.The data has come to psa correctly.While running the DTP to move the data from PSA to MASTER DATA INFOOBJECT(ZZEMPLOYEE) some records are showing error.
The error is Data record 2 ('00050008):version(HYD) is not valid.
The above error comes for another 10 records.
what i have to do now? Could you please someone help me out?
Thanks

Hi Vishwaanand,
Datatypes are same for both (ECC 6.0 Field : Infoobject in BI 7.0)that is CHAR
In this scenario 10 fields are enhanced to 0EMPLOYEE_ATTR in ECC 6.0. Out of these 10 fields 2 fields are coming from one table(T500P-NAME1(Transfer from Circle) and 2 fields are coming from table(T001P-BTEXT(Transfer from Location) and 2 fields are coming from table(PA0000-BEGDA),   2 fields are coming from (PA0023-ARBGB,Difference between BEGDA and ENDDA) etc.
I have checked the datatype for those fields in ECC 6.0 and created corresponding infoobject prefix with Z. I have mapped these infoobjects with(YEMPLOYEE( Target : Master data infoobject) to 0EMPLOYEE_ATTR)).
Dataflow is in 7.0 like 0EMPLOYEE_ATTR(3.X)->INFOSOURCE--->YEMPLOYEE.
I have replicated and run the infopackage then i got the data till PSA(362) Correctly.
While runnig DTP Out of 362 Error records are 29. Showing the message as
YTRTOLOC(Transfer to location) : Datarecord 6 ("00050008") : Version 'chennai' is not valid
YTRTOCIR(Transfer to Circle)   : Datarecord 6 ("00050008") : Version 'Corporate' is not valid
YTRFRLOC(Transfer from Location):Datarecord 6 ("00050008") : Version 'Chennai' is not valid
YTRFRCIR(Transfer from Circle)       :Datarecord 6 ("00050008") : Version 'Corporate' is not valid etc
How will i correct those records?
Could you please help me out?

What does this DTP error indicate?

I am trying to correct this error in DTP:
"Error in formula function (routine 63), record 37816"
"Records filtered becasue records with same key contain errors"
This is a data error but not some bad or invalid characters. I am not sure how it can be corrected based on above message
Has anyone come across such an error - how was it resolved?
Thanks!
Edited by: BI Quest on Aug 30, 2008 9:20 AM

Hi,
This issue can be resolved by correcting the error records in PSA and updating it into the target. For that the first step should be to identify if all the records are there in PSA. You can find out this from checking the Details tab in RSMO, Job log , PSA > sorting records based on status,etc. Once its confirmed force the request to red and delete the particular request from the target cube. Then go to PSA and edit the incorrect records (correcting or blanking out the invalid entries for particular field InfoObject for the incorrect record) and save it. Once all the incorrect records are edited go to RSA1>PSA find the particular request and update to target manually (right click on PSA request > Start update immediately).
I will add the step by step procedure to edit PSA data and update into target (request based).
Identifying incorrect records.
System wont show all the incorrect records at the first time itself. You need to search the PSA table manually to find all the incorrect records.
1. First see RSMO > Details > Expand upate rules / processing tabs and you will find some of the error records.
2. Then you can go to PSA and filter using the status of records. Filter all the red requests. This may also wont show the entire incorrect records.
3. Then you can go to PSA and filter using the incorrect records based on the particular field.
4. If this also doesnt work out go to PSA and sort (not filter) the records based on the particular field with incorrect values and it will show all the records. Note down the record numbers and then edit them one by one.
If you want to confirm find the PSA table and search manually."
Also Run the report RS_ERRORLOG_EXAMPLE,By this report you can display all incorrected records of the data & you can also find whether the error occured in PSA or in TRANSFER RULES.
Steps to resolve this
1. Force the request to red in RSMO > Status tab.
2. Delete the request from target.
3. Come to RSMO > top right you can see PSA maintenace button > click and go to PSA .
4.Edit the record
5. Save PSA data.
6. Got to RSA15 > Search by request name > Right click > update the request from PSA to target.
Refer how to Modify PSA Data
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40890eda-1b99-2a10-2d8b-a18b9108fc38
This should solve your problem for now.
As a long term fix you can apply some user exit in source system side or change your update rules to ensure that this field is getting blanked out before getting loaded in cube or add that particular char to permitted character list in BW.
Also in Tcode RSKC --> type ALL_CAPITAL --> F8 (Execute)
OR
Go to SE38 and execute the program RSKC_ALLOWED_CHAR_MAINTAIN and give ALL_CAPITAL or the char you want to add.
Check the table RSALLOWEDCHAR. It should contain ALL_CAPITAL or the char you have entered.
In RSKC you can add upto 45 characters
if you add any character in RSKC it will autometically update into RSALLOWEDCHAR table, But in this table you can add upto 72 characters,using ABAP program..
Refer
Invalid characters in SAP BW 3.x: Myths and Reality. Part 2.
Invalid characters in SAP BW 3.x: Myths and Reality. Part 1.
Steps of Including one special characters into permitted ones in BI
http://help.sap.com/saphelp_nw04/helpdata/en/64/e90da7a60f11d2a97100a0c9449261/frameset.htm
For adding Other characters
OSS note #173241 u2013 u201CAllowed characters in the BW Systemu201D
Sample cleansing routine (#)
Help loading char EQUIP#1111#TAG#3311 SN#A01040 * into Cube
Invalid character error while activating DSO - Please help
Regarding Special Characters
how to prevent bad charectors from source system
Regards
Tg

Record filtered in advance as error records with the same key exist

Dear Masters
I am getting below error for master data (0MATERIAL_ATTR), while loading data from PSA to Info object through DTP (I have set the Handle duliocate record also). When I checked that error data in Error Stack, I am getting below error for all records(100)
"Record filtered in advance as error records with the same key exist"
Could u please help me to resolve this issue
Thanks in Advance
Raja

Hi
Thanks for reply
I have loaded the Delta data in PSA. In PSA data was loaded successfully. I got the failure only when I loaded the from PSA to Maste data
Thanks in advance
Raja

To find Error records

While loading data I got an error message "Conversion of dimensionless units is not possible"
Can anyone suggest how to identify the error records for which conversion is not possible.

Hi,
Are you using function module for unit conversion in transformation routine....T006D is the table for dimensions..If dim ID is not maintained for units..system will throw an error'"Conversion of dimensionless units is not possible".
Try creating error DTP to identify incorrect records..

Dtp error when loading data from one cube to another cube?

hi,experts
it seems strange that when I tick the some characteristics as navigational attributes in the cube , the error occurs during the execution of the DTP:error while updating to target Z* (Cube name ).
once i turn the flag off , no error appear. could anyone give me a clue ?
thanks in advance!

Hi,
When u make changes in the cube u need to make necessary changes in Transformation and activate the DTP.The checking of Navigational attributes in cube will appear in u r transformation as new fields where u need to create a mapping for them and then activate, also activate your DTP and then load the data. This should resolve your issue.
Regards

Issue regarding bdc for capturing error records

Hi All,
        My requirement is to capture the error record and download the error record to a flat file .
I have done recording for MM01 transaction .
I am getting a problem like no error records are downloaded into the flat file .It is downloading only the empty records.
Pls see the below code which i developed & modify it for any changes .Its an urgent .Pls provide me the solution ASAP.
My Flat file
M     FERT     X     MATL105     KG
X     FERT     X     MATL106     KG
In the above flat file 'X' is an Industry sector which doesnot exists which is an error record that has to be captured and download it into the flat file .
Source code :
report Z_MM01_MSG_F MESSAGE-ID MSG1
       no standard page heading line-size 255.
include bdcrecx1.
parameters: dataset(132) lower case.
***    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: MBRSH
        MBRSH_001(001),
* data element: MTART
        MTART_002(004),
* data element: XFELD
        KZSEL_01_003(001),
* data element: MAKTX
        MAKTX_004(040),
* data element: MEINS
        MEINS_005(003),
* data element: MTPOS_MARA
        MTPOS_MARA_006(004),
      end of record.
*DECLARATION OF BDCDATA STRUCTURE
DATA: IT_BDCDATA LIKE BDCDATA OCCURS 0 WITH HEADER LINE .
*declaration to store the message
DATA: IT_MESSTAB LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE .
*DECLARATION TO STORE THE MESSAGE
DATA: BEGIN OF IT_STORE_MSG OCCURS 0,
      STORE(1000),
      END OF IT_STORE_MSG.
*declaration SUCCESS MESG
DATA: BEGIN OF IT_SUCCESS OCCURS 0,
      SUCCESS_REC(10),
      MBRSH(10),
      TABIX LIKE SY-TABIX,
      END OF IT_SUCCESS.
*declaration ERROR MESSAGE
DATA: BEGIN OF IT_ERROR OCCURS 0,
      ERROR_REC(10),
      MBRSH(10),
         TABIX LIKE SY-TABIX,
      END OF IT_ERROR.
DATA:TABIX LIKE SY-TABIX.
*validating Material type(mtart) field data with table T134
data : v_type like T134-mtart.
DATA: V_INDSECT LIKE MARA-MBRSH.
*** End generated data section ***
start-of-selection.
CALL FUNCTION 'UPLOAD'
* EXPORTING
*   CODEPAGE                      = ' '
*   FILENAME                      = ' '
*   FILETYPE                      = ' '
*   ITEM                          = ' '
*   FILEMASK_MASK                 = ' '
*   FILEMASK_TEXT                 = ' '
*   FILETYPE_NO_CHANGE            = ' '
*   FILEMASK_ALL                  = ' '
*   FILETYPE_NO_SHOW              = ' '
*   LINE_EXIT                     = ' '
*   USER_FORM                     = ' '
*   USER_PROG                     = ' '
*   SILENT                        = 'S'
* IMPORTING
*   FILESIZE                      =
*   CANCEL                        =
*   ACT_FILENAME                  =
*   ACT_FILETYPE                  =
TABLES
    data_tab                      = record
* EXCEPTIONS
*   CONVERSION_ERROR              = 1
*   INVALID_TABLE_WIDTH           = 2
*   INVALID_TYPE                  = 3
*   NO_BATCH                      = 4
*   UNKNOWN_ERROR                 = 5
*   GUI_REFUSE_FILETRANSFER       = 6
*   OTHERS                        = 7
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
*perform open_dataset using dataset.
perform open_group.
LOOP AT RECORD.
perform bdc_dynpro      using 'SAPLMGMM' '0060'.
perform bdc_field       using 'BDC_CURSOR'
                              'RMMG1-MATNR'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
*- Validating industry sector(MBRSH) from the master table(MARA)
select single MBRSH from T137 into V_INDSECT where MBRSH eq
record-MBRSH_001.
IF SY-SUBRC EQ 0.
perform bdc_field       using 'RMMG1-MBRSH'
                              record-MBRSH_001.
*endif.
perform bdc_field       using 'RMMG1-MTART'
                              record-MTART_002.
perform bdc_dynpro      using 'SAPLMGMM' '0070'.
perform bdc_field       using 'BDC_CURSOR'
                              'MSICHTAUSW-DYTXT(01)'.
perform bdc_field       using 'BDC_OKCODE'
                              '=ENTR'.
perform bdc_field       using 'MSICHTAUSW-KZSEL(01)'
                              record-KZSEL_01_003.
perform bdc_dynpro      using 'SAPLMGMM' '4004'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'MAKT-MAKTX'
                              record-MAKTX_004.
perform bdc_field       using 'BDC_CURSOR'
                              'MARA-MEINS'.
perform bdc_field       using 'MARA-MEINS'
                              record-MEINS_005.
perform bdc_field       using 'MARA-MTPOS_MARA'
                              record-MTPOS_MARA_006.
perform bdc_dynpro      using 'SAPLSPO1' '0300'.
perform bdc_field       using 'BDC_OKCODE'
                              '=YES'.
perform bdc_transaction using 'MM01'.
*ELSE.
*message E000 WITH 'Industry sector does not Exist' .
*endif.
LOOP AT MESSTAB.
CALL FUNCTION 'FORMAT_MESSAGE'
EXPORTING
   ID              = MESSTAB-MSGID
   LANG            = MESSTAB-MSGSPRA
   NO              = MESSTAB-MSGNR
   V1              = MESSTAB-MSGV1
   V2              = MESSTAB-MSGV2
*   V3              = SY-MSGV3
*   V4              = SY-MSGV4
IMPORTING
   MSG             = IT_STORE_MSG-STORE
   EXCEPTIONS
*   NOT_FOUND       = 1
   OTHERS          = 0.
IF MESSTAB-MSGTYP = 'S'.
   IT_SUCCESS-SUCCESS_REC = IT_STORE_MSG-STORE.
   IT_SUCCESS-MBRSH = record-MBRSH_001.
   IT_SUCCESS-TABIX = TABIX.
   APPEND IT_SUCCESS.
   ELSEIF MESSTAB-MSGTYP = 'E'.
   IT_ERROR-ERROR_REC = IT_STORE_MSG-STORE.
   IT_ERROR-MBRSH = record-MBRSH_001.
   IT_ERROR-TABIX = TABIX.
APPEND IT_ERROR.
ENDIF.
endloop.
endif.
ENDLOOP.
CALL FUNCTION 'DOWNLOAD'
TABLES
    DATA_TAB                      = IT_error
*   FIELDNAMES                    =
* EXCEPTIONS
*   INVALID_FILESIZE              = 1
*   INVALID_TABLE_WIDTH           = 2
*   INVALID_TYPE                  = 3
*   NO_BATCH                      = 4
*   UNKNOWN_ERROR                 = 5
*   GUI_REFUSE_FILETRANSFER       = 6
*   OTHERS                        = 7
IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
perform close_group.
*perform close_dataset using dataset.
Code Formatted by: Alvaro Tejada Galindo on Apr 9, 2008 5:05 PM

Hi,
DATA: IT_MESSTAB LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE .
CALL FUNCTION 'DOWNLOAD'
TABLES
DATA_TAB = IT_error
FIELDNAMES =
EXCEPTIONS
INVALID_FILESIZE = 1
INVALID_TABLE_WIDTH = 2
INVALID_TYPE = 3
NO_BATCH = 4
UNKNOWN_ERROR = 5
GUI_REFUSE_FILETRANSFER = 6
OTHERS = 7.
IF SY-SUBRC 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
instead of using IT_error ion tables use IT_MESSTAB.
<REMOVED BY MODERATOR>
Code Formatted by: Alvaro Tejada Galindo on Apr 9, 2008 5:07 PM

Hi All,Issue regarding bdc for capturing error records,its urgent

Hi All,
        My requirement is to capture the error record and download the error record to a flat file .
I have done recording for MM01 transaction .
I am getting a problem like no error records are downloaded into the flat file .It is downloading only the empty records.
Pls see the below code which i developed & modify it for any changes .Its an urgent .Pls provide me the solution ASAP.
My Flat file
M     FERT     X     MATL105     KG
X     FERT     X     MATL106     KG
In the above flat file 'X' is an Industry sector which doesnot exists which is an error record that has to be captured and download it into the flat file .
Source code :
report Z_MM01_MSG_F MESSAGE-ID MSG1
       no standard page heading line-size 255.
include bdcrecx1.
parameters: dataset(132) lower case.
   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: MBRSH
        MBRSH_001(001),
data element: MTART
        MTART_002(004),
data element: XFELD
        KZSEL_01_003(001),
data element: MAKTX
        MAKTX_004(040),
data element: MEINS
        MEINS_005(003),
data element: MTPOS_MARA
        MTPOS_MARA_006(004),
      end of record.
*DECLARATION OF BDCDATA STRUCTURE
DATA: IT_BDCDATA LIKE BDCDATA OCCURS 0 WITH HEADER LINE .
*declaration to store the message
DATA: IT_MESSTAB LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE .
*DECLARATION TO STORE THE MESSAGE
DATA: BEGIN OF IT_STORE_MSG OCCURS 0,
      STORE(1000),
      END OF IT_STORE_MSG.
*declaration SUCCESS MESG
DATA: BEGIN OF IT_SUCCESS OCCURS 0,
      SUCCESS_REC(10),
      MBRSH(10),
      TABIX LIKE SY-TABIX,
      END OF IT_SUCCESS.
*declaration ERROR MESSAGE
DATA: BEGIN OF IT_ERROR OCCURS 0,
      ERROR_REC(10),
      MBRSH(10),
         TABIX LIKE SY-TABIX,
      END OF IT_ERROR.
DATA:TABIX LIKE SY-TABIX.
*validating Material type(mtart) field data with table T134
data : v_type like T134-mtart.
DATA: V_INDSECT LIKE MARA-MBRSH.
End generated data section ***
start-of-selection.
CALL FUNCTION 'UPLOAD'
EXPORTING
CODEPAGE                      = ' '
FILENAME                      = ' '
FILETYPE                      = ' '
ITEM                          = ' '
FILEMASK_MASK                 = ' '
FILEMASK_TEXT                 = ' '
FILETYPE_NO_CHANGE            = ' '
FILEMASK_ALL                  = ' '
FILETYPE_NO_SHOW              = ' '
LINE_EXIT                     = ' '
USER_FORM                     = ' '
USER_PROG                     = ' '
SILENT                        = 'S'
IMPORTING
FILESIZE                      =
CANCEL                        =
ACT_FILENAME                  =
ACT_FILETYPE                  =
TABLES
    data_tab                      = record
EXCEPTIONS
CONVERSION_ERROR              = 1
INVALID_TABLE_WIDTH           = 2
INVALID_TYPE                  = 3
NO_BATCH                      = 4
UNKNOWN_ERROR                 = 5
GUI_REFUSE_FILETRANSFER       = 6
OTHERS                        = 7
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
*perform open_dataset using dataset.
perform open_group.
LOOP AT RECORD.
perform bdc_dynpro      using 'SAPLMGMM' '0060'.
perform bdc_field       using 'BDC_CURSOR'
                              'RMMG1-MATNR'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
*- Validating industry sector(MBRSH) from the master table(MARA)
select single MBRSH from T137 into V_INDSECT where MBRSH eq
record-MBRSH_001.
IF SY-SUBRC EQ 0.
perform bdc_field       using 'RMMG1-MBRSH'
                              record-MBRSH_001.
*endif.
perform bdc_field       using 'RMMG1-MTART'
                              record-MTART_002.
perform bdc_dynpro      using 'SAPLMGMM' '0070'.
perform bdc_field       using 'BDC_CURSOR'
                              'MSICHTAUSW-DYTXT(01)'.
perform bdc_field       using 'BDC_OKCODE'
                              '=ENTR'.
perform bdc_field       using 'MSICHTAUSW-KZSEL(01)'
                              record-KZSEL_01_003.
perform bdc_dynpro      using 'SAPLMGMM' '4004'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'MAKT-MAKTX'
                              record-MAKTX_004.
perform bdc_field       using 'BDC_CURSOR'
                              'MARA-MEINS'.
perform bdc_field       using 'MARA-MEINS'
                              record-MEINS_005.
perform bdc_field       using 'MARA-MTPOS_MARA'
                              record-MTPOS_MARA_006.
perform bdc_dynpro      using 'SAPLSPO1' '0300'.
perform bdc_field       using 'BDC_OKCODE'
                              '=YES'.
perform bdc_transaction using 'MM01'.
*ELSE.
*message E000 WITH 'Industry sector does not Exist' .
*endif.
LOOP AT MESSTAB.
CALL FUNCTION 'FORMAT_MESSAGE'
EXPORTING
   ID              = MESSTAB-MSGID
   LANG            = MESSTAB-MSGSPRA
   NO              = MESSTAB-MSGNR
   V1              = MESSTAB-MSGV1
   V2              = MESSTAB-MSGV2
V3              = SY-MSGV3
V4              = SY-MSGV4
IMPORTING
   MSG             = IT_STORE_MSG-STORE
   EXCEPTIONS
NOT_FOUND       = 1
   OTHERS          = 0.
IF MESSTAB-MSGTYP = 'S'.
   IT_SUCCESS-SUCCESS_REC = IT_STORE_MSG-STORE.
   IT_SUCCESS-MBRSH = record-MBRSH_001.
   IT_SUCCESS-TABIX = TABIX.
   APPEND IT_SUCCESS.
   ELSEIF MESSTAB-MSGTYP = 'E'.
   IT_ERROR-ERROR_REC = IT_STORE_MSG-STORE.
   IT_ERROR-MBRSH = record-MBRSH_001.
   IT_ERROR-TABIX = TABIX.
APPEND IT_ERROR.
ENDIF.
endloop.
endif.
ENDLOOP.
CALL FUNCTION 'DOWNLOAD'
TABLES
    DATA_TAB                      = IT_error
FIELDNAMES                    =
EXCEPTIONS
INVALID_FILESIZE              = 1
INVALID_TABLE_WIDTH           = 2
INVALID_TYPE                  = 3
NO_BATCH                      = 4
UNKNOWN_ERROR                 = 5
GUI_REFUSE_FILETRANSFER       = 6
OTHERS                        = 7
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
perform close_group.
*perform close_dataset using dataset.

Hi,
DATA: IT_MESSTAB LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE .
CALL FUNCTION 'DOWNLOAD'
TABLES
DATA_TAB = IT_error
FIELDNAMES =
EXCEPTIONS
INVALID_FILESIZE = 1
INVALID_TABLE_WIDTH = 2
INVALID_TYPE = 3
NO_BATCH = 4
UNKNOWN_ERROR = 5
GUI_REFUSE_FILETRANSFER = 6
OTHERS = 7.
IF SY-SUBRC 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
instead of using IT_error ion tables use IT_MESSTAB.
<REMOVED BY MODERATOR>
Code Formatted by: Alvaro Tejada Galindo on Apr 9, 2008 5:07 PM

DTP - Error Records

Similar Messages

Maybe you are looking for