Toolkit for SAP consultants

IS-Automotive What are the use cases? What is the process flow? What are the functions involved? IS-Automotive Special companies (external service providers: ESPs) can manage holding stock and staging materials. A supplier and the manufacturer/customer can r educe warehouse stock, storage space and therefore storage costs . In this case, the stocks remain the property of the supplier up until they are staged. The ESP’s stock is then managed as supplier consignment stock in SAP . What are the use cases? Parts procured externally: the supplier stores the parts, that are required by the manufacturer, in the ESP’s storage location. The ESP delivers these to the manufacturer when they are required. Parts procured externally and parts returned to storage: the manufacturer returns parts, that have already been received from the supplier (or ESP), to the ESP’s storage location. Parts manufactured in-house: the manufacturer stores parts manufactured internally in the ESP’s storage location. W

To be added smth about SAP ARM  Reverse logistics focusing on organization level Returns from the customer: Free-of-Charge Deliveries Free-of-Charge Subsequent Deliveries Returns: Make a subsequent delivery of the goods, free of charge Credit Memo Request (If the customer complains that the price was miscalculated) Debit Memo Requests (If prices were calculated as too low) Invoice Correction Requests (price or quantity that should have been calculated) Refurbishment  Customer paid repair  Return to vendor Using a PO Using a QM notification Stock transfer return  ARM Determining what to do with a large volume of returned products is a complex process, and many retailers rely on manual, rule-based decisionmaking and inefficient processing, which can lead to a significant amount of waste.  Using returns technology automates the returns routing process by leveraging data-driven decision-making that sends returned inventory to the most profitable channel. This starts with a customer-facing

SAP EM is used to actually monitor the status of an end-to-end business process matching up the planned events and measurements with the actual events and measurements to uncover exceptions. Questions to answer Which processes do I want to track? Which objects of these processes should be monitored? Which events do I need to track within each process? Are my events date- and time-driven? For each event, check whether the event is expected to occur at a certain date or time. At the same time, also consider if the event is location- or partner-based. Where should the planned dates and times for my expected events come from? From where will the actual events be reported (e.g., IDoc, Legacy System, R/3)? Do I have any events that may occur but are not planned? Which rules should be applied to my process when events are or are not posted? Key Points Partners – See how your partners are performing and react to deviations to planned partners performing certain events in your pr

Basics  What are the BBD/SLED fields/Was sind die BBD/SLED-Felder? What are functions do we have with SLED?  When it is calculated?  What are the prerequisites?  How can I avoid recalculation of the expiration date in the case of goods movements? Additional information  2190893 - Shelf Life Expiration fields not available in MIGO 2915951 - SLED/BBD check on batch during goods issue 2281693 - Remaining shelf life check problem (Goods receipt for purchase order) Enhancements Basics  What are the BBD/SLED fields/Was sind die BBD/SLED-Felder? The last goods receipt date (LWEDT) is set during the receipt of the goods from production orders or external purchase orders. If the system is set to plant level, the date is also set during the receipt of the goods for a stock transport order. We can either maintain this date field in the batch master record manually or have it derived from the date of manufacture if a total shelf life has been entered in the master record of the batch material.

Content Field symbols  Modifying internal table records Appending to internal table Reading the internal table Read components of a structure using ABAP RTTS Declare generic field symbols Reading internal table using generic field symbol Change rows of the dynamic table  Data reference  Assigning existing data object to data reference Working with structures Working with internal tables Dynamically create data objects ABAP RTTS Read components of a structure using ABAP RTTS Check if a column exists in a table  Examples  Get a type of a data reference  itpfed (materials) Additional information https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=42965 Field symbols  Field symbol is a placeholder for data object, which points to the value present at the memory address of a data object. It does not reserve any physical memory space when we declare them. It only points to a data object at run time. Field symbols are of two types: Typed Field Symbol Generic Field Symbol Modifying inte