Purchase Order Read only/inquiry Responsibility

HI,
We are using R12.04, I want to create a new responsibility for purchase order inquiry/view only. User can only view purchase order details and but can't update details.
I have restricted responsibility to Create New PO but still user can update PO detail. I have excluded all relevant functions from standard responsibility to restrict new responsibility to read only but still i can update PO information.
I found metalink note for 11i (POXPOEPO - New Responsibility with View Purchase Orders Functionality Allows Users to Make and Save Changes [ID 169131.1]).
Can anyone explain, how can i achieve this goal, Which function should i exclude to restrict responsibility to read only/inquiry ?
Regards,
Fahd

HI,
Thanks for the update, there is no standard way achieve this goal, as we have to define custom function, menu, responsibility to restrict PO form in inquiry mode.
Reference:
Metalink note id: I found metalink note How To Create a QUERY-ONLY FORM [ID 400380.1]
Regards,
Fahd

Similar Messages

  • Make short text field in Purchase order creation only display..

    Sir,
    Yeah my requirement is quite unusual, but such is the situation.
    I want to make the short text field in purchase order creation "only disply". what is happening is that user while creating PO is able to change the text of material in short text column. I want to make it only for display.
    Can it done on document type level, since for service type, and Text type of account assignment cat, only text field is filled up. so how to do it.
    Please assist...
    Rahul

    Dear Rahul,
    If you want to have the short text display only for standard item but not service item, you may check below customizing.
    Transaction SPRO:
    MM-PUR-PO
    -> Define screen layout at document level
    Field Selection group: Basic Data, Item
    Field Selection Key:  PT0F Standard item purchase order
    Field: Short text -> set as display
    Hope this help.
    Ian Wong Loke Foong

  • Purchase order release only at header level?

    Hello all,
    does anyone knows a method or workaround to allow implementation a release strategy based on the positions
    of a purchase order (like the posibilities in purchase requisition's customizing).
    I can't find anything that helps further, only a customer development seems to be the solution.
    The goal is, to route a workflow on position based cost center and account responsibilities.
    There is only a field for PO release status in the table EKKO, not in EKPO. For the PR, there is a correspondig
    field in the table EBAN.
    Thanks for incoming answers!
    Jens

    Hi Diego,
    sorry, my error! Thank you for your hint, but i can't find ad hoc the matching forum on sdn.
    Yes, i'm talking about MM, in detail the customizing of
    the purchasing process (procurement).
    Best
    Jens

  • Extended Classic Purchase Order created from RFx Response having complex pricing conditions enabled

    Hello Colleagues,
    I am currently analysing the correct usage of the complex pricing conditions in the sourcing process and wanted to understand the usage of the complex pricing condtions ( 01CT , dis % , header disc% , location dependent conditions , etc. with or without scales , ) while creating a extended classic purchase order directly as follow on document from rfx response.
    How relevant is the price conditions 01CT. Consider a case if the price condition from rfx response to po is changed to price manual 01PB but the price is correctly copied when the po is initially created from rfx response.
    Is this is the correct system behaviour ?
    Kindly help to clarify the above points.
    Thanks & Best Regards,
    Rahul

    Hi
    <b> You can either of these BADIs to handlwe the scenario.</b>
    BBP_CREATE_BE_PO_NEW Exit while creating a purchase order in the backend system
    BBP_CREATE_PO_BACK   OLD Exit while creating a PO in the backend system     
    BBP_ECS_PO_OUT_BADI  ECS: PO Transfer to Logistics Backend                  
    BBP_EXTLOCALPO_BADI  Control Extended Classic Scenario  
    Hope this will help.
    Please reward suitable points.
    Regards
    - Atul

  • Manufacturer field in Purchase Order - display only

    Does anyone know of a way (config or user exit) to make the field MFRNR on the purchase order item detail (Material Data tab) as an optional entry rather than dispaly only?
    I checked in the screen layout configuration for the screen sequence NBF (which is what we use) and I didn't see it as a changeable/updateable field.
    We are on ECC 6.0
    Thanks,
    Gina Feldner

    Gina Feldner,
    May be you can check for ME21N level also,
    Regards,
    Bhima

  • Advance payment & purchase order (Allowed Only 20% )

    Hi all,
    i have a purchase order number according this purchase order i have to pay the advance payment ( in Terms of payment 20 % Adv payment  with in 30 days based on purchase order date) 
    ex: purchase order value 20,000, 20% adv payment  4000 rs.in f-48 vendor down payment  vendor name, adv payment, bank name if user 5000 rs enter then after assigned purchase order the system automatically  checks the amount value the system is not allows i need popup message generated

    Hi,
    If there is any adavance payment against vendor and when you do any transaction system will give information massage. then
    you can handle through massage controlle as you required. (some technical changes required and ABAPer will help you in this regard)
    Regards,
    Venkat

  • Purchase Order Printout only after po release

    Dear All,
    Plz help me with the below mention problem :
    i donot want the purchase order to get printed untill the po get released completely, plz suggest me required configuration need to be done regarding this
    regds
    joy

    Hi Joy,
    You can adopt a release procedure where in you can block a PO for printing unlease its release strategy is fulfilled.
    Please go though below documents and grant me points if it works for you.
    Release Purchase Orders (MM-PUR)
    Technical name: SAP_MM_PUR_PO_RELEASE
    Tasks
    You can use this role to release (approve) purchase orders.
    A purchase order may be blocked via a release procedure (if its total value exceeds a predefined value - say $10,000 - for instance). Before this purchase order can be outputted (printed out or transmitted directly to the vendor), it must be approved (i.e. released).
    Activities in Materials Management
    Activity
    Transaction
    Release purchase order
    ME28
    Regards,
    Subha

  • Purchase Order printed only once

    Hello.
    I need to print the PO automatically when I create it.
    But if the PO is changed or release it sholdn't printed again automatically.
    How can I configure the message for this purpose?
    Is it possible print only once?
    Thank you in advance.
    Regards.

    Hi,
    In Standard only PO Printing  is possible after PO release.But if business needed, you can develop a DRAFT COPY OF PO PRINT OUT with help of ABAPer before PO release.
    After release if you needed automatic PO print then need to set Dispatch time as 4 {Send immediately (when saving the application)} in NACE t.code in application EF & in condition record t.code:MN04 for PO message type.
    As you needed ,only once print and no further PO print , then do not select" Multiple Issuing" check box in General data TAB for your required PO output type in NACE t.code in application EF .
    Regards,
    Biju K

  • Open purchase order only with open production or maintenance order

    Hi everyone,
    I am looking for a report that would show open purchase order but only linked to open orders (I am here talking about the source production or maintenance order in the Account Assignement tab).
    I have already checked transactions ME2L and ME2N but these do not seem helpfull.
    Thanks in advance for your help.
    Kind Regards,
    Olivier

    Use ME2K and enter the A/C category faor Production order and Maintenance order
    make sure that Selection parameter should be selected as open GR and if you want to make your own filter than
    go to SPRO-MM-Purchaisng-reporting-selection parameter-define sel parameter
    here you can create your own and use that for report.

  • SRM 7.02 Classic Scenario - Transfer of Purchase Order to Backend

    Good day,
    I would really appreciate some assistance on the following matter:
    We are implementing the classic scenario of SRM7.02 with ECC6.04 as backend.
    Our process is as follows: Purchase
    Requisitions are created in ECC and transferred to SRM by means of report BBP_EXTREQ_TRANSFER (we do not have PI/XI). These Purchase Requisitions are
    converted to shopping carts in SRM and goes to the Sourcing Cockpit. RFX's are created and responses are entered on behalf of vendors. When I now want to
    create a purchase order from the RFX response, I get a warning “PO xxxx is inthe process of transfer to backend system”.
    When executing transaction SM21, I get a warning “XI unable to access SLD:"Could_not_determine_SLD_access_data".  We do not have PI/XI and I would really
    appreciate if somebody can assist me with the exact entries that must be maintained in table BBP_FUNCTION_MAP to transfer purchase orders from SRM to ECC.
    I changed entries BUS2012 / CreateFromData1 /ERP_4.0/ERP_5.0 and ERP_6.0 from /SAPSRM/CL_SOA_ADPT_PO_CRT_ERP to L_BBP_BS_ADAPTER_PO_CRT_ERP10 and the PO replicated from SRM to ECC, but now in ECC, the purchase ordercannot be changed. It gives an error : Purchase Requisition xxxx can only be
    ordered in system SRDxxxx (which is the SRM system).
    Can somebody also please confirm that once Ihave replicated the Purchase order from SRM to ECC, the Purchase Order can be changed in ECC.
    Thank you in advance,
    Marinda

    I managed to resolve this by changing the system landscape from ERP6.0 to ERP 6.02

  • ESYU: Importing Standard Purchase Orders에서 문제 발생시 진단 방법

    Purpose
    Oracle Purchasing - Version: 11.5.10.2 to 12.0.6
    Information in this document applies to any platform.
    ConcurrentProgram:POXPOPDOI - Import Standard Purchase Orders
    이 문서는 reader게 Importing Standard Purchase Orders 실행 중 갑자기 발생하는 issue에 대해 어떻게
    대응하는지에 대한 자세한 정보를 제공한다.
    Instroduction
    Purchase Document Open Interface는 다량의 Standard Purchase Order는 Oracle Purchasing으로 빨리
    import 할 수 있게 한다. Import process는 import 되어야 하는 document information을 PO interface tables에
    넣어주는 작업을 필요로하며, data를 validate 하고 application에 PO를 생성하거나 error message를 return 하는
    Import Standard Purchase Orders concurrent program을 실행한다.
    이 문서의 목적은 Importing Standard Purchase Orders에 관련된 process를 이해하거나 갑자기 발생한 문제의
    원인을 찾는데 도움을 주기 위함이다. PO import 문제는 일반적으로 interface tables에 입력된 불일치하는 data가
    원인이며, 일단 문제가 확인되면 Metalink는 비슷한 문제를 찾아주거나 Oracle Support에 Service Request를 log
    할 수 있다.
    Test case Information
    1. 아래 insert 문장을 이용하여 PO interface tables에 data를 입력:
    INSERT INTO po.po_headers_interface
    (interface_header_id,
    action,
    org_id,
    document_type_code,
    currency_code,
    agent_id,
    vendor_name,
    vendor_site_code,
    ship_to_location,
    bill_to_location,
    reference_num)
    VALUES
    (apps.po_headers_interface_s.NEXTVAL,
    'ORIGINAL',
    207, -- Seattle
    'STANDARD',
    'USD', -- Your currency code
    24, -- Your buyer id stock
    'Advanced Network Devices',
    'FRESNO',
    'V1- New York City', -- Your ship to
    'V1- New York City', -- Your bill to
    'Currency test') -- Any reference num
    INSERT INTO po.po_lines_interface
    (interface_line_id,
    interface_header_id,
    line_num,
    shipment_num,
    line_type,
    item,
    uom_code,
    quantity,
    --unit_price,
    promised_date,
    ship_to_organization_code,
    ship_to_location)
    VALUES
    (po_lines_interface_s.nextval,
    po_headers_interface_s.currval,
    1,
    1,
    'Outside processing',
    'Flooring OSP',
    'Ea',
    1,
    --17.50,
    '10-APR-2009',
    'V1',
    'V1- New York City' )
    INSERT INTO po.po_distributions_interface
    (interface_header_id,
    interface_line_id,
    interface_distribution_id,
    distribution_num,
    quantity_ordered,
    charge_account_id)
    VALUES
    (po_headers_interface_s.currval,
    po.po_lines_interface_s.CURRVAL,
    po.po_distributions_interface_s.NEXTVAL,
    1,
    1,
    12975) -- Your Charge Account Id
    2. Interface tables에 data가 insert 되었다면 import progra을 실행전 정보를 확인하기 위해 아래 query 문을 이용한다.
    a - Select * from PO_HEADERS_INTERFACE where INTERFACE_HEADER_ID=&headerid
    b - Select * from PO_LINES_INTERFACE where INTERFACE_HEADER_ID=&headerid
    c - Select * from PO_DISTRIBUTIONS_INTERFACE where INTERFACE_HEADER_ID=&headerid
    3. Data를 review 했으면 Import Standard Purchase Orders program을 실행한다.
    Parameter >>
    Default Buyer: Null
    Create or Update Items: No
    Approval Status: INCOMPLETE
    Batch Id: Null
    4. 만일 program에 문제가 있어 error가 발생한다면 error의 원인을 제공하기 위해 Purchasing Interface Error Report를
    실행할 수 있다.
    Parameter >>
    Source Program: PO_DOCS_OPEN_INTERFACE
    Purge Data: No
    만일 PO가 import 되지 않았다면 Puchasing Interface Errors Report와 동일한 정보를 보기 위해 Interface Errors table을
    아래 SQL을 이용하여 조회할 수 있다.
    SELECT * FROM PO_INTERFACE_ERRORS WHERE INTERFACE_TRANSACTION_ID ='&recordsinterfacetransid';
    Diagnostics
    Import Standard Purchase ORder process의 troubleshoot 도움을 위해 아래 Diagnostics과 Reports를 이용한다.
    1. Diagnostics Tool : Oracle Purchasing Purchasing Documents Open Interface Data Collection Test
    (please refer to Note 224887.1 for assistance)
    이 Diagnostics는 import program에 의해 import 되는 data를 validate 할 것이며 missing 되거나 맞지않는 정보를 highlight 한다.
    이 Tool은 interface tables에 있는 맞지 않거나 불완전한 data의 자세한 정보를 제공할 수 있다.
    Error는 PO를 import 할 때 발생한 문제 분석을 시도하는데 매우 유익하므로 SR을 log시 이 Diagnostic output을 upload 하는
    것을 권장한다.
    2. Purchasing Interface Errors Report
    이 report는 Oracle Purchasing에서 사용가능하며 Import Standard Purchase Orders program을 실행시 발생하는
    error를 강조한다.
    Tracing
    11.5.10 이상의 version에서 Import Standard Purchase Orders program의 trace를 생성:
    1. Navigate to System Administrator responsibility
    2. Navigate to Profiles->System
    3. Query the Profile Option Concurrent: Allow Debugging and set it to Yes at User level
    4. Navigate to Purchasing responsibility
    5. From the Requests form, choose the Import Standard Purchase Orders program and set the required Parameters
    6. Click the Debug button
    7. Check the SQL Trace checkbox and specify Trace with Binds and Waits
    8. Submit the Concurrent program
    9. Retrieve the trace file created.
    Logging
    Import Standard Purchase Orders program의 FND Deug Log 생성:
    1. Log_seq를 아래 SQL을 이용하여 확인.
    select max(log_sequence) from fnd_log_messages;
    2. Set the following profiles at the user level:
    FND: Debug Log Enabled = YES
    FND: Debug Log Filename = NULL
    FND: Debug Log Level = STATEMENT
    FND: Debug Log Module = %
    3. Run Import Standard Purchase Orders program
    4. Using a SQL client run the following query :
    Select * from fnd_log_messages
    where log_sequence > &log_seq_noted_above
    order by log_sequence;
    이 query의 output은 Import Standard Purchase Orders program이 실행 중 발생한 error를 표시한다.
    Reference
    Note 781351.1

  • With a lock item in a purchase order, release strategy works?

    Dear All,
    I have a very important question for myself.
    I have a purchase order with only one item.
    I have set this item to locked.
    Release strategy works without problems.
    Is this situation correct?
    I don't understand it but maybe the release strategy works normally too....
    Please help me with a explanation
    Thanks in advance

    Yes, if a release strategy is applied to a PO, then even if you block / delete an item, it will still have the release strategy.
    This is standard behaviour, because you can later remove the deletion indicator or unblock the PO, whence the PO will again have to go through the Release Procedure.

  • FM / BAPI Inbound delivery creation for a Purchase Order without material

    Dear All,
    I have a requirement to create a Inbound Delivery for a Purchase order without material number. The Purchase Order has only Material text and no material number. Please let me know a BAPI or FM to create inbound delivery in this case where there is no material defined on PO. I require BAPI / FM  since I have to make a web-service for the same.
    Thanks in advance!
    Abhishek

    Hi I did a coding in one of the userexit. If ekpo-matnr is empty then fill
    KOMDLGN-UMVKZ = 1
    KOMDLGN-UMVKN = 1
    KOMDLGN-MEINS = EKPO-MEINS
    This parameters i.e. Qty conversion are necessary and since MATNR does not exists it has to be filled.

  • Down payment based on the purchase order

    i raise one purchase order 1000 Rs  in t code me21n after popup with number.  based on purchase order i pay advance amount 500 Rs with reference of purchase order number (in  f-48 i have given number reference field). when i saw the purchase oder (me21n)  in status tab down payments fields not updated like purchase order 1000 only and down payment 0 only the system showing.

    Hi
    In F-48 enter the input parameters and when you click enter it takes you to next screen. here you would enter the amount for 2nd line item. It is here you would enter the Purchase doc field.
    If the same is not visible, then check the field status for the GL field status group in OBC4 and also posting key field status in OB41
    Thank You,

  • Item text in Purchase Order getting updated with info. record Purchase Order Text

    Hello All,
    I am working in a roll out project and facing issue in text repeating twice for the line item in the Purchase Order for the new company code for which rollout is happening
    Issue:
    Item text in Purchase Order getting updated with info. record Purchase Order Text
    01) PO Text is maintained in the material master under "Purchase Order Text" tab
    02) The PO text that is maintained in material master is getting updated in the Purchase Info. Record
    03) When Purchase Order is created, the "Item Text" gets updated in the Purchase Order automatically only for the new company code for which rollout is happening. when printed, this results in the text getting duplicated twice
    03.1) this behavior is not observed in the Plants/ Company code that is already Live
    Configurations in the system:
    The copying rules for the "Texts for Purchase Orders" is
    Source Object = "Info Record", Source Text="Purchase Order Text", Fix="*"
    We have modified the Purchase Order form to print one of  the condition types maintained for calculating the tax. Other than this there is no change to the plants that are already live.
    I could not locate any "Purchase Organization" / "Company Code" / "Plant specific configuration.
    Am I missing any configuration or where can I look in what is causing this error.
    Request help from the experts in the forum.
    with Regards,
    Dhandapani R

    There is no company/purchasing/plant specific customizing for purchase order text.
    The customizing copying rules for the "Texts for Purchase Orders" affects all equally .
    If the text in the purchase order in ME23N is already filled different to other plants, then you either have a modification in place, or the texts are differently maintained in the referenced data (vendor, material, info record, contract)

Maybe you are looking for