BDC error log

Dear Experts,
In BDC session method i have uploaded 2000 records from excel sheet to the transation pp02. But i got the message that 46 records are found error.
How to find the error records which are not uploaded in the transaction pp02.
regards
chinnaiya P

Hi,
If you are using 'Call Transaction' approach all your errors are in BDCMSGCOLL( Recall that all your error message texts are saved in T100 table)
Srini..

Similar Messages

Bdc - error logs

Hello friends........can any one help me....how 2 find out the errors occured during batch input method , call transaction method and direct input method.
for example..when uploading 100 records of data.... the error occured in the 60 th record...whr the error will be stored? ....what happens to the process?........n how to rectify it?
Regds,
Ariff

Try this code for error log in bdc it will get u all errors while loading a file . But the problem is if its a flat file thn u should validate it while downloading it to the SAP system. I mean validating the entries in the internal table before you actually call the transaction.That is effective for performance.
To get the SAP generated messages which are generated while the transaction here's the code.
DATA:   MESSTAB LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
LOOP AT MESSTAB.
SELECT SINGLE * FROM T100 WHERE SPRSL = MESSTAB-MSGSPRA
                           AND   ARBGB = MESSTAB-MSGID
                           AND   MSGNR = MESSTAB-MSGNR.
      IF SY-SUBRC = 0.
        L_MSTRING = T100-TEXT.
        IF L_MSTRING CS '&1'.
          REPLACE '&1' WITH MESSTAB-MSGV1 INTO L_MSTRING.
          REPLACE '&2' WITH MESSTAB-MSGV2 INTO L_MSTRING.
          REPLACE '&3' WITH MESSTAB-MSGV3 INTO L_MSTRING.
          REPLACE '&4' WITH MESSTAB-MSGV4 INTO L_MSTRING.
        ELSE.
          REPLACE '&' WITH MESSTAB-MSGV1 INTO L_MSTRING.
          REPLACE '&' WITH MESSTAB-MSGV2 INTO L_MSTRING.
          REPLACE '&' WITH MESSTAB-MSGV3 INTO L_MSTRING.
          REPLACE '&' WITH MESSTAB-MSGV4 INTO L_MSTRING.
        ENDIF.
        CONDENSE L_MSTRING.
        GV_MSG = L_MSTRING.
        IF T100-ARBGB NE 'M3' AND
             T100-MSGNR NE '800'.
      ELSE.
      ENDIF.
    ENDLOOP.
    REFRESH MESSTAB.

BDC Error Log return

Hi All,
A session is run using the RSBDCSUB.
I wld like to display as how many entries from my flat file have failed. i.e Those entries with errors.
Is there any FM or any standard program which wil return the No. of entries that have failed?
Thanks in Advance,
Rahul

look table APQI fields TRANSCNT and TRANSCNTE

When does a error log is creaded during BDC recording

hi,
i am working on Reports, i need to know how the BDC recording works, and when the error log log be created

Hi anitha,
You have got a message generated from message class "RQ" with message number "XXX".
Are you getting this error during recording. Which transaction you are using for recording.
The error messages will be generated when you documented is not proceesed completly via BDC. You can collect the error messages in to an internal table and print at the end of the program as a report.
If you are using Call Traansaction
*------ Declaring Internal Table to Store BDC Errors *----
DATA: BEGIN OF T_MESSTAB OCCURS 0.
        INCLUDE STRUCTURE BDCMSGCOLL.
DATA: END OF T_MESSTAB.
CALL TRANSACTION 'TCODE' USING BDC_TAB MODE 'A'
                       MESSAGES INTO T_MESSTAB.
LOOP AT T_MESSTAB.
        WRITE / TEXT-001.
        WRITE:/10 T_MESSTAB-DYNAME, 30 T_MESSTAB-DYNUMB.
        WRITE:/10 T_MESSTAB-MSGV1.
ENDLOOP.
Lanka

Regarding capturing VF01 ERROR logs in a background job

Hi ,
We are running a background job that calls transaction VF01 via BDC .
CALL TRANSACTION 'VF01' USING   bdcdata
                          MODE    S
                          UPDATE N
                          MESSAGES INTO gt_messtab.
