Page tree
Skip to end of metadata
Go to start of metadata

Since SAP ECTR it is possible to combine different explosion scenarios with different sets of application load options.


This functionality depends on the capabilities of the underlying CAD-system and may work differently or not work at all with some CAD-systems.
Important prerequisite: the application (e.g. CAD-system) has to be able to work with partially provided assemblies!


A "load scenario" is a combination of an explosion scenario and application specific load options.

Use Case

Optimize fast load for large assemblies:

  • Loading a large assembly can take a long time (reading structure and metadata for all parts).
  • The file transfer needs a lot of time.
  • The CAD-system may even not be able to load large assemblies with full structure due to
    • RAM limitation
    • loading in CAD takes too long
    • bad performance of CAD when assembly is loaded

Using special "load scenario" can reduce the amount of data which needs to be exploded in SAP, download to the client and loaded into the CAD system.


We want to make it possible to load just first level of an assembly in CAD-system NX.

1 Create explosion scenario (transaction CDESK_CUS in ECC6.0, CAD_SRV_CUS in S/4HANA) which only takes direct children of an assembly.


The main difference between the usual explosion scenario "CAD_LOAD" and the explosion scenario we just created is the usage of the rules "1A/1N instead of NA/NN" - it means return child but don't return the structure underneath this child.

Make sure that the tables are maintained for CDESK_C_EXPLCF and CDESK_C_EXPLFA.

  • You can maintain these table with transaction SM30 and enter the corresponding view V_CDESK_C_EXPLCF or V_CDESK_C_EXPLFA.
  • For V_CDESK_C_EXPLCF maintain the values SORTF.
  • For V_CDESK_C_EXPLFA please maintain your possible SORTF value like above in the picture UGS:PI, UGS:C, UGS:CR, ...

2 Define the combination of explosion scenario named "FIRST_LEVEL" with load options "fitting" to the application.

This is done in the application-specific load_scenarios.xml
For NX  in the following file:

<?xml version="1.0" encoding="utf-8"?>
<document_load_scenarios xmlns:xsi="" xsi:noNamespaceSchemaLocation="../../../../basis/aux-files/load-scenarios.xsd">
    <description>first level</description>
    <!-- since new parameter - do/don't update cache in background -->
ONLY_FIRST_LEVEL_COMPONENTSname of load scenario
UGSapplication type used for NX Integration
FIRST_LEVELname of the explosion scenario (definition of how to resolve the structure in SAP Customizing)
COMPONENTS and COMPSETTINGSNX-specific load options required to be able to partially load the assembly with only a subset of provided files

2.1 Clean up working directory when opening documents with "Load Scenario"

This feature is available from SAP ECTR versions or

When opening the document with "Load Scenario", you can define in load_scenarios.xml whether the working directory should be cleaned up.
To do this, the element <cleanup_session> ... </cleanup_session> must be defined.

The files to be deleted can be defined with the element <document_selector/>. The element <document_selector/> can have the attributes master_filename_pattern and/or master_wsappl. At least one of the two attributes must be defined, otherwise the element is not considered.

load_scenarios.xml (Example)
  <document_selector master_filename_pattern=".*\.prt" master_wsappl="UGI"/>
  <document_selector master_filename_pattern=".*\.doc"/>
<!-- defines if the sessoin should be cleared before loading -->
<xs:element name="cleanup_session" minOccurs="0" maxOccurs="1">
    <!-- defines which files should be deleted when clearing the cache -->
        <xs:element name="document_selector" maxOccurs="unbounded">
                <xs:attribute name="master_filename_pattern" type="xs:string"/>
                <xs:attribute name="master_wsappl" type="xs:string"/>

If you want to delete all files allowed for deletion from the working directory, the following can be defined:

  <document_selector master_filename_pattern=".*"/>

3 Configure the function for documents (application type UGS)

This is done in the application-specific menu_macros.txt
For NX in the following file:


Add the following line...


... wherever it serves best:

? DOC_UGS 	= mnu.flyout.doc_doc
 			= fnc.doc.checkout
 			= -----------------------------

4 Configure dictionary text and icon

Add text for the function key in customer.txt:


Add the following line:

Codeblock = Open partially

Add the icon mapping in customer_icons.txt
For NX in the following file:


Add the following line:

Codeblock = {0}/view_without_structure


Function in ECTR

What happens when this function is executed

  1. SAP ECTR resolves the structure using explosion scenario "FIRST_LEVEL"
  2. SAP SAP ECTR provides files of all resolved documents into session directory
  3. ECTR sends top-level file to NX to open - with defined NX load options, the name of the used load scenario and the name of the explosion scenario

Effect of the function

  1. The session contains only files of the top-level document and documents directly referenced by the top-level document
  2. The assembly is loaded partially in NX without any errors (remember, loading of components was switched off by load options)

Application specific load options - sample





There may be more possible values. See CAD specific documentation.