ABAP, NetWeaver, ERP Tutorial

I found a very interesting question on SAP SD Pricing from SDN. I quoted it below.

"Requirement: Packing fee to be charged to customers on sales orders. The way the condition type is configured is % based. The problem is when the value of the order goes up as the calculation is % basis there is no limitation for the packing fee to be charged for the order i.e. 30 $ (Max. Limit). I need to come up with a work around where in if the calculated value based on % is higher than 30 Dollars then the value should be restricted to 30 $ not more than that. If the value is below 30 then no changes are expected.
If there are two line items system should distribute the 30$ across two line items under Packing fee condition type."

I extended this requirement by define below rules to determine the packing fee.

For example, the customer place a sales order valued $2000. Use above matrix, the packing fee is 100 * 2% + 900 * 1.5 % + 1000 * 1% = $25.5.

Read more…

Sometimes,user have the requirements to set a range for specific condition type.

There are two ways to control this.

First way,control price in VK11,VK12.Just click Go to->Detail

you can set the limits on the screen.

Read more…

Question: When I look at conditions on the line item, press ‘Access’ button, I get the message ‘No price determination analysis available’. How can I analysis price determination in CRM?

Answer: Go to SU01. Enter your user id. Click parameter tab, add parameter ‘PRC_TRACE’ and value ‘X’. This will solve your problem.

If you create a purchasing document, the system attempts to find a price for the material to be procured. The system always searches from “specific” to “general”. When you create a purchase order, the system searches for an info record for the vendor/material combination at purchasing information level/plant level. If there is no specific data for the purchasing organization/plant combination, it searches at purchasing organization level. If there is no data here either, you must enter the price manually.

Hint: In the purchase order, the valuation price from the material master record is not proposed as the purchase order price.

If a purchasing info record exists, then valid conditions have priority during price determination. If an info record does not contain any conditions or only contains invalid conditions, the system reads the number of the last purchasing document in the info record and then proposes the price from this document. The prices determined in this way are default values that can be changed by the buyer if necessary.

In the default values for buyers (Customizing), you can define how the system handles conditions from the last purchase order. To transfer conditions from the last purchase order, you can specify the following:

- The conditions are always copied

- The conditions are not copied if the price is entered manually

- The conditions are never copied

If using BAPI ‘BAPI_PO_CREATE1‘, import parameter ‘NO_PRICE_FROM_PO‘ can be set with value ‘X’. If the flag is set, no price is coming from last po. The po price is then adopted by manual input price.

All the condition records are stored in table KONH(Conditions Header),KONP(Conditions Item),KONM(Conditions 1-Dimensional Quantity Scale). Condition table like A017(A***) has a field named KNUMH which is the primary key of above condition record table.

Table KONV is used to store the condition transaction data. Field named KNUMV is used to connect table VBAK and KONV.

When define the condition table, we can mark one or serval fields with tool icon. Like pic below:

Read more…

SAP Internet Pricing and Configurator (SAP IPC) is used in numerous SAP applications to configure products through the Internet. SAP IPC belongs, technically speaking, to SAP Customer Relationship Management (SAP CRM), but it can also be installed separately on its own database (“standalone”).

As of SAP CRM 5.0 the SAP IPC 7.0 is a component of the Application Platform (AP). Compared to the previous release that is SAP IPC 4.0, the technology has been switched to SAP Virtual Machine Container (VMC), which is part of the SAP Web Application Server (SAP Web AS) and SAP NetWeaver 2004s. Installation of a separate database is not required as SAP IPC 7.0 is moved to the SAP Web AS. This was done in order to use VMC.

IPC supports the same functionality like R/3 pricing and VC(variant configuration) and it is the first Java applicaiton that runs in the VMC(virtual machine container). It comprises below parts:

• SCE Sales Configuration Engine
• SPE Sales Pricing Engine
• PME Product modeling Environment

IPC also contains an JSP application that is integrated into ERP ECO and CRM web channel. Use this JSP application, internet customer can easy configure an configurable material in the browser.

This post will only focus on the technical perspective of SD pricing. Condition technique has many uses in SAP, the most import part is in pricing. I will post a new blog about how to add custom condition type to pricing procedure.

Program:

SAPMV45A. This is the entry point of sales document process like tcode VA01,VA02 and so on. The two userexit in this program for pricing is:

USEREXIT_PRICING_PREPARE_TKOMK This userexit is used to fill custom field of pricing communication structure in header level.

USEREXIT_PRICING_PREPARE_TKOMP This userexit is used to fill custom field of pricing communication structure in item level.

Read more…

SAP CRM uses IPC to determine pricing information when creating a business transaction, such as a quotation, sales order, service process or a contract. For example, the system automatically determines the gross price and the discounts and surcharges that are relevant for a specific customer or for a particular date, in accordance with the valid conditions.

From a technical point of view, pricing in CRM still use condition technique to perform pricing. Here you can find a link about condition technique and the process when determining the price.

Reference

http://help.sap.com/saphelp_crm60/helpdata/en/51/0302403d62c442e10000000a1550b0/frameset.htm

If your company has already got ERP system online, you can direct download the configuration data to the CRM system using CRM middleware. The configuration data contains pricing procedure, condition type, access sequence. The condition master data can also be downloaded to the CRM side. If your company uses the standalone CRM system, the consultant will need to configure everything in CRM directly.

Read more…