RFC func module name changing on transport

Hi
We are using web service to push data into BI from XI. we are following the guide "How to Integrate XI and BI in SAP NetWeaver 2004s".
Accordingly, we have used the RFC FM name generated while activation of WebService DataSources to create the proxies. The XI system is using the same RFC names to connect to BI.
Now, when we are transporting the DataSources from Dev to QA environment, the RFC functional module names are getting changed in the DataSources. Hence our entire development becomes ineffective.
Any suggestion on how to prevent the FM names from changing during transport?
Thanks a lot,
Sushmita

Hi Sushmita,
Did you know how to solve your issue? Because we have this problem same with you. If you know how to solve. Could you please to reply me.
Thanks a lot.
Park Saeiam

Similar Messages

  • How to trigger RFC Func Module from XI.

    Hi Everyone,
               I am trying to implement a scenario where in the data is passed from
    RFC (async) <--> (async) BPM (Sync)<--> (Sync) SOAP
    I trigger the initial RFC function module in the background by running a report in R/3 to send data async to BPM.
    But how do I trigger the receiving RFC (Async) in R/3 from XI to post the data sent by synchronous SOAP service.
    Regards,
    Ashish

    Hi,
    1. You can make the RFC as Sync so that you need to worry.
    2. In BPM 1st step will be receive that is RFC Async, 2dn step is Send to SOAP Sync and what you can do is...
    Get the SOAP response and have once more Send step in BPM and trigger that RFC you watnted to.
    Thanks,
    Prakash

  • Report painter object name change during transport

    We have a requirement to add 5 fields (In selection screen) to report painter reports ( Reports of CJE3 and GRR3 ).We created Z reports as a copy of standard reports, added required 5 fields by implementing SAP notes and other settings .We have also done implicit enhancements for all these reports to make change in the behavior of new fields .This is working fine in the development client but the problem is once we transport this to Quality system new reports get generated( With new name ) and implicit enhancement will be lost.
    For E.g.:
    In development client for CJE1/CJE2 report the program name will be "GPAVPSATWFP4NN0YRDBIQBHI8MQ"  (In this program we have done implicit enhancement )
    but when we transport it to other client new program "GP8O1UCNZTJYY5LTO8GN0UW2GQB" is generated in which implicit enhancements are not found.
    Rgds
    Sameer

    Hi,
    have you looked at export/ inport functionality (gr57/ gr58) or what mode of transport are you using?
    Regards
    Hein

  • Logical system Name Change Via Transport

    Hi All,
    Recently we made changes in parallel processing profile customizing table  (/SAPAPO/SDP_PAR) and created entries for Macro Jobs and CIF.
    For Application "CIF Delta Report", Logical system is mandatory and in Dev we gave the APO Dev Logical System Name (AD1XXX). Now when we moved the changes to Quality, expectation was that Logical system name for CIF Entry in the table would change to AQ1XXX - However, it still shows as AD1XXX there. Moreover AD1XXX entry is not a valid entry in Quality System and even when we see Drop Down values for that column (Press F4) - Only APO and ECC Quality systems names are appearing.
    Please suggest how can this logical system name be corrected. One option is running BDLS, but when this TR moves to Production there also we might end up in same scenario (Logical system as AD1XXX instead of AP1XXX) and running BDLS in Production wont be approved.
    Please suggest if there is any other option to handle this.
    Regards,
    Alok

    Hi Alok,
    we describe a solution in our
    SAP Rapid Deployment Solutions (RDS)
    Quick Link
                    Access SAP Rapid Deployment Solutions (RDS) directly via
                      http://service.sap.com/rds
    SAP Demand and Supply Network Planning rapid-deployment solution
    Quick Link
        Access this area directly via
    http://service.sap.com
    /rds-dpa
    In confgiguration guide
    Central Master Data Replication (SCO)
    you can read how it is done with
    Create Entries in Table
    TVARVC for Logical System Variable in Variants
    Frank

  • RFC Function module Error

    Dear Experts,
    I have written simple Remote Function module as like given below.
    Before that i did all required RFC settings in SM59 and tested from there.
    It is connecting from each other.
    REPORT  ZTEST_RFC                               .
    data: rfc_var1 type i VALUE '10',
          rfc_var2 type i VALUE '599',
          rfc_result type i.
    CALL FUNCTION 'Z_SUM'
      DESTINATION 'dev'
      EXPORTING
        VAR1                  = RFC_VAR1
        VAR2                  = RFC_VAR2
      IMPORTING
        RESULT                = RFC_RESULT
      EXCEPTIONS
        COMMUNICATION_FAILURE = 1
        OTHERS                = 2.
    I am getting sy-subrc eq 1.
    Please guide what could be wrong...do we need pass any parameters in FM.
    Thanks
    Cris

    Also To debug a RFC:
    You need to make sure that you are able to login in to the system containing the RFC using SM59 with your own login. Now place a break point just before the RFC Fm in your se38 and press F5. now it goes into the RFC .Now you need to place a break point at your RFC FM by specifying your RFC name.
    and hit F8 . It goes inside the RFC Func module code.
    Try it and let me know.
    Sri

  • Where to define remote function module name in RFC adapter

    R/2(IDOC) <->XI <-> R/3 (RFC)
    I can only define remote server information in RFC receiver adpater, but where to define the function module on remote server&#65311;

    Hi,
    the communication channel need the request in an specific xml format.
    Part of this format is the function modul name.
    when you use an imported rfc module you have automaticly the right xml format which the communication channel understand.
    the Communication channel need as root tag the function module name
    like:
    <ns0:Z_MY_FUNCTION xmlns:ns0="urn.sap-com:document:sap:rfc:functions">
    so it is with xslt mappings (for example) as well possible to call a rfc modules without importing it into your repository.
    regards,
    Robin

  • How to change the module name

    Hello All,
    I saved a report as XYZ.rdf. When I open this it opens with a module name as say ABC.
    Now is it possible to change the module name to DEF instead?
    (I have some closely numbered reports, I need to change one of them to avoid stepping over the names)
    Thanks,
    Chiru

    Hi Chiru,
    Right click on the module name and select the Property Inspector. Now you can change the property Name.
    Regards,
    Vincent

  • RFC function module always creating BPs with the same user name (RFC user )

    Hi All
    I posted the below question in a different area before. But thought it would be more suitable here.
    Moderators - Please let me know if am doing any mistake.
    Question:
    I have a RFC function module in CRM that creates Business Partners in ECC (XD01 tcode).
    I am using a dialog RFC destination configured in SM59 in CRM.
    But my RFC function module in CRM is always creating the Business Partners in ECC with the RFC user id (the user that we maintain for the RFC destination in SM59).
    This is a problem for the users because they are not able to track the actual person responsible for creating these Business Partners.
    Can somebody please let me know how to solve this problem?
    Thanks
    Raj

    Hi.
    You may use the trust relationship between CRM and R/3 and in SM59 instead of set a specific username, you set the flag "current user".
    With this flag, the system will access R/3 system with the user logged in CRM system. The Trust relationship must be created between CRM and R/3 in order to the system doesn't ask for a password to login in R/3.
    If you need more details please reply.
    Kind regards,
    Susana Messias

  • Collection problem with RFC function module WSDL.

    Hi.
    I have developed an RFC function module in a SAP system version 4.7 (WAS 620). This FM has 2 table parameters. I have no problem when I see the WSDL in the SAP Web Service Browser.
    Another team is trying to consume this RFC FM as a web service from a Java application but they say they can't see the table parameters as collections.
    Here is the WSDL of the FM, the table parameters are T_MOVIM and T_ERROR:
    <?xml version="1.0" encoding="UTF-8" ?>
    <definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:s0="urn:sap-com:document:sap:rfc:functions" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="urn:sap-com:document:sap:rfc:functions">
         <types>
              <xsd:schema targetNamespace="urn:sap-com:document:sap:rfc:functions">
                   <xsd:element name="ZMMFUSAPTK_0001">
                        <xsd:complexType>
                             <xsd:all>
                                  <xsd:element name="GENIDOC" minOccurs="0">
                                       <xsd:simpleType>
                                            <xsd:restriction base="xsd:string">
                                                 <xsd:maxLength value="1" />
                                            </xsd:restriction>
                                       </xsd:simpleType>
                                  </xsd:element>
                                  <xsd:element name="T_ERROR">
                                       <xsd:complexType>
                                            <xsd:sequence>
                                                 <xsd:element name="item" minOccurs="0" maxOccurs="unbounded" type="s0:ZMMTASAPTK_0012" />
                                            </xsd:sequence>
                                       </xsd:complexType>
                                  </xsd:element>
                                  <xsd:element name="T_MOVIM">
                                       <xsd:complexType>
                                            <xsd:sequence>
                                                 <xsd:element name="item" minOccurs="0" maxOccurs="unbounded" type="s0:ZMMTASAPTK_0011" />
                                            </xsd:sequence>
                                       </xsd:complexType>
                                  </xsd:element>
                             </xsd:all>
                        </xsd:complexType>
                   </xsd:element>
                   <xsd:element name="ZMMFUSAPTK_0001.Response">
                        <xsd:complexType>
                             <xsd:all>
                                  <xsd:element name="CODRET">
                                       <xsd:simpleType>
                                            <xsd:restriction base="xsd:string">
                                                 <xsd:maxLength value="1" />
                                            </xsd:restriction>
                                       </xsd:simpleType>
                                  </xsd:element>
                                  <xsd:element name="T_ERROR">
                                       <xsd:complexType>
                                            <xsd:sequence>
                                                 <xsd:element name="item" minOccurs="0" maxOccurs="unbounded" type="s0:ZMMTASAPTK_0012" />
                                            </xsd:sequence>
                                       </xsd:complexType>
                                  </xsd:element>
                                  <xsd:element name="T_MOVIM">
                                       <xsd:complexType>
                                            <xsd:sequence>
                                                 <xsd:element name="item" minOccurs="0" maxOccurs="unbounded" type="s0:ZMMTASAPTK_0011" />
                                            </xsd:sequence>
                                       </xsd:complexType>
                                  </xsd:element>
                             </xsd:all>
                        </xsd:complexType>
                   </xsd:element>
                   <xsd:complexType name="ZMMTASAPTK_0011">
                        <xsd:sequence>
                             <xsd:element name="REFERENCIA" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="10" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="FECHACONT" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="8" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="FECHADOC" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="8" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="CODMOV" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="2" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="NROPLAN" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="12" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="NROCOMP" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="10" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="CLASEMOV" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="3" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="CENTRO" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="4" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="ALMACEN" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="4" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="MATERIAL" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="5" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="LOTE" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="10" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="CANTIDAD" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="15" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="MOTIVOMOV" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="4" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="CENTROREC" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="4" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="ALMACENREC" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="4" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="CENTROCTO" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="10" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="ORDEN" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="12" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="TIPOSTK" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="1" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="NROPEDIDO" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="10" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="CODCISTERNA" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="50" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                        </xsd:sequence>
                   </xsd:complexType>
                   <xsd:complexType name="ZMMTASAPTK_0012">
                        <xsd:sequence>
                             <xsd:element name="REFERENCIA" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="10" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="CODERR" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="3" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="MSJERR" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="100" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                        </xsd:sequence>
                   </xsd:complexType>
              </xsd:schema>
         </types>
         <message name="ZMMFUSAPTK_0001Input">
              <part name="parameters" element="s0:ZMMFUSAPTK_0001" />
         </message>
         <message name="ZMMFUSAPTK_0001Output">
              <part name="parameters" element="s0:ZMMFUSAPTK_0001.Response" />
         </message>
         <portType name="ZMMFUSAPTK_0001PortType">
              <operation name="ZMMFUSAPTK_0001">
                   <input message="s0:ZMMFUSAPTK_0001Input" />
                   <output message="s0:ZMMFUSAPTK_0001Output" />
              </operation>
         </portType>
         <binding name="ZMMFUSAPTK_0001Binding" type="s0:ZMMFUSAPTK_0001PortType">
              <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
              <operation name="ZMMFUSAPTK_0001">
                   <soap:operation soapAction="http://www.sap.com/ZMMFUSAPTK_0001" />
                   <input>
                        <soap:body use="literal" />
                   </input>
                   <output>
                        <soap:body use="literal" />
                   </output>
              </operation>
         </binding>
         <service name="ZMMFUSAPTK_0001Service">
              <documentation>SAP Service ZMMFUSAPTK_0001 via SOAP</documentation>
              <port name="ZMMFUSAPTK_0001PortType" binding="s0:ZMMFUSAPTK_0001Binding">
                   <soap:address location="http://dbades00.bue.bemberg.com.ar:8002/sap/bc/soap/rfc" />
              </port>
         </service>
    </definitions>
    Should I change something in the definition of the parameters of the FM? or the problem is with the parsing process on the other system?
    Thanks in advance.
    Fabian.

    Welcome to SDN.
    I am not sure about this particular issue, but i have used WSDL from WAS6.20 system in MS Office infopath to consume webservice where we have had table parameters without any issue.
    may be try with office infopath to make sure that the problem is with the WSDL or with the java application.
    Regards
    Raja

  • RFC Function module is not working in program while Background

    Hi All,
    we have a one program in BI  system which is calling RFC function module. it is executing the program in foreground very well. Same program we have executed in background , it is not working at all. Thiis RFC function module exists in R/3 4.6c system.

    Hello Raju,
    Transactional call of a remote-capable function module specified in func using the RFC interface. You can use the addition DESTINATION to specify an individual destination in dest. If the destination has not been specified, the destination NONE is used implicitly. Character-type data objects are expected for func and dest.
    When the transactional call is made, the name of the called function, together with the destination and the actual parameters given in parameter list, are registered for the current SAP LUW in the database tables ARFCSSTATE and ARFCSDATA of the current SAP system under a unique transaction ID (abbreviated as TID, stored in a structure of type ARFCTID from the ABAP Dictionary, view using transaction SM58). Following this registration, the program making the call is continued by way of the statement CALL FUNCTION.
    When executing the COMMIT WORK statement, the function modules registered for the current SAP LUW are started in the sequence in which they were registered. The statement ROLLBACK WORKdeletes all previous registrations of the current SAP LUW.
    If the specified destination is not available for COMMIT WORK, an executable called RSARFCSE is started in the background. This attempts to start the functional modules registered for an SAP LUW in their destination, every 15 minutes up to a total of 30 times. You can make changes to these parameters using transaction SM59. If the destination does not become available within the given time, this is noted in the database table ARFCSDATA as a CPICERR entry. By default, this entry in database table ARFCSSTATE is deleted after 8 days.
    Thanks and Regards,
    SAP Shori

  • Debugging RFC function module from ECC to CRM

    Hi All,
    My requirement is to debug an RFC function module present in CRM(7.0) system from ECC(6.0) system. A report program in ECC will call CRM custom FM. I found many posts in SDN with the same issue and tried to implement suggestions provided there. But I couldn't succeed. The approach I followed is:
    I logged in to ECC report program and kept an external breakpoint just before the function module call.
    I logged in to CRM system, opened the function module and kept an external breakpoint there.
    In both the systems I provided the dialogue userid( id through which I log in to SAPGUI) in the system->settings->debugging option.
    In CRM I activated the external break point in  transaction SRDEBUG.
    Now when I execute the report program in ECC, control stops at the breakpoint. If I press F5 at the function call, control is not going to the external break point set in the CRM FM. I am getting output of FM directly.
    I tried with different settings like turning on the check box for IP matching and session breakpoint active immediate, switching to classic debugger etc. I also tried to provide the RFC user id instead of dialogue user but system throws exception saying only dialogue userids are allowed. I found that by inserting an infinite loop statement, control goes inside the RFC CRM FM but I prefer not to change the code.
    Please let me know if I missed anything.
    Thanks and Regards,
    Naren

    Hi,
    Debug RFC calls
    When an RFC function module is called it is usually not possible to debug the call, using the below techniques we can achieve the same. For this example we are calling an RFC enabled FM in ECC system from CRM system.
    Scenario 1: Calling a custom RFC FM
    STEP 1: Add an infinite loop in the remote custom Function Module (adding a u201CDO. ENDDO.u201D statement at the start of the FM would be enough).
    STEP 2: Execute your program in the CRM system. The execution stops at the RFC call, because of the infinite loop.
    STEP 3: Now login to the ECC system and go to transaction SM51 select the process which is executing the RFC and navigate to the menu: u201CProgram/Session->Program->Debuggingu201D this triggers the debugger session in a separate window.
    Scenario 2: Calling a Standard RFC FM
    When we are debugging a standard program we cannot add the infinite loop, hence we cannot go to SM51 and debug the work process. The RFC destination for the ECC system has a User specified, the RFC function module gets executed using this users credentials. Usually the basis team set up the RFC user as non Dialog user, this does not allow debugging. Contact your Basis team and get this changed to a dialog user enabling you to debug RFC function calls via the normal debugger.
    Note: User name configured in the RFC destination (transaction SM59) 
    Note: User type for the RFC User (transaction SU01D)
    Hope this will be helpful..

  • Error when call RFC Function module in R/3

    Dear All,
    We are trying to call RFC function module CBIF_GLM1_PROCESS_ORDER_READ (This is not a BAPI and also not released ) in R/3 from XI system.
    we are facing the error "Error while lookup Exception during processing the payload. Error when calling an adapter by using the communication channel CC_PPPI_MES_RFC_Rcvr (Party: , Service: WCD_320, Object ID: 16563889b449328eac76caa6a3bc592e) XI AF API call failed. Module exception: 'error while processing the request to rfc-client: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: failed to parse BAPI response due to: com.sap.aii.adapter.rfc.util.bapi.BapiException: Parameter with name RETURN not found.'. Cause Exception: 'com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: failed to parse BAPI response due to: com.sap.aii.adapter.rfc.util.bapi.BapiException: Parameter with name RETURN not found.'."
    This is the first time we are doing this configuration.
    Could you please let me know what woulbe the reason.

    read the original message
    We are trying to call RFC function module CBIF_GLM1_PROCESS_ORDER_READ (This is not a BAPI and also not released ) in R/3 from XI system.
    I am talking about the above Receiver RFC channel which you guys are using to call R/3 from XI. That where you need to change the commit parameter

  • Facing Problem with RFC Function Module

    Hi,
    I have created an RFC function module to get some data in table format.
    I have run the RFC in original system: It is giving the data.
    However, when I run this in target system, It is not giving any values.
    Could you please let me know, why it happens? I am not sure where I missed out.
    Thanks,
    Sandeep

    HI,
    i hope you are calling the RFC function module in the target system like this
    CALL FUNCTION <FUNC NAME> DESTINATION <DESTINATION NAME> . The destination should be logical system name of the source Logical system .
    Regards,
    Nagaraj

  • Functional module name of smartform

    Hi,
    I have created a smartform and generated it.
    what will be the name of the Functional module?
    how to use it in abap
    Thanks,
    Mounika.

    hi,
    Use
    You trigger form printing by calling as few as two function modules. The first module uses the name of the form to determine the name of the generated function module. Then you call this module.
    The name of the generated function module is unique only within one system. Therefore, you must always call that function module first that uses the form name to determine the current name of the generated module.
    Prerequisites
    You defined the form interface in your form and activated the form.
    Procedure
    In the Form Builder call the function Environment ® Name of the function module and use STRG-Y and STRG-C to copy its name.
    In the application program define a variable of type RS38L_FNAM for the name of the generated function module:
    data fm_name type RS38L_FNAM .
    You can call the Smart Form in other parts of the application program as well. However, in that case you must make sure that the system can access the data to be passed from that location. We recommend to encapsulate the data retrieval in a function module as well.
    If desired, you can call the function module SSF_FIELD_LIST . It returns a list of the form parameters actually used in the form. You can use this information to limit data selection, if necessary.
    Call function module SSF_FUNCTION_MODULE_NAME . It returns the name of the generated function module:
    CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
      EXPORTING
        FORMNAME             = '
    ENDIF.
    If the form is not active, SSF_FUNCTION_MODULE_NAME triggers the exception NO_FORM . There are two cases in which the function module generates an active version by itself:
    After a transport into another system
    After you changed the form interface of a previously activated form
    Call the generated function module. To do this, use the Insert Statement function for CALL FUNCTION in the ABAP Editor and use the name you copied in step 1 (to avoid having to copy all interface parameters manually). Then replace the function module name with the variable fm_name defined in step 2.
    CALL FUNCTION fm_name
      EXPORTING
      ARCHIVE_INDEX =
      ARCHIVE_PARAMETERS =
      CONTROL_PARAMETERS =
      MAIL_APPL_OBJ =
      MAIL_RECIPIENT =
      MAIL_SENDER =
      OUTPUT_OPTIONS =
      USER_SETTINGS = 'X'
        G_CARRID =
    IMPORTING
      DOCUMENT_OUTPUT_INFO =
      JOB_OUTPUT_INFO =
      JOB_OUTPUT_OPTIONS =
      TABLES
        GT_SBOOK =
    ENDIF.
    In this example, three variables and an internal table are passed. The parameters G_CARRID , G_CONNID , G_FLDATA , and GT_SBOOK have been defined before in the form interface.
    In the interface, pass all data you want to transfer to the form.
    Result
    The generated function module processes the form logic defined in the Smart Form. Its output is sent to spool processing.
    As long as you do not change the form interface, you can make any changes to the form. When you activate it again, the system generates the current version of the form as soon as you call the function module. Only if you change the form interface, you must adapt the interface in the application program.
    plzz reward if this information is usefull to u....
    plzz dont forget to reward

  • Windows Forms Application Crashes Out with "Faulting module name: clr.dll"

    OS: Windows 7
    Framework: 4.5
    Windows Form Application crashes while invoking printer settings method "printersettings.sethdevmode()"
    Application: DHSDEVASystem.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.AccessViolationException
    Stack:
       at System.Runtime.InteropServices.Marshal.CopyToManaged(IntPtr, System.Object, Int32, Int32)
       at System.Runtime.InteropServices.Marshal.Copy(IntPtr, Byte[], Int32, Int32)
       at System.Drawing.Printing.PrinterSettings.SetHdevmode(IntPtr)
       at DHSPresentationLayer.Logic.PrinterAPI.OpenPrinterPropertiesDialog(System.Drawing.Printing.PrinterSettings, System.Windows.Forms.Form)
       at DHSPresentationLayer.Logic.PrinterAPI.SendFileToPrinter(DHSPresentationLayer.Logic.PrinterInfo, System.String, System.Windows.Forms.Form)
       at DHSPresentationLayer.Logic.PrinterAPI.PrintLabel(System.String, System.String, System.Data.DataTable, System.Func`2<System.String,System.String>, System.String, System.String, Int32, System.Windows.Forms.Form)
       at DHSPresentationLayer.MRPFR130.showSSReport()
       at DHSPresentationLayer.MRPFR130.confirmCancelCloseButton_Confirm()
       at MINDBaseFormLibrary.BaseScreenReports.confirmCancelCloseControl1_EventButtonClicked(System.Object, DHSControlLibrary.MyEventArgs)
       at DHSControlLibrary.ConfirmCancelCloseControl.OnEventButtonClicked(DHSControlLibrary.MyEventArgs)
       at DHSControlLibrary.ConfirmCancelCloseControl.cmdConfirm_Click(System.Object, System.EventArgs)
       at System.Windows.Forms.Control.OnClick(System.EventArgs)
       at Infragistics.Win.Misc.UltraButtonBase.OnClick(System.EventArgs)
       at Infragistics.Win.Misc.UltraButton.OnMouseUp(System.Windows.Forms.MouseEventArgs)
       at System.Windows.Forms.Control.WmMouseUp(System.Windows.Forms.Message ByRef, System.Windows.Forms.MouseButtons, Int32)
       at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef)
       at System.Windows.Forms.Control+ControlNativeWindow.OnMessage(System.Windows.Forms.Message ByRef)
       at System.Windows.Forms.Control+ControlNativeWindow.WndProc(System.Windows.Forms.Message ByRef)
       at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)
       at System.Windows.Forms.NativeWindow.DefWndProc(System.Windows.Forms.Message ByRef)
       at Infragistics.Win.UIAutomation.UiaProviderControlNativeWindow.WndProc(System.Windows.Forms.Message ByRef)
       at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)
       at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)
       at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32)
       at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)
       at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)
       at System.Windows.Forms.Application.Run(System.Windows.Forms.Form)
       at DHSPresentationLayer.Program.Main()
    then 1 second after :
    Faulting application name: DHSDEVASystem.exe, version: 7.8.0.4, time stamp: 0x54c8f680
    Faulting module name: MSVCR110_CLR0400.dll, version: 11.0.50709.17929, time stamp: 0x4ffa580c
    Exception code: 0xc0000005
    Fault offset: 0x0000156e
    Faulting process id: 0x8ec
    Faulting application start time: 0x01d046916142e1e3
    Faulting application path: C:\Users\savaa\AppData\Local\Apps\2.0\DR9VMJ96.MZ3\DP07HVCX.MDB\dhsd..tion_0000000000000000_0007.0008_cfa90b0813b3f063\DHSDEVASystem.exe
    Faulting module path: C:\Windows\system32\MSVCR110_CLR0400.dll
    Report Id: 38cf9363-b285-11e4-b29f-0023242a2561
    The PC is on windows 7 32 bits with .net 4.5 installed.

    Hello,
    Based on the exception message, I found that your project is build with .NET 4.0, you could consider changing it to .NET 4.5.
    If you want to keep it built with .NET 4.0, then you could consider the following fix.
    FIX: "Faulting module name: clr.dll" error message when you run a Microsoft .NET Framework 4-based application
    Regards,
    Carl
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

Maybe you are looking for