ALE output in Backend

Hi All,
I need to send out the PO created from SRM via ORDERS IDoc to a B2B hub Middleware system. I have configured everything in R/3. Its working for the PO's being created in R/3 but not the PO's being created from SRM. Please help. Am I missing any config in SRM or R/3?
BTW: We have SRM 4.0 Extended Classic Scenario
     And ECC 5.0
Thanks in advance.

Hello,
You should check the messaging part in the R/3.
A condition record missing ?
Any realease strategy in the backend ?
A check you can do is to create manually an ale message for a PO coming from SRM. It can give you some information on what is missing.
Rgds,
Pierre

Similar Messages

  • Output from backend in extended classic

    Hi Experts,
    In extended classic scenario it is possible to sent the output from backend?
    Does anyone know have to activate this, and how to deactivate the output control from SRM.
    Proces as I want it:
    - Creates a shopping cart in SRM.
    - Creates a PO in SRM on behalf of the shopping cart, no output.
    - The PO from SRM is replicated to R/3.
    - The PO is sent to vendor fra R/3.
    Best regards
    Kim Oster

    yes franz is correct. we can do this from consulting note which he mentioned.
    PO Output messages for ECS PO's
    br
    muthu

  • EDI/ALE output Post Goods Issue from ME2O

    Dear experts,
    I have to create an outbound IDoc (I assume MBGMCR03) of a Goods issue done with ME2O (mvt type 541).
    So far I have read through:
    http://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=88113280
    http://scn.sap.com/thread/3146742
    http://scn.sap.com/thread/2056081
    but they all talk about printing the message - I need to create an IDoc.
    In NACE:
    - Application "ME"
    - but which condition record can I choose?
    - output types are all set up with print parameters - no EDI/ALE as far as I can see. Do I have to create new ones?
    Can you please help on how to set this up in NACE?
    Next step would be MN21 for the output condition record I assume,
    WE20 to define output for logical system.
    Thank you for your help.
    Best regards,
    Peter

    Dear experts,
    I am a little further now.
    I used output condition WA01 which is already set up in NACE and in MN23 I set up:
    In SP01 I can see the created Spool entries after creating the Good issue with ME2O. So the print out would work. But I need an EDI output....
    I created a new output condition ZWA1 in NACE and set "Processing routines" to EDI.
    I set "Partner functions" to EDI and LS - logical system.
    In MN23 I have:
    I set Event Type to "WA" because when I look at a material document in MB03 it also shows WA:
    In WE20 I have my LS - logicals system and set up the output for MBGMCR03:
    What confuses me is: I have to send the EDI output to a LS - logical system. But in MN23 I can't set the LS - it gives error: "You cannot enter a partner function for output ZWA1"
    No IDoc is created so far - please help. Thank you.
    Best regarsd,
    Peter

  • EDI/ALE-Output type-Process code relation?

    Hi.
    In EDI preocessing the relation between the Message type and the process code is know.
    But where is the realtion of either of these two to the output type?
    When we hit a F4 in the message control in WE20 for process codes it gives us a list.
    How is this linkages established.
    Output type-process code-message type-output routines?
    Please dont answer in vague terms.

    Dear experts,
    I am a little further now.
    I used output condition WA01 which is already set up in NACE and in MN23 I set up:
    In SP01 I can see the created Spool entries after creating the Good issue with ME2O. So the print out would work. But I need an EDI output....
    I created a new output condition ZWA1 in NACE and set "Processing routines" to EDI.
    I set "Partner functions" to EDI and LS - logical system.
    In MN23 I have:
    I set Event Type to "WA" because when I look at a material document in MB03 it also shows WA:
    In WE20 I have my LS - logicals system and set up the output for MBGMCR03:
    What confuses me is: I have to send the EDI output to a LS - logical system. But in MN23 I can't set the LS - it gives error: "You cannot enter a partner function for output ZWA1"
    No IDoc is created so far - please help. Thank you.
    Best regarsd,
    Peter

  • Caching Output from backend drivers

    Hi,
    I am noticing in the trace file that much time is consumed with the following trace note while sending reports to networked printers.
    DST 51103 (rwfdt: rwfdtprint) CachingOutput from the backend drivers.
    I am running oracle 10g release 2 on windows 2003 server platform.
    Any thoughts?
    Thank u.

    Hi,
    I am noticing in the trace file that much time is consumed with the following trace note while sending reports to networked printers.
    DST 51103 (rwfdt: rwfdtprint) CachingOutput from the backend drivers.
    I am running oracle 10g release 2 on windows 2003 server platform.
    Any thoughts?
    Thank u.

  • Error 50103 (rwfdt:rwfdtprint): ERR Error occurred sending Job output

    Getting the below with a particular report I am running. Seems that the cache file isn't getting created for some reason. There are other cache files in the directory so it's not a user permission type thing I'm guessing.
    Anyone seen this before?
    [2007/7/4 2:10:15:431] APP 50103 (rwfdt:rwfdtni_NextInstance): running
    [2007/7/4 2:10:15:431] APP 50103 (rwfdt:rwfdtni_NextInstance): quit
    [2007/7/4 2:10:15:431] APP 50103 (rwfdt:rwfdtgcf_GenCachefile): running
    [2007/7/4 2:10:15:431] APP 50103 (rwfdt:rwfdtgcf_GenCachefile): Cache file is C:\oracle\product\10.2.0\MT\reports\cache\66117201.txt
    [2007/7/4 2:10:15:431] APP 50103 (rwfdt:rwfdtgcf_GenCachefile): quit
    [2007/7/4 2:10:15:431] APP 50103 (rwfdt:rwfdtprint): caching output from backend drivers
    [2007/7/4 2:10:15:431] Error 50103 (rwfdt:rwfdtprint): 14:10:15 ERR Error occurred sending Job output to cache

    Hi,
    Sorry I didn't realize that i didn't answer to this question because of reference to others.
    I solve it with change of values in rwserver.conf
    one of values is default but other solve issue.
    <property value="no" name="keepConnection"/>
    engLife="2"   or    engLife="1"This happens in my env because application often change user (db schema). And this is workaround for restarting engine.
    regards

  • ALE funda doubt

    hi experts,
    First of all let me request you to not answer this question by linking it to some sites or threads.I want its answer written by you in short and brief.
    Why ALE is required??
    Thanks,
    Gaurav

    Hi,
    ALE allows the user to perform an SAP transaction in the sending system, after which the following steps occur:
    1. 1 or more communication IDocs (intermediate documents: container for the application data) are created in the sending system database. An ALE distribution model, that needs to have been configured, determines which systems the IDocs are to be sent
    2.These communication IDocs, that contain the relevant application data of the transaction that was performed, are then passed to the ALE communication layer
    3. This layer performs an RFC call using the port definition and RFC destination determined through the customer model
    4. The IDocs are then transferred to the respective receiving systems. These could be SAP R/3, R/2 or external systems
    5. If the receiving system is an SAP system then:
    -In the case of master data distribution the same transaction that was performed on the sending system is again performed on the receiving system with the data contained in the IDoc. This allows the data to go through the SAP checks before posting occurs
    -In the case of transaction scenarios the relevant data is passed to the respective transactions in order to load the required application document. E.g.. A PO is loaded on the sending side, yet a SO is created on the receiving system
    6. Master data has another difference:
    -It can be set up in such a way that any changes made to specific fields in master data tables can automatically trigger off the ALE distribution process for that particular master data object
    -If a master data object is created or changed on a sending system and distributed to another system the respective transaction is used to either create or change that respective master data object on the receiving system
    In general, if standard SAP can't perform the task required then neither can ALE. It doesn't add functionality, it merely decouples it and allows you to distribute it onto other remote systems.
    The Detail as described by SAP
    In the output processing one of the function modules of the application creates an IDoc, the so-called master IDoc. This IDoc is sent to the ALE layer where the following processing steps are applied:
    Outbound processing
    Receiver determination
    An IDoc is similar to a normal letter in that it has a sender and a receiver. If the receiver has not been explicitly identified by the application, then the ALE layer uses the customer distribution model to help determine the receivers for the message.
    The ALE layer can find out from the model whether any distributed systems should receive the message and, if so, then how many. The result may be that one, several or no receivers at all are found.
    For each of the distributed systems that have been ascertained to be receiver systems, the data that is specified by the filter objects in the customer distribution model is selected from the master IDoc. This data is then used to fill an IDoc, and the appropriate system is entered as receiver.
    Data selection
    Segment filtering
    Individual segments can be deleted from the IDoc before dispatch by selecting Functions for the IDoc processing -> Settings for filtering in ALE Customizing. The appropriate setting depends on the sending and receiving logical R/3 System.
    Field conversion
    Receiver-specific field conversions are defined under Functions for the IDoc processing -> Conversions.
    General rules can be specified for field conversions; these are important for converting data fields to exchange information between R/2 and R/3 Systems. For example, the field "plant" can be converted from a 2-character field to a 4-character field.
    The conversion is done using general EIS conversion tools (Executive Information System).
    Version change
    SAP ensures that ALE functions between different R/3 System releases. By changing the IDoc format you can convert message types of different R/3 releases. SAP Development use the following rules when converting existing message types:
    -Fields may be appended to a segment type;
    -Segments can be added;
    ALE Customizing keeps a record of which version of each message type is in use for each receiver. The correct version of the communication IDoc is created in the ALE output.
    The resulting IDocs (it is possible that several IDocs could be created in the receiver determination) are referred to as communication IDocs and are stored in the database. The dispatch control then decides which of these IDocs should be sent immediately. These are passed to the communications layer and are sent either using the transactional Remote Function Call (RFC) or via file interfaces (e.g. for EDI).
    If an error occurs in the ALE layer, the IDoc containing the error is stored and a workflow is created. The ALE administrator can use this workflow to process the error.
    Inbound processing
    After an IDoc has been successfully transmitted to another system, inbound processing is carried out in the receiver system, involving the following steps in the ALE layer:
    Segment filtering
    Segment filtering functions the same way in inbound processing as in outbound processing.
    Field conversion
    Specific field conversions are defined in ALE Customizing.
    The conversion itself is performed using general conversion tools from the EIS area (Executive Information System).
    Generalized rules can be defined. The ALE implementation guide describes how the conversion rules can be specified.
    One set of rules is created for each IDoc segment and rules are defined for each segment field.
    The rules for converting data fields from an R/2-specific format to an R/3 format can be defined in this way. An example of this R/2 - R/3 conversion is the conversion of the plant field from a 2 character field to a 4 character field.
    Data transfer to the application
    Input control
    When the IDocs have been written to the database, they can be imported by the receiver application.
    IDocs can be passed to the application either immediately on arrival or can follow in batch.
    You can post an inbound IDoc in three ways:
    1. by calling a function module directly: A function is called that imports the IDoc directly. An error workflow will be started only if an error occurs.
    2. by starting a SAP Business Workflow. A workflow is the sequence of steps to post an IDoc.
    3. by starting a work item A single step performs the IDoc posting.
    The standard inbound processing setting is that ALE calls a function module directly. For information about SAP Business Workflow alternatives refer to the online help for ALE programming.
    Regards

  • How to Create a Single Backend Socket connectivity in a Server Socket Pgm

    Hi Everybody,
    I have a written a Server Socket which connects to back end socket and receiving the data and sending back to the front end. But as per my client requirement i need to create only one socket at the back end. But the code I have written is creating new sockets for each request. Is there any way to use the single client socket connection for all the transactions. I have attached the sample code for the reference.
    import java.io.*;
    import java.net.*;
    import java.nio.ByteBuffer;
    import java.nio.channels.SocketChannel;
    public class serl implements Runnable
    ServerSocket serversocket;
    Socket clientsoc;
    Socket fromclient;
    PrintStream streamtoclient;
    BufferedReader streamfromclient;
    SocketChannel socket_channel=null;
    Thread thread;
    public serl()
    try
    serversocket = new ServerSocket(1001);//create socket
    clientsoc = new Socket("10.100.53.145",200);
    socket_channel = clientsoc.getChannel();
    catch(Exception e)
    System.out.println("Socket could not be created "+e);
    thread=new Thread(this);
    thread.start();
    public void run()
    try
    while(true)
         PrintStream streamtobackend=null;
         BufferedReader streamfrombackend = null;
    fromclient=serversocket.accept();//accept connection fromclient
    streamfromclient=new BufferedReader(new InputStreamReader((fromclient.getInputStream())));
    //create a input stream for the socket
    streamtoclient=new PrintStream(fromclient.getOutputStream());
    //create an a output stream for the socket
    String str=streamfromclient.readLine();
    //read the message sent by client
    System.out.println("Output Input From Vtcpd "+str);
    streamtobackend.print(str);
    streamtobackend = new PrintStream(clientsoc.getOutputStream());
    //create an a output stream for the backend socket
    streamfrombackend = new BufferedReader(new InputStreamReader(clientsoc.getInputStream()));
    //create a input stream for the backend socket
    str=streamfrombackend.readLine();
    System.out.println("Output From Backend Client"+str);
    streamtoclient.println(str);
    }//end of while
    catch(Exception e)
    System.out.println("Exception "+e);
    finally
    try
    fromclient.close();
    catch(Exception e)
    System.out.println("could not close connection "+e);
    public static void main(String ar[])
    new serl();
    }

    Srikandh,
    Create a singelton pattern for you socket ( IP, port, etc..) and each time you read the input stream and write to the output stream, do the following to the socket to reset it in the working thread
    fromclient.getInputStream().mark(0);
    fromclient.getInputStream().reset();Hope this could help
    Regards,
    Alan Mehio
    London,UK

  • About back-end adapter and IDoc

    Hi everybody!
    I was watching in the FAQ of Mobile 7.1 about the possibility to use IDOC as a mechanism to push data to DOE, but this document only says: "IDocs are supported only for back-end-triggered scenarios" and provides a link to configure ALE between the backend and DOE, but the link doesn't work. (Somebody has this information on a link that works?)
    I'm trying to find any information, blog, article, how-to guide, however I cant found anything. Anybody has documentation about how to configurate and implement a backend-adapter to push data from the backend through IDOC? Any information will be welcome.
    Thanks in advance.
    Best regards,
    Simon.

    Hi San,
    You will have to look after this in Tansaction SE80. Open the BSP application cProjects, and find the appropriate view. (The naming convetion will help a little). Open the view tab: layout >> e.G. progAssignedPha.bsp Here you will find what BSP elements it consists of. You will find the
    <htmlb:tableView and <htmlb:inputField ... elements.
    Here you will find the information you are looking for.
    As easy as in SAPGui you can not find out this information.
    Regards.

  • Problem running reports to network printer

    Application Server Enterprise Edition 10g (9.0.4.1)
    Customer is having some difficulty printing reports to printers attached to client PCs and shared on the network. Occasionally, when a report is requested by the application with DESTYPE=PRINTER, DESFORMAT=DFLT and DESNAME=\\<PC>\<server share>, the status of the report remains "Opening report" and it never completes and cannot be removed. The report server (and dependent services) must be restarted to free the engine. The report is requested from a Forms application via a Report object.
    Here's detail from the Report Server engine trace file (traceOpts=trace_all):
    Debug 50103 (EngineImpl:setCommandLine): Running
    Info 50132 (EngineImpl:setCommandLine): Get command line: userid="ELSIEM paramform="NO" jobname="flysheet.rep" p_cov_effdt="20030315" desname="\\oldmelishal155\wc_hp4" p_rcvd_dt="" p_carrid="24724" p_ar_amt="" authid="ANONYMOUS" destype="printer" p_type="POL" batch="YES" p_ar_code="" report="flysheet.rep" background="yes" expiredays="0" desformat="DFLT" p_polnbr="08WC001094"
    Debug 50103 (EngineImpl:setCommandLine): Quit
    Debug 50103 (EngineImpl:run): Running
    Error 50103 (C Engine): 11:31:47 ERR REP-34551: BACKGROUND is deprecated. See help for more information.
    Error 50103 (C Engine): LOG :
    Error 50103 (C Engine): Logged onto server:
    Error 50103 (C Engine): Username: ELSIEM
    Error 50103 (C Engine):
    Error 50103 (rwfdt:rwfdtprint): Distributing the report
    Error 50103 (rwfdt:rwfdtpredo): running
    Error 50103 (rwfdt:rwfdtpredo): no preformat of pages requested, quit
    Error 50103 (rwfdt:rwfdtni_NextInstance): running
    Error 50103 (rwfdt:rwfdtni_NextInstance): quit
    Error 50103 (rwfdt:rwfdtgcf_GenCachefile): running
    Error 50103 (rwfdt:rwfdtgcf_GenCachefile): Cache file is e:\Spectrum\Cache\Test\45525639.eps
    Error 50103 (rwfdt:rwfdtgcf_GenCachefile): quit
    Error 50103 (rwfdt:rwfdtprint): caching output from backend drivers
    The last line appears to be the culprit. It seems as if the engine is attempting to communicate with the printer but failing. While this report was still "active" another request was made about 3 hours later that printed without issue.
    The printer's host OS is XP. The printer is a HP LaserJet 5si with up-to-date drivers (PCL 5e).
    Are there any specific issues with HP printers? Any ideas how to proceed with this problem? I've search high and low on Metalink and have not seen anything like this. I'd appreciate any help.
    Thanks,
    Robert Glossip

    >
    wavery wrote:
    > You should be able to specify the printer in the scheduling settings of the report itself in Infoview.
    Oh yes, I can see at "Print Settings" that I can specify a printer ("Set layout to: Specify printer settings"). However, I can't specify a printer in the "Destination" settings. So I can't do a scheduling, after my opinion?

  • Sales order web service

    Hi all
    We currently recieve orders from webMethods using an SAP adapter via an RFC call to FM IDOC_INBOUND_ASYNCHRONOUS. ALE output type aginst the order we RFC back order and delivery confirmation iDocs which wM then interporates.
    I am exploring the possibility of exposing this interface using web services...
    - what is the best approach for receiving orders asynchronously?
    - do we expose the IDOC_INBOUND_ASYNCHRONOUSas a web service?
    - has anybody tried this?
    - can we do this without XI?
    Thanks...
    JR

    hi rudster,
    i think it is not possible without xi.
    if you want the proces in xi see the below link
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/59ef6011-0d01-0010-bfb0-b51381e00509 -
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/7521a237-0701-0010-499b-b3285b789c0d
    thanks
    karthik

  • IDOC Number

    Hi All,
    Using a z program,does anyone know how to get the IDOC number generated using the sales order number. We have automatic output determination for this which generates the IDOC.
    This there a function module for this...
    Thanks in advance,
    Finbarr

    If you look at transaction WE09, you'll find a program that allows you to search IDocs based on data within segments.  Unfortunately, there is no direct link between order num and IDoc num.  If you are processing the ALE output immediately, you can use the order create date to help narrow down the selection from EDIDC.  If you are running RSNAST00 to process the ALE output, then you can select from NAST to determine approx date and time of IDoc creation.
    Once you pull EDIDC records by message type, date/time, you can run through EDID2(or EDID3, EDID4 depending on version) to find your order number.

  • Can we stop incoming IDOC in XI

    In a particular XI scenario, IDOC is coming from a R/3, but due to some performance reason, we need to stop those IDOCs entering into XI,
    i am not supposed to change the Configuration, or Design in Integration builder (due to some reason),
    also, we cannot stop those IDOC from R/3 (due to some reason),
    How can we stop these IDOCs flowing into XI,
    is there any facility in IDOC adapter to filter those particular IDOCs,
    pls advice

    Dear Sudeep,
    I'm not sure what exactly is your performance issue.
    If you dont want specific IDocs send to XI from R3 you should remove it
    from the Destribution model (BD64)
    and\or from the partner profile (WE20).
    best of all is to remove the action from the customization that initiats calls for th ALE output type.
    consul your SAP R3 uisness pepole or your ALE specialist.
    Nimrod.G

  • Multiple Outbound Message in a single XML

    Hi,
    My XML output from backend application will contain multiple messages. What should the XML look like in order for B2B to process all the messages?
    Should it be something like that?
    <XYZ>
    <Message-INVRPT xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.edifecs.com/xdata/100 guideline.xsd" XDataVersion="1.0" Standard="PFF" Version="">
    </Message-INVRPT>
    <Message-INVRPT xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.edifecs.com/xdata/100 guideline.xsd" XDataVersion="1.0" Standard="PFF" Version="">
    </Message-INVRPT>
    </XYZ>
    regards,
    nww

    Hi,
    Batching is not supported for custom document. You need to enqueue your message one by one into B2B. If you want to batch them together, you will need to write a script to concat them together after the messages have been translated into native EANCOM format.
    Eng

  • E-filing of TDS

    Hi guru
    what are the process to be followed in e-filing of tds in sap.
    Thanks
    shivaji

    Hi,
    j1inqefile is having two options.
    ALE output and efile generation.
    for Efilling please use the Efilling option.
    to view the data use the ALE option.
    Reg
    Madhu M

Maybe you are looking for