Using AME for Purchase Requisition Apporval transaction type

Hi ,
Product : EBS --11.5.10.2 AME B rollup 2 .
We wanted to introduce approvers based on requisition line total and a dff value on requisition line.
For that we created a line level attribute to calculate the requisition line amount Then created a test condition saying if req line total is > 1500 Introduce and approval group.
When creating a rule It says create a rule at header level So went into Approvals Management Administrator resp and changed the Configuration Variables allowAllItemClassRuleswhether AME allows to create subordinate item class rules-- Yes at transaction type Purchase requisition Approval . This allowed be to create the rule for the line level Tested real transaction on test workbench --This works fine
When tested this using the actual requisition --It gives and error "You do not have the authority to approve this requisition and an Approval List was not created automatically. Please contact your system administrator."
Error message in the log shows :
EXCEPTION:[icx.por.approval.server.ApprovalListAMImpl]:Fatal OAException:java.sql.SQLException: ORA-20001: The input ame_util.approverRecord2 does not belong to the header item class, as ame_api requires.
ORA-06512: at "APPS.POR_AME_APPROVAL_LIST", line 485
ORA-06512: at line 1
Is it the correct way to define rules ?
Is it possible to create a Header level attribute to calculate the line total or check for req total and add an approver looking at the line level req totals ?
Please suggest if any body implemented Line level approval for requisition using AME ?
If this is not the correct forum please inform which forum should i post the thread.
-Regards,
Chandra

Hi,
Please review the following documents and see if it helps.
Note: 333270.1 - APINV: Line Item Class Rules Error in AP with ORA-20001: The input ame_util.approverRecord2 does not belong to the header item class, as ame_api. No Errors In AME Test Tab
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=333270.1
Note: 393099.1 - Ora-20001 Error When Testing In Ame Test Tab
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=393099.1
Regards,
Hussein

