Purchase requsition report

Hi All,
I want detailed purchase req. report with customized layout. not like me5a,
Satpal

Hi
Copy the report program of ME5A & include the Customizied layout in the output include of the program.
Thanks & Regards
Kishore

Similar Messages

Regarding Purchase Requsition Report

hi,
i am making report on Purchase Requsition in which i have to display that these are the persons who had approved at this date.
i am currently using tables: EBAN,T16FG but it is not giving the desierd result ,can anybody help me out in making thisreport ,HE OR SHE will be definately rewarded.
Reply as fast as possible.
regards,
ric.s

Hi
Check/Use the Tables
T161E and T161F for the PR Release info
by taking the related fields from EBAN
also check the Pur requisition Business Object BUS2105 Program for the other release info in SWO1 Tcode, you will find it
Regards
Anji

Re: Regarding Purchase Requsition Report

HI,
I am making purchase Requisition Report and i want to display that these are the PURCHASE REQUISITIONS and these are approved by these persons at these dates.
if anybody provide me help he or she will be definately rewarded.
Message was edited by:
ric .s

Hi
First fetch the data from the EBAN table
and using the fields
FRGKZ
FRGZU
FRGST
check in the tables like T161s,T162 etc for the release info of PR's and display
also check the business object BUS2105 Program for the release info fun modules like
BAPI_REQUISITION_GETRELINFO
Regards
Anji

Urgent : Regarding Purchase Requsition Report

Hi,
I am making a report on Purchase Requisition in which i have to display that these are the persons who have released this requisition (i.e. If General Manager has released that should be displayed,if Director had released it should be displayed and if Managing Director had released it should display it and also the dates on which they released..)
In my report i am not allowed to displayed that these are released by MMCONS OR SDCONS BUT it should display General Manager,Director or Managing Director.. at these particular dates...
If anybody help me out in this report he or she will be definately rewarded with points as it is most urgent to me ,,so plz reply as fast as possible.
Regards,
Ric.s
Message was edited by:
 ric .s

Hai ric,
 i have done a pr tracking report. it will show the persons name, plant, and department, etc .i have added that program here. if u dnt mine u can take
with regards,
safiq
TYPE-POOLS slis.
TABLES: t024, ekko, lfa1, ekpo, ekkn, cdhdr, cdpos, t16fs,
eban, eket, ekbe, t024d.
DATA: repid LIKE sy-repid.
DATA: releasedat LIKE cdhdr-udate.
CONSTANTS: c_to(4) TYPE c VALUE ' to ',
 c_vgabe_1 TYPE c VALUE '1',
 c_vgabe_2 TYPE c VALUE '2',
 c_object_banf LIKE cdpos-objectclas VALUE 'BANF',
 c_fname_frgzu LIKE cdpos-fname VALUE 'FRGZU',
 c_tcode like cdhdr-tcode value 'ME54',
c_tcode1 like cdhdr-tcode value 'ME55',
 A1=add one more constant and value for ME55.
 c_tcode2 like cdhdr-tcode value 'ME28',
CN 2 >> Addition
CN 2 Start
 c_tcode3 like cdhdr-tcode value 'ME54N',
 c_tcode4 like cdhdr-tcode value 'ME29N',
CN 2 End
 c_object_eink LIKE cdpos-objectclas VALUE 'EINKBELEG',
 c_fname_frgke LIKE cdpos-fname VALUE 'FRGKE'.
DATA: list_layout TYPE slis_layout_alv, "Layout
 ist_fieldcat TYPE STANDARD TABLE OF "Field Catalog
 slis_fieldcat_alv,
 tmp_fieldcat TYPE slis_fieldcat_alv, "Temp. Field Cat.
 gt_xevents TYPE slis_t_event, "Events Table
 xs_event TYPE slis_alv_event. "Event Line
RANGES: tcode for cdhdr-tcode.
A1=Add range to store ME54 & ME55
*& To store Summary report information - added 30/5
data: begin of i_summary occurs 100,
 PlantName1 LIKE T001W-Name1, "Plant Name
 plant1 LIKE ekpo-werks, "Plant
 Dept LIKE t024d-dsnam, "MRP Contrl Code
 PRafIR type i,
 PRbfIR type i,
 Grandtotal type i,
 PerPRafIR type p decimals 2,
 PerPRbfIR type p decimals 2,
end of i_summary.
STRUCTURES
DATA: BEGIN OF t_ekko OCCURS 0.
 INCLUDE STRUCTURE ekko.
DATA: END OF t_ekko.
DATA: BEGIN OF st_itab,
 pur_grp(22) TYPE c,
 vendor_name LIKE lfa1-name1,
 po_num LIKE ekko-ebeln,
 item_num LIKE ekpo-ebelp,
 mat_num LIKE ekpo-matnr,
 description LIKE ekpo-txz01,
 qty_order LIKE ekpo-menge,
 unit_price LIKE ekpo-netpr,
 total_price LIKE ekpo-netwr,
 plant LIKE ekpo-werks,
 cost_center LIKE ekkn-kostl,
 internal_order LIKE ekkn-aufnr,
 gl_code LIKE ekkn-sakto,
 dept LIKE t024d-dsnam,
 po_release_dat LIKE cdhdr-udate,
 delivery_dat LIKE eket-eindt,
* gr_dat like ekbe-budat, "MICH01- 24/04/03
 gr_dat LIKE ekbe-bldat, "MICH01+ 24/04/03
 on_time_delivery TYPE c,
 gr_qty LIKE ekbe-menge,
 gr_doc_num LIKE ekbe-belnr,
 ir_posting_date LIKE ekbe-budat, "??? change to budat
 ir_doc_num LIKE ekbe-belnr,
