Egypt SAP implementation leagl requirment

HI
Any one implemented in Egypt let me know below:
1. Tax structures wtih respect SD
2. As per information direct delivery as third party not possible?
3. Any special requirment in TAX structure from SD side.
Thank you in Advance.

http://help.sap.com/erp2005_ehp_05/helpdata/en/25/340b0507434193adbfe3f8fc8896c7/frameset.htm
refer here for all technical components

Similar Messages

Critical Issues During SAP Implementation or After Golive

Can anybody tell me one of the most critical/ challenging issues During SAP Implementation or After Golive
in these modules:-
MM implementation
PP implementation
SD implementation
FI/CO implementation
PS implementation
QM implementation
HR implementation
BI implementation
XI implementation
Thanks and regards
RS

hi,
I will list out few of critical issues in
Implementation :
1 . Ensure 100% mapping of business process for all modules with SAP(avoid customization in support phase)
2. Unit & Integeration testing should be through with all validations
3. Master datas(Vendor,Customer) care must be taken will uploading datas thru LSMW,
If there are common vendors for all plants,Create a vendor for a plant extend it to other plants
4. Check tax procedures are customized according to requirements.
5. Complete all print document customizations before go live
6. Complete end user training(2 or more cycles) should be top priority before go live(This will avoid
cancellation/reversal of documents after post go live)
7. Ready with standard MIS reports & customized reports for business decision making
8. Excise opening balance updation in tables for RG1 register in tables(Note 951955) on go live
9. Check all tables datas are updating correctly
10. Declare go live to SAP Support
11. Check All user authorization should be correct according to their roles.
12. Centeralize all master datas creation(avoid duplication)
13. Create transaction variants to avoid entires in unnecessary fields & make certain fields mandatory.
14. Ensure document numbering is completed for all documents
15. Validate accounting entries are hit properly according to requirement in quality client with FI CTM(Core team member).
After Go live :
1. Missing authorization for users will play key part here,For ex : PGI while doing delivery,Excise capture & post in MIGO/J1IEX.
2. Do internal audit every month,identify transactions if there will possibility for misuse or wrong entries,requires validation,identify users weak in certain areas.
3. Identify there is enhancements to be done in transaction process(By step-2)
4. Prepare a list of month & year end activities to be performed for all modules give to users
5. Prepare a list of frequently used transaction codes module wise give it to users
6. If there is subcontracting,ensure challan creation,GR,reconcillation should be done regulary(monthly)
7. Train the users,take reports in respective modules.
8. Additonal customization might be done in print documents.
9. Instruct users/CTM's to adapt SAP Standard practise
10. Update excise tax rates after every indian budget
Hope it helps.
Edited by: Jeyakanthan A on Apr 29, 2010 6:48 PM

Roles & Responsibilities of a Basis consultant in an SAP implementation

Hi All,
What are the Roles & Responsibilities of a Basis consultant before/during/after an SAP implementation project?
Please list all of them separately.
Regards,
Nivas

1.    1. Perform User administration and role/profile assignment.
2.   2. Perform Role Creation, Modification and Full trouble shooting support for the users authorization failures in all SAP applications and resolving the Security issues and support in integration testing of Roles/Profiles.
3. 3. Maintain the integrity of the SAP environment by managing the SAP Correction and Transport System (CTS) to ensure all configuration and development objects are promoted properly.
4.    4. Distribute the online SAP user workload and monitor and manage the SAP background job workload.
5.   5. Perform OSS / SAP Service Marketplace: Searching notes & creating OSS messages for the respective queries to improve the Performance. And software download, Maintain System Data, License Key & Maintenance Certificate, Developer & object registrations and connection maintenance etc.
6.     Starting and Stopping SAP instance/(s).
7.   6. Preventive Maintenance activities - Support Pack/Plug-in implementations, Kernel upgrades, OSS note applications and to apply support pack for Java using JSPM.
8.    7. SAPGUI/SAPLGPAD troubleshooting and maintenance/upgrades/installations.
9.    8. Prepare and maintain system documentation, procedures, and standards.
10. 9. Perform SAP Database Administration – Space management, database reorganizations, design and implement backup and restore strategy, maintain database security, administer database performance, database problem determination and resolution, etc.
11. 10. Perform SAP Installation, Post installation, client administration, System Refresh and Post-Refresh activities as required.
12. 11. Perform parameter modification, Buffer, memory management, performance tuning and troubleshoot.
13. 12. Perform SAP Licensing – Indentify inactive user, user classification and prepare System Measurement result for SAP Global Audit team.

"Case use" technique for SAP implementation?

