Sales order - difference between Cancel and Close?

Hi All,
In Sales Order, is there any differences between Cancelling order and Closing order?
Thanks
Ric

Hi Ric...........
Difference between Cancel and close means if you raised Sales Order and your terms and condition is not accepted by your customer in such situation you have to cancel your order.
if you raised Sales Order and you did not agree with the payment terms sent by your customer in such situation you have to cancel your order.
if you raised Sales Order and put a date on which sale order should be canceled automatically if its not proceeded further from your customer in such situation you have to cancel your order.
But order cancellation must be before raising and type of target document.
Order close means if you have already raised target document against SO and now before completing order you have to stop the transactions or as per the validity of the Sales Contract then in such case you have to close the document......
Hope this is sufficient to know the difference between those....
Regards,
Rahul

Similar Messages

Difference between techo and close order

Dear all
plz tell what is a difference between techo and close production order
guide me
Rgds
SDB
Edited by: surendra patil on Aug 21, 2008 12:18 PM

TECO means ending a production order from a logistical viewpoint. This function is usually used, if the execution of an order has to be stopped prematurely or if the order
could not be executed in the required manner and open requirements for the order (reservations,capacities) should be deleted.
The following actions are executed if an order is set to TECO:
· The order is not relevant for MRP planning
· Reservations are deleted
· Capacity requirements are deleted
· Purchase requisitions for external operations or non-stock materials are deleted
· The order and its operations receive the system status (TECO)
If an order is technically complete, you cannot change it. The fields in the order are displayed but
cannot be changed. You can however cancel technical completion, for instance if order data has
to be changed.
After technical completion you can still make posting for order.
For instance,material withdrawal or a confirmation can be posted if they were previously forgotten.
*Closed Order :
*The Closed (CLSD) status has been introduced in the production order. It has the following
characteristics:
· No more costs can be posted to the order, that is, confirmations and goods movements are
no longer permitted for the order.
· The order can no longer be changed. Exceptions to this are revoking the CLSD status and
setting the deletion flag.
· All actions relating to the status technically completed are executed
· In a collective order, the CLSD status is also set for subordinate orders.
· If the system comes across an order in the collective order that cannot be closed, the orders
that come between this order and the leading order are also not closed. Other subtrees are
closed if they only contain orders that can be closed.
Regards,
Hrishi.

Difference Between Shutdown and Close Database

Hi all,
Let say I want to start the instance of database with the following processes :
1. STARTUP MOUNT
2. ALTER DATABASE OPEN
With two commands above, now the database is open. Then, I want to close the database with command :
3. ALTER DATABASE CLOSE
After this, I want to reopen the database again by using this :
4. ALTER DATABASE OPEN
I know that it will produce an error because when the database is opened and closed, its lifetime has already ended, so we must shutdown it first.
My questions are :
1. What's the difference between CLOSE and SHUTDOWN ? Suppose in the case above, I want to close the database. Why don't I just type SHUTDOWN ? Why is it necessary for me to use command CLOSE instead of SHUTDOWN ?
2. What are the conditions of database when I CLOSE database, also, what are the conditions of database when I SHUTDOWN database ? I want to know more detail because I have tried to find in google, but now satisfying result
Thanks before
Edited by: cycon on Nov 8, 2010 9:00 AM

alter database close;this you can execute only from OPEN status
when ever you close the database it will go to mount status here you cannot open the database again, you need to clean sutdown and need to startup.
alter database open;ths you can execute only on MOUNT status, it will takes you to mount --> open status.
Thanks

Difference between stop() and close()

