How to incoporate a function module in data source based on view

Hi,
I need to develop a data source in R/3 based on a view (which is straight forward).
One field in the R/3 Z table will be in like this 20,070,709,110,000
There is a function module developed in R/3 when executed will split the record(20,070,709,110,000) and display time & date
How can i incorporate this function module in data source so that the data and time records will be loaded to BW
Thanks

Enhance the data source with date and time and populate these fields in the user exit using the function module IB_CONVERT_FROM_TIMESTAMP .
OR
You can create Z function module IB_CONVERT_FROM_TIMESTAMP in BW side and write a routine in update rules/transfer rules to populate date and time.
hope this helps ...
Ravi

Similar Messages

Delta field for generic data source based on view EKBE

Hello,
I am creating a generic datasource based on table EKBE. Can anyone please tell me what field should I use for delta. Is it BUDAT(Posting Date in the Document) or CPUDT(Day On Which Accounting Document Was Entered).
Thanks for the help.
Praveen

Hello Ajeet Singh,
Thank you very much for the reply.
I will go ahead with CPUDT.
BUDAT is the date which can be changed. I can change the date in system and chances are it will not pick in delta.
CPUDT is the date on which document was created/changed.
Thanks,
Praveen

How to use read_text function module

Hi how to use read_text function module to read purchase order header text .what are all tht things to pass in ID,Name and Object
thanks,
Mahe

Dear,
Use below code.
DATA:IT_LINE LIKE TLINE OCCURS 0 WITH HEADER LINE,
V_TDNAME LIKE THEAD-TDNAME.
V_TDNAME = PO_NUMBER.
CALL FUNCTION 'READ_TEXT'
EXPORTING
*   CLIENT                        = SY-MANDT
    ID                            = 'F01'
    LANGUAGE                      = 'EN'
    NAME                          = V_TDNAME
    OBJECT                        = 'EKKO'
TABLES
    LINES                         = IT_LINE.
Thanks and Regards,

How to use BAPI_MATERIAL_AVAILABILITY Function Module....

Hi Experts,
I want to know actual free available quantity (ATP Qty.) for mass materials,
How to use BAPI_MATERIAL_AVAILABILITY function module ?
I have select all material from MARA and inserted in itab.
LOOP AT ITAB.
CALL FUNCTION 'BAPI_MATERIAL_AVAILABILITY'
EXPORTING
    PLANT                    =
    MATERIAL                 =
    UNIT                     =
CHECK_RULE               =
STGE_LOC                 =
BATCH                    =
CUSTOMER                 =
DOC_NUMBER               =
ITM_NUMBER               =
WBS_ELEM                 =
STOCK_IND                =
DEC_FOR_ROUNDING         =
DEC_FOR_ROUNDING_X       =
READ_ATP_LOCK            =
READ_ATP_LOCK_X          =
IMPORTING
ENDLEADTME               =
AV_QTY_PLT               =
DIALOGFLAG               =
RETURN                   =
TABLES
    WMDVSX                   =
    WMDVEX                   =
I dont know how to use it.
pl. guide us.
Yusuf

Hi,
       data: iwmdvsx type table of bapiwmdvs with header line,
       iwmdvex type table of bapiwmdve with header line.
parameters: p_matnr type mara-matnr,
            p_werks type marc-werks,
            p_meins type mara-meins.
call function 'BAPI_MATERIAL_AVAILABILITY'
exporting
    plant            = p_werks
    material         = p_matnr
    unit             = p_meins
CHECK_RULE       =
STGE_LOC         =
BATCH            =
CUSTOMER         =
DOC_NUMBER       =
ITM_NUMBER       =
WBS_ELEM         =
STOCK_IND        =
IMPORTING
ENDLEADTME       =
AV_QTY_PLT       =
DIALOGFLAG       =
RETURN           =
tables
    wmdvsx           = iwmdvsx
    wmdvex           = iwmdvex.
check sy-subrc = 0.
Text
ATP information
Functionality
Using this function module, you can determine the receipt quantity still available for a particular material in a certain plant according to ATP logic (MRPII).
The availability check is carried out on transferring the material number, the plant and the input table (WMDVSX). The scope of the check, that is, which stocks, receipts and issues are to be included in the check is defined by the combination of checking group (material master) and cheking rule. In the function module, the system uses the checking rule defined in Sales & Distribution (A). You can overrule this checking rule by using an interface or a user-exit (exit_saplw61v_001). A similar procedure is also valid for the plant parameters. The customer number in the user-exit means that the plant selection can be controlled via the customer. If no plant parameters are given via the interface, the system uses the parameter 'WRK' saved in the user's fixed values.
The results of the availability check are recorded in the output table (WMDVEX). This table contains dates and available receipt quantities (ATP quantities). The results of the check depends on the following entries:
If no date and no quantity is transferred, the system displays the ATP situation from today's date into the future as the result.
If only a date and no quantity is transferred, the system displays the ATP situation from the corresponding date as the result.
If both a date and a quantity are transferred, the system calculates the availability situation for the quantity specified.
In the last two cases, the parameter 'DIALOGFLAG' is supplied. This can result in the following:
' ' (blank)   <=> quantity completely available
'X'           <=> only partial quantity available or not available at
                  all
'N'           <=> Material not included in the availability check
                  (Material not relevant to the availability check)
