Doubt About Function Module

Hi Experts,
I want one function module which wil allows us to attach a attachment to the material in the SAP PLM System.
Please clear my doubt . Why Because i got strucked here in this issue of selecting a right Function Module.
Please clear my doubt. Helpful ANswers wil be Reward.
Regards
Khanna

Hi khanna,
try this MATERIAL_MAINT_DIAL_GET_DOC Functional Module for attachment in Material Master,
In DIR try this CV110_DOC_ASSIGN_FILE,
Regards
Rehman

Similar Messages

Doubt in function module BAL_DSP_LOG_DISPLAY

Hai, guys,
i have doubt in the function module BAL_DSP_LOG_DISPLAY.
actually after executing the functin module bapi_acc_document_post, how to pass bapi return table to this function module bal_dsp_log_display.
if any one know means please tell me with sample coding.
thanks in advance.
From Elamaran.

Hi Elamaran!
Did you try to use SE37 with this module and use "Where-Used List" (CTRL + SHIFT + F3)? This should give you enough examples to look through.
Best regards
Wolfgang
Message was edited by: Ralf Wolfgang Geithner

About function module in alv

hai all
iwant to know about few function modules in alv
1) reuse_alv_default_varients_get.
2)reuse alv_varients_f4
what is the use of these function modules
how to use these function modules, what r the structures used to use these function module. where to pass this in
in list and grid display function modules.
plz help me.
thanks & regards
sindu

HI,
check this.
REPORT Z_TEST_alv_variant .
TYPE-POOLS : SLIS.
PARAMETERS: ONE RADIOBUTTON GROUP G1 DEFAULT 'X',
            TWO RADIOBUTTON GROUP G1.
DATA: BEGIN OF I_TAB OCCURS 0,
FIELD1 TYPE I,
FIELD2 TYPE I,
END OF I_TAB.
DATA: GT_FIELDCAT TYPE SLIS_T_FIELDCAT_ALV,
      LS_FIELDCAT TYPE SLIS_FIELDCAT_ALV.
DATA: L_VARIANT TYPE DISVARIANT,
      LX_VARIANT LIKE DISVARIANT,
      L_SAVE TYPE C,
      L_EXIT(1) TYPE C.
SELECTION-SCREEN BEGIN OF BLOCK 0 WITH FRAME TITLE TEXT-VAR.
PARAMETERS: P_VARI LIKE DISVARIANT-VARIANT.
SELECTION-SCREEN END OF BLOCK 0.
INITIALIZATION.
L_SAVE = 'A'.
PERFORM VARIANT_INIT.
Get default variant
LX_VARIANT = L_VARIANT.
CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'
    EXPORTING
      I_SAVE     = L_SAVE
    CHANGING
      CS_VARIANT = LX_VARIANT
    EXCEPTIONS
      NOT_FOUND = 2.
IF SY-SUBRC = 0.
    P_VARI = LX_VARIANT-VARIANT.
ENDIF.
Process on value request
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_VARI.
PERFORM F4_FOR_VARIANT.
I_TAB-FIELD1 = 19.
I_TAB-FIELD2 = 20.
APPEND I_TAB.
I_TAB-FIELD1 = 19.
I_TAB-FIELD2 = 20.
APPEND I_TAB.
I_TAB-FIELD1 = 19.
I_TAB-FIELD2 = 20.
APPEND I_TAB.
I_TAB-FIELD1 = 19.
I_TAB-FIELD2 = 20.
APPEND I_TAB.
I_TAB-FIELD1 = 19.
I_TAB-FIELD2 = 20.
APPEND I_TAB.
PERFORM INITIALIZE_FIELDCAT USING GT_FIELDCAT[].
PERFORM CALL_ALV TABLES I_TAB[]
                   USING GT_FIELDCAT.
