Full life cycle implementation means implementing the project start from requirement gathering, analysis, solution desion, mapping, implementing according to ASAP methodology.
collective delivery is only if the order has same sh & shipping point.u can view due bill list & select the order for delivery which has same ship to pary & shipping point.
It is a vendor stock ordered by the customer that is still to be posted.Go for MMBE(stock overview)to look at the open order quantity.
item cat for indivdual purchase order is TAB and item cat group is BANC
SAP is an ERP application which is mainly used for automating all business activities with integration. The concept ERP says Enterprise Resources Planning. SAP does the same, like in normal course of business we get lot of cross functions while doing our own work say in Materials department. When we have to raise the request we have to see the possibilities of demand of end products, sales in the previous years, prices of materials weather to make or buy? and lot other things. Once we take the position of goods we got to pay the vendor, here usually the Finance department comes into picture and takes care of payment.
For doing these activities in a normal (real) business senario it would take at least 2 to 3 weeks time to collect the information and take decisions and organizing things. But in SAP application the time factor reduces. It become to 1 day for knowing information and do things, or it might take less time that depends on the company's policies and procedures. The level of acuracy in information is extreemly good. The integration part as explained in above example the connection between the departments as they follow in their company. If Materials department raises an order the check will be done before raising order (S&D department would have updated the status in system which can be viewed) and getting goods, then immediately the finance department will take the further actions about it.
A life cycle implementation consists of 5 stages.They are
The first major issue you are likely to face is in deciding what the company will want SAP to do at first Go-Live and what they anticipate they will want it to do in the future. It is usually much easier to build things into SAP at the beginning, even if they will not be used immediately, than it is to change them later after postings are being made in a live system. To resolve this you need to make a full analysis of the current and predicted future needs of the organisation.
Your next issue is that SAP will probably work, and require users to work, in a different way to how things were done in the past. The way to resolve this is: 1) Minimise the differences where you can and where it will not detract from the advantages of changing to SAP. 2) Keep the users informed throughout the process. 3) Provide good quality SAP training before the system goes live. 4) Provide high quality support after Go-live until the users are competent with the new system.
During implementation you will almost certainly face the issue of how to bring data from the systems that an organisation is currently using into SAP. How difficult this is depends on how old the current systems are and how compatible they are with SAP. Sometimes you can import the data directly using tools built into SAP, sometimes you will need consultants to configure specific solutions and sometimes it is simply easier and more cost effective to spend the time transferring data manually.
There are many other technical and business issues you might face but those are common ones early in the implementation.
GR/IR is the intermediate account.
Entries are debiting and crediting at the time of GRN and Invoice verification...
At the time of GRN entry is debit from GR/IR clearing account and in MIRO entry is crediting from the account
You should know the fields which you are going to update. For eg. If vendor master is to be uploaded, one should know which fields(like vendor name, address, accounting details, etc) are to be updated. Without even knowing that, one cannot update in LSMW.
Sand box, development , quality and production servers are landscape for sap
We use sand box for practice and development server for implementation, quality for check settings and then transfer to production server all the settings.
Testing in SAP is usually done by use of test scripts. These are sequences of instructions which follow business processes. They can be used by configuration, support and end users.
New configuration in SAP is usually done in a Development client. After the configuration is completed it will be tested in that client by the configuration and/or support team. When they are satisfied the config is working correctly they will transport the new settings to a Quality Assurance client. There, any client-specific configuration is added and then the tests are run again. When the config/support team are satisfied they will have the tests run by end users. The end users are more likely to spot any procedures that don't meet the usual business requirements but these might be deliberate, either as improvements or to meet the requirements of operating with SAP.
There are many points of integration between mm and both FICO and SD. However, MM deals with stock purchase and storage and the main poi with FICO is therefore Accounts Payable (there are others such as customs excise duty, tax, stock valuation, etc).
MM is where the stock sold through SD is controlled. The Materials master data, in which details of each item of stock is created and maintained, stock levels, etc is used in SD transactions to identify the goods or services being sold, how many are available and from where.
An item category defines the characteristics of an item. Which characteristics ar taken into account differs between modules. e.g. in MM - material number, goods receipt, invoice receipt, etc: in SD - Pricing, Billing, delivery, etc.
An item category Group, groups a variety of items together for accounting/stock control purposes.
A Pricing procedure governs the price applied to a material. It might take into account cost, discount, surcharge, freight, and tax. A Tax procedure determines the type and amount of tax that is applied and might vary according to the type of item e.g. food might have a different tax category compared to an automobile, fuel for domestic heating might be taxed differently from fuel for cars.
The full life cycle of mm module are:
enquiry,quotation, sale, billing and delivery.
After post goods issue the amount of stock reduces in the plant, value of stock reduces in the plant,when invoices are received the revenue accounts updated,also no requirement sits in the stock requirements list (md04).
SAP has 2 sides, one is technical which is ABAP, Basis and Netweaver which requires BE, B.Tech, MCA, MSc Is or any other equalent qualification, the other side is functional which has the functions like Materials Management, Production Management, Sales & Distribution, Finance and Controlling, CRM and so on...... which requires sound functional knowledge(work experiance) to understand the systems of different companies or industies how can we automize the activities of them through SAP.
So basically you deside based on your qualification and intrest, a BE with MBA can enter into functional side, an commerce graduate with MCA can enter into technical side, that means basically it is dealing with business, I feel people with technical and functional background can perform well and understand well in this field.
In 1st case it is called as intracompany stock transfer and the 2nd case is inter company stock transfer.
Profit centre is a managment oriented organizatinal unit created for internal controlling purpose.
They say cost centre hierarchy can be copied as profit center hierarchy...may be that means wotever u take as cost centre can be taken as a profit centre as well..e.g. departments in an organisation,or say products.But m not sure about it.
Is a program to transfer data from the SAB and the system is done through a private report to you.
contracts does not contains any schedulines where as sch agreements contains the delivery dates or sch lines it is the major difference.
The posting key DA is used for posting Customer Credit memos.
Maintain exchange rate in ob08 and in app user parameters we are giving company code payment method and next date.So in vendor master data we are maintaining USD.So the payment will be make in USD for that vendor.
In MM module we can do the following activities :-
you don't require enquiry or quotation , you can directly start salesorder process.
By using transaction code OBYC we can get the details of MM,Fico integration.
Vendor document posting is nothing but inputing the purchase invoice on to the systemPurchase account DBto Vendor Account.
Dunning Business Processes: Dunning is actually the process by which you ?bill? or ?invoice? a customer for past due items.
With regards bad Checks for example dunning procedure could follow these steps:
Steps 2-6 above will be handled by dunning levels in SAP.
Configuration before dunning can be carried out
Apart from ASAP another methodology is VSAP
account type and posting key