Use
In this section you will find information about how Bills of Material (BOMs) are transferred from SAP R/3 to the Production Process Model (PPM) of the SAP Advanced Planner and Optimizer (SAP APO). Features
| Question | Answer |
| Which BOM categories are supported? | Only material BOMs are supported. In the production version (SAP R/3) you can only enter alternatives for material BOMs. Technical place, equipment, document, sales order and project BOMs are not taken into account by the system. |
| How is the area of validity regulated? | Since only production versions are relevant for the transfer to SAP APO and production versions are plant-related, customer BOMs are not taken into account. |
| How is the validity period regulated? | With and without change management: BOMs can have different validity periods at both the header and item level. In SAP APO only one PPM is maintained per production version. During the transfer to SAP APO, the system selects the BOM that is currently valid for the production version. As of release PI2000.2, changes to BOMs are also transferred to SAP APO. The PPM is completely retransferred, although the PPM fields maintained in SAP APO are not changed. Planning jobs are written in SAP R/3 for changes to BOMs made with or without change numbers. You can update the PPM by using a report. The change statuses (change number in R/3) are implemented for the runtime object. The SAP R/3 parameter effectivity function is not supported for the PPM or for the runtime object. |
| What technical types are supported? | Since the BOM variant is to be given in the production version, both the multiple BOM and the variant BOM are integrated. For configurable materials use the super BOM in SAP R/3, which also contains object dependencies. The super BOM is not used in the PPM. You have to include the runtime object in the configuration. |
| How are BOM usage and item status integrated? | All BOM items relevant to production are taken into account. |
| Are subitems integrated? | In SAP R/3 no subitems from the BOM are incorporated into the production order. They are also not relevant to SAP APO. |
| Which item categories are relevant to the PPM? | Warehouse Is represented in SAP APO. Non-Warehouse Possible with and without material number: Without material number: Not relevant to SAP APO. In SAP R/3, when a production order is generated, so is a purchase requisition assigned to the production order (direct procurement). With material number: This depends upon whether the material is SAP APO relevant.
Prior to SAP R/3 Release 4.6 there is no direct procurement in the individual customer segment. The purchase requisition is only created during the Material Requirements Planning (MRP) run.  When using material number: Material should not be APO relevant. PM Structure Element Not relevant for SAP APO. Intra Not relevant for SAP APO. Document Not relevant for SAP APO. Class Not relevant for the PPM. Text Not relevant for SAP APO. |
| How is a co-product represented? | It is taken into account as an output node in the PPM. |
| Is there a recursiveness check? | No. |
| How is the alternative item or the alternative item group integrated? | The SAP R/3 functions for the alternative item or alternative item group are not available in SAP APO. SAP R/3 functions are used after the conversion of a planned order into a production order has been triggered (via the ATP check for the components in the production order). The provision dates for the components are calculated in SAP R/3 using scheduling. The deadlines for task list operations given by SAP APO are not affected by the scheduling. The production order created in SAP R/3 is transferred to SAP APO along with any changed components that may be relevant to SAP APO. |
| How is phase-out control integrated? | Simple Phase-Out Control Using SAP R/3 Material Master Record SAP R/3 phase-out control using the material master record is not available in SAP APO. You can use restricted versions of the SAP R/3 functions for phase-out control via the SAP APO Core Interface (CIF). If planning occurs in SAP APO and conversion of a planned order to a production order also occurs in SAP APO, you can use a customer exit (extension PPAPO004: "Conversion of Planned order from SAP APO: New BOM Explosion") to create a new BOM explosion for the production order. If the requirements planning run occurs in SAP R/3, phase-out control is already contained in the planning run and is taken into account during the conversion into a production order. The provision dates for the components are calculated in SAP R/3 using scheduling. The deadlines for task list operations given by SAP APO are not affected by the scheduling. The SAP R/3 phase-out control functions run when the production order has been installed. The production order created in SAP R/3 is transferred to SAP APO along with any changed components that may be relevant to SAP APO. Simple phase-out materials and their corresponding successor materials are represented in SAP R/3 according to the following scheme: In the SAP R/3 production order there are two reservations that only differ in the key field RSART and in the data fields Material Number and Requirements Quantity. There is a problem in that the key field RSART is not recognized in SAP APO. A basic synchronization of the simple phase-out materials is therefore not possible in SAP APO. A simple synchronization using BOM material is also not possible as both reservations have the same BOM information. As a consequence, there are the following problems during the transfer of orders from SAP R/3 to SAP APO. For synchronization using RSNUM and RSPOS as well as synchronization using BOM data, there are the same SAP APO input nodes for both SAP R/3 reservations, so the second record from SAP R/3 overwrites the SAP APO input nodes. This is dependent upon the sorting of the SAP R/3 reservation tables that have been transferred. This procedure is only correct if the second record from SAP R/3 contains the full requirements quantity. If the requirements quantity is split, only a part of the requirements quantity is transferred to the SAP APO reservation. If the second record does not contain a requirements quantity, the requirements quantity for the corresponding component in SAP APO is set to 0. The material number will also be written over with the material number of the second SAP R/3 reservation record. In CIF the following solution is implemented for SAP APO 3.0, which prevents inconsistencies appearing in both programs. Only the reservation with the full requirements quantity is transferred to SAP APO. If a redirection of requirement has already been carried out in SAP R/3 and phase-outs and their successors contain a requirements quantity, the full requirements quantity will be diverted to the successor in the CIF interface. In this way at least the procurement of the successor is guaranteed. The consequence of this is a possible surplus for the successor. The phase-out material is therefore only fully used if you create an order using the exact quantity of the phase-out material already available in stock. Multiple Phase-Out Control Using Phase-Out Control in the SAP R/3 BOM Item See above with restrictions under Simple Phase-Out Control. By using a new BOM explosion you can use the phase-out control functions in SAP R/3. |
| Is the dummy item implemented? | Dummy assemblies are used in SAP R/3 to enable the simple structuring of BOMs. You can see dummy assemblies as parentheses around a group of components that are often used in conjunction with each other. This significantly reduces the amount of administration needed for the master data. For changes to materials (for example, discontinued material) you only have to carry out the changes on one BOM. The changes have an effect on all BOMs that the dummy assemblies use. Dummy assemblies also facilitate component assignment since the components of a dummy assembly are assigned to the same operation. The same is true for the dummy assembly itself if you have not made an assignment for the components. During the BOM explosion in an SAP R/3 production order, the BOMs for dummy assemblies are also exploded. The components of the dummy assemblies become normal reservations, while the dummy assembly itself is transferred to the order as an unplanned effective reservation. The components of a dummy assembly are connected in a hierarchy with the superordinate assembly. For the transfer of the PPM from SAP R/3 to SAP APO the dummy assemblies are also exploded into components, although the dummy assemblies themselves are not transferred. No hierarchy information is assigned to the components of a dummy assembly. You have a flat structure in the SAP APO PPM. As a result there are significant differences in the handling of a SAP APO order in comparison to a SAP R/3 production order. It should be taken into account that a simple synchronization of components during the transfer of a SAP APO order to SAP R/3 is not possible if a dummy assembly appears several times in the BOM of an end product. Data that should be redetermined by SAP APO (for example, requirements quantity, plant, storage location) can therefore not be transferred to the SAP R/3 order. Since it will be possible in future to transfer components directly from SAP APO into an SAP R/3 production order, even if these do not exist in the assigned BOM in R/3, this would lead to additional, double reservations.  If the calculated value of the dummy assembly is smaller than the basic quantity of the dummy assembly BOM and the number of components in the dummy assembly is very small, the system produces the wrong values when calculating the required quantities for components in the dummy assembly. End product basic quantity: 1000 Required quantity dummy in end product: 120 Dummy assembly basic quantity: 1000 Required quantity component in dummy: 0.001 As decimal places are only given to three figures for quantities, the system gives a quantity of zero (on the basis that the result was 0.00012).Recommendation: In SAP R/3 you have to adjust the BOMs affected by increasing the base quantities and component quantities. |
| Is the distribution key implemented? | Yes, but it is hard-coded (linear distribution). |
| Is the lead-time offset implemented? | Yes, it is taken into account. |
| How is explosion type control integrated? | Using explosion type control you can deactivate the following settings in the material master record at the BOM level. BOM Explosion Switch Off Dummy Assembly: the BOMs in the dummy assembly are not exploded and the dummy assembly becomes relevant to requirements. This is taken into account in the PPM. Switch Off Planning: the components of the dummy assembly are not assigned dependent requirements in the requirements planning run if the planning strategies Planning Without Final Assembly and Planning with Planning Material are used. This is not taken into account. Switch off Direct Production: the BOM of a directly produced material is not exploded and therefore no order network is created. This creates a dependent requirement that is relevant to requirements planning. This is not taken into account, as an order network is not possible in SAP APO. From SAP R/3 Release 4.6A the explosion type control has been extended to include direct procurement so that direct procurement is suppressed if it has been activated using the special procurement key. For more see item type Non-Warehouse above. Switch Off Long Term Planning: no long term planning is carried out for the components of the dummy assembly. Not relevant for SAP APO.Dependent Requirements Indicator: corresponds to the entry in the material master record and overrides the one in the material master record. This indicator is not taken into account at the BOM level. |
| Is component and operation scrap taken into account? | See the entry on scrap in the section on Routing |
| Can the firm quantity be taken into account? | Yes. |
| How are components to be provided taken into account? | No material provision indicator is used in the PPM. Using subcontracting in SAP APO 3.0, materials with provision of materials or components can be procured externally. However, if this product can be manufactured in-house, the product has to refer back to the same PPM. If the number of components needed for production differs from the number of provision of material components, this situation cannot currently be depicted. |
| How is bulk material taken into account? | Bulk material is not relevant to SAP APO, it is available in the production order as a BOM item. |
| How is the production supply area taken into account? | This is not taken into account. |
| What units of measure are relevant for the components? | BOM components are always available in the base unit of measure in SAP APO, although they may be converted. |
沒有留言:
張貼留言