Give me details about customer exit, sap exit using characterstics variabl

give me details about customer exit, sap exit using characterstics variable

Hi,
Customer Exit:
http://help.sap.com/saphelp_nw04/helpdata/en/f1/0a56f5e09411d2acb90000e829fbfe/content.htm
SAP Exit:
http://help.sap.com/saphelp_nw04/helpdata/en/f1/0a56f5e09411d2acb90000e829fbfe/frameset.htm
Characteristic Variables:
http://help.sap.com/saphelp_nw04/helpdata/en/5c/8db07d555411d189660000e829fbbd/frameset.htm
SAP and Customer Exit:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f1a7e790-0201-0010-0a8d-f08a4662562d
Some Imp Docs:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/650ee690-0201-0010-4bb7-83c3e2a74039
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/009819ab-c96e-2910-bbb2-c85f7bdec04a
Assign points if these are helpful.
Rgs,
I.R.K

Similar Messages

Calculations on customer exit using input variable

hi,
suppose i have a date input variable on my query, and i want to use the input value as an input for a calculation to be done in a different characteristic variable whose value is derived via a customer exit. how could this be done?
as an example - i have an input date field, and say, the user enters 1/15/2005. the other characteristic variable is, for example, sales for a given date, restricted against a characteristic variable (customer exit) which should restrict the KF to say, the start of the month of the input date up to the input date (in this case, 1/1/2005 - 1/15/2005).
thanks in advance. =)
ryan.

Hi Ryan,
you have to use parameter I_STEP = 2 in your exit (IF I_STEP = 2. (...))
This second step is called after the processing of the variable pop-up and only for those variables that are not marked as ready for input and are set to mandatory variable entry.
Build your second variable in this way and then you can use this step to see first (pop-up) variable value.
For details see www.service.sap.com/bw -> SAP BW InfoIndex -> Variables -> How to... Derive a Variable value from another variable 2.x (pdf).
Hope it helps (and please don't forget to assign some points by clickin'on the yellow star to the contributors that help you !!!)
Bye,
Roberto

Puzzled about Customer Exits

