LSMW and enhancement objects

hi all
I am uploading new maintenance plans, using object 0460 in LSMW.
in Table MPOS, we added 2 enhancement fields that need of course to be included in the upload: how can i add them to the map in lsmw to be included?
thanks
Alisa

like I said befor, I used an existing object, not a recording.
the existing object includes all the possible tables of the transaction but, of course, not the enhancements.
I was thinking to upload all the data with the object and create a recording for a second upload for the enhancements.
any better idea?

Similar Messages

LSMW and enhancements

hi all
I am uploading new maintenance plans, using object 0460 in LSMW.
in Table MPOS, we added 2 enhancement fields that need of course to be included in the upload: how can i add them to the map in lsmw to be included?
thanks
Alisa

Hi Alisa,
I am also working on some thing similar, I would say the development for the two new enhnaced fields have to be completed first and then you can do the recording for the LSMW, other wise i think this problem can also be solved with the help of a technical resource (ABAP). Best is to tell your developer what you are planning to do and ask them if they can do the programming to add the new fields as that will be easier and faster approach, according to me, once the fields are there then you can thorughly check and go ahead with LSMW.
Hope it helps.
Regards
Anoop.

LSMW or EMIGALL for loading Businesss partner and Insurance Objects

Dear All,
I have to upload huge volumes of Business partners and Insurance objects in SAP insurance system,
I have checked EMIGALL, but it is for IS-U and my requirement is to load SAP insurance, i can use LSMW but am worried about the huge volumes
can you kindly suggest which is the best tool to upload the data considering high volumes of data, if LSMW is choosen can you also suggest me the best techniques to improve the performance
Kind regards,
Sujith

hii,
Go through this links.
<removed by moderator>
regards,
Sri
Moderator message: please do not post link farms.
Edited by: Thomas Zloch on Mar 27, 2011 12:12 PM

Delete customized enhancement objects issue

Hello everyone!
I'm quite new to SAP, and I was trying to make an enhancement to display additional field in the Product Header area. I did some steps, but at some point wanted to start again and delete enhancement. When I've tried to do that with the button "Delete component enhancement" warning message appeared that enhancement is not empty. Then I went to tc sm34 cluster BSPWDVC_CMP_EXT and deleted controller substitutes and enhancement definition there. After that I wanted to delete obsolete objects from the Z package and that's the point where the issue comes in. When I select, for example, BSP Application or classes created by wizard, and try to delete them, GUI just hangs. No errors, no warnings. If I try to create enhancement again without deleting obsolete objects, it asks me if I want to overwrite the BSP application, that was created with my first attempt. If I choose yes, it hangs in the same manner.
Is there a way to solve this? Please advise.
Thanks in advance,
Alex.

I've actually followed note 1122248, but at the step: "Then go to the BSP components in the ABAP workbench (SE80) that are used to store the enhancements. Search for the obsolete objects and delete them" GUI just hangs.
In addition, even if I try to create new package, or class, or even save a program in a local object GUI hangs. Is it some global problem?
Regards.

Differences between LSMW and BDC

Hi All
Please can you give me the few points about the differences between LSMW and BDC?
Awaiting for your Responce
Praveen

