Idoc to HTML

hi Friends,
I am doing idoc to HTML file scenario with out using BPM and have to use xslt mapping can some body suggest me some example for the scenario.Please reply soon .
Thanks & Regards,
Vinay Yadav

Why do you want HTML? What is your scenario?
How should your HTML look like?

Similar Messages

IDOC TO HTML FILE SCENARIO WITH XSLT MAPPING

Hi ,
I am doing idoc to html file using xslt mapping can anyone provide me some help(material or example ) please reply soon.
Thanks & Regards,
Vinay Yadav

Hi ,
For xslt mapping the place to start is
http://www.w3schools.com/.
in help.
http://help.sap.com/saphelp_nw2004s/helpdata/en/83/2200cb50d345c793336d9a1683163e/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/a4/64b93d0d4e6b3be10000000a114084/frameset.htm
There are some blogs here which can proove to be good.
/people/pooja.pandey/blog/2005/06/27/xslt-mapping-with-java-enhancement-for-beginners
/people/pooja.pandey/blog/2005/06/27/xslt-mapping-with-java-enhancement-for-beginners
https://weblogs.sdn.sap.com/pub/wlg/3823 [original link is broken] [original link is broken] [original link is broken] [original link is broken]
Regards ,
Deepak
/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping

Inbound idoc status 62

hi,
am getting the sales order as inbound with status 62.
can anybody reply how to rectify this problem.
but in we19 i have executed privious idocs it will give the status 53,

Hi Sathish,
Please check the following links given below:
IDOC:
http://www.sapbrainsonline.com/ARTICLES/TECHNICAL/idoc/SAP_IDOC_structure_introduction.html
Status codes:
http://publib.boulder.ibm.com/tividd/td/ITMAN/SC23-4812-00/en_US/HTML/sa51mst256.htm
Regards
Satish

Idoc Testing! Need help!

Hi!
   (Please give answers specific to my question & pls read below)
     i want to test idoc outbound as well as inbound.
First Consider inbound,
   I ve read previous posted threads it was mentioned goto>we19> give idoc no
I want to know <b>what is idoc no how we get idoc no for the idoc.
</b>
Then i know the steps...
Now Outbound,
How to test outbound idoc -- i want to know how my posting program has correctly generated idoc to ale layer.
I want this in complete detail.
   Thanks!
   Rahul.

Hi Rahul,
<b>idoc structure</b>
http://www.sapbrainsonline.com/ARTICLES/TECHNICAL/idoc/SAP_IDOC_structure_introduction.html
<b>What is Idoc?</b>
<b>I give overview of IDoc terminology and how IDocs work in an enterprise will clarify the process</b>
SAPs presence in the IT world is justified by a central premise: It turns a companys many individual systems into one, big supersystem. More than a linking together of applications, SAPs implementation causes a redirection of the flow of information through a company and its partner companies that enhances the potential of its business functions.
This flow of information is enabled by a core element in SAP technology: the Intermediate Document, or IDoc. Technically, the IDoc is an example of Electronic Data Interchange (EDI). Unlike conventional EDI, IDocs are not based on a descriptive language.
The IDoc concept borrows the best features of EDI and combines them with the best features of conventional transaction file formats. The result is a lean data transport mechanism that is the engine of SAP data flow, tying together applications, databases, companies, and networks. Here is a look at the makeup of IDocs within the application architecture.
Form and content: IDoc terminology
As is often the case with proprietary technologies, SAP assigns specific, object-oriented meanings to familiar terms. When referring to IDocs, the term document refers to a set of data comprising a functional group of records with a business identity. (For example, all the data in a purchase order, or all the profile information of a supplier in a supplier master record.)
A message refers to the contents of a specific implementation of an IDoc; its a logical reference. This differs from a reference to the IDoc itself, which specifies the messages physical representation. Think of it this way: If youre watching a parade pass by, the mayor waving to the crowd from his limousine is the message, and the mayors limousine (which is specific to the mayor) is the IDoc. Youre building a logical object, and the IDoc is both its container and the vehicle that moves it.
The IDoc control record
Each IDoc has a single control record, always the first record in the set. The structure of this record describes the content of the data records that will follow and provides administrative information, such as the IDocs functional category (Message Type/IDoc Type), as well as its origin (Sender) and destination (Receiver) as in conventional EDI (see Figure A).
Figure A
IDOC number Sender Receiver Port Message type IDoc type
1234567890    R3NYC R3LA     FILE INVOICES       INVOICE01
This cover slip format informs the receiving system of the IDocs purpose, and the receiving system uses it to determine the correct processing algorithm for handling the arriving IDoc.
Data records
The data records following the control record are structured alike, including two sections: a segment information section and a data section.
In the first part of a data record, the segment information section describes the structure of the data that follows, for the benefit of the IDoc processor. There is a segment name (like an EDI segment identifier) that corresponds to a data dictionary structure to which the IDoc processor has access. The remaining information is useful for foreign systems, such as a partner companys Oracle system, which has no such data dictionary.
The second part of the record is the data itself, a storage area of 1,000 characters.
Status records
If youve ever ordered a package from a faraway location and tracked its progress using the Internet-based tracking utilities now provided by most major parcel carriers, youre familiar with the list of stops and transfer points through which a package passes on its way to you.
This collection of records is exactly what youll see in an IDoc that has begun its work. Following the data records in an IDoc, status records accumulate as an IDoc makes its way from one point in a process to another.
Typically, an IDoc will acquire several of these records as its does its job. They are simple records, consisting of a status code (there are more than 70 codes, covering a broad range of conditions and errors), a date/time stamp, and some additional status information fields for system audit purposes. In addition, as errors occur in the processing of an IDoc, status records (see Figure B) are used to record these errors and the date/time of their occurrence.
Figure B
(Display Status Record)
IDoc number 0000000000123456
Direction 1 Outbound
Status information
     38 IDoc archived
