WM Partial TO confirmation and delivery

Please help me on how to resolve below WM scenario
1)Outbound delivery of 5 quantity created
2)Transfer order created with quantity 5
3) Transfer order partially confirmed of quantity 3
Now I am unable to do Post Goods Issue as error "Delivery has not yet been put away / picked (completely)" is displayed
Requirement is that Remaining qty is to return to source storage bin and Post Goods Issue should be allowed with the picked quantity. Is there any config settings for serving this purpose?
Can the delivery get updated with the WM picked quantity?
Regards
Iyer Kartik

Hello,
Ideally, if you have partially confirmed the transfer the same should get updated in your outbound delivery.The delivery quantity which was 5 when it was created sales order/ purchase order, must get updated to 3.
Please check whether your delivery qty in Outbound delvery is update to 3, so that you can do the post goods issue.
Also the remaining qty can be transfered using transaction MB1B and movement type specifically defined for warehouse supervision.
Br,
Tushar

Similar Messages

"Material is not the same for confirmation and delivery"

Hello
If this is not the right forum, my apologies. Direct me to the correct one if it is not ....
Have been doing automated test development (HP's QTP) against SAP systems for over a year. I am not an application expert - very much a newbie when it comes to application knowledge but trying to gain some. I have "googled" the phase "Material is not the same for confirmation and delivery" and have not been able to find any references. What does this mean?
I see this message for an iDoc using WE02. Have looked and looked but don't really know what I'm looking for.
Clues?
Thanks,
DW

DW,
I have never seen that exact message, but I have seen similar ones. Generically, the message probably means that you are attempting to perform a transaction against a document (perhaps a Purchase order?) and the Material number (Part Number) contained in the transaction is not the same as the Material number in the originating document in SAP.
An example might be you have previously created a confirmation against a Purchase order, which now exists in SAP. This Confirmation is for a specific Purchase order, item, and material. Now, when you attempt to create an inbound delivery for the Confirmation, the material number contained in the new IDOC is different from the material number that was contained in the original Confirmation.
I don't know what IDOC Message type you are having the problem with, but generically you can do some troubleshooting. Find the SAP Material number in the IDOC (MATNR probably). Find the appropriate reference document number in the IDOC (confirmation number? Purchase order number? or...?), and then manually review the document in SAP to ensure that the Material numbers are the same.
If you are totally lost, you should really consult with an SAP App expert. I am guessing that this is part of the Materials Management module, so you would be asking for an MM expert.
Or, you can send more details, and we can try to help.
What is the IDOC message type?
What is the Message number of the error message? Functionally, what is this IDOC trying to do, from a business perspective?
Rgds,
DB49

In order confirmation i need invoice number and delivery number.

Dear Experts,
I need invoice number and delivery number in order confirmation.
how can i get the delivery number an invoice number.
Program name: RVADOR01
Regards
Ahmed

Hi
In the Order confirmation Only sales order details will be there
You better write a PERFORM statement in Script and in the subroutine fetch the Delivery number and Invoice number with the following links and display them in script
LIPS-VGBEL = VBAK-VBELN
LIPS-VGPOS = VBAP-POSNR
VBRP-AUBEL = VBAK-VBELN
VBRP-AUPOS = VBAP-POSNR
You can also can use the VBFA table
using Prev doc type = C (order) and Subsequent doc type = J to get the Delivery
and Sunsequent type = M for getting the Invoice Number
see the sample code for subroutine
REPORT ZMPO1 .
form get_freight tables in_par structure itcsy out_par structure itcsy.
tables: ekko,konv,t685t.
data: begin of itab occurs 0,
 ebeln like ekko-ebeln,
 knumv like ekko-knumv,
 end of itab.
data: begin of itab1 occurs 0,
 knumv like konv-knumv,
 kposn like konv-kposn,
 kschl like konv-kschl,
 kbetr like konv-kbetr,
 waers like konv-waers,
 kwert like konv-kwert,
 end of itab1.
data: begin of iout occurs 0,
 kschl like konv-kschl,
 vtext like t685t-vtext,
 kbetr like konv-kbetr,
 kwert like konv-kwert,
 end of iout.
data v_po like ekko-ebeln.
read table in_par with key 'EKKO-EBELN'.
if sy-subrc = 0.
 v_po = in_par-value.
 select
 ebeln
 knumv
from ekko
into table itab
where ebeln = v_po.
if sy-subrc = 0.
 loop at itab.
 select
 knumv
 kposn
 kschl
 kbetr
 waers
 kwert
 into table itab1
 from konv
 where knumv = itab-knumv and
 kappl = 'M'.
 endloop.
 loop at itab1.
 if itab1-kposn <> 0.
 select single * from t685t
 where kschl = itab1-kschl
 and kappl = 'M'
 and spras = 'EN'.
 iout-vtext = t685t-vtext.
 iout-kschl = itab1-kschl.
 iout-kbetr = itab1-kbetr.
 iout-kwert = itab1-kwert.
 append iout.
 clear iout.
 endif.
 endloop.
 sort itab1 by kposn.
 loop at iout.
 sort iout by kschl.
 if ( iout-kschl eq 'GSDC' OR
 iout-kschl eq 'GSFR' OR
 iout-kschl eq 'GSIR' ).
 at end of kschl.
 read table iout index sy-tabix.
 sum.
 write:/ iout-kschl,iout-vtext,iout-kwert.
 out_par-name = 'A1'.
 out_par-value = iout-vtext.
 append out_par.
 out_par-name = 'A2'.
 out_par-value = iout-kwert.
 append out_par.
 endat.
 endif.
 endloop.
 endif.
endif.
endform.
IN THE FORM I AM WRITING THIS CODE.
/:DEFINE &A1& = ' '
/:DEFINE &A2& = ' '
/:PERFORM GET_FREIGHT IN PROGRAM ZMFORM_PO1
/:USING &EKKO-EBELN&
/:CHANGING &A1&
/:CHANGING &A2&
/:ENDPERFORM
&A1&
&A2&
This Code is to be written in the PO form under ADDRESS window.
/:DEFINE &A1& = ' '
/:DEFINE &A2& = ' '
/:DEFINE &A3& = ' '
/:DEFINE &A4& = ' '
/:DEFINE &A5& = ' '
/:DEFINE &A6& = ' '
/:PERFORM GET_VENDOR IN PROGRAM ZMFORM_PO
/:USING &EKKO-EBELN&
/:CHANGING &A1&
/:CHANGING &A2&
/:CHANGING &A3&
/:CHANGING &A4&
/:CHANGING &A5&
/:CHANGING &A6&
/:ENDPERFORM
&A1&
&A2&
&A3&
&A4&
&A5&
&A6&
Regards
Anji

User exits for delivery picking confirmation and transfer order creation

Hi
We have a scenario for which we need help.
This is to do with replenishment from plant to plant.
We have sales sets.
The sales sets needs to be replenished from one plant to another. We want the componenets of the sales sets to picked from the issuing plant. For this we need a transfer order. this needs tobe confirmed and then the goods issue should take place from the issuing plant. Its a two step process.
we are doing Sales sets in STO. The explosion takes place in STO. However when we create deliveries for this. Only the sales set header item without its components are flowing into the delivery.
The Tranfer order does not contain the components either.
However post the goods issue we can create a TO with reference to the TR. This is is not acceptable because we want the picking and confirmation to occur before PGI from the issuing plant.
Could anybody help: We want the TO to be created with the components even though in the delivery only the Sales set header appears. Can u suggest a user exit in which when we create the TR from the delivery the components of the set.
After confirmation of the TO then we want the picking status to be put as C.
Supreeth

Hi,
Check the following users exits.
MWMRFSSG            user exit for sorting TOs in RF system-guided transaction
MWMRFUP             Customer defined general purpose pushbutton called from scr.
MWMRP001            Cust. Exit for Fixed Bin Replenish.: Delivery Item Selection
MWMRP002            Cust. Exit for Fixed Bin Replenishment: TR Quantity Distr.
MWMRP003            Customer Exit for Replenishment using RLLNACH1
MWMRP004            User Exit for Replenishment using RLLNACH4
MWMTO001            Enhancements for end of transfer order generation
MWMTO010            Exit: Calculation of Total Planned TO Processing Time
MWMTO011            Correction of Planned Processing Time for TO Item
MWMTO012            Correction of Sorting and Split Transfer Order
MWMTO013            Stock Removal for Sev. Storage Types as in Stringent FIFO
MWMTOAU3            Separate selection of posting changes for autom.TO creation
MWMTR001            Exits at the end of transfer rqmnt creation (IM,PP interf.)
MWMD0001            Transfer order print via RLVSDR40
MWMD0002            Transfer order print as multiple process with RLKOMM40
MWMIDI07            Enhancement for Output WMPIHU (Create Pick-HU) Inbound
MWMIDO11            Enhancement for message WMTORD: TO with several items
MWMIDO12            Enhancement for Output WMPIHU (Pick-HUs) Outbound
MWMIDO13            Extension for WMMBXY (subsequent tasks after goods movement)
MWMPP001            Enhancement WM/PP Interface (automatic TR generation)
Regards,
Murali

CC charged and email confirmation says delivery on 24th

It sounds like I was one of the lucky ones who was able to squeak in an order for delivery yesterday.
My email confirmation and account status say it will deliver on the 24th. How much are we betting this will still be accurate with the huge demand we've seen?
I also was under the impression my card wouldn't be charged until it shipped. Anyone else who got an order in yesterday see this?
Just excited to receive the phone like the rest of us.
And yes, I don't trust the reservations after having worked in Apple stores for launches. That is not a safety blanket folks. Get there early if you actually want to get a phone on launch day.

Yes, I made my order yesterday at about 8:30 pm eastern standard time. The charge has posted to my credit card and my email confirmation indicates delivery on June 24th. I also checked my order status today and it too says delivery for June 24th. But just in case it does not arrive, i do have one on reserve at the apple store.

Partial confirmation and credit block

Hi Friends,
I have a scenario where we are using automatic credit check. in the sales order based on the availability check the full 2 quantity is confirmed and then there is a credit block. hence i check back the document and the confirmed quantity becomes 0. When i release the credit check thru vkm3 and check the sales doc again the quantity is now confirmed for 2.
But the same doesnt happen for if the order quantity is 2 and the confirmed quantity is 1 and the credit check happens. Once the credit check is released the sales doc still shows 0 quantity rather than 1 confirmed quantity.
Any suggestions?
Regards,
Anand

Hi Friends,
I got the solution to this problem. The 'availa;bity check rule' which is there in AvC>ATP>Define default settings; was set to 'E' from 'blank'. Earilier because it was set to blank it used to do a recheck after the credit relealseon the full quantity, hence if the order qty was equal to the confirmed qty after the release it showed the confirmed qty. but when the confirmed qty was less than the ordered qty, when the avcheck happened after the credit release it used to check for the full quantity, where it will fail, so the confirmed qty would go back to zero.
Thanks for all your help.
Regards,
Anand

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.

Purchase Order and Delivery

I am using DELVRY03 and FM: IDOC_INPUT_DESADV1. I want to in wch function does the PO confirmation and Inbound Delivery gets updated or generated. I want order confirmation without the inbound delivery.Can anyone help me in this matter????

i got to know how to proceed. Thanks all for helping me out

Process Order does Confirmations and GR even after the Process order is CNF

Not Sure why the Formatting is lost.
Hi Gurus,
I am a beginner in this area and request your help.
We are implementing a project where the process order Confirmation in SAP ECC 5.0 in SAP PPPI module is done using xMII which call the BAPI_PROCORD_CREATE_TT     RFC.
The customer wants to (certain times) do a final confirmation without actually completing the order e.g if the Order Qty is 100 then, they want to just manufacture 25 and then do a final confirmation, after which SAP GUI screen does not allow any Process order Confirmations against that process order.
We are using the BAPI_PROCORDCONF_CREATE_TTRFC to do multiple PO Confirmations and GR for particular Process order. Below is a scenario
Case 1:
1. Order Qty =100 ( Unlimited Delivery is not checked and tolerance is Zero).
     Which means only 100 is accepted.
2. 100 Quantities are produced and confirmed using the BAPI_PROCORDCONF_CREATE_TT (with Final confirmation value as 1 , which mean auto confirmation)
3. Next when the BAPI confirms & GR's against the same order, the Complete qty is not visible in the COR3 status. And is visible only in the COGI transaction.
That is expected behavior. and i am ok with that.
Case 2: (The one with the problem)
1. Order Qty =100 ( Unlimited Delivery is not checked and tolerance is Zero).
     Which means only the 100 is accepted.
2. 25 Quantities are produced and confirmed using BAPI_PROCORDCONF_CREATE_TT (with Final Confirmation value as X , which mean Final confirmation)
3. The Confirmation and GR go through and the status of the process order now changed is CNF and the Deliverd qty is 25.
At this point , if you logon to SAP GUI and try to make a process order confirmation you get an error messages which says the Process Order is already confirmed and no more confirmations or GR can be done against this Process order.
4. But when you Again Run the BAPI_PROCORDCONF_CREATE_TT, it goes ahead and confirms and makes the GR for that Process order.
The Expected Behavior should have been that this quantity is now in the COGI transaction.
5. The Process order allows any number of Further confirmations till the Ordered Qty and Delivered quantity are same .
so dear gurus I know i have written a very long doubt but would be very happy to get a response from you. I would ideally not like to enhance or change the BAPI and want to understand if I have missed some setting or parameter that I have to pass in the BAPI for the final confirmation so that once the Status of the Process order is CNF , no more Confirmations are allowed even from the BAPI.
Thanks in Advance.
Regards
Suraj

Hi Suraj,
I am not positive, but I suspectt the problem lies in the BAPI. It might be how you have the data set in MII, but it sounded like you are doing it correctly.
However there are a number of things you can do to troubleshoot your situation.
First create a few process orders to test with.
Record the confirmation numbers and counters for each of the following:
1) Do a final confirmation (for quantity of 25 instead of the 100) in CORK (or whichever transaction you are using).
2) Do a final confirmation (for quantitiy of 25 instead of the 100) in SE37 or BAPI in ERP using the BAPI_PROCORDCONF_CREATE_TT.
3) Do a final confirmation (for quantitiy of 25 instead of the 100) from MII using your current transaction.
Review the confirmations in ERP to see if there are any differences.
Review the confirmaitons in MII to see if there are any non visible differences (use a Tracer to retrieve the response segment from an execution of BAPI_PROCORDCONF_GETDETAIL using the recorded confirmation numbers and counters)
Case 1) If there are differences in the results, that should tell you how to modify your transaction to include or change the appropriate values in your inputs.
Case 2) If there are no differences, then it is most likely that there is something not working properly in the BAPI you are using. It may not completely replicate the functionality in CORK (or whichever transaction you are using in ERP). Then open a ticket, because the BAPI is not working as it should.
Good luck,
Mike
Edited by: Michael Appleby on Aug 17, 2009 8:20 PM

