Strategy 50 issue

Dear Gurus,
I have an issue for the following scenario, I have:
an Indipendent requirment (MD61 Req.Type VSE) qty 26
the I plan the material with strategy group main 50 secondary 10
I ran the MRP via MD42 for the FG
A planned order not convertable is created
Then I should sell it so I create a sales order with qty 26
What I read from the forum is that the sales order should use the qty of the planned order and so I will be happy.
It does not happen when I create the sales order I am not able to see that the requirement of the planned order is assign to the SO.
I think there is something over the SO that does not work
Can any body help me achieving the solution?
G

Dear,
In the sales order display mode, go the Procurement tab and see whether Requirement type is "KEV", it should be "KEV" then only it would consume the Non-Convertable Planned orders and convertable Planned orders would be created.
Incase the requirement type is not KEV, please check with your SD- Consultant on this.
Regards,
Prasobh

Similar Messages

Purchase requisition release strategy issue

I have created release strategy in development, it was working fine with work flow. When I try to import the TR's I found that the document types in development are not in quality so I changed the document type. then I tried to create a PR and when I clicked on messages its not triggering the release strategy don't know why. In total there are 2 characteristic plant and document type.I even tried to delete the plant characteristic and tried again creating PR but still no use. let me put some screen shots comparing the development and quality. Please do help.

Thanks for the quick reply, I just checked that the over all indicator for the development and quality, I found that in development its not activated while its activated in quality will that be of any issue.
In development
In Quality

PO Release Strategy Issue

HI,
We have created a PO release strategy workflow.All scenarios are working fine except 1 scenario.
That is,when a PO is created and rejected by a user in user decision step.The workflow will end.If the PO is changed(amount) again,the release strategy is triggered for the same user.But the workflow is not triggering.
If the release strategy is for a different user,its triggering the workflow.
I have used a fork inside which 1 parallel branch contains a wait for significantly changed event & another branch contains the user decision step,po release step & rejection reason scenario.
Can anyone tell the solution for why the workflow is not triggering for only this scenario?
Thanks,
Aparna.