Hai Check with the following document
GOOD
THERE IS THREE TYPE OF METHOD IN BDC
BDC SESSION
CALL TRANSACTION
CALL DIALOG
What is BDC or batch input
The Batch Input is a SAP technic that allows automating the input in transactions. It lies on a BDC (Batch Data Commands) scenario.
BDC functions:
· BDC_OPEN_GROUP : Opens a session group
· BDC_CLOSE_GROUP : Closes a session
· BDC_INSERT : Insert a BDC scenario in the session
· The ABAP statement "CALL TRANSACTION" is also called to run directly a transaction from its BDC table.
It runs the program RSBDCSUB in order to launch automatically the session. The session management is done through the transaction code SM35.
The object itself is maintanable through the transaction SE24.
BDC methods:
Method
Description
Parameters
OPEN_SESSION
Opens a session
SUBRC (Return Code 0 OK)
SESSIONNAME (Session to be created)
CLOSE_SESSION
Closes a session
None
RESET_BDCDATA
Resets the BDC Internal Table...
None. Normally, for internal purpose
BDC_DYNPRO
Handles a new screen
PROGNAME (Name of the program)
DYNPRONR (Screen Number)
BDC_FIELD
Puts a value on the screen
FIELDNAME (Name of the field)
FIELDVALUE (Value to be passed)
CONSTRUCTOR
Constructor - Initializes NO_DATA
NODATA (No data character). The constructor is called automatically when the object is created.
RUN_SESSION
Launches a session with RSBDCBTC
None
CALL_TRANSACTION
Calls a transaction with the current BDC Data
MODE (Display Mode)
UPDATE (Update Mode)
TCODE (Transaction to be called)
BDC_INSERT
Inserts the BDC scenario in the session
TCODE (Transaction to be called)
BDC techniques used in programs:
1) Building a BDC table and calling a transaction,
2) Building a session and a set of BDC scenarios and keeping the session available in SM35,
3) Building a session and lauching the transaction right after closing the session.
BDC using Call Transaction
BDC using Call transaction involves calling an SAP transaction in back ground from within the ABAP
program. The process involves building an Internal BDC table containing the screen information needed to
execute the required transaction and then passing this to the Call transaction command (See code example).
The full procedure for creating a BDC program is as follows:
What is the difference between batch input and call transaction in BDC?
Session method.
1) synchronous processing.
2) can tranfer large amount of data.
3) processing is slower.
4) error log is created
5) data is not updated until session is processed.
Call transaction.
1) asynchronous processing
2) can transfer small amount of data
3) processing is faster.
4) errors need to be handled explicitly
5) data is updated automatically
BATINPUT/DIRECT INPUT
A: Batch-inputs can not be used to fill the "delivery due list" screen because it is not a dynpro. This is a standard SAP report. A SAP report (check with "System -> Status") may be called using SUBMIT sentence with the appropriate options . It is preferred to call a report than create a Batch-input program.
GO THROUGH THIS LINK
http://www.guidancetech.com/people/holland/sap/abap/zzsni001.htm
The LSM Workbench is an SAP R/3 based tool that supports the one-time or periodic transfer of data from non-SAP systems ("legacy systems") to SAP systems.
The LSM Workbench helps you to organize your data migration project and guides you through the process by using a clear sequence of steps.
The most common conversion rules are predefined. Reusable conversion rules assure consistent data conversion for different data objects.
LSMW vs DX Workbench
The LSM Workbench covers the following steps:
Read the legacy data from one or several files (e.g. spreadsheet tables, sequential files).
Convert the data from source format to target format.
Import the data using standard interfaces (Batch Input, Direct Input, BAPI, IDoc).
Experiences made in successful implementation projects have shown that using the LSM Workbench significantly contributes to accelerating data migration.
SAP provides this tool along with documentation to customers and partners free of charge.
Users of the LSM Workbench receive the usual support via SAP Net - R/3 Frontend (component BC-SRV-DX-LSM).
Releases:
Version 1.7.2 of the LSM Workbench ("LSMW 1.7.2") available
Attention : LSMW 1.7.2 requires an SAP R/3 system with SAP R/3 4.0 or SAP R/3 4.5.
Version 1.8.0 of the LSM Workbench (1.21mb) ("LSMW 1.8.0") available
Attention : LSMW 1.8.0 requires an SAP R/3 system with SAP R/3 4.6.
Version 3.0 of the LSM Workbench (1.89mb) ("LSMW 3.0") available for Web Application Server 6.10
Attention : LSMW 3.0 requires a SAP WAS 6.10. Functionality of version 1.7.2 and 3.0 are identical !
Version 4.0 of the LSM Workbench ("LSMW 4.0") integrated in Web Application Server 6.20
Attention : LSMW 4.0 is an integrated part of SAP WAS 6.20.
Thanks & regards
Sreenivasulu P
Message was edited by: Sreenivasulu Ponnadi

LSMW and transaction MM01

Hi experts!
I am going to extend several materials from one plant to another.
Is it possible to use LSMW and batch input recording at transaction MM01 with the copy-function?
Kind regards

Hello Lene,
I believe you can do this by choosing Business Object Method (BAPI) option of the LSMW attributes. Business Object should be BUS1001006, Method SAVEDATA, Message Type MATMAS_BAPI, Basic Type MATMAS_BAPI01. The related BAPI where the copy/change should take place is BAPI_MATERIAL_SAVEDATA - I suggest you read the documentation of this BAPI, I noticed
it states:
When changing material master data, you need enter only the material
number. In the header data, you must select at least one view for which data
is to be created. Depending on the view selected, you must maintain other
required parameters. If you do not enter values for all of the required parameters,
the method is ended with an error message.
Also, this BAPI provides structure PLANTDATA as an import parameter so I think you should be able to copy the materials into the new plant. If this works then you wouldn't need the Batch Input recording at all but when using this in LSMW remember to generate the inbound IDoc settings for this message type from the first screen of LSMW via menubar Settings->IDoc Inbound Processing.
Hope this helps.
Cheers,
Sougata.

LSMW and As-is To-Be

Hello all,
could anyone send me documents and web links related to LSMW and As-is To-be.
if possible also include some explanations about the above said concepts.
thanks,
Maxx

