CPU PARAMETER in ABAP for BDC

how to fix the CPU PARAMETER to particular user id .
Or how to use CPU PARAMETER in BDC .

If you SEARCH in SCN you will get lot of information about CTU_PARAMS structure.
You can put simple condition for restricting to specific user.
DATA: batch_params LIKE ctu_params.
If sy-uname = 'TABAP1'.
batch_params-nobiend = 'X'.
batch_params-dismode = 'N'.
endif.
CALL TRANSACTION 'FK01' USING bdcdata
OPTIONS FROM batch_params
MESSAGES INTO itab_messages.

Similar Messages

Please provide me material for bdc

Hi everyone,
can you please provide me some stuff for bdc, actually i am working on bdc for mm01 , so plz send me study materials and if you have any scenario then please forward me.
Thanks & Regards,
Vimarsh B.

Hi
Hope it will help you.
Reward if help.
BATCH DATA COMMUNICATION
About Data Transfer In R/3 System
When a company decides to implement the SAP R/3 to manage business-critical data, it usually does not start from a no-data situation. Normally, a SAP R/3 project comes into replace or complement existing application.
In the process of replacing current applications and transferring application data, two situations might occur:
u2022 The first is when application data to be replaced is transferred at once, and only once.
u2022 The second situation is to transfer data periodically from external systems to SAP and vice versa.
u2022 There is a period of time when information has to be transferred from existing application, to SAP R/3, and often this process will be repetitive.
The SAP system offers two primary methods for transferring data into SAP systems. From non-SAP systems or legacy system. These two methods are collectively called u201Cbatch inputu201D or u201Cbatch data communicationu201D.
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 u201Cdata transferu201D 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:
u2022 To build an internal table containing every screen and every field to be filled in during the execution of an SAP transaction.
u2022 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:
u2022 The transaction code, if you do not already know it.
u2022 Which fields require input i.e., mandatory.
u2022 Which fields can you allow to default to standard values.
u2022 The names, types, and lengths of the fields that are used by a transaction.
u2022 Screen number and Name of module pool program behind a particular transaction.
To analyze a transaction::
u2022 Start the transaction by menu or by entering the transaction code in the command box.
(You can determine the transaction name by choosing System u2013 Status.)
u2022 Step through the transaction, entering the data will be required for processing your batch input data.
u2022 On each screen, note the program name and screen (dynpro) number.
(dynpro = dyn + pro. Dyn = screen, pro = number)
u2022 Display these by choosing System u2013 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.
u2022 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 youu2019ll 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.
u2022 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:
u2022 Create a BDCDATA structure
u2022 Write the structure out to a session or process it with CALL TRANSACTION USING; and then
u2022 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:
u2022 Data that is entered into screen fields.
u2022 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:
u2022 PROGRAM: Name of module pool program associated with the screen. Set this field only for the first record for the screen.
u2022 DYNPRO: Screen Number. Set this field only in the first record for the screen.
u2022 DYNBEGIN: Indicates the first record for the screen. Set this field to X, only for the first record for the screen. (Reset to u2018 u2018 (blank) for all other records.)
u2022 FNAM: Field Name. The FNAM field is not case-sensitive.
u2022 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:
u2022 User Name: User name
u2022 Group: Name of the session
u2022 Lock Date: The date on which you want to process the session.
u2022 Keep: This parameter is passed as u2018Xu2019 when you want to retain session after
processing it or u2018 u2018 to delete it after processing.
BDC_INSERT
This function creates the session & data is transferred to Session.
Parameters to this function are:
u2022 Tcode: Transaction Name
u2022 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 u2013 1 is transaction code.
Parameter u2013 2 is name of BDCTAB table.
Parameter u2013 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 u2013 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 u2013 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.
u2022 Click Get Transaction.
u2022 Return to BI.
u2022 Click overview.
u2022 Position the cursor on the just recorded entry and click generate program.
u2022 Enter program name.
u2022 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.
u2022 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.
u2022 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.
u2022 Job name. Define the name of assigned to the job. It identifies the job. You can specify up to 32 characters for the name.
u2022 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.
u2022 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 donu2019t 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.
AN EXAMPLE WITH SESSION METHOD
Following program demonstrates how data is passed from flat file to SAP transaction and further to database table by using SESSION method.
The transaction is TFBA (to change customer).
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.
Flat file can be created in your hard disk as follows:
1 Vinod Hyderabad
2 Kavitha Secunderabad
3 Kishore Hyderabad
(Where 1st character field is Customer number, 2nd field is Customer name and 3rd field is City.)
To transfer this data to database table SCUSTOM following interface can be used.
REPORT DEMO1.
Following internal table is to upload flat file.
DATA: BEGIN OF ITAB OCCURS 0,
ID(10),
NAME(25),
CITY(25),
END OF ITAB.
*Following internal table BDCDATA is to pass date from internal table to session.
DATA: BDCTAB LIKE BDCDATA OCCURS 0 WITH HEADER LINE.
Variables
DATA: DATE1 LIKE SY-DATUM. DATE1 = SY-DATUM - 1. u201C This is for Hold Date
To upload flat file to internal table.
CALL FUNCTION UPLOAD
EXPORTING
FILE NAME = u2018C:\FF.TXTu2019
FILE TYPE = u2018ASCu201D
TABLES
DATA_TAB = ITAB
EXCEPTIONS
CONVERSION_ERROR = 1
INVALID_TABLE_WIDTH = 2
INVALID_TYPE = 3
NO_BATCH = 4
UNKNOWN_ERROR = 5
OTHERS = 6.
If sy-subrc = 0.
Calling Function to Create a Session
CALL FUNCTION u2018BDC_OPEN_GROUPu2019
EXPORTING
CLIENT = SY-MANDT
GROUP = u2018POTHURIu2019
HOLDDATE = DATE1
KEEP = u2018Xu2019
USER = SY-UNAME
EXCEPTIONS
CLIENT_INVALID = 1
DESTINATION_INVALID = 2
GROUP_INVALID = 3
GROUP_IS_LOCKED = 4
HOLDDATE_INVALID = 5
INTERNAL_ERROR = 6
QUEUE_ERROR = 7
RUNNING = 8
SYSTEM_LOCK_ERROR = 9
USER_INVALID = 10
OTHERS = 11.
If sy-subrc = 0.
*-- MAIN Logic--
LOOP AT ITAB
PERFORM GENERATE_DATA. u201C Populating BDCDATA Table
CALL FUNCTION u2018BDC_INSERTu2019
EXPORTING
TCODE = u2018TFBAu2019
TABLES
DYNPROTAB = BDCTAB
EXCEPTIONS
INTERNAL_ERROR = 1
NOT_OPEN = 2
QUEUE_ERROR = 3
TCODE_INVALID = 4
PRINTING_INVALID = 5
POSTING_INVALID = 6
OTHERS = 7.
REFRESH BDCTAB
ENDLOOP.
Calling function to close the session
CALL FUNCTION u2018BDC_CLOSE_GROUPu2019
EXCEPTIONS
NOT_OPEN = 1
QUEUE_ERROR = 2
OTHERS = 3.
Endif.
Endif.
*& Form GENERATE_DATA
Create BDC Data
FORM GENERATE_DATA
Passing information for 1st screen on BDCDATA
BDCTAB-PROGRAM = u2018SAPMTFBAu2019.
BDCTAX-DYNPRO = 100.
BDCTAP-DYNBEGIN = u2018Xu2019.
APPEND BCDTAB.CLEAR BDCTAB.
Passing field information to BDCDATA
BDCTAB-FNAM = u2018SCUSTOM-IDu2019
BDCTAB-FVAL = ITAB-ID.
APPEND BDCTAB.CLEAR BDCTAB.
Passing BDC_OKCODE to BDCDATA
BDCTAB-FNAM = u2018BDC_OKCODEu2019.
BDCTAB-FVAL = u2018/5u2019.
APPEND BDCTAB.CLEAR BDCTAB.
Passing screen information for next screen to BDCDATA
BDCTAB-PROGRAM = u2018SAPMTFBAu2019.
BDCTAB-DYNPRO = 200.
BDCTAB-DYNBEGIN = u2018Xu2019.
APPEND BDCTAB.CLEAR BDCTAB.
Passing screen information to BDCDATA
BDCTAB-FNAM = u2018SCUSTOM-NAMEu2019.
BDCTAB-FVAL = ITAB-NAME.
APPEND BDCTAB.CLEAR BDCTAB.
Passing screen information to BDCDATA
BDCTAB-FNAM = u2018SCUSTOM-CITYu2019.
BDCTAB-FVAL = ITAB-CITY.
APPEND BDCTAB.CLEAR BDCTAB.
Passing BDC_OKCODE to BDCDATA
BDCTAB-FNAM = u2018BDC_OKCODEu2019.
BDCTAB-FVAL = u2018SAVEu2019.
APPEND BDCTAB.CLEAR BDCTAB.
ENDFORM. u201CGENERATE_DATA
AN EXAMPLE WITH CALL TRANSACTION
Same steps to be repeated for CALL TRANSACTION
The only difference between the two types of interface is in Session method, you create session and store information about screen and data into session. When session is processed the data is transferred to database. While in CALL TRANSACTION, data is transferred directly to database table.
REPORT DEMO1.
Follow above Code till MAIN Logic. Even the Subroutine should be copied
LOOP AT ITAB
PERFORM GENERATE_DATA, u201CPopulating BDCDATA Table
Call transaction u2018TFBAu2019 using BCDDATA Mode u2018Au2019 Update u2018Su2019.
REFRESH BDCTAB
ENDLOOP.

