Function group memory with RFC calls

We have a system where a web front-end interacts with our 4.6C system through RFC calls.
I am having a number of problems where variables declared in a function group are not being cleared out between separate RFC calls to functions in the same group.
I would not have expected separate RFC calls from an external system to use the same memory area.
I have seen this happen at other sites too, but have never found an explanation for it.
Has anyone else experienced this problem and if so can you give me more information about why it happens?
Thanks for you help,
Denis.

This does make sense as global data within a function group is accessable by all function modules of the group.  Normally, in the ABAP system, you call multiple function modules of the same group, and they all share the data.  If you are calling from outside the system, I would expect a different behavior if you are connecting one by one.  But if you are using a pooled connection, this may be the issue.  Not sure though.  It seems that the session on r/3 has not ended and you are accessing the same when calling the second function module.  Is there any function module of the group that looks like it is a "refresher".  In some groups, there is a function module that will refresh the global data. 
http://help.sap.com/saphelp_46c/helpdata/en/9f/db992335c111d1829f0000e829fbfe/frameset.htm
Regards,
Rich Heilman

Similar Messages

  • Problem with RFC-Call within BPM

    Hello Experts,
    I am developing a scenario in which I call an rfc-function-module for saving information from an incoming xml which will be transmitted as Idoc to another SAP System.
    The Idoc transmission is doing properly. But the RFC-Call I try to do always ends with a red flag. Error-Message: message has error status on outbd. side at the Process-Engine.
    Can someone help solving that problem?
    Thanks in advance.
    Regards, Alexander

    Hi Rajhans,
    1) The user mentioned in the RFC communication channel is having the authorization.
    Yes, he have the authorizations.
    2) Go to Communication channel monitoring and check what error you are getting for the communication channel is showing.
    There is an error about the FileSenderChannel. Error: java.lang.NullPointerException.
    3) Check whether the RFC created at abap stack is remote enabled or not.
    The function module is remote enabled.

  • Custom Metadata Extension with RFC call

    Hi all,
    I am trying to create a custom metadata extension that pulls data from ECC via an RFC call and returns values as a IMetaValueList in the getAllowedValues method.
    Does anybody have any experience?
    Thx
    Ismail

    Hello Sanjeev,
    - I Kept External break point in SRM where we are calling RFC Call for ECC, I am able to debug untill the RFC call,
    - But, on RFC Call ( CALL FUNCTION ZABC destination <Destination>), when I press F5 it is not going inside the function module.
    - I am getting Export parameter values, means ctrl is going to ECC, but not able to debugg our BE system -ECC.
    Pls suggest. Thanks for your quick reply.
    Regards,
    Mohan Vamsi

  • Problem with RFC call between different clients. Plesae help!

    Hi Experts,
           I have a RFC enabled function module in one SAP instance 'A' where the client is 130. I am trying to call this function module from another SAP systen 'N' where client is 220. RFC destination has been set in 'N' system.
    The RFC functin module pulls data fromm a custom table. For a given input it is puuling data in 'A' system.
    But when I call it from 'N' system with the same input it is not pulling the data.
    I feel the problem is with teh different clients.
    please help me how to resolve this.
    Is there any setting in RFC destination?
    Thanks
    Gopal

    Hi gopalkrishna,
    1. Is there any setting in RFC destination
    Ofcourse there is.
    2. The tcode is sm59.
    3. Where u have maintained in system 'N',
       we have to specify
       a) Server 'A'
    <b>   b) Client Number 130</b> 
    4. So while calling from N(220),
       it will connect A(130)
       and fetch data from A(130) only.
    regards,
    amit m.

  • Facing a problem with RFC Call receiver error while importing the table sap sandbox

    Hi All,
    I am trying to import a table from sap sand box . while importing it is showing below error..
    RFC CallReceive error <Function DDIF_FIELDINFO_GET: RFC_ABAP_EXCEPTION-(Exception_Key: NOT_FOUND, No active nametab exists for /BIC/OHZ_ISP_SCX)[SAP NWRFC 720][SAP Partner 731 ][SCX][ics106046124][APOBODS][4103]>.
    Please suggest me how can i overcome this problem ??

    Hi Kishore,
    Can you quickly check with your SAP Basis Team whether they have installed necessary  functions related to BODS on the SAP Application server.
    Please check Supplement for SAP Guide
    Regards
    Arun Sasi

  • Empty tables with RFC call

    Good day,
    we have a delphi application using wdtfuncs.ocx to connect to SAP via RFC. Since we updated the GUI from 6.2 to 6.4 we have the strange problem, that in some cases select statements returning 0 hits (they should return at least 1 hit).
    After downgrading the wdtfuncs.ocx to version 6.2, everything seems to work fine.
    Maybe someone has a good idea?!
    Any help appreciated.
    regards,
    Andreas Hähre

    Thank you for trying to help me Kathirvel!
    But unfortunately I have not solved my problem.
    Let me be sure I did this right: I set OBJECTID=PA and SUBTYPE=0000 ?
    Well, I have tried diffrent combinations ...
    Are there a connection between subtype and infotype?
    (I did try 0006 as well ...)
    The problem with wdtfuncs.ocx are also described in this thread:
    I tried to swap the files wdtfuncs.ocx and wdtaocx.ocx from version 6.4 til 6.2, but it didn't help.
    The same problem as I'm struggeling with appears in this thread:
    The SAP Note 310190 I mentioned earlier are from 2002, and have Service Packages for version 4.5B to 4.6C. We are running SAP ERP 2004 PS, I think this is version 5.0. I did belive these Service Package were too old for our system, but am I wrong? Should I try to install them?
    Well, this seems to be a hard nut to crack! ...
    Kindly regards
    Arnstein Ørjavik

  • RFC hangs with a call to function module SSFC_PARSE_CERTIFICATE

    Hello ,
    We are working on BI 7.0  SP9 .
    When we try to test the RFC connection from the WAS Abap to the portal ( WAS JAVA ) using  SM59  , the test is hanging but we can read in the bottom of the screen 'Connexion bcv51sf2... OK' !!!
    The test connection works sometimes .
    But when it’s not working  , with the debug mode , I can see that the program SAPLSSFG/LSSFGU19 is hanging in the function module  SSF_GET_PARAMETER with a call to the function SSFC_PARSE_CERTIFICATE
          CALL FUNCTION 'SSFC_PARSE_CERTIFICATE'
            EXPORTING
              CERTIFICATE               = PABCERT
            IMPORTING
              SUBJECT                   = STR_PROFILEID
            EXCEPTIONS
              SSF_KRN_ERROR             = 1
              SSF_KRN_NOMEMORY          = 2
              SSF_KRN_NOSSFLIB          = 3
              SSF_KRN_INVALID_PAR       = 4
              OTHERS                    = 5.
             ENDIF.
           ENDIF.
         ENDFUNCTION.
    The variable STR_PROFILEID has the value of the field ID of the table SSF_PSE_H
    STR_PROFILEID =’CN=QWO, OU=XXXXX, O=YYYY, C=FR’
    Due to this error , we can’t transport BI Web templates  because at the end of the import in the method execution of the transport there is a call to the portal with the RFC. And the transport is hanging …
    Thanks in advance for you help .
    Happy new year.  Milan.

    Hi Frank ,
    See below the result of the test :
    Test for function group      SSFG
    Function module              SSF_GET_PARAMETER
    Export parameters
    Value
    APPFOUND
    <SYST>
    SSFTOOLKIT
    SAPSECULIB
    STR_FORMAT
    PKCS7
    STR_PAB
    /usr/sap/QWO/DVEBMGS01/sec/SAPSYS.pse
    STR_PAB_PASSWORD
    STR_PROFILEID
    CN=QWO, OU=XXXX, O=YYYY, C=FR
    STR_PROFILE
    /usr/sap/QWO/DVEBMGS01/sec/SAPSYS.pse
    STR_PROFILEPW
    STR_HASHALG
    SHA1
    STR_ENCRALG
    DES-CBC
    B_INCCERTS
    X
    B_DETACHED
    B_DISTRIB
    X
    But my problem now , it's that 1 of the 2 RFC is working fine and the other one after 1 good rfc test , is hanging now at the end of the function 'CONVERSION_EXIT_ISOLA_OUTPUT'  line 14 !!!
    See below the ABAP stack just before the hanging .
    1     FUNCTION CONVERSION_EXIT_ISOLA_OUTPUT.
    2     *"----
    3     ""Lokale Schnittstelle:
    4     *"       IMPORTING
    5     *"             VALUE(INPUT)
    6     *"       EXPORTING
    7     *"             VALUE(OUTPUT)
    8     *"----
    9       OUTPUT = SAVE_INPUT(1) = INPUT.
    10       CHECK SAVE_INPUT(1) NA ' *'.
    11       SELECT SINGLE * FROM T002 WHERE SPRAS = INPUT.
    12       CHECK SY-SUBRC = 0.
    13       OUTPUT = T002-LAISO.
    14     ENDFUNCTION.
    Stack Dep     Event type     Event     Program     Include     Line
    10     FUNCTION     CONVERSION_EXIT_ISOLA_OUTPUT     SAPLLANG     LLANGU04     14
    9     FORM     CONVERSION_EXIT     SAPCNVE     SAPCNVE     107
    8     EVENT     SYSTEM-EXIT     SAPLDSYA     <SYSINI>     20
    7     FUNCTION     DOKU_OBJECT_EXIST     SAPLDSYA     LDSYAU09     43
    6     FORM     FILL_EXCL_TAB     RSDBRUNT     RSDBRUNT     5.664
    5     FORM     %_INIT_PBO_LAST     RSDBRUNT     RSDBRUNT     4.061
    4     FORM     INIT_PBO     RSDBRUNT     RSDBRUNT     3.666
    3     FORM     %_INIT_PBO_NEW     RSRFCPIN     RSRFCPIN     496
    2     MODULE (PBO)     %_INIT_PBO     RSRFCPIN     RSRFCPIN     496
    1     EVENT     SYSTEM-EXIT     RSRFCPIN     <SYSINI>     20
    As i said in the first post , the RFC test is hanging sometimes but now it seems that it's not  hanging everytime at the same line of the abap code , if i can trust the debugger !
    ...and after another RFC test , now all the RFC to the portal are working ...
    It seems that when it's hanging , it's at the end of the functions ( SYSTEM_CALLSTACK
    or CONVERSION_EXIT_ISOLA_OUTPUT or SSF_GET_PARAMETER ) .
    A memory or OS problem ?
    Best Regards.  Milan.

  • Call the subscreen from a function group

    hi experts.
    i have created a module program in which i need to call a subscreen. the sub screen is created in a function group .
    how can i call it.
    thanks
    <REMOVED BY MODERATOR>
    Edited by: Alvaro Tejada Galindo on Feb 7, 2008 11:45 AM

    deepu K,
    I always have the same problem in such cases.
    Your hints concerning se38 and deleting with /h are very helpful but
    it is diffucult to locate the right location of this problem. I have followed
    your instructions and I get this:
    PROCESS AFTER INPUT.                    
      CHAIN.                                
        MODULE EXIT.                        
        FIELD: RS38M-FUNC_EDIT,             
               RS38M-FUNC_HEAD,             
               RS38M-FUNC_DOCU,             
               RS38M-FUNC_TEXT,             
               RS38M-FUNC_SSET.             
          MODULE SET_XCODE_SE38.            
        FIELD RS38M-PROGRAMM:               
          MODULE PROGRAMM.                  
        MODULE FUNCTION_MENU.               
      ENDCHAIN.                             
      MODULE MNGR_PAI.                      
    Is generally any way to find out very quickly the affected loacation
    in such cases ?
    Regards
    sas

  • Call screen of a function group

    Hi experts,
    How can I call a screen of a function group from another function and then return to the place of call?
    I have my own function and I need to call the screen of a certain function group.

    Hi.
    If there is function module A, which calls screen N assigned to function group B,
    so to call screen N,
    you should call function module A within your function module.

  • Function group in tablenaintenance generator.

    hi experts,
           can anybody please tell me why we create a function group
          while creating a table maintenance generator?
    what is the utility of creating a function group.
    regards
    pankaj

    Function Groups
    Function groups are containers for function modules. You cannot execute a function group. When you call a function module, the system loads the whole of its function group into the internal session of the calling program (if it has not already been loaded). For further information, refer to Organization of External Procedure Calls.
    The following diagram shows the structure of a function group: The name of a function group, fgrpcan be up to 26 characters long. This is used by the system to create the components of the group (main program and corresponding include programs). When you create a function group or function module in the Function Builder , the main program and include programs are generated automatically.
    The main program SAPLfgrp contains nothing but the INCLUDE statements for the following include programs:
    &#65399; LfgrpTOP. This contains the FUNCTION-POOL statement (equivalent for a function group of the REPORT or PROGRAMstatement) and global data declarations for the entire function group.
    &#65399; LfgrpUXX. This contains further INCLUDEstatements for the include programs LfgrpU01, LfgrpU02,... These includes contain the actual function modules.
    &#65399; The include programs LfgrpF01, LfgrpF02,... can contain the coding of subroutines that can be called with internal subroutine calls from all function modules of the group.
    The creation of these INCLUDE programs is supported from the ABAP Workbench by forward navigation (for example creation of a subroutine include by double clicking on the name of a subroutine in a PERFORM statement within a function module).
    You cannot declare a COMMON PART in a function group. Function groups have their own table work areas (TABLES). Function groups encapsulate data. In this respect, they are a precursor of ABAP Objects (see From Function Groups to Objects ).
    All of the function modules in a function group can access the global data of the group. For this reason, you should place all function modules that use the same data in a single function group. For example, if you have a set of function modules that all use the same internal table, you could place them in a function group containing the table definition in its global data.
    Function groups, like executable programs and module pools, can contain screens (selection screens and lists) as components. User input is processed either in dialog modules or in the corresponding event blocks in the main program of the function group. There are special include programs in which you can write this code. In this way, you can use function groups to encapsulate single screens or screen sequences.
    In SAP, it is a function group - instead of function - that is loaded into active memory.
    Function ( or function module ) is the one that you call from the program to do things.
    A function group contains functionally related function modules, global variables and procedures .
    To display / edit function module you use SE37,
    To display / edit function group you use SE80 .
    Reward if found helpful,
    regards
    palak

  • F4 help for Function Group

    Hi,
    We are creating an application in which we require the user to enter Function Group Name, the related type bound to mapped context attribute is AREA.
    We have searched in the system but couldn't find any Function Module which returns list of all function groups.
    can anyone help here.
    Regards
    Manas Dua

    Hi,
    Thnks, its solved.
    Created an OVS search help with 2 input params - Package Name and Function Group.
    using function module REPOSITORY_INFO_SYSTEM_SET to fech the function group name.
    and before calling this storing the package name in Memory Object by usign the statement
    ds_rxxadir-sign = 'I'.
            ds_rxxadir-option = 'EQ'.
            ds_rxxadir-low = <ls_query_params>-package_name.
            APPEND ds_rxxadir TO dt_rxxadir.
            EXPORT rxxadir FROM dt_rxxadir  TO MEMORY ID '%RANGES_DEVCLASS'.
    Regards
    Manas Dua

  • How to add function group to the  authorization object S_RFC ?

    Hi All,
    Can you  please tell you how to add the function group FG_DIAGLS_DATA_ENRICHMENT  to the authorization object
    S_RFC?
    In solman_setup under basis configuration when I execute the step "SetupDPC/DCC Web Service URL" its getting failed because of the
    following error which i found it in the agent log
    "java.rmi.RemoteException:RfcExecutionException; nested exception is:
    com.sap.sup.admin.abap.rfc.exception.RfcExecutionException: An
    exceptionoccured during the execution of the function
    'FM_DIAGLS_PUSH_PHYSICAL_HOST': RFC_NO_AUTHORITY >
    com.sap.sup.admin.abap.rfc.exception.RfcExecutionException:An exception
    occured during the execution of the function
    'FM_DIAGLS_PUSH_PHYSICAL_HOST': RFC_NO_AUTHORITY >
    com.sap.mw.jco.JCO$Exception:No RFC authorization for function module
    FM_DIAGLS_PUSH_PHYSICAL_HOST. <Mid"
    Thanks,
    Satheesh E

    Hi,
    Please follow below steps:
    1) Go to SE01
    2) Click on create New workbench request and give desc once popup appears, Click Ok
    3) Now open the trasport in edit mode
    4) Add
    Program ID - R3TR
    Object Type - FUGR
    Object name - Name of the Function group
    >note that if you tranport Function group all the latest Function modules in function group along
    >with screens will be included in the transport.
    Regards
    Shital
    Formatted by: Vijay Babu Dudla on Apr 25, 2009 5:08 AM

  • Function Groups and Function Modules

    Hi,
    Can anyone give me the detail steps for creating Function Group and then from that function group creation of function module with example?
    Regards,
    Chandru

    Hi,
    Function Group creation -
           A function group is a program that contains function modules. With each R/3 system, SAP supplies more than 5,000 pre-existing function groups.
         In total, they contain more than 30,000 function modules. If the functionality you require is not already covered by these SAP-supplied function modules, you can also create your own function groups and function modules.
          We can put all the relevant function modules under one function group and all the global variables can be declared in this FG.
    FG Creation:
    1)     Function group can be created in SE80. There choose the 'Function Group' from the list of objects.
    2)    Then give a name for ur function group (starts with Y or Z) and press ENTER.
    3)   The click 'YES' in the create object dialog box and give a short desc. for this FG and save.
    Function Module:
                 A function module is the last of the four main ABAP/4 modularization units. It is very similar to an external subroutine in these ways:
    Both exist within an external program.
    Both enable parameters to be passed and returned.
    Parameters can be passed by value, by value and result, or by reference.
    The major differences between function modules and external subroutines are the following:
    Function modules have a special screen used for defining parameters-parameters are not defined via ABAP/4 statements.
    tables work areas are not shared between the function module and the calling program.
    Different syntax is used to call a function module than to call a subroutine.
    Leaving a function module is accomplished via the raise statement instead of check, exit, or stop.
    A function module name has a practical minimum length of three characters and a maximum length of 30 characters. Customer function modules must begin with Y_ or Z_. The name of each function module is unique within the entire R/3 system.
    Defining Data within a Function Module
    Data definitions within function modules are similar to those of subroutines.
    Within a function module, use the data statement to define local variables that are reinitialized each time the function module is called. Use the statics statement to define local variables that are allocated the first time the function module is called. The value of a static variable is remembered between calls.
    Define parameters within the function module interface to create local definitions of variables that are passed into the function module and returned from it (see the next section).
    You cannot use the local statement within a function module. Instead, globalized interface parameters serve the same purpose. See the following section on defining global data to learn about local and global interface parameters.
    Defining the Function Module Interface
    To pass parameters to a function module, you must define a function module interface. The function module interface is the description of the parameters that are passed to and received from the function module. It is also simply known as the interface. In the remainder of this chapter, I will refer to the function module interface simply as the interface.
    To define parameters, you must go to one of two parameter definition screens:
    1) Import/Export Parameter Interface
    2) Table Parameters/Exceptions Interface
    Then in the FM interface screen, give the following
    1) Import parameters
    2) Export parameters
    3) Changing parameters
    Then give
    1) Define internal table parameters
    2) Document exceptions
    You enter the name of the parameter in the first column and the attributes of the parameter in the remaining columns. Enter one parameter per row.
    Import parameters are variables or field strings that contain values passed into the function module from the calling program. These values originate outside of the function module and they are imported into it.
    Export parameters are variables or field strings that contain values returned from the function module. These values originate within the function module and they are exported out of it.
    Changing parameters are variables or field strings that contain values that are passed into the function module, changed by the code within the function module, and then returned. These values originate outside the function module. They are passed into it, changed, and passed back.
    Table parameters are internal tables that are passed to the function module, changed within it, and returned. The internal tables must be defined in the calling program.
    An exception is a name for an error that occurs within a function module. Exceptions are described in detail in the following section.
    Syntax for the call function Statement
    The following is the syntax for the call function statement.
    call function 'F'
        [exporting   p1 = v1 ... ]
        [importing   p2 = v2 ... ]
        [changing    p3 = v3 ... ]
        [tables      p4 = it ... ]
        [exceptions  x1 = n [others = n]].
    where:
    F is the function module name.
    p1 through p4 are parameter names defined in the function module interface.
    v1 through v3 are variable or field string names defined within the calling program.
    it is an internal table defined within the calling program.
    n is any integer literal; n cannot be a variable.
    x1 is an exception name raised within the function module.
    The following points apply:
    All additions are optional.
    call function is a single statement. Do not place periods or commas after parameters or exception names.
    The function module name must be coded in uppercase. If it is coded in lowercase, the function will not be found and a short dump will result.
    Use the call function statement to transfer control to a function module and specify parameters. Figure 19.9 illustrates how parameters are passed to and received from the function module.
    sample FM
    CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
      I_INTERFACE_CHECK                 = ' '
      I_BYPASSING_BUFFER                = ' '
      I_BUFFER_ACTIVE                   = ' '
      I_CALLBACK_PROGRAM                = ' '
      I_CALLBACK_PF_STATUS_SET          = ' '
      I_CALLBACK_USER_COMMAND           = ' '
      I_CALLBACK_TOP_OF_PAGE            = ' '
      I_CALLBACK_HTML_TOP_OF_PAGE       = ' '
      I_CALLBACK_HTML_END_OF_LIST       = ' '
      I_STRUCTURE_NAME                  =
      I_BACKGROUND_ID                   = ' '
      I_GRID_TITLE                      =
      I_GRID_SETTINGS                   =
      IS_LAYOUT                         =
      IT_FIELDCAT                       =
      IT_EXCLUDING                      =
      IT_SPECIAL_GROUPS                 =
      IT_SORT                           =
      IT_FILTER                         =
      IS_SEL_HIDE                       =
      I_DEFAULT                         = 'X'
      I_SAVE                            = ' '
      IS_VARIANT                        =
      IT_EVENTS                         =
      IT_EVENT_EXIT                     =
      IS_PRINT                          =
      IS_REPREP_ID                      =
      I_SCREEN_START_COLUMN             = 0
      I_SCREEN_START_LINE               = 0
      I_SCREEN_END_COLUMN               = 0
      I_SCREEN_END_LINE                 = 0
      I_HTML_HEIGHT_TOP                 = 0
      I_HTML_HEIGHT_END                 = 0
      IT_ALV_GRAPHICS                   =
      IT_HYPERLINK                      =
      IT_ADD_FIELDCAT                   =
      IT_EXCEPT_QINFO                   =
      IR_SALV_FULLSCREEN_ADAPTER        =
    IMPORTING
      E_EXIT_CAUSED_BY_CALLER           =
      ES_EXIT_CAUSED_BY_USER            =
      TABLES
        t_outtab                          =
    EXCEPTIONS
      PROGRAM_ERROR                     = 1
      OTHERS                            = 2
    IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    Example
    1  report ztx1905.
    2  parameters: op1 type i default 2,   "operand 1
    3              op2 type i default 3.   "operand 2
    4  data rslt type p decimals 2.        "result
    5
    6  call function 'Z_TX_DIV'
    7       exporting
    8            p1      = op1
    9            p2      = op2
    10      importing
    11           p3      = rslt.
    12
    13 write: / op1, '/', op2, '=', rslt.
    Regards,
    Shanthi.P
    Reward points if useful ****
    Edited by: shanthi ps on Jan 26, 2008 12:03 PM

  • Function group / Function modules approvals

    Hi,
    We have couple of function modules related to RFC / BAPI in QA we need to give approvals before we move them to production.
    What precautions do we need to take before approving?
    How to segregate Function groups / Function modules?
    Thanks,
    Ram

    Well you should test function groups and function module coding as per your normal procedures. They are widely used.
    Whether they are accessible depends on your roles, right?
    Which release are you on?
    Prior release 7.01 you can only control at function group level with object S_RFC.
    Subsequently you can use RFC_TYPE 'FUNC' to control at module name level if FUGR fails.
    Luckily, this check is central and to my knowledge only one developer ever hardcoded it for list outputs, so you should be okay to convert for manual authorizations.
    For standard ones from the menu, you will need to deactivate S_RFC (there is not option to un-merge, unfortunately..........). Easiest is to get the names from the menu and paste them into the manual authorization, or use a Su24 "dummy" for the role or scenario.
    Dummy's are usefull workarounds and protect you against upgrades as well... (when SAP adds a load of stuff because GRC needs it, and then toasts your roles, sets active auths to inactive and adds new ones which are merged automatically...)
    Cheers,
    Julius

  • Component group type assignment in call components in JIS

    Hi All
    How Component group type assignment is done  in call components ?
    Edited by: mayuresh  bhurke on Jan 20, 2012 8:25 PM

    Hi Mayuresh bhurke,
    How the system will does the job:
    The system carries out this function automatically, each time a JIT call is received. In this way it assigns each call component transmitted to a components group type. The components group type then takes on the internal control of the call components.
    With sequenced JIT calls for assemblies, the system assigns several call components to the same components group type. With the other call types the call components and the components group type form a logical unit and the system therefore assigns a different components group type to each call component.
    In the components group determination the system compares whether the characteristics of the call components match a components group type. As soon as it can assign a call component, it continues with the next one. In the profile for the components group determination you can define with which priority the system should consider the various characteristics. The system determines the relevant characteristics of the call components as follows:
    JIT customer
    The JIT customer is made up of the sold-to party and the partner description and can therefore be taken from the IDoc.
    Unloading point and assembly location
    The unloading point and, if necessary the assembly location, are also transmitted with the JIT call. The system can also take these characteristics of the call components from the IDoc.
    Components group material
    The JIT customer generally transmits the components group material with a call. You have several options for defining the components group material of the call component before the components group determination.
    You can realize an individual components group material determination using a customer exit. This is particularly recommended for sequenced JIT calls for assemblies, due to the large number of variants.
    If you use the process for discrete materials, you can transfer the material of the call components as a components group material.
    If you use the process for discrete materials and exactly one components group material can be assigned to a call component, you can transfer the configurable material of the call component as a components group material. To do this you must have entered the configurable material in the material master of the call component in the tab page Basic data 2 in the field Cross plant conf.mat.
    Production version
    You can also assign the production version using a customer exit. The production version allows you to assign two otherwise equal call components to different components group types, to produce them on different production lines, for example.
    There are also call types:
    please follow the below link:
    http://help.sap.com/saphelp_di46c2/helpdata/EN/7a/ad7d2b1e4c11d3b69c0000e82d81c3/content.htm
    I hope you can find the need full information.
    Regards,
    Madhu.G

Maybe you are looking for