FM Update and Commitment Category

Hi,
Company wants each document should be update in Funds management. System only update the document of commitment item which have catgory (30/3) either it is real or statiscal.
I just want to know the soultion , should I change the catgory of all commitment item ? or any other advise. Company even want update of commitement item (60/2, 60/3) which is assigned to customer/vendor reconciliation account. what is the impact on system i change thecategor of this commitement item?
Thanks

Thanks for detailed reply.
I know when FM is active, every document is updated in FM as well. I think it needs to clear my requirement .
client has 25 Commitment items which are assigned to General ledger and out of 15 ,client want to watach the budget. I mean avaliablity control must work . I created these 15 commitement item (30/3) in system and made assignement to GL ( Expense/Balance Sheet). as repuirement .Client entered Budget and avaliability control working fine. at the time actual posting system also create the FM document . which is OK
10 Commitement item which they want to assigned General ledger ( Cash & Bank account, reconciliation account Clearing Account, loan, Capital etc), Client do not want to make budget of these commitement item. I created commitement item for reconciliation account ( vendor/Customer) with catogory 60/2/3, some commitementitem with catogory 90/1. and made assignement to GL as per requirement. But at the time of actual posting , system does not create FM document for these commitment item. Client want FM document of these commitement item, but not real. Thats mean they need statiscal posting for these Commitement item.
Now please guide if change the commitment catogry (30/3) with statiscal indicator , system create the FM document and the client requirement fulfill, but need to know the impact on system. they want to get the line item report of these commitement item which is usful for their reporting, they can get from FI ( by selecting GL which are relevant to Commitement Item )as well but they need from FM
What is your opinion, should I change the Commitement item category or any other solution or should i convince user to get this report from fi line report by adding your general ledger as per commitement item....................
Thanks
Edited by: SAP 2008 on Aug 3, 2009 3:12 PM

Similar Messages

MM-FM integration. How to stop update of Fund Center and Commitment Item

Hello!
Anyone please help. MM-FM integration.
Our problem is after automatic creation of PR and PO from work orders, and the fund center and commitment item in the PR and PO has been changed/updated by the user, and then we change something in the work order and save it, the fund center and commitment item of the PR and PO goes back to default value (based on FMderive). Is there a way to stop this?
Thanks in advance for your help.
Regards,
Rona

It seems like you have selected "Do not overwrite target values" option in both Funds Enter and Commitment Item in the derivation rule defined.
Go through SAP Note 666322, make sure the Trace feature in On and then choose the option "Overwrite Target Values" in both Funds Enter and Commitment Item in your derivation rule. After that, see the Difference before and after values in the trace log created after performing the derivation rule.
I am sure this will help.
Regards,
Amar Lal

Fund center and commitment item not updated

Hi!
We are using Funds Management together with SRM. When we change the value of e.g. cost center and not the account assignment itself we do not get an update on fund center. When changing account we do not get an update on commitment item either. This is standard SAP and we have been asked to use BBP_DOC_CHANGE_BADI. Have anyone else had this problem?
I would really appreciate if anyone have some code for this BADI or any other badi e.g. BBP_ECS_PO_OUT_BADI. It is only important that changes in PO when replicated to back end results in the correct update of commitment item and fund center.
Sincerely
Andres

Solved through BBP_DOC_CHANGE_BADI

How update Fund Center and Commitment Item after posting

hi Experts,
Funds management was activated during the year and hence there are few open items saved without capturing Fund Center and Commitment Item. When i tried to clear these open item i get the following error
Line in document xxx xxxxxxxxxxxx does not contain any commitment items
Is there any program which i can use to update derivation to the already posted line item
Thanks in Advance

Hi,
Solutions proposed by Alexey are good if FM document was created for the FI documents in question. If, however, no FM document was created, reassignment process won't help. You can try FMN0 transaction after creating a derivation rule in FMDERIVE for these documents, but I cannot confirm that it would be sucessful as FMN0 transaction is not perfect.
The solution could be updating FI tables (BSEG/BSIS/BSAS) with FM assignment (fund centre/commitment item) and only then running FMN0 transaction. In this case, FM document will be created and you'll be able to process the items.
Regards,
Eli

How often "New and Noteworthy" category is updated in App Store

