Show full documentation

 Show full documentation

Definition

A2A Inbound Servce for Invoice Replication

Business Context and Use

A2A Inbound Servce for Invoice Replication

More Information

See Operation Documentation for more info

 Show full documentation

 Show full documentation

Definition

A2A Invoice Replication

Business Context and Use

The request message of the operation Invoice Replicate contains a MessageHeader node element as well as an InvoiceReplicateRequest node element that contains the Invoice data to be created or updated. The InvoiceReplicateRequest node can occur multiple times in the request message. This means that multiple invoices can be created through a single web service request.

Structure

The Invoice node contains all relevant information which is required for creation or update of a payment, such as

• general information like identifications, name, creation date, status, due amount, invoice amount, paid amount, sales organisation id, sales organisation uuid, distribution channel code, division code

• parties like payer party and account party

• btd reference

• texts and attachments

General information

BusinessTransactionDocumentID

The unique identifier of an invoice. This is the Invoice ID coming from External system and will be stored as BTD reference of the newly created Invoice

Name

The name of an Invoice.

InvoiceDate

The date of an Invoice

InvoiceAmount

The amount and currency code of Invoice

PaidAmount

The paid amount with currency code

SalesOrganisationID

The identifier of the Sales organisation as in the External System

SalesOrganisationRecipientID

The identifier of the Sales organisation as on the C4C side

InvoiceStatus

The InvoiceStatus which specifies the status of the Invoice can be provided with the following values:

LeanInvoiceStatus	Description
0	Open
1	Partially Paid
2	Paid

If it is not provided in Invoice creation case, the default value 0 will be set by the system.

Parties

AccountParty

For External system ID , fill InternalID

The AccountParty is mandatory data of a payment and shall be provided in payment creation case.

RecipientID can be specified to directly fill the C4C Partner ID

PayerParty

For External system ID , fill InternalID

The PayerParty can be specified with the BusinessPartnerInternalID

RecipientID can be specified to directly fill the C4C Partner ID

BusinessTransactionDocumentReference

The BusinessTransactionDocumentReference is specified by ID, UUID, TypeCode and RoleCode of the referenced business document.

Text

With Text, texts can be provided for specified TextTypeCode.

Allowed TextTypeCode values are '10011'

If the textListCompleteTransmissionIndicator is set to true in invoice update case, the existing texts in the invoice will be replaced by the given texts.

Example:

   <Text actionCode="01">
    <TextTypeCode>10011</TextTypeCode>
    <ContentText>header customer information</ContentText>
    <CreationDateTime>2015-09-01T12:00:00.1234567Z</CreationDateTime>
   </Text>

Example

The following xml message requests bulk replication of 2 Invoices

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:glob="http://sap.com/xi/SAPGlobal20/Global">
   <soap:Header>
      <MessageID xmlns="http://www.sap.com/webas/640/soap/features/messageId/">urn:uuid:925c6e2c-5cc2-14ca-a144-08012bac1435</MessageID>
   </soap:Header>
   <soap:Body>
      <glob:InvoiceReplicateRequest>
         <MessageHeader>
            <ID>148D7B8BFA411EE122B1F96C294827E2</ID>
            <CreationDateTime>2015-06-03T12:55:22.678271Z</CreationDateTime>
           <SenderParty>
   <InternalID schemeAgencyID="310" schemeID="LocalSystemID">Q5ECLNT004</InternalID>
  </SenderParty>
  <RecipientParty>
   <InternalID schemeID="LocalSystemID" schemeAgencyID="310">0M1OT1G</InternalID>
  </RecipientParty>
         </MessageHeader>
         <InvoiceReplicateRequest>
            <BasicMessageHeader>
               <ID>14AD7B4B1C911EA111BE91CF7114C282</ID>
            </BasicMessageHeader>
            <InvoiceRequest actionCode="01">
     <BusinessTransactionDocumentID>142011</BusinessTransactionDocumentID>
               <Name>New N 1</Name>
               <InvoiceDate>1999-01-24</InvoiceDate>
               <InvoiceAmount currencyCode="EUR">415</InvoiceAmount>
               <SalesOrganisationRecipientID>DE1100</SalesOrganisationRecipientID>
               <SalesOrganisationUUID/>
               <DistributionChannelCode>01</DistributionChannelCode>
               <DivisionCode/>
                  <SenderSequenceNumberValue>0</SenderSequenceNumberValue>
<ReceiverSequenceNumberValue>0</ReceiverSequenceNumberValue>
               <PayerParty>
                  <RecipientID>10009477</RecipientID>
               </PayerParty>
               <AccountParty>
                  <RecipientID>10009477</RecipientID>
               </AccountParty>
            </InvoiceRequest>
         </InvoiceReplicateRequest>
          <InvoiceReplicateRequest>
            <BasicMessageHeader>
               <ID>14AD7B4B1C911EA111BE91CF7110C182</ID>
            </BasicMessageHeader>
            <InvoiceRequest actionCode="01">
     <BusinessTransactionDocumentID>112311</BusinessTransactionDocumentID>
               <Name>New N 2</Name>
               <InvoiceDate>1999-01-24</InvoiceDate>
               <InvoiceAmount currencyCode="EUR">415</InvoiceAmount>
               <SalesOrganisationRecipientID>DE1100</SalesOrganisationRecipientID>
               <SalesOrganisationUUID/>
               <DistributionChannelCode>01</DistributionChannelCode>
               <DivisionCode/>
                  <SenderSequenceNumberValue>0</SenderSequenceNumberValue>
<ReceiverSequenceNumberValue>0</ReceiverSequenceNumberValue>
               <PayerParty>
                  <RecipientID>10009477</RecipientID>
               </PayerParty>
               <AccountParty>
                  <RecipientID>10009477</RecipientID>
               </AccountParty>
            </InvoiceRequest>
         </InvoiceReplicateRequest>
      </glob:InvoiceReplicateRequest>
   </soap:Body>
</soap:Envelope>