Hello all,
has anyone used "case use" technique for SAP implementation? I mean for standard process, not only developing.
Any recommendation about it?
Thanks in advance and best regards,
Adolfo

It would be helpful to go through the help document of ASAP Methodology.
The following information may clarify some doubts/requirements you have.
Generating the Project IMG through ASAP:
After you have set the project scope, the next step is to generate the Project IMG. From the Business Process Master List (BPML), you can directly access the IMG activities relevant for configuring each process.
BPML: The Business Process Master List, along with the Business Blueprint, is a key result of the second phase of the Roadmap. Microsoft Excel tables contain the SAP scenarios, process groups, and processes that have been set in scope in the SAP Reference Structure, and are crucial for configuring your SAP System. In Realization, the third phase of the Roadmap, the BPML provides the basis for monitoring and steering test activities and for configuring your SAP System. It contains the titles of the structure items, and displays the status, the owner, links to documentation and links to the SAP System. Amongst other things, the BPML allows you to:
1) Set your baseline and final scope. These are used for baseline and final configuration.
2) Access the Project IMG and specific IMG activities assigned to structure items.
3) Access integration test plans, which help you carry out all required integration tests.
The Prerequisite is you have set the project scope.
Process Flow to use the Business Blueprint as a basis for configuring your SAP System:
1) Set the project scope.
2) Generate the Project IMG.
3) Generate the BPML.
4) From a specific processes in the BPML, you can go to the relevant IMG activities and make Customizing settings.

Closing down an SAP implementation for restart later

OK, this is a strange one, to me at least, but here goes...
Our company has been using an implementation of SAP for a specific project that is now coming to an end. They want to close down the system completely, but with the option of relaunching it later using the data records that currently exist, but probably imported into a new Enterprise structure. The financial data will also have to be maintained for audit and other legal purposes.
I've done several SAP implementations but never a close-down like this! From a functional, rather than a Basis/infrastructure, point of view, does anyone know what configuration or other data protection measures we will need to take to safeguard the data and facilitate a restart so much later? Are there any other issues the company will need to consider? We use ECC6 and FICO (GL/AR/AP/Banks) with COPA, and SD MM
During the period between the closure of the SAP system and its re-initialisation in expanded form - maybe 18 months later - they will run the functions now done in SAP in an old system. Again, I have done transfers of data from legacy systems into SAP but never the reverse. Any suggestions, other than ensuring compatibility, for this process?
I strongly suspect that when they look at re-starting the use of SAP it will essentially be a new implementation from scratch, with perhaps some Customer/Vendor/Materials/FICO master data imported, but involving all the stages of the road map. However, if there is anything we can do to help whoever does that then we will. So, any suggestions or information will be welcome.
Thank you
David
Edited by: David Crossley on May 13, 2009 12:14 PM

Note also that the support provided by Nokia for a particular phonemodel does not require that there is a factory still manufacturing that model. In other words, spare parts can be provided, as well as software updates and support, without factories churning out new units.
And while Nokia has closed a couple of factories, the company still has serveral that are operational all over the world, and for which no plans for closing has been announced.

SAP Implementation Process !!!

Hi Folks,
I need brief information about the SAP implementation process. As per the ASAP Methodology we have different phases involved in the entire implementation process from Project preparation,Blue print analysis,Realization,Final Preparation and Go Live Support.
I did not involve myself into implementation. Being a Basis consultant I would like to know what is the involvement of basis consultant in each phase in detail and what are the activities being carry out by a basis team, what would be the avg team size and what would be the duration of the project approximately. I know it depends on the project and modules being used,architecture and all. i just wanted to know the rough details for information.
I would really appreciate for any useful information.
Regards,
Vinod

