Abbreviations:SAP - Systems Applications & Products for data processing ABAP - Advanced Business Application Programming.

SAP ECC - SAP ERP Central Component. IDES - International Demo and Educational System IMG - Implementation Projects R/3 - ? is an integrated suite of applications designed to handle the data processing for large corporations. BAdI - Business Ad-Ins. RICEFW - Reports, Interfaces, Conversions, Extensions, Forms & Workflow. STO - Stock Transport Orders. RM - Receipt Management. PI - Process Integration. IDoc - Intermediate Document. BDC - Batch Data Communications session RFC - Remote Function Call DG - Data Governance Group ALE - Application Link Enabling Kanban - Similar to fixed storage bins in SAP PP. Sold units -->electronically-->whse-->replenished to whse. SAP AFS - SAP Apparel & Footwear Solutions ATP - Available-to-Promise APO - Advanced Planner and Optimizer P & D - Pick-up & Drop-off ARUN - Allocation RUN (AFS retail function). You must carry out the allocation run in the AFS system. A sales order requirement cannot be delivered until an allocation run has already released it. POS - Point of sale MAP - Merchandise and Assortment Planning. ASAP - AcceleratedSAP (Implementation process). Development system (sand box(diff. client) or crash and burn), QA or Test system and a Production system. Client Code Environment Description 100 Training 200 To review and approve business logic 300 Production System (end user work or day to day work) 500 Development activity 900 QA or Test client


• • • • •

• • •

Warehouse: To define, copy, delete, check warehouse number use code EC09 (tables T300, T300T, T320) o Number of warehouses assigned to a more than one storage location within a plant. o SAP with out WM function will go with only storage location. If SAP WM has been activated then that storage location has to be linked with warehouse and assign it to plant. o Warehouse Control Parameters: IMG * Logistics Execution * Warehouse Management * Master Data * Define control parameters for warehouse number (tables V_T3000) To check the company code use transaction code EC01 (table T001) To check about plant use transaction code EC02 (table T001W) To assign a plant to a company code use code OX18 (table T001K) To maintain storage location use code OX09 (table T001L) Print Control for WM: Use code OMLV o Print program per warehouse number is RLVSDR40. o Print control program for multiple processing is RLK0MM00 (Group deliveries), RLK0MM40 (Group of TR). To go SAP Enhancements use code CMOD. Debug: On screen go to option system on menu bar and select status, then double click to see the source code and select option test under program and debug. SAPScript Form (Reports) Transaction code SE71. o OPEN_FORM and CLOSE_FORM o START_FORM and END_FORM o WRITE_FORM Decentralized warehouse management refers to the use of SAP as a stand alone WMS system, with SAP (or another ERP system) as a separate core system. The two system communicate by using BAPIs for transactions or IDoc for master data. Goods movements are done through delivery notes from the core system to the stand-alone WMS. To define a storage type use menu path in customizing: Logistics Execution * Warehouse Management * Master Data * Define Storage Type (tables T331) Note no transaction code for this SAP uses Table view (SM30). o Standard Storage Type:Storage Type Description 001 High rack storage 002 Shelf storage 003 Open storage 004 Block storage (PkMS - Bulk storage) 005 Fixed bin storage 035 Packed Materials (Used in Near picking Bin putaway strategy) page 306 (SAP WM) 100 Production supply 110 Finished goods (pallets strategy)

• • • •

• •

• • • •

301 - 303 Raw/semi-finished 901 GR area for Production 902 GR area for external receipts 904 Returns 910 GI area general 911 GI area for cost center 912 GI area for customer order 914 GI area for production orders 915 Fixed bin picking area 916 Shipping area deliveries 918 Planned SU interim area Page 360. 999 Differences To define a storage section use menu path in customizing: Logistics Execution * Warehouse Management * Master Data * Define Storage section (tables T302, T302T) o Storage bins of certain capacities (volume or storage weight or item ABC classification ) are combined together as storage sections. Dynamic storage bins are created automatically by the system when goods receipts and goods issues are posted. Storage unit: If you also manage your stocks in the WM system with pallets or other loading equipment (wire baskets, metal containers, etc,.) you have to configure storage units for the relevant storage types. To define storage unit type use code OMM1 (T307, T307T) Storage Bin Type (2 character): is a grouping that can be assigned to storage bins of similar nature. Example: Bin Height One Meter. o Menu path: IMG * Logistics Execution * Warehouse Management * Master Data * Storage Bins * Define Storage Bin Types (tables T303). Storage Bin Structure: Code LS10 Storage Bin: To Create manually use code LS10N (tables LAGP) o Automatically create bins: Code LS10 and use the header menu and select Environment * Create Bins. o Block storage bins: use code LS08 o To display storage bin use code LS03N o Bin status report use code LX03 Transferring storage bins from legacy system to SAP:- Use web-link under favorites. You can use the RLPLAT00 program to transfer storage bins automatically
from a legacy system to the R/3 System.

Blocking reasons: Menu path: IMG * Logistics Execution * Warehouse Management * Master Data * Storage Bins * Define Blocking Reasons (tables T330, T330T). Empty Bins: Use code LX01 (got memory error with this code) Stock Category: Stock Category code Description Q Stock in quality control

• •

R Return stock S Blocked Stock Blank All available stock Quant: to display quant use LS23 (LQUA) Special Stock Indicator: Example Special stock number for E is 16 character long (10 sales order number + 6 character item number) Special Stock Indicator Description E Sales Order Stock K Consignment (Vendor) Q Project Stock M Returnable Transport Packaging (vendor) Batch Management: o Batch level can be determined at different levels:  Client level  Plant level  Material level o Number range object for this is BATCH_CTL. Transaction code is OMAD. o Two configuration steps can be carried out if the customer requires batch number assignment:  Internal batch number assignment, use code OMCZ.  For automatic numbering of batches on GR with account assignment - check book o Create Batch Record: Code MSC1N (tables MCHA) o Shelf-life functionality (SLED): code OMJ5 Data Extract: o SAP ---> External : By using Logical databases data extracted in ABAP program and send to external system. (see in page 322 in ABAP programming book).  Logical Databases: code SE36 o External ---> SAP : Using BDC session  Identifying screens in a transaction (On screen select system/status command on menu).  Building the BDC table  Submitting the BDC table in a batch or a single CALL TRANSACTION command. • Functions :- BDC_OPEN, BDC_INSERT, BDC_CLOSE Mobile Data Entry: o GUI: Small keypad, o Character-based devices:  RF devices for forklifts: 8 lines X 40 characters  Portable RF devices: 16 lines X 20 characters o Define Verification Profiles: Menu path: IMG * Logistics Execution * Mobile Data Entry * Verification Control * Define Profiles.

o Assign verification profiles: Menu path: IMG * Logistics Execution * Mobile Data Entry * Verification Control * Assign Verification Profiles to Goods Movements. o Define Bar Codes for Warehouse: Menu path: IMG * Logistics Execution * Mobile Data Entry * Bar Code * Assign Bar Code Types to Warehouses. o Maintaining Bar Code Specifications: Menu path: IMG * Logistics Execution * Mobile Data Entry * Bar Code * Maintain Bar Code Specification. o Defining the RF Queue: Menu path: IMG * Logistics Execution * Mobile Data Entry * RF Queue Management. o Adding a User for Mobile Data Entry: Use code LRFMD. o Logging on for Mobile Data Entry: Use code LM00. o Master Data:• Material Master: A material that will be stored in a warehouse will need the material master to be extended for the specific warehouse and storage type that it will be stored in. We may need to enter hazardous material information in warehouse section of the material master. Menu path: Logistics * Logistics Execution * Warehouse Management * Master Data * Material * Create o Transaction codes:  MM01 - Create new material master data  MM02 - Change existing material master data  MM03 - View existing material master data at current point in time  MM19 - view existing material master data as it was at a specified point in time  MM06 - Mark existing material master data o Material Type: Group of materials with similar attributes. code OMS2. Material Type Description CONT KANBAN Container DIEN Services ERSA Spare parts FERT Finished Good FHMI Production resources/tools HALB Semi-Finished Goods HAWA Trading goods HERS Manufacturer parts HIBE Operating Supplies IBAU Maintenance Assembly LEER Empties LEIH Returnable packaging NLAG Non-stock material PIPE Pipeline material ROH Raw Material VERP Packaging Material

