PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 04/25/2017 2:31 PM by  Lynne
Primary Table for S_PFQU
 5 Replies
Sort:
You are not authorized to post a reply.
Author Messages
Lynne
Application Specialist
Covenant HealthCare
Veteran Member
(283 points)
Veteran Member
Posts:115


Send Message:

--
04/24/2017 11:21 AM
    I've read a past blog where Kelly explains the relationship between tag tables and the primary table.  We are implementing v10 and I am working on the conversion of req approval to IPA.  With it being on landmark now, I can make the actions of 'reject' and 'unrelease' pop up a box for entry of a required 'Action Reason'.  My problem is that I cannot figure out how to retrieve the reason after it has been taken.  I found tag table S_PFQU where the reason they entered resides.  I thought maybe it's primary table was one of the PFIQU... series of tables, but there is no link to connect them.  The only key looking field in S_PFQU is PROCESSFLOWQUEUE, and I cannot figure out what it links to.  I'm hoping someone can help me.  Thanks!
    Woozy
    Private
    Private
    Veteran Member
    (3487 points)
    Veteran Member
    Posts:707


    Send Message:

    --
    04/24/2017 12:01 PM
    Hi Lynn - Interestingly, I don't find table S_PFQU on my systems (LMRK 10.1.1.19 or LMRK 10.1.1.48). However, if we had an "S_PFQU" table, it would be associated with table PROCESSFLOWQUEUE which has a prefix of PFQU on S_PFQU.PROCESSFLOWQUEUE = PROCESSFLOWQUEUE.PROCESSFLOWQUEUE. The ProcessFlowQueue table includes a WorkUnitID field which I suppose would link to PFIWORKUNIT.

    That said, I'd be curious to know if your reqs generate records in the ActionRequest table. If so, then the reason code is likely associated with that Action instead of (or in addition to) the ProcessFlowQueue record. Note that a single ActionRequest may have multiple WorkUnits (if the ActionRequest was returned one or more times), but there would only be one ActionRequest. If they do generate ActionRequest records, then you would need to use a Landmark query to get the action reason...which is another adventure. I can help with that if you find this is the case.

    Kelly
    Kelly Meade
    J. R. Simplot Company
    Boise, ID
    Lynne
    Application Specialist
    Covenant HealthCare
    Veteran Member
    (283 points)
    Veteran Member
    Posts:115


    Send Message:

    --
    04/24/2017 12:45 PM
    Thanks, Kelly. I was hoping you would respond and you have helped me. I mistyped the tag table. It is actually S$PFQU. Yes, it does link up to PROCESSFLOWQUEUE, so thank you for that. Unbelievably, though, the workunit in PROCESSFLOWQUEUE does not get populated when I do any of the actions that I have turned the action reason pop up box on for. That seems like a bug as it populates on an 'Approve' action. Anyway, it appears that I will be able to go from PFIQUETASK (UNIQUEID) to PROCESSFLOWQUEUE (QTBUSINESSOBJECTKEY). Then, I should be able to get to S$PFQU. This seems like it should be a little more straight forward. And no, the reqs do not generate records in the ActionRequest table. That does seem how it should be (and would make it a lot easier).
    Woozy
    Private
    Private
    Veteran Member
    (3487 points)
    Veteran Member
    Posts:707


    Send Message:

    --
    04/24/2017 1:38 PM
    Just to be sure - are you querying the correct Landmark schema/database? Can you see the workunits in PFIWORKUNIT? If not, then that would tell me that you're querying the wrong schema. Are your reqs on LSF or LANDMARK? I'm assuming LSF...

    From your comments I can't tell if you are just migrating to IPA now, or if you've been using IPA prior to moving to v10. If IPA is new to you, it's important to note that in Landmark handles flow-related data differently than LSF. In Landmark, the IPA-related data is not in GEN or LOGAN but in the appropriate application prodline. If you are triggering from LSF, you should have a Landmark productline/schema that matches your LSF productline. That's where the IPA-related data would be.

    Since we don't use Reqs, I don't have much information about how these work, so I may be sticking my foot in my mouth.
    Kelly Meade
    J. R. Simplot Company
    Boise, ID
    Lynne
    Application Specialist
    Covenant HealthCare
    Veteran Member
    (283 points)
    Veteran Member
    Posts:115


    Send Message:

    --
    04/24/2017 2:41 PM
    Yes, I am querying the landmark database. I see all the data. It's just that on the ones I set to require an action reason are not populating the WU in the PROCESSFLOWQUEUE table. The other data is there.
    Lynne
    Application Specialist
    Covenant HealthCare
    Veteran Member
    (283 points)
    Veteran Member
    Posts:115


    Send Message:

    --
    04/25/2017 2:31 PM
    Just wanted to let you know, Kelly, that I got this working. I also learned that in the landmark query, it incorporates the tag tables in with the primary table. This made ActionComment from S$PFQU available when I queried PROCESSFLOWQUEUE- no need to link it up myself. I did have to start w/ PFIQUETASK since the WU is not loaded to PROCESSFLOWQUEUE for any actions (I previously thought it was just the ones that I added the pop up box to). It all worked so I am happy. Thanks for your help.
    You are not authorized to post a reply.