END OF st_itab.
DATA: BEGIN OF st_itab1,
 aedat LIKE ekko-aedat, "PO creation date
 lifnr LIKE ekko-lifnr,
 ebeln LIKE ekko-ebeln, "PO number
 ekgrp LIKE ekko-ekgrp,
 matnr LIKE ekpo-matnr,
 banfn LIKE ekpo-banfn, "PR number
 werks LIKE ekpo-werks, "PO item number
 ebelp LIKE ekpo-ebelp,
 bnfpo like eban-bnfpo, "PR item number
 txz01 LIKE ekpo-txz01,
 menge LIKE ekpo-menge,
 netpr LIKE ekpo-netpr,
 netwr LIKE ekpo-netwr,
 kostl LIKE ekkn-kostl,
 aufnr LIKE ekkn-aufnr,
 sakto LIKE ekkn-sakto,
 prctr LIKE ekkn-prctr,
 anln1 LIKE ekkn-anln1,
 pstyp LIKE eban-pstyp,
 badat LIKE eban-badat,
 afnam LIKE eban-afnam,
 dispo LIKE eban-dispo,
 vgabe LIKE ekbe-vgabe,
 belnr LIKE ekbe-belnr,
 bldat LIKE ekbe-bldat, "GR Creation date
 budat LIKE ekbe-budat, "IR Creation date
 gr_qty LIKE ekbe-menge,
 eindt LIKE eket-eindt,
 udate LIKE cdhdr-udate,
 beln1 LIKE ekbe-belnr, "IR Doc. No.
 dsnam LIKE t024d-dsnam, "MRP Controller Desc
 pur_grp LIKE t024-eknam, "Desc. of Purchasing Gp
 name1 LIKE lfa1-name1, "Vendor Code
 on_time_delivery TYPE c, "On-time-delivery
 flag type c, "Flag
Added by @, 21.05.2007 >>
 PRAFIR TYPE i,
 PRBFIR TYPE i,
 TOTPR TYPE i,
Added by @, 21.05.2007 <<
 END OF st_itab1.
GR History Movements
DATA: BEGIN OF st_history,
 bldat LIKE ekbe-bldat,
 menge LIKE ekbe-menge,
 belnr LIKE ekbe-belnr,
 END OF st_history.
PO Release Data
DATA: BEGIN OF st_change,
 changenr LIKE cdpos-changenr,
 value_new LIKE cdpos-value_new,
 END OF st_change.
data: begin of st_change1,
 udate like cdhdr-udate,
 end of st_change1.
INTERNAL TABLES
DATA: itab LIKE TABLE OF st_itab,
 ist_history LIKE TABLE OF st_history,
 wa_history LIKE st_history,
 ist_change LIKE TABLE OF st_change,
 wa_change LIKE st_change,
 ist_change1 like table of st_change1,
 wa_change1 like st_change1.
data: begin of ist_itab occurs 0.
 include structure st_itab1.
DATA : vgabe LIKE ekbe-vgabe,
 belnr LIKE ekbe-belnr,
 bldat LIKE ekbe-bldat, "GR Creation date
 budat LIKE ekbe-budat, "IR Creation date
 beln1 LIKE ekbe-belnr, "IR Doc. No.
 gr_qty like ekbe-menge, "GR Qty
 gr_unres LIKE ekbe-menge, "GR to unrestricted
 gr_inspec_stk like ekbe-menge, "GR to inspection stock
 gr_blk_stk like ekbe-menge, "GR to blocked stock
 gr_rejected_stk like ekbe-menge, "GR to rejected stock
 relcode1 like t16fs-FRGC1, "Release code 1
 reldate1 like cdhdr-udate, "Release date 1
 relcode2 like t16fs-FRGC1, "Release code 2
 reldate2 like cdhdr-udate, "Release date 2
 relcode3 like t16fs-FRGC1, "Release code 3
 reldate3 like cdhdr-udate, "Release date 3
 relcode4 like t16fs-FRGC1, "Release code 4
 reldate4 like cdhdr-udate, "Release date 4
 relcode5 like t16fs-FRGC1, "Release code 5
 reldate5 like cdhdr-udate, "Release date 5
 po_rel_date like cdhdr-udate. "PO release date
data: end of ist_itab.
data: wa_itab LIKE ist_itab.
Added on 21.05.2007 >>
data: s_po Type C.
data: s_pr Type C.
SELECTION SCREEN
SELECTION-SCREEN BEGIN OF BLOCK screen1 WITH FRAME TITLE text-001.
SELECT-OPTIONS:
so_aedat FOR ekko-aedat no-display, "Purchase Order Creation Date
so_udate FOR cdhdr-udate no-display, "PO Release Date
so_eindt FOR eket-eindt no-display, "Delivery Date
so_ekgrp FOR t024-ekgrp no-display, "Purchasing Group
so_lifnr FOR ekko-lifnr no-display, "Vendor Code
so_ebeln FOR ekko-ebeln no-display, "PO Number
so_matnr FOR ekpo-matnr no-display, "Material No.
so_banfn FOR ekpo-banfn no-display, "PR No.
so_dispo for eban-dispo no-display, "MRP controller
so_pstyp FOR ekpo-pstyp no-display, "Item Category
so_badat FOR eban-badat OBLIGATORY, "PR Creation Date
so_afnam FOR eban-afnam no-display, "PR Requester Name
so_werks FOR ekpo-werks OBLIGATORY, "Plant
so_kostl FOR ekkn-kostl no-display, "Cost Center
so_aufnr FOR ekkn-aufnr no-display, "Internal Order
so_sakto FOR ekkn-sakto no-display, "G/L Account
so_prctr FOR ekkn-prctr no-display, "Profit Center
so_anln1 FOR ekkn-anln1 no-display, "Asset Number
so_belnr FOR ekbe-belnr no-display, "GR Doc. No.
so_bldat FOR ekbe-bldat no-display, "GR Creation Date
so_budat FOR ekbe-budat no-display, "IR Posting Date
so_beln1 FOR ekbe-belnr no-display, "IR Doc. No
so_frgkz for eban-frgkz no-display. "Release status of PR
SELECTION-SCREEN SKIP 1.
PARAMETERS:
p_pr_rel(1) TYPE C no-display, "PR Release Indicator
p_on_del(1) TYPE C no-display. "On-time-delivery
SELECTION-SCREEN END OF BLOCK screen1.
Selection Screen - add 30/5
selection-screen begin of block screen2 with frame title text-002.
selection-screen begin of line.
parameters: r_sum radiobutton group grp1.
selection-screen comment 2(20) text-003 for field r_sum.
selection-screen end of line.
selection-screen begin of line.
parameters: r_det radiobutton group grp1 default 'X'.
selection-screen comment 2(20) text-004 for field r_det.
selection-screen end of line.
selection-screen end of block screen2.
 MAIN *
