JPY Currency issue in SRM 5 Limit Items

Hi
We are having an issue JPY Currency issue in SRM Limit Items (550 SP 13).
Basically the currencies like JPY, KWR where there are no decimals causes value to be multiplied by 100.
There are lot of notes and threads on JPY currency issues.
But I have not found one that helps fix SRM Limit Items.
Let me know if there is a note or thread that talks about it.
We are on SRM 550 SP 13.
Thank You
Nikhil

see MDM forum

Similar Messages

Import po JPY currency issue

Dear All,
We have a Import PO where the currency of that vendor is JPY which is having 4 decimals. The strange thing is in PO we have 2500 qty while we received the first schedule system is allowing to do GRN for any no of qty.
But for second schedule system is not allowing GRN and throwing Dump error at the tme of 105.
For eg:
PO no: 45000023 has 2500 qty but we did grn only for 100 qty then there is no issue it allowed to do GRN
Second time for 100 qty if we try system is throwing dump error
We created new po there also only for one tme system is allowing to do gr other wise it is not allowing. We did debugging but could not able to find.
Please suggest.

DEar Sir,
Please find the below dump error. I could not able to attach it as document
Category
ABAP Programming Error
Runtime Errors
MESSAGE_TYPE_X
ABAP Program
SAPMSSY0
Application Component BC-ABA-LA
Date and Time
27.03.2014 10:10:12
Short text
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
Short text of error message:
COMMIT WORK during ON COMMIT or ON ROLLBACK
Long text of error message:
Technical information about the message:
Message class....... 00
Number.............. 085
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
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:
"MESSAGE_TYPE_X" " "
"SAPMSSY0" or "SAPMSSY0"
"%_BEFORE_COMMIT"
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.
System environment
SAP Release..... 731
SAP Basis Level. 0006
Application server... "msqas"
Network address...... "192.168.140.89"
Operating system..... "Linux"
Release.............. "2.6.32-220.el6.x86_6"
Hardware type........ "x86_64"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 12
Shortdump setting.... "full"
Database server... "msqas"
Database type..... "ORACLE"
Database name..... "QAS"
Database user ID.. "SAPSR3"
Terminal.......... "C1031"
Char.set.... "C"
SAP kernel....... 720
created (date)... "Aug 15 2011 20:19:20"
create on........ "Linux GNU SLES-11 x86_64 cc4.3.4 use-pr101110"
Database version. "OCI_112, 11.2.0.3.0, V1, default"
Patch level. 100
Patch text.. " "
Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"
SAP database version. 720
Operating system..... "Linux 2.6"
Memory consumption
Roll.... 0
EM...... 37708272
Heap.... 0
Page.... 237568
MM Used. 1309640
MM Free. 2877528
User and Transaction
Client.............. 900
User................ "ADMIN"
Language key........ "E"
Transaction......... "MIGO "
Transaction ID...... "5331516F2A4E2866E1000000C0A88C59"
EPP Whole Context ID.... "5CF3FCE6DD4C1EE3ADABD70ED2D199C7"
EPP Connection ID....... 00000000000000000000000000000000
EPP Caller Counter...... 0
Program............. "SAPMSSY0"
Screen.............. "SAPMS380 0100"
Screen Line......... 3
Debugger Active..... "none"
Information on where terminated
Termination occurred in the ABAP program "SAPMSSY0" - in "%_BEFORE_COMMIT".
The main program was "SAPMS380 ".
In the source code you have the termination point in line 196
of the (Include) program "SAPMSSY0".
Source Code Extract
Line
SourceCde
166
rb_orders_wa-i_level = i_level.
167
insert rb_orders_wa into rb_orders index sy-tabix.
168
endif.
169
endif.
170
endform.
"%_order_form_for_rollback
171
172
173
174
* %_COMMIT_PREPARE
175
* Set date and time for aRFC
176
177
form %_commit_prepare using date time.
"#EC *
178
179
%_sys000-arfc-send_time = time.
180
%_sys000-arfc-send_date = date.
181
182
endform.
"%_commit_prepare
183
184
185
* FORM %_BEFORE_COMMIT
186
* called from RSYN commit.rs1
187
188
form %_before_commit.
"#EC *
189
data: l_oncom like sy-oncom.
190
data: txend type c.
191
192
* forbid COMMIT if already in ON ROLLBACK handling
193
* allow COMMIT during ON COMMIT for backward compatibilty
194
call 'GET_SWITCH_TXEND' id 'STATE' field txend.
195
if txend = 'R'.
>>>>>
message x085(00).
197
endif.
198
199
* COMMIT during CALL DIALOG/SUBMIT, POC, Update task
200
* or End Transaction event?
201
check sy-oncom <> 'N' and sy-oncom <> 'P' and
202
sy-oncom <> 'E' and sy-oncom <> 'V'.
203
* change sy-oncom to avoid recursion
204
l_oncom = sy-oncom.
205
sy-oncom = 'E'.
"E = Event Handling
206
207
* no escape out off this form other than ENDFORM
208
system-call state_limit set.
209
* Hook for Process Information Infrastructure
210
call function 'SPI_AGENT_COMMIT'.
211
* Raise event 'Commit Requested' for Object Manager
212
call method cl_os_transaction_end_notifier=>raise_commit_requested.
213
* restore sy-oncom
214
sy-oncom = l_oncom.
215
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
0
SY-DBCNT
0
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
ABAP Runtime Error
SY-MSGTY
X
SY-MSGID
00
SY-MSGNO
085
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
1
SY-DATUM
20140327
SY-UZEIT
101011
SY-XPROG
SY-XFORM
Active Calls/Events
No.   Ty.
Program
Include
Line
Name
4 FORM
SAPMSSY0
SAPMSSY0
196
%_BEFORE_COMMIT
3 FORM
SAPMS380
MS380F10
1287
DELETE_OLD_SNAP_RECORDS
2 FORM
SAPMS380
MS380F10
15
INIT
1 MODULE (PBO) SAPMS380
MS380O10
14
PBO_100_MAIN
Chosen variables
Name
Val.
No.
4
Ty.
FORM
Name
%_BEFORE_COMMIT
DP_J2EE_INACTIVE
0
4
04
TXEND
R
5
2
0
0
5200
%_SYS000-ARFC-DONTSEND
2
0
0
0
2000
%_PRINT
000
0###
2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2000200020002000300030003000200020002000200020002000200020002000200020002000200020002000200020
SY-REPID
SAPMSSY0
5454555322222222222222222222222222222222
310D339000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5300410050004D00530053005900300020002000200020002000200020002000200020002000200020002000200020
SY-MSGID
00
33222222222222222222
00000000000000000000
00000000000000000000
00000000000000000000
30003000200020002000200020002000200020002000200020002000200020002000200020002000
%_SYS000
00000000000000
2333333333333332222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2000300030003000300030003000300030003000300030003000300030002000200020002000200020002000200020
RST_VB_DISPATCHING_INFO
0
A
0A
SPACE
2
0
0
0
2000
SY-MSGNO
085
333
085
000
000
300038003500
%_TIME_CONFIRMED
001000
333333
001000
000000
000000
300030003100300030003000
SY-MSGV1
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
2000200020002000200020002000200020002000200020002000200020002000200020002000200020002000200020
SY-MSGV2
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
2000200020002000200020002000200020002000200020002000200020002000200020002000200020002000200020
SY-MSGV3
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
2000200020002000200020002000200020002000200020002000200020002000200020002000200020002000200020
SY-MSGV4
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
2000200020002000200020002000200020002000200020002000200020002000200020002000200020002000200020
SY-ONCOM
N
4
E
0
0
4E00
SYST-REPID
SAPMSSY0
5454555322222222222222222222222222222222
310D339000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5300410050004D00530053005900300020002000200020002000200020002000200020002000200020002000200020
TH_BOOL
0
0
00
%_DUMMY$$
2222
0000
0000
0000
2000200020002000
No.
3
Ty.
FORM
Name
DELETE_OLD_SNAP_RECORDS
DELT-DATUM
00000000
33333333
00000000
00000000
00000000
30003000300030003000300030003000
%_DUMMY$$
2222
0000
0000
0000
2000200020002000
DELT-UZEIT
000000
333333
000000
000000
000000
300030003000300030003000
SY-REPID
SAPMS380
5454533322222222222222222222222222222222
310D338000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5300410050004D00530033003800300020002000200020002000200020002000200020002000200020002000200020
DELT-AHOST
22222222222222222222222222222222
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
2000200020002000200020002000200020002000200020002000200020002000200020002000200020002000200020
SYST-REPID
SAPMS380
5454533322222222222222222222222222222222

