Function modules from the function pool Z_MEREP_G (Message no. MEREP_00530)

We installed a new system and imported the syncbo definitions to this new system.
After the import and generation of all T01 SyncBOs we get an error. E.g. for MAM25_016:
Function modules from the function pool Z_MEREP_GEN_T01_MAM25_016 contain syntax errors
Message no. MEREP_00530
After investigation the following syntax error is shown:
Source code LZ_MEREP_GEN_T01_MAM25_016U04 Line 641
The FORM "MAM25_016_CONV_NAME" does not exist, but there is a FORM with the similar name "MAM25_016_I_CONVERSION".
"MAM25_016_I_CONVERSION".
We are already using three systems D -> Q -> P. The export/import of files between these systems work okay. But not with the new system. All are on NW04 SPS 18. In the other systems the form is available.
Does someone have an idea how to solve this?
Thanks in advance,
Benjamin de Rijke

Hello Rahul / Karthick,
Thanks for the tip, I already reimported these with no effect. Next to this I deleted the function modules for a Z-syncbo (our own developed one). But this didn't help as well. The MAM-SyncBO function group can not be deleted because the system is not a developement system. We are not allowed to develop things in this environment.
I have the feeling that it has something to do with the initial setup of this system. All the others were first on SPS15 were we developed the SyncBOs. At a certain time we updated the systems to SPS18 and developed further. No issues so far regarding the import / export of the files from D to Q and P.
Now we initial installed a new system on SPS18 and on this one the generation failes with the mentioned syntax error.
Kind regards,
Benjamin

Similar Messages

How to call a function module from the Web Template?

Hi all,
how can I call a function module from a BI 7.x web template and then show the result of the FM on the web template?
Many thanks for your hints.
Regards, Nils

Hi!
I am too working on a similar issue.
Probably this helps:
Re: Calling a function module from a Web Template
Regards,
Sri

Copying function module from one function group to another

What is the efficient way to copy a module from one group to other so that all its subroutines and any dependencies with in the FM can also be copied?

Hello,
Tcode:SE37
Menu: FunctionModule->OtherFunctions->Copy in that there are different option give a new name of the function group this should work
regards
suresh nair

Unable to find the RFC function module in the impoting list in IR

HI
I am trying to import a RFC function module from the R/3 system.
I am not able to find the RFC in the list that comes for the RFC function modules that can be imported.
The RFC is present in the destination system and is actiated too
If anyone has and idea why is such a thing happning
Regards
Nikhil

Hi Nikhil,
The Checklist,
1. Check the connection parameter at XI
2. Make sure ur function module is remote enabled
3. Make sure ur RFC exists for the same user, client credentials
Regards,
Prateek

Can a function module call another function module

Can a function module call another function module:-
within the same function group
(ii) within different function groups

Hi,
We can call function from another function. If there is a function which is like a calculator and all the operations are from different functions then we have to call the functions from the calculator function for different functions.
If all the function are from same function group, Then the data is globally available to all the functions with in the group.
Otherwise we have to declare the data definitions for each of the functions if they are in different function groups.
Yes it is possible to call a function module from another function module:-
within the same function group
(ii) within different function groups
Reward.

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

Execute function module from Custom Table Value?

Hi,
I have custom table with following field
FUNNAME CHAR 1000
That contains records like the following
CALL FUNCTION 'ZMATF' EXPORTING MATNR = P_MATNR IMPORTING MATDESCRIPTION = V_MATERIALDESC.
CALL FUNCTION 'Y_CHECK_EXIT' EXPORTING USEREXIT = 'EFNDTAXWAR' IMPORTING EXECUTE = EXECUTE TABLES I_ZA01 = I_ZA01.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT' EXPORTING WAIT = 'X'.
CALL FUNCTION 'RS_TABLE_LIST_CREATE' EXPORTING TABLE_NAME = TABNAME.
My requirement is according some of the user conditions i need to select entry from this table and execute the corresponding function module
I tried to use GENERATE SUBROUTINE POOL itab NAME name. But this have limitation of 36 subroutine pools for one program.
Any info highly appreciated.
aRs

If you can put the name of the FM in a variable and the parameters and exceptions in separate internal tables, then you can call the function modules using the statement:
call function NAME
parameter-table
 PARA_TAB
exception-table
 EXCP_TAB.
See a small example:
Example
type pools ABAP.
data NAME type STRING value `READ_SPFLI_INTO_TABLE`.
data PARA_TAB type ABAP_FUNC_PARMBIND_TAB.
data PARA_LINE like line of PARA_TAB.
data EXCP_TAB type ABAP_FUNC_EXCPBIND_TAB.
data EXCP_LINE like line of EXCP_TAB.
data CARRIER type SPFLI-CARRID.
data JTAB type SPFLI_TAB.
CARRIER = 'XYZ'.
PARA_LINE-NAME = 'ID'.
PARA_LINE-KIND = ABAP_FUNC_EXPORTING.
get reference of CARRIER into PARA_LINE-VALUE.
append PARA_LINE to PARA_TAB.
PARA_LINE-NAME = 'ITAB'.
PARA_LINE-KIND = ABAP_FUNC_IMPORTING.
get reference of JTAB into PARA_LINE-VALUE.
append PARA_LINE to PARA_TAB.
EXCP_LINE-NAME = 'NOT_FOUND'.
EXCP_LINE-VALUE = 1.
insert EXCP_LINE into table EXCP_TAB.
EXCP_LINE-NAME = 'OTHERS'.
EXCP_LINE-VALUE = 4.
insert EXCP_LINE into table EXCP_TAB.
call function NAME
parameter-table
 PARA_TAB