Hi everyone,
I'm trying to get into the field of customer exit coding to enhance reporting capabilities. Now from what I've learned, the way to go is via one of the SAPLRRS0 exits and do the actual coding in includes like ZXRSRU01, which should be located in the customer namespace (since it's a 'Z', as I understand) and hence be modifiable. Still, if I try to edit the file, SAP asks for a developer key, but I thought this was the whole point about customer exits (and what sets them apart from user exits): Since you're not tampering with the original system, there would be no need for a developer key
I have also checked in SE03 if the customer namespace is modifiable (from what I can tell it is).

Hi Tilman Budde ,
Keys are required at 2 levels .
1. When you try to modify existing sap object ... This is called as object key.
2. When you try to modify existing sap object ..This is called as developer access key ..Unless your user id have this (developer key) ..even if you have object key you will not be able to modify abap workbench objects..
Hope that helps.
Regards
Kapadia
***Assigning points is the way to say thanks in SDN.***

How to create customer exit for characteristic variables and for text vars.

hi friends,
can anybody tell me how to create customer exit for characteristic variables and for text variables in bw ides system.
thanks,
sree

Hi,
Please have a look at:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f1a7e790-0201-0010-0a8d-f08a4662562d
Krzys

Give me details about conversion routine like alpha

give me details about conversion routine like alpha and how many conversion routines are ther and their uses give detail

Hi Deba,
There are many Conversion routines...
ALPHA Conversion Routine
BUCAT Conversion Routine
EAN11 Conversion Routine
GJAHR Conversion Routine
ISOLA Conversion Routine
MATN1 Conversion Routine
NUMCV Conversion Routine
PERI5 Conversion Routine
PERI6 Conversion Routine
PERI7 Conversion Routine
POSID Conversion Routine
PROJ Conversion Routine
REQID Conversion Routine
IDATE Conversion Routine
Conversion Routine RSDAT
SDATE Conversion Routine
WBSEL Conversion Routine
Check this link for conversion routines and its types...
http://help.sap.com/saphelp_nw04s/helpdata/en/2b/e9a20d3347b340946c32331c96a64e/frameset.htm
Hope this helps u...
Regards,
KK.

Give me details about differrent views in generic extraction give details

give me details about differrent views in generic extraction give details such as database view, projection view, help view, etc please give detail

Dear Deba,
Projection view - Just retrieves some fields from a single table.
Help View - This is used for search help.
Database View - This is inner join view of one or more tables
Maintenance View - Helps in creating maintaining data of the application object. The data can be distributed among several tables
Data Base View:
A database view is defined in the ABAP Dictionary and automatically created on the database during
activation. Accesses to a database view are passed directly to the database from the database interface.
The database software performs the data selection.
If the definition of a database view is changed in the ABAP Dictionary, the view created on the database
must be adjusted to this change. Since a view does not contain any data, this adjustment is made by
deleting the old view definition and creating the view again in the ABAP Dictionary with its new definition.
The maintenance status defines whether you can only read with the view or whether you can also write
with it. If a database view was defined with more than one table, this view must be read only.
The data read with a database view can be buffered. View data is buffered analogously to tables. The
technical settings of a database view control whether the view data may be buffered and how this should
be done. The same settings (buffering types) can be used here as for table buffering. The buffered view
data is invalidated when the data in one of the base tables of the view changes.
Maintainance View:
Data that is distributed on more than one table often forms a logical unit, called an application object.
You should be able to display, change and create the data of such an application object together. Users
usually are not interested in the technical implementation of the application object, such as the distribution of the data on several tables.
You can maintain complex application objects in a simple way using a maintenance view. The data is
automatically distributed on the underlying database tables.
All the tables used in a maintenance view must be linked with a foreign key. This means that the join
conditions are always derived from the foreign key in the maintenance view. You cannot enter the join
conditions directly as in a database view.
A maintenance interface with which the data of the view can be displayed, changed and created must be
generated from the definition of a maintenance view in the ABAP Dictionary.
When the maintenance interface is created, function modules that distribute the data maintained with the
view on the underlying tables are automatically generated.
The maintenance interface is generated with the Transaction Generate Table View (Transaction SE54)
or from the view maintenance screen with Environment -> Tab.maint.generator.
Database views implement an inner join. You only get those records which have an entry in all the tables
included in the view.
Maintenance views implement an outer join.
Help View:
A help view is defined analogously to a maintenance view. Help views can only be used as selection
methods in search helps. Since the R/3 System cannot pass the selection directly to the database using
a help view, it must generate its own access routines. The database view should therefore be used as
selection method in preference to the help view.
http://help.sap.com/saphelp_nw2004s/helpdata/en/cf/21ecf9446011d189700000e8322d00/frameset.htm
Difference between "Help View" and "Search Help"
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ed06446011d189700000e8322d00/frameset.htm
for more detailed info look on:
http://www.sap-img.com/abap/what-is-the-different-types-and-usage-of-views.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/abap+dictionary&
Regards,
Ram.

How to Write a CUstomer Exit for a variable in BEx

Hi,
How to write a customer exit variable in bex Query designer
Do i need developers key for this (If so what type of key do i need so that i can ask basis tean to generate)
Info Object: ZEXP_DTE (Expiry Date)
Variable on ZEXP_DTE :
ZEDTE
Type: Customer Exit
Can any one please tell me how to write a code in CMOD from this (Step-by Step)
Expiry Date > Current Cal Day
As arun said
'l_s_range-low = SY-DATUM.
l_s_range-opt = 'I'.
l_s_range-sign = 'GT'.
APPEND l_s_range TO e_t_range.'
I want to insert the above code for the above customer exit but as i am new to BW as ABAP please explain me what are the steps involved in CMOD
Thanks

Hi,
To write customer exit for a variable, you require Access key.
Contact your BASIS to get that.
Access Key,BASIS?
To write Customer exit,
User Exits
User Exit for Variable
/thread/809285 [original link is broken]
Hope these helps u...
Regards,
KK.

Give me details about rule details functions conversion, currency etc in bi

give me details about rule details functions conversion, currency etc in bi when creating transformation

Rule Type
Use
The rule type determines whether and how a characteristic or key figure, or a data field or key field is updated into the target.
Direct Assignment:
The field is filled directly from the selected source InfoObject. If the system does not propose a source InfoObject, you can assign a source InfoObject of the same type (amount, number, integer, quantity, float, time) or you can create a routine.
If you assign a source InfoObject to a target InfoObject that has the same type but a different currency, you have to translate the source currency into the target currency using a currency translation, or apply the source currency.
If you assign a source InfoObject to a target InfoObject that has the same type but a different unit of measure, you have to convert the source unit of measure into the target unit of measure using a unit of measure conversion, or apply the unit of measure from the source.
Constant:
The field is not filled by the InfoObject; it is filled directly with the value specified.
Formula:
The InfoObject is updated with a value determined using a formula.
Read Master Data:
The InfoObject is updated by reading the master data table of a characteristic that is included in the source with a key and a value and that contains the corresponding InfoObject as an attribute. The attributes and their values are read using the key and are then returned.
The Financial Management Area characteristic is included in the target but does not exist in the source as a characteristic. However, the source contains a characteristic (cost center, for example) that has the Financial Management Area characteristic as an attribute. You can read the Financial Management Area attribute from the master data table and use it to fill the Financial Management Area characteristic in the target.
It is not possible to read recursively, that is, to read additional attributes for the attribute. To do this, you have to use routines.
If you have changed master data, you have to execute the change run. By reading the master data, the active version is read. If this is not available, an error occurs.
If the attribute is time dependent, you also have to define when it should be read: at the current date (sy-date), at the beginning or end of a period (defined by a time characteristic in the InfoSource), or at a constant date that you enter directly. Sy-date is used as the default.
Routine:
The field is filled by the transformation routine you have written.
The system allows you to select whether the routine is to be valid for all attributes for this characteristic, or only for the attributes displayed.
Transformation rules generally only have one return value. If you select Return Table, the corresponding key figure routine no longer has a return value; it has a return table. You can then generate any number of values from a data record.
For DataStore objects and InfoObjects: you cannot use the return code in the routine for data fields that are updated by being overwritten. If you do not want to update specific records, you can delete these from the start routine.
If, for the same characteristic, you generate different rules for different key figures or data fields, a separate data record can be created for each key figure from a data record of the source.
With InfoCubes: You can also select Routine with Unit. The return parameter 'UNIT' is then also added to the routine. You can store the required unit of the key figure, such as 'ST', in this parameter. You can use this option, for example, to convert the unit KG in the source, into tons in the target.
If you fill the target key figure from a transformation routine, currency translation has to be performed using the transformation routine. This means that automatic calculation is not possible.
Time Update:
When performing a time update, automatic time conversion and time distribution are available.
Direct Update: the system automatically performs a time conversion.
Time Conversion:
You can update source time characteristics to target time characteristics using automatic time conversion. This function is not available for DataStore objects, since time characteristics are treated as normal data fields. The system only displays the time characteristics for which an automatic time conversion routine exists.
Time Distribution:
You can update time characteristics with time distribution. All the key figures that can be added are split into correspondingly smaller units of time. If the source contains a time characteristic (such as 0CALMONTH) that is not as precise as a time characteristic of the target (such as 0CALWEEK), you can combine these characteristics with one another in the rule. The system then performs time distribution in the transformation.
The time distribution is always applied to all key figures.
Initial:
The field is not filled. It remains empty.
No Transformation:
The key figures are not written to the InfoProvider.
Unit of Measure Conversion and Currency Translation
You can convert data records into the unit of measure or currency in the target transformation.
Assigning InfoObjects for Converting Amounts or Currencies
Use
An InfoObject has to be assigned to a source field of a DataSource if currencies or units of measure need to be converted. The translation types require InfoObjects as input fields to carry out a conversion. You therefore have to assign the appropriate InfoObject to the source field.
If the target has a fixed unit, you only have to assign an InfoObject if you want to carry out a conversion. Otherwise, you can select the No Conversion option.
Procedure
1.      You are in the rule details. Select the rule type Direct Assignment.
2.      Select an appropriate key figure in the InfoObject Assignment field in the Source Fields of Rule area.
3.      Choose the required conversion in the Currency field.
4.      Choose Transfer Values.
Example
In your transformation, you want to assign the AMOUNT field of the DataSource to the FIX_EUR InfoObject in your target, carrying out a currency conversion. To do so, you assign the FIX_EUR InfoObject to the AMOUNT field in the rule details so that the currency can be read from the InfoObject.
Hope this helps u...
Regards,
KK.

How and where to create SAP Exit or Customer Exit in query variable

Hi,
I have to create a date variable in BEx and it should always contain default value as SY-DATUM i.e. current date.
I dont have 0CalDay in any of my data flow,also I am not supposed to add 0CALDAY.
If so,where i can write that exit.
Thanx in advance.

Actually,what my requirement is...
I will not filter any characteristic based on this sy-datum instead I will use that variable value in formulae.
For ex: in my selection,i mention As of date = today's date..then inside the quer designer,a formula will calculate No.of days=As of date-Due date,where "As of Date" is nothing but the date which i have enterd in my selections.
please let me know any solution

Could you pls give the details about the Unicode conversion during Upgrade

Hi,
Can anyone give details about the Unicode conversion during SAP Upgradation fro 4.6C to ECC6.
Waiting for quick response
Best Regards,
Padhy

Hi,
These are the few points i gathered during my upgradation project.
Before starting any upgradation project, it is necessary to take up the back-up of the existing systems. As we are going to upgrade the entire system, we will be changing so many things and if something happens, without back-up, we will be in a trouble.
So it is advised to keep a back-up of the existing system.
Say for example we have the existing system E4B which is of Version 4.6C. Now we want to upgrade it to Version 4.7. Let us see how we can do it.
Version upgrades not only means that we need to run the new Version CD over the existing Version System but only involves some other thing.
Version Upgrade involves the following Steps.
Say we want to upgrade for Version 4.7 from Version 4.6, which is in the System E4B. Now we created one more system called as E1B in which the upgradation for Version 4.7 can be done.
First copy the entire E4B system into the E1B System which is created for Version 4.7.
Apply the Version 4.7 CD provided by SAP over the E1B System.
Now check whether all the functionalities that was in E4B system works fine with E1B system also.
Thus the Version Upgrade involves two steps.
1. SAP Upgradation with the help of the CD
2. Manual Upgradation.
1. SAP Upgradation with the help of the CD
This is nothing but after taking the copy of the existing system into a new system, the upgradation CD from SAP is applied over the new system.
2. Manual Upgradation.
This Manual Upgradation involves
2.1 Upgradation of Standard Objects
2.1.1 SPAU Objects
2.1.2 SPDD Objects
2.2 Upgradation of Custom Objects.
Upgradation of Custom Objects can be placed under the following three categories.
Unicode Compliance
Retrofit
Upgrade
Please Find below some of the common Unicode Errors and their solutions
1. Error:
In case of Translate Error; Dangerous use of Translate in Multilingual system.
Correction:
To correct the Error occurring on TRANSLATE statement use this additional statement before the Translate statement.
SET LOCALE LANGUAGE sy-langu.
This statement defines the Text Environment of all the programs & internal sessions in the language specified in the LANGUAGE KEY, which in this case is sy-langu, i.e. the log on language of the user.
2. Error:
In case of Open Dataset Error; Encoding Addition must be included.
Correction:
This Error occurs only when the MODE is TEXT.
To correct the Error occurring on OPEN DATASET statement use this statement instead.
OPEN DATASET dataset_name FOR access IN TEXT MODE ENCODING DEFAULT.
Where: dataset_name NAME OF THE DATASET.
Access INPUT or OUTPUT or APPENDING or UPDATE.
DEFAULT - Corresponds to UTF-8 in UNICODE systems &
NON_UNICODE in NON-UNICODE systems.
3. Error:
In case of the usage of the Obsolete FM UPLOAD/DOWNLOAD or WS_UPLOAD/DOWNLOAD; Function module UPLOAD is flagged as obsolete.
Correction:
The FM GUI_DOWNLOAD/UPLOAD is used.
The variations to be made in the parameters of the FM:
1. Filename It must be of STRING type.
2. Filetype DAT is not used any longer, instead ASC is used.
3. Field Separator The default value SPACE is used, incase for a TAB separated file X can be used.
4. Error:
In case of CURRENCY/UNIT Addition Error; Use addition CURRENCY/UNIT when outputting.
Correction:
The CURRENCY addition specifies the currency-dependant decimal places for the output of the data objects of type i or p. To obtain the currency-key, the field CURRKEY of the table TCURX is used. The system determines the number of the decimal places from the field CURRDEC of the selected CURRKEY.
To correct this error follow the following method:
WRITE: /3 'TOTAL',' ', TOTAL.
WRITE: /3 TOTAL, , TOTAL CURRENCY 2. --- Where 2is the Currency Key for Getting 2 decimal places.
5. Error:
In case of TYPE X Error; Variable must be of C, N, D, T or STRING type.
Correction:
We need to change all the Type X (Hexadecimal) variables to Type C with their values unchanged.
So the method to be followed is:-
1. Load the definition of the class CL_ABAP_CONV_IN_CE or CL_ABAP_CHAR_UTILITIES.
2. Declare the variable as Type C, and use the method UCCP(XXXX) of the class CL_ABAP_CONV_IN_CE where XXXX represents the 8-bit Hexadecimal value and incase the variable holds a Hex value for a Horizontal Tab , then the Attribute HORIZONTAL_TAB of the class CL_ABAP_CHAR_UTILITIES can be used directly instead of using the method UCCP.
E.g.:
i) *DATA: TAB TYPE X VALUE 09, Tab character
CLASS: CL_ABAP_CHAR_UTILITIES DEFINITION LOAD.
DATA TAB TYPE C VALUE CL_ABAP_CHAR_UTILITIES=>HORIZONTAL_TAB.
ii) * DATA: CHAR TYPE X VALUE 160.
CLASS: CL_ABAP_CONV_IN_CE DEFINITION LOAD.
DATA CHAR TYPE C.
CHAR = CL_ABAP_CONV_IN_CE=>UCCP(00AO).
(Here 00A0 is the Hexadecimal equivalent of the decimal 160).
3. Incase the TYPE X Variable has a length more than 1, then an internal table must be created for the variable.
E.g.:
CLASS: CL_ABAP_CONV_IN_CE DEFINITION LOAD.
DATA : LF(2) TYPE X VALUE 'F5CD'.
DATA : BEGIN OF LF,
A1 TYPE C,
A2 TYPE C,
END OF LF.
LF-A1 = CL_ABAP_CONV_IN_CE=>UCCP('00F5').
LF-A2 = CL_ABAP_CONV_IN_CE=>UCCP('00CD').
6. Error:
In case of the Character -Error; The Character -cant appear in names in Unicode Programs.
Correction:
The Character -(Hyphen) appearing in Variable names is replaced by the character _ (Under Score) for Unicode/Upgrade Compliance.
E.g.:
*wk-belnr LIKE bkpf-belnr,
*wk-xblnr LIKE bkpf-xblnr,
*wk-date LIKE sy-datum,
*wk-wrbtr LIKE bseg-wrbtr,
*wk-name1 LIKE lfa1-name1,
*wk-voucher(8) TYPE c.
wk_belnr LIKE bkpf-belnr,
wk_xblnr LIKE bkpf-xblnr,
wk_date LIKE sy-datum,
wk_wrbtr LIKE bseg-wrbtr,
wk_name1 LIKE lfa1-name1,
wk_voucher(8) TYPE c.
7. Error:
In case of The SUBMIT-TO-SAP-SPOOL Error; you should not use the statement SUBMIT-TO-SAP-SPOOL without the WITHOUT SPOOL DYNPRO addition.
Correction:
1. Declare variables of type PRI_PARAMS, ARC_PARAMS, and a variable of TYPE C which would be used as a VALID FLAG.
2. Call the FM GET_PRINT_PARAMETERS:
CALL FUNCTION 'GET_PRINT_PARAMETERS'
EXPORTING
ARCHIVE_MODE = '3'
DESTINATION = P_DEST
IMMEDIATELY = 'X'
IMPORTING
OUT_ARCHIVE_PARAMETERS = archive_parameters
OUT_PARAMETERS = print_parameters
VALID = valid_flag
EXCEPTIONS
INVALID_PRINT_PARAMS = 2
OTHERS = 4
3. Use the SUBMIT-TO-SAP-SPOOL statement.
E.g.:
     submit zrppt500
     using selection-set 'AUTO3'
     with res_no eq lo_rsnum
     with sreserv in preserv
     to sap-spool destination p_dest
     immediately 'X'. "print immediate