Hi Maxx,
The Legacy System Migration Workbench (LSMW) is a tool recommended by SAP that you can use to transfer data once only or periodically from legacy systems into an R/3 System.
The LSM Workbench carries out the following tasks:
Reads the transfer data from one or more files (for example, spreadsheets, sequential files
Converts the data from the source format into the target format
You can download the LSMW at no cost from SAPNet under Services, SAP Methodology and Tools, category Tools. You can also find more information about the LSMW here.
If you have installed the LSMW, it is available as a default tool in the Data Transfer Workbench.
In the Data Transfer Workbench you can use a conversion object created in the LSMW for tasks of type MAP. When the task is executed, the conversion program is generated and executed.
Link to teh initial upload :check this
<b>http://help.sap.com/saphelp_46c/helpdata/en/0c/e785d8f8af11d2a61f0060087832f8/frameset.htm</b>
regards
kp

LSMW and SCAT.

Hi all,
Can anybody send me the document for LSMW and SCAT.
I need it urgently.
My email id is [email protected]
Thanks in advance.
Regards,
MHP
Edited by: MHP on Jan 10, 2008 9:28 AM

Hai.
check this.
Step-by-Step Guide for using BAPI in LSMW
Note! The screen prints in this article are from ECC 5.0. They may differ slightly in other versions.
Introduction:
This document details the usage of BAPI in LSMW. We have used the example of migration of the purchase order data into SAP.
Pre-requisites:
It is assumed that the reader of this article has the minimum knowledge required on the Business Object, BAPI, Message Types and IDoc Types.
Step-by-Step Procedure:
Details of the BAPI used in this scenario:
Business Object: BUS2012
Method: CreateFromData
Details of Message Type and Basic IDoc Type:
Message Type: PORDCR
Basic IDoc Type: PORDCR02
Lets have a look at the BAPI first, before proceeding to the LSMW:
1. Go to Transaction BAPI
2. Click on Search Button
3. Enter the value BUS2012 and select Obj.type(Technical Object Name
4. Press ENTER
5. Following screen appears:
6. On the left side of the screen, Expand the PurchaseOrder.
7. Select PurchaseOrder and double-click on the same for details.
Building LSMW using BAPI:
1. Go to Transaction LSMW.
2. Enter the Project, Subproject and Object information and click on CREATE.
3. Enter the descriptions for Project, Subproject and Object.
4. Now select Settings à IDoc Inbound Processing
5. IDoc Inbound Processing screen appears. Enter the required details as shown below:
6. Click on Activate IDoc Inbound Processing.
7. Click on Yes when prompted for Activate IDoc Inbound?
8. Hit on Back to return to the main screen.
9. Click on Continue (F8). Following Screen appears:
10. Select the Step 1 Maintain Object Attributes and select Execute.
11. Select the radio button Business Object Method and enter the following details:
Business Object: BUS2012
Method: CreateFromData
Hit ENTER
12. Save and click on BACK button. Following information message is displayed.
13. Now select step 2 Maintain Source Structures and click Execute.
14. In this step, we need to maintain the source structure. In our example, lets consider the example of a file with 2 structures Head and Item data as shown below:
Click on Create and name the source structure as HEADERDATA. Now select HEADERDATA and click on Create again to create the child structure. Following popup appears:
Select Lower Level and click on Continue. Enter the Item data structure name.
Click Save and hit BACK button to go to the main screen.
15. Select step 3 Maintain Source Fields and hit execute.
16. Enter the fields as shown below:
17. Click SAVE and return to main screen.
18. Select step 4 Maintain Structure Relations and click Execute.
Select E1PORDCR and click on CREATE RelationShip. Following screen appears:
Select HEADERDATA and hit ENTER
Similarly do the same for the structure E1BPEKKOA, E1BPEKPOC and E1BPPEKET.
Click Save and return to main screen.
19. Select the step Maintain Field Mapping and Conversion Rules and click on execute. Maintain the Field Mapping as seen below:
20. Select step 7 Maintain Source Files and provide the link for the test file created. (Create a test file with the same structure as defined earlier).
Save and return to main screen.
21. Select the step Assign Files and click on Execute.
Assign the file provided to the source structure. Here the same file is provided for both the structures.
Save and return to the main screen.
22. Select the step Read Data and click on Execute.
Click on Execute.
Return to the main screen.
23. Select the step Display read data and click on execute.
Click on the structure name to get the field level values.
24. Return to main screen and now select Convert Data.
25. Return to the main screen and select Display Converted data.
26. Return to main screen and select Start IDoc generation.
27. Now select the step Start IDoc Processing on the main screen.
28. Return to main screen and click on Create IDoc overview. Here the data record and status records of the IDoc could be viewed
It is given in screen shot.
http://www.****************
BDC is the way to transfer data by writing a batch input program which can use either session or call transaction method.
LSMW used to transfer data without/less code.
What type of data we transfer using LSMW?
LSMW is best suited for transferring master data.
Actually BDC and LSMW are not comparable at all.
for example LSMW itself can use BDC as a way of mass data transfer.
BDC is a mass data transfer technique via screen logic of existing SAP Data entry transactions. It behaves as if you are manually making thousand of entires into sap system as a background job. And that is probably the reason why BAPI's are preffered over BDC's.
On the other hand LSMW is a tool to facilitate DATA migration from other legacy systems ... It contains step by step procedure for data migration.
Like Managing Data Migration Projects , Creating Source Structures , Mapping Source structures wid Target structures , etc etc
LSMW internally might well be using the following techniqes for data transfer..
1. IDOX
2. Direct Input / BDC
4. BAPI's
LSMW is an encapsulated data transfer tool. It can provide the same functionality as BDC infact much more but when coming to techinical perspective most the parameters are encapulated. To listout some of the differences :
LSMW is basicaly designed for a fuctional consultant who do not do much coding but need to explore the fuctionality while BDC is designed for a technical consultant.
LSMW offers different techinque for migrating data: Direct input ,BAPI,Idoc,Batch input recording. While bdc basically uses recording.
LSMW mapping is done by SAP while in BDC we have to do it explicitly .
LSMW is basically for standard SAP application while bdc basically for customized application.
Coding can be done flexibly in BDC when compared to LSMW
see this and do accordingly
http://esnips.com/doc/1cd73c19-4263-42a4-9d6f-ac5487b0ebcb/LSMW-with-Idocs.ppt
Go through the steps
Hi please go through the following steps for IDOC method
Step 1. Run the transaction ( /nlsmw ) you will reach to the screen
Here you have to specify
Project : 060_BUS_TRANS
Subproject : SERVICE_TICKET
Object : SRV_TICKET_ZSVT
click on the execute button .you will reach the screen :
The screen shows the 15 steps to Run the lsmw
Step 2) select the first step ( Maintain object attributes) and click the execute button.After clicking on the execute button you will reach at. the screen
Here you have to specify ( MEssage type and basic type)
click on the BACK button
Step 3) select the 2nd step ( Maintain source structures) and click the execute button
Here you have to specify the source structures.
Step 4) Select the 3rd step ( Maintain source fields) and click on the execute button :
Here you have to specify the fields present in the source structure
Step 5) select the 4th step ( Maintain structure relationship ) and click on the execute button :
Here you have to specify relationship between source and target structures
Step 6) select the 5th step ( Maintain field mapping ) and click on the exécute button :
Here you have to map the fields between source and target structure. Also you have to apply conversion rules here if any
STEP 7) select the 6th step and click on the exécute button
Here you can define any fixed value or user define routines
Step 8) select the 7th step ( Specify files) and click on the exécute button :
At This screen we have to specify the files for This we should be in change mode .So please click on the button shown in the above screen. After clicking on This button you will be in change mode and will be able to specify the files :
Step 9) select the 8th step ( Assign files) and click on the exécute button
For assigning files yoy should be in change mode do the same thing click on the button as shown in the above screen :
Then assign the files to different structures.
Step 10 ) select the 9th step ( Read Data) and click on the exécute button :
After clicking on the exécute button you will reach to the screen
Again click on the exécute button . After clicking on the exécute button you will reach to the next screen
Here you will see data is read.
Step 11) select the 10th step ( Display read data) and click on the exécute button :
Here you can see your test data present in test files assign to source sturcture
Step 12 ) select the 11th step ( Convert data) and click on the exécute button :
After clicking on the exécute button you will reach to the screen
Click on the exécute button as shown on the : After click on the exécute button you will reach to the next screen
Data is converted
Step 12th ( Display converted data is same as Display read data )
Step 13 ) select the 13th step ( Start idoc generation) and click on the exécute
button :
At this step Idoc is generated using converted data
Step 14) select the 14th step ( Start idoc processing ) and click on the exécute button :
After clicking on the exécute button you will reach to the screen :
And then click on the exécute button : After clicking on the exécute button you will reach to the final processive screen
If data is processed correctly you will see ( 53 Status message with green sign)
Check the following link:
http://www.sapbrainsonline.com/TUTORIALS/TECHNICAL/LSMW_tutorial.html
http://www.sapbrain.com/TOOLS/LSMW/SAP_LSMW_steps_introduction.html
http://esnips.com/doc/8e732760-5548-44cc-a0bb-5982c9424f17/lsmw_sp.ppt
http://esnips.com/doc/f55fef40-fb82-4e89-9000-88316699c323/Data-Transfer-Using-LSMW.zip
http://esnips.com/doc/1cd73c19-4263-42a4-9d6f-ac5487b0ebcb/LSMW-with-Idocs.ppt
http://esnips.com/doc/ef04c89f-f3a2-473c-beee-6db5bb3dbb0e/LSMW-with-BAPI.ppt
http://esnips.com/doc/7582d072-6663-4388-803b-4b2b94d7f85e/LSMW.pdf
for Long texts Upload
Please take a look at this..
http://help.sap.com/saphelp_erp2005/helpdata/en/e1/c6d30210e6cf4eac7b054a73f8fb1d/frameset.htm
LSMW with TABLE CONTROL
Refer the links -
just refer to the link below
http://www.sapmaterial.com/?gclid=CN322K28t4sCFQ-WbgodSGbK2g
1. Maintain Attributes:
Here you have to choose the second option and you can do the recording how this should work. Then assign the same to the Batch Input Recording name.
2. Maintain Source structure:
Create a structure name
3. Maintain Source field:
In this you have to create a structure same as that of the input file
eg: name
age
4. Maintain structure relations:
This will link the structure to the input file.
5. Maintain field mapping and conversion rules:
Here is the place where you can do coding, depending upon the code you have written or assignment you have done the values will get picked up from the file and get processed.
6. Maintain field mapping and conversion rules:
If you have any fixed values you can define here.
7. Specify files:
Specify the input file path and type.
8. Assign files:
This will assign ur file to the Input file
9. Read Data:
This will read ur data from teh file.
10. Dispaly Read Data:
You can see the uploaded data
11. Convert Data
This will convert the data to the corresponding format for processing
12. Display Converted data:
13. Create batch input session
Here this will create a batch input session for processing
14. Run Batch Input session:
By clicking on the session and process the same you can do teh needfu.
regards
sowjanya.b.

