Auto PO using Purchase requisition

What are the steps and procedure for creating auto Po
I have tried the following at my end and failed
1) Material Master tick Auto Po
2) vendor master tick auto Po
3) source list
4) info record
5) ME59N,ME59
let me know what could be the possible problem i have commited cause of which my attempt was not succesful
I would like to create a Purcahse order with a non standard PO document type

Hi,
You can create auto P.O. from purchase requisition using assignment list.
Prerequisites for auto P.O.generation from assignment list are;
Sources must have already been assigned to the requisitions to be converted
Create P.O.using assignment list:
SAP Menu-Logisticsmaterial management-purchasing-purchase ordercreate-via requisition assignment list
Second Alternative is:
In automatic PO Generation, the system selects only those requisition items that satisfy the following conditions
:The Automatic Purchase Order indicator must have been set in the plant specific purchasing data of material master record
:The Automatic Purcahsr Order Indicator must have set in the purchasing data of the Vendor Master Record
: Valid Conditions must have been determined for the assigned source
Thanks,
Tushar Patankar

Similar Messages

Auto PO creation using purchase requisition

Hi,
I have tried the following steps for auto PO creation using purchase requisition.
i. Maintain Auto PO in Material master Purchasing view
ii. Select Automatic purchase order in Vendor master- Purchase data
iii. Maintain info-record
iv. Create PR through ME51
v. enable source determination during creation of PR
vi. Execute using ME59N
But Auto PO is creating with the same document type (e.g NB) which is used while creating purchase requisition (e.g NB). Following steps have done in SPRO.
1. SPRO - MM - Purchasing - purchase requisition - define document type
a. NB- PR document type LINK TO DI01- PO document type
2. SPRO - MM - Purchasing - Purchase order - Define document type
a. DI01- PO document type LINK TO NB- PR document type
3. There is no linking from NB - NB & DI01 - DI01 but still it is creating auto PO with document type NB iif requisition has been created with document type NB.
Please suggest on this . waiting for ur quick response.
Thanks...
ARATI.
Thanks!
Arati.
Edited by: Rakesh Gupta on Aug 20, 2009 11:00 AM

Hi
Please check the below thread
PR to PO via ME59 -Doc type issue
Thanks/karthik

How to delete no longer use Purchase Requisition

Dear Experts,
How to delete no longer use Purchase Requisition, thanks!
Wilson Hong

Hi Hong,
Hope you are looking for archiving PR. Please refer below link.
http://help.sap.com/saphelp_nw04s/helpdata/EN/8d/3e4c11462a11d189000000e8323d3a/frameset.htm
As per SAP you cant delete any data....you can only archive it.
Cheers
Arun.

Auto Purging of Purchase Requisition

Does anyone has any experience in auto purging of incomplete purchase requisition? Currently it can be done manually but we would prefer to run a concurrent program to do it periodically. Any information will be appreciated.

I have seen a PO program called "Purge System-saved Requisitions" (POXSSPG, execution method is SQL*Plus) - may be you can analyze it for your custom concurrent program.

Auto Creation of Purchase Requisition at Contract Level

Hi All,
I am having business requirement for creation of purchase requisition at contract level for third party Products.
Brief Business requirement
My client is in trading business of telecom product. They are sourcing product from different-different vendors and some of the product is also supplied by him self. As a business practice the system will automatically create an Installed base as per structured by business owner once delivered the product to end customer and also assigned warranty norms.
Once warranty is over then customer will called for contract since at the time sailing the product warranty will be liability of the company which in terns had some mutual contract with supplier (back to back replacement).
But once the same will come under service agreement/contract on that time they want installed base selection of components should had a functionality to segregate component based on vendor because they want to calculate % margin based on net sale value of the product.(e.g 10% of net sale Value 10,0000) not only that they also wants based on that system should automatically create Purchase requisition so that logistic department will take care of third party agreement part.
If any body come across with such kind of business scenario. Please share the proposed solution.
Regards
Neeraj

Hello,
I noticed that this question had status answered. We have the same requirement.... how did you resolve this?
Best Regards
Kristof

