ERS posting reverse GR after flag activated, ignoring original GR

Hello
I am having an issue with ERS PO's in our system.
Scenario is as follows -
ERS flag isn't initially set on the PO. Then, a GR posted is from SES release, however because ERS flag isn't turned on EKRS table wasn't populated. Thus ERS would not create IR for the GR.
ERS flag was then set for the PO.
User reversed the GR. Reverse GR posted to EKRS therefore ERS batch picked up the reverse GR to post a reverse IR.
ERS will still not pick up the original GR to create a IR doc.
As a result, vendor account is incorrect and also the GR/IR is incorrect.
Any possible solutions to make correct the PO history?
Due to user error, we will always have cases where ERS flag is turned on after GR.
What is the best way to avoid this imbalanced PO scenario in the future? Should user first reverse GR prior to setting ERS flag?

posted in the wrong forum

Similar Messages

ERS posting reversal, but not payment

Hello
I am having an issue with ERS PO's in our system.
Scenario is as follows -
ERS flag isn't initially set on the PO. Then, a GR posted is from SES release, however because ERS flag isn't turned on EKRS table wasn't populated. Thus ERS would not create IR for the GR.
ERS flag was then set for the PO.
User reversed the GR. Reverse GR posted to EKRS therefore ERS batch picked up the reverse GR to post a reverse IR.
ERS will still not pick up the original GR to create a IR doc.
As a result, vendor account is incorrect and also the GR/IR is incorrect.
Any possible solutions to make correct the PO history?
Due to user error, we will always have cases where ERS flag is turned on after GR.
What is the best way to avoid this imbalanced PO scenario in the future? Should user first reverse GR prior to setting ERS fla

You should do the GR reversal BEFORE you change the PO to ERS.
After you reverse the GR you then
- change the PO to ERS
- do the GR (receipt which is the "original" receipt of the product that you had to reverse because the ERS flag was not set)
If you see this happening alot then I'd suggest looking at your processes and improve the process to make sure this does not happen. For example - it sounds like you are taking existing suppliers with existing POs and converting them to ERS. This would result in POs not being checked for ERS because they were created before the supplier was an ERS supplier. As part of the process to convert the supplier to ERS you need to add a few steps such as:
1) identify open POs/SAs and either close them and create new ones OR convert all of them to ERS.
2) you would also need to identify what POs/SAs have pending invoices and communicate with the supplier what paper invoices they need to send and when they should stop sending the paper invoices.
Sandra

Lion Server postfix mail not being delivered to mailboxes. "SMTP restriction `reject_invalid_helo_hostname' after `permit' is ignored" and "connect to private/policy: Connection refused" errors.

