Bapi_PR_Create - Enter valuation price error

Hi all,
I'm using the BAPI_PR_CREATE and it's giving me the "Enter Valuation Price" Error.
Does any one can tell me what is the fields for passing the Valuation Price?
I'm not really sure.
I'm Using the PRITEM-PREQ_PRICE (and I'm not forgeting the PRITEMX ).
Thanks in advanced.
Miguel

Hi
The valuation price of the material is not picked up from the field PRITEM-PREQ_PRICE in the BAPI.
Please maintain the Price in the material master in the accounting view , then only the price will be picked up.
If you are not able to do so please maintain the price of the material using MR21.
Even though you fill the field the valuation price in BAPI this will always be over written by the Material price.
Thanks & Regards
Kishore
Edited by: Kishore Kumar Chiluka on May 15, 2008 2:53 PM

Similar Messages

Valuation price Error

Hi All,
I am trying to create a P.Req for a VC part, iam getting the follwoing error.
" Enter Valuation price ", even though i maintained the Valuation class and Price Control fields.
The weired thing is, it's not shwoing any error for another VC material with the same settings except, the one working has price control as 'V' and moving average price is defined as 1USD.
the one which is not working has price control as ' V' but iam not able to maintain the Moving average price
,i can only fill in the Std Price field, it graded out the moving price field...
It's a kind of urgent scenario.. if any body can give some hints where i need to check,, it wil be really appreciated
Thanks,
Kanth

please check the material type
i am saying this because in standard system we have 2 material type for finished good but bot are finished good so the seetings for both vary
step1 chec the material type not buy the short desciption but the technical word of the material type then goto tcode oms2 and select the materila type and click ondetail buttonto check the price control indicator in back end

Enter Net Price Error in SRM System

Dear Gurus,
The user has created Purchase order in SRM Portal without flagging 'Confirmation-Related Invoice Verification' and 'Invoice Expected'. The PO is transferred to R/3 system with '0' price and free goods indicator. Then the user modified the PO in the portal, flagging the Confirmation-Related Invoice Verification & Invoice Expected indicator.
Now the changes is not getting transferred to R/3 and getting error message as 'Enter Net Price' in RZ20.
Is there any note on this issue.
Please throw some light to resolve this issue.
Regards,
Suresh

Hi,
Since you have flagged Invoice Expected indicator, make sure you enter a non zero price when you change the PO.
Alternatively you could implement note 1532505 and check
Regards,
Nikhil

BAPI_PR_CREATE enter GL account error

Hi Experts,
I a using babi BAPI_PR_CREATE to create a PR with two line items. but I am getting error 'Enter GL account'.
Please check below program and let me know if anything wrong in it.
data: lv_prnum type BAPIEBANC-PREQ_NO.
data: lv_prnumber type BAPIMEREQHEADER-PREQ_NO.
data: it_req_item type table of BAPIEBANC,
      wa_req_item type BAPIEBANC.
data: it_req_item_new type table of BAPIEBAN,
      wa_req_item_new type BAPIEBAN.
data: it_acc_assig type table of BAPIEBKN,
      wa_acc_assig type BAPIEBKN.
data: it_req_ser type table of BAPIESLLC,
      wa_req_ser type BAPIESLLC.
data: it_ser_val type table of BAPIESKLC,
      wa_ser_val type BAPIESKLC.
data: it_return type table of BAPIRETURN,
      lv_return type BAPIRET2.
data: lv_msg type char50.
data: it_change_return type table of BAPIRET2,
      wa_change_return type BAPIRET2.
data: it_pritem type table of BAPIMEREQITEMIMP,
      wa_pritem type BAPIMEREQITEMIMP.
data: it_pritemx type table of BAPIMEREQITEMX,
      wa_pritemx type BAPIMEREQITEMX.
data: it_pritemexp type table of BAPIMEREQITEM,
      wa_pritemexp type BAPIMEREQITEM.
data: it_praccount type table of BAPIMEREQACCOUNT,
      wa_praccount type BAPIMEREQACCOUNT.
data: it_praccountx type table of BAPIMEREQACCOUNTX,
      wa_praccountx type BAPIMEREQACCOUNTX.