(additional descriptive text)
Log time
    Date 6-30-02
    Time 14:35:21
Portion of IDoc status display
IDoc Base
IDocs, as data formatting tools, enable the easy sharing of data between databases and applications within a company as well as being an efficient data courier between companies. Typically in SAP, a database of IDoc definitions exists, to which any application may have access.
This IDoc Base gives all the applications and processes in your company domain the capacity to send, receive, and process a document in a contextually appropriate way, without doing anything to the data. For example, a purchase order IDoc can filter through every process it touches, passing from system to system, accumulating status records to track its progress.
Every department using the data can use it appropriately without any cumbersome intermediate processes, because each department draws its key to interpreting the IDoc from the same source.
Multiple messages
One cumbersome feature of conventional EDI is the embedding of more than one functional record type in a document. The unwieldy X-12 888 Item Maintenance transaction set is an example: It purports to handle so many different configurations of product master data that it is horrifically difficult to integrate into an existing system.
IDocs, on the other hand, handle multiple messages with ease. Given the centralized IDoc interpretation that SAP provides to all its parts, its no problem to define an IDoc that will contain more than one message, that is, more than one data record type.
A customer master IDoc, for example, may contain customer profile information records for a customer with many locations. But it may also contain location-specific pricing information records for that customer in the same document. This is an incredibly efficient way of bundling related records, particularly when passing large amounts of complex information from system to system (see Figure C).
Figure C
CONTROL RECORD
DATA RECORD - CUST PROFILE LOC #1
DATA RECORD - CUST PROFILE LOC #2
DATA RECORD - CUST PROFILE LOC #3
DATA RECORD - CUST DISCOUNT STRUCTURE LOC #1
DATA RECORD - CUST DISCOUNT STRUCTURE LOC #2
DATA RECORD - CUST DISCOUNT STRUCTURE LOC #3
STATUS RECORD
STATUS RECORD
STATUS RECORD
Records in a multiple-message IDoc
Final thought
There is no mastering SAP without mastering its workhorse, the IDoc. ERP environments utilizing SAP and similar platforms are made necessary in the first place by the increasing demands of ever more integrated business relationships. IDoc technology addresses this trend with a simple but powerful design philosophy: Data is no longer something to be stored; its something to be moved.
<b>And</b>
These links give u complete details abt idocs testing
Test Tool
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b80f643d711d1893e0000e8323c4f/content.htm
Status Monitor for ALE Messages
http://help.sap.com/saphelp_nw04/helpdata/en/d4/0d67e4d85511d2a6080060087832f8/content.htm
Regards ,
Kumar.

Folder_g component wizard failure from R35UpdateBundle Extra patch