Schedule Line Confirmations after delivery

I need to be able to delivery a confirmed schedule line, then go back and add quantity to the sales order and confirm the additional quantity. The system is showing the original schedule (pre-delivery) confirmed and delivered, but the added quantity shows on the schedule lines, but remains unconfirmed, even if I run availability check again. sch. line cat is CP. If I add the additional qty as another line item, it confirms.
Any advice?

Hi,
Where are you adding the additional quantity? Have you tried adding in the Confirmed Quantity Column in the Schedule lines tab?
Thanks
Krish.

Difference between Scheduling lines and Delivery schedule

Hi SD Experts
can u say me the clear difference between Scheduling lines and Delivery schedule.
where we will maintain deliver schedule. whether delivery schedule is automatically created along scheduling agreements..
with regards
James

Hi James,
Schedule Lines: Has basically information realted to delivery scheduling in Sales Order level.
Delivery Scheduling: Is a process using which system will determine what are the different activities which need to be performed and time taken for each activitiy only after which the material can be delivered to the customer.
Delievry scheduling will be started only from the material availability date i.e., system will first determine the material avail date and then do scheduling. By default Standard SAP system does Backward Scheduling in case material availability falls beyond the required delivery date system will do forward schedluing
Delivery Scheduling consists of the following Basic activities:
We give deatils while creating order:
Order Creation Date
Required Delivery Date
Order date - Material availability date - Transportation Planning Date - Loading date - Goods Issue Date - Required Delivery Date
Time Between GI Date and required Delivery Date is called Transit Time
Time Between LoadingDate and GI Date is called Loading time
Time Between Material Availability Date and Loading Date consists of 2 components - Pick / PackTime and Transportation Planning Time
System has to calculate all this before it determines the confirmed delivery date.
Give your mail Id I have some Presentation I will send you across.
REWARD POINTS IF IT HELPS
Regards
Srini