data: it_ret type table of BAPIRET2,
      wa_ret type BAPIRET2.
data: it_prheader type table of BAPIMEREQHEADER,
      wa_prheader type BAPIMEREQHEADER.
data: it_prheaderx type table of BAPIMEREQHEADERX,
      wa_prheaderx type BAPIMEREQHEADERX.
data: it_ser_acc type table of BAPI_SRV_ACC_DATA,
      wa_ser_acc type BAPI_SRV_ACC_DATA.
data: it_ser_accx type table of BAPI_SRV_ACC_DATAX,
      wa_ser_accx type BAPI_SRV_ACC_DATAX.
*first item - material
wa_pritem-PREQ_ITEM = '00010'.
wa_pritem-PUR_GROUP = 'ITD'.
wa_pritem-preq_name = 'abcd'.
wa_pritem-SHORT_TEXT = 'ABC'.
wa_pritem-MATERIAL = 'NCAD100001'.
wa_pritem-PLANT = '1100'.
wa_pritem-TRACKINGNO = 'XXX'.
wa_pritem-MATL_GROUP = 'Z111'.
wa_pritem-QUANTITY = 1.
*wa_pritem-UNIT = 'AU'.
wa_pritem-PREQ_DATE = '20140430'.
wa_pritem-DELIV_DATE = '20140505'.
wa_pritem-PRICE_UNIT = 1.
*wa_pritem-ITEM_CAT = ' '.
wa_pritem-ACCTASSCAT = 'N'.
*wa_pritem-des_vendor = '0050000793'.
*wa_pritem-fixed_vend = '0050000793'.
wa_pritem-PURCH_ORG = '1000'.
append wa_pritem to it_pritem.
*2nd item - service
clear wa_pritem.
wa_pritem-PREQ_ITEM = '00020'.
wa_pritem-PUR_GROUP = 'ITD'.
wa_pritem-preq_name = 'abc'.
wa_pritem-SHORT_TEXT = 'ABC'.
*wa_pritem-MATERIAL = 'NCAD100002'.
wa_pritem-PLANT = '1100'.
wa_pritem-TRACKINGNO = 'XXX'.
wa_pritem-MATL_GROUP = 'S0010'.
wa_pritem-QUANTITY = 1.
*wa_pritem-UNIT = 'AU'.
wa_pritem-PREQ_DATE = '20140430'.
wa_pritem-DELIV_DATE = '20140505'.
wa_pritem-PRICE_UNIT = 1.
wa_pritem-ITEM_CAT = '9'.
wa_pritem-ACCTASSCAT = 'N'.
*wa_pritem-des_vendor = '0050000793'.
*wa_pritem-fixed_vend = '0050000793'.
wa_pritem-PURCH_ORG = '1000'.
wa_pritem-pckg_no = '0000000001'.
append wa_pritem to it_pritem.
*fields for 1st item - material
wa_pritemx-PREQ_ITEM = '00010'.
wa_pritemx-PREQ_ITEMX = 'X'.
wa_pritemx-PUR_GROUP = 'X'.
wa_pritemx-preq_name = 'X'.
wa_pritemx-SHORT_TEXT = 'X'.
wa_pritemx-MATERIAL = 'X'.
wa_pritemx-PLANT = 'X'.
wa_pritemx-TRACKINGNO = 'X'.
wa_pritemx-MATL_GROUP = 'X'.
wa_pritemx-QUANTITY = 'X'.
*wa_pritem-UNIT = 'AU'.
wa_pritemx-PREQ_DATE = 'X'.
wa_pritemx-DELIV_DATE = 'X'.
wa_pritemx-PRICE_UNIT = 'X'.
*wa_pritem-ITEM_CAT = ' '.
wa_pritemx-ACCTASSCAT = 'X'.
*wa_pritemx-des_vendor = 'X'.
*wa_pritemx-fixed_vend = 'X'.
wa_pritemx-PURCH_ORG = 'X'.
append wa_pritemx to it_pritemx.
*fields for 2nd item - service
clear wa_pritemx.
wa_pritemx-PREQ_ITEM = '00020'.
wa_pritemx-PREQ_ITEMX = 'X'.
wa_pritemx-PUR_GROUP = 'X'.
wa_pritemx-preq_name = 'X'.
wa_pritemx-SHORT_TEXT = 'X'.
wa_pritemx-MATERIAL = 'X'.
wa_pritemx-PLANT = 'X'.
wa_pritemx-TRACKINGNO = 'X'.
wa_pritemx-MATL_GROUP = 'X'.
wa_pritemx-QUANTITY = 'X'.
*wa_pritem-UNIT = 'X'.
wa_pritemx-PREQ_DATE = 'X'.
wa_pritemx-DELIV_DATE = 'X'.
wa_pritemx-PRICE_UNIT = 'X'.
wa_pritem-ITEM_CAT = 'X'.
wa_pritemx-ACCTASSCAT = 'X'.
*wa_pritemx-des_vendor = 'X'.
*wa_pritemx-fixed_vend = 'X'.
wa_pritemx-PURCH_ORG = 'X'.
wa_pritem-pckg_no = 'X'.
append wa_pritemx to it_pritemx.
*Account assignment data for 1st item - material
wa_praccount-PREQ_ITEM = '00010'.
wa_praccount-SERIAL_NO = '01'.
wa_praccount-QUANTITY = 1.
wa_praccount-DISTR_PERC = '1.00'.
wa_praccount-NET_VALUE = 1.
wa_praccount-GL_ACCOUNT = '0040100801'.
wa_praccount-UNLOAD_PT = 'ABC'.
wa_praccount-CO_AREA = '1000'.
wa_praccount-NETWORK = '000004011841'.
append wa_praccount to it_praccount.
*Account assignment data for 2nd item - service
clear wa_praccount.
wa_praccount-PREQ_ITEM = '00020'.
wa_praccount-SERIAL_NO = '02'.
*wa_praccount-QUANTITY = 1.
*wa_praccount-DISTR_PERC = '1.00'.
*wa_praccount-NET_VALUE = 1.
wa_praccount-GL_ACCOUNT = '0040100801'.
wa_praccount-UNLOAD_PT = 'ABC'.
wa_praccount-CO_AREA = '1000'.
wa_praccount-NETWORK = '000004011841'.
append wa_praccount to it_praccount.
*Account assignment fields for 1st item - material
wa_praccountx-PREQ_ITEM = '00010'.
wa_praccountx-SERIAL_NO = '01'.
wa_praccountx-PREQ_ITEMX = 'X'.
wa_praccountx-SERIAL_NOX = 'X'.
wa_praccountx-QUANTITY = 'X'.
wa_praccountx-DISTR_PERC = 'X'.
wa_praccountx-NET_VALUE = 'X'.
wa_praccountx-GL_ACCOUNT = 'X'.
wa_praccountx-UNLOAD_PT = 'X'.
wa_praccountx-CO_AREA = 'X'.
wa_praccountx-NETWORK = 'X'.
append wa_praccountx to it_praccountx.
*Account assignment fields for 2nd item - service
clear wa_praccountx.
wa_praccountx-PREQ_ITEM = '00020'.
wa_praccountx-SERIAL_NO = '02'.
wa_praccountx-PREQ_ITEMX = 'X'.
wa_praccountx-SERIAL_NOX = 'X'.
*wa_praccountx-QUANTITY = 'X'.
*wa_praccountx-DISTR_PERC = 'X'.
*wa_praccountx-NET_VALUE = 'X'.
wa_praccountx-GL_ACCOUNT = 'X'.
wa_praccountx-UNLOAD_PT = 'X'.
wa_praccountx-CO_AREA = 'X'.
wa_praccountx-NETWORK = 'X'.
append wa_praccountx to it_praccountx.
*2nd item Service details
wa_ser_acc-doc_item = '00020'.
wa_ser_acc-outline = '0000000001'.
wa_ser_acc-srv_line = '0000000010'.
wa_ser_acc-serial_no = '02'.
wa_ser_acc-serial_no_item = '02'.
wa_ser_acc-quantity = 10.
append wa_ser_acc to it_ser_acc.
*2nd item Service fields
wa_ser_accx-doc_item = '00020'.
wa_ser_accx-outline = '0000000001'.
wa_ser_accx-srv_line = '0000000010'.
wa_ser_accx-serial_no = '02'.
wa_ser_accx-serial_no_item = 'X'.
wa_ser_accx-quantity = 'X'.
append wa_ser_accx to it_ser_accx.
*Header details
wa_prheader-pr_type = 'PURE'.
wa_prheaderx-pr_type = 'X'.
CALL FUNCTION 'BAPI_PR_CREATE'
EXPORTING
    PRHEADER                     = wa_prheader
    PRHEADERX                    = wa_prheaderx
