(0 comments, 4 posts)
This user hasn't shared any profile information
Posts by Thijs Janssen
The Case At the customer we use Oracle Incentive Compensation (OIC). OIC is used to compensate external partners. These partners are maintained in CRM foundation. The partners are set up as salesperson. Salespersons can be used inside OIC.
The customer has two operating units. In CRM for each operating unit, the salesperson must be set up. So if you had setup the salesperson in operating unit A, then there’s not yet a salesperson in operating unit B.
The problem in CRM foundation is that it is possible to change information of operating unit B, while you’re using a responsibility that is assigned to operating unit A. If you change information of operating unit B, using the responsibility for operating unit A, the relation in the database will be made with operating unit A. So for example you changed a role that is used in operating unit B this will be related to the salesperson of operating unit A. This causes inexplicable errors. On screen everything seems ok, but somewhere hidden in the database there is a wrong relation.
Changing the retained earnings account in General Ledger is pretty easy. Just go to the define Set of Books form and change the retained earnings account. But is this a proper method?No it isn’t. If you change the retained earnings since 11i there will be a warning displayed. In this warning also the steps that you have to perform are displayed.This warning appears if you change the retained earnings account from one account into another account. Off course this new account must exist in your SOB.
Last week I installed some updates for windows and internet explorer. After installing I tried to open a form page, but instead of opening forms my internet explorer disappeared without any warning. (more…)
Last few weeks Iâ€™ve worked with Mercury Quality Center (MQC). This product can be used to register the test scenarioâ€™s you made. For example the functional tests in Oracle E-business Suite. In MQC the scenarioâ€™s can be registered so tests in the future can be done in the same way as you did the original test. A very nice feature of MQC is that the tests can be automated. When the tests are automated the time you need to test your system can be reduced by hours. For example you can activate the test when your leave and when you come back the next morning the test results are displayed. (more…)