*& Form initialize_fieldcat
text
-->P_GT_FIELDCAT[] text
FORM INITIALIZE_FIELDCAT USING L_FIELDCAT TYPE SLIS_T_FIELDCAT_ALV.
LS_FIELDCAT-FIELDNAME = 'FIELD1'.
LS_FIELDCAT-KEY = 'X'.
LS_FIELDCAT-COL_POS = 1.
LS_FIELDCAT-SELTEXT_S = 'Work center'.
LS_FIELDCAT-SELTEXT_L = 'Work center'.
APPEND LS_FIELDCAT TO L_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME = 'FIELD2'.
LS_FIELDCAT-KEY = ' '.
LS_FIELDCAT-COL_POS = 2.
LS_FIELDCAT-SELTEXT_S = 'Work center2'.
LS_FIELDCAT-SELTEXT_L = 'Work center2'.
APPEND LS_FIELDCAT TO L_FIELDCAT.
CLEAR LS_FIELDCAT.
ENDFORM. " initialize_fieldcat
*&      Form call_alv
      text
     -->P_GT_FIELDCAT text
     -->P_I_TAB text
FORM CALL_ALV TABLES   P_TAB
                USING    P_GT_FIELDCAT .
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
      I_CALLBACK_PROGRAM = SY-REPID
      IT_FIELDCAT        = P_GT_FIELDCAT
      I_DEFAULT          = 'X'
      IS_VARIANT         = L_VARIANT
      I_SAVE             = L_SAVE
    TABLES
      T_OUTTAB           = P_TAB[]
    EXCEPTIONS
      PROGRAM_ERROR      = 1
      OTHERS             = 2.
IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    " call_alv
*&      Form VARIANT_INIT
      text
FORM VARIANT_INIT.
CLEAR L_VARIANT.
L_VARIANT-REPORT = SY-REPID.
ENDFORM.                               " VARIANT_INIT
*&      Form variant_SELECTION_SCREEN
      text
FORM VARIANT_SELECTION_SCREEN .
IF NOT P_VARI IS INITIAL.
    MOVE L_VARIANT TO LX_VARIANT.
    MOVE P_VARI TO LX_VARIANT-VARIANT.
    CALL FUNCTION 'REUSE_ALV_VARIANT_EXISTENCE'
      EXPORTING
        I_SAVE     = L_SAVE
      CHANGING
        CS_VARIANT = LX_VARIANT.
    L_VARIANT = LX_VARIANT.
ELSE.
    PERFORM VARIANT_INIT.
ENDIF.
ENDFORM.                    " variant_SELECTION_SCREEN
*&      Form F4_FOR_VARIANT
      text
FORM F4_FOR_VARIANT.
CALL FUNCTION 'REUSE_ALV_VARIANT_F4'
    EXPORTING
      IS_VARIANT = L_VARIANT
      I_SAVE     = L_SAVE
    IMPORTING
      E_EXIT     = L_EXIT
      ES_VARIANT = LX_VARIANT
    EXCEPTIONS
      NOT_FOUND = 2.
IF SY-SUBRC = 2.
    MESSAGE ID SY-MSGID TYPE 'S'      NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ELSE.
    IF L_EXIT = SPACE.
      P_VARI = LX_VARIANT-VARIANT.
    ENDIF.
ENDIF.
ENDFORM.                    "F4_FOR_VARIANT
Regards,
Laxmi.

About Function module reltate to Enhancement

Hi All,
i need to know about the Usage and purpose of the function module FKK_BP_BADI_UPDATE.
Kindly help me to know about this function module

Hi Venkat,
The function module BAPI_CUBE_GETDETAIL provides you the detials of infocube (including dimension, characteristics, keyfigures etc).
Moreoverthis FM is RFC enabled; so you can call this FM from DEV and pass RFC connection of PROD to get detials of the cube in prod. This compare the structures between DEV and PROD.
Similarly you can use BAPI_ODSO_GETDETAIL from DSO structure comparision across the system landscape.
Thanks
Vasu

Table that stores information about function module

