Pricing Date

Embed Size (px)

Citation preview

  • 8/10/2019 Pricing Date

    1/88

    Pricing date based on delivery date

    Used transaction VOV8 .

    This configuration is by order type.

    There is a field called proposal for pricing date .

    There you can select pricing date as requested delivery date.

    A - Proposed pricing date based on the requested dlv.date (Header)

    This control is set at the document level as oppose to the condition type level (PR00).

    That means your other condition types such as surcharges and discounts are alsodetermined using the requested delivery date.

    If your requirement is for PR00 to alone to be priced at delivery date then this ill notor!.

    Pricing date based on delivery date

    Used transaction VOV8 .

    This configuration is by order type.

    There is a field called proposal for pricing date .

    There you can select pricing date as requested delivery date.

    A - Proposed pricing date based on the requested dlv.date (Header)

    This control is set at the document level as oppose to the condition type level (PR00).

    That means your other condition types such as surcharges and discounts are alsodetermined using the requested delivery date.

    If your requirement is for PR00 to alone to be priced at delivery date then this ill notor!.

  • 8/10/2019 Pricing Date

    2/88

    Ho pricing date is deter!ine in the sales order andbilling docu!ent" #here is the setting"

    The pricing date is proposed based on the setting you ma!e in the "ales document

    configuration. ( T code # $%$&)'ou have a field Prop.f.pricing date in the Requested delivery date pricing date purchase order date segment.

    Then you can choose the foll oing options#*lan! + Indicates the current date as the pricing date, + Indicates the date based on the requested delivery date* + Indicates the date based on the order validity start from date

    ,nd the pricing in the billing document is copied from thte sales order -eliverydocument..

    It again depends on the setting u have in the copy control from order + billng or delivery + billing.In the copy control in the item settings you have t o fields relavant for this.

    %ne is pricing source and the other is pricing type.

    The pricing sources are generally the order. *ut if you ant you can change it to othervalues mentioned in the drop do n

    but this values have no effect if the pricing type is *.

    ,ny other value other than * in the pricing type ill ta!e the reference document pricementioned in the pricing source field. but for the pricing type *. The ne price is determined in the billing order.

    $eport to %hec& the 'ntered Pricing %ondition Price

    #hich is the best transaction code to chec& the Pricing condition price entered inV ** "

    %ther than $/ 1 to display the price you can use $ 2- + 34ecute Pricing Report tochec! the prices entered into the Pricing 5aster.

    6ormally Pricing Report + 07 8ust.+specific Prices ith "cale -isplay ill do.

    %ther Pricing Reports you can tried are these#

    ---------------------------------------------------------------------------

  • 8/10/2019 Pricing Date

    3/88

    |LR|Reporttitle |--------------------------------------------------------------------------|01|Comparison of Price Lists Without ScaleDisplay ||02|Comparison of Price Groups Without ScaleDisplay ||03| ncoterms !ith ScaleDisplay ||0"| ncoterms Without ScaleDisplay ||0#|Price List $ypes Without ScaleDisplay ||0%|Price List $ypes !ith ScaleDisplay ||0&|Cust'-specific Prices !ith ScaleDisplay ||0(|Cust'-specific Prices W)out ScaleDisplay |

    |0*|+aterial List)+aterial Pricin, Group !ith ScaleDisplay ||10|List +at')+at'Pricin, Groups Without ScaleDisplay ||11|Price Groups With ScaleDisplay ||1"|$a es

    ||1#|+aterialPrice ||1%| n.i/i.ualPrices ||1&|Discounts an. Surchar,es yCustomer ||1(|Discounts an. Surchar,es y+aterial ||1*|Discounts an. Surchar,es y PriceGroup ||20|Discounts an. Surchar,es y +aterialGroup ||21|Discounts an. Surchar,es yCustomer)+aterial ||22|Discounts an. Surchar,es y Customer)+aterialGroup ||23|Discounts an. Surchar,es y PriceGroup)+aterial ||2"|Discounts an. Surchar,es y Price Group)+aterialGroup ||2#| $) $ 1

    ||2%|Cana.a)4S

    ||2&| '5'P'S+e ico ||2(|Con.itions yCustomer |

  • 8/10/2019 Pricing Date

    4/88

    |30|Con.itions y Customer6ierarchy ||31|Price List !ith ReleaseStatus || C|

    || D|

    |---------------------------------------------------------------------------Fast Links:

    +ass ,pdate of condition pricing

    'ou can update the condition pricing for a range of sales order.

    9or e.g. if you create sales order for : months or so and at the beginning of each yearyou have to update the prices for lots of sales orders.

    %ther than using VA and ma!e an Update of the conditions at item level hich is a bigor! because you ill have lots of open sales order after so many months.

    Use VA / select your %rders and on the result screen #+

    clic! 'dit- 0 +ass %hange -0 1e Pricing (menu).

    or

    if you don;t ant to do that %nline rite your o n abap report and use 9unction2345,6 4%HA17' (chec! here+Used at 2' 9 TraceVA / on ho to fill the

    parameters 9unction +P$:

  • 8/10/2019 Pricing Date

    5/88

    It is this simple if you do not have any other Prices in the price procedure.

    >o ever if you are using one pricing procedure here for some items you price usingVP$2 and some others using P$ then you should use requirement routines to enable

    the correct price condition type at the right time.

    The second method involves more or! as you need to rite a formula ( VO:+ ) to getthat information.

    This is ho it goes #+

    . "et VP$2 to be the first step in the pricing procedure and to be subtotal * (asstandard).

    ?. "et P$ ith alt. calc. type formula hich sets the value of P$ to be equal to the

    subtotal *.The routine (created ith transaction VO:+ ) is#

    R$@A,B09%R5 9R5C/%6-ICD3RTC@00.

    E/D3RT < /%5P+D,$DR.36-9%R5.

    The pricing procedure than loo!s li!e that#

    "tep VP$2 statistical subtotal * reqt A

    "tep ? P$ ,ltcty @00

    %usto!er discounts on effort only

    +++++%riginal 5essage+++++"ubFect# 8ustomer discounts on effort only

    >i ,ll

    De have a requirement of giving a discount to customer based on the totalamount invoiced so far (across financial years).Dhere do e set this upG De have seen so far the discounts are calculated

    based on the value of the current invoice.The discount should be on a graduated scale basis for e4ample

    0 + 00000 6o discount00000 + ?00000 :H

    ?00000 + and above 0H

  • 8/10/2019 Pricing Date

    6/88

    This means that discount ould only start after the customer;s net salevalue crosses 00000.9or e4ample if the customer has been billed for BB000 and the currentinvoice is for 1000 a discount of :H should be given on ?000 i.e. 00.,nother complication is that the discount is not based on the total amount

    billed so far but only on the effort billed and not on reimbursements (li!eairfares living e4penses visa charges beeper charges etc). The discountapplies only to the effort and not to the reimbursements. In the abovee4ample (invoice of 1000) say the effort billed is only :00 the rest beingreimbursements. The discount is only on the :00. (the rest being ta!en up bythe lo er limit for eligibility of 00000)

    9or e4ample the customer might have been billed say :0000 so far but actualeffort billed might be only B0000 the rest being reimbursements of actualcosts and hence the customer is not eligible for the discount.

    /indly help+++++Reply 5essage+++++"ubFect# R3# 8ustomer discounts on effort only

    >i

    The solution for this is Using rebate condition types and suitable conditionrecords.

    %f this to handle your first problem that is the rebate has to be applied

    only on the effort you have to set up a line in the pricing procedurehich gives the rebate basis i.e the value to be used for rebate cond types.This I believe solves your problem of rebate only on effort.

    'our second problem i.e the discount should start getting appliedautomatically hen it reaches the first scale for hich the values span fefinancial years. This I am not really sure hether it can be made possiblein the invoice itself. *ut a or! around is not giving the discount directlyin the invoice but settling it against the rebate agreements by 8redit notes

    periodically.

    >ope it helps.Than!s

    +++++Reply 5essage+++++"ubFect# R3# 8ustomer discounts on effort only

    >i

  • 8/10/2019 Pricing Date

    7/88

    ,rent e loo!ing at rebate agreeement. That appears to be a straighta aysolution to your problem. 'ou activate the sales organi ation and the

    payer for that

    Regards

    +++++Reply 5essage+++++"ubFect# R3# 8ustomer discounts on effort only

    I am in ",P R 1 rel.109.De have ? options to meet your requirement.

    . Using scale in condition type ( tcode $ 0@ ) choose scale basisJ."cale based on a formula ( be# your based amount is invoice ). -efinescale formula. 'ou need ,*,P3R to define it.?. Using routine in ,lt.calc.type ( tcode $ 0& 5aintain PricingProcedure ). >ere you also need ,*,P3R to create routine.

    hope this help

    2teps to %reate %o!!ission for Agent

    9or creating commission agent you have to follo belo steps.

    ) 3stablish Partner 9unctions for the 8ommissionee(s)5enu Path# T%%2" +=K *U"I63"" 36JI633R +=K 8U"T%5ILI6J +=K ",23" ,6--I"TRI*UTI%6 +=K *,"I8 9U68TI%6" +=K P,RT63R -3T3R5I6,TI%6 +=K-39I63 P,RT63R 9U68TI%6"Transaction 8ode# $%P,

    ?) ,ssign the Partner 9unctions to Partner Procedures5enu Path# T%%2" +=K *U"I63"" 36JI633R +=K 8U"T%5ILI6J +=K ",23" ,6--I"TRI*UTI%6 +=K *,"I8 9U68TI%6" +=K P,RT63R -3T3R5I6,TI%6 +=K-39I63 P,RT63R 9U68TI%6"Transaction 8ode# $%P,

    1) 8reate a Partner Procedure for the 8ommissionees5enu Path# T%%2" +=K *U"I63"" 36JI633R +=K 8U"T%5ILI6J +=K ",23" ,6--I"TRI*UTI%6 +=K *,"I8 9U68TI%6" +=K P,RT63R -3T3R5I6,TI%6 +=K-39I63 P,RT63R 9U68TI%6"Transaction 8ode# $%P,

    A) 8reate 6e 8ustomer ,ccount Jroup(s) for 8ommission ,gents5enu Path# T%%2" +=K *U"I63"" 36JI633R +=K 8U"T%5ILI6J +=K 2%JI"TI8"J363R,2 +=K 2%JI"TI8" *,"I8 -,T,# *U"I63"" P,RT63R" +=K 8U"T%53R"+=K 8%6TR%2 +=K -39I63 ,88%U6T JR%UP" ,6- 9I32- "3238TI%6 9%R

  • 8/10/2019 Pricing Date

    8/88

    8U"T%53RTransaction 8ode# %$T0

    :) ,ssign the Partner 9unctions to the 8ustomer ,ccount Jroup(s)5enu Path# T%%2" +=K *U"I63"" 36JI633R +=K 8U"T%5ILI6J +=K ",23" ,6-

    -I"TRI*UTI%6 +=K *,"I8 9U68TI%6" +=K P,RT63R -3T3R5I6,TI%6 +=K-39I63 P,RT63R 9U68TI%6" +=K J%T% +=K P,RT63R 9U68TI%6" +=K36$IR%6536T +=K ,88%U6T JR%UP ,""IJ6536TTransaction 8ode# $%P,

    @) ,ssign the Partner 9unctions to the Partner Procedure for the "ales -ocument >eader5enu Path# Tools +=K *usiness 3ngineer +=K 8ustomi ing +=K "ales and -istribution +=K*asic 9unctions +=K Partner -etermination +=K -efine Partner 9unctionsTransaction 8ode# $%P,

    7) ,ssign the Partner 9unctions to the Partner Procedure for the "ales -ocument Item

    (%PTI%6,2)5enu Path# T%%2" +=K *U"I63"" 36JI633R +=K 8U"T%5ILI6J +=K ",23" ,6--I"TRI*UTI%6 +=K *,"I8 9U68TI%6" +=K P,RT63R -3T3R5I6,TI%6 +=K-39I63 P,RT63R 9U68TI%6"Transaction 8ode# $%P,

    &) 3dit the Pricing 8ommunication "tructure (/%5/,L) to >old the 6e 9unctions(8lient Independent)5enu Path# 5enu Path# T%%2" +=K ,*,P D%R/*368> +=K -3$32%P536T +=K-I8TI%6,R'Transaction 8ode# "3

    B) 3dit 5$A:,9LL M usere4itCpricingCprepareCt!om! (8lient Independent)5enu Path# T%%2" +=K ,*,P D%R/*368> +=K -3$32%P536T +=K ,*,P3-IT%RTransaction 8ode# "31&

    0) 3dit R$@0,9LL + usere4itCpricingCprepareCt!om! (8lient Independent)5enu Path# T%%2" +=K ,*,P D%R/*368> +=K -3$32%P536T +=K ,*,P3-IT%RTransaction 8ode# "31&

    ) 3dit 5$A:,9L* + usere4itCne CpricingCvb!d changing ne Cpricing (8lientIndependent)5enu Path# T%%2" +=K ,*,P D%R/*368> +=K -3$32%P536T +=K ,*,P3-IT%RTransaction 8ode# "31&

  • 8/10/2019 Pricing Date

    9/88

    The follo ing code should be inserted into program 5$A:,9LL to allo the system tore+e4ecute pricing if the user ma!es a change to the relevant partner function (alterationaddition deletion).

    1) ,dd the /%5/,L 9ields to the Pricing 9ield 8atalog (8lient Independent)

    5enu Path# T%%2" +=K *U"I63"" 36JI633R +=K 8U"T%5ILI6J +=K ",23" ,6--I"TRI*UTI%6 +=K *,"I8 9U68TI%6" +=K PRI8I6J +=K PRI8I6J 8%6TR%2 +=K-39I63 ,883"" "3NU3683" +=K 5,I6T,I6 ,883"" "3NU3683"Transaction 8ode# %$?A

    A) 8reate 8ondition Tables (8lient Independent)5enu Path# T%%2" +=K *U"I63"" 36JI633R +=K 8U"T%5ILI6J +=K ",23" ,6--I"TRI*UTI%6 +=K *,"I8 9U68TI%6" +=K PRI8I6J +=K PRI8I6J 8%6TR%2 +=K-39I63 ,883"" "3NU3683" +=K 5,I6T,I6 ,883"" "3NU3683"Transaction 8ode# $ 01

    :) 8reate an access sequence containing the ne tables (8lient Independent)5enu Path# T%%2" +=K *U"I63"" 36JI633R +=K 8U"T%5ILI6J +=K ",23" ,6--I"TRI*UTI%6 +=K *,"I8 9U68TI%6" +=K PRI8I6J +=K PRI8I6J 8%6TR%2 +=K-39I63 ,883"" "3NU3683" +=K 5,I6T,I6 ,883"" "3NU3683"Transaction 8ode# $ 07

    @) 8reate a ne condition type5enu Path# T%%2" +=K *U"I63"" 36JI633R +=K 8U"T%5ILI6J +=K ",23" ,6--I"TRI*UTI%6 +=K *,"I8 9U68TI%6" +=K PRI8I6J +=K PRI8I6J 8%6TR%2 +=K-39I63 8%6-ITI%6 T'P3" +=K 5,I6T,I6 8%6-ITI%6 T'P3"Transaction 8ode# $ 0@

    7) ,dd the 8ondition Type to the Pricing Procedure5enu Path# T%%2" +=K *U"I63"" 36JI633R +=K 8U"T%5ILI6J +=K ",23" ,6--I"TRI*UTI%6 +=K *,"I8 9U68TI%6" +=K PRI8I6J +=K PRI8I6J 8%6TR%2 +=K-39I63 ,6- ,""IJ6 PRI8I6J PR%83-UR3" +=K 5,I6T,I6 PRI8I6JPR%83-UR3"Transaction 8ode# $ 0&

    ) 8reate 8ommsission Report LL8%55I""I%6 (8lient Independent)5enu Path# T%%2" +=K ,*,P D%R/*368> +=K -3$32%P536T +=K ,*,P3-IT%R

    Transaction 8ode# "31&

    23 ;uestions About Pricing %ondition

  • 8/10/2019 Pricing Date

    10/88

    Tables O ,ccess "equences. Dhat e do is e Fust define our o n pricing procedures by using the e4isting condition types (i.e# PR00 /00A /007 /,0? /900 etc.) O thenassign that Pricing Procedure ith "ales ,rea -ocument Pricing Procedure O8ustomer Pricing Procedure .

    ,fter that e put the values against each 8ondition Types mentioned in our PricingProcedure by using the T+8ode $/ . *ut e also need to !no about the 8onditionTables 8ondition Types O ,ccess "equence 8reation. "o for that purpose e have to usethe follo ing T+8odes respectively # $ 0: $ 0@ O $ 07 . 6o it ill become easyto create the same.

    ,lso to inform that using T+8odes is more smarter than follo ing paths through I5Jscreen.

    Utsav 5u!herFee + utsavmu!herFee A1 hotmail.

    #hat is the difference of V ** and V * (condition records)"

    +y condition type is P$ and Access sequence is P$ . And in this accesssequence table > is available. 1o hen = as entering the P$ in V * itsho s error is not defining for the condition type P$ . 5ut hen = asentering the P$ at V ** it is accepting it.

    -ifference bet een $/ and $/1 + if you go through the menu path you ill get thev! 1 as condition record from the tamplets hereas v! as simple condition record. In$/ you can store condition record for more than one conditiontype. This means you can have same condition record for different condition types.This

    feature is given to enhance the system;s performane and not to create the duplcation ofthe or! for each condition type.,gain system is not allo ing to store the record in the v!1 for the condition type pr00and access sequence pr0?.This is because if you see this ac seq cointains t o accessses?0 and 10 having the same table no.*ut you see there is the difference bet een thetechnical vie of it for transfering the data from document field and condition field soyou can not maintain the data at $/1 .

    #hat is the difference bet een Header condition and =te! condition" = &no ite!condition applies to each ite! in a sales docu!ent. Header condition can only be

    applied to an entire docu!ent. -ifference bet een header and item condition + as '%U 8%RR38T2' ",I- >3,-3R8%6-ITI%6 I" ,PP2I8,*23 9%R T>3 D>%23 -%8U536T here as item is foritem.34+"ay fright is dependent on the total eight of all the items in the documents thenheader condition adds on eights of all items and calculates the record accordingly.'ou have t o different types of the header conditions.a) In one you can duplicate the same value throughout the document for each item."ay

  • 8/10/2019 Pricing Date

    11/88

    discount ?H at header level hich is also applicable to all the items b)"econd is the accumulation of the values of all the item at the header level as earliere4plained for the eight fright.These differenes are controlled through the indicator of group condition in the cond.typeconfiguration.

    ,nd so obviously header condition can not have the condition record and hence accesssequence.

    2AP 23

  • 8/10/2019 Pricing Date

    12/88

    3g if the pricing scale is maintained and pricing for A: units comes under the scale of00 per unit. the base value is A: units but if the client ants a standard base value in

    some casesto be assumed inspite of maintaining the scale an alternate base value isconfihured that is the base value based on hich the order value is to be calculatedchanges.

    :. ,ccruals# ,ccruals are maintained for rebate agreements it constitutes the totalaccumulated value hich customer has earned through rebate one the rebate for certainamount is settled the amount from the accruals get deducted.

    Q++ 6itin

    Add a :ield

  • 8/10/2019 Pricing Date

    13/88

    ?. 8all up structure /%5P,L in the ,*,P -ictionary (Transaction "3 ) in the changemode and ma!e the follo ing entry#8omponent 8omponent type#LLP"T'$ LLP"T'$"ave chec! and activate the change you made.

    1. 6ote#*ecause of the change in structure /%5P,L field LLP"T'$ is no !no n instructures /%5J and /%5P because structure /%5P,L is included in both structures.

    A. 8all up Transaction "PR%. 6avigate to ;"ales and -istribution += *asic 9unctions +=Pricing += Pricing 8ontrol; and e4ecute ;-efine 8ondition Tables;.8hoose ;8onditions# ,llo ed fields; and include LLP"T'$ as a ne entry.

    :. 6ote#6o you can use field LLP"T'$ as a !ey field hen you create a conditiontable ,444.

    @. "upply the ne field you defined by including the follo ing source code line inU"3R3EITCPRI8I6JCPR3P,R3CT/%5P#5%$3 4444+P"T'$ T% T/%5P+LLP"T'$.In order processing you find the user e4it in Include 5$A:,9LL and in billingdocument processing you find it in Include R$@0,9LL.

    8onsider that you can also use this note as a help if you ant to use other customer+specific fields as !ey fields in a condition table.

    9or header fields use structure /%5/,L instead of structure /%5P,L andU"3R3EITCPRI8I6JCPR3P,R3CT/%5/ instead of

    U"3R3EITCPRI8I6JCPR3P,R3CT/%5P.9or more information see Transaction "PR% via the path ;"ales and -istribution +="ystem 5odifications += 8reate 6e 9ields (Using 8ondition Technique) += 6e 9ieldsfor Pricing; and %"" 6ote ? 0A0.

    Header %ondition and 7roup %ondition

    #hat are header conditions"

    >eader conditions are those hich appear in the header level of any sales order. theseconditions are to be entered manually and get distributed automatically and the basis fordistribution are ta!en from the 63T $,2U3 of items mentioned at item level.

    Dhen e go to the conditions section in a sales order here the details of pricing ismentioned here e add these conditions.

    Dhenever any >eader 8ondition is used it overrides the PR00 condition type.

  • 8/10/2019 Pricing Date

    14/88

    34amples of header condition.

    + >,00 + H *ased >eader 8ondition.

    + R*00 + ,bsolute or numeric value hich applies to all items.

    + >*00 + 6umeric value or ,bsolute value. Q++ $ive! 8ho!shi

    #hat is the difference bet een group condition and header condition"

    Jroup 8ondition# 'ou can use this is feature of a condition type to apply price ordiscount for a material based on common property.

    >eader 8ondition# This is a manual condition hich you apply to header (8onditionscreen) of a sales document. This amount is applicable to all items.

    ,sage of this feature is to apply price C discount for a specific group of !aterials.

    . 'ou maintained a discount based condition record fbased on material group ( < 0 fore4ample). 'ou maintained scales also.

    Nty -iscount + 0 Rs. 00.00 + :0 Rs. 0:.00

    : + :0 Rs. 0.00 etc.

    ?. 'ou are creating a sales order for a customer ith five different items ith different

    quantities as belo

    IT35 + ?: 6o;sIT35 ? + 1 6o;sIT35 1 + ? 6o;sIT35 A + ?7 6o;sIT35 : + @? 6o;s

    ,ll the material is having the material group < 0 .

    1. Dhile calculating the discount because of this group condition system add the

    quantities of items hich have material group < 0 . In the above e4ample total quantity is< 0B. "ystem apply a discount of Rs. 0.00 to each item irrespective of the individualquantities.

    A. If you have not activated the group condition feature system determines the discountvalue based on individual item quantity hich is as belo .

    -iscountIT35 + ?: 6o;s Rs. 0:.00

  • 8/10/2019 Pricing Date

    15/88

    IT35 ? + 1 6o;s Rs. 00.00IT35 1 + ? 6o;s Rs. 0:.00IT35 A + ?7 6o;s Rs. 0:.00IT35 : + @? 6o;s Rs. :.00

    :. Is it clear no . Sust try a sales order and see the out come

    Procedure to

  • 8/10/2019 Pricing Date

    16/88

    ?. $,0 + "ales %rder + 3nsure that you have the right -ocument Pricing Procedure fromhere1. Dhile 8reating ,ccess "equence chec! your 9ields and ensure that they appear ithany arning (>ighlighted in Red)A. -o not forget to mention your ,ccess "equence hile defining your 8ondition Type

    :. ,l ays remember that your Procedure -etermination has only *asic Price as8ondition Type@. -o not forget to mention the Range (9rom To) hile creating your Pricing Procedure.

    I made most of the mista!es that appear above. >ope it helps.

    2ales Order :reight %ondition =n Header %ondition

    '$P 2AP DD0 23 2AP

    %o!!on questions? #e are using the :reight in Header %ondition. = !aintained t o line ite!s in the2ales Order. 2o the Header freight is splitting irregularly for t o line ite!s (in ite!conditions) . Ho it is happening" Any for!ula is there"

    >eader 8onditions + ,utomatic pricing does not ta!e header conditions into accountK youcan not create condition records for them in the standard system.

    >eader conditions are entered manually in order processing. R 1 includes the follo ingheader conditions#

    + Percent discount (>,00)+ ,bsolute discount (>*00)+ 9reight (>-00)+ %rder value (>500)

    >eader 8ondition# If this condition is mar!ed as a header condition it is possible to enterthe condition type in the header condition screen. 8hec!s for changing the conditionmanually are unaffected by this.

    Jroup 8ondition# Jroup conditions are helpfull incase of discounts. If group condition isselected then the discount percentage or quantity is applicable for the total sum of the

    quantity in the P% for those materials belonging to the same material group. "uppose ift o materials of same matl grp have discounts for 00 qty and above but in P% if the t omatls are bieng procured for :0 qty then they cant avail discounts but if group conditionis selected then the sum of the quantity of both matl of same matl group is considered (:0

    :0) and discount can be availed for 00 qty.

    9urther Jroup condition# Indicates hether the system calculates the basis for the scalevalue from more than one item in the document.

    http://www.sap-img.com/index.htmhttp://www.sap-img.com/sap-sd.htmhttp://www.sap-img.com/sap-sd.htmhttp://www.sap-img.com/index.htmhttp://www.sap-img.com/sap-sd.htm
  • 8/10/2019 Pricing Date

    17/88

    The nature of header condition is that hatever value you are giving in sale order billing line item ise it ill be distributed proportionately.

    If you access $ 0@ and the header condition type you can see that the condition type+ does not have any access sequence

    + field Jroup condition is selected

    6ormally 9reight >eader condition li!e condition type >-00 is calculated on the basisof eight. This is a 5anual condition and you have to enter it in the header screen. It

    ill be proportionately distributed on each item on the basis of eight. If you illunchec! the group condition field the same freight amount ill be copied to each item

    possibly irrespective of different eight hich may not be logical.

    That is the standard behaviour of the header condition type.

    *ased on hether the group condition field is tic!ed on or off it ill either split the

    header condition value to the items on pro+rata basis or it ill Fust duplicate the headervalue to all the items.

    Dhat you are e4periencing ith 9i4ed ,mount >eader conditions is standard behaviour.Please see belo 6otes#+ &7@@ 7 9,N# >eader conditions >eader condition screen+ 1 7 ? *ehavior of conditions calculation rule * changed+ A&:7A0 8onditions ith fi4ed amount in copy activities

    $o achie/e !hat you !ish 7a solute amount89 solution is in the elo!:otes;- ("%0# $ransfer a solute amount con.ition to illin, .oc'

    - 2#020 alue chan,es .urin, o/er)un.er.eli/ery- 2#1""

  • 8/10/2019 Pricing Date

    18/88

    >o ever a specific customer can buy the material for 00 U"-. "ince this is a particularly good price the customer should not also have a discount of 0 U"- per 00 pieces. Therefore this discount is to be e4cluded from pricing.

    To do this you must follo t o steps#

    'ou must set a condition e4clusion indicator for the price. 'ou can do this in t o ays# If you ant to set the condition e4clusion indicator a follo s then you specify it#

    + for all condition records of a condition type (e.g. ith condition type PR00) hendefining a condition type in "- 8ustomi ing

    + for an individual condition record (e.g. only for material A7 ) in the detail screen of acondition record (in the 8ondition e4clusion field)

    'ou must set a condition for the discount in the pricing procedure in 8ustomi ing for

    sales. If this condition is set the discount is not valid if the condition e4clusion indicatoris set. 8ondition ? is available in the standard R 1 "ystem.

    The condition e4clusion indicator is not valid for condition supplements.

    This means that if a condition record contains condition supplements they ill be ta!eninto account during pricing.

    %ondition 'Eclusion 7roup F

    In any normal situation there could be more than one condition type in a pricing

    procedure offering a discount to a customer. "hould the discounts be automaticallydetermined there is the ris! that the customer ill receive all the relevant discounts andthus purchase the product for a lo er price than he should.

    *y using condition e4clusion groupsV you can ensure that the customer does not receiveall the discounts but instead only receives the best of the available discount conditiontypes.

    5enu path M I5J + "ales O -istribution + *asic functions M pricing M conditione4clusion M condition e4clusion for groups of conditions (%$1 ).

    , condition e4clusion group is merely a grouping of condition types that are compared toeach other during pricing and result in the e4clusion of particular condition types ithin agroup or entire groups. It is important to note that the condition types you ant thesystem to compare must e4ist in the pricing procedure and must have valid conditionrecords created for them.

  • 8/10/2019 Pricing Date

    19/88

    If for e4ample a sales order is created using the pricing procedure that the e4clusiongroup is assigned to you can see that the condition offering the most favorable discountto the customer is represented in the pricing procedure.

    9or instance condition type /007 has offered a discount of 0H off the sale price or a

    real value of 10 hile another condition type /00: has offered a real value discount of0. The system then ta!es the best discount for the customer bet een the t o hich is/007 and ma!es the other discount /00: inactive. This can be seen by double clic!ingon the condition type /00: here you can find a entry saying Inactive , conditione4clusion itemV.

    There are four possible methods of using condition e4clusion groups M

    , M best condition bet een the condition types

    * M best condition ithin the condition types

    8 M best condition bet een the t o e4clusion groups

    - M e4clusive

    3 M least favorable ithin the condition type

    9 M least favorable ithin the t o e4clusion groups

    %onfiguring G%ondition 'Eclusion 7roups

    9irst step is to define a condition e4clusion groupV by using a four character alphanumeric !ey.

    6e4t step is to assign the relevant condition types to the e4clusion groups such asdiscount condition types freight condition types.

    ,fter completing the assignment of the condition types to the e4clusion group proceedith assigning the condition e4clusion group to the relevant pricing procedure.

    ,fter selecting the pricing procedure for hich you ant the condition e4clusion to beactive select the folder 34clusionV here you can assign the relevant condition e4clusion

    procedure to the relevant condition e4clusion group.

    Dhen using the condition e4clusion group to find the best condition record in a conditiontype M only use one condition type per e4clusion group. The most important thing toremember here is to WdeactivateX the 34clusive Indicator on the access sequence assignedto that condition type. %ther ise the system ill merely find the first condition recordand stop searching for other records.

  • 8/10/2019 Pricing Date

    20/88

    Pricing $eport I %ondition =ndeE

    #hat is difference bet een pricing report I condition indeE"

    Pricing $eport?

    , Pricing report basically helps to get the list of all the pricing details hich e havemaintained in the system. De can get details of all the condition types including thescales. De can get the details as per our requirement i.e. "ales org -c -ivision Plant

    material etc ise. The selection criteria ould be as per the /ey combination hich youselect in the I5J screen

    'ou get follo ing information from pricing report.

    . It informs you about the customer specific price agreements that ere made ithin a

    certain period?. 9rom pricing report you can !no hich condition records e4ist for freight charges1. Dhich condition records e4ist for customers in a particular region or country

    'ou can create your o n pricing reports ith $ 2,.

    ,lso

    $ 2- is very useful. This can be customi ed.The sales personnel use it to

    . get information for price (discounts) that e4isted at previous period ("ay Sune ?00E)

    ?. Inform potential buyer about the current price (and discounts)

    1. Revie price and discounts.

    Though all the above T 8odes and there are many 5ore standard ",P Reports have veryhigh utility it is not idely used. 8lients prefer customi ed reports hen it comes to

    pricing reports + all L programs and Transactions.

    These !ind of reports are generally required by the Top 5anagement for periodical

    revie 9inance team for price control 5aster data team for record purposes Processaudits by Internal e4ternal agency %f late for every "%E audit done in thecompany...especially the change records for prices.

    %ondition =ndeE

  • 8/10/2019 Pricing Date

    21/88

    8ondition inde4 is very useful for searching the condition record for a customer.It becomes easier and faster to search for condition records for a customer or material Fustli!e it become easier to search a topics in the boo! ith help of inde4.

    'ou have to mar! the condition inde4 chec! bo4 in the condition type and you have to

    activate the inde4 in customi ation.

    'ou can set the discount for fast ten orders through condition update .

    9irst in your discount condition type($ 0@) activate the condition update chec! bo4.

    "econd in the condition record in additional data put ma4imum number of orders as0.

    'ou may also create the condition record for discount through $/1 . 6o go tochange($/1?) scroll to the right you ill find a column 6 . This is ma4imum number

    of order field. >ere you can put value 0 and save it.

    6o system ill give the discount to the first 0 orders.

    #hat =s %ondition 5ase Value"

    #here does the standard condition base value (3efault one) isdeter!ined for a %ondition type"

    9irst chec! the 5aterial 5aster U%5 8onversion + ,dditional -ata + Units of 5easure.

    8ondition base value is a concept used in pricing procedure and actual term used isalternate condition base value. This is a formula assigned to a condition type in order to

    promote an alternate base value for the calculation of the value.

    If you have to calculate price of a material then you have to have a base value for it. 9ore.g. if you ant to calculate the discount of 0 H for a material then you have to have a

    base value on hich this 0H is calculated. 6ormally you ta!e the condition value of the base price of the material to calculate the value.

    6o you don;t ant to ta!e the base value and ta!e other value as base value hich arederived on some formula. "o you create a routine hich ill do the mathematicaloperations in the routine and derive you a value hich is no used as the base value forcalculating the condition value for a particular condition type.

    ,s per my understanding there is ,lternative 8ondition *ase $alue It is a routine hichis assigned to the condition type in the pricing procedure.

  • 8/10/2019 Pricing Date

    22/88

    Jo to transaction $ 0& here you select pricing procedure then go in to the control data ofthe pricing procedure here you can find ,lter native 8ondition

    *ase $alue in the Ath column of the pricing procedure control data.

    #hat is the difference bet een? *. %onditional base value

    . %onditional value.

    . %onditional a!ount

    . 8onditional base value

    Dhen a value is derived for a condition type based on certain calculation this value ista!en as base.

    ?. 8onditional value.

    9or the number of units ordered depending on the condition amount mentioned this valueis derived.

    1. 8onditional amount

    This is nothing but the unit list price hat you are mentioning for the line item.

    *) #hat is the role of alternative calculation typeB condition base valueB require!ent

    in pricing procedure"

    ) #here do e define value for alternative condition base value and alternativecalculation type so that syste! pic&s up different valueB hen the value foralternative condition base value and alternative calculation type is !ention inpricing procedure"

    QQ,lternative 8alculation Type#QQ

    This function allo s you use a formula as an alternative in finding the value of thecondition type instead of standard condition technique. this can be used to calculate

    comple4 ta4 structures.,lternative condition base value

    The alternative condition base value is a formula assigned to a condition type in order to promote an alternative base value for the calculation of a value.

    34ample

  • 8/10/2019 Pricing Date

    23/88

    ,n absolute header discount is for e4ample distributed in the standard system accordingto the cumulative value of the items.

    If the system distributes the absolute header discount according to volume based on the,lternative formula for condition base value a header discount of 10 results in the

    follo ing discounts#

    Item $alue $olume .

    000 ? cbm

    ? :00 A cbm

    "tand. disc. $olume disc.(Dith 9ormula)

    ?0 0

    0 ?0

    8ondition formula for alternative calculation type

    ,lternative formula to the formula in the standard system that determines a condition.

    Requirement

    This function is used to assign a requirement to the condition type. This requirement can be used to e4clude the system from accessing the condition type and trying to determine

    the value. This can be used to specify that the condition type should only be accessed ifthe customer has a lo ris! credit.

    $ounding Off %ondition 1ot Appearing =n 2alesOrder

    =n sales order 3iff condition type is not co!ingB hen chec&ed inanalysis it says require!ent * is not fulfilledB but in pricing procedure =Jveassigned the require!ent as * B alt.cal type-*KB alt %5V->.

    Please refer to the follo ing documentation for requirement 0 1#

    R3 2$@ ,0 1

    Title

  • 8/10/2019 Pricing Date

    24/88

    Rounding as per Table T00 R

    Purpose

    This is an e4ample of a pricing requirement. This requirement is met if an entry has been

    made in the ;Unit to be rounded up to; field in Table T00 R. Table T00 R stores therounding rules for company code and currency combinations. This requirement can beassigned to the condition type in the pricing procedure that is used to calculate thedifference hen rounding. Using this requirement the difference is only calculated hennecessary.

    34ample

    , company has the requirement to carry out rounding for certain company code andcurrency combinations. This information is stored in Table T00 R. In the document

    pricing procedure the user has configured the ",P delivered condition type -I99 to

    calculate the difference hen rounding occurs. The user also assigns pricing requirement; 1; to the condition type -I99 in the pricing procedure so that the condition is onlycalculated hen a corresponding entry has been maintained in the table T00 R.

    Please chec! the customi ing table T00 R.

    or try this go to I5J path ++= ",P 6et eaver ++= Jeneral "ettings ++= 8urrencies ++=-efine rounding rules for currencies. >ere maintain the rounding unit hich ill bestored in Table T00 R.

    then in the t+code obB0 you can maintain that.

    Jo to v 0& maintain in condition base value @ routine.

    Purpose

    This is an e4ample of a condition value formula. This type of formula can be used toinfluence the value sho n for the condition in pricing. , condition value formula isassigned to a condition type or value line in the pricing procedure.

    9ormula ; @; as delivered along ith condition type -I99 to support the rounding unitrules that can be defined in T00 R for company code currency combinations. 8ondition

    type -I99 as delivered to perform the rounding at the end of the pricing procedure iththe total value. Using formula ; @; the system computes the rounded value and assignsthe difference to the condition type -I99.

    In+ 7 c.base value

    Round according to T00 R

  • 8/10/2019 Pricing Date

    25/88

    Purpose

    This is an e4ample of a condition value formula. This type of formula can be used toinfluence the value sho n for the condition in pricing. , condition value formula isassigned to a condition type or value line in the pricing procedure.

    9ormula ; 7; as delivered so that a condition value could be rounded off according tothe rounding unit rules (e.g. plus : or 0 or 00 units) that can be defined in T00 R forcompany code currency combinations. Dhen formula ; 7; is assigned to a conditiontype the condition value ill al ays be rounded using T00 R.

    #here = can do setting of rounding profile for a ne created condition type"

    ) 8reate Rounding rule ( Unit of measure rounding rules )

    Path #5aterials ++= "PR% Nuantity %ptimi ing and ,llo ed ++= %rder %ptimi ing ++=Purchasing ++= 5anagement Unit of 5easure Rounding Rules ++= 2ogistics Units of5easure

    >ere give ne rounding rule and H rounding up and do n values

    ?) 8reate Unit of measure groups

    Path #%rder %ptimi ing ++= Purchasing ++= 5aterials 5anagement ++= "PR% Unit of 5easure

    ++= Nuantity %ptimi ing and ,llo ed 2ogistics Units of 5easure Jroups8reate ne group for '- and R%2

    1) -ynamic rounding profile

    Path #%rder %ptimi ing ++= Purchasing ++= 5aterials 5anagement ++= "PR% 5aintainRounding ++= Nuantity %ptimi ing and ,llo ed 2ogistics Units of 5easure Profile

    >ere give Rounding profile name and plant and clic! on -ynamic to create ne profile

    In ne4t screen give desc. 9or rounding profile rounding off method as ? and roundingrule hich you have created.

    ,ssign created Rounding profile in info record also U%5 group

    5aintain minimum order qty as Rol and %rder unit as R%2 in Info record

  • 8/10/2019 Pricing Date

    26/88

    In material master maintain conversion as Rol < 1:00 yards

    Ho

  • 8/10/2019 Pricing Date

    27/88

    dictionary to create and change fields and tables. 'ou may have to use an ,*,P s!ill toassist you. If the field is from the header table (for e4ample the order table $*,/)youVll need to add it to the include table /%5/,L in table /%5/. If the field is fromthe item table (for e4ample the order item table $*,P) youVll need to add it to theinclude table /%5P,L in table /%5P.

    2etVs say you need to use the Wbase materialX to define a price and the base material is notin the pricing field catalog. The base material is a field on the material master basic datascreen and is defined as 5,R,+DR/"T. "ince this relates to the material it is at theitem level so you ould add the field to the /%5P,L include table.

    6ote Dhen you add a field to these tables it must start ith WLL.X Therefore thefield you add ould be LLDR/"T. In ,*,P hen you add the field use the samedomain as in the field in the original table 5,R,DR/"T.

    ,fter adding the field generate the structure /%5P. This field is not available in the fieldcatalog and can be used in condition tables.

    #riting the A5AP %ode

    The field in the communications structure ill be blan! unless the ,*,P code transfersthe data from the material master to the field /%5PLLDR/"T. Pricing occurs in theorder and in the invoice so you need to put this code in both places. 9or the ordertransaction rite the ,*,P code in user e4itU"3R3EITCPRI8I6JCPR3P,R3CT/%5P in include program 5$A:,9LL. 9or the

    billing transaction rite the ,*,P code in user e4itU"3R3EITCPRI8I6JCPR3P,R3CT/%5P in R$@0,9LL.

    :ote ; $he $=>+P is for the item le/el' f you are !ritin, the co.e fora fiel. at the hea.er le/el9 you !oul. use the user e its that en. !ith$=>+=' $he ? P co.e !oul. select the ?ase material fiel. from thematerial master ta le usin, the material from ta le ? P) ?RP' t !oul.then transfer this fiel. to the structure $=>+P from +> 5 + R WR=S$ to$=>+P-@@WR=S$'

    5illing cannot be $elease to Accounting

    This ",P message ill appear if the system is unable to find the J 2 codes match fromthe configuration in transaction $/%,

    6o account is specified in item 000000 00 5essage no. 9: @70

    -iagnosis 6o account as specified for account type " in item 000000 00 of the 9I 8%document.

  • 8/10/2019 Pricing Date

    28/88

    "ystem Response The 9inancial ,ccounting program cannot process the document.

    Procedure , system error has probably occurred in the application you called up. 8hec! the data

    transferred to item 000000 00 of the 9I 8% document.

    ,ssuming that one of the !ey combination is ,ccount ,ssignment Jroup you ill haveto chec! hether have the ,ccount ,ssignment Jroup been input in the 8ustomer 5aster (*illing tabstrips + ,ccounting sections + 9ield name# ,cct assgmt group).

    The ,ccount ,ssignment Jroup ill be copied automatically into the sales order.

    8hec! hether the configuration in transaction $/%, have been done correctly.

    8hec! hether the sales order ($,01 + Joto + >eader + 9inancial ,ccounting + 9ield

    name# ,cct,ssgJr) have been filled in automatically.

    8hec! hether the billing document ($901 + Joto + >eader + >eader + 9ield name#,cct,ssgJr) have been filled in automatically.

    If the customer master have not been maintained and the user have already input the salesorder then the user ill have to maintained the ,ccount ,ssignment Jroup manuallyeither in the sales order or the billing documents.

    Ta!e note for %ne Time 8ustomer the user have to input the ,ccount ,ssignment Jroupmanually into the sales order. %ne Time 8ustomer can be used by many customer

    therefore the system ill not be able to determine the ,ccount ,ssignment Jroupmanually.

    3efault 2tart Variant for V: >

    There are t o types of variant in V: > .

    %ne is the selection variant before clic!ing the 3isplay 5illing 6ist *utton.

    'ou can set the start variant via 2'L using the %hange mode.

    The second variant is the 5illing 6ayout display variant.

    This is after clic!ing the -isplay *illing 2ist *utton.

    ,fter creating your layout display variant you can set it by clic!ing #+

  • 8/10/2019 Pricing Date

    29/88

    2ettings +=3isplay Variant

    += Ad!inistration

    "elect the layout display variant you ant and clic! #+

    'dit +=3efine default settings

    %ondition 'Eclusion hich ill bedeter!ined in the billing docu!ent

    9** costs */ ,23. 2o!e custo!ers receive a discount of * ,23 per *pieces.

    Ho everB a specific custo!er can buy the !aterial for * ,23. 2ince this is aparticularly good priceB the custo!er should not also have a discount of * ,23 per* pieces.

  • 8/10/2019 Pricing Date

    30/88

    When illin, .ocument is ein, create. Aust enter manually your ne!price an. the pricin, pro,ram lo,ic !ill inclu.e only the hi,her priceone9 e clu.in, the rest that are lo!er price'

    2teps for creating a ne or changing an eEisting 5illing3ocu!ent

  • 8/10/2019 Pricing Date

    31/88

    Target "ourcee.g. 9 + Invoice %R + "tandard "ales %rder

    9 + Invoice L%R + 'our "ales %rder

    *illing documents in V

  • 8/10/2019 Pricing Date

    32/88

    the entire proAect cost or simply a pre-.efine. amount'

    Durin, sales or.er processin,9 the system .etermines from the itemcate,ory !hether a

    illin, plan is reBuire. an.9 if so9 !hich type of plan

    $he type of illin, plan that is .etermine. at this point is set up inCustomi in, an.cannot e chan,e. in the sales .ocument'

    ?illin, plans for perio.ic illin, an. milestone illin, plans forproAect-relate. milestone

    illin, ha/e .ifferent o/er/ie! screens so that you can enter .atarele/ant to yourprocessin,'

  • 8/10/2019 Pricing Date

    33/88

    Deli/ery-rele/ant or.er items for !hich a milestone illin, plan appliesare ille. on the

    asis of the reBueste. .eli/ery Buantity an. not on the total of theconfirme. Buantities'

    $he connection et!een the proAect an. the sales .ocument item is ma.ein the in.i/i.ualsche.ule lines of the item' 5ach sche.ule item can e assi,ne. to anet!or in a proAect'

    $o .isplay the proAect-relate. .ata for a sche.ule line9 procee. asfollo!s;

    n one of the o/er/ie! screens of the sales .ocument9 select

    1' tem -E Sche.ule lines'2' +ar the sche.ule line an. select Procurement .etails'

    $he follo!in, fi,ure sho!s an e ample of milestone illin, !here onlythe Contract ha/e

    een ille. ;

    >r.er tem $ur ine 1009000

    ?illin, Plan

    ?illin, .ate Description F alue ?illin, ?loc +ilestone?illin, Status01-10-*" Contract 10 109000 - 01-03-*# ssem ly 30 309000 01-0"-*# +aintenance 30 309000 01-0#-*# cceptance 30 309000 01-0%-*#

  • 8/10/2019 Pricing Date

    34/88

    *illing plan processing includes the follo ing functions#

    ,utomatic creation of billing plan dates Pricing *illing bloc!

    *illing inde4 *illing status *illing rule for milestone billing 9i4ed dates in milestone billing -ocument flo 8reating ith reference 34change rate determination ,utomatic 8reation of *illing Plan -ates

    In 8ustomi ing for "ales you control ho the system automatically creates the scheduleof dates in a billing plan. The system determines the schedule of individual dates based

    on general date information such as the start and end dates. This general date informationis copied either from contract header data or from proposals in the billing plan type.

    Pricing

    "ales document items are billed as each billing date in the plan becomes due. The systemdetermines the amount to be billed either from the condition records that are applicable tothe item or from the values that are e4plicitly entered in the billing plan for a particular

    billing date. In milestone billing for e4ample you can specify a percentage to be billedor an actual amount.

    5illing bloc&

    , billing bloc! can be set for each date in a billing plan. The bloc! prevents processingfor a particular billing date but does not necessarily affect any of the other dates in the

    plan. In milestone billing the system automatically sets a billing bloc! for each billingdate. This bloc! remains in effect until the proFect system reports bac! that the milestonein the corresponding net or! has been successfully completed. ,t this point the systemremoves the bloc!.

    5illing indeE

    9or every billing date in a plan the system creates and updates a billing inde4. If a billingdate is bloc!ed for billing the system copies this information into the inde4.

    5illing status

    The system assigns a billing status to each billing date in the plan. The status indicates tohat e4tent the billing has been processed for that particular date. ,fter billing has been

  • 8/10/2019 Pricing Date

    35/88

    carried out successfully the billing status is automatically set to 8V. This prevents a billed date from being billed again.

    5illing $ule for +ilestone 5illing

    9or every date in the milestone billing plan you can specify a billing rule. The ruledetermines ho the billing amount for the particular date is calculated. 9or e4ample youcan specify hether the billing amount is a percentage of the total amount or hether it isa fi4ed amount.

    In addition you can specify that the amount to be billed is a final settlement that ta!esinto account billing that has not yet been processed. 9or e4ample price changes may ta!e

    place after billing dates in the plan have already been processed. The price differencescan be ta!en into account during final settlement.

    9inal settlement is not automatically proposed in the billing plan by the systemK you must

    enter it manually during processing.

    :iEed dates in !ilestone billing

    'ou can control for each date in a billing plan hether the date is fi4ed or hether thesystem copies the date from the planned or actual milestone dates in a proFect.

    3ocu!ent flo

    ,fter a particular date in a billing plan is processed for billing the system updates thedocument flo for the corresponding sales document item.

    The document flo for the sales document displays the follo ing data#

    8reation date *illing date *illed value

    %reating ith reference

    Dhen you define a billing plan type in 8ustomi ing for "ales you can enter the number

    of an e4isting billing plan to serve as a reference during subsequent billing plan creation.-uring sales order processing for items that require billing plans the systemautomatically proposes the reference plan and if necessary re+determines the billingdates (based on the current date rules) for inclusion in the ne billing plan.

    'Echange rate deter!ination

  • 8/10/2019 Pricing Date

    36/88

    In the billing plan ith partial billing you can store a certain e4change rate for each date.The amount billed is the amount determined after using this e4change rate to convertfrom the local currency into the document currency.

    ,n e4change rate can also be stored at item level for the sales document (field# 34change

    rate for 9I on the *illing tab page. This fi4ed rate is valid for all dates in the item billing plan for hich no rate is specified in the billing plan. If an e4change rate is entered bothfor the date in the billing plan and at item level in the e4change rate field then the systemuses the rate specified for the date during billing.

    If no e4change rate is entered for the the date or at item level then the system uses thee4change rate used for invoice creation and it is for arded to 9I.

    When usin, a hea.er illin, plan9 all illin, plans lin e. to thishea.er illin, plan are automatically up.ate.' f9 for e ample9 youenter an e chan,e rate manually for the first .ate in the hea.er illin,plan9 this is automatically copie. to the correspon.in, .ates for the

    item illin, plans'

    2AP 5illing - %o!bine 5illing for deliveries ithdifferent date

    Dhen using transaction V: > or *illing (bac!ground) the date of the billing document(e.g. the current date) must be entered (In V: > # settings default data.)

    In V: K or bac!ground# variant ith parametri ation) to avoid an un anted split due tothe billing date.

    This %"" notes is very helpful #+

    ***K + Invoice split criteria in billing document

    K8 + Invoice split in fields from the sales order

    5illing 2pilt by =te! %ategory

    =s it possible to split invoice =te! category ise. = !ean =f in sales order there is

  • 8/10/2019 Pricing Date

    37/88

  • 8/10/2019 Pricing Date

    38/88

    P"T'$ 2I/3 $*,P+P"T'$ Y+ 6e line36- %9 LU/.

    LU/+"P,RT < $*,/+"P,RT.LU/+$TD3J < $*,/+$TD3J.

    LU/+P"T'$ < $*,P+P"T'$. Y+ 6e line$*R/+LU/RI < LU/.

    36-9%R5.

    ,fter this routine is created and activated place it as the default copy control routineinstead of the old ones.

    +aEi!u! nu!ber of ite!s in := reached +essage no.:/ 9 9

    If you hit the above erros hen you create an invoice in "- the correspondingaccounting document is not created.

    The error is as follo s#

    5a4imum number of items in 9I reached 5essage no. :/ 9 9

    3iagnosisThe ma4imum number of items for an 9I document (;BBB;) has been e4ceeded.

    2yste! response 9I documents have a 1+digit item counter that limits the number of items permitted perdocument.

    ProcedureIf the documents ith an e4cessive number of items come from another application area(e.g. sales logistics order accounting) you can configure the system to the effect thatthese documents are summari ed in 9I.

    >o could this error be solved as none of your invoices are getting accounted in 9IG

    To overcome this the only ay as to brea! the accounting invoices ith B:0 itemsand the other ith the rest.

    Prepaid process possible

    +++++%riginal 5essage+++++"ubFect# Prepaid process possible

  • 8/10/2019 Pricing Date

    39/88

    I am loo!ing for information on ho e could implement a prepaid process. *y prepaid process I mean#+ 8ustomer sends to us his order+ If customer is set as prepaid e produce an invoice for him to pay+ %nce e have received his payment e release the sales order for delivery

    + no further billing document is produced.

    I found information in online documentation about do n payments (I imagine that our prepaid process could be a 00H required do n payment) but it does not seem that it

    ould or!. 9rom hat I understood it loo!s li!e the billing plan is handled based upontheitem category hich implies the processing is material specific not customerspecific.

    Dhat e do no #+ De have defined a ris! category prepaid hich is assigned to our prepaid customer.

    This ris! category automatically bloc! the sales order for delivery.+ De receive the sales orders and produce a Pro 9orma invoice from it and send it tocustomer

    + %nce e receive the payment e release the sales order for delivery and produce theinvoices.

    + De post the payment e received earlier against this last invoice.

    ,s you see this requires a lot of manual or! and a lot of time is asted to match alldocuments together. There most be a more efficient ay to handle this anybody have any

    hintsG

    +++++Reply 5essage+++++"ubFect# R3# Prepaid process possible

    >i againZ

    'ou are rightZ >o ever if you create a ne item category for the prepaid scenario youcanselect hat item category (and process) to use at order entry. It is also possible to code auser e4it so that only certain customers ill get the prepaid process. This can be done also

    ith item category groups (can be used to determine hat default item category thatshould appear). This ould mean that you either have different materialnumbers for thedifferent processes or use different distribution channels in the sales order. -8 0 could

    bethe normal process and -8 ?0 the prepaid process. Then you need to create the salesvie s in material master for -8 ?0 for all materials that should be possible to run in the

    prepaid scenario and enter the prepaid item category group in the sales item categorygroup field in material master.

  • 8/10/2019 Pricing Date

    40/88

    >ere is a proposal of customi ing activities to achieve this#. 8reate a ne item category as a copy of the normal item category used for non+prepaid

    sales. (8hange the billing in the item category to order related billing ith no billing plan)

    ?. 8reate a ne item category group LEEE or something of your choice ith thedescription Prepaid or something li!e that.1. In item category assignment add or chec! entries so that you have the order type used

    and item category group defaulting the ne item category.A. 8hec! copy control from sales document to billing document for the ne itemcategory.

    ,lso delivery copy control could be good to chec!.:. 8reate a ne distribution channel and assign it to the company structure (plant sales

    org etc)@. 34tend your material(s) ith vie s for the ne distribution channel and enter the

    LEEE

    item category group in the field for sales item category group (I thin! it is on sales ?screen but I am not sure can;t access a system right no ).

    6o you should be able to create a sales order ith the ne distribution channel herethe ne item category is defaulted. 8hec! that the sales order is completed hen both

    billing and goods issue for the delivery is posted. If not chec! the completion rule in thene item category.

    $estricting 1u!ber Of =te!s =n 5illing 3oc

    Ho = can restrict nu!ber of ite!s in an invoice"

    =f = enter !ore than 8 ite!s in a sales order and those ite!s get copied into deliverydoc then to billing doc. 5ut our client ant to restrict nu!ber ite!s to 8 (!aE) in aninvoice.

    'ou can restrict delivery ith delivery tolerance thereby causing invoicing of thedesired.

    or

    Jo to "PR%===I5J==="ales O -istribution===*illing===*illing-ocuments===8ountry+specific features===5aintain 5a4imum 6o. %f *illing Items.

    This is here you can define a ma4imum number of items allo ed for all billingdocuments ithin a given sales organi ation.

    >o ever maintaining data here is not enough alone to bring about a billing split bynumber of billing items.

  • 8/10/2019 Pricing Date

    41/88

    'ou must also go to copying control for order delivery to billing document at item levelunder -ata $*R/ $*RP and maintain routine 00@ individual invoice limited or asimilar routine that accesses the data maintained here

    3ocu!ent 1ot $elevant :or 5illing

    Ho to resolve 3ocu!ent not relevant for billing error !essage"

    8hec! the detailed error log in $90 screen. De may get more information on error.

    Then chec! have you completed the PJI for the delivery document or not.

    6e4t go to that Item 8ategory functionality $%$7 and find if it is order or deliveryrelated billing.

    ,nd after that go and chec! in the particular "ales order document type hether billingdocument types are maintained in the sales document or not.

    If every thing is correct go and find ith copy controls

    If it order related go $T9,If it -elivery related go $T92 and chec! in your document type combination ismaintained or not if they are maintained item category is available or not.

    After delivery hile creating billing docu!ent syste! sho ing error that no billingdocu!ent is generated for !aterial no L/. 2o ho = can solve this issue.

    8hec! if Item 8ategory is chec!ed for *illing or not.

    1or!al 2ales Order %ycle?-

    2tep *? 2ales 3ocu!ent eader#

    . "ales -ocument Type#The sales document types represent the different businesstransactions such as Inquiry Nuotation "ales %rder etc. To create ne sales order typeal ays copy as ith reference to similar sales order. If possible use standard sales order.?. -efine 6umber Ranges 9or "ales -ocuments# 5aintain number range ith discussion

    ith core team.1. ,ssign "ales ,rea To "ales -ocument Types#,. 8ombine sales organi ations 8ombine distribution channels 8ombine divisions#3nsure to maintain these else "ales %rder creation ill give error.*. ,ssign sales order types permitted for sales areas# ,ssign only required "ales %rderTypes to required "ales ,rea. This ill minimi e selection of "ales %rder Type as persales area.

  • 8/10/2019 Pricing Date

    42/88

    2ales 3ocu!ent =te!? Q . -efine Item 8ategories# If possible use "tandard Item 8ategory. Incase if required tocreate ne copy as from standard O maintain 6e .Q?. ,ssign Item 8ategories# If possible use standard. 9ormula for deriving item category#"ales -ocument Type Item 8ategory Jroup Usage >igher 2evel Item 8ategory :or =ndividual 5illing $un

    2AP :unctional DD0 23 =n 2AP

    Ho to schedule billing to be run auto!atically"

    'ou can create individual *illing documents in $90A ith out any saving of each and

    every billing document.

    "elect all the deliveries hich you ant to create billing documents using 8ntr *uttonand clic! on individual billing. Then all the deliveries ill go for billing individually in asingle run. ,nd you can also see all the billing documents numbers hich are created.

    6o need to select single delivery each time.

    If you ant to do a batch Fob for billing proceed for the follo ing process

    . goto $90A in the selection screen -elivery document range for hich you ant tocreate billing documents e.g. in "- -ocument field give delivery to 0.

    ?.6o 8lic! on J%T% += $ariant += "ave as $ariant then it ill ta!e you to anotherscreen give the variant name e.g. test and save it.

    1. goto "51@ this is used to do batch Fob if you dont !no any thing also you can dothe entire process using S%* DIL,R- clic! on Sob Di ard hich is on the screen.

    A. It ill ta!e you to different steps Fust you need to give your variant name (in Fob namefield) (in the first screen) the continue for further steps In the ,*,P Progamme 6amegive "-*I22-2 (this is the programme used to create billing documents) continue togive the specified time hich you ant to run this batch Fob li!e immediate after an

    hour or a specific day li!e so.

    :. 8ontinue further to complete the tas! no you batch Fob ill run at a specified timehich you mentioned if you mentioned as immediately then once you comple this

    process your vairant ill run and billing documents ill be created.

    @. Plese ensure that all the deliveries are perfect meaning there is no billing bloc! or anything.

    http://www.sap-img.com/index.htmhttp://www.sap-img.com/sap-sd.htmhttp://www.sap-img.com/sap-sd.htmhttp://www.sap-img.com/index.htmhttp://www.sap-img.com/sap-sd.htm
  • 8/10/2019 Pricing Date

    45/88

    'ou can chec! the status of your batch Fob using t. code "517.

    3ifference bet een the $21A2< and 235=6636 progra!.

    R"6,"T00 is a program hich is related to output related activities. Using this programe can schedule the creation of outputs (P-9s email etc) in total for any documentcreated in any of the applications. The details are read and stored in the database table

    6,"T. The same program is customised for each applications using programs li!e"-70,$ , hich are also used for the same purpose but only for sales orders.

    "-*I22-2 is the program for *illing due list. This program finds out all the orders ordeliveries or both hich are due for billing and it ill trigger the billing creation. It readstables li!e $*,/ $*,P $*U/ $*UP 2I/P 2IP" etc and the created billingdocuments are stored in tables $*R/ $*RP.

    'Eplain

  • 8/10/2019 Pricing Date

    46/88

    @) "elect the billing usage and clic! on characteristics. eg++= ,ctivity Type

    7) Then define sources. "elect ,ctual 8ost as e use actual cost for RR*. -efineH

    &) "ources ++= "election 8riteria# This ould display all characteristics. 6o in ,ctivity

    Type ++= 5ention the activity type

    B) If more activity type are being used then create set of activity type using T.code J"0

    0) 5aterial -etermination ++= Initially create material ith 5aterial Type < "ervice

    ) The service material should be mentioned in the material determination

    ?) 8riteria ++ In criteria allocate the activity type for the specific material. (De can alsouse cost element cost center hich e have defined in characteristics)

    1) 8reate ProFect (T.code 8S?06)

    A) 8reate "ales %rder (T.code $,0 )

    :) *oo! 8,T"

    @) 34ecute -PB to vie "ales Pricing

    %o!!on 'rrors? A3 *-*//? 'rror during !aterial deter!ination for sales docu!ent ite!. +aterial

    Origin field as not chec&ed in the %osting tab of the !aterial !aster. =M- /9? 1o cost !anage!ent is provided for sales docu!ent (contract) ite!. 8 ) 1o eEpenditure ite! found.

    Jo bac! to the service order and chec! there are actual costs

    8hec! your -IP ProfileK specifically the sources section to ensure you are not filtering

    out any dynamic items.

    8% 8onfiguration#

    /201# 8hec! activity type validity dates

    /,01# 8hec! cost element validity dates

  • 8/10/2019 Pricing Date

    47/88

    /,01# 9or labour chec! cost element category is A1

    /,01# 8hec! if Record qty flag is set on Indicators tab

    /,01# 8hec! cost element assigned to your controlling area

    /P?@# 8hec! that activity type is lin!ed to cost centre

    /P?@# 8hec! that there is a rate for the activity type cost centre

    /P?@# 8hec! are you using the correct version

    %ancelled 5illing 3ocu!ent Has 1o Accounting3ocu!ent

    $eal 23 2upport ;uestion? = have cancelled a billing docu!ent through vf**.

  • 8/10/2019 Pricing Date

    48/88

    @. 8hec! ith 9I 8onsultant hether ,ccounting entries has been posted ith referenceto customer and Invoice.

    "econd "cenario

    If accounting documents gets generated and you use $9 to 8ancel the invoice thenautomatically the posting document gets reversed and separate number ill be assignedfor those documents. This you can see in the document flo . 8hec! ith 9I 8onsultant.

    Please 8hec! this #

    "PR%+++="ales and -istribution++=*illing -ocuments++=-efine *illing Types

    "elect *illing type " .

    Then chec! Posting *loc! it should be unchec!ed.

    8hec! hether for the " billing document type Posting bloc! has been chec!ed or not. If it has been chec!ed then unchec! it and secondly also chec! in the 9? billing documenttype hether " cancellation billing document type has been assigned or not.

  • 8/10/2019 Pricing Date

    49/88

    control area. 'ou assign customers to specific credit control areas and specify theappropriate credit limits in the customer master record.

  • 8/10/2019 Pricing Date

    50/88

    -elivery type#8redit group for delivery#8redit group for goods issue#

    B. Transaction O5 *

    8redit management 8hange ris! category-efinition of the ris! category for each credit control area. This ris! category can beassigned to a credit account by using Transaction :3 .

    0. Transaction OVA8 >ere the individual credit chec!s for !ey fieldso credit control areao ris! categoryo credit group are set. Ta!e these !ey fields from the above settings and go to the detail

    screen. In particular chec! hether fields Reaction and "tatus bloc! are set

    correctly. To carry out follo +up actions in case of a credit bloc! the credit chec!status must be set (field "tatus bloc! ).

    . Transaction :3 8redit master data for the payer of the relevant document.8redit account#8redit limit#Ris! category#8urrency#

    ?. "ettings for updating the credit values Update of the credit values is required for the

    limitchec! (static or dynamic credit limit chec!).

    1. Transaction OVA9 Update of the credit value is active for the corresponding item type if the chec! bo4 is

    mar!ed. This field corresponds tofield ,ctive receivable in Transaction VOV9 .Item type#,ctive receivable#

    A. Transaction VC 8 Pricing

    In the pricing procedure used for pricing subtotal , must be entered in a line fordetermining the credit value (mar! the pricing procedure and doubleclic! on8ontrol ).Usually the net value plus ta4es is used. This ay the system is determined to use thissubtotal for credit pricing. The credit price is stored in field $*,P+85PR3 and used

    forupdate and credit chec!.'ou can find the used pricing procedure of the order under Item += 8ondition +=

  • 8/10/2019 Pricing Date

    51/88

    ,nalysis .Pricing procedure#2ine ith subtotal < ;,;#

    :. Transaction O5>/

    Dhich update group (field Update ) do you use in the relevant credit control areaGThedefault setting is ? . If you use another update group chec! hether this is fine ithyou. If you open an %"" message please tell us the alternative update group.8redit control area#Update#

    @. Transaction O+O* Dhich !ind of update did you choose for structure "0@@GIn any case "ynchronous update ( ) has to be chosen as the !ind of update.,ll other settings ill lead to errors.

    +$P bloc& for %redit li!it attained %usto!ers

    Ho to bloc& the require!ent (+3 >) generated by the ite! category in a salesorder hen the custo!er has attained the credit li!it"

  • 8/10/2019 Pricing Date

    52/88

    I5P%RT $*U/+85J"T T% DC85J"T 9R%5 535%R' I- ;8R3-IT;.

    I9 DC85J"T < "P,83.53"",J3 I70@(L ).3EP%RT $*U/+85J"T T% 535%R' I- ;8R3-IT;.

    36-I9.

    Q[ R3P2,83Q\ I6"3RT -3$/B@@B0&

    Q[ I6"3RTQ Read the subsequent function information for the messageP3R9%R5 9%9U6CT3ETCR3,- U"I6J J2C9%9U68>,6JI6J 9%9U6CT3ET.53"",J3 I- ;$ ; T'P3 ;3; 6U5*3R ;&AB;

    DIT> 9%9U6CT3ETR,I"I6J 3RR%R.Q\ I6"3RT -3$/B@@B0& ?

    Q[ I6"3RT36-I9.36-9%R5.

    %redit +g!t 3yna!ic chec&ing

    +++++%riginal 5essage+++++"ubFect# 8redit 5gmt -ynamic chec!ing9rom# Richard -ragani

    >i credit e4perts

    -oes anyone !no ho I can automatically re+e4ecute a dynamic credit chec! a fe days prior to shipment for future dated sales orders. ,ny ideas ould be appreciated.

    Rich -ragani

    +++++Reply 5essage+++++"ubFect# Re# 2%J# 8redit 5gmt -ynamic chec!ing9rom# " ami "ubramanyan

    Program R$/R3-0&G %r manually e4ecute function module"-C%R-3RC8R3-ITCR38>38/.

    Regards" ami

  • 8/10/2019 Pricing Date

    53/88

    +++++Reply 5essage+++++"ubFect# Re# 8redit 5gmt -ynamic chec!ing9rom# 2eslie Paolucci

    De chec! credit at the time of the delivery (at delivery creation and before pic!ing) and

    use the bloc!ed sales doc process list to release them. This can be set up in customi ingunder ris! management+= credit management.

    +++++3nd of Reply 5essage+++++

    2ales value field in not getting updated after creatingthe billing

    +++++%riginal 5essage+++++"ubFect# "ales value field in not getting updated after creating the billing

    e are on A.@b. e are going for credit management but facing one problem. in fd1?+customer credit management change + the sales value feild in not getting updated aftercreating the billing.eg. hen i create the order + the order value get updated in the sales value in fd1?. aftercreating the delivery + that value remains same in the feild of sales value. but hen i amgoing for billing (delivery related) the bill value is appearing in ;receivables; but theamountin ;sales value; is not getting reduced. because of this the credit e4posure is increasingcontinuously.update group for corrosponding credit ctrl area is ?. also the item is mar! for credit

    update.can anyone tell the missing lin!Gthan!ing in advance

    +++++Reply 5essage+++++"ubFect# R3# "ales value field in not getting updated after creating the billing

    >i

    'ou need to chec! couple of settings li!e#

    . 'our customer should be assigned the credit control area.?. In your Item 8ategory 8redit should be active.

    Regards

    +++++Reply 5essage+++++"ubFect# R3# "ales value field in not getting updated after creating the billing

  • 8/10/2019 Pricing Date

    54/88

    customer is assign to concorn 88, and item category is mar! for credit active

    +++++Reply 5essage+++++"ubFect# R3# "ales value field in not getting updated after creating the billing

    >i

    8hec! the credit update group in the transaction %*A:. The credit update group controlshen the values of open sales orders deliveries and billing documents are updated. It

    should be ;0000 ?;.

    9urther also refer to the %"" note &@ 1.

    >ave fun

    +++++3nd of 5essage+++++

    3ifference 5et een 2i!ple and Auto!atic %redit%hec&

  • 8/10/2019 Pricing Date

    55/88

    "T,TI8 8R3-IT 2I5IT -3T3R5I6,TI%6 #8hec!ing Jroup Ris! 8atageory 8redit 8ontrol ,rea.

    ,) 8redit 8hec!ing Jroups # Types of 8hec!ing Jroups.

    0 ) "ales0?) -eliveries01) Joods Issue

    ,t all the above 1 levels orders can be bloc!ed.

    *) Ris! 8atageory # *ased on the ris! catageories company decide ho much credit hasto give to the customer.

    >IJ> RI"/ (000 ) # 2%D 8R3-IT2%D RI"/ (000?) # 5%R3 8R3-IT53-IU5 RI"/(0001) # ,verage 8redit

    "tatic 8redit 8hec! it chec!s all these doc value O chec! ith the credit limit

    ) %pen -oc.$alue "ales %rder $alue # Dhich is save but not delievered

    ?) %pen -elivery -oc.$alue # Dhich is delivered but not billed

    1) %pen *illing -oc.$alue # Dhich is billed but not posted to 9I

    A) %pen Item # Dhich is transfered to 9I but not received from the customer.

    -'6,5I8 8R3-IT 8>38/ # ) %pen -oc?) %pen -elivery1) %pen *illingA) %pen Items:) >ori on Period < 3g.15onths

    >ere the "ystem ill not consider the above ? 1O A values for the lost 1 months

    Then assign the "ales -oc O -el -ocuments.

    "ales -oc.Type(%R) credit 8hec!(0) 8redit Jroup (0 )

    8redit 2imit 8hec! for -elivery Type # -el.Type (29) -el 8reditJroup (0?) Joods Issue 8redit Jroup (01)

  • 8/10/2019 Pricing Date

    56/88

    Jiven belo is the set up for credit card payment processing#

    "et Up 8redit 8ontrol ,reas#

    -efine 8redit 8ontrol ,rea

    Transaction# %*A:Tables# T0 A,ction# -efine a credit control area and its associated currency. The Update Jroupshould be 000 ?V. This entry is required so the sales order ill calculate the value toauthori e

    ,ssign 8ompany 8ode to 8redit 8ontrol ,reaTransaction# %*1&Tables# T00,ction# ,ssign a default credit control area for each company code

    -efine Permitted 8redit 8ontrol ,rea for a 8ompany8odeTransaction#Tables# T00 85,ction# 9or each company code enter every credit control area that can be used

    Identify 8redit PriceTransaction# $ 0&Tables# T@&1",ction# To ards the end of the pricing procedure after all pricing and ta4 determinationcreate a subtotal line to store the value of the price plus any sales ta4. 5a!e the

    follo ing entries#"ub to# W,XReqt# W?X,lt8Ty# WAX

    ,utomatic 8redit 8hec!ingTransaction# %$,&Tables# T@B 9,ction# "elect each combination of credit control areas ris! categories and documenttypes for hich credit chec!ing should be bypassed. 'ou need to mar! the field Wno8redit 8hec!X ith the valid number for sales documents.

    "et Up Payment Juarantees

    -efine 9orms of Payment JuaranteeTransaction# %$9-Tables# T@B /,ction# R 1 is delivered ith form W0?X defined for payment cards. %ther than thedescriptor the only other entry should be W1X in the column labeled WPymtJua8atX

  • 8/10/2019 Pricing Date

    57/88

    -efine Payment Juarantee ProcedureTransaction#Tables# T@B 5 T@B %,ction# -efine a procedure and a description.9orms of Payment Juarantee and ma!e the follo ing entries "equential 6umber W X

    Payment Juarantee 9orm W0?XRoutine 6umber W0X Routine 6umber can be used to validate payment card presence.

    -efine 8ustomer Payment Juarantee 9lagTransaction#Tables# T@B P,ction# -efine a flag to be stored in table.8reate 8ustomer Payment Juarantee < WPayment 8ard Payment 8ards (,ll 8ustomerscan use Payment 8ards)X.

    -efine "ales -ocument Payment Juarantee 9lag

    Transaction#Tables# T@B R,ction# -efine the flag that ill be associated ith sales document types that are relevantfor payment cards

    ,ssign "ales -ocument Payment Juarantee 9lagTransaction#Tables# T$,/,ction# ,ssign the document flag type the sales documents types that are relevant for

    payment cards.

    -etermine Payment Juarantee ProcedureTransaction# %$9STables# T@B U,ction# 8ombine the 8ustomer flag and the sales document flag to derive the paymentguarantee procedure

    Payment 8ard 8onfiguration

    -efine 8ard TypesTransaction#Tables# T$8I6

    ,ction# 8reate the different card types plus the routine that validates the card for lengthand prefi4 (etc])$isa 5astercard ,merican 34press and -iscover8reate the follo ing entries for each payment card,53E ,merican 34press L88,R-C8>38/C,53E 5onth-8 -iscover 8ard L88,R-C8>38/C-8 5onthQQQQQ58 5astercard L88,R-C8>38/C58 5onth$I", $isa L88,R-C8>38/C$I", 5onth

  • 8/10/2019 Pricing Date

    58/88

    The Routines can be created based on the original routines delivered by ",P.

    QQQQQ",P does not deliver a card chec! for -iscover 8ard. De created our o n routine.

    -efine 8ard 8ategories

    Transaction#Tables# T$8T',ction# -efine the card category to determine if a

    payment card is a credit card or a procurement card.8reate the follo ing t o entries8at -escription %ne 8ard ,dditional -ata88 8redit 8ards 6o+chec! 6o+chec!P8 Procurement 8ards 6o+chec! 8hec!

    -etermine 8ard 8ategoriesTransaction#

    Tables# T$8T-,ction# 9or each card category map the account number range to a card category.5ultiple ranges are possible for each card category or a mas!ing technique can be used.Jet the card number ranges from user community. *elo is Fust a sample of hat I ama are are the different types of cards.

    $isa 8redit 34pires in 7 days.A00000 A0::00A0::0: A0::ABA0:::: A :B?7A :B?B A?A@01

    A?A@0@ A?7:1?A?7:1A A?&7BBA?&B00 A7 @BBA7 700 ABBBBB

    $isa Procurement 34pires in 7 days.A0::0 A0::0AA0:::0 A0:::AA :B?& A :B?&A?A@0A A?A@0:A?7:11 A?7:11A?&&00 A?&&BB

    5astercard 8redit 34pires in 10 days:00000 :A0ABB:A0@00 ::ABBB::7000 :BBBBB

    5astercard Procurement 34pires in 10 days:A0:00 :A0:BB:::000 ::@BBB

  • 8/10/2019 Pricing Date

    59/88

    ,merican 34press 8redit 34pires in 10 days1A0000 1ABBBB170000 17BBBB

    -iscover 8ard 8redit 34pires in 10 days

    @0 00 @0 BB

    "et "ales -ocuments to accept Payment 8ard Information Transaction#Tables# T$,/,ction# Revie the listing of "ales -ocument types and enter W01X in the column labeledWPTX for each type hich can accept a payment card

    8onfiguration for ,uthori ation Request

    5aintain ,uthori ation RequirementsTransaction# %$B,

    Tables# T9R5,ction# -efine and activate the abap requirement that determines hen an authori ationis sent. 6ote that the follo ing tables are available to be used in the abap requirement($*,/ $*,P $*/- $*U/ and $*UP).

    -efine 8hec!ing JroupTransaction#Tables# 88PJ,,ction# -efine a chec!ing group and enter thedescription. Then follo the belo guidelines for the remaining fields to be filled.,uthReq Routine B0 is set here.

    Pre,u If chec!ed R 1 ill request an authori ation for a .0 and the authori ation ill beflagged as such. (Insight does not use pre+authori ation chec!)., hori on This is the days in the future ",P ill use to determine the value to authori e(Insight does not use auth hori on period).$alid 'ou ill get arning message if the payment card is e4piring ithin 10 days oforder entry date.

    ,ssign 8hec!ing Jroup to "ales -ocumentTransaction#Tables# T$,/,ction# ,ssign the chec!ing group to the sales order types relevant for payment cards

    -efine ,uthori ation $alidity PeriodsTransaction#Tables# T$8I6,ction# 9or each card type enter the authori ation validity period in days.

    ,53E ,merican 34press 10-8 -iscover card 10

  • 8/10/2019 Pricing Date

    60/88

    58 5aster card 10$I", $isa 7

    8onfiguration for clearing houses

    8reate ne Jeneral 2edger ,ccountsTransaction# 9"0Tables#,ction# T o Jeneral 2edger accounts need to be created for each payment card type.%ne for , R reconciliation purposes and one for credit card clearing.

    5aintain 8ondition TypesTransaction# %$&:Tables# T@&:,ction# -efine a condition type for account determination and assign it to accesssequence W,00 X

    -efine account determination procedureTransaction# %$&@Tables# T@&1 T@&1",ction# -efine procedure name and select the procedure for control. 3nter the conditiontype defined in the previous step.

    ,ssign account determination procedureTransaction#Tables#,ction# -etermine hich billing type e are using for payment card process.

    ,uthori ation and "ettlement 8ontrol

    Transaction#Tables# T88,,,ction# -efine the general ledger accounts for reconciliation and clearing and assign thefunction modules for authori ation and settlement along ith the proper R98 destinationsfor each.

    3nter 5erchant I-VsTransaction#

    Tables# T885,ction# 8reate the merchant idVs that the company uses to process payment cards

    ssi,n merchant i.Hs$ransaction;$a les; $CC

    ction; 5nter the merchant i.Hs !ith each clearin,house account

    3unning Process =n %redit +anage!ent

  • 8/10/2019 Pricing Date

    61/88

    'Eplain about dunning process in credit !anage!ent"

    2et me e4plain in simple terms#

    ) 'ou have a 8ustomer hich you had felt he is doing good business and supplied

    material on 8redit of A: days.

    ?) "ince this customer is good as you felt you have not managed 8redit 8hec!s as ell."o he had comfortably reached to the fullest credit (or even more) hich you can affordfor any customer.

    1) %ne fine day you got realised that there is very bad debt ith this customer and needto recover from him and till then there ill be no further supply to the customer.

    A) 'our company;s legal department has laid a policy that inorder to recover any baddebts li!e#

    a) De ill send a normal payment reminder. b) In case customer doesnt respond e ill send at least further reminder (dunningnotice) may be B times

    (B reminders) (-unning level) and hat intervels of time (dunning frequency)c) "till if the customer doesnt resopond for the reminders you ill file a la suit againstthe customer for recovering

    the Payments.d) 9inally after getting veridict you may proceed for auction of his property or as per theorder for 2a .

    6o in ",P the definition of -unning procedure is a pre+defined procedure specifying

    ho customers or vendors are dunned.9or each procedure the user defines+ 6umber of dunning levels+ -unning frequency+ ,mount limits+ Te4ts for the dunning notices

    In ",P you ill maintain the -unning Procedure at customer master. Referring to thisyour "- Team 9I Team (user team) ill effect -unning

    P"# 'ou might remembered the dunning procedure laid by Relaince 5obile sometime bac! sending street ro dies for recovering the bad debts from users. That is dunning.Remember Reliance you ill not forget dunning forever.

    #hat =s %redit 'Eposure

    #hat do you !ean by credit eEposure"

  • 8/10/2019 Pricing Date

    62/88

    They are the transactions ith a customer that are relevant for credit limits on a specifieddate.

    The credit e4posure is updated based on the update algorithm assigned to the creditcontrol area.

    0000 ? + updated at "ales %rder0000 : + updated at -elivery0000 & + updated at *illing

    To loo! at only Receivables for a customer loo! in 9-1?. If you have bad data run thereorgani ation program through "31&.

    8hec! 6ote A?::?1 + 8ollection of consulting notes# 8redit update and related.

    "urely you must run report R$/R3-77 (6ote A001 + R$/R3-77# Reorgani ation

    credit data ne documentation and related ill help you).

    *. Ho is credit eEposure calculated (seen in :3 )"

    ItVs simple summation of Receivables "pecial liabilities (li!e do n payments advance) "ales value

    . =f ,pdateD * in %%Ar then on creating 2ales OrderB the eEposure increasesby 2O value. 5ut if updateD */B then also on creating 2ales OrderB the eEposure increases by2O value.

    =s this correct"

    I thin! in case of 0000 : %pen sales order values should not be considered.

    . #hat role eEposure play in the credit !anage!ent process. = !ean does thesyste! !atch the value of credit eEposure ith credit li!it to find that it is eEceededor it does it differently"

    8redit e4posure is in fact the main player. In credit management if the customerVs creditlimit is 0000 and credit e4posure is BB00 then customer can only be able to buy no

    orth of 00 only. ItVs the credit e4posure hich should not crossed over the credit limit.

    9or reporting purpose here e can get customer credit e4posure hich sho ing in9-1?.

    Jo to t.code 9.1 for an overvie of the credit e4posure and also you can usesC,2RC&70 ? ?? & to overvie the credit e4posure.

    2AP 23 %=1 %onfiguration

  • 8/10/2019 Pricing Date

    63/88

    *y "hesagiri

    #hat is %=1" 8I6 5eans 8ountry India $ersion

    In Indian Ta4ing procedure 34cise -uty plays a vital role in manufacturing cenarioVs.34cise related configuration is !no n as 8I6 configuration. 8I6 8onfiguration is a topicin itself.

    "ome info on 8I6 8onfiguration (it may not appear as understandable belo but if youchec! on screen it ill be understood better)

    8ountry $ersion India comes ith four pricing procedures as follo s#+ SI69,8 ("ales from manufacturing plants)+ SI63EP (34port sales)+ SI6-3P ("ales from depots)

    + SI6"T/ ("toc! transfers

    8I6# I5J = 2ogistics + Jeneral = Ta4 on Joods 5ovement = India = *asic "ettings =5aintain 34cise Registrations

    In this I5J activity you maintain the data relating to your e4cise registrations.+ 3nter each of your e4cise registrations specifying a four+character code for each 34ciseRegistration Ids

    In this activity you maintain e4cise registration I-s. 'ou create one I- for each of your business;s e4cise registrations.

    + 9or each e4cise registration in your business create a registration I- and state#+ Dhich ta4es the registration covers (additional e4cise duty special e4cise duty andcess) 9ields for any ta4es that are not covered ill be hidden in transactions involvinge4cise duty.+ The ma4imum number of items to be printed on each e4cise invoice+ Dhether you are allo ed partial 836$,T credits

    5aintain Registration I- 6U5*3R 34cise code number e4cise registration number

    388 6umber# "pecifies the organi ation;s 388 number.34cise Registration 6umber# , number assigned to each premises or location that has

    registered as a manufacturer ith the e4cise authorities.3very entity ith an e4cise registration number is required to !eep its o n e4cise boo