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

Similar Messages

Using a function module i want to create another function module

Hi all,
My requirement is by using a function module i want to create another function module(if needs modify action should also be done if i need this is for the created function module) and the main thing is that the function module which we are used to create is should be RFC enabled.
Thanks,
Vichu.

Hi,
You can do one thing... you write the BDC code in the function module name you are creating... so that if you call the function module in a program and execute that program and if you give the function module to be created in the selection screen of the program... in this way there is chance of creating another function module.
Hope this would help you.
Good luck
Narin

How to create a custom function module with the records in SAP R/3?

Hi All,
How to create a custom function module with the records in SAP R/3? Using RFC Adapter I have to fetch the custom function module records.
Regards
Sara

Hi
goto se37...here u need to create a function group... then u need to create a function module. inside assign import/export parameters. assign tables/exceptions. activate the same. now write ur code within the function module
http://help.sap.com/saphelp_nw04/helpdata/en/9f/db98fc35c111d1829f0000e829fbfe/content.htm
Look at the below SAP HELP links, These links will show you the way to create a Function Module
http://help.sap.com/saphelp_nw04/helpdata/en/26/64f623fa8911d386e70000e82011b8/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/9f/db98fc35c111d1829f0000e829fbfe/content.htm

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

Howt 2 delta with the extractor created on Function Module..

hi there,
can anybody tell me how to update delta with the extractor created on Function Module..
rgds,
amol

refer to the document at the below link
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d3219af2-0c01-0010-71ac-dbb4356cf4bf
Generic Extractor using FM with Delta Logic
hope it helps,
rgs,
Parth.
Edited by: Partho Mukherjee on Jan 12, 2009 6:00 PM

Is there any function module or BAPI to create maintenance item.(Urgent)

Hi Experts,
 I want to create an RFC which creates the maintenance item in the sap. The RFC is going to receive data from XI. So is there any function module or BAPI to create maintenance item? so that i can call that FM in my RFC.
Thanks,
Prasanna
Helpful answers will be rewarded.

Check and implement your program accordingly:
*& Report ZMRS_BAPI_DEMO_ORDERS
REPORT ZMRS_BAPI_DEMO_ORDERS.
DATA: gs_method TYPE bapi_alm_order_method,
 gs_header TYPE bapi_alm_order_headers_i,
 gs_header_up TYPE bapi_alm_order_headers_up,
 gs_return TYPE bapiret2,
 gs_numbers TYPE bapi_alm_numbers,
 gs_return_commit TYPE bapiret2,
 gs_demo_order TYPE objidext,
 gt_demo_order LIKE TABLE OF gs_demo_order,
 gt_method LIKE TABLE OF gs_method,
 gt_header LIKE TABLE OF gs_header,
 gt_header_up LIKE TABLE OF gs_header_up,
 gt_return LIKE TABLE OF gs_return,
 gt_numbers LIKE TABLE OF gs_numbers,
 gt_return_commit LIKE TABLE OF gs_return_commit.
DATA lv_not_successful TYPE c.
DATA lv_ref_cnt TYPE i.
IMPORT gt_method FROM MEMORY ID 'MET'.
IMPORT gt_header FROM MEMORY ID 'HED'.
IMPORT gt_header_up FROM MEMORY ID 'HUP'.
CALL FUNCTION 'BAPI_ALM_ORDER_MAINTAIN'
TABLES
 it_methods = gt_method
 it_header = gt_header
 it_header_up = gt_header_up
 return = gt_return
 et_numbers = gt_numbers.
CLEAR lv_not_successful.
LOOP AT gt_return INTO gs_return.
IF gs_return-type = 'E'.
 lv_not_successful = 'X'.
ELSEIF gs_return-type = 'W'.
 lv_not_successful = 'X'.
ELSE.
do nothing
ENDIF.
ENDLOOP.
IF lv_not_successful <> 'X'.
commit changes
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
 EXPORTING
 wait = 'X'
 IMPORTING
 return = gs_return_commit.
ELSE.
rollback changes
CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'
 IMPORTING
 return = gs_return_commit.
ENDIF.
EXPORT gt_return TO MEMORY ID 'RET'.
EXPORT gs_return_commit TO MEMORY ID 'COM_RET'.

Require Function module or BAPI to create recurring GL entries in FBD1

All,
Are there any function modules or BAPI to create recurring GL entries as done through FBD1 transaction.
Help is very much appreciated.
Regards,
Hari

BDC Session is the best approach available. In order to have a clean BDC, use the Fast Data entry screen available in the transaction, which will help you in opening up all the fields irrespective of the field status groups

Rfc enabled function module for the updating the database table

Hi,
I need one rfc enabled function module for the updating the database table from the legacy system.currently i am using the rfc_read_table to read the database table.similarly i need for the update.