Help needed for enhancement in Purchase requisition

Hi all,
Our client uses me59n to generate PO's automatically using purchase requisitions.
Now, the requirement is ...
If net Purchase value is 0 in purchase requisition, then
Free(UMSON) field in Purchase order shoud be "checked".
lemme explain the steps a bit detail.
1. lots of purchase requisitions will be created in me51n.
2. Client will use me59n to generate PO's automatically, using Purchase requisitions.
3. purchase orders will be created.
3. Now, i am in search of a badi/user exit , which will
     if netPurchasevalue(gswrt) = 0
        (free)umson = X.
     endif.
so , i need a enhancement, which links both fields(gswrt) from purReq & (umson) in PO.
please lemme know if anybody have experience on similar issues earlier.
Regards.
santosh.

Hi,
Try implementing the BADI -ME_PROCESS_PO_CUST ...the method "PROCESS_ITEM" can be used to do the check that you want...
Thanks,
Renjith

Best Practice while creating Contract, Purchase Requisition, Purchase Order

Hi
What is the best practice with respect to Contract & Purchase Requisition?
IN T Code ME31K, there is a button Reference to PReq, meaning that we can create contract with using Purchase Requisition. (We have done the same)
While creating the Purchase Order using Contract, we could find Purchase Requisition reference in the Purchase Order; similarly when we created the Purchase Order using Purchase Requisition, we could find Contract reference in the Purchase Order.
I have done the following:
1. Create a Contract.
2. Create a Purchase Requisition
3. Assign Requisition and Create Purchase Order using T Code ME57.
4. Create Purchase Order
Here in this case we could find references of both Contract & Purchase Requisition.
I just want to know what Practice should we adopt / advise while creating Contract, Purchase Requisition. & Purchase Order?
Regards,

Hi,
In ME51N Screen, enter Contract number in the "AGREEMENT" TAB and if more items in the contract, you can mention the item number in the next TAB to the AGREEMENT TAB and then proceed with creating PR by entering other details. This TAB you can find in the 4th column from extreme right end of PR screen.
Regards,
Biju K
Edited by: Bijay Kumar Barik on Sep 10, 2009 2:23 PM

Generated a report which gives PR(Purchase Requisition) analysis using ALV.

hi experts,
please give me tables and fields for following report, and also exlain me briefly,
Generated a report which gives PR(Purchase Requisition) analysis using ALV.
thanks in advance,
radhakrishna

