External mail for Woktiem notification - Language of shortcut.

Hi Experts!
The external email functionality to official emails, for the workitem notifications.
has a shortcut to SAP. (link) - part of the report RSWUWFML2.
this shortcut opens in Language EN.
User having different login language want to have option of Language in shortcut.
Can you provide any help is this case?
Thanks!
VJ

HI VJ,
according to documentation of report RSWUWFML2, shortcut language is the language set in the users adress.
Please check transaction su01 for a user who should receive shortcut in different language than english.
hth
Ute
P.S. If ypu find this answer helpful, please reward points

Similar Messages

External mail for workflow of release strategy for PO

Dear All,
I have configured the workflow of two step release strategy for purchase order and the internal mail is getting generated in the sap business workplace with the error message SWF_RUN 594 this i have taken care with SWE2 with changing the settings of "Behaviour upon error feedback" from "default" to "do not change linkage"
Now the requiremnt is that the message has to be send to first level releaser through external mail and once first level release the PO external mail should be send to second level releaser.
Please help me with the configuration step that is to be done
Thanks in advance
Naveen Singh

Schedule the report Rswuwfml2. this will send workitem from sap inbox to respective user external mail id maintain in user master.

CC with external mail for RFQ and PO

Dear All,
Mails are triggered to the vendors for RFQ and PO. The Purchase department does not get any report or system confirmation if the mails are successfully triggered or not. Having a CC to the external mails would confirm that the mails have been triggered by the system. Can we have a CC for all the external mails getting generated for the RFQs and POs? Is this technically feasible?
CC : can be user sending the RFQ or PO.
Regards
Sushant

Dear All,
Mails are triggered to the vendors for RFQ and PO. The Purchase department does not get any report or system confirmation if the mails are successfully triggered or not. Having a CC to the external mails would confirm that the mails have been triggered by the system. Can we have a CC for all the external mails getting generated for the RFQs and POs? Is this technically feasible?
CC : can be user sending the RFQ or PO.
Regards
Sushant

Add text in mail for payment notification RFFOAVIS_FPAYM

Hi All,
We are sending payment notification to vendors via RFF0AVIS_FPAYM program. We are using SAP script form for this.
We want to add text in mail body. I have checked note 1033893. I have created text with name z* in SO10 and assigned in process exit for 00002040. But text is not appearing in mail.
Am i missing some settings ?
Please give suggestions.
Thanks in advance.
Regards,
Chintan

Hello,
Point 1
Please check up the function module attached to proces 00002040 in FIBF.
Make the changes in the function module.
Please refer:
SAP NOTE 1033893, 836169.
Also see Note 521587.
Regards,
Ravi

Set a new mail for the notification

Hello,
I dont find in MSDN Profile or in Live.com website a place to set or retreive the notification mail I used for the forum answers.. etc.
If I remember good We can set another mail than the login live email ? right ?
Any tips where i could find this option ?
THanks

Hello,
On the left of the screen, click "Quick access" and then click "My settings".
In the settings page, you will see "Configure alerts", and your configured email address.
You may change it there.
Karl
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer.
My Blog: Unlock PowerShell
My Book: Windows PowerShell 2.0 Bible
My E-mail: -join ('6F6C646B61726C40686F746D61696C2E636F6D'-split'(?<=\G.{2})'|%{if($_){[char][int]"0x$_"}})

High Priority External mail

Hi Experts,
We are using external mails for PO deadline notification and this is working fine. Now they have asked for high priority mail in Outlook.Is it possib to sent a high priority mail to external Id.
Regards,
Hari

Hi Hari,
do you mean, you want high priority mail (Importance High mail) in Outlook side,
or you mean once deadline is done you want to send mail to Outlook.
If its the first case, then I think you need to ask the MS Exchange Server people to try configure any mail coming from SAP as high.
If its the second case, then you have Extended Notifications or RSWUWFML2 report which could send mails to Outlook.
Hope it helps.
Aditya

Approval process from external mail

Experts,
I want to create a workflow that should trigger the mail with PO data (Either PDF or any other format) to the external mail. The external mail for example PDF file should have 2 buttons for approve and reject. From the external mail, they should have the flexibility to approve or reject PO. Is there any possibility to do this process.
How the link happend between the action performed from PDF file to SAP. Is there any way to get the indicator(A or R) that happened in PDF to SAP.
Give me some conclussion or any alternative flow on this process.
Thanks.

