Use of Release Procedure / status in Condition Table
What is the purpose of Release Procedure / Release status when creating condition tables ?
Hi
Release procedures are used in condition tables to control whether the condition types for these condition tables have to be read during pricing condition determination or not.
If the condition table status is released then only the condition types will be read during pricing determination. If the status is not released, then they can be used for information purposes or for simulation of pricing.
The release status is controlled by processing status too, which can be seen in condition record creation screen.
So in crux, the processing status with Release status help in simulation of pricing, blockign the condition records from being read during pricing etc.
For more information an F1 help on the following path will give you some more information.
SPROSD-BF-PRICING-DEFINE PROCESSING STATUS----Here read the documentation meant for this link. You will get some more clarity on this.
Rwd point if it helps.
Reward points if it helps.
Similar Messages
-
Activate Release Status in condition table
HI,
Some has created a pricing condition table and it is being used since 5 years.
Now client had a requirement where he wants release mechanism for any new condition records created.
For this SAP provided a standard functionality of release status.
In our case release status button is not checked while creation of condition table.
Now how to reactivate the release button in the condition table.
Regards,Hi Uday
We can't activate release function in old tables just like that. You have to create new table with same fields but with release status activate. For copying old condition records in this new table you can use
SD_MOVE_A004_TO_A304 report. As you can see with its name this report is for tables 004 and 304. If you want to copy records from 004 to 304 you can use this report. In your case you must have some other tables but if you show this report to your ABAPer he would be able to generate a new report using your tables.
You can take a look on following document provided by SAP and see the conversion section at the end of this document.
http://help.sap.com/saphelp_46c/helpdata/en/9b/3b1a2bc925d311b60f0060b03c2bff/content.htm
Thank$ -
Hi All,
Can any one explain what is the use of "Release procedure" in Pricing. I found a check box in create condition table in pricing i.e. V/03-- what is the use if it is checked and unchecked?
Thanks in Advance,
Regards,
Vamsi.Dear vamsi
The release status (NOT Release Procedure) controls in which scenarios the condition records are found.
If the status is set at 'B', for example, then the corresponding records are taken into account during a pricing simulation, but are not used in current documents.
The release status can only be maintained directly for agreements (sales deals). For condition records, this is done via the processing status.
Thanks
G. Lakshmipathi -
Hi SAP Gurus,
We do release procedure in PR with Account assignment category K.Here ,for collective release in pr (ME55),check box is disabled... Kindly help me how we enable the check box.We use scope of list as "F".All customization for release procedure is correct.
Thnks & Regards
SAP MM UserYou use this component if you wish to set up approval procedures for purchase requisitions or other purchasing documents. Under such a procedure, if a purchase requisition or external purchasing document fulfills certain conditions (e.g. the total order value exceeds $10,000), it has to be approved (by the cost center manager, for instance) before it can be processed further. This process of approving (clearing, or giving the "green light" to) a proposed item of expenditure is replicated in the SAP System by the "release procedure".
It is sensible to define separate release procedures for different groups of materials for which different departments are responsible, and to define separate procedures for investment goods and consumption goods.
Features
Each person involved in the release procedure effects release (signifies approval) via a release transaction, using his or her release code. Once effected, a release can also be cancelled with the same code (that is to say, the original status is reinstated).
If linkage to SAP Business Workflow has been defined for a release code, rejection is also possible. This is only possible for purchase requisitions.
Which Documents Can be Released (Approved)?
Release procedures can be defined for the following documents:
Purchase Requisition
The external purchasing documents purchase order (PO), contract, scheduling agreement, request for quotation (RFQ), and service entry sheet
Release Procedure for Purchase Requisitions
Two different procedures are available for requisitions:
With classification
With this procedure, requisitions can be released both at item level (i.e. item-by-item) and in total. The latter approach is also termed "overall release".
Without classification
With this procedure, requisitions can only be released at item level.
The two procedures are mutually exclusive (that is to say, you must decide in favor of one of them only - you cannot use both).
Release Procedure for External Purchasing Documents
External purchasing documents (i.e. purchasing documents other than requisitions) are released at header level. Item-by-item release is not possible. These documents can only be released using the release procedure with classification.
sri -
hi sapgurus,
here is the scenario,
i have as issue ( for P.O value only)
1) if the value is < 2 lacks then one person will release.
2) if the value is > 2 lacks then 2 persons will releasehi,
3.4.24 Releasing Procedure for Purchase Documents
Use
This setting is incorporated to just give demonstration of how SAP Release procedure works. The aim of this procedure is to replace manual written authorization procedures using signatures by an electronic one, while maintaining the dual Ctrl principle. The person responsible processes the purchasing document in the system, thereby marking it with an "electronic signature" which can give the document legal force.
3.4.24.1 Creation of Characteristics
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Materials Management Purchasing Purchase Order Release Procedure for Purchase Orders Edit Characteristic
Transaction Code CT04
2. On the Characteristic screen, make the following entries.
3. In put POVAL in filed Characteristic and choose Create (White paper) icon or Ctrl + F3 to begin creation of characteristic.
Field name Description User action and values Note
Select Addnl Data tab
Table Name Table Name CEKKO
Field Name Field Name GNETW
Choose Enter to continue, system will give an information message saying Format Data taken from ABAP dictionary, Choose Enter again to continue.
Select Basic Data tab
Description Description Total net order value
Status Status Released
Data Type Data type Currency format Selected by system
Number of characters Number of characters 15
Decimal places Decimal places 2
Currency Currency INR
Interval vals allowed Interval values allowed Check this tick box
Multiple Values Multiple values allowed Select this radio button
4. Choose Enter to complete the entries
5. Choose Save icon or Ctrl + S to save the characteristic.
3.4.24.2 Creation of Class
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Materials Management Purchasing Purchase Order Release Procedure for Purchase Orders Edit Class
Transaction Code CL02
2. On the Class screen, make the following entries:
Field name Description User action and values Note
Class Class PORELPROC
Class Type Class Type 032
Choose Create icon or white paper icon to create new class.
Description Description Purchase Order Release Procedure
Status Status Released
Choose Char. Tab to input characteristic name.
Characteristic Characteristic POVAL Created in above step
3. Choose Enter to complete the entries
4. Choose Save icon or Ctrl + S to save the characteristic.
Result
Class type 032: Class PORELPROC created.
3.4.24.3 Configuration of Release Procedure
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Materials Management Purchasing Purchase Order Release Procedure for Purchase Orders Define Release Procedure for Purchase Orders
Transaction Code SPRO
2. On executing the transaction system will give a popup screen choose Release Groups, system will display Change View u201CRelease Groups: External Purchasing Documentu201D: Overview.
3. Choose New Entries icon and make the following entries:
Field name Description User action and values Note
Rel. Group Release Group 02
Class Class Name PORELPROC Created in above step
Description Description PO Release Procedure
4. Choose Enter to complete the entries
5. Choose Save icon or Ctrl + S to save the entries.
6. Choose yellow arrow to go back to popup screen.
7. Choose Release Codes to select.
8. Choose New Entries icon and make the following entries:
Field name Description User action and values Note
Grp Release group 02 Created in above step
Code Release Code 01
Workflow Workflow Leave it blank
Description Description Purchase Officer
Grp Release group 02 Created in above step
Code Release Code 02
Workflow Workflow Leave it blank
Description Description Materials Manager
9. Choose Enter to complete the entries
10. Choose Save icon or Ctrl + S to save the entries.
11. Choose yellow arrow to go back to popup screen.
12. Choose Release indicator to select.
13. Choose New Entries icon and make the following entries:
Field name Description User action and values Note
Release ind. Release Indicator 1
Released Released Leave it blank
Chgable Changeability 4
Value change % Change of value 10%
Description Description Purchase Order Blocked
Go to 2nd line and input the following values:
Release ind. Release Indicator 2
Released Released Select Check box
Changeable Changeability 6
Description Description Purchase Order Released
14. Choose Enter to complete the entries
15. Choose Save icon or Ctrl + S to save the entries.
16. Choose yellow arrow to go back to popup screen.
17. Choose Release Strategies to select.
18. Choose New Entries icon and make the following entries:
19. System will give new screen New Entries: Details of Added Entries
Field name Description User action and values Note
Release Group Release group 02
Rel. Stategy Release Strategy S1
Capital Items Release
Release Code Release Code 1 01
Release Code Release Code 2 02
20. Choose Enter to complete the entries.
21. Choose Release prerequisites icon and select check box 02 at the bottom and choose Enter.
22. Choose Release statuses icon, system will give a popup screen system will default 1, 1 and 2 entries one by one as a default. Choose Continue.
23. Choose Classification icon, here you can see Total net order value is displayed, please input >= 1.00 INR value in the white placed and choose Enter.
24. Choose Next Screen icon or choose F8 to continue.
25. If you want to simulate the release procedure you can choose Release Simulation icon.
26. Choose Enter to complete the entries.
27. To save the settings choose Save icon or Ctrl + S.
Result
Release procedure is saved.
3.4.24.4 Assignment of Values to Release Procedure
As a default all the purchase documents >= Rs. 1000000.00 is suggested in the following step of release procedure, if you want to have different one you need to change the value in the following step. If you do not want release procedure you may change the value to Zero.
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Cross-Application Components Classification System Assignments Assign Object to Classes
Transaction Code CL20N
2. On the Class screen, make the following entries:
Field name Description User action and values Note
Class Type Class Type 032
Choose Enter to Assign values.
Release group Release Group 02
Rel. Strategy Release strategy S1
Choose Enter.
System will give Class name in Assignments, Double choose Class Name.
System will display Characteristic name Total net order value. Assign the value >= 1000000.00 INR against filed Value.
3. Choose Enter to complete the entries
4. Choose Save icon or Ctrl + S to save the characteristic.
Follow these steps
G.Ganesh Kumar -
Release Procedure for every Purchasing documents
Hi,
for a procument of material eg:- Material007
Can I set Release Procedure for Purchase rquisition
then after releasing Purchase rquisition i need to create a RFQ
which is also subject to Release Procedure ,After releasing RFQ I should able to enter into a Contract,which also subject to Release Procedure ,After releasing Contract i need to create a Purchase Order which is also subject to Release Procedure,After releasing Purchase Order only I should be able to Receive the goods.
Is it possible to do this way ?Can any one help me?
ThanksWhy you want to put so many locks??????
well if case your required use below steps for all document typew in IMG.
suggestion to download the BBP from below link also
http://help.sap.com/bestpractices/BBLibrary/bblibrary_start.htm
3.4.24 Releasing Procedure for Purchase Documents
Use
This setting is incorporated to just give demonstration of how SAP Release procedure works. The aim of this procedure is to replace manual written authorization procedures using signatures by an electronic one, while maintaining the dual Ctrl principle. The person responsible processes the purchasing document in the system, thereby marking it with an "electronic signature" which can give the document legal force.
3.4.24.1 Creation of Characteristics
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Materials Management Purchasing Purchase Order Release Procedure for Purchase Orders Edit Characteristic
Transaction Code CT04
2. On the Characteristic screen, make the following entries.
3. In put POVAL in filed Characteristic and choose Create (White paper) icon or Ctrl + F3 to begin creation of characteristic.
Field name Description User action and values Note
Select Addnl Data tab
Table Name Table Name CEKKO
Field Name Field Name GNETW
Choose Enter to continue, system will give an information message saying Format Data taken from ABAP dictionary, Choose Enter again to continue.
Select Basic Data tab
Description Description Total net order value
Status Status Released
Data Type Data type Currency format Selected by system
Number of characters Number of characters 15
Decimal places Decimal places 2
Currency Currency INR
Interval vals allowed Interval values allowed Check this tick box
Multiple Values Multiple values allowed Select this radio button
4. Choose Enter to complete the entries
5. Choose Save icon or Ctrl + S to save the characteristic.
3.4.24.2 Creation of Class
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Materials Management Purchasing Purchase Order Release Procedure for Purchase Orders Edit Class
Transaction Code CL02
2. On the Class screen, make the following entries:
Field name Description User action and values Note
Class Class PORELPROC
Class Type Class Type 032
Choose Create icon or white paper icon to create new class.
Description Description Purchase Order Release Procedure
Status Status Released
Choose Char. Tab to input characteristic name.
Characteristic Characteristic POVAL Created in above step
3. Choose Enter to complete the entries
4. Choose Save icon or Ctrl + S to save the characteristic.
Result
Class type 032: Class PORELPROC created.
3.4.24.3 Configuration of Release Procedure
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Materials Management Purchasing Purchase Order Release Procedure for Purchase Orders Define Release Procedure for Purchase Orders
Transaction Code SPRO
2. On executing the transaction system will give a popup screen choose Release Groups, system will display Change View u201CRelease Groups: External Purchasing Documentu201D: Overview.
3. Choose New Entries icon and make the following entries:
Field name Description User action and values Note
Rel. Group Release Group 02
Class Class Name PORELPROC Created in above step
Description Description PO Release Procedure
4. Choose Enter to complete the entries
5. Choose Save icon or Ctrl + S to save the entries.
6. Choose yellow arrow to go back to popup screen.
7. Choose Release Codes to select.
8. Choose New Entries icon and make the following entries:
Field name Description User action and values Note
Grp Release group 02 Created in above step
Code Release Code 01
Workflow Workflow Leave it blank
Description Description Purchase Officer
Grp Release group 02 Created in above step
Code Release Code 02
Workflow Workflow Leave it blank
Description Description Materials Manager
9. Choose Enter to complete the entries
10. Choose Save icon or Ctrl + S to save the entries.
11. Choose yellow arrow to go back to popup screen.
12. Choose Release indicator to select.
13. Choose New Entries icon and make the following entries:
Field name Description User action and values Note
Release ind. Release Indicator 1
Released Released Leave it blank
Chgable Changeability 4
Value change % Change of value 10%
Description Description Purchase Order Blocked
Go to 2nd line and input the following values:
Release ind. Release Indicator 2
Released Released Select Check box
Changeable Changeability 6
Description Description Purchase Order Released
14. Choose Enter to complete the entries
15. Choose Save icon or Ctrl + S to save the entries.
16. Choose yellow arrow to go back to popup screen.
17. Choose Release Strategies to select.
18. Choose New Entries icon and make the following entries:
19. System will give new screen New Entries: Details of Added Entries
Field name Description User action and values Note
Release Group Release group 02
Rel. Stategy Release Strategy S1
Capital Items Release
Release Code Release Code 1 01
Release Code Release Code 2 02
20. Choose Enter to complete the entries.
21. Choose Release prerequisites icon and select check box 02 at the bottom and choose Enter.
22. Choose Release statuses icon, system will give a popup screen system will default 1, 1 and 2 entries one by one as a default. Choose Continue.
23. Choose Classification icon, here you can see Total net order value is displayed, please input >= 1.00 INR value in the white placed and choose Enter.
24. Choose Next Screen icon or choose F8 to continue.
25. If you want to simulate the release procedure you can choose Release Simulation icon.
26. Choose Enter to complete the entries.
27. To save the settings choose Save icon or Ctrl + S.
Result
Release procedure is saved.
3.4.24.4 Assignment of Values to Release Procedure
As a default all the purchase documents >= Rs. 1000000.00 is suggested in the following step of release procedure, if you want to have different one you need to change the value in the following step. If you do not want release procedure you may change the value to Zero.
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Cross-Application Components Classification System Assignments Assign Object to Classes
Transaction Code CL20N
2. On the Class screen, make the following entries:
Field name Description User action and values Note
Class Type Class Type 032
Choose Enter to Assign values.
Release group Release Group 02
Rel. Strategy Release strategy S1
Choose Enter.
System will give Class name in Assignments, Double choose Class Name.
System will display Characteristic name Total net order value. Assign the value >= 1000000.00 INR against filed Value.
3. Choose Enter to complete the entries
4. Choose Save icon or Ctrl + S to save the characteristic. -
When I am using Tcode-V/77 to edit condition table I am getting error message
Table 901 can only be accessed by application Inbound Delivery (E1)
Kindly inform how to resolve the issueHi,
I am setting up RDS for trucking where some settings needs to be done in ECC as speciifed below.
Transaction Code
V/77
Customizing Path
Logistics Execution → Transportation → Basic Transportation Functions → Output Control → Maintain Output Determination for Shipments → Maintain Condition Tables (continue with step 7)
1. If you are using the transaction code, continue with step 4. If you are using the Customizing menu path, a Choose Activity dialog box appears. Select the Maintain Output Condition Table for Shipments line and choose the Choose (F2) button.
2. Choose menu command Condition → Create and Enter.
3. On the Create Condition Table (Output Transport) screen, enter the following:
Field Name
Input Value
Table
901
4. The Create Condition Table (Output Transport): field Overview screen appears
5. On this screen, transfer Shipment type (technical name: SHTYP) and Ov. Transport status (technical name: STTRG) from the FieldCatlg list on the right-hand side to the Selected fields list double-click each field. As a result, the text ShipmntTyp/OverallSta should be shown on left-hand side next to table number 901.
Sinc ethe table already exist hence need to edit the table to add teh required fields. -
PO Release procedure based on Cost Centers
Currently a have release procedure based on purchasing groups created as departments. Now i have to create release procedure based on cost centers. Is it possible to bind cost centers with purchasing groups, in order to use the release procedure that I already have?
Hi,
PO Release based on Cost Center wise, with combination of Purchase groups & departments, will be done with the help of ABAPer.
Regards,
Sai -
Table Type Stored Procedure in OBIEE Physical table properties
Hi,
Any one has ever used the Stored Procedure in OBIEE Physical table properties??
I've a procedure & a table i want to plopulate the tabel using the Procedure from OBIEE physical layer.It would be nice if we know more details about 'Populating table'...
Using connection pool->connection pool scripts tab you may go for inserting/updating (Populating table) records into table.
It would be nice if you use dedicated connection pool for init blocks...
Ex: I want to insert user login time some xyz table my query would be like
insert into xyz values ('valueof(NQ_SESSION.USER)',sysdate)
without knowing your requirements its hard to tell anything apart from what is said.
If helps pls mark
Edited by: Srini VEERAVALLI on Jan 16, 2013 10:37 PM -
Condition Table Link to Condition Types
Please Explain me How it is logical/useful/consistent to assign a particular Condition Table to More than One Condition Types ( Via Access Sequence).
As access sequence is used to find valid data for a particular condition type. It determines the sequence in which the system searches for data, as the accesses tell the system where to look first, second, and so on, until it finds a valid condition record [maintained in condition table fields] for the condition types.
<b>Example:</b>
Condition table 001 is for Sales org/Plant
Access seq A001 is having the following search
Sales Org/Dist channel/division
Sales Org/Plant [001]
Access sequence A002 is having the following search
Sales Org/Dist channel/division
Sales Org/Country
Sales Org/Plant[001]
Sales Org/Sold-to
Now the condition table 001 is defined in access sequence A001 and A002 at different level and these access sequence would be used for different condition types.
The same condition table can be used in different access sequence and at different level also depending on the business need and avoiding repeation of data.
Hope this clear your query, Reward Points if resolution appropriate for you.
Regards,
Gaurav -
Adding SERVICE_ORG_RESP_SHORT field to Condition Table
Dear Experts!
We want to use the SERVICE_ORG_RESP_SHORT field in our Condition Table to define product Pricing. The problem is it doesn't exist in a Field Catalog (SPRO -> CRM -> Master Data -> Conditions and Condition Technique -> Condition Technique: Basics -> Create Field Catalog).
We see two possible ways of dealing with this issue:
1) Adding SERVICE_ORG_RESP_SHORT field into Global Field Catalog (SPRO -> CRM -> Master Data Conditions and Condition Technique -> Condition Technique: Basics -> System Configuration for Condition Technique -> Set Up Usage -> folders "Global Field Catalog: Fields" and "Global Field Catalog: Data Elements").
2) Using BAdI (SPRO -> CRM -> Basic Functions -> Pricing -> Define Settings for Pricing -> Adopt User-Defined Fields).
Please, tell us, which of these ways is correct?
Kind Regards,
Alexander Smirnyagin.Hi Alexandr,
the first step mentioned above is required to define the field, so that you can use it to create a conditon table based on it and maintain master data for that condition table. In addition, you should implement the /SAPCND/ROLLNAME BADI for the field.
The second step described above is required to integrate the field for transaction processing, e.g. in a sales or service order. You need to define which order value should get passed to your pricing attribute.
Best Regards,
Michael -
Condition Tables with Release status
When we create condition tables, we have the option of creating them with release status or without release status. What is the difference? What is release status?
Thanks,
Venkathi,
The release status for condition records in a sales deal enables you to limit the use of records that have already been created.
Release status has the following characteristics:
no entry: released
A: blocked
B: released for price simulation
C: released for price simulation and planning
The amount and significance of individual characteristics is defined using domain fixed values and can not be maintained.
Maintenance of the release status is carried out in the sales deal itself (in the proposed values block), is transferred over to the condition records concerned and can then not be changed for these records.
When setting up a new sales deal (with copy), a proposed value is suggested for the release status, which can be set up in Customizing for the agreement type.
A record blocked for an application is treated in the access, as though it has been identified with a deletion indicator. It can however be recognized and displayed as such via the log functionality in Pricing.
The characteristic Pricing Simulation is only used in the report SDNETPRO, which gives a net price list.
If when maintaining individual condition records a sales deal is assigned to the condition record using the transaction VK12, the release status from the sales deal is used for this record. When changing the release status using this sales deal or changes to the sales deal, the user will be notified of any changes to the status.
The release status of conditions in an agreement can only be changed, if
the condition record has release status in the key
the agreement has the release status released
Otherwise the condition record always has the release status of the agreement.
The processing status is always directly assigned to a release status. If conditions are assigned to an agreement, the agreement passes the release status on to all related conditions. The related processing status is then set accordingly.
If you have several processing statuses assigned to a release status, the condition record receives the first (alphabetical) suitable entry as a processing status.
The processing status, which the conditions have received indirectly from an agreement via the release status, can only be changed in the case of released agreements.
source : Library.
regards -
What is the purpose of the release status in creating condition table
hi gurus,
can you please tell me the purpose of the release status and validity date in creating condition table for pricing?
thanks,
PaulDear John
The release status controls in which scenarios the condition records are found.
If the status is set at 'B', for example, then the corresponding records are taken into account during a pricing simulation, but are not used in current documents.
The release status can only be maintained directly for agreements (sales deals). For condition records, this is done via the processing status.
thanks
G. Lakshmipathi -
Processing and Released Status when we create a new Condition table
Hi all
I created a new condition table in M/03, and assigned one field to it, Generated and saved. Then added the condition table in the access sequence. There appeared two more lines below the field that i have assigned. One is Processing status and the other is released status, both are having green lights. what are these and what is its impact.
inputs will be highly appreciated
thanksI myself could find the answer
-
Process Status & Release Status for Condition Record
Hi Gurus,
Pls help me out in the the following scenario.
I want to activate Authorization level check for Condition records.
For example, Product price PR00 is being entered by first level.
After verification done by second level only, that condition record to be used for sales order processing.
I have gone through Process status & Release Status. But not getting full clarity on this.
Rgds,
Senni.BHi,
Please go through the following information.
[Relase Procedure for Condition Record|http://help.sap.com/saphelp_47x200/helpdata/en/a4/af9e78e69611d2ace10000e8a5bd28/frameset.htm]
[Release Procedure for PR|http://www.sap123.com/showthread.php?t=59]
Reward if helpful.
Thanks and Regards,
Naveen Dasari
Maybe you are looking for
-
No data in mo_glob_org_access_tmp
Hi, EBS R12. I've built a custom concurrent on PL/SQL stored procedure executable. The concurrent and executable were defined on Paybles Application. I've devined P_ORG_ID parameter on FND_MO_OU Value Set that (as you know) is built on temporary tabl
-
Thumbnail images of Thumbnail Slideshow Widget not releasing Tooltips
I'm running Muse v2.2 Build 6 CL 770942 and had mistakenly assigned a number of tooltips to a number of thumbnail images of a thumbnail slideshow widget. After deleting those tooltips via the contextual menu on selected thumbnails and the "edit image
-
I have several statements that can throw errors. I currently have nested try statements. Is this the normal way to catch exceptions and is good java coding? 1. ConnectToSQL - could throw SQL Excep 2. Loop Process a. Get Next Item in ResultSet - could
-
Dear gurus, Can we delete the process order, if yes kindly guide me What is the deletion t-code for process order? Reg/ Shankar g.
-
IIS Redirect to Web Logic Server
I have a web server Machine A dedicated to provide static web pages on port 80. I have weblogic server 7.0 sp 4 installed on Machine B. The web applications are deployed on port 8200. If a user comes with a port number 8200 on the URL. I want to redi