What are the Includes in Function Module...? if the fuction group IS ZSJ_FC

What are the Includes in Function Module...? if the fuction group IS ZSJ_FC..?
How can I access SAP through Internet....?
Moderator Message: Interview-like question(s). Thread locked.
Edited by: Suhas Saha on Sep 30, 2011 11:14 AM

Hi
No! U can insert an own you Z-INCLUDE or somethingelse, try to regenerate the index of the program.
Max

Similar Messages

What are difference b/w functional module&infoset

hi this is ramireddy.

Hi Ram,
Hey i didnt get as to why you were comparing FM and Infoset.But any ways let me just brief you as to what they individually are:
I am also new to SAP .Let me try.
I hope this helps you.
Function Modules are procedures that are defined in Functional groups.These can be called from any ABAP program.
*Function Modules allow you to reuse global functions in R/3.
*T-Code for Function modules in SE37.Unlike your usual SourceCode which has SE38.
You can create infoset on ODS and master data tables only. Multiprovider you can create on any combination(cubes, ods, master data).
There are many advantages of FM's.
Infact it also supports Exception Handling.
*We have some standard function modules which can be used in our programs.
Check these links for creating Infoset Query,
https://www.sdn.sap.com:443/irj/sdn/thread?threadid=163772&messageid=1837694
https://www.sdn.sap.com:443/irj/sdn/thread?threadid=199410&messageid=2217326
https://www.sdn.sap.com:443/irj/sdn/thread?threadid=189150&messageid=2113030
Please go through these links.
Hope it helps..
Pleae assign points if helpful
Regards,
Priyanka

Function module to the newly created 'Z' function group

I am facing a strange issue when I am trying to reassign the existing 'Z' Function module to the newly created 'Z' function group. The system gives an error as 'Modified Function Modules may not be reassigned'.
Could anyone face this issue before or if you have any suggestion on this, please let me know.
Thanks in Advance.

Hi,
Check this steps:
1) The FM to be moved is activated.
2) Both new Z-FG and the previous FG are activated.
3) You are not editing the the FM you are trying to move.
4) If you are in the Object List view (se80 view) goto : Utilities->Update Navigation Index
Guess that should take care of the issue!!
Cheers,
Lakshmiraj
Reward if useful

Tracking the execution of Function Modules

Hi there,
for ABAP reports there is an enhancement S38MREP1 'Exit at Start report' in transaction CMOD available which could be used e. g. to track the execution at least of executable programs (TRDIR-SUBC = 1); limitation: it is executed before the selection screen, so no guarantee that a certain program is really submitted afterwards.
Is there something similar available in release 4.5B (or in any higher release?) or how can I track the execution of function modules in the customer name space in a smart way?
Thanks in advance for any support,
Peter

Expanding a bit on Seigfried's post, you could write a little function module with with a parameter which would be function module name and it would update a custom table everytime it is executed.
Put this function call at the end of the function module that you want to log.
call function 'Z_LOG_FUNCTION_EXECUTION'
exporting
fcname = 'Z_THE_NAME_OF_THE FUNCTION'.
The code inside this function module could be something like this.
ztable-fcname = fcname.
ztable-uname = sy-uname.
ztable-datum = sy-datum.
ztable-uzeit = sy-uzeit.
insert ztable.
Regards,
Rich Heilman

What are all the types of Function module?

Hi,
What are all the types of Function module.
Pls reply me.

Hi,
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.
plz go through the below links
http://help.sap.com/saphelp_nw2004s/helpdata/en/9f/db988735c111d1829f0000e829fbfe/content.htm
Thanks,
Reward If Helpful.

What are the parameters of Function Module

Hi,
What are the parameters of Function Module?

