Function Module to save existing Shipment Document

Hello,
I have a list of deliveries and I want to re-save the shipment document so the corresponding output types of the shipment documents are re-triggered. I am currently working in 4.6C and there is no BAPI to change the shipment document. Please let me know if there is any FM that can be used to re-save the shipment document.
My ultimate requireent is to trigger the output type in the shipment. However when i re-save shipment document without any change, it does not triggeres the output type. How can we trigger the output type in shipment based on some condition in delivery?
Thanks & Regards,
Rohit
Edited by: Rohit Malik on Dec 9, 2010 6:02 PM

Thanks Sravanthi. But I still have some more issue with this BAPI. 'Coz I my requirement is to add a new screen enhancement. So I created additional custom fields to table AFIH. This is my problem, I can't find ways to update those fields.
When I looked in your BAPI, I can't find ay structure there that includes those custom fields for update. Do you have more idea on this? Any reply will be highly appreciated.

Similar Messages

RSAR_TRFC_DATA_RECEIVED Function module does not exist or EXCEPTION raised

Dear All,
We have 2 production systems one is a APO server & the other being BW server.
While checking in SM58 of our APO production server we found that so many entries were in error saying "ERROR REQU_<number> PG# 12 In BW" with target system as BWCLNT<CLIENT NO>.
We checked in both the production systems for any job failure w.r.t same time span but could find nothing.
When we tried to solve this by using F6 option to re-execute the LUW it says "Functional Module doesnot exists or Exception Raised". After doing checks it was found out that the Functional Module (RSAR_TRFC_DATA_RECEIVED) was existing . So we need to know about how we can solve this EXCEPTION RAISED issue.
Thanks & Regards,
SAPAPO
Edited by: SAP-APO on Dec 30, 2009 8:38 AM

Hi,
This migth be problem with not catching exact exception in the code.There might be data you are passing which not getting caught by the exception.
If you are using any code add this FM in the code or else try to debug where exactly u r facing this problem.
Regards,
Shiva Kumar G.C

Function module for checking existance of rfc destination?

hi all,
is their any function module for checking existance of rfc destination?
regards
deepak

Hi,
check teh table 'RFCDES'.
reward if helpful.
Regards,
nagaraj

Function module does not exist in ECC 6.0

Hi All,
These two below function module does not exist in ECC 6.0 but exist in 4.6.Could you please let me know replacement of these two's.
FI_DOCUMENT_ARCH_READ_SINGLE
CHECK_IBAN_ACTIVE
Thanks
Mohit

Hi,
Thanks for your reply.Could you please give me example that how to use it.
Thanks
Mohit

Error in ERM: Function module does not exist

Hi all,
Lately, we are experiencing a frequent error in ERM (5.3 SP 15.0) that we had not had before. We are unsure what caused the error. The message displayed to the user is "Unhandled error". The log error message is "Message Code is 651 Messsage Details Function module does not exist Message Type is E" (see full logs below).
The error occurs for example, when users are trying to generate derived roles after saving the org values for the derived role during the methodology process, or when administrators are trying to update the impacted derived roles after for org value mappings.
Has anyone experienced this or someting similar before? Any ideas what could be the reason here?
Thanks!
Patrick
Edited by: Patrick Weyers on Sep 15, 2011 9:36 AM

Log extract:
2011-09-15 09:05:15,103 [SAPEngine_Application_Thread[impl:3]_18] ERROR Message Code is 651 Messsage Details Function module does not exist Message Type is E
java.lang.Throwable: Message Code is 651 Messsage Details Function module does not exist Message Type is E
     at com.virsa.re.service.sap.dao.ManageAuthDataDAO.getAuthorizationData(ManageAuthDataDAO.java:1064)
     at com.virsa.re.bo.impl.AuthorizationDataBO.getNewTransactionObjects(AuthorizationDataBO.java:821)
     at com.virsa.re.role.actions.AuthAuthorizationDataAction.addObjsForNewTxns(AuthAuthorizationDataAction.java:3527)
     at com.virsa.re.role.actions.AuthAuthorizationDataAction.reloadTransactions(AuthAuthorizationDataAction.java:4128)
     at com.virsa.re.role.actions.AuthAuthorizationDataAction.execute(AuthAuthorizationDataAction.java:157)
     at com.virsa.framework.NavigationEngine.execute(NavigationEngine.java:273)
     at com.virsa.framework.servlet.VFrameworkServlet.service(VFrameworkServlet.java:230)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
     at com.virsa.framework.servlet.VFrameworkServlet.service(VFrameworkServlet.java:286)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:117)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:62)
     at com.virsa.comp.history.filter.HistoryFilter.doFilter(HistoryFilter.java:43)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:58)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:384)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(AccessController.java:219)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