Hi,
trigger the mail with PO data (Either PDF or any other format) to the external mail.
Sending Mail to Outlook : U need the Following things done for this:-
1> Use the Mail Step in the WF and Choose the Receipient as the E-Mail Address and Give the E-Mail Address there.
2> Check the Configurations that need to be done in Transaction SCOT. SMTP Server Settings are done to get the Desired Results.
From the external mail, they should have the flexibility to approve or reject PO.
When the decision is approved, U can Send a mail to the Earlier Approvers Regarding the Status of the Work-Item.
To get Workitems in Outlook..!!
https://www.sdn.sap.com/irj/scn/wiki?path=/display/abap/workflow%252bscenario
Problem in transferring the workitems into OUTLOOK
/people/saujanya.gn/blog/2006/12/19/how-to-get-work-items-your-outlook-inbox
Workflow Items in Outlook
Let me know if u still face any issues.
Regards,
Kanika

Multiple Languages in Outlook mail for a workitem not working(Note 1230808)

All Gurus,
I am on ECC 6.0 with the below system details.
SAP_ABA     700     0015     SAPKA70015     Cross-Application Component
SAP_BASIS     700     0015     SAPKB70015     SAP Basis Component
PI_BASIS     2006_1_700     0005     SAPKIPYM05     Basis Plug-In (PI_BASIS) 2006_1_700
We have implemented Extended Notifications in our system and it has been working fine so far with a single language EN. Now, we got a new requirement to generate Outlook mails corresponding to a work item in multiple language (FR for French apart from EN). Towards this, I applied OSS Note 1230808, with all the pre-requisites taken care as mentioned in the Note in our Sandbox system. I found this note from following blog (Thanks to Mike Pokrara !!!)
[Re: Extended notification languages]
The FR text has been maintained for a standard task (Created by us only) as below:
1. Task Description in FR is maintained thru' PFTC txn, by choosing the FR option, and
2. Work item text for task is maintained thru' SE63.
Also, as mentioned in the OSS note, a value 'C' has been maintained for Parameter "WI_TASK_LANGUAGE" in SWNCONFIG.
Even after this implementation, when the emails are generated for an EN user, the Outlook mail is fine with all the text in EN, as expected. But, when the FR email is generated for a FR user, only the Workitem header text, the std. Header and Footer (maintained and picked up by std. SAP SO10 text) are translated into FR. But the Task Description part is still displaying in EN only.
Anybody had same / similar issue for this reqiurement ?. Can anybody tell me if anything is wrong in the way we are implementing or any limitaitons or known issues of this note / requirement ?
Your timely help is greatly appreciated.
Thanks in advance & Best Regards,
venu

All,
It was a type from our side while implementing the manual corrections that were part of the OSS note 1230808. We found this with SAP's help and it's fixed now.
So, closing this thread.
Thanks to you all
venu

How to configure Workflow Notification Mailer for oracle alert in R12

Hi all....,
How to configure Workflow Notfication mailer for oracle Alert in R12. Please provide the complete steps.. Its urgent.. Plz help me..
Regards ,
Madhan

Duplicate thread (please post only once)
plz help me...!!!! Workflow Notification Mailer
plz help me...!!!! Workflow Notification Mailer

Send Mail to External Mail ID's for Multiple Users

Hi All,
I want to send mail from SAP to External mail ID's for multiple Users.The program is ok.
But I want to send this to Multiple external Mail id's. Where should I assign this receivers list. Pls advise.
What is the transaction to assign multiple receivers.?
CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
      EXPORTING
        DOCUMENT_DATA              = GD_DOC_DATA
        PUT_IN_OUTBOX              = 'X'
        COMMIT_WORK                = ''
      TABLES
        PACKING_LIST               = IT_PACKING_LIST
        CONTENTS_TXT               = IT_MESSAGE
        RECEIVERS                  = IT_RECEIVERS
      EXCEPTIONS
        TOO_MANY_RECEIVERS         = 1
        DOCUMENT_NOT_SENT          = 2
        DOCUMENT_TYPE_NOT_EXIST    = 3
        OPERATION_NO_AUTHORIZATION = 4
        PARAMETER_ERROR            = 5
        X_ERROR                    = 6
        ENQUEUE_ERROR              = 7
        OTHERS                     = 8.