Hi there,
I'm running a JMS test case, and in the setUp routine (run before each test case is called) I'm clearing out any messages in any of my test queues (can't use temporary queues).
My cleanup code looks like this:
-create a connection
-create a session
-setup my messagelisteners to consume the existing messages
-start the connection
-give some time for the messages to be consumed
-call connection.close()
Now, this works, but my question is why can't the last line be:
-call connection.stop()
Seems to me like in this instance the result should be the same, but it doesn't work! Can someone explain why not?
Thanks!
Mark

BTW to test JMS code I find myself frequently using an ActiveMQ broker embedded in the test case - with the 'persistence' option set to false. Then you have a fully functional JMS broker - in RAM - which has no persistence, so there's no messages to delete etc.
e.g.
BrokerService broker = new BrokerService()
broker.setPersistence(false);
broker.start();
// now go ahead and connect on vm://localhost or whatever
James
http://logicblaze.com/
Open Source SOA

What is a difference between MB01 and MBST for GR Cancellation

Hi,
What is a difference between MB01 and MBST for GR Cancellation.
Regards,
Aditya

Hi,
MB01 is used for doing the GR for collective PO at a single instance.
This transaction will be utilize when an individual needs to create a material document. A material document can only be displayed or changed after it has been generated in the SAP system. In a computer based inventory management system, the principal of "no posting without a document" applies. A material document is generated and stored in the SAP system for every transaction that causes a change in stock.
As mentioned, when a goods movement is posted a material document is created. It serves as proof of the movement If the movement updates a G/L account; an accounting document is also created. The material and accounting document s are identified by unique document numbers
Once you have posted a goods movement, you cannot change material numbers, quantities or account numbers in the material document. You can however use the Change command to enter additional or change text information such as comments or references. To reverse the movement or change a quantity, a new transaction must be performed.
MBST:-
Perform this transaction when a previously performed goods issue must be cancelled due to an error in data entry or other circumstances deem the previous transaction unnecessary.
Prerequisites:-
A previously played transaction that requires cancellation.
An existing Material Document in SAP.
This Transaction will be utilized when an individual needs to cancel a material document due to a data entry error or other circumstances deem a previous transaction unnecessary. A material document can only be cancelled after it has been generated in the SAP system. A material document is generated and stored in the SAP system for every transaction that causes a change in stock.
Performing this transaction will "undo" a previous transaction by reversing individual line items in a material document or by reversing an entire material document. This transaction will reinstate the affected cost center, purchase order or stock location to the state they were in prior to playing the original transaction.
Regards,
Archit

Difference between BAPI and RFC?

Difference between BAPI and RFC?
also where to use BAPI and where to use RFC?

Hi,
BAPI are RFC enabled function modules. the difference between RFc and BAPI are business objects. You create business objects and those are then registered in your BOR (Business Object Repository) which can be accessed outside the SAP system by using some other applications (Non-SAP) such as VB or JAVA. in this case u only specify the business object and its method from external system in BAPI there is no direct system call. while RFC are direct system call Some BAPIs provide basic functions and can be used for most SAP business object types. These BAPIs should be implemented the same for all business object types. Standardized BAPIs are easier to use and prevent users having to deal with a number of different BAPIs. Whenever possible, a standardized BAPI must be used in preference to an individual BAPI.
The following standardized BAPIs are provided:
Reading instances of SAP business objects
GetList ( ) With the BAPI GetList you can select a range of object key values, for example, company codes and material numbers.
The BAPI GetList() is a class method.
GetDetail() With the BAPI GetDetail() the details of an instance of a business object type are retrieved and returned to the calling program. The instance is identified via its key. The BAPI GetDetail() is an instance method. BAPIs that can create, change or delete instances of a business object type
The following BAPIs of the same object type have to be programmed so that they can be called several times within one transaction. For example, if, after sales order 1 has been created, a second sales order 2 is created in the same transaction, the second BAPI call must not affect the consistency of the sales order 2. After completing the transaction with a COMMIT WORK, both the orders are saved consistently in the database.
Create( ) and CreateFromData! ( )
The BAPIs Create() and CreateFromData() create an instance of an SAP business object type, for example, a purchase order. These BAPIs are class methods.
Change( )
The BAPI Change() changes an existing instance of an SAP business object type, for example, a purchase order. The BAPI Change () is an instance method.
Delete( ) and Undelete( ) The BAPI Delete() deletes an instance of an SAP business object type from the database or sets a deletion flag.
The BAPI Undelete() removes a deletion flag. These BAPIs are instance methods.
Cancel ( ) Unlike the BAPI Delete(), the BAPI Cancel() cancels an instance of a business object type. The instance to be cancelled remains in the database and an additional instance is created and this is the one that is actually canceled. The Cancel() BAPI is an instance method.
Add<subobject> ( ) and Remove<subobject> ( ) The BAPI Add<subobject> adds a subobject to an existing object inst! ance and the BAPI and Remove<subobject> removes a subobject from an object instance. These BAPIs are instance methods.
Regards,
Prakash

Difference Between BAPI And RFC in ABAP

Hi,
i want to know difference between BAPI and RFC in SAP,
can we call SAP GUI screen from NON SAP System Using BAPI.
Reg,
Hariharan

Hi Ravishankar,
The difference is not importat while you understand the concept.
I think, RFC is the protocol for calling functions from external systems in R/3.
I understand like BAPI a series of complet functions that SAP offers you for use and model a business use.
But if I need program a function that can be called for external system i would call it RFC_NAME, because is a unique function that makes a single task.
In other words, the difference i think is about work idea more than another thing.
RFC
A remote function call is a call to a function module running in a system different from the caller's. The remote function can also be called from within the same system (as a remote call).
RFC consists of two interfaces : A calling interface for ABAP Programs and a calling interface for Non-SAP programs.
The RFC Interface takes care of :-
- Converting all parameter data to the representation needed in the remote system
Calling the communication routines needed to talk to the remote system.
Handling communications errors, and notifying the caller, if desired ( using EXCEPTIONS paramater of the CALL FUNCTION).
BAPI
BAPIs are standardized programming interfaces (methods) enabling external applications to access business processes and data in the R/3 System.
BAPIs provide stable and standardized methods to achieve seamless integration between the R/3 System and external applications, legacy systems and add-ons.
BAPIs are defined in the BOR(Business object repository) as methods of SAP business object types that carry out specific business functions.
BAPIs are implemented as RFC-enabled function modules and are created in the Function Builder of the ABAP Workbench.
The most critical difference btwn BAPI and FM is that BAPI can be wrapped in Business objects whereas RFC cant.
BAPI are RFC enabled function modules. the difference between RFc and BAPI are business objects. You create business objects and those are then registered in your BOR (Business Object Repository) which can be accessed outside the SAP system by using some other applications (Non-SAP) such as VB or JAVA. in this case u only specify the business object and its method from external system in BAPI there is no direct system call. while RFC are direct system call Some BAPIs provide basic functions and can be used for most SAP business object types. These BAPIs should be implemented the same for all business object types. Standardized BAPIs are easier to use and prevent users having to deal with a number of different BAPIs. Whenever possible, a standardized BAPI must be used in preference to an individual BAPI.
The following standardized BAPIs are provided:
Reading instances of SAP business objects
GetList ( ) With the BAPI GetList you can select a range of object key values, for example, company codes and material numbers.
The BAPI GetList() is a class method.
GetDetail() With the BAPI GetDetail() the details of an instance of a business object type are retrieved and returned to the calling program. The instance is identified via its key. The BAPI GetDetail() is an instance method. BAPIs that can create, change or delete instances of a business object type
The following BAPIs of the same object type have to be programmed so that they can be called several times within one transaction. For example, if, after sales order 1 has been created, a second sales order 2 is created in the same transaction, the second BAPI call must not affect the consistency of the sales order 2. After completing the transaction with a COMMIT WORK, both the orders are saved consistently in the database.
Create( ) and CreateFromData! ( )
The BAPIs Create() and CreateFromData() create an instance of an SAP business object type, for example, a purchase order. These BAPIs are class methods.
Change( )
The BAPI Change() changes an existing instance of an SAP business object type, for example, a purchase order. The BAPI Change () is an instance method.
Delete( ) and Undelete( ) The BAPI Delete() deletes an instance of an SAP business object type from the database or sets a deletion flag.
The BAPI Undelete() removes a deletion flag. These BAPIs are instance methods.
Cancel ( ) Unlike the BAPI Delete(), the BAPI Cancel() cancels an instance of a business object type. The instance to be cancelled remains in the database and an additional instance is created and this is the one that is actually canceled. The Cancel() BAPI is an instance method.
Add<subobject> ( ) and Remove<subobject> ( ) The BAPI Add<subobject> adds a subobject to an existing object inst! ance and the BAPI and Remove<subobject> removes a subobject from an object instance. These BAPIs are instance methods.
Check these Links out
http://searchsap.techtarget.com/ateQuestionNResponse/0,289625,sid21_cid558752_tax293481,00.html
http://www.sap-img.com/abap/interview-question-on-bapi-rfc-abap-objects-tables.htm
http://www.sap-img.com/fu033.htm
http://www.sap-img.com/abap/ale-bapi.htm
Refer following SDN threads:
Diff. Between BAPI and RFC
Re: BAPI and RFC
Hope this resolves your query.
Reward all the helpful answers.
Regards

Credit Management: Difference Between Static and Dynamic Credit Check

Hi,
Could anyone tell the difference Between Static and Dynamic Credit Check?
According to website: http://www.sap-basis-abap.com/sd/difference-between-static-and-dynamic-credit-check.htm ... this is the answer:
====================
Simple Credit Check : Tr.Code - FD32
It Considers the Doc.Value + Open Items.
Doc.Value : Sales Order Has been saved but not delivered
Open Item : Sales Order has been saved , Delivered, Billed & Transfered to FI, but not received the payment from the customer.
Static Credit Check it checks all these doc value & check with the credit limit
1) Open Doc.Value / Sales Order Value : Which is save but not delievered
2) Open Delivery Doc.Value : Which is delivered but not billed
3) Open Billing Doc.Value : Which is billed but not posted to FI
4) Open Item : Which is transfered to FI but not received from the customer.
Dynamic Credit Check         1) Open Doc
                                            2) Open Delivery
                                            3) Open Billing
                                            4) Open Items
                                            5) Horizon Period = Eg.3Months
Here the System will not consider the above 1, 2, 3 & 4 values for the lost 3 months.
====================
Question 1: Could you further explain the above information, if there is any?
Question 2:: What is the Tcode to customize settings of:
a) Simple Credit Check (isn't this same with b) below?)
b) Static Credit Check
c) Dynamic Credit Check

Hi Tanish,
Diff between Static and Dynamic Filters.
Example One at report Level.
Create a variable for a Infoobject say ,Material .
1)In the Query Designer and if u restrict it to some 10 materials at query level, the report will display for only those 10 materials only.This is Static Filter.UR AHrdcoding it to those materials.You cant change them at Query Run time.i.e not changeable by user.
2)If u give the variable as input ,and when u run the query ,u can can choose the material,may 10 may be 1 or may 20 .It is dynamic.Changeable by user at run time
Example Two at DTP and Start Routine Level,say Document Type.
1)If u give filters in Start routine it is Static as u cannot change it in Production,not changeable by user.
2)f u give filters in DTP it is Dyanamic as u can change it in Production.U can give any doc type,Changeable by user at run time.
Hope it is Understood.
Rgds
SVU

Difference between MBBS and MB5L report.

All capital inventory till FY-2008-09 was transferred to revenue inventory by movemnt typr 411-Q in MB1B.All the codes those were transferrd are now appearing in MBBS but with zero value. However these codes are appearing in MB5L with value under GL 132006 (for capital items) and having value of 1.08 crores (0.94 crore for imported items and 0.14 crore for revenue items). The GL for all these codes neds to be changed to 132000 (revenue inventory GL) so that in MB5L also these items appear as revenue items.As of today GL of all the codes appearing under GL 132006 are to be changed to 132000 except code 496700086.
now, changes are reflected in report MBBS but not showing correct information in MB5L report..
Please guide what is the difference between MBBS and MB5L report.
Regards
SHreya

