This document summarizes the key depot activities in the SAP ERP system for manufacturing (PP) processes, including goods receipt of stock transferred material, excise duty capture, depot excise invoice generation, displaying depot stock balances, extracting the RG23D register, and printing the RG23D register. It provides an overview of the purpose, master data, primary steps, and transaction codes for each major depot activity.
The document discusses depot sales processes in SAP. A depot is treated like a warehouse where goods can be sold to customers. Goods received and leaving the depot must be recorded in depot registers, which track opening and closing balances each day. Intra-company stock transfers are used to move inventory from the manufacturing plant to the depot. Excise values flow from proforma invoices created during the transfer to the factory excise invoice. Goods are moved via delivery and MIGO updates the depot registers. Depot registers can also be updated individually. Sales orders, deliveries, and billing are used to sell from the depot, with a J1IJ transaction used for depot outgoing excise posting linked to the factory excise invoice
The document provides an overview of excise duty processes and reports in SAP. It discusses master data setup for excise, standard procurement and sales processes involving excise, accounting entries for excise, and reports like RG1, RG23, and monthly returns. Key excise processes covered include goods receipt, capture and posting of excise invoices, stock transfer, and CENVAT availment for capital goods.
The document discusses India localization with respect to SAP, including an introduction to Indian taxes, CENVAT concepts, tax procedures, registers, and configurations needed in SAP. It covers the Indian tax structure of direct and indirect taxes, types of excise duties, CENVAT rules, and how CENVAT credit is availed. It also discusses sales processes, tax procedures, excise registers, and transactions codes relevant for India localization in SAP.
This document provides instructions for using SAP's Country India Version (CIN) functionality. It covers essential excise master data, tax condition records, procedures for claiming CENVAT credit for raw materials and capital goods, importing goods, and printing excise registers. The document includes transaction codes for key excise processes like invoice posting, register updating, and extraction. It aims to guide users through India-specific excise compliance features in SAP.
This document provides an overview of India localization with respect to SAP SD (Sales and Distribution) module. It discusses key topics like Indian tax structure, CENVAT concept, different sales processes, excise registers, tax procedures and configurations required in SAP for India localization. The sales processes covered include sales from factory, stock transfers, sales from depot, exports and more. It also explains concepts like excise duty types, CENVAT rules and credit availability.
This document provides answers to common questions about CIN (SAP's excise module). It explains how CIN determines tax rates, allows changing tax rates retrospectively, and maintaining different rates for incoming and outgoing transactions. It also covers topics like handling concessional excise, opening balances, printing registers and invoices, and fortnightly utilization postings. The document provides technical details on tax setup and configuration in CIN.
This document provides an overview and agenda for a presentation on Country Version India (CIN) and its interfaces with SAP modules. It will cover the background of CIN, how it interfaces with SAP SD, MM, and FI processes. It will also cover Indian localisation coverage for taxes, duties, and reports in areas like procurement, sales, finance. The objective is to provide participants a basic understanding of CIN requirements and interfaces with SAP.
This document provides an overview of Indian taxes, including direct and indirect taxes. It discusses excise duties in detail, explaining the key differences between excise duty and sales tax. Excise duty is levied on manufacturing, while sales tax is levied only when a sale occurs. The document also covers CENVAT (Central Value Added Tax) rules and how CENVAT credit can be availed and utilized in India. It discusses the tax procedures in SAP for availing CENVAT credit and maintaining excise registers for India localization.
The document discusses depot sales processes in SAP. A depot is treated like a warehouse where goods can be sold to customers. Goods received and leaving the depot must be recorded in depot registers, which track opening and closing balances each day. Intra-company stock transfers are used to move inventory from the manufacturing plant to the depot. Excise values flow from proforma invoices created during the transfer to the factory excise invoice. Goods are moved via delivery and MIGO updates the depot registers. Depot registers can also be updated individually. Sales orders, deliveries, and billing are used to sell from the depot, with a J1IJ transaction used for depot outgoing excise posting linked to the factory excise invoice
The document provides an overview of excise duty processes and reports in SAP. It discusses master data setup for excise, standard procurement and sales processes involving excise, accounting entries for excise, and reports like RG1, RG23, and monthly returns. Key excise processes covered include goods receipt, capture and posting of excise invoices, stock transfer, and CENVAT availment for capital goods.
The document discusses India localization with respect to SAP, including an introduction to Indian taxes, CENVAT concepts, tax procedures, registers, and configurations needed in SAP. It covers the Indian tax structure of direct and indirect taxes, types of excise duties, CENVAT rules, and how CENVAT credit is availed. It also discusses sales processes, tax procedures, excise registers, and transactions codes relevant for India localization in SAP.
This document provides instructions for using SAP's Country India Version (CIN) functionality. It covers essential excise master data, tax condition records, procedures for claiming CENVAT credit for raw materials and capital goods, importing goods, and printing excise registers. The document includes transaction codes for key excise processes like invoice posting, register updating, and extraction. It aims to guide users through India-specific excise compliance features in SAP.
This document provides an overview of India localization with respect to SAP SD (Sales and Distribution) module. It discusses key topics like Indian tax structure, CENVAT concept, different sales processes, excise registers, tax procedures and configurations required in SAP for India localization. The sales processes covered include sales from factory, stock transfers, sales from depot, exports and more. It also explains concepts like excise duty types, CENVAT rules and credit availability.
This document provides answers to common questions about CIN (SAP's excise module). It explains how CIN determines tax rates, allows changing tax rates retrospectively, and maintaining different rates for incoming and outgoing transactions. It also covers topics like handling concessional excise, opening balances, printing registers and invoices, and fortnightly utilization postings. The document provides technical details on tax setup and configuration in CIN.
This document provides an overview and agenda for a presentation on Country Version India (CIN) and its interfaces with SAP modules. It will cover the background of CIN, how it interfaces with SAP SD, MM, and FI processes. It will also cover Indian localisation coverage for taxes, duties, and reports in areas like procurement, sales, finance. The objective is to provide participants a basic understanding of CIN requirements and interfaces with SAP.
This document provides an overview of Indian taxes, including direct and indirect taxes. It discusses excise duties in detail, explaining the key differences between excise duty and sales tax. Excise duty is levied on manufacturing, while sales tax is levied only when a sale occurs. The document also covers CENVAT (Central Value Added Tax) rules and how CENVAT credit can be availed and utilized in India. It discusses the tax procedures in SAP for availing CENVAT credit and maintaining excise registers for India localization.
CIN configuration in SAP SD refers to the Country India Version configuration settings for excise duty processes in India. It includes maintaining excise registration IDs, assigning them to plants, and defining excise groups which each require separate excise registers and accounts. Key aspects of CIN configuration include defining pricing procedures, exchange rate types, document types for financial posting, and indicators controlling behaviors like automatic invoice creation and CENVAT crediting.
This document is a user manual for implementing SAP R/3 for excise duty management at Bharat Aluminum Co. Ltd. It covers essential excise master data configuration including excise registration, group, rates, and materials. It describes roles for goods receiving and excise invoice posting. It provides guidance on capturing capital goods cenvat credit, special cases like rejections, and reports for monitoring cenvat balances and transfers. The goal is to guide BALCO's implementation and use of SAP's country-specific India features for accurate excise compliance.
The document provides configuration details for setting up excise tax functionality for India in an SAP system. It includes instructions for configuring basic settings like maintaining excise registrations, company codes, plants and excise groups. It also describes how to determine excise duties, define tax codes, assign accounts and set up transaction posting. The configuration covers areas like tax calculation procedures, condition types, series groups and account determination for accurate excise tax processing in India.
Country Version India (CIN) is an SAP add-on that contains functionality for Indian statutory requirements related to financial accounting and logistics. It covers areas like excise duty calculation and CENVAT credits, sales tax, and maintenance of statutory registers. CIN comes preconfigured with settings for taxation, accounts, and number ranges to facilitate compliance with Indian laws. Transactions like creation of excise invoices and depot invoice capture allow invoicing and reporting as required for excise and sales tax purposes.
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.
TO ENLIGHTEN THE PARTICIPANTS ON COUNTRY VERSION INDIA (CIN) AND THE VARIOUS REQUIREMENTS WHICH ARE TO BE COMPLETED UNDER THE INDIAN STATUTE. HOW CIN INTERFACES WITH SAP SD, MM AND FI PROCESSES AND MEETS THE REPORT REQUIREMENTS .
PAÍS VERSIÓN INDIA, PAYS VERSION INDE, 国家版印度
CIN Domain Basic concepts
FI consultant steps in CIN configuration
CIN VS Service Tax
CIN VS TDS
CIN MM Configuration Steps
CIN SD Configuration Steps
J1I9 CIN Number range objects
Master Data for CIN
MM CYCLES
DEPOT PLANTS
CIN TABLES
CIN Forms
CIN NOTES
CIN ACCOUNTING ENTRIES
UTILIZATION
CIN/VAT/TDS/SERVICE -TAX List of Reports
TAXINN VS TAXINJ
CAPITAL Procurement in SAP
SD CYCLES
Miscellaneous Topics
The document is a handbook for SAP taxation in India that covers:
1) The configuration of tax procedures in SAP like TAXINN and TAXINJ and defining tax codes, condition types, and tax accounts.
2) The Indian localisation coverage in SAP which includes taxes like VAT, excise duty, service tax, and TDS.
3) An overview of the CIN (Country Version India) interface with SAP modules like SD, MM, and FI and how it meets Indian reporting requirements.
CIN is used to calculate excise duty and VAT for sales and purchases based on industry requirements. It involves configurations across the FI, MM, and SD modules including maintaining master data like chapter IDs, customer and vendor excise details, and material-chapter combinations. The sales process is enhanced to calculate excise duty for various sales scenarios like sales from factory, depot, stock transfers, and returns. Pricing procedures need to be configured and condition techniques copied for the different excise duty types. Various scenarios and documents need to be reviewed and configurations set through IMG and checking with transaction code J1iLn.
This document provides configuration steps for setting up excise tax functionality for India in an SAP system, including:
- Maintaining excise registrations, company code settings, plant settings, excise groups, series groups, and excise duty indicators
- Selecting the tax calculation procedure
- Defining tax codes for purchasing documents and assigning them to company codes
- Classifying condition types for tax determination
- Specifying G/L accounts for recording different taxes
The document includes detailed instructions for configuring key areas for excise tax management in India within the SAP system.
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
SAP MM IM Physical inventory -cycle countingLokesh Modem
Cycle counting is a process where inventory is counted at regular intervals within a fiscal year to increase accuracy. It can be configured and implemented in SAP. Key steps include defining cycle count indicators, generating physical inventory documents for materials using report MICN, printing documents using MI21, entering counts using MI24, and integrating differences by posting.
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.
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.
The document describes the process for transferring stock internally between plants within the same organization but different company codes. Key steps include a stock transfer requisition created by MRP or a buyer, converting this into a purchase order, picking and shipping material from the supplying plant, receiving at the receiving plant, and billing between the plants. The process requires SAP ERP, and roles such as purchaser, warehouse clerk, and billing administrator are involved.
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
1. An inter-company stock transport order can be used to transfer materials between two plants in different company codes. This involves configuring the supplying and receiving plants, creating a customer and assigning delivery types and document types.
2. To create an inter-company STO, a vendor must be created for the receiving plant and assigned to the supplying plant. The receiving plant must also be created as a customer with the correct sales area. The delivery type, checking rule and document types must then be assigned in customizing.
3. Once configured, an STO can be created to transfer stock from the supplying to receiving plant. A delivery is then generated, goods can be issued and receipted to complete the transfer between the
Gst implementation road map by endeavour technologiesNiranjan Emparala
The document provides an overview of the proposed roadmap for implementing GST in SAP. It discusses key aspects like the GST components, impact on existing tax systems, prerequisites for implementation in SAP, the process for migrating from TAXINJ to TAXINN, required master data changes, tax configuration, business processes, reporting, and the role of GSTN and GSPs in the digital infrastructure. The implementation will require resources across various SAP modules and involve changes to taxation, billing, purchasing, and reporting processes.
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.
The document outlines the 7 steps for factory sales in India which includes: 1) creating a sales order, 2) creating a delivery referenced to the order, 3) creating an invoice referenced to the delivery, 4) creating an excise invoice, 5) updating the RG1 register, 6) extracting the excise registers, and 7) printing the excise registers. Each step lists the associated transaction code to use in the ERP system.
CIN configuration in SAP SD refers to the Country India Version configuration settings for excise duty processes in India. It includes maintaining excise registration IDs, assigning them to plants, and defining excise groups which each require separate excise registers and accounts. Key aspects of CIN configuration include defining pricing procedures, exchange rate types, document types for financial posting, and indicators controlling behaviors like automatic invoice creation and CENVAT crediting.
This document is a user manual for implementing SAP R/3 for excise duty management at Bharat Aluminum Co. Ltd. It covers essential excise master data configuration including excise registration, group, rates, and materials. It describes roles for goods receiving and excise invoice posting. It provides guidance on capturing capital goods cenvat credit, special cases like rejections, and reports for monitoring cenvat balances and transfers. The goal is to guide BALCO's implementation and use of SAP's country-specific India features for accurate excise compliance.
The document provides configuration details for setting up excise tax functionality for India in an SAP system. It includes instructions for configuring basic settings like maintaining excise registrations, company codes, plants and excise groups. It also describes how to determine excise duties, define tax codes, assign accounts and set up transaction posting. The configuration covers areas like tax calculation procedures, condition types, series groups and account determination for accurate excise tax processing in India.
Country Version India (CIN) is an SAP add-on that contains functionality for Indian statutory requirements related to financial accounting and logistics. It covers areas like excise duty calculation and CENVAT credits, sales tax, and maintenance of statutory registers. CIN comes preconfigured with settings for taxation, accounts, and number ranges to facilitate compliance with Indian laws. Transactions like creation of excise invoices and depot invoice capture allow invoicing and reporting as required for excise and sales tax purposes.
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.
TO ENLIGHTEN THE PARTICIPANTS ON COUNTRY VERSION INDIA (CIN) AND THE VARIOUS REQUIREMENTS WHICH ARE TO BE COMPLETED UNDER THE INDIAN STATUTE. HOW CIN INTERFACES WITH SAP SD, MM AND FI PROCESSES AND MEETS THE REPORT REQUIREMENTS .
PAÍS VERSIÓN INDIA, PAYS VERSION INDE, 国家版印度
CIN Domain Basic concepts
FI consultant steps in CIN configuration
CIN VS Service Tax
CIN VS TDS
CIN MM Configuration Steps
CIN SD Configuration Steps
J1I9 CIN Number range objects
Master Data for CIN
MM CYCLES
DEPOT PLANTS
CIN TABLES
CIN Forms
CIN NOTES
CIN ACCOUNTING ENTRIES
UTILIZATION
CIN/VAT/TDS/SERVICE -TAX List of Reports
TAXINN VS TAXINJ
CAPITAL Procurement in SAP
SD CYCLES
Miscellaneous Topics
The document is a handbook for SAP taxation in India that covers:
1) The configuration of tax procedures in SAP like TAXINN and TAXINJ and defining tax codes, condition types, and tax accounts.
2) The Indian localisation coverage in SAP which includes taxes like VAT, excise duty, service tax, and TDS.
3) An overview of the CIN (Country Version India) interface with SAP modules like SD, MM, and FI and how it meets Indian reporting requirements.
CIN is used to calculate excise duty and VAT for sales and purchases based on industry requirements. It involves configurations across the FI, MM, and SD modules including maintaining master data like chapter IDs, customer and vendor excise details, and material-chapter combinations. The sales process is enhanced to calculate excise duty for various sales scenarios like sales from factory, depot, stock transfers, and returns. Pricing procedures need to be configured and condition techniques copied for the different excise duty types. Various scenarios and documents need to be reviewed and configurations set through IMG and checking with transaction code J1iLn.
This document provides configuration steps for setting up excise tax functionality for India in an SAP system, including:
- Maintaining excise registrations, company code settings, plant settings, excise groups, series groups, and excise duty indicators
- Selecting the tax calculation procedure
- Defining tax codes for purchasing documents and assigning them to company codes
- Classifying condition types for tax determination
- Specifying G/L accounts for recording different taxes
The document includes detailed instructions for configuring key areas for excise tax management in India within the SAP system.
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
SAP MM IM Physical inventory -cycle countingLokesh Modem
Cycle counting is a process where inventory is counted at regular intervals within a fiscal year to increase accuracy. It can be configured and implemented in SAP. Key steps include defining cycle count indicators, generating physical inventory documents for materials using report MICN, printing documents using MI21, entering counts using MI24, and integrating differences by posting.
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.
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.
The document describes the process for transferring stock internally between plants within the same organization but different company codes. Key steps include a stock transfer requisition created by MRP or a buyer, converting this into a purchase order, picking and shipping material from the supplying plant, receiving at the receiving plant, and billing between the plants. The process requires SAP ERP, and roles such as purchaser, warehouse clerk, and billing administrator are involved.
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
1. An inter-company stock transport order can be used to transfer materials between two plants in different company codes. This involves configuring the supplying and receiving plants, creating a customer and assigning delivery types and document types.
2. To create an inter-company STO, a vendor must be created for the receiving plant and assigned to the supplying plant. The receiving plant must also be created as a customer with the correct sales area. The delivery type, checking rule and document types must then be assigned in customizing.
3. Once configured, an STO can be created to transfer stock from the supplying to receiving plant. A delivery is then generated, goods can be issued and receipted to complete the transfer between the
Gst implementation road map by endeavour technologiesNiranjan Emparala
The document provides an overview of the proposed roadmap for implementing GST in SAP. It discusses key aspects like the GST components, impact on existing tax systems, prerequisites for implementation in SAP, the process for migrating from TAXINJ to TAXINN, required master data changes, tax configuration, business processes, reporting, and the role of GSTN and GSPs in the digital infrastructure. The implementation will require resources across various SAP modules and involve changes to taxation, billing, purchasing, and reporting processes.
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.
The document outlines the 7 steps for factory sales in India which includes: 1) creating a sales order, 2) creating a delivery referenced to the order, 3) creating an invoice referenced to the delivery, 4) creating an excise invoice, 5) updating the RG1 register, 6) extracting the excise registers, and 7) printing the excise registers. Each step lists the associated transaction code to use in the ERP system.
The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive function. Exercise causes chemical changes in the brain that may help protect against mental illness and improve symptoms.
The document discusses SAP's solution approach for implementing the Goods and Services Tax (GST) in India. It outlines the key areas that will be impacted including tax configuration, master data maintenance, business processes, and reporting. The proposed solutions involve enhancements to tax registration, accounts, document numbering, billing and purchasing documents, tax postings, utilization, and registers. Pre-requisites for the solution include using the TAXINN tax procedure and a minimum support pack level.
F070 – Utilization of Credit & Payment of Service TaxFIROZ KHAN
This document provides instructions for utilizing service tax credits and paying the net tax amount in SAP. It includes the process flow, screenshots of key screens, and step-by-step instructions. The process involves simulating credit utilization, paying the tax online, posting the utilization in SAP, and making the outgoing payment. The payment is made by debiting service tax clearing accounts and crediting bank accounts in a journal entry if credits are insufficient.
This document describes the master data requirements for a sales and distribution business blueprint project in SAP for an organization called Pragathi. It outlines 15 different master data elements that need to be configured including customer, material, plant, pricing conditions, and vendor masters. It also describes the client requirements for the master data implementation including authorization rules, legal requirements, and interface needs. The specifications for how these master elements will be modeled and implemented in SAP are provided.
This document provides an overview of excise processes and registers in SAP for Indian excise law. It covers master data setup, procurement and sales processes involving excise duty, key excise registers like RG23A, RG23C and RG1, and reports for monthly returns and tracking unavailed CENVAT credits. Standard SAP transactions are demonstrated for activities like goods receipt, invoice capture, CENVAT posting, register updates and prints.
The document discusses Goods and Services Tax (GST) and its impact on the hotel industry in India. It provides an overview of the current tax structure for hotels, which includes various state and central taxes that result in an overall tax rate of 20-27%. The document outlines the proposed GST structure of 5%, 12%, 18%, and 28% tax slabs. While the 5% tax slab for food is beneficial, there is concern about the 18% tax rate for hotel services being higher than competitor countries. The hotel industry demands a lower 6-8% tax rate under GST. Overall, GST could simplify taxes for hotels but the impact will depend on the final tax rate applied to the industry.
Service taxes india and SAP Configuration (TAXINN)Irfan Shokat
This document describes the SAP configuration required to calculate service taxes in India including service tax, education cess, and secondary education cess. The key steps are:
1. Create new condition types for the taxes and maintain tax procedure TAXINN to use the new types.
2. Create account determination procedures and assign G/L accounts for the taxes.
3. Maintain tax rates for the new condition types by linking them to the existing "ST" tax code in FV11.
4. Create a new "S1" tax code to select on invoices so postings show only the "ST" code as configured in FV11.
This allows invoices to correctly calculate total taxes
SAP offers four services to help customers implement the Goods and Services Tax (GST) in India:
1. Assessment Service to understand the impact of GST on processes and systems and define an implementation approach.
2. Migration Service to migrate tax procedures from TAXINJ to TAXINN.
3. Implementation Service to execute the implementation roadmap with testing and user training.
4. QA and Expert Services to validate the solution design, implementation, and final preparation for go-live.
- The document discusses Goods and Services Tax (GST) in India, including key highlights of GST such as advantages, proposed structure and rates.
- It summarizes STAN's background as a leading assurance and consulting firm in India with a presence across 14 locations, and capabilities in areas such as GST, accounting and consulting.
- STAN has multi-disciplinary professionals and subject matter experts who can provide integrated services to help clients with GST compliance and transformation.
Prepare for your interview with these top 20 SAP FICO interview questions. For more IT Profiles, Sample Resumes, Practice exams, Interview Questions, Live Training and more…visit ITLearnMore – Most Trusted Website for all Learning Needs by Students, Graduates and Working Professionals.
Best IT Online Training Institute. Access video courses anytime, anywhere. High quality, Low Prices, Free Courses, Career Guidance, Tutorials & More in ITLearnMore.com. For more information visit http://www.ITLearnMore.com.
The document is a presentation on customizing SAP for country-specific functionality in India, known as CIN (Country Version India). It discusses setting up excise tax and sales tax functionality to meet Indian statutory requirements. This includes configuring excise registrations, plants, accounts, and transaction types. It also covers customizing logistics areas like materials management and sales and distribution to support features like excise duty calculation and sales tax processing that are required in India. The presentation provides an overview of key areas to customize to implement the tax and regulatory rules for SAP in India.
Here are some key points about FI organizational structure in SAP:
- The top level entity is the client, which represents the company.
- Below the client is the operating concern, which represents the legal entity or group. There can be multiple operating concerns under a client.
- Controlling areas are used to separate responsibilities for planning, budgeting, reporting etc. There can be multiple controlling areas under an operating concern.
- Company codes represent individual companies or plants. They are the lowest level for accounting and are mandatory.
- Business areas can be used to separate divisions, regions etc. for reporting. Multiple business areas can be assigned to a company code.
- Profit centers can be used below
Here are the steps to create the RFQ:
1. Enter your purchase requisition number
2. Select all items
3. Click "Adopt" to copy item details to RFQ
4. Click "Save" to save the RFQ
This will create the RFQ with the item details copied from the purchase requisition. Now you can generate quotations by adding vendors.
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
F073 – Transfer of CENVAT on hold to CENVAT Credit – for Capital GoodsFIROZ KHAN
The document provides instructions for transferring CENVAT credit held for capital goods to the CENVAT credit account in SAP. It outlines the process which includes generating a general ledger report of the CENVAT held account, transferring the selected amounts to the CENVAT credit account, and printing the journal voucher documenting the transfer. Screenshots and detailed steps are provided for each part of the process.
The success of an SAP implementation in Brazil requires careful planning and monitoring of many interdependent elements throughout the rollout. Special focus is needed on the complex Brazilian SAP localization, as Brazil has the most complex localization worldwide. Each country in Latin America has unique localization requirements that affect SAP configuration and implementation efforts. Nota Fiscal electronic invoicing (NF-e) integration and ensuring compliance with various tax obligations are especially important for the Brazilian implementation.
This document discusses setting up a relational database for a department store. It notes that following the store's expansion to new locations, there is a need for an enterprise-wide database to store sales and transaction data, especially with anticipated increased sales from marketing activities. When designing the database, important steps include supporting data accuracy, avoiding redundant data, and enabling enterprise-level reporting. The document discusses defining the relationships between entities like customers, products, sales and stores at varying levels of detail.
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.
PROCUREMENT (MM) CASE STUDY BUAD3050 Information T.docxbriancrawford30935
This document provides an overview and instructions for a case study on procurement (MM) using SAP. It outlines 5 steps to complete a purchase order, receive goods, enter an invoice, post payments, and submit documentation. The steps include creating a purchase order for water bottles and cages from a supplier, receiving the goods, entering the supplier's invoice, and posting a payment to settle the accounts payable balance. Screenshots are to be captured and submitted at the end of each step.
1. The document discusses excise duty configurations and settings in SAP for Indian tax procedures. It covers maintaining excise registrations, registration IDs, plant and company code settings related to excise.
2. It also discusses defining excise groups, series groups, tax calculation procedures, and defaults. Condition-based and formula-based excise determination techniques are covered.
3. Maintaining excise duty indicators, registration numbers, and other excise related data is also summarized.
This document provides instructions on how to create and configure various accounting masters in Tally.ERP9 such as company, ledger accounts, inventory items and units of measurement. It also describes how to enter voucher transactions, generate common reports like trial balance, profit and loss statement, balance sheet, cash flow statement and how to view registers like sales and purchase. Configuring the accounting features and statutory/taxation modules is also briefly outlined.
This document provides instructions on how to create and configure various accounting masters in Tally.ERP9 such as company, ledger accounts, inventory items and units of measurement. It also describes how to enter voucher transactions, generate common reports like trial balance, profit and loss statement, balance sheet, cash flow statement and how to view registers like sales and purchase. Configuring the accounting features and statutory/taxation modules is also briefly outlined.
Document types in SAP define number ranges, account types, and reversal entries. Financial statement versions allow customized reporting outputs. Input and output taxes are managed through tax procedures and codes that can expense or capitalize taxes. Validations and substitutions define rules at the document and line item levels. Configuring document clearing requires accounts with open item management. The GR/IR clearing account is an interim account used for goods receipt and invoice receipt entries.
The process of procurement within the organization is quite complicated. For a smooth procurement process, it is very important to look for a set of tools that can help you to ease the process of procuring. For an effective procurement process, it is the best option to look for procurement software.
The implementation of procurement software helps the organization in supporting the acquisition of goods and services. It allows the organization to automate the entire source-to-pay cycle. Right from the beginning stage of analyzing and managing the contracts and invoice generation procurement to pay software helps to get complete access to control the procurement process operation.
Sathyamoorthy has over 12 years of experience in SAP FICO, including 5 years working on SAP FICO implementations and support projects. They have experience leading workshops to gather AS-IS data and prepare TO-BE documents, as well as performing configuration and customization of SAP FICO submodules like AP, AR, AA, GL, and CO. Currently they are supporting a Leo Pharma implementation and support project in the US on SAP FICO.
The document discusses an Enterprise Resource Planning (ERP) software provided by BizSol Technologies. It provides an overview of ERP systems and describes BizSol's ERP modules including marketing/sales, purchasing, production planning, inventory control, finance/accounting, HR/payroll, and taxes. It highlights features such as integration, customization, real-time data, and automated processes. The document also lists some current customers and provides an implementation plan overview involving project initiation, design/customization, testing, go-live, and post-live support.
This test procedure covers the creation of a billing document with external billing data. Key steps include logging in as a billing clerk, accessing the Test Billing Document Request API app, entering sample external billing data, creating the external billing document request, and accessing the Create Billing Documents app to generate the billing document. The procedure validates that the external billing data is correctly passed through to the billing document.
This document describes a direct subcontracting process in SAP where a subcontractor ships the final product directly to the customer. The key steps are: 1) A sales order triggers a subcontracting purchase order. 2) Components are sent to the subcontractor. 3) The subcontractor sends a shipping notification creating an inbound delivery. 4) Goods receipt of the inbound delivery backflushes the components. 5) The sales order can be billed once goods receipt of the purchase order is complete. The process brings efficiency over a consignment model by allowing earlier billing tied to product receipt.
CIN configuration in SAP refers to country-specific excise duty settings for India. It includes maintaining excise registration IDs, excise groups, plant settings, and company code settings related to excise invoices, CENVAT credits, and accounting. Excise groups allow separate excise registers and accounts to be maintained for different parts of a business. Plant and company code settings control excise invoice generation and accounting at different sites.
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfChart Kalyan
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
Main news related to the CCS TSI 2023 (2023/1695)Jakub Marek
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
This presentation provides valuable insights into effective cost-saving techniques on AWS. Learn how to optimize your AWS resources by rightsizing, increasing elasticity, picking the right storage class, and choosing the best pricing model. Additionally, discover essential governance mechanisms to ensure continuous cost efficiency. Whether you are new to AWS or an experienced user, this presentation provides clear and practical tips to help you reduce your cloud costs and get the most out of your budget.
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Ocean lotus Threat actors project by John Sitima 2024 (1).pptxSitimaJohn
Ocean Lotus cyber threat actors represent a sophisticated, persistent, and politically motivated group that poses a significant risk to organizations and individuals in the Southeast Asian region. Their continuous evolution and adaptability underscore the need for robust cybersecurity measures and international cooperation to identify and mitigate the threats posed by such advanced persistent threat groups.
GraphRAG for Life Science to increase LLM accuracyTomaz Bratanic
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
Letter and Document Automation for Bonterra Impact Management (fka Social Sol...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on automated letter generation for Bonterra Impact Management using Google Workspace or Microsoft 365.
Interested in deploying letter generation automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...Tatiana Kojar
Skybuffer AI, built on the robust SAP Business Technology Platform (SAP BTP), is the latest and most advanced version of our AI development, reaffirming our commitment to delivering top-tier AI solutions. Skybuffer AI harnesses all the innovative capabilities of the SAP BTP in the AI domain, from Conversational AI to cutting-edge Generative AI and Retrieval-Augmented Generation (RAG). It also helps SAP customers safeguard their investments into SAP Conversational AI and ensure a seamless, one-click transition to SAP Business AI.
With Skybuffer AI, various AI models can be integrated into a single communication channel such as Microsoft Teams. This integration empowers business users with insights drawn from SAP backend systems, enterprise documents, and the expansive knowledge of Generative AI. And the best part of it is that it is all managed through our intuitive no-code Action Server interface, requiring no extensive coding knowledge and making the advanced AI accessible to more users.
Trusted Execution Environment for Decentralized Process MiningLucaBarbaro3
Presentation of the paper "Trusted Execution Environment for Decentralized Process Mining" given during the CAiSE 2024 Conference in Cyprus on June 7, 2024.
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Depot sales
1. 8/9/12 Community Network Wiki - ERP Manufacturing (PP) - Depot Activities - CIN
SAP
Welcome, Guest
Login
Register
Getting Started
Newsletters
Store
Search the Community
Solutions
SAP Services & Support
About SCN
Downloads
Industries
Training & Education
Partnership
Developer Center
Lines of Business
University Alliances
Events & Webinars
Idea Place
Depot Activities - CIN
Added by Prashanth@SD, last edited by Alon Mizrahi on Nov 07, 2011
Depot Activities - CIN Useful Information
Depot Sales process, RG23 D, Excise
Summary Registers, J1IG, J1IJ,
Depot activities are mainly performed for trading material purchase and sale and sale of material transferred from factory.
Author(s):
Company: YASH Technologies
Created on: 13-01-2011
Author(s) Bio
Prashanth Gaddam is SD Consultant at Yash Technologies Pvt Ltd. He has 10 years work experience, including 7.6 years
functional experience (like Sales officer and Sales Manager) in pharmaceutical industry and 2.6 years in SAP Implementation, Roll-
out and support.
Table of Contents
Depot Activities - CIN
Summary
Author(s):
Header 1
Purpose
Master Data
Required Primary Steps
Process Overview
Related Content
Purpose.
Prerequisite.
Master Data.
Required Primary Steps
Process Steps
Process Overview Table.
Scenario:
Goods Receipt of Stock Transferred material at Depot.
Excise Duty capture against Goods Receipt.
Depot Excise Invoice generation and Post Excise Duty for Clearance.
Display of Depot Stock and Excise Duty Balance.
RG23 D Register Extraction.
Print RG23 D Register
Header 1
Purpose
Depot or Dealer activities are mainly performed for trading material purchase and sale and sale of material transferred from
factory.
wiki.sdn.sap.com/wiki/display/ERPMan/Depot+Activities+-+CIN#DepotActivities-CIN-RequiredPrim… 1/4
2. 8/9/12 Community Network Wiki - ERP Manufacturing (PP) - Depot Activities - CIN
SAP
factory.
There are two aspects of Depot / Dealer scenario:
1. Domestic as well as Import trading material is directly received at Depot / Dealer’s premises for subsequent sale.
2. Stock transferred from factory in bulk and the same will be sold from Depot / Dealer’s premises as and when there is a
demand from Customer as a Part or Full consignment considering various factors of factory, Depot / Dealer’s and Customer’s
location, time period, transportation, taxation etc.
Entries of receipt and issues at Depot / Dealer’s are accounted in RG23 D Register.
Master Data
Material Master
CIN Master
Required Primary Steps
P.O. of Trading Material
Outbound Delivery of Stock Transfer
Process Overview
STEP
Step Name
Business Condition
T code
Results
Goods Receipt of Stock transferred Material at Depot/DealerThis activity is performed to account the Goods Receipt at Depot/
Dealers against Stock Transfer outbound deliveryMIGO
Goods Receipt and material document is generated
Excise Duty capture against Goods Receipt.This activity is performed to Capture Excise Duty in RG23 D Register against Goods
Receipt.J1IG
RG23 D Register entry is updated and Internal Document is generated.
Depot Excise Invoice generation and Post Excise Duty for sale.This activity is performed to generate Depot Excise Invoice and
Post the Excise Duty element against sale.J1IJ
Depot Excise Invoice is generated. RG23 D Register entry is accounted.
Display of Depot Stock with Excise Duty Balances and Entry StatusThis activity is performed to see the Depot Stock with Excise
Duty Balances with the posting status.J1IDEPOTSTOCK1.Depot Stock with Excise Duty balance and Status will be displayed.
Extraction of RG23 D Register.This activity is performed to Extract the entries into RG23 D RegisterJ2I5Entries are extracted in
Rg23D register.
Print RG23 D RegisterTo take print of RG23 D RegisterJ2I6RG23 D Register is printed.
Goods Receipt of Stock Transferred material at Depot.
Use
This activity is performed to account the Goods Receipt of Stock Transferred material.
Prerequisite
Delivery Order
Excise Invoice
Procedure
Easy Access PathLogistics > Logistics Execution > Inbound Process > Goods Receipt for Purchase Order, Order, Other
Transactions > Enter Goods Receipt for Purchase OrderTransaction CodeMIGO
On the initial screen, ensure that the Goods Receipt and Outbound Delivery are selected in the fields on the top of the screen and
press Enter.
Enter Outbound Delivery Order (Stock Transfer Delivery Order) and press Enter. Ensure that the movement type in Where tab is
101.
Check the details, in case of change in Quantity , change the same in Quantity tab, or any other details appearing in Where tab,
Tick on Item OK ,
and press Enter. In Excise Invoice tab, select “06 No Excise Entry”, and click on button, system will display the message as ,
Document is OK click
on POST button to post the document.
Excise Duty capture against Goods Receipt.
Use
This activity is performed to capture Excise Duty in RG23 D Register against Goods Receipt.
Prerequisites
Goods Receipt Material Document.
Procedure
Access the transaction choosing one of the following navigation options:
Easy Access PathSAP Easy Access India Localization Menu (J1ILN) > Indirect Taxes > Procurement > Excise Invoice > For
DepotTransaction CodeJ1IG
In the initial screen, Click on Capture button or press F5 key. On next screen, enter the Excise Group and Material Document
as Goods Receipt and Material document year and press Enter. You can also enter Excise Invoice No. and date. You will see the
details of Purchase Order No and other details as per the material document. Click on Details button. On next screen,
For Stock Transfer Goods Receipt, enter Internal Excise Document Number and Year, Internal Excise Document Number is
generated at supplying plant at the time of Excise Invoice creation. Excise Duty element, will be captured from the
wiki.sdn.sap.com/wiki/display/ERPMan/Depot+Activities+-+CIN#DepotActivities-CIN-RequiredPrim… 2/4
3. 8/9/12 Community Network Wiki - ERP Manufacturing (PP) - Depot Activities - CIN
SAP
Internal Excise No., check the same and click on Save button.
In case of non availability of Internal Excise No., select the line item and click on MORE DOCUMENTS button. On next screen,
enter Excise Inv. No.,
Date, Challan Qty, Excise Base value, ensure that Excise Duty rates are maintained in respective duty rates column, you can also
manually enter the excise duty amount and press Enter. System will give warning messages, press Enter for each message and
press Back button.
System will display the excise duty amount, check the same and click on Save button.
Result
RG23 D Register entry is updated and Internal Document No. is generated.
Depot Excise Invoice generation and Post Excise Duty for Clearance.
Use
This activity is performed to generate Depot Excise Invoice and to post Excise Duty for sale.
Prerequisite
Delivery Order is created.
Procedure
Access the transaction choosing one of the following navigation options:
Easy Access Path
SAP Easy Access India Localization Menu (J1ILN) > Indirect Taxes > Sales/Outbound Movements Excise Invoice > For Depot
Transaction Code
J1IJ
In the initial screen, select RG23D Selection from Main Menu – “Delivery”. Enter Delivery Order No. in Delivery,
Excise Group and Series Group and press Enter. On next screen, Delivery Order details will be displayed on screen,
select the line item and Click on Details button or press F6 key. On next screen, Click on Excise Invoice button.
Mother Invoice details against which you have captured the Excise Duty element will be displayed.
Select the line and Click on Continue button, on next screen press Enter. Proportionate Excise Duty for Quantity to
be sold will be calculated by system and displayed on screen which will be passed on to customer. Click on Save button.
Result
Depot Excise Invoice will be generated and Rg23 D Register entry is updated.
Display of Depot Stock and Excise Duty Balance.
Use
This activity is performed to see the Material wise Depot Stock with Excise Duty Balances with the entry status.
Prerequisite
Procedure
Access the transaction choosing one of the following navigation options:
Easy Access PathSAP Easy Access India Localization Menu (J1ILN) > Indirect Taxes > Sales/Outbound Movements Excise
Invoice > For DepotTransaction CodeJ1IDEPOTSTOCK1
On the initial screen, enter either Plant or Excise Group. Select Output Format as “ABAP list” and press Execute. Depot Stock can
be also seen for a specific material to be entered in “Material number” Field.
Result
Material wise Depot Stock with Excise Balance and Rg23 D Register entries are displayed with status.
Status Indicators:
In Process
C
Completed
D
Deleted
P
Posted
R
Reversed
B
Canceled
RG23 D Register Extraction
Use
This activity is performed to extract the RG23 D Register Entries from CIN Table.
Prerequisite
Entries are updated in RG23 D Register.
Procedure
Access the transaction choosing one of the following navigation options:
Easy Access PathSAP Easy Access India Localization Menu (J1ILN) > Indirect Taxes > Registers > Excise TaxTransaction
CodeJ2I5
In the Initial Screen, enter Excise group, Start date, End date and Select RG23 D Register and press Execute .
If already extracted, system will ask for confirmation of Re-Extraction. Click on YES button, since system
overwrite the data. System displays the Register extracted with OK Button.
Result
wiki.sdn.sap.com/wiki/display/ERPMan/Depot+Activities+-+CIN#DepotActivities-CIN-RequiredPrim… 3/4
4. 8/9/12 Community Network Wiki - ERP Manufacturing (PP) - Depot Activities - CIN
SAP
RG23 D Register is extracted.
Print RG23 D Register
Use
This activity is performed to take printout of RG23 D Register.
Prerequisite
Entries are updated and extracted in respective RG23 D Register.
Procedure
Access the transaction choosing one of the following navigation options:
Easy Access PathSAP Easy Access India Localization Menu (J1ILN) > Indirect Taxes > Registers > Excise Tax
Transaction Code
J2I6In the Initial Screen, Select RG23 D Register and press Execute. In next screen enter Excise Group, Start Date, End Date and
press Execute.
In next screen, enter Output Device, Enter Number of Copies, Tick in Print immediately box and click on Print Button. To see the
print preview,
click on Print Preview Button.
Result
RG23 D Register is printed.
Error formatting macro: highlighter: com.atlassian.core.exception.InfrastructureException: Error occurred rendering template
content
Related Content
Please include at least three references to SDN documents or web pages.
Reference 1
Reference 2
Reference 3
Labels
standard template document paper article
Follow SCN
Contact Us
SAP Help Portal
Privacy
Terms of Use
Legal Disclosure
Copyright
wiki.sdn.sap.com/wiki/display/ERPMan/Depot+Activities+-+CIN#DepotActivities-CIN-RequiredPrim… 4/4