Integration of ABAP and SD?

The integration points b/w SD module and ABAP?
(also specify the underlying databse table names and fields with detail)

Hi,
Kindly go through the following link for SAP SD tables:
http://www.erpgenie.com/abap/tables_sd.htm
<b>Important SAP SD Tables:</b>
http://www.sap-img.com/sap-sd/important-tables-for-sap-sd.htm
best regards,
Thangesh

Similar Messages

ABAP and Java Stack: Which to choose/supported standards and components?

Hello,
I am trying to understand the role of the two stacks in NW. Maybe anyone has a few
hints where I can find answers to the following questions:
- An overview of supported Standards (Java 5 since when?)
- An overview of which component runs on which stack? Portal->Java, Integration Server->ABAP and so on.
- Guidelines when to install both stacks and when to use just one stack? When do I use which one?
- Has SAP an stategy towards an one Stack solution (possibly Java?)
Best regards and thanks for any pointers!
Stefan

An overview of supported Standards (Java 5 since when?)
Go to service.sap.com/pam
Product Availability Matrix will tell you about supported version and platforms.
An overview of which component runs on which stack? Portal->Java, Integration Server->ABAP and so on.
Usually the question goes the other direction: what stacks we need for implementation of a particular function?
More and more products require ABAP backend and Java frontend.
For example Employee Self Service has been transerred from ABAP only ITS based to ABAP backend and Java frontend.
Same with SRM.
Guidelines when to install both stacks and when to use just one stack? When do I use which one?
Same as above, driven by business requirements, not technology.
Has SAP an stategy towards an one Stack solution (possibly Java?)
No. Core business functions are still being developed on ABAP and interface, GUI etc utilize JAVA.
Regards,
Slava

ABAP AND DATABASES

Hi Experts..
I would like to know how to create a databases in SQL and have access from ABAP.. to Modify, Consult and do the basic operations like insert information, drop and modify in the respective tables.
I'm ussing MiniSap Minigui 6.2 on Windows XP and the BCUSER
Thank you very much for your help
REGARDS

