Release path
1.0.1Published Mar 4, 2026PackagePublished package
@pasar6987/sf-revenue-payment
Payment schedule construction with policy-driven treatment details, distribution methods, term definitions, and batch payment run processing.
OSISchema 0.1.1Domain crmSource developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference
Published package · Latest published 1.0.1 Mar 4, 2026 · 10 datasets / 26 measures in the latest review · Updated Mar 11, 2026
Publisher
@pasar6987Published Mar 4, 2026Structure snapshot
10 datasets26 measures · 105 dimensionsSemantic Graph
Relationship counts appear after the graph loads.
Loading graph
Package graph is loadingPackage relationships will appear when the summary is ready.
Reference context
Secondary package facts stay compact
- Updated
- Mar 11, 2026
- Visibility
- Public hub listing
- License
- MIT
- Created
- Mar 4, 2026
Reference facts
Secondary package facts after the usage path is clear
Licensing, categorization, ownership, and linked metadata stay below the runnable path so the page reads in the right order.
Format
OSI
Upstream
developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference
Repository
Not linked
Domain
Source
Owner
@pasar6987Organization
Independent
License
MIT
Visibility
Public hub listing
Publisher
@pasar6987Published Mar 4, 2026
Latest published version
1.0.1Published Mar 4, 2026
Tags
Schema preview
Schema 0.1.1
SDK handoff
Use this package in code and AI
After structure review, move straight into typed reads with load() or compact LLM context with to_prompt().
Python SDK
Python example for @pasar6987/sf-revenue-payment
This example uses the current package ref and, when preview data is available, fills in real dataset names from the published summary.
import rawctx
model = rawctx.load("@pasar6987/sf-revenue-payment")
prompt = rawctx.to_prompt(
"@pasar6987/sf-revenue-payment",
datasets=["PaymentBatchRun", "PaymentLineInvoiceLine"],
max_tokens=2000,
)
print(model.datasets) # ["PaymentBatchRun", "PaymentLineInvoiceLine", "PaymentSchedule"]
print(model.measures) # [Measure(name="PaymentBatchRun.TotalFailedScheduleItems", ...), Measure(name="PaymentBatchRun.TotalFilteredScheduleItems", ...), Measure(name="PaymentBatchRun.TotalProcessedScheduleItems", ...)]
print(model.dimensions) # [Dimension(name="BillingBatchSchedulerId", ...), Dimension(name="Comments", ...), Dimension(name="CompletionTime", ...)]
print(model.relationships) # [Relationship(name='...', ...)]
print(prompt)README
Package narrative and examples
Use documentation after the package clears provenance, ownership, and runnable-path checks.
@pasar6987/sf-revenue-payment
Payment schedule construction with policy-driven treatment details, distribution methods, term definitions, and batch payment run processing.
Overview
| Count | |
|---|---|
| Objects (Datasets) | 10 |
| Dimensions | 105 |
| Measures | 26 |
| Relationships | 0 |
Objects
- PaymentBatchRun — Represents a batch processing job that processes payments in Billing. During a payment batch run, all the payment schedules that meet the specified criteria are processed and the corresponding Payment records are created. These payments are then applied to invoices or invoice lines.
- PaymentLineInvoiceLine — Represents information about a payment line that's applied to or unapplied from an invoice line.
- PaymentSchedule — Represents information about a set of payments that a customer wants to collect at different times for a certain record. A schedule contains one or more payment schedule items, where each item represents one payment to be processed. Each of a schedule’s items can have different payment configuration fields, such as payment methods, payment dates, and payment accounts. When a payment scheduler launches a payment run, the run evaluates active payment schedule items, and picks them up for payment processing if they match the scheduler’s payment criteria.
- PaymentScheduleItem — Represents information about a payment to be processed. Each schedule item can have different payment configuration fields, such as payment methods, payment dates, and payment accounts. When a payment scheduler launches a payment run, the run evaluates active payment schedule items, and picks them up for payment processing if they match the scheduler’s payment criteria.
- PaymentSchedulePolicy — Represents information about the configuration for the payment schedule.
- PaymentScheduleTreatment — Represents information about the processing of payment schedules including the payment method and the payment amount for the payment schedule.
- PaymentScheduleTreatmentDtl — Represents information about the processing of payment schedules after the corresponding invoices are posted.
- PaymentTerm — Represents an agreement between a buyer and a seller about when payment is due for an invoice.
- PaymentTermItem — Represents configuration of a payment term.
- PymtSchdDistributionMethod — Represents information about the partial payments that the total payment is divided into.
Install
rawctx snapshot-download @pasar6987/sf-revenue-payment
Structure review
Inspect package structure after the usage path is clear
Use the structural review when you need the package footprint, field counts, and model paths before a deeper explorer pass.
models/sf-revenue-payment.osi.yamlAI context included
10 datasets26 measures105 dimensions0 relationships