Regarding RSRV transaction
hia
can anyone tell , when we have to use RSRV transaction and what are the precautions we have to take to use this transaction . please tell me ...
Any weblog or documentation . please tell me ....
Thanks
bye
hi
it's for bw objects consistency analysis and repair.
from transaction code RSRV doc itself :
Transaction RSRV: BW Data and Metadata Test and Repair Environment.
Transaction RSRV checks the consistency of data stored in BW. It mostly examines the foreign key relationships between individual tables in the enhanced star schema of the BW system.
The transaction interface was re-designed for SAP Portals release 3.0A. A brief guide about how to use the transaction follows.
Starting the Transaction
You can reach the test and repair environment
By entering the transaction code RSRV
From InfoObject maintenance (Transaction RSD1)
By clicking on the "Analyze" button in the intial screen.
After selecting a characteristic in the maintenance screen via the "Processing -> Analyze InfoObject" menu option.
The Initial Screen
When using the test and repair environment for the first time, the message "Values were not found for all setting parameters" draws your attention to the fact that there aren't any saved settings for your user.
After confirming the dialog box, you reach the initial screen of the transaction. This is divided into two parts:
1. On the left-hand side, you can see a tree structure with the pool of available tests.
2. The right-hand side is empty at first. The tests you have selected will be put here. A selection of tests is called a Test Package here.
Combined and Elementary Tests
An Elementary Test is a test that cannot be divided into smaller tests and that can therefore only be executed as a whole.
In this regard, a Combined Test determines which elementary tests are to be executed after entering the parameters. You can remove individual elementary tests from the test package before carrying out the actual test run, in order to reduce run time, for example.
Combining a Test Package and Executing it.
Firstly select one or more tests with drag&drop or by double-clicking. Each selected test appears as a closed folder in the view of your test package. (An exception is elementary tests without parameters: These do not appear as a folder). You can also drag a whole folder of tests from the test pool across to the right-hand screen area; all tests that are located in the hierarchical structure under this folder are then added to the test package. You can also display a short description of the test, if required. Do this right-clicking on a test and choosing "Description" from the context menu.
Afterwards, you must supply the tests with parameters. Tests without parameters must not be given parameters. You are given notification of this when selecting them. You can enter parameters by double-clicking on a test (or a test package) or by expanding the folder of the test.
A dialog box appears in which you must enter the required parameters. Input help is often available. After entering the parameters, a folder with the name "Parameter" is added under the test. This contains the parameter values. The test name can change in some circumstances, enabling you to see at first sight for which parameter values the test is to be executed. It is possible to select the same test several times and give it different parameters, which may even be preferable in some situations. When you have supplied the combined test with parameters, the folder with the name "Elementary Tests" is added under this one. It contains the elementary tests, from which the combined test is built. You can delete individual elementary tests in the test pool using drag & drop.
After supplying all tests with parameters, you can start the test run by clicking on the "Execution" button. After execution, the test icons change from a gray rhombus to a red, yellow or green one, depending on whether the test had errors, warnings or was error-free.
Test Results
The test results are written to the application log. Depending on the settings, the system jumps automatically to this display, or you can reach it by clicking on the "Display" button. The results are saved in the database, and can therefore be compared later with additional test runs.
In the left-hand side of the window, you can see an overview of the most recent test runs. Double-clicking on a folder displays all messages under these nodes as a flat (non-hierarchical) list in the right-hand screen area. Long texts or detail data may be available for individual messages, which can be displayed with a mouse click.
Repairs
Some tests can repair inconsistencies and errors. Automatic correction is generally not possible: If entries are missing from the SID table for a characteristic, in which case the lost SIDs are still being used in a dimension table (and the corresponding dimension keys are still being used in the fact table) of an InfoCube, you can only remove the inconsistency by reloading the transaction data of the InfoCube. Also note that you must make repairs in the correct sequence. You must always read the documentation for the test and have a good idea about how the error occured, before making the repairs.
After executing the test run, go from the application log back to the initial screen to make these repairs. Click on the "Fix Errors" button to start an error run. Since the dataset could have changed between the test and the repair run, the required tests are executed again before the actual repair. The results can be found in the application log once again.
Test Packages
The test package is deleted if you do not save the test package in the display before leaving the test environment. Choose "Test Packages -> Save Test Package" in the option menu. You can do the following via options in the "Test Package" menu:
Load packages
Load for processing - the package is then locked against changes by others.
Delete and
Schedule execution at a later date or at regular intervals in background processing
Settings
In the "Settings" menu option, you can make settings (adjust the size of the screen areas, for example) and save them. The settings are automatically read when starting the test environment. Support packages are being delivered with additional settings options since the test environment is under development at the moment. A message notifies the user at the start if there aren't any values for the setting options.
Jobs Menu Option
You can access the job overview via the Jobs -> Job Overview menu. Use this when you want to check the status of a test package you have scheduled.
Application Log Menu Option
You can display old logs from previous test runs in the dialog box, as well as scheduled ones. The option of deleting test logs can also be found here.
New Selection Button
The currently selected test package is deleted when you press this button.
Filter Button
After a test run, click on this button to remove all elementary tests without errors or warnings from the test package.
Executing Test Packages in Process Chains
You can add a process chain to the ABAP Programm RSRV_JOB_RUNNER in the process chain maintenance transaction, RSPC. To do this, use drag & drop to select the process type "ABAP Program" under "General Services" in the process type view. When maintaining process variants you will be asked for the program name and a program variant. Enter RSRV_JOB_RUNNER for the program name. Choose a program variant name and click on "Change". In the next screen you are able to either change or display an already existing variant, or create a new variant. When creating a new variant you will be asked for the following: Package name (an imput help on this is available), the detail level for the log to which the RSRV log in the process chain log is to be integrated, and a message type severity at which process chain processing should be terminated.
The RSRV process log in the process chain is built as follows:
First is a summary specifying whether errors, warnings, or no errors occurred for each elementary test.
A log view of the RSRV test package at the specified detail level follows.
Example: If you choose the value '3' for the detail level, only messages up to and including detail level 3 will be included in the log processes for the process chain. Messages occuring at a lower layer of the test package test are not displayed in this log. Please note that, unlike the application log, the process log does not propagate errors from deep detail levels to low detail levels. For example, if a single detail level 4 error occurs the summary will show that the relevant test delivered an error. However, this error will not be listed in the second part of the log.
A complete log is always written independantly of the RSRV process log in the process chain. You can view this in the menu option "Application Log->Display Log->From Batch".
Please note that there is currently no transport object for test packages and that consequently these cannot be transported. Process chains that execute RSRV test packages must therefore be manually postprocessed after a transport to a different system: The relevant test packages must be created.
Similar Messages
-
Hi all,
I am facing a problem regarding CJ02 transaction.
The problem is when I am saving the classifications of the project it is not reflected back to the corresponding fields of respective table.
It would be very helpfull if anybody sahres his/her any idea regarding this.
Thanks in advance.Hi
Is it the field name or the field value which u have given? Did u add custom fields to this table?
Regards,
Vishwa. -
Hi friends,
I have a simple query regarding the transaction CS03. When I give the Material Number, Plant and BOM Usage as input, I would get the list of components for this material.
Inside the transaction, is a CHECKBOX field ASM - this Indicates that the component for this material has its own BOM or has further components).
Could anyone tell me in which SAP table this information is stored i.e. an indicator to tell us if the component/material has further BOM or not.
I checked MAST and STPO tables but could not figure out the right field.
Awaiting your valuable inputs.
Thank You.
Regards,
Gayathri.hi gayathri,
1.
the bom can exist for HALB or FERT .
u can dimnish the material not having a bom on this category .
i.e to say material type 'RAW' dosent hav a bom .
2.
like check out for table "MVKE" (Sales Data for Material) and in here check the fields
MVKE-MTPOS (Item category group from material master)MVKE-DWERK(Delivering Plant).
now giv the material and execute for initially dont giv a plant , and execute .
proceed with parent-matrial in bom and execute ,
u'll see the list of materials assigned in a particular sales area now check for MTPOS status this will have a category called LUMF ( this u will hav only for parent)
now say that the parent have 4 child materials (say)of which one has subassemblies so as u said it will hav a ASM check box ticked in CS03, now take this material and goto mvke and repeat the procedure and check the MTPOS status this will have item category like 'NORM'
remember for parent it was 'LUMF'
now for child(having subass;les) we got'NORM'
now check for same which dosent have a subassemblies from the child items it will be like 'ZATP' or 'XXXX' but not LUMF or NORM. to tell that it dosent hav further bom.
generalise the conclusion for all the materials(parent childorphans)if found okay apply this logic.
second alternative is ,
check the transaxction cs12.
give BOm material and observe that the first field(dglvl) ...
it indicates the level of that material in thta BOM.
exact indiaction is whether it has sub assemblies in that Material is the
field (BOMFL) If it has sub assemblies then it will be' X'.
see if u can make any hit in the tables using this relation above
regards,
vijay. -
Hi all,
Please let me know the T-code or Programs for RSRV repair, where i can Schedule the RSRV Tests - Elementary Tests in Background (that can be monitored in SM37 and the logs should be seen).
Say for example i want to run Elementary Test on Master Data - "Value Available in the Navigation Attributes"
So can i run it in background and see the logs once its completed and then can run the Repair for this in Background again?
Please let me know all ur suggestions.
I need another Help, Can RSRV Test and repair be run on a particular Master Data once the Master Load is completed and but still when the Transactions Loads are in Progress?
Thanks in Advance,
SowrabhHi Sowrabh,
From RSRV you can save the test as a package and this package can
be scheduled as a periodic job as per your requirement.
RSRV > All Elementary Tests > choose
> Menu >Edit >Test Package > Save.
After you save the test as package you can schedule it.
You should only run the tests when there are no loads (master or transaction)
running in the system. If this is not possible then you should at least only run
the tests when there is no master data or transaction data load running for
the master data objects or attributes of these objects that you want to run the
test for.
Best Regards,
Des. -
hello all
i want to know much about RSRV tcode.I know that its being used for repairing infobject,but how do v repair and in what circumstances v repair and use this tcode.
do anyone has a pdf or doc on it please let me know?
thanks for all
regards
baljihi
check ur mail id i sent some documents to u
it's for bw objects consistency analysis and repair.
from transaction code RSRV doc itself :
Transaction RSRV: BW Data and Metadata Test and Repair Environment.
Transaction RSRV checks the consistency of data stored in BW. It mostly examines the foreign key relationships between individual tables in the enhanced star schema of the BW system.
The transaction interface was re-designed for SAP Portals release 3.0A. A brief guide about how to use the transaction follows.
Starting the Transaction
You can reach the test and repair environment
By entering the transaction code RSRV
From InfoObject maintenance (Transaction RSD1)
By clicking on the "Analyze" button in the intial screen.
After selecting a characteristic in the maintenance screen via the "Processing -> Analyze InfoObject" menu option.
The Initial Screen
When using the test and repair environment for the first time, the message "Values were not found for all setting parameters" draws your attention to the fact that there aren't any saved settings for your user.
After confirming the dialog box, you reach the initial screen of the transaction. This is divided into two parts:
1. On the left-hand side, you can see a tree structure with the pool of available tests.
2. The right-hand side is empty at first. The tests you have selected will be put here. A selection of tests is called a Test Package here.
Combined and Elementary Tests
An Elementary Test is a test that cannot be divided into smaller tests and that can therefore only be executed as a whole.
In this regard, a Combined Test determines which elementary tests are to be executed after entering the parameters. You can remove individual elementary tests from the test package before carrying out the actual test run, in order to reduce run time, for example.
Combining a Test Package and Executing it.
Firstly select one or more tests with drag&drop or by double-clicking. Each selected test appears as a closed folder in the view of your test package. (An exception is elementary tests without parameters: These do not appear as a folder). You can also drag a whole folder of tests from the test pool across to the right-hand screen area; all tests that are located in the hierarchical structure under this folder are then added to the test package. You can also display a short description of the test, if required. Do this right-clicking on a test and choosing "Description" from the context menu.
Afterwards, you must supply the tests with parameters. Tests without parameters must not be given parameters. You are given notification of this when selecting them. You can enter parameters by double-clicking on a test (or a test package) or by expanding the folder of the test.
A dialog box appears in which you must enter the required parameters. Input help is often available. After entering the parameters, a folder with the name "Parameter" is added under the test. This contains the parameter values. The test name can change in some circumstances, enabling you to see at first sight for which parameter values the test is to be executed. It is possible to select the same test several times and give it different parameters, which may even be preferable in some situations. When you have supplied the combined test with parameters, the folder with the name "Elementary Tests" is added under this one. It contains the elementary tests, from which the combined test is built. You can delete individual elementary tests in the test pool using drag & drop.
After supplying all tests with parameters, you can start the test run by clicking on the "Execution" button. After execution, the test icons change from a gray rhombus to a red, yellow or green one, depending on whether the test had errors, warnings or was error-free.
Test Results
The test results are written to the application log. Depending on the settings, the system jumps automatically to this display, or you can reach it by clicking on the "Display" button. The results are saved in the database, and can therefore be compared later with additional test runs.
In the left-hand side of the window, you can see an overview of the most recent test runs. Double-clicking on a folder displays all messages under these nodes as a flat (non-hierarchical) list in the right-hand screen area. Long texts or detail data may be available for individual messages, which can be displayed with a mouse click.
Repairs
Some tests can repair inconsistencies and errors. Automatic correction is generally not possible: If entries are missing from the SID table for a characteristic, in which case the lost SIDs are still being used in a dimension table (and the corresponding dimension keys are still being used in the fact table) of an InfoCube, you can only remove the inconsistency by reloading the transaction data of the InfoCube. Also note that you must make repairs in the correct sequence. You must always read the documentation for the test and have a good idea about how the error occured, before making the repairs.
After executing the test run, go from the application log back to the initial screen to make these repairs. Click on the "Fix Errors" button to start an error run. Since the dataset could have changed between the test and the repair run, the required tests are executed again before the actual repair. The results can be found in the application log once again.
Test Packages
The test package is deleted if you do not save the test package in the display before leaving the test environment. Choose "Test Packages -> Save Test Package" in the option menu. You can do the following via options in the "Test Package" menu:
Load packages
Load for processing - the package is then locked against changes by others.
Delete and
Schedule execution at a later date or at regular intervals in background processing
Settings
In the "Settings" menu option, you can make settings (adjust the size of the screen areas, for example) and save them. The settings are automatically read when starting the test environment. Support packages are being delivered with additional settings options since the test environment is under development at the moment. A message notifies the user at the start if there aren't any values for the setting options.
Jobs Menu Option
You can access the job overview via the Jobs -> Job Overview menu. Use this when you want to check the status of a test package you have scheduled.
Application Log Menu Option
You can display old logs from previous test runs in the dialog box, as well as scheduled ones. The option of deleting test logs can also be found here.
New Selection Button
The currently selected test package is deleted when you press this button.
Filter Button
After a test run, click on this button to remove all elementary tests without errors or warnings from the test package.
Executing Test Packages in Process Chains
You can add a process chain to the ABAP Programm RSRV_JOB_RUNNER in the process chain maintenance transaction, RSPC. To do this, use drag & drop to select the process type "ABAP Program" under "General Services" in the process type view. When maintaining process variants you will be asked for the program name and a program variant. Enter RSRV_JOB_RUNNER for the program name. Choose a program variant name and click on "Change". In the next screen you are able to either change or display an already existing variant, or create a new variant. When creating a new variant you will be asked for the following: Package name (an imput help on this is available), the detail level for the log to which the RSRV log in the process chain log is to be integrated, and a message type severity at which process chain processing should be terminated.
The RSRV process log in the process chain is built as follows:
First is a summary specifying whether errors, warnings, or no errors occurred for each elementary test.
A log view of the RSRV test package at the specified detail level follows.
Example: If you choose the value '3' for the detail level, only messages up to and including detail level 3 will be included in the log processes for the process chain. Messages occuring at a lower layer of the test package test are not displayed in this log. Please note that, unlike the application log, the process log does not propagate errors from deep detail levels to low detail levels. For example, if a single detail level 4 error occurs the summary will show that the relevant test delivered an error. However, this error will not be listed in the second part of the log.
A complete log is always written independantly of the RSRV process log in the process chain. You can view this in the menu option "Application Log->Display Log->From Batch".
Please note that there is currently no transport object for test packages and that consequently these cannot be transported. Process chains that execute RSRV test packages must therefore be manually postprocessed after a transport to a different system: The relevant test packages must be created. -
Doubt Regarding MIGO Transaction
Hi,
Where exactly the source code of MIGO transaction fills these two fields : BED , SED (Note: Under the Tab Excise Invoice).
Thanks & Regards,
Lakshmi.ok
-
Doubt regarding SHDB transaction
Hi All,
I have a doubt regarding the Process Tab in the application tool bar of SHDB transaction. What is the use of the following check boxes?
1) Default Size
2) Cont.after commit
3) not a batch input session
4) END: Not a Batch Input session
5) Simulate Background modeHi,
Basically these are the properties for CALL TRANSACTION using. You need not worry about these unless you really need those.
1) Default Size: it will set the Default screen size for CALL TRANSACTION USING...
2) Cont.after commit : it will set indicator that CALL TRANSACTION USING... is not completed by COMMIT. after commit also the process will continue
3) not a batch input session: sets indicator that present session is not batch input
4) END: Not a Batch Input session
5) Simulate Background mode : session will be run in foreground. but similar to back grpund
you can see the documentation by placing the cursor on these and click f1. -
Hi All,
In transaction FK03 i am able to view full name of vendor but when i am going for transaction FBL1N for the same vwndor i am not able to see full name there, last few characters are missing there. Can you please tell me how can i increase the lenght of vendor name in FBL1N transaction?
Thanks.Hello,
The output of the name is 'just' possible until the 35th character.
The reason is the following:
In the creation of the master data, the 'address' data is stored in
two different areas, first in the master data table (LFA1) and in the
specially created 'address information' tables.
Out of the technical design of the 'header setup' for the line item
display transactions, 'only' the LFA1 master data table is accessed.
As the field only contains 35 characters in this table LFA1, only these
will be displayed.
The restriction within some functions about the 'display' length of
the address information is also mentioned in a warning message you
receive, if you store a value which is 'bigger' then 35 characters:
The use of the last 5 characters in field NAME1 is restricted (40 of 40)
Message no. AM228
Diagnosis
The address data in field NAME1 exceeds the 35th position (40 of 40
characters occupied).
System Response
In this form the data can be saved and used up to the complete length
of 40 characters.
In some scenarios, the system only uses the first 35 characters of name
fields.
REgards,
REnan -
Regarding XK02 transaction in SAP ECC 6.0 Version
Hi All,
I am working with an object which calls a transaction <b>XK02</b> to modify the name and contact details fields in Version <b>SAP ECC 6.0</b>.
The problem is that, when the transaction is run manually and saved or when an SHDB Recording is created, the data is getting updated.
But when the transaction is called from a program or when the SHDB Recording which is already created is run, the data is not getting updated in Version SAP ECC 6.0.
The data is getting updated properly when it is done in Version SAP 4.6b.
Central Address Management System is used here.
Can anybody please help me in this regard?
Thanks & Regards,
Vaitheeswaran.Hi Prabhu,
The call transaction statement is running smoothly. The SY-SUBRC is 0 for this.
The thing is, there is a Check Box at the end of the screen called 'Use Central Address Management' when the SHDB is created.
If this is checked, the contact details are stored in ADRC and LFA1 tables and only in LFA1 if not checked.
In the new version SAP ECC 6.0, the data should also get populated in the ADRC table.
There is a slight change in the logic in SAP ECC 6.0 version.
Thanks & Regards,
Vaitheeswaran. -
Regarding F110 Transaction - Check printing
Hi All,
I switch on debuggin for the form of check printing and set a break point in the print program. then when i am going thru the process using F110 tanasaction by providing the variant and other details exactly, then it is not stopping in the form or in the print program, directly it is creating the spool request.
kindly help me how to debug the check printing form and print program using F110 transaction
Regards,
PrasadHi Jilan,
After activating the debugger in the form and putting break-point in the print program restart the transaction F110.It will stop there.
If even then it is not getting stopped there then check in the Transaction NACE which form and Print program is configured with the output type of your application.
OR Go to SE37 transaction display the FM 'OPEN_FORM'.
put the break-point at the line
check co_perform-active <> true.
Restart the transaction F110.Check the value of 'FORM' in debugging mode that will be the form configured to your transaction.
Regards,
Mukesh KUmar
Message was edited by: mukesh kumar -
Need Information regarding JTA Transactions
Hi all,
I have written session beans with out transaction.But now i want to apply JTA Transactions to that session bean methods.Can you pls send some code,Examples and related links regarding this.
Regards,
KiranHi Kiran,
But it was discussed so many times, check:
Problems while providing Transaction for a method in EJB
Problems while giving a transaction attribute to a Method in EJB
EJB transaction concurrency issue
Best regards, Maksim Rashchynski. -
Regarding New transaction in BPM's
Hi Everyone,
1.Are there any Prerequisites for defining BPM's?
2. In the Block Step Type,we have option as New Transaction. Can anyone tell me the use of this. please site some examples.
3. In some step Types like Send, Transformation, Receiver Determination, We have an option with Check Box as Create New Transaction. Is it the same function as in Block step New Transaction when do we use this option.
4. How to check the errors in BPM.
5. What are the different Error codes in BPMs.
I have found some information in SAP Help as well, please provide with some suitable Examples so that It would be much easy to Understand .
Thanks & Regards,
VarunHi
Create New Transaction
Create New Transaction in Block step, is used mainly for Error monitoring. If any error then can restart block. use below thread.
New transactions in BPM
To monitor BPM process use this guide
https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/troubleshooting%252bintegration%252bprocess
Various Error TCode
SXMB_MONI_BPE -> To monitor Integration Process.
SWWL->To Know open BPM Instances -
Regarding VX22 Transaction [Change License Data]
Hi All,
I have a issue related to <b>VX22 Transaction [Change License Data]</b>.
Do anybody knows the wether any <b>BAPI</b> available for <b>Change License Data[VX22]</b>.
I actually have to perform a BDC for change license data some times for <b>Multiple items for single Sales Document number</b> at a time.
I have Done the recording[SHDB] and added the following code to main program.
Can anybody tell me wether this code will perfectly work for <b>Multiple Items of Single Sales Document Number</b> in <b>VX22 Transaction</b>.
<b> PERFORM f_bdc_dynpro USING 'SAPMV52G' '0100'.
PERFORM f_bdc_field USING 'BDC_CURSOR'
'VBAK-VBELN'.
PERFORM f_bdc_field USING 'BDC_OKCODE'
'/00'.
PERFORM f_bdc_field USING 'VBAK-VBELN'
i_data-vbeln.
PERFORM f_bdc_field USING 'RV52G-SELKZ'
c_x.
LOOP AT i_pdata.
PERFORM f_bdc_dynpro USING 'SAPLV52E' '0500'.
PERFORM f_bdc_field USING 'BDC_CURSOR'
'RV52G-SELKZ(08)'.
PERFORM f_bdc_field USING 'BDC_OKCODE'
'=DETA'.
PERFORM f_bdc_field USING 'RV52G-SELKZ(08)'
c_x.
PERFORM f_bdc_dynpro USING 'SAPLV52E' '0520'.
PERFORM f_bdc_field USING 'BDC_CURSOR'
'VBEX-MODCO'.
PERFORM f_bdc_field USING 'BDC_OKCODE'
'/00'.
PERFORM f_bdc_field USING 'VBEX-ALNUM'
i_pdata-zzalnum.
PERFORM f_bdc_field USING 'VBEX-EMBGR'
i_pdata-zzembgr.
PERFORM f_bdc_field USING 'VBEX-GENNR'
i_pdata-zzgennr.
PERFORM f_bdc_field USING 'VBEX-MODCO'
i_data-modco.
PERFORM f_bdc_dynpro USING 'SAPLV52E' '0520'.
PERFORM f_bdc_field USING 'BDC_CURSOR'
'VBEX-ALNUM'.
PERFORM f_bdc_field USING 'BDC_OKCODE'
'=BACK'.
PERFORM f_bdc_field USING 'VBEX-ALNUM'
i_pdata-zzalnum.
PERFORM f_bdc_field USING 'VBEX-EMBGR'
i_pdata-zzembgr.
PERFORM f_bdc_field USING 'VBEX-GENNR'
i_pdata-zzgennr.
PERFORM f_bdc_field USING 'VBEX-MODCO'
i_data-modco.
ENDLOOP.
PERFORM f_bdc_dynpro USING 'SAPLV52E' '0500'.
PERFORM f_bdc_field USING 'BDC_CURSOR'
'*VBEX-VBELN'.
PERFORM f_bdc_field USING 'BDC_OKCODE'
'=SICH'.
PERFORM f_bdc_transaction USING 'VX22'.</b>
I have make use of Session Method for it.
I had run through it against VX22 in all 3 modes and it is working fine for single line item for a sale order.
If any changes required for it to work for Multiple line items please suggest.
If any body knows <b>BAPI</b> for the same process please post.
Thanks in advance.
Thanks & Regards,
Rayeez.Hi All,
Anybody worked on above kind of scenario,
If yes please sujjest!
Has Anybody worked with <b>VX22</b> Transaction
If worked please reply to above post!
Thanks & Regards,
Rayeez. -
Dear PS consultants,
While processing the transaction IM52 i am getting an error message as NO MEASURES FOUND. Can any one help me out, where i had done misatake.
I created project and wbs elements and activated availbility control and budgeted.
and also invest program created. assigned to wbs elements also.
Kindly help me out.
Regards,
Pardhui think you should post this message in PS as this forum is for MM.
use below link.
/community [original link is broken]
Regards,
qsm sap -
Regardding CAll Transaction where i will get return value
Dear Expert ,
My Requirment is i am Passing parameter to call transaction it is working fine , but
i want to get data which is displayed after calling that transation .
Such as
sel_data-program = 'gp3umn8b57fzlorwxdm2y9lqq7e'.
sel_data-dynpro = 1000.
sel_data-dynbegin = 'X'.
APPEND sel_data.
CLEAR sel_data.
sel_data-fnam = 'S_FICTR-LOW'.
sel_data-fval = fund_cntr .
APPEND sel_data.
CLEAR sel_data.
sel_data-fnam = 'FIPEX-LOW'.
sel_data-fval = 'OS001' .
APPEND sel_data.
CLEAR sel_data.
sel_data-fnam = 'PAR_01'.
sel_data-fval = 'BFL' .
APPEND sel_data.
CLEAR sel_data.
sel_data-fnam = 'PAR_02'.
sel_data-fval = '2010' .
APPEND sel_data.
CLEAR sel_data.
CALL TRANSACTION 'FMRP_3FMB4004' USING sel_data . " AND SKIP FIRST SCREEN.
After Executing this code it calls this code 'FMRP_3FMB4004' with output such as Available budget and etc ...
this out put i want to return through call transaction which i am calling through RFC .
I Dont want to use SUBmit Report .
Regards
Deepak Dhamat .i have included that program name as a include program name
and accessed that table to get data .
Problem Solved .
Maybe you are looking for
-
Can't uninstall or reinstall Quicktime/Itunes etc.
I have Vista X64 I recently install itunes and quicktime. Now I want to remove them but it won't let me in control panel. So I manually deleted the folders in program files and did a search for the keywords in regedit and deleted every single referen
-
Simple Program Stuck (possibly in a loop)
Ok so i have a program which takes the students names from a file at location C:\Users\Patrick\Documents\Grades.txt and their grades and adds each students grades together to get their total average and than assigns them the letter grade they would r
-
Is anyone else experiencing the same problem or knows a solution?
-
How to open off iCloud Outlook add-in
It worked perfect until my employer invested in office 365. When it was installed it ended to work. After some trial and error incidents it suddenly worked, but now it has been shutoff again nad I cannot get it into funktion. It is very embaressing b
-
I downloaded the ibook instead of the audio book can I get a refund?
I downloaded the ibook instead of the audio book can I get a refund?