IBM Support

IV75475: MRLINE AND MRCOST HAVE DIFFERENT VALUES WHEN A THERE IS A SINGLE REQUISITION LINE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If there is a single MR Line that has a different GL Account
    than what is entered on the MR Header, the MR Line's GL Account
    does not populate, or overwrite the GL Account on the MR
    Header
    Steps To Reproduce:
    Use the following steps to submit a single-line MR that gets
    charged to a GL instead of a Storeroom (GL Account on MR header
    will be the GL Account for the MR Line); then create a PR, then
    PO, and then recieve the PO:
    -Log in to maxdemo instance as wilson
    -Go To Self Service | Desktop Requisitions | Create Requisition
    -In the Gl Debit Account field | Select Value
    -Click 6000, then 200, then 200, then OK
    -Click the Continue button
    -Click the New Row button
    -In the Item field | Detail Menu | Select Value | click any
    item, such as 8N-3080
    -In the Quantity field enter 1
    -In the Order Unit field enter "each" and tab out
    -In the Unit Cost field enter 3 and tab out
    -Click the Continue button
    -Click the Submit button
    -In the Requisition Submitted dialog click the View Details
    button
    -In the Requisition Line Items section click the Line number
    -In the Line Details dialog | PR field | Detail Menu | Go To
    Purchase Requisitions
    -In the Company field enter "almar" and tab out
    -Select Action | Create PO
    -In the Create PO dialog click the Autonumber button
    -Note the PO number and click OK
    -Click the Return hyperlink, then click OK
    -Go To Purchasing | Purchase Orders
    -In the PO field enter the PO number that was just generated
    from the requisition and press Enter
    -Click the record to open it
    -Click the Change Status button on the toolbar
    -In the New Status field use the drop-down arrow to click
    Approved
    -Click OK
    -Go To Purchasing | Receiving
    -In the PO field enter the PO number that was just Approved and
    press Enter
    -Click the record to open it
    -Click the Select Ordered Items button
    -Click the checkbox for the PO Line
    -Click OK
    -Save the record
    Use the following steps to create another single-line MR and
    enter a GL Account on the MR Header (do not use the same GL
    Account that was used on the first MR);
    the GL Account on the MR Line will be different than the GL
    Account on the MR Header:
    -Go To Self Service | Desktop Requisitions | Create Requisition
    -In the Gl Debit Account field | Select Value
    -Click 6100, then 229, then 300 (select different GL Codes than
    what were used on the first requisition), then OK
    -Click the Continue button
    -Click the Add Line Item button | Existing Requisitions
    -In the Previously Requisitioned Items section highlight the
    Item that was used on the first requisition
    -In the Quantity field enter 1
    -In the Required Date field click the Select Date and Time
    button and click on the date that is two days from now; click
    on any time, such as 09:00 AM, then click OK
    -Click the Add To Requisition button
    -Expand the details and observe that the GL Debit Account is
    different than the GL Debit Account that was entered on the MR
    header (expected)
    -Click the Submit button
    -Query the database and observe that the GL Debit Account value
    is different between the mrcost and mrline tables:
    select mrnum, linecost, gldebitacct from mrcost where mrnum =
    '<the second requisition>';
    MRNUM      LINECOST GLDEBITACCT
    -------- ---------- -----------------------
    1005              3 6100-229-200
    select mrnum, linecost, gldebitacct from mrline where mrnum =
    '1005';
    MRNUM      LINECOST GLDEBITACCT
    -------- ---------- -----------------------
    1005              3 6000-200-200
    *The results indicate that if there is a single MR Line, that
    has a different GL Account than what is entered on the MR
    Header, the MR Line's GL Account does not populate, or
    overwrite the GL Account on the MR Header.  The issue is that
    there is a different GL Account being committed in the MRCOST
    and MRLINE tables for the same transaction.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users who are selecting an Existing Requisition line when    *
    * performing the Add Line action during Desktop Requisition    *
    * creation.                                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When a line is added to a new Desktop Requisition using Add  *
    * Line > Existing Requisition, if the new line has a different *
    * GL Account than the Desktop Requisition header, then the new *
    * MRCOST row will have the wrong GL Account.                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply Fixpack Release 7.5.0.10 or later.                     *
    ****************************************************************
    

Problem conclusion

  • Now, when a line is added to a new Desktop Requisition using Add
    Line > Existing Requisition, if the new line has a different GL
    Account than the Desktop Requisition header, then the new MRCOST
    row has the same GL Account as the new MRLINE row.
    
    The fix for this APAR is contained in the following maintenance
    package: Fixpack Release TPAE 7.5.0.10.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV75475

  • Reported component name

    PURCHASING

  • Reported component ID

    5724R46PU

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-07-24

  • Closed date

    2015-11-04

  • Last modified date

    2015-11-04

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

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

Modules/Macros

  • MAXIMO
    

Fix information

  • Fixed component name

    PURCHASING

  • Fixed component ID

    5724R46PU

Applicable component levels

  • R750 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCHPN3","label":"Purchase Requisitions"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"750","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 November 2015