Error while installing NW7.3 ABAP for DB2 on z/OS Install DB CLI driver

Dear Experts,
i'm installing for the first time NW7.3 ABAP for DB2 on z/OS with AIX application server. Central Services was installed succesfull but next step Install Database on AIX stoped with error (establishConn.log):
db2radm (release: "720", patch level: "000", version: "Jan 14 2012") begin:28.02.2012 10:54:39
This is db2radm release: "720", patch level: "120", version: "Jan 14 2012".
This is db2radm setting up DB2 Connect.
Message file is /sapmnt/tmp/sapinst_instdir/NW73/INSTALL/NW73/DB2/HA/PI/DB/establishConn.log.
db2radm called as: /usr/sap/DW8/SYS/exe/uc/rs6000_64/db2radm -m db2i -P 456 -L DW8DDF -S DW88 -H s10d1 -u SAPADM -p ******** -W primary_only -l /sapmnt/tmp/sapinst_instdir/NW73/INSTALL/NW73/DB2/HA/PI/DB/establishConn.log
Adjusting environment
dbs_db2_ssid=DW88
SAPDBHOST=s10d1
dbs_db2_user=SAPADM
dbs_db2_schema=SAPADM
dbs_db2_schema8=1
dbs_db2_pw=********
Checking environment
DB host    = s10d1
SSID       = DW88
SAPSYSTEMNAME = DW8
DB2Trc:    000000 CLI_ALLOC_ENV 1
connect.ini file used: 'connect.ini.for.db2radm'
Fail over connection list of this application server:
NAME       = DW88_on_s10d1
USER       = SAPADM
PASSWORD   = <***>
SCHEMA     = SAPADM
PS         = SAP0907U
LOCATION   = DW8DDF
SSID       = DW88
HOST       = s10d1
PORT       = 456
RETRY_CNT = 3
SLEEP_TIME = 0
DB2Trc: trace level of dbdb2cli set to 1
COLLECTION ID used is "SAP0907U"
DB2 Call 'SQLDriverConnectW' Warning: SQLCODE = 8007 : [IBM][CLI Driver][DB2] SQL8007W There are "90" day(s) left in the evaluation period for the product "DB2 Connect". For evaluation license terms and conditions, refer to the License Agreement document located in the license directory in the installation path of this product. If you have licensed this product, ensure the license key is properly registered. You can register the license via the License Center or db2licm command line utility. The license key can be obtained from your licensed product CD. SQL
use lib_dbsl for DB2 version V9.
Callback functions for dynamic profile parameter registered
DbSl library successfully loaded.
WARNING: schema with 8 bytes length allowed; shadow upgrate will not work
dbs/db2/use_accounting != 1 -> DB2 accounting is switched off
dbs/db2/use_drda_lob_handling != 1 -> SAP LOB handling is used
dbs/db2/chaining = 20 -> CLI CHAIN optimization is switched on
dbs/db2/opt2_hint = 1 -> implicit 'optimize for 1 rows' hint is switched off
SQL DRIVER VERSION is "09.07.0003"
DB2Connect driver identified as THIN CLIENT
Now I'm connected to DW88_on_s10d1
DB2 DBMS version 09.01.0005
DB2 LOCATION name DW8DDF
(HYB): Info: Using OLD dbsl support.
DB2 connect shared library loaded successfully.
09.07.0003DB2Connect driver identified as THIN CLIENT
WARNING: schema with 8 bytes length allowed; shadow upgrate will not work
dbs/db2/use_accounting != 1 -> DB2 accounting is switched off
dbs/db2/use_drda_lob_handling != 1 -> SAP LOB handling is used
dbs/db2/chaining = 20 -> CLI CHAIN optimization is switched on
dbs/db2/opt2_hint = 1 -> implicit 'optimize for 1 rows' hint is switched off
DBSLHA: Got Failover profile /usr/sap/DW8/SYS/global/connect.ini
DBSLHA: Using new Failover Support
DBSLHA: Using user( SAPADM) and password(<pwd>) from profile.
DBSLHA:
DBSLHA:Connection List
DBSLHA:
DBSLHA:NAME      |HOST      |SSID|COLLECTION |PLAN    |PORT             |SCHEMA |OWNER   |LOCATION |RETRY|SLEEP|
DBSLHA:--|||||||||-|---|
DBSLHA:DW88_on_s1|s10d1     |DW88|SAP<DB2Conne|        |                 |SAPADM |SAPADM |DW8DDF    |00003|00000|
DBSLHA:--|||||||||-|---|
GetHaProfile: GetHaProfile: found 1 connections in connection profile.
GetHaProfile: found section DW88_on_s10d1, ssid DW88, port 456, location DW8DDF, host s10d1 in connection profile
connection profile /usr/sap/DW8/SYS/global/connect.ini opened.
>>>>>> dump of connection profile
ADDED 20120228 103331 by DB2RADM RELEASE 720 PATHLEVEL 000
[DEFAULT_GROUP]
CON1=DW88_on_s10d1
[DW88_on_s10d1]
SSID=DW88
HOST=s10d1
PORT=456
LOCATION=DW8DDF
<<<<<< end of dump of connection profile
ssid DW88 found in connection profile, section DW88_on_s10d1.
>>> analyse line: * ADDED 20120228 103331 by DB2RADM RELEASE 720 PATHLEVEL 000
>>> analyse line: [DEFAULT_GROUP]
>>> analyse line: CON1=DW88_on_s10d1
>>> analyse line:
>>> analyse line: [DW88_on_s10d1]
section DW88_on_s10d1 found.
>>> analyse line: SSID=DW88
>>> analyse line: HOST=s10d1
>>> analyse line: PORT=456
>>> analyse line: LOCATION=DW8DDF
>>> analyse line: section DW88_on_s10d1 found and data matches.
backup connection profile /usr/sap/DW8/SYS/global/connect.ini .
switch connection profile /usr/sap/DW8/SYS/global/connect.ini .
check for adapted connection profile.
WARNING: schema with 8 bytes length allowed; shadow upgrate will not work
dbs/db2/use_accounting != 1 -> DB2 accounting is switched off
dbs/db2/use_drda_lob_handling != 1 -> SAP LOB handling is used
dbs/db2/chaining = 20 -> CLI CHAIN optimization is switched on
dbs/db2/opt2_hint = 1 -> implicit 'optimize for 1 rows' hint is switched off
DBSLHA: Got Failover profile /usr/sap/DW8/SYS/global/connect.ini
DBSLHA: Using new Failover Support
DBSLHA: Using user( SAPADM) and password(<pwd>) from profile.
DBSLHA:
DBSLHA:Connection List
DBSLHA:
DBSLHA:NAME      |HOST      |SSID|COLLECTION |PLAN    |PORT             |SCHEMA |OWNER   |LOCATION |RETRY|SLEEP|
DBSLHA:--|||||||||-|---|
DBSLHA:DW88_on_s1|s10d1     |DW88|SAP<DB2Conne|        |                 |SAPADM |SAPADM |DW8DDF    |00003|00000|
DBSLHA:--|||||||||-|---|
GetHaProfile: GetHaProfile: found 1 connections in connection profile.
GetHaProfile: found section DW88_on_s10d1, ssid DW88, port 456, location DW8DDF, host s10d1 in connection profile
ssid DW88 found in connection profile, section DW88_on_s10d1.
check for adapted connection profile passed.
WARNING: schema with 8 bytes length allowed; shadow upgrate will not work
dbs/db2/use_accounting != 1 -> DB2 accounting is switched off
dbs/db2/use_drda_lob_handling != 1 -> SAP LOB handling is used
dbs/db2/chaining = 20 -> CLI CHAIN optimization is switched on
dbs/db2/opt2_hint = 1 -> implicit 'optimize for 1 rows' hint is switched off
DBSLHA: Got Failover profile /usr/sap/DW8/SYS/global/connect.ini
DBSLHA: Using new Failover Support
DBSLHA: Using user( SAPADM) and password(<pwd>) from profile.
DBSLHA:
DBSLHA:Connection List
DBSLHA:
DBSLHA:NAME      |HOST      |SSID|COLLECTION |PLAN    |PORT             |SCHEMA |OWNER   |LOCATION |RETRY|SLEEP|
DBSLHA:--|||||||||-|---|
DBSLHA:DW88_on_s1|s10d1     |DW88|SAP<DB2Conne|        |                 |SAPADM |SAPADM |DW8DDF    |00003|00000|
DBSLHA:--|||||||||-|---|
GetHaProfile: GetHaProfile: found 1 connections in connection profile.
GetHaProfile: found section DW88_on_s10d1, ssid DW88, port 456, location DW8DDF, host s10d1 in connection profile
WARNING: schema with 8 bytes length allowed; shadow upgrate will not work
dbs/db2/use_accounting != 1 -> DB2 accounting is switched off
dbs/db2/use_drda_lob_handling != 1 -> SAP LOB handling is used
dbs/db2/chaining = 20 -> CLI CHAIN optimization is switched on
dbs/db2/opt2_hint = 1 -> implicit 'optimize for 1 rows' hint is switched off
DBSLHA: Got Failover profile /usr/sap/DW8/SYS/global/connect.ini
DBSLHA: Using new Failover Support
DBSLHA: Using user( SAPADM) and password(<pwd>) from profile.
DBSLHA:
DBSLHA:Connection List
DBSLHA:
DBSLHA:NAME      |HOST      |SSID|COLLECTION |PLAN    |PORT             |SCHEMA |OWNER   |LOCATION |RETRY|SLEEP|
DBSLHA:--|||||||||-|---|
DBSLHA:DW88_on_s1|s10d1     |DW88|SAP<DB2Conne|        |                 |SAPADM |SAPADM |DW8DDF    |00003|00000|
DBSLHA:--|||||||||-|---|
SQL DRIVER VERSION is "09.07.0003"
DB2Connect driver identified as THIN CLIENT
DB2Trc: 00 000000 cli_get_cli_driver_bld_level 1 s101006
SQL DRIVER NAME is "libdb2.a"
SQL DBMS NAME is "DB2"
SQL DBMS VERSION is "09.01.0005"
DATABASE NAME(DB2 Connect DCS database name) is "DW8DDF"
The bind is skipped since collection for ssid DW88 is already bound.
To force the bind, use option "-B force".
DB2TRC: 0000000000 00      000000   CLI_DISCONNECT
DB2TRC: 0000000000 00      000000   CLI_FREE_DBC 1
DB2TRC: 0000000000 00      000000   CLI_FREE_ENV 1
DB VERSION is 09.01.0005.
Starting Grants .
DB2Trc:    000000 CLI_ALLOC_ENV 1
COLLECTION ID used is "SAP0907U"
DB2 Call 'SQLDriverConnectW' Warning: SQLCODE = 8007 : [IBM][CLI Driver][DB2] SQL8007W There are "90" day(s) left in the evaluation period for the product "DB2 Connect". For evaluation license terms and conditions, refer to the License Agreement document located in the license directory in the installation path of this product. If you have licensed this product, ensure the license key is properly registered. You can register the license via the License Center or db2licm command line utility. The license key can be obtained from your licensed product CD. SQL
Connecting to <DW88_on_s10d1> on connection 0 ...
Now I'm connected to DB2 (09.01.5)
SQL DRIVER NAME is "libdb2.a"
SQL DBMS NAME is "DB2"
SQL DBMS VERSION is "09.01.0005"
DATABASE NAME(DB2 Connect DCS database name) is "DW8DDF"
New functions of DB2 V9 are switched on
Profile parameter dbs/db2/cli_trace_dir is not set
dbdb2dic.c 1709 INFO    Profile: SDB2_DEBUG=<UNSET>
dbdb2dic.c 1733 INFO    Envrmnt: sdb2_debug=<UNSET>
dbdb2dic.c 1733 INFO    Envrmnt: SDB2_DEBUG=<UNSET>
DB2 Call 'CLI_EXECUTE' Error: sqlcode = -204 : [IBM][CLI Driver][DB2] SQL0204N "SAPADM.#LOBU" is an undefined name. SQLSTATE=42704
dbdb2dic.c 2251 INFO    rc=103,sqlcode=-204: ExeRead
dbdb2dic.c 1709 INFO    Profile: dbs/db2/max_retry=<UNSET>
dbdb2dic.c 1733 INFO    Envrmnt: DB2_MAX_RETRY=<UNSET>
dbdb2dic.c 1709 INFO    Profile: dbs/db2/retry_on_924=<UNSET>
dbdb2dic.c 1733 INFO    Envrmnt: DB2_RETRY_ON_924=<UNSET>
dbdb2dic.c 1709 INFO    Profile: dbs/db2/no_retry_on_10=<UNSET>
dbdb2dic.c 1733 INFO    Envrmnt: dbs_db2_no_retry_on_10=<UNSET>
dbdb2dic.c 1733 INFO    Envrmnt: DBS_DB2_NO_RETRY_ON_10=<UNSET>
DB2 Call 'SQLEndTran' Error: sqlstate = 08003 : [IBM][CLI Driver] CLI0106E Connection is closed. SQLSTATE=08003
[dbdb2dic.c 1873:rc=99: COMMIT WORK failed]
dbdb2dic.c 1873 ERROR   rc=99: COMMIT WORK failed
[dbdb2dic.c 2019:rc=99,sqlcode=268435455: ExecDDL failed (DB error)]
dbdb2dic.c 2019 ERROR   rc=99,sqlcode=268435455: ExecDDL failed (DB error)
DB2 Call 'SQLEndTran' Error: SQLCODE = -99999 : [IBM][CLI Driver] CLI0106E Connection is closed. SQLSTATE=08003
ROLLBACK failed with SQL error '-99999'
ERROR: couldn't connect to DB
rc = 99
error message returned by DbSl:
rc=99,sqlcode=268435455: ExecDDL failed (DB error)
DB2RADM EXITCODE: 12
db2radm finished (0012)
db2radm stop:28.02.2012 10:54:39
i've patched db2radm and sapinst to the latest version.
May be i should manually create "SAPADM.#LOBU"?
Please help to solve these issue.
Best regards,
Alexander V

