Label Printing WMS

Note: 242789.1 - Oracle Warehouse Management Label Customization 
Note: 298250.1 - Troubleshooting WMS / MSCA Label Printing
Note: 875122.1 - Certified Integration Partners With Oracle WMS/MSCA For Label Printing

Label Printing Strategies for Oracle Warehouse Management System (WMS) (Doc ID 414368.1)

11i - Inventory Label Printing Documentation (Doc ID 277357.1)

MMT Columns

For Sales Order Pick

TRX_SOURCE_LINE_ID : Sales order line id

SOURCE_LINE_ID : Move order line id

PO receipt

TRX_SOURCE_LINE_ID : NULL

SOURCE_LINE_ID :  rcv transaction id

Sales order imp columns

------------------------------------------------------------

OE ORDER HEADERS ALL 

------------------------------------------------------------

order_category_code  

Identify if it's a return

ORDER
RETURN


order_source_id

Identify if its a Normal Sales order or Internal

SELECT *
FROM   OE_ORDER_SOURCES
WHERE  order_source_id

SELECT org_id, order_source_id
FROM   po_system_parameters_all

sales_channel_code

lookup_type = 'SALES_CHANNEL' 

freight_terms_code

lookup_type = 'FREIGHT_TERMS' 

fob_point_code

lookup_type = 'FOB'

payment_term_id

ra_terms

shipping_method_code

wsh_carrier_services

price_list_id

qp_list_headers

------------------------------------------------------------

OE ORDER LINES ALL 

------------------------------------------------------------

item_type_code

lookup_type = 'ITEM_TYPE'

source_type_code 

INTERNAL   : non-dropship orders  
EXTERNAL  : Dropship

---------------------------------------------------------------------

PROGRAMS

---------------------------------------------------------------------

DEMAND INTERFACE PROGRAMS - 

Creates Demand in mtl_demand table.

After Order is booked

SCHEDULE ORDER PROGRAM - 

Creates soft reservation for the sales order

SELECT ooh.order_number
              ,ool.line_id
              ,ool.ordered_quantity
              ,ool.shipped_quantity
              ,ool.invoiced_quantity
              ,wdd.delivery_detail_id
              ,wnd.delivery_id
              ,rctl.interface_line_attribute1
              ,rctl.interface_line_attribute3
              ,rctl.interface_line_attribute6
              ,rct.org_id
              ,rct.creation_date
              ,trx_number
              ,rctl.quantity_ordered
              ,rct.interface_header_context
  FROM oe_order_headers_all ooh
             ,oe_order_lines_all ool
             ,wsh_delivery_details wdd
             ,wsh_new_deliveries wnd
             ,wsh_delivery_assignments wda
             ,ra_customer_trx_all rct
             ,ra_customer_trx_lines_all rctl
 WHERE ooh.header_Id=ool.header_id
      AND wdd.source_header_id=ooh.header_id
      AND wdd.delivery_detail_Id=wda.delivery_detail_id
      AND wda.delivery_id=wnd.delivery_id
      AND rctl.interface_line_attribute1=to_char(ooh.order_number)
      AND rctl.interface_line_attribute6=to_char(ool.line_id)
      AND rctl.interface_line_attribute3=to_char(wnd.delivery_id)
      AND rctl.customer_trx_id=rct.customer_trx_id
      AND rct.interface_header_context='ORDER ENTRY'

SQLERRM : ORA-06508 PL/SQL: Could Not Find Program Unit Being Called

SOURCE

When you search this error on the net, you will find out these :

Cause:	An attempt was made to call a stored program that could not be found. The program may have been dropped or incompatibly modified, or have compiled with errors.
Action:	Check that all referenced programs, including their package bodies, exist and are compatible.

Yes, that’s true. But if you have lots of objects depends to a lot of object  You will need to more information to fix this error. If you face up with this error, you probably use SQLCODE and SQLERRM in your exception block of your PL/SQL code. Something  like this:

BEGIN
 NULL;
EXCEPTION
 WHEN OTHERS THEN
 ROLLBACK;
 INSERT_LOG(SQLCODE, SQLERRM);
END;

I do not advise to handle errors in this way. Because this error description does not give you enough information abour your error as ORA-06508 error. You don’t really know what triggered this exception. Operation of this code on a production database is also not easy. At this point, Oracle’s DBMS_UTILITY package will be included in out lives. 

If you write something like this:

BEGIN
 NULL;
EXCEPTION
 WHEN OTHERS THEN
 ROLLBACK;
 INSERT_LOG(SQLCODE,
 DBMS_UTILITY.FORMAT_ERROR_STACK || '@' ||
 DBMS_UTILITY.FORMAT_CALL_STACK);
END;

You will not get ORA-06508 error for the same error. You will get something like this explanation:

ORA-04045: errors during recompilation/revalidation of SIM.PKXXX
ORA-04052: error occurred when looking up remote object TCLCM.PRC_XX@ERP_APPS.WORLD
@----- PL/SQL Call Stack -----
 object      line  object
 handle    number  name
3dc3a9010      1565  package body SIM.PK_XXX
3d9571de8         3  anonymous block