IBM AIX5L Maintenance Release allowable for 9.2.0.7

Does anyone know if we can install Oracle 9.2.0.7 on an IBM pSeries with aix 5300-04-02?
Are the ptfs the same as Metalink note 282036.1 for 5300-03?

Hmmmm. Let's see ...
- you apparently have metalink access;
- metalink is the pipe to support;
- support is the group that maintains the certification information;
Can I assume you have opened a TAR/SR to ask this question, and are simply trying to get a complementary answer here?

Similar Messages

Purchase and release order not allowed for TECO work orders

Hi
We are typically setting maintenance work orders to TECO once the physical work as been performed as that sets the reference date for showing the history of when the maintenance was performed, and when the maintenance call was completed. However, we have invoices that may come in significantly later than when the physical work was performed.
Once the order is in TECO a purchase or release order (for services against a contract) cannot be created for the work order. Additionally it appears that even if we have a release order,or purchase order, if it is not for the exact amount of the invoice the release or purchase order cannot be ammended - we get the sameerror mssage (BS007) as when creating a new purchase order for the TECO order.
I had wondered about using BS22 to change TECO to continue to allow purchase and release orders when the order is in TECO status.
Any input on pros/cons or other approachs appreciated.
Philip

Thanks
That was what I initially thought. However I was informed that if the invoice is not for the originally determined amount that to post the invoice means having to change the PO, and changing the PO appears to hit the same business transaction as creating a PO, and so we get the error mssage.
The issue is that we may know we need to have services estimated at, say, $5.000. But we do not know what the actual final invoice will be. So the actual amount may end up being $4,500 or $5,500 as an example, and it may come ni late from the vendor. The Purchse Order side is not my expertize, but I am being informed that the invoice must match the PO amount, otherwise the PO must be ammended to match. As the order is in TECO, the user cannot amend the PO.
I would be happy to know of other options, or at least good questions to ask. I want the end user to be able to post the invoice against the PO, after the order is in TECO, even it the invoice amount is not exactly the same as what was originally anticipated.
regards
Philip

Instance in distributed environment for 11.1.2.1 using maintenance release

Hi Experts,
As i plan for 11.1.2.1 using maintenance (from 11.1.2).
I need clarification:
as in 11.1.2 "Oracle EPM Instance name" was similar on all servers (D:\oracle\middleware\user_project; epmsystem1)
while in 11.1.2.1 "Oracle EPM Instance" should be different (D:\oracle\middleware\user_project; epmsystem1, D:\oracle\middleware\user_project; epmsystem2, etc....)
OR EPM ORACLE Instance Directory recommended on shared drive accessible to all machine.
In my case 11.1.2 is having similar instance name on all servers.
Please suggest
Regards
Kumar

Hi John,
Thanks for the help.
As per suggested document
When you configure in a distributed environment, provide a new, unique instance name as you configure each server. For example, if you are using the default instance name epmsystem1 on the >first server, and you keep the same naming convention on subsequent servers, you would create new, unique instance names on each subsequent server, such as epmsystem2, epmsystem3, and >so on. Is it applicable in maintenance release where all instance name are similar (epmsystem1) on all servers?
Does it mean i should modify and make it (epmsystem1, epmsystem2, epmsystem3....)?
Please suggest as i am not very sure
Regards
Kumar

Releasing authorization for maintenance order and permit.

Hi,experts,
We have two different user id say "X" and Y.We want to block releasing authorization of maintenance order and permit for user id "X" and give the same to user id "Y",How we can do it in SAP?Please,give some suggestions on this.Thanks in advance.
rgds
rajib

Hiii
You can create two seperate Authorization role using PFCG transaction code. Assign it to particular users & control the authorization. Use Following procedure.
1. Transaction code PFCG will take you on screen role creation screen.
2. Give authorization for IW32 transaction code in that block authorization according to business transaction for BFRE. This business operation is made for order release.
For permit there is seperate option is available for permits also.
If you have any issue, pl. be free to ask question.
Regards

TS4498 I JUST, 9 July 13, bought Logic Pro... Any change Apple will allow for some type of upgrade to Pro X, since we had NO Fore Knowledge of its release...

I JUST, 9 July 13, bought Logic Pro... Any change Apple will allow for some type of upgrade to Pro X, since we had NO Fore Knowledge of its release...

I bought Logic Pro 9 a few days ago and they just sent me a response with a big NO! Twice! so far!
see this threads:
https://discussions.apple.com/message/22496383#22496383
https://discussions.apple.com/message/22490113#22490113
https://discussions.apple.com/message/22490862#22490862
https://discussions.apple.com/message/22500131#22500131
https://discussions.apple.com/message/22494804#22494804
This is no way to treat your customers.