Installed and had running the 10gR3 version 10.1.3.3.3 (version 20080807) using MS sqlserver as backend db http://download.oracle.com/otn/content_management/V13682-01.zip. See edit for additional details at the resource level.
Applied the patches in the following order:
CS10gR35UpdateBundle-20090707-11 (Version 10.1.3.5.0) http://download.oracle.com/otn/content_management/CS10gR35UpdateBundle-20090707-11.zip
CS10gR34ContentAccessUpdate-20090505-4 (Version 10.1.3.4.1) http://download.oracle.com/otn/content_management/CS10gR34ContentAccessUpdate-20090505-4.zip
CS10gR34NativeUpdate-20090708-5 (Version 10.1.3.4.1) http://download.oracle.com/otn/content_management/CS10gR34NativeUpdate-20090708-5.zip
IBR10gR3UpdateBundle-20090630-26 (Version: 10.1.3) http://download.oracle.com/otn/content_management/IBR10gR3UpdateBundle-20090630-26.zip
Able to log into content server with the admin user, checked that Version 10.1.3.5.0 has been applied
Lost the ability to edit the folder structure under the Browse content option
Launched the component wizard to examine if the Folder_g was enabled
Custom Component List shows
Folders_g     Enabled     c:/oracle/UCM/server/install/custom/Folders_g/Folders_g.hda
Attempted to open this component I receive the following error dialog box
“Please correct the following errors:
!csCompWizMergeTableNotFound, VCR_FOLDERS_ServiceHandlersFile ‘c:/oracle/UCM/server/install/custom/Folders_g/resources/vcr_folders_tables.idoc’ is invalid resource file type.
File ‘c:/oracle/UCM/server/install/custom/Folders_g/resources/lang/en/vcr_folders_strings.idoc’ is invalid resource file type.
Can anyone give me a starting point to how to resolve this error.
Regards
Rob
The contents of ‘ c:/oracle/UCM/server/install/custom/Folders_g/resources/vcr_folders_tables.idoc’ is
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>VCR_FOLDERS htmlIncludeOrString</title>
</head>
<body>
<@table VCR_FOLDERS_ServiceHandlers@>
<table>
<tr>
     <td>serviceName</td>
     <td>handler</td>
     <td>searchOrder</td>
</tr>
<tr>
     <td>Service</td>
     <td>vcr_folders.VcrFoldersServiceHandler</td>
     <td>100</td>
