Kontakt

Ansicht
Dokumentation

Portal-Independent Navigation Frame (New) ( RELNSRM_701_INDEP_NAVFRM )

Portal-Independent Navigation Frame (New) ( RELNSRM_701_INDEP_NAVFRM )

PERFORM Short Reference   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

Portal-Independent Navigation Frame (New)

Use

As of SAP Supplier Relationship Management 7.0 SP05 (SAP SRM 7.0 SP05), the Portal-independent navigation frame is available. With this function, you can work with SAP SRM applications without using the SAP NetWeaver Portal and its navigation features. This navigation frame has a look and feel that is very similar to the Portal-based navigation frame. An inbox that allows you to access your work items, alerts, and notifications is also available. The functions that can be accessed by the individual users depend on the standard PFCG roles, available in the Role Maintenance transaction (PFCG), that you assign to your users.

The standard PFCG roles delivered by SAP include all work centers, worksets, and service links that you need in order to perform the same procurement functions that are available in the standard SAP NetWeaver Portal roles for SAP SRM.

Note: The following features available in the SAP NetWeaver Portal are not supported:

  • Harmonized procurement roles for SAP ERP and SAP SRM
  • Business Package for Supplier Collaboration
  • User self-registration and the corresponding approval workflow
  • Accessibility functions for vision-impaired users are not supported by the Portal-independent navigation frame nor by SAP SRM applications running in this navigation frame. This is due to restrictions of the underlying technology, NetWeaver Business Client for HTML. For more information, see SAP Note 1029940.

Note: You must have installed SAP NetWeaver 7.01 SP06 to use the Portal-independent navigation frame and inbox.

For more information about the above-mentioned SAP NetWeaver Portal roles, see SAP Help Portal at http://help.sap.com → SAP Supplier Relationship Management → Business Packages → Business Package for SAP SRM 7.0or Business Package for Supplier Collaboration 4.0.

Effects on Existing Data

If you migrate from a system landscape with SAP NetWeaver Portal to a landscape without the Portal and you have customer-specific Portal roles, the roles are not automatically migrated. Instead, you can use transaction PFCGto either adapt the roles delivered by SAP or to model new roles that match the Portal roles that you were previously using.

If you have a system landscape without the SAP NetWeaver Portal and would like to implement the SAP NetWeaver Portal navigation, you must also implement any customer-specific changes you made in the roles in transaction PFCGin the Portal roles.

Effects on Data Transfer

Effects on System Administration

Effects on Customizing

You can activate the Portal-independent navigation frame and inbox in Customizing for SAP Supplier Relationship Managementunder SRM Server → Technical Basic Settings -> Portal-Independent Navigation Frame -> Activate/Deactivate Portal-Independent Navigation Frame.

In addition to the standard RFC connections, you must define an RFC connection of type H (HTTP) to your back-end systems under SRM Server -> Technical Basic Settings -> Define RFC Destinations, or use transaction SM59. Note that the name of the connection must end with one of the following character sequences:

  • For a non-secure connection, use "_HTTP".
Example: SAP_ERP_HTTP
  • For a secure connection, use "_HTTPS".
Example: SAP_ERP_HTTPS

You must also enter the HTTP connection defined above, but without the suffix, in the Customizing activity Define System Landscape in the System Alias for POWL Navigation field. For example, enter "SAP_ERP".

Settings for SAP NetWeaver Business Warehouse

If you want to use SAP NetWeaver Business Warehouse (SAP NetWeaver BW) together with the Portal-independent navigation frame, you must define your SAP NetWeaver BW system in Customizing for SAP Supplier Relationship Management under SRM Server-> Technical Basic Settings -> Define System Landscape. Make the following entries:

  • In the Logical Systemfield, enter "SAP_BW". This entry must be identical with the system alias that you defined in Customizing for the launchpad. For more information about the launchpad, see SAP Library for SAP NetWeaver on SAP Help Portal at http://help.sap.com -> SAP NetWeaver by Key Capability -> Application Platform by Key Capability -> ABAP Technology -> UI Technology -> Web UI Technology -> Floorplan Manager for Web Dynpro ABAP -> Launchpad.
  • In the System Alias for POWL Navigation field, enter "SAP_BW".

For SAP NetWeaver BW, as for all systems that you define in the Customizing activity Define System Landscape, you must configure an RFC connection under SRM Server -> Technical Basic Settings-> Define RFC Destinations, or use transaction SM59. This connection must be of type H (HTTP). Note that the name of the connection must end with one of the following character sequences:

  • For a non-secure connection, use "_HTTP".
Example: SAP_BW_HTTP
  • For a secure connection, use "_HTTPS".
Example: SAP_BW_HTTPS

Further Information






ABAP Short Reference   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 6966 Date: 20240523 Time: 054104     sap01-206 ( 129 ms )