How the availability of a system is calculated?

Hello all,
Could you please let me know how the availability of a system is calculted? I have generated the EWA report for one of my production system and the report says that my systems availability is 40%. But my system wasn't down for the whole week. Could you please help me to understand how this calcuatiion is done? Any document existing for this?
Thanks and Regards,
Rajeev

Hello Rajeev,
Are you using CCMSPING for accurate for accurate reporting of
System Availability?
The "Avg. availibility per week" (as an example of how early watch
checks the system availability) is derived from the logs of the SAP
Performance Collector (report RSCOLL00).
If the logs are available for the whole day, it is assumed also that the system
(with at least one application instance) was available for the whole day.
So it may be that if the log were not available at some point in time or the sapcol didn't run on
occassion, despite the system being up 100% of the time, the avail-
ability will not report as >99%. And this will not generate an error.
The ST03 Collectors tries to aggregate certain checks on the server
and instance, and really isn't measuring system availability.
This is why SAP's recommendation is to use CCMSPING for accurate
reporting of system avaiolability. If you are not using CCMSPING,
please reference SAP note 1332677.
Regards,
Paul

Similar Messages

System Monitoring (Availability of satellite systems)

Hi!
I would like to set up System monitoring in SAP Solution Manager.
First of all the availibility of SAP systems is of great interest for me.
How can I create and add the monitoring context for the systems in tcode RZ20?
Is some suitable documentation for my question?
Thank you very much
Philip

Hi,
the relevant documentation can be found under item "Availability Monitoring with CCMSPING" at
<Monitoring Availability> [original link is broken]
Best Regards, Vital

Rule based monitors (RZ20) - Show system availability for selected systems

Hi experts,
I'm new with CCMS monitoring and need an advice for rule based monitors.
I want to create three alert monitors (RZ20). One for our developing systems, one for our quality assurance systems and one to monitor our production systems.
For the start, I want to show data in each of this monitor for free space of the filesytems (MTE class: "FilesystemFreeSpace"), for users which are locked out (MTE class "R3SyslogSecurity") and for the availabilty of the ABAP systems (MTE class "Availability_SysPercent_ABAP").
I started to create the monitor for our developing system and got a problem. I started with the rule "CCMS_DEFINE_R3_SYSTEMS" to select our developing systems "HRT", "CRT" and so on. Under this nodes, I defined the mte classes ("CCMS_GET_MTE_BY_CLASS") which needs to be shown: "FilesystemFreeSpace", "R3SyslogSecurity" and "Availability_SysPercent_ABAP".
When I checked the results, I was able to see the free space of the filesystems and whether a user has been locked out. Unfortunately, I recognized that the availability is not shown. Instead there is the message "No MTEs currently available".
I'm aware, the availability cannot be shown on this way, since the agents are part of the central monitoring system and hence i need to choose the central system for "CCMS_DEFINE_R3_SYSTEMS". However I'd like to show the availability separated for each system under "HRT", "CRT" and so on. That means for example, there should me a node "HRT", which contains the free space of the filesystems, whether users are locked out, and the availability for the system.
It's not a problem to get a solution with a static monitor. I simply create a virtual node "HRT" and tick the checkbox under "<central system>, ..., <availability>, <hrt> ..."
However, I'd like to use rule based monitor to keep the effort at a minimum by not ticking thousand of check-boxes when I expand the monitored objects.
I also tried to use the rule "CCMS_GET_AVAILABILITY_FOR_SYSTEM", but it doesn't work and SAP documentations say "This rule is reserved by SAP for later use".
Does anybody know a solution for my problem?
In addition, I've got one more question concerning rule based monitors: If I want to create a monitor for my developing systems, I'll not be able to choose "<all>" for "CCMS_DEFINE_R3_SYSTEMS". Do I need to create "CCMS_DEFINE_R3_SYSTEMS" for each system separately? Or is there another possible way?
Thanks for your help in advance.
Bob
Edited by: Bob Norwich on Oct 17, 2010 12:04 PM
I read something about logical MTE classes: http://help.sap.com/saphelp_nw04s/helpdata/en/31/5462405c910272e10000000a155106/frameset.htm --> Does I need to use this?

