Newspaper VS internet

The newspapers started around the 1600’s. Back then the newspaper was a very essential source to the humans. It was the source where we got all of the latest information from. Every family would buy one and read it to know what’s going on around the world. Newspapers made a lot more money back then. Now a days the internet is an extreme popular source that is being used to get information from. Around 1994 the public interest for internet grew and by 1996 internet was frequently used by the humans.

As we all might known the internet is very beneficial. Internet always had the most recent news on their site. Today most of the families have an computer with internet connection in their house and prefer reading the latest news on their computers screens. The reasons for this is because is cheaper, quicker and internet posts the current news. Some people might want to read only an specific section as choose to read it from the internet because its quicker and current, they can just type the specific title their looking for in the search engine. Internet is making the print media ( newspaper) disappear slowly. Many newspaper subscriptions are disappearing. Because the internet is free it has a immense affect on the sales of the newspapers. Online newspapers are also becoming a trend now since it’s been proven that more people spend their time searing for their information on internet instead of the newspaper.

Bonjour,

Face à la crise et au manque de liquidité préoccupant des entreprises, des galeries et des web galleries se sont lancés dans Le leasing (possibilité de louer une oeuvre d’art avec option d’achat). Bonne idée ou palliatif à une situation de plus en plus compliquée pour le marché de l’art. D’autant qu’il justifie cette initiative, par la complexité de la mise en place du mécénat (ce qui n’est pas faux). Mais pour autant, rien ne les oblige à solliciter les avantages fiscaux…
N’est-ce pas un peu léger ?
Est-ce une vraie volonté d’adaptation à un carcan juridique et fiscale contraignant, où l’annonce d’une volonté sous-jacente de remise en cause des avantages fiscaux du mécénat.

A suivre…

Voici l’article de la tribune.

http://www.latribune.fr/patrimoine/20090824trib000413442/oeuvre-d-art-le-bon-plan-du-leasing.html?title=Oeuvre%20d’art%20:%20le%20bon%20plan%20du

N’hésitez pas à participer et à donner votre avis.

Nicolas Dehorter

Following query gives the scheduling details of all concurrent requests in an EBS instance.

* Please make sure the pipe symbols for indentation are set (formatting changes when copied through editors)

SELECT cr.request_id,
DECODE (cp.user_concurrent_program_name, ‘Report Set’, ‘Report Set:’|| cr.description, cp.user_concurrent_program_name )  NAME,
argument_text, cr.resubmit_interval,
NVL2 (cr.resubmit_interval, ‘PERIODICALLY’,
NVL2 (cr.release_class_id, ‘ON SPECIFIC DAYS’, ‘ONCE’) ) schedule_type,
DECODE (NVL2 (cr.resubmit_interval, ‘PERIODICALLY’,
NVL2 (cr.release_class_id, ‘ON SPECIFIC DAYS’, ‘ONCE’) ),
‘PERIODICALLY’, ‘EVERY ‘ || cr.resubmit_interval || ‘ ‘ || cr.resubmit_interval_unit_code || ‘ FROM ‘ || cr.resubmit_interval_type_code || ‘ OF PREV RUN’,
‘ONCE’, ‘AT :’ ||TO_CHAR (cr.requested_start_date, ‘DD-MON-RR HH24:MI’),
‘EVERY: ‘ ||fcr.class_info ) schedule, fu.user_name, requested_start_date
FROM apps.fnd_concurrent_programs_tl cp, apps.fnd_concurrent_requests cr, apps.fnd_user fu, apps.fnd_conc_release_classes fcr
WHERE cp.application_id = cr.program_application_id
AND cp.concurrent_program_id = cr.concurrent_program_id
AND cr.requested_by = fu.user_id
AND cr.phase_code = ‘P’
AND cr.requested_start_date > SYSDATE
AND cp.LANGUAGE = ‘US’
AND fcr.release_class_id(+) = cr.release_class_id
AND fcr.application_id(+) = cr.release_class_app_id;

En ocaciones hay que borrar programas concurrentes por lo regular los de pruebas..
este es el api

declare
cursor init_values Is
select
   us.user_id
  ,rg.responsibility_id resp_id
  ,rg.responsibility_application_id resp_appl_id
  ,rg.security_group_id
 from fnd_user  us
    , fnd_user_resp_groups rg
where us.user_id = rg.user_id
  and us.user_name = '&user_name'
  and rownum < 2 ;
----------------------------------
cursor program_val is
select fcp.concurrent_program_name  program_name
     , fa.application_short_name    prog_app_name
     , fe.executable_name           exec_name
     , fa2.application_short_name   exec_app_name
   from fnd_concurrent_programs fcp
      , fnd_application         fa
      , fnd_application         fa2
      , fnd_executables         fe
where fcp.application_id = fa.application_id
  and fcp.executable_id  = fe.executable_id
  and fe.application_id = fa2.application_id
  and fcp.concurrent_program_name ='&program_shortname';
-------------------------------------------------
cursor rg_group_val is
select
  rg.request_group_name          request_group
, fa.application_short_name      req_app_name
, fcp.concurrent_program_name    program_name
, fa2.application_short_name     prog_app_name
from fnd_request_group_units     rgu
   , fnd_request_groups          rg
   , fnd_application             fa
   , , fnd_application           fa2
   , fnd_concurrent_programs     fcp
