IBM Support

IJ49062: WHILE CREATING DESKTOP REQUISITION OF SERVICE ITEM, THE SYSTEM DOES NOT BRING UNIT COST FROM PURCHASE CONTRACT

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • STEPS TO REPRODUCE:
    
    1. Go to Purchase Contracts application.
    
    
    2. Create a new Purchase Contract against Vendor BWC.
    
    
    3. Go to Contract Lines tab.
    
    
    4. Enter 2 new Contract Lines as the following info:
    
    Line 1:
    Line Type: Item
    Item: EB12 - 12 Volt Battery
    Quantity: 10.00
    
    Order Unit: EACH
    
    Unit Cost: 10.00
    
    
    Line 2:
    Line Type: Standard Service
    Item: ELEV - ELEVATOR REPAIR SERVICE
    Quantity: 10.00
    
    Order Unit: EACH
    
    Unit Cost: 10.00
    
    
    5. Save the record.
    
    
    6. Authorize the BEDFORD Site.
    
    7. Approve the Contract.
    
    8. Go to Create (Desktop) Requisition application.
    
    
    9. Accept the default values and click on Continue.
    
    10. In the Requisition Line Items section, click on New Row
    button.
    
    11. Enter the following info:
    Line Type: Item
    
    Item: EB12 (then hit the Tab key)
    Vendor: BWC (then hit the Tab key)
    
    12. Note that the system brings up the Unit Cost 10.00 from the
    Purchase Contract above. That's OK.
    
    
    13. Enter Quantity 1.00.
    
    14. Still in the Requisition Line Items section, click on New
    Row button again.
    
    15. Enter the following info:
    Line Type: Standard Service
    Item: ELEV (then hit the Tab key)
    Vendor: BWC (then hit the Tab key)
    
    RESULTS:
    When the Line Type is Standard Service, the system does not
    bring the Unit Cost from the Purchase Contract and the Unit Cost
    remains zeroed. This is the issue.
    
    EXPECTED RESULTS:
    The system should bring the Unit Cost from the Purchase Contract
    regardless the Line Type.
    
    REPORTED IN VERSION:
    IBM Maximo Asset Management 7.6.1.3
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * _MAXIMO_                                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * WHILE CREATING DESKTOP REQUISITION OF SERVICE ITEM, THE      *
    * SYSTEM DOES NOT BRING UNIT COST FROM PURCHASE CONTRACT       *
    ****************************************************************
    Currently,
    When the Line Type is Item,
    and when we add the itemnum the system brings up the standard
    cost from the inventory as unit cost.
    and when we add the vendor, the system brings up the unit cost
    from the purchase contract for that particular vendor.
    The Issue -
    When the Line Type is Standard Service (or line type any other
    than item and tool), the system does not bring the Unit Cost
    from the Purchase Contract and the Unit Cost remains zeroed.
    After the fix -
    When the Line Type is Standard Service / Service / Material
    (line type any other than item and tool),
    and when we add the itemnum, the system does not bring the Unit
    Cost as there is no standard cost for it.
    and when we add the vendor, the system brings up the unit cost
    from the purchase contract for that particular vendor.
    

Problem conclusion

  • The fix for this APAR will be contained in a future release.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ49062

  • Reported component name

    PURCHASING

  • Reported component ID

    5724R46PU

  • Reported release

    760

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-10-30

  • Closed date

    2023-11-01

  • Last modified date

    2023-11-01

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    PURCHASING

  • Fixed component ID

    5724R46PU

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"760","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
01 November 2023