Register Parent

Marketing Authorization Holders (MAHs) that own Indonesia Compliance can now generate a Register Parent report to capture the parent serial numbers that are part of a shipment. Register Parent report includes only secondary- and tertiary-level serial numbers in an aggregation.

Configure the report

Configure event triggers

The event triggers (i.e. workflow subscriptions) for the report can be set in Administer for Indonesia Compliance. Make sure one of the following event triggers are enabled:

Source Application	Event	Action	Description
Serialized Operations Manager	Shipment	Generate Register Parent, Packing Aggregate and Send Product Reports for In Country Sales from Core Integration	TraceLink generates Register Parent, Packing Aggregate and Send Product Reports for in-country sales shipments within Indonesia when they are submitted via core integration or the Web UI, as long as all of the following trigger conditions are met: Event trigger conditions for Register Parent. Event trigger conditions for Packing Aggregate. Event trigger conditions for Send Product.
Serialized Operations Manager	Shipment	Generate Register Parent, Packing Aggregate and Send Product Reports for In Country Sales from ESM Integration	TraceLink generates Register Parent, Packing Aggregate and Send Product Reports for in-country sales shipments within Indonesia when they are submitted via ESM integration as long as all of the following trigger conditions are met: Event trigger conditions for Register Parent. Event trigger conditions for Packing Aggregate. Event trigger conditions for Send Product.

Source Application

Event

Action

Description

Serialized Operations Manager

Shipment

Generate Register Parent, Packing Aggregate and Send Product Reports for In Country Sales from Core Integration

TraceLink generates Register Parent, Packing Aggregate and Send Product Reports for in-country sales shipments within Indonesia when they are submitted via core integration or the Web UI, as long as all of the following trigger conditions are met:

Event trigger conditions for Register Parent.
Event trigger conditions for Packing Aggregate.
Event trigger conditions for Send Product.

Serialized Operations Manager

Shipment

Generate Register Parent, Packing Aggregate and Send Product Reports for In Country Sales from ESM Integration

TraceLink generates Register Parent, Packing Aggregate and Send Product Reports for in-country sales shipments within Indonesia when they are submitted via ESM integration as long as all of the following trigger conditions are met:

Event trigger conditions for Register Parent.
Event trigger conditions for Packing Aggregate.
Event trigger conditions for Send Product.

For more information on how to enable the event triggers, see the Administer Help Center.

Generate the report

Automatically, using event triggers

To generate the Register report automatically, enable the appropriate event triggers and ensure that the relevant event trigger conditions are met. When configured, Indonesia Compliance generates the Register report automatically when a product release event occurs in one of the following interfaces:

API integration

Use any of the following Serialized Operations Manager APIs to trigger the Register report:

ESM Shipment (EPCIS v1.2)
ESM Shipment (XML)
Sales Shipment (EPCIS v1.2)
Sales Shipment (XML)
Shipment Event (EPCIS v1.2)
Update Order Shipment (SOAP)

ESM Shipment (EPCIS v1.2)

Complete the elements required for the report as follows. See the Serialized Operations Manager ESM Synchronization API Guide for more information.

Element	Values
VocabularyElement	Must include: A ship from location with a name, address, and identifier. A ship to location with a name, address, and identifier. The locations can also be specified in the sourceList or destinationList for the shipment event as a master data lookup.
tl:shipToCountryCode	`ID`.
tl:shipFromCountryCode	`ID`.
tl:salesDistributionType	`INCOUNTRYSALE`.
bizTransactionList	Specify the business transaction identifiers for the Advance Ship Notice and/or Invoice and/or Purchase Order governing this shipment. For example: `urn:epcglobal:cbv:btt:po:0333331013655:45006290016` The GLN that occurs after `urn:epcglobal:cbv:bt:` identifies the party that issued the message, i.e. if the customer issues a purchase order, the GLN of the customer is included as the GLN in the bizTransaction string. A delivery number or ASN is mandatory, all other transaction types are optional.
epcList	Specify the list of the EPCs of top most containers (e.g. pallets, cases) in the shipment.
action	Set the action value to ADD.
bizStep	Set the action value to `urn:epcglobal:cbv:bizstep:shipping`.
disposition	Set the action value to `urn:epcglobal:cbv:disp:in_transit`.
readPoint	Specify the readPoint ID.

ESM Shipment (XML)

Complete the elements required for the report as follows. See the Serialized Operations Manager ESM Synchronization API Guide for more information.

