MI 7.1 data objects push data to backend in some sequence

Hi all,
Let's say we have 2 data objects with no dependency between these. If we add instances of these data objects on the client in some sequence, can we be sure that these instances will arrive on DOE in the same order and will be processed in that order? Or do we actually have to define this order with report 'DOE_MAINTAIN_DO_SYNC_ORDER' ? But i've read on this forum that this is only for backward compatibility reasons... I find it rather strange that this sequence was easily be set in MI7.O with MI_MCD, but in MI7.1 it seams not.
In thread Re: How to set execution preferences between Data Objects, someone says that this will be encorporated in the DOE workbench (SDOE_WB) itself. We are on MI 7.1 SP9. Is this the case then? Were can we do these settings?
Additional question:
Let's say there is a dependency between these 2 data objects, then i know that download request for leading data object triggers download request of following DO. Does this also define the update order from client to DOE?
thanks in advance,
regards
Peter

Hi,
I will answer your questions in the same sequence as posted by you.
1. If the objects have no association between them: In this case whenever on the client any change is made to an object the state of the transaction is commited to the device outbound queue. It does not matter whether Obj1 was modified or object 2. The order in which the changes are done will be the order in which the transactions will be commited to DB and the same order will be used by MI to process these messages when client syncs.
2. In case the objects have dependency: Here also the same principle works as in 1. Having a dependency between two objects technically drills down to having referential integrity between these objects. Lets say DO1 refers to DO2 instances. Then when you are saving DO1 your application would obviously ensure that it maintains the business referential integrity to DO2 else it will not even be a valid DO1 instance in your SAP Backend.
Thus the order in which changes are done on the client is what determines the order of processing of these instances on the server.
Regards,
Vikas

Similar Messages

Difference b/w DATA TYPE and DATA OBJECT & differences b/w TYPE and LIKE

hai
can any one say the differences between Data type and Data Object.
And also differences between TYPE and LIKE
thanks
Gani

hi,
_Data Types and Data Objects_
      Programs work with local program data that is, with byte sequences in the working memory. Byte sequences that belong together are called fields and are characterized by a length, an identity (name), and as a further attribute by a data type. All programming languages have a concept that describes how the contents of a field are interpreted according to the data type.
      In the ABAP type concept, fields are called data objects. Each data object is thus an instance of an abstract data type. There are separate name spaces for data objects and data types. This means that a name can be the name of a data object as well as the name of a data type simultaneously.
Data Types
   As well as occurring as attributes of a data object, data types can also be defined independently. You can then use them later on in conjunction with a data object. The definition of a user-defined data type is based on a set of predefined elementary data types. You can define data types either locally in the declaration part of a program using the TYPESstatement) or globally in the ABAP Dictionary. You can use your own data types to declare data objects or to check the types of parameters in generic operations.
     All programming languages distinguish between various types of data with various uses, such as .. type data for storing or displaying values and numerical data for calculations. The attributes in question are described using data types. You can define, for example, how data is stored in the repository, and how the ABAP statements work with the data.
Data types can be divided into elementary, reference, and complex types.
a. Elementary Types
These are data types of fixed or variable length that are not made up of other types.
The difference between variable length data types and fixed length data types is that the length and the memory space required by data objects of variable length data types can change dynamically during runtime, and that these data types cannot be defined irreversibly while the data object is being declared.
Predefined and User-Defined Elementary Data Types
You can also define your own elementary data types in ABAP using the TYPES statement. You base these on the predefined data types. This determines all of the technical attributes of the new data type. For example, you could define a data type P_2 with two decimal places, based on the predefined data type P. You could then use this new type in your data declarations.
b. Reference Types
Reference types are deep data types that describe reference variables, that is, data objects that contain references. A reference variable can be defined as a component of a complex data object such as a structure or internal table as well as a single field.
c. Complex Data Types
Complex data types are made up of other data types. A distinction is made here between structured types and table types.
Data Objects
      Data objects are the physical units with which ABAP statements work at runtime. The contents of a data object occupy memory space in the program. ABAP statements access these contents by addressing the name of the data object and interpret them according to the data type.. For example, statements can write the contents of data objects in lists or in the database, they can pass them to and receive them from routines, they can change them by assigning new values, and they can compare them in logical expressions.
       Each ABAP data object has a set of technical attributes, which are fully defined at all times when an ABAP program is running (field length, number of decimal places, and data type). You declare data objects either statically in the declaration part of an ABAP program (the most important statement for this is DATA), or dynamically at runtime (for example, when you call procedures). As well as fields in the memory area of the program, the program also treats literals like data objects.
        A data object is a part of the repository whose content can be addressed and interpreted by the program. All data objects must be declared in the ABAP program and are not persistent, meaning that they only exist while the program is being executed. Before you can process persistent data (such as data from a database table or from a sequential file), you must read it into data objects first. Conversely, if you want to retain the contents of a data object beyond the end of the program, you must save it in a persistent form.