DATA: print_parameters type pri_params,
archive_parameters type arc_params,
valid_flag(1) type c.
CALL FUNCTION 'GET_PRINT_PARAMETERS'
EXPORTING
ARCHIVE_MODE = '3'
DESTINATION = P_DEST
IMMEDIATELY = 'X'
IMPORTING
OUT_ARCHIVE_PARAMETERS = archive_parameters
OUT_PARAMETERS = print_parameters
VALID = valid_flag
EXCEPTIONS
INVALID_PRINT_PARAMS = 2
OTHERS = 4
Submit zrppt500
Using selection-set 'AUTO3'
With res_no eq lo_rsnum
with sreserv in preserv
to sap-spool
SPOOL PARAMETERS PRINT_PARAMETERS
ARCHIVE PARAMETERS ARCHIVE_PARAMETERS
WITHOUT SPOOL DYNPRO.
8. Error:
In case of Message Error; Number of WITH fields and number of Place Holders are not same .
Correction:
Split the statement after WITH into the same number as the place holder for that Message ID.
E.g.:
1. * MESSAGE E045.
MESSAGE E045 WITH '' ''.
2. in program ZIPI0801
     Start of change for ECC6
     message e398(00) with 'Could not find access sequence'
     'for condition type:'
     p_ptype.
