Sending customer Idoc to iView of portal

Hello Everybody,
I have an scenario where i need to send customer data to an iVeiw portal thru XI. I know that if there is any webservice available on that portal then i can call that webservice but i am not sure though.
So, please provide your inputs in achieving this.
Thanks,
Vijay Kumar T.

Hi Mike
First you define the
1-RFC Destination that is unique name for your RFC destination.
2-Then you define Connection Type in it can be TCP/IP/R3 Connections etc.
3-Then define Target host ,this is the TCP/IP host name of the remote system.
  You can see the list of these options in tocde SM51.
4-System number ,this also you can check in SM51 if you have an account on the remote system.
5-Logon:here you give the client number ,user id and password to log on to the remote system.
Hope it is helpful.

Similar Messages

  • Track changes in customer material info (VD52) and create custom IDocs

    Dear experts,
    we want to track changes, which are made in VD52 (Customer matertial info record) and create custom IDocs (Z-format) based on these changes. What is the best way to do this?
    Best regards,
    David

    Hi,
    There are a dedicated BTEs (Business Tranaction Event) for this purpose (transaction FIBF).
    - created customer material infos OUTBOUND_CALL_00504001_E
    - changed customer material infos OUTBOUND_CALL_00504002_E
    - deleted customer material infos OUTBOUND_CALL_00504003_E
    You can assign your own FM to the BTE and send custom IDoc whenever there is a new/updated/deletd customer-material info record.
    Regards,
    Marcin

  • Problem with Custom idoc sending

    Hi Experts,
    We have created partner profile and port for receiver system, our idoc is Z (custom) idoc.
    but the problem is here, when we are sending that idoc from R/3 system, it is in Yellow position with message number 30. How we can solve this problem.
    Is there any other configuration required for Z (Custom) idoc.
    Please help,
    Regards,
    Study SAP

    hi check this...
    http://www.****************/Tutorials/ALE/CustomIDOC/Create.htm
    check  the process followed or not if u miss any steps then it will give warning....that is not a problem..see one thing after creating the idoc u need to give the status back to the idoc_status. otherwise it will not show the green message 51...we have to do it if this is the custom idoc ...otherwise if it is a standard one there is nothing to do it will automatically catch the message back.

  • Custom IDoc program to send PO ?

    Hai,
    Can any one send the complete program, on how to send PO (Purchase Oeder) through custom IDoc .
    Please send code for both outbound and inbound process ?

    Hi Vamsi,
    Here i am sending sample codes for Inbound and Outbound Processes..
    IN OUTBOUND SIDE :
    REPORT  ZSTAND_PROGRAM.
    *1.     Create parameters/select-options for input data. i.e., empno, message type, logical system.
    PARAMETERS : P_SNO LIKE ZSAMP1-SNO OBLIGATORY,
                 P_MESTYP LIKE EDMSG-MSGTYP DEFAULT 'ZMSG1',
                 P_LOGSYS LIKE TBDLST-LOGSYS OBLIGATORY.
    *2.     Create Data objects for control record, data record and database table.
    DATA : C_SEGMENT LIKE EDIDD-SEGNAM VALUE 'ZSEG1',
           C_IDOCTP LIKE EDIDC-IDOCTP VALUE 'ZIDOC1'.
    DATA : BEGIN OF IT_ZSAMP1,
              SNO LIKE ZSAMP1-SNO,
              SNAME LIKE ZSAMP1-SNAME,
           END OF IT_ZSAMP1.
    DATA : INT_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE.
    DATA : INT_CONTROL_RECORD LIKE EDIDC.
    DATA : INT_COMM_IDOC LIKE EDIDC OCCURS 0 WITH HEADER LINE.
    *3.     Select the data from corresponding tables into internal table for a defined condition.
    SELECT SINGLE SNO SNAME FROM ZSAMP1 INTO CORRESPONDING FIELDS OF IT_ZSAMP1 WHERE SNO = P_SNO.
    *4.     create control record into internal table.
    INT_CONTROL_RECORD-MESTYP = P_MESTYP.
    INT_CONTROL_RECORD-IDOCTP = C_IDOCTP.
    INT_CONTROL_RECORD-RCVPRT = 'LS'.
    INT_CONTROL_RECORD-RCVPRN = P_LOGSYS.
    *5.     create data record into internal table.
    INT_EDIDD-SEGNAM =   C_SEGMENT.
    INT_EDIDD-SDATA =    IT_ZSAMP1.
    APPEND INT_EDIDD.
    *6.     Process ALE Service Layer using the function module  MASTER_IDOC_DISTRIBUTE.
    It returns the corresponding IDoc No.s.
    CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
      EXPORTING
        master_idoc_control                  = INT_CONTROL_RECORD
      tables
        communication_idoc_control           = INT_COMM_IDOC
        master_idoc_data                     = INT_EDIDD
    EXCEPTIONS
       ERROR_IN_IDOC_CONTROL                = 1
       ERROR_WRITING_IDOC_STATUS            = 2
       ERROR_IN_IDOC_DATA                   = 3
       SENDING_LOGICAL_SYSTEM_UNKNOWN       = 4
       OTHERS                               = 5
    IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
             WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    *7.     Display Communication IDocs.
    LOOP AT INT_COMM_IDOC.
      WRITE : / 'Communication IDoc No. is : ', INT_COMM_IDOC-DOCNUM.
    ENDLOOP.
    *8.     Commit Work.
    COMMIT WORK.
    IN INBOUND SIDE :
    FUNCTION ZL_IDOC_INPUT_MATMAS_MDM.
    ""Local interface:
    *"  IMPORTING
    *"     VALUE(INPUT_METHOD) LIKE  BDWFAP_PAR-INPUTMETHD
    *"     VALUE(MASS_PROCESSING) LIKE  BDWFAP_PAR-MASS_PROC
    *"  EXPORTING
    *"     VALUE(WORKFLOW_RESULT) LIKE  BDWF_PARAM-RESULT
    *"     VALUE(APPLICATION_VARIABLE) LIKE  BDWF_PARAM-APPL_VAR
    *"     VALUE(IN_UPDATE_TASK) LIKE  BDWFAP_PAR-UPDATETASK
    *"     VALUE(CALL_TRANSACTION_DONE) LIKE  BDWFAP_PAR-CALLTRANS
    *"  TABLES
    *"      IDOC_CONTRL STRUCTURE  EDIDC
    *"      IDOC_DATA STRUCTURE  EDIDD
    *"      IDOC_STATUS STRUCTURE  BDIDOCSTAT
    *"      RETURN_VARIABLES STRUCTURE  BDWFRETVAR
    *"      SERIALIZATION_INFO STRUCTURE  BDI_SER
    *"  EXCEPTIONS
    *"      WRONG_FUNCTION_CALLED
    *"      OTHER_EXC
    *1.     Call workflow include program MBDCONWF.
    INCLUDE MBDCONWF.
    *2.     Create Data Objects for segment(s) and DB Table.
    TABLES : ZSAMP1.
    DATA : FS_SHDR_DATA LIKE ZSEG1.
    DATA : FS_APP_SDET LIKE ZSAMP1.
    *3.     Raise the exception if the message type is not ZMSG1.
    IF IDOC_CONTRL-MESTYP NE 'ZMSG1'.
      RAISE WRONG_FUNCTION_CALLED.
      CLEAR FS_APP_SDET.
    ENDIF.
    *4.     Process Each segment in the IDoc.
    LOOP AT IDOC_CONTRL.
      LOOP AT IDOC_DATA WHERE DOCNUM EQ IDOC_CONTRL-DOCNUM.
        CASE IDOC_DATA-SEGNAM.
          WHEN 'ZSEG1'.
            FS_SHDR_DATA = IDOC_DATA-SDATA.
           MOVE-CORRESPONDING FS_SHDR_DATA TO FS_APP_SDET.
             FS_APP_SDET-mandt = '000'.
             FS_APP_SDET-sno = FS_SHDR_DATA-zsno.
             FS_APP_SDET-sname = FS_SHDR_DATA-zsname.
        ENDCASE.
      ENDLOOP.
    5.     If the data already exists update the data or else insert the data.
      SELECT SINGLE * FROM ZSAMP1 WHERE SNO EQ FS_APP_SDET-SNO.
        IF SY-SUBRC NE 0.
          INSERT INTO ZSAMP1 VALUES FS_APP_SDET.
          ELSE.
            UPDATE ZSAMP1 FROM FS_APP_SDET.
        ENDIF.
    *6.     If the data successfully posted maintain status as 53 or if unsuccessful give status as 51.
        IF SY-SUBRC EQ 0 .
         POPULATE RETURN VARIABLES FOR SUCCESS.
            RETURN_VARIABLES-WF_PARAM      = 'PROCESSED_IDOCS'.
            RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
            APPEND RETURN_VARIABLES.
         ADD STATUS RECORD INDICATES SUCCESS.
            IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
            IDOC_STATUS-STATUS = '53'.
            IDOC_STATUS-MSGTY  = 'I'.
            IDOC_STATUS-MSGID  = 'ZM'.
            IDOC_STATUS-MSGNO  = '006'.
            IDOC_STATUS-MSGV1  = FS_APP_SDET-SNO.
            APPEND IDOC_STATUS.
            ELSE.
           POPULATE RETURN VARIABLES FOR ERROR.
              RETURN_VARIABLES-WF_PARAM      = 'ERROR_IDOCS'.
              RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
              APPEND RETURN_VARIABLES.
           ADD STATUS RECORD INDICATES ERROR.
              IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
              IDOC_STATUS-STATUS = '51'.
              IDOC_STATUS-MSGTY  = 'E'.
              IDOC_STATUS-MSGID  = 'ZM'.
              IDOC_STATUS-MSGNO  = '007'.
              IDOC_STATUS-MSGV1  = FS_APP_SDET-SNO.
              APPEND IDOC_STATUS.
       ENDIF.
    ENDLOOP.
    ENDFUNCTION.
    These are sample code for custom idoc...i did this for customized tables..change this according to your requirement.
    Reward if it useful..
    Lakshmi.
    Edited by: lakshmi matti on May 26, 2008 11:05 AM

  • Custom IDoc & ALE AUDIT

    All,
    I have custom IDoc send data out to SAP XI and SAP XI will send to some third party.
    My question is
    1). Can i use ALEAUD01 message type to configure the ALEAUDIT for return confirmation from SAP XI after updation of third party.
    2). I need steps or any document related to how to configure ALEAUDIT IDoc (Inbound)

    Hey,
    U have plenty of blogs and XI forum posts to how to handle IDOC acknowledgements. But then, you may like to have a look at this:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb
    Thanks
    Kiran

  • LDAP users Faicng Error While Accessing the ESS Iviews in Portal

    Hi,
    My Portal is SAP EP 7.0 SP20 And ECC 6.0 SP16.
    UME users able to access the ESS MSS Iviews.But only one LDAP User only access ESS/MSS Iviews Other getting the Below error.
    Critical Error
    A critical error has occured. Processing of the service had to be terminated. Unsaved data has been lost.     
    Please contact your system administrator     
    Syntax error in program CL_XSS_CAT_BUFFER=============CP        ., error key: RFC_ERROR_SYSTEM_FAILURE     
    Syntax error in program CL_XSS_CAT_BUFFER=============CP        ., error key: RFC_ERROR_SYSTEM_FAILURE:
    com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Syntax error in program CL_XSS_CAT_BUFFER=============CP        ., error key: RFC_ERROR_SYSTEM_FAILURE
                    at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
                    at com.sap.xss.ser.xssmenu.fc.ModelHandler.onInit(ModelHandler.java:205)
                    at com.sap.xss.ser.xssmenu.fc.wdp.InternalModelHandler.onInit(InternalModelHandler.java:428)
                    at com.sap.xss.ser.xssmenu.fc.FcXssMenu.setPersonnelNumber(FcXssMenu.java:570)
                    at com.sap.xss.ser.xssmenu.fc.FcXssMenu.onInit(FcXssMenu.java:292)
                    at com.sap.xss.ser.xssmenu.fc.wdp.InternalFcXssMenu.onInit(InternalFcXssMenu.java:455)
                    at com.sap.xss.ser.xssmenu.fc.FcXssMenuInterface.onInit(FcXssMenuInterface.java:165)
                    at com.sap.xss.ser.xssmenu.fc.wdp.InternalFcXssMenuInterface.onInit(InternalFcXssMenuInterface.java:389)
                    at com.sap.xss.ser.xssmenu.fc.wdp.InternalFcXssMenuInterface$External.onInit(InternalFcXssMenuInterface.java:546)
                    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)
                    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
                    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
                    at com.sap.pcuigp.xssutils.navi.FcNavigation.onInit(FcNavigation.java:314)
                    at com.sap.pcuigp.xssutils.navi.wdp.InternalFcNavigation.onInit(InternalFcNavigation.java:358)
                    at com.sap.pcuigp.xssutils.navi.FcNavigationInterface.onInit(FcNavigationInterface.java:145)
                    at com.sap.pcuigp.xssutils.navi.wdp.InternalFcNavigationInterface.onInit(InternalFcNavigationInterface.java:142)
                    at com.sap.pcuigp.xssutils.navi.wdp.InternalFcNavigationInterface$External.onInit(InternalFcNavigationInterface.java:278)
                    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)
                    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
                    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
                    at com.sap.pcuigp.xssutils.roadmap.VcRoadmap.onInit(VcRoadmap.java:188)
                    at com.sap.pcuigp.xssutils.roadmap.wdp.InternalVcRoadmap.onInit(InternalVcRoadmap.java:162)
                    at com.sap.pcuigp.xssutils.roadmap.VcRoadmapInterface.onInit(VcRoadmapInterface.java:153)
                    at com.sap.pcuigp.xssutils.roadmap.wdp.InternalVcRoadmapInterface.onInit(InternalVcRoadmapInterface.java:144)
                    at com.sap.pcuigp.xssutils.roadmap.wdp.InternalVcRoadmapInterface$External.onInit(InternalVcRoadmapInterface.java:220)
                    at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
                    at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
                    at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196)
                    at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
                    at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
                    at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
                    at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
                    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
                    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
                    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:782)
                    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:302)
                    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
                    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
                    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
                    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
                    at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
                    at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:869)
                    at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:229)
                    at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1344)
                    at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356)
                    at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
                    at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:193)
                    at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
                    at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
                    at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
                    at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
                    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
                    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
                    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:782)
                    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:302)
                    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
                    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
                    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
                    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
                    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
                    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
                    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
                    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
                    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
                    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
                    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
                    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
                    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
                    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
                    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
                    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
                    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
                    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
                    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                    at java.security.AccessController.doPrivileged(Native Method)
                    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
                    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Caused by: com.sap.aii.proxy.framework.core.BaseProxyException: Syntax error in program CL_XSS_CAT_BUFFER=============CP        ., error key: RFC_ERROR_SYSTEM_FAILURE
                    at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
                    at com.sap.pcuigp.xssutils.xssmenu.model.MenuModel.hrxss_Ser_Getmenudata(MenuModel.java:171)
                    at com.sap.pcuigp.xssutils.xssmenu.model.Hrxss_Ser_Getmenudata_Input.doExecute(Hrxss_Ser_Getmenudata_Input.java:137)
                    at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
                    ... 76 more
    Thanks & Regrads,
    Subba Rao

    Hi,
    Now every user facing the same error while accessing ESS Iviews from Portal.
    in ST22 Dump is created.
    What happened?                                                                                |
    Error in the ABAP Application Program
    The current ABAP program "CL_XSS_CAT_TIME_SHEET=========CP" had to be
    terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program
    "CL_XSS_CAT_BUFFER=============CP " in include
    "CL_XSS_CAT_BUFFER=============CM00C " in
    line 50:
    ""L_CATSDB" and "L_CATSDBCOMM" are not mutually convertible. In Unicode"
    " programs, "L_CATSDB" must have the same structure layout as "L_CATSDB"
    "COMM", independent of the length of a Unicode character."
    The include has been created and last changed by:
    Created by: "SAP "
    Last changed by: "SAP "
    Error in the ABAP Application Program
    The current ABAP program "CL_XSS_CAT_TIME_SHEET=========CP" had to be
    terminated because it has
    |    come across a statement that unfortunately cannot be executed.
    What we need to resolve the above issue.
    Thanks & Regards,
    Subba Rao

  • Issue with the configuration of http xml port for sending the idoc

    Hello,
          I am planning to send multiple idocs in a single file using http xml port.
    Presently I am trying to send a single idoc, but am having the issue.
    I am trying to create a RFC for HTTP XML port of type H i.e. HTTP Connection to ABAP System
    In the how to guide for - How Tou2026 Send Multiple IDocs Within One XI Message
    ( https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30ea2fdf-f047-2a10-d3a2-955a634bde6b )
    the following parameters are defined for the path prefix -
    RFC destination of type H (HTTP Connection to R/3 System).
    Specify the path prefix as follows:
    /sap/xi/adapter_plain/
    ?namespace=< your namespace>
    &interface=<IDoc_Type>
    &service=<Sender System>
    &qos=EO (or EOIO).
    I am trying to use the following prefix -
    /sap/xi/adapter_plain/
    ?namespace=urn:sap-com:document:sap:idoc:messages ( this is the standard namespace of SAP for all the idocs)
    &interface=DEBMAS05 (Idoc type )
    &service=SNDLS100 ( ECC system name )
    &qos=EOIO
    On testing the RFC connection, I am getting the error of page not found.
    Can anyone please give me pointers for the issue.
    Regards,
    Mayank

    Thanks Barry!!!
    Now I am getting a different message.
    In RFC...it is giving me the following message ->
    Status HTTP Response     204
    Status Text     Body is empty
    In case of Idoc, the status is till 02...
    the error description for the idoc is --
    "When transferring the IDoc by HTTP, the return code with the message '500<SAP:Error><SAP:Category>XIServer</SAP:Category><S' has occurred.
    The target address was: http://emgeccsnd1:8001/sap/xi/adapter_plain/?namespace=urn:sap-com:document:sap:idoc:messages&interf
    Check whether the IDoc can be sent again.
    It is unfortunately not possible to determine automatically whether the IDoc has in fact arrived in the target system and the error occurred afterwards"
    I am still not able to resolve the issue.
    Regards,
    Mayank

  • Development of custom IDOC's

    Hi All,
    Can we go for approach of developing custom IDOC's? where in our scenarios are getting files from thrid party and updating data in file  into ECC.
    Approach towards Custom IDOC's is for error monitoring and recprocessing.
    Would request your inputs and suggesions in this regard.
    Is that good approach for going to custom idocs? if not why?
    Thanks,
    chandra.

    Hi,
    SAP R/3 systems send out data through IDoc (Intermediate Document), which in internally has segments and fields containing the data. But sometimes, these fields are not sufficient for a specific end-to-end business scenario as far as data transfer is concerned. So in such scenario, either few fields are to be added or subtracted, or completely new structure- IDoc needs to be created.
    At times because of the business scenario we do have to create Custom idocs .
    Regards,
    Bhanu

  • Trigger custom idoc through ALV when sales order is created in VA01 & VA02

    Dear Experts,
    I am new to the concept of ALV_idoc. Please give me the procedure in detail.
    How to send custom fields to non SAP system when sales order is created or modified in VA01 &VA02?
    Can i use existing Logical Systems and Ports and partner profiles?
    Thanks & Regards
    Moderator message: please search for available information/documentation.
    Edited by: Thomas Zloch on Jan 17, 2012

    hi,
    the first option is the right one. the FM invoked makes a direct input, so all the functionalities in S.O. are the standard one in the same way as if you are making it manually.
    Also you can have some exits in the Idoc FM, so you can manipulate data there before loading the sales order.
    pls. reward if helpful
    regards
    Roberto

  • Send Customer Payment document to external application.

    Dear All,
    I am working on one of our customer requirement to send Customer Payment data from SAP ECC 6.0 to their application using SAP PI 7.0
    I have created a customer Invoice (in Transaction Code FB70)  without any reference document .
    Now I want to generate a Customer payment document on the top of Customer Invoice generated as mentioned above.
    Can any one please suggest the following:
    1) Can we generate Customer payment document in transaction FII0
    2) What are the mandatory parameters to generate Customer payment document.
    3) If I need to send this data to external application using IDOCs , so can i use Program RFFOEDI1 as suggested in other threads.
        what are the parameters needs to given to run the program?
    4) How to configure the our output type so whenever we generate a Customer payment document, an IDOC should be genarated.
    Also please confirm if I can use IDOC PAYEXT with basic type PEXR2001 or should I go for some other IDOC.
    Best Regards
    Honey
    Edited by: Honey Gyanani on Jun 29, 2009 7:19 AM

    I have posted the same Question in ERP Financials and got the answer.
    Honey...

  • Is it possible to use BAPI-ALE to send an idoc using the message control?

    Hi Guys
    Is it possible to use BAPi-ALE to send an IDOC using a message control?
    I have configured the system to send an IDOC when a outbound delivery is saved in the system.
    I have done the following.
    1). I am using the std BAPI-ALE interface provided by the object type LIKP.
    2). I am using the method SAVEREPLICA for which an interface already exists in BDBG transaction.
    3). I hace created a distribution model in BD64 and added the BAPI - LIKP and SAVEREPLICA
    4). Created a partner profile ( using the generate partner profile option in the BD64 transaction )
    QUESTION:
    1). How do i associate the custom OUTPUT type created for Delivery ?
    2). I tried to associate the custom output type in the Partner profile definition under the message control tab but i am not sure which Process code to be used? Since the partner profile was generated automatically from BD64 it has an entry for SHP_OBDLV_SAVE_REPLICA as a message type in the outbound parameters. and i am unable to find a process code for this Message type in WE41. So what process code should i use in the Message control tab against the custom output type?
    3). Do i need to leave the message control tab empty without making any entry? If yes then how would the system come to know that it needs to trigger this partner profile when the custom output type is proposed by the system?
    will award points for useful answers
    Edited by: Workflow  learner on May 29, 2008 8:49 PM

    "any way"
    Applications such as ScreenRecycler, http://www.screenrecycler.com/ScreenRecycler.html, can do it.

  • Send customer documents to different application

    Hello all,
    We have a need to send customer invoices to an external applocation via IDOCs. We need to send an invoice as soon as it is generated and also when a payment is recieved against a customer invoice for a particulat customer group. We genrate customer invoices through batch program. any idea how this can be done. I've ABAP experience but no IDOC experience whatsover. I would greatly appreciate if you can tell me how can this be acheived and what are the steps that are involved. Any pointers to  online documentation will also be much appreciated.
    Thanking you all in anticipation.
    Regards,
    Rajani

    Hi All,
    I was successfully able to send IDOCs to another system, but I would like to filter the IDOCs based on G/L account. Can anyone ple..............ase tell me how to create filter objects. We are on ECC6.
    Prompt responses will be greatly appreciated.
    Thanking you in anticipation.
    Regards,
    Rajani

  • Inbound function module for  custom IDOC

    HI,
    I have created custom IDOC.I need to create inbound function module for that custom IDOC.Can any one send me sample
    function module for custom IDOC.(what are all the import Export,tables  parameters and exceptions  that I need  to create for function module)
    Thanks&Regards
    Rama.Mekala

    HI Rama,
    I presumed that You are talking about a FM to create inbound IDOC. So for creating inbound IDOC you can use '
        CALL FUNCTION 'IDOC_INBOUND_ASYNCHRONOUS'
        TABLES
          idoc_control_rec_40 = gt_edidc
          idoc_data_rec_40    = gt_edidd.
      IF sy-subrc NE 0.
    *    MESSAGE e000 WITH text-003.
    *  ELSE.
    *    MESSAGE i000 WITH text-004  .
      ENDIF.
    just prepare edidc and edidd record in and pass it to the FM..
    Hope this will work for you...
    Thanks

  • Urgent: Sending order05 IDOC from R/3 to ICH (SAP SCM) through SAP XI

    Hi All
    I have requirement where I have to send Order05 IDOC from SAP R/3 (ECC 6) to ICH (SAP SCM 5) through SAP XI (PI 7).
    I came to know that there is one standard scenario in SAP SCM Basis content in integration repository.
    I never done any XI development, please guide me with the useful links or whole step by step process. I will be very thankful for your inputs.
    Please reply asap.
    Regards,
    Amol

    Hi !
    Check this note:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_xi/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d383336323030%7d
    Regards,
    Matias.

  • Error in Inbound Customer IDOC (WE19)

    Hi All
    I am creating Inbound Customer IDOC
    Message Type : DEBMAS
    & FM : IDOC_INPUT_DEBITOR.
    But getting error(51) : "No batch input data for screen SAPMF02D 0340".
    According to previous threads, I have seen this screen for Mandatory fields but I didnt found any.
    Could anyone tell me what mandatory fields to enter in DEBMAS or  the Solution for this Error.
    Regards.

    Hi Nikhil I am getting this error which you got it before but this time I am getting it in LSMW when creating customer master screen."No batch input data for screen SAPMF02D 0340"
    what am i supposed to check?
    Can u plz send me ur mail ID.

Maybe you are looking for

  • Please help - Safari crashing every time I open it

    Guys for months now I've been unable to open Safari. It loads then the I get the spinning beach ball and it crashes. Every time. I did an archive and re-install but it didn't help. Using Safari 3.0.4 with Macbook 10.4.11 Date/Time: 2008-02-02 14:47:2

  • Importing photos from iPhoto to Aperture

    Importing from cd, Nikon camera, and cf memory card to Aperture Library is working well for me; but importing from iPhoto is troublesome. If I import from the iPhoto Library (a Library that has always seemed unnecessarily complex to me), there is nei

  • Best Java JRE for OS X 10.5.X?

    Is there a recommended Java version for OS X 10.5.X?

  • Sort photos

    Can someone tell me how to resort photos in an album on iPad air? Tried to drop and drag but that doesn't work.  Any way to name each photo? Thanks. The photos are all screenshots taken on the iPad.

  • Material Data Extend to New Plant

    Hi, This is understandable how to extend data to new plant; however, is there any way material master can be extended with whole range or material group or material can be extended individually only. Thanks