Similar Messages

  • Is it possible Line level approval in AME for purchasing requisition?

    hi
    is it possible Line level approval in AME for  purchasing requisition ?
    so that send each line to separate approver ?

    If using AME, it should be possible. Check AME Guide for POs for details. Let me know if you run into issues.
    Thanks
    Shree

  • AME for Purchase Requisitions

    Hello All
    I am in the process of setting up AME in R12.1.2 for purchase requisitions and got struck with an issue
    My requirement is to route the requisition to a particular job based on the item category and the requisition total. I setup conditions, action types and approval groups and then the rule.
    When I used static in my Approval Group setup it works fine with out issues however we do not want to use static as employees keep changing and want my approval driven out of the job hence updated the approval group to use Dynamic usage type and used the below query to pick the name of the employee based on the job.
    select papf.full_name from per_all_assignments_f paaf, per_all_people_f papf, per_jobs pej where
    paaf.person_id = papf.person_id
    and sysdate between paaf.effective_start_date and paaf.effective_end_date
    and paaf.job_id = pej.job_id
    and pej.name like 'IT.Group IT Operations Manager.Staff'
    Now when trying to create a requisition it shows up a message that "Approval List could not be generated. Please contact your System Administrator to review AME rules setup."
    When validated the above query it says query is valid but still not working. I even tried with person_id but still no luck
    Thanks a ton in advance
    Regards
    Dilip

    Hi Dilip,
    Pl. visit following links.
    AME for iProcurement requisitions
    Re: AME-Hierarchy Deciding Feature ?
    HTH
    Sanjay

  • Can AME used in combination with position heirarchy for purchase requisitions ?

    Hello,
    We are using position heirarchy for purchase requisitions.
    Can we use Approval Management engine in combination with the existing position heirarchy for purchase requisitions for more flexible workflow routing ?
    regards,
    Natalia

    Hi Natalia,
    Have your inquiry been addressed? Please let me know if you need any further assistance in this, otherwise, Please mark the answer as Correct/Helpful in order to leverage the discussion and facilitate correct answer to other members who may confront the same concern of yours.
    Note: Liking the answer will not mark it as Correct/Helpful, you have to open the discussion first to be able to mark it (This is not possible by opening the discussion from your inbox)
    Thanks,

  • 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

  • Using AME for auto approval of requisitions

    Hi,
    Is there a way to handle a scenario with AME where we need to have the requisition auto-approved whenever the amount is less than 1K.
    I am able to use AME for all other scenarios, where the requistion moves for a different person's approval. But what about auto-approval ?
    Pls help me on this.
    Regards,
    Sambit

    On 'Purchase Requisition' Document type, check 'Owner can approve' checkbox.
    In AME, set the attribute ALLOW_EMPTY_APPROVAL_GROUPS and ALLOW_REQUESTOR_APPROVAL to true and test.
    Have a condition so that it retrieves empty approver group or the requestor himself as the approver.
    Thanks
    Pradeep
    Edited by: Pradeep Kalyan on Oct 8, 2012 6:43 PM

  • Is it possible Line level approval for purchasing requisition in AME?

    hi
    is it possible Line level approval for purchasing requisition  in AME?
    so that send each line to separate approver ?

    If using AME, it should be possible. Check AME Guide for POs for details. Let me know if you run into issues.
    Thanks
    Shree

  • How do I enter Document Type for Purchase requisition IDOC

    Hello,
    File - IDOC (PREQCR.PREQCR02)
    The file is getting picked up and shows up a checkered flag in Moni..
    but in WE05, on R3 side, i see an error message
    "Enter Document Type"
    How do I enter document type for Purchase requisition IDOC?
    will that solve this issue?
    thanks and regards
    Nikhil.

    Hi,
    For error 51, you need to set the default document type in the inbound processing FM of the IDOC
    Standard type - NB
    Subcontrator type
    Blank PO
    Service PO
    Stock transport PO.
    Document types is used for below things,
    1. It controls the no. range of the document i.e. the doc no.
    2. It controls whether doc no. is auto assigned or manually entered
    3. It controls the field status of the doc header fields i.e. whether input is mandatory or optional
    4. It controls the physical doc filing
    Thanks
    Swarup

  • Release strategy for purchase requisition does not kick in

    Hi Gurus!
    I've been struggling with this issue for some weeks now.
    I have set up the release strategy configuration for purchase requisitions with classifications.
    However, if I create a purchase requisition the release functionality is not taken into account by the system.
    See below some more information regarding my configuration:
    1. I've created a new characteristic "REL_PR_GROUP". Status: released, Multiple values, Number of Chars 3, 7 values (TR1, TR2, TR3....TR7), Table name: CEBAN, Field name: EKGRP, Procedure for value assignment set to not ready for input.
    2. I've created a new class: "REL_PR_ANPC". Class type 032, Status: released, Same classification: do not check, Char: "REL_PR_GROUP"
    3. I have one release group "T1", Rel. object 1, OverReqRel is marked, Class: "REL_PR_ANPC"
    4. I have 5 release codes. Grp: T1, Code: 01....05
    5. I have 2 release indicators:
    "R = Released", Rel. for ordering is marked, Changeabil: 4, Value chgs. 100,0
    "X = Blocked",  Changeabil: 4, Value chgs. 100,0
    6. I have 1 release strategy:
    "T1 with Grp T1"
    - one release group, 01 Manager
    - release prerequisites not applicable because of only one release group
    - release status, nothing marked = blocked, 01 marked = released
    - classification, purchasing group is TR1 or TR2 or TR3 or TR4 or TR5 or TR6 or TR7
    I intentionally kept the configuration as simple as possible so I can try to get it working first.
    Now if I create a purchase requisition for an item with release group T1, I would expect the release strategy to be activated. However, this is not the case. I don't see the "release status" tab in the PR, and if I try to relase via ME54 the system says the PR is not relevant for release.
    Could you please assist in getting this working?

    Hi,
    Have you checked in CL30/CL30N if your release strategy is derived successfully?
    See section 3 of Note 365604. A small section of it:
    You can use transaction CL30 search for an object using the data
    of the purchase requisition/purchase order. Here, it is important
    that the object search determines exactly one strategy. If this
    is not the case, this indicates that there are overlapping
    strategies in the system or that the release strategies in
    Customizing do not correspond with those from transaction CL24.
    See the previous point. If the object search returns more than
    one result, the system subsequently determines an incorrect
    release strategy or no release strategy at all.
    If it is derived successfully, next, check the user exit EXIT_SAPLEBND_001 as per Note 371667:
    The following assignment statement has to exist within activated SAP
    enhancements M06B0002 (include zxm06u13) and M06B0005 (include zxm06u31)
    for purchase requisitions:
         E_CEBAN = I_CEBAN.
    Regards,
    Purnima.

  • User exit/BADI  for Purchase requisition through release of Process order

    Hi ,
    i need to add some text to the Pur Req.
    The Pur Req will be created THROUGH the release of PROCESS order. Please let me know any exits are available for the same.
    regards

    Hi
    Check the following Exits and BADI for Pur Requisition
    Enhancement
    MEVME001                                WE default quantity calc. and over/ underdelivery tolerance
    MM06E001                                User exits for EDI inbound and outbound purchasing documents
    MM06E003                                Number range and document number
    MM06E004                                Control import data screens in purchase order
    MM06E005                                Customer fields in purchasing document
    MM06E007                                Change document for requisitions upon conversion into PO
    MM06E008                                Monitoring of contr. target value in case of release orders
    MM06E009                                Relevant texts for "Texts exist" indicator
    MM06E010                                Field selection for vendor address
    MM06E011                                Activate PReq Block
    MMAL0001                                ALE source list distribution: Outbound processing
    MMAL0002                                ALE source list distribution: Inbound processing
    MMAL0003                                ALE purcasing info record distribution: Outbound processing
    MMAL0004                                ALE purchasing info record distribution: Inbound processing
    MMDA0001                                Default delivery addresses
    MMFAB001                                User exit for generation of release order
    MRFLB001                                Control Items for Contract Release Order
    AMPL0001                                User subscreen for additional data on AMPL
    LMEDR001                                Enhancements to print program
    LMELA002                                Adopt batch no. from shipping notification when posting a GR
    LMELA010                                Inbound shipping notification: Transfer item data from IDOC
    LMEQR001                                User exit for source determination
    LMEXF001                                Conditions in Purchasing Documents Without Invoice Receipt
    LWSUS001                                Customer-Specific Source Determination in Retail
    M06B0001                                Role determination for purchase requisition release
    M06B0002                                Changes to comm. structure for purchase requisition release
    M06B0003                                Number range and document number
    MEQUERY1                                Enhancement to Document Overview ME21N/ME51N
    MELAB001                                Gen. forecast delivery schedules: Transfer schedule implem.
    MEFLD004                                Determine earliest delivery date f. check w. GR (only PO)
    MEETA001                                Define schedule line type (backlog, immed. req., preview)
    ME590001                                Grouping of requsitions for PO split in ME59
    M06E0005                                Role determination for release of purchasing documents
    M06E0004                                Changes to communication structure for release purch. doc.
    M06B0005                                Changes to comm. structure for overall release of requisn.
    M06B0004                                Number range and document number
    Business Add-in
    ME_PROCESS_REQ_CUST                     Enhancements for Processing Enjoy PReqs: Customer
    ME_PROCESS_REQ                          Enhancements for Processing Enjoy PReqs: Internal
    ME_PROCESS_PO_CUST                      Enhancements for Processing Enjoy Purchase Order: Customer
    ME_PROCESS_PO                           Enhancements for Processing Enjoy Purchase Order: Intern.
    ME_PROCESS_COMP                         Processing of Component Default Data at Time of GR: Custome
    ME_PO_SC_SRV                            BAdI: Service Tab Page for Subcontracting
    ME_PO_PRICING_CUST                      Enhancements to Price Determination: Customer
    ME_PO_PRICING                           Enhancements to Price Determination: Internal
    ME_INFOREC_SEND                         Capture/Send Purchase Info Record Changes - Internal Use
    ME_HOLD_PO                              Hold Enjoy Purchase Orders: Activation/Deactivation
    ME_GUI_PO_CUST                          Customer's Own Screens in Enjoy Purchase Order
    ME_FIELDSTATUS_STOCK                    FM Account Assignment Behavior for Stock PR/PO
    ME_DP_CLEARING                          Clearing (Offsetting) of Down Payments and Payment Requests
    ME_PURCHDOC_POSTED                      Purchasing Document Posted
    SMOD_MRFLB001                           Control Items for Contract Release Order
    EXTENSION_US_TAXES                      Extended Tax Calculation with Additional Data
    ARC_MM_EKKO_WRITE                       BAdI: Enhancement of Scope of Archiving (MM_EKKO)
    ARC_MM_EKKO_CHECK                       BAdI: Enhancement of Archivability Check (MM_EKKO)
    MM_EDI_DESADV_IN                        Supplementation of Delivery Interface from Purchase Order
    MM_DELIVERY_ADDR_SAP                    Determination of Delivery Address
    ME_WRF_STD_DNG                          PO Controlling Reminder: Extension to Standard Reminder
    ME_TRIGGER_ATP                          Triggers New ATP for Changes in EKKO, EKPO, EKPV
    ME_TRF_RULE_CUST_OFF                    BADI for Deactivation of Field T161V-REVFE
    ME_TAX_FROM_ADDRESS                     Tax jurisdiction code taken from address
    ME_REQ_POSTED                           Purchase Requisition Posted
    ME_REQ_OI_EXT                           Commitment Update in the Case of External Requisitions
    ME_RELEASE_CREATE                       BAdI: Release Creation for Sched.Agrmts with Release Docu.
    ME_DEFINE_CALCTYPE                      Control of Pricing Type: Additional Fields
    ME_CHANGE_OUTTAB                        Enrich ALV Output Table in Purchasing
    ME_CHANGE_CHARACTER                     Customer-Specific Characteristics for Product Allocation
    ME_CCP_DEL_DURATION                     Calc. of Delivery Duration in CCP Process (Not in Standard)
    ME_CCP_BESWK_AUTH_CH                    BAdI for authorization checks for procuring plant
    ME_CCP_ACTIVE_CHECK                     BAdI to check whether CCP process is active
    ME_BSART_DET                            Change document type for automatically generated POs
    ME_BAPI_PR_CREATE_02
    ME_BAPI_PR_CREATE_01
    ME_BAPI_PO_CREATE_02
    ME_BAPI_PO_CREATE_01
    ME_BADI_DISPLAY_DOC                     BAdI for Internal Control of Transaction to be Invoked
    ME_ACTV_CANCEL_PO                       BAdI for Activating the Cancel Function at Header Level
    MEGUI_LAYOUT                            BAdI for Enjoy Purchasing GUI
    ME_CHECK_ALL_ITEMS                      Run Through Items Again in the Event of Changes in EKKO
    ME_COMMTMNT_REQ_RE_C                    Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_REQ_RELE                    Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_PO_REL_C                    Check for Commitment-Relevance of Purchase Orders
    ME_COMMTMNT_PO_RELEV                    Check for Commitment-Relevance of Purchase Orders
    ME_COMMITMENT_STO_CH                    BadI for checking if commitments for STOs are active
    ME_COMMITMENT_RETURN                    Commitment for return item
    ME_CIP_REF_CHAR                         Enables Reference Characteristics in Purchasing
    ME_CIP_ALLOW_CHANGE                     Configuration in Purchasing: Changeability Control
    ME_CIN_MM06EFKO                         Copy PO data for use by Country version India
    ME_CIN_LEINRF2V                         BADI for LEINRF03 excise_invoice_details
    ME_CIN_LEINRF2R                         BADI for CIN India - Delivery charges
    ME_CHECK_SOURCES                        Additional Checks in Source Determination/Checking
    ME_CHECK_OA                             Check BAdI for Contracts
    Reward points if useful
    Regards
    Anji

  • How can i use AME for the new OAF page.

    Dear all,
    I have developed a new OAF page and registered under Employee Self Service.
    How can i use AME for the approval process.
    Appreciate your ideas?
    zamora

    I will try to answer based on my experience of working with iProcurement and AME. It depends on how you want to make a call to AME , directly from OAF Page or from Workflow and your requirement. You didn't specify what you want to show the users on OAF Page and your business requirement.
    Before calling AME Engine from the OAF page or workflow, I guess you did already setup AME Transaction Type and it's Approval Groups, Conditions, Action Types and Rules. Do some testing from AME Business Analyst Test Workbench. Please note that, AME provides lot of PL/SQL API's that you have to call from your programs (java or workflow pl/sql)
    Let's look at the workflow and putting an OAF Page as notification.
    As Sameer said, you have kick-off workflow process from PR of CO and with in the workflow function, you make a call to AME Engine API's with the AME Transaction ID. This transactionId belongs to the AME Transsaction Type that you setup. Based on the rules setup, AME Engine generates list of approvers/approver and stores them AME Tables for that transactionId. Then, it sends a notification to the approver.
    In the workflow, where that notification is defined, in the message body you have to put an attribute(&XX_WF_FWK_RN) of type document/send. And this attribute will have the constant JSP:/OA_HTML/OA.jsp?OAFunc=XX_FUNC&paramId=-&DOCUMENT_ID-. This function is SSWA Jsp function that makes a web html call to your OAF Region.
    If your requirement is to just show the list of approvers on the OAF Page, you may have to call AME API diectly passing your AME TrasnactionId with other parameters. Then AME generates list of approvers and stores them in AME tables with each approver status. You can pickup those approvers using VO and show them on OAF Page.
    Hope this gives some idea.

  • BADI for Customer's own screen for Purchase Requisition.

    Hi All,
    I have a requirement where I need to create a BADI implementation for creating addition screens in the Purchase Requisition Transaction (ME51n/ME52n/ME53n).
    I know there are User exits but we donu2019t want to implement them. Now in case of PO there is a standard SAP given BADI -> ME_GUI_PO_CUST for Customeru2019s own screen but as far as my understanding goes there are no such BADIs for Purchase Requisition.
    Could anyone please advice if I can create a Custom BADI similar to ME_GUI_PO_CUST for PR for adding the screen and throw some light on it like how can this be achieved?
    Thanks,
    Ameesha

    Thanks Darek for replying back and the BADI   ME_BAPI_PR_CUST looks helpful but could you please help me in understanding how can i create my own custom screens within ME51N / ME52N / ME53N tcode using the BADI , ME_BAPI_PR_CUST.
    For example in PO, we have the BADI   ME_GUI_PO_CUST, with several methods like SUBSCRIBE and others which we can make use of for creating screen exits but what in the case of PR fpr BADI  ME_BAPI_PR_CUST. i couldn't find any sample code for implementing this.
    Any help is greatly appreciated.
    Thanks,
    Ameesha

  • Workflow purchase Requisition through transaction ME51.

    Dear Friends,
    Can anybody help me out by telling me a step-by-step process as setup up workflow purchase Requisition. and one more thing i wants to complete this through purchase Requisition transaction .
    scenario is just like,
      firstly i want create the purchase Requisition then this is directly connected for approver through WORKFLOW,
      How to connect the creation purchase Requisition through Transaction and that number goes for take approver through Workflow.
      Can you please you give me one example step by step , so i can do this one.
      Thanks in Advance for help.
    Cheers.
    Puneet.

    You check standard Business object BUS2009 thru SWo1 and standard Workflow Template WS00000038 thru PFTC_DIS.
    <b>Please reward points if useful</b>

  • Change customer for purchase requisition

    Hi gurus,
    i'm trying to change customer number for purchase requisition.
    i tried to enter this code in badi ME_PROCESS_REQ_CUST~PROCESS_ITEM but KUNNR is not changed:
      DATA : ls_item_data   TYPE mereq_item,
             ls_item_datax  TYPE mereq_itemx,
             lv_obj         TYPE REF TO object,
             lv_attr        TYPE string,
             lv_aktyp       TYPE aktyp,
             lv_kunnr       TYPE ekunnr.
      FIELD-SYMBOLS : <fs_lcl> TYPE any,
                     <fs_source> TYPE any.
      IF im_count EQ 1.  " to avoid infinate Loop"
    Access Attributes value of Local Class
    for getting the transaction mode of Line item
    H-> Create
        lv_obj ?= im_item.
        MOVE 'MY_STATE->AKTYP' TO lv_attr.
        ASSIGN lv_obj->(lv_attr) TO <fs_lcl>.
        lv_aktyp = <fs_lcl>.
        IF lv_aktyp EQ 'H' OR lv_aktyp EQ 'V'.        "While creating line item"
    Extracting existing Item Data and Modify the fields
    Requestor Name (AFNAM) & Source of supply details
          CLEAR : ls_item_data.
          ls_item_data = im_item->get_data( ).
         ls_item_datax = im_item->get_datax( ).
         MOVE ls_item_data-ernam TO ls_item_data-afnam.
          lv_kunnr = '0000100000'.
          ls_item_data-kunnr = lv_kunnr.
             ls_item_datax-kunnr = 'X'.
         im_item->set_datax(
         EXPORTING
         im_datax = ls_item_datax ).
          im_item->set_data(
          EXPORTING
          im_data = ls_item_data ).
        ENDIF.
      ENDIF.
    when trying changing other fields like AFNAM for example, the data is changed.
    the customer number exists in KNA1.
    any ideas?
    Thanks,
    Sagit.

    SEARCH  SEARCH  SEARCH  SEARCH  SEARCH  SEARCH  SEARCH
    Good work

  • Issuing storage location for purchase requisition

    Hi All,
    Anyone knew how to have a default issuing storage location on purchase requisition (source of supply tab) created through MRP?
    Thanks.
    Jump

    Hi,
    For this you need to implement BADI MD_EXT_SUP in combination with special procurement type 40 or 45.
    Documentation of this badi:
    Business Add-In for Determination of Issuing Storage Locatio
        Use
        You can use this Business Add-In (BAdI) to control the determination of
        the issuing storage location during stock transfer processing.
        The BAdI is used in the following components:
        Material requirements planning (PP-MRP)
        The BAdI runs both for manual creation of externally procured planned
        orders, and in the MRP during creation of stock transfer procurement
        proposals.
        Purchasing (MM-PUR)
        The BAdI runs as part of the source determination for purchase
        requisitions and during purchasing.
        Standard settings
        o   The Business Add-In is not active in the standard.
        o   The Business Add-In cannot be used multiple times.
        Example
        Sample coding is stored.
        Further notes
        Documentation on BAdI method GET_SUPPLYING_SL
        Documentation on BAdI method GET_PLIFZ
    MZ

Maybe you are looking for