PM Confirmations to update CATS2 (IW42 - CATS2)

Hi Experts,
We have a business requirement to use CATS2 for a standard approach to time entry. As such, the project that implemented SAP PM did not give access to the IW42 transaction (confirmations).
Now we still have the requirement for all time confirmations to be available in CATS for reporting, but the maintenance staff want to use IW42 to make life easier when completing their work.
So, we will have some people using IW42, and some using CATS directly. Because all data is required in CATS2 for reporting as part of our standard processes, we need to update CATS2 with any time confirmations entered in IW42. Sounds a bit backwards i know, but this seems to be the only option we have to achive the best of both worlds.
Considering the above,
1. Does anyone know of a better alternative to this approach?
2. Does anyone have serious concerns with this approach?
3. Are there any standard BAPI's that we can call to update data from IW42 into CATS (e.g. personnel number, order number, operation number, hours etc)?
4. What is the best way to ensure that CATS doesn't try to send data BACK to PM confirmations? Don't want double ups.
Regards,
Maikel

The worklist will look at all orders for a given work center or employee for a given period of time as specified via the CAT profile when configured. You can set this up so that if you select an order it will take the planned start and finish times fromthe operation that you wish to do the confirmation for.
Check online pdf file at (copy and paste the link to your internet browser) you will find the information on branching to material issues on page 41
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CATS/CATS.pdf
This explains that you can branch to for instance goods issue from the CAT2 timesheet
Jim

Similar Messages

BAPI for Purchase Order Confirmation and update EKES table

Hi all,
I have a requirement to update the PO confirmation soon after successful creation of PO in an IDOC.
I have used BAPI_PO_CHANGE function module which didnt serve the purpose as it cannot update confirmations.
I tried using ME_CONFIRMATION_UPDATE where I was able to add a confirmation entry in EKES table but that is not being reflected in ME23N transaction when I display the PO.
Please help me out on this.
Thanks & Regards
Pavan

NB: Never use a standard update FM (check attributes of ME_CONFIRMATION_UPDATE) its often only a SQL statement collector without any check, logging of changes or database consistency, if you perform a where-used you should find it is never called alone but with a bunch of other update FM after checks and other update preparation.
Get back to the BAPI and table parameter POCONFIRMATION, also use BAPI_PO_GETDETAIL1 to get current data for the call of BAPI_PO_CHANGE.
Regards,
Raymond
PS: If it is not in 197958 - BAPIs for purchase orders: Missing functions, you should be able to do it

Transfer Order Confirmation not updated in Header level (Table: LTAK)

Hi,
We are facing a problem, transfer order header is not updated with confirmation, but TO items are confirmed and resulting these transfer order to display in RF monitor (LRF1 and LRF2 transactions).
And the other issue is, we are seeing some transfer orders created without item data (in LTAP table) and unable to confirm these TOs since Item data is not available, hence TO header is not updated with confirmation and resulting these TOs to display in LRF1 and LRF2 report.
I have cleared some transfer orders by updating the confirmation field in LTAK table through debugging. But we see the issue is ongoing and would like to have permanent solution.
It will be a great help if anyone have solution to these issues.
Thanks & Regards,
Nagarjun

Hi Nagarjun,
do you have any Z code in-between ? Did you check OSS notes ? Did you apply all patches to your system ?
What you are describing is something usual when Z programs were developed, you should provide more details for analysis.
Many thanks,
Enrico

Vendor confirmation tab update using idoc ORDERS02

Hi all,
This is the first time i am working on idocs.
I have a requirement where i have to update the vendor confirmation tab in ME22n(Purchase order), I am using IDOC type ORDERS02. and i am using segment E1EDP20 to update quantity,date and reference no. This is working fine.
Now i need to update 2 more fields in the tab i.e confirmation category(EKES-EBTYP) and Date category of delivery date in vendor confirmation(EKES-LPEIN).But i dint find these fields in segment E1EDP20.
My question is whether these 2 fields are available in any other segment?
or should i extend the segment E1EDP20 ?is it the correct segment to be extended...
Please provide the inputs....<removed by moderator>
Regards,
Greeshma.
Edited by: Thomas Zloch on Feb 22, 2012

Hi,
I have a questions for you and that will help me provide better solution .
a) Is vendor providing you the Confirmation category or are you expecting to get this information from Vendor ?
There are many points at which this information can be entered in ME22N.
1. When the Vendor Acknowledege your PO(If the Acknowledgment required is selected) .
2. When the Vendor request a change in schedule due to his own priorities .
3. When the Vendor actually does a goods issue and you are ready to do a Goods receipt.
In all these cases you update the system with confirmation category .In most cases this is the last phase of PO processing where you do the goods receipt and simultaneoulsy update the confirmation category. You are geting the quantity and the date updated from your schedule lines currently and since Schedules lines does not contain the confirmation category you are not getting it in E1EDP20.Confirmation category in most business scenarios is a mere stastical data rather than concrete data like schedule lines.
Depending on 1/2/3 you should be approching the solution. 1.If you want to update the confirmation category during the Order acknowledgment Use BAPI_PO_CHANGE and call it from the PI or middleware or(3) if during the Goods receipt then call the Exit of MIGO to get the PO populated if not exit then write a custom program to see all the Goods receipt and update the PO confirmation category accordingly (Remember this is a statstical data ). Although i highly doubt that the confirmation category will be provided by vendor it is the Buyer who will be determining it and that is why it is not there in the Standard Idoc.I shall not prefer the IDOC extension.
You can have a discussion with your Functional/Customer to figure out the best approcah. Word of Caution : Analyze before you extend an Idoc .
Thanks,
Anjaneya .
Edited by: Anjaneya Bhardwaj on Feb 24, 2012 7:33 AM

Why Confirmation not updated in ERP

Hi All;
We are using SRM 7.0 classic scenario & ECC6.
The user created confirmation and the manager approved it. but while transferring to backend, somebody was editing the PO. As a result, the system did not update the GR in ERP.
When i checked in in BBP_PD i found stats: currently being transferred"
How can I trigger again the confirmation to be transferred to backend.?
Thanks

Dear;
I have already checked in WE05 but I dod not find that IDoc other IDocs are successfull.
Now I am trying to cancel or re-confirm the confirmation but the system gives error message
System status FREE is active
System Status TRANS is active
what should I do to re-transmit it.

Please confirm the update