New IBM JDK 1.4.2 for SAP NetWeaver 2004 and 2004s

In May 2006 IBM System p brand and SAP announced the direction to enhance the IBM AIX 5L JDK 1.4.2 for SAP NetWeaver 2004 and SAP NetWeaver 2004s based applications. The new IBM JDK 1.4.2 for SAP NetWeaver applications on AIX 5L is 100% upward compatible for all SAP business applications and, compared to the classical AIX JDK, provides a more consistent runtime behavior, enhances memory management, and improves debugging capabilities.
<b>General Availability (GA) of the new IBM JDK 1.4.2 for SAP NetWeaver 2004 and 2004s on AIX 5L</b>
As part of a staged release process aligned between IBM and SAP a customer pilot program was started in August 2006 followed by a Controlled Availability (CA) program. Based on positive customer feedback resulting from real production usage and the very encouraging internal test results, the new IBM JDK on AIX 5L is/will be generally available
     for SAP NetWeaver 2004 SP14 and above starting at 5th of February 2007
                and
     for SAP NetWeaver 2004s SP06 and above starting at 30th of March 2007.
This means systems running above SAP NetWeaver releases in an AIX 5L environment are allowed to use the new IBM JDK without restrictions.
This announcement does not affect the use and support of the classical AIX JDK outside SAP environments.
<b>Transition Plan to the new IBM JDK 1.4.2 on AIX 5L</b>
SAP will support the classical and the new JDK in parallel for a limited number of NetWeaver support packages. Afterwards only the new IBM JDK will be supported:
     for SAP NetWeaver 2004 the first support package only supporting the new JDK will be SP21 (planned date for SP21 see http://service.sap.com/~sapidb/011000358700001130682005E),
     for SAP NetWeaver 2004s it will be SP14 (planned date for SP14 see http://service.sap.com/~sapidb/011000358700004584092005E).
So please plan a transition to the new JDK prior to the upgrade to these support packages.
SAP and IBM strongly believe that the switch to the new JDK will improve your experience with JAVA based SAP applications on AIX 5L. Both companies recommend upgrading to the new IBM JDK 1.4.2 for SAP applications running on AIX 5L as soon as it matches your companys maintenance plans.

You can download the JDK directly from the sun java website...
http://java.sun.com/products/archive/j2se/1.4.2_12/index.html
I don't think Ubuntu is supported...
Regards
Juan

Why can we only use 1 release class for overall Release of Purchase Req?

Hi,
After realizing that it would be beneficial to use more than one release class for overall release of Purchase Requisition with classification, in use with release groups for overall release, I now ask if someone knows why SAP has chosen to only allow 1 release class for overall release of Purchase Requisition?
In my scenario I would like Release group US, used for release strategies for US-plant to be able to use 1 release class with a specific set of characteristics.
For example class REL_PREQ_CLASS_OVERALL_VALUE_IN_USD including a characteristic PR_TOTVAL_USD looking at CEBAN-GFWRT. The chosen currency for this characteristic would be USD.
I would then like to allow Release group FR, used for release strategies for FRANCE-plant to use another release class with another set of characteristics.
For example class REL_PREQ_CLASS_OVERALL_VALUE_IN_EUR including a characteristic PR_TOTVAL_EUR looking at CEBAN-GFWRT. The chosen currency for this characteristic would be EUR.
In this way the release strategies for the respective release groups US and FR, could maintain their overall limit values in their respective release strategies in their own currencies.
1. Observe that I do not want to use the same Release class for both release groups for overall release, even though I know that this is currently the only allowed option, as far as I've understood.
2. Observe that I do not want to specify the two characteristics PR_TOTVAL_USD and PR_TOTVAL_EUR for overall value in the same release class, as this would lead to double maintenance for a large number of release strategies. Also consider the maintenance when new countries with new currencies want release strategies.
3. Observe that I only want to use overall release.
What I'm trying to avoid is having to continuously translate local business USD overall value limits to limits in the currency chosen for the overall value characteristic. If this for example is specified in DKK, this would lead to a need to adjust the overall value limits as soon as the exchange rate between USD and DKK changes in the system.
Please consider this simple example:
Local requirement is that USD purchase requisitions should be blocked when the USD value is above 1000 USD. However in my release strategy I would have to maintain a value of >5365 DDK, if DKK is chosen as the currency for overall characteristic.(e.g exchange rate 5,365).
Next month the currency exchange rate in the system between USD and DKK has changed, and therefore I would have to go into CL24N and maintain the value to reflect the new exchange rate between USD and DKK. Lets say it has gone up to 5,435. I would now have to maintain a value of > 5435 DKK in my release strategy to correctly reflect the local business requirement of 1000 USD.
So if anyone could please explain why SAP has taken the decision to make the Release class for overall release client specific that would be much appreciated and awarded accordingly. Also if you have any suggestion on how I could obtain the above scenario on maintaning overall value limits in different currencies than that would be awarded to.
BR Jakob F. Skott

You can give feed back to Apple from the iTunes drop-down menu in the iTunes menu bar..
You can also contact the iTS Customer Service from the links on this page - http://www.apple.com/support/itunes/store/
MJ

Release strategy for Scheduling Agreement(SA)

Dear Forum,
This issue is with regards to the release strategy for Scheduling Agreement(SA)
Until now release has only been applicable to contracts at our client site. But we now plan to introduce it for SA as well. Such a feature is available in SAP but the problem is that with the given release strategy GR is not allowed until the release is affected. The system allows you to post the delivery schedule.
Now what I want is that after making the SA the system should not allow to make delivery schedule if release is not affected.
We also have MRP run at client site..Kindly suggest the procedure as, how to configure it.Are der any User Exit for the same,if so please discuss..
Warm Regards
Nainesh
SAP ECC 6.0

Hi,
What's the SA Type that was created via MRP.
If it's LP (without release document), release will not do anything BUT
If it's LPA (release document), then you will not be able to Post the GR until release is affected.
Thanks.
Scheduling Agreement can be categories as
1) LP (without release document) and
2) LPA (with release document)
If use LP, you can do GR without release but with LPA, you need to release the schedule line via ME38.
Thanks.
NanoSAP
Posts: 58
Registered: 1/5/09
Forum Points: 6
   Re: release strategy for Scheduling Agreement(SA)
Posted: Jun 26, 2009 8:32 AM    in response to: sathish.kumar           Reply
Dear Mr.Satish,
Thanks a lot for your earliest reply...But my point is i want the system should not allow to make delivery schedule if release is not affected...Though schedule lines are generating through MRP run...Is is possible,by any chance...??

Error F5742 - While Releasing Billing for accounting

Hi,
We are getting an error F5742- Break down of hold back/retainage pay is allowed for only subledger accounts while releasing a billing document for accounting.
We are using installment payment terms for the billing.
we are not sure why system is trying to split the billing amount other than reconciliation accounts. One observation is that, we have duplicate line items in the billing.Not sure if this is causing the issue?
Please share your thoughts.
Thanks,
Mano.

HI,
I have identified the reason for the error,
These billing documents are created with a billing type FCR - NF Consignment fill up and in this case the invoice not getting charged to a customer account instead it is charged to GL account.
Since an installment payment terms YL33 has been used on these orders, system is trying to allocate the installment payment to the GL account and it is giving an error since it is not a sub ledger account.
we are changing peyment term on the sales order to a non-installement one.
Thanks,
Mano.

How to setup a release strategy for store generated purchase order

Hi there,
Does anybody know how to setup a release strategy for store/plant generated purchase order? I have a request from our client, but I never cross this before. Please help and let me know the step with every single detail.
Greatly thank for your help.
Kind Regards,
2tea

Please go thru the below Release Procedure and check whether you have maintained all the settings properly.
PO RELEASE STRATEGY
The release code is a two-character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
CT04 - Create Characteristic e.g. NETVALUE
Click Additional data Table name CEKKO Field name GNETW and press enter
(for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
In the Basic data (X refers to tick),
X Mutliple values
X Interval values
In the Value data, in the Char. value column, type >10000 and press enter
Save your data
CL02 - Class
Class - Create REL_PUR
Class type - 032
Click Create
Description - Release Procedure for Purchase Order
In the Same Classification section, click Check with error
In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
OMGS - Define Release Procedure for Purchase Order Type
Release Group - New entries
Rel.group Rel. Object Class Description
02 REL_PUR Rel. Strategy for PO
Release codes - New entries
Grp Code
02 01
Release indicators
Release indicators Release Description
0 Blocked
1 X Release
Release Strategy
Release group 02
Rel.strategy 01
Release codes 01
Release status 01
Classification Choose your check values
OMGSCK - Check Release Strategies
(make sure there are no error messages)
Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order.
The person with the release authorization have to use ME28 to release the Purchase Order.
Regards,
Ashok

11.1.2.3 maintenance release pre-req step

We are currently running Distributed installation of our production environment on version 11.1.2.1
Plan is to apply maintenance release 11.1.2.3 to existing 11.1.2.1
Going through document: Oracle® Enterprise Performance Management System Installation and Configuration Guide Release 11.1.2.3
Page 188
Apply any required PSEs before proceeding with maintenance the installation.
To review the list of defects fixed between earlier releases, use the Defects Fixed Finder. This
tool enables you to identify the products you own and your current implementation release.
With a single click, the tool quickly produces a customized report of fixed-defect descriptions
with their associated platforms and patch numbers. This tool is available here:
https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1292603.1
QUESTION:
=======
Ran the defect fixed finder tool as suggested above and it came up with list of defects fixed AFTER my current release 11.1.2.1
1) Since we are applying maintenance patch release 11.1.2.3 on top of 11.1.2.1 would it just suffice if we apply patches to address defects on top of 11.1.2.3 ALONE as a post maintenance patch step?
2) Since the instruction mentions "any required PSU's" -- is it ok we skip the PSU's for version 11.1.2.1 and proceed with maintenance upgrade -- will there be any problem with this approach. Please suggest.

I would question the requirement to install PSEs because in theory the maintenance release should be deploying the latest set of files/fixes and I would think it only relates to patches for the release you are currently running, this requirement was not in previous maintenance releases and with the software being released only a week ago it is difficult to give a definitive answer, maybe one to ask Oracle.
Cheers
John
http://john-goodwin.blogspot.com/

Adjusting AP Payment terms to allow for mail service

I am interested in adjusting the Accounts Payable process to release payments earlier than the payment terms (e.g. Net 30 payment would release for payment on 28th day) to allow for postal delays. Is that possible on across the board for all payees?

Hi Chris
In the automatic payment run(F110), in the parameters tab -> input a date which is two days ahead in the filed 'Customer items due by' and input todays date in the field 'Docs entered up to'
Ex: If the item is due on Sep 14 then input details as below
Docs enetered up to: 09/12/2014
Customer items due by: 09/14/2014
System will pick up all items due as of Doc entered up to date + till the date in Customer items due by.
Run the payment run the above inputs and check if the next few days due items are pulled into or not.
Thanks,
Sekhar

Purchase Order Release Strategies for Changed Amount

Hi Gurus,
We have a unique request from the business to set the release strategies for POs based on the Still to Deliver amount, not the Net Total Amount of the PO.
Example: Configuration is PO total amount <$5K requires only L1 approval. PO total amount >$5K requires L1 and L2 approval. PO was created for $8K and was release using L1 and L2 approvals. Receipts were posted to PO in the amount of $7K. Now the buyer has added an additional line item for $1K. The PO total amount now shows $9K ($8K + $1K), the Still to Deliver field shows only $2K ($1K from original remaining amount + $1K from new line item). Business wants the release strategy for this change order to go through L1 only since the Still to Deliver amount is <$5K.
Has anyone done this before? Any ideas??
Thanks,
Gabe

from http://help.sap.com/saphelp_40b/helpdata/fr/dd/2d547bb435d1118b3f0060b03ca329/content.htm
User exit M06E0004 is provided to enable you to adapt the release strategy determination process to meet your requirements.
This user exit allows you to change the communication structure for determining the release strategy for purchasing documents.
The following user fields are available:
USRC1
USRC2
USRN1
USRN2
In addition, communication structure CEKKOZZ is available, allowing you to use your own fields.

Regarding releasing procedure for p.o.

hi sapgurus,
the configuration for p.o. release procedure is working perfectly but whenever i go to me29n or me28 i am getting two step release procedure but in industry if the manager has given excess to me29n/me28 then himslef ca release the p.o by means of clicking both release steps, that means without general manager review the manager can release the p.o by means of clicking both. hence i am willing to restricate each user's acess to other stepd release procedure.
examaple
in me29n/me28 :-
1) manager.
2) general manager.
in this case i want the manager to click on his resepctive release step and should not allow to acess the general manager's relase step's.
thanking you
praveer

hi,
please visit
www.sap123.com
there is a thread which explain very clearly for the release procedure for PO.
In PR (With classification0 there is only difference , you use CEBAN communication structure instead of CEKKO for PO)
Regards,
vijay

Release procedure for p.o.

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 release

hi,
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

IBM AIX5L Maintenance Release allowable for 9.2.0.7

Similar Messages

Maybe you are looking for