Route redetermination at delivery

Hello all,
we are planning to carry out route - re determination at the delivery level based on shipping point considering the weight groups and not based on delivery type.
there is a user exit in standard SAP (EXIT_SAPL0VRF_001) that does the customer specific route re determination by data transferred from delivery header and also from sales order.
the question is whether the SAP user exit will be sufficient to carry a route re determination at delivery level by checking the shipping point or is any new Zprogram needed to satisfy the requirement.
If i need a zprogram, is it mandatory to have any special Ztables to read the shiiping point at the delivery or can the zprogram be created with no special Ztables, so that it checks the shipping point in the delivery header to carry out delivery level route redetermination.
Pl. advise.
Thanks,
Maxx

As per my understanding there's no difference between route determination in sales order and delivery, system considers the same inputs to determine the route based on logic defined in config.
One key factor in route detrmination is the departure transportation zone which comes from the shipping point (SPRO > Transportation > Basic Transportation Functions > Routes > Route Determination > Maintain Country And Transportation Zone For Shipping Points; V_TVST_RF).
Since the departure transportation zone comes from shipping point, you can define a different transportation zone for each of yourshipping points and thus your problem is solved w/o any user exit.
If the "solution" described is not acceptable you can go to development - whether you need a separate z-table to define your logic or the program code is "enough", you should find out based on how many shipping points you have, how sophisticated your logic is. I feel you would need such z-table if you have several shipping points and each of them need some different route determined.
Please also note that in case of user exit there might be so called check tables (z-check tables) in your system which check table might be suitable to maintain the rules you need (if you do not know what a z-check table is (concerning user exists, BADIs), please ask your skilled ABAPer who should know what I'm speaking about) - in this case there's no need for a new z-table.
Just my opinion...
Edited by: Csaba Szommer on Aug 10, 2010 8:30 AM

Similar Messages

Weight group-route redetermination

Friends,
In the current system route is getting redetermined at delivery level depending on the weight group.Now how it is getting redetermined please do help me with settings done for the same and importantly to find HOW to find out if its picking the right route at delivery.
I am aware how route is determined
1.     Departure zone of the Shipping point in customisation
2. Shipping condition ( system first check the sales doc type, then the customer master of SP)
3. Transportation Group ( from the material master)
4. Transportation zone (from customer master of SH)
So please do help me w.r.t weight group.
Regards
ASD

Hi
Route in delivery depends on weight groups as mentioned above
Route Determination with Weight Group(Delivery)
Shiping ConditionTransportation Groupweight Group----
>Actual Routes,
But where do we get weight group from ,we need to define Weight groups and weight assigned to different weight groups
as mentioned below
SPRO->SD->BASIC FUNCTIONS->ROUTES->ROUTE DETERMINATION->DEFINE WEIGHT GROUPS
*Total Weight   Unit            Seq          Weight group      Description*
1     KG      1     0001     Up to 1 kg
10     KG      2     0010     Up to 10 kg
100     KG      3     0100     Up to 100 kg
so based on weight groups assigned in above transaction,actual route is determined.
S.C                                                      T.GROUP                                WT.GROUP                       ACTUAL ROUTE
01     As soon as possible     0001     On palettes     0001     Up to 1 kg     000001     Northern Route
                                                              0010     Up to 10 kg     000002     Southern Route
                                                              0100     Up to 100 kg     000003     Eastern Route
when order is raised for say 10 items (each item weight is 1 kg) so in deleivery,it means total weight in delivery is 10 kg so route determined isn 00002-southern route in above example.
If order raised for 1 item,total wt is 1 kg so route determined will be 00001,
we can configure as per the requirement,
Regards
Jai

Redetermine PO Delivery Date on Release

Hi
When a PO is created, the buyer ensures that the correct delivery date is put in place. However it sometimes very long for the PO to be released and by the time the PO is released and the PO is sent to the Vendor, the delivery date is already in the past.
Is there anything that can be done in order to redetermine the PO delivery date at the time of release/ at the time the PO is sent to the Vendor.
Thanks
Vinesh

Hi Vinesh,
You can change the delivery date manually in ME22N(Change PO) if there are more line items then u can use fast change to change the delivery date.Once delivery date is changed u have to release the PO again..As per i know automatica redetermination is not possible for already cretaed PO.
Regards,
AM

Route determination in delivery without reference

Hi All,
I am creating Delivery without reference.In this after entering ship to party ,route is not getting determined initially with original shipping condition but when i change shipping condition route determined accordingly and when i change it again to original shipping condition then original route comes.
I am surprised why it is not getting determined initially.
Regards
Amit

If I understand your issue correctly, the Shipping Condition is not automatically defaulting in your delivery, and therefore, Route is not being determined. Please check that you have the correct shipping condition maintained in the customer master, Sales Area screens. This should default the shipping condition to the delivery, and hopefully help in defining route determination.
Also, check route determination config, to make sure that you have the correct combination of Shipping Point, Countries, transportation zones. Then, drill into the route to verify that you have the correct shipping condition, loading group, and route defined.
Good luck

Intercompany return delivery route determination

Hi SAP gurus!
How can we setup route determination for intercompany return delivery based on Purchase Order?
We setup in SPRO route determination by delivery type RL by adding route determination check "A" which means "New route determination without check". But this doesn't work - route doesn't appear in delivery, when returns for Purchase Order is created.
What you would suggest?

Hi,
Route Determination is based on Departure Zone, Shipping Conditions, Transport Zone & Transport Group.
Departure Zone: Identify the shipping locations (Plants and shipping points).
Usually Plant, Shipping point and Departure Zone are same.
If multiple locations share the route determination then the Departure Zone is same for all the locations.
Shipping Conditions: Identify the shipping conditions to be used for Domestic, Exports and Intercompany.
Transport Zones: The destinations are defined based on postal code, geographic area and transit time.
For specific customers, specific carriers and specific warehouses special Transport Zones are required.
Transport Group: The global design is that all the materials are mastered as transport group 0001.
Thanks and Regards,
Shashi

Route is not considering in delivery scheduling for Third party order proce

Hi All
Advance thanks for your inputs
We need to consider the route in the delivery scheduling for third party order processing..
Example
i have standard order (document type OR) when i have item cat TAN its considering the route for ariving the material availability date, if it has TAS(third party) then its not considering the route......
But we want to consider the route in deliver scheduling in case of third party order...
kindlly pls advice..
regards
raja

Hi Viven.,
Routes they come under normal order as we deliver the goods,but here in TAS,third party sale we are not delivering the goods,Just there is logical moment i.e MIGO,So i dont think we do routes for TAS
Thanks & Regards
Narayana

Route dtermine in the delivery

When i am doing stock transport order.after that i am doing delivery through cl10d after that in delivery route is not appearing ,where we should do the settings for route determination in delivery ,please let me know
Regards
Damodhar

Hi Chilukri,
Please check in OVLO whether, during delivery processing, the system uses the route that is determined during stock tranfer order/sales order processing or whether it determines a new route.
If no new route determined during delivery processing, the route will be copied from stock transfer order to delivery. so please check if there is a route in the shipment view in your PO. If there is no one, please maintain in 0VRF.
Regards
Jean

Routes For the Shipments without Considering the Delivery Routes

Hi All,
we are working in transportation related project and We are using the Route determinations to the Shipments.
I wanted to understand is there any way that we determine the Route directly to a Shipment Type without using the Leg Determination from the delivery Routes.
These routes would be diff form the delivery Routes and they need to get directly determined at Shipment Document Level.
Appreciate the valuable Answers
Thanks
Mahesh

Hi Mahesh,
-->As per the standard route will be determined in the delivery from the document it will copied to the shipment through copying routine which you are maintaining in the shipment document type detail screen.
-->If you don't want to copy the route from the delivery then change the copying routine in the shipment document type.
-->You can enter route manually in shipment document.
I hope it will help you,
Regards,
Murali.

Delivery typ

Dear SAPpers,
there are different delivery types in SAP System. For this reason i would like to know which type of functions in SAP does a delivery type control?
Thanks for helping
It will be rewarded

Hi
Delivery type controls many important functions. Few of them, I have mentiond below.
A Delivery type controls,
- Whether an order reference is required to create the said Delivery or not.
- In standard Storage location is determined in Delivery , but it is determined based on a rule (MALA, RETA & MARE in standard).
Which rule will be used to determine Picking/Storage location is controlled in the Delivery type.
- Whether Route will get redetermine during Delivery for the said Delivery Type or not (Route can be re-determined during delivery based on weight).
- Whether rescheduling should take place during delivery or not.
Delivery split by warehouse numbers. That means whether delivery should be splitted if the items are meant for different warehouse or not.
- Beside these above control functions, you can also control what is the Output determination Procedure, Text determination Procedure and Partner determination Procedure will work for the said Delivery Type.
Hope, it will be helpful to you.
Regards

Re-Org/Update Program for Route determination

Hi
does anyone know if there is a Re-org / Update program for Routes ?
I have added new routes, against Shipping conditions from NO and SE to many Western European Countries , and would like to update Sales orders/ deliveries with these new routes
Many thanks for your advice
Tony

Hello Tony
For the orders, if you have configured 'Define New Route Determination By Delivery Type', then route redetermination takes place during delivery creation and finds the new route. So I would say don't bother about fixing the orders.
Just ensure you have configured these 2 items in IMG:
LE/Shipping/Basic Shipping Functions/Routes/Define New Route Determination By Delivery Type,
and
LE/Shipping/Basic Shipping Functions/Routes/Define Allowed Actual Route By Proposed Route.
That leaves open deliveries which are not PGIed to be taken care of.

Change of ship-to party right before dispatch on delivery (not order)

have a client that consistently has to change the ship-to party right before dispatch. the client has customers that are dealers, who in turn have sub-dealers. the dealers very rarely accept shipment to their address, they want the delivery posted to the sub-dealers and this can change at the last minute. as of right now, the addresses for sub-dealers is not maintained by the client, but they would like to have this option.
i would like to maintain the address of the sub-dealers. but once the delivery document is created the ship-to party is greyed out, how would i change this, so i can enter a new ship-to party? the address changes last minute, but after the delivery has been created.
thanks in advance!

Hi
In standard SAP it is not possible.
Once , you create a Delivery document, you can not change the Ship-to-party. Ship-to-party is a Header data in Delivery.
If you want the change then you have to delete the Delivery.
Make your client understand that it is not only Ship-to-party, so many other related data will get redetermine once the Ship-to-party is changed.
For example, When Ship-to-party is changed, Route will be redetermined, Tax will be redetermined, partial delivery agreement may be different etc.
The new Ship-to-party may have a choice of different Plant also.
Normally, the above data are determined in Sales order, therefore you can change those in Sales order only and NOT possible to change in the Delivery document.

Route Determination and Shipping Point

Hi,
In what way Route Determination and Shipping Point are connected.
advise please.
thanks

Simon,
The country and transportation zone of the Shipping point is also considered for determination of Route in sales order and also for redetermining it in delivery.
The system can automatically determine a route for each item during order entry. If visit lists/plans underlie order entry the system uses the routes from the visit lists/plans. If no visit lists/plans exist, the system performs standard route determination. The following criteria affect route determination in an order:
·        Country and transportation zone of the shipping point (departure zone)
·        Shipping condition
·        Transportation group of the material
·        Country and transportation zone of the ship-to party
the system is to perform standard route determination in the delivery again, it also takes into account the weight group (weight of entire delivery). The system saves the delivery route in the delivery header. As it is saved in the document header the route applies to the whole delivery
Regards

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

Routing in Stock Transfer Order

Hi,
We are having SAP 4.7 & we have activated Transportation Routing process.
Routing is copied in Sales order & Delivery. But the same is not copied in the stock transfer Order. We are doing following steps.
We are using Stock Transfer order to transfer the material from One storage location to another storage location. Supplying Plant & Receiving Plant are same in Stock transfer Order. We are entering Receiving STorage location & Shipping point in the STO.
Is this b'coz of Supplying plant & receing plant are same in the STO ? Or i need to active something els for this.
Kindly revert back.
Thanks in advance.
Samir Bhatt

Hi,
this is one of the problems caused by an organisation structure that is not quite matching the "real world".
In SAP each Plant should have a unique address and the storage locations are thought of as areas within that address.
If you have two sites that have different addresses, they should <u>ideally</u> be separate plants. You can then use all of the available functionality within SAP that you would expect.
If you want to set up a route that goes from one address to another than this is possible, but in your case you are actually saying that you want a route for s delivery from and too the same address, not really a real world scenario.
So if you really want to do this then each site should be a plant. I expect that it is too late to change your design but it is important for others reading this to understand the problems that are caused when Storage locations are used instead of Plants for physically separate addresses.
Sorry if this is not much help to you but it should help you to understand why you are having a problem.
Steve B

Incorrect Transport Requests : SAP delivery version getting collected

Hi,
In our development system, when we try to include objects in a transport request, the entries in the transport request are getting saved as the SAP Delivery version rather than the active version.
For example an ODS ( z object, newly created in development environment) entry is being logged as R3TR DODS XXXX (Obj name) rather than R3TR ODSO XXXX.This is happening for all object types ( Info objects, cubes, workbooks etc).
Also while collecting workbooks in transport request ( using transport connection) we got the following error -Logical transport object 414Q not found in table RSTLOGOPROP. Not sure if the above two issues are interlinked.
Appreciate your help on this.
Kind Regards,
Bansi

Hi KxD,
I don't expect the loading date to be equal to the delivery date but I expect it to be 2 days before the delivery date since the time specified on the route is 2 days. So I would expect my loading date = delivery date - 2 days (route time)
The way system is acting is loading date = committed date + 2 days (route time).
FYI.. when you turn on route scheduling the delivery creation date is based off of your route time and not your planned delivery time from the material master
Thanks,
Imran

Route redetermination at delivery

Similar Messages

Maybe you are looking for