message e398(00) with 'Could not find '
'access sequence'
'for condition type:'
p_ptype.
     End of change made for ECC6
9. Error:
In case of Move between 2 different Structures; The structures are not mutually convertible in a Unicode program.
Correction:
Make both the Data Types compatible and then assign the contents.
E.g.:
The statement move retainage_text to temp_text. Gives an error, where RETAINAGE_TEXT is an internal table and TEMP_TEXT is a string of length 200.
A Feasible solution for this is to specify from which position to which position of the string, the fields of RETAINAGE_TEXT should be assigned.
TEMP_TEXT+0(1) = RETAINAGE_TEXT-DQ1.
TEMP_TEXT+1(1) = RETAINAGE_TEXT-HEX.
TEMP_TEXT+2(20) = RETAINAGE_TEXT-FILLER1.
TEMP_TEXT+22(15) = RETAINAGE_TEXT-AMT_DUE.
TEMP_TEXT+37(8) = RETAINAGE_TEXT-TEXT.
TEMP_TEXT+45(10) = RETAINAGE_TEXT-DUE_DATE.
TEMP_TEXT+55(1) = RETAINAGE_TEXT-DQ2.
10. Error:
In case of no description found; add a GUI title.
Correction:
In this type of error gui title is generally missing so add a GUI title to the module pool.
11. Error:
In case of writing internal or transparent table
Correction:
Write individual fields.
E.g.:
WRITE: / EXT. --> EXT should be a character type field
WRITE: / EXT-ZZSTATE, EXT-LINE_NO, EXT-LINE_TXT, EXT-AMT, EXT-ZZSKUQTY.
12. Error:
In case of combination reference table/field S541-UMMENGE does not exist
Correction:
Was due to error in reference table S541. TABLE S541 has errors
1)Foreign key S541- ZZMARKET (ZZMARKET AND KATR2 point to different domains)
2)Foreign key S541-ZZACQUIGRP (ZZACQUIGRP AND KATR8 point to different domains)
Changed the domain of ZZMARKET (from ZMKCODE to ATTR2)
And that of ZMKCODE (from ZACCODE to ATTR8)
13. Error:
In case of KEY does not exist
Correction:
The reference table for field KBETR was KNOV earlier changed it to RV61A as KNOV was in turn referring to RV61A.
14. Error:
Incase of WRITE statement, Literals that take more than one line is not permitted in Unicode systems.
Correction: To correct this error, we need to align the spaces accordingly so that the statement doesnt go beyond the line.
15. Error:
Incase of Data statement, The data type ZWFHTML can be enhanced in any way. After a structure enhancement, this assignment or parameter might be syntactically incorrect..
Correction: To correct this error, instead of like in the Data statement, use type.
16. Error:
Incase of DESCRIBE statement, DESCRIBE can be used only with IN BYTE... Or IN CHARACTER mode in Unicode systems.
Correction: To correct this error, use additional text, IN BYTE MODE / IN CHARACTER MODE along with this statement.
CHARACTER MODE is added when the data object is of flat/ character type.
BYTE MODE is added when the data object is a deep structure.
Syntax: DESCRIBE FIELD data_obj : LENGTH blen IN BYTE MODE,
LENGTH clen IN CHARACTER MODE.
Where blen and clen must be of type I.
17. Error:
Incase of DO-LOOP Error, In Do loop range addition needed
Correction:
An internal tables is declared and the two fields (VARYING field and NEXT field) were
Included inside the internal table
E.g.: In program SAPMZP02
DO 11 TIMES
     VARYING STATION_STATE FROM STATION1 NEXT STATION2. ECC6