Contracts on Limit Items SRM 7

Hi,
We running SRM 7 with extended classic scenario and with ECC EHP 4.
I have received info from SAP that you can´t use contracts on limit items when using extended classic scenario, is there any workaround for using contracts on limit item?
BR
Jonas Andersson

Hello,
As far as I know, this is a technical limitation. A work around would affect other functionalities.
Note 1358679 corrected such issue.
Regards,
Ricardo

SC limit item currency change

Hello,
After creating the SC with limit items, in the soco we create a held PO so that we could change the vendor.
Say SC with 9000 quantity price 1 SEK.
1. In the held PO for the user is changing the currency to EUR and reducing the corresponding quantity to 90 (CONVERSION 1 EUR = 10SEK) and creating the PO.
2. However the SC reappears in the soco with 9000-90 quantity and SC currency SEK. So with this, more POs can be created using step 1.
I checked few notes corresponding to BBP_GET_STATUS_2 and clean_req_req however from the code it looked like only the quantity is considered to set the sourcing indicator and not the net value.
Has anyone faced this problem? Any hints about how to approach this.. I suppose it is a standard error and any BADI changes may not be a good solution.

Very well Sanjay. It was very helpful information. I checked in general it is only quantity that is considered for sourcing.
However regarding the indicator mentioned, I am unable to see the checkbox to set the complete requirement indicator in the item data tab of the PO. We are using SRM 5.0 with SP08. I checked all the sub-tabs like Basic data, partner etc, but was not able to find it. I checking on the PO (BBP_POC) which is on held status.
I also checked the BADI BBP_UI_CONTROL_BADI but there is no method concerning PO and this BADI is not implemented anyway. I checked both in the display mode and the change mode. Is there some specific customization required for activating this?
Thanks again for the info.
Rgds
Swetha

