| Description | Manage Invoice In |
| Name | ManageInvoiceIn |
| Namespace | http://sap.com/xi/AP/CRM/Global |
| Process Component Description | Retail Execution Processing |
| Process Component Name | RetailExecutionProcessing |
| Process Component Namespace | http://sap.com/xi/AP/CRM/Global |
| Deploymnent Unit Description | Customer Relationship Management |
| Endpoint Activation | By Scoping of Process Component | Operations |
| Release Status | Deprecated |
No documentation available.
| Description | Check invoices |
| Name | CheckMaintainBundle |
| Synchronous | yes |
| Release Status | Deprecated |
Simulation of "MAINTAIN_BUNDLE"
Test check response of operaton "MAINTAIN_BUNDLE" of II_MANAGE_COD_REX_LINV_IN without commite the save.
| Description | Maintain invoices |
| Name | MaintainBundle |
| Synchronous | yes |
| Release Status | Deprecated |
To create or update an Invoice
The request message of the operation MaintainBundle contains a BasicMessageHeader node element as well as an Invoice node element that contains the Invoice data to be created or updated. The Invoice node can occur multiple times in the request message. This means that multiple invoices can be created and updated through a single web service request.
The response message type of the operation MaintainBundle contains log items, processing information, and an invoice-specific node with ChangeStateID as well as ID and UUID of the invoice.
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
payment reference
texts and attachments
The unique identifier of an invoice. In creation case, it is automatically generated by the system. In update case, the ID must be provided.
The universally unique identifier of an invoice . In creation case, it is automatically generated by the system. In update case, the UUID (or ID) must be provided.
The name of an Invoice.
The BusinessTransactionDocumentTypeCode is required only if a customer special processing type code is used (instead of the standard processing type code).
The special processing type code which is provided must be available in the system (configuration).
The date of an Invoice
The amount and currency code of Invoice
The paid amount with currency code
The identifier of the Sales organisation
The LeanInvoiceStatus 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.
The AccountParty is mandatory data of a payment and shall be provided in payment creation case.
In standard case, only the ID (BusinessPartnerInternalID) of the account party needs to be provided.
Remark:
In order update case, the AccountParty shall not be provided once the order has been submitted because change of the AccountParty is then not allowed.
The PayerParty can be specified with the BusinessPartnerInternalID
The BusinessTransactionDocumentReference is specified by ID, UUID, TypeCode and RoleCode of the referenced business document.
The ID and UUID do not need to be provided both. However one of them must be given.
Allowed values for the RoleCode are 1 (Predecessor) and 2 (Successor).
More than one BusinessTransactionDocumentReference can be provided. If the businessTransactionDocumentReferenceListCompleteTransmissionIndicator is set to true in order update case, the existing business transaction document references in the order will be replaced by the given business transaction document references.
For external references which are linked to an external business transaction documents, the schemeID of the ID/UUID for the referenced business document shall be filled with the name of the logical system where the external document is located. Currently only references to external sales orders as follow-up document of the customer order are supported. For internal references, the schemeID shall not be filled.
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.
Additionally the text creation date time can be given. The TextID can also be provided in invoice update case, but is optional.
Example:
Show full documentation
Show full documentation
<Text actionCode="01">
<TextTypeCode>10011</TextTypeCode>
<ContentText>header customer information</ContentText>
<CreationDateTime>2015-09-01T12:00:00.1234567Z</CreationDateTime>
</Text>
With AttachmentFolder, attachments can be provided.
The allowed attachment TypeCode for invoice is '10001' (Standard attachment).
The allowed CategoryCode values are '2' (Document attachment) and '3' (Link attachment).
Multiple attachments can be provided within the AttachmentFolder. If the DocumentListCompleteTransmissionIndicator is set to true in invoice update case, the existing attachments in the invoice will be replaced by the given attachments.
The Document UUID can be provided in invoice update case, but is optional.
The following xml message requests creation of a Invoice
<n0:LeanInvoiceBundleMaintainRequest_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader>
<CreationDateTime>2006-03-28T12:00:00.1234567Z</CreationDateTime>
</BasicMessageHeader>
<Invoice actionCode="01">
<Name>Test Webservice</Name>
<BusinessTransactionDocumentTypeCode> </BusinessTransactionDocumentTypeCode>
<CreationDate>2016-10-24</CreationDate>
<InvoiceAmount currencyCode="EUR">226</InvoiceAmount>
<SalesOrganisationID>D1000</SalesOrganisationID>
<SalesOrganisationUUID></SalesOrganisationUUID>
<DistributionChannelCode></DistributionChannelCode>
<DivisionCode></DivisionCode>
<AccountParty>
<BusinessPartnerInternalID>MC9785</BusinessPartnerInternalID>
</AccountParty>
<PayerParty>
<BusinessPartnerInternalID>MC9785</BusinessPartnerInternalID>
</PayerParty>
</Invoice>
</n0:LeanInvoiceBundleMaintainRequest_V1>
This xml message requests update of the Invoice 262 with the following changes:
Add a new BTD reference (Payment) with ID 39
<n0:LeanInvoiceBundleMaintainRequest_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <Invoice actionCode="02"> <BusinessTransactionDocumentID>262</BusinessTransactionDocumentID> <Name>Test Web</Name> <CreationDate>2016-10-24</CreationDate> <InvoiceAmount currencyCode="EUR">22</InvoiceAmount> <BusinessTransactionDocumentReference actionCode="01"> <ObjectNodeSenderTechnicalID>Token 147</ObjectNodeSenderTechnicalID> <ID>39</ID> <TypeCode>2209</TypeCode> </BusinessTransactionDocumentReference> </Invoice> </n0:LeanInvoiceBundleMaintainRequest_V1>