Fix pack 22

In Internet Explorer 8, the Sterling Business Center home page is not displayed after login.

Documentation is updated for recommending users to use the latest version of Internet Explorer browser. For more information, see Log in to IBM Sterling Business Center topic.

Solution: A new attribute 'Action' is introduced under the OrderLineInvAttRequest element for the changeOrder API. For more information, refer Javadocs.

Problem: The validation and override rules caches are not being refreshed after a change project is imported. This might cause incorrect evaluation of these rules if they are changed by a change project import.

Solution: If a change project contains data that is being used by validation or override rules, the caches for these rules are flushed.

For more information about this enhancement, see Overview of order attribute based pricing.

• DonotConsiderPendingCharge rule is set to Y.
• AllowRefundToExceedChargeAmount rule is set to N.

Solution: The issue is resolved. When repetitive requestCollection API calls are made, additional entries will not be logged for the canceled amount.

1. Configures a payment method, say Credit Card, with Authorization reversal strategy set to do not reverse.
2. Enables the Do Not Consolidate Settlement Or Refund Requests Across Invoices financial rule.
3. Creates on order of $100 and authorizes it on credit card for $100.
4. Adds a line for $30 and authorizes the $30 on credit card.
5. Cancels order line of $50.
6. Amount to charge is displayed as $130 instead of $80.
7. Ships the order and creates the invoice.
8. Opens the order in the Call Center for Commerce application and navigates to Payment Confirmation screen.
9. Amount to charge is displayed as $30 instead of $0.

The application is enhanced to execute and apply discounts sequentially and non cumulatively when the rule, Process pricing rules sequentially by exclusivity ID, is enabled and the rule, Apply Rules Cumulatively, is disabled.

Problem: The Applications Manager, System Management Console, and Channel Applications Manager need to be supported on Java™ Web Start technology with WebSphere® Application Server.

-Dyfs.jnlp.forceCookieVersionZero=true

Solution: This issue has been fixed. Also, the documentation has been updated.

For more information about the enhanced, see Fetch inventory availability from Inventory Visibility.

Solution: The documentation has been updated to list all the unsupported special characters.

For more information about the unsupported special characters, see Create a category in IBM® Sterling Business Center.

Solution: Check for the lockid column during the generation of the update statement.

For the updated description, see the YPMGetOrderPriceUE Javadocs.

Solution: The default value of the yfs property, scwc.value.mapping.file has been corrected.

• Application Platform > Participant Modelling > participant setup
• Application Platform > Security > users
• DOM>Distributed Order management >Customer

1. Enables the dynamic distribution logic in the financial rules.
2. Creates an order and moves it to the Shipped status.
3. Creates a return order with ProcessPaymentOnReturnOrder=N.
4. Purges the Sales Order and the Return Order.
5. Restores the Sales Order.
6. Calls the getOrderList API for the Sales Order with the output template that has @ChargeTransactionDetail element.

Solution: Since createUserHiearchy API does not make any changes in Organization, it should not validate YFS_ORGANIZATION.SYNC_TARGET_ID with YFS_SYNC_TARGET.SYNC_TARGET_ID.

Solution: A new property, yfs.synchLoadedInventory.MultiRec, has been added. When this property is enabled, the syncLoadedInventory API calculates the inventory picture against multiple supply records.

Solution: Avoided Zone level LPN query when LPN tracking is disabled in all zones.

Solution: The Listener logic is enhanced to be more deterministic by identifying ListenerPreferredPickupStatus based on other mapping entries in the Listener.

When the purchase order quantity is moved from PO.statusA to PO.status B, the Listener drops the sale order quantity to SO.statusB. It can pick either SO.statusA or SO.statusB (higher status is picked) and drop it to SO.statusB. With this enhancement, the Listener determines that the purchase order status is moved from PO.statusA, and there is a mapping SO.statusA->PO.status A. Therefore, it prefers SO.statusA over other statuses.

Condition: If the input XML contains a different containerDetail element for each Transshipment and for same shipment line.

1. Configures Financial Rule - For Pricing Confirmed Orders - "System Date".
2. Creates the pricing rule to apply a discount with the effective start date as current date plus 1.
3. Creates a draft order. The discount is not applied as the pricing rule is effective tomorrow.
4. On the second day, confirms the order. The system applies the discount. The order total is updated with the discount, but the delta is not reflected in yfs_charge_transaction.

Solution: The recordCountResult and getNodeInventory have been enhanced to filter in getNodeInventory instead of filtering in the final output.

1. Sets a sharded environment with two different colonies (DEFAULT and COLONY1) for organizations such as DEFAULT and Enterprise1.
2. Sets the value of the lockItemOnInventoryChanges property to N.
3. Creates an item for Enterprise1.
4. Calls the adjustInventory API to adjust inventory for the organization "Enterprise1" by using a user of the DEFAULT Organization.

1. Creates a pricing rule for any item say I1.
2. From the Sterling Business Center, open the pricing rule and set "This pricing rule is not assigned to any customer".
3. Calls the getOrderPrice API with Pricing Date less than the current time - 1 day or greater than the current time +1 day.
4. Makes sure that pricing rule is not applied.
5. Calls the managePricingRuleAssignment API to assign pricing rule to any customer attribute, say Vertical.
6. Calls the getOrderPrice API again with attribute Vertical in Selection Criteria with the same pricing date.

1. Enables "Use same authorization multiple times".
2. Enables "Do Not Consolidate Settlement Or Refund Requests Across Invoices".
3. Creates an order with 2 lines ($70 and $30).
4. Adds a payment method with the maximum charge limit ($200) more than the order total.
5. Records 2 authorizations ($99.99 and $0.01) which sum up to the order total.
6. Ships and generates invoice for line 1.
7. Runs payment agents, CHARGE for the first invoice collected.
8. Ships and generates invoice for line 2.
9. Runs the requestCollectionAPI.

1. Creates an order for $100.
2. Adds a payment method to the order.
3. Creates an invoice for $100.
4. Calls the requestCollection API.
5. Closes the CHARGE of $100 as Async.
6. Suspends the payment method for both charge and refund.
7. Calls the recordExternalCharges to record the $100 CHARGE, which was closed as Async in step 5.

YFS_PAYMENT.REQUESTED_CHARGE_AMOUNT is updated as -100

Solution: The system checks if the unexpected lines are allowed and sets the substitute or override item id accordingly.

• GDPR_Execute_Request
• GDPR_Get_Data
• GDPR_Get_Detail_Data
• GDPR_Manage_Request
• GDPR_Restrict_Data
• GDPR_Undo_Restrict_Data
• GDPR_Delete_Data

Order Line's ChargePerLine is again invoiced and the total invoiced ChargePerLine for the Non Billable charges is doubled.

This issue happens randomly. When the getCompleteItemList API is invoked with filter criteria that produces a mix of tag controlled and non-tag controlled items, the non-tag-controlled-item's logic could end up being used, which results in an inventory mismatch when compared to the API being invoked only for the tag-controlled items.

Problem: The support for applets is being removed by web browsers. Hence, applications like Applications Manager, System Management Console and Channel Application Manager need to be supported on Java Web Start technology.

Solution: The applications that are mentioned are supported on Java Web Start now. In the future, the support for applet applications may be completely removed. It is strongly recommended to use the new Java Web Start based Applications Manager, System Management Console and Channel Application Manager. For instructions, refer online documentation.

yfs.yfs.configurator.usewebstart=true

Solution: If the attribute is passed, it is automatically removed.

org.eclipse.jst.j2ee.commonarchivecore.internal.exception.DeploymentDescriptorLoadException: WEB-INF/web.xml