SRM Local Purchase Order with both a standard line item and limit item...

In SRM is it standard that you can create a local purchase order from the sourcing cockpit that contains a mix of limit items and standard items?
I know this can be done in R/3.

Paul,
I am a functional/business person, and we are running SRM550 in extended classic, linking to ERP backed.
From our business point of view it makes little sense to mix a limit item with one or more standard catalog item. SAP standard SRM 550 actually stops our users from doing this.
For those who are not aware of the differences I will elaborate.
A standard item is either from a Free Text entry process with the process being completed by a professional purchaser or a catalog item either internal to SRM, or maybe from an external website.
Limit orders are value based and are mostly used for the payment of Utility bills, or for services. We don't use services at all.
In our business we use limit orders for an Electricity Bill for example.
When the user confirms a limit order the quantity should always be 1 and the user enters the value of the item.
The Invoice entry team then needs to match the Invoice to the GR line. It's at this point that if you have Limit items and standard items mixed our invoice entry team could run into problems.
We are aware that it is not recommended practice for Limit orders to have GR and if you can avoid this step then you should. Unfortunately our operating model insist on everything being confirmed and in the case of limit orders this can cause us invoice blocking issues.
Limit orders are normally set up to run for a full FY so the addition of standard catalog items to a limit order makes little or no business sense.
If a user added two limit items to a shopping cart for the same supplier our system would produce two PO's for the supplier to use.
We actually avoid transmitting Limit order details to our suppliers as this would indicate the maxiumum value they could invoice us for, businesses just don't do that. We just send them the PO number and description of the item. This provides them with a PO Ref number to puton their invoices.
As we are still running SRM 550 maybe someone with SRM 7 knowledge would care to expand on this analysis?
Hope this helps?
Allen
PS We don't use the Sourcing Cockpit, just read your earlier response
Edited by: Allen Brooks on Mar 3, 2010 3:22 PM

SRM 7.0 - Unconfirmed PO limit items not showing up when creating Invoice

Hi Guys,
For PO standard items, when creating an invoice and is unconfirmed, these items still show up in the invoice screen and the invoice gets created with the status 'Waiting for preceding document'. For unconfirmed limit items, these items do not show up at all in the creation of the invoice and displays an error. My question is how will I make the unconfirmed limit items scenario work just like the standard items scenario whereby instead of the unconfirmed limit items not showing up and generating an error, they will show up and have the invoice created with the status 'Waiting for preceding document'?
Thanks in advance!

Is this thread still valid? If not, please close the thread.
If so, as no response has been submitted, please rephrase your question and/or provide further information to describe your requirement.
Thanks
Jason
SDN SRM Moderator Team

Unable to hide feilds for a limit item at PO level in SRM 7.0

Hi,
Currently we are working in SRM 7.0. extended classic scenario. While creating a limit item at PO level we are unable to control the custom feilds in general data tab.
We have created some custom fields. And we are trying to control (Visible,Enable & Required) these custom fields from IMG settings (Customer Metadata for item fields in Normal entries) for LIMIT items at PO Level. But we are unable to control.
Where this is working fine at Shopping cart level.
Can anybody help me in this regard.
Thanks.
Regards,
Kalyani