Hi All,
I know that table TFDIR stores primary information about any function module.
Could anyone tell me where the code of that function module gets stored in?
Also.. If I want to write an ABAP code to read the function module code then what is the best possible solution?
Thanks in advace and any answer will be appreciated.
Regards
Jignesh

Hi All,
Apologies for the same!
The codes are not stored in any table, they are stored as cluster.
To read the code, you can use READ REPORT.
But there you must provide the Include Name For Example , If you want to read the code of READ_TEXT,
READ REPORT 'LSTXDU01'.
You can get this include name inside include LSTXDUXX
Table TFDIR also stores the program name and include number.
You need to truncate first 3 char 'SAP' and append UXX at the end and that will be your program name.
Then we can use READ REPORT!!!
Regards
Jignesh

About function module for personnel no

is there any function module to provide search help for personnel no with search criterias.similarly for applicant nos also.can one help on this.

Hello Murthy,
I have read all the three of your latest posts. And they all seem very much related to me. I shall try to explain things out to you. Please get back with doubts and / or reward points :-).
For Personnel Number, you can use the search help <b>PREM</b> provided by SAP.
For Applicant No., the standard search help is <b>PAPM</b>.
You just need to attach these search helps to your screen elements.
Regards,
Anand Mandalika.

ABOUT FUNCTION MODULE (urgent)

hi ,
is any one know about below function module.
CUST_ACCT_STMT_REQUEST_LITE
we schedule customer account statement in th background.
we want to add some functionality.
if any one know anything then it will be appreciated.
thans,
jack

Hi,
I am giving the Function Modules list link, from there you can findout which is suitable for your application:
http://sap-img.com/abap/function-list.htm
Regards,
Bhaskar

Doubt on function module

in function module how to export all the fields in a table ..
i.e. i am giving these fields..
in
IMPORT
P_EBELN LIKE EKKO-EBELN
IN
EXPORT
BUKRS LIKE EKKO-BUKRS
and in source code
SELSCT SINGLE BUKRS INTO BUKRS
WHERE EBELN = EBELN.
and i am getting for one record
but if i want to export more than one columns
how to code it in source code.
and what is the use of TABLES in FM
AND HOW TO EXPORT full table columns ?
and how to code it ...
plz help me .......

