Pricing not possible for line Item

hi
I am facing the follwong error because of which I am nto able to go to change mode . can you guys please suggest what could be the solution?
Pricing not allowed for item 000020 (Split 0001)
Message no. /DBM/PRICING004
Pricing is not allowed for the specified item. (Split 0001)
regarsd

Hi,
The note 1040320 may be relevant for the issue that you are facing.
Symptom: The pricing relevant partner role gets changed to an partner with a
different currency. Now the currency of the header (/DBM/VBAK_COM-WAERK)
and/or splitheader (/DBM/SPLHDR-WAERK) gets updated but not the currency
on item level and on split item level (only for DBM600).
The creation of warranty difference splits is not possible, because
pricing changes are not allowed.
Just take a look.
Regards,
Sandeep

Similar Messages

GR of Delivery completed item not possible for line item of PO/SA ?

Hi,
Am unable to Receive Goods in MIGO an Error - "GR of delivery completed item not possible for line item of PO/SA"?
Regards
Mohammed Khaja Pasha
+919550917395.

Hi Mohammed Khaja Pasha ;
Delivery Completed checkbox provides a lot of fonctionality like an additional delivery is not expected, but is possible. If you prevent posting of migo , you can benefit from system messages M7 163 and 254.
You want to ensure that the delivery is made before the planned delivery date : Set message 254.
You want to ensure last possible delivery date : Set message 163.
However ;
The open PO quantity of the PO item equals zero.
The PO item is no longer relevant for materials planning.
The PO item is ignored when letters urging delivery of overdue goods are generated.
The PO item can be deleted and archived.
You can specify whether the Delivery Completed checkbox is to be selected automatically.
Regards.
M.Ozgur Unal

Pricing at time of goods receipt not possible for this item

We're receiving error Message no. 06634 Pricing at time of goods receipt not possible for this item when trying to change the PO Pricing Date Category from No Control to 5 GR Date.
The error message is clear and reads:
Pricing at time of goods receipt not possible for this item
Message no. 06634
Diagnosis
For this purchasing document item, you wish to specify that a new price determination process is to be carried out at the time of goods receipt.
System Response
Pricing cannot be carried out for the item at the time of goods receipt because the price was either entered manually or copied from the last purchasing document.
The scenario is that we have a contract reference on a PO and the contract condition records are to be maintained as a new price is valid each day. The problem without this is that the new pricing will not be reflected in the GR.
What is the solution to overcome this issue?
NOTE: the Info Record conditions are not being read during GR as the PO references a contract.

For further clarification the PO is referencing a contract and as such not pulling the pricing information from the info record and instead pulling the price from the conditions on the contract.
I want to change the pricing date category from " No Control" to "5 GR Date" however I'm receiving the error message stated and unsure of how to make this change.
The intent is not to create a new PO each day the condition record is created and instead we are utilizing one PO referencing one contract with multiple date delimited condition records containing the daily pricing.

'BAPI_PO_CREATE1' Multiple account assignment is not possible for AFS item