where fa.application_id   = rg.application_id
and  rgu.request_group_id = rg.request_group_id
and rgu.request_unit_id = fcp.concurrent_program_id
and fcp.application_id  = fa2.application_id
and fcp.concurrent_program_name ='&&program_shortname' ;
-------------------------------------------------
l_init             init_values%rowtype ;
l_program          program_val%rowtype ;
invalid_user       exception ;
BEGIN
  open init_values ;
 fetch init_values into l_init_val ;
 close init_values ;
 --------------------------
  open program_val ;
 fetch program_val into l_program ;
 close program_val ;
 if l_init.user_id is not null then

   if init_values%isopen then
     close init_values ;
   end if;
   if l_program.program_name is null then
      raise invalid_program ;
   End if;
   ----inicializar valores
   FND_GLOBAL.apps_initialize( l_init.user_id, l_init.resp_id, l_init.resp_appl_id, l_init.security_group_id, -1);
   FND_PROGRAM.set_session_mode( 'customer_data') ;
   for r in  rg_group_val
   loop
      dbms_output.put_line(' remover del group '||r.request_group);
      fnd_program.remove_from_group( r.program_name,r.prog_app_name, r.request_group, r.req_app_name );
   end loop ;
   dbms_output.put_line(' borrar programa: '||l_program.program_name);
   fnd_program.delete_program( l_program.program_name, l_program.prog_app_name );
   dbms_output.put_line(' borrar executable: '||l_program.exec_name);
   fnd_program.delete_executable( l_program.exec_name, l_program.exec_app_name );
   commit;
   dbms_output.put_line(' programa borrado exitosamente!!');
 else
    raise invalid_user ;
 end if;
exception
when invalid_program then
   dbms_output.put_line(' invalid program name '||'&&program_shortname');
   if program_val%isopen then
      close program_val ;
   end if;
when invalid_user then
   dbms_output.put_line(' invalid user name '||'&&user_name');
   if init_val%isopen then
      close init_val ;
   end if;
end ;

It could be because of the maximum number of IMAP connections by IP.  Have them modify this file in imapd.conf:

##NAME: MAXPERIP:0
#Maximum number of connections to accept from the same IP address

MAXPERIP=20

This should get you 5 IMAP accounts.

Tout le monde le sait dans la création, le nerf de la guerre est le capital de démarrage

“La société de gestion de fonds d’investissement XAnge Private Equity annonce avoir investi 750 000 euros dans le site KissKissBankBank.com.”

Bravo pour ce site Internet, mais je doute qu’ils auront les mains totalement libre et qu’ils s’inscrivent dans une dimension éthique et souhaitent apporter une vraie solution aux problèmes de financement des artistes dans la musique.

5 parties : Fournisseur, Consommateur, Concurrent, Partenaire et Soi-même.

Fournisseur :

- Les prestataires de services de paiement (PSP) ont un business model qui fonctionne par les commissions (partie fixe et variable) sur les transactions de leur clients (environ 2%). Pour que leur profit augmente, ils veulent augmenter leur volume de transactions et à ce que les clients envoient de plus grosse somme.

- Leur principaux partenaires sont les marchands et les plateforme de trading qui leur permet d’accroitre leur volume de transactions et les montants via les utilisateurs qui les utilisent. Ceci se fait par l’augmentation de leur nombre de clients qui est proportionnel à l’accès de leur système d’informations : l’API (Application Programming Interface) qui permet à quiconque d’automatiser les paiements.

- Leur fournisseurs sont une ou plusieurs banques. Les messages financiers sont géré électroniquement par la banque. Le PSP reçoit des confirmations via une API.

Consommateur :

- Les utilisateurs de l’internet veulent répondre à leur besoins. Les besoins de l’humanité sont récurrent (doivent être satisfait tout les jours). Ce besoin est soit un produit ou service, soit de l’argent. Les produits se trouvent chez les marchants en ligne (e-commerce). L’argent facilement gagné se trouve sur les plateforme de trading.

- Pour envoyer de l’argent, l’utilisateur à besoin d’un PSP. Et son PSP lui demande d’avoir un compte bancaire pour remplir son portefeuille électronique. Comparativement au PSP, l’internaute gagne plus par transaction si le profit est à sa valeur par défaut (maximum).

Concurrent, Partenaire et Soi-même :

- Le business model de la plateforme de trading est soit le même que celui du PSP (commissions par transactions), soit des frais d’entrée, soit des frais mensuels, soit des primes de parrainages (lien avec id) ou soit gratuit. (L’argent est gagné de la même manière que les utilisateurs.)

- Les fournisseurs des plateformes de trading sont les PSP avec leur API. (le logo est mis en évidence)

- Les utilisateurs consomment un service qui leur permet de déplacer de l’argent. La stratégie de déplacement de l’argent est définie soit par la plateforme de trading soit par les utilisateurs euxmême. (dépend de la politique interne de la plateforme de trading)

- La plateforme de trading est une couche logiciel au dessus du PSP. La conception et l’évolution de ce produit informatique peut être en partie externalisé auprès d’une ou plusieurs personnes qui s’occupe d’un logiciel libre de plateforme de trading ce qui permettrait de réduire les coûts et le temps de développement.

Waarom service zo belangrijk is.

- Boordevol oefeningen, vragen en opdrachten
- Voor bedrijven die nóg betere service willen verlenen

Service en klantgerichtheid
Met uitmuntende service bereiken we meer dan alleen concurrentievoordeel: het is dé manier om als bedrijf succes te hebben en te overleven. In een tijd waarin klanten steeds meer gaan eisen en sneller naar de concurrent stappen, moeten bedrijven heel bewust omgaan met hun klanten: wat willen ze? Wat hebben we hun te bieden? Hoe houden we hen vast? Het overtreffen van de verwachtingen van de klant is daarbij van levensbelang

Lees hier meer over Kruid in de huid van de klant

Waarom service zo belangrijk is.

- Boordevol oefeningen, vragen en opdrachten
- Voor bedrijven die nóg betere service willen verlenen

Service en klantgerichtheid
Met uitmuntende service bereiken we meer dan alleen concurrentievoordeel: het is dé manier om als bedrijf succes te hebben en te overleven. In een tijd waarin klanten steeds meer gaan eisen en sneller naar de concurrent stappen, moeten bedrijven heel bewust omgaan met hun klanten: wat willen ze? Wat hebben we hun te bieden? Hoe houden we hen vast? Het overtreffen van de verwachtingen van de klant is daarbij van levensbelang.