*s_pr = 'X'.
Added on 21.05.2007 <<
*repid = sy-repid.
Assign release indicator
*if p_pr_rel = 'Y'.
so_frgkz-low = '2'.
so_frgkz-option = 'EQ'.
so_frgkz-sign = 'I'.
append so_frgkz.
clear so_frgkz.
*elseif p_pr_rel = 'N'.
so_frgkz-low = 'X'.
so_frgkz-option = 'EQ'.
so_frgkz-sign = 'I'.
append so_frgkz.
clear so_frgkz.
*endif.
*tcode-low = 'ME54'.
*tcode-option = 'EQ'.
*tcode-sign = 'I'.
*append tcode.
CN 2 >> Addition
CN 2 Start
*tcode-low = 'ME54N'.
*tcode-option = 'EQ'.
*tcode-sign = 'I'.
*append tcode.
CN 2 End
*tcode-low = 'ME55'.
*tcode-option = 'EQ'.
*tcode-sign = 'I'.
*append tcode.
*PERFORM:
get_details,
get_data,
get_gr_ir_data,
get_other_data,
Setup events --> Top-of-page
setup_events,
Build up ALV field catalogue
setfieldcat,
Output the data
output_alv_report TABLES ist_fieldcat.
Perform print_data.
top-of-page.
perform print_heading.
END-OF-PAGE.
WRITE :/ SY-ULINE(126).
 FORM Assign_Values *
FORM assign_values.
ENDFORM.
 FORM setFieldCat *