In some cases billing documents will not be generated. In such cases systems will throw message "Check the log "
After which we can check the error messages via Menu Edit>logs.
This error messages (stored in XVBFS internal table) need to captured in the job log i.e custom programme.
Unfortunately i could not found any user exits/BADIs that can help me in capturing message.
Can you please help me how can i solve this issue?
Thanks in advance
Manoj
Edited by: Manoj J on Nov 16, 2011 9:42 AM
Moderator message : Duplicate post locked, continue with original thread [How to capture error logs of VF01 in a background job log   |Re: How to capture error logs of VF01 in a background job log].
Edited by: Vinod Kumar on Nov 16, 2011 3:34 PM

Hi Manoj,
I had a similar problem.
I solved it selecting from VBSK the last record of the user regarding elaboration of invoices, and then calling f.m. 'VBSK_ALV_DISPLAY'.
Otherwise you could call directly transaction "V.21"
Hope this could help you
Andrea

Any existing program to list before and after BDC error?

Looking for a way to report any BDC errors and show before and after its been corrected.

Hi,
Before making correction:-->
!. If you are using call transaction , then you can all errors in BDCMSGCOLL internal table
and use fm MESSAGE_PREPARE to generate message texts
2. If you are using session method then you have error log SM35.
After making coorection i don't think you have anyway to capture corrected errors
a®

ERROR LOG IN XLS

I Had run a BDC in session method through SM35.
I need to download the error log generated in XLS file or any other format. Is there any method in SM35 to get it download?

Hi sashi,
Goto SM35, Select your session-
Click Log or F7
Log overview is displayed. now select and double click current log.
Log will be displayed in table format.
now click the print button ot Ctrl+P
Log will be displayed in list format.
Now you can download it via System->List->Save
Hope it helps.
Regards,
Komal

Bdc error recovery

Hi,
plz any body tell me the best method of error recovery in bdc both in call transaction and bdc session, since data is in huge ammount and in excel sheet.
plz give me answer in full details, bcaz i am is in big trouble uploading around 40 lakh line of data in implementation project.
thanks and regards
vijay dwivedi

Hi Vijay,
The general practice is that you for such huge data, BDC session is the better option. When you create the session using the program, you can go to sm35 and process it at a later stage. Once the processing is done, an error log is created automatically with all the records that have failed. YOu can then analyse the reason for the error by running a few of those records in E mode(Error screen mode) correct the data and reprocess the error records.
Regards,
Ravi

BDC Error Session and Database update??

Hi all,
I am having Query about BDC Error Session. If I see the log of Error Session, then few Transactions are processed and few are in incorrect status.
Those transaction, which are processed, Does it mean that it has updates the database successfully or Error Session will never update the Database?
Thanks in advance.

Thanks for your reply
Message was edited by: Vipin Nagpal
Message was edited by: Vipin Nagpal

Reprocess the bdc error session

hi all
in bdc session method .i have a error log how. ican reprocess the error log

Go To Analyze Session in SM30 for your records processed with errors.
Compare with your text file to trace the records not processed.
Copy them to new text file. do the corrections and re-processed.
But be sure that you had kept the previous session, otherwise you are not able to trace the records.
Regds,
Anil

How do we print the error logs

hi friends , i want to print the error log file of a bdc session method ,can any one sugest me a answer

Check out this Sample Program
*& Report                                             *
*& This program is to transfer data from flat file to transaction 'FD01'
REPORT zgopi_report
NO STANDARD PAGE HEADING
                        LINE-SIZE 255
                        MESSAGE-ID ZRASH.
*                 Internal Table Declarations                          *
*--Internal Table for Data Uploading.
DATA : BEGIN OF IT_FFCUST OCCURS 0,
         KUNNR(10),
         BUKRS(4),
         KTOKD(4),
         ANRED(15),
         NAME1(35),
         SORTL(10),
         STRAS(35),
         ORT01(35),
         PSTLZ(10),
         LAND1(3),
         SPRAS(2),
         AKONT(10),
       END OF IT_FFCUST.
*--Internal Table to Store Error Records.
DATA : BEGIN OF IT_ERRCUST OCCURS 0,
         KUNNR(10),
         EMSG(255),
       END OF IT_ERRCUST.
*--Internal Table to Store Successful Records.
DATA : BEGIN OF IT_SUCCUST OCCURS 0,
         KUNNR(10),
         SMSG(255),
       END OF IT_SUCCUST.
*--Internal Table for Storing the BDC data.
DATA : IT_CUSTBDC LIKE BDCDATA OCCURS 0 WITH HEADER LINE.
*--Internal Table for storing the messages.
DATA : IT_CUSTMSG LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
DATA : V_FLAG1(1) VALUE ' ',
"Flag used for opening session.
       V_TLINES LIKE SY-TABIX,
       "For storing total records processed.
       V_ELINES LIKE SY-TABIX,
       "For storing the no of error records.
       V_SLINES LIKE SY-TABIX.
       "For storing the no of success records.