IDocs for Invioce and Delivery

Hi all,
I have to send the customer the Invoice and Delivery confirmation for that order placed by him through an IDoc in background job.
We are going for a standard IDoc for invoice and Delivery also but how to fill the data into that standard IDoc.
1.Do we have standard report like (BD12, BD14, BD10 etc.)
2.Should we develop a report to fill the data into that Idoc.
Please help me to find standard report or please help me to write code for that standard IDoc.
Thank you all in advance,
Regards,
Shalem.

Hi Shalem,
You need to do the following activities.
- Setup condition record (t/code NACE) for shipping (V2) and billing (V3).
- Setup output type (t/code NACT) for shipping (V2) and billing (V3) with transmission medium A (ALE).
- Setup procedures (t/code NACZ) for shipping (V2) and billing (V3) if required.
- Once the above setup are done, for any creation of billing and shipping will create entries into table NAST (Message Status).
- Then you can create IDoc using this standard program RSNAST00. Please ensure your ALE and IDoc configuration have been done such as BD64, WE20, WE21 and etc.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

Read and Delivery Receipts

My Blackberry Curve sends read and delivery receipts to the email sender and to my email. Many times I don't even open the message. In my BB email options, I have NO marked on confirm delivery, confirm read and send read receipts. Does anyone know how to make these stop sending?

