Condition valid date in inforecord

Hi experts
I am getting error in creating info record. The net price valid date shall be normally proposed by system as 31.12.9999.. But in my ides system, the date field is grey and blank, hence system prompting error.
Please guide me how to get the date proposed by the system
warm regards
marias

Hi
U need to enter the net value while creating the info record then the system will automatically takes the date evnthough field is gray. U can change the validity after giving net price from by clicking conditions in the menu.
Ravi

Similar Messages

Mass extention of service entry sheet condition record validity date

Hi all,
I have immediate requirement. i need to extend the validity date for condition record related to the Service entry sheet. This has to done mass sheet changes.
I am looking for Any bapi or Standard function module or any config changes.
I am looking forward for your valuable inputs.
Regards,
Sreenivasa Sarma K

Arun,
This doesn't suprise me...
I'm not sure if there is a standard solution, but you could do this via user-exit/BADI (see [here|http://www.sapfans.com/forums/viewtopic.php?p=648307] under maintenance plans )
PeteA
[www.pjas.com]

Trans ME31K:Defaulting item condition validity to contract validity date

Hello Experts,
I have a request from my client which is as follows :
On transaction ME31K (Create Contract), at header I can enter a start date and an end date for the validity of my contract.
Program name : SAPMM06E
FIELD-NAMES : EKKO-KDATB & EKKO-KDATE
The users want the same date range to appear at item level for the conditions :
Select a new created Item > Conditions.
Program name :SAPMV13A
FIELD NAMES : RV13A-DATAB & RV13A-DATBI
Because, the transaction is changing the program name, it is very difficult for us to replicate the dates at the item's condition level.
Can you please suggest any idea to implement this solution ?
Thanks & Regards,
Mahesh
Edited by: Maheshsingh Sharma Jhoomuck on Oct 5, 2009 4:52 PM
Edited by: Maheshsingh Sharma Jhoomuck on Oct 5, 2009 4:53 PM

Hi raghavendra sai !
Thanks for the answer.
But actually, my client wants 'from date' of the items conditions to be defaulted to the date that he indicated on the contract's validity date at header (from date - EKKO-KDATB).
A contract can be created with a validity interval that starts from a past date.

Rebate conditions with mulitple validity dates

Hello,
I have an urgent requirement. My customer wants to define different rebate rate by date in one agreement like normal pricing condition types.
for an example,
The validity date of the agreement is
1/1/2008 ~ 3/31/2008
Rebate conditons are as follows,
Material A $2 per 1unit, 1/1/08 ~2/28/08
Material A $3 per 1unit, 3/1/08 ~ 3/31/08
I would appreciate with your help. I will give you high point!

Hi,
Thanks for your answer.
When I tried to create a new condition record with different validity date, the system gave me a message "VK 104, the condition is being processed in current session". and then removed the record from the screen. It's because of the same condition key exists.
I think it's related to the difference on condition tables. When I checked a condition table for PR00, the attribute was "with validity period" but a rebate condition table had none in attribute.
Do you have any idea?

Mass change Condition valid to dates into Info record

Hi,
is there any mass changes for condition validity to dates into purchase info record?????
i have check into MEMASSIN, there is field for conditions valid to Date,
Pl. guide .
Regards,
Devendra

Hi,
It is not possible to change validity date using MEMASSIN - Mass Maintenance t code.
You need to create LSMW with recording method to achieve this. we are doing the same.
It is very easy. And take care that while recording select the validity button and click executive to record the do not double click on the validity tab.
Reg

Create Table/View with Validity Date Control?

Hi,
does anyone know the easiest way for me to create a custom view that uses validity dates to control records by time periods, similar to time constraint 1 infotypes in HR?
For instance, if I define a table to store entries like so
Client (Key): 100
PSubArea (Key): C001
Grouping (Key): 01
End Date (Key): 99991231
Begin Date: 18000101
and I want to ensure that there can only be one record active on any given date, how can I prevent someone from creating a record from 20061107 - 20071107 that overlaps the existing record?
Is there a setting I missed?
Add conditions to generated view coding? Is there a good example?
Thanks

