Scribd
Upload
62 views44 pages

RP - Pawan - Training Notes

This document provides an overview of pricing configurations and concepts in Microsoft Dynamics 365 Business Central. It describes basic and advanced pricing, price lists, pricing formulas, attributes, and debugging pricing issues. Basic pricing uses price lists to determine item prices on sales orders, while advanced pricing uses rules-based pricing engines. Price lists can include defaults for terms, currencies, and precision. Pricing attributes allow prices to be determined based on item configurations. Formulas can also be used to derive prices. The document provides examples of configuring pricing breaks, government pricing rules, intercompany invoices, and debugging tools.

Uploaded by

ratheeshposhala
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
62 views44 pages

RP - Pawan - Training Notes

This document provides an overview of pricing configurations and concepts in Microsoft Dynamics 365 Business Central. It describes basic and advanced pricing, price lists, pricing formulas, attributes, and debugging pricing issues. Basic pricing uses price lists to determine item prices on sales orders, while advanced pricing uses rules-based pricing engines. Price lists can include defaults for terms, currencies, and precision. Pricing attributes allow prices to be determined based on item configurations. Formulas can also be used to derive prices. The document provides examples of configuring pricing breaks, government pricing rules, intercompany invoices, and debugging tools.

Uploaded by

ratheeshposhala
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 44

Basic pricing  it’s a component of OM module which has features of price list, price is determine when

item is entered on the sales order form

Its is part of OM product

Adv Pricing  it’s a separate Module, engine based application where you call pricing engine based on
rules what you have setup, different attribute determine the price of an item

Modifier are existing in both Basic & Advance pricing

QP: Price rounding  to round the price rounding (how rounding will be done)

Rounding Decimal can be done from Pricing list (Precision)

Precision also set up at Currency level.

But if set the profile value of this as “Enforce Currency Precision”, it takes from currency otherwise, the
precision values takes from Price list

Price List:

You can default Freight terms and payment term from price list

Enter the each price and price associate to it

Multi-Currency Conversion: - function currency OU in one currency and price list in another currency.
SO is priced, system will use transactional currency.

 List all currency

Precision is -2 (2 points a decimal places)

Other Profile QP: Selling Price Rounding Options:


Scenario1:

Create a new item  Copy from  Template: @ATO Item then assign to M1 org

Create a new item  Copy from  Template: @ATO Item then assign to M1 org  Tools: Item Category
= Item.Misc

Go to Sales Order  Order Type : Mixed  Enter the item  It should throw an error saying “ Item and
UOM does not exist in the price list” (unless the price list has ALL_ITEM attributes)

Query the price list and add below items to the price list:
Enter the value as 100
Item unit price gets from price list

SO  first it check whether item exist in Price list

 2nd check the item category exit in price list


 3rd check ALL_ITEM is defined in price list

Price Break

Based on volume of quantity, can provide different prices.


2nd scenario:

Price Break –

Line Type: Price Break

Price Break Type: Point

Application Method: Block

1 – 10 = 100

10 – 100 = 90

If you order 12 quantity = 90/12 = 7.5

3rd Scenario:

Application : Unit Price


General Service Administration:
Profile : OE : GSA Discount Violation Action
Profile:

Prevent option  will not let you save the line


GSA Price list  Qualifier Setup
If value of this item in SO is less than this value, system will throw an error on the sale order form.

Enable the GSA flag on the customer on customer setup

Price Formulas:

Allows to have a specific set of rules to govern by a formula, that formula end up generating a price for
an item.

Different price or values setup for formula, based on that price gets derived.

Pricing engine will generate the price based on formula.


List Price – that get a value of item from Price List

Function – oracle provided a function where you can write a custom logic to get the price value

Pricing Attribute Context

Set up  Attribute Management  Context and Attributes

There are 100 of Pricing Attributes columns which can be mapped to one column
Attribute Linking & Mapping:
Click on Link Attributes  Attribute Mapping:
List of values of User Source Type:
When select PL/SQL API  you can invoke custom package and derive the value.

Attach the formula to Price list of an item


Based on Formula: 150+ 15 = 165

Test Case 2:

Remove the List price from Price and check whether value calculates based on only formuala
Now the value should be: 150 on sales order form

Test Case3: Pricing Attributes:


Sort of attributes gives ability to pricing engine to decide on the price based on what attribute have been
used or which attribute have been selected.

 Generic Pizza
 Customized pizza with your own toppings

Medium size pizza is 300. If you customize the same pizza with additional topping or protein – will
be 500/-

1. Identified the Attributes:


Each context can have more than one attributes:
Topping and Proteins

Then link the attributes


2. Go to Link Attribute Mapping
Add this new Pricing Context to Order Fulfillment
Click on Link Attributes – you will see both attributes which are already linked to Pricing
Context.
Run Build Attribute Mapping Rules  seeded program which will build the attributes – Run
successful with Normal.

3. Define Pricing Formula:


Click on “Factors” button

XX_FACTOR = Toppings (under topping – 3 categories – Veg1, Veg2 & Veg3 and
respective prices)
Value mentioned below are from Basic Pricing Attributes , you can define associate
pricing attributes means Veg1 can categories like Veg1_tomoto, Veg1_paneer
XX_FACTOR1 = Toppings Protein (under Protein – 3 categories – Bacon, Chicken &
Paneer and respective prices)
Here basic Attribute Context : XX_TOPPINGS
4. Go to Price List and attach the pricing formula.
Basic Price is 350 + Formula
5. Go to Sales Order Form:

Enter pizza item:


No toppings, so price is 350/-

As we mentioned “User Entered” at Attribute level, in order apply any specific pricing, user
has to select manually from Pricing Context.
After selecting “XX_TOPPINGS”, click on [ ]
Earlier it was 385,
After save or reprice:
Amount would be: 550
= 385 + 50 + 50 =
Enable Debug  which will give you values of selectin of each attribute value
Intercompany Invoice – Pricing Issues:

OM and INV
Inv program  Create InterCompany AR Invoices
If set up, customer is using Adv Prices for transfer price in inter company invoice

NAv: Set up Attribute Management  Pricing Transaction Entry Associations


If both are defined means Inter company using Adv Price

Same precedence error come for price lists (they may be chance of defining pricing in both
moduels: INV & QP)

To identify which module has defined the price list – you can check below: Price List (Others Tab)
If below profile set:
Then System Source would be INV on Price List (Others Tab)

To Debug the Issue:

Set the profile for QP log messages:


QP: Debug = Request Viewer Off  will capture all QP debug messages
Can set at User Level Only:
Below note helps to idenfiry the issue with PO and Adavance pricing:

Check the Test cases on Pricing Confluence Page

You might also like