Hi ,
Please check if Note 1581637 - Installing a System with DB2CODEPAGE other than the default is useful.
Award points if useful.
Thanks,
Ravi

Functional specs for BDC

Kindly can ayone helo me out in prepare Functional specs for BDC For f-28

Hi
There is no need of preparing FS (Functional Specs) for BDC.
You can Record the BDC and just give the Recording Name to the ABAP Guy, he will prepare the BDC based on that recording.
Go to SHDB and do the Recording.
Regards
Venkat

BCD FOR BDC ?

Hi Moderators,
On the data transfers page there is a mistake it is printed as bcd for bdc
Expert Forums » ABAP Development » Data Transfers
Forum: Data Transfers
LSMW, ALE, BCD - forum to discuss various Data Transfer Techniques, Batch Data Communication, Legacy System Migration Workbench, Application Link Enabling, IDOCs, BAPIs.
Regards

Funny -:) Would like to help, but I don't have access to the forum internals -:(
Greetings,
Blag.

How to put a report which contains code for BDC in background

Hello Experts ,
Please provide your valuable opinions on following issue,
My BDC execution is taking longer time and it gives time out error. To avoid this problem i have created a separate report which l contains the BDC code (Call transaction ) and i have put this report for background execution. But upon doing this My BDC code is not performing the transaction call which it was performing when it was executed individually. In sm37 it shown the job that i am creating but nothing is actually happening as a result of transaction call.
The code that i have written is :
RFC code
SUBMIT ZREPORT AND RETURN.
RFC end
Z_REPORT .
PERFORM open_job.
PERFORM get_print_parameters.
PERFORM job_submit. here in Submit i have specified the another report name(zbdcreport) which contains the actual logic for bdc
PERFORM job_close.
Report END.
zbdcreport
The call transaction is as follows :
( CALL TRANSACTION TCODE USING BDCDATA
                     MODE   'N' "CTUMODE "N
                     UPDATE 'S' "CUPDATE "S
                     MESSAGES INTO MESSTAB .)