Hi
I believe you need to create one by yourself
Max

How to create RFC function module and how to call this function module

Hi,
i want to know step for creating RFC function module and then How to use this function module from some other sap system.
Thnaks,
jigar

Jigar,
To implement a remote function module in ABAP, perform the following steps:
Register the module as remotely callable in the RFC server system.
In the function module Administration screen (transaction code SE37), set the field Can be called via REMOTE CALL. Registering a module as remote causes an RFC stub to be generated for it.
Write the code for the function module.
Create the destinations.....................
Displaying, Maintaining and Testing Destinations
To display, create or modify destinations, choose Tools ® Administration ® Administration ® Network ® RFC destinations or enter transaction code SM59.
Remote Destinations are stored in table RFCDES. The RFCDES table describes logical destinations for remote function calls.
It is not possible to maintain the RFCDES table directly.
You can also access logical destinations via the Implementation Guide (IMG) by choosing Tools ® AcceleratedSAP ® Customizing ® Execute Project ® SAP Reference IMG.
In the Implementation Guide, expand the following hierarchy structure:
Basis
Application Link Enabling (ALE)
Sending and Receiving Systems
Systems in Network
Define Target Systems for RFC Calls
Displaying Destinations
The initial screen for this transaction displays a tree:
Different connection types (i.e. partner systems or programs) are possible. For further information, see Types of Destinations.
To display all information for a given destination, double-click it, or place the cursor on it and press F2 .
To search for a destination, press the Find button and specify your selection. You get a list of all entries matching your selection. Place the cursor on the one you want, and press F2 or simply double-click the destination. All information for the given entry appears.
Creating Destinations
On the destinations overview screen (transaction code SM59), the connection types and all existing destinations are displayed in a tree structure.
All available connection types are explained in Types of Destinations.
To create a new RFC destination, press the Create button. A new screen is displayed with empty fields for you to fill in.
If you want to create a new destination
As you create a remote destination, you can specify a particular application server or a group of servers for a balanced distribution of system load.
For details of the destination parameters, see Entering Destination Parameters.
Changing Existing Destinations
On the destinations overview screen (transaction code SM59), the connection types and all existing destinations are displayed in a tree structure.
You can display all information for a given destination by double-clicking it or pressing F2 on it.
To change an existing destination, double-click it, or place the cursor on it and press the Change button.
For details of the destination parameters, see Entering Destination Parameters.
Testing Destinations
To test a destination, choose the appropriate function from the Test menu.
Connection (also available via the Test connection pushbutton)
Authorization (checks logon data)
Local network (provides a list of application servers)
You can use the CALL FUNCTION statement to call remote functions, just as you would call local function modules. However, you must include an additional DESTINATION clause to define where the function should run:
CALL FUNCTION RemoteFunction
DESTINATION Dest
EXPORTING
f1 =...
f2 =...
IMPORTING
f3 =...
TABLES
t1 =...
EXCEPTIONS......
The field Dest can be either a literal or a variable: its value is a logical destination (for example, "hw1071_53") known to the local SAP System. Logical destinations are defined in the RFCDES table (or the TRFCD table in R/2 Systems) via transaction sm59 or the following menu path: Tools ® Administration, Administration ® Network ® RFC destinations. You can also access logical destinations via the Implementation Guide (IMG) by choosing Tools ® Customizing ® Enterprise IMG. In the Implementation Guide, you can then choose Cross-application components ® ALE ® Communication ® Define RFC destination.
The remote function call concept, for example, allows you to access a function module in an R/2 System from an ABAP program in an R/3 System. If you want to read a customer record from your R/2 Systems database, create a remotely callable function module in the R/2 environment which retrieves customer records. Call this function from your R/3 System using a remote function call and listing the destination for the target R/2 System:
Pls. reward if useful

Function module for the Inbound Delivery

Dear ABAPers,
        I have created the Inbound Delivery in VL01N Transaction.I want to create the Post goods issue for the Delivery number.What is the Function module for the Post goods issue for the Delivery number and what all the Parameter needs to be passed.
Thanks & Regards,
Ashok.

Hi,
Try this code...
PARAMETERS: p_vbeln LIKE likp-vbeln OBLIGATORY.
DATA:    l_vbkok_wa   TYPE vbkok,
         l_i_prott    TYPE STANDARD TABLE OF prott,
         l_pgi_status TYPE xfeld,
         c_check      TYPE c VALUE 'X'.
l_vbkok_wa-vbeln_vl = p_vbeln.
l_vbkok_wa-vbtyp_vl = 'T'.
l_vbkok_wa-wabuc    = c_check.
Do PGI
CALL FUNCTION 'WS_DELIVERY_UPDATE'
EXPORTING
    vbkok_wa                  = l_vbkok_wa
    commit                    = c_check
    delivery                  = l_vbkok_wa-vbeln_vl