*   TESTRUN                      =
IMPORTING
    NUMBER                       = lv_prnumber
*   PRHEADEREXP                  =
TABLES
    RETURN                       = it_ret
    PRITEM                       = it_pritem
    PRITEMX                      = it_pritemx
*    PRITEMEXP                    = it_pritemexp
*   PRITEMSOURCE                 =
    PRACCOUNT                    = it_praccount
*   PRACCOUNTPROITSEGMENT        =
    PRACCOUNTX                   = it_praccountx
*   PRADDRDELIVERY               =
*   PRITEMTEXT                   =
*   PRHEADERTEXT                 =
*   EXTENSIONIN                  =
*   EXTENSIONOUT                 =
*   PRVERSION                    =
*   PRVERSIONX                   =
*   ALLVERSIONS                  =
*   PRCOMPONENTS                 =
*   PRCOMPONENTSX                =
*   SERVICEOUTLINE               =
*   SERVICEOUTLINEX              =
*   SERVICELINES                 =
*   SERVICELINESX                =
*   SERVICELIMIT                 =
*   SERVICELIMITX                =
*   SERVICECONTRACTLIMITS        =
*   SERVICECONTRACTLIMITSX       =
    SERVICEACCOUNT               = it_ser_acc
    SERVICEACCOUNTX              = it_ser_accx