User creation fails when the organization name contains a single quote.

In the createOrder API, on passing SuppressNodeCapacity="Y", the nodes are getting ignored instead of the node capacity. Due to this, the order gets backordered.

Problem: The manageCategory API fails to create a child category with some of the attributes same as that of parent category.

Solution: The manageCategory API has been modified so that it does not inherit attribute from parent category, if the same attribute is passed in the input. However, it inherits the rest of the attributes from it's parent category.

For document updates, see Configuring integrations with IBM Inventory Visibility and Sterling Order Management.

When an order is scheduled against future inventory and is unscheduled, the order line status should point to the current date.

1. Create a node STORE_1. Configure sourcing such that this node is considered.
2. Create ITEM_1 and adjust inventory for this item on STORE_1.
3. Create Resource pool RP_1 at STORE_1 of type RELEASE.
4. Call the reserveAvailableInventory, createOrder, scheduleOrder, and releaseOrder APIs in a multi API call.

Problem: Three capacity consumption is observed.

Solution: Set the property of yfs.yfs.persitCapacityAdjustments=true such that the capacity is adjusted only when a transaction is committed.

In the changeRegion API, the ResetAll flag at ZipCodeRanges element level is not behaving as expected. If the number of records for a particular region key is more than 500, and if ResetAll="Y", only the first 500 records are deleted as opposed to delete all records from the YFS_REGION_DETAIL table.

Solution: The getOrderDetails API is fixed to return Reference1,2,3 instead of Reference_1,_2,_3

Solution: The getOrderDetails API is fixed to return Reference1,Reference2,Reference3 instead of Reference_1,Reference_2,Reference_3.

Problem: When safety factors are defined at store level, the YFS_Item fires a SELECT statement on YFS_SKU_SAFETY_FACTOR_DEFN per item related entry in YFS_ITEM_NODE_DEFN, which causes performance issues with large number of stores.

1. Removes the modification type "Change Other Attributes" at "Line" level from Modification Impacting Pricing in Applications Manager.
2. Creates a custom modification type at the line level for "TranDiscrepancyQty" attribute.
3. Configures custom modification type to Modification Impacting Pricing.
4. Creates sales order with 2 quantities of item I1.
5. Schedules and releases the order and creates a shipment.
6. Confirms the shipment with 3 quantities.

1. Extends the YFS_SHIPMENT table and add a custom column.
2. Creates multiple shipments and makes sure that the value of extended column is populated for all the records.
3. Calls the getShipmentList API with paginate element and extended column in the OrderBy element.
4. Calls the getShipmentList API again with the PreviousPage record and extended column in the OrderBy element.

1. Create two Organizations ORG1 and ORG2 which define their own catalog but have a common inventory organization.
2. Create an Item ITEM_A under ORG1
3. Adjust Onhand inventory for ITEM_A under ORG2
4. Call the reserveravailableInventory API for ITEM_A by passing EnterpriseCode="ORG1", OrganizationCode="ORG1" and ReservationID="RES_1"5.
5. Call the getInventoryReservationList API for ReservationID="RES_1"

Solution: This issues is addressed.

• Delayed authorization is enabled in payment rule.
• Configures X Hours Before Release Date For Product in payment rule.
• Bundle fulfillment strategy is set to "Delivery together".
• Creates a bundle item with two components.
• One of the component is available ONHAND and the other is available after X hours + 10 days.
• Creates an order for bundled item.

Solution: To push the authorization expiration date till the last component release date, enable the following property:
yfs.delayAuthorizationForBundleParentUntilLastComponent

The valid values are Y and N. By default, the value is set to N.

The Future Authorization is created with the Authorization expiration date that is pushed till the last bundle components release date.

To delay the authorization for bundle parent till the last components release date, in the customer_overrides.properties file, set the value of this property as yfs.yfs.delayAuthorizationForBundleParentUntilLastComponent=Y.

Sample scenario:

An order is created for 5 units of Bundle item B1 for which the unit price is 10. The components item BC1 and BC2 with the Kit ratio 1:1.

1. Create stores, NODE1 and NODE2.
2. Create sourcing and scheduling rules such that NODE1 is a ship node that procures from NODE2.
3. Create an item, ITEM_1 having inventory at NODE2.
4. On the current date, multiple transfer schedule exists from NODE2 to NODE1 as follows:
   1. Transfer schedule 1 is already expired.
   2. Transfer schedule 2 is currently active but ends in the next six days with no possible day to ship.
   3. Transfer schedule 3 is effective from seventh day to three years from now.
   4. Call the findInventory API for ITEM_1 with quantity 1.

Solution: YFSGetItemNodeCostForSourcingUE is not called.

1. Enable Use same Authorization multiple times.
2. Disable partial reversal supported.
3. Authorization reversal strategy "Reverse Excess".

Run requestCollection, authorization reversal for auth id A1 of $100 is created.

1. Creates an order with two order lines having two different Ship Nodes being stamped.
2. Schedule and release the order.
3. Creates Shipment for all releases.
4. Logs in to the Sterling Store application with different Node or Store users and performs the Record Pick action using the order number.

Condition: Create an inbound PO order, receive the same order through receiveOrder API or by using the Inbound UI screens.

Operation: In this scenario, the supply type moves from PO_PLACED to ONHAND and an activity is published in the yfs_inventory_activity table.

Solution: RTAM publishes the inventory picture of the inbound PO while supply type moves from PO_PLACED to ONHAND.

An unresponsive Pierbridge or Agile shipping label call blocks the subsequent packing process.

• Configuration: Create an item and a node.
• Condition: Create an inbound Purchase Order (PO), receive the same through receiveOrder API through inbound UI screens.
• Operation: In this scenario, the supply type moves from PO_PLACED to ONHAND and an activity should be published in the yfs_inventory_activity table.
• Solution: RTAM should publish the inventory picture of this inbound PO, while supply type moves from PO_PLACED to ONHAND

Problem: Sterling Order Management is unable to resolve the path of the ValueMaps file (based on the value defined for the property scwc.value.mapping.file) if the file exists in the properties.jar in the deployed EAR .

Solution: Sterling Order Management code is modified to always read the 'value map' file (based on the value defined for the property scwc.value.mapping.file) from the class path.

After the fix, with the property defined as scwc.value.mapping.file=/ValueMaps.xml, the Application Server and Agent or Integration Server would read the 'value map' file from their respective class paths.

The BypassPricing flag is used to determine whether repricing is required from the Pricing Engine or not. By design, the YFSOrderRepricingUE is separate from the Pricing Engine. If implemented, the YFSOrderRepricingUE runs even when BypassPricing=Y.

Fix: There is an internal flag, SuppressRepricingUE that can be set on the order header to suppress calls to YFSOrderRepricingUE.

• Configuration: Backorder against highest priority node is configured.
• Problem: If an order is backordered while releasing, it is always backordered against the highest priority node. However, in case the order has been scheduled from a lower priority node, releasing the order should backorder it against that node itself . Releasing the order should not change the node decided while schedule the order.

• Configuration:
  1. Edit sandbox.cfg file and set the value of DATABASE_PROPERTY_MANAGEMENT parameter to true.
  2. Run setupfiles.cmd/sh script from the <INSTALL_DIR>/bin directory.
  3. Run loadProperties.cmd/sh script from the <INSTALL_DIR>/bin directory.
     Properties are loaded into database in the PLT_PROPERTY and PLT_PROPERTY_METADATA tables. However, certain properties will remain file based and their entries are persisted for reference in the <INSTALL_DIR>/properties\filesystem.properties file. Following properties are file based:

     • JDBC based properties
     • log based properties
     • sandbox.cfg
     • servers.properties
     • vendor.properties
     • security.properties
     • logfilter.properties
     • logCodes.properties
     • logMessageCodes.properties
     • tuning.properties

  4. Build resource JAR.
  5. Create and deploy EAR.
  6. Restart app,agents, and integration servers.
