BW complete documentation

hi to all
i am new to BW 3.5. so i want complete reference e-book of BW 3.5. pls help me to find total information for the above.

Hi Priyadarshini,
Here are some links which will give you information from basics to detailed topics .
Architectural Overview
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/800a7bd4-7897-2910-c6b2-9ee791e9913c
BI Data Modeling
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/6ce7b0a4-0b01-0010-52ac-a6e813c35a84
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3668618d-0c01-0010-1ab5-aa75c3a4dfc2
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/2f5aa43f-0c01-0010-a990-9641d3d4eef7
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/dc43c445-0d01-0010-23a1-ca348ff5f975
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6090a621-c170-2910-c1ab-d9203321ee19
Frontend Design
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/58fd9183-0e01-0010-f183-fdc9019f77ab
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/bda556e9-0c01-0010-83b0-d519d6deb9e9
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ad214fe9-0c01-0010-4291-a629e5ba5f90
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/07c361e9-0c01-0010-90b5-a7e315ea4875
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ce496e17-0301-0010-e0b4-b8ca8b4588ac
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/efdbd593-0e01-0010-4eb1-a09ffedd550a
Go through these PDF's.
Enterprise Dataware Housing.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/67efb9bb-0601-0010-f7a2-b582e94bcf8a
Enterprise Reporting.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/0901c9bb-0601-0010-49ab-c1770c527673
http://help.sap.com/saphelp_nw04s/helpdata/en/a4/1be541f321c717e10000000a155106/content.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm
https://www.sdn.sap.com/irj/sdn/bi
Check these presentaions:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5c46376d-0601-0010-83bf-c4f5f140e3d6
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5ee3725b-0401-0010-e381-ac323362ce91
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5c46376d-0601-0010-83bf-c4f5f140e3d6
http://csc-studentweb.lrc.edu/swp/Berg/BB_index_main.htm
http://csc-studentweb.lrc.edu/swp/Berg/articles/NW2004s_what_is_new.ppt
BI 7.0 reporting features
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/910aa7a7-0b01-0010-97a5-f28be23697d3
http://help.sap.com/saphelp_nw2004s/helpdata/en/b2/e50138fede083de10000009b38f8cf/frameset.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/4487dd91-0b01-0010-eba1-bcd6419
/people/michael.eacrett/blog/2006/06/07/whats-new-in-sap-netweaver-702004s--an-introduction-to-the-functionality-deltas-and-major-changes
http://searchsap.techtarget.com/cgi-bin/rd.pl/ftID-1121728-ctID-1064004?//expert/KnowledgebaseAnswer/0,289625,sid21_gci1064004,00.html
http://help.sap.com/saphelp_nw04s/helpdata/en/9d/24ff4009b8f223e10000000a155106/content.htm
check if this helps
Multi-Dimensional Modeling with SAP NetWeaver BI
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/6ce7b0a4-0b01-0010-52ac-a6e813c35a84
Modeling the Data Warehouse Layer with BI
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3668618d-0c01-0010-1ab5-aa75c3a4dfc2
Frontend Design Guidelines - SAP BI in SAP NetWeaver 2004s
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/58fd9183-0e01-0010-f183-fdc9019f77ab
Enterprise Reporting, Query, and Analysis - Developers Guide
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/0901c9bb-0601-0010-49ab-c1770c527673
check
https://www.sdn.sap.com/irj/sdn/developerareas/bi
John Wiley & Sons - SAP NetWeaver For Dummies:
0201703661 SAP BW: A Step by Step Guide for BW 2.0
SAP Business Information Warehouse on the AS/400 System
Code:http://www.redbooks.ibm.com/redbooks/pdfs/sg245200.pdf
Code:http://www.best.tuke.sk/~ejo/books/SAP%20Enterprise%20Modelling%20-%20Consultants%20Handbook.pdf
https://www.sdn.sap.com/irj/sdn/bi
http://aiokeh.wdf.sap.corp:50000/SAPIKS2/contentShow.sap?TMP_IWB_TASK=DISPLAY&_CLASS=IWB_EXTHLP&_LOIO=42CA6A69992F6BB1E10000000A1553F6&_SLOIO=E3E60138FEDE083DE10000009B38F8CF&LANGUAGE=EN&RELEASE=700&_SCLASS=IWB_STRUCT
http://help.sap.com/saphelp_nw2004s/helpdata/en/52/a21f407b402402e10000000a1550b0/frameset.htm
https://websmp201.sap-ag.de/instguidesNW2004s
/people/gilad.weinbach2/blog/2007/02/23/a-beginners-guide-to-your-first-bi-model-in-nw2004s
How to Papers
https://www.sdn.sap.com/irj/sdn/docs?rid=/webcontent/uuid/93eaff2d-0a01-0010-d7b4-84ac0438dacc [original link is broken] [original link is broken]
Check links..
http://help.sap.com/saphelp_nw04s/helpdata/en/a4/1be541f321c717e10000000a155106/content.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm
https://www.sdn.sap.com/irj/sdn/bi
Check these presentaions:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5c46376d-0601-0010-83bf-c4f5f140e3d6
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5ee3725b-0401-0010-e381-ac323362ce91
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5c46376d-0601-0010-83bf-c4f5f140e3d6
http://csc-studentweb.lrc.edu/swp/Berg/BB_index_main.htm
http://csc-studentweb.lrc.edu/swp/Berg/articles/NW2004s_what_is_new.ppt
https://www.sdn.sap.com/irj/sdn/developerareas/bi
Frequently Asked Questions in SAP NW 7.0 - Enterprise Data Warehousing, Reporting, Query & Analysis and Business Planning [original link is broken]
https://www.sdn.sap.com/irj/sdn/docs?rid=/webcontent/uuid/93eaff2d-0a01-0010-d7b4-84ac0438dacc [original link is broken] [original link is broken]
You could get some SAP Documents here.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5ee3725b-0401-0010-e381-ac323362ce91
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5c46376d-0601-0010-83bf-c4f5f140e3d6
These two pdf files has all almost all info about BI2004s.
Go through this Link for BI 7.0 Documents.
https://websmp101.sap-ag.de/bi
and Click on BI StandardPresentations link.
New Features in BI:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/910aa7a7-0b01-0010-97a5-f28be23697d3
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/4487dd91-0b01-0010-eba1-bcd6419
/people/michael.eacrett/blog/2006/06/07/whats-new-in-sap-netweaver-702004s--an-introduction-to-the-functionality-deltas-and-major-changes
BI 7.0 reporting features
http://searchsap.techtarget.com/cgi-bin/rd.pl/ftID-1121728-ctID-1064004?//expert/KnowledgebaseAnswer/0,289625,sid21_gci1064004,00.html
Search SDN by giving topic name you find more related information
Assign points if helpful.
Regards,
Kunal Gandhi

