Sales order output type in error

[chandan_ramesh]

Hi Experts,

I have two different order documents for which output type with medium special function is configured.

For user X, the output type status is "successfully processed"

But for user Y, the same output type is "processed with errors"

There is no processing log for this output type and hence i am wondering if this is related to authorization.

This is also happening for a specific partner function. Screenshot attached.

Thanks

[chandan_ramesh]

Apologies.

[VeselinaPeykova]

Most probably this ZRS3 output is associated with a custom program which performs certain actions.

Considering that these screenshots are from are different documents it makes sense to compare the data between the documents and check the logic in the program itself (you can try to debug it if you can reproduce the test case in the quality environment).

I noticed also that the document types are different - the first one seems to be standard return while the second is return of free of charge items. Maybe the program was not designed to work with free items?

General recommendation - check the code of the custom program, if possible - find the development specification or ask a developer to explain briefly the program logic.

It is not impossible that the problem is related to authorizations but it should be easy to rule this out - create a test case in QAS exactly as document 1, create a test user exactly as user 2 and process the output. If the output is processed correctly then this is not related to authorization problems.

Check also whether the output in document 2 was added manually, if yes - when and how it was processed (some custom programs might not work correctly with immediate output or the program might need certain parameters which are available at a later stage in processing).

[Lakshmipathi]

There would be "Determination Analysis" in the output screen if you go via change mode. This will explain what the issue is.

[TammyPowlas]

I do not see a screen shot attached.

If you feel it is authorization-related, please ask your Security admin to run a trace using transaction STAUTHTRACE to see if it is really authorization related