The document summarizes how goods receipts or invoices are distributed among existing schedule lines in a purchasing document. It explains that the distribution is based on comparing the creation date of the schedule line and the entry date of the goods receipt/invoice. If the schedule line was created before the goods receipt was entered, then its quantities can be distributed to that schedule line. The document provides examples to illustrate this distribution process.
Validation and substitution -sap fi advance functions 2019GuangfuDavidLi
The document discusses validation and substitution in SAP accounting documents. Validation adds checks to minimize data entry errors, which can be set up at the document header and line item levels using Boolean logic. Substitution helps replace field contents based on predefined conditions. Examples are provided of setting up validations to check business areas on invoices and substitutions to automatically populate blank fields like customer name and profit center.
The document outlines the steps to configure output for a picking list in SAP:
1. Check the output type EK00 and maintain standard partner functions.
2. Assign the output type to shipping points and define message numbers, dispatch times, and transmission mediums.
3. Maintain print parameters for shipping points, then test by creating a sales order and delivery to see the picking list automatically populate picked quantities.
This summary provides an overview of the key points about COPA (Controlling Profitability Analysis) and COPA realignment from the document:
1. COPA allows companies to evaluate profitability by strategic business units by capturing sales data, discounts, expenses, and costs to determine actual profits.
2. COPA data is stored in four main tables (CE1XXXX, CE2XXXX, CE3XXXX, CE4XXXX) with profitability segments assigning a unique set of characteristic values like product, customer, and business unit.
3. COPA data may require realignment due to changes in organization structure, master data corrections, etc. Realignment updates the characteristic combinations in profitability
Sales Order Specific Planned Independent Reqt ConsumptionVijay Pisipaty
Standard SAP ECC 6.0 functionality does not provide an ability to control Sales Order specific (or Customer Speciifc) Planned Independent Requirements netting/offsetting/reduction.
There now exists a solution that alleviates the aforesaid GAP in SAP ECC 6.0.
For more details on the solution, please see attached solution brief.
New gl functionality_by_guntupalli_hari_krishna_Hari Krishna
SAP NUEVO LIBRO MAYOR,SAP NEW دفتر الأستاذ العام,SAP新总账,SAP neue Hauptbuch,एसएपी नई सामान्य खाता,எஸ்ஏபி புதிய பொது லெட்ஜர்,SAP NEW総勘定元帳,SAP의 새로운 원장,SAP General Ledger НОВЫЙ,SAP NUEVO LIBRO MAYOR,SAP NEW GENERAL LEDGER
This document lists key tables used in SAP IS-U (Industry Solution for Utilities) for billing, invoicing, device and installation master data, profiles, settlements, and data exchange. It includes tables for business partner, contract, product, installation, device, and meter reading master data as well as billing documents, invoices, settlements, and pricing.
The document discusses asset accounting in SAP, including:
- Asset accounting is a subsidiary ledger of financial accounting that updates general ledger accounts.
- Asset classes are used to group assets, assign accounts and default values, and structure assets for reporting.
- Charts of depreciation define depreciation areas for book, tax, and other purposes across asset classes.
- Master data includes creating asset records via asset classes or copying, and time-dependent assignments.
- Asset acquisitions can integrate with accounts payable/receivable or use a clearing account.
Validation and substitution -sap fi advance functions 2019GuangfuDavidLi
The document discusses validation and substitution in SAP accounting documents. Validation adds checks to minimize data entry errors, which can be set up at the document header and line item levels using Boolean logic. Substitution helps replace field contents based on predefined conditions. Examples are provided of setting up validations to check business areas on invoices and substitutions to automatically populate blank fields like customer name and profit center.
The document outlines the steps to configure output for a picking list in SAP:
1. Check the output type EK00 and maintain standard partner functions.
2. Assign the output type to shipping points and define message numbers, dispatch times, and transmission mediums.
3. Maintain print parameters for shipping points, then test by creating a sales order and delivery to see the picking list automatically populate picked quantities.
This summary provides an overview of the key points about COPA (Controlling Profitability Analysis) and COPA realignment from the document:
1. COPA allows companies to evaluate profitability by strategic business units by capturing sales data, discounts, expenses, and costs to determine actual profits.
2. COPA data is stored in four main tables (CE1XXXX, CE2XXXX, CE3XXXX, CE4XXXX) with profitability segments assigning a unique set of characteristic values like product, customer, and business unit.
3. COPA data may require realignment due to changes in organization structure, master data corrections, etc. Realignment updates the characteristic combinations in profitability
Sales Order Specific Planned Independent Reqt ConsumptionVijay Pisipaty
Standard SAP ECC 6.0 functionality does not provide an ability to control Sales Order specific (or Customer Speciifc) Planned Independent Requirements netting/offsetting/reduction.
There now exists a solution that alleviates the aforesaid GAP in SAP ECC 6.0.
For more details on the solution, please see attached solution brief.
New gl functionality_by_guntupalli_hari_krishna_Hari Krishna
SAP NUEVO LIBRO MAYOR,SAP NEW دفتر الأستاذ العام,SAP新总账,SAP neue Hauptbuch,एसएपी नई सामान्य खाता,எஸ்ஏபி புதிய பொது லெட்ஜர்,SAP NEW総勘定元帳,SAP의 새로운 원장,SAP General Ledger НОВЫЙ,SAP NUEVO LIBRO MAYOR,SAP NEW GENERAL LEDGER
This document lists key tables used in SAP IS-U (Industry Solution for Utilities) for billing, invoicing, device and installation master data, profiles, settlements, and data exchange. It includes tables for business partner, contract, product, installation, device, and meter reading master data as well as billing documents, invoices, settlements, and pricing.
The document discusses asset accounting in SAP, including:
- Asset accounting is a subsidiary ledger of financial accounting that updates general ledger accounts.
- Asset classes are used to group assets, assign accounts and default values, and structure assets for reporting.
- Charts of depreciation define depreciation areas for book, tax, and other purposes across asset classes.
- Master data includes creating asset records via asset classes or copying, and time-dependent assignments.
- Asset acquisitions can integrate with accounts payable/receivable or use a clearing account.
SAP scripts can be used to design customized printing formats for documents like purchase orders and invoices. SAP scripts allows printing barcodes directly by combining it with barcode software. This document provides tips and tricks for using various SAP script commands and functions, including how to calculate totals and subtotals using subroutines, set different fonts on the same line, print footers only on the last page, and retrieve data without modifying the original program. It also discusses topics like orientations, protect/endprotect, and converting SAP script spools to PDF.
The document provides an overview of the enterprise structure for SAP accounting, human resources, sales, purchasing, and logistics modules. It outlines the default controlling areas, company codes, purchasing and sales organizations, plants, and other standard organizational units used in SAP best practices. The structure includes areas for finance, controlling, human resources, purchasing, production, distribution, and sales.
Free goods is a type of quantity discount where additional goods are provided at no extra charge when a certain purchase quantity is met. Free goods can be configured manually by specifying free item categories, or automatically where the system proposes free goods that are either exclusive, meaning the free goods quantity is excluded from the total, or inclusive, where it is included. Multiple steps must be taken to set up and activate free goods determination including creating condition tables, defining condition types, procedures, and records to control how free items are granted and priced.
A business requirement may arise making it necessary for you to move Fixed assets from one
company code to another (intercompany assets transfer for Eg: From company code XXX to YYY)
or from one organization unit to another, within the same company code (intracompany transfer).
The end to end process of fixed asset transfers involves configuration settings as well as user
frontend activities.
This posts will discuss the process of intercompany asset transfer end to end. It is assumed that the
reader has, at the very least, a basic knowledge of Asset Accounting. The complete cycle of
intercompany fixed asset transfer will include the below steps:
I. Prerequisites/ Configuration steps: (Asset accounting configuration should be
available in the system, apart from below configurations are required)
1. Creation of GL Accounts
2. Define Transfer Variants
3. Assign G/L Accounts Determination
4. Activate Inter-company postings for Asset document type (AA)
II. Intercompany Asset Transfer Steps (End User):
1. Executing an intercompany asset transfer transaction
2. Display document
3. Cross company code document display
4. Asset explorer
The document describes how to clear quantity differences between goods receipts and invoices for a purchase order using transaction code MR11 in SAP. Quantity differences result in a balance on the GR/IR clearing account. Using MR11, the user selects a purchase order, posts the difference, and an accounting document is generated. The accounting document can be displayed to view the original materials management document.
This document provides an overview of invoice verification in SAP, including the key steps and concepts. It describes the target groups, types of invoices, data required, screens used, and how to handle tasks like parking invoices, credit memos, excise invoices, devaluation, physical inventory, and retrieving inventory management information. The goal is to explain how to enter, verify, and process different types of vendor invoices correctly in SAP.
1. The document describes product allocation during sales order entry between SAP R/3 and SAP APO. It can be done with or without directly checking the planning area.
2. Key steps include creating a sales order in SAP R/3, checking availability in SAP APO which may result in a delivery proposal, and adopting the results in SAP R/3.
3. Settings must be configured in both SAP R/3 and SAP APO for the systems to communicate properly during the product allocation check.
Master data in SAP contains records that remain in the database over an extended period of time, such as material, vendor, and customer records. Material master data integrates information from different departments and contains details like material numbers, descriptions, purchasing data, and accounting information. Service master records describe services that may need to be procured and contain details like the service number, category, description, and valuation class. Master data is organized according to organizational hierarchies like clients, plants, and storage locations to prevent redundant storage and allow easy management of information.
The document summarizes the process of scheduling agreement release processing in SAP R/3. It involves 3 main steps: 1) Material requirements planning to determine delivery schedules. 2) Release generation by translating schedules into forecast (FRC) and JIT releases. 3) Output and transmission of releases as messages to vendors. Creation profiles allow customizing how releases are aggregated and generated. The system updates fields and stores releases upon output to designate them as completed.
This document provides an overview of PI sheets in SAP, which can be used to inform production operators of steps to perform. There are two types: ABAP-based and browser-based. Browser-based PI sheets are configured by defining master data like materials and BOMs, transporting standard SAP settings, creating control recipes and destinations, defining process message characteristics, assigning process instructions to recipes, releasing control recipes to generate PI sheets, and using the sheets to record operator inputs and update order data. PI sheets allow recording of various production activities and values in a flexible manner.
The document discusses the Legacy System Migration Workbench (LSMW) in SAP, which is a tool used to transfer data from non-SAP legacy systems to an SAP R/3 system. It describes the basic principles, features, and steps of using LSMW, including maintaining source structures and fields, mapping fields, importing and converting data, and displaying the results. The main steps are creating an LSMW project, mapping source and target structures and fields, importing legacy data files, and converting the data for use in SAP.
Presentation from LBSi SAP Business One User Group December 2012. Inventory Management in SAP Business One. Learn how to setup inventory and perform cycle counts.
Revamping Ticket Management System For Efficient Support Operations Powerpoin...SlideTeam
The document discusses the benefits of meditation for reducing stress and anxiety. Regular meditation practice can help calm the mind and body by lowering heart rate and blood pressure. Studies have shown that meditating for just 10-20 minutes per day can have significant positive impacts on both mental and physical health over time.
This document provides instructions for configuring and activating split valuation in SAP to separately value in-house production stocks and externally procured stocks of materials. It outlines the steps to 1) activate split valuation in the system, 2) create valuation types for in-house and external stocks, 3) assign valuation categories to the types, and 4) create material master records and production/purchase orders to value the stocks separately. The purpose of split valuation is to allow different valuation prices for internally produced versus externally sourced materials.
Validation checks values entered by the user and substitutes incorrect values, while substitution removes incorrect values entered by the user. Validations can be applied at the document header, line item, and master data level to check for values like company code and business area. Substitutions can also be applied at various levels to replace values like profit centers or business areas. Both validations and substitutions use user exits and can be transported between systems after configuration.
The document provides an overview of key concepts in SAP's Overhead Cost Management (OCM) module, including:
1) OCM helps plan, allocate, control, and monitor overhead costs by developing standards to control costs and value internal activities using cost centers, internal orders, and other tools.
2) Cost centers analyze where overhead occurs and costs are assigned to sub-areas where they originated, while internal orders collect and analyze costs of internal jobs and tasks.
3) Master data like cost elements, cost centers, activity types, and internal orders are used throughout the OCM processes of planning, actual posting, period closing, and reporting.
The document provides instructions on how to perform various accounting tasks in Tally.ERP 9 such as creating a company, ledger accounts, inventory items, voucher entries, and generating reports. It explains how to configure accounting features and statutory/tax settings. It also summarizes the key advantages of Tally.ERP 9 like increased audit efficiency through remote access and its limitations like lack of alerts for credit limit exceeds.
This document provides an overview of the Sales and Distribution (SD) module in SAP. It describes the core components and functions of SD including master data, sales support, sales orders, shipping, billing, and the sales organization structure. Key elements covered are materials master data, pricing, sales documents, delivery processing, invoicing, and how the sales hierarchy is organized into sales areas, offices, and groups.
Condition technique is a configuration technique in SAP used to configure complex business rules, such as pricing. It consists of several key components, including a field catalog, condition tables, an access sequence, condition types, pricing procedures, and pricing procedure determination. Condition tables contain business rules and are accessed in the order specified by the access sequence. Condition types represent logical components like taxes or discounts. Pricing procedures combine condition types and are assigned to documents like sales orders. Overall, condition technique provides a rules engine for flexibly configuring diverse and changing business rules through its various components.
The document discusses the benefits of exercise for mental health. It notes that regular physical activity can help reduce anxiety and depression and improve mood and cognitive function. Exercise has also been shown to enhance self-esteem and serve as a healthy means of stress management.
The document describes IcSoft, a business software that provides ERP and manufacturing execution system capabilities. Key features include user-defined fields, barcode support, direct data entry from devices, document management, multi-currency accounting, customizability, paperless office functionality, statistical process control, plant maintenance, and integrated reporting. The software allows for rapid implementation between 3-6 months and supports lean manufacturing practices. It provides functionality across standard business areas like sales, purchasing, inventory, quality control, and finance.
This document provides instructions for configuring stock transport orders in SAP, which allow for the physical transfer of goods between two plants or company codes. It outlines the key configuration steps, which include defining a stock transport order document type, assigning shipping data and checking rules to plants, and associating delivery types and one-step procedures with document types and plant combinations. The configurations allow goods to be transferred between plants within a company code or across company codes with delivery and optional billing.
SAP scripts can be used to design customized printing formats for documents like purchase orders and invoices. SAP scripts allows printing barcodes directly by combining it with barcode software. This document provides tips and tricks for using various SAP script commands and functions, including how to calculate totals and subtotals using subroutines, set different fonts on the same line, print footers only on the last page, and retrieve data without modifying the original program. It also discusses topics like orientations, protect/endprotect, and converting SAP script spools to PDF.
The document provides an overview of the enterprise structure for SAP accounting, human resources, sales, purchasing, and logistics modules. It outlines the default controlling areas, company codes, purchasing and sales organizations, plants, and other standard organizational units used in SAP best practices. The structure includes areas for finance, controlling, human resources, purchasing, production, distribution, and sales.
Free goods is a type of quantity discount where additional goods are provided at no extra charge when a certain purchase quantity is met. Free goods can be configured manually by specifying free item categories, or automatically where the system proposes free goods that are either exclusive, meaning the free goods quantity is excluded from the total, or inclusive, where it is included. Multiple steps must be taken to set up and activate free goods determination including creating condition tables, defining condition types, procedures, and records to control how free items are granted and priced.
A business requirement may arise making it necessary for you to move Fixed assets from one
company code to another (intercompany assets transfer for Eg: From company code XXX to YYY)
or from one organization unit to another, within the same company code (intracompany transfer).
The end to end process of fixed asset transfers involves configuration settings as well as user
frontend activities.
This posts will discuss the process of intercompany asset transfer end to end. It is assumed that the
reader has, at the very least, a basic knowledge of Asset Accounting. The complete cycle of
intercompany fixed asset transfer will include the below steps:
I. Prerequisites/ Configuration steps: (Asset accounting configuration should be
available in the system, apart from below configurations are required)
1. Creation of GL Accounts
2. Define Transfer Variants
3. Assign G/L Accounts Determination
4. Activate Inter-company postings for Asset document type (AA)
II. Intercompany Asset Transfer Steps (End User):
1. Executing an intercompany asset transfer transaction
2. Display document
3. Cross company code document display
4. Asset explorer
The document describes how to clear quantity differences between goods receipts and invoices for a purchase order using transaction code MR11 in SAP. Quantity differences result in a balance on the GR/IR clearing account. Using MR11, the user selects a purchase order, posts the difference, and an accounting document is generated. The accounting document can be displayed to view the original materials management document.
This document provides an overview of invoice verification in SAP, including the key steps and concepts. It describes the target groups, types of invoices, data required, screens used, and how to handle tasks like parking invoices, credit memos, excise invoices, devaluation, physical inventory, and retrieving inventory management information. The goal is to explain how to enter, verify, and process different types of vendor invoices correctly in SAP.
1. The document describes product allocation during sales order entry between SAP R/3 and SAP APO. It can be done with or without directly checking the planning area.
2. Key steps include creating a sales order in SAP R/3, checking availability in SAP APO which may result in a delivery proposal, and adopting the results in SAP R/3.
3. Settings must be configured in both SAP R/3 and SAP APO for the systems to communicate properly during the product allocation check.
Master data in SAP contains records that remain in the database over an extended period of time, such as material, vendor, and customer records. Material master data integrates information from different departments and contains details like material numbers, descriptions, purchasing data, and accounting information. Service master records describe services that may need to be procured and contain details like the service number, category, description, and valuation class. Master data is organized according to organizational hierarchies like clients, plants, and storage locations to prevent redundant storage and allow easy management of information.
The document summarizes the process of scheduling agreement release processing in SAP R/3. It involves 3 main steps: 1) Material requirements planning to determine delivery schedules. 2) Release generation by translating schedules into forecast (FRC) and JIT releases. 3) Output and transmission of releases as messages to vendors. Creation profiles allow customizing how releases are aggregated and generated. The system updates fields and stores releases upon output to designate them as completed.
This document provides an overview of PI sheets in SAP, which can be used to inform production operators of steps to perform. There are two types: ABAP-based and browser-based. Browser-based PI sheets are configured by defining master data like materials and BOMs, transporting standard SAP settings, creating control recipes and destinations, defining process message characteristics, assigning process instructions to recipes, releasing control recipes to generate PI sheets, and using the sheets to record operator inputs and update order data. PI sheets allow recording of various production activities and values in a flexible manner.
The document discusses the Legacy System Migration Workbench (LSMW) in SAP, which is a tool used to transfer data from non-SAP legacy systems to an SAP R/3 system. It describes the basic principles, features, and steps of using LSMW, including maintaining source structures and fields, mapping fields, importing and converting data, and displaying the results. The main steps are creating an LSMW project, mapping source and target structures and fields, importing legacy data files, and converting the data for use in SAP.
Presentation from LBSi SAP Business One User Group December 2012. Inventory Management in SAP Business One. Learn how to setup inventory and perform cycle counts.
Revamping Ticket Management System For Efficient Support Operations Powerpoin...SlideTeam
The document discusses the benefits of meditation for reducing stress and anxiety. Regular meditation practice can help calm the mind and body by lowering heart rate and blood pressure. Studies have shown that meditating for just 10-20 minutes per day can have significant positive impacts on both mental and physical health over time.
This document provides instructions for configuring and activating split valuation in SAP to separately value in-house production stocks and externally procured stocks of materials. It outlines the steps to 1) activate split valuation in the system, 2) create valuation types for in-house and external stocks, 3) assign valuation categories to the types, and 4) create material master records and production/purchase orders to value the stocks separately. The purpose of split valuation is to allow different valuation prices for internally produced versus externally sourced materials.
Validation checks values entered by the user and substitutes incorrect values, while substitution removes incorrect values entered by the user. Validations can be applied at the document header, line item, and master data level to check for values like company code and business area. Substitutions can also be applied at various levels to replace values like profit centers or business areas. Both validations and substitutions use user exits and can be transported between systems after configuration.
The document provides an overview of key concepts in SAP's Overhead Cost Management (OCM) module, including:
1) OCM helps plan, allocate, control, and monitor overhead costs by developing standards to control costs and value internal activities using cost centers, internal orders, and other tools.
2) Cost centers analyze where overhead occurs and costs are assigned to sub-areas where they originated, while internal orders collect and analyze costs of internal jobs and tasks.
3) Master data like cost elements, cost centers, activity types, and internal orders are used throughout the OCM processes of planning, actual posting, period closing, and reporting.
The document provides instructions on how to perform various accounting tasks in Tally.ERP 9 such as creating a company, ledger accounts, inventory items, voucher entries, and generating reports. It explains how to configure accounting features and statutory/tax settings. It also summarizes the key advantages of Tally.ERP 9 like increased audit efficiency through remote access and its limitations like lack of alerts for credit limit exceeds.
This document provides an overview of the Sales and Distribution (SD) module in SAP. It describes the core components and functions of SD including master data, sales support, sales orders, shipping, billing, and the sales organization structure. Key elements covered are materials master data, pricing, sales documents, delivery processing, invoicing, and how the sales hierarchy is organized into sales areas, offices, and groups.
Condition technique is a configuration technique in SAP used to configure complex business rules, such as pricing. It consists of several key components, including a field catalog, condition tables, an access sequence, condition types, pricing procedures, and pricing procedure determination. Condition tables contain business rules and are accessed in the order specified by the access sequence. Condition types represent logical components like taxes or discounts. Pricing procedures combine condition types and are assigned to documents like sales orders. Overall, condition technique provides a rules engine for flexibly configuring diverse and changing business rules through its various components.
The document discusses the benefits of exercise for mental health. It notes that regular physical activity can help reduce anxiety and depression and improve mood and cognitive function. Exercise has also been shown to enhance self-esteem and serve as a healthy means of stress management.
The document describes IcSoft, a business software that provides ERP and manufacturing execution system capabilities. Key features include user-defined fields, barcode support, direct data entry from devices, document management, multi-currency accounting, customizability, paperless office functionality, statistical process control, plant maintenance, and integrated reporting. The software allows for rapid implementation between 3-6 months and supports lean manufacturing practices. It provides functionality across standard business areas like sales, purchasing, inventory, quality control, and finance.
This document provides instructions for configuring stock transport orders in SAP, which allow for the physical transfer of goods between two plants or company codes. It outlines the key configuration steps, which include defining a stock transport order document type, assigning shipping data and checking rules to plants, and associating delivery types and one-step procedures with document types and plant combinations. The configurations allow goods to be transferred between plants within a company code or across company codes with delivery and optional billing.
Abongnwi Neba has over 7 years of experience with SAP FI/CO modules. He has expertise in configuring and implementing SAP FI modules such as general ledger, accounts payable, accounts receivable, asset accounting, bank accounting, and controlling. He also has experience with SAP BI/BW including creating data sources, info cubes, and BEX reports. Neba provides training to SAP end users and students.
This document discusses the implementation of SAP SD (Sales and Distribution) module at Shoppers' Stop chain of malls in Mumbai. It describes the master data maintained in SAP SD, various sales document types and business processes supported. Key steps in the implementation included training employees over 50 hours, running the existing and SAP systems simultaneously for 4 months, and ensuring all work was completed each day. Benefits included increased staff quality, confidence and pay over time as the company worked more efficiently, though costs were high initially.
Transforming supply chain Harish Bawari - Hero MotoCorp May 2016INDUSCommunity
The document discusses a project implemented by Hero MotoCorp to strengthen its supply chain planning through the use of information technology. The system implemented, called e-Material Flow, integrated SAP ERP with other systems to automate material flow tracking and enable real-time visibility across the supply chain. This allowed Hero to issue production plans and schedules to vendors in a more timely, consistent manner. It reduced inventory costs, line stoppages, and improved on-time delivery. Benefits also included manpower savings, increased production levels, and faster truck turnaround times.
The document discusses financial and supply chain systems for an organization. It provides an overview of current systems, including Oracle, Infoflo and Titan. It outlines objectives to integrate systems on an end-to-end basis and automate supply chain operations. The implementation strategy discusses upgrading Oracle and a multi-phase approach to integrate business processes and retire legacy systems.
The document provides a summary of qualifications for an individual with over 9 years of experience in SAP R/3, information technology, and finance. It includes details of SAP FI/CO module experience and certifications, as well as experience implementing SAP projects for various industries. Education qualifications including a Master's in Information Systems and Bachelor of Commerce are also listed. The summary highlights technical skills in SAP modules like FI, CO, SD, MM and proficiency with other tools like Microsoft Office, accounting packages, and programming languages. It also provides details of configuration experience and skills within various SAP FI/CO sub-modules. Finally, the document lists the individual's work experience across various SAP implementation, support and testing
The document contains the resume of Rasmi Ranjan Pradhan summarizing his professional experience as an SAP ABAP Technical Consultant for over 3 years, including developing reports, forms, and configuring ALE and IDOC settings. He has expertise in ABAP, RICEF, ALE, IDOCs and has worked on SAP implementations for clients in India and the US. Pradhan is looking for a role that allows him to continue growing his SAP ABAP skills and experience.
Suresh Sadasivan is a senior SAP consultant with over 16 years of experience implementing SAP SD, MM, and EDI modules. He has extensive experience leading large global SAP implementations, including developing global templates. He is proficient in all areas of the order-to-cash process, including pricing, delivery, billing, and integration with FI and other modules. He has implemented SAP solutions across various industries, such as manufacturing, consumer products, and public sector.
The document describes an enterprise architecture that connects different business units and systems through a centralized bus (BUS) architecture. It aims to improve existing processes, facilitate new capabilities, and better support acquisitions through system integration. Several candidate processes are identified for initial integration projects, including supplier quality data sharing, consolidated procurement, and expense processing. Next steps involve mapping current processes, analyzing integration opportunities, and standing up a development environment to test integration of candidate processes using service-oriented architecture components.
[CV] Denmark Santos_Financial Analyst cum Cost AccountantDenmark Santos
This document provides a summary of the candidate's SAP ERP experience and qualifications. It details their work history with various companies implementing and using SAP modules for materials management, production planning, and financial accounting. Key responsibilities included financial analysis and reporting, budgeting, inventory control, product costing, and supporting audits. The candidate has over 10 years of experience in manufacturing industries utilizing SAP.
SAP FICO Interview Questions By Garudatrainingspiyushchawala
SAP FICO is a core SAP module that covers the financial and reporting segments of a business.
It consists of the interrelated component modules-FI (Financials) and CO (Controlling) with an
extensive set of sub-modules that cover every aspect of the financial and managerial accounting
for both external and internal reporting. Skilled FICO Technical and Functional Consultants are in
very high demand as enterprises world over have been moving to SAP as a single solution for their
business needs. As financial management forms the very basis for any business, SAP FICO has seen
a consistent increase in its implementation with a very high demand for FICO professionals. Garuda
Trainings has come out with a comprehensive online training course in SAP FICO to give our students
the much needed advantage in this highly competitive and sought after segment of the ERP industry.
Online SAP FICO Course Contents: FICO is an integration of two modules FI and CO and the below
curriculum has been segmented accordingly.
Contents:
1) An Introduction to SAP
2) The FI module and its architecture
3) General Ledger Accounting
4) Fixed Assets sub-module
5) The Account Receivables sub-module
6) The Accounts Payable sub-module
7) Integration with other SAP modules and business implementation and deployment
8) The CO module and its architecture, interaction with the FI and other SAP modules
9) Cost centres and profit centres accounting
10) Internal orders and profitability
11) Product costing and activity based costing
For More Info: http://garudatrainings.com/sap-fico-online-training/
Why Choose Us: Our online course in SAP FICO gives you a perfect flexibility of pursing the
course within your existing schedule as you can opt from weekend or weekday batches as per
your convenience. The training resources are prepared by experts with rich experience in SAP
implementations. All modules are led by trainers and are interactive with a recording ability for
future use and access. We offer a 24/7 access to training resources and technical support and give
you a perfect quality training course with an extra emphasis on practical exposure to real-time
implementation scenarios and live projects.
The Complete Advantage: We endeavour to give you a perfect career as a SAP FICO consultant and
our online training course also includes the advantage of placement assistance through our industry
network. To help our users easily clear the interview evaluation, we offer an extensive collection of
in-depth interview questionnaires along with tips of effectively writing resumes. Choose us to get
the perfect advantage in your career as an SAP FICO consultant.
Register For Free Demo:
www.Garudatrainings.com
Email Us:garudatrainings@gmail.com
Ph No:+1-508-841-6144
Gopi Shankar is a SAP MM/WM consultant with over 10 years of experience implementing SAP MM, WM, and EWM modules. He has extensive experience working for companies like IBM, Computer Sciences Corporation, and directly with clients like Johnson Matthey and Coca-Cola Enterprises Europe. Gopi has led implementations, provided support, and trained end users. He is proficient in all aspects of the procurement lifecycle from strategic sourcing and purchasing to inventory management, warehousing, and logistics. Gopi holds a Bachelor's degree in Mechanical Engineering and is SAP MM certified.
- The document provides a summary of the professional experience and qualifications of Gunavathi K. P., including over 10 years of experience in database design, development, and implementation using technologies like MS SQL Server, VB.Net, and .Net.
- Key responsibilities included leading database development projects, designing user interfaces, database administration tasks, and performance tuning. Experience covered the full software development lifecycle from requirements to delivery.
- Recent projects included developing a cloud-based application for insurance claims processing using .Net and SQL Server, and upgrading older VB6 applications to .Net while retaining the SQL Server database.
This document discusses various data analytics projects for a telecom company in India including:
1) Creating a robust data mart by mapping data from Oracle, call records, and recharge data to track customer origination and performance.
2) Creating daily, monthly, and yearly business reports on metrics like ARPU, RPM through Excel pivots, charts and formulas using summarized extract data.
3) Preparing regular reporting and dashboards in Qlikview with drilldown capabilities for easy access to business insights.
Sreenivasan R has over 10 years of experience in SAP MM and ERP implementations. He has worked as a consultant for SAP MM modules and implemented ERP systems like NOW and TIM for various textile and manufacturing companies. He is proficient in procurement, inventory management, and order processing. Currently, he works as a SAP Business Analyst for Milacron LLC providing global support for their SAP system.
The document summarizes British American Tobacco's (BAT) upgrade of their PeopleSoft payroll system from version 9.1 to 9.2. Key points include:
- BAT brought payroll processing in-house in 2003 and implemented PeopleSoft Global Payroll in 2004.
- In 2013, BAT decided to upgrade from 9.1 to 9.2 to remain supported and evaluate new functionality. Cedar Consulting managed the upgrade project.
- The upgrade went live successfully in December 2013. It addressed issues with court orders processing and allowed BAT to use new features like positive input templates and employee loans.
- Parallel testing showed the payroll results matched between the old and upgraded systems. The upgrade future-
Best Practice: Automating Cash Flow in Hyperion Financial ManagementEmtec Inc.
Automating the statement of cash flows in Hyperion Financial Management requires a number of design considerations. This presentation takes a consultant’s perspective of the design and implementation of cash flow automation including best practices. View the full presentation at the Emtec Event Archive.
- Rohit Kumar is a DW/BI developer with over 5 years of experience developing data warehouse and BI reporting solutions for clients in various domains including banking, finance, insurance, and research.
- He has extensive experience designing and implementing ETL processes using tools like SAP BODS and Talend to extract, transform, and load data from various source systems into data warehouses.
- He also has experience designing BI universes and reports using tools like SAP BO and Microstrategy and providing reporting solutions, training, and support to clients.
Macroeconomics- Movie Location
This will be used as part of your Personal Professional Portfolio once graded.
Objective:
Prepare a presentation or a paper using research, basic comparative analysis, data organization and application of economic information. You will make an informed assessment of an economic climate outside of the United States to accomplish an entertainment industry objective.
This presentation includes basic of PCOS their pathology and treatment and also Ayurveda correlation of PCOS and Ayurvedic line of treatment mentioned in classics.
A workshop hosted by the South African Journal of Science aimed at postgraduate students and early career researchers with little or no experience in writing and publishing journal articles.
How to Fix the Import Error in the Odoo 17Celine George
An import error occurs when a program fails to import a module or library, disrupting its execution. In languages like Python, this issue arises when the specified module cannot be found or accessed, hindering the program's functionality. Resolving import errors is crucial for maintaining smooth software operation and uninterrupted development processes.
This slide is special for master students (MIBS & MIFB) in UUM. Also useful for readers who are interested in the topic of contemporary Islamic banking.
How to Add Chatter in the odoo 17 ERP ModuleCeline George
In Odoo, the chatter is like a chat tool that helps you work together on records. You can leave notes and track things, making it easier to talk with your team and partners. Inside chatter, all communication history, activity, and changes will be displayed.
How to Build a Module in Odoo 17 Using the Scaffold MethodCeline George
Odoo provides an option for creating a module by using a single line command. By using this command the user can make a whole structure of a module. It is very easy for a beginner to make a module. There is no need to make each file manually. This slide will show how to create a module using the scaffold method.
How to Manage Your Lost Opportunities in Odoo 17 CRMCeline George
Odoo 17 CRM allows us to track why we lose sales opportunities with "Lost Reasons." This helps analyze our sales process and identify areas for improvement. Here's how to configure lost reasons in Odoo 17 CRM
Assessment and Planning in Educational technology.pptxKavitha Krishnan
In an education system, it is understood that assessment is only for the students, but on the other hand, the Assessment of teachers is also an important aspect of the education system that ensures teachers are providing high-quality instruction to students. The assessment process can be used to provide feedback and support for professional development, to inform decisions about teacher retention or promotion, or to evaluate teacher effectiveness for accountability purposes.
Assessment and Planning in Educational technology.pptx
Mm
1. When a goods receipt or invoice has been posted against a purchasing document, the quantities and values will be
distributed among the opened quantities of the existing schedule lines of the purchasing document. The opened
quantity of a schedule line is the difference between the quantity ordered and the quantity already assigned to this
schedule line.
The creation date of the schedule line - EKET-BEDAT and the system date when the goods receipt/invoice has
been entered; EKBE-CPUDT, have an important role during the quantity distribution process in the purchasing
statistics.
The creation date of the schedule line (EKET-BEDAT) is important because new schedule lines (EKET) can be
created at any moment in the purchasing document and it's also possible to create a schedule line with a delivery
date (EKET-EINDT) in the past or in the future. The entry date of the goods receipt/invoice (EKBE-CPUDT) is
important because you can post this document with a posting date that is not the same as the entry date. (In the past
or in the future). In order to make a correct distribution and to avoid that during the reconstruction process ( OLI3 -
RMCENEUA ) the distribution changes, before assigning the goods receipt/invoice quantity to a schedule line,
system first check if at the moment that a goods receipt/invoice has been posted, a schedule line has been already
created:
EKBE-CPUDT >= EKET-BEDAT
Since the creation date of the schedule line is not displayed in the purchasing document (only the delivery date) and
also the entry date of the goods receipt/invoice (only the posting date), it's normal that system assign the goods
receipt quantity in a way different than you are expecting.
In order to better understand the quantity distribution process, please always check the relevant dates:
EKET-BEDAT
EKBE-CPUDT
Example of distribution process:
1) A purchasing document has been created with the following schedule lines:
(EKET-BEDAT) (EKET-EINDT)
Creation date Delivery date Quantity Quantity received
01.04 01.04 10 0
01.04 10.04 10 0
a) For this document a goods receipt with quantity 15 is posted on 05.04 (EKBE-CPUDT) with posting date 05.04
(EKBE-BUDAT). The distribution result is the following:
Creation date Delivery date Quantity Quantity received
01.04 01.04 10 10
01.04 10.04 10 5
As you can check both schedule lines were created before the goods receipt has been posted. For this reason, it’s
possible to assign the quantity to both schedule lines.
b) A new goods receipt wit quantity 10 is posted on 20.04 (EKBE-CPUDT) with posting date 20.04 (EKBE-
BUDAT). The distribution result is the following:
Creation date Delivery date Quantity Quantity received
01.04 01.04 10 10
01.04 10.04 10 15
In this case there is an over delivery in the last schedule line.
2. c) For this purchasing document a new schedule line has been created
Creation date Delivery date Quantity Quantity received
01.04 01.04 10 10
01.04 10.04 10 15
21.04 15.04 5 0
You may expect a new distribution of the goods receipt quantity, but this will not occur as the schedule line has
been created after the goods receipt document has been entry in the system.
EKBE-CPUDT < EKET-BEDAT
20.04 < 21.04
2) A purchasing document has been created with the following schedule lines:
Creation date Delivery date Quantity Quantity received
01.04 01.04 10 0
01.04 10.04 10 0
a) For this document a goods receipt with quantity 15 is posted on 05.04 (EKBE-CPUDT) with posting date 05.04
(EKBE-BUDAT)
The distribution result is the following:
Creation date Delivery date Quantity Quantity received
01.04 01.04 10 10
01.04 10.04 10 5
As you can check both schedule lines were created before the goods receipt has been posted. For this reason is
possible to assign the quantity to both schedule lines.
b) A new goods receipt wit quantity 20 is posted on 15.04 (EKBE-CPUDT) with posting date 25.04 (EKBE-
BUDAT)
The distribution result is the following:
Creation date Delivery date Quantity Quantity received
01.04 01.04 10 10
01.04 10.04 10 25
The last schedule line will be overdelivered.
It's possible to assign the goods receipt quantity to the last schedule line, because the goods receipt has been posted
after the creation of the last schedule line.
c) For this purchasing document a new schedule line has been created on 20.04 (EKET-BEDAT) with delivery
date 20.04 (EKET-EINDT) and order quantity 10
Creation date Delivery date Quantity Quantity received
01.04 01.04 10 10
01.04 10.04 10 25
20.04 20.04 10 0
3. You may expect the last goods receipt quantity to be assign to the new created schedule line, but this will not
happen because the schedule line has been created after the goods receipt document has been entry in the system.
It doesn't matter that the posting date of the goods receipt is greater than the schedule line creation date. The check
is made with the entry date of the goods receipt against the creation date of the schedule line.
EKBE-CPUDT < EKET-BEDAT
15.04 < 20.04
http://www.saptechies.org/distribution-quantities-against-schedule-lines/
kumar Arza
SAP SD/MM Consultant at GE Transportation
➢ Total of 11 years of extensive experience in the field of Materials Management, this includes experience in project analysis,
customization and Implementation of SAP R/3 MM Module.
➢ Involved 3 full life cycle implementation projects and also involved in SAP MM support and maintenance projects.
➢ Expert in Gap-Analysis - As Is/To Be, business blue printing, prototyping, detailed configuration, training, documentation,
testing, data uploading, go-live implementation, after go-live support.
➢ Worked in MM areas of Inventory management, Purchasing, subcontracting, third-party, consignment, External
Procurement- Stock transports, requisitions, service entry, info records, release strategies, vendor evaluation, master
records.
Databases: Oracle 8.x, 9i, Oracle 10g, Sybase, Teradata, PowerBuilder,
DB2, SQL Server 2k, 2005, Netezza.
ERP: Oracle Applications (GL, AR, AP, OE, SCM OM, INV)
BOM, PO, iProcurement (Rel. 10.7, 11.i,), SAP Ecatt 6.x, SAP (FI, CO,
SD, MM, WM)
BI Report Tools: OBIEE10.x, 11.g, BO (Business Objects) XI.R2, BO XI R3, Crystal
Reports 8.x /9.x/10, Crystal Xcelsius, SQR, Discoverer 4.i, 9.i,
Power Analyzer, Hyperion, Siebel Analytics 7.x, 2, 8.x, 9.x,
Microstrategy7.5.2, 8.x, Cognos 7.x, 8.x, SAP BO XI 3.x.
ETL TOOLS: Ab Initio GDE, 1.13, 1.14, 1.15, Data Stage 6.x, 7.x, Micro Strategy 7
(Narrowcast Server), Informatica 8.x/7.x, SAP BW/BI.
Front End Tools: Designer/2000, 6.x, Forms 4.5, 6.x, Reports 2.5, 6.x, Visual Basic 6.0,
.NET, Erwin, Toad, SQL Navigator, ColdFusion, Visual Studio.
Testing Tools: HP Win runner7.x/8.0,9.x,Load Runner7.x, 9.x, HP Quality Center
TestDirector7.x/8.0,9.x, Silk, Caliber RM, Rational Suite (Clear Quest,
Clear Case), Quick Test Pro (QTP), JMeter, Sox (Risk Navigator).
Work Experience
SAP SD/MM Consultant
GE Transportation
-
Erie, PA
September 2010 to Present
Responsibilities: • Configured the Materials Management module such as defining and assigning various components of the
company and material master data, info records, source lists, purchasing and inventory management.
• Set up plant parameters for inventory management, tolerance limits on goods issues and receipts.
• Customized plant parameters for MRP and consumption based planning and defined MRP groups and controllers.
• Customized the conversion of purchase request to purchase orders.
• Configured Inter and Intra company stock transfer.
• Configured goods receipt and issue for all stock categories and special stocks viz. consignment, third party and sub-
4. contracting.
• Assisted technical team to develop interface for inventory movements with SAP and other legacy systems.
• Setup creation of outline agreements - scheduling (delivery/forecast delivery) and contracts (Value/quantity based).
• Post Go-Live support for inventory transactions coming from legacy system through IDocs for Purchase Order, creating
Inbound/Outbound delivery, shipments, trouble shoot and fixed failed IDocs.
• Carried out unit testing and integration testing with all possible business scenarios.
• Communicated status, issues and impacts to business team leadership, relevant client sponsors and process owners.
• Post Go-Live support, prepared training documents and trained end users.
SAP MM/SD Consultant
JHUAPL - Medical Research Center , Baltimore, MA
January 2007 to August 2010
Responsibilities: • Study of business processes, process mapping and preparation of ready-to-use templates.
• Defined plants, purchase organization and storage locations, assigned purchasing organization to company codes and
plants, assigned plants to company code.
• Customized new material types and material groups and assigned number ranges for new material types.
• Managed master data for Material Master, Vendor Master, Customer Master, Info Records, Source Lists, and BOMs.
• Performed configuration enhancements for MM module (Purchasing, Inventory Management, Physical Inventory, and
Invoice Verification) to meet the Business needs for the plant.
• Worked on GI/GR for Purchase Orders, Sales Orders, Stock transport orders, Inbound and Outbound deliveries.
• Configured the Inter & Intra company stock transfer and handling of special stocks and special procurement types like Sub-
contracting, and Consignment.
• Configured Logistics invoice verification with over and under limits, and established ERS (Evaluated Receipt S ettlement) for
preferred vendors.
• Monitor IDOC failures and supported resolution process.
• Configured Shipping Point determination and Route determination.
• Defined various Sales Order types such as standard sales order, sample orders, rush orders, contracts etc.
• Configured Item categories and Schedule Line Categories for sales order, delivery and etc.
• Worked with ABAP/4 programmers to develop new structure of custom reports.
• Prepared Change Request which included functional specs and ensured that the transport was moved across other
environments.
• Performed unit testing and integration testing for custom transactions.
• Worked with end users and prepared training material for Purchasing and Inventory Management process.
• Provided support and solved user issues, ensured configuration changes and ABAP development activities to fulfill the
requirements.
SAP MM Implementation Consultant
JHUAPL - Medical Research Center , Baltimore, MA
-
Washington, DC
December 2008 to June 2010
Responsibilities: • Responsible for full cycle implementation of MM module: project preparation, business blueprint, realization,
final preparation and finally go live & support using ASAP methodology.
• Prepared a detailed document of AS-IS study and developed the detailed TO-BE processes to suit the company's
objectives.
• Set up of organization structure related to MM & their respective assignments.
• Configured the Material Master Data (material groups, material types, field selection groups) and Vendor Master Data (field
status for vendor account groups, partner determination schema, account groups, partner functions).
• Invovled in data migration of material data from legacy to SAP R/3 system.
• Carried out split valuation of materials based on valuation category.
• Configured the Inventory Management of goods at the points of receipt and issue for all stock categories and special stocks
viz. consignment, pipeline, stock transfers, returnable transport packaging, third-party and sub-contracting.
• Verified Materials Management module configuration with populating data for complete business cycle by generating PR,
RFQ/Quotation, vendor evaluation, ranking list, contracts, scheduling agreements, PO, GR/GI, invoice verification and
purchase info records.
• Mapping and customizing the price determination process by using condition techniques.
• Involved in interfacing and integration of MM with IM, SD, WM and FI/CO modules.
5. • Configured and utilized movement types, cycle counting in the physical inventory, and posting the cycle count variance.
• Performed Unit Testing and Integration Testing.
• Designed and coordinated post implementation support.
• Demonstrated various MM transactions and business scenarios for the users as a part of end
user training & created detailed user documentation.
SAP MM Implementation Consultant
Eli Lilly and Company
-
Indianapolis, IN
May 2006 to November 2008
Responsibilities: • Involved in customizing of Materials Management module.
• Finalizing of organizational structure of Business processes to be integrated with SAP system.
• Responsible for customization of MM Module and Integration between various modules.
• Presentation of TO-BE processes to the steering committee.
• Customizing of Master data like Material Master, Vendor master, BOM, Work centers, Routings.
• Core Member for Data Conversion, testing and execution process.
• Configuration of Purchasing documents, PR/ RFQ/ quotation entry / PO/ confirmations, release procedures.
• Defined number ranges for various documents & setup up document Release procedures.
• Creating Outline agreements - scheduling delivery/forecast delivery, contracts-value/quantity based.
• Establishing the whole procurement Cycle from automatic creation of Requisitions from MRP run to invoice verification.
• Configuration of Goods movement documents for GR / Issues / Stock Transfers / Transfer Postings & handling of
consignment stocks.
• Co-ordination with other modules for integration, Account determination for materials management with finance.
• Worked with OSS notes related to system problems and coordinated with technical team to implement those notes.
SAP MM/IM Consultant
Maytag
-
Nashville, TN
December 2003 to April 2006
Responsibilities: • Studying existing business process in the context of material management and deciding TO-BE process
and to be mapped to the SAP system.
• Set up of Enterprise Structure related to MM like creating storage locations and Purchasing Organizations.
• Assigned purchasing organizations to company codes and plants.
• Configured new material types as per requirements of client and created several valuation classes and account category
references.
• Involved in data mapping and data migration of master data and condition records.
• Configured Purchasing Process including RFQ/Quotation, Contract, Scheduling Agreement, Purchase Requisition, Purchase
Order and special procurement processes.
• Created Functional Specification documents along with process flow.
• Worked extensively on Release strategy for Purchasing Documents.
• Defining number ranges for various documents like Purchase order, Purchase requisition etc.
• Worked extensively on Stock Transport Order and Stock Transfer.
• Configured price determination schema defined condition types with access sequences, calculation schemas and condition
tables.
• Involved in the Unit Testing & Integration testing.
• Involved deeply with client interaction & also handled the task of training power users and end user training. Also worked on
documentation for power users and end users.
• Involved in Post go-live production support
SAP MM Consultant
Maruti Udyog Pvt. Ltd
6. September 2000 to September 2003
Responsibilities: • Involved in the live implementation of SAP R/3.
• Configuring master data. e.g., Material master, Bill of Materials, work centers.
• Developing an Interactive list for plant wise purchase requisitions.
• Customizing different purchasing documents such as PR, RFQ and POs. Preparation of contracts, scheduling agreements,
quota arrangements, external service management, release procedures and pricing conditions. Prepared the user documents
for the MM module, giving presentation and demos.
• Trained to the users executives about the working of MM module and collecting feedback.