Pricing procedure Steps and Details in SAP MM

What is Pricing procedure?

The main concept of pricing procedure is combination of different type charges, like Gross price, freight, discount, surcharges etc etc.

We use pricing procedure to determine these all conditions into one procedure, where we can find the sub-total for net amount.

To understand pricing procedure we have to comfortable with these below things:

1. Condition Table

2. Access Sequence

3. Condition Type

4. Condition Record.

5. Schema Group

6. Calculation Schema

7. Schema Determination

Let’s discuss about all these points in details.

1. Condition Table

It’s a table where we can save the all fields with the combination for individual condition record. Suppose if I use Plant as condition table, then the condition record will be created for plant only.

We can use many fields in one condition tables.

2. Access Sequence

The main concept of Access sequence is, it searches condition record for condition type from condition table.

One access sequence contains many condition tables.

Suppose we maintain 4 condition tables in one access sequence. Then when a condition type will be searching for condition record via this access sequence, the access sequence will allow to search only this 4 condition tables.

3. Condition Type

In simple term, condition type is used for different type of charges. Like gross price, discount, freight, rebate etc etc.

Suppose we purchase a material for price 10, we get a discount of price 2. Then the price 10 will be going to a condition type and the price 2 will be going to another condition type.

4. Condition Record

Condition record contains the record which is maintained against condition table with regards to condition type.

It can be fetched via access sequence and condition type.

Suppose we maintain a condition record against condition table (vendor) with regards to condition type. Then whenever the vendor used this condition type, the condition record will be fetched.

5. Schema Group

It’s assigned to our vendor and Purchase Organization, It helps the vendor and purchase organization to choose pricing procedure.

One schema group will be assigned to vendor and one schema group will be assigned to Purchase organization. With this combination, system will fetch the pricing procedure.

6. Calculation Schema

Here we maintain sequence for the pricing calculation, like gross price, discount, rebate, surcharges etc. Here we maintain the calculation for all condition types and group together all required condition types for our pricing procedure.

7. Schema Determination

Here we maintain the pricing procedure for purchasing document. We maintain calculation schema combination of per each vendor – schema group and each purchase organization – schema group.

In general, below image will give the concept how a condition type will search for the condition records :

Configurations:

Step 1 : Maintain Condition Table

T-code M/03 or Path SPRO-IMG-MM-Purchasing-Conditions-Define Price Determination Process-Maintain Condition Table-Create condition table.

The initial screen will be appear for create condition table.

Give the new condition table no. You can use old condition table number as reference. To give reference just give the old condition table number in below “copy from condition table”.

Note: As per standard SAP, they give the entire condition table for general business requirement. If any condition table doesn’t fulfill your requirement, then you can create new condition table. Please use between 501 to 999 as condition table.

Now press enter

You can see the left side will be blank in initial screen, Right side will be always filled. Just double click on the right side field which you can add for this condition table.

When you double click the field the field will be blue colour and the field is appear in left side.

As we can see the 1 field I have selected in this condition table.

Save your data.

You can change the option as per your business requirement. For more details for these options, just press F1 on these option, you will find sap help doc.

Step 2: Maintain Access Sequence

T-code M/07 or path SPRO-IMG-MM-Purchasing-Conditions-Define Price Determination Process-Define Access Sequences.

The initial screen will appear.

You can create a new access sequence or maintain the condition table in existing access sequence (depend on your business process)

If you want to create then click New Entries. (Or you can use copy reference, Just select the access sequence and press Copy as…)

Enter your Access Sequence and give the description and also you can choose Access category.

Then select the AS and double click on Accesses

Click on New Entries

Enter the access number, condition table and if required the give routing number and Exclusive.

If you tick exclusive indicator, then if valid condition record found then system will stop searching after the first.

Choose as per your requirement.

Then select the line item and click on the fields (left side) to activate the condition table in access sequence. You do not need to do anything here, just double on the fields and go back. If you will not do that, then your condition table will be not accessible. You can add more condition table (s) on this access sequence.

Save your data.

Step 3: Maintain Condition Type

T-code M/06 or path SPRO-IMG-MM-Purchasing-Conditions-Define Price Determination Process-Define Condition Types-Define Condition Type

The initial screen will be appear 

As for gross price SAP default maintain as PBXX for time independent condition and PB00 for time dependent condition.

Time Independent condition is use with validity period, which can be differ as validity period (we use it in info record, RFQ, Contract, SA(as per configuration for document type)).

So we don’t need to create new condition type for gross price, although you can create your own starting with Z.

Assign you newly created access sequence to the gross price condition type (I have maintain in for PBXX)

Here you can find all types of condition type like as freight, discount, rebate, cash discount etc. If it can fulfill your requirement, then no need to create new condition type. If doesn’t the go for New Entries.

