ALE Usage
How ALE will be useful in delivering data to the receier? cant we do that using EDI ? thanks in advance
Hi Lakshman,
I the basic difference between ALE and EDI will make things clear:
If we send data to an external partner, we generally speak of EDI, while ALE is a mechanism to reliable replicate data between trusting systems to store a redundant copy of the IDoc data. The difference is made clear, when we think of a purchase order that is sent as an IDoc. If we send the purchase order to a supplier then the supplier will store the purchase order as a sales order. However, if we send the purchase order via ALE to another R/3 system, then the receiving system will store the purchase order also as a purchase order.
Regards,
Gajendra.
Similar Messages
-
Hi Friends,
I have doubt which may seesm to be silly, but I am not clear with this concept ,, so could anyone of you walk me through this?Pleaseee
In SAP we have many technologies for talking with NON SAP Systems.
Lets say BDC, BAPI and BADI's ans also now we have ALE IDOC 's and EDI.
My doubt is , when do we go for ALE Technology , despite we having BAPI and BADI's for talking with the other legacy Systems.?
IF I was silly in my Questions, please bare with me , and help mein understanding the concepts.
Thanks in Advance
Regards
TinaWell, I have seen like when you have two systems and youre entraining data in one system and you want to in sink with other system , youll create distribution model , set up port and partner to send the data using message types. So when user change some data it creates the data and then using ALE you can update the other system. You can see all ALE transaction by going it tr.SALE.
You can also refer links :
http://www.sapgenie.com/ale/
http://www.thespot4sap.com/Articles/SAP_ALE_Introduction.asp
http://www.middlewarespectra.com/abstracts/8_95_07.htm
Hope thisll give you some clue.. Dont forget to award the points
Thanks
Saquib
Message was edited by: Saquib Khan -
Usage of ALE - idocs generated for BAPIs
Hi
I need to use - the std idocs generated for BUS2032 object - CREATEFROMDAT2 method to store the BAPI call ( BAPI_SALESORDER_CREATEFROMDAT2 )data for those sales orders that could not be created.
If I want to use the SAP delivered BAPI ( BAPI_SALESORDER_CREATEFROMDAT2 ) to call as it within an ABAP program - and then if the call did not go through - then log the data for BAPI into the corresponding idoc with the message type SALESORDER_CREATEFROMDAT2 ( idoc type SALESORDER_CREATEFROMDAT202 ) do I need to move the values from the BAPI structures to the idoc segments programatically ? Or since the idoc is linked to the BAPI - by definition, is there an implicit way to move data to the corresponding idoc segments and save the idoc .
Can anyone out there give me a code sample to do - what I have asked above ?Hi,
I guess you can use function module ALE_SALESORDER_CREATEFROMDAT2 to create idoc from bapi data. You can pass the entire data in internal tables that you are passing to BAPI into above mentioned function module and then it will create an Idoc for the same. Also populate the receivers in the internal table receiver.
KR Jaideep, -
ALE Transactional and VA01 Again
Dear Friends
Some of you gives me good links fordocumentation but after customizing and done a lot of thing I can't have an automatic IDOC when I create a sale order via VA01.
As it was explain in the documentation I have written a module function and done a lot of thing but nothing appens.
With an user exit SAPMVFZZ I can create the IDOC and it well sent to the good port. So BD64 is good.
==========================================================
<b>Table NAST is not filled up when I create an Sales order.</b>
==========================================================
Here after a resume of what I heve done.
If you have a good idea and may be you know why no IDOC when I create an Sales order, you are wellcome.
1. OUTBOUND PROCESSING
1.1. Create IDoc type (WE30) Client independent
IDoc type ZSALES01
To create the IDoc type, follow these next few steps:
Enter transaction WE30 (ALE -> Extensions -> IDoc types -> Maintain IDoc type)
Type in ZSALES01 and click on Basic IDoc type, click the Create icon
EC1VBAK (father) and two sons
EC1VBAP Enter EC1VBA2
1.2. Create message type (WE81) Client independent
To create a new message type, follow these next few steps:
Enter transaction WE81 (ALE -> ALE Development -> IDoc -> IDoc types Development -> WE81 logical messages ZORDER01
Save and exit.
1.3. Link message to IDoc type (WE82 & BD69) Client independent
To link the message types to the IDoc type follow these next few steps:
Enter transaction WE82 (ALE -> ALE Development -> IDoc -> IDoc types Development -> WE82 IDoc Type for message
Enter the message type ZORDER01 and the Basic IDoc type as ZSALES01
Save and exit the result is set in SAP table EDIMSG
1.4. Transaction NACE / NACT
Creation of OUTPUT TYPE Z001 for application V1.
Access sequence 004 = SalesOrg/Sales Order Type
<b>Default Value</b>
Dispatch time send immediately
Transmission Medium Distribution ALE
<b>Time</b>
Timing 2 is set off Job and time entry
Condition table 5 has been generated.
Consistency check for output control all is OK
Assignment output type to partner function In the IMG
Creation of Procedure Z00001 OUTPUT FOR IDOC ZSALES01 for Usage B and application V1
The control procedure: control type z001 requirement 2 (Order confirmation)
1.5. Assign Output type to partner function
Z001 A SP (sold to party)
Transaction V/43 assign Output determination Procedure
Allocate Sales Document header
Sale doc type OR Output procedure Z00001 Output type Z001
1.6. Transaction WE20
Partner profile
Partner number 0000000001
Partner type KU
Partner role SP
Message type ZORDER01
Partner status Actif
Output options
Port A000000002
Pack size 1
Transfer IDOC Immediate YES
Cancel processing after syntax error YES
IDOC Type Basic type ZSALES01
Message control
Application V1
Process code ZVA01
Message type z001
Result of checking (program RSECHK07) with partner 0000000001 and partner type KU: All OK
Table EDP13, table EDP12 message control are well filled up.
A module function is created with the good parameters ZSALESORDERIDOC
The process code point to a function ZSALESORDERIDOC (transaction WE41) Outbound process code
Process code ZVA01 Linked to module function ZSALESORDERIDOC processing with ALE service
Function module version 3.0
Table EDIMSG Output Types and Assignment to IDoc Types give
Message type ZORDER01 Basic type ZSALES01 release 50A
Enter transaction BD69 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Assign message type to IDoc for ALE)
Enter the message type ZORDER01 and the Basic IDoc type as ZSALES01
1.7. Maintain object type for message type (BD59) Client independent
Type in your message type ZORDER01 and press enter
Enter your object type, KUNNR (We need to use the customer as a filter object), the segment name where KUNNR resides, EC1VBAK, a number 1 for the sequence followed by the actual field name KUNNR
1.8. Configuring the Distribution Model BD64
This task is performed on your ALE reference client.
Manual Configuration (BD64) Client dependent
Create a new model. (Create model POCALE)
POC ALE to send Outbound Idoc POCALE
Choose the receiving systems to which the sending system must forward message type ZORDER01 to.
We have generated the model view after creation.He Ferry,
I try your checking and with VA02 -> Enter <sales order> -> Enter -> Extras -> Output -> Header -> Edit.
The system propose me Z001 when I click on OUTPUT TYPE (F4).
I have selected Z001 and submit. The following message comes "Processing program missing for output Z001 " ==> "No processing program is defined in table TNAPR for output type Z001 (transmission medium A) in application V1."
In transaction NACE for V1 and OUTPUT type, in TAB Processing routine I can add one program and Form routine.
The module function created zsalesorderidoc has generated a program (SE38) ZSALESORDERIDOC===============FT
Is this one I have to use or I have to create a special one? If I have to create one may I have a model?
In the program ZSALESORDERIDOC===============FT we have these FORM.
FORM EXISTENCE_CHECK CHANGING VARIA.
FORM FUNCTION_CALL.
FORM CLEAR_DATA.
FORM CLEAR_TABLE.
FORM DELETE_LINE USING KEY INDEX.
FORM INIT_EXCEPTIONS USING NAME.
FORM PARAM_ACCESS_TYPES USING KEY DEST P_MODE P_UPPER.
FORM PARAMETER_SET USING NAME DIRECTION VALUE.
PERFORM CB_CALLBACK_VALUE_SET(SAPLSEUJ)
USING VALUE
CHANGING %_IOBJECT.
FORM PARAMETER_GET USING NAME DIRECTION
CHANGING VALUE
OLD_VALUE.
FORM PARAMETER_TABLE_SET USING NAME VALUE.
FORM PARAMETER_TABLE_GET USING NAME
CHANGING VALUE.
FORM PARAMETER_DESCRIBE USING CBPROG
NAME.
FORM PARAMETER_CONTAINER TABLES LCONT STRUCTURE SWCONT
USING NAME
DIRECTION .
FORM TABLES_CONTAINER TABLES LCONT STRUCTURE SWCONT
USING NAME
DIRECTION.
FORM SET_VARIABLES USING KEY VALUE.
FORM GET_VARIABLES USING KEY
CHANGING VALUE.
FORM PARAMETER_READ_INPUT USING NAME
KEY
CHANGING VALUE.
FORM PARAMETER_READ_OUTPUT USING NAME
KEY
CHANGING VALUE.
FORM PARAMETER_COMPARE USING NAME
CHANGING VALUE.
FORM EXPORT_IMPORT_MEMORY USING SEL KEY STRUCTURE EXPORTKEY.
FORM EXPORT_IMPORT USING SEL KEY STRUCTURE D102N_EXPORTKEY.
FORM GET_EXCEPTION_DIFFERENCE
FORM COMPARE_DATA
TABLES DIFFERENCES STRUCTURE UNTERSCHIED
USING FIELD
CHANGING RETCODE.
Thank you for All
Best regards
Henri -
Hello Everyone,
We currently run payroll and process ACH payment information via RFFOUS_T. The information is sent directly to the bank. We have a new request which will require HR Payroll payment information to be sent from our SAP system to another SAP system via ALE/IDOC. Does anyone have any documentation which offers an explanation as to how Payroll processes payment information ALE/IDOC.
I have found a few references to PC00_M08_CDTA, RFFOEDI1, type PEXR2002/PEXR2003 etc, but nothing that brings it all together. The process seems to be fairly standard and should be easy to implement (RFC, partner profile, etc). I am ultimately looking for a best practices or some other document which brings everything together and indicates which transactions the user must execute.
Thank you for your help.
ScottHi,
Please use SAP help link below which gives you idea about ALE connection set-up and IDOC segment usage.
http://help.sap.com/printdocu/core/print46c/en/data/pdf/CABFAIS/CABFAIS.pdf
Thanks,
Ameet -
Import oracle.bpel.worklistapp.dc.ale.beans.view.* not found
Hello experts,
JDeveloper cannot find the classes below:
import oracle.bpel.worklistapp.dc.ale.beans.view.ApprovalListEditorComp;
import oracle.bpel.worklistapp.dc.ale.util.ApprovalListUtil;
Any hints about locating these classes?
Thanks in advance!
About
Oracle JDeveloper 11g Release 1 11.1.1.4.0
Studio Edition Version 11.1.1.4.0
Build JDEVADF_11.1.1.4.0_GENERIC_101227.1736.5923
Copyright © 1997, 2011 Oracle and/or its affiliates. All rights reserved.
IDE Version: 11.1.1.4.37.59.23
Product ID: oracle.jdeveloper
Product Version: 11.1.1.4.37.59.23
Version
Component Version
========= =======
ADF Business Components 11.1.1.59.23
BPMN Editor 11.1.1.4.0.5682
Java(TM) Platform 1.6.0_24
Oracle IDE 11.1.1.4.37.59.23
SOA Composite Editor 11.1.1.4.0.56.82
Versioning Support 11.1.1.4.37.59.23
Extensions
Name Identifier Version Status
==== ========== ======= ======
ADF Business Components oracle.BC4J 11.1.1.4.37.59.23 Loaded
ADF Business Components Dependency oracle.bc4j.dependency 11.1.1.4.37.59.23 Loaded
ADF Business Components Deployment oracle.bc4jdt.deploy 11.1.1.4.37.59.23 Loaded
ADF Business Components Modeler oracle.adfbcdt.modeler 11.1.1.4.37.59.23 Loaded
ADF Business Components Syscat oracle.bc4j.syscat 0 Loaded
ADF Business Components Tester oracle.bc4j.tester 11.1.1.4.37.59.23 Loaded
ADF Common Audit oracle.adf.common.audit 0 Loaded
ADF Context Debugger oracle.adf.share.debug 11.1.1.4.37.59.23 Loaded
ADF Controller Configuration Design Time oracle.adf.controller.config.dt 11.1.1.4.37.59.23 Loaded
ADF Data Visualizations Design Time Tests oracle.dvt.dt 11.1.1.4.37.59.23 Loaded
ADF Debugger oracle.adf.debug 11.1.1.4.37.59.23 Loaded
ADF Debugger Diagram Support oracle.adf.debug.diagram 11.1.1.4.37.59.23 Loaded
ADF Desktop Integration Design Time oracle.adfdt.desktopintegration 11.1.1.4.37.59.23 Loaded
ADF Faces Cache oracle.webcache 11.1.1.4.37.59.23 Loaded
ADF Faces Data Visualization Tools Help oracle.dvt-faces-doc 11.1.1.0.0 Loaded
ADF Faces Databinding Design Time oracle.adf-faces-databinding-dt 11.1.1.4.37.59.23 Loaded
ADF Faces Design Time oracle.adf-faces-dt 11.1.1.4.37.59.23 Loaded
ADF Faces Design Time Migration oracle.adffacesdt.migration 11.1.1.4.37.59.23 Loaded
ADF Faces Runtime Help oracle.adf-faces-rt-doc 11.1.1.0.0 Loaded
ADF Faces Skin Design Time oracle.adf-faces-skin-dt 11.1.1.4.37.59.23 Loaded
ADF JMX Data Control Designtime oracle.adf.jmxdc 11.1.1.4.37.59.23 Loaded
ADF Java Server Faces Diagram oracle.adf.jsf.diagram 11.1.1.4.37.59.23 Loaded
ADF Library Design Time oracle.jdeveloper.adflibrary 11.1.1.4.37.59.23 Loaded
ADF Lifecycle Design Time oracle.adf.lifecycle.dt 11.1.1.4.37.59.23 Loaded
ADF Management Pages oracle.adf.management 11.1.1.4.37.59.23 Loaded
ADF Menu Model Design-Time oracle.adfmenudt 11.1.1.4.37.59.23 Loaded
ADF Page Flow Design Time oracle.adf.pageflow.dt 11.1.1.4.37.59.23 Loaded
ADF Page Flow Design Time Extras oracle.adf.pageflow.dt.extras 11.1.1.4.37.59.23 Loaded
ADF Page Template DT oracle.adf-faces-templating-dt 11.1.1.4.37.59.23 Loaded
ADF Region Design Time oracle.adf-faces-region-dt 11.1.1.4.37.59.23 Loaded
ADF Struts Page Flow Modeler oracle.struts.adf 11.1.1.4.37.59.23 Loaded
ADF Struts and Model One Databinding oracle.adf.struts.and.model.one.databinding.dt 11.1.1.4.37.59.23 Loaded
ADF Swing oracle.adfdt.swingcore 11.1.1.4.37.59.23 Loaded
ADF View Debugging Design Time adf.view.debugging.dt 11.1.1.4.37.59.23 Loaded
ADFv Common Databinding oracle.adf-view-databinding-dt 11.1.1.4.37.59.23 Loaded
Ant oracle.ant 11.1.1.4.37.59.23 Loaded
Application Server Manager oracle.jdeveloper.asnav 11.1.1.4.37.59.23 Loaded
Application State - Application Navigator oracle.ideimpl.appstate.appnav 11.1.1.4.37.59.23 Loaded
Application State - Editors oracle.ide.appstate.editors 11.1.1.4.37.59.23 Loaded
Application State Manager oracle.ide.appstate 11.1.1.4.37.59.23 Loaded
Archive Compare oracle.jdeveloper.archive-compare 11.1.1.4.37.59.23 Loaded
BAM oracle.bam 11.1.1 Loaded
BI Beans Graph oracle.bibeans 11.1.1.4.37.59.23 Loaded
BM metamodel framework oracle.bm.meta 11.1.1.4.37.59.23 Loaded
Bug Reporter oracle.jdeveloper.bugfiler 11.1.1.4.37.59.23 Loaded
Business Modelers oracle.bm 11.1.1.4.37.59.23 Loaded
Check For Updates oracle.ide.webupdate 11.1.1.4.37.59.23 Loaded
Code Editor oracle.ide.ceditor 11.1.1.4.37.59.23 Loaded
Command Line Formatting Support oracle.jdeveloper.ojformat 11.1.1.4.37.59.23 Loaded
Command Line Make/Rebuild Support oracle.jdevimpl.oj-compiler 11.1.1.4.37.59.23 Loaded
Common Controller Design-Time oracle.controller.dt 11.1.1.4.37.59.23 Loaded
Common Page Flow Design-Time oracle.pageflow.dt 11.1.1.4.37.59.23 Loaded
Component Palette oracle.ide.palette1 11.1.1.4.37.59.23 Loaded
Controller to ADF Bindings Bridge oracle.controller.bindings.dt 11.1.1.4.37.59.23 Loaded
Database Connection Support oracle.jdeveloper.db.connection 11.1.1.4.37.59.23 Loaded
Database Features (JDeveloper) oracle.jdeveloper.db 11.1.1.4.37.59.23 Loaded
Database Features (SQLDeveloper in JDeveloper) oracle.jdeveloper.db.navigator 11.1.1.4.37.59.23 Loaded
Database Modeler oracle.dbmodeler 11.1.1.4.37.59.23 Loaded
Database Modeler Migration oracle.dbmodeler.migrate 11.1.1.4.37.59.23 Loaded
Database Object Dependency API Support oracle.jdeveloper.db.dependency 11.1.1.4.37.59.23 Loaded
Database Object Explorers oracle.ide.db.explorer 11.1.1.4.37.59.23 Loaded
Database Object Transfer Framework oracle.jdeveloper.db.transfer 11.1.1.4.37.59.23 Loaded
Database UI oracle.ide.db 11.1.1.4.37.59.23 Loaded
Design Time Resource Bundle Variable Resolver oracle.jdeveloper.resourcebundle.resolver.dt 11.1.1.4.37.59.23 Loaded
Diagram Framework oracle.diagram 11.1.1.4.37.59.23 Loaded
Diagram Framework Toplink extensions oracle.diagram.toplink 11.1.1.4.37.59.23 Loaded
Diagram Javadoc Extension oracle.diagram.javadoc 11.1.1.4.37.59.23 Loaded
Diagram Thumbnail oracle.diagram.thumbnail 11.1.1.4.37.59.23 Loaded
Diagram to XMLEF Bridge oracle.diagram.xmlef 11.1.1.4.37.59.23 Loaded
Diff/Merge oracle.ide.diffmerge 11.1.1.4.37.59.23 Loaded
EJB oracle.ejb 11.1.1.4.37.59.23 Loaded
EJB Modeler oracle.ejbmodeler 11.1.1.4.37.59.23 Loaded
Editor Tint oracle.ide.ceditor-tint 11.1.1.4.37.59.23 Loaded
Editor Tint (Java) oracle.jdeveloper.ceditor-tint-java 11.1.1.4.37.59.23 Loaded
Extended IDE Platform oracle.javacore 11.1.1.4.37.59.23 Loaded
Extension Designtime Core oracle.jdeveloper.extensiondt.core 11.1.1.4.37.59.23 Loaded
Extension Designtime UI oracle.jdeveloper.extensiondt.ui 11.1.1.4.37.59.23 Loaded
External Tools oracle.ide.externaltools 11.1.1.4.37.59.23 Loaded
Feedback oracle.ide.feedback 11.1.1.4.37.59.23 Loaded
File Support oracle.ide.files 11.1.1.4.37.59.23 Loaded
Fusion Application Overview Definition oracle.ide.appoverview.fusion.definition 11.1.1.4.37.59.23 Loaded
Fusion Web Application (ADF) Template oracle.adf.webapp.template 11.1.1.4.37.59.23 Loaded
Go to File oracle.ide.gotofile 11.1.1.4.37.59.23 Loaded
Go to Java Type oracle.jdeveloper.gotojava 11.1.1.4.37.59.23 Loaded
HTML oracle.html 11.1.1.4.37.59.23 Loaded
Help System oracle.ide.help 11.1.1.4.37.59.23 Loaded
History Support oracle.jdeveloper.history 11.1.1.4.37.59.23 Loaded
IDE Reports Extension oracle.ide.report 11.1.1.4.37.59.23 Loaded
Import/Export Support oracle.ide.importexport 11.1.1.4.37.59.23 Loaded
Index Migrator support oracle.ideimpl.indexing-migrator 11.1.1.4.37.59.23 Loaded
J2EE oracle.j2ee 11.1.1.4.37.59.23 Loaded
J2EE oracle.j2ee.webapp.ve 11.1.1.4.37.59.23 Loaded
J2EE oracle.j2ee.webapp.ve.facelets 11.1.1.4.37.59.23 Loaded
J2EE CSS oracle.css 11.1.1.4.37.59.23 Loaded
J2EE Faces Config oracle.j2ee.facesconfig 11.1.1.4.37.59.23 Loaded
J2EE Web App oracle.j2ee.webapp 11.1.1.4.37.59.23 Loaded
J2EE-ADRS oracle.j2ee.adrs 11.1.1.4.37.59.23 Loaded
J2ee extension help oracle.j2ee.help 11.1.1.0.0 Loaded
JDeveloper oracle.jdeveloper 11.1.1.4.37.59.23 Loaded
JDeveloper Runner oracle.jdeveloper.runner 11.1.1.4.37.59.23 Loaded
JGoodies Forms oracle.jdeveloper.jgoodies 11.1.1.4.37.59.23 Loaded
JPublisher oracle.jdeveloper.db.jpub 11.1.1.4.37.59.23 Loaded
JSON Language support oracle.jdeveloper.json 11.1.1.4.37.59.23 Loaded
JUnit Integration oracle.jdeveloper.junit 11.1.1.4.37.59.23 Loaded
JViews Registration Addin oracle.diagram.registration 11.1.1.4.37.59.23 Loaded
Java Annotation Inspector oracle.jdeveloper.annotation.inspector 11.1.1.4.37.59.23 Loaded
Java Breadcrumbs oracle.jdeveloper.ceditor-breadcrumbs-java 11.1.1.4.37.59.23 Loaded
Java Class Modeler oracle.javamodeler 11.1.1.4.37.59.23 Loaded
Java Modeler Toplink extensions oracle.javamodeler.toplink 11.1.1.4.37.59.23 Loaded
Java Server Faces Page Flow Modeler oracle.jsfmod 11.1.1.4.37.59.23 Loaded
Java Structure Compare oracle.jdeveloper.java-compare 11.1.1.4.37.59.23 Loaded
Java Type Search oracle.jdeveloper.searchbar.java 11.1.1.4.37.59.23 Loaded
Java extension help oracle.java.help 11.1.1.0.0 Loaded
JavaBeans, Swing, and AWT oracle.swingawt 11.1.1.4.37.59.23 Loaded
JavaScript Language Support oracle.ide.javascript 11.1.1.4.37.59.23 Loaded
Jdeveloper UI Editor oracle.jdeveloper.uieditor 11.1.1.4.37.59.23 Loaded
Jdeveloper XML Extension oracle.jdeveloper.xml 11.1.1.4.37.59.23 Loaded
Legacy Controller Design-Time oracle.controller.bm.dt 11.1.1.4.37.59.23 Loaded
Legacy Preferences integration for BM oracle.modeler.bm.prefs 11.1.1.4.37.59.23 Loaded
Log Window oracle.ide.log 11.1.1.4.37.59.23 Loaded
MDS Extension oracle.mds 11.1.1.4.37.59.23 Loaded
MOF Ide Integration oracle.mof.ide 11.1.1.4.37.59.23 Loaded
MOF Modeler Integration oracle.modeler.mof 11.1.1.4.37.59.23 Loaded
Mac OS X Adapter oracle.ideimpl.apple 11.1.1.4.37.59.23 Loaded
Modeler Framework oracle.modeler 11.1.1.4.37.59.23 Loaded
Modeler Framework Common Layer oracle.modeler.common 11.1.1.4.37.59.23 Loaded
Modelling migration from BM oracle.modeler.bm.migrate 11.1.1.4.37.59.23 Loaded
Navigator oracle.ide.navigator 11.1.1.4.37.59.23 Loaded
Nightly Indexing support oracle.ideimpl.indexing-rt 11.1.1.4.37.59.23 Loaded
OAR/MAR/SAR Deployment Support Extension oracle.deploy.orapp 11.1.1.4.37.59.23 Loaded
OWSM Policy Manager Installer oracle.jdeveloper.webservice.wsmpm.installer 11.1.1.4.37.59.23 Loaded
Object Gallery oracle.ide.gallery 11.1.1.4.37.59.23 Loaded
Object Viewer oracle.sqldeveloper.oviewer 11.1.1.64.46 Loaded
Offline Database oracle.jdeveloper.offlinedb 11.1.1.4.37.59.23 Loaded
Offline Database Import/Generate oracle.jdeveloper.offlinedb.transfer 11.1.1.4.37.59.23 Loaded
Offline Database Reports Extension oracle.jdeveloper.offlinedb.report 11.1.1.4.37.59.23 Loaded
Offline Database SXML oracle.jdeveloper.offlinedb.sxml 11.1.1.4.37.59.23 Loaded
Offline Database User Properties oracle.jdeveloper.offlinedb.userprops 11.1.1.4.37.59.23 Loaded
Offline Database User Properties SXML oracle.jdeveloper.offlinedb.userprops.sxml 11.1.1.4.37.59.23 Loaded
Oracle BPEL 1.1 Designer oracle.bpel.v1.designer 11.1.1.4.0.56.82 Loaded
Oracle BPEL 1.1 Designer Plugins oracle.bpel.v1.designer.plugins 11.1.1.4.0.56.82 Loaded
Oracle BPEL 2.0 Designer oracle.bpel.v2.designer 11.1.1.4.0.56.82 Loaded
Oracle BPEL 2.0 Designer Plugins oracle.bpel.v2.designer.plugins 11.1.1.4.0.56.82 Loaded
Oracle BPEL Designer Shared Code oracle.bpel.designer.shared 11.1.1.4.0.56.82 Loaded
Oracle BPM DVM oracle.bpm.dvm 11.1.1.4.0.56.82 Loaded
Oracle BPM Internal oracle.bpm.fusion.internal 11.1.1.4.0.5682 Loaded
Oracle BPM Internal oracle.bpm.resources 11.1.1.0.30.50.25 Loaded
Oracle BPM Internal ar oracle.bpm.resourcesrt-ar 11.1.1.0.30.50.25 Loaded
Oracle BPM Internal cs oracle.bpm.resourcesrt-cs 11.1.1.0.30.50.25 Loaded
Oracle BPM Internal da oracle.bpm.resourcesrt-da 11.1.1.0.30.50.25 Loaded
Oracle BPM Internal de oracle.bpm.resourcesrt-de 11.1.1.0.30.50.25 Loaded
Oracle BPM Internal el oracle.bpm.resourcesrt-el 11.1.1.0.30.50.25 Loaded
Oracle BPM Internal en oracle.bpm.resources-en 11.1.1.0.30.50.25 Loaded
Oracle BPM Internal es oracle.bpm.resourcesrt-es 11.1.1.0.30.50.25 Loaded
Oracle BPM Internal fi oracle.bpm.resourcesrt-fi 11.1.1.0.30.50.25 Loaded
Oracle BPM Internal fr oracle.bpm.resourcesrt-fr 11.1.1.0.30.50.25 Loaded
Oracle BPM Internal hu oracle.bpm.resourcesrt-hu 11.1.1.0.30.50.25 Loaded
Oracle BPM Internal it oracle.bpm.resourcesrt-it 11.1.1.0.30.50.25 Loaded
Oracle BPM Internal iw oracle.bpm.resourcesrt-iw 11.1.1.0.30.50.25 Loaded
Oracle BPM Internal ja oracle.bpm.resources-ja 11.1.1.0.30.50.25 Loaded
Oracle BPM Internal ko oracle.bpm.resourcesrt-ko 11.1.1.0.30.50.25 Loaded
Oracle BPM Internal nl oracle.bpm.resourcesrt-nl 11.1.1.0.30.50.25 Loaded
Oracle BPM Internal no oracle.bpm.resourcesrt-no 11.1.1.0.30.50.25 Loaded
Oracle BPM Internal pl oracle.bpm.resourcesrt-pl 11.1.1.0.30.50.25 Loaded
Oracle BPM Internal pt oracle.bpm.resourcesrt-pt 11.1.1.0.30.50.25 Loaded
Oracle BPM Internal pt_BR oracle.bpm.resourcesrt-pt_BR 11.1.1.0.30.50.25 Loaded
Oracle BPM Internal ro oracle.bpm.resourcesrt-ro 11.1.1.0.30.50.25 Loaded
Oracle BPM Internal ru oracle.bpm.resourcesrt-ru 11.1.1.0.30.50.25 Loaded
Oracle BPM Internal sk oracle.bpm.resourcesrt-sk 11.1.1.0.30.50.25 Loaded
Oracle BPM Internal sv oracle.bpm.resourcesrt-sv 11.1.1.0.30.50.25 Loaded
Oracle BPM Internal th oracle.bpm.resourcesrt-th 11.1.1.0.30.50.25 Loaded
Oracle BPM Internal tr oracle.bpm.resourcesrt-tr 11.1.1.0.30.50.25 Loaded
Oracle BPM Internal zh_CN oracle.bpm.resourcesrt-zh_CN 11.1.1.0.30.50.25 Loaded
Oracle BPM Internal zh_TW oracle.bpm.resourcesrt-zh_TW 11.1.1.0.30.50.25 Loaded
Oracle BPM Studio oracle.bpm.fusion.core 11.1.1.4.0.5682 Loaded
Oracle BPM Studio oracle.bpm.fusion.repository 11.1.1.4.0.5682 Loaded
Oracle BPM Studio oracle.bpm.fusion.builder 11.1.1.4.0.5682 Loaded
Oracle BPM Studio oracle.bpm.fusion.ui 11.1.1.4.0.5682 Loaded
Oracle BPM Studio oracle.bpm.fusion.studio 11.1.1.4.0.5682 Loaded
Oracle BPM Studio oracle.bpm.tests.jdev-test 11.1.1.4.0.5682 Loaded
Oracle BPM Studio oracle.bpm.fusion.jdeveloper 11.1.1.4.0.5682 Loaded
Oracle BPM Studio oracle.bpm.fusion.fcp 11.1.1.4.0.5682 Loaded
Oracle BPM Studio oracle.bpm.fusion.designer 11.1.1.4.0.5682 Loaded
Oracle BPM Studio SOA Extension oracle.bpm.fusion.soa 11.1.1.4.0.5682 Loaded
Oracle BPM XREF oracle.bpm.xref 11.1.1.4.0.56.82 Loaded
Oracle Business Rules Designer oracle.bpm.rules 11.1.1.4.0.56.82 Loaded
Oracle Database Browser oracle.sqldeveloper.thirdparty.browsers 11.1.1.64.46 Loaded
Oracle Enterprise Repository Editor oracle.jdeveloper.oereditor 11.1.1.4.37.59.23 Loaded
Oracle Events Designer oracle.bpm.events 11.1.1.4.0.56.82 Loaded
Oracle Fabric Plugins oracle.sca.modeler.plugins 11.1.1.4.0.56.82 Loaded
Oracle Human Task Designer oracle.bpm.workflow 11.1.1.4.0.56.82 Loaded
Oracle IDE oracle.ide 11.1.1.4.37.59.23 Loaded
Oracle JDeveloper Spring, WebLogic SCA Integration oracle.jdeveloper.spring 11.1.1.4.37.59.23 Loaded
Oracle JDevloper Deployment Core Module oracle.deploy.core 11.1.1.4.37.59.23 Loaded
Oracle MDS Design time oracle.mds.dt 11.1.1.4.37.59.23 Loaded
Oracle Mobile ADF oracle.wireless.dt 11.1.1.4.37.59.23 Loaded
Oracle Page Templates oracle.adf-page-template-samples 11.1.1.4.37.59.23 Loaded
Oracle SOA Composite Editor oracle.sca.modeler 11.1.1.4.0.56.82 Loaded
Oracle SOA Mediator oracle.sca.mediator 11.1.1.4.0.56.82 Loaded
Oracle SQL Developer oracle.sqldeveloper 11.1.1.64.46 Loaded
Oracle SQL Developer Reports oracle.sqldeveloper.report 11.1.1.64.46 Loaded
Oracle SQL Developer Worksheet oracle.sqldeveloper.worksheet 11.1.1.64.46 Loaded
Oracle User Messaging Service Client Extension oracle.ums.jdev 11.1.1.4.0 Loaded
Oracle XML Schema Support oracle.sqldeveloper.xmlschema 11.1.1.64.46 Loaded
PL/SQL Debugger oracle.jdeveloper.db.debug.plsql 11.1.1.4.37.59.23 Loaded
PROBE Debugger oracle.jdeveloper.db.debug.probe 11.1.1.4.37.59.23 Loaded
Peek oracle.ide.peek 11.1.1.4.37.59.23 Loaded
Persistent Storage oracle.ide.persistence 11.1.1.4.37.59.23 Loaded
Profiler oracle.jdeveloper.profiler 11.1.1.4.37.59.23 Loaded
Properties File Support oracle.jdeveloper.props 11.1.1.4.37.59.23 Loaded
Property Inspector oracle.ide.inspector 11.1.1.4.37.59.23 Loaded
Quick Start Features for Web Applications quickstart.webapp.dt 11.1.1.4.37.59.23 Loaded
QuickDiff oracle.ide.quickdiff 11.1.1.4.37.59.23 Loaded
REST Web Services oracle.jdeveloper.webservice.rest 11.1.1.4.37.59.23 Loaded
Refactoring oracle.jdeveloper.refactoring 11.1.1.4.37.59.23 Loaded
Replace With oracle.ide.replace 11.1.1.4.37.59.23 Loaded
Reports Extension oracle.javatools.report 11.1.1.4.37.59.23 Loaded
Resource Bundle Support oracle.ide.resourcebundle 11.1.1.4.37.59.23 Loaded
Resource Bundle Support for Properties Files oracle.jdeveloper.resourcebundle.props 11.1.1.4.37.59.23 Loaded
Resource Catalog Application Server Adapter oracle.jdeveloper.asadapter 11.1.1.4.37.59.23 Loaded
Resource Catalog DB UI extension oracle.jdeveloper.db.rcadapter.ui 11.1.1.4.37.59.23 Loaded
Resource Catalog Database Adapter oracle.jdeveloper.rcdbadapter 11.1.1.4.37.59.23 Loaded
Resource Catalog WSIL Adapter oracle.jdeveloper.rcwsiladapter 11.1.1.4.37.59.23 Loaded
Resource Lookup oracle.jdeveloper.rclookup 11.1.1.4.37.59.23 Loaded
Runner oracle.ide.runner 11.1.1.4.37.59.23 Loaded
SQL*Plus Integration oracle.jdeveloper.db.sqlplus 11.1.1.4.37.59.23 Loaded
SQLJ oracle.jdeveloper.sqlj 11.1.1.4.37.59.23 Loaded
Search Bar oracle.ide.searchbar 11.1.1.0.0 Loaded
SearchBar Commands oracle.ide.searchbar.commands 11.1.1.4.37.59.23 Loaded
Searchbar Preferences oracle.ide.searchbar.preferences 11.1.1.4.37.59.23 Loaded
Snippet Window oracle.sqldeveloper.snippet 11.1.1.64.46 Loaded
Struts Page Flow Modeler oracle.struts 11.1.1.4.37.59.23 Loaded
Studio oracle.studio 11.1.1.4.37.59.23 Loaded
Studio extension help oracle.studio.help 11.1.1.0.0 Loaded
Template oracle.ide.ceditor-template 11.1.1.4.37.59.23 Loaded
TopLink oracle.toplink 11.1.1.4.37.59.23 Loaded
Trinidad Databinding Design Time oracle.trinidad-databinding-dt 11.1.1.4.37.59.23 Loaded
Trinidad Design Time oracle.trinidad-dt 11.1.1.4.37.59.23 Loaded
UDDI Resource Catalogue Provider oracle.jdevimpl.uddiadapter 11.1.1.4.37.59.23 Loaded
UML XMI oracle.uml.v2.xmi 11.1.1.4.37.59.23 Loaded
UML v2 oracle.uml.v2 11.1.1.4.37.59.23 Loaded
UML v2 Activity Modeler oracle.uml.v2.activity 11.1.1.4.37.59.23 Loaded
UML v2 Class Diagram oracle.uml.v2.clazz 11.1.1.4.37.59.23 Loaded
UML v2 Migration oracle.uml.v2.migrate 11.1.1.4.37.59.23 Loaded
UML v2 Sequence Diagram oracle.uml.v2.sequence 11.1.1.4.37.59.23 Loaded
UML v2 Transformation to Java oracle.uml.v2.umljava 11.1.1.4.37.59.23 Loaded
UML v2 Use Case Diagram oracle.uml.v2.usecase 11.1.1.4.37.59.23 Loaded
UML2 Modelers Common Classes oracle.uml.v2.modeler 11.1.1.4.37.59.23 Loaded
URL Connection Designtime oracle.jdevimpl.urlconn 0 Loaded
VHV oracle.ide.vhv 11.1.1.4.37.59.23 Loaded
Versioning Support oracle.jdeveloper.vcs 11.1.1.4.37.59.23 Loaded
Versioning Support for Subversion oracle.jdeveloper.subversion 11.1.1.4.37.59.23 Disabled by user
Virtual File System oracle.ide.vfs 11.1.1.4.37.59.23 Loaded
WSDL Chooser oracle.jdeveloper.wsdllookup 11.1.1.0.0 Loaded
WSDL web services extension oracle.jdevimpl.wsdl 11.1.1.4.37.59.23 Loaded
Web Browser and Proxy oracle.ide.webbrowser 11.1.1.4.37.59.23 Loaded
Web Services oracle.jdeveloper.webservice 11.1.1.4.37.59.23 Loaded
WebDAV Connection Support oracle.jdeveloper.webdav2 11.1.1.4.37.59.23 Loaded
WebStart oracle.j2ee.webstart 11.1.1.0.0 Loaded
XML Compare oracle.jdeveloper.xml-compare 11.1.1.4.37.59.23 Loaded
XML Editing Framework IDE Extension oracle.ide.xmlef 11.1.1.4.37.59.23 Loaded
XML Editing Framework Java Integration oracle.jdeveloper.xmlef 11.1.1.4.37.59.23 Loaded
XSL Mapper oracle.bpm.mapper 11.1.1.4.0.56.82 Loaded
adf-deploy-dt oracle.adfdt.common.deploy 11.1.1.4.37.59.23 Loaded
adf-deploy-dt-mds oracle.adfdt.common.deploy.mds 11.1.1.4.37.59.23 Loaded
adf-installer-ide adf.installer.dt 11.1.1.4.37.59.23 Loaded
adf-logging-dt oracle.adf.logging.dt 11.1.1.4.37.59.23 Loaded
adf-model-debugger-dt oracle.adf-model-debugger-dt 11.1.1.4.37.59.23 Loaded
adf-model-sqldc-ide oracle.adfm.sqldc 11.1.1.4.37.59.23 Loaded
adf-model-tools oracle.adf.model.tools 11.1.1.4.37.59.23 Loaded
adf-security-policy-dt oracle.adfdtinternal.adf-security-policy-dt 11.1.1.4.37.59.23 Loaded
adf-share-audit oracle.adf-share-audit 11.1.1.4.37.59.23 Loaded
adf-share-deploy-dt oracle.adf.share.deploy.dt 11.1.1.4.37.59.23 Loaded
adf-share-dt oracle.adf.share.dt 11.1.1.4.37.59.23 Loaded
adfm-business-editor-deploy oracle.adf.businesseditor.deploy 11.1.1.4.37.59.23 Loaded
adfm-business-editor-ide oracle.adf.model.businesseditor 11.1.1.4.37.59.23 Loaded
adfm-business-editor-settings-ide oracle.adfm.businesseditor.settings 11.1.1.4.37.59.23 Loaded
adfmcoredt-xdf oracle.adfm.xdf 11.1.1.4.37.59.23 Loaded
adfquerylovdt oracle.adf-faces-query-and-lov-dt 11.1.1.4.37.59.23 Loaded
analytics.measurement oracle.bpm.analytics.measurement 11.1.1.4.0.5682 Loaded
appoverview oracle.ide.appoverview 11.1.1.4.37.59.23 Loaded
asnav-weblogic oracle.jdeveloper.asnav.weblogic 11.1.1.4.37.59.23 Loaded
audit oracle.ide.audit 11.1.1.4.37.59.23 Loaded
audit-core oracle.ide.audit.core 11.1.1.4.37.59.23 Loaded
bam oracle.bpm.bam 11.1.1.4.0.5682 Loaded
bcgen oracle.bpm.bcgen 11.1.1.4.0.5682 Loaded
bi-jdbc oracle.bi.jdbc 11.1.1.4.37.59.23 Loaded
boot oracle.bpm.boot 11.1.1.4.0.5682 Loaded
bpa oracle.bpm.bpa 11.1.1.4.0.5682 Loaded
bpm-services.client oracle.bpm.bpm-services.client 11.1.1.4.0.5682 Loaded
bpm-services.interface oracle.bpm.bpm-services.interface 11.1.1.4.0.5682 Loaded
bpmobject oracle.bpm.bpmobject 11.1.1.4.0.5682 Loaded
bpmobject.datacontrol oracle.bpm.bpmobject.datacontrol 11.1.1.4.0.5682 Loaded
bpmobject.runtime oracle.bpm.bpmobject.runtime 11.1.1.4.0.5682 Loaded
casemanagement.implementation oracle.bpm.casemanagement.implementation 11.1.1.4.0.5682 Loaded
chart oracle.bpm.chart 11.1.1.4.0.5682 Loaded
classpath: protocol handler extension oracle.jdeveloper.classpath 11.1.1.0.0 Loaded
compiler oracle.bpm.compiler 11.1.1.4.0.5682 Loaded
compiler.debug oracle.bpm.compiler.debug 11.1.1.4.0.5682 Loaded
compiler.xpath oracle.bpm.compiler.xpath 11.1.1.4.0.5682 Loaded
configuration oracle.bpm.configuration 11.1.1.4.0.5682 Loaded
connectors oracle.bpm.connectors 11.1.1.4.0.5682 Loaded
core oracle.bpm.core 11.1.1.4.0.5682 Loaded
db-audit oracle.ide.db.audit 11.1.1.4.37.59.23 Loaded
db-modeler-transform oracle.dbmodeler.transform 11.1.1.4.37.59.23 Loaded
dcadapters-ide oracle.adfm.dc-adapters 11.1.1.4.37.59.23 Loaded
dependency-java oracle.jdeveloper.java.dependency 11.1.1.4.37.59.23 Loaded
dependency-refactor oracle.jdeveloper.refactoring.dependency 11.1.1.4.37.59.23 Loaded
deploy-ant oracle.deploy.ant 11.1.1.4.37.59.23 Loaded
deploy-rt oracle.jdevimpl.deploy-rt 11.1.1.4.37.59.23 Loaded
designer oracle.bpm.designer 11.1.1.4.0.5682 Loaded
diagram.draw oracle.bpm.diagram.draw 11.1.1.4.0.5682 Loaded
diagram.editor oracle.bpm.diagram.editor 11.1.1.4.0.5682 Loaded
editor oracle.bpm.editor 11.1.1.4.0.5682 Loaded
fdi oracle.bpm.fdi 11.1.1.4.0.5682 Loaded
feedback-client2 oracle.ideimpl.feedback2.client 11.1.1.4.37.59.23 Loaded
fuegoui oracle.bpm.fuegoui 11.1.1.4.0.5682 Loaded
fusion.sca oracle.bpm.fusion.sca 11.1.1.4.0.5682 Loaded
fusion.scac oracle.bpm.fusion.scac 11.1.1.4.0.5682 Loaded
ide-diagnostics oracle.ide.diagnostics 11.1.1.0.0 Loaded
j2ee-adrsimpl oracle.j2ee.adrsimpl 11.1.1.0.0 Loaded
j2ee-facelets oracle.j2ee.facelets 11.1.1.4.37.59.23 Loaded
j2ee-jpsconfig oracle.j2ee.jpsconfig 11.1.1.4.37.59.23 Loaded
j2ee-security oracle.j2ee.security 11.1.1.4.37.59.23 Loaded
j2ee-server oracle.j2ee.server 11.1.1.0.0 Loaded
j2ee-server-dt oracle.j2ee.server.dt 11.1.1.4.37.59.23 Loaded
j2ee-serverimpl oracle.j2ee.serverimpl 11.1.1.4.37.59.23 Loaded
j2ee-weblogic oracle.j2ee.weblogic 11.1.1.4.37.59.23 Loaded
j2ee-weblogic-editors oracle.j2ee.weblogic.editors 11.1.1.4.37.59.23 Loaded
jdukshare oracle.bm.jdukshare 11.1.1.4.37.59.23 Loaded
lib oracle.bpm.lib 11.1.1.4.0.5682 Loaded
library-dconfig-infra oracle.jdeveloper.library.dconfig.infra 11.1.1.4.37.59.23 Loaded
library-jee-api oracle.jdeveloper.library.jee.api 11.1.1.4.37.59.23 Loaded
library-jmx oracle.jdeveloper.library.jmx 11.1.1.4.37.59.23 Loaded
library-jps oracle.jdeveloper.library.jps 11.1.1.4.37.59.23 Loaded
library-weblogic-api oracle.jdeveloper.library.weblogic.api 11.1.1.4.37.59.23 Loaded
library-weblogic-client oracle.jdeveloper.library.weblogic.client 11.1.1.4.37.59.23 Loaded
mof oracle.mof 11.1.1.4.37.59.23 Loaded
mof-index oracle.mof.index 11.1.1.4.37.59.23 Loaded
mof-xmi oracle.mof.xmi 11.1.1.4.37.59.23 Loaded
obpi oracle.bpm.obpi 11.1.1.4.0.5682 Loaded
oracle.adfm oracle.adfm 11.1.1.4.37.59.23 Loaded
oracle.adfm.contextual oracle.adfm.contextual 11.1.1.4.37.59.23 Loaded
oracle.dynamic-faces-dt oracle.dynamic.faces 11.1.1.4.37.59.23 Loaded
oracle.ide.dependency oracle.ide.dependency 11.1.1.4.37.59.23 Loaded
oracle.ide.filequery oracle.ide.filequery 11.1.1.4.37.59.23 Loaded
oracle.ide.indexing oracle.ide.indexing 11.1.1.4.37.59.23 Loaded
oracle.ide.usages-tracking oracle.ide.usages-tracking 11.1.1.4.37.59.23 Loaded
oracle.todo.tasks oracle.todo.tasks 11.1.1.4.37.59.23 Loaded
palette2 oracle.ide.palette2 11.1.1.4.37.59.23 Loaded
papi oracle.bpm.papi 11.1.1.4.0.5682 Loaded
parser oracle.bpm.parser 11.1.1.4.0.5682 Loaded
placeholder-jsf-ui oracle.placeholderjsf-ui 11.1.1.4.37.59.23 Loaded
placeholderdc-dt oracle.placeholderdc.dt 11.1.1.4.37.59.23 Loaded
pml.service oracle.bpm.pml.service 11.1.1.4.0.5682 Loaded
project oracle.bpm.project 11.1.1.4.0.5682 Loaded
project.catalog oracle.bpm.project.catalog 11.1.1.4.0.1 Loaded
project.command oracle.bpm.project.command 11.1.1.4.0.5682 Loaded
project.compile oracle.bpm.project.compile 11.1.1.4.0.5682 Loaded
project.draw oracle.bpm.project.draw 11.1.1.4.0.5682 Loaded
project.importer oracle.bpm.project.importer 11.1.1.4.0.5682 Loaded
project.interface oracle.bpm.project.interface 11.1.1.4.0.5682 Loaded
project.io oracle.bpm.project.io 11.1.1.4.0.5682 Loaded
project.metadata oracle.bpm.metadata 11.1.1.4.0.5682 Loaded
project.model oracle.bpm.project.model 11.1.1.4.0.5682 Loaded
project.ui oracle.bpm.project.ui 11.1.1.4.0.5682 Loaded
project.view oracle.bpm.project.view 11.1.1.4.0.5682 Loaded
rcasadapter-dt oracle.jdeveloper.asadapter.dt 11.1.1.4.37.59.23 Loaded
rcasadapter-oc4j oracle.jdeveloper.asadapter.oc4j 11.1.1.4.37.59.23 Loaded
rcasadapter-rescat2 oracle.jdeveloper.asadapter.rescat2 11.1.1.4.37.59.23 Loaded
rcasadapter-thirdparty oracle.jdeveloper.asadapter.thirdparty 11.1.1.4.37.59.23 Loaded
rcasadapter-weblogic oracle.jdeveloper.asadapter.weblogic 11.1.1.4.37.59.23 Loaded
rcasadapter-weblogic-api oracle.jdeveloper.asadapter.weblogic.api 11.1.1.4.37.59.23 Loaded
rescat2 oracle.jdevimpl.rescat2 11.1.1.4.37.59.23 Loaded
resourcebundle-api-adfdeps oracle.jdeveloper.resourcebundle.adfdeps 11.1.1.4.37.59.23 Loaded
resourcebundle-api-xliff oracle.resourcebundle.xliff 11.1.1.4.37.59.23 Loaded
resourcebundle-customization oracle.jdeveloper.resourcebundle.customization 11.1.1.4.37.59.23 Loaded
rmi oracle.bpm.rmi 11.1.1.4.0.5682 Loaded
script oracle.bpm.script 11.1.1.4.0.5682 Loaded
searchbar-gallery oracle.ide.searchbar.gallery 11.1.1.4.37.59.23 Loaded
searchbar-help oracle.ide.searchbar.help 11.1.1.4.37.59.23 Loaded
searchbar-index oracle.ide.searchbar.index 11.1.1.4.37.59.23 Loaded
soa.humantask oracle.bpm.soa.humantask 11.1.1.4.0.5682 Loaded
status oracle.ide.status 11.1.1.4.37.59.23 Loaded
tests.core oracle.bpm.tests.core 11.1.1.4.0.5682 Loaded
ui oracle.bpm.ui 11.1.1.4.0.5682 Loaded
vfilesystem oracle.bpm.vfilesystem 11.1.1.4.0.5682 Loaded
web.execution oracle.bpm.web.execution 11.1.1.4.0.5682 Loaded
xml oracle.bpm.xml 11.1.1.4.0.5682 Loaded
xml-schema-dt oracle.jdevimpl.xml.schema 11.1.1.4.37.59.23 Loaded
xobject.devel oracle.bpm.xobject.devel 11.1.1.4.0.5682 Loaded
xobject.runtime oracle.bpm.xobject.runtime 11.1.1.4.0.5682 Loaded
xsl-dt oracle.jdevimpl.xml.xsl 11.1.1.4.37.59.23 Loaded
xsqldt-ide oracle.xsqldt-ide 11.1.1.4.37.59.23 LoadedI think you are looking for jar $MW_Home\Oracle_SOA1\soa\modules\oracle.soa.worklist_11.1.1\adflibWorklistComponents.jar ( $JDev_Home\soa\modules\oracle.soa.worklist_11
.1.1\adflibWorklistComponents.jar)
ApprovalListEditorComp is an interface and ApprovalListUtil is a class.
Regards,
Anuj -
hi gurus ,
how can i communicate with SAP to Non SAP using ALE and IDOCS.
with regards
aru.Hi
SAP Integration using ALE
(Application Linking and Enabling)
- Introduction -
Page 1 of 7
1.0 Introduction
Enterprises are increasingly looking to deliver real business benefits by integrating their systems and processes both within their organizations and between organizations. ng processes in this way, which requires tight integration, frequent communication and data exchange.
Highly integrated and inter-dependent SAP and non-SAP systems require frequent communication, tight integration and (usually) high levels of data exchange. In order to achieve this interoperability, SAP has come up with the concept of ALE (Application Linking and Enabling).
The idea behind ALE is to provide a more rigid integration service while allowing a high degree of independence to the individual SAP com
ge of business information across SAP and non-SAP systems. Applications are integrated by using synchronous and asynchronous communication without implementing a central database.
In this 7 article tutorial we will cover subjects such as:
Data Distribution Model
ALE process
IDOCS
Converters
Configuring ALE
Other concepts
RFC
Purpose
Communication between applications of different systems in the SAP environment includes connections between SAP systems as well as between SAP systems and non-SAP systems. Remote Function Call (RFC) is the standard SAP interface for communication between SAP systems. The RFC calls a function to be executed in a remote system.
Synchronous RFC
The first version of RFC is synchronous RFC (sRFC). This type of RFC executes the function call based on synchronous communication, which means that the systems involved must both be available at the time the call is made.
Transactional RFC (tRFC)
Transactional RFC (tRFC, also originally known as asynchronous RFC) is an asynchronous communication method that executes the called function module in the RFC server only once. The remote system need not be available at the time when the RFC client program is executing a tRFC. The tRFC component stores the called RFC function, together with the corresponding data, in the SAP database under a unique transaction ID (TID).
If a call is sent, and the receiving system is down, the call remains in the local queue until a later time. The calling dialog program can proceed without waiting to see whether or not the remote call was successful. If the receiving system does not become active within a certain amount of time, the call is scheduled to run in batch.
tRFC is always used if a function is executed as a Logical Unit of Work (LUW). Within a LUW, all calls are
· executed in the order in which they are called
· executed in the same program context in the target system
· run as a single transaction: they are either committed or rolled back as a unit.
Implementation of tRFC is recommended if you want to guarantee that the transactional order of the calls is preserved.
Disadvantages of tRFC
· tRFC processes all LUWs independent of one another. Due to the amount of activated tRFC processes, this procedure can reduce performance significantly in both the send and the target systems.
· In addition, the sequence of LUWs defined in the application cannot be kept. Therefore, there is no guarantee that the transactions are executed in the sequence dictated by the application. The only guarantee is that all LUWs are transferred sooner or later.
Queued RFC (qRFC)
To guarantee that multiple LUWs are processed in the order specified by the application, tRFC can be serialized using queues (inbound and outbound queues). This type of RFC is called queued RFC (qRFC).
qRFC is therefore an extension of tRFC. It transfers an LUW (transaction) only if it has no predecessors (in reference to the sequence defined in different application programs) in the participating queues.
Implementation of qRFC is recommended if you want to guarantee that several transactions are processed in a predefined order.
RFC: Data Transfer
All RFC types are transferred by means of CPI-C or TCP/IP. They constitute a form of gateway communication.
Additional Information
· RFC Basics (BC-MID-RFC)
· The RFC API
· RFC Programming in ABAP
· Queued Remote Function Call (qRFC)
· SAP Gateway
IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. IDocs are used for asynchronous transactions: each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.
A large enterprise's networked computing environment is likely to connect many geographically distributed computers to the main database. These computers are likely to use different hardware and/or operating system platforms. An IDoc encapsulates data so that it can be exchanged between different systems without conversion from one format to another.
IDoc types define different categories of data, such as purchase orders or invoices, which may then be broken down into more specific categories called message types. Greater specificity means that an IDoc type is capable of storing only the data required for a particular transaction, which increases efficiency and decreases resource demands.
An IDoc can be generated at any point in a transaction process. For example, during a shipping transaction process, an IDoc may be generated that includes the data fields required to print a shipping manifest. After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model. The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external system.
is a set of interfaces to object-oriented programming methods that enable a programmer to integrate third-party software into the proprietary R/3 product from SAP. For specific business tasks such as uploading transactional data, BAPIs are implemented and stored in the R/3 system as remote function call (RFC) modules.
A good place to get started is this Introduction to BAPIs presented by sappoint.com.
SAP also provides this in-depth BAPI User Guide to help you master the basics. Terminology, rules for usage and prerequisites are included.
Also, SAP provides this BAPI Programming Guide
For ALE
http://www.thespot4sap.com/Articles/SAP_ALE_Introduction.asp
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
For RFC
http://help.sap.com/saphelp_nw04/helpdata/en/6f/1bd5b6a85b11d6b28500508b5d5211/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/22/042518488911d189490000e829fbbd/content.htm
http://www.planetsap.com/RFC.htm
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..
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
Check 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://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
Please check this PDF documents for ALE and IDoc.
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
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
Reward all helpfull answers
Regards
Pavan -
User exit for Internal Order SaveReplica or ALE/IDOC
Hi,
We're currently copying back internal orders from our PRD environment into QAS using the class method InternalOrder SaveReplica via the distribution model in BD64.
We've extended table AUFK to include some custom fields and are populating it nicely via the user exit provided. However, we want to include these values when we replicate the data back in our QAS environment.
The BAPI for method CREATE contains the "EXTENSIONIN" table so I think I know what to do there, but we are using SAVEREPLICA which doesn't offer any extra fields.
What is the best way to copy this data back into QAS?
Would it make sense to put a user exit RFC call in the QAS system to populate the values after reading them from the PRD system at the time of saving?
I can't find any user exits. We are doing this based off of change pointers.
Would you recommend using basic ALE, doing an extension to idoc type internalorders01 or something?
Thanks for any suggestions.Hi,
usage of specific combinations of internal orders + cost elements:
Create FI-validation rule (T-code OB28 or GGB1) using BSEG-HKONT, BSEG-AUFNR for call-up point 2. Assigne this rule to the comp. code(s) needed.
Best regards, Christian -
URGENT-Usage Of -BAPI_CUSTOMER_CREATEFROMDATA
HI CONSULTANTAS,
i have got this document(SEE BELOW) form SAP-0SSNOTES,
1.WT DOES REALLY MEAN.
2.<b>CAN I CALL THIS FROM REPORT PROG TO CREATE THE CUSTOMER
OR CAN I HAVE TO USE BDC ONLY</b>
Symptom
This note is meant to provide an explanation of the usage of function modules BAPI_CUSTOMER_* of function group V02D.
Other terms
BAPI_CUSTOMER_CREATEFROMDATA, BAPI_CUSTOMER_CREATEFROMDATA1,
BAPI_CUSTOMER_CHANGEFROMDATA, BAPI_CUSTOMER_CHANGEFROMDATA1
BAPI_CUSTOMER_GETDETAIL, BAPI_CUSTOMER_GETDETAIL1
BAPI_CUSTOMER_SEARCH, BAPI_CUSTOMER_SEARCH1
BAPI, SAP Online Store, ISA, ISA-R3, ISA-R/3, consumer, create customer
Solution
The BAPIs of the function group V02D are intended exclusively for use in the SAP Online Store and the SAP Internet Sales R/3 Edition, that is you can create or change consumers from the SAP Online store and SAP Internet Sales R/3 Edition in the R/3 system. You cannot use them to create or change customer masters or consumers in the standard system; you can only do this using ALE or Batch Input.
When you use the above-mentioned BAPIs outside of SAP Online Store or SAP Internet Sales R/3 Edition, or with customer master records that were created or edited outside of the SAP Online Store or SAP Internet Sales R/3 Edition, there is a danger that you will lose data.
PLZ HELP ME
REGARDS
HARIHi Martin,
from the function module documentation:
- Fields of import parameter PI_COPYREFERENCE:
R/3 reference customer, sales area data (sales organization,
distribution channel, division)
Note on reference customer:
The reference customer should be created bearing in mind that its
sole purpose is to provide data for customers that are created via
the BAPI.
That is, the reference customer is not an operative customer in the
business sense. As a result, the customer should be created with a
separate account group with internal number assignment. In addition,
the reference customer must exist in the organizational data that is
transferred to the BAPI.
If company-code-independent data is transferred to the BAPI, the
reference customer must be created for a company code.
So, if you have created a reference customer already, you should know the organizational data (Org/DistrChan/Division and Company code). -
Hi,
Please can any one send me details about partner profiles usage and the tcode where exactly we have to maintain this.
If anyone have documentation on AlE is added advantage for me.
Regards,
KotiHi,
Logical System name is used to indicate the application system to which you are sending the data. Partner profiles use the above Logical System name to determine the system to which the data is to be sent ie you have to tell wether inbound or outbound.
Below are the links for ALE IDOC related materials.
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
/people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)
Reward points if useful.
Regards,
Soumya. -
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 SAPs 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 IDocs 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 programs 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 IDocs 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 modules 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 -
Please let me know the usage of def Backend systems?
Hi friends
Please let me know the usage of Def Backend systems with fields
Thanks
regards
chinna
Edited by: chinna krishna on Nov 25, 2008 5:53 AMHi krishna
In this Define Backend system . you can define all your backend system and EBp system, Catalog system, SUS ROS system. This configuration helps you to communicate with other system. and it helps to view howm many systems are connected with other systems.This configuration is mother of all configuration.
Define Backend Systems
In this activity, you specify
u2022 Which backend system(s) you are working with
u2022 Which local system you use to run your business scenario
u2022 Whether purchase orders and their follow-on documents (confirmations, goods receipts/service entry sheets, and invoice) are to be created locally in Enterprise Buyer
u2022 Whether contracts from the Sourcing application or from the Bidding Engine are to be created in the backend system (as of backend release 4.6B)
u2022 Whether SAP Supplier Self-Services and SAP Enterprise Buyer are to run in the same client
Requirements
u2022 In the activity Define RFC Destination, you have defined the RFC destinations for your systems.
u2022 In the activity ALE Settings (Logical System), you have defined the logical systems for your systems.
Activities
Define the following:
u2022 Name and description of the system. If you have already defined the logical system in ALE Settings (Logical System) you should use the same description here.
u2022 The RFC destination for the system
u2022 Type and release level of the backend system
In order to create a contract in the backend system, set up a logical system with RFC and system type CM.
If you are using supplier registration with catalog integration, you must enter SUPPL_DIR here. A prerequisite is that you have have made a dummy entry under Logical System.
If you are using SAP SUS and SAP EBP in the same client, you must enter EBP_SUS here.
u2022 Select Local if the system is your local Enterprise Buyer system.
As of SRM Release 4.0, this setting is required for all SRM scenarios. In previous releases, this entry was only required for standalone deployment.
u2022 In the column SLD ID, enter the name of the associated system in the SAP System Landscape Directory (SLD). Prerequisite: The technical name of the local EBP system is entered in the SLD. Make this setting for
o The local Enterprise Buyer system if you exchange documents via the SAP Exchange Infrastructure (XI). The ID of the local EBP system is located in the SAP Landscape Directory (or LCR). Example: PJC_CLIENT_300
o An external system (for example, SAP PP-MRP or the system of an external provider) from which, you transfer requirements into Enterprise Buyer.
o The SUS System if you use this scenario
o For the SAP Content Integrator (CI). If you use the CI to map product IDs, the SLD-ID must be available for all systems whose product IDs are to be mapped.
Hope this helps you
regards
Muthu -
Dear Experts,
1.What is the different b/w ALE and LSMW ?
2. Can you explain the differents in Variant configuration scenario using both?
3.BD91,BD92 what are the usages in ALE?
RegardsHi,
ALE:
Highly integrated and inter-dependent SAP and non-SAP systems require frequent communication, tight integration and (usually) high levels of data exchange. In order to achieve this interoperability, SAP has come up with the concept of ALE (Application Linking and Enabling).
The idea behind ALE is to provide a more rigid integration service while allowing a high degree of independence to the individual SAP. Manage of business information across SAP and non-SAP systems. Applications are integrated by using synchronous and asynchronous communication without implementing a central database.
LSMW:
LSMW an abbreviation for Legacy System Migration Workbench is a tool in SAP which is used to migrate Legacy data into SAP. It is a very important tool and easy to learn and master it. LSMW has a recording tool which can record the transaction and the fields to be uploaded. Thus upload of master data and transaction data is made very simple in this tool. You can use this tools in almost all modules for upload of master data and too some extent transaction data also.
Thus in FI you can upload the following master data through this: Vendors, Customers, General Ledger, Asset master, Bank Master. You can upload Transaction balance through this i.e. an FI document.
In CO you can upload the following master data: Cost element, Cost center, Profit center, Activity types, Internal orders, Statistical key figures.
In other modules likewise you can upload other sets of master data.
for your reference:
http://www.sapdb.info/quick-reference-guide-on-lsmw/
Release strategy transport:
BD91 - SAP Menu > Tools > ALE > Master Data Distribution > Logistics > Classification > Characteristic > Send
BD91: for sending Characteristics Master
BD92 - SAP Menu > Tools > ALE > Master Data Distribution > Logistics > Classification > Class > Send
BD92: for sending Class Master. -
Problem with Firefox and very heavy memory usage
For several releases now, Firefox has been particularly heavy on memory usage. With its most recent version, with a single browser instance and only one tab, Firefox consumes more memory that any other application running on my Windows PC. The memory footprint grows significantly as I open additional tabs, getting to almost 1GB when there are 7 or 8 tabs open. This is as true with no extensions or pluggins, and with the usual set, (firebug, fire cookie, fireshot, XMarks). Right now, with 2 tabs, the memory is at 217,128K and climbing, CPU is between 0.2 and 1.5%.
I have read dozens of threads providing "helpful" suggestions, and tried any that seem reasonable. But like most others who experience Firebug's memory problems, none address the issue.
Firefox is an excellent tool for web developers, and I rely on it heavily, but have now resorted to using Chrome as the default and only open Firefox when I must, in order to test or debug a page.
Is there no hope of resolving this problem? So far, from responses to other similar threads, the response has been to deny any responsibility and blame extensions and/or pluggins. This is not helpful and not accurate. Will Firefox accept ownership for this problem and try to address it properly, or must we continue to suffer for your failings?55%, it's still 1.6Gb....there shouldn't be a problem scanning something that it says will take up 300Mb, then actually only takes up 70Mb.
And not wrong, it obviously isn't releasing the memory when other applications need it because it doesn't, I have to close PS before it will release it. Yes, it probably is supposed to release it, but it isn't.
Thank you for your answer (even if it did appear to me to be a bit rude/shouty, perhaps something more polite than "Wrong!" next time) but I'm sitting at my computer, and I can see what is using how much memory and when, you can't. -
Problem with scanning and memory usage
I'm running PS CS3 on Vista Home Premium, 1.86Ghz Intel core 2 processor, and 4GB RAM.
I realise Vista only sees 3.3GB of this RAM, and I know Vista uses about 1GB all the time.
Question:
While running PS, and only PS, with no files open, I have 2GB of RAM, why will PS not let me scan a file that it says will take up 300Mb?
200Mb is about the limit that it will let me scan, but even then, the actual end product ends up being less than 100Mb. (around 70mb in most cases)I'm using a Dell AIO A920, latest drivers etc, and PS is set to use all avaliable RAM.
Not only will it not let me scan, once a file I've opened has used up "x" amount of RAM, even if I then close that file, "x" amount of RAM will STILL be unavaliable. This means if I scan something, I have to save it, close PS, then open it again before I can scan anything else.
Surely this isn't normal. Or am I being stupid and missing something obvious?
I've also monitored the memory usage during scanning using task manager and various other things, it hardly goes up at all, then shoots up to 70-80% once the 70ishMb file is loaded. Something is up because if that were true, I'd actually only have 1Gb of RAM, and running Vista would be nearly impossible.
It's not a Vista thing either as I had this problem when I had XP. In fact it was worse then, I could hardly scan anything, had to be very low resolution.
Thanks in advance for any help55%, it's still 1.6Gb....there shouldn't be a problem scanning something that it says will take up 300Mb, then actually only takes up 70Mb.
And not wrong, it obviously isn't releasing the memory when other applications need it because it doesn't, I have to close PS before it will release it. Yes, it probably is supposed to release it, but it isn't.
Thank you for your answer (even if it did appear to me to be a bit rude/shouty, perhaps something more polite than "Wrong!" next time) but I'm sitting at my computer, and I can see what is using how much memory and when, you can't.
Maybe you are looking for
-
Can't get ATV working with Onkyo TX-SR605-URGENT ASSISTANCE NEEDED!!
I'm hoping someone will be able to give me some advice, as I've now spent way too much time trying to figure out what's going wrong. I've just purchased the Onkyo receiver, which in itself is an extremely daunting piece of equipment after my very str
-
How to get PS from G5 to MacPro?
I bought a new Mac Pro, but my PhotoShop (upgraded 10 - cs3? - according to my registration) is on my old Mac G5. How do I get that PS onto my new computer? and if possible, how do I upgrade from there? I found my original PS 7.0 CD, but it will not
-
Error while using save option in OfficeCntrol UI
Hi Experts I am facing issue while using OfficeControl ui in my webdynpro java application. I am trying to save the xlsx spreadsheet data from the officecontrol UI using the below code: try IWDIOSFactory factoryInstance=null; IWDIOSSpreadsheet docume
-
help
-
Zen Touch says its connected to PC, PC says it is
I just bought a Zen Touch 40GB player today and am pulling my hair out with it. Basically at the minute when I open up the mediasource software the Zen player will light up and claim that its docking with PC, but mediasource will show the window that