InfoPackage

 Definition

An InfoPackage (active object: ISIP/delivery object :SHIP) is a source-system dependent object that has the GUID as key. There is one object for each source system.

You can find additional information about this BW object under Maintaining an InfoPackage.

Structure

Key Fields of an InfoPackage (ISIP/SHIP)

Version	Key Fields	Data Fields
A (active) / M (modified) / T (Transport) - ISIP	GUID	Source System
D (Delivery /. Content) - SHIP	GUID	Source system release

As the source system does not exist in the key, but is contained within the data part, the InfoPackage objects is also delivered as a shadow table.

Example

The following example aims to show what you need to be aware of when delivering InfoPackages within partner Content.

The Content development system is connected to source system Q1. There is exactly one InfoPackage with GUID1 for this source system.

In the customer system, this InfoPackage is to be activated for several source systems with the same release status:

·        Source system X1, Release 4.0

·        Source system X2, Release 4.0

Accordingly, the InfoPackage is copied into the A version twice. The logic behind this is the same as for transfer rules (see Transfer Rules and DataSource). Conversion is carried out byRSSM_SHIP_PSEUDO_DVERSION_WIR. The copies contains GUID3 and GUID4.

When SAP delivers again, you need to know from which InfoPackage GUID3 and GUID4 are derived. This information is stored in table RSSHIPDVERS:

Table RSSHIPDVERS

LOGDPID_SH	LOGSYS	LOGDPID
GUID3	X1	GUID2
GUID4	X2	GUID2