Hi
please find this report which link SO PO PR and Prd Ord and there status.
>
REPORT z_so_info.
TABLES: vbak, vbap, afko, afpo.
*Field catalog
TYPE-POOLS: slis.
DATA: lv_repid TYPE sy-repid VALUE sy-repid,
xfield TYPE slis_t_fieldcat_alv,
afield TYPE slis_fieldcat_alv.
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 1(25) text-002.
SELECT-OPTIONS: so_so FOR vbak-vbeln OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN END OF BLOCK b1.
SELECTION-SCREEN BEGIN OF BLOCK b2 WITH FRAME TITLE text-003.
PARAMETERS:
p_kunnr LIKE vbak-kunnr, " sold-to
p_kunwe LIKE vbak-kunnr. " ship-to
SELECTION-SCREEN END OF BLOCK b2.
*Constants
CONSTANTS: c_zor TYPE vbak-auart VALUE 'ZOR',
c_we TYPE vbpa-parvw VALUE 'WE',
c_ag TYPE vbpa-parvw VALUE 'AG'.
c_space TYPE space.
*Ranges
RANGES: ra_parvw FOR vbpa-parvw,
ra_kunnr FOR vbpa-kunnr.
*Tables
DATA: BEGIN OF gt_output OCCURS 0,
vbeln LIKE vbak-vbeln, " sales order number
posnr LIKE vbap-posnr, " SO item number
matnr LIKE vbap-matnr, " material number
sh LIKE vbpa-kunnr, " Ship-to
sp LIKE vbpa-kunnr, " Sold-to
lifnr LIKE ekko-lifnr, " Vendor
bstnk LIKE vbak-bstnk, " PO number
banfn LIKE vbep-banfn, " Purchase requi
po_st TYPE char30, " PO status text
pstyv TYPE vbap-pstyv, " Item catagory
aufnr LIKE afpo-aufnr, " Production Order
prd_stat TYPE string, " Prd order status
END OF gt_output.
DATA: wa_output LIKE gt_output.
FIELD-SYMBOLS: <fs_output> LIKE gt_output.
*Table for sales order and PO
TYPES : BEGIN OF gs_data,
vbeln TYPE vbak-vbeln,
posnr TYPE vbap-posnr,
pstyv TYPE vbap-pstyv,
matnr TYPE vbap-matnr,
END OF gs_data.
DATA: gt_data TYPE STANDARD TABLE OF gs_data,
wa_data TYPE gs_data.
*Table for Production Orders
TYPES: BEGIN OF gs_prd,
aufnr TYPE afpo-aufnr,
posnr TYPE afpo-posnr,
kdauf TYPE afpo-kdauf,
kdpos TYPE afpo-kdpos,
wepos TYPE afpo-wepos, "Goods Receipt Indicator
elikz TYPE afpo-elikz, "Delivery Completed Indicator
objnr TYPE aufk-objnr, "Object number
getri TYPE afko-getri, "Confirmed Order Finish Date
gltri TYPE afko-gltri, "Actual finish date
END OF gs_prd.
DATA: gt_prd TYPE STANDARD TABLE OF gs_prd,
wa_prd TYPE gs_prd.
*Table for partner data
TYPES: BEGIN OF gs_partner,
vbeln TYPE vbak-vbeln,
posnr TYPE vbap-posnr,
parvw TYPE vbpa-parvw,
kunnr TYPE vbpa-kunnr,
END OF gs_partner.
DATA: gt_partner TYPE STANDARD TABLE OF gs_partner,
wa_partner TYPE gs_partner.
TYPES: BEGIN OF gs_po,
ebeln TYPE ekkn-ebeln,
ebelp TYPE ekkn-ebelp,
vbeln TYPE ekkn-vbeln,
vbelp TYPE ekkn-vbelp,
END OF gs_po.
DATA: gt_po TYPE STANDARD TABLE OF gs_po,
wa_po TYPE gs_po.
TYPES: BEGIN OF gs_preq,
vbeln TYPE vbep-vbeln,
posnr TYPE vbep-posnr,
banfn TYPE vbep-banfn,
END OF gs_preq.
DATA: gt_preq TYPE STANDARD TABLE OF gs_preq,
wa_preq TYPE gs_preq.
TYPES: BEGIN OF gs_po_stat,
ebeln TYPE ekko-ebeln,
procstat TYPE ekko-procstat,
lifnr TYPE ekko-lifnr,
END OF gs_po_stat.
DATA: gt_po_stat TYPE STANDARD TABLE OF gs_po_stat,
wa_po_stat TYPE gs_po_stat.
*Field symbols
FIELD-SYMBOLS: <fs> TYPE tj02t-txt04,
<fs_temp> TYPE tj02t-txt04,
<fs_stat> TYPE char30.
START-OF-SELECTION.
PERFORM fr_build_range.
PERFORM fr_get_data.
PERFORM fr_build_fc.
PERFORM fr_output.
*& Form fr_get_data
text
--> p1 text
<-- p2 text
FORM fr_get_data.
*Get SO
SELECT avbeln aposnr apstyv amatnr
FROM vbap AS a
JOIN vbak AS b
ON avbeln = bvbeln
JOIN vbpa AS c
ON bvbeln = cvbeln
INTO TABLE gt_data
WHERE b~vbeln IN so_so
AND b~auart EQ c_zor "Only Sales Orders
AND c~kunnr IN ra_kunnr. "from selection screen
DELETE ADJACENT DUPLICATES FROM gt_data COMPARING vbeln posnr.
*get data of the production order
IF NOT gt_data[] IS INITIAL.
SELECT aaufnr aposnr akdauf akdpos awepos aelikz
b~objnr
FROM afpo AS a
JOIN aufk AS b
ON aaufnr = baufnr
INTO TABLE gt_prd
FOR ALL ENTRIES IN gt_data
WHERE a~kdauf EQ gt_data-vbeln
AND a~kdpos EQ gt_data-posnr.
ENDIF.
*Get partner data
IF NOT gt_data[] IS INITIAL.
SELECT vbeln posnr parvw kunnr
FROM vbpa
INTO TABLE gt_partner
FOR ALL ENTRIES IN gt_data
WHERE vbeln EQ gt_data-vbeln.
ENDIF.
*Get Purchase Order
IF NOT gt_data[] IS INITIAL.
SELECT ebeln ebelp vbeln vbelp
FROM ekkn
INTO TABLE gt_po
FOR ALL ENTRIES IN gt_data
WHERE vbeln EQ gt_data-vbeln
AND vbelp EQ gt_data-posnr.
SELECT vbeln posnr banfn
FROM vbep
INTO TABLE gt_preq
FOR ALL ENTRIES IN gt_data
WHERE vbeln EQ gt_data-vbeln
AND posnr EQ gt_data-posnr.
ENDIF.
IF NOT gt_po[] IS INITIAL.
SELECT aebeln aprocstat a~lifnr
FROM ekko AS a
JOIN ekpo AS b
ON aebeln = bebeln
INTO TABLE gt_po_stat
FOR ALL ENTRIES IN gt_po
WHERE b~ebeln EQ gt_po-ebeln
AND b~ebelp EQ gt_po-ebelp.
ENDIF.
*Move data to output table
LOOP AT gt_data INTO wa_data.
wa_output-vbeln = wa_data-vbeln.
wa_output-posnr = wa_data-posnr.
wa_output-pstyv = wa_data-pstyv.
wa_output-matnr = wa_data-matnr.
READ TABLE gt_po INTO wa_po WITH KEY vbeln = wa_data-vbeln
vbelp = wa_data-posnr.
IF sy-subrc EQ 0.
wa_output-bstnk = wa_po-ebeln.
READ TABLE gt_po_stat INTO wa_po_stat WITH KEY ebeln = wa_po-ebeln.
IF sy-subrc EQ 0.
wa_output-lifnr = wa_po_stat-lifnr.
CASE wa_po_stat-procstat.
WHEN '01'.
wa_output-po_st = 'Version in process'.
WHEN '02'.
wa_output-po_st = 'Active'.
WHEN '03'.
wa_output-po_st = 'In release'.
WHEN '04'.
wa_output-po_st = 'Partially released'.
WHEN '05'.
wa_output-po_st = 'Released Completely'.
WHEN '08'.
wa_output-po_st = 'Rejected'.
ENDCASE.
ENDIF. "inner read subrc
ENDIF. "outer read subrc
READ TABLE gt_preq INTO wa_preq WITH KEY vbeln = wa_data-vbeln
posnr = wa_data-posnr.
IF sy-subrc EQ 0.
wa_output-banfn = wa_preq-banfn.
ENDIF.
READ TABLE gt_prd INTO wa_prd WITH KEY kdauf = wa_data-vbeln
kdpos = wa_data-posnr.
IF sy-subrc EQ 0.
wa_output-aufnr = wa_prd-aufnr.
*get the purchase requisition for production order as well
SELECT SINGLE banfn
FROM ebkn
INTO wa_output-banfn
WHERE aufnr EQ wa_prd-aufnr.
*Get the status of the production order
PERFORM fr_get_prd_stat USING wa_prd-objnr
CHANGING wa_output-prd_stat.
ENDIF. " sy-subrc
READ TABLE gt_partner INTO wa_partner WITH KEY vbeln = wa_data-vbeln
parvw = c_we.
IF sy-subrc EQ 0.
wa_output-sh = wa_partner-kunnr.
ENDIF.
READ TABLE gt_partner INTO wa_partner WITH KEY vbeln = wa_data-vbeln
parvw = c_ag.
IF sy-subrc EQ 0.
wa_output-sp = wa_partner-kunnr.
ENDIF.
APPEND wa_output TO gt_output.
CLEAR: wa_data, wa_prd,wa_partner,wa_output.
ENDLOOP.
ENDFORM. " fr_get_data
*& Form fr_build_range
text
--> p1 text
<-- p2 text
FORM fr_build_range .
*Range for partner function
MOVE 'I' TO ra_parvw-sign.
MOVE 'EQ' TO ra_parvw-option.
MOVE 'SH' TO ra_parvw-low. " we
APPEND ra_parvw.
CLEAR ra_parvw.
MOVE 'I' TO ra_parvw-sign.
MOVE 'EQ' TO ra_parvw-option.
MOVE 'SP' TO ra_parvw-low. " ag
APPEND ra_parvw.
CLEAR ra_parvw.
*Range for ship-to and sold-to
MOVE 'I' TO ra_kunnr-sign.
MOVE 'EQ' TO ra_kunnr-option.
MOVE p_kunnr TO ra_kunnr-low.
APPEND ra_kunnr.
CLEAR ra_kunnr.
MOVE 'I' TO ra_kunnr-sign.
MOVE 'EQ' TO ra_kunnr-option.
MOVE p_kunwe TO ra_kunnr-low.
APPEND ra_kunnr.
CLEAR ra_kunnr.
ENDFORM. " fr_build_range
*& Form fr_build_fc
text
--> p1 text
<-- p2 text
FORM fr_build_fc .
sales order number
afield-fieldname = 'VBELN'.
afield-seltext_s = 'Sales #'.
afield-ref_tabname = 'VBAK'.
APPEND afield TO xfield. CLEAR afield.
sales ITEM number
afield-fieldname = 'POSNR'.
afield-seltext_s = 'Item #'.
afield-ref_tabname = 'VBAP'.
APPEND afield TO xfield. CLEAR afield.
Material Number
afield-fieldname = 'MATNR'.
afield-seltext_s = 'Material #'.
afield-ref_tabname = 'VBAP'.
afield-outputlen = 10.
APPEND afield TO xfield. CLEAR afield.
*Vendor Number
afield-fieldname = 'LIFNR'.
afield-seltext_s = 'Vendor Num.'.
afield-ref_tabname = 'EKKO'.
APPEND afield TO xfield. CLEAR afield.
ship-to-party
afield-fieldname = 'SH'.
afield-seltext_s = 'Ship-to'.
afield-ref_tabname = 'VBPA'.
APPEND afield TO xfield. CLEAR afield.
sold-to-party
afield-fieldname = 'SP'.
afield-seltext_s = 'Sold-to'.
afield-ref_tabname = 'VBPA'.
APPEND afield TO xfield. CLEAR afield.
*PO number
afield-fieldname = 'BSTNK'.
afield-seltext_s = 'PO NUM'.
afield-ref_tabname = 'EKKO'.
APPEND afield TO xfield. CLEAR afield.
*PO status
afield-fieldname = 'PO_STAT'.
afield-seltext_s = 'Step'.
afield-ref_tabname = 'zbacklog_v2'.
APPEND afield TO xfield. CLEAR afield.
*PO step status
afield-fieldname = 'PO_ST'.
afield-seltext_s = 'PO.Status'.
afield-ref_tabname = 'zbacklog_v2'.
APPEND afield TO xfield. CLEAR afield.
*Purchase requisition
afield-fieldname = 'BANFN'.
afield-seltext_s = 'Pur. Req.'.
afield-ref_tabname = 'VBEP'.
APPEND afield TO xfield. CLEAR afield.
*Item catagory
afield-fieldname = 'PSTYV'.
afield-seltext_s = 'Itm. Catg'.
afield-ref_tabname = 'VBAP'.
APPEND afield TO xfield. CLEAR afield.
*Prodcution Order number
afield-fieldname = 'AUFNR'.
afield-seltext_m = 'Prod.Order'.
afield-ref_tabname = 'AFKO'.
APPEND afield TO xfield. CLEAR afield.
*PRODCUTION status
afield-fieldname = 'PRD_STAT'.
afield-seltext_s = 'Prd. Step'.
afield-ref_tabname = 'zbacklog_v2'.
afield-outputlen = 20.
APPEND afield TO xfield. CLEAR afield.
*PRODUCTION step status
afield-fieldname = 'PRD_ST'.
afield-seltext_s = 'Prd. Status'.
afield-ref_tabname = 'zbacklog_v2'.
APPEND afield TO xfield. CLEAR afield.
ENDFORM. " fr_build_fc
*& Form fr_output
text
--> p1 text
<-- p2 text
FORM fr_output .
CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
EXPORTING
i_callback_program = sy-repid
I_CALLBACK_PF_STATUS_SET = ' '
I_CALLBACK_USER_COMMAND = ' '
I_STRUCTURE_NAME =
IS_LAYOUT =
it_fieldcat = xfield[]
i_default = 'X'
i_save = 'A'
TABLES
t_outtab = gt_output
EXCEPTIONS
program_error = 1
OTHERS = 2.
ENDFORM. " fr_output
*& Form fr_get_prd_stat
text
-->P_WA_PRD_OBJNR text
FORM fr_get_prd_stat USING p_objnr CHANGING p_prd_stat.
DATA: lt_status TYPE STANDARD TABLE OF jstat,
wa_status TYPE jstat,
lv_status TYPE tj02t-txt04,
lv_temp2 TYPE char5,
lv_buff TYPE string.
CALL FUNCTION 'STATUS_READ'
EXPORTING
client = sy-mandt
objnr = p_objnr
only_active = 'X'
TABLES
status = lt_status
EXCEPTIONS
object_not_found = 1
OTHERS = 2.
LOOP AT lt_status INTO wa_status.
IF wa_status-stat(1) EQ 'I'.
SELECT txt04 FROM tj02t
INTO lv_status
WHERE istat EQ wa_status-stat
AND spras EQ 'E'.
ENDSELECT.
lv_temp2 = lv_status.
CONCATENATE lv_temp2 p_prd_stat INTO p_prd_stat
SEPARATED BY ','.
ENDIF.
CLEAR: wa_status, lv_status, lv_temp2.
ENDLOOP.
lv_buff = p_prd_stat.
*Status of Production Order
IF lv_buff CS 'CRTD'.
p_prd_stat = 'Not Active'.
ENDIF.
IF lv_buff CS 'REL'.
IF lv_buff CS 'GMPS'.
p_prd_stat = 'Printed In Prod'.
ELSE.
p_prd_stat = 'Printed'.
ENDIF.
ENDIF.
IF lv_buff CS 'TECO'.
p_prd_stat = 'Technically Compt.'.
ENDIF.
ENDFORM. " fr_get_prd_stat
>

