Error messages for external operation GRs registration for many rows not efficient

Our Customer needs to register Beas external operation GRs for many PO rows (about 2 hundred) in one time, but if any error occurs (e.g. for no components in stock, etc.) it is very difficult for the user to detect them. User must search in the protocol. It will be better to have a beas standard report linked to the registration form that summarizes the errors.