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

Similar Messages

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

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

Looking for SAP solution to extract data from the production system

Hello,
we are looking for the SAP standard tool to extract data from the production system and copy it to the development system. It should be as functional as some kind of partial client copy. The data, which we need to replicate is master and transactional data from FI, CO, AA MM and nice to have FS-RI modules. There is a product offered by the IntelliCorp called "Data Management" but we would like to know if SAP offers its own product.
Kind regards,
Krzysztof Murkowski

Hi,
SAP offers a solution called 'Test Data migration Server' or TDMS.
You can access the master guide from the below link:
https://service.sap.com/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700006332942006E
Cheers !!
Satya.
PS: Pls reward points if the answer was helpful...Thx.

Extraction of the open items(TC FPBW) and clear items in FI-CA(TC FPCIBW)

Dear experts,
I have a question regarding as the transaction FPBW and FPCIBW .
What i know is that these transactions tranfer the open item and clear item information from the table DFKKKO to table DFKKOPBW and DFKKCIBW.
But I would like to know whether there are some filters when these transaction SAP transfer the table from DFKKKO.
As we are adding a new document type (DFKKKO -> BLART) in the FI-CA system, I wonder whether they would be also transferted by the transaction.
Thanks in advance.

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

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

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

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......

Issue with java on production system help!

We just started getting this error when we have a portlet showing over twenty listings and a user selects the next but to view more of the list. We just wen't live this morning what could be wrong? Help
java.lang.ArrayIndexOutOfBoundsException
at javax.servlet.ServletInputStream.readLine(ServletInputStream.java, Compiled Code)
at oracle.webdb.page.PageBuilder.getMetaData(PageBuilder.java, Compiled Code)
at oracle.webdb.page.PageBuilder.process(PageBuilder.java, Compiled Code)
at oracle.webdb.page.ParallelServlet.doGet(ParallelServlet.java, Compiled Code)
at oracle.webdb.page.ParallelServlet.doPost(ParallelServlet.java, Compiled Code)
at javax.servlet.http.HttpServlet.service(HttpServlet.java, Compiled Code)
at javax.servlet.http.HttpServlet.service(HttpServlet.java, Compiled Code)
at org.apache.jserv.JServConnection.processRequest(JServConnection.java, Compiled Code)
at org.apache.jserv.JServConnection.run(JServConnection.java, Compiled Code)
at java.lang.Thread.run(Thread.java, Compiled Code)
James
null

This seems like a pretty serious issue. We have a production system up where we cannot limit PORTAL MADE REPORTS to a certain number a page. Users CANNOT click a NEXT button. We have found no way to eliminate the NEXT button on a Calendar.
We need a workaround before Feb 9.

Reg: Open items now showing in F-44

HI all,
I want clear open items using with f-44 but some of the open items are messing. i checked in FBL1N all open items are shwoing i want see all open items inf-44 how to see plz help me
with regards
JK Rao

Hi,
Please refer to
SAP Note Number 136754 - F-03, F-32, F-44, F-28 missing open items
Symptom
When you call clearing transactions (F-03, F-32, F-44) in Financial Accounting, the system displays fewer open items
than when you call up the line item display (FBL3, FBL5, FBL1).
Additional key words
FIINCON, SAPMF05A, SAPMF05B, RFEPOS00, OI, REGUP, REGUS, FBL1, line items, F-53, F-58, FB05
Cause and prerequisites
Cause: Although the missing items are actually open, these are not taken into consideration in the clearing transaction
due to other technical information in the R/3 System.
Although it may seem so at the beginning, this is usually not about a data inconsistency (exception: BSEG-XOPVW <>
X for open item account line items, see below).
Solution
Check some table fields in the missing documents using Transaction SE16. The following conditions must exist:
BSIS-XOPVW = X (Indicator: Open item management, only for G/L accounts)
BSEG-XOPVW = X (Indicator: Open item management)
BSEG-AUGBL = space (clearing document number)
BSEG-DISBN = space (discount document number)
BKPF-BSTAT = space (document status)
BKPF-XSTOV = space (indicator reversal flag)
REGUS/REGUP -> see below
Should one or more conditions not exist, please note the following information:
1. BSEG-XOPVW <> X or BSIS-XOPVW <> X for G/L account line items:
The line item presumably comes from a time before you activated the open item management of a G/L
account. Documents before this master record change do not contain this technical information. Use report RFSEPA02
if you want to bring the documents in line with the new master record. You must refer to the documentation of this
report.
Because there may be problems subsequently acivating open item management, RFSEPA02 was changed as
of Release 4.5A so that it cannot be started without modifications. SAP wants to make sure you are familiar with the
problems, which may result from activating open item management. You can however restart RFSEPA02 when you
have deactivated the line:
leave program.
1. BSEG-XOPVW <> X for open item account line items:
This data status is not allowed. Contact the SAP Hotline.
1. BSEG-DISBN <> space.
The line item has already been used within bill of exchange accounting.
1. BKPF-BSTAT <> space.
This is a document with a special function, for example a sample document or recurring entry document.
Generally these are not taken into account in clearing transactions.
1. BKPF-XSTOV <> space.
The document was flagged for reversal. Only if you cancel the reversal flag, can you clear the documentagain. You can do this by removing the planned date for the reverse posting (BKPF-STODT) in the document header
using Transaction FB02 (Change document).
1. REGUS/REGUP:
Look at table REGUS using Transaction SE16. Enter the account (KONKO) in the selection screen. If you
selected an entry, use the information Run date (LAUFD) and Identification (LAUFI) in Transaction F110 (payment
program). Check the status of the payment run. If only the proposal was carried out, the documents proposed for
payment are blocked for other clearing transactions. It is only when you delete the proposal run that the items are
taken into account again in the clearing transaction.
Rgds.

