Embed Size (px)
Citation preview
INDEX
1) Material Master : Material type Configuration 2)Setting up Simple Release Procedure for Purchase Requisitions3)Split Valuation 4)Loading Material Master Characteristics with LSMW Direct Input method5)Load release procedure values using ABAP program6) Finding a transaction in the SAP menu
7)Mass Maintenance processing - tcode MASS8)Two-step movement Plant to Plant9)Adding fields to Material Document List (MB51)10)SAP Steps for Opening previous period in MMrr11)SAP SU01 Create new user
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 IMG: Logistics > Material Master > Basic Settings > Material Type > Define Attributes (OMS2)
Some settings can be done per plant
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)
First create a Group
Then link the material type to it
This is the main settings of material type. In later articles, we will address other configuration that can be be done per material type.
************************************************************************************************************************
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).
The valuation types are set up in configuration could be for example: 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 possible to change a valuation category if no stock and PO were created. However, once a Valuation category is assigned -- it can not be un-assigned (make blank again). 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
1. Activate Valuation - tcode OMW0
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 Select: Types > cat.
Activate valid valuation categories
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.
2. Create Accounting views for every valuation type - mm01
USING SPLIT VALUATION IN TRANSACTIONS
1. Create Purchase Order - ME21N
2. Goods Receipt / Goods Issue - MIGO
4. Physical Inventory - example MI10
Note that the batch field is used!
5. Stock Overview - MMBE
--------------- END OF DOCUMENT -----------
Setting up simple Release Procedure for Purchase RequisitionsBy Willem Hoek
Release Procedures (approval) can be used for Purchase Requisitions (PR), Purchase Orders (PO), RFQ's, Outline Agreements and Service Entry Sheets. The principle is exactly the same for all. If you can master one, you will know them all.
Lets set up release procedures for PR for the following example:
Our company have got 2 plants: Plant 3100 (London) and plant 3600 (New York). For New York (plant 3100), if PR item value is between 0 - 1000 dollars, then
PR needs to be released by one person (person B) For New York (plant 3100), if PR item value is bigger than 1000 dollars, then
PR needs to be released by two people (first by person B, then person C)
For London (plant 3600), if PR item value is bigger than 1000 dollars, then PR needs to be released by two people (first by person A, then person C).
Key terminology: Release Codes - The different levels that the approval will go through. Release Groups - Grouping of strategies.
Release Strategy - Unique, set of condition, sequence and levels of releases. Every line in diagram is a Strategy (so we have 3).
Release Indicator / Status - The status of PR as it moves through the strategy. Example 'Block' (can't create PO yet) or 'Final Release' (can create PO from PR)
Here is a summary of the steps to follow to set up our example: Create Characteristics & link to comm. structre (CEBAN for PR) Create Class & link to characteristic
Create Release Groups & link to class
Create Release Codes
Release Indicator
Set up strategies - Strategies & Codes - Prerequeirements - Status - Assign values for strategies
Set overall / item for doc type (PR only)
Create and allocate autorisation profiles
--------------- DETAILS OF SETTING IT UP ---------------
Create Characteristics & link to communication structure (CEBAN for PR)
Here we define which fields are used to determine the strategy that will kick in. In our case we used 'Plant' and 'Item value'. Not all fields in the PR can be used. For a full list of fields that can be used to determine the release startegy, see tcode se12 table CEBAN.
So the two fields that will be used is:
Field CEBAN-WERKS for Plant Field CEBAN-GSWRT for Item Value
We need to create a characteristic for every field. tcode ct04 Any characteristic name can be used. Keep something descriptive to avoid confusion.
For Item Value -- lets create characteristic Z_GSWRT
First go to Additional Data tab and enter the table/field (and Enter)
Enter currency to be used in the Basic data tab. Also select multiple values and Intervals allowed
The Intervals allowed will allow us to assign a range of values, example: If PR value is 0 - 1000 USD .....
Save the characteristic
For Plant -- characteristic Z_WERKS Again, the table/field name in Additional Data to enter table/field
Again set multiple values and save the characteristic The multiple values is to assign more than one plant to strategy, example: If PR for plant 3100 and plant 3600 is ...
Create Class & link to characteristic
Create a class (simply to group the characteristics). Again any name can be used. Tcode CL01 -- Create Class. The Class Type must be 032.
Configure Release Procedures
Above actions was all master data. We now need to do some configuration. Menu: IMG > Materials Management > Purchasing > Purchase Requisition > Release Procedure > Procedure with classification > Set up procedure -- (tcode OMGQ in older SAP versions)
Create Release Groups & link to class
We have two groups to create AA and AB. We need to indicate the class we are working with, in out case Z_PR.
Create Release Codes
Create all the release code / group combinations. This is all the dots in diagram above. So we have 4.
Later on, authorisation profiles will be linked to these code / group combinations.
Release Indicator
First we create the different statusses that the PR can be in throughout it lifecycle. Later on (below), we will be linking using these statusses. Here is the standard SAP indicators, wou probably wouldn't need to add any.
We will be using two of these -- X (Block) and 2 (Released)
Under the Details section, you can indicate which documents can be created from this PR. For Indicator 2, one can create PO's and RFQ's.
With Field Selection you can define which fields can be changed. This is the same indicator that gets used with document type configuration to make some fields read only, mandatory, hidden.
Set up strategies - Strategy & Codes
Every line in our diagram above is a strategy. So We have three Lets call them: Group AA / Startegy S1 -- Code L1 (for plant 0001) Group AA / Startegy S2 -- Code L1 & L2 (for plant 0001) Group AA / Startegy S2 -- Code L1 & L2 (for plant 0002)
Here are the settings for AA / S2
Set up strategies - Prerequisites
For every strategy, we need to define a release prerequisites. This indicate if one code need to take place before the other. In this case, level 2 (L2) can only take place if level 1 (L1) has been released.
Set up strategies - Status
This is also done for every strategy. The screen is dependant on what groups were linked to the strategy as well as prerequisites that was set up. In this example:
- if nobody release it then PR is block.
- if L1 release the PR, the PR is still blocked - if L1 and L2 release the PR, the PR can be converted to RFQ/PO
Out of interest, the reason why there is not a L2 only option is because of the setting in the prerequisites.
Set up strategies - Values for strategies
The values linked to strategies are master data (not configuration) and can be set in two places. Either within the configuration itself -- selecting the classification button
Or, in classification, example CL24N
Both methods work, the advantage of CL24N is that all the strategies can be viewed easier.
Set overall / item for doc type (PR only)
For Puchase Requisitions, there is an option to release either on item level or on document level. For PO / RFQ / Contracts, one can only release on header level. Back to the PR, it is highly recommended to use item release. This can be done in two places.
Firstly where the groups were created
On the document type configuration for PR Config menu: Materials Management > Purchasing > PR > Define document types
Create and allocate authorisation profiles
In our example we will have three people releasing, so three profiles will need to be created. Authorisation profiles can be created using tcode PFCG.
Usage of PFCG are not being discussed here, but see below for relevant screen where the profile was created.
--------------- USING RELEASE PROCEDURES ---------------
Create a Purchase Requisition srinLets create a PR, and see if the release procedure kicks in. In our case we will create it for plant 3600 and any value. So we will expect Strategy AB / S2 to kick in.
Create PR -- me51n
If no 'Release strategy' tab, then it didn't work. In this case all is fine. The user can see the Release Group (AB), Strategy (S2) and release indicator (X).
(SAVE)
Release a Purchase Requisition
Releasing can be done per PR or collective. Lets' use the collective release. SAP Menu: Logistics > Material Management > Purchasing > Purchasing Requisition > Release > Collective Release -- ME55
Select all the items to be released and then hit Save. You will see the status of the item change to the next Release Indicator.
This is the absolute basics of setting up Release Procedures for Purchase Requisitions. For more posts on Release Procedures, see index of posts.
SAP version used for this post: SAP ECC (ERP Central Component) 5.0
********************************************************
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 [sap123.com]. 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 [ultraedit.com]
Same information but displayed in Excel
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
Details of LSMW (attached)
Running LSMW If no error, you will see the deliberate error (that was added in last line)
This demo was produced using LSMW version: 4.0.0 SAP version: SAP R/3 Enterprise
************ End of Document************************
Load release procedure values using ABAP program
his post shows how you can use an custom ABAP program to load characteristic values for release procedures.
Method described in this post is not the recommended way. The best way to load Release Procedure values is by using a standard LSMW. See here for details.
Background information
If you have lots many release strategies (set up via configuration) it is quite a task to load the characteristic values. It can be loaded manually using transaction cl24n (SAP menu: Cross-Application Components > Classification System > Assignment > Assign Objects/Classes to Class) but it can take quite some time. The information reside in table AUSP
The program listed here can be used to do this task programmatically.It has been used many times in production systems without problems -- but use it at your own risk. Changes may need to be done to program to fit your requirements.
Loading information
Before loading up the values, you need the following information: Name of class used (use it in the upload program) Internal number of class -- get it in table KLAH (use in the upload program)
Internal number of characteristic -- from table AUSP (use in text file)
Text file with data
If no data in AUSP, you need to load at least one set manually (cl24n) so that you can get the internal characteristic number. This number will not change, except if you change your release procedure.
Delete current information in table AUSP
If you want to re load information, you first need to delete the existing information. This can be done via cl24n or using attached program ZCL24N_DELETE
Loading new values -- sample input data
Data is in tab delimited format, no title row in text file: column 1 - Release code + Strategy - 4 characters - example AAS1 column 2 - Characteristic value - 10 digies - example 0000000810 column 3 - Counter - 3 digits - example 001 001 column 4 - number - 1 digit - example 1 or 9 column 5 - class type - 032 column 6 - Characteristic value
Sample input file:
Source code
zcl24n.txt -- load up information zcl24n_delete.txt -- delete information from ausp
SAP version used for this post: SAP ECC (ERP Central Component) 5.0
*********** End of Document ****************
Finding a transaction in the SAP menu
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.
Example
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 > Shipping and Transportation > Picking > Create Transfer Order > Single
****** End of Document************* 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
Transaction MASS
Select the tables for the selection screen. In our case, material type = MARA.
The materials selected will be listed. Now indicate which field must be change. In our example the material group field.
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
*************End of Document ****************
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: Lets 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.
Using Transfer Postings (TP)
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
Here the source plant, destination plant and allowed STO document type is specified.
The post is based on SAP ECC6 ********************** End of Document ***************
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
**************End of Document *****************
SAP Steps for Opening previous period in MM
If you want to open previous period for reversal entry or additional entryThe following are steps for Opening previous period in MM :
1. Go to TCode SU01 (see OSS NOTES 487381)2. Choose "change" tab with your loging Name3. Choose "Parameter" tabgive Parameters MMPI_READ_NOTE with date format as YYYYMMDD(say today 20071201)4. SAVE.5. Go to T-code MMPI6. open the old periods which you want to post into,Note : the period opening will be valid for only for the particular day only.
7. Complete the posting you want to reverse or add
8. Go to MMPV to close the periodsNote : If we enter the date or month in MMPV means we are opening that date or month by closing previous date or month (Never use MMPV without completing the transaction in previous month)
************* END of document ***************
SAP SU01 Create new user
SAP SU01 Create New User
1. Go to SU01
2. Click button
3. Fill in all the required fields4. Fill in all the tabs password and last name are mandatory
5. In the "logon data" tab , choose the right user type.For end users you should choose Dialog user
5. In "roles" tab, add roles to user.
If you want to give all authorizations, in "profile" tab add sap_all and sap_new profiles.
********** End of Document ******************
How to input stock into SAP – Jan 2011 SAP Training Batch
Problem : When doing delivery, some of our students faced issues with stock not being available. This is a very common problem
faced by anybody who is currently training in SAP.
Solution : To resolve this, you would have to put dummy stock into the storage location ( As though real stock has come in ) . The
easiest way to do this is via Transaction code [ MB1c ]. The menu path for the same is [ SAP Easy Access -> Logistics -> Logistics
Execution -> Inbound Processes -> Goods Receipt for PO -> MB1c Goods Receipt for other activities ]
Step 1 : Use Transaction Code MB1c
Step 2 : Enter the Movement Type of 561, enter the plant and storage location where you want to input the stock
Step 3 : Enter the Materials and Quantities that you want to input. Save the Transaction. You can immediately go to MMBE ( Verify
Stock in SAP ) and check the increase in quantity under the respective plant/storage location combination.