Here I have maintain ZCAH as discount, I give condition class A, Calculation type A, Plus/Minus X-Negative

(Note: Not required to maintain like that, you can maintain as per your requirement.)

As per this way please create other condition types as per your requirement (which will be used in Pricing Procedure)

Save you data.

Step 4: Maintain Calculation Schema

T-code M/08 or path SPRO-IMG-MM-Purchasing-Conditions-Define Price Determination Process-Define Calculation Schema

This is very very important part in pricing procedure.

Here we give the calculation for all condition types.

Here also you can find the SAP default calculation schema, you can also use one of them as your pricing procedure. Although you can create new calculation schema as per your requirement.

Just click on New Entry. (or you can copy old schema and can modify yourself. then select copy as…)

Give the name and description for new procedure.

Then Select this procedure and press Control (in left side)

You can see a lots of option there, You can read all option help which is provide by SAP (Just select the portion and press F1)

Maintain PBXX as gross price in step 1, counter 1, leave the from and to blank, Subtotal will be value 9-Copy values to KOMP-BRTWR (gross value).

Maintain other condition types as per your requirement.

I have maintained ZCAH and ZCAS, I have used from 1, it means it will calculate the value against Gross Price (PBXX)

I have used Total Discount amount, from 7 to 9, It shows the total discount value (Total of ZCAH and ZCAS)

At last I have used TOTAL AMOUNT, It shows net value for this pricing procedure.

Step 5: Maintain Schema Group for Vendor

T-code OMFN or path SPRO-IMG-MM-Purchasing-Conditions-Define Price Determination Process-Define Schema Group-Schema Groups: Vendor

Just click on New Entries and enter the Schema Grp Vndr and give the description.

Here I have maintained Z1.

Step 6: Maintain Schema Groups for Purchasing Organizations

T-code OMFM or path SPRO-IMG-MM-Purchasing-Conditions-Define Price Determination Process-Define Schema Group-Schema Groups for Purchasing Organizations

Just click on the new entries and enter the Schema GrpPOrg and description.

Here I have maintained ZMM1.

Step 6: Assign Schema Group to Purchasing Organization

T-code OMFP or path SPRO-IMG-MM-Purchasing-Conditions-Define Price Determination Process-Define Schema Group-Assignment of Schema Group to Purchasing Organization

Here find your Purchase Organization, and assign Schema GrpPOrg to Purchase organization.

Step 7: Maintain Schema Determination

T-code OMFO or path SPRO-IMG-MM-Purchasing-Conditions-Define Price Determination Process-Define Schema Determination-Determine Calculation Schema for Standard Purchase Orders

Step 8: Assign Schema group to Vendor

When you are going to create a vendor from XK01 in purchasing data you will find “Schema Group, Vendor”

Here assign the schema group which you have created on step 5.

You can also maintain it on existing vendor via XK02.

Step 9: Maintain Condition Record

T-code MEK2

Maintain the condition record against the key combination.

Save your data.

Finally all configurations has been done.

Now see the result.

Create PO with this purchase organization and with this vendor.

We can see the my new pricing procedure is working perfect.

We can use this in SA.

Just we have to configure this for document of schedule agreement.

Go to path SPRO-IMG-MM-Purchasing-Scheduling Agreement-Define Document Types

Just un-tick Time Dep. Condition for SA document type.

Then Create SA for this vendor and purchasing organization.

This is called time independent condition. You can also use this pricing procedure for RFQ. But Contract and Info record will be always time dependent condition.

Time Independent conditions are not dependent on time. It hasn’t any validity period, that means it will be always same for all time. The above settings are for time independent condition. Whenever you will use time independent condition, then you need to do these above settings.

Time dependent conditions are always time dependent. It has the validity period. You can use more than one price for the same condition record with different validity period, so that system will change it automatically as per the validity period.

I think I do not need to explain anything more about the differences Time dependent condition and Time Independent condition because there are many discussions already there for the differences.

You can use either time dependent or time independent for Schedule Agreement and Request For Quotation but you can only use time dependent condition for Contract and Info record and for Purchase Order, you need to always use time independent conditions.

For time dependent settings, you just need to set the up the condition type, Access sequence, Condition table and Calculation schema. Schema group is not needed for the time dependent condition.

We can also maintain the fixed discount for particular vendor.

Suppose one of my vendors gives me material as 5 % discount for all material.

We can maintain it in condition record.

Go to MEK2

Click on Supplement Condition. Maintain there your condition type for ZCAH as 5.

You can see the default 5% discount has been automatically arrived in PO or SA.

You can only able to see these condition types which is associated with the condition type which you have entered at the first screen and it will be your gross condition type.

