Purchase Requisition - Standard Content

All, do you know if there is any standard content provided by SAP regarding Purchasing Requisitions? I am looking for some basic data in PReq. I looked at help.sap.com but, all i could find was Purchasing cubes. I want to make sure that SAP does not provide any before creating a custom datasource.
Thank

Hi
I dont think there are any standard datasource which brings PR details.
But I think you can enhance the Purchasing Item datasource to brint the PR number and qty etc into it and then use the purchasing cube.
Regards,
Vineeth

Similar Messages

Overall purchase requisition's Workflow : mechanism of release code

Hi all,
i need to implement Overall purchase requisition standard workflow ; i need to have 2 actors for process's validation, so i set release code like this :
01 - ACTOR1
02 - ACTOR2
The workflow is launched, the ACTOR1 received a work item in his workplace, whe he execute the work item, the transaction ME54N is launched. Well. But the ACTOR1 can a decision for him but also for ACTOR2, why ? the process is not good for me. If ACTOR1 has taken a decision the workflow of release code 01 is finished. An other workflow is launched for release code 02, when the ACTOR2 go to the transaction ME54N he can take a decision for his relase code but he can also cancel the previous decision of ACTOR1, it's not good for me, can you explain to me ?
Thanks for help.
Cheers.

Interesting solution using the user-exit.
I just finished modifying the delivered overall purch req approval WF. I needed to add a few fields for reporting so I created virtual attributes via delagation on BUS2105. I created approval and initiator agent attributes and email addresses. It works fine and I don't have maintain any further code other than what is in my business object which I can use again and again.
Many roads on the way to Rome

Standard Smartform printing purchase requisition through - ME51N / ME52N

Hi Experts,
we are trying to build functionality to print Purchase requisition through transaction ME51N / ME52N / ME53N. we have created a print button on Customer data screen for that. Now we are looking for any standard smartform or script which can be used for printing Purchase requisition.
Please provide me some pointers for the same.
There is print button avalable at item level of purchase requisition. but it will not print header records. i am not able to find this form in system also. how can i find this form?
thanks

>
rajpal sehrawat wrote:
> Hi,
>
>
> Header records means we might provide some header level information like PR number , short text and logo. Currently we are able to print only line items present in the ALV grid.
>
>
> we are looking for some similar form which can be enhanced.
>
>
> thanks
actually the PR number is a line item field - it comes out of table EBAN. You would have to store the logo someplace else, since it does not belong to the PR (EBAN) -> neither header nor item, but is 'simply' graphics stored elsewhere in the database.
I wouldn't know of any form in MM-PUR which you could easily adapt to printing PRs (and have never before heard of the need to print them) - so you will have to do a custom abap. Since there is no possibility to maintain NACE for PRs (it's simply not available) - I wouldn't know where you could use a smartform/sapscript ... that custom abap is all you can do ...

Standard Purchase Price List @ Purchase Requisitions

Hi everyone
I am trying to find a way to maintain a standard purchase price list that is used at the Purchase Requisition creation.
Our sourcing managers will negotiate prices with vendors. Once these prices are set, any purchase requisition created should default to this purchase price.
Using PIR did not work - maybe some configuration is required.
I do not want to define contracts - because in essence there is no contract.
Can someone help..
Thanks

No, nothing else than standard or moving average price field from material master (depends on price control).
if you want any other price in the PR then you may need to develope an individual solution

Purchase requisition to be created when Inspection lot is released

Hello,
A Purchase Requisition need to be created (for external services) at the time of Inspection lot generation. I tried using the Inspection Plan operation control key with 'Extenally processed processing' with Info record, Pur Org details.. etc. Still, when Inspection lot is released, Purchase requisition is not generated.
Any clue?
Thanks
JK

Can you explain your business scenario.
In standard QM you cannot create purchase requisition from inspection lot creation.
1. You can use Userexit QAAT001 to create purchase req if needed.
2. Refer to "external processing in QM' if you want to create Purchase req during production.
http://help.sap.com/saphelp_46c/helpdata/en/42/75f1e256cc11d1896a0000e8323c4f/content.htm