Declaring Data Objects
      Apart from the interface parameters of procedures, you declare all of the data objects in an ABAP program or procedure in its declaration part. These declarative statements establish the data type of the object, along with any missing technical attributes. This takes place before the program is actually executed. The technical attributes can then be queried while the program is running.
     The interface parameters of procedures are generated as local data objects, but only when the procedure is actually called. You can define the technical attributes of the interface parameters in the procedure itself. If you do not, they adopt the attributes of the parameters from which they receive their values.
ABAP contains the following kinds of data objects:
a. Literals
Literals are not created by declarative statements. Instead, they exist in the program source code. Like all data objects, they have fixed technical attributes (field length, number of decimal places, data type), but no name. They are therefore referred to as unnamed data objects.
b. Named Data Objects
Data objects that have a name that you can use to address the ABAP program are known as named objects. These can be objects of various types, including text symbols, variables and constants.
Text symbols are pointers to texts in the text pool of the ABAP program. When the program starts, the corresponding data objects are generated from the texts stored in the text pool. They can be addressed using the name of the text symbol.
Variables are data objects whose contents can be changed using ABAP statements. You declare variables using the DATA, CLASS-DATA, STATICS, PARAMETERS, SELECT-OPTIONS, and RANGESstatements.
Constants are data objects whose contents cannot be changed. You declare constants using the CONSTANTSstatement.
c. Anonymous Data Objects
Data objects that cannot be addressed using a name are known as anonymous data objects. They are created using the CREATE DATAstatement and can be addressed using reference variables.
d. System-Defined Data Objects
System-defined data objects do not have to be declared explicitly - they are always available at runtime.
e. Interface Work Areas
Interface work areas are special variables that serve as interfaces between programs, screens, and logical databases. You declare interface work areas using the TABLES and NODESstatements.
What is the difference between Type and Like?
Answer1:
TYPE, you assign datatype directly to the data object while declaring.
LIKE,you assign the datatype of another object to the declaring data object. The datatype is referenced indirectly.
Answer2:
Type is a keyword used to refer to a data type whereas Like is a keyword used to copy the existing properties of already existing data object.
Answer3:
type refers the existing data type
like refers the existing data object
reward if useful
thanks and regards
suma sailaja pvn

Data types and Data object

Can Any one give me Clear definition of Data type and Data objects.
Concept i know clearly.. but unable to explain it..
Regards,
Prasanna

Data consists of strings of bytes in the memory area of the program. A string of related bytes is called a field. Each field has an identity (a name) and a data type. All programming languages have a concept that describes how the contents of a field are interpreted according to the data type.
 In the ABAP type concept, fields are called data objects. Each data object is an instance of an abstract data type. Data types in ABAP are not just attributes of fields, but can be defined in their own right. There are separate name spaces for data objects and data types. This means that a name can at the same time be the name of a data object as well as the name of a data type.
Data Types:
 As well as occurring as attributes of a data object, data types can also be defined independently. The definition of a user-defined data type is based on a set of predefined elementary data types. You can define data types either locally in the declaration part of a program (using the TYPES statement) or globally in the ABAP Dictionary. You can use your own data types to declare data objects or to check the types of parameters in generic operations.
 Data types can be divided into elementary, reference, and complex types