o Message to IM: This field is activated in Material master when WM is decentralized. • Customer Master: Menu path: Logistics * Logistics Execution * Master Data * Partner * Customer o Transaction Codes:  VD01 - Create sales area data for a customer  XD01 - Create all data for a new customer  VD02 - Change sales area data for an existing customer  XD02 - Change all data for an existing customer  VD03 - View sales area data for an existing customer  XD03 - View all data for an existing customer  VD04 - List all changes of sales area data for an existing customer  XD04 - List all changes of all data for an existing customer  VD05 - Lock complete customer master or only specific sales areas of a customer for a delivery  VD06 - Mark a customer for deletion. • Vendor Master: Menu path: Logistics * Logistics Execution * Master Data * Partner * Vendor o Transaction Codes:  XK01 - Create vendor master data  XK02 - Change vendor master data  XK03 - View vendor master data • Batch Master: Menu path: Logistics * Materials Management * Master Data * Batch o Transaction Codes:  MSC1N - Create batch  MSC2N - Change batch  MSC3N - View batch  MSC4N - View all changes in batch master • Dangerous Goods Master: Menu path: Logistics * Environment, Health and Safety * Dangerous Goods Management * Dangerous Goods Master o Transaction Codes:  DGP1 - Create dangerous goods master record  DGP2 - Change dangerous goods master record  DGP3 - View dangerous goods master record  DGR1 - View all dangerous goods master records Purchase Orders:• To define, copy, delete, check sales organization use code EC04 (tables TVKO, TVKOT, TVKWZ) • Stock Transport Orders: Need to setup receiving plant a customer number via customizing.

o Path in customizing: Materials Management * Purchasing * Purchase Order * Setup Stock Transport Order * Define Shipping Data for Plants (tables T001W) o Path in customizing: Materials Management * Purchasing * Purchase Order * Setup Stock Transport Order * Assign Delivery type and checking rule (tables T161V) o Path in customizing: Materials Management * Purchasing * Purchase Order * Setup Stock Transport Order * Assign Document type, one-step procedure, under-delivery tolerance (tables T161W) o Cross-Company-Code STO: use code ME21N. • Delivery Document:• Create delivery document use transaction code VL01N. • Create delivery document (Collective Run) use transaction code VL10A. • • Business Ad-Ins (BAdI):o Overview LE_SHP_TAB_CUST_OVER  Filter include module: RVV50TOP  V50R_USEREXITS o Header LE_SHP_TAB_CUST_HEAD o Item LE_SHP_TAB_CUST_ITEM o Proc LE_SHP_DELIVERY_PROC  Include module: MV50AFZ1 • Delivery Type: Transaction code: OVLK (tables TVLK, TVLKT) Vendor/Delivery Type Description LF Delivery BV Cash sale NK Consignment fill-up NL Delivery for stock transport order LR Returns delivery • Item Category for deliveries: Transaction code: OVLP (tables TVLP) o If you create a delivery document with reference to a sales order, the item category is copied from the order to the delivery document. • Item Category Groups: Path in Customizing: Sales and Distribution * Sales * Sales Documents * Sales Document Item * Define Item Category Groups (tables TPTM, TPTMT) Item Category Group Description BANS Delivery (? for 3rd party also same) DIEN Service item LEER Empties LEIH Returnable packaging NORM Standard item VERP Packaging

Item Category Usages: Path in Customizing: Logistics Execution * Shipping * Deliveries * Define Item Category Usage (tables TVVW, TVVWT) Item Category Usage Description CHSP Batch split PACK Shipping unit TEXT Text item

• Receiving Process:GR/IB delivery process:-

• •

A GR into warehouse is triggered by one of two documents: o A TR from IM or production. o An IB delivery if HUM or external system is used. GR process has variations based on SUs (to improve the storage capacity utilization and the material flow, batch management) & HUs (to map a complete packaging-controlled logistics system) or both when mapping logistical processes in SAP system:o GR without SUM and HUM o GR with active SUM o GR with HUM o IB delivery with/without SUM o IB delivery with HUM GR for PO Without With Active With RF Solution in the SUM and SUM Active Standard System HUM HUM Post GR for PO MIGO MIGO Create TO for LT06 LT06 material document Confirm LT11/LT12 LT11/LT12 LM03/LM04 LT13 LM02
GR Process for PO with screen Transaction and Mobile Standard SAP Transactions

GR for Delivery

Without With Active With Active SUM and SUM HUM HUM Create delivery VL31N VL31N MIGO/VL3 1N GR for delivery VL32N VL32N VL32N Create TO for LT0F LT0F LT0F delivery LT03 LT03 LT03 GR for HU VL32N VL32N VL32N Create TO for HU LT0J LT0J LT0J LT09 LT09 LT09 Confirm TO LT11/LT12 LT11/LT12 LT11/LT12 LT13 LT13

RF Solution in the Standard System LM71 LM71 LM76 LM76 LM03/LM04 LM02

GR Process for Delivery with screen Transaction and Mobile Standard SAP Transactions

GR without SUM & HUM o In the standard SAP system, the mobile support is limited for this process. We can use LM03 - Putaway by TO or LM04 - Putaway by system guided to confirm TO. o Optimization option: scheduled the automatic TO creation as a job using report RLAUTA10 to optimize the procedure during TO creation without RF support. Because single material pallets/containers are not always delivered, in customizing we have set the TO split for each material. This allows differing destination storage types to be taken into account. To optimize the confirmation we have to activated and adjusted the barcode output of the TO number in the TO form (LVSTAEINZEL) using Transaction SE71 (SAPScript Form). You must print the TO in the GR confirmation, to do this adjust the print management in customizing of the WM system to your requirements. GR with Active SUM o Standard SAP system only offers the option of confirming TOs that have already been created. You can use mobile transaction LM03 and LM04. You can also use LM02 - Putaway by SU. o Optimization Options in the standard SAP system:  Must develop at least one new mobile transaction for the palleting and TO creation after the GR posting. For example, if you are working with upstream I-point storage types, you must develop a further new mobile transaction for creating the TO from the I-point into the warehouse. During the form adjustment, we first copied the form WESCHEINVERS3 (GR slip version 3) using code SE71 and set it to print barcode for material document number and item. In customizing, we then set the message determination for the message type WE03 (GR certificate version 3) with the new form.  Developing the new mobile transaction: In order to pallet the material into SUs using the printed material document and at the same time be able to create TOs for these SUs, we have developed a new mobile transaction, ZMAL1 in our example, whose function is similar to code LT06 (Create TO for material document).  In order to be able to post the SUs formed of the I-point storage type into the warehouse while mobile, we have also developed a new mobile code for this (ZMAL2 in the example) whose function resembles screen transaction LT09 (ID Point function for storage units). See on page 20 (Mobile). GR with active HUM o With active HUM the IB delivery process, It including the packaging, is performed. The GR via code MIGO thereby always only generates IB deliveries. IB delivery with/without SUM o We can divide the GR process into the following:  Create the IB delivery for the PO.

 Create TO for IB delivery.  Confirmation of TOs.  GR posting for delivery. o See page 24 (Mobile) for more details and optimization options. IB delivery with HUM: o Create the IB delivery for PO:  GR postings with code MIGO always only create one IB delivery.  To create IB delivery manually use code VL31N Or automatically via collective processing using report (RM06EANL). Or using EDI messages.  Packing in the HU:  EDI: they can transfer their packing data and HU numbers in the ASN.  Or automatic packing when the IB delivery is created by the IDoc (message type DESADV). There is no special function module with which you can create the batch automatically when the delivery is created.  Or if no EDI from vendor, you can optimize the delivery creation process by activating the automatic packing in the SD module when the delivery is created based on the set packing instructions.  Or last option to pack the delivery manually by using VL31N. o Create the TO for Putaway:  You can only create TOs through mobile transactions if the delivery is fully packed. Fully packed deliveries have 2 variants for the GR posting • Placement in storage before GR posting: When TO is created you can neither see nor change the palletization quantity, the load carrier, or the destination storage type and bin. GR Transaction Code By HU LM76 By Delivery LM71 By MS area LM72 By Shipment LM73 By All LM74 • Placement in storage after GR posting: Currently one transaction code available in standard system. GR Transaction Code By Delivery LM71 o Confirm the TO:  We use mobile Transaction code LM02  WM picking status of a delivery for TOs that have already been confirmed cannot be reset using code LT0G. While you can undo the GR using code VL09, all you can do is delete the delivery.