Hi,
MBBS gives stock values of "project'" and "sales order" only.
MB5L gives total stock value .

What's the Difference Between OLAP and OLTP?

HI,
What's the difference between OLAP and OLTP ? and which one is Best?
-Arun.M.D

Hi,
The big difference when designing for OLAP versus OLTP is rooted in the basics of how the tables are going to be used. I'll discuss OLTP versus OLAP in context to the design of dimensional data warehouses. However, keep in mind there are more architectural components that make up a mature, best practices data warehouse than just the dimensional data warehouse.
Corporate Information Factory, 2nd Edition by W. H. Inmon, Claudia Imhoff, Ryan Sousa
Building the Data Warehouse, 2nd Edition by W. H. Inmon
With OLTP, the tables are designed to facilitate fast inserting, updating and deleting rows of information with each logical unit of work. The database design is highly normalized. Usually and at least to 3NF. Each logical unit of work in an online application will have a relatively small scope with regard to the number of tables that are referenced and/or updated. Also the online application itself handles the majority of the work for joining data to facilitate the screen functions. This means the user doesn't have to worry about traversing across large data relationship paths. A heavy dose of lookup/reference tables and much focus on referential integrity between foreign keys. The physical design of the database needs to take into considerations the need for inserting rows when deciding on physical space settings. A good book for getting a solid base understanding of modeling for OLTP is The Data Modeling Handbook: A Best-Practice Approach to Building Quality Data Models by Michael C. Reingruber, William W. Gregory.
Example: Let's say we have a purchase oder management system. We need to be able to take orders for our customers, and we need to be able to sell many items on each order. We need to capture the store that sold the item, the customer that bought the item (and where we need to ship things and where to bill) and we need to make sure that we pull from the valid store_items to get the correct item number, description and price. Our OLTP data model will contain a CUSTOMER_MASTER, A CUSTOMER_ADDRESS_MASTER, A STORE_MASTER, AN ITEM_MASTER, AN ITEM_PRICE_MASTER, A PURCHASE_ORDER_MASTER AND A PURCHASE_ORDER_LINE_ITEM table. Then we might have a series of M:M relationships for example. An ITEM might have a different price for specific time periods for specific stores.
With OLAP, the tables are designed to facilitate easy access to information. Today's OLAP tools make the job of developing a query very easy. However, you still want to minimize the extensiveness of the relational model in an OLAP application. Users don't have the wills and means to learn how to work through a complex maze of table relationships. So you'll design your tables with a high degree of denormalization. The most prevalent design scheme for OLAP is the Star-Schema, popularized by Ralph Kimball. The star schema has a FACT table that contains the elements of data that are used arithmatically (counting, summing, averaging, etc.) The FACT Table is surrounded by lookup tables called Dimensions. Each Dimension table provides a reference to those things that you want to analyze by. A good book to understand how to design OLAP solutions is The Data Warehouse Toolkit: Practical Techniques for Building Dimensional Data Warehouses by Ralph Kimball.
Example: let's say we want to see some key measures about purchases. We want to know how many items and the sales amount that are purchased by what kind of customer across which stores. The FACT table will contain a column for Qty-purchased and Purchase Amount. The DIMENSION tables will include the ITEM_DESC (contains the item_id & Description), the CUSTOMER_TYPE, the STORE (Store_id & store name), and TIME (contains calendar information such as the date, the month_end_date, quarter_end_date, day_of_week, etc).
Database Fundamentals > Data Warehousing and Business Intelligence with Mike Lampa
Search Advice from more than 250 TechTarget Experts
Your question may have already been answered! Browse or search more than 25,000 question and answer pairs from more than 250 TechTarget industry experts.

