Package Dependencies show information about upstream or downstream package dependencies.
Package Dependencies can be found inside each Package:
Package Dependencies affects how Packages can be deployed to different Runtime environments in Deployment Management.
Package dependencies with Entity Mapping
Package dependency will be created, when Entities from different packages are mapped together in Entity mapping.
In STG_NY_TAXI package, DEPENDENT PACKAGE is now the upstream DV_TAXI_TRIP package.
In DV_TAXI_TRIP package, DEPENDENCY PACKAGE is now the downstream STG_NY_TAXI -package.
Package dependencies with References
Package dependency will be created, when Entities from different packages are referenced with Foreign keys.
In DV_TAXI_TRIP package, Foreign keys are added from dv.L_TAXI_TRIP entity to dv.H_TAXI_TRIP_LOCATION entity in DV_TAXI_LOCATION package:
In DV_TAXI_TRIP package, DV_TAXI_LOCATION package is added to DEPENDENCY PACKAGE:
In DV_TAXI_LOCATION package, DV_TAXI_TRIP is added to DEPENDENT PACKAGE:
Circular dependencies with Foreign keys
References can cause circular dependencies
Packages can reference another package with Foreign keys only to one direction.
In this example, package DV_TAXI_TRIP already references package DV_TAXI_LOCATION with References, as seen in previous example.
If references are now added to DV_TAXI_LOCATION package to reference DV_TAXI_TRIP package, an error will occur: