AES filing error - Idoc Outbound Processing: EDI number cannot be compiled

Hi Gurus,
We are configuring the AES filing.
we've done the EDI  configI and initally we got the error that EDI partner is not maintained. As per the suggestions from this Forum we've added the cusoms office details in geography tab.
Now when we are trying to process the same, we are getting the error "Idoc Outbound Processing: EDI number cannot be compiled"
All suggestions are welcome.........
Thanks in Advance.

Hi Shiva,
Here goes the solution: you need to maintain the Number of the Number Ranges starting with "10" and this applies only to GTS system as this is HARD-CODED in the Program, apart from 10 any number of the number range will result in an "EDI Number Range compilation" error.
Cheers
Harsha

Similar Messages

  • Error in outbound processing:ALE/IDOC

    Dear all,
    I am getting an error in outbound processing as follows(I have extended the BD12 IDOC for customer master).
    The issue is that there is no hierarchie of segments in IDOC transaction we05.(Thogh the hierarchie can be observed in WE30)
    EDI: Syntax error in IDoc (segment cannot be identified)
    Message no. E0078
    Diagnosis
    The segment Z1KNA1M_ADRC does not occur at the current level of the basic type DEBMAS06 (extension ).
    This error can have several reasons:
    u2022     The segment Z1KNA1M_ADRC is assigned to a group whose header segment does not occur.
    u2022     The segment Z1KNA1M_ADRC does not exist in the syntax description of the basic type DEBMAS06 (extension ).
    u2022     The sequence of segments in the group in which the segment appears is incorrect.
    Previous errors ('mandatory' segment or group missing) may be due to this error.
    Procedure
    Please check the IDoc or the syntax description of the basic type DEBMAS06 (extension ).
    I will be thankful if anybody can help resolve the issue.
    thanks.
    Edited by: sanjivrd on Aug 4, 2009 2:17 PM

    hi,
    after adding those segments you need to release it.
    check it menu you can see the release option, you need to release it.
    then only it will work
    [Refer following link|EDI: Syntax error in IDoc (segment cannot be identified)]
    In the menu edit-> set release
    click on it and release
    Even check If the Hierrarchy of the segment is correct. This also will result in Syntax Errors.
    thanks & Regards,
    ShreeMohan

  • RFC For IDoc outbound processing

    I am creating an RFC for BDC for call transaction we19
    input as : idoc number
    and output:-.. iDoc Outbound processing done
    so:-
    I go to we19> give iDoc Number (say, some number for ALEREQ01), and execute> click on Outbound processing-->click enter -->enter
    in this way, I can process any iDoc from SAP system to outbound.
    I want  to create RFC for the same.
    Problem:-
    when i am executing that RFC, and when I check the iDoc status in we05, that iDoc shows status as Idoc ready to dispatch( its in yellow color).. Its not showing green color and not saying that IDoc passed OK
    when I try manually ,I see the status green..OK..successfully
    Any idea why I am getting this problem??
    Is there any problem in my BDC recording?..but when I run that recording for Process, i dont see any problem,it executes successfully.. but when I copy the Code from BDC and make a RFC using that code, its giving problem as mentioned.

    Hi Ankit,
    Theorotically it should work.... but I'll suggest not to use BDC here. What you can do is,
    1. You have Idoc number..Right?
    2. Read control record from EDIDC and data record from EDID4.
    3. Then call Master_idoc_distribute.
    4. This will again distribute the same IDoc with same control and data record as a new one. It will be same as WE19 , but without WE19.
    Please check and confirm.
    Regards,
    Audy.

  • IDOC Outbound processing using SAP BC

    Hello Experts,
    I am trying to develop a simple IDOC outbound processing scenario using SAP BC. In this an IDOC from SAP ECC server will be sent to an external webserver via SAP BC, for this i have done all the setup i.e Establishing connection between SAP BC & SAP ECC,  ALE settings, creating a new Routing rule, but when i try to run this scenario, i am getting the following error 'IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE' , is there any way to import the IDOC metadata, just like how we do in SAP XI using IDX2. Please Help...
    Thanks & Regards,
    Amit Naik

    Hi Michal,
    Following is the error which i am getting :-
    2009-03-12 21:56:59 IST com.sap.conn.idoc.IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "" is unavailable.
         at com.sap.conn.idoc.rt.DefaultIDocDocument.<init>(DefaultIDocDocument.java:132)
         at com.sap.conn.idoc.jco.JCoIDocDocument.<init>(JCoIDocDocument.java:74)
         at com.sap.conn.idoc.jco.JCoIDocDocument.createIDocDocument(JCoIDocDocument.java:117)
         at com.sap.conn.idoc.jco.JCoIDocRuntime.createIDocDocumentList(JCoIDocRuntime.java:83)
         at com.sap.conn.idoc.jco.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:88)
         at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:141)
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:2621)
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2298)
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2130)
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2012)
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:1903)
         at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:258)
         at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:320)
         at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:219)
         at com.wm.util.TimeWrappingProvider$TimeMesuredTask.run(TimeWrappingProvider.java:40)
         at com.wm.pkg.sap.rfc.ListenerThread.run(ListenerThread.java:70)
    Thanks & Regards,
    Amit

  • Error in batch processing: background job cannot be scheduled

    Error in batch processing: background job cannot be scheduled in transaction code jpmg0. How to resolve the same?

    Hello,
    Check system log and also check work process trace, to know the error.
    I feel that it could be Authorization issue, you don't have sufficient authorization to do.
    Hope this helps.
    Regards
    venkata
    Edited by: venkata emandi on Sep 12, 2011 8:13 AM

  • IDoc Outbound processing

    Hi All,
    I am doing IDoc to File scenario. I have my IDocs in AXI system and XI in ZXI system.I want to send idocs from AXI to ZXI. I have configured the following in AXI :
    RFC dest to ZXI (Dest4ZXI)
    Transaction Port to ZXI having RFC dest as Dest4ZXI
    Logical system for receiver file system
    Partner profile for receiver file system with outbound parameter
    and the following configuration in ZXI:
    RFC dest to AXI (AXICLNT100)
    Port to get IDoc's metadata from AXI (SAPAXI) having RFC dest as AXICLNT100
    In SLD, i created a tech sys and business sys for sender system AXI and then i created a scenario in ZXI for IDoc to File. In IR, imported the idoc and created all other objects till interface mapping. In ID, assigned the business system, created a service for file receiver and created rec det,int det and rec agreement.
    Using Idoc test tool i started the outbound processing after giving the data and control record and got the IDoc sent successfully message.
    Control record values:
    Receiver: port = (port created in AXI), partner no = (LS File receiver sys created in AXI)
    sender  : port = (SAPAXI - port creted in zXI), partner no = (AXICLNT100 - LS created in sld - which is same name as RFC detination created in ZXI)
    If i check in we05, its green flag. But in sm58, error status message for the idoc is showing as "No service for the system SAPAXI for client 100 in Integration Directory.
    Note: I am using a custom IDoc with 8 fields.
    Kindly reply if my descriptions are not clear!
    Appreciating all help.
    Thanks in advance,
    Uma

    Hi Uma,
    <b>Have u imported the Business System as Service or not?create u r cc in the service for that bs only</b>
    If not just try with it..
    If the sender system is maintained as the business service then we have to edit adapter specific identifiers and give the appropriate logical system name in the integration directory...
    In ID goto Service Adapter-Specific Identifiers and mention the Logicalsystem and Client and ID...
    Check this blog
    /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
    and also
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    for refernece...
    Regards,
    Sridhar

  • Error while outbound processing

    Hi
    In WE19, when i enter control record details( sender and receiver port, partner etc ) and then when i
    click outbound processing button i am getting a warning saying that "IDOC saved successfully but it
    should not or cannot be sent". i am tring to send the IDOC out from ecc6 to xi . can anyone tell me
    what would the problem?
    thanks and regards
    manoharan

    hi
    is this ALE configuration specific to any message or idoc types used because if i use message type
    FLCUSTOMER_CREATEFROMDATA  iam not getting the warning message. in this case the required
    message is displayed( idoc created sucessfully and sent to sap or external system).
    regards
    mano

  • Error on outbound processing (- to IDoc), nodetailed error message

    Hi guys!
    I'm facing a problem with sending IDocs to R/3. My messages have red flag in outbound status, but there is no detailed error message. Everything seems to be ok, but my IDoc doesn't arrive to R/3 and there is that red flag in XI.
    What could cause this? It seems like there is some communication problem. Any ideas?
    Thank you,
    Olian

    Hi,
    IT will give the status number,what is the status number in IDOC check it and update the thread.
    if u find its a data problem u can debugg the FM,go to WE19 and give ur IDOC number and there u will find the option start out bound processing form this opion u can debugg the code and know wat is the error.
    Check ur ALE settings.
    STEP 1:ALE SETTINGS TO POST IDOC OUT OF SAP R/3
    We need to do the following settings in XI
    1) Create an RFC Destination to the Sending System in transaction code (SM59)
    a) Choose create
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#
    e) Enter the Gateway host as same details above SID/URL
    f) Gateway service is 3300+system number#
    g) In the Logon /Security tab, enter the client user & Password details of Destination system
    h) Test the connection and remote logon.Both should be succesful
    2) Create Port Using Transaction Code IDX1
    a) Select create new button
    b) Enter the port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client
    d) Enter the RFC Destination created in SAP R/3 towards other system
    e) Save
    3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
    a) Create new
    b) IDOC Message Type
    c) Enter port created in IDX1
    SETTINGS IN SAP R/3
    We need to do the following settings in R/3
    Logon to Sap R/3 System
    1) Create an RFC Destination to XI in transaction code (SM59)
    a) Choose create
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#
    e) Enter the Gateway host as same details above SID/URL
    f) Gateway service is 3300+system number#
    g) In the Logon /Security tab, enter the client user & Password details of Destination system
    h) Test the connection and remote logon.Both must be succesful
    2) Create communication Port for Idoc processing Using Transaction(We21)
    a) First Select Transactional RFC and then click create button
    b) Enter the destination port name as SAP+SID (The starting char should be SAP)
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Create Partner Profile with Outbound Parameters (WE20)
    a) Create New
    b) Create the Partner no. name as same the logical system name of the destination system
    c) Select Partner type LS
    d) Enter details for Type: US/USER, Agent, and Lang
    Then Save
    e) Select Partner no. and LS which were create above
    f) Now we have to give some Outbound Parameters.So click on ADD TO Create Outbound Parameter
    g) Select Message type
    h) Double click on Message Type and Then Enter the details for Receiving port, Pack size=1 and Basic type
    I) save
    4) In Transaction SALE, Create Logical System
    a). Go to Basic Settings-> First Define logical systems
    and then assign logical systems
    b) Double click on Define the logical systems
    c) Give data for your Logicaal System and Name
    d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
    e) Assign the logical system name to the client
    5) Create Customer Distribution model in the transaction code BD64
    1) Click on the Create modal View button and enter the short text, Technical name etc as shown below
    2) Now select the created model view and click on Add message type button .A pop up box appears, enter Sending system, receiving system and message type
    3) Save the Distribution model
    Generate Partner Profiles
    Click on Menu Item ‘Generate Partner Profiles’
    It leads to the next transaction where in the selection screen you have to provide Model view name, Partner System logical system and execute
    Then, you will be intimated about the partners, port creation, and outbound parameters creation
    4) Distribute Customer Distribution Model
    In the menu item GO to Edit->Modal View-> ‘Distribute’ to the destination client
    Popup window appears ,press Enter
    You will be intimated about the the Modal View Distributed
    Regards,
    Phani
    Reward points if Helpful

  • Error in inbound processing: EDI message - XML Gateway

    Hello!
    I've setup a DELFOR transaction in B2B and modified XML Gateway settings for internal delivery channel in order to send the message to EBS, but I'm getting weird errors in b2b.log. (XML Gateway in EBS is not setup yet, but it should't be an issue since incoming errors are handled in EBS, and I would just see an inbound transaction with processing errors in Transaction Monitor.)
    In the beginning of b2b.log I see this:
    2009.07.07 at 15:26:31:897: B2BStarter thread: BusinessLogicLayer - (DEBUG) Push Stack: queryInternalDeliveryChannel
    2009.07.07 at 15:26:31:897: B2BStarter thread: BusinessLogicLayer - (DEBUG) Pop Stack: queryInternalDeliveryChannel
    2009.07.07 at 15:26:31:897: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:31 CEST 2009 inbound initialize
    2009.07.07 at 15:26:31:897: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:31 CEST 2009 Obtaining inbound connection...
    2009.07.07 at 15:26:31:897: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:31 CEST 2009 inbound connect string: jdbc:oracle:thin:@server64.xa.si:1521:test2
    2009.07.07 at 15:26:31:897: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:31 CEST 2009 inbound username: apps
    2009.07.07 at 15:26:32:522: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:32 CEST 2009 inbound initialize exit
    2009.07.07 at 15:26:32:522: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:startListen Enter
    2009.07.07 at 15:26:32:538: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:startListen Exit
    2009.07.07 at 15:26:32:538: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:run Thread start
    2009.07.07 at 15:26:32:538: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize Exit
    2009.07.07 at 15:26:32:538: B2BStarter thread: B2B - (DEBUG) B2BStarter - B2B initialized
    After I copy the edi file to the incoming directory B2B starts processing the file:
    2009.07.07 at 15:30:01:878: Thread-10: B2B - (DEBUG)
    Protocol = File
    Version = 1.0
    Transport Header
    filename:00003442_23.CMS
    filesize:12345
    file_ext:CMS
    fullpath:C:\xa_endpoint\00003442_23.CMS
    timestamp:2009-07-06T16:14:29.393+01:00
    As I see in the log: B2B finds the trading partner and agreement and all looks fine. But later comes this:
    2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination Enter
    2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination deliver message to destination. protocol is XMLGateway Queues
    2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination deliver message to XMLGW
    2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : Tue Jul 07 15:30:05 CEST 2009 Converting B2B message to ECX message..
    2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : Tue Jul 07 15:30:05 CEST 2009 Inbound - B2BtoECX - Enter
    2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : Tue Jul 07 15:30:05 CEST 2009 B2B Message -
    2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : COLLABORATION_NAME : null
    2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : ACTION_NAME : DELFOR
    2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : DOCUMENT_TYPE : DELFOR
    2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : DOCUMENT_TYPE_REVISION : D97A
    2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : SOURCE_NAME : tpartner
    2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : DESTINATION_NAME : Xa d.d.
    2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : PAYLOAD : UNB+UNOA.............. edi message continues here
    2009.07.07 at 15:30:05:925: Thread-9: B2B - (DEBUG) : PAYLOAD : <?xml version="1.0" ?><Transaction-DELFOR............... xml continues here
    2009.07.07 at 15:30:05:925: Thread-9: B2B - (DEBUG) : Tue Jul 07 15:30:05 CEST 2009 ECX Message -
    2009.07.07 at 15:30:05:925: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:handleAppMessageRetry Could not deliver the message; exception message is null
    2009.07.07 at 15:30:05:925: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:handleAppMessageRetry No application side retry
    2009.07.07 at 15:30:06:081: Thread-9: B2B - (ERROR) Error -: AIP-50903: Message "0A14011912255682A58000003257C600-1" retry count is zero
         at oracle.tip.adapter.b2b.msgproc.MessageHandler.handleAppMessageRetry(MessageHandler.java:394)
         at oracle.tip.adapter.b2b.msgproc.MessageHandler.deliverMessageToDestination(MessageHandler.java:344)
         at oracle.tip.adapter.b2b.msgproc.Request.putMsg(Request.java:657)
         at oracle.tip.adapter.b2b.msgproc.Request.continueRequest(Request.java:481)
         at oracle.tip.adapter.b2b.msgproc.Request.incomingRequest(Request.java:410)
         at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:2062)
         at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2574)
         at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2444)
         at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2399)
         at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
         at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
         at java.lang.Thread.run(Thread.java:534)
    Last message repeats once more and then:
    2009.07.07 at 15:30:06:081: Thread-9: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
    2009.07.07 at 15:30:06:081: Thread-9: BusinessLogicLayer - (DEBUG) Push Stack: updateBusinessMessage
    2009.07.07 at 15:30:06:096: Thread-9: BusinessLogicLayer - (DEBUG) Pop Stack: updateBusinessMessage
    2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateMsgError(3 params) Exit
    2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) DBContext commit: Enter
    2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) DBContext commit: Transaction.commit()
    2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) DBContext commit: Leave
    2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination Exit
    2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest Exit
    2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: processIncomingMessage setting seq numbers
    2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Call Incoming Request Processor
    2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest Enter
    2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest TransportBindings created
    2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest Create a Message Table Row for Request message with message state Continue Processing
    2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow Enter
    2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
    2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Push Stack: queryExchangeProtocolRevision
    2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Pop Stack: queryExchangeProtocolRevision
    2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
    2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Push Stack: queryDocumentProtocolRevision
    2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Pop Stack: queryDocumentProtocolRevision
    2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (ERROR) Error -: AIP-13115: Not in an active transaction
         at oracle.tip.repos.core.persistency.BaseObject.prologue(BaseObject.java:1408)
         at oracle.tip.repos.core.persistency.BaseObject.createObject(BaseObject.java:913)
         at oracle.tip.model.instance.DataStorage.create(DataStorage.java:794)
         at oracle.tip.adapter.b2b.message.MessageStorage.create(MessageStorage.java:145)
         at oracle.tip.adapter.b2b.msgproc.DbAccess.insertMsgTblRow(DbAccess.java:953)
         at oracle.tip.adapter.b2b.msgproc.Request.incomingRequest(Request.java:397)
         at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:2062)
         at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2574)
         at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2444)
         at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2399)
         at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
         at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
         at java.lang.Thread.run(Thread.java:534)
    2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) setRuntimeActiveandQuiescing()
    2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage General Exception ERROR
    Error repeats a few times.
    Wire message stays in Processing status, Business message is errored and an exception message is created in ip_in_queue.
    Both remote and host delivery channels have retry set to 1. Agreement was re-deployed + all B2B restared, but the problem remained.
    Could anyone help with this? What could be wrong?
    Thanks in advance.
    Kind regards,
    Wanda
    PS. I've checked all threads that might have anything to do with this, but found nothing useful.

    Hi Anuj,
    thanks for taking the time to examine the file.
    Answers to your questions:
    1. Yes, this is the 1st time for B2B, but the EBS I'm trying to connect to is up and running for approx. 2 years (it's a test instance).
    2. Patching was done by the customer's sysadmin, so I don't really have an overview on what and how he did. Result of opatch:
    Installed Patch List:
    =====================
    1) Patch 8298731 applied on Sat Jun 13 09:23:42 CEST 2009
    2) Patch 5907304 applied on Thu Jul 17 14:26:55 CEST 2008
    3. In theory the sysadmin should have run it, but how could I double-check this?
    I know he had problems while applying patch 8298731, but he said it was solved later. (Customer is using windows os, which is making a lot of troubles otherwise.)
    Regarding IDC log there is no success. I've restared B2B at least 5 times plus once the database, but still nothing. In tip.properties:
    oracle.tip.adapter.b2b.transportTrace = C:\APPS\OAS\ip\log/transport.trc
    also I tried the following values:
    C:\\APPS\\OAS\\ip\\log/transport.trc (since there is a similar entry: oracle.tip.LogDirectory = C:\\APPS\\OAS\\ip\\log)
    C:\\\\\\\\\\\\\\\\APPS\\\\\\\\\\\\\\\\OAS\\\\\\\\\\\\\\\\ip\\\\\\\\\\\\\\\\log/transport.trc (this was commented before; maybe it comes from some default)
    true (I had no other idea)
    Result is the same for all the cases: b2b_idc_transport.log file is 0 bytes, but b2b_dc_transport.log has initial data+writes log when processing.
    If I remove or comment the above line from tip.properties, then no transport log files are created.
    I've updated the agreement to have B2B inbound for the internal delivery channel, re-deployed it and it worked fine -> transaction(s) appeared in IP_IN_QUEUE.
    Changing it back to XML Gateway (and re-deploying) causes all original problems.
    Regards,
    Wanda

  • ALE idocs outbound process

    ale setting i properly then i created zprogram to generate idocs , idocs are generated for out bond process . then i checked in other client the data is not received sending system showing the idoc status is 3 . other client i am not able to see the data? can any one tell me how check that idocs.

    first check the RFC thru SM59, whether the ports are mainted properly, next check whether partner profiles(WE20) are mainted correctly with the respective ports and then check if the idocs are stagnated anywhere between the server thru the help of middleware team
    if both are mainted properly debug the code with BD87 or WE19, where exactly u will know the issue which helps you to rectify the problem

  • COND_A Idoc Outbound Process

    Hi,
    I did set up everything to trigger COND_A. Its not getting triggering ?. What is the problem?. My changes are CDHDR and CDPOS tables. How can I trigger the change pointers of this idoc?. Thanx

    Did you activate change pointers for the COND_A message type?

  • ALE / IDOC Outbound Error Handling

    Hi Experts,
    I got an error in Outbound Process.
    An IDOC gets the status 36 - Timed out.
    Can anyone tell me how can i resolve this Error?.
    Thanks in advance,
    Sudhakar

    Hi ,
            Best option is to keep a sql trace on the outbound idoc which will tell you at which perform or functional module ,the performance is taking time to fetch .
    all check with basis in terms of timed out ,they would have set a paramater for time out in terms of mins or hrs.

  • Difference btw idoc ale and edi

    Hi all,
    I'm a beginner in abap, can anyone send me the concepts of ALE, IDOC and EDI and the difference btw all the three.
    Also do send some materials for the same.

    Hi,
    ALE (Application Linking and Enabling)
    Ale Technology is SAP’s technology to support distributed yet integrated processes across several SAP systems.
    Distributed Process:
    A distributed process is one in which part of a business process is carried out on one system and part on another. The two systems would exchange data with each other at appropriate points to stay synchronized.
    Need for Distributed Process:
    • Business in Different Geographical Locations.
    • Non availability of dedicated network.
    • Cultural and language differences in Geographical locations.
    • Running of Mission-critical Applications (Like Maintenance downtime etc.).
    • Separate up gradation of Modules.
    Distributed SAP SYSTEM – CHALLENGES
    • A system that understands the syntax and semantics of the data. It was important from the very beginning to base the distribution of data on business rules, not on database replication techniques.
    • Distributed systems that can maintain their autonomy while being integrated as one logical SAP system. The systems should be able to operate independently and support logical processing of transactions and data.
    • Distributed systems that can handle different data models. A local implementation should be able to customize the system to meet its local needs.
    • Receiving systems that can handle their own problems and not tie up the sending system.
    • Systems that maintain continued operation in spite of network failure. Changes made to either system should be synchronized after the network connection is restored.
    • A sound technology and methodology that can be used in all distribution scenarios.
    SAP Distributed environment:
    ALE allows for efficient and reliable communication between distributed processes across physically separate SAP systems.
    ALE is based on application to application integration using messaging architecture. A message defines data that is exchanged between two processes. IDocs are containers that hold data exchanged between the two systems.
    Benefits of ALE:
    • Integration with non-SAP systems: ALE architecture allows third party applications to integrate with SAP system.
    • Reliable Distribution: Once message type created and the receiver of the message is determined, ALE delivers the message to the recipient. If there is any network problem it will buffer the message and delivers the message once the network is restored. It also ensures that the message is not delivered twice.
    • Release Upgrade: Any of the distributed system can be upgraded to the new release of SAP without affecting the functionality. The ALE layer ensures backward compatibility of messages exchanged between systems.
    ALE Architecture:
    It consists of an Outbound process, an Inbound process, and an Exception – Handling process.
    Outbound Process:
    ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.
    1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.
    2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.
    3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.
    4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.
    Inbound Process:
    The inbound process receives an IDoc and creates a document in the system.
    1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.
    2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.
    3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.
    Over view of IDocs:
    IDoc is a container that is used to exchange data between any two processes. The document represented in an IDoc is independent of the complex structure SAP uses to store application data. This type of flexibility enables SAP to rearrange its internal structure without affecting the existing interface.
    IDoc interface represents an IDoc Type or IDoc data. IDoc Type represents IDoc’s definition and IDoc Data is an instance of the IDoc Type.
    IDoc Types:
    IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
    An IDoc is an instance of an IDoc Type and consists of three types of records.
    i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
    ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
    iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
    Message in IDoc Type:
    A Message represents a specific type of document transmitted between two partners.
    Outbound Process in IDocs:
    Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
    The Customer Model:
    A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
    Message control:
    Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.
    Change Pointers:
    The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
    Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
    IDoc Structure:
    A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
    Selection Program:
    Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection program’s design depends on the triggering mechanism used in the process.
    Filter Objects;
    Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
    Port Definition:
    A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
    RFC Destination:
    The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
    Partner Profile:
    A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDoc’s packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
    Service Programs and Configuration Tables:
    The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
    Process flow for Distributing Transactional Data:
    Transactional data is distributed using two techniques: with Message control and without message control.
    Process flow for Distributing Master Data:
    Master data between SAP systems is distributed using two techniques: Stand alone Programs and Change Pointers.
    Triggering the Outbound Process via Stand-Alone Programs:
    Stand-Alone programs are started explicitly by a user to transmit data from one SAP system to another. Standard Programs for several master data objects exist in SAP. Ex. The material master data can be transferred using the RBDSEMAT program or transaction BD10.
    The stand-alone programs provide a selection screen to specify the objects to be transferred and the receiving system. After the stand-alone program is executed, it calls the IDoc selection program with the specified parameters.
    Triggering the Outbound Process via Change Pointers:
    The change pointer technique is used to initiate the outbound process automatically when master data is created or changed.
    A standard program, RBDMIDOC, is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process for distributing the master data to the appropriate destination. The RBDMIDOC program reads the table TBDME to determine the IDoc selection program for a message type.
    Processing in the Application Layer:
    The customer distribution model is consulted to make sure that a receiver has been defined for the message to be transmitted. If not, processing ends. If at least one receiver exists, the IDoc selection program reads the master data object from the database and creates a master IDoc from it. The master IDoc is stored in memory. The program then calls the ALE service layer by using the function module MASTER_IDOC_DISTRIBUTE, passing the master IDoc and the receiver information.
    Processing in the ALE Interface Layer:
    Processing in the ALE Layer consists of the following steps:
    • Receiver Determination: The determination of the receiver is done through Customer Distribution Model.
    • IDoc Filtering: if an IDoc filter is specified in the distribution model for a receiver, values in the filter are compared against the values in the IDoc data records. If a data record does not meet the filter criteria, it is dropped.
    • Segment Filtering: For each sender and receiver combination, a set of segments that are not required can be filtered out.
    • Field conversion: Field values in data records are converted by using the conversion rules specified for the segment.
    • Version change for segments: Segments are version-controlled. A new version of a segment always contains fields from the preceding version and fields added for the new version. Release in IDoc type field of the partner profile to determine the version of the segment to be generated.
    • Version change for IDocs: IDocs are also version controlled. The version is determined from the Basic Type field of the partner profile.
    • Communication IDocs generated: The final IDoc generated for a receiver after all the conversions and filtering operations is the communication IDoc. One master IDoc can have multiple communication IDocs depending on the number of receivers identified and the filter operations performed. IDoc gets the status record with a status code of 01 (IDoc Created).
    • Syntax check performed: IDoc goes through a syntax check and data integrity validation. If errors found the IDoc get the status of 26 (error during syntax check of IDoc – Outbound). If no errors found the IDoc gets the status 30 (IDoc ready for dispatch – ALE Service).
    • IDoc dispatched to the communication Layer: In the ALE process, IDocs are dispatched using the asynchronous RFC method, which means that the sending system does not await for data to be received or processed on the destination system. After IDocs have been transferred to the communication layer, they get a status code 01 (Data Passed to Port OK).
    Processing in the Communication Layer:
    To dispatch an IDoc to a destination system, the system reads the port definition specified in the partner profile to determine the destination system, which is then used to read the RFC destination. The RFC destination contains communication settings to log o to the remote SAP system. The sending system calls the INBOUND_IDOC_PROCESS function module asynchronously on the destination system and passes the IDoc data via the memory buffers.
    Inbound Process in IDocs:
    An inbound process used IDoc structure, posting programs, filter objects, conversion rules, a partner profile, service programs, and configuration tables to post an application document from an IDoc.
    Posting Program:
    Posting programs, which are implemented as function modules, read data from an IDoc and create an application document from it. A posting program exists for each message. Each posting program is assigned a process code. A process code can point to a function module or a work flow. In the standard program process codes always point to a function module.
    Ex. The posting program for message type MATMAS is IDOC_INPUT_MATMAS which has a process code MATM.
    Workflow:
    A workflow represents a sequence of customized steps to be carried out for a process. The workflow management system is used to model the sequence, identify information required to carry out the steps and identify the person responsible for the dialog steps.
    Partner Profile;
    A partner profile specifies the components used in an inbound process (partner number, message type, and process code), the mode in which IDocs are processed (batch versus immediate), and the person to be notified in case of errors.
    Process flow for the Inbound process via a Function Module:
    In this process, IDocs are received from another system and passed to the posting function module directly.
    1. Processing in the communication Layer:
    The IDOC_INBOUND_ASYCHRONOUS program, triggered as a result of an RFC from the sending system, acts as the entry point for all inbound ALE processes. The IDoc to be processed is passed as an input parameter. Control is transferred to the ALE/EDI layer.
    2. Processing in the ALE/EDI Interface Layer:
    • Basic integrity check: A basic integrity check is performed on the control record.
    • Segment Filtering and conversion: Filtering out unwanted segments and carry out any required conversion of field values.
    • Creation of Application IDoc: The application IDoc is created and stored in the database and a syntax check is performed. If there are errors it gets status code of 60 (Error during Syntax check of IDoc – Inbound). At this point a tangible IDoc, which can be monitored via one of the monitoring transactions, is created and the IDoc gets status code 50 (IDoc Added).
    • IDoc Marked ready for Dispatch: IDoc gets the status code 64 (IDoc ready to be passed to application).
    • IDoc is passed to the posting program: The partner profile table is read. If the value of the Processing field is set to Process Immediately, the IDoc is passed to the posting program immediately using the program RBDAPP01.
    3. Processing in the Posting Module:
    The process code in the partner profile points to a posting module for the specific message in the IDoc. The posting program implemented as a function module either calls a standard SAP transaction by using the Call Transaction command for posting the document or invokes a direct input function module.
    The results of execution are passed back via the function module’s output parameters. If the posting is successful IDoc gets the status code 53 (Application Document Posted) or it gets status code 51 (Error: Application Document Not Posted).
    IDOC:
    Data Creation in Idoc
    IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
    asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
    While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
    IDoc is a intermediate document to exchange data between two SAP Systems.
    *IDocs are structured ASCII files (or a virtual equivalent).
    *Electronic Interchange Document
    *They are the file format used by SAP R/3 to exchange data with foreign systems.
    *Data Is transmitted in ASCII format, i.e. human readable form
    *IDocs exchange messages
    *IDocs are used like classical interface files
    IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    FOr testing you can use WE19.
    How to create idoc?
    *WE30 - you can create a IDOC type
    For more information in details on the same along with the examples can be viewed on:
    [http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404]
    [http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm]
    [http://www.sappoint.com/presentation.html]
    [http://www.allsaplinks.com/idoc_search.html]
    [http://www.sapgenie.com/sapedi/idoc_abap.htm]
    [http://www.erpgenie.com/sapedi/idoc_abap.htm]
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30 )
    Create Message Type ( WE81 )
    Assign Idoc Type to Message Type ( WE82 )
    Creating a Segment
    Go to transaction code WE31
    Enter the name for your segment type and click on the Create icon
    Type the short text
    Enter the variable names and data elements
    Save it and go back
    Go to Edit -> Set Release
    Follow steps to create more number of segments
    Create IDOC Type
    Go to transaction code WE30
    Enter the Object Name, select Basic type and click Create icon
    Select the create new option and enter a description for your basic IDOC type and press enter
    Select the IDOC Name and click Create icon
    The system prompts us to enter a segment type and its attributes
    Choose the appropriate values and press Enter
    The system transfers the name of the segment type to the IDOC editor.
    Follow these steps to add more number of segments to Parent or as Parent-child relation
    Save it and go back
    Go to Edit -> Set release
    Create Message Type
    Go to transaction code WE81
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter
    Click New Entries to create new Message Type
    Fill details
    Save it and go back
    Assign Message Type to IDoc Type
    Go to transaction code WE82
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.
    Click New Entries to create new Message Type.
    Fill details
    Save it and go back
    Check these out..
    [Re: How to create IDOC;
    Check below link. It will give the step by step procedure for IDOC creation.
    [http://www.supinfo-projects.com/cn/2005/idocs_en/2/]
    ALE/ IDOC
    [http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm]
    [http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc]
    [http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419]
    [http://www.netweaverguru.com/EDI/HTML/IDocBook.htm]
    [http://www.sapgenie.com/sapedi/index.htm]
    [http://www.sappoint.com/abap/ale.pdf]
    [http://www.sappoint.com/abap/ale2.pdf]
    [http://www.sapgenie.com/sapedi/idoc_abap.htm]
    [http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm]
    [http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm]
    [http://www.allsaplinks.com/idoc_sample.html]
    [http://www.sappoint.com/abap.html]
    [http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm]
    [http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc]
    [http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419]
    [http://www.netweaverguru.com/EDI/HTML/IDocBook.htm]
    [http://www.sapgenie.com/sapedi/index.htm]
    [http://www.allsaplinks.com/idoc_sample.html]
    [http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs]
    go trough these links.
    [http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm]
    [http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc]
    [http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419]
    [http://www.netweaverguru.com/EDI/HTML/IDocBook.htm]
    [http://www.sapgenie.com/sapedi/index.htm]
    [http://www.sappoint.com/abap/ale.pdf]
    [http://www.sappoint.com/abap/ale2.pdf]
    [http://www.sapgenie.com/sapedi/idoc_abap.htm]
    [http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm]
    [http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm]
    [http://www.allsaplinks.com/idoc_sample.html]
    [http://www.sappoint.com/abap.html]
    [http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm]
    [http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc]
    [http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419]
    [http://www.netweaverguru.com/EDI/HTML/IDocBook.htm]
    [http://www.sapgenie.com/sapedi/index.htm]
    [http://www.allsaplinks.com/idoc_sample.html]
    [http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm]
    An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
    1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
    2.IDOCs are independent of the sending and receiving systems.
    3.IDOCs are independent of the direction of data exchange.
    The two available process for IDOCs are
    Outbound Process
    Inbound Process
    AND There are basically two types of IDOCs.
    Basic IDOCs
    Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
    Extended IDOCs
    Extending the functionality by adding more segments to existing Basic IDOCs.
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30)
    Create Message Type ( WE81)
    Assign Idoc Type to Message Type ( WE82)
    imp links
    [http://www.allsaplinks.com/idoc_sample.html]
    [http://www.sapgenie.com/sapedi/idoc_abap.htm]
    [www.sappoint.com]
    --here u can find the ppts and basic seetings for ALE
    [http://sappoint.com/presentation.html]
    [www.sapgenie.com]
    [http://www.sapgenie.com/ale/index.htm]
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    Try this..Hope this will help.
    SAP ALE & IDOC<<<<
    Steps to configuration(Basis) >>
    1. Create Logical System (LS) for each applicable ALE-enabled client
    2. Link client to Logical System on the respective servers
    3. Create background user, to be used by ALE(with authorizaton for ALE postings)
    4. Create RFC Destinations(SM59)
    5. Ports in Idoc processing(WE21)
    6. Generate partner profiles for sending system
    The functional configuration(Tcode: SALE)
    • Create a Customer Distribution Model (CDM);
    • Add appropriate message types and filters to the CDM;
    • Generate outbound partner profiles;
    • Distribute the CDM to the receiving systems; and
    • Generate inbound partner profiles on each of the clients.
    Steps to customize a new IDoc >>>
    1. Define IDoc Segment (WE31)
    2. Convert Segments into an IDoc type (WE30)
    3. Create a Message Type (WE81)
    4. Create valid Combination of Message & IDoc type(WE82)
    5. Define Processing Code(WE41 for OUT / WE42 for IN)
    6. Define Partner Profile(WE20)
    RFC:
    RFC (Remote Function Call) is similar to the general SAP fun module: except that in the attributes you click the radio button: RFC enabled;
    and you will be passing an Import parameter DESTINATION to it.
    Other code and usage will be similar to any fun module;
    Have a look at any fun module in SE37 to understand better about the different components of Fun modules;
    Refer this link:
    [http://help.sap.com/saphelp_nw04/helpdata/en/22/042518488911d189490000e829fbbd/frameset.htm]
    check out the following link it might help you
    [http://help.sap.com/printdocu/core/Print46c/de/data/pdf/BCFESDE2/BCFESDE2.pdf]
    EDI:
    Electronic Data Interchange
    Cross-company exchange of electronic data (for example business documents) between domestic and international business partners who use a variety of hardware, software, and communication services. The data involved is formatted according to predefined standards. In addition to this, SAP ALE technology is available for data exchange within a company.
    Refer
    [http://www.erpgenie.com/sapedi/index.htm]
    [http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm]
    [https://www.2020software.com/products/Fourth_Shift_Edition_for_SAP_Business_One_Electronic_Data_Interchange.asp]
    [http://downloads-zdnet.com.com/SoftwareandWebDevelopment/SoftwareDevelopmentTools/ElectronicData+Interchange/]
    [http://www.erpgenie.com/sapedi/index.htm]
    [http://www.kostal.com/english/downloads/EDI_AGB_eng.pdfd]
    EDI FLOW :
    Here is some thing which helps you and here the purchase order is taken as example too..
    Electronic Data Interchange, or EDI, is the electronic exchange of business data. Using a standard format, EDI provides a method of transmitting business data from one computer to another, without the need to re-key data. This electronic link can result in more effective business transactions. With EDI, paper documents such as invoices can be replaced with electronic transmissions, thus time is saved, and the potential for error is minimized. Data can be exchanged at any time. Related business expenses, such as postage, printing, phone calls, and handling, can also be significantly reduced. EDI can aid in the support of manufacturing efforts, such as Just-in-Time and Third Party Warehousing, and financial efforts, such as Electronic Payments.
    What parts of the business cycle can be supported by EDI?
    Any business documents that are currently exchanged using paper can be converted to an EDI. Standards. Standards include ANSI X12 and XML/EDI are primarily used in the United States, while EDIFACT is used in Europe and Asia.
    How does EDI get started?
    EDI gets started when one company contacts another expressing interest in trading business documents electronically using Electronic Data Interchange. The two companies must first determine each other's EDI capabilities. If you do not already know your EDI capabilities, we have prepared a questionnaire to help you determine them. If you are already EDI capable, we will coordinate with your technical staff to determine a testing plan. Upon completion of testing the EDI documents, the appropriate business personnel will set a production start date to begin the exchange of EDI business data. If you are not EDI capable, we recommend you first obtain a commitment from your upper management. Your company will need to allocate resources and capital for software, hardware, testing, possible programming, and training.
    What is the flow of EDI?
    The flow of EDI depends on the sophistication of your systems and your EDI software. If you have internal purchasing/order entry systems, you will need interface programs that can extract and insert data out of and into these systems. EDI programs that interface with your internal systems are preferred over software that requires re-keying of data. Embassy Software specializes in seemless interface between EDI and your back office systems. Using a purchase order as an example of a business document your customer would send that PO electronically (850) to you. It could be sent either through a VAN (Value Added Network) or through an FTP server. You would take that 850 and convert it either into and ODBC database, a flat file or XML document to be imported into your Order System with the use of EDI Software such as PassportXchange.. Using EDI communication software, which is part of the PassportXchange package you would pull down data at set intervals from the VAN or FTP. These documents are then processed through EDI translation software and output to our order entry system. Finally, an EDI document called a functional acknowledgment (997) is sent to your customer.
    check this.
    [http://www.netweaverguru.com/EDI/HTML/IDocBook.htm]
    [http://www.sapgenie.com/sapedi/idoc_abap.htm]
    [http://www.sapgenie.com/sapedi/index.htm]
    [http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm]
    [https://www.2020software.com/products/Fourth_Shift_Edition_for_SAP_Business_One_Electronic_Data_Interchange.asp]
    [http://downloads-zdnet.com.com/SoftwareandWebDevelopment/SoftwareDevelopmentTools/ElectronicData+Interchange/]
    [http://www.erpgenie.com/sapedi/index.htm]
    [http://www.kostal.com/english/downloads/EDI_AGB_eng.pdfd]
    [ALE / IDOC / RFC / EDI]
    [SAP ABAP and EDI/ALE/IDOC]
    [Re: IDOC/BAPI/ALE/EDI]
    Regards,
    Dhruv Shah

  • Start-Process : This command cannot be run due to the error: The system cannot find the file specified.

    Hi, 
    I need some help with my script. It copies the file to the remote laptops but when it needs to install the .exe it fails.
    If I run 1 line at the time in Powershell ISE, then it works. Somebody has an idea why it doesn't work or can help me on the right way?
    Script: 
    $laptops = Get-Content -Path "C:\Users\bruyld01\Documents\STEPSTONE\Powershell\SAP\LaptopList.txt"
    foreach ($laptop in $laptops)
        Copy-Item "C:\Users\bruyld01\Desktop\SAP_Business_ByDesign_Add-In_for_Microsoft_Outlook_V5.exe" -Destination \\$laptop\C$\
        Enter-PSSession $laptop
        $version = Get-WmiObject -Class Win32_Product | where {$_.Name -like "*SAP Business*"} | Select-Object Version
        if ($version -ne "135.0.2071.1047")
            Start-Process -Filepath "C:\SAP_Business_ByDesign_Add-In_for_Microsoft_Outlook_V5.exe" -ArgumentList "/quiet"
        else
            Write-Host "SAP outlook add-in is up to date!" -ForegroundColor Green
        Exit-PSSession
    Error message:
    Start-Process : This command cannot be run due to the error: The system cannot find the file specified.
    At line:2 char:1
    + Start-Process -Filepath "C:\SAP_Business_ByDesign_Add-In_for_Microsoft_Outlook_V ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Start-Process], InvalidOperationException
        + FullyQualifiedErrorId : InvalidOperationException,Microsoft.PowerShell.Commands.StartProcessCommand
    Thanks, 
    Dimitri

    Hi,
    Enter-PSSession is used for interactive remote sessions. Look into Invoke-Command instead.
    http://ss64.com/ps/invoke-command.html
    Don't retire TechNet! -
    (Don't give up yet - 13,085+ strong and growing)

  • REG: Error in IDoc adapter outbound processing

    Hi All,
          I had a couple of doubts regarding these IDoc's.
    1)        I am dealing with the web services to IDoc Scenario. When i am activated my wed services it               is giving an error like
    "IDOC_ADAPTER.ATTRIBUTE_BE_NOT_SUPP" and "Only asynchronous processing supported for IDoc adapter outbound processing"
    Can any one help me to Solve my Problem
    2) How to find out whether the IDoc is of synchronous or Asynchronous mode
        and how to  handle the synchronous type of IDoc's
    Thanks in advance.
    with Regards,
    Kalyan Dannapaneni.

    Hi Kalyan,
    IDOCs are only Aynchronous (EO or EOIO).
    If you want to call Synchronious, you will have to find remote enabled function modules (RFCs, BAPIs).
    Or you have to use the ccBPM Synch-Async pattern to have an synchronos call passed to an IDoc, waiting for the Acknowledgement. In your situation I would check if a similar BAPI/RFC exists on your Backend SAP system.
    Best regards,
    Silvia

Maybe you are looking for