Data objects:
 Data objects are the physical units with which ABAP statements work at runtime. Each ABAP data object has a set of technical attributes, which are fully defined at all times when an ABAP program is running. The technical attributes of a data object are its length, number of decimal places, and data type. ABAP statements work with the contents of data objects and interpret them according to their data type. You declare data objects either statically in the declaration part of an ABAP program (the most important statement for this is DATA), or dynamically at runtime (for example, when you call procedures). As well as fields in the memory area of the program, the program also treats literals like data objects.
ABAP contains the following kinds of data objects
Literals
 Named Data Objects
Predefined Data Objects
Dynamic Data Objects

Data type and Data object

Hi Friends,
        What is the difference between Data type and Data object?
Best Regards,
VRV Singh

hi
good
Each ABAP program define its own data types using the statement.
TYPES dtype TYPE type ...
and declare its own variables or instance attributes of classes using the statement
DATA var {TYPE type} ...
Within the program or a class, you can also define local data types and variables within procedures. Local variables in procedures obscure identically-named variables in the main program or class.
When creating data types and data objects, there are a number of naming convention that also apply for other local program definitions, such as procedures. These are described in detail in the keyword documentation.
The Additions TYPE and LIKE
The additions TYPE type and LIKE dobj are used in various ABAP statements. The additions can have various meanings, depending on the syntax and context.
·        Definition of local types in a program
·        Declaration of data objects
·        Dynamic creation of data objects
·        Specification of the type of formal parameters in subroutines
·        Specification of the type of formal parameters in methods
·        Specification of the type of field symbols
Constructing New Data Types
The TYPE addition allows you to construct new data types in the TYPES, DATA; CONSTANTS; and STATICSstatements. In the TYPES statement, these are local data types in the program. In the other statements, they are attributes of new data objects, meaning that the newly defined data types are not free-standing. Rather, they are linked to database objects.This means that you can refer to them using the LIKEaddition, but not using TYPE.
To construct new data types, the addition TYPE can be used with the following type constructors:
·        Construction of reference types
REF TO type|dobj
·        Construction of structured data types
BEGIN OF struc_type.
END OF struc_type.
·        Construction of table types
tabkind OF linetype
These data types only exist during the runtime of the ABAP program.
Referring to Known Data Types or Data Objects
Using the additions TYPE or LIKE in the TYPESstatement, local data types in a program can be referred to known data types or data objects. This is mainly the case with user-defined elementary data types. If you declare variables using the additions TYPE type or LIKE dobj with statement DATA, the data type of var is already fully defined before the declaration is made.
The known types or data that are referred to must be visible at the point where the data type or variable is declared.
A known data type can be any of the following:
·        A predefined ABAP type to which you refer using the TYPE addition
·        An existing local data type in the program to which you refer using the TYPE addition
·        The data type of a local data object in the program to which you refer using the LIKE addition
·        A data type in the ABAP Dictionary to which you refer using the TYPE addition. To ensure compatibility with earlier releases, it is still possible to use the LIKE addition to refer to database tables and flat structures in the ABAP Dictionary. However, you should use the TYPE addition in new programs.
The LIKE addition takes its technical attributes from a visible data object. As a rule, you can use LIKE to refer to any object that has been declared using DATA or a similar statement, and is visible in the current context. The data object only has to have been declared. It is irrelevant whether the data object already exists in memory when you make the LIKE reference.
·        In principle, the local data objects in the same program are visible. As with local data types, there is a difference between local data objects in procedures and global data objects. Data objects defined in a procedure obscure other objects with the same name that are declared in the global declarations of the program.
·        You can also refer to the data objects of other visible ABAP programs. These might be, for example, the visible attributes of global classes in class pools. If a global class cl_lobal has a public instance attribute or static attribute attr, you can refer to it as follows in any ABAP program:
DATA dref TYPE REF TO cl_global.
DATA: f1 LIKE cl_global=>attr,
       f2 LIKE dref->attr.
