Description Affect the IOM REST API - Inventory Service 2.0 (https://knowledge.intershop.com/kb/2940Y3) When inventory data are requested for a list of products, the service return a 400 status without any inventory information when a single SKU from the list is invalid. Inventory of existing products

Description The functions bound to the db jobs defined in the table admin.db_jobs have a locking mechanism to prevent that a same job can run in parallel, when the previous scheduled job is not yet terminated. These locks are not taken due to a wrong reference used in the functions. It is unlikely that

Description With update IOM from 4.7.11 to 5.1.5 configured EventRegistryEntryDO is not executed for PaymentNotificationTransmissionedQueue. Steps to Repeat Preconditions (already attached all the files for a working system) a payment workflow a payment notification transmitter to be set up, e.g. for

Description Creating a manual credit on order charges will modify the original order data (OrderChargeDO). This means that it is not transparent at all what the originally charged costs were. Steps to Repeat Create an order with order charge(s). Process the order so that an invoice will be created. The

Description Creating a manual credit note for a charge fails in certain scenarios (see steps to repeat). Steps to Repeat Prerequisites: Invoice creation is configured. Invoices are created per dispatch. Shipping costs should be invoiced as soon as at least one item is shipped. Create an order with multiple

Description OMT displays shipping charges in manual credit note creation form that are not related to the underlying invoice. Steps to Repeat Prerequisite: Invoice creation enabled on dispatch Steps to repeat: Create order with two or more shipping buckets. Each of the buckets need to have charges assigned

Description Adding an expanded value to SalesPriceCalculatorBeanDefDO will result in an exception and stop the further checks of the expanded enum values during the deployment, without stopping it though. background: the enum check does not cope with name differences between the java attributes and the

Description The rebuild of the stored procedures that takes place during the migration contains some drop/create trigger statements. (background: there is no create trigger IF NOT EXISTS... statement in postgres.) It appears that these statements require an exclusive table lock which may cause dead locks

Description Steps to reproduce the bug: Prepare database: BEGIN; -- Event registry configuration --> Trigger Mail Event Manager INSERT INTO "EventRegistryEntryDO" ( "id","creationDate","modificationDate", "processesRef","version", "eventDefRef","shopRef","description") SELECT nextval('"EventRegistryEntryDO_id_seq"')

Description The OMT has no direct support for product shop name aliases. It display such aliases instead as a comma separated list. Trying to edit such a product leads to an exception (stack trace attached, in "log"): java.lang.NullPointerException: Cannot invoke \"bakery.persistence.viewobject.article