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

Similar Messages

Send purchase order e-mail with release strategy

Hi!!
I have a problem with sending e-mails in purchase order that are blocked with release strategy.
I create a purchase order that is block for the release strategy, then I release it. This is working OK, but I can't send an e-mail with this released puchase order, to do it, I have to modify something in the purchase order.
Somebody knows what is happening?
I would like to send e-mails without previous modification of the purchase order.
Thanks for your help.

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

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 Order generate mail with custom attachment

Hi
I have a requirement to create an output type for Purchase Order document. The mail should be sent with attachment file .CSV, which I will generate in my own Z- program. As I understand I have to create a new output type (NACE), make the customizing for output determination on vendor level (VOFM), and to write my own Z-type program and form, where I generate my attachment, and then I execute the function module to send an email - so everything is done manually during output determination. Can I use somehow standard functionality to achieve something like that?

no clue?

How to accept purchase order in mail

Hi Experts,
We need to accept purchase order in mail, without login into system.
Is there any way to do it.
Thanks
R.Sundaravel

I believe this can be achieved thru workflow notifications and inbound response processing. Pl see these MOS Docs
221268.1 - How To Make Use Of The E-Mail Function In The Purchase Order/Requisition Approval Form
267159.1 - 11.5.x Upgrade to 11.5.9 -- Changes to Links in Requires Approval Notifications
352594.1 - Email Approval Notifications In 11.5.10 are Different From 11.5.9 - How to force users to login to system?
268085.1 - Configuring the Oracle Workflow 2.6/11i.OWF.H Java-based Notification Mailer with Oracle Applications 11i
and the necessary PO and Workflow Guides at http://www.oracle.com/technology/documentation/applications.html
HTH
Srini

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

Item text in Purchase Order getting updated with info. record Purchase Order Text

Hello All,
I am working in a roll out project and facing issue in text repeating twice for the line item in the Purchase Order for the new company code for which rollout is happening
Issue:
Item text in Purchase Order getting updated with info. record Purchase Order Text
01) PO Text is maintained in the material master under "Purchase Order Text" tab
02) The PO text that is maintained in material master is getting updated in the Purchase Info. Record
03) When Purchase Order is created, the "Item Text" gets updated in the Purchase Order automatically only for the new company code for which rollout is happening. when printed, this results in the text getting duplicated twice
03.1) this behavior is not observed in the Plants/ Company code that is already Live
Configurations in the system:
The copying rules for the "Texts for Purchase Orders" is
Source Object = "Info Record", Source Text="Purchase Order Text", Fix="*"
We have modified the Purchase Order form to print one of the condition types maintained for calculating the tax. Other than this there is no change to the plants that are already live.
I could not locate any "Purchase Organization" / "Company Code" / "Plant specific configuration.
Am I missing any configuration or where can I look in what is causing this error.
Request help from the experts in the forum.
with Regards,
Dhandapani R

There is no company/purchasing/plant specific customizing for purchase order text.
The customizing copying rules for the "Texts for Purchase Orders" affects all equally .
If the text in the purchase order in ME23N is already filled different to other plants, then you either have a modification in place, or the texts are differently maintained in the referenced data (vendor, material, info record, contract)

Disabling selected Purchase Order field(s) after released/approved

Hi Experts,
I have a requirement to disable specific Purchase Order fields after released via ME29N.
For example, in Purchase Requisition - I can "Release Indicator - Field Selection Key" to control Purchase Requisition screen layout. However, for Purchase Order - the configuration for "Release Indicator" consist only standard default "Chgable" options.
Question:
Is there a way to customize the Purchase Order "Release Indicator" for screen layout based on customer requirements other that using the default as mentioned above?
Thank you.
Steven

Hi Padmasri,
I understand your explanation on the standard SAP behavior.
Nevertheless, I'm looking for some flexibility to meet customer requirement. Like in Purchase Requisition, there is option to further customize the screen layout by linking it to the "Release Indicator".
Therefore, apart from the standard 6 options given by standard SAP, can we add/customize the options? For example, my customer may one to change a field in the Purchase Order even after released.
Thank you.
Steven