IMPORTING
    ef_error_in_goods_issue_0 = l_pgi_status
TABLES
    prot                      = l_i_prott.
IF l_pgi_status IS NOT INITIAL.
WRITE:/ 'PGI Failure : ', p_vbeln.
ELSE.
WRITE:/ 'PGI Success : ', p_vbeln.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    EXPORTING
      wait = c_check.
ENDIF.
Regards
Meenakshi

How to connect our outbound function module to the message type

how to connect our outbound function module to the message type any transcation code exits to assign the message type with the function module .
Thank in advance .
A. Thiru

Hi Thiru,
Standard Transaction Codes, have their own Function Modules for generating Outbound/Indbound Idocs. Where these Function Modules will be configured to a particular Process Codes.
For E.g for PO's
Process code : ME10 - IDOC_OUTPUT_ORDERS - for creation
In case if its a Z Function Module, It depends on the case how you use IDOC types. either directly through Z Program or through Inbound/Outbound Process codes with respective Function modules.
Regards,
Anbalagan

Function modules for the following

Hi,
I want to know the function modules for the following purposes.
1) Check whether a date is valid or not
2) Calculate the no of days between two dates.
Expecting an early response.
Thanks n Regards,
Amit

Hi,
PARAMETERS: p_list LIKE t009b-bumon AS LISTBOX
 VISIBLE LENGTH 11 OBLIGATORY ,
 p_list1 LIKE t009b-bdatj OBLIGATORY.
SELECTION-SCREEN POSITION POS_HIGH.
PARAMETERS: p_list2 LIKE t009b-bumon AS LISTBOX
 VISIBLE LENGTH 11 OBLIGATORY,
 p_list3 LIKE t009b-bdatj OBLIGATORY.
Calling Function Module for calculating no of days between the
selected period
 CALL FUNCTION 'NUMBER_OF_DAYS_PER_MONTH_GET'
 EXPORTING
 par_month = p_list
 par_year = p_list1
 IMPORTING
 par_days = ws_n_days.
 CALL FUNCTION 'NUMBER_OF_DAYS_PER_MONTH_GET'
 EXPORTING
 par_month = p_list2
 par_year = p_list3
 IMPORTING
 par_days = ws_n_days1.
For Concatenating the month and year into the date format
 CONCATENATE p_list1 p_list ws_i INTO ws_c_date1.
 CONCATENATE p_list3 p_list2 ws_n_days1 INTO ws_c_date2.
date = ws_c_date1 - ws_c_date2.
In the above sample code the selection screen has month and year as input.
Also check this link
http://www.sapdevelopment.co.uk/tips/date/datehome.htm
Check FM
RP_CALC_DATE_IN_INTERVAL Add/subtract years/months/days from a date
SD_DATETIME_DIFFERENCE Give the difference in Days and Time for 2 dates
Also for checking valid date:
U can specify the date field as
Select-options: s_date like likp-date(similar to ur requirement)
This itself ceck for the valid date no seperate validation needed.
Thanks & Regards,
Judith.

How do I "see" a check function module in the debugger?

I am correctly starting a custom workflow based on an event raised by standard SAP code in transaciton QE51N.
I have to write a check function module to interrogate the event and start/not start
the workflow because the same event is raised by SAP code in transaction QA02, and I have to be sure to start the workflow only if the event is raised in QE51N, not QA02. (I also have to check some other properties of the QALS row for the inspection lot.)
I know how to code the check function module, but if I need to debug it, how do I "set-up" for seeing the check function module in the debugger?
I'm sure this is an obvious question and that I'm missing something simple.
So thanks in advance for the answer.
djh

Dear DJH,
Put a break-point in the function module and process the transaction. It will stop at runtime.
Hope this will help.
Regards,
Naveen.

How to find out the inbound function module in the extended idoc

Hi,
how to find out the inbound function module in the extended idocs
Thanks .

through we41/we42 you can find the inbound function module.......
or
thorough we19(idoc test tool) ....
give the input as message type or basic idoc..
press exec...
then you can find th button on application tool bar as inbound funtion module....
from here also you can find..........
<REMOVED BY MODERATOR>
Khasimsa
Edited by: Alvaro Tejada Galindo on Apr 14, 2008 1:34 PM

Function module for the transcation CS02(i.e) BOM

Hi All,
I want the function module for the transction CS02.
Actually I need the details of BOM for any material.
Please help....Its a urgent requirement.
Thanks in advance

Hi,
You can also try with MGW1_CHANGE_BOM and CS_CL_S_BOM_CHANGE
Regards,
Ram
Message was edited by:
Ram Mohan Naidu Thammineni

Function module to the newly created 'Z' function group

Similar Messages

Maybe you are looking for