Explain System and User Status in Production Order

Loading Material Master Characteristics with LSMW Direct Input method

This LSMW shows how to mass load material master characteristics. The LSMW used is exactly the same as what was used to load release procedure values. Input file is obviously different. Material Master classification can be used to store additional information against a material master. Example: if it is finished products you may want to store: brand, pack, etc. If it is maintenance materials, you may want to store: size of item, grouping, etc.

Before loading the values (per material), you first need to create the fields (characteristics) and group them together in a class. This is done with following transaction codes:

• Create class – transaction CL02

• Create characteristic(s)s – transaction CT04 • Assign characteristic(s) to class - transaction CL02

No screen shots about CL02 and CT04 – you should be be able to get that right. Material characteristic values can be viewed from a few places:

• MM03 Display material and select characteristic view • CL20N Specify class type 001 and material master number • CL24N Specify class name and class type (001 in this case)

This data was loaded with attached LSMW and following input file (cl20_1.txt)

If the material numbers is numeric (example '123') then add leading zero's (as in my sample input file). This is not required for alpha material numbers (example if material number is 'A123C').

This is how the data look in UltraEdit

See how the leading zero's are chopped off in Excel, this is one of the main reasons to use Excel only to display data. Do not save from Excel, as you may alter the input data.

The last line can be deleted – it was added to show a deliberate error when all the data was loaded.

So in this case

• KLART - 001 (Material Master) • OBJEK - material master number • CLASS - Class name

• ATNAM - Characteristic name • ATWRT - Characteristic value

Running LSMW

This demo was produced using LSMW version: 4.0.0 SAP version: SAP R/3 Enterprise

Loading Material Masters with LSMW Direct Input method

INTRODUCTION

It is a lot easier and quicker to load material masters using the Standard Direct Input object in LSMW rather than with a recording of transaction mm01 or mm02. (To learn more about loading data using recording, see this post)

One input file can be used to create all the views of the material master. For all the material types. Even if different views and fields are used for the different materials.

Steps to take

• Create text file with data to be loaded • Set up and run LSMW

All steps are discussed in this post. A sample data file and LSMW Project can also be found in

attachment (end of post).

Please take note that my project and input file will need slight modification to work fully on your SAP system. You will have different material types, number ranges, field selections, etc. To get going, use my LSMW Project and data file and make changes as required to get a simple dataset loaded.

The most difficult bit in loading materials is getting the input file correct. I suggest you create the file from a database (SQL) or programmatically. Excel does work but it sometimes convert

numbers / strings (example 0100 becomes 100). More notes about this at the end of this post. Let’s first go through LSMW steps – then look at the input file.

LSMW

You can either create the LSMW project manually or load my project, see attachment at end of post.

Import Project

Download project as attachment from end of this post to your PC. Go to LSMW – transaction LSMW

select file LSMW_Z2_MM01.txt

Press “Import” (or “Import Under Another Name”).

Select Project / Subproject / Object and press “Execute”

Step 1: Maintain Object Attributes

With first option selected – press “Execute” Press “Display <> Change” to select Object

Step 2: Maintain Source Structures

Step 3: Maintain Source Fields

Define here all the fields that will be in your input file (text file with data). As a rule, keep the field names the same as in SAP. This way mapping can be done automatically.

The order of the fields is not important. For simplicity, make field size bigger than required, in this case mostly 40.

Step 4: Maintain Structure Relations

To get an idea what material master field can be loaded – click on the structure. Example for BMMH1

You will see BMM00 is to select the Views and BMMH1 contains bulk of the material fields. The fields can also be viewed via ABAP Dictionary (se11 /se12) and display the database table BGR00, BMM00, BMMH1, BMMH2 (or other).

Step 5: Maintain Field Mapping and Conversion Rules

Map field in input file to fields in SAP Material master. If your fieldnames in file is same as in SAP, then you can map them automatically by selecting Menu: Extras > Auto-Field Mapping

Not all fields need to be mapped, only those that you are loading (as defined in input file). Don’t worry to much about the warning that “Source field is longer than target file” just make sure your input data is correct. Example material type must be 4 characters.

Step 6: Maintain Fixed Values, Translations, User-Defined Routines

Step 7: Specify Files

Specify source file (on your PC) and what the files will be called on the SAP server.

Step 8: Assign Files

Step 9: Read Data

sample file attached to this post as a start.

Note you don’t need to specify path / filename. This was done is step above.

For big files – many thousand of records this might take a while.

Step 10: Display Read Data

Step 11: Convert Data

Step 12: Display Converted Data

You can display converted data to ensure that all is ok so far before creating the materials.

Step 13: Start Direct Input Program

If all is OK – let’s run them in.

First run it in test mode (not creating material) by selecting the “Check data, do not update” option

I now run it without the test option. same as above but “untick” the “Check data, do not update” option

Materials were successfully created.

At this point you may still have errors. Either your input data is incorrect, you may have fields as mandatory that was not in your input fields, different material types, etc. etc.

INPUT FILE

In step 7 above we have indicated that we are using TAB delimited files.

TIP: if you will be working with LSMW files a lot, get a decent text editor. Some suggestions are: UltraEdit or Crimson Editor (if you want a good free one).

This is how my input file looks (via Crimson Editor). The funny “>>” fields are TAB’s. My editor is set up to show TAB characters.

Note that the material number field (MATNR) is blank for first line and 0 (zero) for subsequent lines. This is the way to specify that internal numbering will be used. And 0 (zero) indicates that material being created will be extended. Fields to be ignored are marked with "/". For more about format of file, see notes in SAP Help file.

In my file, every line is unique material / plant / sloc. The input file can be prepared using database, spreadsheet or other program. In my case I generated the tab delimited file directly from database program.

LAST NOTE ON PREPARING THE DATA (OPTIONAL)

I find the easiest way is to prepare the material master data is using a SQL database. I used

MySQL. That way a sql script can be created that implement all the conversion rules.

This sample file used in this post was created directly from the database program. Below is the SQL statement (used in MySQL) that created the final data file. The header (field names) was added in another step.

Code: SELECT

'/','/','/','X','/','/','X','/','X','X','/','/','/',base_uom,'MAT DESCRIP','0100',

'/','/','/','/',1,'/',1,'/','F','ND','001',1,1,'HB',1,100,'A','02','BIN','/', price_control, price, val_class,'/',14,'/','/','/','/','/','/','/',

old_matnr,'01','00010',profit_centre

INTO OUTFILE 'c:/data/sap123.com/lsmw_direct/lsmw_directinput.txt' FIELDS TERMINATED BY '\t'

LINES TERMINATED BY '\n' FROM main_table

GROUP BY mat_number, plant, sloc

ORDER BY mat_type, old_matnr, plant, sloc;

If above code is meaningless to you. Don't stress, you don't need to use any of this in LSMW. (But I do suggest you buddy up with someone who knows SQL ).

GETTING HELP FROM SAP

Very detail help is available in SAP Help Files. For SAP Help files, goto http://help.sap.com/

Cross Application Components > CA Data Transfer > Data Transfer Objects > LO logistics General > Material Master

This post was prepared using SAP R/3 Enterprise (and LSMW version 4.0.0)

