This document highlights some factors and benefits of the solution GuiXT, along with few ROI cases...
Enhancements
Reduce training time and increase user comprehension
Change standard ERP terminology to those your organization's pervasive business terms, thus eliminating ambiguity and uncertainty
Reduce manual data entry by automating redundancies
Increase productivity, efficiency, and data integrity
Rearrange your ERP tabs and fields to match those of your internal processes
Hide unused fields and create validations for all of the fields necessary to achieve a complete set of mandatory data
Increase speed, ease of navigation, and ensure a comprehensive data footprint
Consolidate multiple tabs and screens within your transactions and create a streamlined and easy to navigate environment
Consolidate multiple transactions into one screen and ensure that users provide all necessary data without expending extra effort
Benefits
Increase in productivity creates direct Full Time Employee (FTE) benefits thereby enabling a redeployment of resources to other areas of this business
Increase in efficiency improves employee experience and reduces training and retraining burden from the company and management
Speed, clarity, and ease of navigation creates enhanced customer satisfaction and leads to more happy and reference-able clients
Automation and validation reduces the time required to navigate through systems and ensures a more comprehensive data set for management reporting
Consolidation and streamlining creates a cleaner and more scalable environment that is more conducive to retention of existing workforce without the need for additional resource expenditure
Survival of enhancements through upgrades ensures that your investment is preserved and additional resources are used for additional enhancements
Ease and speed of deployment ensures that you can create a multitude of enhancements in a very short time with near immediate results
GuiXT can enable Mobile, Web, and Offline environments for your SAP ERP application in addition to the traditional SAP GUI
ROI - Case 1
Canada Post optimizes HR Appraisal process using GuiXT.
CHALLENGES
There are no employee names or numbers on the initial PPPM or PPPD screens, making it impossible to differentiate between the appraisals listed without clicking on additional icons to go to another screen
As more and more appraisals are tied to a People Manager, it became more time consuming to find a specific appraisal
There were problems with ensuring correct appraisals were displayed/updated without having the personnel number of the Line Manager and employee indicated on the individual appraisal screen
RESULTS
Canada Post cited that using GuiXT increases productivity and user satisfaction by simplifying the screens and streamlining the processes. Through GuiXT, Canada Post can reduce training costs and eliminate the usability barrier between the users and the business processes
There was need to make SAP transactions available on hand-held devices
Goal was to keep development to a minimum level
RESULTS
GuiXT and GuiXT Mobile enhanced Steelscape’s user interfaces, improved employee productivity, and facilitated better shipment tracking. Steelscape processes about 3000 scans a day, using about 200 man hours. With GuiXT, that is reduced to 17 man hours (12X faster)
SAP System Audit - Post Implementation Audit - Part 1
Author: Ranjit Simon John
One of the main challange faced by companies that has implemented SAP ERP (any ERP) will be to get a clear understanding of the current ERP system. Two or three years after implementation what will be status of the system.
The main areas of focus will be;
- Whether all the management controls are working fine
- Whether all the postings are being done as per accounting standards
- Whether proper documentation is being maintained
- Whether critical business related activites are done accurately etc.
A lot of practical difficulties arise in doing a ERP post implementation audit. Main challange is to frame the right set of questions and how to obtain answers for those. From my experience and research, I have prepared a question list of more than 500 questions both from the functional and technical side, which drill downs to the minutest level providing all the necessary data required for the audit.
SAP has provided a very powerful framework in the standard ERP package for conducting Audits, evaluvating them and taking corrective actions.
In this article I will explain how to set up the audit components, prepare audit and question list in SAP. Before starting the Audit user must have a clear understanding on the end result to be achieved from the audit.
User should have answer for the following questions before starting the Audit procedure;
Kindl of Audit to be Conducted (Technical or Functional)
Number of questions for the Audit
Structure of list of Questions (Question drill down level)
Valuation type of Questions
Question Priorites
What kind of Audit Controls to be implemented
Audit purpose
Audit Type
Kind of rating for the questions
First we need to do few configuration changes to tune the audit as per our requirement.
Once the question profile is created you have to create the drill down level for the profile. Below attached is the pictorial representation of the drill down level for questions I created.
Similarly you can create drill down level according to your requirement. After defining the question hirerachy you have to specify the Valuation Specification and the scores to be awared for each value.
I have created valuation 8003 Valuation of PRD system. By selecting the created valuation profile double click on the "valuation" icon on the right side. There we need to set the details of valuation and the scores we intend to provide for each.
Now all the configuration related to conducting the Audit has been configured. Now we have to create Audit, Audit Plan, Question List.
Following are the main objects used for the Audit;
1) Audit Plan
The audit plan consists of all auditsplanned for a particular period of time. For example, all audits that are to be executed in the space of one year are defined in an annual audit plan. There is always only one current version of an audit plan, where all date shifts and the degree of completion for the individual audits can be found.
2) Audit
An audit, according to DIN EN ISO 9000, is a systematic, independent, and documented process used to obtain audit results and to evaluate these results objectively in order to determine to what extent the criteria of the audit have been fulfilled.
3) Question List
Question lists are multilingual collections of questions that are answered during the execution of the audit. The allowed valuation can be planned for each hierarchy level.
4) Corrective Actions
These are actions that are deemed necessary to eliminate the cause of errors that were determined during the audit and to prevent the recursion of these errors. The corrective actions to be executed must be appropriate to the effects that the particular error has on the product.
5) Preventive Actions
These are actions that are deemed necessary to eliminate the causes of possible errors before they occur. The preventive actions to be executed must be appropriate to the effects that the possible error could have on the product.
An audit, according to DIN EN ISO 9000, is a systematic, independent, and documented process used to obtain audit results and to evaluate these results objectively in order to determine to what extent the criteria of the audit have been fulfilled.
Execute transaction PLMD_AUDIT, first create the question list required for the audit with the components newly configured.
The main success factor for any audit depends on the questions used for the audit. Let me add few of the topics under which I have prepared the question list.
The main topics are;
System Overview
Security & Access Protection
Workbench Organizer
Transport System
Accessing and Logging DB Tables
Job Request Procedure
Documentations
System Logs
Batch Input Interface
Master Data Changes
Reconciling Posting Data Closing
Invoice Checking and Posting Run
Business Process Auditing
BASIS Audit
Once the audit question list is created / uploaded to SAP\, user must create a sample set of check list to be submitted to the client. The Check list should contain;
* All the documents that client has to Submit
* All the questions client has to answer.
Every company should run the audit at least twice a year to ensure that the system is working perfectly, no manipulations are done, to ensure 100% management control over the system ther by over the employees.
This article provides the user with the technique for creating quick reports on any function through SAP query and the procedure to transport these reports across clients. This is a useful technique for beginners with no background on queries.
Article: Availability Check and Batch Management for a Process/Chemical Industry - A SAP R/3 solution approach
Summary: Article describes the key points to consider while in the Availabilty-To-Promise strategy for a Process based or Chemical industry.
Author: Naveena Advani
Created on: 27th June, 2013
Author Bio: Naveen is Lead Consultant at Infosys and has over 9 years of professional work experience in SAP sales and Distribution. He has vast experience on various implementations and Rollouts for chemical, auto ancillary industry. His expertise is in processes in the Market to Sales, Order to Cash, Procure to Pay and Integrated Planning. Naveen is engineering graduate and post graduate in Management. He is alumni of Indian Institute of Technology – Roorkee. Naveen would like to thank his team members Vijay Vittal, Srinivas Kumar and Sajith Hari for their contribution towards this article
Introduction
The Prime benifits for a Chemical/Pharamaceutical Organisations by SAP ECC implementations are listed as below
it assists in optimizing their business processes,
it is a full solution therefore reducing the time and effort required to develop such a system, and it gives companies a high level of return on their investment.
Most common process based manufacturing practices around chemical industry developed a SAP R/3 solution that resolves some of the key chemical industry issues with SAP R/3 and increases the return on investment.
Key Issues/Challanges
How can an organisation best manage multiple batch (lot) materials within SAP based ERP when there is no batch split functionality on the sales order?
How do supply chain department determine true available to promise inventory when the products are overlapping specifications?
How can Inventory management prioritize finished goods inventory and maximize its efficiency in order to best meet customers’ requirements and expectations?
How can Logistics execution ensure the warehouseis choosing the material best fit for customers and work on a first in first out (FIFO) basis?
How to restrict certain batches only in certain countries due to varying regulations
The SAP run chemical Organisations normally develop or enhances the SAP ECC package to solve the above issues and meet the chemical industry’s specific finished goods batch management needs in order to best meet customer requirements. The solution includes the following processes:
Receiving finished goods from production
Testing and grading the properties of the finished goods
Prioritization of inventory through material grading
Recording the test/grade results on the produced batches
Material movements associated with material testing
Placing the product in the warehouse/tank farm
Configuring PI (Process Instructions) sheets and integrating the PI sheets with RFID devices to record the results.
True available to promise inventory on sales orders based upon classification characteristics (customer specifications) to prioritize inventory
Picking the best product (batches) to meet the customer’s requirements at time of delivery
Simplified warehouse movements through enhanced front end screens and SAP console devices to confirm WM movements.
Creation of Certificates of Analysis and customer bar code labels out of SAP ECC
The key process is to allow availability checking on batch managed material based upon characteristics within the SAP ECC Classification system. This enhancement allows organisations to determine their true available to promise position for a customer without hard allocation of batches to a sales order at the time of order entry. Instead, through an enhanced inventory prioritization, availability checking, picking strategy and picklist, the batches are not allocated to the order until the shipment is picked for delivery. This enhancement would have to be acheived utilizing user exits within the R/3 system.
Why the Solution is Necessary
The key to success on implementation of such solutions thorough gap analyis be performed. The gap analysis is to determine where further development was necessary to meet the business needs. In assessment of the software/ERP application, a system agnostic, holistic end-to-end perspective must be carried out. It is very common gap in process based industry especially the problem on how R/3 allocated material to an order and performed the availability checking process for single material/multiple batch orders.
Although the standard SAP solution does include functionality to select material for a customer order based upon specifications; this functionality is limited when it comes to processing orders with multiple batches. In fact, R/3 requires creation of a separate sales order line item for each batch that needed to commit customer. This is partly due to the Sales & Distribution system(of SAP) not having batch split capabilities on the order. Not only does this add time and effort to the process of order taking; it also hard allocates those batches to an order, limiting the inventory flexibility. In some organisations the orders are large(bulk) contract orders and batches are not known at the time of order entry.
Many Organisaitons in the chemical industry produce individual products that have different specifications for various customers. Many of these specifications overlap or are subsets of another specification. The standard SAP solution would choose any material within the customer’s specification with no regard for the priority or importance of the inventory. Here is an example of that depicts the impact:
Chem Industries produces a product with two specifications. The regular specification that most customers use has a wide range for its key characteristics. The other specification is a narrow, subset of the wide specification used by a single customer. Using standard R/3, the narrow specification material could and would be shipped to regular customers without regard for priority. This could leave without any material that a narrow specification customer could use.
This is a type of situation that can be avoided by using the enhanced availability check solution. With the solution, the above scenario would be:
Chem Industries produces a product with two specifications. The regular specification that most customers use has a wide range for its key characteristics. The other specification is a narrow, subset of the wide specification used by a single customer. Using the enhanced R/3 chemical solution, the inventory is prioritized. When a regular specification customer orders material, the material that meets only the wide specification is soft allocated at the batch level to the customer, leaving the narrow specification material for future orders from the narrow specification customer. The narrow specification material will only be soft committed to a regular customer when the material outside the narrow specification is not available.
Integrated Solution Approach
As mentioned in the introduction, this solution for the chemical industry starts at the end of the production line, and goes through product testing, warehouse putaway, sales, picking and delivery. It includes the following R/3 Modules and Applications:
The typical chemical industry solution includes the following functions:
Data collection integration– An external interface receives production data from factory/shop floor data collection system and creates the appropriate movements within the R/3 system as well as collecting key production information for the classification system. This also includes integration to warehouse putaway if you plan to utilize the Warehouse Management application. PP/PI integration with WM is a great functionality SAP offers.
Quality data integration– with or without LIMS (laboratory information management system) and with or without the QM module – Depending upon laboratory system and decision to use R/3’s Quality Management module, this piece of the solution either uses pre-configured standard SAP functionality or a customized interface to get your production quality data into the SAP ECC Classification System.
Warehouse putaway strategies and screen enhancements– The solution includes the ability to utilize any of the standard warehousing strategies within SAP. In addition, screen enhancements would be of a great value and provides rich user experience in warehouse processing. These enhancements include the ability to easily move multiple batches on a single screen. It is also set up for integration to bar code scanning equipment.
Availability checking enhancement– This type of enhancement will allow availability checking to the “grade” (customer specification) or classification characteristic level. This enhancement does not replace the SAP standard availability checking functionality, but instead works in conjunction with it to add functionality.
Like the standard availability check, the ATP quantity (ATP = Available To Promise) is calculated from the warehouse stock, the planned inward movements of stock (production orders, purchase orders, planned orders) and the planned outward movements of stock (sales orders, deliveries, reservations). This type of check is performed dynamically each time, taking the relevant stock and planned goods movements into account with or without replenishment lead time. The additional functionality of the enhancement is that it classifies the inventory by “grade” and passes each order requirement against the classified inventory “on the fly”.
The availability check enhancement does not “commit” any batches to the order, yet still reserves the inventory with the best fit for that customer order. This commitment is executed using an algorithm that keeps the higher priority and multi-grade material for the customers that require it. This “soft commit” allows warehouse flexibility and facilitates the improved warehouse picking described in the next section.
Some of the key features of the enhanced availability checking include:
· Intelligent (manual) prioritization of inventory based upon customer specification requirements and capability to produce
· Prevents “wrong reservation” of inventory by Customer Service Representatives from a committed order without supervisor approval
· Allows real-time commitment to a customer over the phone that their order can be filled with inventory that meets their specification.
Warehouse picking strategies, forms (picklist) and screen enhancements–
The warehouse picking strategies and picklist work very much like the enhanced availability checking functionality. It uses the same algorithm as the availability check to create the picklist. The enhanced picklist automatically generates a group of batches to pick for a particular order based upon criteria such as batch “value” and age. By generating a group of batches from which to pick and not specific batches, you can reduce the warehouse effort of digging for batches while still meeting your customers’ requirements.
In addition, simplified warehouse data entry screens can be developed to streamline the process of entering the picked batches into SAP ECC. Within these screens, validation would be recommended to ensure that the batches that were picked are either on the picklist or at least meet the customer’s requirements. When a batch selected does not appear on the picklist (but does meet customer requirements), an exception handling needs to be implemented. This process not only allows flexibility in warehouse processing, but also enforces discipline.
Delivery strategies and forms(Certificate of Analysis, Bill of Lading, Bar Code Labels) – This kind of design allows to print quality certificates out of LIMS or SAP, depending upon the preference. It also includes customized Bill of Lading forms and customer bar code labels printed from SAP.
Uses of the Solution
This solution can add value to a batch managed Organisation. This section describes the situations in which the specific programming enhancements described above (availability check, warehousing, and picking) are designed to be used. It is in these situations that this solution fills in “gaps” in SAP R/3’s functionality.
Multiple, overlapping product/customer specifications– As described above, it allows availability checking to the customer specification level based upon inventory prioritization. These companies will also get the full benefit of the improved picking and warehouse functionality.
Single material/multiple batches per sales order line item– The solution also add value to companies with single material/multiple batches that do not have multiple specifications. In this scenario, enhanced availability checking is no longer required. The material is either good or outside of the specification limits. With only one specification, standard R/3 availability checking is sufficient with proper quality data integration.
The added value is in the improved inventory and warehouse management. The solution prioritizes inventory to be delivered to customers using optimal date and location algorithm processing.
Assumptions
There are several assumptions associated with this type of solution. These assumptions include:
The definition of a batch matches SAP’s definition . A batch is a quantity of material produced during a given cycle of manufacture. The essence of a batch is therefore its homogeneity (according to Good Manufacturing Practice Guidelines). A batch is a non-reproducible unit. It is characterized by unique features. In current scenario, 1 batch = 1 pallet or 1 tank or 1 container.
Batch is client specific and is unique to the material
The solution utilizes the classification system as a database for the finished goods batch quality data.
The solution includes business process designs, configuration and programming.
The modules included in the solution are MM (with WM), SD, CA – Classification and QM. There is also a solution without the QM module.
My client is facing huge increase on table TST03 due to frequent use of spool data, and this is starting to affect performance of the production system.
Although currently it is fine with deleting spool data after 10 days by house keeping job,
I believe once user increase (when other entities get into production later), start using the system and output spool,
it will result in worse performance for the system.
If anyone experienced a system using a huge number of spool data,
can you advise me what kind of action you took for this?
Here are some details.
System: SAP ERP 7.2
Quantity of Spool Data: Around 7,000 per day (80% of these are immediate output from smartforms)
The current size of table TST03: 90GB (DB total is 300GB)
All Enterprise Resource Planning implementation initiatives.
Summary
This paper signifies the need of undertaking a due diligence activity by any organization before considering an ERP implementation. This will allow them to leverage the outcome of this activity in making a more considerate and beneficial decision on an ERP implementation.
Author(s): Sachin Rao
Company: Barclays Bank Plc
Created on: August 25, 20112011
Author Bio
Sachin a Mechanical Engineer by education has been in the field of SAP consulting for over 8 years, having core expertise in the modules of SRM, MM and WM. He has worked on several projects in SAP comprising implementation, roll-outs and support engagements. He has a good understanding of the business and its drivers especially in Automobile, Chemicals and Petroleum and Banking Domain. He has is also the author of the whitepaper ‘Need of Post Implementation Audits for ERP Implementation’.
Introduction
The success of any Enterprise Resource Planning (ERP) implementation in-terms of the operational and strategic value it brings to the organization, the benefits it realizes and the return on investment (ROI) is largely determined before the implementation starts.
This is an astonishing statement but true, the companies who have plans of implementing an ERP package should give a thought on the core benefits and reasons they want to get at the other end of implementation. This should begin well ahead of the implementation cycle, even before the ERP package and the implementation partner is identified.
Most of the failure in an ERP implementation has been more or less due the following reasons
§ Lack of specific goals and metrics
§ Users resistant to the new system
§ Users under-trained
§ Limited resources dedicated to implementation
Due Diligence
The dictionary meaning - ‘An investigation or audit of a potential investment’.
Generally, due diligence refers to the care a reasonable person should take before entering into an agreement or a transaction with another party.
Any company thinking in terms of a new ERP implementation has to be clear as to what it is expecting from having this task undertaken and the value for money spent on such implementation. Choosing to implement an ERP system can be a complex and time-consuming process; organizations should take a detailed look at their position, needs, and interests before going forward with planning an ERP implementation. In order to take into account the real need, benefits and core impact of implementation, one needs to undertake the activity of due diligence.
There are a number of indicators that signal when a company should consider implementing an ERP system:
§ Uncontrolled and rapid growth
§ Poor inventory control mechanism
§ Lack of process co-ordination
§ Failure to meet customer needs or expectations
§ Inconsistent delivery schedules
§ Inaccuracy in forecasting
§ Difficulties assessing financial health
§ Inaccurate or unknown Employee costs
But many of the times it is seen that a company gets into implementation for one of the following reasons which should not be the only determining factor to decide for an ERP implementation and hence the need for due diligence.
- Our current system is not good enough to meet the current business needs and will require a lot of customization to keep it going
- We are running out of support for the existing ERP package / the cost of keeping the existing package is more than implementing a new one
- We have substantial budget this fiscal and want to spend it on a new implementation of ERP
As we know that each and every business is completely unique, and identifying which specific business conditions and processes need to be integrated or improved will ultimately determine if a system is necessary. The ERP package which may be built on any technology should fit the existing business process model, but not the other way around.
Due Diligence key Areas
The company that is undertaking this activity should at the end have answers for most if not all of the questions from the list. The in-depth insight that each answers gives will vary based on the interest and the type of business the company is interested in. Moreover the domain in which the business is operating will determine which questions need to be answered and to what extent. The questions which need to be dodged is the complete prerogative of the business under consideration.
Below is the list of probable questions which will have to be answered by any company to get a clearer understanding on the real need, benefits and core impact of an ERP implementation.
o Why do we need this implementation?
This may seem to be an open ended question, forcing the company to think in various directions, which is a good start. This will give them an opportunity to list out all the points they would want to bring to the table and justify the need of going for the implementation. A clear understanding on the priority of the points listed and which they wish to accomplish can be listed. This will give clarity on the factors that can be accomplished with the implementation. Some of the probing questions which can be listed are as below,
· Enhance productivity, flexibility and customer responsiveness
· Enable new business and growth strategies
· Eliminate costs and inefficiencies
· Extend business using the Internet
o Which are the pain points that will be addressed with the implementation?
During the listing and prioritizing the factors which are compelling and directing for taking up the new initiative of implementation there will be some of the points which will qualify to be in the list by the virtue of being a pain point. These pain points need to be seen in the light of any business impact it makes or reduces the efficiency of a business process which can be eliminated or more efficiently managed with the development of a new process or deploying an ERP package.
o What benefits / returns are expected from and after this implementation?
· Improve alignment of Corporate strategies and business operations
· Improve overall productivity
· Reduce costs through increased flexibility
· Improve financial management and corporate governance
· Reduce risk across business
· Gain higher ROI faster
· Bring transparency in the business process
· Support dynamically changing industry requirements
o Who are the stake holders who will be affected from this change?
An organization which intends to implement ERP will need to identify and understand the stakeholders involved and how they contribute to the success or failure of the project. Broadly, the stakeholders can be categorized as below. The need to assign ownership with clear roles and responsibilities for each is a must
· Executives and upper management
· Departmental personnel such as middle management, procurement, and sales team
· The IT department
· Any other functions in the organization who are affected by the process changes
Due Diligence Activity Deliverables
Once the key areas are taken into account and all the outstanding questions and clarifications are complete, then all the activities carried out have to be consolidated as an approach document. Some of the points that needs to be highlighted are as below
· Business Overview
· Pain Areas
· Business Process Improvements
· Measurable Specifics of improvement
· Cost Benefits
· Long term benefits to the organization.
· Road Map to accommodate future growth
· Prerequisites for ERP package implementation
o Process to identify the ERP package
o Evaluation process for selection of Implementation Partner
Conclusion
The Due Diligence activities should be conducted by a service provider who should be a purely consulting firm and who should preferably not have any presence in the ERP implementation services. The only justification for this statement is that it may lead to a biased approach which will defeat the basic purpose of Due Diligence as one needs to have an open view during and at the end of this activity.
It would be better to seek the expertise of an independent consultant in the Supply Chain Management [SCM] area or a service provider having rich consulting experience pool. Consultants with specialized certifications in Supply Chain or with minimum of 10 years of experience in SCM would be best fit for conducting such due diligence. They will not only have a sound knowledge in the area but call also suggest core changes / inputs to the business process which will augment the overall efficiency and effectiveness of the business through ERP implementations.
Key feature of any ERP implementations
After the due diligence activity if the outcome justifies for going ahead with the ERP implementation the following should to be kept in mind
ERP initiatives are always very challenging and demanding
Business process re-engineering should happen before, not after, you implement your ERP software
ERP is about your business, not only technology
Selecting the right software is the first step in a successful ERP implementation
SAP System Audit - Post Implementation Audit - Part 1
Author: Ranjit Simon John
One of the main challange faced by companies that has implemented SAP ERP (any ERP) will be to get a clear understanding of the current ERP system. Two or three years after implementation what will be status of the system.
The main areas of focus will be;
- Whether all the management controls are working fine
- Whether all the postings are being done as per accounting standards
- Whether proper documentation is being maintained
- Whether critical business related activites are done accurately etc.
A lot of practical difficulties arise in doing a ERP post implementation audit. Main challange is to frame the right set of questions and how to obtain answers for those. From my experience and research, I have prepared a question list of more than 500 questions both from the functional and technical side, which drill downs to the minutest level providing all the necessary data required for the audit.
SAP has provided a very powerful framework in the standard ERP package for conducting Audits, evaluvating them and taking corrective actions.
In this article I will explain how to set up the audit components, prepare audit and question list in SAP. Before starting the Audit user must have a clear understanding on the end result to be achieved from the audit.
User should have answer for the following questions before starting the Audit procedure;
Kindl of Audit to be Conducted (Technical or Functional)
Number of questions for the Audit
Structure of list of Questions (Question drill down level)
Valuation type of Questions
Question Priorites
What kind of Audit Controls to be implemented
Audit purpose
Audit Type
Kind of rating for the questions
First we need to do few configuration changes to tune the audit as per our requirement.
Once the question profile is created you have to create the drill down level for the profile. Below attached is the pictorial representation of the drill down level for questions I created.
Similarly you can create drill down level according to your requirement. After defining the question hirerachy you have to specify the Valuation Specification and the scores to be awared for each value.
I have created valuation 8003 Valuation of PRD system. By selecting the created valuation profile double click on the "valuation" icon on the right side. There we need to set the details of valuation and the scores we intend to provide for each.
Now all the configuration related to conducting the Audit has been configured. Now we have to create Audit, Audit Plan, Question List.
Following are the main objects used for the Audit;
1) Audit Plan
The audit plan consists of all auditsplanned for a particular period of time. For example, all audits that are to be executed in the space of one year are defined in an annual audit plan. There is always only one current version of an audit plan, where all date shifts and the degree of completion for the individual audits can be found.
2) Audit
An audit, according to DIN EN ISO 9000, is a systematic, independent, and documented process used to obtain audit results and to evaluate these results objectively in order to determine to what extent the criteria of the audit have been fulfilled.
3) Question List
Question lists are multilingual collections of questions that are answered during the execution of the audit. The allowed valuation can be planned for each hierarchy level.
4) Corrective Actions
These are actions that are deemed necessary to eliminate the cause of errors that were determined during the audit and to prevent the recursion of these errors. The corrective actions to be executed must be appropriate to the effects that the particular error has on the product.
5) Preventive Actions
These are actions that are deemed necessary to eliminate the causes of possible errors before they occur. The preventive actions to be executed must be appropriate to the effects that the possible error could have on the product.
An audit, according to DIN EN ISO 9000, is a systematic, independent, and documented process used to obtain audit results and to evaluate these results objectively in order to determine to what extent the criteria of the audit have been fulfilled.
Execute transaction PLMD_AUDIT, first create the question list required for the audit with the components newly configured.
The main success factor for any audit depends on the questions used for the audit. Let me add few of the topics under which I have prepared the question list.
The main topics are;
System Overview
Security & Access Protection
Workbench Organizer
Transport System
Accessing and Logging DB Tables
Job Request Procedure
Documentations
System Logs
Batch Input Interface
Master Data Changes
Reconciling Posting Data Closing
Invoice Checking and Posting Run
Business Process Auditing
BASIS Audit
Once the audit question list is created / uploaded to SAP\, user must create a sample set of check list to be submitted to the client. The Check list should contain;
* All the documents that client has to Submit
* All the questions client has to answer.
Every company should run the audit at least twice a year to ensure that the system is working perfectly, no manipulations are done, to ensure 100% management control over the system ther by over the employees.
This article provides the user with the technique for creating quick reports on any function through SAP query and the procedure to transport these reports across clients. This is a useful technique for beginners with no background on queries.
Attached document briefs about some of the scenarios of Credit management processused by Automobile industry & how can we make use of Standard Credit management offered by SAP with some enhancements to meet their business demand.
Summary:- This document is meant to share the experience related to the Purchasing Document Release with the multiple currencies. Audience will be P2P consultants who would like to understand the configurations and setting required for the release strategy with multiple currencies.
Awadhesh Kumar, is a SAP-MM Consultant at Larsen & Toubro Infotech Ltd. and holds Bachelor degree in Electrical & Electronics Engineering. He has almost 7 years of experience, out of which 5 years in Procurement function and 2 years in the area of SAP consulting in Procure to pay process.
Table of Contents
1. Executive Summary.
2. Business Requirement Analysis.
2.1. Current Business Process.
2.2. Business Requirement.
3. Purpose of Multiple currencies.
3.1. Purpose of Multiple currencies – Materials Management.
4. Purchasing Doc. Release with Multiple Currencies.
4.1. MM Configurations.
4.1.1. Creation of new characteristic for AED (new) currency.
4.1.2. Assignment of characteristic to PO class.
4.1.3. Assigning object to class.
4.1.4. Maintain Release Strategy.
4.2. Process flow: Releasing Purchasing Document.
4.2.1. PO Release with AED Currency.
4.2.2. PO release with INR Currency. 12
1. Executive Summary
When we have to procure external goods or services from a vendor, we have to place order on them so that they can provide the same to us. When we create the external purchasing document, depending upon the procurement policy of the individual organization, it goes for a release (approval) process. Here, we can have different levels of releaser (or approver). There could be situation where the operations of the organization could be on different geographical areas having different local currency. Under such a situation, we may like to have our orders & release process in the respective local currencies for ease.
Purchase orders can be subject to a release (approval) procedure. Control over the purchase order generation is very important for every organization. Therefore, SAP has introduced a functionality called release strategy for PO's, where we can have different authorization levels/ steps to approve a purchase order. Based on the procurement policy of the organization, release procedures are defined. The purchase order can be released and then, sent to the vendor.
We have recommended the use of different release strategy with multiple currencies for their outside companies (abroad) that deals with their local (or different) currencies. This will ensure that all POs are properly released by the authorized person in the respective local currencies.
2. Business Requirement Analysis
2.1.Current Business Process
Purchasing Documents are being released in the single currency (Company code currency) in all Organizational units (i.e.; Company code, plants etc).
When the local currency & the currency in release strategy differs, we need to maintain the release values limits as and when there is change in the exchange rates between the two.
There is dependency of Purchasing Doc. Release on the change in the exchange rate since it is not fix.
2.2.Business Requirement
Business doesn’t wants to maintain the release value if the exchange rates changes.
They want to use different currencies in their release approval procedure. For this, we need to create different release strategies and maintain it for every currency in their own characteristics.
3. Purpose of Multiple Currencies
3.1.Purpose of Multiple Currencies – Materials Management
From a MM purchasing perspective:-
The currency at the header data of Purchasing Document is converted into local currency (Company code currency) and afterwards, the local currency is converted into the currency of the characteristics for Release.
Whenever there is change in the local currency & the currency in release strategy, we need to maintain the release values limits. There is dependency on the exchange rate value change.
4. Purchasing Doc. Release with Multiple Currencies
Business needs to configure Release for PO for different country with different currency and want to use different currencies in your release approval procedure you must create different release strategy and maintain for every currency own characteristics.
4.1. MM Configurations
Here, we are taking a scenario where our Company code currency is in INR. We have got one company in India (INR) and another Company at Dubai where AED is the local currency. Presently, the PO release is in INR only. So, every time there is change in the exchange rate between INR & AED, we need to change the release value for company at Dubai.
Therefore, we want to implement the addition of new currency i.e; AED in our PO Release Strategy.
MM configurations require the following procedures:-
Creation of new characteristic for AED (new) currency.
Assignment of characteristics to release class.
Assigning object to classes.
Maintain release strategies.
4.1.1. Creation of new characteristic for AED (new) currency for PO Release
Menu Path: IMG > Materials Management > Purchasing > Purchase Order > Release Procedure for Purchase Orders > Edit Characteristic
Tcode: - CT04
Create new characteristic for PO Release in AED currency.
In PO release strategy one of the most used characteristics is the net order value. In values tab, we are defining the values of characteristic in AED currency.
4.1.2. Assignment of Characteristic to PO Release Class
Menu Path: IMG > Materials Management > Purchasing > Purchase Order > Release Procedure for Purchase Orders > Edit Class
Tcode:- CL02
Add the newly created characteristic in the Char. Tab of PO Release class.
Select the value for the new characteristic for particular Release Strategy.
Since, the characteristic field can’t be blank so, we need to maintain some value for the characteristic for INR currency (1 AED = 16.20 INR). The currency can’t be negative so, to satisfy the INR characteristic, we just need to make it other currency (i.e.: INR) greater than or equal to ‘0’.
Select the respective values (here: Plant, Order Type, Total Net order value) for individual characteristics that will trigger the release strategy for the Dubai company in AED currency. The same values needs to be removed from the characteristics value that is configured for the Indian company. Eg:- here plant ‘Jabel Ali Mfg Plant’ will be added to new release strategy J1 for Dubai Company (in AED) and the same will be removed from the release strategy 20 for the Indian Company (in INR)
For release strategies, where we want it to happen in INR currency, we need to maintain the positive value for AED characteristic as well (1 INR = 0.062 AED).
4.1.4. Maintain Release Strategy
Menu Path: IMG > Materials Management > Purchasing > Purchase Order > Release Procedure for PO > Define Release Procedure for Purchase Orders
Select release strategies for Dubai Company (local currency is AED). Go to classification tab. In the Classification tab, we can check the values of all characteristics maintained for the particular release strategy & code. Via the Characteristics and their values, we specify the POs to which your release strategy is assigned by system when a PO is created or changed.
The value for INR is maintained to be equal or greater than ‘0’.
4.2. Process Flow: Releasing Purchasing Document
4.2.1. PO creation with AED currency
Here, we have considered below PO release scenarios:-
For Dubai Company:
Rel Strategy
Release Value
J1
0-50000 AED
J2
50001-750000 AED
For Indian Company:
Rel Strategy
Release Value
20
0 - 1600000 INR
40
16000000.01 - 24000000 INR
The new release strategy is getting triggered for the AED value and not going for the conversion from AED to INR and then, going for INR value in characteristic of INR.
Article: Partner integration for SAP based ERP systems - A SAP R/3 solution approach
Summary: This document explains the importance of partner integration in manufacturing industries, along with a solution approach to partner integration for SAP based ERP systems.
Author: Chirag Chandramohan Gowda M
Company: Infosys Limited
Created on: 11August, 2013
Author Bio:
Chirag Chandramohan Gowda M is currently working as SAP Senior Associate Consultant in Infosys Limited, and has expertise in SAP Sales and Distribution processes. He is a post graduate in Management and also a certified associate in Order Fulfillment with SAP ERP 6.0 EHP4. Chirag would like to thank his colleagues Naveen Advani and Siddaram C P for their support and guidance.
Introduction:
In a progressively fast paced, competitive interconnected business landscape efficiency stands tall and provides competitive edge over rival business firms. The most effective way to improve supply chain affiliations in order to stay ahead in this era of volatile market conditions and vary in purchasing power of consumers is to leverage Partner Integration.
Need for Partner Integration in business processes worldwide:
With demands on a supply chain higher than ever, flexibilty and agility are no longer competitive differentiators, they are business necessities. In order to streamline the supply chain process and to meet the changing needs of consumers and to have a competeitive edge over rival firms, most of the business entities are implementing partner integration solutions and prominent needs are noted below :
To elevate business growth
Product innovation
Cost reduction
Focus on increased quality
Partner integration solutions can be deployed in any industries where :
Partners
Vendors
Suppliers
Brokers, plays an important role in supply chain, manufacturing and sales processes respectively.
Important benefits of Partner Integration:
Emphasis on Product innovation in order to meet the increasing change in consumer needs
Proper demand management
Focus on capacity planning
Proper production flow planning
Effective sales order management
The above laid benefits will result in streamlining the supply chain process, improved ability in interacting with trading partners which helps in maintaining the competitiveness in the marketplace and meet the customer and partner expectations.
Partner integration for SAP based ERP systems: SAP Solution
Manufacturing industries are partnering with vendors, suppliers etc in order to ensure proper prodcution planning, effective inventory management and proper sales order management.
Due to instablity in market conditions and decrease in purchasing power of consumers, today some of the industries are enagaging in make to order process instead of make to stock process.
In Make to Order proces, production orders are caused by sales orders. This means that an ERP system must have a strong integration
between its sales order module and the production-planning module. Sales orders must be translated into production orders. System should be capable enough to monitor the progress of individual production orders so that customers are informed about a particular sales order.
Make to order process is extensively increasing in Manufacturing industries in order cut the raising inventory management costs and meet the customer demands on a planned production basis.
Rise in the need for Partner integration for SAP based ERP systems in manufacturing industries:
Since ,partners play an important role in manufacturing industries in day to day production, inventory and sales activities, it is very important to have the proper systems in place for placing purchase orders, sales orders, shipment documents, invoices etc. In order to ensure smooth and uninterrupted environment between business system and partner systems, there arises the need for Partner integration for SAP based ERP systems.
Typical Business Reasons:
Business firms who have deployed SAP based ERP systems will be receiving order files from various partners in manufacturing industries who will be using different non sap systems to place orders. These order files will be in different file format, and SAP system needs to convert these incoming order files into an inbound Idoc and create sales orders in sap systems
Operational framework for rollout or implementation:
Below diagram portrayes how to create sales orders in SAP ECC from incoming order files from legacy systems and in different file format:
We need to implement a simple one way Asynchronous link between a file sender and SAP R/3 system using SAP XI/PI. Custom XML document containing order file information is picked up from the FTP server by file adapter. The Message is mapped to IDoc –XML format & then routed to the IDoc adapter. The created Inbound IDoc is then posted into the backend R/3 System and sales order will be created by the R/3 system in SAP ECC provided that it has authorization to do so and based upon certain prerequisites in place in SAP ECC.
Solution points portrayed below :
Registered partners places order from non sap systems and in different file format.
SAP PI converts these order files into an Inbound Idoc and saves the order in SAP ECC. If an Inbound Idoc fails, a communication mechansim can be enhanced.
For instance; an email notification can be trigerred and sent to partners along with a partner number, error number and error message
If an Inbound Idoc is succesfull and an order is created in ECC, then based upon ATP check rule the acknowledgement is sent to the dealer. Outbound Idoc is created for the same and sent to delaer for accepting the order.
Cross reference data for fields :
A cockpit button can be created and enhanced in order to establish the connection between sap and non sap systems and below basic information can be maintained
Partner code and Partner name
Product/Material information
Email ids can be maintained in the table in order to send email notifications
In order to map the above data a database table or tvarvc variant cna be created and different fields can be created for each table under the cockpit button
Data mapping using SAP PI/XI:
We need to implement a simple one way Asynchronous link between a file sender and SAP R/3 system using SAP XI/PI. Custom XML document containing partner order file information is picked up from the FTP server by file adapter. The Message is mapped to IDoc –XML format & then routed to the IDoc adapter. The created Inbound IDoc is then posted into the backend R/3 System and sales order will be created by the R/3 system in SAP ECC provided that it has authorization to do so and based upon certain prerequisites in place in SAP ECC
.
Prerequisites to be in place in SAP ECC :
Partner numbers and name should be created in the SAP ECC
Materials to be ordered by the partners should be mapped to the respective partner codes
A program and t code can be created in order to map or upload the partner name and partner codes, material mapping, email ids mapping etc
Monitoring Mechanism :
Once the implementation is in place, we need to monitor the cockpit button and tables created. Tables should be updated periodically, preferably launching a background job. Key users should be trained to upload the tables and to make entries in the fields.
Customer sales representatives or the key users should be trained enough to correct the failed inbound Idocs. Access should be provided only to key users as the cockpit button table entries carry cross reference data.
Error Handling Procedure :
SLA should be defined to resolve the errors occured
A repository should be created in order to store the hand document providing the procedures to handle the errors and made accessible to the key business users.
User trainings should be provided periodically in order make them well acquainted with the process
Expectations should be set with the business to reslove the errors and to by pass certain errors.
A table can be created to store the error messages. In parallel we can create a cockpit button and can insert a table to store the by pass error numbers and these errors can be by passed by the business.
Assumptions:
ERP system should have all the necessary customization in place as that of normal sales order processing:
Partner integration for SAP based ERP systems can be deployed by any industries where partners act as an integral part of business processes.
Partner integration will help business firms for rationalization of supply chain model
Partner integration will help business firms in reduction of costs
Partner integration will help business firms to reach out the clients effectively and efficiently
Conclusions:
SAP ERP system must establish integration between the sales order module and the production planning module in order to transfer sales orders into production orders.
Monitoring of individual production orders must be possible in order to meet the consumer's demands and to keep them informed about the progress of their orders. Production orders must traced back to sales orders.
SAP ERP system must empower a highly flexible processing of orders in order to meet irregular sales demands.
SAP ERP system should strongly support the inventory manager and the purchasing department, to ensure an uninterrupted and continuous flow of components and to keep inventories as low as possible.
Measures should be taken in order to reduce the risk of inefficiency and wastage.
All the entities in the organization and the partners should be involved in the implementation in order to have a complete understanding about the functionality and business processes.
Hope we all are aware about trading partner functionality from SAP FICO point of view, which is mainly used for recording and reporting of inter-company transactions.
Trading partners are updated in GL, Customer and Vendor master and majorly used in customers and vendors. Some clients may use trading partner in an indirect way to update in GL transactions thereby not updating in GL master through exit or substitutions.
Trading partner can be inherited or derived from master or can be entered manually in transactions. Updation of trading partner is being controlled through relevant document type configuration in SAP.
Lets take an example of the document type configuration:-
Its being controlled through two main checkboxes in document type configuration (OBA7 transaction code) namely, "Inter-company postings" and "Enter Trading partner" checkboxes
a) If "Inter-company postings" checkbox is set and "Enter Trading partner" is not set
Functionality: Trading partner is derived from master data and no manual entry is possible in line item / transactions. Here trading partner must not be unique in a document.
b) If "Inter-company postings" checkbox is not set and "Enter Trading partner" is set
Functionality: Trading partner can be manually entered in line item / transaction by choosing Extras menu button -> Trading partner which will be applicable for all the line items in a document. Here trading partner is unique in the document.
c) If both "Inter-company postings" and "Enter Trading partner" checkboxes are set
Functionality: Trading partners are derived from master data and can also be entered manually in the line item / transaction in the "More Data" screen. Here trading partner must not be unique in a document.
d) If both "Inter-company postings" and "Enter Trading partner" checkboxes are not set
Functionality: Trading partner can be manually entered in a line item / transaction by choosing Extras menu button -> Trading partner which will be applicable for all the line items in a document. Here trading partner is unique in the document.
In short, both (b) and (d) represents the same functionality and it depends on each of the document type configuration with the business process involved.
Error message: We normally get error message "Consolidated Companies are different" Message F5080 in either posting or clearing transaction codes.
I faced this problem specifically in clearing transaction codes especially with AB document type where one of the document contains trading partner and other doesnt contains blank or different trading partner.
Solution: For example, in AB doc type, "Enter trading partner" is set but "Inter-company postings" checkbox is not set. The above error message can be solved by also ticking "Inter-company postings" so that even different trading partners or blank trading partner field will be cleared off without any error message.
The standard SAP R/3 System contains the following material types:
CONT (KANBAN containers)
This material type is recommended for creating KANBAN containers as a material. In the standard SAP R/3 System, only the Basic Data view is offered. Using this material type makes it easy to search for KANBAN containers.
DIEN (services)
Services can be performed internally or procured externally (outsourced). They cannot be stored or transported. Examples include construction work, janitorial/cleaning services, and legal services.
ERSA (spare parts)
Spare parts are used to replace defective parts. They may be kept in stock. A material master record of this material type can contain purchasing data, but not sales data.
FERT (finished products)
Finished products are produced in-house. Since they cannot be ordered by Purchasing, a material master record of this material type does not contain purchasing data.
FGTR (beverages)
FHMI (production resources/tools)
Production resources/tools are procured externally and used in production or plant maintenance. A material master record of this material type can contain purchasing data, but not sales data. It is managed on a quantity basis. Examples of production resources/tools include jigs and fixtures, and measuring and test equipment.
FOOD (foods excluding perishables)
FRIP (perishables)
Goods in an assortment that are perishable such as fruit, vegetables, dairy products, and meat.
HALB (semifinished products)
Semifinished products can be procured externally and manufactured in-house. They are then processed by the company. A material master record of this material type can contain both purchasing and work scheduling data.
HAWA (trading goods)
Trading goods are always procured externally and then sold. A material master record of this material type can contain purchasing data and sales data.
HERS (manufacturer parts)
Manufacturer parts are materials that can be supplied by different manufacturers and/or vendors who use different manufacturer part numbers to identify the materials.
HIBE (operating supplies)
Operating supplies are procured externally and required for the manufacture of other products. A material master record of this material type can contain purchasing data, but not sales data.
IBAU (maintenance assemblies)
Maintenance assemblies are not individual objects, but logical elements to separate technical objects into more clearly defined units in plant maintenance. For example, an automobile can be a technical object, and the engine, gearbox, chassis, and so on the maintenance assemblies. A material master record of this material type can contain basic data and classification data.
INTR (intra materials)
Intra materials exist only temporarily between two processing steps. A material master record of this material type contains neither purchasing nor sales data.
KMAT (configurable materials)
Configurable materials are materials that can have different variants. For example, an automobile can have different types of paintwork, trim, and engine. The Material is configurable indicator is already set for this material type in Customizing for the Material Master in the activity Define attributes of material types.
A material master record of this material type contains sales data, but not purchasing data.
LEER (industry empties) and LGUT (retail empties)
Empties are a type of returnable transport packaging generally subject to a deposit. They can consist of several components grouped together in a bill of material (BOM) that are assigned to a full product. For example, an empty crate and the empty bottles are assigned to the full product beer. Each of the components in the BOM has a separate material master record.
MODE (apparel (seasonal))
NLAG (nonstock materials)
Nonstock materials are not held in stock because they are consumed immediately.
NOF1 (nonfoods)
Nonfoods are items sold in grocery stores, other than food. Examples include paper products and magazines.
PIPE (pipeline materials)
Materials such as oil, power, or water that flow into the production process directly from a pipeline, line, or other type of conduit. Since pipeline materials are always available, they are not planned.
PROC (process materials)
Process materials are used in the manufacture of co-products. They are not physical entities, but represent production processes. They are useful if production is initiated by the availability of input materials and capacities, and not by material requirements planning.
PROD (product groups)
Product groups aggregate materials according to certain freely definable criteria. For example, the products may be similar to each other in some way, or they may be finished products that were produced on the same machine. A material master record of this material type can contain MRP and work scheduling data.
ROH (raw materials)
Raw materials are always procured externally and then processed. A material master record of this type contains purchasing data, but not sales data since they cannot be sold.
UNBW (nonvaluated materials)
Nonvaluated materials are managed on a quantity basis, but not by value.
VERP (packaging materials)
Packaging materials are used to transport goods and come with the goods free of charge. A material master record of this material type is managed on both a quantity basis and value basis.
VKHM (additionals)
Additionals are assigned to a material to be sold to ensure its effective presentation to customers. Examples include clothes hangers, care labels, and services such as pressing clothing for display or arranging it on hangers.
VOLL (full products)
Full products are the counterpart to empties. For example, with a crate of lemonade, the full product is the lemonade itself, while the empties are the individual bottles and the crate.
WERB (advertising media)
Means of presentation used in advertising that groups together advertising messages about a number of materials. Examples include printed mail-order catalogs, computer catalogs on CD-ROM, and promotional fliers.
WERT (value-only articles)
A value-only article represents a group of articles whose inventory is not managed on an article basis. All goods movements for this group of articles are posted to the value-only article.
WETT (competitive products)
Observing and evaluating the activities of your competitors is essential for optimum market analysis. You can enter basic data on
the products of your competitors in material master records of this material type. By specifying a competitor number, you can
Here is a list of common standard reports available in SAP across various modules. Hope it is helpful.
No
Broad level Report
Options available for report execution
Tcode in SAP
Remarks
Used by
Report area
1
Purchase order analysis
By delivery schedule By purchase order details By purchase order history
ME80FN
This report can be used for displaying the information of purchase orders created and the transactions that has taken place.
Purchase
Purchase
2
Purchase order display
By supplier By material By buyer By plant
ME2L ME2M
Facility available to restrict the viewing based on the status of PO viz. Partly received, Closed, No GR made Bill passing not done , etc.
Purchase
Purchase
3
Analysis of order values
By Material By buyer By supplier
ME81N
Totals analysis ABC analysis Analysis using comparison period Frequency analysis
Purchase & Finance
Purchase
4
Goods receipt forecast
By purchase order By vendor wise By material wise
ME2V
Number of anticipated deliveries
Purchase & Stores
Purchase
5
Stock lying with subcontractors
By Supplier By material
ME2O
Can be useful in deciding which component is to be given to supplier if the procurement is on subcontracting basis. It also helps in giving the visibility of stocks lying at subcontractor.
Purchase & Stores
Purchase
6
Monitor supplier confirmation
By Supplier By buyer
ME2A
This program is useful especially for imported purchase orders or such cases where the lead time of procurement is very high.
Purchase & planning
Purchase
7
Purchase analysis
By buyer By Material By commodity type By supplier
MCE1 MCE3 MCE5 MCE7 MCE8
This program will give you information on purchase value, invoice value during a selected period. However for these reports it is necessary to update the relevant LIS structure.
Purchase Executives
Purchase
8
Long term planning analysis
By supplier By material By commodity type
MCEA MCEB MCEC
This report can be used for Purchase budget requirement. However for this report to work, long term planning functionality should be put in use.
Purchase Executives
Purchase
9
Material document listing
By Material By movement wise By supplier
MB51
This report provides you with a list of the material documents which were posted for one or more materials.
Stores / Finance
Inventory
10
Account document listing
By material By date
MR51
The report Accounting documents for material produces a list containing all accounting documents available for a selected material.
Finance
Inventory
11
Stock Overview
By material By Plant By batch
MMBE
The stock overview provides you with an overview of the current stocks of a material at all places within plant
All
Inventory
12
Stock requirement list
By material By material planner
MD04
This report will help you to analyse material requirement plan considering stocks and future requirements.
Planning
Inventory
13
Plant Stock availability
By material By material type By buyer group
MB52 MB53 MCBA MCBE MCBR
This report provides an overview of the stock situation of a given material in selected plants. If there are multiple plants where the same material exists, this report can give the information on stocks at various places
Stores / Purchase
Inventory
14
Expiration date list
By material By Plant By batch
MB5M
This report provides an overview of the remaining shelf life of batches. This report is generally useful in Pharma.
Stores / Planning
Inventory
15
Stock on posting date
By material By Plant By batch
MB5B
The report Stock for posting date lists a company's own stocks in a particular time period.
Stores
Inventory
16
Stock in transit
By material By supplying plant By receiving plant
MB5T
This report issues a list with all stocks that are located in a plant's stock in transit. This information is useful when interplant / intercompnay material transfer is taking place.
Stores / Finance
Inventory
17
Stock with subcontractor
By plant By supplier By plant
MBLB
This report provides an overview of the stocks of material provided to vendor
Stores / Purchase / Accounts
Inventory
18
List of GR / IR balances
By material By supplier By buyer By Purchase order
MB5S
The report compares the GR quantities and values relating to a purchase order with the invoice quantities and values for the same PO. The report can thus be used to check goods and invoice receipts when purchasing documents show some discrepancy.
Purchase / Accounts
Inventory
19
MRP Controller analysis
By inventory controller
MCBG
This report will help you in tracking the inventory by responsible person.
Executive
Inventory
20
Material usage based ABC Analysis
By usage By requirement
MC40 MC41
This report will help you in identifying the fast moving, slow moving / non moving items. The report can be executed at the material level / plant level
Executive
Inventory
21
Range of coverage
By usage By requirement
MC42 MC43 MC.G MC.4
This report will help you in getting the information of coverage of the material for production purpose based on the past consumption pattern. The report can be executed material wise, commodity type wise, material planner wise etc.
Stores / Planning
Inventory
22
Inventory turnover
By material By commodity type By buyer By material planner
MC44 MC.3 MC.B MC.7 Mc.O
This report will help you in getting the information on the inventory turn over ratio.
Executive
Inventory
23
Slow moving items
By material By commodity type By buyer By material planner
MC46
This report will help you to identify slow moving items.
Executive
Inventory
24
Dead Stock items
By material By commodity type By buyer By material planner
MC50
This report will help you to identify dead inventory
Executive
Inventory
25
Usage value
By material By commodity type By buyer By material planner
MC45
This report identifies the share of the usage value to the total usage. You can also see the report graphically for a selected material in detail screen.
Executive
Inventory
26
Sales analysis
By Customer By material By sales person By sales office
MCTA MCTC MCTE MCTI MCTG
These reports can give you information regarding incoming sales order, credit memos, quantity, value etc.
These reports can be used for seeking the information on billing
All
Sales
28
Sale report with option like Area wise Statewise Executive wise
By sales area By customer By material
MC+2 MC+6 MCSI
The standard report MC+2 & MC+6 can meet the reporting requirement. However in case the standard report are not serving the reporting requirement user defined info structure can be created and transaction MCSI can be used for sales analysis.
All
Sales
29
Vendoe master list
By Supplier By Purchase group
MKVZ
This report can give you the list of suppliers
Purchase
Purchase
30
Status of indents
By indent By material By buyer
ME5A ME5K
This report can be used to seek the information of status of indent raised, purchase order number, goods receipt status etc.
Purchase Stores
Purchase
31
Quotations listing
By suppliers By mateial By commodity group
ME4L ME4M ME4C
This report is useful to view / extract information on quotations from supplier in case the quotations are invited for a particular indent
Purchase Executives
Purchase
32
Commodity price
By material By plant By Supplier
ME1L ME1M ME1W ME1P
This report is useful to view the purchase order price change history for various pricing conditions
Purchase Manager Finance
Purchase
33
Planned share of business
By material By supplier
MEQM
This report can be useful to know the % share of business planned with a supplier in case multiple sources exist for a commodity.
Purchase Executives
Purchase
34
Vendor rating
By commodity By commodity group By supplier
ME64 ME6D ME6C ME65
This report is useful to extract information of supplier performance on various parameters such as delivery, quality, cost etc.
Purchase Manager Quality Manager
Purchase
35
Commodity listing
By commodity By plant By commodity group
MM60
This report will give you the list of all materials created in the system with the parameter values
All
Logistics
36
Purchase value Purchase quantity Quantity reliability
MC$G MC$1 MC$M
This report can be used by purchase buyer / manager to track purchase performance
Purchase Executives
Logistics
37
Availability overview
CO09
This report gives you the information of material availble for production
Stores
Inventory
38
Physical inventory listing
MI24
This report may be used in case physical inventory system is followed in an organization
Stores Finance
Inventory
39
Bill of Materials
Display BOM Display BOM allocation to Plant Where used list BOM Comparison BOM explode - Multi level Bom explode - Level by level
CS03 CS09 CS15 CS14 CS12 CS11
This report can give you information related to Bill of materials, comparison of BOM between two materials etc.
All
Production
40
Work center information system
By machine wise By planner wise By plant wise
CR60 CR05
This report will give you information of the machines used for the purpose of manufacturing. The machines / work center could be labor work center also
Shop floor Costing
Production
41
Work cener analysis Operation analysis
By lead times By date By quantity
MCPB MCPY MCPK MCPQ
This report can be used to extract the information of operation qy, scrap qty, lead time, target lead time etc.
Shop floor Manager
Production
42
Material analysis
By lead times By date By quantity By product cost By material consumption By sales / production plan
MCPW MCPF MCPO MC89
This report is useful for giving the information of Target vs actual lead time, Planned order qty vs actual order qty, Planned cost vs actual cost, Planned consumption vs actual consumption
Executive
Production
43
Operation analysis Material analysis Work center analysis Production order analysis
By plant By material By order By machine
MCP1 MCP3 MCP5 MCPB MCPU MCPW
The order information system is a tool for shop floor control with a reporting function for production orders and planned orders. These reports are useful in discreet manufacturing set up.
Shop floor
Production
44
In repetitive manufacturing set up: - Production analysis Material consumption analysis Product cost analysis
By plant By material By component used
MCRP MCRK MCP6
These reports are extensively used for reporting purpose in the repetitive manufacturing environment
Shop floor
Production
45
Pull list
By plant By material By quantity By storage location
MF60
This report can be used in repetitive manufacturing environment to know the shortage of material for production
Shop floor Stores
Production
46
For process industry: - Shop floor information system related to material analysis, operation analysis, process order analysis, material usage analysis, product cost analysis
By plant By material By order By machine
MCP5 MCRU MCRV MCRW MCRX MCRY
These reports are useful only when PP-PI component is installed.
Shop floor
Production
47
Kanban analysis
By plant By supply area By material
This report will give the information of Kanban usage. Can be used only when Kanban component is used
Shop floor
Production
48
Kanban analysis
By demand source overview By supply source overview By plant overview
PK13 PK12 PK11 PK18
This report can be used only when Kanban feature of SAP is used.
Shop floor
Production
49
Material usage analysis
By plant By material By component used By order
MCRE
This report can be used for analysing the actual material usage against plan in manufacturing process.
All
Production
50
Product cost analysis
By plant By material By component used By order
MCRI
This report can be used for finding out planned cost vs. actual cost in the manufacturing process
All
Production
51
Product cost analysis - Summarised
By hierarchy By period
KKBC_HOE
This report can give you summrised information of all the production orders related to cost & quantity
Executive
Production
52
Cost Variance Target / Actual Variance analysis
By plant
S_ALR_8701348
This report can give you information on the cost variance analysis
Executive
Production
53
Missing parts checklist
By plant By material By component used By order
CO24
Missing Part list check
54
Order progress report
By plant By material By order
CO46
This report can give you information of the order which is in process.
Shop floor
Production
55
Production order information system
By order By Material By plant By production planner
COOIS
This report give information on production order
Shop floor
Production
56
Production order cost analysis
By order
KKBC_Ord
This report can give you information on target cost against actual cost for production order
Executive
Production
57
Actual comparison of financial results by period with previous period
By GL Account By Financial statement version
S_ALR_8701249 / 87012250 / 87012251 / 87012252
This report can give you financial statement for the selected period with comparison. The report can be viewed on half yearly / quarterly / periodic basis as well. For 10year comparison use transaction S_ALR_87012257
GL
Finance
58
Balance sheet / P&L statement
By financial statement By company code
S_ALR_870122284
This report will give you balance sheet / P&L
GL
Finance
59
Plan / actual comparison on periodic basis
S_ALR_87012253
This report will be useful incase you are using GL planning.
GL
Finance
60
Cash flow report
S_ALR_87012271
This report will give you cash flow.
GL
Finance
61
GL Balances
S_ALR_87012277 S_ALR_87012301
This report can be used to display GL balances
GL
Finance
62
Document Journal at summary level Document Journal at line item level
S_ALR_87012287 S_ALR_87012291
This report is useful to extract information of GL entries
GL
Finance
63
Statement of customer / vendor / GL Accounts
By company GL Account Customer account Supplier Account
S_ALR_87012332
This report will give you statement of customer wise / Vendor wise / GL wise accounts
GL
Finance
64
Customer payment history
S_ALR_87012177
This report will help you to analyse history of customers. It contains a forecast of payment volumes and arrears.
AR
Finance
65
Due date analysis for customer open items
S_ALR_87012168
AR
Finance
66
Account receivable information system
S_ALR_87012167
The report is used for displaying the evaluations available in the customer information system.
AR
Finance
67
Customer balances
S_ALR_87012172
This report will give you balance at the period start, debit total & credit total for the reporting period and closing balance at the end of reporting period.
AR
Finance
68
Customer evaluation with open item sorted list
By Customer By Company
S_ALR_87012176
This report can give you open AR sorted in days bucket as per your selection
AR
Finance
69
Vendor information system
By company By supplier
S_ALR_87012077
This report is used for displaying the vendor payment information based on due date, over due, currency etc.
AP
Finance
70
Vendor business
By company By supplier
S_ALR_87012093
This report is to be used when you want to see the information of purchases made from a supplier
AP
Finance
71
Due date analysis for supplier open items
By company By supplier
S_ALR_87012078
AP
Finance
72
Vendor payment history
By company By supplier
S_ALR_87012085
This report is used for determining the current payment status for vendors. The report carrry out an analysis of the vendor open items according to user defined time pattern.
AP
Finance
73
Check register
By bank By amount
S_P99_41000101
This report is used to extract the information of check issued
Bank
Finance
74
Asset History
By Asset By asset class By company code
S_ALR_87012075 AR02
It is the most important and most coprehensive report for the year-end clsoing or for an interim financial statement
Asset
Finance
75
Depreciation simulation / forecast
By Asset By asset class By company code
S_ALR_87012936
This is a report for the simulation of future depreciation
Asset
Finance
76
Posted depreciation
By Asset By company code
S_P99_41000192
The report list the period values from posting depreciation
Asset
Finance
77
Year end income tax depreciation report
By Asset By company code
J1IQ
Asset
Finance
78
Asset Inventory list
S_ALR_87011981
Asset
Finance
79
Cost center accounting - Plan / Actual comparison
By Cost Center By cost center group By version
S_ALR_87013611 S_ALR_87013615 S_ALR_87013620
This report lists actual and plan figures for cost center .
CCA
Controlling
80
Cost center accounting - Actual / Actual comparison
By Cost Center By cost center group
S_ALR_87013640
This report can be used to compare the actual costs on period basis
CCA
Controlling
81
Cost center plan
By cost center
KSBL
This report can be used to view cost center plan
CCA
Controlling
82
Analyse / compare product cost estmates
By plant By material number
S_P99_41000111 S_ALR_87013047
This report can give you the information on standard cost of material
PC
Controlling
83
Profitability report
By sales order By material By plant
KE30
This report can give you profitability at the sales order level. However it is necessary to implement PA module
PA
Controlling
84
Profit center report
S_ALR_87010777 S_ALR_87010779
PA
Controlling
85
Display machine list
By machine number By plant By status
IH08 IW29 IW33 IW39
This report will give you the list of machines installed in the plant
Shop floor
Maintenance
86
MTTR / MTBR for machine
By machine number
MCJB MCJC
This report can be used for extracting information on Meant time to repair.
Shop floor
Maintenance
87
Damage analysis
By machine By damage code
MCI5
This report can be used to extract the information on damage analysis
Shop floor
Maintenance
88
Breakdown analysis
By machine By machine group
MCI7
This report can be used to extract the information on breakdown such as number of break down, MTTR, MTBF
Shop floor
Maintenance
89
Maintenance cost analysis
By machine By machine group
MCI8
This report will be used to extract information on planned cost and actual cost for different type of breakdown
Shop floor
Maintenance
90
Customer notification analysis
MCIA
This report can be used for reporting customer notifications. It can be used if service management functionality is put in use.
Service
Maintenance
91
History of inspection characteristics
QGP1
You can use this report to display inspection results for a task list characteristics
Quality
Quality Magt
92
Control Chart
QGC1 QGC2 QGC3
You can get quality control charts are lot level / characteristics level
Quality
Quality Magt
93
Quality Notification analysis
QM11 QM15 QM50
Quality
Quality Magt
94
Defect analysis report
MCXX MCVX MCOX
This report can be used to view quality defects at material / vendor / customer level
Quality
Quality Magt
95
Calliberation inspection
IP24 IP19 QA33
These reports can be used for extracting information related to calliberation of equipments
Quality
Quality Magt
96
Project cost / revenue / expenditure
S_ALR_87013531 S_ALR_87013532
These reports gives you cost related information of projects. However it is necessary to implement Project systems module to extract these reports
Projects
Project System
97
Batch where used list
S_ALR_87012972
For extracting the information of batch traceability
Logistics
Logistics
98
Engineering change management
S_ALR_87012975 S_ALR_87012976
For tracking engineering changes.
Logistics
Logistics
99
All Standard SAP Reports -- Module wise
Module wise
SAP1
Displays all the Standard report available in SAP in each module
WAY to export the contents of structures and table when the standard option of exporting it using System> List> Save> local File is not available:
Please find below the steps to export the contents of structures and table where the standard option of exporting it using the path:
System> List> Save> local File is not available.
For example, in the case of the table - VBAK, the option to export using the path - System> List> Save> local File is not available, as shown in the screen shot below:
Step 3 – Now the standard path for exporting the contents of the table to local file - System> List> Save> local File is available, as shown in the screen shot below:
How to Download and Upload SAP Queries,Infosets and User Groups to another client or System[QAS,PRD]?
Downloading SAP Queries,Infosets and usergroups could be a bit daunting at first,but nevertheless it is quite a useful skill to have in your arsenal. SAP Queries can be divided into 2 parts called work areas:
(a)Standard Area(client-specific)
(b)Global Area(cross-client)
Any query created in the standard area is available to a particular client in the sap system. For instance in the Development system with client 100.
Any Query created in the Global Area is available across all clients of given system. For instance in the Development system,which has clients 100,200,300 etc.
Most of the SAP Standard Queries available under 'Information System' nodes belong to the Global Area,which usually used for SAP created Query Reports. Most custom SAP Query reports are created in the Standard Area.
The following steps would be required in order to download and upload SAP Queries:
01 - Identifying the list of reports to be downloaded(T-code = SQ01):
> To seek out all queries relevant to your user group first enter in the transaction 'SQ01' in the command field.
> use the menu path:
Environment > Query Areas > Standard Area(client-specific)
> Now click the other user group button[ Image may be NSFW. Clik here to view. ] on the extreme left of the application toolbar or use the key board shortcut of 'Shift + F7'.
Clicking it will bring in all user groups associated with the the selected area and select your specific user.
> Once the user group has been selected it brings in all the Queries created by your specific user group.
01 - Finding list of SAP Query Reports to be downloaded using SQ01
> Copy the names of all the reports that you want to download,by selecting one of the columns and pressing the 'Ctrl + Y' shortcut to select values of a specific column. ideally copy and paste them in an excel sheet.
> Also copy the names of the infosets for the reports to be downloaded,by following the same procedure as carried out by copying the names of the reports.
02 - Finding list of SAP Query infosets to be downloaded using SQ01
> First download the user groups,associated with the Queries and Infosets.
> Secondly download the Infosets
> Lastly,download the relevant queries.
> Do keep in mind that all infosets associated with the reports must also be downloaded.
> In SQ01,you can also find the name of the infoset associated with it as well. Which is shown in the form of an alv like list,once you have selected your user group,as mentioned above.
> Do remember the work area in which you have created your user group(Standard Area or Global Area),as all queries are associated with your usergroup,and if the correct work area is not selected,the list of queries associated with it won't be shown.
For finding the list of all SAP Queries associated with an Infoset:
> There is a query mechanism in SQ02,that allows you to fetch all the reports associated with a particular infoset. Right click the infoset name and choose the 'Queries for Infoset' option,this will show a list of SAP Query reports that are using this selected infoset.
03A-For finding SAP Queries associated with a given infoset in SQ02
This will bring the 'SAP Query Transport Tool',a utility for performing transports of mentioned objects.
> In the 'Transport Action Selection' area,select the 'Download' radio button. Next check the
'Overwriting allowed(only with import/upload/copy)' checkbox. Finally uncheck the 'Test run' checkbox in this area. If you want to transport variants created by the users as well,you can check one of the query variant option checkboxes.
> Now in the 'Transport Option Selection' area,select the radio buttons based on the following sequence as mentioned before:
(A)User Group
Select the 'Transport user groups' radio button,in the 'Import Option' field enter in 'REPLACE' and in the 'user groups' field,enter in one or more user groups to be downloaded.
Select the 'Transport Infosets' radio button,in the 'Import Option' field enter in 'REPLACE' and in the 'Infosets' field,enter in one or more Infosets to be downloaded.
Select the 'Transport queries' radio button,in the 'Import Option' field enter in 'REPLACE' and in the 'Usergroups' field,enter in one or more usergroups and in the 'Queries' field.
You will need add in the list of all User groups, Infosets and SAP Queries names already copied in the first step in an excel sheet. Just copy and paste each of them in their respective fields.
> Finally,once you have provided the selection criteria above,click the execute button,which will prompt you to download the provided SAP Queries and Infosets into an archive file with no extension. Do keep in mind that this archive will be used for uploading these on a target client.
[NOTE]:
> In case you don't see the topmost set of radio buttons for downloading or uploading SAP Query related objects via the menu path mentioned above in transaction SQ02,you can use the program version of the Download utility(RSAQR3TR).
03 - Procedure for Uploading Usergroups, SAP Query Reports and Infosets:
The method for uploading all query related objects to the target system or client,uses the same mechanism as that of downloading these objects. The only difference is that you will need to select the 'Upload' radio button in the 'Transport Action Selection' area in the SAP Query Transport tool. For accessing the SAP Query Transport tool through two different mechanisms,please the refer the section '02 - Procedure for Downloading Usergroups, SAP Query Reports and Infosets' in this document. For User groups you will need to provide the User group name,for Infosets you will need to provide infoset names and finally for Queries you will need to provide usergroup name as well as the SAP Query names in the fields provided. When you execute the Transport utility by pressing the 'Execute' button [or] pressing the F8 key,you will be prompted to provide the file name for the given object which you would like to upload to. Do remember that you need to log into the target system to complete it.
and finally if all the steps have been successfully followed,you will find them uploaded to any of the targeted systems. In my case,on QAS server. See the screenshot below.
I have also attached the sample sap user group,infoset and queries backup as were demonstrated throughout this document. These could found individually attached with the following names 'z_sap_queries.zip','zfj_infoset.zip' and 'zfj_usergroup.zip'. Just extract each of them to upload them via SQ02.
Some Caveats for SAP Query Uploads to Work:
> Lets say you have not added a user(An SAP User) to a user group from where you want to access you sap query related objects. You should add it in the SAP User group from the SQ03 transaction.
> Make sure that all SAP Queries have been re-generated and they don't have any errors. These could be achieved by first selecting the SAP Query in SQ01 and going to the menu path:
Query > More Functions > Generate Program
Secondly,you can also adjust your query to reflect newer changes in the SAP Info set associated with it. This can be achieved by going to the menu path:
Query > More Functions > Adjust
Do keep in mind that if there are any errors in you SAP Query objects,they wont be uploaded successfully to the targeted system.
[NOTE]:
> These caveats should be followed on the Source Client on which you have created all your SAP Query related objects.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the United States and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries.
Oracle and Java are registered trademarks of Oracle and its affiliates.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems Inc.
HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.
IOS is a registered trademark of Cisco Systems Inc.
RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registered trademarks of Research in Motion Limited.
Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks of Google Inc.
INTERMEC is a registered trademark of Intermec Technologies Corporation.
Wi-Fi is a registered trademark of Wi-Fi Alliance.
Bluetooth is a registered trademark of Bluetooth SIG Inc.
Motorola is a registered trademark of Motorola Trademark Holdings LLC.
Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company.
Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
The projects which are using the old 4.7 versions of the SAP or might have migrated upgraded versions but having a whole lot of profiles dependency existing ; still needs to go to a next step .
If your landscape is large and your users are having a wide range of already existing profiles ; in that case even if you upgrade your SAP version , but haven’t created the corresponding roles to the profiles ,, then the concept of new versions to move from profiles to roles is not fully achieved .
There are ways to achieve it ; depending upon the scenario or your landscape :
Analyzing of the profile based upon the user groups .
The key to make roles form the guide line of the profiles is to analyse the profile ; one way of doing this is classifying the users in terms of their user groups and seeing which are the profiles assigned to the maximum number of users and then those profiles can be analyzed further for their authorizations and correspondingly new roles can be created , single or composite .
There are certain other ways also to reduce the number of profiles in the roles ; i.e by creating single roles for each profile or by merging profiles to the existing roles .
How to do it technically :
Converting profiles into Roles
Tcode - SU25 – Select Option 6. Copy Data from Old profiles
Now the profile converted into Role with the objects from the profiles and some additional objects with yellow which needs to be deactivated, also in this option tcodes list will be created under Menu tab as shown in the next screen shot
In this option, the profile will be copied exactly same as profile data, you will not see any additional objects with yellow, there is no adjustment required in the role after conversion.
The disadvantage of this option is Menu, there is no Menu item created in this option as shown in the next screen.
Apart from above method ; you can also use insert option in the pfcg edit mode ; if you want to add the all the authorizations of a profile to an existing role or new role .
![04B_SAP_Standard_Program_downloading_sapquery_and_SAP_Infoset[Alternate].png](http://scn.sap.com/servlet/JiveServlet/downloadImage/284755/04B_SAP_Standard_Program_downloading_sapquery_and_SAP_Infoset%5BAlternate%5D.png)