Please let me know how often "New and Noteworthy" category is updated in App Store in different countries? It seems that it is updated every Friday in USA App Store. What about other countries?

Hmm I heard it was updated on Thursdays?

Financial transaction and commitment item category

Hello,
Can any one suggest what financial transaction and commitment item category can be used when creating the following commitment items:
u2022     Value added tax (VAT)
u2022     tax on profits
u2022     before-tax income
u2022     nett income
u2022     net financial result
And moreover, should such a commitment items be created?
Thanks
Irina

Hi Irina,
As I said, the real question is whether you are going to use these commitment items for budget management. If not, it does not really matter if it will be defined 50/2 or 50/3 - in any case, the AVC will not be applied to these lines. It's not even necessary to define a separate commitment item for these G/Ls; it's possible to define one dummy commitment item for all transactions which are not relevant for budget activities.
Regards,
Eli

Return Sales order - update of Item category change

Hi
We are creating the Return Sales order with respective original sales order.
After copying the line item details in to return sales order, we are not able to change item category to another. Since item category is in display mode(grayed out).
We tried with
1.Transaction varant, it is not helpful.
2.Maintained the item category which is required in item category determination(Manual entries)
Though we are able to change the item catgory in the sales order through some user exit, price condition are in active status. we are doing price update, but still condition types are still in-active.
Please help, how to change the item cateogry and to redetermine the price based on the item category in sales order.
Thanks & Regards,
Rajesh.

Then how do you settle it with the customer? He has still paid for the original materials and has returned some or all of them. He is still going to be invoiced for the full quantity. There should be some way to either replace the materials or give him a credit memo
but coming to Gunda's query, the only way I see to map this is to create a different order type ZRE which is a copy of RE and item category ZREN which is a copy of REN. In ZREN, turn on Pricing. Maintain copy controls from OR to ZRE and keep the pricing condition type Manual. Then whenever the business decides not to give the customer a refund, go to the item conditions, set the pricing condition value to 0 and save the order

Control multiple updates and queries within one transaction in JPA

Hi,
I have a question regarding control multiple updates and queries within one transaction. We are using EclipseLink 2.3.1. With below code, will I be able to:
- have all insert, update, select queries committed in one transaction;
- queryGetBalance will return the latest OrgBalance after update;
- if one fails, everything rolls back.
Thanks!
Jeffrey
PS: I realized that I cannot use em.getTransaction().begin() and em.getTransaction().commit(), since I am using JTA.
=============
@PersistenceContext(unitName="Test")
EntityManager em;
em.setFlushMode(FlushModeType.COMMIT);
newTransaction.setAmount(1000);
newTransaction.setType("check");
em.persist(newTransaction);
orgAudit.setUpdateUser("Joe")
orgAudit.setupUpdateTime(time);
em.merge(orgAudit);
Query queryUpdateBalance = em.createQuery("update OrgBalance o set o.balance = o.balance + :amount where orgId = :myOrgId");
queryUpdateBalance.setParameter("amount", 1000);
queryUpdateBalance.setParameter("myOrgId", 1234);
Query queryGetBalance = em.createQuery("select OrgBalance o where o.orgId = :myOrgId");
queryGetBalance.setHint("javax.persistence.cache.storeMode", CacheStoreMode.REFRESH);
queryGetBalance.setHint("javax.persistence.cache.retrieveMode", CacheRetrieveMode.BYPASS);
queryGetBalance.getResultList();
em.flush();
Edited by: JeffreyW on Dec 12, 2011 10:34 AM

Yes, the operation will be in a single transaction, assuming you are using a JTA managed SessionBean and the code is part of a SessionBean method.

Updating and deleting records in access DB

