Difference between revisions of "HOWTO Process Documents"

From ADempiere
Jump to: navigation, search
This Wiki is read-only for reference purposes to avoid broken links.
m
Line 25: Line 25:
 
* About the [[Default_Accounts_Usage|usage of DEFAULT_ACCOUNTS]] - these are special accounts from the Chart Of Accounts, which are bound in the source code to standard processes. So the posting of mainstream activities is backed up and automated.  
 
* About the [[Default_Accounts_Usage|usage of DEFAULT_ACCOUNTS]] - these are special accounts from the Chart Of Accounts, which are bound in the source code to standard processes. So the posting of mainstream activities is backed up and automated.  
 
'''Note that all the examples given include accounts from the American COA which comes along with the ADempiere installation.'''
 
'''Note that all the examples given include accounts from the American COA which comes along with the ADempiere installation.'''
* Generally there are '''16''' ''model classes'' describing the behavior of the '''36''' active ''Document Types'' and corresponding to '''15''' ''document classes'' at the server side application (responsible for posting the documents). The mapping between the classes and their corresponding document types are provided in the following table.
+
* Generally there are '''16''' ''model classes'' describing the behavior of the '''36''' active ''Document Types''.
 +
* Concerning ''accounting'' there are '''15''' ''document classes'' which are responsible for posting the documents. The mapping between the classes and their corresponding document types are provided in the following table.
 +
* When we talk about automatic generation of documents the consequent documents in the corresponding workflow should be minded, and the automation is provided by the workflow itself. That means with the completion of a single document the set of connected documents is generated and posted in a sequence. The automatic generation is not when we use certain form to choose from which document to produce other type.
  
 
{| border="1" align="center"
 
{| border="1" align="center"
 
|+ ADempiere Model classes and their corresponding Document Types
 
|+ ADempiere Model classes and their corresponding Document Types
! width="200" | Model class !! width="200" | Document Class !! width="300" | Document Types
+
! width="200" | Model class !! width="300" | Document Type !! width="200" | Document-Posting Class
 
|-
 
|-
 
| MAllocationHdr
 
| MAllocationHdr
 +
|
 
| Doc_Allocation
 
| Doc_Allocation
|
 
 
|-
 
|-
 
| MBankStatement
 
| MBankStatement
| Doc_Bank
+
|
|  
+
| Doc_Bank
 
|-
 
|-
 
| MCash
 
| MCash
 +
|
 
| Doc_Cash
 
| Doc_Cash
|
 
 
|-
 
|-
 
| MInOut
 
| MInOut
|
 
 
| [[DocType_Material_Receipt|MM Material Receipt]]<br/>[[DocType_Shipment|MM Shipment]]<br/>MM Shipment Indirect<br/>MM Shipment with Pick
 
| [[DocType_Material_Receipt|MM Material Receipt]]<br/>[[DocType_Shipment|MM Shipment]]<br/>MM Shipment Indirect<br/>MM Shipment with Pick
 +
|
 
|-
 
|-
 
| MInOutConfirm
 
| MInOutConfirm
|
 
 
| MM Material Receipt with Confirmation
 
| MM Material Receipt with Confirmation
 +
|
 
|-
 
|-
 
| MInventory
 
| MInventory
Line 56: Line 58:
 
|-
 
|-
 
| MInvoice
 
| MInvoice
 +
| AP Credit Memo<br/>[[DocType_Invoice_Vendor|AP Invoice]]<br/>AR Credit Memo<br/>[[DocType_Invoice_Customer|AR Invoice]]<br/>AR Invoice Indirect<br/>
 
|
 
|
| AP Credit Memo<br/>[[DocType_Invoice_Vendor|AP Invoice]]<br/>AP Protocol<br/>AR Credit Memo<br/>[[DocType_Invoice_Customer|AR Invoice]]<br/>AR Invoice Indirect<br/>AR Protocol<br/>
 
 
|-
 
|-
 
| MJournal
 
| MJournal
Line 76: Line 78:
 
|-
 
|-
 
| MOrder
 
| MOrder
|
 
 
| Purchase Order<br/>On Credit Order<br/>POS Order<br/>Prepay Order<br/>Proposal<br/>Quotation<br/>Return Material<br/>Standard Order<br/>Warehouse Order
 
| Purchase Order<br/>On Credit Order<br/>POS Order<br/>Prepay Order<br/>Proposal<br/>Quotation<br/>Return Material<br/>Standard Order<br/>Warehouse Order
 +
|
 
|-
 
|-
 
| MPayment
 
| MPayment
|
 
 
| [[DocType_AP_Payment|AP Payment]]<br/>[[DocType_AR_Receipt|AR Receipt]]
 
| [[DocType_AP_Payment|AP Payment]]<br/>[[DocType_AR_Receipt|AR Receipt]]
 +
|
 
|-
 
|-
 
| MRequisition
 
| MRequisition
|
 
 
| Purchase Requisition
 
| Purchase Requisition
 +
|
 
|-
 
|-
 
| MRMA
 
| MRMA

Revision as of 00:32, 27 December 2007

Processing Basics

In ADempiere there are several predefined types of documents, as can be seen in the picture below.

The predefined types of documents of ADempiere

This window can be reached in the ADempiere Client App's menue (if you are logged in a role with access level 'Client+Organization') this way:

 Menu -> Performance Analysis -> Accounting Rules -> Document Type

The automated internal processing of those documents is a complex matter. What we start here is a simple FAQ-like explanation of those base documents. Where appropriate a further explanations are provided, redirecting to database entities, source code and articles by other ADempiereans.


List of described documents


The questions touched in these documents' inspections just skim the deeper matters related to document processing. When looking at those explanations some prior knowledge might be useful:

  • About the usage of DEFAULT_ACCOUNTS - these are special accounts from the Chart Of Accounts, which are bound in the source code to standard processes. So the posting of mainstream activities is backed up and automated.

Note that all the examples given include accounts from the American COA which comes along with the ADempiere installation.

  • Generally there are 16 model classes describing the behavior of the 36 active Document Types.
  • Concerning accounting there are 15 document classes which are responsible for posting the documents. The mapping between the classes and their corresponding document types are provided in the following table.
  • When we talk about automatic generation of documents the consequent documents in the corresponding workflow should be minded, and the automation is provided by the workflow itself. That means with the completion of a single document the set of connected documents is generated and posted in a sequence. The automatic generation is not when we use certain form to choose from which document to produce other type.
ADempiere Model classes and their corresponding Document Types
Model class Document Type Document-Posting Class
MAllocationHdr Doc_Allocation
MBankStatement Doc_Bank
MCash Doc_Cash
MInOut MM Material Receipt
MM Shipment
MM Shipment Indirect
MM Shipment with Pick
MInOutConfirm MM Material Receipt with Confirmation
MInventory
MInvoice AP Credit Memo
AP Invoice
AR Credit Memo
AR Invoice
AR Invoice Indirect
MJournal
MJournalBatch
MMovement
MMovementConfirm
MOrder Purchase Order
On Credit Order
POS Order
Prepay Order
Proposal
Quotation
Return Material
Standard Order
Warehouse Order
MPayment AP Payment
AR Receipt
MRequisition Purchase Requisition
MRMA
MTimeExpense

Specific automations common to the most types of documents

  • Payment Term specifics - for documents defining Payment Term other than 'Immediate' the contents of the tab Payment Schedule are automatically populated with data, based on the chosen rule. If the Payment Term is changed after the document is Completed, the Payment Schedule is not affected and the necessary changes must be made manually.