'BAPI_PO_CREATE1' -> This BAPI works perfectly without the 'account assignment' option . But for purchase requisitions which have account assignments BAPI returns the error - E|8W |185   |Multiple account assignment is not possible for AFS items.
Can somebody please help me to get this error resoleve .
My coding I have done like below.
DATA: pohead TYPE bapimepoheader.
DATA: poheadx TYPE bapimepoheaderx.
CONSTANTS : c_x VALUE 'X'.
DATA: exp_head TYPE bapimepoheader.
DATA: return TYPE TABLE OF bapiret2 WITH HEADER LINE.
DATA: poitem TYPE TABLE OF bapimepoitem WITH HEADER LINE.
DATA: poitemx TYPE TABLE OF bapimepoitemx WITH HEADER LINE.
DATA: posched TYPE TABLE OF bapimeposchedule WITH HEADER LINE.
DATA: poschedx TYPE TABLE OF bapimeposchedulx WITH HEADER LINE.
DATA: POACCOUNT TYPE TABLE OF BAPIMEPOACCOUNT WITH HEADER LINE.
DATA: POACCOUNTX TYPE TABLE OF BAPIMEPOACCOUNTx WITH HEADER LINE.
pohead-comp_code = '1000'.   "IEQ1 plant. "'1000'.
pohead-doc_type   = 'NB'     .
pohead-creat_date = sy-datum   .
pohead-vendor = EKKO-LIFNR. "'0000500004'.
pohead-purch_org = purch_org.
pohead-pur_group = purch_grp.
pohead-langu      = sy-langu   .
pohead-doc_date   = sy-datum.
poheadx-comp_code = c_x.
poheadx-doc_type   = c_x.
poheadx-creat_date = c_x.
poheadx-vendor     = c_x.
poheadx-langu      = c_x.
poheadx-purch_org = c_x.
poheadx-pur_group = c_x.
poheadx-doc_date   = c_x.
poitem-po_item    = iLineItem.      "1.
poitem-material   = req_item-MATERIAL.   " '000000000040000234'.
poitem-plant      = req_item-PLANT.
poitem-quantity   = req_item-QUANTITY.
poitem-net_price = NET_PRICE.
poitem-price_unit = PRICE_UNIT.
poitem-shipping   = 'Z1'.
poitem-preq_no    = req_item-PREQ_NO.
poitem-preq_item = req_item-PREQ_ITEM.
poitem-acctasscat = 'K'.
APPEND poitem.
poitemx-po_item    = iLineItem. "1.
poitemx-po_itemx   = c_x.
poitemx-material   = c_x.
poitemx-plant      = c_x .
poitemx-quantity   = c_x .
poitemx-tax_code   = c_x .
poitemx-item_cat   = c_x .
poitemx-acctasscat = c_x .
poitemx-net_price = c_x.
poitemx-price_unit = c_x.
poitemx-shipping   = c_x.
poitemx-preq_no    = c_x.
poitemx-preq_item = c_x.
poitemx-acctasscat = c_x.
APPEND poitemx.
POACCOUNT-PO_ITEM = iLineItem.
POACCOUNT-SERIAL_NO = iLineItem.
POACCOUNT-GL_ACCOUNT = '0000211010'.
POACCOUNT-SD_DOC = '0001001056'.
POACCOUNT-ITM_NUMBER = '000100'.
POACCOUNT-CO_AREA = '1000'.
APPEND POACCOUNT.
POACCOUNTX-PO_ITEM = '00001'.
POACCOUNTX-SERIAL_NO = '01'." '01'.
POACCOUNTX-PO_ITEMX = 'X'.
POACCOUNTX-SERIAL_NOX = 'X'.
POACCOUNTX-GL_ACCOUNT = 'X'.
POACCOUNTX-SD_DOC = 'X'.
POACCOUNTX-ITM_NUMBER = 'X'.
APPEND POACCOUNTX.
CALL FUNCTION 'BAPI_PO_CREATE1'
    EXPORTING
      poheader = pohead
      poheaderx = poheadx
    IMPORTING
    exppurchaseorder = ex_po_number
    expheader        = exp_head
    TABLES
      return    = return
      poitem    = poitem
      poitemx   = poitemx
      POACCOUNT = POACCOUNT
      POACCOUNTX = POACCOUNTX.

I found the answer

Business area not determined for line item?

Hello All,
I am trying to create a sales order. When I enter a line item and enter plant for the item, it gives me an error "Business area not determined for the line item #" and it does not accept the item.
I have already checked in the enterprise structure in IMG that the business area is defined and assigned for this plant.
Is there anything else need to be done? Do we have to define or assign the business area in material master?
I would appreciate if somebody can answer.
Thanks.

There are three rules for determining a business area:
o   Rule 1: plant and division
o   Rule 2: for each sales area
o   Rule 3: for each plant and item division
See what you are missing

Error M8-688 - Creation of several vendor line items is not possible for document type RN.

Hello All,
We are using the Net Invoice Posting with document type RN(Invoice- Net). We are generating different vendor line items in the accounting document based on the withholding tax codes involved in the invoice posting. When it comes to net invoice posting system is giving an error message M8-688 - Creation of vendor line items is not possible for document type RN. Is there is any way to create multiple vendor items with net invoice posting? Please suggest.
Thanks,
Chandu.

I dont think that there is any way because it is a hardcoded error message.
      IF NOT t003-xnetb IS INITIAL.
        MESSAGE e688 WITH pi_rbkpv-blart.
      ENDIF.
SAP is checking the customizing for net/gross posting per document type in table T003
And if it is set up as net, then it is a hard error.

GL display for inventory account which are not defined as line item display

Hi All,
We have inventory gl accounts which are auto post accounts , these accounts get posted when grn is done. these accounts are not defined as line item display accounts, but if we execute the T code: FS10 we get the gl balance display and not line item display.
Our requirement is that we should be able to view the line item display matching the GL account balance in that GL account.
Can we get the report in MM module line items wise display.
Regards
Prashant P. Zinge

Hello,
You should use RFSEPA01 program via execute SE38 transaction.
This program activate line item for each account. Activation means, this program generate line items to BSIS table. So that after this program running, you can see line items in FBL3N.
Regards,
Burak

