View source | Discuss this page | Page history | Printable version   
Toolbox
Main Page
Upload file
What links here
Recent changes
Help

PDF Books
Add page
Show collection (0 pages)
Collections help

Search

ERP/3.0/Developers Guide/Database Model/org.openbravo.model.project/C ProjectProposal

This article is protected against manual editing because it is automatically generated from Openbravo meta-data. Learn more about writing and translating such documents.
Back button.png   Back to ERP/3.0/Developers Guide/Database Model/org.openbravo.model.project


Contents

C_ProjectProposal

This table contains the following columns:

Name Nullable Data Type Description


FootNote Yes NVARCHAR (2000) Using this field you can write a text that will show on the foot of the document when you print it
HeaderNote Yes NVARCHAR (2000) Using this field you can write a text that will show on the header of the document when you print it
C_Project_ID No VARCHAR (32) Identifier of a project defined within the Project & Service Management module.
C_BPartner_ID No VARCHAR (32) A Business Partner is anyone with whom you transact. This can include a customer, vendor, employee or any combination of these.
C_Projectproposal_ID No VARCHAR (32) The ID identifies a unique proposal for the project
AD_Client_ID No VARCHAR (32) A Client is a company or a legal entity. You cannot share data between Clients.
AD_Org_ID No VARCHAR (32) An organization is a unit of your client or legal entity - examples are store, department. You can share data between organizations.
IsActive No CHAR (1) There are two methods of making records unavailable in the system: One is to delete the record, the other is to de-activate the record. A de-activated record is not available for selection, but available for reporting. There are two reasons for de-activating and not deleting records:

(1) The system requires the record for auditing purposes. (2) The record is referenced by other records. E.g., you cannot delete a Business Partner, if there are existing invoices for it. By de-activating the Business Partner you prevent it from being used in future transactions.

Created No TIMESTAMP (7) The Created field indicates the date that this record was created.
CreatedBy No VARCHAR (32) The Created By field indicates the user who created this record.
Updated No TIMESTAMP (7) The Updated field indicates the date that this record was updated.
UpdatedBy No VARCHAR (32) The Updated By field indicates the user who updated this record.
Datesend Yes TIMESTAMP (7) The date of the proposal was sent
C_BPartner_Location_ID No VARCHAR (32) The Partner address indicates the location of a Business Partner
AD_User_ID Yes VARCHAR (32) The User identifies a unique user in the system. This could be an internal user or a business partner contact
CopyFrom Yes CHAR (1) Copy lines (products) from another document of the same type.
IsSOTrx Yes CHAR (1) The Sales Transaction checkbox indicates if this item is a Sales Transaction.
Projectwon Yes CHAR (1) Award contract to project
PaymentRule Yes VARCHAR (60) Form of Payment indicates the method of payment used for this transaction (eg. cash, wire transfer, etc.)
C_PaymentTerm_ID Yes VARCHAR (32) Payment Terms identify the method and timing of payment for this transaction.
FIN_Paymentmethod_ID Yes VARCHAR (32)

Columns

Footer



top


Header Note



top


Project

Foreign key column to C_Project table, (column: C_Project_ID)

top


Business Partner

Foreign key column to C_BPartner table, (column: C_BPartner_ID)

Callout: SE_Proposal_BPartner

This column has a callout associated.

It is implemented by [1] Java Class.

top


Project Proposal



top


Client


Foreign key column to AD_Client table, (column: AD_Client_ID)

top


Organization


Foreign key column to AD_Org table, (column: AD_Org_ID) It has a validation "AD_Org Trx Security validation", with the following code

AD_Org.AD_Org_ID<> '0' AND AD_Org.IsReady='Y'

top


Active



top


Creation Date



top


Created By


Foreign key column to AD_User table, (column: AD_User_ID)

top


Updated



top


Updated By


Foreign key column to AD_User table, (column: AD_User_ID)

top


Date Sent



top


Partner Address


Foreign key column to C_BPartner_Location table, (column: C_BPartner_Location_ID) It has a validation "C_BPartner Location", with the following code

C_BPartner_Location.C_BPartner_ID=@C_BPartner_ID@

top


User/Contact


Foreign key column to AD_User table, (column: AD_User_ID) It has a validation "AD_User C_BPartner User/Contacts", with the following code

AD_User.C_BPartner_ID=@C_BPartner_ID@

top


Copy from



top


Sales Transaction



top


Project Bid Won



top


Form of Payment



List values: All_Payment Rule

The allowed values for this list are:

top


Payment Terms


Foreign key column to C_PaymentTerm table, (column: C_PaymentTerm_ID)

top


Payment Method


Foreign key column to FIN_PaymentMethod table, (column: Fin_Paymentmethod_ID) It has a validation "FIN_PaymentMethodsWithAccount", with the following code

EXISTS (SELECT 1 FROM FIN_FinAcc_PaymentMethod fapm WHERE FIN_PaymentMethod.FIN_PaymentMethod_ID=fapm.FIN_PaymentMethod_ID)

top


Other Info

Indices

These are the indices for this table (for each index there is a list of all the columns included within it):

top

Check Constraints

These are the check constraints for this table:

top

Back button.png   Back to org.openbravo.model.project

Retrieved from "http://wiki.openbravo.com/wiki/ERP/3.0/Developers_Guide/Database_Model/org.openbravo.model.project/C_ProjectProposal"

This page has been accessed 985 times. This page was last modified on 2 March 2016, at 13:09. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.