Hi
See the doc on fun modules and create accordingly
Function Modules;
Check this matter.
Function Modules are Global ABAP programs created by SAP for reusable purpose.they have IMPORT,EXPORT and TABLE parameters, and EXCEPTIONS to through when error occurs.
You can create them from TCode SE37.
Go through the following doc:
Function modules are cross-program, reusable procedures that are organized into function groups, and whose functions are implemented between the statements FUNCTION and ENDFUNCTION. Function modules and their interfaces are created in the Function Builder.
Function Module Interfaces
The parameter interface of a function module is defined in the Function Builder. It includes the definition of interface parameters and the specification of exceptions that can be triggered by a function module. The Function Builder automatically generates comment lines below the FUNCTION statement in the source code of the function module, which represent the interface of the function module with the following syntax:
Syntax
... [IMPORTING parameters]
[EXPORTING parameters]
[CHANGING parameters]
[TABLES table_parameters]
[{RAISING|EXCEPTIONS} exc1 exc2 ...]
The syntax and semantics of IMPORTING, EXPORTING, CHANGING, RAISING, and EXCEPTIONS mainly correspond to the definition of method interfaces with [CLASS-]METHODS. The additional option of defining table parameters using TABLES is obsolete.
Interface parameters
The interface parameters are defined on the relevant tab pages in the Function Builder.
IMPORTING parameters are input parameters. When the function module is called, a suitable actual parameter must be specified for every non-optional input parameter. The content of the actual parameter is passed to the input parameter when the call is made. The content of an input parameter for which 'pass by reference' is defined cannot be changed in the function module.
EXPORTING parameters are output parameters. When the function module is called, a suitable actual parameter can be specified for every output parameter. The content of an output parameter that is defined for 'pass by value' is transferred to the actual parameter if the function module is completed without errors. An output parameter that is defined for pass by reference is not initialized when the function module is called.
CHANGING parameters are input and output parameters. When the function module is called, a suitable actual parameter must be specified for every non-optional input or output parameter. When the function module is called, the content of the actual parameter is passed to the input/output parameter, and when the function module is completed, the content of the input/output parameter is passed to the actual parameter.
TABLES parameters are table parameters. Table parameters are obsolete CHANGING parameters that are typed as standard tables with a header line. If an internal table without a header line or a table body is passed as an actual parameter to a formal parameter of this type, an empty local header line is generated in the function module. If an internal table with a header line is used as an actual parameter, both the table body and the header line are passed to the function module. Pass by value is not possible in formal parameters defined using TABLES. Formal parameters defined with TABLES can be replaced by formal parameters defined with CHANGING. A local work area can be created for the internal table in the function module by using the addition LIKE LINE OF itab of the DATA statement.
Exceptions
The exception of a function module are defined on the Exceptions tab page in the Function Builder. Here you can select exception classes to define whether class-based exceptions are declared or non-class-based exception are defined. Class-based exceptions are represented in the above syntax by RAISING, and non-class-based exceptions are represented by EXCEPTIONS.
The addition RAISING is used to declare class-based exceptions that can be propagated from the function module to the caller. Exceptions in the categories CX_STATIC_CHECK and CX_DYNAMIC_CHECK must be explicitly declared, otherwise a propagation can lead to an interface violation. A violation of the interface leads to the treatable exception CX_SY_NO_HANDLER. Exceptions of the category CX_NO_CHECK are implicitly always declared. The declaration of exceptions of the category CX_STATIC_CHECK is statically checked in the syntax check. For exceptions of the category CX_DYNAMIC_CHECK, the check is not performed until runtime. In a function module in which class-based exceptions are declared with the RAISING addition, the statement CATCH SYSTEM-EXCEPTIONS cannot be used. Instead, the relevant treatable exceptions should be handled in a TRY control structure.
The addition EXCEPTIONS is used to define a list of non-class-based exceptions that can be triggered in the function module using the statements RAISE or MESSAGE RAISING. Exceptions defined in this way - as with formal parameters - are bound to the function module and cannot be propagated. If an exception of this type is triggered in a function module, and no return value has been assigned to it with the homonymous addition EXCEPTIONS of the CALL FUNCTION statement when the call was made, this leads to a runtime error.
Note
For new developments after release 6.10, SAP recommends that you work with class-based exceptions that are independent of the function module.
RFC is a technology which is used to access a functions (Modules) from
the remote systems.
If a function module is set as remote enabled which can be access from
the remote system via RFC.Eg: U can access the Remote enabled function modules in ur VB,Webdynpro,Java,Visual composer program.
A function module can be set as remote enabled by SE37->Go to ur FM->click the option Button "remote enabled".
But Normal function modules can not accessd from the remote system.
Good Example for RFC enabled function module is : BAPI(Business Application Programming Interface)
Note: All BAPIs are Remote enabled but not all remote enabled function modules are BAPI.
CALLING A FUNCTION MODULE:
1)In U ABAP Editor --> Click "Patter" ---> Selection Option Button "Call Function"
--> Write the Corresponding FM name --> Hit Enter
2)The appropriate import ,export Parameters will be displayed in ur editor
3)Pass the Values Here.
Also check these links.
http://www.geocities.com/victorav15/sapr3/abapfun.html
Check this link:
http://help.sap.com/saphelp_erp2004/helpdata/en/9f/db988735c111d1829f0000e829fbfe/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/ef/d94b78ebf811d295b100a0c94260a5/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/41341147041806e10000000a1553f6/frameset.htm
Check this link:
http://help.sap.com/saphelp_erp2004/helpdata/en/9f/db988735c111d1829f0000e829fbfe/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/ef/d94b78ebf811d295b100a0c94260a5/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/41341147041806e10000000a1553f6/frameset.htm
See the following links:
http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/26/64f623fa8911d386e70000e82011b8/content.htm
<b>Reward points for useful Answers</b>
Regards
Anji

