PostJournalEntry schema, example, validation rules, validation stylesheet |
PostJournalEntry type: PostJournalEntry | |
The purpose of the PostJournal is to transmit data necessary to create a journal entry from any sub ledger business application to a general ledger application. Many applications in the enterprise environment create data that cause changes in the account balances of a general ledger application. Some components that have activity which will be reflected in a general ledger application are: 1. Benefits 2. Costing 3. Human Resources 4. Inventory Control 5. Manufacturing 6. Payroll 7. Production 8. Treasury By no means is this a complete list of all the components that create activity which generate a journal entry. Many tasks that occur within the enterprise applications cause the creation of a General Ledger journal entry. Tasks relate directly to the Component. For example, the adjustment of inventory value is a task that occurs within the Inventory Control Component. Some of the tasks that would be catalysts for changes in a general ledger include: 1. Receiving Inventory 2. Issuing Inventory 3. Transferring Inventory 4. Adjusting Inventory Value 5. Adjusting Inventory Count 6. Calculating Material Variances 7. Calculating Labor Variances 8. Calculating Overhead Variances |
PostJournalEntry extends: BusinessObjectDocument | |||||||
Structure: |
![]() |
||||||
Elements: |
|
PostJournalEntryDataArea extends: DataArea | ||||||||||
Structure: |
![]() |
|||||||||
Elements: |
|
PostJournalEntry Scenario Diagram |
Post schema |
Post type: Post | |
The POST verb is used to describe specific processing in a more fine grained manner beyond add, change or delete processing. An example is POST JOURNAL, where information is posted to a general ledger set of financial records. The business use of the word is used instead of the data processing term for the sake of clarity. |
Post extends: ConfirmableVerb | |
Structure: |
![]() |
JournalEntry schema |
JournalEntry type: JournalEntry | |
A journal represents a change in the balances of a business’s financial accounts. Many tasks or transactions throughout an enterprise will result in the creation of a journal. Some examples are creating a customer invoice, paying a vendor, transferring inventory, or paying employees. A journal consists of a header with general information, and two or more lines specifying what accounts will be affected. A journal typically includes balanced debit and credit lines. |
LedgerEntry type: LedgerEntry | |
JournalEntry extends: Noun | |||||||||||||||||||||||||||||||||||||
Structure: |
![]() |
||||||||||||||||||||||||||||||||||||
Elements: |
|
JournalEntryHeader | ||||||||||||||||||||||||||||||||||
Structure: |
![]() |
|||||||||||||||||||||||||||||||||
Elements: |
|
JournalEntryId restricts: xs:string | |
LedgerEntry | |||||||||||||||||||
Structure: |
![]() |
||||||||||||||||||
Elements: |
|
Verb Common Files |
Verb.xsd schema |
AcknowledgableVerb extends: ConfirmableVerb | |||||||||
Structure: |
![]() |
||||||||
Attributes: |
|
AcknowledgementType restricts: xs:NMTOKEN | |||||||
Enumerations: |
|
ConfirmableVerb extends: Verb | |||||||||
Structure: |
![]() |
||||||||
Attributes: |
|
ConfirmType restricts: xs:NMTOKEN | |||||||
Enumerations: |
|
Expression restricts: xs:string | |
ExpressionCriteria | |||||||||
Structure: |
![]() |
||||||||
Elements: |
|
||||||||
Attributes: |
|
RequestVerb extends: ConfirmableVerb | |||||||
Structure: |
![]() |
||||||
Elements: |
|
VerbBase.xsd schema |
Verb type: Verb | |
Verb | |
Structure: |
![]() |
Noun Common Files |