Purchase Requisition transfer from ECC to SRM via XI

Experts,
Please let me know if you have any information on the following issue:
Environment : SRM 7.0, ECC ep4, Extended Classic scenario
The purchase requisitions have been created in ECC and released. I believe in SRM 7.0 the PR's get automatically transferred to SRM Sourcing cockpit via XI from ECC.
One PR was pushed manually from SMQ1(Outbound queue ) in ECC and this failed due to a login issue in XI.
The XI was using the interface PurchaseRequestERPSourcingRequest.
My question is
1. When the PR is released in ECC, where to check if the PR is pushed to XI. Do we need to schedule a job? When I checked SMQ1 (outbound queue, the queues are empty)
2. Do we need to define the partner profile in ECC for XI in We20. If so, then what message types to use for the IDocs going from ECC to XI.
2. Do we need to configure the interface PurchaseRequestERPSourcingRequest in XI to map the incoming PR from ECC.
3. In transaction SXMB_moni in XI I am not able to pull the XML messages. What options options do I need to
set to pull the messages that errored out.
Thanks,
Scott.

Hi All,
Hope this helps you for XI configuration
Importing Business Scenarios for Sourcing
In this section, you transfer the business scenario Strategic Sourcing from the SAP Integration Repository, generate it, and activate it.
Prerequisites
You have:
Defined the business systems for SAP Supplier Relationship Management (SAP SRM) and SAP ERP in the SAP System Landscape Directory. For more information about SAP NetWeaver Process Integration (SAP NetWeaver PI), see the SAP Marketplace
Imported the SAP NetWeaver PI content for SAP SRM into the SAP Integration Repository.
Procedure
Log on to the SAP Netweaver PI system.
Choose Integration Builder: Configuration.
In the left pane, select the Objects tab.
Choose Service Without Partner Business System .
Right-click to display the context menu and choose Business Systems Assign Business System . This opens the wizard.
Choose Continue. The wizard guides you through the required steps.
Create the business system for both SAP SRM and ERP (you can bypass this step if the business system is already setup).
Select a business system.
You can create communication channels either manually or automatically. You can create them automatically here. In this case, the systems are applied from the SAP System Landscape Directory (SLD). Channels must be complete in terms of URLs and authentication information.
Choose Finish, and then choose Close.
11. On the main screen, choose Tools Transfer Integration Scenario from Integration Repository . This opens a wizard.
Choose Name using input help SE_Sourcing_Enhancements
Choose Continue. The scenario name is SE_Sourcing_Enhancements.
Choose Finish and then choose Close. The Business Scenario Configurator opens automatically.
Choose Component View.
The Select Component View window opens.
Choose Apply.
Choose Assign Services. The Assign Services to Application Component window opens.
Press F4 to retrieve the available services.
Choose Assign.
Select the related service and choose OK.
Assign a business service to all roles.
Choose Configure Connections.
Select the connections from the Service Assignment tab.
Press F4 in the Communication Channel field.
Select a communication channel. This channel must be of type XI.
Note
If the systems are applied from the SAP Landscape Directory, the Integration Builder automatically creates the communication channels.
If the systems are not applied from the SAP Landscape Directory, you create communication channels manually. To do this choose an existing service and then Communication Channel using context menu New. You must assign a communication channel for each connection.
End of the note.
Choose OK and then choose Apply.
Choose Generate to open the Create Configuration Objects window.
Choose Simulation, then Generate, then mark all in the list Scope of Generation.
Choose Start to generate a log. Check the log for errors and save it if required.
In the Close Integration Scenario screen, choose Apply.
In the left pane, select the Scenarios tab; your scenario has been added.
In the left pane, select the Change List tab.
Expand the Standard Change List.
Right click on the scenario name SE_Sourcing_Enhancements and choose Activate.
Regards
Sam

About Purchasing Requisition Extraction