Please refer to this link.
https://websmp105.sap-ag.de/~sapidb/011000358700001969972008E.pdf
This has everything you need to know about extending fields and controlling there behaviour on UI.
Regards
Mustameer

Creating Limit item throgh Catalog in SRM 7.0

Hi,
We have a scenario to create " Limit items" in SRM 7.0 using Catalog.Can we create "limit shopping carts" in srm using catalogs? is it standard or required any customization?
Even though, we are having order type as an identification parameter, still when we add a limit item through Catalog link, it treats it as a catalog order.Please help, if there is any way to integrate this.
Thanks
Ajit.

Hi,
As far as I know this is not possible, maybe someone can correct me though
Regards,
Jason

SC (SRM) = PO (BE) with limit item (Itm.Cat = B)

Dear all,
in SRM I create a SC with two items, the first item is quit normal (material, cost center assignment, etc). The second item is a copy of the first one, unit of measure is LE. Now when this SC is transfered into the BE I want the PO to contain a limit item ( item category = B). The customer is using the classic scenario and upgraded from SRM4.0 to SRM7.0.
What are the important flags/tables etc. in BADI BBP_CREATE_PO_BACK, method FILL_PO_INTERFACE.
Currently I'm filling the following parameters:
PO_SRV_ACCOUNT,
PO_LIMITS
zusätzliche Kontierungsinformationen für Serviceposition
      clear ls_po_srv_account.
      ls_po_srv_account-pckg_no    = ls_po_items-pckg_no.
      ls_po_srv_account-percentage = '100'.
      ls_po_srv_account-serial_no = '01'.
      append ls_po_srv_account to po_srv_account.
PO Limits
      ls_po_limits-limit     = ls_po_items-net_price.
      ls_po_limits-exp_value = ls_po_items-net_price.
      APPEND ls_po_limits TO po_limits.
The PO will be created in the backend with the two items, but the item category of them is blank (= normal item).
Does anyone of you have an idea what is missing?
Kind regards,
Thomas

Hello Laurent,
I don't know. I think this is something from former times when they had been running on SRM4.0 and they simply took over.
The UoM is LE and in the BE there should be an appropriate line item in the PO with category B (= Limit).
How do I define limit items in SRM?
Kind regards,
Thomas
Edited by: Thomas Mueller on Dec 16, 2011 12:36 PM

Asian (JPY) currency Decimal Places Issue

HI All,
Need your help, we have a program which creates a BDC session and when the user tries to process it it throws an errror for amount in asian currencies like JPY - no decimal places allowed for currency, in the background it calls the FBB1 transaction.
The original amount is in USD however after conversion when we store it back to amount field which is of type
"glpct-tslvt" it stores the amount in JPY currency with decimal places so for example :
USD amount = 93,214. 00
JPY amount = 115,021. 86
guess the amount is stored with decimals in BSEG table, so now when we try to process the session with the JPY amount with decimals it throws an error.
I have tried the
CALL FUNCTION 'CURRENCY_AMOUNT_SAP_TO_DISPLAY'
and
CALL FUNCTION 'BAPI_CURRENCY_GETDECIMALS'
it gives me the correct value for amount so for above example JPY amount = 115,021. 86 by using the mentioned two methods i am able to get the currency in this format 11502186.00 but still has two decimal places, i think it still will not work when we process the session for FBB1.
Need your help people, appreciate your co-operation.

sorry to revive an old thread...but we are having an issue with JPY in our electronic bank statements.
the BAI format for our JPY account has for example 900 yen which according to our finance department is really 9 yen. the bank claims this is a known issue and the BAI format documentation seems to be confirming the bank's position in that the decimals are implied according to the currency code (whatever that means in SAP terms is a bit foggy to us).....
currently we wrote a custom code to suppress the last two zeros (when they are zeros) but i feel this error is caused either by a wrong setting in our currency or translation tables in SAP or something else since our feeling is that this should work right out of the box without any custom programming...any ideas???...where we shoudl start looking in our currency config....does the 100:1 or 1:1 translation ratio between JPY/USD make any difference...should we try and use a function module to convert the currency ...any ideas or hints are welcome
thanks
Ram
[email protected]

Inforecord Net price issue JPY currency

