Automate Account Reconciliations

Is Cash Management the module to use to automate account reconciliations?
Does the feature include reconciliation of accounts other than bank accounts, produce account logs, reference who is reconciling, handle 90+ day items etc?

Hi,
Thanks for the reply.
Currently we are doing Account assignment Manually in cProjects.
Our requirment is to make this process of Account assignment Automatic in cProjects.
(In cProjects, we are using Accounting Tab in cProjects to assign a WBS Element at the top level of the project.)
1 ) Is there a standard FM, method to add this assignment.
2) Can this be possible with the help of following Class :
cl_dpr_fin_gecco_iaom_services=>replicate2 ??
If yes- How can we use this Class and Method ( It would be great if you provide me a sample code).
Waiting for your reply.
Thanks

Similar Messages

Automatic bank reconciliation with Electronic bank statement

Deal All,
As mentioned in the subject of this mail, this is to request for your inputs to advice the configuration steps with process for Configuration of Electronic Bank Statment in R3 to eneble the user for automatic bank reconciliation with clearing customer/vendor open items.Please send confi doc.
Request you to provide documentation if possible along with your valuble advices.
cvs

Hi
I implemented the EBS in my company 4 month ago and here are some advises on the problems i experienced in the setup process. As for the setup process it is straightforward just read the manual at help.sap.com.
We used the MT940 format for importing bank statements from our bank.
The first thing i would advice you to do is make a list of all the possible transactions that are to be handled by the EBS application.
Then make estimation of how many payments that are recieved in constant structured way which the EBS can handle. (invoice number in the text)
The people in our accounting department complained alot about the output format in the EBS not being userfreindly compared to the advises they recieved in e-mail form from the bank so if not the bulk of your payments can be processed automatically it might not be worth the trouble to implement it. (i still think they uses the the email to postprocess the transactions that was not automatically cleraed)
Make sure you havent got any other applications handling some of the transactions that are contained in the bank statement because this wont work. eg. we had a program automatically placing fx trades on customer and bank account which meant that when we recieved the fx trade on the statement it was already placed and therefore had to be placed on a interims account for later reversal.
We get alot of bankcharges on our payments and we set up the EBS to place them automatically on a bankcharge account if the difference between the recieved amount on the invoice was less that 30 dollars.(we just assume that a difference is a bank charge) This means that a customer if he wants to always can pay x dollars under the invoice amount because it will be automatically processed and therefore go unnoticed.
Establish a contact in your bank who knows how their MT940 format has been structured.
Then contact your bank and get them to provide some test statements of old bank statements.
Make sure that you are not the first customer for using the MT940 format or else you will end up being ginny pig for the banks possible mistakes.
As i learned the way banks interpret the MT940 format guidelines can varry quite alot eg. the ocmt field our bank interpreted as the original payed amount in its original currency. SAP inprets this field as the recieved amount in its original currency and therefore it always try to clear the OCMT amount if availleble which meant it always tried to clear the original amount even though there had been taken som bankcharges underways.
I also found out that our bank didnt really bother to specify the type of transaction (interest, fx contract, bank charges, check and so on) which meant we only had two external transaction codes availleble s103 for incomming payments and ntrf for outgoing payments. This gave alot of trouble as i had to identify the type of transaction through seach algorithms.
Our bank also had trouble creating the MT940 file because it has a limited number of characters availleble which meant in the initial file that it only gave the first x characters of each line and then left out the rest. This meant that the text was broken into alot of pieces and you hardly ever had a complete invoice number to clear on. We had the bank altering their format so they now leave out text at the end of the transaction instead.
In the implementation process we experienced that the EBS application created a payment advice each time the amount of the payment didnt match the invoice in the system. We implemented a note from service.sap which disabled this and just assigned the difference to a bankcharge account.
I dont know if you can use these advices but just felt i would try to warn you about the potential problems that i experienced in the process. .
If you have concrete questions to the EBS setup feel free to contact me and i will see if i can help you.

Semi Automatic GL Reconciliation has no recommendations.

Hi
I am trying to reconcile a GL account. When I select the Semi Automatic method and double click and amount (that has a matching entry on the other side) there are no recommendations.
I have the settings
Amount> High
Posting Date> Medium
Ref 1 > Low
Thank you in advance for your help
Henry

