HOW TO Purchase Reqisition Release date ( PR release date )

CAN abybody tell me how to find puchase requisition release date ( PR release date )

Hi Sandeep,
Check Tables : <b>EBAN, EBKN.</b>.
Hope this will helpful.
<b>Reward is useful</b>
Regards,
sunil kairam.

Similar Messages

Create custom data when releasing a Purchase Order

Hello people,
The customer uses ME28 to release the Purchase Order.
They have, for instance, two release estrategies: W1/01 and W2/02, that differ about the price.
The scenario is:
When the customer releases a Purchase order from W2/02 strategy using ME28 transaction, we need to do some verifications in Z tables and create a record in another Z table. If for some reason the purchase order will not be released, this Z data does not have be saved.
And if some error occurs and the data don´t be saved, the estrategy must remain blocked (not released).
In which EXIT is the best point to do this?
Thanks a lot!

hey
try these 2 user exits
MM06E005 - ZXM06U43 which is called from exit EXIT_SAPMM06E_012. This code is hit at the time you check or save.
M06E0004 - Changes to communication structure for release purch. doc - EXIT_SAPLEBND_002

How to restrict to unrelease the purchase requisition when po is released.

Hi Expert's,
please suggest me how can I restrict to unrelease the purchase requisition when Po is released.
Pls guide me .
Regards,
Sanjay

Hi,
I don't think there is standard settings where u can restrict PR changes when the PO corresponding to this is released.
You have 2 options: One is to restrict all the changes once the PR is released. This can be done in the release indicator (Changeability - 1). Once this is set, PR cannot be changed after release irrespective of whether PO is created or released.
Second option is to go for an enhancement (You may use ME_PROCESS_REQ_CUST) and write a logic to see the release indicator of corresponding PO and restrict the changes.
Regards,
Sudeep.

Purchase Requistion release date as system date

Dear Experts,
Our Requirement is the top management want to know time taken to release a purchase requisition,means the duration
between purchase requisition creation date to release date.
here user are manually changing the release date to system date to know duration exact time duration between the creation date and release date,so user requirement is the release date should be system date so he can easily understand when the requisition is released.
we are thinking that,if we make the release date as system date,please suggest me.
Thanks in Advance.
Varun

Dear Madhu,
1.)     Whenever you are creating a new PR system will automatically take that PR creation date as system date.
2.)     All the releases in SAP System will be recorded as Item/Header change and system will maintain their history in Item/Header change details
3.)     If your requirement is to track the duration between creation, release of levels it can be very much possible by creating a quary it self.
Regardsu2026
Srini Rao

Any ideas on how to control the amount of sustain pedal data that Logic Pro 9 records? Every time I press the sustain pedal down, it records 4 sustains. Same thing when I release the pedal. Thanks!

Any ideas on how to control the amount of sustain pedal data that Logic Pro 9 records? Every time I press the sustain pedal down, it records 4 sustains. Same thing when I release the pedal. Thanks!

This gets confusing, you have two Macs with different issues and two pedals with different issues? First let's sort out what's what. So, do the issues come from the pedals or from the Mac software? To find out, simply switch the pedals and note their behaviour. No change: it's the software, change: it's the pedals (imho the most likely scenario).
Second, what kind of pedals are they? Can you name the type of pedal too? The Yamaha what and the Mgear which?
Third, with the 4 fold data problem, are the doubled events simultaneous, or a few ticks apart, or more?
Also, you have no MIDI keyboard? Are the pedals both "standalone"?
I think you have to sort this problem at its' source, which are the pedals. You could, if push really comes to shove, perhaps create some sort of ingeneous/elaborate transformer setup in the environment to filter the extra messages, although with the 4/4 sustain events that may not even be possible. With the "stepped" events you could set up a filter to just block all events with values 20-110 or so.
But much better would be to configure the pedal(s) correctly.

How to delete the old schedule line release in apo

How to delete the old schedule line release (from current date) in apo which is having schedule firmed?
Please suugest.
Sunil

How is it possible to delete old purchasing schedule lines in APO (that do not exist in R/3)?
Though used successfully before, /SAPAPO/CCR will not reconcile our discrepancy in this case.
Thanks in advance,
Jim

Purchase Order not subject to release strategy

Good day everyone!
I've created one release strategy for all my purchasing documents. The characteristic is net value, and the value of this characteristic is >=0.00. Meaning, ALL purchase orders are subject to release strategy.
After I did the release strategy in SPRO, I created a few PO and when I tried to release them, I got this message: "Purchasing document 45xxxxxxxx not subject to release strategy".
My question is: How to assign purchasing document to release strategy?
Please help. Thank you in advance.
Anisah

