Delivery acceptance

Hi,
If the sales order contains different partner functions, where does the system check the information to know if the customer accepts delivery on a certain day and time. Does it look at the records of sold to party, payer, bill to party or ship to party ?
Thanks

Hello,
As he delivery is always related to ship-to-party master record. The system checks the ship-to-party for delivery acceptence.
Prase

Similar Messages

Pay After Delivery disappeared as method of payment with a seller that DOES accept PAD.

I have been using Pay After Delivery for a few months now, especially on Kidizen (an app for buying used baby and kids clothes). Today, I was shopping and went to check out with PayPal and as usual, it showed PAD as my payment method. Before finishing the transaction though, I needed ot double check my cart so I pressed the back button, verified it was all correct, and then went right back to PayPal. However, this time, Pay After Delivery was not showing as my method of payment. I refreshed the app and re-entered PayPal a hundred times to no avail. I tried other websites that accept PAD and for some reason PAD won't show up as my method of payment on any of them. I even went into my PayPal settings to turn off PAD and turn it back on, but again my efforts were futile. Can someone please tell me what is going on and how to fix it?

This is EXACTLY what happened to me, but I was using eBay. Ready to check out, changed shipping method, never even left the page...PAD dissapeared. Awful. How are you supposed to find the best deal and manage your purchases and budget when your payment methods are so messed up. It's obviously not about the item or the seller/store because it has dissapeared like this for both of us. Really unhappy.......

Your message wasn't delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept e-mail from certain senders, or another restriction may be preventing delivery

HI,
We are getting following error message for all users while sending mail to external but we able to receive mail from internet.
Your message wasn't delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept e-mail from certain senders, or another restriction may
be preventing delivery.

Hi,
Please follow Luke and Shelly’s suggestion to check your SPF record and Send Connector configuration. Also you can post the complete NDR message(with NDR status code) here for further analysis.
If there is any updates, please feel free to let us know.
Thanks,
Winnie Liang
TechNet Community Support

Payment Terms according to delivery and acceptance

Hi,
Is it possible to configure standard SAP payment term according to 90% Upon Delivery, 10% On Final Acceptance?
Thanks,
CW

Hi
Yes ...You can ...
Go to TCode OBB9 and define Terms of Payment for Installment Payments.
Cheers
Srinivas

NotificationServiceFault - Message accepted for delivery

This is a bit of a strange one ...
I have one BPEL process set up for exception handling and error notification via email and it is working fine. I then went to another "like" type process and setup the same thing. The notification throws a fault but the message is "Message accepted for delivery" ... but the message does not arrive ... this seems odd .. Has anyone else ever had this problem with the notification system.
InvokeNotificationService (faulted)
[2006/06/05 12:41:52] "{http://xmlns.oracle.com/ias/pcbpel/NotificationService}NotificationServiceFault" has been thrown. less
<NotificationServiceFault>
<part name="faultInfo" >
<faultInfo>250 2.0.0 k551tgn15962 Message accepted for delivery </faultInfo>
</part>
</NotificationServiceFault>

We have had intermittent issues with invoking the notification service, I have not looked further on the server (appserver 10.1.2.0.2 on Solaris) where the e-mail is sent to try and track down the issue. Instead we put a loop around the invoke notification and retry for a configurable number of times incase a fault is thrown (not ideal and adds to the overall code needed). It seems after the fault is thrown the next time it will invoke with no troubles.

Delivery date accepting holidays

Hi Experts,
While creation of a sales order, in the schedule line tab the system proposes the delivery date automatically taking into consideration the holiday calendar set by skipping the holidays. But when the user manually changes the delivery date in schedule lines on Sunday (set as holiday in factory calendar), system is not throwing an alert or error message and user is able to save the sales order.
The factory calendar has been set in Plant, Shipping point and Sales Organization. Requirement is that system should not allow to save with holidays in factory calendar as delivery dates. Kindly advise. Thanks in advance.
Regards,
Madhavan

