Pack Slip Generating Issues

During Ship confirmation, below error is coming and Pack Slip is not generating

Error

Error: There is an error generating/validating the sequence number. Please check the assignments are defined and are valid.

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

Warning: Pack Slip information could not be automatically created for delivery 115506201.

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

Error: There is an error generating/validating the sequence number. Please check the assignments are defined and are valid.

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

Warning: Bill of Lading information could not be automatically created for Delivery 115506201.

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

Submitted 1 out of 1 documents for this document set. (REQ_IDS=293613)

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

Warning: Failed to submit document set for delivery 115506201

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

Interface Trip Stop request 293614 has been submitted

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

Warning: 1 deliveries will be marked as In-Transit/Closed.

Issue:

This order will be able to ship confirm, if re-queried but Pack Slip will not be generated.

Solution:

As in this case, this is not able to properly generate the sequence number, it cannot insert record into WSH_DOCUMENT_INSTANCES table

In most business, Delivery Name been used as the pack slip number.

So for every pack slip document, data being inserted into the table with entity_id as the delivery name.

So as in this case, it is not able to generate the sequence number, this will not be inserted in the table and pack slip canot be generated.

So for this issue, the solution is to do the below profile option setup in following level

Profile Option: Sequential Numbering

Value: Always Used

Level: Application

Application Level values: Shipping Execution and Order Management

If you don’t want to use the same value across all sites, then you can do the setup at specific responsibility levels too.

Read More

Label Printing in MSCA/WMS

Labels

Either we can use the existing labels or we can design new labels

Label Types:

There are different label types depending on the different business and requirement with data elements.

Label Format:

A single design of a label that may include fixed data (such as field prompts) and variable data (such as Part Number). A Label Format is associated to a Label Type. It includes a subset of the available data elements from a particular Label Type. A label type can have multiple label formats, however each Label Format belongs to only one label type. Label Formats are registered within Oracle Warehouse Management after you create the label design in the third party software package.

Either you can use the seeded label format or you can design your own label format

We can customize the label as per our requirement with required and customized fields

Printing Modes

Asynchronous:

An integration mode between Oracle Warehouse Management and the third party software supplier that is handled through dropping an XML file into a watched directory. When using this mode, Oracle Warehouse Management has no knowledge of the status of the print request after creation of the XML file.

Synchronous:

Generic:

A real-time integration mode between Oracle Warehouse Management and the third party software vendor that is handled through a PL/SQL API. When using this mode, the third party supplier is able to return success or failure messages regarding the status of the label print request. Oracle Warehouse Management stores those messages in the label print history so label printing problems can be easily identified and diagnosed.

TCP/IP:

A real-time integration mode between Oracle Warehouse Management and the 3rd Party software vendor that is handled through a standard Ethernet TCP/IP connection. When using this mode, Oracle ensures that the printer or print server is listening to the IP and port and has successfully received the message, but no knowledge of the detailed status of the print request beyond acceptance of the XML message is known by Oracle Warehouse Management.

Example Printer vendors like Zebra, Intermec, Cognitive Solutions, Datamax, Toshiba TEC, Printronix and Sato

Printer

·        Define the printer details in Oracle system (Sysadmin) with proper styles and drivers and with unique name

·         Assign IP and Port to printers

Assigning Label Types to Business Flow

Business Flow: An identifiable business process that occurs as part of material handling within Oracle Warehouse Management. Oracle Warehouse Management recognizes a pre-determined list of Business Flows you can set up to include label printing as part of the transaction processing.

Defining Label Format Rules

Creating label format rules is an optional step. Some implementations may require only a single label format for each label type. If this is the case, the system picks the default label format for each type. The system also picks the default if there are no applicable rules. If the implementation requires more than one label format for a label type label format rules are necessary.

Assigning Printer to the Required Level

Printers can be assigned to Site level, responsibility level, user level.

Read More

Below are the basic tables used during Drop Ship flow

apps.oe_order_headers_all 

apps.oe_order_lines_all

apps.oe_drop_ship_sources

apps.po_requisitions_interface_all

apps.po_interface_errors

apps.po_requisition_headers_all

