<ROOT>
 <APPS_INITIALIZE_DATA>
  <USER_NAME>ENGINATICS</USER_NAME>
  <RESPONSIBILITY_KEY>SYSTEM_ADMINISTRATOR</RESPONSIBILITY_KEY>
  <APPLICATION_SHORT_NAME>SYSADMIN</APPLICATION_SHORT_NAME>
 </APPS_INITIALIZE_DATA>
<LOVS>
<!-- loader xml for Enginatics Blitz Report lov: HR Operating Unit -->
 <LOVS_ROW>
  <GUID>8E2FF36EDEB979D2E0530100007F1FF2</GUID>
  <LOV_NAME>HR Operating Unit</LOV_NAME>
  <VALIDATE_FROM_LIST>Y</VALIDATE_FROM_LIST>
  <LOV_QUERY>select
hou.name value,
null description
from
hr_operating_units hou
where
sysdate between hou.date_from and nvl(hou.date_to,sysdate) and
(:$flex$.ledger is null or hou.set_of_books_id in (select gl.ledger_id from gl_ledgers gl where xxen_util.contains(:$flex$.ledger,gl.name)=&apos;Y&apos;)) and
hou.organization_id in (select mgoat.organization_id from mo_glob_org_access_tmp mgoat union select fnd_global.org_id from dual where fnd_release.major_version=11)
order by
hou.name</LOV_QUERY>
  <VERSION_COMMENTS>Fixed where clause duplication</VERSION_COMMENTS>
  <LOV_TRANSLATIONS>
   <LOV_TRANSLATIONS_ROW>
    <LANGUAGE>AR</LANGUAGE>
    <DESCRIPTION>وحدة التشغيل مقيدة بالتحكم في الوصول متعدد المنظمات (MOAC)</DESCRIPTION>
   </LOV_TRANSLATIONS_ROW>
   <LOV_TRANSLATIONS_ROW>
    <LANGUAGE>D</LANGUAGE>
    <DESCRIPTION>Bedieneinheit eingeschränkt durch Multi Org Access Control (MOAC)</DESCRIPTION>
   </LOV_TRANSLATIONS_ROW>
   <LOV_TRANSLATIONS_ROW>
    <LANGUAGE>E</LANGUAGE>
    <DESCRIPTION>Unidad operativa restringida por el control de acceso multiorgánico (MOAC)</DESCRIPTION>
   </LOV_TRANSLATIONS_ROW>
   <LOV_TRANSLATIONS_ROW>
    <LANGUAGE>F</LANGUAGE>
    <DESCRIPTION>Unité opérationnelle restreinte par un contrôle d&apos;accès multi-organismes (MOAC)</DESCRIPTION>
   </LOV_TRANSLATIONS_ROW>
   <LOV_TRANSLATIONS_ROW>
    <LANGUAGE>I</LANGUAGE>
    <DESCRIPTION>Unità operativa limitata dal controllo di accesso multiorgano (MOAC)</DESCRIPTION>
   </LOV_TRANSLATIONS_ROW>
   <LOV_TRANSLATIONS_ROW>
    <LANGUAGE>JA</LANGUAGE>
    <DESCRIPTION>多機関アクセス制御(MOAC)で制限された操作ユニット</DESCRIPTION>
   </LOV_TRANSLATIONS_ROW>
   <LOV_TRANSLATIONS_ROW>
    <LANGUAGE>KO</LANGUAGE>
    <DESCRIPTION>다중 조직 액세스 제어 (MOAC)에 의해 제한되는 운영 단위</DESCRIPTION>
   </LOV_TRANSLATIONS_ROW>
   <LOV_TRANSLATIONS_ROW>
    <LANGUAGE>PTB</LANGUAGE>
    <DESCRIPTION>Unidade operacional restrita por controle de acesso multi org (MOAC)</DESCRIPTION>
   </LOV_TRANSLATIONS_ROW>
   <LOV_TRANSLATIONS_ROW>
    <LANGUAGE>RU</LANGUAGE>
    <DESCRIPTION>Операционное устройство, ограниченное мультиорганизованным контролем доступа (MOAC)</DESCRIPTION>
   </LOV_TRANSLATIONS_ROW>
   <LOV_TRANSLATIONS_ROW>
    <LANGUAGE>S</LANGUAGE>
    <DESCRIPTION>Styrenhet begränsad av multi-org access control (MOAC)</DESCRIPTION>
   </LOV_TRANSLATIONS_ROW>
   <LOV_TRANSLATIONS_ROW>
    <LANGUAGE>TR</LANGUAGE>
    <DESCRIPTION>Çoklu kuruluş erişim kontrolü (MOAC) tarafından kısıtlanan işletim birimi</DESCRIPTION>
   </LOV_TRANSLATIONS_ROW>
   <LOV_TRANSLATIONS_ROW>
    <LANGUAGE>US</LANGUAGE>
    <DESCRIPTION>Operating unit restricted by multi org access control (MOAC)</DESCRIPTION>
   </LOV_TRANSLATIONS_ROW>
   <LOV_TRANSLATIONS_ROW>
    <LANGUAGE>ZHS</LANGUAGE>
    <DESCRIPTION>受多机构访问控制（MOAC）限制的操作单元。</DESCRIPTION>
   </LOV_TRANSLATIONS_ROW>
  </LOV_TRANSLATIONS>
 </LOVS_ROW>
<!-- loader xml for Enginatics Blitz Report lov: OKS Contract Number -->
 <LOVS_ROW>
  <GUID>A72A182C50EA2557E0530100007F63D0</GUID>
  <LOV_NAME>OKS Contract Number</LOV_NAME>
  <VALIDATE_FROM_LIST>Y</VALIDATE_FROM_LIST>
  <FILTER_BEFORE_DISPLAY>Y</FILTER_BEFORE_DISPLAY>
  <LOV_QUERY>select
okhab.contract_number value,
okhab.contract_number_modifier||nvl2(okhab.contract_number_modifier,&apos; &apos;,null)||osv0.meaning||&apos;: &apos;||osclv.meaning||&apos; (&apos;||haouv.name||&apos;)&apos; description
from
hr_all_organization_units_vl haouv,
okc_k_headers_b okhab,
okc_statuses_v osv0,
okc_subclasses_v osclv
where
(:$flex$.operating_unit is null or haouv.name=:$flex$.operating_unit) and
okhab.scs_code in (&apos;SERVICE&apos;,&apos;WARRANTY&apos;,&apos;SUBSCRIPTION&apos;) and
haouv.organization_id=okhab.authoring_org_id and
okhab.sts_code=osv0.code(+) and
okhab.scs_code=osclv.code(+)</LOV_QUERY>
  <LOV_TRANSLATIONS>
   <LOV_TRANSLATIONS_ROW>
    <LANGUAGE>US</LANGUAGE>
   </LOV_TRANSLATIONS_ROW>
  </LOV_TRANSLATIONS>
 </LOVS_ROW>
<!-- loader xml for Enginatics Blitz Report lov: OKS Contract Status -->
 <LOVS_ROW>
  <GUID>01EBA8B26251E287E0630100007FDA69</GUID>
  <LOV_NAME>OKS Contract Status</LOV_NAME>
  <VALIDATE_FROM_LIST>Y</VALIDATE_FROM_LIST>
  <LOV_QUERY>select