FORM setfieldcat.
PERFORM:
 add_field_to_fieldcat TABLES ist_fieldcat
 USING 'T024D'
 'DSNAM'
 'IST_ITAB'
 'DSNAM'
 'Dept'
 'X'
 add_field_to_fieldcat TABLES ist_fieldcat
 USING 'EKPO'
 'WERKS'
 'IST_ITAB'
 'WERKS'
 'Plant'
 'X'
 add_field_to_fieldcat TABLES ist_fieldcat
 USING 'EBAN'
 'AFNAM'
 'IST_ITAB'
 'AFNAM'
 'PR Requestor Name'
 'X'
 add_field_to_fieldcat TABLES ist_fieldcat
 USING ''
 'IST_ITAB'
 'PRBFIR'
 'PRbfIR'
 '6'
 add_field_to_fieldcat TABLES ist_fieldcat
 USING ''
 'IST_ITAB'
 'PRAFIR'
 'PRafIR'
 '6'
 add_field_to_fieldcat TABLES ist_fieldcat
 USING ''
 'IST_ITAB'
 'TOTPR'
 'TotalPR'
 '7'
 add_field_to_fieldcat TABLES ist_fieldcat
 USING 'EBAN'
 'BADAT'
 'IST_ITAB'
 'BADAT'
 'PR Creation Date'
 'X'
 add_field_to_fieldcat TABLES ist_fieldcat
 USING 'EBAN'
 'BANFN'
 'IST_ITAB'
 'BANFN'
 'PR No'
 'X'
 add_field_to_fieldcat TABLES ist_fieldcat
 USING 'EKKO'
 'EBELN'
 'IST_ITAB'
 'EBELN'
 'PO Number'
 'X'
 add_field_to_fieldcat TABLES ist_fieldcat
 USING 'EKKO'
 'EBELP'
 'IST_ITAB'
 'EBELP'
 'PO Item'
 'X'
 add_field_to_fieldcat TABLES ist_fieldcat
 USING 'EKKO'
 'AEDAT'
 'IST_ITAB'
 'AEDAT'
 'PO Creation Date'
 'X'
 add_field_to_fieldcat TABLES ist_fieldcat
 USING 'EKBE'
 'BLDAT'
 'IST_ITAB'
 'BLDAT'
 'GR Date'
 'X'
 add_field_to_fieldcat TABLES ist_fieldcat
 USING 'EKBE'
 'BUDAT'
 'IST_ITAB'
 'BUDAT'
 'IR Document Date'
 'X'
 add_field_to_fieldcat TABLES ist_fieldcat
 USING 'EKPO'
 'TXZ01'
 'IST_ITAB'
 'TXZ01'
 'Description'
 'X'
 add_field_to_fieldcat TABLES ist_fieldcat
 USING 'EKPO'
 'MENGE'
 'IST_ITAB'
 'MENGE'
 'Qty Ordered'
 add_field_to_fieldcat TABLES ist_fieldcat
 USING 'EKPO'
 'NETPR'
 'IST_ITAB'
 'NETPR'
 'Unit Price'
 add_field_to_fieldcat TABLES ist_fieldcat
 USING 'EKPO'
 'NETWR'
 'IST_ITAB'
 'NETWR'
 'Total Price'
 'X'
 add_field_to_fieldcat TABLES ist_fieldcat
 USING 'T024'
 'EKNAM'
 'IST_ITAB'
 'PUR_GRP'
 'PO PurGrp'
 'X'
 add_field_to_fieldcat TABLES ist_fieldcat
 USING 'LFA1'
 'NAME1'
 'IST_ITAB'
 'NAME1'
 'Vendor Name'
 'X'
 add_field_to_fieldcat TABLES ist_fieldcat
 USING 'EKPO'
 'MATNR'
 'IST_ITAB'
 'MATNR'
 'Material Number'
 'X'
 add_field_to_fieldcat TABLES ist_fieldcat
 USING 'EKKN'
 'KOSTL'
 'IST_ITAB'
 'KOSTL'
 'Cost Center'
 'X'
 add_field_to_fieldcat TABLES ist_fieldcat
 USING 'EKKN'
 'AUFNR'
 'IST_ITAB'
 'AUFNR'
 'Internal Order'
 'X'
 add_field_to_fieldcat TABLES ist_fieldcat
 USING 'EKKN'
 'SAKTO'
 'IST_ITAB'
 'SAKTO'
 'GL Code'
 'X'
 add_field_to_fieldcat TABLES ist_fieldcat
 USING 'EKKN'
 'ANLN1'
 'IST_ITAB'
 'ANLN1'
 'Asset'
 'X'
 add_field_to_fieldcat TABLES ist_fieldcat
 USING 'EKKN'
 'PRCTR'
 'IST_ITAB'
 'PRCTR'
 'Profit Centre'
 'X'
 add_field_to_fieldcat TABLES ist_fieldcat
 USING 'T16FS'
 'FRGC1'
 'IST_ITAB'
 'RELCODE1'
 'PR RelCode1'
 'X'
 add_field_to_fieldcat TABLES ist_fieldcat
 USING 'CDHDR'
 'UDATE'
 'IST_ITAB'
 'RELDATE1'
 'PR RelDate1'
 'X'
 add_field_to_fieldcat TABLES ist_fieldcat
 USING 'T16FS'
 'FRGC2'
 'IST_ITAB'
 'RELCODE2'
 'PR RelCode2'
 'X'
 add_field_to_fieldcat TABLES ist_fieldcat
 USING 'CDHDR'
 'UDATE'
 'IST_ITAB'
 'RELDATE2'
 'PR RelDate2'
 'X'
 add_field_to_fieldcat TABLES ist_fieldcat
 USING 'T16FS'
 'FRGC3'
 'IST_ITAB'
 'RELCODE3'
 'PR RelCode3'
 'X'
 add_field_to_fieldcat TABLES ist_fieldcat
 USING 'CDHDR'
 'UDATE'
 'IST_ITAB'
 'RELDATE3'
 'PR RelDate3'
 'X'
 add_field_to_fieldcat TABLES ist_fieldcat
 USING 'T16FS'
 'FRGC4'
 'IST_ITAB'
 'RELCODE4'
 'PR RelCode4'
 'X'
 add_field_to_fieldcat TABLES ist_fieldcat
 USING 'CDHDR'
 'UDATE'
 'IST_ITAB'
 'RELDATE4'
 'PR RelDate4'
 'X'
 add_field_to_fieldcat TABLES ist_fieldcat
 USING 'T16FS'
 'FRGC5'
 'IST_ITAB'
 'RELCODE5'
 'PR RelCode5'
 'X'
 add_field_to_fieldcat TABLES ist_fieldcat
 USING 'CDHDR'
 'UDATE'
 'IST_ITAB'
 'RELDATE5'
 'PR RelDate5'
 'X'
add_field_to_fieldcat TABLES ist_fieldcat
 USING 'CDHDR'
 'UDATE'
 'IST_ITAB'
 'PO_REL_DATE'
 'PO Release Date'
 'X'
add_field_to_fieldcat TABLES ist_fieldcat
 USING 'EKET'
 'EINDT'
 'IST_ITAB'
 'EINDT'
 'PO Dlv Date'
 'X'
add_field_to_fieldcat TABLES ist_fieldcat
 USING ''
 'IST_ITAB'
 'ON_TIME_DELIVERY'
 'On Time Delivery'
 '16'
 'X'
add_field_to_fieldcat TABLES ist_fieldcat
 USING 'EKBE'
 'MENGE'
 'IST_ITAB'
 'GR_QTY'
 'GR Qty'
 'X'
add_field_to_fieldcat TABLES ist_fieldcat
 USING 'EKBE'
 'BELNR'
 'IST_ITAB'
 'BELNR'
 'GR Doc Num'
 'X'
add_field_to_fieldcat TABLES ist_fieldcat
 USING 'EKBE'
 'MENGE'
 'IST_ITAB'
 'GR_UNRES'
 'GR to Unrestricted'
 'X'
add_field_to_fieldcat TABLES ist_fieldcat
 USING 'EKBE'
 'MENGE'
 'IST_ITAB'
 'GR_INSPEC_STK'
 'GR to Inspection Stock'
 'X'
add_field_to_fieldcat TABLES ist_fieldcat
 USING 'EKBE'
 'MENGE'
 'IST_ITAB'
 'GR_BLK_STK'
 'GR to Blocked Stock'
 'X'
add_field_to_fieldcat TABLES ist_fieldcat
 USING 'EKBE'
 'MENGE'
 'IST_ITAB'
 'GR_REJECTED_STK'
 'GR to Rejected Stock'
 'X'
Added by @, 21.05.2007 >>
add_field_to_fieldcat TABLES ist_fieldcat
 USING 'EKBE'
 'BELNR'
 'IST_ITAB'
 'BELN1'
 'IR Doc Num'
 'X'
add_field_to_fieldcat TABLES ist_fieldcat
 USING 'EKBE'
 'BELNR'
 'IST_ITAB'
 'BELN1'
 'IR Doc Num'
 'X'
