What is the main purpose of MEREP_EX_REPLIC transaction code

hi,
i want know the main use of MEREP_EX_REPLIC, MEREP_MIG and
MEREP_MON transaction codes.
Regards,
Anu

Hi anusha,
MEREP_EX_REPLIC- (Execute Replicator) is used for replicating SyncBO IDs.
MEREP_MIG -    (Used for Migration) When u go for migration of a SyncBO using the SAP transport technology we use the Export and Import options.
MEREP_MON-   (Mobile Monitor )The transaction MEREP_MON is a tool used to display inbound and outbound worklists of SyncBOs. Simply, transaction MEREP_MON allows you to see what is sent from the client to the MW and what happend when trying to send it to the Backend. May check there if you can see anything coming into the MW from the client. As well check what is the outcome (processing status) of these worklists.
Do check the below link...Its worth.
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/909d75c3-0801-0010-5f92-920a78c53daa">https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/909d75c3-0801-0010-5f92-920a78c53daa</a>
Similarly there are many other transactions...Check some of the below:
MCD - MI:Process Mobile Component
ME_WIZARD -ME:Registration and eneration
MEREP_EX_REPLIC-Execute Replicator
MEREP_LOG -Activity Log
MEREP_MIG -Migration
MEREP_MON- Mobile Monitor
MEREP_PD - Profile Dialog
MEREP_PURGE - Purge Tool
MEREP_SBUILDER - SyncBO Builder
MI_ALBACK - Back Up CCMS Alerts for MI
MI_ALMON - Alert Monitor for MI Alerts
MI_MCD -MI:Process Mobile Component
MI_MSD -MI:Process Mobile Component
S_ABA_72000157-Alert Customizing
SMOMO - Mobile Engine
Cheers,
kumarR
Message was edited by:
KumarR
        kumarR

Similar Messages

What is the main purpose of VBA in bex analyser

what is the main purpose of VBA in bex analyser

Hi,
you can enhance standard BEx functionality with VBA Macros (Excel).
Pls chk This link:
http://help.sap.com/saphelp_nw04/helpdata/en/f1/0a55f9e09411d2acb90000e829fbfe/frameset.htm
Regards
CSM Reddy

What is the main Purpose of ADF tool...

What is the main Purpose of ADF tool...

Not sure what you mean, but take a look at:
Oracle Application Development Framework - Wikipedia, the free encyclopedia
Oracle Application Development Framework - Oracle ADF
or, if you mean Oracle ADF Tools::
http://www.oracle.com/technetwork/developer-tools/eclipse/overview/adf-315490.html
Oracle ADF Tools

What is the main advantage in EJB Transactions.

My question is i can have a stateless bean to accept the client requests and will set the Autocommit of database to false and which will invoke the java bean component based up on transaction code and passes the database connection object . the java bean component may perform its business logic and return a success or failure to the stateless bean. then the stateless bean can commit or rollback the transaction.
In the above case i am able to achieve atomicity . In that case what is the need for Transactions.
Thanks
Bala.J

you're forgetting that EJBs are components.
I may decide that my component should call your component.
I may need to have all this work happen as a unit of work.
I may be on a different app-server (connections are not serializable)
Possibly your component is integrated into a larger work-flow process.
In these cases, a commit of rollback by your EJB would be incorrect.

What is the main purpose of aggregates

hi friends,
I need clarification on Aggregates.
=> why we create aggregates
=> What will happend in background after creation of aggregate and the need of switch on/off option..
cheers
mohhan

