Counter logic in Function module of the generic extraction

Hi,
I had like to add this counter field which can be used in reporting..
As this extraction logic is bit different, i cannot include it in transformations with 1 as a constant..
so i am wrtiting this logic in Function Module..
in the main table loop i had assigned this counter as 1 and after appending it i am clearing the counter field...
is it a correct way or is there any thing that needs to be taken care?

Hi,
it will put 1 for every record.
Can you share your coding ? please copy past your coding
Regards,
G

Similar Messages

Function Module in a Generic Function Module Extractor

I want to use a generic function module (ZFM_CONNECTION_DETAIL) in a Generic Function Module based Extractor.
After Creating, I have checked it in RSA3... Data is showing properly on the Extractor Check.
And replicated on BW side, after triggering the extractor using infopackageu2026 only one record is coming on the target side (BW).
And one job is running endless on the source system.
Generic extractor on the normal code is working properly on both sides.
But problem occurs while I was using Function Module in the Generic function Module extractor.
Waiting for a Reply with solution...........
Hi Siegfried Szameitat,
I have searched a lot to find out the solution of my Question (Problem). But there is no solution for the problem I have.
Please let me to find out a proper solution of my issue....
Thanks

FUNCTION zcrm_questionnaire.
Its a full Load...
Codes are as followed..........
DATA:lv_times     TYPE i.
DATA:lv_datapakid TYPE numc4.
CLEAR:lv_datapakid,lv_times .
STATICS: s_s_if TYPE srsc_s_if_simple,
           sd_no_more_data TYPE flag.
DATA: l_s_select TYPE srsc_s_select.
DATA : s_counter_datapakid LIKE sy-tabix,
          s_cursor TYPE cursor.
RANGES : date FOR zresult_lt-date.
DATA: lv_count TYPE i VALUE 1.
IF i_initflag = sbiwa_c_flag_on.
Initialization: check input parameters
                buffer input parameters
                prepare data selection
Check InfoSource validity
    CASE i_dsource.
      WHEN 'ZCRM_QUESTIONNAIRE'.
      WHEN OTHERS.
        IF 1 = 2. MESSAGE e009(r3). ENDIF.
        log_write 'E'                  "message type
                  'R3'                 "message class
                  '009'                "message number
                  i_dsource            "message variable 1
                  ' '.                 "message variable 2
        RAISE error_passed_to_mess_handler.
    ENDCASE.
    APPEND LINES OF i_t_select TO s_s_if-t_select.
    s_s_if-requnr    = i_requnr.
    s_s_if-dsource   = i_dsource.
    s_s_if-maxsize   = i_maxsize.
    APPEND LINES OF i_t_fields TO s_s_if-t_fields.
ELSE.                 "Initialization mode or data extraction
    IF NOT sd_no_more_data IS INITIAL.
      RAISE no_more_data.
    ENDIF.
    LOOP AT s_s_if-t_select INTO l_s_select .
      MOVE-CORRESPONDING l_s_select TO date.
    ENDLOOP.
    DATA : v_questionire TYPE crm_svy_db_sid.
    DATA : itab_questionire TYPE zsurveyid.
    DATA : e_tt_data_get TYPE zresult_lt OCCURS 10.
    v_questionire = 'CALL CENTER'.
    APPEND v_questionire TO itab_questionire.
    v_questionire = 'METER INSTALLATION TEAM'.
    APPEND v_questionire TO itab_questionire.
    v_questionire = 'METER READING & BILLING'.
    APPEND v_questionire TO itab_questionire.
    v_questionire = 'NO SUPPLY'.
    APPEND v_questionire TO itab_questionire.
    v_questionire = 'CASH COLLECTION CENTER'.
    APPEND v_questionire TO itab_questionire.
    v_questionire = 'STREET LIGHT'.
    APPEND v_questionire TO itab_questionire.
    v_questionire = 'CONSUMER CARE CENTER'.
    APPEND v_questionire TO itab_questionire.
    v_questionire = 'WEBSITE'.
    APPEND v_questionire TO itab_questionire.
    DATA : counter TYPE i,
          high LIKE sy-datum,
           low LIKE sy-datum.
    CONCATENATE
    l_s_select-high+6(4)
    l_s_select-high+3(2)
    l_s_select-high+0(2)
    INTO
    high.
    CONCATENATE
    l_s_select-low+6(4)
    l_s_select-low+3(2)
    l_s_select-low+0(2)
    INTO
    low.
    BREAK-POINT.
   do i_maxsize times.
    CALL FUNCTION 'ZCRM_SURVEY_REPORTING'
      EXPORTING
        e_date_frm    = low
        e_date_to     = high
        e_questionire = itab_questionire
      CHANGING
        it_result     = e_tt_data_get.
    IF sy-subrc IS INITIAL.
      e_t_data[] = e_tt_data_get[].
      APPEND e_t_data.
    ELSE.
      EXIT.
    ENDIF.
     sd_no_more_data = 'X'.
ENDIF.              "Initialization mode or data extraction ?
ENDFUNCTION.
lk

FUNCTION MODULE CREATION FOR GENERIC DATA SOURCE