You can access the technical properties of an instance attribute using the class name and a reference variable without first having to create an object. The properties of the attributes of a class are not instance-specific and belong to the static properties of the class.
http://help.sap.com/saphelp_nw2004s/helpdata/en/fc/eb2ff3358411d1829f0000e829fbfe/content.htm
thanks
mrutyun^

Data types and data objects

diff b/w data types and data objects

hi prasanth,
Data Types and Data Objects
Programs work with local program data that is, with byte sequences in the working memory. Byte sequences that belong together are called fields and are characterized by a length, an identity (name), and as a further attribute by a data type. All programming languages have a concept that describes how the contents of a field are interpreted according to the data type.
In the ABAP type concept, fields are called data objects. Each data object is thus an instance of an abstract data type. There are separate name spaces for data objects and data types. This means that a name can be the name of a data object as well as the name of a data type simultaneously.
Data Types
Data types are templates for creating data objects. Data types can be defined independently in the ABAP program or in the ABAP Dictionary. As attributes of a data object, data types can also exist in a non-independent state. Data types do not use any memory space for work data, but may require memory for administration information.
As well as occurring as attributes of a data object, data types can also be defined independently. You can then use them later on in conjunction with a data object. The definition of a user-defined data type is based on a set of predefined elementary data types. You can define data types either locally in the declaration part of a program using the TYPESstatement) or globally in the ABAP Dictionary. You can use your own data types to declare data objects or to check the types of parameters in generic operations.
All programming languages distinguish between various types of data with various uses, such as .. type data for storing or displaying values and numerical data for calculations. The attributes in question are described using data types. You can define, for example, how data is stored in the repository, and how the ABAP statements work with the data.
Data types can be divided into elementary, reference, and complex types.
a. Elementary Types
These are data types of fixed or variable length that are not made up of other types.
The difference between variable length data types and fixed length data types is that the length and the memory space required by data objects of variable length data types can change dynamically during runtime, and that these data types cannot be defined irreversibly while the data object is being declared.
Predefined and User-Defined Elementary Data Types
You can also define your own elementary data types in ABAP using the TYPES statement. You base these on the predefined data types. This determines all of the technical attributes of the new data type. For example, you could define a data type P_2 with two decimal places, based on the predefined data type P. You could then use this new type in your data declarations.
b. Reference Types
Reference types are deep data types that describe reference variables, that is, data objects that contain references. A reference variable can be defined as a component of a complex data object such as a structure or internal table as well as a single field.
c. Complex Data Types
Complex data types are made up of other data types. A distinction is made here between structured types and table types.
Data Objects
A data object is an instance of a data type and occupies as much memory space as its type specifies. An ABAP program only works with data that is available as content of data objects. Data objects are either created implicitly as named data objects, or exanonymous data objects using CREATEDATA.
Data objects are the physical units with which ABAP statements work at runtime. The contents of a data object occupy memory space in the program. ABAP statements access these contents by addressing the name of the data object and interpret them according to the data type.. For example, statements can write the contents of data objects in lists or in the database, they can pass them to and receive them from routines, they can change them by assigning new values, and they can compare them in logical expressions.
Each ABAP data object has a set of technical attributes, which are fully defined at all times when an ABAP program is running (field length, number of decimal places, and data type). You declare data objects either statically in the declaration part of an ABAP program (the most important statement for this is DATA), or dynamically at runtime (for example, when you call procedures). As well as fields in the memory area of the program, the program also treats literals like data objects.
A data object is a part of the repository whose content can be addressed and interpreted by the program. All data objects must be declared in the ABAP program and are not persistent, meaning that they only exist while the program is being executed. Before you can process persistent data (such as data from a database table or from a sequential file), you must read it into data objects first. Conversely, if you want to retain the contents of a data object beyond the end of the program, you must save it in a persistent form.
Declaring Data Objects
Apart from the interface parameters of procedures, you declare all of the data objects in an ABAP program or procedure in its declaration part. These declarative statements establish the data type of the object, along with any missing technical attributes. This takes place before the program is actually executed. The technical attributes can then be queried while the program is running.
The interface parameters of procedures are generated as local data objects, but only when the procedure is actually called. You can define the technical attributes of the interface parameters in the procedure itself. If you do not, they adopt the attributes of the parameters from which they receive their values.
ABAP contains the following kinds of data objects:
a. Literals
Literals are not created by declarative statements. Instead, they exist in the program source code. Like all data objects, they have fixed technical attributes (field length, number of decimal places, data type), but no name. They are therefore referred to as unnamed data objects.
b. Named Data Objects
Data objects that have a name that you can use to address the ABAP program are known as named objects. These can be objects of various types, including text symbols, variables and constants.
Text symbols are pointers to texts in the text pool of the ABAP program. When the program starts, the corresponding data objects are generated from the texts stored in the text pool. They can be addressed using the name of the text symbol.
Variables are data objects whose contents can be changed using ABAP statements. You declare variables using the DATA, CLASS-DATA, STATICS, PARAMETERS, SELECT-OPTIONS, and RANGESstatements.
Constants are data objects whose contents cannot be changed. You declare constants using the CONSTANTSstatement.
c. Anonymous Data Objects
Data objects that cannot be addressed using a name are known as anonymous data objects. They are created using the CREATE DATAstatement and can be addressed using reference variables.
d. System-Defined Data Objects
System-defined data objects do not have to be declared explicitly - they are always available at runtime.
e. Interface Work Areas
Interface work areas are special variables that serve as interfaces between programs, screens, and logical databases. You declare interface work areas using the TABLES and NODESstatements.
regards,
sravanthi

