Fix pack 4

Solution: The history table query is optimized to use UNION and is modified similar to the query fired on the YFS_WORK_ORDER table.

Solution: The StartDate and RollingCount attributes are introduced in the getTransactionSummary API input. If RollingCount is Y and StartDate is passed, then the API computes orders created from the month and year of the StartDate for one year.

1. Has an asynchronous service with the JMS receiver component and Sterling Integrator (SI) component.
2. Has multiple consumer threads configured in the JMS Receiver.
3. Starts the integration server such that the above service starts reading messages from external JMS queue and sends them to Sterling Integrator component parallel by multiple threads.

Solution: The product is enhanced such that the access to cookies is synchronized in the HTTP Component and SI Component.

1. Enables the Native application in SFDC custom settings. Sterling enterprise code is different from omni configurator org code or tenant id. For example, external partner id in Visual Modeler.
2. Creates or Modifies a quote in SFDC, the configurator pop-up does not open up.

Solution: Along with .xml extension files, the .wip extension files are picked for processing, the issue is fixed by ignoring the .wip extension file.

1. Sets up a Change Project.
2. Sets up a synch profile for category.
3. Creates a new item and associates it with a category. A record is inserted in the yfs_entity_change table for this item with sync_exported = N.
4. Runs the export agent in delta mode. The record does not get exported.

Solution: For YFS_Category_Item, the locking entity is YFS_Category, hence changes on YFS_Category_Item can be exported only if the YFS_Category is modified. This issue is fixed by updating Category.modifyts, when the CategoryItem is modified. So when ever CategoryItem is modified, its Category is also modified and both these details gets exported during delta export.

1. Configures Sterling Order Management 9.5.
2. Configures Sterling Store Application – for backroom pick & registering customer pickup using recordCustomerPick API.
3. Configures Sterling Store Inventory Management Application (9.3) – For having node with location
4. Configures ShipNode as WMS node ( node with location).
5. Creates Sales Order for the Store. This order must be customer pick up order
6. Schedules the order and Releases the order
7. Creates Shipment for the order.
8. Picks the order using backroom pick screen in Sterling store application.
9. Moves the Order( shipment) to Ready for customer pickup status.
10. Invokes API recordCustomerPick without passing any output template from the API tester.

Solution: The recordCustomerPick API is fixed to set the default output template properly.

1. Creates an Order for a Node with Sterling Store Inventory Management.
2. Schedules an order and releases the order.
3. Creates a shipment for the order.
4. Completes the Backroom Picking for the shipment.
5. Completes the Packing of the shipment in a container.
6. Calls removeFromContainer API and changeShipmentContainer API in a multiApi call to remove one quantity from the container and to reduce the weight of the container.

1. Sets property yfs.yfs.completetask.considersystemqty.countrequesttypelist= to a valid count request type.
2. Adjusts inventory for item I1 at location B1 for quantity=100. (System Qty)
3. Creates count request with request type based on the set value at the property level. A record of the current inventory picture is inserted in the yfs_phy_cnt_request table (new table) against the count request key.
4. Adjusts inventory for item I1 at location B1 for 20 quantities. (Sales Qty)
5. Completes the count task with count as 90 quantities. A record is inserted in the yfs_count_result table with a variance of -10 quantities.
6. Releases a recount task, the existing record in the yfs_phy_cnt_request table is updated with the current inventory picture.
7. Completes recount task with count as 90 quantities. A new record is inserted in the yfs_count_result table with a variance of -30 quantites.

Solution: As part of the solution for Stage rollout, the requirement here is multiple version of Sterling Order Management instances will process data from the same transaction schema. This requirement would be addressed by the following enhancements:· Transactional data should be tagged by their RollOut Version.· Agent servers should be aware of the RollOut Version of the transaction data and process only transaction data that matches the Agent’s Rollout Version. The agent multi Version support feature addresses this requirement.

1. Creates an Order.
2. Schedules the Order, releases the Order and ships the Order.
3. Calls getShipmentListForOrder API with SelectMethod="NO_WAIT". The select method used comes as WAIT even if NO_WAIT is passed in input.

Solution : The getShipmentListForOrder API is fixed to honor the SelectMethod.

1. Ensures that there are more than 21 queues created in the system.
2. Opens the Agent Criteria Detail pop-up screen and clicks the lookup icon for the Alert Queue name.
3. Creates a new queue by selecting create new icon in the search result panel of the Queue Search pop-up.
4. Searches for the newly created screen in the search screen.

Solution : This issue is fixed.

Solution: The Data Sync Export agent exports data for the YFS_ATTRIBUTE_GROUP, selected by ATTRIBUTE_GROUP_PATH.

