Finding the modules implemented in a SAP system

Hi All,
Is there any way of finding the modules implemented in a SAP system?
Please reply.
Thanks in advance
Dhanapal S

Hi Dhanpal,
This is more of a functional question than a technical question. But if you can give a list of all the modules that you would like to know about, then it may be possible to get fair idea of which of them have been implemented.
For example, if you'd like to know whether SD is imploemented or not, you would look for data in tables like TVKO, VBAK, VBAP etc.,
In case of HR, you will see if there are any infotypes being used. for example tables PA0001 etc.,
In case of MM, you will look at tables like MARA etc.,
These points are by no means comprehensive. There are so many other factors that neeed to be considered. For example, if SD is implemented, then in general MM will also be implemented (may not necessairly be the case, but this is common).
The point is that we examine the Customizing Data and Master Data for each of the modules and figure out if it is being implemented.
But the easiest way is to ask the customer which ones he is implementing.
Regards,
anand Mandalika.

Similar Messages

Where do I find the Group account number in SAP system

Hi All,
I have the same problem. I work in a company where all was installed and configured before my arrival and so I always need to do a lot of research to solve a problem.
I tried somedays ago using txcode FS00 to create a new GL account but got stocked because the system requested a Group Account Number (Consolidation data in Charts of Accounts).
I do not know where to find this number in the system. After a very long search, I have given up searching and hereby ask for your help.
Can anyone tell me where to find the Group Account Number in the system. Is there a txcode for this? I tried already OBD4.
As I am new in the SAP world, a step by step explanation will be appreciated.
Many thanks in advance

Hello aolowu
Group Account Number field has lot of year/period end ramifications. Here is the definition " When you define the balance sheet and PL structures, then accounts are assigned to line items within the balance sheet and PL. This assignment is made either via the G/L account number or alternatively via the group account number given in this field. The usage of the group account number offers the advantage that by specifying a number, a group of accounts can be assigned immediately to the balance sheet or P+L item". Suggest you work with a FI guy.
To quickly get over however, you can enter the same number that you are creating in that field. At my current client, I have seen several accounts set up like this, although many of them have a different number there.

Finding the Installed version of a SAP system

Hi Colleagues,
If a system is upgraded, how do i see on what level it was installed or which SP level Installer was used??
Regards,
Anu

Hi Ajit,
I think i have not made myself clear. The system is already undergone several upgrades. But i want to know on what level it was installed initially...... How do i check it ...
Through the procedure u have mentioned i will be able to check the version of the system at present....
Regards,
Anu

Where i can find the deleted transport request in SAP development system?

where i can find the deleted transport request in SAP development system?

Hi,
When you delete the transport request from SE10 , you can not find the request entry from E070 and E071.
and only local change request are possible to delete from SE10 /SE09
if you are try to delete the change request with target system then it's gives you the error that request cannot be deleted because it contains locked objects.
It's not possible to find out the deleted request from SE10.
regards,
kaushal

What are the major process to transfer the data from legacy to sap system.

What are the major process to transfer the data from legacy to sap system using BDC at Real Time only?

