IBM Support

High CPU utilization on findInventory API call with very high reqEndDate attribute, in a procurement transfer scenario

Question & Answer


Question

Why high CPU utilization is observed while using findInventory API with very high reqEndDate attribute, in a procurement transfer scenario  ?

Cause

Scenario -
Define Item I having inventory at procuring node P.  Shipping node S does not have inventory for Item I.
Do not define the transfer schedule and shipping and receiving calendar. Also, have zero node capacity at procuring node and capacity is defined as slot based.
Call a findInventory API with below sample input XML i.e. with  ReqEndDate="2500-01-01" -
-----------
<Promise AllocationRuleID="SYSTEM" OrganizationCode="DEFAULT">
    <PromiseLines>
        <PromiseLine ItemID="I" LineId="1"
            ReqEndDate="2500-01-01" RequiredQty="1" UnitOfMeasure="EACH" kitQty="1"/>
         </PromiseLines>
</Promise>
-----------
High CPU utilization will be observed and system performance degrades drastically.

Answer

This happens because of the very high reqEndDate passed in the findInventory input XML.  Passing high date will increase the window period for finding an item and hence one should pass only the realistic window, if at all it needs to be passed.

Either ReqEndDate should be passed as valid finite date as per business use case or if not provided in input, it  will get calculated based on scheduling rules.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS6PEW","label":"Sterling Order Management"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.5","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Product Synonym

Sterling OMS

Document Information

Modified date:
18 April 2019

UID

ibm10881722