Madhavan,
If you are using transportation scheduling (this is somewhat common), then 'delivery date' represents the date that the customer can expect the goods to arrive on his doorstep. Respect for holidays are irrelevant to any calendars you may have assigned to your factories or shipping points. Check in OVLY.
In this case, the calendar assigned to the Route can have an impact. Also, if you have assigned unloading points, these can have an impact.
If you ARE using transportation scheduling, you may want to reconsider this business requirement. The dates that most companies are concerned with are Material availability date, planned Goods Issue date, Transportation Planning date, and Loading date. The only time Delivery date becomes a concern is when the customer will not accept goods on specific dates.
Best Regards,
DB49

Seeking definition of "Message accepted for delivery"

In Exchange 2010 I have a situation where if I send a message to both internal and external recipients, the external recipients only receive the message if I turn Sophos PureMessage off. However, in both
successful attempts and failed attempts the last record in my Exchange Message Tracking Logs is identical, as follows:
EVENTID = SEND
SOURCE = SMTP
SOURCECONTEXT = "...Message accepted for delivery"
That leads to my wondering what exactly that log entry means?
For example, it could mean "Sending server will attempt to deliver message"
or it could mean "Sending server has attempted to deliver message"
or it could mean "Receiving server has accepted message"
or it could means something else. If you know *for sure*, can you please reply? Please don't guess what it means. Also, if you respond, please don't use the word "server" in your response without explicitly stating which server
you mean (eg "sending server" or "receiving server").
If it turns out that log record does NOT indicate the receiving server accepted the message, can anyone tell me how I can be sure the receiving server has accepted the message?
Thank you very much!

If it turns out that log record does NOT indicate the receiving server accepted the message, can anyone tell me how I can be sure the receiving server has accepted the message?
Hi,
You can try to enable the NDR. If the recipient's mailbox doesn't receive this email, it will return NDR to the sender.
Also try to configure Get delivery and read receipt confirmations. More details to see:
https://support.office.microsoft.com/en-us/article/Get-delivery-and-read-receipt-confirmations-a34bf70a-4c2c-4461-b2a1-12e4a7a92141?CorrelationId=f2166a89-93d0-4137-8268-601b7aa337cc&ui=en-US&rs=en-US&ad=US
Thanks
Mavis Huang
TechNet Community Support

If I don't accept the UPS delivery, will UPS return it to Apple?

Hi
I ordered a macbook but I realized too late that I had ordered the wrong keyboard.
If I do not accept UPS delivery, will UPS return it to Apple? Or will UPS simply store it until I pick it up?

They will attempt two more deliveries before returning it to the sender unless you tell the delivery person you refuse to accept it. But this won't fix the problem for you. You would be wiser to accept it then make arrangements to exchange it within your first 14 days either with Apple directly or at a local Apple retailer. If you do the former just contact Apple to make the arrangements.
Apple Store Customer Service at 1-800-676-2775 or visit online Help for more information.
To contact product and tech support visit online support site.

Delivery is accepting material in Blocked & quality inspection stock

Hi Experts,
During delivery ( VL01N) the system asks for Serial Nos for the delivered Material and serial Nos are assigned by going to Extras--> serial Nos. and PGI is completed
In this process the system could able to take the serial Nos that are in Blocked (07)or Quality (02) state also apart from the Unrestricted Use.
How can we restrict the system to prevent selecting the stock/material apart apart from 01 state ( i.e unrestricted use)
Regds
Rajiv

You have customize that availability check which runs behind delivery to check what are the stock available.
You have to make sure u unchecked the quality inspection stock and blocked stock
thanks

Restrict accepting delivery of mail

Hi all,
Thanks for your help.
We are running OSX Server 10.5.8 and would like to stop direct delivery of mail from the internet.
We have a hosted anti-spam provider, but sometimes spammers are connecting directly to our server.
I don't believe the mail server can restrict the delivery of incoming mail by IP address? We would like to only receive internet email from our hosted anti-spam relay AND receive from our remote workers in order to relay it on.
The Mail Service Admin guide suggests that this should be accomplished with the firewall. If one were to limit connections at the firewall, or even at the mail service by IP, wouldn't this also stop SMTP connections from users with laptops working remotely?
How is this achieved with Mac Mail server as incoming mail and remote workers all use SMTP?
I suspect the answer is to send mail via another host when working remotely, but will this then reach the "sent" folder in users' mailboxes?
Many thanks,
James.
Message was edited by: James Ratcliff
Message was edited by: James Ratcliff

