Oem: import job error

i get the following message when i import any object in database.
couldn't open "d:\import.log" : no such file or directory
please help
thanks

Are you running the DataGatherer service?
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by rafael:
if i try to export/import any object of a remote database the job works fine, but if then export/import job is on local database i get the same error. I try to change all parameters and credential, always get the same error.
if i try to import an object (a table, for example) i get this error.
"@EXP_USEROLE@"."D"
"@EXP_USERNAME@"."SYSTEM"
"@EXP_MODE@"."R"
"@EXP_TYPE@"."USERS"
COULDN'T OPEN "D:\ORANT\ORA81\WORK\547125707.LOG" : NO SUCH FILE OR DIRECTORY
THANKS FOR ALL.
<HR></BLOCKQUOTE>
null

Similar Messages

Personnel Import job Error

Hi,
We found that we get this error when the system tries to process an Import Job. Could anyone kindly help out ?
An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail. An unsecured or incorrectly secured fault was received
from the other party. See the inner FaultException for the fault code and detail.   Server stack trace:     at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.ProcessReply(Message reply, SecurityProtocolCorrelationState
correlationState, TimeSpan timeout)    at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.Request(Message message, TimeSpan timeout)    at System.ServiceModel.Security.SecuritySessionSecurityTokenProvider.DoOperation(SecuritySessionOperation
operation, EndpointAddress target, Uri via, SecurityToken currentToken, TimeSpan timeout)    at System.ServiceModel.Security.SecuritySessionSecurityTokenProvider.GetTokenCore(TimeSpan timeout)    at System.IdentityModel.Selectors.SecurityTokenProvider.GetToken(TimeSpan
timeout)    at System.ServiceModel.Security.SecuritySessionClientSettings`1.ClientSecuritySessionChannel.OnOpen(TimeSpan timeout)    at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)    at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)    at System.ServiceModel.Channels.ServiceChannel.CallOpenOnce.System.ServiceModel.Channels.ServiceChannel.ICallOnce.Call(ServiceChannel
channel, TimeSpan timeout)    at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade)    at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway,
ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)    at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)    at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage
message) Exception rethrown at [0]:     at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)    at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData&
msgData, Int32 type)    at PersonnelJob.UtilityService.IUtilityService.GetStates(Boolean activeOnly)    at PersonnelJob.UtilityService.UtilityServiceClient.GetStates(Boolean activeOnly)    at PersonnelJob.Program.Main(String[]
args)      At least one security token in the message could not be validated.

Hi ValenTinaAlex,
This is a WCF Forum, are you meeting the error when using the WCF Services? If so, could you please try to post the config file in here.
Best Regards,
Amy Peng
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

PI 711 Installation: Loading of 'SAPNTAB' import package: error but no log

Hello,
I'm perfromong an installation of a SAP PI 7.11 ystem on windoows Server 2003 and Oracle 10.2 .
I've perfromed the installation of the DEV system without particular issue.
But now when tryning to install the QAS system , I can't finish the installation : Im' stuck in the import ABAP step ...
It is impossible to import the 'SAPNTAB' package. I couln't find the reason.
I've tried updating the R3load binary, rebooting the server, restarting the instalaltion from scratch but it didn't help.
Here I provide you the logs, maybe you can help me
SAPNTAB.log
E:\usr\sap\PIQ\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20110223195542
E:\usr\sap\PIQ\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/711_REL/src/R3ld/R3load/R3ldmain.c#6 $ SAP
E:\usr\sap\PIQ\SYS\exe\uc\NTAMD64\R3load.exe: version R7.11/V1.4 [UNICODE]
Compiled Dec 14 2010 22:52:23
E:\usr\sap\PIQ\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -stop_on_error -loadprocedure fast
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
(DB) INFO: SVERS deleted/truncated #20110223195543
sapinst_dev.log
Syslib info about system call. OS message 109 (The pipe has been ended.
) after execution of system call 'ReadFile' with parameter ((read end of child process output pipe)), line (403) in file (synxcpipe.cpp).
WARNING    2011-02-23 19:56:12.607
           CJSlibModule::writeWarning_impl()
Execution of the command ""C:\Program Files\sapinst_instdir\NW71\INSTALL\SYSTEM\ORA\STD\AS\sapjvm\sapjvm_5\bin\java.exe" -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.5.0_14"
Java(TM) 2 Runtime Environment, Standard Edition (build 5.1.024)
SAP Java 64-Bit Server VM (build 5.1.024, Sep 4 2008 23:21:58 - 51_REL - optU - windows amd64 - bas2:106386 (mixed mode))
Import Monitor jobs: running 1, waiting 28, completed 0, failed 0, total 29.
Loading of 'SAPNTAB' import package: ERROR
Import Monitor jobs: running 0, waiting 28, completed 0, failed 1, total 29.
TRACE      2011-02-23 19:56:12.607
Function setMessageIdOfExceptionMessage: nw.programError
ERROR      2011-02-23 19:56:12.607
           CJSlibModule::writeError_impl()
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
import_monitor.log
TRACE: 2011-02-23 19:55:42 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\NW71\INSTALL\SYSTEM\ORA\STD\AS\DDLORA.TPL' template file is started.
INFO: 2011-02-23 19:55:42 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\NW71\INSTALL\SYSTEM\ORA\STD\AS\DDLORA.TPL' template file is successfully completed.
Primary key creation: after load.
Index creation: after load.
INFO: 2011-02-23 19:55:42
Data codepage 1100 is determined using TOC file 'E:\SAPCD\51036706\DATA_UNITS\EXP1\DATA\REPOSRC.TOC' for package 'REPOSRC'.
INFO: 2011-02-23 19:55:42
Version table 'SVERS' is found in STR file 'E:\SAPCD\51036706\DATA_UNITS\EXP3\DATA\SAPNTAB.STR' from package 'SAPNTAB'.
INFO: 2011-02-23 19:55:42
Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'E:\SAPCD\51036706\DATA_UNITS\EXP3\DATA\SAPNTAB.STR' from package 'SAPNTAB'.
TRACE: 2011-02-23 19:55:42 com.sap.inst.migmon.LoadTask run
Loading of 'SAPNTAB' import package is started.
TRACE: 2011-02-23 19:55:42 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPNTAB' import package into database:
E:\usr\sap\PIQ\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -stop_on_error -loadprocedure fast
ERROR: 2011-02-23 19:55:45 com.sap.inst.migmon.LoadTask run
Loading of 'SAPNTAB' import package is interrupted with R3load error.
Process 'E:\usr\sap\PIQ\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -stop_on_error -loadprocedure fast' exited with return code -1,073,741,819.
For mode details see 'SAPNTAB.log' file.
Standard error output:
sapparam: sapargv(argc, argv) has not been called!
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
WARNING: 2011-02-23 19:56:12
Cannot continue import because not all import packages with data conversion tables are loaded successfully.
WARNING: 2011-02-23 19:56:12
1 error(s) during processing of packages.
INFO: 2011-02-23 19:56:12
Import Monitor is stopped.
Edited by: Raoul Shiro on Feb 23, 2011 8:11 PM
Edited by: Raoul Shiro on Feb 23, 2011 8:12 PM

Hello,
Thank you for your answer.
I already opened a sap cutomer call, they answered that it it not a database issue,
I restarted the installationfriom scracth , but i still got the same error :
Here is the full content of the file SAPNTAB.log
E:\usr\sap\PIQ\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20110225170643
E:\usr\sap\PIQ\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/711_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP
E:\usr\sap\PIQ\SYS\exe\uc\NTAMD64\R3load.exe: version R7.11/V1.4 [UNICODE]
Compiled Dec 22 2008 00:13:12
E:\usr\sap\PIQ\SYS\exe\uc\NTAMD64\R3load.exe -ctf I E:\SAPCD\51036706\DATA_UNITS\EXP3\DATA\SAPNTAB.STR C:\Program Files\sapinst_instdir\NW71\INSTALL\SYSTEM\ORA\STD\AS\DDLORA.TPL SAPNTAB.TSK ORA -l SAPNTAB.log
E:\usr\sap\PIQ\SYS\exe\uc\NTAMD64\R3load.exe: job completed
E:\usr\sap\PIQ\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20110225170643
E:\usr\sap\PIQ\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20110225170643
E:\usr\sap\PIQ\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/711_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP
E:\usr\sap\PIQ\SYS\exe\uc\NTAMD64\R3load.exe: version R7.11/V1.4 [UNICODE]
Compiled Dec 22 2008 00:13:12
E:\usr\sap\PIQ\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -stop_on_error -loadprocedure fast
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
(DB) INFO: SVERS created #20110225170643
Regards.
Raoul

Import job RSI_IMPORT_CCMS_JOBS is not working in Redwood Cronacle

Hi,
We are facing problems in the redwood cronacle, where in the standard import job RSI_IMPORT_CCMS_JOBS is not working. When ever we are running the script, the status of the import job goes to waiting and never gets completed. When its killed and re-run it again moves to waiting status.
Cronacle version : 7.0.4.2. Hope some one will help me out to solve this issue.
Thanks,
Arun Raghavan

Hi,
as mentioned by Anton in his previous post, the import of abaps and variants is a kind of nice to have that CPS does for you. The import of abap and variant data enables CPS to create a Script with the defaults all set and ready for you to submit. Having this data in CPS also means that when you submit your CPS SAP Script the parameter values for instance,client, abap,variant will only be a valid combination. If you remove the Script Parameter constraints for your CPS Script then you can submit your own Script (using a copy of RSI_ABAP_RUN or RSI_ABAP_RUN_PRINT but with the param constraints removed) with whatever values you like. If you enter a valid combination the SAP job will run. If invalid you'll get an error when trying to submit in SAP. Obviously the parameter constraints ideally are there to prevent this second scenario.
In terms of why the import of variants seems to hang; you haven't got variants begining with '&' have you? CPS doesn't like these 'dynamic' variants. I have had problems in the past where this is the case.
Regards,
Simon

Job Error (RUN-050406)

Hi,
we have installed Data Services Release XI 3.2 SP3 on Linux machine SUSE Linux Enterprise 10 version 64 bit, with
Tomcat 5.5 and Java JRE 5.0.
When we try to execute a simple job that should create a single flat file we receive this error from Job Error Log:
(12.2) 03-07-11 10:36:54 (E) (16840:1206227584) *RUN-050406*: |Session Job_Srv_test|Data flow DF_Load_File
                                                            Data flow <DF_Load_File> received a bad system message. Message text from the child process is
                                                            <huFFA1, ==========================================================
                                                            Please collect the following and send to Customer Support:
                                                            1. Log files(error_*, monitor_*, trace_*) associated with this failed job.
                                                            2. Exported Atl file of this failed job.
                                                            3. DDL statements of tables referenced in this failed job.
                                                            4. Data to populate the tables referenced in the failed job. If not possible, get the last few rows (or sample of them) when
                                                            the job failed.
                                                            5. Core dump, if any, generated from this failed job.
                                                            ==========================================================
                                                            >. The process executing data flow <DF_Load_File> has died abnormally. For NT, check errorlog.txt. For HPUX, check
                                                            stack_trace.txt. Also, notify Technical Support.
(12.2) 03-07-11 10:36:54 (E) (16840:1206227584) *RUN-050409*: |Session Job_Srv_test
                                                            The job process could not communicate with the data flow <DF_Load_File> process. For details, see previously logged error
                                                            <50406>.
(12.2) 03-07-11 10:36:54 (E) (16840:1206227584) *RUN-050406*: |Session Job_Srv_test|Data flow DF_Load_File
                                                            Data flow <DF_Load_File> received a bad system message. Message text from the child process is
                                                            <huFFA1, ==========================================================
                                                            Please collect the following and send to Customer Support:
                                                            1. Log files(error_*, monitor_*, trace_*) associated with this failed job.
                                                            2. Exported Atl file of this failed job.
                                                            3. DDL statements of tables referenced in this failed job.
                                                            4. Data to populate the tables referenced in the failed job. If not possible, get the last few rows (or sample of them) when
                                                            the job failed.
                                                            5. Core dump, if any, generated from this failed job.
                                                            ==========================================================
                                                            >. The process executing data flow <DF_Load_File> has died abnormally. For NT, check errorlog.txt. For HPUX, check
                                                            stack_trace.txt. Also, notify Technical Support.
We try to restart Job Server, again and again, but nothing change.
The validate of the data flow and of all the objects in the project return with no error.
From Designer we can see Job Server running successfully but we can't login in Profiler Server although is running, we have configured a Profiler Repo and an User Admin Repo in the Management Console, can't understand why the login is not successful, but i think that is not important to our problem.
We try to create another simple Job but the result it's the same..
Anyone have any ideas of the type of problem?
Thanks.

Hi:
    Please check if the SAP note below helps you in solving this issue.
1299106 - "Error: Data flow received a bad system message - in job containing Table Comparison object"
Regards,
Francisco Milán.

Loading of 'SAPSSEXC' import package: ERROR

Hi All
I am installing Solution Manager 7.0
but it prompt error when import ABAP ......
Loading of 'SAPSSEXC' import package: ERROR
Edited by: Kevin Wong on Jun 19, 2009 9:53 AM

Log of 'SAPSSEXC'
F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20090618160337
F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP
F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Jan 24 2008 01:41:39
F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe -ctf I F:\software\sap\51033518_2\EXP4\DATA\SAPSLEXC.STR C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL SAPSLEXC.TSK ORA -l SAPSLEXC.log
F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: job completed
F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20090618160337
F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20090618160337
F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP
F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Jan 24 2008 01:41:39
F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe -i SAPSLEXC.cmd -dbcodepage 4103 -l SAPSLEXC.log -stop_on_error
DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
DbSl Trace: CONNECT failed with sql error '1034'
DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
DbSl Trace: CONNECT failed with sql error '1034'
(DB) ERROR: db_connect rc = 256
DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
DbSl Trace: CONNECT failed with sql error '1034'
DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
DbSl Trace: CONNECT failed with sql error '1034'
(DB) ERROR: DbSlErrorMsg rc = 99
F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20090618160338
F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20090619095804
F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP
F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Jan 24 2008 01:41:39
F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe -i SAPSLEXC.cmd -dbcodepage 4103 -l SAPSLEXC.log -stop_on_error
DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
DbSl Trace: CONNECT failed with sql error '1034'
DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
DbSl Trace: CONNECT failed with sql error '1034'
(DB) ERROR: db_connect rc = 256
DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
DbSl Trace: CONNECT failed with sql error '1034'
DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
DbSl Trace: CONNECT failed with sql error '1034'
(DB) ERROR: DbSlErrorMsg rc = 99
F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20090619095805
F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20090619153522
F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP
F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Jan 24 2008 01:41:39
F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe -i SAPSLEXC.cmd -dbcodepage 4103 -l SAPSLEXC.log -stop_on_error
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
DbSl Trace: CONNECT failed with sql error '12541'
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
DbSl Trace: CONNECT failed with sql error '12541'
(DB) ERROR: db_connect rc = 256
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
DbSl Trace: CONNECT failed with sql error '12541'
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
DbSl Trace: CONNECT failed with sql error '12541'
(DB) ERROR: DbSlErrorMsg rc = 99
F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20090619153527
Edited by: Kevin Wong on Jun 19, 2009 9:54 AM

The SSP Timer Job Distribution List Import Job was not run.

The SSP Timer Job Distribution List Import Job was not run. Reason: Logon failure: the user has not been granted the requested logon type at this computer
We are facing the above mentioned problem . I have added the service account in backup operates and did everything like update farm credentils , update managed account etc , but still no luck . Please note that we haven't done any chnages to the account
Application pool is keeping going into stop mode when we try to access the site . Both CA and webapplication are down with the error as Service Unavailble . Please help
Srini

sounds like the account can only be used on certain COMPUTERS ("has not been granted the requested logon type
at this computer")... check active directory.
Scott Brickey
MCTS, MCPD, MCITP
www.sbrickey.com
Strategic Data Systems - for all your SharePoint needs

Sending job error message to admin by email

Hi everyone...
Anyone knows how to send job error message to admin by email? For example, if crawler failed, an email is sent to admin with the error message. I'm thinking of building windows service which run at the background and knows when a job fail and send the error message through email to admin.
Is there a better way?
Cheers,
Jefi Santoso

hi,
>>>Can this be achieved through BPM?
yes you can put your transformation step
and send step in a block and specify an exception
branch and catch all exceptions that will
occur during transformations and the send step
then you can send info from the exception branch to
any other system
you won't be able to catch the error's name
but you will be able to notify any thinrd party
about the error
more on error catching:
http://help.sap.com/saphelp_nw04/helpdata/en/33/4a773f12f14a18e10000000a114084/content.htm
Regards,
michal

AP INVOICE IMPORT시 GDF 관련 ERROR 가 날때

제품 : FIN_AP
작성날짜 : 2003-01-20
AP INVOICE IMPORT시 GDF 관련 ERROR 가 날때
====================================
PURPOSE
AP Invoice Import시 GDF 관련 Error 가 발생할 때의 해결책을 제시한다.
Problem Description
Korean Tax program을 설치하여 사용하는 고객 사이트에서 AP INVOICE IMPORT 수행시 TAX 관련한 GDF IMPORT 부분에서 ERROR 가 발생하였다.
Error Message 는 다음과 같다.
Invoic 무효한 GF_CONTEXT 컬럼 GLOBAL_ATTRIBUTE_CATEGORY 에 무효한 값
Workaround
KR TAX 프로그램에 따른 specific 한 문제이므로 global한 support를 받을 수 없고 아래와 같은 작업을 해주어야만 한다.
Solution Description
1. GDF 생성
JG_AP_INVOICE_INTERFACE GDF를 JG_AP_INVOICES와 마찬가지로 Setup한다.
2. 다음의 Package의 에서 '수정' 이란 주석이 달린 부분과 같이 수정하여 컴파일 한다.
PACKAGE BODY JG_GLOBE_FLEX_VAL
......(중략)...
IF p_calling_program_name = 'APXIIMPT' THEN --Invoice Gatewayvalidation prog
IF p_context_code IN ('JA.TH.APXIISIM.INVOICES_INTF',
'JA.TW.APXIISIM.INVOICES_FOLDER',
'JA.SG.APXIISIM.INVOICES_FOLDER',
-- 'JA.KR.APXIISIM.INVOICES_FOLDER',
'JA.KR.APXINWKB.INVOICES', -- 수정
-- 'JA.CN.APXIISIM.INVOICES_FOLDER',
-- 'JA.KR.APXIISIM.LINES_FOLDER',
-- 'JA.CA.APXIISIM.LINES_FOLDER',
'JE.BE.APXIISIM.EFT',
......(중략)...
FUNCTION reassign_context_code(
p_global_context_code IN OUT VARCHAR2) RETURN BOOLEAN IS
BEGIN
IF (p_global_context_code IS NULL) THEN
RETURN(TRUE);
ELSIF (p_global_context_code = 'JA.TH.APXIISIM.INVOICES_INTF') THEN
p_global_context_code := 'JA.TH.APXINWKB.INVOICES';
RETURN(TRUE);
ELSIF (p_global_context_code = 'JA.TW.APXIISIM.INVOICES_FOLDER') THEN
p_global_context_code := 'JA.TW.APXINWKB.INVOICES';
RETURN(TRUE);
ELSIF (p_global_context_code = 'JA.SG.APXIISIM.INVOICES_FOLDER') THEN
p_global_context_code := 'JA.SG.APXINWKB.INVOICES';
RETURN(TRUE);
-- ELSIF (p_global_context_code = 'JA.CN.APXIISIM.INVOICES_FOLDER') THEN
-- p_global_context_code := 'JA.CN.APXINWKB.INVOICES';
-- RETURN(TRUE);
-- ELSIF (p_global_context_code = 'JA.KR.APXIISIM.INVOICES_FOLDER') THEN
-- p_global_context_code := 'JA.KR.APXINWKB.AP_INVOICES';
-- RETURN(TRUE);
ELSIF (p_global_context_code = 'JA.KR.APXINWKB.INVOICES') THEN
p_global_context_code := 'JA.KR.APXINWKB.INVOICES';
RETURN(TRUE); -- 수정
-- ELSIF (p_global_context_code = 'JA.KR.APXIISIM.LINES_FOLDER') THEN
-- p_global_context_code := 'JA.KR.APXINWKB.INVOICE_DISTR';
-- RETURN(TRUE);
Reference Documents
-------------------

Code in before report getting executed but "Job error is: BIP job failed."

Customer is executing a BIP job that fires a pl/sql procedure via before report trigger. Procedure is completing successfully. But the BIP report is not getting generated. ESS process ends in error with the following error:
oracle.as.scheduler.ExecutionErrorException: ESS-07033 Job logic indicated a system error occurred while executing an asynchronous java job for request 604103. Job error is: BIP job failed.
     at oracle.as.scheduler.rp.AsyncFinalizeProcessor.processFinalizeRequest(AsyncFinalizeProcessor.java:131)
     at oracle.as.scheduler.rp.AsyncJavaSysExecWrapper.finalizeExecution(AsyncJavaSysExecWrapper.java:250)
     at oracle.as.scheduler.rp.EndpointProcessor.finalizeExecute(EndpointProcessor.java:1018)
     at oracle.as.scheduler.rp.EndpointProcessor.finalizeExecuteWrapper(EndpointProcessor.java:980)
     at oracle.as.scheduler.adapter.EndpointImpl.finalizeExecute(EndpointImpl.java:561)
     at oracle.as.scheduler.ejb.EssAppEndpointBean.finalizeExecute(EssAppEndpointBean.java:162)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
     at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
     at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
     at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
     at $Proxy197.finalizeExecute(Unknown Source)
     at oracle.as.scheduler.ejb.ESSAppEndpoint_t596cy_MDOImpl.__WL_invoke(Unknown Source)
     at weblogic.ejb.container.internal.MDOMethodInvoker.invoke(MDOMethodInvoker.java:35)
     at oracle.as.scheduler.ejb.ESSAppEndpoint_t596cy_MDOImpl.finalizeExecute(Unknown Source)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at oracle.as.scheduler.adapter.ra.rdp.RequestProcessor.invokeFinalizeExecute(RequestProcessor.java:8133)
     at oracle.as.scheduler.adapter.ra.rdp.RequestProcessor.execStage_Finalize(RequestProcessor.java:7331)
     at oracle.as.scheduler.adapter.ra.rdp.RequestProcessor.process_execute(RequestProcessor.java:4813)
     at oracle.as.scheduler.adapter.ra.rdp.RequestProcessor.dispatchHandler(RequestProcessor.java:2833)
     at oracle.as.scheduler.adapter.ra.rdp.RequestProcessor.processExecuteEvent(RequestProcessor.java:696)
     at oracle.as.scheduler.adapter.ra.rdp.RequestProcessor.processUpdateEvent(RequestProcessor.java:1345)
     at oracle.as.scheduler.adapter.ra.WorkUnitWorkerBase.processWork(WorkUnitWorkerBase.java:199)
     at oracle.as.scheduler.adapter.ra.WAWorker.run(WAWorke...
Any tips/pointers on possible issues? Could this be a template corruption?

Any reply for the above error please.I do have the same issue.
Please suggest.

Job error in external Service when printing from Google Cloud: HP Laserjet Professional P 1102w

I have set up my printer and associated it with Google Cloud Printing. I have shared the printer with my daughter who is on a chromebook. When she tries to print, the printer is there and the job is sent to ePrint bu I get an error saying: "job error in external service". No documents are able to print. Google says this is an HP problem.
I have deleted the printer on my daughters account and re-shared it and reassociated it, but this does not help. On my printers page, my daughter's google account is identified as "allowed to print". But it still doesnt work. Any ideas?
This question was solved.
View Solution.

Hello mapuche,
Welcome to the HP Support Forums!
Will the Laserjet P1102w accept an ePrint from any / all other areas? For example, if (on the Chromebook) you open an Email, forward the Email to the printers ePrint address, will it print?
Try logging into HPConnected, under Devices, click Settings> Open to Anyone.
Try sending a print via Google Cloud Print now with this setting enabled, let me know if it sends the print through. I have seen this straighten many issues out.
Would not be a bad idea to check for firmware updates on the printer too: HP LaserJet P1102w Firmware Update Utility<---A USB connection and Windows computer is needed.
Cheers,
JERENDS
I work on behalf of HP
Please click “Accept as Solution” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos Thumbs Up" to the left of the reply button to say “Thanks” for helping!

ABAP Import Phase error during Install

Hi out there. I am installing an ERP system ECC 6.0 SR3 with just the AS ABAP and ECC components. It is now on the ABAP import phase and returns the error that certain ABAP objects are failing out of the 112 objects that is processing. Current examples are : -
=============================================================================
Loading of 'SAPSDIC_2' import package: ERROR
(DB) ERROR: DDL statement failed
(CREATE INDEX "VRSX2~1" ON "VRSX2" ( "RELID" , "OBJNAME" , "VERSNO" ) )
DbSlExecute: rc = 99
(SQL error -602)
error message returned by DbSl:
=============================================================================
Loading of 'DD03L' import package: ERROR
ERROR : Execute for create index SEOSUBCO~001 on SEOSUBCO failed (dbrc=99).
(SQL error -602)
error message returned by DbSl:
SQL-Statement: CREATE INDEX "SEOSUBCO~001" ON "SEOSUBCO" ( "CLSNAME" , "CMPNAME" , "SCOTYPE" )
=============================================================================
Loading of 'SAPAPPL2_9' import package: ERROR
ERROR : Execute for create index SEOSUBCO~001 on SEOSUBCO failed (dbrc=99).
(SQL error -602)
error message returned by DbSl:
SQL-Statement: CREATE INDEX "SEOSUBCO~001" ON "SEOSUBCO" ( "CLSNAME" , "CMPNAME" , "SCOTYPE" )
=============================================================================
I wish to know how else can 1 work around this ABAP import phase with errors such as these? Is there a manual procedure I can perform for this phase during installations so to avoid these errors that come up. And then re-run the install that goes past this?
Any help will be greatly appreciated.
Thanks in advance.

Hi
Try increasing your shared pool size
login to database level
sqlplus "/as sysdba"
>show parameter shared_pool_size;
if the value is some thing aroung 150 to 200 MB increase it to 250MB
>alter sytem set shared_pool_size=250M scope=both;
Hope this will solve your problem
Regards
Uday

KDE login: Fetch Job Error

Hi,
since today I receive an error message when I log in into KDE. It says
"Fetch Job Error - Plasma Desktop Shell
Unknown Error: Unable to fetch from backend"
I have to click OK otherwise I can't use the system. After that everything works (or at least seems to).
Don't know if this is related or belong into another thread: Resume from KDEs Suspend doesn't work anymore - the screen just turns black.
Last edited by Barghest (2011-12-28 11:17:54)

This is probably caused by some stale entries in the akonadi cache for your calendars. Try to remove and re-add the calendars in korganizer, that fixed the error for me. This error was silent before, but a "fix" in 4.7.4 makes it show those annoying dialogs.

Project Server 2013 - Reporting ( Project publish ) Queue Job Error - 24006

I am trying to publish a project and getting below error
please provide me a solution your help greatly appreciated
Reporting ( Project publish ) Queue Job Error - 24006
General
Reporting message processor failed:
ReportingProjectChangeMessageFailed (24006) - Object reference not set to an instance of an object.. Details: id='24006' name='ReportingProjectChangeMessageFailed' uid='5a10ad83-4736-e311-941a-00155d0c1708' QueueMessageBody='Project
UID='eaf690a4-5fda-e211-af15-b8ac6f50f278'. PublishType='ProjectPublish'' Error='Object reference not set to an instance of an object.'.
ReportingProjectChangeMessageFailed (24006) - Object reference not set to an instance of an object.. Details: id='24006' name='ReportingProjectChangeMessageFailed' uid='e412ad83-4736-e311-941a-00155d0c1708' QueueMessageBody='Project
UID='eaf690a4-5fda-e211-af15-b8ac6f50f278'. PublishType='ProjectPublish'' Error='Object reference not set to an instance of an object.'.
ReportingProjectChangeMessageFailed (24006) - Object reference not set to an instance of an object.. Details: id='24006' name='ReportingProjectChangeMessageFailed' uid='6e15ad83-4736-e311-941a-00155d0c1708' QueueMessageBody='Project
UID='eaf690a4-5fda-e211-af15-b8ac6f50f278'. PublishType='ProjectPublish'' Error='Object reference not set to an instance of an object.'.

If your farm is not updated please update it from OCT CU for 2013 project server.
Please update it as cumulative update is having hotfix for this issue.
http://www.intersoft.no/blogg/item/33-april-2013s-cumulative-update-for-project-server-2013
http://www.datazx.cn/Fv7p5a/xw-US/dc6mbbt6-btss-fxi4-s8c4-8jsribt69m8x/nnn.projectserverexpertrs
As per the 2nd link Oct Cu for 2013 is fix this issue hence i would suggest you to upgrade from OCT CU.
kirtesh

Import rules, error message "Invalid system"

Hi,
When importing rules under Rule Architect - Import rules, error message "VBS is invalid system" . In the configuration tab we have system and System Name defined as VBS, test connection successful.
Why is it giving an error message VBS is invalid system? Please advise.
Thanks,
Sri

Hi,
Is it rule import after taking an export from other system? In that case, make sure destination system name doesn't contain any space in it.
Also, make sure text and auth Objects are uploaded for VBS system before doing rules import.
Regards,
Sabita

Oem: import job error

Similar Messages

Maybe you are looking for