i'm trying to make multiple updates and deletes in a access DB and it doesn't work.
my program executes lot's of updates and delete statements when saving, but I only commit in the end when I know all the statements finished ok.
I can't make it a batch update since I need to retrieve the auto-number that access issues me on some of my tables.
I know it's kinda fuzzy, but my program is SO big already, and I can't really put the code in here - it wouldn't do much good.
what I will do is write what my log shows (i issue a log output whenever there's a executeQuery/Update and before commit/rollback
DBG : 29/04/03 : UPDATE CASES_T SET CASE_office_case_id = 1 ,CASE_year = 2 ,CASE_total_debt = 10009 ,CASE_is_limited = true ,CASE_monthly_payment = 400 ,CASE_hotzlap_case_id = ' - - - ' ,CASE_status = 26 WHERE CASE_tech_id = 5
DBG : 29/04/03 : SELECT count(*) from CASES_OWEES_T where CAOW_Tech_Id = 23
DBG : 29/04/03 : UPDATE CASES_OWEES_T SET CAOW_case_tech_id = 5 ,CAOW_id_number = '046259990' ,CAOW_first_name = '��' ,CAOW_last_name = '��' ,CAOW_work_place = 'jjjjjjjjjjjjj' ,CAOW_address = '1jjjjjjjjjjjj' ,CAOW_telephone = '09-8099999' ,CAOW_pelephone = '000-000000' ,CAOW_hotzlap_case_id = ' - - - ' ,CAOW_is_valid_address = false WHERE CAOW_TECH_ID = 23
DBG : 29/04/03 : SELECT count(*) from CASES_OWEES_T where CAOW_Tech_Id = 24
DBG : 29/04/03 : UPDATE CASES_OWEES_T SET CAOW_case_tech_id = 5 ,CAOW_id_number = ' ' ,CAOW_first_name = '��' ,CAOW_last_name = '��' ,CAOW_work_place = '��' ,CAOW_address = '��?' ,CAOW_telephone = ' - ' ,CAOW_pelephone = ' - ' ,CAOW_hotzlap_case_id = ' - - - ' ,CAOW_is_valid_address = true WHERE CAOW_TECH_ID = 24
DBG : 29/04/03 : SELECT count(*) from CASES_INNER_CASES_T where CICA_Tech_Id = 10
DBG : 29/04/03 : UPDATE CASES_INNER_CASES_T SET CICA_case_tech_id = 5 ,CICA_debt = 5000897 ,CICA_winner_name = '��' ,CICA_lawyer_tech_id = '6' ,CICA_hotzlap_case_id= '02-22122-22-2' WHERE CICA_tech_id= 10
DBG : 29/04/03 : SELECT count(*) from CASES_INNER_CASES_T where CICA_Tech_Id = 11
DBG : 29/04/03 : UPDATE CASES_INNER_CASES_T SET CICA_case_tech_id = 5 ,CICA_debt = 20008 ,CICA_winner_name = '��' ,CICA_lawyer_tech_id = '2' ,CICA_hotzlap_case_id= '02-22222-22-2' WHERE CICA_tech_id= 11
DBG : 29/04/03 : SELECT count(*) from CASES_INNER_CASES_T where CICA_Tech_Id = 14
DBG : 29/04/03 : UPDATE CASES_INNER_CASES_T SET CICA_case_tech_id = 5 ,CICA_debt = 129 ,CICA_winner_name = '' ,CICA_lawyer_tech_id = '4' ,CICA_hotzlap_case_id= '02-22222-22-2' WHERE CICA_tech_id= 14
DBG : 29/04/03 : SELECT count(*) from CASES_CUSTOMER_CARDS_T where CUCA_Tech_Id = 23
DBG : 29/04/03 : UPDATE CASES_CUSTOMER_CARDS_T SET CUCA_case_tech_id = 5 , CUCA_sum = 324 , CUCA_fee_plus_maam = -38.0 , CUCA_for_division = 285.0 , CUCA_voucher = '3222 ' , CUCA_date = '2003-04-24' , CUCA_in_or_out = true WHERE CUCA_tech_id = 23
DBG : 29/04/03 : SELECT count(*) from CASES_CUSTOMER_CARDS_T where CUCA_Tech_Id = 22
DBG : 29/04/03 : UPDATE CASES_CUSTOMER_CARDS_T SET CUCA_case_tech_id = 5 , CUCA_sum = 324 , CUCA_fee_plus_maam = -38.0 , CUCA_for_division = 285.0 , CUCA_voucher = '2222 ' , CUCA_date = '2003-04-23' , CUCA_in_or_out = true WHERE CUCA_tech_id = 22
DBG : 29/04/03 : SELECT count(*) from CASES_CUSTOMER_CARDS_T where CUCA_Tech_Id = 21
DBG : 29/04/03 : UPDATE CASES_CUSTOMER_CARDS_T SET CUCA_case_tech_id = 5 , CUCA_sum = 100 , CUCA_fee_plus_maam = -11.0 , CUCA_for_division = 0.0 , CUCA_voucher = '2222 ' , CUCA_date = '2003-04-23' , CUCA_in_or_out = true WHERE CUCA_tech_id = 21
DBG : 29/04/03 : SELECT count(*) from CASES_CUSTOMER_CARDS_T where CUCA_Tech_Id = 20
DBG : 29/04/03 : UPDATE CASES_CUSTOMER_CARDS_T SET CUCA_case_tech_id = 5 , CUCA_sum = 1000 , CUCA_fee_plus_maam = -118.0 , CUCA_for_division = 882.0 , CUCA_voucher = '1111 ' , CUCA_date = '2003-04-23' , CUCA_in_or_out = true WHERE CUCA_tech_id = 20
DBG : 29/04/03 : SELECT count(*) from CASES_INVESTIGATIONS_T where CAIN_Tech_Id = 16
DBG : 29/04/03 : UPDATE CASES_INVESTIGATIONS_T SET CAIN_case_tech_id = 5 ,CAIN_text = '' ,CAIN_was_declared_limited = false ,CAIN_date = '2003-03-01' ,CAIN_rulling_effective_date = '2003-02-01' ,CAIN_payment_amount = 400 WHERE CAIN_TECH_ID = 16
DBG : 29/04/03 : SELECT count(*) from CASES_INVESTIGATIONS_T where CAIN_Tech_Id = 12
DBG : 29/04/03 : UPDATE CASES_INVESTIGATIONS_T SET CAIN_case_tech_id = 5 ,CAIN_text = '' ,CAIN_was_declared_limited = true ,CAIN_date = '1970-01-01' ,CAIN_rulling_effective_date = '1905-03-06' ,CAIN_payment_amount = 90 WHERE CAIN_TECH_ID = 12
DBG : 29/04/03 : SELECT count(*) from CASES_INVESTIGATIONS_T where CAIN_Tech_Id = 10
DBG : 29/04/03 : UPDATE CASES_INVESTIGATIONS_T SET CAIN_case_tech_id = 5 ,CAIN_text = '' ,CAIN_was_declared_limited = false ,CAIN_date = '1970-01-01' ,CAIN_rulling_effective_date = '1990-01-30' ,CAIN_payment_amount = 89 WHERE CAIN_TECH_ID = 10
DBG : 29/04/03 : DELETE FROM CASES_INVESTIGATIONS_T where CAIN_tech_id = 9
DBG : 29/04/03 : DELETE FROM CASES_INVESTIGATIONS_T where CAIN_tech_id = 9
DBG : 29/04/03 : DELETE FROM CASES_INVESTIGATIONS_T where CAIN_tech_id = 14
DBG : 29/04/03 : DELETE FROM CASES_INVESTIGATIONS_T where CAIN_tech_id = 14
DBG : 29/04/03 : DELETE FROM CASES_INVESTIGATIONS_T where CAIN_tech_id = 13
DBG : 29/04/03 : DELETE FROM CASES_INVESTIGATIONS_T where CAIN_tech_id = 13
DBG : 29/04/03 : DELETE FROM CASES_INVESTIGATIONS_T where CAIN_tech_id = 11
DBG : 29/04/03 : DELETE FROM CASES_INVESTIGATIONS_T where CAIN_tech_id = 11
DBG : 29/04/03 : SELECT count(*) from CASES_PAYMENTS_T where CAPY_Tech_Id = 71
DBG : 29/04/03 : UPDATE CASES_PAYMENTS_T SET CAPY_case_tech_id = 5 ,CAPY_sum = 400 ,CAPY_exception_text = '' ,CAPY_is_exception = true ,CAPY_voucher = '' ,CAPY_date = '2003-04-01' ,CAPY_is_paid_in_hotzlap = false WHERE CAPY_TECH_ID = 71
DBG : 29/04/03 : SELECT count(*) from CASES_PAYMENTS_T where CAPY_Tech_Id = 70
DBG : 29/04/03 : UPDATE CASES_PAYMENTS_T SET CAPY_case_tech_id = 5 ,CAPY_sum = 400 ,CAPY_exception_text = '' ,CAPY_is_exception = true ,CAPY_voucher = '' ,CAPY_date = '2003-03-01' ,CAPY_is_paid_in_hotzlap = false WHERE CAPY_TECH_ID = 70
DBG : 29/04/03 : SELECT count(*) from CASES_PAYMENTS_T where CAPY_Tech_Id = 69
DBG : 29/04/03 : UPDATE CASES_PAYMENTS_T SET CAPY_case_tech_id = 5 ,CAPY_sum = 400 ,CAPY_exception_text = '' ,CAPY_is_exception = true ,CAPY_voucher = '' ,CAPY_date = '2003-03-01' ,CAPY_is_paid_in_hotzlap = false WHERE CAPY_TECH_ID = 69
DEV : 29/04/03 : commit

sure - I don't get any exception. the data just
doesn't show in the DB. (no updating/deletion of
records)
as I wrote before - when the the programm commits the
changes and does the next select command it seems as
if the data was changed/deleted but if I check the DB
with access or if I restart the prgoram then I see
that the data didn't change.
Access/jdbc-odbc has a problem where modifications are not 'commited' when the statement completes. Instead one must do one of the following:
1. Explicit commit.
2. Simple select after statement.
3. Close the connection.
Presumably you are doing 1.
Since other than this it does work, it suggests one of the following.
1. Something is wrong with your environment. For instance you are looking at the wrong database. Or not refreshing. Or something else like that.
2. You are using something besides a simple connection - like opening it with 'scroll insensitive'.
3. The complexity is causing it to lose an error message. This can be tested by doing each statement individually and verify that none produce an error.
4. Maybe you found a bug. You can turn on ODBC tracing via the applet panel and see if digging through all of the detail provides any clues (you can also do this with 3 above.)

