Callback routines and data

Hi -
Still very new to CVI here.
I'm designing a small application that will accept data from various sources (file, socket) and plot the data on a graph. I read in the online help how the variable
void *callbackdata
can be used to avoid the need for global variables. But I don't fully understand this -- since the program isn't directly calling these callback routines, how does it specify/access the data location here?
Maybe if someone would be kind enough to provide a brief example, the light would come on for me. Thanks.
Solved!
Go to Solution.

When designing your application you must decide whether your data array (or data structure, as you have supposed) is defined at a global or function level. If it is global to the whole app you have no need to struggle about how to pass data between functions, but if it is defined at function level (e.g. in the main function) every other function that must handle data must be informed of it. The button callback that is in charge of filing the data structure can receive its pointer in callbackData, the only parameter the programmer can freely use, while user defined functions (like your display_data function) can receive it directly as a parameter.
To protect your data structure from concurrent access to it you can for example define a 'busy' flag inside the structure itself: every time you want to modify data you must verify that busy flag is not set and set it as the fist thing if free. Alternatively you can use locks from the utility library calling CmtGetLock or CmtTryToGetLock to verify that data structure is free or locked.
Proud to use LW/CVI from 3.1 on.
My contributions to the Developer Zone Community
If I have helped you, why not giving me a kudos?

Similar Messages

How to call routine and pass data to routine in vofm

Hi Experts,
I need to update KBETR and KWERT values present in 'Conditions Tab' in Purchase Order (ME21N/ME22N).
I have created a new customer tab in which we enter amount field and percentage filed. When user enters some value in this and clicks on 'Conditions Tab', calculation has to be done and the calculated value has to be appeared across a specific condition type.as i am new to abap i dont know how to create routine and pass data to routine in vofm from customised tab in me21n .
Thank's in advance

Hello Rajendra,
You can get plenty of forums in SCN related to it. Follow below steps to create VOFM routine.
Go to VOFM Transaction Code
1. On the Menu Select required Application i.e Pricing
2. Enter any Number in between 600 to 999 for Custom Developments.
3. On entering Pop Screen appears ask for Access Key(We have to remember that Every New Routine needs an Access Key)
4. Once the Access Key is received we can do modification.
5. Enter the Routine Number ,description and insert the Access Key
6. Now the ABAP Editor will open and required code can be copied from Standard SAP Routine and Custom Code Can be developed.
7. Once the coding is completed we have to Activate the Routine
8. Select the Routine and Go to Edit – Activate
9. Ensure that Active check box is ticked upon Activation of the Routine.
10. Double click on the routine will enter into ABAP Editor, we have to generate the Routine
11. Go to Program and select Generate
12.A screen pops up with the related Main Programs and select all required main programs wherever the Routine is being called.
13. Once the Routine is Generated and Activated, We need to configure the Routine in the config.
** Important SAP note: 156230.
Check the below document too.
http://www.scribd.com/doc/35056841/How-to-create-Requirement-Routines
Regards,
Thanga

Difference between Start Routine and End Routine in Transformations

Hi Friends,
I'm using BI 7.0... here in Transformations step we have two options..that is START ROUTINE... and END ROUTINE... What is the Difference between Start Routine and End Routine in Transformations..
When we go for Start Routine.. and when we go for End Routine..
Plz clarrify... points will be rearded..
thanks
babu

Hi,
One real time scenario for End Routine.
We have a scenario where in a datasource field is mapped to three infoobjects on the datatarget side. There are 2 key figures which need to get data after these these Infoobjects are filled. The best place for this to happen would be in a End Routine, where in we would loop through the results package and using the values of the infoobjects from the data target ( Cube in this case).
Hope this helps,
HD

Qty and Date Variance using Purchasing InfoCube

