Hi, we are in multi-site environemnt ( two sites - Site A and Site B). Site B have a configurator part (part: ABC) and it has a sub assembly to another configured part from Site A( part: XYZ).
when we raise quote/order in Site B for part ABC, the configurator shows configurator pages of ABC, but not the configurator pages of XYZ.
How does product configurator works in multi-site especially parent assembly in site A and sub-assembly is in site B, demand is in site A . the application help have more info for the multi-company but not for multi-site.
Do you have more info on this? Any knowledge articles or user guides? We are working to have parent parts on a job in site a that generate a job in site b for the subassembly. Both are parts on the fly using two separate configurators.
Typically all items that result from a configurator session will be built on the same job as for the sub (aka Cascading) configurator to work it has to be marked as pull as assembly. Which means the assembly will be manufactured as part of the parent job.
Half-baked idea, the cascading configurator could make a real part as part of its session. You would need to adjust the MOM somehow either manually or via some after configurator code (possibly in document rules) that changes the newly created part material input into a part pulled off the shelf. This would create demand for that part when a job is created. At this point as long as the part is setup properly MRP should pickup where it needs to be manufactured and a job created for the part to be supplied to the parent part.
I mention document rules as that is a great place to put things as document rules only run after successfully saving a configurator and also any parts that are created have been created. You can do anything you can do in a BPM in document rules.