end zbdcreport
Can anybody provide the reason for the error .
Regards,
Uma

Hi
Check the code using this...
DATA: number           TYPE tbtcjob-jobcount,
      name             TYPE tbtcjob-jobname VALUE 'JOB_TEST',
      print_parameters TYPE pri_params.
CALL FUNCTION 'JOB_OPEN'
EXPORTING
    jobname          = name
IMPORTING
    jobcount         = number
EXCEPTIONS
    cant_create_job = 1
    invalid_job_data = 2
    jobname_missing = 3
    OTHERS           = 4.
IF sy-subrc = 0.
SUBMIT submitable TO SAP-SPOOL
                    SPOOL PARAMETERS print_parameters
                    WITHOUT SPOOL DYNPRO
                    VIA JOB name NUMBER number
                    AND RETURN.
IF sy-subrc = 0.
    CALL FUNCTION 'JOB_CLOSE'
      EXPORTING
        jobcount             = number
        jobname              = name
        strtimmed            = 'X'
      EXCEPTIONS
        cant_start_immediate = 1
        invalid_startdate    = 2
        jobname_missing      = 3
        job_close_failed     = 4
        job_nosteps          = 5
        job_notex            = 6
        lock_failed          = 7
        OTHERS               = 8.
    IF sy-subrc <> 0.
    ENDIF.
