Field extension hub for extension fields across a customer landscape

A system comprising:

• one or more computers;
• and
• a non-transitory computer-readable medium coupled to the one or more computers having instructions stored thereon which, when executed by the one or more computers, cause the one or more computers to perform operations via a field extension hub, the operations comprising:
• receiving, from a customer, a request to modify a structure of an entity used in a customer landscape by adding an extension field to the entity, wherein the customer landscape includes multiple system tenants of different types of systems, and the extension field is to be added to at least two different systems used by the customer, wherein the at least two different systems are provided by different vendors, and each system of the at least two different systems includes an entity-using system tenant that uses instances of the entity in at least one process;
• in response to receiving the request to modify the structure of the entity, determining, from among the multiple system tenants, at least one entity-using system tenant that uses instances of the entity in at least one process;
• providing event-pairing information to each entity-using system tenant to enable each entity-using system tenant to receive extension field events;
• receiving field attribute values for a set of field attributes for the extension field, wherein the field attribute values describe a target state of the extension field;
• generating, using the received field attribute values, a field creation event that instructs an entity-using system tenant receiving the field creation event to modify the structure of the entity in that entity-using system tenant by creating a local field that has the target state of the extension field in that entity-using system tenant and adding the local field to the structure of the entity;
• and
• sending the field creation event to each entity-using system tenant, wherein each respective local field created by a respective entity-using system tenant and added to the structure of the entity in response to receiving the field creation event has the target state of the extension field;
• and
• updating an integration component by updating integration content to map a first local field of a first entity-using system tenant to a second local field of a second entity-using system tenant.

A computer program product encoded on a non-transitory storage medium, the product comprising non-transitory, computer readable instructions for causing one or more processors to perform operations via a field extension hub, the operations comprising:

• receiving, from a customer, a request to modify a structure of an entity used in a customer landscape by adding an extension field to the entity, wherein the customer landscape includes multiple system tenants of different types of systems, and the extension field is to be added to at least two different systems used by the customer, wherein the at least two different systems are provided by different vendors, and each system of the at least two different systems includes an entity-using system tenant that uses instances of the entity in at least one process;
• in response to receiving the request to modify the structure of the entity, determining, from among the multiple system tenants, at least one entity-using system tenant that uses instances of the entity in at least one process;
• providing event-pairing information to each entity-using system tenant to enable each entity-using system tenant to receive extension field events;
• receiving field attribute values for a set of field attributes for the extension field, wherein the field attribute values describe a target state of the extension field;
• generating, using the received field attribute values, a field creation event that instructs an entity-using system tenant receiving the field creation event to modify the structure of the entity in that entity-using system tenant by creating a local field that has the target state of the extension field in that entity-using system tenant and adding the local field to the structure of the entity;
• and
• sending the field creation event to each entity-using system tenant, wherein each respective local field created by a respective entity-using system tenant and added to the structure of the entity in response to receiving the field creation event has the target state of the extension field;
• and
• updating an integration component by updating integration content to map a first local field of a first entity-using system tenant to a second local field of a second entity-using system tenant.