As Camelot pointed out, there are many options.
-Ask your spam gateway provider if they are able to send to you on a different port.
-Set up a separate submission port for your users so that they can send while out of the office and firewall port 25 for everyone except your provider's IP.
-Should you not require your users to be able to send through your mail server while outside your network, simply lock port 25 for everyone except your provider's IP.
Except for the last solution, all will require some (minor) degree of command line changes.

[Solved] postfix local mail delivery fails

Hi Guys,
on my home pc i use postfix (gmail as a smtp relay) and fetchmail for sending/receiving mails, this works very well, however sending a mail to a local user fails, I'm lost here and need your help guys.
if i send a mail like :
$>echo "Test" | mail -s "Test : local mail delivery" "andy"
The mail stays in the queue for ever...
$>mailq
-Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------
CC82513BCA* 455 Sun Aug 3 09:53:09 [email protected]
[email protected]
Sending to external addresses works without any problems.
Here some important info/config files :
$>whoami
andy
$>hostname
box
$>cat /etc/host.conf
# /etc/hosts
#<ip-address> <hostname.domain.org> <hostname>
127.0.0.1 localhost.localdomain localhost box
::1 localhost.localdomain localhost
192.168.1.3 lbox.localdomain lbox
$>cat /etc/postfix/main.cf
# Global Postfix configuration file. This file lists only a subset
# of all parameters. For the syntax, and for a complete parameter
# list, see the postconf(5) manual page (command: "man 5 postconf").
# For common configuration examples, see BASIC_CONFIGURATION_README
# and STANDARD_CONFIGURATION_README. To find these documents, use
# the command "postconf html_directory readme_directory", or go to
# http://www.postfix.org/.
# For best results, 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 = /var/spool/postfix
# The command_directory parameter specifies the location of all
# postXXX commands.
command_directory = /usr/bin
# 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/lib/postfix
# The data_directory parameter specifies the location of Postfix-writable
# data files (caches, random numbers). This directory must be owned
# by the mail_owner account (see below).
data_directory = /var/lib/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
#myhostname = mail.example.com
myhostname = localhost.localdomain
# 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
mydomain = localdomain
# 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
inet_interfaces = 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 VIRTUAL_README).
# 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
# STANDARD_CONFIGURATION_README).
# 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, localhost
#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain,
# mail.$mydomain, www.$mydomain, ftp.$mydomain
#mydestination = localhost, localhost.localdomain
# 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, $inet_interfaces or $pr/oxy_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 local(8)).
# 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
# ${proxy,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
# 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 postconf(5).
# 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 description in
# postconf(5) 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 or $proxy_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 description in postconf(5).
#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 = [mailserver.isp.tld]
#relayhost = uucphost
#relayhost = [an.ip.add.ress]
relayhost = [smtp.gmail.com]
# 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 100 SMTP server process
# limit, this limits the mail inflow to 100 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
# The ADDRESS_REWRITING_README document gives information about
# address masquerading or other forms of address rewriting including
# username->Firstname.Lastname mapping.
# ADDRESS REDIRECTION (VIRTUAL DOMAIN)
# The VIRTUAL_README document gives information about the many forms
# of domain hosting that Postfix supports.
# "USER HAS MOVED" BOUNCE MESSAGES
# See the discussion in the ADDRESS_REWRITING_README document.
# TRANSPORT MAP
# See the discussion in the ADDRESS_REWRITING_README document.
# 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
alias_maps = hash:/etc/postfix/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
alias_database = $alias_maps
# 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"
mailbox_command = /usr/bin/procmail
# 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".
# Cyrus IMAP over LMTP. Specify ``lmtpunix cmd="lmtpd"
# listen="/var/imap/socket/lmtp" prefork=0'' in cyrus.conf.
#mailbox_transport = lmtp:unix:/var/imap/socket/lmtp
# Cyrus IMAP via command line. Uncomment the "cyrus...pipe" and
# subsequent line in master.cf.
#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,
# unknown@[$inet_interfaces] or unknown@[$proxy_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. The file
# SMTPD_ACCESS_README provides an overview.
# 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 "man header_checks".
#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".
# See the ETRN_README document for a detailed description.
# The fast_flush_domains parameter controls what destinations are
# eligible for this service. By default, they are all domains that
# this server is willing to relay mail to.
#fast_flush_domains = $relay_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 = 20
# 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
ddd $daemon_directory/$process_name $process_id & sleep 5
# If you can't use X, use this to capture the call stack when a
# daemon crashes. The result is in a file in the configuration
# directory, and is named after the process name and the process ID.
# 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
# Another possibility is to run gdb under a detached screen session.
# To attach to the screen sesssion, su root and run "screen -r
# <id_string>" where <id_string> uniquely matches one of the detached
# sessions (from "screen -list").
# debugger_command =
# PATH=/bin:/usr/bin:/sbin:/usr/sbin; export PATH; screen
# -dmS $process_name gdb $daemon_directory/$process_name
# $process_id & sleep 1
# 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
# html_directory: The location of the Postfix HTML documentation.
html_directory = no
# 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.
# This parameter is obsolete as of Postfix 2.1.
sample_directory = /etc/postfix/sample
# readme_directory: The location of the Postfix README files.
readme_directory = /usr/share/doc/postfix
inet_protocols = ipv4
# Enable smtp auth
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/saslpass
smtp_sasl_security_options = noanonymous
# Enable tls
smtp_use_tls = yes
smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination
# Max message size limit
message_size_limit = 0
Please help
Last edited by Rumcajs (2014-08-05 06:16:11)

