关于Sanjeev

谢谢@DavidSmith . The document is quite comprehensive and detailed. I have figured out my own way to create a Hierarchy BOM. And it involves no change in the file structure whatsoever. The only requirement is to have an Action process to run through the BOM creation in an interactive way. I could do a 9 level deep BOM with running the process about 70 odd times. And it took Anaplan less than 15 mins to do so. Once you have built the detailed BOM, you can create a single level BOM out of this hierarchy that shows all the components at the first level as a leaf. Makes it extremely simple. I will try and put it together in a document or maybe publish an app on the App Store. As it can save time and effort for the whole community. Pls bear with me till I do so 。。。View more

嗨 @dihya.atmani anaplan支持创建多级BOM。您可以采用两种方法1.在输入文件中获取层次结构，并使用它在Anaplan上构建一个嵌套的复合列表，显示父子关系。这些列表将被编号列表，因为您可以将单个组成部分作为父母和孩子，还有多个父母的孩子。优点 - 这种方法使BOM级别的信息非常容易，因为Anaplan为您做到了。一路可追溯性简单简单。缺点 - 更改BOM是一个挑战，因为您需要重新建立整个层次结构。然后，将旧的层次结构完好无损，可能很难做到。此外，我们发现SAP（在制造设置中大部分使用的ERP）不会抛出多层次的BOM。它只会给出一个级别的BOM，具有级别，ALT级别，父级，基本数量，基本uom，组件，comp base qty，comp base uom，数量等。2.Build在Anaplan中构建单个级别的BOM，并使用动作按钮滚动 -将成本从最低级别到最高职业选手 - 在这种方法中，更改很容易捕获。在整个模型中，在建模方面的努力最小的努力可以轻松地传播一个父子关系变化。 Cons - loose traceability from top level to bottom level. At any point, you only get that level Material Costs and Semi-Finsihed Goods cost. My recommendation is to take the 2nd approach as the problem statement gets compounded when you include Recipes as well. With multiple recipe versions and alternate versions, the challenge to manage is very difficult in a single nested BOM in Anaplan. 。。。View more