About Function module 'PRICING'

Hi experts,
Now My requirement is get all contract condition data. If I don't want to create a new contract to get these condition data, I can use Function module 'PRICING' to get all condition data. But the question is the parameter COMM_ITEM_I is a structure, it only can store a record(single material). If the contract has many item, eg Service + Goods............ How to process this scenario? If you have experience in this, please give me any idea. Thanks in advance!
function pricing.
""Globale Schnittstelle:
*" IMPORTING
*"     VALUE(CALCULATION_TYPE) LIKE KOMV-KSTEU DEFAULT 'A'
*"     VALUE(COMM_HEAD_I) LIKE KOMK STRUCTURE KOMK
*"     VALUE(COMM_ITEM_I) LIKE KOMP STRUCTURE KOMP
*"     VALUE(PRELIMINARY) TYPE C DEFAULT ' '
*"     VALUE(NO_CALCULATION) TYPE C DEFAULT ' '
*" EXPORTING
*"     VALUE(COMM_HEAD_E) LIKE KOMK STRUCTURE KOMK
*"     VALUE(COMM_ITEM_E) LIKE KOMP STRUCTURE KOMP
*" TABLES
*"      TKOMV STRUCTURE KOMV
*"      SVBAP STRUCTURE VBAPU OPTIONAL
*" CHANGING
*"     VALUE(REBATE_DETERMINED) TYPE C DEFAULT ' '

Hi,
I guess contracts will be found in EKKO, not in VBAK. Correct me if I am wrong.
If I am correct, you can use the BAPI "BAPI_PO_GETDETAIL1". POCONDHEADER and POCOND inporting tables will retrieve pricing information.
Regards,
Ganga

Query about Function Module 'RSPO_RETURN_SPOOLJOB'

Hi all,
     I am currently working on a report that takes the SPOOL NO. for the back ground runned job and passes to the Function module 'RSPO_RETURN_SPOOLJOB' that gives the data in BUFFER after reading this data I am converting it to the excel format and sending it as an attached mail to the specified recepient.
     But the FM mentioned is getting data in weird manner. I am converting it to excel format as we do for the normal internal table data being converted to excel format. But the problem is ragarding the data...
     Is there a way to covert this data into excel format? Or is there any other function Module that converts the data into excel format for the job. If it is there then let me know...
regards,
Brijesh Patel

I have not used this myself, but check if this works for you.
RSPO_DOWNLOAD_SPOOLJOB
Regards,
Ravi
Note : Please mark the helpful answers

Doubt in function module...Urgent!!

hii all
     I want to find the difference between sy-datum and BLDAT and have to get only the days value...
for eg...
    sydatum(28.11.2007) - bldat(24.11.2007)= Days(4)
4 must the result... so i used the function module C14B_DIFF_BT_2_DATES..
but im unable to get the result...
my code is.....
*& Report ZAGE1
REPORT ZAGE1.
type-pools : slis,icon.
tables : bsid,kna1,knvv.
data : d_fieldcat type slis_t_fieldcat_alv,
       d_fieldcat_wa type slis_fieldcat_alv.
data : begin of itab_bsid occurs 0,
       kunnr like bsid-kunnr,
       bukrs like bsid-bukrs,
       bldat like bsid-bldat,
       waers like bsid-waers,
       belnr like bsid-belnr,
       end of itab_bsid.
data : begin of itab_kna1 occurs 0,
       kunnr like kna1-kunnr,
       end of itab_kna1.
data : begin of itab_knvv occurs 0,
       kunnr like knvv-kunnr,
       zterm like knvv-zterm,
       end of itab_knvv.
