How we can see when the condition records created.

Hi,
How we can see when the condition records created ( Valid from and Valid to ) ? And also how we can see the changes made in the Condition records?
Regards,
jyothi.

Hello,
you can display the condtion records in transaction VK13.
Here you have the posibillity to display the changes of the condtion records.
Please goto VK13
> Enter your selection criteria
> Enviroment
> changes
But you can also create a condtion list. and the you can display more than one condition record:
Please have a look at the transation V/LD - Pricing Report
For example: conditon list 14 for taxes.
Here you get an overview of tax condtions.
I hope that the information are helpful.
Regards
Claudia
If you are satisfied with the answer, please give Reward Points.

Similar Messages

How can see when the last time you downloaded an app was?

I Want to see when the last time a certain app was downloaded on my phone.

I got the last ~10 logins on the computer, but not the last time a specific user was logged in.

Photo attachments in gmail - Can I see when the photo was created?

Hi,
just a quick query; I received a photo in Gmail earlier and would like to know when the photo was created, if I download it from Gmail and chose 'get info' it states the device used to capture it etc(iphone5) but says it was created at the download point. My question is, is there anyway to find the original date using a third party program?
regards

I got the last ~10 logins on the computer, but not the last time a specific user was logged in.

Can the Condition records in the transaction NACE be transported?

Can we Transport the Condition records in the transaction NACE from one system to another ( I mean from Dev to Quality).
I have navigated through all the menu in the transaction NACE but haven't found any link for transport.
Any help pls.

Hi,
Please find the bellow thread which is related to NACE transaction.
<<link removed>>
Regards,
Goutam Kolluru.
Edited by: goutam kolluru on Feb 1, 2012 4:56 AM
Edited by: kishan P on Feb 1, 2012 11:48 AM

How to know if an output condition record is ever used in sales docs

All,
I can see some output condition records in table B001. Additional detail of these records is in table NACH. But is there a way to know whether these condition records are determined in any sales docs?
In individual sales documents, I can manually check what condition records are determined from the 'output determination analysis' screen. Here I can see the number of the condition record that the system has determined. But is there a table which links sales document and output condition record? (equivalent of KONV)
Thanks & Regards,
KC
PS: Table NAST stores transaction data but only the output type and sales doc number is shown but it doesn't show the condition record (though it can be checked manually).

Hi Krishna,
Depending on the version of SAP you are using there is a transaction i think it is VA70 in ECC6 or in 4.6 there is a standard program for mass printing from a sales order.
You can use this tcode/program the very same as VL71 for deliverys and enter in your output type and change the processing mode to 2 and execute from here you can see if it was ever printed
Regards
Paul

I am currently using an ipod touch 3. When i record in voice memos with the apple earphones(with an inbuilt mic) i can see on the screen that its recording; but when i hear it, its just a long beep. Need some help!

I am currently using an ipod touch 3. When i record in voice memos with the apple earphones(with an inbuilt mic) i can see on the screen that its recording;
but when i hear it, its just a long beep. Need some help!

Does the mic work for other apps like Voice Control?
Does the mic work OK in other devices?
Have you tried it with another mic?
Try:
- Reset the iOS device. Nothing will be lost
Reset iOS device: Hold down the On/Off button and the Home button at the same time for at
least ten seconds, until the Apple logo appears.
- Reset all settings
Go to Settings > General > Reset and tap Reset All Settings.
All your preferences and settings are reset. Information (such as contacts and calendars) and media (such as songs and videos) aren’t affected.
- Restore from backup. See:
iOS: How to back up
- Restore to factory settings/new iOS device.
- Make an appointment at the Genius Bar of an Apple store.
Apple Retail Store - Genius Bar

I want to hide certain pictures in the "Gallery"so only I can see when I want. How can I do this?

I want to hide certain pictures in the "Gallery"so only I can see when I want. How can I do this?