All, Im stumped. In fact I have been on the phone with Apple Support and this has been escalated to the top engineers, as I think its got them too..
Anyway, here is my problem..
I'm running an Mac Mini with OS X 10.7.4 Server. I have had mail running on it for 2 months or so, without any issues. The mail was actually migrated from 10.6 in March, and It actually went smoothly. I have 3 domains which all recieve mail and they all work (or did up until 2 weeks ago)..
So the story is this.. I can send mail from my domains, without issue. imap and dovecot must be working.. cause all the stored mail, can be read with the mail IMAP client.. I can even transfer mail messages from one mailbox to another with Mail client. Sending mail is a breeze, it still works and the recipients still recieve their mail. But I noticed I wasnt getting any mail at all from those mailboxes... no mail, no spam, nothing.. which is unusal. I fired up Server admin and checked out the SMTP log, and this is what it showed for every email recieved: (xxxxxx is just me hiding sensitive info)
Jul 21 14:25:20 xxxxxxxx postfix/postscreen[65857]: CONNECT from [17.158.233.225]:41909
Jul 21 14:25:26 xxxxxxxx postfix/postscreen[65857]: PASS OLD [17.158.233.225]:41909
Jul 21 14:25:26 xxxxxxxx postfix/smtpd[65858]: connect from nk11p03mm-asmtp994.mac.com[17.158.233.225]
Jul 21 14:25:26 xxxxxxxx postfix/smtpd[65858]: warning: restriction `reject_invalid_helo_hostname' after `permit' is ignored
Jul 21 14:25:27 xxxxxxxx postfix/smtpd[65858]: warning: connect to private/policy: Connection refused
Jul 21 14:25:27 xxxxxxxx postfix/smtpd[65858]: warning: problem talking to server private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: warning: connect to private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: warning: problem talking to server private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: NOQUEUE: reject: RCPT from nk11p03mm-asmtp994.mac.com[17.158.233.225]: 451 4.3.5 Server configuration problem; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<nk11p99mm-asmtpout004.mac.com>
Jul 21 14:25:28 azathoth postfix/smtpd[65858]: disconnect from nk11p03mm-asmtp994.mac.com[17.158.233.225]
Ok, now what is odd, is these rejected messages are not even appearing in the mail queue in Server Admin. I have no idea why there are not being delivered
Ive checked my postfix main.cf file and master.cf files they both look ok.. Ive even replaced them with the main.cf.defualt.10.7 and master.cf.default.10.7 files and to no avail... same problem..
So in summary
I can send mail out
IMAP is working on the client end (thus dovecot is) exsisting stored emails can be accessed, read, moved unread etc..
mail is coming into the sever, but its being rejected. there is NO rejection email sent back to the sender.
mail is recieved by postfix, but cyrus isnt doing anything with it.. I have no idea where it goes...
Could anyone shed light on this...
my main.cf file:
# Global Postfix configuration file. This file lists only a subset
# of all 300+ parameters. See the postconf(5) manual page for a
# complete list.
# The general format of each line is: parameter = value. Lines
# that begin with whitespace continue the previous line. A value can
# contain references to other $names or ${name}s.
# NOTE - CHANGE NO MORE THAN 2-3 PARAMETERS AT A TIME, AND TEST IF
# POSTFIX STILL WORKS AFTER EVERY CHANGE.
# SOFT BOUNCE
# The soft_bounce parameter provides a limited safety net for
# testing. When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
# soft_bounce = no
# LOCAL PATHNAME INFORMATION
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
queue_directory = /private/var/spool/postfix
# The command_directory parameter specifies the location of all
# postXXX commands.
command_directory = /usr/sbin
# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
daemon_directory = /usr/libexec/postfix
# QUEUE AND PROCESS OWNERSHIP
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes. Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
mail_owner = _postfix
# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#default_privs = nobody
# INTERNET HOST AND DOMAIN NAMES
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#myhostname = host.domain.tld
#myhostname = virtual.domain.tld
# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
#mydomain = domain.tld
# SENDING MAIL
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites. If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# [email protected].
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#myorigin = $myhostname
#myorigin = $mydomain
# RECEIVING MAIL
# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on. By default,
azathoth:postfix root#
azathoth:postfix root# less main.cf
azathoth:postfix root# more main.cf
# Global Postfix configuration file. This file lists only a subset
# of all 300+ parameters. See the postconf(5) manual page for a
# complete list.
# The general format of each line is: parameter = value. Lines
# that begin with whitespace continue the previous line. A value can
# contain references to other $names or ${name}s.
# NOTE - CHANGE NO MORE THAN 2-3 PARAMETERS AT A TIME, AND TEST IF
# POSTFIX STILL WORKS AFTER EVERY CHANGE.
# SOFT BOUNCE
# The soft_bounce parameter provides a limited safety net for
# testing. When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
# soft_bounce = no
# LOCAL PATHNAME INFORMATION
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
queue_directory = /private/var/spool/postfix
# The command_directory parameter specifies the location of all
# postXXX commands.
command_directory = /usr/sbin
# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
daemon_directory = /usr/libexec/postfix
# QUEUE AND PROCESS OWNERSHIP
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes. Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
mail_owner = _postfix
# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#default_privs = nobody
# INTERNET HOST AND DOMAIN NAMES
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#myhostname = host.domain.tld
#myhostname = virtual.domain.tld
# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
#mydomain = domain.tld
# SENDING MAIL
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites. If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# [email protected].
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#myorigin = $myhostname
#myorigin = $mydomain
# RECEIVING MAIL
# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on. By default,
# the software claims all active interfaces on the machine. The
# parameter also controls delivery of mail to user@[ip.address].
# See also the proxy_interfaces parameter, for network addresses that
# are forwarded to us via a proxy or network address translator.
# Note: you need to stop/start Postfix when this parameter changes.
#inet_interfaces = all
#inet_interfaces = $myhostname
#inet_interfaces = $myhostname, localhost
# The proxy_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on by way of a
# proxy or network address translation unit. This setting extends
# the address list specified with the inet_interfaces parameter.
# You must specify your proxy/NAT addresses when your system is a
# backup MX host for other domains, otherwise mail delivery loops
# will happen when the primary MX host is down.
#proxy_interfaces =
#proxy_interfaces = 1.2.3.4
# The mydestination parameter specifies the list of domains that this
# machine considers itself the final destination for.
# These domains are routed to the delivery agent specified with the
# local_transport parameter setting. By default, that is the UNIX
# compatible delivery agent that lookups all recipients in /etc/passwd
# and /etc/aliases or their equivalent.
# The default is $myhostname + localhost.$mydomain. On a mail domain
# gateway, you should also include $mydomain.
# Do not specify the names of virtual domains - those domains are
# specified elsewhere (see 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
# 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 $proxy_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]
# 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
# The alias_database parameter specifies the alias database(s) that
# are built with "newaliases" or "sendmail -bi". This is a separate
# configuration parameter, because alias_maps (see above) may specify
# tables that are not necessarily all under control by Postfix.
#alias_database = dbm:/etc/aliases
#alias_database = dbm:/etc/mail/aliases
#alias_database = hash:/etc/aliases
#alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
# ADDRESS EXTENSIONS (e.g., user+foo)
# The recipient_delimiter parameter specifies the separator between
# user names and address extensions (user+foo). See canonical(5),
# local(8), relocated(5) and virtual(5

