Print-Screen of PR Release STRATEGY

Please give me PR Release Strategy With Print Screen and Basic Concept
ASAP.

Please read the forum rules and use the search button.
ASAP

Similar Messages

How to Display PO Release Strategy in Enjoy Screen

Dear all,
I have a PO with a release strategy, which contain several release codes to release the PO (i.e. M1 & V1).
However, I am only able to display the release code (i.e. M1 & V1) in t-code ME23. I could not do the same in the enjoy screen t-code ME23N for the same PO number.
In the item level, there should be a tab with release strategy to display the PO release strategy (similar to PR), but it is not appearing.
Could anyone tell me what is the problem here? I just could not find the tab or menu to view the release strategy of a PO in the enjoy screen. Similar goes to other PO. I could not view it as well. But in the old screen, I could view it.
Thanks a lot.

Thanks 4 the reply Rahul.
I understand that it is only possible to release at header level. What my problem is that I am unable to view the release strategy (which code to release and who to release) for the PO in enjoy screen.
In my earlier thread replying to Ankur, I am simply describing that I could just select a line item, click on the release strategy button and the release strategy is displayed. A different line item with different value generated a different release strategy of course. Different amount require different set of release strategies, usually more level of approvals.
So, actually this question is not about where or how I can release a PO, but actually I could not view who is releasing for a PO in ME23N.
I even simulate it in the development server and still the same thing happen. Is it the same for everyone else? If yes, how to view who is releasing the PO in ME23N? Version of system is 4.7.
Thanks and appreciate if anyone could help.

The PO was printed straight away without going through Release Strategy.

Hello,
Purchase order was raised in March for over Rs 1,000,000/- and went through the Release Strategy for printing.
The value of this order was changed today - about Rs 7,000/- was added in the purchase order.
The Purchase Order was printed straight away without going through Release Strategy,
In a customization we have maintained the Release strategy for the Purchase order
Please provide the solution on this issue.
Regards
Sarin
Edited by: sarin toms on Nov 26, 2008 1:57 PM

Dear,
Check at....OLME-->PO->Release Procedure->Configure Release procedure for PO> Release Indicator--> Pl. Check In Changebility of Release Procedure after release...here you have to give the option " 4".....and percentage of changebility also you have to take care...
Apart from that...in OLME--> Messages--> Message output---> Message determination...you have to fine tune your message type for Change mode...
Changeability 4 and percentage 0 will reset the release ONLY when the value of the PO increases. Any other change including decrease in value will not reset the release.
You can use the release user exit. If the PO is in change mode and Save option is selected, then increase the value in the user exit (This does not increase the PO value actually, just fools the release strategy into thinking that the value has increased).
Try with changeability 6 instead of 4. 4 will not reset the strategy if the PO is outputted (printed, emailed, etc)
Please refer the note 662993 and 365604
Regards,
R.Brahmankar

Print Preview Purchase Order with release strategy

Hi gurus,
With release stratregy you can not print a PO before release through ME9F. The system will give error message 'No corrosponding document found'. However, you can print PO through 'Print Preview' by clicking on Print icon in ME22N, we need that "Print Preview"doesn't print PO without release. System it shouldn't print.
Thank you!

Hi,
Hope you are using Z output type & print program for PO printing. You can restrict this by modification in program. Please do it with help of abaper.
Regards,
Sandeep

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

Print of PO Before release

Dear All,
Please help me in one scenario.
My client want PO print before release.
He want to take print of po before release so that he can bargain with vendor & make changes accordinglly before release.
Actually he doesn't want to release the po again & again.
Please help me out
Regards
SANTOSH KADAM.

Yes you can print the PO before release . For that in release strategy against the "Release Indicator" tab see the check box against the colomn"Released". If the box is checked against the final release indicator ,than uncheck it and check the same against the first Release indicator (Blocked). This will allow yoy to print out the PO in blocked state also. But as per standard we do not follow this practice.

How to setup a release strategy for store generated purchase order

Hi there,
Does anybody know how to setup a release strategy for store/plant generated purchase order? I have a request from our client, but I never cross this before. Please help and let me know the step with every single detail.
Greatly thank for your help.
Kind Regards,
2tea