Similar Messages

Complete documentation of the richtext editor

Is there a way to find out the complete documentation on how to customize the richtext editor? In my case, I don't have an access to the administrator side of Coldfusion. Thanks.

I did not understand the last line in your reply.
"It is the launch.exe (in the form of uninst.exe) which invokes setup.exe."
You mean to say to uninstall olite launch.exe is used to invoke setup.exe, may be with a command line parameter.

Complete documentation of command lines parameters of Olite programs

Where can one find the complete documentation of the command line parameters supported by following olite programs?
1) update.exe
2) dmagent.exe
3) setup.exe
4) olver.exe
5) olSyncAgent.exe
6) olmig.exe
7) FileServer.exe
8) autosync.exe
Can any one explain me the purpose of the launch.exe?

I did not understand the last line in your reply.
"It is the launch.exe (in the form of uninst.exe) which invokes setup.exe."
You mean to say to uninstall olite launch.exe is used to invoke setup.exe, may be with a command line parameter.

XML Forms Builder complete Documentation and more

Hi,
I have several questions to the XML-Forms-Builder (XML-FB):
1)
I am searching for a really complete documentation of the XML-FB. I know the "how to create xml forms - PDF", the "help.sap.com", this forum,...., but i don't find one complete documentation. For example i miss the description of really all controls AND whose properties.
2)
Can I await any changing/enhancement between NW 2004 SP16 (my active Release) and NW 2004s SPx - with focus to the XML-FB?
3)
Is it possible to create forms witch allows <u>the author</u> to choose the placement of controls - for example images in the left, right, middle of the page - maybe via select/assign the corresponding form (-> maybe via using control-selector)? This means more individual flexibility for the author.
I am searching for a solution without programming a proprietary solution, only customizing !
okay, that's all, up to now
Thanks for your patience
Hermann

Hi Herrmann,
1.) There is no. Some features have been added more or less silently within the last year, but a central doc hasn't been published.
2.) All I know is: Not much. Maybe the Forms Builder developer at SAP reads this and could throw a somewhat more detailed answer.
3.) We have developed this as a small part of easyWCM; when creating the XML form, you can define not only 1 ShowForm, but different; the author then can choose which form to use. We provide such pre-defined forms within the BP.
Hope it helps
Detlev
PS: Please consider rewarding points for helpful answers on SDN. Thanks in advance!

BI complete documentation

Dear all,
I am new to BI/BW - can anyone explain the complete process of BI/BW with example and documentation for me to understand the configuration ?
Regards,
M.M

