PR creation ERROR: SAPSQL_ARRAY_INSERT_DUPREC via PS
When I create a Purchase Requisition via project systems, I get this error ERRO info 00671: Abap/4 processor: SAPSQL_ARRAY_INSERT_DUPREC. I configured a new PR document type and assigned a number range to it, I transported it o QAS and then PRD, I didnt test PS in detail, when I use base unit % there is not problem, but when I use PC and ROL, then I get an Update was terminated ERROR. How do i fix this?
Please give directive on which transactions or path I have to use to fix it.
Thank you.
Hi,
If you are using some badi or exit, check the process by de activating the same.
If same results are coming, then check OSS notes applicability in your case. (e.g. 148828, 193580 etc)
Other wise take help from OSS message, since this problem mainly occures due to program error.
Regards,
Manoj
Similar Messages
-
Hi!
I ran into the following problem when referencing the public parts of
an external j2ee library project stored in the NWDI. Specifically I would
like to reference an API part for having a correct build path during development.
Unfortunately I can create this reference but afterwards the NWDS tells
me that it requires to rebuild the ejb-jar.xml and the ejb-j2ee-engine.xml.
This automated refactoring leaves me with two 'empty' files, having all
my ejb definitions removed.
I tried to define new stateless ejbs by creating them via the context menu
and ran into the error 'Not able to create Session Bean'. In order to find out
what happened, I checked the .log file of the NWDS in my workspace folder
and found the following lines:
com.tssap.j2ee.ui.ejb.external.EjbCreationException: Creation error of EJB
at com.tssap.j2ee.ui.ejb.external.EjbFactory.createSessionBean(EjbFactory.java:304)
at com.tssap.j2ee.ui.ejb.external.EjbFactory.createSessionBean(EjbFactory.java:91)
at com.tssap.j2ee.ui.perspective.core.action.CreateEjbInPackageActionProvider$CreateStatelessSessionBeanInPackageAction.run(CreateEjbInPackageActionProvider.java:468)
at com.tssap.selena.model.extension.action.SelenaActionCollector$GenericElementActionWrapper.run(SelenaActionCollector.java:224)
at com.tssap.util.ui.menu.MenuFactory$MuSiAction.saveRunAction(MenuFactory.java:1425)
at com.tssap.util.ui.menu.MenuFactory$MuSiAction.run(MenuFactory.java:1407)
at com.tssap.util.ui.menu.MenuFactory$DelegateAction.processInternal(MenuFactory.java:616)
at com.tssap.util.ui.menu.MenuFactory$DelegateAction.access$100(MenuFactory.java:586)
at com.tssap.util.ui.menu.MenuFactory$DelegateAction$BusyProcessWorker.run(MenuFactory.java:716)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
at com.tssap.util.ui.menu.MenuFactory$DelegateAction.process(MenuFactory.java:610)
at com.tssap.util.ui.menu.internal.MenuListenerFactory$ProcessAdapter.widgetSelected(MenuListenerFactory.java:172)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
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:324)
at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
at com.sap.ide.eclipse.startup.Main.main(Main.java:607)
Nested exception -
com.tssap.j2ee.model.J2eeCreateException: Creation error of EJB
at com.tssap.j2ee.model.ejb.impl.EjbProject.createSessionBean(EjbProject.java:155)
at com.tssap.j2ee.model.ejb.impl.EjbModule.createSessionBean(EjbModule.java:385)
at com.tssap.j2ee.ui.ejb.wizard.internal.CreationFactorySemanticAPI.createEJB(CreationFactorySemanticAPI.java:115)
at com.tssap.j2ee.ui.ejb.wizard.internal.CreationFactorySemanticAPI.createSessionBean(CreationFactorySemanticAPI.java:55)
at com.tssap.j2ee.ui.ejb.external.EjbFactory.createSessionBean(EjbFactory.java:301)
at com.tssap.j2ee.ui.ejb.external.EjbFactory.createSessionBean(EjbFactory.java:91)
at com.tssap.j2ee.ui.perspective.core.action.CreateEjbInPackageActionProvider$CreateStatelessSessionBeanInPackageAction.run(CreateEjbInPackageActionProvider.java:468)
at com.tssap.selena.model.extension.action.SelenaActionCollector$GenericElementActionWrapper.run(SelenaActionCollector.java:224)
at com.tssap.util.ui.menu.MenuFactory$MuSiAction.saveRunAction(MenuFactory.java:1425)
at com.tssap.util.ui.menu.MenuFactory$MuSiAction.run(MenuFactory.java:1407)
at com.tssap.util.ui.menu.MenuFactory$DelegateAction.processInternal(MenuFactory.java:616)
at com.tssap.util.ui.menu.MenuFactory$DelegateAction.access$100(MenuFactory.java:586)
at com.tssap.util.ui.menu.MenuFactory$DelegateAction$BusyProcessWorker.run(MenuFactory.java:716)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
at com.tssap.util.ui.menu.MenuFactory$DelegateAction.process(MenuFactory.java:610)
at com.tssap.util.ui.menu.internal.MenuListenerFactory$ProcessAdapter.widgetSelected(MenuListenerFactory.java:172)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
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:324)
at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
at com.sap.ide.eclipse.startup.Main.main(Main.java:607)
Does anyone has been confronted with such an error before and could give
me a hint about how to solve this problem.
Kind regards,
Christian KreutzfeldtI resolved the problem myself by creating a new library project where I added
the libraries stepwise until building the referencing project failed. The library
project contains the hibernate framework which includes a file named jboss-j2ee.jar.
In some way or another this conflicts with the NWDS which leads to failures
when updating the ejb-jar.xml and ejb-j2ee-engine.xml files. -
Creation of notification via BAPI
Hi Guys,
I'm working in ECC 6.0 version. i have found a BAPI 'BAPI_ALM_NOTIF_CREATE' to create a notification. When i'm creating the notification through IW21 by passing notification type and functional location, i'm able to create a notification
But when i'm passing the same parameters to the BAPi, its neither returning any error record nor the notification is getting created.
Has anyone worked on the creation of notification via BAPI
Thanks in advanceThanks martin and ravi.
i have got the solution. Just thought of sharing with you guys.
After calling the BAPI passing the parameters notification type and functional location, a field NOTIF_NO will be returned which you have to pass to the BAPI 'BAPI_SERVNOT_SAVE
thats it
Thanks a lot -
Download Helper Screen Capture worked to capture video if the default "no audio" option is active. But, no audio. The "speakers" or "microphone" audio options are confusing....the audio to be captured is from the video, so what do you choose? With either "speakers" or "microphone" selected, the captured file has poor audio and no video. Re-capture efforts (speakers) get "Invalid capture file error" and "File Creation error- Unable to rename/copy audio file"
The paid upgrade of "Converter" doesn't work.
Instructive documentation - not very good.
Suggestions - Need time delay between initiation of "Record" and starting the video to be recorded.
Could use timer tracking of the record process.
Are there operating system limitations? (Have Windows XP Pro)That is an issue for the developer of that Download Helper.
-
How to send error message via a mail to the customers email id
HI experts ,
i have a requirement,In idoc where i have to send the error message via email to a perticular emailid?
please help me n tell also which fm is used for that?
Thanks
RAhul SisodiaHi ,
Check this Link..
[sending an email with multiple attachments;
Regards,
Sachin M M -
Getting error "Access via null" when running the web dynpro application
Hi experts,
I am getting the below error while executing my web dynpro application
500 SAP Internal Server Error
ERROR: Access via 'NULL' object reference not possible. (termination: RABAX_STATE)
I am getting the error only when I am calling a method create manufacturer from my web dynpro program. If i comment this code my application works fine
CALL METHOD wd_this->mo_ch_instance->create_manufacturer
EXPORTING
gi_manufacturer = ls_manufacturer
IMPORTING
lv_message = lv_status
i have created a attribute mo_ch_instance of type YSRM70CL_CH_SW_MD where YSRM70CL_CH_SW_MD is the class which has the create_manufacturer method that i am using in my code.
Kindly let me know whats the issue.
Regards,
VinodHi,
if wd_this->mo_ch_instance is not initial.
CALL METHOD wd_this->mo_ch_instance->create_manufacturer
EXPORTING
gi_manufacturer = ls_manufacturer
IMPORTING
lv_message = lv_status
endif.
Check wether you have created the object for that class r not.
Regards,
Lekha. -
FI-SL error SAPSQL_ARRAY_INSERT_DUPREC during direct posting to the SL.
I am working on FI- Special Ledger and currently encountering an error:
I am trying to post journals to the special purpose ledger using a local file where I am encountering the following error:
Runtime Errors SAPSQL_ARRAY_INSERT_DUPREC
Except. CX_SY_OPEN_SQL_DB
The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
in
procedure "INS_XXXXXA" "(FORM)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
If you use an ABAP/4 Open SQL array insert to insert a record in
the database and that record already exists with the same key,
this results in a termination.
XXXXXA is the custom database table name.
The form mentioned is a item table for one the special ledger which has been custom defined.
I have debugged the code and found out the following:
1. There are two records which needs to be updated to the items table of the ledger.
2. When I checked the items table the key value (which needs to be updated) doesn't exist currently.
3. I saw some resolution on the number range definition which i tried to apply but not fruitful.
Although the new records which needs to be inserted to the database table is not there I am getting the error SAPSQL_ARRAY_INSERT_DUPREC.
Please let me know of any suggestion to resolve the issue.
I might have not correctly implemented the solution for the number range.
Your valuable suggestions will be awarded accordingly.
Also let me know if anymore clarity is required.
Kind Regards,
himansu royHello everyone,
Got the issue and resolution.
The problem was in the custom code the ledger update was happening twice so the duplicate entries were giving dump during the COMMIT.
Regards,
Himansu Roy -
Update terminate : error SAPSQL_ARRAY_INSERT_DUPREC
We are getting error "SAPSQL_ARRAY_INSERT_DUPREC" while using tcode : VK12 ME13 ME11,
Error is in function module 'RV_KONDITION_SICHERN_VK13' , form 'KONH_CHANGE" in program "SAPLV13A". I checked OSS notes also but didnot find anything.We using ECC6. Can anybody tell what could be the reason and how to eliminate this.Hi Meena ,
are u running out of Number series ?, i had this kind of errors while i'm creating Delivery documents , then i found out Number ranges are missing ,thats y i got that errors, in ur case , i never seen number ranges for CONDITION records , but still u can cross check with ur function consultants.
regards
Prabhu -
Run-time error SAPSQL_ARRAY_INSERT_DUPREC occurred
When creating a new SyncBo (T51) instance after syncing eventually MI Clients shows the following message:
[20070315 01:28:14:343] E [MI/Sync ] Received exception info code 10 and detailed message "Exception while callSync: The ABAP/4 Open SQL arrayinsert results in duplicate database records. records in the data base."
In sm21 shows message:
AB0 Run-time error "SAPSQL_ARRAY_INSERT_DUPREC" occurred
AB1 > Short dump "070316 205056 sapnw ELDA " generated
Looking for SAPSQL_ARRAY_INSERT_DUPREC error in SAP Note we found the note 817849 (Runtime error SAPSQL_ARRAY_INSERT_DUPREC occurs during sync).
We have downloaded and applied this note in Backend as note requires and ALL prerequisites of this note. Also we have upgraded to SP19 and Kernel to 155 (part 1 and 2). But problem continues and the client that happened this problem does not work any more, all new SyncBO instances created goes to MEREP_MON as Waiting status.
The dump on duplicate record is happening when the user is synchronizing and when a record is getting inserted to table merep_10100.
The solution /workaround could be to do a client reset for those devicesand test again and see if it is happening, but error returns happening after this.
When this happen SyncBo instance keeps on Waiting status (MEREP_MON). We couldn't understand why this happen suddenly and then no more new SyncBo could be created, all goes to Waiting status. Reprocess (ShiftF5) or start handler (Shift10) does not take any effect.
Best Regards,
RogérioHi Ajith
I am getting the same error and below is the error message from ST22. The only change is I am using for MTR application and the sync fails for the 2nd time when synched for patches for the MTR application. As it is generic sync, could you please advice to get rid of the problem.
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
neither
caught nor passed along using a RAISING clause, in the procedure
"LOG_INSERT_DB" "(FORM)"
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:
If you use an ABAP/4 Open SQL array insert to insert a record in
the database and that record already exists with the same key,
this results in a termination.
(With an ABAP/4 Open SQL single record insert in the same error
situation, processing does not terminate, but SY-SUBRC is set to 4.)
Thanks, Raj -
Runtime error SAPSQL_ARRAY_INSERT_DUPREC during migo
Hi Friends,
When I try doing MIGO with reference to a PO and save the document it gives me runtime error SAPSQL_ARRAY_INSERT_DUPREC.
I have check the buffer, and the no. range everything is perfect, but still i am getting this error.
Can anyone please give me the possible solution for this. Is there any SAP note that I need to apply.
Regards,
Wasim.Hello Wasim,
The common cause of this termination is the material document
number range as per note 31793 - SAPSQL_ARRAY_INSERT_DUPREC.
So please check if the current numbers are synchronized with the
database tables:
OMBT trx x MKPF table
OMH6 trx x EKKO table
If it has the same number range the sort dump should not be raised
anymore.
The main root causes are:
-> when you are transporting number ranges from one client to another;
-> when you face a shut down in your system and you have defined a
buffer application server tolerance in transaction SNRO;
-> when you are doing the posting by using BAPI's and for some reason
the BAPI failed.
I hope it helps you.
Best Regards,
Fábio Almeida
MM Consultant -
Service Contracts Billing Schedule Creation Error
Hi,
I have a requirement of creating service contracts from back-end for which I am using the oks_contracts_pub.create_contract_header, create_service_line, and create_bill_schedule. I am creating my contracts with active status and renewal type of EVN (Header level), FUL(Line Level). My contract is of type subscription. The contract header and line are creating fine but the Bill schedule API is throwing an UNEXPECTED ERROR. The billing schedules need to be created based on accounting rule which can be quarterly or monthly. I have included the bill schedule code (hard coded values) for review. Any help is greatly appreciated.
Also the version I am working on is R12
________________________________________________CODE___________________________________________________________________
CREATE OR REPLACE PROCEDURE BILLING_SCHEDULE AS
l_strm_level_tbl OKS_BILL_SCH.STREAMLVL_TBL;
v_bill_qtrs NUMBER := 0;
v_bill_mths NUMBER := 0;
v_bill_days NUMBER := 0;
v_net_amount NUMBER := 468;
v_acct_rule_name VARCHAR2(50) := 'QUARTERLY';
v_amt_per_day NUMBER;
x_error_locator VARCHAR2(2000);
v_start_date DATE := '04-MAY-2010';
v_end_date DATE := '25-MAY-2010';
x_return_status VARCHAr2(3);
x_msg_count NUMBER;
x_msg_data VARCHAR2(2000);
v_billing_sequence NUMBER;
x_chr_id NUMBER := 17000;
x_line_id NUMBER := 223248604345353294444923586786456728480;
g_day_uom VARCHAR2(10) := 'DAY';
g_month_uom VARCHAR2(10) := 'MTH';
g_quarter_uom VARCHAR2(10) := 'QTR';
v_amt NUMBER;
v_invoicing_rule_id NUMBER := -2;
BEGIN
--Create Billing Schedule based on accounting rule
okc_context.set_okc_org_context;
MO_GLOBAL.INIT('OKS');
MO_GLOBAL.SET_POLICY_CONTEXT('S', 83);
v_bill_qtrs := 0;
v_bill_days := 0;
v_bill_mths := 0;
SELECT NVL(v_net_amount, 0)/(v_end_date - v_start_date)
INTO v_amt_per_day
FROM dual;
dbms_output.put_line('Calculated amt per day ' || v_amt_per_day);
IF v_acct_rule_name LIKE '%QUARTERLY%' THEN
--Quarterly billing schedule
SELECT FLOOR(MONTHS_BETWEEN( v_end_date,
v_start_date)/3),
v_end_date - ADD_MONTHS(v_start_date, (FLOOR(MONTHS_BETWEEN(v_end_date, v_start_date)/3)*3))
INTO v_bill_qtrs,
v_bill_days
FROM dual;
dbms_output.put_line('Calculated the qtrs and days');
IF v_bill_qtrs > 0 THEN
SELECT (ADD_MONTHS(v_start_date, (FLOOR(MONTHS_BETWEEN(v_end_date, v_start_date)/3)*3)) - v_start_date)*v_amt_per_day
INTO v_amt
FROM dual;
dbms_output.put_line('Calculated qtr amt');
SELECT NVL(MAX(sequence_no), 0) + 1
INTO v_billing_sequence
FROM oks_stream_levels_b
WHERE dnz_chr_id = x_chr_id
AND cle_id = x_line_id;
--Populating the stream line variables
l_strm_level_tbl(v_billing_sequence).sequence_no := v_billing_sequence;
l_strm_level_tbl(v_billing_sequence).dnz_chr_id := x_chr_id;
-- l_strm_level_tbl(v_billing_sequence).id := x_line_id;
l_strm_level_tbl(v_billing_sequence).cle_id := x_line_id;
l_strm_level_tbl(v_billing_sequence).uom_code := g_quarter_uom;
l_strm_level_tbl(v_billing_sequence).uom_per_period := 1;
l_strm_level_tbl(v_billing_sequence).level_periods := v_bill_qtrs;
l_strm_level_tbl(v_billing_sequence).start_date := v_start_date;
l_strm_level_tbl(v_billing_sequence).end_date := v_end_date;
l_strm_level_tbl(v_billing_sequence).invoice_offset_days := NULL;
l_strm_level_tbl(v_billing_sequence).amount := v_amt/v_bill_qtrs;
l_strm_level_tbl(v_billing_sequence).level_amount := v_amt/v_bill_qtrs;
l_strm_level_tbl(v_billing_sequence).lines_detailed_yn := 'Y';
l_strm_level_tbl(v_billing_sequence).due_arr_yn := 'Y';
dbms_output.put_line('Before calling the Bill Sch API for QTR');
OKS_CONTRACTS_PUB.CREATE_BILL_SCHEDULE ( p_billing_sch=>'E',
p_strm_level_tbl=>l_strm_level_tbl,
p_invoice_rule_id=>v_invoicing_rule_id,
x_return_status=>x_return_status);
dbms_output.put_line('After calling the Bill Sch API for QTR');
IF x_return_status <> 'S' THEN
x_msg_count := 1;
dbms_output.put_line('Quarterly schedule creation error ' || x_msg_data);
---DBMS_TRANSACTION.ROLLBACK_SAVEPOINT('OKS_A');
-- RETURN;
END IF;
END IF;
IF v_bill_days > 0 THEN
SELECT NVL(MAX(sequence_no), 0) + 1
INTO v_billing_sequence
FROM oks_stream_levels_b
WHERE dnz_chr_id = x_chr_id
AND cle_id = x_line_id;
dbms_output.put_line('sequence '||v_billing_sequence);
--Populating the stream line variables
l_strm_level_tbl(v_billing_sequence).sequence_no := v_billing_sequence;
l_strm_level_tbl(v_billing_sequence).dnz_chr_id := x_chr_id;
--l_strm_level_tbl(v_billing_sequence).id := x_line_id;
l_strm_level_tbl(v_billing_sequence).cle_id := x_line_id;
l_strm_level_tbl(v_billing_sequence).uom_code := g_day_uom;
l_strm_level_tbl(v_billing_sequence).uom_per_period := v_bill_days;
l_strm_level_tbl(v_billing_sequence).level_periods := 1;
l_strm_level_tbl(v_billing_sequence).start_date := v_start_date;
l_strm_level_tbl(v_billing_sequence).end_date := v_end_date;
l_strm_level_tbl(v_billing_sequence).invoice_offset_days := NULL;
l_strm_level_tbl(v_billing_sequence).amount := v_net_amount;--v_amt_per_day*v_bill_days;
l_strm_level_tbl(v_billing_sequence).level_amount := v_net_amount;--v_amt_per_day*v_bill_days;
l_strm_level_tbl(v_billing_sequence).lines_detailed_yn := 'Y';
l_strm_level_tbl(v_billing_sequence).due_arr_yn := 'Y';
dbms_output.put_line('Before calling the Bill Sch API for QTR days');
OKS_CONTRACTS_PUB.CREATE_BILL_SCHEDULE ( p_billing_sch=>'E',
p_strm_level_tbl=>l_strm_level_tbl,
p_invoice_rule_id=>v_invoicing_rule_id,
x_return_status=>x_return_status);
dbms_output.put_line('After calling the Bill Sch API for QTR days ' || v_bill_days || ' ' || x_return_status);
IF x_return_status <> 'S' THEN
x_msg_count := 1;
dbms_output.put_line('Day schedule, for quarterly accounting rule, creation error ' || x_msg_data);
--DBMS_TRANSACTION.ROLLBACK_SAVEPOINT('OKS_A');
--RETURN;
END IF;
END IF;
ELSE
--Monthly billing schedule
SELECT FLOOR(MONTHS_BETWEEN( v_end_date,
v_start_date)),
v_end_date - ADD_MONTHS(v_start_date, FLOOR(MONTHS_BETWEEN(v_end_date, v_start_date)))
INTO v_bill_mths,
v_bill_days
FROM dual;
dbms_output.put_line('Calculated the mths and days');
IF v_bill_mths > 0 THEN
SELECT (ADD_MONTHS(v_start_date,FLOOR(MONTHS_BETWEEN(v_end_date, v_start_date))) - v_start_date)*v_amt_per_day
INTO v_amt
FROM dual;
dbms_output.put_line('Calculated the mths amt');
SELECT NVL(MAX(sequence_no), 0) + 1
INTO v_billing_sequence
FROM oks_stream_levels_b
WHERE dnz_chr_id = x_chr_id
AND cle_id = x_line_id;
--Populating the stream line variables
l_strm_level_tbl(v_billing_sequence).sequence_no := v_billing_sequence;
l_strm_level_tbl(v_billing_sequence).dnz_chr_id := x_chr_id;
--l_strm_level_tbl(v_billing_sequence).id := x_line_id;
l_strm_level_tbl(v_billing_sequence).cle_id := x_line_id;
l_strm_level_tbl(v_billing_sequence).uom_code := g_month_uom;
l_strm_level_tbl(v_billing_sequence).uom_per_period := 1;
l_strm_level_tbl(v_billing_sequence).level_periods := v_bill_mths;
l_strm_level_tbl(v_billing_sequence).start_date := v_start_date;
l_strm_level_tbl(v_billing_sequence).end_date := v_end_date;
l_strm_level_tbl(v_billing_sequence).invoice_offset_days := NULL;
l_strm_level_tbl(v_billing_sequence).amount := v_amt/v_bill_mths;
l_strm_level_tbl(v_billing_sequence).level_amount := v_amt/v_bill_mths;
l_strm_level_tbl(v_billing_sequence).lines_detailed_yn := 'Y';
l_strm_level_tbl(v_billing_sequence).due_arr_yn := 'Y';
dbms_output.put_line('Before calling the Bill Sch API for MTHS');
OKS_CONTRACTS_PUB.CREATE_BILL_SCHEDULE ( p_billing_sch=>'E',
p_strm_level_tbl=>l_strm_level_tbl,
p_invoice_rule_id=>v_invoicing_rule_id,
x_return_status=>x_return_status);
dbms_output.put_line('After calling the Bill Sch API for MTHS');
IF x_return_status <> 'S' THEN
x_msg_count := 1;
dbms_output.put_line('Monthly schedule creation error ' || x_msg_data);
--DBMS_TRANSACTION.ROLLBACK_SAVEPOINT('OKS_A');
--RETURN;
END IF;
END IF;
IF v_bill_days > 0 THEN
SELECT NVL(MAX(sequence_no), 0) + 1
INTO v_billing_sequence
FROM oks_stream_levels_b
WHERE dnz_chr_id = x_chr_id
AND cle_id = x_line_id;
--Populating the stream line variables
l_strm_level_tbl(v_billing_sequence).sequence_no := v_billing_sequence;
l_strm_level_tbl(v_billing_sequence).dnz_chr_id := x_chr_id;
--l_strm_level_tbl(v_billing_sequence).id := x_line_id;
l_strm_level_tbl(v_billing_sequence).cle_id := x_line_id;
l_strm_level_tbl(v_billing_sequence).uom_code := g_day_uom;
l_strm_level_tbl(v_billing_sequence).uom_per_period := v_bill_days;
l_strm_level_tbl(v_billing_sequence).level_periods := 1;
l_strm_level_tbl(v_billing_sequence).start_date := v_start_date;
l_strm_level_tbl(v_billing_sequence).end_date := v_end_date;
l_strm_level_tbl(v_billing_sequence).invoice_offset_days := NULL;
l_strm_level_tbl(v_billing_sequence).amount := v_amt_per_day*v_bill_days;
l_strm_level_tbl(v_billing_sequence).level_amount := v_amt_per_day*v_bill_days;
l_strm_level_tbl(v_billing_sequence).lines_detailed_yn := 'Y';
l_strm_level_tbl(v_billing_sequence).due_arr_yn := 'Y';
dbms_output.put_line('Before calling the Bill Sch API for MTH days');
OKS_CONTRACTS_PUB.CREATE_BILL_SCHEDULE ( p_billing_sch=>'E',
p_strm_level_tbl=>l_strm_level_tbl,
p_invoice_rule_id=>v_invoicing_rule_id,
x_return_status=>x_return_status);
dbms_output.put_line('After calling the Bill Sch API for MTH days');
IF x_return_status <> 'S' THEN
x_msg_count := 1;
dbms_output.put_line('Day schedule, for monthly accounting rule, creation error ' || x_msg_data);
--DBMS_TRANSACTION.ROLLBACK_SAVEPOINT('OKS_A');
--RETURN;
END IF;
END IF;
END IF;
COMMIT;
EXCEPTION
when others then
dbms_output.put_line('Error ' || sqlerrm);
END;
Thanks,
Yash.Hi There,
I have a similar requirement to create rental service contracts and create billing schedules.
Can you please pass on your functional docs so that i can refer to them.
Thanks,
Raidu -
Request creation error for mitigation control workflow
Dear Expert,
I had activiate the workflow from RAR to CUP on Mitigated User assignment, I had completed following customizing:
1)RAR->configaration->Workflow
2)CUP->configaration->initiator, stage, path.
but when I created mitigated user assignments in RAR, after click "Submit", error popup: "Request creation error"
can some one help?
thanks!Dear,
the log is below:
ERROR service 'SAPGW00' unknown
TIME Thu May 20 13:33:16 2010
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -3
MODULE niuxi.c
LINE 1732
DETAIL NiPGetServByName2: service 'SAPGW00' not found
SYSTEM CALL getservbyname_r
COUNTER 375
May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
INFO: Exception in Server YYY:
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
Could not start server: Connect to SAP gateway failed
Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
ERROR service 'SAPGW00' unknown
TIME Thu May 20 13:33:16 2010
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -3
MODULE niuxi.c
LINE 1732
DETAIL NiPGetServByName2: service 'SAPGW00' not found
SYSTEM CALL getservbyname_r
COUNTER 375
May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
INFO: Exception in Server YYY:
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
Could not start server: Connect to SAP gateway failed
Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
ERROR service 'SAPGW00' unknown
TIME Thu May 20 13:33:16 2010
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -3
MODULE niuxi.c
LINE 1732
DETAIL NiPGetServByName2: service 'SAPGW00' not found
SYSTEM CALL getservbyname_r
COUNTER 375
May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
INFO: Exception in Server YYY:
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
Could not start server: Connect to SAP gateway failed
Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
ERROR service 'SAPGW00' unknown
TIME Thu May 20 13:33:16 2010
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -3
MODULE niuxi.c
LINE 1732
DETAIL NiPGetServByName2: service 'SAPGW00' not found
SYSTEM CALL getservbyname_r
COUNTER 375
May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
INFO: Exception in Server YYY:
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
Could not start server: Connect to SAP gateway failed
Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
ERROR service 'SAPGW00' unknown
TIME Thu May 20 13:33:16 2010
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -3
MODULE niuxi.c
LINE 1732
DETAIL NiPGetServByName2: service 'SAPGW00' not found
SYSTEM CALL getservbyname_r
COUNTER 375
May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
INFO: Exception in Server YYY:
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
Could not start server: Connect to SAP gateway failed
Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
ERROR service 'SAPGW00' unknown
TIME Thu May 20 13:33:16 2010
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -3
MODULE niuxi.c
LINE 1732
DETAIL NiPGetServByName2: service 'SAPGW00' not found
SYSTEM CALL getservbyname_r
COUNTER 375
May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
INFO: Exception in Server YYY:
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
Could not start server: Connect to SAP gateway failed
Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
ERROR service 'SAPGW00' unknown
TIME Thu May 20 13:33:16 2010
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -3
MODULE niuxi.c
LINE 1732
DETAIL NiPGetServByName2: service 'SAPGW00' not found
SYSTEM CALL getservbyname_r
COUNTER 375
May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
INFO: Exception in Server YYY:
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
Could not start server: Connect to SAP gateway failed
Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
ERROR service 'SAPGW00' unknown
TIME Thu May 20 13:33:16 2010
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -3
MODULE niuxi.c
LINE 1732
DETAIL NiPGetServByName2: service 'SAPGW00' not found
SYSTEM CALL getservbyname_r
COUNTER 375
May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
INFO: Exception in Server YYY:
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
Could not start server: Connect to SAP gateway failed
Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
ERROR service 'SAPGW00' unknown
TIME Thu May 20 13:33:16 2010
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -3
MODULE niuxi.c
LINE 1732
DETAIL NiPGetServByName2: service 'SAPGW00' not found
SYSTEM CALL getservbyname_r
COUNTER 375
May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
INFO: Exception in Server YYY:
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
Could not start server: Connect to SAP gateway failed
Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
ERROR service 'SAPGW00' unknown
TIME Thu May 20 13:33:16 2010
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -3
MODULE niuxi.c
LINE 1732
DETAIL NiPGetServByName2: service 'SAPGW00' not found
SYSTEM CALL getservbyname_r
COUNTER 375
May 20, 2010 2:10:50 PM com.virsa.cc.workflow.bo.WorkflowBO submit
INFO: END POOINT URL: http://9.186.143.129:50100/AEWFRequestSubmissionService_5_2/Config1?style=document
May 20, 2010 2:10:50 PM com.virsa.cc.workflow.bo.WorkflowBO submit
INFO: before submit:
May 20, 2010 2:10:50 PM com.virsa.cc.workflow.bo.WorkflowBO submit
INFO: wftype: MITIOBJ reqid: GRC01
May 20, 2010 2:10:50 PM com.virsa.cc.rulearchitect.dao.dto.MitObjDTO getObjContext
FINEST: validfrom: 2010-05-20 validto: 2011-05-20
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Data Type: String
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Descripton: MITREFNO
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Name: MOMITREFNO
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Value: CT01
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Data Type: String
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Descripton: RISKID
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Name: MORISKID
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Value: ZC02
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Data Type: String
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Descripton: LANG
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Name: LANG
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Value: EN
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Data Type: String
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Descripton: MONITORID
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Name: MONITORID
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Value: GRC01
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Data Type: Integer
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Descripton: STATUS
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Name: MOSTATUS
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Value: 0
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Data Type: DATE
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Descripton: VALIDFROM
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Name: VALIDFROM
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Value: 05/20/2010
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Data Type: DATE
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Descripton: VALIDTO
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Name: VALIDTO
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Value: 05/20/2011
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Data Type: String
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Descripton: BU ID
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Name: BUID
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Value: null
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Data Type: String
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Descripton: Approver ID
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Name: MOAPPROVERID
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Value: null
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Data Type: String
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Descripton: OBJTYPE
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Name: OBJTYPE
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Value: U
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Data Type: String
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Descripton: OBJID
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Name: OBJID
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Value: 207471
May 20, 2010 2:10:50 PM com.virsa.cc.workflow.bo.WorkflowBO submit
INFO: Return code: 2010 Message: com.virsa.ae.core.ObjectNotFoundException: Invalid Priority Value : MO_HIGH workflow id: null Status: null
May 20, 2010 2:10:50 PM com.virsa.cc.workflow.bo.WorkflowBO submit
WARNING: 2010: null -
Runtime Errors SAPSQL_ARRAY_INSERT_DUPREC in t-code KO02
Hi Guru,
I got runtime error in transaction KO02, below i given all the details.
Runtime Errors SAPSQL_ARRAY_INSERT_DUPREC
Exception CX_SY_OPEN_SQL_DB
(With an ABAP/4 Open SQL single record insert in the same error
situation, processing does not terminate, but SY-SUBRC is set to 4.)
How to correct the error
Use an ABAP/4 Open SQL array insert only if you are sure that none of
the records passed already exists in the database.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"SAPSQL_ARRAY_INSERT_DUPREC" "CX_SY_OPEN_SQL_DB"
"SAPLA02S" or "LA02SF00"
"INSERT_ENTRIES"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
The exception must either be prevented, caught within proedure
"INSERT_ENTRIES" "(FORM)", or its possible occurrence must be declared in the
RAISING clause of the procedure.
To prevent the exception, note the following:
Information on where terminated
Termination occurred in the ABAP program "SAPLA02S" - in "INSERT_ENTRIES".
The main program was "RSM13000 ".
In the source code you have the termination point in line 132
of the (Include) program "LA02SF00".
The program "SAPLA02S" was started in the update system.
The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
procedure "INSERT_ENTRIES" "(FORM)", but it was neither handled locally nor
declared
in the RAISING clause of its signature.
The procedure is in program "SAPLA02S "; its source code begins in line
85 of the (Include program "LA02SF00 ".
Plz tell me if some one have idea to solve this problem,
Thanks,
NamdevHi,
check in the OSS and see if there is any note available:
e.g.
Note 78466 - RA_ASSET_MODIFIKATION - SAPSQL_ARRAY_INSERT_DUPREC
https://service.sap.com/sap/support/notes/78466
Best regards. -
Delivery Note to Subcontract creation error "Essential transfer parameters
Hi
I am facing issue in return delivey
Delivery Note to Subcontract creation error "Essential transfer parameters are missing in record:000001".
Could you please let me know the casue of this error and where exactly i can see error.
Regards
vikcyHi Vicky,
Check If the Customer number(Plant) has been maintained in the vendor master record control data and the vendor should also be maintained in the customer master data. Once you maintain this system determines the shipping point based on the customer master and the shipping data missing. Kindly try delivering after maintaining these and let me know If you need any more information on this.
Regards
Ram Pedarla -
Error SAPSQL_ARRAY_INSERT_DUPREC executing infopackages
Hi,
When we execute any infopackage with source system R3 the following runtime error is generated:
Category ABAP Programming Error
Runtime Errors SAPSQL_ARRAY_INSERT_DUPREC
Except. CX_SY_OPEN_SQL_DB
ABAP Program SAPLEDI1
Short text
The ABAP/4 Open SQL array insert results in duplicate database records.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
in
procedure "F09_IDOC_INSERT_WITH_NUMBER" "(FORM)", nor was it propagated by a
RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
If you use an ABAP/4 Open SQL array insert to insert a record in
the database and that record already exists with the same key,
this results in a termination.
(With an ABAP/4 Open SQL single record insert in the same error
situation, processing does not terminate, but SY-SUBRC is set to 4.)
The line code with the error in this FORM is:
>>> INSERT EDID4 FROM TABLE LIST_CONTAINER_CREATE.
We have simulated correctly all datasources in the source system using t-code RSA3, then we think that the problem is BW and not in the source system.
Also we removed the PSA and executed the infopackage again, but the same error is showed.
Please, could you help us?
Thanks in advance,
Regards,
Edited by: dbenitez on Feb 29, 2012 8:58 AMHi Kiran,
I have checked your links but the problem has not been solved. I think that the problem could be the IDOCs because the line code with error is (program SAPLEDI1):
>>> INSERT EDID4 FROM TABLE LIST_CONTAINER_CREATE.
The table EDID4 contents all IDOCs of the system (this table is very big (>150.000.000 records))
could be a memory space problem? but the messate error is by Duplicated records... I don't know...
please, could anyone help me?
Thanks!
Regards,
Maybe you are looking for
-
Suggestions for new forum names
iMac (PPC) - iMac (PPC including G5, pre-2006) iBook - iBook (pre-2006 notebook). Powerbook - Powerbook (pre-2006 notebook) MacBook - MacBook (consumer notebook) MacBook Pro - MacBook Pro (pro notebook) Mac Pro - Mac Pro (Intel CPU Desktop Tower) Pow
-
Entourage 2008 email sync with PocketPC WIndows Mobile 6
Hi: Does anybody know a software or procedure for syncronize emails between Entourage 2008 and PocketPC? I´ve tried Missing Sync and PocketMac but unfortunately none can do it. They only include notes, tasks, contacts, calendar, but email isnt includ
-
Benefits services (WD Java) in EhP5 using NWBC
Hi, We are using NWBC to acces WDA portal application... They seems to work fine, however, the Benefits applications are still in WD for Java. Is there a way we can access these Benefits applications using NWBC (for html)? We are using EhP5. I am tol
-
I Bought Elements/Premiere 11 and I cannot install it.
I was more accurately given them for Christmas this past year by my parents. I had no trouble installing them on my main computer but I wanted to install them on my school computer as well and ran into trouble. My school computer does not have a CD/D
-
MacBook Pro, Parallels, Quickbooks and Printing
Neither laptop or iMac now recognize my wireless printer, although they were working at first. The wireless printer is on, and can print its own diagnostic report that says it is connected to the WiFi (the same one both Macs are connected to). Orig