Handling Fialure IDocs in the Production
Hi,
Can anyone let me know, How Failed Idocs would be handled in the Production System?
Is there any IDoc specialist monitor WE02/WE05 T.Code?
Thanks,
Sekhar.J
Hi MxG,
Thanks for your Reply. We may get Status message as 51.
That means "IDoc: 0000000001230290 Status: Application document not posted".
The Reason could be as. No jurisdiction code could be determined.
I should send this message back to PI system which triggers IDoc. How can i handle this?
Thanks,
Sekhar.J
Similar Messages
-
Failed IDocs in the Production
Hi,
Can anyone let me know, How Failed Idocs would be handled in the Production System?
Thanks,
Sekhar.JHi MxG,
Thanks for your Reply. We may get Status message as 51.
That means "IDoc: 0000000001230290 Status: Application document not posted".
The Reason could be as. No jurisdiction code could be determined.
I should send this message back to PI system which triggers IDoc. How can i handle this?
Thanks,
Sekhar.J -
How the material PRT issue/receipt to the production order can be handled?
Hi PP Gurus,
For one of our clients, the handling of PRT is to be controlled with the issue/receipt for the production order.
1. What is the procedure for issue/receipt of PRT material in the SAP?
2. What is the procedure to block the PRT for the creation/release of production order when it was already assigned to the other production order during the same time?
3. The PRT is to be available automatically once the assigned production order operation is confiremd.How it can be handled in the SAP?
Appreciate your early response.
Thanks,
Reddy.Hi Ramanujam,
Thanks for your response.
1. The dies can be used for the production of Pressing, Casting and Forging etc. These dies will be managed in the stores. The stores representatives will issue the die to the shop floor for an operation of a production order.They will return back the die once the production is completed at that operation using the die. How to map this process in the SAP.
Typically, these dies can be treated as PRT materials in the SAP system.
2. OPJK configuration is not sufficient. The same PRT will be assigned to the many production orders during the same time.The system won't block with only this setting. There are some other steps involved to complete the process.
I would like to know the complete procedure with all the steps to block the PRT once it was assigned to the production order operation. The same PRT is to be available for other production orders automatically once the operation is confirmed after production. -
What are the solutions offered to handle length based or mill products?
We are on 11.5.10. Current version treats beams as each, we have 30 feet beams, 20 feet beams etc.
We do not want to set-up different items for each length of beam.
We need ability to tell we have 10 pieces of 26 feet beams in inventory.
Currently we can only tell we have 260 feet of beams.
Current solution treats it discretley. We need ability to sell length based items, receive length based items, do inventory management based on length based items.
a) What are the solutions offered by Oracle in latest releases for Length based products or for Mill products.
b) If there are any solutions offered by Oracle to handle length based or mill products, can these be back ported to Oracle 11.5.10?At the time of entering orders, item inquiry, receiving, inventory transfers etc...You can enter the lot attributes during receiving because you create a new lot number.
On Item onhand inquiry, you can enter lot context and lot attributes to limit your search to specific lots.
You may have to write personalizations on other screens.
Hope this helps,
Sandeep Gandhi -
To find out how SAP is handling language support in the standard product.
Hi All,
i have one issue like "To find out how SAP is handling language support in the standard product". Any body have the solution, please send me as soon as possible.
i am very thankful to you all in advance.
Thanks & Regards,
Nagarjuna.It would be easier to send a solution if you'd clearly defined the problem!.
SAP is built to be multilingual.
For ABAP development, to ensure that your code is able to be multilingual, you should not hard code any text that the users could see - you should instead use text elements, standard texts, OTR, message classes etc.
matt -
How to check the Production order exits
Hi Experts
Modification to processing of Command Orders & Tickets
We require a modification to the processing being performed on sales data originating from the Command Concrete system and potentially from other systems yet to come online (e.g. Pinkenba Cement plant).
The Sap process involved is ZINT_INBOUND_POLLING and within that, ZINT_CSTPORD_ROUTINES.
The problem
Currently there is an assumption that every sales order (and its deliveries) will include a product which is made to order, i.e. for which a production order will be required.
In ZINT_CSTPORD_ROUTINES, a check is made to identify the production order linked to the sales order. If there is no such production order (usually because of the customeru2019s credit status) then processing of the ticket is terminated.
This assumption would fall down if an order was to be raised (in Command) on which there is no concrete material. For example, if we sold a bag of pigment or a screed to a customer. In this case the item would be sold from stock and there would be no need for a production order.
The solution
In the routine which checks for the existence of a production order, modify the code as follows:
Inspect each item on the sales order
If (and only if) there is at least one item with a category of u201CZTACu201D then check for a production order, otherwise process the order in the usual manner.
---- ZINT_CSTPORD_ROUTINES -
*& Form process_inbound_data
Create prod. orders from ticket data extracted from the COMMAND
system. Note that large portions of the code in this routine
have been copied from the retired ZPPU_COMMAND_PRODUCTION
interface program. This was done (1) because the old code works
and (2) to save development time.
-->T_ZINT_IDATA Internal table of interface data
-->T_ZINT_PARAM Internal table of interface parameters
-->T_ZINT_MSLOG Internal table of messages
-->P_ZINT_ID Interface ID
-->P_ZINT_TY Inteface type
-->P_ZINT_IS IDOC group for interface
-->P_ZINT_DL Flag: delete IDOC group when complete
-->P_ZINT_AL Flag: run in standalone mode
-->P_ZINT_NW Flag: do not log warning messages
-->P_ZINT_SQ Interface sequence number
<--P_ZINT_RC Return code (<>0=>error)
form process_inbound_data tables t_zint_idata structure zint_idata
t_zint_param structure zint_param
t_zint_mslog structure zint_mslog
using p_zint_id type zint_id
p_zint_ty type zint_ty
p_zint_is type zint_is
p_zint_dl type zint_dl
p_zint_al type zint_al
p_zint_nw type zint_nw
p_zint_sq type zint_sq
changing p_zint_rc type zint_rc.
program is continuing .............
I WANT TO WRITE A CODING HERE **********************
CHECK IF PRODUCTION ORDER REQUIRED
IF NOT THEN GO TO PERFORM UPDATE DATA
if production order required then check
for each item on sales order item list
with item category = 'ZTAC' then
return true
next
end function
if there is no production code
these has to be check from VBAP TABLE field VBELN and PSTYV (ZTAC,ZTAN Etc)
select * from Vbap WHERE VBELN = '00000269951' and VBAP.PSTYV = 'ZTAC','ZTAN' Etc
No production order?
elseif lva_prodord is initial.
clear v_messg.
call function 'CONVERSION_EXIT_ALPHA_OUTPUT'
exporting
input = lva_filemat
importing
output = lva_filemat.
No production order found - log a warning message.
concatenate 'Production Order not be found for'
'Command order' lva_cmdord
'Material' lva_filemat
'Customer' lwa_02-customer
into v_messg separated by space.
perform write_log_entry
tables t_zint_mslog
using 'E' 'ZINT_CSTPORD_ROUTINES'
'FIND_SAP_PRODORD'
v_messg
p_zint_nw
lwa_01-ticketnumber. " RJS
continue.
endif.
Production Order WAS found... Continue creating IDOCS
lwa_hdrlevel-postg_date = lwa_01-ticketdate.
Obtain the storage location parameter value.
read table t_zint_param with key zint_fn = 'LGORT'.
if sy-subrc ne c_noerr.
perform write_log_entry
tables t_zint_mslog
using 'E' 'ZINT_CSTPORD_ROUTINES'
'PROCESS_INBOUND_DATA'
'Parameter LGORT is missing from ZINT_PARAM'
p_zint_nw
lwa_01-ticketnumber. " RJS
exit.
endif.
loop at l_it_05 into lwa_05
where ticketnumber = lwa_01-ticketnumber.
clear lwa_gm_item_create.
lva_filemat = lwa_05-material.
if lva_filemat eq lva_prodmat.
concatenate 'Command ticket-' lwa_05-ticketnumber
into lwa_hdrlevel-conf_text.
lwa_hdrlevel-conf_quan_unit = lwa_05-unitofmeasure.
lwa_hdrlevel-yield = lwa_05-quantity.
check whether the confirmed value + current delivery value is equal *
the production order qty. If the production order value is less
than the total delivered value, set final conf indicator and clear
reservations
lva_wemng = lva_wemng + lwa_05-quantity.
if lva_wemng < lva_psmng.
lwa_hdrlevel-clear_res = c_false.
lwa_hdrlevel-fin_conf = ' '.
else.
lwa_hdrlevel-clear_res = c_true.
lwa_hdrlevel-fin_conf = 'X'.
endif.
move: 'Z1BP_PP_HDRLEVEL' to t_idoc_data-segnam,
lwa_hdrlevel to t_idoc_data-sdata.
append t_idoc_data.
clear lva_formmat.
lva_formmat = lwa_05-material.
lwa_gm_item_create-material = lva_formmat.
lwa_gm_item_create-plant = lwa_03-plant.
lwa_gm_item_create-ref_date = lwa_01-ticketdate.
lwa_gm_item_create-prod_date = lwa_01-ticketdate.
lwa_gm_item_create-move_type = '101'.
lwa_gm_item_create-spec_stock = 'E'.
lwa_gm_item_create-sales_ord = lva_saleord.
lwa_gm_item_create-entry_qnt = lwa_05-quantity.
lwa_gm_item_create-entry_uom = lwa_05-unitofmeasure.
lwa_gm_item_create-orderid = lva_prodord.
lwa_gm_item_create-move_mat = lva_formmat.
lwa_gm_item_create-move_plant = lwa_03-plant.
lwa_gm_item_create-mvt_ind = 'F'.
clear t_idoc_data.
move: 'E1BP2017_GM_ITEM_CREATE' to t_idoc_data-segnam,
lwa_gm_item_create to t_idoc_data-sdata.
append t_idoc_data.
else.
clear: lva_loggr,
lva_formmat.
lva_formmat = lwa_05-material.
select single loggr into lva_loggr from marc
where matnr = lva_formmat
and werks = lwa_03-plant.
if sy-subrc ne 0.
clear v_messg.
No logistics handling group - log a warning message.
concatenate 'No logistics handling group for material'
lva_formmat
'in plant'
lwa_03-plant
into v_messg separated by space.
perform write_log_entry
tables t_ldata
using 'W' 'ZINT_CSTPORD_ROUTINES'
'PROCESS_INBOUND_DATA'
v_messg
p_zint_nw
lwa_01-ticketnumber. " RJS
clear lva_loggr.
endif.
if lwa_03-satsur eq 'T'.
lwa_e1edl21-lprio = 30.
else.
lwa_e1edl21-lprio = 20.
endif.
else.
if lwa_03-satsur eq 'T'.
lwa_e1edl21-lprio = 10.
else.
lwa_e1edl21-lprio = ' '.
endif.
endif.
lwa_e1edl21-berot = lwa_04-driver.
move: 'E1EDL21' to t_idoc_data-segnam,
lwa_e1edl21 to t_idoc_data-sdata.
append t_idoc_data.
lwa_e1edl55-qualf = '001'.
lwa_e1edl55-refnr = lva_saleord.
move: 'E1EDL55' to t_idoc_data-segnam,
lwa_e1edl55 to t_idoc_data-sdata.
append t_idoc_data.
Loop at materials - create delivery entry for each
loop at l_it_05 into lwa_05
where ticketnumber = lwa_01-ticketnumber.
clear t_idoc_data.
lwa_e1edl24-matnr = lwa_05-material.
lwa_e1edl24-werks = lwa_03-plant.
lwa_e1edl24-vfdat = lwa_01-ticketdate.
lwa_e1edl24-lfimg = lwa_05-quantity.
lwa_e1edl24-vrkme = lwa_05-unitofmeasure.
lwa_e1edl24-lgort = t_zint_param-zint_fv.
clear lva_loggr.
lva_formmat = lwa_05-material.
clear lva_loggr.
select single loggr into lva_loggr from marc
where matnr = lva_formmat
and werks = lwa_03-plant.
if sy-subrc ne 0.
No logistics handling group - log a warning message.
concatenate 'No logistics handling group for material'
lva_formmat
'in plant'
lwa_03-plant
into v_messg separated by space.
perform write_log_entry
tables t_ldata
using 'W' 'ZINT_CSTPORD_ROUTINES'
'PROCESS_INBOUND_DATA'
v_messg
p_zint_nw
lwa_01-ticketnumber. " RJS
lva_loggr = 'BBIN'.
endif.
if lva_loggr is initial.
move: 'E1EDL24' to t_idoc_data-segnam,
lwa_e1edl24 to t_idoc_data-sdata.
append t_idoc_data.
endif.
endloop.
clear: lva_xabln,
lva_vbeln,
l_vbfa.
Matching ticket against a Delivery?
select single xabln vbeln into (lva_xabln,lva_vbeln) from likp
where xabln = lwa_01-ticketnumber.
if sy-subrc = 0.
If found, does this delivery match the sales order?
select * from vbfa into l_vbfa
where vbelv = lva_saleord
and vbeln = lva_vbeln.
exit.
endselect.
endif.
No matching delivery found, or Matching delivery, but for other Sls Ord
if lva_xabln is initial
or ( lva_vbeln <> space and l_vbfa is initial ).
if not lva_saleord is initial.
perform create_delivery_idocs tables t_zint_mslog
using s_idcgp
lwa_01-ticketnumber
p_zint_nw.
else.
concatenate 'Error finding a Sales Order for ticket "'
lwa_01-ticketnumber
'" reprocess the file AFTER'
' the sales order issues have been fixed'
into lva_outtext.
perform write_log_entry tables t_zint_mslog
using 'E'
'ZINT_CSTPORD_ROUTINES'
'PROCESS_INBOUND_DATA'
lva_outtext
p_zint_nw
lwa_01-ticketnumber. " RJS
endif.
else.
concatenate 'Command Ticket "'
lwa_01-ticketnumber
'" has already been processed into delivery "'
lva_vbeln
into lva_outtext.
perform write_log_entry tables t_zint_mslog
using 'I'
'ZINT_CSTPORD_ROUTINES'
'PROCESS_INBOUND_DATA'
lva_outtext
p_zint_nw
lwa_01-ticketnumber. " RJS
refresh t_idoc_data.
endif.
endif.
refresh t_idoc_data.
Write out all messages collected so far
perform update_data tables t_zint_mslog
using p_zint_id p_zint_ty.
endloop.
Write out all messages collected so far
perform update_data tables t_zint_mslog
using p_zint_id p_zint_ty.
endform. " process_inbound_data
Thnaks
RegardsThanks
Thread closed -
IDoc Configuration for Production Order Creation and Change
Hi All,
Please Help me out for IDoc Configuration for Production Order Creation and Change
I have found the IDoc for Production Order
Messgae Type : LOIPRO and IDoc type : LOIPRO01
Actually my requirment is to send the (LOIPRO01 )IDoc from SAP R/3 to XI system ,when ever the Production Order Created and Changed,
I have done following Configurations:
1. RFC Destination created for XI system
2. PORT was created for XI
3. Partner profile created WE20 and LOIPRO01 IDoc is added in OutBound Perameter.
I need to know how to do the followning.
1. How do i configure the outbound Production order idocs when Production Order is created or changed.
2. in NACE (Output control) which is the Application for Production Order.
3. How can I set IDoc as output Type for Production Order Creation.
Thanks in advance
Dhanabal THi Michal,
I know that it is the old thread but still want to get clarified from you out of curiosity.
Unlike other IDOC, i actiavated change pointers for LOIPRO
1.message and idoc type is linked
2.function module , message type , idoc type is linked
function module used is CLOI_MASTERIDOC_CREATE_LOIPRO
3.BD64, distribution model is created and distributed
4. port and partner profile is in place.
5. IDOC is not getting generated after creating the process order.
do we need to activate the change documents for the message type in BD52,
if yes can you please provide the object types for the same.
or i am missing something else. please guide me in this regards.
Thanks in advance for your time.
S.Janagar -
Idoc creation on production order create and save
I need to know if there is a way to create an idoc on the change and save of a production order. We will need to base this on plants (not all plants get an idoc). Is there any "safe" way to do this automatically? We previous had a system in place that used the user exit of a production order save but it no longer works.
Regards,
DavisIt's not an error as such. The program is doing exactly what it has been told to do.
If you go to SE38, and look at ZXCO1U06, you'll find that there is a statement "BREAK-POINT". This is hard-coded way of opening the debugger.
Your best approach is to find the developer responsible for doing this, and ask them to change it. If this is happening outside of development system - perhaps in test or production, then perhaps
a) The programmer needs to be disciplined shot
b) The development team need to introduce some review procedure of ALL coding, before transport.
Regards
matt -
I m using SQL Server 2012 Developer Edition. Even I tried 2012 express and enterprise edition but all
gave same error. I browsed msdn blog. But nothing help me out.
Below is the error log details--
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893606
Start time: 2013-10-21 12:58:05
End time: 2013-10-21 13:52:30
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for RS: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for DQ: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for FullText: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for Replication: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Machine Properties:
Machine name: CROY-TOSH
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: C:\Users\CRoy\Downloads\SQL Server 2012 Developer Edition (x86 and x64) - DVD (English)\x64\setup\
Installation edition: Developer
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT Service\SQLSERVERAGENT
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AI
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Data
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: NT Service\MSSQLServerOLAPService
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: CRoy-TOSH\CRoy
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: ROY
CLTRESULTDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir\
CLTSTARTUPTYPE: Manual
CLTSVCACCOUNT: NT Service\SQL Server Distributed Replay Client
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir\
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\ConfigurationFile.ini
CTLRSTARTUPTYPE: Manual
CTLRSVCACCOUNT: NT Service\SQL Server Distributed Replay Controller
CTLRSVCPASSWORD: <empty>
CTLRUSERS: CRoy-TOSH\CRoy
ENABLERANU: false
ENU: true
ERRORREPORTING: true
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, BIDS, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, DREPLAY_CTLR, DREPLAY_CLT, SNAC_SDK, MDS
FILESTREAMLEVEL: 2
FILESTREAMSHARENAME: MSSQLSERVER
FTSVCACCOUNT: NT Service\MSSQLFDLauncher
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT Service\MsDtsServer110
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: SharePointFilesOnlyMode
RSSVCACCOUNT: NT Service\ReportServer
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AI
SQLSVCACCOUNT: NT Service\MSSQLSERVER
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: CRoy-TOSH\CRoy
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
Status: Passed
Feature: Client Tools Connectivity
Status: Passed
Feature: Client Tools SDK
Status: Passed
Feature: Client Tools Backwards Compatibility
Status: Passed
Feature: Management Tools - Basic
Status: Passed
Feature: SQL Server Data Tools
Status: Passed
Feature: Reporting Services - Native
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Data Quality Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Master Data Services
Status: Passed
Feature: Distributed Replay Client
Status: Passed
Feature: Distributed Replay Controller
Status: Passed
Feature: Integration Services
Status: Passed
Feature: Data Quality Client
Status: Passed
Feature: Analysis Services
Status: Passed
Feature: Reporting Services - SharePoint
Status: Passed
Feature: Reporting Services Add-in for SharePoint Products
Status: Passed
Feature: SQL Browser
Status: Passed
Feature: Documentation Components
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\SystemConfigurationCheck_Report.htmHi,
This 3rd time I followed this link. But nothing new, same error.
Can you please tell me how to do follow, I cannt do the 1st step, how to change the local system to windows level account, vice-versa. It is shown mine as
Server Configuration Manager(Local)
From here I folllowed the steps ---[I cannt insert link/image :-(]
SQL 2008/R2 setup fails with "Wait on the database engine recovery handle failed"
If I right clicked on SQL Server Service, there is no option to change the account.
Hello,
Thanks for your patience,did you tried stesp mentioned in below article
http://blogs.msdn.com/b/sqljourney/archive/2012/03/16/sql-2008-r2-setup-fails-with-quot-wait-on-the-database-engine-recovery-handle-failed-quot.aspx
To resolve it, follow these steps:-
When the installation throws this error, click on OK and allow it to proceed. It will fail for Database Engine, but the SQL Server service should have
been created. Check the Services console.
If the service is present, perform the following steps:-
1. Go to SQL Server Configuration manager, right click on the SQL Server service, and change the service account (if it is local system, give
it a windows level account, and vice-versa). It might throw a WMI error but you will see the account getting updated anyway. If not, then use the Services console. Change the account for SQL Agent as well.
Use this link to change sql server service account
http://technet.microsoft.com/en-us/library/ms345578.aspx
2. Next, try to start the service. It should come online.
3. However, you will not be able to log in to the SQL Server
4. Now stop the service and start it from the command prompt using -m -c -T3608 parameters.
5. Now try logging in to the server using admin connection from sqlcmd (sqlcmd admin:<server name>\<instance name> ...)
6. Once logged in, use the sp_addsrvrolemember '<domain\username>','sysadmin'.
Also add the builtin/administrators to the sysadmin role
7. Now stop the service from the command prompt and start it from SQL Server configuration manager
You should be able to log in to the server now.
Hope this helps someone.
Please revert if it helps or even if it does not
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers -
Exception handling in IDOC using workflows
exeception handling in idoc using workflows
i. what will be the trigerring event in case of idoc ?
ii.will it be BOR -- IDOC<message_type >?
thanks in advance
naval bhattHi Naval Bhatt,
it depends on what you would like to do, but there is an object IDOCAPPL, more information you find Objekttyp IDOC<MSGTYP>:
http://help.sap.com/saphelp_47x200/helpdata/en/04/92725546f311d189470000e829fbbd/frameset.htm
General how it works:
Objects, Events and Tasks to be Created
http://help.sap.com/saphelp_47x200/helpdata/en/78/2176d251ce11d189570000e829fbbd/frameset.htm
This is an example how the application should implement the exception handling in IDOC by using workflows.
Events for example:
- inputErrorOccurred
- inputFinished
Regards
Tibor -
I want create Idoc CONF21 for Production Order ConfirmationIdoc (In bound)
Dear All,
My Requirement is to confirm the Production Orders though Idoc in executable program.Hi Frank,
Did u check this Link on the PP confirmaitos[LINK|http://help.sap.com/saphelp_47x200/helpdata/en/12/3bbc1c504811d182c20000e829fbfe/frameset.htm]
Reg
Dsk
Edited by: DSk on Sep 14, 2010 3:44 PM -
IDOCs error in Production System
Hi Gurus,
In Production system, there is a CRM oppertunities process chain is running on hourly basis, the data was updated to DSO successfully, but for the past one week it was not updating to further processing InfoCube, there is an error.
error: Idoc Ready to be transferred to application.
Please update me step by step procedure.
ThanksHi,
Check the DataSource in RSA3, if it is working fine and able to see the data in RSA3, there is no problem in DS level, then checl the Mappings and any routines in BW for that DS, if this is also fine then check the below options.
See Dumps in ST22, SM21 also.
Check RFC Connection between ECC and BW systems, i.e. RSA1-->Source System->Right Click on Source system and Check.
You must have the following profiles to BWREMOTE or ALEREMOTE users.So add it. Bcoz either of these two users will use in background to get extract the data from ECC, so add these profiels in BW.
S_BI-WHM_RFC, S_BI-WHM_SPC, S_BI-WX_RFC
And also check the following things.
1.Connections from BW to ECC and ECC to BW in SM59
2.Check Port,Partner Profiles,and Message Types in WE20 in ECC & BW.
3.Check Dumps in ST22, and SM21.
4.If Idocs are stuck i.e see the OLTP Idoc numbers in RSMO Screen in (BW) detials tab see in bottom, you can see OLTP Idoc number and take the Idoc numbers and then goto to ECC see the status in WE05 or WE02, if error then check the log else goto to BD87 in ECC and give the Idoc numbers and execute manually and see in RSMO and refresh.
5.Check the LUWs struck in SM58,User Name = * (star) and run it and see Strucked LUWs and select our LUW and execute manually and see in RSMO in BW.
See in SDN
Re: Loading error in the production system
Thanks
Reddy -
How to re-build the Production database after failover
We have performed a failover in our environment by the below method . It was worst we are not able to bring up the production the only choice left over is failover.
We have enabled the flash back and created a checkpoint then failover.
SQL> select max(sequence#) from v$log_history;
MAX(SEQUENCE#)
9221
SQL> alter system set db_recovery_file_dest_size=14G;
System altered.
SQL> alter system set db_recovery_file_dest='/u01/oradata/flashback';
System altered.
SQL> alter database recover managed standby database cancel;
Database altered.
SQL> alter database flashback on;
Database altered.
SQL> create restore point before_open_standby guarantee flashback database;
Restore point created.
SQL> alter database activate standby database;
Database altered.
SQL> select database_role from v$database;
DATABASE_ROLE
PRIMARY
SQL> shutdown immediate;
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SQL> startup
ORACLE instance started.
SQL> select max(sequence#) from v$log_history;
MAX(SEQUENCE#)
9221 (This is the log sequence same after the failover also)
after the we have nearly some 30 log sequence are generated but it started from the no 1.
Now we need to rebuild the Production DB and to sync with the standby.. please help us with the steps and suggest some documents.Hi,
Please take a look at this http://shivanandarao.wordpress.com/2012/08/28/dataguard-failover/
SHANOJ
Handle: SHANOJ
Status Level: Newbie (5)
Registered: Feb 15, 2006
Total Posts: 154
Total Questions: *25 (21 unresolved)*
Name SHANOJ
Location Chennai - India
Occupation DBA
Biography OCP 10G, LPI, ITIL V3
If you feel your questions have been answered, then please consider closing your threads as answered by providing appropriate points rather than leaving it open. Follow the forums etiquette. -
Billing output to IDoc & reprocess the IDoc in same sys. to post FI entry
I have a requirement to send the billing output to IDoc, read the same IDoc to post a FI entry but to another company code. Please suggest how can this be acheived, and is there any other alternative to acheive the above requirement.
Thanks in advance.Hi Naga,
I have to select the records in JDBC based on different conditions each time. For example I have to select based on company code '1000' and Employee claasification 'E1' and date range. After I post these records in SAP again I want to select other records for some other company code '2000' and different business area and different dates. Basically I want to extract data multiple times based on different conditions.
-->
Such requirements cant be handle through select query of the sender...but you can handle this in the message mapping area.....you can fire a select query in the database to pick up records in a batch of 10K (do not keep any condition on this except for sorting). After the records come into PI you can send the message to your target based on the unique combination of "Company code+ Employee clasification + date range" handling this in the message mapping.
Another question is in the JDBC to IDOC scenario since the sender adapter is JDBC and the sender adapter polls depending on the duration of time ( say 60 secs ) in the adapter once after I extract the data based on a condition how do I control in such a way that the same data is not extracted again.
You can use the N--> C logic
The data records that you pick have a corresponding control table i assume. There should be a field STATUS where the initial status of record should be N.
After you pick the records this status should be made C so that only those records present in the database with status = N are picked up.
Mention the condition Status = N in the select query.
Thanks
Dhwani -
Re : How to Error Handling In Idoc /ALE.
Hi This is Arief ,
I tranfer the Data Through ALE from One Client To Other Client some of Data not Posted ......how check other client wither Data Posted or not ....
How to error Handling In IDocs.....pls Help me.......
Kind Regards
Arief .SHi
The exception handling for idocs
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7f1543d711d1893e0000e8323c4f/frameset.htm
Exception handling in File to IDoc Scenario
For RFCs
Re: Passing SAP Exceptions to a sync SOAP Call
Error Handling when using RFC
Exception Handling while Calling RFC - BPM
handle exceptions in remote function modules
Maybe you are looking for
-
How can I change security question when I don't have a rescue email address
Can anybody help me with this I don't know The answers and I don't have a rescue address is there anyway Ivan edit this with out starting a new one
-
Changing the owners name...
hey, just a little thing but is kinda annoying, anyone know how to change the name the ipod is registered to...u know when the ipod is updating in itunes it says "name Ipod"....
-
Trace the reference Standard movement type from customized movement type
Hi, In my system there are few customized movement type. Can I know which Standard movement type was used as reference to create the customized movement type.
-
Error ODCIindexstart() routine when doing a text query
Platform 8.1.5 Linux RH6.0 all applicable Ora and RPM patches applied. I created 2 indexes 1 small 150k records 1k per document the other larger 350k records 30k documents. I have no probllm indexing either text table, and I have no problem querying
-
Having problems with effects and having to unlock panels to get them to work?
I am having problems getting panels to work... the scrolling function is locked.... but when I undock the panel so it floats freely the scrolling function comes back--this happens with the effects and project panels (prbably others as well).... then