Modify the transaction OAAR Production environment

Dear
We need to change the transaction to open OAAR period of depreciation. But faced with the message that the client is closed. I talked with my staff to open this transaction basis in production but they failed. Does anyone have any idea how this transaction would be opened in production?
Any help is welcome
Sorry for my english

Hi,
In OAAR - you can change the closed period as per depreciation area level and in OAAQ it would change for all the areas.
You have any specific depreciation area where you need to open up the closed year?

Similar Messages

Exit/Badi in the transaction of production order create or change (CO02)

hi all,
I need an exit/Badi in the transaction of production order create or change (preferably during SAVE).
I want to change structure AFVGD-usr02,AFVGD-usr03 .
<b>PPCO0007 Exit when saving production order</b>
the exit is not applicable EXIT_SAPLCOZV_001 .

Hi
we around 200 exit for this tcode i found only three badi for this tcode.
AFABD_CHANGE          Change Relationship
CAUFVD_CHANGE        BAdI: Overall Network Scheduling with Selection Option
SIDAT_UPDATE            Change date of price simulation.
check with this goto se18 and F4 thn give the Package as CO.enter u get this three.
reward pointd if use full

Sandbox to the DEV/Quality/Production environment

Hello,
Is there any way we can Transfer all we had done is Sandbox to the DEV/Quality/Production environment?
We are using SAP 5.2 and had done all the configuration is SANDBOX side.
Please let me know if any one has any information regarding this.
Thanks
IMRAN

Hi IMRAN,
S2S functionality allows you to transfer only product-related configuration which list you can find in the online help as Alex suggested. However, you will not be able to transfer System Rules or Collaborations in particular. Thus if you need to "copy" the entire configuration of ME @ Sandbox, then you need to export the database dumps of ME WIP and ODS from Sanbox and import to e.g. QA and re-create synonyms in QA. Then install/deploy the ME build in QA and point to the new database.
Regards,
Sergiy

IMG Transactions in Production Environment

Hi all you SAP experts
I would dearly like to know how you handle the execution of IMG transactions like OB52 (Opening and closing of accounting periods), OB83 (Tax Rates) etc. in your production environment. We currently "Open" the system for the business user (system is kept non-modifiable) to allow the user to perform the transaction. Once completed, we "Close" the system again. However, I do not believe this is best practise. Our DEV and PROD environments are not in sync regarding master data which makes maintaining IMG in DEV and transporting to PROD for some IMG transactions impossible (eg. Linking of a symbolic account to a vendor).
What is the best way of handling this?
Regard
Neels

For OB52 can be alternatively accessed through F-60 which can be give to the needed users.
OB83 one may need to work with security to find a *object* which can be used to give security to modify /display.
regards

Creating a Bug after Launching the Project into Production Environment

Hello My Friends;
As I'm New in Implementing TFS 2013, would U advise me How to open a new Bug - after Launching The Project in to Production Environment which has already conducted more than a year ago before implementing TFS. So, a Bug has come from the Business Colleagues.
I'd like to open a new Bug on TFS ?!
What Repro Steps Mean ?!
Thanks for your supportRegards;
EB

Hi EB,
Thanks for your post.
After you connected to team project using your VS, you can open a new Bug work item in VS, please refer to the steps in this document:
https://msdn.microsoft.com/en-us/library/dd293538.aspx.
The Repro Steps mean: provide the detailed reproduce steps there, then developer can follow the detailed steps to reproduce this bug and try fix it.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Getting the error access denied trying to modify the workbook with identifier in Disocverer Admin

