For Order to Cash Entries. Step 1: Sales order creation - No entries Step 2: Pick release : Inventory Stage A/c Dr To Inventory Finished goods a/c Step 3: Ship confirm : Cogs A/c Dr Inventory Organization A/c. Step 4: In Receviable : Receviable A/c dr To Revenue A/c To Tax To Freight step 5: When the reciept is not applied to the transaction Unbilled receivabels a/c dr to receivables a/c cr Step 6: Cash : Cash A/c Dr Receivable A/c cr
12 May 2012
what are the accounting entries which get affected in order to cash cycle
Processing Cash Receipts-Oracle Apps
Processing Cash Receipts
There are three steps to processing cash receipts:
1. Enter a receipt
2. Apply the receipt
3. Create journal entries
The last process in the Order to Cash Cycle is to collect payment from your customer. The first step is to enter the receipt. You can enter a receipt three ways: manually entering it, using the lockbox program, or by using automatic receipt process. After the cash receipt has been entered into the Receivables module, you will need to apply the receipt to your invoice.
Apply cash receipt varies based on how you have entered the receipt in step 1. If you have manually entered your receipt, then you will need to manually apply the receipt to your invoice. If you are using the lockbox program, you can set rules to automatically apply the receipt. Sometimes, you will still need to apply the receipt manually if the lockbox program cannot determine the correct invoice. Lastly if you are creating receipts using the automatic receipt process, the receipt is automatically when the receipt is created.
Oracle Apps Tutorial: Overview of the Order to Cash Cycle in Oracle R12
There are four high-level processes in the Order to Cash cycle. The first is processing the order, the second is processing the invoice, the third is recognizing the Cost of Goods (COGS), and the last is processing the cash receipt.
Order Processing
There are five steps to processing an order:
1. Enter an order
2. Book the order
3. Pick release the order
4. Ship confirm the order
5. Close the order
A sales order is an agreement between you and your customer to sell them a product (i.e. inventory item) at a specific price. When you enter the order into the Order Management module, you will specify the customer, the ship-to location, the item, and the item’s selling price. When you have completed the order (and the customer agrees to the order), then you perform step 2 and book the order.
Booking the order notifies the planning and shipping modules that the order has been finalized and can be included in the supply chain planning process. The planning modules will determine if you need to buy or make the item. Once the item has been purchased or manufactured, you will perform step 3 and pick release the order
Pick releasing the order will allocate on-hand inventory to your order and tell the warehouse to move the item from inventory to the shipping staging area. Once your item is in the shipping staging area, it is ready to be shipped. At this point you are ready to perform step 4 and ship confirm the order.
Ship confirming the order tells Oracle that the shipment is complete and to decrement the on-hand inventory. During this process, Oracle will also print out any shipping documents that you need. Invoice lines will also be generated this process for the shipments on your order. If you wish, you can configure the order to only generate invoice lines when all order lines have been shipped. After the shipment process is complete, you are ready for step 5 – closing the order.
Closing the order will prevent you from adding additional lines to the order. If you do not manually close the order, Oracle’s workflow will close all orders that do not have open lines at the end of the month. The process of closing orders helps Order Management and Shipping programs run more efficiently because they only look for open orders.
Invoice Processing
There are four steps to processing an invoice:
1. Import
2. Print
3. Revenue Recognition
4. Create journal entries
As we discuss in order processing, the invoice lines are generated during the shipping process. Order Management uses the “Order Line” workflow to load records into the AR invoice open interface tables. You can perform step 1, Import the invoices, by using the AutoInvoice program. After you successfully import your invoices, you are to perform step 2 and print your invoices.
Printing your invoices is pretty straight-forward, you can use the Print invoice program to print all new the invoices. Once the invoice is printed, Oracle will record the date it was printed on the invoice header. If you need to re-print the invoice, you can use another program to print only select invoices.
At the same time you are printing your invoice, you can run the revenue recognition program. This program will determine if there any revenue rules attached to your invoice and if those rules require revenue to be deferred. Once you have run the revenue recognition program, you can perform step 4 and create the journal entries.
In R12, all journal entries are created by using Subledger Accounting programs. In Receivables, you can create journal entries by using the “Submit Accounting” program or you can create the journal entry by going into the Invoice and clicking on the Create Accounting on the Tools menu.
Recognizing Cost of Goods Sold (COGS)- Oracle R12
Recognizing Cost of Goods Sold (COGS)
There are three steps to processing Cost of Goods Sold:
1. Defer cost of goods
2. Recognize cost of goods
3. Create journal entries
In R12, the Cost of Goods Sold is automatically deferred when the item is shipped. This deferral happens when the Shipping module interfaces a Sales Order Issue transaction to the Inventory module. After you have recognized revenue in the Receivables module, you can perform step 2 and recognize Cost of Goods Sold.
You will need to run three programs: Record Order Management Transactions, Collect Revenue Recognition Information, and Generate COGS Recognition Events. These programs will calculate the percent of COGS to recognize based on the percent of revenue that was recognized. The Generate COGS Recognition Events program will create a new transaction record in the Inventory module for accounting. Once you have these three programs you are ready to perform the last step and create accounting.
In R12, all journal entries are created by using Subledger Accounting programs. The transactions in the Inventory module are accounted for in the Cost Management module, you can create journal entries by using the “Create Accounting – Cost Management” program.
10 May 2012
How to post HTML or XML in blogs
While writing tutorials or asking a question, sometimes it becomes very necessary to post html and javascript codes in your blog comment forms powered by Blogger. You have seen many authors posting HTML effectively but when some of you try to do it, you get an error. This is because Blogger Comment form doesn't support direct posting of HTML and JavaScript. In order to help you to do that we will need to change/encode the same code into a text and then post it effectively without any error. The Tool below will help you to change HTML characters to simple text, which could be easily inserted in your blogger template and comment form. You can also use it to convert your adsense code into an embeddable form. It converts special characters in this way,
'<' becomes '& l t ;' '>' becomes '& g t ;'
'"' (double quote) becomes '& q u o t;'
''' (single quote) becomes ' & # 0 3 9 ;'
'&' becomes '& a m p;'
Use URL : http://centricle.com/tools/html-entities/
To convert the HTML/XML codes
'<' becomes '& l t ;' '>' becomes '& g t ;'
'"' (double quote) becomes '& q u o t;'
''' (single quote) becomes ' & # 0 3 9 ;'
'&' becomes '& a m p;'
Use URL : http://centricle.com/tools/html-entities/
To convert the HTML/XML codes
Invoking web services in Oracle using SOAP
Introduction:-
This document gives fair knowledge of invoking web services using Oracle 9i. Oracle9i allows direct access to web services from PL/SQL using the UTL_HTTP package. This document explains step by step process to invoke web services using UTL_HTTP. Communication between client and server is implemented by SOAP protocol.
What is WSDL?
WSDL stands for Web Services Description Language. It is written in XML and treated as an XML document. The document describes a Web service. It specifies the location of the service and the operations (or methods) the service exposes. WSDL is not yet a W3C standard. It is a language proposed by IBM and Microsoft for describing the capabilities of web services. WSDL is a specification defining how to describe web services in a common XML grammar. WSDL describes four critical pieces of data:
1) Public functions available with the web service
2) Data type information for all message requests and message responses
3) Binding information about the transport protocol to be used (GET or POST method to be used)
4) Address information for locating the specified service (URL to be used to access web service)
In a nutshell, WSDL represents a contract between the service requestor and the service provider, The crucial difference is that WSDL is platform- and language-independent and is used primarily (although not exclusively) to describe SOAP services. Using WSDL, a client can locate a web service and invoke any of its publicly available functions. WSDL therefore represents a cornerstone of the web service architecture, because it provides a common language for describing services and a platform for automatically integrating those services.
The WSDL Specification
WSDL is an XML grammar for describing web services. Some of the major elements are mentioned below. Examples mentioned in each specification are taken from the WSDL example which is attached as a screen shot.
• Definitions
The definitions element must be the root element of all WSDL documents. It defines the name of the web service, declares multiple namespaces used throughout the remainder of the document, and contains all the service elements described.
<?xml version="1.0" encoding="utf-8" ?>
<wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://fxpress.com/webservices" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="http://fxpress.com/webservices" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
• Types
The types element describes all the data types used between the client and server. WSDL is not tied exclusively to a specific typing system, but it uses the W3C XML Schema specification as its default choice. If the service uses only XML Schema built-in simple types, such as strings and integers, the types element is not required.
<s:element name="GetForeignCurrencyCalendarMonthEndRates"><s:complexType><s:sequence>
<s:element minOccurs="1" maxOccurs="1" name="month" type="s:int" />
<s:element minOccurs="1" maxOccurs="1" name="year" type="s:int" />
</s:sequence></s:complexType></s:element>
<s:element name="GetForeignCurrencyCalendarMonthEndRatesResponse">
<s:complexType><s:sequence>
<s:element minOccurs="0" maxOccurs="1"name="GetForeignCurrencyCalendarMonthEndRatesResult">
<s:complexType><s:sequence><s:element ref="s:schema" />
• Message
The message element describes a one-way message, whether it is a single message request or a single message response. Message parameters or message return values are defined in tag.
<wsdl:message name="GetForeignCurrencyCalendarMonthEndRatesSoapIn">
<wsdl:part name="parameters" element="tns:GetForeignCurrencyCalendarMonthEndRates" />
</wsdl:message>
<wsdl:message name="GetForeignCurrencyCalendarMonthEndRatesSoapOut">
<wsdl:part name="parameters" element="tns:GetForeignCurrencyCalendarMonthEndRatesResponse"/>
</wsdl:message>
• PortType
The portType element defines the operation adopted for client server communication.
For example, a portType can combine one request and one response message into a single request/response operation, most commonly used in SOAP services.
<wsdl:port name="BoeingRetrievalSoap" binding="tns:BoeingRetrievalSoap">
<soap:addresslocation="https://treasury2.fxpress.com/Secure/WebServices/BoeingRetrievalTest
/BoeingRetrieval.asmx" />
</wsdl:port>
• Binding
The binding element provides specific details on how a portType operation will actually be transmitted over the wire. HTTP GET and POST bindings are generally used in the operation. The HTTP GET binding adds any input parameters to the operation to the uniform resource locator (URL). But, the HTTP POST binding sends the parameters in the request body.
GET
The GET binding request does not send a request document. Instead, you attach all of the necessary parameters in the query string to the URL You can attach a query string to the URL with a question mark (?). The delimiter between any parameter=value pair is the ampersand (&). The following example is a GET binding request that uses a query string with the question mark, and a delimiter. In this way whatever you will send will be seen by other user so can say that it is not even secure.
http://server:port/contextRoot/group/dadx/operationName?param1=abc¶m2=1234¶m3=thi&20is&20a&20parameter
POST
The Post method is more powerful request. By using Post we can request as well as send some data to the server. We use post method when we have to send a big chunk of data to the server, like when we have to send a long enquiry form then we can send it by using the post method.
A POST binding issues an HTTP POST request. A POST bind request sends a request document. The document contains the request parameter, but the parameter is not in XML format. An HTTP client application, such as a Web browser, creates the request document. A Web browser usually creates a request document from input forms that are sent to the server.
This document gives fair knowledge of invoking web services using Oracle 9i. Oracle9i allows direct access to web services from PL/SQL using the UTL_HTTP package. This document explains step by step process to invoke web services using UTL_HTTP. Communication between client and server is implemented by SOAP protocol.
What is WSDL?
WSDL stands for Web Services Description Language. It is written in XML and treated as an XML document. The document describes a Web service. It specifies the location of the service and the operations (or methods) the service exposes. WSDL is not yet a W3C standard. It is a language proposed by IBM and Microsoft for describing the capabilities of web services. WSDL is a specification defining how to describe web services in a common XML grammar. WSDL describes four critical pieces of data:
1) Public functions available with the web service
2) Data type information for all message requests and message responses
3) Binding information about the transport protocol to be used (GET or POST method to be used)
4) Address information for locating the specified service (URL to be used to access web service)
In a nutshell, WSDL represents a contract between the service requestor and the service provider, The crucial difference is that WSDL is platform- and language-independent and is used primarily (although not exclusively) to describe SOAP services. Using WSDL, a client can locate a web service and invoke any of its publicly available functions. WSDL therefore represents a cornerstone of the web service architecture, because it provides a common language for describing services and a platform for automatically integrating those services.
The WSDL Specification
WSDL is an XML grammar for describing web services. Some of the major elements are mentioned below. Examples mentioned in each specification are taken from the WSDL example which is attached as a screen shot.
• Definitions
The definitions element must be the root element of all WSDL documents. It defines the name of the web service, declares multiple namespaces used throughout the remainder of the document, and contains all the service elements described.
<?xml version="1.0" encoding="utf-8" ?>
<wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://fxpress.com/webservices" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="http://fxpress.com/webservices" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
• Types
The types element describes all the data types used between the client and server. WSDL is not tied exclusively to a specific typing system, but it uses the W3C XML Schema specification as its default choice. If the service uses only XML Schema built-in simple types, such as strings and integers, the types element is not required.
<s:element name="GetForeignCurrencyCalendarMonthEndRates"><s:complexType><s:sequence>
<s:element minOccurs="1" maxOccurs="1" name="month" type="s:int" />
<s:element minOccurs="1" maxOccurs="1" name="year" type="s:int" />
</s:sequence></s:complexType></s:element>
<s:element name="GetForeignCurrencyCalendarMonthEndRatesResponse">
<s:complexType><s:sequence>
<s:element minOccurs="0" maxOccurs="1"name="GetForeignCurrencyCalendarMonthEndRatesResult">
<s:complexType><s:sequence><s:element ref="s:schema" />
• Message
The message element describes a one-way message, whether it is a single message request or a single message response. Message parameters or message return values are defined in
<wsdl:message name="GetForeignCurrencyCalendarMonthEndRatesSoapIn">
<wsdl:part name="parameters" element="tns:GetForeignCurrencyCalendarMonthEndRates" />
</wsdl:message>
<wsdl:message name="GetForeignCurrencyCalendarMonthEndRatesSoapOut">
<wsdl:part name="parameters" element="tns:GetForeignCurrencyCalendarMonthEndRatesResponse"/>
</wsdl:message>
• PortType
The portType element defines the operation adopted for client server communication.
For example, a portType can combine one request and one response message into a single request/response operation, most commonly used in SOAP services.
<wsdl:port name="BoeingRetrievalSoap" binding="tns:BoeingRetrievalSoap">
<soap:addresslocation="https://treasury2.fxpress.com/Secure/WebServices/BoeingRetrievalTest
/BoeingRetrieval.asmx" />
</wsdl:port>
• Binding
The binding element provides specific details on how a portType operation will actually be transmitted over the wire. HTTP GET and POST bindings are generally used in the operation. The HTTP GET binding adds any input parameters to the operation to the uniform resource locator (URL). But, the HTTP POST binding sends the parameters in the request body.
GET
The GET binding request does not send a request document. Instead, you attach all of the necessary parameters in the query string to the URL You can attach a query string to the URL with a question mark (?). The delimiter between any parameter=value pair is the ampersand (&). The following example is a GET binding request that uses a query string with the question mark, and a delimiter. In this way whatever you will send will be seen by other user so can say that it is not even secure.
http://server:port/contextRoot/group/dadx/operationName?param1=abc¶m2=1234¶m3=thi&20is&20a&20parameter
POST
The Post method is more powerful request. By using Post we can request as well as send some data to the server. We use post method when we have to send a big chunk of data to the server, like when we have to send a long enquiry form then we can send it by using the post method.
A POST binding issues an HTTP POST request. A POST bind request sends a request document. The document contains the request parameter, but the parameter is not in XML format. An HTTP client application, such as a Web browser, creates the request document. A Web browser usually creates a request document from input forms that are sent to the server.
To claim deduction u/s 80DDB following condition should be satisfied.
Rules to claim deduction u/s 80DDB following condition should be satisfied
1.Taxpayer should be resident in India in the previous year.
2.Deduction is available to Individual or HUF only.
3.Deduction is available on actual expenditure on medical treatment of specified Disease or ailment as prescribed.
4.Expenditure should be incurred for medical treatment of
1.assessee himself
2.wholly/mainly dependent Husband/wife(spouse)
3.wholly /mainly dependent children
4.wholly/mainly dependent parents
5.wholly/mainly dependent Brother
6.wholly/mainly dependent Sisters
7.in case of Huf ,wholly/mainly dependent member of the HUF
5.Assesee shall have to submit certificate in form no 10-I from prescribed specialist working in Government hospital
6.Government hospital includes a departmental dispensary whether full-time or part-time established and run by a Department of the Government for the medical attendance and treatment of a class or classes of Government servants and members of their families, a hospital maintained by a local authority and any other hospital with which arrangements have been made by the Government for the treatment of Government servants;
7.This deduction can not be allowed by DDO(employer) while calculating the TDS amount .So assessee have to apply for claim this deduction while filing his return in Income tax tax department
Amount of Deduction:
1.Deduction is available for Rs. 40000 or amount actually paid ,which ever is less.
2.If expenditure has been done in respect of dependent who is at least of 65 year of age in any time during the previous year then deduction shall be Rs. 60000 or amount paid which ever is less. Update : Age Limit for Senior Citizen has been proposed to be reduced to 60 Year wef financial year 2012-13 through Finance Bill 2012
3.deduction Amount as arrived in above (1) or (2) will be reduced by amount reimbursed by employer or by insurer.
Specified diseases and ailments for the purpose of deduction under section 80DDB.
(i) Neurological Diseases where the disability level has been certified to be of 40% and above,
(a) Dementia ;(b) Dystonia Musculorum Deformans ;(c) Motor Neuron Disease ;(d) Ataxia ;(e) Chorea ;(f) Hemiballismus ;(g) Aphasia ;(h) Parkinsons Disease ;(ii) Malignant Cancers ;(iii) Full Blown Acquired Immuno-Deficiency Syndrome (AIDS) ;(iv) Chronic Renal failure ;(v) Hematological disorders :(i) Hemophilia ;(ii) Thalassaemia.
On the Basic of facts given by you ,you are eligible to for deduction of Rs 40000 only.Enhanced Limit of 60000 is available if dependent /patient is senior citizen (attain age 65 in previous year ) not assesse who is is claiming the deduction.in your case your age is 66 ,However your wife's age is just 60 ,so you are eligible for only 40000 deduction or expenses incurred which ever is less.
Moreover the above said amount will be reduced by the amount reimbursed by employer/Insurance company .In your case this is nil.so you will get 40000 or expenses incurred ,which ever is less as deduction u/s 80DDB of the Income Tax Act.
More information refer income tax site : http://law.incometaxindia.gov.in/DitTaxmann/IncomeTaxActs/2005ITAct/rules011dd.htm
Form 10I can be downloaded from internet
Sample,
Certificate of prescribed authority for the purposes of section 80DDB
Name of the Patient
Address
Father’s name
Name and address of the person on whom the patient is dependent
and his relationship with the patient.
Name of the disease or ailment
(please see rule 11DD)
For diseases or ailments mentioned in item (i) of clause (a) of
sub-rule (1), whether the disability is 40% or more (Please specify
the extent).
Name, address, registration number and qualification of the
specialist issuing the certificate, along with the name and address
of the Government hospital [see rule 11DD(2)]
Verification
This is to verify that I, Dr.____________________________________________________ s/o (w/o) Shri_____________________, in the case of the patient Shri/Smt./Ms. ________________________, after considering the entire history of illness, careful examination and appropriate investigations, am of the opinion that the patient is suffering from ______________________________disease/ailment during the previous year ending on 31st March,_______________________ I also certify (only in case of neurological disease) that the extent of disability is more than 40%) (Strike off, if not applicable).
I certify that the information furnished above is true to the best of my knowledge.
Date _______________
Place _______________
Signature
(Name and Address)
To be countersigned by the Head of the Government hospital, where the prescribed authority is a
specialist with post-graduate degree in General or Internal Medicine.
Date ______________
Place ______________
Signature
(Name and Address)
1.Taxpayer should be resident in India in the previous year.
2.Deduction is available to Individual or HUF only.
3.Deduction is available on actual expenditure on medical treatment of specified Disease or ailment as prescribed.
4.Expenditure should be incurred for medical treatment of
1.assessee himself
2.wholly/mainly dependent Husband/wife(spouse)
3.wholly /mainly dependent children
4.wholly/mainly dependent parents
5.wholly/mainly dependent Brother
6.wholly/mainly dependent Sisters
7.in case of Huf ,wholly/mainly dependent member of the HUF
5.Assesee shall have to submit certificate in form no 10-I from prescribed specialist working in Government hospital
6.Government hospital includes a departmental dispensary whether full-time or part-time established and run by a Department of the Government for the medical attendance and treatment of a class or classes of Government servants and members of their families, a hospital maintained by a local authority and any other hospital with which arrangements have been made by the Government for the treatment of Government servants;
7.This deduction can not be allowed by DDO(employer) while calculating the TDS amount .So assessee have to apply for claim this deduction while filing his return in Income tax tax department
Amount of Deduction:
1.Deduction is available for Rs. 40000 or amount actually paid ,which ever is less.
2.If expenditure has been done in respect of dependent who is at least of 65 year of age in any time during the previous year then deduction shall be Rs. 60000 or amount paid which ever is less. Update : Age Limit for Senior Citizen has been proposed to be reduced to 60 Year wef financial year 2012-13 through Finance Bill 2012
3.deduction Amount as arrived in above (1) or (2) will be reduced by amount reimbursed by employer or by insurer.
Specified diseases and ailments for the purpose of deduction under section 80DDB.
(i) Neurological Diseases where the disability level has been certified to be of 40% and above,
(a) Dementia ;(b) Dystonia Musculorum Deformans ;(c) Motor Neuron Disease ;(d) Ataxia ;(e) Chorea ;(f) Hemiballismus ;(g) Aphasia ;(h) Parkinsons Disease ;(ii) Malignant Cancers ;(iii) Full Blown Acquired Immuno-Deficiency Syndrome (AIDS) ;(iv) Chronic Renal failure ;(v) Hematological disorders :(i) Hemophilia ;(ii) Thalassaemia.
On the Basic of facts given by you ,you are eligible to for deduction of Rs 40000 only.Enhanced Limit of 60000 is available if dependent /patient is senior citizen (attain age 65 in previous year ) not assesse who is is claiming the deduction.in your case your age is 66 ,However your wife's age is just 60 ,so you are eligible for only 40000 deduction or expenses incurred which ever is less.
Moreover the above said amount will be reduced by the amount reimbursed by employer/Insurance company .In your case this is nil.so you will get 40000 or expenses incurred ,which ever is less as deduction u/s 80DDB of the Income Tax Act.
More information refer income tax site : http://law.incometaxindia.gov.in/DitTaxmann/IncomeTaxActs/2005ITAct/rules011dd.htm
Form 10I can be downloaded from internet
Sample,
FORM NO. 10-I
[See rule 11DD]
Certificate of prescribed authority for the purposes of section 80DDB
Name of the Patient
Address
Father’s name
Name and address of the person on whom the patient is dependent
and his relationship with the patient.
Name of the disease or ailment
(please see rule 11DD)
For diseases or ailments mentioned in item (i) of clause (a) of
sub-rule (1), whether the disability is 40% or more (Please specify
the extent).
Name, address, registration number and qualification of the
specialist issuing the certificate, along with the name and address
of the Government hospital [see rule 11DD(2)]
Verification
This is to verify that I, Dr.____________________________________________________ s/o (w/o) Shri_____________________, in the case of the patient Shri/Smt./Ms. ________________________, after considering the entire history of illness, careful examination and appropriate investigations, am of the opinion that the patient is suffering from ______________________________disease/ailment during the previous year ending on 31st March,_______________________ I also certify (only in case of neurological disease) that the extent of disability is more than 40%) (Strike off, if not applicable).
I certify that the information furnished above is true to the best of my knowledge.
Date _______________
Place _______________
Signature
(Name and Address)
To be countersigned by the Head of the Government hospital, where the prescribed authority is a
specialist with post-graduate degree in General or Internal Medicine.
Date ______________
Place ______________
Signature
(Name and Address)
05 May 2012
Firefox asks for user name and password on internal sites
Firefox asks for user name and password on internal sites
This article describes why Firefox may ask for a user name and password on internal/intranet sites (for example, a Sharepoint site) while Internet Explorer doesn't.
Many internal sites use NTLM authentication, which reuses your network login as a login for the site. In many organizations, Internet Explorer is configured to allow NTLM on the internal sites, but Firefox is not. You can configure Firefox on Windows to allow certain sites:
1.In the Location bar, type about:config, and press Enter.
◦The about:config "This might void your warranty!" warning page may appear. Click I'll be careful, I promise!, to continue to the about:config page.
1.In the about:config page, search for the preference network.automatic-ntlm-auth.trusted-uris, and double-click on it.
2.In the prompt that comes up, type a list of server you want to allow, separated by a comma and a space. For example, if you wanted to allow http://myinternalserver and http://anotherinternalserver, you would type in myinternalserver, anotherinternalserver.
3.Press OK.
Now that Firefox is configured to use NTLM on these sites, you should no longer be prompted for your user name and password.
This article describes why Firefox may ask for a user name and password on internal/intranet sites (for example, a Sharepoint site) while Internet Explorer doesn't.
Many internal sites use NTLM authentication, which reuses your network login as a login for the site. In many organizations, Internet Explorer is configured to allow NTLM on the internal sites, but Firefox is not. You can configure Firefox on Windows to allow certain sites:
1.In the Location bar, type about:config, and press Enter.
◦The about:config "This might void your warranty!" warning page may appear. Click I'll be careful, I promise!, to continue to the about:config page.
1.In the about:config page, search for the preference network.automatic-ntlm-auth.trusted-uris, and double-click on it.
2.In the prompt that comes up, type a list of server you want to allow, separated by a comma and a space. For example, if you wanted to allow http://myinternalserver and http://anotherinternalserver, you would type in myinternalserver, anotherinternalserver.
3.Press OK.
Now that Firefox is configured to use NTLM on these sites, you should no longer be prompted for your user name and password.
Steps to Convert RDF file into BI Report/XML Publisher report
There is no single step method where you can converting RDF file into XML Publisher/BI reprot. BI Publisher developer guide has complete details. For the benifit of everyone i am publishing these steps.
Approach 1, Here you still need RDF file to generate XML outpu : Convert the output format of Standard report to XML, create a new RTF template and register a Data Definition and Template with XML Publisher.
Approach 2 : Convert the RDF report into XML Report and use this XML as a Data Template. Create a new XML Publisher report Data Definition with this XML as Data Template and create a new Template.
The problem with Approach 2 is that Oracle provides no tool to convert Reports 6i into XML Report and any other supporting APIs to handle associated PL/SQL logic embedded into RDF.
Enter Reports 9i (or higher) and XML Publisher 5.6.3. These two combinations of Oracle products provide tools to first convert RDF report into XML report and associated XML Publisher API to handle PL/SQL logic.
This is how it works.
-----------------------------
Oracle Reports contains both Data Model (logic) and Layout (presentation) in a single file. In XML Publisher they are stored separately. Therefore migration involves a 2 step process.
Step 1 RDF to XML format report : Oracle Reports 9i (or higher) comes with utility "rwconverter.exe". Use either Reports Designer or "rwconverter.exe" command line to convert RDF into XML format report.
From the Designer :
The following command executes “rwconverter.exe” utility, taking the source report,
XXTEST.rdf and converting it to an RDF-XML format that can be consumed by the
XML Publisher conversion utility.
Note the dtype must be specified as "xmlfile".
\BIN>rwconverter batch=yes source= c:\XXTEST.rdf
dest= c:\XXTEST.xml dtype=xmlfile overwrite=yes
This would create an RDF-XML file, with all the PL/SQL logic and presentation logic.
Step 2.1 Data Model Migration :
XML Publisher 5.6.3 provides a Java API Package "oracle.apps.xdo.rdfparser". This package has "DataTemplateGenerator" class that creates a DataTemplate from the XML report file. If report has triggers this will generate '.pks' and '.pkb' file for that trigger which needs to be compiled into the Database
Example
javaw.exe oracle.apps.xdo.rdfparser.DataTemplateGenerator c:\XXTEST.xml
Output Files:
PL/SQL Package : XXTESTS.pls
PL/SQL Body : XXTESTB.pls
DataTemplate : XXTEST_template.xml
Step 2.2 Data Model Migration :
XML Publisher 5.6.3 API Package "oracle.apps.xdo.rdfparser" has "RTFTemplateGenerator" class to migrate the Oracle Reports layout to an XML Publisher RTF template. Because there is no support for PL/SQL in an RTF Template, the generator writes all Oracle Report format trigger code to the log file. This must later be implemented as XSL code
Example
javaw.exe oracle.apps.xdo.rdfparser.RTFTemplateGenerator c:\XXTEST.xml
Output Files:
RTF Template : C:\XXTEST.rtf
Log File : C:\XXTEST.log
That’s it we are done with the conversion.
Now that we have converted the RDF into XML publisher report, we simply need to use the Data Template and RTF to register with the XML Publisher.
Step 3 : Register a new Data Definition with XML Publisher Responsibility, with XML file generated as part of Step 2.2 as Data Template. Register the RTF template for the DD.
Step 4 : Create a Concurrent Report Program with Report output as XML and executable as "XDODTEXE". XDODTEXE is XML Publisher Data Template Executable Engine, which is a Java Concurrent Program.
More information refer,
http://docs.oracle.com/cd/E10415_01/doc/bi.1013/e10416/convertrpts.htm#CIHIHICD
http://apps2fusion.com/at/kr/346-bi-publisher-report-migration-utility
Approach 1, Here you still need RDF file to generate XML outpu : Convert the output format of Standard report to XML, create a new RTF template and register a Data Definition and Template with XML Publisher.
Approach 2 : Convert the RDF report into XML Report and use this XML as a Data Template. Create a new XML Publisher report Data Definition with this XML as Data Template and create a new Template.
The problem with Approach 2 is that Oracle provides no tool to convert Reports 6i into XML Report and any other supporting APIs to handle associated PL/SQL logic embedded into RDF.
Enter Reports 9i (or higher) and XML Publisher 5.6.3. These two combinations of Oracle products provide tools to first convert RDF report into XML report and associated XML Publisher API to handle PL/SQL logic.
This is how it works.
-----------------------------
Oracle Reports contains both Data Model (logic) and Layout (presentation) in a single file. In XML Publisher they are stored separately. Therefore migration involves a 2 step process.
Step 1 RDF to XML format report : Oracle Reports 9i (or higher) comes with utility "rwconverter.exe". Use either Reports Designer or "rwconverter.exe" command line to convert RDF into XML format report.
From the Designer :
The following command executes “rwconverter.exe” utility, taking the source report,
XXTEST.rdf and converting it to an RDF-XML format that can be consumed by the
XML Publisher conversion utility.
Note the dtype must be specified as "xmlfile".
\BIN>rwconverter batch=yes source= c:\XXTEST.rdf
dest= c:\XXTEST.xml dtype=xmlfile overwrite=yes
This would create an RDF-XML file, with all the PL/SQL logic and presentation logic.
Step 2.1 Data Model Migration :
XML Publisher 5.6.3 provides a Java API Package "oracle.apps.xdo.rdfparser". This package has "DataTemplateGenerator" class that creates a DataTemplate from the XML report file. If report has triggers this will generate '.pks' and '.pkb' file for that trigger which needs to be compiled into the Database
Example
javaw.exe oracle.apps.xdo.rdfparser.DataTemplateGenerator c:\XXTEST.xml
Output Files:
PL/SQL Package : XXTESTS.pls
PL/SQL Body : XXTESTB.pls
DataTemplate : XXTEST_template.xml
Step 2.2 Data Model Migration :
XML Publisher 5.6.3 API Package "oracle.apps.xdo.rdfparser" has "RTFTemplateGenerator" class to migrate the Oracle Reports layout to an XML Publisher RTF template. Because there is no support for PL/SQL in an RTF Template, the generator writes all Oracle Report format trigger code to the log file. This must later be implemented as XSL code
Example
javaw.exe oracle.apps.xdo.rdfparser.RTFTemplateGenerator c:\XXTEST.xml
Output Files:
RTF Template : C:\XXTEST.rtf
Log File : C:\XXTEST.log
That’s it we are done with the conversion.
Now that we have converted the RDF into XML publisher report, we simply need to use the Data Template and RTF to register with the XML Publisher.
Step 3 : Register a new Data Definition with XML Publisher Responsibility, with XML file generated as part of Step 2.2 as Data Template. Register the RTF template for the DD.
Step 4 : Create a Concurrent Report Program with Report output as XML and executable as "XDODTEXE". XDODTEXE is XML Publisher Data Template Executable Engine, which is a Java Concurrent Program.
More information refer,
http://docs.oracle.com/cd/E10415_01/doc/bi.1013/e10416/convertrpts.htm#CIHIHICD
http://apps2fusion.com/at/kr/346-bi-publisher-report-migration-utility
How to: Running Multiple Firefox Instances
Create shortcut
“C:\Program Files\Mozilla Firefox\firefox.exe” -P -no-remote
assuming that your mozilla has installed at C:\Program Files\Mozilla Firefox
Setting up multiple instances of Firefox is a 5 minute task which is made possible by the creation of separate profiles, whereby each instance of Firefox will use its own profile. A few key points about profiles:
•Every profile has its own set of bookmarks, extensions, themes and browsing history.
•If one instance of Firefox crashes, it will not bring down other instances of Firefox running under different profiles.
•The only thing shared between profiles are the plugins (Java, Flash, etc).
•Separate profiles can be used to run different versions of Firefox at the same time.
Here’s how it’s done:
1.Launch the profile manager to create a new profile:
“C:\Program Files\Mozilla Firefox\firefox.exe” -profilemanager
Make sure you close all current instances of Firefox otherwise it will simply open a new window instead of the manager.
2.Create a new profile. I would recommend using a single lowercase word.
3.Modify your Firefox shortcut to look like this:
“C:\Program Files\Mozilla Firefox\firefox.exe” -P “profile-name”
4.Now that you’ve setup separate profiles, you still need to tell Firefox to run them independently of one another, by adding the “-no-remote” option to one or both of your shortcuts:
“C:\Program Files\Mozilla Firefox\firefox.exe” -P “profile-name” -no-remote
or
“C:\Program Files\Mozilla Firefox\firefox.exe” -P -no-remote
-no-remote allows you to run multiple profiles simultaneously, otherwise any new request to open a Firefox window will simply attach the window to the profile that’s already running.
-no-remote effectively tells Firefox to open an independent instance of the indicated profile.
The disadvantage of the -no-remote option is that it limits you to one instance of a profile at any given time, so clicking twice on a Firefox shortcut that has the -no-remote parameter will give you the following error.
Getting around this is fairly simple: only add -no-remote to the profile that you expect to use less often.
“C:\Program Files\Mozilla Firefox\firefox.exe” -P -no-remote
assuming that your mozilla has installed at C:\Program Files\Mozilla Firefox
Setting up multiple instances of Firefox is a 5 minute task which is made possible by the creation of separate profiles, whereby each instance of Firefox will use its own profile. A few key points about profiles:
•Every profile has its own set of bookmarks, extensions, themes and browsing history.
•If one instance of Firefox crashes, it will not bring down other instances of Firefox running under different profiles.
•The only thing shared between profiles are the plugins (Java, Flash, etc).
•Separate profiles can be used to run different versions of Firefox at the same time.
Here’s how it’s done:
1.Launch the profile manager to create a new profile:
“C:\Program Files\Mozilla Firefox\firefox.exe” -profilemanager
Make sure you close all current instances of Firefox otherwise it will simply open a new window instead of the manager.
2.Create a new profile. I would recommend using a single lowercase word.
3.Modify your Firefox shortcut to look like this:
“C:\Program Files\Mozilla Firefox\firefox.exe” -P “profile-name”
4.Now that you’ve setup separate profiles, you still need to tell Firefox to run them independently of one another, by adding the “-no-remote” option to one or both of your shortcuts:
“C:\Program Files\Mozilla Firefox\firefox.exe” -P “profile-name” -no-remote
or
“C:\Program Files\Mozilla Firefox\firefox.exe” -P -no-remote
-no-remote allows you to run multiple profiles simultaneously, otherwise any new request to open a Firefox window will simply attach the window to the profile that’s already running.
-no-remote effectively tells Firefox to open an independent instance of the indicated profile.
The disadvantage of the -no-remote option is that it limits you to one instance of a profile at any given time, so clicking twice on a Firefox shortcut that has the -no-remote parameter will give you the following error.
Getting around this is fairly simple: only add -no-remote to the profile that you expect to use less often.
Subscribe to:
Posts (Atom)