Method ACTIVATE_PDS_2005 is not availble in ECC 6 in BADI CUSLNTRTO_ADDIN
method ACTIVATE_PDS_2005 is not availble in ECC 6 in BADI CUSLNTRTO_ADDIN, is there any replacement or particular solution availble?
Please advise.
Hi Julia,
My question is different, that Method is the BADI is not availble in ECC 6.0 to implement the solution (Active x parameter).
is there any alternative method to keep this BADI in ECC 6.0 active by setting up that parameter?
The solution you suggested we already implemented in 4.7 version thats working fine, since we are upgrading into ECC 6 we are not able to find the same method in that BADI.
Thanks,
Suresh.
Similar Messages
-
MB_DOCUMENT_BADI not triggring in ECC 6.0 version
Hi All,
We are upgrading our SAP R3 from 4.6c to ECC 6.0.
In the new system, Transaction SE18 now has two options
1. Enhancement spot
2. BAdI Name
When I display my BADI MB_DOCUMENT_BADI
Attributes tab shows BAdI migrates to enhancement spot MB_GOODSMOVEMENT
When I display Enhancement spot Technical details Tab shows Enhancement Implementation Status shows "Initial".
We have implemented this BADI in our 4.6c version. And its triggering when I run MIGO transaction.
In the new system BADI is not triggering when I run the MIGO.
Above is the only difference I found in the new system when compared with our old system settings.
Can any one suggest me what all the things I need to take care to get working this BADI
Thanks,
SatishHi
Also please read this.
Business Add-In: Create a Material Document
Business add-ins when creating a material document
The enhancement MB_DOCUMENT_BADI has two methods that are called up by the same interface, though at different times. All material document data from the following tables is transferred to this business add-in:
MKPF (material document header)
MSEG (material document items)
VM07M (update data)
This data can be used in other programs, but cannot be changed.
The methods differ according to the time at which they are called up:
The method MB_DOCUMENT_BEFORE_UPDATE is called up before the FI document is created. This means that it is called up even if the program is terminated by an error during the subsequent processing. The update of data in separate tables should always be contained in function modules that are called up with the addition 'in update task'. This ensures that all the data is updated consistently.
The method MB_DOCUMENT_UPDATE is not carried out until update. This means that all updates are carried out immediately in their own tables and do not have to be contained in 'update task' in function modules. For performance reasons, you should not re-read the tables or carry out any time-consuming routines at this point.
You should always call up MB_DOCUMENT_BEFORE_UPDATE before MB_DOCUMENT_UPDATE, particularly if time is a critical factor when posting the material documents. The method MB_DOCUMENT_UPDATE is processed after the FI document numbers are called. As a result, no other FI documents can be posted until this document is completely updated.
Even if the two methods are in the same class, you cannot access the same global fields, as the methods are called up at different times and are therefore carried out in another roll area.
From the business add-in display, you can go to coding examples for both methods by choosing Goto -> Example coding -> Display
Note
The enhancement does not transfer any data to the material document, that is, you cannot change material document data before it is updated.
If this business add-in is not set up properly, it may result in an inconsistency between the documents and the stocks and between the material documents and the accounting documents. Inconsistencies like these may be caused by the following elements in the business add-in:
COMMIT WORK
Remote function call (CALL FUNCTION ... DESTINATION)
Own updates in document tables or stock tables (for example, update in tables MBEW, MARD, MSEG)
The unlocking of data (for example, via DEQUEUE_ALL)
Before the two business add-ins are called up, data is already flagged for the UPDATE. If a COMMIT WORK or a Remote Function Call is transmitted in the enhancement, these are written in the database. If another error occurs after the business add-ins are processed, you cannot carry out a complete ROLL BACK, as the data up to the COMMIT or Remote Function Call has already been written in the database. This can result in an inconsistent status (for example, material document without accounting document), which can only be repaired with considerable cost and effort.
The business add-ins are not suitable for customer-specific updates in the stock tables, as updates like these destroy the standard stock update.
Unlocking the data (for example, via DEQUEUE_ALL) is also critical, as the data that is to be updated is no longer protected from updates from external systems, and inconsistencies can result from parallel updates.
Before you activate an enhancement, check carefully that the business add-in does not contain any critical coding places.
If data inconsistencies have already occurred in your system as a result of the business add-in, remove the critical coding so that it does not cause any further inconsistencies.
Business Add-In: Change Item Data in Transaction MIGO
Use
Application component: MM-IM-GR-MIGO
The Business Add-In (BAdI) MB_MIGO_ITEM_BAdI enables you to set the storage location and item text in the transaction for goods movements ( MIGO).
The Business Add-In is called when a new item is inserted in MIGO or when an existing item is changed.
If changes are made at header-level, the Business Add-In does not run; the header data is then transferred to the external application for information.
All available header and item data is transferred from MIGO to the external application.
The determined storage location and item text of a material document item is transferred back from the external application.
Note
The Business Add-In is called in MIGO at different times. The external application must be prepared for this.
Standard settings
In the standard system, the Business Add-In is not active.
There is no default code that would run without an active implementation.
The Business Add-In is not filter-dependent.
The Business Add-In cannot be used more than once.
Activities
To activate the Business Add-In, you must create an active implementation. Do this in Inventory Management and Physical Inventory Customizing and choose the relevant activity under Maintain Customer-Exits and Business Add-Ins.
For more information about this procedure, see the SAP Library under
Basis Components -> ABAP Workbench -> Changing the SAP Standard -> Business Add-Ins -> Implementing Business Add-Ins.
Example
Storage location determination
The Business Add-In should be used for a customer-specific storage location determination.
Item text
Goods receipt for purchase order with account assignment: As the purchase order item does not have a material number, the material short text in the puchase order should be adopted as the item text.
Example of source text:
IF IS_GOITEM-MATNR IS INITIAL.
E_ITEM_TEXT = IS_GOITEM-MAKTX.
ENDIF.
If the material short text is to be adopted as the item text for all goods movements, the source text only consists of the following line:
Example of source text:
E_ITEM_TEXT = IS_GOITEM-MAKTX.
Further notes
Documentation on the BAdI method:
Change particular fields of a line (GOITEM)
ITEM_MODIFY
You can also call the documentation on the BAdI method via the menu, by carrying out the following steps:
1. Choose the tab page Interface.
2. Double-click on the relevant method.
3. Click on the right mouse button and choose Component documentation.
Change a Row from Certain Fields (GOITEM)
Functionality
The ITEM_MODIFY method makes it possible to set the storage location and item text in the transaction for goods movements ( MIGO).
The method is called if a new item is added in MIGO or if an existing item is changed.
If changes are made to the header, the method will not run; however, the header data is transferred to the external application for information.
All available header and item data is transferred from MIGO to the external application.
The external application then transfers back the determined storage location and the item text of a material document item.
Requirements
Note that the Business Add-In can run several times for each material document item if entries are changed on the entry screen, or if error messages are outputted.
Result
The storage location and item text is returned from the external application to MIGO. The item text is also saved in the accounting document.
Note:
Data is only copied into MIGO, if the corresponding fields are visible and ready for input.
Parameters
The following structures are transferred:
IS_GOHEAD: contains the header data for the goods movement
IS_GOITEM: contains the itemd ata for the goods movement
E_STGE_LOC: storage location
E_ITEM_TEXT: item text
Exceptions
None
Notes
GOITEM includes all information on an item, in other words, both business data (material number) and technical data (for example, whether or not a tab page is to be shown for an item). We recommend you only analyze the business data of an item, as the technical data may be changed due to new developments at SAP.
Documentation for Business Add-In:
BAdI in MIGO for Changing Item Data (MB_MIGO_ITEM_BADI)
<b>Also try out the BADI - MB_MIGO_BADI</b>
Business Add-In: Maintain External Detail Subscreens for Transaction MIGO
Use
Application component: MM-IM-GR; MM-IM-GI
With the Business Add-In (BAdI) MB_MIGO_BADI, you can extend the interface of the goods movements transaction ( MIGO) with additional tabstrip controls for the detailed information (detail tabstrips) and header information (header tabstrips). It is possible for an external application
to display an additional detail tabstrip with own subscreen (max. 10 lines) in MIGO
to display an additional header tabstrip with own subscreen (max. 3 lines) in MIGO
The program name, screen number and tab page text can be determined dynamically. Different screens can therefore be controlled according to the mode (for example, change mode, display mode, goods receipt, goods issue).
Pushbuttons
It is not possible to implement pushbuttons in the MIGO menu, but you can, however, implement pushbuttons directly on the external subscreen. The OK code from MIGO is forwarded to the external application so it can react.
Cursor Control
So that the cursor stays on the same subscreen after you press Continue, if it was positioned there before, the external application in the own PAI must hold the cursor positioning (on the same screen 'yes'/'no'; if 'yes', on which field), to set the cursor in PBO again.
Requirements
If you use the BAdI MB_MIGO_BADI in MIGO to update customer-own data, in addition to the material document, to the database, you should note the following:
The BAdI MB_MIGO_BADI is only active in transaction MIGO.
If you post goods movements with other transactions (for example, with MB01, MB1C, VL02N), you must ensure that customer data is also updated, if necessary.
You can do this by using the BAdI MB_DOCUMENT_BADI (Creating a material document) to post the goods movements with the transactions mentioned above.
Note that otherwise, posting the goods movements will lead to inconsistencies between SAP system data (for example, in stocks, material documents, FI documents) and customer data.
To avoid these inconsistencies, we recommend posting all goods movements with transaction MIGO.
Standard settings
In the standard system, the Business Add-In is not active.
There is no default code.
The Business Add-In is not filter-dependent.
The Business Add-In can be used more than once.
Activities
To activate the Business Add-In, you must create an active implementation. Do this in Inventory Management and Physical Inventory Customizing and choose the relevant activity under Maintain Customer-Exits and Business Add-Ins.
For more information about this procedure, see the SAP Library under
Basis Components -> ABAP Workbench -> Changing the SAP Standard -> Business Add-Ins -> Implementing Business Add-Ins.
Note that the Business Add-In can be used multiple times and therefore all active implementations are called and run through.
Create Implementations
BAdI definition MB_MIGO_BADI was created with transaction SE18.
Using transaction SE19, you can create an implementation for this BAdI. You can provide the methods with customer-defined code.
The BAdI definition can be used several times. In MIGO, five additional tabstrip control were defined for the detail screen, and five additional tabstrip controls for the header information. In other words, up to five different implementations can be created.
Recommendation
We recommend that you do not install the external application data directly in the implementation, but enclose it in function modules. You assign the screen with the subscreens to the corresponding function group; see the example implementation.
Example
For easier comprehension, an example code has been created for the BAdI MB_MIGO_BADI. The example implementation class isCL_EXM_IM_MB_MIGO_BADI.
To activate the example implementation, use transaction SE19 to create a new implementation and then activate it. Copy the example code with Goto -> Sample Code -> Copy.
The tabstrip controls MIGO BAdI Example are then displayed in MIGO for the header and detail information.
On the tabstrip control for the detail information, you can enter an additional quantity (and unit of measure). Both are saved in table MIGO_BADI_EXAMPL.
The text field SGTXT can also be changed. An example shows how an external application can change the data from the GOITEM (item data in MIGO) structure.
On the tabstrip control for the header information, you can enter an additional number. This is saved in table MIGO_BADI_EXAMP2.
Further notes
Documentation for BAdI methods:
Initialization and registration of external detail screens:
INIT
PBO of detail screen
PBO_DETAIL
PAI of detail screen
PAI_DETAIL
Insert / change line (GOITEM)
LINE_MODIFY
Delete line (GOITEM)
LINE_DELETE
MIGO reset (delete all internal data)
RESET
Post a goods movement
POST_DOCUMENT
Check item data for goods movement
CHECK_ITEM
Mode of transaction MIGO (action, reference document, etc.)
MODE_SET
Status information and header data
STATUS_AND_HEADER
Save held data
HOLD_DATA_SAVE
Load held data
HOLD_DATA_LOAD
Delete held data
HOLD_DATA_DELETE
PBO of header screen
PBO_HEADER
PAI of header screen
PAI_HEADER
Check item data for goods movement
CHECK_HEADER
You can also call the documentation on the BAdI method via the menu, by carrying out the following steps:
1. Choose the tab page Interface.
2. Double-click on the relevant method.
3. Click on the right mouse button and choose Component documentation.
Hope this will help.
Please reward suitable points.
Regards
- Atul -
Migrated BADI Implementation not triggering in ECC 6.0
Hi Experts,
Need your urgent assistance how to deal with migrated BADI implementation which is not triggering in ECC 6.0. This is for PO (ME_PROCESS_PO_CUST). In the original version (4.6) it was working fine. But when this is migrated to ECC 6.0, it's not firing. Please help to trigger this one in ECC 6.0.
Points will be awarded and thanks in advance,
LMHi LM,
Can you just paste the code in the BADI.(The method in which code is there)
Is this BADI implemented and in the Active status.
Check in SE19 if the implementation exist or not?
There may be chances that some condition is not met which can trigger this BADI. Have you read the documentation of the BADI?
Regards,
Atish -
Function Download not support in ECC 6.0
Dear All ,
Now i faced the problem when upgrade my coding to ECC6.0 , my current program is using Call funtion "Download" to export the report data to Excel, but this "Download" function is not support in ECC 6.0 , they suggest me to use call function "GUI_dowload", but this function cannot give me the features like "Donwload" funtion . Any others function which can use in ECC 6.0 and same features like "Download" .
ThanksThose functions are obsolete, ([Note 594356 - Function modules ws_upload and ws_download are obsolete|https://service.sap.com/sap/support/notes/594356])
Use news FM GUI_DOWNLOAD or class CL_GUI_FRONTEND_SERVICES method GUI_DOWNLOAD.
Regards,
Raymond -
Payment method(s) are not allowed for this program / Program RFFOAVIS_FPAYM
Dear Friends,
In Se38 abap editor, I entered the program RFFOM100, i entered the details program run date,identification future,paying company code,payment methods T, House bank, Account Id and executed the program. I am getting the error 'Payment method(s) are not allowed for this program'.
Payment method S is not used in F110, It was not mentioned in vendor master or vendor invoice.It is not mentioned in fbzp in bank determination. When i tried to delete payment method 'S' the system shows a message Payment Method S is being used in the company code.
In the program RFFOAVIS_FPAYM, i entered the details program run date,identification future,paying company code,payment methods T, House bank, Account Id and executed the program. I am getting the error 'Program RFFOAVIS_FPAYM: No records selected'. But there open items or invoices.
Please suggest how to resolve the errors.
Regards
SridharHello,
Why are you directly executing these programs?
You will not expect these program to execute directly by going to SE38.
I would have configured the relevant payment methods in the country with DME structure or classical RFFO* programs, which in turn pick up the inherent programs at the time of running F110.
For example, if you need to generate BACS file for country GB, either you copy the GB_BACS to ZGB_BACS or use GB_BACS directly in FBZP settings.
Make sure that you have maintained OBPM1 / OBPM2 / OBPM3 and OBPM4 settings properly.
The system automatically gives the access to system RFFOAVIS_FPAYM. Prepare a variant against this program in F110. Relevant file gets generated to folder path mentioned in OBPM4 will get generated. The file get generated can be seen in AL11.
Hope this is informative and solves your issue.
Regards,
Ravi -
CRM To ECC Sold to party Communication Details Not populated in ECC
Hi All
i have one problem when we create sales order through crmd_order we need to give sold to party and ship to party numbers suppose like
8000002166 for both and status i keep as order created and in partner tab i i seem all partner funtions(sold to, ship to ,bill to, payer)with 8000002166
in header overivew i given posting date as feature date like 30-09-2013 then i try to save this order.
the order generated sucussfully but problem is i am not getting sold to party details in ECC when i check VA03 And open cretaed order in CRM and clicking on sold to party and i seem details for this but i am not getting communication details like telephone number and email id extension number.
for this sold to party we already maintained all communication details in CRM.When i open this sold to party BP i am able to see all details
didnt understand why these details not replicated to ECC?
We implemented one custom class there we implemented badi.
IF_EX_CRM_DATAEXCHG_BADI~CRM_DATAEXCH_AFTER_BAPI_FILL
i am not getting BAPI ADDRESS Table values into CT_BAPIADDR1
how can i send communciation details to ECC For sold to party?
The code part we follow like below
TYPES : BEGIN OF t_otc, " Type to create a table with the given columns.
bpid TYPE bu_partner, " variable of store processed business partner ID's
otcid TYPE bu_partner, " variable of store processed OTC ID's
otcguid TYPE bu_partner_guid, " variable of store processed OTC GUID's
address TYPE bapibus1006_address,
tel1_numbr TYPE ad_tlnmbr1,
tel1_ext TYPE ad_tlxtns1,
e_mail TYPE ad_smtpadr,
END OF t_otc.
*& V A R I A B L E S &*
DATA : lv_bp_payer TYPE bu_partner, " Variable To Cast the payer Id into BU_Partner data type.
lv_partner_fct TYPE crmt_partner_fct, " Variable To Store Partner Function Number.
lv_partner TYPE bu_partner, " Variable To Store Current Business Partner ID.
lv_process_type TYPE crmt_process_type, " Variable to Store process type.
lv_sales_org TYPE crmt_sales_org, " Variable to store sales org. name of order
lv_dis_channel TYPE crmt_distribution_channel, " Variable to store distribution channel of order.
lv_division TYPE crmt_division, " Variable to store division of sales org. data.
lv_role TYPE comt_partner_parvw, " Variable to store retrieved role from FM.
lv_role_value TYPE parvw, " Variable to store the role value of Partner Functions.
lv_otc_guid TYPE bu_partner_guid, " Variable to store OTC GUIDs for the OTC ID.
lv_otc_id TYPE kunnr. " Varaible to OTC ID revocered from Table.
DATA: lv_busspartner TYPE bapibus1006_head-bpartner,
lw_central_data TYPE bapibus1006_central,
lw_centraldata_person TYPE bapibus1006_central_person.
*& W O R K A R E A S &*
DATA : lw_address TYPE bapibus1006_address, " Work Area to store address recovered for BPID.
*Start of code change for Defect 904 Fix
lw_tel TYPE bapiadtel,
lw_email TYPE bapiadsmtp.
*End of code change for Defect 904 Fix
*& INTERNAL TABLES &*
DATA : li_otc TYPE TABLE OF t_otc, " Internal Table to Store the OTC IDs and BPS.
li_values TYPE zconst_values_t,
*Start of code change for Defect 904 Fix
li_tel TYPE STANDARD TABLE OF bapiadtel,
li_email TYPE STANDARD TABLE OF bapiadsmtp.
*End of code change for Defect 904 Fix
* F I E L D - S Y M B O L S *
FIELD-SYMBOLS: <f_orderadm> TYPE bad_orderadm_h_mess,
<f_otc> TYPE t_otc, " Field-Symbol to Read the OTC TABLE data.
<f_partner> TYPE bad_partner_mess, " Field-Symbol of Partner Table For Looping.
<f_bapiparnr3> TYPE bapiparnr3, " Field-Symbol to Store The Row of BAPIPARNR3.
<f_bapiaddr1> TYPE bapiaddr1,
<f_orgman> TYPE bad_orgman_mess, " Field-Symbol to Read the ORGMAN table.
<f_values> TYPE zcr_const_values.
*& C O N S T A N T S &*
CONSTANTS : lc_program_name TYPE progname VALUE 'ZOTC',
lc_param_payer TYPE paramname VALUE 'PAYER', " Constant to Store Payer Parameter name.
lc_ref_kind TYPE crmt_object_kind VALUE 'A',
lc_req_1 TYPE zrequest_no VALUE '1',
lc_req_2 TYPE zrequest_no VALUE '2'.
* Retrieving the general and Common Data for a Order.
READ TABLE it_bus_trans_msg-orderadm_h INDEX 1 ASSIGNING <f_orderadm>.
IF sy-subrc EQ 0.
lv_process_type = <f_orderadm>-process_type.
ENDIF.
* Reading the Orgnisation Details from ORGMAN Table.
READ TABLE it_bus_trans_msg-orgman WITH KEY ref_kind = lc_ref_kind ASSIGNING <f_orgman>.
IF sy-subrc EQ 0.
* Storing the Sales Organisational Data to find the OTC_ID.
lv_sales_org = <f_orgman>-sales_org.
lv_dis_channel = <f_orgman>-dis_channel.
lv_division = <f_orgman>-division.
ENDIF.
* Retrieving the partner function number for the payer by giving requirement no 2 and rule no 1.
CALL FUNCTION 'ZCRAN_GET_CONSTANT_VALUES'
EXPORTING
pi_program_name = lc_program_name
pi_req_no = lc_req_2
IMPORTING
po_const_values = li_values.
IF sy-subrc <> 0.
RETURN.
ENDIF.
* Reading the value for the constant with the name as PAYER.
READ TABLE li_values WITH KEY param_name = lc_param_payer ASSIGNING <f_values>.
IF sy-subrc NE 0.
RETURN.
ENDIF.
* Retrieving the Partner ID for the PAYER.
READ TABLE it_bus_trans_msg-partner ASSIGNING <f_partner> WITH KEY ref_partner_fct = <f_values>-constant_value.
IF sy-subrc EQ 0.
* Storing the current partner ID.
lv_bp_payer = <f_partner>-ref_partner_no.
ENDIF.
REFRESH li_values.
* Retrieving the Partner Function Number which are to be checked for replacing with the OTC ID with request no 1 and rule no 01.
CALL FUNCTION 'ZCRAN_GET_CONSTANT_VALUES'
EXPORTING
pi_program_name = lc_program_name
pi_req_no = lc_req_1
IMPORTING
po_const_values = li_values.
IF sy-subrc <> 0.
RETURN.
ENDIF.
* Transferring the constant value to our table for Partner Fucntion.
LOOP AT li_values ASSIGNING <f_values>.
* Read Partner table for Header data and the reference partner function retrieved.
READ TABLE it_bus_trans_msg-partner WITH KEY ref_kind = lc_ref_kind ref_partner_fct = <f_values>-constant_value ASSIGNING <f_partner>.
IF sy-subrc EQ 0.
* Storing Current Partner Function.
lv_partner_fct = <f_partner>-ref_partner_fct.
* Storing Current Partner No.
lv_partner = <f_partner>-ref_partner_no.
* Retrieving the Partner Role (R/3) for the current partner function of CRM.
CALL FUNCTIONThe problem is in the Lotus Notes security level, not in SAP.
-
G_G_IDOC_REC_ZZINCOT function module not found in ECC 5.0
i am getting the dump.
the fuction module is not presend in ECC 5.0
Runtime Errors CALL_FUNCTION_NOT_FOUND
Exceptn CX_SY_DYN_CALL_ILLEGAL_FUNC
Date and Time 04/05/2007 07:13:25
ShrtText
Function module "G_G_IDOC_REC_ZZINCOT" not found.
What happened?
The function module "G_G_IDOC_REC_ZZINCOT" was called, but cannot be
found in the Function Library.
Error in ABAP application program.
The current ABAP program "SAPLGUIF" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
is especially useful if you want to keep a particular message.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_DYN_CALL_ILLEGAL_FUNC',
was neither
caught nor passed along using a RAISING clause, in the procedure
"IDOC_INPUT_GLROLL" "(FUNCTION)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
The program "SAPLGUIF" contains a CALL FUNCTION statement. The name
of the function module to be called is "G_G_IDOC_REC_ZZINCOT".
No function module exists with the name "G_G_IDOC_REC_ZZINCOT".
All function modules are stored in the Function Library (SE37).
Possible reasons:
a) Wrong name specified. Particular attention should be paid
to upper/lower case and underscores ("_")
b) Transport error
c) If an enqueue/dequeue module has been used, the lock object
may not have been activated (ABAP Dictionary)
may not have been activated (ABAP Dictionary).
How to correct the error
Check the last transports to the R/3 System.
Is the program "SAPLGUIF" currently being changed?
If an enqueue/dequeue module is involved, is the activation
of the lock object missing in the ABAP/4 Dictionary?
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"CALL_FUNCTION_NOT_FOUND" CX_SY_DYN_CALL_ILLEGAL_FUNCC
"SAPLGUIF" or "LGUIFU05"
"IDOC_INPUT_GLROLL"
Function modules with names similar to "G_G_IDOC_REC_ZZINCOT":
G_G_IDOC_REC_COFIT
G_G_IDOC_REC_FILCT
G_G_IDOC_REC_ECMCT
G_G_IDOC_REC_GLPCT
G_G_IDOC_REC_GLT0
G_G_IDOC_REC_SECURE
G_POSTING_ZZINCOT
G_G_IDOC_SEND_COFIT
G_G_IDOC_SEND_ECMCT
G_G_IDOC_SEND_SECURE
If you cannot solve the problem yourself and you wish to send
an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
To obtain this, select in the current display "System->List->
Save->Local File (unconverted)".
2. A suitable printout of the system log
To obtain this, call the system log through transaction SM21.
Limit the time interval to 10 minutes before and 5 minutes
after the short dump. In the display, then select the function
"System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, select the Editor function "Further Utilities->
Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
The exception must either be prevented, caught within the procedure
"IDOC_INPUT_GLROLL"
"(FUNCTION)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
System environment
SAP Release.............. "640"
Application server....... "d48ix100"
Network address.......... "151.162.153.62"
Operating system......... "AIX"
Release.................. "5.3"
Hardware type............ "00C65EFD4C00"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 2
Short dump setting....... "full"
Database server.......... "d48ix100"
Database type............ "ORACLE"
Database name............ "D48"
Database owner........... "SAPR3"
Character set............ "en_US.ISO8859-1"
SAP kernel............... "640"
Created on............... "Nov 5 2006 20:46:58"
Created in............... "AIX 1 5 00538A4A4C00"
Database version......... "OCI_920 "
Patch level.............. "156"
Patch text............... " "
Supported environment....
Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
10.2.0.."
SAP database version..... "640"
Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
Memory usage.............
Roll..................... 16128
EM....................... 8379856
Heap..................... 0
Page..................... 16384
MM Used.................. 2530176
MM Free.................. 1657232
SAP Release.............. "640"
User and Transaction
Client.............. 010
User................ "OS0730"
Language key........ "E"
Transaction......... "YICUPLD "
Program............. "SAPLGUIF"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "SAPLGUIF" in "IDOC_INPUT_GLROLL".
The main program was "Y21091IRECON ".
The termination occurred in line 65 of the source code of the (Include)
program "LGUIFU05"
of the source code of program "LGUIFU05" (when calling the editor 650).
Processing was terminated because the exception "CX_SY_DYN_CALL_ILLEGAL_FUNC"
occurred in the
procedure "IDOC_INPUT_GLROLL" "(FUNCTION)" but was not handled locally, not
declared in the
RAISING clause of the procedure.
The procedure is in the program "SAPLGUIF ". Its source code starts in line 5
of the (Include) program "LGUIF$05 ".
Source Code Extract
Line SourceCde
35
36 *Prüfen, ob Customizing richtig eingestellt ist
37 CHECK EXIT IS INITIAL.
38 PERFORM CHECK_CUSTOMIZING USING IDOC_NUMBER.
39
40 *Für Einzelposten neue Belegnummern vergeben
41 CHECK EXIT IS INITIAL.
42 PERFORM NEW_DOCUMENT_NUMBER USING IDOC_NUMBER
43 IDOC_CONTRL-MESTYP.
44
45 *Füllen der Segmentdaten
46 CHECK EXIT IS INITIAL.
47 CLEAR IDOC_SEGMENT. REFRESH IDOC_SEGMENT.
48
49 LOOP AT IDOC_DATA WHERE DOCNUM EQ IDOC_NUMBER.
50 IDOC_SEGMENT = IDOC_DATA.
51 APPEND IDOC_SEGMENT.
52 ENDLOOP.
53
54 *Name des zu rufenden Funktionsbausteines ermitteln
55 ROL_FUNCNAME = 'G_G_IDOC_REC_$'.
56 PERFORM BUILD_ROL_FUNCNAME USING IDOC_NUMBER ROL_FUNCNAME.
57
58 *Funktionsbaustein zum Empfangen des IDOC's aufrufen
59 *Wenn Sender 4.0 System -> Nimm' TAB30, sonst altes TAB
60 IF NOT E1GLTTF-TAB30 IS INITIAL.
61 L_TAB30 = E1GLTTF-TAB30.
62 ELSE.
63 L_TAB30 = E1GLTTF-TAB.
64 ENDIF.
>>>>> CALL FUNCTION ROL_FUNCNAME
66 EXPORTING
67 MESTYP = IDOC_CONTRL-MESTYP
68 DOCNUM = IDOC_NUMBER
69 TAB = L_TAB30
70 TABLES
71 IDOC_SEGMENT = IDOC_SEGMENT
72 IDOC_STATUS = IDOC_STATUS
73 RETURN_VARIABLES = RETURN_VARIABLES.
74
75 ENDLOOP.
76
77 *Keine IDOC's empfangen
78 IF SY-SUBRC NE 0.
79 RAISE WF_ERROR_PROCESS.
80 ELSE.
81 *Prüfen, ob Fehler bei der Verarbeitung der IDOCs aufgetreten sind
82 LOOP AT IDOC_STATUS WHERE MSGTY = 'A'
83 OR MSGTY = 'E'.
84 EXIT.
Contents of system fields
Name Val.
SY-SUBRC 0
SY-INDEX 0
SY-TABIX 2
SY-DBCNT 1
SY-FDPOS 0
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY &I think that the FM is a customized one. Correct me if I am wrong. It is quite possible that certain FM's might have been missed out while the new system is built. Here I am assuming that the you are doing an upgrade.
If whatever, I've mentioned above is correct, you can copy the FM and its other components from the old system into the new one, to rectify the error -
Table M_VMVLB does not exist in ECC 5.0
Hi,
We found that table M_VMVLB is available in 4.6C system but not available in ECC 5.0.
Do yo have ay idea about this? Is there any other table created for this ?
Regards,
UmeshHi Umesh,
as such kind of match code tables like M_VMVLB are not longer supported by the ABAP basis, all these match code tables where replaced by normal data base tables, e.g. the content of M_VMVLB can be found in table SHP_IDX_PICK now.
General information about the changes in match codes of delivery processing can be found at the release info for 4.70 - component LE-SHP-DL.
Regards; Ulrich -
We have cycle of material or vendor creation as given below.
New vendor/material creation on portal > Approve on portal > Check in MDM data manager > PI > Check ECC > Table Entry.
In many cases we have found Materials or vendors are reflecting in MDM after approval from portal but not going in ECC.
In some cases we have observed that PI_MDM sender adapter is picking up same file twice. The data contain payload are same in both messages.
While posting these messages in ECC 1st Idoc is successful in WE05 & 2nd is throwing error u201Cvendor is locked by user ABC (our own user ID)u201D
MDM adapter in PI server is occasionally picking same XML twice from MDM ready folder & tries to post both Idocs in ECC at same time, hence at ECC system gives an error.
Kindly suggest the solution.
Regards,
GAGPlease have a look at the Note 947081, Now on a broader level
this can be achieved by the Note mentioned above.
the hierarchy of what locale a component will be shown in the portal,
will be :
1)component- if he have a locale define
2) portal mandatory locale -
3)user locale
4)browser locale
5)Portal default locale
6) system locale
if you check on the prtDefault.properties file you will see
a line with : request.defaultcountry=us . on the hierarchy it is No 5.
on your Portal it determine to 'us', so you can make the change on this
level to uk , that way the default locale will take effect only if
the locale was not determine on a higher level.
and for your question : that way
afrench user will have a french locale. because the user locale locate
on a higher level on the hierarchy.
Hope the information will help you. -
Getting "Method 'sign_in' does not exist" Error (using Charles)
This may be a bit off the FLEX field, and have to do with Zend Framework's ZEND_AMF class. Unfortunately I haven't been able to dig anything up, and comments posted on Wade Arnolds site have not received any responses, so I thought I'd give it a go here.
My ServiceController Class:
public function loginAction()
$this->_helper->viewRenderer->setNoRender();
$server = new Zend_Amf_Server();
$server->setClass('LoginAmfService', 'LoginService');
$server->setClassMap('CurrentUserVO', 'CurrentUserVO');
$server->setProduction(false);
print($server->handle());
My LoginAmfService class:
class LoginAmfService
* Main login function.
* @param string $name
* @param string $password
* @return CurrentUserVO
public function sign_in($name, $password)
$authAdapter = new Zend_Auth_Adapter_DbTable(Zend_Registry::get('db'), 'users', 'user_name', 'password', 'PASSWORD(?) AND active = 1');
$returnValue = new CurrentUserVO();
$authAdapter->setIdentity(htmlspecialchars($name))
->setCredential(htmlspecialchars($password));
$authResult = $authAdapter->authenticate();
if ($authResult->isValid())
$userArray = $authAdapter->getResultRowObject(array('id', 'first_name', 'last_name', 'title', 'photo'));
$returnValue->first_name = $userArray->first_name;
$returnValue->last_name = $userArray->last_name;
$returnValue->title = $userArray->title;
$returnValue->photo = $userArray->photo;
$returnValue->token = $userArray->id;
return $returnValue;
* Function used to log people off.
public function sign_out()
$authAdapter = Zend_Auth::getInstance();
$authAdapter->clearIdentity();
My SignIn FLEX module (the relevant portions):
<mx:RemoteObject
id="LoginRemote"
destination="login"
source="SignIn"
showBusyCursor="true"
fault="parentDocument.handleFault(event)"
>
<mx:method name="sign_in" result="signin_handle(event)" />
<mx:method name="sign_out" result="signout_handle(event)" />
</mx:RemoteObject>
<mx:Script>
<![CDATA[
import mx.rpc.events.FaultEvent;
import mx.utils.ArrayUtil;
import mx.rpc.events.ResultEvent;
import mx.controls.Alert;
import com.brassworks.ValueObjects.CurrentUserVO;
import mx.events.VideoEvent;
[Bindable]
private var this_user:CurrentUserVO = new CurrentUserVO();
private function mdl_init():void
focusManager.setFocus(txt_username);
private function signin_handle(event:ResultEvent):void
this_user = event.result as CurrentUserVO;
if (this_user.token == null) {Alert.show("Supplied login credentials are not valid. Please try again.");}
else
this.parentApplication.setUser(this.this_user);
private function signout_handle(event:ResultEvent):void
private function sign_in(event:Event):void
try
//Alert.show(txt_name.text + "|" + txt_password.text);
LoginRemote.sign_in(txt_username.text, txt_password.text);
catch (error:Error)
this.parentDocument.handleFault(error);
private function sign_out(event:Event):void
private function show_error(error:Error, s_function:String):void
Alert.show("Method:" + s_function + "\nName: " + error.name + "\nID: " + error.errorID + "\nMessage: " + error.message + "\nStack Trace: " + error.getStackTrace() + "\nError: " + error.toString());
private function handleFault(event:FaultEvent):void
Alert.show(event.fault.faultDetail, event.fault.faultString);
]]>
</mx:Script>
Now, all this is great and good, as it works with Zend Framework 1.7.6. However, when I try to upgrade to 1.7.8 (to take advantage of session management and other bug-fixes), I get the following error (using Charles):
#1 /var/web/htdocs/core/library/Zend/Amf/Server.php(390): Zend_Amf_Server->_handle(Object(Zend_Amf_Request_Http))
#2 /var/web/htdocs/core/application/default/controllers/ServicesController.php(73): Zend_Amf_Server->handle()
#3 /var/web/htdocs/core/library/Zend/Controller/Action.php(503): ServicesController->loginAction()
#4 /var/web/htdocs/core/library/Zend/Controller/Dispatcher/Standard.php(285): Zend_Controller_Action->dispatch('loginAction')
#5 /var/web/htdocs/core/library/Zend/Controller/Front.php(934): Zend_Controller_Dispatcher_Standard->dispatch(Object(Zend_Controller_Request_Http), Object(Zend_Controller_Response_Http))
#6 /var/web/htdocs/core/application/bootstrap.php(39): Zend_Controller_Front->dispatch()
#7 /var/web/htdocs/core/public/index.php(5): Bootstrap->runApp()
#8 {main} ?Method "sign_in" does not exist
I have no idea why this would not work anymore. My assumption is that I am not correctly setting up Zend_Amf (but then again, my counter-argument is that it worked before, so ..... ????)
Thanks for any help!
-MikeFor those that are also fighting this issue:
The problem appears to be that the RemoteObject needs to specify the class containing the methods as a source parameter. According to this bug report (http://framework.zend.com/issues/browse/ZF-5168) it is supposed to have been addressed, but apparently has re-emerged in Zend_Amf since version 1.7.7.
Using my example above, I would have to specify the RO as:
<mx:RemoteObject
id="LoginRemote"
destination="login"
source="LoginAmfService"
showBusyCursor="true"
fault="parentDocument.handleFault(event)"
>
<mx:method name="sign_in" result="signin_handle(event)" />
<mx:method name="sign_out" result="signout_handle(event)" />
</mx:RemoteObjecct> -
F0282 payment method(s) are not allowed to this program*
Hi.......... every one
after running app i select systems in menu bar>out put control>press enter and clicked on execute button,then i selected the log and click on the display contents button but the system is giving the error message that
f0282 payment method(s) are not allowed to this programHI,
The error message F0282 that you are receiving, is not an error but the
normal system functionality. This would be due to your customising so
please check the detailed error description provided in detail in this
reference.
For example, the detailed error description would be as below
=====================================================================
Message no. F0 282
Diagnosis
In order to avoid incorrect payment media being able to be created
with a program specified incorrectly, exactly one program is assigned
to each payment method.
System Response
The list of payment methods(T) may only be processed by other payment
medium programs. Therefore these payment methods are not processed by
program RFFOM100.
Procedure
Check the payment medium programs allowed in the country IN payment
method specifications.
=====================================================================
In customizing trans. FBZP, you have select the report that you are
going to use for the payment method. Therefore, for example if you are
using the RFFOUS_T in customising and afterwards try to use RFFOM100
separately, you will get this message so you will have to change your
customizing accordingly..
xSo please check your customising in FBZP under Payment Method/country
settings.Hope this info helps you to resolve this issue.
Regard
Madhu M -
Reg msg "Payment method(s) are not allowed for this program".
Hi...
I am copying a standard program RFFOES_T (Print program for bank transfer) into a custom program. When i try to execute the custom program it gives me a msg saying
"Payment method(s) are not allowed for this program".
Can you please Provide a solution for this problem.
Regards,
Indira.Indira,
1.RFFOES_T is using Logical database PYF.Seems you have copied it as it is without changing the attributes of the program.
2.As it is using logical database PYF it needs to be tagged to the respective payment methods in FBZP settings as below
FBZP
>>Payment methods in Country
>> in the next screen click on position and give the company code and payment method
>> in the next screen select the corresponding payment method and click on the details(ctrlshiftf2) ie magnifying glass icon
>>in the next screen within Payment Medium you will get to see two radio buttons as Payment medium workbench(uses DMEE tree structure) and payment medium programs (uses the standard prog).Here in Payment medium Program either the standard prog or your zprogram should be tagged otherwise you will get the error message as you mentioned.
3.Once you tag the program in the FBZP setting to the respective payment methods,after the payment run you will be able to run the program.
4.If you don't want the program to be linked to FBZP settings then as far as my knowledge is concerned you need to avoid using logical database PYF and change the entire code using the regular database tables like reguh,regup,bkpf,bseg etc.(I think this should be the best approach)
Thanks,
K.Kiran. -
Limit PO price changes are not replicated to ECC backend
Hi all,
SRM 5.0 ECS SP13.
When I change the value(increase/decrease) in limt PO which is already created(PO is changed for first time) and order the PO,under Overview screen.,the PO total value(at header level) shows the correct changed /new value while at the Item level,the Net price is shown as the old value!However when I go and check the item details,the field "VALUE" and "EXPECTED VALUE" have the changed/new value.
Because of the above issue,the PO changes are not replicated to ECC backend system.When I tested the BAPI BAPI_PO_CHANGE1 with the test data,there is no error mesasge in ECC backend system.
After this,when I change the PO for second time(again value increase/descrease),the total value and net price is shown correctly in SRM and changes are also replicated to ECC backend system!
I have also checked the cong for SPOOLPARAMETERS under Set Control Parameters and eveything is set correctly as shown below
SPOOL_JOB_USER User that execueds spool job. CUA_ADMIN
SPOOL_LEAD_INTERVAL intervall by which the retrytime incr. 60
SPOOL_MAX_RETRY Max. number of retrys for writing BAPIS 10
Can someone throw some pointers how to resolve the above issue.
Thanks in advance.Hi
can you recreate the same issue
are you saying that
1. create a limit po for 100 USD and replicated to ECC AS 100 USD total value.
2 . now update the PO in SRM 150 USD and it was not replicated to ECC ?
or
1. limit sc
2. Limit PO
3. update not reached ECC.
Note 1284361 - Limits not transferred to backend purchase order
Symptom
Extended classic scenario.
You have ordered a purchase order with more than one hierarchy item containing a limit.The purchase order is created or updated in the backend system without errors but the limits are missing in the backend purchase order. -
Copying a Payment method to another not working.
Hi guys,
I want to copy the payment method check C to a different one.
I copied and did all the config steps in FBZP. But When i run the payment run using payment method C, it is working.
But it is giving me error when i am using the copied payment method. Is there some thing else that is missing here.
Thanks
Srikanth.Hi Srikanth,
First I would like to tell if u copy a payment method and do not want check printing, then in F110 do not select the 5th tab or else u can remove the RFFOUS_C payment program in the copied payment method in FBZP.
coming to error as company xyz is not present, that error is only because there are no open items present for processin ur payments for the given vendor.
See, copying a payment method and after doing required configurations in FBZP, I am 100% sure that F110 runs fine without error.
Please check thoroughly by comparing the original payment method configurations with the copied ones.
Your Problem will be solved.
regards
srikath. -
The method getBean() is not valid for metadata object /ex/model/remittance/client/common/bc4j.xcfg
Hi,
I am getting bellow error when i am running my application. I am using JDeveloper 11.1.2.3
<Nov 6, 2013 9:52:57 AM AST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Nov 6, 2013 9:52:57 AM AST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<BC4JConfigLifeCycleCallBack> <contextInitialized> MDS-01702: The method getBean() is not valid for metadata object /ex/model/remittance/client/common/bc4j.xcfg - it is allowed on only bean metadata objects.
oracle.mds.exception.MDSRuntimeException: MDS-01702: The method getBean() is not valid for metadata object /ex/model/remittance/client/common/bc4j.xcfg - it is allowed on only bean metadata objects.
at oracle.mds.core.MetadataObject.getBean(MetadataObject.java:327)
at oracle.adf.share.jndi.MDSBackingStore.getMOBean(MDSBackingStore.java:558)
at oracle.bc4j.mbean.RuntimeMXBeanImpl.init(RuntimeMXBeanImpl.java:120)
at oracle.bc4j.mbean.RuntimeMXBeanImpl.<init>(RuntimeMXBeanImpl.java:110)
at oracle.bc4j.mbean.RuntimeMXBeanImpl.<init>(RuntimeMXBeanImpl.java:101)
at oracle.bc4j.mbean.BC4JConfigLifeCycleCallBack.contextInitialized(BC4JConfigLifeCycleCallBack.java:114)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1872)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
<Nov 6, 2013 9:53:11 AM AST> <Notice> <LoggingService> <BEA-320400> <The log file C:\Users\maroof\AppData\Roaming\JDeveloper\system11.1.2.3.39.62.76.1\DefaultDomain\servers\DefaultServer\logs\DefaultDomain.log will be rotated. Reop
I seen oracle docs solution
MDS-01702: The method getBean() is not valid for metadata object {0} - it is allowed on only bean metadata objects.
Cause: An attempt was made to access the metadata object using the bean API but the metadata object was not a bean metadata object. The schema for the root element may not have been registered with MDS, or the beans were not available on the classpath.
Action: Regenerate the beans from the schema definitions and ensure that the correct versions are on the classpath. Check that the schemas are registered with the MDS instance.
Level: 1
Type: ERROR
Impact: Configuration
But i am not getting what i do in my application for removing this error.
MaroofDo you use MDS in your application?
It's possible that you see a leftover of an earlier deployment.
Do you get the same error if you only start the integrated server (application server navigator->integrated server->debug or run)?
IF you don't get it when you only start the server without running your application, the problem is somewhere in your app. If you get the error it's probably an old deployment or a configuration error of your server. In this case stop jdev, rename the DefaultDomain folder C:\Users\maroof\AppData\Roaming\JDeveloper\system11.1.2.3.39.62.76.1\DefaultDomain tp C:\Users\maroof\AppData\Roaming\JDeveloper\system11.1.2.3.39.62.76.1\xxxDefaultDomain and start jdev again. Then use hte application server navigator to create a new integrated server (you should see this option as the DefaultDomain folder is not present) and once the new integrated server is created test again.
Timo
Maybe you are looking for
-
Issues with changing connection at run-time
Post Author: dmazourick CA Forum: Data Connectivity and SQL Weu2019ve tried a lot of different ways to resolve this issue, but are getting every time the different result. Probably someone deal with that issue before and know how to correctly resolve
-
I cant get my iphone (5) or ipad (1) to recognize or find the apple tv on my apple tv app.
-
A while back I set up my iMac so that Chrome and mail opened up automatically at start up. I want to remove Chrome from opening automatically. I've gone to accounts -- admin account, log in items and unchecked Chrome but it still opens. What am I doi
-
Hi All, How can i fetch the name of active tab at level 1 of TLN in a variable so that i can use it in a different iView. Actually the requirement is to get the Name of active tab from TLN iView and use it in masthead iView. Please suggest. Regards,
-
Executing javascript actions from flash...
I have a flash header with my site navigation in it. I want to use this great javascript utility (loaded in the head section of my page) that dynamically loads page content, instead of reloading the whole page. This works great with static html text