Where are IPA Inbasket messages stored in the database?

 3 Replies
 0 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
boardsh80
New Member
Posts: 2
New Member
    Hi all,

       As part of a workflow in PFI, we scrap messages written for inbasket items, put them in a file, and send them to our document imaging system.  In PFI this was accomplished by querying a combination of LOGAN.WFMSGHDR and LOGAN.WFMSGDTL  We are upgrading to IPA and these nodes did not convert properly.  We put in a few test messages on some inbasket items and looking in the IPA Landmark database, there is a table called PfiMessage that appears to have most of the information (message type, subject, date\time, user) but it does not contain the message itself.  I have looked everywhere in Landmark and Logan and cant seem to find them.  Does anybody know where they are now stored?

    Thanks!
    Tim Cochrane
    Veteran Member
    Posts: 154
    Veteran Member
      It's all in PfiMessage. i ran a flow with the following LM query, SELECT of attachby and workunit:

      _dataArea="secr" & _module="pfi" & _objectName="PfiMessage" & _actionName="Find" & _actionOperator="NONE" & _actionType="MultipleRecordQuery" & _pageSize="30" & _setName="SymbolicKey" & AttachBy="tbc1242" & PfiWorkunit="95" & PfiMessage & AttachByName & AttachDate & Message

      Results were:


      complete: true
      response message: null
      record count: 1
      has next: false
      has previous: false
      Results header string: PfiMessage,AttachByName,AttachDate,Message
      Results string: 1,Tim Cochrane,2013102912572580,i denied this action



      You can see message I added "i denied this action"

      I'm including the latest PFI-IPA file mapping i have, which is 14 months old. From what I understood from Lawson IPA developers were that, if a table is not in the mapping file, it doesn't exist in IPA, and Msg Dtl doesn't exist in IPA.

      FieldMapping,oFILE=WFMSGHDR,oFIELD=WORKUNIT,oFormName=MessageHeaderForm,oFormField=workUnit,nFILE=PfiWorkunit,nFIELD=PfiWorkunit
      FieldMapping,oFILE=WFMSGHDR,oFIELD=ATTACH-DATE,oFormName=MessageHeaderForm,oFormField=attachDate,nFILE=PfiMessage,nFIELD=AttachDate
      FieldMapping,oFILE=WFMSGHDR,oFIELD=ATTACH-BY,oFormName=MessageHeaderForm,oFormField=attachBy,nFILE=PfiMessage,nFIELD=AttachBy
      FieldMapping,oFILE=WFMSGHDR,oFIELD=SUBJECT,oFormName=MessageHeaderForm,oFormField=subject,nFILE=PfiMessage,nFIELD=Subject

      DBMapping,oFILE=WFMSGDTL,oFIELD=MESSAGE,nFILE=PfiMessage,nFIELD=Message
      DBMapping,oFILE=WFMSGDTL,oFIELD=WF_MESSAGE_ID,nFILE=PfiMessage,nFIELD=PfiMessage
      DBMapping,oFILE=WFMSGDTL,oFIELD=WORKUNIT,nFILE=PfiMessage,nFIELD=PfiWorkunit
      DBMapping,oFILE=WFMSGHDR,oFIELD=ATTACH_TIME,nFILE=PfiMessage,nFIELD=AttachDate
      DBMapping,oFILE=WFMSGHDR,oFIELD=WF_MESSAGE_ID,nFILE=PfiMessage,nFIELD=PfiMessage

      Tim Cochrane - Principal LM/IPA Consultant
      boardsh80
      New Member
      Posts: 2
      New Member
        Great, Thanks. And I did figure out what was up with the database. The actual messages in an Oracle instance get stored in a table called S$PFIME. So all the data is in the same business class but split into two tables it looks like.
        Tim Cochrane
        Veteran Member
        Posts: 154
        Veteran Member
          ah yes...we're DB2, hence the difference. Good that you got it figured out.
          Tim Cochrane - Principal LM/IPA Consultant