Sometimes depending on the SD card (you set the sd card to be where photos are sent) and then place a security code on the files and photos. I know this can be done on a computer not 100% sure about a cell phone.
Another option is to have the photos sent to Picassa (going to be Google+ shortly) or Photo bucket or other web spots for photos or even Drop Box etc. this way your photos are away from the phone, and only the ones on the phone you don't care about remain on the cell
So I hope it works out ok for you.

When I play a video in mirroring mode,I can see only the video in the tv thru apple tv ,not in my ipad 2 how can i fix it? to see in both parts.

when I play a video in mirroring mode,I can see only the video in the tv thru apple tv ,not in my ipad 2 how can i fix it? to see in both parts.

Have you tried resetting the iPad:
Reset iPad: Press and hold the On/Off Sleep/Wake button and the Home
button at the same time for at least ten seconds, until the Apple logo appears.

Where can I see the condition record change value -?

Hi friends
Please let me know this
Ex: if I change my condition record for $10 to $12 to day.
where can I see both the prices ?
In vk 13 if i go to environment ->changes , it is only showing new value not showing old value -?
Please help me with this.
thanks
Kris

Hi Kris,
Go to [VK13]. Enter the condition type and select the access sequence. Enter the necessary values in the selection fields and click on the condition info option in the application toolbar. Now ensure the selection values are still present and remove the validity date. Press F8 and you would get the history of the condition record.
Regards
Nadarajah Pratheb

The condition record for use B can not be displayed

Hi gururs,
What does this message (number : VE896 ) mean ?
How to make it desapear ?
P.S : it's about output type for purchase orders.
This message is displayed when I click on : "Goto -> Determi analysis" in tcode ME22N.
Regards,
Bahia.

Hi
It means you are trying to veiw the executed condition record. System found the condition record for entered transactional data which you cannot see by clicking on it (when you see green record in condition analysis).
For given condition type -> and access sequence/ access - system shows the condition record that is determined. You can see its details by clicking the access which shows the message that condition record has been found with its determined parameters.
Ex: For batch determination I have set up one search strategy with a condition type (with access sequence). I created one condition record. When creating say sales order -batch determination takes place based on condition record parameters. System shows a green light for determined condition record. You cannot see its details - if you try to see then system issues a message like ''The condition record for use B can not be displayed''. If you want to see click on its immediate predecessor (access ).
Thanks

How can I retrieve the condition in an update or delete using instead of trigger

I have 2 tables, on which a view is created. To distinguish the tables within the view trigger, a column "source" had been added in the view creation. I want to be able to delete row(s) in table t1 or table t2 through the view, depending on a condition. The problem is that I don't know how I can get back the delete condition IN the INSTEAD of trigger :
CREATE TABLE t1(m NUMBER, n VARCHAR2(10), o date);
CREATE TABLE t2(a NUMBER, b VARCHAR2(10), c date);
-- The view is created based on the 2 tables.
CREATE OR REPLACE VIEW vt12 AS
SELECT 't1' source, m, n, o
FROM t1
UNION
SELECT 't2' source, a, b, c
FROM t2;
-- The trigger will fire whenever INSERT is performed on the tables through the view
create or replace trigger tvt12 instead of insert or delete on vt12
begin
if inserting then
if :new.source = 't1' then
insert into t1 values (:new.m, :new.n, :new.o);
else
-- will insert a default value of -1 for the fourth column "d"
insert into t2(a,b,c,d) values (:new.m, :new.n, :new.o, -1);
end if;
elsif deleting then
-- We don't know the condition for the deletion, so all rows from the
-- table from which the current row is coming will be deleted
if :old.source = 't1' then
delete t1;
else
delete t2;
end if;
end if;
end;
show error
insert into vt12 values ('t1',1,'1',sysdate);
insert into vt12 values ('t2',2,'2',sysdate+1);
insert into vt12 values ('t1',3,'3',sysdate+2);
insert into vt12 values ('t2',4,'4',sysdate+3);
insert into vt12 values ('t1',5,'5',sysdate+4);
insert into vt12 values ('t2',6,'6',sysdate+5);
commit;
select * from vt12;
select * from t1;
select * from t2;
delete vt12 where m = 1;
commit;
select * from vt12;
select * from t1;
select * from t2;
When I execute this script, the delete statement seems to recognize that the condition is affecting a row in table t1, and therefore deletes all rows from the table, as specified in the delete statement of the trigger... But, what I want to do is ONLY to delete the row affected by the original condition. So my question is to know how I can get back the original condition for the delete, and still use it in the trigger, that will be executed INSTEAD of the delete statement.. I checked in the doc, and everywhere an example of INSTEAD OF trigger can be found, but it's always and only using an INSTEAD OF INSERT trigger, which doesn't need a condition.
Can anyone help ?
null