Ok 1st one. The warning restriction message relates to this line in main.cf:
smtpd_helo_restrictions = permit_sasl_authenticated permit_mynetworks check_helo_access hash:/etc/postfix/helo_access reject_non_fqdn_hostname reject_invalid_hostname permit reject_invalid_helo_hostname
The last reject occurs after the single word "permit" and is ignored.
However, that's not the problem.
I'm not exactly sure what's happening, but this might be a clue.
It would appear that either postfix is not being able to create the socket for private/policy or it's somehow created with the wrong permissions. You might need to ramp up the debug level to get a better idea.
You could check if it's being created by "netstat -a | grep private/policy" in terminal.
My guess is that it's not being created because there is no setup statement in your master.cf file, but I don't understand why postfix would be looking for it if it isn't set up. Private/policy I think relates to grey listing. Maybe gives you a hint.

[Solved] UEFI. System hangs on boot after successfully activating swap

Alright.
Unnecessary Background:
I've been using Arch for years. I just bought a stupidly good computer with a bunch of specs that I don't think are relevant, except for the fact that I am using an X99-pro. It has RAID support, but I am not using that currently. I bought all the parts and finished constructing it this morning (I live in Japan, so that was a while ago). Normally, I have no problems with installation; however, I wanted to do this one UEFI mode. After booting into the live disk, I checked to make sure everything was working as it should. Arch recognized my graphics card, most of my ram (one of the cards is a bit finicky for some reason), my SSD and HDD, along with the built-in WiFi (although it is an annoying broadcom one, so I need to install the driver separately later). Now, there are plenty of sources of error in here:
Problem:
I got through the arch installation and tried gummiboot. It would hang every time after successfully activating swap. I tried grub, too, but had the same problem. Because gummiboot is much less cumbersome, I switched back to that. Interestingly, systemd will sometimes recognize my drive twice before activating swap, and if I edit my fstab to ignore the swap completely, it hangs on the next step with is mounting the boot partition. I would like to point out that because I am not able to successfully boot my system, I cannot provide the exact messages for you guys, which may pose a problem.
Solutions I have tried:
1. Chrooting / mkinitcpio -p linux
2. modifying fstab / removing swap from it completely
3. fresh re-install
Sources of error:
1. Construction. Everything seems appropriate on the live usb, but maybe there is a problem in which ports I used for the SSD and HDD
2. UEFI. It could be that UEFI just doesn't like mounting multiple things and freezes up when put on the spot.
3. Legacy. It could be that this is not a problem with UEFI or my construction, but something I missed in the installation.
Additional info:
Partitioning scheme:
sda1: ~500MiB boot / EFI partition
sda2: ~4G swap
sda3: ~110G /
sdb: ~2T, untouched (for storage later)
I apologize for any typos and hope it was readable. I am super exhausted and going to take a nap. I'll check back in on this in the morning.
Last edited by Leios (2015-02-08 00:16:27)

