Drop Ship Order Issue

Hello Gurus,
After booked the Dropship order, initially i got the error as workflow stuck in Purchase Release Deferred. After running the workflow background process, i am able to perform the progress order funtions.
In the progres order function when i choose the Purchase Release Eligble a pop window appear with the below error message.
'The person who entered the order, &USER, is not a valid employee'
Please help me to resolve the issue

Hi Sandeep,
I have added the person who created the user as an employee in the HR module. And also i have added the user who created the order as an employee. But still i am getting the error.
Could you please help me to resovle the issue.
Thanks in advance

Similar Messages

VF06 not working for drop ship orders

Hi All,
We use VF06 for creating billing docs. Interesting it works good for all order/delivery types but does not create any billing document for third party sales orders. I have flagged both - order related and delivery realted document indicators and leaving all the selection inputs blank except for the sales org. When we try to create the invoice for a drop ship order, it gets created but surprisingly does not get picked up in VF04 or VF06.
Any help would be appreciated.
Thanks & Regards,
Vidya

Hi,
I did go through some notes and could find out the problem. In copy controls we have set the billing quantity to F to enable billing even if GR is done for the PO and need nt have the Vendor Invoice Recipet to be done. SAP says in some notes that if this is set, then the billing due list will not have the order displayed even if it can be manually invoices. But I dont have any idea how to overcome this. SAP has provided standard reports but somehow these reports are not working for me.
Thanks & Regards,
Vidya

Changes to Drop Ship Orders with configurations/star items

Hi,
Can someone in this group clarify a few things with respect to changes to drop ship orders that has configured/star items. The CTO guide says that we cannot do configuration changes on the sales order, if the related PO is 'Approved'. There is a processing constraint that prevents it.
-->So can we cancel PO and the Purchase Requisition, then de-link the configured/star item on the sales order and then do configuration changes?
-->Assuming that the PO is NOT 'Approved', then we can do configuration changes on the sales order, so what happens to the PO. Does the PO get cancelled or the old configured/star item's PO line gets cancelled? The guide says it depends on the status of the PO. Its a bit ambiguous.
Can someone who has tested this function in R11i or R12 share their experience?
Thanks,
Nitin

The PO changes are not reflected automatically on the SO.
However, you can run the "Sales Order and Purchase Order Discrepancy Report" in Order Management. This report will at least give you the drop ship orders that don't match.
Hope this answers your question
Sandeep Gandhi
Omkar Technologies Inc.
Independent Techno-functional Consultant

Drop ship & Non Drop Ship order differentitation

Folks
1. How do I differentitate a Drop ship & Non Drop Ship order by looking at the SO Items ?
2. Which parameters drive whether a SO item is a drop ship or Non Drop ship item
3. Can a SO have both drop ship and non drop ship items ?
Thanks

Hi Dear,
Following is the SQL for Drop Ship I have. I think it will be useful to you and make necessary changes as per your requirements.
begin
fnd_client_info.set_org_context('p_org_id');
end;
select ooh.ordered_date, ott.NAME order_type, ooh.order_number, ooh.TRANSACTIONAL_CURR_CODE so_curr_code, --ooh.order_type_id,
arc.customer_name, ooh.cust_po_number, --ool.inventory_item_id,
ool.line_number so_line_number, ool.ordered_item, msi.DESCRIPTION item_description,
ool.ordered_quantity, ool.unit_selling_price, --ods.PO_HEADER_ID,
(ool.ordered_quantity* ool.unit_selling_price) ordered_value,
          poh.segment1 po_number, poh.CURRENCY_CODE po_curr_code, poh.CREATION_DATE po_date,
          pov.VENDOR_NAME, pol.LINE_NUM po_line_num, pol.QUANTITY po_quantity, pol.UNIT_PRICE po_unit_price,