Hi,
Check these links.
Re: STEPS REQUIRED TO EXTRACT DATA FROM FLAT FILE TO BI 7.0
http://help.sap.com/saphelp_nw04/helpdata/en/33/f3843b0af3de0ee10000000a114084/frameset.htm
Re: STEPS REQUIRED TO EXTRACT DATA FROM FLAT FILE TO BI 7.0
http://help.sap.com/saphelp_nw04/helpdata/en/33/f3843b0af3de0ee10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/a4/1be541f321c717e10000000a155106/content.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/52/a21f407b402402e10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm
https://www.sdn.sap.com/irj/sdn/bi
Certification & Syllabus
Check the deatils for the certification at the below link
https://websmp105.sap-ag.de/~sapidp/011000358700002412512003
check out this link for some more documentation available for the BI Certification
https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=bi+certification&adv=true&adv_sdn_all_sdn_author_name=&sortby=cm_rnd_rankvalue
https://www.sdn.sap.com/irj/sdn/developerareas/bi
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/67efb9bb-0601-0010-f7a2-b582e94bcf8a
BI7.0(sap netweaver 2004s) pls check the below links
http://help.sap.com/saphelp_nw2004s/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm
NW2004s help:
http://help.sap.com/saphelp_nw2004s/helpdata/en/index.htm -> SELECT key capability
http://help.sap.com/saphelp_nw2004s/helpdata/en/30/c4461ff69d5a438f1286e344b545fa/frameset.htm then select-> information integration -> business intelligence.
For Modeling in Netweaver BI:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/6ce7b0a4-0b01-0010-52ac-a6e813c35a84
To know the New Features in BI:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/4487dd91-0b01-0010-eba1-bcd64196ec6b
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/910aa7a7-0b01-0010-97a5-f28be23697d3
Also check these links as well:
https://www.sdn.sap.com/irj/sdn/developerareas/bi?rid=/webcontent/uuid/e78a5148-0701-0010-7da9-a6c721c6112e [original link is broken] [original link is broken]
BI Data Modeling and Frontend Design [original link is broken]
For Netweaver Security & Authorizations:
http://help.sap.com/saphelp_nw2004s/helpdata/en/8c/2ec59131d7f84ea514a67d628925a9/frameset.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/39f29890-0201-0010-1197-f0ed3a0d279f
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/fda2a990-0201-0010-5497-b81b1556df24
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/adeac294-0501-0010-5a97-9ac5d562b1be
https://www.sdn.sap.com/irj/sdn/developerareas/bi?rid=/webcontent/uuid/e78a5148-0701-0010-7da9-a6c721c6112e [original link is broken] [original link is broken]
http://help.sap.com/bp_biv170/
and more starting from here:
https://www.sdn.sap.com/irj/sdn/developerareas/bi
In this one - check out slides 28-34
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/4487dd91-0b01-0010-eba1-bcd64196ec6b
Check this link to get PDF doc on SAP BI
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5ee3725b-0401-0010-e381-ac323362ce91
Here is a powerpoint overview with illustrations of the differences between NW2004s (BI 7.0) and BW 3.5.x
http://csc-studentweb.lrc.edu/swp/Berg/Articles/NW2004s_what_is_new.ppt
check the presentaion
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5c46376d-0601-0010-83bf-c4f5f140e3d6
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5ee3725b-0401-0010-e381-ac323362ce91
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5c46376d-0601-0010-83bf-c4f5f140e3d6
http://csc-studentweb.lrc.edu/swp/Berg/BB_index_main.htm
http://csc-studentweb.lrc.edu/swp/Berg/articles/NW2004s_what_is_new.ppt
Web Blogs & Threads in SDN
/message/502929#502929 [original link is broken]
/people/sap.user72/blog/2006/01/27/sap-netweaver-bi-versus-sap-bw-the-sequel
New Features in BI:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/910aa7a7-0b01-0010-97a5-f28be23697d3
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/4487dd91-0b01-0010-eba1-bcd6419
/people/michael.eacrett/blog/2006/06/07/whats-new-in-sap-netweaver-702004s--an-introduction-to-the-functionality-deltas-and-major-changes
BI 7.0 reporting features
http://searchsap.techtarget.com/cgi-bin/rd.pl/ftID-1121728-ctID-1064004?//expert/KnowledgebaseAnswer/0,289625,sid21_gci1064004,00.html
http://help.sap.com/saphelp_nw04s/helpdata/en/9d/24ff4009b8f223e10000000a155106/content.htm
Some of the How to Papers available at these links
https://www.sdn.sap.com/irj/sdn/docs?rid=/webcontent/uuid/93eaff2d-0a01-0010-d7b4-84ac0438dacc [original link is broken]
https://www.sdn.sap.com/irj/sdn/docs?rid=/webcontent/uuid/9280fb2d-0a01-0010-0f80-f33ab5c1606d [original link is broken]
Frequently Asked Questions in SAP NW 7.0 - Enterprise Data Warehousing, Reporting, Query & Analysis and Business Planning [original link is broken]
Thanks & regards,
Sunil