2011-09-15 09:05:15,105 [SAPEngine_Application_Thread[impl:3]_18] ERROR com.virsa.re.role.actions.AuthAuthorizationDataAction
java.lang.Throwable: java.lang.NullPointerException
     at com.virsa.re.service.sap.dao.ManageAuthDataDAO.getAuthorizationData(ManageAuthDataDAO.java:1084)
     at com.virsa.re.bo.impl.AuthorizationDataBO.getNewTransactionObjects(AuthorizationDataBO.java:821)
     at com.virsa.re.role.actions.AuthAuthorizationDataAction.addObjsForNewTxns(AuthAuthorizationDataAction.java:3527)
     at com.virsa.re.role.actions.AuthAuthorizationDataAction.reloadTransactions(AuthAuthorizationDataAction.java:4128)
     at com.virsa.re.role.actions.AuthAuthorizationDataAction.execute(AuthAuthorizationDataAction.java:157)
     at com.virsa.framework.NavigationEngine.execute(NavigationEngine.java:273)
     at com.virsa.framework.servlet.VFrameworkServlet.service(VFrameworkServlet.java:230)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
     at com.virsa.framework.servlet.VFrameworkServlet.service(VFrameworkServlet.java:286)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:117)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:62)
     at com.virsa.comp.history.filter.HistoryFilter.doFilter(HistoryFilter.java:43)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:58)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:384)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(AccessController.java:219)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

XI datasources function modules does not exist after BW upgrade to 7.3

We have recently upgraded our dev BI system to 7.3
During our testing phase we found that we are unable to load data coming from XI system.
When we checked the functional modules of the XI(web services)
datasources we found that the function modules does not exist in the system.
Eg : For our GECARS datasource we have 2 funcitonal modules
1. /BIO/QI6AZXH_ZIFIGECARS
2. /BIO/QI6AZXH_ZIFIGECARS_RFC (delta function module)
we have activated resp datasource and found that code for
/BIO/QI6AZXH_ZIFIGECARS exist now but we are facing issues with RFC
funciton modules (/BIO/QI6AZXH_ZIFIGECARS_RFC )
To put it in simple terms we are facing issues with Dev BI since upgradeto 7.3 with respect to RFC and non-availability of function modules.
Kindly help us in resolving this.
Thanks,
Kiran

Hello Kiran,
Have you found the reason for the non existence of the FM in the system after the upgrade?
Have you found any alternative? I hope you would have created an OSS message, if so whats the response have you got?
Kindly let me know as I am experiencing similar issue where one of the FM (RSDRC_MULTIPROV_GET_MAPPING) does not exist in BI system after the upgrade.
Regards,
Vinoth V

Function Module which creates goods receipt document

Dear all:
Do you know a function module which creates goods receipt document?
Thanks
Bac

Hello, Satyanarayana and Mickael,
I found the function module. It is called BAPI_GOODSMVT_CREATE.
Thank you for your suggestion. I think your suggestion works also, so now I have two solutions that I can use.
Bac

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)
<b>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.</b>
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
<b>Reward pts if found usefull :)</b>
regards
Sathish

Function Module Does not exist

Hello Experts,
I am trying to run the initialization for the Billing conditions 2lis_13_vdkon datasource.
Job is getting cancelled and the following error messages are coming when i check the job log in source system
Job started
Step 001 started (program SBIE0001, variant &0000000006238, user ID BASIS
Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
DATASOURCE = 2LIS_13_VDKON
RLOGSYS    = BWDCLNT900
REQUNR     = REQU_DHKONXGA1B82HZ49O94KQ03C4
UPDMODE    = C
LANGUAGES = *
*          Current Values for Selected Profile Parameters               *
* abap/heap_area_nondia......... 2000683008
* abap/heap_area_total.......... 2000683008
* abap/heaplimit................ 40894464
* zcsa/installed_languages...... ED
* zcsa/system_language.......... E
* ztta/max_memreq_MB............ 2047
* ztta/roll_area................ 3000320
* ztta/roll_extension........... 2000683008
Function module /BI0/QI2LIS_13_VDKON does not exist
You can only use LIKE and TYPE to specify types in RFC
Internal session terminated with a runtime error (see ST22)
Job cancelled
even when i check in ST22
Category
ABAP Programming Error
Runtime Errors
IMPORT_ALIGNMENT_MISMATCH
Except.
CX_SY_IMPORT_MISMATCH_ERROR
ABAP Program
SAPLMCEX
Application Component LO-LIS
Date and Time
06.05.2014 12:30:28
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_IMPORT_MISMATCH_ERROR', was
not caught in
procedure "MCEX_BW_LO_API" "(FUNCTION)", nor was it propagated by a RAISING
clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
When importing object "MC13VD0KON_TAB", the structure did not match the
structure of the target object. The error occurred in component
no. 21.
This may be due to one of the following reasons:
- the structure is actually different (the next field has, for
example, a different data type) or
- the same sequence of components were exported and imported,
but the fields were from other include units.
How to correct the error
There is a probably a new version of the program active that does
not match the dataset. The data may not have been converted.
It is also possible that the field type of the imported field
has been changed in the Data Dictionary.
Try to eliminate the error by regenerating the program "SAPLMCEX". To
do this, proceed as follows:
Call Transaction SE38 in the R/3 System, enter the program
name "SAPLMCEX" and then choose "Generate".
If the error occurred in your own ABAP program or in an SAP
program you modified, try to remove the error.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"IMPORT_ALIGNMENT_MISMATCH" "CX_SY_IMPORT_MISMATCH_ERROR"
"SAPLMCEX" or "LMCEXU06"
"MCEX_BW_LO_API"
If you cannot solve the problem yourself and want to send an error
please help me in this regards
Quick response will be appreciated.
Thanks in advance

Hi Ram,
no upgrades recently
they have taken backup from production server.
now i am facing this prob in development server.
when i am trying to check in RSA3 it is throwing same short dump
as u said i did all the re activations still i am facing the same issue.
please give me some other sol...
thanks,
srikanth Putta'

Function Module For Customer Receivable Invoice Document Wise

Dear All,
Is there a standard Function Module / BAPI available for calculating Customer Receivable amount invoice document wise? I will explain the scenario in greater detail:
1) Invoice is booked against customer (FB70 / SD Interface)
2) Receipt is made (F-28 )
3) Matching of invoice is done at the time of receipt (either partial or residual)
4) Customer Account Clearing is done (F-32)
We have explored tables BSID,BSAD,BSEG and BSE_CLR, but are unable to decipher the exact logic by which the System is storing the cleared amount, invoice document wise. We have tried referring to BSEG-REBZG (Invoice Reference) and BSE_CLR for finding out the clearing document and thus arriving at the invoice document balance, but the table entries are not similar in case of partial and residual payment and hence it is creating problem in deducing the actual invoice wise open balance. Can anyone refer to some FM / API / Logic for deducing the same?
Your inputs will be sincerely appreciated.
Thanks and Sincere Regards,
Amitabha

Hi People,
Any ideas?
Thanks and Sincere regards,
Amitabha

Function module - post new G/L document

What function module can I use to post a new document in FI?
BR.

Hi,
Please refer to the link below and see if it helps
Re: Posting Key in BAPI_ACC_DOCUMENT_POST
Regards
K.R

Function module to read the pdf document.

Hi guys ,
I need to know the function module which is used to read all the documents(pdf).?
Regards,
vinothkumar.G

Hi
If you need to open and show a pdf file you can use the method EXECUTE of class CL_GUI_FRONTEND_SERVICES.
CALL METHOD cl_gui_frontend_services=>execute
EXPORTING
document = 'MY_FILE.pdf'
APPLICATION =
PARAMETER =
default_directory = path
MAXIMIZED =
MINIMIZED =
SYNCHRONOUS =
OPERATION = 'OPEN'
EXCEPTIONS
cntl_error = 1
error_no_gui = 2
bad_parameter = 3
file_not_found = 4
path_not_found = 5
file_extension_unknown = 6
error_execute_failed = 7
synchronous_failed = 8
not_supported_by_gui = 9
OTHERS = 10
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.

Error EU 802: Function Module does not exist

Hello everyone!
While running a DTP, I'm getting the following error:
EU 802: Function Module RSD_YPERSON_TXT_GET does not exist
Anyone has any idea what this is about?
Thanks in advance for your responses!
Best Regards,
Luís.

Hi,
I have resolved this issue. Turns out that I was mapping a source field INPER (In-Period) directly to 0CALMONTH. The problem is that this source field can have more than 12 periods per year.
The error message was totally misleading... there's SAP for you
Points assigned for the effort.
Best regards,
Luís.

Upgrade: Function Module does not exist

Hi Experts,
transaction FOIM is giving DUMP in ECC.
It shows a message
Function module "/CUKREQ/RECN_EVENT_FMOD2" not found.
This function module exist in 4.6c.
Will anyone suggest what to do?
Regards:
Vipin

Check for a SAP note in service.sap.com

Function Module does not exist error during query run time.

Hi,
During the execution of one of our queries we get the error "Function module RSD_(InfoObject Tech Name)_TXT_GET does not exist.
Now, this InfoObject is used in the query as a filter to restrict on certain values.
I searched in SE37 and no such function exists.
Let me know if you have any suggestions/resolutions to this issue.
Thanks,
AR.

even if the question is quite old already, maybe some other people need the answer to this, too:
In our case this error which Sudhir Anandarao describes meant, that there was no data found for given input. This is quite strange, but definitly was the source as I dont get the error if something is found by the query. The Query, InfoObject were correct, just the data asked for was wrong (like get me all ID's greater than 5, if there are only ID's smaller or equal 5 it would state "Function module RSD_(InfoObject Tech Name)_TXT_GET does not exist.")

Function Module to save existing Shipment Document

Similar Messages

Maybe you are looking for