<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/da/onlinemanual/000400c" xml:lang="en">
	<Header>
		<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Event Publishing Usage</Title>
		<Keyword ContextSensitive="No"><Level1>Event Publishing</Level1>
		</Keyword>
		<Keyword ContextSensitive="No"><Level1>Business Object</Level1>
		</Keyword>
	</Header>
	<AimSection></AimSection>
	<GeneralSection><List><ListIntro>There are different types of usage for event publishing:</ListIntro>
			<ListItem>Event handling: use events from ERP LN to take action in another application.</ListItem>
			<ListItem>Synchronization: use events from ERP LN to synchronize business data in another application or database.</ListItem>
		</List>
		<Paragraph class="Default">Event handling is needed when an application needs to be notified of a specific event in ERP LN. For example, the creation of a new sales order, the completion of a production order, or the blocking of a customer. In that case the PublishChanges can be used. Events on a specific business object are published and can be processed by, for example, a workflow application.</Paragraph>
		<Paragraph class="Default">Synchronization is a type of integration where the involved sites or applications have an overlap in persistent data. For example, in addition to an ERP application containing item (product) data, a customer relationship management application is used that also contains product information.</Paragraph>
		<List><ListIntro>Basically, two approaches exist for this type of integration:</ListIntro>
			<ListItem>Regularly re-sending the complete data set containing all relevant instances of the business objects.</ListItem>
			<ListItem>In change-based synchronization, instead of re-sending the whole data set regularly, the target applications receive change events, such as 'create', 'change' or 'delete' for those object instances that were changed. In this case a one-time synchronization of all relevant instances of the business objects is done in order to get a baseline, followed by synchronization of relevant changes whenever they occur.</ListItem>
		</List>
		<Paragraph class="Default">You can implement the first approach by regularly issuing a PublishList request, which will send the requested data set. You can implement the second approach by using a combination of PublishList and PublishChanges.</Paragraph>
	</GeneralSection>
	<RelatedTopics><SectionTitle>
                              Related topics
                           </SectionTitle>
		<RelTopic><Link href="/baanerp/da/onlinemanual/000400a" role="manual">Publishing Methods</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/da/onlinemanual/000400b" role="manual">Overview of components</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/da/onlinemanual/000400" role="manual">Event Publishing Overview</Link>
		</RelTopic>
	</RelatedTopics>
</ManualTopic>