*          Selection screen                                            *
SELECTION-SCREEN BEGIN OF BLOCK B1.
PARAMETERS : V_FNAME LIKE RLGRAP-FILENAME,
             V_SESNAM LIKE RLGRAP-FILENAME.
SELECTION-SCREEN END OF BLOCK B1.
*          Start-of-selection                                          *
START-OF-SELECTION.
*-- Form to upload flatfile data into the internal table.
PERFORM FORM_UPLOADFF.
*        TOP-OF-PAGE                                                   *
TOP-OF-PAGE.
WRITE:/ 'Details of the error and success records for the transaction'
ULINE.
SKIP.
*          End of Selection                                            *
END-OF-SELECTION.
*-- Form to Generate a BDC from the Uploaded Internal table
PERFORM FORM_BDCGENERATE.
*--To write the totals and the session name.
PERFORM FORM_WRITEOP.
*&      Form form_uploadff
*     Form to upload flatfile data into the internal table.
FORM FORM_UPLOADFF .
*--Variable to change the type of the parameter file name.
DATA : LV_FILE TYPE STRING.
LV_FILE = V_FNAME.
*--Function to upload the flat file to the internal table.
CALL FUNCTION 'GUI_UPLOAD'
    EXPORTING
      FILENAME                      = LV_FILE
*     FILETYPE                      = 'ASC'
      HAS_FIELD_SEPARATOR           = 'X'
*     HEADER_LENGTH                 = 0
*     READ_BY_LINE                  = 'X'
*     DAT_MODE                      = ' '
*   IMPORTING
*     FILELENGTH                    =
*     HEADER                        =
    TABLES
      DATA_TAB                      = IT_FFCUST
    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.
*--Deleting the headings from the internal table.
    DELETE IT_FFCUST INDEX 1.
*--Getting the total number of records uploaded.
    DESCRIBE TABLE IT_FFCUST LINES V_TLINES.
ENDIF.
ENDFORM.                    " form_uploadff
*&      Form Form_bdcgenerate
*     Form to Generate a BDC from the Uploaded Internal table
FORM FORM_BDCGENERATE .
*--Generating the BDC table for the fields of the internal table.
LOOP AT IT_FFCUST.
    PERFORM POPULATEBDC USING :
                                'X' 'SAPMF02D' '0105',
                                ' ' 'BDC_OKCODE' '/00' ,
                                ' ' 'RF02D-KUNNR' IT_FFCUST-KUNNR,
                                ' ' 'RF02D-BUKRS' IT_FFCUST-BUKRS,
                                ' ' 'RF02D-KTOKD' IT_FFCUST-KTOKD,
                                'X' 'SAPMF02D' '0110' ,
                                ' ' 'BDC_OKCODE' '/00',
                                ' ' 'KNA1-ANRED' IT_FFCUST-ANRED,
                                ' ' 'KNA1-NAME1' IT_FFCUST-NAME1,
                                ' ' 'KNA1-SORTL' IT_FFCUST-SORTL,
                                ' ' 'KNA1-STRAS' IT_FFCUST-STRAS,
                                ' ' 'KNA1-ORT01' IT_FFCUST-ORT01,
                                ' ' 'KNA1-PSTLZ' IT_FFCUST-PSTLZ,
                                ' ' 'KNA1-LAND1' IT_FFCUST-LAND1,
                                ' ' 'KNA1-SPRAS' IT_FFCUST-SPRAS,
                                'X' 'SAPMFO2D' '0120',
                                ' ' 'BDC_OKCODE' '/00',
                                'X' 'SAPMF02D' '0125',
                                ' ' 'BDC_OKCODE' '/00',
                                'X' 'SAPMF02D' '0130',
                                ' ' 'BDC_OKCODE' '=ENTR',
                                'X' 'SAPMF02D' '0340',
                                ' ' 'BDC_OKCODE' '=ENTR',
                                'X' 'SAPMF02D' '0360',
                                ' ' 'BDC_OKCODE' '=ENTR',
                                'X' 'SAPMF02D' '0210',
                                ' ' 'KNB1-AKONT' IT_FFCUST-AKONT,
                                ' ' 'BDC_OKCODE' '/00',
                                'X' 'SAPMF02D' '0215',
                                ' ' 'BDC_OKCODE' '/00',
                                'X' 'SAPMF02D' '0220',
                                ' ' 'BDC_OKCODE' '/00',
                                'X' 'SAPMF02D' '0230',
                                ' ' 'BDC_OKCODE' '=UPDA'.