Regarding ALE/Idocs PDFs & complete Documentation & Step by Step Procedure

Hi Gurus,
Iam working on Netweaver XI and i need some PDF's on ALE/Idocs.
1. How to create and send a custom idoc?
2. Serialization of idocs?
3. Archiving of idocs?
4. Idoc Acknowledgement?
5. How to send multiple Idocs at a time?
6. Idoc Sheduling?
7. Idoc bundling and Packaging?
8. How to Debug a Idoc?
For the above questions i need complete procedure and Pdf's upon these and send me some FAQ's on them.can any one send me the details plz very urgent.plz send Especially pdf's. My id is ajaykodali22 at the rate of gmail.com
Thanks & Regards,
ajay kodali.

Hi,
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,
Shiva.

Complete Documentation on SLIS

Hi Experts,
I know that SLIS is a type-pool, used in ALV reports. Could you let me know is there any documentation available on 'SLIS'?
Thanks a ton.

Hi Raj,
SLIS: is a type group (pool of predefined data types)
rest of them are all the data types in slis
1) SLIS_T_FIELDCAT_ALV is used to build a fieldcatalog which will be list of fields to be displayed in alv.
2) is the structure
3) to build events table in alvs
4) str for the above
5) is useful in usercommand
SLIS_T_FIELDCAT_ALV --> field catalog internal table
SLIS_FIELDCAT_ALV --> structure of field catlog
SLIS_T_EVENT ---> capture the events inside the ALV
SLIS_ALV_EVENT ---> event structure
SLIS-SELFIELD -
> will capture the selected field in a row.
for sample programs..
chk this link.
http://www.sapdevelopment.co.uk/reporting/alv/alvgrid.htm
A field catalog is prepared using the internal table (I_FIELDCAT) of type SLIS_T_FIELDCAT_ALV.
A field catalog need not be built-up and passed explicitly only under the following conditions:
1. The internal table to be output has the same structure as a Data Dictionary structure which is referred to in the internal table declaration using LIKE or INCLUDE STRUCTURE. In this case the attributes of the different fields is taken directly from the table and the attributes (key fields, length, texts etc) need to state explicitly.
2. all fields in this structure are to be output
3. The structure name is passed to ALV in the parameter I_STRUCTURE_NAME of the function module REUSE_ALV_LIST_DISPLAY.
All the values entered in the catalog is specific to the particular field whose name is entered in the fieldname FIELDNAME of the fieldcat structure. The name of the table is also entered in the corr. Fieldname TABNAME of the structure.
The different possible attributes are:
Row_pos (row position): Only relevant if the list output is to be multi-line (two or three lines) by default. So, this attribute can be used maintain certain level of alignment in the output.
Value set: 0, 1 3
Col_pos (column position): This parameter is relevant when the fields in the output are to be different from the sequence of the fields in the internal table used for display. The parameter specifies the relative column position of the field in the list output. The column order can be changed interactively by the user. If this parameter is initial for all field catalog entries, columns appear in the internal table field sequence.
Value set: 0, 1 60
Fieldname (field name): This is the name of the internal table field for which the parameters are passed in the catalog.
Value set: internal output table field name (required parameter)
Tabname (internal output table): Name of the internal output table that contains the field FIELDCAT-FIELDNAME above.
Value set: SPACE, internal output table name.
Ref_fieldname (reference field name): Name of the Data Dictionary field referred to. This parameter is only used when the internal output table field described by the current field catalog entry has a reference to the Data Dictionary (not a program field), and the field name in the internal output table is different from the name of the field in the Data Dictionary. If the field names are identical, naming the Data Dictionary structure or table in the FIELDCAT-REF_TABNAME parameter is sufficient.
Value set: SPACE, Data Dictionary field name.
Ref_tabname (reference table/structure field name): Structure or table name of the referred Data Dictionary field. This parameter is only used when the internal output table field described by the current field catalog entry has a Data Dictionary reference (not a program field).
Value set: SPACE, name of a Data Dictionary structure or table
Link to currency unit
Cfieldname (currency unit field name): This is used for currency fields that have a reference to any unit field. This is only relevant for amount columns with associated unit. This parameter contains the Name of the internal output table field containing the currency unit associated with the amount field FIELDCAT-FIELDNAME. The field in FIELDCAT-CFIELDNAME must have its own field catalog entry.
Value set: SPACE, output table field name
Ctabname (internal currency unit field output table): Name of the internal output table containing the FIELDCAT-CFIELDNAME field.
Value set: SPACE, output table field name.
Link to measurement unit
Qfieldname (measurement unit field name): Only relevant for quantity columns with unit link. Name of the internal output table field containing the measurement unit associated with the quantity field FIELDCAT-FIELDNAME. The field in FIELDCAT-QFIELDNAME must have its own field catalog entry.
Value set: SPACE, output table field name.
Qtabname (internal measurement unit field output table): Name of the internal output table containing the FIELDCAT-QFIELDNAME field.
Value set: SPACE, output table field name.
Outputlen (column width): This parameter is used if the desired output length for a field is desired to be different from the internal output table field. For fields with a Data Dictionary link this parameter can be left initial. For fields without a Data Dictionary link (program field) the parameter must be given the value of the desired field list output length (column width).
Initial = column width is the output length of the referred Data Dictionary field (domain).
N = column width is n characters.
Value set: 0 (initial), n.
Key (key column): By default, the system makes some fields in the output as key fields, provided the fields are key fields in their referencing table. Using this parameter, fields other than key fields of the referencing table can be made key field. This parameter is most important if the output needs to contain some field which are not scrollable or cannot be hidden.
If the internal output table contains fields that are key fields from different tables, then all those fields in the report output becomes unscrollable and cannot be hidden. So, the fields in the output internal table should not be referenced from tables in which they are key fields. Instead, they should be referenced to the tables in which they are not key fields, incase they are not desired as key field in the output.
'X' = key field (key field output in color) and Key fields can not be interactively hidden. Parameter FIELDCAT-NO_OUT must be left initial.
Value set: SPACE, 'X'.
Key_sel (hideable key column): This parameter is only relevant for the fields which are made key fields using FIELDCAT-KEY = 'X'. Using this parameter the Key field can be hidden interactively.
The key column sequence cannot be changed interactively by the user. The output is controlled by the FIELDCAT-NO_OUT parameter analogously to non-key fields.
Value set: SPACE, 'X'.
No_out (field in field list): This parameter is used to remove certain fields from the output during initial display. The user can however interactively choose the field for output from the field list in the display variant.
'X' = field is not displayed in the current list.
Value set: SPACE, 'X'.
Tech (technical field): This parameter is used to make certain field display only in the field catalog. The fields with this parameter set cannot be output in the list nor can they be displayed interactively from the catalog.
'X' = technical field.
Value set: SPACE, 'X'.
Emphasize (highlight columns in color): As name suggests, this field parameter is used to highlight certain field with chosen colors.
Value set: SPACE, 'X' or 'Cxyz' (x:'1'-'9'; y,z: '0'=off ,'1'=on).
'X' = column is colored with the default column highlight color.
'Cxyz' = column is colored with a coded color:
- C: Color (coding must begin with C)
- X: color number
- Y: bold
- Z: inverse
Hotspot (column as hotspot): This parameter is used to make certain field appear as hotspot i.e. a hand is displayed if the cursor is positioned on the field value. Single click on such fields cause the PICK OR F2 events to happen.
Value set: SPACE, 'X'.
'X' = column cells are output as hotspots.
Fix_column (fix column): This parameter is used to fix certain columns in the output. All columns to be fixed must have this flag, starting from the left. If a column without this flag is output, only the columns to the left of this column are fixed. The user can change the column fixing interactively.
Value set: SPACE, 'X'.
'X' = column fixed (does not scroll horizontally).
Do_sum (sum over column): the user can also call this function interactively.
Value set: SPACE, 'X'.
'X' = a sum is calculated over this internal output table field.
No_sum (sums forbidden): No sum can be calculated over this field, although the data type of the field would allow summing.
Value set: SPACE, 'X'.
Icon: The parameter displays certain column contents as icons. The internal output table column contents must be valid icon strings.
Value set: SPACE, 'X'.
'X' = column contents to be output as an icon.
Symbol: The internal output table column must be a valid symbol character.
Value set: SPACE, 'X'
'X' = column contents are to be output as a symbol.
Just (justification): This parameter is used for alignment of the contents of the output table. This is only relevant for CHAR or NUMC fields in the output internal table. The justification of the column header always follows the justification of the columns. Independent justification of the column header is not possible.
Value set: SPACE, 'R', 'L', and C.
' ' = Default justification for this data type
'R' = right-justified output
'L' = left-justified output
'C' = centered output.
Lzero (leading zeros): By default ALV outputs NUMC fields right-justified without leading zeros. Using this parameter only the NUMC fields can be displayed with leading zeroes.
Value set: SPACE, 'X'.
'X' = output with leading zeros.
No_sign (no +/- sign): This parameter is used to suppress the signs of the output fields. It is only relevant for the value fields.
Value set: SPACE, 'X'.
'X' = value output without +/ sign.
No_zero (suppress zeros): Only relevant for value fields.
Value set: SPACE, 'X'.
'X' = suppress zeros.
Edit_mask (field formatting): To apply the report output formatting options same as in the WRITE statement in report writing.
Value set: SPACE, template.
2. Slis_ev_reprep_sel_modify TYPE slis_formname VALUE 'REPREP_SEL_MODIFY'.
RS_SELFIELD-TABINDEX contains the header table index for which the item entries are to be put in the global item output table (T_OUTTAB_SLAVE). The Callback is only called if ALV has no items for a header that is to be expanded.
RFLG_ALL is passed with 'X' if the user shows all items. The application must ensure that entries are not repeated in the item table.
RS_SELFIELD is initial in this case.
3. Slis_ev_caller_exit_at_start TYPE slis_formname VALUE 'CALLER_EXIT'.
Is called at the beginning of the function module to make special settings. It is not usually used.
4. Slis_ev_user_command TYPE slis_formname VALUE 'USER_COMMAND'.
As this is a frequently-used Callback event, the form routine can also be passed directly in the interface by passing the user command in the IMPORTING parameter I_CALLBACK_USER_COMMAND.
5. Slis_ev_top_of_page TYPE slis_formname VALUE 'TOP_OF_PAGE'.
Equivalent to the list processing TOP-OF-PAGE event.
6. Slis_ev_top_of_coverpage TYPE slis_formname VALUE 'TOP_OF_COVERPAGE'.
The selection information and list status are output together (if they exist) on a separate page by default
7. Slis_ev_end_of_coverpage TYPE slis_formname VALUE 'END_OF_COVERPAGE'.
Analogously to TOP_OF_COVERPAGE the user can add other information
to the information output by ALV (selection information, list status) at this event.
8. Slis_ev_foreign_top_of_page TYPE slis_formname VALUE FOREIGN_TOP_OF_PAGE'.
The Top-of-page event is always processed in ALV and is only passed to the caller via the Callback mechanism. This is still the case if the caller, e.g. by a user action, processes a branch list which was not formatted by ALV (e.g. a popup with additional information about the list record selected and displayed by ALV).
In this case, top-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller. The event top-of-page still occurs in ALV. When ALV notices a top-of-page which was not caused by an ALV output, the form routine in FOREIGN_TOP_OF_PAGE is called.
9. Slis_ev_foreign_end_of_page TYPE slis_formname VALUE 'FOREIGN_END_OF_PAGE'.
The event end-of-page is always processed in ALV and only passed to the caller via callback. This is still the case, e.g. when the caller processes a details list which was not formatted by ALV (e.g. a popup with further information about selected list records which were displayed by ALV).
In this case, end-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller. The event end-of-page still occurs in ALV. When ALV notices an end-of-page that was not caused by an ALV output, the form routine in FOREIGN_END_OF_PAGE is called.
10. Slis_ev_pf_status_set TYPE slis_formname VALUE 'PF_STATUS_SET'.
If a user list status is to be set, it must be done in the form routine assigned to this event. The ALV function codes, which must not be active, are in the Parameter RT_EXTAB. This table must be passed with the SET PF-STATUS command (with inactive user function codes as well, if necessary).
The STANDARD status of the function group SALV should be used as a template for a user-specific status. As this is a frequently used Callback event, its form routine can also be passed directly in the interface in the IMPORTING parameter I_CALLBACK_PF_STATUS_SET.
11. Slis_ev_list_modify TYPE slis_formname VALUE 'LIST_MODIFY'.
LIST_MODIFY USING R_TABNAME TYPE SLIS_TABNAME
R_INDEX LIKE SY-TABIX
R_INDEX_ITEM LIKE SY-TABIX
R_INDEX_SUM LIKE SY-TABIX.
12. Slis_ev_top_of_list TYPE slis_formname VALUE 'TOP_OF_LIST'.
Information output at the start of the list
13. Slis_ev_end_of_page TYPE slis_formname VALUE 'END_OF_PAGE'.
Information output at the end of a page. This is only called for printing.
14. Slis_ev_end_of_list TYPE slis_formname VALUE 'END_OF_LIST'.
Information output at the end of the list
15. Slis_ev_after_line_output TYPE slis_formname VALUE 'AFTER_LINE_OUTPUT'.
Output information after each output line. Should only be used in justified cases because it costs a lot of performance.
16. Slis_ev_before_line_output TYPE slis_formname VALUE 'BEFORE_LINE_OUTPUT'.
Output information before each output line. Should only be used in justified cases because it costs a lot of performance.
17. Slis_ev_subtotal_text TYPE slis_formname VALUE 'SUBTOTAL_TEXT'.
This event table (I_EVENTS) is now checked with the desired constants. If the desired constant is found, then the corresponding field for the FORM NAME is populated with the name of the routine containing the corresponding event.
Reward if useful,
Thanks
Aneesh.