K, so I found these
<a href="http://help.sap.com/saphelp_nw04s/helpdata/en/91/ca9fb3a9d111d1a5690000e82deaaa/content.htm">SAP Help - Time-Dependent Table/View</a>
<a href="http://help.sap.com/saphelp_nw04s/helpdata/en/c1/df5c3c3b067331e10000000a114084/content.htm">Generate Time-Dependence</a>
I'll give it a whirl now.

Info Record Validity Dates - Future Period

Hi Gurus
can you help
we have current Purchase Info Recs in place, with pricing condition records that have a validity date that will expire in the next few days
we have already loaded the next pricing for the next cotnract period with the vendor, but wish to check the accuracy of the data before that pricing condition becomes "current"
do you know how can we pull the data from the future validity period pricing condition record, so we can validiate this
i have only found ways to get the current pricing conditions, but not the one for the future period
please advise
many thanks

hi Velu
we maintain Pricing Condition Type PB00 in ME13
when i key a Pur Ord for the part, then go to Conditions tab in ME21n, then select the Analysis of the Pricing Condition, it bring up Procedure RM0000
then Gross Price PB00, then various steps under this
a number of steps not executed due to requirements not filled etc, being Contracts, outline agreements, Plant Infor Rec Order Unit, then Material Info Rec (Plant Specific) A017, then Material Info Rec table A018 with various field names
For Access Sequence step Mat Info Rec (Plant Specific) it does say No condition record was found for this condition using the document data.
any thoughts
If we cannot resolve i shall leave it for now, and review on the day it becomes current
many thanks

Question regarding usage of CRM pricing conditions using date ranges

Hi,
I wonder if someone has a suggestion regarding how to set up pricing conditions in CRM to accomplish the following scenario:
For existing customers we want to “freeze” the product price for certain customers,
but at the same time let other customers get another prize for the same product
and period.
(We have scenarios where the product price changes retroactively, years back in time, but only for those custoemrs that fulfill a specific criteria at the time where the prize change was decided to take place..)
We want the prize to be dependent on the customer status AND when this status was set
(before a specific date), but there doesn’t seem to be a way to set up pricing
conditions with date ranges (i e "customer status changed before YYYYMMDD
renders prize X").
Since we are talking about quite a lot of customers we do not want to add each and every
one of them as “individual price items” in the pricing conditions tables.
Does anyone have an idea regarding how to set this up?
Thanks
/Marika Wasserman

Hi Marika,
condition records have validity (FROM - TO). Let us assume you have a condition record for product A with 50 EUR per piece and this record is valid from 01.01.2014 until 31.12.2014.
If you create CRM Sales Order having product A at 4.12.2014 and this date is used as pricing date for the conditon determination, then it will find this condition record with price 50 EUR per piece. This 50 EUR should be the froen price.
Now how can you achieve that for the same CRM Sales Order another product price is determined for certain customer or a certain customer group?
The idea is to pass an additional pricing attribute, e.g. customer group. Then you can create a new condition table with this field with the key fields product and customer group. In the access seqeunce first the new condition table is checked and if no record is found, then the second conditon table is checked as shown below:
Access Sequence ABC
Access 10: condition table with key fields product + customer group
Access 20: condition table only key field product
Instead of customer group you define also any other field. You create your own implementation of the BAdI CRM_COND_COM_BADI that passes this field with a value to pricing.
Best regards,
Baris Yalcin

Sales Deal with two different validation dates for the same material

Hi SAPers,
I am trying to create a u201CSales Dealu201D VB31, for the same material/condition, but with two different validation dates. After the creation of the first record, I select u201CNew conditionu201D button, but the system give me the message VK104, u201Cthe condition is being processed in the current session.u201D.
How can I solve this issue?
Thanks in advance.
Pedro

We can't have multiple records for the same condition and key values valid on the same date. The condition end date is part of the primary key in the database table. The date ranges between the records cannot overlap. When you create a new record, usually the end date is set to 12/31/9999 by default. If you need to have this deal to end on a different date and a new deal to start afterwards, then first you need to change 12/31/9999 to a different date.
Also usually I try to exit the screen between the transactions.

GATP - Issue with substitution rules with validity dates

Hi,
We are using GATP with RBA. Our condition table has plant as a field.
We are planning to have a substitution procedure (rules) defined at plant level.
Our rule control for product substitution list is "Start from top of list"
The issue we are facing is explained below.
The first item in the substitution procedure (rule) cannot have validity dates.
So it will always be balnk. And validity dates can be maintained for other items in the procedure (rule).
What happens in our scenario is when there is a requirement on an item in the substitution procedure (rule) which has a validity date, the first item in the procedure (which can never have validity dates) is never considerd for substituions.
If I remove the validity dates, then the first item in the procedure (rule) is considered for substitutions.
We find this strange and against our business requirement. We want the first item in the procedure (rule) to be considered for substitution ireespective of the validity date for the requested product.
It would be great if you could suggest a method to achieve this.
Thanks & regards,
Arvind.S

Hi Mohan,
Thanks for the response.
We are using back order processing (BOP) for allocation.
We observed that the first item was not getting considered for substitution in the BOP results and also in product view after the BOP run. No stock of that item was allocated for the order taken up in the BOP run.
However, we tried rule evaluation also. It shows the first item also, but in actual allocation the issue exists.
We are not using "start immediately" in check instructions.
Thanks & regards,
Ashok

Validation "is a valid date" does not pass but Apex proceeding anyway

Hi,
I have a simple date-item which I validate first against "not null", then for "is a valid date", then that the date is not in the future.
In debug mode the first validation passes, the second ( is a valid date ) does not pass, but the validation process proceeds anyway...!? Then the third validation "date not in the future" produces ad DB-Error because it is not a valid date.
Why does the validation proceed even if the validation does not pass...?
Version 2.2.0
Juergen

Juergen,
"In debug mode the first validation passes, the second ( is a valid date ) does not pass, but the validation process proceeds anyway...!?"
Do you mean that the third validation is firing even though the second is failing? This behaviour is correct. All validations fire (regardless of any having already failed) unless they have specific conditions set on them to make them act differently.
If you don't want the third validation to fire if the second has failed then you will need to put a condition on the 3rd validation to prevent this. Alternatively you could bundle all you validations into one of type "PL/SQL returning Error Text" then have some IF...THEN...ELSE logic in your PL/SQL to return the relevant validatoin text depending on what the problem is (i.e. Date is null, date is invalid or date is in the future).
Andy

Join condition validation error in owb 10gR2

Hi friends,
When I tried to validate the join condition in the mapping im getting the below error like
an error occurred during expression validation, bad expression return type
When I googled for the above error, I got the below link mentioning like a bug for that join condition validation problem
https://forums.oracle.com/thread/717194
In which it is mentioned like a BugNo: 7417869 for that issue.
Is there any fix for that bug??
Thanks in advance.
Brgds,
Mini

Dear Allan,
Happy to get reply from you and sorry for my late reply as im been stuck with other work
Like you said, I downloaded the required patch 4898608 for the validation bug in mapping with owb 10.2.0.4. By viewing the readme.txt file of the patch I followed the below steps like
Set the ORACLE_HOME environment variable to point to the OWB Home
Add $ORACLE_HOME/OPatch in the PATH
Stopped the runtime service using the supplied SQL*PLUS script stop_service.sql as a rep_owner
      OWB_HOME/rtp/sql/stop_service.sql
After the above three steps I applied the opatch like below in cmd prompt
C:\orahome\10gR3_1\OPatch>opatch version
Invoking OPatch 10.2.0.4.9
OPatch Version: 10.2.0.4.9
OPatch succeeded.
C:\OraHome_1\OPatch>opatch apply
Invoking OPatch 10.2.0.4.9
Oracle Interim Patch Installer version 10.2.0.4.9
Copyright (c) 2009, Oracle Corporation. All rights reserved.
Oracle Home       : C:\OraHome_1
Central Inventory : C:\Program Files (x86)\Oracle\Inventory
   from           : n/a
OPatch version    : 10.2.0.4.9
OUI version       : 10.2.0.1.0
OUI location      : C:\OraHome_1\oui
Log file location : C:\OraHome_1\cfgtoollogs\opatch\opatch2013-06-24_18-14-27PM.
log
Patch history file: C:\OraHome_1\cfgtoollogs\opatch\opatch_history.txt
Failed to load the patch object. Possible causes are:
The specified path is not an interim Patch shiphome
Meta-data files are missing from the patch area
Patch location = C:\OraHome_1\OPatch
Details = PatchObject constructor: Input file "C:\OraHome_1\OPatch\etc\config\
actions" or "C:\OraHome_1\OPatch\etc\config\inventory" does not exist.
ApplySession failed: PatchObject constructor: Input file "C:\OraHome_1\OPatch\et
c\config\actions" or "C:\OraHome_1\OPatch\etc\config\inventory" does not exist.
System intact, OPatch will not attempt to restore the system
OPatch failed with error code = 73
C:\OraHome_1\OPatch>
Im not sure why the above error is occuring, kindly help me with that error.
Thanks in advance.
Brgds,
Mini

Fm for Validity Dates.

Hi Gurus,
I need Discount Condition Start Validity Date and Discount Condition End Validity Date along with condition details.
I have tried RV_INVOICE_DOCUMENT_READ &
FM RV_PRICE_PRINT_HEAD is returning all the pricing conditions in the invoice in TKOMV, but I couldn't find the Validity Dates in TKOMV.
please help me to sort out my problem.
I have closed my previous [Thread|http://forums.sdn.sap.com/thread.jspa?threadID=2139454]
Thanks & regards.

Hi,
try use COND_VALIDITY_FOR_SINGLE_DATE, may help u
Thanks & regards.

CIN - J1ID TAX RATE MAINTAINED VALIDITY DATE (INDIAN SCENARIO)

IN INDIA TAX RATES CHANGE DURING EVERY YEARS BUDGET. EXCISE AND CUSTOMS DUTY CHANGE FROM MARCH WHEREAS SALES TAX CHANGES FROM APRIL. THIS TIME DUE TO RECESSION AND ELECTION THE EXCISE DUTY STRUCTURE WAS CHANGED THRICE FROM DEC 2008 TILL DATE. FROM 14 TO 10 AND NOW 8%. IN CIN DATA (J1ID) THE TAX RATES ARE ALSO TO BE MAINTAINED. NOW THE TAX RATE IS STORING DIFFERENT VALIDITY DATES. THIS AFFECTS THE POSTING OF MIRO AND MIGO. WHILE POSTING THE DOCUMENT IT CONSIDERS THE POSTING DATE AND APPLIES THE TAX RATE AS PER THAT DATE. YOU HAVE PENDING DOCUMENTS WHERE THE TAX RATE IS DIFFERENT THAN THE CURRENT DATE. IS THERE A SOLUTION SO THAT TAX RATES ARE CORRECTLY PICKED.
BEST REGARDS
PANKAJ

HI,
The condition type has nothing to do with the consignment settlement.The factor which influence for
consignment settlement thro MRKO is the price u have given in PIR,PB00 & the tax code which u have
entered in the PIR tax code tab.It is no way connected to the vendor master.So if the tax code is
changing for different time period ask them to change manually.
regards
murugan

Multiple Validity Dates in Contract Pricing Agreements

Hi
We are using Quantity contracts in ECC 5.0. Now business wants to maintain multiple validity dates in price agreement of contract.
When we try to create the agreement with multiple validity dates, i am getting following message:
The condition is being processed in the current session.
Message no. VK104
Diagnosis
A condition record with the same variable key is already being processed.
System response
The new record is not included in processing.
Procedure
Carry out the changes to the record that is currently being processed.
In this case we are unable to maintain multiple validity dates for same combination (Sales Document & Line Item).
Is this standard scenario? If no, how to address this issue.
Please awaiting your valuable feedback.
Regards,
Shankar

Question answered by SAP.
1. Use VK11/12 to maintain the multiple validity dates.
2. If 2 Logical systems are used, then need to use separate condition types for CRM & ECC.
3. Ensure new condition types are blocked from replicating to CRM.
Now, we are able to maintain separate condition for ECC & CRM and working satisfactorily.
Thanks
Shankar

Condition valid date in inforecord

Similar Messages

Maybe you are looking for