Resolved issues

Solution: This issue is resolved. The records that fail to synchronize with Order Service remain in the YFS_Awaiting_Index table and are picked up in the next iteration of the SSI Delayed Sync agent.

Solution: This issue is resolved and the yfs.suppressModTypeValidationForCancelledOrders property has database support. For more details, check yfs.suppressModTypeValidationForCancelledOrders property in the properties guide.

Solution: This issue is resolved.

Solution: This issue is resolved. The Manage Variations page displays the custom attributes correctly.

Solution: This issue is resolved and more debug logging is added for Task queue segregation feature.

Solution: This issue is resolved.

• When organization maintains external inventory and multiple sourcing sequences are present in sourcing rules.
• Not enough inventory is available in the first sourcing sequence, so the line gets expanded to the next sourcing sequence.

Solution: This issue is resolved. A new business rule READ_GTIN_AVAIL_UNPUBLISHED_ITEMS is introduced with the default value as Y. To suppress inventory read for Unpublished GTIN items, set the rule to N for the inventory organization.

1. Create Order1 using Item1 for 1 qty having no available supply. Schedule the order and the order moves to Backordered status.
2. Create Order2 using the same item for 1 qty but with 1 available supply. Schedule the order and the order moves to Scheduled status.
3. Run IBA agent and both the orders change to hold.
4. Run the schedule order agent. The hold status gets resolved but Order1 is still in Backordered state while Order2 is in Scheduled status.

Solution: This issue is resolved and the CONSIDER_BACKORDER_DEMAND_FOR_IBA rule must be set to Y.

1. A listener is implemented between Sales Order and Transfer Order pipelines. The listener listens to Transfer Order Scheduled status and updates Sales Order line status when Transfer Order is scheduled.
2. Under Logistics Management, Delivery Schedule is configured for the used CarrierServiceCode in Step 1 with Allow Up To Days Of Non-Transit Time For An Item as blank.
3. The Sales Order is created with CarrierServiceCode passed on the OrderLine.
4. The Sales Order is scheduled and Procurement Transfer Order is created.
5. The Transfer Order is Scheduled.

Solution: This issue is resolved. The executeCollection API is enhanced to keep the authorization record open when the Payment Execution User Exit returns zero authorization, provided the threshold set by yfs.payment.zeroAuthCTRThreshold is reached.

For more information, check the yfs.payment.keepAuthOpenForZeroAmt property in the properties guide.

Solution: This issue is resolved. When the yfs.siv_integration.skipAvailabilityCacheForAllNodesShip is set as true, the node availability is read based on distance or nearby node attribute.

Solution: This issue is resolved. The Shipment Notes is getting preserved when order is canceled.

Solution: This issue is resolved. When infinite loop error happens while fetching order details, the subsequent API call in the same transaction updates the order header record.

Solution: This issue is resolved. The MIN_SHIP_BY_DATE on demand adjustments created by purge during purging reservation inherits the value from the original reservation.

1. Enable the override transfer schedule between nodes by using a carrier service feature. A CarrierServiceCode is configured for transferring inventory between the nodes and yfs.overrideTransferScheduleForProc property is set to true.
2. A listener is implemented between Sales Order and Transfer Order pipelines that listens to Transfer Order Scheduled status and updates Sales Order line status to reflect the Transfer Order is scheduled.
3. The Sales Order is created for a line requiring Special Service and Carrier Service specified by passing CarrierServiceCode attribute.
4. The Sales Order is scheduled. Inventory is not available in Shipping Node and a Procurement Transfer Order is created.
5. The Sales Order ETS in calculated with Special Service processing Time included in ExpectedShipmentDate.
6. The Transfer Order is Scheduled.

Solution: This issue is resolved. The Sales Order ExpectedShipmentDate timestamp is now calculated as per ProcurementNode Carrier Pick up schedule, Special Service processing Time at ShipNode, and ShipNode's Carrier Pick up schedule, and not defaulted to 00:00.

Solution: This issue is resolved.