ENDIF.
ENDIF.

Problem during recording of CJ01 transaction for BDC

Hello All,
I am facing a problem during the recording of CJ01(Creation of projects) for creation of BDC program.
The problem is during recoding after entering the the first WBS element with level 1 and i press the '+' button to create one more WBS element with Level 2,the first WBS element with level 1 goes to the bottom of the line item table and now if try to create the WBS element with Level 2 in the first line it wont allow because of the fact that the first WBS element with level 1 is below it.
But if i enter the first WBS elemnt with level 1 in the first line and come to the next line and enter the second WBS element with level 2 it will create since Level 2 WBS is below the Level 1.But this approach cannot be used for doing a recording for BDC.
Can anyone help in this regard
Thanks in Advance
Ashish

Hi Ashish,
NW is right. It is not proper to use BDC for CJ01. You can get more control and better if you use the following function module,
1. Use BAPI_PROJECT_MAINTAIN to create project definition and WBS Structure in one go. see the documentation in the BAPI on how to use this. Post the resut in this forum if you face any problem
Ravi

ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance

hi
how to fix this error??
ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance
ORACLE instance started.OS := OEL 5.6
DB:= 11R2 single instance
kind regards

no one wrote:
hi
how to fix this error??
ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance
ORACLE instance started.OS := OEL 5.6
DB:= 11R2 single instance
kind regardsThis parameter is deprecated in Oracle 10g
This parameter determines if the background process ARCH is started. It can be set to either true or false.
Of course, it makes no sense, if this parameter is set to true if the database is running in noarchive log mode. If ARCH is started with the database being in noarchive log mode, messages like media recovery disabled will be written into the alert.log file.

