type subtype

945 EDI Code

945 EDI Code

945 EDI Code

945 EDI Code

945 EDi Code

945 EDI Code

945 EDI Code

945 EDI Code

944 EDI Code

944 EDI Code

944 EDI Code

 945 business pr

945 business pr

945 business pr
940
945
940
943 business pr
943

944

944

947

945

945
940
945

940 process

SET issues

SET issues

SET issues
error msg

Order Line Split with multiple deliveries against the same order line

Missing Lot Number (3PL Short shipped with multiple lots allocated)

Ship Set count mismatch (Short ship with ship set orders)

Serial Number Mismatch - Serial Number shipped not in FG or shipped out in Oracle

Lot Number shipped by DSV doesn’t match with what was allocated

Error in create shipment records in Oracle Ebiz : ORA-00060: deadlock detected while waiting for resource

Serial number does not match with whats shipped

Order is picked, but not shipped due to HOLD

, EDI944-API-ERROR :QUANTITY: Error: Quantity XX is greater than 10, quantity ordered plus tolerance.

Cause: Quantity you wish to ship is greater than quantity ordered plus the over receipt tolerance.

Action: Either reduce the quantity to ship or increase your quantity received tolerance on the Purchase Order.

Sold_to Org error

, EDI944-API-ERROR :ORG_ID: Error: The ORG_ID specified is invalid. The value specified (1354) does not match the expect
lot serial mismatch between 940 and 945

lot serial mismatch when manual update on allocation by user

shipment received for same delievry in diffeent time, and delivery closed with first shipment and second shipment fails sinc
Derma item reelased in decimal qty due to UOM conversion
ship set order not interfaced
order header DFF Phone Fax filed length issue
order not send to 3PL - due to requsition type (Purchase order)
no 943 receievd since internal sales order shipment is not closed

receiving failed due to shipment with multiple orders in one delivery, code can not handle this cae and we need to manual
records to success

receipt routing at item level is not direct, manually receive and inspect and update records to success

buisness verifying 947 error on 3pL error correction form and updating the records accordingly and request to update the r

intercompany order from O&M to BOMI, order not closed at 115 and 943 send to BOMI and no 944 at BOMI which need to
data extract for pricing
record in V status - code fix required and shipment not closed

Order is closed in Oracle by DSV logistics due to lot mismatch or different lot / serials- so they may request us to mark thos
before marking the record to success -usually I will go through entire order to decide whether those records can be marked

Orders Not Transmitted to DSV - We have to check from Order -> Delivery -> Outbound ( a series of checks are here ) -> SOA
shipment split lines for partial quantity releases, code is not back ordering remaining quantity and crerates new delievry wi
Issues faced by DSV logistics while fixing EDI 945 - Example while they correcting 945 - some new delivery drop out to DSV
Observed reduction in this scenario after explaining scenarios where we can have double delivery drop out
Set Related issues
Not able to book set sales order at 135 - training required for IS support

Error in EDI 947

123956 : EDI947-17: Unable to derive mandatory parameters due to wrong Adjustment code - error in xx_derive_trans_typ
: EDI947-25: No Valid records to be processed for intf_inbound_id: 1126147

adjustment transaction type - 56 added to lookup XXINTG EDI 947 ADJ Code

Set Nr in order is not matching with the sub-inventory Set Nr

Backorder lines cannot be removed

Customer service may request to back order if they want to modify or cancel the order
Deliveries got pick confirmed in Oracle - but not ship confirmed - but no errors in 3PL - some delay to get it done by progra
RMA issues - those got stuck in EDI 944
IRISO Scenarios - from DSV to BOMI - EDI 943 ( type internal should be there), CANADA TO DSV etc.
Order is not booking - various reasons like - credit check failure hold
Order is not closing / invoicing - due to holds or due to any other miscellaneous issues

Order not booked:

Price override approval looping in which happens basically when there is price list missing from order line level.
Order on hold.
Sales credit not 100%
Order not released to Warehouse:
Hold on order header/line level and they are trying to release without removing hold.
Onhand of Items does not exists in Inventory.
How to cancel the Order:
Sometimes CS has issue cancelling an order which is in status of released to Warehouse.

Apart from this on purchasing side we get most issues related to Approval Hierarchy or change the approval hierarchy for a
what to do to fix ?
The order line number needs to be updated in the 3PL tool and re-submitted. Currently, I use SOAP UI to re-submit the
transactions. 3PL tool can be used once it is available and usable

Go to Transact Move order form and check the lots allocated. If DSV has not shipped one of the lots, delete the lot and
update the qty on the View/ Update Allocations screen so that the qty allocated matches with the Lot/Serial Qty. Save.
Once allocations are modified, resubmit the transaction
DSV does not consider ship sets. (We have asked them to fix this issue). Update the order and remove the ship sets.
Resubmit the transaction