osv0.meaning value,
count(*) description
from
okc_k_headers_all_b okhab,
okc_statuses_v osv0
where
okhab.authoring_org_id in (select mgoat.organization_id from mo_glob_org_access_tmp mgoat union select fnd_global.org_id from dual where fnd_release.major_version=11) and
okhab.scs_code in (select osb.code from okc_subclasses_b osb where osb.cls_code=&apos;SERVICE&apos;) and
okhab.sts_code=osv0.code
group by
osv0.meaning
order by
osv0.meaning</LOV_QUERY>
  <VERSION_COMMENTS>Fixed bug in operating unit access restriction when the default operating unit is set to something else</VERSION_COMMENTS>
  <LOV_TRANSLATIONS>
   <LOV_TRANSLATIONS_ROW>
    <LANGUAGE>US</LANGUAGE>
   </LOV_TRANSLATIONS_ROW>
  </LOV_TRANSLATIONS>
 </LOVS_ROW>
</LOVS>
<REPORTS>
<!-- loader xml for Enginatics Blitz Report: OKS Service Contracts Billing History -->
 <REPORTS_ROW>
  <GUID>B164E50410B64BF2E0530100007FF40D</GUID><ENABLED>Y</ENABLED>
  <SQL_TEXT>select
haouv.name operating_unit,
ocv.meaning class,
osclv.meaning category,
okhab.contract_number,
okhab.contract_number_modifier modifier,
osv0.meaning contract_status,
osv1.meaning line_status,
osv2.meaning subline_status,
oklb1.line_number||nvl2(oklb2.line_number,&apos;.&apos;||oklb2.line_number,null) line_number,
xxen_util.meaning(nvl(olsb2.lty_code,olsb1.lty_code),&apos;OKC_LINE_TYPE&apos;,0)||&apos; &apos;||xxen_util.meaning(okslb1.usage_type,&apos;OKS_USAGE_TYPES&apos;,0) contract_line_type,
okslb2.base_reading subline_base_reading,
okslb1.usage_period,
rr.name invoice_rule,
rr2.name accounting_rule,
xxen_util.meaning(obcl.bill_action,&apos;OKS_BILL_ACTIONS&apos;,0) bill_action,
obsl.date_billed_from,
obsl.date_billed_to,
obsl.amount,
obsl.manual_credit,
obcl.currency_code,
obsl.average,
obsld.unit_of_measure,
xxen_util.yes(obsld.amcv_yn) amcv_yn,
&amp;counter_cols
obsld.start_reading,
obsld.end_reading,
obsld.fixed,
obsld.actual,
obsld.default_default,
obsld.adjustment_level,
obsld.adjustment_minimum,
obsld.base_reading,
obsld.estimated_quantity,
obsld.result,
obcl.date_next_invoice,
obsl.date_to_interface,
rcta.trx_number,
rcta.trx_date,
xxen_util.meaning(rctta.type,&apos;INV/CM/ADJ&apos;,222)||case when rctta.type=&apos;CM&apos; and obcl.bill_action=&apos;TR&apos; then &apos; termination&apos; end trx_class,
rctta.name trx_type,
rctla.extended_amount trx_line_amount,
okhab.scs_code,
okslb1.usage_type,
olsb1.lty_code,
obcl.bill_action bill_action_code
from
hr_all_organization_units_vl haouv,
okc_k_headers_all_b okhab,
okc_subclasses_v osclv,
okc_classes_v ocv,
okc_statuses_v osv0,
okc_statuses_v osv1,
okc_statuses_v osv2,
okc_k_lines_b oklb1,
okc_k_lines_b oklb2,
oks_k_lines_b okslb1,
oks_k_lines_b okslb2,
okc_line_styles_b olsb1,
okc_line_styles_b olsb2,
ra_rules rr,
ra_rules rr2,
oks_bill_cont_lines obcl,
oks_bill_sub_lines obsl,
oks_bill_sub_line_dtls obsld,
&amp;counter_tbls
oks_bill_transactions obt,
oks_bill_txn_lines obtl,
ra_customer_trx_lines_all rctla,
ra_customer_trx_all rcta,
ra_cust_trx_types_all rctta
where
1=1 and
okhab.authoring_org_id in (select mgoat.organization_id from mo_glob_org_access_tmp mgoat union select fnd_global.org_id from dual where fnd_release.major_version=11) and
okhab.scs_code in (select osb.code from okc_subclasses_b osb where osb.cls_code=&apos;SERVICE&apos;) and
haouv.organization_id= okhab.authoring_org_id and
okhab.scs_code=osclv.code(+) and
osclv.cls_code=ocv.code(+) and
okhab.sts_code=osv0.code(+) and
oklb1.sts_code=osv1.code(+) and
oklb2.sts_code=osv2.code(+) and
okhab.id=oklb1.chr_id and
oklb1.id=oklb2.cle_id(+) and
oklb1.id=okslb1.cle_id and
oklb2.id=okslb2.cle_id(+) and
oklb1.lse_id=olsb1.id and
oklb2.lse_id=olsb2.id(+) and
oklb1.inv_rule_id=rr.rule_id(+) and
okslb1.acct_rule_id=rr2.rule_id(+) and
nvl(oklb2.id,oklb1.id)=obsl.cle_id and
obsl.bcl_id=obcl.id(+) and
obsl.id=obsld.bsl_id(+) and
&amp;counter_joins
obsl.id=obtl.bsl_id(+) and
obtl.btn_id=obt.id(+) and
to_char(obtl.bill_instance_number)=rctla.interface_line_attribute3(+) and
rctla.interface_line_context(+)=&apos;OKS CONTRACTS&apos; and
rctla.customer_trx_id=rcta.customer_trx_id(+) and
rcta.cust_trx_type_id=rctta.cust_trx_type_id(+) and
rcta.org_id=rctta.org_id(+)
order by
haouv.name,
okhab.scs_code,
okhab.contract_number,
okhab.contract_number_modifier,
line_number,
to_number(oklb1.line_number),
to_number(oklb2.line_number),
obsl.date_billed_from desc,
obcl.bill_action desc</SQL_TEXT>
  <REPORT_TRANSLATIONS>
   <REPORT_TRANSLATIONS_ROW>
    <LANGUAGE>AR</LANGUAGE>
    <REPORT_NAME>OKS Service Contracts Billing History</REPORT_NAME>
    <DESCRIPTION>سجل فوترة عقود الخدمة مع قواعد الفواتير والمحاسبة وإجراءات الفواتير وتواريخ فترات الفاتورة والمبالغ وتفاصيل قراءة العداد لفواتير الاستخدام.
عند تشغيل فوترة عقود الخدمة ، توجد دائمًا مجموعة كاملة من السجلات التي تم إنشاؤها في جداول محفوظات الفواتير التالية:

oks_bill_cont_lines obcl
oks_bill_sub_lines
oks_bill_sub_line_dtls obsld
الموافقة على الحصول على المعاملات
oks_bill_txn_lines غير مسموح به