hi,
BATCH DATA COMMUNICATION
main methods are:
1. SESSION METHOD
2. CALL TRANSACTION
3. DIRECT INPUT
Advantages offered by BATCH INPUT method:
1. Can process large data volumes in batch.
2. Can be planned and submitted in the background.
3. No manual interaction is required when data is transferred.
4. Data integrity is maintained as whatever data is transferred to the table is through transaction. Hence batch input data is submitted to all the checks and validations.
To implement one of the supported data transfers, you must often write the program that exports the data from your non-SAP system. This program, known as a data transfer program must map the data from the external system into the data structure required by the SAP batch input program.
The batch input program must build all of the input to execute the SAP transaction.
Two main steps are required:
To build an internal table containing every screen and every field to be filled in during the execution of an SAP transaction.
To pass the table to SAP for processing.
Prerequisite for Data Transfer Program
Writing a Data Transfer Program involves following prerequisites:
Analyzing data from local file
Analyzing transaction
Analyzing transaction involves following steps:
The transaction code, if you do not already know it.
Which fields require input i.e., mandatory.
Which fields can you allow to default to standard values.
The names, types, and lengths of the fields that are used by a transaction.
Screen number and Name of module pool program behind a particular transaction.
To analyze a transaction::
Start the transaction by menu or by entering the transaction code in the command box.
(You can determine the transaction name by choosing System Status.)
Step through the transaction, entering the data will be required for processing your batch input data.
On each screen, note the program name and screen (dynpro) number.
(dynpro = dyn + pro. Dyn = screen, pro = number)
Display these by choosing System Status. The relevant fields are Program (dynpro) and Dynpro number. If pop-up windows occur during execution, you can get the program name and screen number by pressing F1 on any field or button on the screen.
The technical info pop-up shows not only the field information but also the program and screen.
For each field, check box, and radio button on each screen, press F1 (help) and then choose Technical Info.
Note the following information:
- The field name for batch input, which youll find in its own box.
- The length and data type of the field. You can display this information by double clicking on the Data Element field.
Find out the identification code for each function (button or menu) that you must execute to process the batch-input data (or to go to new screen).
Place the cursor on the button or menu entry while holding down the left mouse button. Then press F1.
In the pop-up window that follows, choose Technical info and note the code that is shown in the Function field.
You can also run any function that is assigned to a function key by way of the function key number. To display the list of available function keys, click on the right mouse button. Note the key number that is assigned to the functions you want to run.
Once you have program name, screen number, field name (screen field name), you can start writing.
DATA TRANSFER program.
Declaring internal table
First Integral Table similar to structure like local file.
Declaring internal table like BDCDATA
The data from internal table is not transferred directly to database table, it has to go through transaction. You need to pass data to particular screen and to particular screen-field. Data is passed to transaction in particular format, hence there is a need for batch input structure.
The batch input structure stores the data that is to be entered into SAP system and the actions that are necessary to process the data. The batch input structure is used by all of the batch input methods. You can use the same structure for all types of batch input, regardless of whether you are creating a session in the batch input queue or using CALL TRANSACTION.
This structure is BDCDATA, which can contain the batch input data for only a single run of a transaction. The typical processing loop in a program is as follows:
Create a BDCDATA structure
Write the structure out to a session or process it with CALL TRANSACTION USING; and then
Create a BDCDATA structure for the next transaction that is to be processed.
Within a BDCDATA structure, organize the data of screens in a transaction. Each screen that is processed in the course of a transaction must be identified with a BDCDATA record. This record uses the Program, Dynpro, and Dynbegin fields of the structure.
The screen identifier record is followed by a separate BDCDATA record for each value, to be entered into a field. These records use the FNAM and FVAL fields of the BDCDATA structure. Values to be entered in a field can be any of the following:
Data that is entered into screen fields.
Function codes that are entered into the command field. Such function codes execute functions in a transaction, such as Save or Enter.
The BDCDATA structure contains the following fields:
PROGRAM: Name of module pool program associated with the screen. Set this field only for the first record for the screen.
DYNPRO: Screen Number. Set this field only in the first record for the screen.
DYNBEGIN: Indicates the first record for the screen. Set this field to X, only for the first record for the screen. (Reset to (blank) for all other records.)
FNAM: Field Name. The FNAM field is not case-sensitive.
FVAL: Value for the field named in FNAM. The FVAL field is case-sensitive. Values assigned to this field are always padded on the right, if they are less than 132 characters. Values must be in character format.
Transferring data from local file to internal table
Data is uploaded to internal table by UPLOAD of WS_UPLOAD function.
Population of BDCDATA
For each record of internal table, you need to populate Internal table, which is similar to BDCDATA structure.
All these five initial steps are necessary for any type of BDC interface.
DATA TRANSFER program can call SESSION METHOD or CALL TRANSACTION. The initial steps for both the methods are same.
First step for both the methods is to upload the data to internal table. From Internal Table, the data is transferred to database table by two ways i.e., Session method and Call transaction.
SESSION METHOD
About Session method
In this method you transfer data from internal table to database table through sessions.
In this method, an ABAP/4 program reads the external data that is to be entered in the SAP System and stores the data in session. A session stores the actions that are required to enter your data using normal SAP transaction i.e., Data is transferred to session which in turn transfers data to database table.
Session is intermediate step between internal table and database table. Data along with its action is stored in session i.e., data for screen fields, to which screen it is passed, the program name behind it, and how the next screen is processed.
When the program has finished generating the session, you can run the session to execute the SAP transactions in it. You can either explicitly start and monitor a session or have the session run in the background processing system.
Unless session is processed, the data is not transferred to database table.
BDC_OPEN_GROUP
You create the session through program by BDC_OPEN_GROUP function.
Parameters to this function are:
User Name: User name
Group: Name of the session
Lock Date: The date on which you want to process the session.
Keep: This parameter is passed as X when you want to retain session after
processing it or to delete it after processing.
BDC_INSERT
This function creates the session & data is transferred to Session.
Parameters to this function are:
Tcode: Transaction Name
Dynprotab: BDC Data
BDC_CLOSE_GROUP
This function closes the BDC Group. No Parameters.
Some additional information for session processing
When the session is generated using the KEEP option within the BDC_OPEN_GROUP, the system always keeps the sessions in the queue, whether it has been processed successfully or not.
However, if the session is processed, you have to delete it manually. When session processing is completed successfully while KEEP option was not set, it will be removed automatically from the session queue. Log is not removed for that session.
If the batch-input session is terminated with errors, then it appears in the list of INCORRECT session and it can be processed again. To correct incorrect session, you can analyze the session. The Analysis function allows to determine which screen and value has produced the error. If you find small errors in data, you can correct them interactively, otherwise you need to modify batch input program, which has generated the session or many times even the data file.
CALL TRANSACTION
About CALL TRANSACTION
A technique similar to SESSION method, while batch input is a two-step procedure, Call Transaction does both steps online, one after the other. In this method, you call a transaction from your program by
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>
Messages into <MSGTAB>.
Parameter 1 is transaction code.
Parameter 2 is name of BDCTAB table.
Parameter 3 here you are specifying mode in which you execute transaction
A is all screen mode. All the screen of transaction are displayed.
N is no screen mode. No screen is displayed when you execute the transaction.
E is error screen. Only those screens are displayed wherein you have error record.
Parameter 4 here you are specifying update type by which database table is updated.
S is for Synchronous update in which if you change data of one table then all the related Tables gets updated. And sy-subrc is returned i.e., sy-subrc is returned for once and all.
A is for Asynchronous update. When you change data of one table, the sy-subrc is returned. And then updating of other affected tables takes place. So if system fails to update other tables, still sy-subrc returned is 0 (i.e., when first table gets updated).
Parameter 5 when you update database table, operation is either successful or unsuccessful or operation is successful with some warning. These messages are stored in internal table, which you specify along with MESSAGE statement. This internal table should be declared like BDCMSGCOLL, a structure available in ABAP/4. It contains the following fields:
1. Tcode: Transaction code
2. Dyname: Batch point module name
3. Dynumb: Batch input Dyn number
4. Msgtyp: Batch input message type (A/E/W/I/S)
5. Msgspra: Batch input Lang, id of message
6. Msgid: Message id
7. MsgvN: Message variables (N = 1 - 4)
For each entry, which is updated in database, table message is available in BDCMSGCOLL. As BDCMSGCOLL is structure, you need to declare a internal table which can contain multiple records (unlike structure).
Steps for CALL TRANSACTION method
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. UPLOAD or WS_UPLOAD function to upload the data from local file to itab. (Considering file is local file)
4. Loop at itab.
Populate BDCTAB table.
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>.
Refresh BDCTAB.
Endloop.
(To populate BDCTAB, You need to transfer each and every field)
The major differences between Session method and Call transaction are as follows:
SESSION METHOD CALL TRANSACTION
1. Data is not updated in database table unless Session is processed. Immediate updation in database table.
2. No sy-subrc is returned. Sy-subrc is returned.
3. Error log is created for error records. Errors need to be handled explicitly
4. Updation in database table is always synchronous Updation in database table can be synchronous Or Asynchronous.
Error Handling in CALL TRANSACTION
When Session Method updates the records in database table, error records are stored in the log file. In Call transaction there is no such log file available and error record is lost unless handled. Usually you need to give report of all the error records i.e., records which are not inserted or updated in the database table. This can be done by the following method:
Steps for the error handling in CALL TRANSACTION
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. Internal table BDCMSG like BDCMSGCOLL
4. Internal table similar to Ist internal table
(Third and fourth steps are for error handling)
5. UPLOAD or WS_UPLOAD function to upload the data from the local file to itab. (Considering file is local file)
6. Loop at itab.
Populate BDCTAB table.
Call transaction <tr.code> using <Bdctab>
Mode <A/N/E>
Update <S/A>
Messages <BDCMSG>.
Perform check.
Refresh BDCTAB.
Endloop.
7 Form check.
IF sy-subrc <> 0. (Call transaction returns the sy-subrc if updating is not successful).
Call function Format_message.
(This function is called to store the message given by system and to display it along with record)
Append itab2.
Display the record and message.
DIRECT INPUT
About Direct Input
In contrast to batch input, this technique does not create sessions, but stores the data directly. It does not simulate the online transaction. To enter the data into the corresponding database tables directly, the system calls a number of function modules that execute any necessary checks. In case of errors, the direct input technique provides a restart mechanism. However, to be able to activate the restart mechanism, direct input programs must be executed in the background only. Direct input checks the data thoroughly and then updates the database directly.
You can start a Direct Input program in two ways;
Start the program directly
This is the quickest way to see if the program works with your flat file. This option is possible with all direct input programs. If the program ends abnormally, you will not have any logs telling you what has or has not been posted. To minimize the chance of this happening, always use the check file option for the first run with your flat file. This allows you to detect format errors before transfer.
Starting the program via the DI administration transaction
This transaction restarts the processing, if the data transfer program aborts. Since DI document are immediately posted into the SAP D/B, the restart option prevents the duplicate document posting that occurs during a program restart (i.e., without adjusting your flat file).
Direct input is usually done for standard data like material master, FI accounting document, SD sales order and Classification for which SAP has provided standard programs.
First time you work with the Direct Input administration program, you will need to do some preparation before you can transfer data:
- Create variant
- Define job
- Start job
- Restart job
Common batch input errors
- The batch input BDCDATA structure tries to assign values to fields which do not exist in the current transaction screen.
- The screen in the BDCDATA structure does not match the right sequence, or an intermediate screen is missing.
- On exceptional occasions, the logic flow of batch input session does not exactly match that of manual online processing. Testing the sessions online can discover by this.
- The BDCDATA structure contains fields, which are longer than the actual definition.
- Authorization problems.
RECORDING A BATCH INPUT
A B recording allows you to record a R/3 transaction and generate a program that contains all screens and field information in the required BDC-DATA format.
You can either use SHDB transaction for recording or
SYSTEM ? SERVICES ? BATCH INPUT ? EDIT
And from here click recording.
Enter name for the recording.
(Dates are optional)
Click recording.
Enter transaction code.
Enter.
Click Save button.
You finally come to a screen where, you have all the information for each screen including BDC_OKCODE.
Click Get Transaction.
Return to BI.
Click overview.
Position the cursor on the just recorded entry and click generate program.
Enter program name.
Click enter
The program is generated for the particular transaction.
BACKGROUND PROCESSING
Need for Background processing
When a large volume of data is involved, usually all batch inputs are done in background.
The R/3 system includes functions that allow users to work non-interactively or offline. The background processing systems handle these functions.
Non-interactively means that instead of executing the ABAP/4 programs and waiting for an answer, user can submit those programs for execution at a more convenient planned time.
There are several reasons to submit programs for background execution.
The maximum time allowed for online execution should not exceed 300 seconds. User gets TIMEOUT error and an aborted transaction, if time for execution exceeds 300 seconds. To avoid these types of error, you can submit jobs for background processing.
You can use the system while your program is executing.
This does not mean that interactive or online work is not useful. Both type of processing have their own purposes. Online work is the most common one entering business data, displaying information, printing small reports, managing the system and so on. Background jobs are mainly used for the following tasks; to process large amount of data, to execute periodic jobs without human intervention, to run program at a more convenient, planned time other than during normal working hours i.e., Nights or weekends.
The transaction for background processing is SM36.
Or
Tools ? Administration ? Jobs ? Define jobs
Or
System ? services ? Jobs
Components of the background jobs
A job in Background processing is a series of steps that can be scheduled and step is a program for background processing.
Job name. Define the name of assigned to the job. It identifies the job. You can specify up to 32 characters for the name.
Job class. Indicates the type of background processing priority assigned to the job.
The job class determines the priority of a job. The background system admits three types of job classes: A B & C, which correspond to job priority.
Job steps. Parameters to be passed for this screen are as follows:
Program name.
Variant if it is report program
Start criteria for the job: Option available for this are as follows:
Immediate - allows you to start a job immediately.
Date/Time - allows you to start a job at a specific name.
After job - you can start a job after a particular job.
After event - allows you to start a job after a particular event.
At operation mode - allows you to start a job when the system switches to a particular operation mode.
Defining Background jobs
It is two step process: Firstly, you define the job and then release it.
When users define a job and save it, they are actually scheduling the report i.e., specifying the job components, the steps, the start time.
When users schedule program for background processing, they are instructing the system to execute an ABAP/4 report or an external program in the background. Scheduled jobs are not executed until they are released. When jobs are released, they are sent for execution to the background processing system at the specified start time. Both scheduling and releasing of jobs require authorizations.
HANDLING OF POP UP SCREEN IN BDC
Many times in transaction pop up screen appears and for this screen you dont pass any record but some indication to system telling it to proceed further. For example: The following screen
To handle such screen, system has provided a variable called BDC_CURSOR. You pass this variable to BDCDATA and process the screen.
Usually such screen appears in many transactions, in this case you are just passing information, that YES you want to save the information, that means YES should be clicked. So you are transferring this information to BDCDATA i.e., field name of YES which is usually SPOT_OPTION. Instead of BDC_OKCODE, you are passing BDC_CURSOR.
BDC_CURSOR is also used to place cursor on particular field.
A simple transaction where you are entering customer number on first screen and on next screen data is displayed for the particular customer number. Field, which we are changing here, are name and city. When you click on save, the changed record gets saved.
Prerequisite to write this BDC interface as indicated earlier is:
1. To find screen number
2. To find screen field names, type of the field and length of the field.
3. To find BDC_OKCODE for each screen
4. Create flat file.
generally Batch Input usually are used to transfer large amount of data. For example you are implementing a new SAP project, and of course you will need some data transfer from legacy system to SAP system.
CALL TRANSACTION is used especially for integration actions between two SAP systems or between different modules. Users sometimes wish to do something like that click a button or an item then SAP would inserts or changes data automatically. Here CALL TRANSACTION should be considered.
2. Transfer data for multiple transactions usually the Batch Input method is used.
check these sites for step by step process:
For BDC:
http://myweb.dal.ca/hchinni/sap/bdc_home.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&
http://www.sap-img.com/abap/learning-bdc-programming.htm
http://www.sapdevelopment.co.uk/bdc/bdchome.htm
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html
Check these link:
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://www.sap-img.com/abap/question-about-bdc-program.htm
http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/
http://www.planetsap.com/bdc_main_page.htm
call Transaction or session method ?
null

PageComposer Error - Cannot find the module necessary for printing C5051

Hi
Having some problems trying to setup a Windows 2008 R2 print server with shared Canon iR C5051 printer
I've created the printer, installed the 64 bit driver Canon iR-ADV C5045/5051 PCL6 v 20.90 and works fine for 64 bit Windows 7 clients, installed the 32 bit driver by selecting printer properties, sharing tab, additional drivers and selecting x86 and pointing to the 32 bit PCL driver. Driver installs fine on the print server without any errors.
Goto 32 bit client, add printer, select the shared printer from the printserver, printer installs Ok. When the user however tries to print, get the error:-
Canon PageComposer
Cannot find the module necessary for printing
Re-install the printer driver
I've done this countless times, any idea's on how to fix ?
Thanks

Where is the code you posted? Running in a separate project, I assume? Does that project have a dependency on the project containing the app module specified?
And just to check (although by default, JDev should do this for you)--the app module project has been compiled since adding the configuration, right? You need to check to make sure the config exists not only under Project/src, but under Project/classes.
Edited by: Avrom Roy-Faderman on Oct 6, 2008 2:02 PM
Oh, and BTW--I assume this is not a typical ADF application, right? In a standard ADF application, you would very rarely need to instantiate an application module in code like this; you could just let the data binding facility do it for you. The technique like the one you're using is most appropriate for purely programmatic, no-UI cases. (e.g., once I tried to implement an SMTP server backed by business components. That was an appropriate case for ditching databindings and doing the sort of thing you're doing, because it had no view layer (because it had no UI to render).