Hi Viond,
Please find below an elaborated details for SAP Implementaion.
The ASAP (Accelerated SAP) Roadmap provides the methodology for implementing and continuously optimizing your SAP System. It divides the implementation process into five major phases and offers detailed Project Plans to assist you (Microsoft Project format). The documentation stored at each level of the Roadmap tree structure contains recommendations on implementing your SAP System and links to helpful tools and accelerators. We use SAP Solution Manager for the same and define the steps and this information can be transformed into MPP.
The implementation of your SAP System covers the following major phases:
Project Preparation
In this phase you plan your project and lay the foundations for successful implementation. It is at this stage that you make the strategic decisions crucial to your project:
Define your project goals and objectives
Clarify the scope of your implementation
Define your project schedule, budget plan, and implementation sequence
Establish the project organization and relevant committees and assign resources
Sizing for the SAP Servers (SAPS) Important for Basis.
Business Blueprint
In this phase you create a blueprint using the Question & Answer database (Q&Adb) older versions and now it has been replaced by new value adds from SAP in Solution Manager, which documents your enterpriseu2019s requirements and establishes how your business processes and organizational structure are to be represented in the SAP System. You also refine the original project goals and objectives and revise the overall project schedule in this phase. In short its As is >> To be its from from functional consultant (mapping of business process) Basis will be involved how and when backup will be taken what 3rd party/vendor will be used, how users will be handled (CUA or normal procedure).
Realization
In this phase, you configure the requirements contained in the Business Blueprint. Baseline configuration (major scope) is followed by final configuration (remaining scope), which can consist of up to four cycles. Other key focal areas of this phase are conducting integration tests and drawing up end user documentation. Major part will be creation of transport requests and transportation to QAS system. Configuration of SAProuter, Solution manager and its various configuration
Final Preparation
In this phase you complete your preparations, including testing, end user training, system management, and cutover activities. You also need to resolve all open issues in this phase. At this stage you need to ensure that all the prerequisites for your system to go live have been fulfilled...Final Check.
Go Live & Support
In this phase you move from a pre-production environment to the live system. The most important elements include setting up production support, monitoring system transactions, and optimizing overall system performance.
You can also download an HTML version of the ASAP Core Roadmap 7.1 on [SAP Services Marketplace - ASAP Roadmaps and Run SAP Roadmaps|http://service.sap.com/asap] (SMP login required).
All the best !

SAP Implementation at Core Shop in Foundry.

Does anyone have idea about what scenario is required to be configured for SAP implementation in Core Shop of Foundry. Cores are basically sand structures manufactured with the help of Core Manufacturing Machines. After few operations & sub Assys, these cores are then placed in Mould to get cavities in the castings on the Moulding Line. Then these moulds are poured with Molten Metal & we get Castings. This is the process in brief.
With Sand as input material procured as an indirect material. Cores would also fall in same category. Cores are prone to damages at every operation (washing, drying, Water jacket, Trimming, L-bolt fitment etc) during manufacturing process.
Raw Sand --->Raw Caores from Core manufacturing Machines -
> Semifinished or Sub Assy Core Area -
> Core Setting Area -
> Finished Core Assy placed in the Moulds.
At every stage given above, rejection codes are to be maintained as Rejection % is important factor from improvements point of view..
How to map this process in SAP? Which SAP scenario is to be used?

Hi,
u can use discreate manufacturing scenoria for core manufaturing.
My suggestion is as follows,
1.define the finished core as core assembly.
2. since demand of core is decided from the demand of mold, u can define core assembly as bom item of Mold(under Mold BOM header).
3.by doing this, during the MRP, systems gives procurements proposals for core assembly if there is no stock avalibale.
4.so we ccan create seperate production order, and we can confirm yield and rejection qty.
5.after production u can enter the rejection qty while conforing production order.
letme know if u have any futher doubt..
regards
pradeep

SAP Implementation Starting

Hi all
I am heading an SAP implementation for my company .
I want to make sure that the implementing company
delivers a fine and within time and budget solution.
What are the points that are usually written in contracts
to avoid delays / bad solutioning ?Pls give me tips as to
what all I can have as part of the contract .
All suggestions / Inputs welcome.
Thanks

Dear Oops Kooops,
You question is broad in spectrum. To start with you can refer to some good Project Management books in SAP.
These are some of the details you can look for:
Business Goals
Know how your project will benefit the business, and make sure you communicate those benefits to the employees who will use the technology. Poorly defined goals doom a technology project; well-defined goals help keep all project personnel working together. The system with unclear business benefits is one better left unsponsored and undone.
User Involvement
Getting user buy-in requires more than just communicating benefits. It also helps dramatically to enlist users' collaboration in designing or selecting the system.
To convince business line managers to lend their workers to the front end of a project, executives recommend talking to their wallets.
Risk Management
Every I.T. project faces risk, whether it is technical (caused by unproven technology or integration problems) or business risk. Veterans say project sponsors should not only understand the risks but also demand that contingency plans be put in place before the first nail is hammered. But even though risk management is a project management basic, it is easy for executives with little technical knowledge to ignore it because they are intimidated by the technology. Fortunately, they also say technical risk is easier to manage than business risk. If the project hinges on a relatively new technology, it makes sense to build and test a prototype before going whole hog.
Scope Management
Keeping requests for new features from derailing or slowing down a project is a step that should be handled by the project manager, but occasionally the executive sponsor has the clout to say no to a request the IT leaders can't refuse. Besides inflating costs, scope creep can deflate user enthusiasm as the project's benefits are pushed off. Getting the project done quickly is a good goal for the executive sponsor to champion; bells and whistles can be added later, after the initial rollout. "Vanilla is a very good flavor"
Appropriate Accountability
No accountability, no progress--that's no surprise. The challenge in IT projects is to hold the right people accountable for the right deliverables. The IS department's job is to hand over the specified level of system functionality by the due date. After that, it's up to the business workers to get the specified business benefits out of the system. And the executive sponsor should make sure accountability is in place to enforce that division of labor.
Non-IT execs have a tendency to exaggerate the role IS workers will play after a system is rolled out. As a result, it is common to point the finger for system failure at IS. That gives the other employees less incentive to make the new system work.
IS and business line workers develop a lot more synergy when both feel an equal burden of responsibility.
Helpful Hype
Amidst all the spreadsheets, numbers, risk analyses and so forth, remember to add a spoonful of sugar for those who will actually have to use the technology.
Do let me know in case of any queries.
Hope this helps you.
Regards,
Rakesh

SAP Roles and Access for SAP Implementation team members

Hi,
Is it correct practice to give SAP_ALL role access for all SAP Implementation team members in Dev and QA?
If not, what is the correct practice?
Kindly let me know

Madhu,
It is NOT correct practice to give anyone SAP_ALL in any of the systems; not DEV, not QAS, and certainly not PRD. However, many implementation teams (and particularly consultants from SIs) insist that they cannot possibly do their jobs without it. This is completely incorrect as there are specific roles for them to use for that purpose. The only circumstance where it could be justified is if you require a special "firefighter" role - and even then, I would still be a bit doubtful.
You should also consider that once you have given someone SAP_ALL, they will fight tooth and nail to keep it. It also means that they probably are not testing the user roles correctly. Most of those that insist they need it simply do not understand the security issues and probably don't care.
Just think; if they have access to do soemthing that they shouldn't and then cause a big problem, are they the ones that will have to fix it or are they going to expect you to do it? If they expect you to clear up after them, then you have the right to insist on restricting their access to cause issues in the first place.
But I know just how demanding they can be....
Best of luck
Tony

SAP Implementation for a building construction company

Dear All ,
               We are doing SAP implementation for a building construction Company .My client is responsible for building construction .What they do is initially some 10 members of this Company will create a society(Legal Entity) .They are like promoters for company . They will put advertisement for buying of flats belonging to that society . Then some 20 members (outside) join this society by registering who are actual buyers of the Flats which society builds .
               Then this society passes a resolution that my client will be the building contractor for flats . After that these 20 outside members will pay the full amount . After this Flats were built then these members will occupy flat ,then after some 4 -5 years of maintenance these 10 core members of society will hand over the society completely to secondary members and come out of the society .
                Now how we will map this society in SAP .One society can have more than one project going on . Somebody is suggesting to treat a society as a company code . But we have more than 250 societies . Is it viable . Shall we create plant for each project .
Regards
Abhijit Das

Hi Abhijit,
Suggestion by our PS consultant for your requirement is
>>>I would suggest that in case of PS, consider society as Business area and each building as one Project and under project WBS and if any activities floor wise consider as networks.
Oust side membersu2019 Account payables and receivables and downpayments will come under FICO.
Regards,
Uzair

Please help how to design query to implement this requirement.

Dear Expert,
Here is what I have and what the requirement is:
I have a InfoCube:
Dimensions:
1. Material
2. Currency
Key Figures:
1. Qty
2. Amount
We want to get the Qty and Amount by Material, but use Currency to be the filter.
It means for example, if the Currency have CNY for one material, we need to show all the Qty/Amount, not only Qty/Amount in CNY.
So please help give some idea about how to design the query to implement this requirement.
Thank you,
Andy

Hi Andy:
To accomplish your requirement you need to do 2 things:
1. Create a Variable for the Currency (to be used as the Target Currency not as a filter for the Characteristic itself).
2. Use the Standard Currency Conversion for the Amount Key Figure (Conversion Tab).
This way, while executing the report you can select any currency you want and all the amounts will be converted to that currency.
Take a look at this paper:
"How to... Use Variables for Currency Conversion"
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/287bab90-0201-0010-f48e-cc55b0cd13d0?quicklink=index&overridelayout=true
A more detailed explanation can be found on this article provided by Ramakrishna Gattikoppula:
"Currency Conversion in BI 7.0"
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a0d5bf96-b19b-2c10-e3b6-e2f12a3de99a?quicklink=index&overridelayout=true
In summary, to work with the Standard Currency Conversion you need to define 4 things:
- Exchange Rate Type.
- Source Currency.
- Target Currency.
- Time Reference.
Regards,
Francisco Milán.
Edited by: Francisco Milan on May 31, 2010 11:19 AM

U00C4S IS STUDY in SAP implementation in MM context

Dear friends Can any one explain what exactly ÄS IS STUDY means in SAP implementation in MM context. Though I am aware about study of the client requirements and others I would like to know in eloberate what exactly it means if possible some materail on it
regards
Radha

Hi,
AS IS study includes (Materials Management )the complete information about the current purchasing activities and materials management operations of your client company. The current activities like procurement processes, procedures and methods that company follows and should be detailed as possible in your As Is Document
Following are some of the details which may need to be taken cares
1.Current Organization structure (PO, Plants,LS,PG..etc)
2.Details of current IT System or manual systems are in use.
3. Details of any new requirements which are required by the Company.
4. Complete list of all the reports which are currently used by company.
5. List of all new information requirements.
6. Details of master data which need to be uploaded.
7. Details of transaction data which need to be uploaded.
If helpful then reward.
Regards,
Biju K

Tasks/activities of a Basis consultant during SAP implementation

Hi,
Could someone share the list of tasks/activities of a Basis resource to handle during an SAP Implementation project.
Thanks in advance,
Srinivas

HI,
i think these are the simplest Basis activities in an sap implementation.
1. Preapration of the Landscape of the systems
2. Connectivities btw. different systems like SAP R/3 - BW and so on
3. Transport Administation i.e TP creation, release, importing to QA - PRD and so
4. configuration of RFCs and TRFCs if needed
5. Config. of Data Transmissions
6. Config. of IDOCs and Message Types
7. Cutover plan preparation for the Go-Live
8. System back ups and Logs Maintanance
9. Installation of all required Patches and Notes
10. system down time estimatations and planning
Rgds
Radhakrishna D S

Role & Responsibilities of an ABAPer during SAP Implementation

Dear Friends,
Shall anyone of you kindly let me know of a link or send a document addressing the Role & Responsibilities of an ABAPer during SAP Implementation?
Regards,
Alok.

Hi,
ABAPer is required after installation and business study by functional consultant...
In case of upgrade project, ABAPer is required during upgrade (Basis activity) itself in SPAU and SPDD step.
Otherwise, ABAPer has following role in their area:
1. Business study in brief. (To resolve simple issue and to understand logic)
2. Coding for User exits / enhancements to co-operate with functional consultant.
3. Custom reports / Program developement (Normally print programs and some analytical reports)
4. Upload program implementation thru' BDC / BAPI / LSMW
etc.
5. Interface developement if required. (in case of legacy system integration projects)
These are the major tasks of ABAPer in implementation project.
Activities that form the SAP implementation process are:
1. Project Preparation
2. Sizing and blue printing
3. SAP Functinal development - here abap comes into picture
4. Final Preparation
5. Go live
Have a look at below link. It will give you more details abt the same.
http://en.wikipedia.org/wiki/SAP_Implementation
<b>Reward points</b>
Regards

Preparation beforehand SAP implementation

Hello Gurus, I'm an OCP in developer track. I look after the customized software of one of the production unit of a big company. Our company runs SAP in other production units and corporate. In a recent move, management decided to bring this unit under SAP and implementation will start by a month. It is also decided that I will get functional role in the project. Now how can I be prepared myself earlier than the implementation starts. Please looking for your expert advice...

Dear Mr. Md. Iqbal,
In my view, you may do some of the tasks mentioned under as per your role in the project:
1) Start building team consisting of IT and functional persons. Functional persons must be champion in their area. these team members should be full time dedicated to the project-take commitment from higher management on this.
2) Inform the functional team to start preparing their processes with flow charts.
3) Get demo of SAP running at other production unit so that your functional team members can start thinking of mapping their processes in SAP.
4) Start learning ABAP if you are going to be ABAPer OR start understanding business processes slowly and gradually. Material management (purchase, warehouse) would be most important part to start with. You may get into other processes as per your area of interest and background.
Most IMP : find out project owner and project manager at your location for this project.
Documentation may seem boring but it will help in longer run so if possible, try to document each and every task, meeting, requirement, commitments from implementation partner, etc. Signing on the document is equally important.
If you are going to be project manager or similar to that, ERP Demystified by Alex, SAP Project Management by Joy Ghosh and many other books may help you further.
God bless you and your company grand success in the SAP implementation project.

Egypt SAP implementation leagl requirment

Similar Messages

Maybe you are looking for