[Music] so in this video we have to learn about two major terms price determination and price configuration we have already studied about this price determination in our last three videos where we have learned that to judge the final price of the product suppose if I want to sell iPhone XR and the order is of 120 pieces then the condition record would be felt that if order is above 100 pieces and the iPhone rate between all the $9.99 per piece this was my final price for my product what we did we applied the pricing procedure what is the pricing procedure it is basically a function on sales area sales document and sold to party when we apply the function of pricing procedure on these three entities we get in the output condition type and on the condition type we apply the excess sequence to get the condition tables and the condition tables retrieve the condition records from the condition records we fetch rows like this to get the final price this is all what we have learnt till now that is called the price determination now in this video we have to learn about price configuration let me tell you the difference between price determination and price configuration in price determination we were finding out the final price of some particular product but in price configuration what we have to do we have to configure our system configure of the system means we have to make those necessary changes we have to make these conditions records because whenever we will make the condition records like this then only the price would be determined not first of all we have to store in our recipe system the condition records like this these conditions records will be stored by the condition table that means we have to make these condition tables also in our recipe system then we have to define the condition types also in our SDP system then we have to configure our pricing procedure such that the relevant pricing procedure is fetched from the system relevant condition type is fetched from the system then we can get the relevant condition tables relevant condition regards and then the final price so what we are trying to do is we are following a back step process opposite to determination why we are following the back step process because now in price configuration we have to make all these so that the final price of a product can be just if all these are already made and you have to just the final price you will call it price determination but to get price determination to get the price determination procedure work in your recipe systems first the price determination system has to be configured so that you can get the final price by applying the pricing procedure I hope it is clear to you we have to set the values and the condition records we have to set the fields and data in the condition tables we have to make the condition types we have to judge this function of pricing procedure we have to make the sales area we have to make the sales document and we have to make the customer database that is the customer master record to get this whole to parties I hope it is clear to you what is the major difference between determination and configuration so till now we have studied that for price determination the first step was procedure determination where we identified the sales area sales document and sold to party we gave these three entities to the pricing procedure and the pricing procedure gave these entities to the condition type condition type calls the excess sequence and the excess sequence outputs the condition tables and the condition tables gives us the condition records which finally give us the final price of a particular product now in this unit we have to move on to pricing configuration so let me tell you what is pricing configuration for determining the final price of the products all these pricing procedures condition tables condition records excess sequences have to be configured before first of all any ASAP employee have to creep in the systems of SP and have to save all this information so that in any time in future the price of a particular product can be retrieved the SP system cannot accumulate all those technologies all those formulas all the mathematics on its own some employee has already saved this that's where we are getting the final price of the product some employee has created the condition table some employee has created the extra sequences some employees have created the condition types some employees have created the sales document sales organization customers in the SP system that's why we are able to find out the final price of a particular product keeping all those factors in mind so through the simulation let us learn what is price configuration before starting the simulation let me tell you the red arrows will be depicting the price determination and the yellow arrows would be depicting the price configuration okay so here the first step is procedure determination which carries the sales area sales organization distribution channel these three entities combined for the sales area sales document and sold to party sales area sales document and sold to party were the three entities that are required to be given to the pricing procedure okay and from this three entities sales area sales document and sold to party we infer that this customer seaman has to be identified with the standard price that means this customer is a normal customer and we have to follow the standard pricing procedure okay so the pricing procedures available in our system were standard free of charge service third party out of those standard was selected and then the condition type relevant to the standard pricing procedure is selected this is what happens when the price determination is taking place because red arrows are depicting the price determinations from the sales area sales document and sold to party we determine that standard pricing procedure has to be allocated the rising procedure determines that the relevant condition type has to be find out now then this condition type is assigned to the pricing procedure and this pricing procedure is assigned to the procedure determination that means the three entity sales area sales document and sold to party so the pricing configuration means assigning the condition type to the pricing procedure and assigning the pricing procedure to sales area sales document and sold to party the pricing configuration works in almost the backward steps of the price determination for determining the price we move forward and to consider the price we move backwards it would be more clear now so up till now we have studied the condition type now let us begin with this pricing procedure again we saw that we need the standard pricing procedure and for standard pricing procedure in the SFA system there are these four condition types available PR zero zero price key description bears K a zero zero discount percentage ka zero seven my Tyrael discount k zero to nine special offer the red arrow depicts price determination obviously after determining the pricing procedure we find out the condition type then this condition type has to be assigned to this pricing procedure before so that the price can be determined later on some employees have already assigned these condition types to these pricing procedures for example the standard pricing procedure carries PR 0 0 + ka 0 7 that means PR 0 0 price and ka 0 7 material discount these two condition types have been assigned to pricing procedure some employee of the si PSD have already assigned these condition types to the standard pricing procedure some employees might have defined some other condition types for free of charge pricing procedure some employee might have allocated the condition types to service pricing procedure some condition types must have been previously allocated to third party so these allocation of condition types to the pricing procedure comes under the category of price configuration and when the SLP system determines that standard pricing procedure for standard pricing procedure these condition types were previously allocated so I have to go to those condition types and proceed further so price determination takes place after the system has been already configured by some employee if the system hasn't been configured by some employee how the pricing determination will check that for standard pricing procedure we have to check for price and material discount I hope you got my point clear other some system PO configure in occurring Fla the pricing procedure you can see judge periodically other micro standard pricing procedures for low karna the Australian Mirko PR 0 0 RK 0 7 welly condition type or honey you see I said became ploy in a pellet essa Peka system go configure car ahead abuses so much re energy other standard I autonomy Reebok TR 0 0 K 0 7 is pricing procedure course I engineer MATLAB Joe Pele assign well accounta cusco hungarian pricing configurations of paella Casillas apk employ image about become me Mesa because of the IATA is employee no configure Tara a bad me a barber to configure courage any bad Mia Pookie occur nap give us to customer anger cotton a salmon business the pricing procedure logic about Mohammed Shah first time krpa configuration and after that every time pricing determination is taking place jab because Mariah apprising determinations allow guru say final price but a dog a lake into fine and price I akan say to be kisi employ image of essa Peka software Nyonya to say configure Kiyosaki sa other pricing procedure standard I storming every condition types trainee a free of charge I have to get any service I had any or third-party I Ithaca Valley condition types Linea metal backstage process parallel follow her to crack abhi na kabhi kabhi a page a red valley arrows mullah pricing determination ho paura tick now the condition type PR 0 0 if selected then the relevant excess sequence will take place why because excessive Curren is applied to the condition type so that we can get condition tables this was the main concept so here it is written that XA sequence 2 is assigned and sometimes in feud in the past the XS sequence 2 was judged that why this excess sequence 2 has to be assigned some employee might have configured the SOP system that these much excess sequences are available for example x equals 1 x equals 2x a sequence 3 so now from that configuration our SFP system is judging which XS sequence has to be assigned to this particular condition type that means our SOP system was configured somewhere in the past and now while determining the price it is using its intelligence to determine which XS equals has to be assigned note that we can do the SAT employee can define their own condition types also again and again and can define their own extra sequences also again again that means when we are defining the condition types when we are defining the XS sequences when we are defining the pricing procedures then we call it configuration Jochum Benari some kudani condition types Binaca apk system safe there there from APNIC good condition types XS sequences Binaca SS PK system safer there Tom get the configuration or the binary condition I use binary XS sequences from use the Thais come at em price determination I hope Authority for a concept our customers are over chicken a bath dat a system name s epic a system you hate you judge keyaki XS sequence 2 Q use kernel they cook Easter concept a stable me hamari past sales organization p1000 distribution channels are 10 a pricing list type t0 to price list type metal optimal past i sorry place less money or ta just a wholesaler customers Kelly a price list retailers will hear a lot so it's my price list item Mary selector is 0 do you see his heart be correspond or such be a good sales document currency the US dollar materials I am 1 or local currency the euro maryska local currency euro MATLAB for example other iPhone keepeth current local currency euro metal hamare iPhone table Andre Europe men who steal local currency k he wrote abhi Europe me burning it a bit o local currency euro bogie lake in America steamer aya us the customer I us that the customer Peter and CEO key US dollar Islam at the sales document we currency Kok US dollar the currency of iPhone production unit is euro and the currency of customer is US dollar so excess sequence one says it will run the search strategy when the document currency and local currency are same but here the document currencies US dollar and local currencies you know that means they are not same so the system will go to the excess sequence 2x a sequence to say that it will run the search strategy then document currency and local currency are different that means X a sequence to is matching the sales document sales document currencies US dollar local currencies euro they are different that means X a sequence to matches this criteria therefore X a sequence to was assigned to this condition type this all configuration is done by some s AP employee before that's why the SMP system is able to judge that why this excess sequence 2 has to be assigned Java price determination Curtis price determination a condition type B are zero zero kinetic Hakeem and poor excess occurrence to Milla where okay semilla skpk system Naruto day media TC employee could be defined here thana he access equals one couple of non access sequence to table Hana so easy form configuration Bolton Joe passed miko ASAP employee pls a virtue per ticket now we have studied up to this much after the excess sequence we talk about the condition tables this excess occurrence to retrieves the condition table for example these four condition tables are retrieved the first table carries price foreign currency and material then second table carries customer and material third table carries price currency and material and fourth table here is the material so as here the iPhone swerving used in Europe and the local currency was euro the customer was of USA that's why the sales document currency was US dollar that means the iPhone production unit is exporting the iPhones to us and that means if iPhone production unit is exporting the iPhones to us that means the US customer will remit the payment to the iPhone production unit after getting the delivery when the US customer will remit the payment to the iPhone production company that means some foreign currency is going to the iPhone production company Agora Mary Ison production in Europe may our customer Amara USA k2w sa customer payment Garriga if one go - Karina Kelly the Islamic love of foreign currency there are now Europe Kelly the US dollar foreign currency obey - Ashley Amara access sequence - chilaka or extra sequence tunic goose irrelevant condition table Gunda Leah this can the price of foreign currency theorem materials new price currency material well Ani - now's new price foreign currency material valid unda yogi is sales document Mohammed foreign currency milner earlier I hope you got this point why this price foreign currency and material condition table is chosen because excess sequence - says the sales document currency and local currency are different so foreign currency table has to be chosen and this condition table and this condition table would be assigned to the excess equals 2 so so that in future whenever price determination has to take place this extra sequence to will find this condition table only when excess sequence when we applied the search strategy by access sequence to the excess equals 2 will always return this condition table only that that means this relevant condition tables were assigned somewhere in passed to this excess occurrence - and Forex a sequence 1 this condition table might have been assigned by the SFA system so I hope you are getting the point how we have already assigned the relevant condition tables to the excess sequence so that in future the while determining the price those are relevant condition tables are only featured okay now this condition table will output the condition records when we are determining the price we learned this only from condition tables we get the condition records and this condition records has been assigned to the relevant condition table before somewhere in passed by some SLP employee when this condition record was assigned to this condition table somewhere in passed that's why only now while determining the price we are getting this condition record as output so the s if employed in past configured the SI system that whenever this condition table will come you have to assign this condition record so now when we were determining the price this condition record was outputted this is only called rise configuration so after the price has been configured the condition record is outputted this condition records will output the final price and these final price were somewhere in past already assigned to this condition record is employee into a condition record benaiah hana PHP sigh - ah huzzah dollar decreased business or PC super order retinosyn an annual dollar per piece - business some ASAP employee has already written these values some asset employees have already made these condition records or some SME employees have used some mathematical formulas to automatically make this condition record some calculation has been done already in past I hope you are getting the point so those past transactions that some SF employees has already done so that in future price can be determined that process is called price configuration see that price determination is moving with red arrows in the forward direction and in the reverse direction through yellow arrow price configuration is moving that means in past these yellow arrows were followed to configure our asipi system and now in future these red arrows will be followed to determine the price of a particular product I hope you are getting this point and here you can see through this yellow arrow that this pricing procedure is assigned to this sales area sales document and sold to body that means pricing procedure is assigned to sales area sales document and sold to party that means the customer whenever this customer semen will come to this division of this sales organization then this pricing determination procedure would be followed so whenever we will see the customers even later on in our sales document number a 4:03 type then we have to follow this pricing determination this is called pricing configuration so here is the summary step one procedure determination that carries the sales area sales document and sold to party step two is pricing procedure step three installation type extra sequence from x equals related condition table from condition table we get condition records and from condition records we get the final price this was the process of price determination and how the price is being determinate and determinated somewhere in possum SFA employee had configured the SFA system that final price would be saved in the condition records condition records would be conditioned via condition tables and condition tables would be assigned to the XS sequences and XS equals would be assigned to the condition type and these condition type would be assigned to this pricing procedure and this pricing procedure to this sales area sales document and customer so all in all pricing configuration is done whenever an SI p organization establishes the SI p software in it and after that that organization has to use that software to determine the price of a particular product a company whose Niko's nine products introduced array to open ASAP system cope a level configure the regular product scale here is backward step process for follow per K and after that the broken Figaro's as opposed products they lose domingo customer willing otoko SI pica software's completely price determined Caraga in red arrow stuff forward step process used okay i hope up co-simulation get through sahaja yoga key price determination or configuration yeah