Difference in Date Objects - Urgent

How to find out the difference in two date objects?
I have two date values : Start Date and End Date.
I want to user to enter the dates in the range of 10 years gap only.
I need a validation for this.
can any one help me.
Thanks
Meghna

use a gregorian calendar object (java.util.GregorianCalendar). add 10 years to you start date and check if the end date is before the result date.

Similar Messages

Facing lot of problems with the DATA object -- Urgent

Hi,
I am facing lot of problems with the data object in VC.
1. I created the RFC initially and then imported the data object in to VC. Later i did some modifications to RFC Function module,and when i reload the data object, I am not able to see the new changes done to RFC in VC.
2. Even if i delete the function module, after redeploying the IVIew, results are getting displayed.
3. How stable is the VC?
I restarted the sql server and portal connection to R3 is also made afresh.... still i am viewing such surprise results..
please let me know what might be the problem.

Hi Lior,
Are u aware of this problem.
If yes, please let me know...
Thanks,
Manjunatha.T.S

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

Differences between Oracle BAM and Oracle BI and Question BAM Data Objects

Hi,
I have two questions.
1. Can someone tell me differences between Oracle BAM and Oracle BI?
My understanding about Oracle BAM is, we use BAM to build Dashboards or Reports.
We can also build DashBoards or reports using Oracle BI.
I am not able to understand why Oracle has two tools for same purpose?
Which tool is more powerful and user friendly(Oracle BI or Oracle BAM)?
2. Every time we plan to develop Dashboard or report in BAM, we need to create BAM ADC Data Object to store Data (i.e first step is to get data from external database or application and second step is to store data in BAM ADC data object).
My understanding is we have an extra step(i.e creating Data Object) in Oracle BAM to develop a report or DashBoard
I am wrong pl correct me?
Regards,
Shanti Nagulapalli.

Oracle 11g has many advanced features in PL/SQL over Oracle 9i.
refer here,
http://www.oracle.com/technetwork/database/features/manageability/9i-to-11g-real-world-customer-exper-133754.pdf
http://www.oracle.com/global/de/upgradecommunity/artikel/upgrade11gr2_workshop2.pdf
http://www.compuworks.com/events/view/233.pdf
http://education.oracle.com/pls/web_prod-plq-dad/db_pages.getCourseDesc?dc=D52601GC10&p_org_id=15942&lang=US
Thanks

Difference between Service data objects and process data object

Hi
Can anybody tell me what is the difference between SDO (Service Data Objects) & PDO (Process Data Objects).I am using 2 port PCI-CAN series 2 card.
If anybody knows the answer then please reply.
Thanking You

Hi,
See the online help file from our NI CANopen Library for LabVIEW for some basic informations about SDOs and PDOs.
More information should be available from the web.
DirkW
Attachments:
lvcanopenvhelp.zip ‏154 KB

Please tell me the difference between CREATE OBJECT & CREATE DATA ,statements in CRMTECHNICAL

Please tell me the difference between CREATE OBJECT & CREATE DATA ,statements in CRMTECHNICAL

found it on my own . the best way to do this is use the RetriveLimitedHierTreeCommand with a search on the taxonomy table.

What is the difference between data base objects and runtime objects

What is the difference between data base objects and runtime objects

Hi raja,
data base objects means u can have the presence of these objects in the database.So the tables,searchhelps,structures,lockobjects comes under these ones.
Runtime objects are created and destroyed after the program ends, any changes we make to them are temporary only.
regards,
nagaraj
Message was edited by: nagaraj kumar nishtala

Difference Between Data Type and Data Object

Difference Between Data Type and Data Object

hi magesh
Data types can be divided into
elementary,
reference, and
complex types.
Elementary Types
Elementary types are the smallest indivisible unit of types. They can be grouped as those with fixed length and those with variable length.
Fixed-Length Elementary Types
There are eight predefined types in ABAP with fixed length:
Four character types:
Character (C),
Numeric character (N),
Date (D),
and Time (T).
One hexadecimal type:
Byte field (X).
Three numeric types:
Integer (I),
Floating-point number (F)
and Packed number (P).
Variable-Length Elementary Types
There are two predefined types in ABAP with variable length:
STRING for character strings
XSTRING for byte strings
Reference Types
Reference types
describe data objects that contain references (pointers) to other objects (data objects and objects in ABAP Objects).
Data Types
1) As well as occurring as attributes of a data object, data types can also be defined independently.
2)You can then use them later on in conjunction with a data object.
3) The definition of a user-defined data type is based on a set of predefined elementary data types.
4) You can define data types either locally in the declaration part of a program using the TYPESstatement) or globally in the ABAP Dictionary.
5) You can use your own data types to declare data objects or to check the types of parameters in generic operations.
Data Objects
1)Data objects are the physical units with which ABAP statements work at runtime.
2) The contents of a data object occupy memory space in the program.
3) ABAP statements access these contents by addressing the name of the data object and interpret them according to the data type..
4) 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.
5) 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).
6) 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).
7) As well as fields in the memory area of the program, the program also treats literals like data objects.
hope this helps u,
reward points if useful
Ginni

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.

Difference between date info object in characteristics and keyfigure

What is the difference between "date" data type in characteristic and keyfigure?
Thanks in advance.
Raj

Hi Rajasekhar,
If date is characteristics,query can be analysed based on date and filters can also be set using this date.
If it is key figure query cannot be analysed based on date,
Based on requirements,we have to decide whether it should be chatracteristic or key figure
Regards
Prakash

Difference between abap object and function

hi all,
i read the book on abap object of the difference between abap object and classical abap.
i know that there is only 1 instance of a specific function group but somehow i still not so clear why subsequent vehicle cannot use the same function. i also can use the do and loop to call the function? if cannot then why?
hope can get the advice.
thanks
using function *********
function-pool vehicle.
data speed type i value 0.
function accelerate.
speed = speed + 1.
endfunction.
function show_speed.
write speed.
endfunction.
report xx.
start-of-selection.
*vehicle 1
call function 'accelerate'.
call function 'accelerate'.
call function 'show_speed'.
*vehicle 2
*vehicle 3
*****abap object*******
report xx.
data: ov type ref to vehicle,
 ov_tab type table of ref to vehicle.
start-of-selection.
do 5 times.
create object ov.
append ov to ov_tab.
enddo.
loop at ov_tab into ov.
do sy-tabix times.
call method ov->accelerate.
enddo.
call method ov->show_speed.
endloop.

Hi
Now try this:
REPORT ZTEST_VEHICLEOO .
PARAMETERS: P_CAR TYPE I,
 P_READ TYPE I.