Please go thru the below Release Procedure and check whether you have maintained all the settings properly.
PO RELEASE STRATEGY
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 01
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,
Ashok

Req:Print the PO before release

Hi all,
My requirement is to print the po before release.I have searched for exits/badis but could not find any.
Can anyone help me out how to print the PO before release

Yes you can print the PO before release . For that in release strategy against the "Release Indicator" tab see the check box against the colomn"Released". If the box is checked against the final release indicator ,than uncheck it and check the same against the first Release indicator (Blocked). This will allow yoy to print out the PO in blocked state also. But as per standard we do not follow this practice.

PO release strategy not triggered after PO printout

Hi Experts,
I have configured PO release strategy and have given 10% tolerance to PO value.
When I change PO value (more than 10%) after releasing the PO, but before taking Print out of PO, the system triggers new release strategy.
But when I change the PO value (More than 10%) after taking PO print out, system do not trigger the new release strategy.
I want the system to trigger new release strategy after PO print out (if its going beyond the tolerance).
Please help.
regards,
Anand

Hi Anand,
you cannot reset the release once the PO is printed.
When the purchase order is printed/faxed the vendor will deliver the goods. Therefore it would make no sense if the system resets the strategy.
Please ensure that changeability of the release indicator should be 5 or 6.
Sanjeev

Print PO Form before Release PO

Hi Expert,
I have some problem Print PO Form.
PO cannot print automatically before release PO. (Not release yet)
How can I do ?
Thanks,

Hi,
Yes you can print the PO before release . For that in release strategy against the "Release Indicator" tab see the check box against the colomn"Released". If the box is checked against the final release indicator ,than uncheck it and check the same against the first Release indicator (Blocked). This will allow yoy to print out the PO in blocked state also. But as per standard we do not follow this practice.
Regards ,
Rahul.

Change in Purchase Order Release Strategy Values

Dear All,
I am in process of changing Purchase Order release strategy values.
I have following release strategy -
                       Current Value                  (Proposed Value)
Level 1 -         Upto INR 0.1 Mn               (Proposed value - Upto 1.0 Mn)
Level 2 -         From 0.11 Mn to 0.5 Mn   (Proposed Value - From 1.01 Mn to 5.00 Mn)
Level 3 -         From 0.51 Mn to 1.0 Mn   (Proposed Value - From 5.01 Mn to 10.0 Mn)
Level 4 -         Above 1.0 Mn                  (Proposed Value - Above 10.0 Mn)
My questions are -
1) Will this change affect the existing Purchase Orders (already created) which are not yet released?
2) Will this change affect the existing Purchase Orders (already created) which are released?
3) Are there any risk factors?
Can you pl. put light on above questions?
Regards,
Prashant Kolhatkar

Hi,
Actually, what you had given is not enough to determine if the existing PO will be impacted or not
If you are just changing the classification but not changing the number of release level of the release code in the release strategy, the partial released PO will not be impacted unless there's PO changes. PO that are released will definitely not be impacted unless there are changed.
In general, after a release strategy is determined for PO, SAP will retrieve the latest list of release code of that release strategy for display for that PO. If this list never change (mean you only change classification of the release strategy), then they will not be apparent to the user. But if this list change (you add new release code, replace existing release code or remove release code), then you will see some discrepency on screen as you will only see the modified list of release code and not the old list of release code
Hope this help

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 E-mailing with Release Strategy

Hello,
We are experiencing an issue when e-mailing a Purchase Order which has a release strategy. When the order is released, the confirmation e-mails are going to the person who releases it when it is supposed to go to the person who has created the P.O. We are using a Smartform P.O. based on /SMB11/BL_MM_PO_L and print program /SMB40/FM06P. I must note that there was a bug found in the aforementioned print program and before that was fixed e-mailing would not work at all.
We have also attempted to use all combinations of standard unmodified print programs and standard unmodified smartforms and have had no luck at getting the confirmation e-mail to send to the correct person this way either.
SAP has recommended that we use program SAPFM06P with form Medruck. While this combination does work correctly, Medruck is not a Smartform. Has anybody here used a smartform Purchase Order with a release strategy and had the confirmation e-mail send to the created and not the releasor?
Below is a list of the print programs and forms we have tried in various combinations. We are running ECC6/Basis 7
Print Programs:
/SMB11/FM06P
/SMB40/FM06P
SAPFM06P (Sapscript Only)
Forms:
/SMB11/BL_MMPO_L
/SMB11/MMPO_L
/SMB40/MMPO_L