Master data object - Available for reporting related

Hi Colleagues,
I want to load some 'duplicates' to info Object X. Meaning I have all values same but differ in one attribute. (Key is same). I do not want to use compounding for few reasons. I have not explored on functinality masterdata for reporting (Flexible update, not sure i used correct word) Can you please extend help in understanding the following..
Questions 1:
I understand that I can make available for reporting the existing master data object.
2) Can I add some code to allow duplicates there?
3) Can still the infoobjet navigational attributes has the same functionality - meaning they can be reported from reports of this newly extended masterdata?
Thanks for your time.
Best Regards,
Hari

Hi Arun,
Thanks for your time..
Infoobject alread exists with out the attribute below at the monet. It is also available in the cubes for my reporting on cubes..I would like to add the following attribute for my phase 2 for my new reporting needs..
Data:
Infoobject - Attribute,
SKU1 - GRP1
SKU1 - GRP2
SKU2 - GRP2
The issue is with the 1st 2 records.. As I do not have the componding.. My Cube already have Infoobject with lots of data... I do not want to add attribute componding as it demands for the presence in the cubes also. So I have to double the current data base size.. Ahh I do not want this..
Coming to reporting on the cube
I would like to report on both the things.. Like..
Including attribute
SKU1 GRP1 abcd
SKU1 GRP2 abcd
SKU2 GRP3 xyz
excluding attribute
SKU1 abcd
SKU2 xyd
We do not have any keyfigures..none is related with time..
Hope I am clear..
Thanks for your time,
Regards,
Hari
Message was edited by: Hari Kiran

The creation of device local data objects - Unable to find generated object

Hi all,
I get an error when I try to generate an ESDMA containing a "Device Local" data object.
I have created a "Device Local" data object containing a very simple node structure. The object is "active" and everything seems to work fine, until I generate the ESDMA. The following error is shown : Unable to find generated objects in repository.
The esdma is generated without problems, when I remove the device local data object.
I hope you have some ideas of what the issue might be.
Best regards,
Nima