CASE SYST-INDEX.
WHEN 1
STATION_STATE = STATION1.
WHEN 2
STATION_STATE = STATION2.
WHEN 3
STATION_STATE = STATION3.
WHEN 4
STATION_STATE = STATION4.
WHEN 5
STATION_STATE = STATION5.
WHEN 6
STATION_STATE = STATION6.
WHEN 7
STATION_STATE = STATION7.
WHEN 8
STATION_STATE = STATION8.
WHEN 9
STATION_STATE = STATION9.
WHEN 10
STATION_STATE = STATION10.
WHEN 11
STATION_STATE = STATION11.
18. Error:
Incase of the parameter QUEUE-ID Error, QUEUE-ID is neither a parameter nor a select option in program rsbdcbtc.
Correction:
The parameter in program rsbdcbtc is QUEUE_ID and so is changed in this program
E.g.: In program Z_CARRIER_EDI_INTERFACE
     submit rsbdcbtc with queue-id = apqi-qid and return. "ECC6
     The parameter name changed by replacing '-' with '_' as in program rsbdcbtc "ECC6
Submit rsbdcbtc with queue_id = apqi-qid and return. "ECC6
19. Error:
Incase of EPC Error, Field symbol <TOT_FLD> is not assigned to a field .
Correction:
This error couldn't be rectified as the error occurs in a Standard SAP include- LSVIMF29.
The OS Note - 1036943 needs to be applied.
Error:
OPEN DATASET P_FILE FOR OUTPUT IN TEXT MODE.
Correct:
OPEN DATASET P_FILE FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
Error:
Constants : c_tab type x value '09' .
Correct:
Constants : c_tab type abap_char1 value cl_abap_char_utilities=>horizontal_tab .
Error:
Data : begin of output_options occurs 0 . Include structure ssfcompop.
Data : end of output_options .
Correct:
Data : output_options type standard table of ssfcompop with header line .
Error:
PARAMETERS : NAST TYPE NAST .
Correct:
PARAMETERS : NAST TYPE NAST NO-DISPLAY .
Replace WS_DOWNLOAD and WS_UPLOAD by
GUI_UPLOAD and GUI_DOWNLOAD and check the import and export parameter types , do the changes accordingly. Because FILENAME paramater type is different because of this it will give dump.
For issue during Issue using SO_NEW_DOCUMENT_ATT_SEND_API1 Function module, the solution is After this FM we should put COMMIT WORK.
Issue:
Moving data from one structure to another structure if those two structures are not compatible
Solution:
we should use move-corresponding or field by filed we need to move it.
If database structures are different in 4.6c and ECC6.0,
Then we should go with append structure concept.
While testing the report if it gives dump at Select query level or any database or view level,then just goto that table or view and goto the data base utility(se14) adjust the database. But make sure that selected radio button in se14 transaction should be activate and adjust database
Also Check this link.
http://help.sap.com/saphelp_nw04/helpdata/en/62/3f2cadb35311d5993800508b6b8b11/frameset.htm
Reward points if helpful.
Regards,
Ramya