data : begin of itab_key occurs 0,
        kunnr like bsid-kunnr,
       bukrs like bsid-bukrs,
       bldat like bsid-bldat,
       waers like bsid-waers,
       belnr like bsid-belnr,
       zterm like knvv-zterm,
       due type i,
       end of itab_key.
selection-screen : begin of block blk1 with frame title text-001.
parameters : p_cc like bsid-bukrs.
selection-screen : end of block blk1.
select distinct kunnr bukrs bldat waers belnr from bsid into corresponding fields of table itab_bsid where bukrs = p_cc.
if not itab_bsid[] is initial.
select kunnr from kna1 into corresponding fields of table itab_kna1 for all entries in itab_bsid where kunnr = itab_bsid-kunnr.
if not itab_kna1[] is initial.
select kunnr zterm from knvv into corresponding fields of table itab_knvv for all entries in itab_kna1 where kunnr = itab_kna1-kunnr.
endif.
endif.
     loop at itab_bsid.
     itab_key-kunnr = itab_bsid-kunnr.
     itab_key-bukrs = itab_bsid-bukrs.
     itab_key-bldat = itab_bsid-bldat.
     itab_key-waers = itab_bsid-waers.
     itab_key-belnr = itab_bsid-belnr.
     append itab_key.
     clear itab_key.
     endloop.
     sort itab_key by kunnr.
     loop at itab_key.
     read table itab_knvv with key kunnr = itab_key-kunnr.
     if sy-subrc = 0.
     itab_key-zterm = itab_knvv-zterm.
     modify itab_key transporting zterm.
     endif.
     endloop.
    d_fieldcat_wa-fieldname = 'KUNNR'.
    d_fieldcat_wa-seltext_l = 'CUSTOMER'.
    d_fieldcat_wa-col_pos = 1.
    append d_fieldcat_wa to d_fieldcat.
    clear d_fieldcat_wa.
     d_fieldcat_wa-fieldname = 'BUKRS'.
    d_fieldcat_wa-seltext_l = 'COMPANY CODE'.
    d_fieldcat_wa-col_pos = 2.
    append d_fieldcat_wa to d_fieldcat.
    clear d_fieldcat_wa.
     d_fieldcat_wa-fieldname = 'WAERS'.
    d_fieldcat_wa-seltext_l = 'CURRENCY'.
    d_fieldcat_wa-col_pos = 3.
    append d_fieldcat_wa to d_fieldcat.
    clear d_fieldcat_wa.
     d_fieldcat_wa-fieldname = 'BLDAT'.
    d_fieldcat_wa-seltext_l = 'DOCUMENT DATE'.
    d_fieldcat_wa-col_pos = 4.
    append d_fieldcat_wa to d_fieldcat.
    clear d_fieldcat_wa.
     d_fieldcat_wa-fieldname = 'BELNR'.
    d_fieldcat_wa-seltext_l = 'DOCUMENT NO'.
    d_fieldcat_wa-col_pos = 5.
    append d_fieldcat_wa to d_fieldcat.
    clear d_fieldcat_wa.
     d_fieldcat_wa-fieldname = 'ZTERM'.
    d_fieldcat_wa-seltext_l = 'PAYMENT TERMS'.
    d_fieldcat_wa-col_pos = 6.
    append d_fieldcat_wa to d_fieldcat.
    clear d_fieldcat_wa.
*data : due type i.
loop at itab_key.
   CALL FUNCTION 'C14B_DIFF_BT_2_DATES'
     EXPORTING
       I_DATE_FROM                     = itab_key-bldat
       I_DATE_TO                       = sy-datum
    IMPORTING
      E_DAYS                          = itab_key-due
     E_MONTHS                        = months
    E_YEARS                         = years
   EXCEPTIONS
     PLAUSIBILITY_CHECK_FAILED       = 1
     OTHERS                          = 2
   IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
   ENDIF.