* CLASS vehicle DEFINITION
CLASS VEHICLE DEFINITION.
PUBLIC SECTION.
 CLASS-DATA: MAX_SPEED TYPE I,
 MAX_VEHICLE TYPE I,
 NR_VEHICLES TYPE I.
 CLASS-METHODS CLASS_CONSTRUCTOR.
 METHODS CONSTRUCTOR.
 METHODS ACCELERATE.
 METHODS SHOW_SPEED.
 METHODS GET_SPEED EXPORTING E_SPEED TYPE I.
PRIVATE SECTION.
 DATA: SPEED TYPE I,
 NR_VEHICLE TYPE I..
ENDCLASS.
* CLASS vehicle IMPLEMENTATION
CLASS VEHICLE IMPLEMENTATION.
METHOD CLASS_CONSTRUCTOR.
 NR_VEHICLES = 0.
ENDMETHOD.
METHOD CONSTRUCTOR.
 NR_VEHICLES = NR_VEHICLES + 1.
 NR_VEHICLE = NR_VEHICLES.
ENDMETHOD.
METHOD ACCELERATE.
 SPEED = SPEED + 1.
 IF MAX_SPEED < SPEED.
 MAX_SPEED = SPEED.
 MAX_VEHICLE = NR_VEHICLE.
 ENDIF.
ENDMETHOD.
METHOD SHOW_SPEED.
 WRITE: / 'Speed of vehicle nr.', NR_VEHICLE, ':', SPEED.
ENDMETHOD.
METHOD GET_SPEED.
 E_SPEED = SPEED.
ENDMETHOD.
ENDCLASS.
DATA: OV TYPE REF TO VEHICLE,
 OV_TAB TYPE TABLE OF REF TO VEHICLE.
DATA: V_TIMES TYPE I,
 FL_ACTION.
DATA: V_SPEED TYPE I.
START-OF-SELECTION.
DO P_CAR TIMES.
 CREATE OBJECT OV.
 APPEND OV TO OV_TAB.
ENDDO.
LOOP AT OV_TAB INTO OV.
 IF FL_ACTION = SPACE.
 FL_ACTION = 'X'.
 V_TIMES = SY-TABIX * 2.
 ELSE.
 FL_ACTION = SPACE.
 V_TIMES = SY-TABIX - 2.
 ENDIF.
 DO V_TIMES TIMES.
 CALL METHOD OV->ACCELERATE.
 ENDDO.
 CALL METHOD OV->SHOW_SPEED.
ENDLOOP.
SKIP.
WRITE: / 'Higher speed', VEHICLE=>MAX_SPEED, 'for vehicle nr.',
 VEHICLE=>MAX_VEHICLE.
SKIP.
READ TABLE OV_TAB INTO OV INDEX P_READ.
IF SY-SUBRC <> 0.
 WRITE: 'No vehicle', P_READ.
ELSE.
 CALL METHOD OV->GET_SPEED IMPORTING E_SPEED = V_SPEED.
 WRITE: 'Speed of vehicle', P_READ, V_SPEED.
ENDIF.
Try to repeat this using a function group and I think you'll undestand because it'll be very hard to do it.
By only one function group how can u read the data of a certain vehicle?
Yes you can create in the function group an internal table where u store the data of every car: in this way u use the internal table like it was an instance, but you should consider here the example is very simple. Here we have only the speed as characteristic, but really we can have many complex characteristics.
Max

I made a new Date object