Element	Values
cmn:DeliveryNumber	Specify the order information to the serialized receive information for this customer delivery.
cmn:DeliveryCompleteFlag	Instructs TraceLink to process the outbound delivery, update the status of all serial numbers and sub-child aggregations to shipped, and trigger generation of regulatory reporting messages based on customer configuration. If all of the information (order detail and received serial numbers) is in a single message, the delivery complete flag is set to true. If only partial information is in the message (e.g. order detail only, received items sent incrementally, etc.) the delivery complete flag is set to false for all intermediate messages, and then set to true when the delivery is complete and all information has been communicated to TraceLink.
cmn:TransactionIdentifier	Specify the identifier that associates with the received serial numbers, for regulatory reporting purposes. At least one transaction id is mandatory.
cmn:TransactionDate	Specify the date of the transaction in YYYY-MM-DD format.
cmn:ShipToCountryCode	`ID`.
cmn:ShipFromCountryCode	`ID`.
cmn:SalesDistributionType	`INCOUNTRYSALE`.
cmn:OrderItemList	Order item list group is populated to communicate the expected receive quantities for each item code at the EACH (unit) level. This information is used to verify the actual serial number received, the correct product, the correct lot number (if provided), and the correct each quantity.
cmn:SenderInfo	Specify the information about the supply chain partner that is sending the shipment. Contains XML choice elements of cmn:FromBusinessParty and cmn:ShipFromLocation that govern whether to use master data lookup to populate the address, license, and contact elements.
cmn:ReceiverInfo	Specify the information about the supply chain partner that is receiving the shipment. ReceiverInfo contains XML choice elements for cmn:ToBusinessParty and cmn:ShipToLocation that govern whether to use master data lookup to populate the address, license, and contact elements.

Sales Shipment (EPCIS v1.2)

Complete the elements required for the report as follows. See the Serialized Operations Manager Core Integration API Guide for more information.

Element	Values
VocabularyElement	Must include: A ship from location with a name, address, and identifier. A ship to location with a name, address, and identifier. The locations can also be specified in the sourceList or destinationList for the shipment event as a master data lookup.
tl:shipToCountryCode	`ID`.
tl:salesDistributionType	`INCOUNTRYSALE`.
bizTransactionList	Specify the business transaction identifiers for the Advance Ship Notice and/or Invoice and/or Purchase Order governing this shipment. For example: `urn:epcglobal:cbv:btt:po:0333331013655:45006290016` The GLN that occurs after `urn:epcglobal:cbv:bt:` identifies the party that issued the message, i.e. if the customer issues a purchase order, the GLN of the customer is included as the GLN in the bizTransaction string. A delivery number or ASN is mandatory, all other transaction types are optional.
epcList	Specify the list of the EPCs of top most containers (e.g. pallets, cases) in the shipment.
action	Set the action value to ADD.
bizStep	Set the action value to `urn:epcglobal:cbv:bizstep:shipping`.
disposition	Set the action value to `urn:epcglobal:cbv:disp:in_transit`.
readPoint	Specify the readPoint ID.

Sales Shipment (XML)

Complete the elements required for the report as follows. See the Serialized Operations Manager Core Integration API Guide for more information.

Element	Values
cmn:DeliveryNumber	Specify the delivery number that links the order information to the serialized pick information for this customer delivery. cmn:DeliveryNumber must be unique for across all shipments.
cmn:DeliveryCompleteFlag	Instructs TraceLink to process the outbound delivery, update the status of all serial numbers and sub-child aggregations to shipped, and trigger generation of regulatory reporting messages based on customer configuration. If all of the information (order detail and received serial numbers) is in a single message, the delivery complete flag is set to true. If only partial information is in the message (e.g. order detail only, received items sent incrementally, etc.) the delivery complete flag is set to false for all intermediate messages, and then set to true when the delivery is complete and all information has been communicated to TraceLink.
cmn:TransactionIdentifier	Specify the identifier that associates with the received serial numbers, for regulatory reporting purposes. At least one transaction id is mandatory.
cmn:TransactionDate	Specify the date of the transaction in YYYY-MM-DD format.
cmn:ShipToCountryCode	`ID`.
cmn:ShipFromCountryCode	`ID`.
cmn:SalesDistributionType	`INCOUNTRYSALE`.
cmn:OrderItemList	Order item list group is populated to communicate the expected receive quantities for each item code at the EACH (unit) level. This information is used to verify the actual serial number received, the correct product, the correct lot number (if provided), and the correct each quantity.
cmn:SenderInfo	Specify the information about the supply chain partner that is sending the shipment. Contains XML choice elements of cmn:FromBusinessParty and cmn:ShipFromLocation that govern whether to use master data lookup to populate the address, license, and contact elements.
cmn:ReceiverInfo	Specify the information about the supply chain partner that is receiving the shipment. ReceiverInfo contains XML choice elements for cmn:ToBusinessParty and cmn:ShipToLocation that govern whether to use master data lookup to populate the address, license, and contact elements.