I have solved it, and this was the problem (main.cf) message_size_limit = 0 i have set this to unlimited "0" so bigger mails not get rejected by postfix, the defualt value was 10240000 (~10 Mb) after finally checking the postfix log with journalctl -u postfix (because /var/log/mail.log) is not used anymore i found this line : "fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit" after setting mailbox_size_limit to unlimited "0" postfix starts to delivery local mail.
Last edited by Rumcajs (2014-08-05 06:17:23)

Process Order accepts Confirmation & GR from BAPI even after Confirmed

No matter what i try the formatting and CRLF go for a toss in this text.
Hi PPPI Gurus,
I am a beginner in this area and request your help.
We are implementing a project where the process order Confirmation in SAP ECC 5.0 in SAP PPPI module is done using xMII which call the BAPI_PROCORD_CREATE_TT     RFC.
The customer wants to (certain times) do a final confirmation without actually completing the order e.g if the Order Qty is 100 then, they want to just manufacture 25 and then do a final confirmation, after which SAP GUI screen does not allow any Process order Confirmations against that process order.
We are using the BAPI_PROCORDCONF_CREATE_TTRFC to do multiple PO Confirmations and GR for particular Process order. Below is a scenario
Case 1:
1. Order Qty =100 ( Unlimited Delivery is not checked and tolerance is Zero).
     Which means only 100 is accepted.
2. 100 Quantities are produced and confirmed using the BAPI_PROCORDCONF_CREATE_TT (with Final confirmation value as 1 , which mean auto confirmation)
3. Next when the BAPI confirms & GR's against the same order, the Complete qty is not visible in the COR3 status. And is visible only in the COGI transaction.
That is expected behavior. and i am ok with that.
Case 2: (The one with the problem)
1. Order Qty =100 ( Unlimited Delivery is not checked and tolerance is Zero).
     Which means only the 100 is accepted.
2. 25 Quantities are produced and confirmed using BAPI_PROCORDCONF_CREATE_TT (with Final Confirmation value as X , which mean Final confirmation)
3. The Confirmation and GR go through and the status of the process order now changed is CNF and the Deliverd qty is 25.
At this point , if you logon to SAP GUI and try to make a process order confirmation you get an error messages which says the Process Order is already confirmed and no more confirmations or GR can be done against this Process order.
4. But when you Again Run the BAPI_PROCORDCONF_CREATE_TT, it goes ahead and confirms and makes the GR for that Process order.
The Expected Behavior should have been that this quantity is now in the COGI transaction.
5. The Process order allows any number of Further confirmations till the Ordered Qty and Delivered quantity are same .
so dear gurus I know i have written a very long doubt but would be very happy to get a response from you. I would ideally not like to enhance or change the BAPI and want to understand if I have missed some setting or parameter that I have to pass in the BAPI for the final confirmation so that once the Status of the Process order is CNF , no more Confirmations are allowed even from the BAPI.
Thanks in Advance.
Regards
Suraj
Edited by: surajprabhu on Aug 17, 2009 6:37 AM

