Confirmation Error

[Former Member]

Hi,

The confirmation was created from SUS system against limit PO. After created the confirmation, the table <b>BBP_PDIGP</b> is updated with wrong entry of the filed “<b>QUAN_CF_E</b>” and "<b>QUAN_CF</b>". Wrong entry means quantity set’s with – sign for example (833,000-). So for that when ever we open the confirmation it’s going dump error.

Please suggest solving this issue.

Thanks,

Senthil.

[Former Member]

Hi

Which SRM version are you using ? How this problem happened ?

<b>Meanwhile, try the following SAP OSS notes -></b>

Note 856185 - SRM40-SUS: Quantity proposal incorrect when creating conf

Note 1058510 - Limit Order Line can be deleted when open confirmation

Note 865410 SRM50-SUS: Missing follow-on doc buttons in sched agrmnt rel

Note 888122 - SUS purchase order with cancelled item can not be archived

Note 813869 SRM40-SUS: Follow-on doc buttons displayed incorrectly (2)

Note 798577 SRM40 SUS: Follow-on document buttons displayed incorrectly

Note 731037 Converting SUS 1.0 and SUS 2.0 documents to SUS 3.0

Do let me know.

Regards

- Atul

[Former Member]

Atul,

Thanks for your responce.

We are using SRM 4.0 Version.

I checked all the OSS message, the first note (856185) is the one related to this issue. And also it was implemented as before.

I appreciate your quick response.

[Former Member]

Hi,

I found the related OSS note # 632620 and I applied the note as well. Still I am facing the same dump error in the system.

Regards,

Senthil.

[Former Member]

Hi

Incase nothing helps, take help of ABAP person here. Using SE11 transaction, Manually, change the table entry in the table BBP_PDIGP from -VE (negative) value to a +VE (positive) value and then try again.

Do let me know.

Regards

- Atul

[Former Member]

Senthil,

I have same problem in production for only one PO. I looked in BBP_PDIGP table, QUAN_CF_E and QUAN_CF have negative values. Could you please tell me, how you did for this problem.

Regards

Gopi

[Former Member]

Gopi,

Sill i am facing the same problem. I am tracing the root cause the probelm. Let you know if i found somthing. Let me know if you found somthing.

Regards,

Senthil.