هذه المجموعة من السجلات مكتملة وصولاً إلى مستوى الخط الفرعي القديم / القديم ، بغض النظر عما إذا كان نوع بند العقد المفوتر به خط فرعي أم لا.
بالنسبة إلى سطور الاشتراك (lse_id = 46 ، lty_code = &apos;SUBSCRIPTION&apos;) بدون خط فرعي ، على سبيل المثال ، يشير كل من obcl و obsl إلى cle_id الخاص بهما إلى نفس السطر في okc_k_lines_b بدلاً من سطر مختلف وخط فرعي.

المعرف الفريد لإدخال الفواتير هو obstl.bill_instance_number ، والذي يرتبط بسطر المستحقات rctla.interface_line_attribute3.
عند توجيه الاستعلامات من جانب OKS ، تأكد من تضمين تحويل to_char () من أجل رقم obl.bill_instance_number ، لتمكين استخدام الفهرس في نوع الحرف rctla.interface_line_attribute3.

لا يحتوي سجل فوترة OKS على رابط إلى سجل جدول الفواتير الأصلي في oks_level_elements (راجع https://www.enginatics.com/reports/oks-service-contracts-billing-schedule/)

يمكن العثور على نظرة عامة حول عقود خدمة أوراكل وأنواع الخطوط الأخرى هنا: https://www.enginatics.com/reports/okc-contract-lines-summary/

oks_billing_history_v</DESCRIPTION>
   </REPORT_TRANSLATIONS_ROW>
   <REPORT_TRANSLATIONS_ROW>
    <LANGUAGE>D</LANGUAGE>
    <REPORT_NAME>OKS Service Contracts Billing History</REPORT_NAME>
    <DESCRIPTION>Serviceverträge Abrechnungshistorie mit Fakturierungs- und Abrechnungsregeln, Rechnungsaktion, Daten des abgerechneten Zeitraums, Beträge und Zählerstandsdetails für die Verbrauchsabrechnung.
Bei der Abrechnung von Serviceverträgen wird immer ein vollständiger Satz von Datensätzen in den folgenden Abrechnungshistorientabellen erstellt:

oks_bill_cont_lines obcl
oks_bill_sub_lines obsl
oks_abrechnung_unter_linien_dtls obsld
oks_abrechnung_transaktionen obt
oks_abrechnung_txn_linien obtl

Dieser Satz ist vollständig bis zur Unterzeilenebene obsl/obsld, unabhängig davon, ob die abgerechnete Vertragszeilenart eine Unterzeile hat oder nicht.
Bei Abonnementzeilen (lse_id=46, lty_code=&apos;SUBSCRIPTION&apos;) ohne Unterzeile zeigen z.B. sowohl obcl als auch obsl mit ihrer cle_id auf dieselbe Zeile in okc_k_lines_b statt auf unterschiedliche Zeilen und Unterzeilen.

Eindeutiger Bezeichner für den Rechnungseintrag ist obtl.bill_instance_number, der auf die Forderungszeile rctla.interface_line_attribute3 verweist.
Wenn Sie Abfragen von der OKS-Seite aus steuern, stellen Sie sicher, dass Sie eine to_char()-Konvertierung für die numerische obtl.bill_instance_number einschließen, um die Indexverwendung für den Zeichentyp rctla.interface_line_attribute3 zu ermöglichen.

Die OKS-Abrechnungshistorie hat keine Verknüpfung mit dem verursachenden Abrechnungsplansatz in oks_level_elements (siehe https://www.enginatics.com/reports/oks-service-contracts-billing-schedule/)

Eine Übersicht über Oracle-Serviceverträge und andere Zeilentypen finden Sie hier: https://www.enginatics.com/reports/okc-contract-lines-summary/

oks_abrechnung_historie_v</DESCRIPTION>
   </REPORT_TRANSLATIONS_ROW>
   <REPORT_TRANSLATIONS_ROW>
    <LANGUAGE>E</LANGUAGE>
    <REPORT_NAME>OKS Service Contracts Billing History</REPORT_NAME>
    <DESCRIPTION>Historial de facturación de los contratos de servicios con reglas de facturación y contabilidad, acción de facturación, fechas de los periodos facturados, importes y detalles de los contadores para la facturación del uso.
Cuando se ejecuta la facturación de los contratos de servicios, siempre hay un conjunto completo de registros creados en las siguientes tablas del historial de facturación:

oks_bill_cont_lines obcl
oks_bill_sub_lines obsl
oks_bill_sub_line_dtls obsld
oks_bill_transactions obt
oks_bill_txn_lines obtl

Este conjunto de registros está completo hasta el nivel de sublínea obsl/obsld, independientemente de si el tipo de línea de contrato facturado tiene una sublínea o no.
Para las líneas de suscripción (lse_id=46, lty_code=&apos;SUBSCRIPTION&apos;) sin sublínea, por ejemplo, tanto obcl como obsl apuntan su cle_id a la misma línea en okc_k_lines_b en lugar de a una línea y sublínea diferentes.

El identificador único para la entrada de facturación es obtl.bill_instance_number, que se vincula a la línea de cuentas por cobrar rctla.interface_line_attribute3.
Al realizar consultas desde el lado de OKS, asegúrese de incluir una conversión to_char() para el número numérico obtl.bill_instance_number, para permitir el uso del índice en el tipo de carácter rctla.interface_line_attribute3.

El historial de facturación de OKS no tiene un enlace con el registro del programa de facturación de origen en oks_level_elements (véase https://www.enginatics.com/reports/oks-service-contracts-billing-schedule/)

Una visión general de los contratos de servicio de oracle y otros tipos de línea se puede encontrar aquí: https://www.enginatics.com/reports/okc-contract-lines-summary/

oks_billing_history_v</DESCRIPTION>
   </REPORT_TRANSLATIONS_ROW>
   <REPORT_TRANSLATIONS_ROW>
    <LANGUAGE>F</LANGUAGE>
    <REPORT_NAME>OKS Service Contracts Billing History</REPORT_NAME>
    <DESCRIPTION>Contrats de service - Historique de la facturation avec les règles de facturation et de comptabilité, l&apos;action sur la facture, les dates de la période facturée, les montants et les détails de la lecture du compteur pour la facturation de l&apos;utilisation.
Lors de l&apos;exécution de la facturation des contrats de service, il y a toujours un ensemble complet d&apos;enregistrements créés dans les tableaux d&apos;historique de facturation suivants :

oks_bill_cont_lines obcl
oks_bill_sub_lines obsl
oks_bill_sub_line_dtls obsld
oks_bill_transactions obt
oks_bill_txn_lines obtl

Cet ensemble de données est complet jusqu&apos;au niveau de sous-ligne obsl/obsld, que le type de ligne de contrat facturé comporte ou non une sous-ligne.
Pour les lignes d&apos;abonnement (lse_id=46, lty_code=&apos;SUBSCRIPTION&apos;) sans sous-ligne, par exemple, obcl et obsl font tous deux pointer leur cle_id sur la même ligne dans okc_k_lines_b au lieu d&apos;une ligne et d&apos;une sous-ligne différentes.

L&apos;identifiant unique de l&apos;entrée de facturation est obtl.bill_instance_number, qui renvoie à la ligne de créances rctla.interface_line_attribute3.
Lorsque vous lancez des requêtes du côté OKS, veillez à inclure une conversion to_char() pour le numéro numérique obtl.bill_instance_number, afin de permettre l&apos;utilisation de l&apos;index sur le type de caractère rctla.interface_line_attribute3.

L&apos;historique de facturation OKS n&apos;a pas de lien avec l&apos;enregistrement du calendrier de facturation d&apos;origine dans oks_level_elements (voir https://www.enginatics.com/reports/oks-service-contracts-billing-schedule/)

Un aperçu des contrats de services oracle et d&apos;autres types de lignes peut être trouvé ici : https://www.enginatics.com/reports/okc-contract-lines-summary/

oks_billing_history_v</DESCRIPTION>
   </REPORT_TRANSLATIONS_ROW>
   <REPORT_TRANSLATIONS_ROW>
    <LANGUAGE>I</LANGUAGE>
    <REPORT_NAME>OKS Service Contracts Billing History</REPORT_NAME>
    <DESCRIPTION>Cronologia di fatturazione dei contratti di servizio con regole di fatturazione e contabilità, azioni di fatturazione, date del periodo fatturato, importi e dettagli di lettura del contatore per la fatturazione dell&apos;utilizzo.
Quando si esegue la fatturazione dei contratti di servizio, c&apos;è sempre una serie completa di record creati nelle seguenti tabelle della storia di fatturazione:

oks_bill_cont_lines obcl
oks_bill_sub_lines obsl
oks_bill_sub_line_dtls obsld
oks_bill_transactions obt
oks_bill_txn_lines obtl

Questo insieme di record è completo fino al livello di sublinea obsl/obsld, indipendentemente dal fatto che il tipo di linea contrattuale fatturata abbia o meno una sublinea.
Per le linee di abbonamento (lse_id=46, lty_code=&apos;SUBSCRIPTION&apos;) senza una sottolinea, per esempio, sia obcl che obsl puntano il loro cle_id alla stessa linea in okc_k_lines_b invece di linee e sottolinee diverse.

L&apos;identificatore unico per la voce di fatturazione è obtl.bill_instance_number, che si collega alla linea dei crediti rctla.interface_line_attribute3.
Quando si guidano le query dal lato OKS, assicurarsi di includere una conversione to_char() per il numerico obtl.bill_instance_number, per abilitare l&apos;uso dell&apos;indice sul tipo di carattere rctla.interface_line_attribute3.

La cronologia di fatturazione OKS non ha un collegamento al record del programma di fatturazione originario in oks_level_elements (vedi https://www.enginatics.com/reports/oks-service-contracts-billing-schedule/)

Una panoramica dei contratti di servizio oracle e di altri tipi di linea può essere trovata qui: https://www.enginatics.com/reports/okc-contract-lines-summary/

oks_billing_history_v</DESCRIPTION>
   </REPORT_TRANSLATIONS_ROW>
   <REPORT_TRANSLATIONS_ROW>
    <LANGUAGE>JA</LANGUAGE>
    <REPORT_NAME>OKS Service Contracts Billing History</REPORT_NAME>
    <DESCRIPTION>請求書と会計ルール、請求アクション、請求された期間の日付、金額、および使用料請求のためのカウンター読み取りの詳細を持つサービス契約の請求履歴。
サービス契約の請求を実行すると、以下の請求履歴テーブルに作成されたレコードのフルセットが常に存在します。

oks_bill_cont_lines obcl
oks_bill_sub_lines obsl
oks_bill_sub_line_dtls obsld
oks_bill_transactions obt
oks_bill_txn_lines obtl

このレコードのセットは、請求された契約ライン・タイプにサブラインがあるかどうかに関係なく、サブライン・レベルの obsl/obsld までの完全なレコードです。
例えば、サブラインのないサブスクリプション・ライン (lse_id=46, lty_code=&apos;SUBSCRIPTION&apos;) の場合、obcl と obsl の両方が、異なるラインとサブラインではなく、 okc_k_lines_b の同じラインに cle_id をポイントします。

課金エントリの一意な識別子はobtl.bill_instance_numberで、債権ラインrctla.interface_line_attribute3にリンクしています。
OKS側からクエリを駆動する場合は、文字型rctla.interface_line_attribute3でインデックスを使用できるように、数値のobtl.bill_instance_numberにto_char()変換を必ず含めるようにしてください。

OKSの請求履歴には、 oks_level_elementsの元の請求スケジュールレコードへのリンクがありません（https://www.enginatics.com/reports/oks-service-contracts-billing-schedule/ を参照）。

オラクルのサービス契約およびその他のラインタイプの概要については、こちらをご覧ください: https://www.enginatics.com/reports/okc-contract-lines-summary/

オークス請求履歴</DESCRIPTION>
   </REPORT_TRANSLATIONS_ROW>
   <REPORT_TRANSLATIONS_ROW>
    <LANGUAGE>KO</LANGUAGE>
    <REPORT_NAME>OKS Service Contracts Billing History</REPORT_NAME>
    <DESCRIPTION>인보이스 발행 및 회계 규칙, 청구 조치, 청구 기간 날짜, 금액 및 사용량 청구에 대한 카운터 읽기 세부 사항과 함께 서비스 계약 청구 내역.
서비스 계약 청구를 실행할 때 항상 다음 청구 내역 테이블에 생성 된 전체 레코드 세트가 있습니다.

oks_bill_cont_lines obcl
oks_bill_sub_lines obsl
oks_bill_sub_line_dtls obsld
oks_bill_transactions obt
oks_bill_txn_lines obtl

이 레코드 세트는 청구 된 계약 항목 유형에 하위 항목이 있는지 여부에 관계없이 하위 항목 수준 obsl / obsld까지 완료됩니다.
예를 들어, 서브 라인이없는 구독 라인 (lse_id = 46, lty_code = &apos;SUBSCRIPTION&apos;)의 경우, 예를 들어, obcl과 obsl은 모두 다른 라인과 서브 라인 대신 okc_k_lines_b에서 동일한 라인을 가리키는 cle_id를 가리 킵니다.

청구 항목의 고유 식별자는 obtl.bill_instance_number이며 AR 라인 rctla.interface_line_attribute3에 연결됩니다.
OKS 측에서 쿼리를 구동 할 때 문자 유형 rctla.interface_line_attribute3에서 인덱스 사용을 활성화하려면 숫자 obtl.bill_instance_number에 대한 to_char () 변환을 포함해야합니다.

OKS 청구 내역에는 oks_level_elements의 원래 청구 일정 레코드에 대한 링크가 없습니다 (https://www.enginatics.com/reports/oks-service-contracts-billing-schedule/ 참조).

오라클 서비스 계약 및 기타 라인 유형에 대한 개요는 https://www.enginatics.com/reports/okc-contract-lines-summary/에서 확인할 수 있습니다.

oks_billing_history_v</DESCRIPTION>
   </REPORT_TRANSLATIONS_ROW>
   <REPORT_TRANSLATIONS_ROW>
    <LANGUAGE>PTB</LANGUAGE>
    <REPORT_NAME>OKS Service Contracts Billing History</REPORT_NAME>
    <DESCRIPTION>Histórico de faturamento de contratos de serviço com regras de faturamento e contabilidade, ação de faturamento, datas de períodos faturados, valores e detalhes de leitura do contador para faturamento de uso.
Ao executar o faturamento de contratos de serviço, há sempre um conjunto completo de registros criados nas seguintes tabelas do histórico de faturamento:

oks_bill_cont_lines obcl
oks_bill_sub_lines obsl
oks_bill_sub_line_dtls obsld
oks_bill_transactions obt
oks_bill_txn_lines obtl

Este conjunto de registros é completo até o nível da sub-linha obsl/obsld, independentemente se o tipo de linha de contrato faturado tem uma sub-linha ou não.
Para linhas de assinatura (lse_id=46, lty_code=&apos;SUBSCRIPTION&apos;) sem uma sub-linha, por exemplo, tanto obcl como obsl apontam seu cle_id para a mesma linha em okc_k_lines_b em vez de linha e sub-linha diferentes.

O identificador exclusivo para a entrada de faturamento é obtl.bill_instance_number, que se liga à linha de contas a receber rctla.interface_line_attribute3.
Ao conduzir consultas pelo lado OKS, certifique-se de incluir uma conversão to_char() para o numérico obtl.bill_instance_number, para permitir o uso do índice no tipo de caractere rctla.interface_line_attribute3.

O histórico de faturamento OKS não tem um link para o registro da programação de faturamento de origem em oks_level_elements (ver https://www.enginatics.com/reports/oks-service-contracts-billing-schedule/)

Uma visão geral dos contratos de serviços do oracle e outros tipos de linha pode ser encontrada aqui: https://www.enginatics.com/reports/okc-contract-lines-summary/

oks_billing_history_v</DESCRIPTION>
   </REPORT_TRANSLATIONS_ROW>
   <REPORT_TRANSLATIONS_ROW>
    <LANGUAGE>RU</LANGUAGE>
    <REPORT_NAME>OKS Service Contracts Billing History</REPORT_NAME>
    <DESCRIPTION>История выставления счетов по сервисным контрактам с правилами выставления счетов и учета, действием счетов, датами выставления счетов, суммами и деталями показаний счетчиков для выставления счетов за использование.
При выставлении счетов по сервисным договорам всегда имеется полный набор записей, созданный в следующих таблицах истории выставления счетов:

oks_bill_cont_lines obcl
oks_bill_sub_lines obsl
oks_bill_sub_line_dtls obsld
oks_bill_transactions obt
oks_bill_txn_lines obtl

Этот набор записей является полным вплоть до уровня подлиний обсл/объединения, независимо от того, есть ли у типа контрактной линии, для которой выставляется счет, подлиния или нет.
Например, для подписных линий (lse_id=46, lty_code=&apos;SUBSCRIPTION&apos;) без подстроки, как obcl, так и obsl указывают свою cle_id на одну и ту же строку в okc_k_lines_b вместо разных строк и подстрок.

Уникальным идентификатором для биллинговой записи является obtl.bill_instance_number, который ссылается на строку дебиторской задолженности rctla.interface_line_attribute3.
При управлении запросами со стороны OKS убедитесь, что для числового obtl.bill_instance_number включено преобразование с помощью функции to_char(), чтобы включить использование индекса на символьном типе rctla.interface_line_attribute3.

История биллинга OKS не имеет ссылки на исходящую запись расписания биллинга в oks_level_elements (см. https://www.enginatics.com/reports/oks-service-contracts-billing-schedule/).

Обзор договоров на предоставление услуг oracle и других типов линий можно найти здесь: https://www.enginatics.com/reports/okc-contract-lines-summary/.

oks_billing_history_v</DESCRIPTION>
   </REPORT_TRANSLATIONS_ROW>
   <REPORT_TRANSLATIONS_ROW>
    <LANGUAGE>S</LANGUAGE>
    <REPORT_NAME>OKS Service Contracts Billing History</REPORT_NAME>
    <DESCRIPTION>Servicekontrakt faktureringshistorik med fakturerings- och bokföringsregler, fakturahantering, fakturerade perioddatum, belopp och kontraläsningsinformation för användningsfakturering.
När du kör fakturering av servicekontrakt skapas alltid en fullständig uppsättning poster i följande fakturahistoriktabeller:

oks_bill_cont_lines obcl
oks_bill_sub_lines obsl
oks_bill_sub_line_dtls obsld
oks_bill_transactions obt
oks_bill_txn_lines obtl

Den här uppsättningen poster är fullständig ned till underradenivå obsl / obsld, oavsett om den fakturerade kontraktsraden har en underrad eller inte.
För prenumerationsrader (lse_id = 46, lty_code = &apos;SUBSCRIPTION&apos;) utan till exempel underlinje riktar både obcl och obsl sin cle_id till samma rad i okc_k_lines_b istället för olika rader och underrader.

Den unika identifieraren för faktureringsposten är obtl.bill_instance_number, som länkar till fordonsrad rctla.interface_line_attribute3.
När du kör frågor från OKS-sidan, se till att inkludera en to_char () -konvertering för det numeriska obtl.bill_instance_number för att möjliggöra indexanvändning på teckentyp rctla.interface_line_attribute3.

OKS-faktureringshistoriken har ingen länk till den ursprungliga faktureringsplanposten i oks_level_elements (se https://www.enginatics.com/reports/oks-service-contracts-billing-schedule/)

En översikt över oracle-serviceavtal och andra linjetyper hittar du här: https://www.enginatics.com/reports/okc-contract-lines-summary/

oks_billing_history_v</DESCRIPTION>
   </REPORT_TRANSLATIONS_ROW>
   <REPORT_TRANSLATIONS_ROW>
    <LANGUAGE>TR</LANGUAGE>
    <REPORT_NAME>OKS Service Contracts Billing History</REPORT_NAME>
    <DESCRIPTION>Faturalama ve muhasebe kuralları, fatura işlemi, fatura dönemi tarihleri, tutarlar ve kullanım faturalandırması için sayaç okuma ayrıntılarıyla birlikte Servis Sözleşmeleri fatura geçmişi.
Hizmet sözleşmeleri faturalandırması çalıştırılırken, aşağıdaki faturalama geçmişi tablolarında her zaman tam bir kayıt kümesi oluşturulur:

oks_bill_cont_lines obcl
oks_bill_sub_lines obsl
oks_bill_sub_line_dtls obsld
oks_bill_transactions obt
oks_bill_txn_lines obtl

Bu kayıt seti, faturalandırılan sözleşme satırı türünün bir alt satırı olup olmadığına bakılmaksızın, alt satır düzeyinde obsl / obsld&apos;ye kadar tamamlanmıştır.
Alt satırı olmayan abonelik satırları (lse_id = 46, lty_code = &apos;SUBSCRIPTION&apos;) için, örneğin, hem obcl hem de obsl cle_id&apos;lerini farklı satır ve alt satır yerine okc_k_lines_b&apos;deki aynı satıra işaret eder.

Faturalama girişi için benzersiz tanımlayıcı, alacaklar satırına rctla.interface_line_attribute3 bağlanan obtl.bill_instance_number&apos;dır.
OKS tarafından sorgu çalıştırırken, rctla.interface_line_attribute3 karakter türünde dizin kullanımını etkinleştirmek için sayısal obtl.bill_instance_number için bir to_char () dönüşümü eklediğinizden emin olun.

OKS faturalama geçmişinin oks_level_elements&apos;taki kaynak faturalandırma programı kaydına bir bağlantısı yoktur (bkz. Https://www.enginatics.com/reports/oks-service-contracts-billing-schedule/)

Oracle hizmet sözleşmelerine ve diğer hat türlerine genel bir bakış burada bulunabilir: https://www.enginatics.com/reports/okc-contract-lines-summary/

oks_billing_history_v</DESCRIPTION>
   </REPORT_TRANSLATIONS_ROW>
   <REPORT_TRANSLATIONS_ROW>
    <LANGUAGE>US</LANGUAGE>
    <REPORT_NAME>OKS Service Contracts Billing History</REPORT_NAME>
    <DESCRIPTION>Service Contracts billing history with invoicing and accounting rules, bill action, billed period dates, amounts and counter reading details for usage billing.
When running service contracts billing, there is always a full set of records created in the following billing history tables: 

oks_bill_cont_lines obcl
oks_bill_sub_lines obsl
oks_bill_sub_line_dtls obsld
oks_bill_transactions obt
oks_bill_txn_lines obtl

This set of records is complete down to subline level obsl/obsld, regardless if the billed contract line type has a subline or not.
For subscription lines (lse_id=46, lty_code=&apos;SUBSCRIPTION&apos;) without a subline, for example, both obcl and obsl point their cle_id to the same line in okc_k_lines_b instead of different line and subline.

Unique identifier for the billing entry is obtl.bill_instance_number, which links to receivables line rctla.interface_line_attribute3.
When driving queries from the OKS side, make sure to include a to_char() conversion for the numeric obtl.bill_instance_number, to enable index use on character type rctla.interface_line_attribute3.

The OKS billing history does not have a link to the originating billing schedule record in oks_level_elements (see https://www.enginatics.com/reports/oks-service-contracts-billing-schedule/)

An overview of oracle service contracts and other line types can be found here: https://www.enginatics.com/reports/okc-contract-lines-summary/

oks_billing_history_v</DESCRIPTION>
   </REPORT_TRANSLATIONS_ROW>
   <REPORT_TRANSLATIONS_ROW>
    <LANGUAGE>ZHS</LANGUAGE>
    <REPORT_NAME>OKS Service Contracts Billing History</REPORT_NAME>
    <DESCRIPTION>服务合同计费历史记录，包括开票和核算规则、账单动作、计费期日期、金额和计数器读数等使用计费细节。
在运行服务合同计费时，总会在以下计费历史表中建立一套完整的记录。

oks_bill_cont_lines obcl
OKS_bill_sub_line obsl
oks_bill_sub_line_dtls obsld
oks_bill_transactions obt.
oks_bill_txn_lines obtl。

这组记录是完整的，直到子行级别的obsl/obsld，不管出单合同行类型是否有子行。
例如，对于没有子行的订购行(lse_id=46, lty_code=&apos;SUBSCRIPTION&apos;)，obcl和obsl都将其cle_id指向okc_k_lines_b中的同一行，而不是不同的行和子行。

账单条目的唯一标识符是obtl.bill_instance_number，它链接到应收账款行rctla.interface_line_attribute3。
当从OKS端驱动查询时，一定要为数字obtl.bill_instance_number包含一个to_char()转换，以实现对字符类型rctla.interface_line_attribute3的索引使用。

OKS计费历史记录没有链接到oks_level_elements中的原始计费表记录（见https://www.enginatics.com/reports/oks-service-contracts-billing-schedule/）。

关于oracle服务合同和其他线路类型的概述可以在这里找到：https://www.enginatics.com/reports/okc-contract-lines-summary/。

oks_billing_history_v。</DESCRIPTION>
   </REPORT_TRANSLATIONS_ROW>
  </REPORT_TRANSLATIONS>
  <CATEGORY_ASSIGNMENTS>
   <CATEGORY_ASSIGNMENTS_ROW>
    <CATEGORY>Enginatics</CATEGORY>
   </CATEGORY_ASSIGNMENTS_ROW>
  </CATEGORY_ASSIGNMENTS>
  <ANCHORS>
   <ANCHORS_ROW>
    <ANCHOR>&amp;counter_cols</ANCHOR>
   </ANCHORS_ROW>
   <ANCHORS_ROW>
    <ANCHOR>&amp;counter_joins</ANCHOR>
   </ANCHORS_ROW>
   <ANCHORS_ROW>
    <ANCHOR>&amp;counter_tbls</ANCHOR>
   </ANCHORS_ROW>
   <ANCHORS_ROW>
    <ANCHOR>1=1</ANCHOR>
   </ANCHORS_ROW>
  </ANCHORS>
  <PARAMETERS>
   <PARAMETERS_ROW>
    <SORT_ORDER>1</SORT_ORDER>
    <DISPLAY_SEQUENCE>-10</DISPLAY_SEQUENCE>
    <ANCHOR>&amp;counter_cols</ANCHOR>
    <SQL_TEXT>cccg.name counter_group,
ccr.value_timestamp,</SQL_TEXT>
    <PARAMETER_TYPE_DSP>Char</PARAMETER_TYPE_DSP>
    <MATCHING_VALUE>12</MATCHING_VALUE>
    <DEFAULT_VALUE>select decode(fnd_release.major_version,&apos;11&apos;,&apos;11&apos;,&apos;12&apos;)
from dual</DEFAULT_VALUE>
    <PARAMETER_TRANSLATIONS>
     <PARAMETER_TRANSLATIONS_ROW>
      <LANGUAGE>US</LANGUAGE>
      <PARAMETER_NAME>EBS Release Version</PARAMETER_NAME>
     </PARAMETER_TRANSLATIONS_ROW>
    </PARAMETER_TRANSLATIONS>
   </PARAMETERS_ROW>
   <PARAMETERS_ROW>
    <SORT_ORDER>2</SORT_ORDER>
    <ANCHOR>&amp;counter_joins</ANCHOR>
    <SQL_TEXT>obsld.ccr_id=ccr.counter_value_id(+) and
obsld.cgr_id=cccg.counter_group_id(+) and</SQL_TEXT>
    <MATCHING_VALUE>12</MATCHING_VALUE>
    <PARAMETER_TRANSLATIONS>
     <PARAMETER_TRANSLATIONS_ROW>
      <LANGUAGE>US</LANGUAGE>
      <PARAMETER_NAME>EBS Release Version</PARAMETER_NAME>
     </PARAMETER_TRANSLATIONS_ROW>
    </PARAMETER_TRANSLATIONS>
   </PARAMETERS_ROW>
   <PARAMETERS_ROW>
    <SORT_ORDER>3</SORT_ORDER>
    <ANCHOR>&amp;counter_tbls</ANCHOR>
    <SQL_TEXT>csi_counter_readings ccr,
cs_csi_counter_groups cccg,</SQL_TEXT>
    <MATCHING_VALUE>12</MATCHING_VALUE>
    <PARAMETER_TRANSLATIONS>
     <PARAMETER_TRANSLATIONS_ROW>
      <LANGUAGE>US</LANGUAGE>
      <PARAMETER_NAME>EBS Release Version</PARAMETER_NAME>
     </PARAMETER_TRANSLATIONS_ROW>
    </PARAMETER_TRANSLATIONS>
   </PARAMETERS_ROW>
   <PARAMETERS_ROW>
    <SORT_ORDER>4</SORT_ORDER>
    <DISPLAY_SEQUENCE>10</DISPLAY_SEQUENCE>
    <ANCHOR>1=1</ANCHOR>
    <SQL_TEXT>haouv.name=:operating_unit</SQL_TEXT>
    <PARAMETER_TYPE_DSP>LOV</PARAMETER_TYPE_DSP>
    <LOV_NAME>HR Operating Unit</LOV_NAME>
    <LOV_GUID>8E2FF36EDEB979D2E0530100007F1FF2</LOV_GUID>
    <VALIDATE_FROM_LIST_DSP>Y</VALIDATE_FROM_LIST_DSP>
    <LOV_QUERY_DSP>select
hou.name value,
null description
from
hr_operating_units hou
where
sysdate between hou.date_from and nvl(hou.date_to,sysdate) and
(:$flex$.ledger is null or hou.set_of_books_id in (select gl.ledger_id from gl_ledgers gl where xxen_util.contains(:$flex$.ledger,gl.name)=&apos;Y&apos;)) and
hou.organization_id in (select mgoat.organization_id from mo_glob_org_access_tmp mgoat union select fnd_global.org_id from dual where fnd_release.major_version=11)
order by
hou.name</LOV_QUERY_DSP>
    <DEFAULT_VALUE>coalesce(xxen_util.default_operating_unit,xxen_util.previous_parameter_value(:parameter_id))</DEFAULT_VALUE>
    <PARAMETER_TRANSLATIONS>
     <PARAMETER_TRANSLATIONS_ROW>
      <LANGUAGE>US</LANGUAGE>
      <PARAMETER_NAME>Operating Unit</PARAMETER_NAME>
     </PARAMETER_TRANSLATIONS_ROW>
    </PARAMETER_TRANSLATIONS>
   </PARAMETERS_ROW>
   <PARAMETERS_ROW>
    <SORT_ORDER>5</SORT_ORDER>
    <DISPLAY_SEQUENCE>20</DISPLAY_SEQUENCE>
    <ANCHOR>1=1</ANCHOR>
    <SQL_TEXT>okhab.contract_number=:contract_nunber</SQL_TEXT>
    <PARAMETER_TYPE_DSP>LOV</PARAMETER_TYPE_DSP>
    <LOV_NAME>OKS Contract Number</LOV_NAME>
    <LOV_GUID>A72A182C50EA2557E0530100007F63D0</LOV_GUID>
    <VALIDATE_FROM_LIST_DSP>Y</VALIDATE_FROM_LIST_DSP>
    <FILTER_BEFORE_DISPLAY_DSP>Y</FILTER_BEFORE_DISPLAY_DSP>
    <LOV_QUERY_DSP>select
okhab.contract_number value,
okhab.contract_number_modifier||nvl2(okhab.contract_number_modifier,&apos; &apos;,null)||osv0.meaning||&apos;: &apos;||osclv.meaning||&apos; (&apos;||haouv.name||&apos;)&apos; description
from
hr_all_organization_units_vl haouv,
okc_k_headers_b okhab,
okc_statuses_v osv0,
okc_subclasses_v osclv
where
(:$flex$.operating_unit is null or haouv.name=:$flex$.operating_unit) and
okhab.scs_code in (&apos;SERVICE&apos;,&apos;WARRANTY&apos;,&apos;SUBSCRIPTION&apos;) and
haouv.organization_id=okhab.authoring_org_id and
okhab.sts_code=osv0.code(+) and
okhab.scs_code=osclv.code(+)</LOV_QUERY_DSP>
    <PARAMETER_TRANSLATIONS>
     <PARAMETER_TRANSLATIONS_ROW>
      <LANGUAGE>US</LANGUAGE>
      <PARAMETER_NAME>Contract Number</PARAMETER_NAME>
     </PARAMETER_TRANSLATIONS_ROW>
    </PARAMETER_TRANSLATIONS>
   </PARAMETERS_ROW>
   <PARAMETERS_ROW>
    <SORT_ORDER>6</SORT_ORDER>
    <DISPLAY_SEQUENCE>30</DISPLAY_SEQUENCE>
    <ANCHOR>1=1</ANCHOR>
    <SQL_TEXT>okhab.contract_number_modifier=:modifier</SQL_TEXT>
    <PARAMETER_TYPE_DSP>LOV custom</PARAMETER_TYPE_DSP>
    <VALIDATE_FROM_LIST_DSP>Y</VALIDATE_FROM_LIST_DSP>
    <LOV_QUERY_DSP>select
okhab.contract_number_modifier value,
null description
from
okc_k_headers_b okhab
where
okhab.contract_number=:$flex$.contract_number
order by
okhab.creation_date desc</LOV_QUERY_DSP>
    <PARAMETER_TRANSLATIONS>
     <PARAMETER_TRANSLATIONS_ROW>
      <LANGUAGE>US</LANGUAGE>
      <PARAMETER_NAME>Modifier</PARAMETER_NAME>
     </PARAMETER_TRANSLATIONS_ROW>
    </PARAMETER_TRANSLATIONS>
   </PARAMETERS_ROW>
   <PARAMETERS_ROW>
    <SORT_ORDER>7</SORT_ORDER>
    <DISPLAY_SEQUENCE>40</DISPLAY_SEQUENCE>
    <ANCHOR>1=1</ANCHOR>
    <SQL_TEXT>osv0.meaning=:contract_status</SQL_TEXT>
    <PARAMETER_TYPE_DSP>LOV</PARAMETER_TYPE_DSP>
    <LOV_NAME>OKS Contract Status</LOV_NAME>
    <LOV_GUID>01EBA8B26251E287E0630100007FDA69</LOV_GUID>
    <VALIDATE_FROM_LIST_DSP>Y</VALIDATE_FROM_LIST_DSP>
    <LOV_QUERY_DSP>select
osv0.meaning value,
count(*) description
from
okc_k_headers_all_b okhab,
okc_statuses_v osv0
where
okhab.authoring_org_id in (select mgoat.organization_id from mo_glob_org_access_tmp mgoat union select fnd_global.org_id from dual where fnd_release.major_version=11) and
okhab.scs_code in (select osb.code from okc_subclasses_b osb where osb.cls_code=&apos;SERVICE&apos;) and
okhab.sts_code=osv0.code
group by
osv0.meaning
order by
osv0.meaning</LOV_QUERY_DSP>
    <PARAMETER_TRANSLATIONS>
     <PARAMETER_TRANSLATIONS_ROW>
      <LANGUAGE>US</LANGUAGE>
      <PARAMETER_NAME>Contract Status</PARAMETER_NAME>
     </PARAMETER_TRANSLATIONS_ROW>
    </PARAMETER_TRANSLATIONS>
   </PARAMETERS_ROW>
   <PARAMETERS_ROW>
    <SORT_ORDER>8</SORT_ORDER>
    <DISPLAY_SEQUENCE>50</DISPLAY_SEQUENCE>
    <ANCHOR>1=1</ANCHOR>
    <SQL_TEXT>osv0.meaning&lt;&gt;:exclude_contract_status</SQL_TEXT>
    <PARAMETER_TYPE_DSP>LOV</PARAMETER_TYPE_DSP>
    <LOV_NAME>OKS Contract Status</LOV_NAME>
    <LOV_GUID>01EBA8B26251E287E0630100007FDA69</LOV_GUID>
    <VALIDATE_FROM_LIST_DSP>Y</VALIDATE_FROM_LIST_DSP>
    <LOV_QUERY_DSP>select
osv0.meaning value,
count(*) description
from
okc_k_headers_all_b okhab,
okc_statuses_v osv0
where
okhab.authoring_org_id in (select mgoat.organization_id from mo_glob_org_access_tmp mgoat union select fnd_global.org_id from dual where fnd_release.major_version=11) and
okhab.scs_code in (select osb.code from okc_subclasses_b osb where osb.cls_code=&apos;SERVICE&apos;) and
okhab.sts_code=osv0.code
group by
osv0.meaning
order by
osv0.meaning</LOV_QUERY_DSP>
    <PARAMETER_TRANSLATIONS>
     <PARAMETER_TRANSLATIONS_ROW>
      <LANGUAGE>US</LANGUAGE>
      <PARAMETER_NAME>Exclude Contract Status</PARAMETER_NAME>
     </PARAMETER_TRANSLATIONS_ROW>
    </PARAMETER_TRANSLATIONS>
   </PARAMETERS_ROW>
   <PARAMETERS_ROW>
    <SORT_ORDER>9</SORT_ORDER>
    <DISPLAY_SEQUENCE>60</DISPLAY_SEQUENCE>
    <ANCHOR>1=1</ANCHOR>
    <SQL_TEXT>obsl.creation_date&gt;=:billed_from</SQL_TEXT>
    <PARAMETER_TYPE_DSP>Date</PARAMETER_TYPE_DSP>
    <PARAMETER_TRANSLATIONS>
     <PARAMETER_TRANSLATIONS_ROW>
      <LANGUAGE>US</LANGUAGE>
      <PARAMETER_NAME>Billed From</PARAMETER_NAME>
     </PARAMETER_TRANSLATIONS_ROW>
    </PARAMETER_TRANSLATIONS>
   </PARAMETERS_ROW>
   <PARAMETERS_ROW>
    <SORT_ORDER>10</SORT_ORDER>
    <DISPLAY_SEQUENCE>70</DISPLAY_SEQUENCE>
    <ANCHOR>1=1</ANCHOR>
    <SQL_TEXT>obsl.creation_date&lt;:billed_to+1</SQL_TEXT>
    <PARAMETER_TYPE_DSP>Date</PARAMETER_TYPE_DSP>
    <DEFAULT_VALUE>last_day(:$flex$.billed_from)</DEFAULT_VALUE>
    <PARAMETER_TRANSLATIONS>
     <PARAMETER_TRANSLATIONS_ROW>
      <LANGUAGE>US</LANGUAGE>
      <PARAMETER_NAME>Billed To</PARAMETER_NAME>
     </PARAMETER_TRANSLATIONS_ROW>
    </PARAMETER_TRANSLATIONS>
   </PARAMETERS_ROW>
   <PARAMETERS_ROW>
    <SORT_ORDER>11</SORT_ORDER>
    <DISPLAY_SEQUENCE>80</DISPLAY_SEQUENCE>
    <ANCHOR>1=1</ANCHOR>
    <SQL_TEXT>obcl.bill_action=xxen_util.lookup_code(:bill_action,&apos;OKS_BILL_ACTIONS&apos;,0)</SQL_TEXT>
    <PARAMETER_TYPE_DSP>LOV custom</PARAMETER_TYPE_DSP>
    <VALIDATE_FROM_LIST_DSP>Y</VALIDATE_FROM_LIST_DSP>
    <LOV_QUERY_DSP>select
flvv.meaning value,
flvv.description
from
fnd_lookup_values_vl flvv
where
flvv.lookup_type=&apos;OKS_BILL_ACTIONS&apos; and
flvv.view_application_id=0 and
flvv.security_group_id=0
order by
flvv.meaning</LOV_QUERY_DSP>
    <PARAMETER_TRANSLATIONS>
     <PARAMETER_TRANSLATIONS_ROW>
      <LANGUAGE>US</LANGUAGE>
      <PARAMETER_NAME>Bill Action</PARAMETER_NAME>
     </PARAMETER_TRANSLATIONS_ROW>
    </PARAMETER_TRANSLATIONS>
   </PARAMETERS_ROW>
  </PARAMETERS>
  <PARAMETER_DEPENDENCIES>
   <PARAMETER_DEPENDENCIES_ROW>
    <FLEX_BIND>:$flex$.billed_from</FLEX_BIND>
    <PARAMETER_NAME>Billed From</PARAMETER_NAME>
    <IS_DATE>Y</IS_DATE>
    <DEPENDENT_PARAMETER_NAME>Billed To</DEPENDENT_PARAMETER_NAME>
   </PARAMETER_DEPENDENCIES_ROW>
   <PARAMETER_DEPENDENCIES_ROW>
    <FLEX_BIND>:$flex$.contract_number</FLEX_BIND>
    <PARAMETER_NAME>Contract Number</PARAMETER_NAME>
    <DEPENDENT_PARAMETER_NAME>Modifier</DEPENDENT_PARAMETER_NAME>
   </PARAMETER_DEPENDENCIES_ROW>
   <PARAMETER_DEPENDENCIES_ROW>
    <FLEX_BIND>:$flex$.operating_unit</FLEX_BIND>
    <PARAMETER_NAME>Operating Unit</PARAMETER_NAME>
    <DEPENDENT_PARAMETER_NAME>Contract Number</DEPENDENT_PARAMETER_NAME>
   </PARAMETER_DEPENDENCIES_ROW>
  </PARAMETER_DEPENDENCIES>
  <TEMPLATES>
  </TEMPLATES>
  <DEFAULT_TEMPLATES>
  </DEFAULT_TEMPLATES>
  <UPLOAD_COLUMNS>
  </UPLOAD_COLUMNS>
  <UPLOAD_PARAMETERS>
  </UPLOAD_PARAMETERS>
  <UPLOAD_SQLS>
  </UPLOAD_SQLS>
  <UPLOAD_DEPENDENCIES>
  </UPLOAD_DEPENDENCIES>
 </REPORTS_ROW>
</REPORTS>
</ROOT>
