• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Mis project   jka - 21 - slideshare
 

Mis project jka - 21 - slideshare

on

  • 341 views

 

Statistics

Views

Total Views
341
Views on SlideShare
341
Embed Views
0

Actions

Likes
0
Downloads
14
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Mis project   jka - 21 - slideshare Mis project jka - 21 - slideshare Presentation Transcript

    • MANAGEMENT INFORMATION SYSTEM PROJECT TOPIC : IMPLEMENTATION OF SAP (SD) IN SHOPPERS’ STOP CHAIN OF MALLS, MUMBAI Submitted By J K Achuthan PGCBM - Defence 2013 Batch NMIMS, Mumbai
    • DESIGN OF THE OVERALL SAP SYSTEM
    • MASTER DATAs IN SAP SALES & DISTRIBUTION MODULE 1. 2. 3. 4. Maintain Customer Master Record Data Maintain Material Master Record Data Maintain Customer - Material Information Record Data Maintain Condition Master Record Data and Explain the Pricing Functions 5. Issue Output for Sales Documents 6. Work with the Incompletion Log
    • STEPS IN BUSINESS PROCESS 1. Pricing 16. Material Determination / Product Selection 2. Condition Types for Pricing 17. Item Proposal / Product Proposal 3. Condition Exclusion Groups for Pricing 18. Material Listing and Exclusion 4. Condition Supplement 19. Cross Selling 5. Free Goods 20. Customer Material Info Record 6. Header Conditions in Pricing 21. Cash Sales 7. Account Determination 22. Rush Order 8. Revenue Account Determination 23. Customer Complaints 9. Route Determination 24. Returns 10. Partner Determination Procedure 25. Subsequent Free of Charge Delivery 11. Output Determination 26. Free of Charge Delivery 12. Text Determination 27. Invoice Correction Request 28. Contracts / Outline Agreements 29. Consignment Business Process 30. Credit Management 13. 14. 15. Copy Control for Sales Documents Incompletion Log Bill of Materials
    • SPECIAL BUSINESS PROCESSES • • • • • • Inter Company sales Third Party sales process Make to Order Variant Configuration Consignment Business process Rebate processing
    • • The Sales and Distribution Document Types are categorized as follows: – Sales Document Types: Inquiry, Quotation, Standard Order, Credit and Debit Memo requests – Delivery Types: Delivery, Returns (delivery) – Billing Types: Invoice, Credit Memo, Debit Memo • Documents can be created with reference to previously created documents (for example, an Order created with reference to a Quotation). SAP can also keep track of the order cycle through the use of document flow. • You can influence the control of the Sales and Distribution documents and create new document types. • When creating a New Document Type, copy an existing one. By copying an existing entry you will also copy other table entries related to document processing. Select an Order Type that functions most like the one you are trying to create. Thereafter make the necessary changes. • The initial rule on an SAP SD project should be that no new document types will be created. During design, the sales processes are defined and SAP Standard Order Types and Configuration Options should be fully explored to meet the business requirements. Once it is determined that a process cannot be fulfilled with standard SAP document types / configuration, a New Document Type can be created.
    • The various Sales Document types are distinguished by their control elements, which are defined in tables. In this way, Sales Document types can be adapted to meet special demands or additional document types can be defined. Documents can vary along the following lines: Can the document be entered only with reference to another document? Should the existing customer-material information record be taken into consideration? Should the delivery date be proposed? Should the division be taken from the material master record for every item or should an alternative division specified in the header take precedence over the item specifications? Should a delivery note automatically be created when the sales document is posted?
    • Above are the document types delivered with SAP to support various business transactions. Sales documents are differentiated by whether they are Pre-Sales or Sales documents. Pre-Sales documents include Inquiries (IN) and Quotations (QT). An Inquiry is not a legally binding document but is used to document Customer inquiries about a company’s products or services. A quotation is a legal document in that you are giving a Customer Price information, which you need to abide by if the Customer decides to make the Purchase. Standard and Rush Orders are legal sales documents and represent a Customer’s request for product to be delivered on a specified date. Outline Agreements: Contract and Scheduling Agreements are legal agreements between supplier and customer to supply certain products in certain quantities for a specified price. There are several Document which are related to dealing with Customer Complaints. The Reject Button on the tool bar of the Sales Document allows the rejection of the entire document, a dialog box also allows entry of a rejection reason.
    • The system supports the following Shipping functions: Deadline monitoring for referencing documents such as Sales Orders and Purchase Orders Delivery creation and processing Monitoring and rechecking of Availability. If quantity is NA, a delivery is not created. Picking/Picking Confirmation Packing and Transportation Planning Printing and Transmission of Shipping Document and Shipping Papers Posting Goods Issue Updating of the Billing due List via posting of Goods Issue Using Overviews to control Business transactions currently being carried out. The Delivery Document is used for initiating and tracking shipping related activities in SD.
    • The following functions are supported by Billing: Invoice creation Credit and Debit memo creation Cancellation of business transactions/invoices Transferring Posting data to Financial accounting. This transfer is generally carried out when the Billing document is created. For complex Billing documents (i.e., Credit and Debit memos), you may need to set a posting block in the Billing document instead. The Accounting document associated with the Billing document will be created only after this block has been removed.
    • Using the menu path “Billing DocumentCreate,” you enter the SD Document number(s) for which you are creating a Billing Document. The system will verify whether or not the documents are relevant for billing. More than one document can be specified for billing. Also, more than one invoice can be created, if the line items specified do not meet the reqmts specified in the document flow. If the system is not able to create an invoice for a particular document to be billed (for example, because of a billing block), it is recorded as such in the billing log. Menupath: To create a specific billing document: LogisticsSDBillingBilling documentCreate
    • You create a Return Order (RE) when you agree to take back goods as a result of a complaint. A Return Order can be created with or without reference to a Sales Order. It can also be created with reference to a Billing Document. When you process Returns, you can control whether the system should automatically set a Billing Block. This is controlled in Sales Document Type configuration. After checking the goods, you can release the Returns Delivery for Credit Memo creation by removing the Billing Block on the Return Order. At this stage, you can also determine the amount of the quantity to be credited. You can also enter a reason for rejection. The basic steps regarding Return processing in SAP are as follows: A Return Order is created that has an automatic Billing Block. A Return Delivery is created (post Goods Issue, but system understands it as a receipt). The Billing Block is removed from the Return Order, and the order quantity is adjusted to equal the quantity actually received. A Credit Memo is created, using the Return Order quantity as the basis.
    • CONCLUSION • Introducing SAP (SD) in the Firm required 3 x 2 Hrs Training Sessions for the employees per Week for Two Months. Total 50 Hrs. • Implementation Method chosen was simultaneous running of both SAP and previous systems for further period of 4 Months. This ensured gaining of familiarity as well as removal of glitches, and correcting Employees’ mistakes. • Success in Implementing SAP was that ‘No Work’ was left incomplete at the end of each Day. Otherwise the System cannot run on the next Day, and will show which all work is outstanding of the previous day. • Introducing SAP was a costly affair. The benefits could be understood only during the Second year onwards. • The Quality and confidence of the Staff has increased. They are also getting better paid as the Company is working more efficiently. • The Company has retained the Consultants to help further simplify procedures, apply better Report formats and switch to ‘Cloud’.