Maximo

Maximo

Come for answers, stay for best practices. All we're missing is you.

 View Only

  • 1.  PR to PO

    Posted Thu March 18, 2021 05:05 PM

    Hi All,

    I had created a new field "notes" at the PR header Level. I had also created the same field "notes" in the PO header Level.

    once the PR is approved, user can create a PO from the approved PR.

    My request here is that how can I set the value of the new field at the PO header Level to get the same value from the new field "notes" at the PR header level once the PO is created from PR.

    your support is appreciated



    ------------------------------
    Darwish Darwish
    ------------------------------

    #Maximo
    #AssetandFacilitiesManagement


  • 2.  RE: PR to PO

    Posted Fri March 19, 2021 02:07 AM
    Short answer - Crossover domain. There are plenty of good references, so I will share a few. Keep those fields in synch if you did not relate them via sameas function. 

    Anyway, here you go:

    Instructions: https://www.ibm.com/support/pages/setting-crossover-functionality-maximo
    Help: https://www.ibm.com/support/knowledgecenter/SSWT9A_7.6.1/com.ibm.mbs.doc/domainadm/t_add_crossover_domain.html

    Bruno's page on 'All about domains' is a handy reference as well at https://bportaluri.com/2012/06/maximo-domain-lookup-lists.html

    Good luck.

    ------------------------------
    christopher winston
    ------------------------------

    Original Message


  • 3.  RE: PR to PO

    Posted Fri March 19, 2021 08:29 AM
    There's an issue doing PR to PO because the link is actually one to many. What I mean by that is the mapping from PO->PR is at the line level and a PO supports having lines from multiple PRs.

    You have to tie your event to the POLINE.PRNUM attribute and then get the PO header. It's been a while since I did this (I don't like things that are random) but I'm assuming I did it via automation script on the attribute, got the PR information by opening a new set to PR, and then got the PO header by doing mbo.getOwner(). I'm not sure though, as the owner of the POLINE might be the PRLINE object instead of the PO. I'll have to see if I can track down where I did this.

    ------------------------------
    Steven Shull
    Director of Development
    Projetech Inc
    Cincinnati OH
    ------------------------------

    Original Message


  • 4.  RE: PR to PO

    Posted Fri March 19, 2021 09:11 AM
      |   view attached
    Or, digging WAAAAAY back into the deep secrets of Maximo v. 4.1.1, they knew a long time ago that crossover domains within the standard Maximo framework were going to be a challenge in that situation, so they hardcoded some spare fields to make such a crossover.

    I'm uploading a copy of the 4.1.1 System Administrator's Guide (from MRO Software!).  Have a look at Appendix A.

    ------------------------------
    Travis Herron
    ------------------------------

    Attachment(s)

    pdf
    411MAXSAG.pdf   6.88 MB 1 version
    Original Message


  • 5.  RE: PR to PO

    Posted Fri March 19, 2021 09:41 AM
    Chris is correct that technically you can use a crossover domain to carry data from one object to another and it would be easiest.  But as Steven points out that is a real problem with the PR to PO artifact for the simple reason you can very easily have many PRs related to many POs ,and it is many to many not one to many, since any given PR can have any given number of items requested form n number of vendors, and this is the root of the issue with doing a crossover form PR header to PO header. In this case if there is some significant note on the item that is needed to be known on the PO then do it at the line level and not the header.

    If you create a PR to PR crossover you create a system level limitation in your ability to reduce transaction cost friction.  You will end up not using the feature or the feature will drive up costs to procurement. instead of 10 PRs with many items all getting routed to 10 POs to the 10 vendors, you will have 100 PRs for those same vendors ending up on 100 PO to those same 10 vendors.

    Just because you can do it, does not mean you should do it.

    ------------------------------
    Bradley K. Downing , MBA
    IBM Certified Adv. Deployment Prof. Maximo v7.6.1
    IBM
    Bakersfield CA
    ------------------------------

    Original Message


Related Content