Hi All,
I have exported a workbook created by business user as an .eex file logging in as discoverer admin from a Production enviornment (transactional databse) and trying to import it to a different environment called reporting environment ( non transactional databse) and getting a warning 'WFS GTP REPORT SINAPORE.eex:Access denied trying to modify the workbook with identifier 'WFS_GTP_REPORT_SINGAPORE'.
It says Files Partially Imported so clicked on Finish to complete the import.
The report has been imported under the user account but the sharing to the different responsibilities/Users has not been imported. I need to import the report with the sharing of the responsibilities/users as well.
I do not have an option login into discoverer administratore using the user account, i can only login using the administator account ( i know loging in as the business user it self will allow you to import the sharing). But our DBA's oppse this is a security threat for the users as you are logging in as the user in production environment.
Please help with this issue.

I have the same problem, and I figured out that my windows is installed in french, and every users groups are created in french also, groups like Everyone don't exists and i can't change by console.
Regards, Roberto Borges please remember to mark the replies as answers if they help and unmark them if they provide no help.

Customizing PFAC Transaction in Production (Role to Postion Mapping)

All,
We have added email recipients in PFAC. Our recipents are based on 'Roles to Position Mapping'.
We often get a request to add or delet a recipient in production.
We can transport our changes from Dev as the roles to position mapping is different in Dev QA and Prod.
I know SAP makes some transaction maintenable in Production. So that we can directly make the changes in Production environment. or is there any other way that you must be following at your work place to overcome this issue.
I have also opened a OSS note for this, thought will get some insight from the gurus here.
Are you aware if PFAC is one of them.
Regards,
XIer

SAP Note 534029, provide thesolution I was looking for.

MSDN and Production Environment (again)

I started this on another forum before I found this one, but this seems a more suitable place.
The definition of "production environment" seems rather odd. In some responses on this forum it appears to refer to "soft" systems whereas the latest MSDN licence refers to environment and physical kit.
Below is a conversation I had over email with someone from MSDN and I find the whole thing utterly bizarre. I cannot for the life of me see how this helps anyone apart from MS being able to charge for non-production software. It renders having a powerful desktop
for local lab experimentation pointless as you're not allowed to install anything and effectively doubles the hardware cost to small companies if they have to buy a separate server for any testing work (yes, best practice and all that, but budgets...) or pay
out for a Windows Datacenter licence.
Question:
“If a physical machine running one or more virtual machines is used entirely for development and test, then the operating system used on the physical host system can be MSDN software. However, if the physical machine or any of the VMs hosted on that physical
system are used for other purposes, then both the operating system within the VM and the operating system for the physical host must be licensed separately.”
Is this actually saying that if I have a physical server licenced with a purchased (not MSDN) Server 2012 R2, running Hyper-V with, say, a production file server VM on it, that ALL Windows VMs on that machine must have purchased licences even if they
are only for development & testing purposes?
Is this saying that all production and development Windows VMs must be only completely separate hardware, cluster, SAN, etc otherwise you must pay for full licences for the VMs?
Or does it just mean that the bare metal licence (plus any additional ones required for running further production VMs) must be purchased if the VMs are a mix of production and development?
Answer:
We kindly inform that any products licensed under the developer tools model (e.g. SQL/BizTalk developer and/or MSDN) must be installed on their own separate physical hardware.
You are not allowed to run test or development products on a server where production workloads are running at the same time. Kindly run your developer software on a device/host that is dedicated to testing and development.
Explanation:
The Product Use Rights (PUR) say that the developer software is not licensed for use in a production environment. Even if the PUR does not have a separate definition of production environment, a production environment is a set of resources for network, physically
dedicated hardware and software to provide "live" service. If the intent was to say that the same physical server could be used for both development and production - it would say "not licensed for use in a production OSE," instead
it says environment.
See current PUR, page 51:
Developer Tools (User License)
You have the rights below for each license you acquire.
# You must assign each license to a single user.
# Each Licensed User may run an unlimited number of copies of the Developer Tools software and any prior version on any device.
# The Licensed User may use the software for evaluation and to design, develop, test, and demonstrate your programs. These rights include the use of the software to simulate an end user environment to diagnose issues related to your programs.
# The software is not licensed for use in a production environment. # Additional rights provided in license terms included with the software are additive to these product use rights, provided that there is no conflict
with these product use rights, except for superseding use terms outlined below.
Question:
Classifying an entire physical infrastructure as "production" in these days of virtualisation and shared storage really does not make any sense at all. Not using the software for production purposes makes perfect sense, but not being able to locate
it alongside production OS installs is mad. Does this only apply to the server running the VM (CPU and RAM)? If the VHDX is hosted on shared SAN storage does the SAN have to be dedicated to non-production storage?
Answer:
We kindly inform that after double-checking the case we would like to confirm the development software cannot be run on the same hardware with production software.
We have also received a feedback from the responsible team regarding your request about a dedicated SAN (Storage Area Network) for MSDN software.
They have confirmed that the SAN has to be dedicated to the development and testing environment if it is used to run the software acquired through MSDN.
Question:
OK, so if I have my desktop (which is a production environment as I use it for email and other day to day office tasks), can I turn on Hyper-V and install an MSDN Windows Server 2012 instance for development purposes?
Answer:
We kindly inform it is not allowed to install and run software from MSDN subscriptions in production environments. Please do not install MSDN software on a desktop in a production environment:
"[.] The customer will need to run the developer software on a device/host that is dedicated to testing and development.
Explanation:
The Product Use Rights (PUR) say that the developer software is not licensed for use in a production environment. Even if the PUR does not have a separate definition of production environment, a production environment is a set of resources for network, physically
dedicated hardware and software to provide "live" service. If the intent was to say that the same physical server could be used for both development and production - it would say "not licensed for use in a production OSE," instead
it says environment.
See current PUR, page 51:
Developer Tools (User License)
You have the rights below for each license you acquire.
- You must assign each license to a single user.
- Each Licensed User may run an unlimited number of copies of the Developer Tools software and any prior version on any device.
- The Licensed User may use the software for evaluation and to design, develop, test, and demonstrate your programs. These rights include the use of the software to simulate an end user environment to diagnose issues related to your programs.
- The software is not licensed for use in a production environment.
- Additional rights provided in license terms included with the software are additive to these product use rights, provided that there is no conflict with these product use rights, except for superseding use terms outlined below.