Using MD42 purchase requisitions creating instead of schedule lines

Hi PP Guru's
Can any one help while using MD42/MD43 purchase requisitions generating instead of schedule lines.
MRP Type :M0
what are the required settings for this..?
please help me to solve this issue.

Hello
This is a link to a note and you need to have access to SAP service marketplace.
Please ask your system admin/basis and he will be able to provide you an user.
The following information from the note should be relevant for you:
If the flag "SC Vendor" is checked on the scheduling agreement, this source list entry will only be considered on a third-party order processing scenario with MRP areas.
If you are not using MRP areas, this source list entry will not be considered and the vendor/schedule agreement will not be selected. This setting can be found on transaction ME32, on the menu path "ITEM" - "MORE FUNCTIONS" - "DELIVERY ADDRESS". See note 214298 for more details.
BR
Caetano

Enter short text error when creating a purchase requisition using ME51

Hello
I would be grateful if someone can help. I am currently trying to raise a purchase req using ME51. The purchase req is for one item so i enter details of this item on line 1. However when i try to save the purchase req i get an error message stating "enter short text" on line 3 and it does not let me continue. Line 3 however does not contain any item information so i dont understand why i am getting this error message.
Another user created the same purchase req and it worked fine for them so i am not sure why i am getting this message.
I would be grateful if you can please help.
Thank you
Regards
Bindi