o Posting GR for Delivery:  Placement in storage before GR posting: • Creation of all TOs for deliveries must be completed when the TOs are confirmed. • When you create on confirm the TOs, you thus, in turn, first create negative quant for the HU in GR zone 902 (interim storage type). You clear these -ve quant with the GR posting. Only then is the material available. • In order to automate GR postings for deliveries, schedule the WS_MONITOR_INB_DEL_GDRC report as a job. o Placement in storage after GR posting:  The situation is different here, the material is in the freely available stock immediately after the GR posting through screen transaction VL32N. Unfortunately, there is no mobile transaction here that allows you to create a single TO for the HU, and that offers destination data for changing. Optimization options: o This approach provides for the development of the missing mobile transaction, which enables a single TO to be created for the HU. o In standard SAP system, the delivery must always be fully packed if you want to create mobile TOs. There is no mobile transaction in standard SAP that allows you to manually pack a delivery in sub quantities in HUs, and that then automatically creates a TO for the Putaway for the HU. We have first copied the form RT_CHECK_LIST (Count list for delivery) using code SE71 and set it in such a way that the material document and item are also output as a barcode. In customizing, we then set the message determination for the message type CHKL (Count list) with the new form. For HU label, we also set the message determination E128 (EAN 128 label) for all of our packaging material types for immediate printing on the user's printer. we also developed a new mobile transaction (here called ZMAL3), so that sub quantities of a delivery item are manually packed into HUs and TO is then automatically created for Putaway for the created HU. The rough structure of the transaction is as follows:  Delivery number and item is scanned on the first screen.  The data that is determined is then proposed on the second screen. The packing data can be overwritten here.  When you save the data, the transaction packs the material into an HU. The TO is created for Putaway with the created HU using the (L_TO_CREATE_MOVE_SU) function module.  The 3rd screen displays the most important data for the TO. IB delivery monitor: o use code VL06I o use code LT0F (Create TO for delivery) and press "Delivery Monitor Inb.Deliveries".  You can also see work flow under "Environment".

Display Material Document: use code MB03 Review of stock levels/Display of stock levels after GR: use code MMBE. GR without IM: Normally materials are receipted into a storage location, and that triggers a TR and TO in WM. However, there are materials in the warehouse that sometimes do not require a GR in IM, but are required for warehouse operations. Example: Packaging material, such as pallets and crates. These are used for material storage and shipment, but don't have to be GR into IM. o Create TO without source: use code LT01 with movement type 501. Putaway Strategies:• Stock placement control indicators in storage type:Putaway strategy Description Manual stock placement B Bulk storage C Open storage F Fixed bins I Addition to existing stock K Near picking bin L Next empty bin P Storage unit type • Destination bin change during confirm:- This indicator needs to be set in-order to change bin while confirming TO. • Mixed storage:- this can be set to allow different quants to be stored in a storage bin in this storage type. Mixed storage indicator Description Mixed storage is not allowed A SU with the same material B Same material, different batches and storage unit. Each storage unit can contain more than one batch of the same material. C A number of batches in one storage bin, only one material. However, it is not possible different batches in a single storage unit. X Any mixed storage without restrictions. • Capacity Check Method:Capacity Check Description Method indicator No check of capacity 1 Check of the maximum weight 2 Check based on palletization of SU type 3 Check of maximum qty per storage bin in a storage type. 4 Capacity usage check based on material 5 Capacity usage check based on SUT

• • •

• •

• •

Capacity usage check based on the sum of the material and the SU. • Assigned ID point storage type:- Any goods movements that do not have a specific storage bin in this storage type as their destination are first directed to the identification point. At this point the material is identified and a TO is generated for the transfer of the material into the correct storage type. Fixed-Bin Storage:- data that has been entered into the material master record for the material to be placed in stock. The material is stored in a single bin; i.e., a fixed bin. Open Storage:- When materials are stored in areas of open floor, where there are no racks or lines. Storage type is roughly divided into storage section, and the protocol is that one storage section is represented by one storage bin. o Note : Mixed storage and Addition to existing stock indicators are set. Next Empty Bin:- Note that other indicators are switched on for this strategy. The most significant is the storage section check indicator. Because the strategy is to find the next empty bin, further strategies can be used at the storage section and storage bin. This gives the warehouse staff a better idea of where the next bin will be located. This is not necessary, but is often used with the next empty bin strategy. o Display of empty bins use code LS04. o Cross-Line Stock Putaway:- Using the next empty bin putaway strategy can be problematic if the storage bins are selected only from one part or one side of the warehouse. So we need a search criteria for cross-line stock putaway strategy must be configured. Use code OMLM. Before we do this we need to understand bin structure. o Bin Structure: use code LS10. Bulk Storage (B):- here materials are stored in large quantities. Use code OMM4. o Storage type used is 004. Note other indicators used: SUT check active. and addition to stock. Near Picking Bin (K):- Storage type used is 035. T code used is OMLA. See more configuration details on page 306 (SAP WM).


Transfer Requirement:- Is a phase of planning to move material from one warehouse location to another. • We need to created TR manually for many occasions like GI for cost center, when issuing materials to a salesman for samples or for replenishments for material into the fixed bins. Use code LB01. • Create TR for replenishment of a fixed bin: use code LP21. o Replenishment control for storage type: path IMG * Logistics Execution * Warehouse Management * Activities * Define Stock Transfers and Replenishment control. • Display TRs : use code LB11 (list) or LB03 (single). • Display TRs for storage type : use code LB10 o You can create TO on header go to environment and select option accordingly.

o Delete TRs : use code LB02 and double click item and set the deletion flag. After saving the changes item will be deleted. Transfer Order:- Is used to perform the move and confirm the move when it is completed. • A TO can be created with reference to a source document either from WM or from another SAP module, such as MM. • Each line item is a individual movement of a certain quantity of material from a source bin to a destination storage bin. So, number of line items will depend on how many destination storage bins are required for the total quantity of material. • A source document can be a: o TR o Delivery document o Material document o Posting change notice (PCN). Example: Blocked sts to Unblocked sts. • Create TO for a given TR: use code LT04 • Create TO without Reference: use code LT01 o Movement type (999) used to create TO should not have flag set to "Manual TO creation not allowed". • Display TO: use code LT21 (for known TO), or use code LT24 (for known material). • Cancel TO: use code LT15 • Confirm a TO: o LT11 - Confirming a single item on a TO o LT12 - Confirming the TO  You can also enter the actual quantities here by selecting the input list. All the differences are logically stored in storage type 999.  If SU are used you can also pack option here. o LT13 - Confirming by SU o LT31 - Print a TO Sales Orders:• Display sales order use codeVA03 • To define, copy, delete, check sales organization use code EC04 (tables TVKO, TVKOT, TVKWZ) • To define, copy, delete, check sales distribution use code EC05 (tables TVTW, TVTWT, TVKOV) • To define, copy, delete, check division use code EC06 (tables TSPA, TSPAT, TVKOS) • To maintain sales office use menu path in customizing: Enterprise Structure * Definition * Sales and Distribution * Maintain sales office (tables TVBUR, TVKBZ) • Sales Order type/Document type: Path in customizing: Sales and Distribution * Sales * Sales Documents * Sales Document Header * Define Sales Document Types o Transaction code is VOV8 (tables TVAK, TVAKT)

