TW201017576A - System and method to determine root cause constraints and resolution options to solve order promising exceptions - Google Patents

Abstract

A system and method is disclosed for determining root cause constraints and resolution options to solve order promising exceptions. The system includes a database storing order promise data associated with one or more enterprises. The system further includes a computer coupled with the database, the computer is configured to receive an order promise from the one or more enterprises, define one or more constraints, and create one or more strategy models comprising one or more strategy changes. The computer is further configured to execute the one or more strategy models to relax the one or more constraints using the one or more strategy changes and generate a report of the reasons for lateness and shortness of the order promise and store the generated report in the database.

Description

201017576 6. INSTRUCTIONS OF THE INVENTION: TECHNICAL FIELD OF THE INVENTION The present invention relates generally to order commitments and, more particularly, to systems and methods for determining root cause limitations and analytical choices to resolve order commitment exceptions. [Prior Art] - ' . The traditional order commitment solution mainly involves generating the best demand submission response given the specific requirements, products or business requirements. However, one of the shortcomings of traditional order-commitment solutions is that there is no mechanism for understanding the reasons for shortened or late orders when orders are shortened or delayed. When an immediate response is generated to submit a supply to a descendant's needs, the time between the analysis of the demand requirement and the response is not matched and the time taken to take the action (4) is smaller. 13 This problem becomes more complicated. This phenomenon of failure to provide a mechanism for understanding the reasons for shortening or late/delayed orders is not desirable. ^ [Summary of the Invention] The present invention discloses a method for displaying a system of commitments. The system includes a database, i store left j,. _ octopus and one or more enterprises associated with the order bearing: the data system _ step includes a computer coupled to the database, the computer group State: to receive this ^ Receive - order commitments from the one or more companies; define - or multiple restrictions; and generate multiple types of strategies including ~ ~ 201017576. The step-by-step configuration is to use the one or more policies to change the execution of the one or more policy models to relax the one or more restrictions, and to generate the late and shorter of the subscription commitments. The reason for the report I and the generated report is stored in the database. A method of providing an order commitment system is not disclosed. The method provides for receiving an order fulfillment from one or more businesses; defining one or more restrictions by the electric cat; and by 兮Φ and generating one or more policy changes by the computer - Or multiple policy models. The method further provides: by using the one or more flute-, Α. ti* Jfcl y, a strategy change to execute the one or more strategy models to relax the material - or redundant system; f The employee reports on the reason for the late and shorter reasons for the order commitment, and stores the report of the occurrence. A readable medium for implementing a software having an order fulfillment system is disclosed. The computer readable medium: receiving an order fulfillment from one or more businesses; defining - or multiple restrictions; and generating - or multiple policy changes - or multiple strategies (4). The computer readable medium further uses the one or more policies to change the execution of the one or more policy models to relax the one or more restrictions; and to generate the later and shorter reasons for the order commitment Report and store the resulting report. [Embodiment] The following detailed description will be referred to with reference to preferred and alternative embodiments. It will be appreciated by those skilled in the art <RTIgt;the</RTI> <RTIgt; </ RTI> <RTIgt; </ RTI> <RTIgt; </ RTI> <RTIgt; Therefore, the specific embodiments discussed herein are presented by way of example and not limitation of the invention. 1 illustrates an exemplary system 1 according to a more illustrative embodiment, system 100 includes an order commitment system 110, one or more businesses 120a-i 20n, one or more customers 130a_13〇n, a network 14 and/or Communication links ΐ42, 144a-144n and 146a-146n. Although a single order commitment system 110, one or more businesses u〇a_12〇n, and one or more customers 130a-13〇n' are shown and described, embodiments may encompass any number of order commitment systems, depending on particular needs. Any number of businesses 12〇al2〇n and/or any number of customers 13〇a_i3〇n. Additionally or alternatively, the order fulfillment system 110 can be integrated or separated from the hard copy and/or soft pack of any one or more of the one or more businesses 120a-120n. In one embodiment, the order fulfillment system 11() determines the root cause limit and the resolution choice to resolve the order commitment exception. Additionally or alternatively, the order fulfillment system 11 prioritizes one or more businesses 12〇a_12〇n and selects a policy level to analyze and resolve order fulfillment anomalies for one or a group of orders. That is, in an order that matches the supply/distribution available in the supply chain when it is not required to be specified or analyzed in the requirements. By way of example and not limitation, the order commitment system 11 can relax, for example, allocation, delay, and source restrictions for a deployed order, and the order commitment system 11 can relax the minimum number of different deployments and supply constraints. Thus, the method is designed for each deployment to relax certain restrictions that may be modified to obtain high priority requirements from one or more customers 130a l30n in order to negotiate such high priority requirements 6 201017576 Agree to submit a response. In another embodiment, one or more enterprises 120a-120n may analyze one or a set of orders using one or more hierarchical policies to simulate, for example, a possible answer to the graphical user interface 'assumed restrictions are relaxed in a hierarchical manner, The hard requirements are kept in place to clearly identify some of the root causes of the mismatch response in the model, and ultimately guide the user to use the action that should be selected to modify the mismatch response using the relaxed limit. In one embodiment, the system can operate on one or more computers that can be hardened with a support order commitment system 11 , one or more businesses 120a-120n, and one or more customers i3〇a-130n The body and / or soft body are integrated or separated. The one or more electrical devices may include any suitable input device such as a keypad, mouse, touch screen, microphone or other means for inputting information. In addition, the one or more computers may include any communicative output device that conveys information associated with the operation of system 100, including digital or analog data, visual information, or audio information. Moreover, such one or more computers may include fixed or removable electrical &quot; brain readable storage media such as magnetic computer disks, CD-ROMs or cartridges, receiving input from system 100 and providing input to system 100; Suitable media. In addition, such one or more commissioning computers may include a package or processor and associated memory for performing instructions and manipulating information in accordance with the operation of system 100. Additionally or alternatively, the order fulfillment system 11 , one or more businesses 120a-120n and/or one or more customers I 30a-130n may each operate on a single computer at 201017576 or on a separate computer, or may be at - or Each of the multiple shared computers, or each of the computers, can be a workbench, a personal computer (pc), a network leikui/m^ electric leg, a personal digital assistant (pda), a wireless data file, or any Other combined gentlemen + once 0 weeks of the device. In another embodiment, one or more users can subscribe to #/,. The Ding Commodity Commitment System 110, one or more businesses 120a-120n, and a Roll of Customer Plus Red Offices are associated with a plurality of customers 130a-130n. Such one or more users may include, for example, an order commitment and/or within the treatment system (10)

❹

Or "planners" for multiple related tasks. Additionally or alternatively, the one or more users may include, for example, one or more of the _ 3 μ 订货 order commitments, order fulfillment, supply chain plans, and/or one or more correlations within the autonomous disposal system 100 The computer of the mission. In one embodiment, the order fulfillment system 110 can be coupled to the network 140 using a communication link 142 that can be adapted to support an order fulfillment system "i" and network during operation of the system 1"! Any wired, wireless, or other link that communicates between the data. One or more enterprises 120a-120n may be coupled to the network using communication keys 144a to 44n, which may be adapted to support one or more fake businesses 12〇a-i20n and the network during operation of system 1GG Any wired, wireless or other link between the 140 data exchanges. One or more customers l3〇a_l3〇n may be interfaced with network 140 using communication links 146a-146n, which may be adapted to support one or more customers 130a during operation of system 1〇〇 Any wired, wireless or other link that communicates with the data between the network and the network 14〇. Although the communication links 142, U4a-144n, and 146a-146n are shown as integrally coupling the 201017576 order commitment system 110, one or more enterprises i2〇a l2〇n.., the customers 130a-13 0n are integrally coupled to the network 14 Oh, but according to special circumstances, the order commitment system 110, one or more enterprises i2〇a l2〇n έΒ _ ^ one or more customers 130a-130n can directly communicate with each other. Alternatively or in the absence of a hole*, the order commitment system 11 can reside within one or more of the businesses 120a-120n, depending on the particular needs. In another embodiment, the network 14 may include an internet and any suitable local area network (LAN) that is coupled to the order commitment system lio, one or more enterprises 120a-120n, and/or multiple customers 130a-13On. Local Area Network (MAN) or Wide Area Network (WAN) Those skilled in the art will recognize that the complete structure and operation of the communication network 14 and other components within the system 1 are not depicted or described. Embodiments are used with the network and other components. Figure 2 illustrates the order commitment system 110 of Figure 1 in more detail in accordance with a preferred embodiment. As discussed above, the order commitment system 11A includes one of one or more locations Or a plurality of computers, including associated input devices, output devices, computer readable storage media, processors, memory's or other components for receiving, processing, storing, and transmitting information in accordance with the operation of system 100. In an embodiment, the order commitment system 110 receives, processes, stores, and transmits strategic data associated with one or more businesses 12〇a-120n and/or one or more customers 13〇a_13〇n in the repository 220. Server 2 10 includes one or more requirements implementation engines 2丨 2. Although server 210 is shown and described as including one or more requirements implementation engines 201017576 212, embodiments may encompass any suitable optimizer, depending on particular needs, Workflow, order commitment engine 'engine or engine combination. In an embodiment, demand implementation engine 212 may shorten or delay ordering depending on supply, distribution, allocation, and/or supply chain constraints. As an example and not a limitation, supply Chain restrictions include (but are not limited to) the following: k The order quantity is less than the minimum quantity that can be shipped. In this case, the entire order will be shortened even if there is sufficient supply and distribution. _ 2. The order quantity is not a multiple of the shipment quantity. In this case, the order will be shortened (assuming that the commitment policy for the order is allowed for partial shipment). / Order for the request for the location (guard, warehouse, distribution center or other specific location) m. In this case If there is no sufficient supply and distribution at the selected location, the order can be shortened or delayed. 4. Requested for a specific mode of transport In this case, the installation can only be carried out from the position where the transport mode is provided and may have the engine's choice to meet the order or meet the order on time. "Bu or as an alternative to the above restrictions - some restrictions The hard limit 1 may be non-negotiable, while the other limit may be a flexible limit: in addition, the bounce 1 ± limit may be the cause of the sub-optimal commitment and may be relaxed, for example, in the case of a high priority order. In another embodiment, the requirements implementation engine 212 only considers that it can be relaxed: due to (supply chain restrictions). For example, if the shipping lot (supply key limit cannot be changed), then this limit is not provided. The demand fulfillment engine 212, = the demand fulfillment engine 21r does not decide to relax the limit, may provide a better 201017576 database 220 contains one or more locations located at one or more locations of the feeder 21 remotely or remotely The library or other data is stored separately. Database 220 includes, for example, one or more policy models, change profiles, and report data 226. By way of example only and not limitation, the order fulfillment system 110 stores order fulfillment information associated with one or more businesses 120a-120n and one or more customers 130a 130n that may be by the server 21 and, in particular, by one or more The requirements implementation engine 212 is used. In addition, the user associated with the order commitment system 11A can specify the constraints that the demand implementation engine 212 should consider when calculating the cause via one or more policy models 222. The requirements fulfillment engine 212 includes one or more policy models, and the user can provide a strategy that the requirements implementation engine 212 should use in calculating the reasons discussed in more detail below and parsing the reports. In one embodiment, one or more policy models 222 define the types of demand requirements that the requirements implementation engine 212 considers when generating the cause and parsing the report. In addition, the strategy may be defined during the design phase and may depend on all changes that are authorized by the user to make a commitment to improve the order. As described above, if the user cannot change the shipment lot size, there is no need in the demand realization engine 2D' to report as a cause, because it is a time-consuming calculation. Additionally or alternatively, the demand fulfillment engine 212 can specify a pending policy that the one or more policy models 222 will use when generating an order for the user's attention and analyzing the report. In one embodiment, 'each policy model 222 includes one or more change profiles 224 that the requirements implementation engine 212 considers in the defined sequence (ie, one or more of the changes 201017576 are described in more detail below, in one embodiment, Relax_Min Quanthy Changes the minimum number of shipments. Essentially, the minimum number is - or the minimum number of multiple companies 120a-120n that can be shipped in any delivery. For example, if the requested quantity is less than the minimum quantity, then Unable to promise to order. In addition or as an alternative, the minimum quantity is modeled on the sales order line, product (essential) and delivery path. In addition, this strategy changes the relaxation needle

All such minimum quantities for sales orders. By way of example and not limitation, orders for 3 units of a project are subject to expiration as soon as possible (ASAP) commitment policy. In this example, the supply is 12 units on the 1st day and 12 units on the 5th day. The minimum quantity on the sales order line is 1G units, and the minimum number of products is 20 units. The order commitment will be 1 unit on the 1st day and 1G units on the 5th day and the remaining 1Q units will be shortened. When the demand implementation engine 212 executes this strategy, it can commit 12 units at the third and commit 12 units on the 5th, and the remaining 6 units will be shortened. In this case, the sales order will be changed to set the minimum quantity to - and the order will be re-committed. This ensures that the minimum quantity is not considered for this order. In another embodiment, the Relax Quote Multiple (Relax-Quote_Multiple) changes the shipping lot on the order line. In this change, any delivery quantity can be only a multiple of the quote multiple. For example, if the quote multiple is 10 units and the requested quantity is Η units, the order will be shortened. The quotation multiple is modeled on the sales order line, the product (essential) and the delivery channel. This strategy changes the relaxation of the 12 201017576 with these quotation multiples, and can then promise to place an order without any restrictions on the quantity delivered. Orders for 80 units of a project, by way of example and not limitation. The ASAP commitment policy is due on the first day. The supply is 25 units on the 5th day and 1 unit on the 5th. The quotation multiples on the sales order line product and delivery channel are 2〇, 4〇 and 3〇 units respectively. The commitment to order will be 20 units on the i-th day, and the remaining 6 units will be shortened. When the demand fulfillment engine 212 relaxes the compensation multiple policy, it provides that 25 units can be promised on time on the first day, and 1G units on the fifth day, and the remaining 45 units will be shortened. In this case, the order will be changed to have a quote multiple of ·i and the order will be re-committed. In another embodiment, the relaxation of the selection time (Relax-Pick-Pack_Time) changes the selection time of the relaxed order line. The selection time is the extra time to build the model on the sales order line, participation in the product (essential) and delivery. The selection time of the model is established at the channel and thus the order can be delayed. Relaxing this restriction symbolizes the accelerated disposal of materials and materials. However, unlike the minimum quantity and the quote multiple change, 'the package time is added by i so the limit is relaxed and (4) the package time at the product and delivery channel. • . . . . . . . . . . . . . . . . . As an example and not a limitation, the order for 2 units of the ASAP commitment policy is due on the first day. The supply is (10) units on the first day. The selection time for the sales order line, product (essential) and delivery channel is 3曰, 曰 and 日 respectively. The promise of ordering will be the first... 13 201017576 20 20 units (add all three option time). When the demand implementation engine 212 performs this policy with a relaxed package time change, it provides: 2 units can be committed on the 3rd day. In this case, the selection time will be removed from the sales order line and the order will be re-committed. In another embodiment, relaxing the maximum edge (Relax_Max_Edges) changes the number of relaxed shipping branches and this makes multipoint delivery possible. The largest edge of the sales order line provides this line to the largest wheel branch for delivery. In particular, this indication relates to the cost of shipping associated with the order. If the maximum number of branches is large, the order can be supplied from a source that is not directly shipped to the customer. Relaxing this limit symbolizes the willingness to adopt higher shipping costs to satisfy customers. In addition, each order line specifies the maximum shipping branch (edge) that can be used for the delivery of the order line. For example, if the ordering coffee _ is set to i, the delivery from the point of supply to the customer's destination must be direct. 参. For example only and not as a limitation, order for 20 units for AS AP The commitment policy expires on the first day. The supply at position 1 and position 2 is 1G units on the first day. The destination of the order is distribution center 2. The channel is assigned from the location h to the center distribution center 2 From position 2... knife with center 2. The maximum edge of the sales order line is 1. Here