</tr>
</table>
<@end@>
<@table VcrFoldersFieldDefinitions@>
<table>
     <tr>
          <td>name</td>
          <td>description</td>
          <td>propertyDefinitionType</td>
          <td>propertyType</td>
          <td>isMandatory</td>
          <td>isReadOnly</td>
          <td>isMultiValued</td>
          <td>isRestricted</td>
          <td>isSearchable</td>
          <td>isPrimary</td>
          <td>nestedClass</td>
     </tr>
     <tr>
          <td>dCollectionID</td>
          <td>wwCollectionID</td>
          <td>NATIVE</td>
          <td>LONG</td>
          <td>1</td>
          <td>1</td>
          <td>0</td>
          <td>0</td>
          <td>1</td>
          <td>0</td>
     </tr>
     <tr>
          <td>dCollectionPath</td>
          <td>wwCollectionPath</td>
          <td>NATIVE</td>
          <td>STRING</td>
          <td>1</td>
          <td>1</td>
          <td>0</td>
          <td>0</td>
          <td>1</td>
          <td>0</td>
     </tr>
     <tr>
          <td>dCollectionGUID</td>
          <td>wwCollectionGUID</td>
          <td>NATIVE</td>
          <td>STRING</td>
          <td>1</td>
          <td>1</td>
          <td>0</td>
          <td>0</td>
          <td>1</td>
          <td>0</td>
     </tr>
     <tr>
          <td>dParentCollectionID</td>
          <td>wwCollectionParentCollectionID</td>
          <td>NATIVE</td>
          <td>LONG</td>
          <td>1</td>
          <td>1</td>
          <td>0</td>
          <td>0</td>
          <td>1</td>
          <td>0</td>
     </tr>
     <tr>
          <td>dCollectionName</td>
          <td>wwCollectionCollectionName</td>
          <td>NATIVE</td>
          <td>STRING</td>
          <td>1</td>
          <td>0</td>
          <td>0</td>
          <td>0</td>
          <td>1</td>
          <td>0</td>
     </tr>
     <tr>
          <td>dCollectionType</td>
          <td>wwCollectionType</td>
          <td>NATIVE</td>
          <td>LONG</td>
          <td>1</td>
          <td>1</td>
          <td>0</td>
          <td>1</td>
          <td>1</td>
          <td>0</td>
     </tr>
     <tr>
          <td>dCollectionMark</td>
          <td>wwCollectionMark</td>
          <td>NATIVE</td>
          <td>STRING</td>
          <td>1</td>
          <td>1</td>
          <td>0</td>
          <td>0</td>
          <td>1</td>
          <td>0</td>
     </tr>
     <tr>
          <td>dDependent</td>
          <td>wwCollectionDependent</td>
          <td>NATIVE</td>
          <td>STRING</td>
          <td>0</td>
          <td>1</td>
          <td>0</td>
          <td>0</td>
          <td>1</td>
          <td>0</td>
     </tr>
     <tr>
          <td>dCollectionQueries</td>
          <td>wwCollectionQueries</td>
          <td>NATIVE</td>
          <td>LONG</td>
          <td>1</td>
          <td>1</td>
          <td>0</td>
          <td>0</td>
          <td>1</td>
          <td>0</td>
     </tr>
     <tr>
          <td>dCollectionEnabled</td>
          <td>wwCollectionEnabled</td>
          <td>NATIVE</td>
          <td>LONG</td>
          <td>1</td>
          <td>0</td>
          <td>0</td>
          <td>0</td>
          <td>1</td>
          <td>0</td>
     </tr>
     <tr>
          <td>dCollectionInherit</td>
          <td>wwCollectionInherit</td>
          <td>NATIVE</td>
          <td>LONG</td>
          <td>1</td>
          <td>1</td>
          <td>0</td>
          <td>0</td>
          <td>1</td>
          <td>0</td>
     </tr>
     <tr>
          <td>dChildManipulation</td>
          <td>wwCollectionChildManipulation</td>
          <td>NATIVE</td>
          <td>LONG</td>
          <td>1</td>
          <td>1</td>
          <td>0</td>
          <td>0</td>
          <td>1</td>
          <td>0</td>
     </tr>
     <tr>
          <td>dLastModifiedDate</td>
          <td>wwCollectionModified</td>
          <td>NATIVE</td>
          <td>CALENDAR</td>
          <td>1</td>
          <td>1</td>
          <td>0</td>
          <td>0</td>
          <td>1</td>
          <td>0</td>
     </tr>
     <tr>
          <td>dCollectionOwner</td>
          <td>wwCollectionOwner</td>
          <td>NATIVE</td>
          <td>STRING</td>
          <td>1</td>
          <td>0</td>
          <td>0</td>
          <td>0</td>
          <td>1</td>
          <td>0</td>
     </tr>
     <tr>
          <td>dPromptForMetadata</td>
          <td>wwPromptForMetaData</td>
          <td>NATIVE</td>
          <td>LONG</td>
          <td>1</td>
          <td>0</td>
          <td>0</td>
          <td>0</td>
          <td>1</td>
          <td>0</td>
     </tr>
     <tr>
          <td>dCollectionCreator</td>
          <td>wwCollectionCreator</td>
          <td>NATIVE</td>
          <td>STRING</td>
          <td>1</td>
          <td>0</td>
          <td>0</td>
          <td>0</td>
          <td>1</td>
          <td>0</td>
     </tr>
     <tr>
          <td>dCollectionModifier</td>
          <td>wwCollectionModifier</td>
          <td>NATIVE</td>
          <td>STRING</td>
          <td>1</td>
          <td>0</td>
          <td>0</td>
          <td>0</td>
          <td>1</td>
          <td>0</td>
     </tr>
     <tr>
          <td>dDocName</td>
          <td>apTitleDocName</td>
          <td>NATIVE</td>
          <td>STRING</td>
          <td>1</td>
          <td>0</td>
          <td>0</td>
          <td>0</td>
          <td>1</td>
          <td>0</td>
     </tr>
     <tr>
          <td>dDocType</td>
          <td>apTitleDocType</td>
          <td>NATIVE</td>
          <td>STRING</td>
          <td>1</td>
          <td>0</td>
          <td>0</td>
          <td>1</td>
          <td>1</td>
          <td>0</td>
     </tr>
     <tr>
          <td>dDocTitle</td>
          <td>apTitleDocTitle</td>
          <td>NATIVE</td>
          <td>STRING</td>
          <td>1</td>
          <td>0</td>
          <td>0</td>
          <td>0</td>
          <td>1</td>
          <td>0</td>
     </tr>
     <tr>
          <td>dDocAuthor</td>
          <td>apTitleDocAuthor</td>
          <td>NATIVE</td>
          <td>STRING</td>
          <td>1</td>
          <td>0</td>
          <td>0</td>
          <td>0</td>
          <td>1</td>
          <td>0</td>
     </tr>
          <tr>
          <td>dRevLabel</td>
          <td>apTitleRevisionLabel</td>
          <td>NATIVE</td>
          <td>LONG</td>
          <td>1</td>
          <td>0</td>
          <td>0</td>
          <td>0</td>
          <td>1</td>
          <td>0</td>
     </tr>
          <tr>
          <td>dSecurityGroup</td>
          <td>apTitleSecurityGroup</td>
          <td>NATIVE</td>
          <td>STRING</td>
          <td>1</td>
          <td>0</td>
          <td>0</td>
          <td>1</td>
          <td>1</td>
          <td>0</td>
     </tr>
     <tr>
          <td>dDocAccount</td>
          <td>apTitleAccount</td>
          <td>NATIVE</td>
          <td>STRING</td>
          <td>0</td>
          <td>0</td>
          <td>0</td>
          <td>0</td>
          <td>1</td>
          <td>0</td>
     </tr>
     <tr>
          <td>dCreateDate</td>
          <td>apTitleCreateDate</td>
          <td>NATIVE</td>
          <td>CALENDAR</td>
          <td>1</td>
          <td>1</td>
          <td>0</td>
          <td>0</td>
          <td>1</td>
          <td>0</td>
     </tr>
     <tr>
          <td>dInDate</td>
          <td>apTitleInDate</td>
          <td>NATIVE</td>
          <td>CALENDAR</td>
          <td>1</td>
          <td>0</td>
          <td>0</td>
          <td>0</td>
          <td>1</td>
          <td>0</td>
     </tr>
     <tr>
          <td>dOutDate</td>
          <td>apTitleOutDate</td>
          <td>NATIVE</td>
          <td>CALENDAR</td>
          <td>1</td>
          <td>0</td>
          <td>0</td>
          <td>0</td>
          <td>1</td>
          <td>0</td>
     </tr>
     <tr>
          <td>dReleaseDate</td>
          <td>apTitleReleaseDate</td>
          <td>NATIVE</td>
          <td>CALENDAR</td>
          <td>1</td>
          <td>1</td>
          <td>0</td>
          <td>0</td>
          <td>1</td>
          <td>0</td>
     </tr>