Please post the output of:
# gdisk -l /dev/sda
lsblk -f
And the contents of your gummiboot loader.conf and arch.conf (or whatever you've called it).
Post the output of the commands after you have mounted all your partitions and (arch-)chroot'd into your system.
You can use wgetpaste to post the outputs, as described by @ewaller here:
https://bbs.archlinux.org/viewtopic.php … 8#p1500528
Alternatively, pipe the command output to a text file and export it (using a live distribution or a USB stick).
You should remove swap from your fstab -- systemd mounts it automatically anyway.

Cancelling the GR the excise item tab is not coming after flagging the OK

Hi SAP Experts,
there is one subcon PO for excisable material for depot, after its GR it have been posted from j1iex.
Now there is a requirement to cancel the excise posting for which first of all its GRN should be cancel.
But while cancelling the GR the excise item tab is not coming after flagging the OK.
This problem is there only for the depot, for other plant Im able to cancel for subcon PO.
Thanks & Regards,
Anisha Sinha

still not cleared

InDesign CS5 is not opening after deactivation/activation. How can I fix this? Illustrator and Photoshop open and are working fine. Please help!

InDesign CS5 is not opening after deactivation/activation. How can I fix this? Illustrator and Photoshop open and are working fine. Please help!

First of all, thank you for replying so promptly to my posts this morning!
I can't remember how I got the software on his computer, but I'm pretty sure it wasn't through migration assistant.
I was looking into doing an uninstall of InDesign and a fresh install. However, I initially downloaded the CS5 suite digitally and I can't find out how I am able to perform a fresh install of InDesign. Do you know where I find this info or gain access to download just InDesign again? I can't seem to find anything in my Adobe account that shows where I might do another download.

Posting reversal

Hi
we reversed the payroll of an employee through OC workbench but do not know how to reverse the FI posting. My concern is, if I the do the posting reversal , it it would reverse posting for all the employees in that posting document.
Wondering, how to reverse posting for just one employee. we do not have the process model configured. will it work? if yes, how can we configure it?
Please suggest.
Thanks
Wills

Hi William,
There are two possibilities when you reverse the payroll.
1. You did not want to pay an EE and paid erroneously.
2. You paid him incorrectly and now after reversal you need to pay him again.
In both scenario you will have to correct the master data because system will change earliest MD change date in IT0003 for this EE assuming that you will pay him after reversal.
As per your reply it seems that you need to pay him. So correct the master for the entry which paid him incorrectly and run payroll.
After running payroll post it and when you will next regular payroll system will offset the entries of reversal posting.
I hope this helps.
Arti

How can i call java class implemented as service from ExtJS after successfull activation of a page ?

Hi ,
I want to call a java class implemented as a service in felix . This should be called after succesfull activation of the page .
I want to use ExtJs implemented in /libs/cq/ui/widgets/source/widgets/wcm/SiteAdmin.Actions.js file CQ.wcm.SiteAdmin.activatePage method.
Please suggest something on this .

Hi Sham ,
i tried this ,
var response = CQ.HTTP.post(
        CQ.shared.HTTP.externalize("/bin/replicate.json"),
        callback,
        { "_charset_":"utf-8", "path":paths, "cmd":"Activate" }
if (CQ.HTTP.isOk(response)) {
     CQ.HTTP.post("/bin/sample.json",
              null,
              {"_charset_":"utf-8","path":paths});
It is giving an alert messege on siteadmin screen as "Unspecified Error" .
What can be the problem , am i missing something here?

System allows to post migo even after material flaged for deletion.

Dear Experts,
system allowing to post MIGO , even after material has been flaged for deletion.
while posting migo, system giving warning, i want this to be error, how to achive this.
regards
rajakarthik.

yes it'll allow u to create PO , GR ..etc.
Because its flagged for deletion means , its nothing but u have marked for deletion. only marking jus lik u have noted that has to be deleted from system.
But by doing MM06 it 'll not get change. So u have to archivation .
Revert if any clarification....
Thanks
SAP_MM

Post Goods issue after clicking on Load Starting push button

Hi All,
Post goods issue for deliveries, suppose if the shipment document is created for XXXX country do the post goods issue after clicking the push button loading start on. and if the shipment is created other than the XXXX Country do the post goods issue after clicking the shipment start button(Done by Standard SAP).
There will be validation table in background to identify which shipping point to allow Post Goods Issue before shipment completion. This will require enhancement of Delivery User Exit to incorporate above check based on below mentioned Z Table.
Z-Table
- Shipping Point.
- Delivery Type
Any body please suggest the user exit or any function module and how to start code for this particular requirement.
Thanks & Regards,
Narasimha

Hi,
You can write your own vaalidation on click of loading start button.
Go to include MV56AI_IS_ENHANCEMENT of program SAPMV56A.
Click on the circular button(Enhance).
Then Edit --> Enhancement Operation --> Create.
Create your enhancement giving it a Z name.
Then in this enhancement you can write your code.
For loading start you can write your code in the following fashion.
IF fcode = 'MM_ST03'.
business logic.....
ENDIF.
Regards,
Firoz.

Post installation steps after SAP BW system copy

Hi!
I am about to do post processsing steps after system copy of SAP BW system.
1) One of the steps is to delete all entries from tables DBSTATHORA, DBSTAIHORA, DBSTATIORA,
DBSTATTORA.
Question: what is the way to do this?
2) During the installation I received the error within import ABAP step.
(IMP) INFO: import of D010TAB completed (4477754 rows) #20090505133631
DbSl Trace: Error 12801 in exec_immediate() from oci_execute_stmt(), orpc=0
DbSl Trace: ORA-12801 occurred when executing SQL stmt (parse error offset=0)
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "D010TAB~0" ON "D010TAB" ( "MASTER", "TABNAME" ) TABLESPACE PSAPSR3700 STORAGE (INITIAL 423090176 NEXT 0000000640K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) NOLOGGING COMPUTE STATISTICS PARALLEL )
DbSlExecute: rc = 99
(SQL error 12801)
error message returned by DbSl:
ORA-12801: error signaled in parallel query server P000
ORA-01659: unable to allocate MINEXTENTS beyond 34 in tablespace PSAPSR3700
(DB) INFO: disconnected from DB
As solution I changed the the following lines within D010TAB.TSK:
from D010TAB~ 0 C err to D010TAB~0 C ign and
from D010TAB1 C err to D010TAB1 C ign
Question:
how to create index manually after system copy?
Thnak you very much!

