DataArea

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

Element information

Content

• Sequence [1..1]
  1. Get [1..1]    The Get verb is to communicate to a business software component a request for an existing piece or pieces of information to be returned. The Get may be paired with most of the nouns defined in the OAGIS specification.The response to this request is the Show verb. The behavior of a BOD with a Get verb is quite predictable across the nouns it is paired with.The Get is designed to retrieval of information by using that information's primary retrieval field, or key field. The Get verb may also be used to request several documents at once. Selection Criteria:There are two types of selection capabilities for most BOD's that use the Get verb.1) The first selection capability is called Field-Based Selection. Within a Get-based Business Object Document, the first Data Type that occurs in a specific BOD structure is commonly used to provide the Field-Based Selection criteria. This is always defined within the specific BOD and is commonly the required fields for that specific Data type.The Field-Based Selection enables the requester to provide a value or values (in the case of multiple required Field Identifiers), in the required fields. Then the responding component uses those values to find and return the requested information to the originating business software component.2) The second type of selection capability for Get-based BODs is called Data Type Selection. Data Type selection enables the requester to identify which Data Types within the noun are requested to be returned in the response. The use of this capability is described for each corresponding Data Type for all BODs that use the Get verb. The Data Types are identified for retrieval within the Get instance of a BOD by including the name of the Data Type in the meta data but without any Field Identifiers or Segments identified within the Data Type. This will signify to the responding application that all of the data that corresponds to that Data Type is to be included in the response.If the Data Type is not requested, the Data Type identifier is not included in the Get request and this will signify to the responding component that the Data Type is not to be returned.
  2. RemittanceAdvice [1..*]    The purpose of the RemittanceAdvice Business Object Document is to provides a detailed breakdown of a payment amount. It includes all credits, debits, discounts, adjustments taken on an invoice, and adjustment reason codes. A payment can attach a Remittance Advice Notification. Payment can be for products only, transportation, or other services. The Process RemittanceAdvice sends the electronic form of a remittance advice document from a payer to a payee. It is usually executed when an outstanding accounts payable balance (credit or debit) exists.

Attributes

None

Used in

• Type GetRemittanceAdviceType (Element GetRemittanceAdvice)

Sample instance

<DataArea>
   <Get>
      <Expression>token</Expression>
   </Get>
   <RemittanceAdvice>
      <RemittanceAdviceHeader>
         <ID/>
         <RevisionID>normalizedString</RevisionID>
         <VariationID>normalizedString</VariationID>
         <DocumentIDSet>...
         </DocumentIDSet>
         <LastModificationDateTime></LastModificationDateTime>
         <DocumentDateTime></DocumentDateTime>
         <Description/>
         <Note/>
         <DocumentReference>...
         </DocumentReference>
         <Attachment>...
         </Attachment>
         <Status>...
         </Status>
         <EffectiveDate></EffectiveDate>
         <InitiatingParty>...
         </InitiatingParty>
         <BillToParty>...
         </BillToParty>
         <FinancialParty>...
         </FinancialParty>
         <RemitToParty>...
         </RemitToParty>
         <Party>...
         </Party>
         <CheckInstruction>...
         </CheckInstruction>
         <PaymentMethodCode>token</PaymentMethodCode>
         <TotalAmount/>
         <TransactionID>normalizedString</TransactionID>
         <Extension>.......................................
         </Extension>
      </RemittanceAdviceHeader>
      <RemittanceAdviceLine>
         <LineNumberID/>
         <LineIDSet>...
         </LineIDSet>
         <Description/>
         <Note/>
         <DocumentReference>...
         </DocumentReference>
         <Attachment>...
         </Attachment>
         <Status>...
         </Status>
         <PaymentAmount/>
         <Extension>.......................................
         </Extension>
      </RemittanceAdviceLine>
   </RemittanceAdvice>
</DataArea>