HI Araceli,
Database Access using Advanced Business Application Programming (ABAP)
Basics :
Accessing the Database in the R/3 System is performed through the interface provided by the SAP System, which in the SAP System is referred to as the Database Interface. A user can access the database from his/her program through Open SQL and Native SQL depending upon the circumstances.
About SQL
The Structured Query Language (SQL) is a largely standardized language, which is used for accessing relational databases. It can be divided as follows:
Data Manipulation Language (DML)
These statements are for reading and changing data in database tables.
Data Definition Language (DDL)
These statements are for creating and administering database tables.
Data Control Language (DCL)
These statements are used for authorization and consistency checks.
So each database has a programming interface. This programming interface allows the user to access the database tables by using SQL statements. But, these SQL statements in the programming interfaces are not fully standardized. So, you must refer to the documentation of that system for a list of the SQL statements available and also their correct syntax in order to access a specific database system.
Interface thru data base
Each work process on an application server must have a database interface if you want to make the R/3 system independent of the database system, and also to use it correctly despite the differences in the SQL syntax between various databases. By means of this interface only, the R/3 system can communicate with the database. All of the database requests from the R/3 system are converted into the correct Standard SQL statements for the database system by the database interface. In order to perform this function, it has to use a database-specific component, which shields the differences between database systems from the rest of the database interface. You have to choose the appropriate layer when installing the R/3 system. A user can access a database from a program through Open SQL and Native SQL.
Open SQL
Open SQL are statements that make up a subset of Standard SQL which is fully integrated in ABAP. Open SQL consists of Data Manipulation Language (DML) which is a part of Standard SQL.
One of the ways to access the database from a program is Open SQL. These Open SQL statements are nothing but a subset of Standard SQL, which is fully integrated in ABAP. Irrespective of which database system the R/3 installation is using, they allow you to access data. When I said that, Open SQL consists of the Data Manipulation Language (DML). I meant that it allows you to read (i.e. to SELECT) and change (For example to INSERT, UPDATE, DELETE) data.
Moreover, Open SQL also goes beyond Standard SQL. This is to provide statements that can simplify or speed up database access in conjunction with other ABAP constructions. Apart from that, it also gives you the freedom to buffer certain tables on the application server, thereby enabling you to save excessive database access. In this case, the database interface is responsible for comparing the buffer with the database. As far as buffer storage is concerned, they may be stored in two parts: the working memory of the current work process, and the shared memory for all work processes on an application server. The data in the various buffers is synchronized at set intervals by buffer management where an R/3 system is distributed across more than one application server. It should be noted that data in the buffer is not always up to date when you are buffering the database. That is why you should only use the buffer for data which does not change often. You can specify whether a table can be buffered in its definition in the ABAP Dictionary.
Open SQL consists of a set of ABAP statements. These statements perform operations on the central database in the R/3 system. The results of the operations and any error messages which come out of it are independent of the current database system. Thus, uniform syntax and semantics for all of the database systems supported by SAP is provided by Open SQL. Regardless of the current database system, the ABAP programs, which use Open SQL statements only, will work in any R/3 system. Moreover, Open SQL statements work only with database tables that have been created in the ABAP Dictionary.
You have the freedom to combine columns belonging to different database tables to a database view (or view for short) in the ABAP Dictionary. Views are also handled in exactly the same way as database tables in Open SQL statements.
Some Open SQL keywords are as follows:
SELECT - It reads data from database tables.
INSERT - It adds rows to database tables.
UPDATE - It changes the contents of rows of database tables.
MODIFY - It inserts rows into database tables or changes the content of existing rows.
DELETE - It deletes rows from database tables.
OPEN CURSOR, FETCH, CLOSE CURSOR - It reads rows of database tables using the cursor.
Return Codes
The following two system fields are filled with return codes by all Open SQL statements:
SY-SUBRC: The system field SY -SUBRC contains the value 0 after every Open SQL statement if the operation was successful. When a value is other than 0, then it is unsuccessful.
SY-DBCNT: The system field SY-DBCNT contains the number of database lines processed after an open SQL statement.
Native SQL
The other possible way to access the database from a program is Native SQL. It is only loosely integrated into ABAP. It allows access to all of the functions contained in the programming interface of the respective database system. Native SQL statements are not checked and converted as compared to Open SQL statements. Unlike Open SQL, these are sent directly to the database system. The function of the database-dependent layer remains minimal when you use Native SQL. The Programs which use Native SQL are written specifically for a database system. You should avoid using Native SQL wherever possible when writing R/3 applications. However, you can use it in some parts of the R/3 Basis System, for instance, for creating or changing table definitions in the ABAP Dictionary.
Regardless of the database platform that your R/3 system is using, Open SQL allows you to access database tables, which are declared in the ABAP Dictionary. Native SQL allows you to use database specific SQL statements in an ABAP program. This means that you can use database tables that are not administered by the ABAP Dictionary. Aside from that, you can also integrate data that is not part of the R/3 system.
As a rule, an ABAP program that contains database-specific SQL statements will not run under different database systems. You have to use Open SQL statements only, if your program is used on more than one database platform.
You must proceed with the EXEC SQL statement, and follow the ENDEXEC statement to use a: Native SQL statement. For example
Listing 1
EXEC SQL [PERFORMING
ENDEXEC.There is no period after Native SQL statements. Also, using quotation marks (") or an asterisk (*) at the beginning of a native SQL statement's line does not introduce a comment as it would in normal ABAP syntax. You need to know if the table and field names are case-sensitive in your chosen database.
The data is transported between the database table and the ABAP program using host variables in Native SQL statements. These are preceded in a Native SQL statement by a colon ( and are declared in the ABAP program. The elementary structures can be used as host variables. The structures of an INTO clause are treated exceptionally, as though all of their fields are listed individually. If the selection in a Native SQL SELECT statement is a table, then you can pass it to ABAP line by line using the PERFORMING addition. For each line read, the program calls a subroutine
. Further, you can process the data within the subroutine.
After the ENDEXEC statement, SY-DBCNT contains the number of lines processed as it does in Open SQL. In almost all cases, SY-SUBRC contains the value a after the ENDEXEC statement. Cursor operations form an exception: after FETCH, SY-SUBRC is 4 if no more records could be read. This is also applied when you read a result set using EXEC SQL PERFORMING.
Native SQL Scope
Native SQL is very important as it allows you to execute nearly all available statements through the SQL programming interface (usually known as SQL Call Interface or similar) for directly executing SQL program code (using EXEC IMMEDIATE or a similar command). The statements that are not supported are listed in the following section:
·         Native SQL and the Database Interface,
·         Native SQL and Transactions
·         Native SQL and the Database Interface
Native SQL statements bypass the R/3 database interface. With the database buffer on the application server, there is no table logging, and no synchronization. Therefore, you should use Open SQL to change database tables declare in the ABAP dictionary wherever possible. Since the columns contain extra database specific length information for the column tables declared in the ABAP dictionary, containing long columns with the type LCHAR or LRAW should only be addressed using Open SQL. Native SQL may not produce the correct result, as it does not take this information into account. Native SQL does not support automatic client handling. Instead, you must treat a client field like any other field
Native SQL and Transactions
One should not use any transaction control statement such as COMMIT, ROLLBACK WORK, or any statements that set transaction parameters using Native SQL to ensure that transaction in the R/3 System are consistent.
ABAP Dictionary
The ABAP Dictionary is nothing but a part of the ABAP Workbench. It allows you to create and administer database tables. There are no statements from the DDL part of Standard SQL in Open SQL. It should be noted that normal application programs should not create or change their own database tables.
To create and change database tables, the ABAP Dictionary has to use the DDL part of Open SQL. Besides this, it also administers the ABAP Dictionary in the database. In addition, the ABAP Dictionary contains meta-descriptions of all database tables in the R/3 system. Here, only database tables appears in the Dictionary, which you have created using the ABAP Dictionary. Open SQL statements can only access tables, which exists in the ABAP Dictionary.
Authorization and Consistency Checks
With regard to authorization and consistency checks, the DCL part of Standard SQL is not used in R/3 programs. Whereas, the work processes which are within the R/3 system are logged into the database system as users with full rights. By using the R/3 authorization concept, the authorizations of programs or users to read or change database tables is administered within the R/3 system. In addition, transactions must equally ensure their own data consistency using the R/3 locking concept.
The R/3 lock concept allows you to monitor your system with regards to lock logics. The R/3 lock concept works closely together with the R/3 updates.
As an example, say that a travel agent wants to book a flight for a customer who wants to fly to a particular city with a certain airline on a certain day. If there are still available seats on the flight, then the booking will be possible, otherwise it will lead to overbooking. Hence, the database entry corresponding to the flight must be locked against access from other transactions to avoid the possibility of overbooking. This is because two agents might both be doing this same thing at the same time, and we need to make sure that we don't overbook.
Lock Mechanisms
When the database system receives change statements (INSERT, UPDATE, MODIFY, DELETE) from a program, it automatically sets database locks. Database locks are locks on the database entries affected by statements to prevent problems. Since the lock mechanism uses a, lock flag in the entry, you can only set a lock for an existing database entry. After each database commit, these flags are automatically deleted. This means that database locks can never be set for longer than a single database LUW, a single dialog step in an R/3 application program.
Therefore, physical locks in the database system are insufficient for the requirements of an R/3 transaction. Locks in the R/3 system must remain set for the duration of a whole SAP LUW, that is, over several dialog steps. They must also be capable of being handled by different work processes and application servers. As a result, each lock must apply on all servers in that R/3 system.
Database Accesses of the NetWeaver AS ABAP
The NetWeaver AS ABAP stores long-term data in a central relational database table. In a relational database model, the real world is represented by tables. A table is a two-dimensional matrix, consisting of lines and columns (fields). The smallest possible combination of fields that can uniquely identify each line of the table is called the key. Each table must have at least one key, and each table has one key that is defined as its primary key. Relationships between tables are represented by foreign keys.
Standard SQL
SQL (Structured Query Language) is a largely standardized language for accessing relational databases. It can be divided into three areas:
·        Data Manipulation Language (DML)
Statements for reading and changing data in database tables.
·        Data Definition Language (DDL)
Statements for creating and administering database tables.
·        Data Control Language (DCL)
Statements for authorization and consistency checks.
Each database has a programming interface that allows you to access the database tables using SQL statements. The SQL statements in these programming interfaces are not fully standardized. To access a specific database system, you must refer to the documentation of that system for a list of the SQL statements available and their correct syntax.
The Database Interface
To avoid incompatible situations between different database tables and to make the NetWeaver AS ABAP system independent of the database system in use, each work process on an ABAP application server contains a database interface. The NW AS communicates with the database solely through the database interface. The database interface converts all of the database requests from the NW AS into the correct Standard SQL statements for the database system in use. To do this, it uses a database-specific component that shields the differences between database systems from the rest of the database interface. You choose the this component when you install NetWeaver AS ABAP in accordance with the database in use.
ABAP programs have two options for accessing the database interface: Open SQL and Native SQL.
Open SQL
Open SQL statements are a fully integrated subset of Standard SQL within ABAP. They enable the ABAP programs to access data irrespective of the database system installed. Open SQL consists of the Data Manipulation Language (DML) part of Standard SQL; in other words, it allows you to read (SELECT) and change (INSERT, UPDATE, DELETE) data.
Open SQL also goes beyond Standard SQL to provide statements that, in conjunction with other ABAP constructions, can simplify or speed up database access. It also allows you to buffer certain tables on the application server, saving excessive database access. In this case, the database interface is responsible for comparing the buffer with the database. Buffers are partly stored in the working memory of the current work process, and partly in the shared memory for all work processes on an application server. In SAP systems that are distributed across more than one application server, the data in the various buffers is synchronized at set intervals by buffer management. When buffering the database, you must remember that data in the buffer is not always up to date. For this reason, you should only use the buffer for data which does not often change. You specify whether a table can be buffered in its definition in the ABAP Dictionary.
Native SQL
Native SQL is only loosely integrated into ABAP, and allows access to all of the functions contained in the programming interface of the respective database system. Unlike Open SQL statements, Native SQL statements are not checked and converted, but instead are sent directly to the database system. When you use Native SQL, the function of the database-dependent layer is minimal. Programs that use Native SQL are specific to the database system for which they were written. When developing generally valid ABAP applications, you should as far as possible avoid using Native SQL. In some components of the SAP System, Native SQL is used for example, in the ABAP Dictionary for creating or changing tables.
The ABAP Dictionary
The ABAP Dictionary, part of the ABAP Workbench, allows you to create and administer database tables. Open SQL contains no statements from the DDL part of Standard SQL. Normal application programs should not create or change their own database tables.
The ABAP Dictionary uses the DDL part of Open SQL to create and change database tables. It also administers the ABAP Dictionary in the database. The ABAP Dictionary contains meta descriptions of all database tables in the NetWeaver AS ABAP system. Only database tables that you create using the ABAP Dictionary appear in the Dictionary. Open SQL statements can only access tables that exist in the ABAP Dictionary.
Authorization and Consistency Checks
The DCL part of Standard SQL is not important in ABAP programs. The work processes within the ABAP application server are logged on to the database system as users with full authorization. The authorizations of programs or program users to read or change database tables is managed by the authorization concept. Equally, transactions must ensure their own data consistency in the database using the SAP locking concept. For more information, refer to the chapter Data Consistency.
Work Processes
Work processes execute the individual dialog steps of ABAP application programs. They are components of ABAP application servers. The next two sections describe firstly the structure of a work process, and secondly the different types of work process in NetWeaver AS ABAP.
Structure of a Work Process
The following diagram shows the components of a work process:
Screen Processor
In ABAP application programming, there is a difference between user interaction and processing logic. From a programming point of view, user interaction is controlled by screens. As well as the actual input mask, a screen also consists of flow logic, which controls a large part of the user interaction. NetWeaver AS ABAP contains a special language for programming screen flow logic. The screen processor executes the screen flow logic. Via the dispatcher, it takes over the responsibility for communication between the work process and the SAPgui, calls modules in the flow logic, and ensures that the field contents are transferred from the screen to the flow logic.
ABAP Processor
The actual processing logic of an application program is written in ABAP - SAPs own programming language. The ABAP processor executes the processing logic of the application program, and communicates with the database interface. The screen processor tells the ABAP processor which module of the screen flow logic should be processed next. The following screen illustrates the interaction between the screen and the ABAP processors when an application program is running.
Database Interface
The database interface provides the following services:
·        Establishing and terminating connections between the work process and the database.
·        Access to database tables
·        Access to Repository objects (ABAP programs, screens and so on)
·        Access to catalog information (ABAP Dictionary)
·        Controlling transactions (commit and rollback handling)
·        Table buffer administration on the ABAP application server.
The following diagram shows the individual components of the database interface:
The diagram shows that there are two different ways of accessing databases: Open SQL and Native SQL.
Open SQL statements are a subset of Standard SQL that is fully integrated in ABAP. They allow you to access data irrespective of the database system that your installation is using. Open SQL consists of the Data Manipulation Language (DML) part of Standard SQL; in other words, it allows you to read (SELECT) and change (INSERT, UPDATE, DELETE) data. The tasks of the Data Definition Language (DDL) and Data Control Language (DCL) parts of Standard SQL are performed in NetWeaver AS ABAP by the ABAP Dictionary and the authorization system. These provide a unified range of functions, irrespective of database, and also contain functions beyond those offered by the various database systems.
Open SQL also goes beyond Standard SQL to provide statements that, in conjunction with other ABAP constructions, can simplify or speed up database access. It also allows you to buffer certain tables on the ABAP application server, saving excessive database access. In this case, the database interface is responsible for comparing the buffer with the database. Buffers are partly stored in the working memory of the current work process, and partly in the shared memory for all work processes on an ABAP application server. Where NetWeaver AS ABAP is distributed across more than one ABAP application server, the data in the various buffers is synchronized at set intervals by the buffer management. When buffering the database, you must remember that data in the buffer is not always up to date. For this reason, you should only use the buffer for data which does not often change.
Native SQL is only loosely integrated into ABAP, and allows access to all of the functions contained in the programming interface of the respective database system. In Native SQL, you can primarily use database-specific SQL statements. The Native SQL interface sends them as is to the database system where they are executed. You can use the full SQL language scope of the respective database which makes all programs using Native SQL specific for the database system installed. In addition, there is a small set of SAP-specific Native SQL statements which are handled in a special way by the Native SQL interface. ABAP applications contain as little Native SQL as possible. In fact, it is only used in a few components (for example, to create or change table definitions in the ABAP Dictionary).
The database-dependent layer in the diagram serves to hide the differences between database systems from the rest of the database interface. You choose the appropriate layer when you install NetWeaver AS ABAP. Thanks to the standardization of SQL, the differences in the syntax of statements are very slight. However, the semantics and behavior of the statements have not been fully standardized, and the differences in these areas can be greater. When you use Native SQL, the function of the database-dependent layer is minimal.
Types of Work Process
Before you start NetWeaver AS ABAP, you determine how many work processes each ABAP application server will have, and what their types will be. Since all work processes have the same structure (see preceding section), the type of work process does not determine the technical attrributes of the ABAP application server but the type of tasks to be performed on it. The dispatcher starts the work processes and only assigns them tasks that correspond to their type. This means that you can distribute work process types to optimize the use of the resources on your ABAP application servers.
The following diagram shows again the structure of an ABAP application server, but this time, includes the various possible work process types:
Dialog Work Process
Dialog work processes deal with requests from an active user to execute dialog steps (see also Dialog Programming).
Update Work Process
Update work processes execute database update requests. Update requests are part of an SAP LUW that bundle the database operations resulting from the dialog in a database LUW for processing in the background.
Background Work Process
Background work processes process programs that can be executed without user interaction (background jobs).
Enqueue Work Process
The enqueue work process administers a lock table in the shared memory area. The lock table contains the logical database locks for NetWeaver AS ABAP and is an important part of the SAP LUW concept. In NW AS, you may only have one lock table. You may therefore also only have one ABAP application server with enqueue work processes. Normally, a single enqueue work process is sufficient to perform the required tasks.
Spool Work Process
The spool work process passes sequential datasets to a printer or to optical archiving. Each ABAP application server may contain only one spool work process.
Role of Work Processes
The types of its work processes determine the services that an ABAP application server offers. The application server may, of course, have more than one function. For example, it may be both a dialog server and the enqueue server, if it has several dialog work processes and an enqueue work process.
You can use the system administration functions to switch a work process between dialog and background modes while the system is still running. This allows you, for example, to switch an SAP System between day and night operation, where you have more dialog than background work processes during the day, and the other way around during the night.
thanks
karthik
reward me points if usefull

Information about Integration WebDynpro for ABAP and Business-Workflow

Hi Experts,
I'm looking for information about
Integration WebDynpro for ABAP and Business-Workflow
Link, documents and books are welcome!
Thanks
mishak

If you have worked on workflows earlier the procedure is very simple. You just need to enter certain parameter values of your application in SWFVISU for the respective task and re-register your system in UWL administration. Thats it! your webdynpro and workflows are integrated. For details on the parameters check the following link,
http://help.sap.com/saphelp_nw04/helpdata/en/19/bff5c18ba44da4a4ca68cf572dabda/frameset.htm
There are also a couple of blogs on "launching webdynpro from UWL" (Procedure for both Java and webdynpro is almost similar). You can also check these for more details.
Thanks,
Prasath N

How to check Integration Server Client and ABAP stack Client?

How to check Integration Server Client and ABAP stack Client? How to check,,pls tell in detailed steps???
Points would be awarded.
Arnab

hi,
Must be the server has different clients,one declared as application server ie abap stack client and the other declared as Integration server ie XI. U might be trying to open idx5 in application server client, in which idx5 exists but you cant open the screen even, that can be achieved through we02.
000 is the default client when XI server is installed .We can create separate clients on the system through sccl tcode.
As told we can find the client on sap logon screen.
Logon to sxmb_adm and check whether the client is declared as an application system(r/3) or Integration server(xi).Try idx5 in xi not r/3
Edited by: NagaDurga Nannapaneni on Aug 28, 2008 11:36 AM

ABAP and JAVA sync issue

Hello,
We are having MI 7.0 at SPS15.Am trying to apply add to our system(we created SDA file from NWA as an addon).SDA addon getting deployed but its not getting sync between ABAP and Java stack even if is run reload sever time from NWA->Administrator->Mobile Infrastructure->Mobile Components.I can see add-on when i check from SDM but it cannot see when i search under Mobile component in NWA.Application logs shows below error.
#703543993#/Applications                                                                                #sap.com/tcmobileadmin~ea#com.sap.ip.mi.ejb.mcd.MobileContainerBean.Method---:                                                                                Processfunction#J2EE_GUEST#0##n/a##8e6d577024d511e1a299001635730592#SAPEngine_Ap                                                                                plication_Thread[impl:3]_10##0#0#Error#1#com.sap.ip.mi.ejb.mcd.MobileContainerBe                                                                                an#Plain####
#1.#001635730592001800000015000030100004B3E6C1311ED1#1323703575929#/Applications                                                                                #sap.com/tcmobileadmin~ea#com.sap.ip.mi.ejb.mcd.MobileContainerBean.Method---:                                                                                Processfunction#J2EE_GUEST#0##n/a##a19424a024d511e18ede001635730592#SAPEngine_Ap                                                                                plication_Thread[impl:3]_9##0#0#Error#1#com.sap.ip.mi.ejb.mcd.MobileContainerBea                                                                                n#Plain####
#1.#001635730592000F00000016000030100004B3E6C662CEBE#1323703663073#/Applications                                                                                #sap.com/tcmobileadmin~ea#com.sap.ip.mi.ejb.mcd.MobileContainerBean.Method---:                                                                                Processfunction#J2EE_ADMIN#47##n/a##d588777024d511e1c64a001635730592#SAPEngine_A                                                                                pplication_Thread[impl:3]_18##0#0#Error#1#com.sap.ip.mi.ejb.mcd.MobileContainerB                                                                                ean#Plain####
#1.#001635730592002000000015000030100004B3E6CDC2D7E4#1323703786809#/Applications                                                                                #sap.com/tcmobileadmin~ea#com.sap.ip.mi.ejb.mcd.MobileContainerBean.Method---:                                                                                Processfunction#J2EE_GUEST#0##n/a##1f482a9024d611e18dc1001635730592#SAPEngine_Ap                                                                                plication_Thread[impl:3]_29##0#0#Error#1#com.sap.ip.mi.ejb.mcd.MobileContainerBe                                                                                an#Plain####
#1.#00163573059200260000000C000030100004B3E6D02A2DDA#1323703827137#/Applications                                                                                #sap.com/tcmobileadmin~ea#com.sap.ip.mi.ejb.mcd.MobileContainerBean.Method---:                                                                                Processfunction#J2EE_GUEST#0##n/a##37527e6024d611e1a43c001635730592#SAPEngine_Ap                                                                                plication_Thread[impl:3]_39##0#0#Error#1#com.sap.ip.mi.ejb.mcd.MobileContainerBe                                                                                an#Plain####
#1.#00163573059200350000000B000030100004B3E6D1150767#1323703842528#/Applications                                                                                #sap.com/tcwddispwda#com.sap.ip.mi.admin.wd.paramset.Details.Method-->wdDoModi                                                                                fyView()#J2EE_ADMIN#56##uwsvt729.merck.com_VZ1_12609950#J2EE_ADMIN#2e05832024d61                                                                                1e1b753001635730592#SAPEngine_Application_Thread[impl:3]_33##0#0#Error#1#com.sap                                                                                .ip.mi.admin.wd.paramset.Details#Plain###Specify all parameters#
#1.#00163573059200250000007C000030100004B3E6F8460AEE#1323704500063#/Applications                                                                                #sap.com/tcmobileadmin~ea#com.sap.ip.mi.ejb.mcd.MobileContainerBean.Method---:                                                                                Processfunction#J2EE_GUEST#0##n/a##c86ab33024d711e185b5001635730592#SAPEngine_Ap                                                                                plication_Thread[impl:3]_22##0#0#Error#1#com.sap.ip.mi.ejb.mcd.MobileContainerBe                                                                                an#Plain####
#1.#001635730592002F00000015000030100004B3E728C1AF02#1323705313486#/Applications                                                                                #sap.com/tcmobileadmin~ea#com.sap.ip.mi.ejb.mcd.MobileContainerBean.Method---:                                                                                Processfunction#J2EE_GUEST#0##n/a##ad1da59024d911e1a138001635730592#SAPEngine_Ap                                                                                plication_Thread[impl:3]_37##0#0#Error#1#com.sap.ip.mi.ejb.mcd.MobileContainerBe                                                                                an#Plain####
#1.#001635730592000F0000000000002A400004B3E754A629F8#1323706045836#/Applications                                                                                /CMS/PCS#sap.com/tcSLCMS~PCS#com.sap.cms.pcs.serverAPI.CmsOrganizerAdapter#J2E                                                                                E_GUEST#0##n/a##61feecc024db11e1b4cb001635730592#SAPEngine_Application_Thread[im                                                                                pl:3]_26##0#0#Info#1#com.sap.cms.pcs.serverAPI.CmsOrganizerAdapter#Plain###CMS o                                                                                rganizer proxy is waiting for requests#
#1.#001635730592000F0000000100002A400004B3E754A659EE#1323706045848#/Applications                                                                                /CMS/PCS#sap.com/tcSLCMS~PCS#com.sap.cms.pcs.serverAPI.CmsManagerAdapter#J2EE_                                                                                GUEST#0##n/a##61feecc024db11e1b4cb001635730592#SAPEngine_Application_Thread[impl                                                                                :3]_26##0#0#Info#1#com.sap.cms.pcs.serverAPI.CmsManagerAdapter#Plain###CMS manag                                                                                er proxy is waiting for requests#
#1.#001635730592000F0000000200002A400004B3E754A6715D#1323706045854#/Applications                                                                                /CMS/PCS#sap.com/tcSLCMS~PCS#com.sap.cms.pcs.transport.proxy.CmsLogViewer#J2EE                                                                                GUEST#0##n/a##61feecc024db11e1b4cb001635730592#SAPEngineApplication_Thread[imp                                                                                l:3]_26##0#0#Info#1#com.sap.cms.pcs.transport.proxy.CmsLogViewer#Plain###CMS Log                                                                                Viewer is waiting for requests#
#1.#001635730592000F0000000300002A400004B3E754A67B77#1323706045857#/Applications                                                                                /CMS#sap.com/tcSLCMS~PCS#com.sap.cms.recovery.RecoveryServlet#J2EE_GUEST#0##n/                                                                                a##61feecc024db11e1b4cb001635730592#SAPEngine_Application_Thread[impl:3]_26##0#0                                                                                #Info#1#com.sap.cms.recovery.RecoveryServlet#Plain###CMS recovery servlet is wai                                                                                ting for requests#
#1.#001635730592000F0000000400002A400004B3E754A67CE5#1323706045857#/Applications                                                                                /CMS#sap.com/tcSLCMS~PCS#com.sap.cms.recovery.RecoveryServlet#J2EE_GUEST#0##n/                                                                                a##61feecc024db11e1b4cb001635730592#SAPEngine_Application_Thread[impl:3]_26##0#0                                                                                #Info#1#com.sap.cms.recovery.RecoveryServlet#Plain###start recovery#
#1.#001635730592000F0000000500002A400004B3E754AA7F91#1323706046120#/Applications                                                                                /CMS#sap.com/tcSLCMS~PCS#com.sap.cms.recovery.pcs.QueueItemRecovery#J2EE_GUEST                                                                                #0#SAP J2EE Engine JTA Transaction : [0ffffffc069ffffff9e0008]#n/a##61feecc024db                                                                                11e1b4cb001635730592#SAPEngine_Application_Thread[impl:3]_26##0#0#Info#1#com.sap                                                                                .cms.recovery.pcs.QueueItemRecovery#Plain###CMS recovery found 0 QueueItem(s) wi                                                                                th state Import running in 0 queue(s). Start check if they are really running or                                                                                need recovery.#
#1.#001635730592000F0000000600002A400004B3E754AA8344#1323706046121#/Applications                                                                                /CMS#sap.com/tcSLCMS~PCS#com.sap.cms.recovery.pcs.QueueItemRecovery#J2EE_GUEST                                                                                #0#SAP J2EE Engine JTA Transaction : [0ffffffc069ffffff9e0008]#n/a##61feecc024db                                                                                11e1b4cb001635730592#SAPEngine_Application_Thread[impl:3]_26##0#0#Info#1#com.sap                                                                                .cms.recovery.pcs.QueueItemRecovery#Plain###Finished check and recovery for all                                                                                CMS QueueItems of state Import running. Checked Items: 0; Recovered Items: 0; Re                                                                                covery Failed Items: 0; Real running Items: 0#
#1.#001635730592000F0000000700002A400004B3E754AAACBA#1323706046132#/Applications                                                                                /CMS#sap.com/tcSLCMS~PCS#com.sap.cms.recovery.pcs.QueueItemRecovery#J2EE_GUEST                                                                                #0#SAP J2EE Engine JTA Transaction : [0ffffffc069ffffff9e0008]#n/a##61feecc024db                                                                                11e1b4cb001635730592#SAPEngine_Application_Thread[impl:3]_26##0#0#Info#1#com.sap                                                                                .cms.recovery.pcs.QueueItemRecovery#Plain###CMS recovery found 0 QueueItem(s) wi                                                                                th state Assembly running in 0 queue(s). Start check if they are really running                                                                                or need recovery.#
#1.#001635730592000F0000000800002A400004B3E754AAAEE5#1323706046132#/Applications                                                                                /CMS#sap.com/tcSLCMS~PCS#com.sap.cms.recovery.pcs.QueueItemRecovery#J2EE_GUEST                                                                                #0#SAP J2EE Engine JTA Transaction : [0ffffffc069ffffff9e0008]#n/a##61feecc024db                                                                                11e1b4cb001635730592#SAPEngine_Application_Thread[impl:3]_26##0#0#Info#1#com.sap                                                                                .cms.recovery.pcs.QueueItemRecovery#Plain###Finished check and recovery for all                                                                                CMS QueueItems of state Assembly running. Checked Items: 0; Recovered Items: 0;                                                                                Recovery Failed Items: 0; Real running Items: 0#
#1.#001635730592000F0000000900002A400004B3E754AAB68F#1323706046134#/Applications                                                                                /CMS#sap.com/tcSLCMS~PCS#com.sap.cms.recovery.RecoveryServlet#J2EE_GUEST#0##n/                                                                                a##61feecc024db11e1b4cb001635730592#SAPEngine_Application_Thread[impl:3]_26##0#0                                                                                #Info#1#com.sap.cms.recovery.RecoveryServlet#Plain###finished recovery#
#1.#00163573059200140000000300002A400004B3E7AA40154F#1323707482010#/Applications                                                                                #sap.com/tcmobileadmin~ea#com.sap.ip.mi.ejb.mcd.MobileContainerBean.Method---:                                                                                Processfunction#J2EE_GUEST#0##n/a##b9c439d024de11e1a4ee001635730592#SAPEngine_Ap                                                                                plication_Thread[impl:3]_10##0#0#Error#1#com.sap.ip.mi.ejb.mcd.MobileContainerBe                                                                                an#Plain####
Thanks

Hi,
Tha ABAP stack consists of the Integration Server which in turn contains your Integration Engine and Business Process Engine.
The J2EE stack contains the Adapter Engine and your IR and ID run on the J2EE engine.
Ever wondered how and where the XI pipeline gets executed? It happens in the ABAP stack.
All messsages picked by the Adapter Framework running on the J2EE engine are passed to the Integration Engine, which does the routing. The mapping program again gets executed on the Java stack and the rest of the pipeline servies are executed again on the ABAP stack and so on.
Take a look at the XI overview doc to understand this better,
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a3d3c390-0201-0010-c490-bd85917138c8
Regards,
Bhavesh

Hi All difference between abap and hr-abap urgent pls

Hi All difference between abap and hr-abap urgent pls

Hello,
To add to the above points regarding infotypes
Infotypes stand apart in HR and manage a volume of data in HR domain..they are unique to HR module ranging from basic employee information to time management and finally the custom infotypes.....
Payroll and other monetory activities related to an employee also form a vital part of the HR module....
while considering Reports..in HR data is mainly with respect to infotypes and the concept of PAKEY...7 key fields which uniquely defines any record in an infotype is used..with Pernr(employee number),Begda(begindate) and Endda(enddate) form an integral part of the key..Based on the time constraints(1,2,3) of an infotype the keys are judged (to retrieve data from an infotype)
In ABAP HR we also have lots of predefined function modules that can be used..eg:go to se37..put 'HR*' and press F4...
finally to update an HR infotype record we use the function module hr operation rather than direct updates...also there are standard audit trail reports that monitors various activities such as insert/modify/delete operations on an hr infotype record...
Pls revert back for clarity and reward if helpful
Regards
Byju

Using Portal navigation for KM Integration in ABAP

Hi All,
I am trying to call the KM Navigation iview from ABAP webdynpro view. it is like implement the same functionality as currently available for Repository filters through ABAP coding. I have to create a new Folder in the KM and call the KM Navigation iview for that specific folder. I know KM has provided few new webservices which I can use to create a new folder in the KM repository but I am unable to open the KM navigation iview with the newly created folder through coding.
I am using the navigate_absolute Portal Navigation method to call the KM Navigation iview from ABAP code. Currently it is opening iview with the folder set as root folder in the iview property but I need to open it with the newly created folder through the code. The same sort of functionality is implemented from java code by passing the Business parameter with navigate_absolute method. The problem with ABAP code is that I don't know what is the exact format of the Business parameter to be passed.
In the java code the Business parameter is passed as
Uri=/documents/cprxrpm/46A73F1FEED21B0DE10000000A4241A8:DFM_450_MIT3_SAURABH/RIH/47B44774254208CCE10000000A4241A8:wonder-item-01 :WONDER-ITEM-01
Does anybody have idea how can i implement the same scenario in ABAP and what should be the format of the to be passed as Business Parameter from ABAP code ?
Regards,
Vikash

There isn't specific knowledge concerning the BusinessObjectsKM in this forum - you may try over at Business Object > Integration Kit SAP forum, or open a new Support Message with SAP.
Sincerely,
Ted Ueda

ABAP aND Java Stack

Whats the use of an ABAP and Java Stacks in XI? What exactly they are doing for XI?
Thanks.

Hi,
Tha ABAP stack consists of the Integration Server which in turn contains your Integration Engine and Business Process Engine.
The J2EE stack contains the Adapter Engine and your IR and ID run on the J2EE engine.
Ever wondered how and where the XI pipeline gets executed? It happens in the ABAP stack.
All messsages picked by the Adapter Framework running on the J2EE engine are passed to the Integration Engine, which does the routing. The mapping program again gets executed on the Java stack and the rest of the pipeline servies are executed again on the ABAP stack and so on.
Take a look at the XI overview doc to understand this better,
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a3d3c390-0201-0010-c490-bd85917138c8
Regards,
Bhavesh

Integration Webdynpro ABAP with Webdynpro Java in Portal

Hi All,
I am facing problem while integrating WDA application with WDJ. I can integrate successfuly one application and trying to invoke other one with different parameters, i am facing the problem
There is no iView available for system "XXXX_SAP_XXX": object "xxx.xxxx.xxx.xxxx". For more information, contact your administrator.
I am passing the parameters
system
object_type
object_value_name
operation
Thanks in advance

Hi Samir,
Pls look into these threads -
IE8 problem (WebDynpro ABAP iView call)
WebDynpro for ABAP and IE 8.0
Regards,
Sen

Can we have ABAP and PI in same client in the same system?

Hi Consultants,
Can inbound and outbound scenarios work, if the ABAP and PI (7.01) is in the same client ?
If yes, then can you please let me know the settings and configurations required.
Thanks in advance.
Regards,
Naushad

Hello
Please elaborate on your requirements. Are you talking about proxy scenarios? Do you mean can the PI Integration Server client act as a proxy Sender/receiver?
If yes, I don't think this is possible.
Regards
Mark

I would say integrating an ABAP Debugger in Eclipse would be a super idea

Because debugging is the best medicine for root cause analysis, integrating an ABAP Debugger in Eclipse for next generation ABAP development would be a great idea, as this will help facilitate faster and more efficient root cause analysis.
Also in line with SAP's future strategy (support without incidents), this integration on the client's side will in my opinion help fastrack critical issues, thereby reducing the volumes of incoming incidents.
More suggestions on this topic are welcome!

Hi Adrian,
we have a debugger in place in Eclipse. In case you are developing on an ABAP system 7.31 you need an Kernel update in order to debug with eclipse. The Kernel version you need is 7.21.
Have Fun,
Regards,
Thomas.

What is the meaning of ABAP/4 editor integrated with ABAP/4 data dictionary

hi All
i want the correct meaning of the following sentence <b>"What is the meaning of ABAP/4 editor integrated with ABAP/4 data dictionary"</b>.If any onre knows kindly explain me...
thanks in advance...

Hi,
Abap is programming language in business, data dictionary is kind a interface for editor to retrive from database level to presentation area. its a meta data.
The ABAP Dictionarys integration with the rest of the development environment enables ABAP programs to automatically recognize the names and characteristics of dictionary objects.
Additionally, the system provides easy navigation between development objects and dictionary definitions. For example, as a programmer, you can double-click on the name of a dictionary object in your program code, and the system will take you directly to the definition of that object in the ABAP/4 Dictionary.
Reward points if helpful,
regards,
jinesh

Level of Knowledge in ABAP and Java?

Hi All,
I am seeking a career in SAP Netweaver Process Integration - XI and would like to know what level of knowledge would i need to have in ABAP and Java. If i should have any what are the area's that would be expected. Please Clarify.
Your advice will be greatly appreciated.
Thank You,
Ajay C Indukuru.

Hi Ajay
in addition to chirag's comment
We use ABAP Proxies in case of we are dealing with the ABAP Based Applications
We use JAVA Proxies in case of we are dealing with the JAVA based application
in SAP XI We have two ways of connectivity
1) adapter
2)proxy
in applications based on WAS 6.20 or above we can directly communicate to XI through Proxies
while application based on below WAS 6.20 you have to use adaptyer to communicate to XI
proxies seperate business application logic from the integration logic of integration logic
proxy generation converts non language specific interface description in WSDL into executable interface
Java proxy is generated from the WSDL description opf interface and this is generated as a JAR file in IR
while ABAP proxy is generated by transaction SPROXY
on Application server based on WSDL description of message interface
PROXIES have same mode and direction as Interfaces have
To learn Java you should know only basic concepts of java means you must have basic java programmin skill
Java proxy can be generated through wizard also this is an inbuild functionality of SAP XI
to lear java follow this link
java.sun.com/docs/books/tutorial/
To learn ABAP you should know beginner level ABAP4GL
ABAP is very simple language and coding is like that you are writing simple english sentence so you would be feeling comfortable withABAP with a little practice
GO to T CODE se24 and start developing
learn ABAP with this link
http://www.itquestionbank.com/sams-teach-yourself-abap-4-in-21-days.html
for more advance version you may follow SDN
in my opinion nothing is so hard to learn
i hope this may assist you
if helpful kindly reward points
Regards
Sandeep Sharma

Integration of SD and MM Module

Hi,
I Want to know the How to Integrating the SD and MM Module .Please help this topic .
Thanks & Regards
Raghava

hi,
MM Process flow:
The typical procurement cycle for a service or material consists of the following phases:
1. Determination of Requirements
Materials requirements are identified either in the user departments or via materials planning and control. (This can cover both MRP proper and the demand-based approach to inventory control. The regular checking of stock levels of materials defined by master records, use of the order-point method, and forecasting on the basis of past usage are important aspects of the latter.) You can enter purchase requisitions yourself, or they can be generated automatically by the materials planning and control system.
2. Source Determination
The Purchasing component helps you identify potential sources of supply based on past orders and existing longer-term purchase agreements. This speeds the process of creating requests for quotation (RFQs), which can be sent to vendors electronically via SAP EDI, if desired.
3. Vendor Selection and Comparison of Quotations
The system is capable of simulating pricing scenarios, allowing you to compare a number of different quotations. Rejection letters can be sent automatically.
4. Purchase Order Processing
The Purchasing system adopts information from the requisition and the quotation to help you create a purchase order. As with purchase requisitions, you can generate Pos yourself or have the system generate them automatically. Vendor scheduling agreements and contracts (in the SAP System, types of longer-term purchase agreement) are also supported.
5. Purchase Order Follow-Up
The system checks the reminder periods you have specified and - if necessary - automatically prints reminders or expediters at the predefined intervals. It also provides you with an up-to-date status of all purchase requisitions, quotations, and purchase orders.
6. Goods Receiving and Inventory Management
Goods Receiving personnel can confirm the receipt of goods simply by entering the Po number. By specifying permissible tolerances, buyers can limit over- and underdeliveries of ordered goods.
7. Invoice Verification
The system supports the checking and matching of invoices. The accounts payable clerk is notified of quantity and price variances because the system has access to PO and goods receipt data. This speeds the process of auditing and clearing invoices for payment.
Common Tables used by SAP MM:
Below are few important Common Tables used in Materials Management Modules:
EINA Purchasing Info Record- General Data
EINE Purchasing Info Record- Purchasing Organization Data
MAKT Material Descriptions
MARA General Material Data
MARC Plant Data for Material
MARD Storage Location Data for Material
MAST Material to BOM Link
MBEW Material Valuation
MKPF Header- Material Document
MSEG Document Segment- Material
MVER Material Consumption
MVKE Sales Data for materials
RKPF Document Header- Reservation
T023 Mat. groups
T024 Purchasing Groups
T156 Movement Type
T157H Help Texts for Movement Types
MOFF Lists what views have not been created
A501 Plant/Material
EBAN Purchase Requisition
EBKN Purchase Requisition Account Assignment
EKAB Release Documentation
EKBE History per Purchasing Document
EKET Scheduling Agreement Schedule Lines
EKKN Account Assignment in Purchasing Document
EKKO Purchasing Document Header
EKPO Purchasing Document Item
IKPF Header- Physical Inventory Document
ISEG Physical Inventory Document Items
LFA1 Vendor Master (General section)
LFB1 Vendor Master (Company Code)
NRIV Number range intervals
RESB Reservation/dependent requirements
T161T Texts for Purchasing Document Types
Transaction Codes:
RFQ to Vendor - ME41
Raising Quotation - ME47
Comparison of Price - ME49
Creation of PO - ME21N
Goods Receipt - MIGO
Invoice (Bill PAssing) - MIRO
Goods Issue - MB1A
Physical Inventory - MI01( Create doc)
MI04 (Enter Count)
MI07 (Post)
Also please check this links.
http://www.sapgenie.com/sapfunc/mm.htm
http://www.sap-basis-abap.com/sapmm.htm
SD Process Flow:
The sales documents you create are individual documents but they can also form part of a chain of inter-related documents. For example, you may record a customers telephone inquiry in the system. The customer next requests a quotation, which you then create by referring to the inquiry. The customer later places an order on the basis of the quotation and you create a sales order with reference to the quotation. You ship the goods and bill the customer. After delivery of the goods, the customer claims credit for some damaged goods and you create a free-of-charge delivery with reference to the sales order. The entire chain of documents the inquiry, the quotation, the sales order, the delivery, the invoice, and the subsequent delivery free of charge creates a document flow or history. The flow of data from one document into another reduces manual activity and makes problem resolution easier. Inquiry and quotation management in the Sales Information System help you to plan and control your sales.
Transaction Codes:
Inquiry - VA11/VA12/VA13
Quotation - VA21/VA22/VA23
Sales Order - VA01/VA02/VA03
Delivery - VL01N/VL02N/VL03N
Billing/Invoicing - VF01/VF02/VF03
Also please check this links.
http://www.sapgenie.com/sapfunc/sd.htm
http://www.sap-basis-abap.com/sapsd.htm
http://www.sapgenie.com/abap/tables_sd.htm
VBAK: Sales Document(Header Data) (VBELN)
VBAP: Sales Document(Item Data) (VBELN,POSNR,MATNR,ARKTX,CHARG)
Enquiry, Quotation, Sales Order are differentiated based on Doc.
Type(VBTYP field) in VBAK,VBAP Tables( for Enquiry VBTYP = A,
for Quotation 'B' & for Order it is 'C'.)
LIKP: Delivery Table (Header Data)(VBELN,LFART,KUNNR,WADAT,INCO1)
LIPS: Delivery Table (Item Data)(VBELN,POSNR,WERKS,LGORT,MATNR,VGBEL)
(LIPS-VGBEL = VBAK-VBELN, LIPS-VGPOS = VBAP-POSNR)
VTTK: Shipment Table (Header Data)(TKNUM)
VTTP: Shipment Table (Item Data)( TKNUM,TPNUM,VBELN)
(VTTP-VBELN = LIKP-VBELN)
VTFA: Shipping Document Flow(TKNUM,VBELV,VBELN)
VTPA: Shipping Partners data(VBELN,PARVW,KUNNR,PERNR)
VTTS: Stages in Shipment(TKNUM,TSNUM,TSTYP)
VTSP: Transport Stage/Shipment Item Allocation(TKNUM,TSNUM,TPNUM)
VEKP: Handling Unit: Header(Packing)(VENUM,VSTEL)
VEPO: Handling Unit: Item (Packing)(VENUM,VEPOS,VBELN)
VBRK: Billing Table(Header Data)(VBELN,FKART,BELNR)
VBRP: Billing Table(Item Data)(VBELN,POSNR,FKIMG,NETWR,VGBEL,VGPOS)
(VBRP-AUBEL = VBAK-VBELN, VBRP-VGBEL = LIKP-VBELN)
Apart from these tables there are lot of other tables which starts with
V, but we use the following tables frequently.
VBUK: All Sales Documents status & Admn. Data(Header)(VBELN,VBTYP)
VBTYP= C(Sales Order) VBTYP=J(Delivery) VBTYP=M(Invoice)
VBUP: Sales Documents status & Admn. Data(Item)(VBELN,POSNR)
MM
EBAN-- Pur.Reqn. Data (BANFN,BNFPO,BADAT,MATNR)
EBKN-- Purchase Requisition Account Assignment(BANFN,BNFPO,VBELN)
EINA- Purchase Info.Record (General Data)(INFNR,MATNR,LIFNR)
EINE-- Purchase Info.Record (Pur.Orgn Data )(INFNR,EKORG)
ELBK-- Vendor Evaluation Header Data(LIFNR,EKORG,KLASS)
ELBM-- Vendor Evaluation: Material-Related Item(LIFNR,MATNR,EKORG,INFNR,HKRIT)
ELBP- Main Criteria for Vendor Evaluation (LIFNR,EKORG,HKRIT)
EKKO-- Purchase Order Data (Header)(EBELN,BSTYP,BSART)
EKPO-- Purchase Order Data (Item)(EBELN,EBELP,MATNR)
RFQ and PO are differentiated by Doc Type(BSTYP)in EKKO table.
For RFQ it is A and for PO it is F.
MKPF-- GRN Data (Header) (EBELN,BLDAT,BUDAT,XBLNR,BKTXT)
MSEG-- GRN Data (Item)(MBLNR,BWART,LIFNR,MATNR,EBELN)
The link between SD and MM :-
1. When you create sales order in SD, all the details of the items are copied from Material master of MM.
2. MRP and availibility check related data is also taken from MM although you control this data in SD also.
3. While you create inbound/outbound delivery with reference to a sales order,the shipping point determination takes place with the help of the loading group, plant data, shipping conditions etc. This also refers to Material Master.
4. The material which you are entering in a sales order must be extended to the sales area of your sales order/customer otherwise you cannot transact with this material.

Integration of ABAP and SD?

Similar Messages

Maybe you are looking for