Jgen Pfeiffer wrote:>
> Hi!
>
> I am about to do post processsing steps after system copy of SAP BW system.
>
> 1) One of the steps is to delete all entries from tables DBSTATHORA, DBSTAIHORA, DBSTATIORA,
> DBSTATTORA.
> Question: what is the way to do this?
Simply run
TRUNCATE TABLE <table_name>;
for each of those tables.
Make sure to either logon as SAP<SID> or provide the owner of the tables with the statement.
> 2) During the installation I received the error within import ABAP step.
> (IMP) INFO: import of D010TAB completed (4477754 rows) #20090505133631
> DbSl Trace: Error 12801 in exec_immediate() from oci_execute_stmt(), orpc=0
> DbSl Trace: ORA-12801 occurred when executing SQL stmt (parse error offset=0)
> (DB) ERROR: DDL statement failed
> (CREATE UNIQUE INDEX "D010TAB~0" ON "D010TAB" ( "MASTER", "TABNAME" ) TABLESPACE PSAPSR3700 STORAGE (INITIAL 423090176 NEXT 0000000640K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) NOLOGGING COMPUTE STATISTICS PARALLEL )
> DbSlExecute: rc = 99
> (SQL error 12801)
> error message returned by DbSl:
> ORA-12801: error signaled in parallel query server P000
> ORA-01659: unable to allocate MINEXTENTS beyond 34 in tablespace PSAPSR3700
> (DB) INFO: disconnected from DB
>
> As solution I changed the the following lines within D010TAB.TSK:
> from D010TAB~ 0 C err to D010TAB~0 C ign and
> from D010TAB1 C err to D010TAB1 C ign
>
> Question:
> how to create index manually after system copy?
The problem here was the large INITIAL size clause.
If there is enough freespace at all in the tablespace this should work:
CREATE UNIQUE INDEX "D010TAB~0" ON "D010TAB" ( "MASTER", "TABNAME" ) TABLESPACE PSAPSR3700 NOLOGGING COMPUTE STATISTICS PARALLEL;
If I'm not wrong, the second index is just vice versa:
CREATE UNIQUE INDEX "D010TAB~1" ON "D010TAB" ( "TABNAME", "MASTER" ) TABLESPACE PSAPSR3700 NOLOGGING COMPUTE STATISTICS PARALLEL;
In general it is really not a good idea to skip the creation of unique indexes...
regards,
Lars