Feddie wrote:>
> Kjetil, I am not clear still, could you explain me a bit clear. I have not seen any tool tip in my release tab.
Don't you see any buttons in the subscreen? The tooltip is not for the tab (title) it is for the button. I am quite sure there is a button there for cancelling the rejection, but without access to a system where this has been set up I can't check it. I just had the same issue before Christmas, where the users said the solution didn't work for the same reason mentioned here - no workflow was sent after changes where made. In fact the solution did work flawlessly as soon as they cancelled the rejection.
See also [documentation at help.sap.com|http://help.sap.com/erp2005_ehp_02/helpdata/en/4c/16443c4a089537e10000000a114084/frameset.htm|ERP release ECC 6.0] for the workflow for rejected purchase orders.

COPA Valuation Strategy Issue

Hi,
When posting the Billing document,I am getting Direct Material cost 2 times in COPA line item document in KE24.
I guess this is beccause problem in Valuation strategy configuration for COPA in the system.Kindly advice me why i am getting Material Costs 2 times,one is From KWMAEK value field,it is getting updated from Stadard Cost estimate.
if it is having problem with Valuation Strategy in COPA,kindly advice me what are the necessary settings that i need to make.It would be a great help for me.
Why it is taking material cost 2 times,kindly advice me as it is very very critical issue for me.
I will assgin points
Thanks
Sunitha

Hi Thanks for your reply.
System is posting differant amounts one with value field VVMAT material Cost and one with KWMAEK direct material cost.
Can you suggest me
Thanks
Sunitha

Scheduling Agreement Release Strategy Issue

Hi,
We have a typical problem in Scheduling Agreement Release Strategy.
Once the SA is released for the first time it should restart the release strategy again if there is a change in Quantity or Value or Purchasing group. The release strategy is getting restart for some of the release strategies and not for others. I compared the characteristics, class for both the release strategies and I am not seeing any difference.
Can anyone please help me in this regard.
Thanks in advance.
Regards
Ram

release strategy can be rerigger in case where qty or price change and the changes is over the percentage you defined for Release indicator
goto release indicator config and in SPRO for release strategy and check the Value change %
maintian 0.1 here
so any change above 0.1 will retrigger
and maintian value 4 in chgable field.

JPA mixed inheritance strategy issue

Table : A, b
Class : A, B, C
@Entity
@Table(name="A")
@Inheritance(strategy=InheritanceType.JOINED)
@DiscriminatorColumn(name="type")
abstract Class A
@Entity
@Table(name="B")
@DiscriminatorValue("B")
@PrimaryKeyJoinColumn()
Class B extends A
@Entity
@DiscriminatorValue("C")
Class C extends A
From A - B its *@Inheritance(strategy=InheritanceType.JOINED)* and from A - C its *@Inheritance(strategy=InheritanceType.SINGLE_TABLE)* by default. When I try to run some test Toplink doesn't identifies class C as mixed strategy but expects C to have its own table as the super class A is specified with Joined strategy. Not sure how else would mixed strategy work !
Any help would be greatly appreciated.
Tx
K

Hello,
My understanding is that all classes should use the inheritance strategy defined in its parent class - there is no way to have two strategies used on a single parent class.
If you are aiming to get 3 classes (A, B and C) to use two tables (A, B) you might instead try specifying the root (A) to use SINGLE_TABLE. B will then automatically have an entry in Table A, and Class B can then be defined to use the B table as well by adding the @SecondaryTable(name="B") annotation to it, specifying the joincolumn if the primary key field names are different. A and C will then only use Table A, B will use Table A for inherited attributes and join to Table B - be sure to explicietly define the table to be used in any mappings on B that you wish to use Table B, otherwise I believe Table A will be assumed as it is the primary table.
Best Regards,
Chris

Derivation strategy issue

Dear Sapgurus
i create one derivation rule t codes is fmderiver in 100 client, for testing we copy transport request to 120, if i check rule in 100 tcode is fmderive system its showing which i have created, in 120 if i check fmderive system its not showing which i have created and transport request is successfully completed.
Regards
Raju

Hi,
When you create a transport in FMDERIVE, the system shows a pop-up window asking if you want to transfer also the values of the rules. If you choose 'yes', the values will be transported. Go to FMDERIVE, enter to your strategy, then Menu - Extras - Transport and generate a new transport, this time with values.
Regards,
Eli

PR Overall release issue

PR release strategy issue comes when Line items in PR added by two different persons, PR Release strategy(overall release) not getting triggered.
Release strategy is working fine if i create PR with only one user id.
Both id's maintained in classification.
Is this sap standard behavior??
Created PR 4201001933 line item 10. using User ID - 20061704
Triggered correct release strategy TD QH.
Added line item 20 using user Id - 345045 --- (release startegy gone)
classification Maintained for TD QH

We have a similar equirement since we have cost center as one of the characteristics in PR overall release strategy.
In our case we agreed with Business that the CC in the first PR line item will decide the release strategy. (Or the first CC of thefirst line item in case of multiple account assignment.) We wrote a small piece of code to achieve this, to enter that CC in ceban-kostl.
If your business requirement permits, you may follow this strategy, where user id of the first line item will derive release strategy.
Regards.
Satish Patankar.

Purchase order workflow issue

Hi All,
A PO is created and rejected by a user in user decision step.The workflow will end.If the PO is changed(amount) again,the release strategy is triggered for the same user.But the workflow is not triggering.If the release strategy is for a different user,its triggering the workflow.I have used a fork inside which 1 parallel branch contains a wait for significantly changed event & another branch contains the user decision step,po release step & rejection reason scenario.
Please refer the thread below.
PO Release Strategy Issue
Replies will be greatly appreciated.
Edited by: Feddie on Jan 3, 2008 11:43 AM

Hi,
This is not workflow issue(work flow is different term)
It seem problem of BADI (program written for creation of purchase order based on sales order)
Take help of ABPer so he/she can solve this issue
Kapil

Release Strategy Question

Hi,
Can anyone explain me with example, why is it that we can have only one class and not more, when configuring groups in the release strategy.
Why is it mandatory to have only one class for overall and one class for line item release, can someone explain with examples.
The system allows creation of multiple groups, but all have to use the same Class when it comes to overall release/ Line item release.
I am not able to understand the reason behind this restriction as of now, can someone share some insights.
Thanks
Shailesh

Hi,
Better & always keep one release class ....ie.......one release class for PR, one release class for PO, one release class for Contract & one release class for SES.Under each separate class keep your requires characteristics.Then do necessary confuguration for release statergy.
For more check the links:
/people/arminda.jack/blog/2009/03/12/mm--check-list-to-detect-and-solve-release-strategy-issues
Re: Class and release group and code in release strategy??
Regards,
Biju K

Authorization object to control plant code in ME54N

Dear All,
Problem: Restrict user "PURAUTALL" userid to release PR's in ME54N for plants "5350" & "5360" only but should be allowed to create/change/display PR's for all other plants including 5350 & 5360.
Analysis: Object M_BANF_FRG is used to control releasing PR's using release codes but how to link up plant codes
Setup:
PURAUTALL userid has access to create/change/display PR's for all plants - M_BANF_WRK is *
PURAUTALL userid has role same as user id but does not contain object M_BANF_FRG in PFCG
Kindly provide suitable solution &/or process to create object M_BANF_FRG in PFCG.
Thx & Reg
Bhushan

Hi Julius,
Thx for replying, actually we havent tried any options because it seems to be a release strategy issue. As of now, thinking to create the object M_BANF_FRG in PFCG and then linking release codes.
But before that business needs to decide to create new release strategies / codes based on plant as characteristics.
If this correct, if any other way out pls help.
Thx
Bhushan

Planned order & Purchase Requisition

I want SAP to create Pur Req not planned orders. Is that the release strategy issue?
1) Planned order
2) Purchase Requisition
3) Purchase order
Can I setup SAP to by pass planned order and go straight to pur recs for purchase parts ?