Added by @, 21.05.2007 <<
ENDFORM.
 FORM XEVENTS *
FORM setup_events.
CLEAR xs_event.
xs_event-name = slis_ev_end_of_page.
xs_event-form = 'XEND_OF_PAGE'.
APPEND xs_event TO gt_xevents.
CLEAR xs_event.
xs_event-name = slis_ev_top_of_page.
xs_event-form = 'XTOP_OF_PAGE'.
APPEND xs_event TO gt_xevents.
CLEAR xs_event.
xs_event-name = slis_ev_top_of_list.
xs_event-form = 'XTOP_OF_LIST'.
APPEND xs_event TO gt_xevents.
CLEAR xs_event.
xs_event-name = slis_ev_end_of_list.
xs_event-form = 'XEND_OF_LIST'.
APPEND xs_event TO gt_xevents.
ENDFORM.
 FORM XTOP_OF_PAGE *
FORM xtop_of_page.
Write at 117 sy-pagno right-justified.
WRITE: / 'PR Tracking Report (against Invoice Date)'.
WRITE:/(42) sy-uline.
PO Creation Date
IF NOT so_aedat-low IS INITIAL AND
 so_aedat-high IS INITIAL.
 WRITE:/ 'PO Creation Date:', so_aedat-low.
ELSEIF NOT so_aedat-low IS INITIAL AND
 NOT so_aedat-high IS INITIAL.
 WRITE:/ 'PO Creation Date:', so_aedat-low, c_to, so_aedat-high.
ENDIF.
PR Creation Date
IF NOT so_badat-low IS INITIAL AND
 so_badat-high IS INITIAL.
 WRITE:/ 'PR Creation Date: ', so_badat-low.
ELSEIF NOT so_badat-low IS INITIAL AND
 NOT so_badat-high IS INITIAL.
 WRITE:/ 'PR Creation Date: ', so_badat-low , c_to, so_badat-high.
ENDIF.
Plant
IF NOT so_werks-low IS INITIAL AND
 so_werks-high IS INITIAL.
 WRITE:/ 'Plant: ', so_werks-low.
ELSEIF NOT so_werks-low IS INITIAL AND
 NOT so_werks-high IS INITIAL.
 WRITE:/ 'Plant: ', so_werks-low , c_to, so_werks-high.
ENDIF.
Delivery Date
IF NOT so_eindt-low IS INITIAL AND
 so_eindt-high IS INITIAL.
 WRITE:/ 'Delivery Date: ', so_eindt-low.
ELSEIF NOT so_eindt-low IS INITIAL AND
 NOT so_eindt-high IS INITIAL.
 WRITE:/ 'Delivery Date: ', so_eindt-low , c_to, so_eindt-high.
ENDIF.
Purchasing Group
IF NOT so_ekgrp-low IS INITIAL AND
 so_ekgrp-high IS INITIAL.
 WRITE:/ 'Purchasing Group: ', so_ekgrp-low.
ELSEIF NOT so_ekgrp-low IS INITIAL AND
 NOT so_ekgrp-high IS INITIAL.
 WRITE:/ 'Purchasing Group: ', so_ekgrp-low , c_to, so_ekgrp-high.
ENDIF.
Vendor Code
IF NOT so_lifnr-low IS INITIAL AND
 so_lifnr-high IS INITIAL.
 WRITE:/ 'Vendor Code: ', so_lifnr-low.
ELSEIF NOT so_lifnr-low IS INITIAL AND
 NOT so_lifnr-high IS INITIAL.
 WRITE:/ 'Vendor Code: ', so_lifnr-low , c_to, so_lifnr-high.
ENDIF.
PO Number
IF NOT so_ebeln-low IS INITIAL AND
 so_ebeln-high IS INITIAL.
 WRITE:/ 'PO Number: ', so_ebeln-low.
ELSEIF NOT so_ebeln-low IS INITIAL AND
 NOT so_ebeln-high IS INITIAL.
 WRITE:/ 'PO Number: ', so_ebeln-low , c_to, so_ebeln-high.
ENDIF.
Material No
IF NOT so_matnr-low IS INITIAL AND
 so_matnr-high IS INITIAL.
 WRITE:/ 'PO Number: ', so_matnr-low.
ELSEIF NOT so_matnr-low IS INITIAL AND
 NOT so_matnr-high IS INI

Urgent:regarding purchase requsitions

HI,
i am making purchase requsition report in which i have to display that these are the person who released the purchase requsition at dese dates.
plzzzz help me out as i am able to display only release requsitions but not the person who had released it. i am using table eban.
IF ANYBODY HELP ME OUT HE OR SHE WILL BE DEFINATELY REWARDED.
Regards,
ric.s