Change posted reversed FI document (G/L) posting date

Hi All, my finance staff wrongly enter the posting date when she reverse a FI document. She wanted to know the way to change the poster reversed FI document, if possible.
Or
can she undo the reverse process back to before reverse so that she can redo...
thanks. Looi

Hi,
Reversal document can'be reversed again.
You have to post a manual entry for this using F-02.
Also you can use FBR2(Select Generate reverse posting)
Rgds
Murali. N

CORUAWFP "An application for posting goods movements is already active"

Hi Experts,
We have a strange message- we don't get it why this happnes so often.
In our system, production order confirmatins are done vai BAPI (BAPI_PRODORDCONF_CREATE_TT) and we are executing CO1P (CORUAWFP) every 10 minutes in order to avoid "Intended Goods Movements (GRs are suspendded, because of Lock sutuation)" .
The problem is when CO1P(CORUAWFP)) is kicked, sometimes a strange message is displayed ,"An application for posting goods movements is already active" , and the job ends abnormaly. We are sure we don't run CO1P (CORUAWFP) in parallel.
Why this situation happnens?
Thanks in advance.
Best Refards,
/Hiro Okamoto
Edited by: Hiro Okamoto on Aug 27, 2011 5:36 PM
Edited by: Hiro Okamoto on Aug 27, 2011 5:37 PM
Edited by: Hiro Okamoto on Aug 27, 2011 5:37 PM

The message simply means there are 2 or more programs being executed simultaneously accessing the same set of data & hence a locking occurs or the table lock is not getting released within time so that the next program can get a lock.
Get in touch with your system admin & ask them to monitor & let you know which programs are locking. Once you have that info, you can then change the schedule of the programs to prevent locking.

I changed my gmail password after suspicious activity was detected. It works fine on my computer but my iphone 5 doesn't recognize my new password ("cannot get mail" message). I've tried changing my phone settings to the new password, but no good.

I changed my gmail password after suspicious activity was detected. It works fine on my computer but my iphone 5 doesn't recognize my new password ("cannot get mail" message). I've tried changing my phone settings to the new password, but no good.

Hello there dinadinadina,
It sounds like you have modified the password settings for your Gmail account after changing the password. Thats where I would have started too. Next I would restart the device and test it one more time, and then remove and add the account again in Settings:
Get help with Mail on iPhone, iPad, and iPod touch
Restart your iOS device.
Delete the affected email account from your device.
Tap Settings > Mail, Contacts, Calendars.
Tap the affected email account.
Tap Delete Account.
Add your account again.
Thank you for using Apple Support Communities.
Take care,
Sterling

Can I install Flash CS4 after installing, activating & updating Photoshop CS5 ?

Can I install Flash CS4 after installing, activating & updating Photoshop CS5 ?

Sure. I have Flash 8, CS3,4,5 all installed and each will run.

ERS posting reverse GR after flag activated, ignoring original GR

Similar Messages

Maybe you are looking for