New Line Splitting methods - Can we have some examples and further documentation please?

hI @Dmitrii Naumov -

Sure. I will just run you through what I’m working on right now, and hopefully that will illustrate where some of the questions are coming up.

We are in the metals industry, which means for every receipt of material, we need to track certain things on a per lot basis. One of these would be a Lot Number (already built into Acumatica). But there is also something called a Heat Number (which is related to Lot Number but generally distinct from it). And then we usually have a document called a Test Report which gives specific details about that lot of material, and which needs to be tracked with each lot of material we receive.

So, when we receive material, we need to record this information against each lot received. It also needs to be tracked in INTran, so that it is logged against the actual receipt of material. Likewise, this needs to be selectable in SOLineSplit, so that if a salesperson wants to sell a specific lot of that material, they can see what is available and review the test report document attached to each lot of material.I have already extended POReceiptLineSplit, and added the two fields I want. Code is below. This part works!

Extension of POReceiptLineSplit:

	public class POReceiptLineSplitExt : PXCacheExtension<POReceiptLineSplit>
	{
		#region Heat Number
		public abstract class heatNumber : PX.Data.BQL.BqlString.Field<heatNumber> { }
		[PXDBString(255)]
		[PXUIField(DisplayName = "Heat Nbr")]
		public virtual string HeatNumber
		{
			get;
			set;
		}
		#endregion
		#region Test Report Document
		public abstract class testReport : PX.Data.BQL.BqlString.Field<testReport> { }
		[PXDBString(255)]
		[PXUIField(DisplayName = "Test Report")]
		public virtual string TestReport
		{
			get;
			set;
		}
		#endregion
	}

Now, when we receive material, we can fill out these fields and they will be stored along with the Lot/Serial in the database (confirmed by looking in the database). Great!

But...how do we extend the graph logic for these fields? Or have these fields flow to the INTran and SOLineSplit DACs when we allocate this material downstream of the Purchase Receipt process?

Let’s say we want these fields to flow through to INTran (material receipt process), and SOLineSplit (allocate inventory to specific sales order), and then SOShipLineSplit. Just for example purposes, let’s say we also want to manipulate some of the data inbetween pulling it into the SOLineSplit line.

The only documentation I’ve seen at all about extending the graph for the new LineSplitting extensions is a small reference on Yuriy Zaletskyy’s blog. He posted this screenshot:

https://blog.zaletskyy.com/image.axd?picture=/LSSelect/21R2Override.png

Here is the full blog post: https://blog.zaletskyy.com/post/2022/04/08/lsselect-view-in-acumatica

So put yourselves in the shoes of a programmer who has to create an extension of the Line Splitting logic, and how it will flow from Purchase Receipt, to Inventory Receipt, to Sales Order and to Shipment. The data is linked up through all these processes, so how do we step into the middle of the line splitting logic when, for example, there is a field updating event on the SOLineSplit field in the Sales Order inventory allocation screen?

I have tried implementing this the way Yuriyy laid out in the screenshot on his blog, and it doesn't throw any errors, but at least for now I can’t hit breakpoints in that code. Below is a stub implementation of the approach on Yuriyy’s blog for the SalesOrderLineSplittingExtension. Can we get some examples of what can be down here, and whether this is in fact the correct approach to extending the graph of these SOLineSplits?

	public class SOOrderEntry : PXGraph<SOOrderEntry, SOOrder>
	{
		public SOSalesOrderLineSplittingExtension SOOrderLineSplitExt =>
			  FindImplementation<SOSalesOrderLineSplittingExtension>();

		public SOSalesOrderLineSplittingAllocatedExtension SOOrderLineAllocExt =>
              FindImplementation<SOSalesOrderLineSplittingAllocatedExtension>();
	}
	public class SOSalesOrderLineSplittingExtension : PX.Objects.SO.GraphExtensions.SOOrderEntryExt.SOOrderLineSplittingExtension
	{

       //WHAT DO WE DO HERE? CAN WE CHANGE THE BEHAVIOR OF WHAT HAPPENS WHEN WE CHOOSE 
       //INVENTORY FOR ALLOCATION IN A SALES ORDER? WHAT WOULD THAT LOOK LIKE?

       //HOW DO WE PROPERLY GRAB DATA FROM POReceiptLineSplit AND PULL IT INTO SOSalesOrderLineSplit?
	}

	public class SOSalesOrderLineSplittingAllocatedExtension : PX.Objects.SO.GraphExtensions.SOOrderEntryExt.SOOrderLineSplittingExtension
	{
       //WHAT DO WE DO HERE? CAN WE CHANGE THE BEHAVIOR OF WHAT HAPPENS WHEN WE CHOOSE 
       //INVENTORY FOR ALLOCATION IN A SALES ORDER? WHAT WOULD THAT LOOK LIKE?
	}