Specifications

For all ShowAndPublish<Verb>BOD() methods, a new optional parameter is added: 
long ppmmm.bl999st00.OrderBOD.ShowAndPublish<Verb>BOD(
		domain	ppmmm.orno	i.internalOrderNumber,  | for example
	const		string		i.actionCode,
	const		string		i.documentId,
	const		string		i.revisionId,
	const		string		i.variationId,
	const		string		i.tenantId,
	const		string		i.accountingEntityId,
	const		string		i.locationId,
		[	long		i.settings ] )

Parameter i.settings optionally contains a 'struct' (XML) to specify the new optional settings and any future additions.

These elements are currently handled:

  • batchID
  • batchSequence
  • batchSize
For example: 
<Settings>
	<batchSequence>...</batchSequence>
	<batchID>...</batchID>
	<batchSize>...</batchSize>
</Settings>

The behavior is as follows.

If batch elements are set, the BOD is published as usual, but additionally some name-value pairs are added to the BODID of the published BOD:

  • If a batchSize element is included in the settings: batchSequence=<batchSequence.data>&batchID=<batchID.data>&batchSize= <batchSize.data> For example: infor-nid:acme:100:1:PO123:4?PurchaseOrder&verb=Sync&batchSequence=1& batchID=infor.ln.1:1&batchSize=2
  • If no batchSize element is included in the settings: batchSequence=<batchSequence.data>&batchID=<batchID.data> For example: infor-nid:acme:100:1:PO123:4?PurchaseOrder&verb=Sync&batchSequence=2 &batchID=infor.ln.1:1

If a variationID is used, then the batch elements are added after variationID name-value pair.

For example:

infor-nid:acme:100:1:PO123:4?PurchaseOrder&verb=Sync&variationID=1& batchSequence=2&batchID=infor.ln.1:1

Exception handling:

  • If batchSequence, batchID or batchSize does not exist or is empty then it is not included in the BODID. Because empty values are ignored, you cannot set an empty value such as batchSequence=2&batchID=&batchSize=2.
  • If batchSequence does not exist or is empty then batchID and batchSize are also ignored.
  • When including the same element multiple times, only one will be used.
  • For unknown elements a warning message is set. These elements are ignored, but the publishing continues, to ensure compatibility for future releases. Note that element names are case-sensitive.
  • The contents of the elements is not checked; it can be checked in the application (e.g. tcboddll0001) if needed.