Hi,
Purchase order via e-mail in SAP sys,the configurations and pre-requisites are follow:
1. You must maintain an e-mail address in the address in the vendor master.
2. The same applies to your own user master. You also have to specify an e-mail address there in order to identify the sender.
Note that it is not possible to change the e-mail address of the vendor via the SAP purchase order transaction (ME21N, ME22N, and so on). The system only uses the e-mail address of the vendor that is maintained in the vendor master!
3. For the output type for default values, a communication strategy needs to be maintained in the Customizing that supports the e-mail. You can find the definition of the communication strategy in the Customizing via the following path: (SPRO -> IMG -> SAP Web Application Server -> Basic Services -> Message Control -> Define Communication Strategy). As a default, communication strategy CS01 is delivered. This already contains the necessary entry for the external communication. Bear in mind that without a suitable communication strategy it is not possible to communicate with a partner via Medium 5 (external sending).
4. Use the standard SAP environment (program 'SAPFM06P', FORM routine 'ENTRY_NEU' and form 'MEDRUCK') as the processing routines.
5. In the condition records for the output type (for example, Transaction MN04), use medium '5' (External send).
6. You can use Transaction SCOT to trigger the output manually. The prerequisite for a correct sending is that the node is set correctly. This is not described here, but it must have already been carried out.
7. To be able to display, for example, the e-mail in Outlook, enter PDF as the format in the node.
For more details, check SAP note:191470
Regards,
Biju K

How to use Print Screen function (part deux)?

The previous thread for the Print Screen function has been marked as read only, and won't allow any replies. I tried all of the suggestions (PrtScr, CTRL + C + PrtScr, etc.) and then CTRL V into MS Paint, but Print Screen still doesn't work on my machine.
I'm running Win 7 on a HP Pavilion laptop cv7-6b32us. I suspect there's a switch somewhere in Win 7 or HP that allows the key to be turned off. I know of this because my previous employer did not want anyone doing print screens due to HIPAA violations. Thus, the functionality was turned off. Those of us in I.T. were provided a third-party software that aloowed us to do the same function, but it was not released to the physicians or nursing staff. If I have to, I'll go out and buy the software. I really need this functionality for a class I'm taking.
Thanks!
This question was solved.
View Solution.

Kurt, welcome to the forum.
Here is a video to show you how to use the Snipping Tool:
Please click the "Thumbs Up+ button" if I have helped you and click "Accept as Solution" if your problem is solved.
Signature:
HP TouchPad - 1.2 GHz; 1 GB memory; 32 GB storage; WebOS/CyanogenMod 11(Kit Kat)
HP 10 Plus; Android-Kit Kat; 1.0 GHz Allwinner A31 ARM Cortex A7 Quad Core Processor ; 2GB RAM Memory Long: 2 GB DDR3L SDRAM (1600MHz); 16GB disable eMMC 16GB v4.51
HP Omen; i7-4710QH; 8 GB memory; 256 GB San Disk SSD; Win 8.1
HP Photosmart 7520 AIO
++++++++++++++++++
**Click the Thumbs Up+ to say 'Thanks' and the 'Accept as Solution' if I have solved your problem.**
Intelligence is God given; Wisdom is the sum of our mistakes!
I am not an HP employee.

Upload Release strategy into T16FW table

Hi Guys
I am trying to uplad data into T16FW table for release strategy but this program is not working , I would be thankful if anyone correct it please.
*& Report Z_UPLOAD                                    *
REPORT ZUPLOAD.
INCLUDES                                            *
*INCLUDE ole2incl.
*&   TYPES                                            *
TYPES: BEGIN OF ty_t16fw,
       frggr TYPE T16fw-FRGGR,
       frgco TYPE T16fw-frgco,
       WERKS TYPE T16fw-werks,
       otype TYPE T16fw-otype,
       objid TYPE T16fw-objid,
       END of ty_t16fw.
