Difference between GL and AA. Error MQ555 in ABST2

Hi,
My client has put an asset in service in 2009 (fiscal year 2010) with a value of 70,000 EUR. In 2010 (fiscal year 2011) my client has retired 20,000 EUR worth of it (Transaction ABAON). This amount is not showing in the asset values and the depreciation was not adjusted for that. We are currently is fiscal year 2012 and it is now that we have discovered that we have the difference been FI and AA. I believe that we will have to re-open the financial period and redo all the end of year activity. However my problem is how to get the retirement to be shown in the asset values table? Thank you for your help?

Hi,
please see the following block (point 8).
/people/javier.reviriego/blog/2008/07/09/year-end-closing-in-asset-accounting-best-practices
regards Bernhard

Similar Messages

ABST2 - Differences between Assets and G/L accts

Hi Experts
We are working on ECC 6.0 and INR is our local currency.
At the end of FY 2007 by mistake direct postings were made to Dep Fund Account which is a Recon a/c and FY 2007 was closed
And because of which FI-GL and FI-AA doesnt match by INR 37353.71 (amt posted in above doc) as shown in ABST2
I've referred SAP notes 104567 & 69225 and found the note 69225 relevant to follow as the difference has not resulted in the current or open years.
So we have passed direct entry which is exactly the reversal of entry posted above using ABF1 (INR -37353.71)
After posting the 2nd document, in ABST2 another line has appeared of INR -37353.71. Although the sum for my recon GL is now zero.
The output of ABST2 is as below now -
Sc Acct no.   BusA Year SG 1st local difference LCurr Doc.no.    Period
AS 31100                2009               37,353.71-        INR     W004
AS 31100                2009               37,353.71         INR     W004       999
When I come out of ABST2 , addition to 1st, error no 2 is also coming which I thought would disappear.
1.Differences between assets and G/L accts in the balance carried forward
     Message no. MQ555
2.Differences between assets and G/L accounts at the key date
     Message no. MQ557
Is still something else needs to be done?
Or can I move ahead as the summation of the difference is now zero?
Please suggest.
Kapil

We referred to SAP and they suggeted that the tagging of W004 in both the lines means that now there is no error even system prompts it as error.
So we continued with the transactions and after closing the FY 2009, today when we run ABST2, we dont get any error messages as there is no difference left between Assets & GL.

What is the difference between #variable_name and :variable_name?

Hi!
What is the difference between #variable_name and :variable_name?
I have found that if we use alphanumeric variable then :variable_name return value in quotes but #variable_name without quotes.
Why it does not work in the same way for variable default values when variable is used in filter? (It works in mapping)
I use variable in filter like T.OUT_DATE>convert(datetime,:LAST_UPDATE_DATE,121)
When I use my variable in package and do refresh it works fine. But when I try to execute the same interface with variable default value I get error. Seems that variable name has been not changed to the value. It does not work with default value in quotes neither without quotes.
Any ideas how to solve that?
Thank you in advance!
Edited by: user13278245 on Sep 15, 2010 4:34 AM

Question is how to make it work with default value, when I execute interface standalone, not in package? And why it works in mapping but not in filter?
+ I have found that it works if source is Oracle. It doesn't work only for MS SQL source.
Edited by: user13278245 on Sep 15, 2010 6:43 AM

Difference between void and null?

wht is da difference between void and null w.r.t java?

