IBM Support

IJ35916: POLINE.ENTERBY AND PRLINE.ENTERBY FIELD USES USERID INSTEAD OF PERSONID.

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

  • DESCRIPTION:
    
    Purchase Orders, POLINES and Purchase Requisition Application's
    PRLINES, ENTERBY Field contains the Userid by default. They
    should contain the PERSONID instead of Userid.
    
    
    STEPS TO REPRODUCE:
    1) Login with maxadmin or other privileged user; Go to Security
    Application-> Users
    (i) Open the record: WILSON
    (ii) From More Actions-> Select Duplicate User; Name the new
    user: WILSONCOPY
    (iii) A System Message appears as below:
    BMXAA3844W - Person WILSONCOPY does not exist. Do you want to
    create a new person?
    Click NO
    (iv) Go to Person Lookup field, Go to People Application and
    create a new PERSON;
    
    (v) Name the Person: WILSONPERS; Save the record and Return
    with Value;
    (vi) Set password for the user: WILSONCOPY; Save the record
    
    
    2) Logout and Login with the user: WILSONCOPY
    (i) Go to Purchasing-> Purchase Requisitions Application
    (ii) Create a new PR: TESTPR;
    
    (iii) Switch to PRLines Tab; Add a new PRLine by click New Row;
    Add item: 0-0031; Storeroom: CENTRAL; Conversion Factor: 1;
    
    (iv) In the Entered By field(PRLINE.ENTERBY), Observe the
    default value filled in at ENTERED BY Field is userid, here:
    WILSONCOPY and REQUESTED BY Field is Personid, here WILSONPERS;
    Save; PR gets saved without any error.
    
    Perform another test.
    
    (v) In the Entered by field, remove the already filled in
    Userid, here: WILSONCOPY. Attempt to save. It says ENTERED by
    field is mandatory.
    Re-enter the same Userid: WILSONCOPY; Save
    Observe, an error is thrown as below: You entered: wilsoncopy.
    The person does not exist or is not active (BMXAA3097).
    (vi) Now, enter the PersonId: WILSONPERS; Save. Observe the
    record gets saved without any error.
    
    
    RESULT:
    PRLINE.ENTERBY Field contains Userid by default, in this case:
    WILSONCOPY.
    
    
    EXPECTED RESULT:
    PRLINE.ENTERBY Field should contain PERSONID instead of USERID.
    In this case: WILSONPERS.
    
    
    REPORTED IN VERSION:
    Tivoli's process automation engine 7.6.1.2
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Maximo users                                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * POLINE and PRLINE ENTERBY is set to USERID when addedUserid  *
    * by default. They should be set to PERSONID as is defined by  *
    * SAMEAS relationship and field class FldPurEnterBy.           *
    ****************************************************************
    STEPS TO REPRODUCE:
    1) Login with maxadmin or other privileged user; Go to Security
    Application-> Users
    Open the record: WILSON
    (ii) From More Actions-> Select Duplicate User; Name the new
    user: WILSONCOPY
    (iii) A System Message appears as below:
    BMXAA3844W - Person WILSONCOPY does not exist. Do you want to
    create a new person?
    Click NO
    (iv) Go to Person Lookup field, Go to People Application and
    create a new PERSON;
    (v) Name the Person: WILSONPERS; Save the record and Return
    with Value;
    (vi) Set password for the user: WILSONCOPY; Save the record
    2) Logout and Login with the user: WILSONCOPY
    Go to Purchasing-> Purchase Requisitions Application
    (ii) Create a new PR: TESTPR;
    (iii) Switch to PRLines Tab; Add a new PRLine by click New Row;
    Add item: 0-0031; Storeroom: CENTRAL; Conversion Factor: 1;
    (iv) In the Entered By field(PRLINE.ENTERBY), Observe the
    default value filled in at ENTERED BY Field is userid, here:
    WILSONCOPY and REQUESTED BY Field is Personid, here WILSONPERS;
    Save; PR gets saved without any error.
    Perform another test.
    (v) In the Entered by field, remove the already filled in
    Userid, here: WILSONCOPY. Attempt to save. It says ENTERED by
    field is mandatory.
    Re-enter the same Userid: WILSONCOPY; Save
    Observe, an error is thrown as below: You entered: wilsoncopy.
    The person does not exist or is not active (BMXAA3097).
    (vi) Now, enter the PersonId: WILSONPERS; Save. Observe the
    record gets saved without any error.
    RESULT:
    PRLINE.ENTERBY Field contains Userid by default, in this case:
    WILSONCOPY.
    EXPECTED RESULT:
    PRLINE.ENTERBY Field should contain PERSONID instead of USERID.
    In this case: WILSONPERS.
    

Problem conclusion

  • The fix for this APAR is contained in the following maintenance
    package:  Release 7.6.1.3 of Base Services
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ35916

  • 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

    2021-11-02

  • Closed date

    2022-05-22

  • Last modified date

    2022-05-22

  • 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

    MAXIMO ASST MGM

  • Fixed component ID

    5724R46AM

Applicable component levels

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

Document Information

Modified date:
23 May 2022