Complete documentation of RDS sources?

Hi,
Does it exsist any documentation for the different RDS packages that simply list all specific tables/columns that are being used as the source for a specific HANA view? If yes; where is it possible to download it?
Thanks in advance!
Regards,
Erik Schmelck

System.Show()
Show a message box for Windows clients.
System.Notify()
Notify another application who may be waiting for upon some event to begin their logic.
System.Cleanup()
Cleanup of the actions done by .otl files. This is very specific to Oracle Lite.

Complete documentation of Oracle 10g

Have anyone a electronical docuemt about the functionality of Oracle 10g.
my email: [email protected]
Thanks

Have you looked at the user guide on otn.oracle.com?
http://www.oracle.com/pls/db102/homepage
Should be a good start.
C.

JDev 11g Where can I find "Complete" MDS Documentation

Hello All,
I am not able to find complete documentation for Oracle Meta Data Store(MDS) under 11g R1 docs
can anybody please point me where can I find this
Thanks a lot

Hi,
you can try to seach in the JDEV TP Forum (JDeveloper and OC4J 11g Technology Preview for MDS to get an overview.
But I don't know if the links to the TPx documents and cuecards still work.
There was some MDS included in the technologie previews but as Shay said not in the current production release.
regards
Peter

Complete arch (system) documentation?

Hi. I would like to have arch and it's mechanisms and infrastructure completely documented. Of course this could be quite a large task, but i think people like me (who like to read the manual before using stuff) would appreciate this, and it would also serve to leverage the overall knowledge of archlinux, so that less people would ask "stupid questions" (i don't mean it like that.. ) on the forums.
I also understand that this could realistically only be done for a "base" install arch system, as X11 and other applications/services go beyond the scope of such basic documentation.
The reason i would like this is because i couldn't find anything like this on the wiki, _and_, it would also be nice to have something compiled in a form you could print out. (ie without further references, but a compilation).