Hi BI gurus,
I am creating function module for generic datasource. For that I followed below mentioned steps
Steps
1.     Created s structure with the fields that needed.
2. Created FM by copying the standard Function module
" RSAX_BIW_GET_DATA_SIMPLE " and Give a New name starting With
Y or Z .
3. IN SE37 ->Your Function module name -> Change, In table tab given structure
name by deleting the associated type given in E_T_DATA .
And inserted the required code given below
      PROGRAM 'ZHU_BALANCE'.
*& Report ZHU_BALANCE
TABLES: VEKP, VEPO.
DATA: BEGIN OF T_DISPLAY,
      DATE   LIKE SY-DATUM,
      EXIDV LIKE VEKP-EXIDV,
      LGORT LIKE VEPO-LGORT,
      WERKS LIKE VEKP-WERKS,
      END OF T_DISPLAY.
DATA: ITAB_DISPLAY LIKE TABLE OF T_DISPLAY.
DATA: WA_ITAB_DISPLAY LIKE LINE OF ITAB_DISPLAY.
SELECT VEKPEXIDV VEPOLGORT VEPO~WERKS
       INTO CORRESPONDING FIELDS OF TABLE ITAB_DISPLAY
       FROM VEKP AS VEKP INNER JOIN VEPO AS VEPO
         ON VEKPVENUM = VEPOVENUM
         AND VEKPWERKS = VEPOWERKS
       WHERE VEKP~VSTEL = SPACE
         AND VEKP~VEGR1 = '401'
         AND VEKP~VPOBJ = '12'
         AND VEKP~STATUS = '0020'
         AND VEPO~VEPOS = '000001'.
LOOP AT ITAB_DISPLAY INTO WA_ITAB_DISPLAY.
WA_ITAB_DISPLAY-DATE = SY-DATUM.
MODIFY ITAB_DISPLAY FROM WA_ITAB_DISPLAY TRANSPORTING DATE.
ENDLOOP.
WRITE:/ 'DATE', 20 'EXIDV', 40 'LGORT', 60 'WERKS'.
ULINE.
LOOP AT ITAB_DISPLAY INTO WA_ITAB_DISPLAY.
WRITE:/ WA_ITAB_DISPLAY-DATE, 20 WA_ITAB_DISPLAY-EXIDV , 40 WA_ITAB_DISPLAY-LGORT, 60 WA_ITAB_DISPLAY-WERKS.
ENDLOOP.
While checking the function module its populating the syntax error as
THE TYPE SRSC_S_IF_SIMPLE IS UNKOWN. (Though this is commented in program)
So pls suggest
Regards,
praful

hi indira,
thanx for ur reply we have created the funcion module successfuly it is also showing the output correct. But when we put that function module in the generic data source and try to extract data in RSA3 it shows the correct output of function module but with the msg ' 0 entries found in customer enhancement' and therfore zero records in the display list.
is there any correction or steps to be followed in data extraction
pls suggest
regards,
praful

FUNCTIONAL MODULE AS A GENERIC EXTRACTOR

Hi,
Im looking to extract fields in from the following tables and want to create a functional module as a generic extractor for that:
BSEG
BKPF
COEP
MBEW
EINA
Could some one tell me how I can create a FUNCTIONAL MODULE AS A GENERIC EXTRACTOR for this or send me a documet at mysapsource at gmail com
Thanks

Hi,
Please find the steps to create FM:
Step 1.
GO to transaction SE80.In the drop box list select function group enter your Z Function group name.Press enter it will ask for creating the function group.Create your function group.
OR
In SE37 transaction,in the menu bar Goto - > Function Group - > Create Group.Your Function Group will be created.
Step 2.
Go to transaction SE37.Enter your Z Function module name,your recently created function group name and the description.Press Enter.Now your FM is created.
Step 3.
Enter Export,Import parameters.In the source code tab write the code what you want to write.If any exception write in the exception tab.
Method 2:
First u have to create Function Group.
1.se37->Goto->Function Group--->Create.
2.Create FM.
3.maintain import /export parameters and tables , exceptions.
4.based on the ur requirement u have to bulid ur logic in Source Code by using there Import parameters and u can pass the results by using Export or table.
5.u can raise error by using exception.
Create Function Module:
http://help.sap.com/saphelp_nw04s/helpdata/en/9f/db98fc35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/26/64f623fa8911d386e70000e82011b8/frameset.htm
Creating Function Modules.
Create Generic Datasource using Function Module:
Generick Extarction using Function Module.
Hope this helps u...
Regards,
KK.
Edited by: koundinya karanam on May 2, 2008 7:29 AM

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

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

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

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 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

Is there any function module getting the cpu type?

Is there any function module getting the cpu type?

I guess the database server...
I would like to get the SAP system cpu type as done in transaction st06 under system information.
Thanks.

How can I call the function module of the ECC when I save the campaign?

HI Experts!
I want to call function module of the ECC when I click the save button in the campaign view,A badi or userexit is needed,but I don't find, can you tell me which badi or userexit is used to implement?

Thanks a lot.
I have tried,but it can't do.
who can tell me which badi and detailed implementation step?
waiting on line.

How to find which function module write the relevant idoctype?

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

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

Counter logic in Function module of the generic extraction

Similar Messages

Maybe you are looking for