Reconciliation - mont end

hi,
How do we do reconcilisation for clearing account at month end?
Eg: GR/IR - how do we manintan open items at month end
please explan me

KP,
I would leave that to business - Open GR/IR items indicates that we received the goods, but we received no invoice for that.
Hope that helps..
Thanks,
Nandita

Similar Messages

Bank Reconciliation Statement-End User Document

Hi,
Does some body have an End User Document for uploading Bank Reconciliation Statement, both Manual and Automatic ?
If yes please post a link in this thread.
Regards,
Swapnil

http://help.sap.com/saphelp_erp2005/helpdata/en/43/0bd58143de11d1896f0000e8322d00/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/43/0bd58143de11d1896f0000e8322d00/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/43/0bd58143de11d1896f0000e8322d00/frameset.htm
regards
S

Difference in AR Reconciliation Report

My submitted AR Reconciliation Report has a different of $8,000.00 and the amount was found from a unapplied receipt. How could I trace the root cause of this different amount?? Aging 4-Buckets report??
The amount in bule is the +/- amount from its own column
      Calculated Total for the Period                                             200,008,000.00
      Ending Balance as of xx-SEP-20xx                                     200,000,000.00
      Difference                                                                              ------------------------
                                                                                                              8,000.00
                                                                                                   ========================
Calculation:
Total Activity in a period is calculated as follows:
Transaction Register for the Period
(-)Applied Receipts Register for the Period
(-)Un-Applied Receipts Register for the Period
(+)Adjustments Register for the Period
(-)Invoice Exceptions for the Period
(+)Rounding Differences for the Period (*)
(+)Credit Memo gain/loss for the Period(*)
= 200,008,000.00

Hi ,
Please see if the following notes help you:
ARXRECON - How To Resolve AR Reconcilation Report Difference . (Doc ID 246804.1)
AR Reconciliation Report Ending Balance Does Not Match ATB 7 Buckets Or ATB 4 Buckets (Doc ID 402199.1)
11i: Differences On The AR Reconciliation Report In Case On Account Credit Memo Refunds (Doc ID 549648.1)
Thanks &
Best Regards,

Transformation of Data During User Reconciliation

Hi all,
I'd want transform data during user reconciliation from a trusted source SAP HR.
In my case I have to transform the userid coming from SAP to generated a custom OIM User Login attribute.
As described in the "Connector Guide for SAP Employee Reconciliation", I wrote a java class that implements the Transformation interface,
the method "transform" has the code to generate the userid; then I created a jar, unploaded it, and finally I changed the following lookup definitions as described in the doc guide:
- Lookup.SAP.HRMS.Configuration
COD KEY = Use Transformation For Recon
DECODE = YES
- Lookup.SAP.HRMS.ReconTransformation
COD KEY = User ID
DECODE KEY = com.mycompany.custom.ReconUserLoginGenerator
When the reconciliation process ends the OIM user login is created but it isn't trasformed; in the log I did't see any excpetion of my class and it seems that no trigger has been triggered for the class.
Someone has suggestion about the Transformation data during user recon? I forgot something in order to transform data?
Thanks a lot,
Ettore

Hi Martin,
I uploaded the jar using the "Upload" utility as described in the doc, (the version of OIM system is 11g).
Ettore

Automatic Price Change at the time of Confirmation of PP order

Dear Sir,
When Production Order is being confirmed (T Code COR6), the
price of the BOM material (Finished Goods with standatd price)is getting
changed. PR document type FI document is created and UMB key
is getting the hit with a very minimum amount. (0.01 Indian Rupees) . This is not happening regularly. But suddenly in one confirmation it is happening. The process order are created in
the system for 1 month say Start Date 01.01.2009 End Date
31.01.2009
This is happeing when confirmation is made in first day of next month
for previous month i.e. for process order of January 2009 (Start
Date 01.01.2009 End Date 31.01.2009 ) confirmation is made on the
01.02.2009. Document date is 01.02.2009, posting date is
31.01.2009.
The PR (Price Change) docuement is getting generated on 01.02.2009 with posting date on 01.02.2009.
At the mont end there is no manual Price Change thru MR21 transaction.
Regards,
Partha Pratim Bhar