Function Modules are special external subroutine stored in a central library. The R/3 system provides numerous predefined function modules that you can call from the ABAP/4 programs.
All the function Modules are created under the Function Groups. Function Groups are nothing but the related group of function modules.
The function modules can be maintained through T.CodeSE37 and T.Code SE80.
In general the function module has the following components.
Documentation:
This is the place where you can find the discription/purpose of the function module.
Import & Export Parameters.
Import parameters correspond to the formal input parameters of subroutines. They pass data from the calling program to the function module.
Export parameters correspond to the formal input parameters of subroutines. They pass data from the function module back to the calling program.
Table Parameters.
Table parameters are internal tables. Internal tables are treated like changing parameters and are always passed by reference.
Exceptions.
Exceptions are used to handle error scenarios which can occur in the function modules. The function modules checks for any type of error and raise exception and returns SY-SUBRC value to the calling program.
Source Code:
the programming logic of the function module is written in this source code.
Rewards if useful.

What is the table contains Function module include program name

Hi,
What is the table contains Function module include program name
Regards,
Raja

Try this FUNCTION_INCLUDE_INFO to get the include number to which function module belongs to.From this u ll get only the particular include name.
or
if u need the all the includes used in the function group u have use INNER JOIN on TFDIR and D010INC table
Select binclude into itab from trdir as a inner join d010inc as b on apname = bmaster where apname = fmodname.
I hope this will help u.
Thanks & Regards
Santhosh
Message was edited by:
santhosh ds

What are the sequence of function modules executed in payroll result

Dear all,
what are the sequence of function modules executed while retrivieng pryroll result.or
functionmodule sequence in payroll programming.
By
bose

Hi Bose,
The sequence of FM executed in payroll result are
1. cu_read_rgdir ---> from this u will get the country key.
2. cd_read_last -
> from this fm u will identify the seqnr for the latest record and finally for the payroll result
3. pyxx_read_payroll_result.

What is the Exceptions in function module

Hi,
wt is the exceptions in function module? can anyone tell me?
Thanks
swathi

Exception is the mechanism by which you can give the error messages back to the program.
Say for the REUSE_ALV_GRID_DISPLAY, we have so many exceptions. Every exception has some meaning. Say the exception PROGRAM_NOT_FOUND will be raised when you had passed wrong program name in the CALLBACK program.
PROGRAM_NOT_FOUND = 1...
If the exception was raised than this value will be set to the SY-SUBRC.
SO, by accessing SY-SUBRC, you can get to know which exception was raised.
Regards,
Naimesh Patel

Whats the use of function module RSAP_IDOC_SEND?

Hi Gurus,
Can anyone please let me know the use of Function Module - RSAP_IDOC_SEND.
Regards
Avi....

Hi
Check this...
Send IDOC in parallel dialog process.
 CALL FUNCTION 'RSAP_IDOC_SEND'
 STARTING NEW TASK l_task
 PERFORMING callback_parallel_idoc ON END OF TASK
 EXPORTING
 i_mestyp = p_mestyp
 i_rcvprt = p_rcvprt
 i_rcvprn = p_rcvprn
 i_flag_commit_work = sbiwa_c_flag_on
 i_s_rqstprms = l_s_rorqstprms
 TABLES
 i_t_idoc_data = p_t_idoc_data
 EXCEPTIONS
 system_failure = 1
 communication_failure = 2.
reward if Helpful

How to write the exceptions in function module

dear all,
how to write the exceptions in function modules with example.
thanq
jyothi