*   SERVICELONGTEXTS             =
*   SERIALNUMBER                 =
*   SERIALNUMBERX                =
IF sy-subrc eq 0.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
   EXPORTING
     WAIT          = 'X'
   IMPORTING
     RETURN        = lv_return.
endif.

Hi
Now i able to post PR. I DID BELOW CHANGE. I ADDED serrial no.
Ls_acct-SERIAL_NO = '01'.
Ls_acct-COSTCENTER = gs_psdata-kostl.
Ls_acct-WBS_ELEMENT = gs_psdata-wbs_element.
append ls_acct to lt_acct.
Ls_acctx-SERIAL_NO = '01'.
Ls_acctx-COSTCENTER = GC_X.
Ls_acctX-WBS_ELEMENT = GC_X.
append ls_acctx to lt_acctx.
But second issue i am facing
i am using item category 'L' subcontracting
i am trying to replace existing BOM with new material USING BELOW LOGIC.
LS_COMP-MATERIAL = gs_psdata-COMP_MATNR. " Ne material act as component of product
LS_COMP-PLANT = gs_psdata-werks.
LS_COMP-CHANGE_ID = 'I'. "gc_value_r.
LS_COMP-ENTRY_QUANTITY = gs_psdata-QUANTITY.
APPEND LS_COMP TO LT_COMP.
CLEAR LS_COMP.
*LS_COMPx-PREQ_ITEM = '00010'.
LS_COMPX-MATERIAL = GC_X.
LS_COMPx-PLANT = gc_x.
LS_COMPX-CHANGE_ID = GC_X.
LS_COMPX-ENTRY_QUANTITY = GC_X.
APPEND LS_COMPX TO LT_COMPX.
CLEAR LS_COMPX.
But i observed that old BOM is pulled into PR. and not appeared my material added in above logic.
Any advise.
Regards
Ramakrishnaiah Y

Valuation Price error in Scheduling Agreement