Aggregrates:
An aggregate is a rollup of fact data where a total value is sufficient and no detailed information is
needed.
So aggregates are like InfoCubes except that they summarize or aggregate data from an InfoCube.
When you use an aggregate, the summarization it represents does not need to be done during
runtime.
Aggregate functions happen in the background. They are not visible to the end-user.
Aggregates can be created: are not possible for:
For BasicCubes
On dimension characteristics
On navigational attributes
On hierarchy levels
Aggregates Cannot be created on
Multiprovider
RemoteCube
Ods Object
Infoset
When we need to use aggregates:
As a rule of thumb, an aggregate is reasonable and may be created if,
Aggregation ratio >10 i.e, 10 times more records are read than are displayed ( Aggregation ratio = Number of records read from DB / Number of records transferred)
AND
Percentage of DB Time > 30% ie; the time spent on database is a substantial part of the whole query runtime
I hope for creating aggregates i think the thumrule should be successful... But where can we check that Aggregation ratio > 10% and Percentage DB time > 30%.
AGGREGATES
There are three methods for viewing this data.
1. You can see in table RSDDSTAT.
2. By using t-code ST03
( Expert mode -> BW system load -> last minute's load)
3. By implementing BW Statistics.
(AWB -> Tools -> BW statistics for info cubes
o: OLAP (front end)
w: Warehouse (loading)
-> Delete specify from date, to date
-> select cube
-> execute )
You will have the following fields
QDBSL - No. of records selected
QDBTRANS - No. of records transferred.
QTIMEOLAP - OLAP time
QTIMEDB - DB time
QTIMECLIENT - Front end time
if QDBSL/QDBTRANS RATIO > 10 AND DBTIME >30 we will use aggregates.

What is the main purpose of ichat server what is it good for?

i've been looking at ichat server, but can't figure what advantages is has opposed to just using ichat on bonjour on my network? what is it good about it?

What are your goals here for chatting-style communications?
iChat server provides a way to leave messages for offline users, server federation, connection encryption, public key authentication, connections across networks, and various other features and options.
Here is the [iChat Server Administration 10.5|http://images.apple.com/server/macosx/docs/iChatService_Adminv10.5.pdf] manual; check the first couple of pages for some high-level details on the features. A quick Google search for iChat Server or jabberd or /"ichat server" features/ will most certainly turn up a [feature list|http://www.apple.com/server/macosx/features/ichat.html], too.

What is the main purpose of the synchronous disply in LV?

Anybody know what is really the synchronous display do. In the front panel, when we right click to the object,,
>>Advance
>>>Synchronous Display
When we can use this option??

If an indicator is set to have synchronous display the block diagram will always wait until the indicator value has been updated on the screen, otherwise everything will just continue even though the user interface has not "discovered" the new value yet....
here is an extract of NIs text on performance;
"In multithreaded systems, controls and indicators have a synchronous display pop-up item that controls whether or not updates can be deferred. In single-threaded execution, this item has no effect. However, if you turn this item on or off within VIs in the single-threaded version, those changes affect the way updates behave if you load those VIs into a multithreaded system.
By default, this item is off, which means that after the execution system passes data
to front panel controls and indicators, it can immediately continue execution. At some point thereafter, the user interface system notices that the control or indicator needs to be updated, and it redraws to show the new data. If the execution system attempts to update the control multiple times in rapid succession, you might not see some of the intervening updates.
In most applications, this significantly speeds up execution without affecting what the user sees. For example, you can update a Boolean value hundreds of times in a second, which is more updates than the human eye can discern. Asynchronous displays permit the execution system to spend more time executing VIs, with updates automatically reduced to a slower rate by the user interface thread.
If you want synchronous displays, you can turn the synchronous display on.
Note: Turn on synchronous display only when it is necessary to display every data value. Using synchronous display results in a large performance penalt
y on multithreaded systems."
MTO

The main purpose of table T778T - Infotypes per object type

What is the main purpose of T778T - Infotypes per object type.
How does it differ from other subdialogs/tables in T778V?
Points will be awarded.
Thanks
Olekan Babatonde

T778T -you can change the attributes of an infotype
You can make the following settings:
You can change the infotype names.
You can assign infotypes to standard object types or to customer- specific object types.
You can define another time constraint for an infotype.
T778V -In this step, you make the settings that are required for creating relationships.
You can make the following settings:
You can create new relationships.
You can control the response of the system (error messages, warnings, information) if the 100% mark is exceeded in the case of "weighted" relationships.
You can show or hide the weighting percentage of a relationship and, if required, define additional data for a relationship. You can specify, for example, in the view 'Additional relationship info' whether the recursiveness
You can define the object types that are allowed for each relationship and inverse relationship.
You can set up external relationships.
External relationships are relationships between external object types i.e. object types that are not stored in the PLOG database in Personnel Development and Planning. (See also the step "Maintain object types").
You can enter a time constraint for each relationship.
You can change the "alias" name (semantic abbreviation) of a relationship.

What are the main transaction codes in XI?

What are the main transaction codes in XI?

SAP XI TRANSACTION CODES
ALRTCATDEF- Alerts Configuration.
ALRTDISP - Display of Alerts Created
SXMB_IFR -> Start Integration Builder
SXMB_MONI -> Integration Engine - Monitoring
SXI_MONITOR -> XI: Message Monitoring
SXI_CACHE -> To Access IS runtime cache
SXI_SUPPORT -> Test all the Repository and Directory Objects
SXI_CACHE -> XI data directory cacheidx1 -> idoc adapter
IDX2 -> idoc metadata
IDX5 -> monitor idoc adapter
SM21 -> log di sistema
ST22 -> dump abap (analisi di eccezioni)
SMQ1 -> messages inbound e outbound queue
SMQ2 -> messages inbound e outbound queue
SMICM -> J2EE administration
ST06 -> stato della macchina cpu memory filesystem machine status - cpu, memory and file system.
ST03 -> workload.
SCC4 -> visualizza mandanti del sistema
WE20 -> partner profiles
sale - ale settings
RZ10 - edit system profile
SM59 ->mantain rfc destinations
BD64 -> mantain distribution model (trasformazioni)
SU01 -> users
AL08 -> list all logged users(user login logon)
SE10 -> Change Request
SE09 -> Change Request
WE05 -> All idocs
WE19 -> IDoc Test Tool
WE21 -> port definition
SE11 -> Data dictionary
SM21 -> log sistema xi
se37 -> mantain funcion modules
SICF -> http server configuration
SMGW -> trace, alzare livello di trace.
BD13 ->
BD64 -> modelli di distribuzione
PFCG -> Roles
tabella TSTC -> sap transactions codes
tabella TSTCT -> transaction descriptions
STMS -> transports management
SPAM -> apply ABAP support packages
SPAU -> manage objects after apply support packages
SE01 -> manage change requests
SLDCHECK -> Test SLD Connection
SLDAPICUST-> SLD API Customizing
SXMB_ADM -> Integration Engine - Administration
SXMB_MONI_BPE -> Process Engine - Monitoring
SE38 -> ABAP Editor
SE11 -> ABAP Dictionary
ST22 -> ABAP dump analysis
SPROXY-> ABAP Proxy Generation
SE80 -> Object Navigator
ABAPDOCU -> ABAP Documentation and Examples
SE24-> Class Builder
SM21-> Online System Log Analysis
SMQ1-> qRFC Monitor (Outbound Queue)
SMQ2-> qRFC Monitor (Inbound Queue)
RZ70-> SLD Administration
SM58-> Asynchronous RFC Error Log
SM59-> RFC Destinations (Display/Maintain)
SMICM-> ICM Monitor
WE60-> Documentation for IDoc types
BD87-> Status Monitor for ALE Messages
IDX1-> Port Maintenance in IDoc Adapter
IDX2-> Meta Data Overview in IDoc Adapter
WE05-> IDoc Lists
WE02-> Display IDoc
WE19-> Test tool
WE09-> Search for IDocs by Content
WE20-> Partner Profiles
WE21-> Port definition in XI
SE16-> Data Browser
SE93-> Maintain Transaction Codes
SM30-> Call View Maintenance
SU01-> User Maintenance
SM02-> System Messages
BD54 -Logical System Creation.
SWXF_PBUILDER -> for Detail BPM Process
SMQS - > to register the destination in QOUT scheduler
WEOUTQUEUE - > to start the queue processing
SMQR - > to register the queue
IDXPW - > to activate the IDOC message package
IDXP - > to monitor the message packages.
SWF_XI_CUSTOMIZING -> transaction to check prerequisites for integration processes.
http://www.erpgenie.com/abaptips/content/view/452/62/

What is the exact purpose of Transaction NACE and NAST Table?

Hi All,
What is the exact purpose of Transaction NACE and NAST Table?
Pls help me
Akshitha.

Hi
When a Output type in an apllication doc is configured with a Medium, Partner, Lang and other communication paramters an entry is created in NAST table
so to trigger the output an entry in NAST is compulsory
Output is a link between the Driver Program and the Sapscript,
An output type summarizes messages of the same meaning. It contains parameters that are valid for all its assigned messages, for example appropriate partner functions.
Transmission medium is a medium which the layout will be come out, this may be printout, Fax or Mail
Check this link.
http://help.sap.com/saphelp_nw2004s/helpdata/en/c8/19884743b111d1896f0000e8322d00/content.htm
ex-how to config output type.
You will assign output types using Transaction NACE.
Do the follow steps to assign output type
1)Select Application Type V2 which will have description Shipping.
2)Click on Output types button.
3)Go to change mode by pressing Ctrl+F4.
4)Select one output type which already exists
5)Do Copy As(F6)
6)Give your output type against Output Type field.
7)Under General data Tab, Give Program and Form routine and Save the data.
i think it a work of functional guy but at senior level i think it is not a big deal for abaper.
Check the following documentation
In NACE t-codewe have the application for each one. based on the application output type can be defined, based on output type script and print progrma can be defined.
If suppose data can be read from EDI then we should go for condition records.
So whenever we execute the script first composer checks the output type and then execute the program. in program whenever opn form FM will be populate then script will open first. After that again program till another FM will populate if it then script will populate........like it is cycle proces. Composer does all these things and at last it will submit that output to spool.
Go to the Transaction NACE.
choose the related sub module.. like billing or shipping
doubel click on Output Types
Choose the Output Type for which whcih you wanted your script to trigger
Then select the Output Type and double click on Processing Routine
Then go to create new entries--> Select the Medium (1- print output), then enter your Script and Print Program detls --> Save and come out
Now go to the Transaction (for which you have created the output type)... Issue output--> Select the output type --> Print....
Device Types for SAP Output Devices (Detail Information)
Definition
The device type indicates the type of printer to be addressed. When you define an output device, choose the name of the device type that was defined in the SAP System for your printer model, such as Post2 for a PostScript printer. In the case of frontend printing under Microsoft Windows, you can also use the generic (device-independent) device type SWIN.
The system uses the information in the device type to convert a document from the internal SAP character representation (spool request in OTF or in text format) to a device-specific, print-ready data stream (output request). Since a device type specifies attributes that apply to all devices of a certain model, it can be shared among device definitions. For example, all devices in the SAP spool system that are compatible with Hewlett-Packard LaserJet IIID printers would use the HPLJIIID device type.
You should not confuse the device type with the printer driver. The device type is the total of all attributes of an output device that the SAP System must know to control the output device correctly, such as control commands for font selection, page size, character set selection, and so on. These attributes also include the printer driver that SAPscript/Smart Forms (the SAP form processor) should use for this printer. The SAPscript printer driver that is to be used for devices of this type for output formatting is therefore only an attribute that the device type specifies.
How do I choose the correct device type?
In most cases, the SAP System already provides the appropriate device type for the printer type for the printer model that you want to use.
These standard device types are completely defined and need no modification or extension before you use them in device definitions.
You can also download missing device types from the sapserv server. For a current list of the supported device types, see SAP Note 8928 in the SAP Service Marketplace.
Most printers can be controlled using a generic format, such as PostScript. They can be switched to a mode that is compatible with one of the standard printers for which an SAP device type is available. In this case, a supported model is emulated.
Almost all printers are delivered with Microsoft Windows printer drivers. The system can control these printers with the generic (device-independent) device type SWIN. The Microsoft Windows spool system then performs the processing of the print data.
If the specified device types are not available, and generic device types cannot be used, you must create your own device type or edit a copy of an existing device type. We recommend that only those with specialist knowledge of the SAP Spool System and printer driver code do this. For more information, see Defining a New Device Type .
Attributes of a Device Type
A device type is distinguished by the attributes listed below. If you change an existing device type or create a new device type, you must change at least some of these attributes.
Character set: A character set specifies the codes with which characters must be represented in the print-ready output stream (output request). This code replaces the generic SAP characters set that is used internally by the SAP spool system (spool request).
Printer driver: You can specify different printer drivers for printing SAPscript documents and ABAP lists.
Print controls: Print controls represent printer operations, such as boldface or changing the font size. These print control are replaced by printer-specific commands during the creation of the output request from a spool request.
Formats: Formats specify the format supported by the SAP system. The system differentiates between SAPScript formats (DINA4 and LETTER) and ABAP list formats (X_65_132 = 65 rows/132 columns).
Page format: A page format is the interface between a format and SAPscript. It specifies the paper dimensions with which SAPScript can calculate the row and column lengths.
Actions: Actions are output device-specific commands that are required for the implementation of a format. The action printer initialization, for example, can contain a printer command with which the number of rows on a page is defined. There is a set of actions for every format supported by a device type.
Reward points for useful Answers