Need help in writing ABAP for and Object

Hi ,
I am an ABAPer and I need a help related to BW.
As per the Client Requirement ,I need to write ABAP for object ZC_MRPAMC.
what he expects is :
0MRP_CONTROL is an attribute of 0MAT_PLANT. There can be only one 0MRP_CONTROL per 0MAT_PLANT.
Assign the attribute value of 0MRP_CONTROL to ZC_MRPAMC per 0MAT_PLANT.
How to assign value of 0MRP_CONTROL to ZC_MRPAMC per 0MAT_PLANT.
Kindly give me the steps.
Thanks.
Anu.

Hi,
U can use FM RSAU_READ_MASTER_DATA.
Give as input the info object(I_IOBJNM=0MAT_PLANT) and attribute name(I_ATTRNM=0MRP_CONTROL).
Output u will get the value of that attribute which u want(E_ATTRVAL=ZC_MRPAMC).
Hope it helps
Regards,
Rathy

ABAP for BW

Hi Folks,
Can someone point me in the right direction for ABAP Programming for BW- (generating Update routines, transfer routines and Start Routines)....is there a book or any good websites/forums which concentrates only on ABAP for BW......... Help.sap.com is no good ......
Thank You,
Southie

Hi Southei,
you can try Sams Teach Yourself ABAP-4sup®-sup in 21 Days on http://cma.zdnet.com/book/abap/index.htm
also you can try my site http://www.geocities.com/dear_jayant/abap which i have created for BW user who needs little working knowledge of ABAP. However this site is not yet completed.
or use any search engine (like google,yahoo etc) and search for "ABAP beginner" ,"ABAP Guide beginners"
Regards,
Jayant Dhawale