Using Purchasing Cube, I want to find out the Qty Variance and Date variance,
Iu2019m calculating these using GR Posting date and Requested Delivery Date and GR Qty and Qty in UoM.
Iu2019ve the following doubts:
1.     In order to calculate the Variance, do we need to filter the data pertaining to any particular BW Transaction Key (0PROCESSKEY) since we donu2019t want Goods Issues (can be Purchase Returns or intra company Stock Transfers ), If so what are the values for the Process Key to be considered for filter.
2.     Though the Qty key figure matches the Requested Qty, the PO status is u2018Openu2019. What could be the possible reasons?
3.     The qty. and days variance for the POs already received can be calculated. But what should be done incase of POs for which Goods are not yet received? Again in that scenario, we can have two cases: Delivery Past Due and Delivery Date in Future. How to tackle these 2 cases. As per our Requirement, we have to calculate the difference between System date and Requested Delivery Date incase of Past Delivery Date so that we can have the variance as of System Date. Like If the Delivery Date is 25th Nov, if we run the Query on 28th, it should show 3 days late and if run on 29th, it has to be 4 days if still undelivered. Please give me the code to be written in Transformations.
We have not yet decided what has to be done in the second case i.e. Future Delivery Date. Please guide me what is the best option in that case.
Thanks,
Aryaman

Hi,
1. In order to calculate the Variance, do we need to filter the data pertaining to any particular BW Transaction Key (0PROCESSKEY) since we donu2019t want Goods Issues (can be Purchase Returns or intra company Stock Transfers ), If so what are the values for the Process Key to be considered for filter.
You need to add Z-Keyfigures and then write Routines based on Process Keys in Update Rules/Transformations and filter the required Process Keys, you need to find required Process Keys in ECC, SPRO-->Reference IMG an dthen search for BW Transactional Key and see it disuss with MM FUnctional COnsultant and Identify it.
2. Though the Qty key figure matches the Requested Qty, the PO status is u2018Openu2019. What could be the possible reasons?
I faced the problem with 2LIS_02_* datasources so I created new generic data source and used it. Just take only one record with that you track in ECC. You must take MM Consultants help, they will guide you.
3. The qty. and days variance for the POs already received can be calculated. But what should be done incase of POs for which Goods are not yet received? Again in that scenario, we can have two cases: Delivery Past Due and Delivery Date in Future. How to tackle these 2 cases. As per our Requirement, we have to calculate the difference between System date and Requested Delivery Date incase of Past Delivery Date so that we can have the variance as of System Date. Like If the Delivery Date is 25th Nov, if we run the Query on 28th, it should show 3 days late and if run on 29th, it has to be 4 days if still undelivered. Please give me the code to be written in Transformations.
We have not yet decided what has to be done in the second case i.e. Future Delivery Date. Please guide me what is the best option in that case.
Once you have Qty and Dates from Transactional Data then it is easy to calculate the Date Varience and Qty varience, see the follwoing URL it is having one article How to Calculate Meterial Aging whcih will give how to calculate the differnce..
http://wiki.sdn.sap.com/wiki/display/profile/Surendra+Reddy
Thanks
Reddy

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

BW 3.5 Update rule routine and start routine convert to BI 7.0 Endroutine.

I have bw 3.5 update routine and update rules start routine( r/3 to ODS). i need to replicate that routine into BI 7.0 endroutine with the same logic with some minor changes(DSO to DSO).
IN BW 3.5 the data is getting from r/3 where as in BI7.0 the data fetching from DSO itself but the logic is same as bw 3.5.
following is the start routine:
DATA: G_FISCPER_TO TYPE /BI0/OIFISCPER,
      G_CALMONTH   LIKE /BI0/PCALMONTH-CALMONTH,
      G_MONAT      TYPE /BIC/OIYRDFMONAT.
