Archived System CR SCR013102-13 Detail |
| Title: LSOG 6 Issue 1825: Add Revenue Accounting Code (RAO) to LSR | |||||
| CR Number |
Current Status Date |
Level of Effort |
Interface/ Release No. |
Area Impacted |
Products Impacted |
|
|
|||||
| SCR013102-13 |
Withdrawn 3/3/2003 |
2800 - 4675 | 3/ | Funtional Impact not product impact | |
| Originator: Zimmerman, Carol |
| Originator Company Name: Qwest Corporation |
| Owner: Winston, Connie |
| Director: |
| CR PM: Stecklein, Lynn |
| Description Of Change |
|
OBF issue 1825 seeks to add a new data element to several practices to identify a Billing Service Provider's Revenue Account Code (RAO) so that calls can be billed to the approprieate Local Service Provider (LSP). Additionally, data populated in this field will be utilized to update LIDB data information. If this issue is not implemented calls may not be correctly identified.
|
Status History |
| Date | Action | Description |
| 1/31/2002 | CR Submitted | |
| 1/31/2002 | CR Acknowledged | |
| 2/7/2002 | Status Changed | Status changed to clarification. |
| 2/7/2002 | LOE Issued | The LOE is Medium. |
| 2/21/2002 | Discussed at Monthly CMP Meeting | SCR013102-13 discussed during 'New Qwest CR' portion of February Systems CMP Monthly meeting; Attachment C for February Distribution Package |
| 2/21/2002 | Discussed at Monthly CMP Meeting | SCR013102-13 discussed during 'Review of 11.0 Prioritization Eligible CRs' portion of February Systems CMP Monthly meeting; please see Attachment I of February Systems CMP Distribution Package |
| 2/22/2002 | Status Changed | Status changed to presented |
| 3/1/2002 | Release Ranking | Ranking for Release 11.0 following the February 2002 Systems CMP Meeting. SCR013102-13 ranked number 23 |
| 3/1/2002 | Status Changed | Status updated to 'Prioritized' from 'Presented' |
| 4/1/2002 | Release Ranking | Ranking for SATE following the March 2002 Systems CMP Meeting. SCR013102-13 ranked number 18 |
| 6/7/2002 | Status Changed | SCR013102-13 status updated to 'Pending Prioritization' based upon outcome of IMA 11.0 Packaging Selection vote |
| 7/18/2002 | Discussed at Monthly CMP Meeting | SCR013102-13 discussed at July Systems CMP Monthly meeting; please see Systems CMP Distribution Package July CMP -- Attachment P |
| 7/26/2002 | Release Ranking | Ranking for Release 12.0 following the July 2002 Systems CMP Meeting. SCR013102-13 ranked number 39 |
| 10/30/2002 | Status Changed | SCR013102-13 status updated to 'Pending Prioritization' based upon outcome of release 12.0 packaging effort |
| 12/19/2002 | Discussed at Monthly CMP Meeting | SCR013102-13 discussed at December Systems CMP Monthly meeting; please see Systems CMP Distribution Package December CMP -- Attachment O |
| 12/31/2002 | Release Ranking | Ranked #41 for IMA 13.0 Release |
| 1/23/2003 | Release Ranking | Ranked #40 for IMA 13.0 after exception request SCR011303-02EX |
| 3/3/2003 | Status Changed | Status changed to pending withdrawal |
| 3/20/2003 | Status Changed | CR withdrawn in CMP Meeting |
Project Meetings |
| 2/21/02 CMP Systems Meeting Carol Zimmerman/Qwest presented this CR. Issue 1825 seeks to add a new data element to several practices to identify a Billing Service Provider’s Revenue Account Code (RAO) so that calls can be billed to the appropriate Local Service Provider (LSP). Additionally, data populated in this field will be utilized to update LIDB data information. Jonathon Spangler/AT&T questioned whether this is going to tie into the usage for billing? AT&T has an issue trying to capture DUF information. Carol Zimmerman/Qwest stated that she did not think this would remedy AT&T’s concern. The issue says that the RAO is at the line level (is required to verify LIDB). Since the SOP feeds LIDB, the RAO needs to be present. The level of effort is medium. The status will change to presented.
|
CenturyLink Response |
| 2/21/02 CMP Systems Meeting Carol Zimmerman/Qwest presented this CR. Issue 1825 seeks to add a new data element to several practices to identify a Billing Service Provider’s Revenue Account Code (RAO) so that calls can be billed to the appropriate Local Service Provider (LSP). Additionally, data populated in this field will be utilized to update LIDB data information. Jonathon Spangler/AT&T questioned whether this is going to tie into the usage for billing? AT&T has an issue trying to capture DUF information. Carol Zimmerman/Qwest stated that she did not think this would remedy AT&T’s concern. The issue says that the RAO is at the line level (is required to verify LIDB). Since the SOP feeds LIDB, the RAO needs to be present. The level of effort is medium. The status will change to presented. 2/7/02 The LOE is 2800 to 4675 hours..
|
Information Current as of 1/11/2021