Best Practices in use of ABAP for SRM and/or CRM Configuration

I was wondering if there is a document that defines best practices for the use of ABAP with the installation and customization of SRM and/or CRM. Such as amount of ABAP coding typically required, and best practices around the use of ABAP for customization and configuration.
Thanks.

Hi, Johnson
Sorry, Please don't mind, you are not at right place to ask the Question like this
Please read "The Forum Rules of Engagement" before posting! HOT NEWS!!
Thanks and Regards,
Faisal

Services WD ABAP for Career and Job of ESS

Dear Experts.
We are implementing ESS with BP 1.41 and we have the following issue.
The standard ESS package only provides steps to setup the original BSPs for the services of the Area Page Career and Job :
· Candidate Profile
· Data Overview
· Profile Release
· Apply directly
· Search for jobs
· Favorites
· Applications
· Personal settings
I want that this services call the EHP4 E-recruitment WDA applications.
SAP says that may be possible adapting the ESS role to include these applications.
What are the steps what I Sould do for include this service WD ABAP for the Area of Career and Job?
Best Regards

Juan,
Please refer my answer in ESS forum
Thanks
Bala Duvvuri

How to find field name for BDC

Hi,
to find out the field name for BDC ,
1. press F1 for that field
2. click technical info
3. use SCRREN FIELD name given in Field desc for batch input.
NOw what to do if SCREEN field name in "Field desc for batch input." is not given...Even During BDC recording if we input values in those fields,values are saved in appropritae tables but not inn BDC recording fields

Hi again,
1. ABSOLUTELY Sure.
2. Container (Container Control)
   is nothing but an EMPTY control
   to place controls inside it.
    eg. Its a FRAME
    inside which, there are contros!
