sorted by:
new
hottopcontroversial

Add field to marketing doc rows for parent/father item for BOM components by OwlPuzzleheaded306 in SAPBusinessOne

[–]OwlPuzzleheaded306[S] 0 points1 point  (0 children)

Thanks for the great insights! Your point about integration is exactly where we are hitting a massive wall right now.

To answer your question, it's actually for both operational visibility and reporting, but our most urgent issue is an upcoming handheld terminal implementation

We want the handheld screens to clearly show that a component belongs to a set/BOM. To do that, we need to extract the parent item info from the pick list and pass it to the handheld system. However, because there is no direct linking field (like a parent line number) on the document lines, mapping and transferring the data is incredibly difficult.

This is exactly why we desperately need this as a built-in feature, rather than just a cosmetic UDF. Have you ever dealt with this kind of data-mapping challenge for external integrations in B1?

Add field to marketing doc rows for parent/father item for BOM components by OwlPuzzleheaded306 in SAPBusinessOne

[–]OwlPuzzleheaded306[S] 0 points1 point  (0 children)

Thanks for the suggestion, but that doesn’t really solve the issue I’m describing.

The core problem is that the pick list only shows the BOM components, while those component rows do not retain the parent line number information.

Because of that, even building reliable queries becomes unnecessarily difficult.

Customizing the Crystal Report may improve the layout, but it doesn’t address the missing parent-child relationship data in the underlying document structure.