SD Error?????

[Former Member]

Hi Sapians,

We are unable to convert the req to a PO due to error SD 18024 on the MM side. On the SD side the error message "No pricing listed because PO was not selected" occurs. The SO is complete, Credit OK, Configuration green, qty confirmed.

Appreciate if you could please advice the right procedure to handle the issue.

Thanks in advance.

MM

[Former Member]

The pricing to be calculated at PO level, Info-Record may have to be maintained, based on PO condotion type. Try checking maintaintining condition record for PO Condition type in Transaction Code: FV11. If possible, take guidance from MM consultant.

Regards,

Rajesh Banka

[Former Member]

Hi Mohammed,

We determine how the prices are calculated, taking into account sales area(sales org, distribution channel, division), document type and customer(generally sold-to-party).

The main differences between pricing procedures would be the differences as we mentioned above, from the point of view of field entries. Coming to the output and the procedure, Suppose the condition types used will be different and hence the following whole procedure. One pricing procedure determination to the others, which data control these differences

The main differences between pricing procedures would be the differences as I mentioned above, from the point of view of field entries.

Coming to the output and the procedure, I suppose the condition types used will be different and hence the following whole procedure.

As rajesh banka had explained..

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 -> Basic Function -> 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 -> Basic Function -> 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 -> Basic Function -> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary 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 neccesary 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 -> Basic Function -> 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 -> Basic Function -> Pricing Procedure --> Determine Pricing Procedure.

Step 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.

if you give me brief i can help you out more.

if helpful REWARD points

Thank you .

Regards

Ram