Rfc doubt

hi folks im try to create an invoice by calling a bapi incoming invoice i have declared fiscal year still my programe lands into to dump stating
Function module "BAPI_INCOMING_inVOICE_CREATE" was called 
with the parameter "FISCALYEAR".                         
This parameter is not defined.    i have defined the paratmeter fiscalyear can u let me know who should i troubl shoot this .
regards,

HI:
type should be as declared
""Lokale Schnittstelle:
*"  IMPORTING
*"     VALUE(HEADERDATA) LIKE  BAPI_INCINV_CREATE_HEADER STRUCTURE
*"        BAPI_INCINV_CREATE_HEADER
*"     VALUE(ADDRESSDATA) LIKE  BAPI_INCINV_CREATE_ADDRESSDATA
*"       STRUCTURE  BAPI_INCINV_CREATE_ADDRESSDATA OPTIONAL
*"  EXPORTING
*"     VALUE(INVOICEDOCNUMBER) LIKE  BAPI_INCINV_FLD-INV_DOC_NO
*"     VALUE(FISCALYEAR) LIKE  BAPI_INCINV_FLD-FISC_YEAR
*"  TABLES
*"      ITEMDATA STRUCTURE  BAPI_INCINV_CREATE_ITEM
*"      ACCOUNTINGDATA STRUCTURE  BAPI_INCINV_CREATE_ACCOUNT OPTIONAL
*"      GLACCOUNTDATA STRUCTURE  BAPI_INCINV_CREATE_GL_ACCOUNT OPTIONAL
*"      MATERIALDATA STRUCTURE  BAPI_INCINV_CREATE_MATERIAL OPTIONAL
*"      TAXDATA STRUCTURE  BAPI_INCINV_CREATE_TAX OPTIONAL
*"      WITHTAXDATA STRUCTURE  BAPI_INCINV_CREATE_WITHTAX OPTIONAL
*"      VENDORITEMSPLITDATA STRUCTURE  BAPI_INCINV_CREATE_VENDORSPLIT
*"       OPTIONAL
*"      RETURN STRUCTURE  BAPIRET2
Regards
Shashi