Changing the default view for Line Items in an Auction.

Hello All,
We have a version 5 client who is asking for us to change the default view for line items in an auction.
Currently, if you have an auction setup, and you go to the Line Items tab, the default view is the "Basic View". The client would like to change the Default from "basic view" to "price view".
Is there a way to change this default in the system? Can this be configured using query groups? Any information would be helpful.

Hi wood cloud,
This is not possible, bcz there is no VLV for that drop down and we cant set it to the price view.
Thanks,
Ankur Goyal

Adding a characteristics to AR Drill down report for line items

I have raised an OSS note on this, but they deem this to be consulting.
I have an AR drill down report for line items
It calls the structure RFRRD20.
I need to add a value into the characteristics so I can use it in the drill down report.
I have appended the structure, added a value in TKAF for the field, and it still does not show.
Has anybody done something similar?
I am sure this is easy, but only when you know how, so if you know how to do it please can you let me know.
thanks
Mark

Hi Mark
    I am also in the same situation where i need to add two characteristics (invoice date, due date) to the AR drill down reports. I added them to the structure and TKAF table as you did, but still could not get them to the drill down reports (FDI5 or FI1).
   From your posts, i see that SAP's response was that it is not possible to add characteristics to AR drilldown reports? Did they mention any reasons or OSS notes? How did you handle your requirement, were you able to work around?
   Your suggestions would be highly appreciated.
Thanks
Vamsi

Error Handling in table control for line item.

Hi,
Please how to do error handling in table control for line item in bdc,i have used format_message for header but i don't no fill decamps internal tabled and how to do background processing in call transaction.
Thanks

Background processing is not possible using call transaction method.
You can create an executable program which can have CALL TRANSACTION BDC code. And this can be run in background.
What do you exactly mean by Error handling for Items in table control. Can you give some more details.

Shipping Invoice for line item

Hello SAP Gurus,
Shipping invoice only triggers a invoice for the complete order but it is not possible for each line item.
Is it possible to open the item field on shipping invoices?
Please advise.
Regards,
Manoj

Hi PJ,
Thanks for your prompt reply.
Yes ..I mean partial billing for some line item.
I understand that I need to define item catg. for billing relevance to K per your advise but is there any other way to pull some line items to billing without making change item catg ?
Regards,
Manoj

Subtotal for line item in REUSE_ALV_HIERSEQ_LIST_DISPLAY

Hi Abapers,
Is it possible to have subtotal functionality for line item for
REUSE_ALV_HIERSEQ_LIST_DISPLAY.
when i select particular line item and press subtotal button
system displaying information mesage
"Subtotals cannot be calculated using item
characteristics"
Even when i executed standard hie program same message displaying for line item.
please provide any sample code for subtotal for line item .
regards,
Hari priya

just copy the program and execute
*& Report Z_HIERSEQ_REP2                                              *
*& author : ramesh.k                                                                    *
*& title : hierseq list in alv format                                                                    *
REPORT z_hierseq_rep2 MESSAGE-ID zrae.
TYPE-POOLS : slis.
*structure declarations
*structure for likp
TYPES : BEGIN OF ty_likp,
         vbeln TYPE vbeln_vl,
         vkorg TYPE vkorg,
         END OF ty_likp.
*structure for lips
TYPES : BEGIN OF ty_lips,
         vbeln TYPE vbeln_vl,
         posnr TYPE posnr_vl,
         matnr TYPE matnr,
         matkl TYPE matkl,
         ntgew TYPE ntgew_15,
         END OF ty_lips.
*internal table declarations
DATA : t_likp TYPE STANDARD TABLE OF ty_likp INITIAL SIZE 0,
       t_lips TYPE STANDARD TABLE OF ty_lips INITIAL SIZE 0.
DATA : t_fieldcat TYPE slis_t_fieldcat_alv,
       t_sortinfo TYPE slis_t_sortinfo_alv,
       i_events TYPE slis_t_event.
*workareas
DATA : w_likp TYPE ty_likp,
       w_lips TYPE ty_lips,
       w_fieldcat TYPE slis_fieldcat_alv,
       w_keyinfo TYPE slis_keyinfo_alv,
       w_sortinfo TYPE slis_sortinfo_alv,
       W_event TYPE slis_alv_event ,
       sub_text type slis_subtot_text.
*global declarations.
DATA : g_vbeln like likp-vbeln.
*selection-screen declarations
SELECTION-SCREEN BEGIN OF BLOCK blk1 WITH FRAME.
SELECT-OPTIONS : s_vbeln FOR g_vbeln.
SELECTION-SCREEN END OF BLOCK blk1.
AT SELECTION-SCREEN.
SELECT SINGLE
         vbeln
         FROM likp
         INTO (w_likp-vbeln)
         WHERE vbeln IN s_vbeln.
