ASN not updating in MD04

Followed the SMI fully automated process (Scheduling Agreement). Published an ASN succesfully in SNC but checking MD04 in the R3 system shows no ASN.
The system has been working without a problem with other materials, any ideas what could be wrong? I have checked for an IDOC in both systems (in integration monitor) but nothing is posted/generated (no errors either).
Thanks

Hi,
Did you check if the XML message is processed successfully in PI / XI system?
Does ASN work correctly for other materials (as you said)?
Regards,
Sandeep

Similar Messages

Open orders should not update in MD04

Hi, SD gurus,
I have the below requirement,
My business scenario is
when total open sales order quantity crosses a particular number(Ex:1000 Pcs) in a month, after that whatever the sales order we create it should not update in MD04.
Our Business process,
1. Creating a sales order
2. Allocation run (here system will execute Credit check, availability check, and listing an Exclusion etc. here we need to enter sales order no, plant, allocation type)
3. Creating a delivery
4. Invoicing the customer
Note:
Usually when we de check MRP type and allocation in Scheduline category system should not update in MD04, but if we de check this as for our business process system should not execute Allocation run
Thanks in Advance
Yuvaraj.

Respected Lakshmipathiji,
Thanks for your clarification but i have query here..
""if the users are ready to do this manually once a line item exceeds 1000 pcs a month, well and good""
How users will check material wise?(suppose if sales order contains more than 100 line items and each line item will have its own requirement updates--will they do this material wise?)
Is there any report which give the Status on Requirements for group of materials(MD04 status) in Standard SAP??
Phanikumar

Sales Order not updated in MD04

Dear Gurus
Sales order is not getting updated in MD 04 for few Materials and those materials are not relevant for MRP.
Kindly help me in this regard
Thnx
MK

This may be due to schedule line category in the sales order ->item level.
In t.code VA03, enter the sales order number. Then highlight line item and click on schedule lines for items button on the bottom. Find the schedule line category derived for the item under schedule line category column.
Then go to t.code VOV6. Select the schedule line that you found in the sales order and click on details button. Under transaction flow, you will find Req/Assembly field, which may NOT be checked in your case. If this field is not checked, then the requirement will not be passed to MRP.
If this is checked and still you dont see the details in MD04, then run report SDRQCR21 in SA38 and check again.
Regards,

Issuance is not updating in Reservation and MD04

Hi folks!!
I am getting a problem in stock issuance.
While issuing against reservation created for production order, for some material the issued quantity is not getting updated in the withdrawl field in reservation, and it is also not getting updated in MD04.
what could be the possible reason. Please help
Best regards,

I got the answer,
We need to create production planning option in Consumption Based Planning--plant parameters.

Storage location entry in ASN is not reflected in MD04 screen

Hi Gurus,
We are using scheduling agreements with confirmations (ASN) . For some business reason we change the storage in inbound delivery created against the SA . However change effect of storage location is not reflected in MD04 .
In MD04 screen storage location is getting defaulted from the scheduling agreement .
Why the system is not considering the storage location from the inbound delivery ?
Thanks in advance