Sorry Sean for my very late anwser.
I was very busy in my company.
Yes, I had tried you suggestion but it didn't work for me.
The problem is, that the Agent "CCMSPING" is part of the central monitoring system by definition.
Furthermore I tried to copy the default availabiliy monitor to look how it is definied. It didn't help.
I made the decision to define my monitor differently (an extra monitor for the availability for all system) and replace this temporalily solution when ""CCMS_GET_AVAILABILITY_FOR_SYSTEM" will be available.
The situation is not so bad after all.
Thx for your help. I appreciate it!!
Bob

How the system calculated the last evaluated price

how the system calculated the last evaluated price in inventory

Hi!
Last Evaluated Price u2013 the price calculated in the last run of the Inventory Valuation report

How to handle the CRM Middleware after system refresh?

Guys,
We are using CRM 5.0 & R/3 4.6C. We have the middleware configured and set up. We finished all inital loads & delta loads are activated as well. The system works perfectly.
Now for some reason the client wants to refresh the R/3 system. (Basically they are copying over the R/3 Dev system to refresh the R/3 Sandbox system. Our connection is currently between the 2 sand box systems) What impact will this have on the CRM system? Will it cause mass delta downloads? I have already referred to notes 588701 & 765018. Any additional information or watch outs will be appreciated.
Secondly what's the best practice do a refresh in the future? Is there a SAP recomendation on how to go about with system refresh when CRM & R/3 are connected?
ARP

Hello ARP,
as always: It depends what to do:
a) do you have a CRM DEV System available? If possible you should get the connection working over there and then do a Landscape Copy of the R/3 DEV + CRM DEV to the Sandbox Landscape.
b) Let them copy the R/3 DEV to the R/3 Sandbox. Then use the Data Integrety Manager (Transaction SDIMA) to get the missing Customers, Transactions exchanged.
In the future they normally have to do a Landscape Copy.
Regards
Gregor

Is this roughly how the labVIEW Execution Systems work?