I've never faced this case myself, but from the documentation it would seem that the INSTEAD OF DELETE is also a FOR EACH ROW trigger. Therefore, you don't really have to worry about the actual "where" clause of the original "delete" operation: Oracle has it all parsed for you, so you just need to redirect, in turn, each view record being deleted to the appropriate table.
In extenso: for your
delete vt12 where m = 1;
=> the INSTEAD OF trigger fires once for all records in vt12 where m=1, and I would guess that you trigger code should look like:
begin
delete from t1 where m = :old.m and n = :old.n and o = :old.o;
delete from t2 where a = :old.m and b = :old.n and c = :old.o;
end;
It's a bit of overkill compared to the "where" clause of the original "delete" statement, but it should do the job...
BTW, if by any luck you do have some primary key on tables t1 and t2 (say: columns o and c respectively), then obviously you can make the thing simpler:
begin
delete from t1 where o = :old.o;
delete from t2 where c = :old.o;
end;
HTH - Didier

How we can see the data in import id 'LZUT5U11'

HI
Plz observe below code carefully
import lsind
         report_title
         table_name
         report_field
         change_display
         show_hide
         conversion_exits
         table_description
         form_program
         select_form
         update_form
         line_size
         line_count
         records[]
         fields[]
         header_fields[]
         select_fields[]
         xrep[]
         from memory id 'LZUT5U11'.
sy-lsind = lsind.
when i was trying to import the data to above mentioned fields
from memory id 'LZUT5U11' getting dump due to length difference between memory id 'LZUT5U11' and field 'lsind'.
how we can see the field length in memory id 'LZUT5U11'.
Regards
santhosh
[email protected]

For Finance the standard datasources are
0FI_GL_4
0FI_AR_4
0FI_AP_4
Go to R/3 lbwe
select these datasources
click on manage
you will get a window with fields. here in the right hand corner there is a drop down which giives table names
OR
Goto RSA3 and give the datasource name

How we can see the abap memory data

How we can see the abap-memory data
fine the code below
import lsind
         report_title
         table_name
         report_field
         change_display
         show_hide
         conversion_exits
         table_description
         form_program
         select_form
         update_form
         line_size
         line_count
         records[]
         fields[]
         header_fields[]
         select_fields[]
         xrep[]
         from memory id 'LZUT5U11'.
Regards
santhosh
mail-id : [email protected]