What is the main use of SM13

Hello All,
What is the main use of SM13. I know the SAP definition tha tit is used to check"whether update is active".
So if the transactions are struck here,can we manually process them?
I see a couple of records with Status V2. When I try to manually update them, the system gives me a message"Update request does not have status init". What does this mean.
What would be the document change flow to delta queue. Is it as below?
In case of V3 updates,
1)The user make changes to a document.
The changes are made to application tables in V1 step-VBAK,VBAP etc
2)The delta(after and before image is captured in the log tables---How is this done?
3)The changes(before and after images) from the log table are moved to extarction queue in V2 step using function modules
4)In SM13, if you see the transactions in V2 status ,does it mean that the FM are not yet executed
5)once v2 is complete(FM' run) the delta is moved from log table to extraction queue, v3 init is run
6)all the accumulated changes are moved from extraction queue to delta
Thanks
Simmi

Hi,
Check if the following threads help :
sm13 and lbwq
Re: SM13 Best Practices?
Cheers,
Kedar

What is the main use of mseg table

what is the main use of mseg table. when we should actually use this. please explain me in detail. then what is the difference betweeln mseg and mara table.

MM Process flow:
The typical procurement cycle for a service or material consists of the following phases:
1. Determination of Requirements
Materials requirements are identified either in the user departments or via materials planning and control. (This can cover both MRP proper and the demand-based approach to inventory control. The regular checking of stock levels of materials defined by master records, use of the order-point method, and forecasting on the basis of past usage are important aspects of the latter.) You can enter purchase requisitions yourself, or they can be generated automatically by the materials planning and control system.
2. Source Determination
The Purchasing component helps you identify potential sources of supply based on past orders and existing longer-term purchase agreements. This speeds the process of creating requests for quotation (RFQs), which can be sent to vendors electronically via SAP EDI, if desired.
3. Vendor Selection and Comparison of Quotations
The system is capable of simulating pricing scenarios, allowing you to compare a number of different quotations. Rejection letters can be sent automatically.
4. Purchase Order Processing
The Purchasing system adopts information from the requisition and the quotation to help you create a purchase order. As with purchase requisitions, you can generate Pos yourself or have the system generate them automatically. Vendor scheduling agreements and contracts (in the SAP System, types of longer-term purchase agreement) are also supported.
5. Purchase Order Follow-Up
The system checks the reminder periods you have specified and - if necessary - automatically prints reminders or expediters at the predefined intervals. It also provides you with an up-to-date status of all purchase requisitions, quotations, and purchase orders.
6. Goods Receiving and Inventory Management
Goods Receiving personnel can confirm the receipt of goods simply by entering the Po number. By specifying permissible tolerances, buyers can limit over- and underdeliveries of ordered goods.
7. Invoice Verification
The system supports the checking and matching of invoices. The accounts payable clerk is notified of quantity and price variances because the system has access to PO and goods receipt data. This speeds the process of auditing and clearing invoices for payment.
Common Tables used by SAP MM:
Below are few important Common Tables used in Materials Management Modules:
EINA Purchasing Info Record- General Data
EINE Purchasing Info Record- Purchasing Organization Data
MAKT Material Descriptions
MARA General Material Data
MARC Plant Data for Material
MARD Storage Location Data for Material
MAST Material to BOM Link
MBEW Material Valuation
MKPF Header- Material Document
MSEG Document Segment- Material
MVER Material Consumption
MVKE Sales Data for materials
RKPF Document Header- Reservation
T023 Mat. groups
T024 Purchasing Groups
T156 Movement Type
T157H Help Texts for Movement Types
MOFF Lists what views have not been created
A501 Plant/Material
EBAN Purchase Requisition
EBKN Purchase Requisition Account Assignment
EKAB Release Documentation
EKBE History per Purchasing Document
EKET Scheduling Agreement Schedule Lines
EKKN Account Assignment in Purchasing Document
EKKO Purchasing Document Header
EKPO Purchasing Document Item
IKPF Header- Physical Inventory Document
ISEG Physical Inventory Document Items
LFA1 Vendor Master (General section)
LFB1 Vendor Master (Company Code)
NRIV Number range intervals
RESB Reservation/dependent requirements
T161T Texts for Purchasing Document Types
Transaction codes:
RFQ to Vendor - ME41
Raising Quotation - ME47
Comparison of Price - ME49
Creation of PO - ME21N
Goods Receipt - MIGO
Invoice (Bill PAssing) - MIRO
Goods Issue - MB1A
Physical Inventory - MI01( Create doc)
MI04 (Enter Count)
MI07 (Post)
Also please check this links.
http://www.sapgenie.com/sapfunc/mm.htm
http://www.sap-basis-abap.com/sapmm.htm
Go thro this link, u will get a clear picture abt the MM flow.
MM flow
MM flow
MM flow
<b>Reward Points if it is helpful</b>
Thanks
Abhay Singh.

