No transactions transferred to GL

Sample transactions has been processed in Oracle Inventory through an OPM organization with standard cost for items. After closing inventory period, running cost rollup, running cost update, and test subledger update, no transactions transferred to GL.
The log file of Subledger Update Process (OPM Subledger Update) has the following lines
Inv trans rows retrieved:6 Rows selected for processing:0
0 rows written to sub-ledger for inv trans.

Is this issue resolved ? Definitely the view->error messages in the subledger should show the reason, if you have valid transactions and still not seeing any subledger posting.
Thanks
Dinesh

Similar Messages

Account Merging- Transaction Transferring Issue

Hi Everyone,
We are working on merging accounts in SAP CRM WEB UI. Now the issue is that the transactiosn like leads, opportunities are not getting transferred from Source BP to Master BP.
Please suggest me inputs to achieve this at the earliest.
Thanks
Aakshi Suri

This depends on the transaction in the back end.
I guess that once you click save in VA01 the transaction is being left. So in the SAPGui you leave the transaction as well.
Once the transaction is left in transaction launcher, the transaction launcer assumes that the call is ended and needs to determine where to navigate instead...
Whenever an ITS ased launch transaction has ended the transaction launcer also end the related session as otherwise this would just consume ressources and could never be reused.
Peter

Inventory Transaction to Projects

Hi,
I am working on DEMO Instance (12.0.4).
- Created a User Transaction Type with Project enabled
- Created an Expenditure Type with Exp. Category as "Inventory Transfers"
- Did the Misc. Receipt (Which I have created in step 1) with Required Project Information.
- Ran the "Cost Manager" and the transaction Costed successfully (Material Transaction -> Reason, Reference Column -> Costed 'YES')
- Ran the "Cost Collection Manager" and found from the Table (PA_TRANSACTION_INTERFACE_ALL) that No Transaction happen. (From Application I found that, Inv ->Material Transaction -> Transferred to Projects 'NOT APPLICABLE' ).
Why Transferred To Projects is "NOT APPLICABLE". Did I miss any step.
Regards,
Khan.

Hi
There could be several reasons:
The item cost may be zero - will not transfer
You may be acting with an expense type item - will not transfer.
The subinventory you are taking the item from may be an expense subinventory - will not transfer.
If you are working in a PJM organization, when the MISC Issue is taking item from locator of project A task B, and issuing it to the same project and task, the system will not transfer the transaction to Projects.
Dina

Asset Transfers

Hi Guys,
I am geting this error while i am trying to transfer assets via T-code ABUM (since this t-code gives you an option to enter transaction type). Basic requirment is to pass-on the trading partner as well and thats why i am trying to use transaction type 350 -- Transfer prior-yr acquis to affiliated company.
Please suggest me how to get rid of the error - "Contact your system administrator(Table Error)"
Drill down error is:
Contact your system administrator (table error)
Message no. AA423
Diagnosis
You are using a transaction type for a transfer between affiliated companies. You cannot post using transaction type 350.
According to the Customizing definition for this transaction type, posting has to be made to area 01. However, this area has been defined for 'Transfer from affiliated company - gross' (Asset Customizing: Valuation -> Areas).
System Response
The posting is rejected.
Procedure
Check the transaction type entered and the specifications for the area named above.
Thanks,
Maulik

Hi,
check whether any limitations are specified for TTY-350:
Financial Accounting> Asset Accounting> Transactions> Transfers> Define Transaction Types for Transfers> Limit Transaction Types to Depreciation Areas (OAXC)
if limitations exists include your depreciation area 01, other wise remove the limitations.
Thanks
VK

Script to download source packages