ABORT = 0.
------ Globale Variable füllen --------------------------------------*
CALL FUNCTION 'Y_RDF_FISCPER_FOR_INFOPACKAGE'
    EXPORTING
      I_ISOURCE    = '0FI_AA_001' (*** this is infosurce getting from r/3, in 7.0 this one is DSO 'B")
    IMPORTING
      E_FISCPER_TO = G_FISCPER_TO
      E_MONAT      = G_MONAT
    EXCEPTIONS
      OTHERS       = 1.
IF SY-SUBRC = 0.
    CALL FUNCTION 'Y_RDE_FISCPER_TO_CALMONTH'
      EXPORTING
        I_PERIV    = 'K4'
        I_BDATJ    = G_FISCPER_TO(4)
        I_POPER    = G_FISCPER_TO+4(3)
      IMPORTING
        E_CALMONTH = G_CALMONTH
      EXCEPTIONS
        OTHERS     = 1.
    IF SY-SUBRC NE 0 OR G_CALMONTH IS INITIAL.
      CALL FUNCTION 'Y_RDN_MONITOR_SET'
        EXPORTING
          I_MSGID   = 'YRDFBW'
          I_MSGNO   = '027'
          I_MSGV1   = '0FI_AA_001'
          I_MSGV2   = 'YRDF_FIAA_PERIOD'
        TABLES
          T_MONITOR = MONITOR.
      ABORT = 1.
    ENDIF.
ELSE.
    CALL FUNCTION 'Y_RDN_MONITOR_SET'
      EXPORTING
        I_MSGID   = 'YRDFBW'
        I_MSGNO   = '027'
        I_MSGV1   = '0FI_AA_001'
        I_MSGV2   = 'YRDF_FIAA_PERIOD'
      TABLES
        T_MONITOR = MONITOR.
    ABORT = 1.
ENDIF.
Update routine:
RETURNCODE = 0.
ABORT = 0.
CLEAR RESULT.
IF NOT COMM_STRUCTURE-ASSET_MAIN BETWEEN '000000200000' AND
                                           '000000299999'.
    CALL FUNCTION 'Y_RDF_GET_CCTR_0ASSET'
      EXPORTING
        I_COMP_CODE = COMM_STRUCTURE-COMP_CODE
        I_ASSET      = COMM_STRUCTURE-ASSET
        I_ASSET_MAIN = COMM_STRUCTURE-ASSET_MAIN
      IMPORTING
        E_COSTCENTER = RESULT
      EXCEPTIONS
        OTHERS       = 1.
    IF SY-SUBRC NE 0 OR RESULT IS INITIAL.
      CALL FUNCTION 'Y_RDN_MONITOR_SET'
        EXPORTING
          I_MSGID   = 'YRDFBW'
          I_MSGTY   = 'E'
          I_MSGNO   = '061'
          I_MSGV1   = COMM_STRUCTURE-COMP_CODE
          I_MSGV2   = COMM_STRUCTURE-ASSET
          I_MSGV3   = COMM_STRUCTURE-ASSET_MAIN
        TABLES
          T_MONITOR = MONITOR.
      RETURNCODE = 1.
    ENDIF.
ENDIF.
How can i write this in BI7.0?
Thanks

Hi ,
solved on my own. Thankyou very much..
thanks & regards,
M.S
Edited by: M.S on Oct 27, 2009 6:57 AM
Edited by: M.S on Oct 27, 2009 6:59 AM

Routine in data selection tab

hi friends,
i need to write routine in data selection tab , i need like when ever i open need to show current data.
how can i write coding.
i have code like this, please correct my code
L_t_RANGE_IOBJNM = '0CALDAY'.
L_t_RANGE-FIELD NAME = 'CALDAY'.
L_t_RANGE-SIGN = 'I'.
L_t_RANGE-OPTION = 'EQ'.
L_t_RANGE-LOW = sy-datum .
I DIDNT UNDERSTAND HERE WHAT IS ACTUALLY IOBJNM WHAT DO U MEAN BY LOW AND HIGH ACTUALLY. FIELD NAME MEANS I NEED TO MENTION LIKE/BIC/ZMNO LIKE .
THANKING U,
SUNEEL.

Check below link to understand the RANGE type objects in ABAP. The OBJNAM is the object name which is used for selection in the InfoPackage. l_t_range is the internal table which contains all the selections used in the InfoPackage. So, if you need dynamic selections you have to code to populate dynamic values for the corresponding InfoObject in this Internal table. Low/High are the fields which actually contains the "From" and "to" range in selection.
Option - <,>,=, <> etc.
Sign -Include/Exclude (I/E)
http://help.sap.com/saphelp_nw2004s/helpdata/en/9f/dba71f35c111d1829f0000e829fbfe/content.htm
Regards,
Sree

Abap Routine for Date selection in Infopackage

Hi
I have to write an abap routine for date selections in the infopackage,
There are two date begda and enda.
Do i code for BEGDA and fill in the begin date using routine and use another routine to fill the ENDA.
JPJP

Hi JP,
If you have two info objects BEGDA and ENDA in the Info package for selection
then you will have to write seperate routine for each of them.
If you want to give single value for each date field then update only the field l_t_range- low otherwise if you want to give range then you can update the internal table fields l_t_range-low and l_t_range-high .
Regards,
Prakash

How to view "date from" and "date to"

Hi,
I have loaded EMP data. In the mapping "date from" and "date to" are visible. But these fields are not seen when I display the EMP data.Can someone please tell me how to view these fields?
Thanks,
Williams

I got your question . Please find my understandings .
In the transformation Please check weather routine or formula is written which is stopping the dats
to be updated to the target .
I mean data is there in the source but if its not updating to target it seems some rules have been set up in the transformation . Please check .
Assign marks is the best way to appreciate help

Conversion Routines and Function Modules

Hi All,
I have to write the Conversion Routines and Transformation Process for below Fields,
I have a situation, where am having text files with the data having below fields, and before uploading the data to Database i have to do conversion.
So anybody Plz help me regarding this conversion topic how to write the process and how to write the code.
Table       Field Name Type    Length        Short Text
BKPF     BLART       CHAR     2     Document Type
BKPF     BUKRS       CHAR     4     Company Code
BSEG     BUKRS       CHAR     4     Company Code
BSEG     HKONT       CHAR     10     General Ledger Account
BSEG     KOSTL       CHAR     10     Cost Center
BSEG     VERTN       CHAR      13     Contract Number
KNA1     KUNNR       CHAR     10     Customer Number

Hi Bala
Supposing all the fields exist in internal table itab. You can add the code simple as below:
loop at itab.
   perform conv_fld changing: itab-bukrs,
                              itab-blart,
                              itab-hkont,
                              itab-kostl,
                              itab-vertn,
                              itab-kunnr.
endloop.
*&      Form conv_fld
FORM conv_fld CHANGING fld.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
    INPUT         = fld
IMPORTING
   OUTPUT        = fld.
ENDFORM.                    " conv_fld
So for each field depending on its length the conversion routine acts and gives the right output. Please make sure, that your internal table if defined with the right field references or length.
Kind Regards
Eswar

Nls lang and date format

The chinese character and date in the result are not displayed properly.
How can I change the nls lang setting as same as in db? And,
how to change the date format to yyyy/mm/dd?
Please help! Thanks!

The SQL Developer team already informed that the implementation of a routine is foreseen for future versions to configure these parameters
It sees what the Sharon (sbkenned) said in the topic of the follow link:
Re: Alter session command on start-up

Data package and data packet

Hit
i want to know the difference between data package and data packet .when this comes in sap bw
with regards
tushar

Hello,
Data package term is related to DTP which is used to load Data from PSA to further Data Targets
Start and end routine works at package level so routine run for each package one by one .By default package have sorted data based on keys (non unique keys (characteristics )of source or target) and by setting semantic keys you can change this order.So Package having more data will take more time in processing then package have lesser data .
Data Packet Term is related to Info Package which is used to load data from Source System to BI (PSA).
As per SAP standard, we prefer to have 50,000 records per one data packet.
For every data packet, it does commit & save --- so less no. of data packets required.
If you have 1 lakh records per data packet and there is an error in the last record, the entire packet gets failed.
Hope it helps!

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

Copy contract PO number and Date to Sales Order

Hi freinds,
I have one requirement. I want to copy contract PO number and date to Sales order PO Number and Date while creating the sales order with reference to contract.
Thanks,
Satya

Hi,
You have to modify your data transfer routine with the help of ABAPer.
You have to give him the requirement that these value should be copied to sales order from contract.
He will do the needful changes in the data transfer routine.
Then assign that routine to the copy control of sales order from contract.
Regards
Raj.

Using ABAP routines for data selection

Hello,
I want to use ABAP routine to determine value range of data selection in Data Package but when I use routine for one field, selection criterias for other fields are ignored, e.g.:
in Data Package I have two selection fields:
CPUDT Accounting Document Entry Date
AEDAT Date of the Last Document Change by Transaction
For CPUDT I wrote ABAP routine
and for AEDAT I have just typed in period of time.
I started data extraction and open Monitor for this Data Package.
At Header tag I checked selections info and there is selection only for CPUDT.
Could somebody explain me is it normal system behaviour?
Thanks
Andrzej

Thanks for reply but that would be too easy...
I have tried your advice but nothing changed.
I think this is data extraction configuration problem.
Andrzej

Callback routines and data

Similar Messages

Maybe you are looking for