@Sivasankar Based on my suggested approach earlier, we can use TIMESUM to identify missing range from the fourth module (which is by supplier, maetrial, range, and time) . You said that missing price range would be placed in the same timescale as the previous range. As in your earlier attachment, there is quantity of 26,000 (Range 3) in Week 34 FY20, and of 37,000 (Range 5) in Week 35 FY20. My question is which week the missing price range 4 should belong to. Based on your explanation, I understand that it should be in Week 34 FY20 i.e. same timescale as previous range. However, we cannot put it in Week 34 unless we have another list as part of the module. As you said there are 16 price ranges, this is the number of list items that will be in the range list. They can be re-used for each supplier and material combination even though the range value themselves are different for each combination (price module uses supplier and material list). However, if adding a price range list will blow the size of the module (I am not sure how big your supplier and material lists are), another option is to use a running number list item instead of actual range to reduce number of items in that list. The fourth module will be similar to this. I have not really tried it but think that it can be achieved despite of now requiring a more complex transformation. The number of items in that list can be probably reduced depending on how many missing price ranges can really happen between two adjacent weeks If there is still problem with the module size, we can probably: - Make a final module as a one list (numbered list) module with line items only (no timescale) - With base contract module as source, use action to create the numbered list (supplier, material, and range as code) and load final module - Create another action to insert the missing ranges. I do not have an exact idea though. Regards, Andre
... View more
