'Check covered levels OKS' process results in error during QA checkup

Question

Hi,
The following process in QA test, before submiting a service contract results in error.
'Check covered levels OKS' with the error message
"Atleast one covered line is required".
I'm not able to choose any product.
How to set the covered level as product in service contracts?
In the service contracts authoring window, under lines tab -->pricing/products-->
effectivity
line number
level- covered product. But the lov in name field doesn't list any value ?
what could be the possible reason for this?
Regards,
Nithya

Answer 1

Well, I think I can only give some limited info about these questions since I am only a contracts user, not a developer or administrator.
But here's a few things that might help.
1 & 2) I have always created contracts from scratch where I work. They can't seem to get OM to create contracts correctly (so I can't help with question 2). I don't use OM except for inqueries.
When you create such a contract, it should show up in the Install Base (IB) if you look up the IB record with the related Reference Number (which changed to Product Number in the IB when my company switched from 11.5.5 to 11.5.8). In my case it was the Contracts tab in 11.5.5 (Java interface) and the Contracts link in 11.5.8 (HTML interface).
3) From my experience, the Contract Number is the Sales Order Number in View Transactions if you had the AR Interface checked in the contract.
If you want to change from not having the AR Interface checked to having it checked, I think this works fine and the contract will bill the next time the Main Billing program is run after you make the change, as long as the Bill On Date (11.5.5) or Invoice Date (11.5.8) is set to the current date or earlier. An Invoice (INV line item with invoice # -99) will show up in the Billing History after the AR to Contracts Interface program is run. The actual invoice # will show up in this Billing History after the Invoicing programs are run.
In 11.5.5, if our contract started in the future, we not only had to make sure the Bill On Date was current or earlier, but also run the Main Billing program on that contract with a date equal to or later than the end date of the contract we wanted to bill before it would work. Do not do this on all your contracts at once if you have recurring billing on any of them. You must run it on the individual contracts, otherwise the recurring contracts will bill in full. This is supposedly fixed in 11.5.8, since you can use offsets of more than 31 days on the invoice date, but we haven't billed any yet, so I can't say for sure.
I had problems with billing when trying to change the ammounts in the line items after the billing program had already invoiced a contract in 11.5.5 and haven't tried this in 11.5.8 (it billed incorrect ammounts on the successive invoices).
Note that we have a highly customized version of Oracle Applications 11i, so your results may differ somewhat.