| Description | Query Identified Stocks |
| Name | QueryIdentifiedStocksIn |
| 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 query identified stocks from a source system.
The web service interface Query IdentifiedStocks In enables you to connect external applications to your SAP Business ByDesign system and to query Identified Stock in your system. The web service interface Query IdentifiedStocks In is relevant if your company wants to access identified stock data from external applications.
You can view and track identified stocks at the Identified Stock view of the Planning and Production Master Data work center
Query selection parameters are mainly exposed as select options or ranges, with an inclusion/exclusion code, interval boundary type code, lower boundary value, and upper boundary value.
The inclusion/exclusion code (element name InclusionExclusionCode) specifies the inclusion or exclusion of a set in a result set.
| Inclusion Exclusion Code | Description |
|---|---|
| E | Excluding |
| I | Including |
The interval boundary type code (element name IntervalBoundaryTypeCode) is used to describe intervals by their boundaries. Depending on the operator, the lower boundary value or both boundary values are relevant.
| Interval Boundary Type Code | Name | Description | Logical Operator |
|---|---|---|---|
| 1 | Equal to | Single Value | =X |
| 2 | Between(Excluding upper boundary) | Interval with closed lower and open upper boundary | [X, Y) |
| 3 | Between | Interval with open lower and open upper boundary | (X, Y) |
| 4 | Between (excluding both boundaries) | Interval with open lower and open upper boundary | (X, Y) |
| 5 | Between (excluding lower boundary) | Interval with open lower and closed upper boundary | (X, Y] |
| 6 | Less than | Interval with unlimited lower and open upper boundary | < X |
| 7 | Less than or Equal to | Interval with unlimited lower and closed upper boundary | <= X |
| 8 | Greater than | Interval with open lower and unlimited upper boundary | > X |
| 9 | Greater than or Equal to | Interval with closed lower and unlimited upper boundary | = X |
Before a query is executed on identified stock, instance of identified stock has to be created and maintained first.
Action codes represent an instruction to the recipient of the web service request to process transmitted message node elements.
The action code to be used is QUERY_BY_ELEMENTS.
Optional leaf elements in request messages that are not transmitted within a web service request are not considered while querying. Therefore, any value of missing parameters would meet the comparison.
Query operation is stateless synchronous web service operation. 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.
The structure of the request message type consists of two parts:
• Selection parameters for the query.
• Processing conditions. This specifies the limit on the output i.e number of records returned. You can also specify if you want unlimited number of records.
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:
• Find Identified Stock based on certain set of information like supplier ID etc.
This finds the Identified Stock that has specific ID.
<n0:IdentifiedStockQueryMessage_sync xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <IdentifiedStockSelectionByElements> <SelectionByIdentifiedStockID> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>1</IntervalBoundaryTypeCode> <LowerBoundaryIdentifier>ISTOCK_RTS_01</LowerBoundaryIdentifier> </SelectionByIdentifiedStockID> <SelectionByIdentifiedStockID> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>1</IntervalBoundaryTypeCode> <LowerBoundaryIdentifier>BAT010108-MX09</LowerBoundaryIdentifier> </SelectionByIdentifiedStockID> </IdentifiedStockSelectionByElements> <ProcessingConditions> <QueryHitsMaximumNumberValue>150</QueryHitsMaximumNumberValue> <QueryHitsUnlimitedIndicator>false</QueryHitsUnlimitedIndicator> <LastReturnedObjectID/> </ProcessingConditions> </n0:IdentifiedStockQueryMessage_sync>
This finds the Identified Stock that has specific supplier.
<n0:IdentifiedStockQueryMessage_sync xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <IdentifiedStockSelectionByElements> <SelectionBySupplierIDPartyID> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>1</IntervalBoundaryTypeCode> <LowerBoundaryIdentifier>MC2000</LowerBoundaryIdentifier> </SelectionBySupplierIDPartyID> </IdentifiedStockSelectionByElements> <ProcessingConditions> <QueryHitsMaximumNumberValue>150</QueryHitsMaximumNumberValue> <QueryHitsUnlimitedIndicator>false</QueryHitsUnlimitedIndicator> <LastReturnedObjectID/> </ProcessingConditions> </n0:IdentifiedStockQueryMessage_sync>
| Description | Find identified stocks |
| Name | QueryByElements |
| Synchronous | yes |
| Release Status | Released |
QueryIdentifiedStocksIn interface allows to query on existing identified stocks in the system
The request message of the QueryByElements contain two parts: Body and Processing Conditions. Body comprises of the various parameters on which Identified Stocks can be queried. Details on these parameters is discussed in the following sub-sections. Processing conditions control the execution of query. For example, you can specify if you want a certain number of records as output or unlimited records should be shown.
The response message contains the main information of identified stocks along with the processing conditions. The processing condition here indicates that how many records are returned and if there are any more existing records, which meet the criteria but not fetched.
The search can contain complex criteria instead of having simple equation. You can get results based on equal to or a range or less than or greater than logical operations. These type codes should be specified in the request message.
Get the detail information of identified stocks according to the search parameters
The web service interface QueryIdentifiedStocksIn offers the operation QueryByElements, which is used to query for one or more instances of identified stocks based on the query filter parameters passed.
Name : QueryIdentifiedStocksIn (II_QUERY_ISTOCK_IN)
Operation : QueryByElements (QUERY_BY_ELEMENTS)
Package : AP_FO_COMPOUNDSERV_IST_PRX
Implementing Process agent : QUERY_ISTOCK_BUNDLE
Leading BO Name : IdentifiedStock (IDENTIFIED_STOCK)
Query selection parameters are mainly exposed as select options or ranges, with an inclusion/exclusion code, interval boundary type code, lower boundary value, and upper boundary value.
The inclusion/exclusion code (element name InclusionExclusionCode) specifies the inclusion or exclusion of a set in a result set.
| Inclusion Exclusion Code | Description |
|---|---|
| E | Excluding |
| I | Including |
The interval boundary type code (element name IntervalBoundaryTypeCode) is used to describe intervals by their boundaries. Depending on the operator, the lower boundary value or both boundary values are relevant.
| Interval Boundary Type Code | Name | Description | Logical Operator |
|---|---|---|---|
| 1 | Equal to | Single Value | =X |
| 2 | Between(Excluding upper boundary) | Interval with closed lower and open upper boundary | [X, Y) |
| 3 | Between | Interval with open lower and open upper boundary | (X, Y) |
| 4 | Between (excluding both boundaries) | Interval with open lower and open upper boundary | (X, Y) |
| 5 | Between (excluding lower boundary) | Interval with open lower and closed upper boundary | (X, Y] |
| 6 | Less than | Interval with unlimited lower and open upper boundary | < X |
| 7 | Less than or Equal to | Interval with unlimited lower and closed upper boundary | <= X |
| 8 | Greater than | Interval with open lower and unlimited upper boundary | > X |
| 9 | Greater than or Equal to | Interval with closed lower and unlimited upper boundary | = X |
The request message of the operation QueryByElements contains the IdentifiedStockSelectionByElements node that groups all possible selection parameters.
Below is the list of available selection parameters:
| SEL_BY_ID | SelectionByIdentifiedStockID |
| SEL_BY_EXTERNAL_ID | SelectionByExternalIdentifiedStockID |
| SEL_BY_SEARCH_TEXT | SelectionBySearchText |
| SEL_BY_IDENTIFIED_STOCK_DESCRI | SelectionByIdentifiedStockDescription |
| SEL_BY_SUPPLIER_ID | SelectionBySupplierIDPartyID |
| SEL_BY_STATUS | SelectionByLifeCycleStatusCode |
| SEL_BY_IDENTIFIED_STOCK_TYPE_C | SelectionByIdentifiedStockTypeCode |
| SEL_BY_PVL_TYPE_CODE | SelectionByProductValuationLevelTypeCode |
| SEL_BY_PRODUCTION_DATE_TIME | SelectionByProductionDateTime |
| SEL_BY_EXPIRATION_DATE_TIME | SelectionByExpirationDateTime |
| SEL_BY_PRODUCT_ID | SelectionByMaterialKeyProductID |
| SEL_BY_PRS_ID | SelectionByProductRequirementSpecificationKeyRequirementSpecificationID |
| SEL_BY_CREATION_DATE_TIME | SelectionByAdministrativeDataCreationDateTime |
| SEL_BY_LAST_CHANGE_DATE_TIME | SelectionByAdministrativeDataLastChangeDateTime |
| SEL_BY_BATCH_MANAGED_INDICATOR | SelectionByBatchManagedIndicator |
The response contains the list of found identified stocks, log items, and processing conditions.
In the IdentifiedStock node, all found identified stocks are contained according to the selection parameters provided in the query request.
Below is the list of available identified stock elements and their corresponding business contexts with the UI.
Identified Stock
The following are the elements of this node:
| Elements | Description |
|---|---|
| ISTOCK_ID | Unique identifier of a identified stock |
| EXTERNAL_ISTOCK_ID | External identifier of a identified stock |
| PRODUCT_ID | Product ID, which is assigned to the identified stock |
| PRODUCTION_DATE_TIME | Production Date Time of identified stock |
| EXPIRATION_DATE_TIME | Expiration Date Time of identified stock |
| SUPPLIER_ID | Supplier ID assigned to identified stock |
| PRS_KEY | Product Requirement Specification Key assigned to identified stock |
| STATUS | Life cycle status of identified stock |
| ISTOCK_DESCRIPTION | Descriptions of identified stock |
| QUANTITY_CONVERSION | Quantity Conversion of identified stock |
| ATTACHMENT_FOLDER | Attachment of identified stock |
| TEXT_COLLECTION | Note of identified stock |
Below is the coded representation of the statuses used in the IdentifiedStock node:
Life Cycle Status
| Code Value | Description |
|---|---|
| 1 | In Preparation |
| 2 | Active |
| 3 | Blocked |
| 4 | Obsolete |
Identified Stock Description
The following are the elements of this node:
| Elements | Description |
|---|---|
| LANGUAGE_CODE | Language Code |
| CONTENT | Description Content |
Quantity Conversion
The following are the elements of this node:
| Elements | Description |
|---|---|
| QUANTITY | Base Quantity |
| CORRESPONDING_QUANTITY | Corresponding Quantity |
Query Identified Stock with specific IStock ID
<n0:IdentifiedStockQueryMessage_sync xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <IdentifiedStockSelectionByElements> <SelectionByIdentifiedStockID> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>1</IntervalBoundaryTypeCode> <LowerBoundaryIdentifier>ISTOCK_RTS_01</LowerBoundaryIdentifier> </SelectionByIdentifiedStockID> <SelectionByIdentifiedStockID> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>1</IntervalBoundaryTypeCode> <LowerBoundaryIdentifier>BAT010108-MX09</LowerBoundaryIdentifier> </SelectionByIdentifiedStockID> </IdentifiedStockSelectionByElements> <ProcessingConditions> <QueryHitsMaximumNumberValue>150</QueryHitsMaximumNumberValue> <QueryHitsUnlimitedIndicator>false</QueryHitsUnlimitedIndicator> <LastReturnedObjectID/> </ProcessingConditions> </n0:IdentifiedStockQueryMessage_sync>
Show full documentation
Show full documentation
<n0:IdentifiedStockQueryResponseMessage xmlns:n0="http://sap.com/xi/SAPGlobal20/Global" xmlns:prx="urn:sap.com:proxy:ACL:/1SAI/TASA3C59DD8D844E17877AE:804">
<ProcessingConditions>
<ReturnedQueryHitsNumberValue>2</ReturnedQueryHitsNumberValue>
<MoreHitsAvailableIndicator>false</MoreHitsAvailableIndicator>
<LastReturnedObjectID>00300571C92402DBBFBCA5C5100B816D</LastReturnedObjectID>
</ProcessingConditions>
<Log/>
<IdentifiedStock>
<IdentifiedStockID>ISTOCK_RTS_01</IdentifiedStockID>
<ExternalIdentifiedStockID>2344</ExternalIdentifiedStockID>
<ProductID>MCA-0009</ProductID>
<ProductionDateTime>2017-12-01T18:08:00Z</ProductionDateTime>
<ExpirationDateTime>2018-02-24T17:30:00Z</ExpirationDateTime>
<SupplierID>
<PartyTypeCode>147</PartyTypeCode>
<PartyID>MC2000</PartyID>
</SupplierID>
<LifeCycleStatusCode>
<LifeCycleStatusCode>2</LifeCycleStatusCode>
</LifeCycleStatusCode>
<Description languageCode="EN">Testing RTS for Identified Stock</Description>
<AttachmentFolder>
<UUID>00163e07-3d68-1ee8-82ca-e8243f5dcb41</UUID>
<Document>
<UUID>00163e07-3d62-1ee8-82e4-2adf6a4725ff</UUID>
<VersionID>0</VersionID>
<SystemAdministrativeData>
<CreationDateTime>2018-02-06T09:37:28.956748Z</CreationDateTime>
<CreationIdentityUUID>00163e07-3d66-1ee7-ace1-b4fb8fef5e9f</CreationIdentityUUID>
<LastChangeDateTime>2018-02-06T09:37:28.956748Z</LastChangeDateTime>
<LastChangeIdentityUUID>00163e07-3d66-1ee7-ace1-b4fb8fef5e9f</LastChangeIdentityUUID>
</SystemAdministrativeData>
<VisibleIndicator>true</VisibleIndicator>
<CategoryCode>3</CategoryCode>
<TypeCode>10006</TypeCode>
<PathName>/BOAttachments/00163E073D681EE882CAE8243F5DCB41/888</PathName>
<Name>888</Name>
<AlternativeName>888</AlternativeName>
<ExternalLinkWebURI>http://888</ExternalLinkWebURI>
<FileContentURI>http://888</FileContentURI>
</Document>
<Document>
<UUID>00163e07-3d68-1ee8-82ca-e953c7492b6a</UUID>
<VersionID>0</VersionID>
<SystemAdministrativeData>
<CreationDateTime>2018-02-05T09:31:17.686127Z</CreationDateTime>
<CreationIdentityUUID>00163e07-3d66-1ee7-ace1-b4fb8fef5e9f</CreationIdentityUUID>
<LastChangeDateTime>2018-02-05T09:31:17.686127Z</LastChangeDateTime>
<LastChangeIdentityUUID>00163e07-3d66-1ee7-ace1-b4fb8fef5e9f</LastChangeIdentityUUID>
</SystemAdministrativeData>
<VisibleIndicator>true</VisibleIndicator>
<CategoryCode>3</CategoryCode>
<TypeCode>10006</TypeCode>
<PathName>/BOAttachments/00163E073D681EE882CAE8243F5DCB41/www.163.com</PathName>
<Name>www.163.com</Name>
<AlternativeName>163</AlternativeName>
<Description>rwqrwqre</Description>
<ExternalLinkWebURI>http://www.163.com</ExternalLinkWebURI>
<FileContentURI>http://www.163.com</FileContentURI>
</Document>
</AttachmentFolder>
<TextCollection>
<UUID>00163e07-3d68-1ee8-82ca-e8243f5beb41</UUID>
<Text>
<TypeCode>10011</TypeCode>
<SystemAdministrativeData>
<CreationDateTime>2018-02-05T09:31:17.686127Z</CreationDateTime>
<CreationIdentityUUID>00163e07-3d66-1ee7-ace1-b4fb8fef5e9f</CreationIdentityUUID>
<LastChangeDateTime>2018-02-05T09:31:17.686127Z</LastChangeDateTime>
<LastChangeIdentityUUID>00163e07-3d66-1ee7-ace1-b4fb8fef5e9f</LastChangeIdentityUUID>
</SystemAdministrativeData>
<TextContent>
<Text>rqwrqwrer</Text>
</TextContent>
</Text>
<Text>
<TypeCode>10011</TypeCode>
<SystemAdministrativeData>
<CreationDateTime>2018-02-06T09:37:28.956748Z</CreationDateTime>
<CreationIdentityUUID>00163e07-3d66-1ee7-ace1-b4fb8fef5e9f</CreationIdentityUUID>
<LastChangeDateTime>2018-02-06T09:37:28.956748Z</LastChangeDateTime>
<LastChangeIdentityUUID>00163e07-3d66-1ee7-ace1-b4fb8fef5e9f</LastChangeIdentityUUID>
</SystemAdministrativeData>
<TextContent>
<Text>uioioo</Text>
</TextContent>
</Text>
</TextCollection>
</IdentifiedStock>
<IdentifiedStock>
<IdentifiedStockID>BAT010108-MX09</IdentifiedStockID>
<ProductID>MCA-0009-MX09</ProductID>
<ProductionDateTime>2007-01-01T10:32:37Z</ProductionDateTime>
<ExpirationDateTime>2110-01-01T10:32:37Z</ExpirationDateTime>
<LifeCycleStatusCode>
<LifeCycleStatusCode>2</LifeCycleStatusCode>
</LifeCycleStatusCode>
</IdentifiedStock>
</n0:IdentifiedStockQueryResponseMessage>
Query Identified Stock with specific supplier ID and fuzzy search
<n0:IdentifiedStockQueryMessage_sync xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <IdentifiedStockSelectionByElements> <SelectionBySupplierIDPartyID> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>1</IntervalBoundaryTypeCode> <LowerBoundaryIdentifier>MC2000</LowerBoundaryIdentifier> </SelectionBySupplierIDPartyID> <SelectionBySearchText>ISTOCK</SelectionBySearchText> </IdentifiedStockSelectionByElements> <ProcessingConditions> <QueryHitsMaximumNumberValue>150</QueryHitsMaximumNumberValue> <QueryHitsUnlimitedIndicator>false</QueryHitsUnlimitedIndicator> <LastReturnedObjectID/> </ProcessingConditions> </n0:IdentifiedStockQueryMessage_sync>
Response
<n0:IdentifiedStockQueryResponseMessage xmlns:n0="http://sap.com/xi/SAPGlobal20/Global" xmlns:prx="urn:sap.com:proxy:ACL:/1SAI/TASA3C59DD8D844E17877AE:804">
<ProcessingConditions>
<ReturnedQueryHitsNumberValue>9</ReturnedQueryHitsNumberValue>
<MoreHitsAvailableIndicator>false</MoreHitsAvailableIndicator>
<LastReturnedObjectID>00163E073D6A1ED8839057C93B5B9597</LastReturnedObjectID>
</ProcessingConditions>
<Log/>
<IdentifiedStock>
<IdentifiedStockID>ISTOCK_A2X06</IdentifiedStockID>
<ExternalIdentifiedStockID>EX_ISTOCK_06</ExternalIdentifiedStockID>
<ProductID>MCF-0001</ProductID>
<ProductionDateTime>2018-02-28T12:00:00.1234567Z</ProductionDateTime>
<ExpirationDateTime>2018-12-28T12:00:00.1234567Z</ExpirationDateTime>
<SupplierID>
<PartyTypeCode>147</PartyTypeCode>
<PartyID>MC2000</PartyID>
</SupplierID>
<LifeCycleStatusCode>
<LifeCycleStatusCode>1</LifeCycleStatusCode>
</LifeCycleStatusCode>
<Description languageCode="ZH">A2X Test IStock 06</Description>
</IdentifiedStock>
<IdentifiedStock>
<IdentifiedStockID>ISTOCK_A2X07</IdentifiedStockID>
<ExternalIdentifiedStockID>EX_ISTOCK_07</ExternalIdentifiedStockID>
<ProductID>MCF-0001</ProductID>
<ProductionDateTime>2018-02-25T12:00:00.1234567Z</ProductionDateTime>
<ExpirationDateTime>2018-12-28T12:00:00.1234567Z</ExpirationDateTime>
<SupplierID>
<PartyTypeCode>147</PartyTypeCode>
<PartyID>MC2000</PartyID>
</SupplierID>
<LifeCycleStatusCode>
<LifeCycleStatusCode>2</LifeCycleStatusCode>
</LifeCycleStatusCode>
<Description languageCode="EN">A2X Test IStock 07</Description>
</IdentifiedStock>
<IdentifiedStock>
<IdentifiedStockID>ISTOCK_A2X16</IdentifiedStockID>
<ExternalIdentifiedStockID>EX_ISTOCK_16</ExternalIdentifiedStockID>
<ProductID>MCF-0001</ProductID>
<ProductionDateTime>2018-02-28T12:00:00.1234567Z</ProductionDateTime>
<ExpirationDateTime>2018-12-28T12:00:00.1234567Z</ExpirationDateTime>
<SupplierID>
<PartyTypeCode>147</PartyTypeCode>
<PartyID>MC2000</PartyID>
</SupplierID>
<LifeCycleStatusCode>
<LifeCycleStatusCode>1</LifeCycleStatusCode>
</LifeCycleStatusCode>
<Description languageCode="ZH">A2X Test IStock 06</Description>
</IdentifiedStock>
<IdentifiedStock>
<IdentifiedStockID>ISTOCK_A2X17</IdentifiedStockID>
<ExternalIdentifiedStockID>EX_ISTOCK_17</ExternalIdentifiedStockID>
<ProductID>MCF-0001</ProductID>
<ProductionDateTime>2018-02-28T12:00:00.1234567Z</ProductionDateTime>
<ExpirationDateTime>2018-12-28T12:00:00.1234567Z</ExpirationDateTime>
<SupplierID>
<PartyTypeCode>147</PartyTypeCode>
<PartyID>MC2000</PartyID>
</SupplierID>
<LifeCycleStatusCode>
<LifeCycleStatusCode>1</LifeCycleStatusCode>
</LifeCycleStatusCode>
<Description languageCode="ZH">A2X Test IStock 06</Description>
</IdentifiedStock>
<IdentifiedStock>
<IdentifiedStockID>ISTOCK_A2X23</IdentifiedStockID>
<ExternalIdentifiedStockID>EX_ISTOCK</ExternalIdentifiedStockID>
<ProductID>MCF-0001</ProductID>
<ProductionDateTime>2018-02-28T12:00:00.1234567Z</ProductionDateTime>
<ExpirationDateTime>2018-12-28T12:00:00.1234567Z</ExpirationDateTime>
<SupplierID>
<PartyTypeCode>147</PartyTypeCode>
<PartyID>MC2000</PartyID>
</SupplierID>
<LifeCycleStatusCode>
<LifeCycleStatusCode>3</LifeCycleStatusCode>
</LifeCycleStatusCode>
<Description languageCode="EN">A2X Test IStock 11</Description>
<AttachmentFolder>
<UUID>00163e07-3d66-1ee8-87a4-c3416bad87ba</UUID>
<Document>
<UUID>00163e07-3d66-1ee8-87a4-c3416bae07ba</UUID>
<VersionID>0</VersionID>
<SystemAdministrativeData>
<CreationDateTime>2018-03-01T07:56:52.654275Z</CreationDateTime>
<CreationIdentityUUID>00163e07-3d68-1ed7-abc8-df3d53203d6a</CreationIdentityUUID>
<LastChangeDateTime>2018-03-01T07:56:52.654275Z</LastChangeDateTime>
<LastChangeIdentityUUID>00163e07-3d68-1ed7-abc8-df3d53203d6a</LastChangeIdentityUUID>
</SystemAdministrativeData>
<VisibleIndicator>true</VisibleIndicator>
<CategoryCode>3</CategoryCode>
<TypeCode>10006</TypeCode>
<PathName>/BOAttachments/00163E073D661EE887A4C3416BAD87BA/Test</PathName>
<Name>Test</Name>
<AlternativeName>Test</AlternativeName>
<Description>A2X Test 23</Description>
<ExternalLinkWebURI>http://sap.com/anyURI</ExternalLinkWebURI>
<FileContentURI>http://sap.com/anyURI</FileContentURI>
</Document>
<Document>
<UUID>00163e07-3d66-1ee8-87a4-d464dd2607f4</UUID>
<VersionID>0</VersionID>
<SystemAdministrativeData>
<CreationDateTime>2018-03-01T08:00:42.572417Z</CreationDateTime>
<CreationIdentityUUID>00163e07-3d68-1ed7-abc8-df3d53203d6a</CreationIdentityUUID>
<LastChangeDateTime>2018-03-01T08:00:42.572417Z</LastChangeDateTime>
<LastChangeIdentityUUID>00163e07-3d68-1ed7-abc8-df3d53203d6a</LastChangeIdentityUUID>
</SystemAdministrativeData>
<VisibleIndicator>true</VisibleIndicator>
<CategoryCode>3</CategoryCode>
<TypeCode>10006</TypeCode>
<PathName>/BOAttachments/00163E073D661EE887A4C3416BAD87BA/Test 1111</PathName>
<Name>Test 1111</Name>
<AlternativeName>Test 11111</AlternativeName>
<Description>A2X Test 1111</Description>
<ExternalLinkWebURI>http://sap.com/anyUR111I</ExternalLinkWebURI>
<FileContentURI>http://sap.com/anyUR111I</FileContentURI>
</Document>
</AttachmentFolder>
<TextCollection>
<UUID>00163e07-3d66-1ee8-87a4-c3416bade7ba</UUID>
<Text>
<TypeCode>10011</TypeCode>
<SystemAdministrativeData>
<CreationDateTime>2018-03-01T08:00:42.572417Z</CreationDateTime>
<CreationIdentityUUID>00163e07-3d68-1ed7-abc8-df3d53203d6a</CreationIdentityUUID>
<LastChangeDateTime>2018-03-01T08:00:42.572417Z</LastChangeDateTime>
<LastChangeIdentityUUID>00163e07-3d68-1ed7-abc8-df3d53203d6a</LastChangeIdentityUUID>
</SystemAdministrativeData>
<CreationDateTime>2018-03-28T12:00:00Z</CreationDateTime>
<TextContent>
<Text>A2X Test 111</Text>
</TextContent>
</Text>
<Text>
<TypeCode>10011</TypeCode>
<SystemAdministrativeData>
<CreationDateTime>2018-03-01T07:56:52.654275Z</CreationDateTime>
<CreationIdentityUUID>00163e07-3d68-1ed7-abc8-df3d53203d6a</CreationIdentityUUID>
<LastChangeDateTime>2018-03-01T07:56:52.654275Z</LastChangeDateTime>
<LastChangeIdentityUUID>00163e07-3d68-1ed7-abc8-df3d53203d6a</LastChangeIdentityUUID>
</SystemAdministrativeData>
<CreationDateTime>2018-03-28T12:00:00Z</CreationDateTime>
<TextContent>
<Text>A2X Test 23</Text>
</TextContent>
</Text>
</TextCollection>
</IdentifiedStock>
</n0:IdentifiedStockQueryResponseMessage>