PostCostingActivity

In an effort to simpilify the usage of the verbs the PostCostingActivity BOD is being deprecated as of OAGIS 9.0, the PostCostingActivity will still be provided for the next three releases at which time it is scheduled to be removed from OAGIS.  As such for all new development we recommend that you use the PostCostingActivity BOD which may serve the same function of the PostCostingActivity BOD.

The purpose of the PostCostingActivity BOD is to enable the update of Activityinformation from a production or manufacturing application to a costing application.  This is necessary for applications that are based on a Dual Cycle Accounting model.  This Dual Cycle Accounting model does not capture the details of the Activities that caused entries to be made in the general ledger application, but instead captures them in a separate overall costing application.
This BOD commonly causes updates to occur and may be used as part of a large integration scenario or as a single tool for updating data. 

For Single Cycle accounting systems, the PostJournalEntry BOD will be used to ensure that the costing information flows from the Manufacturing Application to the Financial Application.

In most cases either PostJournal or PostActivity will be used when the Financial applications are included with Logistics, but both Business Service Requests will not be used in the same integration scenario.

Element information

Content

• Sequence [1..1]
  from type BusinessObjectDocumentType
  ApplicationArea [1..1]    Provides the information that an application may need to know in order to communicate in an integration of two or more business applications. The ApplicationArea is used at the applications layer of communication. While the integration frameworks web services and middleware provide the communication layer that OAGIS operates on top of.
  1. DataArea [1..1]    Is where the information that the BOD message carries is provided, in this case PostCostingActivity. The information consists of a Verb and one or more Nouns. The verb (Post) indicates the action to be performed on the Noun (CostingActivity).

Attributes

Sample instance

<PostCostingActivity releaseID="normalizedString">
   <ApplicationArea>
      <Sender>
         <LogicalID>normalizedString</LogicalID>
         <ComponentID>normalizedString</ComponentID>
         <TaskID>normalizedString</TaskID>
         <ReferenceID>normalizedString</ReferenceID>
         <ConfirmationCodes>...
         </ConfirmationCodes>
         <AuthorizationID>normalizedString</AuthorizationID>
      </Sender>
      <Receiver>
         <LogicalID>normalizedString</LogicalID>
         <ComponentID>normalizedString</ComponentID>
         <ID/>
      </Receiver>
      <CreationDateTime></CreationDateTime>
      <Signature>
         <!--any element-->
      </Signature>
      <ScenarioID>normalizedString</ScenarioID>
      <CorrelationID>normalizedString</CorrelationID>
      <BODID>normalizedString</BODID>
      <Extension>
         <AnyExtension>
            <!--any element-->
         </AnyExtension>
         <Amount/>
         <Code/>
         <DateTime></DateTime>
         <ID/>
         <Indicator>true</Indicator>
         <Measure/>
         <Name/>
         <Number>1.0</Number>
         <Quantity/>
         <Text/>
         <Time></Time>
         <ValueText>string</ValueText>
      </Extension>
   </ApplicationArea>
   <DataArea>
      <Post>
         <ActionCriteria>...
         </ActionCriteria>
      </Post>
      <CostingActivity>
         <ID/>
         <IDSet>...
         </IDSet>
         <GLEntityID>normalizedString</GLEntityID>
         <DocumentDateTime></DocumentDateTime>
         <LastModificationDateTime></LastModificationDateTime>
         <ActivityDateTime></ActivityDateTime>
         <SourceActivity>...
         </SourceActivity>
         <Extension>.......................................
         </Extension>
      </CostingActivity>
   </DataArea>
</PostCostingActivity>