Hi,
You need to check that material Standard Cost estimation has run or not for the next period. Normally Standard cost run can be run every period or once in 3 periods or once in a year. Based on this the standard cost estimate will update the material prices in the costing 2 view if any changes in the existing price. May be his could be the reason you may face the problem.
Regards,
V. Suresh

Deferred Tax - Incorrect Profit center at the time of Transfer

Hi,
We are on ECC 6.0 ehp4. We have created the service tax codes with target service tax codes & every month end we run standard sap program S_AC0_52000644 to transfer the service tax from receivable to availed account. Following is the issue
Invoice Posted with following entry (In GL view)
SRIR A/c Dr..............                                          Profit center 5001
Service Tax Recevble A/c Dr...............                  Profit center 5001
R/off A/c Cr                                                         Profit center 9001
Tds A/c cr                                                           Profit center 5001
domestic vendor A/c cr                                         Profit center 5001
domestic vendor A/c cr                                         Profit center 9001
This entry was reversed with transaction code MR8M & exact reversal entry was posted. Now this reversal entry and the above original entry was cleared, after that when in the mont end I ran the service tax transfer report below is the scenario
Service Tax Receivable for Original Invoice entry got transfered correctly to profit center 5001. Service tax receivable for reversed entry also got transfere correctly but the entire amount of service tax was transfered to profit center 9001 instead of 5001, can any one advise on system behaviour. Now in this my issue is, for reversal entery, the service tax got credited to profit center 5001, but when it got transfered system credited to profit cetner 9001.
Please advise
Shailesh

Hi,
Please consider notes :
1469580
1073837
BR,
Raquel

Problem with a fusion of two companies

Hi,
Maybe somebody can help me with my problem with implementing FICO modules in two companies which are soon going to become one company. The fusion will probably take place on 1st january, but it can be posponed as well.
Everything is prepared to run the common mont-end closing procedures and common planning/budgeting for both companies from the 1st january.
However, there is a great risk, that the fusion will be delayed.
In that case I suppose it would be better to enter one separate budget for the leading company and upload the budget of the other company after the fusion takes place. These actions have influence on calculating the manufacturing cost of products. It will certainly be different before and after the fusion.
Maybe you can advise me on this subject, wheter I should make a common budget for both companies no matter the date of fusion or make a buget in SAP only for the leading company and upload the budget of the other company after the fusion, and then recalculate the manufacturing cost of products.
Best wishes,
karol

Hi,
As of now the time frame is more than 7 months to the go live date of Jan 01st 2008. Definitely, you would have drawn up a project plan for executing this project.
In my view if the project is on schedule, at this point of time we can still consider making a consolidated budget after fusion. And the project schedule should be monitored closely as the deadline is coming closer. However, if by Oct 01st 2007 the project is not on schedule and there is a likelihood of delay / postponement, the second option of having a separate budget for each company code can be considered.
A contingency / back up should be prepared and this should be implemented if the original plan is not working out.
Thanks
Murali.

Report Painter Output in Local Currency

Dear Experts,
I have 2 Co Code 1 with Currency INR and another one with USD Controlling area currency is INR for both.
I want to run a Plan VS Actual report in INR for USD Co Code so when I run the report the actuals values appear in INR correctly but the plan figures comes in USD since I have uploaded the same in USD but it does not gets converted in INR.
Is their anyway through I can get plan figs in INR.Please advice
Regards,

Hi Use the Target currency currency translation option. And if you need a mont end exchange rate to be applied create a New exchange rate type. You will be able to run the currency conversion for a specifc data( Ie Pla or actual)
rgds
Vinod S

Performance Problem-Getting huge Dump