• Condition: 950FP12 has to be installed as database property management is enabled only from this release onwards.
• Out of Scope: Unexposed properties and SMA UI work is out of scope. Unexposed properties can be managed through database using manageProperty API or using customer overrides files.
• Solution: For more information on merits of database property management and the issues faced in the file based management, refer to Property management in the database.
• Additional Details:
  • agentServer and startIntegrationServer scripts have been enhanced to take additional details other than having only SERVER NAME as argument. An example to handle server override logic in this feature, from <INSTALL_DIR>/bin directory run the following command:

    agentserver.sh RTAM_SERVER -jvminstance TestJVMInstance1

    The value of "-jvminstance" argument (TestJVMInstance1) should match the value in PROPERTY_OVERRIDE_NAME in the PLT_PROPERTY table for server override logic to work.

  • Use manageProperties.cmd to perform following actions (edit, import, list and detail modes) on database managed properties:

    manageProperties.cmd/.sh -mode edit -property "yfs.considerUnassignedDemands" -category "yfs" -override "BASE" -value "Y" -usercomment "change value of base property to Y"

    manageProperties.cmd/.sh -mode import -file "<INSTALL_DIR>\properties\customer_overrides.properties" -usercomment "importing co properties to db"

    manageProperties.cmd/.sh -mode list -category "yfs"

    manageProperties.cmd/.sh -mode details -property "yfs.context.namespace" -category "yfs"

• Configuration: Enable yfs.yfs.order.maintainProductServiceAssociationExternally=Y in the customer_overrides.properties file.
• Condition:
  1. When product service association are not defined in catalog management, customer should pass the product service associations in input of createOrder or changeOrder API as specified as follows:

     <Order>
     <OrderLines>
     <OrderLine/>
     </OrderLines>
     <ProductServiceAssocs>
         <ProductServiceAssoc ProductQuantity="2"  ServiceQuantity="2">
     <ProductLine PrimeLineNo="1" SubLineNo="1" />
     <ServiceLine PrimeLineNo="3" SubLineNo="1" />
         </ProductServiceAssoc>
     <ProductServiceAssocs>
     </Order>

     No change in behavior should be observed, if associations are not passed in input of createOrder or changeOrder APIs. Additionally, the ProductQty, ServiceQty attributes should not be zero or not less than zero, when passed at Order Product Service Association element.
  2. For the generateWorkOrder API to work for Delivery Service lines with this feature enabled, the Order Product Service Association mentioned in Step 1 should be in place, as catalog module will not have this association.
  3. When both catalog and order layers have association, order takes precedence over catalog associations.

  Operation: Ensure that the createOrder or changeOrder API has Order Product Service Association in place, before invoking the generateWorkOrder API.

  Solution: Work Order is created for Delivery Service lines by using the generateWorkOrder API only when the Order Product Service Association is in place, else the work order wont be created in system

  Limitations:

  1. Variable capacity calculation for external product service association is not in scope.
  2. Service skill association defined in the catalog layer is out of scope for external product service association.
  3. Service Pricing Quantity and Product Pricing Quantity is out of scope for external product service association.

Problem: An order is partially backordered intermittently, when multiple items placed on order are being procured and the constraint line ship complete and ship from single node is enabled.

Solution: Enable the yfs.yfs.expandAllLinesIfAny=Y property in customer overrides.

1. Create a node say, NODE1and adjust inventory capacity and adjust inventory for 'ITEM1' at this node.
2. Set the configuration to consider only nodes that have XX% capacity in next Y days in sourcing rule sequence.
3. Create reservation for ITEM1 at NODE1 using the reserveAvailableInventory API.
4. Create more reservations or orders such that the capacity cut off criteria set up in sourcing rule is met.
5. Create an order using this reservation for ITEM1.
6. Schedule the order. Order is backordered.

Solution: Fixed the product to consider the extended Cancel status for updating the LinePackListPriceInfo values to zero.

Solution: Enhanced the product code to update the container to fix the JavaScript errors.

Solution: Enhanced the product code to submit to the server based on the auto-post option selected by a user.

Condition: Call changeShipment and confirmShipment in a single transaction boundary.

Solution: Action attribute is cleared properly, so confirmShipment behaves consistently irrespective of the transaction boundary.

1. Goes to the details of any existing service in the Application Manager,that has an alert component.
2. Clicks the Alert component in the service diagram.

By default the above statements are not enabled. In order to enable these JMS trace statements the following property needs to be set in customer_overrides.properties file. If enabled, these statements are logged with INFO level logging.

yfs.jms.debug.enabled=true

Optional properties:

The following optional properties can also be set in customer_overrides.properties file to control the frequency with which the JMS trace statements are logged.

1. yfs.jms.debug.send.interval.perthread=<n>

   <n> is number greater than 0. Default value of <n> is 1000.

   Tracing statement printing total time, will be logged after every 'n' message sends done by a thread to a queue defined in an SDF service.

2. yfs.jms.debug.qsender.interval.perthread=<n>

   <n> is number greater than 0. Default value of <n> is 1000.

   Tracing statement printing total time, will be logged after every 'n' Queue Sender creations done by a thread.

3. yfs.jms.debug.commit.interval.perthread=<n>

   <n> is number greater than 0. Default value of <n> is 1000.

   Tracing statement printing total time, will be logged after every 'n' Queue Session Commits done by a thread.

4. yfs.jms.debug.pool.fetch.interval=<n>

   <n> is number greater than 0. Default value of <n> is 1000.

   Tracing statement printing total number of sessions in pool, will be logged after every 'n' fetch requests made to the pool, across all threads.

1. Ensures GIV has "iba allowed" is set.
2. Enables yfs.yfs.considerUnassignedDemands = Y in the customer overrides file.
3. Creates an order with order line reservation (created through reserveItemInventoryList API).

Solution: The invalid node error is fixed and order creation will succeed.

Problem: confirmShipment API deletes all the canceled bundle lines.

All the bundle lines are deleted.

Solution: Similar to the normal items, the canceled bundle lines are retained during confirmShipment.

A Sku is considered as a trigger item, if it has all the attributes within an attribute group.

1. Enables the ON_ORDER_RELEASE_STATUS_CHANGE event of the changeOrder transaction.
2. Creates an item and a node.
3. Adjusts the inventory ONHAND=10 for this item-node combination.
4. Creates an order for the quantity 15.
5. Schedules the order.

Upon scheduling, the order moves to the Partially Scheduled status. Quantity 10 moves to the scheduled status and quantity 5 moves to the back-ordered status.

Solution: The agent allowed the auto trigger to happen early by the margin of 60 seconds. This margin is reduced to 30 seconds when the auto trigger interval of the agent is 1 minute. For higher values of the trigger interval, this margin will remain as 60 seconds.

1. Creates five purchase orders. For example, from NODE2 to NODE1 for multiple items.
2. Schedules and releases the purchase orders.
3. Creates a single shipment for the above orders.
4. Receives only the first line of shipment.

Solution: If the shipment line key is specified in the order line element of the receiveOrder API, only the corresponding order will be locked for the update.

A new property yfs.bDoNotConsiderNonInvHeaderDiscountForAdjInv is introduced. Set the value of this property in the customer_overrides.properties file as yfs.yfs.bDoNotConsiderNonInvHeaderDiscountForAdjInv=Y.