Hi Siva
Actually i am working on this problem together with Nima and the problem is not related to SAP Basis objects.
The problem is in SDOE_WB, with the SWCV. Creating a Data object of type LOCAL DEVICE and a NODE. If you add a field/s and then activate, and look in Generated objects The Table object is not generated (only the structure and the table type). At this point there are no syntax/error messages.
If we try to generate an esdma using the ESDMA design time, using this SWCV, it fails, with the message, Unable to find generated objects, in the repository. That is it is looking for the Table object that was not generated in sdoe_wb. This is only a problem with creating a data object of type DEVICE LOCAL, every other type of DO is fine.. I assume it is an SAP error.

Differences between DATA TYPE and DATA OBJECTS

I am new to ABAP,I want to know the differences between DATA TYPE and DATA OBJECTS with some examples.
please help me regarding this.

Hi Ashish,
Data Types:       Are pure descriptions.
               No memory is associated with data types.
               Describes the technical properties of data objects.
EX.
1.     C-CHARACTER
2.     D-DATE
3.     F-FLOAT
4.     I-INTEGER
5.     N-NUMERIC TEXT
6.     T-TIME
7.     P-PACKED NUMBER
8.     X-HEXADECIMAL
9.     STRING-Variable length string.
10.     XSTRING-Variable length byte string.
Data Objects: Are created during runtime.
                They cannot exist without the data Types.
                Occupies memory space.
EX:
1.     INTERNAL DATA OBJECT- Internal Data objects
     LITEERAL- A literal has a fixed value.Ex: WRITE:u201DWORK HARDu201D.
     VARIABLES: Data statement is used to create variables.
EX.DATA: NUM TYPE I.
NUM: VARIABLE defined by data statement.
EX: DATA: PRICE LIKE NUM.
     CONSTANT-It is a data object, which contains a constant value throughout the program.
Can be declared in program by using CONSTANT statement.
EX:CONSTANT: INT TYPE I VALUE 15.
2.     EXTERNAL DATA OBJECT: Are defined in tables i.e In ABAP/4 dictionary you can access this data from table.
         EX: TABLES: SFLIGHT
          DATA: SEATS LIKE SFLIGHT-SEATSMAX.
3.     SYSTEM DEFINED DATA OBJECTS:Space & system variables like SY-UNAME,SY-DATUM, SY-REPID.
4.     SPECIAL DATA OBJECTS:
     PARAMETERS: Are Variables ,which can accept value from user.
      SELECTION SCREEN : Are special internal tables to accept value ranges from user.
3 APPROACHES TO DEFINE DATA OBJECTS.
1.     ELEMENTARY TYPES
DATA: Customer _Name (25) TYPE C,
               Vendor_Name (25) TYPE C.
2.     REFRENCE TO AN EXISTING FIELD:
DATA: Customer _Name2 (25) TYPE C,
              Vendor_Name2 (25) LIKE Customer_Name2
3.     REFRENCE TO NON-ELEMENTARY TYPE:
TYPES: T_NAME (25) TYPE C
DATA: CUSTOMER_NAME TYPE T_NAME
               VENDOR_NAME TYPE T_NAME
4.     RECORD-Information in rows & columns.
DATA: BEGIN OF BOOKING,
                                ID (4) TYPE C,
                                FLIGHT_DATE TYPE D,
                                NAME LIKE CUSTOMER_NAME,
                                END OF BOOKING.
You can also look into SAP help for more information.
Regards,
Indu.

Getting (+/-)n th days date from given date

Hi all ,Please help to solve this problem.
Given a date, I need to get date object for the (given date-1) date object ,(given date-2),(given date-3) ....
and also
givendate+1,given date+2 ...
help me out to solve this problem

