License issue on multiple ip machine with WLServer6.0

Question

We are running weblogic 6.0 sp2 on solaris with the machine having multiple ip
addresses.
The primary address of the machine is 10.4.0.62 and ip address of one of the interfaces
is 10.5.2.2. We want to run weblogic through 10.5.2.2 ip address and have got
the license fo 10.5.2.2 address. After installing the license when we attempt
to start weblogic it gives us "Invalid host/IP address" error. utils.myip utility
returns 10.4.0.62 address and upon running utils.showLicenses command it doesn't
show the newly installed license. We also tried to define 10.5.2.2 as a value
for ListenAddress system property value on startup but still same prob.
Currently we are running an evaluation license with ip=any and through the console
ListenAddress is set to 10.5.2.2 and its handling the traffic through that interface
fine.
How can we get it to work on 10.5.2.2 interface through proper license.

Answer 1

1.Define Number Ranges for Shopping Carts and Follow-on Docume
2.Determine Number Ranges and Grouping in Backend Documents
3.The Business Add-In BBP_BS_GROUP_BE offers the following options
You can, independent of the standard, use the method GROUP_RQ to create a separate grouping for purchase requisitions.
In the standard, the system creates only one purchase requisition in the backend for all purchase requisitions with the same backend document type . If the document types are different, the standard creates a separate purchase requisition for each document type.
In the case of purchase orders , the grouping is made by the following fields in this order:
Vendor
Purchasing organization
Purchasing group
Contract
Document type
Item
Company code
In the second step, you can use the method GROUP_PO to create further groupings of the grouped items according criteria you have selected yourself and that are not on header level.
sc converted into po with help of organisation structure  and you must check what document type you maintained in your organisation structure. i believe you can write a custome logic which document type should pick ..while create a PO since your your PR converted into external requirement i.e SC and this sc can be converted into PO if it has appropriate document type.
BBP_BS_GROUP_BE for new document type and number range
br
muthu