Thanks for the reply.
Indeed it will appear in MD04 if you change in SA. However I don`t want do that , in certain cases only I want change at IBD level which should reflect in MD04. Is there a way to achieve this ?
Thanks in advance

Sales Order number is not showing in MD04

Hi Gurus ,
I have got one case where Sales order number is not showing in MD04 screen . This sales order , line item has already delivered , PGI & billing document also been generated . Moreover accounting document is also been created .As cheeked & found that it is not shwoing in MD04 screen because at the time sales order creation availability check “01” was maintained which has sum up all the requirement in one particular day ( Also as
per SAP note -70408) .
Now because all the subsequent document has been generated for sales order so we can not mark it for “Rejection for rejection “ & to create new sales order with availability check “02” in material master .
Please let me know the possible solution for the same or if any sap note would be required to get the sales order number in MD04 .
Thanks ,
Aman

Hi Kiran ,
Actually before running the report in “SDRQCR21” in PRD I wanted to run it in “Quality “ .
In quality I am not able to simulate the same .
Please refer below points related to my testing result .
1.Mainatined availability check group “01” .
2 . Created Sales order
3. Check in MD04 screen & as expected sales order was coming blank with negative Qty .
4. Run the MRP which generated PR
5. PR converted to PO & GRN was done which updated the stock
6. Created delivery & checked the same in MD04 . It was also coming blank . No delivery document numbe was showing in screen but it was coming with negative Qty .
7. Done the PGI & blank delivery document number was removed & it become normal .
In PRD .
There are 3 sales order
One sales order is already marked reason for rejection & two sales order delivery , PGI has been done .
But still it is showing blank sales order with negative Qty & after MRP run it is generating the PR also .
I don't why it was showing with negative values .
Please refer attacehed screen shot .
Thanks,
Regards ,
Aman

Purchase Order history not updating in my STO

Dear Experts,
We are doing stock transfer order internally for FERT and *BOUGHT OUT * items. Now at the time of delivery through VL10B all bought out items are appear in outbouddelivery but FERT item material is not coming automatically in delivery. System pickes up item category as NLN but if i manually added FERT material at the end system picks up item category as ULN & purchase order history also not updated in STO.
Also in MD04 system is showing reservation against STO number & the result is i am not able to do delivery because system is showing message as only 0 qty is available for picking
Can any body helps me in this?
Thanks
Trupti

Hi,
Define your item category setting for your Delivery..
Under SPRO>Loge-Exce>Shipping-->Define item category determination in Deliveries.
Note: You should not enter the line item manually in delivery, thus it will store the item category as DLN (DLN is for without order Reference) so it wont record any history.
Regards
GK..
Edited by: Gnana Kumar on Oct 26, 2010 1:04 PM

Specific order not updated in MI

Hi,
I have a PM order for which no update (in description, operation or anything else...) that we do in R/3 PM can reach middleware. It's linked notification updates reach MI with no problem. All other orders update work just fine as well. Only this given order is not updated in MI.
I thought that it was F.M. MAM30_001_CHANGE that would be called to update it in middleware, but it is not used. What F.M. is used to update order in middeware?
Is there anybody that could give me a hint about my issue?
Thanks
Davy

This may be due to schedule line category in the sales order ->item level.
In t.code VA03, enter the sales order number. Then highlight line item and click on schedule lines for items button on the bottom. Find the schedule line category derived for the item under schedule line category column.
Then go to t.code VOV6. Select the schedule line that you found in the sales order and click on details button. Under transaction flow, you will find Req/Assembly field, which may NOT be checked in your case. If this field is not checked, then the requirement will not be passed to MRP.
If this is checked and still you dont see the details in MD04, then run report SDRQCR21 in SA38 and check again.
Regards,

Cannot update delivery attributes: the following field(s) are not updatable

Hi. I create in EBS simple Order
Now , my goal is to create a delivery , pick , change shipping quantity and ship confirm. Here is my code
DECLARE
p_sales_order NUMBER := 10014445;
p_line_number NUMBER := 1.1;
p_org_id NUMBER := 308;
l_shipped_quantity NUMBER := 5;
p_api_version_number NUMBER := 1.0;
init_msg_list VARCHAR2(200);
l_commit VARCHAR2(30);
x_msg_details VARCHAR2(3000);
x_msg_summary VARCHAR2(3000);
x_return_status VARCHAR2(3);
x_msg_count NUMBER;
x_msg_data VARCHAR2(3000);
p_validation_level NUMBER;
v_errbuf VARCHAR2(2000);
v_retcode VARCHAR2(20);
v_released_status wsh_delivery_details.released_status%TYPE;
v_inv_interfaced_flag wsh_delivery_details.inv_interfaced_flag%TYPE;
v_oe_interfaced_flag wsh_delivery_details.oe_interfaced_flag%TYPE;
v_source_code wsh_delivery_details.source_code%TYPE;
v_pending_interface_flag wsh_trip_stops.pending_interface_flag%TYPE;
l_changed_attributes wsh_delivery_details_pub.changedattributetabtype;
l_source_code VARCHAR2(30) := 'OE';
-- Parameters for WSH_DELIVERIES_PUB
p_delivery_name VARCHAR2(30);
p_action_code VARCHAR2(15);
p_asg_trip_id NUMBER;
p_asg_trip_name VARCHAR2(30);
p_asg_pickup_stop_id NUMBER;
p_asg_pickup_loc_id NUMBER;
p_asg_pickup_loc_code VARCHAR2(30);
p_asg_pickup_arr_date DATE;
p_asg_pickup_dep_date DATE;
p_asg_dropoff_stop_id NUMBER;
p_asg_dropoff_loc_id NUMBER;
p_asg_dropoff_loc_code VARCHAR2(30);
p_asg_dropoff_arr_date DATE;
p_asg_dropoff_dep_date DATE;
p_sc_action_flag VARCHAR2(10);
p_sc_intransit_flag VARCHAR2(10);
p_sc_close_trip_flag VARCHAR2(10);
p_sc_create_bol_flag VARCHAR2(10);
p_sc_stage_del_flag VARCHAR2(10);
p_sc_trip_ship_method VARCHAR2(30);
p_sc_actual_dep_date VARCHAR2(30);
p_sc_report_set_id NUMBER;
p_sc_report_set_name VARCHAR2(60);
p_sc_defer_interface_flag VARCHAR2(60);
p_sc_send_945_flag VARCHAR2(60);
p_sc_rule_id NUMBER;
p_sc_rule_name VARCHAR2(60);
p_wv_override_flag VARCHAR2(10);
p_asg_pickup_stop_seq NUMBER;
p_asg_dropoff_stop_seq NUMBER;
x_trip_id VARCHAR2(30);
x_trip_name VARCHAR2(30);
fail_api EXCEPTION;
x_debug_file VARCHAR2(100);
l_ship_method_code VARCHAR2(100);
l_user_id NUMBER;
l_resp_id NUMBER;
l_appl_id NUMBER;
CURSOR c_ord_details IS
SELECT DISTINCT det.source_header_number sales_order,
det.org_id,
det.source_line_number,
det.source_header_id,
det.source_line_id,
det.source_header_type_name,
det.inventory_item_id,
det.requested_quantity,
det.delivery_detail_id,
(SELECT concatenated_segments
FROM mtl_system_items_kfv
WHERE inventory_item_id = det.inventory_item_id
AND organization_id = det.organization_id) ordered_item,
det.organization_id,
det.src_requested_quantity,
det.shipped_quantity,
del.delivery_id,
del.status_code delivery_status_code,
det.released_status pick_release_status,
det.oe_interfaced_flag,
det.inv_interfaced_flag
FROM wsh_delivery_details det,
wsh_delivery_assignments asn,
wsh_new_deliveries del
WHERE 1 = 1
AND det.delivery_detail_id = asn.delivery_detail_id
AND asn.delivery_id = del.delivery_id(+)
AND det.source_header_number = 1199656
AND det.source_line_number = '1.1'
AND det.org_id = 10102
AND shipped_quantity IS NULL
AND NVL(del.status_code, 'OP') <> 'CL'
and det.delivery_detail_id =21439836
/* AND det.released_status = 'Y'*/;
BEGIN
-- Initializing the Applications
SELECT user_id INTO l_user_id FROM fnd_user WHERE user_name = 'MSHAPIRA';
SELECT responsibility_id, application_id
INTO l_resp_id, l_appl_id
FROM fnd_responsibility_vl
WHERE responsibility_name = 'OM Super User - UDS UK';
fnd_global.apps_initialize(l_user_id, l_resp_id, l_appl_id);
FOR i IN c_ord_details LOOP
DBMS_OUTPUT.put_line('Initializing the Application for Shipping Transactions');
-- Mandatory initialization for R12
mo_global.set_policy_context('S', i.org_id);
mo_global.init;
-- Ship Confirming
p_delivery_name := TO_CHAR(i.delivery_id);
DBMS_OUTPUT.put_line('Before Shipping, Calling WSH_DELIVERY_DETAILS_PUB API to Update Shipping Attributes');
DBMS_OUTPUT.put_line('=============================================');
l_changed_attributes(1).delivery_detail_id := i.delivery_detail_id;
l_changed_attributes(1).shipped_quantity := 5;
wsh_delivery_details_pub.update_shipping_attributes(p_api_version_number => 1.0,
p_init_msg_list => init_msg_list,
p_commit => l_commit,
x_return_status => x_return_status,
x_msg_count => x_msg_count,
x_msg_data => x_msg_data,
p_changed_attributes => l_changed_attributes,
p_source_code => l_source_code);
IF (x_return_status <> wsh_util_core.g_ret_sts_success) THEN
RAISE fail_api;
DBMS_OUTPUT.put_line('Failed to Update the Shipping Attributes');
ELSE
DBMS_OUTPUT.put_line('Successfully Updated the Shipping Attributes');
END IF;
BEGIN
SELECT shipping_method_code
INTO l_ship_method_code
FROM oe_order_headers_all
WHERE order_number = i.sales_order
AND org_id = i.org_id;
EXCEPTION
WHEN OTHERS THEN
l_ship_method_code := NULL;
END;
p_action_code := 'CONFIRM'; -- The action code for ship confirm
p_sc_action_flag := 'S'; -- Ship entered quantity.
p_sc_intransit_flag := 'Y';
--In transit flag is set to 'Y' closes the pickup stop and sets the delivery in transit.
p_sc_close_trip_flag := 'Y'; -- Close the trip after ship confirm
p_sc_trip_ship_method := l_ship_method_code; -- The ship method code
p_sc_defer_interface_flag := 'Y';
p_sc_stage_del_flag := 'Y';
p_sc_create_bol_flag := 'N';
p_wv_override_flag := 'N';
-- API Call for Ship Confirmation
DBMS_OUTPUT.put_line('Calling WSH_DELIVERIES_PUB to Perform Ship Confirmation');
DBMS_OUTPUT.put_line('=============================================');
wsh_deliveries_pub.delivery_action(p_api_version_number => 1.0,
p_init_msg_list => init_msg_list,
x_return_status => x_return_status,
x_msg_count => x_msg_count,
x_msg_data => x_msg_data,
p_action_code => p_action_code,
p_delivery_id => i.delivery_id,
p_delivery_name => p_delivery_name,
p_asg_trip_id => p_asg_trip_id,
p_asg_trip_name => p_asg_trip_name,
p_asg_pickup_stop_id => p_asg_pickup_stop_id,
p_asg_pickup_loc_id => p_asg_pickup_loc_id,
p_asg_pickup_stop_seq => p_asg_pickup_stop_seq,
p_asg_pickup_loc_code => p_asg_pickup_loc_code,
p_asg_pickup_arr_date => p_asg_pickup_arr_date,
p_asg_pickup_dep_date => p_asg_pickup_dep_date,
p_asg_dropoff_stop_id => p_asg_dropoff_stop_id,
p_asg_dropoff_loc_id => p_asg_dropoff_loc_id,
p_asg_dropoff_stop_seq => p_asg_dropoff_stop_seq,
p_asg_dropoff_loc_code => p_asg_dropoff_loc_code,
p_asg_dropoff_arr_date => p_asg_dropoff_arr_date,
p_asg_dropoff_dep_date => p_asg_dropoff_dep_date,
p_sc_action_flag => p_sc_action_flag,
p_sc_intransit_flag => p_sc_intransit_flag,
p_sc_close_trip_flag => p_sc_close_trip_flag,
p_sc_create_bol_flag => p_sc_create_bol_flag,
p_sc_stage_del_flag => p_sc_stage_del_flag,
p_sc_trip_ship_method => p_sc_trip_ship_method,
p_sc_actual_dep_date => p_sc_actual_dep_date,
p_sc_report_set_id => p_sc_report_set_id,
p_sc_report_set_name => p_sc_report_set_name,
p_sc_defer_interface_flag => p_sc_defer_interface_flag,
p_sc_send_945_flag => p_sc_send_945_flag,
p_sc_rule_id => p_sc_rule_id,
p_sc_rule_name => p_sc_rule_name,
p_wv_override_flag => p_wv_override_flag,
x_trip_id => x_trip_id,
x_trip_name => x_trip_name);
IF (x_return_status <> wsh_util_core.g_ret_sts_success) THEN
DBMS_OUTPUT.put_line('Ship confirm has not been Completed For SO => ');
ROLLBACK;
RAISE fail_api;
ELSE
DBMS_OUTPUT.put_line('Ship confirm Successfully Completed For SO => ');
COMMIT;
DBMS_OUTPUT.put_line('Checking the Delivery Status after delivery action API Call');
DBMS_OUTPUT.put_line('==========================================');
SELECT wdd.source_code,
wdd.released_status,
wdd.inv_interfaced_flag,
wdd.oe_interfaced_flag,
wts.pending_interface_flag
INTO v_source_code,
v_released_status,
v_inv_interfaced_flag,
v_oe_interfaced_flag,
v_pending_interface_flag
FROM wsh_trips wtr,
wsh_trip_stops wts,
wsh_delivery_legs wlg,
wsh_new_deliveries wnd,
wsh_delivery_assignments wda,
wsh_delivery_details wdd
WHERE wtr.trip_id = wts.trip_id
AND wts.stop_id = wlg.pick_up_stop_id
AND wts.pending_interface_flag = 'Y'
AND wdd.inv_interfaced_flag <> 'Y'
AND wlg.delivery_id = wnd.delivery_id
AND wnd.delivery_id = wda.delivery_id
AND wda.delivery_detail_id = wdd.delivery_detail_id
AND wnd.delivery_id = p_delivery_name
AND wdd.source_line_id = i.source_line_id;
IF (v_source_code = 'OE' AND v_released_status = 'C' AND
v_inv_interfaced_flag <> 'Y' AND v_oe_interfaced_flag <> 'Y' AND
v_pending_interface_flag = 'Y') THEN
DBMS_OUTPUT.put_line('The Delivery has been Shipped & the Next Step is - Run Interface');
DBMS_OUTPUT.put_line('===========================================');
-- API Call for Submitting Interface Trip Stop
wsh_ship_confirm_actions.interface_all_wrp(errbuf => v_errbuf,
retcode => v_retcode,
p_mode => 'ALL',
p_stop_id => NULL,
p_delivery_id => p_delivery_name,
p_log_level => 0,
p_batch_id => NULL,
p_trip_type => NULL,
p_organization_id => i.organization_id,
p_num_requests => 1,
p_stops_per_batch => 1);
ELSE
DBMS_OUTPUT.put_line('The Delivery has not Shipped Properly');
END IF;
END IF;
END LOOP;
EXCEPTION
WHEN fail_api THEN
DBMS_OUTPUT.put_line('==============');
DBMS_OUTPUT.put_line('Error Details If Any');
DBMS_OUTPUT.put_line('==============');
wsh_util_core.get_messages(p_init_msg_list => 'Y',
x_summary => x_msg_summary,
x_details => x_msg_details,
x_count => x_msg_count);
IF x_msg_count > 1 THEN
x_msg_data := x_msg_summary ||' '||x_msg_details;
DBMS_OUTPUT.put_line(x_msg_data);
ELSE
x_msg_data := x_msg_summary||' '|| x_msg_details;
DBMS_OUTPUT.put_line(x_msg_data);
END IF;
END;
But at the stage of updating delivery attributes I get the following error message
Warning: For Delivery Detail 21439836, the following field(s) are not updatable: SHIPPED_QUANTITY.
Why?

Hi Paul
Looks like the authorisation is failing due to a bad registration for some reason.
Would you be kind enough to clear out the registration to ensure we are dealing with a fresh start and no information is being used which may have become corrupt. You may do this by following this procedure;
Remove existing reg details
# usr/lib/cc-ccr/bin/eraseCCRRepository
List /tmp/RegistrationProfile.properties file
# cat /tmp/RegistrationProfile.properties
Attempt re-registration
# sconadm register -a -r /tmp/RegistrationProfile.properties
Send us the full output of the commands above if you would please.

Sales Order Items does not appear in MD04 after BAPI_SALESORDER_CHANGE

Hi Gurus,
I have this scenario.
1)Create sales order with 3 items.
2)Check in MD04. All items are there.
3)Assign reason for rejection for all the items.
4)Use BAPI_SALESORDER_CHANGE to remove the reason for rejection.
5)Only the first item can be shown in MD04.
Do you have any idea how can #5 happen?
Thanks and Best regards,
Andre

Thanks for the replies.
@ A.L.V Ramana,
Yes they all have confirmed qty. The one thing I noticed is that only the first item is being saved to table VBBE from which MD04 is getting sa sales documents. Is there any condition that must be met in order for this table to be filled except that if the item has reason for rejection or does not have confirmed qty?
@ Anirudh.vb
Thanks for the suggestion but the users wants a real time update on MD04.
Best regards,
Andre

IPod 4,1 will not update to iOS 7. I updated my iMac to 10.9.1 (maverick). Latest Numbers version on iMac is not compatible with Numbers on iPod. Ideas? Can I go back a version with Numbers?

iPod 4,1 will not update to iOS 7. I updated my iMac to 10.9.1 (maverick). Latest Numbers version on iMac is not compatible with Numbers on iPod. Ideas? Can I go back a version with Numbers? I downloaded old version of Numbers 2.0.1 from DVD but with both versions the 2.0.1 will not open. So both versions are present but only the new version functions. I tried to drag the new version to the trash but the old version still runs error message and will not open. I did not try to restart with the new version in the trash.

Maybe. See:
Reverting to previous version of Numbers

IPod will not update in iTunes with Windows Vista

Every time I connect my ipod to my computer, my computer locks up and it does not update. The only way I can even connect my ipod is to use manual update.

iTunes does not yet support Windows Vista. There are numerous problems running iTunes on it. The latest release of iTuens 7.1 fixed some of them but not all.

Previews in Adobe Bridge in Essentials View do not update after manipulation in Adobe Camera Raw

When I open a RAW file in Bridge and manipulate it in ACR, the preview is not updated in Bridge Essentials View. The only way I can get it to update the preview is to open the file in "Preview" view, then it updates and looks fine in Essentials view.

Is Bridge set up to store the ACR modifications to those XMP files? Only then it can update the preview right after working on it. Else you need to refresh the preview cache.

Can not update request in data target

Hi,
We have a process chain for master data (10 parallel) loads. One of the load
failed with error "can not update request REQU_46xxxxxxxxxxxxxx in data target".
When I checked the InfoPackage
(a) update: full load
(b) it has data selection
(c) processing :PSA and then to data targets
(d) Data targets: update in all data targets for which active rules exist.
But I do not see any list of data targets here.
Can some one please suggest me how do I correct this load failure.
Thanks

Hi Wondewossen, NS and Nagesh,
Thanks for the information. I am in support, and the developer is
not here now.
I have checked Header tab in the monitor, in this there
is a update symbol and infosource name and an -->
but after arrow there is nothing.
when I click on this I get a message
"No active update rules exist".
Can you please advice me how to I correct this.
Thanks

Exporting catalog, making changes, then importing catalog does not update file movements and deletions

I export part of my master catalog to a laptop. I include the image files so I can edit the files at full res. After managing and editing files I import the catalog back into the master catalog. When importing I check to replace metadata, develop settings and negative files. I have been running some tests to be sure all my work is being captured in the master catalog by this process. I find that if I change develop settings or photo ratings this is detected when the file is imported and the data in the master catalog is updated properly. The surprise is that if I delete files or move files among folders in the exported catalog these changes are not detected and these changes are not updated inthe master catalog. It seems bizarre to me that such changes are not detected but I do not see how to get LR to recognize these changes and include them in the catalog update. Without this capability I don't see how to use catalogs to move part of a catalog to another computer for edits and file management and then move back to the master catalog.

There are various reasons why Lightroom works this way, but you'll need use pick flags to indicate photos to be deleted, and other metadata like colours or collections.

ASN not updating in MD04

Similar Messages

Maybe you are looking for