The Order IOM Extension REST API works only with the IOM Connector enabled. This API specification is available for download as an Open API 3.0 YAML file: icm-order-iom-extension-1x0x1.yaml References The following page lists available REST APIs for ICM 11 and their version dependencies: Reference -

Table of Contents Introduction ER Diagrams Order Product Introduction This document shows how the database schema of the BI Data Hub is defined. The target audience are data analysts who plan to use the data for own reporting. ER Diagrams Order order_document document_no order ID, as it comes from ICM

1 Introduction 2 Feature List 2.1 Order Data 2.1.1 Base Order Data 2.1.2 Shipping Bucket Data 2.1.3 Product Line Item 2.1.4 Payment 2.1.5 Order States 2.2 Product Data 2.2.1 Base Product Data 2.2.2 Category Path Data 2.2.3 Assigned Categories 3 Accessing the Data 1 Introduction This document describes

Introduction Recipe: Configure the Order Export for the BI Data Hub Recipe: Add BI Dashboard to ICM Recipe: Create Report Based on Intershop Template Recipe: Adjust Reports Recipe: Download Default Report Templates from Intershop Introduction The BI Data Hub allows you to gain insight into different

Introduction Preconditions Instructions Creating an Order Submission Service Configuring the Service Setting Up the Order Export Optional: Export "Old" Orders Introduction To collect order data from an ICM for the BI Data Hub, an order submission service must to be created in the ICM. Once the service

What Is the BI Data Hub? What Do You Get? How Are Your Systems Connected? How to Get Started With BI Data Hub? Decisions System Information Onboarding Process What Is the BI Data Hub? The BI Data Hub is your central starting point for targeted reporting and analytics of your e-commerce system. The Data

1. Table of Contents 1. Table of Contents 2. Introduction 2.1. BI Data Hub 2.2. Multi-tenancy 3. Overview 2. Introduction The present page serves as an overview for the topic. All available documents for the topic can be found here. 2.1. BI Data Hub The BI Data Hub is a customer's central starting point

Description In case of a successfully exported order, status matches IOM (mostly). If the exact same order is then exported again from ICM (user error, other reasons) the result is that the order is flagged as export failed and the correct status can no longer be seen in ICM. Steps to Repeat Copied from

Description Customer noticed, that there are some issues in the Payload they are receiving from IOM for RMA: Payload looks like this, and it is missing the county field: Also there is a NULL in the Addition address field: <ns2:Addition>Principala nr 145 null</ns2:Addition> <?xml version="1.0" encodi

Description The order history (my account) gets very slow when there are more and more orders. In our case 17 orders led to a 6s load time. ICM 7.10.30.2 / IOMConnector 6.5.1/2 We use the RSS Repro Steps Have an account with roughly 20 orders and navigate to the order history. Observe long loading times

Description Description: lower case in Order List should be adjusted. inSPIRED > Orders > Order List Steps to Repeat In the backoffice: Open inSPIRED > Orders > Order List Actual Behavior Description: lower case in Order List should be adjusted. Expected Behavior All items need to be in Sentence Case

Description The OrderPositionState information from the IOM is assigned to the corresponding ICM OrderProductLineItem via the article identifier ( IOM#articleID <–> ICM#productSKU ). This mapping is no longer unique, as the IOM Order REST API now also supports multiple shipping-buckets and a product

Description ICM 7.10.30.2 IOM 3.4.3.0 IOMCONN 6.5 During our testing of the IOMConnector migration, we've observed that the are sometimes unexpected product names visible in IOM after export. The reason is the product mapper, that does not use the orders locale: product.setName(productBO.getDisplayName()

Description Description: The system tried to export an order, terminating with the following exception: "Value too long for Field "Name" in com.theberlinbakery.types.v1_0.Article" Is the ICM and also the IOM supports at this place the same attribute length (1000 chars) this mapping-error should not be

Description Actual behavior ICM defines an enumeration TaxClass in ac_iomconnector_common that is hardcoded to three tax classes: NoTax, ReducedTax, FullTax if you are not using the exact same tax types in your product data, you have to implement and override TaxClassResolver via the Component Framework

Description Bug description During the yesterdays demo an order export to IOM failed. The product in the order included surcharge product. For product without surcharge was the order export to IOM successful. Where (Environment & Channel) ICM: https://iom29demo.intershop.de:8443/INTERSHOP/web/WFS/SLDSystem/

Description IOM-Connector 6.0.8 I am seeing errors in the IOM logs regarding the order export: The given SOAPAction http://v1_0.services.theberlinbakery.com/OrderServicePort/storeOrderRequest does not match an operation. Sending orders from SOAP UI to the system is working fine. I could reproduce the

Description Current Behaviour: An order that is already existing in IOM raises a DuplicateException and denies the order. The ICM-IOM-Connector treats this as an exception and not as a note. Expected Behaviour: Because the exception notes, that the order already exists, the connector should return a

Description This ticket is linked to link IOM-9003. Actual Behavior The IOM connector can not handle documents created by IOM other than invoices, credit notes and delivery notes. Expected Behavior Anything that is visible in the documents section of an order in OMT should be visible in the MyAccount

Description Current Behaviour: The zipped delivered demo assembly needs adjustments in dependencies. So it's not easy to use as promised in Preview Assembly of https://confluence.intershop.de/display/ENFDEVDOC/Public+Release+Note+-+IOM+Connector+6.0#PublicReleaseNote-IOMConnector6.0-Setup. Expected Behaviour: