R11i update PO need_by_date

Hi All,
It seems that there is impossible to update po need by date by using PO open interface.
Is it true?
We find that there is an API:PO_CHANGE_API1_S.UPDATE_PO, which can be use to update qty,price,promise_date, need_by_date in R12, but only qty,price,promise_date in R11i.
Is there any other standard API/Interface for updating need by date of existed POs?
Any Suggestions will be appreciated.
Best regards,
Zhxiang

Hi Zhxiang,
1. Po Need by Data can not be update using API/Interface
2. This Option is available in R12 but not in 11i.
As I believe there is no such interface/API through which you can update the need by date in PO.
Regards,
Jyoti

Similar Messages

Read Only Columns

Hi,
We have designed a update METADATE type custom integrator to download, update and re-upload data to Oracle Apps. As a part of the integrator we are displaying few extra columns for the end users viewing purpose. The client want us to make such view only columns as 'READ ONLY' and prevent any changes to them. They want such columns to either be greyed out or protected in order to prevent any changes. Is it possible to achieve this using WebADI? We tried updating the READ_ONLY_FLAG column in the table bne_interface_cols_b but it doesn't work as expected. This set-up allows the end user to update/make changes to the column in the excel sheet and throws an error only when the sheet is uploaded, not before that.
Any suggestions/help is appreciated. We are on R11i.
Thanks,
Nitin jain

As suggested, an update statement like below will address the issue in R11i:
update bne_layout_cols
set style = 'mso-protection:locked;'
where application_id = <>
and interface_code = <>
and sequence_num in <>;

Oracle North American Payroll Customers - US Q2 Statutory Updates Released

Dear Oracle North American Payroll Customer,
The United States (US) Second Quarter Statutory Update (Q2), 2006 has been released!
The following patches are available:
R11i: 4938760
R11: 4938760
Please be sure to carefully read ALL the readmes before beginning to install
these patches, to ensure successful processing!
The functional readmes are available on MetaLink:
US Q2 2006 Statutory Update Readme R11i - NOTE. 374042.1
US Q2 2006 Statutory Update Readme Rel 11 - NOTE. 374043.1
We would like to make you aware of several important points. Please read this entire note carefully.
1. US Q2 2006 Statutory Update Highlights
2. Other Important Notes
3. R11i HRMS Product Information
4. Payroll Recommended Patches
5. HR Recommended Patches
6. Global OHUG Conference
7. Other Information
8. Canadian Payroll Customers
A. US Q2 2006 Statutory Update Highlights
* JIT and School District Updates
* Miscellaneous Statutory Bug Fixes
Please refer to the readmes on Metalink for full details. See above for Note numbers.
B. Other Important Notes
Recorded TOIs (Transfer of Information) for the FPK RUP1 are available through Oracle University:
Go to the Oracle University url: http://ilearning.oracle.com/ilearn/en/learner/jsp/user_home.jsp
Select the Catalog tab
Search for the appropriate course or enter R12.
Note: You must be able to access the 'Knowledge Center' to view these TOIs. You may be required to purchase the Oracle University Knowledge Center Passport.
The Oracle University Knowledge Center Passport is the most cost-effective way to give multiple users the Oracle, PeopleSoft, and JD Edwards training they need. Provide your Enterprise with unlimited access to the entire catalog of web based OU Knowledge Center offerings. Your employees gain the opportunity to learn new skills, sharpen existing ones, and take advantage of thousands of web based classes to meet their ongoing training needs. As an added bonus, students can keep their valuable skills up-to-date with unlimited access to all new Oracle University Knowledge Center courses added within the one-year period from the date of purchase.
Patch Information:
- Enhanced Vertex Consolidated patch (5187702) this patch delivers all code updates/fixes that have been made to the enhanced tax interface since the 2005 Year End patches. It is included in this FPK RUP1 patch, but is also available as a stand alone patch 5187702.
- The Annual Geocode update (5253339) will be released in July 2006 and will be mandatory for Year End processing for both R11i and R11
- For Statutory patching requirements, please refer to the North American
Payroll Annual Patching Schedule document available on MetaLink. Note: 216109.1 <http://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=216109.1>
- US HR Customers: We will be releasing a US HR Rollup Patch (5179027) in August 2006 that will include the new Ethnic and Job categories required for 2007 reporting.
Desupport Information:
- Note: 329685.1/329689.1 Product Obsolescence / De-support Information: Oracle Corporation announces the end of Error Correction Support for E-Business Suite (Oracle Applications) version(s) 11.0 & 11.0.x on the following platform(s): ALL Platforms version(s) All, effective 31-JAN-2007. Oracle Corporation recommends customers upgrade/migrate to the following as soon as possible to maintain the highest level of support: Oracle E-Business Suite 11.5.7 or higher. For North American customers, 2006 will be the last year end supported. Quarterly updates beyond Q4 2006 will not be provided. No new JIT/Geocode updates will be provided beyond Q4/Year End. If new jurisdictions are added with a tax rate, no taxation will occur.
- As a result of the above de-support dates, Applications customers must upgrade to 9i in order to run 2006 Year End.
- If you are an 11.0.3 customer, please see Note: 329685.1.
- Please note that Tax and Legislative updates are not available for products during the 'extended support' phase. Please see note 334749.1 <https://metalink.oracle.com/metalink/plsql/showdoc?db=NOT&id=334749.1> for specific details regarding the availability of legislative patches.
- Discoverer 4i de-support. Reference note 237607.1 ALERT: Required and Recommended Patch Levels for All Discoverer Versions
- For Oracle HRMS Product Family - Release 11i Information, see note 135266.1.
Year End Information for Payroll:
o All mandatory patches are required for R11
o The Annual Geocode update (5253339) will be released in July 2006 and will be mandatory for Year End processing for both R11i and R11
o The HRMS Family Pack K Rollup patch is mandatory for R11i for Year End and is a pre-requisite for the Year End Phase 1 patch.
o Year End Phase 1 will be released on Sept 30th, Year End Phase 2 (includes Q4) will be released on Dec 15th, Year Begin will be released as a one-off (also included in Phase 2) on Dec 15th and Year End Phase 3 will be released on January 15th, 2006. Due to statutory or late breaking updates, the Jan 15th date is subject to change.
o Like last year, Year End Phase 2 and Phase 3 will be offered as incremental patches ONLY. Cumulative versions will not be released. This means that Year End Phase 1 is a pre-requisite to Year End Phase 2 and 3. Incremental patches do not require the application of a new HR legislative data install (hrglobal). Customers only need to apply the hrglobal driver currently installed.
Note: FPK RUP1 is a pre-requisite for Year End Phase 1. Year End Phase 1 is a pre-requisite for Year Begin. As in the past several years, Year Begin should be applied for any client going live in 2007.
For the complete R11i Payroll Mandatory Patch List see Metalink Note 111499.1 <http://metalink.oracle.com/metalink/plsql/showdoc?db=NOT&id=111499.1>
For the complete R11 Payroll Mandatory Patch List see Metalink Note 74293.1 <http://metalink.oracle.com/metalink/plsql/showdoc?db=NOT&id=74293.1>
For additional non-mandatory North American Payroll patches see Metalink Note 74292.1 <http://metalink.oracle.com/metalink/plsql/showdoc?db=NOT&id=74292.1>
C. R11i HRMS Product Information
For the latest Oracle HRMS Product Family - Release 11i Information,
please see Metalink Note:135266.1
This page contains important information including:
o High Priority Alerts
o Mandatory Patches
o Family Packs and Minipacks
o Latest Legislative Data - hrglobal.drv
o Maintenance Pack Information
D. Payroll Recommended Patches
The Payroll recommended patch spreadsheet Metalink Note 74292.1 contains additional features and functions.
E. HR Recommended Patches
We have created an HR Recommended patch spreadsheet similar to the Mandatory Payroll patch spreadsheet on Metalink. This new spreadsheet contains a list of patches needed to be in compliance for HR Statutory reporting i.e. EEO-1, VETS-100 etc.
The spreadsheet is located on Metalink in Note number: 273196.1
F. Global OHUG Conference
2006 Fall OHUG Conference
Location: Orlando Florida
Dates: November 29 - December 1
Hotel: Rosen Shingle Creek
Hotel Reservations: 866-996-9939 refer to the OHUG rate of $165.00 a night. http://rosenshinglecreek.com/
G. Other Information Sources
1. MetaLink - http://metalink.oracle.com <http://metalink.oracle.com/>
MetaLink is a customer resource provided by Oracle World-wide Support.
The Applications section of Metalink contains all the latest product documentation and documentation updates for Oracles products.
2. Payroll World
Payroll World is an email distribution list for North American Oracle Payroll customers used to quickly disseminate information regarding product updates, patches, and statutory changes. To be added to this email distribution list, send e-mail to: [email protected] <mailto:[email protected]>
Subject: Oracle North American Payroll World Contact Update with your contact name, CSI number, and company name
3. Metalink Service Request profiles:
Please update all Service Request profiles on Metalink with any updates to Database Version, Product Version, and/or contact information
Metalink->UserProfile button
4. Information for NEW North American Payroll customers:
A pamphlet is available for all North American Payroll customers explaining Vertex, Payroll World, SIG's, etc.
The North American Payroll Handout document can be located in Metalink Note 316077.1
H. Canadian Payroll Customers
A reminder to Canadian Payroll customers that the Payroll Tax Q Series
(Quantum) version 2.7.6 program (patch 5326425) and the June data file are required for the tax changes effective July 1, 2006. Please note that Quantum 2.7.6 has a Canadian pre-req of patch 5223777. The Federal and Alberta basic personal amount changes effective July 1, 2006 are available with patch 5237516.

We need to know the new codes which will be added and which if any will be replaced. We know those identified on the US Gov site but can Oracle Dev. provide the specifics in advance so we can update our Employment Applications etc to match Oracle HR definitions?
Regards,
Ed

ATTN: Oracle North American HCM Customers: Q1 2007 Statutory Update Release

Dear Oracle North American HCM Customer,
The United States (US) First Quarter Statutory Update (Q1), 2007 has been released!
Patch number:
* R11i: 5917868
*Note: The Q1 2007 Statutory patch does not include the Year End patches, but it does pre-req the Year End Phase 3 patch.
The functional readme is available on MetaLink:
US Q1 2007 Statutory Update Readme R11i - NOTE. 421114.1
Please be sure to carefully read the readme before beginning to install this patch, to ensure successful processing!
We would like to make you aware of several important points. Please read this entire note carefully.
A. Q1 2007 Highlights
B. Other Important Notes
C. R11i HRMS Product Information
D. Payroll Recommended Patches
E. HR Recommended Patches
F. Global OHUG Conference
G. Other Information
A. Q1 2007 Highlights
* JIT and School District Updates
* Miscellaneous Statutory Bug Fixes
Please refer to the readme on Metalink for full details. See above for Note number.
B. Other Important Notes
Checkwriter/Deposit Advice:
Oracle will de-support the Live Checkwriter and Deposit Advice for US and Canada beginning with EOY Phase 1 in September. Archive Checkwriter and Deposit Advice will continue to be supported. What this means is that new code changes and bug fixes will not be tested on the Live Checkwriter and Deposit Advice. Additionally, enhancements made to the Archive version will NOT be made for the Live version.
*Note: If you would like to view the output of the archive version of this report without needing pre-printed stationery, try the following in a test instance:
disable the trigger pay_action_parameters_ari
insert a row in pay_action_parameters with the following value -
name=PRINT_REPORT_LABELS
value=PAYUSCDA
enable the trigger pay_action_parameters_ari
Run the report. This will print the labels and make it easier to check the report without needing pre-printed stationery.
In early summer, we are targeting release of an XML version of Checkwriter and Deposit Advice.
R12 Released:
We are pleased to announce the availability of Oracle Applications E-Business Suite Release 12, the Global Business Release. Release 12 is currently available for both new and upgrading customers on all supported languages through Oracle E-Delivery and the Oracle Store. Please check EPD for specific Platform availability and continue to check E-Delivery for additional Platforms to be available.
References:
E-Business Suite Release 12 on Oracle.com
<http://www.oracle.com/applications/e-business-suite-release.html>
R12 Information Center on MetaLink
<https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=401740.1>
Documentation Roadmap on MetaLink
<https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=394692.1>
Translation Information on MetaLink
<https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=405992.1>
Note: E-Business Suite Release 12 will NOT be a requirement for
processing 2007 year end.
HCM Configuration Workbench:
HCM Configuration Workbench Rollup Patch 5 (5135963 ) has been released to Oracle MetaLink for customer download.
This patch delivers the HRMS Configuration Workbench HRMS Family Pack K
Delta RUP1 Certification patch, for more information please refer to the Readme of this patch and navigate to the ‘E. New Features in Patch 5135963’ section of the readme to see more details.
Year End Information for Payroll:
The HRMS Family Pack K Rollup 2 patch will be mandatory for R11i for Year End and is a pre-requisite for the Year End Phase 1 patch.
For the complete R11i Payroll Mandatory Patch List see Metalink Note
111499.1
For the complete R11 Payroll Mandatory Patch List see Metalink Note 74293.1
For additional non-mandatory North American Payroll patches see Metalink Note 74292.1
C. R11i HRMS Product Information
For the latest Oracle HRMS Product Family - Release 11i Information, please see Metalink Note:135266.1 This page contains important information including:
* High Priority Alerts
* Mandatory Patches
* Family Packs and Minipacks
* Latest Legislative Data - hrglobal.drv
* Maintenance Pack Information
D. Payroll Recommended Patches
The Payroll recommended patch spreadsheet Metalink Note 74292.1 contains additional features and functions.
E. HR Recommended Patches
The HR Recommended spreadsheet contains a list of patches needed to be in compliance for HR Statutory reporting i.e. EEO-1, VETS-100 etc. The spreadsheet is located on Metalink in Note number: 273196.1
F. Global OHUG Conference
Mark your calendar!
The Global OHUG 2007 Conference will be held in Las Vegas, Nevada!
Monday, September 24th - Thursday, September 27th
Location:
* Paris Hotel & Casino, Las Vegas, Nevada - Hotel Contact Number:
888-266-5687 refer to the OHUG (Oracle HCM Users Group) group rate of
$179.00 a night
Visit www.ohug.org for more information.
G. Other Information
1. MetaLink - http://metalink.oracle.com
MetaLink is a customer resource provided by Oracle World-wide Support. The Applications section of Metalink contains all the latest product documentation and documentation updates for Oracle’s products.
2. Payroll World
Payroll World is an email distribution list for North American Oracle Payroll customers used to quickly disseminate information regarding product updates, patches, and statutory changes. To be added to this email distribution list, send e-mail to: [email protected] <mailto:[email protected]>
Subject: Oracle North American Payroll World Contact Update with your
contact name, CSI number, and company name
3. Metalink Service Request profiles:
Please update all Service Request profiles on Metalink with any updates to Database Version, Product Version, and/or contact information Metalink->UserProfile button
4. Information for NEW North American Payroll customers:
A pamphlet is available for all North American Payroll customers explaining Vertex, Payroll World, SIG's, etc.
The North American Payroll Handout document can be located in Metalink
Note 316077.1
Regards,
Greg

We need to know the new codes which will be added and which if any will be replaced. We know those identified on the US Gov site but can Oracle Dev. provide the specifics in advance so we can update our Employment Applications etc to match Oracle HR definitions?
Regards,
Ed

Updating unit_price in PO_LINES for a Blanket Purchase Agreement

Hello,
In R11i, 'PO_CHANGE_API1_S.update_po' was the API we call to achieve the price update of blanket PO.
This api in turn calls 'PO_DOCUMENT_UPDATE_GRP'.
The api 'PO_DOCUMENT_UPDATE_GRP' has two overloaded procedures 'update_document'.
a. 'update_document' with 18 parameters is not suited for R12 as per oracle api documentation.
b. Thus, we have to call 'update_document' with 12 parameters for achieving the objective.
Thus, I tried to update price using the following sample code attached. But am hitting on few issues,
a. If I do not pass 'release' or 'shipments' or 'distributions' information as part of this api call, the api fails at the validation indicating 'Invalid Doc Id'.
b. If I do pass 'release' or 'shipments' or 'distributions' information, inside the api for 'some' reason, they reassign the po_header_id as 'NULL' and cause of that in another validation block inside the same API it throws an error indicating 'Releases have no lines'.
I have to admit my search in metalink/other forums has not really helped me to find out how to 'update a blanket purchase agreement'.
Please advise.
Thanks,
Santhosh
sample code (without shipment/releases/distributions):
DECLARE
lv_var            VARCHAR2(2000) := NULL;
lr_changes        PO_CHANGES_REC_TYPE;
x_api_error       PO_API_ERRORS_REC_TYPE;
x_return_status   VARCHAR2(4000);
dummy             NUMBER;
BEGIN
lr_changes := PO_CHANGES_REC_TYPE(21696 -- header id
+,NULL -- release id+
+,PO_LINES_REC_TYPE(po_tbl_number(54121) -- line id+
+,po_tbl_number(100) -- price+
+,po_tbl_varchar30(NULL) -- vendor product num+
+,po_tbl_number(NULL) -- quantity+
+,po_tbl_date(NULL) -- start date+
+,po_tbl_date(NULL) -- expiration date+
+,po_tbl_number(NULL) -- amount+
+,po_tbl_varchar30(NULL) -- request uom+
+,po_tbl_number(NULL) -- secondary_quantity+
+,po_tbl_varchar30(NULL) -- request sec uom+
+,po_tbl_varchar1(NULL) -- delete record+
+,po_tbl_varchar240(NULL) -- preferred_grade+
+,po_tbl_number(NULL) -- quantity+
+,po_tbl_varchar30(NULL) -- unit meas lookup code+
+,po_tbl_number(NULL) -- item id+
+,po_tbl_number(NULL) -- from header id+
+,po_tbl_number(NULL) -- from line id+
+,po_tbl_varchar1(NULL) -- has ga reference+
+,po_tbl_varchar1(NULL) -- cancel flag+
+,po_tbl_varchar30(NULL) -- closed code+
+,po_tbl_varchar30(NULL) -- value basis+
+,po_tbl_varchar30(NULL) -- purchase basis+
+,po_tbl_number(NULL) -- amount+
+,po_tbl_date(NULL) -- start date+
+,po_tbl_date(NULL) -- expiration date+
+,po_tbl_number(NULL) -- unit price+
+,po_tbl_number(NULL) -- from line location id+
+,po_tbl_number(NULL) -- secondary quantity+
+,po_tbl_varchar30(NULL) -- secondary uom+
+,po_tbl_varchar40(NULL) -- item number+
+,po_tbl_varchar240(NULL) -- preferred grade+
+,po_tbl_varchar1(NULL) -- from price break+
+,po_tbl_number(NULL) -- from line location id+
+,po_tbl_number(NULL) -- base unit price+
+,po_tbl_varchar1(NULL) -- manual price change flag+
+,po_tbl_varchar30(NULL) -- new secondary uom+
+)+
+,PO_SHIPMENTS_REC_TYPE(po_tbl_number(NULL) -- line location id+
+,po_tbl_number(NULL) -- quantity+
+,po_tbl_date(NULL) -- promised date+
+,po_tbl_number(NULL) -- price override+
+,po_tbl_number(NULL) -- parent line location id+
+,po_tbl_number(NULL) -- split shipment num+
+,po_tbl_date(NULL) -- need by date+
+,po_tbl_number(NULL) -- ship to location id+
+,po_tbl_date(NULL) -- sales order update date+
+,po_tbl_number(NULL) -- amount+
+,po_tbl_varchar30(NULL) -- request uom+
+,po_tbl_number(NULL) -- secondary quantity+
+,po_tbl_varchar30(NULL) -- request secondary_uom+
+,po_tbl_varchar1(NULL) -- delete record+
+,po_tbl_varchar240(NULL) -- preferred grade+
+,po_tbl_varchar30(NULL) -- payment type+
+,po_tbl_varchar240(NULL) -- description+
+,po_tbl_varchar25(NULL) -- new supplier order num+
+,po_tbl_number(NULL) -- po line id+
+,po_tbl_number(NULL) -- quantity+
+,po_tbl_varchar30(NULL) -- unit meas lookup code+
+,po_tbl_varchar1(NULL) -- cancel flag+
+,po_tbl_varchar30(NULL) -- closed code+
+,po_tbl_number(NULL) -- item id+
+,po_tbl_number(NULL) -- ship to organization id+
+,po_tbl_varchar1(NULL) -- drop ship flag+
+,po_tbl_number(NULL) -- quantity received+
+,po_tbl_number(NULL) -- quantity billed+
+,po_tbl_number(NULL) -- amount received+
+,po_tbl_number(NULL) -- amount billed+
+,po_tbl_varchar1(NULL) -- accrue on receipt flag+
+,po_tbl_varchar30(NULL) -- value basis+
+,po_tbl_varchar30(NULL) -- purchase basis+
+,po_tbl_number(NULL) -- amount+
+,po_tbl_number(NULL) -- price override+
+,po_tbl_number(NULL) -- parent quantity+
+,po_tbl_number(NULL) -- parent amount+
+,po_tbl_number(NULL) -- secondary quantity+
+,po_tbl_varchar30(NULL) -- secondary uom+
+,po_tbl_varchar40(NULL) -- item number+
+,po_tbl_date(NULL) -- approved date+
+,po_tbl_varchar1(NULL) -- encumbered flag+
+,po_tbl_varchar30(NULL) -- shipment type+
+,po_tbl_number(NULL) -- quantity shipped+
+,po_tbl_varchar240(NULL) -- preferred grade+
+,po_tbl_varchar30(NULL) -- payment type+
+,po_tbl_varchar1(NULL) -- from price break+
+,po_tbl_varchar1(NULL) -- manual price change flag+
+,po_tbl_varchar1(NULL) -- sec qty grade change only+
+)+
+,PO_DISTRIBUTIONS_REC_TYPE(po_tbl_number(NULL) -- po distribution id+
+,po_tbl_number(NULL) -- quantity ordered+
+,po_tbl_number(NULL) -- parent distribution id+
+,po_tbl_number(NULL) -- split shipment num+
+,po_tbl_number(NULL) -- amount ordered+
+,po_tbl_varchar30(NULL) -- request uom+
+,po_tbl_varchar1(NULL) -- delete record+
+,po_tbl_number(NULL) -- po line id+
+,po_tbl_number(NULL) -- line location id+
+,po_tbl_number(NULL) -- quantity ordered+
+,po_tbl_varchar30(NULL) -- unit meas lookup code+
+,po_tbl_number(NULL) -- item id+
+,po_tbl_number(NULL) -- quantity delivered+
+,po_tbl_number(NULL) -- quantity billed+
+,po_tbl_number(NULL) -- amount delivered+
+,po_tbl_number(NULL) -- amount billed+
+,po_tbl_varchar30(NULL) -- value basis+
+,po_tbl_varchar30(NULL) -- purchase basis+
+,po_tbl_number(NULL) -- amount ordered+
+,po_tbl_number(NULL) -- parent line location id+
+,po_tbl_number(NULL) -- award id+
+,po_tbl_number(NULL) -- project id+
+,po_tbl_number(NULL) -- task id+
+,po_tbl_number(NULL) -- distribution num+
+,po_tbl_varchar1(NULL) -- encumbered flag+
+,po_tbl_number(NULL) -- req distribution id+
+,po_tbl_date(NULL) -- creation date+
+)+
+);+
dbms_output.put_line('BEFORE API');
fnd_global.apps_initialize
+(user_id => 8171+
+,resp_id =>20707+
+,resp_appl_id => 201+
+);+
dbms_application_info.set_client_info(201);
mo_global.init('PO');
FOR i IN 1..2
LOOP
BEGIN
PO_DOCUMENT_UPDATE_GRP.update_document
+(p_api_version => '1.0'+
+,p_init_msg_list => NULL+
+,x_return_status => x_return_status+
+,p_changes => lr_changes+
+,p_run_submission_checks => NULL+
+,p_launch_approvals_flag => NULL+
+,p_buyer_id => NULL+
+,p_update_source => NULL+
+,p_override_date => NULL+
+,x_api_errors => x_api_error+
+,p_approval_background_flag => NULL+
+,p_mass_update_releases => NULL+
+);+
EXCEPTION
WHEN OTHERS THEN
dbms_output.put_line ('SQLERRM <'||SQLERRM||'>');
END;
dbms_output.put_line('value of x_return_status<'||x_return_status||'>');
dbms_output.put_line ('SQLERRM <'||SQLERRM||'>');
dbms_output.put_line ('get msg <'||fnd_message.get||'>');
dbms_output.put_line('value of message_name <'||x_api_error.message_name(1)||'>');
dbms_output.put_line('value of message_name <'||x_api_error.message_text(1)||'>');
END LOOP;
EXCEPTION
WHEN OTHERS THEN
dbms_output.put_line ('SQLERRM <'||SQLERRM||'>');
dbms_output.put_line('value of x_return_status<'||x_return_status||'>');
END;
+/+

Hi Alister,
You can't create a release of a BPA through API, there is no such APIs provided by oracle.
Where as you can create a BPA by using API. You need to dump/poplulate data in PO_headers_interface & PO_Lines_intreface table.. Then use Purchasing Documents Open Interface API to create a BPA.
Regards,
S.P DASH

[12.1.2] Forms Perso : Updating a DFF at PO_LINES level in the PO screen

Hello
In the PO screen (POXPOEPO), I'd like to maintain some consistency between 3 dates fields at PO_LINE level, according to some business rules, with Forms Perso.
2 dates fields are the standard ones, PROMISED_DATE and NEED_BY_DATE, the third one is a DFF ATTRIBUTE1
e.g : If I modify the PROMISED_DATE, I'm using the PO_LINES.NEED_BY.NEW_ITEM_INSTANCE to modify the 2 other fields.
With an action "Property", Object Type = "Item" and PO_LINES.NEED_BY.Value = '...' or PO_LINES.ATTRIBUTE1.Value = '...'
It works for the NEED_BY_DATE field, it is correctly updated.
But the DFF ATTRIBUTE1 is cleared instead of being updated ? With the same code as the NEED_BY_DATE field
The DFF is defined with the value set FND_STANDARD_DATETIME, which requires to have a format DD/MM/RRRR HH24:MI:SS
If someone has any experience in modifying DFF with Forms Perso, I would like to understand why I obtain such a behavior, and if possible have some tips about doing what I'd like to do.
Take care,
Xavier
Edited by: Xavier_Vlieghe on 18 août 2011 09:41

I think date formatting is involved in my problem.
Here are the date format settings in OA :
Profile option "ICX Date format" = '31/12/1999' for my user and '31-DEC-1999' at site level
My DFF ATTRIBUTE1 has a date format like this in the GUI (PO screen) : "23/09/2011 00:00:00"
But I don't know what settings is used to format this data ?
If I do a query on the data I have the following :
ATTRIBUTE1
2011/09/23 00:00:00
If PROMISED_DATE = '20/09/2011 00:00:00', and I want to add 3 days for populating the date in ATTRIBUTE1, I have tested the following :
1/ try to fit GUI date format:
PO_LINES.ATTRIBUTE1.VALUE = TO_CHAR((TO_DATE(:PO_LINES.PROMISED_DATE, 'DD/MM/RRRR HH24:MI:SS') + :GLOBAL.XX_LOAD), 'DD/MM/RRRR HH24:MI:SS')
Result in DFF : field cleared !
(same thing by replacing RRRR by YYYY)
The "Validate" button in the Forms Perso screen is yet showing a nice result, "23/09/2011 00:00:00"
2/ try to let GUI format the data:
PO_LINES.ATTRIBUTE1.VALUE = (TO_DATE(:PO_LINES.PROMISED_DATE, 'DD/MM/RRRR HH24:MI:SS') + :GLOBAL.XX_LOAD)
Result in DFF : '11/09/0023 00:00:00' (field is updated with a value now!)
(same thing by replacing RRRR by YYYY)
The "Validate" button in the Forms Perso screen is showing the result, "23-SEP-11"
I must admit I'm a little lost with this topic, if anyone has an explanation on which date format parameter is applied in the GUI (and also how to solve my problem), I would appreciate :)

[11i] Forms Perso : Updating a DFF at PO_LINES level in the PO screen

Hello
In the PO screen (POXPOEPO), I'd like to maintain some consistency between 3 dates fields at PO_LINE level, according to some business rules, with Forms Perso.
2 dates fields are the standard ones, PROMISED_DATE and NEED_BY_DATE, the third one is a DFF ATTRIBUTE1
e.g : If I modify the PROMISED_DATE, I'm using the PO_LINES.NEED_BY.NEW_ITEM_INSTANCE to modify the 2 other fields.
With an action "Property", Object Type = "Item" and PO_LINES.NEED_BY.Value = '...' or PO_LINES.ATTRIBUTE1.Value = '...'
It works for the NEED_BY_DATE field, it is correctly updated.
But the DFF ATTRIBUTE1 is cleared instead of being updated ? With the same code as the NEED_BY_DATE field
If someone has any experience in modifying DFF with Forms Perso, I would like to understand why I obtain such a behavior, and if possible have some tips about doing what I'd like to do.
Take care,
Xavier

Xavier_Vlieghe wrote:
Sorry for duplicate message, I don't know how it occurs as I just click once on "Post message" ?
This one can be deletedOriginal post -- [12.1.2] Forms Perso : Updating a DFF at PO_LINES level in the PO screen
Locking this thread.

Pre-requisite packages required for Oracle R11i

Hi Gurus,
I am new to DBA.I am working with oracle 11i cloning.In that task is to pre-clone from source system(os:Red Hat-4.0) and do post clone in target system in which I installed new os(os:Red Hat-4.0).
Here I need your help.What are all the pre-requisite packages required for Oracle R11i before configuring the Target System and how to apply the pre-requisite packages.
Could you please help me.
Thanks
Vinoth

Hi;
Here I need your help.What are all the pre-requisite packages required for Oracle R11i before configuring the Target System and how to apply the pre-requisite packages. Imagine you are making new installation on your target server. So you need to check all pre-req which is mention in below notes. You need to have all rmp hosts file edit and some other steps.
Please see:
Subject: Recommendations to Install Oracle Applications 11i Doc ID: 294932.1
Oracle Applications 11.5.10 - Installation Update Notes for Linux x86, Solaris SPARC, MS Windows, HP-UX PA-RISC, HP-Tru64, IBM AIX - B13590-01 [ID 287453.1]
Oracle Applications Installation Update Notes, Release 11i (11.5.10.2) [ID 316806.1]
PS: I suggest also see my blog http://heliosguneserol.wordpress.com/2010/05/31/cloning-oracle-applications-release-11-and-12/
Regard
Helios

Updating Salespersons in Multi-Org Environment

Has anyone devised an easy way to update salespersons in a Multi-Org Environment? The application requires you to update the salesperson at the address site level and frequent changes in personnel can force massive amounts of data entry time.
Any ideas?

Hi
I have a setup document for R12 AME regarding invoice approval process.
However i need to find out if i have the same for R11i.
I am not sure whether R12 ame approval doc will be of any help for you, however i can forward you the same if you need it.
Thanks
Manish Jain.

Flex 4.7 update

Hi,
I have the last update and when trying to update it, it indicates me that the serial is good but no installation found to link with.
I'm completely lost.
I have Flex Builder 4.6.
What's hapening?

Hi,
Make sure you source the application env file, and use the complete syntax as outlined in the following document.
$ f60gen module=<form name>.fmb userid=apps/<apps password> output_file=<form name>.fmx module_type=form batch=yes compile_all=special
Note: 742617.1 - How do I Generate Forms in R11i or R12?
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=742617.1
Regards,
Hussein

US Oracle Payroll Customers - Q1 2006 Statutory Update Released

The United States (US) First Quarter Statutory Update (Q1), 2006 has been released. The following patches are available:
R11i: 4938757
R11: 4938757
US Q1 2006 Statutory Update Readme R11i - NOTE.363051.1
US Q1 2006 Statutory Update Readme Rel 11 - NOTE.363050.1
Regards,
Greg
Message was edited by:
HCMgaclark

At OpenWorld, the developers said that XML Checkwriter and Deposit Advice would be available in version 12.6. I don't recall the expected date of release.

US Oracle Payroll Customers: Urgent Update

Dear US Payroll Customer,
We would like to make you aware of two important items. Issues have been discovered in the SQWL output files for the states of Michigan and Massachusetts that may cause the files to be rejected. The following two patches should be applied if you submit SQWL files in these states.
The Q1 2006 Update (4938757) is a pre-req for both of these patches. If you do not file in these two states you may disregard this update. These fixes will be included in the Q2 2006 update.
1) Michigan: Patch 5183542 is now available. You only need to apply this patch if you are required to complete quarterly reporting for the State of Michigan.
2) Massachusetts: Patch 5196285 is now available. You only need to apply this patch if you are required to complete quarterly reporting for the State of Massachusetts.
R11i HRMS Product Information
For the latest Oracle HRMS Product Family - Release 11i Information, please see Metalink Note:135266.1 -
http://metalink.oracle.com/metalink/plsql/showdoc?db=NOT&id=135266.1
This page contains important information including:
o High Priority Alerts
o Mandatory Patches
o Family Packs and Minipacks
o Latest Legislative Data - hrglobal.drv
o Maintenance Pack Information
Payroll Recommended Patches
The Payroll recommended patch spreadsheet Metalink Note 74292.1 contains additional feature functionality.
HR Recommended Patches
We have an HR Recommended patch spreadsheet similar to the mandatory Payroll patch spreadsheet on Metalink. This spreadsheet contains a list of patches needed to be in compliance for HR Statutory reporting i.e. EEO-1, VETS-100 etc. The spreadsheet is located on Metalink in Note number: 273196.1
Other Information
1. MetaLink - http://metalink.oracle.com <http://metalink.oracle.com/>
MetaLink is a customer resource provided by Oracle World-wide Support.
The Applications section of Metalink contains all the latest product documentation and documentation updates for Oracles products.
2. Payroll World
Payroll World is an email distribution list for North American Oracle Payroll customers used to quickly disseminate information regarding product updates, patches, and statutory changes. To be added to this email distribution list, send e-mail to: [email protected] <mailto:[email protected]>
Subject: Oracle North American Payroll World Contact Update with your contact name, CSI number, and company name
3. Metalink Service Request profiles:
Please update all Service Request profiles on Metalink with any updates to Database Version, Product Version, and/or contact information
Metalink->UserProfile button
4. Information for NEW North American Payroll customers:
A pamphlet is available for all North American Payroll customers explaining Vertex, Payroll World, SIG's, etc.
The North American Payroll Handout document can be located in Metalink Note 316077.1

There's no localization for payroll all IL companies use local software for payroll and import the accouting to GL.
You can can contact me if you need any more informations and advices
Michael Saghroun
[email protected]

Tecra M9-136 - BSOD during Vista SP2 update

Tecra M9-136 asked this morning to update to Vista SP2 and during the process the BSOD 0x0000007E arrived. Restarted in Safe Mode and the installer continued and then finally reported that the update had failed - and reverted to SP1. This took most of the morning.
It will start in Safe Mode but on a normal boot-up, Vista SP1 gets through the fingerprint recognition and then fails with the same BSOD (it doesn't get as far as displaying the desktop).
The laptop has BIOS level 1.80. I've tried in Safe mode to install 1.90 but it tells me that the battery has insufficient charge and the power adapter isn't attached. Both untrue.
Stuck - need advice. Could this be a hard fault? Can't see how I can update anything if it's a soft fault.
thanks

The message with the BSOD mentioned checking BIOS and driver versions. Anyway, no change made to that.,
I tried System Restore but the only available restore point was the SP2 installation. I thought Vista was supposed to save a restore point every 24 hours even if nothing new had been installed.
I've now found in System Information / Windows Error Reporting several messages like this:
28/09/2009 12:08 Windows Error Reporting Fault bucket 0x7E_NULL_IP_DRVNDDM+57bd, type 0
Event Name: BlueScreen
Response: None
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
C:\Windows\Minidump\Mini0928 09-04.dmp
C:\Users\me\AppData\Local\Te mp\WER-75660-0.sysdata.xml
C:\Users\me\AppData\L ocal\Temp\WER7D78.tmp.version.txt
& #x000d;
These files may be available here:
C:\Users\me\AppData\Local\Mic rosoft\Windows\WER\ReportArchive\Report06d1c4b5

Cannot open and update IPhoto after upgrading to OXYosemite

From the App store, I downloaded and installed OXYosemite. There are 2 more updates available: iPhoto and iMovie. When I try to upload them, the notice I get is "Update Unavailable with This Apple ID This update is not available for this Apple ID either because it was bought by a different user or the item was refunded or cancelled."
I have 2 apple IDs when I inquire about my ids. Signing in App Store with either of them, doesn't resolve the problem. I get the same notice. iTunes, Mac, mobile downloads, all use the same apple IP, only for the computer downloads from App Store isn't working.
What should I do?
Thanks, Sev

I have the same problem and can't find out how to correct it. Unable to update iPhoto or iMovie .. I get the same message as above user. Help!

Error message: "playlists selected for updating no longer exist"

I tried to update my ipod nano and I guess I had deleted a playlist, but since then, I have not been able to update. Every time I try, I get the following message:
"Cannot be updated because all of the playlists selected for updating no longer exist."
I haven't been able to highlight which playlists are selected to begin with.
I read through the manual and thought that maybe rebooting the whole system might work. So I deleted Itunes from my computer and re-installed.
Then I tried re-setting my ipod. So now I have nothing on my ipod.
I also deleted everything from my library, thinking it might help to start from scratch. Nothing has worked.
How do I "select" and "unselect" playlists so I can get up and running again?

Here you go.
http://discussions.apple.com/thread.jspa?messageID=607312&#607312

R11i update PO need_by_date

Similar Messages

Maybe you are looking for