cancel
Showing results for 
Search instead for 
Did you mean: 

V.25 (RVKPR002) Expected Price Report only catches EDI1 / EDI2 condition type?

Former Member
0 Kudos

Hi,

I'm working on a requirement where if a certain minimum price is not met for a sales order line item, the sales order should go into in-complete status like how EDI1 and EDI2 function.

I created a custom Z* pricing condition and instead of using calculation type 8 or 9, I used a custom calculation type routine which compares the net price of the item with the minimum price value set in the Z* condition.

If the net price is less than the minimum price then VBAP-CEPOK would be set to B etc....

The Sales Order goes into in-incomplete status where the in-completion log says "Expected Price" just like how EDI1 / EDI2 function but when I execute V.25, the sales order is not appearing.

Does anybody know whether V.25 (RVKPR002) only looks at sales order line items with VBAP-CEPOK = B and those with EDI1 / EDI2 conditions?

Thanks.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member

Hi.

The issue has been solved.

I set the condition category of my Z* pricing condition type to 'J' (Customer expected price / customer val) which is the same as the category found in both EDI1 and EDI2.

Afterwards, V.25 was able to pick up the sales order.

Answers (0)