Solution: This issue is resolved. When the events are configured at the enterprise level, the AFTER_DELETE and AFTER_MODIFY events are generated as expected.

Solution: This issue is resolved. The part of code causing this issue is made threadsafe.

Solution: This issue is resolved. The shipment notes does not get deleted when the shipment is canceled and the Shipment Notes JavaDocs is updated as follows:
If Action is Cancel, then except for the shipment, shipment lines, and shipment notes, all related entities are deleted.

Solution: This issue is resolved.

Solution: This issue is resolved.

Solution: This issue is resolved.

Solution: This issue is resolved.

A new property yfs.readResourcePoolsForNodesWithInventory is introduced. When the property is set to true, the product does not retrieve capacity for nodes with no inventory.

Solution: This issue is resolved.

1. Create NODE1 and NODE2 with shipping calendar and working hours from 01:00 to 23:59 and Sunday as non-working.
2. Mark May 22 and May 23, 2025 as holiday in the node shipping calendars.
3. Create node transfer schedule from NODE1 to NODE2. Mark Sunday as cannot ship and default transit time as 2 days, daywise override for Sunday to Thursday as 0 transit time, and Friday and Saturday as 3 days transit time.
4. Create node transfer schedule and mark the following overrides:
   • For May 20, 2024 - 4 days transit time
   • For May 21, 2025 - 5 days transit time
5. Adjust inventory at node NODE1 for an item.
6. Call the FindInventory API with ShipNode as NODE2 and ProcureFromNode as NODE1 and ReqStartDate as May 24, 2025.
   The FindInventory output is observed as follows:
   At NODE1, assignment shipDate is May 21, NODE2 assignment shipDate is May 24, ProductAvailable date at NODE2 is May 26.
   he FindInventory output is expected as follows:
   At NODE1, assignment shipDate is May 20 and at NODE2 assignment shipdate is May 24.

Solution: This issue is resolved.

A new property yfs.considerNodeHolidayDuringBackwardCalculationOfProc is added with default value as false. If you set the property to true, during backward shipdate calculations, the product considers shipnode holidays from shipping calendar even if they are not marked in the node transfer schedules.

Solution: This issue is resolved.

Solution: This issue is resolved.

In the Entity Relationship Diagram (ERD) documentation, the ACTIVATE_FLAG column in the YFS_SHIP_NODE table is deprecated.

When SBA is enabled, the contract order key is stored in the CONTRACT_ID column of the YFS_SBA_ORDER_LINE_STATUS table. This column's data type does not align with the corresponding column in the YFS_CONTRACT_ORDER table.

Solution: This issue is resolved.

The contract order ID is stored in the new column CONTRACT_ORDER_ID of the YFS_ORDER_HEADER table for orders created from a contract.

When SBA is enabled, the contract order key is stored in the new column CONTRACT_ORDER_KEY of the YFS_SBA_ORDER_LINE_STATUS table.

Solution: This issue is resolved.

Solution: This issue is resolved.

The getPossibleSchedules API is fixed to ignore the generating promise line when the delivery method is CARRY.

Solution: This issue is resolved.

Solution: This issue is resolved.

The getOrderInvoiceList API is enhanced to support the <OrderBy> element. For more information, see getOrderInvoiceList API documentation.

Solution: This issue is resolved.

The manageNodeTransferSchedule API javadocs is updated.

Solution: This issue is resolved.

Solution: This issue is resolved.

Solution: This issue is resolved.

The order line key is displayed in the error stack.

Solution: This issue is resolved.

Issue: The user is not able to modify any aspect of the routing guide after they add multiple freight term values.

Solution: This issue is resolved.

The manageRoutingGuide API is enhanced to update routing guide with multiple freight term values.

Issue: In an Sterling Intelligent Promising Inventory Visibility-integrated environment with Adapter Phase2, the getCompleteItemList API displays an error when a distribution group is not passed in the API input and is not configured in the basic configuration.

Solution: This issue is resolved.

