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:
Name Type Description
DataArea PostJournalEntryDataArea

Is where the information that the BOD message carries is provided, in this case PostJournalEntry. The information consists of a Verb and one or more Nouns. The verb (Post) indicates the action to be performed on the Noun (JournalEntry).

PostJournalEntryDataArea extends: DataArea
Structure:
Elements:
Name Type Description
JournalEntry reference
Post reference

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:
Name Type Description
AccountingDate DateTimeAny

Is the date that is used to determine the accounting period the transaction is posted within. It is also known as the effective or post date.

AccountingPeriod Period

Is the accounting period the document is to post within. The period is within a fiscal year to which a business transaction is assigned.

AccountingYear Year

Is the accounting year the document is to post within. Generally a period of 12 months for which the company regularly has to create financial statements. A fiscal year may correspond to a calendar year.

DocumentReferences reference
EntryCreator UserId

The user’s enterprise-wide identifier. It is also known as the user code. SYNONYMS: Operator ID

Id JournalEntryId
LedgerEntry reference
LedgerId LedgerId

Identifies the Ledger to which this transaction entry is to be inserted

SourceGLEntity GLEntity

The primary balancing segment of the G/L Account structure. P and L statements are required at this level. A G/L entity is the smallest organizational unit for which individual financial statements must be drawn up according to relevant commercial law.

Synonyms: Business Unit, Fund, General Ledger Company, Joint Venture, Non-Profit Association Name

Total Amounts
UserArea reference

JournalEntryHeader
Structure:
Elements:
Name Type Description
AccountingDate DateTimeAny

Is the date that is used to determine the accounting period the transaction is posted within. It is also known as the effective or post date.

AccountingPeriod Period

Is the accounting period the document is to post within. The period is within a fiscal year to which a business transaction is assigned.

AccountingYear Year

Is the accounting year the document is to post within. Generally a period of 12 months for which the company regularly has to create financial statements. A fiscal year may correspond to a calendar year.

DocumentReferences reference
EntryCreator UserId

The user’s enterprise-wide identifier. It is also known as the user code. SYNONYMS: Operator ID

Id JournalEntryId
LedgerId LedgerId

Identifies the Ledger to which this transaction entry is to be inserted

SourceGLEntity GLEntity

The primary balancing segment of the G/L Account structure. P and L statements are required at this level. A G/L entity is the smallest organizational unit for which individual financial statements must be drawn up according to relevant commercial law.

Synonyms: Business Unit, Fund, General Ledger Company, Joint Venture, Non-Profit Association Name

Total Amounts
UserArea reference

JournalEntryId restricts: xs:string

LedgerEntry
Structure:
Elements:
Name Type Description
AccountingDate DateTimeAny

Is the date that is used to determine the accounting period the transaction is posted within. It is also known as the effective or post date.

AccountingPeriod Period

Is the accounting period the document is to post within. The period is within a fiscal year to which a business transaction is assigned.

AccountingYear Year

Is the accounting year the document is to post within. Generally a period of 12 months for which the company regularly has to create financial statements. A fiscal year may correspond to a calendar year.

LineNumber LineNumber

Is the Line Number of the given Line Coponent within the document. LineNumbers are assigned by the sending system.

Identifies the instance of a Line within a given document.

UserArea reference

Verb Common Files

Verb.xsd schema

AcknowledgableVerb extends: ConfirmableVerb
Structure:
Attributes:
Name Type Usage Description
acknowledge AcknowledgementType

AcknowledgementType restricts: xs:NMTOKEN
Enumerations:
Always
Never
OnChange

ConfirmableVerb extends: Verb
Structure:
Attributes:
Name Type Usage Description
confirm ConfirmType

ConfirmType restricts: xs:NMTOKEN
Enumerations:
Always
Never
OnChange

Expression restricts: xs:string

ExpressionCriteria
Structure:
Elements:
Name Type Description
SelectExpression Expression

Allows the 1-n number of selection expressions for the information to be returned.

Attributes:
Name Type Usage Description
expressionLanguage xs:string optional

RequestVerb extends: ConfirmableVerb
Structure:
Elements:
Name Type Description
ReturnCriteria

Allows the initator of the BOD to indicate the information (down to the field level) that is requested to be returned. The expressionLanguage indicates the expression language being used.

VerbBase.xsd schema

Verb type: Verb

Verb
Structure:

Noun Common Files