Update was terminated error ,while doing PGI

Hello All,
While Posting Goods issue for a Delivery we are geeting -Update was terminated error.
When Analysed in SM13 ,it shows error message as :-Error Info... C4 001: Value "03/09/2010
Checked for various dates in Delivery ,Sales Order & delivery both created after 9th march 2010.
Please advice ,if someone have encountered same kind of issue .?
Do we have way to find clue to error through update key.?
Update key... 4BA0B325C79F00BEE10080009974E162
Regards,
Vikas

Hi Vikas,
This is Basis issue, you need to talk with the basis team.
They will clear this issue.
Hope it helps,
Regards,
MT

Similar Messages

Update was terminated error while trying to attach output type to VA22

Hi
We are getting the below message while trying to attach output type to quotation in VA22 transaction
Can you tell us what exactly the problem is?
It doesn't happen with other output types...
Update was terminated
System ID....   PEQ
Client.......   300
User.....   Swetha
Transaction..   VA21
Update key...   1CB83C9AAEF946C8A1CDE4E19BC94479
Generated....   19.05.2008, 08:22:54
Completed....   19.05.2008, 08:23:41
Error Info...   Application area: /SMB40/SSFCOMPOSER , message no.: 002, no entry found in T100
Regards
Sudha

Hi ,
Please check the message in the table - T100 using transaction se11. You might get the answer.
Thanks
vamshi

Update was terminated error while scheduling maintenance plan

HI Friends,
I created a maintenance plan.I scheduled the order and i saved.
Now when i tried to see the schedule i am getting a message
"Update was terminated"
the detailed error is
Update was terminated
System ID....   DEV
Client.......   XXX
User.....   XXXXX
Transaction..   IP10
Update key...   49041E2C02935CCCE10000000AFA0209
Generated....   30.10.2008, 17:22:18
Completed....   30.10.2008, 17:22:19
Error Info...   00 671: ABAP/4 processor: SAPSQL_ARRAY_INSERT_DUPREC
Can anyone tell me why this error is coming and how to rectify.
Thanks in advance
Vivek
Edited by: vivek mankad on Oct 30, 2008 1:38 PM

Vivek,
Talk to your ABAP/Basis team
PeteA

Termination error while doing me31k

HI Experts,
This is the sincere apology for the previous thread which was in capital letter subject" termination error while doing me31k
Posted: Mar 6, 2012 2:56 AM
HI while performing transaction ME31K I'm getting follow error
Runtime error: DYNPRO_NOT_FOUND
What Happened?
Error in the ABAP application Program
The current ABAp program "SAPLXM06" had to be terminated because it has come across a statement that unfortunately canont be executed.
Error Analysis
The system attempted to use dynpro 0201 in program "SAPLXM06".
This dynpro does not exist.
Trigger Location of Run TIme Error
Program: SAPLXM06
Include: MM06E00C_CUSTSCR1_HEAD_SET_DAT
ROW: 10
There is a Edit button, that allows you to change the subject
Edited by: Jürgen L. on Mar 6, 2012 8:41 AM

Dear MM user,
Follow the documentation of this enhancement (see transaction SMOD):
Within the documentation of enhancement MM06E005, via TA SMOD, it specifically states that if you use the enhancement you must generate six listed dynpros (screens), even if you are not using them.
So you may goto transaction CMOD and enhance the same.
For example, the dynpro area should be like the following:
Calling screen No. Area Called screen No. ShortTxt
SAPMM06E 0101 CUSTSCR1 SAPLXM06 0101 Subscreen: PO header
SAPMM06E 0111 CUSTSCR1 SAPLXM06 0111 Subscreen: PO item
SAPMM06E 0201 CUSTSCR1 SAPLXM06 0201 Subscreen: agreement
Regards,
ian Wong Loke Foong

Error while doing PGI for Outbound delivery using BAPI BAPI_GOODSMVT_CREATE

Hi All,
I am getting an below error while doing PGI for outbound delivery using the BAPI BAPI BAPI_GOODSMVT_CREATE:
Goods movement not possible with mvmt type 601
Can anyone suggest me what will be the solution for it?
Regards,
Raghuraman.k

I tried with the above BAPI but it is not working.
In my case a delivery has one line item with batch split and other line item without batch split.
Below is my code :
DATA : gwa_header_data TYPE bapiobdlvhdrcon,
       gwa_header_ctrl TYPE bapiobdlvhdrctrlcon,
       lv_delivery     TYPE bapiobdlvhdrcon-deliv_numb,
       git_item_data TYPE STANDARD TABLE OF bapiobdlvitemcon,
       gwa_item_data TYPE bapiobdlvitemcon,
       git_item_ctrl TYPE STANDARD TABLE OF bapiobdlvitemctrlcon,
       gwa_item_ctrl TYPE bapiobdlvitemctrlcon,
       git_return    TYPE STANDARD TABLE OF bapiret2,
       gwa_return    TYPE bapiret2.