Sales Order Type Description OR Standard Order RO Rush Order CS Cash sale CF Consignment fill-up FD Free-of-charge delivery SDF Subsequent delivery free of charge RE Returns order Sales order item category: o Define path: IMG * Sales and Distribution * Sales * Sales Document * Sales Document Item * Define Item Categories (tables TVAP , TVAPT) o Assign path: Sales and Distribution * Sales * Sales Document * Sales Document Item * Assign Item Categories (tables T184) Item Category Description TAN Standard item TAL Loaner item TATX Text item TAX Non stock item KBN Standard item consignment fill-up KLN Free-of-charge item ELN Shipping notification o For Third-party item category group is BANS Schedule Line Categories: Here we give the details like movement types, delivery block, delivery relevant, and availability check flag etc,. o Transaction code to define: VOV6 (tables TVEP , TVEPT) o To Assign path: Sales and Distribution * Sales * Sales Document * Schedule Line * Assign Schedule Line Categories (tables TVEPZ) o For third party item category is 5 and account assignment category is 1. o For consignment item category is E1 with movement type 631. o For returns order item category is DN with movement type:  Goods are first posted in to a blocked returns sotck within your plant (with movement type 651) and therefore must first be checked. Later transfer posting is performed in MM component in the freely available stock using movement type 453.  If post the GR of the returned goods directly to the freely available stock, you must enter a different schedule line category under schedule lines during order entry. By using movement type 653. Schedule Line Categories 1st place Description A Request for quote B Offer C Order D Return Schedule Line Categories 2nd place Description T No inventory management


No inventory management with goods issue No materials planning Consumption-based planning Material requirements planning

Goods Issue (GI) Process:• Is the movement of material from the warehouse to an external source, which could be a production order or a customer. • Is triggered by one of the two documents: o TR from IM or production. o OB delivery if one has been created for a customer sales order.
GI with OB delivery:-

• • • • •

• • •

