IDOC types by Function Module

Hello,
I would like to find the IDOC types available by function module. For example, all idoc types for Production Planning module. Is there an easy way to get that info?
Thanks

Hi,
Go to Repository Browser (SE80) -> select Appliction Hierarchy and filter it down by Function Modules. you can now go to individual functional area (SD, MM , PP, etc) and drill down EDI objects hierarchy. You can very well judge the IDOC types based on IDOC Processing function modules.
Hope this will help...
regards,
PB

Similar Messages

RE:Idoc type and function module

HI All
What are the generic IDoc types and function modules used for the following objects ??We are on SAP R/3 4.7.
Invoice Release (inbound)
Payments (outbound)
Purchase Orders (outbound)
Goods Receipts (outbound)
Cost Centers (outbound)
GL Codes (outbound)
Internal Orders (outbound)
WBS (outbound)
Materials (outbound)
Invoices (inbound)
Invoices Blocked (outbbound)
And How do i judge which IDOC types and function module fit my requirement( I mean what are the things i have to keep in mind while choosing idoc types and function modules)?
Any help will be very much appreciated
Thank you
Steve

Hi Steve...
You can find the IDOC types in Tcode WE30 , WE60.
Invoice Release (inbound)
INVOIC03
Payments (outbound)
Purchase Orders (outbound)
ORDERS03
Goods Receipts (outbound)
ACC_GOODS_MOVEMENT02
Cost Centers (outbound)
GL Codes (outbound)
Internal Orders (outbound)
WBS (outbound)
Materials (outbound)
MATMAS04
Invoices (inbound)
ACC_INVOICE_RECEIPT03
Invoices Blocked (outbbound)
<b>REWARD IF HELPFUL.</b>

Types of function Modules

What are different types of function modules ??
Please tell in detail about Normal function modules and RFC enabled functional modules ?
I have searched other threads also but did not get the enough descriptions of the same.
Please respond !

Hi Shreya.
Basically, RFC function modules deal with remote function call which means those ABAP programs can be run/executed from a remote SAP system.
The best example for implementing the RFC Function modules are the BAPIs.
In case of normal function module, The call is made within this SAP system.
RFCs are more often used to establish link between two servers.
Normal function modules provide linking localy that is with the same SAP server/environment.
The calling of RFC function module depends on different client-server specifications.
In case of normal one, the call is same client related call.
Hence, In short RFC for Global
and Normal Function module for Local.
Good Luck.
Harsh

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.

Types in function modules

hi i want to know how many types of function modules are there please help in this .
thankyou
pavan

Hi,
You have so much information regarding this in sdn.
But function modules basically classified into
1)Normal Function Module
2)Remote-Enabled Module
For more information check this link.
http://www.allinterview.com/showanswers/62377.html
Regards and Best wishes.

Possible to trigger output type through Function module?

Hi,
Is it possible to trigger output type through Function modules or through some codings or any standard FM's?
Regards
Bala.

You did not specify what area you need to retrigger an output type for, but here is a sample to retrigger a delivery output.
CALL FUNCTION 'BAPI_LIKP_PROCESS_MSG_DIRECT'
    EXPORTING
DYNAMICOUTPUTDEVICE       =
      processing                       = PROCESSING
SORTMESSAGE               = 1
    TABLES
      deliverynumber                 = delnbrs
      outputtype                       = outputs
      messageprotocol              = bapimsgprot
      return                              = bapiret2.
Thanks

How many types of function modules are there

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

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

Unable to generate IDOCS using IDOC_INPUT_ORDERS Function Module

Hi,
I have written a program to post IDOCS using function module IDOC_INPUT_ORDERS .
In the debugging mode,I found that after the call of this function-module,sy-subrc is set to zero which means that this function-module is getting successfully executed.
But when I go to WE02 transaction code , i do not see any IDOCS being generated for IDOC Type ORDERS05 .
Please could someone help me out with this .
Regards,
Sushanth H.S.

hi
check your ALE configuration:
go thru the links:
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
reward points for useful ans
Regards
Aarti

JDBC to IDoc (Custom inbound function module)

Hi,
In my scenario JDBC to IDoc, I am using a custom function module to change the planned order. When I exectue the function module in WE19, it works fine and the IDoc status is also updated correctly.
But when I execute the entire interface right from JDBC, the status of the IDoc is set to 51 and the description it is giving is "No status record was passed to ALE by the application".
Can any one help me with this, where exactly is the error?

For IDOC status 51 : Inbound IDOC
In WE19, Give the IDOC number & execute ... then put the cursor on the idoc control record . then click on the Standard Inbound push button on the application tool bar.it will show show all the details like partner no,type , message type , process code & function module name ...
now put a break point in the function module .. & debug .
if u r using customised inbound function module , then click on inbound function module .. there u will get a pop screen with FM name & debugging option in both background & foreground mode...

IDOC from inbound function module

Hi All,
I have a inbound function module..
I dont know its Idoc type.
Ho to find the IDOC based on Inbound Function module
Thanks
Amruta

Hi Amruta
Inbound Function Moduel always in the format of IDOC_INPUT_XXXXXXX
xxxxxx is the your Message type...
Based on you message type u can get you idoc type....
if function moduel is Standard one ...
Thanks
Ram

IDOC error 51- Function module not allowed:

Hi,
I am getting following error in IDOC inbouond.I verifyed all parameters mentioned in error.
Issue still not resolved.
When debugged from WE19 this issue dosnt arise.
Kindly guide.
Function module not allowed: ZIDOC_INPUT_MATCLASS
Message no. B1252
Diagnosis
The function module ZIDOC_INPUT_MATCLASS and the application object type BUS1001 which were determined are not valid for this IDoc.
Procedure
1. Please check that the process code in the inbound partner profile is correct.
2. If this is the case, you should check the ALE inbound methods ALE inbound methods for the process code and see whether the specified function module and application object type are correct.
3. If this is also the case, then the function module and the application object type are not permitted for the logical message type, message variant, message function and basis type that are contained in the IDoc control record. You should check whether the correct values have been assigned to these fields in the control record. If they do have the correct values, then the assignment to the function module and the application object type needs to be maintained.