CREATE TABLE TMP(CODE VARCHAR2(5), ID VARCHAR2(5))
INSERT INTO TMP VALUES('0','1')
INSERT INTO TMP VALUES('000','0')
INSERT INTO TMP VALUES('006','0')
INSERT INTO TMP VALUES('006','1')
CREATE TABLE MAIN(CODE VARCHAR2(5), ID VARCHAR2(5), DC NUMBER)
INSERT INTO MAIN VALUES('0','1',0)
INSERT INTO MAIN VALUES('000','0',0)
INSERT INTO MAIN VALUES('006','0',0)
INSERT INTO MAIN VALUES('006','1',0)
INSERT INTO MAIN VALUES('006','3',0)
INSERT INTO MAIN VALUES('006','4',0)
INSERT INTO MAIN VALUES('0','4',0)
INSERT INTO MAIN VALUES('8','1',0)
I want the column DC to be null in main table for all those ids and codes in tmp table
I gave this:
update main AA set AA.DC = null
where AA.CODE IN (SELECT CODE FROM TMP )
AND AA.ID IN (SELECT ID FROM TMP )
it does give 4 rows updated, but this is just example, i am working on a much bigger table with thousands
of rows, i want the actual combination of id and code to be updated..
example, there may be thousands of rows with id as 1, and code not in 0 and 006, they should not be updated
eg: 8,1,0 row in main table should not be updated/.
will the above update do ?

Just confirming a bit here ;) :
MHO%xe> select * from tmp;
CODE ID
0     1
000   0
006   0
006   1
4 rijen zijn geselecteerd.
Verstreken: 00:00:00.29
MHO%xe> select * from main;
CODE ID            DC
0     1              0
000   0              0
006   0              0
006   1              0
006   3              0
006   4              0
0     4              0
8     1              0
8 rijen zijn geselecteerd.
Verstreken: 00:00:00.37
MHO%xe> update main
2 set dc = null
3 where ( id, code ) in ( select id, code
4                          from tmp
5                        );
4 rijen zijn bijgewerkt.
Verstreken: 00:00:00.96
MHO%xe> select * from main;
CODE ID            DC
0     1
000   0
006   0
006   1
006   3              0
006   4              0
0     4              0
8     1              0
8 rijen zijn geselecteerd.
Verstreken: 00:00:00.06
MHO%xe> rollback;
Rollback is voltooid.
Verstreken: 00:00:00.12
MHO%xe> update main a
2 set a.dc = null
3 where exists ( select null
4                 from   tmp b
5                 where b.id = a.id
6                 and    b.code = a.code
7               );
4 rijen zijn bijgewerkt.
Verstreken: 00:00:00.15
MHO%xe> select * from main;
CODE ID            DC
0     1
000   0
006   0
006   1
006   3              0
006   4              0
0     4              0
8     1              0
8 rijen zijn geselecteerd.
Verstreken: 00:00:00.06
MHO%xe> rollback;
Rollback is voltooid.
Verstreken: 00:00:00.03
MHO%xe> update main aa
2 set    aa.dc = null
3 where aa.code in (select code from tmp )
4 and    aa.id in (select id from tmp );
4 rijen zijn bijgewerkt.
Verstreken: 00:00:00.21
MHO%xe> select * from main;
CODE ID            DC
0     1
000   0
006   0
006   1
006   3              0
006   4              0
0     4              0
8     1              0
8 rijen zijn geselecteerd.
Verstreken: 00:00:00.06
MHO%xe>

External services confirmation- ML81N vs. IW42??

Hello everyone,
I have a question around confirmation of external services, addressing to those who are savvy with external services config side..
First of all- Does accepted service entry sheet represent itself a confirmation? Or do we need also confirm it standard way as well? In case of latter, itu2019s confusing, since when we hit u2018actual datau2019 in IW42, we only have operations to confirm, not the particular services that lying beneath in sub screen External (e.g. from contact). So, subscreen Services is activated in confirmation layout, stays grey regardless whether you have services from contract or from material master (Mat type DIEN), nor using PM02 or PM03 ctrl keys..
So, what should I do to enable those services in confirmation screen?and all in all, is it necessary at all from business process design standpoint, or service entry sheet is normally enough to confirm external services? if so, what is the purpose of that subscreen in confirmation then??
Thanks in advance,
Sergey

Hi Sergey,
In case of external services process we dont do confirmation from standard transactions i.e. IW42/IW41, whereas it used for internal operations only or the opeartions carried out by external workcenter.
In SAP we do service entry acceptance & GR against the PO for confirmation followed by MIRO i.e. invoice verification for payments.
We get the following statuses upon above activities....
EODL-External Operation Delivered
EOPL-External Opeation Partially Delivered.
Sundar

VZW Tech Support confirms "Software Update has begun"

Just got off the phone with VZW tech support. Apparently another update has started rolling out as of July 15th. She said it is being done in batches, but she was unable to confirm if it was Android 2.3(GB) or not. Anyone know ?

I definitely agree that there is a mix up with the mr2 update, since tech told me they were pushing me an update with gingerbread, even after I argued that it was the mr2 update and the "pushed' phantom update never showed up. Late last night I was told by a supervisor that gingerbread was a few months out. I am convinced that none of them have a clue what they're talking about, based upon my own experiences. Maybe too many build numbers is confusing the reps, maybe we should use pictures or building blocks. Don't get me wrong, there are great reps out there, but those with a lack of knowledge and poor service make it harder to notice the ones that excel at their job. Reason is you are so frustrated with ignorance that by the time you get to a decent rep, tech or customer care, you simply look at them like they're just doing their job.

Confirm PO updated in table before GR

Hi All,
I have program to create PO via BAPI_PO_CREATE and followed by BAPI_GOODSMVT_CREATE to do GR.
When there is little PO line items, after PO created, no problem in create material document through BAPI_GOODSMVT_CREATE but when PO line items alot (50 ~ 200 lines), even after PO created, BAPI_GOODSMVT_CREATE has error in create GR.
Currently I use key word wait up to few seconds in do loop before BAPI_GOODSMVT_CREATE but i think in the loop to check total line items created in table is more secured.
May I know what table I need to check to confirm all PO line item added in table and PO number created in table then only I proceed with BAPI_GOODSMVT_CREATE.
Thanks
Rgds

Hello,
PO line table is EKPO. But you may try the following:
After PO is created through BAPI_PO_CREATE, you should make a synchronous commit (COMMIT WORK AND WAIT) before calling BAPI_GOODSMVT_CREATE. This ensures PO has been saved before proceeding to make Goods Receipt.
Thanks,
Venu

