Purchase requisition currency

Hi Gurus,
I need your help.
One of my users discovered an issue with the ZSE service requisitions.
Sometimes, the requisition currency needs to be changed. This doesnu2019t seem to be possible for ZSE requisitions while it can be done without problem for NB requisitions.
I could not find if the PR currency cant be changed for service PR in case of item category B
Can you tell me if this can be done?
Thanks for your cooperation

from OSS Note 1570943 - Change currency in purchase requisitions in External Services Management
Cause
In the case of service purchase requisitions (PR)  (with item category D or B), once you have pressed ENTER after filling the PR item level information:
- the services modules are triggered and the services/limits tab opens up,
- the PR item would have passed the currency that was first entered or defaulted from the item level to the services module.                                                                               
Hence in the case of service PR's it is not possible to change the currency in the valuation tab.
This is a technical limitation in the system.                                                                               
Resolution
There is no solution for this problem currently.
As the current MM-Services architecture is tightly bound with the MM-Purchasing core it is not planned to change this functionality.
Please do not change the currency in the service purchase requisition.

Similar Messages

  • Purchase Requisition number : In which table the PR currency field stored?

    When we raise a Purchase requisition nr : t codes ME53N / ME21N
    the PR nr, item nr, PR doc type, PR group, plant etc are stored in EBAN table.
    PR amount can be calculated based on MENGE * PREIS / PEINH from the table EBAN.
    Where will be the PR amount currencies like 'EUR' or 'GBP' stored?
    How can we relate those Table with EBAN/EBKN?
    Please let me know the exact TABLE for this.

    Hi,
    currency keys will be stored in
    TCURC table..  ( all currency keys will be available )
    eban - waers is the field where the currency key value stored
    regards,
    Venkatesh

  • Purchase Requisition number : In which table the currency field stored?

    When we raise a Purchase requisition nr : t codes ME53N / ME21N
    the PR nr, item nr, PR doc type, PR group, plant etc are stored in EBAN table.
    PR amount can be calculated based on MENGE * PREIS / PEINH from the table EBAN.
    Where will be the PR amount currencies like 'EUR' or 'GBP' stored?
    How can we relate those Table with EBAN?
    Please let me know the exact TABLE for this.

    hi kpreddy
    before going to raise purchage order u must give the purchage requisition plan
    why we r going to purchage the material??? so many things to approve to purchage a material
    menge - purchage order quntity
          preis -
    that currencies depend upon the country wise purchage order..........

  • Currency change in Purchase Requisition

    Hi All,
    1 Compnay code - currency "INR"
    2 Plants assigned to same company code (Plant A & Plant B)
    1 Material created in both the plants. Inmaterial master -Accounting view-currecny "INR"
    While creating Purchase Requisition for plant A, currency cannot be changed from INR (Company code) to USD, system give error "Currency cannot be changed". But I am able to change currency for Plant B with same material code.
    Why currecny change differes in the plants which belong to same company code
    Waiting for your reply..
    Regards

    see this thread:
    [Changing currency in Purchase Requisitions;

  • Currency in purchase requisition

    Hi Gurus,
    The user is trying to create a PR with services. By default the currency is taking PKR (pakistan) currrency. But the user wants it to be USD for that requisition.
    I think it wont possible, but i want to know the info indetail.  Can anyone explain me about this.
    Regards
    subbu

    What is your Plant Currency??
    System will the Currency in Purchase Requisition as per the Plant Currency....
    Go to ME51N and Click on Personal Settings and Check Currency is Set as Default. If Set, Remove and Save.
    Note : Even if you Set the currency Default it will Overwrite the Plant Currency. That is As soon as you enter Plant it will Overwrite.
    Edited by: Ashøk Kümàr Telikülà on Jan 23, 2009 2:34 PM

  • Purchase requisition release strategy

    I want each purchase requisition should be created with valid release strategy. The problem presently is that if somebody puts wrong parametes (such as purchasing group, currency) the purchase requisition will not be applicable to release and the purchase order can be easily created. So in such cases there is no need to release purchase requisition which is not correct for business point.
    Pls advise.

    Hi Balaji
    Ur need is appreciated but inorder for that to work we have to make sure that all the possible combinations exist in ur characteristics list which may not be possible all times.
    So better way would be to check whether the characteristics combinations of ur class and the corresponding data of ur requisitions matches and trigger error msg if differs.
    Ex: Plant and doc type be the characteristics used in ur class.
    Check whether the PR has only the plants and doc types that is specified in ur release strategy and if no trigger error msg.
    Try this using BAPI also. Get help from ur ABAPer.
    Thx
    Raja

  • Purchase Requisition creation

    Hai Experts,
    I am trying to create Purchase requisition using BAPI BAPI_PR_CREATE.
    I have passed Header, Item,Account data and corresponding Headerx.......structures to my BAPI and when i am running my Bapi it is throughing error....."Enter Cost Centre" when the account assignment category is 'K' ..
    and "G/L account should be assigned to the CO Area"  when the account assignment category is "P".
    and the function setting regarding the CO Area and G/L account are correct..and exists in my system.
    Can anyone  plz provide  solution 4 dis...
    Thanx in advance..

    hi ram
    pls check out the fields in the check table  may it has some currency and quantity fields take that fields in to the local varibles
    pass the values to bapi
    bapi won't support the reference fields in the strcuture...................................

  • Purchase Requisition release

    Hi,
    Could anybody help me out with the configuration settings of purchase requisition Release.
    Client want to set release status for Purchase Requisition , where two persons will be responsible to release the requisition . when the first person releases the requisition , it will come to the second or final person for release ,when he releases then the requisition is released for purchase orders.
    Could anybody help me out with the configuration settings.
    Thanks N Regards,
    Siddhartha

    Use this steps. below is for PO same do it with PR. that is in place of PO take it as PR.
    Releasing Procedure for Purchase Documents
    Use
    This setting is incorporated to just give demonstration of how SAP Release procedure works.  The aim of this procedure is to replace manual written authorization procedures using signatures by an electronic one, while maintaining the dual Ctrl principle.  The person responsible processes the purchasing document in the system, thereby marking it with an "electronic signature" which can give the document legal force.
    3.4.24.1     Creation of Characteristics
    Procedure
    1.     Access the activity using one of the following navigation options:
    IMG Menu     Materials Management  Purchasing  Purchase Order  Release Procedure for Purchase Orders  Edit Characteristic
    Transaction Code     CT04
    2.     On the Characteristic screen, make the following entries.
    3.     In put POVAL in filed Characteristic and choose Create (White paper) icon or Ctrl + F3 to begin creation of characteristic.
    Field name     Description     User action and values     Note
    Select Addnl Data tab                
    Table Name     Table Name     CEKKO     
    Field Name     Field Name     GNETW     
    Choose Enter to continue, system will give an information message saying Format Data taken from ABAP dictionary, Choose Enter again to continue.
    Select Basic Data tab               
    Description     Description     Total net order value     
    Status     Status     Released      
    Data Type     Data type     Currency format     Selected by system
    Number of characters     Number of characters     15     
    Decimal places     Decimal places     2     
    Currency     Currency     INR     
    Interval vals allowed     Interval values allowed     Check this tick box     
    Multiple Values     Multiple values allowed     Select this radio button      
    4.     Choose Enter to complete the entries
    5.     Choose Save icon or Ctrl + S to save the characteristic.
    3.4.24.2     Creation of Class
    Procedure
    1.     Access the activity using one of the following navigation options:
    IMG Menu     Materials Management  Purchasing  Purchase Order  Release Procedure for Purchase Orders  Edit Class
    Transaction Code     CL02
    2.     On the Class screen, make the following entries:
    Field name     Description     User action and values     Note
    Class     Class     PORELPROC     
    Class Type     Class Type     032     
    Choose Create icon or white paper icon to create new class.
    Description     Description     Purchase Order Release Procedure     
    Status     Status     Released     
    Choose Char. Tab to input characteristic name.
    Characteristic     Characteristic     POVAL     Created in above step
    3.     Choose Enter to complete the entries
    4.     Choose Save icon or Ctrl + S to save the characteristic.
    Result
    Class type 032: Class PORELPROC created.
    3.4.24.3     Configuration of Release Procedure
    Procedure
    1.     Access the activity using one of the following navigation options:
    IMG Menu     Materials Management  Purchasing  Purchase Order  Release Procedure for Purchase Orders  Define Release Procedure for Purchase Orders
    Transaction Code     SPRO
    2.     On executing the transaction system will give a popup screen choose Release Groups, system will display Change View u201CRelease Groups: External Purchasing Documentu201D: Overview.
    3.     Choose New Entries icon and make the following entries:
    Field name     Description     User action and values     Note
    Rel. Group     Release Group     02     
    Class     Class Name      PORELPROC     Created in above step
    Description     Description     PO Release Procedure     
    4.     Choose Enter to complete the entries
    5.     Choose Save icon or Ctrl + S to save the entries.
    6.     Choose yellow arrow to go back to popup screen.
    7.     Choose Release Codes to select.
    8.     Choose New Entries icon and make the following entries:
    Field name     Description     User action and values     Note
    Grp     Release group     02     Created in above step
    Code     Release Code     01     
    Workflow     Workflow     Leave it blank     
    Description     Description     Purchase Officer     
    Grp     Release group     02     Created in above step
    Code     Release Code     02     
    Workflow     Workflow     Leave it blank     
    Description     Description     Materials Manager     
    9.     Choose Enter to complete the entries
    10.     Choose Save icon or Ctrl + S to save the entries.
    11.     Choose yellow arrow to go back to popup screen.
    12.     Choose Release indicator to select.
    13.     Choose New Entries icon and make the following entries:
    Field name     Description     User action and values     Note
    Release ind.     Release Indicator     1     
    Released     Released     Leave it blank     
    Chgable     Changeability     4     
    Value change %     Change of value     10%     
    Description     Description     Purchase Order Blocked     
    Go to 2nd line and input the following values:
    Release ind.     Release Indicator     2     
    Released     Released     Select Check box     
    Changeable     Changeability     6     
    Description     Description     Purchase Order Released     
    14.     Choose Enter to complete the entries
    15.     Choose Save icon or Ctrl + S to save the entries.
    16.     Choose yellow arrow to go back to popup screen.
    17.     Choose Release Strategies to select.
    18.     Choose New Entries icon and make the following entries:
    19.     System will give new screen New Entries: Details of Added Entries
    Field name     Description     User action and values     Note
    Release Group     Release group     02     
    Rel. Stategy     Release Strategy     S1     
              Capital Items Release     
    Release Code     Release Code 1     01     
    Release Code     Release Code 2     02     
    20.     Choose Enter to complete the entries.
    21.     Choose Release prerequisites icon and select check box 02 at the bottom and choose Enter.
    22.     Choose Release statuses icon, system will give a popup screen system will default 1, 1 and 2 entries one by one as a default.  Choose Continue.
    23.     Choose Classification icon, here you can see Total net order value is displayed, please input >= 1.00 INR value in the white placed and choose Enter.
    24.     Choose Next Screen icon or choose F8 to continue.
    25.     If you want to simulate the release procedure you can choose Release Simulation icon.
    26.     Choose Enter to complete the entries.
    27.     To save the settings choose Save icon or Ctrl + S.
    Result
    Release procedure is saved.
    3.4.24.4     Assignment of Values to Release Procedure 
    As a default all the purchase documents >= Rs. 1000000.00 is suggested in the following step of release procedure, if you want to have different one you need to change the value in the following step.  If you do not want release procedure you may change the value to Zero.
    Procedure
    1.     Access the activity using one of the following navigation options:
    IMG Menu     Cross-Application Components  Classification System  Assignments  Assign Object to Classes
    Transaction Code     CL20N
    2.     On the Class screen, make the following entries:
    Field name     Description          User action and values     Note
    Class Type     Class Type          032     
    Choose Enter to Assign values.
    Release group     Release Group          02     
    Rel. Strategy     Release strategy          S1     
    Choose Enter.
    System will give Class name in Assignments, Double choose Class Name.
    System will display Characteristic name Total net order value. Assign the value >= 1000000.00 INR  against filed Value.
    3.     Choose Enter to complete the entries
    4.     Choose Save icon or Ctrl + S to save the characteristic.
    Regards
    S

  • Purchase Requisition extractor

    Hi,
      I am planning to pull purchasing requisition data. As there is no generic extractor I guess I have to create create view on EBAN and EBKN tables and then create generic datasource on it. I have some doubts..
    1)Should I pull data from both tables EBAN and EBKN. If yes on what key should I create view.
    2)How can I maintain delta for this?
    Thanks.

    thnx for the reply subray..
    I require only PO req no,item no and requisitioner...so I guess its better to create view in EBAN.
    Moreover When I am trying to create generic extractor for EBAN its saying...
    <b>Invalid extract structure template EBAN of DataSource ZPURCH_REQ
    Message no. R8359
    Diagnosis
    You tried to generate an extract structure with the template structure EBAN. This operation failed, because the template structure quantity fields or currency fields, for example, field MNG02 refer to a different table.
    </b>
    I guess I have to create include currecy field...Should I crete different view for EBAN and the table for MNG02.

  • Can't use Overall Release for Purchase Requisitions

    I have two groups, AA and ZZ.  Each group has it's own Class.
    Group AA uses Cost Center Class (CN)  (uses Characteristics Cost Center and Line Amount)
    Group ZZ uses Order Class (OC) (uses Characteristic Order)
    I have built one and only one Release Strategy for each of these Groups.  These Strategies both work successfully when I select the other group to be the group for Overall Release.  That is, if I set ZZ to be for Overall Release, then create a requisition, the release strategy for Group AA is applied successfully.  However, if I modify the req the strategy for ZZ, does not get applied.
    The opposite is true.  When AA is set to be for Overall release, then ZZ works.  However, if I modify the req, then AA's release strategy does not get applied.
    Again, both strategies work correctly when the other Group is set to be the one to use for Overall Release.  However, neither strategy works if its group is set to be the one for Overall Release.
    What am I missing?  I only have two classes, two groups, and two release strategies.

    SAP Standard system allows only 8 levels of release codes.If client requirement is more than 8 then for excess release codes customisation is done by the technical team (Abapers).Lets take an example of 15 release levels required for a client according to his Business needs then in this case initial 7 codes are customised and remaining 8 release codes are configured in the system.
    Release procedure is of two types
    Release Procedure without classification
                 This procedure is applicable only for Purchase Requisitions.
                 Here PR is released Item by Item only.
    Release Procedure with classification
                This procedure is applicable to PR,RFQ,Service Entry sheet,RFQ,PO,Contract  and scheduling agreements.
                Item by Item and Header level releases can be configured
                For PR - both item by item and Header level release can be configured
                For external purchasing documents - Release is possible only at Header level.
    Step 1:
    Create Characteristics
    In this step we need to create characteristics - conditions to be satisfied for triggering Release startegy.For example client has asked to set release strategy based on 3 inputs.Combination of value, Plant and Purchasing group
                1) Total value of PR more than Rs 50,000
                   create  characteristic as "Release_PR_total_value" in transaction code CT04.
                  Tab -  Basic data " Data type --- CURR currency format", "Decimal places - eg. 2 " and "currency  eg. INR or USD"
                  Tab -values key in > 50000 INR
                  Tab -  Additional Data-  Table Name "CEBAN" and Field Name "GSWRT"
                  Tab - Restrictions - class type - 032 - Release strategy
                2) Plant
                     Create characteristic "Release_PR_plant" in transaction code CT04.
                     Tab - Basic data - Data type - CHAR; Number of chars - 4
                     Tab - Values - Key in all the plants for which you are required to configure release proc.  eg. 1000,2000,3000
                     Tab - Additional data - Table name CEBAN and Field Name is WERKS.
                3) Purchaisng Group
                     Create characteristic "Release_PR_PurchasingGroup" in TCode CT04
                    Tab - Basic data - Data Type - char, Number of chars eg. 3
                    Tab - values - Key in all the purchasing Groups for which Release proc. is to be configured as required by Client.
                    Tab - Addnl Data - Table Name CEKKO and field name - EKGRP
    Step 2:
    Define class in transaction code CL02
    Menu path SPRO>Materials Mgmt>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>Edit classes
    Here we assign all the above created Characteristics to a CLASS so that a release strategy to be triggered when all the conditions are met.
    Create a new class with free choice of names as "PR_Release_proc" in transaction code CL02.*Key in the class name and select class type as 032 - RELEASE STRATEGY then click on symbol create to enter all the details as mentioned below.
    Tab - Basic data - Enter description as "PR_Release-Proc",
    status- Released, Same classification - check the push button - Warning Message
    Tab- CHAR Enter above created 3 characteristics
    1.Release_PR_total_value
    2.Release_PR_plant
    3.Release_PR_PurchasingGroup
    step3:   
    Menu path is
    SPRO>Materials Mgmt>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>set up procedure with classification>
    here define
    1.Release Groups
    Release group 01 is used for Purchase requisitions and 02 for Purchase orders.
    Here assign class "PR_Release_proc" against release code "01"
    check "OvRelPReq" indicator for over all release (All line items )of document in one shot else it will be released line item wise.
    2.Release codes
    Release codes are assigned to Release groups, in Workflow these release codes are tagged to users' SAP IDs through which they will be able to approve or reject a PR in SBWP(Inbox in SAP Business workplace.
    PRs are released by users in transaction code ME54N.
    Eg
    Type of user            - Level -             Release code                    
    PR creator - clerk or Business user -  
    Approver    -  Supervisor                 -   R1
    Approver  -   Project Lead              -   R2
    Approver   -  Asst. Manager             -  R3
    Approver   -  HOD/General Manager  - R4
    Release codes R1 to R5 are assigned to corresponding users.Manager R4 can only approve the PR if prior approvals till R3 are completed else not in ideal situation.
    For detailed info please refer
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
    3. Release Indicator:
    Release indicators show the release status of a Purchase Requisition.
    For detailed info please refer SAP Help official site
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
    4.Release Pre requisites:
    These define the order in which individuals or departments release the PR in sequence.
    3.Release strategies
    Create a new release startegy  eg ."A1" or "U1" , write its description PR release for value >1 lakh
    Now select release codes according to the Chart of Authority set by your client.
    Eg.
    Release startegy " A1 - PR release for value >1 lakh"
    R1 - Supervisor   
    R2- Project Lead    
    R3- Asst. Manager 
    R4- General Manager
    Now click on" Release  Prerequisites "push button and check all the boxes in ascending order.Save the document
    click on "Release statuses" push button, check release statuses then click on "Continue" push button.
    In third push button you can maintain CLASSIFICATION data or later you can directly mainatain in transaction code CL20N for this strategy.
    Classification data for example
    1. Value - > 100000
    2. Plant - 1000,2000,3000 etc
    3. Purchasing groups - 101,102,103 etc
    By clicking on "Release Simulation" push button you can check whether release is getting affected for configured release codes or not.
    In this way you can configure all the required Release startegies.
    Now create a PR in T code ME51N with the above conditions then a new tab will appear in PR creation screen at the time of check.Save the document and this can be released by respective users in TCode ME54N.
    Tcode - ME54N - For Individual Release
    Tcode - ME55 - For Collective Release
    For detailed info please visit SAP HELP website
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
    Regards,
    Indranil

  • Purchase Requisition Release at Header Level

    Hi MM experts,
    We are on ERP6. Can we activate purchase requisition release at header level (ie overall requisition dollar level - sum total of all requisition line items) just for one business (company code) without affecting rest of client which uses release strategy at requisition line item level?
    Is it possible to share the same document type, e.g. NB that is used by other business?
    Many thanks.
    Thomas

    With the release procedure with out classification , it is possible to release the PR at header level based on the value of the PR . In determination of release strategy , you can maintain the value , currency and release stratergy .
    But to restrict this to a particular comany code , you may use the exit M06B0002 where in you can write the logic .
    -Hari.

  • FI MM integration with purchase requisition

    Hi,
    For FI MM integration - acquire asset through MM - the process is -
    1) create asset master
    2) Purchase requisition
    3) PO
    4) Assign asset master to PO
    5)Goods receipt
    It is difficult to create an asset master in advance, so the solution is to create purchase requisition without account assignment.
    I would like to know whether this is possible. because once we select Account assignment category "A" system does not allow us to save the Purchase requisition.
    Can someone pl. help me understand how to achieve this.
    Thank you
    - Vedavatee

    Hi vedavatee,
    You need to assign Asset Number since PR when you are using Account Assignment A.

  • Error in new purchase requisitions, for already deliverd materials

    Dear all,
    I have a problem with newly created purchase requisitions, although material was partially delivered and no delivery is expected anymore.
    For example I have ordered 1767kg of oil and a total sum of 1766.2kg was deliverd. This means only a minor amount of material was not deliverd and only 80gramm are missing. The purchase value key allows a 5% over and under delivery.
    Usually I would expect, that because of the purchasing value key of 5 % over and under deliverance allowence this situation should not occur anymore. Additionally at the time of goods receipt the key of final delivery was set and the purchase order is updated correctly.
    But when I run the MRP again I will have another purchase requisition. The dependend requiement of the material above still existis as production is not finished yet or this is still a planned order.
    What keys do I need to set in total for allowing a "partial delivery"?
    - Purchaseing value key in the material master
    - Delivery completed at the time of goods receipt
    Maybe this question is to basic as I cannot find any questions / answers related to this issue here in the forum.
    In some points, I found that I need to set up the vendor accordingly to set up partial deliveries. But I cannot find the right setting to allow the vendor to do so. I use MK02 for the change of the vendor settings.
    Thank you very much for your support!
    With best greetings,
    Bjoern

    Hello Jürgen,
    yes after thinking about this issue again, I think this might not be an appropriate solution. Now I am thinking about other possibilities.
    1) Automatically change the value in the production order at the time of saving MIGO - will not create any more missing material messages and no new purchase requisitions .
    2) Errror message, that for this positions no more postings are possible as the purchase order still remains "open"
    3) I need to find the customizing of the indicator "delivery completed". At the moment I just dont see, the influence of this indicator.
    Sorry for my "stupid" questions, but I am quiete new to these MM topics. Up to now I was always doing only PP and QM but our collegue for MM has left the team and there are some open issues which now belong to me. Lucky me.
    I have created a new posting at:
    With best greetings,
    Bjoern

  • 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.

  • 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

Maybe you are looking for