Solution: This issue is resolved. The order moves to the Procurement Transfer Order Created status.

Issue: Inventory visibility reservation is not used during order creation if nonzero lead days are configured for an item.

Solution: This issue is resolved.

Solution: This issue is resolved. The capacity is freed from all nodes.

Issue: When an invalid line error occurs during the changeOrder API call, the error stack does not mention the order line key.

Solution: This issue is resolved. The order line key is displayed in the error stack when an invalid line error occurs during the changeOrder API call.

Issue: The parent item description is displayed instead of the substitution item description in the getShipmentDetails API response after the substitution.

Solution: This issue is resolved. The getShipmentDetails API is fixed to display the substitution item description in the response.

Issue: When the retry flag is Y from the PAYMENT_EXECUTION transaction user exit output, then the existing mappings in the YFS_PAYMENT_REASON_MAPPING table are deleted.

Solution: This issue is resolved.

Issue: In a Sterling Intelligent Promising Inventory Visibility reservation call from Sterling Order Management System Order Schedule and release in IV-integrated environment with Adapter Phase2, the Accessing context outside creating thread error occurs intermittently.

Solution: This issue is resolved.

Issue: When the payment rule is set to collect payment externally, then the infinite loop error occurs while processing refunds or discounts.

Solution: This issue is resolved.

Issue: The orders that consist of the NOT_APPLICABLE payment status are not getting purged.

Solution: This issue is resolved.

The Order Purge Agent is enhanced to purge orders with the NOT_APPLICABLE payment status.

Issue: When multiple procurements are from the nodes with same cost, date and quantity are eligible to fulfill the request, order scheduling fails intermittently.

Solution: This issue is resolved.

Issue: The getChargeTransactionList API does not have a limit on the maximum records that can be retrieved in the output.

Solution: This issue is resolved.

The getChargeTransactionList API is enhanced to retrieve the number of records based on the value that is set for the MaximumRecords attribute. Default is 5000 records.

Solution: This issue is resolved.

The Sterling Order Management System application is enhanced to support IBA with PostgreSQL database.

Issue: getAvailableInventory API returns total accumulative availability and does not filter the availability to match the tag information that is provided at PromiseLine input.

Solution: This issue is resolved.

getAvailableInventory API is enhanced to return the availability based on the tag information that is provided as part of PromiseLine input.

Issue: The option to use AWS S3 sdk JAR files is not available for deploying applications.

Solution: This issue is resolved. The AWS S3 sdk JAR files and the related dependent JAR files such as jackson and joda-time are added to the Application class path and are available for deploying applications.

Issue: In the getOrderInvoiceDetails API, when the CollectionDetails element is used without a child element, the stack overflow error occurs.

Solution: This issue is resolved.

Issue: The getExternalCostForOptionsUE user exit is enhanced to show the capacity usage information when resource pool exists for the assignment nodes.

Solution: This issue is resolved.

Issue: The PageSetToken attribute in the getPage API documentation is updated to provide information about maximum number of tokens that are retained in the cache.

Solution: This issue is resolved.

Solution: This issue is resolved.

Issue: When you compress data for columns with compression enabled, the application cannot compress special characters. Instead, a duplicate text is created.

Solution: This issue is resolved.

If the application fails to compress the data, the uncompressed data is saved in the database, to prevent data corruption that might occur during compression.

Issue: The Order Monitor agent stamps the future date in NEXT_ALERT_TS instead of the current date when the agent is expected to again raise alerts until a specific date.

Solution: This issue is resolved.

The Order Monitor agent now stamps NEXT_ALERT_TS as the current date when it is required to again raise alerts until a specific date.

Issue: For external promotions, the award description that is provided in the input is not saved.

Solution: This issue is resolved.

Issue: When a return order includes both bundle parent and component lines, duplicate component lines are created.

Solution: This issue is resolved.

In the return order creation XML, the DerivedFrom element now retrieves the derived order based on the combination of DocumentType, EnterpriseCode, and OrderNo.