Hi,
Raising Exceptions
There are two ABAP statements for raising exceptions. They can only be used in function modules:
RAISE except.
und
MESSAGE.....RAISING except.
The effect of these statements depends on whether the calling program handles the exception or not. The calling program handles an exception If the name of the except exception or OTHERS is specified after the EXCEPTION option of the CALL FUNCTION statement.
If the calling program does not handle the exception
· The RAISEstatement terminates the program and switches to debugging mode.
· The MESSAGE..... RAISING statement displays the specified message. Processing is continued in relation to the message type.
If the calling program handles the exception, both statements return control to the program. No values are transferred. The MESSAGE..... RAISING statement does not display a message. Instead, it fills the system fields sy-msgid, sy-msgty, sy-msgno , and SY-MSGV1 to SY-MSGV4.
Source Code of READ_SPFLI_INTO_TABLE
The entire source code of READ_SPFLI_INTO_TABLE looks like this:
FUNCTION read_spfli_into_table.
""Local Interface:
*" IMPORTING
*" VALUE(ID) LIKE SPFLI-CARRID DEFAULT 'LH '
*" EXPORTING
*" VALUE(ITAB) TYPE SPFLI_TAB
*" EXCEPTIONS
*" NOT_FOUND
SELECT * FROM spfli INTO TABLE itab WHERE carrid = id.
IF sy-subrc NE 0.
MESSAGE e007(at) RAISING not_found.
ENDIF.
ENDFUNCTION.
The function module reads all of the data from the database table SPFLI where the key field CARRID is equal to the import parameter ID and places the entries that it finds into the internal table spfli_tab. If it cannot find any entries, the exception NOT_FOUND is triggered with MESSAGE ... RAISING. Otherwise, the table is passed to the caller as an exporting parameter.
Calling READ_SPFLI_INTO_TABLE
The following program calls the function module READ_SPFLI_INTO_TABLE:
REPORT demo_mod_tech_fb_read_spfli.
PARAMETERS carrier TYPE s_carr_id.
DATA: jtab TYPE spfli_tab,
wa LIKE LINE OF jtab.
CALL FUNCTION 'READ_SPFLI_INTO_TABLE'
EXPORTING
id = carrier
IMPORTING
itab = jtab
EXCEPTIONS
not_found = 1
OTHERS = 2.
CASE sy-subrc.
WHEN 1.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno.
WHEN 2.
MESSAGE e702(at).
ENDCASE.
LOOP AT jtab INTO wa.
WRITE: / wa-carrid, wa-connid, wa-cityfrom, wa-cityto.
ENDLOOP.
The actual parameters carrier and jtab have the same data types as their corresponding interface parameters in the function module. The exception NOT_FOUND is handled in the program. It displays the same message that the function module would have displayed had it handled the error.
Or
just have to decide what exceptions u want and under what conditions.
then declarethese exeptions under the exceptions tab.
in the source code of ur function module.
if
like this u can code .
now when u call the function module in tme mainprogram.
if some error occurs and u have declared a exception for this then it will set sy-subrc = value u give inthe call of this fm.
in the fm u can program these sy-subrc values and trigger the code for ur exception.
Please reward if useful
Regards,
Ravi
Edited by: Ravikanth Alapati on Mar 27, 2008 9:36 AM

Includes in function module

hiya ,
do INCLUDES in the function module all shud be in the same function group??
what iam doing is ..copied the sap standard function module but when iam executing it says <function module cannot be found in the same group>
is it something to do with includes...
plz advise
thanks

Hi
No! U can insert an own you Z-INCLUDE or somethingelse, try to regenerate the index of the program.
Max

How to add a created Z function module to the existing list in WE21

Hi all,
There is some existing function modules ( like EDI_PATH_CREATE_CLIENT_DOCNUM ) in WE21 in the function module field.
here, i need to create one Z function module as per user requirement & want to add to that list. is it possible???
actually, i want the file name format is like
" Document Number_YYYYMMDDHHMMSS.xml ". but existing function modules are not giving this format.do anybody give any idea.
correct answers will be rewarded.
Thanks & Regards

