Batch Importsil fails with receipts

SOLVED

Hi Sage Community!

After struggling with this problem I decided to post it here just in case someone had or is having the same situation as we do.

We have a system that manages the receipts thought import templates and is working just fine in different Sage X3 installations, but we kind of found an strange behaviour recently that we are not able to solve.

When we launch the command IMPORTSIL with our RECEIPTS using the batch server it returns an error that says the "Wrong stock transaction detail"  but when we retry to import this file thought the import system that X3 has it doesn't return any error and works properly.

This only happens with the receipts, deliveries are working properly and is more or less the same file format.

Origin error:

After we reprocess the same file not using the batch (is the same being executed the only difference is the environtment):

Thanks in advance!

Regards.

Parents
  • +1
    verified answer

    Hi

    I think batch server runs a little bit different than usual in x3.
    maybe a User issue that you set up the batch task?, maybe no permissions for something regarding stock?

  • 0 in reply to Barak

    We tried with two different users, the same user that runs the import in batch is the same user executing the import through X3. The only difference that I can see is the user and role that runs the batch but I dont know if this settings can affect the way it works. Thanks for your answer.

    Edit:

    After one month with this issue we managed with the client to check the user, the server user had wrong profile and it was the origin of the problem. Thanks to Bark for the suggestion.

Reply
  • 0 in reply to Barak

    We tried with two different users, the same user that runs the import in batch is the same user executing the import through X3. The only difference that I can see is the user and role that runs the batch but I dont know if this settings can affect the way it works. Thanks for your answer.

    Edit:

    After one month with this issue we managed with the client to check the user, the server user had wrong profile and it was the origin of the problem. Thanks to Bark for the suggestion.

Children
No Data