Regarding Error records in Sesson method

in an interview i have faced one question that
"i have 2000 records. when session is processed 1500 records processed perfectly, rest of the records failed to process".
Q) what we have to do those error records.
q) Need to process the session again?.
q) Need to process that praticular error again?.

Hi Sirisha,
I would say that before going for actual data upload in a BDC session program, u should generate an error log flat file and a success file by running the program in Simulation Mode, means in simulation mode the transactions will be executed in backgroud or foreground as u wish, just in place of OKCODE pass the value /N instead of /SAVE. For this simulation mode u need to generate a call transaction program inside the same program. This method will help u to forcast about the nature of data before going for actual session mode upload.
If Helpful please reward with some points.
Regards,
Pulokesh

Similar Messages

Updating error records in seession method

error records in session method
Posted: Jan 15, 2008 9:52 AM Edit E-mail this message Reply
hai anybody tell me how can we handle error records in session method ..we have a logfile ok...how can we update those error records in online..

Hi,
If there are not too many errors you can process the session in Error mode & correct the errors online. Else you have to check the cause of error taking inputs from the log file. & repeat the steps.
Best Regards, Murugesh

Errors in IDOC transfer method.....

Hi
I am loading customer data ( LIS , S001) by using transfer method as IDOC. now i got 4 error records. so how do we rectify in IDOC method. i can use PSA also, so that its very easy to rectify errors. But how do we rectify the error records in IDOC method...., any idea gurus......,
Regards
swetha

Looks to me like you're not telling the linker to create a library (DLL). I'm not familiar with Linux, but clearly if the linker if looking for 'main' then its trying to build an executable.

How to send error record to session in call transaction method

Hi experts,
I want to send only the error record to session while executing the program in call transaction method. please give me example on this
regards,
siva kumar

One logiv that I can suggest is that after you have got the details of the record in error, you write another perform build_Session and put the below logic in that.
Logic:
1. Build a internal table for the error records similar to the internal table you used for looping for the call transaction. In short this internal table will have only the records that have an error in call transaction.
2. Copy the recordign that you have done before and put it in the perform inside the loop and build the BDC table.
3. Then .using this BDC table you can build the BDC session.
- Guru
Reward points for helpful answers
3.

Call transaction and session methods error records

Hi All,
In call transaction method we will define a table of type bdcmsgcoll for storing the error records and later we will display that error message with format_message.In that table only those records with message type 'E' are stored or any other ?
I mean while transferring data using BDC either by call transaction or session method ,if we got message type other than 'E', like W or A etc.what about those records ,they will be udpated sucessfully or not?which message type records will be stored in the error log or in bdcmsgcoll table.
Thanks,
Rakesh.

You will get all type of message recorded in the BDCMSGCOLL table when you use the CALL Transaction
For Session mehtod, while running you need to tick the "Extended Log" checkbox on the popup which comes after the process button.
Regards,
Naimesh Patel

Listing BDC session method error records

Hi ABAP'rs,
                 Can any one help me, how to show error records of BDC session method on the List screen.
                                    Thanks and Regards,
                                                          Param.

Hi,
goto sm35 and find the error logs.
what do you mean by list screen...do you mean in ort output ?
Regards,
pankaj singh

How will you collect error records in call transaction method

hello
how will handle errors in call transaction method...

DATA: BEGIN OF ITAB OCCURS 0,
      F1(10) TYPE C,
      F2(18) TYPE C,
      F3(15) TYPE C,
      END OF ITAB.
DATA: BEGIN OF ITAB1 OCCURS 0,
      F1(2) TYPE C,
      F2(10) TYPE C,
      F3(18) TYPE C,
      F4(15) TYPE C,
      END OF ITAB1.
DATA : ITAB2 LIKE ITAB OCCURS 0 WITH HEADER LINE,
            IT_SUCCESS LIKE ITAB OCCURS 0 WITH HEADER LINE,
            IT_ERROR LIKE ITAB OCCURS 0 WITH HEADER LINE.
DATA : BDCDATA LIKE BDCDATA OCCURS 0 WITH HEADER LINE,
           T_BDCMSGCOLL LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