HI Pabitra,
Yes, can always change the existing fm and add it with message type as follows pls note step 7 and step 8. (for inbound it is we42 and for outbound it is we41 )
Basic IDOCs have supplied by SAP with standard structure. (Segments). You can extend them with your own segments.
IDOCs does have unique number. They contain control, data, and status records.
Useful Transaction Codes:
WEDI : IDoc Menu
WE02 : IDoc List (can enter IDoc number to select on)
WE05 : IDoc List
WE19 : Transaction WE19 can be used to test the IDoc
WE30 : IDoc Type Development: Initial Screen
WE31: Development Segments: Initial Screen
WE60 : Documentation for IDoc Types. This allows you to view the IDoc you have created.
WE81 : Display View EDI: Logical Message Types: Overview
WE82: Display View Message Types and Assignment to IDoc Types: Overview
WE21 - Creation of POrt
WE20 - Partner Profile creation
SALE - ALE (Application Linking and Enabling) settings
For Outbound ALE Configurations: (Example)
IDoc definitions and necessary ALE configurations settings for the outbound .
Create Idoc segments Transaction WE31.
Create Idoc type Transaction WE30.
Create Message Type Transaction WE81.
Assign Message Type to Idoc type Transaction WE82.
Create a distribution Model - Transaction BD64
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
for creating a IDOC
see the below steps for outbound processing IDOCS..
2.1 Outbound Interface
PROCESS DIAGRAM
Outbound Interface
1. Analyse Hierarchy Levels
2. Create New segment
3. Create New IDoc Type
4. Create New Message Type
5. Link Message with IDoc Type
6. Create an entry in EDP13 via transactions WE20 and BD64
7. Populate the Custom IDoc via ABAP Program
7b Error Handling
7c. Send Status Email
8. Test the Population of the Custom IDoc
Step 1 Analyse Hierarchy Levels:
Analyse the data relationships being processed in the interface. Define the appropriate hierarchical Parent-to-Child relationships.
Navigate to transaction code WEDI
Transaction WEDI displays the IDOC main menu. This allows navigation around the various development and control areas to create a customised IDOC.
Step 2 Create a new segment:
via wedi : Development - IDOC Segments or Transaction code WE31.
Enter segment name and click on Create.
The? name of the segment type must start with Z1 , and have a maximum of eight characters.
Enter description and enter the relevant field names and data elements.
The segment should represent a structure in the program so for? each field in the segment a field name and a data element must be defined.
Save the segment and enter Person Responsible and Processing Person .
Go to Edit and Set Release.
Repeat this procedure for each new Segment in the IDOC.
Step 3 Create a new IDOC Type
via wedi Development - IDOC Types or Transaction WE30.
Enter segment name (starting with Z), click on Basic Type and then Create.
Create as new, enter Person Responsible and Processing Person and enter description.
On Create Basic Type screen decide where segments should be inserted and go to Edit/Create Segment.
Complete relevant fields in the Maintain Attributes screen:
From the relevant segments created in Step 2 enter the Segment type and if mandatory segment.
The Minimum and Maximum number of segments to be allowed in the sequence. (One minimum and one maximum if segment is mandatory).
The Parent Segment and Hierarchy Level will be automatically created depending on where in the IDOC tree you decided to create that particular segment.
Repeat this process for each segment needed in the IDOC type, deciding whether to add the next segments at the same level or as a Child.
When IDOC created return to initial screen. Go to Edit and Set Release.
Go to Transaction WE60 to view the IDoc Type you have created.
Step 4 Create new Message Type
via wedi Development - Message Types or Transaction WE81.
Display/Change and click on New Entries
Create a new Message Type and Save.
Step 5 Link Message Type to IDOC Type
via wedi Development - IDOC Type/Message or Transaction WE82.
Display/Change and then click on New Entries.
Enter Message Type, Basic Type (IDOC Type) and Release (46C) and Save.
Step 6 Create an entry in EDP13 via transactions WE20 and BD64.
The partner profile for the Idoc must be set up and generated in the transaction BD64 and transaction WE20.
WE20 Add Message Type to appropriate Partner Type, Enter Message Type, Receiver Port and Idoc Type and Save.
BD64 Create a Model View, Enter Sender and Receiver Ports, Attach Message Type. Go to Environment on Menu and click on Generate Partner Profiles and generate (not save) profile.
Step 7 Populate the custom IDOC via ABAP Program
See Test Program ZOUTBD_IDOC_TEMPLATE, Appendix IV.
Create an Internal Table for each segment type, this should be exactly the same structure as the segment type.
The control record is filled into a structure like EDIDC. The message type and the Idoc type for the Idoc must be populated into the eddic structure.
- PERFORM populate_Control_structure USING c_mestyp
c_SEGMENT_type1.
The data segments are filled into a structure like edidd-sdata; sdata and the segment name are populated into the edidd structure.
- PERFORM transfer_Parent_data_to_seg.
The standard SAP function module MASTER_IDOC_DISTRIBUTE is called to pass the populated IDOC to the ALE Layer.
- PERFORM master_idoc_distribute.
NOTE: This function module is only called for stand alone programs and Shared Master Data programs (SMD). It is not called when using extensions or output determination.
The ALE Layer handles the sending of the IDOC to the receiving system.
Error Handling (see Step 7b).
Commit work.
Project SpecificStep 7b Error Handling
Analyse which fields in the interface are mandatory for the receiving system and who needs to receive error notification.
Declare a structure of type MCMAILOBJ for sending instructions.
Enter values for the internal table based on structure MCMAILOBJ
For selection processes, on SY-SUBRC checks and where fields are mandatory for the receiving system; insert Function Module MC_SEND_MAIL.
Enter values in the following parameters: -
MS_MAIL_SENDMODE = B (Batch Mode)
MS_MAIL_TITLE = 'Mail Title'
MS_MAIL_DESCRIPTION = Error description (e.g. MATNR not given)
MS_MAIL_RECEIVER = Name of Receiver (To be determined)
MS_MAIL_EXPRESS = E (Express Delivery)
MS_MAIL_DLINAME = Leave Blank
MS_MAIL_LANGU = 'E' (Language)
MS_MAIL_FUNKOBJ_NAME = Leave Blank
TABLES
MS_MAIL_CONT = I_MCMAILOBJ
Note:
It has to be determined separately for each interface how these errors and mail notifications are to be grouped dependant upon the number of errors that are potentially likely. One possible approach is to send an email for each reason for rejection and include all the records that failed for that reason in the mail notification. Another possible approach is to send an email for every failure.
When error checking for mandatory fields it is common SAP practice to reject a record on its first failure (irrespective of subsequent errors in that record)
Step 7
(Transaction WE57)
Assign the custom function module to the IDoc type and the message type.
Set function module to type F and direction 2 for inbound.
Step 8
(Transaction WE42)
Create a new process code and assign it to the function module. The process code determines how the incoming IDoc is to be processed in SAP.
Step 9
(Transaction BD67)
Assign the function module to the process code created above. Got to New Entries and enter the process code and the function module name.
Step 10
(Transaction WE20 and Transaction BD64)
Create a partner profile for your message and ensure that in transaction WE20 the process code is the one that points to your function module. (See step 6 of creating Outbound Idocs).
Step 11
Ensure that error handling functionality is present.
If u still have doubt, i can send u the print screen doc - hope this helps u
Reward pts if found usefull :)
regards
Sathish