append itab_key.
endloop.
    d_fieldcat_wa-fieldname = 'DUE'.
    d_fieldcat_wa-seltext_l = 'DUE DATE'.
    d_fieldcat_wa-col_pos = 7.
    append d_fieldcat_wa to d_fieldcat.
    clear d_fieldcat_wa.
    data : gd_repid like sy-repid.
    gd_repid = sy-repid.
    CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
     EXPORTING
      I_INTERFACE_CHECK                 = ' '
      I_BYPASSING_BUFFER                = ' '
      I_BUFFER_ACTIVE                   = ' '
       I_CALLBACK_PROGRAM                = gd_repid
      I_CALLBACK_PF_STATUS_SET          = ' '
      I_CALLBACK_USER_COMMAND           = ' '
      I_CALLBACK_TOP_OF_PAGE            = ' '
      I_CALLBACK_HTML_TOP_OF_PAGE       = ' '
      I_CALLBACK_HTML_END_OF_LIST       = ' '
      I_STRUCTURE_NAME                  =
      I_BACKGROUND_ID                   = ' '
      I_GRID_TITLE                      =
      I_GRID_SETTINGS                   =
      IS_LAYOUT                         =
       IT_FIELDCAT                       = d_fieldcat
      IT_EXCLUDING                      =
      IT_SPECIAL_GROUPS                 =
      IT_SORT                           =
      IT_FILTER                         =
      IS_SEL_HIDE                       =
      I_DEFAULT                         = 'X'
      I_SAVE                            = ' '
      IS_VARIANT                        =
      IT_EVENTS                         =
      IT_EVENT_EXIT                     =
      IS_PRINT                          =
      IS_REPREP_ID                      =
      I_SCREEN_START_COLUMN             = 0
      I_SCREEN_START_LINE               = 0
      I_SCREEN_END_COLUMN               = 0
      I_SCREEN_END_LINE                 = 0
      I_HTML_HEIGHT_TOP                 = 0
      I_HTML_HEIGHT_END                 = 0
      IT_ALV_GRAPHICS                   =
      IT_HYPERLINK                      =
      IT_ADD_FIELDCAT                   =
      IT_EXCEPT_QINFO                   =
      IR_SALV_FULLSCREEN_ADAPTER        =
    IMPORTING
      E_EXIT_CAUSED_BY_CALLER           =
      ES_EXIT_CAUSED_BY_USER            =
      TABLES
        T_OUTTAB                          = itab_key[]
    EXCEPTIONS
      PROGRAM_ERROR                     = 1
      OTHERS                            = 2
    IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
Urgent plz help me....!!
Regards
Asha

Check the following code for subtract years/months/date from particular date:
DATA: EDAYS LIKE VTBBEWE-ATAGE,
EMONTHS LIKE VTBBEWE-ATAGE,
EYEARS LIKE VTBBEWE-ATAGE.
PARAMETERS: FROMDATE LIKE VTBBEWE-DBERVON,
TODATE LIKE VTBBEWE-DBERBIS DEFAULT SY-DATUM.
call function 'FIMA_DAYS_AND_MONTHS_AND_YEARS'
exporting
i_date_from = FROMDATE
i_date_to = TODATE
I_FLG_SEPARATE = ' '
IMPORTING
E_DAYS = EDAYS
E_MONTHS = EMONTHS
E_YEARS = EYEARS.
WRITE:/ 'Difference in Days ', EDAYS.
WRITE:/ 'Difference in Months ', EMONTHS.
WRITE:/ 'Difference in Years ', EYEARS.
INITIALIZATION.
FROMDATE = SY-DATUM - 60.
For difference between two dates.
data : date1 like sy-datum,
date2 like sy-datum,
diff(10 ) type c.
date1 = '20071003'.
date2 = '20071104' .
CALL FUNCTION 'DAYS_BETWEEN_TWO_DATES'
EXPORTING
I_DATUM_BIS = date1
I_DATUM_VON = date2
I_KZ_EXCL_VON = '0'
I_KZ_INCL_BIS = '0'
I_KZ_ULT_BIS = ' '
I_KZ_ULT_VON = ' '
I_STGMETH = '0'
I_SZBMETH = '1'
IMPORTING
E_TAGE = diff
EXCEPTIONS
DAYS_METHOD_NOT_DEFINED = 1
OTHERS = 2
IF SY-SUBRC <> 0 .
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF .

