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.
Element information
Namespace: http://www.openapplications.org/oagis/10
Schema document: Common.xsd
Type: ProcessType
Properties: Global, Qualified, ID: oagis-id-80c6fc8106764599aee3f6e3c0c5bd33
Content
- ActionCriteria [0..*] Identifies with the ActionExpression the level by carrying a value of the expressionLanguage (this is typically XPath) within the BOD that the actionCode is to be performed. The ChangeStatus communicates just that the Change Status.
from type ActionVerbType
Attributes
| Name | Occ | Type | Description | Notes |
|---|---|---|---|---|
| recordSetStartNumber | [0..1] | PositiveIntegerNumberType | from type ActionVerbType | |
| recordSetCountNumber | [0..1] | PositiveIntegerNumberType | from type ActionVerbType | |
| recordSetTotalNumber | [0..1] | PositiveIntegerNumberType | from type ActionVerbType | |
| recordSetCompleteIndicator | [0..1] | IndicatorType | from type ActionVerbType | |
| recordSetReferenceID | [0..1] | IDType_B3F14E | from type ActionVerbType | |
| acknowledgeCode | [0..1] | ResponseCodeContentType |
Used in
- Type PostActualLedgerDataAreaType (Element DataArea)
- Type PostBudgetLedgerDataAreaType (Element DataArea)
- Type PostCostingActivityDataAreaType (Element DataArea)
- Type PostInvoiceLedgerEntryDataAreaType (Element DataArea)
- Type PostJournalEntryDataAreaType (Element DataArea)
- Type PostMatchDocumentDataAreaType (Element DataArea)
- Type PostPayableDataAreaType (Element DataArea)
- Type PostProjectAccountingDataAreaType (Element DataArea)
- Type PostReceivableDataAreaType (Element DataArea)
Sample instance
<Post> <ActionCriteria> <ActionExpression actionCode="token">token</ActionExpression> <ChangeStatus> <ID/> <IDSet>... </IDSet> <Code/> <Description/> <ReasonCode>normalizedString</ReasonCode> <Reason/> <EffectiveTimePeriod>.................. </EffectiveTimePeriod> <StateChange>... </StateChange> <Extension>....................................... </Extension> </ChangeStatus> </ActionCriteria> </Post>



