Ezsap.com

SAP Purchase to Pay Flow- SAP MM

admin — Sat, 05 Dec 2009 07:53:50 +0000

SAP MM (Materials Management)

SAP MM (Materials Management) is a module of the SAP Enterprise Resource Planning (ERP) package that is used for Procurement Handling and Inventory Management.
The module has two important master data – material and vendor.
Broadly, the various levels that can be defined for a SAP MM implementation are: Client, Company Code, Plant, Storage Location and Purchase Organization.
This is the largest and most complex in all of SAP modules. It can be divided into five major components. There are: materials management, plant maintenance, quality management, production planning and control, and a project management system. Each is divided into number of subcomponents.
SAP Materials management covers all tasks within the supply chain, including consumption-based planning, planning, vendor evaluation and invoice verification.
It also includes inventory and warehouse management to manage stock until usage dictates the cycle should begin again. Electronic Kanban/Just-in-Time delivery is supported.
Material Management covers the functionality required to purchase goods and services, manage inventory, and inspect incoming materials.
The Purchasing function includes creation of requisitions, requisition approval, purchase order generation, and receipt of goods and services.
Inventory Management includes issuing and transferring inventory, inventory restocking, and the inventory count and adjustment processes.

The basic of the purchase to pay flow is explained below.

Determination of Requirements
In this step, there is a requirement of material or service, which must be procured externally, from the user. The requirement must be recorded as Purchase Requisition (PR) document in SAP MM.
Purchase Requisition (PR) isan internal purchasing document in SAP ERP that is used to give notification to responsible department about the requirement of material/service and to keep track of such requirement.
Determination of the Source of supply
After the PR has been created in the previous step, the responsible department must process it. The buyer of the procurement department must determine the possible sources of supply of the material/service specified in the PR.
Vendor Selection
If in the previous step, there are some outline agreements or info record documents that can be used as references to create a PO, the buyer can select or choose which vendor that will be appointed to provide the material/service at this time.
PO Processing
In the previous step, the buyer has selected the vendor which will provide the material/service needed in PR. In this step, the buyer creates a Purchase Order (PO) based on the PR and the reference document (that can be an outline agreement, an info record, or a quotation).
PO Monitoring
After the PO has been sent to the vendor, the buyer has the responsibility to monitor whether the vendor delivers the material/service at the right time on the right place.
Goods Receipt
When the vendor delivers the material or perform the service, the responsible person of the company must perform the goods receipt (GR) or service acceptance (SA) transaction. The GR/SA will update the PO history.
Invoice Verification
After the vendor delivered the material/service, it will send the invoice to the person responsible in the company. Invoice is a formal document issued by a vendor to the company to request the payment for the material or service that the vendor has already provide to the company according to the terms of payment agreed in the PO.
Payment Processing
After the Invoice Receipt (IR) transaction has been posted, the vendor’s account payable will increase and the company must process the payment to that vendor as stated in the terms of payment of the PO. The payment transaction will be performed in FI module. After the payment has been posted, the vendor’s account payable will be debited and the cash or bank account will be credited.

SAP MM stands for Materials Management and this is part of SAP Logistics includes:

Requisitions
Purchase orders
Goods receipts
Accounts payable
Inventory management
BOM’s
Master raw materials, finished goods etc

Some of the Main SAP MM Transactions are:

ME51N – Create Requisition
ME21N – Create Purchase Order
MIGO – Goods receipt a PO
MIRO – Create Invoice

One of the main areas covered by MM module is Purchasing/Procurement. The purchasing process is initially started when there is a requirement of material/service from a user. If the material/service can not be obtained from company’s internal resource, the responsible person of that company must find the vendor/supplier which can provide it on the required date. The purchasing process is ended when the payment processing to the vendor that supply the material/service has been done.

SAP Order to Cash Flow- SAP SD

admin — Sat, 05 Dec 2009 07:03:14 +0000

SAP SD is simply Sales and Distribution

It’s all about selling goods & distributing them to relevant parties and gets the payments for relevant parties.
Helps to optimize all the tasks and activities carried out in sales, delivery and billing.
Key elements are: pre-sales support, inquiry processing, quotation processing, sales order processing, delivery processing, billing and sales information system.
SAP SD application components fulfills many of the international requirements that supports the sales and distribution activities with functions such as pricing and conditions, customer order processing, delivery monitoring, billing, credit and risk management.
The SAP sales and distribution is part of the logistics module that support your customers, starting from quotations, sales order and all the way towards billing the customer.
It is tightly integrated with the MM and PP functional modules. It allows companies to input their customer sales price, check for open orders and forecast etc.

The most important basic functional features in the SD module are:

Pricing
Availability Check
Credit Management
Material Determination
Output Determination
Text Processing

SAP SD stands for Sales and Distribution and this is the module which is used to manage customer-focused activities, from selling to delivery, including -

RFQ
Sales orders
Pricing
Picking (and other warehouse processes)
Packing
Shipping

Some of the main SAP SD transactions are:

VA01 – Create Customer Order
VL01N – Create a Delivery
VA03 – Display a Order
VL02N – Change Customer Delivery (F20 is to post a good issue)
VA05 – List Orders
VF01 – Create a Invoice

The Order to Cash flow roughly follows the following sequence -

A customer orders some items from your company by creating a sales order
Your company decides to deliver the items ordered by the customer.
This is recorded by creating a outbound delivery document
Once the items are available for sending to the customer, you post goods issue which reduces your inventory and puts the delivery in transit. This will create a material document.
You will post goods but the material document created will be stored in tables.
You will then create shipment document to actually ship the items.
You finally create a sales billing document.
This will have a corresponding accounting document created that will be in different tables.
When customer pays to your invoice, it will directly hit your AR account in FI.