Dear Santosh,
ABAP MEMORY:
A logical memory model illustrates how the main memory is distributed from the view of executable programs. A distinction is made here between external sessions and internal sessions .
An external session is usually linked to an R/3 window. You can create an external session by choosing System/Create session, or by entering /o in the command field. An external session is broken down further into internal sessions. Program data is only visible within an internal session. Each external session can include up to 20 internal sessions (stacks).
Every program you start runs in an internal session.
All "squares" with rounded "corners" displayed in the status diagram represent a set of data objects in the main memory.
The data in the main memory is only visible to the program concerned.
CALL TRANSACTION and SUBMIT AND RETURN open a new internal session that forms a new program context. The internal sessions in an external session form a memory stack. The new session is added to the top of the stack.
When a program has finished running, the top internal session in the stack is removed, and the calling program resumes processing.
The same occurs when the system processes a LEAVE PROGRAM statement.
LEAVE TO TRANSACTION removes all internal sessions from the stack and opens a new one containing the program context of the calling program.
The ABAP memory is initialized after the program is called. In other words, you cannot transfer any data to a program called with LEAVE TO TRANSACTION via the ABAP memory.
SUBMIT replaces the internal session of the program performing the call with the internal session of the program that has been called. The new internal session contains the program context of the called program with which it is performed.
When a function module is called, the following steps are executed:
A check is made to establish whether your program has called a function module of the same function group previously.
If this is not the case, the system loads the associated function group to the internal session of the calling program as an additional program group. This initializes its global data.
If your program used a function module of the same function group before the current call, the function module that you have called up at present can access the global data of the function group. The function group is not reloaded.
Within the internal session, all of the function modules that you call from the same group access the global data of that group.
If, in a new internal session, you call a function module from the same function group as in internal session 1, a new set of global data is initialized for the second internal session. This means that the data accessed by function modules called in session 2 may be different from that accessed by the function modules in session 1.
You can call function modules asynchronously as well as synchronously. To do so, you must extend the function module call using the addition STARTING NEW TASK ''. Here, '' is a symbolic name in the calling program that identifies the external session, in which the called program is executed.
Function modules that you call using the addition STARTING NEW TASK '' are executed independently of the calling program. The calling program is not interrupted.
To make function modules available for local asynchronous calls, you must identify them as executable remotely (processing type: Remote-enabled module).
There are various ways of transferring data between programs that are running in different program contexts (internal sessions). You can use:
(1) The interface of the called program (standard selection screen, or interface of a
subroutine, function module, or dialog module)
(2) ABAP memory
(3) SAP memory
(4) Database tables
(5) Local files on your presentation server.
For further information about transferring data between an ABAP program and your presentation server, refer to the documentation for the function modules WS_UPLOAD and WS_DOWNLOAD.
Function modules have an interface, which you can use to pass data between the calling program and the function module itself (there is also a comparable mechanism for ABAP subroutines). If a function module supports RFC, certain restrictions apply to its interface.
If you are calling an ABAP program that has a standard selection screen, you can pass values to the input fields. There are two options here:
By using a variant of the standard selection screen in the program call
By passing actual values for the input fields in the program call
If you want to call a report program without displaying its selection screen (default setting), but still want to pass values to its input fields, there is a variety of techniques that you can use.
The WITH addition allows you to assign values to the parameters and select-options fields on the standard selection screen.
If the selection screen is to be displayed when the program is called, use the addition: VIA SELECTION-SCREEN.
Use the pattern button in the ABAP Editor to insert a program call via SUBMIT. The structure shows you the names of data objects that you can complete with the standard selection screen.
For further information on working with variants and further syntax variants for the WITH addition, see the key word documentation in the ABAP Editor for SUBMIT.
You can use SAP memory and ABAP memory to pass data between different programs.
The SAP memory is a user-specific memory area for storing field values. It is available in all of the open sessions in a user's terminal session, and is reset when the terminal session ends. You can use its contents as default values for screen fields. All external sessions can access SAP memory. This means that it is only of limited use for passing data between internal sessions.
The ABAP memory is also user-specific, and is local to each external session. You can use it to pass any ABAP variables (fields, structures, internal tables, complex objects) between the internal sessions of a single external session.
Each external session has its own ABAP memory. When you end an external session (/i in the command field), the corresponding ABAP memory is released automatically.
To copy a set of ABAP variables and their current values (data cluster) to the ABAP memory, use the EXPORT TO MEMORY ID statement. The (up to 32 characters) is used to identify the different data clusters.
If you repeat an EXPORT TO MEMORY ID statement to an existing data cluster, the new data overwrites the old.
To copy data from ABAP memory to the corresponding fields of an ABAP program, use the IMPORT FROM MEMORY ID statement.
The fields, structures, internal tables, and complex objects in a data cluster in ABAP memory must be declared identically in both the program from which you exported the data and the program into which you import it.
To release a data cluster, use the FREE MEMORY ID statement.
You can import just parts of a data cluster with IMPORT, since the objects are named in the cluster.
In the SAP memory, you can define memory areas (SET/GET parameters, or parameter IDs), which you can then address by a name of up to 20 characters.
You can fill these memory areas either using the contents of input/output fields on screens, or using the ABAP statement:
SET PARAMETER ID '' FIELD .
The memory area with the name now has the value .
You can use the contents of a memory area to display a default value in an input field on a screen.
You can also read the memory areas from the SAP memory using the ABAP statement GET PARAMETER ID FIELD . The field then contains the value from parameter .
The link between an input/output field and a memory area in SAP memory is inherited from the data element on which the field is based. You can enable the set parameter or get parameter attributes in the input/output field attributes.
Once you have set the Set parameter attribute for an input/output field, you can fill it with default values from SAP memory. This is particularly useful for transactions that you call from another program without displaying the initial screen. For this purpose, you must activate the Set parameter functionality for the input fields of the first screen of the transaction.
You can:
(1) Copy the data that is to be used for the first screen of the transaction to be called to the parameter ID in the SAP memory. To do so, use the statement SET PARAMETER immediately before calling the transaction.
(2) Start the transaction using CALL TRANSACTION or LEAVE TO
TRANSACTION . If you do not want to display the initial screen, use the AND
SKIP FIRST SCREEN addition.
(3) The system program that starts the transaction fills the input fields that do not already have default values and for which the Get parameter attribute has been set with values from SAP memory.
The Technical information for the input fields in the transaction you want to call contains the names of the parameter IDs that you need to use.
Parameter IDs should be entered in table TPARA. This happens automatically if you create them via the Object navigator.
Programs that you call using the statements SUBMIT , LEAVE TO TRANSACTION , SUBMIT AND RETURN, or CALL TRANSACTION run in their own SAP LUW, and update requests receive their own update key.
When you use SUBMIT and LEAVE TO TRANSACTION , the SAP LUW of the calling program ends. If no COMMIT WORK statement occurred before the program call, the update requests in the log table remain incomplete and cannot be processed. They can no longer be executed. The same applies to inline changes that you make using PERFORM … ON COMMIT.
Data that you have written to the database using inline changes is committed the next time a new screen is displayed.
If you use SUBMIT AND RETURN or CALL TRANSACTION to insert a program and then return to the calling program, the SAP LUW of the calling program is resumed when the called program ends. The LUW processing of calling and called programs is independent.
In other words, inline changes are committed the next time a new screen is displayed. Update requests and calls using PERFORM ... ON COMMIT require an independent COMMIT WORK statement in the SAP LUW in which they are running.
Function modules run in the same SAP LUW as the program that calls them.
If you call transactions with nested calls, each transaction needs its own COMMIT WORK, since each transaction maps its own SAP LUW.
The same applies to calling executable programs, which are called using SUBMIT AND RETURN.
The statement CALL TRANSACTION allows you to
Shorten the user dialog when calling using CALL TRANSACTION USING .
Determine the type of update (asynchronous, local, or synchronous) for the transaction called. For this purpose, use the addition CALL TRANSACTION USING UPDATE 'update_mode', where update_mode can have the values a (asynchronous), L (local), or S (synchronous).
Combining the two options enables you to call several transactions in sequence (logical chain), to reduce their screen sequence, and to postpone processing of the SAP LUW 2 until processing of the SAP LUW 1 has been completed.
When you call a function module asynchronously using the CALL FUNCTION STARTING NEW TASK ' ' statement, it runs in its own SAP LUW.
Programs that are executed with a SUBMIT AND RETURN or CALL
TRANSACTION statement starts their own LUW processing. You can use these to perform nested (complex) LUW processing.
You can use function modules as modularization units within an SAP LUW.
Function modules that are called asynchronously are suitable for programs that allow parallel processing of some of their components.
All techniques are suitable for including programs with purely display functions.
Note that a function module called with CALL FUNCTION STARTING NEW TASK is executed as a new logon. It, therefore, sees a separate SAP memory area. You can use the interface of the function module for data transfers.
Example: In your program, you want to call a display transaction that is displayed in a separate window (amodal). To do so, you encapsulate the transaction call in a function module, which you set as to Remote-enabled module. You use the function module interface to accept values that you write to the SAP memory. You then call up the transaction in the function module using CALL TRANSACTION AND SKIP FIRST SCREEN. You call the function module itself asynchronously.
Type ‘E' locks for nested program calls may be requested more than once from the same object. This behavior can be described as follows:
Lock entries from function modules called synchronously increment the cumulative counter, And are therefore successful.
Lock entries from programs called with CALL TRANSACTION or SUBMIT
AND
RETURN is refused. The object to be locked by the called program is displayed as already Locked by another user.
Programs that you call using SUBMIT or LEAVE TO TRANSACTION cannot come into conflict with lock entries from the calling program, since the old program ends when the call is made. When a program ends, the system deletes all of the lock entries that it had set.
Lock requests belonging to the same user from different R/3 windows or logons are treated as lock requests from other users.
Regards,
Rajesh.
Please reward points if found helpful.

