WESOUT Badi ‘WES_SE_MERCHANDISE_OUTBOUND’ does not support individual error handling, what next?

1 week ago 7

Hi everyone,

I’m encountering an contented with WESOUT and request immoderate assistance. Here’s the situation:

  1. Custom Field Mapping: We usage the Badi ‘WES_SE_MERCHANDISE_OUTBOUND’ to representation customized fields.
  2. Error Logging Requirement: I request to log an mistake if a worldly lacks a definite value.

The Problem:

  • When processing a tiny fig of materials, WESOUT calls the Badi for each worldly individually.
  • However, erstwhile processing a ample fig of materials, WESOUT calls the Badi erstwhile for each materials.
  • This causes a logic issue: if I rise an mistake for 1 incorrect material, it results successful an mistake for each materials.

Objective:

  • I privation to support some the customized tract mapping and mistake logging successful the aforesaid place.
  • Duplicating the customized codification successful aggregate places is not ideal.

Challenge:

  • There is an entity for logging conscionable extracurricular the Badi call, but it is not disposable wrong the Badi.

Request:

  • Does anyone person immoderate suggestions connected however to support the customized mapping logic and adhd idiosyncratic mistake logging wrong the Badi?

Any ideas oregon insights would beryllium greatly appreciated!

Thanks successful advance!

utsavar_0-1729240018916.png

Read Entire Article