Out bound interface

Hi all
iam having scenario , where i have select some data  from SAP tables to other system using Interface . So i need to put this data in a File at application sever . From here , the data will proceeds to other system.
When our interface triggers it will undergo certain data mapping and translation rules. Once the data mapping is done SAP will generate data in a fixed delineated format which will then uploaded or read by the other system iterface. This part iam unable to understood?
Give me how i need to proceed for the above cases.
regards
venkat

Use fnd_profile.value (your_profile_name) in your code.
Hope this answers your question
Sandeep Gandhi

Similar Messages

  • In-Bound & Out-bound interfaces list of GL, AP & PO modules

    Hi,
    GoodDay, I'm working with GL, AP & PO modules. Please let me know both In-bound and Out-bound interfaces list of those three modules.
    Regards,
    Ram.

    For 11i, these are listed at http://irep.oracle.com
    HTH
    Srini Chavali

  • For inbound and out bound interface

    what is inbound interface and outbound interface.what is diff b/w inbound and outbound interface.
    thnx

    Hi,
    The interface through which data comes inside SAP is inbound interface on the other hand the interface through which data goes out of SAP is called outbound interface.
    Rgds
    Mayank

  • Out bound interface (SAP to other system)

    Hi all
    iam having scenario , where i have to select some data from SAP tables and i need to put this data in a File at application sever . From here , the data will proceeds to other system.
    When our interface triggers it will undergo certain data mapping and translation rules. Once the data mapping is done SAP will generate data in a fixed delineated format which will then uploaded or read by the other system iterface. This part iam unable to understood?
    tell me how i need to proceed for the above cases.
    regards
    venkat

    Hi,
    After u get the data u can check mapping and translation rules and then finally put the data in application server
    use OPEN DATASET , tranfser the values and then CLOSE DATASET..
    Check the below link..
    http://www.sapdev.co.uk/file/file_uploadsap.htm
    Regards,
    Nagaraj

  • Incoming purchase order  vs out bound goods receipt processing

    Hi
    any body know how to develop an interface for below requrement
    creating an interface for incoming purchase order creation and out bound goods receipt processing
    please let me know anybody knows this
    Thanks in advance,
    Best regards
    Alleiah

    I done Purchase order inbound ...
    you have to set up partner profile at we20 like message type,idoc type,port..
    Message type : orders
    idoc type : orders05,once you done it creates the purchase order,for testing you can use we19 ,enter data manually and you can see the status at we02 or we05 transaction
    Reward Points if it is helpful
    Thanks
    Seshu

  • Out bound IDOC creation

    Hi experts,
    I am given a task to create an out bound IDOC which would be input to TIBCO, which must be triggered every time Good issue transaction is completed by either VT02N or VL02N transaction up pressing SAVE.
    IDOC is to have fields from Customize tables apart from standard SAP tables, so was asked to create an own IDOC ( eg: Z--Idoc).
    Please tell me how to create the idoc, and also the method to trigger it and how to populate the IDOC ( program etc).
    Use full inputs would be promtly rewarded.
    Regards,
    Ram.

    Hi
    Creation of Custom IDOc type and message Type
    First Create Partner Profile(WE20 Tcode) and Port Definition in WE19 Tcodes.
    take the Basis help to create them.
    1.First create segments in WE31 Tcode with the required dataelements
    2.Create the Basic Idoc Type in WE30
       release the Segments and IDOC type.
    3.Create Message type in We81
    4.Assign the message type to IDOC type in WE82 T code
    5.Create the process code in We41 (for Outbound) WE42 (for Inbound)
    6.Create A fun module in SE37 starting with ZIDOC_OUTPUT_.. by copying some Inbound (for    Inbound) Outbound Fun module
    7.Create  Workflow setting if needed ..
    8. Assign the fun module to Idoc Type, Message Type and WF object (if it is there0
    9.Define setting for fun module in BD51
    10.In BD51 Define the settings for Fun module..
    10.Assign the Processs Code to Fun mod`ule
    Outbound Interface
    PROCESS DIAGRAM for Outbound Interface
    1. Analyse Hierarchy Levels
    2. Create New segment
    3. Create New IDoc Type
    4. Create New Message Type
    5. Link Message with IDoc Type
    6. Create an entry in EDP13 via transactions WE20 and BD64
    7. Populate the Custom IDoc via ABAP Program
    7b Error Handling
    7c. Send Status Email
    8. Test the Population of the Custom IDoc
    Step 1 – Analyse Hierarchy Levels:
    Analyse the data relationships being processed in the interface. Define the appropriate hierarchical Parent-to-Child relationships.
    Navigate to transaction code WEDI
    Transaction WEDI displays the IDOC main menu. This allows navigation around the various development and control areas to create a customised IDOC.
    Step 2 – Create a new segment:
    via wedi : Development - IDOC Segments or Transaction code WE31.
    • Enter segment name and click on Create.
    ? The name of the segment type must start with Z1 , and have a maximum of eight characters.
    • Enter description and enter the relevant field names and data elements.
    ? The segment should represent a structure in the program so for each field in the segment a field name and a data element must be defined.
    • Save the segment and enter Person Responsible and Processing Person .
    • Go to Edit and Set Release.
    • Repeat this procedure for each new Segment in the IDOC.
    Step 3 – Create a new IDOC Type
    via wedi Development - IDOC Types or Transaction WE30.
    • Enter segment name (starting with Z), click on Basic Type and then Create.
    • Create as new, enter Person Responsible and Processing Person and enter description.
    • On ‘Create Basic Type’ screen decide where segments should be inserted and go to Edit/Create Segment.
    • Complete relevant fields in the Maintain Attributes screen:
    • From the relevant segments created in Step 2 enter the Segment type and if mandatory segment.
    • The Minimum and Maximum number of segments to be allowed in the sequence. (One minimum and one maximum if segment is mandatory).
    • The Parent Segment and Hierarchy Level will be automatically created depending on where in the IDOC tree you decided to create that particular segment.
    • Repeat this process for each segment needed in the IDOC type, deciding whether to add the next segments at the same level or as a ‘Child’.
    • When IDOC created return to initial screen. Go to Edit and Set Release.
    • Go to Transaction WE60 to view the IDoc Type you have created.
    Step 4 – Create new Message Type
    via wedi Development - Message Types or Transaction WE81.
    • Display/Change and click on New Entries
    • Create a new Message Type and Save.
    Step 5 – Link Message Type to IDOC Type
    via wedi Development - IDOC Type/Message or Transaction WE82.
    • Display/Change and then click on New Entries.
    • Enter Message Type, Basic Type (IDOC Type) and Release (46C) and Save.
    Step 6 – Create an entry in EDP13 via transactions WE20 and BD64.
    The partner profile for the Idoc must be set up and generated in the transaction BD64 and transaction WE20.
    • WE20 – Add Message Type to appropriate Partner Type, Enter Message Type, Receiver Port and Idoc Type and Save.
    • BD64 – Create a Model View, Enter Sender and Receiver Ports, Attach Message Type. Go to ‘Environment’ on Menu and click on Generate Partner Profiles and generate (not save) profile.
    Step 7 – Populate the custom IDOC via ABAP Program
    See Test Program ZOUTBD_IDOC_TEMPLATE, Appendix IV.
    • Create an Internal Table for each segment type, this should be exactly the same structure as the segment type.
    • The control record is filled into a structure like EDIDC. The message type and the Idoc type for the Idoc must be populated into the eddic structure.
    - PERFORM populate_Control_structure USING c_mestyp
    c_SEGMENT_type1.
    • The data segments are filled into a structure like edidd-sdata; sdata and the segment name are populated into the edidd structure.
    - PERFORM transfer_Parent_data_to_seg.
    • The standard SAP function module MASTER_IDOC_DISTRIBUTE is called to pass the populated IDOC to the ALE Layer.
    - PERFORM master_idoc_distribute.
    • NOTE: This function module is only called for stand alone programs and Shared Master Data programs (SMD). It is not called when using extensions or output determination.
    • The ALE Layer handles the sending of the IDOC to the receiving system.
    • Error Handling (see Step 7b).
    • Commit work.
    Project Specific
    Step 7b – Error Handling• Analyse which fields in the interface are mandatory for the receiving system and who needs to receive error notification.
    • Declare a structure of type ‘MCMAILOBJ’ for sending instructions.
    • Enter values for the internal table based on structure ‘MCMAILOBJ’
    • For selection processes, on SY-SUBRC checks and where fields are mandatory for the receiving system; insert Function Module ‘MC_SEND_MAIL’.
    • Enter values in the following parameters: -
    MS_MAIL_SENDMODE = ‘B’ (Batch Mode)
    MS_MAIL_TITLE = 'Mail Title'
    MS_MAIL_DESCRIPTION = ‘Error description’ (e.g. MATNR not given)
    MS_MAIL_RECEIVER = ‘Name of Receiver’ (To be determined)
    MS_MAIL_EXPRESS = ‘E’ (Express Delivery)
    MS_MAIL_DLINAME = Leave Blank
    MS_MAIL_LANGU = 'E' (Language)
    MS_MAIL_FUNKOBJ_NAME = Leave Blank
    TABLES
    MS_MAIL_CONT = I_MCMAILOBJ
    Note:
    It has to be determined separately for each interface how these errors and mail notifications are to be grouped – dependant upon the number of errors that are potentially likely. One possible approach is to send an email for each reason for rejection and include all the records that failed for that reason in the mail notification. Another possible approach is to send an email for every failure.
    When error checking for mandatory fields it is common SAP practice to reject a record on its first failure (irrespective of subsequent errors in that record)
    Step 7c – Send status mail
    • Append to table I_MCMAILOBJ details of the time the interface was processed, how many Idocs were created and how many of these produced a status of 03.
    • Select the user to receive the mail from ZINT_RECEIVER, using the name of the program as a key (SY-CPROG).
    • Use function Module ‘MC_SEND_MAIL’ to send a mail to the user containing the contents of I_MCMAILOBJ at the end of the interface processing.
    Step 8 – Test the population of the custom IDOC
    via wedi IDoc - Display IDoc or Transaction WE02.
    • Enter your message type and execute.
    • Status should be green, double click on one of the Idocs you have created to view its contents.
    • If a problem has occurred click on Status which will give you a description of the error.
    • Drop down Data Records arrow and this should list the data in the IDoc in the correct hierarchical structure.
    • Click on each individual segment and view the content to check that the correct data has been read.
    • If you have UNIX access by using AL11 you can view the file that you have created.
    Note:
    For some interfaces it may be valid to send an empty file to SAP. This empty file is converted to the custom IDOC format expected by SAP. This custom IDOC will contain dummy information. In the inbound processing code, if the dummy information is identified then the processing of the IDOC is considered to be complete and the IDOC should then be assigned a successfully processed status of 53, even though it has not been processed at all.
    Regards
    Anji

  • How 2 Copy Header & Line Item Text from Purchase Order 2 Out Bound Delivery

    Hi SD Gurus,
    I want to copy header and line item text from Purchase Order to Out Bound Delivery (This is required in Stock Transfer Process).
    I have been able to do successful config. for copying header and line item text from Sales Order to Outbound Delivery but config. doesn't seems to be same for copying text from PO to OBD.
    Is there any way to achieve the same? Can some expert show the way to achieve this.
    Thanks in advance.
    Warm regards,
    Rahul Mishra

    Hi Ravikumar thanks for u quick reply.
    This is wht is currently coded.
    concatenate values to get item text for read text function
       invar3+0(10) = invar1. "PO number
       invar3+10(5) = invar2. "PO line number
       SELECT SINGLE * FROM stxh WHERE tdobject = 'EKPO'
                                   AND tdname   = invar3
                                   AND tdid     = 'F01'
                                   AND tdspras  = sy-langu.
       IF sy-subrc = 0.
         invar4 = invar3.
    reading the text for the document items.
         CALL FUNCTION 'READ_TEXT'
           EXPORTING
             id       = 'F01'
             language = sy-langu
             name     = invar4
             object   = 'EKPO'
           TABLES
             lines    = it_itab.
    I have seen some PO's which have info rec texts in that, which gets pulled by the above code...first thing is its id is F02 which exist in STXH table also there is other text with F01 id, and hence the table it_itab gets both these text hence no pbm.
    but i came across a PO which has only one text which is info rec text with id F05 and is not store in stxh and hence doesnot get pulled by read_text fm. How do i change my cod to get this text which should not hamper other PO's as well.
    As mentioned in above msgs, this F05 could be retrieved by providing object name as EINE.
    anyhelp will be appreciated and rewarded.
    thanks

  • Out Bound IDOC Status 03

    Hi,
    Can any one let me know about the out bound IDOC ststuses.
    In our system the Out bOund IDOC's are being in status 03, they are not moving to 12. Can any one please let me know why it is not moving to status 12.
    Regards,
    Ravi G

    Hi
    Please execute RBDMOIND program you will get change status 03 to 12
    Thanks,
    Murali

  • Video out Ipad interface screen

    How can I use the iPad to project out the interface screen with the video out cable ? Is there an app I can use to do so ?

    This is not an option. VGA out only works within applications, and then only those that support is, like Keynote, NetFlix, a few browsers etc. Safari will not even project, I use Expedition.

  • Change batch header of out bound ACH payment file??

    Hi all,
    Currently in the batch header of settlement file for all processed ACH transactions, we are using PPD(Prearranged Payment and Deposit Entry) as standard entry class code for all type of CA's(residential and business)
    we need to change in the batch header of the out bound ACH payment file as....PPD for residential customer and CCD(Cash Concentration & Disbursement) for commercial  customer...
    The batch is consisting of the programs SAPFKPY3  and RFKPYL00_MASS.
    please suggest how can we change the batch header of the out boun file.
    Any help appreciate..

    Srinivas-
    That field in company batch header with record type is called "effective entry date". Please look at the attached thread.
    Effective Entry Date
    Shail

  • Out bound delivery for STO

    Hi
    In stock transfer order in delivery tab part Del/Item tab it is mentioned "B" means it will create only one outbound delivery  for sto. if stock is not available it will create deliver y with quantity 0.
    But for 1  sto it has created 3 out bound deliveries.
    Why it is happened?
    Thanks,
    Kiran

    Hi
    To check the possible reasons of splitting, see these notes:
    SAP Note 166397 - Delivery split according to customer field ZUKRL
    SAP Note 546668 - FAQ: Delivery split when creating deliveries
    I hope this helps you
    Regards
    Eduardo

  • Out bound delivery against STO

    Hi
    My client requirement is to trace every movement against STO i-e system should track each GR against each GI against STO.
    Meaning when we issue a goods against STO system should track against which GI user post GR as in the system there is no standard available to track this activity.
    We will see a possibility that the we have posted a outbound delivery against STO and the GOODS ISSUE and similarly do the inbound delivery and then GR against STO this is the only way to track the Goods Receipts against Good Issue.
    It is only suggestions kindly correct me if I am wrong and one more help how the system create out bound delivery against STO.
    Regards,
    Tahir

    HI,
    Whatever you mention is correct

  • Idoc Status error 29 for Out bound Idoc( Receiver of IDoc is its own logic)

    I try to create the Out bound Idoc with messag type WMMBXY ( basic Idoc type - WMMBID02 ).
    which is configured with the out put type XXXX in VT01N( shippment creation). But I am getting the error status 29 in the Idoc.
    Only I am passing the sender, receiver port , partner type and partner function to the communication structure.
    Could you please tell me , what is the issue with the partner type configuration .

    Hi,
    Error 29 occurs when there is an incomplete or no partner profile maintained.
    Check whether you have done the correct partner profile settings in WE20 outbound parameters.
    For the partner no defined in Idoc check whether there is an entry(under partner type LI, KU or LS)
    with correct message type WMMBXY  and Idoc type WMMBID02. Also check for message function code.
    Regards,
    Savitha

  • Out Bound Function Module For IDoc Types CODCMT01

    Hi Experts,
        Can you please tell me the Out Bound Function Module For IDoc Types CODCMT01,CODCAGN01,PRCDOC01.
    Thanks..
    Debi.

    Hi Debi,
    You can use FM MASTER_IDOC_DISTRIBUTE to distribute outbound IDoc CODCMT01, CODCAGN01 and PRCDOC01.
    Regards,
    Ferry Lianto

  • Out Bound / In Bound IDOC Succes full status in R3

    Hi Frnds,
    I am sending IDOC from OUT BOUND.
    Its succes full wts the Status in R/3 12 or 3. How to check in R/3.
    I am sending IDOC from IN BOUND.
    Its succes full wts the Status in R/3 ??. How to check in R/3.
    Can any one explain the process..
    Regards,
    Raj

    Hi,
    Outbound IDOCs
    Code      Error      Event Severity      SAP Meaning
    02      Yes      Error      Error passing data to port
    03      No      Error if transaction SM58 indicates an RFC transmission error      Data pass to port OK
    04      Yes      Error      Control information of EDI subsystem
    05      Yes      Error      Translation
    06      No      Harmless      Translation
    07      Yes      Error      Syntax check
    08      No      Harmless      Syntax check
    09      Yes      Error      Interchange handling
    10      No      Harmless      Interchange handling
    11      Yes      Error      Dispatch
    12, 13, 14      No      Harmless      OK
    15      Yes      Warning      Interchange acknowledgement negative
    16      No      Harmless      Functional acknowledgement
    17      Yes      Warning      Functional acknowledgement negative
    18      No      Harmless      Triggering EDI subsystem
    20      Yes      Error      Triggering EDI subsystem
    22      No      Harmless      Dispatch OK, acknowledgement still due
    23      Yes      Error      Retransmission
    24      No      Harmless      Control information of EDI subsystem
    25      Yes      Warning      Processing despite syntax error
    26      Yes      Error      Syntax check
    27      Yes      Error      ALE error
    29      Yes      Error      Error in ALE services
    30      No      Harmless      Ready for dispatch (ALE)
    31      No      Harmless      IDOC is marked for deletion
    33      No      Harmless      Original of an IDOC which was edited
    34      Yes      Error      Error in control record of IDOC
    36      Yes      Error      Timeout error; electronic signature not performed
    37      Yes      Error      IDOC added incorrectly
    38      No      Harmless      IDOC archived
    39      No      Harmless      Receive confirmed
    40      Yes      Error      Application document not created in target system
    41      No      Harmless      Application document created in target document
    Inbound IDOCs
    Code      Error      Event Severity      SAP Meaning
    51, 52      Yes      Error      Posting error
    53      No      Harmless      Posting successful
    54      Yes      Error      Error during formal application check
    55      No      Harmless      Formal application check
    56      Yes      Error      IDOC with error added
    60      Yes      Error      Syntax error
    61      Yes      Warning      Processing despite syntax error
    62      No      Harmless      IDOC passed to application
    63      Yes      Error      Error passing IDOC to application
    64      No      Harmless      IDOC ready to be passed to application
    65      Yes      Error      ALE error
    68      No      Harmless      IDOC is marked for deletion
    70      No      Harmless      Original of an IDOC which was edited
    73      No      Harmless      IDOC archived
    Regards
    Seshagiri

Maybe you are looking for