Hi Guruz,
I am facing performanece issue in my Production Server.From the last mont end I am getting a lot of TIME_OUT dump though the number of users and processing are quite same.
The profile parameter "rdisp/max_wprun_time" is not set so it is taking its default value of 600 secs.Mine is <b>4.6C with Oracle 8i</b>.
Now my question is that is this parameter "rdisp/max_wprun_time" is a dynamic one means can any change of value to this parameter can take effect with restarting the Instance? I am having three instances here.
Please reply asap.
Regards,
Mofizur

Yes this parameter is dynamically switchable, means you can change values without a restart. But once you restart the server it will then back to the default.
Normally 600 sec will give you many TIME_OUT dumps because most of the cases manuy of the customer reports will take more than 10 min to execute.
You may need to look at the programs that causes this dump and analyze it to see what is going wrong. ST03N analysis can be a starting point.

Is it possible to execute a code in my program based on a click event in SAP B1?

Hi!, everybody
I may be doing some wishful dreaming, but I ask my question nevertheless. We never know...
My pictures are self explanatory, but I explain my requirement below:
I have a grid which is populated by a query. Briefly, it is a list of Invoices to be reconciled.
The user selects the invoice to be reconciled by selecting the row. Then he presses the Reconcile? button.
This is what the Reconcile? button does:
         It colors the background of the selected row Red - just to indicate all rows which have already been selected (because reconciliation has to be
         done one row at a time).
         Then it opens the Internal Reconciliation screen in SAP B1 to allow the user to reconcile his items.
Ideally, I should color the selected row Red only after the user has done his reconciliation.
         If he decides not to proceed, he can cancel, and the selected row will not be colored red.
         But I don't know how to do this. (Is it possible???). So I color the selected row assuming the user will proceed with the recon.
Can anyone tell me if I can fire my program (color the background red) only if the user clicks the reconcile and OK buttons in SAP B1?
Thanks
Leon Lai

Hi Pedro,
Your VB.NET code finally runs without syntax error.
However, I still have a problem. The program does not behave as intended.
See the attached picture.
And my code is below.
I am sure you are very near the correct solution.
So, please tell me what is not working in my code.
I notice you have removed the lines concerning Handler. Is this the problem?
My objective is to display the Reconciliation Completed MsgBox (or row coloring in the real project) if the Reconciliation is successful.
Best Regards,
Leon
Option Strict Off
Option Explicit On
Module SubMain
    Friend WithEvents Action As ABC = New ABC()
    Public Sub Main()
     Action.Reconcile()
    End Sub
    Private Sub OnReconcileComplete(ByVal sender As Object, ByVal e As EventArgs) Handles Action.ReconcileComplete
        MsgBox("Reconciliation completed")
    End Sub
End Module
Dim BPForm2 As SAPbouiCOM.Form
Public Event ReconcileComplete As EventHandler
    Private Sub RaiseReconcileComplete(ByVal e As EventArgs)
        RaiseEvent ReconcileComplete(Me, e)
        '//Dim Handler As EventHandler = Me.ReconcileComplete
        '// If Not Handler Is Nothing Then
        '// Handler(Me, EventArgs.Empty)
        '// End If
    End Sub
    Public Sub Reconcile()
        SBO_Application.ActivateMenuItem("9459")
        '// 9459 = Modules -> Business Partners -> Internal Reconciliations
        BPForm2 = SBO_Application.Forms.ActiveForm
        Dim oCode As String
        oCode = "LV10010"
        Dim oBPCode As SAPbouiCOM.EditText = CType(BPForm2.Items.Item("120000008").Specific, SAPbouiCOM.EditText) ' 120000008 = Business Partner Field
        oBPCode.Value = oCode
        BPForm2.Items.Item("120000001").Click()
        RaiseReconcileComplete(New EventArgs())
    End Sub

Price Change at the time of confirmation of PP order