Thank You.
Pranitha.

IT_RECEIVERS parameters needs to be passed as shown below.
    wa_receivers-receiver = "..........External mail id".
    wa_receivers-rec_type = 'U'.
    wa_receivers-express = 'X'.
    APPEND wa_receivers TO lt_receivers.
    CLEAR wa_receivers.
Once mail is triggered to the external mail id's, check the mail is transferred from SAP or not using the tcode SCOT.
In SCOT,follow the path UTILITIES-> Overview of send orders.
Regards,
Satish Kanteti

Send notification to external mail id when work item reach users inbox

hi all ,
i would like to know wat are all the settings required for sending an external mail when a user recieves a work item. i think it can be done by running the program rswuwfml .but wat are all the settings required to be done before running the program .....
Useful answers will be rewarded.......

What the??!!!! I totally missed this before and actually found it quite acidentally....
>Yep true! Totally agree with Kjtetil, it adds to an already noisy forum and I am >afraid if others start aping it will be brought down on level with the XYZ forum. >And we don't want that!
>Anyone volunteering to have the 'M' flag?
Though I cannot comprehend what you are trying to get at or say I will, attempt to set the record straight.
Yes I have said that on another thread. I am not asking for points anywhere, I am happy to receive and happier to solve someone's problem.
The issue with this thread is the author obviously has not bothered to do any investigation. I am not for spoon feeding just for the sake of some points, I am willing to help those who do some bit from their end as well who encounter a genuine stumbling block.
My reference to "reward" was with a bit of sarcasm, if you know what that means.

Setting Up Mailserver to received and Send Mail for external Network

I have a G5 currenty running 10.3.9 Server with Mail services run and working fine, we are upgrading to 10.4 Server and would like our Sales Reps the ability to send and Receive mail from outside the office. How do I configure my server, Router, ISP and/or Mail clients to do this??? we are currently able to recieve mail from outside just not send.