*--Calling the transaction 'fd01'.
    CALL TRANSACTION 'FD01' USING IT_CUSTBDC MODE 'N' UPDATE 'S'
    MESSAGES INTO IT_CUSTMSG.
    IF SY-SUBRC <> 0.
*--Populating the error records internal table.
      IT_ERRCUST-KUNNR = IT_FFCUST-KUNNR.
      APPEND IT_ERRCUST.
      CLEAR IT_ERRCUST.
*--Opening a session if there is an error record.
      IF V_FLAG1 = ' '.
        PERFORM FORM_OPENSESSION.
        V_FLAG1 = 'X'.
      ENDIF.
*--Inserting the error records into already open session.
      IF V_FLAG1 = 'X'.
        PERFORM FORM_INSERT.
      ENDIF.
*--Populating the Success records internal table.
    ELSE.
      IT_SUCCUST-KUNNR = IT_FFCUST-KUNNR.
      APPEND IT_SUCCUST.
      CLEAR IT_SUCCUST.
    ENDIF.
*--Displaying the messages.
    IF NOT IT_CUSTMSG[] IS INITIAL.
      PERFORM FORM_FORMATMSG.
    ENDIF.
*--Clearing the message and bdc tables.
    CLEAR : IT_CUSTBDC[],IT_CUSTMSG[].
ENDLOOP.
*--Getting the total no of error records.
DESCRIBE TABLE IT_ERRCUST LINES V_ELINES.
*--Getting the total no of successful records.
DESCRIBE TABLE IT_SUCCUST LINES V_SLINES.
*--Closing the session only if it is open.
IF V_FLAG1 = 'X'.
    PERFORM FORM_CLOSESESS.
ENDIF.
ENDFORM.                    " Form_bdcgenerate
*&      Form populatebdc
*       FOrm to Populate the BDC table.
FORM POPULATEBDC USING    VALUE(P_0178)
                           VALUE(P_0179)
                           VALUE(P_0180).
IF P_0178 = 'X'.
    IT_CUSTBDC-PROGRAM = P_0179.
    IT_CUSTBDC-DYNPRO = P_0180.
    IT_CUSTBDC-DYNBEGIN = 'X'.
ELSE.
    IT_CUSTBDC-FNAM = P_0179.
    IT_CUSTBDC-FVAL = P_0180.
ENDIF.
APPEND IT_CUSTBDC.
CLEAR IT_CUSTBDC.
ENDFORM.                    " populatebdc
*&      Form FORM_OPENSESSION
*       Form to Open a session.
FORM FORM_OPENSESSION .
*--Variable to convert the given session name into reqd type.
DATA : LV_SESNAM(12).
LV_SESNAM = V_SESNAM.
*--Opening a session.
CALL FUNCTION 'BDC_OPEN_GROUP'
   EXPORTING
     CLIENT                    = SY-MANDT
     GROUP                     = LV_SESNAM
     HOLDDATE                  = '20040805'
     KEEP                      = 'X'
     USER                      = SY-UNAME
     PROG                      = SY-CPROG
* IMPORTING
*    QID                       =
   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 :/ 'Session not open'.
ENDIF.
ENDFORM.                    " FORM_OPENSESSION
*&      Form FORM_INSERT
*       fORM TO INSERT ERROR RECOED INTO A SESSION.
FORM FORM_INSERT .
*--Inserting the record into session.
CALL FUNCTION 'BDC_INSERT'
    EXPORTING
      TCODE                  = 'FD01'
*     POST_LOCAL             = NOVBLOCAL
*     PRINTING               = NOPRINT
*     SIMUBATCH              = ' '
*     CTUPARAMS              = ' '
    TABLES
      DYNPROTAB              = IT_CUSTBDC
    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 :/ 'Unable to insert the record'.
ENDIF.
ENDFORM.                    " FORM_INSERT
*&      Form FORM_CLOSESESS
*       Form to Close the Open Session.
FORM FORM_CLOSESESS .
CALL FUNCTION 'BDC_CLOSE_GROUP'
    EXCEPTIONS
      NOT_OPEN    = 1
      QUEUE_ERROR = 2
      OTHERS      = 3.