Hi there,
I've made a Bash script "getsrc.sh" which download easily and quickly source packages from AUR or ABS (dependencies : yaourt and makepkg). The idea is just to do in one command, something we usually do in several commands (I use yaourt -G, then makepkg -o). Example :
/home/ehmicky $ getsrc gnome-terminal
/tmp/gnome-terminal/src/gnome-terminal-3.2.1 $ ls
aclocal.m4 AUTHORS ChangeLog ChangeLog.pre-2-23 ChangeLog.README config.guess
config.h.in config.sub configure configure.ac COPYING depcomp
gnome-doc-utils.make gnome-terminal.desktop.in.in HACKING help install-sh ltmain.sh
Makefile.am Makefile.in missing mkinstalldirs NEWS omf.make
po README src xmldocs.make
It's just a Bash script you need to source in your ~/.bashrc if you want to use :
source /path/to/getsrc.sh
I didn't package it cause I'm new to Archlinux and still uncomfortable with the packaging procedure right now.
I'm really not sure this might be useful for anyone (it might probably be useless indeed). I guess there are already alternatives doing just the same thign, but since while googling for it, I didn't bump into them, I thought I could post this script just in case.
Do getsrc -h for usage.
Here is the script file :
#!/bin/bash
#============================================================================
# NAME : getsrc
# DESCRIPTION : Download source packages from ABS or AUR.
# AUTHOR AND COPYRIGHT : ehmicky <ehmickyy at hotmail dot fr>
# LICENSE : GPL3, see end of file
# DEPENDENCIES : yaourt makepkg
# USAGE : getsrc PACKAGE_NAME...
# INSTALLATION : this file needs to be sourced (e.g. "source
# getsrc.sh") in your ~/.bashrc
# VARIABLES :
# SourceDir : directory where to download the source package (default :
# current directory)
# VERSION : 1.1 (13/03/2012)
# CHANGELOG : 1.1
# * Supressed output
# * Fix getopts bug
# 1.0
# * First release
#============================================================================
#Must define a function so it doesn't spawn a new subshell, and so we can
#change the current directory of the caller
getsrc()
#Define this variable to change the download directory for source packages
#(default is the current directory)
local SourceDir="/tmp/MyTemp"
#Verify dependencies
test_command()
while (( $# ))
do
if ! type "$1" &> /dev/null
then
echo "Error: $1 is not installed." >&2
return 1
fi
shift
done
test_command yaourt makepkg
#Script options : see help message for more info
local makepkg_options="#"
OPTIND=1
while getopts ":hr" Opt
do
case "$Opt" in
h)
echo "getsrc: Download source packages from ABS or AUR
Usage: $0 [OPTION]... PACKAGE_NAME...
-r Use this option if you're root.
-h Prints this help message.
E-mail bug reports to: <ehmickyy at hotmail dot fr>"
return ;;
r)
local makepkg_options="--asroot" ;;
echo "Error: -$OPTARG is not a valid option." >&2
return 1 ;;
esac
done
shift $(( OPTIND - 1 ))
local _SourceDir="${SourceDir:-.}"
if [[ $UID -eq 0 && "$makepkg_options" != *"--asroot"* ]]
then
echo "Error: when root, please use the -r flag." >&2
return 1
fi
#Process every argument from command line
while (( $# ))
do
local PreviousDir="$PWD"
#Go in the source package download directory
[[ -d "$_SourceDir" ]]\
|| mkdir -p "$_SourceDir"
if [[ ! -d "$_SourceDir" ]]
then
echo "Error: cannot create directory $_SourceDir" >&2
cd "$PreviousDir"
return 1
fi
cd "$_SourceDir"
#Download the ABS of the package
yaourt -G "$1" > /dev/null 2>&1
#Check is the ABS has been downloaded
if [[ ! -d "$1" ]]
then
echo "Error: $1 is not a valid package name" >&2
local RelatedPackages="$( yaourt --color -Ss "$1"\
| sed -n 'h;n;p;g;p'\
| tac) "
[[ "$RelatedPackages" =~ ^\ *$ ]]\
|| echo -e "Maybe you meant:\n$RelatedPackages" >&2
cd "$PreviousDir"
return 1
fi
#Download the source package from the ABS
cd "$1"
if ! makepkg -o "$makepkg_options" > /dev/null 2>&1
then
echo "Error: could not download source package" >&2
rm -r "$_SourceDir/$1"
cd "$PreviousDir"
return 1
fi
#Goes to the root of the source package
[[ -d "src/" ]]\
|| return
cd "src/"
local FinalSourceDir="$( find -mindepth 1 -maxdepth 1 -type d )"
[[ -d "$FinalSourceDir" ]]\
&& cd "$FinalSourceDir"
#Process next argument
shift
done
# GNU GENERAL PUBLIC LICENSE
# Version 3, 29 June 2007
# Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
# Everyone is permitted to copy and distribute verbatim copies
# of this license document, but changing it is not allowed.
# Preamble
# The GNU General Public License is a free, copyleft license for
# software and other kinds of works.
# The licenses for most software and other practical works are designed
# to take away your freedom to share and change the works. By contrast,
# the GNU General Public License is intended to guarantee your freedom to
# share and change all versions of a program--to make sure it remains free
# software for all its users. We, the Free Software Foundation, use the
# GNU General Public License for most of our software; it applies also to
# any other work released this way by its authors. You can apply it to
# your programs, too.
# When we speak of free software, we are referring to freedom, not
# price. Our General Public Licenses are designed to make sure that you
# have the freedom to distribute copies of free software (and charge for
# them if you wish), that you receive source code or can get it if you
# want it, that you can change the software or use pieces of it in new
# free programs, and that you know you can do these things.
# To protect your rights, we need to prevent others from denying you
# these rights or asking you to surrender the rights. Therefore, you have
# certain responsibilities if you distribute copies of the software, or if
# you modify it: responsibilities to respect the freedom of others.
# For example, if you distribute copies of such a program, whether
# gratis or for a fee, you must pass on to the recipients the same
# freedoms that you received. You must make sure that they, too, receive
# or can get the source code. And you must show them these terms so they
# know their rights.
# Developers that use the GNU GPL protect your rights with two steps:
# (1) assert copyright on the software, and (2) offer you this License
# giving you legal permission to copy, distribute and/or modify it.
# For the developers' and authors' protection, the GPL clearly explains
# that there is no warranty for this free software. For both users' and
# authors' sake, the GPL requires that modified versions be marked as
# changed, so that their problems will not be attributed erroneously to
# authors of previous versions.
# Some devices are designed to deny users access to install or run
# modified versions of the software inside them, although the manufacturer
# can do so. This is fundamentally incompatible with the aim of
# protecting users' freedom to change the software. The systematic
# pattern of such abuse occurs in the area of products for individuals to
# use, which is precisely where it is most unacceptable. Therefore, we
# have designed this version of the GPL to prohibit the practice for those
# products. If such problems arise substantially in other domains, we
# stand ready to extend this provision to those domains in future versions
# of the GPL, as needed to protect the freedom of users.
# Finally, every program is threatened constantly by software patents.
# States should not allow patents to restrict development and use of
# software on general-purpose computers, but in those that do, we wish to
# avoid the special danger that patents applied to a free program could
# make it effectively proprietary. To prevent this, the GPL assures that
# patents cannot be used to render the program non-free.
# The precise terms and conditions for copying, distribution and
# modification follow.
# TERMS AND CONDITIONS
# 0. Definitions.
# "This License" refers to version 3 of the GNU General Public License.
# "Copyright" also means copyright-like laws that apply to other kinds of
# works, such as semiconductor masks.
# "The Program" refers to any copyrightable work licensed under this
# License. Each licensee is addressed as "you". "Licensees" and
# "recipients" may be individuals or organizations.
# To "modify" a work means to copy from or adapt all or part of the work
# in a fashion requiring copyright permission, other than the making of an
# exact copy. The resulting work is called a "modified version" of the
# earlier work or a work "based on" the earlier work.
# A "covered work" means either the unmodified Program or a work based
# on the Program.
# To "propagate" a work means to do anything with it that, without
# permission, would make you directly or secondarily liable for
# infringement under applicable copyright law, except executing it on a
# computer or modifying a private copy. Propagation includes copying,
# distribution (with or without modification), making available to the
# public, and in some countries other activities as well.
# To "convey" a work means any kind of propagation that enables other
# parties to make or receive copies. Mere interaction with a user through
# a computer network, with no transfer of a copy, is not conveying.
# An interactive user interface displays "Appropriate Legal Notices"
# to the extent that it includes a convenient and prominently visible
# feature that (1) displays an appropriate copyright notice, and (2)
# tells the user that there is no warranty for the work (except to the
# extent that warranties are provided), that licensees may convey the
# work under this License, and how to view a copy of this License. If
# the interface presents a list of user commands or options, such as a
# menu, a prominent item in the list meets this criterion.
# 1. Source Code.
# The "source code" for a work means the preferred form of the work
# for making modifications to it. "Object code" means any non-source
# form of a work.
# A "Standard Interface" means an interface that either is an official
# standard defined by a recognized standards body, or, in the case of
# interfaces specified for a particular programming language, one that
# is widely used among developers working in that language.
# The "System Libraries" of an executable work include anything, other
# than the work as a whole, that (a) is included in the normal form of
# packaging a Major Component, but which is not part of that Major
# Component, and (b) serves only to enable use of the work with that
# Major Component, or to implement a Standard Interface for which an
# implementation is available to the public in source code form. A
# "Major Component", in this context, means a major essential component
# (kernel, window system, and so on) of the specific operating system
# (if any) on which the executable work runs, or a compiler used to
# produce the work, or an object code interpreter used to run it.
# The "Corresponding Source" for a work in object code form means all
# the source code needed to generate, install, and (for an executable
# work) run the object code and to modify the work, including scripts to
# control those activities. However, it does not include the work's
# System Libraries, or general-purpose tools or generally available free
# programs which are used unmodified in performing those activities but
# which are not part of the work. For example, Corresponding Source
# includes interface definition files associated with source files for
# the work, and the source code for shared libraries and dynamically
# linked subprograms that the work is specifically designed to require,
# such as by intimate data communication or control flow between those
# subprograms and other parts of the work.
# The Corresponding Source need not include anything that users
# can regenerate automatically from other parts of the Corresponding
# Source.
# The Corresponding Source for a work in source code form is that
# same work.
# 2. Basic Permissions.
# All rights granted under this License are granted for the term of
# copyright on the Program, and are irrevocable provided the stated
# conditions are met. This License explicitly affirms your unlimited
# permission to run the unmodified Program. The output from running a
# covered work is covered by this License only if the output, given its
# content, constitutes a covered work. This License acknowledges your
# rights of fair use or other equivalent, as provided by copyright law.
# You may make, run and propagate covered works that you do not
# convey, without conditions so long as your license otherwise remains
# in force. You may convey covered works to others for the sole purpose
# of having them make modifications exclusively for you, or provide you
# with facilities for running those works, provided that you comply with
# the terms of this License in conveying all material for which you do
# not control copyright. Those thus making or running the covered works
# for you must do so exclusively on your behalf, under your direction
# and control, on terms that prohibit them from making any copies of
# your copyrighted material outside their relationship with you.
# Conveying under any other circumstances is permitted solely under
# the conditions stated below. Sublicensing is not allowed; section 10
# makes it unnecessary.
# 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
# No covered work shall be deemed part of an effective technological
# measure under any applicable law fulfilling obligations under article
# 11 of the WIPO copyright treaty adopted on 20 December 1996, or
# similar laws prohibiting or restricting circumvention of such
# measures.
# When you convey a covered work, you waive any legal power to forbid
# circumvention of technological measures to the extent such circumvention
# is effected by exercising rights under this License with respect to
# the covered work, and you disclaim any intention to limit operation or
# modification of the work as a means of enforcing, against the work's
# users, your or third parties' legal rights to forbid circumvention of
# technological measures.
# 4. Conveying Verbatim Copies.
# You may convey verbatim copies of the Program's source code as you
# receive it, in any medium, provided that you conspicuously and
# appropriately publish on each copy an appropriate copyright notice;
# keep intact all notices stating that this License and any
# non-permissive terms added in accord with section 7 apply to the code;
# keep intact all notices of the absence of any warranty; and give all
# recipients a copy of this License along with the Program.
# You may charge any price or no price for each copy that you convey,
# and you may offer support or warranty protection for a fee.
# 5. Conveying Modified Source Versions.
# You may convey a work based on the Program, or the modifications to
# produce it from the Program, in the form of source code under the
# terms of section 4, provided that you also meet all of these conditions:
# a) The work must carry prominent notices stating that you modified
# it, and giving a relevant date.
# b) The work must carry prominent notices stating that it is
# released under this License and any conditions added under section
# 7. This requirement modifies the requirement in section 4 to
# "keep intact all notices".
# c) You must license the entire work, as a whole, under this
# License to anyone who comes into possession of a copy. This
# License will therefore apply, along with any applicable section 7
# additional terms, to the whole of the work, and all its parts,
# regardless of how they are packaged. This License gives no
# permission to license the work in any other way, but it does not
# invalidate such permission if you have separately received it.
# d) If the work has interactive user interfaces, each must display
# Appropriate Legal Notices; however, if the Program has interactive
# interfaces that do not display Appropriate Legal Notices, your
# work need not make them do so.
# A compilation of a covered work with other separate and independent
# works, which are not by their nature extensions of the covered work,
# and which are not combined with it such as to form a larger program,
# in or on a volume of a storage or distribution medium, is called an
# "aggregate" if the compilation and its resulting copyright are not
# used to limit the access or legal rights of the compilation's users
# beyond what the individual works permit. Inclusion of a covered work
# in an aggregate does not cause this License to apply to the other
# parts of the aggregate.
# 6. Conveying Non-Source Forms.
# You may convey a covered work in object code form under the terms
# of sections 4 and 5, provided that you also convey the
# machine-readable Corresponding Source under the terms of this License,
# in one of these ways:
# a) Convey the object code in, or embodied in, a physical product
# (including a physical distribution medium), accompanied by the
# Corresponding Source fixed on a durable physical medium
# customarily used for software interchange.
# b) Convey the object code in, or embodied in, a physical product
# (including a physical distribution medium), accompanied by a
# written offer, valid for at least three years and valid for as
# long as you offer spare parts or customer support for that product
# model, to give anyone who possesses the object code either (1) a
# copy of the Corresponding Source for all the software in the
# product that is covered by this License, on a durable physical
# medium customarily used for software interchange, for a price no
# more than your reasonable cost of physically performing this
# conveying of source, or (2) access to copy the
# Corresponding Source from a network server at no charge.
# c) Convey individual copies of the object code with a copy of the
# written offer to provide the Corresponding Source. This
# alternative is allowed only occasionally and noncommercially, and
# only if you received the object code with such an offer, in accord
# with subsection 6b.
# d) Convey the object code by offering access from a designated
# place (gratis or for a charge), and offer equivalent access to the
# Corresponding Source in the same way through the same place at no
# further charge. You need not require recipients to copy the
# Corresponding Source along with the object code. If the place to
# copy the object code is a network server, the Corresponding Source
# may be on a different server (operated by you or a third party)
# that supports equivalent copying facilities, provided you maintain
# clear directions next to the object code saying where to find the
# Corresponding Source. Regardless of what server hosts the
# Corresponding Source, you remain obligated to ensure that it is
# available for as long as needed to satisfy these requirements.
# e) Convey the object code using peer-to-peer transmission, provided
# you inform other peers where the object code and Corresponding
# Source of the work are being offered to the general public at no
# charge under subsection 6d.
# A separable portion of the object code, whose source code is excluded
# from the Corresponding Source as a System Library, need not be
# included in conveying the object code work.
# A "User Product" is either (1) a "consumer product", which means any
# tangible personal property which is normally used for personal, family,
# or household purposes, or (2) anything designed or sold for incorporation
# into a dwelling. In determining whether a product is a consumer product,
# doubtful cases shall be resolved in favor of coverage. For a particular
# product received by a particular user, "normally used" refers to a
# typical or common use of that class of product, regardless of the status
# of the particular user or of the way in which the particular user
# actually uses, or expects or is expected to use, the product. A product
# is a consumer product regardless of whether the product has substantial
# commercial, industrial or non-consumer uses, unless such uses represent
# the only significant mode of use of the product.
# "Installation Information" for a User Product means any methods,
# procedures, authorization keys, or other information required to install
# and execute modified versions of a covered work in that User Product from
# a modified version of its Corresponding Source. The information must
# suffice to ensure that the continued functioning of the modified object
# code is in no case prevented or interfered with solely because
# modification has been made.
# If you convey an object code work under this section in, or with, or
# specifically for use in, a User Product, and the conveying occurs as
# part of a transaction in which the right of possession and use of the
# User Product is transferred to the recipient in perpetuity or for a
# fixed term (regardless of how the transaction is characterized), the
# Corresponding Source conveyed under this section must be accompanied
# by the Installation Information. But this requirement does not apply
# if neither you nor any third party retains the ability to install
# modified object code on the User Product (for example, the work has
# been installed in ROM).
# The requirement to provide Installation Information does not include a
# requirement to continue to provide support service, warranty, or updates
# for a work that has been modified or installed by the recipient, or for
# the User Product in which it has been modified or installed. Access to a
# network may be denied when the modification itself materially and
# adversely affects the operation of the network or violates the rules and
# protocols for communication across the network.
# Corresponding Source conveyed, and Installation Information provided,
# in accord with this section must be in a format that is publicly
# documented (and with an implementation available to the public in
# source code form), and must require no special password or key for
# unpacking, reading or copying.
# 7. Additional Terms.
# "Additional permissions" are terms that supplement the terms of this
# License by making exceptions from one or more of its conditions.
# Additional permissions that are applicable to the entire Program shall
# be treated as though they were included in this License, to the extent
# that they are valid under applicable law. If additional permissions
# apply only to part of the Program, that part may be used separately
# under those permissions, but the entire Program remains governed by
# this License without regard to the additional permissions.
# When you convey a copy of a covered work, you may at your option
# remove any additional permissions from that copy, or from any part of
# it. (Additional permissions may be written to require their own
# removal in certain cases when you modify the work.) You may place
# additional permissions on material, added by you to a covered work,
# for which you have or can give appropriate copyright permission.
# Notwithstanding any other provision of this License, for material you
# add to a covered work, you may (if authorized by the copyright holders of
# that material) supplement the terms of this License with terms:
# a) Disclaiming warranty or limiting liability differently from the
# terms of sections 15 and 16 of this License; or
# b) Requiring preservation of specified reasonable legal notices or
# author attributions in that material or in the Appropriate Legal
# Notices displayed by works containing it; or
# c) Prohibiting misrepresentation of the origin of that material, or
# requiring that modified versions of such material be marked in
# reasonable ways as different from the original version; or
# d) Limiting the use for publicity purposes of names of licensors or
# authors of the material; or
# e) Declining to grant rights under trademark law for use of some
# trade names, trademarks, or service marks; or
# f) Requiring indemnification of licensors and authors of that
# material by anyone who conveys the material (or modified versions of
# it) with contractual assumptions of liability to the recipient, for
# any liability that these contractual assumptions directly impose on
# those licensors and authors.
# All other non-permissive additional terms are considered "further
# restrictions" within the meaning of section 10. If the Program as you
# received it, or any part of it, contains a notice stating that it is
# governed by this License along with a term that is a further
# restriction, you may remove that term. If a license document contains
# a further restriction but permits relicensing or conveying under this
# License, you may add to a covered work material governed by the terms
# of that license document, provided that the further restriction does
# not survive such relicensing or conveying.
# If you add terms to a covered work in accord with this section, you
# must place, in the relevant source files, a statement of the
# additional terms that apply to those files, or a notice indicating
# where to find the applicable terms.
# Additional terms, permissive or non-permissive, may be stated in the
# form of a separately written license, or stated as exceptions;
# the above requirements apply either way.
# 8. Termination.
# You may not propagate or modify a covered work except as expressly
# provided under this License. Any attempt otherwise to propagate or
# modify it is void, and will automatically terminate your rights under
# this License (including any patent licenses granted under the third
# paragraph of section 11).
# However, if you cease all violation of this License, then your
# license from a particular copyright holder is reinstated (a)
# provisionally, unless and until the copyright holder explicitly and
# finally terminates your license, and (b) permanently, if the copyright
# holder fails to notify you of the violation by some reasonable means
# prior to 60 days after the cessation.
# Moreover, your license from a particular copyright holder is
# reinstated permanently if the copyright holder notifies you of the
# violation by some reasonable means, this is the first time you have
# received notice of violation of this License (for any work) from that
# copyright holder, and you cure the violation prior to 30 days after
# your receipt of the notice.
# Termination of your rights under this section does not terminate the
# licenses of parties who have received copies or rights from you under
# this License. If your rights have been terminated and not permanently
# reinstated, you do not qualify to receive new licenses for the same
# material under section 10.
# 9. Acceptance Not Required for Having Copies.
# You are not required to accept this License in order to receive or
# run a copy of the Program. Ancillary propagation of a covered work
# occurring solely as a consequence of using peer-to-peer transmission
# to receive a copy likewise does not require acceptance. However,
# nothing other than this License grants you permission to propagate or
# modify any covered work. These actions infringe copyright if you do
# not accept this License. Therefore, by modifying or propagating a
# covered work, you indicate your acceptance of this License to do so.
# 10. Automatic Licensing of Downstream Recipients.
# Each time you convey a covered work, the recipient automatically
# receives a license from the original licensors, to run, modify and
# propagate that work, subject to this License. You are not responsible
# for enforcing compliance by third parties with this License.
# An "entity transaction" is a transaction transferring control of an
# organization, or substantially all assets of one, or subdividing an
# organization, or merging organizations. If propagation of a covered
# work results from an entity transaction, each party to that
# transaction who receives a copy of the work also receives whatever
# licenses to the work the party's predecessor in interest had or could
# give under the previous paragraph, plus a right to possession of the
# Corresponding Source of the work from the predecessor in interest, if
# the predecessor has it or can get it with reasonable efforts.
# You may not impose any further restrictions on the exercise of the
# rights granted or affirmed under this License. For example, you may
# not impose a license fee, royalty, or other charge for exercise of
# rights granted under this License, and you may not initiate litigation
# (including a cross-claim or counterclaim in a lawsuit) alleging that
# any patent claim is infringed by making, using, selling, offering for
# sale, or importing the Program or any portion of it.
# 11. Patents.
# A "contributor" is a copyright holder who authorizes use under this
# License of the Program or a work on which the Program is based. The
# work thus licensed is called the contributor's "contributor version".
# A contributor's "essential patent claims" are all patent claims
# owned or controlled by the contributor, whether already acquired or
# hereafter acquired, that would be infringed by some manner, permitted
# by this License, of making, using, or selling its contributor version,
# but do not include claims that would be infringed only as a
# consequence of further modification of the contributor version. For
# purposes of this definition, "control" includes the right to grant
# patent sublicenses in a manner consistent with the requirements of
# this License.
# Each contributor grants you a non-exclusive, worldwide, royalty-free
# patent license under the contributor's essential patent claims, to
# make, use, sell, offer for sale, import and otherwise run, modify and
# propagate the contents of its contributor version.
# In the following three paragraphs, a "patent license" is any express
# agreement or commitment, however denominated, not to enforce a patent
# (such as an express permission to practice a patent or covenant not to
# sue for patent infringement). To "grant" such a patent license to a
# party means to make such an agreement or commitment not to enforce a
# patent against the party.
# If you convey a covered work, knowingly relying on a patent license,
# and the Corresponding Source of the work is not available for anyone
# to copy, free of charge and under the terms of this License, through a
# publicly available network server or other readily accessible means,
# then you must either (1) cause the Corresponding Source to be so
# available, or (2) arrange to deprive yourself of the benefit of the
# patent license for this particular work, or (3) arrange, in a manner
# consistent with the requirements of this License, to extend the patent
# license to downstream recipients. "Knowingly relying" means you have
# actual knowledge that, but for the patent license, your conveying the
# covered work in a country, or your recipient's use of the covered work
# in a country, would infringe one or more identifiable patents in that
# country that you have reason to believe are valid.
# If, pursuant to or in connection with a single transaction or
# arrangement, you convey, or propagate by procuring conveyance of, a
# covered work, and grant a patent license to some of the parties
# receiving the covered work authorizing them to use, propagate, modify
# or convey a specific copy of the covered work, then the patent license
# you grant is automatically extended to all recipients of the covered
# work and works based on it.
# A patent license is "discriminatory" if it does not include within
# the scope of its coverage, prohibits the exercise of, or is
# conditioned on the non-exercise of one or more of the rights that are
# specifically granted under this License. You may not convey a covered
# work if you are a party to an arrangement with a third party that is
# in the business of distributing software, under which you make payment
# to the third party based on the extent of your activity of conveying
# the work, and under which the third party grants, to any of the
# parties who would receive the covered work from you, a discriminatory
# patent license (a) in connection with copies of the covered work
# conveyed by you (or copies made from those copies), or (b) primarily
# for and in connection with specific products or compilations that
# contain the covered work, unless you entered into that arrangement,
# or that patent license was granted, prior to 28 March 2007.
# Nothing in this License shall be construed as excluding or limiting
# any implied license or other defenses to infringement that may
# otherwise be available to you under applicable patent law.
# 12. No Surrender of Others' Freedom.
# If conditions are imposed on you (whether by court order, agreement or
# otherwise) that contradict the conditions of this License, they do not
# excuse you from the conditions of this License. If you cannot convey a
# covered work so as to satisfy simultaneously your obligations under this
# License and any other pertinent obligations, then as a consequence you may
# not convey it at all. For example, if you agree to terms that obligate you
# to collect a royalty for further conveying from those to whom you convey
# the Program, the only way you could satisfy both those terms and this
# License would be to refrain entirely from conveying the Program.
# 13. Use with the GNU Affero General Public License.
# Notwithstanding any other provision of this License, you have
# permission to link or combine any covered work with a work licensed
# under version 3 of the GNU Affero General Public License into a single
# combined work, and to convey the resulting work. The terms of this
# License will continue to apply to the part which is the covered work,
# but the special requirements of the GNU Affero General Public License,
# section 13, concerning interaction through a network will apply to the
# combination as such.
# 14. Revised Versions of this License.
# The Free Software Foundation may publish revised and/or new versions of
# the GNU General Public License from time to time. Such new versions will
# be similar in spirit to the present version, but may differ in detail to
# address new problems or concerns.
# Each version is given a distinguishing version number. If the
# Program specifies that a certain numbered version of the GNU General
# Public License "or any later version" applies to it, you have the
# option of following the terms and conditions either of that numbered
# version or of any later version published by the Free Software
# Foundation. If the Program does not specify a version number of the
# GNU General Public License, you may choose any version ever published
# by the Free Software Foundation.
# If the Program specifies that a proxy can decide which future
# versions of the GNU General Public License can be used, that proxy's
# public statement of acceptance of a version permanently authorizes you
# to choose that version for the Program.
# Later license versions may give you additional or different
# permissions. However, no additional obligations are imposed on any
# author or copyright holder as a result of your choosing to follow a
# later version.
# 15. Disclaimer of Warranty.
# THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
# APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
# HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
# OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
# THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
# PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
# IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
# ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
# 16. Limitation of Liability.
# IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
# WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
# THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
# GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
# USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
# DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
# PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
# EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
# SUCH DAMAGES.
# 17. Interpretation of Sections 15 and 16.
# If the disclaimer of warranty and limitation of liability provided
# above cannot be given local legal effect according to their terms,
# reviewing courts shall apply local law that most closely approximates
# an absolute waiver of all civil liability in connection with the
# Program, unless a warranty or assumption of liability accompanies a
# copy of the Program in return for a fee.
# END OF TERMS AND CONDITIONS
# How to Apply These Terms to Your New Programs
# If you develop a new program, and you want it to be of the greatest
# possible use to the public, the best way to achieve this is to make it
# free software which everyone can redistribute and change under these terms.
# To do so, attach the following notices to the program. It is safest
# to attach them to the start of each source file to most effectively
# state the exclusion of warranty; and each file should have at least
# the "copyright" line and a pointer to where the full notice is found.
# <one line to give the program's name and a brief idea of what it does.>
# Copyright (C) <year> <name of author>
# This program is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
# You should have received a copy of the GNU General Public License
# along with this program. If not, see <http://www.gnu.org/licenses/>.
# Also add information on how to contact you by electronic and paper mail.
# If the program does terminal interaction, make it output a short
# notice like this when it starts in an interactive mode:
# <program> Copyright (C) <year> <name of author>
# This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
# This is free software, and you are welcome to redistribute it
# under certain conditions; type `show c' for details.
# The hypothetical commands `show w' and `show c' should show the appropriate
# parts of the General Public License. Of course, your program's commands
# might be different; for a GUI interface, you would use an "about box".
# You should also get your employer (if you work as a programmer) or school,
# if any, to sign a "copyright disclaimer" for the program, if necessary.
# For more information on this, and how to apply and follow the GNU GPL, see
# <http://www.gnu.org/licenses/>.
# The GNU General Public License does not permit incorporating your program
# into proprietary programs. If your program is a subroutine library, you
# may consider it more useful to permit linking proprietary applications with
# the library. If this is what you want to do, use the GNU Lesser General
# Public License instead of this License. But first, please read
# <http://www.gnu.org/philosophy/why-not-lgpl.html>.
Last edited by ehmicky (2012-03-13 20:46:18)

Here is the output of makepkg -s when I try to install packer:
[tilley@take-kun packer]$ makepkg -s
==> Determining latest git revision...
-> Version found: 20120509
==> Making package: packer 20120509-1 (Wed May 9 17:27:52 CDT 2012)
==> Checking runtime dependencies...
==> Installing missing dependencies...
resolving dependencies...
looking for inter-conflicts...
Targets (2): jansson-2.3-1 jshon-20111222-1
Total Download Size: 0.04 MiB
Total Installed Size: 0.17 MiB
Proceed with installation? [Y/n] y
:: Retrieving packages from community...
jansson-2.3-1-x86_64 30.5 KiB 150K/s 00:00 [######################] 100%
jshon-20111222-1-x86_64 9.8 KiB 806K/s 00:00 [######################] 100%
(2/2) checking package integrity [######################] 100%
(2/2) loading package files [######################] 100%
(2/2) checking for file conflicts [######################] 100%
(2/2) checking available disk space [######################] 100%
(1/2) installing jansson [######################] 100%
(2/2) installing jshon [######################] 100%
==> Checking buildtime dependencies...
==> Retrieving Sources...
==> Extracting Sources...
==> Entering fakeroot environment...
==> Starting build()...
==> Connecting to github GIT server....
Cloning into 'packer'...
error: Could not resolve host: (nil); No address associated with hostname while accessing https://github.com/bruenig/packer.git/info/refs
fatal: HTTP request failed
==> ERROR: A failure occurred in build().
Aborting...

How to transfer FA from one employee to Another employee

Hi to all
Anybody know that how to transfer fixed asset from one employe to another employee .plz post your reply in technical and functional aspect.
Thanks
Zulqarnain

Hi,
You can either transfer individual assets (Asset Workbench -> Assignments) or multiple assets (Mass Transactions -> Transfers)
In case of Mass Transfers, you can enter search criteria and provide from and to employee names.
- Mukul

Report S_ALR_87012050 - Asset Acquisitions

Hello,
The report S_ALR_87012050 - Asset Acquisitions is bringing only information from the "current year" acquisition - Tty 336, and it's not bringing information from the "prior year" - Tty 331.
Is it a customizing in the report to change it, or is it default by SAP?
Comparing to the report S_ALR_87011990 - Asset History Sheet, the values from the acquisition don't match because of this difference.
Thanks,
Barbara

Hi Barbara,
In our system we don't have ttype 331 and 336.
Have a look in SPRO what Transaction type grp you are using (31 or 33 should be in)
Financial Accounting / Asset Accounting / Transactions / Transfers / Define Transaction Types for Transfers.

Setting the doc.type to use for t.code ABUMN (transfer asset ...)

Hi All,
Could anyone show me where to set, in customizing, the doc.type to use for t.code ABUMN (transfer asset within company code)?
Thanks
Umberto Gandalf

AO71                   Document type for posting deprec.
AO72                   Specify posting procedure
AO73                   Define Transaction Type
AO73_INV               Define Transaction Type
AO74                   Define Transaction Type
AO75                   Define Transaction Type
AO76                   Define Transaction Type
AO77                   Define Transaction Type
AO78                   Define Transaction Type
AO79                   Define Transaction Type
AO80                   Define Transaction Type
spro- FA - AA - transactions - transfers
Rgds.

Security Deposit Migration

I am getting following error when migrating Security Deposit.
Document line item without main or sub-transaction transferred
Its workign through FPSEC1.
Please help.
Regards,

Hi,
I assume that the main\sub used for migrating the Security deposit is different from that of the main\sub for creating the security deposits in SAP via FPSEC1.
In this scenario, you need to change the allocation of internal main\sub transaction from the normal main\sub to the main\sub combination used for migration.This is a pre-migration activity.
Go to the following path in SPRO-
Financial Accounting(New)>Contract Account Receivable & Payable>basic functons-->Positng & Documents->Document->maintain Account assignments->maintain tranasction for ISU->maintain transaction for Cash Security Deposit \interest.
Click on "Allocate transactions to internal transactions".
Look for the combination of
IMTR    ISTR
0020    0010
0020    0020
There will be a main\sub assigned to it. Change that combination to that you are using in conversion.Save it and then try to migrate it once.
Hope you will not get the error again........
Thanks,
Amlan

Invoices must not be completed when run throught Autoinvoice

Dear All,
i have written a feeder programe to load data from existing system to AR module via autoinvoice, but the problem is that all transactions transfered through the feeder programe has the complete_flag set to 'Y', so data entry operator is not able to update any record. which in my case is required, so how can i set the complete_flag to 'N'.
any help will be appreciated
Regards,
Kashif Ali

So I had this as well.
I went to the file tab and went to export. From there I picked 720p and it worked. It may be different for you depending on the resolution of the video. hopefully it works for you too!

Is it possible to autocreate requisition from Projects for inventory items

Is it possible to autocreate requisition from Projects for inventory items with destination type of inventory in a non-manufacturing organization?Also how ti budget for inventory items based on actual cost i.e. FIFO cost?
Zeeshan

Hi Dina,
Hope you are fine and enjoyed the weekend.
Thanks for your help, yes there was an error in the Material Transactions form, i have corrected and PA_TRANSACTIONS interface got updated. I issued the stock to Project and there was'nt any transaction transferred to Projects.
I just want to confirm one more thing, we are using FIFO costing method, if i procure same item for 2 different projects like Qty 1 with Rate 10 for Project 123 on 1st Jan 2010 and then i receive same item Qty 1 Rate 20 for Project 124 on 10 Jan 2010. Then everything will be transferred to Projects and Projects Expediture will be updated with the receiving Transactions.
Now what if, the stock is being issued in the reverse order than it was received. Like I enter Miscellaneous issue for Project 124 first, then as per FIFO rules system will pick Issue rate of 10 because it was received first......Due to this, dont you think its wrong from the system's point of view. Infact it should pick issue rate of 20 because it was received at 20.....
One more thing, While doing Miscellaneous Transaction with Projects enabled, do the Locator Project Number and Source Project Number needs to be same. If No then whats the control that stock received for one project should be issued against that project only.
Your thoughts on this scenario.
Zeeshan

Difference between Batch input and Direct Input

Hi please tell me the difference between Batch Input and Direct Input in BDC?

hi aparna,
DIRECT INPUT
TO ENTER THE DATA INTO THE CORRESPONDING DATABASE TABLES DIRECTLY, THE SYSTEM CALLS A NUMBER OF FUNCTION MODULES THAT EXECUTE ANY NECESSARY CHECKS. IN CASE OF ERRORS, THE DIRECT INPUT TECHNIQUE PROVIDES A RESTART MECHANISM. HOWEVER, TO BE ABLE TO ACTIVATE THE RESTART MECHANISM, DIRECT INPUT PROGRAMS MUST BE EXECUTED IN THE BACKGROUND ONLY. DIRECT INPUT CHECKS THE DATA THOROUGHLY AND THEN UPDATES THE DATABASE DIRECTLY.
TO MAINTAIN AND STRAT THESE PROGRAMS, USE PGM RBMVSHOW OR THE TRANSACTION BMVO.
BATCH INPUT
TYPES SESSION METHOD, CALL TRANSACTION, DIRECT INPUT.
TO SAVE DATA IN THE BDCTAB, USE THE FIELDNAME BDC_OKCODE AND FIELD VALUE OF /11.
BDCDATA
THIS IS A STRUCTURE WHICH CONTAINS THE FOLLOWING FIELDS.
PROGRAM NAME OF TH MOD PROG ASSOCIATED WITH THE SCREEN. SET ONLY FOR THE FIRST RECORD OF THE SCREEN.
DYNPRO SCREEN NUMBER. ALSO SET ONLY FOR FIRST RECORD.
DYNBEGIN INDICATES THE FIRST RECORD OF THE SCREEN. SET X FOR FIRST RECORD OTHERWISE .
FNAM FIELD NAME.
FVAL VALUE FOR THE FIELD NAMED IN FNAM.
THE FIRST STEP IN BDC IS TO UPLOAD DATA FROM THE FLAT FILE OR SEQUENTIAL FILE TO THIS BDCTABLE.
SESSION METHOD
WE USE 3 FUNCTION MODULES IN THIS SESSION METHOD.
1) BDC_OPEN_GROUP
 USER NAME: USER NAME
 GROUP: NAME OF THE SESSION
 LOCK DATE: THE DATE ON WHICH YOU WANT TO PROCESS THE SESSION.
 KEEP: THIS PARAMETER IS PASSED AS X WHEN YOU WANT TO RETAIN SESSION AFTER PROCESSING IT OR TO DELETE IT AFTER PROCESSING.
THIS CREATES A SESSION
2) BDC_INSERT
 TCODE: TRANSACTION NAME
 DYNPROTAB: BDC DATA
THIS CREATES A SEESION AND DATA IS TRANSFERRED O SESSION.
3) BDC_CLOSE_GROUP THIS CLOSES THE BDC GROUP.
ONLY ONE SESSION CAN BE CREATED USING BDC_OPEN_GROUP. BUT MULTIPLE TRANSACTIONS CAN BE PROCESSED USING BDC_INSERT.
CALL TRANSACTION
CALL TRANSACTION <TCODE> USING <BDCTAB>
 MODE <A/N/E>
 UPDATE <S/A>
 MESSAGES INTO <MSGTAB>.
A ALL SCREEN MODE. ALL THE SCREEN OF THE TRANSACTION ARE DISPLAYED.
N NO SCREEN MODE. NO SCREEN IS DISPLAYED WHEN YOU EXECUTE THE TRANSACTION.
E ERROR SCREEN. IF THE SCREEN HAS ERROR RECORD, THEN THAT SCREEN WILL BE DISPLAYED.
S - IF YOU CHANGE DATA OF ONE TABLE THEN ALL THE RELATED TABLES GETS UPDATED. AND SY-SUBRC IS RETURNED I.E., SY-SUBRC IS RETURNED FOR ONCE AND ALL.
A - WHEN YOU CHANGE DATA OF ONE TABLE, THE SY-SUBRC IS RETURNED. AND THEN UPDATING OF OTHER AFFECTED TABLES TAKES PLACE. SO IF SYSTEM FAILS TO UPDATE OTHER TABLES, STILL SY-SUBRC RETURNED IS 0 (I.E., WHEN FIRST TABLE GETS UPDATED
WHEN YOU UPDATE DATABASE TABLE, OPERATION IS EITHER SUCCESSFUL OR UNSUCCESSFUL OR OPERATION IS SUCCESSFUL WITH SOME WARNING. THESE MESSAGES ARE STORED IN INTERNAL TABLE, WHICH YOU SPECIFY ALONG WITH MESSAGE STATEMENT. THIS INTERNAL TABLE SHOULD BE DECLARED LIKE BDCMSGCOLL, A STRUCTURE AVAILABLE IN ABAP/4. IT CONTAINS THE FOLLOWING FIELDS: TCODE, DYNAME, DYNUMB, MSGTYP, MSGID.
DIFFERENCE BETWEEN SESSION AND CALL TRANSACTION
 SESSION METHOD CALL TRANSACTION
1. DATA IS NOT UPDATED IN DATABASE TABLE UNLESS SESSION IS PROCESSED. IMMEDIATE UPDATION IN DATABASE TABLE.
2. NO SY-SUBRC IS RETURNED. SY-SUBRC IS RETURNED.
3. ERROR LOG IS CREATED FOR ERROR RECORDS. ERRORS NEED TO BE HANDLED EXPLICITLY
4. UPDATION IN DATABASE TABLE IS ALWAYS SYNCHRONOUS
 UPDATION IN DATABASE TABLE CAN BE SYNCHRONOUS OR ASYNCHRONOUS.
5. ASYNCHRONOUS PROCESSING SYNCHRONOUS PROCESSING
6. TRANSFERS DATA FOR SINGLE TRANSACTIONS TRANSFERS DATA FOR MULTIPLE TRANSACTIONS
ERROR HANDLING IN CALL TRANSACTION
1) CREATE AN INTERNAL TABLE SIMILAR TO THE STRUCTURE OF YOUR LOCAL FILE.
2) CREATE BDCTAB LIKE BDCDATA.
3) CREATE BDCMSG LIKE BDCMSGCOLL.
4) CREATE AN INTERNAL TABLE SIMILAR TO THE 1ST INTERNAL TABLE.
5) UPLOAD FN UPLOADS DATA FROM THE LOCAL FILE TO THE ITAB.
6) LOOP AT ITAB.
POPULATE BDCTAB TABLE.
CALL TRANSACTION STATEMENT.
PERFORM CHECK.
REFRESH BDCTAB.
ENDLOOP.
7) FORM CHECK.
IF SY_SUBRC <> 0.
CALL FUNCTION FORMAT_MESSAGE.
APPEND ITAB2.
ENDFORM.
TRANSACTION FOR RECORDING SHDB.
MAX TIME ALLOWED FOR ONLINE EXECUTION 300 SECONDS.

Pls reward if helpful.

Trnasfer of Asset frm one Business Area to Another in same Company code

Hi Experts
In my Asset Accounting Business Area is mandatory field and when I transfer asset from one business area to another business area system change the asset number from old to new number, the problem is that suppose asset A with useful life of 10 years already utilized three years in business area 1010 and after three years when I transfer this asset to another business area 1020 system again calculate 10 years in new asset which is wrong it should be seven years because 3 years already used in previous business area, please help me that how to resolve this issue.

Hi
If you are transferring to a new asset - You can maintain the useful life in the new asset master as 7 yrs
Else, do the settings in IMG > AA > Transactions > Transfers > Inter CO Asset Trf > Define Trf variants.... Here, you can try to configure which fields must be taken over during transfers... This is usually used for Cross Comp Trf.. however, try to use in your case and see if it works
br, Ajay M

One Time Vendor-Transactions Need to be Transferred to Major Vendor Acct

A. One time Vendor Account is 50001.
B. Some of major Vendor entries have been Uploaded to One Time Vendor.
C. Although Balances Tally, in the financial Statements but AP Vendor Balance is messed up.
D. Major / Normal Vendors are - Polestar (Vendor), GAC (Vendor), etc.
How to transfer these entries to Normal Vendor Accounts from One Time Vendor, when Financial Statements for the year have been printed and transactions are posted.
Urgent Help requested.
Thanks.
Message was edited by: Bhatia
Bhatia

I have done the following -
1.Transaction Code used - F-51
2.Checked the option Transfer with Clearing to transfer entries from One Time Vendor to Full time Vendor; entries being KR and KG NOT KZ.
3.For KZ, with the same transaction code, I opted for Outgoing Payment Option.
Would anyone let me know, whether choosing Outgoing Payment for KZ for such a case is justified?
Rest F-51 was used for transferring the amount in a whole, but not invoices individually.
Could somebody suggest a solution to this kindly?
Thanks.
Message was edited by:
Bhatia

How to check Inventory transactions weather they have transferred to GL?

Hi All,
How I can check Inventory transactions weather they have transferred to GL or not in R12.
Example: I have performed a miscellaneous receipt it has costed as well. Now I am not transferred this transaction to GL from Cost Management i..e using create accounting program.
In this case how I can check from the Inventory tables/from the front end screens (Material Transactions) weather this transaction has transferred to GL or not.
Please let me know If you have any clarifications regarding this point.
Regards,
Kv.

Hi,
There is no way to check whether transactions has been transferred to GL or not. What material transaction form tells us is that distributions for particular transactions has been created in sub ledger tables. For transferring transactions to GL you will have to do some work regarding SRS that whenever Create Accounting Program Runs, a message should be routed that All Transactions have been transferred to GL.

No transactions transferred to GL

Similar Messages

Maybe you are looking for