Inventory purge agent is enhanced to check if there are inventory items whose modify timestamp satisfies the lead days of Inventory purge criteria. If the lead days of Inventory purge criteria is satisfied, the purge agent will lock the inventory item record and checks further if the inventory item is eligible for purge. The inventory item will not be eligible for purge, if there are records for it in any of these tables- YFS_INVENTORY_SUPPLY, YFS_INVENTORY_SUPPLY_ADDNL, YFS_INVENTORY_SUPPLY_TEMP, YFS_INVENTORY_DEMAND, YFS_INVENTORY_DEMAND_ADDNL, YFS_INVENTORY_TAG, YFS_INVENTORY_NODE_CONTROL, YFS_IBA_TRIGGER, YFS_ITEM_NODE_VELOCITY_DUMP, YFS_ITEM_NODE_VELOCITY, YFS_GLOBAL_SERIAL_NUM, YFS_INVENTORY_RESERVATION, YFS_INV_OWN_TRANSFER_RCD, pending status records in YFS_INVENTORY_PENDING_ADJ and YFS_INVENTORY_MATCH, not yet posted records in YFS_INVENTORY_SHIPMENT and YFS_INVENTORY_RECEIPT. If the inventory item isn't eligible for purge, the purge agent updates its modify timestamp to the current timestamp. If records don't exist in any of the above tables for an inventory item, the inventory item is eligible for purge and the purge agent purges its records from the following tables: YFS_INVENTORY_ACTIVITY , YFS_INVENTORY_ALERTS, YFS_INVENTORY_ALERT_DETAIL, INV_ALERT_DTL_RELATIONSHIP, INV_INVENTORY_ITEM_LOCK, YFS_INVENTORY_PENDING_ADJ, YFS_INVENTORY_ITEM_NODE_COST, YFS_INVENTORY_MATCH, YFS_INVENTORY_SHIPMENT, YFS_INVENTORY_RECEIPT and YFS_INVENTORY_ITEM.

Solution: When smcfs EAR or WAR is built, set the -Ddevmode=Y and after the deployment, access the new API tester at <host>:<port>/smcfs/yfshttpapi/ibmapitester.jsp.

New API tester supports only "BASIC" authentication Style. Add property, "xapirest.servlet.authstyle=BASIC" in the customer_overrides.properties file for setting BASIC style authentication.

1. Creates a Store which is on boarded as a follower store.
2. Onboard a store.
3. Selects the store which is modeled as a follower store.
4. Clicks next to view the store and store the address.
5. Selects the model store.
6. Clicks Next and then clicks Finish.

1. Creates the Sales Order with 1 item and completes it.
2. Creates the Return Order that returns the item.
3. Calls processReturnOrder API on the return order.
4. Creates an Exchange Order by passing the ReturnOrderHeaderKeyForExchange=<OHK from Step 2>.
5. Calls processReturnOrder API on the return order from Step 2.

Solution: This issue is fixed and we get the Return Order from the correct thread which returns the Return Order object.

1. Creates sales order with one order line and quantity one at the MOTHERSHIP server.
2. Initiates return for the sales order from the EDS server.
3. Adds order line which is present in sales order in the return order.
4. Tries to add same order line again in return order.

Solution: Return line (EDS) association to the Sale line (MOTHERSHIP) logic is fixed to identify other associated return lines for the same sales line.

1. Configures Sterling Order Management with Multi schema setup. Data Sync Export agent is setup with in the Delta synchronous mode.
2. Creates Data sync profile for table groups that have tables in the MASTER schema and Data Sync Query is associated to that sync profile.
3. Runs the agent.

1. Creates an Enterprise with 2 Sellers, for example, Seller1 and Seller2.
2. Creates a price-list and pricing-rule for this Enterprise.
3. Assigns Seller1 in the Assign To Sellers tab.
4. Performs the Test Pricing from the Sterling Business Center by specifying the Seller2.

The issue is, earlier the property being used in the code had a spelling issue and was yfs.massageapiintput.registerextnpoint which was not defined in OOB yfs.properties_ysc* properties file. So the code reads the default value of it as Y and Data Access override was always enabled.

Solution: For backward compatibility Data Access override must always be enabled OOB, so OOB value for yfs.massageapiinput.registerextnpoint in the properties files(yfs.properties_ysc_ext and yfs.properties_ysc ) must be changed to Y.

Its also consistent with the OOB value for the property, yfs.massageapioutput.registerextnpoint which is already set to Y.

1. Omni configurator is enabled in Sterling by adding the required properties in the customer overrides file.
2. Sterling catalog organization code is different from the omni configurator org code or tenant id (For example, external partner id in Visual Modeler).

1. Navigates to "Customer Contact Type" configuration screen in Sterling Business Center.
2. Clicks save button without making any changes in the User Interface.

Solution: The CapacityConsumed, Capacity and CapacityUnitOfMeasure attributes are exposed in the getExternalCostForOptionsUE input for assignments, so that the utilization percentage could be derived from these attribute values. There is no change in the precision of the OOB CapacityUtilization in the UE input.

1. Configures the authorization reversal strategy "Reverse Excess", Partial reversal disabled.
2. Enables charge consolidation. Disables same authorization."Do Not Consolidate Settlement Or Refund Requests Across Invoices" is enabled.
3. CreateOrder with authorization greater than the order total.
4. Runs requestCollection API.
5. Schedules and releases the order.
6. Ships the order partially and creates shipment invoice.
7. Runs requestCollection API.