t. When the demand implementation engine 212 executes this policy, it provides: 10 units that can be promised from the first day of the day. In this case, the best goods will be re-committed. Preset values in the line (very high number) and subscription 201017576 In another embodiment, the Relaxation License Delivery Area (Relax_permitted_Delivery_zones) change relaxes this limit and allows the Demand Implementation Engine 212 to consider all shipments for final delivery to the customer. point. The sales order line specifies the shipping location at which the final shipment to the customer can be made, known as the delivery area. Relaxing this restriction removes the list of licensed delivery areas from the sales order and provides a commitment not to have this limitation. In addition, each order line specifies the point of shipment at which the final shipment to the customer should occur.

As an example and not a limitation, the order for 2 units is about the AS:P commitment policy is in the first! The date expires. The supply at position 1 is 2 〇 early positions. The delivery channel is the location distribution center. The location 1 - distribution center distribution center 2 (consuming 1 day). Only shipments from Distribution Center 2 are licensed. The order commitment will be 20 units on the 2nd day, where the material is shipped from location 1 to the distribution center! And shipped from distribution center i to distribution t2. When the demand fulfillment engine 212 executes this policy, if the order of shipment is from the location to the distribution center, and to one or more customers 130a-130n, then the offer can be ordered on time on the first day. In the case of 'ordered delivery area will be removed and the order will be re-submitted 0. ' ' . . - - ' ' ' - In another embodiment, the license delivery source is relaxed (Relax-PermiUed-Delivery_s〇 The change in urces allows the requirements implementation engine 2 i 2 to consider all possible sources of supply. The sales order line may specify that the source of the supply must be transferred to the source. This limit removes the list of delivery sources from the sales order and allows the demand realization engine 212 to find the supply of all possible sources. In addition, each order 15 201017576 line can specify where the supply will be consumed. Just as an example and not a limitation 'Orders for 20 units. The ASAP Commitment Policy is due on the 1st. The supply at position 1 is 10 units and at position 2 is 10 units. The delivery source at the sales order line The list only contains the position order commitments will be the units from the position on the second day. When the demand implementation engine 212 executes this policy, if the supply is also consumed from location 2, then it is provided that the order can be promised on time on the second day.

In this case, the license delivery source for the order is removed and the order will be re-committed. In another embodiment, the change in the license delivery service (Relax-Permitted-Delivery_Serviees) allows the demand implementation engine 212 to consider all possible transportation. The model is to improve the promise. The sales order line specifies the shipping mode that will be used for the shipment order. Relaxing this limit allows the demand implementation engine 212 to use a faster mode of transport or to allow other sources and zones with a different mode of the wheel than the mode selected by the user. In addition, each order line can specify the mode of transport that should be used for shipment. Just as an example and not a limitation 'Orders for 2 units are about the ASAP commitment policy that expires on the 2nd day. The destination of the order is 1 ° from the distribution center to the distribution center! There are two modes of transportation: the air transportation mode that consumes i day and the road transportation mode that consumes 2 days. The delivery service list contains only road transport modes. On the first day, there are 2 units of supply at location i. The order 夂 promises to use the road transport pattern from position 1 to 2 units on the 3rd (late 1st). When the demand implementation engine 212 executes this strategy, it provides: the air transport mode can be used to order on time 201017576. In this case, the order delivery service is removed and the order will be re-committed.

In another embodiment, the change in Relaxation License Matching Product (Relax_permitted-Matching-pr〇ducts) allows the demand implementation engine 212 to use the requested item to link to satisfy all products ordered. The sales order line specifies a list of different products that can be consumed by the supplier. In other words, the order line specifies that the supply should be made to meet the order's production =. In the demand implementation engine 212, there may not be any correlation between the requested item and the order tm in the order. When demand implementation engine 212 relaxes this limit, one or more demand fulfillment engines 212 may be able to improve the commitment of the order by consuming all of the products from which the project is mapped. Report Distribution Shortages In another embodiment (Report-Allocation_Sh〇mge) changes relax all allocations and allow orders to be consumed directly from the supply. If the supplier is not assigned to the order to consume, then the order will not receive the best promise. This can only happen if there is a supply and the reasons discussed below and an analytical report, the change report - the order for the mosquito feed, assuming that a certain supply to other sellers is available for the order* The seller of Baozhi 0 this change is only reported, it is a shortage, and it will have to be allocated before re-committed to order to solve the problem. By way of example only, and not limitation, for H-ready, the order for 25 units is entered at Seller 1 and expires on the first day. The helmet is supplied as 10 units on the 1st (1st week) 17 201017576 and 10 units on the 2nd (2nd week). This supply is allocated to Vendor 1 (5 units in Week 1 and 5 units in Week 2) and Vendor 2 (5 units in Week 1 and 5 units in Week 2). The commitment of the order will be 5 units on the first day and 5 units on the 8th. When the demand implementation engine 212 executes this policy, it is assumed that the allocation is available for the seller 1' whose offer can commit an additional 5 units on the 1st and 8th days. In this case, the distribution must be moved from the seller 2 to the seller 1 in the i-week and the second week. In another embodiment, the report commitment shortage (Report_Atp-Shortage) changes the allowable demand realization engine 212 to calculate the supply. The shortage is sufficient to fully satisfy the order on time. If there is a choice to accelerate this supply from the manufacturer or from the manufacturer, the order can be placed on time. In the case of a commitment (CTP) material order (bom), the supply can be sourced at more than one level (final item, first level component or most upstream component, etc.). This leads to more than one choice to resolve the shortage or delay. Φ Additionally or alternatively, the demand implementation engine 212 is only for example in the deployment phase

During this period, supply shortages were provided for selected pre-determined products. In the case of cTP-environment, a large number of intermediates and finished products can be manufactured from a small group of components. - In one embodiment, the user controls the supply of only certain components and only certain t-intermediaries that may also be purchased from an external manufacturer. Therefore, if the cause and resolution report provide a supply defect at the middleware or an additional supply that cannot be moved, then a large amount of information that is not useful is presented to the user. The production can be identified by making the supply elastic by marking the product. Oh, and these products are called marked buffers (Marked 18 201017576

Buffer) is discussed in more detail below. The varietal σ needs to be fully and on time to commit to the additional supply of orders. This «can contain more than one choice to improve the commitment of the order. The user will have to choose this option and will make a selection before the re-commitment of the order, manually, and in the case of the project that can be requested from the component manufacturing. In the case of deep supply chains (multiple layers), the number of choices can be very large.

In an embodiment, the product is marked to move the additional supply (this is referred to as the internal buffer). In many cases, additional supplies can be configured at the intermediate and at the final project. In such cases, if the upstream component is marked by the job, the group should be in short supply. For the step-by-step description of the shortage report, an example is given now. In the following example, the order for 4 units of the project is due on the first day. The supply of 10 units can be obtained on the 1st day, and the supply of the Magic Unit can be obtained on the 5th day. The promise of ordering is the n solid units on the jth day and the 10 units on the 5th. When the demand implementation engine 212 executes this strategy, the order is promised (on the 1st day). In this case, there is only one selection, and this will only be reported if the item is marked. For example, assume that the project can be manufactured from the material % and the capacity c. There is no material supply, and 5 units of capacity are available on the next day. In this case, the strategy will provide two options for ordering on time: ' : ... I supply of 30 units on the first day of the project... 201017576 2·30 in the first material The supply of units. If the additional supply of the item is not available, meaning that the item can only be manufactured and cannot be purchased from outside, the user will only mark the material. In this case, the only choice would be to increase the supply of materials.

The demand fulfillment engine 212 first attempts to use existing material supplies and resources whenever possible in the calculation of the shortage report (this is referred to as the balancing step). To explain the balancing steps, an example is given. In the following examples, if the project can be manufactured from C and C. All products ρ, Μ and c are labeled buffers and P does not have a supply. The supply of material Μ and capacity C is as follows: • Material Μ: 1st day 1 〇 sister unit • Valley C: 1st day... 1 .. Unit for 30. Units in order, $ η . a 炅隹 brother expires on the 5th. The shortfall report for this situation will be as follows (there are two options): • Option 1: 〇1st material Μ1 〇1 unit supply 〇2nd day capacity C 10 units of supply 〇5th day material The supply of 10 servants. Supply of 10 units of capacity on the 5th day. Option 2: Supply of 1 unit of material on the 1st day 2nd supply of 1 unit of capacity C 1 supply of supply of the first two supply shortages The 20 units of the 5th project ρ are consumed as much as possible, and the supply shortages such as 201017576 are calculated before all other options are calculated, and they are common to all choices. As discussed above, when a product is identified by marking the product, the product is referred to as a "marked buffer." In addition, such products may also be identified, where excess supply may be moved under restricted conditions. In one embodiment, a User Defined Intercept (UDF) is generated at the product base model to store whether it is flagged. The UDF at the product model is defined by generating a block in the Item Site Master table stored in the repository 220. For example, if the field is fie丨dl » set the marked buffer by using the value in the rotten fieidl using, for example, the following OIL program command in the plan script:

Supply_chains[l ]. sellers, for—each(#. product—roots .for _each( do( ❷ define(pro〇t, #), if(pro〇t.field 1, proot.set_marked_buffers(proot.fieldl)) In another embodiment, the later and shorter orders of the BOM can be resolved by moving the allocation of one component and generating the supply of another component. If the Rep is executed earlier. rt_A] i〇cati〇n—shortage step' then all the cases are reported in the Report-ATP_Sh〇rtage step-- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . As discussed above, the strategy model 222 includes one or more of the changes discussed above, wherein each of these changes is in its defined order. application. For example, if the strategy includes relaxing the minimum amount and relaxing the quote multiple change, the demand fulfillment engine 212 first calculates the impact of the minimum shipment quantity on the order and then relaxes the shipment lot at its maximum. In addition, the reason and analysis report will provide a commitment to improve directly by applying the first change, then applying the first and second changes, and so on. This situation continues until the demand fulfillment engine 212 performs all of the changes in the strategy or the order is fully committed on time (whichever occurs first). The Fig. 3 diagram illustrates an exemplary system in accordance with an embodiment which includes two options for delivering a service&apos; including an air transportation mode 31〇, and a road transportation mode 320. System 3 includes location "L〇ei" 3i2a, position 2 (Loc2) 312b, and position 3 (L〇c3) 312c, distribution center i (Dc〇❹ 3 i4a, distribution center 2 (DC2) 3 Multiple delivery paths... show and describe a specific number of locations, distribution centers, and delivery paths, but • depending on the specific needs, the embodiment can cover any location, distribution center, and/or _ delivery path. An exemplary workflow for interpreting the operation and analysis of the system and parsing the later and shorter ordering problems in system 300 now gives an example. In the following example, Iteml is in Locl 312a, LOC2 312b, and L〇C3. Available at 312c. The supply of Iteml is shown in Table 1. 201017576 The position of the seller's project begins at the end of the period. The period has been allocated and consumed. τ Item 1 Loci 10/6/2007 10/7/2007 15 0 15 τ Item 1 Loc2 10 /5/2007 10/6/2007 15 0 15 τ Item 1 Loc3 10/5/2007 10/6/2007 15 0 15 Table 1 The assignment of Iteml to sellers S1 and S2 is shown in Table 2 below. Period End Date Allocated Available S1 Item 1 Loci 10/ 1/2007 10/8/2007 10 0 10 S2 Project 1 Loci 10/1/2007 10/8/2007 5 0 5 S1 Project 1 Loc2 10/1/2007 10/8/2007 10 0 10 S2 Project 1 Loc2 10 /1/2007 10/8/2007 5 0 5 S1 Project 1 Loc3 10/1/2007 10/8/2007 10 0 10 S2 Project 1 Loc3 10/1/2007 10/8/2007 5 0 5 Table 2 Here In the example, the order is OrderOl-Iteml for 60 units of Iteml at the seller S1 due to expire on October 6, 2007, where the destination is Distribution Center 2 (DC2) 314b. In this example, the commitment policy is AS AP, and the following attributes are set on the project request: License Delivery Area: DC1 314a License Delivery Source: Loc2 312b and Loc3 3 12c License Delivery Service: Road Transportation Mode 320 License Matching Product Fundamentals: Iteml::SKU::Loc3 Due to License The delivery area is DC 1 314a and the destination is DC2 314b, so the final edge of the delivery is DC 1 3 14a - DC2 3 14b. As indicated above, the license delivery source and the license matching product simply limit the consumption only from Loc3 3 12c, so only one delivery path is possible: Loc3 312c - DC1 314a - DC2 314b. 23 201017576 Continuing with this example, the default edge of the delivery request has a default value of 1, and delivery cannot be done with a delivery path with 2 edges. Therefore, OrderOl-Iteml is completely shortened. The policy change (described above) in this example has the following steps in the same order:

1. RELAX, MAX_EDGES 2. RELAX-PERMITTED, DELIVERY, ZONES 3. RELAX_ PERMITTED, MATCHING. —PRODUCTS 4. RELAX-PERMITTED-•DELIVERY— SOURCES 5. RELAX_ PERMITTED, DELIVERY— SERVICES 6. REPORT _ALLOCATION_SHORTAGE 7. REPORT ATP SHORTAGE In this example, the first step of relaxing the maximum edge will be performed for later and shorter items after the recommitment. However, since there is no change in the provisioning picture, the recommitment will provide the same result, meaning no commitment. ❹ / Therefore, the first step of _ is the needle. Pair: In: This example _. In the number of 60 units provided by the order of H.OrderOl-Iteml, perform the relaxation of the maximum edge... • Result..·· On_time_q.ty ...O late_qty... 10: .late—date..07-10-0.8 • short-qiy 50 API output is as follows: &lt;dfx: Strategy St epResult&gt; .. . - ..... .... &lt;dfx: Strategy St epName&gt;&lt;dfx:Value&gt;RELAX MAX EDGES&lt;/dfx:Value&gt;&lt;/dfx:StrategyStepName&gt; 24 201017576 &lt;dfx:PromiseInformation&gt;&lt;dfx: Promise Quantity OnTime Value =&quot;0&quot;&gt;&lt;/dfx:PromiseQuantityOnTime&gt;&lt;dfx:PromiseQuantityLateValue=&quot;10,,&gt;&lt;/dfx:PromiseQuantityLate&gt;&lt;dfx:PromiseQuantity Short Value = &quot;5 0&quot;&gt;&lt;/dfx:PromiseQuantityShort&gt;&lt;dfx: Late Date Value = &quot;10/08/2007&quot;&gt;&lt;/dfx:LateDate&gt;&lt;/dfx:PromiseInformation&gt;&lt;/dfx: Strategy StepRe suit &gt; As shown above, after relaxing the maximum edge limit, Loc3 312c - DC1314a - DC2314b becomes a possible delivery path, and thus After the allocation of Iteml::SKU::Loc3 is consumed at S1, a commitment of 10 units is provided on the 8th day. In addition, due to the license delivery service limitation, the final edge of the delivery DC 1 314a - DC2 314b must use the φ road transport mode 320, which is 2曰 as shown in Figure 3. however,

Loc3 312c -&gt; ΓΚΠ 314A can use the air transport mode 310 shown in Fig. 3, which is a more time-consuming service and only takes 1 day. Therefore, • The total delivery time is 3 days. The supply at L〇c3 3 12c is available on the 5th day, . . . . . . . . . and therefore the commitment is provided after 3 days (ie, on the 8th day). Continuing with this example, the next step is to implement a relaxed license delivery area for the later and shorter items from the previous step, which is again 60 units. . . . . . . . . . . .... (meaning, 10 are late and 50 are shorter). .. .. . : : Result: 〇n_time_qty Ό. late_qty· 10:.late_dat.e 07-10-07 . . . 1 . ... ........ ..... ... ..... .: ....... ... 25 . . . 201017576 short_qty 50 The API output is as follows: &lt;dfx: Strategy Step Re suit〉 &lt;dfx:StrategyStepName&gt;, &lt;dfx:Value&gt; RELAX_PERMITTED DELIVERY ZONES&lt;/dfx: Value〉 &lt;/dfx:StrategyStepName&gt;&lt;dfx:PromiseInformation&gt;

&lt;dfx:PromiseQuantityOnTime Valu e = &quot;0',x/dfx: Promise Quantity OnTime&gt;&lt;dfx:PromiseQuantityLateValue=&quot;10&quot;&gt;&lt;/dfx:PromiseQuantityLate&gt;&lt;dfx:PromiseQuantity Short Value = &quot ;5 0&quot;&gt;&lt;/dfx:PromiseQuantityShort&gt;&lt;dfx:LateDate

Value = &quot;10/07/2007,,&gt;&lt;/dfx:LateDate&gt;&lt;/dfx:PromiseInformation&gt;&lt;/dfx: Strategy Step.Res.ult&gt; As shown above, after relaxing the license delivery area limit 'Two delivery paths are possible, one delivery path is shown in the previous step, and the second delivery path is Loc3 312c - DC2 3 14b using road transport mode 320, which is 2 days as shown in FIG. The latter is preferred in this example because it consumes less delivery time, meaning 2 曰. Therefore, the commitments provided in the previous steps can now be provided one day in advance (ie, on the 7th - 2β ::;; 201017576). Continuing with this example, the next step is to perform a relaxed license matching product for the later and shorter items from the previous step, which is again 60 units. Result: On_time_qty 0 late—qty..20 late_date. .07-10-07 .short_qty 40 . . . The API output is as follows: &lt;dfx: Strategy StepResult&gt; ❿ &lt;dfx:StrategyStepName&gt;

&lt;dfx:Value&gt;RELAX_PERMITTED_MATCHING_PRODU CTS&lt;/dfx:Value&gt;&lt;/dfx: Strategy StepName&gt;&lt;d fx: Promis el n formation〉 &lt;dfx:PromiseQuantityOnTime Parameter Value = &quot;0&quot;&gt;&lt;/dfx :PromiseQuantityOnTime&gt;&lt;dfx:PromiseQuantityLa1;e:

Value = &quot;20&quot;&gt;&lt;/dfx:PromiseQuantityLate&gt; . . . . .... - &lt;dfx: Promise Quantity Short '..... :..... ... .. .. .........

Value = &quot;40&quot;&gt;&lt;/dfx:PromiseQuantityShort&gt;&lt;dfx:LateDate . . . . . .. . * . . .

Value = &quot;10/07/2007&quot;&gt;&lt;/dfx:LateDate&gt;&lt;/dfx:PromiseInformation&gt;&lt;/dfx:StrategyStepResult&gt; . . . . . . . :..27 .. .... 201017576 As indicated above, the supply of 10 units at Loc2 312b may also be consumed after the relaxation of the license-matched product's fundamental limit (at Loci 312a). . . . Consumption). Loc2 312b and .

The Loc3 312c has a similar delivery network and therefore uses a similar delivery path (Loc2 312b - DC2 314b). The commitments provided in the previous steps have improved the number of 10 units and a total of 20 units of commitments are now available on the 7th day. Continuing with this example, the next step is to perform a relaxed license delivery source for the later and Φ shorter items from the previous step, which is again 60 units. Result: On_time_qty 0 late_qty 30 late_date 07-10-08 short qty 30 The API output is as follows: &lt;dfx: Strategy StepResult&gt;&lt;dfx:StrategySt;epName&gt;. ❹ &lt;dfx:Value&gt;RELAX_PERMITTED_DELIVERY_SO URCES&lt;/dfx: Value〉 - &lt;/.dfx:StrategyStep.Name&gt;: ........ &lt;dfx:PromiseInformation&gt;&lt;dfx:ProrniseQuantityOnTime Value = &quot;0&quot;&gt;&lt;/dfx:PromiseQuantityOiiTime&gt;.&lt;dfx :PromiseQuantityLate Value=&quot; 3 0&quot;&gt;&lt;/dfx:PromiseQuantityLate&gt; 28 201017576 &lt;(ifx: Promise Quantity Short Value = &quot; 3 0&quot;&gt;&lt;/dfx: Promise Quantity Short&gt;&lt;dfx: LateDate . . ' .. .

Value=&quot;l 0/08/200 7 &quot;&gt;&lt;/dfx:LateDate&gt;&lt;/dfx:PromiseInformation&gt;&lt;/dfx:StrategyStepResult&gt; As shown above 'After relaxing the license delivery source limit, Loci 312a The supply of 10 units is also available. Loc 1 3 12a &gt; Loc2 3 12b and Loc3 3 12c have similar delivery networks and therefore adopt a similar delivery path (Loci 312a - DC2 314B). Since the supply at Locl 312a is available on the 6th day, the commitment from Loci 312a is available at 8th (delivery time is 2 days). For reporting purposes, 'collect and display all late promised quantities on the last commitment date. Therefore, the commitment of 30 units is now available on the 8th day. Continuing with this example, the next step is to perform a relaxed license delivery service for later and shorter projects from the previous steps, which is again 6 units 〆.. ... ' . .. .... . . . .. Result: Onjime-qty 20 late-qty 10 late-date 〇7_1〇_〇7 short qty 30 API output is as follows: &lt;dfx:StrategyStepResult&gt;&lt;dfx: Strategy Si epName〉 29 201017576

&lt;dfx:Value&gt;RELAX_PERMlTTED_DELIVERY_SE RVICES&lt;/dfx:Value&gt; . . &lt;/dfx: Strategy StepName&gt;·.... &lt;dfx:PromiseInformation&gt;&lt;dfx: Promise Quantity OnTime

Val ue =&quot; 2 0&quot;&gt;&lt;/dfx: Promise Quant ityOnTime&gt;&lt;dfx:PromiseQuantityLate

Value=&quot; 1 0&quot;&gt;&lt;/dfx:PromiseQuantityLate&gt;&lt;dfx: Promise Quantity Short

Value=&quot;30&quot;&gt;&lt;/dfx:PromiseQuantityShort&gt;&lt;dfx:LateDate

Value = ,,10/07/2007,,x/dfx:LateDate&gt;&lt;/dfx:PromiseInformation&gt;&lt;/dfx: Strategy St epRe suit〉. φ As shown above, after relaxing the license delivery service limit, the third The air transport mode 3 10 shown in the figure is a less time consuming service and will be reduced to -1 day. Loc2 3 12b and Loc3 312c are now available on time 6 • Commitment (supplied on day 5), while Loci 312a will still provide the 7th day ' . . . . . . . ..... late promise (supply on the 6th day). Continuing with this example, the next step is to allocate a shortfall for the project execution report from the later steps of the previous step and ..... . The project is now 40 units. . . . . . . . . . Result: On_time_qty 10. late_qty 15 late_date 07-10-07 201017576 Assignment to product requirements Iteml::SKU::Loc2-Sl::Level2 on

FE Start Date 07-10-01 for Qty 5 Is_On_Time TRUE Assignment for Product Requirements Iteml::SKU::Loe3-Sl::Level2 on FE Start Date 07-10-01 for Qty 5 Is_On_Time TRUE Assignment for Product Requirements Iteml ::SKU::Locl-Sl::Level2 on

FE Start Date 07-10-01 for Qty 5 Is On Time The FALSE API output is as follows:

❹ &lt;dfx: Strategy StepRe suit〉 &lt;dfx: Alloc at ionReport&gt;&lt;dfx:AllocationNeeded&gt;&lt;dfx:Product&gt;&lt;dfx:ItemValue=&quot;Item 1 &quot;&gt;&lt;/dfx:Item&gt ; &lt;dfx:ProductLevel Value = &quot;SKU&quot;&gt;&lt;/dfx:ProductLevel&gt;&lt;dfx:PrDductLocation .. . .... ... . ... ...

Value: &quot;Ι^.οο2&quot;&gt;&lt;/(!£χ:ΡΓ〇άιΐί^Ι/ο cation>:':: . . . . . . .... &lt;/dfx:Product&gt ; &lt;dfx:Seller&gt; ' &lt;d.fx:.:Selle.rName Value = &quot; S 1 &quot;&gt;&lt;/dfx: SellerName&gt;&lt;dfx: SellerLevel

Value = &quot;Level2 &quot;&gt;&lt;7 dfx: SellerLevel&gt;&lt;/dfx:Seller&gt; . .' . . .. ' &lt;dfx:ForecastBucket&gt; 31 201017576

Value: &lt;dfx: StartDate = &quot;10/01/2007,,&gt;&lt;/dfx:StartDate&gt;&lt;dfx:EndDate Value: =&quot;10/0 8/200 7&quot;&gt;&lt;/dfx :EndDate&gt;&lt;/dfx:ForecastBucket&gt;&lt;dfx: Short age Qty

Value = &quot;5&quot;&gt;&lt;/dfx:ShortageQty&gt;

Value: &lt;dfx:OnTime = &quot;TRUE&quot;&gt;&lt;/dfx:OnTime&gt;&lt;/dfx:AllocationNeeded&gt;&lt;dfx:AllocationNeeded&gt;&lt;dfx:Product&gt;&lt;dfx:Item Value = &quot;Item 1 &quot;&gt;&lt;/dfx:Item〉 &lt;dfx:ProductLevel Value: = &quot;SKU&quot;&gt;&lt;/dfx:ProductLevel&gt;&lt;dfx: Pro duct Location Value: = &quot;Loc3 &quot;&gt;&lt;/dfx:ProductLocation&gt;&lt;/dfx:Product&gt;&lt;dfx:Seller&gt;&lt;dfx: SellerName Value: = &quot;Sr'x/dfx:SellerName&gt;&lt;dfx: Sell er Level

Value = &quot;Level2&quot;&gt;&lt;/dfx:SellerLevel&gt;&lt;/dfx:Seller> 32 201017576 &lt;dfx: Fore castBu eke t&gt;&lt;dfx: StartDate

Value = &quot; 10/0 1/2007 &quot;&gt;&lt;/dfx:StartDate&gt;&lt;dfx:EndDate

Value = &quot; 10/0 8/200 7 &quot;&gt;&lt;/dfx:EndDate&gt;&lt;/dfx:ForecastBucket&gt;&lt;dfx: Short age Qty Value=&quot;5&quot;&gt;&lt;/dfx:ShortageQty&gt ; &lt;dfx:OnTime

Value=&quot;TRUE&quot;&gt;&lt;/dfx:OnTime&gt;&lt;/dfx:AllocationNeeded&gt;&lt;dfx: Alio cat ionNeeded&gt;&lt;dfx:Product&gt;&lt;dfx:Item Value = &quot;Item 1 &quot;&gt ;&lt;/dfx:Item〉 &lt;dfx:ProductLevel 馨Value=&quot;SKU&quot;&gt;&lt;/dfx:ProductLevel&gt;&lt;dfx: Pro ductLo cation Value=&quot;Locl &quot;&gt;&lt;/dfx: ProductLocation&gt; - &lt;/dfx:Product&gt;&lt;dfx:Seller&gt;&lt;dfx: SellerName Value:&quot; S 1 ”&gt;&lt;/dfx:SellerName&gt;&lt;dfx: SellerLevel

Value = &quot;Level2&quot;&gt;&lt;/dfx:SellerLevel&gt; 33 201017576 &lt;/dfx: Seller〉 &lt;dfx:ForecastBucket&gt;&lt;dfx:StartDate

Value = &quot;10/01/2007&quot;&gt;&lt;/dfx:StartDate&gt;&lt;dfx:EndDate

Value = &quot; 10/0 8/2007 &quot;&gt;&lt;/dfx:EndDate&gt;&lt;/dfx:ForecastBucket&gt;&lt;dfx:ShortageQty

Value = &quot;5&quot;&gt;&lt;/dfx:ShortageQty&gt;&lt;dfx:OnTime

Value = &quot;FALSE&quot;&gt;&lt;/dfx:OnTime&gt;&lt;/dfx:AllocationNeeded&gt;&lt;/dfx:AllocationReport&gt;&lt;dfx: Strategy StepName&gt;

φ &lt;dfx:Value&gt;REPORT_ALLOCATION_SHORTAGE &lt;/dfx: Value〉 &lt;/dfx: Strategy StepName&gt; - &lt;dfx:PromiseInformation&gt;&lt;dfx:PromiseQuantityOnTime Value = &quot;10&quot;&gt;&lt;/dfx:PromiseQuantityOnTime&gt;&lt;dfx:PromiseQuantityLateValuer&quot; 1 5 &quot;&gt;&lt;/dfx:PromiseQuantityLate&gt; 34 201017576 &lt;dfx:PromiseQuantity Short Value = &quot;15&quot;&gt;&lt;/dfx:PromiseQuantityShort&gt;&lt;dfx:LateDate

Value = &quot; 1 0/07/200 7&quot;&gt;&lt;/dfx:LateDate&gt;&lt;/dfx:PromiseInformation&gt;&lt;/dfx: Strategy StepResult&gt; As shown above, the report allocation shortage step is still not available but can be consumed Any remaining supply used after some mobile allocation steps. In addition, the Reporting Shortage Assignment step also provides a specific mobile allocation step that will be added to the on-time commitment or later commitment. Please note that it only provides the 'to_seller' information for the mobile assignment step and does not provide 'from_seller' information, for example, here it is provided: For Iteml::SKU::Loc2, the number of 5 units 'at a seller 'Also available, but needs to be assigned to Sl::Level2 to improve on-time commitment; the same is true for Iteml::SKU::Loc3. Similarly, for Iteml::SKU::Loc3, the number of 5 units ‘is still available at a certain φ seller', but needs to be assigned to Sl::Level2 to improve the late promise. • Continuing with this example, the next step is to report an ATP shortage for the late and shorter project execution from the previous step, which is now 30 units. Result: On_time_qty 30 late_qty 0 late date -------- short_qty 0 ATP selection number -1

Atp Qty Needed 30 For Product Item 1:: SKU: :Loc3 on ATP Bucket Start Date 07-10-05 Is On Time TRUE 35 201017576 The API output is as follows: &lt;dfx: Strategy St epResult&gt;&lt;dfx: ATP Report〉 &lt ;dfx: ATPShortageOption&gt;&lt;dfx: ATP ShortageRequirement&gt;&lt;dfx:Product&gt;&lt;dfx:Item

Value=&quot;Iteml&quot;&gt;&lt;/dfx:Item&gt;&lt;dfx:ProductLevel

Value=&quot;SKU&quot;&gt;&lt;/dfx:ProductLevel&gt;&lt;dfx:ProductLocation

Value=&quot;Loc3 &quot;&gt;&lt;/dfx:ProductLocation&gt;&lt;/dfx:Product&gt;&lt;dfx:Seller&gt;&lt;dfx: SellerName ❹ Value=&quot;S 1 &quot;&gt;&lt;/dfx: SellerName&gt;&lt;dfx:SellerLevel . Value = &quot;Level2&quot;&gt;&lt;/dfx:SellerLevel&gt; - &lt;/dfx: Seller〉 &lt;dfx: ATPBucket&gt;&lt;dfx: StartDate

Value = &quot;10/05/2007&quot;&gt;&lt;/dfx:StartDate&gt;&lt;dfx:EndDate

Value = &quot;10/06/2007&quot;&gt;&lt;/dfx:EndDate&gt; 36 201017576 &lt;/dfx: ATP Bucket〉 &lt;dfx: Short age Qty

Value=&quot;3 0&quot;&gt;&lt;/dfx: Shortage Qty&gt;&lt;dfx:OnTime

Value:&quot; TRUE &quot;&gt;&lt;/dfx:OnTime&gt;&lt;/dfx: ATP Short age Requirement〉 &lt;/dfx: ATP Shortage Option&gt;

&lt;/dfx: ATP Report> &lt;dfx:StrategyStepName&gt;&lt;dfx:Value&gt;REPORT ATP SHORTAGE&lt;/dfx:Valu &lt;/dfx: Strategy St epName&gt;&lt;dfx:PromiseInformation&gt;

&lt;dfx:PromiseQuantityOnTime Value = &quot;3 0&quot;&gt;&lt;/dfx - Promise Quant ityOnTime&gt;&lt;dfx:PromiseQuantityLate

Value = &quot;0&quot;&gt;&lt;/dfx:PromiseQuantityLate&gt;&lt;dfx: Promise Quantity Short

Value = &quot;0&quot;&gt;&lt;/dfx:PromiseQuantityShort&gt;&lt;dfx:LateDate

Value = &quot;&quot;&gt;&lt;/dfx: Late Date〉 &lt;/dfx:PromiseInformation&gt;&lt;/dfx: Strategy St epResult&gt; 37 201017576 As shown above, you can commit to the report of available shortage steps to consider 'marked-buffer 'Concept to reduce the number of choices in the CTP scenario. Any product with a marked-buffer set m is only considered to be available for purchasing more supplies. In this case, all 3 products Iteml::SKu::L〇ci,

Iteml::SKU::Loc2 ^ Iteml ::SKU::Loc3 ^ marked_buffer is set to ‘true,. Therefore, there may be three promises (Ατρ) choices that will be used to improve on 30 (four) commitments - in the fifth purchase

Iteml::SKU::Locl ^ Iteml ::SKU::Loc2 or Iteml::SKU::Loc3 The number of 30 units. For the forecast in the item-request.matching_f〇recasts list, ----- first look for the forecast and its BOM, and determine all possible ATp choices. In addition, even if there is some sort of later and/or shorter, _____ only reaches the next forecast for further evaluation. However, when the commitment has been fulfilled on time, the ___ one will not reach the next forecast. • In this example, the item-request.matChing_forecasts list happens to be Iteml::SKU::L〇c3, and its first forecast can fulfill the promise by _, so in this example, it is not evaluated in the list. Other pre-reports and only one choice. . . - . . . . - Figure 4 illustrates an exemplary position 4 根据 according to an embodiment. Location 4〇〇 includes component 1 (Compl) 4〇2a, component 2 (Comp2) 4〇2b, component 3 (Comp3) 402c, component 4 (Comp4) 402ci, buffers 404a, 404b, and 4l, intermediate capacity! (CapIintl) 4〇6a, ten capacity 2 (Caplint2) 400b, alternating intermediate component j (Aitintl) 4〇8a, medium 201017576 component 1 (Inti) 408b, intermediate component 2 (Int2) 408c, alternating intermediate component 2 ( Altlnt2) 408d, Finished Capacity 1 (CapFGl) 412, Finished 1 (FG1) 414, and Alternate Finished 1 (AltFGl) 416. Although a particular number of components, buffers, intermediate capacities, alternate intermediate components, intermediate components, finished product capacities, finished products, and/or alternate finished products are shown and described, embodiments may encompass any number of components, buffers, intermediates, depending on particular needs. Capacity, alternating intermediate components, intermediate components, finished product capacity, finished products and/or alternate finished products. To further explain the operation of location 400 and an exemplary workflow for analyzing and resolving later and shorter ordering issues in location 400, an example is now given. In the following example, the supplier of the finished product (FG1) project shown in Table 3 below is started at the end of the period. The period has been allocated and consumed. T FG1 Loci 10/10/2007 10/11/2007 15 0 50 T FG1 Loci 10/15/2007 10/16/2007 10 0 10 Table In addition, the allocation of FG1 to sellers S1 and S2 is shown in Table 4 below. The position of the seller's project begins. The end date has been allocated. The consumed ATP S1 FG1 Loci 10/8/2007 10/15/2007 40 0 40 S2 FG1 Loci 10/8/2007 10/15/2007 10 0 10 S1 FG1 Loci 10/ 15/2007 10/22/2007 10 0 10

Table 4. In this example, the order is OrderOl-FGl-Locl for 170 units of FG1 at the seller S1 due on October 8, 2007, and the commitment policy is ASAP. However, in this example, there is no 'on-time commitment, only two later commitments will be provided, 40 units on the 10th day and 10 units on the 15th, and the remaining 120 units will be shortened. 39 201017576 The policy change (described above) in this example has the following steps in the same order:

1. REPORT_ALLOCATION one SHORTAGE

2. REPORT_ATP_SHORTAGE In this example, the first step reports that the allocation shortage is performed after the recommitment for the later and shorter items. However, since there is no change in the supply picture, the recommitment will provide the same result, meaning no commitment. Therefore, the first step is to perform a report allocation shortage for the number of 1 70 units provided in the order of OrderOl-FGl-Locl in this example. Result: On_time_qty 0 late_qty 60 late_date 07-10-15 short_qty 110 Assignment for product requirements FGl::SKU::Locl-Sl::_Level2 on FE Start Date 07-10-08 for Qty 10 Is_On_Time FALSE API output is as follows: &lt ;dfx:StrategyStepResult&gt; * . . . . ❿:. &lt;dfx: AllocationReport&gt; - Circle&lt;dfx: AllocationNeeded&gt; ... . . . . . . . ' • &lt;dfx:Product&gt; ... . . . . . .... .... - &lt;dfx:Item Value = &quot;FGl &quot;&gt;&lt;/dfx:Item&gt; ' ... ' ' .. .. .... . . ... .... &lt;dfx:ProductLevel . ' ...

Value=&quot;SKU&quot;&gt;&lt;/dfx:ProductLevel&gt;&lt;dfx: Product Location Value = &quot;Loc 1 &quot;&gt;&lt;/dfx:ProductLocation&gt;&lt;/dfx:Product&gt; -. . .. .. .. ...... . . . . . . . . . . . . . . . . . . 40 201017576 &lt;dfx: Seller&gt;&lt;dfx:SellerName Value= &quot;S1 &quot;&gt;&lt;/dfx:SellerName&gt;&lt;dfx:SellerLevelValue=&quot;Level2&quot;&gt;&lt;/dfx:SellerLevel〉&lt;/dfx:Seller&gt;&lt;dfx:ForecastBucket&gt;&lt;dfx : StartDate Value=&quot;10/08/20G7&quot;&gt;&lt;/dfx:StartDate&gt;&lt;dfx:EndDateValue=&quot; 10/1 5/2007M&gt;&lt;/dfx:EndDate&gt;Win&lt;/dfx:ForecastBucket&gt; ❹ &lt;dfx:ShortageQty Value = &quot; 1 0&quot;&gt;&lt;/dfx:ShortageQty&gt;&lt;dfx:OnTimeValue=&quot;FALSE"&gt;&lt;/dfx:OnTime&gt;&lt;/dfx:AllocationNeeded&gt;&lt;/dfx:AMocationReport&gt;&lt;dfx:StrategyStepName&gt;&lt;dfx:Value&gt;REPORT_ALLOCATION_SHORTAGE&lt;/dfx:Value&gt; ... .. .. ... . . ....

.........&lt;/dfx.: Strategy StepName&gt;'V &lt;dfx:PromiseInformation&gt; * &lt;dfx: Promise QuantityOnTime * Value = &quot;0&quot;x/dfx: Promise Quant ityOnTime&gt ; , . ... ... ......... ... .... &lt;dfx: Promise Quantity L:ate:'

Value = &quot;60&quot;&gt;&lt;/dfx:PromiseQuantityLate&gt;&lt;d fx :Pr o mi se Quantity Short . · . . . . . ; ....

Value=&quot;110&quot;&gt;&lt;/dfx:PromiseQuantityShort&gt;&lt;dfx:LateDate..Val.ue=.&quot; [0./1 5./2007&quot;&gt;&lt;/dfx:LateDa.te&gt; 201017576 &lt;/dfx:PromiseIn formation〉 &lt;/dfx:StrategyStepResult&gt; As indicated above, the report allocation shortage step provides any remaining provisioning_ that is still not consumed but can be used after certain mobile allocation steps. It also provides a specific mobile allocation step that will be added to the on-time commitment or late commitment ^ Please note that it only provides the mobile allocation step of 'to a s.eller' information, and does not provide 'from_seller' information, for example, here It provides: For Art FGl::SKU..:Locl, the number of 10 units' is still available at a certain seller, but needs to be assigned to Sl::Level2 to improve the late promise. Therefore, in general, after the proposed mobile allocation step, 50 units of the 10th order and 10 units of the 15th unit can be provided. In addition, 'the final commitment date is assembled and shows all the late commitments. Therefore, a commitment of 60 units on the 15th day is provided. Continue with this example 'Next Step Report ATP shortage is for late and shorter project execution from the previous step, the project is again 170 units, ❿ Result: On a time_qty 170 late_qty 0 late__date --- shortqty 0 • ATP selection Number -1

Atp Qty Needed 170 For Product FGl::SKU::Locl on

ATP Bucket Start Date 07-10-0 8 Is-On-Time TRUE ATP Selection Number -2

Atp Qty Needed 170 For Product AltFGl ::SKU::Locl on

ATP Bucket Start Date 07-10-08 Is_On-Time TRUE ATP selection number -3 . . . - ... . ............................... ' .. . . .. 42 201017576

Atp Qty Needed 180 For Product Int2::SKU::Locl on ATP Bucket Start Date 07-1 0-06 Is_On_Time TRUE

Atp Qty Needed 180 For Product Inti: :SRU: :Locl on '

ATP Bucket Start Date 07-10-06 Is_On_Time TRUE

Atp Qty Needed 180 For Product CaplFGl: W1: :RES: :Loc 1 on ATP Bucket Start Date 07-10-06 Is On Time TRUE ATP Selection Number_4

Atp Qty Needed 180 For Product AltInt2::SKU::Locl on ATP Bucket Start Date 07-10-06 Is_On_Time TRUE

Atp Qty Needed 180 For Product Inti: :SKU::Locl on ATP Bucket Start Date 07-10-06 Is_On_Time TRUE

Atp Qty Needed 180 For Product

CaplFGl :W1 ::RES::Locl on ATP Bucket Start Date 07-10-06 Is_On_Time TRUE ATP Select Number -5

Atp Qty Needed 201 For Product Comp4::SKU::Locl on ATP Bucket Start Date 07-10-01 Is_On_Time TRUE

Atp Qty Needed 201 For Product Comp3 ::SKU: :Loc 1 on ATP Bucket Start Date 07-10-01 Is_On_Time TRUE

Atp Qty Needed 201 For Product

CaplAltInt2: Wl::RES::Locl on ATP Bucket Start Date 07-10-01 Is_On_Time TRUE

Atp Qty Needed 180 For Product Intl::SKU::Locl on . - .- . - ........... .... : 43 201017576

ATP Bucket Start Date 07-10-06 Is_On_Time TRUE

Atp Qty Needed 180 For Product . .- .... ....

CaplFGl: W1::RES::Locl on ATP Bucket Start Date . . . . . .. ... . . . . . 07-10-06 Is—On_Time TRUE ΛΤΡSelect Number-6

Atp Qty Needed 180 For Product Int2::SKU::Locl on ATP Bucket Start Date 07-10-06 Is_On_Time TRUE

Atp Qty Needed 1 80 For Product Altlntl ::SKU::Locl on ATP Bucket Start Date 07-10-06 Is_On_Time TRUE

Atp Qty Needed 180 For Product

Cap 1FG1: W1: :RES: :Locl on ATP Bucket Start Date 07-10-06 Is On Time TRUE ATP Selection Number-7

Atp Qty Needed 180 For Product AltInt2::SKU: :Locl on '

ATP Bucket Start Date 07-10-06 Is_On_Time TRUE

Atp Qty Needed 180 For Product Altlntl ::SKU::Locl on ATP Bucket Start Date 07-10-06 Is_On_Time TRUE

Atp Qty Needed 180 For Product

Cap 1 FG1 : W1: :RES: :Loc 1 on ATP Bucket Start Date . .. .......... . 07-10-06 Is_On_Time TRUE ATP Selection Number - 8

Atp Qty Needed 201 For Product Comp4:;SKU::Locl on

ATP Bucket Start Date 07-10-01 Is_On_Time TRUE . ' . . . .

Atp Qty Needed 201 For Product Comp3 :: SKU: :Loc 1 on ' ...... ' ..... ......... ... . . . ..... . . . . . . :.. ....... . . . . 44 201017576

ATP Bucket Start Date 07-10-01 Is_On_Time TRUE

Atp Qty Needed 201 For.. Product

❹

CaplAltlnt2:W1::RES::Locl on ATP Bucket Start Date 07-10-01 Is_On_Time TRUE

Atp Qty Needed 180 For Product Altlntl ::SKU::Locl on ATP Bucket Start Date 07-10-06 Is_On_Time TRUE

Atp Qty Needed 180 For Product

CaplFGl :W1 ::RES::Locl on ATP Bucket Start Date 07-10-06 Is_On_Time The TRUE API output is as follows: &lt;dfx:StrategyStepResult&gt;&lt;dfx:ATPReport&gt;&lt;dfx: ATP Shortage Option〉 &lt;dfx: ATPShortageRequirement&gt ; &lt;dfx:Product&gt; . ' . ' ·. &lt;dfx:Item Value = &quot;FGl&quot;&gt;&lt;/dfx:Item&gt;&lt;dfx:ProductLevel

Value = &quot;SKU&quot;&gt;&lt;/dfx:ProductLevel&gt; ... ...... . . . . . &lt;dfx:ProductLo cation · . ' ' . . . ........ ..

Value = &quot;Loc 1 &quot;&gt;&lt;/dfx:ProductLocation&gt; Faint . . . . &lt;/dfx:Product&gt;&lt;dfx:Seller&gt;&lt;dfx:SellerNameValue=&quot;S 1 ,,&gt;&lt;/dfx:SellerName&gt;&lt;dfx:SellerLevel . ' . ....-:. ... .. .... . .... .... .. .. . .: ... ...................................................................................... 45 201017576

Value = &quot;Level2&quot;&gt;&lt;/dfx:SellerLevel&gt;&lt;/dfx:Seller&gt;&lt;dfx:ATPBucket&gt;&lt;dfx: StartDate

Value=&quot;10/08/2007&quot;&gt;&lt;/dfx:StartDate&gt;&lt;dfx:EndDate

Value=&quot;l 0/09/2007&quot;&gt;&lt;/dfx:EndDate&gt;&lt;/dfx: ATPBucket> &lt;dfx: Short age Qty Value=&quot;170&quot;&gt;&lt;/dfx:ShortageQty&gt;&lt;;dfx:OnTime Value = &quot;TRUE&quot;&gt;&lt;/dfx:OnTime&gt;&lt;/dfx: ATP Short ageRequirement&gt;&lt;/dfx: ATP Shortage Option&gt;&lt;dfx: ATP ShortageOption&gt;&lt;dfx:ATPShortageRequirement&gt;; ❿ &lt;dfx:Product&gt;&lt;dfx:Item Value = &quot;AltFGr'x/dfx:Item&gt; * &lt;dfx:ProductLevel

Value = "SKU"&gt;&lt;/dfx:ProductLevel&gt;&lt;dfx:ProductLocation Value = &quot;Locl&quot;&gt;&lt;/dfx:ProductLocation&gt;&lt;/dfx:Product&gt;&lt;dfx:Seller&gt;&lt;dfx :SellerName Value = &quot;Sl&quot;&gt;&lt;/dfx:SellerName&gt; 46 201017576 &lt;dfx: SellerLevel

Value=&quot;Level2&quot;&gt;&lt;/dfx :SellerLevel&gt;&lt;/dfx:Seller〉&lt;dfx:ATPBucket&gt;&lt;dfx: StartDate

Value = &quot;10/0 8/2007&quot;&gt;&lt;/dfx:StartDate&gt;&lt;dfx:EndDate

Value=&quot;10/09/200 7&quot;&gt;&lt;/dfx:EndDate&gt;See&lt;/dfx: ATPBucket> &lt;dfx: Short ageQty Value=&quot;170&quot;&gt;&lt;/dfx:ShortageQty&gt;&lt;dfx:OnTime Value = &quot;TRUE&quot;&gt;&lt;/dfx:OnTime&gt;&lt;/dfx: ATP Short ageRequirement&gt;&lt;/dfx: ATP ShortageOption&gt;&lt;dfx:ATPShortageOption&gt; ❹ &lt;dfx: ATP Shortage Re Queryment&gt;&lt;dfx:Product&gt; . &lt;dfx:Item Value = &quot;Int2&quot;&gt;&lt;/dfx:Item&gt; - &lt;dfx:Pro duct Level

Value = &quot;SKU&quot;&gt;&lt;/dfx:ProductLevel&gt;&lt;dfx:ProductLo cation Value=&quot;Locl&quot;&gt;&lt;/dfx:ProductLocation&gt;&lt;/dfx:Product&gt;&lt;dfx:Seller&gt; 47 201017576 &lt;dfx:SellerName Value = &quot;S 1 &quot;&gt;&lt;/dfx:SellerName&gt;&lt;dfx:SellerLevel

Value = &quot;Level2&quot;&gt;&lt;/dfx:SellerLevel&gt;&lt;/dfx: Seller〉 &lt;dfx: ATPBucket&gt;&lt;dfx: StartDate

Value=&quot;10/06/2007&quot;&gt;&lt;/dfx:StartDate&gt;&lt;dfx:EndDate

Value=H10/07/2007&quot;&gt;&lt;/dfx:EndDate&gt;&lt;/dfx:ATPBucket&gt;&lt;dfx: Shortage Qty Value=&quot; 1 8 0&quot;&gt;&lt;/dfx: Shortage Qty&gt;&lt; Dfx:OnTime Value=&quot;TRUE&quot;&gt;&lt;/dfx:OnTime&gt;&lt;/dfx: ATP Short ageRequirement&gt;&lt;dfx: ATP Short ageRequirement&gt;&lt;dfx:Product&gt;&lt;dfx:ItemValue=&quot;Inti”&gt;&lt;/dfx:Item〉&lt;dfx: Product Level Valuer&quot;SKU&quot;&gt;&lt;/dfx: Pro ductLevel&gt;&lt;dfx:ProductLocation Value = &quot;Locl&quot;&gt;&lt;/dfx:ProductLocation&gt ; &lt;/dfx :Product&gt;&lt;dfx:Seller&gt;&lt;dfx:SellerName Value = &quot;Sl&quot;&gt;&lt;/dfx:SellerName&gt; 48 201017576 &lt;dfx: SellerLevel

Value = &quot;Level2&quot;&gt;&lt;/dfx:SellerLevel&gt;&lt;/dfx: Seller〉 &lt;dfx: ATPBucket&gt;&lt;dfx: StartDate

Value = &quot; 10/06/200 7&quot;&gt;&lt;/dfx:StartDate&gt;&lt;dfx:EndDate

Value = &quot;10/07/2007&quot;&gt;&lt;/dfx:EndDate&gt;See&lt;/dfx:ATPBucket&gt;&lt;dfx: Short age Qty Value = &quot;180&quot;&gt;&lt;/dfx:ShortageQty&gt;&lt;dfx:OnTimeValue=&quot;TRUE&quot;&gt;&lt;/dfx:OnTime&gt;&lt;/dfx:ATPShortageRequirement&gt;&lt;dfx:ATPShortageRequirement&gt;&lt;dfx:Product&gt; ❹ &lt;dfx:Item Value = &quot;CaplFGl &quot ;&gt;&lt;/dfx:Item&gt;&lt;dfx:ProductLevel * Value = &quot;RES &quot;&gt;&lt;/dfx:ProductLevel&gt; - &lt;dfx:ProductLocation

Value = &quot;Locl&quot;&gt;&lt;/dfx:ProductLocation&gt;&lt;dfx: WorkcenterName Value = &quot; W1 &quot;&gt;&lt;/dfx: WorkcenterName&gt;&lt;/dfx:Product&gt;&lt;dfx: Seller〉 49 201017576 &lt;dfx:SellerName Value = &quot;Sl M&gt;&lt;/dfx:SellerName&gt;&lt;dfx: SellerLevel

Value=&quot;Level2,,x/dfx:SellerLevel&gt;&lt;/dfx: Seller〉 &lt;dfx: ATP Bucket〉 &lt;dfx: StartDate

Value = &quot;10/06/200 7&quot;&gt;&lt;/dfx:StartDate&gt;&lt;dfx:EndDate Art

Value = &quot;10/07/2007&quot;&gt;&lt;/dfx:EndDate&gt;&lt;/dfx:ATPBucket&gt;&lt;dfx: Short age Qty Value=&quot; 1 80 &quot;&gt;&lt;/dfx: Shortage Qty&gt;&lt;dfx:OnTime Value = &quot;TRUE&quot;〉&lt;/dfx:OnTime&gt;&lt;/dfx:ATPShortageRequirement&gt;&lt;/dfx: ATP Short age Option> 参&lt;dfx: ATPShortageOption&gt;&lt;dfx: ATP ShortageRe quirement&gt;&lt;dfx:Product&gt;&lt;dfx:ItemValuer&quot;Altlnt2&quot;&gt;&lt;/dfx:Item&gt;&lt;dfx:ProductLevel Value = &quot;SKU&quot;&gt;&lt;/dfx:ProductLevel&gt; 〈dfxrProduciLocation Value = &quot;Locl&quot;x/dfx:ProductLocation&gt;&lt;/dfx:Product&gt; 50 201017576 &lt;dfx: Seller&gt;&lt;dfx:SellerNameValue=&quot;Sl,'x/dfx:SellerName&gt;&lt;dfx: Seller Lev El

Value = &quot;Level2&quot;&gt;&lt;/dfx:SellerLevel&gt;&lt;/dfx:Seller&gt;&lt;dfx:ATPBucket&gt;&lt;dfx: StartDate

Value = &quot;10/06/2007&quot;&gt;&lt;/dfx:StartDate&gt; See &lt;dfx:EndDate

Value = ,,10/07/2007&quot;x/dfx:EndDate&gt;&lt;/dfx: ATP Bucket〉 &lt;dfx: Shortage Qty Value = "180&quot;&gt;&lt;/dfx:ShortageQty&gt;&lt;dfx:OnTime Value = &quot;TRUE&quot;&gt;&lt;/dfx:OnTime&gt;&lt;/dfx: ATP Shortage Requirement> ❿ &lt;dfx: ATP Short ageRe quirement&gt;&lt;dfx:Product&gt; * &lt;dfx:Item Value = &quot; Intl &quot;&gt;&lt;/dfx:Item&gt; - &lt;dfx:ProductLevel

Value = &quot;SKU&quot;&gt;&lt;/dfx:ProductLevel&gt;&lt;dfx:ProductLocation Value = &quot;Locl,'x/dfx:ProductLocation&gt;&lt;/dfx:Product&gt;&lt;dfx:Seller&gt; 51 201017576 &lt; Dfx: SellerName Value = &quot;S 1 &quot;&gt;&lt;/dfx:SellerName&gt;&lt;dfx: SellerLevel

Value = &quot;Level2&quot;x/dfx:SellerLevel&gt;&lt;/dfx: Seller〉 &lt;dfx: ATPBucket&gt;&lt;dfx: StartDate

Value = &quot; 1 0/06/200 7&quot;&gt;&lt;/dfx: StartDate&gt;&lt;dfx:EndDate

Value = &quot;10/07/2007&quot;&gt;&lt;/dfx:EndDate&gt;&lt;/dfx:ATPBucket&gt;&lt;dfx: Short age Qty Value = &quot;180&quot;&gt;&lt;/dfx:ShortageQty&gt;&lt; Dfx:OnTime Value = &quot;TRUE&quot;&gt;&lt;/dfx:OnTime&gt;&lt;/dfx: ATP Short age Requirement> References&lt;dfx: ATP ShortageRequirement&gt;&lt;dfx:Product&gt;&lt;dfx:Item Value = &quot;CaplFGl &quot;&gt;&lt;/dfx:Item&gt;&lt;dfx:ProductLevel Value = &quot;RES &quot;&gt;&lt;/dfx: Pro duct Level &gt;&lt;dfx:ProductLocation Value = &quot;Loc 1 &quot;&gt;&lt;/dfx:ProductLocation&gt;&lt;dfx: WorkcenterName Value = &quot; W1 &quot;&gt;&lt;/dfx: WorkcenterName&gt; 52 201017576 &lt;/dfx:Product&gt;&lt;dfx:Seller&gt;&lt;dfx :SellerName Value = &quot;Sl&quot;&gt;&lt;/dfx:SellerName&gt;&lt;dfx:SellerLevel

Value = &quot;Level2 &quot;&gt;&lt;/dfx: SellerLevel&gt;&lt;/dfx: Seller〉 &lt;dfx: ATP Buck et&gt;

&lt;dfx: StartDate

Value=&quot; 1 0/06/200 7 &quot;&gt;&lt;/dfx: StartDate&gt;&lt;dfx:EndDate

Value=&quot;10/07/2007&quot;&gt;&lt;/dfx:EndDate&gt;&lt;/dfx: ATPBucket> &lt;dfx: Short age Qty Value = &quot; 1 80&quot;&gt;&lt;/dfx:ShortageQty&gt;&lt;dfx:OnTime Value = &quot;TRUE&quot;&gt;&lt;/dfx:OnTime&gt;‘&lt;/dfx:ATPShortageRequirement&gt;&lt;/dfx: ATP Shortage Option〉 &lt;dfx: ATP Short age Option&gt; - &lt; Dfx: ATPShortageRequirement&gt;&lt;dfx:Product&gt;&lt;dfx:ItemValue=:&quot;Comp4&quot;&gt;&lt;/dfx:Item&gt;&lt;dfx:ProduciLevel Value = &quot;SKU&quot;&gt;&lt;/dfx:ProductLevel&gt ; &lt;dfx:ProductLocation 53 201017576

Value = &quot;Locl &quot;&gt;&lt;/dfx:ProductLocation&gt;&lt;/dfx:Product&gt;&lt;dfx: Seller〉 &lt;dfx:SellerName Value = &quot;S 1 &quot;&gt;&lt;/dfx:SellerName&gt ; &lt;dfx: SellerLevel

Value = &quot;Level2&quot;&gt;&lt;/dfx:SellerLevel&gt;&lt;/dfx: Seller〉 &lt;dfx: ATPBucket&gt;&lt;dfx:StartDate

Value = &quot;10/01/2007,,&gt;&lt;/dfx:StartDate&gt;&lt;dfx:EndDate

Value=&quot;10/02/2007&quot;&gt;&lt;/dfx:EndDate&gt;&lt;/dfx:ATPBucket&gt;&lt;dfx: Shortage Qty Value = &quot;201 &quot;&gt;&lt;/dfx: Short age Qty&gt;&&lt;dfx:OnTime Value = &quot;TRUE&quot;&gt;&lt;/dfx:OnTime&gt;&lt;/dfx:ATPShortageRequirement&gt;&lt;dfx: ATP ShortageRequirement&gt; - &lt;dfx:Product&gt;&lt;dfx:ItemValuer&quot;Comp3&quot;&gt;&lt;/dfx:Item&gt;&lt;dfx:ProductLevel Value = &quot;SKU&quot;&gt;&lt;/dfx:ProductLevel&gt;&lt;dfx:ProductLocation Value = &quot;Locl&quot;&gt;&lt;/dfx:ProductLocation&gt; 54 201017576 &lt;/dfx:Product&gt;&lt;dfx:Seller&gt;

Value: &lt;dfx:SellerName Value = &quot;S 1 &quot;&gt;&lt;/dfx:SellerName&gt;&lt;dfx:SellerLevel&quot;Level2&quot;x/dfx:SellerLevel&gt;&lt;/dfx: Seller〉 &lt;dfx: ATPBucket&gt;&lt;dfx: StartDate Value = &quot; 10/01/200 7 &quot;&gt;&lt;/dfx:StartDate&gt;&lt;dfx.:EndDate

Value=&quot; 1 0/02/200 7 &quot;&gt;&lt;/dfx:EndDate&gt;&lt;/dfx: ATP Bucket〉 &lt;dfx:ShortageQty

Value=&quot;201&quot;&gt;&lt;/dfx:ShortageQty&gt;&lt;dfx:OnTimeValue=&quot;TRUE&quot;&gt;&lt;/dfx:OnTime&gt;‘&lt;/dfx:ATPShortageRequirement&gt;&lt;dfx: ATPShortageRequirement〉 &lt;;dfx:Product&gt;&lt;dfx:Item Value = &quot;Capl Altlnt2 &quot;&gt;&lt;/dfx:Item&gt;&lt;dfx:ProductLevel Value = &quot;RES &quot;&gt;&lt;/dfx:ProductLevel&gt;&lt; Dfx:ProductLo cation Value = &quot;Locl&quot;x/dfx:ProductLocation&gt;&lt;dfx,WorkcenterName 55 201017576

Value = &quot; W1 &quot;&gt;&lt;/dfx: WorkcenterName&gt;&lt;/dfx:Product&gt;&lt;dfx:Seller&gt;&lt;dfx:SellerName Value = &quot;S 1 &quot;&gt;&lt;/dfx:SellerName&gt ; &lt;dfx:SellerLevel

Value = &quot;Level2&quot;&gt;&lt;/dfx:SellerLevel&gt;&lt;/dfx: Seller〉

&lt;dfx: ATPBucket&gt;&lt;dfx:StartDate

Value = &quot; 10/0 1/2007 &quot;&gt;&lt;/dfx:StartDate&gt;&lt;dfx:EndDate

Value=&quot;l 0/02/2007 &quot;&gt;&lt;/dfx:EndDate&gt;&lt;/dfx: ATPBucket> &lt;dfx: Short age Qty Value=&quot;201&quot;&gt;&lt;/dfx:ShortageQty&gt; ❿ &lt;dfx:OnTime Value = &quot;TRUE&quot;&gt;&lt;/dfx:OnTime&gt;&lt;/dfx: ATP ShortageRequirement&gt;&lt;dfx: ATP S ho rtageRe ment ment&gt;&lt;dfx:Product&gt;&lt;dfx: Item Value = &quot;Intl&quot;&gt;&lt;/dfx:Item&gt;&lt;dfx:ProductLevel Value = &quot;SKU&quot;&gt;&lt;/dfx:ProductLevel&gt;&lt;dfx:ProductLo cation Value=&quot;Locl&quot;&gt;&lt;/dfx:ProductLocation&gt; 56 201017576 &lt;/dfx:Product&gt;&lt;dfx:Seller&gt;&lt;dfx:SellerName Value = &quot;Sl &quot;&gt;&lt;/dfx:SellerName&gt;&lt;dfx: SellerLevel

Value = &quot;Level2&quot;&gt;&lt;/dfx:SellerLevel&gt;&lt;/dfx:Seller&gt;&lt;dfx:ATPBucket&gt; _ &lt;dfx: StartDate ❿

Value = ',10/06/2007&quot;&gt;&lt;/dfx:StartDate&gt;&lt;dfx:EndDate

Value=&quot;10/07/2007&quot;&gt;&lt;/dfx:EndDate&gt;&lt;/dfx: ATP Bucket〉 &lt;dfx: Short age Qty Value=&quot; 1 80&quot;&gt;&lt;/dfx:ShortageQty&gt;&lt;dfx:OnTimeValue==&&quot;TRUE&quot;&gt;&lt;/dfx:OnTime&gt;‘&lt;/dfx: ATP Short age Requirement&gt;&lt;dfx:ATPShortageRequirement&gt; ' &lt;dfx:Product&gt; - &lt;dfx: Item Value = &quot;CaplFGl &quot;&gt;&lt;/dfx:Item&gt;&lt;dfx:ProductLevel Value = &quot;RES &quot;&gt;&lt;/dfx: Pro duct L eve 1&gt;&lt;dfx:ProductLocation Value = &quot ;Loc 1 &quot;&gt;&lt;/dfx:ProductLocation&gt;&lt;dfx: WorkcenterName 57 201017576

Value = &quot; W1 &quot;&gt;&lt;/dfx: WorkcenterName&gt;&lt;/dfx:Product&gt;&lt;dfx:Seller&gt;&lt;dfx:SellerName Value = &quot;S 1 ”&gt;&lt;/dfx:SellerName&gt;&lt;dfx: SellerLevel

Value = &quot;Level2&quot;&gt;&lt;/dfx:SellerLevel&gt;&lt;/dfx: Seller〉 &lt;dfx: ATPBucket&gt; See &lt;dfx:StartDate

Value=&quot;10/06/2007&quot;&gt;&lt;/dfx:StartDate&gt;&lt;dfx:EndDate

Value=&quot;10/07/2007&quot;x/dfx:EndDate&gt;&lt;/dfx: ATPBucket> &lt;dfx: Short age Qty Value=&quot; 1 80&quot;&gt;&lt;/dfx:ShortageQty&gt;‘&lt;dfx :OnTime Value=&quot;TRUE&quot;&gt;&lt;/dfx:OnTime&gt;&lt;/dfx: ATP ShortageRequi remen t&gt; * &lt;/dfx: ATP Shortage Option&gt; ' &lt;dfx: ATP ShortageOption&gt;&lt;dfx: ATP ShortageRe quirement&gt;&lt;dfx:Product&gt;&lt;dfx:ItemValue = &quot;Int2&quot;&gt;&lt;/dfx:Item&gt;&lt;dfx:ProductLevelValue=&quot;SKU&quot;&gt;&lt;/dfx:ProductLevel&gt; 58 201017576 &lt;d fx: Pro ductL 〇cation

Value = &quot;Loc 1 &quot;&gt;&lt;/dfx:ProductLocation&gt;&lt;/dfx:Product&gt;&lt;dfx: Seller〉 &lt;dfx:SellerName Value=&quot; S1 &quot;&gt;&lt;/dfx: SellerName&gt ; &lt;dfx:SellerLevel

Value = &quot;Level2&quot;&gt;&lt;/dfx:SellerLevel&gt;&lt;/dfx:Seller〉&lt;dfx:ATPBucket&gt;&lt;dfx: StartDate

Value = &quot;10/06/2007&quot;&gt;&lt;/dfx:StartDate&gt;&lt;dfx:EndDate

Value=&quot;10/07/200 7&quot;&gt;&lt;/dfx:EndDate&gt;&lt;/dfx: ATP Bucket〉 &lt;dfx: Short age Qty Parameter Value = &quot;180&quot;&gt;&lt;/dfx:ShortageQty&gt ; &lt;dfx:OnTime Value=&quot;TRUE&quot;&gt;&lt;/dfx:OnTime&gt;&lt;/dfx:ATPShortageRequirement&gt;&lt;dfx:ATPShortageRequirement&gt;&lt;&lt;lfx: Product〉 &lt;dfx:Item Value = &quot ;AltIntl&quot;&gt;&lt;/dfx:Item&gt;&lt;dfx:ProductLevel

Value = &quot;SKU&quot;&gt;&lt;/dfx:ProductLevel&gt;&lt; d fx: Pr o due tLo cation 59 201017576

Value = &quot;Locl&quot;&gt;&lt;/dfx:ProductLocation&gt;&lt;/dfx:Product&gt;&lt;dfx:Seller&gt;&lt;dfx:SellerNameValue=&quot;S 1 &quot;&gt;&lt;/dfx:SellerName&gt;&lt;dfx:SellerLevel

Value = &quot;Level2&quot;&gt;&lt;/dfx:SellerLevel&gt;&lt;/dfx: Seller〉 &lt;dfx: ATPBucket&gt;&lt;dfx: StartDate

Value = &quot; 1 0/06/200 7 &quot;&gt;&lt;/dfx: StartDate&gt;&lt;dfx:EndDate

Value = &quot;10/07/2007&quot;&gt;&lt;/dfx:EndDate&gt;&lt;/dfx:ATPBucket&gt;&lt;dfx: Short age Qty Value = &quot; 1 80 &quot;&gt;&lt;/dfx: Shortage Qty&gt ; ❿ &lt;dfx:OnTime Value=&quot;TRUE&quot;&gt;&lt;/dfx:OnTime&gt;&lt;/dfx: ATP ShortageRequirement&gt;&lt;dfx: ATP ShortageRequirement&gt;&quot;&lt;dfx:Product&gt;&lt;dfx:Item Value = &quot;Cap 1FG1 &quot;&gt;&lt;/dfx:Item&gt;&lt;dfx:ProductLevel Value = &quot;RES&quot;&gt;&lt;/dfx:ProductLevel&gt;&lt;d fx: Pro ductLo cation Value = &quot;Locl&quot ;&gt;&lt;/dfx:ProductLocation&gt; 60 201017576 &lt;dfx: WorkcenterName

Value = &quot; W1 &quot;&gt;&lt;/dfx: WorkcenterName&gt;&lt;/dfx:Product&gt;&lt;dfx:Seller&gt;&lt;dfx:SellerName Value = "S 1 "&gt;&lt;/dfx:SellerName&gt;&lt;;dfx: SellerLevel

Value:&quot; Level 2 &quot;&gt;&lt;/dfx:SellerLevel&gt; _ &lt;/dfx: Seller〉

W &lt;dfx: ATP Buck et&gt;&lt;dfx: StartDate

Value=&quot;10/06/2007&quot;&gt;&lt;/dfx:StartDate&gt;&lt;dfx:EndDate

Value=&quot;10/07/2007,,&gt;&lt;/dfx:EndDate&gt;&lt;/dfx:ATPBucket&gt;&lt;dfx:Shortage.Qty. ❿ Value=M180,,&gt;&lt;/dfx:ShortageQty&gt;&lt;dfx:GnTimeValue=&quot;TRUE&quot;&gt;&lt;/dfx:OnTiiiie&gt; ·. ... &lt;/dfx: ATPShortageRequirement&gt; * &lt;/dfx: ATP Shortage Optiοn&gt;&lt;dfx:ATPShortageOption&gt;&lt; D.fx: ATPShortage.Requireme.nt&gt;&lt;dfx:Product&gt;&lt;dfx:Item Value = &quot;AltInt2&quot;&gt;&lt;/dfx:Item&gt;&lt;dfx:ProductLevel 201017576

Value = &quot;SKU&quot;&gt;&lt;/dfx:ProductLevel&gt;&lt;dfx:ProductLocation Value = &quot;Locl&quot;&gt;&lt;/dfx:ProductLocation&gt;&lt;/dfx:Product&gt;&lt;dfx:Seller&gt;&lt; Dfx: SellerName Value = &quot;Sl &quot;&gt;&lt;/dfx:SellerName&gt;&lt;dfx: SellerLevel

Value = &quot;Level2&quot;x/dfx: SellerLevel&gt; See &lt;/dfx: Seller〉 &lt;dfx: ATPBucket&gt;&lt;dfx: StartDate

Value = &quot;10/06/2007&quot;&gt;&lt;/dfx:StartDate&gt;&lt;dfx:EndDate

Value = &quot;10/07/2007&quot;&gt;&lt;/dfx:EndDate&gt;&lt;/dfx: ATP Bucket> Participate in &lt;dfx: Short age Qty

Value=&quot;180&quot;&gt;&lt;/dfx:ShortageQty&gt; * &lt;dfx:OnTime Value = &quot;TRUE&quot;&gt;&lt;/dfx:OnTime&gt; - &lt;/dfx: ATP ShortageRequirement&gt;&lt;dfx : ATP Short ageRequirement&gt;&lt;dfx:Product&gt;&lt;dfx:Item Value = &quot;AltIntl &quot;&gt;&lt;/dfx:Item&gt;&lt;dfx:ProductLevel Value = &quot;SKU&quot;&gt;&lt;/ Dfx:ProductLevel&gt; 62 201017576 &lt;dfx:ProductLocation Value = &quot;Locl&quot;&gt;&lt;/dfx:ProductLocation&gt;&lt;/dfx:Product&gt;&lt;dfx: Seller〉 &lt;dfx: SellerName Value = &quot; S 1 &quot;&gt;&lt;/dfx: SellerName&gt;&lt;dfx:SellerLevel

Value = &quot;Level2&quot;&gt;&lt;/dfx:SellerLevel&gt;&lt;/dfx:Seller> See &lt;dfx: ATPBucket&gt;&lt;dfx:StartDate

Value = &quot; 1 0/06/2 007 &quot;&gt;&lt;/dfx:StartDate&gt;&lt;dfx:EndDate

Va lue = &quot;1 0/07/2007 &quot;&gt;&lt;/dfx:EndD at e&gt;&lt;/dfx: ATPBucket> &lt;dfx: Short age Qty. ❿ Value = &quot; 1 80&quot;&gt;&lt ;/dfx:.ShortageQty&gt;&lt;dfx:OnTime Value = &quot;TRUE&quot;&gt;&lt;/dfx: On Time &gt; • &lt;/dfx: ATP Short age Requirement&gt; • &lt;dfx: ATPShortageRequirement&gt;&lt;Dfx:Product&gt;&lt;dfx:Item Value = &quot;CaplFGl&quot;&gt;&lt;/dfx:Item&gt;&lt;dfx:ProductLevel Value = &quot;RES &quot;&gt;&lt;/dfx:ProductLevel&gt;&lt;dfx:ProductLocation 63 201017576

Value = &quot;Locl&quot;x/dfx:ProductLocation&gt;&lt;dfx: WorkcenterName Value = &quot; W1 &quot;&gt;&lt;/dfx: WorkcenterName&gt;&lt;/dfx:Product&gt;&lt;dfx:Seller&gt;&lt;dfx: SellerName Value = &quot;S 1 &quot;&gt;&lt;/dfx:SellerName&gt;&lt;dfx:SellerLevel

Value = &quot;Level2&quot;&gt;&lt;/dfx:SellerLevel&gt; See &lt;/dfx: Seller〉 &lt;dfx: ATPBucket&gt;&lt;dfx: StartDate

Value = &quot; 1 0/06/2007&quot;&gt;&lt;/dfx:StartDate&gt;&lt;dfx:EndDate

Value = , 'l 0/07/2007&quot;&gt;&lt;/dfx:EndDate&gt;&lt;/dfx:ATPBucket&gt; See &lt;dfx: Short age Qty

Value = &quot; 1 80 &quot;&gt;&lt;/dfx: Short age Qty&gt;&lt;dfx:OnTime Value = &quot;TRUE&quot;&gt;&lt;/dfx:OnTime&gt; - &lt;/dfx: ATPShortageRequirement&gt;&lt;/ Dfx: ATP Shortage Option>. &lt;dfx: ATP Shortage Option> &lt;dfx: ATPShortageRequirement&gt;&lt;dfx:Product&gt;&lt;dfx:Item Value = &quot;Comp4&quot;&gt;&lt;/dfx:Item&gt; 64 201017576

Value &lt;dfx:ProductLevel &quot;SKU&quot;&gt;&lt;/dfx:ProductLevel&gt;

Value &lt;dfx: Pro ductLocation &quot;Loci ”&gt;&lt;/dfx:ProductLocation&gt;&lt;/dfx:Product&gt;&lt;dfx: Seller〉

&lt;dfx:SellerName Value = &quot;Sl &quot;&gt;&lt;/dfx: SellerName&gt;&lt;dfx:SellerLevel Value: &quot;Level2&quot;&gt;&lt;/dfx:SellerLevel&gt;&lt;/dfx: Seller〉 &lt; Dfx: ATP Bucket &gt;&lt;dfx:StartDate

Value = &quot; 10/0 1/2007 &quot;&gt;&lt;/dfx:StartDate&gt;&lt;dfx:EndDate

Value = &quot;10/02/2007&quot;&gt;&lt;/dfx:EndDate&gt; ❿. &lt;/dfx: ATPBucket&gt;&lt;dfx: Shortage Qty Value = &quot;201&quot;&gt;&lt;/dfx:ShortageQty&gt;&lt;dfx:OnTime Value = &quot;TRUE&quot;〉&lt;/dfx.:OnTime&gt;.· &lt;/dfx: ATPShortageRequirement&gt;&lt;dfx: ATP Short ageRe quire me nt&gt;&lt;dfx:Product&gt;&lt;dfx:Item Value = &quot;Comp3 &quot;&gt;&lt;/dfx:Item&gt;&lt;dfx:ProductLevel 65 201017576

Value = &quot;SKU&quot;&gt;&lt;/dfx:ProductLevel&gt;&lt;dfx:ProductLocation'

Value=&quot;Locl &quot;&gt;&lt;/dfx:ProductLocation&gt;&lt;/dfx:Product&gt;&lt;dfx:Seller&gt;&lt;dfx:SellerNameValue=&quot;S 1 &quot;&gt;&lt;/dfx:SellerName&gt ; &lt;dfx:SellerLevel

Value=&quot;Level2&quot;&gt;&lt;/dfx: SellerLevel&gt; ❹ &lt;/dfx: Seller〉. &lt;dfx: ATPBucket&gt;&lt;dfx:StartDate

Value=,'l 0/01/2007 &quot;&gt;&lt;/dfx:StartDate&gt;&lt;dfx:EndDate

Value = , '10/02/2007&quot;&gt;&lt;/dfx:EndDate&gt;&lt;/dfx: ATP Bucket> References &lt;dfx: Short age Qty

Value=&quot;201 &quot;&gt;&lt;/dfx: ShortageQty&gt; ..... .... .... * &lt;dfx:OnTime Value = &quot;TRUE&quot;&gt;&lt;/dfx:OnTime&gt; . . . * &lt;/dfx: ATP ShortageRequirement&gt; . . . . . -.. . . . . . . . . . . . . . . . . . . &quot;&lt;dfx:ATPShortageRequirement&gt;&lt;dfx:Product&gt; .. . : -. .. . &lt;dfx:Item Value=&quot;Cap 1 Altlnt2&quot;&gt;&lt;/dfx:ltem&gt;&lt;dfx:ProductLevel Value = &quot;RES&quot;&gt;&lt;/dfx:ProductLevel&gt; 66 201017576 &lt;d fx: Pro ductLo cation Value = &quot;Locl&quot;&gt;&lt;/dfx:ProductLocation&gt;&lt;dfx: WorkcenterName Value = &quot; W1 &quot;&gt;&lt;/dfx: WorkcenterName&gt;&lt;/dfx:Product&gt;&lt;dfx:Seller&gt;&lt;dfx: SellerName Value = &quot;Sl &quot;&gt;&lt;/dfx:SellerName&gt; _ &lt;dfx: SellerLevel ❿

Value = &quot;Level2&quot;x/dfx:SellerLevel&gt;&lt;/dfx:Seller〉&lt;dfx:ATPBucket&gt;&lt;dfx:StartDate

Value=&quot;10/01/2007&quot;&gt;&lt;/dfx:StartDate&gt;&lt;dfx:EndDate

Value = &quot;10/02/2007&quot;&gt;&lt;/dfx:EndDate&gt; ❿ &lt;/dfx: ATPBucket&gt;&lt;dfx: Shortage Qty Value = &quot;201&quot;&gt;&lt;/dfx:ShortageQty&gt;&lt; Dfx:OnTime Value = &quot;TRUE&quot;&gt;&lt;/dfx:OnTime&gt;&lt;/dfx: ATP ShortageRequirement&gt;&lt;dfx: ATP ShortageRequirement&gt;&lt;dfx:Product&gt;&lt;dfx:Item Value = &quot; Altlnt l &quot;&gt;&lt;/dfx:Item&gt;&lt;dfx:ProductLevel 67 201017576

Value = &quot;SKU&quot;&gt;&lt;/dfx:ProductLevel&gt;&lt;dfx:ProductLocationValue=&quot;Locl&quot;&gt;&lt;/dfx:ProductLocation&gt;&lt;/dfx:Product&gt;&lt;dfx:Seller&gt;&lt;dfx:SellerNameValue=&quot;SI&quot;&gt;&lt;/dfx:SellerName&gt;&lt;dfx: SellerLevel

Value = &quot;Level2&quot;&gt;&lt;/dfx:SellerLevel&gt;&lt;/dfx: Seller〉 &lt;dfx: ATPBucket&gt;&lt;dfx:StartDate

Value = &quot; 1 0/06/2 007 &quot;&gt;&lt;/dfx:StartDate&gt;&lt;dfx:EndDate

Value=H10/07/2007&quot;&gt;&lt;/dfx:EndDate&gt;&lt;/dfx:ATPBucket&gt; 10 &lt;dfx: Short age Qty

Value = &quot; 1 80 &quot;&gt;&lt;/dfx: Short age Qty&gt;&lt;dfx:OnTime Value = &quot;TRUE&quot;&gt;&lt;/dfx:OnTime&gt; - &lt;/dfx: ATPShortageRequirement&gt;&lt;dfx : ATP ShortageRequirement&gt;&lt;dfx:Product&gt;&lt;dfx:Item Value = &quot;CaplFGl&quot;&gt;&lt;/dfx:Item&gt;&lt;dfx:ProductLevel Value = &quot;RES &quot;&gt;&lt;/dfx:ProductLevel&gt ; 68 201017576 &lt;dfx: Pro ductLo cation Value=&quot;Loc 1 &quot;x/dfxrProductLocatioj^ &lt;dfx: Work cent erName Value=&quot; W1 &quot;&gt;&lt;/dfx: WorkcenterName^ &lt;/.dfx : Product〉 &lt;.dfx: Seller〉 &lt;dfx:SellerName Value=&quot;Sl&quot;&gt;&lt;/dfx:SellerName&gt;&lt;dfx: SellerLevel

Value=&quot;Level2&quot;&gt;&lt;/dfx:SellerLevel&gt;&lt;/dfx: Seller〉 &lt;dfx: ATPBucket&gt;&lt;dfx: StartDate

Value = &quot;10/06/2007&quot;x/dfx:StartDate&gt;&lt;dfx:EndDate

Value = M 10/07/2007&quot;&gt;&lt;/dfx:EndDate&gt; Refer to &lt;/dfx: ATPBucket&gt;&lt;dfx:ShortageQty.......; : .-- . - .-.- . * Value=&quot; 1 80M&gt;&lt;/dfx:ShortageQty&gt; - &lt;dfx:OnTime Value=&quot;TRUE&quot;&gt;&lt;/dfx:OnTime&gt; . . .. - ....... .. .. .. ... ..&lt;/dfx:ATPShortageRequiremen.t&gt;:...... &lt;/dfx: ATP Shortage Opt ion〉 &lt;/dfx: ATP Report> &lt;dfx: Strategy StepName&gt;&lt;dfx:Value&gt;REPORTATP_SHORTAGE&lt;/dfx:Value&gt; 69 201017576 &lt;/dfx:StrategyStepName&gt;&lt;dfx:PromiseInformati〇n&gt;&lt;dfx: Promise QuantityOnTime:

Value=&quot; 1 70&quot;&gt;&lt;/dfx:PromiseQuantityOnTime&gt;

&lt;dfx: Promise Quantity Late Value=&quot;0,'&gt;&lt;/dfx:PromiseQuantityLate&gt;&lt;dfx:PromiseQuantity Short Value=&quot;0&quot;&gt;&lt;/dfx:PromiseQuantityShort&gt;&lt;dfx:LateDate Value =&quot;- —.......&quot;&gt;&lt;/dfx:LateDate&gt;&lt;/dfx:PromiseInformation&gt;&lt;/dfx:StrategyStepResult&gt; As indicated above, the report ATP shortage step considers 'marked_buffer' The concept is to reduce the number of choices in the CTP scenario. Any product whose marke_d_buffer is set to 'true' is only considered to be available for purchasing more supplies. In this example, all products are tagged buffers, and thus the requirements reference implementation engine 212 provides all possible options for providing a promise. As indicated above, certain ATP selections involving the Inti's BOM are not shown (for example,

ATP with .C.ompl., .C..o:mp2, .Cap.lIntl., Int2' and Cap.l.FGl ... . . . . . . . ....... .. .. Select), because due to manufacturing lead time constraints can not provide on time: . : ' ' · ' · ', people 'no. Additionally or as an alternative to this example, Altlntl, Int2, and Altlnt2 are removed from the marked buffer area and the ATP shortage step is reported. The ATP selection is reduced as follows (the ATP selections shown above are 3, 4, 6, . . . . . . . . : . . . . ' 7 and 8 are eliminated)·· Result: .On_time_qty 1 7.0"ate_q.ty .'0 late"date ........- 70 201017576 shortqty 0 ATP selection number _ 1

Atp Qty Needed 170 For Product FGl::SKU::Locl on ATP Bucket Start Date 07-10-08 Is_On_Time TRUE ATP Selection Number_2

Atp Qty Needed 170 For Product AltFGl ::SKU::Locl on

ATP Bucket Start Date 07-10-08 Is_On_Time TRUE _ ATP selection number _3

W

Atp Qty Needed 201 For Product Comp4::SKU::Locl on ATP Bucket Start Date 07-10-01 Is_On_Time TRUE

Atp Qty Needed 201 For Product Comp3::SKU::Locl on ATP Bucket Start Date 07-10-01 Is On Time TRUE

Atp Qty Needed 201 For Product CaplAltInt2: Wl::RES::Locl on ATP Bucket Start Date 07-10-01 Is_On_Time TRUE

Atp Qty Needed 180 For Product Inti ::SKU::Locl on ATP Bucket Start Date 07-10-06 Is On Time TRUE

Atp ...::Qt.y: .Vv'N.eeded ' ......180 ' . For Product

CaplFGl:Wl::RES::Locl on ATP Bucket Start Date . . -.. . . ......... .... ....

07-10-06 Is On Time TRUE ._ . — Figure 5 illustrates an exemplary method of determining limits and resolving choices to resolve an order commitment exception. The method begins in step 502 'where the order commitment system 110 is from one Or the plurality of enterprises l2〇a-l2〇n or one or more customers 13 0a-130n receive the order commitment. At step 504, the order commitment system 110 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 201017576 t All or more supply chain restrictions ^ As discussed above, the demand fulfillment engine 212 or the order fulfillment system 11G may shorten or delay the order depending on the (four) limit. By way of example and not limitation, supply chain restrictions include (but are not limited to, less than the minimum quantity that can be shipped, the number of orders that are not a multiple of the shipment quantity, the order for the delivery request from a particular location, and for a particular mode of transportation Requested order.

At step 506, the order fulfillment system 11 determines which of the above defined limits are hard limits and may not be negotiable, and which of the above defined limits are flexible limits. At step 5〇8, the order commitment system ιι〇 produces - or multiple policy models. As discussed above, each policy model 222 includes one or more requirements implementation engines 212 that consider one or more policy changes in a defined sequence. By way of example and not limitation, the order fulfillment system 110 generates one or more policy models via the OIL document content. This can be done by the content of the document itself, since the strategy model is not required during the import, but the strategy model is only required during the planning or order commitment time. For example, using exemplary 〇IL document content to generate a strategy model '..' . . type and associated policy change hierarchy in the strategy model: .. ...... . . define My Strategy, ... . . . strategies.find_or_create(&quot;TestStrategy&quot;));

MyStrategy.set_description(',Test Strategy&quot;); · . . ..

My Strategy, changes. ity&quot;);

My Strategy, changes. find_or_create(&quot;Relax-Quote_Mul tiple&quot;); 72 201017576

MyStrategy.changeS.find_or_create(-Report_Allocation —Shortage&quot;);

MyStrategy.changes.find_〇r_create(-Report_Atp_Short age&quot;); Although an exemplary policy model is shown and described, embodiments may encompass any number of policy changes in the policy model (as discussed above), depending on the particular needs. At step 510, the order fulfillment system 11 selects a policy change from the defined sequence in the strategy model generated in step 5-8. The order commitment system 11 is then stepped at step 512 and, in particular, the demand implementation engine executes the selected strategy model and relaxes and optimizes the constraints, as discussed in detail above. At step 514, the order fulfillment system 11 determines whether to relax the limit (optimization limit) to solve the problem by providing a better commitment. If no, the method proceeds to step 516, otherwise the method proceeds to step 518. In step 516, the demand fulfillment engine 212 increments to the next policy change, and proceeds to step 510 with the subsequent method to select the next policy change from the defined sequence in the policy model generated in step 5-8. At step 518, the demand implementation engine 212 generates a cause and analysis report (discussed in more detail below) and stores the report data 226 in the repository 220 and the method ends. Additionally or alternatively, one or more users associated with one or more businesses 12a-120n and/or one or more customers 13a can be accessed to access the report material 226. In addition, FIG. 5 illustrates an embodiment of a method of determining a limit and parsing selection to resolve an order commitment exception, but 201017576 may make various changes to the method 500 without departing from the embodiment of the present invention. . Figure 6 illustrates an exemplary method for generating a cause and analyzing a report. The method begins in step 602 where the requirements implementation engine 212 generates a Create0rder application programming interface (API). For example, if the order is not fully committed on time, then the CreateOrder API promises, orders and returns later and shorter reasons. The external 'CreateOrder API' includes a label φ GiveReasonsReP〇rt that controls whether the demand implementation engine 212 calculates the cause, and a label ReasonsReportStrategy that specifies the name of the policy used to calculate the cause and resolve the report. At step 604, the requirements fulfillment engine 212 generates GetReas〇nRepc&gt; rt API' which obtains the reason and resolution report for the order that has been promised by the demand fulfillment engine 212. The GetReasonReport API assumes that the order is not in the report data 226 (memory) of the database 220. In addition,

The GetReasonReport API creates a UI workflow where the user can change some of the provisioning and distribution issues' and then recalls the cause and resolves the report to see the impact. In one embodiment, the GetReasonReport API is read-ahead, so, for example, this API is done to calculate new causes and parse reports. • The changes are not persistent in the requirements implementation engine 212. In addition or as an alternative. . . . . . . . . ' _ Generation ' GetReasonReport API uses the name of the strategy, any supply and / or distribution changes and improve the list of 5 goods structure (due to the demand realization engine 2U does not have a report The order in the data 226, so this API needs to be completed. -. . . . . . . . . . . Good order and its pegging. In addition, the requirements implementation engine 212 . . . . . . ' . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . In addition, the commitment to order is for reporting purposes only, and it is not durable within the requirements implementation engine 212. At step 606' demand implementation engine 212 generates

GetBatchReasonReport ΑΡΙ, its service is used with GetReas〇nsR ST • AP [same function] and in case the demand fulfillment engine 212 has an order in the report data 226 (in the allocation plan or batch order commitment scenario). In addition, the 'order ID is sufficient for the report to be obtained instead of the full order. At step 608, the demand implementation engine 212 generates a multiple Αρι, which commits the change to the demand fulfillment engine 2丨2 for the reason and parsing report. The GetReaS〇nReport API provides the supply and allocation changes required to evaluate choices and commit orders. Once the change is known and the change is persistent, the demand implementation engine 212 uses the multiple API to make the final change. For example, it has multiple inputs: 1. Mobile allocation information • 2. Update supply information 3. Improve order structure and commitment details... ..... . . ....... . . . The output of this API contains new commitment information, all of which have been submitted to the requirements to achieve the goal. .: . . . . . . . . . . . . . . . . In an embodiment the 'general situation multiple API may include implementation by requirements......... . . . . . . Any combination of APIs supported by the engine 212, as given below.. . . . . . . . . . . . 1. Generate an order management report _ Use any of these inputs: ': a. Order details - all such orders 〇 M report 201017576 b · OM report that has consumed the forecast details has been forecasted from all orders for consumption c. OM report consuming τρ detail goods 2. Generate allocation management report - period as input. 3. Generate a supply management report and period as input. All orders, products, sellers, start/end dates, products, sellers, and start/end dates that have been consumed by this AT P. 4· Cancellation of orders • Use of 5· Update supply - 〇太〇口, Seller, ATP The barrel and the quantity are updated as a supply, and are updated at the base seller and will be distributed to the seller provided in the input. 6.·Mobile Allocation 1 —_• Product, Seat 00, Seller, Forecast Barrel, and Add/Drop Count as inputs. ..., and then promised to order - a order structure and commitment details as a turn. 8. Generate a new order - an order structure as an input. The 2!2 BatchMultiple API' has the same function as the multiple Αρι, and is used in the case where the demand realization engine 2 12 has an order of the report data 226 1|7. Since the batch demand implementation engine m reads all orders from the database 22, the batch multiple API does not generate a new order in the demand implementation engine 212, although Figure 6 illustrates the reason for the cause and the method of parsing the report - the embodiment ' However, various changes can be made to the method 600 without departing from the scope of the embodiments of the invention. References to "one embodiment" or "an embodiment" in the above description means that the specific features, structures or characteristics described in connection with the embodiments are included in at least one embodiment of the invention. The appearances of the phrase "a" While the invention has been shown and described with respect to the embodiments of the embodiments of the present invention, it is understood that various modifications and changes in the above described embodiments may be made without departing from the spirit and scope of the embodiments of the invention. The present invention is not limited to the disclosed embodiments, but can be modified, modified and replaced without departing from the spirit and scope of the invention. BRIEF DESCRIPTION OF THE DRAWINGS The novel features of the present invention are described in the appended claims. The present invention, as well as its preferred modes of use, as well as further objects and advantages thereof, are best understood by reference to the accompanying drawings, in which: FIG. Sexual system; Figure 2 illustrates the order commitment system of Figure 1 in more detail in accordance with a more detailed embodiment; . . . . . . . . . . . . . . . An exemplary system is illustrated that includes two options for delivering a service 'including an air transportation mode and a road transportation mode; .... Figure 4 illustrates an exemplary embodiment in accordance with an embodiment. Sexual position; 77 201017576 Figure 5 illustrates an exemplary method of determining limitations and analytical choices to resolve anomalies in ordering; and Figure 6 illustrates an exemplary method for generating causes and analyzing reports.

[Main component symbol description] 100 System 110 Order Commitment System 120a Enterprise 120b Enterprise 120η Enterprise 130a Customer 130b Customer 130n Customer 140 Network 142 Communication Keyway - 144a Communication Keyway 144b Communication Keyway 144n Communication Link 146a Communication Link 146b Communication Link 146n Communication Link 210 Server 212 Requirements Implementation Engine 78 201017576 220 Database 222 Policy Model 224 Change Profile 226 Report Profile 300 System 310 Air Traffic Mode 312a Location 1 312b o Location 2 312c Location 3 314a Distribution Center 1 314b Distribution Center 2 320 Road transport mode 400 Location 402a Component 1 402b Component 2 ❹ 402c Component 3 402d Component 4 * 404a Buffer • 404b Buffer 406a Intermediate Capacity 1 406b Intermediate Capacity 2 408a Alternate Intermediate Component 408b Intermediate Component 1 408c Intermediate Component 2 201017576 Component 2 408d alternating 410 buffer 4 12 finished product capacity 414 finished product 1 4 1 6 alternate finished product

Claims (1)

201017576 VII. Patent application scope: ι_ A computer-implementable order commitment system, comprising: a database for storing order commitment information associated with one or more enterprises; a computer coupled to the database, The computer is configured to: receive an order commitment from the one or more enterprises; define one or more restrictions; generate one or more policy models including one or more policy changes; use the one or more Policy changes to execute the one or more policy models to relax the one or more restrictions; and generate a report of the later and shorter reasons for the order commitment, and store the generated report in the database in. Lu Ru applied for the system described in the first item of the patent scope, wherein the 1 = system is selected from the group consisting of: the order that is less than the delivery position of the needle-loadable special position, and the special-wheel mode And the order for the request. And for special A . . . ' . . . . . . . . . . . . . . . . . . . Wait for a red ^ 糸, 4, which is limited by the computer. . Whether or not the restriction is in the case of the computer, where the computer enters 4. The system as described in claim 1 of the patent scope 81 201017576 is configured to determine whether one of the one or more restrictions is elastic limit. 5. The system of claim 1 wherein the one or more policy changes are selected from the group consisting of: relaxing the minimum number; relaxing the quote multiple; relaxing the pack pack time (pick pack time) ; relax the maximum margin; relax the license delivery area; relax the license delivery source; relax the license delivery service; relax the license matching product; report the allocation shortage; and report the promise (available_t〇_pr〇mise) shortage. 6. The system of claim 1, wherein the computer is further configured to access the generated report for an order that has been promised by the order fulfillment system. . ' ' .... . ' . ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Wherein the computer enters -^(4) Μ such as - or a plurality of policy changes are submitted to the order commitment 82 201017576 8. A computer can be implemented to provide an order commitment system comprising the following steps: "One computer receives one from - Or an order fulfillment of multiple companies; one or more restrictions defined by the computer; one or more policy models containing one or more policy changes generated by the computer; (4) the computer uses the - or more policy changes to perform The one or more policy models to relax the one or more restrictions; and a report from the computer that produces the later and shorter reasons for the order commitment. And store the report of the production. 'The number of orders in which one or more of them are smaller than the maximum number that can be shipped' and the method for a specific operation. The method described in item 8 of the patent application is selected from the group consisting of the following: The quantity of tT goods, not the quantity shipped ^Orders requested for the order mode requested from a specific location delivery. . . . . . . . . . ^ ^如申(四)_118 Gu said the money, Wei-step two steps: decide the W 83 201017576 12. If the scope of the patent application is changed from the smallest Quantity; the method described in the item 'where the group consisting of one or more of the following: relaxing the quotation multiple; relaxing the selection time; relaxing the maximum edge; Relaxing the license delivery area; relaxing the license delivery source; relaxing the license delivery service; relaxing the license matching product; reporting the allocation shortage; and reporting the promised shortage. A. For the method described in item 8 of the patent application. Next step: For the report that has been produced by the order (4). Orders' 14. For example, please refer to the method of item 8 of the patent scope. Steps: Submit the - or multiple policy changes to the step including the following steps to the stock commitment system. The body's electrical touch readable body is configured to: J 5 . A soft media containing a system that enables an order fulfillment, which is executed using one or more computers to receive the order from one or more companies 201017576 Defining one or more restrictions; generating one or more policy models including one or more policy changes; using the one or more policy changes, executing the one or more policy models to relax the one or more Restrictions; and a report that produces the reason for the later and shorter of the order commitment and stores the resulting report. 16. The computer readable medium medium of claim 5, wherein the one or more restrictions are selected from the group consisting of: a quantity less than a minimum quantity that can be shipped, not a shipment Order quantities in multiples of the batch, orders placed for delivery from a specific location, and orders requested for a specific shipping mode. The computer readable medium of claim 15, wherein the software is further configured to determine whether any one of the one or more restrictions is a hard limit. . . . .. ... ........ . . . . ' ' - . . . . . . . . . . . . . The computer readable medium of claim 15 wherein the software is further configured to determine whether any one of the one or more restrictions is a flexible limit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The strategy change is selected from the following: the minimum number of small groups is relaxed; 201017576 to relax the quotation multiple; to relax the selection time; to relax the maximum margin; to relax the license delivery area; to relax the license delivery source; to relax the license delivery service; ❻ The report is divided into shortages; and · The report can promise a shortage. 20. The computer readable medium of claim 15, wherein the software is further configured to access the generated report for an order that has been promised by the order fulfillment system. The computer readable medium of clause 15, wherein the software is further configured to submit the one or more policy changes to the order fulfillment system.