*Header data
gwa_header_data-deliv_numb = '0808000002'.
*Header Control data
gwa_header_ctrl-deliv_numb = '0808000002'.
gwa_header_ctrl-post_gi_flg = 'X'.
*Delivery Number
lv_delivery = '0808000002'.
*Item data and its corresponding control data
gwa_item_data-deliv_numb      = '0808000002'.
gwa_item_data-deliv_item      = '900002'.
gwa_item_data-dlv_qty         = 4.
gwa_item_data-dlv_qty_imunit = 4.
gwa_item_data-fact_unit_nom   = 1.
gwa_item_data-fact_unit_denom = 1.
APPEND gwa_item_data TO git_item_data.
gwa_item_ctrl-deliv_numb      = '0808000002'.
gwa_item_ctrl-deliv_item      = '900002'.
gwa_item_ctrl-chg_delqty      = 'X'.
APPEND gwa_item_ctrl TO git_item_ctrl.
gwa_item_data-deliv_numb      = '0808000002'.
gwa_item_data-deliv_item      = '900003'.
gwa_item_data-dlv_qty         = 6.
gwa_item_data-dlv_qty_imunit = 6.
gwa_item_data-fact_unit_nom   = 1.
gwa_item_data-fact_unit_denom = 1.
APPEND gwa_item_data TO git_item_data.
gwa_item_ctrl-deliv_numb      = '0808000002'.
gwa_item_ctrl-deliv_item      = '900003'.
gwa_item_ctrl-chg_delqty      = 'X'.
APPEND gwa_item_ctrl TO git_item_ctrl.
gwa_item_data-deliv_numb      = '0808000002'.
gwa_item_data-deliv_item      = '000020'.
gwa_item_data-dlv_qty         = 10.
gwa_item_data-dlv_qty_imunit = 10.
gwa_item_data-fact_unit_nom   = 1.
gwa_item_data-fact_unit_denom = 1.
APPEND gwa_item_data TO git_item_data.
gwa_item_ctrl-deliv_numb      = '0808000002'.
gwa_item_ctrl-deliv_item      = '000020'.
gwa_item_ctrl-chg_delqty      = 'X'.
APPEND gwa_item_ctrl TO git_item_ctrl.
BREAK-POINT.
CALL FUNCTION 'BAPI_OUTB_DELIVERY_CONFIRM_DEC'
EXPORTING
    header_data    = gwa_header_data
    header_control = gwa_header_ctrl
    delivery       = lv_delivery
TABLES
    item_data      = git_item_data
    item_control   = git_item_ctrl
    return         = git_return.
BREAK-POINT.
IF git_return IS INITIAL.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
ENDIF.

Getting the error while doing PGI for depot delivery

Hi
I am getting the below error while doing PGI for Depot delivery. This error is happening only when I taking the materials from stock transfer order which has more than 10 line items. Same issue is not happening when I am taking one material in Stock transfer order in & same material in depot delivery. Please see the screen shots below attachment. I have already maintained no range for the object J_1IDEPINV for year 2014.
Regards
PK

Moved from SAP ERP SD Sales to Internationalization and Unicode. Please post all your CIN related queries here. Also ensure that before posting, you made efforts in searching in SCN or Google. The reason for this indication is the issue you posted has already been discussed many times here and you will get some clue had you searched.
G. Lakshmipathi

Getting error while doing pgi

i am getting an error while doing pgi, the error is 'runtime error - description of exception'
how could i overcome this problem
pls help me to solve this problem

Hi,
Consult your abaper he can give you a solution.
Thank you,

Update termination error while doing PGR

Hi,
I got this error while doing PGR, please do suggest the dolution.
Update was terminated
System ID....   DPT
Client.......   900
User.....   SDUSER
Transaction..   VL02N
Update key...   4BEAA8A2A6DA0609E1000000AC1107A7
Generated....   12.05.2010, 18:38:55
Completed....   12.05.2010, 18:38:56
Error Info...   Update program: I/O error Error; function Update, RC= 4, key
Thanks,
Swapnil

Hi Lakshmipathi,
I have checked the analysis in SM13, got the folllowing,
Function Module        SERIALNUMBER_POST
Status                        Update was terminated
Report                        LIEP1U01
Row                            159
Error details   Class:     IS         Number:    229
Update program: I/O error Error; function Update, RC= 4, key

"Update was Terminated" Error

Hi ,
I am facing this particular error while creating billing document in VF01 and VF02.
"UPDATE WAS TERMINATED". The program and script are executing fine in Dev System but it is giving this error in Test System.
The Billing type created was F2 Invoice.After entering Logical Destination in output type and running transaction VF02, this error window is popped up saying "EXPRESS DOCUMENT:UPDATE WAS TERMINATED".I have checked the dump in SM13 and tried to analyse it.It shows the error :TD-423: WRITE_FORM.
Any form of help in this issue is highly appreciated.