Data Conversion: LSMW and CATT

Hi Experts
I am plaiing to use LSMW and CATT in data conversion for PP objects.
Can somebody provide me training material on how to record and use these tools.
Any help will be appreciated.
Thanks
Gaurav

hi,
catt:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/erpfi/catt%2b-%2bcomputer%2baided%2btest%2btool
http://help.sap.com/saphelp_nw04/helpdata/en/74/17f6eaecf511d2bdd4080009b4534c/frameset.htm.
lsmw:
http://help.sap.com/saphelp_nw04/helpdata/en/87/f3ae63e68111d1b3ff006094b944c8/frameset.htm
reward if useful,
thanks and regards

Enhancement object does not exist for enhancement implementation

Hi Experts,
When i tried activating my implementation, i got the sujected error. any kind of inputs will be very helpful. This is an existing implementation and was last changed in October, I just wanted to added few more changes to that.
Here is the long description of the problem.
Diagnosis
An enhancement implementation xxxxxxxxx was delivered to customers, but the enhanced object YYYYYYYYYY does not exist in the system. The corresponding record does not exist in Table .
This can have different reasons:
The enhanced program object YYYYYYYYYY belongs to a different software component than the enhancement and this software component was not relevant for delivery.
An error occurred during system setup so that the enhanced object YYYYYYYYYY was not imported.
The enhancement implementation xxxxxxxxx is obsolete and the enhanced object YYYYYYYYYY has meanwhile been deleted or copied. As a result, there could be enhancement implementations in the system that have not been adjusted or that have incurred an error during deletion or renaming.
Procedure
Contact your system administrator and try to clarify the problem - if necessary, with SAP's help.