Hi,
Go through this program, you have answer
It is possible to generate a complete list of purchase document releases with the purchase document number (requisitions and orders), releaser, release date and release time. * First, create an Infoset using transaction SQ02 directly reading from table CDPOS and create an additional table: CDHDR. If you are releasing purchase requsitions at the item level, it is convenient to create an additional field (PURPS LIKE EBAN-BNFPO) to capture the item number.
GO THROUGH THIS CODE
Mass Display of Purchase Orders
Submitted by webmaster at www.sap-img.com
Mass display or print Purchase Order History
You can request report by :
1. Change date
2. User Name
3. Purchase Order Number
4. Vendor Code
Written by : SAP Basis, ABAP Programming and Other IMG Stuff
www.sap-img.com
REPORT ZPOCHANGE LINE-SIZE 132 NO STANDARD PAGE HEADING
LINE-COUNT 065(001)
MESSAGE-ID VR.
TABLES: DD04T,
CDHDR,
CDPOS,
DD03L,
DD41V,
T685T,
VBPA,
TPART,
KONVC,
EKKO.
SELECT-OPTIONS: XUDATE FOR CDHDR-UDATE,
XNAME FOR CDHDR-USERNAME,
XEBELN FOR EKKO-EBELN,
XLIFNR FOR EKKO-LIFNR.
SELECTION-SCREEN SKIP.
TEXT-001 - Sorting Sequence
SELECTION-SCREEN BEGIN OF BLOCK BLK1 WITH FRAME TITLE TEXT-001.
PARAMETERS: SUDATE RADIOBUTTON GROUP R1,
SNAME RADIOBUTTON GROUP R1,
SOBID RADIOBUTTON GROUP R1.
SELECTION-SCREEN END OF BLOCK BLK1.
DATA: WFLAG,
WCHANGENR LIKE CDHDR-CHANGENR.
DATA: INDTEXT(60) TYPE C.
DATA: BEGIN OF ICDHDR OCCURS 50.
INCLUDE STRUCTURE CDHDR.
DATA: END OF ICDHDR.
DATA: BEGIN OF ICDSHW OCCURS 50.
INCLUDE STRUCTURE CDSHW.
DATA: END OF ICDSHW.
DATA: BEGIN OF EKKEY,
EBELN LIKE EKET-EBELN,
EBELP LIKE EKET-EBELP,
ETENR LIKE EKET-ETENR,
END OF EKKEY.
DATA: BEGIN OF ITAB OCCURS 50,
BEGIN OF EKKEY,
EBELN LIKE EKET-EBELN,
EBELP LIKE EKET-EBELP,
ETENR LIKE EKET-ETENR,
END OF EKKEY,
CHANGENR LIKE CDHDR-CHANGENR,
UDATE LIKE CDHDR-UDATE,
UTIME LIKE CDHDR-UTIME,
USERNAME LIKE CDHDR-USERNAME,
CHNGIND LIKE CDSHW-CHNGIND,
FTEXT LIKE CDSHW-FTEXT,
OUTLEN LIKE CDSHW-OUTLEN,
F_OLD LIKE CDSHW-F_OLD,
F_NEW LIKE CDSHW-F_NEW,
END OF ITAB.
DATA: OLD_OBJECTID LIKE CDHDR-OBJECTID.
FIELD-SYMBOLS: <F_OLD>, <F_NEW>.
SELECT * FROM EKKO WHERE EBELN IN XEBELN AND
LIFNR IN XLIFNR.
CLEAR CDHDR.
CLEAR CDPOS.
CDHDR-OBJECTCLAS = 'EINKBELEG'.
CDHDR-OBJECTID = EKKO-EBELN.
PERFORM GETCHGDOCS.
ENDSELECT.
IF SUDATE = 'X'.
SORT ITAB BY UDATE EKKEY-EBELN CHANGENR EKKEY-EBELP
EKKEY-ETENR.
ELSEIF SNAME = 'X'.
SORT ITAB BY USERNAME EKKEY-EBELN CHANGENR EKKEY-EBELP
EKKEY-ETENR.
ELSE.
SORT ITAB BY EKKEY-EBELN CHANGENR EKKEY-EBELP EKKEY-ETENR.
ENDIF.
LOOP AT ITAB.
CLEAR: INDTEXT, EKKEY.
CASE ITAB-CHNGIND.
WHEN 'U'.
INDTEXT(50) = ITAB-FTEXT.
INDTEXT+51 = TEXT-020.
CONDENSE INDTEXT.
WHEN 'D'.
INDTEXT = TEXT-021.
WHEN 'E'.
INDTEXT(5) = ITAB-FTEXT.
INDTEXT+51 = TEXT-021.
CONDENSE INDTEXT.
WHEN 'I'.
INDTEXT = TEXT-022.
ENDCASE.
RESERVE 4 LINES.
IF WCHANGENR NE ITAB-CHANGENR.
WCHANGENR = ITAB-CHANGENR.
EKKEY = ITAB-EKKEY.
WRITE:/ ITAB-UDATE UNDER 'Change Date',
ITAB-UTIME UNDER 'Time',
ITAB-USERNAME UNDER 'User Name',
ITAB-EKKEY-EBELN UNDER 'PO No',
ITAB-EKKEY-EBELP UNDER 'Item',
ITAB-EKKEY-ETENR UNDER 'Sch No',
INDTEXT UNDER 'Changes'.
ELSEIF ITAB-EKKEY NE EKKEY.
WRITE:/ ITAB-EKKEY-EBELP UNDER 'Item',
ITAB-EKKEY-ETENR UNDER 'Sch No',
INDTEXT UNDER 'Changes'.
ENDIF.
CASE ITAB-CHNGIND.
WHEN 'U'.
ASSIGN ITAB-F_OLD(ITAB-OUTLEN) TO <F_OLD>.
ASSIGN ITAB-F_NEW(ITAB-OUTLEN) TO <F_NEW>.
WRITE: / TEXT-023 UNDER 'Changes',
<F_OLD>.
WRITE: / TEXT-024 UNDER 'Changes',
<F_NEW>.
WHEN 'E'.
ASSIGN ITAB-F_OLD(ITAB-OUTLEN) TO <F_OLD>.
WRITE: TEXT-023 UNDER 'Changes',
<F_OLD>.
ENDCASE.
SKIP.
ENDLOOP.
TOP-OF-PAGE.
WRITE:/ SY-DATUM,SY-UZEIT,
50 'P U R C H A S E O R D E R H I S T O R Y',
120 'Page', SY-PAGNO.
WRITE: / SY-REPID,
60 'Purchase Orders Changes'.
SKIP.
ULINE.
IF SUDATE = 'X'.
WRITE:/001 'Change Date',
014 'Time',
024 'User Name',
038 'PO No',
050 'Item',
057 'Sch No',
065 'Changes'.
ELSEIF SOBID = 'X'.
WRITE:/001 'PO No',
013 'Item',
020 'Sch No',
028 'Change Date',
041 'Time',
051 'User Name',
065 'Changes'.
ELSE.
WRITE:/001 'User Name',
015 'Change Date',
028 'Time',
038 'PO No',
050 'Item',
057 'Sch No',
065 'Changes'.
ENDIF.
ULINE.
FORM GETCHGDOCS.
CALL FUNCTION 'CHANGEDOCUMENT_READ_HEADERS'
EXPORTING
DATE_OF_CHANGE = CDHDR-UDATE
OBJECTCLASS = CDHDR-OBJECTCLAS
OBJECTID = CDHDR-OBJECTID
TIME_OF_CHANGE = CDHDR-UTIME
USERNAME = CDHDR-USERNAME
TABLES
I_CDHDR = ICDHDR
EXCEPTIONS
NO_POSITION_FOUND = 1
OTHERS = 2.
CHECK SY-SUBRC EQ 0.
DELETE ICDHDR WHERE CHANGE_IND EQ 'I'.
CHECK NOT ICDHDR[] IS INITIAL.
LOOP AT ICDHDR.
CHECK ICDHDR-UDATE IN XUDATE.
CHECK ICDHDR-USERNAME IN XNAME.
CALL FUNCTION 'CHANGEDOCUMENT_READ_POSITIONS'
EXPORTING CHANGENUMBER = ICDHDR-CHANGENR
IMPORTING HEADER = CDHDR
TABLES EDITPOS = ICDSHW
EXCEPTIONS NO_POSITION_FOUND = 1
OTHERS = 2.
CHECK SY-SUBRC EQ 0.
LOOP AT ICDSHW.
CHECK ICDSHW-TEXT_CASE EQ SPACE.
MOVE-CORRESPONDING ICDSHW TO ITAB.
MOVE-CORRESPONDING ICDHDR TO ITAB.
MOVE ICDSHW-TABKEY+3 TO ITAB-EKKEY.
APPEND ITAB.
ENDLOOP.
ENDLOOP.
ENDFORM.
END OF PROGRAM
Regards,
Satish