If this property in customer_overrides.properties is set to Y, it will stop creating the adjustment invoice for any changes in the charge type Discount until the charge is either partially invoiced or completely invoiced.

1. The behavior change will be a property driven fix.
2. Once you enable this property, the system will not the create adjustment invoice for the Discount Header charges unless the Header charges are either completely or partially invoiced.
3. If the financial rule INVOICE_OPEN_HDR_CHG_TAX_ON_INV_COMPLETE - "Invoice Open Header Charges/Taxes On Invoice Complete" is enabled, it will override the property behavior if the order is completely invoiced. The header level charges on the order that is not invoiced, will be invoiced and the adjustment invoice will be created. The financial rule behavior will remain the same.

Problem: There is a performance issue when the releaseOrder agent fires a query on the YFS_CHARGE_TRANSACTION table with a TRANSFER_FROM_OH_KEY where clause.

A Sku is considered as a trigger item, if it has all the attributes within an attribute group.

Solution: The program creates the classification count request by considering the Max Min unit cost values of the count program condition. The count result records will be created only for the items satisfying the count request criteria.

1. Enables the following financial rules:
   1. "Do Not Consolidate Settlement Or Refund Requests Across Invoices"
   2. "Do Not Allow Debit and Credit Invoice to Settle Each Other"
2. Creates a credit memo that is greater than the actual order total in the PAID status.
3. Runs the payment agents.

1. Selects payment rule, "Use Enterprise of an Order(Instead of the Seller) to Determine Payment Processing Rules" in the System Payment Processing Rules from the application manager.
2. Defines payment method "Test" under the DEFAULT enterprise.
3. Creates a Store under DEFAULT enterprise. For example, TestNode.
4. Creates an Order from store with "TestNode" as a Seller Organization.
5. Opens the order on the Application Console.

1. Enables the free gift pricing rule.
2. Creates an Order.

Solution: When shipToAddress is passed to getFulfillmentOptionsForLines, it is passed to YFSgetExternalAvailabilityUE as input.

1. Enables free gift pricing rules and implements PricelistHeaderrSelectionUE user exit.
2. Creates and activates the Free Gift pricing rule.

Solution: This issue is fixed.

1. Configures a listener to change the status to extended schedule say SCH_EXT when transfer order is received.
2. Sets up node and inventory configuration to support transfer order from NODE2 to NODE1 with fixed transit days as 2 days.
3. Creates an order with delivery date in future and carrier service and SCAC.
4. Schedules the order, a transfer order is created.
5. Schedules, releases, and ships the transfer order before time.
6. Receives the order early. The sales order is moved to SCH_EXT status and ETS is incorrectly updated to current time on the sales order line.

Solution: 'EACH_COMBINATION' FreeGift rule has been fixed by enabling multiple qty to be given as a free gift for each combination of eligible items.

Solution: The application is enhanced to display Original Line Ordered Quantity for the chained lines in the input of the user exit OMPGetSourcedFromNodesExternallyUE. The user exit template must be extended to include OriginalLineQuantity under the <PromiseLine/> element.

Solution: Fixed the product to query on yfs_customer_contact only for customer users based on the YFS_USER.IS_CUSTOMER flag. The YFS_USER.IS_CUSTOMER flag indicates if a user is a customer in the system. As a part of the fix, the manageCustomer API will set YFS_USER.IS_CUSTOMER ='Y' for the inserted user records.

For backward compatibility, if the system has users who are customers, run the following query to update the Is_Customer flag for the existing user records:

UPDATE <SCHEMA>.YFS_USER
           SET IS_CUSTOMER = 'Y'
           WHERE TRIM(LOGINID) IN
          (SELECT USER_ID
           FROM <SCHEMA>.YFS_CUSTOMER_CONTACT a,
                <SCHEMA>.YFS_CUSTOMER b
           WHERE a.CUSTOMER_KEY=b.CUSTOMER_KEY);

Solution: PaymentCollection user exit output object is enhanced to accept asyncRequestIdentifier when a transaction is closed asynchronously. This identifier can be passed in the recordExternalCharges API input to record the response for the original transaction for which the response is getting recorded.

AsyncRequestIdentifier must be passed along with ReducePendingAsyncronousAmounts as Y in the recordExternalCharges API input to store AsyncRequestIdentifier against the newly recorded transaction, and to reduce the requested amount on the payment method. A response for an asynchronously closed transaction must only be recorded once in the system. Trying to call recordExternalCharges twice for the same AsyncRequestIdentifier will record the duplicate transaction in yfs_charge_transaction, but the corresponding requested amount on the payment method will not be reduced.

AsyncRequestIdentifier is an optional attribute, if NULL or not passed the recordExternalCharges will not store AsyncRequestIdentifier against the payment transaction.

1. In the Installation rule, checks "Release Order On Date-Time".
2. Creates an order for 1 quantity with ReqShipDate within 30 minutes from current time.
3. Schedules the order.
4. Runs the ReleaseOrder agent.

Order is not released and AVAILABLE_DATE in YFS_TASK_Q is pushed by 30 minutes.

Solution: After the fix, the AVAILABLE date will not be pushed by 30 minutes rather it will be calculated based on ReqShipDate.

1. Creates a sales order with the two quantities of an item A.
2. Schedules, releases, and ships the order.
3. Invoices and settles.
4. Creates a return from IBM Call Center for Commerce UI for both the quantities and confirms them.
5. Receives 1 quantity on the returned line by using the foundation console.
6. Goes to the Return Order Summary screen in IBM Call Center for Commerce and clicks the Cancel Return screen.
7. Selects the cancellation return reason code and double clicks the Enter Quantity field to cancel the entered quantity.
8. Enters the quantity as 1 and clicks the Save/Next button.
9. Clicks ok on the confirmation dialog box.

   The Error description not available error message is displayed on the UI.

1. Sets the monitor rules and distribution groups for monitoring as required by the RTAM.
2. Creates an item ITEM_1 with no lead time setup.
3. Adjusts an inventory for the above item in STORE1 quantity 5.
4. Creates a reservation for quantity 1 for future date.
5. Calls the monitorItemAvaialbility API for this item. An alert is generated with OnhandAvailableQuantity="5.00".

1. Enables BC payment processing by setting the yfs.payment.persistCtrMaps to Y.
2. Creates an order for $100.
3. Creates a CTR for $100.
4. Takes Authorization for $100.4. Authorization expires.
5. Deletes the CTR.
6. Creates a new CTR.

Solution:

This feature is disabled by default. To enable this feature, the following property must be added in the customer_overrides.properties file:

yfs.jms.sender.anonymous.reuse=true

This feature is effective only when the jms session pooling in the product is enabled.

The maximum number of times the same QueueSender object to be reused can be configured by setting the following property in the customer_overrides.properties file:

yfs.jms.sender.anonymous.reuse.limit=5000

The default value of this property is 5000.

1. Sourcing rule has "Use Only on hand Inventory".
2. Procurement sourcing rule has "Use shipping Delivery Souring Rule Inventory Window".
3. Scheduling constraint "Line ship from single node" is set.

1. Bundles Item with few product lines BUN_1 consisting of component items COMP_1 and COMP_2.
2. Delivers service. For example, DS_1.
3. Delivers service slots and resource pool exist with appropriate resource capacity.
4. Creates an Order with Bundle Item. For example, BUN_1.
5. Calls scheduleOrder with Release="Y", Order status moves to Partially Awaiting shipment consolidation.
6. Calls consolidate to shipment for the release created and then confirms the shipment.
7. Calls Deliver shipment. Order status will be partially delivered as bundle parent line is not yet delivered.
8. Calls changeOrderStatus API to move the status of bundle parent to delivered.
9. Adds a delivery service line. For example, DS_1.
10. Creates work order for DS_1.Takes an appointment.
11. Confirms the work order.