Shipment Event (EPCIS v1.2)

Complete the elements required for the report as follows. See the Serialized Operations Manager Trade Partner Event Exchange API Guide for more information.

Element	Values
VocabularyElement	Must include: A ship from location with a name, address, and identifier. A ship to location with a name, address, and identifier. The locations can also be specified in the sourceList or destinationList for the shipment event as a master data lookup.
tl:shipToCountryCode	`ID`.
tl:shipFromCountryCode	`ID`.
tl:salesDistributionType	`INCOUNTRYSALE`.
bizTransactionList	Specify the business transaction identifiers for the Advance Ship Notice and/or Invoice and/or Purchase Order governing this shipment. For example: `urn:epcglobal:cbv:btt:po:0333331013655:45006290016` The GLN that occurs after `urn:epcglobal:cbv:bt:` identifies the party that issued the message, i.e. if the customer issues a purchase order, the GLN of the customer is included as the GLN in the bizTransaction string. A delivery number or ASN is mandatory, all other transaction types are optional.
epcList	Specify the list of the EPCs of top most containers (e.g. pallets, cases) in the shipment.
action	Set the action value to ADD.
bizStep	Set the action value to `urn:epcglobal:cbv:bizstep:shipping`.
disposition	Set the action value to `urn:epcglobal:cbv:disp:in_transit`.
readPoint	Specify the readPoint ID.

Update Order Shipment (SOAP)

Complete the elements required for the report as follows. See the Serialized Operations Manager SOAP API Guide for more information.

Element	Values
OrderRequest	Specify all the required elements. @deliveryNumber - Specify the delivery number that links the order information to the serialized pick information for this customer delivery. OrderComplete - Specify the order complete flag. This flag instructs the system to process the outbound delivery, update the status of all serial numbers and sub-child aggregations, and trigger generation of regulatory reporting messages based on customer configuration.
ShipToCountryCode	`ID`.
ShipFromCountryCode	`ID`.
SaleType	`INCOUNTRYSALE`.
Transactions	Must include at least one or more identifier types.

Web UI

Use Serialized Operations Manager to trigger the Register report from the Web UI. See the Serialized Operations Manager Online Help for more information.

In Track & Trace Services, hover over Modules, and then select Serialized Operations Manager.
Expand the Outbound Movement drop-down, and then select Create Delivery.
Select the manufacturing location that provisioned the serial numbers from the Show Data From drop-down in the upper right.

Complete the fields required for the report as follows:

Field	Values
Delivery Number	Specify the delivery number of the shipment to generate the report for. The Delivery Number must not contain only special characters.
Sale Type	Sale - In Country.
Ship From Country Code	ID (Indonesia).
Ship To Country Code	ID (Indonesia).
From Business	Specify the name or identifier of the company that currently owns the product.
To Business	Specify the name or identifier of the company taking ownership of the product.
Transaction ID	Must include at least one Identifier Type and Identifier Value.

Complete any other fields that are required in the UI or that your company uses for a specific purpose.
Select Submit.
The View Deliveries screen displays.The confirmation message "Delivery [Delivery Number] has been saved." .

Report details

Report Information

Field	Description	Sourced From	BPOM Report Element
Report Type	Displays as Register Parent.	The type of report.	Not reported
Status	The status of the report: Generated – The report is generated in TraceLink but not yet submitted to the BPOM. Generation Failed – The report failed to generate in TraceLink. Accepted – The BPOM received the report successfully and accepted the information. Partially Accepted – The event has multiple reports, and all of them are successfully submitted to the BPOM, but the BPOM did not accept all of the reports. Submitted – The report is generated and successfully submitted to the BPOM. Submission Failed – The report is generated but was not successfully submitted to the BPOM. Rejected – The BPOM received the report successfully but rejected the information.	The status of the report.	Not reported
Event Type	Displays as Shipment.	The type of event.	Not reported
Delivery Number	The delivery number associated with the shipment.	The Delivery Number for the shipment in Serialized Operations Manager.	Not reported
Date Reported	The date and time that the report is generated.	The system date and time when the report is generated.	Not reported