[Comxe-cvslog] Trifon-HG-ERP/doc info.txt,1.4,1.5

[Trifon N. T. <tri...@us...>]

Update of /cvsroot/comxe/Trifon-HG-ERP/doc
In directory sc8-pr-cvs4.sourceforge.net:/tmp/cvs-serv27535/doc

Modified Files:
	info.txt 
Log Message:
added eclipse launch configuration

Index: info.txt
===================================================================
RCS file: /cvsroot/comxe/Trifon-HG-ERP/doc/info.txt,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** info.txt	6 May 2008 13:02:38 -0000	1.4
--- info.txt	15 Jun 2008 13:32:40 -0000	1.5
***************
*** 15,19 ****
  -05) Account Entry to have:
       Campaign
!      Trx. Organization
       Location From
       Location To
--- 15,19 ----
  -05) Account Entry to have:
       Campaign
!      Trx. Organization Not sure how this can be used! Have to research in Adempiere!
       Location From
       Location To
***************
*** 34,37 ****
--- 34,38 ----
         this.getSearchKey() + ' ' + this.getName() or searchKey + ' ' + name
         this.getSearchKey() + '-' + this.getEAN()  or searchKey + '-' + ean
+        product.name + ' [' + product.key + ']'
       How to add custom columns and expression language to recognize this column?... TODO.
         Probably we must have standard interface? 
***************
*** 42,53 ****
  -08) Create Document Interface........ TODO
       Probably we can reuse Document from Java Content Repository or other Specification?
       Should we have standard method like: complete(), close(), reverse() or have more general method changeStatus(newStatus) throws Exception?
       Probably we must have some default states: Prepared, Completed, Closed, Invalid
  -09) Create Document Transition Interface..... TODO
       Idea is to have standard way which allows to transfer data(custom columns) from one document to another Document.
  -10) Research how Rule Engines can be used?... TODO
  -11) Mandatory columns:
!      C_Tenant_ID
!      C_Org_ID
       DateCreated
       DateUpdated
--- 43,62 ----
  -08) Create Document Interface........ TODO
       Probably we can reuse Document from Java Content Repository or other Specification?
+        Alfresco ECM has very good model and good documentation. It supports model driven design.
       Should we have standard method like: complete(), close(), reverse() or have more general method changeStatus(newStatus) throws Exception?
+        Probably we need to have fields: currentStatus and nextStatus? But isn't it supposed this fields to be part of the Workflow?
+        How the workflow engine know which is the current state and which must be next state?
       Probably we must have some default states: Prepared, Completed, Closed, Invalid
+      Probably we can use Visitor Design Patter inorder to generate Account postings for each document? TODO.
  -09) Create Document Transition Interface..... TODO
       Idea is to have standard way which allows to transfer data(custom columns) from one document to another Document.
+       I think that this would be very useful!
+       For example to create Purchase Order from Sales Order. Most of the fields are only copied from purchase order to sales order.
  -10) Research how Rule Engines can be used?... TODO
  -11) Mandatory columns:
!      C_Holding_ID/C_Tenant_ID...
!      ??? C_Company_ID ???....... 
!      C_Org_ID................... 3 level structure
!      C_Department_ID............ 4 level structure
       DateCreated
       DateUpdated
***************
*** 56,64 ****
       SearchKey
       Name
!      Description
       UniqueIndex - number. Multiple unique columns.
! -12) If new ERP would be created then it must integrate with already existing packages on the market. 
       Like POS applications, Commerce applications.
! -13) 
  
  
--- 65,78 ----
       SearchKey
       Name
!      Description/Comment
!      Help
       UniqueIndex - number. Multiple unique columns.
!        C_Tenant_ID, SearchKey usually will form unique index. We can have Business Partners with the same key in different Tenants. 
! -12) If new ERP would be created then it must integrate with already existing packages on the market.
       Like POS applications, Commerce applications.
!      It must be able to import data from existing ERP systems.
! -13) Sales Order must have Ordering B.Partner, Bill/Invoice B.Partner, Ship B.Partner
!      Sales Order must have Ordering Location, Bill/Invoice Location, Ship Location
! -14)