Dear Sir,
When Production Order is being confirmed (T Code COR6), the
price of the BOM material (Finished Goods with standatd price)is getting
changed. PR document type FI document is created and UMB key
is getting the hit with a very minimum amount. (0.01 Indian Rupees) . This is not happening regularly. But suddenly in one confirmation it is happening. The process order are created in
the system for 1 month say Start Date 01.01.2009 End Date
31.01.2009
This is happeing when confirmation is made in first day of next month
for previous month i.e. for process order of January 2009 (Start
Date 01.01.2009 End Date 31.01.2009 ) confirmation is made on the
01.02.2009. Document date is 01.02.2009, posting date is
31.01.2009.
The PR (Price Change) docuement is getting generated on 01.02.2009 with posting date on 01.02.2009.
At the mont end there is no manual Price Change thru MR21 transaction.
Regards,
Partha Pratim Bhar

Plz try with userexit
Customer specific enhancements when saving- CONFPP06
Confirmations: Actual Data Transfer - CONFPP07

Error 14081 - Conditional aggregates

Hi !
I'd like to create conditional aggregates in OBIEE.
This is my problem : I have a fact table, with an 'amount' column and a 'probability' column. I have to create measures that aggregate (sum) amounts only for a certain range of probability ('Other Opportunities : probability between 1 and 59, 'Strong Opportunities' : probability between 60 and 80, ...).
So, I made indicators with the expression builder, with this kind of expression, using case when :
CASE WHEN
SugarCRM."Affaires Faits".Probabilite > 0
AND SugarCRM."Affaires Faits".Probabilite < 60
THEN SUM(SugarCRM."Affaires Faits".Montant) END
Even though this expression raises no syntax error, this is the description error OBIEE gives me while checking consistency :
BUSINESS MODEL SugarCRM:
[14041] Error in measure definition for column Autres. Nested aggregate measure definitions are currently not supported.
Has someone created conditional aggregates ? Is there another way to make it ?
Thanks.
Cyril

One cannot use Case when for this. You need to use filter expressions for these. Use something like this
FILTER(SUM(SugarCRM."Affaires Faits".Montant) USING (SugarCRM."Affaires Faits".Probabilite > 0
AND SugarCRM."Affaires Faits".Probabilite < 60))
Thanks,
Venkat
http://oraclebizint.wordpress.com

Data Migration_LSMW

hi all,
need information on data migration and possible methods of LSMW
Thanks
Swapna

hi
Can a give a Search on the Topic "Data Migration" & "LSMW" in the forum for valuable information,
<b>Pls Do NOT Post UR Mail-Id, Lets all follow some Rules</b>
Data Migration Life Cycle
Overview : Data Migration Life Cycle
Data Migration
This document aims to outline the typical processes involved in a data migration.
Data migration is the moving and transforming of data from legacy to target database systems. This includes one to one and one to many mapping and movement of static and transactional data. Migration also relates to the physical extraction and transmission of data between legacy and target hardware platforms.
ISO 9001 / TickIT accredited
The fundamental aims of certification are quality achievement and improvement and the delivery of customer satisfaction.
The ISO and TickIT Standards are adhered to throughout all stages of the migration process.
     Customer Requirements
     Dependencies
     Analysis
     Iterations
     Data Cleanse
     Post Implementation
     Proposal
     Project Management
     Development
     Quality Assurance
     Implementation
Customer Requirements
The first stage is the contact from the customer asking us to tender for a data migration project. The invitation to tender will typically include the Scope /
Requirements and Business Rules:
     Legacy and Target - Databases / Hardware / Software
     Timeframes - Start and Finish
     Milestones
     Location
     Data Volumes
Dependencies
Environmental Dependencies
     Connectivity - remote or on-site
     Development and Testing Infrastructure - hardware, software, databases, applications and desktop configuration
Support Dependencies
     Training (legacy & target applications) - particularly for an in-house test team
     Business Analysts -provide expert knowledge on both legacy and target systems
     Operations - Hardware / Software / Database Analysts - facilitate system housekeeping when necessary
     Business Contacts
     User Acceptance Testers - chosen by the business
     Business Support for data cleanse
Data Dependencies
     Translation Tables - translates legacy parameters to target parameters
     Static Data / Parameters / Seed Data (target parameters)
     Business Rules - migration selection criteria (e.g. number of months history)
     Entity Relationship Diagrams / Transfer Dataset / Schemas (legacy & target)
     Sign Off / User Acceptance criteria - within agreed tolerance limits
     Data Dictionary
Analysis
Gap Analysis
Identifying where differences in the functionalities of the target system and legacy system mean that data may be left behind or alternatively generating default data for the new system where nothing comparable exists on legacy.
Liaison with the business is vital in this phase as mission critical data cannot be allowed to be left behind, it is usual to consult with the relevant business process leader or Subject Matter Expert (SME). Often it is the case that this process ends up as a compromise between:
     Pulling the necessary data out of the legacy system to meet the new systems functionality
     Pushing certain data into the new system from legacy to enable the continuity of certain ad hoc or custom in-house processes to continue.
Data mapping
This is the process of mapping data from the legacy to target database schemas taking into account any reformatting needed. This would normally include the derivation of translation tables used to transform parametric data. It may be the case at this point that the seed data, or static data, for the new system needs generating and here again tight integration and consultation with the business is a must.
Translation Tables
Mapping Legacy Parameters to Target Parameters
Specifications
These designs are produced to enable the developer to create the Extract, Transform and Load (ETL) modules. The output from the gap analysis and data mapping are used to drive the design process. Any constraints imposed by platforms, operating systems, programming languages, timescales etc should be referenced at this stage, as should any dependencies that this module will have on other such modules in the migration as a whole; failure to do this may result in the specifications being flawed.
There are generally two forms of migration specification: Functional (e.g. Premise migration strategy) Detailed Design (e.g. Premise data mapping document)
Built into the migration process at the specification level are steps to reconcile the migrated data at predetermined points during the migration. These checks verify that no data has been lost or gained during each step of an iteration and enable any anomalies to be spotted early and their cause ascertained with minimal loss of time.
Usually written independently from the migration, the specifications for the reconciliation programs used to validate the end-to-end migration process are designed once the target data has been mapped and is more or less static. These routines count like-for-like entities on the legacy system and target system and ensure that the correct volumes of data from legacy have migrated successfully to the target and thus build business confidence.
Iterations
These are the execution of the migration process, which may or may not include new cuts of legacy data.
These facilitate:
     Collation of migration process timings (extraction, transmission, transformation and load).
     The refinement of the migration code i.e. increase data volume and decrease exceptions through:
     Continual identification of data cleanse issues
     Confirmation of parameter settings and parameter translations
     Identification of any migration merge issues
     Reconciliation
From our experience the majority of the data will conform to the migration rules and as such take a minimal effort to migrate ("80/20 rule"). The remaining data, however, is often highly complex with many anomalies and deviations and so will take up the majority of the development time.
Data Cuts
     Extracts of data taken from the legacy and target systems. This can be a complex task where the migration is from multiple legacy systems and it is important that the data is synchronised across all systems at the time the cuts are taken (e.g. end of day processes complete).
     Subsets / selective cuts - Depending upon business rules and migration strategy the extracted data may need to be split before transfer.
Freeze
Prior to any iteration, Parameters, Translation Tables and Code should be frozen to provide a stable platform for the iteration.
Data Cleanse
This activity is required to ensure that legacy system data conforms to the rules of data migration. The activities include manual or automatic updates to legacy data. This is an ongoing activity, as while the legacy systems are active there is the potential to reintroduce data cleanse issues.
Identified by
     Data Mapping
     Eyeballing
     Reconciliation
     File Integrities
Common Areas
     Address Formats
     Titles (e.g. mrs, Mrs, MRS, first name)
     Invalid characters
     Duplicate Data
     Free Format to parameter field
Cleansing Strategy
     Legacy - Pre Migration
     During migration (not advised as this makes reconciliation very difficult)
     Target - Post Migration (either manual or via data fix)
     Ad Hoc Reporting - Ongoing
Post Implementation
Support
For an agreed period after implementation certain key members of the migration team will be available to the business to support them in the first stages of using the new system. Typically this will involve analysis of any irregularities that may have arisen through dirty data or otherwise and where necessary writing data fixes for them.
Post Implementation fixes
Post Implementation Data Fixes are programs that are executed post migration to fix data that was either migrated in an 'unclean' state or migrated with known errors. These will typically take the form of SQL scripts.
Proposal
This is a response to the invitation to tender, which comprises the following:
Migration Strategy
     Migration development models are based on an iterative approach.
     Multiple Legacy / Targets - any migration may transform data from one or    more legacy databases to one or more targets
     Scope - Redwood definition / understanding of customer requirements, inclusions and exclusions
The data may be migrated in several ways, depending on data volumes and timescales:
     All at once (big bang)
     In logical blocks (chunking, e.g. by franchise)
     Pilot - A pre-test or trial run for the purpose of proving the migration process, live applications and business processes before implementing on a larger scale.
     Catch Up - To minimise downtime only business critical data is migrated, leaving historical data to be migrated at a later stage.
     Post Migration / Parallel Runs - Both pre and post migration systems remain active and are compared after a period of time to ensure the new systems are working as expected.
Milestones can include:
     Completion of specifications / mappings
     Successful 1st iteration
     Completion of an agreed number of iterations
     Delivery to User Acceptance Testing team
     Successful Dress Rehearsal
     Go Live
Roles and Responsibilities
Data Migration Project Manager/Team Lead is responsible for:
     Redwood Systems Limited project management
     Change Control
     Solution Design
     Quality
     Reporting
     Issues Management
Data Migration Analyst is responsible for:
     Gap Analysis
     Data Analysis & Mapping
     Data migration program specifications
     Extraction software design
     Exception reporting software design
Data Migration Developers are responsible for:
     Migration
     Integrity
     Reconciliation (note these are independently developed)
     Migration Execution and Control
Testers/Quality Assurance team is responsible for:
     Test approach
     Test scripts
     Test cases
     Integrity software design
     Reconciliation software design
OtherRoles:
     Operational and Database Administration support for source/target systems.
     Parameter Definition and Parameter Translation team
     Legacy system Business Analysts
     Target system Business Analysts
     Data Cleansing Team
     Testing Team
Project Management
Project Plan
     Milestones and Timescales
     Resources
     Individual Roles and Responsibilities
     Contingency
Communication
It is important to have good communication channels with the project manager and business analysts. Important considerations include the need to agree the location, method and format for regular meetings/contact to discuss progress, resources and communicate any problems or incidents, which may impact the ability of others to perform their duty. These could take the form of weekly conference calls, progress reports or attending on site
project meetings.
Change Control
     Scope Change Requests - a stringent change control mechanism needs to be in place to handle any deviations and creeping scope from the original project requirements.
     Version Control - all documents and code shall be version controlled.
Issue Management
     Internal issue management- as a result of Gap analysis, Data Mapping, Iterations Output (i.e. reconciliation and file integrity or as a result of eyeballing)
     External issue management - Load to Target problems and as a result of User Acceptance Testing
     Mechanism - examples:
     Test Director
     Bugzilla
     Excel
     Access
     TracNotes
Development
Extracts / Loads
     Depending on the migration strategy, extract routines shall be written to derive the legacy data required
     Transfer data from Legacy and/or Target to interim migration environment via FTP, Tape, CSV, D/B object copy, ODBC, API
     Transfer data from interim migration environment to target
Migration (transform)
There are a number of potential approaches to a Data Migration:
     Use a middleware tool (e.g. ETI, Powermart). This extracts data from the legacy system, manipulates it and pushes it to the target system. These "4th Generation" approaches are less flexible and often less efficient than bespoke coding, resulting in longer migrations and less control over the data migrated.
     The Data Migration processes are individually coded to be run on a source, an interim or target platform. The data is extracted from the legacy platform to the interim / target platform, where the code is used to manipulate the legacy data into the target system format. The great advantage of this approach is that it can encompass any migration manipulation that may be required in the most efficient, effective way and retain the utmost control. Where there is critical / sensitive data migrated this approach is desirable.
     Use a target system 'File Load Utility', if one exists. This usually requires the use of one of the above processes to populate a pre-defined Target Database. A load and validate facility will then push valid data to the target system.
     Use an application's data conversion/upgrade facility, where available.
Reconciliation
Independent end-to-end comparisons of data content to create the necessary level of business confidence
     Bespoke code is written to extract required total figures for each of the areas from the legacy, interim and target databases. These figures will be totalled and broken down into business areas and segments that are of relevant interest, so that they can be compared to each other. Where differences do occur, investigation will then instruct us to alter the migration code or if there are reasonable mitigating factors.
     Spreadsheets are created to report figures to all levels of management to verify that the process is working and build confidence in the process.
Referential File Integrities
Depending on the constraints of the interim/target database, data may be checked to ascertain and validate its quality. There may be certain categories of dirty data that should be disallowed e.g. duplicate data, null values, data that does not match to a parameter table or an incompatible combination of data in separate fields as proscribed by the analyst. Scripts are written that run automatically after each iteration of the migration. A report is then generated to itemise the non-compatible data.
Quality Assurance
Reconciliation
     Horizontal reconciliation (number on legacy = number on interim = number on target) and Vertical reconciliation (categorisation counts (i.e. Address counts by region = total addresses) and across systems).
     Figures at all stages (legacy, interim, target) to provide checkpoints.
File Integrities
Scripts that identify and report the following for each table:
     Referential Integrity - check values against target master and parameter files.
     Data Constraints
     Duplicate Data
Translation Table Validation
Run after new cut of data or new version of translation tables, two stages:
     Verifies that all legacy data accounted for in "From" translation
     Verifies that all "To" translations exist in target parameter data
Eyeballing
Comparison of legacy and target applications
     Scenario Testing -Legacy to target system verification that data has been migrated correctly for certain customers chosen by the business who's circumstances fall into categories (e.g. inclusion and exclusion Business Rule categories, data volumes etc.)
     Regression Testing - testing known problem areas
     Spot Testing - a random spot check on migrated data
     Independent Team - the eyeballing is generally carried out by a dedicated testing team rather than the migration team
UAT
This is the customer based User Acceptance Test of the migrated data which will form part of the Customer Signoff
Implementation
Freeze
A code and parameter freeze occurs in the run up to the dress rehearsal. Any problems post freeze are run as post freeze fixes.
Dress Rehearsal
Dress rehearsals are intended to mobilise the resources that will be required to support a cutover in the production environment. The primary aim of a dress rehearsal is to identify the risks and issues associated with the implementation plan. It will execute all the steps necessary to execute a successful 'go live' migration.
Through the execution of a dress rehearsal all the go live checkpoints will be properly managed and executed and if required, the appropriate escalation routes taken.
Go Live window (typical migration)
     Legacy system 'end of business day' closedown
     Legacy system data extractions
     Legacy system data transmissions
     Readiness checks
     Migration Execution
     Reconciliation
     Integrity checking
     Transfer load to Target
     User Acceptance testing
     Reconciliation
     Acceptance and GO Live
===================
LSMW: Refer to the links below, can get useful info (Screen Shots for various different methods of LSMW)
Step-By-Step Guide for LSMW using ALE/IDOC Method (Screen Shots)
http://www.****************/Tutorials/LSMW/IDocMethod/IDocMethod1.htm
Using Bapi in LSMW (Screen Shots)
http://www.****************/Tutorials/LSMW/BAPIinLSMW/BL1.htm
Uploading Material Master data using BAPI method in LSMW (Screen Shots)
http://www.****************/Tutorials/LSMW/MMBAPI/Page1.htm
Step-by-Step Guide for using LSMW to Update Customer Master Records(Screen Shots)
http://www.****************/Tutorials/LSMW/Recording/Recording.htm
Uploading Material master data using recording method of LSMW(Screen Shots)
http://www.****************/Tutorials/LSMW/MMRecording/Page1.htm
Step-by-Step Guide for using LSMW to Update Customer Master Records(Screen Shots) Batch Input method
Uploading Material master data using Direct input method
http://www.****************/Tutorials/LSMW/MMDIM/page1.htm
Steps to copy LSMW from one client to another
http://www.****************/Tutorials/LSMW/CopyLSMW/CL.htm
Modifying BAPI to fit custom requirements in LSMW
http://www.****************/Tutorials/LSMW/BAPIModify/Main.htm
Using Routines and exception handling in LSMW
http://www.****************/Tutorials/LSMW/Routines/Page1.htm
Reward if USeful
Thanx & regrads
Naren

Bank Reconciliation module

Hi,
How do i use bank reconciliation module? The 'ending balance', do i have to put in exactly the amount which i receive from my montly bank statement? And also the 'ending date', lets say i put it as at end of April (30.04.08), when i review back it will show me the whole list right from the beginning, (1st Jan - 30th April). If i want to see only within april'08, how would i do this?
Thank you, really2 need your help.
Thanks.
Rgds,
Harith

Good day Harith,
Unfortuately you cannot ONLY display transactions for April. All the open tansactions that have not been paid and reconciled with your bank statement will be there.It does not make sense to ONLY display ex for April, because a customer acan pay an invoice from December.
You must exactly put in the date and corresponding amount as it is on your bank statement. It is important,because these amount must match each other.
When done correctly, errors can be picked up easily, for example double postings.
Hope it helps
Regards
Carin

What r daily, weekly, montly and yearly jobs? FICO

What r daily, weekly, montly and yearly jobs? i faced this question in one interview what is the answer

Hi
Month end closing Activities
1. All the expenses including amortization, prepaid expenses, Preliminary expenses and accruals have been booked.
2. Complete Bank Reconciliation
3. Make sure that Sum of Inter company balances is Zero
4. Suspense Accounts should be cleared regularly.
5. Ensure that all documents related to MM & SD have been entered in system.
6. Ensure that all billing documents are released to accounting.
7. Calculate Overheads on all process Orders (CO43)
8. Technically complete all process orders, which are fully processed (CORM).
9. Calculate Variance (KKS1)à (Relevant only if Standard cost is calculated).
10. Settle all process orders, which are technically complete (CO88).
11. Close All settled Process Orders
12. Close MM period (Transaction Code: MMPV).
13. Carry out GR/IR clearing (F.13) transaction
14. Depreciation Run (AFAB) has been carried out for the month
15. Close FI Posting period after the month end closing activity is over.
Year end closing Activities:
1. Calculate production work in progress on process orders which are not technically complete.
2. Carry out Assessment cycle for Cost Centers.
3. All month end closing Activities should be carried out.
4. Carry Forward Balances to next year
a. copy Number ranges to next year (T.Code: OBH2)
b. Carry Forward GL balances to next year(T.Code: F.16)
c. Carry Forward Customer/vendor balances to next year(T.Code: F.07)
5. Close CO Posting Period : T.Code: OKP1
6. Close the year open next year periods by selecting the Posting Period Variant. (T.Code: OB52)
7. Change Fiscal Year For Assets - T.Code: AJRW
7. Year end Closing-- Asset Accounting--final for year end - T.Code: AJAB
8. To check which year is closed for asset accounting - OAAQ
please try to search the forum once before u post these kind of queries..
Assign points if helpful...
Sunoj

Reconciliation - mont end

Similar Messages

Maybe you are looking for