Skip to Content
avatar image
Former Member

pricing

Hello SAP Gurus,

what are the tickets that can be faced in pricing and credit management in Real time scenariol.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

5 Answers

  • Best Answer
    avatar image
    Former Member
    Aug 21, 2007 at 11:28 AM

    Hi,

    PRICING

    1. Tax not getting calculated

    2. New condition types - their control

    3. Condition supplement control

    4. Using columns like 'reqt', 'AltTy', 'BasTy'.

    5. Tax not getting displayed in the Excise invoice.

    CREDIT MANAGEMENT

    1. System not showing message even if credit limit has exceeded.

    2. Controlling the static and dynamic credit control.

    3. delivery block when credit limit has exceeded.

    Reward points if solution helps.

    Regards,

    Allabaqsh G. Patil

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Aug 22, 2007 at 03:19 AM

    every post in this forum relating to pricing is an issue by itself...so don't think of real time tickets as some "rocket science issues" that are completely different....

    i understand that you are new to SAP, so read through all the pricing issues that are posted on the forum, understand them and try and replicate the scenarios in your sandbox....and thats what are the issues..and thats what you will say you have resolved..

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Aug 21, 2007 at 11:21 AM

    Hi

    <b>Pricing: Real Time Tickets</b>

    This is very specific & differs from client to client & may also differ based on scenario.

    Write-up on Pricing -

    In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.

    In SD, the steps to configure Pricing procedure are as under:

    Step 1:

    Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).

    Step 2:

    Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.

    Step 3:

    Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the necessary changes. Here we assign Access sequence to Condition type.

    Step 4:

    a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the necessary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.

    b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.

    5. Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.

    It is assumed that document pricing procedure, customer pricing procedure , ... are in place.

    Sales Document not assigned to Sales Area:

    SPRO --> Sales & Distribution --> Sales --> Sales Documents --> Sales Document Header --> Assign Sales Area To Sales Document Types --> Assign sales order types permitted for sales areas (do ensure to maintain combined Sales organization, combined Distribution channel & combined division. for eg: Sales org 1000 & sales org 1000, Sales org 2000 & sales org 2000, & so on ....

    similarly for distribution channel & Division, so that the Sales area combination is available for assignment to Sales Document Type.)

    Issues related to Customer Master data:

    1. what is the impact of leaving customer pricing procedure & customer statistic group blank in customer master --> sales area data --> sales tab:

    If Customer Pricing Procedure is left blank, Pricing will not be determined.

    If customer statistic group is left blank, then data will not flow to standard reports.

    2. Who maintains reconciliation account in customer master?

    Ideally, reconciliation account is maintained by FI person, but if SD person is authorized & has the knowledge of which reconciliation account to be maintained, then even SD person can maintain the same.

    3. Terms of payment appear in Company Code Data & sales Area Data. What is the impact of each? why is it not populated automatically, once it is maintained at either field?

    Terms of payment from company code data is for reporting purpose & it is from sales area data that it flows to sales order.

    It is a standard feature of SAP that it is not populated automatically if maintained at either of the field, but it is a must in sales area data & can be skipped in company code data.

    4. Unable to select Sales Area for Customer Master Creation?

    Most Probably either sales area is not defined or customization not done for common Sales Org & Common Distribution Channel. To maintain this configuration: SPRO --> Sales & Distribution --> Master Data --> Define Common Distribution Channels / Define Common Divisions

    Other queries:

    Where is the control for Automatic PGI?

    For this you can set batch jobs. T-code SM36, 37 38 or you can use the userexit CSO_P_DLVRT_GOODS_ISSUE_CREATE - auto PGI

    The above are few examples.

    /message/3690162#3690162 [original link is broken]

    Reward if it helps

    Regards

    Prasanna R

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Aug 21, 2007 at 11:21 AM

    hi

    Pricing:

    This is very specific & differs from client to client & may also differ based on scenario.

    Write-up on Pricing -

    In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.

    In SD, the steps to configure Pricing procedure are as under:

    Step 1:

    Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).

    Step 2:

    Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.

    Step 3:

    Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the necessary changes. Here we assign Access sequence to Condition type.

    Step 4:

    a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the necessary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.

    b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.

    5. Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.

    It is assumed that document pricing procedure, customer pricing procedure , ... are in place.

    also refer to

    /message/3690162#3690162 [original link is broken]

    /message/3969535#3969535 [original link is broken]

    Reward if USeful

    Thanx & Regards..

    Naren..

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Aug 21, 2007 at 11:28 AM

    refer the sdn link below

    /message/3968925#3968925 [original link is broken]

    Add comment
    10|10000 characters needed characters exceeded