I cannot find the Line #submission inet n - n -- smtpd in the Main.CF file...here is what I get when I open it
# Global Postfix configuration file. This file lists only a subset
# of all 250+ parameters. See the sample-xxx.cf files for a full list.
# The general format is lines with parameter = value pairs. Lines
# that begin with whitespace continue the previous line. A value can
# contain references to other $names or ${name}s.
# NOTE - CHANGE NO MORE THAN 2-3 PARAMETERS AT A TIME, AND TEST IF
# POSTFIX STILL WORKS AFTER EVERY CHANGE.
# SOFT BOUNCE
# The soft_bounce parameter provides a limited safety net for
# testing. When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
#soft_bounce = no
# LOCAL PATHNAME INFORMATION
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
queue_directory = /private/var/spool/postfix
# The command_directory parameter specifies the location of all
# postXXX commands.
command_directory = /usr/sbin
# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
daemon_directory = /usr/libexec/postfix
# QUEUE AND PROCESS OWNERSHIP
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes. Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
mail_owner = postfix
# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#default_privs = nobody
# INTERNET HOST AND DOMAIN NAMES
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#myhostname = host.domain.tld
#myhostname = virtual.domain.tld
# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
#mydomain = domain.tld
# SENDING MAIL
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites. If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# [email protected].
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#myorigin = $myhostname
#myorigin = $mydomain
# RECEIVING MAIL
# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on. By default,
# the software claims all active interfaces on the machine. The
# parameter also controls delivery of mail to user@[ip.address].
# See also the proxy_interfaces parameter, for network addresses that
# are forwarded to us via a proxy or network address translator.
# Note: you need to stop/start Postfix when this parameter changes.
#inet_interfaces = all
#inet_interfaces = $myhostname
#inet_interfaces = $myhostname, localhost
# The proxy_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on by way of a
# proxy or network address translation unit. This setting extends
# the address list specified with the inet_interfaces parameter.
# You must specify your proxy/NAT addresses when your system is a
# backup MX host for other domains, otherwise mail delivery loops
# will happen when the primary MX host is down.
#proxy_interfaces =
#proxy_interfaces = 1.2.3.4
# The mydestination parameter specifies the list of domains that this
# machine considers itself the final destination for.
# These domains are routed to the delivery agent specified with the
# local_transport parameter setting. By default, that is the UNIX
# compatible delivery agent that lookups all recipients in /etc/passwd
# and /etc/aliases or their equivalent.
# The default is $myhostname + localhost.$mydomain. On a mail domain
# gateway, you should also include $mydomain.
# Do not specify the names of virtual domains - those domains are
# specified elsewhere (see sample-virtual.cf).
# Do not specify the names of domains that this machine is backup MX
# host for. Specify those names via the relay_domains settings for
# the SMTP server, or use permit_mx_backup if you are lazy (see
# sample-smtpd.cf).
# The local machine is always the final destination for mail addressed
# to user@[the.net.work.address] of an interface that the mail system
# receives mail on (see the inet_interfaces parameter).
# Specify a list of host or domain names, /file/name or type:table
# patterns, separated by commas and/or whitespace. A /file/name
# pattern is replaced by its contents; a type:table is matched when
# a name matches a lookup key (the right-hand side is ignored).
# Continue long lines by starting the next line with whitespace.
# See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS".
#mydestination = $myhostname, localhost.$mydomain
#mydestination = $myhostname, localhost.$mydomain $mydomain
#mydestination = $myhostname, localhost.$mydomain, $mydomain,
# mail.$mydomain, www.$mydomain, ftp.$mydomain
# REJECTING MAIL FOR UNKNOWN LOCAL USERS
# The local_recipient_maps parameter specifies optional lookup tables
# with all names or addresses of users that are local with respect
# to $mydestination and $inet_interfaces.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown local users. This parameter is defined by default.
# To turn off local recipient checking in the SMTP server, specify
# local_recipient_maps = (i.e. empty).
# The default setting assumes that you use the default Postfix local
# delivery agent for local delivery. You need to update the
# local_recipient_maps setting if:
# - You define $mydestination domain recipients in files other than
# /etc/passwd, /etc/aliases, or the $virtual_alias_maps files.
# For example, you define $mydestination domain recipients in
# the $virtual_mailbox_maps files.
# - You redefine the local delivery agent in master.cf.
# - You redefine the "local_transport" setting in main.cf.
# - You use the "luser_relay", "mailbox_transport", or "fallback_transport"
# feature of the Postfix local delivery agent (see sample-local.cf).
# Details are described in the LOCAL_RECIPIENT_README file.
# Beware: if the Postfix SMTP server runs chrooted, you probably have
# to access the passwd file via the proxymap service, in order to
# overcome chroot restrictions. The alternative, having a copy of
# the system passwd file in the chroot jail is just not practical.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify a bare username, an @domain.tld
# wild-card, or specify a [email protected] address.
#local_recipient_maps = unix:passwd.byname $alias_maps
#local_recipient_maps = proxy:unix:passwd.byname $alias_maps
#local_recipient_maps =
# The unknown_local_recipient_reject_code specifies the SMTP server
# response code when a recipient domain matches $mydestination or
# $inet_interfaces, while $local_recipient_maps is non-empty and the
# recipient address or address local-part is not found.
# The default setting is 550 (reject mail) but it is safer to start
# with 450 (try again later) until you are certain that your
# local_recipient_maps settings are OK.
#unknown_local_recipient_reject_code = 550
unknown_local_recipient_reject_code = 450
# TRUST AND RELAY CONTROL
# The mynetworks parameter specifies the list of "trusted" SMTP
# clients that have more privileges than "strangers".
# In particular, "trusted" SMTP clients are allowed to relay mail
# through Postfix. See the smtpd_recipient_restrictions parameter
# in file sample-smtpd.cf.
# You can specify the list of "trusted" network addresses by hand
# or you can let Postfix do it for you (which is the default).
# By default (mynetworks_style = subnet), Postfix "trusts" SMTP
# clients in the same IP subnetworks as the local machine.
# On Linux, this does works correctly only with interfaces specified
# with the "ifconfig" command.
# Specify "mynetworks_style = class" when Postfix should "trust" SMTP
# clients in the same IP class A/B/C networks as the local machine.
# Don't do this with a dialup site - it would cause Postfix to "trust"
# your entire provider's network. Instead, specify an explicit
# mynetworks list by hand, as described below.
# Specify "mynetworks_style = host" when Postfix should "trust"
# only the local machine.
#mynetworks_style = class
#mynetworks_style = subnet
#mynetworks_style = host
# Alternatively, you can specify the mynetworks list by hand, in
# which case Postfix ignores the mynetworks_style setting.
# Specify an explicit list of network/netmask patterns, where the
# mask specifies the number of bits in the network part of a host
# address.
# You can also specify the absolute pathname of a pattern file instead
# of listing the patterns here. Specify type:table for table-based lookups
# (the value on the table right-hand side is not used).
#mynetworks = 168.100.189.0/28, 127.0.0.0/8
#mynetworks = $config_directory/mynetworks
#mynetworks = hash:/etc/postfix/network_table
# The relay_domains parameter restricts what destinations this system will
# relay mail to. See the smtpd_recipient_restrictions restriction in the
# file sample-smtpd.cf for detailed information.
# By default, Postfix relays mail
# - from "trusted" clients (IP address matches $mynetworks) to any destination,
# - from "untrusted" clients to destinations that match $relay_domains or
# subdomains thereof, except addresses with sender-specified routing.
# The default relay_domains value is $mydestination.
# In addition to the above, the Postfix SMTP server by default accepts mail
# that Postfix is final destination for:
# - destinations that match $inet_interfaces,
# - destinations that match $mydestination
# - destinations that match $virtual_alias_domains,
# - destinations that match $virtual_mailbox_domains.
# These destinations do not need to be listed in $relay_domains.
# Specify a list of hosts or domains, /file/name patterns or type:name
# lookup tables, separated by commas and/or whitespace. Continue
# long lines by starting the next line with whitespace. A file name
# is replaced by its contents; a type:name table is matched when a
# (parent) domain appears as lookup key.
# NOTE: Postfix will not automatically forward mail for domains that
# list this system as their primary or backup MX host. See the
# permit_mx_backup restriction in the file sample-smtpd.cf.
#relay_domains = $mydestination
# INTERNET OR INTRANET
# The relayhost parameter specifies the default host to send mail to
# when no entry is matched in the optional transport(5) table. When
# no relayhost is given, mail is routed directly to the destination.
# On an intranet, specify the organizational domain name. If your
# internal DNS uses no MX records, specify the name of the intranet
# gateway host instead.
# In the case of SMTP, specify a domain, host, host:port, [host]:port,
# [address] or [address]:port; the form [host] turns off MX lookups.
# If you're connected via UUCP, see also the default_transport parameter.
#relayhost = $mydomain
#relayhost = gateway.my.domain
#relayhost = uucphost
#relayhost = [an.ip.add.ress]
# REJECTING UNKNOWN RELAY USERS
# The relay_recipient_maps parameter specifies optional lookup tables
# with all addresses in the domains that match $relay_domains.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown relay users. This feature is off by default.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify an @domain.tld wild-card, or specify
# a [email protected] address.
#relay_recipient_maps = hash:/etc/postfix/relay_recipients
# INPUT RATE CONTROL
# The in_flow_delay configuration parameter implements mail input
# flow control. This feature is turned on by default, although it
# still needs further development (it's disabled on SCO UNIX due
# to an SCO bug).
# A Postfix process will pause for $in_flow_delay seconds before
# accepting a new message, when the message arrival rate exceeds the
# message delivery rate. With the default 50 SMTP server process
# limit, this limits the mail inflow to 50 messages a second more
# than the number of messages delivered per second.
# Specify 0 to disable the feature. Valid delays are 0..10.
#in_flow_delay = 1s
# ADDRESS REWRITING
# Insert text from sample-rewrite.cf if you need to do address
# masquerading.
# Insert text from sample-canonical.cf if you need to do address
# rewriting, or if you need username->Firstname.Lastname mapping.
# ADDRESS REDIRECTION (VIRTUAL DOMAIN)
# Insert text from sample-virtual.cf if you need virtual domain support.
# "USER HAS MOVED" BOUNCE MESSAGES
# Insert text from sample-relocated.cf if you need "user has moved"
# style bounce messages. Alternatively, you can bounce recipients
# with an SMTP server access table. See sample-smtpd.cf.
# TRANSPORT MAP
# Insert text from sample-transport.cf if you need explicit routing.
# ALIAS DATABASE
# The alias_maps parameter specifies the list of alias databases used
# by the local delivery agent. The default list is system dependent.
# On systems with NIS, the default is to search the local alias
# database, then the NIS alias database. See aliases(5) for syntax
# details.
# If you change the alias database, run "postalias /etc/aliases" (or
# wherever your system stores the mail alias file), or simply run
# "newaliases" to build the necessary DBM or DB file.
# It will take a minute or so before changes become visible. Use
# "postfix reload" to eliminate the delay.
#alias_maps = dbm:/etc/aliases
#alias_maps = hash:/etc/aliases
#alias_maps = hash:/etc/aliases, nis:mail.aliases
#alias_maps = netinfo:/aliases
# The alias_database parameter specifies the alias database(s) that
# are built with "newaliases" or "sendmail -bi". This is a separate
# configuration parameter, because alias_maps (see above) may specify
# tables that are not necessarily all under control by Postfix.
#alias_database = dbm:/etc/aliases
#alias_database = dbm:/etc/mail/aliases
#alias_database = hash:/etc/aliases
#alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
# ADDRESS EXTENSIONS (e.g., user+foo)
# The recipient_delimiter parameter specifies the separator between
# user names and address extensions (user+foo). See canonical(5),
# local(8), relocated(5) and virtual(5) for the effects this has on
# aliases, canonical, virtual, relocated and .forward file lookups.
# Basically, the software tries user+foo and .forward+foo before
# trying user and .forward.
#recipient_delimiter = +
# DELIVERY TO MAILBOX
# The home_mailbox parameter specifies the optional pathname of a
# mailbox file relative to a user's home directory. The default
# mailbox file is /var/spool/mail/user or /var/mail/user. Specify
# "Maildir/" for qmail-style delivery (the / is required).
#home_mailbox = Mailbox
#home_mailbox = Maildir/
# The mail_spool_directory parameter specifies the directory where
# UNIX-style mailboxes are kept. The default setting depends on the
# system type.
#mail_spool_directory = /var/mail
#mail_spool_directory = /var/spool/mail
# The mailbox_command parameter specifies the optional external
# command to use instead of mailbox delivery. The command is run as
# the recipient with proper HOME, SHELL and LOGNAME environment settings.
# Exception: delivery for root is done as $default_user.
# Other environment variables of interest: USER (recipient username),
# EXTENSION (address extension), DOMAIN (domain part of address),
# and LOCAL (the address localpart).
# Unlike other Postfix configuration parameters, the mailbox_command
# parameter is not subjected to $parameter substitutions. This is to
# make it easier to specify shell syntax (see example below).
# Avoid shell meta characters because they will force Postfix to run
# an expensive shell process. Procmail alone is expensive enough.
# IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN
# ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER.
#mailbox_command = /some/where/procmail
#mailbox_command = /some/where/procmail -a "$EXTENSION"
# The mailbox_transport specifies the optional transport in master.cf
# to use after processing aliases and .forward files. This parameter
# has precedence over the mailbox_command, fallback_transport and
# luser_relay parameters.
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf. The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#mailbox_transport = lmtp:unix:/file/name
#mailbox_transport = cyrus
# The fallback_transport specifies the optional transport in master.cf
# to use for recipients that are not found in the UNIX passwd database.
# This parameter has precedence over the luser_relay parameter.
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf. The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#fallback_transport = lmtp:unix:/file/name
#fallback_transport = cyrus
#fallback_transport =
# The luser_relay parameter specifies an optional destination address
# for unknown recipients. By default, mail for unknown@$mydestination
# and unknown@[$inet_interfaces] is returned as undeliverable.
# The following expansions are done on luser_relay: $user (recipient
# username), $shell (recipient shell), $home (recipient home directory),
# $recipient (full recipient address), $extension (recipient address
# extension), $domain (recipient domain), $local (entire recipient
# localpart), $recipient_delimiter. Specify ${name?value} or
# ${name:value} to expand value only when $name does (does not) exist.
# luser_relay works only for the default Postfix local delivery agent.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must specify "local_recipient_maps =" (i.e. empty) in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#luser_relay = [email protected]
#luser_relay = [email protected]
#luser_relay = admin+$local
# JUNK MAIL CONTROLS
# The controls listed here are only a very small subset. See the file
# sample-smtpd.cf for an elaborate list of anti-UCE controls.
# The header_checks parameter specifies an optional table with patterns
# that each logical message header is matched against, including
# headers that span multiple physical lines.
# By default, these patterns also apply to MIME headers and to the
# headers of attached messages. With older Postfix versions, MIME and
# attached message headers were treated as body text.
# For details, see the sample-filter.cf file.
#header_checks = regexp:/etc/postfix/header_checks
# FAST ETRN SERVICE
# Postfix maintains per-destination logfiles with information about
# deferred mail, so that mail can be flushed quickly with the SMTP
# "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld".
# By default, Postfix maintains deferred mail logfile information
# only for destinations that Postfix is willing to relay to (as
# specified in the relay_domains parameter). For other destinations,
# Postfix attempts to deliver ALL queued mail after receiving the
# SMTP "ETRN domain.tld" command, or after execution of "sendmail
# -qRdomain.tld". This can be slow when a lot of mail is queued.
# The fast_flush_domains parameter controls what destinations are
# eligible for this "fast ETRN/sendmail -qR" service.
#fast_flush_domains = $relay_domains
#fast_flush_domains =
# SHOW SOFTWARE VERSION OR NOT
# The smtpd_banner parameter specifies the text that follows the 220
# code in the SMTP server's greeting banner. Some people like to see
# the mail version advertised. By default, Postfix shows no version.
# You MUST specify $myhostname at the start of the text. That is an
# RFC requirement. Postfix itself does not care.
#smtpd_banner = $myhostname ESMTP $mail_name
#smtpd_banner = $myhostname ESMTP $mail_name ($mail_version)
# PARALLEL DELIVERY TO THE SAME DESTINATION
# How many parallel deliveries to the same user or domain? With local
# delivery, it does not make sense to do massively parallel delivery
# to the same user, because mailbox updates must happen sequentially,
# and expensive pipelines in .forward files can cause disasters when
# too many are run at the same time. With SMTP deliveries, 10
# simultaneous connections to the same domain could be sufficient to
# raise eyebrows.
# Each message delivery transport has its XXX_destination_concurrency_limit
# parameter. The default is $default_destination_concurrency_limit for
# most delivery transports. For the local delivery agent the default is 2.
#local_destination_concurrency_limit = 2
#default_destination_concurrency_limit = 10
# DEBUGGING CONTROL
# The debug_peer_level parameter specifies the increment in verbose
# logging level when an SMTP client or server host name or address
# matches a pattern in the debug_peer_list parameter.
debug_peer_level = 2
# The debug_peer_list parameter specifies an optional list of domain
# or network patterns, /file/name patterns or type:name tables. When
# an SMTP client or server host name or address matches a pattern,
# increase the verbose logging level by the amount specified in the
# debug_peer_level parameter.
#debug_peer_list = 127.0.0.1
#debug_peer_list = some.domain
# The debugger_command specifies the external command that is executed
# when a Postfix daemon program is run with the -D option.
# Use "command .. & sleep 5" so that the debugger can attach before
# the process marches on. If you use an X-based debugger, be sure to
# set up your XAUTHORITY environment variable before starting Postfix.
debugger_command =
PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
xxgdb $daemon_directory/$process_name $process_id & sleep 5
# If you don't have X installed on the Postfix machine, try:
# debugger_command =
# PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont;
# echo where) | gdb $daemon_directory/$process_name $process_id 2>&1
# >$config_directory/$process_name.$process_id.log & sleep 5
# INSTALL-TIME CONFIGURATION INFORMATION
# The following parameters are used when installing a new Postfix version.
# sendmail_path: The full pathname of the Postfix sendmail command.
# This is the Sendmail-compatible mail posting interface.
sendmail_path = /usr/sbin/sendmail
# newaliases_path: The full pathname of the Postfix newaliases command.
# This is the Sendmail-compatible command to build alias databases.
newaliases_path = /usr/bin/newaliases
# mailq_path: The full pathname of the Postfix mailq command. This
# is the Sendmail-compatible mail queue listing command.
mailq_path = /usr/bin/mailq
# setgid_group: The group for mail submission and queue management
# commands. This must be a group name with a numerical group ID that
# is not shared with other accounts, not even with the Postfix account.
setgid_group = postdrop
# manpage_directory: The location of the Postfix on-line manual pages.
manpage_directory = /usr/share/man
# sample_directory: The location of the Postfix sample configuration files.
sample_directory = /usr/share/doc/postfix/examples
# readme_directory: The location of the Postfix README files.
readme_directory = /usr/share/doc/postfix
# THE FOLLOWING DEFAULTS ARE SET BY APPLE
# bind to localhost only
inet_interfaces = all
# turn off relaying for local subnet
mynetworks_style = host
# mydomain_fallback: optional domain to use if mydomain is not set and
# myhostname is not fully qualified. It is ignored if neither are true.
mydomain_fallback = localhost
myhostname = jamestownpress.com
mailbox_transport = cyrus
enable_server_options = yes
luser_relay =
maps_rbl_domains = dun.dnsrbl.net
message_size_limit = 0
mydestination = $myhostname,localhost.$mydomain
smtpd_use_tls = no
smtpd_enforce_tls = no
smtpd_tls_loglevel = 0
smtpd_sasl_auth_enable = yes
smtpd_use_pw_server = yes
smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination,permit
smtpd_pw_server_security_options = plain
server_enabled = 1
relayhost =
smtpd_client_restrictions = permit_mynetworks reject_rbl_client dun.dnsrbl.net permit
always_bcc =
mynetworks = 127.0.0.1/32,192.168.0.0/16,192.168.1.98,192.168.1.3,192.168.1.13,192.168.1.5,1 92.168.1.22,192.168.1.18,192.168.1.41
content_filter = smtp-amavis:[127.0.0.1]:10024
so what do I need to change