With this sample and reading the SAP Help files, I hope you are in a position to load your own materials.

Was this helpful to you? Do you require more information? You can discuss this post here.

Starting with LSMW (Legacy System Migration Workbench)

INTRODUCTION

Legacy System Migration Workbench or LSMW is SAP standard program that can be used to easily load / change master data or transactions in SAP without any programming at all. It canbe used to upload data at cutover, such as: open orders, contracts, materials, vendors, stock on hand, ... It can also be used in a production system to make changes to existing data. Very limited authorisation checks are available on the transaction, so the use of it must be very well

controlled.

The functionality is very well documented in the SAP help files. Below is a simple example where vendor masters are loaded using recording in LSMW.

(For an example on how to load materials using Direct Input method in LSMW, see this post) In our example, we will follow these steps.

• Start program and create a project

• Record the transaction to be used in the load • Define the fields to be loaded

• Define conversion rules to take place • Define the file name

• Upload the file from PC to SAP • Convert to correct format

• Create and run batch input session --- DETAIL

---Start it all by executing transaction LSWM (program /SAPDMC/SAPMLSMW ). Define Project / subproject / Object. It is also possible to export the project to a text file, to be imported into another system.

Various methods can be used to load the file (BAPI, ALE, recording ….). We will be using a recorded transaction. To record the transaction, we give the recording a name and type in the transaction code that will be used.

A screen will be shown with all the fields that was recorded. Every field needs a name. To keep it simple, allocate the default SAP name to the fields. Make sure all the fields you want to

load/change are in the list. If not, re-record the transaction and ensure you do a dropdown or type in values in the correct field.

Here is a list of all the process steps that available. In our example, not all will be used. Those to be used in example are mark with a red dot. So, we will be using Process Step 1, 3, 4, 5, 7, 8, 9, 11, 12, 13.

The next screens are the process steps as in screen above.

NB: Every time you select a process step, you will be in display mode -- first thing to do for every

step is to switch to change mode by clicking the "Display<->Change" button.

Process Step 1 - Maintain Object Attributes

Here the method to be used to load the information is defined. We will be using a BDC sesssion / recorded transaction. This method is quick to do but not the fastest. For example, if you want to load a huge amount of materials, ather use direct input method.

Process Step 3 - Maintain Source Fields

The next step is to ensure your input file is created. The input file (to be loaded in SAP) is a text file. The text file can easily be created from Excel or other data tool. Again to keep it simple, use same field names as in recording. A setting in Process Step XX will ensure that order of columns is not important.

As can be seen – in our case we used comma delimited text. It is generally better to use tab delimited format to avoid errors (example where text fields may contain commas). If you will be using LSMW quite a lot, it is better to get a better text editor and not used Notepad (as shown in screen below).

Process Step 4 - Maintain Structure Relationship

Process Step 5 - Maintain Field Mapping and Conversion Rules

In this step the rule on where the value of the recorded fields will come from is spesified. Example: values can come from an external file or a constant can be defined (for fields that will not change).

Vendor account group will not be read from external file. Lets make the field a constant value of LIEF..

Process Step 7 - Specify Files

Process Step 9 - Read Data

Load the file into SAP from your PC.

Process Step 11 - Convert Data

This applies the conversion rules that was set up in Process Step 5. So after this, all the fields to be loaded must be present and all rules applied.

Process Step 12 - Display Converted Data

Process Step 13 - Create Batch Input Session

And process the batch input session.

Thats it, the data should be in SAP!

SAP version used for this post: SAP ECC (ERP Central Component) 5.0

LSMW version used: version 4.0.0 of the LSM Workbench from 31.08.2004 (Menu: Extras > Display Display version)

SAP version used in this post: SAP ERP Central Component (ECC) 5.0

Hint: Use transaction search_sap_menu to find menu path (if in menu) of any SAP transaction.

Introduction

SAP transactions can be executed either from the SAP Menu or by using a transaction code. This post explain how to find the menu path if you have the transaction code.

You use the transaction LT03 (Create Transfer Order) but don't know where to find it in the SAP

Menu. Execute transaction: search_sap_menu

Enter

The result is the menu paths of all the places where the transaction can be found.

In this case, the same transaction can be found at a few places in the SAP Menu. Read entries from the bottom up. Example, the menu path of first entry is: Logistics > Sales & Distribution >

Change SAP documents -- tables CDHDR and CDPOS

This notes relates to SAP ECC (ERP Central Component) 5.0

Changes to a lot of SAP documents are stored in table CDHDR and table CDPOS. This include changes such as: change data in Material Master, changes to Purchase Req (PR), Purch Orders, Contracts, Sales Orders, and many more.

Lets look at an example where an existing purchase order (PO) is changed. • Create a PO (number 4500000616)

• Now lets make a change to the PO. Lets change the Short text in item 10 from "FLOWERS" to "SAP123".

This changed information are stored in table CDHDR and table CDPOS. Lets see if we can find it by displaying the table using transaction se16 (display table):

The detail of what was changed is in table CDPOS. The link is via the document number, field CHANGENR. Lets look at table CDPOS

These tables contains not just PO changes but changes to most SAP documents (accross all functional areas). So, as you can imagine these tables get huge. Entries in tables are grouped by Object Class (field

OBJECTCLAS -- Change doc object). Some of these options include:

OBJECTCLAS - transaction (fields in CDHDR) • ADRESSE - xk01

• BANF - me54n • BELEG - vf21 • BETRIEB - vd02 • COND_A - me31k • DEBI - xd02

• EINKBELEG - me22n <<< example above • ENTRYSHEET - ml85 • FEATURE - ct04 • INCOMINGINVOICE - mrbr • INFOSATZ - me13 • KLASSE - cl02 • KRED - xk02 • LIEFERUNG - vl03n • MATERIAL - mm01 • MM_SERVICE - me22n • MRP_AREA - mm01 • NRINTERVAL - omh6 • PFCG - pfcg • REVISION - me32k • SACH - fs00 • SPEC_TMP - ml10 • STLV - ml02 • VASMD - ac03 • VERKBELEG - va02 • .... etc

Mass Maintenance processing - tcode MASS

Introduction

Mass maintenance is used to make make mass changes to master data such as materials, vendors, purchase orders, purchase requisitions, etc.

The full list of possible "objects" that can be changed are: • BUS0015 Profit center

• BUS1001 Materials (industry) • BUS1001001 Materials (retail) • BUS1133 Rental units

• BUS2012 Purchase orders • BUS2032 Sales orders • BUS2104 Appropriation reqs • BUS2105 Purchase requisition • BUS3003 Purchasing info recs • BUS3006 G/L accounts

• KNA1 Customers • LFA1 Vendors

It is typically used by support staff to maintain / update master data. If your requirement is to complex for Mass Maintenance, then rather use LSMW, it can do even more -- but is more complex to use. (Search for posts on LSMW on this site).

Summary of how the process works: • Run transaction MASS

• Select what master data element you want to change • Select fields for selection and what will be changed • Select master data to be changed

• Indicate what the new value is • Save (Run)

For example: for all materials of type RAW1, make the material group 1012. Lets step through this example to show you how easy it is to use.

Running the transaction