Issue: When the yfs.useNewRoundOffPriceForConventional property is enabled, prices are rounded off, but charges are not.

Solution: This issue is resolved.

When the yfs.useNewRoundOffPriceForConventional property is enabled, similar to prices, charges are also rounded off.

Issue: When the api.security.mode property is set to LAX, the extended elements corresponding to a hang-off table are not populated.

Solution: This issue is resolved.

Issue: When the getTrackingNoAndPrintLabel API throws exception, it is not recorded in the log file.

Solution: This issue is resolved.

Issue: CurrentStorePickup/Pickup/@ProcureFromNode does not reflect the correct procure from node value when IsProcurementAllowed=Y is passed in input of the getStoreAvailability API.

Solution: This issue is resolved.

The CurrentStorePickup/Pickup/@ProcureFromNode now reflects the correct procure from node value from where procurement is evaluated in the getStoreAvailability API output.

Solution: This issue is resolved.

Issue: In an Sterling Intelligent Promising Inventory Visibility-integrated environment with Adapter Phase2, under low availability conditions, on calling the reserveAvailableInventory API, the application occasionally displays a null pointer exception.

Solution: This issue is resolved.

The priority order remains in the backordered status and the non-priority order remains in the scheduled status. Instead, the priority order must move to the scheduled status and non-priority order must be backordered.

Solution: This issue is resolved.

A new CONSIDER_BACKORDER_DEMAND_FOR_IBA rule is introduced with the default value set to N. Ensure that you call the manageRule API to change the value to Y to avoid this issue.

Issue: After you upgrade to fix pack 2403.2, the The input XML to YFSGetAvailabilityCorrectionsForItemListUE does not contain all zero supply records for nodes, which are eligible from previous sequences and had zero supply.

Solution: This issue is resolved.

A dummy supply is added to the YFSGetAvailabilityCorrectionsForItemListUE input for all the eligible nodes from previous sequences and had zero supply.

Issue: The data extract SFTP process to customer's AWS SFTP fails when they upgrade to the latest security policies of AWS from TransferSecurityPolicy-2020-061 to TransferSecurityPolicy-2024-01.

Solution: This issue is resolved.

The JSch (Java Secure Channel) library is upgraded from 0.1.55 to 0.2.21, which supports the latest key exchange algorithms for SFTP and works with AWS SFTP adopting security policies from TransferSecurityPolicy-2024-01.

Issue: Incorrect demand updates are observed for tag items with hot SKU when the Summarize and Maintain Total Supply and Demand rule is enabled.

Solution: This issue is resolved.

Issue: The INVENTORY_KEPT_EXTERNALLY configuration is not inherited by organizations that are positioned lower by multiple levels within the organizational hierarchy.

Solution: This issue is resolved.

Issue: The adjustInventory API, when used with AdjustmentType set to ABSOLUTE and RemoveInventoryNodeControl as A, it incorrectly generates inventory activity records, even when there are no yfs_inventory_node_control records to delete and no changes to the supply picture.

Solution: This issue is resolved. A new record is now created only if yfs_inventory_node_control records are available for deletion, and a corresponding inventory activity record is not present.

Issue: When capacity locking is enabled, a lock is observed for inquiry APIs, such as findInventory and getPossibleSchedules that leads to high lock contention, and thus results in slowness.

Solution: This issue is resolved.

Issue: The capacity cache is not updated intermittently because the process for updating the cache is terminated when it encounters an error.

Solution: This issue is resolved.

A new yfs.capacityAvailablity.jvmcache.maxRetry property is added, which governs how many retries the process can go through before the cache is terminated.

Issue: The orphan records in the YFS_SUB_FLOW table leads to issues while starting a server.

Solution: This issue is resolved.

The subflow records with no corresponding flow records that are stamped on them are ignored during the server startup after logging an error.

Issue: In Applications Manager, click Application Platform. Go to Security > Groups > Group Details > Security. In the Permissions tab, when you view resource permission group, some of the listed components do not display the correct component name.

Solution: This issue is resolved.