The current functionality ‘Transfer all postings errors to a new journal’ misleads users who lack familiarity with the 'Selection by' configuration.

Design proposal:

1) If we set “Transfer all postings errors to a new journal” parameter to value “FALSE”, the posting of the journal will always fail completely, regardless of the value set on “Selection by”. – We are in agreement with the existing design & No change required.

2) When we set “Transfer all postings errors to a new journal” parameter to value “TRUE”, then we can still prevent a given journal to be posted if any of the lines are failing (by setting Selection by = Entry) – In this case, users are misled as they lack familiarity with the 'Selection by' configuration.

So, we request whether the design change can be discussed with product team to disable the function “Transfer all postings errors to a new journal” parameter. (GREYED OUT) as the System is not creating a new journal line for the items failing due to an error and journal fails to be posted.

3) When we set “Transfer all postings errors to a new journal” parameter to value “TRUE or FALSE”, we can allow complete journal lines to go ahead (by setting Selection by = Posting).

We are in agreement with the existing design & No change required.

Feeback received by Microsoft support team below:

Unfortunately, changing the current design (and behavior) cannot be achieved through a flow of actions that involve a support case. This is because, from support side, we cannot ask Product Group directly to implement a change in the design.