To add some more condition type, you need to add these condition types in the associated calculation schema. To find the calculation schema which is associated with the gross condition type, you need to go to M/06 and you will find the calculation schema as below:

You can add your condition type in this calculation schema in t-code M/08. Then your condition type will be visible for time dependent condition (MEK1) or Info record or Contract.

Continue reading

Workflow in SRM User Interface Add-On 1.0

This blog provides insights about workflow in SRM Shopping Cart UI Add-On, draws parallel with Webdynpro and talks about how different workflow scenarios are incorporated.

To begin with SRM SC UI Add-On supports both AC and PC workflows. There is no additional configuration required. The existing configuration data is read and approver or approval chain is determined.You can also add adhoc approvers and reviewers. Let us take a look at what’s in store for workflow scenarios in SRM UI Add-On.

Approval preview:

The approval preview has a different look and feel as shown below:

Clicking on ‘Add approver’ will open up the following row where you can search for approver via first name, last name or user ID:

Here if you have to add an adhoc approver above current level then you have to choose sequence number as ‘001’ from the drop down; if you want to add approver after current level then you choose sequence number as ‘002’ from the drop down and then click on add to add adhoc approver.

In AC workflow, you can also replace existing approvers.

Workflow scenarios:

• Recall scenario:

Once a shopping cart is ordered, you can edit and recall an awaiting approval cart as shown below:

We do not have ‘show my task’ button in UI addon, but we open an awaiting approval cart directly in edit mode from ‘my carts’ tab when user has recalled that cart and has a valid revision workitem associated with it. This holds good for AC and PC workflow.

PC workflow:

Changed data in carts with PC workflow is saved by using enter key and user can add new items to the cart.

AC workflow:

User has to click on save in order to save changed data and thereby cart will switch to display mode You cannot add new items after recalling an AC workflow cart.

• Inquire scenario:

User can open accept/adjust workitem from Suite Inbox and UWL. You can accept the decision or edit the cart. This holds good only if cart is created from SRM UI Add-On.

UWL configuration:

Please refer note 1892681 to set up UWL for UI Add-On. This configuration is only for employee user. Employee can access Accept/Adjust and Revision workitems from UWL via UI Addon if shopping cart is created in UI Addon. Alternately you can also use Suite Inbox in order to access these workitems.

Continue reading

Steps for opening and closing period – MM FI CO

As many of us struggle with changing periods in our DEV and QA environments, here is quick reference for opening and closing period. In doubt, please consult with your FI/CO expert.

There can be upto four transaction involved depending on your situation.

◉ MMRV – Allow posting to previous period
◉ MMPV – Close Periods
◉ OB52 – Change view “Posting Periods: Specify Time Intervals”: Overview
◉ OKP1 – Maintain Period Lock

1. MMRV: View current period / Allow posting to previous period

This transaction allows you to view current period and change setting for posting to previous period.

2. MMPV: Close Periods

In MMPV you can execute period closing up to the end of the current fiscal year. The period closing program updates the administration record, thus ensuring that the stock data of the material master are updated.

If, for example, you want to close your periods up to 03/2013, you are not allowed to post values in 01/2013. Therefore, if you still want to make postings in period t, you should execute period closing only for a maximum of t+1 periods.

3. OB52: Change view “Posting Periods: Specify Time Intervals”: Overview

In this activity, you close the posting periods for FI-AA and open the new periods for FI-AA.

No more FI-AA postings can be made to the previous period. Postings for the future periods are allowed.

4. OKP1: Maintain Period Lock

If needed, unlock period for CO transaction.

If I have missed anything here or misinterpreted, let me know and I will correct it or add additional clarification/tips.

Continue reading

SAP BO Webi report development on HANA views

SAP BO Webi report development on HANA views:

This document explains step by step creation of Hana views, Universe in IDT and development of Webi report on top of the Hana views universes. This document will give understanding of the complete development/creation of end to end scenario from Hana views to report.

In this scenario we are considering Purchase application flow and analysis of report for purchase users assuming that Purchase related data extracted thru SLT from ECC system.

Applications & Versions used for this scenario:

SAP Hana Studio 2.0.7

Information Design Tool 4.1

SAP BO Webi 4.1

This Document explains below major topics:

1. Creation of Attribute View
2. Creation of Analytical View
3. Creation of calculation View
4. Creating and Publishing universe using IDT (Information Design Tool)
5. Creation of Webi Report

Extracted Purchase order header, Item and account assignment tables and also Material, Vendor, Company code and G/L account master data tables in to HANA from ECC using  SLT.

As a best practice need to follow the proper naming conventions for creating any views. (ex: Attribute view –starting with AT followed by table name)