Planned Order to Purchase Order report in SAP

Dear All
The Business process is Planned Order - Converted to Purchase Requsition - Converted to purchase order .
Is there any report in SAP , which shhows the direct link between Planned order to Purchase Order ?
Regards
Shyam

I have never seen a standard report, build a query based on tables PLAF, EBAN and EKET should be involved

Purchase requsition and Purchase order Price Changes

Hi All,
When purchase requsition(XXXXXXXX) is converted in to a purchase order through ME 59N(YYYYYYYYYY),after converting in to a purchase order i will change the purchase order price to a new value.
How can i track the price changes for a purchase order that is converted from a purchase requsition.(i know i can see the changes to a PO,under item changes for PO)
Is this data is stored in any table?
with regards,
Amogh

Hi,
this change is not captured, because the price is being changed at the point of the PO creation and so there will be no record in the header or item changes option (the system does not see anything as being changed because this is a creation of a new PO).
The price from the requisition is merely a suggestion and it is not meant to be a purchase price anyway (it is designed to be used to value the requisition for the release strategy).
I know that you can configure the system to pass this req "price" to the PO, but it is not the same price and so you will not find the type of controls that you would expect.
In many cases a simple ABAP is written that reads POs that have a reference requisition and the ABAP compares the prices and reports on those that exceed a tolerance (either hard coded in the program or held on a new table in SAP).
None of this is standard SAP but it is something that many people create to handle the situation where the user enters the requisition at a deliberately low value to get it through the release strategy.
Steve B

URGETNT: REGARDING Purchase Requsition Approval tables

hi,
I am making a report on purchase requsition and i have to display the details of which person has approved it and its date of approval. can anybody tell me which are the tables used in it to display it,example :-
1st Approval - Name of d person Date of Approval
2nd Approval - Name of d person Date of Approval
3rd Approval - Name of d person Date of Approval
Final Approval - Name of d person Date of Approval
this type of details i want to display in my report. if anybody gives me tables and details about it to make d report ,he or she will be definately REWARDED...
Currently i am using table EBAN,EBKN ..
Regards,
Ric.s

Use these table to see who released and description
T16FC - Release code for particular release group
T16FD - Description for Release code
T16FG - Release Groups
T16FH - Descriptions of Release Groups
T16FK - Release Statuses
use BAPI to get release information for PR .
BAPI_REQUISITION_GETRELINFO.
reward points if useful.
Regards,
Vimal
Message was edited by:
 Vimal Kumar

Purchase Analysis Report

Hi Experts
When I Run Purchase analysis report in SAP Business One 8.8 under individual vendor view the Open A/P Invoice (not done Payment) sowing 0.00 in the Applied amount and the purchase amount is showing negative value bacuse it is a credit memo - which is correct.
But when I run the same report in my customer site who are running SAP B1 2005 PL 43, they are not seeing 0.00 in the applied amount instead they are seeing the same negative amount which is displayed in the purchase amount.which is not correct.
Please assist me
Thanks and regards,
Vinodh
Edited by: Paul Finneran on Oct 15, 2009 12:36 PM

Hi Vinodh,
You may check these threads to see if they have anything related to your question:
Re: Purchase Analysis Report
Purchase Analysis Report not shown.
cant see Purchase analysis report of standard SAP B1
Thanks,
Gordon

Purchase Order Report

When Iam trying to take Purchase Order report,
Fields in PO Report are as follows:
Posting date, Purchase Order number,Vendor Name, Item Name, Qty, Unit Price, Total Price, & Status.
For eg:
PO Num 100 contains 5 Items, Out of which Goods Receipt PO has been raised for 3 Items. and Goods Receipt PO for remaining 2 items have not been raised.
In this case PO status is OPEN.
When iam generating PO Report, It shows Status for all the Items are OPEN. bcoz status for the PO is OPEN.
I want the report to show the status is Closed for the Items for which Goods Receipt PO has been raised. and similarly status must be OPEN for the items for which Goods Receipt PO has not raised. ( PO number is same ).
Your answers will be very helpfull.
Thankyou.