Hi Henry,
Semi Automatic GL Reconciliation gives you half control. You need to play with criteria to find want recommendations could be realized based on you criteria selected. If you only need match Amount, select this setting only.
Thanks,
Gordon

How to configure Automatic Account Clearing for A/R

Hi,
Kindly advice me how to configure Automatic Account Clearing for A/R
The client requirement is
In A/R the customer accounts are not automatically clearing when a payment is posted for that account. We are still seeing all open items and all paid or cleared items when we go to FBL5N and select open items for viewing. Please make account clearing automatic for customer payments.
Thanks in advance
Sunitha

Hi,
Use T code OB74.
Maintain for your Chart Of Account, acct type "D", From and to customer accounts and then add the critera you want. Pls note you cannot define more than 5 criteria.
Then schedule the clearing program job F.13 in the background.
Cheers.

What is the user exit for automatic account determination in PO

Hi Experts
I ned to know what is the user exit for automatic account determination in PO
my client needs the document type to defines Account Assignment Category.
choosen a document type Account Assignment Category is defined automatically. you can't choose
a wrong Account Assignment Category from the drop down list.
thanks form you help.

If this is the case than why don't you use the Transaction variant
SHD0: http://www.mortenhjorthnielsen.dk/Security/transactionvariants.htm
If you have knowledge of Transaction variant then you can use SHD0 tcode and generate the transaction using default type and give that transaction to user instead of ME21N so they will not have the issue.
The exact solution for your problem is as follows
Go to Tcode SHD0 and enter the transaction variant
In T code field enter ME21N and then enter the ZXXXX or the name you want to keep in transaction variant field and hit create button
This will take you to ME21N transaction and here you just enter the data but make sure you enter the A/c which you want to default.
Once you finish system will save this one as a variant
Every time you hit or enter the pop up screen comes here you just hit enter and whichever data you want to default that you have to select in the Popup by checking the Box
W content and output only for your case the field XXXXXXXX should be selected for W content and output only
Make sure you have value 1 in contents field
If not then restart the variant again and on the ME21Nscreen reselect the invoice field
Later exit and save (save in the object which you can transport)
Then from SHD0 transaction select GOTO create variant transaction and here you careate the tcode and use that tcode for ME21N (e.g ZTRAN - For specifix sto)

Automatic account postings (for Intercompany Purchase order and Sales order

Hi all,
I need some help related to the automatic account postings (for Intercompany Purchase order and Sales order)which i can set for the follwoing scenarios. I have looked on the forms and searched alot but not able to a single solution to solve both the pupose. if one scenario works the other doesnt. Please advise.
I have created the master data
Customer receiving--G001
Sales Org.--GXIN
Distr. Channel- 01
Division - 00
Company code receiving - G1
customer supplying- V001
company code for supplying- V1
2 different scenarios
1- Intercompany Purchase order in which a Customer receiving- G001, gets stock replenishment NB purchase order from supplying company V1- GI and GR of stock is done. Biling document for customer receiving G001 is created. But now I need a way to do the opposite side posting at the supplying customer -V001-- this I do using an Idoc which creates a Invoice receipt for creditor(supplying customer) V001.
2. Sales order-- A customer X001 of company code G1 buys stock from the company code V1. the customer G001 of company code G1 bills the customer X001, but the intercompany billing doc/ invoice is created for the customer G001 by company code V1. then now i want an automatic account posting to be created at the supplying customer V001 via idoc.
Can this be achivable via Idoc with automatic account postings.
Please let me know if it doesnt make sense. thanks to all in advance
cheers
Jasmeet

Hi all,
For the Sales order and automatic posting we have created an output type ZR4N- this is creating a batch input session which can be triggered to be processed autmatically.
For the intercompany Purchase order -from Invoice we are creating a different output RD04 (sap standard) which creates invoice receipt at the vendor side.
Rest of the settings are defined using SAP standard functionality within transaction OBCA, OBCB, OBCC, OBCD,OBCE
thanks for viwing the post
Cheers
Jasmeet

Automatic Account Determination for Sale order related PO

Dear all,
I am creating a purchase order with Account Assignment Category "C" (Sale Order). The system asks for GL Account which I don't want the user to enter. I would like to configure the GL account through automatic account determination. In which Trans Key/General Modifier I have to assign GL Account for the Purchase order with Account assignment "C"
Please suggest,
Regards,
S.Suresh

Hi Suresh,
Asssign one Account modifier For example ZBR in OBYC for GBB key
with valuation class and your default account
Then go to SPRO >purchasing>A/C assignment select C go to details and put
Your valuation modifier as ZBR in that a/c assignment details
So when you put a/c assignment as C system will auto default your G/L
ACCORDING TO VALUATION CLASS IN OBYC
Hope this will resolve your issue
BR
Diwakar
reward if useful

OBYC changes in automatic account assignment

Hi
I've a question.
We have configured automatic account assignment under BSX in OBYC with say, GL1.
Now we observed that, it has changed to GL2 by mistake. Now we need to set it back to GL1.
Will system automatically assign all the transactions to the changed GL (i.e from GL2 to GL1), meaning the old transactions as well, or we need to pass a JV for the rectification of the balances to the correct GL.
Please advise.

What must be the rectifying action for this?? Since this is a huge balance and Finance dept is not allowing to pass a JV with such a huge balance for audit reasons.
Plz suggest from MM side what can be done coz reversing and re-posting the whole thing is not possible since its time consuming activity.

Transaction Code to see all automatic account determination GL

Hi All
Please let me know the Transaction Code to see all automatic account determination GL like FI -GL integration with other modules/ submodules like AA,MM,SD, FM,CM etc. I tried with FBKP, but it is not giving all.
Regards
Sekhar

Hi
OMWB will give you account determination by parameter selections combinations viz,
1) plant / material / movement types
2) by company code / valuation area
3) the account determination in OBYC can also be seen here.
Thanks
kamala