3. Container does not have any INPUT VALUE !
regards,
amit m.

VO Substitution : JBO-25006 : Invalid parameter value passed for source

Hello All,
I want to add 2 new fields (attribute columns) to an existing VO for which I am trying to use VO substitution. I have followed these steps.
1.     Downloaded all the class files from server to local machine
2.     Opened an OA project and extended the VO by changing sql query to add 2 attribute columns
3.     Added 2 transient VO attributes to map them to the added fields in sql query
4.     Create a BC4J substitution and imported jpx file using jpximporter
While opening the page which consisted the original VO that I extended (creditRequestsVO), I am getting below error. Appreciate if anyone can throw any light on this.
Exception Details.
oracle.apps.fnd.framework.OAException: oracle.jbo.InvalidParamException: JBO-25006: Invalid parameter value creditRequestsVO for source passed to method ViewLinkImpl.setSource. Explanation: view def mismatch
at oracle.apps.fnd.framework.webui.OAPageErrorHandler.prepareException(OAPageErrorHandler.java:1247)
at oracle.apps.fnd.framework.webui.OAPageErrorHandler.processErrors(OAPageErrorHandler.java:1435)
at oracle.apps.fnd.framework.webui.OAPageBean.processRequest(OAPageBean.java:2542)
at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:1892)
at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:536)
at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:424)
at OA.jspService(_OA.java:212)
at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:379)
at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594)
at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
at oracle.apps.jtf.base.session.ReleaseResFilter.doFilter(ReleaseResFilter.java:26)
at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15)
at oracle.apps.fnd.security.AppsServletFilter.doFilter(AppsServletFilter.java:318)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:313)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:199)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:619)
## Detail 0 ##
oracle.apps.fnd.framework.OAException: oracle.jbo.InvalidParamException: JBO-25006: Invalid parameter value creditRequestsVO for source passed to method ViewLinkImpl.setSource. Explanation: view def mismatch
at oracle.apps.fnd.framework.OAException.wrapperException(OAException.java:896)
at oracle.apps.fnd.framework.webui.OAPageErrorHandler.prepareException(OAPageErrorHandler.java:1169)
at oracle.apps.fnd.framework.webui.OAPageErrorHandler.processErrors(OAPageErrorHandler.java:1435)
at oracle.apps.fnd.framework.webui.OAPageBean.processRequest(OAPageBean.java:2542)
at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:1892)
at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:536)
at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:424)
at OA.jspService(_OA.java:212)
at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:379)
at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594)
at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
at oracle.apps.jtf.base.session.ReleaseResFilter.doFilter(ReleaseResFilter.java:26)
at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15)
at oracle.apps.fnd.security.AppsServletFilter.doFilter(AppsServletFilter.java:318)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:313)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:199)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:619)
oracle.apps.fnd.framework.OAException: oracle.jbo.InvalidParamException: JBO-25006: Invalid parameter value creditRequestsVO for source passed to method ViewLinkImpl.setSource. Explanation: view def mismatch
at oracle.apps.fnd.framework.OAException.wrapperException(OAException.java:896)
at oracle.apps.fnd.framework.webui.OAPageErrorHandler.prepareException(OAPageErrorHandler.java:1169)
at oracle.apps.fnd.framework.webui.OAPageErrorHandler.processErrors(OAPageErrorHandler.java:1435)
at oracle.apps.fnd.framework.webui.OAPageBean.processRequest(OAPageBean.java:2542)
at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:1892)
at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:536)
at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:424)
at OA.jspService(_OA.java:212)
at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:379)
at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594)
at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
at oracle.apps.jtf.base.session.ReleaseResFilter.doFilter(ReleaseResFilter.java:26)
at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15)
at oracle.apps.fnd.security.AppsServletFilter.doFilter(AppsServletFilter.java:318)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:313)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:199)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:619)
Edited by: Bhavesh J Shah on Feb 22, 2010 1:58 AM

Hi Rama,
Parameter being passted to LeadHeaderDetailsVO is not right. Check the parameter values that are being passed,wether there are right or not
Thanks
Sandeep

Build Hierarchy with nodes with ABAP for custom Infoobject

Hi,
Need to build hierarchy with nodes with abap for custom infoobject.
Thanks

Hi,
Using information from:
http://help.sap.com/saphelp_nw04/helpdata/en/fa/e92637c2cbf357e10000009b38f936/content.htm
you can bulid flat file with hierarchy data and then load in into BW...
Krzys

CPU PARAMETER in ABAP for BDC

Similar Messages

Maybe you are looking for