1. Ensures to have multiple SDF services that have the JMS sender component, to send a message to different queues, but all the services have the same queue connection configuration.
2. Ensures that the jms session pooling in the product is enabled.
3. Ensures to have an asynchronous integration service with the multiple threads, such that the above mentioned SDF services are called in the same transaction boundary randomly to send a message.
4. Runs the above mentioned integration service using an integration server.

Solution: This feature is disabled by default. To enable this feature for the jms session pool, the following property must be set in the customer_overrides.properties file:

yfs.yfs.jms.session.pool.reuse.across.services=true

1. Sourcing rule has "Use Only on hand Inventory".
2. Procurement sourcing rule has "Use shipping Delivery Souring Rule Inventory Window".
3. Scheduling constraint "Line ship from single node" is set.

1. If the asynchronous raise event is enabled post commit of the parent transaction using the property 'yfs.asyncevent.enabled=true', it is observed that if the database commit of parent transaction fails for some reason, the asynchronous event still gets raised.
2. If the asynchronous order audit publish to external systems is enabled using the property 'yfs.publish.mode=OrderAudit', it is observed that if the database commit of parent transaction fails for some reason, the order audit record is still published to the external system.

   Solution: If the commit of the database fails for the parent transaction, the 'asynchronous publishing of the order audits to external system' and 'asynchronous raise event' should not occur for the parent transaction.

Solution: The product is enhanced such that the statistics record for the User Exit will display the User Exit name in the CONTEXT_NAME column.

1. Navigates to Application Manager > Warehouse Management System.
2. Selects the nWMS nodes button from the pop-up window.
3. Selects the node to be configured and the enterprise.
4. Clicks OK.

Solution: Enhanced MigratorMain to read CallingOrganizationCode from the Task element and used the same for executing the task.

1. Enables Allow Immediate Refund from Hold Amount.
2. Keeps the refund configuration for the gift card as RFO.
3. Keeps the refund configuration for the credit card as RFO.
4. Creates an order with the two order lines. For example, $80, and $20.
5. Pre-charges the order with a gift card ($30 charges are created with hold against book), and one credit card with the authorize and charge.
6. Ships both the lines.
7. Creates the shipment invoice.
8. Runs the requestCollection API. $30 is distributed against the invoice and the remaining amount of $70 is collected from the credit card.
9. Returns the line 1 ($80).
10. Creates an invoice.
11. Adds the third line to the SO for $20.
12. Runs the requestCollection API. An RFO is created for $70.
13. Runs the requestCollection API. Another RFO is created for remaining $10.

Solution : The new customer override property, yfs.payment.overrideDeferredCreditRefundWithAllowImmRefFromHold, is exposed. This property is set to Y in the customer_overrides.properties file. Setting this property to Y along with the payment rule Allow Immediate refund from hold amount will calculate the sum of negative debit (negative invoice) that are not refunded (distributed). The system refunds the complete negative debit from the amount that is held against the book. (Charges with hold against book as Y).

1. Creates the two enterprises, E1 and S1.
2. Adds the role SELLER to S1.
3. Creates the scheduling rule SR1 for E1.
4. Creates an order for enterprise E1 and seller S1, stamping with AllocationRuleID="SR1".
5. Schedules the order and releases the order.
6. Creates and confirms the shipment.
7. Calls the validateReship API with OrderHeaderKey in the API input.

Solution:The validateReship API is fixed to identify the scheduling rule from E1.

Solution: There are some discrepancies when using the comparator operator with the decimal values. This is fixed by replacing the comparator operators with the associated double-util methods.

1. Enables the dynamic distribution logic in the financial rules.
2. Creates an order and moves it to the Shipped status.
3. Creates a return order.
4. Purges the sales order and the return order.
5. Calls the getCompleteOrderDetails API for the sales order with the output template that has ChargeTransactionDetail.

1. Set up a node and an item.
2. Set up sourcing rules, scheduling rules, and landed cost.
3. Implement OMPGetExternalCostForOptionsUE.

Problem: The fulfillment type attribute is not populated in the XML input of getExternalCostForOptionsUE for certain transactions when a user performs the following sequence of actions:

1. Creates an order with the fulfillment type passed at OrderLine.
2. Schedules the order.

   The UE input formed does not have the fulfillment type in the PromiseLine element.

A new agent criteria, AuthorizationExpirationDateWindowInDays is introduced for the PAYMENT_COLLECTION agent. Setting this criteria to a positive non-zero number would add an additional where clause for the Payment_Collection agent to pick orders having AUTHORIZATION EXPIRATION DATE between the current date and current date - AuthorizationExpirationDateWindowInDays.

Example: AuthorizationExpirationDateWindowInDays=10, if the current date is 9/12/2016. The agent would only process orders having AUTHORIZATION_EXPIRATION_DATE between the current date such as 9/12 and currentDate - 10 such as 9/2/2016.

1. Enables Read Availability across Items Sharing the same GITN feature in the Global Inventory Visibility.
2. Sets up more than one item with the same Global item ID. For example, Item001, Item002, Item003. This allows the Item Substitution feature.
3. Sets up On Hand Inventory for Item002.
4. Creates an Order for Item001.
5. Schedules the order and releases the order.
6. Creates shipment for the same order.
7. Confirms the shipment.
8. Creates a return order for the shipped item. Makes sure to pass UnitPrice. Example, <LinePriceInfo UnitPrice="100.00" IsPriceLocked="Y" />.
9. Creates a return order, and checks the return order total.

Solution: When LinePriceInfo is passed with IsPriceLocked="Y" attribute, the LinePriceInfo element of the order line with the substituted item is not ignored.

1. Enables Landed cost, handling cost, transportation cost.
2. Sets outbound Shipment handling cost for store to $1000000.
3. Creates Items ITEM_1 and ITEM_2.
4. Creates two stores. For example, NODE_1 and NODE2.
5. Configures the Sourcing Rules to have the Nodes created.
6. Calls the FindInventory API with two promise lines; ITEM_1, Quantity 1 and ITEM_2, Quantity 1.

1. Enable landed cost, handling cost, transportation cost.
2. Set outbound Shipment handling cost for store to 1000000.
3. Create an item ITEM_1.
4. Create two stores NODE_1 and NODE2.
5. Adjust the inventory NODE1: 1, and NODE2: 2.
6. Sourcing rules are configured to have the nodes created.

Problem: Handling cost when the choice selection in logs appears as 100000 for NODE1 and 200000 for NODE2 though comes correct in the solution when a user calls the FindInventory API with the promise lines for ITEM_1 Quantity 2.

Solution: The logging framework is fixed such that the unnecessary calls to the YFCLogManager.checkLogRegistry function is eliminated.

1. Creates a new locale from the Applications Manager.
2. Creates a new category using the manageCategory API with the valid input under the CategoryLocale element to localize the category details.

Solution : Two separate API calls or a multi-API call is used to insert the Category and CategoryLocale data. The Java docs are also updated with these details.

1. Creates an Order Total Manual Pricing rule with When to Apply as All Items.
2. Saves the order.
3. Views the pricing rule details using the API.

Solution: The manageServiceSlotGroup is introduced to create, modify, and delete Service Slot and Service Slot Group.

This API enhances Sterling Business Center screens such that a user can manage Service Slot Group from Sterling Business Center.

This configured Service Slot Group is set on a resource Pool for Purpose ‘INVENTORY’ from Sterling Business Center. Currently setting Service Slot Group is allowed only to be set for resource Pool with Purpose ‘SERVICE’ from the Application Manager.