Syed
I have tried logging off and logging back in and still having this issue.
Jurgen
No im only having this problem in a ME51 creating purchase requisitions and not in a CATT or any batch input recording
Regards
Bindi

Creation of Purchase Requisition using BAPI

Hi Experts
Can anyone provide me the sample code for creating Purchase Requisition using BAPI
Thanks in advance

Hi siri,
go throught this, hope
http://www.erpgenie.com/abap/bapi/example.htm
Also refer to the following links..
www.sappoint.com/abap/bapiintro.pdf
www.sap-img.com/bapi.htm
www.sap-img.com/abap/bapi-conventions.htm
www.planetsap.com/Bapi_main_page.htm
www.sapgenie.com/abap/bapi/index.htm
Checkout !!
http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
http://techrepublic.com.com/5100-6329-1051160.html#
http://www.sap-img.com/bapi.htm
http://www.sap-img.com/abap/bapi-conventions.htm
http://www.sappoint.com/abap/bapiintro.pdf
http://sap-img.com/bapi.htm
Thanks
Naveen khan
Message was edited by:
Pattan Naveen

MM: Purchase requisition line Items - How many line items can we use

Hi all,
1. Purchase requisition Line items (How many line items can we use?), is there any restrictions.
2. While creating PO with only one tax code for the related PR to input Tax code (without selecting line Items).
Regards,
Sudheer

