Prev
Next
Forums Supply Chain Management Lawson S3 Supply Chain

MSCM Rq10's not seeing requester

 6 Replies
 0 Subscribed to this topic
 38 Subscribed to this forum
Sort:
Author
Messages
linda phillips
Advanced Member
Posts: 40
Advanced Member
9/2/2008 10:11 AM

    We have rq10 records set up and the requested set in portal MSCM  The rq's do not create because it can not find the requester. All the staff is set up the same and I have 3 that it will not allow a rq to be created. I went as far as deleating the old and creating the again with no success. Any help would be appreciated

    Ben Coonfield
    Veteran Member
    Posts: 146
    Veteran Member
    9/2/2008 10:26 AM
      What release is this? If this is LSF, what do the users have specified in their [PRODUCTLINE]-REQUESTER identity? If you run a par count report, do you see a line for the attempted upload for these 3 users? If so, what error message appears on this line?
      linda phillips
      Advanced Member
      Posts: 40
      Advanced Member
      9/2/2008 10:55 AM

        we are lsf9

         In the product line it reads test and in the prod line requester field it has the exact same information as the rq 04 record, we don't have a rd30 record like for Req SS. we are pretty vanilla here

        we are still on 8.03 apps and running version 9 .0.0.12.7 on the MSCM

         

        Ben Coonfield
        Veteran Member
        Posts: 146
        Veteran Member
        9/2/2008 11:12 AM
          I'm running the same release. Are you uploading via RAD or Par & Cycle count? For par counts, we usually refer to the par count report which is run via the web interface. Just select the time period where these three users had a failed upload, and the company number they were using. The details on this report usually have enough debugging information to identify a problem.

          If this is RAD, I assume there is probably a similar report.

          If that doesn't help, you will have to analyze the MSCM log file, but the information you want is more difficult to find and interpret in that log -- even more so in release 9.
          linda phillips
          Advanced Member
          Posts: 40
          Advanced Member
          9/2/2008 11:53 AM
            This is for par and cycle under reports . That is where we see the Rq10 di not create becasue it doesn't seem to see the requester as a requester. I made sure that the security for the Central staff is all the same and find it funny that some can create RQ10's and others can not. They all have ssop, and requester in portal along with ldap.
            So I can not figure out why I have a few that do not work.
            JonA
            Veteran Member
            Posts: 1163
            Veteran Member
            9/6/2008 1:30 PM

              In the report is the message "USER [userid] IS NOT A LAWSON USER"?  If so, have them log off the MSC App on the handheld and log back in.

              Jon Athey - Sr. Supply Chain Analyst - Materials Management - MyMichigan Health
              linda phillips
              Advanced Member
              Posts: 40
              Advanced Member
              9/8/2008 9:58 AM

                I think the problem might be a cab file. We had to add a patch to the system for MSCM and from what I can see we need to add a cab file to the handhelds, we will see if this clears up the problem.