What is Data conversion ? What are data conversion programs ? please give

What is Data conversion ? What are data conversion programs ? please give me some sample code?

Hi,
I think you mean "Data Acquisition"...
"The Data Acquisition IT process allows you to connect heterogeneous sources (SAP systems, database management systems, files, relational data, multidimensional data) to BI. You can transfer data straight into BI from the source or use SAP NetWeaver XI to transfer data. Furthermore, the process supports direct access to source data, without having to load it into BI."
http://help.sap.com/saphelp_nw04s/helpdata/en/aa/1fb042e745ca6ae10000000a155106/frameset.htm
[Data AcquisitionTechniques in SAP NetWeaver BI|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/329fcd87-0c01-0010-4a9c-86f038e11d23]
Regards
Andreas

Similar Messages

What these pesky SUID files are? Any solution please?

When did permission repair (my computer can't start) , 2 PESKY FILES were found and can not be repaired
despite I've run the repair 4 times.
Here are the warnings at permission repair window:
SUID file" System/Library/private Frameworks/Admin.Frameworks/Versions/A/resources/readconfig" has been modified and will not be repaired
SUID file "System/Library/private Frameworks/Admin.Frameworks/Versions/A/resources/writeconfig" has been modified and will not be repaired.
The big question- what exactly these files are and how to fix/ eliminate them ?
The task is too complex for a novice like me and on the top of everything I am able
start my Mac only from backup disk (I suspect these SUID files for messing up with normal startup)
Mac is MacBookPro OS X 10.6
Any help about these pesky files, please?

You can safely ignore these messages - search the forum there must a request like this every other day. Whatever is causing your other issues it isn't this.
Regards
TD

For XD01, Sales area data tab greyed out

Hi,
User has XD01,XD02,XD05,XD06,XD07,XD99.when user tries to use XD01 with parameters customer,sales org, dist channel and division when go to customer : sales area data screen,sales area data tab is greyed out.It shouldnot be greyed out.what is the cause of it.user has proper authorization for SD.

Hi,
Try with OBD2 tcode...
Also, make sure that while creating customer, you enter sales org., dis channel, & division....
Regards
Edited by: SAP2020 on Jan 27, 2010 11:08 AM

Function module to read sales area data of a Business partner

Hi,
Could anyone please tell me if there is a functio module to read the sales area data of a business partner.
Also, what tables contain the sales area data of a BP.
Thanks,
Sahil

Hi Gregor,
I was basically looking for a function module that would give me the details on the Billing Tab from the BP Sales area data.
we can use BAPI_BUPA_FRG0030_GETDETAIL function module to retreive that data.
Thanks,
Sahil
Message was edited by: sahil gupta

Changes in Sales Area data

We require to provide access to "make changes" in the sales area fields only, of a customer master record. The t code VD02 was looked upon, but strangely when VD02 was accessed, even the general data too comes up for editiing which is strictly not required.
XD02 is not provided to the said user, only the account group, activity 02, and VD02 was provided for the specific sales area.
Request you all to enlighten me as to where am I going wrong, in the understanding of VD02, authorisation or the execution of it.
Further to the same, if tab wise authorisation is possible within the sales area data, would be even more obliged.
Thanks and regards,
Tariq

Dear Aziz
There are 3 tables where customer master data stores
KNA1 - General data
KNB1 - Company code data
KNVV - Sales area data
You can restrict particular user by blocking kna1 table access for tcode - va02.
Regards
Pavan Kumar

Delete Sales Area Data in Account Management

Hello,
we are trying to delete data from Sales Are Data assignment block (BP_SALES/CorpAccountSalesOV) from acconts in WebUI.
For doing that we have activated the Delete button in method GET_OCA_T_TABLE of the enhanced class CL_BP_SALES_CORPACCOUNTSA_IMPL.
When clicking the Delete button the method EH_ONONE_CLICK_ACTION is processeing the DELETE event and the Sales Area Data line entry will disappear as expected from the table view in the assignment block.
But when saving the account the delete sales area entry will be available again.
So it is not deleted by the framework.
Do we have additional adjustments?
Thanks in advance,
André

Hi Veena,
cl_crm_bol_core->modify( ) is called by standard:
The DELETE event is handled by the standard method EH_ONONE_CLICK_ACTION
of the class CL_BP_SALES_CORPACCOUNTSA_IMPL (BP_SALES/CorpAccountSalesOV).
Line 59 of that method calls lr_core->modify( ).
Within that method CL_BUPA_IL_SALES_AREA->MODIFY is called.
Therein the standard is calling the FM CRM_BUPA_FRG*_DELETE but without
importing iv_x_save= X.
So a memory save on commit is not registered and the data will not delete from the database.
Best regards,
André

How to configure a cisco 2960 switch to support two routers(data and voice), please give me any suggestions

HI, I need to configure a 2960 switch at a client site. They have routers already been installed on site, one is for data traffic another is for voice. I have created two vlans on switch for data and voice. Now I couldn't get any idea what would be the default gateway on switch.
Please give me any suggestions.

HI Leo,
Many thanks for your reply.
But there are two up-links going from Gi 0/1 and Gi 0/2. I have configured the S/W like below,
interface GigabitEthernet0/1
description UPLINK TO Data router
switchport access vlan 100
switchport mode access
interface GigabitEthernet0/2
description UPLINK TO voice router
switchport access vlan 100
switchport mode access
interface Vlan1
no ip address
no ip route-cache
shutdown
interface Vlan60
ip address 192.168.1.253 255.255.255.0
ip helper address 192.168.1.1
no ip route-cache
interface Vlan100
ip address 172.16.1.253 255.255.255.0
ip helper address 172.16.1.1
no ip route-cache
I have used IP helper address, but I am getting some connecting issues on PCs and IP phones. Please suggest me, Can I manage it with two uplinks with different IP addresses.
Thanks in advance.

What is the best process for conversion moving district data to city data?

Hi ALL,
I Need to write one conversion which will move the district field data into city field data in infotype 6..
It need to apply for only one Specific country which can be identified by Employee Personnel Area..and it should be apply for all active , Terminated employee as well...
What is the best process so that i can catpure all the data records of employees of the Specific country?
my approacH is..
LDB: PNP.
Start-of-selection.
RP_PROVIDE_FROM_LAST P0001 space pn-begda pn-endda.
check p0001-weks = '5200'.
rp_provide_from_last p0006 space pn-begda pn-endda.
Loop at p0006.
move p0006 to T_p0006.
if ort01 is not initial
Move P0006-ORT01 TO T_P0006-ORT02.
endif.
      CALL FUNCTION 'HR_INFOTYPE_OPERATION'
        EXPORTING
          infty         = '0006'
          subtype       = P0006-subty
   objectid      = P_record-objps
          number        = p0006-pernr     "employeenumber
          validityend   = validityend
          validitybegin = validitybegin
         record        = T_p0006.
          recordnumber = p_record-SEQNR
          operation     = 'MOD'
          nocommit      = nocommit
          dialog_mode   = '0'
        IMPORTING
          return        = return_struct
          key           = personaldatakey
        EXCEPTIONS
          OTHERS        = 0.
      Endloop.
Is this using Loop is fine? or Using PROVIDE * from p0006 between PN-BEGDA AND PN-ENDDA
ENDPROVIDE is fine?
Is my code is accurate...Bapi_employee enque bapiemployee_deque i will add apart from that is this code is fine for my requirement or any additional need to take care to capture all the employee data ?
Regards
sas

Hi,
Please use the following code: -
RP_PROVIDE_FROM_LAST P0001 space pn-begda pn-endda.
check p0001-weks = '5200'.
rp_provide_from_last p0006 space pn-begda pn-endda.
provide * from p0006 between PN-BEGDA AND PN-ENDDA
move p0006 to T_p0006.
if ort01 is not initial
Move P0006-ORT01 TO P0006-ORT02.
endif.
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
EXPORTING
infty = '0006'
subtype = P0006-subty
objectid = P_record-objps
number = p0006-pernr "employeenumber
validityend = p0006-endda
validitybegin = p0006-begda
record = p0006.
recordnumber = p0006-SEQNR
operation = 'MOD'
nocommit = nocommit
dialog_mode = '0'
tclass = 'A'
IMPORTING
return = return_struct
key = personaldatakey
EXCEPTIONS
OTHERS = 0.
endprovide.
Hope this will help you.
Thanks & Regards,
Gaurav

What are the conversion rules

what are the conversion rules?can anybody give information on that?points wil be rewarded?

hI..
From sap help....
Conversion Rules for Elementary Data Types
There are ten predefined ABAP data types. There are 100 possible type combinations between these elementary data types. ABAP supports automatic type conversion and length adjustment for all of them except type D (date) and type T (time) fields which cannot be converted into each other.
The following conversion tables define the rules for converting elementary data types for all possible combinations of source and target fields.
C D F I N P STRING T X XSTRING
Source Type Character

Conversion table for source type C
Target
Conversion
C
The target field is filled from left to right. If it is too long, it is filled with blanks from the right. If it is too short, the contents are truncated from the right.
D
The character field must contain an 8-character date in the format YYYYMMDD .
F
The contents of the source field must be a valid representation of a type F field as described in Literals.
N
Only the digits in the source field are copied. The field is right-justified and filled with trailing zeros.
I, P
The source field must contain the representation of a decimal number, that is, a sequence of digits with an optional sign and no more than one decimal point. The source field can contain blanks. If the target field is too short, an overflow may occur. This may cause the system to terminate the program.
STRING
The occupied length of the source field is copied. All trailing spaces are truncated.
T
The character field must contain a six-character time in HHMMSS format.
X
Since the character field must contain a hexadecimal string, the only valid characters are 0,1,2,3,4,5,6,7,8,9,A,B,C,D,E,F. This string is packed as a hexadecimal number, transported left-justified, and filled with zeros or truncated on the right.
XSTRING
As for fields of type X, except that the target field is not filled with zeros.
Source Type Date
Conversion table for source type D
Target
Conversion
C
The date is transported left-justified without conversion.
D
Transport without conversion.
F
The date is converted into a packed number. The packed number is then converted into a floating point number (see corresponding table).
N
The date is transported left-justified without conversion and, if necessary, filled with zeros on the right.
I, P
The date is converted to the number of days since 01.01.0001.
STRING
The date is converted to a character field, which is then converted to a character string.
T
Not supported. Results in an error message during the syntax check or in a runtime error.
X
The date is converted to the number of days since 01.01.0001 in hexadecimal format.
XSTRING
As for fields of type X, except that only significant bytes are copied.
Source Type Floating Point Number
Conversion table for source type F
Target
Conversion
C
The floating point number is converted to the <mantissa>E<exponent> format and transported to the character field. The value of the mantissa lies between 1 and 10 unless the number is zero. The exponent is always signed. If the target field is too short, the mantissa is rounded. The length of the character field must be at least 6 bytes.
D
The source field is converted into a packed number. The packed number is then converted into a date field (see corresponding table).
F
Transport without conversion.
N
The source field is converted into a packed number. The packed number is then converted into a numeric text field (see corresponding table).
I, P
The floating point number is converted to an integer or fixed point value and, if necessary, rounded.
STRING
As for fields of type C, except that the maximum number of places is used for the mantissa (maximum precision). Despite this, different signs or exponents can lead to different string lengths.
T
The source field is converted into a packed number. The packed number is then converted into a time field (see corresponding table).
X
The source field is converted into a packed number. The packed number is then converted into a hexadecimal number (see corresponding table).
XSTRING
As for fields of type X, except that leading zeros are not copied.
Source Type Integer
Type I is always treated in the same way as type P without decimal places. Wherever type P is mentioned, the same applies to type I fields.
Source Type Numeric Text
Conversion table for source type N
Target
Conversion
C
The numeric field is treated like a character field. Leading zeros are retained.
D
The numeric field is converted into a character field. The character field is then converted into a date field (see corresponding table).
F
The numeric field is converted into a packed number. The packed number is then converted into a floating point number (see corresponding table).
N
The numeric field is transported right-justified and filled with zeros or truncated on the left.
I, P
The numeric field is interpreted as a number, and transferred to the target field, where it is right-justified, and adopts a plus sign. If the target field is too short, the program may be terminated.
STRING
As for fields of type C. The length of the character string matches the length of the numeric text.
T
The numeric field is converted into a character field. The character field is then converted into a time field (see corresponding table).
X
The numeric field is converted into a packed number. The packed number is then converted into a hexadecimal number (see corresponding table).
XSTRING
As for fields of type X, except that leading zeros are not copied.
Source Type Packed Number
If the program attribute Fixed point arithmetic is set, the system rounds type P fields according to the number of decimal places or fills them out with zeros.
Conversion table for source type P
Target
Conversion

C
The packed field is transported right-justified to the character field, if required with a decimal point. The last position is reserved for the sign. Leading zeros appear as blanks. If the target field is too short, the sign is omitted for positive numbers. If this is still not sufficient, the field is truncated on the left. ABAP indicates the truncation with an asterisk (*). If you want the leading zeros to appear in the character field, use UNPACK instead of MOVE.
D
The packed field value represents the number of days since 01.01.0001 and is converted to a date in YYYYMMDD format.
F
The packed field is accepted and transported as a floating point number.
N
The packed field is rounded if necessary, unpacked, and then transported right-justified. The sign is omitted. If required, the target field is filled with zeros on the left.
I, P
A packed field is converted to type I. The resulting four bytes are placed into the target field right-justified. If the target field is too short, an overflow occurs. If the target field is longer, it is filled with zeros on the left.
STRING
As for fields of type C, except that leading zeros are not generated.
T
The packed field value represents the number of seconds since midnight and is converted to a time in HHMMSS format.
X
A packed field is converted to type I. The resulting four bytes are placed into the target field right-justified and in big-endian format. If the target field is too short, it is truncated from the left. If the target field is longer than 4, it is filled with zeros on the left. Negative numbers are represented by the two's complement (= bit complement +1).
XSTRING
As for fields of type X, except that leading zeros are not generated.
Source Type String
Conversion table for source type STRING
Target
Conversion
C
The target field is filled from left to right. If it is longer than the string, it is filled with trailing spaces. If it is too short, the contents are truncated from the right.
D
The string must contain an 8-character date in the format YYYYMMDD .
F
The contents of the string must be a valid representation of a type F field as described in Literals.
N
Only digits in the string are copied. The field is right-justified and filled with trailing zeros. If the target field is too short, it is truncated from the left.
I, P
The string must contain the representation of a decimal number, that is, a sequence of digits with an optional sign and no more than one decimal point. The source field can contain blanks. If the target field is too short, an overflow may occur. This may cause the system to terminate the program.
STRING
The source string is copied to the target string unconverted.
T
The string must contain a six-character time in HHMMSS format.
X
Since the character field must contain a hexadecimal-character string, the only valid characters are 0,1,2,3,4,5,6,7,8,9,A,B,C,D,E,F. This character string is packed as a hexadecimal number, transported left-justified, and filled with zeros or truncated on the right.
XSTRING
As for target fields of type X, except that the field is not filled with zeros.

Source Type Time
Conversion table for source type T
Target
Conversion
C
The source field is transported left-justified without conversion.
D
Not supported. Results in an error message during the syntax check or in a runtime error.
F
The source field is converted into a packed number. The packed number is then converted into a floating point number (see corresponding table).
N
The date is converted into a character field. The character field is then converted into a numeric text field (see corresponding table).
I, P
The date is converted to the number of seconds since midnight.
STRING
The time is converted to a character field, which is then converted to a character string.
T
The date is transported left-justified without conversion and, if necessary, filled with zeros on the right.
X
The date is converted to the number of seconds since midnight in hexadecimal format.
XSTRING
As for fields of type X, except that only significant bytes are copied.
Source Type Hexadecimal Field
Conversion table for source type X
Target
Conversion
C
The value in the hexadecimal field is converted to a hexadecimal character string, transported left-justified to the target field, and filled with zeros.
D
The source field value represents the number of days since 01.01.0001 and is converted to a date in YYYYMMDD format.
F
The source field is converted into a packed number. The packed number is then converted into a floating point number (see corresponding table).
N
The source field is converted into a packed number. The packed number is then converted into a numeric text field (see corresponding table).
I, P
The value of the source field is interpreted as a hexadecimal number. It is converted to a packed decimal number and transported right-justified to the target field. If the hexadecimal field is longer than 4 bytes, only the last four bytes are converted. If it is too short, a runtime error may occur.
STRING
As for target fields of type C, except that the field is not filled with zeros. The length of the string is twice the length of the hexadecimal field.
T
The source field value represents the number of seconds since midnight and is converted to a time in HHMMSS format.
X
The value is transported left-justified and filled with X'00' on the right, if necessary.
XSTRING
The hexadecimal field is copied completely that is, trailing zeros are not truncated.
Source Type Byte Sequence
Conversion table for source type XSTRING
Target
Conversion
C
The value in the byte sequence is converted to a hexadecimal character string, transported left-justified to the target field, and filled with zeros.
D
The byte sequence value represents the number of days since 01.01.0001 and is converted to a date in YYYYMMDD format.
F
The content of the byte sequence is converted into a packed number. The packed number is then converted into a floating point number (see corresponding table).
N
The content of the byte sequence is converted into a packed number. The packed number is then converted into a numeric text field (see corresponding table).
I, P
The content of the byte sequence is interpreted as a hexadecimal number. It is converted to a packed decimal number and transported right-justified to the target field. If the byte sequence is longer than 4 bytes, only the last four bytes are converted. If it is too short, a runtime error may occur.
STRING
As for target fields of type C, except that the field is not filled with zeros. The length of the string is twice the length of the byte sequence.
T
The byte sequence value represents the number of seconds since midnight and is converted to a time in HHMMSS format.
X
The byte sequence is transported left-justified and filled with X'00' on the right, if necessary.
XSTRING
The source byte sequence is copied to the target byte sequence unconverted.
Conversion Rules for Internal Tables
Internal tables can only be converted into other internal tables. You cannot convert them into structures or elementary fields.
Internal tables are convertible if their line types are convertible. The convertibility of internal tables does not depend on the number of lines.
Conversion rules for internal tables:
Internal tables which have internal tables as their line type are convertible if the internal tables which define the line types are convertible.
Internal tables which have line types that are structures with internal tables as components are convertible according to the conversion rules for structures if the structures are compatible.
Conversion Rules for Structures
ABAP has one rule for converting structures that do not contain internal tables as components. There are no conversion rules for structures that contain internal tables. You can only make assignments between structures that are compatible.
You can combine convertible structures in the following combinations:
Converting a structure into a non-compatible structure
Converting elementary fields into structures
Converting structures into elementary fields
In each case, the system first converts all the structures concerned to type C fields and then performs the conversion between the two resulting elementary fields. The length of the type C fields is the sum of the lengths of the structure components. This rule applies to all operations using structures that do not contain internal tables.
If a structure is aligned, the filler fields are also added to the length of the type C field.
A non-aligned structure without filler fields:
If you convert a structure into a shorter structure, the original structure is truncated. If you convert a structure into a longer one, the parts at the end are not initialized according to their type, but filled with blanks.
It can make sense to assign a structure to another, incompatible, structure if, for example, the target structure is shorter than the source, and both structures have the same construction over the length of the shorter structure. However, numeric components of structures that are filled in incompatible assignments may contain nonsensical or invalid values that may cause runtime errors.
DATA: BEGIN OF FS1,
INT TYPE I VALUE 5,
PACK TYPE P DECIMALS 2 VALUE 2.26,
TEXT(10) TYPE C VALUE Fine text,
FLOAT TYPE F VALUE 1.234e+05,
DATA TYPE D VALUE 19950916,
END OF FS1.
DATA: BEGIN OF FS2,
INT TYPE I VALUE 3,
PACK TYPE P DECIMALS 2 VALUE 72.34,
TEXT(5) TYPE C VALUE Hello,
END OF FS2.
WRITE: / FS1-INT, FS1-PACK; FS1-TEXT, FS1-FLOAT, FS1-DATE.
WRITE: / FS2-INT, FS2-PACK, FS2-TEXT.
MOVE FS1 TO FS2.
WRITE: / FS2-INT, FS2-PACK, FS2-TEXT.
Message was edited by:
Rammohan Nagam

What are data types that can be stored on TemSe?

What are data types that can be stored on TemSe(Storage for Temporary Sequential Data)?
Moderator message: please search for available information/documentation.
[Rules of engagement|http://wiki.sdn.sap.com/wiki/display/HOME/RulesofEngagement]
[Asking Good Questions in the Forums to get Good Answers|/people/rob.burbank/blog/2010/05/12/asking-good-questions-in-the-forums-to-get-good-answers]
Edited by: Thomas Zloch on Sep 18, 2011 10:04 PM

Hi
SAP Library: TemSe Data Store:
There are the following TemSe objects, among others:
·        Spool requests (TemSe Name: Spool....)
·        Job logs (TemSe Name: JOBLG...)
·        Objects from other applications, such as Human Resources (TemSe Name: HR)
·        An object whose name begins with KONS; this is object is constantly used by report RSPO1043 and should never be deleted (SAP Note 98065)
Sandra

Cannot implicitly convert type 'System.Data.SqlClient.SqlDataReader' to 'Microsoft.ReportingServices.DataProcessing.IDataReader'. An explicit conversion exists (are you missing a cast?)

Cannot implicitly convert type 'System.Data.SqlClient.SqlDataReader' to 'Microsoft.ReportingServices.DataProcessing.IDataReader'. An explicit conversion exists (are you missing a cast?)
I am getting the above error in c#. Please help me. Thanks in advance
public IDataReader ExecuteReader(CommandBehavior behavior)
string query = "select * from Sales.Store";
SqlConnection readerconn = new SqlConnection("Data Source=localhost;Initial Catalog=AdventureWorks2000;Integrated Security=SSPI");
SqlCommand readercmd = new SqlCommand(query);
try
readerconn.Open();
readercmd = readerconn.CreateCommand();
readercmd.CommandText = query;
readercmd.CommandType = System.Data.CommandType.Text;
SqlDataReader TestReader = readercmd.ExecuteReader();
return TestReader; //Getting error at this line
readerconn.Close();
catch (Exception e)
throw new Exception(e.Message);

Hi,
Please firstly take a look at the documentation:
IDbCommand.ExecuteReader
Method
Users do not create an instance of a
DataReader class directly. Instead, they obtain the
DataReader through the
ExecuteReader method of the Command object. Therefore, you should mark
DataReader constructors as internal.
You need to use this method to get the IDataReader object, all the IDbCommand and IDataReader are in the Microsoft.ReportingServices.DataProcessing namespace. There's another IDataReader object which is in System.Data namespace, but they're actually two different
objects, that's why you got the exception.
For how to properly implement this Microsoft.ReportingServices.DataProcessing.IDataReader, please check this documentation:
Implementing a DataReader Class for a Data Processing Extension
It also provides code samples there.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

What is meant by Defining Common Data Area ??

I have seen a code like this ....
DATA: BEGIN OF COMMON PART FM06LCS2,
 ( All the parameters /select-options are declared here)
 END OF COMMON PART.
what is this ??? what for it is used ??????
My requirement is .....
To add one more Parameter in between this area.....
what all should i do???
Expecting your answers,
Thanks in advance
Cheers,
R.Kripa.

HI
GOOD
GO THROUGH THIS
For the sake of completeness, this section describes a technique that allows you to access the global data of the calling program from an external subroutine. To do this, you declare a common data area for the calling program and the program containing the subroutine. All interface work areas declared using TABLES and NODES behave like the common data area.
Like external subroutines themselves, you should use common data areas very sparingly. The rules for accessing common data areas can become very complicated if you call function modules from nested subroutines.
You declare a common data area in all programs concerned using the statement:
DATA: BEGIN OF COMMON PART [<name>],
 END OF COMMON PART [<name>].
Between the two DATA statements, you declare all of the data you want to include in the common data area.
The common part declaration must be exactly the same in all of the programs in which you want to use it. It is therefore a good idea to put the declaration in an include program.
You can use several common parts in one program. In this case, you must assign a name <name> to each common part. If you only have one common part in each program, you do not have to specify a name. To avoid conflicts between programs that have different common part declarations, you should always assign unique names to common parts.
Assume an include program INCOMMON contains the declaration of a common part NUMBERS. The common part comprises three numeric fields: NUM1, NUM2, and SUM:
***INCLUDE INCOMMON.
DATA: BEGIN OF COMMON PART NUMBERS,
 NUM1 TYPE I,
 NUM2 TYPE I,
 SUM TYPE I,
 END OF COMMON PART NUMBERS.
The program FORMPOOL includes INCOMMON and contains the subroutines ADDIT and OUT:
PROGRAM FORMPOOL.
INCLUDE INCOMMON.
FORM ADDIT.
SUM = NUM1 + NUM2.
PERFORM OUT.
ENDFORM.
FORM OUT.
WRITE: / 'Sum of', NUM1, 'and', NUM2, 'is', SUM.
ENDFORM.
A calling program FORM_TEST includes INCOMMON and calls the subroutine ADDIT from the program FORMPOOL.
PROGRAM FORM_TEST.
INCLUDE INCOMMON.
NUM1 = 2. NUM2 = 4.
PERFORM ADDIT(FORMPOOL).
NUM1 = 7. NUM2 = 11.
PERFORM ADDIT(FORMPOOL).
This produces the following output:
Sum of 2 and 4 is 6
Sum of 7 and 11 is 18
The subroutines in the program FORMPOOL access the global data of the shared data area.
Assume a program FORMPOOL that contains two subroutines TABTEST1 and TABTEST2 as follows:
PROGRAM FORMPOOL.
TABLES SFLIGHT.
FORM TABTEST1.
SFLIGHT-PLANETYPE = 'A310'.
SFLIGHT-PRICE = '150.00'.
WRITE: / SFLIGHT-PLANETYPE, SFLIGHT-PRICE.
ENDFORM.
FORM TABTEST2.
LOCAL SFLIGHT.
SFLIGHT-PLANETYPE = 'B747'.
SFLIGHT-PRICE = '500.00'.
WRITE: / SFLIGHT-PLANETYPE, SFLIGHT-PRICE.
ENDFORM.
A program FORM_TEST calls TABTEST1 and TABTEST2 as follows:
PROGRAM FORM_TEST.
TABLES SFLIGHT.
PERFORM TABTEST1(FORMPOOL).
WRITE: / SFLIGHT-PLANETYPE, SFLIGHT-PRICE.
PERFORM TABTEST2(FORMPOOL).
WRITE: / SFLIGHT-PLANETYPE, SFLIGHT-PRICE.
THANKS
MRUTYUN

All my stored data in Numbers are gone. What do I do?

All my stored data in "Numbers" are gone. What do I do?

every workbook is gone, data in one workbook is gone? Cant open a workbook, any workbook? Please be a little more specific as to the circumstances so we can try to help out.
Thanks
Jason

When I try to restore from my iCloud they say there are a problem of back up data so what can I do ?

When I try to restore from my iCloud they say there are a problem of back up data so what can I do ?

Unfortunately, nothing. If there is a problem with the backup you won't be able to use it. You'll have to restor a backup from your computer using iTunes, if you have one.

How , When and What is the significance of Business Partner's Sales Area Data?

Dear All,
What is the Sales Area data of busines partner , What is the significance of the same?
When it gets modified or extended?
How to maintain its configuration? How maintain its data!!
Hence i want to understand almost all about sales Area data of business partner.
Regards,
Dhruvin
Moderated: Please use the search before posting.
Message was edited by: Andrei Vishnevsky

Hello Dhruvin,
I think you shall have a look on the current help about this issue as it is a Complex ssue meaning "extense" and also one of the basic Points on the customizing and deployment of a CRM System:
Organizational Management in SAP CRM - SAP Library
Basically the Sales Area Data identifies your BP in your Sales Organization.
You define your sales organization so its fits your business requirements and real structure. f
Having this information properly defined helps to link data between SD and CRM so you can have for example: - The proper price for a customer when creating and Oportunity/ Sales Order.
- To restrict the access of the information of an employee.
Hope these hints help..
Regards

What is Data conversion ? What are data conversion programs ? please give

Similar Messages

Maybe you are looking for