See, here's the thing with dates in java, the way i see it. We used to have Date, but Date wasn't international so we got Calendar. But some things, like SimpleDateFormat, still expect java.util.Date. java.sql.Date is out there somewhere, too. None of them have direct support for date differences (i.e. dateA - dateB = 8 days, or whatever). Now you're probably reading this thinking "Java supports all of this" and you're right. Calendar has a getTime method that returns a Date, and i can just pass THAT to SimpleDateFormat. With a little math, getTimeInMillis can be used to find the difference in two Calendars. But i got to thinking, "There should only be one Date object i need to think about," and since i don't ever have enough to do at work i put one together. I don't know if any of you are going to care enough to use it, mostly i'm just looking for advice on features i should add to it, inefficiencies in the design, stuff that's hard to understand, or whatever.
This is it:
*This catastrophe brought to you by SrA Meyerin.
*Proximo Satis pro administatio.
package awesomedate;
//The following are imported for the toFormattedString(), toUtilDate(), toSQLDate, and toCalendar() methods, respectively.
import java.text.SimpleDateFormat;
import java.util.Date;
import java.util.GregorianCalendar;
import java.sql.*;
import java.util.TimeZone;
*This class is designed to be the ultimate date object. It stores dates accurate to the millisecond, has the ability to do date
*arithmetic (adding/subtracting days/months/whatever), date comparison, and date formatting. Also it can, at will, be used as any
*of the other date objects in the standard java API.
public class AwesomeDate
 *Milliseconds from the epoch. This field is where everything starts.
 private long millis;
 * The current year. This is the only aspect of the current date that is stored in addition to the milliseconds. Everything else
 * is calculated as needed.
 private int year;
 //The following six variables are fairly self explanatory. I'll explain them anyway.
 *Milliseconds in one non-leap year. This can be passed to the "adjustDate()" method
 * but mostly it is used to make my code more readable.
 public final static long MILLIS_IN_YEAR = 31536000000L;
 *Milliseconds in one leap year. This can be passed to the "adjustDate()" method
 * but mostly it is used to make my code more readable.
 public static final long MILLIS_IN_LEAP_YEAR = 31622400000L;
 *Milliseconds in one day. This can be passed to the "adjustDate()" method
 * but mostly it is used to make my code more readable.
 public static final long MILLIS_IN_DAY = 86400000;
 *Milliseconds in one hour. This can be passed to the "adjustDate()" method
 * but mostly it is used to make my code more readable.
 public static final long MILLIS_IN_HOUR = 3600000;
 *Milliseconds in one minute. This can be passed to the "adjustDate()" method
 * but mostly it is used to make my code more readable.
 public static final long MILLIS_IN_MINUTE = 60000;
 *Milliseconds in one second. This can be passed to the "adjustDate()" method
 * but mostly it is used to make my code more readable.
 public static final long MILLIS_IN_SECOND = 1000;
 *The number of days in each month.
 private int[] daysInMonth = {31, 28, 31, 30, 31, 30, 31, 31, 30, 31, 30, 31};
 *The timezone offset. GMT is 0, and the default, however, CST (where i live), is -6.
 private int timeZoneOffset = -6;
 *As the name would indicate, this is the number of milliseconds beyond 00:00 of jan 1 of the current year.
 private long millisAfterYear;
 *Basic constructor. Defaults to the current date and time. Works on Greenwich Mean Time, so it may seem off. To avoid this, multiply
 *add your time zone offset * MILLIS_IN_HOUR to the time in milliseconds.
 public AwesomeDate()
 setTimeInMillis(System.currentTimeMillis());
 *Fairly simple constructor. Sets time to the the number of milliseconds passed past the epoch.
 public AwesomeDate(long millis)
 setTimeInMillis(millis);
 *This constructor sets the date to the year/month/day passed.
 public AwesomeDate(int year, int month, int day)
 setDate(year, month, day);
 *This constructor sets the date time to the year/month/day/minute/hour/second passed.
 public AwesomeDate(int year, int month, int day, int hour, int minute, int second)
 setDate(year, month, day, hour, minute, second);
 *When you have the number of milliseconds, the first thing you must calculate is year. Because the number of milliseconds in a
 *year may vary, this is also the most difficult to calculate. This is the method that does it, though.
 private void setYearAfter1970()
 //I don't want to alter the actual number of milliseconds, so i make this variable and perform calculations on it.
 long theseMillis = this.millis;
 //Start at 1970 (the epoch) and work from there.
 year = 1970;
 long nextYear = MILLIS_IN_YEAR;
 //In this loop i subtract the number of millis in whatever year. The condition is if i have enough millis to make it through
 //another year.
 while (theseMillis >= nextYear)
 if (isLeapYear(year))
 theseMillis = theseMillis - MILLIS_IN_LEAP_YEAR;
 nextYear = MILLIS_IN_YEAR;
 else
 theseMillis = theseMillis - MILLIS_IN_YEAR;
 if (isLeapYear(year + 1))
 nextYear = MILLIS_IN_LEAP_YEAR;
 year++;
 millisAfterYear = theseMillis;
 this.year = year;
 *Calculating the year from before 1970 must be done differently. It's pretty much just inverted.
 private void setYearBefore1970()
 long theseMillis = this.millis;
 year = 1970;
 long nextYear = MILLIS_IN_YEAR;
 while (theseMillis <= 0)
 if (isLeapYear(year))
 theseMillis = theseMillis + MILLIS_IN_LEAP_YEAR;
 nextYear = MILLIS_IN_YEAR;
 else
 theseMillis = theseMillis + MILLIS_IN_YEAR;
 if (isLeapYear(year - 1))
 nextYear = MILLIS_IN_LEAP_YEAR;
 year--;
 millisAfterYear = theseMillis * -1;
 this.year = year;
 *Just what it sounds like. Pass it the number of milliseconds past the epoch and it will calculate the date based on that.
 public void setTimeInMillis(long millis)
 this.millis = millis;
 if (millis >= 0)
 setYearAfter1970();
 else
 setYearBefore1970();
 *Returns the number of milliseconds from the epoch.
 public long getTimeInMillis()
 return this.millis;
 *Returns the current year.
 public int getYear()
 return this.year;
 *Sets the date to 00:00 of Jan 1 of the passed year.
 public void setYear(int year)
 this.year = year;
 long theseMillis = 0;
 if (year > 1970)
 //Kind of like setYearAfter1970 method, except it's adding instead of subtracting. So actually it's the opposite.
 for (int cntr = 1970; cntr < this.year; cntr++)
 if (isLeapYear(cntr))
 theseMillis = theseMillis + MILLIS_IN_LEAP_YEAR;
 else
 theseMillis = theseMillis + MILLIS_IN_YEAR;
 else
 for (int cntr = 1970; cntr > this.year; cntr--)
 if (isLeapYear(cntr))
 theseMillis = theseMillis - MILLIS_IN_LEAP_YEAR;
 else
 theseMillis = theseMillis - MILLIS_IN_YEAR;
 //On a leap year there are 29 days in February. If not, there's 28.
 if (isLeapYear(year))
 daysInMonth[1] = 29;
 else
 daysInMonth[1] = 28;
 //This variable helps me calculate denominations of time that are below year.
 millisAfterYear = 0;
 setTimeInMillis(theseMillis);
 *Sets the month to the one that you passed, 0 being January and 11 being December.
 public void setMonth(int month)
 if (month < 0 || month > 11)
 throw new ArrayIndexOutOfBoundsException(month);
 long theseMillis = getTimeInMillis();
 int days = 0;
 setYear(this.year);
 if (getTimeInMillis() > 0)
 theseMillis = theseMillis - getTimeInMillis();
 else
 theseMillis = theseMillis + getTimeInMillis();
 for (int cntr = 0; cntr < month; cntr++)
 days = days + daysInMonth[cntr];
 millisAfterYear = days * MILLIS_IN_DAY + 1;
 setTimeInMillis(getTimeInMillis() + millisAfterYear);
 *Returns the month stored in this object. With this object 0 represents January and 11 represents December.
 public int getMonth()
 long theseMillis = millisAfterYear;
 int cntr = 0;
 while (theseMillis > (MILLIS_IN_DAY * daysInMonth[cntr]))
 theseMillis = theseMillis - MILLIS_IN_DAY * daysInMonth[cntr];
 cntr++;
 return cntr;
 *Set the day of month to the one passed.
 public void setDayOfMonth(int day)
 if (day < 1 || day > daysInMonth[getMonth()])
 throw new ArrayIndexOutOfBoundsException(day);
 setMonth(getMonth());
 //Internally, this actually works starting at zero, however to anyone using this class it appears to start at 1. Therefore
 //i must subtract one here.
 long addMillis = MILLIS_IN_DAY * (day - 1);
 millisAfterYear = millisAfterYear + addMillis;
 setTimeInMillis(getTimeInMillis() + addMillis + 1);
 *Returns the day of month.
 public int getDayOfMonth()
 int days = (int)(millisAfterYear / MILLIS_IN_DAY);
 int cntr = 0;
 while (days >= daysInMonth[cntr])
 days = days - daysInMonth[cntr];
 cntr++;
 //Internally this class stores dates starting at zero, but i want it to look like it starts at 1.
 return days + 1;
 *Sets the time to the currently selected day at the passed hour on the hour. uses 24 hour clock.
 public void setHour(int hour)
 if (hour < 0 || hour > 23)
 throw new ArrayIndexOutOfBoundsException(hour);
 setDayOfMonth(getDayOfMonth());
 long addMillis = MILLIS_IN_HOUR * hour;
 millisAfterYear = millisAfterYear + addMillis;
 setTimeInMillis(getTimeInMillis() + addMillis);
 *Returns the hour (but not how many minutes past the hour).
 public int getHour()
 long millisAfterDay = millisAfterYear % MILLIS_IN_DAY;
 return (int)(millisAfterDay / MILLIS_IN_HOUR);
 *Set the minutes past the hour. Works 0-59.
 public void setMinute(int minute)
 if (minute < 0 || minute > 59)
 throw new ArrayIndexOutOfBoundsException(minute);
 setHour(getHour());
 long addMillis = MILLIS_IN_MINUTE * minute;
 millisAfterYear = millisAfterYear + addMillis;
 setTimeInMillis(getTimeInMillis() + addMillis);
 *Returns the minutes past the hour, 0-59.
 public int getMinute()
 long millisAfterHour = millisAfterYear % MILLIS_IN_HOUR;
 return (int)(millisAfterHour / MILLIS_IN_MINUTE);
 *Sets the seconds past the minute, 0-59.
 public void setSecond(int second)
 if (second < 0 || second > 59)
 throw new ArrayIndexOutOfBoundsException(second);
 setMinute(getMinute());
 long addMillis = MILLIS_IN_SECOND * second;
 millisAfterYear = millisAfterYear + addMillis;
 setTimeInMillis(getTimeInMillis() + addMillis);
 *Returns the seconds past the minute, 0-59.
 public int getSecond()
 long millisAfterMinute = millisAfterYear % MILLIS_IN_MINUTE;
 return (int)(millisAfterMinute / MILLIS_IN_SECOND);
 *The more commonly seen set method of other date objects. Sets the date/time to 00:00 of the year/month/day passed. Convenience method
 *for setDate(int year, int month, int day, int hour, int minute, int second).
 public void setDate(int year, int month, int day)
 setDate(year, month, day, 0 , 0 , 0);
 *Sets every date/time field.
 public void setDate(int year, int month, int day, int hour, int minute, int second)
 setYear(year);
 setMonth(month);
 setDayOfMonth(day);
 setHour(hour);
 setMinute(minute);
 setSecond(second);
 *Returns yes if the stored date is a leap year. A leap year is every year that is divisible by four unless it is divisible by 100
 *unless it is also divisible by 400.
 public boolean isLeapYear()
 return isLeapYear(this.year);
 *For internal use. Returns if the passed year meets the criteria for a leap year.
 private boolean isLeapYear(int year)
 boolean leapYear = false;
 if (year % 4 == 0)
 if (year % 100 != 0)
 leapYear = true;
 else if (year % 400 == 0)
 leapYear = true;
 return leapYear;
 *Returns the difference in milliseconds between the time stored in this object and the millis passed to this method.
 public long getDifferenceInMillis(long millis)
 return getTimeInMillis() - millis;
 *Returns the difference in milliseconds between this date and the date passed to this method.
 public long getDifferenceInMillis(AwesomeDate otherDate)
 return getDifferenceInMillis(otherDate.getTimeInMillis());
 *Designed to be a wrapper method for the getDifferenceInMillis method. This method changes millis into years/days/whatever. Pass
 *the number of milliseconds you have to convert in the first parameter. The second parameter should be the type of denomination you
 *want (year, day, whatever). Use the MILLIS_IN_* fields associated with this object. Also bear in mind when workin with years that
 *some years are leap years, so in extreme cases of differences of 365+ years you may gain/lose a year.
 public static int toGreaterDenom(long millis, long denom)
 return (int)(millis / denom);
 * The first argument is how many of whatever (days, months, years, etc.) to add (use negative numbers to subtract). For the second
 * argument pass one of the MILLIS_IN_* fields. Thus, to add two hours would be
 * <code>
 * AwesomeDate.adjustDate(2, AwesomeDate.MILLIS_IN_HOUR);
 * </code>
 public void adjustDate(int amount, long typeMillis)
 setTimeInMillis(this.millis + amount * typeMillis);
 *Returns an object of type java.util.Date set to the date/time stored here.
 public java.util.Date toUtilDate()
 long offset = TimeZone.getDefault().getRawOffset();
 return new java.util.Date(getTimeInMillis() + -1 * offset);
