| Description | Manage Customer Invoice Requests |
| Name | ManageCustomerInvoiceRequestIn |
| Namespace | http://sap.com/xi/A1S/Global |
| Process Component Description | Customer Invoice Processing |
| Process Component Name | CustomerInvoiceProcessing |
| Process Component Namespace | http://sap.com/xi/AP/CustomerInvoicing/Global |
| Deployment Unit Description | Customer Invoicing |
| Endpoint Activation | By Scoping of Process Component | Operations |
| Release Status | Released |
An interface to replicate customer invoice request from a source system or file.
The web service interface Manage Customer Invoice Request In enables you to connect external applications to your Financials on Demand system and to create and edit customer invoice requests in your system. The web service interface Manage Customer Invoice Request In is relevant if your company wants to manage customer invoice requests from external applications.
The web service interface Manage Customer Invoice Request In offers the operation MaintainBundle.
Here is an example of a simple web service request:
Show full documentation
Show full documentation
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:glob="http://sap.com/xi/SAPGlobal20/Global">
<soapenv:Header />
<soapenv:Body>
<glob:CustomerInvoiceRequestBundleMaintainRequest_sync>
<BusinessDocumentBasicMessageHeader>
<ID schemeID="" schemeAgencyID="" schemeAgencySchemeAgencyID="">123456789</ID>
</BusinessDocumentBasicMessageHeader>
<CustomerInvoiceRequest>
<BaseBusinessTransactionDocumentID>Tibors Invoice</BaseBusinessTransactionDocumentID>
<BuyerParty>
<InternalID>MDEC16008</InternalID>
</BuyerParty>
<SalesUnitParty>
<InternalID>GCDK-1200</InternalID>
</SalesUnitParty>
<PricingTerms>
<PricingProcedureCode>PPSTD1</PricingProcedureCode>
<CurrencyCode>USD</CurrencyCode>
</PricingTerms>
<Item>
<BaseBusinessTransactionDocumentItemID>10</BaseBusinessTransactionDocumentItemID>
<BaseBusinessTransactionDocumentItemTypeCode>002</BaseBusinessTransactionDocumentItemTypeCode>
<ReceivablesPropertyMovementDirectionCode>2</ReceivablesPropertyMovementDirectionCode>
<Product>
<InternalID>MCF-0001</InternalID>
<TypeCode>1</TypeCode>
</Product>
<Quantity unitCode="EA">1.0</Quantity>
<QuantityTypeCode>EA</QuantityTypeCode>
<PriceAndTax>
<PriceComponent>
<TypeCode>7PR1</TypeCode>
<Rate>
<DecimalValue>500</DecimalValue>
<CurrencyCode>USD</CurrencyCode>
<BaseDecimalValue>1</BaseDecimalValue>
<BaseMeasureUnitCode>EA</BaseMeasureUnitCode>
</Rate>
</PriceComponent>
</PriceAndTax>
</Item>
</CustomerInvoiceRequest>
</glob:CustomerInvoiceRequestBundleMaintainRequest_sync>
</soapenv:Body>
</soapenv:Envelope>
The following business entities are only referenced and will not be created by the service operations. They must already exist in the system when the web service is called up. If not, the created customer invoice request will show inconsistencies:
Organisational Data (Parties, SalesUnit)
Products
The operation MaintainBundle supports exactly one execution (idem potency). To ensure exactly one execution of web service requests, the web service consumer has to provide unique values for the elements ID or UUID of the MessageHeader and BasicMessageHeader node element.
You can find general information about Web services, their structure and consumption in the Web Services documentation.
Possible scenarios include the following:
create or update customer invoice requests
The operation MaintainBundle is used to create or update customer invoice requests.
The key is the BaseBusinessTransactionDocumentID and the system reads the existing data. If a customer invoice request for this ID exits, the entry will be updated, otherwise the system creates a new custommer invoice request for this BaseBusinessTransactionDocumentID.
| Description | Maintain customer invoice requests |
| Name | MaintainBundle |
| Synchronous | yes |
| Release Status | Released |
To create, update, or cancel customer invoice requests.
The request message of the operation MaintainBundle contains a BusinessDocumentBasicMessageHeader node element as well as a CustomerInvoiceRequest node element that can occur multiple times. This means that multiple customer invoice requests can be created and updated with a single web service request. The CustomerInvoiceRequest node element contains the customer invoice request data to be created or updated. The detailed structure of the CustomerInvoiceRequest node will be explained in the following sub-chapters.
The CustomerInvoiceRequest node element contains all general information, such as BaseBusinessTransactionDocumentID which is the key field.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:glob="http://sap.com/xi/SAPGlobal20/Global">
<soapenv:Header />
<soapenv:Body>
<glob:CustomerInvoiceRequestBundleMaintainRequest_sync>
<BusinessDocumentBasicMessageHeader>
<ID schemeID="" schemeAgencyID="" schemeAgencySchemeAgencyID="">123456789</ID>
</BusinessDocumentBasicMessageHeader>
<CustomerInvoiceRequest>
<BaseBusinessTransactionDocumentID>Invoice-ID-XXXX</BaseBusinessTransactionDocumentID>
...
</CustomerInvoiceRequest>
</glob:CustomerInvoiceRequestBundleMaintainRequest_sync>
</soapenv:Body>
</soapenv:Envelope>
Name
The attribute Name corresponds to the UI field description.
SettlementBlockedIndicator
The SettlementBlockedIndicator indicates whether the customer invoice request must be blocked. If it is set to true, all items will be blocked for Invoicing.
BaseCancelledIndicator
The BaseCancelledIndicator indicates whether the customer invoice request must be cancelled. If it is set to true, all items will be cancelled.
SettlementPriorityCode
By setting the settlement priority code, the creation of a customer invoice is triggered for the customer invoice request.
| Code Value | Description |
|---|---|
| 1 | Immediate - create the customer invoice if the customer invoice request can be invoiced |
| 2 | Urgent - stop if a down payment exists. The customer invoice request will be created with the status to be Invoiced |
ProposedInvoiceDate
The attribute ProposedInvoiceDate defines the InvoiceDate and is set to current date, if no value is passed. During the creation of the customer invoice the invoice date can be overwritten.
ProposedDeviatingPostingDate
This date is used for a deviating posting date in financials. The default posting date is the ProposedInvoiceDate
ReferenceBusinessTransactionDocumentID
The attribute ReferenceBusinessTransactionDocumentID corresponds to the UI field External Reference. Depending on the configuration data the ReferenceBusinessTransactionDocumentID is used as external reference in the customer invoice.
BuyerParty (mandatory)
A party (Customer) that purchases a good or a service.
ProductRecipientParty (optional)
A party (Customer) that receives a good or a service.
BillToParty (optional)
A party (Customer) that receives the invoice for goods or services.
BillFromParty (optional)
A party (Company) that carries out the billing process.
SalesUnitParty (mandatory)
A party (Functional Unit) that is responsible for the customer invoice request.
PayerParty (optional)
A party (Customer) that is requested to pay the payables from the delivery of goods or the provision of services or that is the recipient of a credit memo.
EmployeeResponsibleParty (optional)
A party (Employee) that is responsible for the customer invoice request.
SalesAndServiceBusinessArea
DistributionChannelCode
A distribution channel is a channel via which goods or services reach the customer.
| Code Value | Description |
|---|---|
| 01 | Direct sales |
| 02 | Indirect sales |
CashDiscountTerms
CashDiscountTerms is an agreement of cash discounts for a payment.
Code
A user-specific code list is assigned to the CashDiscountTermsCode. A user defines the codes in the code list
PaymentControl
PaymentFormCode
| Code Value | Description |
|---|---|
| 04 | Direct Debit |
| 20 | External Payment |
Sample xml structure for External Payment:
<PaymentControl>
<PaymentFormCode>20</PaymentFormCode>
<PaymentReferenceID>REF-12061</PaymentReferenceID>
<PaymentReferenceTypeCode>5</PaymentReferenceTypeCode>
<PaymentServiceSubscriberID>MC10000</PaymentServiceSubscriberID>
<PaymentServiceCustomerID>MC9785</PaymentServiceCustomerID>
<ExternalPayment ActionCode="01">
<HouseBankAccountKeyInternalID>1100062588</HouseBankAccountKeyInternalID>
<PaymentTransactionReferenceID>52786878234</PaymentTransactionReferenceID>
<DocumentDate>2016-04-28</DocumentDate>
<ValueDate>2016-04-28</ValueDate>
<Amount currencyCode="USD">1000</Amount>
</ExternalPayment>
</PaymentControl>
|
|
PricingTerms
Pricing Terms are agreements in the sales or service processes, which are needed exclusively to determine the net value of the customer invoice request.
CurrencyCode
A coded representation of the currency in which the invoice is issued (invoice currency).
ProvisionDate
The provision date is the pricing and taxation relevant date when goods are delivered or services provided.
PricingProcedureCode
A coded representation of the procedure how price components are supposed to be calculated in the customer invoice request.
The following pricing procedure was delivered by SAP.
| Code Value | Description |
|---|---|
| PPSTD1 | Standard Procedure |
| PPGP02 | Standard Gross Procedure |
TaxationTerms (as of Business ByDesign 1811 release)
Tax Due Date
Specifies the reporting period in which a tax item is submitted to the tax authority with the tax return.
Tax Exemption Certificate
TaxExemptionReasonCodeIndicator - Indicates whether a tax exemption certificate is to be assigned.
TaxExemptionCertificateID - The ID of the tax exemption certificate to be assigned.
TaxExemptionReasonCode - The reason code of the tax exemption certificate.
The TextCollection node element can be used to maintain customer information and internal comments.
Possible text type codes include the following:
| Type code | Description |
|---|---|
| 10011 | Internal Comment |
| 10024 | Customer Information |
The AttachmentFolder node element is the collection of all documents attached to a customer invoice (as of Business ByDesign 1808 release).
Document (multiple cardinality)
A document is an attachment that was assigned to the Attachment Folder and contains unstructured information and additional control and monitoring information.
| Elements | Description |
|---|---|
| VisibleIndicator | Specifies whether a document is visible or not. |
| CategoryCode | Coded representation of the document category, such as Folder, File or Link. Code Value Description: 1 Folder; 2 Document; 3 Link |
| TypeCode | Coded representation of the document type. Most general attachments are of type '10001'. |
| MIMECode | Coded representation of the MIMECode of a document. |
| Name | Name of a document that identifies the document within its higher-level folder. The Name is the same as the last component of the DocumentPathName. All characters (apart from the separator "/") are allowed in the name. |
| AlternativeName | Language-independent name of a document |
| Description | Language-independent description of a document |
| ExternalLinkWebURI | Destination URI (if the link is external) |
| Sub-Node: (only relevant when the document is a file) FileContent-BinaryContent | Describes the unstructured data in binary form |
The item node element contains all general information on customer invoice request items, such as BaseBusinessTransactionDocumentItemID which is the key field.
BaseItemCancelledIndicator
If the indicator is set to true or the BaseCancelledIndicator on CustomerInvoiceRequest Node is set to true, the item will be cancelled. If both indicators are set to false and the item is cancelled, the cancellation will be revoked.
SettlementBlockedIndicator
If the indicator is set to true or the SettlementBlockedIndicator on customer invoice request node is set to true, the item will be blocked. If both indicators are set to false and the item is blocked, the system triggers an unblock.
BaseItemInvoicingBlockingReasonCode
A coded representation of the reason why invoicing has been blocked by the underlying business document.
| Code Value | Description |
|---|---|
| 01 | Calculation missing |
| 02 | Confirmation still open |
| 03 | Pricing incomplete |
CancellationReasonCode
A coded representation of the reason why the item has been cancelled.
| Code Value | Description |
|---|---|
| 01 | Delivery too late |
| 02 | Quality issues |
| 03 | Too expensive |
| 04 | Competitor cheaper |
| 05 | Competitor better quality |
| 06 | Customer to receive replacement |
| 07 | Warranty |
| 08 | Other reason |
ReceivablesPropertyMovementDirectionCode
A coded representation of whether a customer invoice based on this item would increase or decrease receivables.
| Code Value | Description |
|---|---|
| 1 | Decrease - Credit Memo Item |
| 2 | Increase - Invoice Item |
Description
Description of the item
CashDiscountDeductibleIndicator
Indicator that the cash discount may be deducted for this item.
Product
InternalID
Identification of the product.
TypeCode
A coded representation of a product type, such as material or service.
| Code Value | Description |
|---|---|
| 1 | Material |
| 2 | Service |
| 3 | Individual Material |
Quantity
The total quantity of goods or services to be invoiced. The quantity consists of a UnitCode and the content.
Below is a list of commonly used unit codes:
| Code Value | Description |
|---|---|
| LTR | Liter |
| SEC | Second |
| MIN | Minute |
| HUR | Hour(s) |
| DAY | Day(s) |
| WEE | Week |
| MON | Month |
| ANN | Year |
| EA | Each |
| E49 | Working day(s) |
QuantityTypeCode
A unit is not sufficient to define the type of a quantity, because a unit can be used in multiple types. For example, unit "kg" can be used in quantity types for gross weight or net weight. On the other hand, the multiple units are valid for one quantity type. The quantity type gross weight can be expressed with units "kg" or "gram", for example. The quantity type is therefore needed in addition to the unit to define a quantity completely.
Below is a list of commonly used quantity type codes:
| Code Value | Description |
|---|---|
| E49 | working day |
| EA | Each |
| TIME | Time |
| WORK | Work |
The price and tax data, such as price, discounts, surcharges, tax codes or the tax date can be set from the external system. If no values are provided, the system uses the values that are set from the internal price and tax calculation.
If an item is cancelled, you cannot maintain the price and tax data. As for an item with status Cancelled, the price and tax data must not be changed.
Node PriceAndTax
The node PriceAndTax contains the node PriceComponent and TaxCountryCode.
TaxCountryCode can be spcified if the tax country is to be overriden by a value other than the country determined by the system
<TaxCountryCode>DE</TaxCountryCode>
A PriceComponent consists of a Rate and a TypeCode.
The TypeCode is the specification of a price, a discount, or a surcharge and depends on the PricingProcedureCode.
The description depends on the entries that are set in the fine-tuning activity. The following descriptions are the defaulted values from SAP.
| PricingProcedureCode | Code Value | Description |
|---|---|---|
| PPSTD1 | 7PR1 | List Price |
| PPSTD1 | 7PR2 | Surcharge (%) |
| PPSTD1 | 7PR3 | Surcharge |
| PPSTD1 | 7PR6 | Product Discount (%) |
| PPGP02 | 8PR1 | Gross List Price |
| PPGP02 | 8PR2 | Gross Surcharge (%) |
| PPGP02 | 8PR3 | Gross Surcharge |
| PPGP02 | 8PR6 | Gross Discount (%) |
The type of the rate depends on the price component and can be an amount for the list price or a percent value for the product discount. For the price components with type Percent you cannot maintain the currency.
In the Update Scenario only the active price components were updated. If a price component is
inactive (for instance, due to errors in currency or quantity conversion), a new price component will be created.
If there are several price components for a specific type code, the exceeding price components will be deleted and the document will contain the price components that are set in the external system.
If a type code is not set from the external system, the internal calculated price components will remain unchanged.
| Freight amount must be added on the Item Price and Tax node and not on the header Price and Tax node. |
Below is an example for a gross list price and a discount for pricing procedure PPGP02:
<PriceAndTax>
<PriceComponent>
<TypeCode>8PR1</TypeCode>
<Rate>
<DecimalValue>100</DecimalValue>
<CurrencyCode>USD</CurrencyCode>
<BaseDecimalValue>1</BaseDecimalValue>
<BaseMeasureUnitCode>EA</BaseMeasureUnitCode>
</Rate>
</PriceComponent>
<PriceComponent>
<TypeCode>8PR6</TypeCode>
<Rate>
<DecimalValue>25</DecimalValue>
</Rate>
</PriceComponent>
</PriceAndTax>
Node ProductTaxDetails
The node ProductTaxDetails contain the TaxationCharacteristicsCode that is determined internally but can be changed externally.
The tax code depends on the country and represents the tax event, tax type and tax rate type. The tax event controls how taxes are posted in the tax return.
The common tax codes for Country US and DE are:
| ListID | Code Value | Description |
|---|---|---|
| DE | 500 | Non-Taxable Sale |
| DE | 501 | Domestic Supply (Standard Rate) |
| DE | 502 | Domestic Supply (Reduced Rate) |
| DE | 503 | Domestic Supply (Exempt) |
| DE | 504 | Export of Service, Reverse Charge |
| DE | 507 | Intra-Community Supply |
| DE | 508 | Export to Third Country |
| DE | 514 | Non-Taxable Sale Within Tax Reporting Group |
| DE | 530 | EU Sale of Services, Reverse Charge |
| US | 500 | Non-Taxable Sales (Out of Scope of Law) |
| US | 501 | Sales Tax - Standard Rate |
| US | 502 | Sales Tax - Exempt |
| US | 503 | Sales Tax (Special Rate: Food) |
| US | 504 | Sales Tax (Special Rate: Health Care) |
| US | 505 | Sales Tax (Special Rate: Clothing) |
| US | 506 | Sales Tax (Special Rate: Other) |
| US | 507 | Non-Taxable Sales Under Nexus Rules |
| US | 514 | Exempt Sale by Other Reason |
| US | 515 | Export |
| US | 522 | Non-Taxable Sale Within Tax Reporting Group |
Tax Country (as of Business ByDesign 1808 release)
This attribute determines the country in which sales are reported for tax declaration.
Node TaxationTerms
Tax Date (as of Business ByDesign 1808 release)
This date is used for tax rate determination and calculation and defaults the date for exchange rate determination and the tax due date. If the tax date is not provided, the invoice date is used as the tax date.
Tax Exemption Certificate (as of Business ByDesign 1811 release)
TaxExemptionReasonCodeIndicator - Indicates whether a tax exemption certificate is to be assigned.
TaxExemptionCertificateID - The ID of the tax exemption certificate to be assigned.
TaxExemptionReasonCode - The reason code of the tax exemption certificate.
ProductRecipientParty (optional)
A party (Customer) that receives a good or a service.
The TextCollection node element can be used to maintain customer information and internal comments on item level.
Possible text type codes include the following:
| Type code | Description |
|---|---|
| 10011 | Internal Comment |
| 10024 | Customer Information |
The revenue assignment can be set from the external system by filling the Node AccountingCodingBlock that is a SubNode of AccountingCodingBlockAssignment.
GeneralLedgerAccountAliasCode
The GeneralLedgerAccountAliasCode is a coded representation of an alias for a General Ledger account.
ProjectReference-ProjectElementID -
The attribute corresponds to the UI field Project Task on the Revenue Assignment tab.
The partner revenue assignment can be set from the external system by filling the Node PartnerAccountingCodingBlock that is a SubNode of AccountingCodingBlockAssignment.
AccountingCodingBlockTypeCode
The AccountingCodingBlockTypeCode is a coded representation of an alias for Accounting Coding Block Type on the Revenue Assignment tab and Partner assignment section.
GeneralLedgerAccountAliasCode
The GeneralLedgerAccountAliasCode is a coded representation of an alias for a General Ledger account on the Revenue Assignment tab and Partner assignment section.
ProjectReference-ProjectElementID
The attribute corresponds to the UI field Project Task on the Revenue Assignment tab and Partner Assignment section.
Cost Centre-CostCentreID
The attribute corresponds to the UI field Cost Centre on the Revenue Assignment tab and Partner Assignment section.
Customer Contract-CustomerContractReference
The attribute corresponds to the UI field Customer Contract ID and Item ID on the Revenue Assignment tab and Partner assignment section.
| Partner revenue assignment feature is part of beta scope and is not for General Availability (GA). In the following use-cases the partner revenue assignment data is ignored by the service interface (incase data is passed, then its ignored) : if partner profit center and Segment is switched off OR Buyer Account (Business Partner) is not a partner company and partner profit center and Segment is switched on (The business configuration scoping element is ‘partner profit center and Segment’) |
If the customer wants to assign a Down Payment that exist in the customer's system, they will have to fill the BusinessTransactionDocumentReference node. In this node there are two subnodes that need to be filled out. First the ID must be filled out on the BusinessTransactionDocumentReference subnode. This will be the Down Payment ID that will be assigned to the invoice.
The BusinessTransactionDocumentReferenceActualValues node would be used when the customer want to put a certain amount of the down payment against the Invoice. There are two elements that need to be filled out.
The PlannedDownPaymentAmount needs to be filled out with the amount that they wish to assign to the invoice and the currency of the Down Payment.
The MaximumDownPaymentAmountApplyIndicator is used to indicate if the maximum possible amount will be used from the Down Payment. This will have to be set to false if you wish to assign a specific amount to the invoice.
<BusinessTransactionDocumentReference> <BusinessTransactionDocumentReference> <ID>MCDP-96</ID> </BusinessTransactionDocumentReference> <BusinessTransactionDocumentReferenceActualValues> <PlannedDownPaymentAmount currencyCode="USD">100</PlannedDownPaymentAmount> <MaximumDownPaymentAmountApplyIndicator>false</MaximumDownPaymentAmountApplyIndicator> </BusinessTransactionDocumentReferenceActualValues> </BusinessTransactionDocumentReference>
The Down Payments should be created and cleared by accounting before assigning to Invoice Request
CroatiaBusinessSpaceID
Identifier of the business space from which customer invoices are issued.
CroatiaBillingMachineID
Identifier of the device used for billing or generating customer invoice.
CroatiaPaymentMethodCode
Represents the payment method supported by the legal authorization process.
| Code Value | Description |
|---|---|
| C | Check |
| G | Cash |
| K | Credit Card |
| O | Other |
| T | Bank Transfer |
CroatiaPartyTaxID
This field represents the OIB or tax number of the operator who issues the customer invoice.
CroatiaParagonBillMark
It is the invoice number as in the pre-printed paper invoice. In case, the billing system is completely down, the company can issue invoices through pre-printed paper invoices. However, these details must be transferred to the tax authority CIS system later.
CroatiaSpecialNote
If it was necessary to issue and send the customer invoice to the legal authority in paper form, for example, due to technical reasons, enter the invoice number printed on the paper invoice when resending the electronic version.
Customer invoice request with freight
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:glob="http://sap.com/xi/SAPGlobal20/Global"> <soapenv:Header /> <soapenv:Body> <glob:DownPaymentCustomerInvoiceRequestBundleMaintainReqiest_sync> <BusinessDocumentBasicMessageHeader> </BusinessDocumentBasicMessageHeader> <CustomerInvoiceRequest itemListCompleteTransmissionIndicator="false" actionCode="04"> <ProposedInvoiceDate>2019-02-05</ProposedInvoiceDate> <BaseBusinessTransactionDocumentID>TEST_FREIGHT</BaseBusinessTransactionDocumentID> <BuyerParty> <InternalID>MC6049</InternalID> </BuyerParty> <BillToParty> <InternalID>MC6049</InternalID> </BillToParty> <SalesUnitParty> <InternalID>MC42162</InternalID> </SalesUnitParty> <PricingTerms> <PricingProcedureCode>PPSTD1</PricingProcedureCode> <CurrencyCode>USD</CurrencyCode> </PricingTerms> <Item> <BaseBusinessTransactionDocumentItemID>10</BaseBusinessTransactionDocumentItemID> <ReceivablesPropertyMovementDirectionCode>2</ReceivablesPropertyMovementDirectionCode> <Product> <InternalID>MCF-0001</InternalID> <TypeCode>1</TypeCode> </Product> <Quantity unitCode="EA">1.0</Quantity> <QuantityTypeCode>EA</QuantityTypeCode> <PriceAndTax> <PriceComponent> <TypeCode>7PR1</TypeCode> <Rate> <DecimalValue>500</DecimalValue> <CurrencyCode>USD</CurrencyCode> <BaseDecimalValue>1</BaseDecimalValue> <BaseMeasureUnitCode>EA</BaseMeasureUnitCode> </Rate> </PriceComponent> <PriceComponent> <TypeCode>7PR8</TypeCode> <Rate> <DecimalValue>3</DecimalValue> </Rate> </PriceComponent> </PriceAndTax> </Item> </CustomerInvoiceRequest> </glob:DownPaymentCustomerInvoiceRequestBundleMaintainReqiest_sync> </soapenv:Body> </soapenv:Envelope>
Adding free text item
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:glob="http://sap.com/xi/SAPGlobal20/Global"> <soapenv:Header /> <soapenv:Body> <glob:CustomerInvoiceRequestBundleMaintainRequest_sync> <BusinessDocumentBasicMessageHeader/> <CustomerInvoiceRequest itemListCompleteTransmissionIndicator="true" actionCode="04"> <ObjectNodeSenderTechnicalID>13221314</ObjectNodeSenderTechnicalID> <BaseBusinessTransactionDocumentID>TES997</BaseBusinessTransactionDocumentID> <Name>Test FreetText</Name> <ProposedInvoiceDate>2019-12-12</ProposedInvoiceDate> <BuyerParty> <InternalID>MC9785</InternalID> </BuyerParty> <SalesUnitParty> <InternalID>MC45000</InternalID> </SalesUnitParty> <SalesAndServiceBusinessArea> <DistributionChannelCode>02</DistributionChannelCode> </SalesAndServiceBusinessArea> <EmployeeResponsibleParty> <InternalID>MC2471</InternalID> </EmployeeResponsibleParty> <PricingTerms> <PricingProcedureCode listID="2">PPSTD1</PricingProcedureCode> <CurrencyCode>USD</CurrencyCode> </PricingTerms> <Item actionCode="04"> <BaseBusinessTransactionDocumentItemID>10</BaseBusinessTransactionDocumentItemID> <BaseBusinessTransactionDocumentItemTypeCode>002</BaseBusinessTransactionDocumentItemTypeCode> <SettlementRelevanceIndicator>true</SettlementRelevanceIndicator> <BaseItemCancelledIndicator>false</BaseItemCancelledIndicator> <ReceivablesPropertyMovementDirectionCode>2</ReceivablesPropertyMovementDirectionCode> <Description languageCode="EN">Test</Description> <CashDiscountDeductibleIndicator>true</CashDiscountDeductibleIndicator> <Quantity unitCode="EA">5</Quantity> <QuantityTypeCode>EA</QuantityTypeCode> <PriceAndTax> <PriceComponent> <TypeCode listID="2">7PR1</TypeCode> <CategoryCode>1</CategoryCode> <PurposeCode>1000</PurposeCode> <MajorLevelOrdinalNumberValue>10</MajorLevelOrdinalNumberValue> <MinorLevelOrdinalNumberValue>1</MinorLevelOrdinalNumberValue> <Rate> <DecimalValue>100</DecimalValue> <CurrencyCode>USD</CurrencyCode> <BaseDecimalValue>1</BaseDecimalValue> <BaseMeasureUnitCode>EA</BaseMeasureUnitCode> </Rate> <CalculationBasis> <BaseCode>3</BaseCode> <Quantity unitCode="EA">5</Quantity> <QuantityTypeCode>EA</QuantityTypeCode> <Amount currencyCode="USD">10</Amount> </CalculationBasis> <CalculatedAmount currencyCode="USD">100</CalculatedAmount> <RoundingDifferenceAmount currencyCode="USD">100</RoundingDifferenceAmount> <EffectiveIndicator>true</EffectiveIndicator> <ManuallyChangedIndicator>true</ManuallyChangedIndicator> <GroupedIndicator/> <OriginCode>2</OriginCode> <PriceSpecificationUUID/> <PriceSpecificationDeterminationTimePoint> <TypeCode>1</TypeCode> <Date>2018-09-02</Date> </PriceSpecificationDeterminationTimePoint> </PriceComponent> </PriceAndTax> <ProductTaxDetails> <ProductTaxationCharacteristicsCode listID="US">501</ProductTaxationCharacteristicsCode> <ProductTax> <CountryCode>US</CountryCode> </ProductTax> <TransactionCurrencyProductTax> <CountryCode>US</CountryCode> </TransactionCurrencyProductTax> </ProductTaxDetails> <TaxationTerms> <TaxDate>2018-09-20</TaxDate> </TaxationTerms> <AccountingCodingBlockAssignment> <AccountingCodingBlock> <GeneralLedgerAccountAliasCode>A-1600</GeneralLedgerAccountAliasCode> </AccountingCodingBlock> </AccountingCodingBlockAssignment> </Item> </CustomerInvoiceRequest> </glob:CustomerInvoiceRequestBundleMaintainRequest_sync> </soapenv:Body> </soapenv:Envelope>
Credit Memo
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:glob="http://sap.com/xi/SAPGlobal20/Global"> <soapenv:Header /> <soapenv:Body> <glob:CustomerInvoiceRequestBundleMaintainRequest_sync> <BusinessDocumentBasicMessageHeader/> <CustomerInvoiceRequest itemListCompleteTransmissionIndicator="true" actionCode="04"> <ObjectNodeSenderTechnicalID>13221314</ObjectNodeSenderTechnicalID> <BaseBusinessTransactionDocumentID>TESTCREDIT</BaseBusinessTransactionDocumentID> <Name>Test InvoicingUnit</Name> <ProposedInvoiceDate>2017-05-05</ProposedInvoiceDate> <BuyerParty> <InternalID>MC9785</InternalID> </BuyerParty> <SalesUnitParty> <InternalID>MC45000</InternalID> </SalesUnitParty> <SalesAndServiceBusinessArea> <DistributionChannelCode>02</DistributionChannelCode> </SalesAndServiceBusinessArea> <EmployeeResponsibleParty> <InternalID>MC2471</InternalID> </EmployeeResponsibleParty> <PricingTerms> <PricingProcedureCode listID="2">PPSTD1</PricingProcedureCode> <CurrencyCode>USD</CurrencyCode> </PricingTerms> <Item actionCode="04"> <BaseBusinessTransactionDocumentItemID>10</BaseBusinessTransactionDocumentItemID> <BaseBusinessTransactionDocumentItemTypeCode>002</BaseBusinessTransactionDocumentItemTypeCode> <SettlementRelevanceIndicator>true</SettlementRelevanceIndicator> <BaseItemCancelledIndicator>false</BaseItemCancelledIndicator> <ReceivablesPropertyMovementDirectionCode>1</ReceivablesPropertyMovementDirectionCode> <Product> <InternalID>MCF-0001</InternalID> <TypeCode>1</TypeCode> </Product> <CashDiscountDeductibleIndicator>true</CashDiscountDeductibleIndicator> <Quantity unitCode="EA">5</Quantity> <QuantityTypeCode>EA</QuantityTypeCode> <PriceAndTax> <PriceComponent> <TypeCode listID="2">7PR1</TypeCode> <CategoryCode>1</CategoryCode> <PurposeCode>1000</PurposeCode> <MajorLevelOrdinalNumberValue>10</MajorLevelOrdinalNumberValue> <MinorLevelOrdinalNumberValue>1</MinorLevelOrdinalNumberValue> <Rate> <DecimalValue>100</DecimalValue> <CurrencyCode>USD</CurrencyCode> <BaseDecimalValue>1</BaseDecimalValue> <BaseMeasureUnitCode>EA</BaseMeasureUnitCode> </Rate> <CalculationBasis> <BaseCode>3</BaseCode> <Quantity unitCode="EA">5</Quantity> <QuantityTypeCode>EA</QuantityTypeCode> <Amount currencyCode="USD">10</Amount> </CalculationBasis> <CalculatedAmount currencyCode="USD">100</CalculatedAmount> <RoundingDifferenceAmount currencyCode="USD">100</RoundingDifferenceAmount> <EffectiveIndicator>true</EffectiveIndicator> <ManuallyChangedIndicator>true</ManuallyChangedIndicator> <GroupedIndicator/> <OriginCode>2</OriginCode> <PriceSpecificationUUID/> <PriceSpecificationDeterminationTimePoint> <TypeCode>1</TypeCode> <Date>2012-09-02</Date> </PriceSpecificationDeterminationTimePoint> </PriceComponent> </PriceAndTax> <ProductTaxDetails> <ProductTaxationCharacteristicsCode listID="US">501</ProductTaxationCharacteristicsCode> <ProductTax> <CountryCode>US</CountryCode> </ProductTax> <TransactionCurrencyProductTax> <CountryCode>US</CountryCode> </TransactionCurrencyProductTax> </ProductTaxDetails> <TaxationTerms> <TaxDate>2012-09-20</TaxDate> </TaxationTerms> <AccountingCodingBlockAssignment> <AccountingCodingBlock> <GeneralLedgerAccountAliasCode>A-1600</GeneralLedgerAccountAliasCode> </AccountingCodingBlock> </AccountingCodingBlockAssignment> </Item> </CustomerInvoiceRequest> </glob:CustomerInvoiceRequestBundleMaintainRequest_sync> </soapenv:Body> </soapenv:Envelope>
| Release | Change Description | Details |
| 1908 | Documentation change | Added Croatia Legal Authorization Fields to request message of MaintainBundle and CheckMaintainBundle |
|
| Description | Check customer invoice requests |
| Name | CheckMaintainBundle |
| Synchronous | yes |
| Release Status | Released |
To check if customer invoice requests can be created updated, or cancelled without errors.
The web service request- and response message types for the CheckMaintainBundle operation are the same as those of the Maintain Bundle operation. The explanations given can therefore also be applied to the CheckMaintainBundle operation.