Need confirmation about updates

I read today on the SANS website about vulnerabilities in practically all versions of Java, save for the most recent updates i.e. Update 6, Update 15, etc.
Reference http://isc.sans.org/newssummary.html
I'm researching which versions of Java are on the workstations in my workplace by using SMS, and I'm seeing that there are a LOT of computers with multiple versions of Java on them.
My question:
If a computer has mulitple versions of Java on it, would each version have to be brought up to the most recent update, or, would only the 'highest' version installed need to be updated in order to set Java security to the proper level?
The task looks pretty daunting and I'd love some qualified replies since I will have to sell the necessary man-hours <person-hours> to my boss, and provide a high degree of confidence that nothing 'Java dependent' will get broken in the process.
Thanks,
Lawson...

Each Java version is independent, and does not rely on,or interact with, any other version. Each version is independently runnable - any version that's installed can be executed. Depending on the Java application, an application may or may not run on more than one Java version.
Typically (in Windows) the last version installed becomes the default version, due to the copying of the file java.exe to the \windows\system32\ directory, which usually causes it to be found first when Windows searchs the system's path environment variable directory list.
There is no "update" of an existing version. New versions are installed alongside of the existing version(s). It's up to the user to uninstall a version. As noted, certain Java applications may require a specific version, and will not run on other versions, and removing older versions may cause problems.

Issue with while updating the PO confirmations

Hi,
My requirement as below.
We have Enterprise portal, through this portal supplier can send the confirmations at PO item level, to work this functionality we developed RFM (remote function module) in this RFM I am using 'ME_CONFIRMATION_UPDATE_AVIS' function module to create/update confirmations in ekes table.
We are able to update and create confirmation, but the problem is once we change existed confirmations those changes are not reflected into CDHDR and CDPOS table. I know 'ME_CONFIRMATION_UPDATE_AVIS' function module will update database directly which means that data flow won't pass through the application. I searched for standard BAPIs for update confirmation at PO line item level I didn't find anything. I think I can do this using BDC, I need any other ways to solve this problem. Can you help me regarding the above issue.
Thanks & Regards,
Krishna

I had to do a similar task and could not find a direct way to do it. Instead I created an idoc ORDRSP.ORDERS05 and submitted against the ECC system. SAP correctly processes these confirmations and updates change details as expected. The only issue you may have is that the change history will be updated by the rfc user and not the originating user on your web app.
If you want some example code, let me know.

EFI Update Causes Time Machine Problems

After the EFI update today (10/12) Time Machine will no longer mount its disk image on an external network drive via AFP wireless connection. The external drive is presented through Ubuntu 8.10 with Netatalk 2.03. Anyone else having this problem yet, or better yet have a solution?

Fixed it! Mounting it in Disk Utility and repairing the file system worked. It should be noted however that I can't confirm the update was the cause of of this problem but, its some kawinky-**** huh?

Production order status was not changed to 'CNF' after final confirmation.

Hi guru.
I experienced very special case that production order status was not changed to CNF after final confirmation.
I did final confirmation and canceled confirmation. (CNF -> REL)
And I did final confirmation again because of fixing activity quantity.
the strange thing is that production order status wasn't changed from REL to CNF.
I did confirmation again with 0 activity, thereby I solved this problem
BUT i don't know why this case happened.
Please, explain the reason.
Thanks.

Hi,
As per my observation, their is not any change in the status of the order REL with confirmation CNF, instead of this, it has change from CRTD & then to TECO.
Sequence of the status of the order as below
1) CRTD MANC NMAT SETC
2) REL NMAT SETC - Changes from CRTD to REL after releasing of the order
3) REL CNF PRC CSER ERTR OPGN SETC - After confirmation, it updated after the order REL status.
Rgd,
Chetan

Partial Pick Confirming Sales Order