open messages icon - menu - options - email settings - make sure it shows your email beside MESSAGE SERVICE
change CONFIRM DELIVERY and CONFIRM READ and READ RECEIPTS to NO

Req. delivery date and Delivery date should be same in a sales order

Hi experts,
We need a customization for getting Requested delivery date, Material Availability date and Delivery date should be same.
Example if I keep request delivery date as 12/12/2012, system should consider same dates for MAD and Delivery and confirm the requested quantity.
How to achieve this customization..
Thanks,
Bala.

system should consider same dates for MAD and Delivery and confirm the requested quantity
What you are going to achieve by this? Hope you know the concept of MAD and confirmed quantity fields. Let us assume, if stock is not there for a material for which sale order is created, can you let me know, you want the system still to confirm the quantity? You can post the goods issue only if system confirms the quantity in schedule line which is possible, only if stock is made available. If client asks something which is not possible in SAP, think in a logical way how SAP works and convince them accordingly.
G. Lakshmipathi

Order confirmation with delivery date in past

Hello everybody,
In the SNC portal, we have a lot of old Purchase order which are not confirmed, and when we try to confirmed them, we have the error below :
Order XXXXXXXX, item 00010, schd. line 0000000002: delivery date lies in past
My client wish create a super user (admin ?) who can confirmed a Purchase Order item with a delivery date in past (for example 06/08/2011).
Is it possible to create such profiles? If so how to configure it in SNC.
Are there other solutions ?
Thank you very much for your help.
Stéphane.