Hi Analucia,
Yes. Planned orders are optional. Whether MRP run creates planned orders for purchased items, or directly purchase requisition is controlled by the parameters of the planning run.
For example, if you run it online, go to MD01, and you'll see that you have a parameter called "create purchase req.", via which this is controlled.
If it not behaving the way you want using when setting this parameter, check also the same parameter in the definition of the MRP group.
Regards,
Mario

Dto changed but database not updated

hi, i am trying to create a simple program that has an entity bean which maps to a table in database.
i created dto for the bean and i was able to find(), create(), with the database insertion of the new creation correctly. but i when i updated an attribute of the dto using its setXXX(), the database was not updated after the action.
can anyone help me with this problem? thanks!

i did some googling n found a thread that says it is the concurreny strategy issue. i tried setting it as other values except readonly but it still doesnt works. anyone can enlighten me?

Business process-BUSES

Sirs, My project is the related to the Manufacturing, industrie BUSES , Under this one what we can say as the BUSINESS PROCESS,(how to the intial stage comes to work in, and how to the finished completed structure) please what have ur valuble suggestion..... help

Dear Ameer,
ASAP Methodology
Forward Media has adopted ASAP (Accelerated SAP) as its methodology of choice for SAP implementations, upgrades and module additions.
Our in-depth knowledge of ASAP allows us to customise and streamline ASAP to suit widely varying project requirements. For example - while ASAP was originally conceived as an implementation methodology, Forward Media has found ways to apply its strengths to the smaller tasks of SAP upgrades and new module additions. Innovations such as these have become part of standard and offically endorsed ASAP methodology.
Our involvement with the ASAP methodology began in 1996, when Forward Media Director Nadia Ward worked extensively with SAP America on the creation of the original ASAP methodology. Nadia led the technical component of the first commercial trial of ASAP in an implementation for CFS in New York - in the process contributing several operational templates to the ASAP toolkit.
ASAP Phases
The ASAP methodology structures the project lifecycle into five phases which run sequentially from project start to project completion. These standard ASAP phases are:
1. Project Preparation
2. Business Blueprint
3. Realisation
4. Final Preparation
5. Go-Live and Support
Concurrently with these ASAP phases, we also run a series of continuous processes which cover the types of activities which, by their nature, transcend individual phase boundaries (eg: Quality Assurance) or which require activity throughout the project lifecycle (eg: Knowledge Transfer).
These continuous processes identified as necessary for most SAP projects:
1. Quality Assurance
2. Data Migration
3. Basis
4. Knowledge Transfer
5. Cutover Planning
6. Project Accelerators
Together, the ASAP phases and our continuous processes define the broad outline of our approach for SAP projects.
Project Management Toolkit
Forward Media has a series of Project Management tools in addition to those sourced from ASAP that we make available to our clients. These include templates such as our:
 Project Plan Template (for SAP Implementations and Upgrades)
 Data Conversion Strategy
 Cutover Plan
 ABAP specifications
 Test Scripts
 Client Landscape
 Change Management Strategy
 Month End Schedule
 Issues Log
 Phase 1: Project Preparation
 Phase 2: Business Blueprint
 Phase 3: Realization
 Phase 4: Final Preparation
 Phase 5: Go Live & Support
Phase 1: Project Preparation
In this phase of the ASAP Roadmap, decision-makers define clear project objectives and an efficient decision-making process. Here Project Organization and roles are defined and implementation scope is finalized.
System landscape and Technical Requirement
 Infrastructure need (Hardware/interfaces): Available- QuickSizing Service: to be accessed via SAPNet
 System Landscape
 High level strategies for client
 Archiving strategy
Issues Database:
Issues must be resolved before phase completion ot before beginning of the next phase. The issues can be
 Unanticipated tasks
 Normal tasks that can not be completed
 External factors that need to be dealt with.
Issues database allows the project team to enter, track and report on project issues.
Phase 2: Business Blueprint
In this phase scope of the R/3 implementation is defined & Business Blueprint is created. Business Blueprint is a detailed documentation of companys requirements.
Various tools are used in this phase.
 AcceleratedSAP Implementation Assistant
 Question & Answer Database (Q&Adb)
 Business Process Master List (BPML)
 R/3 Structure Modeler
 Business Navigator and external modeling tools
Project Management:
Activities nagement:in this work package are:
 Conducting Status meeting for project team
 Conducting steering committee meetings
 General project management
 Addressing organizational issues relating to organizational change management.
Other activities include:
 Project Team Training
 Developing the System Environment
 Defining Organizational Structure
 Defining the Business processes
R/3 reference model can be used for
 Comparing the standard functionality with your companies own organizational requirements
 Creating documentation for the conceptual design
 Optimizing business processes
 Training the project team and users
 Writing user documentation
Question and Answer Database can be used to determine
 The Baseline Scope
 Cycle Plan
 Integration test Plan
Phase 3: Realization
The purpose of Phase 3 is to configure the R/3 system. The configuration is carries out in two steps; baseline configuration & Final configuration.
Business Process Master List (BPML) is created in phase 2 as a report from Q&A database. It is used to identify, plan, schedule and monitor the configuration and testing of all R/3 scenarios and processes within the scope of an implementation. BPML is a representation of the R/3 business and transactions that are contained within the scope of the project. BPML is feeds all business information to all subsequent worksheets.
Implementation Guide (IMG):
It is the main tool for setting the parameters to configure or Customize R/3 during the realization phase. IMG reflect the chronological order in which the customizing activities are carried out.
The following aspects of configuration are also to be considered:
 Defining authorizations in the R/3 system
 Defining workflows
 Creating user documentation
System Manager Procedures
 Developing system test plans
 Defining service level commitment
 Establishing system administration functions
 Setting up Quality Assurance environment
 Defining the design of the productive system
 Defining system management procedures for the productive system
 Setting up the productive environment
At the end of this phase, Project Manager must check the status of deliverables for completeness and accuracy. This internal quality check should be carried out in addition to an external, independent third party Quality Audit.
Preparation for end-user training needs to be gone through and approved at and of this phase.
Phase 4: Final Preparation
The purpose of this phase is to complete the final preparation of the R/3 system for going live. This includes testing, user training, system management and cutover activities, to finalize your readiness to go live.
In this phase the R/3 system is handed over to individual departments for productive operation. This includes preparation of end-user documentation and training the end-users. The technical environment is installed on production system & is tested. Project managers prepare plans for going live, transfer of legacy data and support at early stages.
End-user training is a critical activity for success of the project. InfoDB may be used to plan for the User Training activities. Computer Center Management System (CCMS) must be set at this time. Simulation of productive operation system & testing the same is of great important.
The test plan contains the following activities
 Testing conversion procedures and programs.
 Testing interface programs
 Conducting volume & stress testing
 Conducting final user acceptance testing
 Developing a final go-live strategy.
The Computer Aided Test Tool (CATT) can be used to automate test sequences for key business processes.
Phase 4 also provides for the testing of the disaster recovery plan for the productive environment. Disaster downtimes are verified and details on de-escalation.
Phase 5: Go Live & Support
This phase is concerned with supporting and optimizing the operative R/3 system.
Following activities are carried out
 Production support facilities are defined.
 Validation of business processes and their configuration.
 Follow-up training for users
 Signoffs etc.
During phase 5, the first EarlyWatch session should be held, where experts from SAP analyze the systems technical infrastructure. The aim is to ensure the system functions as smooth as possible.
Version upgrades should be planned whenever found necessary. AcceleratedSAP contains a continuous roadmap, with standard activities necessary after implementation. The tasks in that structure provide solutions for all known types of continuous change: Business changes, technology changes or changes in user community.
with regards,
B.Ravindranath

SAP K Gradings K1 - K8

