Automating the mass activity FPBW (pscd open items extraction into BW)

Hello all -
We are trying to automate the PSCD mass activity for open item extraction into bw.  We have tried using the t-code FPBW (how you would run it manually), and we have also tried using the mass activity scheduler - rfkk_ma_scheduler.  We can't get it so the key date updates each week.  Can anyone provide some guidance on how to get this automated?
Many thanks!

hi buddy,
go to SBIW go to the setting for application specificdatasourse in that go to contact account recivable, click the fileds for extrction add the field the data to see in to dffkopbw table after mass activity
regards
nag

Similar Messages

  • Extracting Open Items : Problem with mass activity FPBW

    Hi everybody,
    I need to extract Open Items in BW. I use the extractor 0FC_OP_01 which extract the content of table DFKKOPBW in OLTP. Open Items are written in table DFKKOPBW by the mass activity FPBW.
    I have a problem with this mass activity : the field "Business partner number" stay empty in table DFKKOPBW after the execution of FPBW, whereas it's not empty in table DFKKOP... (and for the cleared items it works...)
    Does anybody have a solution for my problem?
    Best regards
    Aube

    hi buddy,
    go to SBIW go to the setting for application specificdatasourse in that go to contact account recivable, click the fileds for extrction add the field the data to see in to dffkopbw table after mass activity
    regards
    nag

  • OPEN ITEMS EXTRACTION (FPBW) cancel in productive system... HELP

    Hello!
    I have received this message when I executed FPBW transaction, Open items extraction for BW... I have looked in Notes OSS but nothing... Could you helpme please? Do you have any idea what was the problem??? I think it is Basis problem in Database, but I am not sure, please it is urgent, because the error was in productive system---
    The exception must either be prevented, caught within the procedure    
    "FETCH_CURSOR"                                                        
    "(FORM)", or declared in the procedure's RAISING clause.               
    To prevent the exception, note the following:                          
    Database error text........: "ORA-01555: snapshot too old: rollback segm
    number 169 with name "_SYSSMU169$" too small"                         
    Internal call code.........: "[RSQL/FTCH/DFKKOP ]"                     
    Please check the entries in the system log (Transaction SM21).                                                                               
    You may able to find an interim solution to the problem                
    in the SAP note system. If you have access to the note system yourself,
    use the following search criteria:                                                                               
    "DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC                               
    "SAPLFKKOP03" or "LFKKOP03FR1"                                         
    "FETCH_CURSOR"

    Hi,
    How you resolved this issue?
    If you are having the solution for this please share with me as well.
    and one more thing, how can we schedule these two jobs in background for daily loading the data into DFKKCIBW and DFKKOPBW.
    Please share these two things with me.
    Thanks in advance.
    Srinivas

  • IS-U enhancing transaction FPBW (open items extraction using table DFKKOPBW

    Has anybody experiances with IS-U Accounts Receivable & payable - 'Open Items' extraction using transaction FPBW
    (which fill the table DFKKOPBW).
    1. I need to fill an custom included structure in this table (DFKKOPBW) and I am searching for the correct time (for performance reasons) & place in the (SAP) source (in the program flow) to do this.
    2. Anybody any clues on Custum/user exits in this part?
    See also function group FKKOPBW.
    Jos Reithofer

    Try this code that can search a user exit in a transaction. I got it from previous post in this forum.
    *& Report  Y_SEARCH_USEREXIT                                           *
    REPORT y_search_userexit LINE-SIZE 140 NO STANDARD PAGE HEADING.
    CONSTANTS
    *CONSTANTS: c_user_exit(22) TYPE c VALUE 'CALL CUSTOMER-FUNCTION',
    constants: c_badi(30) type c value 'CALL METHOD CL_EXITHANDLER=>',
               c_funcao_1(13) TYPE c VALUE 'CALLFUNCTION''',
               c_funcao_2(13) TYPE c VALUE 'CALL FUNCTION',
               c_include(07) TYPE c VALUE 'INCLUDE',
               c_submit(06) TYPE c VALUE 'SUBMIT',
               c_comentario TYPE c VALUE '*',
               c_ponto TYPE c VALUE '.',
               c_aspa TYPE c VALUE '''',
               c_x TYPE c VALUE 'X'.
    TABELAS INTERNAS
    DATA: BEGIN OF ti_programa OCCURS 0,
    codigo_fonte(200) type c, " LIKE rssource-line,
    END OF ti_programa.
    DATA: BEGIN OF ti_includes OCCURS 0,
    nome LIKE sy-repid,
    nivel(2) TYPE n,
    END OF ti_includes.
    DATA: BEGIN OF ti_user_exit OCCURS 0,
    programa LIKE sy-repid,
    linha(10) TYPE n,
    codigo_fonte LIKE rssource-line,
    nivel(2) TYPE n,
    END OF ti_user_exit.
    VARIÁVEIS GLOBAIS
    DATA: vg_caracter TYPE c,
    vg_palavra(50) TYPE c,
    vg_inicial LIKE sy-index,
    vg_conta_aspa TYPE n,
    vg_pname LIKE tfdir-pname,
    vg_texto(50) TYPE c,
    vg_contador LIKE sy-tfill,
    vg_nivel(2) TYPE n,
    vg_ini_contagem TYPE c, " INDICA QUE DEVE SER INICIADA A CONTAGEM
    vg_conta_espaco TYPE n. " TOTAL DE ESPAÇOS ( MÁXIMO 2 )
    PARAMETERS
    *- DADOS OBRIGATÓRIOS.
    SELECTION-SCREEN BEGIN OF BLOCK bl01 WITH FRAME TITLE tl_001 .
    selection-screen begin of line.
    selection-screen comment 1(25) tl_003.
    PARAMETERS: p_prog LIKE sy-repid.
    selection-screen end of line.
    selection-screen begin of line.
    selection-screen comment 1(25) tl_004.
    parameters: p_tcode LIKE sy-tcode.
    selection-screen end of line.
    selection-screen begin of line.
    selection-screen comment 1(25) tl_009.
    parameters: p_exit(30) TYPE c default 'CALL CUSTOMER-FUNCTION'.
    selection-screen end of line.
    SELECTION-SCREEN END OF BLOCK bl01.
    *- DADOS OPCIONAIS.
    SELECTION-SCREEN BEGIN OF BLOCK bl02 WITH FRAME TITLE tl_002.
    selection-screen begin of line.
    PARAMETERS: p_incl TYPE c AS CHECKBOX.
    selection-screen comment 4(25) tl_005.
    selection-screen end of line.
    selection-screen begin of line.
    parameters: p_func TYPE c AS CHECKBOX.
    selection-screen comment 4(25) tl_006.
    selection-screen end of line.
    selection-screen begin of line.
    parameters: p_submit TYPE c AS CHECKBOX.
    selection-screen comment 4(25) tl_007.
    selection-screen end of line.
    selection-screen begin of line.
    selection-screen comment 1(25) tl_008.
    parameters: p_nivel(2) TYPE n.
    selection-screen end of line.
    SELECTION-SCREEN END OF BLOCK bl02.
    initialization.
      tl_001 = 'Program Selection'.
      tl_002 = 'Search Depth'.
      tl_003 = 'Program Name'.
      tl_004 = 'Transaction Code'.
      tl_005 = 'Process INCLUDEs'.
      tl_006 = 'Process FUNCTION MODULEs'.
      tl_007 = 'Process SUBMITs'.
      tl_008 = 'Depth level'.
      tl_009 = 'Search string'.
    INÍCIO
    START-OF-SELECTION.
    *- CONSISTÊNCIAS DOS PARÂMETROS.
      PERFORM consisti_parametros.
    *- INICIALIZA TABELA.
      PERFORM inicializa_tabela.
    *- VERIFICA SE NO PROGRAMA EXISTE ALGUM INCLUDE,FUNÇÃO OU SUBMIT.
      PERFORM verifica_include_funcao_submit.
    *- ANALISA OS INCLUDES E PROCURA POR USER EXIT.
      PERFORM procura_user_exit.
    *- EXIBE TODAS USER EXIT ENCONTRADAS.
      PERFORM exibe_user_exit.
    FIM
    END-OF-SELECTION.
    *& Form PROCURA_USER_EXIT
    text
    --> p1 text
    <-- p2 text
    FORM procura_user_exit.
    *- VERIFICA SE NOS INCLUDES SELECIONADOS EXISTEM USER EXITS.
      LOOP AT ti_includes.
    *- ESVAZIA TABELA INTERNA.
        REFRESH ti_programa.
    *- REALIZA LEITURA DO INCLUDE ARMAZENANDO-O EM TABELA INTERNA
        READ REPORT ti_includes-nome INTO ti_programa.
        LOOP AT ti_programa.
    *- VERIFICA SE NA LINHA DO PROGRAMA EXISTE ALGUM INCLUDE.
          SEARCH ti_programa-codigo_fonte FOR p_exit.
    *- SE ENCONTROU INCLUDE E SE A LINHA NÃO ESTÁ COMENTADA...
          IF sy-subrc EQ 0
          AND ti_programa-codigo_fonte+0(1) NE c_comentario.
            CLEAR ti_user_exit.
    *- REMOVE ESPAÇOS NO INÍCIO DA STRING.
            SHIFT ti_programa-codigo_fonte LEFT DELETING LEADING space.
            MOVE: ti_includes-nome TO ti_user_exit-programa,
            sy-tabix TO ti_user_exit-linha,
            ti_programa-codigo_fonte TO ti_user_exit-codigo_fonte,
            ti_includes-nivel TO ti_user_exit-nivel.
            APPEND ti_user_exit.
          ENDIF.
        ENDLOOP.
      ENDLOOP.
    ENDFORM. " PROCURA_USER_EXIT
    *& Form EXIBE_USER_EXIT
    text
    --> p1 text
    <-- p2 text
    FORM exibe_user_exit.
      PERFORM cabecalho.
      PERFORM user_exit_nao_encontrada.
      PERFORM lista_user_exit_encontrada.
      PERFORM rodape.
    ENDFORM. " EXIBE_USER_EXIT
    *& Form PROCURA_INCLUDE
    text
    --> p1 text
    <-- p2 text
    FORM procura_include.
      CLEAR vg_palavra.
    *- VERIFICA SE NA LINHA DO PROGRAMA EXISTE ALGUM INCLUDE.
      SEARCH ti_programa-codigo_fonte FOR c_include.
    *- SE ENCONTROU INCLUDE E SE A LINHA NÃO ESTÁ COMENTADA...
      IF sy-subrc EQ 0
      AND ti_programa-codigo_fonte+0(1) NE c_comentario.
    *- VERIFICA TODOS OS 72
        DO 72 TIMES.
          vg_inicial = sy-index - 1.
          MOVE ti_programa-codigo_fonte+vg_inicial(1) TO vg_caracter.
          IF NOT vg_caracter IS INITIAL.
    *- VERIFICA SE NÃO É FIM DO COMANDO.
            IF vg_caracter EQ c_ponto.
              EXIT.
            ENDIF.
    *- MONTA PALAVRA.
            CONCATENATE vg_palavra vg_caracter INTO vg_palavra.
    *- CONVERTE PARA MAÍUSCULA PARA FUTURA COMPARAÇÃO.
            TRANSLATE vg_palavra TO UPPER CASE.
    *- SE ENCONTROU ALGUM INCLUDE
            IF vg_palavra EQ c_include.
              CLEAR vg_palavra.
            ENDIF.
          ENDIF.
        ENDDO.
    *- SALVA NOME DO INCLUDE P
        READ TABLE ti_includes WITH KEY nome = vg_palavra.
        IF NOT sy-subrc IS INITIAL.
          IF vg_nivel LE p_nivel.
            MOVE: vg_palavra TO ti_includes-nome,
            vg_nivel TO ti_includes-nivel.
            APPEND ti_includes.
          ENDIF.
        ENDIF.
      ENDIF.
    ENDFORM. " PROCURA_INCLUDE
    *& Form PROCURA_FUNCAO
    text
    --> p1 text
    <-- p2 text
    FORM procura_funcao.
      CLEAR: vg_conta_aspa,
      vg_palavra.
    *- VERIFICA SE NA LINHA DO PROGRAMA EXISTE ALGUM INCLUDE.
      SEARCH ti_programa-codigo_fonte FOR c_funcao_2.
    *- SE ENCONTROU INCLUDE E SE A LINHA NÃO ESTÁ COMENTADA...
      IF sy-subrc EQ 0
      AND ti_programa-codigo_fonte+0(1) NE c_comentario.
    *- VERIFICA TODOS OS 72
        DO 72 TIMES.
          vg_inicial = sy-index - 1.
          MOVE ti_programa-codigo_fonte+vg_inicial(1)
          TO vg_caracter.
          IF NOT vg_caracter IS INITIAL.
    *- VERIFICA SE NÃO É FIM DO COMANDO.
            IF vg_caracter EQ c_aspa.
              ADD 1 TO vg_conta_aspa.
              IF vg_conta_aspa EQ 2.
                EXIT.
              ENDIF.
            ENDIF.
    *- MONTA PALAVRA.
            CONCATENATE vg_palavra vg_caracter INTO vg_palavra.
    *- CONVERTE PARA MAÍUSCULA PARA FUTURA COMPARAÇÃO.
            TRANSLATE vg_palavra TO UPPER CASE.
    *- SE ENCONTROU ALGUM INCLUDE
            IF vg_palavra EQ c_funcao_1.
              CLEAR vg_palavra.
            ENDIF.
          ENDIF.
        ENDDO.
    *- PESQUISA NOME DA FUNÇÃO PARA FUTURA PESQUISA POR USER EXIT.
        CLEAR vg_pname.
        SELECT SINGLE pname
        INTO vg_pname
        FROM tfdir
        WHERE funcname EQ vg_palavra.
        IF sy-subrc EQ 0.
          READ TABLE ti_includes WITH KEY nome = vg_pname.
          IF NOT sy-subrc IS INITIAL.
            IF vg_nivel LE p_nivel.
              MOVE: vg_pname TO ti_includes-nome,
              vg_nivel TO ti_includes-nivel.
              APPEND ti_includes.
            ENDIF.
          ENDIF.
        ENDIF.
      ENDIF.
    ENDFORM. " PROCURA_FUNCAO
    *& Form VERIFICA_INCLUDE_FUNCAO_SUBMIT
    text
    --> p1 text
    <-- p2 text
    FORM verifica_include_funcao_submit.
      LOOP AT ti_includes.
        ADD 1 TO vg_contador.
        DESCRIBE TABLE ti_includes.
        PERFORM evitar_time_out USING sy-tfill.
        MOVE ti_includes-nivel TO vg_nivel.
        ADD 1 TO vg_nivel.
    *- ESVAZIA TABELA INTERNA.
        REFRESH ti_programa.
        READ REPORT ti_includes-nome INTO ti_programa.
        LOOP AT ti_programa.
    *- PROCURA POR INCLUDES.
          IF p_incl EQ c_x.
            PERFORM procura_include.
          ENDIF.
    *- PROCURA POR FUNÇÃO.
          IF p_func EQ c_x.
            PERFORM procura_funcao.
          ENDIF.
    *- PROCURA POR SUBMIT.
          IF p_submit EQ c_x.
            PERFORM procura_submit.
          ENDIF.
        ENDLOOP.
      ENDLOOP.
    ENDFORM. " VERIFICA_INCLUDE_FUNCAO_SUBMIT
    *& Form EVITAR_TIME_OUT
    text
    -->P_SY_TFILL text
    -->P_SY_SUBRC text
    FORM evitar_time_out USING p_sy_tfill.
      DATA: vl_total(10) TYPE n,
      vl_atual(10) TYPE n.
      MOVE: p_sy_tfill TO vl_total,
      vg_contador TO vl_atual.
      CONCATENATE 'Total:' vl_total '-' 'Atual:' vl_atual
      INTO vg_texto
      SEPARATED BY space.
      CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
        EXPORTING
          text = vg_texto.
    ENDFORM. " EVITAR_TIME_OUT
    *& Form PROCURA_SUBMIT
    text
    --> p1 text
    <-- p2 text
    FORM procura_submit.
      CLEAR: vg_conta_espaco, vg_palavra, vg_ini_contagem.
    *- VERIFICA SE NA LINHA DO PROGRAMA EXISTE ALGUM INCLUDE.
      SEARCH ti_programa-codigo_fonte FOR c_submit.
    *- SE ENCONTROU INCLUDE E SE A LINHA NÃO ESTÁ COMENTADA...
      IF sy-subrc EQ 0
      AND ti_programa-codigo_fonte+0(1) NE c_comentario.
    *- VERIFICA TODOS OS 7
        DO 72 TIMES.
          vg_inicial = sy-index - 1.
          MOVE ti_programa-codigo_fonte+vg_inicial(1) TO vg_caracter.
          IF vg_ini_contagem EQ c_x AND vg_caracter IS INITIAL.
            ADD 1 TO vg_conta_espaco.
          ENDIF.
          IF NOT vg_caracter IS INITIAL.
            MOVE c_x TO vg_ini_contagem.
            IF vg_caracter EQ c_ponto.
              EXIT.
            ENDIF.
    *- MONTA PALAVRA.
            IF vg_conta_espaco LT 2.
              CONCATENATE vg_palavra vg_caracter INTO vg_palavra.
    *- CONVERTE PARA MAÍUSCULA PARA FUTURA COMPARAÇÃO.
              TRANSLATE vg_palavra TO UPPER CASE.
    *- SE ENCONTROU ALGUM INCLUDE
              IF vg_palavra EQ c_submit.
                CLEAR vg_palavra.
              ENDIF.
            ELSE.
              EXIT.
            ENDIF.
          ENDIF.
        ENDDO.
    *- PESQUISA NOME DA FUNÇÃO
        READ TABLE ti_includes WITH KEY nome = vg_palavra.
        IF NOT sy-subrc IS INITIAL.
          IF vg_nivel LE p_nivel.
            MOVE: vg_palavra TO ti_includes-nome,
            vg_nivel TO ti_includes-nivel.
            APPEND ti_includes.
          ENDIF.
        ENDIF.
      ENDIF.
    ENDFORM. " PROCURA_SUBMIT
    *& Form CONSISTI_PARAMETROS
    text
    --> p1 text
    <-- p2 text
    FORM consisti_parametros.
      IF p_nivel IS INITIAL.
        MOVE 1 TO p_nivel.
      ENDIF.
      IF p_prog IS INITIAL AND p_tcode IS INITIAL.
    *- NOME DO PROGRAMA E NOM
    *- DEVE SER INFORMADO.
        MESSAGE ID 'ZF' TYPE 'I' NUMBER '000' WITH text-003.
        STOP.
      ENDIF.
      IF NOT p_prog IS INITIAL AND NOT p_tcode IS INITIAL.
    *- SOLICITA AO U
        MESSAGE ID 'ZF' TYPE 'I' NUMBER '000' WITH text-004.
        STOP.
      ENDIF.
    ENDFORM. " CONSISTI_PARAMETROS
    *& Form INICIALIZA_TABELA
    text
    --> p1 text
    <-- p2 text
    FORM inicializa_tabela.
      DATA vl_pgmna LIKE tstc-pgmna.
      REFRESH ti_includes.
      IF NOT p_prog IS INITIAL.
        MOVE: p_prog TO ti_includes-nome,
        '0' TO ti_includes-nivel.
        APPEND ti_includes.
      ELSEIF NOT p_tcode IS INITIAL.
        SELECT SINGLE pgmna
        FROM tstc
        INTO vl_pgmna
        WHERE tcode EQ p_tcode.
        IF sy-subrc EQ 0.
          MOVE: vl_pgmna TO ti_includes-nome,
          '0' TO ti_includes-nivel.
          APPEND ti_includes.
        ENDIF.
      ENDIF.
    ENDFORM. " INICIALIZA_TABELA
    *& Form CABECALHO
    text
    --> p1 text
    <-- p2 text
    FORM cabecalho.
      DATA vl_complemento(50) TYPE c.
      IF p_tcode IS INITIAL.
        CONCATENATE '(Program)' p_prog
        into vl_complemento
        SEPARATED BY space.
      ELSE.
        CONCATENATE '(Transaction)' p_tcode
        INTO vl_complemento
        SEPARATED BY space.
      ENDIF.
      FORMAT COLOR COL_KEY.
      WRITE: /001 sy-uline,
      /001 sy-vline,
      040 'User Exits in a Program',
      vl_complemento,
      140 sy-vline,
      /001 sy-uline.
      WRITE: /001 sy-vline,
      003 'Program Name',
      044 sy-vline,
      046 'Level',
      052 sy-vline,
      054 'Lineno',
      065 sy-vline,
      067 'UserExit',
      140 sy-vline,
      /001 sy-uline.
    ENDFORM. " CABECALHO
    *& Form USER_EXIT_NAO_ENCONTRADA
    text
    --> p1 text
    <-- p2 text
    FORM user_exit_nao_encontrada.
      DESCRIBE TABLE ti_user_exit.
      CHECK sy-tfill IS INITIAL.
      FORMAT COLOR COL_NORMAL INTENSIFIED ON.
      WRITE: /003 'Userexit does not exist',
      139 ' '.
      FORMAT RESET.
    ENDFORM. " USER_EXIT_NAO_ENCONTRADA
    *& Form LISTA_USER_EXIT_ENCONTRADA
    text
    --> p1 text
    <-- p2 text
    FORM lista_user_exit_encontrada.
      DATA vl_cor TYPE c.
      LOOP AT ti_user_exit.
        IF vl_cor EQ c_x.
          CLEAR vl_cor.
        ELSE.
          MOVE c_x TO vl_cor.
        ENDIF.
    *- AJUSTA COR NA TELA.
        IF vl_cor EQ c_x.
          FORMAT COLOR COL_NORMAL INTENSIFIED ON.
        ELSE.
          FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
        ENDIF.
    *- INÍCIO DA IMPRESSÃO.
        WRITE: /003 ti_user_exit-programa,
        046 ti_user_exit-nivel,
        054 ti_user_exit-linha,
        067 ti_user_exit-codigo_fonte,
        139 ' '.
      ENDLOOP.
    ENDFORM. " LISTA_USER_EXIT_ENCONTRADA
    *& Form RODAPE
    text
    --> p1 text
    <-- p2 text
    FORM rodape.
      DESCRIBE TABLE ti_includes.
      FORMAT COLOR COL_TOTAL.
      WRITE: /001 sy-uline,
      /001 sy-vline,
      003 'Total include searched:', sy-tfill,
      ' - with level:', p_nivel,
      140 sy-vline,
      /001 sy-uline.
    ENDFORM. " RODAPE

  • Invoice documents not created in the mass activity

    Hello SDN,s
    The invoices(Print documents) have not been created through mass job in the EA29 transaction code.
    When we run the job for mass invoice in EA29, the invoices have not been created and able to create the invoices in the EASIBI transaction code.
    I have created billing documents and trying to create the invoices in EA29 transaction code and getting the error like no documents created in the application.
    Could you please guide me why the invoices are not getting created in the EA29 and where do i check to resolve the issue.
    Please advice.
    Regards,
    KV

    Hi KV:
    The mass activity IS-U for invoice creation is tx. EA26, tx. EA29 is the paralell mass printout IS-U, but first you must create the invoice document with EA26 and then print it with EA29.
    Here's a list of some IS-U Billing transactions
    EASIBI Create Individual Bill
    EA00 Test Billing of a Contract
    EA13 Print/Billing Document Reversal
    EA14 Print/Billing Document Reversal
    EA15 Reversal of Invoicing Documents
    EA16 Create Manual Backbilling
    EA17 Change Manual Backbilling
    EA18 Display Manual Backbilling
    EA19 Create Bill (Individual Creation)
    EA20 Reverse Billing Document
    EA21 Adjustment Reversal Billing Docs
    EA22 Display Billing Document
    EA22_TOOL Billing Tool
    EA24 Delete Adj. Reversal frm Bill.Order
    EA25 Create Partial Bill (Individual)
    EA26 Mass Processing: Create Bill
    EA27 Mass Processing: Create Partial Bill
    EA28 Mass Process.: Request BB Amounts
    EA29 Mass Processing: Bill Printout
    EA29_AGGRBILL Print Aggregated Bill
    EA33 Mass Processing: Bill Reversal
    EA34 Mass Processing: Full Reversal
    EA38 Mass Activity: Billing
    EA39 Mass Activity: Billing Simulation
    EA40 Display Print Document
    EA55 Display Rate Cat.
    EA56 Maint. Rate Type
    EA57 Create Budget Billing Change Doc.
    EA58 Mass Activity: Coll. Bill Printout
    EA59 Print Collective Bill (Old)
    EA60 Print Invoicing Document
    EABI Billing/Invoicing log display
    EABICO Bill Correction
    EABIH Archive Billing Document Headers
    EABIL Archive Billing Document Line Items
    EABR IS-U Billing
    EAIN Billing/Invoicing log display
    EAMABI Mass Billing
    EAMASI Mass Billing Simulation
    EAMS00 Mass Billing of Simulation Indexes
    EAMS01 Mass Act.: Billing of Sim. Indexes
    EATR Mass Activity: Create Bill/Part.Bill
    EAXX IS-U Billing
    EA_DOWNLOAD Download Billing Master Data
    I hope this will be helpful.
    Regards,
    David

  • Foreign Currency Valuation - GL at the time of clearing of open items

    Hi experts,
    We valuate the open items (Balance sheet items) in Company Code Currency without checking the reversal option.
    At the time of clearing of these open items, the GL used for reversal of the valuation difference is been different.
    GL mapped in OBA1:
    Exch.rate diff realized
    Loss/Gain: 716000
    Valuation: Loss/Gain - 716001
    Bal.Adj 1: 101699
    Translation:
    Loss/Gain: 716000
    Bal.sheet adj -Loss/Gain: 716001
    At the time of clearing of open items:
    The entry which is getting passed for the reversal of the valuation difference is some time posted to GL: 101699 and sometime to GL 716000. The off-setting GL been Clearing GL(which is been valuated).
    Could someone kindly through some light as to why the system behaving in such a way. We expect the GL at the time of reversal to be 101699.
    Thanks in advance.

    Hi Pradeep,
    The principle of foreign currency revaluation works as follows for the open items like AR, AP and Bank Balances:
    At the period end the system revaluates the open items (or balances, as the case may be) with the period end exchange rate and thus posts the difference between the original exchange rate (at the time the open item was created) and the period end rate. This could be loss or gain due to revaluation. One side of the entry is P&L (7...account) and the other side is the balance sheet (the balance sheet account typically comes from AR, AP or Bank/Cash range).
    This loss or gain is not realized since at the period end the open item is still out there. When you clear the open item, the loss or gain due to the latest exchange rate is realized immediately and is posted to realized loss or gain, with an offset to the original balance sheet account.
    I hope the above helps.
    Sharabh

  • Mass change on vendor open item.

    Hi
    We have a requirement to change the payment terms for all vendor open items to 60 days, to do mass change i selected few open documents and click on enviornment and mass change and new values but here payment terms field is not there.
    I thought i need to add to the line layout under special fields then i did that even then payment terms are not showing under mass change > new values field under environment but showing as line layout.
    Is there a way to solve this as we may have more than 100,000 open documents for all vendors within the company code.
    Will assign good points.
    Thanks
    Kum

    Hi
    there is no need of payment term to be changed.
    If the Payment term is Payable immediately Due net or Blank in the Open Item, simply change the Base Line date for each open item,give date as of 60th day.then system will pick those line items only after 60 days.
    Go for LSMW or BDC to Update the field in those line items.
    Regards
    Venkat

  • How to ensure that an accrual (FBS1) that was cleared and reversed/reset (FBRA) does not affect the books while being in open items (FAGLB03)?

    At first the user created an accrual using FBS1 for reversal on 5/1/2015.
    This created a clearing document.
    Then it was mistakenly reversed by the user for 5/1/2015 by using F.81
    This also created a clearing document.
    Based on advice in the following thread: Delete reverse accrual/defferal documents | SCN ,
    the user used FBRA to reset and reverse the document. We are unsure if the reset and reverse command was used or just the reset choice.
    Now the accrual value is in the respective accounts with an open status (i.e. red button). Does this mean that the entry has already been discarded and it won't affect the accounts? Or does one then use FB50 to reverse the effects of the accrual in the current and next month?

    Hi
    I guess that the user has not reverse the transaction as its still shows as open item in 30 /4 .. so I belive that you need to use fb50 or simply use FBR2 and enter the original entry no and the choose (generate reversal posting option )..
    regards
    mahmoud el nady

  • F-58: Restrict the selection of no. of open items

    Is it possible to restrict the number of selected open items (to a max of 10 items at a time) in F-58 transaction?

    Can't be restricted.

  • Open Items Extraction takes too much time

    Hi,
    i'm using FPBW to generate Open Items data for BW. This program is takeing up to 12 hours to run. I found and applied notes
    Note 793692 - FPBW: Performance problems
    Note 795182 - FPBW - Performance during selection of dunning data
    but the increased the process time.
    does anyone knows something to do, in order to optimize FPBW processing time.?
    thanks
    Mauricio

    Paolo,
    thanks for the suggestions. I just checked them, put they doesnt seem to apply. FPBW processing is waht I need to boost!.
    These notes talk about deletion of old extractions and delta enablement.
    thans again.
    Mauricio.

  • OPen Items Extraction

    Hi All
    I am extracting Open items data,while extracting  data i ran a tcode fpbw in r3 side.Job was showing green in sm37. Data came into table.But when i saw in tcode:fpbws here  reqest was showing in red colour.
    How to solve this problem...and y it is showing in red colour...
    i saw application logs...there logs are there but there is no process status for particular logs...

    Hi Chang,
    What is the error it is showing in FPBWS? Please elaborate as it shud not happen if FPBW is running fine with date ID and Identification and FPBWS is throwing errors.
    Sunil

  • Open items extract and upload

    Hi
       We are into merging of two company codes 1300 & 1000 which are in of same client, can anyone explain how to move all the open items (Vendor/Customer/GL) in co code 1300 to co code 1000 using LSMW.... and table to view for all those three types of open items... and how to move the open items so that balances in co code 1300 will be Zero...
    Thanks
    Charan

    Try the table name BSIK for Vendor and for customer BSID
    LSMW upload for Vendor and Customer Open items chk this link......

  • Change GL Account from Open Item Managed into non-Open Item Managed

    In the former R3 environments, release 4.6 there was the program RFSEPA03 to turn off open item management.
    However, in ECC 6.0 this program is blocked and there seems to be no possibility to change a GL account back to non-open item mgt.
    Please comment,
    Kind Regards WR

    Yes .. I Agree with you ...
    Actually I accidently, did not check the GL first, but run the ZRFSEPA02 first .... because of that, my GL is check as an open item and as a recon account too ...
    any solutions ?

  • FI-CA open items extraction

    Hello all,
    i have to extract open items using 0fc_op_01 datasource using custom delay (0-14 / 15-45, etc.) values. the problem is that the customers wants the delay being computed by keydt (key date of open items- in dfkkopbw table) and bldat fields...bldat would be ok (in dfkkop table), but keydt field isn't in the table dfkkop so i cannot add it in the customizing view v_tbdls for the open items.
    Does anybody know a workaround?
    Thankfully,
    Tudor

    Hello Tudor,
         You have to calculate the  open items in the query you create on the cube based on the key date customer enters.
    See the example below.
    http://help.sap.com/saphelp_bw33/helpdata/en/ac/b2ae397f768c3ce10000000a11402f/content.htm
    There are number of posts with details  in this forum too on how to calculate open items in the query.
    Jaya

  • Can you remove the new CS4 "docking" of open items?

    CS4 has a way of automatically docking every file you open which I HATE.  Is there a way to have things open in their own windows that can be individually like CS3 and every other one before it would do?

Maybe you are looking for

  • Error "Item 000010 does not exist" while creating sales order in VA01

    Dear All, As per customer requirement we are trying to validate shipping data( item level) and unloading point( item level)  by customer enhancement. Enhancement:       V45A0003 Function Module:    EXIT_SAPMV45A_003 INCLUDE:                ZXVVAU05 I

  • How do you install a backed up hard drive?

    Hi Guys, I recently had my hard drive expire on my G5 I have a back up of all data and applications that is on an external hard drive. How do I now install this back on to my G5 and its new hard drive? Is it as simple as drag and drop? Do I have to r

  • Chart and filter button missing

    when I insert a query in a workbook the chart and filter button are missing.  We are using netweaver 2004s.  is there a way to have them display?

  • Deleting Reservations from MCHB

    Hi I have an issue related to the batch determination in the process orders. The reason for this known, batch archiving is not done. We tried to archive the batches but were able to archive only 45-50% of the total batches. Most of the errors we rece

  • RSV4000 - version 1 or version 2

    Hi, Any idea how to find out if I have version 1 or 2 of the RSV 4000 router? I want to upgrade the firmware and need to be able to find this information. Plus, any idea what the differences are between v1 and v2? Many thanks. Mark