Cannot find the HTML browser installed on your system

Guys forgive me if you have answered this before, I have
tried a search of previous issues TNA.
I have reloaded R/H 6 to my laptop (with full admin rights
set against my user name) everything except works except generating
in Microsoft HTML Help I get the following error when I click
Finish: cannot find the HTML browser installed on your system
Any ideas welcome. With thanks, J

Hi JayRichard
You might try the following.
Inside RoboHelp HTML, click Tools > Options...
Click the Tool Locations tab
At the bottom of the dialog should be an area listing
"Browser paths". You should see one for Internet Explorer and one
for Netscape. Try clicking the little file folder icon to the right
of one of them. (Whichever browser you are using)
Navigate to and select the executable file for the browser.
Mine for Internet Explorer says:
D:\Program Files\...\iexplore.exe (The full path is
D:\Program Files\Internet Explorer\iexplore.exe
Dismiss the dialogs by clicking the Open and OK buttons until
they are all gone.
Keep us posted on whether this helps... Rick

Cannot find the class file for com.sap.portal.services.api.connectorgateway

Hi,
I was trying the "How to BI JAVA SDK in a Portal iView and get the following error.
The project was not built since its classpath is incomplete. Cannot find the class file for com.sap.portal.services.api.connectorgateway.IConnectorGatewayService. Fix the classpath and try rebuilding this project.
I have the following in my portalapp.xml file
<property name="SharingReference" value="com.sap.portal.ivs.connectorservice"/>
and i have also added the jar file "com.sap.portal.ivs.connectorservice_api" in the set of lib's
Has some faced a similar issue? or can someone suggest how I could possibly resolve this.
Thanks,
Smitha

Hi Smitha:
My webdynpro dc was build failed for "This compilation unit indirectly references the missing type com.sap.engine.services.webservices.espbase.client.dynamic.content.GenericObject (typically some required class file is referencing a type outside the classpath)".
How should i do? Thank you!

How to find the print program for a sap script

Hey Experts,
How to find the print program for a sap script (espicially when it is a custom script(Z*))?
Thanks a ton,

Thanx Vijay,
Actually when I searched for the program in both the tables it didnt show up ther.
But when I did check in the texts of script, I found it.
Good job.
Thanks all.
Vijay, a small doubt.
But why didn't it show up in those 2 tables when all the print programs for standard scripts show up usually?
thnx once again.
Message was edited by: dev a

How can we change the SID of an existing SAP system.

Hi to all basis experts.
Is it possible to change the SID of an existing SAP system.
i am performing R3copy method and i want to change the SID of the tar

check these link
http://help.sap.com/saphelp_nwmobile71/helpdata/en/aa/1dc94af0fa11d3a6510000e835363f/content.htm
http://sap.ittoolbox.com/documents/changing-the-ltsidgtadm-password-17764

Connecting the UWL to a non-SAP system

Hi,
I am in need of a solution for showing the tasks from a non SAP system (DotNetNuke to be precise) in the UWL.
Our client wants to change from DotNetNuke to the SAP Portal, but doesn't want to change all the processes at ones.
J

I think I found it myself: It is possible to create a Custom Connector API
check this out: http://help.sap.com/javadocs/NW04S/current/uw/UWL%20Custom%20Connector%20API.pdf
If this doesn't work I will report this on the forum.
J.

How to garantee IDOC types are the same on two communicating sap systems.

Hi all:
    how to garantee IDOC types are the same on two communicating sap systems, including segments and versions, using bd64?
    what's more, what bd64 using for besides generating parter profiles, must we use bd64 for outbound idocs?
    Thank you very much
best regards ?

Hi jingying Sony
You can compare the Idoc type and Version between Sender System and Reciver System.
Use TCode SCMP and Compare the Table EDIMSG in Both System.
This will solve your issue.
Thanks
Ramesh

How to find the Access Key of Standard SAP Function Module

Hi Experts,
I have to change one sap standard function module.
so how can i know the access key for that function module.......
Regards,
DS

Contact the Basis Consultant in your project.
The access key for standard SAP objects can be obtained from service.sap.com under Keys and Requests.
Note 86161 - Registering developers and objects

How to know the which add-ons my sap system Have

AS per Note 1318299 - SAP Enhancement Package 5 for SAP ERP 6.0:Compatible Add-ons
Symptom
You plan to run SAP enhancement package 5 for SAP ERP 6.0 together with an Add-On on the same system. Which points do you need to consider?
Other terms
AddOn; add-on; Enhancement Package; compatibility;
Solution
In general, please check whether your Add-On supplier has released your specific Add-On for usage with SAP enhancement package 5 for SAP ERP 6.0.
If you have a solution categorized as '(Standard) Custom Development' for your ERP system, please contact SAP Custom Development at least three months before implementing SAP enhancement package 5 for ERP 6.0, because sufficient time might be required in case of adjustments.
If you find the add-on you are looking for neither in the list below nor in the related notes, please contact SAP Support (for SAP Products) or the specific partner (non SAP-Products).
Then my question is, how can i find, the add-ons present in my windows/oracle ECC 6.0 installation.

HI
All componets are add-on installed in your system. If you want select according technical usages in mantienance optimazer for EHP5 see sap Note 1324838 - Enhancement package 5 for SAP ERP 6.0: Required SWC
In the attachments you found a table with Technical usages - add on.
When you select your technical usages then appear add-on that will be upgrade.
Regards
William Neira

Cannot find the Web Content repository in test system under KM Content

Hi Experts,
We have implemented Web Page Composer in our development landscape. I have created a web page with the required content in the development and now wish to transport this web page and its content to our test system.
However when I navigate to Content Administration -> KM Content, inside the root directory I am not able to find the Web Content repository within which all WPC content resides.
I want to know what configuration has to be done in the test system so that the Web Content repository becomes available within KM Content.
Thanks and Regards,
Saurabh

Hi,
I just want a confirmation on whether I will have to deploy the .SCA file for Web Page Composer in my test and production systems to be able to use the web pages I have created in the development environment.
Regards,
Saurabh

Finding the modules implemented in a SAP system

Similar Messages

Maybe you are looking for