Hi Mike,
It sucks that MSDN software can't be run in a production environment, that means you have to have two entirely separate hardware environments, which are costly, and it seems unnecessary.
That's essentially it. I'm not saying for one second that it should be used for production purposes, just that it's physical location shouldn't be relevant. Also, the word "environment" is a very bad choice in the documentation simply because it's very open
to interpretation.
A production environment is defined as an environment that is accessed by end users of an application (such as an Internet Web site) and that is used for more than
Acceptance Testing of that application
or Feedback. Some scenarios that constitute production
environments include:
Environments that connect to a production database.
Environments that support disaster-recovery or backup for a production environment.
Environments that are used for production at least some of the time, such a server that is rotated into production during peak periods of activity.
So I dont think (here's that inconclusive language) but am not sure that your desktop machines count as production environments, based on that, unless end users are connecting to them. (I dearly hope they are not!)
My reading is based on the "Other Guidance" section:
"If a physical machine running one or more virtual machines is used entirely for development and test, then the operating system used on the physical host system can be MSDN software. However, if the physical machine or any of the VMs
hosted on that physical system are used for other purposes, then both the operating system within the VM and the operating system for the physical host must be licensed separately."
<o:p>This is the crux of the matter and the interpretation of "licensed separately". A (to my mind) sensible reading of that would be "if you're running any production purpose VMs on a server then the physical host OS must be a full licence
[presuming it's Server 2012 and not, say, VMWare or Hyper-V 2012] as must all production purpose VMs on that server". This has been getting interpreted by others (I'm not the first) and backed up by MS as meaning that if you want to run any dev/test VMs on
a server that also runs production VMs then you can't use MSDN for those dev/test VMs.</o:p>
Also, there is a section
here, on the MSDN Licensing help page that says (with my added emphasis):
Many
MSDN subscribers use a computer for mixed use—both design, development, testing, and demonstration of your programs (the use allowed under the MSDN subscription license) and some other use. Using the software in any other way, such as for doing email,
playing games, or editing a document is another use and is not covered by the MSDN subscription license.
When this happens, the underlying operating system must also be licensed normally by purchasing a regular copy of Windows such as the one that came with a new OEM PC.
Now to me, it seems this might be saying that the underlying operating system on a work
machine cannot be licensed using MSDN if that work machine is going to be doing non-msdn things in addition to MSDN things. It doesn't say "This can't happen" it just says "When this happens, the underlying
OS must be licensed normally..."
So, based on what I'm reading it seems that this quote from you might not be true:
"We can't install a local MSDN instance of Server 2012 or 8.1 for dev and test under Hyper-V on desktops
because desktops used for email, writing documents, etc are production. "
I wouldn't have expected this to be true either, but this is the response I was given. It may well be
that my question was misunderstood. I hope this is the case otherwise one of the big reasons for turning on Hyper-V on expensive, powerful desktops enabling the running of personal test environments goes out the window!
Thanks for your time on this.

How to delete ABAP program of production environment

Dear Experts,
I have to delete a Z program, exists in production environment. But the program does not exist in development environment. Is this possible to delete the program using transport request? or other ways to delete the program in production environment.
Thanks in advance.
Tanay

Hi Tanay,
If you have access tcode SE80 in Production system, you can delete it.
Srivijay

What authorizations to give to developers in the production environment

Hi,
We have setup our development PI 7.1 environment and are now ready to setup production. Can someone point me in the right direction for determining which authorizations need to be given to the PI developers in the production environment?
Do they have to be the same or is there some other set of roles/authorizations for a production environment?
Any help is greatly appreciated.
Best Regards,
Rick

Hi Rick,
Precisely for configuration XI have separate role: SAP_XI_CONFIGURATOR which is used to configure interfaces in ID. But again this is role provided to very selective people (usually Application Support team) because you need to share some sensitive user/password etc for different systems (SAP/Non-SAP).
We used following roles combinations:
- Dev system
Developers = SAP_XI_DEVELOPER, SAP_XI_CONFIGURATOR, SAP_XI_MONITOR, SAP_XI_BPE* ,
TechLead = Developer + SAP_XI_ADMINISTRATOR
- QA System
Developer = SAP_XI_CONFIGURATOR, SAP_XI_MONITOR, SAP_XI_BPE_MONITOR
TechLead = Developer (in special cases SAP_XI_ADMINISTRATOR)
- PROD System
Developer = SAP_XI_MONITOR, SAP_XI_BPE_MONITOR, (None for Configuration If I have separate team for configuration).
TechLead = Developer + SAP_XI_CONFIGURATOR
It is best practise to keep separate team for configuration on Prod system because of sensitivity of information. Even on PROD system you need to modify SAP_XI_MONITOR role to disallow monitoring of payload because of data sensitivity (HR, Finance data etc).
Regards,
Gourav

Set a Hard Currency, after the company is in Production environment

Dear experts,
Please your help to solve the question: Does somebody knows what happen if I try to set a Hard Currency, through OB22 transaction, after the company is in production environment? Is it possible?
The production system only have one local currecy.
Thanks in advance.
Best Regards,
Aguinaldo Masetto

Hello Mauri,
First of all thank you for the prompt answer.
I tried to check the SAP Note 39919 as you suggested, but I faced an error message:
"The requested SAP Note is either in reworking or is released internally only".
Can you please post the texts of the SAP Note 39919 into this Question?
Thanks in advance,
Aguinaldo Masetto

Anyone using the Unified Inbox in a Production Environment yet?

Hi,
I am currently assessing the different SAP Workflow Inbox options, with the Unified Inbox being the first choice.
With it being so new, it still seems to be a bit of a "Work in progress" from SAP's side.
With the BSP application (/IWPGW/TGW_UNIF_INBOX) and Gateway service (/IWPGW/TASKPROCESSING version 2) still evolving in the latest Support Packs and the UI5 Inbox API still being expanded with each release.
Not to mention the fact that the Inbox API has a very clear warning "Experimental API:Since version 1.5.2. API is not yet finished and might change completely" in the API Reference Documentation.
Just wondering if there are any SAP customers out there who are using it in a Production Environment yet?
If so I would really love to get some feedback regarding the following points:
Performance
Stability
Functionality
Or any other feedback will be appreciated.
Thanks,
Brad

Thanks Jocelyn, looking forward to that webex session.
We waited patiently to upgrade to IW_PGW SP06 which contains all the improvements and latest functionality you are referring to. As it had a dependency on SAP_GWFND SP08 which was released only 2 months (Mid September) after. Where as it was available for Gateway add-on IWFND SP09 in July.
It really does contain massive improvements to the Unified Inbox with the extra features you're referring to. The /IWPGW/TASKPROCESSING version 2 Gateway service is way more complete now and the /IWPGW/TGW_UNIF_INBOX Unified Inbox BSP has been completely re-written using UI5 Components approach which has proven extremely useful in our case in order to enhance the Inbox by re-using the Unified Inbox component and not needing to modify anything SAP standard.
I'm really impressed with it so far! I'm a big fan!
Cheers,
Brad

Unable to import the Internet servivce into Production Environment

Hi,
We put the internet service and its HTML templates in a custom package for integrated ITSMobile. We got everything but the internet service ZXXX in the production. Has anyone come across this before? We were able to transport to the quality system. But it did not create the internet service in the production environment. Is it authorization issue? Your input will be highly appreciated.
Regards,
Subbu

Hi Subbu,
I suggest you to as your basis guys how are familiar with transports between systems. They will find out what the reason is. Without being able to look into transport protocols it is unlikeliy that someone here can advise you.
Regards,
Klaus

Use of Emigall for creation of masters in the production environment

Hi,
The EMIGALL objects are normally used for migrating legacy master data and/or cut-over data before production environment is up.
I am contemplating to use EMIGALL object for creation of contract account masters in production environment. One more option that I have is to use standard BAPI for creating contract account masters.
Can anyone tell me whether it is proper to use EMIGALL object for day to day creation of master day in production environment. Is there any disadvantage or risk involved in it.
Kindly reply soon.
Regards,
Ganesh

I've already used emigall multiple times to do delta migrations into an operational prod environment.
Purely looking at the functionalities, it should/would/must be possible to use emigall as a master data generator. I just think you need to look into the requirements:
who will use it? end-user/application manager/...
what's the amount of data to be loaded?
what's the time window of the load? Day/night
how is the data supplied?
As you know, emigall EATS system resources like mad, so using it during the day might not be preferable. emigall is also very picky about the file format, whereas in a custom report you can define the input structure yourself.
On the other hand, the error handling and follow-up of emigall is great...
Personally, I'd go for a custom report with a BAPI... It'll give you more flexibility than emigall.

Most of the time queries remain in suspended state in our production environment.

Most of the time queries remain in suspended state in our production environment.
Not getting any solution.
Thanks

Wait typeS : PAGEIOLATCH_SH,PAGELATCH_EX is when requested page is in buffer and some other process/request
is holding the lock in buffer.
SQL will manage it internally , Have you faced in performance issue if yes the need to check
1) Fragmentation of indexes. if fragmented the defrag it so that time of execution will less and will also reduce wait time.
2) Any missing indexes is there then create it
3) Update statistics status of tables.
4) Check if any table scan is there the create appropriate indexes on that...etc ....

Modify the transaction OAAR Production environment

Similar Messages

Maybe you are looking for