Doubt In Function module : Write_Form_Lines in Sap Scripts

Friends,
I wanted to know for what purpose the funtion module Write_Form_Lines is used in SAP SCRIPTS.
Regards
Yamini

From SAP documentation:
The function module outputs the text lines in table LINES into the specified form window. The text lines must have the SAPscript ITF format. From the data in the text header, the system uses only the field TDSTYLE to apply the formatting attributes defined in the specified style for this text. If the field is empty, the system uses the identically named formatting attributes (character and paragraph formats) of the form.
Use parameter WINDOW to specify into which of the windows defined in the form you want to output the text. You can specify any window used in the form. The parameter FUNCTION determines how to merge the text lines to be output with any existing contents in the window. There are differences between the different window types or areas.
Prabhu Rajesh.

Doubt in function module relating to delta upload

Hi,
Is there any ABAPer alive around who can tell me how i can write a funtion module to update data to BW side.
They only tell me data is not going to BW side. Can anyone throw light as to how function module should be structured. I have a function module that works very finely for full update mode in RSA3. What should be done in my function module for delta update mode to work on BW side?????
<h1> THIS IS CRITICAL </h1>
Regards,
Prakash.K

Critical? Why? Should I respond faster because you've a problem that's urgent for you?
Does full extraction work when you run the extraction from BW? Extraction only stops when you return an empty package. Hence, RSA3 won't tell you if you've made this mistake. RSA3 will work fine, but the extraction will never end when run from BW. I refer you to this discussion I had earlier. [Re: Transport Organ9izer] I'll emphasise one important point: Also SAP supply RSAX_BIW_GET_DATA_SIMPLE as an example of how to write FM extractors
If your FM is actually working with full, then to get your function module to work as a delta load, you need to be able to determine which data records have changed with since the last extraction, and only send those. How you do this depends very much on the data. You'll also have to define the datasource as Generic.
matt

Doubt on Function Modules

Hi Experts,
I am creating one user defind function module. When i am giving table parameters,
For example
git_out like vbak
it shows the error tables are obsolete..
Please can any one tell me whats that error and any one tell me how to do that one..
Thanks in Advance
Thanks and Regards
Srihari.

Hi,
As suggsted you need to move the parameter to CHANGING parameters.
Since you are referenceing VBAK, but need a table, you need to refer the parameter to a table type.
Hence in CHANGING parameter you put as so:
git_out TYPE TAB_VBAK.
After this, you would have to create a work area for the table in the code and always loop at the git_out into this work area for all operations.
The work area should have type VBAK.
Also, when calling the FM from program, you need to pass the body of the internal table to this parameter, i.e. if internal table is it_vbak, then you need to pass it_vbak[].
Regards,
Aditya
Edited by: Aditya Laud on Feb 5, 2008 6:50 AM

Question about Function Module ME_PO_PRICE_SIMULATION

Hi experts,
I am trying to solve an issue concerning the importing parameter I_ROLL_BACK of the function module ME_PO_PRICE_SIMULATION.
Inside the coding of the user-exit ZXM06U44 (executed after saving a purchase order) there is a call to the function module ME_PO_PRICE_SIMULATION with this importing parameter set to true. In that case, purchase order is not created. Otherwise if I modify this value into false the order is created appropriately.
Could someone more functional explain me what is the meaning of this parameter. I try to read the documentation but is in German, so I don't understand anything.
Lots of thanks,
Javier

This is what happens inside the FM using I_ROLL_BACK:
To understand what a rollback statement does, have a look at this:
https://help.sap.com/abapdocu_70/en/ABAPROLLBACK.htm

Doubt About Function Module

Similar Messages

Maybe you are looking for