cancel
Showing results for 
Search instead for 
Did you mean: 

While we create Sales order in CRM for Madhya Pradesh State JIVP (VAT Payable) showing twice in order

former_member552168
Participant
0 Kudos

Dear SAP,

While we create Sales order in CRM for Madhya Pradesh State JIVP (VAT Payable) showing twice in order, but calculation has taken one time i.e. 14%, only JIVP displaying twice (Attached Screen shot S3.JPG) in CRM order, when comes to ECC side it is showing correct entry (Attached Screen shot S4.JPG) .

Due to duplicate condition records exist in CRM table CNCCRMPRCUS956 (Attached Screen shot S1 & S2.JPG).

This happens for MP state, as duplicate entry exist with MP state only,

Please guide us to resolve the same.

Regards,

JK

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi JK,

There is two thing. first is that when you create a sales order very same time pricing conditions added in the transaction as per the pricing procedure add for transaction type. these pricing procedures are transaction type specific not state or country specific so it will work. check here you are getting duplicate condition ?

When ever you add material in the transaction that very time one the basis of the pricing condition added in the transaction IPC method do pricing. check after adding material in transaction duplicate condition is coming ?

Secondly whenever the document replicates in ERP re-pricing again happening on conditions so theses conditions get corrected in ERP. Here if document is re-priced then system will consider it as change so again there suppose to be Bdocs get created from ERP to CRM again overwrite document so condition will be synchronized in CRM . I would request check the same too and revert.

Thanks,

Prem,

former_member552168
Participant
0 Kudos

Hi Prem,

Thanks for your reply.

We found solution, how duplicate records been happened.

Once again thanks for your suggestion.

Regards,

JK.

Former Member
0 Kudos

Hi J K,

You welcome... Nice to know the issue has been resolved. You can now close the thread.

Cheers,

Prem