Purchase Order release date

Dear Experts
Can anybody give me table & field of Purchase order release date .
which we can see in Version tab of ME23n
thanks
Nayan Lad

hi,
please refer to the following thread:
TAble for PO Release date
i hope it helps.
arjun

Similar Messages

  • Purchase Order released date field and table name

    Hi,
    Please tell me the  Purchase Order released date field and table name.
    Regards
    Deepak

    Hi,
    Table : EKKO.
    Fields : FRGKE,FRGZU.
    You can get release date of PO from CDHDR  table.
    give object value as your po number and check.dont forget to give leading zeros.
    The udate will be date field and transaction will be me29n for relaesed po.

  • HOW CAN I GET THE PURCHASE ORDER RELEASE DATE

    Dear All,
    HOW CAN I GET THE PURCHASE ORDER RELEASE DATE - any reprot is there?
    Thank you
    Ahmad

    Hi,
    u goto that PO and select Environment on top line .under that select header changes if u click on that u will get entire details who reased when released, date , time etc
    regards,
    Srinivas Kona

  • External purchase order release date is not calculated

    In our live system, when creating external purchase orders from tasks within work orders, system does not calculate the release date of purchase order as explained in the documentation (planned delivery date - planned delivery time). Strangely, when the calculated release date does not lie within the current year release date is assigned to the creation date. When calculated release date lies within the same year, correct release date is assigned to the PO.
    Althogh our development and productive systems have exactly the same patch level, we do not experience this behaviour on our development system. This makes me think that the problem is due to system-dependent setting or some master data such as factory calendar.
    How could we correct the problem? Thanks in advance.
    Ozgen.
    Edited by: Aselsan IT Department on Jun 14, 2010 2:12 PM

    We don't have a release strategy for PReq.
    On the Preq Item -> quantites/ dates tab there are 3 dates: delivery date, request date and release date. In MRP process, the release date is calculated by the sytem based on planned delivery time and GR processing time. The PReq should be changeable by MRP up to the release date. On the release date the system should transfer PReq to SRM and mark the PReqs
    as u2018firmedu2019 u2013 not changeable. This is a SAP standard process. Worked well with EPRTRANS.
    BADI ME_REQ_SOURCING_CUST imethod CHECK_EXTERNAL_SOURCE is already implemented. The BADI controls what requirements to send to SRM.
    We tried putting a check for Release date like: if release date is = < than system date , send PReq to SRM:
       if is_req_item-FRGDT le sy-datum.
       cv_ext_sourcing = cl_mmpur_constants=>yes.
    It does stop new PReqs with release date in future from coming to SRM. However, the BADI is not retriggered for the same PReq when the release date reached.
    Can you please guide me through the implementation steps? If it possible to retrigger the PI message via a scheduled process?
    Thank you

  • Purchase Order Release Report

    Hi,
    Is there a report that I can run that will give me the following information with regards to Purchase Orders released: PO number, Date Entered, Username, Release Code, Release Date and Released By?
    Thank-you in advance.
    Regards,
    Tracy

    Hi,
    I think there is no such report as you have to develop the report through abap . With the useage of the tables i.e. EKKO,EKPO and few more you can have all this information..

  • Purchase order Release Stratergy-Error in Class CL01

    Purchase Order Release Stratergy:
    In CL01(create class) i have created the class FRG_EKKO and saved.Then in CL02(change class) under Basic data-Administrative data we found Assignment field tick is not selected and that is not in changeable mode.
    Because of that reason Error occured like Error in Class in SPRO release stratergy. Release is taking place in Development Server but not in Production server.
    Regards,
    Wilson Babu G

    Hi
    This indicator shows that objects are assigned to this class.
    The indicator is set automatically by the system.
    once you assign the class to any objects then this flag will come automatically.
    Please check if you have assigned the characteristics to the Class in CL02
    Please check if you have assigned the release strategy to the Class in CL24N
    Thanks & Regards
    Kishore

  • Purchase order release history table

    Hi,
      I would like to know the table where we can have history of purchase order releases.
    For example, If the purchase order created and released. Later purchase order release is cancelled. Again i will release the purchase order.
    Even the the release history is not maintained in the table EKBE. I am not aware of the reason for not having the data in EKBE.
    I would like know all the release history would be maintained . In the table EKKO, i can find only  latest release status.
    Can you please throw light on this. Thanks.
    Regards
    Badari
    Edited by: Badari Narayana1 on Nov 19, 2009 8:10 PM
    Edited by: Badari Narayana1 on Nov 19, 2009 8:11 PM

    If memory serves correctly, you have to use change documents for this.
    Read the documentation for FM CHANGEDOCUMENT_READ . You will also find lots of information in the forum.
    Rob
    Edited by: Rob Burbank on Nov 19, 2009 2:22 PM

  • Purchase order release strategy with multiple characteristics

    Hi All,
    We have Purchase order release strategy based on the following characteristics:
    Total Net Order Value
    Purchasing Organization
    Release strategy Type
    a few other custom fields
    We would like to have PO's with release strategy based on a particular Material Group [say X]. I have created a new Characteristic with respect to CEKKO-MATKL and added this characteristic to the same class.
    I have created a new release code [HR] [we need a different person to sign off] and a new release strategy [TR] for which I have assigned the release code HR. In this release strategy, I have set it to get activated for a particular Material Group that does seem to work, but the remaining PO's are not getting triggered for other material groups. For other release strategies, I have left the material group field blank, because they need to be triggered for any material groups except X.
    Could you please let me know if I am missing something  or is there an alternate approach to this ?
    Thank you,
    Satish

    Hi,
    Obviously system will not trigger release strategy in ur case since in the classification data for other strategies u have left it blank excepting X for one strategy.
    Since u have added a new characteristic Material group  and assigned it to class then system expects an input for Material group for triggering release tab.If this is left blank then system by default will not trigger release strategy tab.
    Solution:
    First add all existing material groups in values tab of mat group characteristic then maintain the required set of material groups except X in other strategies in classification data.
    Hope this is clear to you.
    Regards,
    Uzair

  • User Exit for Purchase Order Release Strategy

    Hi,
    I am a little new to this, how do I search for a user exit for purchase order release strategy (TCode ME29N).
    Thanks in advance.
    Mick

    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
    Rgds,
    Naren

  • Rgarding Purchase order release workflow

    Hi Gurus,
    What is the roll of an abaper while using standard workflow for any thing like Purchase order release ?
    If any one worked pls send me the screen shot both functional as well as technical documentation. Becasue our team is new to workflow.
    Already i searched in sdn.sap.com as well as **************** etc........
    In **************** they gave screen shots but some thing is missing . Pls any one worked on workflow( standard sap scenario).forward those documents to me
    Thanks in Advance,
    Nag

    Hi Naganjana,
    In SWDD transaction open the PO std workflow template (WS20000075). Then click on the Basic data icon (hat icon). Go to start events tab --> Click on the Activate (A). Then now open every task. Go to additional data --> Maintain Agent --> General Task. Generate Index. Now come back to workflow screen. You have define agent. As you are going to determine the agent based on PO value you have write your own rule. For this go to PFAC tcode. Create a rule.
    Check out the link below which gives you an idea on how to create a rule.
    [https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d053fe48-6513-2b10-a59f-871923ff99d8]
    Then define this rule in your workflow taks. Do proper binding. Save and activate your workflow.
    Validation : Go to SWE2/SWETYPV tcode. Check if event linkage is active between workflow template (WS20000075) and Event BO : BUS2012 and RELEASESTEPCREATED (Check if the checkbox for event linkage is checked).
    Let me know if you have any queries.
    Regards,
    Raj

  • Purchase order release strategy report

    Dear Gurus,
    We are using purchase order release strategy with classification.
    We have 3-4 level of release. We want to develop a report where we will come to know at which level purchase order is pending for release .
    How to get it ?
    Please provide ur help for the same
    Rgds,
    Saurabh

    Hi,
    Basically in EKKO table there is a field name FRGZU  -
        Release status based on that we can write a logic take the report.
    for example A1,B2,C3 ARE THREE release codes in that if A1 released means with check thable whether A1 released once it is release it will go to next release code it iwll check the status again inthe loop....
    Just tell him the logic to ABAP person they will develop
    Rehgards
    Murugan J

  • Problem in Purchase Order Release Workflow

    Hello Experts,
       I am working in a workflow for releasing PO.In this workflow I have created just one activity step type to release a purchase order.Here I have taken PO(BUS2012) object as input parameter.In the activity step type I am using a custom task(TS99900011).In this task I have used BUS2012 as Business Object and SINGLERELEASE as method.Here I have used 3 terminating events of BUS2012 object.They are Released, Reset and significantly changed. I have just copied the standard task (TS20000166).
      Now my activity step has four outcomes.We can see them in Outcomes tab.
    1.Purchase Order Released(Cgy:External Events)
    2.Not Used(Cgy:External Events)
    3.Purchase Order Changed Significantly(Cgy:External Events)
    4.Processing obsolete(Cgy:Internal Events).
    I have set agent assignment as user Manas.
    Now, when I am testing the workflow with a valid PO number as input the work item goes to my inbox for release the PO as expected.There I can release or reject the PO.But while saving after releasing or rejecting the PO the work item still remains in Workspace Inbox.Any of the four outcomes is not appropriate for the activity.
      Can anybody suggest any solution to overcome the situation.
    Are the external events are really helpful in developing workflow activity?Please suggest.

    Hi Manas,
    There is one option, where you can stop the workitem and even entire workflow.
    Use Fork for parllel processing
    Have a Wait step with BUS2105-Significantlychanged event and outcome to the end of workflow.
    Thanks,
    Sudhir.

  • Purchase order release workflow - urgent

    Hi friends
    When iam creating purchase order it trigger the workflow WS20000075 for releasing purchase order in that purpose what can i do..
    How can i set the Agents
    How can i trigger the events - i think in that purpose using pftc we trigger the workflow.. so i need clear steps from beginning onwards..
    my exact requirement
    once i create purchase order, the workflow will be triggered..
    after that the mail goes to the approver.. if he/she click that mail purchase order release statement want to be open.. after that he/she release purchase order it will goes to the next level..anyone give the step by step procedure..for that
    Thanks
    Gowrishankar

    yes prabakar.. but iam confused..
    You can get step by step workflow for PO using standard workflow
    Release of Purchase Order :WS20000075
    And for two levels of approvals you have to configure in SPRO the path is
    Purchase Order:
    SPRO> Material Management->Purchasing->/Purchase order-->Release procedure ---> Procedure with classification ---> set up procedure with classification ---> double click on Release strategies and Workflow.
    If you don't know about this configuration, you have to confirm with your MM consultant.
    after finish this iam triggering events using pftc
    in that pftc iam choosing business object bus 2012 for po release..
    i think thats enuf..
    After that it is possible to trigger workflow.. when iam create purchase order..
    Thanks
    Gowrishankar

  • Dead Line Monetering in Purchase Order Release Workflow

    Hi Experts,
                     I have  activated Standard Purchase Order Release workflow and it works fine now i have a requirement of Dead Line monetering for 2 days. In Standard Release Activity TS20000166 if i give 2 days in Latest End.
    Will it work in such a way that if the first approvar does not take any action for 2 day then it automatically esculates to the next person in the release strategy.
    Or should i use Modeled Deadline for esculation to next Level.
    Regards,
    Hari

    Hi,
    If you just have 2 days on the latest end tab, the workflow will only send a deadline notification to the current agent and WILL NOT escalate.
    You have to use modelled deadline and in that branch route the workflow to the next approver based on your agent determination rules.
    Satish

  • No of levels in purchase order release more than 8

    Dear All,
    We have a situation where some of our purchase orders need to be approved by more than 8 people.Can any one help me in telling-> whether we can create release strategies having more than 8 levels of approvals.If yes how to do it since I could see only max of 8 levels of approvals in the release strategy configuration for purchase order(release strategy with classification).
    Regards,
    Feroz Choudhury

    Hello,
    As mentioned by Uttkarsh, It is not possible to go beyond 8 levels in release strategy.
    More than 8 levels of approval is not a best practice, if your requirement still demands this explore the options of using Workflow functionalities in ECC or if approval is complex suggest SRM where you can handle n-level approval.
    Hope this helps.
    Thanks
    Ashu

Maybe you are looking for