Control Delivery

How to control delivery to customer based on the advance received from that customer. In case there is no advance payment, there should not be any delivery or system should stop the delivery.
Moderator: Don't double-post

Hi:
This of your requirement pertains to credit management. You have to define credit limit in FD32 for the corresponding credit control area. Check the settings in the transaction OVAD - for the delivery type. If this group is filled there - the system executes the credit check for that .. Relate your advance indicator from customer in OBXR in properties as Related to credit limit. This will increase your credit limit as per the amount of advance received from customer. I hope it will help you.
Regard

Similar Messages

Control Delivery split based on diff in exchange rate (let. of credit)

Hi Team,
We have a scenarios where the user does nto want split in delivery because of differecne in Exchange rate for line items.
In my case when Letter of credit si assigned to line item.
I understand this as standard behavior that a delivery splits happens based on difference in exchangerate.
My question is to control this split, will it be a right to control it by routine in copy controls routine form order to delivery or we consider the user exit.
So, kindly assit me to solve this or do we have any standard setting by which i can control. this.
Thanks in advance
Balaji

Hi Balaji,
See Note 415716 - User exits in delivery processing, because it tells us how some modification can affect to split documents.
I suggests you to manage it with VOFM subroutine. The idea is that diferent values in LIKP-ZUKRL determintes the split of documents. You can populate until 40 characters, and you manage it with structure ZUK. This concatenation in a string is moved to LIKP-ZUKRL. It works like ZUKRI in spliting of invoice. This VOFM is set in copy rules.
Regards
Eduardo

Control Delivery's Save - if condition is not meat.

Dear all,
I need help at the following.
I added code at USEREXIT_SAVE_DOCUMENT_PREPARE in order to control if the delivery is ready to be saved or not. After the MESSAGE .... 'E'...... I get another message
Risk of posting several mat.documents for one delivery->long text
Message no. VL621
Where should I check the completeness of my document with extra conditions?
Thanks for your help,
Elly

Finally I validated my entries through the "Incompletion Log" functionality.
Note 0000158807 User-defined checks for the incompletion log gave me the answer.
Thanks anyway.
Elly Leondi

Copying control: Delivery to Billing

Hi,
I´m having problems concerning copying control between deliveries and billing documents.
I already maintained the proper copy data in Tcode VTFL either in header and item levels, but I´m still getting the error message "the document is not relevant for billing".
I don´t know what I´m missing here.
Regards.

Hi
Please check in the Item Category(VOV7) - for the field BILLING RELEVANCE. This could be Order related Billing. Change it to Delivery Related Billing and try. It should work if all your configurations are correct.
Thanks,
Ravi

Controlling Delivery of email on webmail

I have setup email using Microsoft Outlook but I am also receiving the same messages on webmail. How can I control the delivery of the webmail messages.

DECIDE IF YOU WANT TO DO THIS.
Settings>Email Settings>Forward
Tom
Freedom Essentials, QIP 7100 1,Bose SOLO TV Sound System,,QIP 7216 P2,M1424WR Rev F, iPad 2 WiFi,iPhone 5,TV SYST INFO Release 1.9.5 Build No. 17.45
Data Object 39.45

Control delivery type for mvt type 313

Hi
Regarding SLOC to SLOC transfer postings, I have a couple of questions:
Using movement type 313 (unr. use stock SLOC to SLOC) in our SAP system automatically creates a delivery in the background. Where can I configure what delivery type I would like to use for this purpose? Also, is there any settings I can do for ATP checks for this? I believe this is standard SAP functionality so a IMG menu path would be very much appreciated.
Brgds,
Lars

Thanks.
However, I am not sure that helped me very much.
What we would like to do is to achieve a scenario where we move stock that is in QI and Blocked stock, in a similar way as with movement type 313. I am not even sure that is possible to do with a delivery? We use the deliery generated from movement type 313 to send with IDOC to one of our 3PL warehouses, managed by another company.
When I look at it, I can find movement type 325 to move Blocked stock from one SLOC to another, but is it possible to do with a delivery (generated in the background)?
Brgds,
Lars