SAP Menu: Logistics > Central Functions > Mass Maintenance > Mass Maintenance > Dialog Processing

The materials selected will be listed.

Enter what the new value (Material Group) must be.

Select the column and copy to all the materials listed below. If you don't want to change all objects -- unselect them at this point

Hit Save -- this will start the action to change the object (material) A log will be displayed on if it was successful

SAP version used: SAP R/3 Enterprise

General notes on SRM Enterprise Buyer

Notes based on Enterprise Buyer 4 (and SAP R/3 4.7)

Q: Why use Enterprise Buyer and not just purchasing in SAP MM?

A: Main reason for using Enterprise Buyer is the ability for users to easily select products and services from a catalogue.

• Enterprise Buyer make extensive use of workflows.

• Lots more Badi’s (Business Add-In’s) (similar to Enhancements).

• Configuration of Enterprise Buyer is via a SAP GUI, and users log on via web browser.

Q: What similar objects exist in Enterprise Buyer vs. SAP MM?

A:

Quota Arrangements (in SAP MM) Nothing similar (in Enterprise Buyer)

Source Lists (in SAP MM)

Vendor Lists (in Enterprise Buyer)

Outline Agreements - Contracts & Scheduling Agreements (in SAP MM) Contract (no scheduling agreements) (In Enterprise Buye)

Info Records (in SAP MM)

Pricing Conditions & Relationships (in Enterprise Buyer)

Purchase Requisition, Purchase Order and Goods Receipt (in SAP MM) Shopping Cart, Purchase Order, Confirmation (in Enterprise Buyer) RFQ and Quote (in SAP MM)

Bid Submission and Bid (in Enterprise Buyer) Materials & Service masters (in SAP MM) Products (in Enterprise Buyer)

Material Groups, Material Types, classification in material master (in SAP MM) Products Categories (in Enterprise Buyer)

Q: What data reside in Enterprise Buyer and what reside in SAP R/3?

A: This depends on the setup (also known as technical Scenario) being used. To determine what technical scenario are being used – ask these questions?

• Are you using a purchasing back end (example R/3) system?

• Where are the main Purchase orders stored (Enterprise Buyer or R/3)

(more of the different technical scenarios in a later post)

Very good out of the box integration between SAP R/3 and Enterprise Buyer. Data exchange mainly by using following methods:

• RFC / qRFC / BAPI’s (calls between systems) • Idocs (ALE) (sending documents between systems)

Enterprise Buyer is typically implemented by a Enterprise Buyer consultant (who knows

purchasing and SAP MM) and a technical consultant (who knows about SAP Workflow and ABAP).

SAP version used in this post: SAP ERP Central Component (ECC) 5.0 Sales Orders have three major levels of information:

• Header • Item

• Schedule line

Within these three levels the main indicator that describes the behaviour of the Sales Order is the:

• Sales Document Type (Header) • Item Category (Item)

• Scedule Line Category (Schedule Line)

Lets create a very basic sales order and have a look at these three levels and indicators. Menu: Logistics > SD > Sales > Order > Create - VA01

The Order Type is selected by the user, we take OR

We now need to enter the customer that we sell the goods to and the material that we sell. This master data was created beforehand. In our case, the customer (Sold-to party) is AA1122 and material being sold (material master) is 77. Also type in quantity, in our case it is 1. And press SAVE. You will get a Sales Order number, number 318 in our case.

Lets look at the Sales document using Sales Order Change - VA02 Lets first look at the Header to verify our Sales Document Type. Menu: Goto > Header > Sales

Menu: Goto > Item > Schedule Lines

Note the Item category (TAN) and Schedule Line Category (CV).

For more detail on these indicators, see posts on: - Document Type

- Item category

- Schedule Line Category

---END---Configuration of Sales Document Item Category

SAP version used in this post: SAP ERP Central Component (ECC) 5.0

Item category is determined automatically by the system based on the following criteria: Item category = Sales Document type + Item category group (in material master) + Usage indicator (ABAP) + High Level I.Cat

It can be changed manually (if configured). Sales Document types are configured at

IMG: Sales and Distribution > Sales > Sales Documents > Sales Document Item > Define Item

Categories -- transaction VOV7

The full list of default Item Categories in SAP are: 0001 - Requisition

AEN - Qtn from Serv. Order AES - Qtn from Serv. Order AFC - Configuration

AFN - Inquiry Item

AFNN - Free of Charge Item AFTX - Text Item

AFX - Inquiry Item

AGC - Config.at Mat.Level AGE - Service Quotation AGM - Config.at Comp.Level AGN - Standard Item

AGNN - Free of Charge Item AGR - Repair Quotation AGTX - Text Item AGX - Quotation Item ALEN - ALE Standard Order ALES - ALE Third Party APX - Quotation Item Proj. APXS - Quotation Item Stat. AVC - Configuration

AVN - Standard Item

B1E - Reb.Credit Memo Req. B1N - Reb.Credit Memo Req. BI1 - Indirect Item Rebate BI2 - Indir.Returns Rebate

BVN - Cash Sales BVNN - Cash Sales:FreeofCh. CH00 - Request Rent D CH01 - Cancel.Rent Req. D CH02 - Request Admin.Cost D CH03 - Cancel.AdmCo Req. D CH04 - IEA Request D CH05 - Cancel.IEA Request D CH06 - IEA Intern. Deb CH07 - Cancel.IEA Intern. D CH08 - Request Rent D Pr. CH09 - Cancel.Rent P.Req.D CH10 - IEA Pr. Req. D CH11 - CancelIEA Pr. Req. D CH12 - IEA pr. Int. Deb. CH13 - Cancel. IEA Pr. Int. CH14 - IE Sett.Req D

CH15 - Cancel.IE Sett.Req D CH16 - CreditMemo IE Sett.D CH17 - C.CreMemo IE Sett. D CH18 - IE Sett. Intern D CH19 - Canc.IE Sett. Int. D CH20 - IE Sett.Req D

CH21 - Cancel.IE Sett.Req D CH22 - CreditMemo IE Sett.D CH23 - C.CreMemo IE Sett. D CH24 - IE Sett. Intern D CH25 - Canc.IE Sett. Int. D CH26 - Request Sec. Dep. D CH27 - Cancel.Sec.Dep.Req D CH28 - Sec.Dep. Statement D CH29 - Cancel.Sec.Dep.Sta D CH30 - Sec.Dep.Inter.Sta D CH31 - Cancel.S.D.Int.Sta D CH32 - Sec.Dep.Res. Req. D CH33 - Ca.Sec.Dep.Res.Req.D CH34 - Sec.Dep.Res. Sta.D CH35 - Ca.Sec.Dep.Res.Req.D CH36 - Sec.Dep.Inter.Req D CH37 - Ca.Sec.Dep.Int.Req.D CHA0 - Payment Statement D CHA1 - Cancel.Payment Sta D CHA2 - Request Payment D CHA3 - RequestCanc.Paymnt D CHB0 - Depreciation D CHB1 - C Depriaition D CHBA - Rebate CHBB - Rebate Cancellation CHBV - Clearing CHBW - Clearing Bonus CHK0 - Payment Sta. C CHK1 - Cancel.Payment Sta D CHK2 - Payment Req. C