(pol.QUANTITY * pol.UNIT_PRICE ) po_value, pol.closed_code po_line_status, pll.QUANTITY_BILLED
from oe_order_headers_all ooh, oe_order_lines_all ool, oe_transaction_types ott, mtl_system_items msi, ar_customers arc, OE_DROP_SHIP_SOURCES ods,
po_headers_all poh, po_lines_all pol, po_line_locations_all pll, po_vendors pov
where-- ooh.ordered_date >= '01-JAN-11'
ooh.org_id = :p_org_id
and ool.header_id = ooh.header_id
and ool.flow_status_code = 'AWAITING_RECEIPT'
and ool.source_type_code = 'EXTERNAL'
and ott.TRANSACTION_TYPE_CODE = 'ORDER'
and ott.TRANSACTION_TYPE_ID = ooh.ORDER_TYPE_ID
and msi.INVENTORY_ITEM_ID = ool.inventory_item_id
and msi.ORGANIZATION_ID = ool.SHIP_FROM_ORG_ID
and arc.customer_id = ooh.sold_to_org_id
and ods.LINE_ID = ool.LINE_ID
and ods.PO_HEADER_ID IS NOT NULL
and poh.PO_HEADER_ID = ods.PO_HEADER_ID
and pol.PO_HEADER_ID = poh.PO_HEADER_ID
and pol.PO_LINE_ID = ods.PO_LINE_ID
and pll.PO_HEADER_ID = pol.PO_HEADER_ID
and pll.PO_LINE_ID = pol.PO_LINE_ID
and pov.VENDOR_ID = poh.VENDOR_ID
order by ooh.ORDERED_DATE, ooh.ORDER_NUMBER, ool.LINE_NUMBER
HTH
Sanjay

Drop ship order logic to select supplier

Hi,
I was trying to figure out how supplier is selected for an item if item is not an ASL item or if there are multiple suppliers with same rank for asl item.
Thanks

Supplier and Price will default automatically in the Drop Ship Requisition/PO if you try this:
(1) Create a Sourcing Rule indicating sourcing for the "Buy" item from the given supplier at rank 1 (make sure allocation =100%). Create sourcing Rule Assignment as well.
(2) Define ASL for the "Buy" Item
(3) Make sure Item is Checked for Approved Supplier List
(4) Create a Blanket PO or QUotation and include the item along with its price

ESYU: FAQ - Drop Ship Purchase Orders 2

Purpose
RECEIVING: Drop Ship PO's - Release 10.7, 11.0, 11.5.X, r12
Information in this document applies to any platform.
Q/A를 통해 Drop Ship Purchase Orders에 대한 이해도를 높인다.
Solution
Q8. Configurable Items은 Drop Shipped 가능한가?
A8: 현재는 Standard Items 만을 Drop Shipped 할 수 있다.
Configurable Items를 위한 functionality는 향후 release에 포함될 것이다.
Q9. Operating Units를 교차하여 Drop Ship을 할 수 있는가?
A9: Release 11i는 현재 이 functionality는 지원하지 않는다.
Q10. Drop Shipment에서 over/under shipment는 어떻게 처리하는가?
A10: 만일 drop-ship line의 일부만 ship 되고 나머지 수량에 대해 fulfill을 원하지 않는다면 line을 cancel 한다.
Over shipments 또한 manual 하게 처리해야 한다.
만일 supplier가 ordered quantity 보다 많은 수량을 ship 하였다면, customer에게 추가된 수량만큼
bill을 할 수 있거나 customer에게 추가 수량을 return 해 달라고 요청 할 수 있다.
Drop-ship Sales Orders와 이에 연계된 purchase requisition/orders 간의 차이를 보고 싶으면
Drop Ship Order Discrepancy report를 이용한다.
Q11. Drop Shipment와 Blanket PO's를 사용할 수 있는가?
A11: Blanket PO는 Drop Shipment와 같이 사용할 수 없다. 왜냐하면 PO는 OM이 PO에게 Drop Ship order가
생성되었음을 공지시 생성되어야 하기 때문이다.
Rececipt이 될때(partial or complete) 이 PO는 Drop Ship order와 link 된다.
Drop Ship lines은 pick release, ship confirm 혹은 INV interface order cycles을 이용하지 않는다.
Q12. Valid Blanket PO를 생성시 blanket agreement에 있는 item을 위해 drop shipment orders를 base로 하는
release를 생성하는 것이 가능한가?
A12: Yes, drop ship orders로부터 자동 혹은 autocreate window를 통하여 release를 생성하는 것은 가능하다.
만일 drop ship requisition이 correct blanket information(source)을 가지고 있다면
1. 요구되는 supplier site에 대한 ASL entry를 setup
2. Hierachy에 따라 어떤 assigment가 좀 더 알맞은지 결정하고, 요구되는 supplier/site를 가지고 요구되는
level에 따라 sourcing rule을 정의한다.
또한 위 supplier/site에 대한 ASL entry가 존재하는지 확인한다.
Profile option 'PO:Allow Automatic Sourcing' = Yes인 경우 automatic sourcing이 실행되며, creation date와
document type에 따하 source document가 자동으로 결정될 것이다.
Q13. Receive 후 Drop Shipment를 cancel 할 수 있는가?
A13: Oracle Purchasing에 한 번 receipt 한 후에는 Drop Shipment는 cancel 할 수 없다.
만일 Drop Ship Sales Order line을 cancel 하길 원한다면 cancel을 원하는 line에 대해 receipts은 없는지와
연계된 requisiton이나 purchase order가 cancel 되어 있는지 확인을 해야 한다.
Partial Deop Ship receipt에 대한 cancellation은 가능하나 아직 receive 되지 않은 부분에 대해서만 cancel
할 수 있다.
만일 모든 수량을 shipped 하지 않은 drop shipment line을 cancel 한다면 order processing은 line을 split 한다.
첫번째 line은 shipped 한 수량을 포함하고 두 번째 line은 non-shipped 수량을 backorder로 가지며,
이 두 번째 line(backorder)을 cancel 할 수 있다.
PO line 수량은 새로운 수량을 반영하기 위해 변경되어져야 한다.
Q14. Drop Shipment를 위한 debugging tools은 무엇인가?
A14: 1. Note 133464.1 - Sales Order의 troubleshooting problems을 위해 사용할 있는 diagnostic script를 포함.
2. Receipt transaction이나 Sales Order issue transaction debugging을 위해 아래 profile options을 set:
RCV: Processing Mode to Immediate or Batch
RCV: Debug Mode to Yes
OM: Debug Level to 5
INV: Debug Trace to Yes
INV: Debug level to 10
TP: INV Transaction processing mode to Background
- Sys Admin: Concurrent> Program> Define> query up the Receiving Transaction Processor and check the Enable Trace box
- Deliver Transaction을 위한 receipt을 저장 (Deliver Tranasction을 위한 destination type은 inventory 이어야 함)
- Receiving Transaction Processor log file, Inventory Transaction Worker log file, trace등을 review
Q15. Drop Shipment로 부터 생성된 PO의 status와 Import source는 무엇인가?
A15: PO status는 언제나 approved.
Import source: Order Entry
Q16. 관련된 Sales Order Line이 cancelled/closed 된 PO shipment를 receive 할 수 있는가?
A16: 관련된 Sales Order Line이 cancel 되었거나 closed 되었다면 PO shipment는 receive 할 수 없다.
이 PO shipment는 cancel 해야 하며, 필요하다면 새로운 Sales Order Line이 생성되어야 한다.
Reference
Note 225434.1