How to write customer exit for the variable

Hi Experts,
I have a requirement to create the variable, the scenaria is like this..
I need to create the variable which gives the period/year values,if yours enters the values 05.2007 then the variable should return the first monthe the year i.e.01.2007.
I hope it can be done by writing the customer exit..but iam unware how to achieve this.
Please explain me step by step and cope for customer exit to done this.
Points will be awarded
Suraj.

hi Suraj,
there should variable sap exit for first month,
for customer exit, check this how to doc for steps
https://websmp210.sap-ag.de/~sapdownload/011000358700002762582003E/HowToDeriveVariableValue.pdf
your code may look like
INCLUDE ZXRSRU01                                                   *
DATA: L_S_RANGE TYPE RSR_S_RANGESID.
DATA: LOC_VAR_RANGE LIKE RRRANGEEXIT.
CASE I_VNAM.
WHEN 'your 1st month variable'.
    IF I_STEP = 2.                                  "after the popup
      LOOP AT I_T_VAR_RANGE INTO LOC_VAR_RANGE
              WHERE VNAM = 'your user input variable'.
        CLEAR L_S_RANGE.
        L_S_RANGE-LOW      = LOC_VAR_RANGE-LOW(4)."low value, e.g.200001
        L_S_RANGE-LOW+4(2) = '01'.
        L_S_RANGE-SIGN     = 'I'.
        L_S_RANGE-OPT      = 'EQ'.
        APPEND L_S_RANGE TO E_T_RANGE.
        EXIT.
      ENDLOOP.
    ENDIF.
