【正文】 so that a supply plan can be determined.ScenariosDepending on whether the manufacturing environment is BuildtoStock (BTS), BuildtoOrder (BTO) or ConfiguretoOrder (CTO), the forecast extraction for supply planning is done at different levels in the product hierarchy. At this point, we must recall that therere are two dimensions to a forecast in a given bucket—seller and product. We just mentioned that the level in the product hierarchy at which the forecast has to be extracted will vary depending on product type. Potentially, the seller hierarchy level at which forecast is extracted can also vary depending on product type though we do not demonstrate this in the template data set. For more details, please see the scenarios below.1. BTS productsIn a BTS environment, the forecast is extracted for the supply planning process typically at a model level (in the product hierarchy). Also, depending on the level in the seller hierarchy at which the forecast is to be planned, the forecast is extracted and ting is performed at the appropriate level in the seller hierarchy. Please note that since allocation planning for BTS is done entirely in the allocation planning engine, so there is no additional information that will be generated by extracting the forecast for BTS at customerdc level. All we need to know is the aggregated forecast for a BTS product in the regions which are served from one supply point. 2. BTO productsIn a BTO environment, forecast is typically extracted at the Product Family or at the model level (for assembly coordination). The Supply planning process uses a bill of material to determine the ponent requirements based on these forecasts to generate a Supply Plan. Depending on the level in the Seller hierarchy at which this supply is to be planned, forecast is extracted at the appropriate level in the seller hierarchy.3. CTO productsIn a CTO environment, the forecast can be extracted in two ways. They are? Component level: Forecast is extracted at the ponent level using the attach rates and by breaking down the model level ted forecast into ponent forecasts. ? Model level: The adjusted forecast is extracted at a model level and is sent to supply planning along with the attach rates.In the SCM template , we follow the latter approach because it helps us to do assembly coordination. What follows is a brief explanation of how assembly coordination is aided by 19 / 36extracting the forecast at model level in the product hierarchy as opposed to extracting it at ponent level:Consider two models M1 and M2. Suppose M1 is assembled from two ponents—C1 and C, and M2 is assembled from C2 and C. Suppose we have forecasts for both M1 and M2 but we are extracting forecast at ponent level. Further suppose that there is no supply for C1 or that the supply for C1 is at least less than that required to fulfill the forecast pletely. In such a scenario, since forecasts have been extracted at ponent level for C1, C2 and C (and since these are independent forecasts), C2 and C would be planned for to the full quantities even though forecast for C1 cannot be planned for pletely. This obviously is something undesired. We would wish to reduce the amount of C manufactured/procured if there isn’t any supply for C1. This problem would not be faced if forecast is extracted at model level and not at ponent level. And that is what is done in SCM template Forecast Extraction for Allocation PlanningMany a time in allocation planning, we would like to allocate product supply to sellers based on the forecasts made by sellers. For instance, it might be desired that the supply from supply planning is allocated to various sellers in the ratio of forecasted quantities (please see the section on Allocation Planning for more details). So it is necessary to have the forecast made available to the Allocation Planning function as well. The level at which forecast has to be extracted for allocation planning purposes can be diff。 TRADEMATRIX and design。 i2 TECHNOLOGIES and design。 and RESULTS DRIVEN METHODOLOGY. The following registered trademarks are the property of i2 Technologies, Inc.: GLOBAL SUPPLY CHAIN MANAGEMENT。 ORB NETWORK。SECTION 1SCM TEMPLATE WORKFLOW3 / 36SCM Template WorkflowRelease Copyright 2022 i2 Technologies, Inc.This notice is intended as a precaution against inadvertent publication and does not imply any waiver of confidentiality. Information in this document is subject to change without notice. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or information storage or retrieval systems, for any purpose without the express written permission of i2 Technologies, Inc.The software and/or database described in this document are furnished under a license agreement or nondisclosure agreement. It is against the law to copy the software on any medium except as specifically allowed in the license or nondisclosure agreement. If software or documentation is tobe used by the federal government, the following statement is applicable: In accordance with FAR Commercial Computer Software — Restricted Rights, the following applies: This software is Unpublished—rights reserved under the copyright laws of the United States.The text and drawings set forth in this document are the exclusive property of i2 Technologies, Inc. Unless otherwise noted, all names of panies, products, street addresses, and persons contained in the scenarios are designed solely to document the use of i2 Technologies, Inc. products.The brand names and product names used in this manual are the trademarks, registered trademarks, service marks or trade names of their respective owners. i2 Technologies, Inc. is not associatedwith any product or vendor mentioned in this publication unless otherwis