Hi Folks,
I have a requirement where I have to Pick Confirm and Ship confirm Sales Order through API.
1. When the quantites to be picked are same as quantity ordered the code seems to work just fine.
But suppose in my example my quantity in SO line is 50 and I want to partially Ship confirm the lines lets say 20 quantites.
then which API i need to use?
The approach I am following is while pick confirming I am passing 20 quantites only and the ship confirming it.
I researched and found that we can use the following API to update shipping attributes 'WSH_DELIVERY_DETAILS_PUB.Update_Shipping_Attributes' but when I run it (I tried before and after Pick confirm) the API runs fine but no changes are getting affected and the code Pick confirms all the quantity.
Could some please help me with this.
Please find the codes for pick confirm and updating shipping attributes
Pick confirm code
DECLARE
lv_order_num        number := 700145812;
vMoveOrderLineId    NUMBER;
p_pick_conf_qty     NUMBER;
pStatus             VARCHAR2(100);
pMsgData            VARCHAR2(4000);
v_movehdr_rec       INV_MOVE_ORDER_PUB.TROHDR_REC_TYPE;
v_movehdr_val_rec   INV_MOVE_ORDER_PUB.TROHDR_VAL_REC_TYPE;
v_moveln_tbl        INV_MOVE_ORDER_PUB.TROLIN_TBL_TYPE;
v_moveln_tbl_p      INV_MOVE_ORDER_PUB.TROLIN_TBL_TYPE;
v_moveln_zero_tbl   INV_MOVE_ORDER_PUB.TROLIN_TBL_TYPE;
v_moveln_zero_tbl_p INV_MOVE_ORDER_PUB.TROLIN_TBL_TYPE;
v_moveln_tbl_d      INV_MOVE_ORDER_PUB.TROLIN_TBL_TYPE;
v_moveln_tbl_o      INV_MOVE_ORDER_PUB.TROLIN_TBL_TYPE;
v_moveln_val_tbl    INV_MOVE_ORDER_PUB.TROLIN_VAL_TBL_TYPE;
v_mold_tbl          INV_MO_LINE_DETAIL_UTIL.G_MMTT_TBL_TYPE;
v_mold_tbl_p        INV_MO_LINE_DETAIL_UTIL.G_MMTT_TBL_TYPE;
l_mold_tbl          INV_MO_LINE_DETAIL_UTIL.G_MMTT_TBL_TYPE;
l_moveln_tbl        INV_MOVE_ORDER_PUB.TROLIN_TBL_TYPE;
l_trolin_rec        INV_MOVE_ORDER_PUB.TROLIN_REC_TYPE;
l_trolin_tbl        INV_MOVE_ORDER_PUB.TROLIN_TBL_TYPE;
l_return_status     VARCHAR2(240);
l_msg_count         NUMBER;
l_msg_data          VARCHAR2(2000);
l_move_hdr_id       NUMBER;
l_move_order_no     NUMBER := 0;
v_return_values     VARCHAR2(2000) := FND_API.G_TRUE;
v_move_hdr_rec      INV_MOVE_ORDER_PUB.TROHDR_REC_TYPE;
v_move_hdr_val_rec INV_MOVE_ORDER_PUB.TROHDR_VAL_REC_TYPE;
v_api_pick_confirm NUMBER;
cv_fail             VARCHAR2(100) := 'Fail';
cv_success          VARCHAR2(100) := 'Success';
g_user_id      number;
g_resp_id      number;
g_resp_appl_id number;
p_user_name    varchar2(100) := 'SYSADMIN';
p_resp_name    varchar2(100) := 'Order Management Super User';
p_mo_apps      varchar2(100) := 'ONT';
CURSOR c_mmtt_recs(vMoveOrderLineId NUMBER) IS
    SELECT transaction_header_id,
           transaction_temp_id,
           source_code,
           source_line_id,
           transaction_mode,
           lock_flag,
           last_update_date,
           last_updated_by,
           creation_date,
           created_by,
           last_update_login,
           request_id,
           program_application_id,
           program_id,
           program_update_date,
           inventory_item_id,
           revision,
           organization_id,
           subinventory_code,
           locator_id,
           transaction_quantity,
           primary_quantity,
           transaction_uom,
           transaction_cost,
           transaction_type_id,
           transaction_action_id,
           transaction_source_type_id,
           transaction_source_id,
           transaction_source_name,
           transaction_date,
           acct_period_id,
           distribution_account_id,
           transaction_reference,
           requisition_line_id,
           requisition_distribution_id,
           reason_id,
           lot_number,
           lot_expiration_date,
           serial_number,
           receiving_document,
           demand_id,
           rcv_transaction_id,
           move_transaction_id,
           completion_transaction_id,
           wip_entity_type,
           schedule_id,
           repetitive_line_id,
           employee_code,
           primary_switch,
           schedule_update_code,
           setup_teardown_code,
           item_ordering,
           negative_req_flag,
           operation_seq_num,
           picking_line_id,
           trx_source_line_id,
           trx_source_delivery_id,
           physical_adjustment_id,
           cycle_count_id,
           rma_line_id,
           customer_ship_id,
           currency_code,
           currency_conversion_rate,
           currency_conversion_type,
           currency_conversion_date,
           ussgl_transaction_code,
           vendor_lot_number,
           encumbrance_account,
           encumbrance_amount,
           ship_to_location,
           shipment_number,
           transfer_cost,
           transportation_cost,
           transportation_account,
           freight_code,
           containers,
           waybill_airbill,
           expected_arrival_date,
           transfer_subinventory,
           transfer_organization,
           transfer_to_location,
           new_average_cost,
           value_change,
           percentage_change,
           material_allocation_temp_id,
           demand_source_header_id,
           demand_source_line,
           demand_source_delivery,
           item_segments,
           item_description,
           item_trx_enabled_flag,
           item_location_control_code,
           item_restrict_subinv_code,
           item_restrict_locators_code,
           item_revision_qty_control_code,
           item_primary_uom_code,
           item_uom_class,
           item_shelf_life_code,
           item_shelf_life_days,
           item_lot_control_code,
           item_serial_control_code,
           item_inventory_asset_flag,
           allowed_units_lookup_code,
           department_id,
           department_code,
           wip_supply_type,
           supply_subinventory,
           supply_locator_id,
           valid_subinventory_flag,
           valid_locator_flag,
           locator_segments,
           current_locator_control_code,
           number_of_lots_entered,
           wip_commit_flag,
           next_lot_number,
           lot_alpha_prefix,
           next_serial_number,
           serial_alpha_prefix,
           shippable_flag,
           posting_flag,
           required_flag,
           process_flag,
           error_code,
           error_explanation,
           attribute_category,
           attribute1,
           attribute2,
           attribute3,
           attribute4,
           attribute5,
           attribute6,
           attribute7,
           attribute8,
           attribute9,
           attribute10,
           attribute11,
           attribute12,
           attribute13,
           attribute14,
           attribute15,
           movement_id,
           reservation_quantity,
           shipped_quantity,
           transaction_line_number,
           task_id,
           to_task_id,
           source_task_id,
           project_id,
           source_project_id,
           pa_expenditure_org_id,
           to_project_id,
           expenditure_type,
           final_completion_flag,
           transfer_percentage,
           transaction_sequence_id,
           material_account,
           material_overhead_account,
           resource_account,
           outside_processing_account,
           overhead_account,
           flow_schedule,
           cost_group_id,
           demand_class,
           qa_collection_id,
           kanban_card_id,
           overcompletion_transaction_id,
           overcompletion_primary_qty,
           overcompletion_transaction_qty,
           end_item_unit_number,
           scheduled_payback_date,
           line_type_code,
           parent_transaction_temp_id,
           put_away_strategy_id,
           put_away_rule_id,
           pick_strategy_id,
           pick_rule_id,
           common_bom_seq_id,
           common_routing_seq_id,
           cost_type_id,
           org_cost_group_id,
           move_order_line_id,
           task_group_id,
           pick_slip_number,
           reservation_id,
           transaction_status,
           transfer_cost_group_id,
           lpn_id,
           transfer_lpn_id,
           pick_slip_date,
           content_lpn_id
      FROM MTL_MATERIAL_TRANSACTIONS_TEMP
     WHERE move_order_line_id = vMoveOrderLineId;
l_moveln_fidx     NUMBER;
l_moveln_lidx     NUMBER;
n_mvln_cntr       NUMBER;
l_Index           NUMBER := 1;
v_records_in_mmtt NUMBER := 0;
REC C_MMTT_RECS%ROWTYPE;
BEGIN
select user_id
    into g_user_id
    from fnd_user
   where user_name = p_user_name;
select responsibility_id, application_id
    into g_resp_id, g_resp_appl_id
    from apps.fnd_responsibility_vl
   where responsibility_name = p_resp_name;