Hi Suda,
Yes, the purchase orders are created directly from the sales order, so there should be some sort of link between the two I would think. However, I may be wrong in this line of thinking.
The UDF would be on the header as our customer puts an entire sales order on only one purchase order.
Thank you for your quick response.
Amanda

Drop ship purchase order creation using Pl/Sql code..

Hi,
We are creating the purchase order for drop ship orders.
1. Created order with line source as external and then we ran the workflow backround processor which created a requisition for the order, using this requisition we are trying to create a purchase order with autocreate functionality by using PO_INTERFACE_S. Is this the way to create a drop ship po from backend.
Can you please suggest any other way.
Thanks in Advance.
jagdish.

Hi,
You can customize the workflow such that it creates PO automatically, by selecting the attributes "Is PO Auto Creation Allowed?" to create PO after the requisition is created.
Requisition Import will call PO Create Documents w/f to create PO.
Plz get back to me if any clarification is needed.

COPA - Third Party Drop Ship Returns - Vendor Discounts

Hello -
This is challenging so I hope some of you can help me please!
Can anyone explain to me how vendor discounts work in copa as they relate to third party drop ship returns? We use net vendor invoices where discount is taken at time of vendor posting and offset by clearing account.
We have several scenarios where we cannot reconcile FI and COPA for COGS account because of the discount on the vendor credit memo.
An example:
We have created the sales order and purchase order for the process. Then we do a migo and a miro from the vendor.
The vendor document has a discount of 1%, so if it costs $100, here is the accounting:
MIGO -
dr. cogs 100
cr. gr/ir 100
miro
dr. vendor discount clearing 1
cr. cogs 1
dr. gr/ir 100
cr vendor 100
then we bill the customer.
Copa at this point gets hit with 99 debit to cogs value field (100 -1 =99)
then we process the customer credit memo request.
Then we process the vendor miro credit.
dr. cogs 1
cr. vendor discount clearing 1
dr. vendor 100
cr. gr/ir 100
At the time the vendor credit memo is posted, sap inserts a new copa line-item on the customer billing document with $1.00 debit to copa.
then we reverse migo
dr. gr/ir 100
cr cogs 100
And then we bill the customer credit memo, which creates another copa document that credits copa with $99.00. why doesn't this create a copa document of -$100. this would help tie out copa and fi.
If you go through and look at all cogs postings on FI side, the credits and debits = 0
If you go through and look at the cogs posting in COPA, the credits and debits = 1
therefore, fi and co don't tie.
please give me any ideas that might help me.