The system also displays the end of the replenishment lead time (ENDLEADTME).
regards

How to use SO_OBJECT_SEND function module

Hi friends,
how to use SO_OBJECT_SEND function module in 4.0B Server .

hi
good
check this code
REPORT ZTSAPMAIL.
DATA: X_OBJECT_TYPE LIKE SOOD-OBJTP.
DATA: BEGIN OF X_OBJECT_HD_CHANGE.
INCLUDE STRUCTURE SOOD1.
DATA: END OF X_OBJECT_HD_CHANGE.
DATA: BEGIN OF X_OBJCONT OCCURS 10.
INCLUDE STRUCTURE SOLI.
DATA: END OF X_OBJCONT.
DATA: BEGIN OF X_OBJHEAD OCCURS 0.
INCLUDE STRUCTURE SOLI.
DATA: END OF X_OBJHEAD.
DATA: BEGIN OF RAW_HEAD.
INCLUDE STRUCTURE SORH.
DATA: END OF RAW_HEAD.
DATA: BEGIN OF X_RECEIVERS OCCURS 0.
INCLUDE STRUCTURE SOOS1.
DATA: END OF X_RECEIVERS.
PARAMETERS: RECEIVER LIKE X_RECEIVERS-RECNAM. " Name
*BUILD MESSAGE HEADER
MOVE 'Sort field goes here' TO X_OBJECT_HD_CHANGE-OBJSRT. " Sort field
MOVE 'Name of the object goes here' TO X_OBJECT_HD_CHANGE-OBJNAM. " Name
MOVE 'Document title goes here' TO X_OBJECT_HD_CHANGE-OBJDES. " Title
MOVE 'F' TO X_OBJECT_HD_CHANGE-OBJSNS. " Functional OBJECT
MOVE 'E' TO X_OBJECT_HD_CHANGE-OBJLA. " Language
Object type of the new document
MOVE 'RAW' TO X_OBJECT_TYPE.
CLEAR X_OBJCONT.
MOVE 'Contents of mail' TO X_OBJCONT-LINE.
APPEND X_OBJCONT.
CLEAR X_OBJCONT-LINE. APPEND X_OBJCONT.
MOVE 'More contents' TO X_OBJCONT-LINE.
APPEND X_OBJCONT.
MOVE 'Still more contents'
to x_objcont-line.
APPEND X_OBJCONT.
MOVE ' ' TO X_OBJCONT-LINE.
APPEND X_OBJCONT.
Specific header (Dependent on the object type, here RAW)
REFRESH X_OBJHEAD.
DESCRIBE TABLE X_OBJCONT LINES RAW_HEAD-RAWSIZ.
MOVE RAW_HEAD TO X_OBJHEAD.
APPEND X_OBJHEAD.
*RECEIVERS table
CLEAR X_RECEIVERS.
REFRESH X_RECEIVERS.
MOVE RECEIVER TO X_RECEIVERS-RECNAM. " Name
MOVE 'B' TO X_RECEIVERS-RECESC. " Receiver type
MOVE 'X' TO X_RECEIVERS-SNDCP. " Send as a copy
MOVE 'X' TO X_RECEIVERS-SNDEX. " EXPRESS DOCUMENT
APPEND X_RECEIVERS.
CALL FUNCTION 'SO_OBJECT_SEND'
EXPORTING
folder_id = 'OUTBOX'
forwarder = x_forwarder
object_fl_change = x_object_fl_change
OBJECT_HD_CHANGE = X_OBJECT_HD_CHANGE
object_id = x_object_id
OBJECT_TYPE = X_OBJECT_TYPE
OUTBOX_FLAG = 'X'
OWNER = SY-UNAME
store_flag = x_store_flag
importing
object_id_new = x_object_id_new
sent_to_all = x_sent_to_all "May need to use
TABLES
OBJCONT = X_OBJCONT
OBJHEAD = X_OBJHEAD
objpara = x_objpara
objparb = x_objparb
RECEIVERS = X_RECEIVERS.
reward point if hlepful.
thanks
mrutyun^

How to Use ECC function Module

Hi Experts - We need to execute the function module in ECC and need to write data in Oracle table.
We are using BODS 4.0.
How to use function module in data flow ? how it can work as a source ?
I just need some basic steps how to use function module as a source and do the transformation to target.
Thanks
R