Notifications failed to send mail for journal approval with attachments

Issue : Notifications failed to send mail for journals sent for approvals with attachments.
Error :
[WF_ERROR] ERROR_MESSAGE=3835: Error '-6502 - ORA-06502: PL/SQL: numeric or value error: character string buffer too small' encountered during execution of Generate function 'WF_XML.Generate' for event 'oracle.apps.wf.notification.send'. ERROR_STACK=
WF_XML.GetAttachments(71009549, http://vfilvappclone.verifone.com:8000/pls/EBIZRPT, 13525)
WF_XML.GenerateDoc(oracle.apps.wf.notification.send, 71009549)
WF_XML.Generate(oracle.apps.wf.notification.send, 71009549)
WF_XML.Generate(oracle.apps.wf.notification.send, 71009549)
Wf_Event.setMessage(oracle.apps.wf.notification.send, 71009549, WF_XML.Generate)
Wf_Event.dispatch_internal()
Cause : Above error is thrown for Journals with attachment of file type Microsoft Office Excel Macro-Enabled Worksheet (.xlsm)
Can anybody help with this?

Please post the details of the application release, database version and OS.
Please see if these docs help.
ORA-20001 & ORA-06502 Workflow Errors [ID 761638.1]
Manager Approval Notification Gives Error: Ora-O6502: Pl/Sql: Numeric Or Value Error: Character String Buffer Too Small [ID 352213.1]
Approval Confirmation Email Is Not Received By Preparer - ERROR_MESSAGE=3835 ORA-20001 ORA-6502 [ID 465146.1]
Notification Fails To Be Generated When A DOCX Document Is Attached [ID 1058183.1]
Not Able To Send Multiple E-Mails Upon Approval Of Purchase Order [ID 333719.1]
Expenses Workflow Error: "ORA-06502: PL/SQL: numeric or value error: associative array shape is not consistent with session parameters has been detected in fnd_global.put(CONC_LOGIN_ID,-1)" [ID 455882.1]
Using Microsoft Office 2007 and 2010 with Oracle E-Business Suite 11i and R12 [ID 1077728.1] -- Notification Generation Fails
ORA-06502 Buffer Too Small Error in Contracts Workflow Notification [ID 870712.1]
Thanks,
Hussein

PO output medium as 'External Send' for Language BG giving '#' instead of character in PDF output

Hi Experts,
When we maintain the PO output medium as ‘External Send’ for Language ‘BG’, the PO pdf is showing # instead of character.
But, if the output medium is PRINT and language is ‘BG’, the PO pdf prints correctly in BG language.I have checked the output type
NEU and find that same smartform is maintained for both the case.
Also it is working fine in the Quality as well as in development server.. issue is coiming only in PRD.
Thanks in advance!!
Regards
Mrinal

Hi,
PLease review the steps from SAP note 191470.
Best Regards,
Arminda Jack

Not send mail for external domains

Hi,
I have installed OCS 10g(10.1.2) in linux. All components ok, but i not send mail for external domain.
Att,
Mesti

I remember in version 9.0.2 that i configure in SMTP_OUTBOUND the IP of DNS external to send mail for other domains.
Mesti

External mail for Woktiem notification - Language of shortcut.

Similar Messages

Maybe you are looking for