Check this code out and let me know if it works for you :
public static GregorianCalendar add(GregorianCalendar gc, int _add) {
     gc.add (Calendar.DATE,_add);
     //System.out.println(gc.toString());
     return gc;

Nokia E61i Push Data using XML Cisco Objects?

Hi:
I have a Nokia E61 (wifi) suscribed to a Cisco Call Manager.
Is there any posibility to Push Data to the device?, like XML Cisco Objects to IP Phone 7970.
Could I send an SMS without use the mobile network?
thanks in advance,
marcelo

Thanks for the reply. Yes, I did compile all the Java and it
works OK with a simple Java program. It just will not work in a
Flex application.
The java classes are:
RRA:
package blah.myPackage;
import java.util.List;
import java.util.Collection;
import flex.data.DataSyncException;
import flex.data.assemblers.AbstractAssembler;
class RRA extends AbstractAssembler
public Collection fill( List fillParameters )
RRS service = new RRS();
return service.getSome();
RRS:
package blah.myPackage;
import java.util.ArrayList;
import java.util.List;
import java.sql.*;
import flex.EORS.*;
class RRS
public List getSome()
ArrayList list = new ArrayList();
String str = "bob";
RR rr = new RR(str);
list.add(rr);
return list;
RR:
package blah.myPackage;
class RR
private String name;
public RR() { }
public RR(String name)
this.name = name;
public String getName()
return this.name;
public void setName(String name)
this.name = name;
I started with something that retrieved data from a database
but watered it down just to try and get some kind of communication
between Flex and Java.

Getting contacts updated in sync logs after pushing data for activity object

Hi,
I used below snippet to create Import Definition for Activity Object using Eloqua Bulk 2.0.
    "syncActions": null,
    "isSyncTriggeredOnImport": "true",
    "name": "External Activity via Bulk API",
    "updateRule": "always",
    "secondsToRetainData": "3600",
    "fields": {
        "C_EmailAddress": "{{Activity.Contact.Field(C_EmailAddress)}}",
        "CampaignID": "{{Activity.Campaign.Id}}",
        "AssetName": "{{Activity.Asset.Name}}",
        "AssetType": "{{Activity.Asset.Type}}",
        "AssetDate": "{{Activity.CreatedAt}}",
        "ActivityType": "{{Activity.Type}}"
After pushing data for this import definition, I checked sync logs and I found that there was 2 contacts updated.
Why this happened?
here is my sample data :
        "C_EmailAddress": "[email protected]",
        "CampaignID": 32,
        "AssetName": "Tradeshow",
        "AssetType": "Tradeshow",
        "AssetDate": "2014-05-12",
        "ActivityType": "Visited Booth"
        "C_EmailAddress": "[email protected]",
        "CampaignID": 32,
        "AssetName": "Tradeshow",
        "AssetType": "Tradeshow",
        "AssetDate": "2014-05-12",
       "ActivityType": "Visited Booth"
Please find sync logs in attachment.
thanks

Hi,
I used below snippet to create Import Definition for Activity Object using Eloqua Bulk 2.0.
    "syncActions": null,
    "isSyncTriggeredOnImport": "true",
    "name": "External Activity via Bulk API",
    "updateRule": "always",
    "secondsToRetainData": "3600",
    "fields": {
        "C_EmailAddress": "{{Activity.Contact.Field(C_EmailAddress)}}",
        "CampaignID": "{{Activity.Campaign.Id}}",
        "AssetName": "{{Activity.Asset.Name}}",
        "AssetType": "{{Activity.Asset.Type}}",
        "AssetDate": "{{Activity.CreatedAt}}",
        "ActivityType": "{{Activity.Type}}"
After pushing data for this import definition, I checked sync logs and I found that there was 2 contacts updated.
Why this happened?
here is my sample data :
        "C_EmailAddress": "[email protected]",
        "CampaignID": 32,
        "AssetName": "Tradeshow",
        "AssetType": "Tradeshow",
        "AssetDate": "2014-05-12",
        "ActivityType": "Visited Booth"
        "C_EmailAddress": "[email protected]",
        "CampaignID": 32,
        "AssetName": "Tradeshow",
        "AssetType": "Tradeshow",
        "AssetDate": "2014-05-12",
       "ActivityType": "Visited Booth"
Please find sync logs in attachment.
thanks

Using Date objects in SQL statements

Hi, I am wondering if it is possible to use Date objects while trying to retrieve entries from an access database with fields set as "Date/Time" fields, as opposed to "Text"? If so, do I need to reformat it before inserting it into the SQL statement, or can I just leave it as a Date object, and call up the variable name?
For example - "SELECT * FROM database WHERE startDate = ' " + dateObject + ' ". And do i need quotes round this value?
Thanks in advance.

I had some problems by just fetching a date and pushing it back to a MS SQL Database.
I used the following reformating step to fix it:
if (o instanceof Timestamp)
String time = o.toString().substring(8,10)+"."+o.toString().substring(5,7)+"."+o.toString().substring(0,4)+" "+o.toString().substring(11,19);
ht.put(columnName, time);
o is the object i receve from the select statement and ht is a Hashtable where i put my data.
To write the data back i now can use:
UPDATE table SET columnname = 'valueOfColumn'
This means i use the value i created above in Quotes to write it back.
Format of Timestamp.toString() is something like yyyy-mm-dd hh:mm:ss.xx
Format used by MS SQL (and i think by Access to) 'dd.mm.yyyy hh:mm:ss'

Need to Push data from BI to XI

Hi Experts,
We have a requirement to push data from BI to XI(using Open Hub).
we found some document, in which excute method is selecting from specific open hub table,
we have more than 5 open hub destinations to send data to XI.
do i require to create like this 5 classes or do u have another other method to create one class
and use it for all objects.
this is the sample code, which give hardcoded open hub name.
DATA:
lt_data TYPE zpushdbpush_table_datarow_tab,
ls_data TYPE zpushdbpush_table_datarow,
ls_applid TYPE zpushdbpush_table_process_id,
l_db_line TYPE /bic/ohnwl_oh_xi,
l_db_tab TYPE TABLE OF /bic/ohnwl_oh_xi.
SELECT * FROM /bic/ohnwl_oh_xi INTO TABLE l_db_tab.
LOOP AT l_db_tab INTO l_db_line.
CLEAR ls_data.
MOVE-CORRESPONDING l_db_line TO ls_data.
APPEND ls_data TO lt_data.
ENDLOOP.
Thank You.
Manjula.B

Hi Manjula,
I'm implementing that soluction... Have you?
Now I'm having problem with the code when says:
lt_data TYPE zpushdbpush_table_datarow_tab,
ls_data TYPE zpushdbpush_table_datarow,
ls_applid TYPE zpushdbpush_table_process_id,
So, when activating that code does not generate... The system return error informing that the TYPE zpushdbpush_table_datarow_tab does not exist... can you help me on that?
With ANY kind of information?
Thanks!
Best regards,
Demétrius

Oracle BPM and JMS Queue: How to associate data from Map Messages to Process Data Objects?

Good Day!
I'm currently working on a project wherein it tries to get data from a JMSqueue Map Message being populated by CEP.
After CEP pushes some data in the JMSqueue. I have BPM configured with a JMS adapter to look up whether there are any messages to be processed upon.
Inside BPM, I want to know how can I correlate the data from the Map Message to my Process Data Object.
For example, If I have a Map Object wherein it has 3 attributes:
FirstName:String
LastName:String
Age:int
What is the expression I need to use inside Oracle BPM Data Association screen in order to map the data from the Map Messages into my process data objects?
Thanks!
Regards,
Jeff

Any ideas? Thanks!

Proxy creation/ access key in the how to guide "push data into BW from XI"

Hi !
I'm experiencing troubles with a step of the how to guide "push Data into BW from XI".
When i want to create the proxy in the BW system (step 10), i'm asked for an access key for the object R3TR CLAS CL_<name of the prefix>_<name of message interface>
I think that access keys are needed when an object has to be modified. Do I really have to modify this SAP object ? I don't really feel like destroying the whole system...
Thanks in advance !

Hi Benjamin,
you are not destroying anything in the system. Since you generating a class for the implementation of the proxy within the SAP name space, you are asked for the access key (you can register developers and objects via the OSS).
The system behavior depends on the setting of the system, whether changes are are recorded, etc..
Ask your basis administrator, who should be able to assist you.
Cheers
Andreas

MI 7.1 data objects push data to backend in some sequence

Similar Messages

Maybe you are looking for