How to Delete the condition record in CRM

HI,
Can you please help me how to delete the condition record from condition table in CRM.
Please explain the usage of FM CRMXIF_CONDITION_SEL_DELETE with examples.
I have also read the documention of the function module. How to use this FM for custom defined condition table.
(this is the code given in Documentation)
DATA-OBJECT_REPRESENTATION         = 'E'
DATA-SEL_OPT-CT_APPLICATION              = 'CRM'
DATA-SEL_OPT-OBJECT_TASK                    = 'D'
DATA-SEL_OPT-RANGE-FIELDNAME        = 'PRODUCT_ID'
DATA-SEL_OPT-RANGE-R_SIGN                  = 'I'    (Including)
DATA-SEL_OPT-RANGE-R_OPTION           = 'EQ'
DATA-SEL_OPT-RANGE-R_VALUE_LOW = 'PROD_1'
Thanks
Shankar

Hi Shankar,
I am using the same CRMXIF_CONDITION_SEL_DELETE function module to delete condition record present in CRM.
But it is giving me below error in the return table of the FM after i run the program. Can you please correct me if I am doing any thing wrong?
Error in lt_return: SMW3     CND_MAST_SEL_DEL_EXT_VALIDATE     CND_M_SD
code:
ls_range-fieldname = 'PRODUCT_ID''.
ls_range-R_SIGN = 'I'.
ls_range-R_OPTION = 'EQ'.
ls_range-R_VALUE_LOW = '123456'.
APPEND ls_range TO lt_range.
MOVE lt_range TO ls_entry-SEL_OPT-range.
ls_data-SEL_OPT-object_task = 'D'.
ls_data-SEL_OPT-ct_application = 'CRM'.
ls_data-object_representation = 'E'.
CALL FUNCTION 'CRMXIF_CONDITION_SEL_DELETE'
EXPORTING
    DATA          = ls_date