Hi,buddies:
Is there any business content or other methods to extract the Purchasing Requisition from SAP R/3? or is there any how-to guide to solve this problem except General Datasource?
Your answer will be highly appreciated.

Hello, You will locate the Datasource on ECC-> RSA5 -> NODESNOTCONNECTED -> IS-DFS-BW
Now you can activate, then replicate Datasources on BW, and then test (or you can just test the Datasource on ECC -> RSA3 to first see what kind of data you will receive.
After that, you will have to activate Standards objects to receive this data on BW.

Error in creation of purchase requisition

Hello Sap Guru,
When we are trying to create a purchase requisition under t.code ME51N, we are getting error message "enter valuation price"?
If anyone can please explain the reason & solution of this error.
Thanks In advance
Deepak Garg

{code)When we are trying to create a purchase requisition under t.code ME51N, we are getting error message "enter valuation price"?{code)
Hi,
it is sap standard process when you create PR and if material master record exist the price is automatically taken from the valuation price field. if record not exist enter lum sum price of requested material price.
When purchase guy create po with reference to Pr they can change valuation price also.
In custommization for Purchasing under Purchase Requisition -> Define Screen Layout at Document Level, you can set price and price unit. The Valuation price field can be set as a mandatory or optional input field.

Purchase requisition report.

Hi,
      Is there any standard report for purchase requisitions, showing purchase requistion number, user created, plant and some basic stuff like that.
      Can anyone pls assist me with this.
thanks in advance,
Ravi Boppana

Hi,
     ME5A has pretty much all the information we are looking for. Thank you very much. But is there a way that we can restrict users to see their own requisitions. Ideally we dont want a user to see requisitions created by other users.
    If there is some way like that, it would be perfect for our situation.
    Thank You very much
Ravi Boppana

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
>

Purchase Order and Purchase Requisition

Hi To All,
my customer while using tcode me2m hase extracted purchase order opened since 2007. now he want to close all this order and settle them to zero. this operation should be done also for the purchase requisition.
there is a standard way to do this? if not any idea?
thanks
C.

Hello
Just by doing
In the PO line item level details, activate DELIVERY COMPLETED check box.
system will not close po from GR
U will have to check what is the gr qty did till date
and update the po with the same qty manually
eq
if po qty is 50 and total gr done till date is 40
change the PO qty to 40 and save
this is the way u can shot close the po
Which effects has the "delivery completed" indicator?
The purchase order item is considered closed, even though the total quantity may not have been delivered.
Although a further delivery is not expected, it is still possible.
At the time of the next goods receipt, the system suggests the item as unselected.
The purchase order item can be deleted, even if the total quantity was not delivered.
Although the "delivery completed" indicator is not set, a purchase order item is still considered closed if the full quantity has been delivered. In this case, the "delivery completed indicator" is not required.
The system allows to make further goods receipts. Why?
Answer
See note 16239 and 856279
hope this helps
Edited by: Umakant Bhangale on Oct 11, 2010 5:20 PM

How to change an Existing Purchase Requisition Document in MM.

Hi Folks,
I want to write a program to change a existing Purchase Requisition in MM.
I found two BAPI's BAPI_PR_CHANGE and BAPI_REQUISITION_CHANGE , which could be used to change PR document in ECC.
I have following question:
1) why we have two seprate BAPI's for changing PR.
2) Do we need to use both BAPI's to change PR, depending on what value we are trying to change.
3) Is it optional to use any of these two BAPI's
Or do we have any other way to implement this PR change process.( Bcoz of when i tried to debug standard PR change process, none of these two BAPI's has been called)
Which FM or method is called when, we try to change and save PR document manually.
I would appriciate, if some one has any sample code to implement this PR change process.
Regards
PG
Edited by: PG on Aug 23, 2010 3:10 PM

>
PG wrote:
> I have following question:
> 1) why we have two seprate BAPI's for changing PR.
BAPI_REQUISITION_CHANGE is the older BAPI, the one based on the older ERP transaction (ME5x family), while BAPI_PR_CHANGE is the newest one, referring to the "recent" Enjoy transaction (ME5xN family).
They both satisfy you task probably, but if you can chose, I'd go for BAPI_PR_CHANGE.
>
PG wrote:
> 2) Do we need to use both BAPI's to change PR, depending on what value we are trying to change.
> 3) Is it optional to use any of these two BAPI's
You can use the first or the second one, it's indifferent. The newest one will also trigger user exits from ME5xN family. Which transactions are used by the users on the ERP? Choose with regards to the transactions used during the normal activity.
>
PG wrote:
> Or do we have any other way to implement this PR change process.( Bcoz of when i tried to debug standard PR change process, none of these two BAPI's has been called)
Normal PR change operativity doesn't use BAPI. BAPIs are used to create/modify docs from "external" systems (it's not properly true, but let assume it), they provide a simple interface to populate with PR data and the process of creation/modification will trigger every check/userexit already defined for the standard transactions on the ERP.
In example, suppose that in ME51N you defined a custom check in a specific userexit which don't allow an user to create a material item which have odd quantity (odd example, I know ). Then using BAPI_PR_CREATE you will not be able to create a PR with items with odd quantity, because the same check will be executed.