What are the main differences between Signal Express and Labview?

National Instruments provides a matrix so one can quickly compare the
various versions of Labview but no comparison of Signal Express with
Labview. Hence how does Signal Express compare with Labview? What
are some of the things one can do with Labview one can't do with
Signal Express?
Howard

hrh1818 wrote: Which version of Labview are you referring to? I don't consider the graphical version of Labview to be a full featured programming language. LabWindows/CVI is by a long shot a lot closer to being a full featured programming language than the graphical version of Labview.
Howard,
You clearly don't know what you are talking about. There is no "graphical version" of LabVIEW, there is just LabVIEW. Click on the article "Is LabVIEW a general purpose programming language?" written by the Jeff K. for some easy reading from a few years ago. It is all still true (except that object oriented features and recursion have been added in recent versions).
One of the main points at this years NI-week was the discussion of how processor development is switching more and more to multicore designs to improve performance because a simple boost in clock frequency is becoming more difficult. Linear, text based code is not well suited to take advantage of multticore design, while the dataflow based LabVIEW programming language automatically scales well to multiple processor cores, without any need to rewrite older code. I would say that only LabVIEW is futureproof in this respect. LabVIEW programmers are not wimps that are simply too stupid to write text based code. LabVIEW is not a toy language for people that don't want to learn a "real" programming language.
LabVIEW is arguably the best programming language in terms of getting things done! I've never felt limited with LabVIEW and my programs often don't even have anything to do with data acquisition or instrument control. The difference between text based code vs. LabVIEW is like "DOS vs. Windows", "Radio vs. HD television". "Trilobyte vs. Homo sapiens" (sorry Putnam ). Text based code is monochrome, archaic and outdated and its linearity imposes unecessary constraints on the programmer that can only be (partially) overcome by wasting even more time throwing even more code at it.
Sure, a seasoned text based programmer will initially have problems adapting to LabVIEW, just because you would need to adapt to and embrace the power of dataflow and not try to make a literal translation of the text code to LabVIEW, retaining old habits. If you get stuck, come back and ask here in the forum.
You were looking for object oriented features and failed. All you need to do is a quick site search. All the information is out there. Just because you cannot find it in the first five sentences of the glossy brochure does not mean it does not exist. Maybe you want to read one of the application notes such as:
LabVIEW Object-Oriented Programming: The Decisions Behind the Design
In general, you should avoid judgement until you have all information. Your opinions seem quite biased and superficial and not really based on hard facts.
Initially you asked about the difference between signal express and LabVIEW.
hrh1818 wrote:
> What kind of measurments do you want to do and what kind of requirements do you have?
> You can also see for yourself and download evaluation version of both.
No thanks, there has to be a better way to get an answer to my
question than get involved in a two month study project.
If you would answer the first question quoted above, we could certainly help you with the decision. Isn't that the main purpose of this thread?
You can also contact your local LabVIEW Field Engineer to go over your requirements and help you make a decision. They usually know their stuff!
Message Edited by altenbach on 09-02-2007 11:51 PM
LabVIEW Champion . Do more with less code and in less time .