Lees hier meer over dit boek

Vkontakte, le premier réseau social russe serait sur le point de se lancer dans une douzaine de pays, selon le journal russe “Vedomosti”.

 Vkontakte, qui dispose déjà de plus de 34 millions d’inscrits, chercherait ainsi à concurrencer l’américain Facebook (lire le dossier Ces réseaux sociaux qui résistent à Facebook, du 29/05/2009), dont il est une quasi-copie conforme. Le réseau social russe est justement financé par Digital Sky Technologies (DST), le fonds d’investissement de Youri Milner qui a dépensé 100 millions de dollars pour entrer dans le capital du réseau américain

At least two trends are making paralell and distributed programming come to focus: computers with multiple cores getting cheaper and getting more cores, and websites leveraging terabytes worth of of user content. There are several services, tools and programming models around to help people cope with such trends, such as Amazon EC2, Hadoop, Fork Join, Actor Models, Non relational Databases, and so on. A couple of things to bear in mind when using multiple cores or multiple computers (with or without these tools):

• Amdahl’s law: It states that, with a fixed problem size, there is a point for every program after which adding more computational units do not give you improved performance. By computational units, you can take either cores (for paralell programming) or hosts (for distributed programming). Gustafson’s law tackles the issue when you do not fix the problem size, but this does not really help when you need faster response for your current problem size.
• Brewer’s CAP Theorem: This has to do with distributed programming only, and many people said a lot of about this. But essentially it means that a distributed system can only have at most two out of the three following properties: consistency, availability and partition tolerance (a kind of fault tolerance).

Amdahl’s law is quite troublesome: you cannot really do anything about it, but changing the algorithms involved. But CAP Theorem allows you to trade off one property for another. You can relax consistency into eventual consistency, you can relax on fault tolerance against partition tolerance, or you may live with less nines of up-time. It all depends on your application’s profile which one you will have to abandon. Dealing with this means no longer looking for ACID (Atomicity, Consistency, Isolation, Durability) systems, where consistency is very important, but looking for BASE (Basic available, soft-state or scalable, and eventually consistent) systems. It means listening to Gregor Hohpe’s suggestion and accepting that Two Phase Commit may not be the right way to go in detriment to pursuing the new ACID properties (Associative, Commutative, Idempotent and Distributed).

Not every system requires looking into these trends and thinking about such limitations and trade-offs. But if yours does, then keeping these in mind might come in handy.

After a few days playing around with the functional language Erlang, I was struck by how easy it is to create parallel processes in the language. One case where this is useful is, given a list of data items and a function to process them, a process is spawned to handle each item in parallel (when executing on a multiprocessor machine). This is made easy not only by Erlang’s excellent built-in primitives for parallel programming but also the support for high-order functions – enabling you to pass in an arbitrary function as an argument to the map function.

-module(pfuncs).
-export([map/2]).