Control delivery type in VL31N

Hi,
I have created a new delivery type (ZEL) from the standard (EL)
I want to affect this new type to the purchase order (NB)
what do you suggest to me ?
Thanks in advance

hi,
as you are copying from EL I am assuming you are working with inbound delivery for order confirmation.
Now as you have created ZEL please assign this in
OLME->confirmation -> define internal confirmation -> here confirmation key LA (Shipping Notificat.) assign ZEL
now you can use ZEL for inbound delivery for your PO
It will serve your purpose

[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)

Item number in billing document not matching with delivery document-reg

Hi All,
In the billing document the item number is coming from Shipment document. ie., there are three deliveries in a shipment. Each delivery has got one line item, ie., 10. These three deliveries are assigned to a shipment, the order in which the deliveries are attached if we take as 10 for first delivery, 20 for th esecond and 30 for the third, In billing document the billing from first delivery is getting the item number as 10, the second delivery's billing document is getting the item number as 20 and the third as 30.
Can someone please reply where and how this is configured?
Thanks and regards,
Tajudeen S.

Hi,
first look at IMG/Sales and Distribution/ Billing / Maintain Copying Control For Billing Documents / Copying control: Delivery document to billing document
There is a field "Copy item number from reference"
Maybe it helps.
regards
Wojciech

Delivery - Proforma - Invoice

Hello Experts,
During requirement gathering we propose order related billing for Proforma,but the problem is some of the data which require for proforma output is capturing from outbound delivery.also user wants to create proforma with reference to delivery.
my question is - is it possible to create proforma with reference to delivery without dng PGI and then billing document from the same delivery nos.
Can one proforma and invoice generated from one delivery nos.???
Kindly suggest.
Thanks
Shri..

Hello,
Yes, we can do this in SAP Standard.
Infact this is the process normally followed in many industries, specially where advance payment is required.
You can create a Proforma Invoice from Delivery Document before PGI & then create actual Invoice after doing PGI.
For Proforma Invoice before PGI you have to do the following setting:
IMG - Sales and Distribution - Billing - Billing Documents - Maintain Copying Control For Billing Documents - Copying control: Delivery document to billing document
Here select your Delivery & Billing Type & at Header Level in Copying requirements insert routine 11 - Head.dlv-rel.w/o GI.
No other setting is required for Delivery to actual Invoice.
Hope this helps,
Thanks,
Jignesh Mehta

Expected Price ED1 EDI2 Sales Order & Incompletion issues re: Delivery/Bill

Hi,
We are using ED1 and EDI2 conditions for expected price on the sales order to trigger incompletion. This works fine, and it's possible to use V.25 to release or manually adjust the pricing conditions to match.
However we have problems in the way it is working re: Header/Item - if say we have two lines, line10 EDI1/2 prices are ok, complete; line 20 EDI1/2 conditions also added but incorrect and therefore incomplete.
Now when user trys to create a Delivery - they can create a delivery for line 10 but the line 20 errors because it is incomplete. This at line level would be ok, if we could subsequently Bill this line, but doing this through VF01 errors because of message 'VF055 (VF)055 Pricing error in document'
The only way to clear it is to clear line 10 on the sales order, say V.25 which then allows Line 10 to also be Delivered and Billed.
The above is with incompletion status group 06 which should prevent Delivery & Billing. Alternatively we could use Incompletion status 02, which blocks Delivery but allows Billing.
However this is inconsistant with the EDI1/2 conditions - Delivery seems to be blocked at the Item Level, but Billing at Header Level.
Is there a solution? Ideally we want the either:-
i) Delivery to prevented if any line is incomplete for EDI1/2, or
ii) Billing to be prevented only if the line Billed on the Delivery is incomplete on the Sales Order, not any line.
Any advice appreciated.

Hi,
I suggest you check copy control (delivery->billing) at item level in tr. VTFL.
Do you use standard routine in 'copying requirements' ? If needed you can also create custom routine that would not raise error for your scenario.
Regards,
Dominik Modrzejewski