Hi
There is no limitation for number of items in PR.
Tax code is always applicable for individual item only.It cannot be selected form the whole PO.
Regards
Dev

Create Purchase Order with reference to Purchase Requisition using BAPI's

Hello Experts,
I need to create a Purchase order with reference to a Purchase Requisition.
All the above has to be done by using BAPI's.
For creating PR, I am using BAPI_REQUISITION_CREATE.
and for PO, I am using BAPI_PO_CREATE.
I am not able to use the requistion number in the PO. BAPI throws the following exception
"Requisition 1014396 00010 not selectable"
"Document contains no items"
Query's:
1. Do I need to release the PR for using it in PO?
2. If so how can I work with the "BAPI_REQUISITION_RELEASE_GEN" to release PR?
I have tried using the BAPI getting the following error "Release outside filed of responsibility".
Please help I am in critical Postion...
Thanks,
Suma

Hi Meenakshi,
When, I try to release error I am getting the following the error " Purchase Requisition can not be released".
Is this problem because of authorization or data issue?
Thanks
Suma

Mass Deletion Of Purchase Requisitions Without Using LSMW

Hi,
We would like to delete huge volume of PR generated through MRP. Deleting PR will be a frequent activity in our business scenario. Since the person responsible for MRP is not very much conversant with LSMW, we want to avoid using LSMW.
I tried with MEMASSQR. But 'deletion indicator' field is not available in the field list.
Is there any method through which I can carry out mass deletion of PR?

Hi,
I've tryed this from Manish Kumar Agarwal :
Go to SM30 enter the table MASSFLDLST
then create the new entry object type = BUS2105
Table name = EBAN Field:- "EBAKZ" (Purchase requisition closed)
Then run MEMASSRQ and select this field and then PRs after tnat on next page you will get option like film:- carry out mass changes go ahead with it.
But strangelly, it doesnt appear in the memassrq... any idea?

Purchase Requisition Auto Close

When a Standard Purchase Requisition get auto closed. although we have created Purchase Order from Requisition and Delivered items to locations but still it is in Open Status.
Edited by: Abdul Wasi on May 24, 2012 12:02 AM

Abdul Wasi wrote:
Hi Mahendra,
As Items are Already places on PO and the Purcahse Order is fully Received and also Invoicing is done. now the PO status is finally close. Same as like PO why the Requisition is not getting Finally Close status.
Thanks. As far as i know..This is the what provided functionality is..
If you think requisitions should also be closed...
Please Log SR or Enhancement request with Oracle :)
Thanks
Mahendra

Auto PO using Purchase requisition

Similar Messages

Maybe you are looking for