How the maintain automatic account postings?

Hi,
I was asked to change the account assignment from account 105000 to account 106000. This is only to occur for a certain movement type and material type/valuation class.
How can I make sure of this? How do I change the acc. cat ref. or value string for this?
Thanks a lot!!
Renate

Hi
Use T.code OBYC for automatic account assignmnets for MM-FI.
To understand the logic follow the below screens:
OMWN--Movement types are linked to Transaction keys via valuation string
OMWD--This T.code groups together valuation areas(combi of plant,co.cd,chart of accounts)
OBYC--Automatic account assignments based on Transaction key like GBB,WRX etc.
Assign points if useful
Regards
Aravind

FBCJ accept post automatically account

Hello friends,
i m facing a problem.
FBCJ accepts GL having post automatically field is active means manual posting is restricted for such GL then FBCJ it gets posted.
What should be the reasong for it?
How can i restrict it that in FBCJ GL with post automatically should not be taken?
Kindly provide ur valuable suggestion at the earliest.
being cash transaction it is important issue.
Regards,
Greeshma
Edited by: greeshma udawat on Oct 23, 2008 2:32 PM

hi,
Thanks for reply
i am not talking about cash GL account.
let me give u example
GL account 111111 cannot be posted manually.
now in FBCJ,under business transcation "expense" when i
select this GL account,the entry gets posted.
i.e
GL 111111 a/c Dr ( how can this be debited when it is post automatically account ????? )
Cash Account Cr
My query is that how to restrict entry of other GL account (Post automaticaaly Account ) in FBCJ
Regards,
Greeshma
guys help me out.
plsss
Edited by: greeshma udawat on Oct 24, 2008 6:25 AM

About automatic account assignment

hi,
in one interview i faced a question ie: what are the sequencial steps involved in configur automatic account assignment?
can i get a answer from seniors

Configure automatic postings
In this step, you enter the system settings for Inventory Management and
    Invoice Verification transactions for automatic postings to G/L accounts.
You can then check your settings using a simulation function.
Under Further information there is a list of transactions in Materials
    Management and their definitions.
What are automatic postings?
Postings are made to G/L accounts automatically in the case of Invoice
    Verification and Inventory Management transactions relevant to Financial
    and Cost Accounting.
Example:
Posting lines are created in the following accounts in the case of a
    goods issue for a cost center:
    o Stock account
    o Consumption account
How does the system find the relevant accounts?
When entering the goods movement, the user does not have to enter a G/L
    account, since the R/3 System automatically finds the accounts to which
    postings are to be made using the following data:
    o Chart of accounts of the company code
       If the user enters a company code or a plant when entering a
       transaction, the R/3 System determines the chart of accounts which is
       valid for the company code.
       You must define the automatic account determination individually for
       each chart of accounts.
    o Valuation grouping code of the valuation area
       If the automatic account determination within a chart of accounts is
       to run differently for certain company codes or plants (valuation
       areas), assign different valuation grouping codes to these valuation
       areas.