I've not taken a class in OS design, so I don't know the strategies used to implement multitasking, preemptive or cooperative. The description below is a rough guess.
LabVIEW compiles Vis to execute within its own multitasking execution environment. This execution environment is composed of 6 execution systems. Each execution system has 5 priority queues (say priorities 0->4). Vis are compiled to one or more tasks which are posted for execution in these queues.
An execution system may either have multiple threads assigned to execute tasks from each priority queue, or may have a single thread executing all tasks from all priority queues. The thread priorities associated with a multithreaded execution system are assigned according to the queue that they service. There are therefore 5 available thread priority levels, one for each of the 5 priority level queues.
In addition to the execution queues, there are additional queues that are associated with tasks suspended in various wait states. (I don't know whether there are also threads associated with these queues. It seems there is.)
According to app. note 114, the default execution environment provides 1 execution system with 1 thread having a priority level of 1, and 5 execution systems with 10 prioritized threads, 2 threads per priority queue. NI has titled the single threaded execution system "user interface" and also given names to the other 5. Here they will be called either "user interface" or "other".
The "user interface" system is responsible for all GUI actions. It monitors the keyboard and mouse, as well as drawing the controls. It is also used to execute non-thread-safe tasks; tasks whose shared objects are not thread mutex protected.
Vis are composed of a front panel and diagram. The front panel provides an interface between the vi diagram, the user, and the calling vi. The diagram provides programmatic data flow between various nodes and is compiled into one or more machine coded tasks. In addition to it own tasks, a diagram may also call other vis. A vi that calls another vi does not actually programmatically branch to that vi. Rather, in most cases the call to another vi posts the tasks associated with the subvi to the back of one of the labVIEW execution system�s queues.
If a vi is non-reentrant, its tasks cannot run simultaneously on multiple threads. This implies a mutex like construction around the vi call to insure only one execution system is executing the vi. It doesn�t really matter where or how this happens, but somehow labVIEW has to protect an asynchronous vi from simultaneous execution, somehow that has to be performed without blocking an execution queue, and somehow a mutex suspended vi has to be returned to the execution queue when the mutex is freed. I assume this to be a strictly labVIEW mutex and does not involve the OS. If a vi is reentrant, it can be posted/ran multiple times simultaneously. If a vi is a subroutine, its task (I think there is always only one) will be posted to the front of the caller's queue rather than at the back of the queue (It actually probably never gets posted but is simply mutex tested at the call.) A reentrant-subroutine vi may be directly linked to its caller since it has no restrictions. (Whether in fact labVIEW does this, I don�t know. In any event, it would seem in general vis that can be identified as reentrant should be specified as such to avoid the overhead of mutexing. This would include vis that wrap reentrant dll calls.)
The execution queue to which a vi's tasks are posted depends upon the vi execution settings and the caller's execution priority. If the caller's execution priority is less than or equal the callee's execution settings, then the callee's tasks are posted to the back of the callee's specified execution queue. If the caller's execution priority is greater than the callee's specifications, then the callee's tasks are posted to the back of the caller's queue. Under most conditions, the vi execution setting is set to "same as caller" in which case the callee�s tasks are always posted to the back of the caller's execution queue. This applies to cases where two vis are set to run either in the other execution systems or two vis are set to run in the user interface execution system. (It�s not clear what happens when one vi is in the �user interface� system and the other is not. If the rule is followed by thread priority, any background tasks in the �other� systems will be moved to the user interface system. Normal task in the �other� systems called by a vi in the �user interface� system will execute in their own systems and vice versa. And �user interface� vis will execute in the caller�s �other� system if the caller has a priority greater than normal.)
Additionally, certain nodes must execute in the "user interface" execution system because their operations are not thread-safe. While the above generally specifies where a task will begin and end execution, a non-thread safe node can move a task to the �user interface� system. The task will continue to execute there until some unspecified event moves it back to its original execution system. Note, other task associated to the vi will be unaffected and will continue to execute in the original system.
Normally, tasks associated with a diagram run in one of the �other� execution systems. The tasks associated with drawing the front panel and monitoring user input always execute in the user interface execution system. Changes made by a diagram to it own front panel are buffered (the diagram has its own copy of the data, the front panel has its own copy of the data, and there seems to be some kind of exchange buffer that is mutexed), and the front panel update is posted as a task to the user interface execution system. Front panel objects also have the advanced option of being updated sequentially; presumably this means the diagram task that modifies the front panel will be moved to the user interface execution system as well. What this does to the data exchanged configuration between the front panel and diagram is unclear as presumably both the front panel and diagram are executing in the same thread and the mutex and buffer would seem to be redundant. While the above is true for a control value it is not clear whether this is also true for the control properties. Since a referenced property node can only occur on the local diagram, it is not clear it forces the local diagram to execute in the user interface system or whether they too are buffered and mutexed with the front panel.
If I were to hazard a guess, I would say that only the control values are buffered and mutexed. The control properties belong exclusively to the front panel and any changes made to them require execution in the �user interface� system. If diagram merely reads them, it probably doesn�t suffer a context switch.
Other vis can also modify the data structure defining the control appearance and values remotely using un-reference property nodes. These nodes are required to run in the user interface system because the operation is not thread-safe and apparently the diagram-front-panel mutex is specifically between the user interface execution system and the local diagram thread. Relative to the local diagram, remote changes by other vis would appear to be user entries.
It is not clear how front panels work with reentrant vis. Apparently every instance gets its own copy of the front panel values. If all front panel data structures were unique to an instance, and if I could get a vi reference to an instance of a reentrant vi, I could open multiple front panels, each displaying its own unique data. It might be handy, sort of like opening multiple Word documents, but I don�t think that it�s available.
A note: It is said that the front panel data is not loaded unless the front panel is opened. Obviously the attributes required to draw an object are not required, nor the buffer that interfaces with the user. This rule doesn�t apply though that if property references are made to front panel objects, and/or local variables are used. In those cases at least part of the front panel data has to be present. Furthermore, since all data is available via a control reference, if used, the control�s entire data structure must be present.
I use the vi server but haven�t really explored it yet, nor vi reference nodes, but obviously they too make modifications to unique data structures and hence are not thread-safe. And in general, any node that accesses a shared object is required to run in the user interface thread to protect the data associated with the object. LabVIEW, does not generally create OS level thread mutexes to protect objects probably because it becomes to cumbersome... Only a guess...
Considering the extra overhead of dealing with preemptive threading, I�m wondering if my well-tuned single threaded application in LV4.1 won�t out perform my well-tuned multithreaded application in LV6.0, given a single processor environment�
Please modify those parts that require it.
Thanks�
Kind Regards,
Eric

Ben,
There are two types of memory which would be of concern. There is temporary and persistent. Generally, if a reentrant vi has persistent memory requirements, then it is being used specifically to retain those values at every instance. More generally, reentrant code requires no persistent memory. It is passed all the information it needs to perform its function, and nothing is retained. For this type of reentrant vi, memory concern to which you refer could become important if the vis are using several MBytes of temporary storage for intermediate results. In that case, as you could have several copies executing at once, your temporary storage requirements have multiplied by the number of simultaneous copies executing. Your max memory use is going to rise, and as labview allocates memory rather independently and freely, the memory use of making them reentrant might be a bit of a surprise.
On the other hand, the whole idea of preemtive threading is to give those tasks which require execution in a timely fashion the ability to do so regardless of what other tasks might be doing. We are, after all, suffering the computational overhead of multithreading to accomplish this. If memory requirements are going to defeat the original objective, then we really are traversing a circle.
Anyway, as Greg has advised, threads are supposed to be used judiciously. It isn't as though your going to have all 51 threads up at the same time. In general I think, overall coding stategy should be to minimize the number of threads while protecting those tasks that absolutely require timely execution.
In that sense, it would have been nice if NI had retained two single threaded systems, one for the GUI and one for the GUI interface diagrams. I've noticed that control drawing is somewhat slower under LV6.0 than LV4.1. I cannot, for example, make a spreadsheet scroll smoothly anymore, even using buffered graphics. This makes me wonder how many of my open front panel diagrams are actually running on the GUI thread.
And, I wonder if threads go to sleep when not in use, for example, on a wait, or wait multiple node. My high priority thread doesn't do a lot of work, but the work that it does is critical. I don't know what it's doing the rest of the time. From some of Greg's comments, my impression is it in some kind of idle mode: waking up and sleeping, waking up and sleeping,..., waking up, doing something and sleeping... etc. I suppose I should try to test this.
Anyway that's all an aside...
With regard to memory, your right, there are no free lunches... Thanks for reminding me. If I try this, I might be dismayed by the additional memory use, but I won't be shocked.
Kind Regards,
Eric

Need to understand how the PGI date is being calculated

Hi,
Need to understand how the PGI date is being calculated.
Does the PGI date get recalculated if the cusotme delivery date is changed.
Thanks,
Raki

Hi,
Thanks for the information and please let us know is there any calculation logic exist for that?
I have changed delivery date in the sales order and based on that-
- Transportation planning/material availability/loading/schedule line and confirmed quantity date was chaged.
Is this the - GI date - Transist time= PGI?
Thanks,

Let me know how to run high availability services in system 9 essbase.

Hi
Let me know how to run high availability services in system 9 essbase.
thanks in ADV
Message was edited by:
user624564
Message was edited by:
user624564

Hi,
Now i am using essbase system 9.2 version,
& URL : http://localhost:11080/eds/EssbaseEnterprise
plz guide me to download the High Availability servers .
thanks in Adv....

How the system picks BED,SED and CESS

Hi Gurus,
I want to know how the system picks the BED,SED and CESS while doing the J1IIN. Actuvally i maintained the condition records in VK11. But upto Billing document all the excise duties are coming right. But in J1IIN these values are not coming. Is there any place to mention the BED ,AED, SED other than VK11?
Reegards,
jyothi.

Hi Friend,
Please check all these settings and find out what are you missing,
IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of Excise Duty >
Condition-Based Excise Determination
When you enter a purchasing document, for example, a purchase order, the R/3 System automatically calculates the applicable excise duties using the condition technique.
Features : The standard system comes with two tax calculation procedures. TAXINN is only supports condition-based excise determination, whereas TAXINJ supports condition-based excise determination and formula-based excise determination. Both tax procedures contain condition types that cover all of the excise duties and sales taxes applicable.
Since the exact rates of excise duty can vary on a large number of factors, such as which vendor you purchase a material from, or which chapter ID the vendor stocks the material under, you create condition records for every sort of excise duty.
When you come to enter a purchasing document, the system applies the excise duty at the rates you have entered in the condition records.
Customizing : Make the settings in Customizing Basic -> India -> for Logistics General, by choosing Taxes on Goods Movements Account -> Excise Duties Using Condition Technique and -> Settings Determination.
These activities include one activity where you define a tax code for condition-based excise determination.
Master Data - Create condition records for all excise duties that apply, and enter the tax code for condition-based excise determination in each.
Day-to-Day Activities - When you enter a purchase order or other purchasing document, enter the tax code for condition-based excise determination in each line item. The system then calculates the excise duties using the condition records you have created.
When the ordered materials arrive, you post the goods receipt and the excise invoice. The system posts the excise duty to the appropriate accounts for deductible input taxes when you enter the excise invoice.
Creating Condition Records for Excise Duty
1. In the command field, enter FV11 and choose .
2. Enter the condition type that you want to create a condition record for and choose .
The Key Combination dialog box appears.
3. Select the combination of objects that you want to create the condition record for. On the dialog box, Control Code means "chapter ID." So, for example, to create a condition record for a tax that applies to a combination of country, plant, and chapter ID, select Country/Plant/Control Code.
4. Choose .
5. Enter data as required. - In the Tax Code field, enter the dummy tax code that you have defined.
6. Save the condition record.
Formula-Based Excise Determination - When you execute a business transaction involving materials that are subject to excise duty, the system automatically calculates the duty for you.
In order for the system to be able to determine which rate of excise duty to apply, you must have maintained all the data on the Excise Rate Maintenance screen, which you can Master Data®access from the SAP Easy Access screen by choosing Indirect Taxes Excise Rate Maintenance.
You maintain the following types of data:
- Plant master data
You assign each of your plants an excise duty indicator. You can use the same indicator for all the plants with the same excise status from a legal point of view, such as all those that are in an exempt zone. See also the information about manufacturers that are only entitled to deduct a certain portion of the duty (see Partial CENVAT Credit).
- Vendor master data
For each of your vendors with the same excise status from a legal perspective, you define an excise duty indicator. You must also specify the vendor type for example, whether the vendor is a manufacturer, a depot, or a first-stage dealer. You must also stipulate if the vendor qualifies as a small-scale industry. For each permutation of plant indicator and vendor indicator, you then create a final excise duty indicator.
- Customer master data
Similarly, you assign the same excise duty indicator to each of your customers that share the same legal excise status.
Again, for each permutation of plant indicator and customer indicator, you then create a final excise duty indicator.
- Material master data
Each material is assigned a chapter ID.
- Excise tax rate
For every chapter ID and final excise duty indicator, you maintain the rate of excise duty.
If your business only qualifies for partial CENVAT credit, you must customize your system accordingly.
Let us consider an example to illustrate how the system determines which rate of excise duty to apply to a material. Assume you are posting a sale of ball bearings to a customer. The system automatically determines the rate of excise duty as follows:
1. Looks up the customer master data to see what status you have assigned the customer.
Let's assume you've assigned the customer status 3.
2. Looks up the plant master data to see what status you have assigned the plant. Similarly, your plant has status 2.
3. The system looks up the table under Excise Indicator for Plant and Customer to see what the final excise duty indicator is for customer status 3 and plant status 2: It is 7.
4. The system determines the chapter ID of the ball bearing for the plant.
Lets assume the chapter ID at plant for the ball bearings is 1000.01.
5. Finally, the system looks up the table under Excise Tax Rate to see what rate of duty applies to chapter ID 1000.01 under
status 7.
Define Tax Code for Purchasing Documents - In this IMG activity, you define a tax code for the purposes of calculating excise duty when you enter purchasing documents. Only carry out this activity if you use condition-based excise
determination.
- Create a new tax code, and set the tax code type to V (input tax). Do not make any other settings for it.
- Assign Tax Code to Company Codes
In this IMG activity, assign the tax code for purchasing documents to the company codes where it will be used.
Only carry out this activity if you use condition-based excise determination.
Classify Condition Types - In this IMG activity, you specify which condition types you use for which sort of tax. Note that this only applies to condition types that you use with the new excise determination method. The system uses this information when you create a document from another one. For example, when you enter an incoming excise invoice from a
purchase order, or when you create an outgoing excise invoice from a sales order, the system determines the various excise duties in the excise invoice using the information that you have entered here. In addition, when you create a purchasing document, the system only uses the condition types that you enter here.
- For taxes on purchases, use the condition types contained in the tax procedure.
- For taxes on sales, use the condition types contained in the pricing procedures.
The standard system comes with sample settings for the tax calculation procedures and pricing procedures.
Use these settings as a basis for your own.
IMG > Logistics - General > Tax On Goods Movement > India > Account Determination
Define G/L Accounts for Taxes - In this IMG activity, you specify which G/L accounts you will use to record which taxes.
Requirements - You have set up G/L accounts for each of the processing keys listed below.
- Assign an account to each of the following posting keys. The accounts for VS1, VS2, and VS3 are used as clearing accounts during excise invoice verification.
- VS1 (basic excise duty)
- VS2 (additional excise duty)
- VS3 (special excise duty)
- VS5 (sales tax setoff)
- MWS (central sales tax)
- MW3 (local sales tax)
- ESA (service tax)
- ESE (service tax expense)

How to find the Version of CRM system

Hi All,
I have to install CRM system and I dont have any other information other than the EWA Report, Can any one let me know how to find the Version of CRM system and we dont have Java installed in it (Generally we check WEBCUIF but as we dont have Java I cannot see the Package). Can I go with the CRMUIF ?? .
I have Pasted the information of Support Package Maintenance, that is available in EWA Report.
BBPCRM
600
4
13
SAP BBPCRM Server
CRMUIF
600
4
17
SAPK-60004INCRMUIF
SAP CRM User Interface Framework
PI_BASIS
2005_1_700
16
26
SAP R/3 Basis Plug-In
SAP_ABA
700
16
29
SAP Application Basis
SAP_AP
700
13
29
SAP_BASIS
700
16
29
SAP Basis Component
SAP_BW
700
18
31
SAP Business Information Warehouse
ST-A/PI
01P_700
0
SAPKITAB7I
SAP Service Tools for Applications Plug-In
ST-PI
2008_1_700
6
8
SAP Solution Tools Plug-In
Please let me Know. Thanks in Advance.
Vijay

Hi,
Logically your Status bar should show that.
Login to gui. --> system -> Status
and then you should see the crm version in your Component version.
SAP CRM ABAP 6.0
You should go with
BBPCRM
600
Thanks
Rishi abrol

T430s Error in how the Power Manager icon displays in system tray at bottom of screen

The icon for the Power Manager in the Windows system tray in the bottom right area of the screen is cut off. It's basically displaying itself too low on the system bar. Please see picture attached:
Does anyone know how to fix this? I've tried updating to the latest version of Power Manager (v 6.40) but that didn't help. I'm running Windows 7 Professional 64-bit.
Thanks.

Hi, wesaturn
Have you tried updating all other driver updates available for your system, such as the BIOS and video drivers? They can all be found here if not.
Also, how long has this been occurring? And has it ever displayed properly?
Best,
Adam
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution!" This will help the rest of the community with similar issues identify the verified solution and benefit from it.

How the systems pick pricing procedure in PO?

Hi Masters
      I have deleted the pricing procedure assignment thro schema group in the configuration.But the system picks the pricing procedure RM0000.How?
Regards
Mohan

Hi
Thank you for your replies
I have maintained blank entries of shema group for the purchasing organisation and vendor.And I have also deleted entries for assignment of blank entries to a pricing procedure in the following path
Materials Management->Purchasing->Conditions->Define Price Determination Process->Define Schema Determination->Determine Calculation Schema for Standard Purchase Orders
ie., Schema grpPorg      Schema Grp          Procedure
        Blank                       Blank                       XXXXXX -
deleted this entry
         01                           Blank                       AAAAA
My question is how the systems picks pricing procedure in PO although the assignment is deleted?
-Mohan

Software used to decode the media not available on this system

"The software that's used to decode the media is not available on this system…" I get this error message when I try to import an H.264 video file (about 3.7 GB in size) into Encore CS6 to make a Blu-Ray. I've read the message threads about this problem but they don't seem to apply to my case. I'm using a recent Mac Pro Tower running OS 10.8.5. I made the H.264 file using Compressor 4 and a Matrox MX02 box using the Matrox encode setting for high-quality Blu-Ray. I've used this workflow a number of times before and never had any trouble importing the resulting files into Encore. I've tried starting a new Encore project and also re-doing the encoding of the H.264 file, without success. I've also experimented with importing other, recently made H.264 files into a new Encore project and these, as before, present no problems. I'm baffled!

I solved the problem and thought it might be helpful if I described the solution. The error message gave no indication of the nature of the problem, which was caused by a single clip in the Avid Media Composer timeline. This clip was an import from Photoshop, resized in Avid Media Composer. In height, the pixel dimensions of the Photoshop file were a bit more than 1080. I have no idea how this dimension survived rendering in Media Composer or H.264 encoding in Compressor using the Matrox MX02 box. But it evidently did. When I resized the image in Photoshop before importing it into Media Composer, then re-encoded the video as H.264, it imported normally as an asset into Encore.

The software that used to decode the media is not available on this system

I can see that this has been asked numerous times over the years. I am sorry to post this AGAIN, but I have not yet found a solution and have a deadline looming.
We created a 200+ DVD's using Encore CS6 on a Windows 7 system.
We upgraded to Windows 8. Re-installed CS6 Production Premium.
Now, when we try to open the projects to make a few edits, we get the "The software that's used to decode the media is not available on this system. Installing the correct decoders for the files you are working with may help to correct the problem."
I've done the Encore Updates. I've done the Media Encoder updates. I've "Run as Administrator".
I've tried re installing.
Does anyone have any suggestions on how to debug this? The videos are already transcoded as *.m2v files.
You'd think this would be easy... like install a codec or something.
==> Mike.

Part of the problem is that this is probably not a "logical" error. The common cause of this issue is still image files where the pixel size is too large. This suggests that Encore's (and other Adobe apps) ability to handle image size is exceeded without a better error message. The link, which I'm going to post until I find a "new" location (if one exists) is now a bad link:
http://helpx.adobe.com/encore/kb/error-software-used-decode-media.html
And in this example where it was not an image issue, the user fixed the problem by re-encoding the problem file.
http://forums.adobe.com/message/6004428#6004428

How the system determines the Requirement type for one sales order

Hi,
SAP-SD Gurus,
Please tell me how the system determines the Requirement type for one sales order?
Thanks & Regards,
Sreenivas.P

Hi,
System follows some search criterial to determine the requirement type
1. First, an attempt is made to find a requirements type using the strategy group in the material master.
2. If the strategy group has not been maintained, the system will determine it using the MRP group.
3. If the MRP group has not been defined, the system uses the material type instead of the MRP group when accessing the corresponding control tables.
4. If no requirements type is found here, the system assumes a special rule and attempts to find a requirements type with the aid of the item category and the MRP type.
5. If this is not possible, a last attempt is made to find a requirements type with the item category only.
6. If the last attempt fails, the system declares the transaction as not relevant for the availability check or transfer of requirements.
Please check the path
SPRO->SALES & DISTRIBUTIONS->BASIC FUNCTIONS>AVAILABILITY CHECK AND TOR->TRANSFER OF REQUIREMENTS--->DETERMINATION OF REQUIREMENT TYPE USING TRANSACTION.
Hope it will clarify
regards,
santosh

How the availability of a system is calculated?

Similar Messages

Maybe you are looking for