Problem creating warehouse shipment lines

MbarlowMbarlow Member Posts: 10
User releases a transfer order and chooses Functions, Create Warehouse Shipment. The shipment is created but with no shipment lines. No error message appears. This happens in our testing environment but only for certain users. It does not appear to be related to the code unit, to the transfer from/to locations, or to the item used.

Users who experience this problem also have a problem creating a warehouse receipt for a purchase order - no receipt lines created, no error message. Any one have any suggestions as to the possible cause of this problem?

thanks

Comments

  • ara3nara3n Member Posts: 9,258
    are they assigned to that location as warehouse employee?
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n
  • MbarlowMbarlow Member Posts: 10
    hi

    yes they are a warehouse employee for that location.
    Mike
  • MbarlowMbarlow Member Posts: 10
    We're getting this problem, (whereby when some users create a warehouse receipt the lines are not created), in our testing environment which is running on SQL 2005, but not on our live environment which is running on older version. The live environment is however due to be upgraded to SQL 2005 in the near future. Does anyone know of any bugs when running Navision on SQL 2005 related to warehouse receipt/shipment lines? Or any hotfixes that may be availabe?
  • ara3nara3n Member Posts: 9,258
    No I have heard of any.
    Have you done any modification in that area?
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n
  • MbarlowMbarlow Member Posts: 10
    We have not done any modification of create warehouse receipt or create warehouse shipment.
  • ArhontisArhontis Member Posts: 667
    Hi Mike,

    I took a look in the code and saw that while choosing the create shipment the code passes through the report "Get Source Documents" which is responsible on locating the appropriate documents and creating the header and lines.

    I suggest you debug a little that report to see where it passes from to create the header and not the lines. You could place a breakpoint in the CreateShptHeader function and follow from there (it is not very far)...

    I guess it is either a permission problem (but I haven't seen any WRITEPERMISSION check in the code) or a user problem, meaning that the users in the productive database might not have followed your instructions correctly and that is why they get that result.

    Anyway, tell us how it went...
  • MbarlowMbarlow Member Posts: 10
    Thanks for the advice. We found by increasing permissions for the roles used by these users that the problem was resolved.
  • jgentlejgentle Member Posts: 6
    I've seen this same behavior. I ran the whole process through the debugger both on the Whse. Shipment and Whse. Receipt side using multiple sessions to the database to see that the line records do in fact get created/inserted. What I mean by multiple sessions is that I validated my visibility of the new record(s) through another terminal server session as I stepped through the code in the other session.

    I agree that the issue seems to be related to permissions, but am curious as to the specific changes you made that caused the problem to disappear. I added users experiencing the problem to SUPER, resynched security, and didn't get a change in the behavior. I'm a super user in this database and can make a Warehouse Shipment with the appropriate lines all day long.

    Frustrating!
  • ara3nara3n Member Posts: 9,258
    What security model are you using for sql 2005?

    I always recommend the standard security.
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n
  • jgentlejgentle Member Posts: 6
    The client is running Windows Authentication. As I understand it, it is a recommended best practice not to run mixed or SQL Authentication.
  • ara3nara3n Member Posts: 9,258
    jgentle wrote:
    The client is running Windows Authentication. As I understand it, it is a recommended best practice not to run mixed or SQL Authentication.

    No. I recommend to run in mixed mode. What happens when your Domain controller fails? How will consultants connect to the db?


    Going back to what I suggested, which is different than your comment above.

    Navision added Two security model in 4.0 sp3. To change this.
    File->database->alter-> advanced tab. You'll find an option for security model.
    you need to set it standard Model.
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n
  • davmac1davmac1 Member Posts: 1,283
    There is a bug in the SQL version where the warehouse request is showing "Whse. Completely Handled" = yes when it should be no.

    This is caused by a SQL bug in flowfields that seems to affect mainly the exists calculation.
    You can edit "Whse. Completely Handled" to = NO in th table to fix this.

    Version 5 update 1 is meant to fix this - but it requires reinstalling nassql as well if you are running it and it also introduces index hinting (like version 4 SP3 update 6).
  • jgentlejgentle Member Posts: 6
    Good information davmac1!

    I am regularly amazed by the sheer volume of bugs we consultants get to explain to our clients. Your explanation about the incorrect flowfield calculation makes sense, but the problem still seems to somehow relate to NAV/SQL security synchronization since it doesn't come up for some users.

    My client is on 4.0 SP1, so it sounds like the first course of action would be for us to get them up to 4.0 SP3 update 6.

    Thanks again for the information!
  • idiotidiot Member Posts: 651
    My client is facing this intermittent problem with 4.02 SQL 2005.
    Is this a bug then? What fix are there?
    NAV - Norton Anti Virus

    ERP Consultant (not just Navision) & Navision challenger
Sign In or Register to comment.