Does anybody know where I could get the full roles and responsibility descriptions for the following SAP consulting gradings :
As far as I am aware the following categories have been defined for SAP consultants:
K1 = Junior Consultant
K2 = Consultant I
K3 = Consultant II
K4 = Consultant III
K5 = Senior Consultant/Management Consultant
K6 = Lead Consultant/Project Implementation Manager/Implementation Specialist
K7 = Development / Consulting Manager / Platinum or Senior Consultant / Global Support Manager / Senior Project Implementation Manager / Industry Specialist
K8 = Senior Development / Consulting Director / Consulting Vice President
We would like to incorporate the relelvant SAP specific aspects into our own company Role profiles (for example statemenst such as May supervise colleagues at Level 1 to Level 3 and allocate resources to make sure work is undertaken effectively and efficiently etc etc.
Thanks, Koen

Hello koen
These are the descriptions of SAP consulting gradings :
TRAINEE CONSULTANT (K1)
Position Concept
The Trainee Consultant is an entry-level SAP consulting position.
Individuals with requisite academic / professional qualification are
candidates for this position. They would typically not have any business
or systems implementation experience.
They need to display potential in basic communication and interpersonal
skills, leadership capabilities, conceptual thinking and innovation.
They have to be results oriented and enthusiastic and have the ability
to work in a team.
Trainee consultants will be trained in a specific
functional/technological area in mySAP. They will attend the SAP
Academy, ASAP training and applicable Consulting skills training.
Trainee consultants have to be SAP certified and ASAP certified prior to
embarking on any SAP project. They are expected to participate as team
members and will be mentored on the project by either a Consultant or
Senior Consultant. They would be given specific tasks on the project,
which will be carried out under the guidance of their mentor.
They will undergo regular Performance assessment processes to monitor
progress.
Responsibilities:
* Will work within a team under direct supervision of a mentor
assigned to them
* Responsible for specific tasks as assigned by their mentors
* Documentation and administrative tasks
* Use ASAP methodology and tools on the project
* Continually develop mySAP core skills and business knowledge
based on accumulated experience.
* Apply knowledge gained from each project experience to execute
future tasks for projects
ASSOCIATE CONSULTANT (K2)
Position Concept
The Associate Consultant has requisite academic / professional
qualifications and with at least 2 years of industry or functional or IT
skills (in specific application areas).
Associate Consultants are either skilled in mySAP specific functional
knowledge or will be trained in a specific functional/technological area
in mySAP. They have to be SAP certified and ASAP certified prior to
embarking on any SAP project. They are expected to participate as team
members and will be mentored on the project by either a Senior or a
Principal Consultant. Typically they would participate in discussions on
process design, configure certain portions of mySAP as per directions
given by the team leader, and provide support in documentation, system
testing and authorizations. They would also perform any administrative
tasks that are involved in a project.
Responsibilities:
* Primary responsibility is preparation and contribution to the
process design workshops, take directions and configure the SAP system,
demonstrate and gain acceptance from the customer
* Assists in the technical preparation of Business Process
Procedures, Test Scenarios, End-user documentation, and User manuals
* Uses ASAP methodology and tools on the project
* Interacts with SAP organisation as necessary during the project
& performs any administrative tasks that are involved in a project.
* Operates as a team member. Continually reports progress. Assumes
additional responsibilities as required
* Continually develops mySAP core skills and business knowledge
based on accumulated experience. Applies knowledge gained from each
project experience to execute future tasks for projects
* Sets priorities appropriately, ensures that work outputs are
timely and of the highest quality
* Receives management direction as appropriate.
CONSULTANT (K3)
Position Concept:
The Consultant performs the bulk of the engagement as defined by the
client contract, and is certified in at least one area of mySAP as well
as in the ASAP methodology. Consultants gather facts, analyse the
client's business processes and draws conclusions. They prepare the
design of the solution and demonstrate SAP functionality to support the
findings and conclusions. Consultants are expected to establish
relationships with client personnel and to deliver timely, high quality
consulting to the client.
Individuals with requisite academic professional qualification and with
at least 5 years of industry or functional or IT skills (in specific
application area) are candidates for this position.
Responsibilities:
* Contributes to consulting projects by analysing client's
business processes and design of mySAP solution. Primary responsibility
is preparation and contribution to the process design workshops, take
directions and configure the mySAP system, demonstrate and gain
acceptance from the customer. Moves logically and creatively from facts
to conclusions. Performs configuration and assists clients in testing
cycles.
* Assists in the technical preparation of Business Process
Procedures, Test Scenarios, End-user documentation, and User manuals
* Assists the client in mySAP knowledge transfer. Establishes
credibility with the client. Interfaces with clients in a professional
manner with emphasis on building client relationships.
* Is alert to opportunities for additional business with the
client. Shares client needs and trends in the marketplace and alerts
Consulting Platinum to potential long-term opportunities
* Continually develops mySAP core skills and business knowledge
based on accumulated experience. Uses ASAP methodology and tools in the
project and acquires additional skills in cross-functional areas and
enabling technologies
* Interact with SAP organisation as necessary during the project &
performs any administrative tasks that are involved
* Leads the execution of assigned project tasks in areas of
demonstrated competence. This includes facilitating meetings/task
groups, tracking and influencing task group progress, tracking project
deliverables, etc.
* Operates as a team member. Continually reports on progress to
the Project Manager and participates as an active member of the project
team. Assumes additional responsibilities as required
* Sets priorities appropriately. Ensures that work outputs are
timely and of the highest quality
* Occupies a non-management position. However operates
autonomously and receives management direction as appropriate.
SENIOR CONSULTANT (K4)/ PROJECT TEAM LEADER
Position Concept
The Senior Consultant plays a key role on the project team; either by
running small projects, Integrating portions of a large project, or
being a team member on a project, driving the analysis, process
finalisation, resolving process and technical issues. The Senior
Consultant performs the role of a Team Leader and ensures high quality
service and high client satisfaction. The Senior Consultant will be
involved in preparing the detailed level plan for their functional area.
The Senior Consultant will also assist in business development
activities by providing proposal inputs.
The Senior Consultant must ensure that the tasks continue to address the
needs of the client and fit within the overall scope of the project, and
are completed on time and within the budget. When issues surface that
could change the scope of the project, the Senior Consultant should
report to the Project Manager and negotiate the impact of these changes
with the client.
Senior Consultants are expected to invest time in the professional
development of other consultants. They act as role models through their
dedication to client service and problem solving and demonstrate their
high-level calibre and capabilities. They provide feedback to their
fellow junior consultants for improvement in their performance.
This position is very visible within SAP and client organisation. Senior
Consultants are expected to build strong relationships and solid
reputations within the industry and market they serve.
Responsibilities:
* Works on more than one engagement at a time. Manages small
engagements or a portion of a large engagement
* Assists in the development and implementation of the project
plan for a project. This includes drafting the project plan (scope,
deliverables, timelines and resources), identifying and recruiting team
members, and preparing and assisting in the preparation of individual
work plans.
* For assigned area, oversees all project activities leading to
the implementation of the requirements.
* Senior Consultants demonstrate creativity and thought
leadership, and use their experience in substantiating the proposed
solutions to the client.
* Contributes to consulting projects by analysing client's
business processes and mySAP solution design. Moves logically and
creatively from facts to conclusions
* Performs configuration and assists clients in testing cycles.
* Assists the client in mySAP knowledge transfer.
* Maintains and expands client contact at high levels and builds
credible relationships with key client personnel.
* Understands client requirements and assists in selling
additional business. Works closely with SAP sales force to create and
define consulting projects and ensures that the client's overall
business objectives and needs are translated into well-defined and
justified projects. This includes preparing work plans and contributing
to proposals that describe the process use to meet the client's needs
and include deliverables, timelines and estimates of the costs and
resources required.
* Primary responsibility is preparation and contribution to the
process design workshops, provide directions to the consultants and
configure the mySAP system, demonstrate and gain acceptance from the
customer.
* Deploy consultants in the technical preparation of Business
Process Procedures, Test Scenarios, End-user documentation, and User
manuals
* Sets priorities appropriately. Ensures that work outputs are
timely and of the highest quality
* Continually develop mySAP core skills, IS-specific skills and
cross-functional expertise and business knowledge based on accumulated
experience. Applies knowledge gained from each project experience to
execute future tasks for projects more effectively.
* Use ASAP methodology and tools in the project
* Perform any administrative tasks that are involved in a project.
* Leads the execution of assigned project tasks in areas of
demonstrated competence. This includes facilitating meetings/task
groups, tracking and influencing task group progress, tracking project
deliverables, etc.
* Interacts with SAP organisation as appropriate, to deploy the
requisite expertise on the engagement team to address specific client
needs in a timely and efficient manner and ensures client access to the
best available resources within SAP. Works with SAP Implementation
Partners to ensure seamless delivery of services to the client. Also
informs SAP organization about client needs and trends in the
marketplace and alerts them of potential long-term opportunities.
* Is a key client contact and will exercise authority appropriate
to particular client requests commensurate with client expectations of
decision-making and consistent with SAP policies and practices. This
will include decisions on resources, contracts, and other
business/process issues where the Senior Consultant is representing SAP.
* Assumes additional responsibilities as required
* Occupies a non-management position. However operates
autonomously and receives management direction as appropriate.
* Acquires additional SAP skills in cross-functional areas and
enabling technologies
PLATINUM CONSULTANT (K5)
Position Concept
Platinum Consultants are involved in large and multiple engagements.
They have Industry focus and are very senior in the consulting
organisation with outstanding track records in industry. The Platinum
Consultant understands and appreciates SAP offerings and mySAP product
capabilities. He utilises his industry skills with SAP product skills to
leverage new opportunities for the SAP country-consulting organisation.
They have overall responsibility for project results including quality
of deliverables, client satisfaction and timelines. The Platinum
Consultant provides direction from Industry Specific or new offering
perspectives to the project team. They would also perform specific tasks
based on the demands of the project.
The Platinum Consultant participates in pre-project activities, such as
defining client opportunities, determining scope, and formulating the
approach to address the client challenges.
Platinum Consultants place heavy emphasis on the client relationship.
Working with the Project Director or Consulting Manager they prepare
proposals that result in client commitment to new and/or expanded
projects.
Platinum Consultants are responsible for contributing to the
professional development of Consultants and may have specific management
responsibilities as well, e.g. administering the professional
development of Consultants. They serve as role models through their
thought leadership, dedication to client service, and routine production
of high quality work. They are mentors and coaches for consultants. They
also provide feedback to Consultants on their consulting performance.
They are active participants in the development of their practice,
including consultant's training/education, mentoring and the recruitment
of new consultants.
Platinum Consultants are the authority in the Industry they represent.
They are active participants in many of the initiatives driven by many
of the Industry associations in the country. They position SAP as a
solution provider as appropriate in these meetings and discussions. They
must be outspoken and well-accepted speakers in many of these key
meetings and gatherings.
Industry knowledge with business, functional knowledge and experience is
a prerequisite. Understanding integrated business environments is
essential. Project Management skills are desirable.
The Platinum Consultant conducts senior management and process design
workshops at strategic level and ensures high quality service and high
client satisfaction. The Platinum Consultant will proactively assist in
business development activities by providing and developing new
initiative proposals.
This position is very visible within SAP and the client organisation.
Platinum Consultants are expected to have some bearing on client
decisions and to have solid relationships with key client executives at
high levels. They should have strong relationships and solid reputations
within the industry and market they serve.
Responsibilities:
* Works on multiple projects simultaneously.
* Provides industry specific solutions and best practices
knowledge to clients
* Develops a solution framework and an implementation plan for
industry specific projects or projects using new dimension products.
* Uses and ensures that mySAP solution maps, ASAP and other
relevant SAP methodologies and tools are deployed very effectively in
client strategic workshops and deliveries.
* Ensures solutions are delivered on time and are of the highest
quality.
* Conducts strategic level workshops with clients to drive a SAP
solution for acceptance and implementation
* The Platinum is involved along with the Project Director/Project
Manager in drafting the project plan (scope, deliverables, timelines and
resources), identifying and recruiting team members, and preparing and
assisting in the preparation of individual work plans.
* For assigned area, oversees all project activities leading to
the implementation of the requirements.
* Platinum Consultants demonstrate creativity and thought
leadership, and use their experience in substantiating the proposed
solutions to the client.
* Contributes to consulting projects by analysing client's
business processes and designing the appropriate SAP solution. Moves
logically and creatively from facts to conclusions
* Maintains and expands client contact at high level and builds
credible relationships with key client personnel. Meets regularly with
client executives to discuss business strategy issues of concern to the
client organisation. Manages client expectations. Has some bearing on
client decisions.
* Understands client requirements and assists in selling
additional business. Works closely with SAP sales force to create and
define consulting projects and ensures that the client's overall
business objectives and needs are translated into well-defined and
justified projects. This includes preparing work plans and contributing
to proposals that describe the process use to meet the client's needs
and include deliverables, timelines and estimates of the costs and
resources required.
* A Platinum Consultant is a role model and coach for consultants-
performs the mentor role. Provides meaningful feedback to consultants to
the overall performance evaluation of project team members.
* Sets priorities appropriately. Ensures that work outputs are
timely and of the highest quality
* Perform any administrative tasks that are involved in a project.
* Leads the execution of assigned project tasks in areas of
demonstrated competence. This includes facilitating meetings/task
groups, tracking and managing task group progress, tracking project
deliverables, etc.
* Interacts with SAP organisation as appropriate, to deploy the
requisite expertise on the engagement team to address specific client
needs in a timely and efficient manner and ensures client access to the
best available resources within SAP. Works with SAP Implementation
Partners to ensure seamless delivery of services to the client. Also
informs SAP organisation of client needs and trends in the marketplace
and alerts them to potential long-term opportunities.
* Is a key client contact and will exercise authority appropriate
to particular client requests commensurate with client expectations of
decision-making and consistent with SAP policies and practices. This
will include decisions on resources, contracts, and other
business/process issues where the Senior Consultant is representing SAP.
* Assumes additional responsibilities as required
* Occupies a non-management position. However operates
autonomously and receives management direction as appropriate.
* Acquires additional SAP skills in cross-functional areas and
enabling technologies
* Works with the Project Management Team and the Country
Consulting Manager to secure SAP's Consulting future and current
strategy and its execution
PROJECT MANAGER (K5)
Position Concept
The Senior Project Manager is a key position in the Consulting
Organisation. They are responsible for the successful delivery of a
project in terms of scope, deliverables, timeline, budget, client
satisfaction and employee satisfaction. The Project Manager is a window
through which the client views SAP and the SAP organisation.
Project Managers must have a rational view to various situations in the
project. They must be very sensitive to client needs bearing in mind the
conflicting requirements that a client team would demand, and the
delivery capabilities of the consulting team.
The skills of the Project Manger are - good project planning skills,
understanding and appreciation of the complexities involved in the
implementation of an integrated application, good communication skills
and people management skills. The Project Manager must be team builder,
motivator, and coach. Must be able to resolve conflicts, take
appropriate decisions at the right time and substantiate the proposed
solution to the client. The Project Manager, with the support of the
Senior Consultants or Integration Consultants, would take the right
decisions for the project. The Project Manager is a taskmaster when it
comes to the delivery of the project. They are responsible for managing
issues that arise from either the consultants and / or the client.
Prior experience in SAP implementation or SAP Project Management is
desirable. The Project Manager must be ASAP certified, to ensure that
the necessary methodology and tools are being deployed fully in the
project by the project team. The consulting team reports to the Project
Manager through their Team Leaders for that project. The Project Manager
works with the Client Project Manager for planning activities, obtaining
necessary infrastructure support and decisions that are required for the
project to progress.
The Project Manager should ensure that regular meetings between the
team, as well as the Steering Committee are conducted. In case of lapse,
the Project Manager communicates the same to the Client Management team
to evoke response, commitment and involvement. As necessary, the Project
Manager may involve an SAP Project Advisor or SAP Auditors, to assist
them in providing useful recommendations for the progress and successful
implementation of the project. Project Managers normally report to the
Consulting Manger in the SAP Organisation. In case of large projects,
where parallel implementations are running, the Project Manager would
report to the Project Director. The Project Manager would take the
Project Director's advice and inputs to run the project.
The Project Manager interacts with the SAP organisation when support is
required in terms of Consulting skills, technical support or SAP issues
or any business issue that is beyond the scope of the implementation.
The personal characteristics of a Project Manager reflect their
capabilities in managing the project as individual resources:
* A well-balanced and tolerant nature
* Ability both to lead and work in teams
* Ability to cope with stress
* Rhetorical skills
* Capacity for enthusiasm and dedication
* Ability to make decisions and assertiveness
* Management and policy-oriented thinking
* Creativity and good judgement
* A systematic approach and way of working
* "Social skills" include abilities that assist the project
manager in coping with difficult social situations
* They assist the PM hold responsibility and take on leadership
* A good understanding and empathy towards human nature
* Ability to deal with conflict and develop relationships
The Professional Skills of a Project Manager should be based on an
all-round, global knowledge:
* SAP Product awareness and the architecture
* Managerial and economic aspects
* Information technology basics
* General project management
* Foreign languages
* Leadership techniques
* Planning and control techniques
* Good Presentation and Communication skills
* Project Planning and Detailed work plan development skills
* Working materials for project management
* SAP implementation tools (Reference Model, IMG (SPELL OUT),
ASAP, others)
* Best Estimator tool for estimating the labour requirement
* Standard software products used at SAP
Responsibilities:
* The Project Manager works on one engagement at a time
* Responsible for implementing mySAP solution within the scope,
time and budget
* Responsible for deliverables with high quality and client's
satisfaction
* Conduct weekly project team meetings
* Conduct monthly or (periodic) Steering Committee Meeting
* Resolve issues without affecting the project
* Communicate and stay in touch with the Senior Management of the
Client organisation with regard to the progress of the project. Gain
acceptance and support for the rapid implementation of the project
* Motivate team for better results
* Provide appropriate support for the project team as and when
required
* Involve SAP Auditors or SAP Project Advisor as and when
necessary
* Work with the Implementation Partner consulting resources for
smooth and cordial functioning of the project activities
* Ensures knowledge transfer occurs with the client team
* Makes clear the roles and responsibilities of the consultants
team and client team
* Ensures outputs and results from both client and consultant
teams
* Report exception to the SAP Project Director/Senior Project
Manager and Client Management
* Prepare weekly progress reports through the Team Leaders and
circulate
* Prepare or provide support in the preparation of Steering
Meeting presentations as well as the minutes
* Overall management of the project
* Have minimum escalation's to SAP Organisation
SENIOR PROJECT MANAGER (K6)
Position Concept
The Senior Project Manager is a key position in the Consulting
Organisation. They are responsible for the successful delivery of a
project in terms of scope, deliverables, timeline, budget, client
satisfaction and employee satisfaction. The Project Manager is a window
through which the client views SAP and the SAP organisation.
Project Managers must have a rational view to various situations in the
project. They must be very sensitive to client needs bearing in mind the
conflicting requirements that a client team would demand, and the
delivery capabilities of the consulting team.
The skills of the Project Manger are - good project planning skills,
understanding and appreciation of the complexities involved in the
implementation of an integrated application, good communication skills
and people management skills. The Project Manager must be team builder,
motivator, and coach. Must be able to resolve conflicts, take
appropriate decisions at the right time and substantiate the proposed
solution to the client. The Project Manager, with the support of the
Senior Consultants or Integration Consultants, would take the right
decisions for the project. The Project Manager is a taskmaster when it
comes to the delivery of the project. They are responsible for managing
issues that arise from either the consultants and / or the client.
Prior experience in SAP implementation or SAP Project Management is
desirable. The Project Manager must be ASAP certified, to ensure that
the necessary methodology and tools are being deployed fully in the
project by the project team. The consulting team reports to the Project
Manager through their Team Leaders for that project. The Project Manager
works with the Client Project Manager for planning activities, obtaining
necessary infrastructure support and decisions that are required for the
project to progress.
The Project Manager should ensure that regular meetings between the
team, as well as the Steering Committee are conducted. In case of lapse,
the Project Manager communicates the same to the Client Management team
to evoke

PR Release with classification

Hello all,
I have created the CHARACTERISTICS: 1. PRTYPE with CEBAN and BSART
2. PRPLANT with CEBAN and WERKS
3. PRVALUE with CEBAN and GSWRT
and CLASS: PRRELEASE with relase starateygy 032
But when I try to create RELEASE GROUPS AA with class as PRRELEASE I am getting the below error.
Please check release classes (see long text)
Please help me to solve this.
Regards,
SA

Hi,
You have created new release class for PR as PRRELEASE & now creating release group and assigning PRRELEASE (release class for PR), so you are getting error!
In your system already for PR release, a RELEASE CLASS FOR PR is created. So when you are assigning a new release class for PR as PRRELEASE ,system showing message.
You can use only ONE release class PR,ONE release class PO, ONE release class SES. Now either you can use old RELEASE CLASS FOR PR or you can delete 1st assignment of old RELEASE CLASS FOR PR to all release groups and then assign your new release class for PR as PRRELEASE with new Release Group.
For more check the link:
/people/arminda.jack/blog/2009/03/12/mm--check-list-to-detect-and-solve-release-strategy-issues
Regards,
Biju K

Strategy 50 issue

Similar Messages

Maybe you are looking for