IBM Support

IJ40729: GL DEBIT ACCOUNT FIELD ( MATRECTRANS.GLDEBITACCT ) IS DIFFERENT TO POLINE.GLDEBITACCT AND PRLINE.GLDEBITACCT

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

  • GL Debit Account field ( MATRECTRANS.GLDEBITACCT ) is different
    to the Account number that exists in both the GL Debit Account
    field in the PO ( POLINE.GLDEBITACCT ) and the GL Debit Account
    field in the PR ( PRLINE.GLDEBITACCT ).
    
    PROBLEM:
    
    In the receiving application, when changing the inspection
    status of an Item, the GL Debit Account field (
    MATRECTRANS.GLDEBITACCT ) is different
    
    to the Account number that exists in both the GL Debit Account
    field in the PO ( POLINE.GLDEBITACCT ) and the GL Debit Account
    field in the PR ( PRLINE.GLDEBITACCT ).
    
    1. The above is seen when a NEW Item is created.
    
    2. If however, you use an Item that ALREADY EXISTS in a
    storeroom, the above is NOT seen - the account number in
    MATRECTRANS.GLDEBITACCT is the SAME as POLINE.GLDEBITACCT and
    PRLINE.GLDEBITACCT.
    
    The client would like an explanation for the difference in
    Scenarios  1 and 2 above.
    
    
    ACTION TAKEN:
    
    I can reproduce both scenarios above.
    I have searched docs for an explanation for the above behaviour
    without success.
    
    
    STEPS TO REPRODUCE:
    
    
    I can repro with these steps:
    
    Step 1:
    In the Item Master application:
    Create a NEW Item (1004). Condition Enabled is Checked.
    
    
    Add 2 condition code rows New and Used.
    
    Go to Storeroom tab and confirm the item does not exist in any
    storeroom.
    
    Make Item Status is Active, Check the "Roll to Orgs and
    inventory" checkbox.
    
    
    Step 2:
    In the PR application:
    Create PR - 1036
    
    Add Vendor (SKF)
    
    Go to PR lines Tab:
    
    PR Lines Details:
    
    Item: 1004
    
    Inspection Required: Checked:
    
    Storeroom: Central
    
    Order Unit: Each
    
    Conversion: 1
    
    Unit Cost: $100
    
    GL Debit Account: 6610-810-200. (Choose Manually, not default
    value).
    
    
    Step 3:
    In the PR application:
    More Actions > Create PO with Auto Number (1096).
    
    Go to the PO Application:
    Go to PO Lines Tab - all info including the GL account is the
    same as above.
    
    
    Step 4:
    In the PO Application:
    Change POs status from WAPPR to In Progress.
    
    
    Step 5:
    Go to the Receiving Application and find PO 1096.
    
    Click Select Ordered Items and check Item 1044.
    
    It is added to the Receiving record.
    
    
    Step 6:
    In the Receiving Application:
    Set the "To Condition Code" field to NEW.
    
    
    Step 7:
    In the Receiving Application:
    In the "To Bin" field, click the search Icon and confirm there
    are no records.
    
    Input any value for the Bin, such as "Test_3"
    
    
    Step 8:
    In the Receiving Application:
    
    Change the Inspection Status:
    
    In Material Receipts there is only record of Item 1004 with Type
    Receipt.
    
    Click change Inspection Status in More Actions.
    
    Check PO Line 1 and click OK.
    
    The PO Line of Item 1004 with Type TRANSFER has been added.
    
    For the Transaction Type of Transfer, A GL Account of
    6600-800-800 has been set, which is different to the one in the
    PR and PO at steps 2 and 3 above.
    
    (The GL Debit Account of 6600-800-800 is the GL Control Account
    as shown in the Storerooms application - this seems to be where
    that Account no. is coming from).
    
    
    
    CURRENT ERRONEOUS RESULT:
    The GL Debit Account field ( MATRECTRANS.GLDEBITACCT ) is
    different to the Account number that exists in both the GL Debit
    Account field in the PO ( POLINE.GLDEBITACCT ) and the GL Debit
    Account field in the PR ( PRLINE.GLDEBITACCT ).
    
    
    EXPECTED RESULT:
    The account number in MATRECTRANS.GLDEBITACCT is the SAME as
    POLINE.GLDEBITACCT and PRLINE.GLDEBITACCT.
    

Local fix

Problem summary

  • ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * In the Receiving application, when changing the inspection   *
    * status of an Item, the GL Debit Account field                *
    * (MATRECTRANS.GLDEBITACCT ) is different to the Account       *
    * number that exists in the GL Debit Account field in the      *
    * PO(POLINE.GLDEBITACCT )                                      *
    ****************************************************************
    

Problem conclusion

  • {color:#172b4d}The {color}{color:#172b4d}fix for this APAR will
    be{color}{color:#172b4d} {color}{color:#172b4d}contained
    in{color}{color:#172b4d} a future{color}{color:#172b4d}
    {color}{color:#172b4d}release{color}
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ40729

  • Reported component name

    MAXIMO ASST MGM

  • Reported component ID

    5724R46AM

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-06-19

  • Closed date

    2022-09-23

  • Last modified date

    2022-09-23

  • 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

    MAXIMO ASST MGM

  • Fixed component ID

    5724R46AM

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":"761","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
23 September 2022