Apps.FND_Global.Apps_Initialize(g_user_id, g_resp_id, g_resp_appl_id);
MO_GLOBAL.INIT(p_mo_apps);
for mol in (select wda.delivery_id,
                     wda.delivery_detail_id,
                     wda.parent_delivery_detail_id,
                     wdd.source_code,
                     wdd.inventory_item_id,
                     wdd.organization_id,
                     wdd.ship_from_location_id,
                     wdd.ship_to_location_id,
                     wdd.requested_quantity,
                     wdd.requested_quantity_uom,
                     wdd.move_order_line_id,
                     wdd.org_id,
                     mtrl.quantity,
                     mtrl.quantity_delivered
                from wsh_delivery_details     wdd,
                     wsh_delivery_assignments wda,
                     oe_order_lines_all       ol,
                     oe_order_headers_all     oh,
                     mtl_txn_request_lines    mtrl,
                     mtl_txn_request_headers mtrh
               where wdd.source_line_id = ol.line_id
                 and wdd.delivery_detail_id = wda.delivery_detail_id
                 and ol.header_id = oh.header_id
                 and wdd.move_order_line_id = mtrl.line_id(+)
                 and mtrl.header_id = mtrh.header_id(+)
                 and oh.order_number = lv_order_num) loop
    vMoveOrderLineId := mol.move_order_line_id;
    p_pick_conf_qty := mol.quantity - nvl(mol.quantity_delivered,0);
    SELECT COUNT(move_order_line_id)
      INTO v_records_in_mmtt
      FROM MTL_MATERIAL_TRANSACTIONS_TEMP
     WHERE move_order_line_id = vMoveOrderLineId;
    IF v_records_in_mmtt > 1 THEN
      pStatus := cv_fail;
      pMsgData := 'Wrong number of records in MMTT for the MOVE_ORDER_LINE_ID : ' ||
                  vMoveOrderLineId;
      DBMS_OUTPUT.PUT_LINE('Multiple records in MMTT for move_order_line_id = ' ||
                           vMoveOrderLineId);
      v_api_pick_confirm := 0;
      GOTO end_of_pkcnf;
    ELSIF v_records_in_mmtt = 0 THEN
      --means that the delivery is already pick confirmed
      pStatus := cv_success;
      DBMS_OUTPUT.PUT_LINE('No records in MMTT for move_order_line_id = ' ||
                           vMoveOrderLineId ||
                           ' hence it is already pick confirmed');
      v_api_pick_confirm := 0;
      GOTO end_of_pkcnf;
    END IF;
    SELECT mtrh.header_id, mtrh.request_number
      INTO l_move_hdr_id, l_move_order_no
      FROM mtl_txn_request_headers mtrh, mtl_txn_request_lines mtrl
     WHERE mtrh.header_id = mtrl.header_id
       AND mtrl.line_id = vMoveOrderLineId;
    DBMS_OUTPUT.PUT_LINE('Obtained MTRH.HEADER_ID = ' || l_move_hdr_id ||
                         ' MTRH.REQUEST_NUMBER = ' || l_move_order_no ||
                         ' for move_order_line_id = ' || vMoveOrderLineId);
    INV_MOVE_ORDER_PUB.GET_MOVE_ORDER(p_api_version_number => 1.0,
                                      p_init_msg_list      => FND_API.G_FALSE,
                                      p_return_values      => v_return_values,
                                      x_return_status      => l_return_status,
                                      x_msg_count          => l_msg_count,
                                      x_msg_data           => l_msg_data,
                                      p_header_id          => l_move_hdr_id,
                                      p_header             => l_move_order_no,
                                      x_trohdr_rec         => v_move_hdr_rec,
                                      x_trohdr_val_rec     => v_move_hdr_val_rec,
                                      x_trolin_tbl         => v_moveln_tbl,
                                      x_trolin_val_tbl     => v_moveln_val_tbl);
     COMMIT;
    DBMS_OUTPUT.PUT_LINE('Return status of INV_MOVE_ORDER_PUB.GET_MOVE_ORDER = ' ||
                         l_return_status);
    IF l_return_status != FND_API.G_RET_STS_SUCCESS THEN
      pStatus := cv_fail;
      pMsgData := 'Failed to get move order inv_move_order_pub.get_move_order for MOVE_ORDER_LINE_ID : ' ||
                  vMoveOrderLineId;
      GOTO end_of_pkcnf;
    END IF;
    OPEN c_mmtt_recs(vMoveOrderLineId);
    FETCH c_mmtt_recs
      INTO rec;
    CLOSE c_mmtt_recs;
    v_mold_tbl(1).transaction_header_id := rec.transaction_header_id;
    v_mold_tbl(1).transaction_temp_id := rec.transaction_temp_id;
    v_mold_tbl(1).source_code := rec.source_code;
    v_mold_tbl(1).source_line_id := rec.source_line_id;
    v_mold_tbl(1).transaction_mode := rec.transaction_mode;
    v_mold_tbl(1).lock_flag := rec.lock_flag;
    v_mold_tbl(1).last_update_date := rec.last_update_date;
    v_mold_tbl(1).last_updated_by := rec.last_updated_by;
    v_mold_tbl(1).creation_date := rec.creation_date;
    v_mold_tbl(1).created_by := rec.created_by;
    v_mold_tbl(1).last_update_login := rec.last_update_login;
    v_mold_tbl(1).request_id := rec.request_id;
    v_mold_tbl(1).program_application_id := rec.program_application_id;
    v_mold_tbl(1).program_id := rec.program_id;
    v_mold_tbl(1).program_update_date := rec.program_update_date;
    v_mold_tbl(1).inventory_item_id := rec.inventory_item_id;
    v_mold_tbl(1).revision := rec.revision;
    v_mold_tbl(1).organization_id := rec.organization_id;
    v_mold_tbl(1).subinventory_code := rec.subinventory_code;
    v_mold_tbl(1).locator_id := rec.locator_id;
    v_mold_tbl(1).transaction_quantity := rec.transaction_quantity;
    v_mold_tbl(1).primary_quantity := rec.primary_quantity;
    v_mold_tbl(1).transaction_uom := rec.transaction_uom;
    v_mold_tbl(1).transaction_cost := rec.transaction_cost;
    v_mold_tbl(1).transaction_type_id := rec.transaction_type_id;
    v_mold_tbl(1).transaction_action_id := rec.transaction_action_id;
    v_mold_tbl(1).transaction_source_type_id := rec.transaction_source_type_id;
    v_mold_tbl(1).transaction_source_id := rec.transaction_source_id;
    v_mold_tbl(1).transaction_source_name := rec.transaction_source_name;
    v_mold_tbl(1).transaction_date := rec.transaction_date;
    v_mold_tbl(1).acct_period_id := rec.acct_period_id;
    v_mold_tbl(1).distribution_account_id := rec.distribution_account_id;
    v_mold_tbl(1).transaction_reference := rec.transaction_reference;
    v_mold_tbl(1).requisition_line_id := rec.requisition_line_id;
    v_mold_tbl(1).requisition_distribution_id := rec.requisition_distribution_id;
    v_mold_tbl(1).reason_id := rec.reason_id;
    v_mold_tbl(1).lot_number := rec.lot_number;
    v_mold_tbl(1).lot_expiration_date := rec.lot_expiration_date;
    v_mold_tbl(1).serial_number := rec.serial_number;
    v_mold_tbl(1).receiving_document := rec.receiving_document;
    v_mold_tbl(1).demand_id := rec.demand_id;
    v_mold_tbl(1).rcv_transaction_id := rec.rcv_transaction_id;
    v_mold_tbl(1).move_transaction_id := rec.move_transaction_id;
    v_mold_tbl(1).completion_transaction_id := rec.completion_transaction_id;
    v_mold_tbl(1).wip_entity_type := rec.wip_entity_type;
    v_mold_tbl(1).schedule_id := rec.schedule_id;
    v_mold_tbl(1).repetitive_line_id := rec.repetitive_line_id;
    v_mold_tbl(1).employee_code := rec.employee_code;
    v_mold_tbl(1).primary_switch := rec.primary_switch;
    v_mold_tbl(1).schedule_update_code := rec.schedule_update_code;
    v_mold_tbl(1).setup_teardown_code := rec.setup_teardown_code;
    v_mold_tbl(1).item_ordering := rec.item_ordering;
    v_mold_tbl(1).negative_req_flag := rec.negative_req_flag;
    v_mold_tbl(1).operation_seq_num := rec.operation_seq_num;
    v_mold_tbl(1).picking_line_id := rec.picking_line_id;
    v_mold_tbl(1).trx_source_line_id := rec.trx_source_line_id;
    v_mold_tbl(1).trx_source_delivery_id := rec.trx_source_delivery_id;
    v_mold_tbl(1).physical_adjustment_id := rec.physical_adjustment_id;
    v_mold_tbl(1).cycle_count_id := rec.cycle_count_id;
    v_mold_tbl(1).rma_line_id := rec.rma_line_id;
    v_mold_tbl(1).customer_ship_id := rec.customer_ship_id;
    v_mold_tbl(1).currency_code := rec.currency_code;
    v_mold_tbl(1).currency_conversion_rate := rec.currency_conversion_rate;
    v_mold_tbl(1).currency_conversion_type := rec.currency_conversion_type;
    v_mold_tbl(1).currency_conversion_date := rec.currency_conversion_date;
    v_mold_tbl(1).ussgl_transaction_code := rec.ussgl_transaction_code;
    v_mold_tbl(1).vendor_lot_number := rec.vendor_lot_number;
    v_mold_tbl(1).encumbrance_account := rec.encumbrance_account;
    v_mold_tbl(1).encumbrance_amount := rec.encumbrance_amount;
    v_mold_tbl(1).ship_to_location := rec.ship_to_location;
    v_mold_tbl(1).shipment_number := rec.shipment_number;
    v_mold_tbl(1).transfer_cost := rec.transfer_cost;
    v_mold_tbl(1).transportation_cost := rec.transportation_cost;
    v_mold_tbl(1).transportation_account := rec.transportation_account;
    v_mold_tbl(1).freight_code := rec.freight_code;
    v_mold_tbl(1).containers := rec.containers;
    v_mold_tbl(1).waybill_airbill := rec.waybill_airbill;
    v_mold_tbl(1).expected_arrival_date := rec.expected_arrival_date;
    v_mold_tbl(1).transfer_subinventory := rec.transfer_subinventory;
    v_mold_tbl(1).transfer_organization := rec.transfer_organization;
    v_mold_tbl(1).transfer_to_location := rec.transfer_to_location;
    v_mold_tbl(1).new_average_cost := rec.new_average_cost;
    v_mold_tbl(1).value_change := rec.value_change;
    v_mold_tbl(1).percentage_change := rec.percentage_change;
    v_mold_tbl(1).material_allocation_temp_id := rec.material_allocation_temp_id;
    v_mold_tbl(1).demand_source_header_id := rec.demand_source_header_id;
    v_mold_tbl(1).demand_source_line := rec.demand_source_line;
    v_mold_tbl(1).demand_source_delivery := rec.demand_source_delivery;
    v_mold_tbl(1).item_segments := rec.item_segments;
    v_mold_tbl(1).item_description := rec.item_description;
    v_mold_tbl(1).item_trx_enabled_flag := rec.item_trx_enabled_flag;
    v_mold_tbl(1).item_location_control_code := rec.item_location_control_code;
    v_mold_tbl(1).item_restrict_subinv_code := rec.item_restrict_subinv_code;
    v_mold_tbl(1).item_restrict_locators_code := rec.item_restrict_locators_code;
    v_mold_tbl(1).item_revision_qty_control_code := rec.item_revision_qty_control_code;
    v_mold_tbl(1).item_primary_uom_code := rec.item_primary_uom_code;
    v_mold_tbl(1).item_uom_class := rec.item_uom_class;
    v_mold_tbl(1).item_shelf_life_code := rec.item_shelf_life_code;
    v_mold_tbl(1).item_shelf_life_days := rec.item_shelf_life_days;
    v_mold_tbl(1).item_lot_control_code := rec.item_lot_control_code;
    v_mold_tbl(1).item_serial_control_code := rec.item_serial_control_code;
    v_mold_tbl(1).item_inventory_asset_flag := rec.item_inventory_asset_flag;
    v_mold_tbl(1).allowed_units_lookup_code := rec.allowed_units_lookup_code;
    v_mold_tbl(1).department_id := rec.department_id;
    v_mold_tbl(1).department_code := rec.department_code;
    v_mold_tbl(1).wip_supply_type := rec.wip_supply_type;
    v_mold_tbl(1).supply_subinventory := rec.supply_subinventory;
    v_mold_tbl(1).supply_locator_id := rec.supply_locator_id;
    v_mold_tbl(1).valid_subinventory_flag := rec.valid_subinventory_flag;
    v_mold_tbl(1).valid_locator_flag := rec.valid_locator_flag;
    v_mold_tbl(1).locator_segments := rec.locator_segments;
    v_mold_tbl(1).current_locator_control_code := rec.current_locator_control_code;
    v_mold_tbl(1).number_of_lots_entered := rec.number_of_lots_entered;
    v_mold_tbl(1).wip_commit_flag := rec.wip_commit_flag;
    v_mold_tbl(1).next_lot_number := rec.next_lot_number;
    v_mold_tbl(1).lot_alpha_prefix := rec.lot_alpha_prefix;
    v_mold_tbl(1).next_serial_number := rec.next_serial_number;
    v_mold_tbl(1).serial_alpha_prefix := rec.serial_alpha_prefix;
    v_mold_tbl(1).shippable_flag := rec.shippable_flag;
    v_mold_tbl(1).posting_flag := rec.posting_flag;
    v_mold_tbl(1).required_flag := rec.required_flag;
    v_mold_tbl(1).process_flag := rec.process_flag;
    v_mold_tbl(1).error_code := rec.error_code;
    v_mold_tbl(1).error_explanation := rec.error_explanation;
    v_mold_tbl(1).attribute_category := rec.attribute_category;
    v_mold_tbl(1).attribute1 := rec.attribute1;
    v_mold_tbl(1).attribute2 := rec.attribute2;
    v_mold_tbl(1).attribute3 := rec.attribute3;
    v_mold_tbl(1).attribute4 := rec.attribute4;
    v_mold_tbl(1).attribute5 := rec.attribute5;
    v_mold_tbl(1).attribute6 := rec.attribute6;
    v_mold_tbl(1).attribute7 := rec.attribute7;
    v_mold_tbl(1).attribute8 := rec.attribute8;
    v_mold_tbl(1).attribute9 := rec.attribute9;
    v_mold_tbl(1).attribute10 := rec.attribute10;
    v_mold_tbl(1).attribute11 := rec.attribute11;
    v_mold_tbl(1).attribute12 := rec.attribute12;
    v_mold_tbl(1).attribute13 := rec.attribute13;
    v_mold_tbl(1).attribute14 := rec.attribute14;
    v_mold_tbl(1).attribute15 := rec.attribute15;
    v_mold_tbl(1).movement_id := rec.movement_id;
    v_mold_tbl(1).reservation_quantity := rec.reservation_quantity;
    v_mold_tbl(1).shipped_quantity := rec.shipped_quantity;
    v_mold_tbl(1).transaction_line_number := rec.transaction_line_number;
    v_mold_tbl(1).task_id := rec.task_id;
    v_mold_tbl(1).to_task_id := rec.to_task_id;
    v_mold_tbl(1).source_task_id := rec.source_task_id;
    v_mold_tbl(1).project_id := rec.project_id;
    v_mold_tbl(1).source_project_id := rec.source_project_id;
    v_mold_tbl(1).pa_expenditure_org_id := rec.pa_expenditure_org_id;
    v_mold_tbl(1).to_project_id := rec.to_project_id;
    v_mold_tbl(1).expenditure_type := rec.expenditure_type;
    v_mold_tbl(1).final_completion_flag := rec.final_completion_flag;
    v_mold_tbl(1).transfer_percentage := rec.transfer_percentage;
    v_mold_tbl(1).transaction_sequence_id := rec.transaction_sequence_id;
    v_mold_tbl(1).material_account := rec.material_account;
    v_mold_tbl(1).material_overhead_account := rec.material_overhead_account;
    v_mold_tbl(1).resource_account := rec.resource_account;
    v_mold_tbl(1).outside_processing_account := rec.outside_processing_account;
    v_mold_tbl(1).overhead_account := rec.overhead_account;
    v_mold_tbl(1).flow_schedule := rec.flow_schedule;
    v_mold_tbl(1).cost_group_id := rec.cost_group_id;
    v_mold_tbl(1).demand_class := rec.demand_class;
    v_mold_tbl(1).qa_collection_id := rec.qa_collection_id;
    v_mold_tbl(1).kanban_card_id := rec.kanban_card_id;
    v_mold_tbl(1).overcompletion_transaction_id := rec.overcompletion_transaction_id;
    v_mold_tbl(1).overcompletion_primary_qty := rec.overcompletion_primary_qty;
    v_mold_tbl(1).overcompletion_transaction_qty := rec.overcompletion_transaction_qty;
    v_mold_tbl(1).end_item_unit_number := rec.end_item_unit_number;
    v_mold_tbl(1).scheduled_payback_date := rec.scheduled_payback_date;
    v_mold_tbl(1).line_type_code := rec.line_type_code;
    v_mold_tbl(1).parent_transaction_temp_id := rec.parent_transaction_temp_id;
    v_mold_tbl(1).put_away_strategy_id := rec.put_away_strategy_id;
    v_mold_tbl(1).put_away_rule_id := rec.put_away_rule_id;
    v_mold_tbl(1).pick_strategy_id := rec.pick_strategy_id;
    v_mold_tbl(1).pick_rule_id := rec.pick_rule_id;
    v_mold_tbl(1).common_bom_seq_id := rec.common_bom_seq_id;
    v_mold_tbl(1).common_routing_seq_id := rec.common_routing_seq_id;
    v_mold_tbl(1).cost_type_id := rec.cost_type_id;
    v_mold_tbl(1).org_cost_group_id := rec.org_cost_group_id;
    v_mold_tbl(1).move_order_line_id := rec.move_order_line_id;
    v_mold_tbl(1).task_group_id := rec.task_group_id;
    v_mold_tbl(1).pick_slip_number := rec.pick_slip_number;
    v_mold_tbl(1).reservation_id := rec.reservation_id;
    v_mold_tbl(1).transaction_status := rec.transaction_status;
    v_mold_tbl(1).transfer_cost_group_id := rec.transfer_cost_group_id;
    v_mold_tbl(1).lpn_id := rec.lpn_id;
    v_mold_tbl(1).transfer_lpn_id := rec.transfer_lpn_id;
    v_mold_tbl(1).pick_slip_date := rec.pick_slip_date;
    v_mold_tbl(1).content_lpn_id := rec.content_lpn_id;
    v_mold_tbl(1).transaction_quantity := p_pick_conf_qty;
    v_mold_tbl(1).primary_quantity := p_pick_conf_qty;
    v_mold_tbl(1).shipped_quantity := p_pick_conf_qty;
    INV_PICK_WAVE_PICK_CONFIRM_PUB.PICK_CONFIRM(p_api_version_number => 1.0,
                                                p_init_msg_list      => FND_API.G_FALSE,
                                                p_commit             => FND_API.G_FALSE,
                                                x_return_status      => l_return_status,
                                                x_msg_count          => l_msg_count,
                                                x_msg_data           => l_msg_data,
                                                p_move_order_type    => 3 -- PickWave - Order
                                                p_transaction_mode   => 1 -- 1:On-Line, 2:Concurrent, 3:Background
                                                p_trolin_tbl         => v_moveln_tbl_d,
                                                p_mold_tbl           => v_mold_tbl,
                                                x_mmtt_tbl           => v_mold_tbl,
                                                x_trolin_tbl         => v_moveln_tbl_o,
                                                p_transaction_date   => SYSDATE);
    COMMIT;
    DBMS_OUTPUT.PUT_LINE('Return status of INV_PICK_WAVE_PICK_CONFIRM_PUB.PICK_CONFIRM = ' ||
                         l_return_status);
    IF l_return_status != FND_API.G_RET_STS_SUCCESS THEN
      pStatus := cv_fail;
      pMsgData := 'Failed to pick confirm move order inv_pick_wave_pick_confirm_pub.pick_confirm for MOVE_ORDER_LINE_ID : ' ||
                  vMoveOrderLineId;
      GOTO end_of_pkcnf;
    END IF;
    v_api_pick_confirm := 1;
    dbms_output.put_line('Status of the Pick Confirm is : ' ||
                         l_return_status);
    <<end_of_pkcnf>>
    NULL;