Similar Messages

  • PI' RFC  Connection pool  doubt.

    Hi PI exports:
    i have a doubt about  pi' RFC  Connection pool ,pi RFC receive channel can set the conn pool size ,but when start the rfc receiver channel ,is there always only one Connection  pool ,or there is only one Connection  pool  instance?
      thinks
    Edited by: kevin liang on Oct 19, 2009 6:45 AM

    Hi,
      Connection poolins size means how many number of connection you want to make open to send data to ECC, We can define maximum number of connection in Receiver RFC Adapter,Go to additional parameters section and define Max Number of connection give the number there,thats it.Internally it works as Connection poolin mechanism.
    Regards,
    Raj

  • Doubt on FILE to RFC & PROXYS

    Hi everybody,
                        I'm able to solve most of my doubts by this forum, thankz to everybody who assisted me.Here are some simple doubts plz give solutions to them as many as possible
                  1.In my FILE to RFC scenario I'm using BPM & i should send response back to SENDER so what steps should i include in it ? I'm using BAPI_GOODS_MVT_CREATE bapi?
                  2.In my FILE to RFC scenario  I'm maintaining single SLD for DEV,CONS,PROD ,so can i configure my file sender service directly in ID as a BUSSINESS SERVICE?
                  3.Can any one give some information In which case we have to go for
    PROXY &  in which case for IDOC?exluding this reason  " if syst config is >6.20 or else go for IDOC or RFC for an sap system?
                  Plz kindly answer to this questions & valuable answers are rewarded.
                                                                                    Regards,
                                                                                    Vinod.

    <i>1.In my FILE to RFC scenario I'm using BPM & i should send response back to SENDER so what steps should i include in it ? I'm using BAPI_GOODS_MVT_CREATE bapi?</i>
    >>>
    Ref: /people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
    Else in case you have SP19 then ref this abstract from an earlier post !!
    <i>All,
    Just thought I'd add a quick note here.
    From SP 19 on XI 3.0 and SP 10 on PI 7.0, a File - RFC - File ( Asynch - Synch ) scenario can be done without a BPM.
    Steps:
    Integration Repository
    The Integration Repository will be similar to any Synchronous Scenario ( say HTTP - RFC ) . 1 Outbound Synch message Interface and 1 Inbound Synch Message Interface.
    Integration Directory
    This is where a few differences lie, so let me take some time.
    1. The Receiver Determination , Interface Determination will be the same as in HTTP - RFC synch scenario. Create the Sender File Adapter, Receiver RFC Adapter and Receiver File Adapter.
    2. Sender Agreement will be for the Sender File Adapter. Sender Agreement uses the Synch Outbound Message Interface.
    3. Receiver Agreement will be for the Receiver RFC adapter. Receievr Agreement will use the RFC as thge Inbound Message Interface.
    4. We need to add a few modules in the Sender File Adapter.
    Go to the Modules Tab of the Sender File Adater, and add the following modules in the same sequence,
    Number - ModuleName - Type - ModuleKey
    1- AF_Modules/RequestResponseBean - Local Enterprise Bean - 1
    2- CallSapAdapter-Local Enterprise Bean - 2
    3-AF_Modules/ResponseOnewayBean-3
    Parameters
    ModuleKey - ParameterName - ParameterValue
    1 - passThrough - true
    3-receiverChannel - Receiver File Adapter Name
    3-receiverService - Receiver Business Service/ System
    With this configuration, you can now handle the requirement without a BPM
    This feature been already blogged for JMS Adapters in these blogs ,
    Sync/Async communication in JMS adapter without BPM (SP19)
    Async/Sync Communication using JMS adapter without BPM (SP 19)
    Dynamic Configuration is also possible,and this as well as many other options are discussed in the How To guide - "How To Realize a sync-async and async-sync
    bridge within the Adapter Framework" available on the Service Market Place.</i>
    <i>
    In my FILE to RFC scenario I'm maintaining single SLD for DEV,CONS,PROD ,so can i configure my file sender service directly in ID as a BUSSINESS SERVICE?</i>
    >>
    you can use Business service !!!
    <i>3.Can any one give some information In which case we have to go for
    PROXY & in which case for IDOC?exluding this reason " if syst config is >6.20 or else go for IDOC or RFC for an sap system?</i>
    >>>
    Advantage of Proxy over RFC, IDOC
    /people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems

  • Doubts about XI and RFC or IDOC

    Hello
    We have an external system that will send a file with data, with data from that file will have to make some Batch input on a number of transactions and I doubt arises in the orient
    The platform of exchange will be XI and I would like if someone could guide me in which are the advantages and disadvantages of undertaking such Batch Inputs through IDOC or through an RFC function or if there is another better way to make this process
    Thanks

    Hi Alberto.
    As far as I understand your scenario, you are fetching the data from a file and update the R3 database using a BDC session.
    In that case, my suggestion is to use a custom RFC that takes these records and creates a BDC session. This would be a better way to handle this scenario instead of using any IDOCs.
    Regards,
    Hari.

  • Doubt in file to rfc to mail scenario

    Hi All,
    I have a doubt in configuring File2Rfc2Mail scenario,
    Actually my requirement is to send flat File to RFC, and trigger mail alerts for successfull execution , like after successfully posting the mesg to rfc i need to trigger a mail alert to mailserver,
    For that what i thought to do is file to rfc and from rfc response to mail , i don't know whether i can do like that or not , do anybody help me in this issue,
    Thanks in advance,
    Nousheen.

    Hey,
       Your BPM will be like this.
    recieve step(file)-> sysnchronous send step(rfc)-> send step(mail)
    3 abstract interfaces:-
    abstract asynchronous(file structure)
    abstract synchronous (in this request as file sturcture and response as mail structure)
    mapping between abstract synchronous and rfc(no need for transformation as mapping is outside)
    abstract asynchronous(mail structure)
    create two container variables, one for each abstract asynchronous interface.
    use them in recieve step(file) and send step(file)
    revert in case of any queries.
    reward points if useful.
    regards,
           Milan

  • Doubt  on RFC at receiver side

    Hi,
           I had some doubts in FILE to RFC scenario plz kindly answer to this questions ur help will be more valuable.
           1. Is it necessary to create RFC destination on ISERV pointing towards receiver syst?or on receiver syst pointing towards XI?
           2.i'm using BAPI_GOODS_MVT_CREATE so what will be the bapi returning parameter values for that?
           3.in FILE to RFC scenario after registering senders non-sap syst in SLD ,can i create B.SERVICE directly in I.D?
           4.canbody give info on REGISTERING OF QUEUES what is this concept ?
    we have to check this in SMQR  or SXMB_ADMIN?
    what we have to do in realtime REGISTER or UNREGISTER them?
              Plz kindly answer to this questions as many as possible?
               points will be awarded for most valuable answers.
                                                                                    Regards,
                                                                                    smitha.

    <i>> 1. Is it necessary to create RFC destination on
    > ISERV pointing towards receiver syst?or on receiver
    >  syst pointing towards XI?</i>
    You do not need any RFC destinations when using the Receiver RFC adapter. You just create a Receiver RFC adapter with the details pointing to your R3 system.
    <i>> 2.i'm using BAPI_GOODS_MVT_CREATE so what will
    >  be the bapi returning parameter values for that?</i>
    In the IR, you can check the Response XML of the same BAPI or execute the BAPI from SE 37 and check it out.
    ><i>> 3.in FILE to RFC scenario after registering
    > senders non-sap syst in SLD ,can i create B.SERVICE
    >  directly in I.D?</i>
    This is optional . if you have created a 3rd Party Business System you can use this as bioth the sender and receiver or you can use a Business Service created in the Integration Directory.
    Regards
    Bhavesh

  • Basic doubts Regarding the RFC to File scenario.

    Hi All,
    I'm doing a RFC to File scenario, so before starting the development i went through many blogs and sites to know more the about scenario. I'm confused in the step where we have to create a RFC (type TCP/IP) in sm59.
    I have the following doubts :
    1)whether  to create the RFC in sender (which will be ECC system) or XI.
    i.e., RFC in sender (ECC) pointing to xi system in sm59 of Sender(ECC)
    or
    in XI pointing to sender (ECC) system.
    2) the program id maintained in RFC.
    the program id is any name or the FM which is being imported in XI system.
    Thanks in Advance,
    Kind Regards,
    Lalitkumar.

    Hi Lalitkumar,
    1)whether to create the RFC in sender (which will be ECC system) or XI.
    i.e., RFC in sender (ECC) pointing to xi system in sm59 of Sender(ECC)
    or
    in XI pointing to sender (ECC) system.
      It should be in sender ECC.
    2) the program id maintained in RFC.
    the program id is any name or the FM which is being imported in XI system.
    It can be any name but should be same in RFC destination and RFC adapter.
      As stefen mentioned use ABAP proxy inspite of RFC as its better performance wise.
    Regds,
    Pinangshuk.

  • Doubt regarding Sender adapter file content conversion to RFC

    Hi Experts,
    Below is the my Source and  Target XML structure ( i have creaated source structure same as target RFC structure),  This scenario is working fine when i give XML file as input. File -> XI -> RFC , xml file is able to update the information in R3.
    How should i configure sender file adapter for file content conversion for above structure(in this case input is fixed lenth text), and i could able to change source structure according to our req, without changing target RFC strucuture.
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:MT_HSA_IDNumber xmlns:ns0="urn:passhe.com/UpdateIdNumberISA32">
       <COMMIT_I>X</COMMIT_I>
       <IDENTIFICATION>
          <STUDENT>6500001191</STUDENT>
          <ID_TYPE>FS0030</ID_TYPE>
          <ID_NUMBER>testxml</ID_NUMBER>
          <VALID_FROM>20070421</VALID_FROM>
          <VALID_TO>20091231</VALID_TO>
       </IDENTIFICATION>
      </ns0:MT_HSA_IDNumber>
    I have configured sender file adapter with FCC like :
    Document name as: MT_HSA_IDNumber
    Document name space as: urn:passhe.com/UpdateIdNumberISA32
    Record structure as: COMMIT_I,1,IDENTIFICATION,1
    COMMIT_I.fieldNames : COMMIT_I
    COMMIT_I.fieldFixedlengths: 1
    IDENTIFICATION.fieldNames: STUDENT,ID_TYPE,ID_NUMBER,VALID_FROM,VALID_TO
    IDENTIFICATION.fieldFixedlengths: 12,6,60,8,8
    i am getting error like this: even when i change source structure like below metioned:
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:MT_HSA_IDNumber xmlns:ns0="urn:passhe.com/UpdateIdNumberISA32">
       <COMMIT>
          <COMMIT_I>X</COMMIT_I>
       </COMMIT>
       <IDENTIFICATION>
          <STUDENT>6500001191</STUDENT>
          <ID_TYPE>FS0030</ID_TYPE>
          <ID_NUMBER>idnumber1</ID_NUMBER>
          <VALID_FROM>20070421</VALID_FROM>
          <VALID_TO>20091231</VALID_TO>
       </IDENTIFICATION>
    </ns0:MT_HSA_IDNumber>
    Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Parameter 'COMMIT_I.fieldFixedLengths' or 'COMMIT_I.fieldSeparator' is missing Consistency check: no. of arguments in 'COMMIT_I.fieldFixedLength' does not match 'COMMIT_I.fieldNames' (0 <> 1)
    Please help me out
    thanks
    dhanush

    Hi Dhanush,
    Try giving the Sender FCC this way for the source structure you have mentioned above.
    Record structure as: COMMIT,1,IDENTIFICATION,1
    COMMIT.fieldNames : COMMIT_I
    COMMIT.fieldFixedlengths: 1
    Hope this helps.
    Thanks and Regards,
    Induja

  • Doubt about RFC Destination in FILE to IDOC Async scenario

    hi
    In FILE-XI-IDOC Async Scenario we are creating RFC Destination in R/3 and XI.
    For Asyn we don't want response But We are Creating RFC Destination in R/3 also.
    Any specific reason.
    Thanks in advance.

    First you need to have a clear understading of how the idoc adapters works.
    In xi we create rfc destination and specify that in the port maintenance on the idoc adapter so that we can establish a connection to the sender / receiver system which contains the IDOC METADATA (IDX2) that is required by the idoc adapter to convert the native idoc into idoc xml format.
    In R/3 as sender we create rfc destination so that when the idoc has to be transported to the xi system first it will be sent to trfc port that rfc desination that  u define the trfc port contains that the target system address(IP) and logon parameters req.So idoc can be sent to the desired destination.
    In R/3 as a receiver to facilitate communication we define rfc dest, partner profile and specify the inbound parameters so that idoc can be posted.
    Hope this answers your ques.
    cheers
    *Raj*
    *POINTS IF SATISFIED WITH ANSWER.

  • File to IDOC Scenario - Doubt in RFC Destination

    Hi all,
    I m working on a File - IDOC Scenario. I got a IDX1 error Also when I try to import IDOC in IDX2, I got I:000 error message(No more information was given) . When I checked the RFC destination, Test Connection works fine. But Remote Logon didnt work, since the target system is not a Trusted System
    Is it necessary to make the Target System, a Trusted System ? (For enabling Remote Logon)

    Hi ,
    There might be some problem with the R3 user that u r using...
    For some versions of R3 it is required that the password be in CAPS for making an RFC connection...
    I knw this sounds weird but even i had this problem....
    Also chk if the XI user has RFC priviliges..
    reward points if helpful
    PrashANt

  • Doubt Regarding Sender Rfc adapter calls

    Hi Experts,
         When we call RFC in R3 system by giving destination as XI system,
    1) where exaxtly RFC cal executes either in R3 or XI?
    In case of sender RFC syncronouse call?  where exaxtly RFC cal executes either in R3 or XI?
    In case of sender RFC asyncronse call? where exaxtly RFC cal executes either in R3 or XI?
    2) In case of Recever RFC syncronouse call, where exactly RFC call executes, is it in XI or R3 system?
    Please help me out.
    thanks
    siva

    <i>1) where exaxtly RFC cal executes either in R3 or XI? </i>
    It is at R3 for bothe sync and asyn sender scenario.
    <i>2) In case of Recever RFC syncronouse call, where exactly RFC call executes, is it in XI or R3 system?</i>
    RFC is called from XI. The call is actually executed at R3 receiver
    Regards,
    Prateek

  • Doubt regarding File Content Conversion. File- RFC

    Hi Experts,
        My scenario is File -> XI -> RFC,
    I am able to update the records in R3 when i get a fixed length file with a single record.
    RFC can process one record at a time (its 1 to 1 , its not 1 to unbounded),
    May i know what are the changes to be done in the scenario to implement this existing interface to process a fixed length file contains a multiple records.
    How to get RFC return messages when ever there is return message , as this is not the synchronous scenario.
    Please help me out.
    Thanks

    HI,
    First you need to create a structure [SE12]
    Once that is done, open the function module [SE37] and select the tab [Table].
    Add a new parameter and for the Associated Type use the structure that you have just created.
    Then reimport the RFC in XI.
    I hope it helps.
    Now, to make the RFC return messages you shall create a BPM.
    Notice that this will be a Async -> Sync -> Async interface...
    Basically your bpm steps will be like this:
    Receive,
    Transform if needed,
    Syncronously Send and receive response,
    Transform again if needed,
    Send Asynchronously.
    Take a look at the image in the link to have a better idea on the BPM setup
    https://weblogs.sdn.sap.com/weblogs/images/251764026/bpmAsync2Sync2Async.JPG
    (please, award points if usefull      )
    Edited by: Luis Melgar on May 9, 2008 9:39 PM

  • Doubts in RFC sender Adapter

    Hi XI Gurus,
    Can any body plz explain me about the parameters used in RFC Sender Adapter (like RFC Server Parameters: Program ID, Gateway, etc..)
    Thanks in advance.

    Hi,
    Refer this link there they have given everything clearly
    http://help.sap.com/saphelp_nw04/helpdata/en/67/6d0540ba5ee569e10000000a155106/frameset.htm
    Application Server (Gateway) : host name of the sender system.
    Application Server Service (Gateway):  Gateway service of the sender system. This can be the numeric description of the service port in the sender system or the alphanumeric equivalent (for example, sapgwXX, where XX is the system number of the sender system).
    Program ID: Program ID of the registered server program. The selected program ID must uniquely describe the RFC sender channel in the configured gateway (Application Server (Gateway) and Application Server Service (Gateway) parameters).
    For Program id: In sender R/3 system Tcode SM59
    1.Create RFC Destination with connection type: T
    2.Choose Registered server program
    3.Give program id(you can give any name here, the program id you give in sender RFC adapter and here should be same )
    4. Give Gateway host and Gateway value.
    You can also check this blog
    /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
    Regards,
    Sakthi

  • RFC to WebService Scenario  doubt

    Hi,
           I'm passing  parameters from R/3 system  RFC.. and  based on that selection criteria  the data will fetch from the  Remote Application.. and  send it to R/3.. finally my RFC will load these data into  R/3 system. this is my Scenario( that means.. RFC to WEBSERVICE)  so, in the reciever side i should use the SOAP adapter..
         but for these type of scenarios..  is  WSDL file is   mandatory or.. with out WSDL file also can we do the  scenario.. and  if this is mandatory means..  how we will get the WSDL file... 
            because  according to my reqirement i know only the sender system (R/3) and Receiver system(Remote Application) details..  I dont know any thing about  other details..
    please  suggest me what are the things are needed.. so, that i will get from my client..
    Regards
    Jain

    Hi,
    WSDL contains the message /data structure for you input and output.
    If you know the Web Services input /output data , you can create it manually or if you have WSDL, you can directly import in IR and all the request/response message would be generated automatically.
    To call a Web Service, only URL is required.
    You can ask your client to provide the WSDL file.
    Regards,
    Piyush

  • Doubts in File to RFC scenario

    <u><b>Scenario we are working on:</b></u>
    Legacy System -> Flat File -> XI2.0 -> RFC -> SAP R/3 470 ( WAS 620 )
    <u><b>What we have done till now:</b></u>
    1. Created technical system for XI server and the SAP 620 ( target system )
    2. Created business system for XI Server and target system
    3. Created a software product for legacy system and the corresponding technical system and the business system
    4. Defined the business scenario in Repository including Actions, Message Interface, Message Type, Data Type (for source file), Imported RFC signature from target system, message mappings and message interfaces.
    5. Configured the file adapter.
    6. Configured business scenario in Integration Directory including interface determination and receiver end points
    <u><b>Where we are stuck:</b></u>
    1. Currently I have created the entire set of objects under the new software component I created for source system. I want to know how to decide under which software component should I create the design objects, e.g under the software component for source system, or under the software component for target system or am I supposed to create a new product altogether including all the software components in my scenario.
    2. What is the significance/dependency of namespace in the design process?
    3. I have configured the inbound file adapter (attached is the configuration file). How do I integrate it with the Integration server? In other words where to specify the link between my business scenario the file adapter.  How do they talk to each other?
    4. We are not able to configure the RFC adapter. Can we get a configuration file for a working adapter? Are there any pre-requisites for the RFC adapter configuration? Also once configured how will it talk to Integration Server?
    5. Is it possible to use proxies on Integration server in our scenario? Our XI system is installed on WAS 620 with J2EE 620 and the target system is also WAS 620.
    6. Is it possible to send email notification from XI in case or any errors e.g while accepting the file, while mapping, or while passing to target system

    Hi Satinder,
    Below are the answers for your questions:
    Regards
    Prasad
    Netweaver RIG-XI
    SAP Labs LLC.
    Ans1: If you are creating a new sceanrio, you can create a product and a software component in SLD and import the software component into Int.Repository. You can define 1 namespace or mutliple namespaces under this SC.
    It all depends on how are desiging your objects in SLD, Int Rep etc. This can be done in various ways.
    Ans2:
    Namespaces  Definition:
    Namespaces in the Integration Builder are namespaces in the sense of XML namespaces that are sub-divided further into semantic units within the Integration Builder software component versions. Objects of a namespace can only be shipped as part of the corresponding software component version and not separately.
    XML Namespace Definition: An XML namespace is a collection of names, identified by a URI reference , which are used in XML documents as element types and attribute names
    RFC2396
    IETF (Internet Engineering Task Force) RFC 2396: Uniform Resource Identifiers (URI): Generic Syntax
    Use
    The following types of namespaces exist in SAP Exchange Infrastructure:
    ·        Repository namespaces are displayed in the Integration Builder (Design) navigation tree. They are all assigned to a software component version but are used differently:
    ¡        Repository namespaces are used to avoid naming conflicts. For objects of the same object type, it is not possible to have duplicate object names within a repository namespace. In other words, a repository namespace is a quantity in the Integration Repository in which the object names are unique.
    ¡        Software component versions are used to define shipment units. It is not possible to ship objects in a namespace (business scenario objects, business process objects, interface objects, mapping objects, and adapter objects) on their own. Instead, they are shipped as a part of the relevant software component version.
    Although repository namespaces are assigned to the software component version in the navigation tree, the software component version does not affect the uniqueness of the object names.
    ·        XML namespaces are used as identifiers for message instances or customer-specific fields in the instance. You can specify XML namespaces as an attribute of (fault) message types and data type enhancements.
    ·        Namespaces in the System Landscape Directory (SLD), which have nothing to do with repository or XML namespaces (see: Namespace).
    ·        Internal namespaces, which are required in message instances, for example. The internal namespace for fields in the message header is: http://sap.com/exchange/MessageFormat, for example. These namespaces are of no further interest for SAP XI users.
    Ans3: Check the Adpater Documentation. In your case, the legacy system will be creating a file in the file system where the file adpater is installed.You have to mention this path in your FA configuration. Once the FA is running, The file is polled automatically. The parameter defined in the config file will send direct the message to XI server. For Ex:
    XMB.TargetURL=http://:8000/sap/xi/engine?type=entry
    Ans4: Check the documentation for RFC Adapter Config. Once configured it will talk to XI via JCO. send me an email if you have more questions.
    Ans5: Yes you can use Proxies as your target system is was620.
    Ans6: this is possible in XI-3.0 -SP04 as the SMTP adpater is available. You have to model the message in XI-3.0 when to send an email message.

Maybe you are looking for