</table>
<@end@>
</body>
</html>
The contents of c:/oracle/UCM/server/install/custom/Folders_g/resources/lang/en/vcr_folders_strings.idoc is below
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>
VCR_FOLDERS htmlIncludeOrString
</title>
</head>
<body>
<@wwCollectionID=Virtual Folder ID@>
<@wwCollectionGUID=Virtual Folder GUID@>
<@wwCollectionType=Virtual Folder Type@>
<@wwCollectionMark=Virtual Folder Mark@>
<@wwCollectionEnabled=Folder Enabled@>
<@wwCollectionPath=Virtual Folder Path@>
<@csVcrFoldersFolderArgMissing=Neither dCollectionID or dCollectionPath are included in the request.@>
</body>
</html>
Edited by: RSward on 28-Oct-2009 20:40
Again using the Component Wizard, selecting the component 'Folder_g' and resouce resources/vcr_folders_tables.idoc
I disabled it due to the error and then tried to enable it. I got this further error
"the table 'VCR_FOLDERS_ServiceHandlers' that is specified in the MergeRules table is not defined. Please either remove it form the MergeRules table or add to the ResourceDefinition table.
Does anyone know if a script exists to create the VCR_FOLDERS to upgrade the MergeRules table.

Rob,
I'm running into the exact same issue.
Did you get this resolved?
Regards,
Rob de Gouw

Customer info record

can any one tell me what the transaction for customer info record and how can we upload data into it

Hi Naresh,
actually the transaction is xd01.
abapprogramming.blogspot.com/2007/11/abap-bdc-sample-code-xd01.html - 119k
abapprogramming.blogspot.com/2007/11/abap-idocs-outlook.html - 106k
abapcode.blogspot.com/2007/05/step-by-step-guide-for-using-lsmw-to.html - 148k
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/59069d90-0201-0010-fd81-d5e11994d8b5
but you refer the above urls for additional ionformation ok.
for any issues reply me.
reward me points if it helps you.
regards
karthik.

Idoc-xi-file scenario. how to display file in html format

I am not sure whether this is a valid question.........but want to confirm as it was asked by somebody
In idoc-xi-file scenario....... how to display file in html format ??
Thanks in advance
Kumar

Hi Vijayakumar,
Thanks for your reply !! You mean to say I got to use XSLT mapping and also .htm and .html extension together to produce the html file ?? or it is sufficient to use any one of them to produce the html file ??
Regards
Kumar

How to use Idoc script in HTML

I know how to make my own fragments made with idoc. It works fine.
But i don't know how to write idoc without using fragments. When i write it inside html on the page, it just get outputs as it is, it doesn't get executed. What tag do i need to use? Can someone give a small example?

