Assential-BW

Hi Gurus,
Can Ascential trigger a process chain(which includes data loads) in BW?
If yes, can u please explain me how.
Regards,
RRK

Hi RRK,
Check it here.
Trigger BW ?
Laxmikant

Similar Messages

What gen of iPod classic is this?

I'm not sure if this is gen 6 or 7, is there any way to tell through the details?
http://www.chapters.indigo.ca/electronics/apple-ipod-classic-160gb-black/8859093 41283-item.html?ikwid=ipod+classic&ikwsec=Home&ikwidx=0

Well - in structure, it is nearest to the Command pattern as far as I can tellOr Strategy. Or Builder. Several design pattenrs may share the same class structure, the difference is in the context, forces, and the parts one want to be flexible. And if someone wants to make it explicit which pattern is applied, they should name things accordingly.
As Saish said this example shows little more that inheritance at work. Not a pattern in itself, but a core element of the language. Trying to "identify" a pattern that is not obvious from the context is either:
- a sign that the original coder completely missed the point of using a pattern (which is, as Saish said too, assentially about communication)
- a sign that the maintenance coder is looking for patterns where there aren't
- an exercise question
but it differs in so much as its motivation is to polymorphically allow the use of different exporters rather than provide a set of action commands.That shouldn't count as a difference, merely as an "application" (it's perfectly valid to have a hierarchy of commands all devoted to exporting, although, as stated, if the original coder applied the Command pattern, he should have made it explicit, by renaming the interface, e.g. to ExportCommand).

What kind of design pattern is this?

Hi ,
I am just learning the designpattern. So when I went through different kinds of design pattern, I got some doubts as it looks same some design patterns. could anybody please tell what kind of design pattern is the following one?
public interface IExporter{
void export();
public class ExcelExporter implements IExporter{
public void export(){
//TODO implementation
public class CVSExporter implements IExporter{
public void export(){
//TODO implementation
}thanks in advance..

Well - in structure, it is nearest to the Command pattern as far as I can tellOr Strategy. Or Builder. Several design pattenrs may share the same class structure, the difference is in the context, forces, and the parts one want to be flexible. And if someone wants to make it explicit which pattern is applied, they should name things accordingly.
As Saish said this example shows little more that inheritance at work. Not a pattern in itself, but a core element of the language. Trying to "identify" a pattern that is not obvious from the context is either:
- a sign that the original coder completely missed the point of using a pattern (which is, as Saish said too, assentially about communication)
- a sign that the maintenance coder is looking for patterns where there aren't
- an exercise question
but it differs in so much as its motivation is to polymorphically allow the use of different exporters rather than provide a set of action commands.That shouldn't count as a difference, merely as an "application" (it's perfectly valid to have a hierarchy of commands all devoted to exporting, although, as stated, if the original coder applied the Command pattern, he should have made it explicit, by renaming the interface, e.g. to ExportCommand).

Assential-BW

Similar Messages

Maybe you are looking for