Add purchase order in SAP with sdk

Hi Experts:
I am doing an aplication for to export a purchase order to SAP with the SDK and I need to read the document number of the last purchase order that was added.
Wich method can I use?
Thanks.

Hi Silvia,
You can use the GetNewObjectKey method right after you have created a new document. You can then get the DocNum using the GetByKey method.
Here an example in VB.NET (if you use C#, it is easy to translate):
'We declare a new document of type delivery
'and set all the necessary properties and values
'We then add the new delivery note
If oDeliveryNote.Add = 0 Then
     Dim tmpDel As Documents = vCmp.GetBusinessObject(BoObjectTypes.oDeliveryNotes)
     'Then using the GetByKey method together with the GetNewObjectKey method,
     'we can get all kinds of interesting info about the newly created delivery note
     If tmpDel.GetByKey(vCmp.GetNewObjectKey) Then
          'Let's populate some variables that we declared earlier
          DelNr = tmpDel.DocNum
          NumAtcard = tmpDel.NumAtCard
          CardCode = tmpDel.CardCode
          DocType = tmpDel.UserFields.Fields.Item("U_type").Value
    End If
End If
The same code applies to all document types.
Good luck,
Johan
Edited by: Johan Hakkesteegt on Feb 13, 2012 12:19 PM

Option sends Purchase Order through mail

Dear All,
My client wants Option sends Purchase Order through mail.
Please tell me what the process for above scenario is.
Thanks in advance,
Nagi Reddy

Hi,
For sending PO via mail, first check if output determintation in properly set in customization settings. Also If you are using customized program for printing, check if code is maintained in program for sending ouput via mails.
If all is maintained in customizing, in PO select output medium as "Mail" and take print. This can also done by using condition records in MN04. Then try sending the output via mail.
Thanks
Alex

Return receipt for the purchase order through mail

Hello Friends,
Can anybody tell me How to receive the return receipt for the purchase order through mail.

What is the type of Inbound document? Is a Return receipt mail can post in to SAP. I have done for my company thro' Idoc after carefully considering many ways. PO only can be triggered to supplier thro' mail.I am not sure.
Cheers!

Deleted purchase order with release strategy

Hi all,
When PO are deleted, the release strategy is disabled. However, if you mark final invoice and delivery completed indicators, the release strategy is triggered, even if the po is deleted.
Is it possible to disable the release strategy when final invoice and delivery completed indicator are marked?
Thank you for your answer

The technical expert in my team has found the explanation to that problem:
A deleted item is "statistical" => there is no release strategy (standard control in ME_REL_STRATEGIE_EKKO function module)
But if ''final invoice'' and ''delivery completion'' are marked, the item is NOT statistical (standard control in LMEPOF4X include)
Therefore, a release strategy is redetermined even if the item is deleted
Thank you all for having tried to help

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

Purchase Order Print out with Digital Signature

Dear Gurus,
1) we are going to implement release strategy, but still business requirement to have a digital signature, Meaning, if only upto Supervisor release, then PO print should come with Supervisor digital signature, if PR value upto Supervisor & manager release, then PO print should come with Manager digital signature, if PR value upto Supervisor, Manager, GM Reelease, then PO print should come with GM digital signature, Whoever approves last, then their signature should appear in the PO printout - How to Achieve this?
2) If any amement in the Purchase order, then is it possible to reflect in the PO print out as Rev1 , Rev 2...?
Please advice
Thanks
RS

Dear,
Check : http://help.sap.com/saphelp_nw70/helpdata/EN/18/ecb69017ad4765855425b97f666470/content.htm
May be helpful.
Another is scan the signature to bmp and attach the bmp through smartform or sapscript - But this is not digital signature.
Regards,
Syed Hussain.

Purchase Order E-mailing with Release Strategy

Similar Messages

Maybe you are looking for