apps.po_headers_all

apps.po_lines_all

apps.po_line_locations_all

apps.po_distibutions_all

apps.po_releases_all

Below is the SQL Statement to find out the Drop Ship SO and corresponding Requistiona and PO details along with their status

select ooh.order_number

       ,ool.ordered_item

       ,ool.ordered_quantity

       ,ooh.flow_status_code header_status                   

       ,ool.flow_status_code line_status

       ,prha.segment1 requisition

       ,poh.segment1 po_number

       ,poh.closed_code po_status

       ,pll.quantity

       ,pll.quantity_received

       ,pll.closed_code po_shipment_status

from apps.oe_order_headers_all                   ooh

    ,apps.oe_order_lines_all                     ool

    ,apps.oe_drop_ship_sources                   odss

    ,apps.po_requisition_headers_all             prha

    ,apps.po_headers_all                         poh

    ,apps.po_lines_all                           pol

    ,apps.po_line_locations_all                  pll

              

where ool.header_id = ooh.header_id

and   odss.header_id = ooh.header_id

and   odss.line_id = ool.line_id

and   prha.requisition_header_id = odss.requisition_header_id

and   poh.po_header_id = odss.po_header_id

and   pol.po_line_id = odss.po_line_id

and   pol.po_header_id = poh.po_header_id

and   pll.po_line_id = pol.po_line_id

and   ooh.order_number = '66411';

Read More

Setting up the Item first

Master Level:

Inventory:

Inventory Item, Stockable, Transactable

Purchasing:

Purchased, Purchasable, List Price

Order Management:

Customer Ordered, Customer Order Enabled, Shippable, OE Transactable

Default SO Source Type should be External

Internal Ordered, Internal Order Enabled (These 2 if the drop ship will happen from internal organization)

Invoicing

Organization Level Setup:

Inventory

Costing

Receiving

Now create the Sales Order

Make sure source type is External

Now Book the order

Now the line is in Booked

Workflow is deferred for Purchase Release

Run the workflow Background

After the program completes, re query the SO

Now the time, you can see the record both in Drop Ship table and Po Req Interface table

select * from apps.oe_order_headers_all where order_number = '66411';

select * from apps.OE_DROP_SHIP_SOURCES where header_id = 190500;

select * from apps.po_requisitions_interface_all where creation_date >= sysdate-1/24;

Now run the Requisition Import Program

If this program not able to create the requisition, then please check the error if any in below table

select * from apps. PO_INTERFACE_ERRORS where transaction_id = <transaction_id from po_requisition_interface_all table>

Once the program, completes, lets check the Req details in Sales order line, additional Information , Drop Ship tab

PO Creation

Now take this Requisition and Auto Create PO from this using the Purchasing responsibility

Click Automatic

Select the supplier and Site and click Create

This will create the PO

Now check the details and Submit for Approval

Wait till you get the confirmation from supplier for the shipments either by ASN or any EDI communication.

Now you can see this PO details in SO Line, Drop Ship tab

PO Receiving

Once confirmed, then go ahead and do the receipt

Once received, check the transaction completion.

Once the receiving transaction completed, go and check the SO line status

Now run the workflow background program, this will close the line

This will interface the record to Receivable

Now run the Autoinvoice Master program to create the Receivable Invoice

Read More

1. Create an Item, should be Customer ordered, customer orderable, purchased, purchase order enabled
2. Give the buyer details
3. OM: Population of Buyer Code for Drop Ship should be Order Creator
4. Now add the buyer Employee to the user who will crete the PO
5. Create a sales order, line source type should be external(this can be setiup at item level too)
6. Once you book the order, workflow will be deferred.
7. Run the Workflow background, this will change the line status to Awaiting Receipt
8. Run the PO Requistion Import program from the PO responsibility with parameter Source as ORDER ENTRY and Initiate Approval after ReqImport as Yes.
9. Go to the sales order and in additoional information, drop ship tab, you can see the PO/PO req details
10.Go to Purchasing --> Autocreate, Goahead and create the PO Document and Approve the same.
11.Now go and receive the PO, this will automatically trigger the Sales order issue transaction for the drop ship SO

Read More