Click to add to Favorites Oracle Advanced Supply Chain Planning Release Notes for Release 12.2.4 (Doc ID 1911524.1) To BottomTo Bottom This document provides delta information from Oracle E-Business Suite Release 12.2.3 to Oracle E-Business Suite Release 12.2.4 for the following products: Oracle Advanced Supply Chain Planning The contents of this document are applicable to all customers who have installed or upgraded to Release 12.2.4 using the applicable instructions in My Oracle Support Knowledge Document 1617458.1, Oracle E-Business Suite Release 12.2.4 Readme or in My Oracle Support Knowledge Document 1644375.1, Applying the R12.SCP_PF.C.Delta.4 Release Update Pack, and the relevant additional resources in My Oracle Support Knowledge Document 1581299.1, Oracle E-Business Suite Release 12.2 Information Center. Note: This document - primarily, Section 4: Known Issues - may be updated after the initial release. Any changes are listed in the Change Log. If you print this document, periodically check to ensure you have the most recent version. In this Document Section 1: Summary of Whats New Section 2: Documentation Resources Section 3: New and Changed Features Section 4: Known Issues Change Log Section 1: Summary of Whats New The following features of Oracle Advanced Supply Chain Planning have been added or changed in Oracle E-Business Suite Release 12.2.4. Refer to Section 3 for a complete description of these new features and their components. Feature Name Description Support for Premium Resource Capacity Constraints Many companies have the need to distinguish between regular or baseline resource capacity that represents their normal operating tempo and overtime or premium capacity that can be added on if required. Typically, premium capacity is expensive and its use should be minimized and restricted only to cater to business needs such as improving on time demand satisfaction. In Release 12.2.4, Oracle Advanced Supply Chain Planning will support the notion of regular and premium capacity for a given production resource. Users can specify a premium capacity percentage at the Resource level. Premium Capacity is calculated by multiplying the regular capacity (in hours) by the premium capacity percentage value. For example if the regular capacity is 16 hours per day and the premium capacity percentage is 20%, the premium capacity is assumed to be 3.2 hours. This feature is only supported in constrained plans with the Constrained Mode set to Constrained without Detailed Scheduling. Advanced Supply Chain Planning will first use all of the available regular capacity when planning supplies to satisfy demands on time. Once the use of regular capacity has been maximized, ASCP will attempt to use premium capacity to satisfy demands on time. When the use of regular and premium capacity is still not sufficient to satisfy demands on time, demands will be satisfied late and in each successive planning time bucket after the demand due date, the use of regular capacity will be maximized before using premium capacity. ASCP will also first search for regular capacity availability across alternate sources, alternate routings and alternate resources before resorting to the use of premium capacity. Exception messages will be generated for those Resource / planning time bucket combinations in which premium capacity is used. Planners will be able to identify instances where the premium capacity has been used but total capacity (regular plus premium) is not exceeded and other instances where the total capacity is also exceeded. Information on regular and premium capacity availability and usage is exported to Advanced Planning Command Center as part of the Archive Plan process. Support for Warehouse Capacity Constraints Many companies have the need to constrain the supply chain plan by the amount of available warehouse capacity. This is especially true for companies dealing with high unit volume products manufactured in facilities that have minimal available storage space, thereby creating the need to ship products out to distribution centers immediately or soon after production completion. Many companies also have the need to separately account for available storage space by storage type – such as Frozen, Refrigerated and Dry goods storage spaces. In Release 12.2.4, Oracle Advanced Supply Chain Planning will account for Warehouse Capacity constraints in the planning process. Planners can instruct the planning process (through plan option setting) to consider these constraints at the Organization level or at Category-Organization level. The Category in this case refers to a storage category such as Frozen, Refrigerated or Dry storage. The Organization level warehouse capacity is a setting within the EBS Inventory Organization parameters form and the Organization-Category level capacity can be specified in the Storage Capacity form in the planning instance. This feature is available only in constrained plans with the Constrained Mode set to Constrained without Detailed Scheduling. Advanced Supply Chain Planning will apply the warehouse capacity constraint to the sum of {Projected Available Balance * item unit volume} across all items in an organization or organization-category (depending on the level at which the warehouse capacity is specified). In doing so, ASCP will often need to plan shipment of items from upstream locations (Plants) to downstream locations (Distribution Centers) ahead of when these shipments are required to satisfy the demands at the downstream locations. When performing this pull ahead of shipments to address the warehouse capacity constraints, ASCP will attempt to minimize the overall excess inventory in the supply chain. When required to choose between different items to pull ahead, ASCP will pick items that have the highest (unit volume / standard cost) ratio. This choice will maximize impact on reducing warehouse capacity consumption at the locations with the constraints and minimize the impact on increasing inventory cost in the supply chain. Planners will be able to view the details of warehouse capacity consumption at the Item, Category and Organization levels in the Material Plan user interface. The information will be presented both in terms of absolute value (the volume used) and the percentage value (the percentage of available warehouse capacity used). ASCP will also generate exception messages for instances where the warehouse capacity was violated. Information on warehouse capacity availability and consumption is exported to Advanced Planning Command Center as part of the Archive Plan process. Minimum Remaining Shelf Life (MRSL) Enhancements Release 12.2.4 provides the following enhancements for MRSL: MRSL Support for Multi Echelon Supply Chain Consideration of MRSL in Making Sourcing Decisions Consideration of Safety Stock in Conjunction with MRSL Ingredient Based MRSL These enhancements are available for the plan Constraints Mode of Constrained (Without Detailed Scheduling). MRSL Support for Multi Echelon Supply Chain - Before this enhancement, ASCP did not consider the expiration dates of on hand lots that are moved to an in-transit status. The in-transit supply was assumed to have full shelf life remaining starting from the due date of the supply at the destination organization. With Release 12.2.4, supplies expiry dates are determined based on the following rules: All supplies expiry dates in the source organization are based on the item/org shelf life specified in the source organization (Item/Lot Expiry Date in the source org). All supplies expiry dates in the destination organization are based on the item/org shelf life specified in the destination organization (Item/Lot Expiry Date in the destination org). Note that if there is no shelf life defined in the destination org, the planning engine considers infinite shelf life. All in-transit supplies expiry dates from the source organization to the destination organization are based on the item/org shelf life of the item in the destination organization. With respect to these rules, there is no collection or snapshot impact for this enhancement in Release 12.2.4. Consideration of MRSL in Making Sourcing Decisions - Before this enhancement, ASCPs decision rules engine that makes sourcing decisions to guide the supply / demand netting, was not cognizant of MRSL. With this enhancement, shelf life and MRSL requirements of demands are taken into account when making sourcing decisions leading to consistency between the sourcing and netting logic within ASCP. Consideration of Safety Stock in Conjunction with MRSL - Before this enhancement, ASCP did not plan safety stock for items that have MRSL specifications on demands. With this enhancement, ASCP plans for safety stock in conjunction with MRSL. In addition you can ensure that supplies used for fulfilling safety stock demand have enough remaining shelf life so they serve as a useful hedge against unanticipated real demand (which also have MRSL requirements). You can specify the Safety Stock MRSL at the Item-Org level in the Item Attributes Mass Maintenance (IMM) window. This is accomplished via a new field called Safety Stock MRSL. Ingredient Based MRSL - Before this enhancement, ASCP supported MRSL for the end item based on the user specified value for the item. With this enhancement, user can specify an ingredient in a formula (a component in a BOM) which its shelf life determines the expiry date of the product. This ingredient is called MRSL ingredient. Note: The MRSL ingredient is not necessarily in the final product formula. It could be an ingredient of any intermediate ingredient that feeds the final product. This is accomplished by using a new field in the Item Attributes Mass Maintenance window at the Item-Org level called MRSL Ingredient. You can enter data manually or upload an Excel spreadsheet to populate this field using the import capability of IMM. Enforcing Process Effective Dates The Process Effective Date Ranges enhancement introduced in Release 12.1.3.8 aligned the timing of the supplies to the Process Effective Dates in the optimization phase of the planning process. The goal of Release 12.2.4 enhancement is to repair any violation of the process effective date range constraints during the scheduling process as much as possible. Specifically ASCP enforces the Process Effective Start Dates with respect to all other planning constraints. This enhancement is available for both EDD and ECC plan in the plan modes Constrained (With Detailed Scheduling) and Constrained (Classic). A new exception called Process effective date range violated is generated when process effective date range constraints are not respected by the planning engine. ASCP enforces the Process Effective Date Range constraints in conjunction with other planning constraints. The order of respecting these constraints depends on the type of the plan: Order of Constraints in EDD Plan Firmed Dates Demand Due Dates (Adjusted Demand Due Date when the profile option MSO: Lead Time Control is set to Do Not Violate Minimum Processing Times) Precedence Constraints (Based on Pegging) Required Processing Times Effective Date Ranges Min Start Times (PTF, Current Date) Note: ASCP planning engine initially attempts to find a solution that respects PTF, Current Date, and Effective Date Ranges. If a feasible solution cannot be found then the planning engine may violate PTF, Current Date, or both in order to respect the Effective Date Ranges. Resource Constraints Note: ASCP planning engine initially attempts to find a solution that respects Resource Constraints and Effective Date Ranges. If a feasible solution cannot be found then the planning engine may violate Resource Constraints in order to respect the Effective Date Ranges. Order of Constraints in ECC Plan Firmed Dates Min Start Times (PTF, Current Date) Precedence Constraints (Based on Pegging) Required Processing Times Resource Constraints Effective Date Ranges Demand Due Dates Note: ASCP planning engine initially attempts to find a solution that respects Demand Due Dates and Effective Date Ranges. If a feasible solution cannot be found then the planning engine may violate Demand Due Dates in order to respect the Effective Date Ranges. Note: The order of constraints in EDD plan is also applied to upstream orders of all firm dates in ECC plan as well. Note: The MRSL and Hard Link constraints are considered before the Process Effective Date Range constraints. In other words, the Process Effective Date Ranges could be violated due to MRSL or Hard Link constraints
Posted on: Sat, 20 Sep 2014 19:32:46 +0000