CALL TRANSACTION 'VA01' USING BDCDATA MODE 'N' UPDATE 'S'
                            MESSAGES INTO T_BDCMSGCOLL.
PERFORM ERRORHANDLING TABLES ITAB2 USING COUNT1 COUNT2.
REFRESH BDCDATA.
FORM ERRORHANDLING TABLES   P_ITAB2 STRUCTURE ITAB
                   USING    P_COUNT1
                             P_COUNT2.
IF SY-SUBRC <> 0.
    CALL FUNCTION 'FORMAT_MESSAGE'
      EXPORTING
        ID        = SY-MSGID
        LANG      = '-D'
        NO        = SY-MSGNO
        V1        = SY-MSGV1
        V2        = SY-MSGV2
        V3        = SY-MSGV3
        V4        = SY-MSGV4
      IMPORTING
        MSG       = T_BDCMSGCOLL
      EXCEPTIONS
        NOT_FOUND = 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.
    IF P_COUNT1 = 1.
      WRITE : / ' The records not loaded are '.
      P_COUNT1 = P_COUNT1 + 1.
    ENDIF.
    LOOP AT P_ITAB2.
      WRITE : / P_ITAB2-F1 , P_ITAB2-F2 , P_ITAB2-F3 .
      CLEAR P_ITAB2.
      DELETE P_ITAB2 INDEX 1.
    ENDLOOP.
    WRITE : /.
ELSE.
    IF P_COUNT2 = 1.
      WRITE : / ' The records loaded are '.
      P_COUNT2 = P_COUNT2 + 1.
    ENDIF.
    LOOP AT P_ITAB2.
      WRITE : / P_ITAB2-F1 , P_ITAB2-F2 , P_ITAB2-F3 .
      CLEAR P_ITAB2.
      DELETE P_ITAB2 INDEX 1.
    ENDLOOP.
    WRITE : /.
ENDIF.
ENDFORM.                    " errorhandling

How to upload error records in call transaction method

Hi all,
While uploading data by using call transaction. If any errors occured, how can we process that error records to database.
If all records are processed. How can we display the recent records which where uploaded.
AdvanceThanks for all.

Hi Bharath
You can handle this in many ways. But the easiest option to do is as below,
once the call transaction ends in error, move that particular upload data to a separate internal table. Then finally download all these data to an error file.
Besides this after processing all the records diplay the log for error. So that users can modify the error in the file and can use the same for uploading again. For the data that has been processed successfully you can display the log similarly.
The error as well as sucess messages can be obtained from the messages table.
    CALL TRANSACTION TCODE USING BDCDATA
                     MODE   CTUMODE
                     UPDATE CUPDATE
                     MESSAGES INTO MESSTAB.
Regards
Kathirvel

Track error records in Call Transaction method

Hi
I have used call transaction method for uploading legacy data.
I need to track the error record.
Please help me to find out the solution.
Thanks in advance
Reagards
shriraam

HI,
!. Obtain the messaged into an Interal table of type BDCMSGCOLL using Call Transaction syntax..
               Call Transactio <Tcode>
                       using <BDC Table>
                      mode <A/N/P>
                      update <A/S>
                     messages INTO <mSGTAB>
2. Read the Msg table for eroors and success messages
3. Then format the messge with the help of Function Module :'Format_messages'.
4. Display the respective messges with the help of write statements or with the help of ALV.
Rgds
Umakanth

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

Regarding Condition record in CRM using field MATKL (Material Group)