ENDCASE.
hope this helps.

Code for Customer exit in a variable is required

Hi Guys,
Document numbers are flowing in to two OD's. These doc numbers are available in 'X' and 'Y' ODS's.
We are missing some doc nos both the ODS's. we want to display those doc nos in a report.
We Created an infoset on these two ODS's.We want to write a Code for the Ccustome exit on this document number.
Can anybody suggest how to get these doc nos in areport.
Can anybody help me in writing a code on customer exit.
Pleas give suggestions how to display rhes doc nos in areport.
Thanks,
Nela

Hi,
case I_VNAM.
when 'ZPRYRPER'.
if I_STEP = '2'.
loop at i_t_var_range into temp.
append temp.
endloop.
read table temp with key vnam = '0S_FPER'.
if sy-subrc eq 0.
move temp-low to l1_period.
move temp-high to l_period.
endif.
if l_period-gjahr = 0000.
l_period-gjahr = 2020.
endif.
if l1_period-gjahr = 0001.
l1_period-gjahr = 1990.
endif.
CLEAR E_T_RANGE_WA.
l1_period-buper = '001'.
l_period-gjahr = l_period-gjahr - 1.
l1_period-gjahr = l_period-gjahr.
E_T_RANGE_WA-SIGN = 'I'.
E_T_RANGE_WA-OPT = 'BT'.
E_T_RANGE_WA-HIGH = L_PERIOD.
E_T_RANGE_WA-LOW = L1_PERIOD.
APPEND E_T_RANGE_WA TO E_T_RANGE.
endif.
Regards,
Marasa.