Solution: Enhanced the product code to allow a user to deselect the default selection in the multi-select tabular display.

Solution: The out of the box relationship is added from the YFS_ORDER_HEADER to the YFS_ORDER_RELEASE_STATUS table. To index the OrderStatus, a user must extend the STATUS column and the relationship "Name=OrderHeader" of the YFS_ORDER_RELEASE_STATUS table.

Solution: The utility is enhanced, such that the xpath expression cache limit is controlled by the system property scxmlutil.xpathexpr.cache.limit.

This property is passed as a system argument at the time of JVM startup. It is used to set the maximum number of XPath expressions which can be present in the cache.

The default value of this system property is -1. If the value < 0, an unlimited cache is used.

If value = 0, no cache is used.

If value > 0, the cache size is limited to the value. If the cache limit is reached, the least recently used entry is removed from the cache to put a fresh entry.

For example, to set a limit of 100K Xpath expressions in the cache, pass the following system argument in the JVM startup: Dscxmlutil.xpathexpr.cache.limit=100000.

1. Creates a delivery order with multiple product lines and a work order with the appointments.
2. Schedules and releases the order.
3. Creates a shipment, for example, S1 and makes sure that all the lines must be in a single shipment.
4. Calls the changeShipment API to set the quantity to zero for one shipment line.
5. Removes corresponding order line from the existing work order.
6. Adds a new delivery request for the order line removed from the shipment.
7. Creates a new work order for a new delivery line.
8. Schedules and releases the order.
9. Creates a shipment S2 for a new release.
10. Calls the changeShipment API to modify the first shipment.

Problem: System reverses the complete $100 authorization A1.

1. Creates an order with two different items having 1 quantity each for a SIM Node.
2. Schedules and releases the order.
3. Creates a shipment for the order.
4. Completes the Backroom Picking of the shipment.
5. Completes the packing of the entire shipment of 2 quantity in the same container.
6. Calls the removeFromContainer and changeShipmentContainer APIs in a multi-API to remove one item from the container and reduce the weight of the container.

Currently, without this feature manual changes are done with each deployment as if the full-sync is performed. This is not scalable for a large number of stores.

With this enhancement, the CHANGE_DATA_EXPORT agent will only consider the sync profiles whose SYNC_TYPE column value matches the CHANGE_DATA_EXPORT agent sync mode which is passed in the agent criteria parameter. Sync profiles with the no sync type defined will be considered for both the full-sync and delta-sync as it is the existing behavior.

A new service MarkEntityChangesForFullSync is provided which can be used by a system user to mark the entity changes as sync exported. So, the entity changes made after the external full sync are not lost due to optimization.

For more information, see External custom full sync support.

1. Creates an ITEM and Node. For example, ITEM_1, NODE_1.
2. Enables RTAM in the activity based mode.
3. Sets up distribution group and rules for monitoring.
4. Adjusts Inventory for ITEM_1 at NODE_1 to infinite.
5. Adjusts Inventory for ITEM_1 at NODE_1 to a finite value.

We have also extended the pricelist or pricingRule seller assignments in the same manner as the customer assignments so all the assignments can use the extended attributes. In case of the seller assignment, the Seller Organization record is used to determine eligibility. To have a valid assignment with an extended attribute set, YFS_Organization will have to be extended with the same attribute as your assignment tables.

Existing functionality for determining the customer assignment eligibility was to use the selectionCriteria or customer record to determine eligibility. There is a related use case where a customer record does not have an attribute set and a user wants to pass this attribute in selectionCriteria when using the remaining customer attributes to determine the assignment eligibility. To allow for this use case we have provided the following rule:

YPM_RULE_PRICING_USE_SELECTION_CRITERIA_AS_OVERRIDE_TO_CUSTOMER

This rule will default to "N", but organizations can set this rule to "Y" to override customer attributes during getOrderPrice or getApplicablePricingRuleList.

1. Creates a draft order for the quantity 2.
2. Calls the changeOrder API to change the quantity to 5.

Condition: Index of each comma-separated data of RetentionDays will correspond to the respective AttributeValue. See https://www.ibm.com/support/knowledgecenter/SS6PEW_9.5.0/com.ibm.help.config.timetriggered.doc/configuration/r_OrderPurge.html for more information.

Operation: Run the OrderPurge agent.

Solution: Orders will be purged based on OrderAttribute (OrderType) apart from the existing PurgeCode based logic.

1. Creates and schedules a Sales Order with Item1 for Node1, that has the future inventory.
2. Adjusts the ONHAND inventory for Item1 at Node1.
3. Invokes the manageItemBasedAllocationTrigger to set IBARunRequired=Y for this Item and Node combination.
4. Triggers IBA agent. A user can see that SCHEDULE_HOLD gets applied on the order.
5. Applies the inventory node control by calling manageInventoryNodeControl API for Item1 at different node such as Node2.
6. Repeats the steps 1 to 4, the hold is not applied on the order.

• Attributes: ShipNode/ProcureFromNode/ReceivingNode/MergeNode/ExpectedDeliveryDate/ExpectedShipmentDate
• Elements: Details/ShipNode

Solution: Fixed to load the schedule only when the mentioned attributes or elements of OrderStatus are present in the template.

Solution : The packages which manifest for the current or prior date will be displayed on the "Ship Packages" screen.

1. Configures an enterprise as DEFAULT and Store1 as an organization being a Node and Seller.
2. Enables the payment processing for DEFAULT.
3. Disables the payment processing for the Seller.
4. Checks the payment rule of the use enterprise of an order to determine the payment processing rule.
5. Creates a customer account.
6. Creates an order with Store1 with the customer account payment method.
7. Ships and invoices the order.
8. Runs the payment API.

1. To enable Granular Locking, set the yfs.hotsku.useGranularLockingForItem property to Y. This property is in addition to the properties introduced for OLA.
2. To enable No lock for an inventory item while availability check, set the yfs.hotsku.qtyMultiplier property to a negative value. For example, yfs.yfs.hotsku.qtyMultiplier=-1.
3. It is recommended to set yfs.hotsku.assumeUnavailableOnLockTimeout=Y with this feature.

Condition: Invoke the inventory APIs such as findInventory.

Operation: Enable the template for a user exit getExternalCostForOptions, with the Supplies element present in it as per the java documentation.

Solution: Every assignment option generated will have the Suppliesdetails. This assignment option can be for a normal item or an item fulfilled with the procurement nodes or substitute items.

1. In the Outbound Shipment Console screen, searches for a shipment.
2. Opens the Shipment Detail screen.
3. Clicks on the action Print.

1. Creates an order of 2 order lines with the delivery method as PICK.
2. Schedules and releases the order.
3. Creates a shipment and makes sure that the shipment is in the Ready For Backroom Pick status.
4. Completes the backroom pick task and makes sure that order moves to the Ready For Customer status.
5. Performs the customer pick for one line item and short picks the other line item.
6. Makes sure that the shipment has a line with zero quantity.
7. Calls the getReshippableOrderLines API for the order.

1. Implements the YFSOrderRepricingUE user exit and additional line charges are included on the order or order line.
2. Triggers the YFSOrderRepricingUE user exit.

Solution: hffiles.ini is corrected to place the UE template in the correct location xapi/template/source/smcfs/userexit. The broken links in the javadocs for the input or output xml for YFSGetOrderExternallyUE are fixed.