Hi,
I have created a Column in Purchase Order Screen and i have given two options by name Open/Close.
I have Created new field by going into...................... Path: ToolsUserdefined FieldsManage User defined fieldsmarketing documentsrows.
And i have selected check box set valid values for fields and i have given Open and Close Options.
This is effecting in new Purchase Orders which iam creating from now. But it is not reflecting in Purchase docs which i have created earlier.
So Please let me know what to be done inorder to reflect this change in all Purchase Order Doc's.
Your Answers will be very much helpfull.
Thankyou.

Purchase Register report in SAP BI

Dear All,
Please suggest me any standard Purchase Register report is available in BI or how to achieve this requirement in BI.
Please let me know process.
Thank
Regards,
Sai.k

Hi,
while there is always a new requirement, one needs to discuss with the functional consultants and find out which tables are being used which may fulfill the scenario. We also need to identify the list of characteristic and Keyfigues the client wants to analyze.
Also SAP Help is a good source to find more of a standard stream lined objects. Need to analyze if standard objects satisfy the requirement or customization is required.
Please perform the steps as Rama has suggested...
thank you

Purchase Register Report

Hi Friends,
I need to develop the Purchase Register Report with Vendor details, TIN number, Invoice details, E1 purchases with purchase base value and VAT and CST percentages. But Iam new to the Purchase module. I know the basic tables for purchasing. but can anybody guide me the tables for TIN number with VAT and CST percentages and how to proceed?
Thanking you in advance
Regards,
Murali

I don't know the fields but a few pointers that might be helpful:
1) Ask your functional analyst - it's part of their job to provide you with the field location or any guidance on that
2) At least someone should be able to point you where the fields are on the screen. Then you should be able to go the usual route - F1 -> Technical info, etc.
3) Respective functional forum might be a better place for such questions if for some reason p. 1 and 2 above are not feasible.
4) You can always use SQL Trace (ST05) to find where the information is being read from or written to. Start the trace, run the transaction, stop the trace and analyze the list. Voila - no need to ask anyone ever again.

Purchase Register Report issue

Hi,
I am working Purchase Register report.
In this, we have a PO with 10 Quantity. But at the time of MIGO we receive 5 qty out of 10.
Now how can we pick the amount according to 5 qty received from MIGO because we want show MIGO condition in our report not from PO.
What should be the table link for this...
Plz guide..

As per ur reference: -
In PO, Condition are like--- PO Qty is 10
Basic Amount..........1000
taxes.........................100
Freight.........................50
Other...........................20
and we have receive only 5 qty out of them, means all the condition amount will be 50%. like...
Basic Amount..........500
taxes.........................50
Freight.......................25
Other.........................10
all condition will be calculate according to qty 5 not for 10 as showing in PO..
I want to pick these condition. (according to 5 qty.)..
Now suggest...

Purchase Order Report In R12

Hi All,
I have created a purchase order report in R12,in the test instance the report is running perfectly for all the operating units but when i moved the rdf to the LIVE instance the report is running for only one operating unit(nothing is hard coded in the rdf) and the report says completed normar but after clicking on view output i am getting a msg as the output is not generated for the concurrent request.
After clicking on the view log i am getting an error msg as
Current NLS_LANG and NLS_NUMERIC_CHARACTERS Environment Variables are :
American_America.US7ASCII
Enter Password:
REP-0004: Warning: Unable to open user preference file.
Report Builder: Release 10.1.2.2.0 - Production on Tue Aug 19 16:41:18 2008
Help me in fixing this issue.
Thanks in advance

Somu,
chk note:
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=210795.1

Purchase register report problem

Hi experts - please help
we have a requirement to create a purchase register for material from PO- to Invoice.
we have PO number -> GRnumber -> Invoice number in our rows . In our keyfigures we have PO Quantity, PO value , GR quantity,GR Value, Invoice quantity and invoice amount .
Becoz of invoice and GR number relationship which is m: m in our report we see that the key figure values are showing up like
for 1 purchase order multiple line items , with multiple gr's, with multiple invoices , becoz of which we see PO quantity field showing like say if it is 30 for 1 PO it is showing 30 for all the invoice numbers in the report which not want , the same case is with Gr quantity and invoice quantity
PO.no / po item / gr no / inv number / po quanitity / po value
1000/10,20,30,40/1000/2000,3000,4000,5000/ 30,30,30,30,30/ 120,120,120,120,120
this way for 1 PO the report is showing same po quantity based on say if 10 invoices it is showing same P0 Quantity 10 times which is not want and the result row shows up (POvalue *10).
how to get rid of this situation..
please suggest any way if anyone has done a similiar report..
any documents related to such purchase register report is highly appreciated.
thanks & regards
krishna

Hi Krishna,
Your PO DSO will have records like this.
PO      Item    POquantity GR Quantity
PO1      1           100              35
Your GR DSO will have information as shown below.
GR Doc      Item      Posting date   GR Quantity   PO     PO Item
DOC1           1         01.07.2011          20            PO1       1
DOC2           1         10.07.2011          15            PO1       1
If the report is based on PO, ( Document date of PO ), then you can show information from the first DSO. If the user wants to have the details of GR documents that constitute GR quantity of 35, you can create a 'Jump to' report on the second DSO and in the RRI Connection map the PO and Item numbers.
This way you will be able to store the information at different granularity and combine them in reporting.
Hope this explains,
Thanks,
Krishnan

Purchase requsition report

Similar Messages

Maybe you are looking for