IDOC fi_idoc_create_fidcc1

Hi all,
   I just want to know how should i use idoc 'FI_IDOC_CREATE_FIDCC1'
Thanks in advance,
Sugeet.

hi u have to check partner profile
for ur function module,
if it is related to message control, u have to maintain  function module in message control screen

Similar Messages

  • Sending Outbound FI Documents IDOC via ALE

    Hi all,
    We would like to send FI documents via IDOC. However, the message types we found, (FIDCC1,FIDCC2,FIDCMT) do not have outbound function. In addition to that how can we trigger IDOC, after posting FI documents .
    Thank you for your help...
    Best Regards,
    Didem GUNDOGDU
    mail: [email protected]

    hi, the outbound function for FIDCC1 FIDCC2 is list as followinig:
    FIDCC1     FI_IDOC_CREATE_FIDCC1
    FIDCC2     FI_IDOC_CREATE_FIDCC2
    But still can't find the FIDCMT, maybe you can create a customize function reference to two others.
    About trigger the IDOC sending, you can add the call function into a proper user-exits.
    Help it can be helpful

  • Regarding IDOC in Finance

    Hi all,
    I'm now starting to work on this IDOC_INPUT_FIDCC1.
    Can I know is there any way to create a IDOC that I can test run in this FM with we19?
    I need a IDOC so that I can test on this FM but currently I don't have any, therefore need to create one by myself.
    I'm thinking maybe I can do something like this.
    For example :
    For the SO, if i need to test on the inbound IDOC_INPUT_ORDERS, i can try create a IDOC with creating a SO in VA01, then trigger the output type and create a IDOC by IDOC_OUTPUT_ORDRSP when execute the program RSNAST00. Then use the generated IDOC and run again by using this FM IDOC_INPUT_ORDERS in we19.
    I get this answer from a kindly expert in SDN that suggesting me to do this:
    You can use this FM FI_IDOC_CREATE_FIDCC1 or FI_IDOC_CREATE_FIDCC2 to generate the outbound IDoc.
    Then use the generated IDoc as reference for your inbound IDoc data mapping and simulate the IDoc via WE19.
    I'm new and technical, lack of idea in FI.
    should I generate the IDOC in Tcode f-28 or another Tcode that I found in forum FB something? How should I know the output type that will trigger this IDOC?
    I mean for SO can get from SPRO then find the output determination and see the output type and program or FM involved..but for this finance...I really have no idea in this.
    I mean I would really like to know what Tcode that I should use to create the Accounting and from there i can generate the IDOC...
    Please advice.
    Thanks..
    Best Regards,
    JL

    Hi all,
    I'm now starting to work on this IDOC_INPUT_FIDCC1.
    Can I know is there any way to create a IDOC that I can test run in this FM with we19?
    I need a IDOC so that I can test on this FM but currently I don't have any, therefore need to create one by myself.
    I'm thinking maybe I can do something like this.
    For example :
    For the SO, if i need to test on the inbound IDOC_INPUT_ORDERS, i can try create a IDOC with creating a SO in VA01, then trigger the output type and create a IDOC by IDOC_OUTPUT_ORDRSP when execute the program RSNAST00. Then use the generated IDOC and run again by using this FM IDOC_INPUT_ORDERS in we19.
    I get this answer from a kindly expert in SDN that suggesting me to do this:
    You can use this FM FI_IDOC_CREATE_FIDCC1 or FI_IDOC_CREATE_FIDCC2 to generate the outbound IDoc.
    Then use the generated IDoc as reference for your inbound IDoc data mapping and simulate the IDoc via WE19.
    I'm new and technical, lack of idea in FI.
    should I generate the IDOC in Tcode f-28 or another Tcode that I found in forum FB something? How should I know the output type that will trigger this IDOC?
    I mean for SO can get from SPRO then find the output determination and see the output type and program or FM involved..but for this finance...I really have no idea in this.
    I mean I would really like to know what Tcode that I should use to create the Accounting and from there i can generate the IDOC...
    Please advice.
    Thanks..
    Best Regards,
    JL

  • Which IDoc Type and Message Type to use for Credit Memo?

    Could you guys please tell me which IDoc type and Message Type to use for Credit Memo? Also if possible tell me the process code/ function module.
    Will certainly give points for right answer. Thank you for reading.

    Hi,
    You can use IDoc type FIDCCP02 with message type FIDCC1/FIDCC2 for Credit Memo.
    Also you can use this FM FI_IDOC_CREATE_FIDCC1/
    FI_IDOC_CREATE_FIDCC2 to generate the IDoc.
    Regards,
    Ferry Lianto

  • I need to create RFC function module which creates the IDOC

    Hi-
    Any idea how to create RFC function module which creates the outbound IDOC. If you have any sample code please forward to me.
    Thanks,
    Sony

    My Problem is
    Whenever they create Invoice using T-code's like FV65(Parked Document), automatically should create IDOC's...
    I have used message type FIDCC1 but this message type is usefull only for Posting documents.
    1. Whenever they create parked document, entries will be stored in BKPF(Parked Document-Filed-BKPF-BSTAT = 'V') and Bseg....
    2. I have to read entries from those tables and should create IDOC...
    3. I checked FM's(FI_IDOC_CREATE_FIDCC1, FI_IDOC_PREPARE) but are not useful...
    4. Now I need to write one RFC function module and that FM should create the IDOC's....
    Can anyone please help me out?
    Thanks,
    Sony

  • ALE: FI-IDoc FIDCCP01/FIDCCP02

    Hi all,
    i have a problem with creating and sending IDocs for FI-Documents. I use Message type FIDCC1 and the IDoc Basictype FIDCCP01 (with an extension). In the Partnerprofiles i maintained this data combination. But by posting an FI Document an IDoc with IDoc type FIDCCP02 is created but faulty with the reason of not existing entries in the outbound table. The reason of faulty is correct, but i do not really understand why an FIDCCP02 is created. I assume that the reason is the used function module 'FI_IDOC_CREATE_FIDCC1' (i think that is used) and the IDoc type that is used is hard coded FIDCCP02. But some created IDocs fit to my maintained partner profile (FIDCCP01 with extension). So that i am really confused and do not really know what has to be done now.
    An OSS message (459938) says that the old FIDCCP01 still can be used. How?
    I am working with a 46B (PatchLevel 51).
    Please help.
    Thanks in advance
    Michael

    Hi,
    in WE20 you maintain the partner profile. Selecting a partner you see which messages are distributed (outbound and inbound). If you select a message type and show the details (for example Screen 'Partner profiles: Outbound parameters) you see in addition to the message type a field for message code (3 digits) and message function (3 digits). With these two additional informations you can separate processes using the same message type.
    Think about several systems sending data with one message type to one central system and you want to handle the inbound different. Therefore you can use message codes and message functions.
    My problem was that i didn't really know what i did when i used this the first time. We wanted to distribute the message FIDCC1 with the IDoc type FIDCCP01. We have done several times with other systems and it always runs without any problems. But when i started using MESCOD and/or MESFCT an error appears with IDoc type FIDCCP02 and that our additional segment is not identifyable).
    So i had a look how the ALE service version conversion works. As i wrote before our Application creates a master IDoc with type FIDCCP02 and former this was converted to FIDCCP01.
    It is done like following (sequences of calls):
    CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
    PERFORM 'IDOC_SELECTION_AND_SERVICES'
    CALL FUNCTION 'ALE_IDOC_SERVICES_APPLY_OUT'
    PERFORM 'IDOC_CONVERT_VERSION_OUTBOUND'
    PERFORM 'CHANGE_IDOC_VERSION'
    The program takes the values of the IDoc control information (MSGTYP, MESCOD, MESFCT) and checks them against table EDP13. If an entry exists the change of the IDoc version will be done, else not.
    So my fault was to maintain the partner profile with MESCOD and MESFCT but in the control information these values were empty (how should the application program know which walue have to be filled in?). So i did it in an exit (F050S004 FM EXIT_SAPLF050_007):
    >>> Enrich IDoc Control structure with a value for the logical
        message function, to make a difference for different processes in
        the partner profile.
      idoc_control-mesfct = c_mesfct_fidcc1.  "YFA
    Now it fits to my partner profile and it runs properly.
    But don't forget to maintain the partner profile in the receiving system equal and VERY IMPORTANT think about the inbound processing. You have to maintain the Assignment of the inbound FM to log. Message and IDoc type with MESCOD and MESFCT using transaction WE57.
    Thats all.
    Hope it helps.
    Michael

  • From Which FI Transaction Trigger outbond IDOC FIDCCP02;

    Hi Experts,
        Can you please let me know From Which FI Transaction Trigger outbond IDOC FIDCCP02;Is there any Exit Or BADI AVAILABLE TO DO THIS?
    Also how to fill Custom segments in this.
    Thanks.
    Debi.

    Hi Debi,
    You can use BADI IDOC_DATA_INSERT to populate your custom segments.
    Also there are user exits available to use in FM
    FI_IDOC_CREATE_FIDCC1 or FI_IDOC_CREATE_FIDCC2.
    Check EXIT_SAPLF050_*
    Regards,
    Ferry Lianto

  • Logical System in IDOC-XI scenario

    Hi,
         I need help to understand few things in IDOC-XI scenario, could any one help me in this regard.
        we use Adapter specific identifiers to map services, we have following type of identifiers 1) Sys.ID & Client No.  2) Logical System. 
    my questions are
    a) Are we use Logical System in B to B scenario ?
    b) Are we use LS in reference to the SAP system or Non SAP system ? if a non SAP system....how a non SAP system send an IDOC and why a non SAP system receive an IDOC ( conversion is possible in XI ) ?
    Thanks and Regards
    Mahesh.

    Hay Kumar,
    Logical systems can also be used for SAp sytems wich are not installed yet as a virtuall placeholder.
    a) yes. if on of your business is a non sap system or a propritery system that you developed yuo'll ue LS.
    b) non SAP system can send and recieve IDOCs. so it's possiable to get an IDOC from a system and turn it into an RFC for SAP or get an IDOC from an SAP system and then turn it into something else for another system.
    Have a Good One,
    Uri Lifshitz.

  • IDoc not received in MII

    Hi All, 
    I am using SAP MII 12.1.5 Build 87. 
    I am facing problem with iDoc Listner we have configured iDoc Listner properly in SAP ERP, SAP NW and in SAP MII. 
    We are able to send iDoc from SAP but we are not able to receive same in MII. 
    Port and iDoc Server is giving status connected previously it was working fine in SAP MII 12.1.5 Build 83. 
    Following are the log details for SAP MII Logger as well as SAP NW Log. 
    SAP NW Log: 
    Error processing JRA IDOC message  
    SAP MII Log: 
    Error processing JRA IDOC message  
    Error processing JRA IDOC message [server=xxx, client=xxx]  
    [EXCEPTION]
    java.lang.NullPointerException
    at com.sap.xmii.ejb.JRAListenerBean.onMessage(JRAListenerBean.java:130)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MessageListenerType.invoke(Interceptors_MessageListenerType.java:110)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Lock.invoke(Interceptors_Lock.java:21)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
    at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
    at com.sap.engine.services.ejb3.runtime.impl.MDBProxyInvocationHandler.invoke(MDBProxyInvocationHandler.java:77)
    at $Proxy943.onMessage(Unknown Source)
    at com.sap.mw.jco.jra.idoc.JRAIDocExtension$IDocMessageHandler.onMessage(JRAIDocExtension.java:72)
    at com.sap.mw.jco.jra.JRA$ReaderThread.sendDirectToMdb(JRA.java:6641)
    at com.sap.mw.jco.jra.JRA$ReaderThread.sendAsynchRequest(JRA.java:6601)
    at com.sap.mw.jco.jra.JRA$ReaderThread.handleRequest(JRA.java:6771)
    at com.sap.conn.jco.rt.DefaultServerWorker$RequestDispatcher.handleRequest(DefaultServerWorker.java:989)
    at com.sap.conn.jco.rt.DefaultServerWorker$RequestDispatcher.handleRequest(DefaultServerWorker.java:967)
    at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:142)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:2927)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2659)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2478)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2362)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2207)
    at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:259)
    at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:322)
    at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:220)
    at com.sap.mw.jco.jra.JRA$ReaderThread.run(JRA.java:7260)
    at com.sap.engine.services.connector.jca15.work.TaskImpl.run(TaskImpl.java:255)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
    at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
    Please help me out on this issue.                                         
    Regards,
    Manoj Bilthare
    Edited by: Manoj Bilthare on May 19, 2010 12:57 PM

    Hi Manoj,
    Once you have configured your Listener have you checked pressing the update button and i dont want to ask you which version of NW SP you have installed as you said it was working for you with Build 83, but nevertheless NW SP Level should not be not less than SP3.
    If this doesn't help you,please try  restarting your server again.
    How about the credential editor have you configured this as well?
    Regards,
    Sudhir Kumar
    Edited by: Sudhir Kumar Shambana on May 19, 2010 10:46 AM

  • Open Sales orders through IDOC

    Hi
    We are trying to send the list of open sales orders of a customer in an IDOC to the customer. For example, if the customer has got 15 sales order to be delivered to him , he needs the details of all these 15 orders in an single IDOC
    Is there any IDOC message type available for this in SAP R/3 4.7 version  or is there a standard solution of sending these details through IDOC
    Regards
    Anandh

    Hi
    We are trying to send the list of open sales orders of a customer in an IDOC to the customer. For example, if the customer has got 15 sales order to be delivered to him , he needs the details of all these 15 orders in an single IDOC
    Is there any IDOC message type available for this in SAP R/3 4.7 version  or is there a standard solution of sending these details through IDOC
    Regards
    Anandh

  • Scheduling Agreement with Delivery Schedule using Idoc messages

    Hi all,
    Can anybody please explain the importance of the field name "LABKY" in Idoc execution for Forecaste/JIT Delivery Schedule.
    My requirement is that when i send a new Idoc i do not want the old schedule line which are not yet released , to be deleted .
    As per the SAP help the use of the field LABKY is related to this , but when i tried its value as "1" , the previous schedule lines are still getting deleted.
    Can you pls explain how to go about it . ( DELFOR/DELJIT Idocs)
    Thank you
    Regards
    Subha

    Hi ,
    The Field
    LABKY : Delivery schedule key
    internal data type : CHAR
    Internal length : 000001 characters
    Position in segment : 026, Offset : 0393. external length : 000001
    Regards
    Seegal

  • Invoice and delivery notes - idocs..

    Hello SD experts,
    I am new to SD.
    Can any one tell me what is the invoice. I mean
    what are the table AND transaction codes I have to go and check ?
    What are delivery notes ?
    My functional consultant is telling that
    there is a consolidated invoice and there are 2 delivery notes that are being combined for this invoice. The invoice # is 6016186004
    For DN#   6073107044 there is a VICS BOL that was passed back that is = 04000000000016146 
                   6073107045 there is a VICS BOL that was passed back that is = 04000000000016023
    and he wants to know how the program selects which VICS BOL fields in IDOC.  He gave me to use IDOC #77122253 in quality system for testing.
    In this case , Idoc checking/testing...I need to go to RSNAST00 program ?
    If so then what are the I need to give
    Output application    (is it V1 or MR ?)       
    Output type    ??

    hi ..
    Please refer below..
    for invoice ,  tables: VBRK and VBRP
    AND transaction codes : VF01 to 03.
    What are delivery notes ?
    after goods issue, we need to issues delivery note to customer.
    In this case , Idoc checking/testing...I need to go to RSNAST00 program ?
    you need to go to VL70 or you can process with RSNAST00.
    Output application type : V2
    Output type : LD00
    Regards
    Venkat.. Ananth Technologies

  • Error Posting IDOC: need help in understanding the following error

    Hi ALL
    Can you please, help me understand the following error encountered while the message was trying to post a IDOC.
    where SAP_050 is the RFC destination created to post IDOCs
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
      <SAP:P1>FM NLS_GET_LANGU_CP_TAB: Could not determine code page with SAP_050 Operation successfully executed FM NLS_GET_LANGU_CP_TAB</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error: FM NLS_GET_LANGU_CP_TAB: Could not determine code page with SAP_050 Operation successfully executed FM NLS_GET_LANGU_CP_TAB</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Your help is greatly appreciated.............Thank you!

    Hi Patrick,
      Check the authorizations assigned to the user which you used in the RFC destinations, If there is no enough authorizations then it is not possible to post the idocs.
    Also Refer this Note 747322
    Regards,
    Prakash

  • Error while executing a JDBC to Idoc scenario : No standard agreement found

    Hello SAP PI Gurus, 
    I am having a JDBC to idoc Scenario .And the interface is running at 10 min of duration. 
    <SAP:AdditionalText>No standard agreement found for ,
    BS_EXT_CTBSREPDB, , BS_ERPQAS_QE1_320, http://XYZ.com/FI/FI_FI_01/Charges, FIDCC2</SAP:AdditionalText>.
    While i test the configuration...i get an error in reciever agreement as mentioned above.
    Can you pls help me in resolving this issue.
    Regards,
    Ravi

    Hi,
        I think the problem is with namespace....for IDOC the namespace will be "urn:sap-com:document:sap:idoc:messages"...but in your case it is different.....i.e http:....etc.....please check whether you 've used the same IDOC withe above mentioned namespace in all the configuration objects like interface determination, receiveragreement etc.....
    Thanks
    Priyanka

  • Getting an error "Customer could not be determined" for IDOCs in SCM 7.0

    Hi Friends,
        I am executing the report RSMIPROACT in ECC 6.0 system to publish Demand and Stocks into the SCM 7.0 system.
    The IDOC is processed without any errors in ECC 6.0 . However, in the SCM 7.0 system , the IDOC fails with the error.
    I have noticed that 2 things .
    1.  E1ADRE1 field is NOT being sent by the ECC system .
    2. I get the same error even if I manually add this field and add value 300 or 301 for the qualifier field.
    Has anybody faced this problem before ?
    I look forward to replies.
    Detailed error is given below.
    Regards,
    Ranjini.
    Customer could not be determined
    Message no. /SAPAPO/EDI010
    Diagnosis
    The system must determine the customer number from the IDoc data in order to update stock and sales figures for customers. It uses the additional section E1ADRE1 with the qualifier '300' or '301' in the vendor address section to do this. The customer number stored here should have a valid customer number in the APO System.
    The section was not available in the processed IDoc.
    System Response
    The system cancels processing.
    Procedure
    Configure the EDI convertor in such a way that the corresponding section has a value.

    Hi Ranjini,
    Please look into the following
    1) Customer master data is fully maintained
    2) Customer number ranges are fully defined in customisation
    3) Customer address details are maintained
    4) Is there any special characters used while defining customer data or customer
    number like $, #,[ etc.,?
    5) Customer int models are active in SCM side prior to IDOC processing (including
    customer, demand, stocks etc)
    Please confirm your findings
    Regards
    R. Senthil Mareeswaran.

Maybe you are looking for