end loop;
END;
Updating Shipping attributes
DECLARE
--Standard Parameters.
p_api_version NUMBER;
init_msg_list VARCHAR2(30);
p_commit      VARCHAR2(30);
--Parameters for WSH_DELIVERY_DETAILS_PUB.update_shipping_attributes.
source_code        VARCHAR2(15);
changed_attributes WSH_DELIVERY_DETAILS_PUB.ChangedAttributeTabType;
--out parameters
x_return_status VARCHAR2(10);
x_msg_count     NUMBER;
x_msg_data      VARCHAR2(2000);
x_msg_details   VARCHAR2(3000);
x_msg_summary   VARCHAR2(3000);
-- Handle exceptions
vApiErrorException EXCEPTION;
BEGIN
-- Initialize return status
x_return_status := WSH_UTIL_CORE.G_RET_STS_SUCCESS;
-- Call this procedure to initialize applications parameters
FND_GLOBAL.APPS_INITIALIZE(user_id      => 0,
                             resp_id      => 21623,
                             resp_appl_id => 660);
source_code := 'OE';
changed_attributes(1).delivery_detail_id := 9317811; -- delivery_detail_id
changed_attributes(1).shipped_quantity := 0; -- quantity to update
changed_attributes(1).cycle_count_quantity := 30;
--Call to WSH_DELIVERY_DETAILS_PUB.Update_Shipping_Attributes.
WSH_DELIVERY_DETAILS_PUB.Update_Shipping_Attributes(p_api_version_number => 1.0,
                                                      p_init_msg_list      => init_msg_list,
                                                      p_commit             => p_commit,
                                                      x_return_status      => x_return_status,
                                                      x_msg_count          => x_msg_count,
                                                      x_msg_data           => x_msg_data,
                                                      p_changed_attributes => changed_attributes,
                                                      p_source_code        => source_code);
                                                      commit;