Migrating Customer exit for BEX variables to BADI's

Hi All,
I am new to ABAP In the context of BW.
I am using exit RSR00001 to populate variables in BEX reports.
I want to migrate this customer exit RSR00001 to BADI.
Can any one please tell me how to migrate the same and how it will fire in place of exit?
Thanks In Advance
Dhananjay

Hi,
Please have a look at:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f1a7e790-0201-0010-0a8d-f08a4662562d
Krzys

Text Variable through Customer Exit using FM MONTH_NAMES_GET

Hi Friends,
I have a query which runs through a variable Key date(ZPDATE). (Key date may also be changed by the user).
I have another customer exit variable(ZVNDATE1) where it reads from the Keydate variable and it represents one month less than the key date and it holds two dates first day of month and last day of month.
Let say: Key date(ZPDATE) = 12.03.2008
             ZVNDATE1 = 01.02.2008 and 28.02.2008
I have created RKF Overdues-1 ristricted with ZVNDATE1.
My requirement is I wan to represent this RKF Overdues-1 as Feb 2008 . In order to do that I want to create a Text variable(ZTEXT1) using customer exit .
As I am not very good in ABAP please can anybody provide me the code for text variable:
I am writing in the below.. but I dont know how to represent FM..etc..
WHEN 'ZTEXT1'.
        READ TABLE i_t_var_range INTO w_var_range WITH KEY vnam = 'ZVNDATE1'.
        IF SY-SUBRC = 0.
          CLEAR l_s_range.
          l_date = w_var_range-low.
                   CALL FUNCTION MONTH_NAMES_GET'
Please can you provide me the remaing code..
Thanks
Sudhakar..

Hi Sudhakar,
Instead what you can do is, add few more lines of code instead of calling fm.
case 'month'.
If month = '1'.
desc = 'jan'.
elseif month = '2'.
desC = 'feb'.
endcase.
concatenate desc year into w_v_range-low.
Hope that helps.
Thanks

Variable multiple single value filled with customer exit used in FOX form.

Hi guys, I definitly need your help in the following scenario:
I have variable (multiple single value) filled in a customer exit and use it in web template. There it is used in the drop down box for selecting a special date in the analysis item. And there comes the first question:Why the results from the customer exit are written in the way "date1; date2; date3" in one line? They should appear line by line in rows. How can I influence that? I tried both data binding types, "variable" and "characteristic".
Now a button raises a planning function with a fox formula which should write the selected date (from the drop down box) in a customer table using "call function".
I always get the error, that I need to restrict the variable to "single value". Why do I have to do that and if necessary how can I do that? Other planning functions without the fox formula also work properly with using the selection from the drop down box.
I appreciate you help.
Kind regards, Anja.

Hi Vamsi.,
Try this code.
WHEN 'PREVIOUS_YEAR_1'.
IF I_STEP = 2. "after the popup of user entry
LOOP AT I_T_VAR_RANGE INTO LOC_VAR_RANGE
WHERE VNAM = 'ZCURRENT_YEAR_PERIOD'.
break-point.
IF SY-SUBRC EQ 0.
WA_YEAR = LOC_VAR_RANGE-LOW+0(4). "Year
WA_MONTH = LOC_VAR_RANGE-LOW+5(3). "Period
WA_YEAR = WA_YEAR - 1.
CONCATENATE WA_YEAR wa_month INTO WA_FISC_PERD .
CONCATENATE WA_YEAR WA_MONTH1 INTO L_S_RANGE-HIGH .
L_S_RANGE-SIGN = 'I'.
L_S_RANGE-OPT = 'EQ'.
APPEND L_S_RANGE TO E_T_RANGE.
ENDIF.
L_S_RANGE-SIGN = 'I'.
L_S_RANGE-OPT = 'BT'.
APPEND L_S_RANGE TO E_T_RANGE.
ENDIF.
ENDIF.
ENDLOOP.
endif.
Assing points if it helps you.
-- Selva

Give me details about customer exit, sap exit using characterstics variabl

Similar Messages

Maybe you are looking for