Migration of SAP FICO transaction's business area to new business area

Hi Expert,
The user would like to migrate the existing/historical transaction from business area 1000 to 1001.
We had perform configuration update, all the new transaction has reflected to new busines area (1001).  For historial data, how to proceed with the changes, we also consider for journal entry for the update.  But this is not applicable for some Recon a/c as it cannot perform direct posting.  Kindly advice how to proceed the changes. 
thanks.
rgds,
tee

Hi,
SAP provided one update / change programe for business area document line item wise , In my previous projects we come across the same situation , sorry to say , at present forgotten the programme name , you can search the programmes and get it .
Thanks,
klreddy

Similar Messages

  • Migrating the SAP-Scripts to smartforma which are related to Finance(FI)

    Hi,
    Do we can migrate the SAP-Scripts to Smartform which are related to Finance(FI) & those SAP-Scripts are called by a standard print program (RFFOUS_C)
    Urgent answer need please!!!
    Thanks,

    Hello,
    Yes you can migrate script to smartform  there are different ways to migrate.
    Use program SF_MIGRATE..
    to migrate from scripts to smartforms.
    Reward if helpful.
    Viswam.

  • Hi Experts confusion on migration  from "SAP Business One" to "SAP R/3"

    Hi All
    I am a certified SAP Business One Certified Solution consultant and working on SAP Business One for the past 2.5 yrs and done 4 implementations.
    I want to migrate to SAP R/3 and have confusion on weather to join Project Systems/Material Management for training and pursue my career in the same. I want to do the Online Certification for the same.
    I feel like Jack of ALL and Master on None after working on SAP Business One.
    Pls guide me on the possible R/3 career options after SAP Business One and weather my experience in SAP will be counted for my future SAP career.
    I am confused Pls help.

    Better get trained in area of domain experience and get SAP certified.
    Check also this links
    Career Advice: SAP Business One to R3 transition in Ottawa Canada
    SAP B1 or R/3...which one to select
    http://it.toolbox.com/blogs/sap-library/sap-business-one-vs-sap-r3-system-architecture-13952
    http://it.toolbox.com/blogs/sap-business-one/sap-business-one-training-isnt-that-the-same-as-r3-9066
    Contact nearest SAP education partner for getting trained.
    http://www.siemens.co.in/en/about_us/index/our_business_segments/information_and_communication/sisl_business_profile/education_training/general_faq.htm
    http://www.sap.com/asia/services/education/schedule/schedule_IN.htm

  • SAP T-Codes with Functiona Area, Business Process, Sub-Process wise details

    Hi Experts,
    I am Involved in GRC AC5.3 implementation Project. In this we need to work on complete Role-Redesign Process, which involves building of New Roles as per their requirement (Transaction used in past one Year). We find 3500 T-Codes, which are used by the client from past one year. We need to segregate the All the T-Codes into Functiona Area, Business Process, Sub-Process wise.
    *Is there any data source available on Complete information on SAP T-Codes with Functiona Area, Business Process, and Sub-Process wise details.
    Thank and Regards,
    Sathish...

    Hi Satish,
    As per my knowledge, Since the role design is more specific to any client there is no standard classification.
    However you can classify them taking leverage of sap provided rule set for RAR or Existing customized ruleset in your landscape, based on that you can start grouping the Tcodes  and start framing the roles.

  • Looking for SAP(FICO) trainer in the Bay Area

    A company in the bay area is looking for SAP(FICO) trainer who has command on configuration of the modules and min work ex of about 5 years.
    Please post your resumes to [email protected] or call at 408-512-8033 for more information.
    Regards
    Uma

    A company in the bay area is looking for SAP(FICO) trainer who has command on configuration of the modules and min work ex of about 5 years.
    Please post your resumes to [email protected] or call at 408-512-8033 for more information.
    Regards
    Uma

  • Business Process in SAP FICO.

    Hi guru,
    I need some example of business process for sap fico project. i want to learn more about business process.
    Thanks
    Chirag

    As per module in FICO, AR, AP,AA,GL there is already business process present in SAP database. As of now, many releases have been out in the net especially good sites. I am recommending you the following links, but before you go to FICO be sure that you have a good background in accounting.
    As you read that, You will need the glossary of terms to the words used in SAP FICO.
    visit this links. www.sapdocs.info
                          http://help.sap.com/bp_bblibrary/600/BBlibrary_start.htm

  • Why most of SAP Standard transactions are written in function pools

    Hi Forum Experts,
    Why most of SAP Standard transactions are written in function pools instead of a normal module pool program? ( In the case of Standard tcode function pools, it is a collection of a large number of funciton modules, includes for forms used by function modules, and screens. Why is it so? ).
    Quick response will be appriciated.
    Thanks in advance.
    Regards,
    Harikrishna Indugu.

    because these functino pools contains so many function mudules and these function modules are used in other transactions also...
    thats why....
    reward points if useful....

  • SAP Standard Transactions are not  Available

    Hi all,
    I have one issue that we want to start our project system but some SAP Standard Transactions are not available when i check that Transaction its showing "DOES NOT EXIST". I have then Checked Program name of that same SAP Transaction code in SE38.. But there also it gives "program does not exist" .
    Path is :SAP Menu ->Information Systems ->Project system ->Financials -> Costs ->Plan-based ->By Cost Element ->---Few Tcodes in this
    I want to find out all Inactive Reports in Project System from Project Information system and then i want to make usefull that reports for client.
    but i dont know the reason why this is not available..?and How can be made these all available.
    Thanks.

    analyse table t800
    A.

  • SAP EH&S 4.6C Migration to SAP ECC6

    Hi All,
    We are having separate SAP R/3 instance for EH&S module (4.6C system). The transactions system is SAP R/3 4.7 system and is due for ECC6 upgrade. Just want to know
    1.     Has anything changed in EHS module from 4.7 to ECC6. If yes, what?
    2.     if we migrate the EH&S functionality from the separate instance for EHS to transactional system in ECC6 / 4.7 R/3  system - will it get affected.
    3.     What will be the best time to do the migration of EHS data to transactional system (before or after upgrade). We are using specifications, active phrase libraries, reports, report templates and report generation variants and WWI server for MSDS.
    Request your help. Thanks
    PS: Even partial answers will also help a lot.
    Best Regards,
    Vithal

    Hi,
    Please visit the following links:
    http://service.sap.com/erp
    http://solutionbrowser.erp.sap.fmpmedia.com/ (Functional perspective)
    /people/thomas.mann2/blog/2006/08/22/sap-upgrade-conflicts-1
    http://service.sap.com/instguides > mySAP Business Suite Applications > mySAP ERP > mySAP ERP 2005 > Upgrade
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
    For Functionality Differences, refer to the below site u2013
    http://solutionbrowser.erp.sap.fmpmedia.com/
    After opening the site, please select the Source Release Version which is 4.6. Then Select the Target Release Version which is "mySAP ERP 2005" or ECC 6.0
    Select the Solution Area like Financials, Human Capital Management, Sales....
    Select module like MM, PP, SD, QM.....
    Click on Search
    Then it displays the Release Version and the Delta Functionality, which can be downloaded to a word document if required. Also check the release notes of ECC 6.0 in service.sap.com.
    Hope this helps some extent.
    regards,
    mahesh.

  • Migration to SAP

    Hello Experts,
    We have a Non SAP system as well as a SAP system. For a particular Co Cd, we enter transactions at both the Co Cds - Now the mgmt has decided to end up with the Non SAP system as it's too much of maintainence.
    As of now, this is how it works - PO's are entered in both the systems and at the end of the month, data is transferred from SAP to Non-SAP system and then the payment program is run in Non-SAP system. After the run, there's no feed back to SAP - so all the PO's remain unpaid in SAP even after they are paid in real ( through infinium)- However for reporting purposes in SAP, we have another Co Cd in SAP, which reconciles with the Non-SAP system.
    So what are the possible issues/concerns you would think/suggest for the transition.
    All answers would be duly rewarded with points.
    Thanks,
    Nan

    Hi,
    It is good to note that Non SAP system is being given up. Based on the information provided by you, there is lot of duplication involved as of now, as the same data is being captured in two systems either through an interface or manually. Basically, now the project is migrating from a legacy non-SAP system to SAP for one company code.
    The steps involved in this process will be as under:
    1. Determine and define the Organization structure of the Company code.
    2. Identify all the Business Processes of the Company Code.
    3. Configure the Business Process which is not there as of now in SAP system.
    4. Extend GL Accounts to new Company code, assuming same chart of accounts being used.
    5. Determine currencies / fiscal year to be adopted (if it is different).
    6. Decide whether to attach the new Company code to the existing Controlling Area or not.
    7. Once the Business process mapping is completed, data conversion needs to be done. All the GL Balances / Customer and Vendor open items, Asset Masters and Asset values, O pen Purchase Orders and Open Sales Orders are to be brought into SAP.
    8. Once data conversion is completed - reconcile the balances with legacy system.
    Thanks
    Murali.

  • Migrating to SAP General Ledger (NewGL)  on a different box

    We are looking at migrating to SAP General Ledger on a production system with over 150 company codes and 10 years of unarchived data. Since this results in pretty large database tables we are looking at several options to minimize business impact.
    Among the available options, I have been told that it is possible to perform a migration from one box to another rather than in-place. I'm having trouble visualizing how transactional data from other modules (CO, SD, MM, PP etc) would be preserved in this case.
    Can anyone tell me if migrating from classic GL on one box to new GL on another is possible? Does it really reduce downtime? If so, how does it achieve this time savings? What are the pitfalls of taking this approach? Can a box-to-box approach be taken without loss of non-GL transactional data?
    Thanks in advance,
    Paul

    Hi,
    we migrated on 31st of march 2008 3 different 46c systems (AT, IN, CN) with 3 huge and a few small company codes into one ECC 60 system (using HR, SD, MM, PM, PP, QM, FI, CO). In ECC 60 we are using NewGL, document split, functional area reporting, PRCTR-wise balance sheets, segment reporting, FI/CO online integration, leding ledger IFRS, 2 non leading ledgers for every comp. code,...
    The migration project was started a year before go-live the system downtime was only the 31st of march (one day) for each company code.
    The main thing was, that we decided not to migrate any old transactional data to the new system but only the data (master data, open items, open PO's,...) thats needed.
    So the old stuff remains still in the old system (FY-end closing was done there) and all comp.codes started the new fiscal year in the new system.
    Due to the fact that many reporting issues where covered by business warehouse this ensured a continously reporting across the old and new system landscape and there was never a need to have "old" data visible in the new system.
    BR Christian

  • List of SAP Enjoy Transactions

    Does any one has the list of SAP Enjoy transactions.
    please send me [email protected]
    It is required immediately. Pls Help.

    Hi                                       
    Tcode for MM Module
    All transaction are stored in table TSTC. 
    Transaction for MM module start with M. 
    IH09 - Display Material
    MM01 - Create Material 
    MM02 - Change Material 
    MM03 - Display Material
    MM50 - List Extendable Materials
    MMBE - Stock Overview
    MMI1 - Create Operating Supplies
    MMN1 - Create Non-Stock Material 
    MMS1 - Create Service
    MMU1 - Create Non-Valuated Material
    ME51N - Create Purchase Requisition
    ME52N - Change Purchase Requisition
    ME53N - Display Purchase Requisition
    ME5A - Purchase Requisitions: List Display
    ME5J - Purchase Requisitions for Project
    ME5K - Requisitions by Account Assignment
    MELB - Purch. Transactions by Tracking No.
    ME56 - Assign Source to Purch. Requisition
    ME57 - Assign and Process Requisitions
    ME58 - Ordering: Assigned Requisitions
    ME59 - Automatic Generation of POs
    ME54 - Release Purchase Requisition
    ME55 - Collective Release of Purchase Reqs.
    ME5F - Release Reminder: Purch. Requisition
    MB21 - Create Reservation
    MB22 - Change Reservation
    MB23 - Display Reservation
    MB24 - Reservations by Material
    MB25 - Reservations by Account Assignment
    MB1C - Other Goods Receipts
    MB90 - Output Processing for Mat. Documents
    MB21 - Create Reservation
    MB22 - Change Reservation
    MB23 - Display Reservation
    MB24 - Reservations by Material
    MB25 - Reservations by Account Assignment
    MBRL - Return Delivery per Mat. Document
    MB1C - Other Goods Receipts
    MB90 - Output Processing for Mat. Documents
    MB1B - Transfer Posting
    MIBC - ABC Analysis for Cycle Counting
    MI01 - Create Physical Inventory Document
    MI02 - Change Physical Inventory Document
    MI03 - Display Physical Inventory Document
    MI31 - Batch Input: Create Phys. Inv. Doc.
    MI32 - Batch Input: Block Material
    MI33 - Batch Input: Freeze Book Inv.Balance
    MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
    MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
    MIQ1 - Batch Input: PhInvDoc. Project Stock
    MI01 - Create Physical Inventory Document
    MI02 - Change Physical Inventory Document
    MI03 - Display Physical Inventory Document
    MI31 - Batch Input: Create Phys. Inv. Doc.
    MI32 - Batch Input: Block Material
    MI33 - Batch Input: Freeze Book Inv.Balance
    MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
    MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
    MIQ1 - Batch Input: PhInvDoc. Project Stock
    MI01 - Create Physical Inventory Document
    MI02 - Change Physical Inventory Document
    MI03 - Display Physical Inventory Document
    MI31 - Batch Input: Create Phys. Inv. Doc.
    MI32 - Batch Input: Block Material
    MI33 - Batch Input: Freeze Book Inv.Balance
    MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
    MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
    MIQ1 - Batch Input: PhInvDoc. Project Stock
    MI21 - Print physical inventory document
    MI04 - Enter Inventory Count with Document
    MI05 - Change Inventory Count
    MI06 - Display Inventory Count
    MI09 - Enter Inventory Count w/o Document
    MI34 - Batch Input: Enter Count
    MI35 - Batch Input: Post Zero Stock Balance
    MI38 - Batch Input: Count and Differences
    MI39 - Batch Input: Document and Count
    MI40 - Batch Input: Doc., Count and Diff.
    MI08 - Create List of Differences with Doc.
    MI10 - Create List of Differences w/o Doc.
    MI20 - Print List of Differences
    MI11 - Physical Inventory Document Recount
    MI07 - Process List of Differences
    MI37 - Batch Input: Post Differences
    CT01 - Create Characteristic
    CT02 - Change Characteristic
    CT03 - Display Characteristic
    CL01 - Create Class
    CL02 - Classes
    CL03 - Display Class
    CL04 - Delete Class
    CL2B - Class Types
    Important SAP MM Tcodes 1
    ME01                 Maintain Source List                 
    ME03                 Display Source List                  
    ME04                 Changes to Source List               
    ME05                 Generate Source List                 
    ME06                 Analyze Source List                  
    ME07                 Reorganize Source List               
    ME08                 Send Source List                     
    ME0M                 Source List for Material             
    ME11                 Create Purchasing Info Record        
    ME12                 Change Purchasing Info Record        
    ME13                 Display Purchasing Info Record       
    ME14                 Changes to Purchasing Info Record    
    ME15                 Flag Purch. Info Rec. for Deletion   
    ME16                 Purchasing Info Recs. for Deletion   
    ME17                 Archive Info Records                 
    ME18                 Send Purchasing Info Record          
    ME1A                 Archived Purchasing Info Records     
    ME1B                 Redetermine Info Record Price        
    ME1E                 Quotation Price History              
    ME1L                 Info Records Per Vendor              
    ME1M                 Info Records per Material            
    ME1P                 Purchase Order Price History         
    ME1W                 Info Records Per Material Group      
    ME1X                 Buyer's Negotiation Sheet for Vendor 
    ME1Y                 Buyer's Negotiat. Sheet for Material 
    ME21                 Create Purchase Order                
    ME21N                Create Purchase Order                             
    ME22                 Change Purchase Order                             
    ME22N                Change Purchase Order                             
    ME23                 Display Purchase Order                            
    ME23N                Display Purchase Order                            
    ME24                 Maintain Purchase Order Supplement                
    ME25                 Create PO with Source Determination               
    ME26                 Display PO Supplement (IR)                        
    ME27                 Create Stock Transport Order                      
    ME28                 Release Purchase Order                            
    ME29N                Release purchase order                            
    ME2A                 Monitor Confirmations                             
    ME2B                 POs by Requirement Tracking Number                
    ME2C                 Purchase Orders by Material Group                 
    ME2J                 Purchase Orders for Project                       
    ME2K                 Purch. Orders by Account Assignment               
    ME2L                 Purchase Orders by Vendor                         
    ME2M                 Purchase Orders by Material                       
    ME2N                 Purchase Orders by PO Number                      
    ME2O                 SC Stock Monitoring (Vendor)                      
    ME2S                 Services per Purchase Order                       
    ME2V                 Goods Receipt Forecast                            
    ME2W                 Purchase Orders for Supplying Plant               
    ME308                Send Contracts with Conditions                    
    ME31                 Create Outline Agreement                          
    ME31K                Create Contract                                   
    ME31L                Create Scheduling Agreement                       
    ME32                 Change Outline Agreement                          
    ME32K                Change Contract                                   
    ME32L                Change Scheduling Agreement                       
    ME33                 Display Outline Agreement                         
    ME33K                Display Contract                                  
    ME33L                Display Scheduling Agreement                      
    ME34                 Maintain Outl. Agreement Supplement               
    ME34K                Maintain Contract Supplement                      
    ME34L                Maintain Sched. Agreement Supplement              
    ME35                 Release Outline Agreement                         
    ME35K                Release Contract                                  
    ME35L                Release Scheduling Agreement                      
    ME36                 Display Agreement Supplement (IR)                 
    ME37                 Create Transport Scheduling Agmt.                 
    ME38                 Maintain Sched. Agreement Schedule                
    ME39                 Display Sched. Agmt. Schedule (TEST)              
    ME3A                 Transm. Release Documentation Record              
    ME3B                 Outl. Agreements per Requirement No.              
    ME3C                 Outline Agreements by Material Group              
    ME3J                 Outline Agreements per Project                    
    ME3K                 Outl. Agreements by Acct. Assignment              
    ME3L                 Outline Agreements per Vendor                     
    ME3M                 Outline Agreements by Material                    
    ME3N                 Outline Agreements by Agreement No.               
    ME3P                 Recalculate Contract Price                        
    ME3R                 Recalculate Sched. Agreement Price                
    ME3S                 Service List for Contract                         
    ME41                 Create Request For Quotation                      
    ME42                 Change Request For Quotation                      
    ME43                 Display Request For Quotation                     
    ME44                 Maintain RFQ Supplement                           
    ME45                 Release RFQ                                       
    ME47                 Create Quotation                                  
    ME48                 Display Quotation                                 
    ME49                 Price Comparison List                             
    ME4B                 RFQs by Requirement Tracking Number               
    ME4C                 RFQs by Material Group                            
    ME4L                 RFQs by Vendor                                    
    ME4M                 RFQs by Material                                  
    ME4N                 RFQs by RFQ Number                                
    ME4S                 RFQs by Collective Number                         
    ME51                 Create Purchase Requisition                       
    ME51N                Create Purchase Requisition                       
    ME52                 Change Purchase Requisition                       
    ME52N                Change Purchase Requisition                       
    ME52NB               Buyer Approval: Purchase Requisition              
    ME53                 Display Purchase Requisition                      
    ME53N                Display Purchase Requisition                      
    ME54                 Release Purchase Requisition                      
    ME54N                Release Purchase Requisition                      
    ME55                 Collective Release of Purchase Reqs.              
    ME56                 Assign Source to Purch. Requisition               
    ME57                 Assign and Process Requisitions                   
    ME58                 Ordering: Assigned Requisitions                   
    ME59                 Automatic Generation of POs                       
    ME59N                Automatic generation of POs                       
    ME5A                 Purchase Requisitions: List Display               
    ME5F                 Release Reminder: Purch. Requisition              
    ME5J                 Purchase Requisitions for Project                 
    ME5K                 Requisitions by Account Assignment                
    ME5R                 Archived Purchase Requisitions                    
    ME5W                 Resubmission of Purch. Requisitions               
    ME61                 Maintain Vendor Evaluation                        
    ME62                 Display Vendor Evaluation                         
    ME63                 Evaluation of Automatic Subcriteria               
    ME64                 Evaluation Comparison                             
    ME65                 Evaluation Lists                                  
    ME6A                 Changes to Vendor Evaluation                      
    ME6B                 Display Vendor Evaln. for Material                
    ME6C                 Vendors Without Evaluation                        
    ME6D                 Vendors Not Evaluated Since...                    
    ME6E                 Evaluation Records Without Weighting              
    ME6F                 Print                                             
    ME6G                 Vendor Evaluation in the Background               
    ME6H                 Standard Analysis: Vendor Evaluation              
    ME6Z                 Transport Vendor Evaluation Tables                
    ME80                 Purchasing Reporting                              
    ME80A                Purchasing Reporting: RFQs                       
    ME80AN               General Analyses (A)                             
    ME80F                Purchasing Reporting: POs                        
    ME80FN               General Analyses (F)                             
    ME80R                Purchasing Reporting: Outline Agmts.             
    ME80RN               General Analyses (L,K)                           
    ME81                 Analysis of Order Values                         
    ME81N                Analysis of Order Values                         
    ME82                 Archived Purchasing Documents                    
    ME84                 Generation of Sched. Agmt. Releases              
    ME84A                Individual Display of SA Release                 
    ME85                 Renumber Schedule Lines                          
    ME86                 Aggregate Schedule Lines                         
    ME87                 Aggregate PO History                             
    ME88                 Set Agr. ***. Qty./Reconcil. Date
    ME91                 Purchasing Docs.: Urging/Reminding               
    ME91A                Urge Submission of Quotations                    
    ME91E                Sch. Agmt. Schedules: Urging/Remind.             
    ME91F                Purchase Orders: Urging/Reminders                
    ME92                 Monitor Order Acknowledgment                     
    ME92F                Monitor Order Acknowledgment                     
    ME92K                Monitor Order Acknowledgment                     
    ME92L                Monitor Order Acknowledgment                     
    ME97                 Archive Purchase Requisitions                    
    ME98                 Archive Purchasing Documents                     
    ME99                 Messages from Purchase Orders                    
    ME9A                 Message Output: RFQs                              
    ME9E                 Message Output: Sch. Agmt. Schedules              
    ME9F                 Message Output: Purchase Orders                   
    ME9K                 Message Output: Contracts                         
    ME9L                 Message Output: Sched. Agreements                 
    MEAN                 Delivery Addresses                                
    MEB0                 Reversal of Settlement Runs                       
    MEB1                 Create Reb. Arrangs. (Subseq. Sett.)              
    MEB2                 Change Reb. Arrangs. (Subseq. Sett.)              
    MEB3                 Displ. Reb. Arrangs. (Subseq. Sett.)              
    MEB4                 Settlement re Vendor Rebate Arrs.                 
    MEB5                 List of Vendor Rebate Arrangements                
    MEB6                 Busn. Vol. Data, Vendor Rebate Arrs.              
    MEB7                 Extend Vendor Rebate Arrangements                 
    MEB8                 Det. Statement, Vendor Rebate Arrs.               
    MEB9                 Stat. Statement, Vendor Rebate Arrs.              
    MEBA                 Comp. Suppl. BV, Vendor Rebate Arr.               
    MEBB                 Check Open Docs., Vendor Reb. Arrs.               
    MEBC                 Check Customizing: Subsequent Sett.               
    MEBE                 Workflow Sett. re Vendor Reb. Arrs.               
    MEBF                 Updating of External Busn. Volumes                
    MEBG                 Chg. Curr. (Euro), Vend. Reb. Arrs.               
    MEBH                 Generate Work Items (Man. Extension)              
    MEBI                 Message, Subs.Settlem. - Settlem.Run              
    MEBJ                 Recompile Income, Vendor Reb. Arrs.               
    MEBK                 Message., Subs. Settlem.- Arrangment              
    MEBM                 List of settlement runs for arrngmts             
    MEBR                 Archive Rebate Arrangements                      
    MEBS                 Stmnt. Sett. Docs., Vend. Reb. Arrs.             
    MEBT                 Test Data: External Business Volumes             
    MEBV                 Extend Rebate Arrangements (Dialog)              
    MECCP_ME2K           For Requisition Account Assignment               
    MEDL                 Price Change: Contract                           
    MEI1                 Automatic Purchasing Document Change             
    MEI2                 Automatic Document Change                        
    MEI3                 Recompilation of Document Index                  
    MEI4                 Compile Worklist for Document Index              
    MEI5                 Delete Worklist for Document Index               
    MEI6                 Delete purchasing document index                 
    MEI7                 Change sales prices in purch. orders             
    MEI8                 Recomp. doc. index settlement req.               
    MEI9                 Recomp. doc. index vendor bill. doc.             
    MEIA                 New Structure Doc.Ind. Cust. Sett.               
    MEIS                 Data Selection: Arrivals                         
    MEK1                 Create Conditions (Purchasing)                   
    MEK2                 Change Conditions (Purchasing)                   
    MEK3                 Display Conditions (Purchasing)                  
    MEK31                Condition Maintenance: Change                    
    MEK32                Condition Maintenance: Change                    
    MEK33                Condition Maintenance: Change                    
    MEK4                 Create Conditions (Purchasing)                   
    MEKA                 Conditions: General Overview                     
    MEKB                 Conditions by Contract                            
    MEKC                 Conditions by Info Record                         
    MEKD                 Conditions for Material Group                     
    MEKE                 Conditions for Vendor                             
    MEKF                 Conditions for Material Type                      
    MEKG                 Conditions for Condition Group                    
    MEKH                 Market Price                                      
    MEKI                 Conditions for Incoterms                          
    MEKJ                 Conditions for Invoicing Party                    
    MEKK                 Conditions for Vendor Sub-Range                   
    MEKL                 Price Change: Scheduling Agreements               
    MEKLE                Currency Change: Sched. Agreements                
    MEKP                 Price Change: Info Records                        
    MEKPE                Currency Change: Info Records                     
    MEKR                 Price Change: Contracts                           
    MEKRE                Currency Change: Contracts                        
    MEKX                 Transport Condition Types Purchasing              
    MEKY                 Trnsp. Calc. Schema: Mkt. Pr. (Pur.)              
    MEKZ                 Trnsp. Calculation Schemas (Purch.)               
    MELB                 Purch. Transactions by Tracking No.               
    MEMASSIN             Mass-Changing of Purch. Info Records              
    MEMASSPO             Mass Change of Purchase Orders                    
    MEMASSRQ             Mass-Changing of Purch. Requisitions              
    MENU_MIGRATION       Menu Migration into New Hierarchy                 
    MEPA                 Order Price Simulation/Price Info                 
    MEPB                 Price Info/Vendor Negotiations                    
    MEPO                 Purchase Order                                   
    MEQ1                 Maintain Quota Arrangement                       
    MEQ3                 Display Quota Arrangement                        
    MEQ4                 Changes to Quota Arrangement                     
    MEQ6                 Analyze Quota Arrangement                        
    MEQ7                 Reorganize Quota Arrangement                     
    MEQ8                 Monitor Quota Arrangements                       
    MEQB                 Revise Quota Arrangement                         
    MEQM                 Quota Arrangement for Material                   
    MER4                 Settlement re Customer Rebate Arrs.              
    MER5                 List of Customer Rebate Arrangements             
    MER6                 Busn. Vols., Cust. Reb. Arrangements             
    MER7                 Extension of Cust. Reb. Arrangements             
    MER8                 Det. Statement: Cust. Rebate Arrs.               
    MER9                 Statement: Customer Reb. Arr. Stats.             
    MERA                 Comp. Suppl. BV, Cust. Rebate Arrs.              
    MERB                 Check re Open Docs. Cust. Reb. Arr.              
    MERE                 Workflow: Sett. Cust. Rebate Arrs.               
    MEREP_EX_REPLIC      SAP Mobile: Execute Replicator                   
    MEREP_GROUP          SAP Mobile: Mobile Group                         
    MEREP_LOG            SAP Mobile: Activity Log                         
    MEREP_MIG            SAP Mobile: Migration                            
    MEREP_MON            SAP Mobile: Mobile Monitor                       
    MEREP_PD             SAP Mobile: Profile Dialog                       
    MEREP_PURGE          SAP Mobile: Purge Tool                           
    MEREP_SBUILDER       SAP Mobile: SyncBO Builder                       
    MEREP_SCENGEN        SAP Mobile: SyncBO Generator                     
    MERF                 Updating of External Busn. Volumes               
    MERG                 Change Curr. (Euro) Cust. Reb. Arrs.             
    MERH                 Generate Work Items (Man. Extension)             
    MERJ                 Recomp. of Income, Cust. Reb. Arrs.              
    MERS                 Stmnt. Sett. Docs. Cust. Reb. Arrs.              
    MEU0                 Assign User to User Group                        
    MEU2                 Perform Busn. Volume Comp.: Rebate               
    MEU3                 Display Busn. Volume Comp.: Rebate               
    MEU4                 Display Busn. Volume Comp.: Rebate               
    MEU5                 Display Busn. Volume Comp.: Rebate               
    MEW0                 Procurement Transaction                          
    MEW1                 Create Requirement Request                       
    MEW10                Service Entry in Web                             
    MEW2                 Status Display: Requirement Requests             
    MEW3                 Collective Release of Purchase Reqs.             
    MEW5                 Collective Release of Purchase Order             
    MEW6                 Assign Purchase Orders WEB                       
    MEW7                 Release of Service Entry Sheets                  
    MEW8                 Release of Service Entry Sheet                   
    MEW9                 mew9                                             
    MEWP                 Web based PO                                     
    MEWS                 Service Entry (Component)                        
    ME_SWP_ALERT         Display MRP Alerts (Web)                         
    ME_SWP_CO            Display Purchasing Pricing (Web)                 
    ME_SWP_IV            Display Settlement Status (Web)                  
    ME_SWP_PDI           Display Purchase Document Info (Web)              
    ME_SWP_PH            Display Purchasing History (Web)                  
    ME_SWP_SRI           Display Schedule Releases (Web)                   
    ME_WIZARD            ME:  Registration and Generation
    <b>Please Awards Point if help full</b>Thanks
    Pankaj Kumar

  • Sap FICO Certification for Financial Accounting with mySAP ERP 2005

    Hi,
    I would like to write SAP-FICO Certification for Financial Accounting with mySAP ERP 2005
    Topic areas:
    SAP overview, Financial Accounting Master Data, Document and Posting Control,Special General Ledger Transactions, Document Parking, Substitution and Validation ,Payment Program, Dunning Program, Correspondence, Interest Calculation,Evaluation Options in Reporting ,Closing Operations in Financial Accounting ,Asset Accounting,The New General Ledger,SAP Solution Manager.
    If anyone have the Material for above topics, please send me my mail Id: [email protected]
    if anyone appeared recently for certification for the same code, please send model questions and answers.
    i will be very thankfull to you.
    Regards,
    Satyaprakash

    Hi
    I am also writing SAP-FICO Certification for Financial Accounting with mySAP ERP 2005.
    Request you to send me whatever the material you have in this regard.
    thanking you in advance
    Suri

  • Migration from SAP BC To SAP P.I

    HI Experts ,
    I am required to do migration from SAP BC to SAP P.I. I would require the following Info/Help from you as i have not worked on such scenario before this!
    1) What kind of challenges can be faced during migration from BC to XI?
    2) What is the best practise for doing the same?
    3) Can you share some scenario from where i can have some idea how to do migration?
    4) Generally how much time it takes in migration activity if ther are not much interfaces involved in it?
    Would appreciate your valuable inputs on the same!
    I have read How to guide docs on how to do migration from BC to XI but not convinced with the content
    Regards
    Saras Jain

    Hi Saras,
    I am giving you an example senario and a how to do all the steps and why it needed. if you need more information just mail me i'll give you the concerned PDF.
    Scenario
    SAP Business Connector enables data exchange between an SAP system and
    external systems using HTTP and e-mail. SAP Exchange Infrastructure (SAP XI)
    replaces SAP Business Connector (SAP BC).
    We distinguish between standard scenarios (that do not contain customer-specific
    development) and individual scenarios (that do contain services or mappings created
    by the customer). The following sections describe how to migrate both types of
    scenarios to SAP XI.
    Scenario 1 (IDoc – HTTP, HTTP – IDoc)
    An SAP system sends an IDoc to SAP BC or to SAP XI. The IDoc is converted to
    XML. It is sent to an external business partner by using HTTP.
    An external business partner sends an XML document by using HTTP to SAP BC or
    to SAP XI. The document is converted to an IDoc and sent to a connected SAP
    system in the internal system landscape.
    Scenario 2 (IDoc – Mail, Mail – IDoc)
    An SAP system sends an IDoc to SAP BC or to SAP XI. The IDoc is converted to
    XML. It is sent to an external business partner as an e-mail.
    An external business partner sends an e-mail to SAP BC or to SAP XI. The
    document is converted to an IDoc and sent to a connected SAP system in the
    internal system landscape.
    Flow Services
    Flow services are services that are written in the proprietary graphical-based flow
    language of SAP BC.
    Java Services
    Java services are services that are written in the Java language.
    There are several platforms that support Java, including SAP XI. However, the data
    model used in the Java services in SAP BC is proprietary.
    Stylesheet Transformations
    Stylesheet transformations are often used for mapping purposes. They take an XML
    document as input, convert it according to rules defined in the stylesheet, which is
    also an XML document, and produce an XML document as output.
    The XML Stylesheet Transformation Language (XSLT) was defined by W3C (World
    Wide Web Consortium), the consortium that defines most of the common standards in modern internet communication, such as HTML and SOAP.
    SAP NetWeaver is the open integration and application platform from SAP. With
    NetWeaver ’04, there is a significant overlap between the functions of SAP
    NetWeaver and SAP BC. Many functions provided by SAP BC are offered by SAP XI
    as part of SAP NetWeaver, for example, conversion of an IDoc to an XML message,
    mapping, routing, and adapters to connect to a large number of third-party back-end
    systems. SAP BC is therefore no longer needed. New or updated SAP solutions are
    based on SAP NetWeaver. Customers looking for a strategic integration solution for
    the complete application landscape should therefore now favor SAP NetWeaver.
    The last version of SAP BC was SAP BC 4.7, which was released in June 2003. SAP
    BC has not been developed further since this release. SAP BC is not released for
    any further platforms (such as Windows 2003) and does not support any further JDK
    versions, including the current version (Version 1.4).
    For information about the supported SAP BC versions, JDKs, and operating systems,
    see SAP Note 309834. For information about the support and maintenance strategy
    for SAP BC, see SAP Note 571530. Customers who still use SAP BC need to be
    aware of the following:
    • A solution based on SAP BC cannot be a strategic, long-term solution.
    • A solution based on SAP BC is based on technology that was implemented in
    2003 and that is no longer further developed.
    • SAP BC is supported on limited platforms and for limited JDKs only. Vendor
    support for some of these platforms and JDK versions will soon be
    discontinued.
    SAP BC and SAP NetWeaver are based on different technologies: SAP BC is based
    on webMethods’ proprietary Integration Server, whereas SAP NetWeaver is based
    on open standards, such as BPEL4WS (business process execution language for
    web services). Therefore, only parts of an SAP BC implementation, such as XSLT
    mappings, can be migrated to a solution based on SAP NetWeaver. Any custom
    programming based on SAP BC, such as SAP BC flow language, is unlikely to be
    reusable in the SAP NetWeaver context.
    Purpose of this Migration Guide
    The purpose of this migration guide is to provide scenario-based descriptions of the
    migration from a company’s system landscape that uses SAP BC to exchange
    documents with business partners, to a system landscape that uses SAP XI instead.
    This migration guide outlines, for certain scenarios, the individual steps a company
    has to take to replace an existing SAP BC implementation with SAP XI.
    The basic steps in the back-end systems are:
    • Defining the logical systems
    • Maintaining the ALE distribution model
    • Maintaining partner profiles and EDI ports
    • Maintaining RFC destinations
    The basic steps in the SAP XI system are:
    • Maintaining the System Landscape Directory
    • Configuring the IDoc adapter
    • Maintaining the receiver determinations, interface determinations, and
    interface agreements
    • Maintaining the communication channels
    The type of scenario to migrate typically has an impact on the communication channels only.
    Scenario 1 IDoc/HTTP
    IDoc – HTTP Using SAP BC
    Within the system landscape of a company, an SAP system sends an IDoc
    asynchronously to SAP BC. SAP BC converts the IDoc into a standard IDoc XML
    document. The fields of the IDoc are not modified, that is, the conversion does not
    involve any mapping of source fields to target fields. After conversion, SAP BC uses
    HTTP to send the XML document synchronously to an external URL of a business
    partner.
    System Landscape
    • An SAP system and SAP BC are installed within the same system landscape
    of a company.
    • The following information is defined in the SAP system to allow data
    exchange between the SAP system and SAP BC:
    o An RFC destination and a logical system for SAP BC
    o The distribution model is maintained, if necessary
    • The following information is defined in SAP BC:
    o An SAP server with an alias is defined. For this SAP server, the
    information that the SAP BC requires to connect to the SAP system is
    specified.
    o A listener is configured to listen to requests from the SAP system.
    o A routing rule with the transport type “XML” is configured for the
    specific sender, receiver, and message type. The routing rule
    determines how a message is to be routed and where it is to be routed
    to. The scenario described does not use an ACL, (Access Control List
    to restrict execution permissions for this routing rule) or pre-processing
    or post-processing SAP BC services.
    4.2 IDoc – HTTP Using SAP XI
    Check the prerequisites described above under Prerequisites for Standard
    Scenarios.
    The IDoc adapter is used to receive an IDoc from an SAP back-end system and
    convert it to XML.
    The adapter used to post this XML to an external destination is the plain HTTP
    adapter.
    To set up the communication channel, perform the following steps:
    1. Locate the routing rule in SAP
    Business Connector.
    In the Administration View, choose
    Adapters – Routing to navigate to
    Routing Rules.
    2. Select the details of the relevant routing rule.
    To display the details, choose the green triangle (Edit).
    Transport is typically set to XML and a URL is specified. You can use this
    URL in your SAP XI settings.In some cases, Transport is set to
    B2B Service and the parameters Server Alias, Folder and Service
    exist. This is the same as when Transport is set to XML and has the
    URL http://<serverhost>:<port>/invoke/<folder>/<service>.
    You can find <serverhost> and<port> in the definition of the
    remote server under Settings –>Remote Server in the Administration
    View.
    3. Set up the communication channel in the Integration Directory using the parameters from the SAP BC routing rule.
    Use the following settings:
    • Adapter Type: HTTP Receiver
    • Transport Protocol: HTTP 1.0
    • Message Protocol: XI Payload in HTTP Body
    • Adapter Engine: Integration Server
    • Addressing Type: URL Address
    • Target Host, Service Number,and Path need to be set in accordance with the SAP BC routing rule. HTTP Proxy Host and HTTP Proxy
    Port can be set if required.All other parameters have no corresponding values in SAP BC and should be set to their default values.
    regards
    Aashish Sinha
    P : Reward points if helpful

  • Delta data migration on SAP upgread from 4.6C to ECC 6.0

    Hi,
    We are planning for SAP upgrade in our Production environment and we are facing the below listed constraints and need your advice on the options to peform ECC Upgrade.
    1) Present HW resource is already facing bottleneck and so no additional load can be added.
    2) We have a completely new HW environment due to which we are unable to perform the test upgrade.
    Also, is there anyway to perform the Prepare Activities on new hardware (copy of Production system) first and then do the delta data migration for update of transactional data from present production system to new system (Prepare Activities done on this system) without affecting the Prepare Activities data.
    Thanks & Regards,
    Pratap

    Hi Pratap,
    You can first make a copy of you production system on new hardware by homogeneous system copy. Then do the test upgrade if everything will be fine. Then as suggested earlier migrate your production to new hardware and then do the upgrade.
    Thanks
    Sunny

Maybe you are looking for