Hi Reddy,
1) Please go through the enhance implementation of that. 2) Check whether any thing activation is missing.3) Check the implementation class. It is better to understand if you explain for which badi you are using.
Regards,
Madhu.

The enhancement object ENHS cannot be read

Hi Genius,
When i am trying to create an enhancemant point in ECC 6.0, I am getting the below error message.
The enhancement object ENHS cannot be read.
Exception of class CX_ENH_IO_ERROR.
Source plug-in is not getting created.
Anyone can help in this.
Thanks in advance,
Nithya

Hi Nithya.
I would like to suggest my opinion, as it is similar to your case.
[SDN - Reference - Error Description - The enhancement object ENHS cannot be read - Exception of class CX_ENH_IO_ERROR|Enhancement Framework and Support Packs SAPKB70011-13;
[SDN - Reference - Error Description - The enhancement object ENHS cannot be read|The enhancement object ENHS cannot be read;
Hope that's usefull.
Good Luck & Regards.
Harsh Dave

Differnce between lsmw and bdc

what is the diffrence between LSMW and BDC

hi
lsmw is user friendly functional consultant can do it with out technical consultant help there is no program required
bdc abaper help is needed some code should be developed
for master data uploading lsmw is suggestable
for transaction data bdc is suggestable
BDC(Batch data communication) is program tool used to load the data which program developer creates from scratch.Traditionaly this is the mechanism used to load the data.thsi you need to do technacally for this you required technical knowledge.
LSMW - Legacy System Migration Workbench SAP has developed user friendly tool for loading the data of the specific objects(vendor master, customers, orders so on) and this can be used by the functional consultant or end user without understanding the underlying program code. No ABAP knowledge is required to use this tool. This tool can be used to load the legacy data and also to conduct mass data changes in the system
Thanks & Regards
phaneendra
Edited by: phaneendra Reddy on Sep 23, 2008 6:21 AM

Releasenotes, bugfixes and enhancements

Hello,
I'm currently using Headstart version 6.5.1(.0). Can anyone send me the releasenotes, bugfixes or enhancements of all patches since then till version 6.5.3., or can anyone give me a good reason of upgrading.
All can be send to [email protected]
Thank you very much.

Kristof,
The release notes of all patches.
Headstart Oracle Designer PATCH 6.5.3.0 FOR 9i
==============================================
This patch is ready for use with Designer 9i, Forms 9i and Reports 9i.
Also it addresses the following bugs and enhancement requests
(mostly the same that are addressed in PATCH 6.5.3.0 FOR 6i):
Bug No. Description
====== =======================================================================
2309129 - ERROR IN UNLD_RPTS.SQL SCRIPT
2309202 - NAVIGATOR FORMS DO NOT HAVE CG$STARTUP_MODE, CAUSES ERROR
2441289 - SAVE BUTTON STAYING DISABLED WHEN IT SHOULD BE ENABLED
2482013 - LOGGING INTO 9I SERVER AS SYS MUST BE DONE AS SYSDBA
2483045 - CHANGE OBJECT LIBRARY USAGE STANDARD IN HEADSTART USER GUIDE
2497339 - CALENDAR-LOV WITH TIME HAS EXTRA BUTTONS, PROBLEM WHEN NULL VALUE
2499198 - USE CALENDAR LOV, GET FRM-40102: "RECORD MUST BE ENTERED OR DELETED
FIRST"
2504387 - SET QMSOLB65.OLB DISPLAY ONLY ITEMS (CGSO$%_DO) TO ENABLED=YES
2520101 - OFGTEL65.PLL CANNOT BE COMPILED AGAINST HST65 TEMPLATE PACKAGE OWNER
2520119 - GENERATION OF HEADSTART DEMO FORM HSD0034F GIVES CDG-01117 INVALID
DISPLAY TYPE
2520191 - MESSAGE QMS-00125 DOES NOT EXIST IN QMS_MESSAGE_PROPERTIES, USED IN
QMSLIB65
2521218 - HEADSTART 6I DOES NOT COMPILE WITH FORMS 9I
2529003 - CAPI SHOULD NOT INCLUDE COLUMNS WITH COMPLETE = NO
2570562 - 'SAVE OLD DATA' NOT GENERATED WHEN CAPI UTILITY PARAM
'TAPI TRIGGERS' IS NO
2600939 - IF SUBTYPE ATTRIBUTE MAPPED TO MULTIPLE TABLES, UTILITY CAN TAKE THE
WRONG ONE
2605551 - STILL HAVE CODE FOR '_CASDEL' IN QMSLIB65.PLL QMS$FORMS_ERRORS
2635597 - HEADSTART 6.5 UTILITIES THAT CALL BLTEXT.DELETE_TAGGED_BLOCK FAIL
2635613 - CALL TO QMS$BLOCK.GO('<BLOCK NAME>') IN QMSLIB65 IS CASE SENSITIVE!!
2635789 - CAPI VALIDATED BUSINESS RULE AGAINST WRONG ROW FROM INTERNAL ROW
STACK
2651107 - CHANGE_CONNECTION DOES NOT UPDATE ENTIRE INFO ABOUT APPLICATION
Headstart Oracle Designer PATCH 6.5.3.0 FOR 6i
==============================================
This patch addresses the following bugs and enhancement requests:
Bug No. Description
======= ======================================================================
2309129 - ERROR IN UNLD_RPTS.SQL SCRIPT
2309202 - NAVIGATOR FORMS DO NOT HAVE CG$STARTUP_MODE, CAUSES ERROR
2482013 - LOGGING INTO 9I SERVER AS SYS MUST BE DONE AS SYSDBA
2441289 - SAVE BUTTON STAYING DISABLED WHEN IT SHOULD BE ENABLED
2483045 - CHANGE OBJECT LIBRARY USAGE STANDARD IN HEADSTART USER GUIDE
2497339 - CALENDAR-LOV WITH TIME HAS EXTRA BUTTONS, PROBLEM WHEN NULL VALUE
2499198 - USE CALENDAR LOV, GET FRM-40102: "RECORD MUST BE ENTERED OR DELETED
FIRST"
2504387 - SET QMSOLB65.OLB DISPLAY ONLY ITEMS (CGSO$%_DO) TO ENABLED=YES
2520101 - OFGTEL65.PLL CANNOT BE COMPILED AGAINST HST65 TEMPLATE PACKAGE
OWNER
2520119 - GENERATION OF HEADSTART DEMO FORM HSD0034F GIVES CDG-01117 INVALID
DISPLAY TYPE
2520191 - MESSAGE QMS-00125 DOES NOT EXIST IN QMS_MESSAGE_PROPERTIES,
USED IN QMSLIB65
2529003 - CAPI SHOULD NOT INCLUDE COLUMNS WITH COMPLETE = NO
2570562 - 'SAVE OLD DATA' NOT GENERATED WHEN CAPI UTILITY PARAM
'TAPI TRIGGERS' IS NO
2600939 - IF SUBTYPE ATTRIBUTE MAPPED TO MULTIPLE TABLES, UTILITY CAN TAKE
THE WRONG ONE
2605551 - STILL HAVE CODE FOR '_CASDEL' IN QMSLIB65.PLL QMS$FORMS_ERRORS
2635597 - HEADSTART 6.5 UTILITIES THAT CALL BLTEXT.DELETE_TAGGED_BLOCK FAIL
2635613 - CALL TO QMS$BLOCK.GO('<BLOCK NAME>') IN QMSLIB65 IS CASE SENSITIVE!
2635789 - CAPI VALIDATED BUSINESS RULE AGAINST WRONG ROW FROM INTERNAL
ROW STACK
2651107 - CHANGE_CONNECTION DOES NOT UPDATE ENTIRE INFO ABOUT APPLICATION
Headstart Oracle Designer 6i PATCH 6.5.2.3
CDM RuleFrame Performance Improvement
==========================================
The main purpose of this patch is to improve the performance of the
CDM RuleFrame engine when large transactions are involved.
The functionality of CDM RuleFrame is only slightly changed by this patch:
- The utility 'Create CAPI Custom Service' makes it possible to include
a CAPI Custom Service (i.e. your own package or function) in more
than one CAPI (see "BUG 2419371" below)
- The utility 'Create VAPI Definition' can now also create VAPI's for
subtypes (controlled by new utility parameter)
This patch addresses the following bugs and enhancement requests:
Bug No. Description
======= ======================================================================
2070417 - PERFORMANCE ENHANCEMENT SUGGESTION FOR DISABLING CDM
RULEFRAME IN BATCH MODE
2204246 - USE NATIVE DYNAMIC SQL FOR RULEFRAME RUNTIME
SOFTWARE
2220682 - IMPROVE RULEFRAME RUNTIME PERFORMANCE WITH NOCOPY
IN TRANSACTION MANAGEMENT
2220697 - RULEFRAME STACK: USE TEMPORARY DATABASE TABLES INSTEAD
OF PL/SQL TABLES
2220707 - STORE ROWS IN RULEFRAME ROW STACK ON AN INDEX CALCULATED BY
A HASH FUNCTION
2220908 - ELIMINATE ROW STACK FROM CAPI AND MAKE OLD ROW STACK SMALLER
2227746 - ENHANCE RULEFRAME PERFORMANCE BY MINIMIZING CAPI USE OF
FIND_ON_STACK
2249250 - WHEN CREATING CAPI FOR TABLE WITH MANY COLUMNS: ORA-06502 VALUE
ERROR
2259418 - IMPROVE RULEFRAME PERFORMANCE BY ENFORCING CERTAIN RULES
IMMEDIATELY
2394119 - RUNNING UTILITIES ERR.SQL GIVES ORA-20000: ORU-10028: LINE
LENGTH OVERFLOW
2394166 - WHEN BUSINESS RULE ALREADY EXISTS, UTILITY STILL TRIES TO
INSERT TRIGGER
2396132 - UTILITY JOURNALLING BUSINESS RULES ORA-01401: INSERTED VALUE
TOO LARGE IN BLTEXT
2419371 - POSSIBILTY TO USE SAME CUSTOM SERVICE IN MORE THAN ONE CAPI
PACKAGE
2441447 - REMOVE WORKAROUND FOR BUG 1347738 IN CAPI GENERATOR (HSU_CAPF)
2481957 - DEFAULT IN SPECIFICATION OF HSU_BRTR.RUN AT WRONG PARAMETER
2485658 - CDA-01305 COLUMN UID - WHEN SAVING RESULTS OF REFRESHING JOURNAL
TABLE UTILITY
Headstart Oracle Designer 6i PATCH 6.5.2.2
==========================================
This patch addresses the following bugs and enhancement requests:
Bug No. Description
======= ======================================================================
2283093 - RUNNING REPORTS USING DESTYPE=CACHE FROM REPORT LAUNCH FORM
2283122 - ERROR WHEN CLOSING WINDOW AFTER DUPLICATE RECORD KEY
2285936 - PROBLEMS WITH REPORT LAUNCH FORM IN 6.5.2.1 SUPPLEMENT OPTION
2303927 - QMS0012 REPORT LAUNCH FORM NO DEFAULT VALUES IN PARAMETERLIST AFTER
STARTUP
Headstart Oracle Designer 6i PATCH 6.5.2.1
==========================================
This patch addresses the following bugs and enhancement requests:
Bug No. Description
======= ======================================================================
1696475 - ONLINE HELP FOR REPORTS HAS STRANGE URL
1702857 - ORA-00600 WHEN TRYING TO RUN HEADSTART FORM USING FORMS DEBUGGER
1727439 - POOR PERFORMANCE IN UTILITY 'CREATE CAPI DEFINITION'
1727886 - ERRORS IN 'CREATE CAPI DEFINITION' UTILITY ARE IGNORED
1747626 - RULEFRAME 6I BUS. RULE VIOLATION ON DELETED RECORD GIVES ORA-01403
OR QMS-00100
1754565 - PROCEDURE QMS$ABOUT_THIS_APPLICATION IS MISSING IN YOUR APPLICATION
LIBRARY...
1754740 - SETUP PART OF USER GUIDE SHOULD MENTION ACCESS TO HEADSTART DATABASE
OBJECTS
1754906 - CREATE FIND WINDOW(S) - SAVING CHANGES FAILED WITH CDA-01151
1764270 - CHAPTER 17 REFERS TO SCRIPT HSU_USER.GRT, WHICH IS NOT AVAILABLE
1769077 - SERVER SIDE INSTALLER SAYS USER ALREADY INSTALLED WHEN MANUAL IMPORT
UTILITIES
1769234 - LONG BLOCK.ITEM NAME RESULTS IN QMS-00100: ORA-06502:
PL/SQL: NUMERIC/VALUE ERR.
1769321 - VALUE ERROR IN HTML ONLINE HELP GENERATOR WHEN ITEMS HAVE LONG HINT
TEXTS
1781424 - CDM RULEFRAME: TRIGGER ALREADY EXISTS ERROR EVEN IF TRIGGER IS IN
OTHER FOLDER
1781454 - CREATE DOMAINS FOR DISCRIMINATOR COLUMNS TRIES TO UPDATE DOMAIN IN
WRONG FOLDER
1802399 - WHEN VIEWING LOG: UNHANDLED EXCEPTION IN VIEW_LOG_MESSAGES:ORA-06502
1832171 - DROP THE PK ON QMS_TRANSACTIONS FOR PERFORMANCE REASONS
1869480 - REPORTS MODULES NOT SHOWN IN MULTI SELECT LIST OF UTIL SET
IMPLEMENTATION NAME
1877521 - ORA-06502 WHEN MAINTAIN BUSINESS RULE DESIGN DEFINITIONS FOR STATIC
DOMAINS
1885204 - BUSINESS RULE TRANSFORMER: TRIGGERING EVENT <X> IS INVALID.
IT HAS NO ENTITY...
1890011 - UNABLE TO GENERATE DEFAULT NULL PARAMETER IN CAPI CUSTOM SERVICE
1890029 - HSD 65 USER GUIDE MENTIONS STFFMB PREF.INST. OF PREF.
SET QMS65_LOV_MODULE
1890035 - SMALL OMISSIONS AND TYPOS IN HEADSTART 65 USER GUIDE
1891637 - REDIRECT HEADSTART REFERENCED OBJECTS: INVALID VALUE FOR OLD QMS
APP VERSION
1978916 - WITH OLD DB TRIGGER, SEE 'ORA-20998'IN FORM INSTEAD IF THE ACTUAL
MESSAGES
1979278 - F9 DOES NOT WORK FOR LIST OF VALUES ON MODAL DIALOG FORM
(ALSO UP/DOWN)
1985903 - APPLICATION CLOSES WHEN USING MULTI-SELECT FEATURES IN MODAL DIALOG
WINDOW
1987743 - ORA-06508: PL/SQL: COULD NOT FIND PROGRAM UNIT.. <TAPI PACKAGE>.INS
2093405 - WHEN INSTALLING HEADSTART IN A 9I DATABASE, CG$ERRORS WON'T COMPILE
ANYMORE
2101690 - ONLINE HELP FOR REPORTS (QMS0012F) DOESN'T WORK
2148764 - CG$ERRORS WON'T COMPILE ON 9I DATABASE
2148774 - ENABLED PROPERTY SET YES ON CGSO$..._DO OBJECTS IN OBJECT LIBRARY
2176331 - ERROR WITH ORDER BY CURRENT FIELD
2176348 - GET ERROR IF LAST REPORT PARAMETER IS TYPE DATE
2176364 - CREATE VIEW DEFINITION DOESN'T UPDATE WHERE CLAUSE OF DOMAIN KEY
CONSTRAINT
2185321 - COMPILATION ERRORS ORACLE 9I: DIFFERENCES PARAMETER DEFAULTS PACKAGE
SPEC/BODY
Regards,
Marcel

Difference in lsmw and bdc

What is the advantage of using lsmw instead of bdc whether there is any disadvantage in using lsmw

Hi,
LSMW and BDC are vastly different.
BDC (Batch Data Communication) is a technology used for data transfer.
it is meant for transferring data thru SAP transactions itself. when u use BDC for data transfer,
the sequence of steps is the same as when u use standard sap transaction screens for data upload. the only difference is that u can use different options for foreground/background processing.
LSMW on the other hand is a tool that helps migrate data from a legacy system (non-sap system ) to SAP system.
it offers u various options to use either batch input, direct input, BAPIs or idocs.
it involves a series of some 17-18 steps to migrate data.
BDC:
Batch Data Communication (BDC) is the process of transferring data from one SAP System to another SAP system
or from a non-SAP system to SAP System.
Features :
BDC is an automatic procedure.
This method is used to transfer large amount of data that is available in electronic medium.
BDC can be used primarily when installing the SAP system and when transferring data from a legacy system (external system).
BDC uses normal transaction codes to transfer data.
Types of BDC :
CLASSICAL BATCH INPUT (Session Method)
CALL TRANSACTION
BATCH INPUT METHOD:
This method is also called as CLASSICAL METHOD.
Features:
Asynchronous processing.
Synchronous Processing in database update.
Transfer data for more than one transaction.
Batch input processing log will be generated.
During processing, no transaction is started until the previous transaction has been written to the database.
CALL TRANSACTION METHOD :
This is another method to transfer data from the legacy system.
Call transaction.
1) asynchronous processing
2) can transfer small amount of data
3) processing is faster.
4) errors need to be handled explicitly
5) data is updated automatically
Session method.
1) synchronous processing.
2) can tranfer large amount of data.
3) processing is slower.
4) error log is created
5) data is not updated until session is processed.
Session method is to populate the data by filling BDC structure
and keep as session to process from SM37 to post in appropriate Transaction.
Call transaction method is to post the data directly into the Transaction from an Executable program.
Features:
Synchronous processing. The system performs a database commit immediately before and after the CALL TRANSACTION USING statement.
Updating the database can be either synchronous or asynchronous. The program specifies the update type.
Transfer data for a single transaction.
Transfers data for a sequence of dialog screens.
No batch input processing log is generated.
For BDC:
http://myweb.dal.ca/hchinni/sap/bdc_home.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&
http://www.sap-img.com/abap/learning-bdc-programming.htm
http://www.sapdevelopment.co.uk/bdc/bdchome.htm
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html
LSMW:
The LSM Workbench is an R/3-based tool that supports You when transferring data from non-SAP systems ("Legacy Systems") to R/3 once or periodically.
The tool supports conversion of data of the legacy system in a convenient way. The data can then be imported into the R/3 system via batch input, direct input, BAPIs or IDocs.
Furthermore, the LSM Workbench provides a recording function that allows to generate a "data migration object" in an entry or change transaction.
The main advantages of the LSM Workbench:
Part of R/3 and thus independent of individual platforms
A variety of technical possibilities of data conversion:
Data consistency due to standard import techniques:
Batch input
Direct input
BAPIs (Business Application Programming Interfaces)
IDocs (Intermediate Documents)
The import technique to be used in an individual case depends on the business object.
Generation of the conversion program on the basis of defined rules
Clear interactive process guide
Interface for data in spreadsheet format
Creation of data migration objects on the basis of recorded transactions
Charge-free for SAP customers and SAP partners
http://help.sap.com/saphelp_nw04s/helpdata/en/87/f3ae74e68111d1b3ff006094b944c8/content.htm
http://www.sap-img.com/sap-data-migration.htm
http://www.scmexpertonline.com/downloads/SCM_LSMW_StepsOnWeb.doc
http://allsaplinks.com/lsmw.html
http://myweb.dal.ca/hchinni/sap/lsmw_home.htm
some more links
BDC
http://www.sap-img.com/bdc.htm
LSMW
http://www.sap-img.com/sap-data-migration.htm
http://www.sapgenie.com/saptech/lsmw.htm
http://sapabap.iespana.es/sapabap/manuales/pdf/lsmw.pdf
http://www.sap.info/public/INT/int/glossary/int/glossaryletter/Word-17643ed1d6d658821_glossary/L#Word-17643ed1d6d658821_glossary
Thanks
Manju