Simple Examples on ABAP Objects without using include or function modules

Hi,
I am new to ABAP. I need simple example codes on ABAP Objects. It should not have Includes or Function Modules. Just simple codes, using local & global classes, interfaces etc. I searched the forum and even <<the site that shall not be mentioned>>, but did not find a solution. Kindly help please.
Regards,
Smruthi.
Edited by: Matt on Mar 1, 2009 1:20 PM - forbidden site reference removed

Hello Smruthi
If you go to the Forum Search and choose the forum ABAP Objects then serach for ZUS_SDN and you will find many of my simple sample reports.
These reports usually do not contain any includes but they may call function modules which makes perfectly sense. For example, if you are still doing a direct table SELECT instead of using an available BAPI (or class) to get a business object then this is a clear sign of poor (=non-ABAP-OO) programming.
Regards
Uwe

How to find which function module write the relevant idoctype?

Dear All,
how to find which function module write the relevant idoctype?

Hi,
Generally the function modules of the idoc types are having a naming convention as IDOC_INPUT for inbound processing and IDOC_OUTPUT for outbound processing followed by the idoc type name
for example : For IDOC type ORDERS
the inbound function module will be IDOC_INPUT_ORDERS and for outbound IDOC_OUTPUT_ORDERSP
In this way you can find the function module for a particular IDOC
P.S: Hope this is what you have asked for
Regards
Sarves

What are the Includes in Function Module...? if the fuction group IS ZSJ_FC

Similar Messages

Maybe you are looking for