Display sales order: use code VA03. (under environment go to overall status to see all the details like delivery, goods issue etc,.) Create OB delivery use code VL01N. Configure shipping point use code EC07. Display OB delivery use code VL03N. Create TO: o TO split configuration: path IMG * Logistics Execution * Warehouse Management * Activities * Transfers * Processing Performance Data/TO split * Define Profiles o OB delivery monitor: use code VL06P o After selecting a delivery and starting the process of crating TO from the delivery note, the OB delivery monitor transaction will pass the parameters to code LT03 (Create TO for delivery). Confirm TO: use code LT12. Now the material is at interim storage type 916 which is a destination storage location for TO. Post GI for OB delivery: use code VL02N to change OB delivery and press button post goods issue. Review material documents: o use code MB51 (shows both IB and OB movements of material. o Or use code MB03 to see single material document GI starts in IM. This may be GI for cost center, a GI to a project or a number of different scenarios. Enter GI by using code MB1A (Movement type 201). GI creates an -ve balance in the GI interim storage type 911 (area) in the relevant warehouse. You can see Bin Stock per Material by using code LS24. The storage bin has been named as the cost center where the material is to be consumed. Create TO from the material document produced from the GI by using code LT06. Movement type 201 has been set to search storage type 001 & 002 in this example.

GI without OB delivery:-

• • • •

Confirm TO by using LT12. You can verify the offset quantity in interim storage area (type) 911 by using code LS24. Similar to the wave function. It allows user to group TR or OB deliveries and process the group at once. A group is defined as a work package containing a number of TR or OB deliveries. This work package is used to optimizing picking operations by grouping same movement type or same storage type. Use T code LT41 to create a group for TRs. Enter shipment type filter 'A' - stock removal, and you can also filter by requirement type. You can use "Assign group" button and a group description screen will pop-up. Here you have choice of 2 step picking. Use T code LT42 to create TO for the group we just created. Set reference doc cat indicator. Reference doc cat Description B Group of TRs L Group of Deliveries Definition of a wave pick: When groups are used with OB deliveries, we normally refer to such groups as waves. We can create them by using wave monitor. The advantage of wave pick is that it is possible to select the OB delivery according to time slots. o Creating a wave from OB delivery monitor: use code VL06P. o After getting the selected deliveries take header bar menu option "Subsequent Function * Group * Wave Pick". Wave number will be displayed at the bottom of the screen. Create Pick Waves using Wave Monitor: Use code VL37. This allows the selection of waves for certain OB deliveries. This allows the use of time slot or a time slot group. o Time Slot: is defined as a period of time that can be configured in IMG. Many cases, a time slot can be a one hour time period in a warehouse shift or a whole shift. Menu path: IMG * Logistics Execution * Shipping * Picking * Wave Picks * Maintain Time Slots.  Each time slot has start and end times along with Picking wave profiles. o Picking Wave Profile: It allows you to set limits on certain criteria when reacting to waves during wave picking. Menu path: IMG * Logistics Execution * Shipping * Picking * Wave Picks * Maintain Wave Picks Profile. o Time Slot Group: a time slot group can contain all the time slots of a particular shift or a particular working day. Menu path: IMG * Logistics Execution * Shipping * Picking * Wave Picks * Maintain Time-slot Group for Wave Pick.

Multiple Processing using Groups:-

• • •

Wave Monitor:-

Results of Pick Wave Monitor: After entering the selection criteria, execute the transaction by using F8. The wave monitor displays all waves for the relevant time slot that was entered for the specific warehouse. • Create TOs by using header menu option "Subsequent Processing * Transfer Order" or (shift + F4). • Now system displays Create TO screen. Select "Start multiple proc" button or F5. Once TOs created they need to be released and printed (use "Subsequent Processing * Release/Print or (shift + F5)) for the material to be pulled. • Once the materials are picked we need to confirm TO (use "Subsequent Processing * Confirm" or (shift + F7)). We have a choice of confirming all or by storage type or picking area etc,. • All the TO from the selection used are displayed and ready for confirmation. use header menu option "Transfer Order * Confirm in Foreground" or F5. Picking (Stock removal) Process:• Picking Area: path IMG * Logistics Execution * Warehouse Management * Master Data * Define Picking Area (tables TVST, TVSTT) • A number of optional steps can be carried out with the material: o Printing price stickers o packing before material leaves warehouse. • Most costly part of the warehouse operation and most labor intensive operation usually employs the majority of the staff. • Picking errors and therefore delivery errors, are a major source of customer dissatisfaction. • Picking Schemes: o Single-Order Picking: Time and effort spent by the staff but most accurate. This Scheme used in majority of warehouses. o Batch Picking: Recommended for small size items with less weight. Chance of error while sorting picked line items to orders at picking station. o Zone Picking: Picker is responsible for only picking at his zone. Advantages of this method are that the picker's travel time is reduced because of smaller area of his and familiarity of his zones on his every day work. The disadvantage found with this is can cause bottlenecks if the pickers work at different speeds; slower zone operators can minimize the benefits of this method. o Progressive Assembly: (Pick and Pass) Picked and passed to the next zone by container on a conveyor belt or some other transport method. o Downstream Sortation: Some what similar to Progressive assembly but is used for wave picking.
Picking Strategies:-

• •

Method that determines the way a material is chosen to be picked. Storage type indicator:- Use code OMLY

• •

• •

o Allows only certain materials to be picked from storage types, and the order of picking can be defined by the storage type search for each storage type indicator. Page 258 (WM) o Max 30 storage type in one search record. o Storage type indicator needs to be updated in material master record. Storage Section Search:- Use code OMLZ. This is used in complex warehouses. Max 10 storage sections we can search (one record). FIFO (F):- Need to set this in storage type. Page 263 (SAP WM). Stock Removal Strategies Description No stock removal strategy A Partial qty management F FIFO H Shelf life expiration date L LIFO M Large/small quantities included P Fixed bin from material master R Dynamic coordinate reference number LIFO (L):- is used by a number of companies for inventory cost accounting. The value of warehouse stock impacts reported gross profit margins. Fixed Storage Bin:- Picking strategy relies on the data that has been entered into the material master record for the material to be picked. o If there is a overflow of material then it may be moved to other bin locations manually. SLED (H)(Shelf-Life Expiration):- In many industries especially retail and grocery, the shelf-life of materials is a very important characteristic. This can be sale-focused shelf-life, where the material can only sit on a store shelf until its sell-by date. Alternatively, it can be production focused, as when chemicals and raw materials can be kept only for so long and still meet tolerance limits for us in the production process. To configure use code OMKW. o Display SLED stock:- use code LX27 Partial Quantities (A):- This strategy is associated with SUM. This can be used in warehouse if the warehouse manager does not want to pick all the contents of a storage unit and then have to return some to the storage bin. Configuration is done in storage type. (make sure "Return stock to same storage bin" flag set). o The logic behind the this picking strategy is defined as follows:  Initially TO qty = or > standard SU then a standard SU can be picked from stock. However, if no standard SU are available, the partial SU quantities in the warehouse are used.  TO qty < standard SU then the system will initially proceed to remove partial SU qty from the warehouse. If no partial then it will break a full SU qty. Quantity Relevant Picking (M):- is used less frequently, but is useful for companies whose warehouses store the same material in varying sizes of bins and storage types. Configure use code OMM9. Page 282 (SAP WM)

o Control qty in material master is used as threshold quantity to determine small or large qty. o Note:- System uses movement type 603 to determine which storage type is to be used in TO for picking. Replenishments:• Movements are initiated within the IM Ex: Plant to Plant or storage location to storage location. If storage location is warehouse-managed, then this will trigger the movement of material in the warehouse. • The optimum amount of empty bin space in the warehouse depends on the materials and industry involved but is usually somewhere between 10 % to 20 %. • Checking empty bins: Display empty bins use code LS04 for specific warehouse and storage type.
Internal Stock Transfers:-

• •

• • •

• • • •

Moving material between storage bins: use code LT10. The warehouse number and storage type must be filled, as must the movement type in the program control section. A list shows the material that is available for stock transfer. A dialog box that is displayed when the stock transfer in the foreground. Enter destination data for stock transfer. After the required data is entered, the transaction uses the information to crate TO. Use code LT21 to view TO or use LT24 if you don't know TO number. Confirm the Stock Transfer: use menu header option "Transfer Order * Confirm in Foreground" or F8. Confirmation Indicator: for discrepancy Confirmation Indicator Description X Target quantity is equal to the actual quantity. U Actual qty is the balance between the target and difference qty. S Difference qty is the difference between actual and target qty. Blanks Allows the actual and difference quantities to be entered manually. Difference Indicator: use code OMLX. Moving material between storage bins: use code LT10. The warehouse number and storage type must be filled, as must the movement type in the program control section. Basis of the replenishment process is defined in the material master record for the items that need to be replenished. Use code MM02, if material has already been created. Configuration for replenishment: To enter the WM movement type for replenishment before TO can be created for replenishment of fixed bins. A replenishment movement type needs to be assigned to the storage type. Menu path: IMG * Logistics Execution * Warehouse Management * Activities * Transfers * Define Stock Transfers and Replenishment Control.

Fixed Bin Replenishment:-

Create TO by using code LP21, make sure requirement type is N, representing the replenishment for fixed bins. The requirement number entered is usually PO or sales order number. On menu bar select "Program * Execute". • Display the TRs by using LB11 and select proper TR and press "TO in Foreground". • Confirm TO by using LT12. You can review stock by using LS24. Posting Changes:- A posting change is a change to the stock level of a material. • Mostly Posting changes happens for the following reasons:o Release from Quality Inspection stock: The change in status from quality inspection to unrestricted occurs in IM module using goods movement. In WM, a movement type is also used in conjunction with a posting change notice. The PCN is created in WM automatically as a result of posting in IM.  Display posting change notice use code LB12. You need material document number, year and warehouse number.  use code LT06 to create TO.  Display stock for given material use code LS24.  Use code LT12 to confirm TO. SAP uses interim storage type 922 to move material logically.  Review stock for a given material use code LS24, you should not see Q for stock category. o Posting change from material number to material number.  Steps are similar to above step. Note: New material is placed in next available empty bin in same storage type but not on same bin. o Dividing batches among other batches.  Steps are similar to above step. Note: New batch numbered material is placed in next available empty bin in same storage type but not on same bin. Packing Process:• Packaging Material Type: use code VHAR Shipping/Loading Process:• To define, copy, delete, check shipping point use code EC07 (tables TVST, TVSTT) • To assign a shipping point to a plant use code OVXC (table TVSWZ) • To maintain a loading point use menu path in customizing: Enterprise Structure * Definition * Logistics Execution * Maintain loading point (tables TVLA, TVLAT) Cross Docking:• Cross docking matches inbound and outbound deliveries to avoid having to store material in the warehouse. o Manufacturing Cross Docking. o Distributor Cross Docking. o Transportation Cross Docking.

• • •

• •

o Retail Cross Docking.  Staple stock - Materials it sells each day of the year.  Direct freight - Material purchased once and sold by the stores and not usually stocked again. o Opportunistic Cross Docking - is the opposite of planned cross docking. Types of material suitable for cross docking: o Perishable materials. o High-quality items. o That are pre-tagged, pre-ticketed, and ready for sale to the customer. o Promotional materials. o Staple retail materials with a constant demand or low demand variance. o Pre-picked, pre-packaged customer orders. Planned Cross Docking in SAP: o Planned cross docking - decision to be made before the material arrives at the warehouse. o Opportunistic cross docking - decision occur after the material has arrived. Configuration for Cross Docking: Menu path: IMG * Logistics Execution * Warehouse Management * Cross Docking * General Settings * Maintain Warehouse Level Settings.. Configuration for Cross Docking Movement Types: Menu path: IMG * Logistics Execution * Warehouse Management * Cross Docking * General Settings * Define Cross-Docking Relevancy for Movement Types. Cross Docking Movements:o One-Step Cross Docking: movement processes the cross docking directly from the inbound goods-receiving area to the outbound goods issuing area. In Planned cross docking, the IB delivery is linked to the OB delivery. o Two-step cross docking: materials to be cross-docked are initially moved from the GR area to a cross docking storage type. In the second step, the material is moved to the GI area from the X-dock storage type when the OB delivery is released. Cross Docking Monitor:- Use code LXDCK Or Menu path: SAP * Logistics * Logistics Execution * Cross Docking * Cross Docking Monitor. Cross Docking Alert Monitor:- Use code LXDCA.

Transportation Process:• To maintain a loading point use menu path in customizing: Enterprise Structure * Definition * Logistics Execution * Maintain transportation planning point (tables TTDS, TTDST) • IM Movement Types:- use code OMJJ • For any IM movement type if the reference WM movement type 999 i.e. in WM there is no corresponding movement type. IM Movement types Description

101 102 201 231 501 551 WM Movement Type:WM Movement types 091 092 093 094 099 101 102 103 104 201 231 309 319 320 321 350 501 561 601 602 631 801 802 711 712 850 • Shipment type: Shipment type A

GR Reversal of GR GI to cost center GI to sales order GR without PO scrapping Description GR Shipping unit GI shipping unit Putaway HU Pick HU Repack GR for PO Reversal of GR GR production order Cancel GR production ord. GI to cost center GI to sales order Posting changes general. Ex: material number to material number Replenish for production Auto fixed bin rplen.type Posting change quality Replenishment Kanban GR without PO Init. Entry of Stock Bal. (used in creation of Storage Unit) GI to delivery note Cancel GI for delivery note Transfer to consignment stock with availability check GR from production GR Production via WM Decrease Differences Increase Differences Removal 2 step picking

Description Stock removal

E Stock placement U Posting changes X Whse superv. Requirement type: Requirement type Description A Asset B PO D Storage bin F Order K Cost center L Sales document V Sales order N Replenishment fixed bins P Production supply Y Container (Storage Units) Automatic TO: TO are created by batch input using the report RLAUTA10 for TR and report RLAUTA11 for posting change notices. Use code OMKZ to configure. default values for each storage type in warehouse. Menu Path: IMG * Logistics Execution * Warehouse Management * Activities * Physical Inventory * Define Default Values Configure Inventory type by storage type:- Menu Path: IMG * Logistics Execution * Warehouse Management * Activities * Physical Inventory * Define Types per Storage Type Inventory Type Description No Inventory PZ Continuous Inventory ST Annual Inventory Inventory Difference and there Movement types:Inventory Difference Movement Type Description 711 Decrease Difference 712 Increase Difference Processing Open TO:- When the physical inventory count begins, the storage types to be counted must be clear of open TO. Check for open TO by using code LT22. Confirm Open TO:- Use code LT12. Blocking the Storage type:- Use code LI06 Creating Annual Inventory Documents:- Use code LX15 Display the count documents:- use code LX22 Entering the Inventory Count:- Use code LI11N Count Differences:- Use code LI14. You can issue recount in this code. Entering a Recount:- Use code LI11N. This time you have to enter recount version.

Inventory Procedures:Annual Physical Inventory:- Set

• •

• • • • • • • •

Clear Differences:- Use code LI20. (Booking inventory or Write Off). inventory type to storage type. • Menu Path: IMG * Logistics Execution * Warehouse Management * Activities * Physical Inventory * Define Types per Storage Type • Creating a continuous inventory count document:- Use code LX16. • Printing a continuous inventory count document (?7646):- Use code LI04. List/Print report is RLLI0400. • Entering the count results:- Use code LI11N. • After the fiscal year is complete and all the bins have been counted, the storage bins should then become available for counting. To ensure table LAGP (Storage Bin) is clear of the count data and time of the previous fiscal year count, a report called RLREOLPQ should be run using transaction SE38 or included as a part of an end-of-year batch job. Cycle Counting:- Set inventory type to storage type. • Menu Path: IMG * Logistics Execution * Warehouse Management * Activities * Physical Inventory * Define Types per Storage Type • The cycle counting indicators A, B, C etc., are configured using code OMCO. • Using the ABC Analysis:- Use code MIBC. We can run analysis by using consumption/usage or requirement. • ABC Indicator and Material Master:- Use code MM03 to update indicator. • Creating a Cycle Count Document:- Use code LX26. • Printing the cycle count document:- Use code LI04. • Entering the Cycle Count:- Use code LI11N Zero Stock Check:- Is performed on storage bin when all the material has been removed, in order to ensure that the storage bin is empty. • Configuration can be set using Menu Path: IMG * Logistics Execution * Warehouse Management * Activities * Physical Inventory * Define Types per Storage Type • Performing an automatic zero stock check:- Configuration for a storage type is set to require a zero stock check on removal of all materials from the storage bin, the check will be triggered from the TO. Inventory Method Description PN Continuous Inventory based on zero check PZ Continuous Inventory ST Annual Inventory MA Manual Inventory CC Cycle counting Storage Unit Management:Definition:- Was developed to enable warehouse management to identify the container that holds a material as it moves around the warehouse. • SUM was developed exclusively for WM, and from it SAP developed HUM for MM. There are slight differences between the two, as seen here: o HUM allows for the nesting of HUs; i.e., a HU containing a number of other HUs, while SUM does not allow nesting of SUs.
Continuous Inventory:- Set

o HUM requires that an item be unpacked and packed, while this is not required for SUM. The SU is used to contain a quantity of material for its movement around the warehouse. • Activate SUM:- Menu path: IMG * Logistics Execution * Warehouse Management * Storage Units * Master Data * Activate Storage Unit Management per Warehouse. • Define SU number ranges:- Menu path: IMG * Logistics Execution * Warehouse Management * Storage Units * Master Data * Define Number Ranges. • Define Storage Type Control:- • Menu path: IMG * Logistics Execution * Warehouse Management * Storage Units * Master Data * Define Storage Type Control. o You should consider several settings:  SU mgmt active: This indicator is set to show that storage type is SU managed.  Putaway strategy: This is set to P, which means that the SU type putaway has been selected.  Mixed storage: Because different materials can be moved on the same pallet as a defined SU, the mixed storage indicator must be activated.  Full stk rmvl reqmt: If this indicator, is set, it affects the SU, not just the materials. A complete removal involves the complete SU. • Define Storage Unit Type:- Menu path: IMG * Logistics Execution * Warehouse Management * Master Data * Material * Define Storage Unit Types • Storage Unit Record:- This can be created in response to a receipt from a PO or be created later for movement within the warehouse. Use code LT07. Movement type used to crate SU is 091 and movement type to move SUs is 561 (see page 357 in SAP WM). • Display a Storage unit:- Use code LS33. • Planning SUs:- Planning storage units is the process of creating the TO, but not confirming them. Creating the TO will create the SU, so that it will exist when the material arrives at the receiving dock. o Planning SUs by TO: Use code LT0A. System uses storage type 918, and movement type used to create SUs is 091 with requirement type 'Y'. o Receiving Planned SUs: Use code LT09. Movement type to move SUs is 999. o Recording Differences in Planned SUs: While receiving code LT09 is difference exists then quantity variance screen is displayed. Difference qty is entered in this screen and confirmed. Storage Unit Documentation:- Following four documents aid the SU process: Use code LT32 to print manually. • TO Document: Movement of the SU or without SU of the material in the warehouse. • SU Content Document: Like content label. • SU Document: Like LPN label.

SU - TO Document: SU and the movement of the SU in the warehouse. Following three methods used to do SU putaway: • SU - Single material: Use code LT01. Movement type 501. • SU - Multiple material: Use code LT07. Movement type 501. • SU - Add to Existing Stock: Use code LT08. Movement type 501. Picking with SUM:- Following are methods used to do picking with SU: • Complete Stock Pick: The entire storage unit can be picked for a GI even if the requirement is for less than the quantity in the SU. We need to set configuration in storage type. Menu path: IMG * Logistics Execution * Warehouse Management * Master Data * Material * Define Storage Types. Make sure "Full stk rmvl reqmt act" indicator is set. • Partial Stock Pick: If full stock removal is not set in storage type configuration then partial stock picking is possible. • Complete stock Pick with Return to Same Bin: If "Return stock to same storage bin" indicator is set in configuration of storage type. • Partial Stock Removal Using a Pick Point: If indicator "Stor.type is pck pnt" is set for storage type. Then by removing SU from a pick point, the SU information is not lost, as it would be if the material was removed to an interim GI and then a partial amount was returned to stock. When TO confirms a qty of material, system posts the remaining qty from SU to pick point. The remaining material from SU can be moved back to the org. storage bin or to a new storage bin. (Page 376 SAP WM). Hazardous Materials Management:- Are often found in warehouse. • Classification of Hazardous Materials:o Flammable Liquid: Flash point below 100 degrees Fahrenheit. o Combustible Liquid: Flash point between 100 and 200 F. o Flammable Solid: Any substance through friction, absorption of moisture. o Oxidizer: which readily yields oxygen like bleach. o Corrosive: like common acids. o Organic Peroxide: like benzoyl peroxide. o Poison: toxic that it presents a risk to life or health. o Compressed Gas: o Cryogenics: o Radioactive: o Biomedical: tissues, organs, and blood from humans and primates. • Fire-Containment sections: Warehouse sections are divided based on fire resistance hours. Menu path: IMG * Logistics Execution * Warehouse Management * Hazardous Materials * Master Data * Define Fire-Containment Sections. • Hazardous Material Warnings: Menu path: IMG * Logistics Execution * Warehouse Management * Hazardous Materials * Master Data * Define Hazardous Material Warning.
Putaway with SUM:-

• •

• • • • • • • • •

Hazardous Material Storage Warnings: Menu path: IMG * Logistics Execution * Warehouse Management * Hazardous Materials * Master Data * Define Hazardous Material Storage Warning. Aggregate States: Is given a material in its normal conditions; i.e., a temperature of 20 C and a pressure of 1 atmosphere. Menu path: IMG * Logistics Execution * Warehouse Management * Hazardous Materials * Master Data * Define Aggregate States. Region Codes: Menu path: IMG * Logistics Execution * Warehouse Management * Hazardous Materials * Master Data * Define Region Codes. Storage Classes: Menu path: IMG * Logistics Execution * Warehouse Management * Hazardous Materials * Master Data * Define Storage Classes. Configuration for Hazardous Material Management: Use code OMM2 or Menu path: IMG * Logistics Execution * Warehouse Management * Hazardous Materials * Strategies * Activate Hazardous Material Management. Hazardous Material Record: Use code VM01. Assign HM to a MM record: Use code MM02. List of HM: Use code LX24 Fire Department Inventory List: Use code LX06. Check Goods Storage: Use code LX07. It produces an error log if the material has been stored in wrong place according to configuration and material class. (Page 396 SAP WM). Hazardous Substance List: Is produces a report of all the HM that is stored in a particular warehouse or storage type or fire-containment area. Use code LX08.

Task and Resource Management:- The functionality in TRM falls into 5 core areas: Before the 5 core areas. We will see the definitions in TRM:• Site: Menu path: IMG * Logistics Execution * Task and Resource Management * Master Data * General Settings for TRM. • Site Map: After the site has been created, it can be defined by means of different physical properties. These physical properties are defined as part of a site map. These physical properties are not found in standard WM and they are: o Zones: Example a work center, or pallet storage area.  To define use Menu path: IMG * Logistics Execution * Task and Resource Management * Master Data * Site Map Management * Define Zones, Operations and Serving Zones. o Nodes: 2 ways. As a physical node where material is placed and as a logical node where resources pass. The logical node may be an entry point or an exit point.  To define use Menu path: IMG * Logistics Execution * Task and Resource Management * Master Data * Site Map Management * Define Nodes and Entries/Exits to/from Zones. o Obstacles: wall or a rack or a office

• •

To define use Menu path: IMG * Logistics Execution * Task and Resource Management * Master Data * Site Map Management * Define Obstacles.  To define a Zone Group: Menu path: IMG * Logistics Execution * Task and Resource Management * Master Data * Site Map Management * Define Zone Groups and Assign Zones. o Working Areas: These are physical areas between two zones that are defined as areas where resources planning occurs. Ex. a working area may be the physical area between the GR dock and the picking area.  To define use Menu path: IMG * Logistics Execution * Task and Resource Management * Master Data * Site Map Management * Define Working Areas. o Resource: To define use Menu path: SAP * Logistics * Logistics Execution * Task and Resource Management * Resource Element Maintenance Wizard. Resource Management: Use Menu path: IMG * Logistics Execution * Task and Resource Management * Master Data * Resource Management. o Define Resource Element Types. o Defining Resource Types. Request Management: Controls the requests that arrive in TRM for movement of materials. Task Management: When the request is moved from request management to task management, the request is broken down into individual tasks:o One request - One task o One request - Several tasks o Several Requests - One Task o Several Requests - Several Tasks Route Management: Contains the functions that determine the route information and calculates route duration and route priority. o Mandatory Routes: Menu path: IMG * Logistics Execution * Task and Resource Management * Control Data * Define Mandatory Routes. o Route Exceptions: Menu path: IMG * Logistics Execution * Task and Resource Management * Control Data * Define Route Exceptions. Bin Management: In TRM function, the site map is created based on X and Y coordinates. For this reason, you need to assign these types of coordinates to the storage bins. The transaction to set X and Y coordinates for warehouse storage bins is LSET_BIN_COORDINATES Or use Menu path: SAP * Logistics * Logistics Execution * Task and Resource Management * Storage Bin * Maintain Storage Bins by Selection. TRM Monitor: Use Code Menu path: SAP * Logistics * Logistics Execution * Task and Resource Management * Monitor. 

Value-Added Services:- Are operations performed on materials that improve their value, functionality, or usefulness. You can create VAS orders that instruct warehouse staff to

perform certain tasks. These tasks may be part of a VAS template that is used for some materials. • Defining a VAS work center profile: A VAS work center is a location where VAS activities, such as packing or labeling, are performed. Menu path: IMG * Logistics Execution * Value Added Services * General VAS Settings * Define VAS Work Centers. • Defining VAS Settings for the warehouse: Menu path: IMG * Logistics Execution * Warehouse Management * Value Added Services * General VAS Settings * Define VAS for Warehouse. • Creating the VAS Template: use code LVAST01. • Creating a VAS order: For a work center with reference use code LVASWC02 or with no reference use LVASWOR. • VAS Monitor: use code LVASM.

RFID:• Simply stated RFID is a means of identifying an object using a radio frequency transmission. • Communication takes place between a reader or interrogator and a transponder or tag. • RFID in the supply chain is expected to generate huge volumes of data, which will have to be filtered and routed to ERP systems. To solve this problem, companies have developed special software packages called savants, which act as buffers between the RFID front end and the ERP back end. • EPC: Electronic Product Code is the emerging RFID standard developed by the MIT AutoID center. • Tag Classes:o Class 0 - Read Only: factory Programmed. o Class 1 - Write once read only (WORM): Factory or User programmed. o Class 2 - Read Write o Class 3 - Read Write with Onboard sessions o Class 4 - Read Write with Integrated Transmitters • Active and Passive Tags:o Passive tags: Can be read at a distance of 4m to 5m. o Semi-passive tags: Can be read at a distance of 100m. o Active tags: Can be read at several kilometers. • RFID and SAP:- Currently called SAP Auto-ID Infrastructure (SAP AII). This is a part of SAP Business Suites similar to SAP SCM. o OB processing (slap-and-ship) o Flexible delivery processing o Generation of pedigree notifications o Returnable transport items processing

Tables: Types of tables in SAP:- There are around 30,000 tables in SAP ECC. • Transparent tables - Mostly used in applications • Pooled tables - used by system • Cluster tables - used by system DFBATCH - Screen fields for batch selection screen LAGP - Storage Bins LQUA - Quants MCHA - Batches T000 - CLIENT T001 - COMPANY CODES T001W - PLANT/BRANCHES T001K - VALUATION AREA (ALL ASSIGNED VALUES, LIKE PLANT TO COMPANY CODE ETC.,) T001L - STORAGE LOCATIONS T002 - LANGUAGE KEYS T003 - Document Type T004 - DIRECTORY OF CHARTS OF ACCOUNTS T005 - COUNTRY CODES T006 - UNIT OF MESUREMENT T007A - TAX KEYS T008 - BLOCKING REASONS FOR AUTOMATIC PAYMENTS TRANS. T009 - FISCAL YEAR VARIANTS T161V - Shipping-Specific data for stock tfr.for purch.doc.type T161W - Order types for stock transfer T30A - WM Picking Areas T300 - WM Warehouse Numbers T300T - Warehouse Number Description T302 - WM Storage Section T302T - Description/names T307 - Storage unit types T307T - Texts T320 - Assignment IM storage location to WM warehouse number T330 - Blocking reasons T331 - Storage Type Control T333M - Mail control for background processing T343 - Storage Bin Structure for Automatic Creation of Storage Bins TPTM - Materials: Item Category Groups in MM TPTMT - Texts TTDS - Org.unit: Transportation Scheduling Point TTDST - Texts TVLA - Org.unit: Loading points per shipping point TVLAT - Org.unit: Loading points per shipping points: Texts TVLK - Delivery Types

TVLKT - Texts TVST - Org.unit: shipping point TVSTT - Org.unit: shipping point: Texts TVSWZ - Shipping points per plant TVKO - Org.unit: Sales Organizations TVKOT - Texts TVKWZ - Allowed plants per sales organization TVTW - Org.unit: distribution channels TVTWT - Texts TVKOV - distribution channels per sales organization TVVW - Item usage TVVWT - Texts TSPA - Org.unit: sales divisions TSPAT - Texts TVKOS - divisions per sales organization TVBUR - Org.unit: sales offices TVKBZ - Org.unit: sales office: assignment to Org.unit TVAK - Sales document types TVAKT - Texts TVAP - Sales Document: item categories TVAPT - Texts TVEP - Sales Document: Schedule line categories TVEPT - Texts TVEPZ - Sales Document Schedule Line Category Determination V_T3000 - Warehouse number control USR40 - Table for illegal passwords SAP Vs PkMS:Shipments - Loads Delivery - Shipment HU - Cartons Variants - Saved parameters (Like IPPARM00 for each program specific) User Exists (Business Ad-Ins) - Custom hooks in the programs SM04 - Work with Active jobs (WRKACTJOB) SE11 - DSPFFD SM30 (SE16/SE17) - DBU (DISPLAY MODE) SM31 - DBU (EDIT MODE) SE38 - STRSEU SM38 - DSPMSGQ Implementation:-

Project Team :Project Manager (Leader)

Executive Steering Committee

SAP Professionals Support

SAP Alliance Partners Technical Team Leaders

Functional Team Leaders Technical Analysts Functional Analysts System Administrators • ASAP (AcceleratedSAP):- The roadmap is composed of five well-known consecutive phases:1. Phase 1 - Project Preparation a) Obtaining senior-level management/stakeholder support. b) Identifying clear project objectives. c) Architecting an efficient decision-making process. d) Creating an environment suitable for change and re-engineering. e) Building a qualified and capable project team. 2. Phase 2 - Business Blueprint : To extract pertinent information about your company that is necessary for the implementation. These blueprints are in the form of questionnaires that are designed to probe for information that uncovers how your company does business. As such, they also serve to document the implementation. a) AcceleratedSAP Question and Answer Database: is a simple although aging tool designed to facilitate the creation and maintenance of your business blueprint. b) Issues Database: Another tool used in the blueprinting phase to track all the issues in the project. 3. Phase 3 - Realization: Functional experts are now ready to begin configuring SAP. The realization phase is broken into two parts: a) Your SAP consulting team helps you configure your baseline system, called the Baseline Configuration. b) Your implementation project team fine-tunes that system to meet all your business and process requirements as part of the Fine Tuning Configuration (around 20%).