As far as a doc for experience users though i think that would be a waste, since most experienced users wouldn't need a doc to let them know how to edit a linux system.
Not the arch linux specifics, take the init system as an example. How, and what files are used. How to write your own init/daemon. Did you for example know that daemons get registered in /var/run daemons when succesfully started? And that rc.multi/functions is responsible for that (and how)? Or that rc.sysinit is resposible for setting you system locale?
Or how to use makepkg/makeworld in archlinux? Again, even if there already is a wiki entry about this, it should be a part of a compiled doc covering basic system maintenance in arch.
Some of the already present wiki articles (like setting up a network connection) though already existing, should be a part of this documentation. If necessary, expand them.

Looking for Documentation on PeopleSoft Delivered App Packages.

Hey Guys,
Do anyone know whether PeopleSoft provide documentation for the Delivered App Packages.
I'm expecting something like Java documentation, we get complete documentation like complete list of classes, respective methods, properties, and relation with other classes and packages.
It would be really helpful, if there is any documentation something similar for PeopleSoft Delivered Packages too.
Thanks in advance.
-M

I've been looking for something similar. There is some interesting stuff around the CDM for PeopleSoft CRM:
http://bloggingaboutoracleapplications.org/creating-peoplesoft-crm-worker-using-cdm-classes/
However nothing as comprehensive as JavaDoc for PeopleSoft - well that I know of anyway.