exception-table
 EXCP_TAB.
case SY-SUBRC.
when 1.
 message id SY-MSGID type SY-MSGTY number SY-MSGNO.
when 2.
 message E888(SABAPDOCU) with 'Error in function module'.
endcase.
REgards,
Ravi

Call ABAP function module from script?

Hi,
I have an ABAP function module, which works fine when I call it in a transformation.
Since I don't need to execute this function for each record but rather for each file I process, I would like to move the call from the DataFlow to a script in the WorkFlow. When I click on the 'functions' button the ABAP FM is available in my SAP Datastore, so I drag and drop it into my script. I also make sure to populate all required variables.
There are no error messages or warning when I check my job definition.
When I execute it, I get the following RFC error:
Function call <xxx ( abcd ) > failed, due to error <150413>: <RFC CallReceive exception <FUNCTION_NOT_FOUND>.>.
Is it just not possible to call an RFC enabled function module in SAP from a script or am I doing something wrong here?
Thanks,
Jan.

Could you please let me know how I can call an abap function module from a transformation? (from abap xslt program). I know how we can call methods of a class from the transformations, but no idea how we can call function modules. Any suggestions or a sample code snippet towards this will be very useful for me.
Thanks,
Shashi.

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

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

CNTL_ERROR while calling a function module from Java webdynpro

I am calling a RFC function module from javawebdynpro app
which inturn calls a function module performing BDC on CAPP transaction. When I run this from SE37 of the same system or a different system everything works fine. But when called from Java webdynpro app, it raises a CNTL_ERROR exception and creates a short dump.
Any help on this is highly appreciated

Good catch, BI Learner. This was exactly it: when assigning the values from SOURCEFIELDS directly to the import/export parameters, you have to make sure that the types are EXACTLY the same, otherwise it will not work (the routine stops with an error when calling the FM, but there is no dump).
Therefore, to solve my problem, I created the declarations precisely as expected by the FM and assigned the values to these fields:
DATA:
      SOURCEVAL TYPE /BIC/OIINVQTY,
      SOURCEUOM TYPE /BIC/OIUSUOM,
      USITM TYPE /BIC/OIUSITM,
      TARGETUOM TYPE /BIC/OIUSUOM,
      CONVERTED_COST TYPE /BIC/OIINVQTY.
DATA PRODUCTION_UOM TYPE /BIC/OIUSUOM.
" get the Production UOM
    SELECT SINGLE I~/BIC/USPRDUOM
      FROM /BIC/PUSITM AS I
      INTO PRODUCTION_UOM
      WHERE I~/BIC/USITM = SOURCE_FIELDS-/BIC/USITM AND I~OBJVERS = 'A'.
    IF ( SY-SUBRC = 4 ). " no records found
      "RAISE PARTNO_NOT_FOUND.
      RAISE EXCEPTION TYPE CX_RSROUT_SKIP_RECORD.
    ENDIF.
" load the parameters
    SOURCEVAL = SOURCE_FIELDS-/BIC/USFRZMFC.
    SOURCEUOM = SOURCE_FIELDS-BASE_UOM.
    USITM = SOURCE_FIELDS-/BIC/USITM.
" then you can call the FM
    CALL FUNCTION 'Z_CA_CONVERT_US_COST'
      EXPORTING
        PSOURCEVAL                = SOURCEVAL
        PSOURCEUOM                = SOURCEUOM
        PUSITM                    = USITM
        PTARGETUOM                = PRODUCTION_UOM
      IMPORTING
        PTARGETVAL                = CONVERTED_COST
      EXCEPTIONS
        CONVERSION_NOT_MAINTAINED = 1
        PARTNO_NOT_FOUND          = 2
        OTHERS                    = 3.
" ... [do the rest]
Thanks for your help,
Dennis

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 to call a function module from a transformation

Hi,
Could somebody please let me know how I can call an abap function module from a transformation (abap xslt program). I know how to call the class methods from transformation, but how do i call a function module..?
Thanks,
Shashi.
Edited by: Shashi Kanth Kasam on Apr 8, 2010 12:45 PM

Ya. I can do that. But I don't want to use a class and a method to call that function module. Want to directly call function module from transformation. Is that possible..?
Thanks,
Shashi

Calling Z function module from BSP page

hi,
i am calling a z function module from BSP application ROS_SELF_REG ,The z function module is inside a z function group,It does not give any sytnax error..but while running BSP application ,it is going into dump saying that Z function module is not found..Any idea why this is happening???

Hi,
Check whether the Z function module is spelled correctly. Also try activating the whole function group and function module in se80 transaction.
Check whether the BSP application is calling the Z FM from the correct server/client where it is available.
Regards,
Harish

Passing values to an InternalTable in a Function Module from WebDynpro

Hi,
I have created a model from a function module that has a internal table.I have assigned the value as a String to the datamodel context element of the internal table as a Line in the node that represents the input for the funtion module.The internal table accepts a value as an input.When i call the execute method on the input node i am not able to pass the value from the Webdynpro to the function module.I have also checked the assignment of the value as a String to the datamodel context element of the internal table as a Line in the node that represents the input for the funtion module and the value was assigned.
If you can provide me any info on how to pass the internal table from Webdynpro to the function module will be very helpful ..???
Thanks In Advance,
Varma.

Hi Rajendra,
what u can pass to a function module is the parameter which are in import and tables of RFC .so u have to declare a variable as a type of your internal table which may be type of structure or table. then in your RFC u have to copy that into a variable of function module and go for ur logic ...

Function modules from the function pool Z_MEREP_G (Message no. MEREP_00530)

Similar Messages

Maybe you are looking for