CHK3 - Cancel.Payment Req C CHT0 - Repayment Sta D CHT1 - Cancel.Repay.Sta D CHT2 - Request Repayment D CHT3 - Cancel.Repay.Req. D CHV0 - Request Refund D CHV1 - Cancel.Req. Refund D CHZ0 - Interest Res. D CHZ1 - Canc.Interest Res. D CHZ2 - Request Interest D CHZ3 - Cancel. Inter.Req. D DIGN - Goods Mov-Inb. Dely DLN - Stndard Itm w/o Ord. DLN2 - DFPS Normal Item DLP - Items from Projects DLTX - Text Item

DLW - Value Item DLX - Non-stock item

DOGN - Goods Mov-Outb. Dely DSI - CMS Stdrd Indiv.Part DSTP - TransfPostItemCentr EDK - ExtAgtCorrectionItem EDK1 - Neg.Correct-Ext Agt EGN - Rough Goods Receipt EGSH - Rough GR:SLSMainItem EGSU - Rough GR:SLS SubItem ELN - Inbound Delivery

ELP - Inb. Delvy Packaging ELSH - Inb. Dely SLS MItem ELSU - Inb.Dely SLS Subitem G2N - Request

G2S - Statistical Request G2TX - Text Item

G2W - Request

G2WT - Val. Item for SBWAP GFN - Request Billing Plan HIDN - SH - Item

HODN - Goods Issue - Item HSTP - TransferPostingItem HUPM - Additionals Item IRAL - Repaired Goods Del. IRAT - Repairs Exchange IRGN - Repairs Credit Memo IRIN - DynItems for BillDoc IRLA - Pickup Replacement IRLB - Send Replacement IRLN - Repairs Debit Memo IRNI - Statist. Dyn. Items IRPA - Fixed Rate Repairs IRRA - Repair Costs IRRE - Return for Repairs IRRP - Repair

IRVE - Scrap Goods

KAN - Consignment Pick-up KBN - Consignment Fill-up KEN - Consignment Issue KLN - Free of Charge Item KLS - F.O.C Non-stock Item KLX - Free of Charge Item KMN - Qty Contract Item KRN - Consignment Returns L2DM - Request L2DP - Request L2N - Request L2S - Statistical Request L2W - Request

L2WT - Val. Item for SBWAP LAN - Ret.Packaging Pickup LBN - Mat. Provided Item LBR - PM Item for Reserv. LFN - Request Billing Plan LKN - SchedAgr w.ExtAgent LNN - Ret.Packaging Issue LPN - Sched.Agreement Item LZMA - Dlv. SchedAgree Item LZN - Sched.Agreement Item LZSN - SAIt-SelfBill w/Inv. MAK - Dlv.-Pos. Correction MAK1 - Dlv.-Neg. Correction MVN - Lease Item

NCRG - IntCo. Full Good Ret NCRN - InterCo.StTR-Returns NCRZ - InterCo.Empties Retn NKN - TF Consgmt Lending NKR - TR consgmt ret. del. NLC - InterCo Stock Tr.Itm NLCG - IComp-StTr-FullGoods NLCU - IC-StTr-Empt(untied) NLCZ - IC-StTr-Empty (tied) NLN - StandStockTransItem NLNG - Full Prod. Stock Tr. NLNZ - EmptStockTran.(tied) NLRG - FullGood ST Ret.Item NLRN - Return StockTransItm NLRZ - ST Empties Ret(tied) NLSH - STrans.SLS Main Item NLSU - STrans.SLS Sub-Item PLPA - Pendulum List Req. PLPN - Pend.List Zero Qty PLPR - Pendulum List Ret. PLPS - Pendulum List Cancel PLPX - Pendulum List Revenu PVN - Item Proposal

REN - Standard Item RENN - Free Goods Item

REQ - Full Product Returns RETX - Text Item

REU - EmptReturns unlinked REX - Non-stock Item REZ - Empties (linked) RLLN - Return Delivery Item RLN - Returns Order

RLNG - Full Gds Return Dely RLNZ - Empt.ret. dely(link) TAB - Indiv.Purchase Order TAC - Config.at Mat.Level TAD - Service

TADC - Configurable Service TAE - Explanation

TAF - Configurable Service TAG - Generic Article TAL - Ret.Packag.Shipment TALS - Standard Item: SLS TAM - Config.at Comp.Level TAMA - Delivery Order Item TAN - Standard Item

TANN - Free of Charge Item TAO - Milestone-Bill.Plan TAP - Pric.at Item Level TAPA - Standard Sourcing TAPN - Free of Ch. Sourcing TAPS - Standard Item (PS) TAQ - Pric.at Header Level TAS - Third Party Item TASG - 3rd Pty Credit Memo TATX - Text Item

TAU - Empties (unlinked) TAUL - Sub-item: SLS TAW - Value Item TAX - Non-stock Item TAZ - Empties (linked) ULN - StandStockTransItem WAC - Con. ValContract Rel WAN - Release Item ValCont WIDN - WMS Inbound Delivery WIGN - Other WMS Inb. Dely WKC - ValContrItem-Config. WKN - Value Contract Item WMPP - Deliv. WM->PP WNLN - Replenishment WMS WODD - Service

WODN - WMS Outbound Dely WODS - Non-stock Item WODW - Value Item WODX - Text Item

WOGN - Other WMS Outb. Dely WRDN - WMS Customer Returns WSTP - TransfPostItemDec

WVC -

WVN - Maint.Contract Item

Configuration of Sales Document Types

SAP version used in this post: SAP ERP Central Component (ECC) 5.0

If you don't know what a Sales Document Type is, you may want to start here first.

Order Types represent business scenarios and are mostly selected by the user when creating the sales document.

Sales Document types are configured at:

IMG: Sales and Distribution > Sales > Sales Documents > Sales Document Header > Define

Sales Document Types -- transaction VOV8

The following document types are available in a standard SAP system for use: 01 - Cust.Independent Req

AA - Promotion Order AE - Qtn from Serv. Order

IN - Inquiry QT - Quotation AP - Project Quotation AR - Repair Quotation AS - Service Quotation SI - Sales Information AV - Quotation f.Contract B1 - Reb.Credit Memo Req. B1E - Exptd RebateCredMemo

B2 - Rebate Correctn Rqst B3 - PartRebSettl.Request B3E - Exp.PartRebSettl.Req B4 - Reb.Req.f.Man.Accrls BIND - Indir. Sales Rebate BK1 - Agrmt Cred.Memo Req. BK3 - Agrmt Cred.Memo Req. BM1 - Agrmnt Deb.Memo Req. BM3 - Agrmnt Deb.Memo Req.

BV - Cash Sale

CH - Contract Handling

DHU - SlsDocTypeDelyHUmvmt DL - Order Type Sched.Ag. DLR - Ord.Type Returns Del DZL - Dec. Dely Order Type ED - Issue by Ext. Agent EDKO - Correction f.ExtAgnt

CR - Credit Memo Request

G2WT - Credit Memo Req. Val GK - Master Contract