Duplicate invoices for single delivery

Hi all,
We have a delivery with 10 EA and create an invoice for this. However, I am able to create another invoice (again for 10EA) which is an exact duplicate of this. I have checked my copy control and it looks fine.
I have looked at SAP note 12934 and this tells me how to determine all billing documents with this problem. I am not sure if this note prevents it from happening again in the future though. How can we determine and fix the root cause?
Thanks,

Hi,
Please look at the copy control (Delivery to Billing, Tcode VTFL) settings Billing Qty Field. It should be D or G depending on your scenario and the Pos./neg. quantity should be +.
Thanks and Regards.
Jogesh

Invoice split by number of delivery line items

Hi,
Can anyone assist in providing me with a solution to the problem of splitting invoices based on the number of delivery line items. I know there is an SAP restricting of 999 lines when posting to SAP.
Example:
If my delivery has 20 line items is there a way to split the invoice into two separate documents of 10 lines each?
Thanks
Anirudh

Hi,
Instead of splitting the Invoice on the basis of delivery line items, you can fix the maximum of lines allowed in the Invoice. So this will help you having multiple invoices from a delivery.
I don't know if this suits you.
There is routine number 6 which acomplishes this (Single Invoice Limited), where coding has been done on the basis of config. (Sales Org:Limit number of billing items TVKO-MAXBI).
This can be assigned at the item level (Copy control - Delivery to Billing, VTFL)
Instead you can create a seperate routine which initially checks the number number of line items in the reference delivery document and then creates an invoice with specific lines.
Hope this helps.
Regards,
Vivek

Copy control for G2W or G2N in Inv.corr.request for TAX item in billingdoc.

Hi all,
There is a billing document for an item with item category TAX(non-stock item) of Item category group NLAG.
Can we use either G2W or G2N for invoice correction request that is created w.r.t. this billling document. Any side effects like determination of cost or etc.
Rgrds,
SKJain

Are you sure your configuration is correct? Here is what the documentation says about 'D' and 'E' and fits exactly to your requirement.
D: Copy pricing elements unchanged. The system
copies the pricing elements unchanged with automatically determined or manually entered surcharges and discounts from the reference document (scales are not read again). This means that the value remains unchanged even if the billing quantity is different to the order quantity
does not redetermine the taxes
E Copy pricing elements and values unchanged. The system
copies the pricing elements and values and automatically determined or manually entered surcharges and discounts from the reference document without changing them (scales are not read again). This means that the value remains unchanged even if the billing quantity is different to the order quantity.
does not redetermine the taxes
Check if your document types and item categories are correctly identified.
Also check if your billing document is created referring to a delivery document, not a sales order. In that case, this setting should be done in the 'Copying control: Delivery document to billing document' activity.
If nothing works, may be you can try using the copying requirements to control the taxes.
Srinivas

Stock Transport Order with Delivery and Billing

Dear all,
I've manage to perform STO process for supplying plant -> delivery (VL10B) until post goods issue (VL02N).
Now, when I attempt to perform standard SD billing (VF01) using the delivery number, the system proposes "IV" billing type (Interco Billing).
My problem is there no net price for the billing document (VF01). Question: normally the pricing is carried over from Sales Order in a normal SD process. Since this is STO crossover from MM process into SD process, do I need to maintain the pricing condition manually in the billing document before saving?
Thanks.
Steven

In the copy control (delivery --> billing document) you can define what the source of the price is, from where system should copy, determine it.
Basically you have two options: determine the price based on sales condition records or copy the price from purchase order (see pasted link). If you use shipment, you can set that shipment cost should be copied as well (see OSS note 574850).
You can find copy control settings under:
SPRO > Sales and Distribution > Billing > Billing Documents > Maintain Copying Control For Billing Documents
As for details please have a look at:
Intercompany Billing Process
(see Raghavendra's answer)
if you are not familiar with SD, please contact your SD consultant to carry out the settings.
Edited by: Csaba Szommer on Jan 14, 2011 12:38 PM

Control Delivery

Similar Messages

Maybe you are looking for