InfoArea, Application Component and InfoPackageGroup 

Development and Delivery of Partner Content

1. Scenario: Nodes as Subnodes of the Root of the Tree on Required Position

Create one or more nodes as subnodes for your partner content object by calling up the context menu for the root node of the relevant tree in the Modeling function area of the Administrator Workbench in the content development system. You can create however many additional nodes under this node.

You can find additional information under InfoArea, Application Component and InfoPackageGroup for the partner Content.

2. Scenario: Nodes as Subnodes of the Root of the Tree on Required Position

If you create a node in the corresponding Administrator Workbench tree for your partner Content object, the system also registers nodes which mark their position in the hierarchy at the same time.

Details

Name	Description	Field name in table RSAPPL
Parent	Superordinate application component (parent node)	APPLNM_P
Child	Subordinate application component (child node) The system (only) enters the first subnode, even if there are several nodes.	APPLNM_C
Next	Next application component (neighbor node)	APPLNM_N

If you insert a node, under which your partner Content objects hang, in a particular position on the child level under the root node of the respective tree, the system inserts your partner Content node as NEXT in the predecessor node.  

With the delivery of partner Content, the system tries to add a partner Content node in accordance with the table entries. If the tree in the partner system is structured differently than in the partner Content development test system, and as a result, the node cannot be assigned, the system then decides to insert the node under Non Assigned Nodes.

The following graphic illustrates the relations between different objects for this node, under which all partner Content objects are placed, using the example of node Content1.  Content1 should be inserted after node SAPI:

To enable the system to insert the node Content1 in the field APPLNM_N of its predecessor node SAP1 in table RSAPPL, you first need to set SAP1 to changeable. Do this by assigning the value 2 to the field CONTENT_CHANGE in table RSOCONTCHNGABLE: External Objects Also Changeable in D Version- CTO Connection.  In this way, you ensure that the table entry (Content 1 as NEXT in SAP1) is also delivered to all junior systems. You can find additional information under Object Changeability in a Partner Content System.