Pricing in NF metal processing

Hi all,
We have activated ECC-DIMP (Release 603 & Level 002) component for our existing customer.
We want to use 'NF metal processing' functionality in purchasing. We are not able to find standard pricing condition types NFM0 & NFM5 in SPRO which are mentioned in help.sap.com.
Reference: http://help.sap.com/saphelp_dimp50/helpdata/EN/4e/1796374b088e5ce10000009b38f8cf/frameset.htm
Pls let me know what needs to be done to make these standard NF condition types available in our system (like activating any add on's).
Also it would be of great help if you could forward me the configuration guide and any help documents (other than link for help.sap.com) for 'NF metal processing' functionality to my gmail id coolsara2000.
Warm regards,
P.Saravanakumar.
Mobile - 91 99760 17055.

hello,
Table:        T685
should contain the NF entries:
MANDT KVEWE KAPPL KSCHL KOZGF DATVO DTVOB J_3GPRAEND J_3GBUARTL J_3GBUARTB VTEXT
   720   A     V     NFM0         5     4                0          0          Gold Notierung
   720   A     V     NFM1         5     4                0          0          Gold Basiswert
   720   A     V     NFM2         5     4                0          0          Gold neg. Basiswert
   720   A     V     NFM3         5     4                0          0          Gold Berichtsbasis
   720   A     V     NFM4         5     4                0          0          Gold neg. Ber.basis
   720   A     V     NFM5         5     4                0          0          Kupfer Notierung
   720   A     V     NFM6         5     4                0          0          Kupfer Basiswert
   720   A     V     NFM7         5     4                0          0          Kupfer neg.Basiswert
   720   A     V     NFM8         5     4                0          0          Kupfer Berichtsbasis
   720   A     V     NFM9         5     4                0          0          Kupfer neg.Ber.basis
   720   A     V     NFMA         5     4                0          0          Kupfer gewichtsabh.
   720   A     V     NFMP PR00                          0          0          Metallpreis gew.abh.
this is an extract of a demo system (not a cust. shipment system !)
If the NF' entries are there, it is only a customzing issue.
Regards,
Stefan Haag

Similar Messages

How to activate NF Metal Processing for SD?

Hi,
how can we activate NF Metal Processing for SD??
(We have a demo ECC 6.0 and EHP)
Thanks

hi
Purpose
This scenario includes three sub-scenarios which cover procurement non ferrous material for the warehouse, sales of non ferrous material with two pricing strategies, one is weight dependent and the other one is not weight dependent.
Function List
The following functions are provided to support the Non Ferrous Metal Processing building block:
Sub-scenario 1: Purchasing Non-Ferrous Processing (Weight-Dependent)
Purchasing order creation
Goods movement
Invoice verification
Sub-scenario 2: Non-Ferrous Processing (Non Weight-Dependent)
Initial stock
Sales order creation
History of coverage
Delivery processing
Goods issue
NF rate maintenance
Billing
Sub-scenario 3: Non-Ferrous Processing (Weight-Dependent)
Initial stock
Sales order creation
Delivery processing
Goods issue
Billing
Key Points
Supports various rate determination processes for NF metals traded on stock/metal exchanges using the condition technique.
NF metal coverage is an agreement to invoice a customer for a specific NF metal quantity within a specific period at a specific rate. It also contains coverage used history.
BB:
http://help.sap.com/bp_metalsv1600/Metals_DE/html/M87_EN_DE.htm

NF Metal processing functionality

Hi all,
We have activated ECC-DIMP (Release 603 & Level 002) component for our
existing customer.
We have materials already created with material types ROH, HALB, FERT
etc,.in the system. We want to use the "NF metal Processing"
functionality for these already existing materials.
But We dont have the option of entering NF metal details in material
master for such materials with material types ROH, HALB, FERT etc,.
(except MCRO, MCHF, MCHA and MCFE)
FYI - As per our analysis in configuration, "processing routines"
relevant for "NFmetal processing" are assigned to the "screen sequence"
relevant to material types MCRO, MCHF, MCHA and MCFE.
But system is not allowing to assign the processing routines relevant
to NF metal processing to the 'screen sequence' relevant to material
types ROH, HALB, FERT etc.,
Hence pls let us know if "NF metal processing fucntionality" is
supported for material types other than MCRO, MCHF, MCHA and MCFE.
Thanks.
Warm regards,
P.Saravanakumar.

Hello,
> my case I have activated DIMP 6.0 in our ecc 6.0 ides but do not see MCFE and other cable material types?
> How do we activate those?
If you do not see in MM01 these types, then i think it might be, that these material types are only in client 000 ?
> Any steps for creating these mat types and assiginig screen sequence or control?
We do not have any "how to description".
In our Mill IDES system e.g. a consultant enhanced material type FERT for NF...
If you intent to enhance existing materials with NF functionalty, then you need to adapt the Customizing of material master.
I agree to the feedback of my support colleague in message 244387:
"There is no note as such that you are looking for. The customizing of
screen sequence for material master is done quite often by customers/
consultants for which there are extensive online help available as well
on www.help.sap.com"
"Modifying the standard screen sequence is not allowed. In this case
you are trying to modify screen sequence 01 to add NF related
sub-screens. Instead why don't you use the existing screen sequence DI,
that has the necessary settings for NF sub-screens. You can then use
the customizing setting: SPRO: Logisitics - General -> Material Master
-> Configuring the material master -> Assign Screen Sequences to User/
Material Type/Transaction/Industry Sector and assign the material types
that you want to have NF screens to screen sequence DI.
If this approach is also not suitable for you, then I request you to
create a Z screen sequence (customer specific)."
Greetings,
Stefan Haag
IBU Mill Products & Mining

Pricing procedure in subcontracting process

Dear gurus,
Is there any difference between standard Pricing procedure and sub contracting pricing procedure. If there is any kindly explain the steps of configuration.
Regards,
Prashanth

Hi,
you can use subcontracting info records. Please check ME1M and CK11N transactions for your material.
Please read the note 597686 in case import is involved in your process.
Regards,
Edit

NF metal pricing

Hi all,
We have activated ECC-DIMP (Release 603 & Level 002) component for our existing customer.
We want to use 'NF metal processing' functionality in purchasing. We are not able to find standard NF pricing procedure NFM000 and NF condition types NFM0 & NFM5 in SPRO which are mentioned in help.sap.com.
Reference: http://help.sap.com/saphelp_dimp50/helpdata/EN/4e/1796374b088e5ce10000009b38f8cf/frameset.htm
Pls let me know what needs to be done to make these standard NF pricing procedure NFM000 and NF condition types NFM0 and NFM5 available in our system (like activating any add on's).
Also it would be of great help if you could forward me the configuration guide and any help documents (other than link for help.sap.com) for 'NF metal processing' functionality to my gmail id coolsara2000.
Warm regards,
P.Saravanakumar.
Mobile - 91 99760 17055.

Hi all,
We have activated ECC-DIMP (Release 603 & Level 002) component for our existing customer.
We want to use 'NF metal processing' functionality in purchasing. We are not able to find standard NF pricing procedure NFM000 and NF condition types NFM0 & NFM5 in SPRO which are mentioned in help.sap.com.
Reference: http://help.sap.com/saphelp_dimp50/helpdata/EN/4e/1796374b088e5ce10000009b38f8cf/frameset.htm
Pls let me know what needs to be done to make these standard NF pricing procedure NFM000 and NF condition types NFM0 and NFM5 available in our system (like activating any add on's).
Also it would be of great help if you could forward me the configuration guide and any help documents (other than link for help.sap.com) for 'NF metal processing' functionality to my gmail id coolsara2000.
Warm regards,
P.Saravanakumar.
Mobile - 91 99760 17055.

Step by Step process for Pricing in SAP

Hello Experts,
Can any one please send me the documentation for whole process of pricing in SAP , So that it will explain me how it works in SAP.
I don´t need the steps for the configuration.
Thanks

Hi
Pricing and Conditions
The term pricing is used broadly to describe the calculation of prices (for external use by customers or vendors) and costs (for internal purposes, such as cost accounting). Conditions represent a set of circumstances that apply when a price is calculated. For example, a particular customer orders a certain quantity of a particular product on a certain day. The variable factors here - the customer, the product, the order quantity, the date - determine the final price the customer gets. The information about each of these factors can be stored in the system as master data. This master data is stored in the form of condition records.
refer link below
<a href="http://www.sap-basis-abap.com/sapsdlog.htm">PRICING</a>
PRICING:
Pricing is the combination of creating correct pricing procedure that map the business needs & processes, such as correct pricing & discounting, & keeping to the legal requirements placed on the business, such as adhering to the tax laws of the country.
SPRO- IMG- SD- Basic Functions- Pricing- Pricing Control
Create Condition Table: V/03, V/04, V/05
Define Access Sequence: V/07
Define Condition Types: V/06
Define & Assign Pricing Procedure
Maintain Pricing Procedure: V/08
Define CuPP: OVKP
Define DoPP: OVKI. The DoPP indicator is used to determine pricing in conjunction with the sales area & CuPP.
Assign DoPP to Order Types & Billing Types: OVKJ & OVTP
Define Pricing Procedure Determination: OVKK
Create Condition Table: V/03, 04, 05
Put the most general field for e.g., Sales Orgn in the highest position & the most specific field in the lowest. After organizational fields, place fields from doc header before those that come from item level (customer comes before material).
Sales Orgn, Distbn Channel, Div, Cust, Mat: Customer Specific Price
Sales Orgn, Distbn Channel, Div, Price List Type, Mat: Price List
Sales Orgn, Distbn Channel, Div, Mat: Material Price.
Maintain Access Sequence: V/07
Go to new entries, define 4-digit acc seq. Select acc seq, go to Accesses and place the cond tables and check exclusive indicator (which determines that if a cond record is successfully found, the system will stop searching further). Select each cond table and go to Fields.
There are some cond types for which you do not create cond records (header discounts that you can only enter manually). These cond types do not require an access sequence.
Define Condition Type: V/06
They are used in the pricing procedure to define how the cond is going to perform, such as either a %tage or a fixed amount. The cond type can be automatic or it can allow manual changes. Copy the required cond type and rename. Then assign acc seq to cond type.
If you use different calculation types for what are otherwise the same conditions (for e.g., %tage, as fixed amt, qty dependent), you do not have to define different cond types in customizing. You can set different calculation type when maintaining cond records.
Functionality of Condition Types:
Access Sequence
Condition Class: surcharge & discounts or prices
Plus/Minus: -ve, +ve or both
Calculation Type: fixed amt, %tage, qty, wt, voln
Rounding rule: commercial, round up and round down
Group Cond
Manual Entry: whether manual or automatic entry has priority
Header Cond: after entering the header cond type click on the button activate. The cond amt of the header conditon is copied as it is to all the line items in the doc.
Item Cond
Amount/ Percent: check & u can change the amount or % for the cond type during data processing
Delete: check & the cond record may be deleted from the doc.
Value: check & the value of the cond type can be changed during data processing
Calculation Type: check & the cal type can be changed during doc processing
Valid from & to
Scale Basis: determines how the system interprets a pricing scale in a cond, for e.g., the scale can be based on qty, wt, voln
Check Value: indicates whether the scale rates must be entered in ascending or descending order.
Define and Assign Pricing Procedure: V/08
A pricing proc consists of a lists of cond types in a defined order, such as price less discount plus tax. Go to new entries, define 6-digit pricing proc with descp. Select the 6-digit pricing proc and go to Control Data, you will be faced with an empty structure.
Step: the no that determines the sequence no of a cond type with in a procedure
Counter: second mini step with in an actual step
Conditon type: specify the cond type
From & To: if you specify the ref steps in these fields, the cond values of the 2 steps specified and steps in between are totaled
Manual:
Mandatory: whether a cond type is mandatory when system carries out pricing
Statistical: the value represented in this step will not alter the overall value
Print: which cond types should be printed on a doc (order confirmation, invoices)
Subtotal: controls whether & in which fields the cond amts or subtotals are stored
Requirement: for a cond type to be executed in the sales doc the requirement specified here must be satisfied. (It is a gateway)
Alternative Calculation Type: alternative formula to the formula in the std system that determines the cond. In the std SAP system for the cust expected price EDI1, the alt cal type is 9, which means it contains a routine with a logic which states that the difference between the customer expected price & the net value is zero.
Alternative Cond Base Value: alternative formula for determining the cond basis (amt to which the discount or surcharge in a scale refers)
Account Key: this field enables the system to post the sales value to different G/L accounts. ERL: sales revenues, ERS: sales deductions, ERF: freight revenue.
Accruals: this is exclusively for rebate cond types BO01 & BO02. Key, which identifies various types of G/L accounts for accrual postings.
TAX: MWST
Tax is calculated on the following parameters:
Plant
Ship to party region
Customer tax classification
Material tax classification
Pricing Procedure Determination: OVKK: Determination Rule
Before one can proceed with the determination rule, one needs to maintain the CuPP & DoPP. One needs to assign a single character alphanumeric key with a short descp. Then assign the DoPP to the sales doc types. This will ensure that for e.g., all sales orders created using order type OR, which has been assigned a DoPP of 1, will all use the same pricing proc if created in the same sales area & with the same CuPP. In some instances, you may not want to have the same pricing proc for a sales doc, as you may want in a billing doc. For this reason, you may allocate a different DoPP to a billing doc.
Do not forget to assign the CuPP indicator to your CMD in the Sales Screen
Sales Orgn + Distbn + Division + CuPP indicator + DoPP indicator = Pricing Procedure
To Create own Sales Doc Types:
SPRO- IMG- Sales Doc- Sales Doc Header-
Define sales doc types: VOV8. Copy std order type& rename
Assign Sales area to Sales Doc Types:
Combine sales orgn
Combine Distbn channel
Combine division
Assign sales order types to permitted sales area
To create Price List Types:
SPRO- IMG- SD- Basic Functions- Pricing- Maintain Price Relevant Master Data:
Define price list category for customers: OVSI: assign to CMD sales area screen in price list type field, in sales tab page in pricing and statistics section.
Define pricing group for customers: OVSL: assign to CMD sales area screen in price group field, in sales tab page in pricing and statistics section.
Define material group: OVSJ: assign to sales orgn 2 view of MMR in Mat Pricing Group Field.
2 digits character key with description
Cond Type Description Cond Class Calculation Type
BO01 Group rebate Exp reimbursement Percentage
BO02 Mat rebate Exp reimbursement Qty (fixed)
BO03 Cust rebate Exp reimbursement Percentage
BO04 Hierarchy rebate Exp reimbursement Percentage
BO05 Hierarchy rebate / Mat Exp reimbursement Percentage
BO06 Sales Independent Rebate Exp reimbursement Fixed amount
EDI1 Cust Expected Price Prices Quantity
HB00 Discount (value) Discount / Surcharge Fixed amount
HD00 Freight Discount / Surcharge Gross weight
K004 Material Discount / Surcharge Qty / absolute
K005 Customer / Material Discount / Surcharge Qty / absolute
K007 Customer discount Discount / Surcharge Percentage
K020 Price group Discount / Surcharge Percentage
K029 Material Pricing Group Discount / Surcharge Absolute discount by wt
K030 Customer/ Mat Group Discount / Surcharge Percentage
K031 Price Grp/ Mat Pr Group Discount / Surcharge Percentage
K032 Price Grp/ Material Discount / Surcharge Quantity / absolute
KF00 Freight Discount / Surcharge Gross weight
NRAB Free Goods Discount / Surcharge Quantity
PI01 Inter company price Prices Quantity (fixed)
PI02 Inter company % Prices Percentage
RB00 Discount / value Discount / Surcharge Fixed amount
PR00 Price Prices Quantity
VPRS Cost Prices Quantity
RL00 Factoring Discount Discount / Surcharge Percentage
MW15 Factoring Discount Tax Taxes Percentage
SKT0 Cash discount
Customer Specific Price: sales orgn, distbn, division, customer & material
Price List Price: sales orgn, distbn, division, price list type & material
Material Price: sales orgn, distbn, division & material
Customer discount: sales orgn, distbn, division & customer
Customer material discount: sales orgn, distbn, division, customer & material or sales orgn, distbn, customer & material.
Material discount: sales orgn, distbn, division & material or sales orgn, distbn & mat.
Condition Records:
Condition records allow you to store & retrieve pricing data in the system. Pricing elements are generally managed at the sales orgn & distbn channel level. There fore you always have to specify organizational level when creating cond records. In the case of cond records for price groups, freight charges, & cust specific prices & discounts you must also enter the division. As a result, you can create conditions according to product groups with these price elements.
Pricing Elements in Sales Order:
Price: the basis of pricing during sales order processing is the gross price of the mat. The system selects the most specific record- the cust specific price. If it does not exist, the system looks for price list type. If it also does not exist then system takes the basic material price. You can define price list types by customer groups (wholesale or retail) or by currency (price lists for each foreign country dealt with)
Surcharge & Discounts:
Freight Costs: you can create cond record either based on: the first part of the inco term (for e.g. FOB) or on the combination of part 1 & 2 (for e.g. FOB & Boston). There are 2 predefined freight conditions
o KF00: applies to each item in a sales doc.
o HD00: applies to entire document.
Sales Taxes:
Prerequisites for Automatic Pricing:
Necessary data must be maintained in MMR & CMD:
Material Master Data: the price related fields can be found in sales orgn 1 & 2.
Tax Classification
Price Material: you can specify another material as ref for pricing info
Material Group: defines a group of materials for which you want to apply the same cond record.
Cash Discount: whether or not mat qualifies for cash discount
Customer Master Data: the price related fields appear on sales data screen.
CuPP: specify the pricing proc for a customer
Price List: Allow you to apply a mat price in a particular currency to a group of customers e.g. wholesale customers.
Price Group: price group lets you apply a discount to a particular group of customers.
Tax Classification: billing tab page.
HEADER & ITEM CONDITIONS:
The standard system includes cond types that you can apply at only the header level, the header conditions. Cond types that you can only use for items are called item conditions. There are some cond types that can be used at both header & item level:
RA01: percent from gross
RB00: absolute discount
RD00: weight discount
Header Conditions: you cannot create cond records for it; it is entered manually in order processing. Automatic pricing does not take place for them.
HA00: percent discount
HB00: absolute discount
HD00: freight
HM00: order value
Item Conditions: in the std SAP most cond types are defined as item conditions:
K004: mat discount
K005: cust/ mat discount
K007: cust discount
PR01: mat price
KF00: freight
Distribution between Header & Item:
Header conditions apply to all items in the doc & are automatically distributed to all the items. It can be either percentage or an absolute amount.
If you enter a header cond that is based on a percentage (e.g., a dis of 2% ) the system automatically applies this percentage to all the items in the doc.
If the header cond is an absolute amount, there are 2 ways in which the system can distribute the amount among the items in the doc:
Distributed proportionally among the items
Amount entered at header level is duplicated for each item.
You control the distribution of absolute header condition in the Group Price Field per cond type.
HB00: header discount distributed as percentage because it is marked as a header cond & group condition. The system distributes the amt proportionally among the various items, in this case according to the value of the items. The distribution of an absolute header cond need not be based on value. For e.g. you can specify in customizing for sales that the distribution is based on weight & volume of the different items. You can specify the basis of distribution in the Alternative Cond Base Value field in the pricing screen.
RB00: assigns the header discount to each item identically, because it is only marked as header condition.
<b>
REWARD IF HELPS</b>
Message was edited by:
SHESAGIRI GEDILA

Sale order- Pricing -Access Sequence

Hi Gurus,
While creating Sale order, the price is picked from the Pricing procedure and Condition records maintained.
In PR00- Material price and Customer-Material special price is maintained in VK11.
So the system picks Customer Material combination price and the same we can see in the Item level conditions-Analysis for pricing and can also see it fetched record from where.
So for this Client wants in the following way: POPUP MESSAGE
At Sale order Warning Message that Price is taken from Which List- Normal Price List or Special Price List for Customer and Material combination
Is there some way to do this?
Thanks in Advance.
Best Regards
Sri

Hi,
U have to take ABAPER HELP No doubt please use this input if tis use full .
User Exits For Price Determination
USEREXIT_PRICING_PREPARE_TKOMK (module pool SAPLV60A, program RV60AFZZ)
This user exit allows you to copy additional fields for pricing in the TKOMK communication structure (header fields), which have not been provided in the standard SAP system. These fields can also be used for pricing in the billing document.
This user exit is described in detail in the "New fields in pricing" section.
USEREXIT_PRICING_PREPARE_TKOMP (module pool SAPLV60A, program RV60AFZZ)
This user exit allows you to copy additional fields for pricing in the TKOMP communication structure (item fields), which have not been provided in the standard SAP system. These fields can also be used for pricing.
This user exit is described in detail in the "New fields in pricing" section.
USEREXIT_FIELD_MODIFICATION (module pool SAPMV61A, program MV61AFZA)
You can use this user exit to adjust the display of individual lines in the condition screen by changing the display attributes of the screen fields. This does not include the display of subtotals.
This user exit is also used in order processing.
USEREXIT_FIELD_MODIFIC_KZWI (module pool SAPMV61A, program MV61AFZB)
You can change the display of subtotals in the condition screen by changing the display attributes of the screen fields.
This user exit is also used in order processing.
USEREXIT_FIELD_MODIFIC_KOPF (module pool SAPMV61A, program MV61AFZB)
You can adjust the display of subtotals in the condition screen to your requirements by changing the display attributes of the screen fields.
This user exit is also used in order processing.
USEREXIT_FIELD_MODIFIC_LEER (module pool SAPMV61A, program MV61AFZB)
You can adjust the display of blank lines in the condition screen to your requirements by changing the display attributes of the screen fields.
This user exit is also used in order processing.
USEREXIT_PRICING_CHECK (module pool SAPMV61, program MV61AFZA)
You can install additional checks to the standard checks of condition lines (e.g. maximum/minimum value).
USEREXIT_PRICING_RULE (module pool SAPLV61A, program RV61AFZA)
In the standard SAP system, it is predefined which condition categories and classes can be copied or recalculated per pricing type. You can change the predefined standard procedure for each pricing type.
USEREXIT_CHANGE_PRICING_RULE (module pool SAPMV61A, program MV61AFZA)
You can use this user exit to change the pricing type that has been predefined in the copying control table in billing.
USEREXIT_XKOMV_BEWERTEN_INIT (module pool SAPLV61A, program RV61AFZB)
This field is used in the formulas and therefore initialized before the loop for the pricing procedure starts.
USEREXIT_XKOMV_BEWERTEN_END (module pool SAPLV61A, program RV61AFZB)
Within a loop for the price components during pricing, specific values can be transferred into the communication structures in pricing to be further processed.
USEREXIT_XKOMV_ERGAENZEN (module pool SAPLV61A, program RV61AFZB)
In change mode, you can change the dynamic part of the condition record (KONVD) that is always redetermined (i.e. it is not stored in database table KONV).
USEREXIT_XKOMV_ERGAENZEN_MANU (module pool SAPLV61A, program RV61AFZB)
You can use this user exit to change the ready-for-input fields of the manually entered condition record in add mode in the condition screen.
USEREXIT_XKOMV_FUELLEN (module pool SAPLV61A, program RV61AFZB)
This user exit is always called up during a redetermination of all or individual price components. You can change the work fields of the condition line. However, this only applies to conditions that have been determined via a condition record.
USEREXIT_XKOMV_FUELLEN_O_KONP (module pool SAPLV61A, program RV61AFZB)
This user exit is always called up during a redetermination of all or individual price components. You can change the work fields of the condition line. However, this only applies to conditions that have been determined via a condition record. This may include subtotals, manually entered conditions or conditions that have been calculated with a formula.
USEREXIT_PRICING_COPY (module pool SAPLV61A, program RV61AFZA)
You can change the KONV fields for copied price components
With best regards,
venkataswamy.y

Bare Metal Deployments: The BMC can't have IP Address defined in logical network?

I have defined a logical network, a logical switch, and a port profile. I apply the logical switch (the NIC teaming settings) and a virtual network adapter that inherits the hosts network configuration (pass through config. no software defined networking)
to each of my Hyper-V hosts successfully.
The issue occurs once I have defined that logical network, I can no longer deploy bare metal hosts because the BMC obtains an IP within that logical network. You see the BMC IPs and NICs are on the same subnet/VLAN.
What's the best practice or perhaps best method to get around this issue?

I am not sure if I follow you on this one.
You have created a logical network for your BMC in VMM? If so, why have you done that?
The bare-metal process requires both PXE and
DHCP during this process, and the scope should therefore be in DHCP and not VMM for this purpose.
Can you try to do that? (If this is a lab environment, you could add the DHCP service to your PXE server or even VMM server).
-kn
Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )

Different pricing procedure in sales order and invoice

Hi All,
I have created a new pricing procedure .When i processed it,in sales order its picking the correct PP. but when I check it in excise invoice,its taking other pricing procedure. Where have i missed the settings.Please help

Hi,
We have document pricing procedure maintained at two levels for Sales order or Billing type.
The pricing procedure is determined based on SAles Area Customer pricing procedureDocument Pricing procedure+pricing procedure.
Example :For Sales Document type the document pricing rpocedure will be A and for billing type 'B"
Sales Area1A+Pricing procedure A
Sales Area1B+Pricing procedure B
Now A will be maintained in VOV8 and B will be maintained in VOFA.So two pricing procedures.
Regards,

BAdI for SD Pricing

Hi,
I am investigating various user-exits and special functionality for SD pricing. I don't have any special customer requirements yet, but would like to expand my bag of tricks.
I came across these two BAdIs.
SD_COND_ACCESS_A Access in Pricing (replacement)
SD_COND_SAVE_A Save condition application A, E
Does anyone have experience with them? In what types of situations would they be used?
Thanks,
Ben

Hi Ben,
Iam not sure what these BADIs are used for but defenitely you could go thru the following user exits...for price determinations...
Iam sure one of them can easily satisfy any of the buisness requirements...and you could include a small routine to satisfy your buisness needs...
reward points if it helps
regards
Biju
USEREXIT_PRICING_PREPARE_TKOMK (module pool SAPLV60A, program RV60AFZZ) This user exit allows you to copy additional fields for pricing in the TKOMK communication structure (header fields), which have not been provided in the standard SAP system. These fields can also be used for pricing in the billing document. This user exit is described in detail in the "New fields in pricing" section.
USEREXIT_PRICING_PREPARE_TKOMP (module pool SAPLV60A, program RV60AFZZ) This user exit allows you to copy additional fields for pricing in the TKOMP communication structure (item fields), which have not been provided in the standard SAP system. These fields can also be used for pricing. This user exit is described in detail in the "New fields in pricing" section.
USEREXIT_FIELD_MODIFICATION (module pool SAPMV61A, program MV61AFZA) You can use this user exit to adjust the display of individual lines in the condition screen by changing the display attributes of the screen fields. This does not include the display of subtotals. This user exit is also used in order processing. USEREXIT_FIELD_MODIFIC_KZWI (module pool SAPMV61A, program MV61AFZB) You can change the display of subtotals in the condition screen by changing the display attributes of the screen fields. This user exit is also used in order processing.
USEREXIT_FIELD_MODIFIC_KOPF (module pool SAPMV61A, program MV61AFZB) You can adjust the display of subtotals in the condition screen to your requirements by changing the display attributes of the screen fields. This user exit is also used in order processing.
USEREXIT_FIELD_MODIFIC_LEER (module pool SAPMV61A, program MV61AFZB) You can adjust the display of blank lines in the condition screen to your requirements by changing the display attributes of the screen fields. This user exit is also used in order processing.
USEREXIT_PRICING_CHECK (module pool SAPMV61, program MV61AFZA) You can install additional checks to the standard checks of condition lines (e.g. maximum/minimum value).
USEREXIT_PRICING_RULE (module pool SAPLV61A, program RV61AFZA) In the standard SAP system, it is predefined which condition categories and classes can be copied or recalculated per pricing type. You can change the predefined standard procedure for each pricing type.
USEREXIT_CHANGE_PRICING_RULE (module pool SAPMV61A, program MV61AFZA) You can use this user exit to change the pricing type that has been predefined in the copying control table in billing.
USEREXIT_XKOMV_BEWERTEN_INIT (module pool SAPLV61A, program RV61AFZB) This field is used in the formulas and therefore initialized before the loop for the pricing procedure starts.
USEREXIT_XKOMV_BEWERTEN_END (module pool SAPLV61A, program RV61AFZB) Within a loop for the price components during pricing, specific values can be transferred into the communication structures in pricing to be further processed.
USEREXIT_XKOMV_ERGAENZEN (module pool SAPLV61A, program RV61AFZB) In change mode, you can change the dynamic part of the condition record (KONVD) that is always redetermined (i.e. it is not stored in database table KONV).
USEREXIT_XKOMV_ERGAENZEN_MANU (module pool SAPLV61A, program RV61AFZB) You can use this user exit to change the ready-for-input fields of the manually entered condition record in add mode in the condition screen.
USEREXIT_XKOMV_FUELLEN (module pool SAPLV61A, program RV61AFZB) This user exit is always called up during a redetermination of all or individual price components. You can change the work fields of the condition line. However, this only applies to conditions that have been determined via a condition record.
USEREXIT_XKOMV_FUELLEN_O_KONP (module pool SAPLV61A, program RV61AFZB) This user exit is always called up during a redetermination of all or individual price components. You can change the work fields of the condition line. However, this only applies to conditions that have been determined via a condition record. This may include subtotals, manually entered conditions or conditions that have been calculated with a formula.
USEREXIT_PRICING_COPY (module pool SAPLV61A, program RV61AFZA) You can change the KONV fields for copied price components

InterCO Billing for Stock - Pricing Date

hi,
I have the following problem:
We do an interco sale from the purchase order to delivery to goods issue to billing,
Sometimes and order is placed a couple of moths ago and we need to adjust the price to that date on the Interco billing document, however, the price date the billing document uses is the Actual Goods Issue date from the delivery. The block is greyed out and cannont be changed.
Does anyone know how we can change the pricing date on the item to pick up the correct pricing.

hi,
Our intercomapny process starts with a purchase order. that purchase carries to the delivery the Planned goods issue date. the delivery occurs some time after and the actual goods issue date is captured. the billing document takes the Actual Goods issue date. We want to be able to change that.

Pricing in ERP ISA

Hi experts,
I'm using program ISA_CATALOG_REPLICATION to replicate the product catalog from ERP to TREX (no CRM involved at all). I would like to show zero price for some materials based on material sales data. It's unclear how to achieve this. Is it best to enhance the build catalog program (I have custom program to build the product catalog) or the replicate product catalog program? and how?
Could you please advise the best approach?
Thanks,
Satish

Hi Satish,
Please have a look of the below paragraphs and hope will help you.
USEREXIT_PRICING_PREPARE_TKOMK (module pool SAPLV60A, program RV60AFZZ) This user exit allows you to copy additional fields for pricing in the TKOMK communication structure (header fields), which have not been provided in the standard SAP system. These fields can also be used for pricing in the billing document. This user exit is described in detail in the "New fields in pricing" section.
USEREXIT_PRICING_PREPARE_TKOMP (module pool SAPLV60A, program RV60AFZZ) This user exit allows you to copy additional fields for pricing in the TKOMP communication structure (item fields), which have not been provided in the standard SAP system. These fields can also be used for pricing. This user exit is described in detail in the "New fields in pricing" section.
USEREXIT_FIELD_MODIFICATION (module pool SAPMV61A, program MV61AFZA) You can use this user exit to adjust the display of individual lines in the condition screen by changing the display attributes of the screen fields. This does not include the display of subtotals. This user exit is also used in order processing. USEREXIT_FIELD_MODIFIC_KZWI (module pool SAPMV61A, program MV61AFZB) You can change the display of subtotals in the condition screen by changing the display attributes of the screen fields. This user exit is also used in order processing.
USEREXIT_FIELD_MODIFIC_KOPF (module pool SAPMV61A, program MV61AFZB) You can adjust the display of subtotals in the condition screen to your requirements by changing the display attributes of the screen fields. This user exit is also used in order processing.
USEREXIT_FIELD_MODIFIC_LEER (module pool SAPMV61A, program MV61AFZB) You can adjust the display of blank lines in the condition screen to your requirements by changing the display attributes of the screen fields. This user exit is also used in order processing.
USEREXIT_PRICING_CHECK (module pool SAPMV61, program MV61AFZA) You can install additional checks to the standard checks of condition lines (e.g. maximum/minimum value).
USEREXIT_PRICING_RULE (module pool SAPLV61A, program RV61AFZA) In the standard SAP system, it is predefined which condition categories and classes can be copied or recalculated per pricing type. You can change the predefined standard procedure for each pricing type.
USEREXIT_CHANGE_PRICING_RULE (module pool SAPMV61A, program MV61AFZA) You can use this user exit to change the pricing type that has been predefined in the copying control table in billing.
USEREXIT_XKOMV_BEWERTEN_INIT (module pool SAPLV61A, program RV61AFZB) This field is used in the formulas and therefore initialized before the loop for the pricing procedure starts.
USEREXIT_XKOMV_BEWERTEN_END (module pool SAPLV61A, program RV61AFZB) Within a loop for the price components during pricing, specific values can be transferred into the communication structures in pricing to be further processed.
USEREXIT_XKOMV_ERGAENZEN (module pool SAPLV61A, program RV61AFZB) In change mode, you can change the dynamic part of the condition record (KONVD) that is always redetermined (i.e. it is not stored in database table KONV).
USEREXIT_XKOMV_ERGAENZEN_MANU (module pool SAPLV61A, program RV61AFZB) You can use this user exit to change the ready-for-input fields of the manually entered condition record in add mode in the condition screen.
USEREXIT_XKOMV_FUELLEN (module pool SAPLV61A, program RV61AFZB) This user exit is always called up during a redetermination of all or individual price components. You can change the work fields of the condition line. However, this only applies to conditions that have been determined via a condition record.
USEREXIT_XKOMV_FUELLEN_O_KONP (module pool SAPLV61A, program RV61AFZB) This user exit is always called up during a redetermination of all or individual price components. You can change the work fields of the condition line. However, this only applies to conditions that have been determined via a condition record. This may include subtotals, manually entered conditions or conditions that have been calculated with a formula.
USEREXIT_PRICING_COPY (module pool SAPLV61A, program RV61AFZA) You can change the KONV fields for copied price components
Thanks,
Hamendra

Price Break through the Pricing Agreement API.

Hi All,
I need to put Range price break on the pricing agreement conversion. I am using the OE_Pricing_Cont_PUB.Process_Agreement API to accomplish this, but couldn't find where and What do I need to put to take care of the Price Breaks.
All pointers are highly appreciated.
Thanks,
Rahul

Hi David,
Advanced Pricing comes with 6 x seeded pricing attributes for cross-order volume d-iscounts: Period 1/2/3 Item Qty and Period 1/2/3 Order Amount ... which relate to the tables I mentioned previously.
Those Periods 1, 2 and 3 are based on the values in the 3 profile options I mentioned. So if you have a quarterly volume d-iscount structure you might use 30, 60, 90 as the values (i.e. not 30, 30, 30) which would bucket 1-30, 31-60 and 61-90 and ignore orders older than 90 days.
The Cross Order Volume Load takes place only for booked sales orders containing items/customers which qualify for a modifier/price list using cross-order volume pricing attributes/qualifiers+. To that end, when you're testing this, remember to run QP: Maintains the denormalized data in QP Qualifiers after creating/assigning qualifiers and before running the Cross Order Volume Load.
It is also important to note that the order amounts which are accumulated are gross only – i.e. they are based on the unit list price not the unit sell price post d-iscounts etc. Also, the cross-order amount does not include the current order being priced since the expected process is that the Cross Order Volume Load will be scheduled to run periodically, probably at the end of the business day. (You may feel that these two riders reduce the value of this functionality - they do for me!)
Note that there is also a Cross Order Volume Report which will list the accumulated data from the Cross Order Volume Load for you.
Hope that helps...
Regards,
Jon

Pricing for delivery

Hi,
I have activated the pricing for delivery. But we have self defined fields -partner function- in pricing.
I want to know the user exit for assigning value to the new fields for pricing. Just like the user exit USEREXIT_PRICING_PREPARE_TKOMK in MV45AFZZ for order, in RV60AFZZ for billing. I cannot find the similar one for delivery.
Many Thanks
Jean

Hi Jean,
Please check this user exits <b>MV50AFZP</b>.
This userexit can be used to modify change mode of pricing screens in delivery processing.
Also you can check other user exits MV50AFZ*.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

STO PRICING INTERCOMPANY MANUAL PRICING IN STO also

Hi ,
I know there is lot of info available reg STO on this forums .But i am looking for detailed step by step configuration involved for Pricing in intercompany STO process.If its posted on this forum please provide the link.I will be thankful and full points will be awarded
Please guide me in doing Pricing configuration for intercompany STO process in detail steps. full points will be awarded.
One more thing is I also need detail steps for manual pricing in STO Intercompay process.Please guide me how to proceed
Thanks

Hello,
Is ZPRO is copy of PI01.If yes, make sure Ref cond tab should be blank (V/06).
Check Sequence in your pricing procedure(V/08).Zpro & Zk04 Should be before net value calculation.
If Pi01 is not required then you can determine new pricing procedure in intercompany billing.
Revert if not resolved.
Regards
Amit

Pricing in NF metal processing

Similar Messages

Maybe you are looking for