Difference between BAPI and IDocs

hello all
what is difference between BAPI and IDocs

Hi,
BAPI
One of the big plusses for BAPIs is that the interface and function are not supposed to change. This is a big plus when you do upgrades or hot packs because the transaction can change (format, required inputs etc) which means you then need to update the call transaction.
Some of the BAPIs are better documented and easier to use than others. You usually need to perform the BAPI that actually does the COMMIT after you call your BAPI.
The Program coding for calling a BAPI is usually cleaner than setting up the screen flow etc for the Call Transaction.
You don't need to worry about special data circumstances interrupting the normal data flow of the screens and causing errors because of that.
BAPIs probably have better performance since they don't do the screen flow processing.
In general if the BAPI exists for the transaction you want to perform and you can figure out how to use it the BAPI is probably the best way to go.
BAPIs are a subset of the RFC-enabled function modules, especially designed as Application Programming Interface (API) to the SAP business object, or in other words: are function modules officially released by SAP to be called from external programs.
IDOC
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
The philosophical difference between EDI and ALE can be pinned as follows: If we send data to an external partner, we generally speak of EDI, while ALE is a mechanism to reliable replicate data between trusting systems to store a redundant copy of the IDoc data. The difference is made clear, when we think of a purchase order that is sent as an IDoc. If we send the purchase order to a supplier then the supplier will store the purchase order as a sales order. However, if we send the purchase order via ALE to another R/3 system, then the receiving system will store the purchase order also as a purchase order.
Regards,
Bhaskar

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