// return new java.util.Date(getTimeInMillis());
 *Returns an object of type GregorianCalendar set to the date/time stored here.
 public GregorianCalendar toGregorianCalendar()
 long offset = TimeZone.getDefault().getRawOffset();
 GregorianCalendar cal = new GregorianCalendar();
 cal.setTimeInMillis(getTimeInMillis() - offset);
 return cal;
 *Returns an object of type java.sql.Date set to the date/time stored here.
 public java.sql.Date toSQLDate()
 long offset = TimeZone.getDefault().getRawOffset();
 return new java.sql.Date(getTimeInMillis() - offset);
 /** Format the date using the string that you pass. Works just like the SimpleDateFormat object. Infact, it uses one! Heres
 *how it works:
 *Letter Date or Time Component Presentation Examples 
 *G Era designator Text AD 
 *y Year Year 1996; 96 
 *M Month in year Month July; Jul; 07 
 *w Week in year Number 27 
 *W Week in month Number 2 
 *D Day in year Number 189 
 *d Day in month Number 10 
 *F Day of week in month Number 2 
 *E Day in week Text Tuesday; Tue 
 *a Am/pm marker Text PM 
 *H Hour in day (0-23) Number 0 
 *k Hour in day (1-24) Number 24 
 *K Hour in am/pm (0-11) Number 0 
 *h Hour in am/pm (1-12) Number 12 
 *m Minute in hour Number 30 
 *s Second in minute Number 55 
 *S Millisecond Number 978 
 *z Time zone General time zone Pacific Standard Time; PST; GMT-08:00 
 *Z Time zone RFC 822 time zone -0800 
 public String toFormattedString(String format)
 SimpleDateFormat formattage = new SimpleDateFormat(format);
 return formattage.format(toUtilDate());
 *I overrode the toString method. Now it tells everyone how awesome my AwesomeDate is.
 public String toString()
 String output = "John's Awesome Date!";
 output = output + " Millis: " + getTimeInMillis();
 output = output + " Year: " + getYear();
 output = output + " Month: " + getMonth();
 output = output + " Date: " + getDayOfMonth();
 output = output + " Time: ";
 if (getHour() < 10)
 output = output + "0" + getHour();
 else
 output = output + getHour();
 if (getMinute() < 10)
 output = output + "0" + getMinute();
 else
 output = output + getMinute();
 output = output + " Seconds: " + getSecond();
 return output;
 public static void main(String[] psvm)
 AwesomeDate blah = new AwesomeDate();
 GregorianCalendar blah1 = new GregorianCalendar();
 GregorianCalendar blah2 = new GregorianCalendar();
}

The reason Callendar is so complicated is that it is trying to solve a very complicated problem.
You don't appear to support leap seconds (of which there can be upto 2 in any time interval)
http://www.timeanddate.com/time/leapseconds.html
Some of your code will not work for large dates very well (seems to iterate over the years). Try using your date class for astronomical or geological calculations. them big numbers will make your code slow at the moment.
You don't seem to support timezones or transitory offsets (BST vs GMT). You most definately don't handle changes to timezone offsets that have occured in the past or historical daylight savings time offsets (they have not always been the same)
The difference between two calendars is a "duration" a duration means nothing unless it is applied to a caledar/date (although you may be able to get away with it if the duration is always stored in millis)

How to know which master data objects need to activated in R3

SALES OVERVIEW CUBE -0SD_C03
How to know which master data objects need to activated from delivery version to active version in R/3 for a particular standard cube like 0SD_C03.
its very urgent please advise.
R/3 in RSA5
Sales Master Data
0ACCNT_ASGN_TEXT Account assignment group for this customer
0ACCNT_GRP_TEXT Customer account group
0BILBLK_DL_TEXT Locked
0BILBLK_ITM_TEXT Billing block for item
0BILL_BLOCK_TEXT Billing block in SD document
0BILL_CAT_TEXT Billing Category
0BILL_RELEV_TEXT Relevant for Billing
0BILL_RULE_TEXT Billing rule
0BILL_TYPE_TEXT Billing Type
0CONSUMER_ATTR Consumer
0CONSUMER_LKLS_HIER Consumer
0CONSUMER_TEXT Consumer
0CUST_CLASS_TEXT Customer Classification
0CUST_GROUP_TEXT Customer Group
0CUST_GRP1_TEXT Customer Group 1
0CUST_GRP2_TEXT Customer Group 2
0CUST_GRP3_TEXT Customer Group 3
0CUST_GRP4_TEXT Customer Group 4
0CUST_GRP5_TEXT Customer Group 5
0DEALTYPE_TEXT Sales Deal Type
0DEL_BLOCK_TEXT Delivery block (document header)
0DEL_TYPE_TEXT Delivery Type
0DISTR_CHAN_TEXT Distribution Channel
0DIVISION_TEXT Division
0DLV_BLOCK_TEXT Schedule line blocked for delivery
0DOC_CATEG_TEXT SD Document Category
0DOC_TYPE_TEXT Sales Document Type
0INCOTERMS_TEXT Incoterms (Part 1)
0INDUSTRY_TEXT Industry keys
0IND_CODE_3_TEXT Industry code 3
0IND_CODE_4_TEXT Industry code 4
0IND_CODE_5_TEXT Industry code 5
0IND_CODE_TEXT Industry code
0ITEM_CATEG_TEXT Sales document item category
0ITM_TYPE_TEXT FS item type
0KHERK_TEXT Condition Origin
0MATL_GRP_1_TEXT Material Group1
0MATL_GRP_2_TEXT Material Group 2
0MATL_GRP_3_TEXT Material Group 3
0MATL_GRP_4_TEXT Material Group 4
0MATL_GRP_5_TEXT Material Group 5
0MATL_TYPE_TEXT Material Type
0MAT_STGRP_TEXT Material statistics group
0NIELSEN_ID_TEXT Nielsen ID
0ORD_REASON_TEXT Order reason (reason for the business transaction)
0PICK_INDC_TEXT Indicator for picking control
0PRODCAT_TEXT Product Catalog Number
0PROD_HIER_TEXT Product Hierarchy
0PROMOTION_ATTR Promotion
0PROMOTION_TEXT Promotion
0PROMOTYPE_TEXT Promotion Type
0PROV_GROUP_TEXT Commission Group
0REASON_REJ_TEXT Reason for rejection of quotations and sales orders
0REBATE_GRP_TEXT Volume rebate group
0RECIPCNTRY_TEXT Destination country
0ROUTE_TEXT Route
0SALESDEAL_ATTR Sales deal
0SALESDEAL_TEXT Sales deal
0SALESORG_ATTR Sales organization
0SALESORG_TEXT Sales Organization
0SALES_DIST_TEXT Sales district
0SALES_GRP_TEXT Sales Group
0SALES_OFF_TEXT Sales Office
0SCHD_CATEG_TEXT Schedule line category
0SHIP_POINT_TEXT Shipping point/receiving point
In BW
Base Unit of Measure 0BASE_UOM
Bill-to party 0BILLTOPRTY
Calendar Day 0CALDAY
Calendar Year/Month 0CALMONTH
Calendar Year/Week 0CALWEEK
Change Run ID 0CHNGID
Company code 0COMP_CODE
Cost in statistics currency 0COST_VAL_S
Credit/debit posting (C/D) 0DEB_CRED
Distribution Channel 0DISTR_CHAN
Division 0DIVISION
Number of documents 0DOCUMENTS
Sales Document Category 0DOC_CATEG
Document category /Quotation/Order/Delivery/Invoice 0DOC_CLASS
Number of Document Items 0DOC_ITEMS
Fiscal year / period
Fiscal year variant 0FISCVARNT
Gross weight in kilograms 0GR_WT_KG
Number of Employees 0HDCNT_LAST
Material 0MATERIAL
Net value in statistics currency 0NET_VAL_S
Net weight in kilograms 0NT_WT_KG
Open orders quantity in base unit of measure 0OPORDQTYBM
Net value of open orders in statistics currency 0OPORDVALSC
Payer 0PAYER
Plant 0PLANT
Quantity in base units of measure 0QUANT_B
Record type 0RECORDTP
Request ID 0REQUID
Sales Employee 0SALESEMPLY
Sales Organization 0SALESORG
Sales group 0SALES_GRP
Sales Office 0SALES_OFF
Shipping point 0SHIP_POINT
Ship-To Party 0SHIP_TO
Sold-to party 0SOLD_TO
Statistics Currency 0STAT_CURR
In R3 RSA5 we have all the Master data data sources as mentioned above, and BW also. How to find the related Master data Infosource in R/3 Master data Data sources.
Thanks in advance,
 Bhima.
Message was edited by: Bhima Chandra Sekhar Guntla

Hi,
How to know which master data objects need to activated from delivery version to active version in R/3 for a particular standard cube like 0SD_C03.
I think, you are looking for master data sources(text,attributes,hier).Am i right?
If so, This cube has almost all SD master data characterstics. So you can activate all the all master data datasources of SD in r/3 (SD-IO).
Any way you requirement does not stop only by using this cube . You will activate all other cubes in SD also. So if you want to activate only needed master data datasources when you are activating a cube, the job becomes senseless. There is no problem(wrong) in activating all master data available under that application , even though you want to activate only one cube.
With rgds,
Anil Kumar Sharma .P

Error message is 'TYPE' is not a component of data object 'PAYLOAD'.

Hello,
I have sceanrio where file->Synchronus bapi ->File.
For this I have defined a bpm.
Text file inut will be read and converted using sender FCC.
Bpm will call a synchronus bapi from r/3 and collect response. I need to create a success or error response file from the status of bapi response. I have used switch step to do that.
But here when I give condtion as this XPath SOResonse./p1:Z_BAPI_SALESORDER_CREATEFROM3.Response/RETURN1/TYPE = S, SXI_CACHE gives status of bpm as 99 and error message is 'TYPE' is not a component of data object 'PAYLOAD'.
At the same time if i just put a condition of simple type container variable (SuccessCounter = 0), it gives status 0 in SXI_CACHE.
Pl can anyone suggest on this as its urgent.
thanks in advance,
Sharada

Thanks for quick response.
Yes BAPI response has TYPE field.
Pl cehck this response xml
<?xml version="1.0" encoding="UTF-8" ?>
- <rfc:Z_BAPI_SALESORDER_CREATEFROM3.Response xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
- <RETURN1>
<TYPE>E</TYPE>
<ID>V4</ID>
<NUMBER>115</NUMBER>
<MESSAGE>Purchase order number in document number: 304928 already exists</MESSAGE>
<LOG_NO />
<LOG_MSG_NO>000000</LOG_MSG_NO>
<MESSAGE_V1>304928</MESSAGE_V1>
<MESSAGE_V2 />
<MESSAGE_V3 />
<MESSAGE_V4 />
<PARAMETER>SALES_HEADER_IN</PARAMETER>
<ROW>0</ROW>
<FIELD />
<SYSTEM>DEV200</SYSTEM>
</RETURN1>
<SALESDOCUMENT />
- <EXTENSIONIN>
- <item>
<STRUCTURE>BAPE_VBAK</STRUCTURE>
<VALUEPART1>X</VALUEPART1>
<VALUEPART2 />
<VALUEPART3 />
<VALUEPART4 />
</item>
</EXTENSIONIN>
<ORDER_CCARD />
<ORDER_CFGS_BLOB />
<ORDER_CFGS_INST />
<ORDER_CFGS_PART_OF />
<ORDER_CFGS_REF />
<ORDER_CFGS_REFINST />
<ORDER_CFGS_VALUE />
<ORDER_CFGS_VK />
<ORDER_CONDITIONS_IN />
<ORDER_CONDITIONS_INX />
<ORDER_ITEMS_IN />
<ORDER_ITEMS_INX />
- <ORDER_KEYS>
- <item>
<REFOBJTYP />
<REFOBJECT>HEADER</REFOBJECT>
<REFOBJKEY />
<REFLOGSYS />
<DOC_NUMBER />
<ITM_NUMBER>000000</ITM_NUMBER>
<SCHED_LIN>0000</SCHED_LIN>
<COND_NO />
<CONDITEMNO>000000</CONDITEMNO>
<COND_ST_NO>000</COND_ST_NO>
<COND_COUNT>00</COND_COUNT>
<COND_TYPE />
<STATUS />
<TINDEX>000000</TINDEX>
<ADDRESS />
<ABRLI>0000</ABRLI>
<ABART />
</item>
- <item>
<REFOBJTYP />
<REFOBJECT>ADDRESS</REFOBJECT>
<REFOBJKEY />
<REFLOGSYS />
<DOC_NUMBER />
<ITM_NUMBER>000000</ITM_NUMBER>
<SCHED_LIN>0000</SCHED_LIN>
<COND_NO />
<CONDITEMNO>000000</CONDITEMNO>
<COND_ST_NO>000</COND_ST_NO>
<COND_COUNT>00</COND_COUNT>
<COND_TYPE />
<STATUS />
<TINDEX>000001</TINDEX>
<ADDRESS />
<ABRLI>0000</ABRLI>
<ABART />
</item>
- <item>
<REFOBJTYP />
<REFOBJECT>ADDRESS</REFOBJECT>
<REFOBJKEY />
<REFLOGSYS />
<DOC_NUMBER />
<ITM_NUMBER>000000</ITM_NUMBER>
<SCHED_LIN>0000</SCHED_LIN>
<COND_NO />
<CONDITEMNO>000000</CONDITEMNO>
<COND_ST_NO>000</COND_ST_NO>
<COND_COUNT>00</COND_COUNT>
<COND_TYPE />
<STATUS />
<TINDEX>000002</TINDEX>
<ADDRESS />
<ABRLI>0000</ABRLI>
<ABART />
</item>
- <item>
<REFOBJTYP />
<REFOBJECT>ADDRESS</REFOBJECT>
<REFOBJKEY />
<REFLOGSYS />
<DOC_NUMBER />
<ITM_NUMBER>000000</ITM_NUMBER>
<SCHED_LIN>0000</SCHED_LIN>
<COND_NO />
<CONDITEMNO>000000</CONDITEMNO>
<COND_ST_NO>000</COND_ST_NO>
<COND_COUNT>00</COND_COUNT>
<COND_TYPE />
<STATUS />
<TINDEX>000003</TINDEX>
<ADDRESS />
<ABRLI>0000</ABRLI>
<ABART />
</item>
- <item>
<REFOBJTYP />
<REFOBJECT>ADDRESS</REFOBJECT>
<REFOBJKEY />
<REFLOGSYS />
<DOC_NUMBER />
<ITM_NUMBER>000000</ITM_NUMBER>
<SCHED_LIN>0000</SCHED_LIN>
<COND_NO />
<CONDITEMNO>000000</CONDITEMNO>
<COND_ST_NO>000</COND_ST_NO>
<COND_COUNT>00</COND_COUNT>
<COND_TYPE />
<STATUS />
<TINDEX>000004</TINDEX>
<ADDRESS />
<ABRLI>0000</ABRLI>
<ABART />
</item>
</ORDER_KEYS>
- <ORDER_PARTNERS>
- <item>
<PARTN_ROLE>RE</PARTN_ROLE>
<PARTN_NUMB>LS-RETAIL</PARTN_NUMB>
<ITM_NUMBER>000000</ITM_NUMBER>
<TITLE />
<NAME />
<NAME_2 />
<NAME_3 />
<NAME_4 />
<STREET />
<COUNTRY />
<COUNTR_ISO />
<POSTL_CODE />
<POBX_PCD />
<POBX_CTY />
<CITY />
<DISTRICT />
<REGION />
<PO_BOX />
<TELEPHONE />
<TELEPHONE2 />
<TELEBOX />
<FAX_NUMBER />
<TELETEX_NO />
<TELEX_NO />
<LANGU />
<LANGU_ISO />
<UNLOAD_PT />
<TRANSPZONE />
<TAXJURCODE />
<ADDRESS />
<PRIV_ADDR />
<ADDR_TYPE />
<ADDR_ORIG />
<ADDR_LINK>0001</ADDR_LINK>
<REFOBJTYPE />
<REFOBJKEY />
<REFLOGSYS />
</item>
- <item>
<PARTN_ROLE>WE</PARTN_ROLE>
<PARTN_NUMB>LS-RETAIL</PARTN_NUMB>
<ITM_NUMBER>000000</ITM_NUMBER>
<TITLE />
<NAME />
<NAME_2 />
<NAME_3 />
<NAME_4 />
<STREET />
<COUNTRY />
<COUNTR_ISO />
<POSTL_CODE />
<POBX_PCD />
<POBX_CTY />
<CITY />
<DISTRICT />
<REGION />
<PO_BOX />
<TELEPHONE />
<TELEPHONE2 />
<TELEBOX />
<FAX_NUMBER />
<TELETEX_NO />
<TELEX_NO />
<LANGU />
<LANGU_ISO />
<UNLOAD_PT />
<TRANSPZONE />
<TAXJURCODE />
<ADDRESS />
<PRIV_ADDR />
<ADDR_TYPE />
<ADDR_ORIG />
<ADDR_LINK>0002</ADDR_LINK>
<REFOBJTYPE />
<REFOBJKEY />
<REFLOGSYS />
</item>
- <item>
<PARTN_ROLE>Z1</PARTN_ROLE>
<PARTN_NUMB>LS-RETAIL</PARTN_NUMB>
<ITM_NUMBER>000000</ITM_NUMBER>
<TITLE />
<NAME />
<NAME_2 />
<NAME_3 />
<NAME_4 />
<STREET />
<COUNTRY />
<COUNTR_ISO />
<POSTL_CODE />
<POBX_PCD />
<POBX_CTY />
<CITY />
<DISTRICT />
<REGION />
<PO_BOX />
<TELEPHONE />
<TELEPHONE2 />
<TELEBOX />
<FAX_NUMBER />
<TELETEX_NO />
<TELEX_NO />
<LANGU />
<LANGU_ISO />
<UNLOAD_PT />
<TRANSPZONE />
<TAXJURCODE />
<ADDRESS />
<PRIV_ADDR />
<ADDR_TYPE />
<ADDR_ORIG />
<ADDR_LINK>0003</ADDR_LINK>
<REFOBJTYPE />
<REFOBJKEY />
<REFLOGSYS />
</item>
- <item>
<PARTN_ROLE>AG</PARTN_ROLE>
<PARTN_NUMB>LS-RETAIL</PARTN_NUMB>
<ITM_NUMBER>000000</ITM_NUMBER>
<TITLE />
<NAME />
<NAME_2 />
<NAME_3 />
<NAME_4 />
<STREET />
<COUNTRY />
<COUNTR_ISO />
<POSTL_CODE />
<POBX_PCD />
<POBX_CTY />
<CITY />
<DISTRICT />
<REGION />
<PO_BOX />
<TELEPHONE />
<TELEPHONE2 />
<TELEBOX />
<FAX_NUMBER />
<TELETEX_NO />
<TELEX_NO />
<LANGU />
<LANGU_ISO />
<UNLOAD_PT />
<TRANSPZONE />
<TAXJURCODE />
<ADDRESS />
<PRIV_ADDR />
<ADDR_TYPE />
<ADDR_ORIG />
<ADDR_LINK />
<REFOBJTYPE />
<REFOBJKEY />
<REFLOGSYS />
</item>
</ORDER_PARTNERS>
<ORDER_SCHEDULES_IN />
<ORDER_SCHEDULES_INX />
- <ORDER_TEXT>
- <item>
<DOC_NUMBER />
<ITM_NUMBER>000020</ITM_NUMBER>
<TEXT_ID>Z001</TEXT_ID>
<LANGU>E</LANGU>
<LANGU_ISO />
<FORMAT_COL />
<TEXT_LINE />
<FUNCTION />
</item>
- <item>
<DOC_NUMBER />
<ITM_NUMBER>000030</ITM_NUMBER>
<TEXT_ID>Z001</TEXT_ID>
<LANGU>E</LANGU>
<LANGU_ISO />
<FORMAT_COL />
<TEXT_LINE />
<FUNCTION />
</item>
- <item>
<DOC_NUMBER />
<ITM_NUMBER>000040</ITM_NUMBER>
<TEXT_ID>Z001</TEXT_ID>
<LANGU>E</LANGU>
<LANGU_ISO />
<FORMAT_COL />
<TEXT_LINE />
<FUNCTION />
</item>
- <item>
<DOC_NUMBER />
<ITM_NUMBER>000050</ITM_NUMBER>
<TEXT_ID>Z001</TEXT_ID>
<LANGU>E</LANGU>
<LANGU_ISO />
<FORMAT_COL />
<TEXT_LINE />
<FUNCTION />
</item>
- <item>
<DOC_NUMBER />
<ITM_NUMBER>000020</ITM_NUMBER>
<TEXT_ID>Z001</TEXT_ID>
<LANGU>E</LANGU>
<LANGU_ISO />
<FORMAT_COL />
<TEXT_LINE />
<FUNCTION />
</item>
- <item>
<DOC_NUMBER />
<ITM_NUMBER>000030</ITM_NUMBER>
<TEXT_ID>Z001</TEXT_ID>
<LANGU>E</LANGU>
<LANGU_ISO />
<FORMAT_COL />
<TEXT_LINE />
<FUNCTION />
</item>
- <item>
<DOC_NUMBER />
<ITM_NUMBER>000040</ITM_NUMBER>
<TEXT_ID>Z001</TEXT_ID>
<LANGU>E</LANGU>
<LANGU_ISO />
<FORMAT_COL />
<TEXT_LINE />
<FUNCTION />
</item>
- <item>
<DOC_NUMBER />
<ITM_NUMBER>000050</ITM_NUMBER>
<TEXT_ID>Z001</TEXT_ID>
<LANGU>E</LANGU>
<LANGU_ISO />
<FORMAT_COL />
<TEXT_LINE />
<FUNCTION />
</item>
</ORDER_TEXT>
- <PARTNERADDRESSES>
- <item>
<ADDR_NO>0001</ADDR_NO>
<FORMOFADDR />
<NAME />
<NAME_2 />
<NAME_3 />
<NAME_4 />
<C_O_NAME />
<CITY />
<DISTRICT />
<CITY_NO />
<POSTL_COD1 />
<POSTL_COD2 />
<POSTL_COD3 />
<PO_BOX />
<PO_BOX_CIT />
<DELIV_DIS />
<STREET />
<STREET_NO />
<STR_ABBR />
<HOUSE_NO />
<STR_SUPPL1 />
<STR_SUPPL2 />
<LOCATION />
<BUILDING />
<FLOOR />
<ROOM_NO />
<COUNTRY />
<LANGU />
<REGION />
<SORT1 />
<SORT2 />
<TIME_ZONE />
<TAXJURCODE />
<ADR_NOTES />
<COMM_TYPE />
<TEL1_NUMBR />
<TEL1_EXT />
<FAX_NUMBER />
<FAX_EXTENS />
<STREET_LNG />
<DISTRCT_NO />
<CHCKSTATUS />
<PBOXCIT_NO />
<TRANSPZONE />
<HOUSE_NO2 />
<E_MAIL />
<STR_SUPPL3 />
<TITLE />
<COUNTRYISO />
<LANGU_ISO />
<BUILD_LONG />
<REGIOGROUP />
<HOME_CITY />
<HOMECITYNO />
<PCODE1_EXT />
<PCODE2_EXT />
<PCODE3_EXT />
<PO_W_O_NO />
<PO_BOX_REG />
<POBOX_CTRY />
<PO_CTRYISO />
<HOMEPAGE />
<DONT_USE_S />
<DONT_USE_P />
<HOUSE_NO3 />
<LANGU_CR />
<LANGUCRISO />
</item>
- <item>
<ADDR_NO>0002</ADDR_NO>
<FORMOFADDR />
<NAME>SUPERIOR SELECTED STONE</NAME>
<NAME_2 />
<NAME_3>33-53 10TH STREET</NAME_3>
<NAME_4 />
<C_O_NAME />
<CITY />
<DISTRICT />
<CITY_NO />
<POSTL_COD1 />
<POSTL_COD2 />
<POSTL_COD3 />
<PO_BOX />
<PO_BOX_CIT />
<DELIV_DIS />
<STREET />
<STREET_NO />
<STR_ABBR />
<HOUSE_NO />
<STR_SUPPL1 />
<STR_SUPPL2 />
<LOCATION />
<BUILDING />
<FLOOR />
<ROOM_NO />
<COUNTRY />
<LANGU />
<REGION />
<SORT1 />
<SORT2 />
<TIME_ZONE />
<TAXJURCODE />
<ADR_NOTES />
<COMM_TYPE />
<TEL1_NUMBR />
<TEL1_EXT />
<FAX_NUMBER />
<FAX_EXTENS />
<STREET_LNG />
<DISTRCT_NO />
<CHCKSTATUS />
<PBOXCIT_NO />
<TRANSPZONE />
<HOUSE_NO2 />
<E_MAIL />
<STR_SUPPL3 />
<TITLE />
<COUNTRYISO />
<LANGU_ISO />
<BUILD_LONG />
<REGIOGROUP />
<HOME_CITY />
<HOMECITYNO />
<PCODE1_EXT />
<PCODE2_EXT />
<PCODE3_EXT />
<PO_W_O_NO />
<PO_BOX_REG />
<POBOX_CTRY />
<PO_CTRYISO />
<HOMEPAGE />
<DONT_USE_S />
<DONT_USE_P />
<HOUSE_NO3 />
<LANGU_CR />
<LANGUCRISO />
</item>
- <item>
<ADDR_NO>0003</ADDR_NO>
<FORMOFADDR />
<NAME>Langenscheidt Publishers Inc.</NAME>
<NAME_2 />
<NAME_3 />
<NAME_4 />
<C_O_NAME />
<CITY />
<DISTRICT />
<CITY_NO />
<POSTL_COD1 />
<POSTL_COD2 />
<POSTL_COD3 />
<PO_BOX />
<PO_BOX_CIT />
<DELIV_DIS />
<STREET />
<STREET_NO />
<STR_ABBR />
<HOUSE_NO />
<STR_SUPPL1 />
<STR_SUPPL2 />
<LOCATION />
<BUILDING />
<FLOOR />
<ROOM_NO />
<COUNTRY />
<LANGU />
<REGION />
<SORT1 />
<SORT2 />
<TIME_ZONE />
<TAXJURCODE />
<ADR_NOTES />
<COMM_TYPE />
<TEL1_NUMBR />
<TEL1_EXT />
<FAX_NUMBER />
<FAX_EXTENS />
<STREET_LNG />
<DISTRCT_NO />
<CHCKSTATUS />
<PBOXCIT_NO />
<TRANSPZONE />
<HOUSE_NO2 />
<E_MAIL />
<STR_SUPPL3 />
<TITLE />
<COUNTRYISO />
<LANGU_ISO />
<BUILD_LONG />
<REGIOGROUP />
<HOME_CITY />
<HOMECITYNO />
<PCODE1_EXT />
<PCODE2_EXT />
<PCODE3_EXT />
<PO_W_O_NO />
<PO_BOX_REG />
<POBOX_CTRY />
<PO_CTRYISO />
<HOMEPAGE />
<DONT_USE_S />
<DONT_USE_P />
<HOUSE_NO3 />
<LANGU_CR />
<LANGUCRISO />
</item>
</PARTNERADDRESSES>
- <RETURN>
- <item>
<TYPE>E</TYPE>
<ID>V4</ID>
<NUMBER>115</NUMBER>
<MESSAGE>Purchase order number in document number: 304928 already exists</MESSAGE>
<LOG_NO />
<LOG_MSG_NO>000000</LOG_MSG_NO>
<MESSAGE_V1>304928</MESSAGE_V1>
<MESSAGE_V2 />
<MESSAGE_V3 />
<MESSAGE_V4 />
<PARAMETER>SALES_HEADER_IN</PARAMETER>
<ROW>0</ROW>
<FIELD />
<SYSTEM>DEV200</SYSTEM>
</item>
- <item>
<TYPE>E</TYPE>
<ID>V4</ID>
<NUMBER>219</NUMBER>
<MESSAGE>Sales document was not changed</MESSAGE>
<LOG_NO />
<LOG_MSG_NO>000000</LOG_MSG_NO>
<MESSAGE_V1 />
<MESSAGE_V2 />
<MESSAGE_V3 />
<MESSAGE_V4 />
<PARAMETER />
<ROW>0</ROW>
<FIELD />
<SYSTEM>DEV200</SYSTEM>
</item>
</RETURN>
</rfc:Z_BAPI_SALESORDER_CREATEFROM3.Response>

Binding a shared variable to a NI-PSP data object does not work

Hi,
I want to share data between a RT-target and one or more hosts (LV 8.6.1). The network shared variables are deployed to the RT-Target. According to NI accessing shared variables from another project or host has to be done by defining a shared variable on the host and aliasing it to the NI-PSP data object on the target.
I did that and the host shared variable generated an error (0x8BBB0011) during runtime.
Next I aliased to a shared variable deployed on the host from another project. This did work.
Another thing I tried was to bind the variable from the RT-target to a display element:
This is working !!! And as you can see the path of the NI-PSP data object is exactly the same ! So what is the difference between binding a data object to a shared variable and to a display element?
Is there a bug in the SVE or am I missing something here?
The host project:
The publisher VI
Hope, someone has an answer.
Regards
Matthias Quade
Solved!
Go to Solution.
Attachments:
AliasTestWrite-RT.vi ‏8 KB
AliasTestConsumer.vi ‏8 KB

Dear Mr. Quade,
thank you for posting at the National Instruments Forum. There is a known issue with the path of the bound variable with LabVIEW 8.6.1
Please download the patch for LabVIEW 8.6.1, it should solve your problem:
http://joule.ni.com/nidu/cds/view/p/id/1255/lang/de
Best regards from Munich
MarianO

Difference in Date Objects - Urgent

Similar Messages

Maybe you are looking for