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

1. Increase in productivity creates direct Full Time Employee (FTE) benefits thereby enabling a redeployment of resources to other areas of this business
2. Increase in efficiency improves employee experience and reduces training and retraining burden from the company and management
3. Speed, clarity, and ease of navigation creates enhanced customer satisfaction and leads to more happy and reference-able clients
4. Automation and validation reduces the time required to navigate through systems and ensures a more comprehensive data set for management reporting
5. 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
6. Survival of enhancements through upgrades ensures that your investment is preserved and additional resources are used for additional enhancements
7. Ease and speed of deployment ensures that you can create a multitude of enhancements in a very short time with near immediate results
8. 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

ROI - Case 2

Steelscape used GuiXT for RF/Mobile Development.

CHALLENGES

• 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)

ROI - Case 3

A US Customer observes 2 processes before and after GuiXT.

1. Kindl of Audit to be Conducted (Technical or Functional)
2. Number of questions for the Audit
3. Structure of list of Questions (Question drill down level)
4. Valuation type of Questions
5. Question Priorites
6. What kind of Audit Controls to be implemented
7. Audit purpose
8. Audit Type
9. Kind of rating for the questions

Figure 12.0

• 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

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.

View Document

• Logon into domain controller
• Transaction STMS
• System Overview ( shift F6)
• Duble click on the system

• Display Change
• Transport tool
• Insert multiple line

• Add parameter NO_IMPORT_ALL = 1
• Update configuration

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

1. it assists in optimizing their business processes,
2. 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. 
3. 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.

• 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

• 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

Why the Solution is Necessary

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:

Assumptions

• 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)

Applies to:

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
• SaaS (Software as a Service) ERP won’t eliminate all of your risks, either
• Your project will fail without adequate organizational change management
• Executive buy-in and support is critical to ERP success
• There is no “one size fits all” ERP strategy
• If your operations and ERP system are misaligned, it’s probably not the software’s fault
• Expectations are high, but most ERP implementations may not always properly define the “finish line.”
• Most organizations strive for “no customization,” initially,  but fail to do so eventually
• You don’t have to implement ERP all at once
• If you don’t measure it, you won’t achieve it

* The contents of this paper are my personal views and opinions, gained in the course of my experience.

1. Kindl of Audit to be Conducted (Technical or Functional)
2. Number of questions for the Audit
3. Structure of list of Questions (Question drill down level)
4. Valuation type of Questions
5. Question Priorites
6. What kind of Audit Controls to be implemented
7. Audit purpose
8. Audit Type
9. Kind of rating for the questions

Figure 12.0

• 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

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.

View Document

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.

The content is in the attachment

Regards

Satisha.K

Applies to: SAP ECC 6.0. For more information, visit theEnterprise Resource Planning homepage.

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.

Author         :   Awadhesh Kumar         

Company     :  Larsen & Toubro Infotech Ltd.

Created on   :  07^th Sept’ 2013

Author Bio    

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.

Now in Additional Data tab, assign table CEKKO & field GNETW to the new characteristic.

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.

4.1.3.      Assigning Object to Classes

Tcode:- CL20N

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:

For Indian Company:

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.

Since, the total value of PO is in between 0-50000 AED so, the release strategy with ‘J1’ is getting triggered.

4.2.2. PO creation with INR currency

Similarly, we can do the scenario for with the INR currency.

Article:  Partner integration for SAP based ERP systems - A SAP R/3 solution approach

 

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:

                                                                            Chart created by the author of the document

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:
• Document type, ATP, item category determination, schedule line, shipping point determination, storage location determination, plant
  determination, account determination, customer pricing procedure, pricing procedure determination, incompletion log check etc.

Recommendations :

• 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.

Deferred Tax Transfer Functionality in SAP

Investment Measure Concept in SAP FICO

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

assign the product to a particular competitor.

Hi All,

Here is a list of common standard reports available in SAP across various modules. Hope it is helpful.

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:

Steps for exporting the content of the table VBAK to local file:

Step 1 - Enter the name of the table in SE16

Step 2 – Click on the icon – Table View> List>Print Preview:

The content of the table is displayed in the ALV grid view as shown 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:

Step 4 – Select the option Spreadsheet and provide the desired name and the path where the data is to be saved:

The content of the file is exported and saved in the specified path:

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[   ] 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

[NOTE]:

> 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

03B-SAP Queries associated with a given infoset in SQ02

02 - Procedure for Downloading Usergroups, SAP Query Reports and Infosets:

There are two ways in which you can download Usergroups,SAP Queries and Infosets:

(A)Using the transaction SQ02 and using the menu path:

     Environment > Transports

04A - Menu Path for downloading Sapquery and SAP Infoset

                                                  [OR]

you can open a program named 'RSAQR3TR' in transaction 'SE38'(ABAP Editor),by copying this name and pressing the 'F8' key to execute this program.

04B - SAP Standard Program downloading Sapquery and SAP Infoset[Alternate]

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.

04C(1A) - Downloading User Groups

04C(1B) - Usergroup Download Log

(B)Infosets

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.

04C(2A) - Downloading an Infoset

04C(2B) - Infoset Download Log

(C)SAP Queries

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.

04C(3A) - Downloading SAP Query

04C(3B) - SAP Query Download Log

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.

(A)User Group

05(1A) - Uploading User Groups

05(1B) - Usergroup Upload Log

(B)Infoset

05(2A) - Uploading an Infoset

05(2B) - Infoset Upload Log

(C)SAP Query

05(3A) - Uploading SAP Query

05(3B) - SAP Query Upload Log

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.

06 - SAP Query Successfully Transported to QAS

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.

Legal

Fahad Javed's Copyrights

All Screen Shots taken,Fahad Javed's Logo are copyrights © 2010-2013 Fahad Javed. All Rights Reserved.

All the material written is a labour of hardwork carried out by the author. Kindly don't copy this material for commercial purposes. If a link is provided do provide the accredition to the author as follows:'© 2010-2013 Fahad Javed. All rights reserved.'.

All the terms used are copyrights of SAP AG  © 2013 SAP AG. All rights reserved. See the section 'SAP - Copyrights and Trademarks' for further details.

SAP - Copyrights and Trademarks

© 2013 SAP AG. All rights reserved.

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.

Profile to Role Conversions

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 :

1. 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 .  

2. 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

Say ok to below screen

Select the profiles(one or more) which you want to convert into Role

Option:1

Converting Profile to Role using option Optimized

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

Tcodes list created under Menu tab

Option: 2

Converting Profile into Role using option Identical to Profile

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.

No Menu item created for the second option

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 .