KA - Consignment Pick-up KAZU - ConsignPick-up CompS KB - Consignment Fill-up KE - Consignment Issue FD - Deliv.Free of Charge CQ - Quantity Contract SD - Subs.Dlv.Free of Ch. KR - Consignment Returns KRZU - ConsignReturn CompS

DR - Debit Memo Request

L2DM - Expense DebitMemoReq L2DP - Expense:Payment Req. L2WT - Debit Memo Req Value LA - Ret.Packaging Pickup LK - Sched.Agreement ExAg LN - Ret.Packaging Issue LP - Scheduling Agreement LV - Deb.MemoReq. f.Ctrct LZ - Sched. Agr. w/ Rel. LZM - SchedAgrt w/Dly Ord. LZS - SA:Self-bill w/Inv. MAKO - Dely Order Correctn MV - Rental Contract

NL - Replenishment Dlv. PLPA - Pendulum List Req. PLPR - Pendulum List Ret. PLPS - Pendulum List Cancel PV - Item Proposal

RA - Repair Request RAS - Repairs / Service

RE - Returns

RK - Invoice Correct. Req RM - Delvy Order Returns

RZ - Returns Sched.Agrmnt

SO - Rush Order OR - Standard Order

TAF - Standard Order (FPl) TAM - Delivery Order

TAV - Standard Order (VMI) TSA - Telesales

WA - Rel. to Value Contr. WK1 - Value Contract- Gen. WK2 - Matl-rel. Value Cont WMPP - WM Prod.Supply WV - Service and Maint. Notes:

1. This list differs between SAP versions.

2. As a guide, the most common document types are marked with bold. A client will only use a few of above depending on requirements.

Mostly copies are made of those being used. For example copy Order Type OR to ZOR. This way one can make changes to ZOR while still keeping the original configuration of the basic order types.

Doc Type, Item category & Schedule Line Category in a Sales Order

SAP version used in this post: SAP ERP Central Component (ECC) 5.0 Sales Orders have three major levels of information:

• Header • Item

• Schedule line

Within these three levels the main indicator that describes the behaviour of the Sales Order is the:

• Sales Document Type (Header) • Item Category (Item)

• Scedule Line Category (Schedule Line)

Lets create a very basic sales order and have a look at these three levels and indicators. Menu: Logistics > SD > Sales > Order > Create - VA01

The Order Type is selected by the user, we take OR

OR is a order type available in standard SAP system.

We now need to enter the customer that we sell the goods to and the material that we sell. This master data was created beforehand. In our case, the customer (Sold-to party) is AA1122 and material being sold (material master) is 77. Also type in quantity, in our case it is 1. And press SAVE. You will get a Sales Order number, number 318 in our case.

Lets look at the Sales document using Sales Order Change - VA02 Lets first look at the Header to verify our Sales Document Type. Menu: Goto > Header > Sales

Menu: Goto > Item > Schedule Lines

For more detail on these indicators, see posts on: - Document Type

- Item category

- Schedule Line Category

---END---Basic financial postings in SD

This article shows the basic account postings in SD.

As a SAP consultant, you must be able to draw and explain the basic T-accounts and know how to set up all the GL accounts in customizing.

Let’s take a simple business process:

• Company sells goods and create a Sales Order for 2,200 dollars (Selling price is 2,000 dollars plus 200 dollars sales tax)

• Create delivery document that starts the delivery process • Process Goods Issue (GI) when goods leave the warehouse • Billing customer (Billing document)

• Accounts Receivable or Clearing (get money from customer)

The material is valued at 1,000 dollars (the price in material master > accounting view)

The yellow blocks are those transactions that will create FI documents (accounting entries).

GL account postings

The GL accounts in diagram is to show typical numbers. GL account determination of the Goods Issue transaction is set up in Automatic Account determination (in Materials Management). Revenue Account determination is done in SD.

END

---SAP SD Tables

Customers

KNA1 – Customer master: General KNVK – Contact persons

KNVV – Customer master: Sales areas KNVA – Unloading point

KNVI – Tax indicators KNVP – Partner functions KNVD - Documents KNVL - Licenses

KNVS - Customer master: Shipping KNVH – Customer Master: Hierarchies

Materials

MARA – Material Master: General

MAKT – Material Master: Short description MARM – Material Master: Conversion factors

MVKE – Material Master: Sales <Sales Org, Distr Ch> MLAN – Material Master: Sales <Country>

MAEX – Material Master: Export Licenses MARC – Material Master: Plant <Plant> MBEW – Material Master: Valuation MLGN – Material Master: WM Inventory

MLGT – Material Master: WM Inventory type MVER – Material Master: Consumption <Plant> DVER – Material Master: Consumption <MRP Area> MAPR – Material Master: Forecast

MARD – Material Master: Storage Location MCH1 – Material Master: X Plant Batches MCHA – Material Master: Batches

MCHB – Material Master: Batch Stock

MARCH - Material Master C Segment: History

MARDH - Material Master Storage Location Segment: History MBEWH - Material Valuation: History

MCHBH - Batch Stocks: History

MKOLH - Special Stocks from Vendor: History MSCAH - Sales Order Stock at Vendor: History MSKAH - Sales Order Stock: History

MSKUH - Special Stocks at Customer: History MSLBH - Special Stocks at Vendor: History MSPRH - Project Stock: History

MSSAH - Total Sales Order Stocks: History MSSQH - Total Project Stocks: History

Customer Material Information

KNMTK - Customer Material Information: Header KNMT - Customer Material Information: Item

Bill of Materials (BOM)

MAST - Material EQST - Equipment KDST – Sales Order DOST - Document STST - Standard Object TPST – Functional location STKO – BOM: Header STZU – STL data

STAS – BOM: Item selection STOP – BOM: Item data STPU – BOM: Sub items

Sales Activities & Sales Document (Header)

VBUK – Header Status / Admin data VBUV – Incompletion log

VBPA – Partner functions SADR - Address

VBFA – Document flow

VBAK – Sales document: header

VBKD – Sales document: Business data VAKPA – Partner index

VEDA - Contract

VBKA – Sales Activity document NAST – Output

JSTO – PP Status STXH – Text: header STXL – Text: Lines

Sales document (Item)

VBUP – Item status

VBAP - Sales document: Item data VBKD - Sales document: Business data VEBA - Contract

VBLB – Forecast

VBEP - Sales document: Schedule line VBBE – Individual requirement

VBBS – Summary requirements VBUV – Incompletion log

VBFA – Document flow VBPA – Partner functions JSTO – PP Status NAST – Output STXH – Text: Header STXL – Text: Lines KONV – Conditions General

AGR_USERS - Assignment of roles to users

CDHDR & CDPOS - Change history of master data and documents TSTC - SAP Transaction Codes, maintained via transaction sm01 NAST - Message status

Very basics of SAP External Service Management

These notes are based on SAP ERP Central Component (ECC) 5.0

Firstly -- SAP External Service Management (ESM) must not be confused with SAP Service Management (SM). ESM is the procurement of services. SM is to provide services to a client. With External Services, you have a PO for services with Goods Receipt taking place. The Goods Receipt is called Service Entries. In contrast with goods (stock or non stock) where receiving is typically done by the inventory management group, the Service Entries are done by business themselves. The logic is that the business generated the request for the service, that is where it was done, it will be best if they do confirmation that service took place.

