Fallout occurs in SOM FY24Q4 release

[Satoshi Abe]

SOM (sales and order management) latest version (FY24Q4) adds many useful features.

We are testing this feature right away with SOMT(sales and order management for telecom), but we were experiencing a Product Order fallout in Bundle Product Offering.

-Fallout message
"The following order characteristics do not contain proper values"

I checked the characteristic of the order line item and found that a new characteristic had been added with a specification of (empty).

This specification of (empty) reflects the value of the customer input. On the other hand, the original specification also exists and its value is empty.

I think this specification (empty) is related to the fallout. If anyone has a similar situation and solved it, please let me know how to solve it.

Is there some plugin update missing?

We are using only the OOB functionality without any customization.

[ShashankInamdar]

Hi @Satoshi Abe ,

Are you using demo data that came with the PDI or have built your own?

If using the demo data, can you tell me the Bundled Offering you are using?

And if not, can you add some screenshots to get a view of your problem statement.

[Satoshi Abe]

Hi @ShashankInamdar 

We are actually creating our own offer, but this issue occurs when ordering even the demo data “Managed Connectivity Services Supreme Bundle” bundle product offer.
First of all, regardless of this issue, if a decomposed is done after the order approval, the default subflow will cause a Fallout (this was happening even before the FY24Q4 release). Therefore, after I set the Fallout to "closed complete" manually,  I set the order tasks to "closed complete" one by one.
Finally, when the product order of the bundled offer is closed, the Fallout as shown in the attached figure will occur again. (img1)
Also, when we checked the characteristics of order line item in the Fallout message, I found that a characteristics of (empty) was created. (img2)

[ShashankInamdar]

Hi @Satoshi Abe 

A couple of things in my observation when I compared this with my instance for the same OOTB Bundle.

[1] About the chars that are without a Spec - they appear to be duplicate and could be instance specific.

I do not see these in my instance for the same Bundle/PS combination -

[2] There is a Subflow 'Managed Connectivity Services fulfillment' getting called as soon the order is decomposed against the topmost bundled offer.

This subflow seems to be trying to close the children Product Orders without waiting for the underlying domain orders to close. 

This is triggering automated fallouts. 

For this, you can change the logic in this subflow.

But for [1], this appears to be instance specific issue and may need to be looked into.

[Satoshi Abe]

@ShashankInamdar 

Thanks for the quick confirm.
If this does not occur in your instance, it could be an instance issue. The plugins that need to be updated are the following as listed in NowLearning?

Guided Decisions Experience

Product Management Catalog Core

Price Management

Order Management

Order Management for Telecom, Media and Tech

Lead to Cash Core 

Opportunity Management Application
Opportunity Management Data Model
Quote Management Application　
Quote Management Data Model

Product Configurator　
Customer Life Cycle Management Workflows　
Product and pricing rules　
Customer Contracts and Entitlements　
Contracts and Entitlement Workflows　

Entitlements Verification　

Also, I am aware of [1], the Characterictic of Product Order is the same. On the other hand, Spec:(empty) is occurring in the Characterictic of "Order Line Item".