1. Creation of Attribute View:

1.1. Select the respective package –>  Right click –->  New a Select Attribute View

1.2. Select the Mara table from the schema and drop it in Data Foundation in view and double click on the selected fields for output display.

Save and activate the view. Attribute view AT_MARA created on Material Master data table – Mara:

Similar way creates other attribute views and by selecting the respective master data tables from the schema, and enable the fields which we want to see in output in each view for below.

Vendor Master – LFA1 – Attribute View

Material Master – MARA – Attribute View

Company Code master – T001 – Attribute View

G/L Account master – SKB1 – Attribute view

Once all attribute views are created it displays as below:

2. Creation of Analytical View:

Below Purchase order tables are from ECC thru SLT.

EKKO : Purchase Document Header

EKPO : Purchase order Item

EKKN : Purchase Data (Account Assignment)

2.1. Right click on your package — Select New – Analytical View:

Enter the details

2.2. Drag the EKKO table in to data foundation and AT_LFA1 and AT_T001 attribute views in to star join.

Join the appropriate fields of EKKO table with both attribute views based on the requirements.

EKKO.company_code = AT_T001.Company_Code

EKKO.vendor = AT_LFA1.Vendor

2.3. In Semantics keep the Key fields, correct the Attributes and measures if required.

Save and activate the view.

Similarly create the other two Analytical views, all three analytical views will displays as below:

3. Creation of Calculation View:

3.1.  Right click on your package — Select New – Calculation View:

Drag two Aggregation nodes and select AN_EKKO and AN_EKPO analytical views in each node respectively.

Select required output fields in each Analytical view

3.2. Connect the two aggregation nodes to Join Node and connect the related common fields.

Drag the Projection node and select required fields.

3.3 Select the key fields and adjust the dimensions and measures.

Save and activate the view.

Right click on the view and select Data Preview, we can see the data output of calculation view CL_Purchase

Now Calculation view is ready need to create universe to expose this data thru webi report.

4. Creating universe using IDT (Information Design Tool)

4.1.  Logon to IDT, In Repository Resources under the respective system expand right on Connections Node.

Select ‘Insert Relational Connection’

Enter the connection name:

Click on Next, and then select the database middle ware drivers under SAP node

Click on Next, and then enter the User name, password details of Hana system and click on Test connection button.

Then click on Finish, Now connection established to Hana system.

Expand the Connections node there we can find the new connection ‘Purchase_Flow’.

4.2. Create project ‘Purchase_Flow’ by clicking on File à Newà Project and enter the project name.

Click on Finish. New project ‘Purchase_Flow’ created in Local Projects node.

4.3. Now select Purchase_Flow connection, right click and click on ‘Create Relational Connection Shortcut’.

It will popup Select a Local Project window; select our ‘Purchase_Flow project.

Relational Connection connected to project as shown below:

Select Project à right click à select New Click on ‘Data Foundation’

Enter the name of Data Foundation

Select Multi Source Enabled as IDT will support.

Check for the user authentication details..

Click on Next and select the connection which was created earlier.

Click on Next, displays the connection parameters.

Click on Finish.

Open the Purchase_Flow_DF, expand the connection node, select _SYS_BIC  schema node where all Hana views columnar table will store. Select the CL_Purchase Calculation view table.

Save it.

4.4. Now create Business layer. Select Purchase_Flow project Right click à New à click on Business Layer.

It displays the below pop up screen

Select Relational Data Foundation and click on Next.

Enter the Name and click on Next

Select the respective data foundation and click on Finish. There is check box if system will create classes and objects, if you want to create on your own need to un check this.

Purchase_Flow_BL business layer created as below, review dimensions and measures change if required.

Select change the data type if necessary

Save the Business Layer. We can check the query output by clicking on Queries tab.

4.5. Click on Insert Query, it will add displays the classes and objects of Business layer

Drag and drop required fields to click on refresh to check the data in first instance.

Close the query.

4.6. To publish as universe Right click on Purchase_Flow_BL business layer à Publish à To a Repository

Click on Next

Click on Next

Click on Finish, Universe published successfully.

5. Creation of Webi Report :

Open BI Launch pad by entering the login credentials

Expand Application and select Web Intelligence

Click on New and select ‘Universe’ as data source.

Select our Universe from the list

Purcahse_Flow_BL universe will open in Query Panel as below:

Drag and drop required dimensions and measures in Result objects and if you want to filter any filed also.

Query filtered based on Vendor, Click on Run Query, pop up display to select Vendor to see the data.

Once required Vendors are selected click on Ok, report will display.

Change the Report Name as Purchase Data Flow Report

You can format the report with Refresh Date, page no, logo and chart as per requirement.

Continue reading