Documentation, success factor? Time consume? Tools, methods to use?

Hello,
Some questions in my mind, Please share your experience and knowledge. This is not a very technical question, it's a discussion.
Experts, database team leaders, Consultants, managers, CTO, CEO can share their thoughts....
- How many of you believe in documentation?
- Is documentation a success factor or is it just a waste of time in some cases?
- How much time should a database team spend on documentation per work day?
- How to "invite" database team members to use, write, maintain the documentation; which "smart" methods can be used?
- How can I know the documentation done is up to date? Should I just "trust" in my team members OR which "smarts" methods can be used to verify it?
- Which methods, tools can be used of a good, complete documentation of the database libray, logical structure, procedures, jobs, backup / recovery, installation, migrations, etc ... ?
Best regards,

Experts, database team leaders, Consultants, managers, CTO, CEO can share their thoughts....I am non of them...
- How many of you believe in documentation? 100% (Because its the number i.e. 100% which is representation of completeness)
- Is documentation a success factor or is it just a waste of time in some cases?It depends. It is waste of time only, if reader is either not having any approach to solve the problem or he/she is not doing practice as per instructions in docs.
- How much time should a database team spend on documentation per work day?Rather than opening facebook, chat room, playing games etc. (of course they are also meant for a mean), but one should think that i am an Oracle DBA; so my first task in free hour is to read docs.
- How to "invite" database team members to use, write, maintain the documentation; which "smart" methods can be used? Some sort of motivation in term of money and/or appraisals.
- How can I know the documentation done is up to date? Should I just "trust" in my team members OR which "smarts" methods can be used to verify it?It depends. First you can ask for proper documentation, check it and make necessary correction (if any required). As far as matter of concern of trust, yes you can but not blindly.
- Which methods, tools can be used of a good, complete documentation of the database libray, logical structure, procedures, jobs, backup / recovery, installation, migrations, etc ... ?As far as Oracle concern, i think there is no such great need to have documentation, because database dictionary is having all sort of metadata; but yes for DBA concern, you have to properly outlined the major in and outs of business, person, technical resources with higher administration that any DBA has to write procedure in this way, these are backup strategies, rules, Guideline for Installation, How to perform migration etc. If any DBA find fail to follow these "Working Manuals" then they might be punished by any mean.
I am not sure, how much all these are helpful, but i expressed my opinion/views.
Regards
Girish Sharma

