Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Internal pricing error V1806

Former Member
0 Likes
4,983

Hi Experts,

I am creating PO from Order (VA01) using BAPI_PO_CREATE1 in user exit MV45AFZZ - USEREXIT_SAVE_DOCUMENT_PREPARE.

I am not passing any price or prising conditions to BAPI.  BAPI is returning the PO number and after coming out from BAPI. I am getting an popup message STOP - Internal Prising Error.

+Internal pricing error

Message no. V1806

Diagnosis

The program link between tables KOMT1 and XKOMV using the XKOMV-IX_KOMT1 field no longer works in the pricing program SAPLV61A. This could be because the PRICING_REFRESH function module has been called up from another function module, even though you did not require it.+

Even though bapi returned the PO number there is no PO exists with that number.

Please provide you valuable inputs.

Thanks & Regards-

Pranab

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
3,258

Hi,

Take out the PO creation part out of the include MV45AFZZ ( via background job ) and come with the PO number to update the SO. Hope this will solve the issue.

Hi Experts,

I am creating PO from Order (VA01) using BAPI_PO_CREATE1 in user exit MV45AFZZ - USEREXIT_SAVE_DOCUMENT_PREPARE.

I am not passing any price or prising conditions to BAPI.  BAPI is returning the PO number and after coming out from BAPI. I am getting an popup message STOP - Internal Prising Error.

+Internal pricing error

Message no. V1806

Diagnosis

The program link between tables KOMT1 and XKOMV using the XKOMV-IX_KOMT1 field no longer works in the pricing program SAPLV61A. This could be because the PRICING_REFRESH function module has been called up from another function module, even though you did not require it.+

Even though bapi returned the PO number there is no PO exists with that number.

Please provide you valuable inputs.

Thanks & Regards-

Pranab

6 REPLIES 6
Read only

Former Member
0 Likes
3,258

Can you please elaborate the business requirement.

Regards,

Tanmoy


Read only

0 Likes
3,258

Hi Tanmoy,

I need to create a PO to automate business process during sales order creation(VA01) and need to attach the PO no in your reference field of order data tab (header).

That is the requirement.

In USEREXIT_SAVE_DOCUMENT_PREPARE i am creating PO by calling BAPI_PO_CREATE1.

After generating the PO when the rest operations are being performed to save the SO i am facing a pop up "Internal pricing error" V1806.

I can find the PO in me23n but no SO is generated due to this abend message.

Regards-

Pranab

Read only

0 Likes
3,258

I don't think that is the right user-exit where we can do that activity of creating a PO. Can you please comment out the code & see if it is still giving that error or not.

It seems to be an internal error -> As per the description of the user-exit this should be used for checks before document save. Can you try to use USEREXIT_SAVE_DOCUMENT & see what happens. This user-exit is used to save data in additional tables when the document is saved.

FORM USEREXIT_SAVE_DOCUMENT.

* Example:

* CALL FUNCTION 'ZZ_EXAMPLE'

*      IN UPDATE TASK

*      EXPORTING

*           ZZTAB = ZZTAB.

ENDFORM.

Please check & let me know.

Regards,

Tanmoy

Read only

0 Likes
3,258

I am not sure about my first solution. I found one SAP Note -> 484256 - Termination of pricing with V1806.

Please check the SAP Note. Incorrect setting of pointers (to the incorrect KOMT1) leads to problems during the processing of the next document which can even lead to the above termination.

Regards,

Tanmoy


Read only

0 Likes
3,258

HI Tanmoy,

I am using Component version EHP 7 where already the changes of note 484256 exists..

Secondly i cannot create PO in SAVE_DOCUMENT as i need to push the PO number to a specific field in SO. When SAVE_DOCUMENT is called vbak-vbeln is populated with order no already.

Hence it is not closing the issue...

Thanks

Pranab

Read only

Former Member
0 Likes
3,259

Hi,

Take out the PO creation part out of the include MV45AFZZ ( via background job ) and come with the PO number to update the SO. Hope this will solve the issue.