Open item indicator in Billing tables

Hi Experts,
I want to know whether any indicator is available in Billing tables VBRK / VBRP if payment is not
received of that bill or apart from BSEG any other table is there where payment receipt data are getting stored.
Regards,
SP Shukla.

hello, friend.
i think you are right that collection/payment indicator is found in BSEG. since payment is done/processed in FI, it is more likely that indicator will be found in FI-related tables.
regards.

Similar Messages

GL Account open items- BSIS table

Hello All,
The standard BSIS table contains the GL Account open items. However i can find the line items for GL Accounts which are not based on "Open item management" also in this table. eg.Salary account postings from yr 2002 (All year end postings have been done appropriately). Is there any other table which can give the relevant info. ?
Any pointers to this will be highly appreciated.
Regards,
Aastha

Not sure if I have understood the question, but I will give it a try.
There are two different concepts - "Open Item Management" and "Line Item Display".
Line Item Display allows you to see from FS10N, further drill-down into FBL3N
Open Item Management allows you to see Open and Cleared Items.
Open Items are stored in tables BSIS, BSIK, BSID
Cleared Items are stored in tables BSAS, BSAK, BSAD
Over and above this, ALL documents are stored in BSEG and BKPF, irrespective of their Open Item or Line Item status.
Hope this helps.

Table for open item

What is the table for customers open item?

Hi Divya,
Table BSID is for Customer Open items
Table BSAD is for Customer Cleared/Closed items
Whilst you can use transaction code FBL5N to display either Open Items, Cleared Items or both.
I hope the above helps.
Do not forget to award the points please.
Regards,
Jacob

Difference between cleared items,open items and all postings (FI).

Hi experts,
Can anybody tell me the difference between cleared items,open items and all postings for an account.
While running corresponding bapis and transaction FAGLL03 (for GL) or FBL1N (for accounts payable) i found that in some cases all postings is less than cleared items or open items for a time period. How could it happen.According to my knowledge all postings should contain cleared items and open items.
Please correct me..
Thanks and Regards
Arjun

Hi Arjun,
For every Billing Documnet created(VBRK/VBRP-VBELN) there will be an accounting document created in BSID/BSAD tables.
OPEN ITEMS means the Billed/Invoice Amounts that are pending from Customers, i.e which we have to receive from Customers.
CLOSED ITEMS means the AMOUNTS received from that customer.
OPEN ITEMS : fetch data from BSID table Only
CLOSED ITEMS : fetch data from BSAD only.
ALL POSTINGS : fetch data from both BSID and BSAD.
Hope this will help.
Regards,
Nitin.

Customer and vendor open items

Hi All,
What is customer and vendor open items.

Hello Shailesh,
When you procure some goods from a Vendor you create a "Vendor Invoice" for it & similarly when you sell goods to a customer you create a "Customer Invoice".
So in simple accounting terms you need to pay money to a vendor & get money from a customer (i am not getting into complicated cases).
The vendor invoices for which you have not paid money are called "Vendor Open Items". Similarly the customer invoices for which you have not received money are called "Customer Open Items".
The SAP tables for this are:
BSIK --> Vendor Open Items
BSID --> Customer Open Items.
Hope this helps.
BR,
Suhas

Cleared/Open Item Symbol not Green for Cleared Items

F.13 process for clearing GR/IR matched items runs to tag documents as cleared. For some reason the Cleared/Open Item Indicator is still showing the status as "Red" for the items which are actually cleared, means the items are shown as "Open" while should be cleared and shown as "closed", this indicator should be "Green".
Any idea in what instance it can happen?

When I run the FBL3n, and pull the report for Open Items, I see these items as open while matching entry has been done manually through MR11 to clear the items. The balance shows up as zero. But for some reason the clearing document field alongwith the clearing date field is not being displayed when I display the line item. It looks like the clearing document is not being created at all. Let me know if you have some idea on that. It is GR/IR account so the account is managed as open item.

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

Comparison of open items in the Migration face to New GL

Hi
How do we check open items in the "validation phase" of the migration
cockpit? That is we what to check that the transfer of open items to
the new tables has gone OK before activating New G/L in
the "activation phase".
There is comparison reports that are available in Migration Phase where we check the status
of Open items migrated to newGL tables. But this report are not very good for getting the "Acceptance of Migration Results by Business Owner"
Pre migration the Business Owner will run reports like S_ALR_87012083, S_ALR_ 87012173 and FBL3N in the "preparation phase", so we have a picture of the situation before
migration. But we can't find any similar reports which uses FAGLEFLEX,
which we need to be able to compare data after the migration (but
before activation new G/L). For FBL3N we hoped to use FAGLL03, but this
is not possible as new G/L is not activated.
We have also tried to run /NGL/COMPARE_LEDGERS via SE38 but we can't
get the program to work this way.
So what do we do? Is the only option to created a report i ex FGI0?
Looking forward to hear for you
FYI we don't activate document splitting.
Best Regards
Torben

HI,
Please refer the below link.
http://wiki.sdn.sap.com/wiki/x/JghNCw
Regards
Madhu M

Open items date and clearing date

Hi,
Could any one tell me what are the field names in BSEG table for the "open items date" and "clearing date"?
thank u
Kaki

You should better analyze open items via secondary index tables (BSID for customers, BSIK for vendors, and BSIS for G/L accounts with open items), it would be more efficient. Those tables by design contain actual open items only.
Anyway if you have to select open items via BSEG then you should select those which have AUGBL and AUGDT fields cleared.
Another option is to use some LDB (Logical DataBase) - KDF or DDF.

GL account customization for open Item managemant

...in fsoo we set the open item management ..Tell me the t.codes for customization where we can set the g/l account setting like open item managament????
Regards
Rekha Sharma

