Entries by Oracle ERP Apps Guide

, , , , , , , , , ,

Performing Back Order on a SO Line using Wsh_Delivery_Pub API

DECLARE x_return_status VARCHAR2 (3000);x_msg_count NUMBER;x_msg_data VARCHAR2 (3000);–Standard Parameters.p_api_version_number NUMBER;init_msg_list VARCHAR2 (30);x_msg_details VARCHAR2 (3000);x_msg_summary VARCHAR2 (3000);p_validation_level NUMBER;p_commit VARCHAR2 (30);–Parameters for WSH_DELIVERIES_PUBp_action_code VARCHAR2 (15);p_delivery_id NUMBER;p_delivery_name VARCHAR2 (30);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_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_asg_pickup_stop_seq […]

, , , , , , , , ,

Creating Move Order Using INV_MOVE_ORDER_PUB

Move Order: Move orders are requests for the movement of material within a single organization. They allow planners and facility managers to request the movement of material within a warehouse or facility for purposes like replenishment, material storage relocations, and quality handling. We can generate move orders either manually or automatically depending on the source […]

, , , , , , , , ,

Allocating Move Order INV_REPLENISH_DETAIL_PUB

DECLARE l_api_version NUMBER := 1.0;l_init_msg_list VARCHAR2 (2) := fnd_api.g_true;l_return_values VARCHAR2 (2) := fnd_api.g_false;l_commit VARCHAR2 (2) := fnd_api.g_false;x_return_status VARCHAR2 (2);x_msg_count NUMBER := 0;x_msg_data VARCHAR2 (255);l_user_id NUMBER ;l_resp_id NUMBER ;l_appl_id NUMBER ;l_row_cnt NUMBER := 1;l_trohdr_rec inv_move_order_pub.trohdr_rec_type;l_trohdr_val_rec inv_move_order_pub.trohdr_val_rec_type;x_trohdr_rec inv_move_order_pub.trohdr_rec_type;x_trohdr_val_rec inv_move_order_pub.trohdr_val_rec_type;l_validation_flag VARCHAR2 (2) := inv_move_order_pub.g_validation_yes;l_trolin_tbl inv_move_order_pub.trolin_tbl_type;l_trolin_val_tbl inv_move_order_pub.trolin_val_tbl_type;x_trolin_tbl inv_move_order_pub.trolin_tbl_type;x_trolin_val_tbl inv_move_order_pub.trolin_val_tbl_type;x_number_of_rows NUMBER ;x_transfer_to_location NUMBER ;x_expiration_date DATE;x_transaction_temp_id NUMBER ; CURSOR c_mo_details IS […]

, , , , , , , , ,

Transact Move Order Using INV_PICK_WAVE_PICK_CONFIRM_PUB

DECLAREl_api_version NUMBER := 1.0;l_init_msg_list VARCHAR2 (2) := fnd_api.g_true;l_commit VARCHAR2 (2) := fnd_api.g_false;x_return_status VARCHAR2 (2);x_msg_count NUMBER := 0;x_msg_data VARCHAR2 (255);l_move_order_type NUMBER := 1;l_transaction_mode NUMBER := 1;l_trolin_tbl inv_move_order_pub.trolin_tbl_type;l_mold_tbl inv_mo_line_detail_util.g_mmtt_tbl_type;x_mmtt_tbl inv_mo_line_detail_util.g_mmtt_tbl_type;x_trolin_tbl inv_move_order_pub.trolin_tbl_type;l_transaction_date DATE := SYSDATE;l_user_id NUMBER;l_resp_id NUMBER;l_appl_id NUMBER;CURSOR c_mo_details ISSELECT mtrh.header_id, mtrh.request_number, mtrh.move_order_type,mtrh.organization_id, mtrl.line_id, mtrl.line_number,mtrl.inventory_item_id, mtrl.lot_number, mtrl.quantity,revision, mtrl.from_locator_id,(SELECT DISTINCT operating_unitFROM org_organization_definitionsWHERE organization_id = mtrh.organization_id) org_idFROM mtl_txn_request_headers mtrh, mtl_txn_request_lines […]

, , , , ,

Removing Enddate from Responsibilities given to Users

Sometimes while working on a support projects, we used to have access to the read only responsibilities ,or though we have given the access to the super users initially, but those accesses might have revoked after system went live. But in test environment, we may require those accesses back so as to fix the bugs […]