IF sy-subrc NE 0.
    MESSAGE i001 WITH 'vbeln not found'.
ENDIF.
START-OF-SELECTION.
get_data_likp
PERFORM sub_getdata_likp.
get_data_lips
PERFORM sub_getdata_lips.
fieldcatlog_build
PERFORM build_fieldcatlog.
*SORTINFO FOR SUBTOTALS
PERFORM get_sortinfo.
*KEYINFORMATION
PERFORM get_keyinfo.
*LIST DISPLAY
PERFORM alv_list_display.
*&      Form sub_getdata_likp
    extracting the data from likp.
--> p1        text
<-- p2        text
FORM sub_getdata_likp .
SELECT vbeln
         vkorg
         FROM likp
         INTO TABLE t_likp
         WHERE vbeln IN s_vbeln.
ENDFORM.                    " sub_getdata_likp
*&      Form sub_getdata_lips
   extracting data from lips.
--> p1        text
<-- p2        text
FORM sub_getdata_lips .
SELECT vbeln
         posnr
         matnr
         matkl
         ntgew
         FROM lips
         INTO TABLE t_lips
         FOR ALL ENTRIES IN t_likp
         WHERE vbeln = t_likp-vbeln.
ENDFORM.                    " sub_getdata_lips
*&      Form build_fieldcatlog
      text
--> p1        text
<-- p2        text
FORM build_fieldcatlog .
*FIELDCATLOG FOR HEADER TABLE
PERFORM build_fieldcatlog1 USING :
                 '1' 'VBELN' 'DELIVERY NO' 'T_LIKP' ' ' ' ' ' ',
                 '2' 'VKORG' 'GROUP'       'T_LIKP' ' ' ' ' ' ',
*FIELDCATLOAG FOR ITEM TABLE
                 '1' 'POSNR' 'ITEM NO' 'T_LIPS' ' ' ' ' ' ',
                 '2' 'MATNR' 'MAT NO' 'T_LIPS' ' ' ' ' ' ',
                 '3' 'MATKL' 'GROUP'   'T_LIPS' ' ' ' ' ' ',
                 '4' 'NTGEW' 'QUAN'    'T_LIPS' 'X' 'X' 'X'.
ENDFORM.                    " build_fieldcatlog
*&      Form build_fieldcatlog1
      text
     -->P_0185   text
     -->P_0186   text
     -->P_0187   text
     -->P_0188   text
FORM build_fieldcatlog1 USING
                              pcol     TYPE char2
                              pfldname TYPE char8
                              pseltext TYPE char20
                              ptabname TYPE char10
                              psum     TYPE char10
                              PQUAN    TYPE CHAR15
                              PSUBTOTAL TYPE CHAR40.
w_fieldcat-col_pos = pcol.
w_fieldcat-fieldname = pfldname.
w_fieldcat-seltext_m = pseltext.
w_fieldcat-tabname = ptabname.
w_fieldcat-do_sum = psum.
W_FIELDCAT-qfieldname = PQUAN.
W_FIELDCAT-subtotals_text = PSUBTOTAL.
APPEND w_fieldcat TO t_fieldcat.
ENDFORM.                    " build_fieldcatlog1
*&      Form GET_KEYINFO
      text
--> p1        text
<-- p2        text
FORM get_keyinfo .
w_keyinfo-header01 = 'VBELN'.
w_keyinfo-item01   = 'VBELN'.
ENDFORM.                    " GET_KEYINFO
*&      Form ALV_LIST_DISPLAY
      text
FORM alv_list_display .
DATA : S_REPID TYPE SY-REPID.
       S_REPID = SY-REPID.
DATA W_LAYOUT TYPE SLIS_LAYOUT_ALV.
W_LAYOUT-totals_text = 'G.TOTAL'.
W_LAYOUT-subtotals_text = 'SUBTOTAL_TEXT'.
*FORM subtotal_text CHANGING p_total TYPE any
                           p_subtot_text TYPE slis_subtot_text.
p_subtot_text-criteria = 'VBELN'.
*p_subtot_text-max_len = 40.
*p_subtot_text-display_text_for_subtotal
*= 'SUBTOTAL'.
**ENDIF.
*ENDFORM.
CALL FUNCTION 'REUSE_ALV_HIERSEQ_LIST_DISPLAY'
    EXPORTING
I_INTERFACE_CHECK              = ' '
     i_callback_program             = S_REPID