Configuration Testing: With the help of your SAP consulting team, you segregate your business processes into cycles of related business flows. The cycles serve as independent units that enable you to test specific parts of the business process. During this process, it becomes necessary to send your project team to level 3 SAP training. • Knowledge Transfer: As configuration phase comes to close, it becomes necessary for the project team to be self-sufficient in their knowledge of the configuration of your SAP system. 4. Phase 4 - Final Preparation: As phase 3 merges into phase 4, you should find yourselves not only in the midst of SAP training, but also in the midst of rigorous functional and stress testing. a) Phase 4 also concentrates on the fine-tuning of your configuration before Go-live and more importantly, the migration of data from your old system or systems to SAP. b) At the conclusion of phase 4, take time to plan and document a Go-live strategy. Preparing for Go-live means preparing for your end users questions as they start actively working on the new SAP system. 5. Phase 5 - Go-Live and Support: Preparation is the key. a) What if scenarios related not only to the individual business process deployed but also to the functioning of the technology underpinning these business process. SAP Solution Manager (SolMan):- At the turn of century, in response to the need to more rapidly and completely deploy R/3 and a host of growing solutions offered by SAP AG, though, ASAP evolved into GlobalSAP and later ValueSAP. In 2001, SAP AG released an improved delivery vehicle - SAP Solution Manager, or SolMan - which is offering not only multiple roadmaps to implementation but also improved content. Some of this contents included sample documents, new templates, a repository for canned business process, and better projectmanagement tools. • Built upon the groundwork created by ASAP. • Robust project monitoring and reporting capabilities have been recently augmented with Learning maps, which are role-specific internet-enabled training tools featuring online tutoring and virtual classrooms. • • • • • The SAP Reference IMG. The SAP Enterprise IMG. The SAP Project IMG. SAP Upgrade Customizing IMGs.


