GR/IR Posting Error CKMLGRIR025 - Purchase Order History Inconsistent
Hi Everyone.
We currently have a posting in our GRIR for a Feright Condition Value against a Purchase Order which gets the above error when trying to post in MR11.
The Diagnosis of the error reads:
"The purchase order history contains differences between the goods receipt and invoice receipts/Account maintenance for the order item in the field Difference Quantitiy (= 43.804 TO) and Difference Value (= -342.77)
The purchase order history for this tiem is inconsistent"
When looking at this Freight Condition information in the Purchase Order I can not see why this item has resulted in this error in MR11.
Has anyone else seen this error come through in their system, and do you have any ideas on how to fix this.
Thanks
Hayley
We are experiencing the same issue with the GRIR Posting Error CKMLGRIR025 - puchase order history inconsistent. The actual message that we receive is Puchase Order history already inconsistent -->Quantity 1.00 EA Value 0.65-USD.
We reviewed SAP Note 708649 which also recommends using transaction MIRO with the corresponding default quantity and value o. However, we are not able to enter an Invoice for the "default qty & value 0", as SAP gives me error message M8278 "You are not allowed to have zero lines" (just like Haley commented). In reviewing this thread, I did not find the solution to the error message M8278 "You are not allowed to have zero lines" . Could someone help me understand?
Thank you!
Similar Messages
-
Accounting document number display in purchase order history tab
Is it possible to display the accounting document number in the purchase order history tab? Currently it is displaying material document number for Good receipts and LIV (logistic invoice verification) document number for Invoice receipts against material document number colmn. We can get to the accounting document number by drilling into the LIV document number. We are looking for a way to display the accounting document number in the display screen of purchase order history tab instead of drilling down.
Is there an option to display accounting document number of the MIRO posting in ME23N , purchase order history tab?
Truly appreciate any help in this regard.Thanks for the response.
-
Batch specific unit of measure - Purchase order history correction
I have maintained an alternate proportional unit for a material. This alternate unit is used as the order price unit in the purchase order. I have created a batch characteristic which is linked to this proportional unit of measure. I have also created a Master inspection characteristic which is linked to this batch characteristic.
I want to correct the purchase order history using quality management by transaction code MWBQ. However, when I perform transaction MWBQ, the inventory is reduced to zero and entire amount is posted to price difference account after correction. Hence, my inventory value becomes zero after MWBQ. I cannot maintain the proportional unit at standard price since this is a raw material. Need a solution on how to post correction in purchase order history without actualy making the inventory zero and with moving average price.Thanks for caring!
As for transaction MMBE it all looks fine. So basic definitions must be OK up to that point.
I think the point is to set requirement for the amount of active ingredient.
Do the batch determination for this.
Do the goods issue in physcial quantity which is the base unit of measure.
I did try now with KG in the BOM. I still get double items in the process order. Now both in KG.
One line is correclty copied.
The incorrect line which is the same in both cases says 1 KG. which is the correct conversion from 0,01KAI.
Regards,
Tor -
Purchase order history already inconsistent -- Quantity * * Value**
Hi experts,
Please note that I am trying to reverse a GR/IR account maintanence document.
But it throws the below error for a line item in the PO.
Purchase order history already inconsistent --> Quantity10,000- SET Value 3,96 AED
For this line item actually account maintanence was done on 30.10.09.And then
further GR has been done & IR also has been done.
Please advise in what circumstances system throw this error and how to reverse
the document now.
Regards,
ParthaHi,
Please check if there exists any multiple order units exists for the PO and thier conversion while posting documents.
Regards, -
Error in : Purchase order Creation using BAPI_PO_CREATE1
Hell guys,
I am trying to create a PO using a BAPI - BAPI_PO_CREATE1
I want the new PO to have all the characteristics of an existing PO. whose PO # is stored in wa_order_split_create-docnr and for the new PO, i want the quantity from wa_order_split_create-qty_acptd and the delivery data to be wa_order_split_create-dly_date. But this process and code below gives a short dump in the std FM - MEPO_DOC_ITEM_GET . It raises an exception of failure. I am trying to create many new PO's in the loop below. If there is just one row, sometimes, it creates the PO even with the exception failure ( which is pretty weird).
Am i making any mistake while filling the header or item or schedule lines for the BAPI_PO_CREATE1 ? Any tips or clues why I am getting a dump ?
DATA: i_insert,
i_create_order,
i_cycle TYPE cycle,
i_qty_acpt TYPE dzmeng,
i_dly_date TYPE vbak-vdatu,
i_item TYPE roijnomiio .
DATA: i_order TYPE symsgv,
i_return TYPE swd_return .
DATA: i_vbak TYPE vbak,
i_vbap TYPE vbap,
i_ekko TYPE ekko,
i_ekpo TYPE ekpo,
i_bsoh TYPE bapisdhd1,
i_bsohx TYPE bapisdhd1x,
i_bpoh TYPE bapimepoheader,
i_bpohx TYPE bapimepoheaderx,
i_vbeln TYPE vbeln_va,
i_posnr TYPE posnr_va,
i_contr TYPE vbeln_va,
i_conit TYPE posnr_va,
i_ebeln TYPE ebeln,
i_ebelp TYPE ebelp,
i_pargr TYPE pargr,
i_thead TYPE thead,
i_line TYPE tline,
i_note TYPE txw_note,
i_new_vbeln TYPE vbeln_va,
i_new_ebeln TYPE ebeln,
i_wa_bsoi TYPE bapisditm,
i_wa_bsoix TYPE bapisditmx,
i_wa_bsop TYPE bapiparnr,
i_wa_bsos TYPE bapischdl,
i_wa_bsosx TYPE bapischdlx,
i_wa_vbpa TYPE vbpa,
i_wa_vbkd TYPE vbkd,
i_wa_bpoi TYPE bapimepoitem,
i_wa_bpoix TYPE bapimepoitemx,
i_wa_bpos TYPE bapimeposchedule,
i_wa_bposx TYPE bapimeposchedulx,
i_wa_bpop TYPE bapiekkop,
i_wa_ekpa TYPE ekpa,
i_message TYPE char72,
i_bapiretn TYPE bapiret2,
i_bapiret2 TYPE TABLE OF bapiret2 INITIAL SIZE 1,
i_vbpa TYPE TABLE OF vbpa INITIAL SIZE 1,
i_vbkd TYPE TABLE OF vbkd INITIAL SIZE 1,
i_ekpa TYPE TABLE OF ekpa INITIAL SIZE 1,
i_bsoi TYPE TABLE OF bapisditm INITIAL SIZE 1,
i_bsoix TYPE TABLE OF bapisditmx INITIAL SIZE 1,
i_bsos TYPE TABLE OF bapischdl INITIAL SIZE 1,
i_bsosx TYPE TABLE OF bapischdlx INITIAL SIZE 1,
i_bsop TYPE TABLE OF bapiparnr INITIAL SIZE 1,
i_bpoi TYPE TABLE OF bapimepoitem INITIAL SIZE 1,
i_bpoix TYPE TABLE OF bapimepoitemx INITIAL SIZE 1,
i_bpos TYPE TABLE OF bapimeposchedule INITIAL SIZE 1,
i_bposx TYPE TABLE OF bapimeposchedulx INITIAL SIZE 1,
i_bpop TYPE TABLE OF bapiekkop INITIAL SIZE 1,
i_text_tab TYPE TABLE OF tline INITIAL SIZE 1,
i_line_tab TYPE TABLE OF tline INITIAL SIZE 1,
i_txw_note TYPE TABLE OF txw_note INITIAL SIZE 1,
i_oij_el_doc_mot TYPE oij_el_doc_mot .
CONSTANTS: c_char_c VALUE 'C',
c_char_e VALUE 'E',
c_char_p VALUE 'P',
c_char_g VALUE 'G',
c_char_i VALUE 'I',
c_char_s VALUE 'S',
c_char_x VALUE 'X',
c_zsw(3) VALUE 'ZSW',
c_nomit_stat(4) VALUE 'ZDNY' .
DATA : lv_nomtk_split TYPE oij_nomtk.
DATA : i_order_split_create TYPE TABLE OF zsws_order_split.
DATA : wa_order_split_create TYPE zsws_order_split.
LOOP AT i_order_split_create INTO wa_order_split_create.
IF NOT i_create_order IS INITIAL .
CLEAR: i_create_order .
MOVE: wa_order_split_create-docnr TO i_ebeln,
wa_order_split_create-docitm TO i_ebelp .
CALL FUNCTION 'ME_EKKO_SINGLE_READ'
EXPORTING
pi_ebeln = i_ebeln
IMPORTING
po_ekko = i_ekko
EXCEPTIONS
no_records_found = 1
OTHERS = 2.
IF sy-subrc <> 0 .
ENDIF .
* Fill PO Header
i_bpoh-comp_code = i_ekko-bukrs .
i_bpoh-doc_type = i_ekko-bsart .
i_bpoh-vendor = i_ekko-lifnr .
i_bpoh-langu = i_ekko-spras .
i_bpoh-pmnttrms = i_ekko-zterm .
i_bpoh-purch_org = i_ekko-ekorg .
i_bpoh-pur_group = i_ekko-ekgrp .
i_bpoh-currency = i_ekko-waers .
i_bpoh-agreement = i_ekko-konnr .
i_bpoh-incoterms1 = i_ekko-inco1 .
i_bpoh-incoterms2 = i_ekko-inco2 .
* Fill PO update indicator 'X'
i_bpohx-comp_code = c_char_x .
i_bpohx-doc_type = c_char_x .
i_bpohx-vendor = c_char_x .
i_bpohx-langu = c_char_x .
i_bpohx-pmnttrms = c_char_x .
i_bpohx-purch_org = c_char_x .
i_bpohx-pur_group = c_char_x .
i_bpohx-currency = c_char_x .
i_bpohx-agreement = c_char_x .
i_bpohx-incoterms1 = c_char_x .
i_bpohx-incoterms2 = c_char_x .
CALL FUNCTION 'ME_EKPO_SINGLE_READ'
EXPORTING
pi_ebeln = i_ebeln
pi_ebelp = i_ebelp
IMPORTING
po_ekpo = i_ekpo
EXCEPTIONS
no_records_found = 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 .
* Fill PO Item
i_wa_bpoi-po_item = i_ekpo-ebelp .
i_wa_bpoi-material = i_ekpo-matnr .
i_wa_bpoi-plant = i_ekpo-werks .
i_wa_bpoi-stge_loc = i_ekpo-lgort .
i_wa_bpoi-quantity = wa_order_split_create-qty_acptd .
i_wa_bpoi-po_unit = i_ekpo-meins .
i_wa_bpoi-tax_code = i_ekpo-mwskz .
i_wa_bpoi-val_type = i_ekpo-bwtar .
i_wa_bpoi-item_cat = i_ekpo-pstyp .
i_wa_bpoi-acctasscat = i_ekpo-knttp .
i_wa_bpoi-agreement = i_ekpo-konnr .
i_wa_bpoi-agmt_item = i_ekpo-ktpnr .
APPEND i_wa_bpoi TO i_bpoi .
* Fill PO Item update indicator 'X'
i_wa_bpoix-po_item = i_ekpo-ebelp .
i_wa_bpoix-po_itemx = c_char_x .
i_wa_bpoix-material = c_char_x .
i_wa_bpoix-plant = c_char_x .
i_wa_bpoix-stge_loc = c_char_x .
i_wa_bpoix-quantity = c_char_x .
i_wa_bpoix-po_unit = c_char_x .
i_wa_bpoix-tax_code = c_char_x .
i_wa_bpoix-val_type = c_char_x .
i_wa_bpoix-item_cat = c_char_x .
i_wa_bpoix-acctasscat = c_char_x .
i_wa_bpoix-agreement = c_char_x .
i_wa_bpoix-agmt_item = c_char_x .
APPEND i_wa_bpoix TO i_bpoix .
* Fill PO Item Schedule
i_wa_bpos-po_item = i_ekpo-ebelp .
i_wa_bpos-sched_line = '0001' .
i_wa_bpos-delivery_date = wa_order_split_create-dly_date .
i_wa_bpos-quantity = wa_order_split_create-qty_acptd .
APPEND i_wa_bpos TO i_bpos .
* Fill PO Item schedule update indicator 'X'
i_wa_bposx-po_item = i_ekpo-ebelp .
i_wa_bposx-sched_line = '0001' .
i_wa_bposx-delivery_date = c_char_x .
i_wa_bposx-quantity = c_char_x .
APPEND i_wa_bposx TO i_bposx .
CLEAR: i_pargr .
SELECT SINGLE pargr
INTO i_pargr
FROM t161
WHERE bstyp = i_ekko-bstyp
AND bsart = i_ekko-bsart .
CLEAR i_ekpa[].
CALL FUNCTION 'MM_READ_PARTNERS'
EXPORTING
application = c_char_p
ebeln = i_ebeln
bstyp = i_ekko-bstyp
pargr = i_pargr
TABLES
x_ekpa = i_ekpa[].
LOOP AT i_ekpa INTO i_wa_ekpa .
i_wa_bpop-partnerdesc = i_wa_ekpa-parvw .
i_wa_bpop-langu = sy-langu .
IF NOT i_wa_ekpa-lifn2 IS INITIAL .
i_wa_bpop-buspartno = i_wa_ekpa-lifn2 .
ELSE .
i_wa_bpop-buspartno = i_wa_ekpa-parnr .
ENDIF .
APPEND i_wa_bpop TO i_bpop .
CLEAR: i_wa_ekpa, i_wa_bpop .
ENDLOOP .
CALL FUNCTION 'DIALOG_SET_NO_DIALOG'.
CALL FUNCTION 'BAPI_PO_CREATE1'
EXPORTING
poheader = i_bpoh
poheaderx = i_bpohx
IMPORTING
exppurchaseorder = i_new_ebeln
TABLES
return = i_bapiret2
poitem = i_bpoi[]
poitemx = i_bpoix[]
poschedule = i_bpos[]
poschedulex = i_bposx[].
i_order = i_new_ebeln .
SHIFT i_order LEFT DELETING LEADING '0' .
i_return-errortype = c_char_i .
i_return-workarea = c_zsw .
i_return-message = '064' .
i_return-variable1 = i_order .
loop at i_bapiret2 into i_bapiretn where type ca 'EAX' .
append i_bapiretn to t_bapi_return .
endloop .
if t_bapi_return[] is initial .
i_create_order = c_char_x .
CALL FUNCTION 'SWD_POPUP_MESSAGE_SEND'
EXPORTING
act_return = i_return. "Popup with new PO no.
ENDCASE . " Docind
ENDIF .
ENDLOOP.Hi Shareen,
I think in the following parts of the code,
CALL FUNCTION 'MM_READ_PARTNERS'
EXPORTING
application = c_char_p
ebeln = i_ebeln
bstyp = i_ekko-bstyp
pargr = i_pargr
TABLES
x_ekpa = i_ekpa[].
Error in : Purchase order Creation using BAPI_PO_CREATE1
Posted: Mar 20, 2006 7:39 PM Reply E-mail this post
Hell guys,
I am trying to create a PO using a BAPI - BAPI_PO_CREATE1
I want the new PO to have all the characteristics of an existing PO. whose PO # is stored in wa_order_split_create-docnr and for the new PO, i want the quantity from wa_order_split_create-qty_acptd and the delivery data to be wa_order_split_create-dly_date. But this process and code below gives a short dump in the std FM - MEPO_DOC_ITEM_GET . It raises an exception of failure. I am trying to create many new PO's in the loop below. If there is just one row, sometimes, it creates the PO even with the exception failure ( which is pretty weird).
Am i making any mistake while filling the header or item or schedule lines for the BAPI_PO_CREATE1 ? Any tips or clues why I am getting a dump ?
DATA: i_insert,
i_create_order,
i_cycle TYPE cycle,
i_qty_acpt TYPE dzmeng,
i_dly_date TYPE vbak-vdatu,
i_item TYPE roijnomiio .
DATA: i_order TYPE symsgv,
i_return TYPE swd_return .
DATA: i_vbak TYPE vbak,
i_vbap TYPE vbap,
i_ekko TYPE ekko,
i_ekpo TYPE ekpo,
i_bsoh TYPE bapisdhd1,
i_bsohx TYPE bapisdhd1x,
i_bpoh TYPE bapimepoheader,
i_bpohx TYPE bapimepoheaderx,
i_vbeln TYPE vbeln_va,
i_posnr TYPE posnr_va,
i_contr TYPE vbeln_va,
i_conit TYPE posnr_va,
i_ebeln TYPE ebeln,
i_ebelp TYPE ebelp,
i_pargr TYPE pargr,
i_thead TYPE thead,
i_line TYPE tline,
i_note TYPE txw_note,
i_new_vbeln TYPE vbeln_va,
i_new_ebeln TYPE ebeln,
i_wa_bsoi TYPE bapisditm,
i_wa_bsoix TYPE bapisditmx,
i_wa_bsop TYPE bapiparnr,
i_wa_bsos TYPE bapischdl,
i_wa_bsosx TYPE bapischdlx,
i_wa_vbpa TYPE vbpa,
i_wa_vbkd TYPE vbkd,
i_wa_bpoi TYPE bapimepoitem,
i_wa_bpoix TYPE bapimepoitemx,
i_wa_bpos TYPE bapimeposchedule,
i_wa_bposx TYPE bapimeposchedulx,
i_wa_bpop TYPE bapiekkop,
i_wa_ekpa TYPE ekpa,
i_message TYPE char72,
i_bapiretn TYPE bapiret2,
i_bapiret2 TYPE TABLE OF bapiret2 INITIAL SIZE 1,
i_vbpa TYPE TABLE OF vbpa INITIAL SIZE 1,
i_vbkd TYPE TABLE OF vbkd INITIAL SIZE 1,
i_ekpa TYPE TABLE OF ekpa INITIAL SIZE 1,
i_bsoi TYPE TABLE OF bapisditm INITIAL SIZE 1,
i_bsoix TYPE TABLE OF bapisditmx INITIAL SIZE 1,
i_bsos TYPE TABLE OF bapischdl INITIAL SIZE 1,
i_bsosx TYPE TABLE OF bapischdlx INITIAL SIZE 1,
i_bsop TYPE TABLE OF bapiparnr INITIAL SIZE 1,
i_bpoi TYPE TABLE OF bapimepoitem INITIAL SIZE 1,
i_bpoix TYPE TABLE OF bapimepoitemx INITIAL SIZE 1,
i_bpos TYPE TABLE OF bapimeposchedule INITIAL SIZE 1,
i_bposx TYPE TABLE OF bapimeposchedulx INITIAL SIZE 1,
i_bpop TYPE TABLE OF bapiekkop INITIAL SIZE 1,
i_text_tab TYPE TABLE OF tline INITIAL SIZE 1,
i_line_tab TYPE TABLE OF tline INITIAL SIZE 1,
i_txw_note TYPE TABLE OF txw_note INITIAL SIZE 1,
i_oij_el_doc_mot TYPE oij_el_doc_mot .
CONSTANTS: c_char_c VALUE 'C',
c_char_e VALUE 'E',
c_char_p VALUE 'P',
c_char_g VALUE 'G',
c_char_i VALUE 'I',
c_char_s VALUE 'S',
c_char_x VALUE 'X',
c_zsw(3) VALUE 'ZSW',
c_nomit_stat(4) VALUE 'ZDNY' .
DATA : lv_nomtk_split TYPE oij_nomtk.
DATA : i_order_split_create TYPE TABLE OF zsws_order_split.
DATA : wa_order_split_create TYPE zsws_order_split.
LOOP AT i_order_split_create INTO wa_order_split_create.
IF NOT i_create_order IS INITIAL .
CLEAR: i_create_order .
MOVE: wa_order_split_create-docnr TO i_ebeln,
wa_order_split_create-docitm TO i_ebelp .
CALL FUNCTION 'ME_EKKO_SINGLE_READ'
EXPORTING
pi_ebeln = i_ebeln
IMPORTING
po_ekko = i_ekko
EXCEPTIONS
no_records_found = 1
OTHERS = 2.
IF sy-subrc <> 0 .
ENDIF .
Fill PO Header
i_bpoh-comp_code = i_ekko-bukrs .
i_bpoh-doc_type = i_ekko-bsart .
i_bpoh-vendor = i_ekko-lifnr .
i_bpoh-langu = i_ekko-spras .
i_bpoh-pmnttrms = i_ekko-zterm .
i_bpoh-purch_org = i_ekko-ekorg .
i_bpoh-pur_group = i_ekko-ekgrp .
i_bpoh-currency = i_ekko-waers .
i_bpoh-agreement = i_ekko-konnr .
i_bpoh-incoterms1 = i_ekko-inco1 .
i_bpoh-incoterms2 = i_ekko-inco2 .
Fill PO update indicator 'X'
i_bpohx-comp_code = c_char_x .
i_bpohx-doc_type = c_char_x .
i_bpohx-vendor = c_char_x .
i_bpohx-langu = c_char_x .
i_bpohx-pmnttrms = c_char_x .
i_bpohx-purch_org = c_char_x .
i_bpohx-pur_group = c_char_x .
i_bpohx-currency = c_char_x .
i_bpohx-agreement = c_char_x .
i_bpohx-incoterms1 = c_char_x .
i_bpohx-incoterms2 = c_char_x .
CALL FUNCTION 'ME_EKPO_SINGLE_READ'
EXPORTING
pi_ebeln = i_ebeln
pi_ebelp = i_ebelp
IMPORTING
po_ekpo = i_ekpo
EXCEPTIONS
no_records_found = 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 .
Fill PO Item
i_wa_bpoi-po_item = i_ekpo-ebelp .
i_wa_bpoi-material = i_ekpo-matnr .
i_wa_bpoi-plant = i_ekpo-werks .
i_wa_bpoi-stge_loc = i_ekpo-lgort .
i_wa_bpoi-quantity = wa_order_split_create-qty_acptd .
i_wa_bpoi-po_unit = i_ekpo-meins .
i_wa_bpoi-tax_code = i_ekpo-mwskz .
i_wa_bpoi-val_type = i_ekpo-bwtar .
i_wa_bpoi-item_cat = i_ekpo-pstyp .
i_wa_bpoi-acctasscat = i_ekpo-knttp .
i_wa_bpoi-agreement = i_ekpo-konnr .
i_wa_bpoi-agmt_item = i_ekpo-ktpnr .
APPEND i_wa_bpoi TO i_bpoi .
Fill PO Item update indicator 'X'
i_wa_bpoix-po_item = i_ekpo-ebelp .
i_wa_bpoix-po_itemx = c_char_x .
i_wa_bpoix-material = c_char_x .
i_wa_bpoix-plant = c_char_x .
i_wa_bpoix-stge_loc = c_char_x .
i_wa_bpoix-quantity = c_char_x .
i_wa_bpoix-po_unit = c_char_x .
i_wa_bpoix-tax_code = c_char_x .
i_wa_bpoix-val_type = c_char_x .
i_wa_bpoix-item_cat = c_char_x .
i_wa_bpoix-acctasscat = c_char_x .
i_wa_bpoix-agreement = c_char_x .
i_wa_bpoix-agmt_item = c_char_x .
APPEND i_wa_bpoix TO i_bpoix .
Fill PO Item Schedule
i_wa_bpos-po_item = i_ekpo-ebelp .
i_wa_bpos-sched_line = '0001' .
i_wa_bpos-delivery_date = wa_order_split_create-dly_date .
i_wa_bpos-quantity = wa_order_split_create-qty_acptd .
APPEND i_wa_bpos TO i_bpos .
Fill PO Item schedule update indicator 'X'
i_wa_bposx-po_item = i_ekpo-ebelp .
i_wa_bposx-sched_line = '0001' .
i_wa_bposx-delivery_date = c_char_x .
i_wa_bposx-quantity = c_char_x .
APPEND i_wa_bposx TO i_bposx .
CLEAR: i_pargr .
SELECT SINGLE pargr
INTO i_pargr
FROM t161
WHERE bstyp = i_ekko-bstyp
AND bsart = i_ekko-bsart .
CLEAR i_ekpa[].
CALL FUNCTION 'MM_READ_PARTNERS'
EXPORTING
application = c_char_p
ebeln = i_ebeln
bstyp = i_ekko-bstyp
pargr = i_pargr
TABLES
x_ekpa = <b>i_ekpa[].</b>
LOOP AT i_ekpa INTO i_wa_ekpa .
i_wa_bpop-partnerdesc = i_wa_ekpa-parvw .
i_wa_bpop-langu = sy-langu .
IF NOT i_wa_ekpa-lifn2 IS INITIAL .
i_wa_bpop-buspartno = i_wa_ekpa-lifn2 .
ELSE .
i_wa_bpop-buspartno = i_wa_ekpa-parnr .
ENDIF .
APPEND i_wa_bpop TO i_bpop .
CLEAR: i_wa_ekpa, i_wa_bpop .
ENDLOOP .
CALL FUNCTION 'DIALOG_SET_NO_DIALOG'.
CALL FUNCTION 'BAPI_PO_CREATE1'
EXPORTING
poheader = i_bpoh
poheaderx = i_bpohx
IMPORTING
exppurchaseorder = i_new_ebeln
TABLES
return = i_bapiret2
<b> poitem = i_bpoi[]
poitemx = i_bpoix[]
poschedule = i_bpos[]
poschedulex = i_bposx[].</b>
it should be only i_bpoi, i_bpoix, i_bpos, i_bposx but not i_bpoi[], i_bpoix[], i_bpos[], i_bposx[].
CHange the code as follows:
DATA: i_insert,
i_create_order,
i_cycle TYPE cycle,
i_qty_acpt TYPE dzmeng,
i_dly_date TYPE vbak-vdatu,
i_item TYPE roijnomiio .
DATA: i_order TYPE symsgv,
i_return TYPE swd_return .
DATA: i_vbak TYPE vbak,
i_vbap TYPE vbap,
i_ekko TYPE ekko,
i_ekpo TYPE ekpo,
i_bsoh TYPE bapisdhd1,
i_bsohx TYPE bapisdhd1x,
i_bpoh TYPE bapimepoheader,
i_bpohx TYPE bapimepoheaderx,
i_vbeln TYPE vbeln_va,
i_posnr TYPE posnr_va,
i_contr TYPE vbeln_va,
i_conit TYPE posnr_va,
i_ebeln TYPE ebeln,
i_ebelp TYPE ebelp,
i_pargr TYPE pargr,
i_thead TYPE thead,
i_line TYPE tline,
i_note TYPE txw_note,
i_new_vbeln TYPE vbeln_va,
i_new_ebeln TYPE ebeln,
i_wa_bsoi TYPE bapisditm,
i_wa_bsoix TYPE bapisditmx,
i_wa_bsop TYPE bapiparnr,
i_wa_bsos TYPE bapischdl,
i_wa_bsosx TYPE bapischdlx,
i_wa_vbpa TYPE vbpa,
i_wa_vbkd TYPE vbkd,
i_wa_bpoi TYPE bapimepoitem,
i_wa_bpoix TYPE bapimepoitemx,
i_wa_bpos TYPE bapimeposchedule,
i_wa_bposx TYPE bapimeposchedulx,
i_wa_bpop TYPE bapiekkop,
i_wa_ekpa TYPE ekpa,
i_message TYPE char72,
i_bapiretn TYPE bapiret2,
i_bapiret2 TYPE TABLE OF bapiret2 INITIAL SIZE 1,
i_vbpa TYPE TABLE OF vbpa INITIAL SIZE 1,
i_vbkd TYPE TABLE OF vbkd INITIAL SIZE 1,
i_ekpa TYPE TABLE OF ekpa INITIAL SIZE 1,
i_bsoi TYPE TABLE OF bapisditm INITIAL SIZE 1,
i_bsoix TYPE TABLE OF bapisditmx INITIAL SIZE 1,
i_bsos TYPE TABLE OF bapischdl INITIAL SIZE 1,
i_bsosx TYPE TABLE OF bapischdlx INITIAL SIZE 1,
i_bsop TYPE TABLE OF bapiparnr INITIAL SIZE 1,
i_bpoi TYPE TABLE OF bapimepoitem INITIAL SIZE 1,
i_bpoix TYPE TABLE OF bapimepoitemx INITIAL SIZE 1,
i_bpos TYPE TABLE OF bapimeposchedule INITIAL SIZE 1,
i_bposx TYPE TABLE OF bapimeposchedulx INITIAL SIZE 1,
i_bpop TYPE TABLE OF bapiekkop INITIAL SIZE 1,
i_text_tab TYPE TABLE OF tline INITIAL SIZE 1,
i_line_tab TYPE TABLE OF tline INITIAL SIZE 1,
i_txw_note TYPE TABLE OF txw_note INITIAL SIZE 1,
i_oij_el_doc_mot TYPE oij_el_doc_mot .
CONSTANTS: c_char_c VALUE 'C',
c_char_e VALUE 'E',
c_char_p VALUE 'P',
c_char_g VALUE 'G',
c_char_i VALUE 'I',
c_char_s VALUE 'S',
c_char_x VALUE 'X',
c_zsw(3) VALUE 'ZSW',
c_nomit_stat(4) VALUE 'ZDNY' .
DATA : lv_nomtk_split TYPE oij_nomtk.
DATA : i_order_split_create TYPE TABLE OF zsws_order_split.
DATA : wa_order_split_create TYPE zsws_order_split.
LOOP AT i_order_split_create INTO wa_order_split_create.
IF NOT i_create_order IS INITIAL .
CLEAR: i_create_order .
MOVE: wa_order_split_create-docnr TO i_ebeln,
wa_order_split_create-docitm TO i_ebelp .
CALL FUNCTION 'ME_EKKO_SINGLE_READ'
EXPORTING
pi_ebeln = i_ebeln
IMPORTING
po_ekko = i_ekko
EXCEPTIONS
no_records_found = 1
OTHERS = 2.
IF sy-subrc <> 0 .
ENDIF .
Fill PO Header
i_bpoh-comp_code = i_ekko-bukrs .
i_bpoh-doc_type = i_ekko-bsart .
i_bpoh-vendor = i_ekko-lifnr .
i_bpoh-langu = i_ekko-spras .
i_bpoh-pmnttrms = i_ekko-zterm .
i_bpoh-purch_org = i_ekko-ekorg .
i_bpoh-pur_group = i_ekko-ekgrp .
i_bpoh-currency = i_ekko-waers .
i_bpoh-agreement = i_ekko-konnr .
i_bpoh-incoterms1 = i_ekko-inco1 .
i_bpoh-incoterms2 = i_ekko-inco2 .
Fill PO update indicator 'X'
i_bpohx-comp_code = c_char_x .
i_bpohx-doc_type = c_char_x .
i_bpohx-vendor = c_char_x .
i_bpohx-langu = c_char_x .
i_bpohx-pmnttrms = c_char_x .
i_bpohx-purch_org = c_char_x .
i_bpohx-pur_group = c_char_x .
i_bpohx-currency = c_char_x .
i_bpohx-agreement = c_char_x .
i_bpohx-incoterms1 = c_char_x .
i_bpohx-incoterms2 = c_char_x .
CALL FUNCTION 'ME_EKPO_SINGLE_READ'
EXPORTING
pi_ebeln = i_ebeln
pi_ebelp = i_ebelp
IMPORTING
po_ekpo = i_ekpo
EXCEPTIONS
no_records_found = 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 .
Fill PO Item
i_wa_bpoi-po_item = i_ekpo-ebelp .
i_wa_bpoi-material = i_ekpo-matnr .
i_wa_bpoi-plant = i_ekpo-werks .
i_wa_bpoi-stge_loc = i_ekpo-lgort .
i_wa_bpoi-quantity = wa_order_split_create-qty_acptd .
i_wa_bpoi-po_unit = i_ekpo-meins .
i_wa_bpoi-tax_code = i_ekpo-mwskz .
i_wa_bpoi-val_type = i_ekpo-bwtar .
i_wa_bpoi-item_cat = i_ekpo-pstyp .
i_wa_bpoi-acctasscat = i_ekpo-knttp .
i_wa_bpoi-agreement = i_ekpo-konnr .
i_wa_bpoi-agmt_item = i_ekpo-ktpnr .
APPEND i_wa_bpoi TO i_bpoi .
Fill PO Item update indicator 'X'
i_wa_bpoix-po_item = i_ekpo-ebelp .
i_wa_bpoix-po_itemx = c_char_x .
i_wa_bpoix-material = c_char_x .
i_wa_bpoix-plant = c_char_x .
i_wa_bpoix-stge_loc = c_char_x .
i_wa_bpoix-quantity = c_char_x .
i_wa_bpoix-po_unit = c_char_x .
i_wa_bpoix-tax_code = c_char_x .
i_wa_bpoix-val_type = c_char_x .
i_wa_bpoix-item_cat = c_char_x .
i_wa_bpoix-acctasscat = c_char_x .
i_wa_bpoix-agreement = c_char_x .
i_wa_bpoix-agmt_item = c_char_x .
APPEND i_wa_bpoix TO i_bpoix .
Fill PO Item Schedule
i_wa_bpos-po_item = i_ekpo-ebelp .
i_wa_bpos-sched_line = '0001' .
i_wa_bpos-delivery_date = wa_order_split_create-dly_date .
i_wa_bpos-quantity = wa_order_split_create-qty_acptd .
APPEND i_wa_bpos TO i_bpos .
Fill PO Item schedule update indicator 'X'
i_wa_bposx-po_item = i_ekpo-ebelp .
i_wa_bposx-sched_line = '0001' .
i_wa_bposx-delivery_date = c_char_x .
i_wa_bposx-quantity = c_char_x .
APPEND i_wa_bposx TO i_bposx .
CLEAR: i_pargr .
SELECT SINGLE pargr
INTO i_pargr
FROM t161
WHERE bstyp = i_ekko-bstyp
AND bsart = i_ekko-bsart .
CLEAR i_ekpa[].
CALL FUNCTION 'MM_READ_PARTNERS'
EXPORTING
application = c_char_p
ebeln = i_ebeln
bstyp = i_ekko-bstyp
pargr = i_pargr
TABLES
x_ekpa = i_ekpa.
LOOP AT i_ekpa INTO i_wa_ekpa .
i_wa_bpop-partnerdesc = i_wa_ekpa-parvw .
i_wa_bpop-langu = sy-langu .
IF NOT i_wa_ekpa-lifn2 IS INITIAL .
i_wa_bpop-buspartno = i_wa_ekpa-lifn2 .
ELSE .
i_wa_bpop-buspartno = i_wa_ekpa-parnr .
ENDIF .
APPEND i_wa_bpop TO i_bpop .
CLEAR: i_wa_ekpa, i_wa_bpop .
ENDLOOP .
CALL FUNCTION 'DIALOG_SET_NO_DIALOG'.
CALL FUNCTION 'BAPI_PO_CREATE1'
EXPORTING
poheader = i_bpoh
poheaderx = i_bpohx
IMPORTING
exppurchaseorder = i_new_ebeln
TABLES
return = i_bapiret2
poitem = i_bpoi
poitemx = i_bpoix
poschedule = i_bpos
poschedulex = i_bposx.
i_order = i_new_ebeln .
SHIFT i_order LEFT DELETING LEADING '0' .
i_return-errortype = c_char_i .
i_return-workarea = c_zsw .
i_return-message = '064' .
i_return-variable1 = i_order .
loop at i_bapiret2 into i_bapiretn where type ca 'EAX' .
append i_bapiretn to t_bapi_return .
endloop .
if t_bapi_return[] is initial .
i_create_order = c_char_x .
CALL FUNCTION 'SWD_POPUP_MESSAGE_SEND'
EXPORTING
act_return = i_return. "Popup with new PO no.
ENDCASE . " Docind
ENDIF .
ENDLOOP. -
Goods Receipt value in Purchase Order History
Hi Experts,
I raised a PO with Account Assignment category as "K" for 100 quantity with a value of 1000.
GR non-valuated option is ticked in "Delivery" tab in line items.
When posted a GR for 25 NUmbers the Purchase Order History is updated with "0,00" in Amount column.
If this is because of GR Non-valuated option used then please let me know where the amount with correct value is stored in Database tables.
Note: I have use only GR Non-valuated option.
I want to know where the correct value of the stock received is stored.
Regards,
Nani.Hi
By assigning K you will have 3 things in default unless uou change them manually. 1. Goods receipt , 2. GR Non-valuated, Invoice receipt.
When you do a GR then this account gets posted against the G/L you have assigned manually at PO or against the the acct. modifier VBR in OBYC, that is it is consumed directly. So you will not have any stock valuation like raw or other materials.
Now when you carry out Invoice verification you get the postings regularised against the acct assignment object(K) and the vendor outstanding/GR/IR account.
Once IV is done you can check the details of your posting.
Regards -
Hi..
Iam trying to display the Purchase order History using BAPI_PO_GETDETAIL function module... and my code is
data : i_ekko type table of ekko,
i_ekko_wa like line of i_ekko.
parameters : p_vendor like ekko-lifnr,
p_po like ekko-ebeln.
select * from ekko into corresponding fields of table i_ekko where lifnr = p_vendor and ebeln = p_po.
loop at i_ekko into i_ekko_wa.
CALL FUNCTION 'BAPI_PO_GETDETAIL'
EXPORTING
PURCHASEORDER = '4500017124'
ITEMS = 'X'
* ACCOUNT_ASSIGNMENT = ' '
* SCHEDULES = ' '
HISTORY = 'X'
* ITEM_TEXTS = ' '
* HEADER_TEXTS = ' '
* SERVICES = ' '
* CONFIRMATIONS = ' '
* SERVICE_TEXTS = ' '
* EXTENSIONS = ' '
* IMPORTING
* PO_HEADER =
* PO_ADDRESS =
* TABLES
* PO_HEADER_TEXTS =
* PO_ITEMS =
* PO_ITEM_ACCOUNT_ASSIGNMENT =
* PO_ITEM_SCHEDULES =
* PO_ITEM_CONFIRMATIONS =
* PO_ITEM_TEXTS =
* PO_ITEM_HISTORY =
* PO_ITEM_HISTORY_TOTALS =
* PO_ITEM_LIMITS =
* PO_ITEM_CONTRACT_LIMITS =
* PO_ITEM_SERVICES =
* PO_ITEM_SRV_ACCASS_VALUES =
* RETURN =
* PO_SERVICES_TEXTS =
* EXTENSIONOUT =
endloop.
Iam not getting the output ... It doesnt show errors..
Regards,
Abaper.where is the displaying PO code???
check your code once again...
look at this example...
report zbapi_1.
data: begin of i_poitem occurs 0.
include structure bapiekpo.
data: end of i_poitem.
parameters p_ebeln like ekko-ebeln default '4500012164'.
call function 'BAPI_PO_GETDETAIL'
exporting
purchaseorder = p_ebeln
ITEMS = 'X'
ACCOUNT_ASSIGNMENT = ' '
SCHEDULES = ' '
HISTORY = ' '
ITEM_TEXTS = ' '
HEADER_TEXTS = ' '
SERVICES = ' '
CONFIRMATIONS = ' '
SERVICE_TEXTS = ' '
EXTENSIONS = ' '
IMPORTING
PO_HEADER = PO_HEADER
PO_ADDRESS = PO_ADDRESS
tables
PO_HEADER_TEXTS = PO_HEADER_TEXTS
po_items = i_poitem.
PO_ITEM_ACCOUNT_ASSIGNMENT = PO_ITEM_ACCOUNT_ASSIGNMENT
PO_ITEM_SCHEDULES = PO_ITEM_SCHEDULES
PO_ITEM_CONFIRMATIONS = PO_ITEM_CONFIRMATIONS
PO_ITEM_TEXTS = PO_ITEM_TEXTS
PO_ITEM_HISTORY = PO_ITEM_HISTORY
PO_ITEM_HISTORY_TOTALS = PO_ITEM_HISTORY_TOTALS
PO_ITEM_LIMITS =
PO_ITEM_CONTRACT_LIMITS =
PO_ITEM_SERVICES =
PO_ITEM_SRV_ACCASS_VALUES =
RETURN =
PO_SERVICES_TEXTS = .
EXTENSIONOUT = EXTENSIONOUT
loop at i_poitem.
write :/ 'PONUMBER = ' , i_poitem-po_number color col_heading,
/ 'ITEM = ' , i_poitem-po_item,
/ 'MATERIAL NAME = ' , i_poitem-material,
/ 'MATERIAL = ' , i_poitem-pur_mat,
/ 'CHANGED ON = ', i_poitem-changed_on,
/ 'SHORT TEXT = ' , i_poitem-short_text,
/ 'COMPANY CODE = ' , i_poitem-co_code,
/ 'PLANT = ' , i_poitem-plant,
/ 'MATERIAL GROUP = ' , i_poitem-mat_grp,
/ 'QUANTITY = ' , i_poitem-quantity left-justified,
/ 'UNIT = ' , i_poitem-unit,
/ 'NET PRICE = ' , i_poitem-net_price left-justified.
uline.
endloop.
Edited by: Venkat Appikonda on Mar 7, 2009 11:57 AM -
How to Enable Delta for a Custom MM Purchase Order History ODS ???
Hi all,
We have a Customized MM Purchase Order History ODS with Full Update on Monthly basis. We want to enable the DELTA for this ODS and how can I proceed, PLEASE.
Please find the Key Figures and Data Fields in the below:
ODS Structure for PO History ODS:
Key Fields
SAP R/3 Field Description Technical Name
Purchasing Document Number EKBE-EBELN
Purchasing Line Item Number EKBE-EBELP
Sequential number of account assignment EKBE-ZEKKN
Transaction/event type, purchase order history EKBE-VGABE
FI Fiscal Period FISCPER (from BKPF-GJAHR + BKPF-MONAT) in the format YYYYPPPP
Number of Material Document EKBE-BELNR
Item in Material Document EKBE-BUZEI
Data Fields
SAP R/3 Field Description Technical Name
Company Code EKKO-BUKRS
Plant EKPO-EWERK
Account Number of the Vendor EKKO-LIFNR
Currency Key (of PO) EKKO-WAERS
Deletion indicator in purchasing document EKPO-LOEKZ
Purchasing Document Date EKKO-BEDAT
Responsible salesperson at vendor's office EKKO-VERKF
Vendor's telephone number EKKO-TELF1
Incoterms (part 1) EKKO-INCO1
Incoterms (part 2) EKKO-INCO2
Short text EKPO-TXZ01
Material Group EKPO-MATKL
Material Number used by Vendor EKPO-IDNLF
Expected Delivery Date EKET-EINDT
Order unit (UOM) EKPO-BSTME
Delivery Completed Indicator EKPO-ELIKZ
Account assignment category EKPO-KNTTP
Business Area (from PO) EKKN-GSBER
Name of requisitioner/requester EKPO-AFNAM
Purchasing organization EKKO-EKORG
Purchasing group EKKO-BKGRP
G/L Account Number (from PO) EKKN-SAKTO
Cost Center (from PO) EKKN-KOSTL
Work Breakdown Structure Element (WBS Element) EKKN-PS_PSP_PNR
Payment Terms (from PO) EKKO-ZTERM
PO History Category EKBE-BEWTP
Movement Type EKBE-BWART, MSEG-BWART
Debit/Credit Indicator EKBE-SHKZG
Reference from Invoice RBKP-XBLNR
Payment Terms (from Invoice) RBKP-ZTERM
Posting Date RBKP-BUDAT for IR, MKPF-BLDAT for GR
Document Date RBKP-BLDAT for Invoice, MKPF-BLDAT for GR
Baseline Date RBKP-ZFBDT
FI Document Number BKPF-BELNR, found through BKPF-AWKEY (IR # or GR # + fiscal year) or MSEG-LFBNR
FI Dcoument Year BKPF-GJAHR
FI Document Type BKPF-BLART
Fiscal Variant Hardcoded: S4
Payment Method (invoice header level) RBKP-ZLSCH
GL Account (from GR/IR document) MSEG-SAKTO for GR, DRSEG-SAKNR for IR (DRSEG is a structure)
Cost Cener (from GR/IR document) MSEG-KOSTL for GR, DRSEG-KOSTL (DRSEG is a structure) for IR
Business Area (from GR/IR document) MSEG-PARGB; not sure on IR
Local Currency BKPF-HWAE
Local Currency 2 BKPF-HWAE2
Amount posted to GR/IR Clearing (LC) EKBE-AREWR
Amount posted to GR/IR Clearing (GC) EKBE-AREWR converted to Group Currecny found through BKPF-KURS2 if BKPF-HWAE2 is USD
Purchase order quantity EKPO-BSTMG
Price Unit (for PO) EKPO-PEINH
Net price in purchasing document (in document currency) EKPO-BPREI
Amount in local currency; amount in document currency MSEG-DMBTR for material document, RSEG-WRBTR for invoice
Amount in local currency; amount in document currency (GC) MSEG-DMBTR for material document,
RSEG-WRBTR for invoice converted to USD
Quantity MSEG-ERFMG for material document;
RSEG-MENGE for Invoice
Delivery costs' share of item value RSEG-BNKAN
Delivery costs' share of item value (GC)RSEG-BNKAN converted to USD
Tax Amount (accrued) BSEG-PSWBT
Freight Amount (accrued) BSEG-PSWBT
Discount Amount (invoice header level) RBKP-WSKTO
Thanks.Hi Venkat,
If you are using a Custom DataSource/Extractor the main problem is that you are collecting data from a lot of tables, so it is really difficult to determine a field for the delta.
If for you is important only a change at Key Fields Table (EKBE) you can set the Generic Delta only on a field of this table (Doc Number or Position Number - Date - Timestamp).
But if you are interested in all changes you have to determine a single field for every tables...
I think it is really difficult to find a delta in all these tables.
Maybe you can think to use in BW an ODS without Reporting BEx flag to determine Delta, and then introduce delta records in a Cube.
Ciao.
Riccardo. -
Purchase Order history tab. DCin line.
Hi All
Can you please explain what is the DCIn line on purchase order history tab under the same number as IR-L?
I assume its related to condition record for delivery costs. Is it so?
Does DCIn somehow correlates with DCGR?
How can i re-produce in the test creation of DCIn line?
Thanks
Best Regards
Andreyhi
this is nothing but the LIV of freight cost
if you are getting this with same number as the IV then ,you might have posted both freight and GR cost at same time
in miro u have options at right middle
>>goods/service items
>>planned delivery cost
>>goods/service items+planned delivery cost
you might have select last option so that you will get same invocie number for both
if you use 1 or 2 you will get separate numbers -
Purchase Order History not appearing for Purchase Order with service items
A purchase order with a service item has been created. A SES has been created and Miro transactions as well. When tcode ME2L is executed, the Purchase Order History field is blank. Any configuration missing or is there an applicable OSS note to fix this?
Hi,
It is a coding error.
Could you please check if you have applied the note 1049031 with the latest version 13?
Regards,
Edit -
Purchase Order History SES not shown when not accepted
We are working on 2 systems : one is ECC 6.0 and the other is 4.6.
When i create a SES via ML81N and the SES is not released yet : on the 4.6 version, the SES is shown in the purchase order history, while in the ECC 6.0 version, the SES is not shown in the purchase order history. In ECC 6.0, the SES is shown inthe purchase order history tab after the SES has been accepted.
Is this a setting in customizing or a difference in the 2 versions of SAP?Hi,
no, it might be a coding error or an inconsistency issue.
Please check the note
442091 - Service entry sheet missing in purchase order hist
In order to repair already existing inconsistencies, you can use report
RMESSRK2 (from Note 141870 or as of Release 4.6C in development class
ML_TOOLS). However, the report must be modified in the two positions
specified in the attachment.
If you can not find the report RMESSRK2 in transaction SE38
in your system - or in transaction SE80 under the development class
ML_TOOLS, then please copy the program from the attached note
ML_TOOLS into your system and correct the coding according to
note 442091.
Regards,
Edit -
Purchase order history for service entry sheet
Hello All,
I created 3 service entry sheets for service P.O. however I saved it with out accepting them. Why the Purchase order history is not updated after the service entry sheets were saved?
When I created another service entry sheet for the same P.O. and accepted the service entry sheet and then saved it, the purchase order history was updated along with the posting of latest service entry sheet and previous three service entry sheets are also visible.
Why this is happening? Please help.
With regards.
SanjayDear Prashant,
Thanks for the response.
1) Whenever a SES is saved (without acceptance) an entry gets updated in PO history with out posting document number.
2)Material doc. entry gets updated in P.O. history table when SES is accepted and saved.
Sl. no. 1 is not happening when I create SES for the first time. Once 2nd SES is made and accepted and saved. After that all entries including the first one is shown in P.O. history table.
Thanks and regards.
Sanjay -
SubContractor issue not updated in purchase order history
Hi Masters
Can anybody explain me why the material document regarding the material issued to sub contractor is not updated in the purchase order history?
Is it a Standard one or anything missing in the configuration?
Regards
MohanHi
Transfer posting to vendor account is nothing but your material lies in vendor area. but liability is with u.
This u can view thro MMBE, in that particular material lies with the vendor qty it will show.
In ME2O, u can list out what are the material lying in vendor yard.
So transfer posting to vendor will not reflect in PO history.Pls check.
Regards,
Raman -
Problem with purchase order history
Hi,
i have the following problem
I create a service purchase order for the quantity of 36000 and amount of 1350 (0.0375 per unit)
Step 1:
I entered a service entry sheet:
quatity: 17800
Value: 667.5
The system create a 101 for the amount of 667.5. Then i reversed the entry service trough movement 102 and i deleted the service entry sheet.
Step 2:
I repeated the step 1 but for the quantity of 17500 and the amount of 656.25.
Step 3: Finally i entered a service entry sheet for the quantity of 9000 and the amount of 337.5 (9000*0.0375)
An error ocurred on the purchase order history. The lerf (service entry sheet, appear for the total amount of the PO: 1350 and the WE 101 for the amount of the service entry sheet: 337.5 (9000*0.0375)
I want to know why the system entered the service entry sheet for the total value (360000.0375) when i did it just for 337.5 (90000.0375)
Thanks in advance for your help.
Enzo.Thanks, but i dont understand what your are trying to explaim me
The problem is when I enter a Service entry sheet trough ML81N the system should generate a 101 for the same value. It doesn´t happend.
In purchase order, the service entry sheet is for the amount of the Lerf created but the 101 (should generate automatically) is for the total of the purchase order.
I dont know why its happend
Thanks in advance for your help
Enzo -
ME23N purchase order history - add new fields (not in layout)
Hello,
I would like to expand the layout of Purchase order history (ME23N).
I would like to add the field MKPF-BKTXT into the purchase order history for more information.
Who can help? - Thank you. - DietlindeHello,
You might have to enhance the column set of the layout..I am not sure if it could be done.. but that's the way to go.. You might want to confirm this from your technical team.
Good Luck!!
Maybe you are looking for
-
Hi, I got Technical Specs from my company to create DSO , so here in Technical Specs under Data Fields Coloumn some are Characteristics and some Keyfigures. but what i know Data Fields should only contains Keyfigures? Need Clarification. Thanks and R
-
Hello Experts, Thinking of un-installing BPC 7.5 from the Windows 2008 R2 server (to re-install again). I assume its just as simple as go to control panel and uninstalling it. Does it remove the registry entries automatically
-
Registry can't find Flash9c.ocx
I'm having this problem on every single computer I own. The error message I'm getting is: "CLSID\{1171A62F-05D2-11D1-83FC-00A0C9089C5A}\InprocServer32," refers to a missing file, "C:\WINDOWS\system32\Macromed\Flash\Flash9c.ocx." There doesn't appear
-
while bbm just came out on other devices, is there any app designed for nokia symbian belle
-
Hi all, I am attempting to install gpsdrive and when I am inserting the map data, I get this error: Using projection SRS 900913 (Spherical Mercator) Setting up table: planet_osm_point NOTICE: table "planet_osm_point" does not exist, skipping NOTICE: