Validity periods for Item Conditions - Purchasing Agreements

hi,
For Agreements (Purchasing) we are looking for creating multiple validity periods for item conditions. We cannot use BTCI for transaction ME31K as it does not allow to create multiple validity periods at one time!
Are there any BAPIs for the same? Is there any other way??
Thanks in advance.
regards,
NB

Hi
Working with eCATT (Extended Computer Aided Test Tool)
Try this.
http://www.erpgenie.com/ecatt/
Thanks
Ashok

Similar Messages

API or interface table to create releases for a blanket purchase agreement

Hi
I need to know if Oracle provides a standard API or interface table to create releases for a blanket purchase agreement.
I tried using the release_num field in PO_HEADERS_INTERFACE, PO_LINES_INTERFACE. But this is not working.
I'm able to create the blanket purchase agreement using the open interfaces, but not the releases.
Regards,
Alister

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

Validity period for Mediclaim on ESS

Hi All,
I am facing following problem in case of Claims:
For medical claim in table V_T7INAA i have maintained 1 year.
When i execute PC00_M40_REMS report here i am getting correct validity period for mediclaim from 01.04.2010 to 31.03.2011
but when employee log into ESS validity period is appearing as 01.04.2010 to 31.03.2012
I have checked all the settings in R/3. I do not understand from wher this 31.03.2012 date is coming cause ESS will fetch data from R/3 and in R/3 everything seems to be correct.
Thanks & Regards,
Neha

Hi,
Wel no we have not implemented any exit. we using standard settings only.
I am clueless from wher its picking up these changed dates. Cause on R/3 dates are appearing perfectly fine.
Neha Desai

How to give validity period for tax codes

In fv12 menu the validity period in display mode how to change and give validity period for a tax code

in fv12 you can change the validity period and for the new validity period maintain another record in fv12
Validity from and to by changing the old validity period upto when that is applicable

How to give valid period for tcodes

Hi all,
i have a question how to give a valid period for tcodes.
Thanks&regards,
rani.

You can't.
You can set validity dates for roles - you do this in the roles section of the user master record
If you need a t-code to be locked for <b>everyone</b> for certain periods then you can look into a custom prog that uses tx SM01, though it usually is not a worthwhile control to mitigate the particular risk.

Validity period for services in ITS

We are on Extended classic scenario with EBO 4.0 and wanted to have service order created.
When I log into ITS server
Shop -> Describe Requirement ->
I have Description, Internal Note, Quantity, Price, Category and Required on.
However I want "From date" and "To date" instead of just Required on date
Is there any configuration setting that needs to be enabled to have validity period for services.
Any help would be highly appreciated.

Hi,
This is strange!At my place,I can see the foll fields when i goto DESCRIBE REQUIREMENT "link:
Describe Requirement
You can describe your requirement if you are unable to find it in the catalog.
Product Type Goods Services
Description
Internal Note
Quantity
Price
Category
Required BetweenOnFrom -
Pls check whether any BADI(like BBP_SC_UI_CTRL/BBP_SC_MODIFY_UI ) has been implemented to modify this screen in you system.
See these related notes:
Note 976533 - Changing the "Required on"/"Start Date" in shopping cart
Note 1064560 - Disabling Service Button causes change in Label/header.
Note 948473 - Change field labels on 'Describe Requirement' screen
BR,
Disha.

Date Range Validity periods for Addresses

Hello,
In the BP transaction when entering address details I cannot see a place to enter a validity period for the address even though in BUT020 there are database fields on this table to store a To and From date for and address.
Does anyone know how to make these date field available for entry?
Many thanks in advance.
David

Thanks.
When I go to this in SPRO I can see the field 'BP Address: Time-Dependent Usages' for the role I need to change.
However when I make this field 'optional' is still does not appear.
If I select optional on some other fields e.g. 'Address-Indep.Communication Data: Mobile Telephone' this field appears.
Is there anything else I need to do to make this field appear?
Regards
David

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

How to define validity period for tax codes

In Fv12 the validity period is in display mode , how to change the validity period ? Will affect the tax codes or the changes remain for condition records.

Hi
You can use t-code FTXP,
Check the menu option in the main transaction menu for tax rate periods
Regards
Sach!n

Credit Check while creation of Sales Order for Item Category Purchase Req

Hi Experts,
We are creating Sales Order using an Order Type ABCD for a material 1000. While creating Sales Order, we use Item categories (ZOVD, ZOVB,ZOST,ZOVP and ZOBO).
Credit Check settings are there at Order Type ABCD as well as all the Item Categories (ZOVD, ZOVB,ZOST,ZOVP and ZOBO). We are trying to test a scenario where a customer does not have enough credit limit while creating a sales order.
When we create a sales order for Item Categories (ZOVD, ZOVB,ZOST,ZOVP), credit check fails because our customer does not have enough credit limit, so that Sales Order gets created and Delivery does not get created (This is what we want), then we go into VKM1 manually and relase the sales order and then if we go to VA02 and check the status of the Sales Order, it says sales order status is complete. My Sales Team is saying here also Purchase Requisition is getting created.
When we create a sales order for Item category ZOBO, it is going into Purchase Requisition screen. Once we give another plant in the create purchase requisition screen and save it we are getting a message that cannot create Purchase Requisiton because of Credit Block.
The settings were same for all the Item categories.
1) What made difference to complete Purchase Requisition for Item Categories (ZOVD, ZOVB,ZOST,ZOVP) and not for Item Category ZOBO when my customer is not having enough credit Limit.
2) Why Purchase Requisition screen is not coming for us when we create an Sales Order for Item Categories (ZOVD, ZOVB,ZOST,ZOVP). We only get Create Purchase Requisiton Screen for Item Category ZOBO.
Thanks
Rajanikanth

Hi,
None of the Item Categories has Create PO Automatically.
Thanks
Rajanikanth

Validity Period for BP relationships

Hello Experts,
We are having a problem with the validity date in BP relationship. Our partner functions get replicated from ECC to CRM. However, if one of the partner function detail changes, the relationship come up with two values for the same partner function which is correct but both show the same validity to and from date.
For eg if we have the payer XYZ for the sold to ABC from validity period 2008 to 2009 and the payer changed to EFG from 2009 to 9999, the relationship tab shows both the payer valid from 01.01.01 to 01.01.9999.
The system then fails to determine the correct payer if an order comes through from MSA and stops with an error in CRM which then has to be processed manually.
How can this problem be resolved so that the validity period comes up with the correct dates and the system can automatically pick up the correct partners?
PT

Hi,
Please go to transaction BUBN and in that one field group would be there called 'Relationship Category/Role Definition Category'.
Select that and go to "Field Group--> Fields" and add the following two fields:
Table                        FieldName
BUS050DFLD           DATE_FROM_STR
BUS050DFLD           DATE_TO_STR
Dont check any of the check boxes like "input field" and "not a required field".
Save it and come out and then again launch BP trx to get the desired result.
This is how i solved my problem in CRM 4.0.
Please let me know if you have problems.
Regards
Sidd

Enrollment Screen - Validity period for benefit plan

Hi,
At the enrollment screen (HRBEN0001), once click the adjustment reason, the respective benefit types and plans will be listed out. Also, the benefit plans have the "Validity period" showing as well (start date and end date).
I understand that the date is configure at "administrative parameter" and the "adjustment reason" . But I needs to have the validity end date of the benefit plan to be displayed (at HRBEN0001) based on the validity period of the plan itself from table (T5UBA). Is it possible to do that?
Thanks
Nikki

Hi Nikki,
In configuration this cannot be done. However there is some badis that allow you to set up plan records date depending of the type of plan. These badis are:
PBEN0038                       Set dates for Spending Account plans
PBEN0039                       Set dates for Miscellaneous plans
PBEN0040                       Set dates for HSA plans
For other plan types I;m afraid only the dates from administrative parameter" and the "adjustment reason" can be used
Hope this help
Sarah

Athorization for item conditions

is there a possibility to make ristrictions to the item conditions?
when I run VA01 I can click on the button "item conditions". And there the user can now make chagnes like PB00 or ZSMX.
The question is now, how can I make the restriction on PB00 that not everyone can run this price conditions?
thx 4 your help
markus

Hi Markus,
It can not be so. Have you checked that you have removed the this object from all the roles assigned to that particular user?
Check for the roles containing this object in trasaction code SUIM and check the values in the role which contains this user ID.
( Don't forget to save the changes & generate the profile.)
Please confirm if solved.
Cheers.
Shamish

CURRENT_ITEM_NAME for item conditions

Say I have a page with well-defined item names like Px_ITEMy where y is a integer from 1 to say 25. I have a application item value as 25 1s and 0s that indicate whether that item is to be displayed on the page.
In a case like this, it would be very useful and provide for better maintenance if the Item Conditional display attribute were to recognize the context of the current item (like item labels do with the CURRENT_ITEM_NAME substitution) so that all the item conditions could use the same PL/SQL expression instead of hardcoding the "y" in each expression. Sort of like the "this" object in Javascript.
Or is there another way to achieve the same result using the Apex dictionary?
Thanks

Bump. Thanks

FM for item condition values in RFQ

Hi,
     I have a RFQ number. now the i want a function module which will return me the item condition values ( eg freight,gross price etc).
     i have gone through a FM named 'PRICING' but thats not helping me
      any help

Hi,
     I have a RFQ number. now the i want a function module which will return me the item condition values ( eg freight,gross price etc).
     i have gone through a FM named 'PRICING' but thats not helping me
      any help

Validity periods for Item Conditions - Purchasing Agreements

Similar Messages

Maybe you are looking for