Difference between revisions of "Table llx facture fourn"

Revision as of 07:39, 21 October 2009

The documentation related to other tables is available on the page: Table SQL
La documentation relative aux autres tables est disponible sur la page: Table SQL
La documentación relativa a otras tablas se encuentra disponible en la página: Table SQL
Eine Dokumentation zu weiteren Tabellen ist auf dieser Seite verfügbar: Table SQL
与其他表相关的文档请参阅：Table SQL

Return to developer
documentation index

Retour index
Documentation développeur

Volver al índice
Documentación desarrolladores

返回
开发文档

Content/Contenu/Contenido

Contains invoices sent by providers. A provider invoice can be linked to a provider order (Table llx_commande_fournisseur) by the Table llx_element_element.

Cette table contient la liste des factures émises par les fournisseurs. Une facture fournisseur peut être liée à une commande fournisseur (Table llx_commande_fournisseur) au travers de la Table llx_element_element

Contiene las facturas emitidas por los proveedores. Una factura de proveedor puede estar enlazada con un pedido a proveedor (Table llx_commande_fournisseur) a traves de la Table llx_element_element.

Structure

Table

Version 1.1 2009/10/07

Field	Type	Null	Key	Default	Extra	Description
rowid	int(11)	NO	PRI		auto_increment	technical index
facnumber	varchar(50)	NO	UNI			invoice number
entity	int(11)	NO	UNI	1		multi company id
type	smallint(6)	NO		0		type of invoice (0=Standard invoice, 1=Replacement invoice, 2=Credit note invoice). For the moment only 0 is supported.
fk_soc	int(11)	NO	UNI			ID society (llx_societe->rowid)
datec	datetime	YES		NULL		creation date
datef	date	YES		NULL		date of invoice
tms	timestamp	NO		CURRENT_TIMESTAMP		last update date
libelle	varchar(255)	YES		NULL		label
paye	smallint(6)	NO		0		Is te invoice payed (1=yes, 0=otherwise)?
amount	double(16,8)	NO		0.00000000		amount
remise	double(16,8)	YES		0.00000000		discount
tva	double(16,8)	YES		0.00000000		VAT
total	double(16,8)	YES		0.00000000		total amount
total_ht	double(16,8)	YES		0.00000000		total amount excluding VAT
total_tva	double(16,8)	YES		0.00000000		total amount of VAT
total_ttc	double(16,8)	YES		0.00000000		total amount with VAT
fk_statut	smallint(6)	NO		0		Status of invoice (0=draft, 1=unpayed, 2=payed, 3=abandoned)
fk_user_author	int(11)	YES	MUL	NULL		ID of user author of invoice (llx_user->rowid)
fk_user_valid	int(11)	YES	MUL	NULL		ID of user validator of invoice (llx_user->rowid)
fk_projet	int(11)	YES	MUL	NULL		ID of related proyect (llx_projet->rowid)
fk_cond_reglement	int(11)	NO		1		Id of payment condition (llx_cond_reglement->rowid)
date_lim_reglement	date	YES	MUL	NULL		date limit for payment
note	text	YES		NULL		comentary
note_public	text	YES		NULL		public comentary
import_key	varchar(14)	YES		NULL		import key

Keys

Version 1.1 2009/10/07

Key	Type	Fields
PRIMARY	PRIMARY	rowid
uk_facture_fourn_ref	UNIQUE	facnumber,fk_soc,entity
idx_facture_fourn_date_lim_reglement	MULTIPLE	date_lim_reglement
idx_facture_fourn_fk_soc	MULTIPLE	fk_soc
idx_facture_fourn_fk_user_author	MULTIPLE	fk_user_author
idx_facture_fourn_fk_user_valid	MULTIPLE	fk_user_valid
idx_facture_fourn_fk_projet	MULTIPLE	fk_projet

Notes

Attention, if the status is 1 (unpayed) but the field "paye" is also 1 (payed), which should never happen under normal use, the invoice is specified payed.

Attention, si le statut est à 1 (impayée) mais le champ "paye" est à 1 également (payée), ce qui ne devrait jamais arriver dans des conditions normales d'utilisation, la facture est indiquée comme payée.

Atención, si el statut está a 1 (impagada) pero el campo "paye" está a 1 también (pagada), cosa que nunca pasa en condiciones normales de uso, la factura se indicará como pagada.

@@ Line 14: / Line 14: @@
 = Structure =
+== Table ==
+'''Version 1.1 2009/10/07'''
 {|  align="left" width="100%" border="0" rules="all" cellpadding="1" cellspacing="0"  style="margin: 0 0 1px 1px; border: 1px solid #dddddd; border-right-width: 2px; border-bottom-width: 2px; background-color: #f3f3f5"
   |style="background-color: #e9e9ef"| <b>Field</b>
@@ Line 26: / Line 27: @@
 | rowid
 | int(11)
-| &nbsp;
+| NO
 | PRI
-| NULL
+|
 | auto_increment
 | technical index
-|-
-| entity
-| int(11)
-| &nbsp;
-|
-| 1
-|
-| multi company id
 |-
 | facnumber
 | varchar(50)
 | NO
-| MUL
+| UNI
 |
 |
 | invoice number
+|-
+| entity
+| int(11)
+| NO
+| UNI
+| 1
+|
+| multi company id
 |-
 | type
@@ Line 59: / Line 60: @@
 | int(11)
 | NO
-| MUL
+| UNI
 |
 |
@@ Line 102: / Line 103: @@
 | 0
 |
-| 1 if the invoice is payed, 0 otherwise
+| Is te invoice payed (1=yes, 0=otherwise)?
 |-
 | amount
@@ Line 118: / Line 119: @@
 | 0.00000000
 |
-|
+| discount
 |-
 | tva
@@ Line 126: / Line 127: @@
 | 0.00000000
 |
-|
+| VAT
 |-
 | total
@@ Line 166: / Line 167: @@
 | 0
 |
-| 0= brouillon, 1=impayée, 2=payée, 3=abandonnée
+| Status of invoice (0=draft, 1=unpayed, 2=payed, 3=abandoned)
 |-
 | fk_user_author
@@ Line 231: / Line 232: @@
 |
 | import key
-|}
+|}&nbsp;
+== Keys ==
+'''Version 1.1 2009/10/07'''
+{|  align="left" width="100%" border="0" rules="all" cellpadding="1" cellspacing="0"  style="margin: 0 0 1px 1px; border: 1px solid #dddddd; border-right-width: 2px; border-bottom-width: 2px; background-color: #f3f3f5"
+ |style="background-color: #e9e9ef"| <b>Key</b>
+ |style="background-color: #e9e9ef"| <b>Type</b>
+ |style="background-color: #e9e9ef"| <b>Fields</b>
+|-
+| PRIMARY
+| PRIMARY
+| rowid
+|-
+| uk_facture_fourn_ref
+| UNIQUE
+| facnumber,fk_soc,entity
+|-
+| idx_facture_fourn_date_lim_reglement
+| MULTIPLE
+| date_lim_reglement
+|-
+| idx_facture_fourn_fk_soc
+| MULTIPLE
+| fk_soc
+|-
+| idx_facture_fourn_fk_user_author
+| MULTIPLE
+| fk_user_author
+|-
+| idx_facture_fourn_fk_user_valid
+| MULTIPLE
+| fk_user_valid
+|-
+| idx_facture_fourn_fk_projet
+| MULTIPLE
+| fk_projet
+|}&nbsp;
+= Notes =
 {{flag en}} Attention, if the status is 1 (unpayed) but the field  "paye" is also 1 (payed), which should never happen under normal use, the invoice is specified payed.