Hi Ashwani,
It is still not possible to use a FM as a source in DS.
You can use a FM in a transformation but you have to start from a file or table as a source and load into a target (a FM can not be an end point of a dataflow - as it is used in the transformation and each transformation requires a source and a target.
The scenario I described above was based on a situation where you have a source (flat file or table) and want to use a Function Module to transform your data and/or load the data in a transparant table in SAP.
Your scenario is different, as your source is not a table/ff but a FM.
In your case, I can see two scerio's:
- Use an ABAP dataflow. Although I haven't got any experience with this I do believe this would be an option for your scenario. Please referer to the Data Services documentation on ABAP dataflows for further guidance.
- As suggested earlier, you can create a bespoke (BW) Datasource based on a Function Module. Please refer to SAP help for creating a generic datasource:
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm
Depending on your scenario there might be a third option:
- Use a SAP transparant table as a source. Create a transformation into the designated Oracle table. In the transformation call a FM which executes whatever logic you require. This solution will work if you have a table which produces the same number of records as your FM. If your function module produces more or less records (than there are in the transparant table), then this might become a bit tricky. It might work, but I have never tried it.
Instead of a transparant table you can also use a table join, obviously. Perhaps part of the complexity of your FM could be resolved by using a join and you can create a new simpler FM for the remaining logic?
Good luck,
Jan.

How to DEBUG a function module running in background mode? Please help!

Hi Experts,
   I am calling a function module in my ABAP code in background module using the following syntax:
CALL FUNCTION 'YBBC2_CREATE_SNAPSHOT' IN BACKGROUND TASK
          TABLES
            itab_std_format_inv = itab_std_format_inv
            itab_snapshot_inv = itab_snapshot_inv.
        COMMIT WORK.
If I put the breakpoint in the CALL FUNCTION line and execute the program, the debugger does not take me to the valled function module. This may be because I am running the function module as background task.
I cannot comment this "IN BACKGROUND TASK" statement as well since i am debugging in Quality system where I don't have change access.
So how to DEBUG a function module running in background mode? Please help!
Thanks
Gopal

Hi,
You could try to use the following trick:
(1) Put an endless loop into the coding of your function module where you want to start debugging, e.g.
DATA:
    lx_exit_loop(1)     TYPE c.
lx_exit_loop = ' '.
DO.
    IF ( lx_exit_loop = 'X' ).
      EXIT.
    ENDIF.
ENDDO.
(2) Call your function module in background task
(3) Call transaction SM50 and search for the background process.
(3) Choose from menu Program/Mode -> Program -> Debugging
Now you the debugger should bring you right to your endless loop. Set lx_loop_exit = 'X' in the debugger and continue (F5 or F6).
<b>Reward points</b>
Regards

How to write a function module?

How can i write a function module that does the same thing as BAPI_FLIGHT_GETLIST in the SAP system?

Hi
Hope it will help you.
Reward if help.
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

How to debug a function module using in the generic datasource?

Hi all,
We have created a generic data source using function modulle and have been extracting the data for a single customer it contains single records but it has pulled out more than 10,000 records. how to debug the function module used in the data source.
since we schedule for extraction in bi and back ground job gets triggered in ecc for extraction,
i know in se37 we can select the function module name and then debug but still need to check while the bacground job is trigered through bi.
Thanks

Yes you can debug the Function Module.
Open the function module in SE37 and put a break point in the code where you want to check from, then come to RSA3 and give the datasource name and check the Debug check box on this screen, once you click on the start button it will take you the place where you have placed the break point in the FM, by pressing F5 you can see the flow of the FM.
Let me know whether this solves your issue.

How to use the function module ....

hi
how to use the function module ssf_function_module_name in smartforms

Hi..
If you are using this Function module, you can get the generated function module name of smartform dynamically. It is good progrmaming practice to get the fucntion module name dynamically because there might be some problems if you are hard coding in program.
This will return the name of the function module and then from the exporting parameters you can use the fucntion module name to pass parameters to Smartforms.
Check this link.I am expalining here how to use this function module.
https://wiki.sdn.sap.com/wiki/pages/pointstab/viewpageversion.action?pageId=36109&version=2
Calling SMARTFORMS from your ABAP program
REPORT ZSMARTFORM.
Calling SMARTFORMS from your ABAP program.
Collecting all the table data in your program, and pass once to SMARTFORMS
SMARTFORMS
Declare your table type in :-
Global Settings -> Form Interface
Global Definintions -> Global Data
Main Window -> Table -> DATA
Written by : SAP Hints and Tips on Configuration and ABAP/4 Programming
http://sapr3.tripod.com
TABLES: MKPF.
DATA: FM_NAME TYPE RS38L_FNAM.
DATA: BEGIN OF INT_MKPF OCCURS 0.
INCLUDE STRUCTURE MKPF.
DATA: END OF INT_MKPF.
SELECT-OPTIONS S_MBLNR FOR MKPF-MBLNR MEMORY ID 001.
SELECT * FROM MKPF WHERE MBLNR IN S_MBLNR.
MOVE-CORRESPONDING MKPF TO INT_MKPF.
APPEND INT_MKPF.
ENDSELECT.
At the end of your program.
Passing data to SMARTFORMS
call function 'SSF_FUNCTION_MODULE_NAME'
exporting
formname = 'ZSMARTFORM'
VARIANT = ' '
DIRECT_CALL = ' '
IMPORTING
FM_NAME = FM_NAME
EXCEPTIONS
NO_FORM = 1
NO_FUNCTION_MODULE = 2
OTHERS = 3.
if sy-subrc <> 0.
WRITE: / 'ERROR 1'.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
call function FM_NAME
EXPORTING
ARCHIVE_INDEX =
ARCHIVE_INDEX_TAB =
ARCHIVE_PARAMETERS =
CONTROL_PARAMETERS =
MAIL_APPL_OBJ =
MAIL_RECIPIENT =
MAIL_SENDER =
OUTPUT_OPTIONS =
USER_SETTINGS = 'X'
IMPORTING
DOCUMENT_OUTPUT_INFO =
JOB_OUTPUT_INFO =
JOB_OUTPUT_OPTIONS =
TABLES
GS_MKPF = INT_MKPF
EXCEPTIONS
FORMATTING_ERROR = 1
INTERNAL_ERROR = 2
SEND_ERROR = 3
USER_CANCELED = 4
OTHERS = 5.
if sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
<b>Reward points if useful</b>
Regards
Ashu

How to use this function module on abap hr GET_PDSNR_RANGE

how to use this function module on abap hr GET_PDSNR_RANGE
thankx.

PASS INETRNAL TABLE WITH SOME DATA TO TABELLE FOR GENERATING PDSNR SEQUENCE

How to replace ws_filename_get function module to file_open_dialog

how to replace ws_filename_get function module to file_open_dialog

Here it is,
DATA: i_file_name TYPE FILETABLE,
      w_file_name TYPE FILE_TABLE,
      v_rc TYPE i.
CALL METHOD cl_gui_frontend_services=>file_open_dialog
EXPORTING
    INITIAL_DIRECTORY       = 'C:\'
CHANGING
    file_table              = i_file_name
    rc                      = v_rc
EXCEPTIONS
    FILE_OPEN_DIALOG_FAILED = 1
    CNTL_ERROR              = 2
    ERROR_NO_GUI            = 3
    others                  = 4.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
READ TABLE i_file_name INTO w_file_name INDEX 1.
No wthe w_file_name will contain the file name.
Regards
Kathirvel

How to use the function module /IRM/IPBB_AGREEMENT_CREATE.

Hi all,
Please help me how to use the function module /IRM/IPBB_AGREEMENT_CREATE.
It is a Vistex fuction module which is used to create Sales contract in SAP-Vistex. If anyone has use the function module and do have the sample code please share it.
Thanks.

FORM create_agreement TABLES pt_agreement
                                       CHANGING po_agreement .
CONSTANTS: c_strt_knumh TYPE knumh VALUE '0000000000'.
DATA: lc_kona TYPE /irm/s_gkona,
        lc_cbasp TYPE /irm/s_ipcbasp,
      lt_cbapr TYPE /irm/t_ipcbapr,         "Partners
      lc_cbapr TYPE /irm/s_ipcbapr,
      lt_cbadt TYPE /irm/t_ipcbadt,        "Dates
      lc_cbadt TYPE /irm/s_ipcbadt,
      lt_cbafs TYPE /irm/t_ipcbafs,
      lc_cbafs TYPE /irm/s_ipcbafs,
      lt_cbacn TYPE /irm/t_ipcbacn,
      lc_cbacn TYPE /irm/s_ipcbacn,
      lt_cbacl TYPE /irm/t_ipcbacl,
      lc_cbacl TYPE /irm/s_ipcbacl,
      lt_cbtpv TYPE /irm/t_ipagtpv,
      lc_cbtpv TYPE /irm/s_ipagtpv,
      lt_texts TYPE text_lh,
      lc_texts TYPE itclh,
      lt_cbasd TYPE /irm/t_ipcbasd,
      lc_cbasd TYPE /irm/s_ipcbasd,
      lc_agreement    TYPE /irm/s_ipcbasp_doc,
      lc_e_log_number TYPE balognr,
      lt_messages     TYPE /irm/t_gprolog.
DATA: lt_vake      TYPE cond_vakevb_t,
        lc_vake      TYPE LINE OF cond_vakevb_t,
        lt_konh      TYPE /irm/t_gkonh,
        lc_konh      TYPE LINE OF /irm/t_gkonh,
        lt_konp      TYPE /irm/t_gkonp,
        lc_konp      TYPE LINE OF /irm/t_gkonp,
        lt_konw      TYPE /irm/t_gkonwu,
        lc_konw      TYPE LINE OF /irm/t_gkonwu,
        lt_konm      TYPE /irm/t_gkonmu,
        lc_konm      TYPE LINE OF /irm/t_gkonmu,
        lt_komg      TYPE /irm/t_gkomg_index,
        lc_komg      TYPE LINE OF /irm/t_gkomg_index,
        lt_user_data TYPE /irm/t_gpraxfu_index,
        lc_user_data TYPE LINE OF /irm/t_gpraxfu_index.
DATA: lc_updt(1) TYPE c.
DATA: lc_knumh TYPE knumh.
DATA: BEGIN OF lc_str_knumh,
         hd(2) TYPE c VALUE '$$',
         inc_num(8) TYPE c,
        END OF lc_str_knumh.
DATA: blank_agree_key TYPE knuma VALUE '~~~~~~~~~~'.
FIELD-SYMBOLS <konh_line> LIKE LINE OF lt_konh.
FIELD-SYMBOLS <konp_line> LIKE LINE OF lt_konp.
DATA: lc_rule TYPE type_key_rule.
READ TABLE pt_agreement INTO lc_rule INDEX 1.
SELECT SINGLE * FROM kona
        WHERE vkorg   = lc_rule-vkorg
        AND    vtweg   = '10'
        AND    spart   = '10'
        AND    boart   = 'ZPS1'
        AND    botext = lc_rule-sap_agkey.
IF sy-subrc = 0.
   lc_updt = 'U'.
ELSE.
lc_updt = 'I'.
ENDIF.
LOOP AT pt_agreement INTO lc_rule.
    MOVE sy-tabix TO lc_str_knumh-inc_num.
    CONDENSE lc_str_knumh-inc_num NO-GAPS.
    WHILE lc_str_knumh-inc_num+7(1) = ' '.
      CONCATENATE '0' lc_str_knumh-inc_num INTO lc_str_knumh-inc_num.
      CONDENSE lc_str_knumh-inc_num NO-GAPS.
    ENDWHILE.
    CONCATENATE '$$' lc_knumh INTO lc_knumh.
    MOVE lc_str_knumh TO lc_knumh.
   MOVE c_strt_knumh TO lc_knumh.
    CLEAR: lc_konh, lc_konp, lc_komg.
    MOVE: lc_rule-vkorg    TO lc_komg-komg-vkorg,
          '10'             TO lc_komg-komg-vtweg,
          '10'             TO lc_komg-komg-spart,
          p_waers          TO lc_komg-komg-waerk,
          '1300'           TO lc_komg-komg-bukrs,
          lc_rule-lifnr    TO lc_komg-komg-lifnr,
          lc_knumh         TO lc_komg-knumh,
          lc_knumh         TO lc_konh-knumh,
          lc_knumh         TO lc_konp-knumh,
          lc_rule-datab    TO lc_konh-datab,
          lc_rule-datbi    TO lc_konh-datbi.
    CASE lc_rule-tablnam.
      WHEN 'A701'.                   "Every Agreement will have a A701 rule -
        "Therefore we acn setup the header using A701
        MOVE: 'New       ' TO lc_kona-knuma,
              lc_rule-vkorg TO lc_kona-vkorg,
              '10'          TO lc_kona-vtweg,
              '10'          TO lc_kona-spart,
              'ZPS1'        TO lc_kona-boart,
              'C'           TO lc_kona-abtyp,
              'V'           TO lc_kona-kappl,
              p_waers       TO lc_kona-waers,
              lc_rule-knuma_ag TO lc_kona-abrex,
              'ZPS2'        TO lc_kona-kobog,
              lc_rule-datab TO lc_kona-datab,
              lc_rule-datbi TO lc_kona-datbi,
              lc_rule-sap_agkey TO lc_kona-botext,
              '1300'        TO lc_kona-bukrs,
              'I'           TO lc_kona-updkz.
        MOVE: 'New       ' TO lc_cbasp-knuma_ag,
              'ZPS1'        TO lc_cbasp-boart_ag,
              p_waers       TO lc_cbasp-waers,
              'A'           TO lc_cbasp-setl_mth,
              'B'           TO lc_cbasp-setl_typ,
              'A2'          TO lc_cbasp-ident,
              'E'           TO lc_cbasp-setlm,
              'ZPDA'        TO lc_cbasp-pargr,
              'X'           TO lc_cbasp-npric,
              'LF'          TO lc_cbasp-stprl,
              lc_rule-lifnr TO lc_cbasp-stpar,
              lc_rule-contract_rev TO lc_cbasp-rvnum,
              'I'           TO lc_cbasp-updkz.
        CONCATENATE: blank_agree_key
               lc_rule-lifnr        INTO lc_konh-vakey.
        MOVE: lc_rule-lifnr TO lc_konp-lifnr.
      WHEN 'A703'.
        CONCATENATE: blank_agree_key
                     lc_rule-kunnr      INTO lc_konh-vakey.
        MOVE lc_rule-kunnr TO lc_komg-komg-kunnr.
      WHEN 'A709'.
        CONCATENATE: blank_agree_key
        lc_rule-zzprodh1 lc_rule-zzprodh2 lc_rule-zzprodh3
               lc_rule-zzprodh4 lc_rule-zzprodh5 INTO lc_konh-vakey.
        CONCATENATE: lc_rule-zzprodh1 lc_rule-zzprodh2 lc_rule-zzprodh3
               lc_rule-zzprodh4 lc_rule-zzprodh5 INTO lc_komg-komg-prodh.
      WHEN 'A710'.
        CONCATENATE: blank_agree_key
            lc_rule-matkl   INTO lc_konh-vakey.
        MOVE lc_rule-matkl TO lc_komg-komg-matkl.
      WHEN 'A711'.
        CONCATENATE: blank_agree_key
             lc_rule-matnr   INTO lc_konh-vakey.
        MOVE lc_rule-matnr TO lc_komg-komg-matnr.
        IF lc_rule-kschl = 'ZPPL'.
          MOVE: 'C'              TO lc_konp-krech,
                'CAD'              TO lc_konp-konwa.
          lc_konp-kbetr = lc_rule-net_po_price * 1.
        ENDIF.
      WHEN 'A717'.
      WHEN 'A718'.
        CONCATENATE: blank_agree_key
             lc_rule-zzextwg INTO lc_konh-vakey.
        MOVE lc_rule-zzextwg TO lc_komg-komg-zzextwg.
     WHEN 'A719'.
       CONCATENATE: blank_agree_key
            lc_rule-werks INTO lc_konh-vakey.
       MOVE lc_rule-werks TO lc_komg-komg-werks.
     WHEN 'A721'.
       CONCATENATE: blank_agree_key
             lc_rule-kunnr lc_rule-werks INTO lc_konh-vakey.
       MOVE: lc_rule-kunnr TO lc_konp-kunnr,
             lc_rule-kunnr TO lc_komg-komg-kunnr.
      WHEN 'A722'.
        CONCATENATE: blank_agree_key
                     lc_rule-vkbur INTO lc_konh-vakey.
        MOVE lc_rule-vkbur TO lc_komg-komg-vkbur.
      WHEN 'A724'.
        CONCATENATE: blank_agree_key
                      lc_rule-kunnr lc_rule-vkbur INTO lc_konh-vakey.
        MOVE: lc_rule-kunnr TO lc_konp-kunnr,
              lc_rule-kunnr TO lc_komg-komg-kunnr,
              lc_rule-vkbur TO lc_komg-komg-vkbur.
    ENDCASE.
    MOVE: 'A'                  TO lc_konh-kvewe,
          lc_rule-tablnam+1(3) TO lc_konh-kotabnr,
          lc_rule-kappl        TO lc_konh-kappl,
          lc_rule-kschl        TO lc_konh-kschl.
    REPLACE ALL OCCURRENCES OF '~' IN lc_konh-vakey WITH ' '.
    APPEND lc_konh TO lt_konh.
    CLEAR lc_konh.
*--- Add in the KONP.Do we need to add
    MOVE: lc_rule-kappl        TO lc_konp-kappl,
          lc_rule-kschl        TO lc_konp-kschl,
          'G'                  TO lc_konp-krech.
    IF lc_rule-kschl+3(1) = '%'.
      MOVE: 'A'              TO lc_konp-krech,
            '%'              TO lc_konp-konwa.
      lc_konp-kbetr = lc_rule-rebate_perc * 1.
    ENDIF.
    APPEND lc_konp TO lt_konp. CLEAR lc_konp.
    APPEND lc_komg TO lt_komg. CLEAR lc_komg.
ENDLOOP.
IF lc_updt = 'I'.
    CALL FUNCTION '/IRM/IPCB_AGREEMENT_CREATE'
      EXPORTING
      I_MESSAGES_DISPLAY        = ' '
      I_SAVE_MESSAGES           = ' '
      I_COMMIT_WORK             = 'X'
      I_CALL_FROM_WS            = ' '
        is_kona                   = lc_kona
        is_cbasp                  = lc_cbasp
        it_cbapr                  = lt_cbapr
        it_cbadt                  = lt_cbadt
        it_cbafs                  = lt_cbafs
        it_cbacn                  = lt_cbacn
        it_cbacl                  = lt_cbacl
        it_cbtpv                  = lt_cbtpv
        it_texts                  = lt_texts
        it_cbasd                  = lt_cbasd
      IMPORTING
        es_agreement              = lc_agreement
        e_log_number              = lc_e_log_number
      TABLES
        t_messages                = lt_messages
     CHANGING
      CT_VAKE                   = lt_vake
      ct_konh                   = lt_konh
      ct_konp                   = lt_konp
      CT_KONW                   = lt_konw
      CT_KONM                   = lt_konm
       ct_komg                   = lt_komg
      CT_USER_DATA              = lt_usr_data
      EXCEPTIONS
        no_documents_to_process   = 1
        no_authorization          = 2
        creation_failed           = 3
        new_pricing_not_maitained = 4
        OTHERS                    = 5.
    IF sy-subrc <> 0.
Implement suitable error handling here
    ELSE.
      MOVE: lc_agreement-knuma_ag TO po_agreement,
            lc_agreement-knuma_ag TO lc_kona-knuma.
    ENDIF.
    APPEND LINES OF lt_messages TO gt_messages.
ELSE.
    MOVE-CORRESPONDING kona TO lc_kona.
ENDIF.
LOOP AT lt_konh ASSIGNING <konh_line>.
    MOVE lc_kona-knuma TO <konh_line>-vakey+0(10).
   move '&'           to <konh_line>-knumh+0(1).
ENDLOOP.
LOOP AT lt_konp ASSIGNING <konp_line>.
   MOVE lc_kona-knuma TO <konp_line>-vakey+0(10).
    move '&'           to <konh_line>-knumh+0(1).
ENDLOOP.
lc_kona-updkz = 'U'.
lc_cbasp-updkz = 'U'.
CLEAR lt_messages.
CALL FUNCTION '/IRM/IPCB_AGREEMENT_CHANGE'
    EXPORTING
    I_MESSAGES_DISPLAY      = ' '
    I_SAVE_MESSAGES         = ' '
    I_COMMIT_WORK           = 'X'
    I_INIT_DATA             = 'X'
      is_kona                 = lc_kona
      is_cbasp                = lc_cbasp
     it_cbapr                = lt_cbapr
     it_cbadt                = lt_cbadt
     it_cbafs                = lt_cbafs
     it_cbacl                = lt_cbacl
     it_cbacn                = lt_cbacn
    IT_FIELDS               =
     it_texts                = lt_texts
   IMPORTING
     e_log_number            = lc_e_log_number
     TABLES
       t_messages              = lt_messages
    CHANGING
      cs_agreement            = lc_agreement
    CT_VAKE                 = lt_vake
      ct_konh                 = lt_konh
      ct_konp                 = lt_konp
    CT_KONW                 = lt_konw
    CT_KONM                 = lt_konm
      ct_komg                 = lt_komg
    CT_USER_DATA            = lt_usr_data
    EXCEPTIONS
      no_documents_to_process = 1
      no_authorization        = 2
      change_failed           = 3
      agreement_locked        = 4
      OTHERS                  = 5.
IF sy-subrc <> 0.
Implement suitable error handling here
ENDIF.
APPEND LINES OF lt_messages TO gt_messages.
ENDFORM.                    " CREATE_AGREEMENT

How to use SD_VBAK_ARRAY_READ functional module

hello
can you please tell me how to use SD_VBAK_ARRAY_READ functional module. that means what i have to pass and what i should get.
Please help me

Hi Ravi,
i want to display vkorg,kunnr,and some other fields from the VBAK. User enters VKORG and some other fields but VKORG is compulsory.
so i written the code like this.
TYPES :BEGIN OF TEITAB_VBAK,
       VKORG type VBAK-VKORG,
       KUNNR TYPE VBAK-KUNNR,
       VBELN TYPE VBAK-VBELN,
       AUDAT TYPE VBAK-AUDAT,
       VDATU TYPE VBAK-VDATU,
       ERNAM TYPE VBAK-ERNAM,
       END OF TEITAB_VBAK.
DATA: ITAB_VBAK TYPE TABLE OF TEITAB_VBAK,
      WA_VBAK TYPE TEITAB_VBAK.
SELECT-OPTIONS: s_VKORG FOR P_VKORG OBLIGATORY,         " Sales Organization
                s_KUNNR FOR P_KUNNR,         " Sold-to party.
                s_VBELN FOR P_VBELN,         " Sales Document.
                s_MATNR FOR P_MATNR,         " Material number.
                s_AUDAT FOR P_AUDAT,         " Document Date (Date Received/Sent).
                s_VDATU FOR P_VDATU,         " Requested delivery date.
                s_ERNAM FOR P_ERNAM,         " Name of Person who Created the Object.
                s_VKAUS FOR P_VKAUS.         " Usage indicator.
SELECT VKORG KUNNR VBELN AUDAT VDATU ERNAM
FROM VBAK
INTO CORRESPONDING FIELDS OF TABLE ITAB_VBAK
WHERE VKORG IN S_VKORG AND AUART EQ 'ZRA'.
CALL FUNCTION 'SD_VBAK_ARRAY_READ'
EXPORTING
I_BYPASSING_BUFFER          = ' '
I_REFRESH_BUFFER            =
TABLES
    IT_VBAK_KEY                 =
ET_VBAK                     =
EXCEPTIONS
RECORDS_NOT_FOUND           = 1
RECORDS_NOT_REQUESTED       = 2
OTHERS                      = 3
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
so i confused where to call this fucntional module and what to pass. That means call this functional module before the select query or after the select query and what to pass.
i am new in ABAP.
Please help me to solve this problem .

How many types of function modules are there

hi gurus,
how many types of function modules are there...
what type of function module bapi is....
i don't know much about that...
pls help me...
regards,
praveen

hi
hope it will help you.
<REMOVED BY MODERATOR>
Function Modules Used in Script:
In the Driver Program we must use all or some of the function modules that are listed below to transfer the data.
Open_Form
Close_Form
Start_Form
Write_Form
Write_Form_Lines
End_Form
Control_Form
Read_Form_elements
Read_Form_Lines
Any driver program must contain Open_Form, Close_Form and Write_Form. Other function modules are optional.
OPEN_FORM: This function module opens layout set printing. One must call this function module before he uses any of other layout set function modules like Write_Form, Start_Form, Control_Form etc., You need specify a layout set name in the export parameters of this function module. If nothing is passed to Open_Form then one should use Start_Form function module to open layout set before starting the output. The layout set opened by Open_Form should be closed by Close_Form function module, other wise output doesnt appear. We can use any number of Open_Form, Close_Form functions in one single program. But Close_Form must be there for every Open_Form in the program.
Some of the important export parameters we have to pass to Open_Form function module.
Form: Enter the Layout set name here, which then controls the output formatting. If nothing is specified then we must use Start_Form for opening layout set.
Language: Layout sets are Language dependent. Enter the desired language here. If the entered layout set is not in that language, then the function tries to open the Form entered in its original language. The default value is SY-LANGU.
Device: SAP Script can format a text on different device types. The device can be PRINTER or TELEX, TELEFAX, ABAP and SCREEN.
Dialog: Use parameter DIALOG to determine whether to display a dialog box before printing, in which the user can set several spool parameters for print formatting. Possible values: SPACE displays no print parameter screen. 'X' display print parameter screen. Default value: 'X'
Options: Use parameter OPTIONS to set several options for print formatting. The parameter has the structure ITCPO. The user can change some of the defined settings on the print control screen. The default value for Options is . We will discuss about ITCPO structure in detail later.
Other Export, Import and Exceptions are self-explanatory.
Close_Form: The function module closes the layout set opened using OPEN_FORM. The system executes any terminating processing steps for the last opened layout set. No Export parameters for this Function Module.
Start_Form: In-between the function modules OPEN_FORM and CLOSE_FORM, we can use different layout sets. This allows us to combine several different layout sets into one print output. However, we can combine only those layout sets that have the same page format. To switch layout sets, use the function module START_FORM. If another layout set is still open, we must close it first using END_FORM. If we specify no layout set name when calling START_FORM, the system restarts the last open layout set. If after OPEN_FORM no layout set was activated yet, the system leaves the function module with the exception UNUSED. Some of the important export parameters for this function module are
Form: The parameter contains the name of the layout set you want to use for printing. If you specify no layout set here, the system restarts the last active layout set.
Language: Layout sets are language-dependent. Enter the desired language here. If the layout set does not exist in this language, the system tries to call the layout set in its original language. If the parameter LANGUAGE is empty, the system uses the language of the last active layout set.
Startpage: Usually, SAP script starts with the page specified as start page in the layout set definition. If we want to start output with another layout set page, enter the name of the desired layout set page here. If the desired page is not defined, the system uses the start page defined in the layout set.
Program: To replace program symbols, SAP script must know which active program contains the work areas for the values to be passed. If we omit the parameter, the system searches for the field values in the program that was specified in the parameter OPTIONS (field TDPROGRAM) of OPEN_FORM. If we enter a program name, the system replaces the program symbols with the values from this program up to the next END_FORM.
Exceptions and other Export, Import parameters are self-explanatory.
Write_Form: The system outputs the layout set element specified in parameter ELEMENT into the currently opened layout set. In the parameter WINDOW we can specify the name of a window for the output. Remember that the layout set element must be defined in this window. The parameter FUNCTION specifies how to merge the text lines to be output with any existing contents in the window. In this case, there are differences between the different window types or areas. Some of the important export parameters used in Write_Form.
Element: Specify the name of the text element you want to output into the layout set window specified in the parameter WINDOW. The element must be defined in that layout set window. If you specify no element, the system uses the default element, if one is defined in the layout set.
Window: Specify the name of the window into which you want to output the layout set element specified in the parameter ELEMENT. Default value for Window is MAIN.
Function: The parameter determines how to output the text element into the respective window. The output type depends on the window type and area:
Window Type: MAIN Area: BODY
SET/APPEND: Appends to previous output.
Window Type: Main Area: Top/Bottom and
Window Type: Other than Main and all areas
SET : Delete the old element contents and prints the new elements
APPEND: Appends the new content to existing elements.
Type: The system interprets this parameter only for output to the main window. The parameter determines the area of the main window into which we want to output the element. Possible values: 'TOP' header area
'BODY' main area
'BOTTOM' footer area
Default value: 'BODY'
Write_Form_Lines: This function module outputs the text lines in table LINES into the specified layout set window. The text lines must have the SAP script 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 layout set.
Use parameter WINDOW to specify into which of the windows defined in the layout set we want to output the text. We can specify any window used in the layout set. 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.
Header: This parameter contains the header of the text module we want to output in the current layout set. For the formatting process, the system uses only the entries in the header fields TDSTYLE and TDFORM. Structure: THEAD
WINDOW: Enter the name of the window into which we want to output the layout set element specified in parameter ELEMENT. Default value: 'MAIN'
FUNCTION: This parameter determines how to output the text element into the respective window. The output type depends on the window type and area: Window type MAIN, area BODY: 'SET' append to previous output 'APPEND' same as SET. DELETE' no effect. Window type MAIN, areas TOP and BOTTOM; all other windows: 'SET' delete old window or area contents and output the element 'APPEND' append the element to the existing elements 'DELETE' no effect Default value: 'SET'
TYPE: The system interprets this parameter only for output to the main window. The parameter determines the area of the main window into which you want to output the element. Possible values: 'TOP' header area 'BODY' main area 'BOTTOM' footer area Default value: 'BODY'
END_FORM: END_FORM ends the currently open layout set and executes the required termination processing. After calling this function module, no more layout set is active. For further output, we must start a new layout set using START_FORM. No Export parameters.
CONTROL_FORM: Use this function module to pass SAP Script Control Commands to the layout set. The Control command is passed through the export parameter COMMAND in quotes.
READ_FORM_ELEMENTS: This function module fills a table with all text elements that appear in one layout set. If we specify no layout set name, the system includes all elements of the currently open layout set. If we specify a layout set, the system uses the information about the active version of the layout set, retrieved from the database. Here we have two export parameters, Form and Language and a table parameter Elements.
READ_FORM_LINES: Use this function module to transfer the lines of a layout set element into an internal table. If we specify no layout set name, the system transfers the text lines of the currently open layout set. If we specify a layout set, the system uses the text lines of the active version of the layout set from the database. The Export parameters are Form, Language, Window and Element. If we pass these 4 parameters the function module returns a table with the lines from layout set.
Function modules are one element. There are no types. However sometimes an RFC enabled function module is referred to as RFC Function module, but really it is just a function module. Also BAPIs are function modules, but are usually referred to as just BAPI as opposed to BAPI Function module.
There is no different function module types , but calling the function module will be different.
check this function calls syntax
1. Calls a function module:
CALL FUNCTION func.
2. Call a function module in a different mode (asynchronous Remote Function Call):
CALL FUNCTION func STARTING NEW TASK taskname.
3. Call a function module in the update task:
CALL FUNCTION func IN UPDATE TASK.
4. Call a function module in a remote system (Remote Function Call, RFC ):
CALL FUNCTION func DESTINATION dest.
5. Asynchronous call to a function module with transactional processing (transactional Remote Function Call):
CALL FUNCTION func IN BACKGROUND TASK.
qRFC with output queue
6. Call a function module that can be activated in the context of enhancements:
CALL CUSTOMER-FUNCTION func.
Cheers,
Chandru
Edited by: Alvaro Tejada Galindo on Feb 27, 2008 11:53 AM

How to incoporate a function module in data source based on view

Similar Messages

Maybe you are looking for