Hi All
Currently we are working in SAP CRM 5.2 and it has been connected with backend ECC 6.0.
This scenario is about Pricing which has been maintained in ECC and inturn flows to CRM with few filters in place.
There are few customized Condition Tables in ECC with combination of Sales org./ material group for which discount has been maintained. A proper condition record is also available for this Condition table and it has been assigned to a access sequence and inturn assigned to a condition type.
All these procedures, condition types, access sequence has flown from ECC to CRM. And all the condition tables are active in IMG (Basic Functions / Pricing / Define Settings for Pricing / Create Condition Tables)
When i check in
(SAP menu / Master Data / Prices and Conditions / SAPCND/GCM - Maintain Conditions )
Application - CRM,
Maintenance group - PRODDISCOU,
Maintenance context - GCM
Here for the above mentioned combination when i select the Key Combination (Condition Table) and enter the customized table number (Sales org. / Material Group) iam getting a dump which says the following.
Error analysis
Short text of error message:
Implementation of Method ATTRIBUTE_CONVERSION for BAdI /SAPCND/ROLLNAME for filter MATKL is missing
Program............. "/SAPCND/CL_MNT_COND_MAINT_UI==CP"
Screen.............. "/SAPCND/SAPLCOND_MAINTAIN 0100"
Screen line......... 8
Information on where terminated
Termination occurred in the ABAP Program "/SAPCND/CL_MNT_COND_MAINT_UI==CP" -
in "ON_FCODE_SELECT".
The main program was "/SAPCND/GENERAL_COND_MAINT ".
In the source code you have the termination point in line 622
of the (Include) program "/SAPCND/CL_MNT_COND_MAINT_UI==CM005".
Please let me know the solution, Request you to do the needful aSAP.
Regards
*Ramesh*

Hi Ramesh,
Have you checked the following note?
Note 441083 - Transferring conditions for material group MATKL to CRM
Kind regards,
Johan Wigert

How to handle the errors in BDC Session method

Hi All,
I am uploading Material Master (MM01) records using BDC Session Method.my problem is when i am running the program, all the error records are going to flat file.how can i correcting the error records and after correction how can i re-process the error records.tell me with example.
i have around 70,000 records in my flat file.

Hi,
I am attaching few threads.Hope these will help you.
If there are any error records in session, all those error records will get poulated in log .SM35 and after the session is completed , u can see error records which can be corrected and reprocessed again
We have the structures BDCLD and BDCLM, which will capture the log details inthe session. Firstly, sesssion should be processed. After that log will be created. Then caputure the information into an internal table using BDCLM and BDCLD.
and refer the link.
error correction in bdc session
regards
Madhu

Workflow condition to check error records in a multi line container element

Hi All,
My requirement is to change a standard workflow in which below condtion is checked and subsequent action is taken.
The condtion checks a return internal table contains a row or not. Now the problem is for success and Information messages
also the return table contains entries and the condition is becoming true. Subsequently workflow follows error recovery steps when there is no error.
SAP suggests a note with manual corrections and mentions to change the condition to check whether error records are there. So can we enhance the condition &return& NX to something that it checks error records. I dont want to create a new step and go to business object method to delete non error records.
Please let me know if this condition can be enhanced.
Thanks in Advance.
Aleem Mohiuddin.

Dear Aleem,
As this is sap standard workflow, should report this error and wait for feed back. Or add a loop step before of this check any E messages inside, if yes put a errflg as x other wise keep as blank.
Best of luck.
Regards,
Ranjith

How to show Session Error Records to End Users

Hi all,
I had to populate data using SESSION Method...
I have 1000 records, out of which 750 records where updated correctly but i got 250 error records in it.
i know that error records are stored in Error log/ INCORRECT SESSION in SM35.
Now i want to modify these errounous records and repopulate them.
Questions.
1) We click on ANALYSE in SM35 to determine which sreen and value produced the error. if we have small data we can correct them interactively there only. But for 250 records how we have to correct them and upload 250 errors records.
2) Can we download those error records into a flatfile.
3) Is there any other method to handle such situation.
Regards
Surendar

Vijay,
I got your piece of code.... Its looking really good.
Here my point is once that first validation is done i am doing exit. That means total process stopped and cotrol comes out of the program. so how can this
IF W_FLAG_ERROR = X. DISPLAY THE ERROR MESSAGE to the user
will be executed ...............
and
bu writing it on the report list or just do LEAVE-LIST PROCESSING and come back to the selection screen. ESLE. CONTINUE PROCESSING ENDIF.
I didn't fallow what u said here can u explain bit clearly plzzzzzz
Nisha....

Regarding Error records in Sesson method

Similar Messages

Maybe you are looking for