Hi,
Check in WE42, for the process code, you have assigned this function module and given the correct process code in the partner profile.
Sujay

Idoc error 51 - "Function module not allowed - APPL_IDOC_INPUT1'

Hello everyone,
We are uploading GL balances from legacy to SAP using the LSMW Bapi
object - bus6035
method - post
message type - ACC_DOCUMENT
Basic type - ACC_DOCUMENT03
When we run the lsmw, idoc is created, however with an error 51 saying
"Function module not allowed - APPL_IDOC_INPUT1'
The partner no. is the logical system (the system on which the lsmw is executed)
In the partner profile, we have defined this as LS. In the inbound parameters, we have defined message type = ACC_DOCUMENT, the process code is APL1 and the corresponding function module is - APPL_IDOC_INPUT1
Please let me know if we are missing something or doing anything wrong ?
Since the data in the LSMW will be read frmo a file on the presentation server, do we need to have a port configuration for the same ?
Thanks,
Sushil Joshi`

Hello Sushil
The long text of message B1(252) is quite informative for error analysis:
NA B1252
Short Text
     Function module not allowed: &
Diagnosis
     The function module and the application object type which were
     determined are not valid for this IDoc.
Procedure
     1. Please check that the process code in the inbound partner profile
         is correct.
     2. If this is the case, you should check the ALE inbound methods ALE
         inbound methods for the process code and see whether the specified
         function module and application object type are correct.
     3. If this is also the case, then the function module and the
         application object type are not permitted for the logical message
         type, message variant, message function and basis type that are
         contained in the IDoc control record. You should check whether the
         correct values have been assigned to these fields in the control
         record. If they do have the correct values, then the assignment to
         the function module and the application object type needs to be
         maintained.
On ECC 6.0 this long text contains 3 transactions for analysis:
- WE20
- BD67
- WE57
Regards
Uwe

Custom idoc [ related to function module]

HI ALL,
sorry for repeating the question
i had an requirement to create a custom idoc for catsdb table with 4 fields
1. pernr
2. workdate
3. lstar ......
and to transfer it from one application server to another.i had created it n transfered it to another application server. now my problem is in receiver side the data in idoc is not posted into database of catsdb [ at receiver side].
can any one give the code for Custom function module at receiver side so that when idoc is received [from sender] it must be updated to databse tables via this FM.
its very urgent . help me ........................
any suggestions are highly appreciated.
with regards,
Suresh Aluri.

Hi Suresh,
In the receiver system you have to :
1. Create a process code and link with message type using WE42
2. Create an inbound function module using SE37.
For example: BAPI_IDOC_INPUT1
3. Link function module with basic type and message type using WE57
Regards,
Hendy

IDOC inbound processing ( Function module Rquired )

Hi,
I am working on IDOC inbound, I am looking for a standard FM for Production order confirmation which i need to assign in WE57 along with the standard Message type(Production order confirmation).
Could you please let me know where i can get the standard inbound function modules for the standard idoc types,
for eg: IDOC_INPUT_ORDERS for sales order.
Thanks.
Krishnakumar

Hi,
Go to WE42 for inbound processing codes and WE41 for outbound.
OR
We have WE19 which is a test tool for IDOC processing.
Provide the IDOC number then press F8, then in the next screen , you will have inbound function module.
Click that button. Then enter the text in search criteria.
Then you can get related function module.
Reward points if helpful.
Thanks and Regards

Handling pop up of sub type HR_MAINTAIN_MASTERDATA function module

Hi All,
I am using HR_MAINTAIN_MASTERDATA for creating employee it's working fine but i am not able to handle pop up for sub type.
For example sub type for Address it gives me pop up with values 1 Permamant address 2 Office address etc.
Anybody know how to handle such pop up in function module. How to provide values to sub type.
Thanks in advance.

Hi,
<li>Instead of using HR_MAINTAIN_MASTERDATA function module, you can use HR_INFOTYPE_OPERATION, because HR_MAINTAIN_MASTERDATA is used inside HR_INFOTYPE_OPERATION.
<li>Check the sample program .
REPORT ztest_notepad .
DATA:p0006 TYPE STANDARD TABLE OF p0006 WITH HEADER LINE.
DATA:return LIKE bapireturn1.
p0006-pernr = '00001234'.
p0006-subty = '2'.
p0006-endda = '99991231'.
p0006-begda = sy-datum.
p0006-anssa = '2'.
p0006-name2 = 'xyz'.
p0006-stras = 'Street 64'.
p0006-ort01 = 'US'.
p0006-pstlz = '560634'.
APPEND p0006.
CLEAR p0006.
LOOP AT p0006.
CALL FUNCTION 'HR_EMPLOYEE_ENQUEUE'
    EXPORTING
      number = p0006-pernr.
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
    EXPORTING
      infty         = '0006'
      number        = p0006-pernr
      subtype       = p0006-subty
      validityend   = p0006-endda
      validitybegin = p0006-begda
      record        = p0006
      operation     = 'INS'
      tclas         = 'A'
    IMPORTING
      return        = return.
IF return IS INITIAL.
    WRITE 'Successfully records created'.
ENDIF.
CALL FUNCTION 'HR_EMPLOYEE_DEQUEUE'
    EXPORTING
      number = p0006-pernr.
ENDLOOP.
Thanks
Venkat.O

IDOC types by Function Module

Similar Messages

Maybe you are looking for