Hi Experts
I am facing an issue in Inforecords Net price when net price is mainatined in JPY currency
The data maintained and as can be seen using ME13 for Net Price for example is 1 JPY
Where as when I fetch this data using EINE table the value is shOWNn as 0.01
( Same is the case when Net price is maintained as 232,687 JPY. In EINE table NET price field this is shown as 2326.87JPY
Please advice why the system behaviour is as mentioned above . Also how can we overcome this issue.
Thanks and Regards
Vikrant

This is because the field is technically defined as currency field with 2 decimals.
Please read OSS Note 53206 - Processing of currency fields.
it explains whatyou have to do in your programs

Issue with limit item in ECC

Hi,
We are facing one issue with Shop with Default (Limit items) in ECC.
In basic data tab, if any value is entered in any field and press enter then that value is not getting reflected in that field. But if we enter the value and click on check then that value get reflected .
The reason is BBP_DOC_CHANGE_BADI is not get triggered if we press only enter but it gets triggered if click on check.
We also tested in Classic case , its working fine in Calssis case.
Do you have idea for this?
Do you know any note that we have to apply for ECC?
Thanks in Advance.
Snehal

The lineitems and such will always be saved with English values. You are supposed to for display purposes, re-lookup the product in the appropriate language when you display it on the cart and what not.
Brad Foley | www.blfoley.com |
www.darklakesoftware.com

Goods Recipts for Limit item SC

Hi,
When we create shopping cart with limit item and choose the "confirmation and invoice option" during the Limit SC creation the backend PO is created with item category 'D'. The service PO is created, but there is no data updated in service tab at the item level, there is only line item created in item overview with the expected value as the net price and Qty as 1 PU. But without the line item in service tab at the item level we cannot do the planned service entry sheet.
Now with the current scenario when i try to do the confirmation in EBP, i have add description, QTY and value details and then i am able to post the document.The staus shows as document posted in backend but when i click to view the document, there is no document to be displalyed. The confirmation data is not getting updated in the follow on documents or in the purchase order history in R/3.
In R/3 i am not able to enter the service entry sheet for the corresponding PO, it says no line items in the PO. Thats because there is no line item in the service tab. I am not able to post the invoice since the GR based IV is checked in PO.
Now my question is whether this is the standard behaviour, cant we do service entry sheet for these kind of PO. How to get the line item detail in the service tab in item level. What is the advantage of this function in SRM if we cannot post service entry sheet.
Please suggest how to overcome this issue.
Regards
GGL

Hi Sanjeev,
I checked the ESSR table and the document is not getting updated. I found that there is an error meaasge occuring when i try to post the service entry sheet. The error is "Express document "Update was terminated" received from author" and when i check my inbox i see the below message
Update was terminated
Update was terminated
System ID....   UDS
Client.......   030
User.....   N0208
Transaction..   ML81N
Update key...   4A0DF49ADEE1006EE1008000820A0466
Generated....   16.05.2009, 11:03:35
Completed....   16.05.2009, 11:03:35
Error info...   SG 105: Enter rate GBP
Error info Enter rate in GBP, i check the service entry sheet and the currency is maintained in GBP and all the other entries looks fine. I am not sure why i am getting this message.
Please let me know if this is related to any config or how to to rectify this.
                                                                                Regards
GGL

Contract Release value is not updated with Limit item value

We have SRM 4.0 with ECS scenario.
Contract are created in SRM and replicated to ERP.
If we create PO with Service line and Limit line using contract in both of these line items, contract Release value is getting updated only with Service line item value.
But the contract Total value is the addition of Service and Limit value of PO.
Why Contract Release value is not getting updated with Limit item value. Please help as early as possible.

Hi Sandeep
Yes. there are various reasons .upon your contract incorrect status and linkage not establised / or more attachment in SRM GOA.
what type of contract are you using? GOA or CCTR
If it is GOA - which version of SRM and service pack ?are you in ?
If it is a GOA , BLAREL idoc might failed to post the release value in the SRM .
How contracts are created material / mat group ?
to fix or understand the issue, you need to recreate the issue.
what is the ERROR in BLAREL in SRM idoc monitoring ?

Deleting Limit Items on PO even though follow on documents exist

Dear SRM Experts
I am hoping someone can explain the below behaviour:
Where PO's have follows on documents i.e. confirmation and /or invoice you cannot delete PO's items on a PO. This makes sense.
However we also have PO's with Limit items(created via limit type shopping carts) and even though the PO's have been confirmed and invoiced we can still delete the items on the PO. Is this standard behavior or a bug?
Why then can you not delete normal items but can delete limit type items where follow on documents have been posted for a PO?
Thanks
Nishad.

Hi
Which SRM version are you using ?
Incase of Limit Items, it is a bug.
We have raised a similar issue with SAP some time back and still waiting for SAP to get back on this.
Hope this will help.
Please reward suitable points.
Regards
- Atul

JPY Currency issue in SRM 5 Limit Items

Similar Messages

Maybe you are looking for