Help for SAP BADI in 6.0 and Enhancement 6.0

I need help links for BADI and Enhancement in 6.0.
As well can anybody tell me about after creating a BADI in se18 how we can implement it with any standard program of SAP?
Message was edited by:
Moni Bindal

Hi,
Implementing Business Add-Ins (BADI)
The use of object orientated code within SAP has lead to new method of enhancing standard SAP code called
Business Add-Ins or BADI's for short. Although the implementation concept is based on classes, methods and
inheritance you do not really have to understand this fully to implement a BADI. Simply think of methods
as a function module with the same import and export parameters and follow the simple instructions below.
Steps:
1. Execute Business Add-In(BADI) transaction SE18
2. Enter BADI name i.e. HRPBSGB_HESA_NISR and press the display
button
3. Select menu option Implementation->Create
4. Give implementation a name such as Z_HRPBSGB_HESA_NISR
5. You can now make any changes you require to the BADI within this
implementation, for example choose the Interface tab
6. Double click on the method you want to change, you can now enter
any code you require.
7. Please note to find out what import and export parameters a
method has got return the original BADI definition
(i.e. HRPBSGB_HESA_NISR) and double click on the method name
for example within HRPBSGB_HESA_NISR contract is a method
8. When changes have been made activate the implementation
just refer to the link below. it will of great help to u.
http://www.sapmaterial.com/?gclid=CN322K28t4sCFQ-WbgodSGbK2g
Regards

LSMW and enhancement objects

Similar Messages

Maybe you are looking for