The big difference is that the item category is D (services) is used. For the item, detail Service to be performed can be specified. The receiving is a 2 step process. Create and then Accept Service Entry Sheet

Lets step through the process and look at the documents. The steps are Step 1 - Create Purchase Requisition

Step 2 - Convert to Purchase Order Step 3a - Service Entry Sheet

Step 3b - Acceptance of Service Entry Sheet Step 4 - Invoice and payment (not shown here) --- DETAIL

---Step 1 - Create Purchase Requisition

What makes the PR a ESM PR is the Item category. For goods it is blank. For ESM it is D

Step 2 - Convert to Purchase Order

The PR is converted to a PO. If me59 (automatic creation of PO) is used, the Material Group must also be entered in the selection criteria, otherwise it doesn't work.

Where:

- P Plan - Items copied from Purchase Order

- C Unplanned from Contract - Items copied from Contract (was not in PO) - U Unplanned - Items was not in PO

Step 3b - Acceptance of Service Entry Sheet

This is the equivalent of a Goods Receipt. The result of accepting a SES will be a material document with movement type 101 (GR against PO). Depending of process the SES can be created and Accepted by different people. Typically the acceptance is done by a more senior person.

A traffic light indicate the status of the SES - Red = Not yet accepted -- only SES - Yellow = Accepted but still to be saved - Green = accepted and saved

Release procedure and SES

