In info spoke customer details generating in two lines

Hi All,
   In Info spoke after file trigerring job background, file creating in AL11 but in that file for each customer details generating in two lines.
Eg:
Correct reocrd : 1212|dsfsdfd|ddf|fdf||dfsdf
Error record: 1212|dsfsdfd
                       |ddf|fdf||dfsdf
Thanks,
Manjunatha

Hi All,
    The above issue is getting due to # character in text at end(e.g ljdfsaa##). After removing # characters in text issue got resolved.
Thansk,
Manjunatha

Similar Messages

  • Zreport for vendor customer details.

    Hi ,
    I have to create a report tto display a vendor and customer details. on screen i have customer code and vendor code with company code and fiscal year. when i select the cust. code plant and year it will show the doc.no ,post. and doc. date,doc type ,qty and amount as per customer details.
    after that as per billing doc. of specific customer ,select excise invoice number and match it with reference number (xblnr) of vendor code. and once it is matched select tht vendor doc.no. post. and doc. date amount and qty and display it in report.so how to right a coding for thesame
    let me know as its urgent.
    Rgrs
    Suchita

    please find below coding for your reference.
    *& Report  ZFI_VEND_CUST_DETAILS
    REPORT  ZFI_VEND_CUST_DETAILS
      NO STANDARD PAGE HEADING
              LINE-COUNT 65
              MESSAGE-ID 00.
    TABLES: BSID,BSIK.
    DATA: IT_BSID LIKE BSID OCCURS 0 WITH HEADER LINE.
    DATA: IT_BSIK LIKE BSIK OCCURS 0 WITH HEADER LINE.
    DATA: IT_J_1IEXCHDR LIKE J_1IEXCHDR OCCURS 0 WITH HEADER LINE.
    DATA: BEGIN  OF IT_OUT OCCURS 0,
            BELNR LIKE BSID-BELNR,        " added On 17.04.2007
            BLDAT LIKE BSID-BLDAT,
            BUDAT LIKE BSID-BUDAT,
            BLART LIKE BSID-BLART,
            NAME  LIKE KNA1-NAME1,                           "Name 1
            MATNR LIKE VBRP-MATNR,    "Material Number
            ARKTX LIKE VBRP-ARKTX,          "Material description
            FKIMG LIKE VBRP-FKIMG,          "Quantity mentioned in the excise invoice
            VBELN LIKE BSID-VBELN,          "Billing Document
            BUKRS LIKE BSID-BUKRS,
           NAME1 LIKE LFA1-NAME1,
            KUNNR LIKE BSID-KUNNR,
            WRBTR LIKE BSID-WRBTR,
            DMBTR LIKE BSID-DMBTR,
            ZUONR LIKE BSID-ZUONR,
           XBLNR LIKE BSID-XBLNR,
           MENGE LIKE VBRP-MENGE,
           LIFNR  LIKE BSIK-LIFNR,        "VENDOR CODE
            EXNUM LIKE J_1IEXCHDR-EXNUM,
            BELNR1 LIKE BSIK-BELNR,        " added On 17.04.2007
            BLDAT1 LIKE BSIK-BLDAT,
            BUDAT1 LIKE BSIK-BUDAT,
           BLART LIKE BSID-BLART,
           NAME  LIKE KNA1-NAME1,                           "Name 1
           MATNR LIKE VBRP-MATNR,    "Material Number
           ARKTX LIKE VBRP-ARKTX,          "Material description
           FKIMG1 LIKE VBRP-FKIMG,          "Quantity mentioned in the excise invoice
           VBELN LIKE BSID-VBELN,          "Billing Document
           BUKRS LIKE BSID-BUKRS,
            NAME1 LIKE LFA1-NAME1,
           KUNNR LIKE BSID-KUNNR,
           WRBTR LIKE BSID-WRBTR,
            DMBTR1 LIKE BSIK-DMBTR,
           ZUONR LIKE BSID-ZUONR,
            XBLNR LIKE BSIK-XBLNR,
           MENGE LIKE VBRP-MENGE,
            LIFNR  LIKE BSIK-LIFNR,
            END OF IT_OUT.
    *DATA: IT_OUT1 LIKE IT_OUT OCCURS 0 WITH HEADER LINE.
    *ALV VARIABLES AND INTERNAL TABLES
    TYPE-POOLS: SLIS.
    DATA: IS_LAYOUT     TYPE SLIS_LAYOUT_ALV,
          IT_FIELDCAT   TYPE SLIS_T_FIELDCAT_ALV,
          IT_LISTHEADER TYPE SLIS_T_LISTHEADER,
          IT_EVENTS     TYPE SLIS_T_EVENT,
          IT_PRINT      TYPE SLIS_PRINT_ALV OCCURS 1 WITH HEADER LINE.
    *SELECTION SCREEN DEFINITIONS
    SELECTION-SCREEN BEGIN OF BLOCK B WITH FRAME TITLE TEXT-001.
    SELECT-OPTIONS : SO_KUNNR FOR   BSID-KUNNR,
                     SO_LIFNR FOR   BSIK-LIFNR,
                     SO_BLART FOR   BSID-BLART.
    PARAMETER      : P_BUKRS LIKE   BSID-BUKRS OBLIGATORY,
                     P_GJAHR LIKE   BSID-GJAHR OBLIGATORY.
    SELECTION-SCREEN END OF BLOCK B.
    *START-OF-SELECTION
    START-OF-SELECTION.
      PERFORM GET_DATA.
      PERFORM DISPLAY_DATA.
    *&      Form  GET_DATA
          text
    -->  p1        text
    <--  p2        text
    form GET_DATA .
    SELECT * FROM BSID
    INTO TABLE IT_BSID
    WHERE KUNNR IN SO_KUNNR AND
    BUKRS = P_BUKRS AND
    GJAHR = P_GJAHR.
    LOOP AT IT_BSID.
    IT_OUT-BELNR = IT_BSID-BELNR.
    IT_OUT-BUKRS = IT_BSID-BUKRS.
    IT_OUT-KUNNR = IT_BSID-KUNNR.
    IT_OUT-ZUONR = IT_BSID-ZUONR.
    IT_OUT-DMBTR = IT_BSID-DMBTR.
    IT_OUT-VBELN = IT_BSID-VBELN.
    IT_OUT-XBLNR = IT_BSID-XBLNR.
    IT_OUT-BLART = IT_BSID-BLART.
    IT_OUT-BUDAT = IT_BSID-BUDAT.
    IT_OUT-BLDAT = IT_BSID-BLDAT.
    APPEND IT_OUT.
    ENDLOOP.
    *SELECT * FROM J_1IEXCHDR
    *INTO IT_J_1IEXCHDR
    *WHERE RDOC = IT_OUT-VBELN.
    *LOOP AT IT_J_1IEXCHDR.
    IT_OUT-EXNUM = IT_J_1IEXCHDR-EXNUM.
    **ENDLOOP.
    *SELECT * FROM BSIK
    *INTO TABLE IT_BSIK
    *WHERE XBLNR = IT_OUT-EXNUM AND
    *LIFNR IN SO_LIFNR AND
    *BUKRS = P_BUKRS AND
    *GJAHR = P_GJAHR.
    *LOOP AT IT_BSIK.
    *IT_OUT-BELNR1 = IT_BSIK-BELNR.
    **IT_OUT-BUKRS = IT_BSIK-BUKRS.
    *IT_OUT-LIFNR = IT_BSIK-LIFNR.
    **IT_OUT-ZUONR = IT_BSIK-ZUONR.
    *IT_OUT-DMBTR1 = IT_BSIK-DMBTR.
    *IT_OUT-XBLNR = IT_BSIK-XBLNR.
    **IT_OUT-BLART = IT_BSIK-BLART.
    *IT_OUT-BUDAT1 = IT_BSIK-BUDAT.
    *IT_OUT-BLDAT1 = IT_BSIK-BLDAT.
    *APPEND IT_OUT.
    *ENDLOOP.
    *ENDLOOP.
    *ENDSELECT.
    *SORT IT_OUT BY KUNNR.
    LOOP AT IT_OUT.
    SELECT SINGLE EXNUM FROM J_1IEXCHDR
    INTO IT_OUT-EXNUM
    WHERE RDOC = IT_OUT-VBELN.
    SELECT BELNR LIFNR DMBTR XBLNR BUDAT BLDAT
    FROM BSIK INTO (IT_OUT-BELNR1,IT_OUT-LIFNR,IT_OUT-DMBTR1,IT_OUT-XBLNR,IT_OUT-BUDAT1,IT_OUT-BLDAT1)
    WHERE XBLNR = IT_OUT-EXNUM.
    ENDSELECT.
    SELECT SINGLE NAME1            "NAME OF CUSTOMER
               FROM KNA1
               INTO IT_OUT-NAME
               WHERE KUNNR = IT_OUT-KUNNR.
    SELECT SINGLE NAME1            "NAME OF VENDOR
                   FROM LFA1
                   INTO IT_OUT-NAME1
                   WHERE LIFNR = IT_OUT-LIFNR.
    SELECT MATNR ARKTX FKIMG
               FROM VBRP
               INTO (IT_OUT-MATNR,IT_OUT-ARKTX,IT_OUT-FKIMG)
               WHERE VBELN = IT_OUT-VBELN AND
                     WERKS = P_BUKRS.
    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_OUTPUT'
      EXPORTING
        input         = IT_OUT-MATNR
    IMPORTING
       OUTPUT        = IT_OUT-MATNR.
    MODIFY IT_OUT.
    CLEAR IT_OUT.
    ENDSELECT.
    ENDLOOP.
    endform.                    " GET_DATA
    *&      Form  DISPLAY_DATA
          text
    -->  p1        text
    <--  p2        text
    form DISPLAY_DATA .
      PERFORM FILL_LAYOUT_STRUCTURE.
      PERFORM ALV_HEADER USING IT_LISTHEADER.
      PERFORM FILL_FIELDCAT USING :
          'BLDAT'    'DOC Date'             10  'IT_OUT'  SPACE SPACE,
          'BUDAT'    'Post.Date'            10  'IT_OUT'  SPACE SPACE,
          'KUNNR'    'Customer Code'        10  'IT_OUT'  SPACE SPACE,
          'NAME'     'Customer Name'        35  'IT_OUT'  SPACE SPACE,
          'LIFNR'    'VENDOR CODE'          10  'IT_OUT'  SPACE SPACE,
          'NAME1'    'VENDOR DESC'          35  'IT_OUT'  SPACE SPACE,
          'BLART'    'Doc. Type'             2  'IT_OUT'  SPACE SPACE,
          'VBELN'    'BILLING DOC NO.'      10  'IT_OUT'  SPACE SPACE,
          'BELNR'    'Account Doc. No.'     10  'IT_OUT'  SPACE SPACE,
          'DMBTR'    'AMOUNT IN LOCAL'      13  'IT_OUT'  SPACE SPACE,
          'MATNR'    'Material Code'        10  'IT_OUT'  SPACE SPACE,
          'ARKTX'    'Material DESC'        35  'IT_OUT'  SPACE SPACE,
          'FKIMG'    'QTY'                  12  'IT_OUT'  SPACE SPACE,
          'ZUONR'    'ASSIGNNMENT'          18  'IT_OUT'  SPACE SPACE,
          'EXNUM'    'Excise inv no.'       13  'IT_OUT'  SPACE SPACE,
          'BELNR1'   'Account Doc. No.'     10  'IT_OUT'  SPACE SPACE,
          'BLDAT1'   'DOC Date'             10  'IT_OUT'  SPACE SPACE,
          'BUDAT1'   'Post.Date'            10  'IT_OUT'  SPACE SPACE,
          'DMBTR1'   'AMOUNT IN LOCAL'      13  'IT_OUT'  SPACE SPACE,
          'XBLNR'    'REFERENCE DOC'        10  'IT_OUT'  SPACE SPACE.
    PERFORM ALV_EVENTS USING IT_EVENTS.
    PERFORM ALV_PRINT.
      PERFORM ALV_DISPLAY.
    endform.                    " DISPLAY_DATA
    *&      Form  FILL_LAYOUT_STRUCTURE
          text
    -->  p1        text
    <--  p2        text
    form FILL_LAYOUT_STRUCTURE .
    DATA: WA_EVENT       TYPE SLIS_ALV_EVENT,
            WA_LISTHEADER  TYPE SLIS_T_LISTHEADER.
      CLEAR IS_LAYOUT.
      IS_LAYOUT-ZEBRA = 'X'.
         is_layout-F2CODE = '&ETA'.
         is_layout-detail_popup = 'X'.
      IS_LAYOUT-INFO_FIELDNAME = 'COL_LINE'.
    endform.                    " FILL_LAYOUT_STRUCTURE
    *&      Form  FILL_FIELDCAT
          text
         -->P_0606   text
         -->P_0607   text
         -->P_10     text
         -->P_0609   text
         -->P_SPACE  text
         -->P_SPACE  text
    form FILL_FIELDCAT  using    F D O T TO P.
      DATA WA_FIELDCAT TYPE SLIS_FIELDCAT_ALV.
      STATICS POS LIKE SY-INDEX VALUE 1.
      POS = POS + 1.
      CLEAR WA_FIELDCAT.
      MOVE : 1     TO   WA_FIELDCAT-ROW_POS,
             POS   TO   WA_FIELDCAT-COL_POS,
             F     TO   WA_FIELDCAT-FIELDNAME,
             D     TO   WA_FIELDCAT-SELTEXT_L,
             O     TO   WA_FIELDCAT-OUTPUTLEN,
             T     TO   WA_FIELDCAT-TABNAME,
             TO    TO   WA_FIELDCAT-DO_SUM,
             P     TO   WA_FIELDCAT-FIX_COLUMN.
      APPEND WA_FIELDCAT TO IT_FIELDCAT.
    endform.                    " FILL_FIELDCAT
    FORM ALV_EVENTS USING EVENTS TYPE SLIS_T_EVENT.
      DATA : WA_EVENTS TYPE SLIS_ALV_EVENT.
      CLEAR WA_EVENTS.
      WA_EVENTS-NAME = 'TOP_OF_PAGE'(001).
      WA_EVENTS-FORM = 'TOP_OF_PAGE'.
      APPEND WA_EVENTS TO IT_EVENTS.
    ENDFORM.                    "alv_events
    *&      Form  ALV_DISPLAY
          text
    -->  p1        text
    <--  p2        text
    form ALV_DISPLAY .
    CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
       EXPORTING
      I_INTERFACE_CHECK                 = ' '
      I_BYPASSING_BUFFER                = ' '
      I_BUFFER_ACTIVE                   = ' '
         I_CALLBACK_PROGRAM                = SY-REPID
      I_CALLBACK_PF_STATUS_SET          = ' '
         I_CALLBACK_USER_COMMAND           = 'CALL_TCODE'
         I_CALLBACK_TOP_OF_PAGE            = 'TOP_OF_PAGE'
      I_CALLBACK_HTML_TOP_OF_PAGE       = ' '
      I_CALLBACK_HTML_END_OF_LIST       = ' '
      I_STRUCTURE_NAME                  =
      I_BACKGROUND_ID                   = ' '
      I_GRID_TITLE                      =
      I_GRID_SETTINGS                   =
         IS_LAYOUT                         = IS_LAYOUT
         IT_FIELDCAT                       = IT_FIELDCAT
      IT_EXCLUDING                      =
      IT_SPECIAL_GROUPS                 =
       IT_SORT                           = i_sort[]
      IT_FILTER                         =
      IS_SEL_HIDE                       =
         I_DEFAULT                         = 'X'
         I_SAVE                            = 'A'
      IS_VARIANT                        =
         IT_EVENTS                         = IT_EVENTS
      IT_EVENT_EXIT                     =
         IS_PRINT                          = IT_PRINT
      IS_REPREP_ID                      =
      I_SCREEN_START_COLUMN             = 0
      I_SCREEN_START_LINE               = 0
      I_SCREEN_END_COLUMN               = 0
      I_SCREEN_END_LINE                 = 0
      I_HTML_HEIGHT_TOP                 = 0
      I_HTML_HEIGHT_END                 = 0
      IT_ALV_GRAPHICS                   =
      IT_HYPERLINK                      =
      IT_ADD_FIELDCAT                   =
      IT_EXCEPT_QINFO                   =
      IR_SALV_FULLSCREEN_ADAPTER        =
    IMPORTING
      E_EXIT_CAUSED_BY_CALLER           =
      ES_EXIT_CAUSED_BY_USER            =
       TABLES
          T_OUTTAB                          = IT_OUT
       EXCEPTIONS
         PROGRAM_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.
    endform.                    " ALV_DISPLAY
    *FORM FOR TOP OF PAGE
    FORM TOP_OF_PAGE.
      CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
        EXPORTING
          IT_LIST_COMMENTARY = IT_LISTHEADER.
    ENDFORM.                    "top_of_page
    *&      Form  alv_header
    FORM alv_header  USING    P_IT_LISTHEADER.
      data : wa_listheader  type slis_listheader.
      data : v_date1(10).
      data : v_date2(10).
      data : v_kunnr1 LIKE bsid-kunnr.
      data : v_kunnr2 LIKE bsid-kunnr.
      data : v_name1 like t001w-name1.
      clear wa_listheader.
      wa_listheader-typ = 'H'.
      move  'DETAILED CUSTOMER VENDOR DETAILS'
      to  wa_listheader-info.
      append wa_listheader to it_listheader.
    select single name1
         from t001w
         into v_name1
         where werks = p_bukrs.
    clear wa_listheader.
    wa_listheader-typ = 'S'.
    wa_listheader-key = 'Plant'.
    move v_name1
    to wa_listheader-info.
    append wa_listheader to it_listheader.
    write so_budat-low  to v_date1  dd/mm/yyyy no-gap.
    write so_budat-high to v_date2  dd/mm/yyyy no-gap.
    if so_budat-low is not initial and so_budat-high is not initial.
       clear wa_listheader.
       wa_listheader-typ = 'S'.
       wa_listheader-key = 'Date '.
       concatenate v_date1 ' To ' v_date2 into
                           wa_listheader-info separated by space.
       wa_listheader-info = wa_listheader-info.
       append wa_listheader to it_listheader.
    elseif  so_budat-low is initial and so_budat-high is initial.
       clear wa_listheader.
       wa_listheader-typ = 'S'.
       wa_listheader-key = 'Date '.
       wa_listheader-info = '*'.
       append wa_listheader to it_listheader.
    elseif so_budat-high is initial.
       clear wa_listheader.
       wa_listheader-typ = 'S'.
       wa_listheader-key = 'Date '.
       wa_listheader-info = v_date1.
       append wa_listheader to it_listheader.
    endif.
    v_kunnr1 = so_kunnr-low.
    v_kunnr2 = so_kunnr-high.
    if so_kunnr-low is not initial and so_kunnr-high is not initial.
       clear wa_listheader.
       wa_listheader-typ = 'S'.
       wa_listheader-key = 'Customer '.
       concatenate v_kunnr1 ' To ' v_kunnr2 into
                           wa_listheader-info separated by space.
       wa_listheader-info = wa_listheader-info.
       append wa_listheader to it_listheader.
    elseif  so_kunnr-low is initial and so_kunnr-high is initial.
       clear wa_listheader.
       wa_listheader-typ = 'S'.
       wa_listheader-key = 'Customer '.
       wa_listheader-info = '*'.
       append wa_listheader to it_listheader.
    elseif so_kunnr-high is initial.
       clear wa_listheader.
       wa_listheader-typ = 'S'.
       wa_listheader-key = 'Customer '.
       wa_listheader-info = v_kunnr1.
       append wa_listheader to it_listheader.
    endif.
    ENDFORM.                    " alv_header.
    waiting for ur reply.
    Thanx
    Suchita

  • Info Spoke-ABAP Code Modification

    Hi,
       The below code is used as a customer exit variable Which give te YEAR TO DATE value on a KF.
    Could you please mofify this,That output will be year to date value & to eliminate '0' values and have to use it in Infospokes
    OUT PUT: If i use this  on a sales Qty KF,The  user enters the week so that it has to display sales qty againist dept starting from the year to the selected week and also should display only values that are NON Zero
    I need to use this in info spoke
    WHEN 'ZYTD'.
    CLEAR l_s_range.
    wdate = ww_date.
    weekno = '01'.
    SELECT SINGLE * FROM /bic/pycalday_w
    WHERE /bic/ycalday_w = wdate
    AND objvers = 'A'.
    thisweek = /bic/pycalday_w-/bic/ylwk_w.
    CONCATENATE thisweek(4) weekno INTO firstweek.
    l_s_range-low = firstweek.
    l_s_range-high = thisweek.
    l_s_range-sign = 'I'.
    l_s_range-opt = 'BT'.
    APPEND l_s_range TO e_t_range.
    Thanks

    I think there is some problem with your ABAP program.
    Have you used OPEN DATASET statement, if so check if you have mentioned file path etc correctly.
    Can you try debugging the code.
    Hope this helps.

  • Cutom T-Code for seding customer details thru IDoc Debmas

    Hi Experts,
    I have a requirment where in.. I need to send customer details thru IDoc from a custom screen which has cutomer text box and a submit button. After entering cutomer and clicking on submit debmas06 Idoc has to be triggered.
    I am not an ABAP expert... please help me with process on devloping the above reqirment.
    This is a critical requirment please help ASAP.
    Thanks,
    Suma

    Hi,
    u have to use standalone program..iam giving one sample code..aong with u have define the RFC (SM59,WE21(Create port),WE20(create partner profile,BD64 distribute model view)...u have to do..
    when u press on submit button,,,
    *& Report ZZ_Program_To_Create_Idoc
    report zz_program_to_create_idoc .
    tables: ekko,ekpo.
    selection-screen skip 3.
    selection-screen begin of block b1 with frame title titl.
    selection-screen skip.
    select-options s_ebeln for ekko-ebeln.
    selection-screen skip.
    selection-screen end of block b1.
    data: header_segment_name like edidd-segnam value 'Z1EKKO',
    item_segment_name like edidd-segnam value 'Z1EKPO',
    idoc_name like edidc-idoctp value 'Z19838IDOC1'.
    data: header_segment_data like z1ekko,
    item_segment_data like z1ekpo.
    data: control_record like edidc.
    data: messagetyp like edmsg-msgtyp value 'ZZ9838MESG1'.
    data: i_communication like edidc occurs 0 with header line,
    i_data like edidd occurs 0 with header line.
    data: begin of i_ekko occurs 0,
    ebeln like ekko-ebeln,
    aedat like ekko-aedat,
    bukrs like ekko-bukrs,
    bsart like ekko-bsart,
    lifnr like ekko-lifnr,
    end of i_ekko.
    data: begin of i_ekpo occurs 0,
    ebelp like ekpo-ebelp,
    matnr like ekpo-matnr,
    menge like ekpo-menge,
    meins like ekpo-meins,
    netpr like ekpo-netpr,
    end of i_ekpo.
    start-of-selection.
    select ebeln aedat bukrs bsart lifnr from ekko
    into table i_ekko where ebeln in s_ebeln.
    select ebelp
    matnr
    menge
    meins
    netpr
    from ekpo
    into table i_ekpo
    where ebeln in s_ebeln.
    control_record-mestyp = messagetyp.
    control_record-rcvprt = 'LS'.
    control_record-idoctp = idoc_name.
    control_record-rcvprn = '0MART800'.
    loop at i_ekko.
    header_segment_data-ebeln = i_ekko-ebeln.
    header_segment_data-aedat = i_ekko-aedat.
    header_segment_data-bukrs = i_ekko-bukrs.
    header_segment_data-bsart = i_ekko-bsart.
    header_segment_data-lifnr = i_ekko-lifnr.
    i_data-segnam = header_segment_name.
    i_data-sdata = header_segment_data.
    append i_data.
    select ebelp
    matnr
    menge
    meins
    netpr
    from ekpo
    into table i_ekpo
    where ebeln = i_ekko-ebeln.
    loop at i_ekpo.
    item_segment_data-ebelp = i_ekpo-ebelp.
    item_segment_data-matnr = i_ekpo-matnr.
    item_segment_data-menge = i_ekpo-menge.
    item_segment_data-meins = i_ekpo-meins.
    item_segment_data-netpr = i_ekpo-netpr.
    i_data-segnam = item_segment_name.
    i_data-sdata = item_segment_data.
    append i_data.
    endloop.
    clear i_ekpo.
    refresh i_ekpo.
    endloop.
    call function 'MASTER_IDOC_DISTRIBUTE'
    exporting
    master_idoc_control = control_record
    OBJ_TYPE = ''
    CHNUM = ''
    tables
    communication_idoc_control = i_communication
    master_idoc_data = i_data
    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.
    else.
    loop at i_communication.
    write: 'IDOC GENERATED', i_communication-docnum.
    endloop.
    commit work.
    endif.
    initialization.
    titl = 'ENTER THE PURCHASE ORDER NUMBER'.
    Regards,
    Nagaraj

  • Info-spoke extraction from ODS ending in DB error - Urgent!!!

    Hello All,
    I'm having a problem scenario where we have deltas from an ODS going to an Info-spoke. In the BADI for the Info-spoke, it has code which does a look-up on another ODS to read some fields that correspond to the target structure of the Info-spoke.
    As part of the process, it also stores some records in a custom Z-Table based on some specific-criteria.
    Given below are the observations:
    It ran successfully in Dev and in QA it ran successfully for the first time. Then on, it is failing consistently on the below error:
    Error in SQL Statement: DBIF_RSQL_INVALID_RSQL
    System error: RSDRC / FORM DATA_GET_ODS RSDRC / FORM DATA_GET_ODS RSDRC /
    Extraction Cube : Error in DataManager API.
    Please find also the consistent 'system log' message for the failure.
    "An SQL statement was executed that conflicts with a restriction on the
    database system. This restriction may be one of the following:
    - the length of the statement exceeds the permitted limit
    - the statement contains too many input variables
    - the total of the input and output values exceeds the
      buffer space for it in the database interface
    All these restrictions depend on the database. To find out which of
    these restrictions was exceeded, look at the entry in the developer
    trace that was written at the same time as this system log message. To
    view the developer trace, use transaction ST11. The message is in the
    file "dev_wi", where i stands for the number of the work process. These
    restrictions are usually only exceeded if highly dynamic statements are
    used, such as when input values are sent in RANGE tables. In this case,
    you may have to split the complex statement into multiple statements
    with smaller RANGE tables."
    The custom Z-Table mentioned earlier has technical-settings which corresponds to a table-size of 1000-10000 records. Does the system log has anything to do with the buffer allocated with some SELECT statements or with the Z-table buffer itself.
    I would really appreciate if someone could please give some pointers on the same.
    Thanks,
    -Amar

    Hello Anand Raj,
    The error says that the length of the SELECT statement is exceeded. I did go through the info-objects of the Z-Table and everything seems to be fine.
    Any other possible thoughts??...
    Thanks,
    -Amar

  • Difference bw open hub destination and info spoke ???

    Hi,
    what are difference b/w open hub destination and info spoke ???
    Thanks In advance.
    Regards
      Nitin

    Hi,
    The open hub destination is the object that allows you to distribute data from a BI system to non-SAP data marts, analytical applications, and other applications. It ensures controlled distribution across multiple systems.
    The open hub destination defines the target to which the data is transferred.
    An InfoSpoke can extract data in two ways:
    1.Full mode (F): the data corresponding to the selection criteria of the InfoSpoke is transferred from the data source into the respective destination.
    2.Delta mode (D): records that were added since the last extraction only are transferred in this mode. This is only possible for the source objects InfoCube and DataStore object.
    See the below Articles:
    InfoSpoke: Part -1
    www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/business-intelligence/g-i/infospoke%20part%201.pdf
    Open Hub Destination: Part 1
    http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/business-intelligence/m-o/open%20hub%20destination%3a%20part%201.pdf
    Open Hub Destination: Part 2
    http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/business-intelligence/m-o/open%20hub%20destination%3a%20part%202.pdf
    Thanks
    Reddy

  • Info-Spoke Capability

    Guys,
    I have a business requirement where i need to do a full data download from a cube during overnight run and deltas during intra-day run. Also based on certain business rule /  master data changes sometimes i want a full data download.
    That means the file that i am going to download from the cube is going to be either delta or full and it should be dynamic in terms of if there was any master data / business rules changes happened i need a full data download. I have already implemented this using ABAP and different tables and utilising the request based delta. But just wondering whether we can do it with info-spokes as info-spokes are SAP standards and handles the delta and has got a better monitor capability.
    As per my understanding i think we can't.
    Any brilliant ideas ????
    Thx,
    Soumya

    Hi Gopi,
    You are absolutely right. Info-spoke extraction is based on request Ids. If you go to the "delta management" in info-spoke you can see there itself. I think i have not put the question the way i wanted to and seems to be a confusion.
    Kedar & Gopi,
    Lets say you have two info-spokes, one with full update and the other one with delta. Full one have updated request 1-10. Then Can your delta one directly update request 11. Becasue both are separate and in the delta info-spoke Request 1-11 will apear for update as there was no prior update from this info-spoke.
    Please clarify.
    Thx,
    Soumya

  • In my email mailbox, I can see two line preview, but when I select the email to read it in detail, the screen is white, not email body is displayed. Any suggestions?

    In my email mailbox, I can see a two line preview, but when I select the email to read it in detail, the body of the email is a blank screen. Any suggestions?

    I'm having the same issue, and as far as I can tell, it's been happening since I downloaded the update that fixed battery issues, etc. I'm on hold with customer support, and will update here once done.

  • Problem with Info Spoke

    Dear Spoke,
    We newly upgraded our BI system to 7.0, Now when i try to transfer data to a File using an existing infospoke, iThe request runs for a long time and get fails, in the monitoring also there is no details.
    the Request runs for 3 hrs and fails, Can any one please suggest me what to do?  this problem is coming only after upgrading, Should i check any thing with support pack.
    Please provide me some solution...like general steps to handle these types of errors.
    Thanks in advance..
    Dev
    Edited by: Srinivas dev on May 7, 2008 10:18 AM

    Hi Srinivas,
    If the rest of the info spokes are working fine and if you have only this as the issue, may be as a least alternative you can activate it again and transport.
    Do you have any selections based on this IO in the info spoke or do you have any Badi logic?
    IF still Problem arises ,then look towards the support packages.
    Thanks,
    Chetan.

  • ISA Customer Details Search

    Hi Forum,
    The problem scenario as follows:
    While creating the order in ISA in BOB scenario, customer number is required to be entered. During order simulate, it shows the customer details.
    I want to know how this customer details are fetched from R/3 and the Function Module called to get the customer details.
    Thanks and Regards,
    Prashil

    Surya,
    You need Customer search in BOB scenario.
    Try to alter value in "helpvalues-config.xml" file. Find below code of line and change value there.
    <helpValuesSearch name = "Customer"
                       type = "extended"
                       description="gs.result.msg.cust.n"
                       maxRow = "20" >
    or you can change "maxhits.search.action.businesspartner" parameter value in UI Component in XCM.
    I hope you are able to resolve your issue.
    Regards.
    Ecommerce Developer.

  • Authorization issue in Info spoke

    Hi all,
    I am facing some authorization issue when executing info spoke in process chain.
    Info spoke is working fine in direct Scheduling (both background and Dialog).
    Am getting this error after execution of process chain
    "System error: RSDRC / FORM AUTHORITY_CHECK RSDRC / FORM AUTHORITY_CHECK R"
    "System error: RSDRC / FUNC RSDRC_BASIC_CUBE_DATA_GET RSDRC / FUNC RSDRC_B"
    "System error: RSDRC / FORM DATA_GET RSDRC / FORM DATA_GET RSDRC / FORM DA"
    "Extraction Cube : Error in DataManager API".
    I dont know why this problem comes.
    Can anyone tel me what went wrong and how to solve it.
    Thanks in advance.
    Kind regards,
    Shanbagavalli.S

    Hi All,
        The above issue is getting due to # character in text at end(e.g ljdfsaa##). After removing # characters in text issue got resolved.
    Thansk,
    Manjunatha

  • Error while creating Info Spoke....

    Hi,
    I am facing one problem while creating Info Spoke.I have 4 DSO which included in one Infoset & that infoset incluede in one Multiprovider. I want to creat info spoke on this Multiprovider.But when i changed the tab or at time of save & activate it gaves me error as "InfoObject ZCGNCRM2___F100 is not available in version A". I checked this info-obj.its already in active version. I reactivate it.I reactivate infoset & multiprovider also.But still exist this error.
    Please suggest me any solutuion.

    Hi Sandeep,
    Check this info object is included in any of your DSO or Info set and Multi provider.If yes check all are active or not.
    activate the info object once again using program RSDG_IOBJ_ACTIVATE and activate your Info spoke
    Check below article
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0d48577-9542-2e10-05a1-d6c1e07ea641?quicklink=index&overridelayout=true
    Regards,
    Venkatesh

  • BAPI to update customer details

    Hi All,
    What is the BAPI that we should use to update customer details into SAP??
    What are the mandatory fields we need to update customer record in SAP?
    Thx
    Navin

    Hi,
    1)
    I tried BAPI_CUSTOMER_CHANGEFROMDATA1, imported to XI. But it has the following Parameter Names and corresponding Associated Types respectively:
    PI_PERSONALDATA, PI_PERSONALDATAX, PI_OPT_PERSONALDATA, PI_OPT_PERSONALDATAX, PI_COMPANYDATA, PI_COMPANYDATAX, PI_OPT_COMPANYDATA, PI_OPT_COMPANYDATAX
    BAPIKNA101_1, BAPIKNA101_1X, BAPIKNA105, BAPIKNA105X, BAPIKNA106,BAPIKNA106X, BAPIKNA105, BAPIKNA105X.
    For the above 8, I am getting following message in XI: Schema for type urn:sap-com:document:sap:rfc:functions: BAPIKNA106 (Category Data Type) not found
    2) SD_CUSTOMER_MAINTAIN_ALL
    It is not Remote-enabled module
    3) BAPI_CUSTOMER_EDIT
    I dont I can update details of the customer...I am not sure...Because it has only Customer ID in request parameters....If I want to change name or address...how would I send them in Request  to BAPI??
    Thx
    Navin

  • To update vendor and customer details in BP transaction

    I have created a donor in the BP transaction . i need to update the vendor and customer details for the reated donor.
    please can someone suggest some BAPI's or FM's which are available to do the same.

    Hello Om,
    You can get vendor/costumer number and their names in FBL3N when you get bank ledger's line item.
    You must use BTE functions.
    I don't your techinal skills about SAP but if you don't know ABAP or ABAP dictionary details, you can get help your ABAPer.
    I will explain step by step.
    First of all, if you don't use BTE before, You must create a product on FIBF.
    Call FIBF transaction -> Settings -> Products -> ...of a customer
    Create a new line,
    Product : ZFI
    Text : BTE Products for FI Exit
    Product active : tick check fro activation.
    Then you must call SE11 for structure RFPOS.
    You must use append structure function for this structure and you can define ZFI_RFPOS append structure.
    Define 4 fields.
    Component : KUNNR - Component type : KUNNR
    Component : NAMED - Component type : NAME1
    Component : LIFNR - Component type : LINFR
    Component : NAMEK - Component type : NAME1
    Then save and active your RFPOS structure.
    After that, you must do same step for structure RFPOSX.
    Then go to SE37 and copy from SAMPLE_INTERFACE_00001650 to ZFI_INTERFACE_00001650 FM.
    After copy action, you must uncomment this line on ZFI_INTERFACE_00001650 FM's source code. It's very very important;
    E_POSTAB = I_POSTAB.
    Then you should add some ABAP code for getting customer & vendor details.
    I give you some examples, you can use it. (next message on this thread, please check)
    Then save and active FM.
    Call FIBF transaction again.
    FIBF -> Settings -> Process Modules -> ...of a customer
    Define a new line.
    Process : 00001650
    Function Module : ZFI_INTERFACE_00001650
    Product : ZFI
    and this customizing.
    Then you go to SE38 transaction.
    start report RFPOSXEXTEND. After starting, a pop-up appears, you must click YES.
    After those operations, you can see customer/vendor code and their names on FBL3N.
    I hope it helps to you.
    Regards,
    Burak.

  • Crystal Reports 2008 Customer Details Aging Report Example / Sample

    Hello!
    Anyone willing to send me a customer details aging report example for SAP Business One? (or give me a link?)
    I've been looking all over and have found examples of things, but not specifically for B1.
    Anything would be useful I am pretty flexible, I just want some bones to work from.  In return I can send you back what I build from it.
    Thanks in advance,
    Mike

    Hi Mike, you might have better  replies if you post your question to the B1 forum. They would be familiar with the B1 functioanlity and data sources.

Maybe you are looking for