What are the main tables using in vendor performance report.

what are the main tables using in vendor performance report.
how many select statements are in ABAP reports.

Refer the links -
vendor performance report !!!
vendor performance report
vendor performance report
I need standard vendor performance report
Regards,
Amit
Reward all helpful replies.

What are the main steps to be taken care while doing recording for LSMW

Hi,
I am facing problem in LSMW.
Can anybody suggest me that What are the main steps to be taken care while doing recording for LSMW for recording mm01 ?
thanks'
naresh

Hi,
Recording in LSMW is similar as SHDB.
in LSMW after you give Project-Subproject and Object.
1)Go to-> Maintain Object Attributes -> double click
2)Press Display/Change Button at top left to make editable mode.
3)Select radiobuton -> Batch Input -> Give Recording name say Z_mm01
4) Click the Recording Overview boton on right -> Give TCode which u want to record....
Rest refer the Document link attached.
Please find the links to various threads on the same.
Re: LSMW - Using a BAPI
BAPI, IDOC in LSMW
Upload the data in LSMW using BAPI
This one is the most complete document for the same
http://sapabap.iespana.es/sapabap/manuales/pdf/lsmw.pdf
http://service.sap.com/lsmw.
Regards
Kiran

What is the main purpose of MEREP_EX_REPLIC transaction code

Similar Messages

Maybe you are looking for