Release procedures can be build in PR, PO and Service Entry Sheets. (Also possible on Outline Agreements and RFQ's)

Service Outlines

The services in the PR / PO can be specified in a hierarchy. See this post for more information on this.

Outline Agreement (Contracts)

Services specified in PR / PO as well as Unplanned Services entered in SES can be pulled from a contract (Outline Agreement).

Service masters & Service Conditions

The services can either be free text or Services Masters (similar to material masters for goods). The prices for these services are stored in Service Conditions. Lots of SAP customers start using ESM without Service Masters. And even if Service Masters are used, one do not need to use Service Conditions.

Lets look at a simple Service Master

Account Assignment U

Under special cases (if allowed), an account assignment U (Unknown) can be selected when creating the PR / PO. In this case the correct account assignment category must be provided when the service entry sheet is created.

Configuration

The focus on this post is to introduce the concept, so no configuration options are discussed. See below for config options related to this functionality. Config Menu: IMG > Materials Management

> External Services Management

Transactions

The following transactions were used for above screens: ME51N - Create PR

ME21N - Display PO

ML81N - Create Service Entry Sheet

ML82N - Change Service Entry Sheet (Acceptance) AC03 - Maintain Service Master

Blanket Purchase Orders

In SAP, Blanket Purchase Orders refer to the business process where you have a Purchase Order with a validity period (start / end date) and a limit on the item. No Goods Receipt takes place. Payment is triggered by Invoice.

Multiple invoices can be processed. Main point is that invoices must be processed within the validity period spesified in PO. The total value of invoices must also not exceed the limit spesified in PO item. The validity period is spesified on PO Header Level, while the Limit is on Item level. The creation of Purchase requisition is Optional.

Purchase Requisitions doesn't have validity period fields, although the limit can be spesified on item level. So if users create PR's then they could type the validity period simply as text in one of the long text fields.

During invoicing, if the date is outside validity period or the amount is bigger, either a Warning or Error will occur. This setting is done in customising.

Examples on where this business process can be used include: Services: example buying flowers, travel. Perticular if the receipt process is not very formalised. It is also sometimes used for

Look at processes where Financial invoices (no PO) are used. To improve control, a lot of vendor invoices could be moved to Blanket Order process.

Lets look at key fields in the Purchase Order

The Overall Limit is the value that will be used to in the check during invoicing. If Commitment is switched on in Costing, the Expected value is the value of the commitment against in this case the Cost Centre. The actual will be posted during invoicing.

Account assignment is mandatory, so this process is non stock purposes only. Stock can not be procured using this method (For stock a GR is required).

Because no Goods Receipt (GR) will take place, the GR indicator is switched off when the item category is selected.

Default GL account in account assigned Purchase Requisition

SAP version used for this post: SAP ECC (ERP Central Component) 5.0

When creating a Purchase Requisition, it is possible to default a GL account based on Material group.

This is set in configuration:

IMG: MM > Purchasing > Material master > Entry Aids for Items without an material master

If the Entry Aids (default valuation class per material group) are not found, one can also set a default GL account in T030 by leaving the Valuation class blank. (First row in above example).

HOWTO change the Materials Type of a material master

SAP version used for this post: SAP ECC (ERP Central Component) 5.0 In some cases it is possible to change the Material Type of a Material Master. Prerequisites:

• Configuration of both material types must be similar (see transaction OMS2 - Material Type configuration)

• There should be no open PO’s against this material • There should be no valuated stock against this material

• There should be no open line items against vendors for this material (see transaction FBL1N - Vendor Line Item display)

Material Type can be changed using transaction MMAM

(tcode MMAM)

• Type in material master number • Indicate new Material Type • Execute

A message will indicate if it was successfull or not. And if not why. For example here it failed due to valuated stock and open purchase orders that exists.

Material Master: Material Type configuration

SAP version used for this post: SAP ECC (ERP Central Component) 5.0 When creating a material, you need to specify the material type.

The Material type is the highest level of categorization of material masters.

Material Types defined in configuration and below is a summary of main areas that material type influence:

• Number range of material master and if it is internal (system allocated) or external (user allocate number)

• Which fields in material are mandatory / read only / optional • User departments (Views in material)

• Purchase Orders allowed • Valid valuation classes

• Quantity and Value update (does it update stock qty and value) • Is it a pipeline material or not

• .... and many more

Standard SAP Material Types include: ABF - Waste

CH00 - CH Contract Handling CONT - Kanban Container COUP - Coupons

DIEN - Service ERSA - Spare Parts FERT - Finished Product FGTR - Beverages

FHMI - Production Resource/Tool FOOD - Foods (excl. perishables) FRIP - Perishables

HALB - Semifinished Product HAWA - Trading Goods HERS - Manufacturer Part HIBE - Operating supplies IBAU - Maintenance assemblies INTR - Intra materials

KMAT - Configurable materials LEER - Empties

LEIH - Returnable packaging LGUT - Empties (retail) MODE - Apparel (seasonal) NLAG - Non-stock materials NOF1 - Nonfoods

PIPE - Pipeline materials

PLAN - Trading goods (planned) PROC - Process materials PROD - Product groups ROH - Raw materials

UNBW - Nonvaluated materials VERP - Packaging

VKHM - Additionals VOLL - Full products WERB - Product catalogs WERT - Value-only materials WETT - Competitor products

The main configuration of material type is in transaction OMS2

This information resides in: T134 - Material Type

T134T - Material Type: Text

T134M - Material Type: Valuation area data

For number range configuration, the transaction is:

IMG: Logistics > Material Master > Basic Settings > Material Type > Define Number range (MMNR)

This is the main settings of material type. In later articles, we will address other configuration that can be be done per material type.

Adding fields to Material Document List (MB51)

Within Inventory Management, the material document list transaction is used to list material documents. It is a very popular transaction.

The selection fields can be changed in configuration.

For example: We want to add the "Order" field to the selection screen.

Selection screen before change

Transaction MB51 - Material Document List Observe -- there is no "Order" field.

Screen after change

Transaction MB51 - Material Document List This time with the "Order" field in the selection.

Configuration required

Config Menu > Materials Management > Inventory Management > Reporting > Define Field Selection for Material Document List

Last edited by SAPman : 12-13-2006 at 07:30 PM.

Two-step movement Plant to Plant

Within SAP Inventory Management, there are two methods how stock are moved between plants using a 2-step process:

• Stock Transport Orders (UB) • Transfer Posting

What does 2-step mean?

Example: Let’s assume stock is moving from Plant A (Storage Location 0001) to Plant B (storage location 0002).

Two step means that two transactions will be used to move the stock. After the first transaction, stock has left plant A but it is not yet available at Plant B. Only after the second transaction is it available for use in Plant B.

Some reasons for using 2-step movements (and not 1 step):

• Long time span between leaving Plant A and arriving at Plant B • Need to control when goods leave plant A but not received at plant B

Using Stock Transport Orders (STO)

Steps:

• Create a Stock Transport Order (ME21N, Purchase Order doc type UB)

• Process Goods Issue against STO (MIGO > Goods Issue > PO) – movement type 351 • Process Goods Receipt against STO (MIGO > Goods Receipt > PO) – movement type 101 The use of Planned Orders and Purchase Requisitions are optional.

Steps:

• Process a Transfer Posting (MIGO > Transfer Posting) – movement type 303 • Process a Transfer Posting (MIGO > Transfer Posting) – movement type 305

The Transfer Posting can be done with reference to a Reservation. Although this is not used a lot.

Similarities between Stock Transport Orders (STO) and Transfer Postings (TP)

• Both use transaction MIGO for both steps

• After first step, goods are already reflected in receiving plant and not available

Differences between Stock Transport Orders (STO) and Transfer Postings (TP)

• Movement types are different 351 & 101 for STO

303 & 305 for TP

• Stock types at receiving plants are different - In Transfer (MARC-UMLMC) for TP

- Stock in Transit (MARC-TRAME)for STO

• For STO, 351 and 101 is group together where for TP there is no link between 303 and 305

• STO requires more transactions than TP

• STO must be configured for the sending plant / receiving plant where no plant specific configuration exists for TP

• STO is based on Stock Transport Order (type of Purchase Order). Where no purchasing document is used for TP

• STO can be initiated with a Planned Order or Purchase Requisition • Planning (MRP) can be used to initiate movements, but only STO’s

Configuration required to use STO

Config: MM > Purchasing > Purchase Order > Set up Stock Transport Order > Assign Document

Type, One-Step Procedure, Underdelivery Tolerance

Maintaining Market Price

This notes relates to SAP ECC (ERP Central Component) 5.0

Where does it get used in Standard SAP?

In SAP Vendor Evaluation, the Automatic calculation of points for price based sub criteria compare the Market Price with Actual price in Purchase Order. In standard SAP, Market price is per Purchase Org + Info Rec Category + Material.

How to maintain the market price?

Can one keep track of changes to information?

Audit log of all changes are kept, see sample below:

Split Valuation

This notes relates to SAP ECC (ERP Central Component) 5.0

Without split valuation, materials are valued at plant level.

With split valuation, the same material number at a plant can have different stock quantity and value for different groupings (called valuation types).

• new, old or

• GB, US, AU, ... (indicating countries for example) • red, blue, black, etc.... (indicating colors for example) The valuation typs are grouped together in a valuation category

So for example, the above valuation types could be grouped by age, country, color.

A material is activated by entering the valuation type in the accounting view of the material master.

IMPORTANT: It is only possible to change a material (valuation category) if no stock and PO

were created. So it is not something that get changed at will. It needs to be decided on creation of material.

Steps to set it up CONFIGURATION

1. Activate Valuation

2. Create Valuation Category 3. Create Valuation Types 4. Link Categories > Types

5. Link valid Valuation Categories to Plant

MASTER DATA

1. Activate Split valuation for a material

(Add Valuation Category in material master) 2. Create Accounting views for every valuation type

Using Split Valuation in transactions

1. Create Purchase Order 2. Goods Receipt / Goods Issue 3. Physical Inventory

4. Stock Overview

---DETAIL---In this example we want to group material in the same plant based on AGE (valuation category). We will have two "groups" (valuation types): OLD and NEW.

Configuration

IMG: Material Management > Valuation > Split Valuation

Configure Split Valuation - tcode OMWC

2. Create Valuation Category

Select: Global Categories

The Ext Mandatory option will force users to enter a valuation type in purchase orders. Select: Create (to save)

3. Create Valuation Types

Select: Global Types > Create

Select: Create (to save)

The Purchase Orders attributes option indicate if PO's are allowed or not. 1 - Not allowed

2 - Allowed but with warning 3 - Allowed

The account category reference determines what GL valuation classes will be allowed.

4. Link Categories > Types

Select: Global categories (from main config menu) Select: Valuation Category

5. Link valid Valuation Categories to Plant

Select: Local Definitions (from main config menu) Select: Plant to use

Select: Cats -> OU

Select: Valuation Categegory and press Activate

ACTIVATE MATERIAL MASTER

1. Activate Split valuation for a material

(Add Valuation Category in material master) Material Master create - MM01

NOTE: It is only possble to change a material (valuation category) if no stock and PO were created. So it is not something that get changed at will. It needs to be decided on creation of material.

1. Create Purchase Order - ME21N

2. Goods Receipt / Goods Issue - MIGO

4. Physical Inventory - example MI10

Note that the batch field is used!

---- END OF DOCUMENT

---SAP MM Tables

Materials

MARA - Material Master: General data MAKT - Material Master: Description MARM - Material Master: Unit of Measure MAPE - Material master: Export control file MARC - Material master: Plant data

MARD - Material master: Storage location MAST - Material link to BOM

MBEW - Material valuation

MLGN – Material Master: WM Inventory MLGT – Material Master: WM Inventory type MDIP - Material: MRP profiles (field contents)

MKOP - Consignment price segment (old versions of SAP) EBEW - Valuation of sales order stock

QBEW - Valuation of project stock

MVER – Material Master: Consumption <Plant> DVER – Material Master: Consumption <MRP Area> MVKE – Material Master: Sales <Sales Org, Distr Ch> MLAN - Material Master: Tax indicator

MARC - Material Master: Plant data MAPR – Material Master: Forecast

MARD – Material Master: Storage Location MCH1 – Material Master: X Plant Batches MCHA – Material Master: Batches

MDMA - MRP Area data

DBVM - MRP Planning File Entry: MRP Area

MOFF - Outstanding Material Master Records (Maintenance status) MARCH - Material Master C Segment: History

MARDH - Material Master Storage Location Segment: History MBEWH - Material Valuation: History

MCHBH - Batch Stocks: History

MKOLH - Special Stocks from Vendor: History MSCAH - Sales Order Stock at Vendor: History MSKAH - Sales Order Stock: History

MSKUH - Special Stocks at Customer: History MSLBH - Special Stocks at Vendor: History MSPRH - Project Stock: History

MSSAH - Total Sales Order Stocks: History MSSQH - Total Project Stocks: History

Vendors

LFA1 - Vendor Master: General data LFB1 - Vendor Master: Company data

LFM1 - Vendor Master: Purchasing Data (Purchasing organization) LFM2 - Vendor Master: Purchasing Data (Plant, Vendor sub-range)

Purchasing

EBAN - Purchase requisition: items

EBKN - Purchase Requisition: account assignment STXH - SAPScript Text Header

STXL - SAPScript Text Lines

EKKO - Purchasing document header EKPO - Purchasing Document: Item

EKET - Purchasing Document: Delivery Schedules

MDBS - Material View of Order Item/Schedule Line (good to find open PO's) EKKN - Account assignment in purchasing document

EORD - Purchasing Source List EIPA - Order price history record EKAB - Release documentation EKBE - Purchasing document history

EKBZ - Purchasing document history: delivery costs

EKPB - "Material to be provided" item in purchasing document ESKL - Account assignment specification for service line ESKN - Account assignment in service package

ESLH - Service package header data ESLL - Lines in service package

ESSR - Service entry sheet header data

ESUC - External services management: Unplanned limits for contract item ESUH - External services management: unplanned service limits header data ESUP - External services management: unplanned limits for service packages ESUS - External services management: Unplanned limits for service types

EINA - Purchase Info Record: General

EINE - Purchasing info record: purchasing organization data KONP - Condition Item

KONH - Condition Header

Inventory Management

ISEG - Physical inventory document items MKPF - Material document: Header

MSEG - Material document: item RKPF - Reservation: Header RESB - Reservation: Item

Invoice Verification

BSIM - Secondary index: documents for material MYMFT - FIFO results table

MYML - LIFO material layer

MYMLM - LIFO material layer (monthly) MYMP - LIFO period stocks, single material MYMP1 - Receipt data LIFO/FIFO valuation MYPL - LIFO pool layer

MYPLM - LIFO pool layer (monthly)

RBCO - Document item, incoming invoice account assignment RBDIFFKO - Invoice Verification: conditions

RBDIFFME - Invoice Verification: quantity differences

RBDRSEG - Invoice Verification batch: invoice document items RBKP - Document header: incoming invoice

RBKPB - Invoice document header (batch invoice verification) RBTX - Taxes:incoming invoice

RBVD - Invoice document: summarization data

RBVDMAT - Invoice Verification: summarization data, material RBWT - Withholding tax:incoming invoice

RKWA - Consignment withdrawals

RSEG - Document item, incoming invoice

Customising and other master data

MDLV - MRP Areas

MDLG - MRP Areas - Storage Locations MDLW - MRP Areas - Plants

MDLL - MRP Areas - Subcontractor T023 - Material Groups

T024 - Purchasing groups

T030 - Standard Accounts Table (Automatic Account Determination) T156 - Movement Type

AUSP - Release Procedure: Strategy values (cl20n, cl24n) AGR_USERS - Assignment of roles to users

CDHDR & CDPOS - Change history of master data and documents EDID4 - EDI information

TSTC - SAP Transaction Codes, lock/unlock: sm01, created: se93 TSTCT - Transaction codes TEXT

SAP Hierarchy -- Materials Management

SAP version used for this post: SAP ECC (ERP Central Component) 5.0

Key Org structure objects used by Materials Management are: • Company (FI)

• Plant

• Storage Location • Purchase Organisation

(the red crosses indicate links that are not allowed -- see notes below)

Q: Why do we set up SAP Organisational Structures (or SAP Hierarchy)?

• It roughly mimic the actual structure of the organisation • Use for reporting purposes, examples:

"What are the current stock levels at storage location 0001?" "I want to have a Balance Sheet for company 1000?"

• Use for authorisation purposes, examples:

• Master data is stored per organisational object, example:

- Valuation is on plant level, so if same material is in two plants the material will have two accounting views (one per plant)

- If the same vendor is used by multiple purchase organisations it will have multiple purchasing views

To keep it simple you want minimum amount of SAP Hierarchy objects (companies, plants, storage locations, ...). Example: Don't just create a lot of plants -- always ask why, why, why?

Company Code

Set up on the FI side of SAP.

Required if we need to do external financial reporting.

All companys must have different codes (company code is 4 characters) Questions to ask business:

• What are the legal entities of the business?

Plant

Used by all Logistics modules (MM, PM, PP, QM, PS,...) Must be link to a company code. (only one)

All plants must have different numbers (plant number is 4 characters) Questions to ask business:

• Where are the physical places (storage locations, distibution centres, ..) where materials are handled?

• If using SAP PP, where are all the factories?

• How does the valuation (prices) of material differ between all these places? • Reporting and authorisation requirements?

Storage Locations

Used by Inventory Management (and Warehouse Management) Part of one Plant.

Storage locations within the same plant must have unique number (4 characters) Questions to ask:

• Where are all the physical storage places (warehouses, tanks, ...)

Purchase Organisation

A plant must have a purchase organisation (one or more)

The link to company code is optional. If a Purchase Organisation is link to a company code, it can only be used by plants within that one company code.

Contracts / Pricing are done in the purchase organisation.

It consists of people (purchasing groups) that manage the purchasing function. Purchasing views in vendor master is per Purchasing Organisation

• What is company structre of contract negotiators and buyers? • Is the same vendor used by only some buyers?

Plants can also be linked to a default Purchase Organisation. This is used for example in "Auto PO create (when doing GR)" functionality, so that the system knows what P.Org to use. This link is only required if these functionalies are used.

CONFIGURATION IN SAP

Creating and Assigning (linking) Plants

First create a plant by copying an existing plant:

IMG: Enterprise Structure > Definition > Logistics > Define, copy, check Plant Select Activity: Copy, delete, check plant

No assign the plant to a company code:

IMG: Enterprise Structure > Assign > Logistics > Assign Plant

IMG: Enterprise Structure > Definition > MM > Maintain Sloc

It is also possible to give a storage location "address" information (optional)

Create and Assigning (linking) Purchase Organisations

Then link it to the plants where it will be used.

It can also be link to a company code (this only takes place if the P.Org will be used plants linked to this company code).

Your first (very simple) MRP run using Re-order Point planning

T

Simple steps

1. create material (or change existing) 2. View current stock on hand

3. Run MRP for the material

4. Evaluate MRP run (View results of MRP run) Step 1 -- Create / change material

Transaction mm01 (create material) or mm02 (change material) if material exist

Ensure that material is created with at least the following views: Basic data, purchasing, MRP 1, Storage, Accounting. Enter Plant / Sloc as required.

The key MRP parameters are the MRP Type and Lot Size.

MRP Type - Defines when the rule used to determine WHEN the PR or Planned Order will be be created.

Lot size - Determine calculation to be used to determine the QUANTITY in the PR or Planned Order

For my simple demo I will use standard SAP MRP type = V1 and Lot size = HB For V1 (Manual reord.point w. ext.reqs

) a re-order point must be spesified, make ROP = 100.

For HB (Replenish to maximum stock level) a maximum level must be spesified, make Max value = 1000.

Step 2 -- View current stock on hand.