You are on page 1of 6

LOG_LE_INTEGRATION: LE, SAP EWM Integration (new

)
Use As of SAP ECC 6.0, Enhancement Package 3 (SAP_APPL 603), the business function LE, Extended Warehouse Management Integration is available. With this business function, you can benefit from the tight integration of SAP ERP 6.0 and SAP EWM that offers you powerful functionality to increase flexibility for a best-in-class warehouse. For more information, see the following release note:

Extended Warehouse Management Integration
Effects on Customizing If you want to use this function, you must activate the business function LE, Extended Warehouse Management Integration (LOG_LE_INTEGRATION). See also For more information, see SAP Library under Business Function Sets and Business Functions --> Enterprise Business Functions --> Logistics --> Logistics Execution --> LE, Extended Warehouse Management Integration.

. the customer can add his own AACs. SAP EWM. where an SAP ERP is connected with an SAP EWM. Enhancement Package 3 (SAP_APPL 603). Account Assignment Determination (GI Consumption) Accounting information from an SAP ERP can be transferred to SAP EWM. In SAP EWM. without having to record a sales order or stock transport order first. o Kit to Order You can use a specific sales bill of materials (BOM) type / kit in a system landscape. In addition to the standard AACs in SAP ERP. enabling you to update the stocks of these materials using the goods issue posting of the delivery. you can use the Extended Warehouse Management Integration component to profit from the functional enhancements to the integration between SAP ERP and SAP Extended Warehouse Management (SAP EWM) in the following areas: Outbound Processing Inbound Processing Cross-Application Returns Processing (LE-IEW-OUT) (LE-IEW-INB) (LE-IEW-X) (LE-IEW-RET) Outbound Processing Batch Management Enhancements o Replication of batch selection criteria Instead of running a batch determination in SAP ERP.0. where batch search functionality is provided. you can also create packaging materials as additional items in outbound deliveries. You can create these deliveries for external and internal goods recipients directly in the warehouse. SAP ERP. SAP ERP is able to receive documentary batches from SAP EWM during goods receipt from external procurement and goods issue for customers for materials managed using documentary batches. which is capable of taking the warehouse layout into account. Support of the documentary batch functionality together with SAP EWM This enables the usage of documentary batches in an integrated way with SAP EWM.LOG_LE_INTEGRATION: EWM Integration (New) Use As of SAP ECC 6. SAP APO). and 'WBS Element'. Direct Outbound Delivery Direct outbound deliveries support unplanned outbound deliveries and direct sales in the warehouse. The kit-to-order process using a sales bill of materials in ERP only supports part of the scope that is developed for the kit-to-order process in the full Service Parts Management (SPM) system landscape (SAP CRM. 'Order'. it is now possible to replicate batch selection criteria to SAP EWM. which uses this information in the context of Goods Issue/Direct Sales/Warehouse-Internal Consumption to read the standard account assignment categories (AACs) 'Cost Center'.

However. The warehouse system may accept the change with a confirmation to update the delivery quantity in the ERP system. the purchasing data (purchasing quantity. the tolerance check no longer takes place during posting in SAP ERP. Creation of Expected Goods Receipt (EGR) Documents Goods receipt processing in SAP EWM is based on inbound delivery documents provided by SAP ERP.based o . one or more deliveries may be created and distributed to SAP EWM for further processing. Inbound Processing Goods Receipt from Production Inbound deliveries are created in SAP ERP at the time manufacturing order confirmation and distributed to SAP EWM. To support a similar check in SAP EWM. scheduling agreements. if the delivery update is rejected by SAP EWM. a scheduled report selects relevant manufacturing orders for which planned inbound deliveries should be created. where they are used primarily for inbound delivery creation and secondarily for workload preview purposes.Invoicing Before Goods Issue This process enables you to create invoices before the actual goods issue posting is done. There are two options: o Direct Billing Triggered from SAP EWM. Only inbound deliveries can be used for warehouse processing . a workflow item can be triggered in SAP ERP for a manual conflict resolution for the sales order. For long-term purchasing scenarios (schedule agreements). If the order item quantity falls below the delivery quantity. These inbound deliveries reflect the actual produced quantities and are used directly for putaway. Inbound deliveries are not created synchronously to production.putaway and goods receipt posting whereas expected goods receipts are excluded. These inbound deliveries usually represent the advanced shipping notifications (ASNs) provided by a supplier to announce that a goods issue has been performed at that supplier's warehouse. a change request is sent to the processing warehouse system (SAP EWM). a bill is created and printed in SAP ERP together with GTS information Wait for Billing Request You can create billing documents for multiple outbound deliveries in one run and print them. To support the SAP EWM goods receipt functions with data on expected goods receipts. the tolerance check . rather in SAP EWM during goods receipt at the gate. required documents are generated based on open purchase orders. tolerance data) is transferred to this system. Instead. These planned inbound deliveries are only persisted in SAP EWM. together with customs documents. o Delivery Change Request Following an (SD) Sales Order Quantity Decrease For an (SD) sales order item. and production orders. The order quantity remains open for changes. The tolerance check in SAP ERP is purchasing-document based. Goods Receipt Tolerances o o In the new release. and to indicate that the goods are on the way to the receiving warehouse.

after the outbound delivery has been confirmed. the actual serial numbers are transferred from SAP EWM to SAP ERP. the handling of predetermined serial numbers is supported. The data for the outbound delivery has to be stored. If the creation is permitted and activated. except for packaging material items. an inbound delivery with the attached EPC information is created automatically in SAP ERP. Therefore.leads to less helpful results for the latest schedules. where a value-added service order is created. There is a new authority check available for this functionality. These deliveries are then distributed to SAP EWM. the tolerance check is more appropriate at delivery level. This also applies in the case of a delivery split. For the outbound process. for scheduling agreements. the incoming data must be distributed to the EWM system Receive EPC from SAP EWM during goods issue (EPCs only at HU-header level) To support the sending of the ASN.on purchasing quantity . the EPC information is sent from SAP EWM to SAP ERP and copied to the IDoc. Cross-Application RFID The following processes are supported: o o Receive Advanced Shipping Notification (ASN) for inbound delivery (EPCs only at handling-unit (HU) level/item level) Replicate inbound delivery with EPC at HU-header/item level To support RFID enabling within SAP EWM for HUs. then production orders are used in SAP ERP as a basis for creating inbound and outbound deliveries. Depending on where the process will be started. Goods Receipt without Reference Document For those delivery items sent from an external warehouse where the reference document is missing. If the process is started manually in SAP EWM by the creation of a value-added service order. Kit to Stock The kit-to-stock process enables you to have a lean assembly process in a decentralized warehouse managed by SAP EWM. With each partial goods receipt. then the inbound and outbound deliveries will be replicated to SAP ERP. the purchase orders will be created by the system in the background. o o . a new purchase order for all items of this delivery with a missing predecessor document will be created. or manually in SAP EWM. Process of stock transport order (EPCs only at HU-header level during goods issue) Create inbound delivery from outbound delivery including EPC data at HU-header level. When a stock transport order is created and an outbound delivery for SAP EWM. the integration with SAP ERP will be realized differently: If the process is driven by a planning in SAP ERP or SAP APO. This process can either be driven by a planning in SAP ERP or SAP APO. Serial Number Handling Enhanced integration of serial number handling between SAP ERP and SAP EWM: o o For the inbound process. the traceability of serial numbers is enabled.

To reduce or avoid incorrect entries completely. Effects on Existing Data The new functions are available for new datasets only.Miscellaneous o Text handling enhancements Enables the bi-directional replication of inbound and outbound delivery header. Effects on Customizing To be able to use the Extended Warehouse Management Integration functions. with the following options: o Scrap predetermined quantity Scrap whole inventory with quantity retention constraint Scrap whole inventory o o GI time Enables maintenance and visibility of the actual GI time in the outbound delivery. This enables the integration with SAP SNC. as well as item texts between SAP ERP and SAP EWM. Catch Weight In SAP ERP. In a linked SAP EWM. you can use the definition of a tolerance group to check whether the values entered by a user for the logistic quantity and parallel quantity are valid. you can define a material as catch weight material. In an SAP ERP without Catch Weight Management. 2-step scrapping using MIGO SAP EWM supports a 2-step scrapping process. inventory management for these materials is done in a second unit of measure independently from the base unit of measure (for example. you must do the following: . which provides a Web interface for customers to pack and ship approved returns. 2-step stock transfers Enables the automatic creation of the inbound delivery upon goods issue of the outbound delivery. in the units of measure pieces and kilograms). Returns Processing You can now create a Return Material Authorization (RMA) for a return delivery. The second step is to finally post goods issue for the physical scrap container. It is now possible to trigger the two-step scrapping process using the transaction MIGO. but still holding the material in the inventory. Quantities in other units of measure are calculated using fixed conversion factors. inventory management only uses the base unit of measure. Effects on System Administration Enhanced monitoring of queues is required. The first step is to move the material to a physical scrap area such as a physical scrap container).

o o activate the business function LE. Extended Warehouse Management Integration (LOG_LE_INTEGRATION) check and maintain all activities listed in the Implementation Guide (IMG) under Logistics Execution -> Extended Warehouse Management Integration that are relevant for you. .