IF SY-SUBRC <> 0.
ENDIF.
ENDFORM.                    " FORM_CLOSESESS
*&      Form FORM_FORMATMSG
*       Form to format messages.
FORM FORM_FORMATMSG .
*--Var to store the formatted msg.
DATA : LV_MSG(255).
CALL FUNCTION 'FORMAT_MESSAGE'
    EXPORTING
      ID        = SY-MSGID
      LANG      = SY-LANGU
      NO        = SY-MSGNO
      V1        = SY-MSGV1
      V2        = SY-MSGV2
      V3        = SY-MSGV3
      V4        = SY-MSGV4
    IMPORTING
      MSG       = LV_MSG
    EXCEPTIONS
      NOT_FOUND = 1
      OTHERS    = 2.
IF SY-SUBRC = 0.
    WRITE :/ LV_MSG.
ENDIF.
ULINE.
ENDFORM.                    " FORM_FORMATMSG
*&      Form form_writeop
*       To write the totals and the session name.
FORM FORM_WRITEOP .
WRITE :/ 'Total Records Uploaded :',V_TLINES,
           / 'No of Error Records :',V_ELINES,
           / 'No of Success Records :',V_SLINES,
           / 'Name of the Session :',V_SESNAM.
ULINE.
ENDFORM.                    " form_writeop

HUMO Error Logs

Does anyone know what table the error logs for the HUMO transaction are stored?
I have a requirement to use BDC to split a delivery and need to be able to track the errors in my main program.

hello,
Can you try BALHDR ?
Cheers !

Oracle errors in Weblogic Error logs appear in non english

We have a problem with weblogic error logging. Specifically, in a managed server's log file, Oracle errors such as ORA-XXXX show in Greek, not English. We are assuming
that this is because the timezone is Europe/Athens. However, the weblogic application server runs with user.language=en, user.country=US. What's more, there are 4 application servers and 2 of them have this problem. The oracle database is accessed via weblogic datasources.
Oracle database server Setup: Oracle Server 11gR2 running on Oracle Linux 64 bit, timezone set to Europe/Athens
Weblogic Server: Weblogic 10.3.5 running on Oracle Linux 64 bit, timezone set to Europe/Athens
The managed server, according to jrockit, the jvm runs with the following language related system properties:
user.language=en, user.country=US, user.timezone=Europe/Athens
The question is: How do we tell oracle / weblogic to log english text for the ORA errors?
Thanks,
Chris

I digged in the weblogic installation directory and it seems like the domain configuration wizard messed up the jdbc configs for the data sources.
The config xml files for the data sources in the /domain root/config/jdbc directory had oracle driver but the test query was for pointbase. I double checked from the database.xml file in the init-info directory and corrected the entry in the datasource config xmls and voila!.. the errors were gone.
I am not sure if this was the right approach and whether i have solved the issue or simply patched it.. so I am keeping the question open. If any one has any inputs I will be grateful.
If the mods/admins feel that the thread should be marked as solved I will surely do so.
Thanks.

Sap Payroll error log report

Hi All,
We are developing Report on SAP Payroll log with the error message . Is any table exist in SAP where we can get the standard error message repositery and then convert it in the User freindly error message ?
Thanks
H

Hello hg,
Before developing report on SAP Payroll error log I suggest taking a look at below blog. There is a new functionality from SAP to improve payroll data validation and they are calling it "Control Center Add-On".
This is going to be a free add on for anyone who is on EHP7 and NetWeaver on 7.4 release. The general availability is June 2nd 2014.
Improve payroll data validation with SAP Payroll control center add-on
Hope this helps.
Thanks,
Hemanth Jamithi.

No Error Log generated in 'Costing' step in Costing Run (CK40N)

In the Costing Run, when the 'Costing' step is run (after 'Material selection' and 'BOM Explosion' steps), it gives a hard stop when it encounters the 1st error, instead of completing the 'Costing ' step and giving an Error Log with material information and nature of errors. This makes it very cumbersome to resolve all the errors.
In the Costing Variant setting in config, the u2018Save Error Log' indicator has been checked.
Please let me know if I am missing something.
Venkat

Hi Vimal,
Your proposal does not resolve the issue. I found OSS Note 375901, which addresses this issue - see below
:In Customizing for the costing variant (Transaction OKKN) in the tab "Misc.", you chose "Messages online" for the Error Management option.
Solution
Change the error management for the costing variant to
"Log and Save Messages..."
Many thanks for your inputs.
Venkat

BDC error log

Similar Messages

Maybe you are looking for