hi
yes you have to use table CEKKO for PO release strategy , now , in PO you can't create without clasification so it will be applicabe for whole PO not for line items ,
now below i am giving u one by one steps , follow and let me know .
The release code is a two-character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
CT04 - Create Characteristic   e.g. NETVALUE
Click Additional data Table name CEKKO      Field name GNETW    and press enter
(for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
In the Basic data (X refers to tick),
X    Mutliple values
X    Interval values
In the Value data, in the Char. value column, type >10000 and press enter
Save your data
CL02 - Class
Class - Create REL_PUR
Class type - 032
Click Create
Description - Release Procedure for Purchase Order
In the Same Classification section, click Check with error
In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
OMGS - Define Release Procedure for Purchase Order Type
Release Group - New entries
Rel.group   Rel. Object   Class                 Description
02                                 REL_PUR        Rel. Strategy for PO
Release codes - New entries
Grp         Code
02           01
Release indicators
Release indicators           Release        Description
      0                                                        Blocked
      1                                     X                Release
Release Strategy
Release group   02
Rel.strategy    01
Release codes   01
Release status   0
                        1
Classification   Choose your check values
OMGSCK - Check Release Strategies
(make sure there are no error messages)
Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order.
The person with the release authorization have to use ME28 to release the Purchase Order.
regards
ravikant dewangan

Purchase Order not subject to release strategy for contract rel. strategy

Hello, I am trying to set release strategy for contracts (TCODE: ME31K). I have created characteristic, which use table CEKKO and field name BSTYP in Addnl data tab. I have checked values, and they are correct. Then I have assigned in release strategies in classification view value contract. But when I try to check release strategy in ME31K with green flag, it display error: Purchase Order not subject to release strategy. (I have tried to do the same strategy in purchase order, of course with value Purchase order, and it works nice).
So I have checked this release strategy with this codes:
CL24N ok,
CT04 ok,
CL30N ok,
CL20N ok,
Release simulation in release strategy works,
Then I found out that I should check SE38, SE37 but I do not understand how to use them (according: Purchasing Document Not Subject to Release Strategy).
Thank you for your help in advance.

I haven't said to use EKPO table in characteristics. You have to use CEKKO - BSTYP in characteristics.
I've just said the compare the value which you have given in Release strategy - Classification and EKPO table for the particular contract.
Also compare your release strategy settings with many existing documents in SCN.
Check your Classification should be like that.
You may see the error message in ME31K. Just save the contract then go to ME32K/ME33K or ME35K you can see the release strategy will effect for the contract.

Purchase requisition : problem with check release Strategies

Hi all,
i created a new class, new release group, new release codes etc. I think all is ok but when i launch the transaction OMGQCK for check release Strategies the system give me an error in node 'Check re release indicators' : Define a release indicator for the status "released".
But how can i do that, i created two release indicator : 'X' for blocked and 'V' for launched but what are the options for purchase requisition ?
Is there a special value to give the release indicator 'released' ?
Thanks for your help.
Edited by: ToraTora on Mar 31, 2011 5:46 PM

Hi,
Goto SPRO -> Materials Management -> Purchasing -> Purchase Requisition -> Release Procedure -> Procedure with classification -> Setup Procedure with Classification
select release indicator
by default, you will be having the following release indicators in the system,
1     Request for quotation
2     RFQ/purchase order
3     RFQ/PO no change of date
4     RFQ/PO no changes
A     Fixed RFQ
B     Fixed RFQ/purchase order
X     Blocked
please check whether you have got these or else create and then assign them to the release strategies.

Purchasing document not subject to release strategy

Hi
I created Scheduling Agreement using BAPI ' BAPI_SAG_CREATE ' . Document number created successfully but when go to release release strategy in
ME33L then it gives information 'Purchasing document not subject to release strategy ' . How i resolve this issue using BAPI .
Regards,
Suvakant

Yes it is created by using same input for ME31L .
report zsa_creation_test.
data:   poheader     type bapimeoutheader,
        poheaderx    type bapimeoutheaderx,
        poitem       type bapimeoutitem occurs 0 with header line,
        poitemx      type bapimeoutitemx occurs 0 with header line,
        i_bapireturn type bapiret2 occurs 0 with header line.
data : i_bapireturn1 type bapiret2 occurs 0 with header line .
data: l_ebeln type ebeln.
poheader-comp_code   = 'ABC'.
poheader-doc_type     = 'ZPA2'.
poheader-creat_date    = '20140507'.
poheader-created_by     = 'ABAP'.
poheader-ITEM_INTVL = '00010' .
poheader-vendor       = '0000100176'.
poheader-purch_org = 'AB01'.
poheader-pur_group = 'RR1'.
poheader-currency    = 'INR'.
poheader-doc_date    = '20140520'.
poheader-vper_start    = '20140520'.
poheader-vper_end     = '20200507'.
poheader-incoterms1    = '1'.
poheader-pmnttrms     = 'YP04'.
poheaderx-comp_code    = 'X'.
poheaderx-doc_type   = 'X'.
poheaderx-creat_date = 'X'.
poheaderx-created_by = 'X'.
poheaderx-ITEM_INTVL = 'X' .
poheaderx-vendor = 'X'.
poheaderx-purch_org     = 'X'.
poheaderx-pur_group     = 'X'.
poheaderx-currency = 'X'.
poheaderx-doc_date = 'X'.
poheaderx-vper_start = 'X'.
poheaderx-vper_end = 'X'.
poheaderx-pmnttrms = 'X'.
poitem-item_no = '00010' .
poitem-material    = 'RT010006'.
poitem-plant = 'PL02'.
poitem-stge_loc     = 'ST01'.
poitem-trackingno    = 'F'.
poitem-rel_create_profile    = 'ZAB1'.
poitem-jit_relvt = '1'.
poitem-target_qty    = '10.000'.
poitem-po_unit = 'EA'.
poitem-orderpr_un    = 'EA'.
poitem-conv_num1 = '1'.
poitem-conv_den1 = '1'.
poitem-net_price = '10.000000000'.
poitem-price_unit    = '1'.
poitem-tax_code    = '00'.
poitem-info_upd    = 'C'.
poitem-item_cat =   '0'.
poitem-acctasscat     = ''   .
poitem-apo_planning     = '1'.
append poitem .
poitemx-item_no = '00010'.
poitemx-item_nox = 'X'.
poitemx-material = 'X'.
poitemx-plant      = 'X'.
poitemx-stge_loc    = 'X'.
poitemx-trackingno = 'X'.
poitemx-rel_create_profile = 'X'.
poitemx-jit_relvt      = 'X'.
poitemx-target_qty    = 'X'.
poitemx-po_unit        = 'X'.
poitemx-orderpr_un    = 'X'.
poitemx-conv_num1        = 'X'.
poitemx-conv_den1      = 'X'.
poitemx-net_price       = 'X'.
poitemx-price_unit    = 'X'.
poitemx-tax_code    = 'X'.
poitemx-info_upd    = 'X'.
poitemx-item_cat    = 'X'.
poitemx-acctasscat = 'X'.
poitemx-apo_planning = 'X'.
append poitemx.
call function 'BAPI_SAG_CREATE'
exporting
    header             = poheader
    headerx            = poheaderx
importing
    purchasingdocument = l_ebeln
*   EXP_HEADER         =
tables
    return             = i_bapireturn
    item               = poitem
    itemx              = poitemx.
call function 'BAPI_TRANSACTION_COMMIT' .

Purchase order don't be release,

Dear all,
I create a purchase order and use ME29N to release it ,
But system come out a message
"Purchasing document 7083000082 cannot be released.
Message no. MEPO823"
Can you help me how to deal with this issue ?
Thanks,
Alex

You need to check two thing:
Firstly go to ME23n and check wheather Po has the release tab at header level If yes then what is the status.
Secondly, I hope release strategh has alreadybeen configured in your system check the charecteristics that you have taken and match it wuth your PO. Then GO to CL24n and check whether you have maintain the same data against your strategy or not
If not maintain then main the data in CL24n
Then go to the POand make a small change releated to your charecteristics.
regards
Anamika

How to Get Spool ID after PO release. (To send PDF for ext E-mail)

Hi Experts,
I am new to Email sending from SAP.
I am facing a big problem from many days. I am in a new support project.
I have a issue that when ever a PO is released from ME23N or ME28 it should send a mail to vendor.
This is working fine in Development including delivery report or failed report back to approver...
I dont know where is PRD and who is doing that,
But my support manager says that only some PO's are sent to vendors not all...
everytime they approve only some emails sent to vendors...!
But every PO is same and for same vendor's...
Even failure & delivery messages are missing for (sent failed email's)
But after all I observed only one thing that we have a select statement....
DATA: GS_RESULT TYPE ITCPP.
DATA : L_DATE(9).
DATA : BEGIN OF LT_TSP01 OCCURS 0,
          RQIDENT LIKE TSP01-RQIDENT,
          RQCRETIME LIKE TSP01-RQCRETIME,
          DATE(8),
          TIME(8) TYPE N,
          END OF LT_TSP01.
SELECT RQIDENT RQCRETIME FROM TSP01 INTO CORRESPONDING FIELDS OF
                       TABLE LT_TSP01 WHERE RQCRETIME LIKE L_DATE
                                        AND   RQIDENT EQ GS_RESULT-TDSPOOLID.
IF SY-SUBRC = 0.
(All Email sending code)(including delivery & failure delivery)
Endif.
So I suspect it is not picking up the Spool request from this Table TSP01 or may be not updated to this table.
I have searched in SCN, I have seen may E-mail Codings
But every one says to get Spool- ID & Convert to PDF,,,
My Question is How to get Spool ID correctly and tell me how it is updated. when a PO released by ME23N or ME28.
please any one clear my doubt as I am completely helpless here.
Thanks in advance,
Dunlop.

Hi,
Is it a SMart form.....
If it is a smartform, then Smartfom interface itself has a spool id parameter....
you can directly het that from this parameter...
    CALL FUNCTION "FMa Name'
      EXPORTING
        control_parameters = wsl_control
        output_options     = wsl_outpt
        user_settings      = ''
        wtg_itemdetails    = tl_itemdet
         wtg_vttp              = l_vttp
      IMPORTING
        job_output_info    = sl_spooldet
      EXCEPTIONS
        formatting_error   = 1
        internal_error     = 2
        send_error         = 3
        user_canceled      = 4
        OTHERS             = 5.
    IF sy-subrc <> 0.
    ENDIF.
The inporting parameter sl_spolldet will have the Spool id.
and you fetch by, using the below mentioned way..........
    READ TABLE wsl_spooldet-spoolids INTO wsl_wa_spool INDEX 1.
      IF sy-subrc = 0.
          Convert it into PDF using 'CONVERT_OTFSPOOLJOB_2_PDF'
          then attach it and send a mail.....with all properties set such as Delivery report....
      endif.
If you have any issues, please let me know........
Thanks & Regards,
Vamsi

How to delete the old schedule line release?

Hello,
How to delete the old schedule line release in apo?
Generally GR has to be carry out schedule line release in r/3 which reduces the Schdule line release.
But i do want do GR against old schdule line release instead i want to delete the old schdule line release.
Please suggest.
Regards,
Sunil Patil

Sunil ,
/sapapo/cmds_del is the tcode to deleted sales scheduling agreement confirmations and releases
/sapapo/display_conf is the tcode for displaying sls. sch.agr confirmations and releases
The above two are in the supply chain collaboration menu
/sappao/cmds_sc02 is the tcode to delete sales scheduling agreements . This tcode is in the application specific master data menu
Thanks
Saradha

Original posting date after releasing in ea05

Hello all,
When you release an outsorted print document in Transaction EA05, a dialog box appears in which you enter the posting parameters that are required for the release process.
the number of the original print document, posting date, and document date for example are changed.
How can I know what the original data were? for example, what was the original posting date before releasing?
I will appreciate any help.
Thank you very much.
Hussam.

Hello Ravi,
The user wants to check what was the original posting date before releasing the document in EA05.
event will not help. is there another way?
pay attention that the user released the print document, and during the process of the releasing he changed the posting date.
and after he finished the process of relesaing he wants to check what was the posting date before he released.
thanks...
Hussam.

All po's released in a given date range:EXIT M06E0004,logic?

Hai,
After lot of browsing in the forum,I came to the conclusion that to capture ALL RELEASED PO in a date range one ahs to use
CDHDR/CDPOS or implement EXIT and populate ZTABLE.
Now i have seen the exit M06E0004 triggers upon lot of actions(change PO / release PO etc)..
Now how should I develop a Logic so as to identify if the user action was to RELEASE the PO when the exit is triggered..
I can see that the values of RELEASE in table EKKO dont change while in the exit,though the user RELEASES the PO.

Whether the specified fields are available in the Structure "CEKKO"? Standard Structure of CEKKO doesn't have these fields.
If the structure having these fields, CEKKO-FRGZU holds the status of Release during this enhancement.
Regards
Vinod
Edited by: Vinod Kumar on Apr 29, 2010 4:05 PM

HOW TO Purchase Reqisition Release date ( PR release date )

Similar Messages

Maybe you are looking for