The following are the steps for BRS: 1. Create Bank Master Data - This can be created through T.Code FI01 or you can also create the house bank through IMG/FA/Bank accounting/Bank account 2. Define House Bank 3. Set up Bank selection payment programe- IMG/FA/ARAP/BT/AUTOIP/PM/Bank selection for payment prg. a. setup all co codes for payment transaction - Customer and vendors b.setup paying co codes for payment transactions c.setup payment method per country d.setup payment method per co code for payment transaction e.setup bank determination for payment transaction
Please go for Cheque mangement using T code FCHI (IMG/FA/ARAP/BT/OP/AutoOp/PaymentMedia/CheckManagement) and for void reasons FCHV. You can create Bank Reconcilliation statement by TC FF67 (SAP/AC/Treasury/CashManagement/Incomings/ManualBankStatement) . Don't forget to keep the opening Balance as zero. Use FBEA for post process.
All the steps together will lead to (FF67) Bank reconciliation statement.
1. Following is the sequence of configuration to be done for Electronis Bank Statment(EBS): 1. create Tranaction types( which helps you group all the house baks with same External transaction code). 2. assign them to house banks. 3 create and define posting rule keys . 4 assign them to external transaction codes. external transaction codes are bank specific codes for buisness tranactions( which it issues in each EBS) each one for each type of payment. eg. transfer order, foreign transfer,bill of exchange etc. 5 define posting specification for G/L posting as well as subledger posting 6. define account symbols(which determines the G/L account to be posted to) and assign them to posting keys.
2.
1. Create account symbols 2. Create gl accounts ans assign t account symbols 3. Create posting keys: 4. Posting rules 5. Assing external transactions
1. LSMW is widely used by EDI programmers. EDI Programmers connect the SAP system to Non SAP system. During this Data migration is a necessity. When data migrates from source to destination the destination code is differrent from the source code. So what LSMW does is * Converts the data in to batch files * Then converts the batch files in to source code batch files * And then mirgates data. Standard Interfaces like BAPI or Idoc are used in this process.
The LSMW comprises the following main steps: * Read data (legacy data in spreadsheet tables and/or sequential files). * Convert data (from the source into the target format). * Import data (to the database used by the R/3 application.
But, before these steps, you need to perform following steps : * Define source structure : structure of data in the source file. * Define target structure : structure of SAP that receives data. * Field mapping: Mapping between the source and target structure with conversions, if any. * Specify file: location of the source file
Of all the methods used for data migration like BDC, LSMW , Call Transaction which one is used most of the time? How is the decision made which method should be followed? What is the procedure followed for this analysis? All the 3 methods are used to migrate data. Selection of these methods depends on the scenario, amount of data need to transfer. LSMW is a ready tool provided by SAP and you have to follow some 17 steps to migrate master data. While in BDCs Session method is the better choice because of some advantages over call transaction. But call transaction is also very useful to do immediate updation of small amout of data. (In call transaction developer has to handle errors).
Bottom line is make choice of these methods based of real time requirements.
These methods are chosen completely based on situation you are in. Direct input method is not available for all scenarios; else, they are the simplest ones. In batch input method, you need to do recording for the transaction concerned. Similarly, IDoc, and BAPI are there, and use of these need to be decided based on the requirement.
Try to go through the some material on these four methods, and implement them. You will then have a fair idea about when to use wh
1. Some organisations select to implement SAP module by module, thus gets updated as per their convenience / schedule. This is called as updated project. Some organisations simply plan all integrated functional modules and decide to go-live with all functional modules and take their entire operations on SAP. This is called as End to End SAP implementation project.
2. Upgrade Project is a project where in SAP is already in place and it is the version upgrade from a lower end to a higher version.
End to End project is a project where SAP is implemented for the first time.
1. Vendor rating has to be done for new purchase order everytime. PO can be generated by using transaction ME21N. This PO has to be released after creation
The other way is to assign that item to the vendor and maintain info records and update it by using ME11. This can also be done manualy.
2. This is not possible. Price comaprison session only gives you the idea which supplier has given the best price for a particular material.you have to raise the po ME21N transaction only.
3. The vendor who has got best price will have a unique quotation number. USe ME21N transaction and create PO with respect RFQ from Overview tab .
profit center accounting is basicaly done for internal controlling purposes. It lets you determine the profit and loss using the cost of sale approach or period accounting approach. Here you can find the profit from an "area of reponsibility or pserson" point of view.this is accound based costing
Whereas in Profitability analysis, market segments based on product , cutomer,order aor any comobination of these are studied to find wots the profit. PA provides information to the marketing,sales and planning department so that they can make decisions. PA has two forms account based and CO based.
both these are tools for profit management, and both are alternative. They are not same.
Unlike a stock transfer from storage location to storage location, a stock transfer from plant to plant affects both accounting and Materials Planning, as follows:
* Accounting
Accounting is affected if both plants are assigned to different valuation areas. This means that a stock transfer leads not only to a quantity update but also to a value update (stock value, G/L accounts). Thus, parallel to the material document for stock transfer, an accounting document is created.
* Materials Planning
Materials Planning is affected because a change of plant stock is taken into account by Materials Planning.
2. The stock transfer from one plant to another belonging to same company code is same as that of belonging to different company code functionally.
In both the types of transfers, there will be a material document generated which will update the QTY in both the plants in the respective storage location.
Accounting document generation will depend on the valuation level of the material. If the materials are being valuated at company level and it is being transferred from one plant to another belonging to the same company code, no accounting entry is generated. However, if the valuation is being done at plant level, the accounting document will be generated in both the cases.
A Great Tutorials Portal
Aquarian Infotech System
Copyright © 2008 interviewmaterial.com. All rights reserved.