corlettk wrote:
Why do you care, unless you're implementing a java compiler or JVM?Wow, you sure do suck at helping out in a forum. Why even make this post? You're not helping the OP any, and you made yourself look like a tool.
To the op:
Null is java's version of a null value. Java's version is more strict then many other languages, and will not work in a boolean expression or anywhere code expects a real and not null value. It's simply null.
Void is java's way of declaring no return type on a method. Methods that are void take no 'return' statement and if one is provided will cause a fatal error. The exception to this is using 'return' without a value, which returns control to the caller of the method.
Observe:
//this method returns an int
public int return_int(){
    int value = 5;
    return value;
//this method does not return an int
public void return_nothing(){
    int another_value = 123;
    System.out.println("Here's the value: " + return_int());
//this method does not return anything
public void nothing_returned(){
    return_nothing();
    return;
    System.out.println("This line never gets printed; the method returned control already!");
}

What is the difference between "= NULL" and "IS NULL" in SQL?

Hi,
I believe there is a difference between "= NULL" and "IS NULL" comparsion, but I couldn't find it. Anyone knows the difference?
Thanks,
Denny

Aha, thanks:
SQL> create table william_test_tab (col binary_double);
Table created.
SQL> insert into william_test_tab
2 select rownum / (rownum - 1) from user_tables where rownum < 4;
select rownum / (rownum - 1) from user_tables where rownum < 4
ERROR at line 2:
ORA-01476: divisor is equal to zero
SQL> insert into william_test_tab
2 select 1d * rownum / (rownum - 1) from user_tables where rownum < 4;
3 rows created.
SQL> select * from william_test_tab;
       COL
       Inf
2.0E+000
1.5E+000
3 rows selected.
SQL> select * from william_test_tab where col is infinite;
       COL
       Inf
1 row selected.
SQL>

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

What is the difference between ojvm and client versions?

Changing the java vm from client to ojvm result in the following error:
Errormessage:
java.lang.UnsatisfiedLinkError: no UniqueC in java.library.path
Project Settings -> Configurations -> Development -> Runner -> Virtual Machine -> ojvm FAILS
Project Settings -> Configurations -> Development -> Runner -> Virtual Machine -> ojvm      RUNS OK.
Project Settings -> Configurations -> Development ->Paths ->Additional Classpath:
C:\jars\xerces.jar;C:\jars\UniqueC.dll;C:\jars\log4j-1.2.8.jar
What is the difference between ojvm and client versions? How can I make ojvm to find UniqueC.dll?
Various version info:
Output from program:
java version:1.4.2_01
java home:C:\programfiler\JAVA\2sdk1.4.2_01\jre
java vm version:9.0.3.738 cdov
Taken from JDeveloper Help About:
Oracle IDE     9.0.3.10.35
UML Modelers Version     9.0.3.9.4
Business Components Version     9.0.3.10.7
java.version     1.3.1_02
java.vm.name     OJVM Client VM
java.vm.version     9.0.3.738 o

However, Adobe offers extra paid services to create PDF or to export PDF to other formats. You are not required to buy them, however.

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

Difference Between BAPI and RFM

Dear Friends,
I have seen a few thread explaining the difference between BAPI and RFM(Remote-enabled function Modules) from functional point of view. I know that there are cases when both are available in BOR. Both can be implement using Object Oriented Technology.
Can any tell me how they differ from techincal point of view ? OR Are they same techinically ?
Thanks in advance,
Rajesh

hi,
Remote Function Call:
RFC is an SAP interface protocol.
Based on CPI-C, it considerably simplifies the programming of communication processes between systems.
RFCs enable you to call and execute predefined functions in a remote system - or even in the same system.
RFCs manage the communication process, parameter transfer and error handling.
http://help.sap.com/saphelp_47x200/helpdata/en/22/042860488911d189490000e829fbbd/frameset.htm.
BAPI
BAPI stands for Business API(Application Program Interface).
A BAPI is remotely enabled function module
ie it can be invoked from remote programs like standalone JAVA programs, web interface etc..
You can make your function module remotely enabled in attributes of Function module but
A BAPI are standard SAP function modules provided by SAP for remote access.
Also they are part of Businees Objest Repository(BOR).
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.
Regards
Reshma

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 SLIN and Code Inspector

Hi,
Can anyone tell me the differences between SLIN and Code Inspector(SCI)..?
and in which cases we use SLIN and SCI..?
and as an ABAPer, which one should we prefer..?
Thanks,
Pradeep.

Hi
Extended syntax check or SLIN is used to check the program in all aspects for the different syntaxes like
When you use select single whether you have passed all the key fields or not>
whether you have maintained the text elements texts or not,
Have you used UNIT...CURRENCY along with the QTY and AMOUNT fields when displayed using the WRITE statement
and check for all the varities of statements used in the code, and if there is some problem with that statement/command, it will display as error or warning.
Check following links -
slin
can any one tell me abt SLIN T-CODE
Reward points if useful
Regards
Anji

Differences between trigger and Integrity Constraints

waht are the differences between trigger and Integrity Constraints

waht are the differences between trigger and Integrity ConstraintsConstraints are to be preferred:
"Declarative Ease
Define integrity constraints using SQL statements. When you define or alter a table, no additional programming is required. The SQL statements are easy to write and eliminate programming errors. Oracle controls their functionality. For these reasons, declarative integrity constraints are preferable to application code and database triggers. The declarative approach is also better than using stored procedures, because the stored procedure solution to data integrity controls data access, but integrity constraints do not eliminate the flexibility of ad hoc data access.
Centralized Rules
Integrity constraints are defined for tables (not an application) and are stored in the data dictionary. Any data entered by any application must adhere to the same integrity constraints associated with the table. By moving business rules from application code to centralized integrity constraints, the tables of a database are guaranteed to contain valid data, no matter which database application manipulates the information. Stored procedures cannot provide the same advantage of centralized rules stored with a table. Database triggers can provide this benefit, but the complexity of implementation is far greater than the declarative approach used for integrity constraints."
More:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14220/data_int.htm#sthref2976

Differences between assets and G/L accts

Differences between assets and G/L accts in the balance carried forward
Message no. MQ 555
Diagnosis
Differences occurred in the balance carried forward when comparing asset summary records and G/L accounts.
Procedure
Using program RFEWSBAL, select the accounts for which differences occurred. To do this, proceed as follows:
1. Changeover package: Active package
Phase: ANALYZE
Origin of change: AS
Proceed
1. Analyze the accounts containing errors using note 104567.
If the document number field contains the entry "W004", this means that although a difference exists in the balance carried forward, this difference was charged off at the key date. Following local currency changeover, the system adjusts the currency differences at the key date only, but not in the balance carried forward.
If the entry "W004" exists for all affected accounts, the status is set to warning instead of error. If the correction at key date described above proves sufficient, you can continue changing over the local currency without additional adjustments in the previous year.
However, SAP does recommend that you make corrections in the previous year in line with note 104567 since this ensures that the balance carried forward is also reconciled.

Hello,
There 2 t codes ABST and ABST2.
You have issue if ABST does not match.
ABST2 is as of today t code. Ideally they will match.
To fix the issue
execute AFAR
then execute AFAB repeat run dep.
Normally your will asset balance will match with GL

What is the difference between rfc and idoc

hi,
My name is rambabu.can anyone of u please tell me the main differences between idoc and rfc??
Thanks in Advance

hi Ramesh,
Remote Function Calls (RFC) and data exchange through IDoc
message documents. RFC makes direct and synchronous calls of a program in
the remote system. If the caller is an external program it will call an
RFC-enabled function in R/3 and if the calling program is the R/3 system
it will call an RFC-function in another R/3-system or it will call a
non-R/3 program through a gateway-proxy (usually rfcexec.exe). 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.
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.
Regards
Sreeram.G.Reddy

Difference between Macros and subroutine

Hi all,
What is the difference between the macros subroutine and function module functinalitywise.;

Hi,
Macros can only be used in the program the are defined in and only after the definition.
Macros can take max 9 parameters.
Macros are expanded at compilation / generation.
Subroutines (FORM) can be called from both the program the are defined in and other programs ('perform
' of 'perform in program ').
Subroutines can take any amount of parameters.
Subroutines are 'expanded' at runtime.
Functions are just like FORMs, but are intended to be called external.
Some differences between FUNCTIONs and FORMs:
The name of a FORM must be unique within the program (two programs can have different FORMs with the same name). A FORM is intended to be called internal (from within the program, however by a 'trick' you can call them external).
The name of a FUNCTION has to be unique throughout the system. A FUNCTION is intended to be called external (and is thus shared by 'many' programs).
The latter is more important for programmers and maintenance. Since a FUNCTION is called external, it is important to keep the interface (parameters) the same. The interface of a FORM (which is intended to be called internal) is check when debugging a program (but it is only checked within the program that is debugged). So if the interface of a FORM is changed, but the call to the FORM (perform ) is not, the debugger will notice this and issue an error message.
In general:
A MACRO is more or less an abbreviation for some lines of code that are used more than once or twice.
A FORM is a local subroutine (which can be called external).
A FUNCTION is (more or less) a subroutine that is called external.
Since debugging a MACRO is not really possible, prevent the use of them (I've never used them, but seen them in action). If the subroutine is used only local (called internal) use a FORM. If the subroutine is called external (used by more than one program) use a FUNCTION.
--Excerpt from http://sap.ittoolbox.com/documents/popular-q-and-a/macro-vs-subroutine-1594#
DATA p_c(10).
FIELD-SYMBOLS: <fs> TYPE ANY.
DATA p_old1 TYPE i VALUE 10.
DATA p_old2 TYPE i VALUE 11.
DATA p_old3 TYPE i VALUE 12.
DATA p_old4 TYPE i VALUE 13.
DATA p_old5 TYPE i VALUE 14.
DATA p_old6 TYPE i VALUE 15.
DATA p_old7 TYPE i VALUE 16.
DATA p_old8 TYPE i VALUE 17.
DATA p_old9 TYPE i VALUE 18.
DATA p_old10 TYPE i VALUE 19.
DATA p_old11 TYPE i VALUE 21.
DATA p_old12 TYPE i VALUE 22.
DATA p_old13 TYPE i VALUE 23.
DATA p_old14 TYPE i VALUE 24.
DEFINE ADD_MAPPING.
p_c = &1.
CONDENSE p_c.
CONCATENATE 'p_old' p_c INTO p_c.
ASSIGN (p_c) TO <fs>.
WRITE <fs>.
END-OF-DEFINITION.
DO 14 TIMES.
ADD_MAPPING sy-index.
ENDDO.
http://sap.ittoolbox.com/documents/popular-q-and-a/macro-vs-subroutine-1594
http://help.sap.com/saphelp_nw2004s/helpdata/en/9f/db972835c111d1829f0000e829fbfe/frameset.htm
Regards,
Priyanka.

Difference between GL and AA. Error MQ555 in ABST2

Similar Messages

Maybe you are looking for