Hello Experts,
I am getting inflated valuation while doing MIGO for delivery schedule.
It always comes as more than price of material in scheduling agreement and varies from 1.5 times to 4 times.
Example
Material Moving Average price: 3
stock : 0
Purchase price: 3.05
QTY RECEIVED 100
Value of goods at the time of MIGO has 4.27 price
I can give few more data
Pr. Date Cat: 5
Condition type is not group condition
Moving average price changes to 4.27.
This moving average price comes down to 3.05 once I do MIRO. But my , point is, why we getting inflated valuation at the time of GR.
Please let me know if anybody has come across such issue
Thanks and Regards
Gyanesh Kumar Jha

Allen
please check the details
Mater stock zero at the time of creation
mov avg price 1 at the time of creation
val class: 3000, price control V,
scheduling agreement net price: 1.28(1.5 with tax)
mat doc              mat no          mvt    date                qty   unit   value       Sch Agmt       item no
5000002301     409031796     103     15.03.2011     100     EA     0.00             7500000075     1
5000002302     409031796     105     15.03.2011     100     EA     256.41     7500000075     1
Let me know if you can find any details out of this.
Thanks and Regards
Gyanesh Kumar Jha

BAPI_PR_CREATE Valuation Price

Hi experts,
I need to create a Purchase Requisition using BAPI_PR_CREATE but I received an error 'Enter Valuation Price' when run this BAPI.
I checked ME51N to create a PR manually and I found that I need to enter a Valuation Price manually. But it seems that there is NOT an input parameter for this field in BAPI.
How can I use this BAPI without Valuation Price. Could you please help me?
Thanks.

Dear Kebab,
Please check if you fill in below structure in the BAPI.
pritem-preq_price
pritem-currency
pritem-price_unit
pritemx-preq_price
pritemx-currency
pritemx-price_unit
Best Regards,
Ian Wong Loke Foong

How to create PR without valuation price.

Hi Gurus,
My scenario is to create a PR for spare part repair.
It is without valuation price because the spare part is within the warranty term.
So I only create a PR without price.
T-code:ME51N
Valuation price field is set into optional, Yes,it is presented as an optional field in ME51N screen.
But a error message ME083 "Enter valuation price" still rises if valuation price is not entered.
I also registered the messge ME083 into Warning in IMG message definition.
But it did not work.
Anyone could give some suggestion about it?

Thanks very much for a lot.
I solved it.
My answer is:
(1)check field selection of purchase requisition through the following path
     IMG.materials management.purchasing.purchase requistion.define screen layout at document level
     and then,you will find the first field selection option is $$$$ with description Without price .
     OK, It's my want.
(2)New a document type for purchase requisition and specify the field selection $$$$ .
(3)Save it ,Now it's OK.
Although some good suggestions are provided,I am sure the above answer is the simplest among all suggestions as its least operation and its least infection to actual job of purchase requistion creation.

Purchase requisition -Valuation price and Quantity greyed out

Hi,
I created purchase requsition with Release strategy, once i have enter Valuation price and quantity and check the document Release strategy Invoked.
And Valuation ,quantity fields greyed out before saving the requisition.
Please help me.
Regards,
Sridhart

Why are you entering the Valuation price in PR creation.
If a material master record exists for the requested material, the price is automatically taken from the valuation price field.
If no material master record exists, you must enter a price when creating the purchase requisition.
Please elaborate in detail.

Valuation Price can be entered upto 99,99,99,999.00 INR only in PR Creation

Dear Team,
One of our end user, is trying to create material PR with single line item, whose valuation price to be entered is around 152 Crore.
But system is not allowing the same. It is giving error 00 089: Entry too long.
As per the system, a maximum valuation price of the material can be entered upto 99,99,99,999.00 INR only. There isn't any provision to enter value more than the value mentioned above in PR creation under "Valuation Price" field.
Any help in this regard, will be highly appreciated.
Thanks & Regards,
MP

Hi,
The system will not take more than the specified character in price field. So better option is to use the alternative unit of measure for purchasing of material (Purchasing Unit) .Use alternative unit as Order unit (Purchasing Unit) in MMR(MM02) & Maintaion conversion factor.
Regards,
Biju K

How can we enter value more than 99 crores in valuation price field in PR