Check the status of the serial number. If serial number is not in FG or if it shipped on another order, we have to receive the
serial or move it to FG and re-submit the transaction. Serials have to be adjusted since there was an issue where-in DSV
shipped the same serial against two orders due to a bug. We may have to issue out another serial to compensate for the
duplicate serial shipped. CS may need to get you the correct serial number
Go to Transact Move order form, and check the lot allocated. If DSV has shipped a different lot, change the lot allocated in
the transact move order form. Save. Once allocations are modofied. Resubmit the transaction

This is due to locking issue. Just re-submit the transaction and it should process

Serial number is present, but CS has reserved a different serial number against the order. This is wrong practice, as we do
not send serial numbers in the EDI message. CS should not be reserving serial numbers. Any specific serial number(s) to be
picked should be communicated manually to 3PL. If this happens, we will have to backorder that line to relieve reservation
If this part of a larger order - unassign that specific line from the delivery. Auto-create delivery to create a new delivery for
that line. Backorder just that line using the ship confirm option. Once the line is backordered, reserve the correct serial
number(s) that was shipped by 3PL. Pick release the order with prior reservations flag checked, AND Auto-pick, AND Auto-
ship enabled. This will pick and ship the line with a new delivery without sending an EDI message to 3PL. The remaining
lines can be shipped/ picked using the original delivery. (Just that the serial number will be part of a different delivery)

Check if the order is put on Manual allocation or shipping hold. If the order or line is on hold, remove the hold and
manually ship the delivery. The interface records may have to be updated to Success, since we are manually ship
confirming the delivery through the form

This happens for an IR/ISO shipment if the same ISO line has multiple delivery detail lines picked with the same lot number
The fix has been moved to Production. The way to fix this would be to manually receive the shipment through Oracle
forms, and update the interface records to Success (Table: XX_944_RECPT_CREATION_STG) and delete the error records
from the EDI error table (xx_edi_interface_errors)

This happens for an IR/ISO shipment if the same shipment has mutiple ISOs consolidated into a single delivery before
interfacing from the source site. This issue has been repoorted to the development team and they are working on a fix to
send one EDI message per shipment/ per order number (ISO). Until then, the fix would be to manually receive the
shipment through Oracle forms, and update the interface records to Success (Table: XX_944_RECPT_CREATION_STG) and
delete the error records from the EDI error table (xx_edi_interface_errors)

New error: being reviewed by development. Do not know the reason yet. Until then, the fix would be to manually receive
the shipment through Oracle forms, and update the interface records to Success (Table: XX_944_RECPT_CREATION_STG)
and delete the error records from the EDI error table (xx_edi_interface_errors)
update lot allocation in transact move order based in 3PL Lot / serial details and resumit error records from 3PL error
correction form
update lot allocation in transact move order based in 3PL Lot / serial details and resumit error records from 3PL error
correction form
communicate to 3PL to cancel new delievry created due to partial shipment, update the deleivry with second partial lot
and close manaually
3PL onhand code hadling uom conversion with viswa to fix - Pual Jennings need to work on daily basis

Rosa / Rohan busienss process issue EDI code only handling internal req

data extract provoided daily to business to reconcile and receive and need funtionaly in 3PL errror correctio form to update
those records to success

request to update the records to success

code issue

fixed to release only released to warehouse, if auto pick confirm is enabeled order not released again

training required for IS support

manually done from iProc by inserting required person in managerial approval.
S.No

5
6
7
8
9
10
Issue Description
Order is closed in Oracle by DSV logistics - so they may request us to mark those records to success in interface table - before m
success or not
Orders Not Transmitted to DSV - We have to check from Order -> Delivery -> Outbound ( a series of checks are here ) -> SOA B2
Known Issue in EDI 940 outbound interface - split lines stage pick confirm issue
Issues faced by DSV logistics while fixing EDI 945 - Example while they correcting 945 - some new delivery drop out to DSV - no
Observed reduction in this scenario after explaining scenarios where we can have double delivery drop out
Set Related issues
- Set Nr in order is not matching with the sub-inventory set nr
- Backorder lines cannot be removed
Customer service may request to back order if they want to modify or cancel the order
Deliveries got pick confirmed in Oracle - but not ship confirmed - but no errors in 3PL - some delay to get it done by programs
RMA issues - those got stuck in EDI 944
IRISO Scenarios - from DSV to BOMI - EDI 943 ( type internal should be there), CANADA TO DSV etc.
Order is not booking - various reasons like - credit check failure hold
Order is not closing / invoicing - due to holds or due to any other miscellaneous issues