| Description | Manage Individual Products |
| Name | ManageRegisteredProductIn |
| Namespace | http://sap.com/xi/A1S/Global |
| Process Component Description | Product Data Maintenance |
| Process Component Name | ProductDataMaintenance |
| Process Component Namespace | http://sap.com/xi/AP/FO/Product/Global |
| Deployment Unit Description | Foundation |
| Endpoint Activation | By Scoping of Process Component | Operations |
| Release Status | Released |
An interface to maintain one or more Registered Product.
The web service interface Manage Registered Product In enables you to connect external applications to your SAP Business ByDesign system.
The inbound service interface enables you to create one or more Registered Product.
The web service interface Manage Registered Product In offers the operations CHECK_MAINTAIN_BUNDLE and MAINTAIN_BUNDLE.
Here is an example of a simple web service request:
Show full documentation
Show full documentation
<n0:ManageRegisteredProduct xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader>
<ID/>
<UUID/>
<ReferenceID/>
<ReferenceUUID/>
</BasicMessageHeader>
<RegisteredProduct actioncode="01">
<ObjectNodeSenderTechnicalID>498</ObjectNodeSenderTechnicalID>
<ChangeStateID/>
<UUID/>
<InternalID/>
<RegisteredProductID>YJ498</RegisteredProductID>
<ReferenceProductID>
<ProductTypeCode>1</ProductTypeCode>
<ProductIdentifierTypeCode>1</ProductIdentifierTypeCode>
<ProductID>MCF-0002</ProductID>
</ReferenceProductID>
<RegisteredProductDescription languageCode="EN">YJ498</RegisteredProductDescription>
<LifeCycleStatus>2</LifeCycleStatus>
<Warranty>
<WarrantyReferencedate>2017-05-24</WarrantyReferencedate>
<WarrantyKey>
<WarrantyID>MCG-0102</WarrantyID>
</WarrantyKey>
</Warranty>
<ParentRegisteredProduct>
<ParentRegisteredProductID>YJ001</ParentRegisteredProductID>
<ParentReferenceProductID>
<ProductTypeCode>1</ProductTypeCode>
<ProductIdentifierTypeCode>1</ProductIdentifierTypeCode>
<ProductID>MCF-0001</ProductID>
</ParentReferenceProductID>
</ParentRegisteredProduct>
<Account>
<PartyKey>
<PartyID>MC8000</PartyID>
</PartyKey>
</Account>
<Contact>
<PartyKey>
<PartyID>1003078</PartyID>
</PartyKey>
</Contact>
<Owner>
<PartyKey>
<PartyID>GCBAC20123</PartyID>
</PartyKey>
</Owner>
<ProductLocation>
<Country>CN</Country>
<CareOf>CO</CareOf>
<Building>Building</Building>
<Floor>Floor</Floor>
<Room>Room</Room>
<AddressLine1>11</AddressLine1>
<AddressLine2>22</AddressLine2>
<HouseNumber>9527</HouseNumber>
<Street>street</Street>
<AddressLine4>44</AddressLine4>
<AddressLine5>55</AddressLine5>
<City>City</City>
<DifferentCity>DiCity</DifferentCity>
<State>010</State>
<PostalCode>610041</PostalCode>
<District>district</District>
<County>County</County>
<TimeZone>UTC-7</TimeZone>
<CompanyPostalCode>610020</CompanyPostalCode>
<POBox>box</POBox>
<POBoxPostalCode></POBoxPostalCode>
<POBoxCity>PBCITY</POBoxCity>
<POBoxState>04</POBoxState>
<POBoxCountry>IN</POBoxCountry>
</ProductLocation>
</RegisteredProduct>
</n0:ManageRegisteredProduct>
Existence of referenced business documents:
The following business documents are only for reference and will not be created by the service operations. They must exist in the system already at the time the web service is called. They are:
• Party(Buyer Party,Employee Responsible Party,End Buyer Party,Requestor Part,Seller Party, etc.)
• Location (Receiving Site)
• Products
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 (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.
| 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. |
Note: Action code 01 (Create) 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 to 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.
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 un-interpretable 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. In addition, 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.
UUID generates automatically when create an instance and return to external application, leave empty in request payload.
UUID is unique key when action code is '02', that is required field in change mode.
Status Indicator represent an instruction to the status of the registered product.
| Status Indicator | Description |
|---|---|
| 1 | In preparation; it is initial status of registered product. |
| 2 | Active. |
| 3 | Blocked; it does not support blocked status when create an new registered product, when pass life cycle status code as 3 during creation it only creates as in preparation. |
Product Type Code represent a type of the product.
| Product Type Code | Description |
|---|---|
| 1 | Material, only allow here. |
| 2 | Service, but it's not allowed here. |
Product Identifier Type Code represent an identifier type of the product.
| Product Identifier Type Code | Description |
|---|---|
| 1 | Internal ID, only allow here. |
| 2 | Inventory ID, but it's not allowed here. |
Warranty would not be auto populated during creat, need to input manually.
| Index | ActoinCode | Input Account | Input Contact | Input Product Location | Final UI Account | Final UI Contact | Final UI Product Location | ||
|---|---|---|---|---|---|---|---|---|---|
| 1 | 01 | Input Value | NA | NA | Input Value | Account master data | Account master data | ||
| 2 | 01 | Input Value | Input Value | NA | Input Value | Input Value | Account master data | ||
| 3 | 01 | Input Value | NA | Input Value | Input Value | Account master data | Input Value | ||
| 4 | 01 | NA | Input Value | Input Value | NA | Input Value | Input Value | ||
| 5 | 01/02 | Input Value | Input Value | Input Value | Input Value | Input Value | Input Value | ||
| 6 | 02 | Input Value | NA(ExistValueInUI) | NA(ExistValueInUI) | Input Value | Remain unchanged | Remain unchanged | ||
| 7 | 02 | Input Value | NA(NoValueInUI) | NA(NoValueInUI) | Input Value | Account master data | Account master data | ||
| 8 | 02 | Input empty | NA(ExistValueInUI/NoValueInUI) | NA(ExistValueInUI/NoValueInUI) | Remove current data | Remove current data | Remove current data | ||
| 9 | 02 | Input empty | Input Value | Input Value | Remove current data | Input Value | Input Value | ||
| 10 | 02 | NA | Input Value | Input Value | Remain unchanged | Input Value | Input Value |
Example:Account
Input empty <Account></Account>.
Input NA not sending in payload.
Input value <Account>MC8000</Account>
Product Location represent the address information of registered product.
Most of the detail fields depend on country(CN, IN etc.) which selected.
State, the valid code depends on country, like 010 Beijing in value list when country is CN China.
Postal code, if country is CN China, length must have 6.
Time Zone, the input value as UTC-7, UTC-8 etc.
Both P.O. Box State and P.O. Box country are same as country, state fiels.
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 runtimes 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:
<n0:ManageRegisteredProduct xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader>
<ID/>
<UUID/>
<ReferenceID/>
<ReferenceUUID/>
</BasicMessageHeader>
<RegisteredProduct actioncode="01">
<ObjectNodeSenderTechnicalID>498</ObjectNodeSenderTechnicalID>
<ChangeStateID/>
<UUID/>
<InternalID/>
<RegisteredProductID>YJ498</RegisteredProductID>
<ReferenceProductID>
<ProductTypeCode>1</ProductTypeCode>
<ProductIdentifierTypeCode>1</ProductIdentifierTypeCode>
<ProductID>MCF-0002</ProductID>
</ReferenceProductID>
<RegisteredProductDescription languageCode="EN">YJ498</RegisteredProductDescription>
<LifeCycleStatus>2</LifeCycleStatus>
<Warranty>
<WarrantyReferencedate>2017-05-24</WarrantyReferencedate>
<WarrantyKey>
<WarrantyID>MCG-0102</WarrantyID>
</WarrantyKey>
</Warranty>
<ParentRegisteredProduct>
<ParentRegisteredProductID>YJ001</ParentRegisteredProductID>
<ParentReferenceProductID>
<ProductTypeCode>1</ProductTypeCode>
<ProductIdentifierTypeCode>1</ProductIdentifierTypeCode>
<ProductID>MCF-0001</ProductID>
</ParentReferenceProductID>
</ParentRegisteredProduct>
<Account>
<PartyKey>
<PartyID>MC8000</PartyID>
</PartyKey>
</Account>
<Contact>
<PartyKey>
<PartyID>1003078</PartyID>
</PartyKey>
</Contact>
<Owner>
<PartyKey>
<PartyID>GCBAC20123</PartyID>
</PartyKey>
</Owner>
<ProductLocation>
<Country>CN</Country>
<CareOf>CO</CareOf>
<Building>Building</Building>
<Floor>Floor</Floor>
<Room>Room</Room>
<AddressLine1>11</AddressLine1>
<AddressLine2>22</AddressLine2>
<HouseNumber>9527</HouseNumber>
<Street>street</Street>
<AddressLine4>44</AddressLine4>
<AddressLine5>55</AddressLine5>
<City>City</City>
<DifferentCity>DiCity</DifferentCity>
<State>010</State>
<PostalCode>610041</PostalCode>
<District>district</District>
<County>County</County>
<TimeZone>UTC-7</TimeZone>
<CompanyPostalCode>610020</CompanyPostalCode>
<POBox>box</POBox>
<POBoxPostalCode></POBoxPostalCode>
<POBoxCity>PBCITY</POBoxCity>
<POBoxState>04</POBoxState>
<POBoxCountry>IN</POBoxCountry>
</ProductLocation>
</RegisteredProduct>
<RegisteredProduct actioncode="02">
<ObjectNodeSenderTechnicalID>499</ObjectNodeSenderTechnicalID>
<ChangeStateID/>
<UUID>00163e07-3d62-1ee7-a5ef-111500df2909</UUID>
<InternalID/>
<RegisteredProductID>YJ499</RegisteredProductID>
<ReferenceProductID>
<ProductTypeCode>1</ProductTypeCode>
<ProductIdentifierTypeCode>1</ProductIdentifierTypeCode>
<ProductID>MCF-0002</ProductID>
</ReferenceProductID>
<RegisteredProductDescription languageCode="EN">YJ499-2</RegisteredProductDescription>
<LifeCycleStatus>2</LifeCycleStatus>
<Warranty>
<WarrantyReferencedate>2017-05-24</WarrantyReferencedate>
<WarrantyKey>
<WarrantyID>MCG-0102</WarrantyID>
</WarrantyKey>
</Warranty>
<ParentRegisteredProduct>
<ParentRegisteredProductID>YJ001</ParentRegisteredProductID>
<ParentReferenceProductID>
<ProductTypeCode>1</ProductTypeCode>
<ProductIdentifierTypeCode>1</ProductIdentifierTypeCode>
<ProductID>MCF-0001</ProductID>
</ParentReferenceProductID>
</ParentRegisteredProduct>
<Account>
<PartyKey>
<PartyID>MC8000</PartyID>
</PartyKey>
</Account>
<Contact>
<PartyKey>
<PartyID>1003078</PartyID>
</PartyKey>
</Contact>
<Owner>
<PartyKey>
<PartyID>GCBAC20123</PartyID>
</PartyKey>
</Owner>
<ProductLocation>
<Country>CN</Country>
<CareOf>CO</CareOf>
<Building>Building</Building>
<Floor>Floor</Floor>
<Room>Room</Room>
<AddressLine1>11</AddressLine1>
<AddressLine2>22</AddressLine2>
<HouseNumber>9527</HouseNumber>
<Street>street</Street>
<AddressLine4>44</AddressLine4>
<AddressLine5>55</AddressLine5>
<City>City</City>
<DifferentCity>DiCity</DifferentCity>
<State>010</State>
<PostalCode>610041</PostalCode>
<District>district</District>
<County>County</County>
<TimeZone>UTC-7</TimeZone>
<CompanyPostalCode>610020</CompanyPostalCode>
<POBox>box</POBox>
<POBoxPostalCode></POBoxPostalCode>
<POBoxCity>PBCITY</POBoxCity>
<POBoxState>04</POBoxState>
<POBoxCountry>IN</POBoxCountry>
</ProductLocation>
</RegisteredProduct>
</n0:ManageRegisteredProduct>
| Description | Manage individual products |
| Name | MaintainBundle |
| Synchronous | yes |
| Release Status | Released |
To create or update Registered Product in Business ByDesign system.
<n0:ManageRegisteredProduct xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader>
<ID/>
<UUID/>
<ReferenceID/>
<ReferenceUUID/>
</BasicMessageHeader>
<RegisteredProduct actioncode="01">
<ObjectNodeSenderTechnicalID>498</ObjectNodeSenderTechnicalID>
<ChangeStateID/>
<UUID/>
<InternalID/>
<RegisteredProductID>YJ498</RegisteredProductID>
<ReferenceProductID>
<ProductTypeCode>1</ProductTypeCode>
<ProductIdentifierTypeCode>1</ProductIdentifierTypeCode>
<ProductID>MCF-0002</ProductID>
</ReferenceProductID>
<RegisteredProductDescription languageCode="EN">YJ498</RegisteredProductDescription>
<LifeCycleStatus>2</LifeCycleStatus>
<Warranty>
<WarrantyReferencedate>2017-05-24</WarrantyReferencedate>
<WarrantyKey>
<WarrantyID>MCG-0102</WarrantyID>
</WarrantyKey>
</Warranty>
<ParentRegisteredProduct>
<ParentRegisteredProductID>YJ001</ParentRegisteredProductID>
<ParentReferenceProductID>
<ProductTypeCode>1</ProductTypeCode>
<ProductIdentifierTypeCode>1</ProductIdentifierTypeCode>
<ProductID>MCF-0001</ProductID>
</ParentReferenceProductID>
</ParentRegisteredProduct>
<Account>
<PartyKey>
<PartyID>MC8000</PartyID>
</PartyKey>
</Account>
<Contact>
<PartyKey>
<PartyID>1003078</PartyID>
</PartyKey>
</Contact>
<Owner>
<PartyKey>
<PartyID>GCBAC20123</PartyID>
</PartyKey>
</Owner>
<ProductLocation>
<Country>CN</Country>
<CareOf>CO</CareOf>
<Building>Building</Building>
<Floor>Floor</Floor>
<Room>Room</Room>
<AddressLine1>11</AddressLine1>
<AddressLine2>22</AddressLine2>
<HouseNumber>9527</HouseNumber>
<Street>street</Street>
<AddressLine4>44</AddressLine4>
<AddressLine5>55</AddressLine5>
<City>City</City>
<DifferentCity>DiCity</DifferentCity>
<State>010</State>
<PostalCode>610041</PostalCode>
<District>district</District>
<County>County</County>
<TimeZone>UTC-7</TimeZone>
<CompanyPostalCode>610020</CompanyPostalCode>
<POBox>box</POBox>
<POBoxPostalCode></POBoxPostalCode>
<POBoxCity>PBCITY</POBoxCity>
<POBoxState>04</POBoxState>
<POBoxCountry>IN</POBoxCountry>
</ProductLocation>
</RegisteredProduct>
</n0:ManageRegisteredProduct>
<n0:ManageRegisteredProduct xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader>
<ID/>
<UUID/>
<ReferenceID/>
<ReferenceUUID/>
</BasicMessageHeader>
<RegisteredProduct actioncode="02">
<ObjectNodeSenderTechnicalID>499</ObjectNodeSenderTechnicalID>
<ChangeStateID/>
<UUID>00163e07-3d62-1ee7-a5ef-111500df2909</UUID>
<InternalID/>
<RegisteredProductID>YJ499</RegisteredProductID>
<ReferenceProductID>
<ProductTypeCode>1</ProductTypeCode>
<ProductIdentifierTypeCode>1</ProductIdentifierTypeCode>
<ProductID>MCF-0002</ProductID>
</ReferenceProductID>
<RegisteredProductDescription languageCode="EN">YJ499-2</RegisteredProductDescription>
<LifeCycleStatus>2</LifeCycleStatus>
<Warranty>
<WarrantyReferencedate>2017-05-24</WarrantyReferencedate>
<WarrantyKey>
<WarrantyID>MCG-0102</WarrantyID>
</WarrantyKey>
</Warranty>
<ParentRegisteredProduct>
<ParentRegisteredProductID>YJ001</ParentRegisteredProductID>
<ParentReferenceProductID>
<ProductTypeCode>1</ProductTypeCode>
<ProductIdentifierTypeCode>1</ProductIdentifierTypeCode>
<ProductID>MCF-0001</ProductID>
</ParentReferenceProductID>
</ParentRegisteredProduct>
<Account>
<PartyKey>
<PartyID>MC8000</PartyID>
</PartyKey>
</Account>
<Contact>
<PartyKey>
<PartyID>1003078</PartyID>
</PartyKey>
</Contact>
<Owner>
<PartyKey>
<PartyID>GCBAC20123</PartyID>
</PartyKey>
</Owner>
<ProductLocation>
<Country>CN</Country>
<CareOf>CO</CareOf>
<Building>Building</Building>
<Floor>Floor</Floor>
<Room>Room</Room>
<AddressLine1>11</AddressLine1>
<AddressLine2>22</AddressLine2>
<HouseNumber>9527</HouseNumber>
<Street>street</Street>
<AddressLine4>44</AddressLine4>
<AddressLine5>55</AddressLine5>
<City>City</City>
<DifferentCity>DiCity</DifferentCity>
<State>010</State>
<PostalCode>610041</PostalCode>
<District>district</District>
<County>County</County>
<TimeZone>UTC-7</TimeZone>
<CompanyPostalCode>610020</CompanyPostalCode>
<POBox>box</POBox>
<POBoxPostalCode></POBoxPostalCode>
<POBoxCity>PBCITY</POBoxCity>
<POBoxState>04</POBoxState>
<POBoxCountry>IN</POBoxCountry>
</ProductLocation>
</RegisteredProduct>
</n0:ManageRegisteredProduct>
| Description | Check individual products |
| Name | CheckMaintainBundle |
| Synchronous | yes |
| Release Status | Released |
To simulate create and update on Registered Product in Business ByDesign system.
<n0:ManageRegisteredProduct xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader>
<ID/>
<UUID/>
<ReferenceID/>
<ReferenceUUID/>
</BasicMessageHeader>
<RegisteredProduct actioncode="01">
<ObjectNodeSenderTechnicalID>498</ObjectNodeSenderTechnicalID>
<ChangeStateID/>
<UUID/>
<InternalID/>
<RegisteredProductID>YJ498</RegisteredProductID>
<ReferenceProductID>
<ProductTypeCode>1</ProductTypeCode>
<ProductIdentifierTypeCode>1</ProductIdentifierTypeCode>
<ProductID>MCF-0002</ProductID>
</ReferenceProductID>
<RegisteredProductDescription languageCode="EN">YJ498</RegisteredProductDescription>
<LifeCycleStatus>2</LifeCycleStatus>
<Warranty>
<WarrantyReferencedate>2017-05-24</WarrantyReferencedate>
<WarrantyKey>
<WarrantyID>MCG-0102</WarrantyID>
</WarrantyKey>
</Warranty>
<ParentRegisteredProduct>
<ParentRegisteredProductID>YJ001</ParentRegisteredProductID>
<ParentReferenceProductID>
<ProductTypeCode>1</ProductTypeCode>
<ProductIdentifierTypeCode>1</ProductIdentifierTypeCode>
<ProductID>MCF-0001</ProductID>
</ParentReferenceProductID>
</ParentRegisteredProduct>
<Account>
<PartyKey>
<PartyID>MC8000</PartyID>
</PartyKey>
</Account>
<Contact>
<PartyKey>
<PartyID>1003078</PartyID>
</PartyKey>
</Contact>
<Owner>
<PartyKey>
<PartyID>GCBAC20123</PartyID>
</PartyKey>
</Owner>
<ProductLocation>
<Country>CN</Country>
<CareOf>CO</CareOf>
<Building>Building</Building>
<Floor>Floor</Floor>
<Room>Room</Room>
<AddressLine1>11</AddressLine1>
<AddressLine2>22</AddressLine2>
<HouseNumber>9527</HouseNumber>
<Street>street</Street>
<AddressLine4>44</AddressLine4>
<AddressLine5>55</AddressLine5>
<City>City</City>
<DifferentCity>DiCity</DifferentCity>
<State>010</State>
<PostalCode>610041</PostalCode>
<District>district</District>
<County>County</County>
<TimeZone>UTC-7</TimeZone>
<CompanyPostalCode>610020</CompanyPostalCode>
<POBox>box</POBox>
<POBoxPostalCode></POBoxPostalCode>
<POBoxCity>PBCITY</POBoxCity>
<POBoxState>04</POBoxState>
<POBoxCountry>IN</POBoxCountry>
</ProductLocation>
</RegisteredProduct>
</n0:ManageRegisteredProduct>
<n0:ManageRegisteredProduct xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader>
<ID/>
<UUID/>
<ReferenceID/>
<ReferenceUUID/>
</BasicMessageHeader>
<RegisteredProduct actioncode="02">
<ObjectNodeSenderTechnicalID>499</ObjectNodeSenderTechnicalID>
<ChangeStateID/>
<UUID>00163e07-3d62-1ee7-a5ef-111500df2909</UUID>
<InternalID/>
<RegisteredProductID>YJ499</RegisteredProductID>
<ReferenceProductID>
<ProductTypeCode>1</ProductTypeCode>
<ProductIdentifierTypeCode>1</ProductIdentifierTypeCode>
<ProductID>MCF-0002</ProductID>
</ReferenceProductID>
<RegisteredProductDescription languageCode="EN">YJ499-2</RegisteredProductDescription>
<LifeCycleStatus>2</LifeCycleStatus>
<Warranty>
<WarrantyReferencedate>2017-05-24</WarrantyReferencedate>
<WarrantyKey>
<WarrantyID>MCG-0102</WarrantyID>
</WarrantyKey>
</Warranty>
<ParentRegisteredProduct>
<ParentRegisteredProductID>YJ001</ParentRegisteredProductID>
<ParentReferenceProductID>
<ProductTypeCode>1</ProductTypeCode>
<ProductIdentifierTypeCode>1</ProductIdentifierTypeCode>
<ProductID>MCF-0001</ProductID>
</ParentReferenceProductID>
</ParentRegisteredProduct>
<Account>
<PartyKey>
<PartyID>MC8000</PartyID>
</PartyKey>
</Account>
<Contact>
<PartyKey>
<PartyID>1003078</PartyID>
</PartyKey>
</Contact>
<Owner>
<PartyKey>
<PartyID>GCBAC20123</PartyID>
</PartyKey>
</Owner>
<ProductLocation>
<Country>CN</Country>
<CareOf>CO</CareOf>
<Building>Building</Building>
<Floor>Floor</Floor>
<Room>Room</Room>
<AddressLine1>11</AddressLine1>
<AddressLine2>22</AddressLine2>
<HouseNumber>9527</HouseNumber>
<Street>street</Street>
<AddressLine4>44</AddressLine4>
<AddressLine5>55</AddressLine5>
<City>City</City>
<DifferentCity>DiCity</DifferentCity>
<State>010</State>
<PostalCode>610041</PostalCode>
<District>district</District>
<County>County</County>
<TimeZone>UTC-7</TimeZone>
<CompanyPostalCode>610020</CompanyPostalCode>
<POBox>box</POBox>
<POBoxPostalCode></POBoxPostalCode>
<POBoxCity>PBCITY</POBoxCity>
<POBoxState>04</POBoxState>
<POBoxCountry>IN</POBoxCountry>
</ProductLocation>
</RegisteredProduct>
</n0:ManageRegisteredProduct>