Hi Stéphane,
Normally in a standard SAP settings Purchase order confirmation in past gives warning message but you can have PO confirmation in past from warning to error or Information.
Go to SPRO>Supply Network Collaboration>Basic Settings>Validation>Own Settings-->Maintain Settings in Validation Profiles
Maintained below setting if you want message as information (No error or warning message)
Profile:POC2
Validation check:PO_DELVRY_DATETIME_IN_PAST
Msg.Type:I
Save Mode:Save Message as Valid
Continuation Mode:Continue checks
Profile:POC3
Validation check:PO_DELVRY_DATETIME_IN_PAST
Msg.Type:I
Save Mode:Save Message as Valid
Continuation Mode:Continue checks
Maintained below setting if you want message as error
Profile:POC2
Validation check:PO_DELVRY_DATETIME_IN_PAST
Msg.Type:E
Save Mode:DO not Save Message
Continuation Mode:Discontinue checks
Profile:POC3
Validation check:PO_DELVRY_DATETIME_IN_PAST
Msg.Type:E
Save Mode:DO not Save Message
Continuation Mode:Discontinue checks
Maintained below setting if you want message as warning
Profile:POC2
Validation check:PO_DELVRY_DATETIME_IN_PAST
Msg.Type:W
Save Mode:Save Message as Valid
Continuation Mode:Continue checks
Profile:POC3
Validation check:PO_DELVRY_DATETIME_IN_PAST
Msg.Type:W
Save Mode:Save Message as Valid
Continuation Mode:Continue checks
Above setting is a generic setting for all user and If you need User specific setting then it is a customization required.
Regards,
Nikhil

WM Partial TO confirmation and delivery

Similar Messages

Maybe you are looking for