IF (x_return_status <> WSH_UTIL_CORE.G_RET_STS_SUCCESS) THEN
    RAISE vApiErrorException;
ELSE
    dbms_output.put_line('The shipped quantity is updated with ' ||
                         changed_attributes(1)
                         .shipped_quantity || ' for the delivery detail ' ||
                         changed_attributes(1).delivery_detail_id);
END IF;
EXCEPTION
WHEN vApiErrorException THEN
    WSH_UTIL_CORE.get_messages('Y',
                               x_msg_summary,
                               x_msg_details,
                               x_msg_count);
    IF x_msg_count > 1 THEN
      x_msg_data := x_msg_summary || x_msg_details;
      DBMS_OUTPUT.PUT_LINE('Message Data : ' || x_msg_data);
    ELSE
      x_msg_data := x_msg_summary;
      DBMS_OUTPUT.PUT_LINE('Message Data : ' || x_msg_data);
    END IF;
WHEN OTHERS THEN
    DBMS_OUTPUT.PUT_LINE('Unexpected Error: ' || SQLERRM);
END;
Thanks

Hi,
Goto VTFL.Select you valid combination.
Click on item.Select yout item category there.Goto details.
Select the Pos/neg quantity field as "+".
Maintain the billing quantity as "A".
Maintain VBRK/VBRP as "001".
Save.
Goto VOV7 and select your item category.Details.
Select completion rule as "B" and billing relevance as "F".
Save.
Pls go through the follwing threads that are posted by me earlier.
[Invoice split|Re: Invoice split]
[Splitiing of invoice|Re: Invoice split]
Regards,
Krishna.

