| Description | Manage Lease Contracts |
| Name | ManageLeaseContractsIn |
| Namespace | http://sap.com/xi/A1S/Global |
| Process Component Description | Lease Contract Management |
| Process Component Name | LeaseContractManagement |
| Process Component Namespace | http://sap.com/xi/AP/LeaseContractManagement/Global |
| Deployment Unit Description | Financials |
| Endpoint Activation | By Scoping of Process Component | Operations |
| Release Status | Released |
An interface to migrate or create lease contracts from a source system or file.
The web service Interface Manage Lease Contracts In enables you to connect external applications to your SAP Business ByDesign system and to create and edit lease contracts in your system. The web service interface Manage Lease Contract In is relevant if your company wants to access and manage lease contract data from external applications.
In the Lease Contract Management work center and Contracts view, you can create, edit and delete a Lease Contract.
The web service interface Manage Lease Contract In offers the operations CheckMaintainBundle and MaintainBundle.
Existence of referenced business documents:
The following business documents are only referenced and will not be created by the service operations. They must exist in the system already at the time the web service is called:
• Business Partners (Lessor, Company)
• Employees
Maintain Bundle operations enable external applications to create and change business document data. Check Maintain Bundle operations enable external applications to simulate maintain bundle requests without changing business document data.
In particular, Check Maintain Bundle operations have the following functions:
• Return system messages similar to corresponding Maintain_Bundle operation
• Provide the same message type as the corresponding Maintain_Bundle operation
• Does not assign internal numbers from a productive number range interval (number range status are not increased)
• Does not change business documents
Action codes represent an instruction to the recipient of the web service request to process transmitted message node elements. Following are the existing action codes and their description.
| Action Code | Description |
|---|---|
| 01 | Create; the system returns an error message if the node element already exists. |
| 02 | Update; the system returns an error message if the node element does not exist. |
| 03 | Delete; the system returns an error message if the node element does not exist. |
| 04 | Save; the system creates or changes the node element data. |
| 05 | Remove; the system deletes the node element. If the node element does not exist, the system does not send an error message. |
| 06 | No Action; the system does not change the node element. |
Default action code: 04 (Save).
Note: Action code 04 (Save) creates business documents if the system could not identify a matching target business document. This applies in particular if no business document ID or UUID is provided by the web service consumer. The web service consumer (external application) is responsible for providing correct business document IDs or UUIDs and to avoid accidental creation of duplicate business documents.
The processing of node elements with cardinality > 1 (for example a list of descriptions in different languages or a list of telephone numbers) can be controlled using List Complete Transmission Indicators (LCTI). The LCTI indicates whether a list of node elements is transmitted completely. The LCTI of a node element with cardinality > 1 is modeled as an attribute of its parent node element (attribute name: <name of child element>ListCompleteTransmissionIndicator).
| LCTI | Description |
|---|---|
| false | The list of node elements is not transmitted completely and hence all node elements that are not transmitted remain unchanged. If transmitted node elements in the list can be identified uniquely, the system processes the node elements according the action code. If transmitted node elements in the list cannot be identified uniquely, the system appends the node element to the corresponding list of node elements in the target business document. |
| true | The list of elements is transmitted completely and hence all node elements that are not transmitted are removed. If no node element is transmitted, the complete list is removed. |
Default list complete transmission indicator: false.
Note: The LCTI refers to the completeness of the list of node elements and does not state completeness of sub-elements.
New description with language code DE (German) is created while an existing description with language code EN (English) is updated. Moreover, an existing description with language code FR (French) remains unchanged and any other description (with language code ES (Spanish), for example) is deleted. An error is raised if there is already a German description or if the English or French description does not exist.
Show full documentation
Show full documentation
<Root actionCode="04" descriptionListCompleteTransmissionIndicator="true" >
<Description actionCode="01">
<Description languageCode="DE">neuer deutscher Text
</Description>
<Description actionCode="02">
<Description languageCode="EN">changed english text
</Description>
<Description actionCode="06">
<Description languageCode="FR"></Description>
</Description>
</Root>
Optional leaf elements in request messages that are not transmitted within a web service request are not changed in corresponding business documents.
In updating a postal address of a purchase order , the request updates the city name, street postal code, street name, and house ID. The country code remains unchanged, as the element "CountryCode" is not contained in the XML document (commented out).
<PostalAddress actionCode="02"> <!-- <CountryCode>DE</CountryCode> --> <CityName>Heidelberg</CityName> <StreetPostalCode>69117</StreetPostalCode> <StreetName>Hauptstrasse</StreetName> <HouseID></HouseID> </PostalAddress>
Note: The request deletes the house ID or updates the house ID with its initial value.
Maintain bundle and check maintain bundle operations are mass-enabled stateless synchronous web service operations. Transferring or requesting amounts of data that are too large causes communication timeouts. The web service consumer is responsible for ensuring reasonable sizes of data for mass operations.
Maintain bundle and check maintain bundle operations support 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 BasicMessageHeader node element.
Using change state identifier (element name ChangeStateID), external applications can enforce that a modifying operation is not executed because the state of the business document has changed since the external application last read its data.
The change state ID is an uninterpretable string that is provided by query and read operations and can be utilized by all modifying operations. If the change state identifier is provided when calling a modifying operation, the system does not perform the operation if the state of the business document instance has changed since the change state ID was computed. If the change state ID is not provided by the web service consumer, the system performs the web service operation without checking the state of the business document.
The web service consumer (external application) is responsible for preventing accidental changes to business documents.
Request node elements with cardinality > 1 contain an object node sender technical identifier to relate response message elements and log items to corresponding node elements in the request message.
The object node sender technical identifiers are provided as ObjectNodeSenderTechnicalID in request message types and referred to as ReferenceObjectNodeSenderTechnicalID in corresponding response message types.
If the object node sender technical ID is initial, the object node sender technical ID of the parent node element in the request is returned as the reference object node sender technical ID. If the object node sender technical IDs of all parent node elements are initial, the reference object node sender technical ID is returned as initial as well.
Note: The values specified in the ObjectNodeSenderTechnicalID are transient values that establish the correspondence between elements for only a single call. The web service consumer is not required to specify them or to use the same values for different calls. Also, the service provider does not interpret these values at all, but returns them to the web service consumer instead in the ReferenceObjectNodeSenderTechnicalID elements.
Note: The ObjectNodeSenderTechnicalID is also used to identify failed business document modifications in a mass operation.
Request
<Child> <ObjectNodeSenderTechnicalID>999_A<ObjectNodeSenderTechnicalID> <Content>Child A: Some correct content</Content> </Child> <Child> <ObjectNodeSenderTechnicalID>999_B<ObjectNodeSenderTechnicalID> <Content>Child B: Some erroneous content</Content> </Child>
Response:
<Log> <Item> <ReferenceObjectNodeSenderTechnicalID>999_B </ReferenceObjectNodeSenderTechnicalID> <Note>Error message for Child B</Note> </Item> </Log>
The structure of the response message consists of two parts:
• A business document-specific part containing information about IDs and UUIDs of the created and changed business documents
• Log items containing system messages including errors, warnings, and information messages raised by the system during processing of the web service request
Many external applications consuming web services have special requirements and restrictions regarding the format of WSDLs. Some external applications require service definition WSDLs describing the web service signature. This is normally sufficient for the creation of static client-side proxies. Other external applications, normally those that do not create static client-side proxies, require binding WSDLs including the endpoint definition and authentication policy information.
In both cases, it may be the case that the external application imposes special restrictions on the structure or the size of WSDLs.
Microsoft InfoPath requires binding WSDLs and considers elements with the attribute "minOccurs=0" as "mandatory". However "minOccurs=0" means "optional" in SAP web services. In order to circumvent this problem, the WSDL must be saved locally and an additional attribute "nillable=true" must be added to make a query parameter optional for Microsoft InfoPath.
For very small clients such as mobile devices, the size of the WSDL itself may become a problem. In most cases the client only requires a very small part of the signature, but due to the complexity of the WSDL they may end up with long runtime during serialization of the request or deserialization of the response. In order to circumvent this problem, the WSDL must be saved locally and the optional parts of the signature have to be removed before the WSDL is imported or static client-side proxies are generated.
External applications have to take into account that web service request and response message types can be enhanced with additional elements and attributes. Enhancements can be created by SAP, SAP partners, and key users. Enhancements of request message types are always optional elements or attributes. The SAP system does not require the external application to provide values in the request. Enhancements of response message types can contain mandatory elements or attributes. The external application must be able to process the extended response successfully.
XML element and attribute names are always stable. Technical definitions of data types can be enhanced in a compatible way. This may result in changed data type names. External applications can rely on XML element names and attribute names, but should not rely on data type names.
Note: You can download the WSDL file for any web service here:
• Application and User Management work center -> Input Output Management -> Communication Arrangement.
• User Management work center -> Service Explorer view.
You can find the documentation of the global data types in the SAP Community Network: Go to http://scn.sap.com/docs/DOC-17516 and click View Document.
You can find general information about Web services, their structure and consumption in the Web Services documentation.
Possible scenarios include the following:
• Create, Update and Delete one or many of Lease Contract
| Description | Maintain lease contracts |
| Name | MaintainBundle |
| Synchronous | yes |
| Release Status | Released |
To create or update one or more lease contract.
The request message of the operation MaintainBundle contains a Basic Message Header node element as well as a Lease Contract node element that contains the Lease Contract data to be created or updated. The detailed structure of the Lease Contract node will be explained in the following sub-chapters. The Lease Contract node can occur multiple times in the request message – this means that multiple Lease contract 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 a Lease Contract-specific node with ReferenceObjectNodeSenderTechnicalID, ChangeStateID, as well as Lease Contract InternalID and UUID.
Example: Create a Lease Contract
web service request
<n0:LeaseContractBundleMaintainRequest_sync xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader/>
<LeaseContract objectItemListCompleteTransmissionIndicator="true" renewalTermListCompleteTransmissionIndicator="true" noticeAgreementListCompleteTransmissionIndicator="true" textCompleteTransmissionIndicator="true" attachmentFolderCompleteTransmissionIndicator="true" actionCode="01">
<CompanyID>MDEC10000</CompanyID>
<ExternalReferenceID>EXT_REF_93348187</ExternalReferenceID>
<Description>Lease Contract for car lease</Description>
<CurrencyCode>USD</CurrencyCode>
<InceptionDate>2020-01-01</InceptionDate>
<LeaseStartDate>2020-02-01</LeaseStartDate>
<LeaseFirstEndDate>2021-12-31</LeaseFirstEndDate>
<LifecycleStatusCode>1</LifecycleStatusCode>
<LessorInternalID>MDEC2000</LessorInternalID>
<LessorContactPersonID>MDECP2000</LessorContactPersonID>
<EmployeeResposibleID>3107</EmployeeResposibleID>
<DataOriginTypeCode>3</DataOriginTypeCode>
<ContractTypeCode>1</ContractTypeCode>
<TransitionTypeCode>2</TransitionTypeCode>
<InterestRatePercent>2</InterestRatePercent>
<ObjectItem conditionsListCompleteTransmissionIndicator="true" oganisationAssignmentListCompleteTransmissionIndicator="true" setOfBooksListCompleteTransmissionIndicator="true" textCompleteTransmissionIndicator="true" attachmentFolderCompleteTransmissionIndicator="true" actionCode="01">
<ObjectNodeSenderTechnicalID/>
<ID>1</ID>
<ExternalReferenceID>OBJ_EXT_REF_93348187</ExternalReferenceID>
<Description>Company Car</Description>
<TypeCode>0002</TypeCode>
<SetOfBooks actionCode="01">
<SetOfBooksID>0002</SetOfBooksID>
<ROUOpeningBalanceAmount currencyCode="USD">10000</ROUOpeningBalanceAmount>
<PostingRelevanceCode>1</PostingRelevanceCode>
<ValuationTypeCode>2</ValuationTypeCode>
</SetOfBooks>
<SetOfBooks actionCode="01">
<SetOfBooksID>0004</SetOfBooksID>
<ROUOpeningBalanceAmount currencyCode="USD">10000</ROUOpeningBalanceAmount>
<PostingRelevanceCode>1</PostingRelevanceCode>
<ValuationTypeCode>2</ValuationTypeCode>
</SetOfBooks>
<OrganisationAssignment actionCode="01">
<CostObjectAssignmentTypeCode>1</CostObjectAssignmentTypeCode>
<CostCentreID>MDEC10000</CostCentreID>
<ValidityStartDate>2020-02-01</ValidityStartDate>
</OrganisationAssignment>
<Conditions actionCode="01">
<TypeCode>01</TypeCode>
<Amount currencyCode="USD">1000</Amount>
<ValidityStartDate>2020-02-01</ValidityStartDate>
<PaymentFormTypeCode>1</PaymentFormTypeCode>
<RecurranceFrequencyCode>3</RecurranceFrequencyCode>
<RecurranceOffsetMonth>1</RecurranceOffsetMonth>
<RecurranceOffsetDay>15</RecurranceOffsetDay>
<TaxData actionCode="01">
<Amount currencyCode="USD">500</Amount>
<TaxationCharacteristicsCode listID="US">500</TaxationCharacteristicsCode>
</TaxData>
<TaxData actionCode="01">
<Amount currencyCode="USD">500</Amount>
<TaxationCharacteristicsCode listID="US">501</TaxationCharacteristicsCode>
</TaxData>
</Conditions>
</ObjectItem>
<ObjectItem actionCode="01" conditionsListCompleteTransmissionIndicator="true" oganisationAssignmentListCompleteTransmissionIndicator="true" setOfBooksListCompleteTransmissionIndicator="true" textCompleteTransmissionIndicator="true" attachmentFolderCompleteTransmissionIndicator="true">
<ID>2</ID>
<ExternalReferenceID>OBJ_EXT_REF_93348188</ExternalReferenceID>
<Description>Company Mobile Phone</Description>
<TypeCode>0002</TypeCode>
<AutomaticSupplierInvoiceIndicator>false</AutomaticSupplierInvoiceIndicator>
<RightOfUseAssetUsageEndDate/>
<PaymentScheduleCreationStatusCode/>
<CashflowCreationStatusCode/>
<SetOfBooks actionCode="01">
<SetOfBooksID>0002</SetOfBooksID>
<ROUOpeningBalanceAmount currencyCode="USD">2000</ROUOpeningBalanceAmount>
<PostingRelevanceCode>1</PostingRelevanceCode>
<ValuationTypeCode>2</ValuationTypeCode>
</SetOfBooks>
<SetOfBooks actionCode="01">
<SetOfBooksID>0004</SetOfBooksID>
<ROUOpeningBalanceAmount currencyCode="USD">10000</ROUOpeningBalanceAmount>
<PostingRelevanceCode>1</PostingRelevanceCode>
<ValuationTypeCode>2</ValuationTypeCode>
</SetOfBooks>
<OrganisationAssignment actionCode="01">
<CostObjectAssignmentTypeCode>1</CostObjectAssignmentTypeCode>
<CostCentreID>MDEC10000</CostCentreID>
<ValidityStartDate>2020-02-01</ValidityStartDate>
</OrganisationAssignment>
<Conditions actionCode="01">
<TypeCode>01</TypeCode>
<Amount currencyCode="USD">1000</Amount>
<ValidityStartDate>2020-02-01</ValidityStartDate>
<PaymentFormTypeCode>1</PaymentFormTypeCode>
<RecurranceFrequencyCode>3</RecurranceFrequencyCode>
<RecurranceOffsetMonth>1</RecurranceOffsetMonth>
<RecurranceOffsetDay>20</RecurranceOffsetDay>
<TaxData actionCode="01">
<Amount currencyCode="USD">500</Amount>
<TaxationCharacteristicsCode listID="US">500</TaxationCharacteristicsCode>
</TaxData>
<TaxData actionCode="01">
<Amount currencyCode="USD">500</Amount>
<TaxationCharacteristicsCode listID="US">501</TaxationCharacteristicsCode>
</TaxData>
</Conditions>
</ObjectItem>
</LeaseContract>
</n0:LeaseContractBundleMaintainRequest_sync>
web service response
<n0:LeaseContractBundleMaintainConfirmation_sync xmlns:n0="http://sap.com/xi/SAPGlobal20/Global" xmlns:prx="urn:sap.com:proxy:ACL:/1SAI/TASD2CDFCA2CFB69FB0466B:804"> <LeaseContract> <ReferenceObjectNodeSenderTechnicalID>BOUMAJ1</ReferenceObjectNodeSenderTechnicalID> <ChangeStateID> 20200716061701.3994380</ChangeStateID> <UUID>00163e94-2a34-1eda-b1e5-7ea442ccfe3b</UUID> <LeaseContractID>00000000000000000000000000000000445</LeaseContractID> <CompanyID>MDEC10000</CompanyID> <VersionID>00000000000000000000000000000000</VersionID> </LeaseContract> </n0:LeaseContractBundleMaintainConfirmation_sync>
Structure of the request message has the following parameters based on which lease contracts can be created or updated:
LeaseContract
| Element | Remark |
|---|---|
| ID | Id of the Lease Contract |
| CompanyID | Lessee Company |
| VersionID | Version of lease contract |
| ExternalReferenceID | External reference of lease contract |
| Description | Description of lease contract |
| CurrencyCode | Currency of lease contract |
| InceptionDate | Inception Date of lease contract |
| LeaseStartDate | Start date of lease contract |
| LeaseFirstEndDate | First end date of lease contract |
| FrameAgreementID | Frame Agreement of lease contract |
| LifecycleStatusCode | Status of lease contract |
| LessorInternalID | Lessor ID |
| LessorContactPersonID | Lessor contact person id |
| EmployeeResposibleID | Lessor employee Responsible |
| DataOriginTypeCode | Should always be 3 |
| InvoiceOffsetDaysNumber | Invoice offset days on lease contract |
| TransitionTypeCode | Transition type of lease contract |
| InterestRatePercent | Interest for valuation of lease contract |
| InterestRateTypeCode | Interest rate applied for valuation of lease contract |
| ObjectItem | Leased Objects details of lease contract |
| RenewalTerm | Renewal details of lease contract |
| NoticeAgreement | Notice details of lease contract |
| Text | Notes on lease contract |
| AttachmentFolder | Attachments on lease contract |
ObjectItem
| Element | Remark |
|---|---|
| ExternalReferenceID | External reference of lease contract object |
| Description | Description of lease contract object |
| TypeCode | Object Type of lease contract object |
| AutomaticSupplierInvoiceIndicator | Automatically generate supplier invoices for lease contract object |
| RightOfUseAssetUsageEndDate | End of usage of lease contract object |
| PaymentScheduleCreationStatusCode | Payment schedule creation status of lease contract object |
| CashflowCreationStatusCode | Cash flow creation status of lease contract object |
| SetOfBooks | Set of books relevance details of lease contract object |
| OrganisationAssignment | Organizational Assignment details of lease contract object |
| Conditions | Conditions details of lease contract object |
| Text | Notes of lease contract object |
| AttachmentFolder | Attachments of lease contract object |
OrganisationAssignment
| Element | Remark |
|---|---|
| CostObjectAssignmentTypeCode | Account assignment type of Organizational assignments |
| CostCentreID | Cost center ID of Organizational assignments |
| ProjectTaskID | Project task ID of Organizational assignments |
| ValidityStartDate | Start date of Organizational assignments |
Conditions
| Element | Remark |
|---|---|
| TypeCode | Condition Type of lease contract object |
| Amount | Condition amount of lease contract object |
| ValidityStartDate | Condition valid from of lease contract object |
| PaymentFormTypeCode | Condition Payment form of lease contract object |
| RecurranceFrequencyCode | Recurrence for condition of lease contract object |
| RecurranceOffsetYear | Recurrence offset for yearly recurrence of lease contract object |
| RecurranceOffsetMonth | Recurrence offset for Monthly recurrence of lease contract object |
| RecurranceOffsetDay | Day of Month of condition recurrence of lease contract object |
| TaxData | Tax details of lease contract object |
RenewalTerm
| Element | Remark |
|---|---|
| Description | Renewal rule name of lease contract |
| TypeCode | Renewal mode of lease contract |
| RenewalDuration | Renewal period of lease contract |
| DueDate | Renewal due date of lease contract |
NoticeAgreement
| Element | Remark |
|---|---|
| Description | Notice Name of lease contract |
| NoticeDuration | Notice period of lease contract |
| DueDate | Notice due date of lease contract |
| GivingPartyTypeCode | Notice Contracting Party of lease contract |
The life cycle status of Lease Contract
| Code | Remark |
|---|---|
| 1 | In-Preparation |
| 2 | Ready For Release |
| 3 | Released |
| 4 | In-Revision |
| 5 | Cancelled |
| 6 | Terminated |
| 7 | Closed |
Transition type of Lease Contract
| Code | Remark |
|---|---|
| 2 | Cumulative A |
| 3 | Cumulative B |
Renewals mode of Lease Contract
| Code | Remark |
|---|---|
| 1 | Automatic |
| 2 | Option |
Notice giving party code of Lease Contract
| Code | Remark |
|---|---|
| 1 | Lessee |
| 2 | Lessor |
| 3 | Both |
Type code of Lease Object Item
| Code | Remark |
|---|---|
| 0001 | Land/Property |
| 0002 | Building |
| 0003 | Hardware |
| 0004 | Fixtures/Fittings |
| 0005 | Machinery |
| 0006 | Vehicles |
| 0007 | Location/Site |
| 0008 | Floor |
| 0009 | Room |
| 0010 | Equipment |
| 0011 | Office Equipment |
Payment schedule creation status of Lease Object Item
| Code | Remark |
|---|---|
| 1 | Not Started |
| 2 | Creation Successful |
Cashflow creation status of Lease Object Item
| Code | Remark |
|---|---|
| 1 | Not Started |
| 2 | Creation Successful |
Account assignment type code of Lease Object Item
| Code | Remark |
|---|---|
| 1 | Cost Center |
| 21 | Overhead Cost Project Task |
| 22 | Other Direct Cost Project Task |
Conditions type code of Lease Object Item
| Code | Remark |
|---|---|
| 01 | Lease Installment |
| 02 | Service Charge |
| 03 | Initial Cost |
| 04 | Residual Value |
| 05 | Penalty Payment |
| 06 | IFRS Incentive |
| 07 | Exercise Price |
| 08 | Estimated Cost |
Recurrence frequency code of Lease Object Item
| Code | Remark |
|---|---|
| 1 | One-time Payment |
| 2 | Daily |
| 3 | Monthly |
| 4 | Yearly |
Lease Valuation Type Code of Lease Object Item Set of Books Relevance
| Code | Remark |
|---|---|
| 1 | IFRS16 |
| 2 | ASC842 |
Relevance Code of Lease Contract Item Set of Books
| Code | Remark |
|---|---|
| 1 | Finance Lease |
| 2 | Operating Lease |
| 3 | Expense |
Payment Form Type Code of Lease Contract Conditions
| Code | Remark |
|---|---|
| 1 | In Advance |
| 2 | In Arrears |
Category Code of Attachment
| Category Code | Description |
|---|---|
| 2 | Document |
| 3 | Link |
Type Code of Text Collection
| TypeCode | Description |
|---|---|
| 10011 | Internal comment |
Example 1: Create a Lease contract in Ready for Release status
<n0:LeaseContractBundleMaintainRequest_sync xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader/>
<LeaseContract objectItemListCompleteTransmissionIndicator="true" renewalTermListCompleteTransmissionIndicator="true" noticeAgreementListCompleteTransmissionIndicator="true" textCompleteTransmissionIndicator="true" attachmentFolderCompleteTransmissionIndicator="true" actionCode="01">
<CompanyID>MDEC10000</CompanyID>
<ExternalReferenceID>EXT_REF_Z3348187</ExternalReferenceID>
<Description>Lease Contract for car lease</Description>
<CurrencyCode>USD</CurrencyCode>
<InceptionDate>2020-01-01</InceptionDate>
<LeaseStartDate>2020-02-01</LeaseStartDate>
<LeaseFirstEndDate>2021-12-31</LeaseFirstEndDate>
<LifecycleStatusCode>2</LifecycleStatusCode>
<LessorInternalID>MDEC2000</LessorInternalID>
<LessorContactPersonID>MDECP2000</LessorContactPersonID>
<EmployeeResposibleID>3107</EmployeeResposibleID>
<DataOriginTypeCode>3</DataOriginTypeCode>
<ContractTypeCode>1</ContractTypeCode>
<TransitionTypeCode>2</TransitionTypeCode>
<InterestRatePercent>2</InterestRatePercent>
<ObjectItem conditionsListCompleteTransmissionIndicator="true" oganisationAssignmentListCompleteTransmissionIndicator="true" setOfBooksListCompleteTransmissionIndicator="true" textCompleteTransmissionIndicator="true" attachmentFolderCompleteTransmissionIndicator="true" actionCode="01">
<ObjectNodeSenderTechnicalID/>
<ID>1</ID>
<ExternalReferenceID>OBJ_EXT_REF_Z3348187</ExternalReferenceID>
<Description>Company Car</Description>
<TypeCode>0002</TypeCode>
<SetOfBooks actionCode="01">
<SetOfBooksID>0002</SetOfBooksID>
<ROUOpeningBalanceAmount currencyCode="USD">10000</ROUOpeningBalanceAmount>
<PostingRelevanceCode>1</PostingRelevanceCode>
<ValuationTypeCode>2</ValuationTypeCode>
</SetOfBooks>
<SetOfBooks actionCode="01">
<SetOfBooksID>0004</SetOfBooksID>
<ROUOpeningBalanceAmount currencyCode="USD">10000</ROUOpeningBalanceAmount>
<PostingRelevanceCode>1</PostingRelevanceCode>
<ValuationTypeCode>2</ValuationTypeCode>
</SetOfBooks>
<OrganisationAssignment actionCode="01">
<CostObjectAssignmentTypeCode>1</CostObjectAssignmentTypeCode>
<CostCentreID>MDEC10000</CostCentreID>
<ValidityStartDate>2020-02-01</ValidityStartDate>
</OrganisationAssignment>
<Conditions actionCode="01">
<TypeCode>01</TypeCode>
<Amount currencyCode="USD">1000</Amount>
<ValidityStartDate>2020-02-01</ValidityStartDate>
<PaymentFormTypeCode>1</PaymentFormTypeCode>
<RecurranceFrequencyCode>3</RecurranceFrequencyCode>
<RecurranceOffsetMonth>1</RecurranceOffsetMonth>
<RecurranceOffsetDay>15</RecurranceOffsetDay>
<TaxData actionCode="01">
<Amount currencyCode="USD">500</Amount>
<TaxationCharacteristicsCode listID="US">500</TaxationCharacteristicsCode>
</TaxData>
<TaxData actionCode="01">
<Amount currencyCode="USD">500</Amount>
<TaxationCharacteristicsCode listID="US">501</TaxationCharacteristicsCode>
</TaxData>
</Conditions>
</ObjectItem>
<ObjectItem actionCode="01" conditionsListCompleteTransmissionIndicator="true" oganisationAssignmentListCompleteTransmissionIndicator="true" setOfBooksListCompleteTransmissionIndicator="true" textCompleteTransmissionIndicator="true" attachmentFolderCompleteTransmissionIndicator="true">
<ID>2</ID>
<ExternalReferenceID>OBJ_EXT_REF_Z3348188</ExternalReferenceID>
<Description>Company Mobile Phone</Description>
<TypeCode>0002</TypeCode>
<AutomaticSupplierInvoiceIndicator>false</AutomaticSupplierInvoiceIndicator>
<RightOfUseAssetUsageEndDate/>
<PaymentScheduleCreationStatusCode/>
<CashflowCreationStatusCode/>
<SetOfBooks actionCode="01">
<SetOfBooksID>0002</SetOfBooksID>
<ROUOpeningBalanceAmount currencyCode="USD">2000</ROUOpeningBalanceAmount>
<PostingRelevanceCode>1</PostingRelevanceCode>
<ValuationTypeCode>2</ValuationTypeCode>
</SetOfBooks>
<SetOfBooks actionCode="01">
<SetOfBooksID>0004</SetOfBooksID>
<ROUOpeningBalanceAmount currencyCode="USD">10000</ROUOpeningBalanceAmount>
<PostingRelevanceCode>1</PostingRelevanceCode>
<ValuationTypeCode>2</ValuationTypeCode>
</SetOfBooks>
<OrganisationAssignment actionCode="01">
<CostObjectAssignmentTypeCode>1</CostObjectAssignmentTypeCode>
<CostCentreID>MDEC10000</CostCentreID>
<ValidityStartDate>2020-02-01</ValidityStartDate>
</OrganisationAssignment>
<Conditions actionCode="01">
<TypeCode>01</TypeCode>
<Amount currencyCode="USD">1000</Amount>
<ValidityStartDate>2020-02-01</ValidityStartDate>
<PaymentFormTypeCode>1</PaymentFormTypeCode>
<RecurranceFrequencyCode>3</RecurranceFrequencyCode>
<RecurranceOffsetMonth>1</RecurranceOffsetMonth>
<RecurranceOffsetDay>20</RecurranceOffsetDay>
<TaxData actionCode="01">
<Amount currencyCode="USD">500</Amount>
<TaxationCharacteristicsCode listID="US">500</TaxationCharacteristicsCode>
</TaxData>
<TaxData actionCode="01">
<Amount currencyCode="USD">500</Amount>
<TaxationCharacteristicsCode listID="US">501</TaxationCharacteristicsCode>
</TaxData>
</Conditions>
</ObjectItem>
</LeaseContract>
</n0:LeaseContractBundleMaintainRequest_sync>
Example 1: Create a Lease contract in Released status
<n0:LeaseContractBundleMaintainRequest_sync xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader/>
<LeaseContract objectItemListCompleteTransmissionIndicator="true" renewalTermListCompleteTransmissionIndicator="true" noticeAgreementListCompleteTransmissionIndicator="true" textCompleteTransmissionIndicator="true" attachmentFolderCompleteTransmissionIndicator="true" actionCode="01">
<CompanyID>MDEC10000</CompanyID>
<ExternalReferenceID>EXT_REF_X3348187</ExternalReferenceID>
<Description>Lease Contract for car lease</Description>
<CurrencyCode>USD</CurrencyCode>
<InceptionDate>2020-01-01</InceptionDate>
<LeaseStartDate>2020-02-01</LeaseStartDate>
<LeaseFirstEndDate>2021-12-31</LeaseFirstEndDate>
<LifecycleStatusCode>3</LifecycleStatusCode>
<LessorInternalID>MDEC2000</LessorInternalID>
<LessorContactPersonID>MDECP2000</LessorContactPersonID>
<EmployeeResposibleID>3107</EmployeeResposibleID>
<DataOriginTypeCode>3</DataOriginTypeCode>
<ContractTypeCode>1</ContractTypeCode>
<TransitionTypeCode>2</TransitionTypeCode>
<InterestRatePercent>2</InterestRatePercent>
<ObjectItem conditionsListCompleteTransmissionIndicator="true" oganisationAssignmentListCompleteTransmissionIndicator="true" setOfBooksListCompleteTransmissionIndicator="true" textCompleteTransmissionIndicator="true" attachmentFolderCompleteTransmissionIndicator="true" actionCode="01">
<ObjectNodeSenderTechnicalID/>
<ID>1</ID>
<ExternalReferenceID>OBJ_EXT_REF_X3348187</ExternalReferenceID>
<Description>Company Car</Description>
<TypeCode>0002</TypeCode>
<SetOfBooks actionCode="01">
<SetOfBooksID>0002</SetOfBooksID>
<ROUOpeningBalanceAmount currencyCode="USD">10000</ROUOpeningBalanceAmount>
<PostingRelevanceCode>1</PostingRelevanceCode>
<ValuationTypeCode>2</ValuationTypeCode>
</SetOfBooks>
<SetOfBooks actionCode="01">
<SetOfBooksID>0004</SetOfBooksID>
<ROUOpeningBalanceAmount currencyCode="USD">10000</ROUOpeningBalanceAmount>
<PostingRelevanceCode>1</PostingRelevanceCode>
<ValuationTypeCode>2</ValuationTypeCode>
</SetOfBooks>
<OrganisationAssignment actionCode="01">
<CostObjectAssignmentTypeCode>1</CostObjectAssignmentTypeCode>
<CostCentreID>MDEC10000</CostCentreID>
<ValidityStartDate>2020-02-01</ValidityStartDate>
</OrganisationAssignment>
<Conditions actionCode="01">
<TypeCode>01</TypeCode>
<Amount currencyCode="USD">1000</Amount>
<ValidityStartDate>2020-02-01</ValidityStartDate>
<PaymentFormTypeCode>1</PaymentFormTypeCode>
<RecurranceFrequencyCode>3</RecurranceFrequencyCode>
<RecurranceOffsetMonth>1</RecurranceOffsetMonth>
<RecurranceOffsetDay>15</RecurranceOffsetDay>
<TaxData actionCode="01">
<Amount currencyCode="USD">500</Amount>
<TaxationCharacteristicsCode listID="US">500</TaxationCharacteristicsCode>
</TaxData>
<TaxData actionCode="01">
<Amount currencyCode="USD">500</Amount>
<TaxationCharacteristicsCode listID="US">501</TaxationCharacteristicsCode>
</TaxData>
</Conditions>
</ObjectItem>
<ObjectItem actionCode="01" conditionsListCompleteTransmissionIndicator="true" oganisationAssignmentListCompleteTransmissionIndicator="true" setOfBooksListCompleteTransmissionIndicator="true" textCompleteTransmissionIndicator="true" attachmentFolderCompleteTransmissionIndicator="true">
<ID>2</ID>
<ExternalReferenceID>OBJ_EXT_REF_X3348188</ExternalReferenceID>
<Description>Company Mobile Phone</Description>
<TypeCode>0002</TypeCode>
<AutomaticSupplierInvoiceIndicator>false</AutomaticSupplierInvoiceIndicator>
<RightOfUseAssetUsageEndDate/>
<PaymentScheduleCreationStatusCode/>
<CashflowCreationStatusCode/>
<SetOfBooks actionCode="01">
<SetOfBooksID>0002</SetOfBooksID>
<ROUOpeningBalanceAmount currencyCode="USD">2000</ROUOpeningBalanceAmount>
<PostingRelevanceCode>1</PostingRelevanceCode>
<ValuationTypeCode>2</ValuationTypeCode>
</SetOfBooks>
<SetOfBooks actionCode="01">
<SetOfBooksID>0004</SetOfBooksID>
<ROUOpeningBalanceAmount currencyCode="USD">10000</ROUOpeningBalanceAmount>
<PostingRelevanceCode>1</PostingRelevanceCode>
<ValuationTypeCode>2</ValuationTypeCode>
</SetOfBooks>
<OrganisationAssignment actionCode="01">
<CostObjectAssignmentTypeCode>1</CostObjectAssignmentTypeCode>
<CostCentreID>MDEC10000</CostCentreID>
<ValidityStartDate>2020-02-01</ValidityStartDate>
</OrganisationAssignment>
<Conditions actionCode="01">
<TypeCode>01</TypeCode>
<Amount currencyCode="USD">1000</Amount>
<ValidityStartDate>2020-02-01</ValidityStartDate>
<PaymentFormTypeCode>1</PaymentFormTypeCode>
<RecurranceFrequencyCode>3</RecurranceFrequencyCode>
<RecurranceOffsetMonth>1</RecurranceOffsetMonth>
<RecurranceOffsetDay>20</RecurranceOffsetDay>
<TaxData actionCode="01">
<Amount currencyCode="USD">500</Amount>
<TaxationCharacteristicsCode listID="US">500</TaxationCharacteristicsCode>
</TaxData>
<TaxData actionCode="01">
<Amount currencyCode="USD">500</Amount>
<TaxationCharacteristicsCode listID="US">501</TaxationCharacteristicsCode>
</TaxData>
</Conditions>
</ObjectItem>
</LeaseContract>
</n0:LeaseContractBundleMaintainRequest_sync>
| Release | Change Description | Details |
| 2008 | Documentation change | Updated sample scenarios |
| Description | Check lease contracts |
| Name | CheckMaintainBundle |
| Synchronous | yes |
| Release Status | Released |
To simulate the MAINTAIN_BUNDLE service interface operation of lease contract.
The web service request and response message types of the CheckMaintainBundle operation are the same as those of the MaintainBundle operation.
The explanations given there can therefore also be applied to the CheckMaintainBundle operation.