Hi Valerio,
Have you found any solution for your issue?
We have a similar problem with 3rd party drop ship orders and COPA. Cost of Goods Sold Drop Ship is being charged when we use MR11 to clear GR/IR account. This is causing reconciliation issues between COPA and the General Ledger.
Let me know if you have come across any clues?
Thanks.
Ram

Drop Ship SO Schedule Ship Date to Purchasing NeedBy Date

Has anyone found a solution to resolve the fact that the Sch Ship Date defined on a sales order becomes the Need By Date on a Purchase Release document sent to a Supplier to fulfill a Drop Ship Order Line? This is confusing to the Supplier as the term NeedBy implies this is when the customer will need the product on site. If the supplier has the product there by the Need By Date transmitted from OM, then the product will arrive too early.
Thoughts?...

Let's assume the Customer Service person does not know whether the item is a drop ship item or not. The problem we have is that the Customer Service person normally uses the Scheduled Ship Date as the date Shipping must send out the product on product sourced internally. We are trying to keep things consistent for the end user.
We hope to use the Scheduled Ship Date as the date the product must be shipped regardless of whether the product is sourced internally or externally. Again, this is to keep order entry consistent for the end user and they do not have to think differently when entering the sales order.
Thanks for any feedback.

Drop ship return

How to return a drop shipment ?
What OM transaction type setup is required ?

Dear David,
There is quiet lot of info. available on metalink.
Following are some Notes you can find on metalink.
1) Note:225434.1
2) Note:99886.1
3) Article "DROP SHIP ORDERS, CHANGE MANAGEMENT"
It will surely help you.
Regards

Drop Ship workflow Process Name

Hello,
Does anyone know the seeded Process Name that could be used for drop ship orders. According to the documentation I've read about drop ship, they explained to use the Generic Order Flow which I did. The problem is with the line level process name. I've tried Line Flow Generic and several other process names but my orders get stuck at the booking level. Other types work just fine. I've also changed the source type to external but nothing works!
I'm using Vision 11.5.7
My setup is as follows:
Item = transactable, stockable, customer ordered, customer orders enabled, shippable, oe transactable
transaction type: Drop ship, order category= order, order workflow = order flow- generic, Assign line flows-->Process name= Line flow- generic
Line type --> source type= external
Set up defaulting rules as well
Orders get stuck at booking! Should be awaiting receipt
Your help will be appreciated
Cheers
Riad

Hi Sandeep,
Are you sure whether the Workflow Background Process has picked the order line and workflow activity is not errored out? Please check the workflow, has it completed Purchase Release activity or is it still in the Purchase Release - Deferred state?
If the workflow is in the Purchase Release - Deferred state, then the line will be in the Booked status. So, run the WBP program (item key - OM Order Line, Process Stuck - Y, Process Timeout - N) & see the line workflow activity & the line status should be progressed to Awaiting Reciept.
Also, make sure you have provided the List Price (greater than zero) & Default Buyer in the Purchasing tab at the Item master level for the dropship item. If these information are not provided then the Requisition will not be created.
Regards,
Hemanth

How to migrate Drop Ship PO and SO from 11.0.3 instance to R12?

Hi Everyone,
We are in process of migrating Drop Ship Orders from 11.0.3 system to R12 system?
Can anyone help me in identifying how to migrate Drop Ship Orders?
Is it possible to migrate Drop Ship PO and SO Separately and then link them through Drop ship sources table? How the reservation will work for this type of orders?
Any guidelines will be really helpful.

Hi,
What I am currently planning to do is as follows:
1) Migrate the Drop Ship SO
2) Run the workflow background process which will progress the line (From Booked -> Awaiting Receipt) and insert the record in to Requisitions Interface and OE_DROP_SHIP_SOURCES Table
3) Migrate the PO separately
4) Update the record created through second step in Drop Ship Sources table with PO Header ID, Line ID and Line Location ID
5) Receive against the PO
6) OM Line is getting shipped at this stage once the receiving is done
7) Delete the lines in Requisition interface table
In this, the only custom thing we are doing is updating the DROP SHIP SOURCES Table with PO IDs.
I am not able to think any other way to migrate Drop Ship SO.
Please suggest, if anyone is foreseeing any problem in this approach or having any other approach.