we want to fill value more than 99 crores in valuation price while making a purchase requisition in sap.
we are not able to do that
we are getting error
entry too long (enter in the format ,,,~.)
how can we configure to get more than 9 digits in a value field in sap
is this the right forum to post this question
Edited by: ca sanjeev mehndiratta on Jan 6, 2010 6:14 AM

Hi,
you can't enter more then 9 digits. This field is using a domain WERT11 which has format 9.2. You could try to modify SAP standard and add some additional digits for this field but this is very risky thing.
Cheers

Price error while entering Service Entry sheet.

>HI All,
>the scenario is like this :-
>We have enter uncoded services in the Services Tab of item details and have entered qty and gross price alongwith wbs element. There are about 63 lines ltems, while selecting the first only three are getting selected correctly the line items 04 to 08 are giving the following error. The line items 09 to 63 are also giving no error. But the below said error is coming for line item no. 03 to 08.
Enter a price.
When we try to enter a price it does not accept.
and gives an error message SE316.
Enter a price
Message no. SE316
The functionality requires that a price must be entered for service lines in purchase orders and service entry sheets.
If you have to enter a line with the price "0", you can mark the line as an informatory line.
We try to sent the price in the column but it is not accepting the price.
What could be the solution to this error.

Hi,
Take help of FI Consultant and write a Substitution in GGB1.

Error in entry sheet creation - SE134 (enter a price)

Hi,
I run CATM tcode and have encountered error which is to enter a price. I have debugged the calling program of the transaction and it uses MS_CREATE_SERVICE_ENTRY_MULTI function module to create the entry sheet. This FM returns error SE134. Can someone knows what caused this error?
ESSL structure which is being passed to the FM has a dummy in the first line and not sure if this has something to do with the error.
We have checked this also to the functional resource and they were able to create entry sheet manually.
Please help.
Thanks so much in advance!

Hi
Could you please check if Message SE 363 is set as an E (Error) in the IMG transaction OME0?. If it is set to an error you will not be able to accept service overdeliveries even if you have the unlimited indicator set.
Regards,
Mauro

Error shows " enter valuation type in field batch"

Hi,
i transfer material from one plant to another plant using t-code mb1b by 311 mov.type ,
Error shows " enter valuation type in field batch",
what value i have to give in batch field and how to resolve this..

Hi
311 represents--storage location to storage location. and it is not from plant to plant. please check it.
regards
ram

Error during PO Change-"Enter the price or set the 'Invoice Expected' indic

Hi Gurus,
I am facing this issue in the PO change. Whenever I try to change a PO and check ; system says" No error" but when I order it then I get this error "Enter the price or set the 'Invoice Expected' indicator " with a pop up "Complete Purchase order xxxx first or 'hold' the changes
This happens for all the POs with any vendor.
Regards
Kapil

Hi Kapil,
We have got similar issue before while changing the P.O in change mode.
This generally happens when the P.O is changed after the follow on documents has been created.
In this case you can delete the change version and then amend the P.O without any issue.
Generally the 'Delete' button gets disabled once the follow on documents get created but in this case the 'Delete' button would be active and clicking on 'Delete' button would delete only Chnage version and the P.O would be back to original ordered status.
Please do the changes and let me know in case of any further clarifications.
Regards,
Teja

BAPI_ENTRYSHEET_CREATE : Error message SE134 - please enter a price

Hi All,
I try to use this bapi to upload my Service Entry Sheet with given data.
However, I encountered the above error message ' Please enter a price '.
I've checked that i passed in the GR_PRICE value and all the required parameters (ENTRYSHEETACCOUNTASSIGNMENT, ENTRYSHEETSERVICES ENTRYSHEETSRVACCASSVALUES, HEADER) too.
Does anyone encounter this problem?
Hope to hear from you soon.
Thank you.
From,
SW

Hi,
Thank you for your suggestion. The notes was alreay implemented earlier.
i've found out the reason.... this is because, i passed in some value to entrysheetservices-pln_pckg and entrysheetservices-pln_line. it supposed to be set ast '00000000'.
Regards,
sw

Bapi_PR_Create - Enter valuation price error

Similar Messages

Maybe you are looking for