Pur Grp and product category changes made in R3E not reflecting back to SRM

Need to investigate why changes made to Purchase Requisitions in SAP R/3 (Purchasing Group & product category) doesn't feed back to SRM.
Purchasing Group and product category changes made in R3E do not reflect back in SRM.

Hi Sanjay,
You should also schedule report BBP_GET_STATUS_2 (updating requirement coverage
requests) to run in the Enterprise Buyer system, so that information on the status of purchase
requisitions, purchase orders, and reservations is up-to-date.
I hope,this helps.
Regards,Nishant

Nsert/Update and Add Column at the same Table and at the "same" Time

Hello,
I want Insert/Update and Add Column at the same Table and at the "same" Time but in different sessions.
Example:
At first the "insert/update" statement:
Insert into TestTable (Testid,Value) values (1,5105);
After that the "add" statement:
Alter table TestTable add TestColumn number;
- sadly now I get the message: ORA-00054: resource busy and acquire with NOWAIT specified
"insert/update" statement:
Insert into TestTable (Testid,Value) values (2,1135);
After that the execute commit.
I don't know when the first session set the commit statement so I want that the DB the "Alter Table..." statement execute if it's possible.
If it's possible I want to save a repeat loop with the "Alter Table..." statemtent.
Thanks for ideas

