Skip to main content
12-Amethyst
April 14, 2026
Question

ESI response file - BOM update

  • April 14, 2026
  • 1 reply
  • 12 views

We have a phantom item at the first level of the BOM that we do not want to publish as-is.

The structure is:

  • Parent → Phantom → Child parts

In Oracle, the expectation is:

  • Parent → Child parts (phantom should be flattened)

We are enabling one-level publishing only. Is it possible to generate the XML in such a way that the phantom is replaced with its child BOM (i.e., flatten the phantom during publishing)?

I’m considering two approaches:

  1. Manually manipulating the XML, though this may be complex and error-prone due to multiple scenarios.
  2. Sending the BOM for phantom instead of phantom before generating the XML.

Is there a better or recommended approach to achieve this?

1 reply

16-Pearl
April 16, 2026

Hi ​@Srivalli,

I am curious to understand why it is configured for one-level publishing.