Hi,
The standard SAP will allow the GR even after the Final Confirmation. The Final Confirmation is acting as a agent to change the status of the process order to CNF. thats all.
If you want to restrict the GR then you have to do Enhancement with use the USer Exits. Pleas try to use the User Exits PPC00009 or MBCF0001,MBCF0005
thanks and regards
murugesan

Inconsistent delivery balance after return with restocking fee

My client does not like the work around she must use to delete negative delivery balances after returns are processed with a restocking fee. Here is her description of the problem:
1. We receive this unit back from customer. When a return is created the unit is received back into stock and cost account is credited.
2. We revised the unit and decided to accept the return but charge a 10% restocking fee which means we will give back to the customer only 90% of what he paid for the unit.
When a credit memo is created, the customer receives the credit and the revenue account is debited. Also the base return document is closed.
3. However the system indicates that there is a negative delivery amount of $509 (On the BP master screen) We donu2019t want to see that balance; there is no document open linked to that balance.
If I do the same process, but add the total credit amount to the unit price directly the system does not show this negative balance even though the total amount of the return document is different than the total amount of the credit memo.
In order for me to clear that balance, I needed to create a return, copy it to a credit memo, and create an invoice to offset the invoice.
Is ther a better way to do this?

The proper way to do it would be full credit plus new service invoice to complete this transaction. The restocking fee s a new charge to customer. That process will reflect the true financial transaction.
Thanks,
Gordon

Open Qty is not copied in Delivery for Stock Transfer Order

Hi,
In the Stock Transfer Order process, Once the STO Order is created, I am creating delivery in the transaction VL10B or VL10G.
When I am clicking the background button Delivery gets generated. Then when i am going in the transaction VL02N and increasing the delivery Quantity which is more than STO order quantity, the system is accepting it. But i want the system to throw an error message if the delivery quantity is more than the order qauntity. For this I have made the following settings.
In the Transaction Code 0VLP, i have selected B in Check Over Delivery field. But still it is not throwing an error.
The reason for the same may be, the system is not copying the Open Delivery Qty from the STO Order (Which normally happens in Sale Order to Delivery process, bcos of Copy Control). This field has 0 value. So the system is not able check for over delivery.
If I get this value in the delivery then it should be working fine and the sytem will throw an error for over delivery.
Can you please suggest me a way to get this open qty value in delivery for STO order or suggest me some other option to check for over delivery in STO.
Regards
Vijay

Dear Friend,
If I can understand you clearly.
to achieve your task the best way you can sit with your abaper and configure a routine and assign the same to T-code OVLK delivery type customizing :
In the Item requirement : Generally it is 202
reward points if helpful,
regards,
Amlan

How to change a delivery from complete order to partial order

Hi,
We have create a delivery from a sale order that initially it was a complete order. During the picking of the TO we found a difference of stock of one unit. We asked to the client if they accept the partial order and they said that there was no problem.
We change the sales order from complete to partial, but the delivery is not accepting the difference, is always warning that we haven't arrive to the quantity.
I have read that there is no way to change the delivery so we have to delete it and create a new one. But we have a problem, the original one was of 56 pallets and all of them are done and label except the last one, if I delete de delivery I will have to move the TO again to the stock and dismount the 56 pallets, and repeat the picking, so, somebody knows a solution to avoid this and not move again everything just for one piece?
Thanks

Hi Allen
Well the problem is that the order is finished but with a difference os 1 unit of the 259 that we have to pick.
If I cancel the order I will have to move all the material to the bins that they proceed and repeat the picking with a new order to pick exactly the same amount of material that I have now.
The problem is, how do I make a new delivery and a new order but without moving the material to the bins and repeat the picking again?
Best Regards and thanks for your time
Edited by: enriquerolo on Mar 5, 2012 7:32 AM

Delivery acceptance

Similar Messages

Maybe you are looking for