Hi,
<br>
Is the same as using fragments.
I use this code in a primary template
<div class="foto-doble">
<div>
          
          <br>
          <br>
<br>
<br>
<br>
Are you using external browser to view the page or "Preview"?

Error in creation of PurOrd IDoc

Hi All,
I have set up the output type for PO and created patner profiles and also add the message types ORDER and ORDCHG but when I save the PO and check the messages, I get an error: " No recipient found for message type ORDERS in the ALE Model ".
What could be the possible problem?
Highly appreciate any kind of help.
Thanks in advance,
Shweta
PS: <b><REMOVED BY MODERATOR></b>
Message was edited by:
Alvaro Tejada Galindo

Hi
Check the Partner Profile in WE20 correctly
also see the steps for it as per the doc
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
>>>> SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
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
RSEOUT00 Process all selected IDocs (EDI)
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.
Regards
Anji

XI idoc-jdbc scenario in details

Hi Experts,
Please provide me this scenario pn detail.
Cheers
Aman

Hi,
For IDOC to JDBC scenario:
Refer the below weblog for help:
/people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30 --> for jdbc receiver: file -JDBC
1) First you need to install the JDBC drivers on XI server refer the below link for installation process.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3867a582-0401-0010-6cbf-9644e49f1a10
2) You need to do the IDOC configuration at R3 as well as at Xi end:
Refer the below configuration steps:
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
Pre-requisites for Outbound IDoc from R/3 to PI:
Configurations required in R/3:
Maintain Logical System (SALE)
Define RFC Destination (SM59) which points to PI system
Maintain Port (WE21)
Maintain partner profile. (WE20):
Maintain Distribution Model (BD64):
Configuration required at Xi side:
Go to IDX2: load the DOC metadata.
3) For updating the table you need to write the stored procedure:
Refer the below link for stored prcedure.
JDBC:
Receiver JDBC scenario MS access - /people/sameer.shadab/blog/2005/10/24/connecting-to-ms-access-using-receiver-jdbc-adapter-without-dsn
Stored Procedures-
/people/siva.maranani/blog/2005/05/21/jdbc-stored-procedures
http://www.ics.com/support/docs/dx/1.5/tut6.html
/people/sriram.vasudevan3/blog/2005/02/14/calling-stored-procs-in-maxdb-using-sap-xi
http://www.ics.com/support/docs/dx/1.5/tut6.html
http://java.sun.com/docs/books/tutorial/jdbc/basics/sql.html
http://www.sqlteam.com/article/stored-procedures-an-overview
Thnx
Chirag
Reward points if it helps and close the threads.

Idoc Script strEqualsIgnoreCase make a wrong evaluation of logic values.

Hi again, this question starts like the last one i put in forum
Re: Cannot find metadata values in workflow queue
but it´s absolutely different.
I need some help customizing workflow action menues.
I´ve created a custom component with an html resource overwriting setup_workflow_action_popups.
Basically is the same code that original. There´s only a little change: in the Approve Link creation section I have put this code (is stupid i know)
<$exec rsAppendNewRow("PopupProps")$>
<$exec setValue("PopupProps", "label", lc("wwApprove"))$>
*<$if strEqualsIgnoreCase(dWfName,"Workflow1")$>*
*<$if strEqualsIgnoreCase(dWfStepName, "Step1")$>*
*<$exec setValue("PopupProps", "function", "javascript:alert('dWfStepName seems to be Step1 and is <$dWfStepName$>');document.Approve_<$dID$>.submit();")$>*
*<$else$>*
*<$exec setValue("PopupProps", "function", "javascript:alert('dWfStepName seems NOT to be Step1 and is <$dWfStepName$>');document.Approve_<$dID$>.submit();")$>*
*<$endif$>*
*<$else$>*
*<$exec setValue("PopupProps", "function", "javascript:alert('<$dWfStepName$>');document.Approve_<$dID$>.submit();")$>*
*<$endif$>*
<$exec setValue("PopupProps", "ifClause", "AllowReview")$>
<$exec setValue("PopupProps", "class", "workflow")$>
<$exec setValue("PopupProps", "id", "workflowApprove")$>
(I have built the component though i think is not necessary since i´m only changing HTML,I restarted Content Server even i think it is not necessary)
I´m watching results in My Workflow Assignments and in Active Workflows.
I have a big trouble. It seems "if" clause doesnt work in Idoc.
I´m getting an alert with this message
dWfStepName seems NOT to be Step1 and is Step1
This means that Step1 is not the same that Step1
So, <$if strEqualsIgnoreCase(dWfStepName, "Step1")$> is not working properly
I tried next other forms with the same result
<$if strEqualsIgnoreCase(dWfStepName, "Step1")==true$>
<$if strEqualsIgnoreCase(dWfStepName, "Step1")==TRUE$>
<$if strEqualsIgnoreCase(dWfStepName, "Step1")==0$>
<$if isTrue(strEqualsIgnoreCase(dWfStepName, "Step1"))$>
I´m really taken aback. i don´t know where is the problem.
Any clue?
Thank you
Thank you very much