Integration of JSR-168 portlet into Portal - Complete Guide

Hi there,
the CE 7.1 is described to be compatible with JSR-168 portlets.
Our Company has developed a JSR-168 portlet which comes as a WAR-File
which can be easily included in other application server and portals (WebShpere, Apache).
But integration in SAP Netweaver fails - I am missing a complete documentation
which describes me the necessary steps to integrate a JSR-168 portlet application
into the SAP Application Server and also how to integrate the GUI into a View of the NW portal.
PLEASE HELP ME!!!
Things I tried - Things I failed:
- Imported a EAR-File into Developement Studio and tried to add it to Server
-> Message "EAR Project: ... should have the SAP specific facet in order EAR to be built."
- Deployement via "Deployement Tool" of Netweaver 2.0 (2004s) worked
and I was able to start app but no integration into NW portal view was possible
(Where is the deployement tool in NW 7.1 CE?!?!?)
- I wanted to create a PAR-File by a WAR-File but dont know how?
- I did not find any iView template which is for my portlet type.
Did anyone out there has the same probs or could help me....
Thanks on advance,
Andi-)
Edited by: Markus Sümmchen on Oct 6, 2008 1:47 PM

Hi Markus,
There is no complete guide for integration of JSR-168 portlets into a portal; however Diyan is correct.
In a nutshell, once you have deployed your portlet, you use GPAL technology in the SAP NetWeaver Portal of CE to create an iView wrapper in the PCD. All of this done by a portal content admin in the Portal Content Studio. Your deployed portet should be displayed in the "Portlets" repository within the Portal Catalog of the Portal Content Studio.
For conceptual and how-to documentation, refer to the following SAP Help Portal links:
- Generic Portal Application Layer (GPAL) Repositories: http://help.sap.com/saphelp_nwce10/helpdata/en/44/5e93dc35624ddee10000000a1553f7/frameset.htm
- Integrating Applications into the Portal: http://help.sap.com/saphelp_nwce10/helpdata/en/45/90e8bfaec26c4ee10000000a1553f7/frameset.htm
- Working with GPAL Repositories: http://help.sap.com/saphelp_nwce10/helpdata/en/44/5b96b37b6f4de1e10000000a1553f7/frameset.htm
Please let me know if this works for you.
Michael

Manufacturing Interfaces documentation in R12

Hi,
For manufacturing interfaces, is the documentation in 11i still valid for R12? If not, where can I find it? I checked the doc library CD for R12 and couldn't find the 'Manufacturing Open Interfaces Guide', as it was in 11i.

Hi,
Refer to the latest version of the 11i Oracle Manufacturing APIs and Open Interfaces Manual for complete documentation on the Purchasing APIs and Open Interfaces and refer (Note: 437587.1 - Release 12 Oracle Purchasing API and Open Interface Changes) for the change made in Release 12.
You can also refer to "Oracle Integration Repository" which comes with R12 as a responsibility.
Regards,
Hussein

BW complete documentation

Similar Messages

Maybe you are looking for