Hello,
This problem occurs due to updation error in SAP database...
you will see number range has been increased but the document does not exist in SAP...!!!
also it can be possible that some users has this problem....
I had similar kind problem in one of my implementaion and got help with SAP...
I would like to suggest to contact SAP service desk...
Thanks.

Update was terminated error is coming?

Hello experts,
I got an error while creating a process order.System allowing to create a process order after saving througing an error
" Express document "Update was terminated" received from author "GLP Developer"
'Error Info... 00 671: ABAP/4 processor: SAPSQL_ARRAY_INSERT_DUPREC".
I did changed the number ranges for a particular order type.Created one order and prcessed.But again getting the same error while processing second order.

Hi max,
Thanks for your immediate response.We removed all number ranges .related process order again assigned the new number ranges 000000200001 to 000000299999 are not used earlier.In this case while creating a process orders it is getting updated randomly and showing present number in number range as 20011.If we see 5 process orders only able to see in system even I created 11 orders. For remaining orders it is showing not found tried continuously creating process orders in COR1 transactions and checking for updating in display mode.Same thing some orders or missing.FOr missing orders it is shoeing the above error.
Please respond.
Thanks in advance,
Charan

FMBBC Express document " Update was terminated error"

Hi ,
while saving data FMBBC i am getting saved message , after that if i come out of the Tcode i am getting message as
Express document " update was terminated".I was debugging the standard code found that the error comes from SXOP table entry, This table is get filled from FM SO_EXPRESS_FLAG_SET. But this FM is called from background I think. There is no job also created.After displaying the message automatically the SXOP table entry is get deleted. I want to debug this FM or wht is the reason for displaying message.
Regards,
siva kumar

Following steps may help you.
1. GO to SM13 transaction.
2. Check your update request.
3. You can see exact point in the standard program where you are getting this message

Error while doing PGI

while doing PGI i am getting error : " Item 000010 requires exactly 10 serial numbers for the asset "
i tried by Extra --> serial no here i am not able to do anything, there is no automatic button in pop up screen.
and in mm02 also i tried in sales:general plant/data
i am not able to do PGI, is there is any other solutions

Dear Mohan,
As per your message the material alredy got assigned some serial number so those serial numbers only you need to assign in the delivery before PGI.
But you have mentioned that there is no popup menu when you go through Extras -->Click on serial numbers this is the place you can assign the serial numbers to the material (go to drop dowmn for existing serial number).
I hope this will help you,
Regards,
Murali.

Earmarked funds - Express document "Update was terminated" error

Hi,
When i create a contract(RECN), a earmarked funds document getting created and it updates the table KBLK with single primary key BELNR.
I see in the Tcode OK60, the number range assinged is '05' - 0200000000 to 0299999999.
KBLK table has entries created from 0200000000 to 0299994311 which were created earlier.
From this financial year, when i am creating a contract, the new BELNR is started again from 0200000000 series, hence it throws an error message "Express document "Update was terminated" since entries are already exist in the KBLK table.
Finally i understand we have to change number range assignment.
Where can i do this? Please help if my understanding is wrong, how can i rectify this issue.
Thanks,
Bharath.

Hi,
U can change the number range for the contract for this fical year and make it start from 0299994312 to 0299999999.
But it seems u have already used most of the numbers, so go for a new number range for both the documents.
Hope this helps
Deepak

Run time error while doing PGI

hi gurus
while doing PGI i am experiencing run time error.
the ERROR ANALYSIS says that " check doc number 49 in company code 1234 and fiscal year 2007. and correct the number range status if necessary".
i'm confused. please guide how to rectify the problem.
thank you all in advance
regards
madhu

Create new number range in T.Code:FBN1
Go to menu path:
IMG > Materials Management >Inventory Management and Physical Inventory > Number Assignment > Define Number Assignment for Accounting Documents
Click on "Financial Accounting Document Types"
go to Accounting Documents WA, WI, WL and double click on them and change the number range to the new number range created.
Regards
AK

Error:while doing PGI in STO getting error

Dear sir,
while doing pgi in sto i m getting this error and i tried in obyc setting is there is there any other option to solve this isssue.
Account determination for entry CAIN AUM ____ ___ 7920 not possible
regards,
Debesh

Hi
Account determination for entry CAIN AUM ____ _ 7920 not possible
This is a clear OBYC error
Here CAIN is chart of accounts
AUM is transaction key
Go to OBYC select AUM double click that
system will ask for chart of accounts give CAIN as chart of accounts
maintain the necessary settings for 7920 and for the valuation grouping code
Here system has not given what is your valuation grouping code
In t code OMWD you can see what is the valuation grouping code assigned to your plant
make the necessary settings
I feel by chance or by mistake in your delivery doc there is a line item with 0 qty in both delivery and picking
That is why system has gone for AUM transaction key
check that and delete that item and then without the above said settings being maintained the PGI can get processed
Check and revert back
Regards
Raja

Update was terminated error ,while doing PGI

Similar Messages

Maybe you are looking for