In reality of course this should work. Try a simple hcsp page and you will see that this works fine. There must be an issue that you are not comparing what you think. Could be scope or whitespace. to eliminate whitespace change code to...
<$if strEqualsIgnoreCase(strTrimWs(dWfStepName), "Step1")$>
If this doesnt work can you use
<$trace("#all", "#console")$>
to dump everything to the server output. You can manage the server output from Administration > System Audit Information >
then load the page again and patse the trace output here.

Unable to generate IDOCS using IDOC_INPUT_ORDERS Function Module

Hi,
I have written a program to post IDOCS using function module IDOC_INPUT_ORDERS .
In the debugging mode,I found that after the call of this function-module,sy-subrc is set to zero which means that this function-module is getting successfully executed.
But when I go to WE02 transaction code , i do not see any IDOCS being generated for IDOC Type ORDERS05 .
Please could someone help me out with this .
Regards,
Sushanth H.S.

hi
check your ALE configuration:
go thru the links:
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
reward points for useful ans
Regards
Aarti

SAP R/3 Mapping with EDI IDOC's 846 and 852 (Outbound)

Hi:
How are the following EDI IDOC Types mapped in SAP - R/3?
1. Inventory Inquiry / Advice (846)
2. Product Activity Data (852)
What is the basic type, message type, idoc type that has to be used
in both the cases - outbound based ones.
This is a consumer products industry and not a retail industry. This
is a hypothetical scenario where the end customer would like to see
the price and the stock from all the plants and then place an order
(846); and also see what is being planned in aparticaular plant for
a planning period (852). The cycle countings are carried out based
on the type of product in question and SAP-R/3 has been set up for
this. What is the trigger point for the enitre activitiy to take
place. Any valuable suggestions or guidelines are most welcome.
Regards
Rohit

Check this link and see if it leads you somewhere.
http://sap.ittoolbox.com/groups/technical-functional/sap-interfaces/information-on-the-edi-idoc-types-1739410
http://www.jt77.com/CRM/related-discussion-1111.html
Regards,
Ravi Kanth Talagana

How to create a simple idoc in practice? can you provide an example?

how to create a simple idoc in practice? can you provide an example with full source code?

Try with the follwoing steps
Sending System(Outbound ALE Process)
Tcode SALE ³ for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ¡V Create Model View
Tcode BD82 ¡V Generate partner Profiles & Create Ports
Tcode BD64 ¡V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ³ for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ¡V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ¡V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 ¡V Send Material Data
Tcode WE05 ¡V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Thanks & regards
Sreenivas
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Take a look at this guide.
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
http://www.sappro.com/downloads/OneClientDistribution.pdf
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
Create The Extension Segment
Transaction: WE31
The first step in extending an IDoc is to create the new segments that will go into that IDoc. There are some rules that you need to follow when creating the segments:
- The name of each segment type must start with Z1
- For each field in the segment you need to define a field name and a
data element.
- The data element for the segment structure must be of data type CHAR.
How to create new segments:
Run the segment maintenance transaction WE31.
Type your new segment name, and click on Create.
Define the fields of your segment:
Field name
Data Element for the field (from the ABAP dictionary).
Do not change the Export length!
Save the segment
Run Segment -->Check to check the segment for consistency.
Release the segment for transport. Select Edit -->Set Release. Note that the Release column now has a check mark.
Create the Extension IDoc Type
Transaction: WE30
After you create the segments to be added to the extension type, you can create the extension type itself. Execute transaction WE30, enter the extension name, select Extension type, and click Create. You now have three options:
Create new type: Does not refer to other extension types
Create copy: Copies info from an extension type that already exists
Create successor: Extends an extension type from a previous release
of R/3. You can only have one version of an extension type for
each release.
Enter the Basic IDoc type that this extension type will extend.
The screen now shows the structure of the IDoc type you used as
a reference.
Position the cursor on one of the segments and click Create. This will insert an extension segment as a child of the selected segment.
NOTE: A segment cannot appear more than once in an IDoc type! You must control the use of duplicate segments with the segment attributes (the next screen).
The segment attribute screen appears. Enter the information and save.
Extension segments should not be mandatory (for future upgrades), and will need to have minimum and maximum number of instances defined. This answers the question, for each instance of the parent segment, how many instances of the child segment may we have?
You can press the Segment Editor pushbutton to view or change the segment definition.
Create the new Message Type
You can only use an extension IDoc type by assigning it to a message type. You can create a new message type for this.
First the message type itself needs to be created.
Transaction: WE81
Create a new entry and save. Use SAP established customer naming conventions (good form is to start with a Z and retain the rest of the related SAP message type, so, for example, MATMAS becomes ZMATMAS).
After creating the message type, associate it with the corresponding Basic IDoc Type and Extension Type. This relationship is used when IDocs are sent to or received from a partner to determine what segments are valid and what the hierarchy for those segments is.
Transaction: WE82
Create a new entry and enter the Message type, Basic IDoc type, Extension type, and Release, and save your data. Note: the release assignment is not valid for prior SAP releases.
One message type can be associated with many basic IDoc types; however, you need a one-to-one relationship for distribution via ALE.
regards,
srinivas
*reward for useful answers*</b>

