End Routine Parameters
Importing
● REQUEST: Request ID
● DATAPAKID: Number of current data package
Exporting
● MONITOR: Table for user-defined monitoring. This table is filled using row structure MONITOR_REC (the record number of the processed record is inserted automatically from the framework).
Changing
● RESULT_PACKAGE: Contains all data that has been processed by the transformation.
Raising
● CX_RSROUT_ABORT: If a raise exception type cx rsrout_abort is triggered in the routine, the system terminates the entire loading process. The request is highlighted in the extraction monitor as Terminated. The system stops processing the current data package. This can be useful with serious errors.
By default, only fields that have a rule in the transformation are transferred from the end routine. Choose Change Update Behavior of End Routine to set the All Target Fields (Independent of Active Rules) indicator. As a result, fields that are only filled in the end routine are updated and are not lost. This function is only available for standard DataStore objects, DataStore objects for direct writing, and for master data tables.
If only the key fields are updated for master data attributes, all the attributes are initialized anyway, whatever the settings described here. For more information, see SAP Note 1096307.
Monday, November 9, 2009
Routine Parameters for Key Figures or Characteristics
Routine Parameters for Key Figures or Characteristics
Importing
● REQUEST: Request ID
● DATAPAKID: Number of current data package
● SOURCE_FIELDS: Structure with the routine source fields defined on the UI
Exporting
● MONITOR: Table for user-defined monitoring. This table is filled using row structure MONITOR_REC (the record number of the processed record is inserted automatically from the framework).
● RESULT: You have to assign the result of the computed key figure or computed characteristic to the RESULT variables.
● CURRENCY (optional): If the routine has a currency, you have to assign the currency here.
● UNIT (optional): If the routine has a unit, you have to assign the unit here.
Raising
Exception handling using exception classes is used to control what is written to the target:
● CX_RSROUT_SKIP_RECORD: If a raise exception type cx_rsrout_skip_record is triggered in the routine, the system stops processing the current row and continues with the next data record.
● CX_RSROUT_SKIP_VAL: If an exception type cx_rsrout_skip_val is triggered in the routine, the target field is deleted.
● CX_RSROUT_ABORT: If a raise exception type cx rsrout_abort is triggered in the routine, the system terminates the entire load process. The request is highlighted in the extraction monitor as Terminated. The system stops processing the current data package. This can be useful with serious errors.
Importing
● REQUEST: Request ID
● DATAPAKID: Number of current data package
● SOURCE_FIELDS: Structure with the routine source fields defined on the UI
Exporting
● MONITOR: Table for user-defined monitoring. This table is filled using row structure MONITOR_REC (the record number of the processed record is inserted automatically from the framework).
● RESULT: You have to assign the result of the computed key figure or computed characteristic to the RESULT variables.
● CURRENCY (optional): If the routine has a currency, you have to assign the currency here.
● UNIT (optional): If the routine has a unit, you have to assign the unit here.
Raising
Exception handling using exception classes is used to control what is written to the target:
● CX_RSROUT_SKIP_RECORD: If a raise exception type cx_rsrout_skip_record is triggered in the routine, the system stops processing the current row and continues with the next data record.
● CX_RSROUT_SKIP_VAL: If an exception type cx_rsrout_skip_val is triggered in the routine, the target field is deleted.
● CX_RSROUT_ABORT: If a raise exception type cx rsrout_abort is triggered in the routine, the system terminates the entire load process. The request is highlighted in the extraction monitor as Terminated. The system stops processing the current data package. This can be useful with serious errors.
End Routine
Example: End Routine
In the SAP ERP system, you are loading data using the General Ledger: Transaction Figures DataSource (0FI_GL_1) into the DataStore object FIGL: Transaction Figures (0FIGL_O06).
You want to create an end routine to fill the additional InfoObject Plan/Actual Indicator (ZPLACTUAL). You also want the routine to read field Value Type. If the value is 10 (actual), value A is written to the Plan/Actual Indicator InfoObject; if the value is 20 (plan), value P is written to the Plan/Actual Indicator InfoObject.
...
1. You are in transformation maintenance. Choose Create End Routine. The routine editor opens.
2. You enter the following lines of code:
*----------------------------------------------------------------------*
METHOD end_routine.
*=== Segments ===
FIELD-SYMBOLS:
TYPE _ty_s_TG_1.
*$*$ begin of routine - insert your code only below this line *-*
loop at RESULT_PACKAGE assigning
where vtype eq '010' or vtype eq '020'.
case-vtype.
when '010'.
-/bic/zplactual = 'A'. "Actual
when '020'.
-/bic/zplactual = 'P'. "Plan
endcase.
endloop.
*$*$ end of routine - insert your code only before this line *-*
ENDMETHOD. "end_routine
*----------------------------------------------------------------------*
The code loops through result_package searching for values that have the value type 10 or 20. For these values, the appropriate value is passed on to InfoObject Plan/Actual Indicator (ZPLACTUAL).
3. You exit the routine editor.
4. You save the transformation. An edit icon next to the End Routine indicates that an end routine is available.
In the SAP ERP system, you are loading data using the General Ledger: Transaction Figures DataSource (0FI_GL_1) into the DataStore object FIGL: Transaction Figures (0FIGL_O06).
You want to create an end routine to fill the additional InfoObject Plan/Actual Indicator (ZPLACTUAL). You also want the routine to read field Value Type. If the value is 10 (actual), value A is written to the Plan/Actual Indicator InfoObject; if the value is 20 (plan), value P is written to the Plan/Actual Indicator InfoObject.
...
1. You are in transformation maintenance. Choose Create End Routine. The routine editor opens.
2. You enter the following lines of code:
*----------------------------------------------------------------------*
METHOD end_routine.
*=== Segments ===
FIELD-SYMBOLS:
*$*$ begin of routine - insert your code only below this line *-*
loop at RESULT_PACKAGE assigning
where vtype eq '010' or vtype eq '020'.
case
when '010'.
when '020'.
endcase.
endloop.
*$*$ end of routine - insert your code only before this line *-*
ENDMETHOD. "end_routine
*----------------------------------------------------------------------*
The code loops through result_package searching for values that have the value type 10 or 20. For these values, the appropriate value is passed on to InfoObject Plan/Actual Indicator (ZPLACTUAL).
3. You exit the routine editor.
4. You save the transformation. An edit icon next to the End Routine indicates that an end routine is available.
Characteristic Routine
Example: Characteristic Routine
In the SAP ERP system, you are loading data using the General Ledger: Transaction Figures DataSource (0FI_GL_1) into the DataStore object FIGL: Transaction Figures(0FIGL_O06).
You want to create a routine for the characteristic Debit/Credit Indicator (0FI_DBCRIND) in the target that assigns the value D to debit postings and the value C to credit postings.
1. You are in transformation maintenance. In the rule group, you double click on InfoObject Debit/Credit Indicator (0FI_DBCRIND). The rule details screen appears.
2. You choose Add Source Fields and add the Total Debit Postings (UMSOL) and Total Credit Postings (UMHAB) fields so that they are available in the routine.
3. You choose Routine as the rule type. The routine editor opens.
4. You enter the following lines of code. They return either D or a C as the result value:
*---------------------------------------------------------------------*
METHOD compute_0FI_DBCRIND.
DATA:
MONITOR_REC TYPE rsmonitor.
*$*$ begin of routine - insert your code only below this line *-*
* result value of the routine
if SOURCE_FIELDS-umhab ne 0 and SOURCE_FIELDS-umsol eq 0.
RESULT = 'D'.
elseif SOURCE_FIELDS-umhab eq 0 and SOURCE_FIELDS-umsol ne 0.
RESULT = 'C'.
else.
monitor_rec-msgid = 'ZMESSAGE'.
monitor_rec-msgty = 'E'.
monitor_rec-msgno = '001'.
monitor_rec-msgv1 = 'ERROR, D/C Indicator'.
monitor_rec-msgv2 = SOURCE_FIELDS-umhab.
monitor_rec-msgv3 = SOURCE_FIELDS-umsol.
append monitor_rec to monitor.
RAISE EXCEPTION TYPE CX_RSROUT_ABORT.
endif.
*$*$ end of routine - insert your code only before this line *-*
ENDMETHOD. "compute_0FI_DBCRIND
*---------------------------------------------------------------------*
The system checks if the debit and credit postings contain values:
○ If the debit posting has values that are not equal to zero and the credit posting is equal to zero, the system assigns the value D.
○ If the credit posting has values that are not equal to zero and the debit posting is equal to zero, the system assigns the value C.
○ If both the debit and credit postings contain values, the system outputs an error in the monitor and terminates the loading process.
5. You exit the routine editor.
6. In the Rule Details dialog box, you choose Transfer Values.
7. You save the transformation.
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/c3963dfbde4dede10000000a422035/frameset.htm
In the SAP ERP system, you are loading data using the General Ledger: Transaction Figures DataSource (0FI_GL_1) into the DataStore object FIGL: Transaction Figures(0FIGL_O06).
You want to create a routine for the characteristic Debit/Credit Indicator (0FI_DBCRIND) in the target that assigns the value D to debit postings and the value C to credit postings.
1. You are in transformation maintenance. In the rule group, you double click on InfoObject Debit/Credit Indicator (0FI_DBCRIND). The rule details screen appears.
2. You choose Add Source Fields and add the Total Debit Postings (UMSOL) and Total Credit Postings (UMHAB) fields so that they are available in the routine.
3. You choose Routine as the rule type. The routine editor opens.
4. You enter the following lines of code. They return either D or a C as the result value:
*---------------------------------------------------------------------*
METHOD compute_0FI_DBCRIND.
DATA:
MONITOR_REC TYPE rsmonitor.
*$*$ begin of routine - insert your code only below this line *-*
* result value of the routine
if SOURCE_FIELDS-umhab ne 0 and SOURCE_FIELDS-umsol eq 0.
RESULT = 'D'.
elseif SOURCE_FIELDS-umhab eq 0 and SOURCE_FIELDS-umsol ne 0.
RESULT = 'C'.
else.
monitor_rec-msgid = 'ZMESSAGE'.
monitor_rec-msgty = 'E'.
monitor_rec-msgno = '001'.
monitor_rec-msgv1 = 'ERROR, D/C Indicator'.
monitor_rec-msgv2 = SOURCE_FIELDS-umhab.
monitor_rec-msgv3 = SOURCE_FIELDS-umsol.
append monitor_rec to monitor.
RAISE EXCEPTION TYPE CX_RSROUT_ABORT.
endif.
*$*$ end of routine - insert your code only before this line *-*
ENDMETHOD. "compute_0FI_DBCRIND
*---------------------------------------------------------------------*
The system checks if the debit and credit postings contain values:
○ If the debit posting has values that are not equal to zero and the credit posting is equal to zero, the system assigns the value D.
○ If the credit posting has values that are not equal to zero and the debit posting is equal to zero, the system assigns the value C.
○ If both the debit and credit postings contain values, the system outputs an error in the monitor and terminates the loading process.
5. You exit the routine editor.
6. In the Rule Details dialog box, you choose Transfer Values.
7. You save the transformation.
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/c3963dfbde4dede10000000a422035/frameset.htm
Start Routine Parameters
Importing
● REQUEST: Request ID
● DATAPAKID: Number of current data package
Exporting
● MONITOR: Table for user-defined monitoring. This table is filled by means of row structure MONITOR_REC (the record number of the processed record is inserted automatically from the framework).
Changing
● SOURCE_PACKAGE: Structure that contains the inbound fields of the routine.
Raising
● CX_RSROUT_ABORT: If a raise exception type cx rsrout_abort is triggered in the routine, the system terminates the entire load process. The request is highlighted in the extraction monitor as having been terminated. The system stops processing the current data package. This can be useful with serious errors.
● REQUEST: Request ID
● DATAPAKID: Number of current data package
Exporting
● MONITOR: Table for user-defined monitoring. This table is filled by means of row structure MONITOR_REC (the record number of the processed record is inserted automatically from the framework).
Changing
● SOURCE_PACKAGE: Structure that contains the inbound fields of the routine.
Raising
● CX_RSROUT_ABORT: If a raise exception type cx rsrout_abort is triggered in the routine, the system terminates the entire load process. The request is highlighted in the extraction monitor as having been terminated. The system stops processing the current data package. This can be useful with serious errors.
Start Routine
Example: Start Routine
In the SAP ERP system, you are loading data using the General Ledger: Transaction Figures DataSource (FI_GL_1) into the DataStore object FIGL: Transaction Figures (0FIGL_O06).
You want to create a start routine that deletes all the records from a data package that have debit and credit postings that are equal to zero.
...
1. Create a transformation. The source of the transformation has the Total Debit Postings (UMSOL) and Total Credit Postings (UMHAB) fields. They are assigned to the InfoObjects Total Debit Postings (0DEBIT) and Total Credit Postings (0CREDIT).
2. Choose Create Start Routine. The routine editor opens.
3. You go to the local part of the routine. You enter the following lines of code:
*----------------------------------------------------------------------*
METHOD start_routine.
*=== Segments ===
FIELD-SYMBOLS:
TYPE _ty_s_SC_1.
*$*$ begin of routine - insert your code only below this line *-*
DELETE SOURCE_PACKAGE where UMHAB = 0 and UMSOL = 0
*$*$ end of routine - insert your code only before this line *-*
ENDMETHOD. "start_routine
*----------------------------------------------------------------------*
The delete statement is the only line you require in order to filter debit and credit postings without values out of the data package.
4. You exit the routine editor.
5. You save the transformation. An edit icon next to the Start Routine indicates that a start routine is available.
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/c3963dfbde4dede10000000a422035/frameset.htm
In the SAP ERP system, you are loading data using the General Ledger: Transaction Figures DataSource (FI_GL_1) into the DataStore object FIGL: Transaction Figures (0FIGL_O06).
You want to create a start routine that deletes all the records from a data package that have debit and credit postings that are equal to zero.
...
1. Create a transformation. The source of the transformation has the Total Debit Postings (UMSOL) and Total Credit Postings (UMHAB) fields. They are assigned to the InfoObjects Total Debit Postings (0DEBIT) and Total Credit Postings (0CREDIT).
2. Choose Create Start Routine. The routine editor opens.
3. You go to the local part of the routine. You enter the following lines of code:
*----------------------------------------------------------------------*
METHOD start_routine.
*=== Segments ===
FIELD-SYMBOLS:
*$*$ begin of routine - insert your code only below this line *-*
DELETE SOURCE_PACKAGE where UMHAB = 0 and UMSOL = 0
*$*$ end of routine - insert your code only before this line *-*
ENDMETHOD. "start_routine
*----------------------------------------------------------------------*
The delete statement is the only line you require in order to filter debit and credit postings without values out of the data package.
4. You exit the routine editor.
5. You save the transformation. An edit icon next to the Start Routine indicates that a start routine is available.
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/c3963dfbde4dede10000000a422035/frameset.htm
Routines in Transformations
You can use routines to define complex transformation rules.
Routines are local ABAP classes that consist of a predefined definition area and an implementation area. The TYPES for the inbound and outbound parameters and the signature of the routine (ABAP method) are stored in the definition area. The actual routine is created in the implementation area. ABAP object statements are available in the coding of the routine. Upon generation, the coding is embedded in the local class of the transformation program as the method.
The routine has a global part and a local part. In the global part you define global data declarations 'CLASS DATA'. These are available in all routines.
You can create function modules, methods or external subprograms in the ABAP Workbench if you want to reuse source code in routines. You can call these in the local part of the routine. If you want to transport a routine that includes calls of this type, the routine and the object called should be included in the same transport request.
Transformations include different types of routine:
Start routines
Routines for Key Figures or Characteristics
End routines and
Expert routine.
Routines are local ABAP classes that consist of a predefined definition area and an implementation area. The TYPES for the inbound and outbound parameters and the signature of the routine (ABAP method) are stored in the definition area. The actual routine is created in the implementation area. ABAP object statements are available in the coding of the routine. Upon generation, the coding is embedded in the local class of the transformation program as the method.
The routine has a global part and a local part. In the global part you define global data declarations 'CLASS DATA'. These are available in all routines.
You can create function modules, methods or external subprograms in the ABAP Workbench if you want to reuse source code in routines. You can call these in the local part of the routine. If you want to transport a routine that includes calls of this type, the routine and the object called should be included in the same transport request.
Transformations include different types of routine:
Start routines
Routines for Key Figures or Characteristics
End routines and
Expert routine.
Wednesday, September 30, 2009
Business Content Installation's
TC - RSORBCT
or
RSA1 --> BI Content.
If you want to install a Infocube select Infocube in second frame.
It ask for source system , select that
It starts collecting and you can see
After Installing
or
RSA1 --> BI Content.
If you want to install a Infocube select Infocube in second frame.
It ask for source system , select that
It starts collecting and you can see
After Installing
Wednesday, September 16, 2009
Process Chains
Process Chains
Dear All,
Here with, i am providing you some best links for process chains, Which explains clearly how to create process chain step by step ?
Step by step procedure to create process chain by Jeurgen
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/8280
For Creating Process chain Step by step:
http://help.sap.com/saphelp_nw70/helpdata/en/67/13843b74f7be0fe10000000a114084/content.htm
For maintianing Pc:
http://help.sap.com/saphelp_nw70/helpdata/en/d3/53e03b8235953ee10000000a114084/content.htm
For all other info abt PC:
http://help.sap.com/saphelp_nw70/helpdata/en/8f/c08b3baaa59649e10000000a11402f/content.htm
Best Regards, Kali
Dear All,
Here with, i am providing you some best links for process chains, Which explains clearly how to create process chain step by step ?
Step by step procedure to create process chain by Jeurgen
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/8280
For Creating Process chain Step by step:
http://help.sap.com/saphelp_nw70/helpdata/en/67/13843b74f7be0fe10000000a114084/content.htm
For maintianing Pc:
http://help.sap.com/saphelp_nw70/helpdata/en/d3/53e03b8235953ee10000000a114084/content.htm
For all other info abt PC:
http://help.sap.com/saphelp_nw70/helpdata/en/8f/c08b3baaa59649e10000000a11402f/content.htm
Best Regards, Kali
Friday, August 7, 2009
Inventory Marker Updates
Inventory Marker Updates
Initialization INFOCUBE LEVEL and DATASOURCE LEVEL 7.0
IF 3.0 FLOW TRANSFERLEVEL SELECT OPENING BALANCE
SELECT OPENING BALANCE IN GENERAL TAB (BX ONLY)
IPACK LEVEL SELECT GENERATE INTI(BX)
IPACK LEVEL INITDELTA(BF,UM)
BX WITH MARKER
BF WITHOUT MARKER
UM WITHOUT MARKER
DELTALOAD
BX Wont Support Delta.
BF WITH MARKER
UM WITH MARKER
Initialization INFOCUBE LEVEL and DATASOURCE LEVEL 7.0
IF 3.0 FLOW TRANSFERLEVEL SELECT OPENING BALANCE
SELECT OPENING BALANCE IN GENERAL TAB (BX ONLY)
IPACK LEVEL SELECT GENERATE INTI(BX)
IPACK LEVEL INITDELTA(BF,UM)
BX WITH MARKER
BF WITHOUT MARKER
UM WITHOUT MARKER
DELTALOAD
BX Wont Support Delta.
BF WITH MARKER
UM WITH MARKER
Thursday, July 2, 2009
Update Types in BI
Update types in BW/BI
With the update type, you control whether a key figure/data field is updated in the InfoProvider.
Functions
For InfoCubes:
Depending on the aggregation type you entered in the Key Figure Maintenance for this key figure, you are given the options Addition or Maximum or Minimum. If you choose one of these options, new values are updated in the InfoCube.
The aggregation type (addition, minimum & maximum) determines how key figures are updated where primary keys are the same. Thus the total, the minimum or the maximum for these values is formed for new values.
If you entered one of these aggregation types in the key figure definition, it is transferred for the update. Otherwise, the aggregation type addition is automatically selected.
• If you choose no update, the key figures are not updated in the InfoCube, meaning that no data records are written in the InfoCube with the first data transfer, or that data records that already exist, will remain in place with subsequent transfers.
For InfoObjects:
Only the Overwrite option is available. With this option, new values are updated to the InfoObject.
For ODS Objects:
1. Depending on the type of data and DataSource, you have the options Addition, Minimum, Maximum or Overwrite. If you choose one of these options, new values are updated in the ODS object.
For numerical data fields, you are given a proposal for the update type through the characteristic 0RECORDMODE. If only the after-image is delivered, the system proposes Overwrite. However, it could make sense to change this: For example, with the meter data field “# Changes”, which is filled with a constant 1 but still has to be updated through addition, although only an after-image is delivered.
Characteristic 0RECORDMODE is used to pass indicators of the DataSource (from SAP systems) to the update.
You do not need characteristic 0RECORDMODE as long as you do not load delta requests in the ODS object or only from file DataSources.
a. Addition:
Addition is not supported with the data types CHAR, DAT, TIMS, CUKY and UNIT. To be able to use the addition function, make sure the DataSource is compatible with an additive delta.
b. Overwrite:
Whether overwriting is supported is determined by the delta-compatibility of the DataSource.
In this example, the order quantity changes after it has been loaded into BW. With the second load process the data is overwritten since it has the same primary key.
First load process
Document No. Document Item Order Quantity Unit of measure
100001 10 200 Pieces
100001 20 150 Pieces
100002 10 250 Kg
Second load process
Document No. Document Item Order Quantity Unit of measure
100001 10 180 Pieces
100001 20 165 Pieces
When you update data, the system keeps to the time sequence of the data packages and requests. You have to decide the logical order of the update yourself. Meaning, for example, orders must be requested before deliveries; otherwise the wrong results may appear when you overwrite the data.
c. If you choose no update, the data fields are not updated in the ODS object, meaning that no data records are written in the ODS object with the first data transfer, or that data records that already exist will remain in place with subsequent transfers.
With the update type, you control whether a key figure/data field is updated in the InfoProvider.
Functions
For InfoCubes:
Depending on the aggregation type you entered in the Key Figure Maintenance for this key figure, you are given the options Addition or Maximum or Minimum. If you choose one of these options, new values are updated in the InfoCube.
The aggregation type (addition, minimum & maximum) determines how key figures are updated where primary keys are the same. Thus the total, the minimum or the maximum for these values is formed for new values.
If you entered one of these aggregation types in the key figure definition, it is transferred for the update. Otherwise, the aggregation type addition is automatically selected.
• If you choose no update, the key figures are not updated in the InfoCube, meaning that no data records are written in the InfoCube with the first data transfer, or that data records that already exist, will remain in place with subsequent transfers.
For InfoObjects:
Only the Overwrite option is available. With this option, new values are updated to the InfoObject.
For ODS Objects:
1. Depending on the type of data and DataSource, you have the options Addition, Minimum, Maximum or Overwrite. If you choose one of these options, new values are updated in the ODS object.
For numerical data fields, you are given a proposal for the update type through the characteristic 0RECORDMODE. If only the after-image is delivered, the system proposes Overwrite. However, it could make sense to change this: For example, with the meter data field “# Changes”, which is filled with a constant 1 but still has to be updated through addition, although only an after-image is delivered.
Characteristic 0RECORDMODE is used to pass indicators of the DataSource (from SAP systems) to the update.
You do not need characteristic 0RECORDMODE as long as you do not load delta requests in the ODS object or only from file DataSources.
a. Addition:
Addition is not supported with the data types CHAR, DAT, TIMS, CUKY and UNIT. To be able to use the addition function, make sure the DataSource is compatible with an additive delta.
b. Overwrite:
Whether overwriting is supported is determined by the delta-compatibility of the DataSource.
In this example, the order quantity changes after it has been loaded into BW. With the second load process the data is overwritten since it has the same primary key.
First load process
Document No. Document Item Order Quantity Unit of measure
100001 10 200 Pieces
100001 20 150 Pieces
100002 10 250 Kg
Second load process
Document No. Document Item Order Quantity Unit of measure
100001 10 180 Pieces
100001 20 165 Pieces
When you update data, the system keeps to the time sequence of the data packages and requests. You have to decide the logical order of the update yourself. Meaning, for example, orders must be requested before deliveries; otherwise the wrong results may appear when you overwrite the data.
c. If you choose no update, the data fields are not updated in the ODS object, meaning that no data records are written in the ODS object with the first data transfer, or that data records that already exist will remain in place with subsequent transfers.
Wednesday, June 24, 2009
What is SAP Portal?
SAP NetWeaver Portal [1] (formerly known as SAP Enterprise Portal, EP) offers a single point of access to information, enterprise applications, and services both in and outside your organization. It provides you the tools to manage this knowledge, to analyze and interrelate it, and to share and collaborate on the basis of it. With its coherent interface, role-based content, and personalization features, the portal enables you to focus exclusively on data relevant to your daily decision-making processes. SAP Enterprise Portal is one of the building blocks in the SAP NetWeaverTM architecture. Users only need a desktop and a Web Browser, and can begin work once they have been authenticated in the portal.
Tightly integrated into SAP Enterprise Portal are the knowledge management and collaboration capabilities of SAP NetWeaver, which allow users to share information, and to work together using that information.
Knowledge Management offers capabilities that everyone can use to distribute and access unstructured information within an organization through a heterogeneous repository landscape.
Collaboration brings users, information, and applications together to ensure successful cooperation. All collaboration tools and channels are easily accessible directly from the portal. These tools include collaboration rooms, instant messaging, chat, e-mail, and calendar integration.
SAP Unification Server enables an enterprise to integrate the resources of its information systems and provide unified access to its structured data. It is the engine driving the unification of databases, legacy systems and enterprise applications in SAP Enterprise Portal.
The Portal is used for different purposes.
* Internationalization
* Personalization
* Integration
* Authorization
SAP NetWeaver Portal is the platform for running Web Dynpro applications or Dyn Page applications created by SAP or custom designed for connecting to some ERP functionality.
Tightly integrated into SAP Enterprise Portal are the knowledge management and collaboration capabilities of SAP NetWeaver, which allow users to share information, and to work together using that information.
Knowledge Management offers capabilities that everyone can use to distribute and access unstructured information within an organization through a heterogeneous repository landscape.
Collaboration brings users, information, and applications together to ensure successful cooperation. All collaboration tools and channels are easily accessible directly from the portal. These tools include collaboration rooms, instant messaging, chat, e-mail, and calendar integration.
SAP Unification Server enables an enterprise to integrate the resources of its information systems and provide unified access to its structured data. It is the engine driving the unification of databases, legacy systems and enterprise applications in SAP Enterprise Portal.
The Portal is used for different purposes.
* Internationalization
* Personalization
* Integration
* Authorization
SAP NetWeaver Portal is the platform for running Web Dynpro applications or Dyn Page applications created by SAP or custom designed for connecting to some ERP functionality.
Subscribe to:
Posts (Atom)