IMPORTING
   RETURN        = lt_return
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
IMPORTING
    return = lt_ret.
Edited by: Saravanaprasad Nadar on Jul 7, 2010 1:27 AM

How I can see the data of my message after processing?

Hi guys,
My scenario is XI -> R/3 (asynchronous) using ABAP Proxy.
When a try to send a message the flag code is ok and the message enters in R/3 inbound queue, so it means that everything ok!
I want to know how I can see my data in queue or better how it enters in proxy and how I can see? In proxy method I put a break point... but can't stop there!!!
What I need to do to make a little test and verify that really works?
Anybody could help?
Thanks in advance,
Ricardo.

Hi Ricardo
If you want to do Debug Asyn Inbound proxy. Do the following steps.
1. Get the Queue-Id from MONI.
2. Deregister the Queue for your message (SMQR).
3. Now resend the message. The message will be stopped in the Deregistered Queue.
4. Start Transaction SMQ2 and select your specific Queue. Double clicking will take you to the detailed level.
5. Press F8 to start the Debugger. And now you can debug the whole Proxy mehtod for Inboud proxy method.
Check the file 'How to Debug XI Applications' for more information.
https://websmp204.sap-ag.de/~form/sapnet?_SHORTKEY=01200252310000071155&_SCENARIO=01100035870000000202
Regards
Paresh

How we can see when the condition records created.

Similar Messages

Maybe you are looking for