I_CALLBACK_PF_STATUS_SET       = ' '
I_CALLBACK_USER_COMMAND        = ' '
   IS_LAYOUT                      = W_LAYOUT
     it_fieldcat                    = t_fieldcat
IT_EXCLUDING                   =
IT_SPECIAL_GROUPS              =
     it_sort                        = t_sortinfo
IT_FILTER                      =
IS_SEL_HIDE                    =
I_SCREEN_START_COLUMN          = 0
I_SCREEN_START_LINE            = 0
I_SCREEN_END_COLUMN            = 0
I_SCREEN_END_LINE              = 0
I_DEFAULT                      = 'X'
   I_SAVE                         = 'X'
IS_VARIANT                     =
   IT_EVENTS                      = i_eventS
IT_EVENT_EXIT                  =
      i_tabname_header               = 'T_LIKP'
      i_tabname_item                 = 'T_LIPS'
I_STRUCTURE_NAME_HEADER        =
I_STRUCTURE_NAME_ITEM          =
      is_keyinfo                     = w_keyinfo
IS_PRINT                       =
IS_REPREP_ID                   =
I_BYPASSING_BUFFER             =
I_BUFFER_ACTIVE                =
IMPORTING
E_EXIT_CAUSED_BY_CALLER        =
ES_EXIT_CAUSED_BY_USER         =
    TABLES
      t_outtab_header                = t_likp
      t_outtab_item                  = t_lips
EXCEPTIONS
PROGRAM_ERROR                  = 1
OTHERS                         = 2
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    " ALV_LIST_DISPLAY
*&      Form GET_SORTINFO
      text
--> p1        text
<-- p2        text
FORM get_sortinfo .
w_sortinfo-fieldname = 'VBELN'.
w_sortinfo-tabname   = 'T_LIKP'.
W_SORTINFO-group     = TEXT-001.
w_sortinfo-subtot    = 'X'.
APPEND w_sortinfo TO t_sortinfo.
ENDFORM.                    " GET_SORTINFO

Header PO discount, not apportioned to line item

Hi MM Gurus
My client wants to create a multi line item PO and also will like to include the header discount (value based). The client does not want the discount to be apportioned to each line item. He wants the line items to be received and paid at its original cost. Can someone suggest if this can be done and how?
Here is the example:
PO with 3 lines
Line one 100 each @ 25 = $2500
Line two 200 eaxh @ 30 = $6000
Line three 150 each @ 10 = $1500
Header discount = $500
Line items still remain at their actual values. The discount is not applied to line items. Upon LIV, the PO line items received at actual price, but the overall discount adjusted.
Any guidance will be appreciated.
Regards,
Vinay

Hi.
I'm not sure if the following info help you.
But how about to set the "Condition is used for
statistics" flag V_T683S-KSTAT?
You can set it in your pricing procedure and
for your condition type.
As far as I know, the header condition is not reflected to
the net price.(Though reflected to the "effective price".)
When GR, GR/IR will be from net price.
Best regards.
Keiichiro

Serialization not possible for material number (SHPCON IDOC error )

Hello,
Can any one shed some light on following inbound PGI IDOC (SHPCON) Error from 3PL.
"Serialization not possible for material number XYZ"
Message no. IO205
Diagnosis
The serial number profile of the material does not allow serialization for the operation you have chosen.
Procedure
Maintain the serial number profile.
Additional info
1) Serial number profile is maintained in the material master
2) Serial number populated in the idoc E1EDL11 is not used in any delivery or assigned and it is valid serial number and has equipment master record
3) If i use the same serial number from the IDOC and post PGI manually via VL02N , I am able to post the PGI without any problems and I don;t get the above error
4) IDOC has all the info required , Delivery number,Valid material # , qty,UOM and Line item number of the delivery .
Thanks in advance for your help
GJ

Dear Jalwadi
I got exact same problem. How did you solve it?

No control line for line item - error while posting bd to accounting

Hi all,
Billing document showing err "no control line for line item" while posting to accounting doc.Sales document is complete no in completion logs.
Previous errr: g/l missing for line item" in order incompletion after maintaining company code for customer, then refresh the g/l missing for line item is no more logs and showing the error "no control line for line item" while posting bd to accts.
Please help
Regards
anush

Hello Anush,
if the company data of the payer was not created when the sales order has been created, then the system could not create the correct records in table VBREVK. Once the company data has been maintained the VBREVK records could be corrected by re-saving the sales, but only if no billing document exists.
In your case you already created the billing document.
Please try these step:
1. reverse billing document
2. run VA02 add a blank char to PO number, save
3. create new billing document
Best regards,
Ivano.

Pricing not possible for line Item

Similar Messages

Maybe you are looking for