Well I want to walk in the rain without and umbrella and still stay dry, but it ain't gonna happen.
You can't run a DDL statement against a table with transactions pending. Session 2 has to wait until session commits or rollbacks (or until the session is killed). That's just the way it is.
This makes sense if you think about it. The data dictionary has to be consistent across all sessions. If session 2 was allowed to change the table structure whilst session 1 has a pending transaction then the database is in an inconsistent state. This is easier to see if you consider the reverse situation - the ALTER TABLE statement run by session 2 does a DROP COLUMN TESTID rather than adding a column: now what should happen to session 1's INSERT statement? You have retrospectively invalidated a statement that was perfectly legal when it was executed.
If it's possible I want to save a repeat loop with the "Alter Table..." statemtent.Fnord.
Cheers, APC

FM/BAPI to update the rate category for the device/installation

Hi,
I need to update a new rate category for a device.
Please let me know if there is BAPI/FM which will update the rate category for a device.
Regards
Shiva

Hi Shiva,
First of all, can you clarify if you want to update the rate category - Is it at the Installation Level or at the Device Level.
For updating the rate category at the installation level, go to Business object INSTLN,and then make the necessary changes in Change Installation without dioalog.Pass the input parameters as required for the Method.
If you find this answer helpful, please reward points.
Amitav