1. Creates at least 20 ship nodes that have procurement allowed.
2. Creates the distribution group including all the nodes for the products being shipped. For example, DG_S and products being procured such as DG_P.
3. Sourcing rule for the fulfillment type such as PRODUCT_SOURCING has DG_S in the sequence 1 and procurement is allowed and for procurement rule, configures DG_P.
4. Sets the Default Transit days to 2 in the Logistics attribute.
   Solution:

   1. Adjust the inventory 1 at each node for an item ITEM_1. So we have overall 20 Units available across the network.
   2. Call getFulfillmentOptionsForLines for the quantity 15.

1. Adjusts inventory for an item at pack location.
2. Creates an outbound shipment.
3. Calls addToContainer API to pack the shipment.
4. Calls ChangeShipment API to stamp Airway_Bill_No in the YFS_SHIPMENT table.
5. Calls addContainerToManifest API.

Solution: As part of this enhancement, the promising APIs invoking getExternalCostForOptionsUE will consider the assignment quantities set by the implementation.

Solution: The attribute ShipToID is exposed in the changeOrder input to update ShipToID at the order header level on change of a customer.

1. Creates five nodes STORE_1, STORE_2, STORE_3, STORE_4 and STORE_5.
2. Sets up transfer schedules to STORE_1 from STORE_2, STORE_3, STORE_4, and STORE_5.
3. Adjusts an inventory for an item. For example, ITEM_1 at any of procurement node. For example, STORE_5 quantity: 5.
4. Sets the Minimize Number of Shipments to Customer Through Transfers Between Shipping Nodes flag to True.
5. Creates a sourcing rule with a distribution group consisting of all the nodes, STORE_1 to STORE_5.
6. Calls the FindInventory or ReserveAailableInventory API for ITEM_1.

1. Create an order with the two payment methods with pre-charge during the order creation.
2. Reduce the order total and run the payment APIs. Transfer out charge is created for the reduced total.
3. Create CTR for the partial amount that is to be released and invoiced.
4. Run processOrderPayments.

1. Creates stores NODE_1 and merge node NODE_2.
2. Creates a calendar at Ship Node NODE_1 from 00:00:00 IST to 23:59:00 IST, all days of the week.
3. Creates a calendar at merge node NODE_2 from 08:00:00 IST to 18:00:00 IST, all days of the week.
4. Creates the Node Transfer schedule from NODE_1 to NODE_2 with the transit time as 1 day.
5. Enables "Use Forwarding" flag under Forwarding/Transfer Rules.
6. Sets the Receipt Processing Time at merge node as 24 hours.
7. Creates a Sales Order. For example, if the current date is 2016-01-01, create an order with shipnode as NODE_1, merge node as NODE_2 and ReqDeliveryDate="2016-01-10 T0 8:00:00".
8. Schedules the order. Expected Delivery Date is stamped as "2016-01-09 T0 18:00:00".

1. Has a condition with one or more order fields. For example, 'OrderType equal to XYZ' and uses this condition in the pipeline determination rule to determine the pipeline for the order.
2. Reuses the above condition in an SDF service and on true or false of the condition calls the createOrder API.
3. Invokes the above SDF service with an input such that the condition returns true. For example, pass the input that has OrderType as XYZ.
4. Invokes the SDF service again with an input having blank values for the condition fields. For example, pass the input that has OrderType as blank.

Solution: Condition parameters to evaluate the condition are corrupt with the order line attributes. This is fixed so that the conditions evaluate to different results as per the order line input.

Condition: Invoke the inventory APIs such as findInventory.

Operation: Enable the template for a user exit getExternalCostForOptions, with the Supplies element present in it as per the java documentation.

Solution: Every assignment option generated will have the Suppliesdetails. This assignment option can be for a normal item or an item fulfilled with the procurement nodes or substitute items.

Solution: The default limit of 500 records is removed, so all the records can be fetched and deleted.

1. Creates at least 20 ship nodes that have procurement allowed.
2. Creates the distribution group including all the nodes for the products being shipped. For example, DG_S and products being procured such as DG_P.
3. Sourcing rule for the fulfillment type such as PRODUCT_SOURCING has DG_S in the sequence 1 and procurement is allowed and for procurement rule, configures DG_P.
4. Sets the Default Transit days to 2 in the Logistics attribute.
   Solution:

   1. Adjust the inventory 1 at each node for an item ITEM_1. So we have overall 20 Units available across the network.
   2. Call getFulfillmentOptionsForLines for the quantity 15.

1. Creates an Enterprise DEFAULT where default is Seller, catalog and Inventory Organization.
2. Creates a Node, STORE_1 in DEFAULT.
3. Creates an Enterprise ENT_1, where default is Seller, catalog and Inventory Organization. ENT_1 consumes inventory from organization DEFAULT.
4. Creates an Item, ITEM_1 in DEFAULT and also an item, ITEM_1 in ENT_1.
5. Adjusts Inventory for ITEM_1 for Inventory organization DEFAULT at STORE_1. For example, 10 Quantities.
6. Inventory item gets created for ITEM_1 - DEFAULT.
7. Calls find Inventory API or getATP API for ITEM_1 with ENT_1 Organization.

1. Creates ORG_1, which is Inventory, catalog and Seller.
2. Creates Store. For example, NODE1.
3. Creates ORG_2 which is Inventory, catalog and Seller. The ORG_2 consumes inventory from ORG_1.
4. Creates ORG_3 which is Inventory, catalog and Seller. The ORG_3 consumes inventory from ORG_1.
5. Creates ITEM_1 in ORG_1, ORG_2 and ORG_3 sharing the same GTIN ID.
6. Creates Store. For example, STORE_1.
7. Sets rule to consider STORE_1 for fulfillment at each Organization ORG_1, ORG_2 and ORG_3.
8. Adjusts Inventory for ITEM_1 at ORG_1.For example, 100 Quantities.
9. Creates Order for ITEM_1 at STORE_1, 10 Quantities and Requested Date in future for ORG_2 .
10. Schedules the Order.
11. Calls findInventory API for ITEM_1 at STORE_1 for ORG3, 100 quantities.

The Demand of 10 quantities by ORG_2 at STORE_1 for ITEM_1 is not considered, during fulfillment suggestion of ITEM_1 at ORG_3.

This causes failure in the configure batch flow of the Sterling Store.

1. Creates pricingRule.
2. Creates pricingRuleAssignment for CustomerId="BC1".
3. Creates pricingRuleAssignment for CustomerId="BC2".
4. Sets getOrderPrice with CustomerId="BC1".
5. Sets getOrderPrice with CustomerId="BC2".

Either step 4 or step 5 will not have the pricingRule applied despite an eligible order.

There was a caching issue where only top element was returned instead of all the specific assignments. All eligible assignments are now considered.

Updated and added files:

• OMPOrderShardEP.java
• YFSApiImpl.javajava
• YFS_HIST_ORDER.java
• YFS_HIST_SHIPMENT.java
• YFS_Source.javaclass
• YFSRestoreCoordinator.java
• YFSRestoreHelper.javaclass
• YFSRestoreManager.java
• YFSRestoreShipments.java
• YFSRestoreWorkOrders.java
• OMPOrderShardEPImpl.java
• YFSGetOrderExternallyUE.java
• YFSUserExistConsts.java
• YSCUserExitProxy.java
• YCP_YFS_USER_EXIT.xml
• YFS_GetOrderExternallyUE_input.xml
• YFS_GetOrderExternallyUE_output.xml

1. Setup the inventory purge.
2. Have some inventory supplies with some supplies having a supply type that does not match with the ship nodes availability type. The supply records must exceed the NumRecordsToBuffer of purge config. Also have some demand records which are eligible for purge.

Solution: The purge logic fetches the eligible inventory supply records completely after filtering.

Solution: The upgrade script issues a message instead of throwing an error, when a view with the same name already exists in the older version.