SAP EP Training

admin — Thu, 26 Nov 2009 07:34:37 +0000

SAP Enterprise Portal, also known as an Enterprise Information Portal (EIP) or corporate portal, is a framework for integrating information, people and processes across organizational boundaries. It provides a secure unified access point, often in the form of a web-based user interface, and is designed to aggregate and personalize information through application-specific portlets. One hallmark of enterprise portals is the de-centralized content contribution and content management, which keeps the information always updated.

EP Administration
Module 1: Overview

Brief overview of SAP
Overview of SAP Netweaver and EP
Motivation for Portals and need for SAP EP

Module 2: Technical Infrastructure

SAP Enterprise Portal installation
SAP NW Architecture
Portal Framework, Portal Runtime, Portal Services.
Building Blocks of SAP EP.
SAP Enterprise Portal Architecture

Module 3: End user Perspective

Portal Login and Navigation
Portal Interface
Users, Roles and Groups.
Super Administration, User Administration, Content Administration
Portal Personalization

Module 4: User Management

Overview and Architecture
User Management Engine.
User Management Tools

Module 5: Portal Security

Security Concepts
Introduction to Authentication
Authorization Concepts
Single Sign On
Network Security

Module 6: Portal Platform Content

Content Object Model
Portal Content
Portal Content Catalog
Portal Content Studio
Object relations: Delta Links and copies
Working with iViews and Pages
Working with Worksets and Roles
Delegated Content Administration
Introduction to business packages
Design Changes and Branding

Module 7: Connectors

Portal Landscape
SAP Java Connector
Configuring of Java connector (JCO)
Integrating SAP systems

Module 8: Knowledge Management & Collaboration

Understanding Knowledge Management
Content Management (CM)
Search and Classification (TREX)
Collaboration & Unification Overview
Collaboration Rooms (CR)
Real Time collaboration

EP Development
Module 10: SAP Java development environment

Sap Net Weaver developer studio
SAP Component Model

Module 11: Web dynpro Introduction

Introduction to Web Dynpro Architecture
Web dynpro Tools
MVC-the roots of Web dynpro
Life cycle of web dynpro

Module 12: The context structure at Design time

Types of nodes
The structure of context
Context mapping
Internal mapping
External mapping

Module 13: The context structure at runtime

The typed context API
The Generic Context API

Module 14: Introduction of UI elements

Putting data on Screen: Context binding
Controlling the behavior of UI Elements using the context binding
Using basic composite UI Element

Module 15: Generic UI Services

Types of value help
Defining static Simple type containing value set
Simple value selector
Populating DDK UI Element
Extended value selector: Value help for using larger value sets.
Dynamic type modification: pModifying the value attribute’s data type programmatically

Module 16: Dynamic UI generation

Introduction
Modification of the context & UI elements at runtime
The use of dynamic actions

Module 17: The Adaptive RFC Layer

Remote invocation of ABAP functionality
The creation and management of Adaptive RFC model objects
The management use of adaptive RFC Model Objects.

Module 18: Overview of Interactive Forms

Prerequisites
Introduction to Interactive forms

Module 19: Overview of NWDI (Net weaver development infrastructure)
Module 20: ESS/MSS
Module 21: Web Page Composer Overview

SAP MSS/ESS Training

admin — Wed, 04 Nov 2009 11:12:50 +0000

ESS – Employee Self Service is an web enabled tool used to update their own datas by the employee itself.
MSS- Manager Self Service is an web enabled tool used for Managers to take report or update the datas of subordinate.
To implement LEAVE REQUEST &APPROVAKL, both ESS and MSS are not mandatory. But ESS is required.However this functionality is developed to be avaialable in MSS also if a client wants have both ESS and MSS. Without MSS, the business flow of Leave request would be in ESS is like this:
1. An employee wants to take two weeks of leave. He or she accesses the Leave Request Web application. He or she sees in the Team Calendar that other team members also have leave at the same time. Nonetheless, he or she requests leave for the planned period.
2. The leave requires approval. The system automatically determines the approver responsible and lists the name in the Web application. If required, the employee can overwrite the name of the approver.

ESS/MSS Architecture based on SAP NetWeaver 7.0
Required Components and Usage Types in a ESS/MSS landscape
Main steps for setting up a new ESS/MSS landscape
Main steps for setting up ESS/MSS in an existing landscape
Required SLD configuration Steps for a SAP ESS/MSS landscape
SAP Enterprise Portal and its technical connection to the SAP Backend System, including the Single Sign-on (SSO) Configuration
Technical configuration of ESS Business Packages in an SAPNW Enterprise Portal
Technical configuration of Adobe Document Services
Technical configuration of the Internet Graphics Server
Technical configuration of the ESS/MSS WebDynpro application
Applying ESS Patches using the Java Support Package Manager
Description and solutions of the top ten problems

Our Ads

admin — Sat, 22 Aug 2009 10:30:45 +0000

Our Classifieds

Our Ads

Our Articles

Our Videos

Security Training links

admin — Fri, 21 Aug 2009 10:11:40 +0000

…For more Links click Security Training links

PS Training links

admin — Fri, 21 Aug 2009 10:10:08 +0000

…For more links click PS Training links

Basis Training links

admin — Fri, 21 Aug 2009 10:04:55 +0000

…For more Links click Basis Training links

Retail Training links

admin — Fri, 21 Aug 2009 09:51:52 +0000

…For more Links click Retail Training links

MM Training links

admin — Fri, 21 Aug 2009 09:51:34 +0000

For more links click MM Training links