map(F, L) ->
	Parent = self(),
	[ receive {Pid, Result} ->
		Result
	  end ||
	  Pid <- [spawn(fun() -> Parent ! {self(), F(X)} end) &#124;&#124; X <- L]].

In Java, however, you can’t just pass a reference to a function. The function needs to be wrapped in an object that implements it (I believe this is called a strategy). For example:

public interface Function<I, R>
{
	public R apply(I item) throws Exception;
}

This is a generic interface where the input is some type I and the output is R. This interface can now be used to define many different functions generically and in a type safe manner. For example, you would like to download a list of images in parallel (for example, when implementing a browser):

Function<URI, BufferedImage> getImage = new Function<URI, BufferedImage>()
{
	@Override
	public BufferedImage apply(URI uri) throws Exception
	{
		return ImageIO.read(uri.toURL());
	}
};

So what does the code look like that will processes the above function as a set of parallel tasks?

public void testPMap() throws Exception
{
	Function<URI, BufferedImage> getImage = new Function<URI, 	BufferedImage>()
	 {
		@Override
		public BufferedImage apply(URI uri) throws Exception
		{
			return ImageIO.read(uri.toURL());
		}
	};

	Set<URI > input = new HashSet<URI>();

	// Add image urls
	input.add(URI.create("http://www.example.com/image1.jpg"));
	input.add(URI.create("http://www.example.com/image2.jpg"));
	input.add(URI.create("http://www.example.com/image3.jpg"));
	input.add(URI.create("http://www.example.com/image4.jpg"));

	List<BufferedImage> output = new ArrayList<BufferedImage>(input.size());

	ExecutorService e = Executors.newFixedThreadPool(Runtime.getRuntime().availableProcessors());

	try
	{
		PMap.map(getImage, input, output, e);
	}
	finally
	{
		e.shutdown();
	}

	// do something with output
}

And just in case you’re wondering, the PMap.map function looks like this:

import java.util.Collection;
import java.util.concurrent.Callable;
import java.util.concurrent.CompletionService;
import java.util.concurrent.ExecutionException;
import java.util.concurrent.Executor;
import java.util.concurrent.ExecutorCompletionService;

public class PMap
{
	public static <I, R> void map(final Function<I, R> func, Iterable<I> input, Collection<R> output, Executor executor) throws InterruptedException, ExecutionException
	{
		CompletionService<R> ecs = new ExecutorCompletionService<R>(executor);

		int count = 0;
		for (final I i : input)
		{
			Callable<R> callableFunc = new Callable<R>()
			{
				@Override
				public R call() throws Exception
				{
					return func.apply(i);
				}
			};
			ecs.submit(callableFunc);
			count++;
		}

		for (int i = 0; i < count; ++i)
		{
			output.add(ecs.take().get());
		}
	}
	private PMap() {}
}

By the way, the above code does not handle failures elegantly. One approach would be to have an type that specifies how a failure in one of the sub-tasks should be handled (i.e. fail all tasks, or continue and return null for that individual task).

Disclaimer: This is just a programming exercise for me so I cannot guarantee that the above code is production-ready or free of bugs etc.

I think this information is very usefull, if you haven’t know yet, whats the difference the oracle APPS multi org handling in technical terms between R11(which has not changed since R10) and new architecture in R12

When I first time get in touch with R12,  I wondered why I can’t practice some R11 routines in multi org environment  (I mean it shown  no error but just not worked as I expected) such as :

FND_GLOBAL.APPS_INITIALIZE –> usually we call this procedure this when we want to initialize before submitting concurrent request from PL/SQL

DBMS_APPLICATION_INFO.SET_CLIENT_INFO –> usually we call this procedure when we work in multi org environment for querying various views

For your preview,  some changes and addition in R12 such as :

1.Default Operating Unit

The user can define a default operating unit. A new profile option, MO: Default Operating Unit, is available to define the defaulting operating unit, which can be set at the Responsibility and User levels. The default operating unit is visible in the Operating Unit field when the form is opened.The user, however, must have access to the default operating unit in his security profile definition. The user can overwrite the default value with another operating unit which the user can access. If the user updates the operating unit, all operating unit sensitive data should be cleared. Alternatively, the entire record can be cleared which is more cost effective in development.

If a user can access only one operating unit, then the operating unit defaults in the operating unit field. This eliminates the task of explicitly defining the default operating unit when the user accesses only a single operating unit.

2.Guidelines for Oracle Applications (OA) Framework Pages Based Applications

The Operating unit field is visible on OA Framework or JTT based user interfaces, similar to the Oracle Forms user interface.

Operating Unit Field in OA Pages

• The Operating Unit field is available as the first field in the page. If the operating unit is the control field for a particular page, for example create or search page, selecting the operating unit form the Operating Unit field list of values displays the same or different fields and restricts the valid list of values in other related fields.
• Fields that depend on the operating unit, are visible after selecting the operating unit or if the profile option defaults the operating unit.
• The user cannot update the operating unit value once the user saves the record. In OA Framework pages, if the user saves the transaction using the feature “Save for Later”, then the user can still update the operating unit.
• Changing the operating unit before saving a record clears the operating unit specific fields. Alternately, the user can also clear the record instead of clearing the organization specific fields.

3.Concurrent Programs/Reporting

Single Org Reports

A new field “Operating Unit Mode” is added in the Define Concurrent Programs in the OA Framework pages. The user can query the program or report based on an operating unit by updating the “Operating Unit Mode” field with one of the following values:

• Single
• Multiple
• Empty

The default value is Empty.

The multiple organizations context is automatically initialized by the concurrent program if the “Operating Unit Mode” is set to either single or multiple. The user can also select a value from the operating unit field’s list of values when the mode is single. The value of the “Operating Unit Mode” must be Single for a majority of the existing operating unit context sensitive reports.

There is no need to change the code for single org reports.

4.Access Control Architecture

Background

Multiple organizations architecture (Multi-Org) was introduced in Release 10.6 to secure the data by operating unit. In Release 10.7, Oracle added a column ORG_ID to each base table to partition the data by operating units. The partitioned tables are renamed with the suffix, ‘_ALL’, and their corresponding secured views are created in Applications (APPS) schema. The following diagram shows a single organization view in the APPS schema.

Multiple organizations views restrict access by filtering records for an operating unit assigned to the application responsibility set for the “MO: Operating Unit” profile option. This profile option value is cached in application context, and is initialized when calling the FND initialization routine. The FND CLIENT_INFO predicate includes all multiple organizations views and SQL statements that require multiple organizations security. The FND_CLIENT_INFO function retrieves the ORG_ID value stored in the application context. This value is valid for a session, unless explicitly changed by the calling procedure.

Use the _ALL table in the SQL statement to retrieve information irrespective of the operating unit. To increase the flexibility and performance in a multiple organizations environment and provide the same level of data security, the DBMS Virtual Private Database (VPD) feature replaces the CLIENT_INFO function.

Virtual Private Database (VPD)

The Virtual Private Database (VPD) feature allows developers to enforce security by attaching a security policy to database objects such as tables, views and synonyms. It attaches a predicate function to every SQL statement to the objects by applying security policies. When a user directly or indirectly accesses the secure objects, the database rewrites the user’s SQL statement to include conditions set by security policy that are visible to the user.

Database Schema – Access to multiple operating units

You can rewrite reference views that join data from multiple single organization views with the security policy attached to one secured synonym and the remaining reference to _ALL tables instead of single organization views. This improves performance because the policy is used once for the reference views that join data from multiple single organization views.

Multiple Organizations Security Policy Predicate

Synonyms replace single organization views that contain the CLIENT_INFO predicate attached to them. When installing, you must attach a security policy function to the multiple organizations synonyms. This indicates that the security is in place irrespective of the tools used to access the data.

The security policy function returns different predicate based on the number of accessible operating units. An application context attribute “ACCESS_MODE” is set based on the accessible operating units. Context sensitive security policy is used for multiple organizations access control to minimize the coding impact. The multiple organizations code in previous releases works in the context of only one operating unit. It was not anticipated that multiple organizations access would be supported. A solution to code impact is to change the policy predicate whenever needed. For example, when you open a form using a responsibility that can access multiple operating units and when you select an operating unit, the operating unit context is established and you do not need to modify the code that is used for validation from that point onwards, if the synonyms return data for the selected operating unit.

If the access mode is M (Multiple), then the policy predicate issues an EXISTS sub-query to a global temporary table. The global temporary table is a new feature in Oracle 8i. The table stores and manipulates data specific to a SESSION or TRANSACTION. If the access_mode is S (Single), then a simple equality predicate is used for performance reasons, since it is cost effective in comparison to the temporary table. An access mode A (All) is incorporated to bypass the security for functionality that needs full table access. If the access mode is not set or is NULL, then a simple predicate that uses the CLIENT_INFO value for ORG_ID is used for the policy predicate to support backward compatibility.

check MO_GLOBAL.Org_Security function

• Access control is not enabled for older releases of the applications, it is not backward compatible: You cannot enable the multiple organizations access control feature for all products simultaneously because multiple organizations views are shared between products at different levels. For example, if you choose to upgrade Payables but choose to keep an earlier version of Purchasing then Payables is access control enabled, but Purchasing is not. Therefore, Purchasing must replace the views it shares with Payables, such as PO_VENDOR_SITES, and PO_HEADERS, with secured synonyms. The secured synonyms must work as before for Purchasing, since you have not upgraded Purchasing and Purchasing still relies on CLIENT_INFO.

The simple predicate using current_org_id is used for the following cases:

• Access control is limited to only one operating unit: In this case, the access mode is ‘S’. An example is when a user can access to only one operating unit through the MO: Security Profile or the MO: Security Profile is not set and the user access depends on MO: Operating Unit.
• Access control is enabled with access to multiple operating units: The security profile provides access to multiple operating units, but in the scope of a transaction since the operating unit is controlled, a simple predicate eliminates additional changes to the server and client side code.

The complex predicate is used for these cases:

• Access is enabled and the security profile gives access to multiple Operating Units. The access mode is set to ‘M’ for this case.

For example, any statement on RA_CUSTOMER_TRX (synonym to which the security policy is attached) is dynamically modified to use the policy predicate.

A simple query by the user:

SELECT trx_number from ra_customer_trx

is modified at runtime if the responsibility can access multiple operating units to:

SELECT trx_number from ra_customer_trx
WHERE (EXISTS (SELECT 1
                 FROM mo_glob_org_access_tmp oa
                 WHERE oa.organization_id = org_id))

or is modified at runtime if the user’s access responsibility can access one Operating Unit with access control enabled for the module to:

SELECT trx_number from ra_customer_trx
 ORG_ID = sys_context('multi_org2','current_org_id')

Multiple Organizations Initialization

The profile options MO: Security Profile or MO: Operating Unit populate the multiple organizations global temporary table. The profile option MO: Security Profile takes precedence over MO: Operating Unit. You can combine the following under one application menu:

• Products at different levels
• Products that are access control enabled
• Products that are not access control enabled (i.e. in transition)

In such cases, initializing the multiple organizations depends on the application of the calling module and not the application tied to the responsibility, since the profile Option MO: Security Profile must be ignored for products that are not access control enabled or are in the transition phase.

A new table (FND_MO_PRODUCT_INIT) is introduced which contains a value Y for products that are enabled with the multiple organizations access control feature. The multiple organizations initialization API uses the module owner to initialize the temporary table depending on the value for the product in the FND_MO_PRODUCT_INIT table.

Legend: Y indicates multiple organizations access control is enabled, N indicates otherwise.

Use the shared services API to register products that are enabled with access control. For example to enable or remove access control for Payables (SQLAP), enter the following code:

To enable access:
FND_MO_PRODUCT_INIT_PKG.register_application('SQLAP',
'SEED','Y');
To delete your application entry:
FND_MO_PRODUCT_INIT_PKG.remove_application('SQLAP');

The Payables system administrator must then seed a row in the Multiple Organizations table to indicate that Payables is enabled with access control.

check metalink doc.id 420787.1

It has been a while since Java was the sole language running over a JVM. Scala is another such language which gained a lot attention recently for being used to scale Twitter’s backend. Scala differs from most other languages that run on the JVM, such as Groovy, JRuby and Jython, as it is statically typed. This means that, similar to Java and C#, the types must be known at compile time. Scala is usually introduced as being both OO and functional. While this statement is true (and daunting, as many people are uncomfortable with the f*** word), it fails to grasp the important aspects of Scala.

Among the most direct benefits of using Scala feature:

• Compatible with Java. Kinda obvious (as so are all the other 200+ languages over the JVM), but it is such an important feature that should not be overlooked. This means that Scala can use all Java libraries and frameworks. Which shows respect for people’s and companies investment on the technology.
• Joint Compilation. This means that, like Groovy, Scala classes are compiled to Java classes, and therefore can be used on Java projects (even by java classes on the same project they are defined). Even if your team decides to make the complete move towards Scala, this can be useful integrating with dynamic languages via JSR 223.
• Type Inference. If the compiler can guess the type (and it usually can), you don’t have to tell it. This allows Scala code to be as concise as dynamic languages, while still being type safe.
• Implicit conversion allows you to achieve in a type safe way what extension methods do for C# and open classes (mostly) do for ruby. That is: add methods to types you might not have not defined yourself (such as strings, lists, integers). This is one of the features that make Scala DSL friendly.
• Object immutability is encouraged and easy to accomplish. Scala even comes with immutable collections built-in.
• Getters and Setters are automatically generated for you. If you don’t want them (if you only want setters for example), you have to explicitly make them private. Which is not a problem, as the common case is to want them.
• Scala has first-order functions and implements an enumeration protocol (with the iterable trait), which helps keeping code clearer, more concise, and brings several other benefits.
• The Actor programming model eases up the development of highly concurrent applications.
• Exceptions don’t have to be explictly caught or thrown. It can be argued that having checked exceptions does more harm than good.

These features alone would be enough to make Scala a very interesting language, and worth being heralded as the current heir apparent to the Java throne by one of JRuby’s creator, Charles Nutter (a view somewhat shared by Neal Gafter). Or even worth of being endorsed both by Groovy’s creator, James Strachan, and by the inventor of Java, James Gosling.  Nonetheless Scala is deep, and there are several exciting advanced features that allow developers to be more productive. But learning such features before getting a good grasp the basics can be quite frustrating, more so without a good supporting literature (such as IBM’s, Aritma’s, Jonas Bonér’s, Daniel Spiewak’s, Sven Efftinge’s, the official one, and several others). However it quite is feasible, not only encouraged, to delve into deeper concepts as you need them.

Even though Scala has academic roots (as it shows on its papers page, and some advanced concepts these tackle), Scala has been successfully used on enterprise projects, besides Twitter, such as Siemens, Électricité de France Trading and WattzOn.

Besides all the good points, Scala does have some rough edges. Even though many people are working on overcoming them, they are likely to be relevant on the short term:

• Incipient IDE support. As Lift’s author expressed, IDEs for Scala, while undergoing a lot of development, are not what they are for Java. There is poor refactoring support, code completion and unit test integration. Not to mention the fact that most framework support tools will not play nicely with Scala. This can also put off some newcomers, as an IDE can help people learn the language. On the other hand, Martin Folwer relativizes this IDE situation, as a language that allows you to be more productive can more than make up for the lack of sophisticated tools.
• Joint Compilation is not supported by most IDEs as well. Again, likely to change as Scala grows in popularity.
• Immutability on a class is not really immutability, since referring objects may not be immutable themselves. And there is no way at the moment to ensure the whole object graph is immutable.
• Making JSR 223 work perfectly with Scala can be challenging. On the other hand, making it work good enough is quite attainable.
• Scala doesn’t support metaprogramming. This can be worked around by combining it with dynamic languages, such as Ruby (following a polyglot programming approach), but if you are going to do heavy use of metaprogramming, than using a whole different language may be a better solution (Fan is another static type language that runs over the JVM, similar to Scala, that has metaprogramming support).
• Frameworks that expect Java source, such as the client-side GWT, will not play nicely with Scala (note that people have made Scala work with GWT on the server-side though). However there is an ongoing project that will translate Scala into Java source.
• The syntax and some concepts are bit different from Java, such as: inverted type declaration order, underscore being used instead of wildcards, asterisks and default values, many kinds of nothing, no static methods (you need to use singleton objects instead) and other minor things. The documentation walks through this quite nicely though, but keep in mind that it is not an automatic transition from writing Java to writing Scala code.

As Joe Armstrong said, the need for languages that allow developers to easily make use of CPUs with multiple cores will only increase as such CPUs become cheaper and gain more and more cores. Scala is quite suited for such task, while Java’s development is stuck dealing with issues that come from being widely deployed, uncertanties of how open it will be in the future and political issues with some of its main contributors. Given the situation, Scala seems to fit quite nicely the role of the successor to Java’s throne.

* Concurrent – is when a punishment is served at the same time as another punishment.  For example, if an offender receives a term of 2 years imprisonment for one offence and another 2 years imprisonment (concurrent) for a second offence, then that equates to a total of 2 years imprisonment to cover both offences.

* Cumulative – is when a punishment is served on top of another punishment.  For example, if an offender receives a term of 2 years imprisonment for one offence and another 2 years imprisonment (cumulative) for a second offence, then that equates to a total of 4 years imprisonment to cover both offences.

* Parity – when more than one offender is charged with the same offence (known as co-offenders), they should receive the same punishment unless they are distinguishable from each other in some way (such as by the particular role they played in the offence or by their criminal records).

* Totality -when an offender is imprisoned for multiple offences, the total sentence must not exceed the overall criminality or be crushing.  It is not just a case of adding up all the terms of imprisonment because that could result in a very long and excessive sentence.  Some of the terms may have to be made concurrent to reduce the total sentence to a fair length in the circumstances.

Please be sure to update your class pages to remind students of the final due dates for their assignments.

All graduating seniors need to have all work completed by May 8th to allow registration to process their diplomas.

If any seniors have problems, please be sure to let their POD instructor know so that he/she can provide support.

Quand l’actualité décide de se déchaîner, il faut suivre. Même si les responsables de ce déchaînement croient pouvoir nous tenir à l’écart en ne nous prévenant pas – contrairement au concurrent. Cris, engueulades, grosse pression, tout y est passé hier. Quand ce fut plus silencieux, pendant l’écriture des papiers, l’ambiance était encore électrique. Mieux valait bosser dans son coin pour ne pas risquer de ré-embraser le tout. Et la tempête qui est née n’étant pas encore tout près de s’arrêter, la tension ne retombe pas à l’agence. Ce matin, avant de faire quoi que ce soit d’autre, épluchage du concurrent. Pour constater avec plaisir que nous avons à peu près dix fois plus d’informations que lui. Ca fait du bien, quand il nous croit morts et enterrés, de lui foutre une bonne claque sur un événement aussi important. Au-delà de cette satisfaction purement égocentrique, il faut espérer que l’effort ait payé dans les ventes…

En ce lendemain de tempête, il m’a fallu sérieusement m’attaquer à mes sujets “polémico-locaux”. Pour l’un d’eux (pas celui avec les bourgeois), près de deux heures passées à recueillir des témoignages, puis un peu de temps perdu en essayant de joindre les personnes mises en cause. Pour finalement tomber sur une partie de ping-pong entre ces dernières. “Ce n’est pas de ma responsabilité, c’est de la sienne.” “Ce n’est pas vrai, c’est de sa responsabilité.” “Ce serait de ma responsabilité si c’était un centimètre plus loin, mais pas là.” “L’ensemble des lieux est sous sa responsabilité, pas seulement un centimètre avant ce qui pose problème.” Autant dire que je ne suis pas sortie. Mais c’est marrant. Ils utilisent les mêmes arguments, qu’ils se contentent simplement d’inverser. Aucun des deux n’est capable de me sortir un papier officiel qui lui donne raison, tout comme aucun des deux n’a l’air vraiment sûr de ce qu’il avance. Impossible de compter les points, impossible donc de désigner un vainqueur. En revanche, les victimes sont parfaitement identifiées et ne se sont pas privé de m’exposer leurs soucis quotidiens, pendant que ceux qui pouraient régler le problème se refilent la patate chaude, tranquillement installés dans leurs bureaux.

Anecdote du jour : le nouveau stagiaire du service des sports est en première année dans la même école que nous. Charge à lui de ne pas ternir l’image de l’école auprès des patrons. Si son rythme de travail reste celui d’aujourd’hui, il ne pourra pas, lui, ternir notre image auprès de l’école… car il lui serait difficile de dire qu’il est honteusement exploité. La tempête ne passe pas par le service des sports.

De façon tout aussi anecdotique, sa présence est l’occasion de contredire une théorie sur le recrutement, que m’avaient exposée certains collègues, avant que la tempête ne se lève. Ils estimaient, avec étonnement, que beaucoup de fraîches recrues étaient du genre féminin. Selon eux, c’était une vraie volonté de leurs chefs, des hommes qu’ils supposent attirés par la chaire fraîche – car l’exposition de cette théorie face à moi est due au fait que nous parlions d’une recrue dont les seuls qualités semblent être la paire de seins et les décolletés. Mes collègues supputaient donc que les arguments physiques faisaient partie du CV.

Appliquer cette théorie à mon cas leur a cependant posé un premier problème : non pas que mes atouts physiques aient été remis en cause dans le bureau (il y aurait pourtant de bonnes raisons), mais il se trouve que la personne me recrutant ne m’a jamais vue. Nous nous sommes parlés au téléphone, par email souvent, mais la seule chose qu’il ait réellement pu juger chez moi, ce sont les articles que j’ai écrits pendant tout le temps où j’ai travaillé là, avant de partir… pour revenir en ce moment.

Le second problème qui s’est posé à mes collègues est purement statistique : après un décompte en toute honnêteté, planning à l’appui, il s’avère que les fraîches recrues ne sont pas que des jeunes femmes, mais que cela s’équilibre plutôt entre les sexes. On peut donc être du sexe masculin et, malgré ce handicap évident dans la vie, être recruté (pour autant, le bon plan n’est pas forcément par ici…).

–Round-Up of Recent VOD News from Concurrent

VOD technology provider, Concurrent, said Monday that Canada’s second-largest MSO, Cogeco Cable, an existing Concurrent customer, has signed a master purchase agreement designating the company as the preferred provider of video technology for its VOD service in all its Canadian markets. According to Concurrent, the multi-year deal supports expansion of and upgrades to Cogeco’s existing VOD platform, and makes it possible for the MSO to offer a range of new services to its 400,000 digital subscribers in Quebec and Ontario, including timeshifted TV, network DVR and advanced advertising. “Operators like Cogeco are increasingly under competitive pressure to add more personalized video services,” Concurrent president and CEO, Dan Mondor, said in a prepared statement. “Concurrent’s vision for the future of on-demand supports a true consumer-driven experience while maximizing the revenue potential of video.” Added Chris MacFarlane, Cogeco’s VP of corporate engineering: “Concurrent has been a strong partner with Cogeco since we first launched on-demand in 2002. This partnership has significantly contributed to the success this service has seen with our customers. This new agreement formalizes the value we place on this relationship and helps us move with confidence into the next generation of on-demand services.”

According to Concurrent, the new agreement will see Cogeco’s existing systems upgraded and expanded using Concurrent’s MediaHawk 4500 video servers, complete with the latest release of the company’s MediaHawk software. Concurrent bills the MediaHawk 4500 as featuring Gatling Resilient Streaming technology (automatically detects failures and instantly routes stream demands to alternate resources, in order to prevent interruption of VOD sessions), and support for such next-generation on-demand applications as timeshifted TV, advanced advertising, network DVR and multi-device content distribution (e.g. VOD on the PC, via a broadband connection).

In other recent news from Concurrent:
–Last month, the company announced a new, “end-to-end, multi-screen” strategy. For an in-depth overview of this, see [itvt]’s interview with James Brickmeier, Concurrent’s VP and general manager of converged video solutions, in Issue 8.35.
–In January, the company announced that Alaska-based triple-play provider, GCI, had selected it to provide VOD performance data collection, warehousing and analytics. According to the company, GCI will use a range of its services and products, including the ReportOne and Operational Intelligence (Oi) tools from Concurrent’s Everstream line of data collection and management tools. “The Concurrent solutions greatly enhance the view into our on-demand business and technical metrics,” Brett Worrall, GCI’s product development manager, said in a prepared statement. “These tools allow different groups within our organization to easily track and share key metrics both internally and with third-party stakeholders, such as TVN, GCI’s comprehensive VOD content service provider.” According to Concurrent, ReportOne and Oi provide a “common metrics” approach to managing key performance indicators, that is necessitated by the fact that operators are rolling out open VOD solutions containing products from multiple different vendors. The company says that the solutions–which offer scorecards, dashboards and reports on key performance indicators–provide the cable and broadband industries’ “first comprehensive solution for performance analytics.” Performance indicators tracked by the tools include subscriber activity rates, capacity utilization, session and stream success/failure rates, root cause analysis and correlations, and VOD usage by location, provider and title. Concurrent bills its Everstream product line as providing a census-level, unbiased, cross-service data collection and aggregation platform that provides analytics for VOD, linear TV, and broadband TV services. It also supports advanced advertising capabilities, such as SCTE-130-compliant campaign management and ad targeting, the company says.
–In January, the company announced a new software release for its MediaHawk 4000 and 4500 video server lines. According to the company, the new release is SCTE-130 compliant and offers various new enhancements, including playlist-support enabling advanced advertising. “Integrating advanced advertising applications with the on-demand delivery framework using the SCTE standards allows operators to use ad-generated revenue to fund the launch of new services such as time-shifted television and network-based DVR,” Concurrent’s James Brickmeier said in a prepared statement. “Our newest version of MediaHawk software provides Concurrent customers the flexibility needed to quickly upgrade their existing systems and prepare for emerging on-demand advertising initiatives such as those being led by Canoe Ventures.” The SCTE-130 standard is designed to enable a unified platform for addressable advertising, by providing inventory and placement definitions, while merging content and subscriber metadata for targeting zones (or, in a unicast environment, for targeting individuals). Concurrent says that it has already upgraded a number of its Everstream data collection and management products to comply with SCTE-130; and the company claims that the addition of playlist support to the MediaHawk platform means that it can now offer an end-to-end solution that supports targeted ad insertion, ad bumpering and ad replacement. The company also bills the new release as including client interface protocols supporting ETV/EBIF, Web client and tru2way platforms; and it says that these interface protocols enabled interoperability trials at CableLabs late last year, where it demo’d collaborative solutions with BIAP, Invidi and This Technology. Other features included in the new release, according to Concurrent, include: NGOD and ISA compatibility, ensuring compatibility between VOD component vendors; improved stream, storage and ingest density (2,400 SD streams per MediaHawk 4500; 120 SD channels per Real Time Pitcher/Catcher; and 3,300 SD hours of content per MediaStore 2000); HTTP progressive download in support of IPTV and Internet video applications; tiered asset management, optimizing content placement within a storage complex, based on content usage patterns; enhanced support of time-shifted television; improved flexibility in providing multiple trick-mode speeds; and RTP encapsulation/DVB retransmission, allowing better Quality of Service in lower-quality network environments.

De concurrentiestrijd tussen de twee autobouwers uit Duitsland heeft wat weg van een spelletje schaken. Om de nieuwe A4 aan het grote publiek voor te stellen, lanceerde Audi een campagne met de slogan: “Your move, BMW.”. Een regelrechte aanval op hun directe concurrent.

Het antwoord uit München liet niet lang op zich wachten. Het media- en/of reclamebureau van BMW plaatste een reclamepaneel dat drie keer zo groot was, naast dat van Audi. Op de affiche stond een afbeelding van de BMW 3, vergezeld van de tekst: “Checkmate.”. Voor BMW was de aanval bij deze afgeweerd. Your move, Audi.

Gedurende mijn loopbaan heb ik vele Retail bedrijven van binnen kunnen bekijken. De één super succesvol met sterk groeiende omzet, de andere onder hoge druk om de voorgaande succesvolle jaren te evenaren en te verbeteren. Organisaties waar de winst is verdwenen en de MT leden het zinkende schip verlaten en anderen proberen het tij te keren.

Er zijn een aantal  cultuurwaarden die in succesvolle organisaties aanwezig zijn en bij de niet succesvolle organisatie juist ontbreken. Veel van de cultuurkenmerken waren aanwezig bij het succesvolle Scapino. Keer op keer was het een feest van herkenning.

De cultuurwaarden voor succes moeten als grondwet worden vastgelegd en bewaakt worden dat deze niet geschonden worden. Kenmerken voor succesvolle organisaties zijn:

• Het heilige vuur. Daar is voor nodig een bedrijfscultuur, charisma van de leiders en “follow the leader” mentaliteit;
• Niet zeuren. Een hoofdknikje moet voldoende zijn om de mensen uit de startblokken te laten schieten;
• De ondernemer zelf aan het roer. Iedere leider in de organisatie moet een ondernemer zijn en zich ook zo manifesteren.
• Kosten laag. Waarom moet een organisatie die winst maakt vet op de ribben krijgen? Houd het simpel, houd het in de lijn. Houd het vooral doelgericht en effectief. Zo min mogelijk staffuncties, reorganiseer ook als het goed gaat.
• Uitproberen en pionieren (innovatie moet). Er zijn vaak veel redenen om een idee niet uit te voeren. Doe het nu wel eens. Blijf ondernemer en koopman!
• Jong en dynamisch. Dit heeft niet met leeftijd te maken maar alles met potentie en flexibiliteit;
• Strijdbaar. Niemand mag ons tegenhouden en wij zetten ons in met hart en ziel. Het zal gebeuren zoals wij dat willen. Wij gaan “erop en erover”;
• Risico’s durven nemen. Bij twijfel niet inhalen, maar zo min mogelijk twijfelen;
• Creatief. Niets is onmogelijk;

Het is zo eenvoudig en een open deur. Toch ontbreekt het vaak aan het de volgende principes van ondernemerschap:

1.  Het zien. Iedere ondernemer weet echt wel wat eraan schort. Kijk maar eens goed;
2. Plannen maken. Iedere ondernemer weet echt wel wat er zou moeten gebeuren, we maken plannen en rapporten en krijgen adviezen van iedereen;
3. De plannen doorvoeren. Dat is het moeilijkst.

De succesfactoren voor realisatie van plannen ligt in leiderschap en bovenstaande cultuurwaarden:

• Ook al heeft u een uniek concept er is altijd een concurrent/vijand die u probeert te verslaan. Het gebrek aan een vijand geeft een gebrek aan focus en richting en verslapt de organisatie. Maak die vijand tastbaar;
• Wees een inspirerend leider. Niet zo voorspelbaar, wees aanspreekbaar en aanstekelijk;
• Zorg voor de juiste informatie. Snel, up-to-date, perfect, niet te veel maar ook niet te weinig;
• Luisteren naar de medewerkers. Niets is meer motiverend dan de baas op de werkvloer;
• Wees altijd op zoek naar nieuwe ideeën die kunnen worden doorgevoerd;
• Eis net zoveel van uzelf als van uw medewerkers (wees een concurrent van uw zelf. Moedig u aan iedere dag iets te doen waar u de dag ervoor tegenop zag).
• Stop meteen ongewenste situaties. Roep ze direct een halt toe;
• Vergaderingen mogen niet langer dan één uur duren;
• Medewerkers die het allemaal al zo goed weten zijn tegenwerkers (ik doe dit werk al 20 jaar, ze hoeven mij niets te vertellen);
• Wees luid en duidelijk. Dan weet men waar men aan toe is;
• Wees enthousiast;