Changing of data class and size category for keyfigures .

Hi,
I am not able to change the data class and size category for keyfigures .
can you please let me know how to enable the changing of data class and size category for keyfigure under Maintain DB storage parameters.

Ok then it sounds like your primary key of 8 fields and secondary index of 3 non-unique fields appear somewhat similar to the database and it wrongly uses the secondary index. Perhaps you can try to declare the table as a SORTED table with index fields as key. I doubt this will do any good, but you can try.
You can try to deactivate the sec. index if it is not being used.
Or by far the best but also debatable, try to pass hints to the SQL parser by %_hints statement. Please refer to SAP note 129385 for details on hints in general and note 772497 for various hints statements for ORACLE DB. This will surely make the DB interface use the primary index and the update would be faster. But with 1 million records, hopefully you are not looking at response time in micro seconds, are you?
rgds,
Prabhu

Corellated update AND merge(update only)

Hi ,
I have few corellated updates in my code , which i though ,i can replace with 10g new Merge update only stmt.
But to my surprise , the sql using merge is showing more cost and using full table scan.
Please find below the sql stmts. below(example). Am using Oracle 10.2.0.1
create table t1 as select * from all_objects where rownum<10000;
create table t2 as select * from t1 where rownum<10000-200;
create unique index t1_objId_ind on t1(object_id);
create unique index t2_objId_ind on t2(object_id);
--Corellated updated query
update t1 set t1.object_name= (select upper(t2.object_name) from t2 where t1.object_id=t2.object_id)
where T1.OBJECT_ID IN (SELECT t2.object_id from t2);Explan for above update stmt.
| Id | Operation                    | Name         | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | UPDATE STATEMENT             |              | 9139 |   383K|    37   (9)| 00:00:01 |
|   1 | UPDATE                      | T1           |       |       |            |          |
|   2 |   NESTED LOOPS               |              | 9139 |   383K|    37   (9)| 00:00:01 |
|   3 |    TABLE ACCESS FULL         | T1           | 9138 |   267K|    35   (3)| 00:00:01 |
|* 4 |    INDEX UNIQUE SCAN         | T2_OBJID_IND |     1 |    13 |     0   (0)| 00:00:01 |
|   5 |   TABLE ACCESS BY INDEX ROWID| T2           |     1 |    30 |     2   (0)| 00:00:01 |
PLAN_TABLE_OUTPUT
|* 6 |    INDEX UNIQUE SCAN         | T2_OBJID_IND |     1 |       |     1   (0)| 00:00:01 |
Predicate Information (identified by operation id):
   4 - access("T1"."OBJECT_ID"="T2"."OBJECT_ID")
   6 - access("T2"."OBJECT_ID"=:B1)I wanted to eliminate the corellated update , So i wrote using MERGE as below
MERGE INTO T2
USING T1
ON (t1.object_id=t2.object_id)
WHEN MATCHED THEN update
SET T2.OBJECT_NAME=UPPER(T1.OBJECT_NAME);Explan for above MERGE stmt.
| Id | Operation            | Name | Rows | Bytes |TempSpc| Cost (%CPU)| Time     |
|   0 | MERGE STATEMENT      |      | 9139 |   303K|       |   201    (2)| 00:00:03 |
|   1 | MERGE               | T2   |       |       |       |            |          |
|   2 |   VIEW               |      |       |       |       |            |          |
|* 3 |    HASH JOIN         |      | 9139 | 2391K| 1256K|   201   (2)| 00:00:03 |
|   4 |     TABLE ACCESS FULL| T1   | 9138 | 1142K|       |    35   (3)| 00:00:01 |
|   5 |     TABLE ACCESS FULL| T2   | 9671 | 1322K|       |    34   (3)| 00:00:01 |
PLAN_TABLE_OUTPUT
Predicate Information (identified by operation id):
   3 - access("T1"."OBJECT_ID"="T2"."OBJECT_ID")Cost is 201 , but for the corellated update the cost is 37.