Office 2013 Home and Business not updating

I have two PCs on my network that I bought from Dell. Both came with a license for Office 2013 Home and Business. Office trial version was already on the machines and i just registered and activated the trial version using the licenses I was given from Dell.
Everything was fine until I was troubleshooting a duplicate email issue in Outlook on of the machines. At this time I noticed Office didn't appear to be on the latest version of click-to-run. I am relatively unfamiliar with click-to-run Office 2013 and the
changes to how it updates. Apparently it does this automatically. Problem is these two machines don't appear to be updating at all. I can't find an update history just a version number. I found online and performed the following troubleshooting steps:
1.) Disable then re-Enable Updates by going into File -> Account -> Update Options
- this seamed to start the downloading of updates but they never installed. That window telling me they were
downloading just goes away and nothing happens.
2.) If "1" doesn't work try an Online Repair.
- the repair begins and ends before completing saying "Something happened". This effectively breaks the install and
a following dialog box explains that Office was uninstalled.
3.) Re-install Office
- but have to run a cleanup tool first to remove remnants of previous install. I then find it difficult to find an
installer that will work at all kept getting "Something happened" message. Finally Dell support found an installer that
works. however even after the install Office will not update.

Per your post, it seems that you activate the Office 2013 Home and Business trial version by Dell provided. I can confirm the update service is available for Office 365 subscription users, but I am not sure whether it is working for the trail version.
You'd better confirm it with you Dell provider or post a new thread in
Office 365 forum, thanks.
Tony Chen
TechNet Community Support

PM Confirmations to update CATS2 (IW42 - CATS2)

Similar Messages

Maybe you are looking for