How to copy sales order item text in to purchase requisition

Hi Experts,
We enter text for the sales order items in the sales order item details.
we have done settings for the purchase requision to copy text from sales order into purchase requisition and this works for purchase requisitions automatically created from sales order.
we need to get text from sales order to be copied in purchase requisitions which are created by converting the planned order.
we have tried SPRO settings SPRO->Materials Management>purchasing--->text for purchase requisition.
but this settings does not works for Pur Req. created by converting the planned order.
is this because planned order does not have segment for text like sales order and purchase requisition?
Please let me know if it is possible through standard SAP or with the lease development, any help will be appreciated.
Thanks
Anand

Hi Rajesha,
Thanks for your reply, some of the items in sales order are procured externally by us and our customer maintains text related to price and specification in the item details of the sales order, MRP creates planned order for these materials and these planned orders are always converted in pur requisition, we want that text from the sales order item details should be copied in to the purchase requisitions converted from planned orders.
is there any user exit which can be called at the time of saving a purchase req or user exit for converting planned order in to pur req.?
if there is any such exit available, then I think I can read the pegged requirement of the planned order where sales order item will be found then read the text in the item then copy this text in pur req then save pur req may work.
but this will be a bulky development, please let me know if we can shorten the development.
Thanks again
Anand

Sales order item text to purchase requisition

Hello Team,
we have scenario in which we create the sales order and while creating the sales order we put the production memo text at the item level under text tab in it.
We have define copying rules for the production memo text under PR customizing text types to get it copied from the sales order. But when we are creating the PR for the sales order then the production memo text is not flowing into the purchase requisition.
I checked some OSS notes and found recently released note 448814 which says that text does not gets copied to PR when PR is created manually from the sales order ( question no 24 and 25 in the note ) due to technical reasons and it gets copied only when the PR gets created directly from the sales order.
Could you please help me to know if this is standard problem or some other settings exists and if anyone have other solution to it. ?
Thanks and Regards,
Deepak Gupta

Hi Jurgen,
Thanks for the reply. I was expecting to know if others have came across similar kind of issue and after following up with SAP, if they have provided some other solution.
Thanks
Deepak

Delivery schedule in purchase requisition should be copied to RFQ

Hi
I had a requirement to maintain delivery schedule in purchase requisition which should be copied to RFQ.
Since standard SAP is not supporting this feature, we maintained delivery schedule for each line item of PR in a custom screen/development.
Now iam not able to call the same data to RFQ screen through a BAPI / Enhancement.
Appreciate your valuable comments on above issue.
Thanks
Deepak

Not sure what you expect from us functionals here in MM.
You have built a function yourself that is not available in standard , and now you expect that other transactions are just taking this into consideration? Of course you need to modify the entire process chain if you create new functionality which is not foreseen by SAP's standard.

Purchase Requisition - Standard Content

Similar Messages

Maybe you are looking for