Any idea , how should i re-write the MERGE stmt.?
Edited by: kumar on Jun 16, 2011 4:41 PM

First "cost" is just a number and you should not compare or tune to get the best "cost" in an execution plan.
What counts ist elapsed time => IO, CPU...
In 11g the "cost" for the merge is better (and also the CPU time is far off to be close to the truth!)
9799 rows updated
78ms elapsed
Plan hash value: 580992724
| Id | Operation                    | Name         | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | UPDATE STATEMENT             |              | 9641 |   404K| 28964 (34)| 00:05:48 |
|   1 | UPDATE                      | T1           |       |       |            |          |
|   2 |   NESTED LOOPS               |              | 9641 |   404K|    41   (3)| 00:00:01 |
|   3 |    TABLE ACCESS FULL         | T1           | 10866 |   318K|    40   (0)| 00:00:01 |
|* 4 |    INDEX UNIQUE SCAN         | T2_OBJID_IND |     1 |    13 |     0   (0)| 00:00:01 |
|   5 |   TABLE ACCESS BY INDEX ROWID| T2           |     1 |    30 |     2   (0)| 00:00:01 |
|* 6 |    INDEX UNIQUE SCAN         | T2_OBJID_IND |     1 |       |     1   (0)| 00:00:01 |
Predicate Information (identified by operation id):
   4 - access("T1"."OBJECT_ID"="T2"."OBJECT_ID")
   6 - access("T2"."OBJECT_ID"=:B1)
Note
   - dynamic sampling used for this statement (level=2)
commited
16ms elapsed
9799 rows merged
125ms elapsed
Plan hash value: 2009158753
| Id | Operation            | Name | Rows | Bytes |TempSpc| Cost (%CPU)| Time     |
|   0 | MERGE STATEMENT      |      | 9641 |   320K|       |   251   (1)| 00:00:04 |
|   1 | MERGE               | T2   |       |       |       |            |          |
|   2 |   VIEW               |      |       |       |       |            |          |
|* 3 |    HASH JOIN         |      | 9641 | 3088K| 1720K|   251   (1)| 00:00:04 |
|   4 |     TABLE ACCESS FULL| T2   | 9640 | 1600K|       |    39   (0)| 00:00:01 |
|   5 |     TABLE ACCESS FULL| T1   | 10866 | 1676K|       |    40   (0)| 00:00:01 |
Predicate Information (identified by operation id):
   3 - access("T1"."OBJECT_ID"="T2"."OBJECT_ID")
Note
   - dynamic sampling used for this statement (level=2)In your example, the elapsed time (thanks for the it!) is 78ms for the update and 125ms for the MERGE. (ORACLE 11g on and old PC) .
So "should you rewrite" the MERGE? No idea how. I assume you want to change from UPDATE to MERGE and see if it's worth?
Here it's not. But, your example just uses 2MB of data. And the difference from my point view is not MERGE or UPDATE it's NL against HASH join with that tiny amount of data.
So generally I use MERGE because of speed and because I have more control over the query. For updating 2MB of data, it's not worth it. For updating GBytes the stuff I worked on it was faster (and better to control).

Statistics-relevant delivery date and Committed date in Stock Transport Ord

Dear Friends,
Kindly tell me how the System Calculate the Statistics-relevant delivery date and Committed date in Stock Transport Order.
Thanks & Regards
T.Arulvanan

Hi Jürgen,
in the Include MM06EFET_ETT_FUELLEN there is following coding:
IF NOT im_sd_scheduling IS INITIAL.
PERFORM ett_sd_scheduling USING 'X' 'X' eket *eket
CHANGING eketdata_sd.
In the FORM ETT_SD_SCHEDULING
there is the following coding:
Datum oder Uhrzeit geändert --> Versandterminierungsdaten zurücksetzen
CLEAR c_eketdata_sd.
Lieferdatum und Uhrzeit setzen
c_eketdata_sd-eindt = i_eketn-eindt.
c_eketdata_sd-uzeit = i_eketn-uzeit.
So the internal table c_eketdata_sd is cleared and only the delivery date and time are updated, but not the statistc relevant date.
It seems to me like standard behaviour of SAP.
Best regards
Georg

FM Update and Commitment Category

Similar Messages

Maybe you are looking for