IDoc to JDBC and JDBC to IDoc Scenario

Dear All,
I am working on IDoc to JDBC and JDBC to IDoc Scenario.
I have to send Idoc from SAP to Non SAP system(.NET application) i almost configured in XI but still i don't know when my INTEGRATION will INVOKE how my data will proceed from IDOC to Oracle database(Through JDBC) and in case of revese how and when Data flow will start.
Does anyone have completed STEP by STEP scenario document for this?
How my Idoc will sent to XI?
How XI will pick up data from IDoc?
How XI will Convert data to JDBC and UPDATE in Oracle Database?
And i reverse case(JDBC to IDoc) when my INTEGRATION will INVOKE?
Where and When i can watch my process and data?
How can i test the whole integration?
I AM GETTING ERROR WHILE TESTING CONFIGURATION IN Integration Directory "Error while refreshing the XI runtime cache" and when i check this in SXI_CACHE it gives me error
"Unable to refresh cache "NO_BUSINESS_SYSTEM"
"Error during last refresh to cache"LCR_GET_OWN_BUSINESS_SYSTEM - NO_BUSINESS_SYSTEM"
Please solve all the above problems i will reward u points
thanks,
RP

Hi,
While we working on IDOC to JDBC interface..
We have to deploy JDBC Drivers?
Go through this links,
/people/varadharajan.krishnasamy/blog/2007/02/27/configuring-jdbc-connector-service-to-perform-database-lookups
http://searchsap.techtarget.com/tip/0,289483,sid21_gci1246926,00.html
To install JDBC driver follow the how to guide.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how%20to%20install%20and%20configure%20external%20drivers%20for%20jdbc%20and%20jms%20adapters.pdf
Configuration of JDBC Adapter for SQL Server
JDBC Driver = com.microsoft.jdbc.sqlserver.SQLServerDriver
Connection = jdbc:microsoft:sqlserver://hostname:<port>;DatabaseName=<DBName>
UserID and Password.
If the connection is not working find the correct port number.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40b92770-db81-2a10-8e91-f747188d8033
JDBC- X I - R/3 Scenario
/people/bhavesh.kantilal/blog/2006/07/03/jdbc-receiver-adapter--synchronous-select-150-step-by-step
/people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30
Please check the driver path as mentioned below.
JDBC Driver : sun.jdbc.odbc.JdbcOdbcDriver
Connection:jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)};DBQ=//location of DB table.mdb;
No JDBC driver required.
Receiver JDBC scenario MS access - /people/sameer.shadab/blog/2005/10/24/connecting-to-ms-access-using-receiver-jdbc-adapter-without-dsn
follow this thread
Re: Problem when connecting to MS Access through JDBC Adapter.
SAP Note 850116 has details
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
Configuring the Sender JDBC Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/1d/756b3c0d592c7fe10000000a11405a/content.htm
Configuring the Receiver JDBC Adapter
http://help.sap.com/saphelp_nw2004s/helpdata/en/b0/676b3c255b1475e10000000a114084/content.htm
Idoc Reveiver adapter..
http://help.sap.com/saphelp_erp2004/helpdata/en/b9/c5b13bbeb0cb37e10000000a11402f/content.htm
Thanks,
Satya Kumar
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
Edited by: SATYA KUMAR AKKARABOYANA on May 8, 2008 5:51 PM

Idoc to HTML

Similar Messages

Maybe you are looking for