Migration of Open Items with Old/New Vendor/Customer number

Hi All,
We are currently working on conversion of Open items. We already have data extracted from legacy system.
Question : I understood that open items extract will have vendor number from legacy and conversion of vendor master will generate new vendor numbers. So what is the best way to update open items extract with new vendor numbers.
Should be done via ABAP program using custom table to store old and new vendor numbers?
What is the best approach to old/new number updation as this issue will again pop up during other conversion objects.
Any help on this will be highly appreciated.
Thanks,
Dharmesh

Hi Dharmesh
In relation to your question about what is the best approach to the old/new recoding, I donu2019t know it exactly.
One option is yours: the custom table to store old and new vendor numbers.
Another is to use the u201CSearch termu201D field in vendor master to store the old vendor number, and the ABAP program will look for the conversion in it. Furthermore in the future the user will be able to know the old code in case he/she needs to consult something in the legacy system. If you choose this option, I would recommend make this field only u201CDisplayu201D (not u201Centryu201D) in order to prevent the user from modifying it, once you have loaded the master.
Other option could be to respect the legacy vendor numbers. It depends on the goodness of the legacy coding, technical-wise. If you selected this option, you must define the number range with u201Cnumber range flagu201D = external. In this way, when you register your vendors, you have to assign the vendor number, in this case this would be the legacy code. After the vendor loading process, you have to change the u201Cnumber range flagu201D = internal, and to change the u201Ccurrent numberu201D, typing the bigger vendor number. From that moment on, the system will assign vendor numbers automatically.
I donu2019t know if I have helped you a little. If you want me to explain some aspect better, donu2019t hesitate to ask it to me.
Best regards.
PacoM

Possible to clear vendor open item against already posted payment document?

Hi
Can you advise if it is possible to clear an open item against already posted payment/clearing doc? Here is the background to the scenario:
An invoice was posted with transaction FB60. This was subsequently picked up in the payment run F110 and cleared by payment document number 200005678. The item went to the bank on the paymnet file and was paid out to the vendor. The transaction reference, which appeared on the incoming bank statemnet was the payment document number 200005678.
Subsequently it was discovered that the original invoice should have been posted with reference to a PO using MIRO. The requirement now is to reverse the paymnet documnet 200005678 in SAP, then reverse the document that was posted using FB60. After this the invoice will be posted using MIRO. This will create an open item on the vendor account.
This item will not be piad out again. Therefore the requirement is to try clear that open item against the previously posted payment document 200005678.
Is there any way to clear this vendor open item against the originally posted payment document 200005678?? Or any other advice on how this scenario can be handled in SAP?
Thank for your help.
Mike

Hi,
I tried that option in our test system. I ran FBRA and entered Paymnet Documnet Number (+Clearing Doc Number), Company Code, Fiscal Year.
Then chose menu option Clearing -> Reset Cleared Items.
The system pops up a window asking for a reversal reason and reversal date. I use 01 and posting date of today.
The system now posts another cleared document. That document places the invoice as an open item on the vendor account. It does not place the Payment Document as an open item on the account.
When I go to F-44 only the open vendor invoice is showing there. There is no open paymnet document.
Is there perhaps some configuration setting that stops the placement of the paymnet document as an open item when reset?
Thanks for your help again.

Account Statement showing that there are no open items. Just Zero

Dear friends,
My customer wants the report with showing that there are no open items. Just Zero balance on 13/08/2009 for the Tax purposes. But there are no line items done on this date.
I am trying to generate statement in F.27 but it does not give statement on date wise though I select the option (0)Open Item Statement - Daily in Customer Master data in Correspondence.
Please suggest how to get on 13/08/2009 though there is no balance/open items.
Thanks,
Venkata Raju

Hi
It may not be possible with the standard reports. The alternative way is to filter FBL5N based on date range (Posting Date Range). However, the same would work only if all the open items have been cleared in the system before your key date.Morever, your customer has to accept the SAP Format. Alternatively, you can look at the option of using balance confirmation Forms and Programs or do the procedure outside system after confirming the data from SAP by properly authorized person.
Regards
Sanil Bhandari

Possibility to restrict interest calculation on open items only

Hello All,
How to restrict calculation to Open Items only via configuration when the system calculates interest on arrears. I have checked the options for interest on arrears and there is no option to restrict via customizing.Ofcourse, there is an option to calculate interest on open item in Item interest calculation but looks like the changes made for the item interest calculation (t056UX) will not work here for t056U(calculation on arrears).
In f.2b , It is possible to exclude the cleared documents via dynamic selections as per the SAP note provided long time back. But this is only a work around.
Any suggestions to restrict via configuration for int. on arrears for open items only?
Thanks in advance....

HI!
It's used for Customer Int Calculations.
INTEREST CALCULATIONS
Ob46          Define Interest calculation
Obaa          Prepare A/c balance interest calculation
Oba4          Define Reference Interest Rates
Ob81          Define Time Depend term
Ob83          Enter Interest values
F-52          Interest calculation
          To give Effect for floating rate of Int
          Foreign currency balances revaluation
Ob59          Define valuation methods
regards,
Rup

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

Similar Messages

Maybe you are looking for