This document provides instructions for configuring VAT in SAP for an organization called TAXINN. It involves 12 steps to configure the customer master, define new condition types, define accounts, include tables, change pricing procedures, create new document types, number ranges, and billing types. It also provides 8 steps for MM configuration, including creating condition types, transaction keys, defining accounts, and changing tax procedures. Finally, it discusses customizing related to migrating from business place to section code for extended withholding tax in SAP.
This document provides instructions for configuring tax collected at source (TCS) in SAP. It outlines 9 steps to define TCS keys and types, create access sequences and condition types, assign GL accounts, and add TCS conditions to pricing procedures in order to calculate, report, and post TCS for sales documents. The configuration ensures TCS is handled correctly in both sales and distribution (SD) and financial accounting (FI).
This document provides a functional specification for a new GST purchase register report (ZMMPRG) in SAP. The specification includes:
1. Justification for the new report to capture additional fields required under the GST regime.
2. Details of the business requirements including a flow diagram and description of the operational requirements. It outlines 16 new fields to be added to an existing report and the logic to retrieve data for each field from various SAP tables.
3. Information on the conversion including tables and fields involved, input screen mapping, validation and error handling requirements.
4. Details for testing including sample test cases and sign-off procedures.
The specification provides a comprehensive description of
Create an asset through finance T-Code AS01 by entering the acquisition value and planned depreciation. The asset can be directly sold through finance or using a sales order to capture excise or generate an invoice. To sell using a sales order, create a non-valuated material code for the asset with an asset account assignment group. Then create a sales order, upload stock, create a delivery, invoice, excise invoice, and retire the asset using T-Code ABAON to check the financial impact.
This document provides instructions for configuring taxation procedures in SAP from TAXINJ to TAXINN. Key steps include:
1. Assigning the TAXINN tax procedure at the country level in SPRO.
2. Configuring TAXINN and maintaining excise defaults.
3. Classifying condition types for excise determination.
4. Converting formula-based pricing procedures to condition-based by removing tax routines.
5. Assigning access sequences for excise condition types and maintaining total excise condition types.
6. Defining tax determination rules and tax relevancy for customer and material master records.
The document discusses the configuration of withholding tax in SAP for a company in India. It describes defining tax keys, tax types, recipient types, tax codes, and assigning them to vendors based on the applicable tax rates for section 194C (1% for HUF/Individual, 2% for others), 194I (2% for plant/machinery rent, 10% for land/building/furniture rent), and 194J (10% professional/technical fees). It also discusses creating a general ledger account for taxes payable and assigning exemptions to vendors if total annual payments are below certain thresholds.
This document provides an overview of how SAP solutions can be configured for Goods and Services Tax (GST) compliance in India. It discusses master data setup, tax configuration, document numbering, business transactions for procurement, sales, and pricing. Key areas covered include tax registration numbers, classification of customers, vendors, materials and services, configuration of tax condition types for intra-state, inter-state, import and export transactions, and pricing procedures.
Text determination, account determination, partner determination, output determination, and storage location determination are used to transfer information throughout the order and delivery process. Account determination specifically maintains fields like sales organization, distribution channel, chart of accounts, and account assignment groups. Pricing determination calculates prices based on various factors like sales area, document type, and customer, with different pricing procedures controlling factors like condition types. A support consultant would maintain reports related to any issues customers are facing.
as per my experinece i have prepared this docuemnt for future referenec and also this document will help to leart GST impact in SAP SD and S4 HANA
Kindly comment your feedback and suggistions
This document provides instructions for configuring tax collected at source (TCS) in SAP. It outlines 9 steps to define TCS keys and types, create access sequences and condition types, assign GL accounts, and add TCS conditions to pricing procedures in order to calculate, report, and post TCS for sales documents. The configuration ensures TCS is handled correctly in both sales and distribution (SD) and financial accounting (FI).
This document provides a functional specification for a new GST purchase register report (ZMMPRG) in SAP. The specification includes:
1. Justification for the new report to capture additional fields required under the GST regime.
2. Details of the business requirements including a flow diagram and description of the operational requirements. It outlines 16 new fields to be added to an existing report and the logic to retrieve data for each field from various SAP tables.
3. Information on the conversion including tables and fields involved, input screen mapping, validation and error handling requirements.
4. Details for testing including sample test cases and sign-off procedures.
The specification provides a comprehensive description of
Create an asset through finance T-Code AS01 by entering the acquisition value and planned depreciation. The asset can be directly sold through finance or using a sales order to capture excise or generate an invoice. To sell using a sales order, create a non-valuated material code for the asset with an asset account assignment group. Then create a sales order, upload stock, create a delivery, invoice, excise invoice, and retire the asset using T-Code ABAON to check the financial impact.
This document provides instructions for configuring taxation procedures in SAP from TAXINJ to TAXINN. Key steps include:
1. Assigning the TAXINN tax procedure at the country level in SPRO.
2. Configuring TAXINN and maintaining excise defaults.
3. Classifying condition types for excise determination.
4. Converting formula-based pricing procedures to condition-based by removing tax routines.
5. Assigning access sequences for excise condition types and maintaining total excise condition types.
6. Defining tax determination rules and tax relevancy for customer and material master records.
The document discusses the configuration of withholding tax in SAP for a company in India. It describes defining tax keys, tax types, recipient types, tax codes, and assigning them to vendors based on the applicable tax rates for section 194C (1% for HUF/Individual, 2% for others), 194I (2% for plant/machinery rent, 10% for land/building/furniture rent), and 194J (10% professional/technical fees). It also discusses creating a general ledger account for taxes payable and assigning exemptions to vendors if total annual payments are below certain thresholds.
This document provides an overview of how SAP solutions can be configured for Goods and Services Tax (GST) compliance in India. It discusses master data setup, tax configuration, document numbering, business transactions for procurement, sales, and pricing. Key areas covered include tax registration numbers, classification of customers, vendors, materials and services, configuration of tax condition types for intra-state, inter-state, import and export transactions, and pricing procedures.
Text determination, account determination, partner determination, output determination, and storage location determination are used to transfer information throughout the order and delivery process. Account determination specifically maintains fields like sales organization, distribution channel, chart of accounts, and account assignment groups. Pricing determination calculates prices based on various factors like sales area, document type, and customer, with different pricing procedures controlling factors like condition types. A support consultant would maintain reports related to any issues customers are facing.
as per my experinece i have prepared this docuemnt for future referenec and also this document will help to leart GST impact in SAP SD and S4 HANA
Kindly comment your feedback and suggistions
This document outlines the key activities and checks needed for a successful cut-off procedure and go-live of a new SAP system. It discusses:
1) Pre-go live activities like master data loading, cost center planning, and product costing runs.
2) Pre-go live checks like customizing, number ranges, and operating concern setup.
3) Transaction data upload including purchase orders, stock, receivables, payables, assets, and general ledger balances.
The goal is to provide a comprehensive guide to migrating accurately from the old to new system on the planned go-live date.
This document provides guidance on configuring and executing the subcontracting process for GST compliance in India. It discusses:
1. Required master data configuration including assigning a sales area to the supplying plant, maintaining the subcontractor as a customer, and creating new billing document types.
2. Configuring views and pricing procedures for subcontracting billing.
3. Executing the subcontracting cycle with challan using transactions J1IGSUBCON and J1IGRECON for reconciliation.
4. Potential errors in J1IGSUBCON and resolutions.
Functional spcification doc for vendor debit memo reportLokesh Modem
The document describes a new vendor debit memo report that will be developed for SAP. The report will display information for vendor debit memos including plant, vendor, MIRO document number, document type, quantities, tax values, and totals. Selection criteria include plant, vendor, and date ranges. The report logic will retrieve document information from various SAP tables and sort it according to selection criteria.
This document provides a functional specification for a TDS Report that will display vendor names along with PAN numbers, which is not available in the standard SAP report. It outlines 8 steps to retrieve the necessary data from various tables, including vendor information from BSEG and LFA1, PAN numbers from J_1IMOVEND, and tax details from WITH_ITEM and T059Z. The report will be generated in Excel format to meet the client's requirement.
The document provides steps for completing the asset closing process in SAP. It includes checking the last closed fiscal year, reconciling asset and accounting data, recalculating depreciation, executing depreciation and periodic postings, reconciling the general and subsidiary ledgers, performing the fiscal year change, and executing the year-end closing program. The asset closing process closes the fiscal year for asset accounting and accounting purposes and prepares the data for the new fiscal year.
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.
This document provides an introduction to the Dynamic Item Processor (DIP) in SAP. The DIP is used to process cost- or quantity-based data between cost accounting and sales. Key applications include resource-related billing, results analysis, quotations for service orders, and pricing for projects. The document covers business processes, technical processes, customizing, and enhancements using customer exits. It also describes differences between SAP releases and the conversion from the old to new resource-related billing functionality.
The document provides steps to configure stock transfers for GST compliance in SAP, including capturing GSTIN in vendor/customer masters, creating an info record, setting up a new billing document type, configuring pricing and copy control, classifying condition types, and maintaining business place-wise GL determination. It also discusses resolving common errors in the J_1IG_INV transaction for stock transfer inbound invoices.
This document provides an overview of the SAP system and its key components. It discusses the enterprise structure in SAP which includes the highest level organizational units like company and company code. It also describes other important organizational units like sales organization, distribution channel, and division. The document explains the relationships between these different organizational units. Furthermore, it provides an introduction to master data in SAP including organizational data, customer and material master data, and document master data. It also discusses some important transaction codes and customizing tools in SAP.
This document provides an overview and instructions for configuring cost center accounting in SAP. It includes steps for setting up the organizational structure, creating cost centers, cost element groups, and assigning expense accounts to cost centers. The document also describes how to automatically generate primary cost elements from chart of accounts data and configure number ranges for controlling documents. This configuration will enable tracking of costs by cost center in the SAP system.
1. The document discusses various sales order and distribution related concepts in SAP SD including drop shipments, sales areas, picking locations, customization vs configuration, shipping points, smart forms, sales document structure, plant determination, billing without delivery, sales deals, pricing date, account groups, item categories, project IMG, extending materials and customers to other sales areas, multiple deliveries, EDI usage, copy controls, schedule line categories, blocking sales documents, reconciliation vs normal accounts, access sequences, types of free goods, the 16 steps in a pricing procedure, differences between plants and storage locations, the sales order cycle, and the relationship between sales organizations and company codes.
2. It also provides explanations for concepts
1. The document describes a request for a functional specification (spec) for a new sales tax report. The spec would include business requirements, data needs, and processing logic to guide development.
2. A functional spec provides details on user inputs, outputs, and how the application should work. It streamlines development by informing programmers of the user experience design.
3. This spec example outlines sections for a report definition, functional requirements, processing logic, and output format. It describes needed fields, tables, and the report flow to retrieve the required data.
Automatic Vendor payment advice notes by email with attachment when a payment is made via APP (Automatic payment program by using T-code F110 and email a sap script form as a PDF attachment along with the mail body in the desired language.
The document provides an overview of new features and changes being introduced in New Asset Accounting in SAP S/4HANA. Key points include: depreciation is now posted per asset rather than in aggregate; reconciliation between FI and AA is integrated by design; a technical clearing account is used for asset acquisition postings; the migration process involves customizing, moving legacy data to the SAP Simple Finance add-on, and activating the new accounting functionality. Various transactions and programs from the previous asset accounting are no longer available.
This document provides instructions for configuring automatic postings in an ERP system for inventory management and invoice verification transactions. Key steps include defining valuation levels, charts of accounts, valuation grouping codes, valuation classes, and account groupings. The system can then simulate postings to automatically determine the correct GL accounts based on these definitions and the transaction type. Definitions must be made for each chart of accounts and valuation grouping code combination.
This document provides instructions for configuring profitability analysis in SAP. It discusses defining characteristics and value fields, which are the key dimensions and values used to analyze profitability. Characteristics can be predefined, fixed, copied from reference tables, or custom defined. Instructions are provided for viewing existing characteristics, creating new user-defined characteristics like "Bill to party" and "Business field", and activating the new characteristics for use. The document outlines the overall profitability analysis configuration process and provides a guide to setting up the necessary master data and structures.
This document provides instructions for testing and debugging IDOCs in SAP. It describes transactions for processing inbound and outbound IDOCs (WE12, WE16, WE17, BD87, BD88), editing IDOC data (WE19, WE02, WE05), and reprocessing IDOCs (BD87). Detailed steps are provided for using WE19 to test inbound IDOCs by function module or standard processing, and to edit IDOC segments. The differences between processing options in WE19 are also summarized.
This document provides instructions for configuring SAP Cash Management. It discusses activating Cash Management in the company code, defining basic settings like value date defaults and source symbols, maintaining required master data, structuring the Cash Management setup by defining account names and groupings, and configuring liquidity forecasting, bank accounting, and cash concentration features. The document is a guide for SAP consultants to customize and implement Cash Management functionality in SAP.
The document discusses availability check configuration in SAP. Key points:
- Availability check verifies stock availability when creating sales orders.
- It can be configured using availability check groups, checking rules, and scope of check parameters.
- Configuration includes options like considering safety stock, stock in transit, blocked stock, and open purchase orders and sales requirements.
- Backorder processing allows assigning quantities from cancelled low priority orders to new high priority orders if stock is unavailable. It requires individual requirements to be set for the material.
This document appears to be a record of transactions for commodities and stocks made between November 6th and 27th. It includes details of the script/stock, transaction date, buy/sell indicator, buy and sell rates, profits/losses for each transaction, and running totals of profits. The transactions resulted in a total profit of Rs. 138,850 over the period according to the document.
The Controlling module in SAP provides management with supporting information for planning, reporting, and monitoring business operations. It includes components like cost element accounting, cost center accounting, internal orders, activity-based costing, product cost controlling, profitability analysis, and profit center accounting. Maintaining controlling areas and number ranges are important setup steps in the Controlling module configuration. A controlling area can include one or multiple company codes that use the same chart of accounts. Number ranges need to be defined for controlling documents like cost centers, internal orders, and product cost estimates.
This document outlines the key activities and checks needed for a successful cut-off procedure and go-live of a new SAP system. It discusses:
1) Pre-go live activities like master data loading, cost center planning, and product costing runs.
2) Pre-go live checks like customizing, number ranges, and operating concern setup.
3) Transaction data upload including purchase orders, stock, receivables, payables, assets, and general ledger balances.
The goal is to provide a comprehensive guide to migrating accurately from the old to new system on the planned go-live date.
This document provides guidance on configuring and executing the subcontracting process for GST compliance in India. It discusses:
1. Required master data configuration including assigning a sales area to the supplying plant, maintaining the subcontractor as a customer, and creating new billing document types.
2. Configuring views and pricing procedures for subcontracting billing.
3. Executing the subcontracting cycle with challan using transactions J1IGSUBCON and J1IGRECON for reconciliation.
4. Potential errors in J1IGSUBCON and resolutions.
Functional spcification doc for vendor debit memo reportLokesh Modem
The document describes a new vendor debit memo report that will be developed for SAP. The report will display information for vendor debit memos including plant, vendor, MIRO document number, document type, quantities, tax values, and totals. Selection criteria include plant, vendor, and date ranges. The report logic will retrieve document information from various SAP tables and sort it according to selection criteria.
This document provides a functional specification for a TDS Report that will display vendor names along with PAN numbers, which is not available in the standard SAP report. It outlines 8 steps to retrieve the necessary data from various tables, including vendor information from BSEG and LFA1, PAN numbers from J_1IMOVEND, and tax details from WITH_ITEM and T059Z. The report will be generated in Excel format to meet the client's requirement.
The document provides steps for completing the asset closing process in SAP. It includes checking the last closed fiscal year, reconciling asset and accounting data, recalculating depreciation, executing depreciation and periodic postings, reconciling the general and subsidiary ledgers, performing the fiscal year change, and executing the year-end closing program. The asset closing process closes the fiscal year for asset accounting and accounting purposes and prepares the data for the new fiscal year.
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.
This document provides an introduction to the Dynamic Item Processor (DIP) in SAP. The DIP is used to process cost- or quantity-based data between cost accounting and sales. Key applications include resource-related billing, results analysis, quotations for service orders, and pricing for projects. The document covers business processes, technical processes, customizing, and enhancements using customer exits. It also describes differences between SAP releases and the conversion from the old to new resource-related billing functionality.
The document provides steps to configure stock transfers for GST compliance in SAP, including capturing GSTIN in vendor/customer masters, creating an info record, setting up a new billing document type, configuring pricing and copy control, classifying condition types, and maintaining business place-wise GL determination. It also discusses resolving common errors in the J_1IG_INV transaction for stock transfer inbound invoices.
This document provides an overview of the SAP system and its key components. It discusses the enterprise structure in SAP which includes the highest level organizational units like company and company code. It also describes other important organizational units like sales organization, distribution channel, and division. The document explains the relationships between these different organizational units. Furthermore, it provides an introduction to master data in SAP including organizational data, customer and material master data, and document master data. It also discusses some important transaction codes and customizing tools in SAP.
This document provides an overview and instructions for configuring cost center accounting in SAP. It includes steps for setting up the organizational structure, creating cost centers, cost element groups, and assigning expense accounts to cost centers. The document also describes how to automatically generate primary cost elements from chart of accounts data and configure number ranges for controlling documents. This configuration will enable tracking of costs by cost center in the SAP system.
1. The document discusses various sales order and distribution related concepts in SAP SD including drop shipments, sales areas, picking locations, customization vs configuration, shipping points, smart forms, sales document structure, plant determination, billing without delivery, sales deals, pricing date, account groups, item categories, project IMG, extending materials and customers to other sales areas, multiple deliveries, EDI usage, copy controls, schedule line categories, blocking sales documents, reconciliation vs normal accounts, access sequences, types of free goods, the 16 steps in a pricing procedure, differences between plants and storage locations, the sales order cycle, and the relationship between sales organizations and company codes.
2. It also provides explanations for concepts
1. The document describes a request for a functional specification (spec) for a new sales tax report. The spec would include business requirements, data needs, and processing logic to guide development.
2. A functional spec provides details on user inputs, outputs, and how the application should work. It streamlines development by informing programmers of the user experience design.
3. This spec example outlines sections for a report definition, functional requirements, processing logic, and output format. It describes needed fields, tables, and the report flow to retrieve the required data.
Automatic Vendor payment advice notes by email with attachment when a payment is made via APP (Automatic payment program by using T-code F110 and email a sap script form as a PDF attachment along with the mail body in the desired language.
The document provides an overview of new features and changes being introduced in New Asset Accounting in SAP S/4HANA. Key points include: depreciation is now posted per asset rather than in aggregate; reconciliation between FI and AA is integrated by design; a technical clearing account is used for asset acquisition postings; the migration process involves customizing, moving legacy data to the SAP Simple Finance add-on, and activating the new accounting functionality. Various transactions and programs from the previous asset accounting are no longer available.
This document provides instructions for configuring automatic postings in an ERP system for inventory management and invoice verification transactions. Key steps include defining valuation levels, charts of accounts, valuation grouping codes, valuation classes, and account groupings. The system can then simulate postings to automatically determine the correct GL accounts based on these definitions and the transaction type. Definitions must be made for each chart of accounts and valuation grouping code combination.
This document provides instructions for configuring profitability analysis in SAP. It discusses defining characteristics and value fields, which are the key dimensions and values used to analyze profitability. Characteristics can be predefined, fixed, copied from reference tables, or custom defined. Instructions are provided for viewing existing characteristics, creating new user-defined characteristics like "Bill to party" and "Business field", and activating the new characteristics for use. The document outlines the overall profitability analysis configuration process and provides a guide to setting up the necessary master data and structures.
This document provides instructions for testing and debugging IDOCs in SAP. It describes transactions for processing inbound and outbound IDOCs (WE12, WE16, WE17, BD87, BD88), editing IDOC data (WE19, WE02, WE05), and reprocessing IDOCs (BD87). Detailed steps are provided for using WE19 to test inbound IDOCs by function module or standard processing, and to edit IDOC segments. The differences between processing options in WE19 are also summarized.
This document provides instructions for configuring SAP Cash Management. It discusses activating Cash Management in the company code, defining basic settings like value date defaults and source symbols, maintaining required master data, structuring the Cash Management setup by defining account names and groupings, and configuring liquidity forecasting, bank accounting, and cash concentration features. The document is a guide for SAP consultants to customize and implement Cash Management functionality in SAP.
The document discusses availability check configuration in SAP. Key points:
- Availability check verifies stock availability when creating sales orders.
- It can be configured using availability check groups, checking rules, and scope of check parameters.
- Configuration includes options like considering safety stock, stock in transit, blocked stock, and open purchase orders and sales requirements.
- Backorder processing allows assigning quantities from cancelled low priority orders to new high priority orders if stock is unavailable. It requires individual requirements to be set for the material.
This document appears to be a record of transactions for commodities and stocks made between November 6th and 27th. It includes details of the script/stock, transaction date, buy/sell indicator, buy and sell rates, profits/losses for each transaction, and running totals of profits. The transactions resulted in a total profit of Rs. 138,850 over the period according to the document.
The Controlling module in SAP provides management with supporting information for planning, reporting, and monitoring business operations. It includes components like cost element accounting, cost center accounting, internal orders, activity-based costing, product cost controlling, profitability analysis, and profit center accounting. Maintaining controlling areas and number ranges are important setup steps in the Controlling module configuration. A controlling area can include one or multiple company codes that use the same chart of accounts. Number ranges need to be defined for controlling documents like cost centers, internal orders, and product cost estimates.
The document provides an overview of organizational structures in SAP R/3 Materials Management (MM) module. It discusses key MM concepts like clients, company codes, plants, purchasing organizations, and storage locations. It also describes how these organizational units are arranged hierarchically and how they determine tasks and responsibilities in the SAP system. The document explains how basic master data like vendors and materials form the foundation for key MM processes like purchasing, goods receipt, and inventory management.
Creating SOA with Oracle Fusion Middleware 11gLonneke Dikmans
A Service Oriented Architecture consists of a number of building blocks. Oracle offers these blocks in the Oracle Fusion Middleware stack. In this presentation an overview of components or building blocks you need in a SOA is given. The Oracle Fusion Middleware stack is plotted on this architecture. Obviously customers can also choose to mix and match products from different vendors. This has both advantages and disadvantages. These issues are discussed and illustrated with some examples from real (anonymized) customers.
The document discusses leased assets and their accounting treatment. Leased assets remain the property of the lessor during the lease term and represent a special form of rented asset. Depending on the country and lease type, leased assets may need to be capitalized on the lessee's balance sheet. The SAP FI-AA module enables capitalizing leased assets using the capital lease method, which calculates the asset value as the present value of future lease payments. Leased assets can be treated as either capital leases, which are capitalized and depreciated, or operating leases, which are expensed as periodic rent payments.
BI-population CMA-ES Algorithms with Surrogate Models and Line SearchesIlya Loshchilov
This document describes recent work on improving covariance matrix adaptation evolution strategies (CMA-ES) for black-box optimization. It introduces several algorithms that use surrogate models to assist CMA-ES, including self-adaptive surrogate-assisted CMA-ES (saACM-ES). The key contributions discussed are:
1) Intensive surrogate model exploitation in BIPOP-saACM-ES-k, which allows for a smaller budget for surrogate-assisted search compared to previous methods.
2) Hybrid algorithms for optimizing separable and non-separable functions, including BIPOP-aCMA-STEP and HCMA.
3) Previous algorithms like BIPOP-saACM-ES and
Primavera _ Mike Sicilia _ Orace Primavera vision and road ahead.pdfInSync2011
This document provides an overview and roadmap for Oracle Primavera. It discusses Oracle Primavera's transformation into a complete enterprise project portfolio management platform. It highlights the benefits of an enterprise approach to project management, including economies of scale, standardization, transparency, and visibility. It also discusses how Oracle Primavera solutions support an enterprise approach through integration, consistency, and providing a global view of all projects.
Management accounting is a recent term that was coined in the 1950s to describe accounting as an effective management tool. [1] It involves techniques like budgeting, standard costing, and analyzing performance to provide information to assist management with planning, control, and decision making. [2] The objectives of management accounting are to compile plans and budgets, allocate responsibilities, analyze transactions, and present up-to-date financial information to help management evaluate performance and plan for the future. [3] Its scope encompasses financial accounting, cost accounting, budgeting, cost control, statistical analysis, and other areas that provide tools to help managers increase productivity.
Chiquita Brands International is a Cincinnati-based company that is the successor to the United Fruit Company. It produces and distributes bananas and other fresh fruits. The company has been involved in controversies including payment to paramilitary groups in Colombia for protection, bribing officials, and ongoing violations of workers' rights. It was found guilty of paying $1.7 million to paramilitary groups from 1989-2004 and was fined $25 million. The company also bribed officials in Colombia and had to pay a $100,000 penalty. It has been accused of endangering workers' health through pesticide exposure and using militias to intimidate unionizing efforts.
The document provides an overview of SAP FICO interview questions and answers related to enterprise structure, the general ledger, accounts receivable, accounts payable, and invoice verification. Key points include how company codes, controlling areas, and fiscal years are configured, the purpose of document types and financial statement versions, and the process for invoice verification from goods receipt to invoice posting. It encourages visiting sap-topjobs.com for additional SAP consulting resources and training.
The document provides an overview of accounts receivable processes in SAP, including master data, credit management, invoice processing, cash receipting, and periodic processing. It describes setting up customer accounts, credit limits, and payment terms. The key processes covered are creating invoices, debit/credit memos, parked documents, and intercompany postings. Reports and periodic jobs are listed for managing accounts receivable.
New GL parallel ledgers in asset accounting Hari Krishna
We can use parallel ledgers in asset accounting to value assets according to different accounting principles. The document outlines how to configure parallel ledgers for US GAAP and Indian GAAP valuations. Key steps include defining depreciation areas, assigning them to asset classes and general ledger accounts, and setting up periodic posting. Testing shows parallel acquisition and depreciation postings are made to the respective ledgers according to the depreciation areas assigned in the asset master. Retiring the asset then results in different gains/losses posted to each ledger.
Su01 parameters fico_guntupalliharikrishna Hari Krishna
This document contains a list of parameter IDs, their associated values, and short descriptions. Some of the parameter IDs and short descriptions include references to SAP modules like FI (Financial Accounting), document types, templates, and user-specific settings for areas like cash journal, general ledger, asset master data, and document display. The parameter values include codes, descriptions, and configuration details for entities like the company code, fiscal year, currency, chart of accounts, and more.
This document provides an overview of management accounting concepts and techniques. It discusses key topics like cost accounting, financial accounting, cost concepts, differences between cost accounting and financial accounting, techniques used in management accounting like budgeting and costing. It also outlines the structure and contents of management accounting syllabus covering concepts of financial accounting, cost accounting, ratios, budgeting and other techniques.
SAP Asset accounting book Sample PDF by LearnSAPLearnSAP LLC
http://www.learnsap.com/sap-study-material.php
SAP Asset accounting step by step study sample material - visit our website http://www.learnsap.com/sap-study-material.php for complete access of printed hardcopy.
These SAP step by step study guides are carefully written by experienced and certified instructors based in the USA
Call +1-832-419-7371 for more details
Sap costing variant by guntupalli hari krishnaHari Krishna
This document discusses SAP costing variants. It provides information on how costing variants allow companies to track different costing methods for planning, actual, and standard costs. Costing variants are used to value inventory and calculate profits using different costing methods for different parts of a company.
Strategic Management Accounting for Business and Career SuccessKen Witt
Identifies the skills and competencies that accountants need in order to contribute to the strategic success of their employer in a complex, global business environment.
Enterprise Security Architecture: From access to auditBob Rhubart
Paul Andres' presentation from OTN Architect Day in Pasadena, July 9, 2009.
Find an OTN Architect Day event near you: http://www.oracle.com/technology/architect/archday.html
Interact with Architect Day presenters and participants on Oracle Mix: https://mix.oracle.com/groups/15511
This document provides an overview of topics related to accounting and finance for bankers, including partnership accounts, company accounts, balance sheet equations, and accounting in a computerized environment. It discusses key concepts such as types of partnerships, methods of calculating goodwill, final accounts for banking companies, asset classification, and the basics of computerized accounting systems.
The document provides information about the Certified Management Accountant (CMA) certification. The CMA credential demonstrates command of critical accounting and financial management skills demanded by businesses. It is designed specifically for accounting and financial professionals. The advantages of obtaining a CMA include worldwide recognition, career opportunities, higher salaries, and pride in a highly acclaimed certification. EMERGE Management Training Center offers CMA exam preparation courses in Dubai and discusses the benefits of their program, including interactive lectures and study materials.
The document describes posting vendor payments in SAP using transaction code F-04. With posting and clearing, line items are entered and then open items are selected to clear them. Once the open item amounts equal the line item amounts, the system clears the items by creating documents to debit vendor accounts and credit bank accounts. Fields required for posting include document date, type, company code, posting date, currency, bank account, account, and amount.
The document describes posting vendor payments in SAP using transaction code F-04. With posting and clearing, line items are entered and then open items are selected to clear them. Once the open item amounts equal the line item amounts, the system clears the items by creating documents to debit vendor accounts and credit bank accounts. Fields required for posting include document date, type, company code, posting date, currency, bank account, account, and amount.
The document outlines the steps to configure and process vendor down payments in SAP. It includes setting up required G/L accounts and configuration, creating a purchase order with a down payment, generating the down payment request, posting the down payment, clearing the down payment against an invoice receipt, and the related financial postings.
This document describes how to analyze goods receipt/invoice receipt (GR/IR) clearing accounts in SAP at a specified key date to generate adjustment postings if necessary. The transaction selects open items in GR/IR clearing accounts and creates adjustment postings in a batch input session if the open items do not balance out to zero per purchase order and item. This ensures goods delivered but not invoiced and goods invoiced but not delivered are displayed correctly in financial statements. The example provided prepares a clearing for GR/IR balances at June 30, 2002 by generating adjustment postings with a specified document date and posting period.
This document provides configuration settings for asset accounting in SAP. It includes instructions on setting up charts of depreciation, general ledger indicators, parallel currencies, asset classes, screen layouts, and depreciation terms. Key steps include copying the reference chart of depreciation, creating general ledger accounts for fixed assets, depreciation, sales, and expenses, maintaining conversion factors and exchange rates, assigning tax codes, and defining asset classes and number ranges. The goal is to properly configure the asset accounting module according to the country's legal and business requirements.
Step 1) Define Table Directory - You can perform an express installation for a FI-SL system using default settings and values.
Step 2) Maintain Table Directory - You can call up and display or maintain tables used in the Special Purpose Ledger system.
Step 3) Maintain Fixed Field Movement - You can define which fields are transferred from sender tables to receiver tables in the FI-SL system.
This document provides instructions for configuring Service Tax and Education Cess tax conditions and accounts in SAP for reporting in India. Key steps include:
1. Creating new tax conditions for Service Tax and Education Cess
2. Defining new tax posting keys for Service Tax and Education Cess accounts
3. Configuring tax codes, procedures, and pricing to calculate Service Tax and Education Cess amounts and post to the correct general ledger accounts.
1. Four condition types (JSB1, JSB2, JSB3, JSB4) need to be created to handle Swachh Bharat Cess (SBCess) for accounts payable (MM) and accounts receivable (SD).
2. Four tax account keys (SB1, SB2, SB3, SB4) need to be created and assigned to the appropriate general ledger accounts to post SBCess for MM and SD.
3. The condition types and account keys need to be assigned in the tax procedure to ensure SBCess is calculated correctly on service costs for both MM and SD transactions.
This document provides step-by-step instructions for creating general ledger (GL) posting documents in SAP. It describes how to create single-entry and mass posting documents using transaction codes F-02 and FB50 respectively. Key steps include entering header information like document date and type, then adding line items with details such as account, amount, cost center, and debit/credit indicator. The document can be simulated and validated before final posting.
Real Time SAP Training with 100% Placement, Best Sap Fico Academy , Attitude Tally learning Institute offers Sap classes at Yamuna Vihar East Delhi NCR
This document provides a summary of important tables and transaction codes for SAP SD (Sales and Distribution). It lists key master data tables for customers, sales documents, billing, delivery, and shipping. It also categorizes and lists commonly used transaction codes for business partners, items, conditions, sales processes, orders, billing, shipping, and more. The tables and transaction codes can be used to create, change, display and process sales documents and master records in SAP SD.
This document provides instructions for setting up intercompany billing between two companies using EDI vendor invoices. It outlines 9 key customizing steps needed at the selling company: 1) Create a vendor for the delivering company, 2) Check output type settings, 3) Check output determination procedure, 4) Maintain the vendor in the internal customer master, 5) Set up partner profiles for outbound processing, 6) Set up partner profiles for inbound processing, 7) Assign vendors to company codes and customers, 8) Maintain output condition records, 9) Process the IDoc output and check for errors. Additional steps are described for invoice verification in MM. The goal is to generate a vendor invoice in FI through outbound and inbound IDoc processing between
This document provides instructions for setting up and configuring SAP for financial accounting for a company called TATACA. It outlines the steps to define the company and company codes, set up fiscal year variants and periods, create a chart of accounts, and generate document number ranges. It also describes how to create general ledger accounts, assign field status groups, define tolerance groups for document posting, and provides an example of posting a general ledger transaction. The key steps are to define the basic master data, set up the chart of accounts and fiscal calendar, and control posting amounts through tolerance groups.
Basic configuration settings for fi asset accountingGuangfuDavidLi
This document provides instructions for configuring asset accounting in SAP. It outlines 20 steps for basic setup including: 1) defining charts of depreciation and depreciation areas, 2) assigning charts of depreciation to company codes, 3) creating asset classes and specifying account determination, 4) maintaining depreciation keys, 5) creating asset master records, 6) acquiring and capitalizing assets, 7) settling assets under construction, 8) retiring assets, 9) transferring assets between records, and 10) transferring assets between company codes. Screenshots and transaction codes are provided for each configuration step.
The document provides transaction codes and descriptions for various excise duty and tax related processes in India. Some key points:
- There are transaction codes for processes like creating excise invoices, registers, returns, migration tools, and more.
- Master data like customer, plant, and item masters have excise related fields to track tax numbers and duty rates.
- Sales processes incorporate excise duty calculation and invoice creation for factories, depots, and other movements.
- Special processes address exports, exemption forms, export oriented units, and batch excise invoice creation.
In summary, the document outlines the SAP transaction codes and master data for comprehensively handling Indian excise duty and tax compliance
1) The document provides an index and details for various SAP CO (controlling) notes including cost center accounting, internal orders, profit center accounting, product costing, and actual costing.
2) Key aspects of cost center accounting covered include creating primary cost elements, cost center master data, posting transactions, and generating reports.
3) The document outlines steps for basic controlling area and organizational structure setup including maintaining versions for budgeting and actual comparisons.
This document provides steps for customizing tax calculation procedures in SAP for India. It discusses setting up condition types, defining tax codes, assigning tax procedures and codes to company codes, and maintaining excise defaults. The tax calculation procedure TAXINN allows for either formula-based or condition-based excise determination. Key areas that must be configured include access sequences, account keys, and assigning the TAXINN procedure and country India.
The document provides an overview of the key processes in SAP FI Accounts Receivable module, including master data maintenance, invoice processing, cash receipting/payments, account analysis and reconciliation, periodic processing like dunning, and reporting. It describes the main sub-processes, business transactions, and configuration settings involved in each step of the accounts receivable lifecycle in SAP.
The document discusses rules for splitting joint venture accounting transactions across multiple ventures in SAP. It provides examples of how purchase invoices, payments, and other documents would be split between two joint ventures defined as Venture V1 and Venture V2. Key points covered include splitting rules for non-clearing documents, clearing documents, and special cases like ensuring balanced books for each venture.
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.
Everything You Need to Know About X-Sign: The eSign Functionality of XfilesPr...XfilesPro
Wondering how X-Sign gained popularity in a quick time span? This eSign functionality of XfilesPro DocuPrime has many advancements to offer for Salesforce users. Explore them now!
Flutter is a popular open source, cross-platform framework developed by Google. In this webinar we'll explore Flutter and its architecture, delve into the Flutter Embedder and Flutter’s Dart language, discover how to leverage Flutter for embedded device development, learn about Automotive Grade Linux (AGL) and its consortium and understand the rationale behind AGL's choice of Flutter for next-gen IVI systems. Don’t miss this opportunity to discover whether Flutter is right for your project.
8 Best Automated Android App Testing Tool and Framework in 2024.pdfkalichargn70th171
Regarding mobile operating systems, two major players dominate our thoughts: Android and iPhone. With Android leading the market, software development companies are focused on delivering apps compatible with this OS. Ensuring an app's functionality across various Android devices, OS versions, and hardware specifications is critical, making Android app testing essential.
INTRODUCTION TO AI CLASSICAL THEORY TARGETED EXAMPLESanfaltahir1010
Image: Include an image that represents the concept of precision, such as a AI helix or a futuristic healthcare
setting.
Objective: Provide a foundational understanding of precision medicine and its departure from traditional
approaches
Role of theory: Discuss how genomics, the study of an organism's complete set of AI ,
plays a crucial role in precision medicine.
Customizing treatment plans: Highlight how genetic information is used to customize
treatment plans based on an individual's genetic makeup.
Examples: Provide real-world examples of successful application of AI such as genetic
therapies or targeted treatments.
Importance of molecular diagnostics: Explain the role of molecular diagnostics in identifying
molecular and genetic markers associated with diseases.
Biomarker testing: Showcase how biomarker testing aids in creating personalized treatment plans.
Content:
• Ethical issues: Examine ethical concerns related to precision medicine, such as privacy, consent, and
potential misuse of genetic information.
• Regulations and guidelines: Present examples of ethical guidelines and regulations in place to safeguard
patient rights.
• Visuals: Include images or icons representing ethical considerations.
Content:
• Ethical issues: Examine ethical concerns related to precision medicine, such as privacy, consent, and
potential misuse of genetic information.
• Regulations and guidelines: Present examples of ethical guidelines and regulations in place to safeguard
patient rights.
• Visuals: Include images or icons representing ethical considerations.
Content:
• Ethical issues: Examine ethical concerns related to precision medicine, such as privacy, consent, and
potential misuse of genetic information.
• Regulations and guidelines: Present examples of ethical guidelines and regulations in place to safeguard
patient rights.
• Visuals: Include images or icons representing ethical considerations.
Real-world case study: Present a detailed case study showcasing the success of precision
medicine in a specific medical scenario.
Patient's journey: Discuss the patient's journey, treatment plan, and outcomes.
Impact: Emphasize the transformative effect of precision medicine on the individual's
health.
Objective: Ground the presentation in a real-world example, highlighting the practical
application and success of precision medicine.
Data challenges: Address the challenges associated with managing large sets of patient data in precision
medicine.
Technological solutions: Discuss technological innovations and solutions for handling and analyzing vast
datasets.
Visuals: Include graphics representing data management challenges and technological solutions.
Objective: Acknowledge the data-related challenges in precision medicine and highlight innovative solutions.
Data challenges: Address the challenges associated with managing large sets of patient data in precision
medicine.
Technological solutions: Discuss technological innovations and solutions
Benefits of Artificial Intelligence in Healthcare!Prestware
Benefits of AI in Healthcare
Faster Diagnoses
AI speeds up the diagnostic process, helping doctors identify conditions quickly and accurately.
Personalized Treatments
AI creates customized treatment plans based on individual patient data, improving outcomes.
Predictive Healthcare
AI anticipates health issues before they arise, allowing for preventative measures.
Improved Accuracy
AI reduces human error in diagnostics and treatment, leading to better patient care.
Enhanced Imaging
AI improves the clarity and precision of medical imaging, aiding in early detection of diseases.
Efficient Drug Development
AI accelerates the drug discovery process, bringing new treatments to market faster.
Streamlined Operations
AI automates administrative tasks, reducing the burden on healthcare professionals and improving efficiency.
24/7 Patient Support
AI-powered virtual assistants and chatbots provide round-the-clock support and information to patients.
Cost Reduction
AI optimizes resource use and reduces operational costs, making healthcare more affordable.
Continuous Monitoring
AI continuously monitors patient health, enabling timely interventions and better management of chronic conditions.
Experience the Future of Healthcare with AI!
#AIinHealthcare #MedicalInnovation #HealthTech #BetterCare
Most important New features of Oracle 23c for DBAs and Developers. You can get more idea from my youtube channel video from https://youtu.be/XvL5WtaC20A
DevOps Consulting Company | Hire DevOps Servicesseospiralmantra
Spiral Mantra excels in providing comprehensive DevOps services, including Azure and AWS DevOps solutions. As a top DevOps consulting company, we offer controlled services, cloud DevOps, and expert consulting nationwide, including Houston and New York. Our skilled DevOps engineers ensure seamless integration and optimized operations for your business. Choose Spiral Mantra for superior DevOps services.
https://www.spiralmantra.com/devops/
WMF 2024 - Unlocking the Future of Data Powering Next-Gen AI with Vector Data...Luigi Fugaro
Vector databases are transforming how we handle data, allowing us to search through text, images, and audio by converting them into vectors. Today, we'll dive into the basics of this exciting technology and discuss its potential to revolutionize our next-generation AI applications. We'll examine typical uses for these databases and the essential tools
developers need. Plus, we'll zoom in on the advanced capabilities of vector search and semantic caching in Java, showcasing these through a live demo with Redis libraries. Get ready to see how these powerful tools can change the game!
How Can Hiring A Mobile App Development Company Help Your Business Grow?ToXSL Technologies
ToXSL Technologies is an award-winning Mobile App Development Company in Dubai that helps businesses reshape their digital possibilities with custom app services. As a top app development company in Dubai, we offer highly engaging iOS & Android app solutions. https://rb.gy/necdnt
UI5con 2024 - Bring Your Own Design SystemPeter Muessig
How do you combine the OpenUI5/SAPUI5 programming model with a design system that makes its controls available as Web Components? Since OpenUI5/SAPUI5 1.120, the framework supports the integration of any Web Components. This makes it possible, for example, to natively embed own Web Components of your design system which are created with Stencil. The integration embeds the Web Components in a way that they can be used naturally in XMLViews, like with standard UI5 controls, and can be bound with data binding. Learn how you can also make use of the Web Components base class in OpenUI5/SAPUI5 to also integrate your Web Components and get inspired by the solution to generate a custom UI5 library providing the Web Components control wrappers for the native ones.
Preparing Non - Technical Founders for Engaging a Tech AgencyISH Technologies
Preparing non-technical founders before engaging a tech agency is crucial for the success of their projects. It starts with clearly defining their vision and goals, conducting thorough market research, and gaining a basic understanding of relevant technologies. Setting realistic expectations and preparing a detailed project brief are essential steps. Founders should select a tech agency with a proven track record and establish clear communication channels. Additionally, addressing legal and contractual considerations and planning for post-launch support are vital to ensure a smooth and successful collaboration. This preparation empowers non-technical founders to effectively communicate their needs and work seamlessly with their chosen tech agency.Visit our site to get more details about this. Contact us today www.ishtechnologies.com.au
Superpower Your Apache Kafka Applications Development with Complementary Open...Paul Brebner
Kafka Summit talk (Bangalore, India, May 2, 2024, https://events.bizzabo.com/573863/agenda/session/1300469 )
Many Apache Kafka use cases take advantage of Kafka’s ability to integrate multiple heterogeneous systems for stream processing and real-time machine learning scenarios. But Kafka also exists in a rich ecosystem of related but complementary stream processing technologies and tools, particularly from the open-source community. In this talk, we’ll take you on a tour of a selection of complementary tools that can make Kafka even more powerful. We’ll focus on tools for stream processing and querying, streaming machine learning, stream visibility and observation, stream meta-data, stream visualisation, stream development including testing and the use of Generative AI and LLMs, and stream performance and scalability. By the end you will have a good idea of the types of Kafka “superhero” tools that exist, which are my favourites (and what superpowers they have), and how they combine to save your Kafka applications development universe from swamploads of data stagnation monsters!
Baha Majid WCA4Z IBM Z Customer Council Boston June 2024.pdfBaha Majid
IBM watsonx Code Assistant for Z, our latest Generative AI-assisted mainframe application modernization solution. Mainframe (IBM Z) application modernization is a topic that every mainframe client is addressing to various degrees today, driven largely from digital transformation. With generative AI comes the opportunity to reimagine the mainframe application modernization experience. Infusing generative AI will enable speed and trust, help de-risk, and lower total costs associated with heavy-lifting application modernization initiatives. This document provides an overview of the IBM watsonx Code Assistant for Z which uses the power of generative AI to make it easier for developers to selectively modernize COBOL business services while maintaining mainframe qualities of service.
Unveiling the Advantages of Agile Software Development.pdfbrainerhub1
Learn about Agile Software Development's advantages. Simplify your workflow to spur quicker innovation. Jump right in! We have also discussed the advantages.
Liberarsi dai framework con i Web Component.pptxMassimo Artizzu
In Italian
Presentazione sulle feature e l'utilizzo dei Web Component nell sviluppo di pagine e applicazioni web. Racconto delle ragioni storiche dell'avvento dei Web Component. Evidenziazione dei vantaggi e delle sfide poste, indicazione delle best practices, con particolare accento sulla possibilità di usare web component per facilitare la migrazione delle proprie applicazioni verso nuovi stack tecnologici.
A Comprehensive Guide on Implementing Real-World Mobile Testing Strategies fo...kalichargn70th171
In today's fiercely competitive mobile app market, the role of the QA team is pivotal for continuous improvement and sustained success. Effective testing strategies are essential to navigate the challenges confidently and precisely. Ensuring the perfection of mobile apps before they reach end-users requires thoughtful decisions in the testing plan.
Consistent toolbox talks are critical for maintaining workplace safety, as they provide regular opportunities to address specific hazards and reinforce safe practices.
These brief, focused sessions ensure that safety is a continual conversation rather than a one-time event, which helps keep safety protocols fresh in employees' minds. Studies have shown that shorter, more frequent training sessions are more effective for retention and behavior change compared to longer, infrequent sessions.
Engaging workers regularly, toolbox talks promote a culture of safety, empower employees to voice concerns, and ultimately reduce the likelihood of accidents and injuries on site.
The traditional method of conducting safety talks with paper documents and lengthy meetings is not only time-consuming but also less effective. Manual tracking of attendance and compliance is prone to errors and inconsistencies, leading to gaps in safety communication and potential non-compliance with OSHA regulations. Switching to a digital solution like Safelyio offers significant advantages.
Safelyio automates the delivery and documentation of safety talks, ensuring consistency and accessibility. The microlearning approach breaks down complex safety protocols into manageable, bite-sized pieces, making it easier for employees to absorb and retain information.
This method minimizes disruptions to work schedules, eliminates the hassle of paperwork, and ensures that all safety communications are tracked and recorded accurately. Ultimately, using a digital platform like Safelyio enhances engagement, compliance, and overall safety performance on site. https://safelyio.com/
1. VAT Configuration for TAXINN
SD Configuration
Step 1: Change in Customer Master
IMG > Logistic General > Business Partner > Customers > Control > Define Account Groups and Field
Selection for Customers (OVT0)
IMG > Logistic General > Business Partner > Customers > Control > Define Transaction-Dependent
Screen Layout (OB20)
OB20 - Change Tax Type to Optional for Create / Change (A/c’ing, Sales & Centrally)
OB20 - Change Tax Type to Display for Display (A/c’ing, Sales & Centrally)
OVT0 - Change Tax Type to Optional for Sold to party, Ship to party, Bill to party & payer.
Step 2: Define New Condition Type
IMG > Sales and Distribution > Basic Functions > Pricing > Pricing Control > Define Condition Types
> Maintain Condition Types (V/06)
V/06 – JIVP copy of JLST (A/R VAT Payable) & change condition category to ‘D’ & Access
Sequence ‘MWST’
V/06 – JIVC copy of JLST (A/R CST Payable VAT) & change condition category to ‘D’ & Access
Sequence ‘MWST’
OBQ1 - JIVP copy of JLST (A/R VAT Payable)
OBQ1 - JIVC copy of JLST (A/R CST Payable VAT)
Step 3: Define Account Key JN6,JN7 & JN8 (T.Code: OBCN & also in SD)
IMG> Financial Accounting> Taxes on Sales and Purchases> Basic Setting> Check & change setting
for Tax Processing (OBCN)
IMG> Sales & Distribution> Basic Function> Account Assignment / Costing> Revenue Account
Determination> Define & assign Account Keys> Define Account Keys.
Step 4: Include Table no 11 & 368 to access sequence JIND (T.Code: V/07)
IMG > Sales and Distribution > Basic Functions > Pricing > Pricing Control > Define Condition Tables
(V/07)
Step 5: Change SD Pricing Procedure (T.Code:V/08 & OBQ3)
IMG > Sales and Distribution > Basic Functions > Pricing > Pricing Control > Define and assign Pricing
Procedure > Maintain Pricing Procedure (V/08)
V/08: Select relevant SD Procedure. Add JIVP & JIVC in Relevant Pricing Procedure immediately after
JLST & JLCT conditions. (Customized change for ZINFAC)
2. OBQ3: Add JIVP, JIVC in TAXINN immediately after JLST, JCST Conditions & assign A/c keys.
(only if SD conditions exist in TAXINN)
Step 6: Create new FI Document Type (T.Code:OBA7)
Financial Accounting > Financial Accounting Global Settings > Document > Document Header >
Define Document Types (OBA7)
Create FT wrt RV.
*** Initially create with reference to RV & on saving return back to FT & change assignment of
reversal Document type to FT
Step 7: Document Number Range for FI Document (T.Code: FBN1)
Financial Accounting > Financial Accounting Global Settings > Document > Document Number Ranges
> Define Document Number Ranges (FBN1)
Create new accounting document number range based on Company Code & assign the same for the
Accounting Document defined in previous step.
*** Document Number Range defined as FT
Step 8: New Billing Type (T.Code: VOFA)
IMG > Sales & Distribution > Billing > Billing Documents > Define Billing Types (VOFA)
Create new billing type FVAT & FBOS wrt F2
SD Doc. Cate: M Invoice
Transaction Gr: 7 (Billing Document)
Document Type: FT
Output Type: Newly created output type should be assigned here.
Step 9: Maintain copy control for Billing Documents (T.Code: VTFL)
Sales & Distribution > Billing > Billing Documents > Maintain Copying Control For Billing Documents
(VTFL)
In customizing settings, we need to maintain item level copying control for data transfer for order /
delivery document to billing document. This would ensure that when billing document is created using
(for eg) F2, the relevant VAT or Bill of Sale invoice would be created.
Sample setting is as under:
Tgt Billing Doc: F2 (Invoice) from Delivery Type: LF (O/B delivery)
Item Category: Tan
Data VRBK/VBRP: Routine 350 (created for VAT invoice for India)
*** Routine 350 is giving error, so avoid this step, as of now.
3. Step 10: Create Output Type for new Billing Type (T.Code: V/40)
Sales and Distribution > Basic Functions > Output Control > Output Determination > Output
Determination Using the Condition Technique > Maintain Output Determination for Billing Documents
> Maintain Output Types (V/40)
Create new output types for Bill of Sales and VAT Invoice, 'RD00' can be taken as a reference output
type. Maintain the program and layout for the same. All other parameters can be same as in RD00.
*** Preferably create separate output type for FVAT & FBOS
Step 11: Maintain Output Type in Output Determination procedure
Sales and Distribution > Basic Functions > Output Control > Output Determination > Output
Determination Using the Condition Technique > Maintain Output Determination for Billing Documents
> Maintain Output Determination Procedures
Step 12: Assign new Output Types in Output Determination Procedure (V/25)
Sales and Distribution > Basic Functions > Output Control > Output Determination > Output
Determination Using the Condition Technique > Maintain Output Determination for Billing Documents
> Assign Output Determination Procedures (V/25)
The output type created in previous step needs to be assigned with output determination procedure for
Billing Type.
In case additional output types for other billing types (e.g. Export, Exempted Material etc.) are there,
then they need to be created.
Configuration for STO via SD Route:
Step 12: Define Condition Types ST00 (V/06)
IMG > Sales and Distribution > Basic Functions > Pricing > Pricing Control > Maintain Condition
Types (V/06)
Create a new Condition Type ST00: STO Turnover - This condition type is required to calculate the
STO Turnover. Maintain the same attribute as in PR00.
Step no 13: Define Pricing Procedure Determination (OVKK)
IMG > Sales and Distribution > Basic Functions > Pricing > Pricing Control > Define and assign Pricing
Procedure > Define Pricing Procedure Determination (OVKK)
Step 14: Activate Item category for Pricing
IMG > Sales and Distribution > Basic Functions > Pricing > Pricing Control > Define Pricing By Item
Category> Activate Pricing Procedure for Item Category
For Replenishment Delivery item category NLN should be made relevant for pricing.
4. Step 15: Create SD Pricing Procedure
IMG > Sales and Distribution > Basic Functions > Pricing > Pricing Control > Define and assign Pricing
Procedure > Maintain Pricing Procedure (V/08)
Create a new pricing procedure for Stock Transfer Turnover and include only one condition type i.e.
ST00 defined earlier.
Step 16: Assign Pricing Procedure for Sales Price to Delivery
IMG > Logistics Execution > Shipping > Basic Shipping Functions > Pricing > Define pricing
procedures for delivery (SPRO)
Assign Delivery type (NL- Replenishment Delivery) to a Pricing Procedure defined for calculating stock
transfer turnover.
Note This is available only in SAP R/3 4.6B onwards.
CIN CUSTOMISING
Step 17: Assign Excise Invoice Billing Type to Delivery Type
J1IL or J1ILN > SAP Menu > Customization > India Localization Menu > Sales & Distribution >
Assign excise invoice billing type to delivery type (J1IT)
New copy controls need to be maintained for new billing type i.e. FBOS and FVAT to delivery type JF/
LF
Step 18: Define Business Place
SM31 > Enter View Name J_1BBRANCV or the path
J1IL or J1ILN > SAP Menu > Customization > India Localization Menu > Global Settings > Define
Business Place
Define your Business Place based on company code. In the "Details" screen, you need to maintain the
VAT registration number for the Business Place in the field "Tax Code 1" (Field STCD1). Also enter the
Country and Region for which the Business Place is defined.
Step 19: Assign Business Place to Plant
SM31 > Enter View Name J_1BT001WV or the path
J1IL or J1IL(N) > India Localization Menu > Global Settings > Assign Business Place
Assign the Business place you created for your company code to the Plants within the company code.
Step 20: Create & assign Tax Category for Customer
5. IMG > Financial Accounting > Account receivable & Account payable> Customer Accounts > Master
data > Preparation for creating Customer Master Data > Accounts Receivable Master Data for
Argentina> Define Fiscal Type / Assign Fiscal Type
Maintain Fiscal Types (Tax Categories) for Country India and Account Type as Customer
o 01 VAT Registered
o 02 Unregistered
o 03 Composite
o 04 Export
Note: Tax Categories for different scenarios can also be created as per requirements of respective State.
Step 21: Assign Billing Type to Business Partners
SM31 > Enter Table Name J_1ICUS_BILL_TYP or the path
J1IL or J1ILN > SAP Menu > Customization > India Localization Menu > Sales and Distribution >
Customizing for VAT > Billing Document Determination > Assign Billing Type to Business Partner
This table maintains Billing Type based on the Country key, Customer, Fiscal Type, Region. Here the
Fiscal Type is the same field created in the earlier steps.
*** As per note no 831870 – The above assignment should not be used.
Step 22: Billing Type Determination for VAT
SM31 > Enter Table Name J_1IBILDET or the path
J1IL or J1ILN > SAP Menu > Customization > India Localization Menu > Sales and Distribution >
Customizing for VAT > Billing Document Determination > Billing Type Determination for VAT
Here we maintain the Country Code, Business Place, Document Category and Sales Area. Based on this
we maintain the table entries for Export Invoice, Interstate Billing, Exempt Billing Type and Billing
Type for Intrastate transactions
-----------------------------------------------------------------------------------------------------------------------------
*** Due to error in routine 350, please avoid the undermentioned steps for time being.
Step 23: Define Document Class
SM31 > Enter Table Name V_DOCCLS or the path
J1IL or J1ILN > SAP Menu > Customization > India Localization Menu > Number RAnge > Number
Ranges Official Official Document Number Determination for VAT > Maintain Document Classes
Define a new document Class for country key 'IN'.
Step 24: Assign Document Class to Document Type
6. SM31 > Enter Table Name V_T003_B_I or the path
J1IL or J1ILN > SAP Menu > Customization > India Localization Menu > Number Range > Official
Document Number Determination for VAT > Assign Document class to Document Type
Assign Accounting Document type to the Document Class for country key 'IN'. Put a check on in the
Self-Issue Check Box. This means that for the particular document class and FI document type, the
company is eligible to issue official documents.
Step 25: Maintain Number Range Group
SM31 > Enter Table Name V_1ANUMGR1 or the path
J1IL or J1ILN > SAP Menu > Customization > India Localization Menu > Number Ranges > Maintain
Number Groups.
Define Number Range Group.
Step 26: Maintain Number Range
Use the transaction code J1AB or the path
J1IL or J1ILN > SAP Menu > Customization > India Localization Menu > India Localization Menu >
Number Ranges > Maintain Number Ranges
Create number ranges for the number range group defined in the previous step. For example maintain a
number range '01' from '1' to '9999999'
Step 27: Assign Number range to Business Place
SM31 > Enter Table Name V_OFNUM_TW_2 or the path
J1IL or J1ILN > SAP Menu > Customization > India Localization Menu > Number Ranges > Assign
Number Range to Business Place
Here official document number range need to be maintained based on the following case:
o Company Code
o Business Place
o Document Type
o Validity Period
o Prefix
o Number Range Group
o Number Range
Step 28: Configuration for Alternate G/L Account
SM30 > Table Name J_1IT030K (or View J_1IT030K) > Maintain the entries
Maintain the alternate G/L Account for following keys :
7. Chart of Accounts +Business Place +Transaction Key +Tax code (optional)
Note: Determination of Alternate G/L Accounts is to be used only for Sales Taxes and not for Excise
Duty.
9. JVCN – JP8 (ST Inventory – India)
*** As JP4, JP6 & JP8 are to be added to inventory, please do not create these transaction / accounts
key. Instead use existing NVV for the same.
Note for Core Team Member:
Create new tax code (Suggested as per SAP)
Tax % RAM Vatable CG Vatable Non Vatable CST
0% V0 V0 V0 V0
1% R1 C1 I1 -
4% R2 C2 I2 N2
12.5% R3 C3 I3 -
10. Customising related to Migration from Business Place to section Code for Extended
Withholding Tax
1) Run Migration program:-
Using T-code SE38. Execute Migration program J_1IEWT_MIGRATE_SECCO. This program
copies data in tables relating to Business Place from Ver 4.6B to related tables in Ver 4.7 under
Section code. It establishes one-to-one relationship between Business place & Section code.
Click Execute.
Note: Kindly note that before executing this program, one should ensure that there is no
manual customizing done for section code.
11. First execute the program in “Test Mode”, a report will be generated which will give
details of the tables that will be updated. In case if there is any customization already
done for section code then this program will give an error.
Once the report is generated, then the same be executed removing the “Test Mode”
tick.
After executing the program u can check if the below mentioned tables are maintained.
12. 2) Maintain EWT-CIN tables using T-code SM30:-
J_1IEWTNUMGR_1 - For internal challan numbers.