Proxy GL Info Records
When a charge and grant are in separate events, the activation event has a GL info record that references the purchased asset, but does not reference any charged balances. This is known as a proxy GL info record.
A proxy GL info record is a placeholder for the charges, discounts, and taxes in the purchase event that have a revenue recognition type of pending. At activation time, if a purchase event has a GL info record with a revenue recognition type field value of 5 (pending), a proxy GL info record is generated so that the GL processor can recognize revenue for purchase-time charges that pay for activation grants that begin at activation time. If a purchased item is never activated, a proxy GL info record is generated in the cancelation event.
When a charge and the grant for which it pays are in separate events, the proxy GL info record in the activation event references any purchased assets, but does not reference any charged balances. The proxy GL info record substitutes for the charges, discounts, and taxes in the purchase event that have a revenue recognition type of pending. Proxy GL info records indicate the revenue recognition type (immediate, per-day, or consumption-based), determined at activation time based on the asset granted.
If charges do not pay for any grants at activation, the proxy GL info record has null
references for both the charged balance and the purchased asset. The
AssetBalanceUpdateIndex and AssetAmount fields are
not set. The TxnType field in these records is always 0, and the
amount is always 0.0. When the Account1,
Account2, Amount, and UpdateType
fields are not set, that indicates that the record is a proxy GL info record.
For more information about these fields, see the discussion about MtxEventGlInfo in MATRIXX Subscriber Management.
In purchase events for bundles, a proxy GL info record is generated for
each product offer in the bundle for which there are charges, discounts, or
taxes in the purchase event with a revenue recognition type of
pending. The GL processor uses the offer
resourceId in applied offer records in the events to
determine which charges in the purchase event pay for the asset referenced by
the proxy GL info record. The GL info records in the purchase event whose
applied offer have the same
resourceId as the applied offer for the proxy GL info
record are the charges represented by the proxy GL info record.
If purchase charges are paid for by a group of which the event initiator is a member (a sponsored purchase charge), separate secondary events are generated at purchase time for each sponsor. If purchase events with the sponsored charges have GL info records with a revenue recognition type of pending, then the proxy GL info records generated at activation or cancelation time are included in the secondary events generated for the sponsor. If there are no sponsored charges as part of the activation or cancelation, then secondary events are generated specifically to hold the proxy GL info records which reference the primary event. In this case, the secondary event does not have balance update records or charge records.
In cancelation events, proxy GL info records for purchase charges do not reference a purchased asset, even if an asset is granted as part of the cancelation. The revenue recognition type for the proxy GL info records in cancelation events is always immediate. For more information about canceled pre-active purchased items, see the discussion about pre-active purchased item cancelation.
A proxy GL info record can be for a product offer for which no component is applied during activation or cancelation. In this case, an applied offer record is added to the activation or cancelation event specifically for the proxy GL info record. In this situation, there are no charge records in the event that reference the applied offer record. The applied offer is referenced only from the proxy GL info record.