1. Creates ORG_1, which is Inventory, catalog and Seller.
2. Creates Store, For example, NODE1.
3. Creates ORG_2 which is Inventory, catalog and Seller. The ORG_2 consumes inventory from ORG_1.
4. Creates RTAM rules for both the organization.
5. Creates ITEM_1 in ORG_1 and ORG_2 sharing the same GTIN ID.
6. Adjusts Inventory for ITEM_1 at ORG_1, say Quantity 100; activity will be created for ITEM_1 at NODE1 for ORG_1.
7. Runs RTAM in activity based mode.

1. Ensures that multiple supply records exist in the YFS_INVENTORY_SUPPLY for the same Item-Node-SupplyType. For example, ITEM_1 - NODE1 - OHNAND.
2. Calls adjust inventory with AdjustmentType as ABSOLUTE for ITEM_1 - NODE1 and ONHAND supply type.

Solution: When OLA is turned ON and when the supply record must be deleted as a part of any transaction, the supply record is updated as zero.

1. Configures an item as the tag controlled item, and sets a batch number as the tag identifier and a manufacturing date as the tag attribute.
2. Creates an inbound order with the buyer and seller organization code and confirms the inbound order.
3. Creates a shipment for the above created order.
4. Performs the report or record receipt task for the above created order from the application console.

Condition: When invoking the manageItem API, set the AssociateItemToCategories attribute to Y for Action= Create/Manage.

Operation: Invoke the manageItem API per the above condition.

Solution: A new attribute AssociateItemToCategories is introduced in the input to manageItem API to perform the Category-Item association during the item creation. The valid values are Y or N.

Configuration: Set IsExtensible=Y, in ysc_tables.xml (YFS_Attribute and YFS_Additional_Attribute) and ycm_tables.xml (YFS_Kit_Item) in the entity definition.

Condition: Build entityjar and then build smcfsear.

Operation: Extensions of the custom columns for the three tables mentioned is possible with above details.

Part 2: manageItem API is enhanced to persist the data in the YFS_ATTR_ALLOWED_VALUE table based on the flag InsertMissingAttributeAllowedValues set at the ItemList level.

Configuration: N/A

Condition: Valid values for the new flag InsertMissingAttributeAllowedValues at the ItemList level is Y or N.

Operation: Invoke the manageItem API with Action=Manage.

Solution: When the existing flag ValidateAdditionalAttributeValues is set to Y at ItemList level in manageItem API, the system validates the value (present in yfs_addtional_attribute) to be associated to an item attribute against corresponding attribute allowed values (part of yfs_attr_allowed_value). Currently the YSC84_0006 error code is thrown when the validation fails. The value of yfs_attr_allowed_value table can be a a free text or a number (decimal or integer in the range or list format). This enhancement is about the manageItem API inserting the data into the table yfs_attr_allowed_value, when validation fails (because of the error code YSC84_0006). The insertion logic is controlled when the InsertMissingAttributeAllowedValues flag is set to true.

• Gift-card Tender=50
• Credit Card=441.55

Overall order-Total=491.55

• Release both the order lines.
• Ship both the units of PrimeLineNo=1.
• Invoice the shipment and collect the invoice by running the ProcessOrderPayments API.
• At this stage, return one quantity of PrimeLineNo=1.
• Invoice the return order. ReturnOrder Total=114.
• Run the requestCollection API.

Problem: Charge transaction record should be opened for $64 ($114 - $50) instead of $114.

1. Enables and implements YFSRecalculateLineTaxUE.
2. Calls createOrder and changeOrder (changeOrder API call does not have any attribute changes that affect pricing) within a single multiAPI call.

Solution:

1. Implement the YCDCanPriceMatchBePerformedUE user exit with a reference implementation provided by YCDCanPriceMatchBePerformedUEImpl user exit.
2. From Sterling Call Center, open an order and select the price match related task.

Condition: Set DisableBundleLookup to Y or N at the Order Line level for the bundle parent item during createOrder.

Operation: Invoke the createOrder API as per above condition.

Solution: Bundle components will not be created, if the flag DisableBundleLookup is set to Y at the Order Line level for a bundle parent item during createOrder. Order fulfillment will have an impact, if the attribute value is set to true without a valid use case.

1. Creates a shipment for one quantity of an item with one shipment line.
2. Packs the shipment in a container.
3. Runs removeFromContainer API for that Shipment.

1. Creates a configurable Model such that an Option Class has a SKU attached with the Quantity selection, and has child Option items.
2. Associates this to a configurable bundle item and initiates quote creation from the Sterling Field Sales.
3. Adds the item to quote and starts configuration.
4. Selects the option class, provides a quantity value and makes option item selections.
5. Views the Summary and saves the quote.

Solution : A new numeric property, kitQty is created, and the value of this at the option item picks is set to the effective multiplier quantity using a Rule.

The value of this kitQty is considered, when calculating quantities and prices on the SIC screens. For example, oc1(qty=3) |-> oi1 (qty=1, kitQty=3) |-> oc2 (qty=2, kitQty=3) |-> oi2 (qty=1, kitQty=6).

1. Creates an Order for 6 quantities.
2. Creates shipment with same quantity and makes sure that it goes to "Ready for backroom pick" status.
3. Calls changeShipment API to reduce the shipment quantity to 3 quantities with CancelRemovedQuantity="Y" and CancelShipmentOnZeroTotalQuantity="Y".
4. Logs in to Sterling Store application and completes picking up all the 3 quantities.
5. Navigates to Pack screen and packs 2 quantities and marks shortage for 1 quantity.

1. Creates Item. For example, ITEM_1.
2. Creates Node. For example, STORE_1.
3. Creates sourcing rule for STORE_1 to be used for sourcing.
4. Implements OMPGetSourcingCorrectionsUE user exit to not return any of the Nodes.
5. Calls findInventory for ITEM_1.

1. Disables the PAYMENT_EXECUTION agent.
2. Creates an Order with multiple Gift cards and the Gift cards are pre-charged for the Order Total.
3. Includes Discounts on the order such that one of the cards is refunded completely.
4. Runs requestCollection API to open the refund CHARGES. The CHARGES are in OPEN status.
5. Calls changeShipmentInvoice API to Invoice the order, and the changeOrder API to give further discount on the order, followed by the requestCollection API, all APIs are in the same transaction boundary using multiApi.

Solution: This issue is fixed.

1. Sets up Item, Node and Distribution group. For example, ITEM_1, STORE_1, DG_1, and Real Time Availability Monitoring rules.
2. Adjusts Inventory for the Item at STORE_1. For example, 100 quantities.
3. Sets up Node capacity at STORE_1. For example, 20 Units for each day.
4. Runs RTAM and checks for availability alert at this time, the availability is published correctly as the on hand available date is set to the current date.
5. Creates Order for 20 quantities and schedules at STORE_1. The Capacity is consumed for the Current date.
6. Runs RTAM. Availability published is 80 quantities for the current date.

1. Goes to System Setup > Pricing > Validation Policies and Override Rules > Pricing in Sterling Business Center.
2. Selects "CPN_GRACE_PERIOD" from the "Policy List" and goes to 'Override Rules' tab.
3. Creates new Override Rule by using 'Days Before Start Of Coupon It Is Used Is' attribute in the UI condition with NOT condition and saves the rule.

1. Creates an Order.
2. Schedules an order.
3. Releases an order and calls CreateShipment API.
4. Creates a Shipment Container for the Shipment.
5. Calls the getShipmentList API with SelectMethod=NO_LOCK as the input and output template with container details. The YFS_ORDER_HEADER record select query is fired with FOR UPDATE

Solution: The SelectMethod is set as WAIT, only if it is not passed in the input.

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.