ALE to Webmethods design
We are on an older version of R/3 currently, and have one feed through wM currently running in production. This carries orders in to SAP and confirmations back out.
With one eye on what might be available when we move on to one of the latest platforms ECC 5 etc, I am wondering what the best practice is for setting up ALE links from SAP to wM?
Should we look to have a single point of contact - one logical system - between the two systems along which all traffic is sent regardless of purpose or end destination, or is it better to have multiple links - for better visibility/flexibility going forwards perhaps?
I see that one limitation is that for one message type e.g. DESADV, it is limited to one receiving destination.
Any thoughts on this would be much appreciated. It isn't obvious to me from the documentation available what the typically chosen design decision is.
Regards
Phil.
Thanks Michal,
Though I'm not necessarily sure that the above helps in this instance.
Can you advise how an outbound message type (such as DESADV) can be incorporated into two logical systems and the ALE config be set up so that the correct RFC destination & partner can be determined when the outbound IDOC is generated?
At present a B1 130 message is issued in the output error log stating that too many recipients have been specified.
cheers.
Similar Messages
-
Migration from webmethods to SAP PI 7.1
Hi All,
I need some information on migrating webmethods to PI 7.1.
We have our interfaces currently working in webmethods which call webservices in SAP.Currently legacy systems call SAP webservices through webmethods which we would like to migrate to PI 7.1.
Could I get some information on how to proceed with this?
1.Could I get the overview
2.Can I import the same structure and mappings into SAP PI?
3.Do I need to recreate the mappings or use the same from webmethods ..if they are XSLT mappings?
4.Can I use the mapping transformation done in webmethods ?
Any thoughts would be of great help
Thanks,
C> I need some information on migrating webmethods to PI 7.1.
> We have our interfaces currently working in webmethods which call webservices in SAP.Currently legacy systems call SAP webservices through webmethods which we would like to migrate to PI 7.1.
>
> Could I get some information on how to proceed with this?
>
2 years back i worked on one migration project from WebMethods to SAP PI 7.1
> 1.Could I get the overview
> 2.Can I import the same structure and mappings into SAP PI?
> 3.Do I need to recreate the mappings or use the same from webmethods ..if they are XSLT mappings?
> 4.Can I use the mapping transformation done in webmethods ?
>
> Any thoughts would be of great help
1)Only XSLT Mapping program can be reused in PI7.1,most of the times without change, sometimes it required change when you have java functions in XSLT Mapping.
Adjust your XSLT mapping programs compatible to without using XML TOOL kit option in Operation mapping.
2) To understand the web methods flow , you should have some basic /medium level of knowledge , then you can easily understand the mapping logic implemented in Web Methods.
3) When you developing interface use Web methods for only mapping logic, donu2019t try to implement the same design what developed in Web Methods. Think PI prospective. The way web methods execute interface is differ compare to PI (execution process).
4)If any java services existing in current web method interfaces, you canu2019t use the same as java mapping program in PI,in web methods we can perform state full operation from java services in web methods. But in PI it is strictly avoided performing state full operation like retrieving the data/sending data to Data base using Java map.
5) If your client forcing you to use XSLT mappings then only use, else implement the same logic using GUI mapping in PI.
6) Connecting to SAP systems and non SAP system use Adapters in PI,it is very easy . Follow standard way of communication using PI ,donu2019t try to copy from Web METHODS.
Thanks and Regards,
Raja Sekhar -
ALE: how do I use dependent distribution for customer and vendor addresses?
Hello SDN'ers
Hopefully someone can help me with an ALE question.
We have two ERP systems connected with ERP - Retail and AFS.
Customers and Vendors may be created in Retail, and are distributed to AFS using DEBMAS, CREMAS and ADRMAS messages.
Not all customers and vendors are required in AFS, so we have various filters set up in the Retail distribution model (BD64).
However with the filters in place, addresses were still being distributed for customers and vendors that had been filtered out.
To try and avoid this for vendors, we created a filter group for AddressOrg.SaveReplica in receiver determination. In the filter group we selected Dependent Distribution for CREMAS (Address owner object).
This works perfectly for vendors - vendor addresses are now only distributed if the vendor itself is distributed.
However I've now discovered it is preventing any customer addresses from being sent! I was surprised about this: I expected CREMAS dependency to only affect vendor addresses. Can someone tell me:
- is this how dependent distribution is designed to work? In which case can anyone offer any suffestions to achieve the filtering some other way?
- or are we doing something wrong to be getting this result?
Thanks for any help!
regards, RogerHi all,
as Robert suggested, I've written an exit to get round this, although I'm surprised I should need to!
What I did was to code an enhancement in function group BDBF, at the start of subroutine COMPUTE_LOGIC_EXPRESSION.
* In the case of addresses, dependencies should only be applied for the appropriate type of address
data: lwa_tbd14 type tbd14.
if P_MODEL_DATA-FTYPE = C_FTYPE_DEPENDENCY_FROM_MESTYP.
* Dependency from Message Type.
* Read the Address Object type
READ TABLE P_FILTER_VALUES
WITH KEY OBJTYPE = 'AD_OBJTYPE'
BINARY SEARCH.
if sy-subrc = 0.
* Check if the Message Type is linked to the Address Owner Object Type
* (Table is buffered on DB)
select single *
from TBD14
into lwa_tbd14
where MESTYP = P_MODEL_DATA-FMESTYP
and OBJTYP = P_FILTER_VALUES-OBJVALUE.
if sy-subrc <> 0.
* Wrong type of address for this dependency - stop here
P_REPLICATE = c_true.
exit.
else.
* Correct address type. Standard processing continues, checking any
* filter values set up against the Address Owner Object Type.
endif.
else.
* It isn't an address - continue with standard processing
endif.
endif.
Let me know if this helps you, or if you know of a better way to achieve the same result.
Roger -
Data transfer using ALE/IDOC into XML.
Dear All,
I have to transfer FI document data (FB01) from the sap system ,convert it into XML and dump it in 1 of the file servers.I want to do this using ALE/IDOC.Is it possible to do the same and how.Similarly i want to do the same for Vendor and Customer master i.e sending the data in XML format.
Kindly Suggest how do i go about doin the same..Its very urgent.Please help.
Thanks & Regards,
Lailu Philip.In continuation:
Example Purchasing & Selling scenario
We will develop a custom IDoc to carry the billing number from the Service Receivers system to the Service Providers system. We will populate the IDoc in a user exit on the sending side and we will process the transaction on the receiving side using a custom function module and a BDC transaction call.
No rule conversion, segment filtering or version conversion will be implemented in the model as described in Figure 1.
Requirements
Working ALE environment - See ALE Basis Configuration Guide;
ALE scenario design together with the business requirement;
Development access; and
ALE configuration access.
NOTES:
1. All IMG references to transactions are located in the transaction SALE which is the ALE portion of the IMG
2. This is one way of developing a scenario where no message control exists. If message control exist (EG. On purchase orders) then NAST can be used to call an outbound function module that would create the required IDocs.
3. Extensive knowledge of IDocs and ALE basis configuration is required in order to understand this guide.
2. OUTBOUND PROCESSING
2.1. Create IDoc type (WE30) Client independent
The IDoc type refers to the IDoc structure that you will require for your development. In our case the IDoc type is called ZINVRV01. This IDoc type will have 1 segment called Z1INVRV with 2 fields, LIFNR & XBLNR, in this segment. If you require many segments or nested segments then they are also created using the same procedure.
We will create the IDoc of the following structure:
ZINVRV01
Purchasing and Selling - Invoice receipt reversal
Z1INVRV P&S - Segment 1
Segment fields
LIFNR Vendor account number
XBLNR Reference document number
Figure 3: IDoc type ZINVRV01
To create the IDoc type, follow these next few steps:
Enter transaction WE30 (ALE -> Extensions -> IDoc types -> Maintain IDoc type)
Type in ZINVRV01 and click on Basic IDoc type, click the Create icon
Click on Create new (we are creating an IDoc from scratch but you may want to copy another IDoc if it is similar to your requirements) and enter a description, and press enter
Click on ZINVRV01 and then on the Create icon
Enter Z1INVRV as the segment type (must start with Z1), check mandatory if the segment must exist (in this case check it), enter 1 in minimum number and 1 as maximum number. (Make the maximum number 9999999999 if there are going to be many of these segments in each IDoc. IE. When line items are passed via IDocs), click on Segment editor
Enter a description for your segment type and create
Enter a description for your segment, enter each field required in your IDoc, in our case type LIFNR across for Field name, DE structure and DE documentation, repeat for XBLNR and press enter to validate.
Save and generate, press back
To release the segment choose Goto, Release from the menu
Check the box on the line of your new segment
Save, back and enter
Your IDoc type structure should be displayed with your new segment
Save and back
To release the IDoc type choose Extras, Release type from the menu and Yes
Your IDoc is now ready for use. If you need to add fields or segments to your IDoc type, you will need to cancel the release of the IDoc type as well as the segment release using a similar procedure followed above (except now you uncheck the release box for the segment and you choose cancel release for the IDoc type).
2.2. Create message type (WE81) Client independent
To create a new message type, follow these next few steps:
Enter transaction WE81 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Create logical message type)
Choose Create logical message type by double clicking on it
Click on change icon to enter change mode
Click on New entries to add a new type
Enter the required message type, in our case it is ZINVRV and an appropriate description
Save and exit.
Your message type has now been created. The next step will be to link it to the IDoc.
2.2.1. Link message to IDoc type (WE82 & BD69) Client independent
To link the message type to the IDoc type follow these next few steps:
Enter transaction WE82 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> EDI: Message Types and Assignment to IDoc Types)
Click on change icon to enter change mode
Click on New entries to create the link
Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
Save and exit
Enter transaction BD69 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Assign message type to IDoc for ALE)
Click on change icon to enter change mode
Click on New entries to create the link
Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
Save and exit
Your IDoc is now linked to your message type. We still need to link object types and add the message to the model before we can use the message.
2.2.2. Maintain object type for message type (BD59) Client independent
The ALE objects are used to create links between IDocs and applications objects, to control the serialisation, to filter messages in the customer model and to use listings.
For our own message type and IDoc you must maintain object types for the links.
If you want to check the serialisation for the message type, then you must maintain object types for the serialisation. If no serialisation object has been maintained for a given message type, then the serialisation will not be checked for this message type.
To add an object type to our message type, follow these next few steps:
Enter transaction BD59 (ALE -> Extensions -> ALE object maintenance -> Maintain object types)
Type in your message type ZINVRV and press enter
Click on New entries
Enter your object type, LIFNR (We need to use the vendor as a filter object), the segment name where LIFNR resides, Z1INVRV, a number 1 for the sequence followed by the actual field name LIFNR
Save and exit.
You have now created an object that well use as a filter object in the customer model to direct the flow of messages to the various logical systems based on the vendors in the filter of the message type ZINVRV.
We now need to add our new message type to the distribution model.
2.3. Configuring the Distribution Model
This task is performed on your ALE reference client.
2.3.1. Manual Configuration (BD64) Client dependent
To manually configure the customer distribution model, read the ALE configuration procedure, and follow these steps:
Perform the Maintain customer distribution model directly function. (ALE -> Distribution customer model -> Maintain customer distribution model directly)
Specify the customer model you want to maintain and the logical system that is to be the sender of the messages OR create a new model. (Create model ALE with logical system ALELS1C400)
Choose the receiving systems to which the sending system must forward message type ZINVRV to.
For each receiving logical system allocate the message type necessary for communication to the receiving systems as per ALE configuration procedure.
Create filter objects (in our case LIFNR as the object type with the associated vendor number, 0000018001 with leading zeros, in the object area) for the message types.
Save the entries.
NOTES:
You cannot maintain a message type between the same sender and receiver in more than one customer distribution model.
Only the owner is authorised to modify the model.
To change the owner of a model, choose the 'Maintain ownership of customer distribution model' function. Make sure that all changes will be distributed to all systems that know the corresponding model. To do so, you can use the correction and transport system.
To transport the customer distribution model you should use the Distribute customer model function of the IMG as described below.
2.3.2. Distribute customer model (BD71) Client dependent
After the customer model has been created centrally, it must be distributed to the other remote systems. This entails first of all setting up the communication for the distributed systems and then sending the model.
2.3.2.1. Distribute Model (BD71) Client dependent
This task is performed on your ALE reference client. To distribute the customer distribution model, read the ALE configuration procedure and follow these steps:
Make the settings for the communication with the other decentral systems, you have not set them yet.
Define the RFC destination for R/3 connections whose names correspond to the name of the corresponding logical system.
Create the output partner profile.
Distribute the customer model
Specify the name of the customer model.
You must specify the target system to which you want to distribute the customer model.
You must repeat this function for every distributed logical system.
2.3.2.2. Maintain sending system partner profile (WE20) Client dependent
With this function, you define the partner profiles for all outbound and inbound messages on the basis of the customer distribution model.
After you have defined and distributed the customer model, you will have to maintain the partner profiles locally. To do this read the ALE configuration procedure.
Enter the output mode (background, immediately) and the package size for outbound processing.
Requirements
The customer model must be maintained.
RFC destinations must be maintained.
The customer model must be distributed.
To ensure that the appropriate persons in charge are informed if a processing error occurs, you must make settings in: Error processing Maintain organisational units.
2.4. Populate & distribute IDoc using ABAP
An IDoc consists of a control record with structure edidc and one or more data records with structure edidd. The control record contains the sender and recipient of the IDoc, as well as information on the type of message.
To be able to pass an IDoc to the ALE layer, you must set up a field string with structure edidc and an internal table with structure edidd. They are used to call function module master_idoc_distribute, which performs the save to the database and triggers the dispatch if necessary.
2.4.1. Example code
The code displayed below does the following:
populates our IDoc segment Z1INVR with the 2 fields XBLNR and LIFNR, populates the segment name and appends this to an internal table used to store the IDoc data;
populates the control record info with the message type and IDoc type; and
calls the MASTER_IDOC_DISTRIBUTE function module which distributes the IDoc as configured in the customer distribution model.
Data declaration statements
DATA: C_INVREV_SEGNAME(7) TYPE C VALUE 'Z1INVRV',
C_INVREV_MESTYPE(6) TYPE C VALUE 'ZINVRV',
C_INVREV_IDOC_TYPE(8) TYPE C VALUE 'ZINVRV01',
Z1INVRV LIKE Z1INVRV,
C_INVREV_DOCTYPE LIKE BKPF-BLART VALUE 'YY',
IDOC_CONTROL LIKE EDIDC,
T_COMM_CONTROL LIKE EDIDC OCCURS 0 WITH HEADER LINE,
IDOC_DATA LIKE EDIDD OCCURS 0 WITH HEADER LINE.
Move the document header into a structure
LOOP AT DOC_HEAD_TAB INTO DOC_HEAD.
ENDLOOP.
Move the document item data into a structure
LOOP AT DOC_ITEM_TAB INTO DOC_ITEM WHERE NOT ( LIFNR IS INITIAL ).
ENDLOOP.
Populate the IDoc segments field with the required data
CLEAR Z1INVRV.
Z1INVRV-LIFNR = DOC_ITEM-LIFNR. Store vendor number for filter
Z1INVRV-XBLNR = DOC_HEAD-XBLNR. Billing number
IDOC_DATA-SEGNAM = C_INVREV_SEGNAME. Segment name
IDOC_DATA-SDATA = Z1INVRV. Segment data
APPEND IDOC_DATA. Populate IDoc internal table
Move the control data info required for the distribution
IDOC_CONTROL-MESTYP = C_INVREV_MESTYPE.
IDOC_CONTROL-DOCTYP = C_INVREV_IDOC_TYPE.
Call the distribute function with the required parameters
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE' IN UPDATE TASK
EXPORTING
MASTER_IDOC_CONTROL = IDOC_CONTROL
TABLES
COMMUNICATION_IDOC_CONTROL = T_COMM_CONTROL
MASTER_IDOC_DATA = IDOC_DATA
EXCEPTIONS
ERROR_IN_IDOC_CONTROL = 1
ERROR_WRITING_IDOC_STATUS = 2
ERROR_IN_IDOC_DATA = 3
SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
OTHERS = 5.
Figure 4: Outbound processing example code
NOTE:
For debugging purposes, use transaction WE05 (IDoc overview) to see check your IDoc status, or to see whether an IDoc was created/
3. INBOUND PROCESSING
3.1. Create Function Module
This function module is called when a message type, of type ZINVRV, comes into the receiving system. This needs to be configured and is dealt with later in this section. The function module is passed the IDoc as a parameter.
Example parameters
Import parameters Reference field Opt Y/N
INPUT_METHOD BDWFAP_PAR-INPUTMETHD N
MASS_PROCESSING BDWFAP_PAR-MASS_PROC N
Export Parameters Reference field Opt Y/N
WORKFLOW_RESULT BDWFAP_PAR-RESULT N
APPLICATION_VARIABLE BDWFAP_PAR-APPL_VAR N
IN_UPDATE_TASK BDWFAP_PAR-UPDATETASK N
CALL_TRANSACTION_DONE BDWFAP_PAR-CALLTRANS N
Table Parameters Reference field Optional Y/N
IDOC_CONTRL EDIDC
IDOC_DATA EDIDD
IDOC_STATUS BDIDOCSTAT
RETURN_VARIABLES BDWFRETVAR
SERIALIZATION_INFO BDI_SER
Exceptions
WRONG_FUNCTION_CALLED
Example code
The code displayed below does the following:
populates a BDC table with the IDoc info;
calls the transaction via a BDC call; and
updates the IDoc status according to the BDC error status.
EXTRACT FROM: Z_IDOC_INPUT_ZINVRV
Declaration of local variables
DATA: C_SEGNAM(10) TYPE C VALUE 'Z1INVRV'.
*-Loop through the IDOCs
LOOP AT IDOC_CONTRL.
*---Loop through the data for the IDOC
LOOP AT IDOC_DATA WHERE DOCNUM = IDOC_CONTRL-DOCNUM.
CASE IDOC_DATA-SEGNAM.
WHEN C_SEGNAM.
Here we get the info from the idoc table
IT_Z1INVRV = IDOC_DATA-SDATA.
ENDCASE.
PERFORM REV_INV.
ENDLOOP.
PERFORM UPDATE_IDOC_STATUS.
ENDLOOP.
FORM REV_INV "Reverse invoice form
Local variables & constants
DATA: C_TCODE LIKE BKPF-TCODE VALUE 'VF11'. "BDC transaction code
Now we can build the bdc table to call the reversal transaction start of screen 109
CLEAR BDC_TAB.
BDC_TAB-PROGRAM = 'SAPMV60A'.
BDC_TAB-DYNPRO = '109'.
BDC_TAB-DYNBEGIN = 'X'.
APPEND BDC_TAB.
Document number
CLEAR BDC_TAB.
BDC_TAB-FNAM = 'KOMFK-VBELN(01)'.
BDC_TAB-FVAL = IT_Z1INVRV-XBLNR. "Billing document number
APPEND BDC_TAB.
OK Code for screen 109
CLEAR BDC_TAB.
BDC_TAB-FNAM = 'BDC_OKCODE'.
BDC_TAB-FVAL = 'SICH'.
APPEND BDC_TAB.
Now we can call transaction 'VF11' with the populated bdc table. The transaction is called inside the idoc-contrl loop, so a transaction will be called for every idoc (journal). the transaction is called in no-display mode ('N') because this code runs in background as it is called by ale. The update is specified to be synchronous ('S') because we have to wait for the result to update the idoc status correctly.
CALL TRANSACTION C_TCODE USING BDC_TAB MODE 'N' UPDATE 'S'.
Store the return code for use in another form (status update)
RETURN_CODE = SY-SUBRC.
Here we check the return code, if there was an error, we put the transaction in a bdc session for the user to review and correct.
IF SY-SUBRC NE 0.
CALL FUNCTION 'BDC_OPEN_GROUP'
EXPORTING
CLIENT = SY-MANDT
GROUP = 'ZINVRV'
USER = C_ALE_USER
KEEP = 'X'.
CALL FUNCTION 'BDC_INSERT'
EXPORTING
TCODE = C_TCODE
TABLES
DYNPROTAB = BDC_TAB.
CALL FUNCTION 'BDC_CLOSE_GROUP'
EXCEPTIONS
NOT_OPEN = 1
QUEUE_ERROR = 2
OTHERS = 3.
ELSE. "No problems
C_EXISTS = 'N'.
Select from the billing document table to get sales doc number
SELECT * FROM VBRP WHERE VBELN = IT_Z1INVRV-XBLNR.
Select from the sales document table to get user status number
SELECT SINGLE * FROM VBAP WHERE VBELN = VBRP-AUBEL AND
POSNR = VBRP-AUPOS.
Select from the status table to change the user status to pending
SELECT * FROM JEST WHERE OBJNR = VBAP-OBJNR AND
STAT LIKE C_USER_STATUS.
IF JEST-STAT = C_US_PENDING. "User status is pending
JEST-INACT = C_UNCHECKED. "Make pending the active status
UPDATE JEST.
C_EXISTS = 'Y'. "I.E. An entry is already in table
ELSEIF JEST-INACT = C_UNCHECKED AND JEST-STAT NE C_US_PENDING.
JEST-INACT = C_CHECKED. "Make everything else inactive
UPDATE JEST.
ENDIF.
ENDSELECT.
IF C_EXISTS = 'N'. "I.E. Pending has never been a status before
JEST-OBJNR = VBAP-OBJNR.
JEST-STAT = C_US_PENDING.
JEST-INACT = C_UNCHECKED. "Make pending the active status
INSERT JEST.
ENDIF.
ENDSELECT. "Select from VBRP (Billing document table)
ENDIF.
ENDFORM. " REV_INV
FORM UPDATE_IDOC_STATUS.
Now we check the CALL TRANSACTION return code and set IDOC status
CLEAR IDOC_STATUS.
IF RETURN_CODE = 0.
WORKFLOW_RESULT = '0'.
IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
IDOC_STATUS-STATUS = '53'.
IDOC_STATUS-UNAME = SY-UNAME.
IDOC_STATUS-REPID = SY-REPID.
IDOC_STATUS-MSGTY = SY-MSGTY.
IDOC_STATUS-MSGID = SY-MSGID.
IDOC_STATUS-MSGNO = SY-MSGNO.
IDOC_STATUS-MSGV1 = SY-MSGV1.
IDOC_STATUS-MSGV2 = SY-MSGV2.
IDOC_STATUS-MSGV3 = SY-MSGV3.
IDOC_STATUS-MSGV4 = SY-MSGV4.
RETURN_VARIABLES-WF_PARAM = 'Processed_IDOCs'.
RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
APPEND RETURN_VARIABLES.
ELSE.
WORKFLOW_RESULT = '99999'.
IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
IDOC_STATUS-STATUS = '51'.
IDOC_STATUS-UNAME = SY-UNAME.
IDOC_STATUS-REPID = SY-REPID.
IDOC_STATUS-MSGTY = SY-MSGTY.
IDOC_STATUS-MSGID = SY-MSGID.
IDOC_STATUS-MSGNO = SY-MSGNO.
IDOC_STATUS-MSGV1 = SY-MSGV1.
IDOC_STATUS-MSGV2 = SY-MSGV2.
IDOC_STATUS-MSGV3 = SY-MSGV3.
IDOC_STATUS-MSGV4 = SY-MSGV4.
RETURN_VARIABLES-WF_PARAM = 'ERROR_IDOCS'.
RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
APPEND RETURN_VARIABLES.
ENDIF.
APPEND IDOC_STATUS.
ENDFORM. " UPDATE_IDOC_STATUS
Figure 5: Inbound processing example code
3.1.1. Debugging inbound FM
Use transaction WE19 to test inbound function module in debugging mode. Also use WE05 to view the IDocs and their statuses.
3.2. Maintain ALE attributes
The inbound function module needs to be linked to the message type and the message type needs to be linked to the appropriate inbound process code at the partner profile level before the scenario is enabled. These steps are described below in detail.
3.2.1. Link Message Type to Function Module (WE57) Client independent
To link a message (ZINVRV) type to a function module (Z_IDOC_INPUT_ZINVRV) follow these steps:
Enter transaction WE57 (ALE -> Extensions -> Inbound -> Allocate function module to logical message)
Select an entry (EG. IDOC_INPUT_ORDERS) and copy
Type in module name Z_IDOC_INPUT_ZINVRV
Type in basic IDoc type as ZINVRV01
Type in message type as ZINVRV
Type object type as IDOCINVOIC (Invoice document) - Used for workflow
Direction should be set to 2 for inbound
Enter and save
3.2.2. Define FM settings (BD51) Client independent
Enter transaction BD51 (ALE -> Extensions -> Inbound -> Define settings for input modules)
Click on New entries
Type in the name of the new function module Z_IDOC_INPUT_ZINVRV
Enter 0 for mass processing in the output column
Save and Exit
3.2.3. Maintain process codes (WE42) Client dependent
A process code needs to be maintained on each client. It then needs to be linked to the message via the partner profiles on each client. This allows the various clients to use a unique function module for the same message type.
To maintain the process code follow these steps:
Log on to the appropriate receiving system client
Execute WE42 (ALE -> Extensions -> Inbound -> Maintaining process codes inbound)
Choose Inbound with ALE service
Choose Processing with function module
Click on Processing with function module and choose create icon
Click on New Entries
Type in process code ZINR and give it a description and save
Now you are asked to Please maintain codes added in ALE entry methods, enter and choose Z_IDOC_INPUT_FIRVSL and copy it. You should choose a FM similar to your one.
Enter your process code ZINR
Enter your function module Z_IDOC_INPUT_ZINVRV
NOTE: The next 6 steps are used in workflow error handling.
Enter IDPKFIDCMT in object type
Enter MASSINPUTFINISHED in End event
Enter IDOCINVOIC in IDoc object type
Enter INPUTERROROCCURREDFI in IDoc start event
Enter INPUTFINISHEDFI in IDoc End event
Enter IDOCINVOIC in Application object type
You will need to determine the task associated with object IDOCINVOIC, and then assign the appropriate position to it. This position will then receive the application error messages via workflow.
To set up the workflow area please consult the Workflow config guide.
3.3. Create inbound partner profile
For each message type you need to maintain the inbound partner profiles.
3.3.1. Maintain receiving system partner profile (WE20) Client dependent
To maintain inbound partner profiles read the document ALE configuration procedure:
Add the message type ZINVRV with process code ZINR.
Enter the output mode (background, immediately) for inbound processing and NO message code.
Enter the position S and choose the ALE administrator 50000085. This position will then receive all the technical ALE errors via workflow.
3.4. Test
Once the inbound function module has been debugged the scenario should be ready to test in its entirety. If problems occur, read through the relevant areas of this document to check your configuration or code.
Hope this will help you,
If you want me to explain more, you can give me your email id.
Reward with points incase you are satisfied.
Regards,
Sushama -
Hi All,
Currently i'm working on the following requirements. we are using TIBCO system as a middleware tool and it will ceate an IDOC which needs to be directed to R/3 system. As we have already imported the IDOC to the TIBCO system and then it will fetch the data from non-SAP system and creates the IDOC and sends it to R/3 system? I've done the following ALE configurations but got the error message as 56..."Partner profile is not define".
I've done the following ALE configurations at R/3 side.
1. Created a logical system and RFC destination for TIBCO.
2. created a TRFC port.
3. Create a Partner profile and linked the TRFC port.
4. posted an IDOC from WE19.
but when i checked the status of IDOC in WE02 its displaying an warning message with status code 56 "Partner profile is not define". and i think no need to do any ALE Configuration at sender side since the sender system is TIBCO.
pls correct me if i'm wrong. as one of my colleage suugested me to create FIle port instead of TRFC port?
regards
FaisalHI
SAP R/3
R/3 to XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
XI to R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1) ( Create port to get IDOC Meta data from sender system)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2) (To maintain IDOC Metadata, it is needed by XI because XI needs to construct IDOC-XML from IDOC. It is not needed by any sap system).
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
Refer the below links for further assistance
4.create partner profile using idx2
ALE configuration for pushing idocs from SAP to XI
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
IDOC testing using WE19
/people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi
File To IDOC - Part1 (SLD and Design):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
File To IDOC - Part2 (Configuration):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
File To IDOC - Part3 (Steps required in XI and R3):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)
cheers -
Unable to open jsp file in Design mode
Hi,
I am unable to open jsp files in design mode, I am using eclipse Version: 3.6.1.
Please help.
Regards,
Ale HasanHi Ale,
Thank you for the additional information. Unfortunately, there does not seem to be anything unusual about your project based on your description. I'm surprised you don't see any processes listed in the process view while waiting for the page to open. I thought you might see something related to a queue manager job to "Manage Resource Event Jobs".
Are there any messages in the error.log? You can open a view to the error log from the menu option, "Window -> Show View -> Error Log". I'm curious if there are any messages about a process timing out, unable to reset some object within a certain time, or any exceptions logged.
If you change to another workspace with just a single JSF web project containing a smaller number of JSP, do you experience the same behavior?
Can you also try using a more recent release of OEPE to see if that helps? The 11.1.1.6.1 release is about a year old.
http://www.oracle.com/technetwork/developer-tools/eclipse/downloads/index.html
Kind regards,
Carlin -
IDOC Receiver - Unable to convert sender service to ALE
Hi!!!
I am trying to configure the following scenario: FILE - XI - IDoc to R/3.
A business service called IDOC_Demo recovers from the server the file, and after mapping it, it tries to send it to IBP, the R/3 system using a IDOC Receiver comunication channel.
IBP is configured in SLD.
I have in XI System the RFC conexion, and I have define the port via TCODE IDX1.
But it does not work, I am geting the following error:
"Unable to convert sender service IDOC_Demo to an ALE logical system"
I have checked the adapter specific identifiers, but I can not see anything wrong...
I do not know what can I check! Could someone help me?! What can I do?
Thank a lot!!
Araitz.Thank you very much, but I still get the error message! Of course, I read your blogs Michal before posting the question, and they have been very useful, but still...
In SLD I only have the R/3 system, the name is IBP and the business landscape and the logical system name (I do not know if this could cause a problem ).
The connexion is IBP, and it works, and in idx1 I have configured a port, and its name is SAPIBP, using the IBP connexion.
Design I have imported the CREMAS.CREMAS03 IDOC, and I have done a mapping interface, I have disabled the EDI_DC40, and set begin and segment to 1.
Configuration I have created a business service, IDOC_Demo, that has a communication channel, sender, file type.
And I have the IBP service. In adapter specific I can see: logical system IBP, and R/3 System IBP, client 100. If I push the Compare with SLD button, nothing happens what should happen?
IDOC_Demo receives the file, and via an Outbound, async interface, calls IBP, that receives the IDoc using a receiver IDoc type adapter
Now the receiver agreement has information in the header mapping, sender service, IDOC_Demo, receiver service, IBP.
And I do not know why, but it does not work any idea?
Than you!
Araitz. -
Resend data unless webmethod receive SOAP data successfully
Hi All,
I want to implement a scenario like as follows:
SAP->Idoc->XI->BPM->SOAP->webmethod
In above scenario whenever HTTP-SOAP communication fails. I want to re-send data after 5 min using BPM to HTTP-SOAP, unless webmethod receive data successfully.
Can any one help me in designing above scenario?
I have very less knowledge of BPM.
<b>Can I do above scenario without BPM, because BPM having some performance issues???</b>
RegardsHi Umesh,
One of the way probably-
Recieve the message(idoc) from the SAP to XI.
Send the Message Synchrnously to the SOAP(Webmethod)
Wait for the positive acknowledgement.. Until you get Positive acknowledgement, you can keep on sending the data from BPM .. But this loop will be kind of infinite..
Some info-
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/65c42db39b0398e10000000a1553f6/content.htm
Without BPM,I don't think so, directly
Hope this helps,
regards,
moorthy -
Can we use HTTPS with ALE to establish a connection between the HR and ERP system? There are seperate instances for FI and HCM and we require an ALE interface between them. RFC with SNC is not an option so am wondering if there is an ALE with HTTPS route we can take? Any info will be greatly appreciated.
Hi Fahad,
As far i know there is no way to using https for ALE without PI. because ALE is base on RFC technology not http / https.
if my knowledge correct then you might need to use other middleware like SAP PI, webMethods, Tipco etc or if not you might need to do some customize scenario using webservices. but both of your ERP and HCM must be at least ECC 6.
for IDOC for example you can set the port to generate xml file. and create program to pickup and send it over soap https to HCM system.
Please correct me if i am wrong.
Regards
Fernand. -
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 anybody,
Please tell me what is IDOC and ALE? What pupose using IDOC and ALE?
Give me Example sample code of using IDOC and ALE.
Thanks
S.Muthu.Dear,
Here is some facts which will be helpful to clear yr concepts for ALE/IDOCs.
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.
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.
*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.
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.
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
How to create idoc?
*WE30 - you can create a IDOC type
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
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)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
This report creates IDocs from the change pointers for the specified message type. It then sends them to the receiving system and flags the change pointers as processed in respect of the specified message type.
The receiving systems for the specified message type are determined from the customer distribution model.
Output:-The report outputs information about the number of master IDocs and communication IDocs created.
RSEOUT00 Process all selected IDocs (EDI) Report for generation of files for EDI outbound processing.The report processes the IDocs available in the system with the status 'to be processed'. The IDocs are selected according to the selection options and parameters specified.
It is important that you make sure that only test messages or productive messages are selected.
The IDocs are processed in various files for various output modes and for various ports. The names of the files are created according to the naming definition for the outbound file. This definition is determined in the port definition.
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
For testing you can use WE19.
Hope This will be helpful,
Best Regards ,
P Singh -
HI ALL,
CAN YOU TELL ME A BRIEF ABOUT ALE, EDI, WAS, BSP, BAPI AS IT IS VERY COMMON IN EVERY INTERVIEW ?
REGARDS
RAJARSHIHi Rajarshi,
IDOCS:
IDOCS are intermediary documents which are like CARRIERS of the data
IDOCs are safe to transfer data, but less volume of data. User is not allowed to access (modify) the data like PSA. IDOCs have 3 parts.
1. Control Record - SOURCE & TARGET details,
2. Data Record - Here comes your query....
Info IDOC - It contains all the technical details related to the data load i.e. Request NO, No of Data Packages, USER, DATE, TIME, LOGICAL SYSTEM, etc. Info IDOC is also ONE segment, the 1 sr segment.
Here data will not be there.
Data IDOC - These are the ones which hold the data. The total no of records are made into Data IDOCs i.e. if 99 records are there then 99 Data IDOCs will be there and all these will be divided into 99 segments.
Hence the total number of Segments in IDOC is 100.
Info IDOC + Data IDOCs = Total no of Segments
1 + 99 = 100.
3. Status Record - Here the status of the data transfer will be available.
ALE:
ALE is Application linking & Enabling which enables to interface SAP with other modules
Pl go through below links as they provide all the required info on ALE & IDOC's:
ALE / IDOC:
Please check this online document for ALE and IDoc.
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
Also check this links for additional information.
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
u will have enough material from above .....
Mostly SD consultant doesnt deal with EDI, Idocs but its always good to have knowledge,
EDI
EDI concept in SD: the EDI concept is intended to realize the sales and distribution process completely automatically with the help of electronical documents. These documents are sent from one customer to another, are processed mostly on the background and give a possibility to realize the sales process extremely efficiently.
If MM-customer would like to purchase the goods then he creates the IDOC of type ORDERS and send it to SD-customer. On the SD-side the IDOC is processed via the function module IDOC_INPUT_ORDERS and creates the sales order. As confirmation the SD-side can send to MM-side the Order-Response IDOC (function IDOC_OUTPUT_ORDERS). The MM-customer can every time send a change to the existing order, then on SD side the ORDCHG IDOC will be processed. It can change the order like in VA02. The creation of the invoice can be made via IDOC of message type INVOIC (function IDOC_OUTPUT_INVOIC).
So, the process can be realized completely automatically between SD and MM partners with the help of IDOCs: ORDERS, ORDCHG, ORDRSP, and INVOIC.
That's all concerning the SD-EDI.
Additional processes in SD, where EDI are used:
1) application of delivery schedules to the scheduling agreement: IDOC of type DELINS
2) creation of a delivery order to the scheduling agreement: IDOC of type DELORD
3) creation of external agent service delivery to scheduling agreement: IDOC of type EDLNOT
4) creation of credit advice / credit memo in the frames of self-billing: IDOCs of type GSVERF, SBWAP and for external invoice creation SBINV.
It is all processes which are realized in the SD module via EDI.
Go through this, You will get better idea on EDI,ALE,IDOCS
The interface concept of the classic R/3 is based on two different strategies: Remote Function Calls (RFC) and data exchange through IDoc message documents. RFC makes direct and synchronous calls of a program in the remote system. If the caller is an external program it will call an RFC-enabled function in R/3 and if the calling program is the R/3 system it will call an RFC-function in another R/3-system or it will call a non-R/3 program through a gateway-proxy (usually rfcexec.exe). BAPIs are a subset of the RFC-enabled function modules, especially designed as Application Programming Interface (API) to the SAP business object, or in other words: are function modules officially released by SAP to be called from external programs.
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.
The philosophical difference between EDI and ALE can be pinned as follows: 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.
BAPI:
BAPI (Business Application Programming Interface) 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.
BAPIs (Business Application Programming Interfaces) are the
standard SAP interfaces. They play an important role in the
technical integration and in the exchange of business data
between SAP components, and between SAP and non-SAP
components. BAPIs enable you to integrate these components
and are therefore an important part of developing
integration scenarios where multiple components are
connected to each other, either on a local network or on the Internet.
BAPIs allow integration at the business level, not the
technical level. This provides for greater stability of the
linkage and independence from the underlying communication
technology
http://www.erpgenie.com/sap/abap/bapi/example.htm
http://www.sap-img.com/bapi.htm
http://help.sap.com/saphelp_nw04/helpdata/en/e0/9eb2370f9cbe68e10000009b38f8cf/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/43/b46c1e53c111d395fa00a0c94260a5/content.htm
http://www.sappoint.com/abap/bapiintro.pdf#search=%22BAPI(SAP)%22
http://www.erpgenie.com/sap/abap/bapi/index.htm
http://www.erpgenie.com/sap/abap/bapi/conventions.htm
http://www.erpgenie.com/sapgenie/docs/BAPI%20Programming.doc
http://64.233.167.104/custom?q=cache:eyMZ5qPOH-0J:www.erpgenie.com/sapgenie/docs/BAPI%2520Intro.doc+bapi&hl=en&ct=clnk&cd=6&ie=UTF-8&client=pub-2723892367221695
http://64.233.167.104/custom?q=cache:c7cwsXMxq-UJ:www.sapdevelopment.co.uk/java/jco/bapi_jco.pdf+bapi&hl=en&ct=clnk&cd=1&ie=UTF-8&client=pub-6389415953938571
List of all bapis
http://www.planetsap.com/LIST_ALL_BAPIs.htm
FOR BAPI's
http://www.sappoint.com/abap/bapiintro.pdf
Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula -
Hi Friends,
Please send me some good documents on ALE,EDI and IDOCs.
Some step by step documents and documents related to all the related transactions will be most welcome.
Mukesh KumarHello,
I have created a customised IDOC scemnario and have a document designed by me with all the minute steps and with screen shots.
Please have a look at http://www.geocities.com/xplosion78/customised_ALE_IDOC_BY_SACHIN_DABHADE.zip
Please reward points if useful.
thnx
Link for that is:
http://www.erpgenie.com/sap/ale/whitepaper.htm
==============================
Other helpful links
http://www.sapgenie.com/whitepapers/ale.htm
http://www.sapgenie.com/ale/index.htm
http://www.sappoint.com/abap.html
http://www.sapbrain.com/TUTORIALS/TECHNICAL/ALE_tutorial.html
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/CABFAALEHR/CABFAALEHR_ALE_QS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/ECPCA/ECPCA_ALE_154.pdf
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
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
Please reward points if useful.
thnx -
Hi Experts,
What is the diff btn EDI and ALE.
Straight answers will be rewarded.
Regards,
SAIHi,
In simple words ...
ALE is technology for SAP mainly use to transfer data between SAP systems.
EDI is the independent technology use to transfer data between two systems, they can be SAP systems or non SAP systems.
ALE = Application Link Enable: Initially developed for SAP as an abstract layer to extract master and transactional data to be sent ellectronically to other SAP systems. These days is also being used to send data no non-SAP systems. ALE is not a protocol or anything like that, it's just abstract layer composed by a set of applications which are capable of extracting aplication data on a 1-time basis or periodically, by selection criteria or incrementally by deltas.
In contrast, EDI = Electronic data interface, this is a comunication protocol not designed by SAP but it´s an industry standard. Of course most SAP software supports EDI, but EDI it's no software but the specification of the protocol in itself.
Regards,
Padmam. -
Regarding an error when an idoc is transferred through ALE
hi guys,
i have designed a custom message type and sent an idoc from server 1 to server 2 ( receiver system ) <b>using ALE</b>, idoc is transferred fine but data in idoc is not sent to receiver system i mean, there is no data in idoc.
i received an error saying: idoc transferred with errors at inbound system.
<b> it displays status 56 i.e EDI: partner profile not defined.</b>
but partner profile and model view for both outbound and inbound system have been absolutely configered.
can you plss help me with this.
thanks very much
pavanhi appana,
thx for ur suggestion, actually outbound idoc is populated but problem is with inbound idoc - there is no data in it.
what exactly do u mean by partner profile maintained for this idoc at inbound, actually i have created partner profile at inbound using we20 and assinged custom message type and process code ( functin module developed by me) to msgtype.
can u be elaborative.
thanks
pavan.
Maybe you are looking for
-
Can you move files between two different user accounts in Time Capsule?
I copied a bunch of stuff from my old NAS (which used FAT) to Time Capsule under one user account... I then reformatted the NAS to HFS+ so I could just use it as a USB drive connected to the TC. Now I realized that I want to have one of those folders
-
Error when running a program /RPM/FIN_PLAN_INT
when executing the program "/RPM/FIN_PLAN_INT", I'm getting an error stating as "Category ID does not exist for item.Instantiate categories first" This error is hitting for only 4 Items in list of all 173 Item. Hence the Financial cost are not gettin
-
How can I change the colors of a photo?
How can I change the colors in a photo?
-
Why wont my phone connect to my laptop
why wont my iphone connect to my laptop to go onto itunes????
-
CS3 does not show up in add/remove programs
To free up space on my laptop I want to uninstall CS3 since CS4 seems to function just fine but CS3 does noet show up in Programs and Features (Windows Vista Home Premium). CS4 does show up in the list. How do I safely uninstall CS3? Thank you.