Differences between BDC and LSMW

Hello SAP Gurus,
Kindly let me know the various differences between BDC and LSMW.
Also, please tell me the STEPS of the CUT-OVER PLANNING (Shifting of Data from the Legacy System to the SAP System). Here, the "Data" means which data? Please explain in details.
Looking for your early feedback.
Regards,
Kaushik.

Hi,
BDC- It is Batch data communication. Its used for data conversion from legacy system to SAP system. Only technical people can do it. Tcode is SHDB.
LSMW- It is legacy system migration workbench. Its also used for data conversion from legacy system to SAP system. But it is role of functional consultant.
There are 14 steps in LSMW. As soon as you complete the one step, automatically it will go to next step.
In general you can use LSMW. But if you want to transfer more than 40,000 data, then it is not possible in LSMW. That time you can take help of BDC.
Cutover strategy depends upon how the organizations design their data load strategies. Normally, you decide the sequence of Data loads for Configuration settings, Master data, Transaction data which follows whom and then you make a copy of the system as a Production system a day before and after checking the successful data loads, you go-live 100% or partial again depending upon organizational setup and policies.
Cutover planning is highly site specific. There's no thumb rule. The stock data as on the date of going live should be correctly entered. But stock being a highly dynamic quantity, the strategy for loading should be crystal clear. Then you have to load all the back dated transaction on the stock. Some stock comes into your plant/storage location as return and some stock is actually delivered to your customer through sales orders of various kinds.
Please refer this link,
[PP Cut over activity|http://www.sap-img.com/production/pp-questions-answers.htm]
Regards,
R.Brahmankar

Difference between Technical and Business transaction archiving?

Hi Guys,
Can any one explain the difference between Technical and business transaction archiving with practical example?
When we will go for Technical archiving and when we will go for business transaction archiving?
Thanks,
Vinod.

Hello Vinod,
To me, Archiving Objects can be separated into 3 categories; Technical, Master Data and Transactional. Technical Archiving would include archive objects such as IDOC's, BC_SBAL (application logs), BDCLOGPROD (batch input logs), etc. Master Data Archive Objects would include MM_MATNR (material master), FI_ACCPAYB (vendor master data), FI_ACCRECV (customer master data), etc. And, Transactional Archive Objects would include FI_DOCUMNT (financial documents), SD_VBAK (sales orders), MM_EKKO (purchase orders), etc.
Techincal Archive Objects usually are easier to implement and require less resources. Master Data and Transactional Archive Objects usually take longer to implement as they will require business testing and sign-off.
This is a high-level explanation and I hope it helps answer your questions.
Best Regards,
Karin Tillotson

DIFFERENCE BETWEEN TECO AND CLOSED

What is the difference between teco and closed?

Dear Debasish,
check this.
For TECO Status:
The following actions are executed if an order is set to Technically complete.
The order is not relevant for MRP planning
Reservations are deleted
Capacity requirements are deleted
Purchase requisitions for external operations or non-stock materials are deleted
The order and its operations receive the system status Technically Completed (TECO)
If an order is technically complete, you cannot change it. The fields in the order
are displayed but cannot be changed. You can however cancel technical
completion, for instance if order data has to be changed.
For Closed Status:
The Closed (CLSD) status has been introduced in the production order. It has the following characteristics:
No more costs can be posted to the order, that is, confirmations and goods movements are no longer permitted for the order.
The order can no longer be changed. Exceptions to this are revoking the CLSD status and setting the deletion flag.
All actions relating to the status technically completed (TECO) are executed.
In a collective order, the CLSD status is also set for subordinate orders.
If the system comes across an order in the collective order that cannot be closed, the orders that come between this order and the leading order are also not closed. Other subtrees are closed if they only contain orders that can be closed.
Check this links for further understanding
<a href="http://help.sap.com/saphelp_erp2005/helpdata/en/a5/63198843a211d189410000e829fbbd/frameset.htm">closed status</a>
<a href="http://help.sap.com/saphelp_erp2005/helpdata/en/a5/63198843a211d189410000e829fbbd/frameset.htm">TECO</a>
Regards
Mangal

Sales order - difference between Cancel and Close?

Similar Messages

Maybe you are looking for