U can mass change in tcode: MASS
Or u can view whether GLs are maintained in open item or not in table
TCode for table: SE16. In that put table name as SKB1

FSCM Dispute Open items with Special GL account (SPL GL indicator)

Hi All,
We are implementing dispute management in SAP 5.0 . When we create dispute case in FBL5n tx, a error message appears
    A dispute case must always contain at least one receivable. For example,
    you cannot inlcude only credit memos or partial payments in a
    receivables-related dispute case. Special G/L transactions are also not
    supported.
     Message number: FDM_AR008
Open items in FI-AR coming throught billing interface, and all have Special GL indicator O.
Dispute case are only possible with GL accounts and Special GL indicators arent support ?.
Does exists alternative solution?
Regards,
Eduardo

Special Gl ledger is also called as alternative recon a/c.
This is linked to Recon a/c of cusomer or vendor
This Spl gl is used for Down paymet(Advance) from cusomers or for vendors and Bill of Exachange etc.
Whenver invoce raised then the Spl gl balence is transferd aginst such invoice to normal a/c.
In Bills of Exchange when the bill is honoured then it clears the bank liability.
Assign points if usefull.
Regs,
NSB

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

Which Trans. table contain Indicator for billing plan in header

Hi All,
I wnat to find out how SAP table storage the following field:
In Sales Document Item with billing plan, the reference to the header billing plan 'check box' in the 'Billing plan' screen.
-> Indicator for billing plan in header (RV60F-KFREL)
Any, Idea?
Thanks,
Neil

Sorry Neil,
that was nonsense: I confused billing plan with installment plan: In telecom, media, utilities and other businesses with many (small) customers, you can use module contract accounting (in connection with SAP business partner). If people can't pay their bill, the company can agree on paying by installments. For this, contract accounting module uses the installment plan. This will split up the debt into slices due i.e. every month. Table fkk_instpln_head is used for this.
Regards,
Clemens

What happens to the open item in bsid table when it is cleared

hi experts,
i have a doubt about open and cleared items of accounting documents. as we know open items of customers are stored in bsid and cleared ones in bsad. For suupose, an open item is closed ina particular period then what happened to the entry in bsid and bsad table. an entry regarding is stored in bsad (cleared),and what happens to the entry in bsid, still it will be there or removed from it.

Hi,
When ever we clear the document(Complete payment) that document will be moved to BSAD table. Other wise it will remain in BSID.
If u are making partial payment then all the partial payment documents along with original document will be stored in BSID till u made the complete payment for that invoice.
Assumption is u have to give all partial payment documents made for particular invoice item while u are making complete payment in F-28 transaction. So that these partail payment documents will also be cleared while making complete payment and moved to BSAD table.
This trasaction can be used for both partial and complete payments.
Irrespective of complete or partial payments made all the documents will remain stored in BKPF and BSEG tables.
BSID and BSAD are index tables to address performance issues with BKPF and BSEG tables.
So all open and cleared documents will be there in BKPF and BSEG tables.
All cleared documents will be there in BSAD table.
Alll open documents will be there in BSID table.
Hope it is clear.
Thanks,
Vinod.

Trouble creating a open items report (BSID and BSAD tables)

Hi guys,
im creating a report that must display open items for an especific date, and i do it very well with a query from BSID table.
The problem comes when u use a date on the past, example last week.
if u do that, the items are now closed and are no longer stored in BSID table, so i think that they must be now in BSAD table, but i dont know how to relate wich ones are recently closed...
i also tried to do a query from BSAD with augdt >= last week date, and i almost get the items that i needed(this items plus the ones from BSID), but is not exactly because u can close an item with a date in the past..
is there any way to relate that 2 tables, or what exactly happens when an items change from bsid to bsad??
any ideas?

Hi;
I think the best way to recive the necessary information is using logical data base DDF. You can use report RFITEMAR to see how use the logical data base.
Some months ago I've read the data in my report in following way:
1. make Z-copy of report RFITEMAR
2. in Z-copy after end-of-selection insert
export it_pos to memory id 'POS_TABLE'.
3. In your report write a form similar to my form below:
*&      Form submit_zrfitemar
FORM submit_zrfitemar tables    rkunnr type trgr_kunnr
                                 it_pos type it_rfposxext
                       using     ibukrs type bukrs
                                 idatsd type sy-datum.
   data: rspar    type table of rsparams,
         l_rspar type rsparams,
         l_pos    type rfposxext,
         akunnr type kunnr.
   l_rspar-selname = 'DD_KUNNR'.
   l_rspar-kind    = 'S'.
   loop at rkunnr.
       move-corresponding rkunnr to l_rspar.
       if l_rspar-high = ''.
           l_rspar-option = 'EQ'.
           else.
           l_rspar-option = 'BT'.
       endif.
       append l_rspar to rspar.
    endloop.
    clear: l_rspar.
    l_rspar-selname = 'DD_BUKRS'.
    l_rspar-kind    = 'S'.
    l_rspar-sign    = 'I'.
    l_rspar-option = 'BT'.
    l_rspar-low = ibukrs.
    append l_rspar to rspar.
    clear: l_rspar.
    l_rspar-selname = 'PA_STIDA'.
    l_rspar-kind    = 'S'.
    l_rspar-sign    = 'I'.
    l_rspar-option = 'BT'.
    l_rspar-low = idatsd.
    append l_rspar to rspar.
    clear: it_pos[].
submit ZRFITEMAR
with selection-table rspar
and return.
import it_pos from memory id 'POS_TABLE'.
ENDFORM.                    " submit_zrfitemar
You find the necessary data in table IT_POS.
JS
Edited by: John Smith on Oct 9, 2008 5:42 PM

Open item indicator in Billing tables

Similar Messages

Maybe you are looking for