Technical Notes (ABAP):By default you can open 6 sessions in SAP. SAP logon pad help to manage your SAP systems and accounts. SM04 - To list all user in the system.

aggregate object page 153 cardinality page 153 value table - no validation DB02 - Database Performance: Tables and Indexes ST02 - Tune Summary SCU3 OR OY18 - To find journal entries (change documents). journal entries - dbtblprt - limitations key - 86 buyts data - 500 buyts RZ10 - system parameters To clear an input field use ! and Enter. System commands on command line:• /nxxxx - in the same session • /*xxxx - in the same session, where the initial screen is skipped. • /oxxxx - in an additional session • /n - to end the current transaction • /i - to delete the current session. • /o - to generate a session list or TO KILL THE LOOPING PROGRAM • /ns000 - To end the current transaction and return to the starting menu • /nend - To log off from the system • /nex - To log off from the system without a confirmation prompt • /nsuim - (User Information System) - for IMG • /$TAB - TO CLEAR BUFFER • /nspro - SAP implementation guide System values:sy-index - we can use this in do loop. every time it gets increment by one. sy-subrc sy-dbcnt sy-dynnr sy-fld.. sy-tabix - Internal table index sy-tfill - Number of internal table rows sy-tleng - Length of a row sy-toccu - Occurs value from sys val ----used date & time (gets at the first time program starts) sy-datum sy-uzeit To get present data use statement 'get time' sy-uline editor-call ----in side program for debug purpose 12.3 Arrays/internal tables clear it - clears header line clear it[] - deletes all rows

append sorted by ----sales example 12.10 --this is the only situation where occurs limits the number of rows that can be added to the internal table. collect it -----12.11 on change of ----can be used in any loop construct not just loop at Variables defined by using tables statement are always global. Events:Check & exit Similar to Leave in RPG subroutine (Check is with condition - when condition is false then it exits routine). Stop Similar to Return in rpg goes to end-of-selection. Do not use stop in initialization, at selection-screen output, top-ofpage and end-of-page. Sub-routines:form. and endform. similar to Begsr and endsr perform is similar to ExecSr. Variables declaried by using local statemant are visible from within the subroutine all the sub-routines called by it. Include:To see all the source run program RSINCL00. ISSUES:10.12 & 10.13 PROBLEMS ON VERYING 12.2 535 - Write to variation does not trigger top-of-page.

Question:1) How can I find SAP tree structure for a given transaction code? 2) While running program - is there anyway we can find out what program is currently running and list a stack of programs and files which is similar to i-series system command? 3) Is there any way I can search for a particular word in all the source code? (like searching for a word in a given library in i-series). 4) Why is system placing converted material in to a new bin instead of putting it in the same bin. That way we don't physically move inventory in the warehouse? page 252 in SAP WM book. 5)

Jobs:1) Coke direct vendor - MDI 2) Johnson Service Group a. Cyrena Gordon b. Phone# (678) 564-5695 or (770) 988-0005 ext. 249 3) Kristine Mitchell a. Account Executive b. CrossFire Group c. Staffing | Consulting | Managed Services d. e. f. 866-839-2600 (toll free) g. 248-364-0009 (fax) 4) PkMS: Jimmy Tam a. Ryder (Atlanta); (305) 500 3214 b. Carl - Auto Base (company) (734) 462 9505 (call after 06/23/09)

Sign up to vote on this title
UsefulNot useful

Master Your Semester with Scribd & The New York Times

Special offer for students: Only $4.99/month.

Master Your Semester with a Special Offer from Scribd & The New York Times

Cancel anytime.