Vendor Drop Ship Sales Order statues Issues

Process flow : OR ( item category ZVDS u2018Vendor Drop Ship" ) >> PO >> MIGO >> Invoice ( its order related billing ) no delivery involved in this because of drop ship
after sales order OR system generate PR and PO and if customer reject the PO so user put line item as mark for deletion in PO we cant delete PO and its tie up with Sales order and Over all statues at header lever is OPEN u2026is there any way where we can change over overall statues in sales order
We have an significant amount of these orders that continue to appear in numerous reports when they should not be of selected criteria,
But the main issue being when these orders are cancelled, returned, etc. They are not removed from VF04 "Billing Due list".

Pls reply me

Purchase Order for Drop ship sales order

We are on version SAP ECC6
We are having issues with the delivery address of a drop ship sales order getting copied correctly into the Purchase Order/purchase requisition.
The sales order is an sd and as the sales order is created on the partner section as they attach the ship to partner, they may add a phone number or a minor "tweek" to the customer ship to. When this gets converted to the po, the customer number (CMMDA-KUNNR) is not the ship to address it is reading but (CMMDA-ADRN2).
When the PO prints, the ship to address section is missing, it is blank and it seems to be the difference in the two fields.
I am interested to see how to resolve this issue as well as to understand the cause for populating the po as it does.
I appreciate your assistance on this.
Thankyou
Wanda Thivierge

The PO automatically gets the ship-to's address as delivery address.
with central address managment active (since 46c) SAP stores the addres in ADRC table, the address in customer master (KNA1) itself is just short duplicate. However, KNA1 table has the field ADRNR which is the link to the ADRC table.
Problems in print forms are usually caused by the programmers who changed the form to make it company specific. They often change the logic of standard SAP given forms and programs.
So I recommend to check with the programmer to print the correct ship-to adress.

Drop Ship SO, Change Management Issue in 11.5.9

Hi,
Currently Client is using Oracle Apps Release 11.5.9
Requirement :
While updating Drop Ship Sales Order, corresponding requisition and Drop Ship Purchase order needs to be updated automatically
Problem:
This functionality is available in 11.5.10 which automatically updates requisition and PO but not in 11.5.9
I couldn't find the package API which they had used in 11.5.10 for implementing this solution.
Hence Please help me in providing the package(API) which is used in 11.5.10 for auto update of requisition and drop ship PO when drop ship SO is changed. So that i can try to implement the same logic in 11.5.9 for client.
Thanks,
Selvan

marist89 wrote:
In anticipation of an impending maelstrom of regulatory changes, I want to upgrade my 11.5.9 EBS environment to 11.5.10 and at least have a hope of being supported. Upgrading to R12 is just not an option at this point, my users are overwhelmed by it. I know that's the best way to go, but it's not going to happen.
I have an 11.5.9 environment on Solaris running on two tiers. The middle-tier serves Web & Forms. The DB Tier serves DB (10.2), CCM, and Reports.
At the same time I upgrade, I want to move my EBS to Linux. I also want to change my configuration so that I am running Web/Forms/CCM/Reports all on the same tier and isolate the DB to it's own node.
My general thought process was:
1. Move the db from Solaris (10.2) to Linux (11.2) using a combination of (362205.1) and (557738.1).
2. Install 11.5.10 on a new node (Linux) and just run the appropriate driver for the 11.5.10 patch against the db on Linux.
Does this seem like a reasonable approach?No, as it is not supported -- You may log a SR to confirm with Oracle Support.
You need to upgrade 11.5.9 to 11.5.10 (or 11.5.10.2) then migrate the database using export/import and the application tier node. Or, migrate the database then upgrade to 11.5.10/11.5.10.2 then migrate the application tier node.
Oracle Applications Release 11.5.10.2 Maintenance Pack Installation Instructions [ID 316365.1]
Upgrade Path Recommendations for E-Business Suite 11i [ID 364623.1]
Release 11.5.10 Maintenance Pack Installation Instructions [ID 259484.1]
Migrating to Linux with Oracle Applications Release 11i [ID 238276.1]
Debugging Platform Migration Issues in Oracle Applications 11i [ID 567703.1]
Oracle Applications Release Notes, Release 11i (11.5.10.2) [ID 316803.1]
Recommendations To Install Oracle Applications 11i [ID 294932.1]
Thanks,
Hussein

Drop Ship Order Issue

Similar Messages

Maybe you are looking for