You must define the automatic account determination individually for
       every valuation grouping code within a chart of accounts. It applies
       to all valuation areas which are assigned to this valuation grouping
       code.
If the user enters a company code or a plant when entering a
       transaction, the system determines the valuation area and the
       valuation grouping code.
    o Transaction/event key (internal processing key)
       Posting transactions are predefined for those inventory management and
       invoice verification transactions relevant to accounting. Posting
       records, which are generalized in the value string, are assigned to
       each relevant movement type in inventory management and each
       transaction in invoice verification. These contain keys for the
       relevant posting transaction (for example, inventory posting and
Transaction/event key (internal processing key)
Posting transactions are predefined for those inventory management and
invoice verification transactions relevant to accounting. Posting
records, which are generalized in the value string, are assigned to
each relevant movement type in inventory management and each
transaction in invoice verification. These contain keys for the
relevant posting transaction (for example, inventory posting and
consumption posting) instead of actual G/L account numbers.
You do not have to define these transaction keys, they are determined
automatically from the transaction (invoice verification) or the
movement type (inventory management). All you have to do is assign the
relevant G/L account to each posting transaction.
Account grouping (only for offsetting entries, consignment
liabilities, and price differences)
Since the posting transaction "Offsetting entry for inventory posting"
is used for different transactions (for example, goods issue,
scrapping, physical inventory), which are assigned to different
accounts (for example, consumption account, scrapping, expense/income
from inventory differences), it is necessary to divide the posting
transaction according to a further key: account grouping code.
An account grouping is assigned to each movement type in inventory
management which uses the posting transaction "Offsetting entry for
inventory posting".
Under the posting transaction "Offsetting entry for inventory
posting", you must assign G/L accounts for every account grouping,
that is, assign G/L accounts.
If you wish to post price differences to different price difference
accounts in the case of goods receipts for purchase orders, goods
receipts for orders, or other movements, you can define different
account grouping codes for the transaction key.
Using the account grouping, you can also have different accounts for
consignment liabilities and pipeline liabilities.
Valuation class of material or (in case of split valuation) the
valuation type
The valuation class allows you to define automatic account
determination that is dependent on the material. for example: you post
a goods receipt of a raw material to a different stock account than if
the goods receipt were for trading goods, even though the user enters
the same transaction for both materials.
You can achieve this by assigning different valuation classes to the
materials and by assigning different G/L accounts to the posting
transaction for every valuation class.
If you do not want to differentiate according to valuation classes you
do not have to maintain a valuation class for a transaction.
   Before you maintain automatic postings, you must obtain the following
   information:
1. Valuation level (plant or company code)
      Establish whether the materials are valuated at plant or at company
      code level
When valuation is at plant level, the valuation area corresponds to a
      plant.
When valuation is at company code level, the valuation area
      corresponds to a company code.
      Define valuation level
2. Chart of accounts and valuation grouping code per valuation area
      Find out whether the valuation grouping code is active.
      Activate split valuation
      If it is not active, determine the chart of accounts assigned to each
      valuation area (via the company code).
      If it is active, determine the chart of accounts and the valuation
      grouping code assigned to each valuation area.
      Group valuation areas
You must define a separate account determination process for chart of
      accounts and each valuation grouping code.
3. Valuation class per material type
      If you wish to differentiate the account determination process for
      specific transactions according to valuation classes, find out which
      valuation classes are possible for each material type.
      Define valuation classes
4. Account grouping for offsetting entries to stock accounts
      Under Define account grouping for movement types, determine for which
      movement types an account grouping is defined for the
      transaction/event keys GGB (offsetting entry to stock posting), KON
      (consignment liabilities) and PRD (price differences).
Default settings
G/L account assignments for the charts of accounts INT and the valuation
   grouping code 0001 are SAP standard.

Dfrnce in automatic account determination

What is the dfrnce b/w automatic account determination with wizard and automatic account determination without wizard ?

Welcome to the MM Account Determination Wizard!
This wizard will ask you a series of questions which will help you to configure the MM account assignment environment.
What is account determination?
When you enter a goods movement, you do not have to enter G/L accounts since ERP automatically determines the correct accounts. ERP does this by using account information that you set up in advance in an area of Customizing known as "account determination". This wizard takes you through this pre-configuration process.
What you need to know before you start:
Depending on how you answer the questions on the following screens, the wizard may need to delete previous account configuration data. A warning will be given prior to any such deletions. No actual changes are carried out until the very end of the wizard session.
The internal processing (transaction/event) key UMB is only shown for the price change transaction.
Purchase account management postings are only shown in the case of goods receipts referencing purchase orders and in invoice verification.
Accounts, cost centers, cost elements and other FI/CO data must be configured in advance.
The wizard always sets the valuation class rule to "on" for the internal processing (transaction/event) keys AKO, AUM, BSV, BSX, EIN, EKG, FRL, GBB, and PRD.
The wizard always sets the valuation grouping code to active.
Restrictions:
The wizard does not recognize non-standard account modifiers.
Material Ledger postings are not taken into account.
Account Determination Without Wizard
In this step, you can make the settings for account determination in Inventory Management and Invoice Verification.
Account determination without the wizard enables you to make a more complex configuration than account determination with the wizard, but requires that you are already familiar with the principle of automatic account determination in the ERP System.
You can configure account determination with the wizard in the first instance, for example. Then, if the wizard does not meet your company's account determination requirements, you can work without it.
Detailed documentation on account determination is contained in the step Configure automatic postings.
Hope this will help.....

Automatic account detrmination

hi sap gurus
what are the standard transaction keys in automatic account determination in obyc
for revenue frm price difference
and expense from price difference
also income form price difference
and expense from price difference
alsu tell posting key to be used for both
handsome points will be given . its urgent

Hi
This is depends upon transaction that causes price differences.
Examples with transaction keys:--
1.Expense/revenue from consumption of consignment material (AKO):-
This transaction is used in Inventory Management in the case of withdrawals from consignment stock or when consignment stock is transferred to own stock if the material is subject to standard price control and the consignment price differs from the standard price.
2.Expenditure/income from transfer posting (AUM):-
This transaction is used for transfer postings from one material to another if the complete value of the issuing material cannot be posted to the value of the receiving material. This applies both to materials with standard price control and to materials with moving average price control. Price differences can arise for materials with moving average price if stock levels are negative and the stock value becomes unrealistic as a result of the posting. Transaction AUM can be used irrespective of whether the transfer posting involves a transfer between plants. The expenditure/income is added to the receiving material.
3.Price differences (PRD) :-
Price differences arise for materials valuated at standard price in the case of all movements and invoices with a value that differs from the standard price. Examples: goods receipts against purchase orders (if the PO price differs from the standard pricedardpreis), goods issues in respect of which an external amount is entered, invoices (if the invoice price differs from the PO price and the standard price). Price differences can also arise in the case of materials with moving average price if there is not enough stock to cover the invoiced quantity. In the case of goods movements in the negative range, the moving average price is not changed. Instead, any price differences arising are posted to a price difference account. Depending on the settings for the posting rules for transaction/event key PRD, it is possible to work with or without account modification. If you use account modification, the following modifications are available in the standard system: - None for goods and invoice receipts against purchase orders - PRF for goods receipts against production orders and order settlement - PRA for goods issues and other movements - PRU for transfer postings (price differences in the case of external amounts)
4.Revenue/expense from revaluation (UMB) :-
This transaction/event key is used both in Inventory Management and in Invoice Verification if the standard price of a material has been changed and a movement or an invoice is posted to the previous period (at the previous price).
regards
rb

Account reconciliation Message MQ555

Hi!
We have problems with the account reconciliation for one fixed assets account. The problem is that in 2005, we change the depreciation key in december because it was wrong. So, the planned depreciation is different form the accounting depreciation. In tabla ANLC, the fields ANLC-KNAFA and ANLC-NAFAP are different.
We have just now realized.
So, the problem is that when change the fiscal year, in 2006, the accumulated ordinay depreciation (ANLC-KNAFA) is the value we had in 2005 in field planned depreciation and the correct one should be the real depreciation.
Now, we run the report ABST2 and it appears the error MQ555.
I have checked the note 104567 but I cannot find the solution.
Thanks in advance.
Best regards,
Iné

HI,
Please pay attention again onnotes 104567 and 543151. Especially note 104567 paragraph 3 describes the procedure for analyzing the cause for error message MQ555.
Please assign points if it useful.
Regards
Ravinagh Boni

Automate Account Reconciliations

Similar Messages

Maybe you are looking for