TYPES: BEGIN OF ty_titles,
       title(20) TYPE c,
       field(20) TYPE c,
       END OF ty_titles.
*&   INTERNAL TABLES                                  *
DATA: t_t16fw TYPE STANDARD TABLE OF ty_t16fw,
      t_titles TYPE STANDARD TABLE OF ty_titles.
*&   FIELD-SYMBOLS                                    *
FIELD-SYMBOLS: <fs_t16fw> LIKE LINE OF t_t16fw,
               <fs_titles> LIKE LINE OF t_titles,
               <fs> TYPE ANY.
*&   VARIABLES                                        *
DATA: w_tabix TYPE sy-tabix,
      w_titles TYPE sy-tabix,
      w_line TYPE sy-tabix,
      w_field TYPE string,
      filename TYPE string,
      path TYPE string,
      fullpath TYPE string.
DATA: data_titles TYPE REF TO data.
*DATA: e_sheet TYPE ole2_object,
     e_activesheet TYPE ole2_object,
     e_newsheet TYPE ole2_object,
     e_appl TYPE ole2_object,
     e_work TYPE ole2_object,
     e_cell TYPE ole2_object,
     e_color TYPE ole2_object,
     e_bold TYPE ole2_object.
*&   SELECTION-SCREEN                                 *
SELECTION-SCREEN BEGIN OF BLOCK b1.
PARAMETERS: p_file TYPE rlgrap-filename,
p_objid TYPE t16fw-objid. "no-extension no intervals OBLIGATORY,
SELECTION-SCREEN END OF BLOCK b1.
*& START-OF-SELECTION                                *
START-OF-SELECTION.
PERFORM get_titles.
PERFORM get_data.
*& AT SELECTION-SCREEN                                *
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
CALL METHOD cl_gui_frontend_services=>file_save_dialog
    EXPORTING
      window_title      = 'Select archivo'
      default_extension = 'xls'
      file_filter       = '*.xls'
    CHANGING
      filename          = filename
      path              = path
      fullpath          = fullpath.
IF sy-subrc EQ 0.
    p_file = fullpath.
ENDIF.
*&      Form get_titles                              *
FORM get_titles.
CREATE DATA data_titles TYPE ty_titles.
ASSIGN data_titles->* TO <fs_titles>.
<fs_titles>-title = 'Grp'.
<fs_titles>-field = 'FRGGR'.
APPEND <fs_titles> TO t_titles.
<fs_titles>-title = 'Code'.
<fs_titles>-field = 'FRGCO'.
APPEND <fs_titles> TO t_titles.
<fs_titles>-title = 'Plnt'.
<fs_titles>-field = 'WERKS'.
APPEND <fs_titles> TO t_titles.
<fs_titles>-title = 'Ob'.
<fs_titles>-field = 'OTYPE'.
APPEND <fs_titles> TO t_titles.
<fs_titles>-title = 'AGENT ID'.
<fs_titles>-field = 'objid'.
ENDFORM.                    "get_titles
*&      Form get_data                                *
FORM get_data.
SELECT frggr frgco werks otype objid
INTO TABLE t_t16fw
FROM t16fw
WHERE OBJID EQ 'GAIW'.
objid eq p_objid.
ENDFORM.                    " get_data
Regards
Chris

Hi paedro,
I think coresponding events are triggered by SAP automatically when you release/create a PR. What you need to do is just do Event Type Linkage of those events with your Workflow .
For this you can use transaction SWETYPV
Also see
Please check the configuration for Release groups (Path SPRO->Materials Management->Purchasing->Purchase Requisition->Release Procedure->Procedure with Classification->Set up Procedure with Classification->Release Groups). In this, you should check 'OverReqRel'.
Check if you are using workflow template WS20000077 (Workflow for overall release of requisition) with object type 'BUS2105'.
Workflow template WS00000038 (Workflow for requisition release) with object type 'BUS2009', is used for releasing at the item level.
regards,
Hareesha k

Print-Screen of PR Release STRATEGY

Similar Messages

Maybe you are looking for