Tuesday, March 18, 2014

Get Item On Hand Quantities of the item through API in Oracle Inventory

This script can be used to get the below quantities.
1. On-hand Quantity
2. Available to Reserve
3. Quantity Reserved
4. Quantity Suggested
5. Available to Transact
6. Available to Reserve

You can also get the On-hand quantities from the table mtl_onhand_quantities

GET ON-HAND QUANTITIES API

DECLARE
   x_return_status         VARCHAR2 (50);
   x_msg_count             VARCHAR2 (50);
   x_msg_data              VARCHAR2 (50);
   v_item_id               NUMBER;
   v_org_id                NUMBER;
   v_qoh                   NUMBER;
   v_rqoh                  NUMBER;
   v_atr                   NUMBER;
   v_att                   NUMBER;
   v_qr                    NUMBER;
   v_qs                    NUMBER;

   v_lot_control_code      BOOLEAN;

   v_serial_control_code   BOOLEAN;

BEGIN

   -- Set the variable values

   v_item_id := '6566';

   v_org_id := 61;

   v_qoh := NULL;

   v_rqoh := NULL;

   v_atr := NULL;

   v_lot_control_code := FALSE;

   v_serial_control_code := FALSE;

   -- Set the org context

   fnd_client_info.set_org_context (1);

   -- Call API

   inv_quantity_tree_pub.query_quantities

   (p_api_version_number       => 1.0,

    p_init_msg_lst             => 'F',

    x_return_status            => x_return_status,

    x_msg_count                => x_msg_count,

    x_msg_data                 => x_msg_data,

    p_organization_id          => v_org_id,

    p_inventory_item_id        => v_item_id,

    p_tree_mode                => apps.inv_quantity_tree_pub.g_transaction_mode,

    -- or 3

    p_is_revision_control      => FALSE,

    p_is_lot_control           => v_lot_control_code,

    -- is_lot_control,

    p_is_serial_control        => v_serial_control_code,

    p_revision                 => NULL,        -- p_revision,

    p_lot_number               => NULL,           -- p_lot_number,

    p_lot_expiration_date      => SYSDATE,

    p_subinventory_code        => NULL,    -- p_subinventory_code,

    p_locator_id               => NULL,           -- p_locator_id,

    -- p_cost_group_id            => NULL,       -- cg_id,

    p_onhand_source            => 3,

    x_qoh                      => v_qoh,      -- Quantity on-hand

    x_rqoh                     => v_rqoh,           --reservable quantity on-hand

    x_qr                       => v_qr,

    x_qs                       => v_qs,

    x_att                      => v_att,  -- available to transact

    x_atr                      => v_atr    -- available to reserve

   );

   DBMS_OUTPUT.put_line ('On-Hand Quantity: ' || v_qoh);

   DBMS_OUTPUT.put_line ('Available to reserve: ' || v_atr);

   DBMS_OUTPUT.put_line ('Quantity Reserved: ' || v_qr);

   DBMS_OUTPUT.put_line ('Quantity Suggested: ' || v_qs);

   DBMS_OUTPUT.put_line ('Available to Transact: ' || v_att);

   DBMS_OUTPUT.put_line ('Available to Reserve: ' || v_atr);

EXCEPTION

   WHEN OTHERS

   THEN

      DBMS_OUTPUT.put_line ('ERROR: ' || SQLERRM);

END;




GET ON-HAND QUANTITIES FROM TABLE

SELECT * FROM MTL_ONHAND_QUANTITIES;

Monday, March 17, 2014

Service line in stuck with status "Awaiting Invoice Interface - Incomplete Data" in OM Oracle APPS R12

Environment
  • Module = Oracle Service Contracts
  • Release = R12i Oracle E-Business Suite
Steps to reproduce
  1. Create SO and two SO lines. The second SO line is a Service Line.
  2. You have given Service duration and Service Period, but the system didn't automatically populated Service Start Date and Service End Date fields.
  3. Run Pick Release and Ship Confirm. Then Workflow background process.
  4. First SO line (which contains the main item) got closed, and got an invoice generated. But the second SO line (service line) stuck in status "Awaiting Invoice Interface - Incomplete Data".
Root Cause of the issue
  1. The system didn't automatically populated 'Service Start Date' and 'Service End Date' fields associated with SO's Service Line.
Resolution
  1. Simply go back and query the SO. Go to the service line and manually give the 'Service Start Date'. The 'Service End Date' will be populated automatically.
  2. Now go to 'Actions' > 'Progress Order' > Choose 'Invoice Interface - Eligible'.
  3. Now the 'Autoinvoice Master Program' and 'Autoinvoice Import Program' will be launched automatically, and invoice will be generated.
  4. Check the invoice associated with the Service line.

Wednesday, January 15, 2014

Delete PO by using API

API "po_headers_sv1.delete_po" can be used to delete POs.

Parameters : 
            X_po_header_id     => PO Header ID
            X_type_lookup_code => Type Lookup Code
            -- STANDARD/PLANNED/BLANKET/CONTRACT
            p_skip_validation  => N/Y
p_skip_validation -> By default it is 'N', if it is 'Y', It checks the encumbered flag in po distribution table against the po header.

Note:- INCOMPLETE POs can be deleted from Purchase Order form itself.
       Though this API can delete Approved POs as well, it is recomended that use this API to delete only INCOMPLETE Pos, because APPROVED POs have entry in inventory and archive tables and this API does not delete the related entries from these tables. Records will be deleted only from base tables.

R12 tested Sample Script :
DECLARE
   l_result                     BOOLEAN                                      ;
   l_po_header_id        NUMBER          := <po_header_id> ;
   l_type_lookup_code VARCHAR2(8) := <lookup_code>  ;
   l_validation               VARCHAR2(1) := <validation_flag> ;
BEGIN
   DBMS_OUTPUT.put_line ( 'API PO_HEADERS_SV1 Call to delete PO with header :'||l_po_header_id);
   l_result := po_headers_sv1.delete_po (X_po_header_id         => l_po_header_id
                                                             ,X_type_lookup_code => l_type_lookup_code
                                                             ,p_skip_validation        => l_validation);

   IF l_result = TRUE THEN
      COMMIT;
      DBMS_OUTPUT.put_line ( 'PO with header: '||l_po_header_id||',Deleted Successfully');
   ELSE
      ROLLBACK;
      DBMS_OUTPUT.put_line ( 'PO with header: '||l_po_header_id||',Failed to Delete');
   END IF;
   DBMS_OUTPUT.put_line ( 'Deletion Process Over');
EXCEPTION
   WHEN OTHERS THEN
      DBMS_OUTPUT.put_line ( 'Error : '|| SQLERRM);
END;

Cancelling PO by Using API called PO_Document_Control_PUB.control_document

PO_Document_Control_PUB.control_document ? 
  • The PL/SQL procedure, PO_Document_Control_PUB.control_document , provides the ability to cancel Oracle Purchasing documents directly through an API.
  • The API will perform all of the same processing that would be done if a cancellation was requested through the PO Summary Control Window.
  • Prior to calling the API we should set our global context to reflect the application, user and responsibility used to perform the cancel action. If we do not set this context, the API will not be able to identify or update your data.
--R12 - PO - Sample Script to cancel PO using po_document_control_pub API.sql

DECLARE

l_return_status VARCHAR2 (10);

CURSOR C_PO_CANCEL is

SELECT pha.po_header_id,
pha.org_id,
pha.segment1 po_number,
pha.type_lookup_code,
pha.cancel_flag,
pha.closed_code
FROM po_headers_all pha
WHERE 1=1
AND pha.segment1 = '376729' -- Enter The Purchase Order Number
AND nvl(pha.closed_code,'OPEN') = 'OPEN'
AND nvl(pha.cancel_flag, 'N') = 'N'
AND approved_flag = 'Y';

BEGIN

fnd_global.apps_initialize (user_id => 1804,
resp_id => 20707,
resp_appl_id => 201);

FOR i IN c_po_cancel

LOOP

mo_global.init ('PO');
mo_global.set_policy_context ('S',i.org_id );

DBMS_OUTPUT.PUT_LINE ('Calling API PO_DOCUMENT_CONTROL_PUB.CONTROL_DOCUMENT For Cancelling Documents');

po_document_control_pub.control_document
(p_api_version => 1.0, -- p_api_version
p_init_msg_list => fnd_api.g_true, -- p_init_msg_list
p_commit => fnd_api.g_true, -- p_commit
x_return_status => l_return_status, -- x_return_status
p_doc_type => 'PO', -- p_doc_type
p_doc_subtype => 'STANDARD', -- p_doc_subtype
p_doc_id => i.po_header_id, -- p_doc_id
p_doc_num => NULL, -- p_doc_num
p_release_id => NULL, -- p_release_id
p_release_num => NULL, -- p_release_num
p_doc_line_id => NULL, -- p_doc_line_id
p_doc_line_num => NULL, -- p_doc_line_num
p_doc_line_loc_id => NULL, -- p_doc_line_loc_id
p_doc_shipment_num => NULL, -- p_doc_shipment_num
p_action => 'CANCEL', -- p_action
p_action_date => SYSDATE, -- p_action_date
p_cancel_reason => NULL, -- p_cancel_reason
p_cancel_reqs_flag => 'N', -- p_cancel_reqs_flag
p_print_flag => NULL, -- p_print_flag
p_note_to_vendor => NULL, -- p_note_to_vendor
p_use_gldate =>NULL ,
p_org_id => i.org_id
);

COMMIT;

DBMS_OUTPUT.PUT_LINE('The Return Status of the API is => ' l_return_status);
If l_return_status = 'S' Then

DBMS_OUTPUT.PUT_LINE('The Purchase Order Which is Cancelled Now => ' i.po_number);
Else

DBMS_OUTPUT.PUT_LINE('The Purchase Order =>' i.po_number 'Failed to cancel Due To Following Reason');

-- Get any messages returned by the Cancel API

FOR j IN 1 .. fnd_msg_pub.count_msg
LOOP
DBMS_OUTPUT.put_line (fnd_msg_pub.get
(p_msg_index => j,
p_encoded => 'F'));
END LOOP;
END IF;
END LOOP;
END;

=============================

PO Cancel API Script:

CREATE OR REPLACE PROCEDURE APPS.XXPO_CANCEL_PO
(ERRBUFF VARCHAR2, RETCODE NUMBER, P_DOC_NUM VARCHAR2)
IS
CURSOR FETCH_PO_CUR IS
SELECT * FROM PO_HEADERS_ALL
WHERE SEGMENT1 = P_DOC_NUM
AND ORG_ID = FND_PROFILE.VALUE('ORG_ID');

V_USER_ID NUMBER ;
V_RESPONSIBILITY_ID NUMBER ;
V_RESPONSIBILITY_APPL_ID NUMBER ;
V_ORG_ID VARCHAR2(20) ;
L_RETURN_STATUS VARCHAR2(1) := NULL;
L_MSG_DATA VARCHAR2(2000);
V_SUCCESS_COUNT NUMBER;
V_FAILURE_COUNT NUMBER;

BEGIN
V_SUCCESS_COUNT := 0;
V_FAILURE_COUNT := 0;

FOR FETCH_PO_REC IN FETCH_PO_CUR
LOOP
FND_FILE.PUT_LINE(FND_FILE.LOG , 'START OF CANCEL PO PROCESS API'SYSDATE );
BEGIN
V_USER_ID := FND_GLOBAL.USER_ID ;
V_RESPONSIBILITY_ID := FND_GLOBAL.RESP_ID ;
V_RESPONSIBILITY_APPL_ID := FND_GLOBAL.RESP_APPL_ID;
FND_GLOBAL.APPS_INITIALIZE( V_USER_ID ,V_RESPONSIBILITY_ID,V_RESPONSIBILITY_APPL_ID);
V_ORG_ID:=FND_PROFILE.VALUE('ORG_ID');
MO_GLOBAL.INIT('PO');
MO_GLOBAL.SET_POLICY_CONTEXT('S',V_ORG_ID);
EXCEPTION
WHEN OTHERS THEN
FND_FILE.PUT_LINE(FND_FILE.LOG , 'ERROR CODE FOR INITIALIZATION IS :'TO_NUMBER( SQLCODE )' ' 'ERROR MSG FOR INITIALIZATION IS :'SUBSTR( SQLERRM , 1 , 50) ) ;
END ;

FND_MSG_PUB.INITIALIZE ;
FND_FILE.PUT_LINE(FND_FILE.LOG , 'PO NUMBER TO CANCEL IS :'FETCH_PO_REC.SEGMENT1 ) ;

IF FETCH_PO_REC.AUTHORIZATION_STATUS <> 'APPROVED'
THEN
UPDATE PO_HEADERS_ALL
SET AUTHORIZATION_STATUS = 'APPROVED'
WHERE SEGMENT1 = FETCH_PO_REC.SEGMENT1 ;
END IF;

PO_DOCUMENT_CONTROL_PUB.CONTROL_DOCUMENT
(1.0, -- P_API_VERSION
FND_API.G_TRUE, -- P_INIT_MSG_LIST
FND_API.G_TRUE, -- P_COMMIT
L_RETURN_STATUS,-- X_RETURN_STATUS
'PO', -- P_DOC_TYPE
'STANDARD', -- P_DOC_SUBTYPE
NULL, -- P_DOC_ID
FETCH_PO_REC.SEGMENT1, -- P_DOC_NUM
NULL, -- P_RELEASE_ID
NULL, -- P_RELEASE_NUM
NULL, -- P_DOC_LINE_ID
NULL, -- P_DOC_LINE_NUM
NULL, -- P_DOC_LINE_LOC_ID
NULL, -- P_DOC_SHIPMENT_NUM
'CANCEL', -- P_ACTION
SYSDATE, -- P_ACTION_DATE
NULL, -- P_CANCEL_REASON
'N', -- P_CANCEL_REQS_FLAG
NULL, -- P_PRINT_FLAG
NULL, -- P_NOTE_TO_VENDOR
'N' ); --P_USE_GLDATE

FND_FILE.PUT_LINE(FND_FILE.LOG,'API RETURN STATUS IS-' L_RETURN_STATUS);

IF L_RETURN_STATUS = 'U' THEN --( FND_API.G_RET_STS_UNEXP_ERROR)
FND_FILE.PUT_LINE(FND_FILE.LOG, 'UNEXPECTED ERROR IN CANCEL PO PROCESS API');
FND_MSG_PUB.ADD_EXC_MSG('QP_PRICE_LIST_PUB',' UNEXPECTED ERROR IN CANCEL PO PROCESS API');
ELSIF
L_RETURN_STATUS ='E' THEN --- ( FND_API.G_RET_STS_ERROR )
FND_FILE.PUT_LINE(FND_FILE.LOG, 'ERROR IN CANCEL PO PROCESS API');
FND_MSG_PUB.ADD_EXC_MSG('QP_PRICE_LIST_PUB','ERROR IN CANCEL PO PROCESS API');
END IF;

IF L_RETURN_STATUS != 'S' THEN
V_FAILURE_COUNT := V_FAILURE_COUNT + 1;
FND_FILE.PUT_LINE(FND_FILE.LOG, 'TOTAL FAIL RECORD COUNT'V_FAILURE_COUNT);
FOR ERR_CODE IN 1..FND_MSG_PUB.COUNT_MSGLOOP
L_MSG_DATA := SUBSTR(FND_MSG_PUB.GET(P_MSG_INDEX => 1,P_ENCODED=>'F'),1,200);
FND_FILE.PUT_LINE(FND_FILE.LOG,'CANCEL PO PROCESS API FAILED FOR REASON-'L_MSG_DATA ) ;
END LOOP;
END IF;

IF L_RETURN_STATUS = 'S' THEN --- ( FND_API.G_RET_STS_SUCESS)
FND_FILE.PUT_LINE (FND_FILE.LOG, 'CANCEL PO PROCESS API PASSED' ) ;
V_SUCCESS_COUNT := V_SUCCESS_COUNT + 1;
FND_FILE.PUT_LINE(FND_FILE.LOG,'TOTAL SUCCESS RECORD COUNT-'V_SUCCESS_COUNT);

-- RENAME PO NUMBER AFTER CANCELLATION
UPDATE PO_HEADERS_ALL
SET SEGMENT1 = 'XX-'FETCH_PO_REC.SEGMENT1
WHERE SEGMENT1 = FETCH_PO_REC.SEGMENT1 ;

UPDATE PO_HEADERS_ARCHIVE_ALL
SET SEGMENT1 = 'XX-'FETCH_PO_REC.SEGMENT1
WHERE SEGMENT1 = FETCH_PO_REC.SEGMENT1 ;

END IF ;
END LOOP ;

EXCEPTION
WHEN OTHERS THEN
FND_FILE.PUT_LINE(FND_FILE.LOG, 'ERROR CODE IN THE EXECUTION OF CANCEL API IS :'TO_NUMBER( SQLCODE )' 'SUBSTR( SQLERRM , 1 , 50) ) ;
END XXPO_CANCEL_PO ;
/

Monday, November 11, 2013

Oracle iSupplier – Advanced Shipment Notice (ASN)

Oracle iSupplier – Advanced Shipment Notice (ASN): The Advance Shipment Notice (ASN) functionality of Oracle iSupplier helps a supplier to communicate the shipment information to the buyer while the goods are being shipped form the premises. It immensely helps the purchasing organization to estimate the expected arrival of goods which in turn helps to determine whether production schedule, customer delivery commitments etc. are on track or there may be a change in various schedules. It also saves the data entry time of the receiver, as an ASN can be automatically converted to a PO receipt which we will discuss later in this document.


Supplier contact actions:
Login to iSupplier as a supplier contact.
Click on the “Shipments” tab and then “shipment Notices” link.
Now click on “Create Advance Shipment Notices” link.
Now select appropriate view or perform an advanced search to extract the purchase orders eligible for shipments.
Select the respective PO, line or shipment you want to create the shipment notice for and click on the “Add to Shipment Notice” button.
Click on the “Shipment Header” link in the subsequent page and enter the shipment number. As expected, this number is unique. Also enter the shipment date and expected receipt date etc., as they are mandatory. You may optionally enter the Freight, packing and weight information.
Now click on the “Shipment Lines” tab and optionally enter the packing slip, container information. You may click on the “Default to All Lines” button to default the mentioned information to all the lines of the ASN or click on the “Show” link of the respective ASN line and enter the aforesaid fields if the values for various lines are not same.
You may also attach various supporting documents, such as packing slip, to the ASN which will be visible by the receiver and will appear as a “From Supplier” attachment. An ASN line can be split into multiple ASN lines if needed.
Finally click on the “Submit” button. This action will send the ASN information to the buyer as a For Your Information (FYI) notification, so that buyer can communicate to stores, planning etc. if needed.
The “Receiving Transaction Processor” program will process ASN records.
Receiver Actions:
While the shipment is in transit, the receiver can view the shipment details and update the same in the below navigation:
Responsibility: Inventory Superuser or similar
Navigation: Transactions -> Receiving -> Manage Shipments
Or
Responsibility: Purchasing Superuser or similar
Navigation: Receiving -> Manage Shipments
Select appropriate inventory organization.
Enter the ASN number in the Shipment field of the “Find In-Transit Shipments” form and click on the “Find” button. You will be able to see the shipment details and update the allowed fields. You may also cancel the whole ASN or a line of it by clicking on Tools -> Cancel menu.
Now, once the shipment arrives in the purchasing organization, the receiver converts the ASN to a PO Receipt.
Responsibility: Inventory Superuser or similar
Navigation: Transactions -> Receiving -> Receipts
Or
Responsibility: Purchasing Superuser or similar
Navigation: Receiving -> Receipts
Select appropriate inventory organization.
Enter the ASN number in the Shipment field of the “Find Expected Receipts” form and click on the “Find” button.
Now follow standard PO receiving process to complete the receiving.
Sometimes you may not get expected results on ASN or Receipt search activities. In that case, make sure to run the “Receiving Transaction Processor” program if it is not periodically scheduled.

The ASN aka Advanced Shipment Notice is a document that is sent to a buyer in advance of the buyer receiving the product. It is typically used within the context of an EDI environment. It can be used to list the contents of an expected shipment of goods as well as additional information relating to the shipment, such as order information, product description, physical characteristics, type of packaging, marking carrier information, and configuration of goods within the transportation equipment. In the implementation of the transaction the latest the ship notice may be sent is the time of shipment. In practice the ship notices just arrive before the shipment.
dgreybarrow Basic Business Needs
  • To receive a Shipping notice in Advance:
  • Provide user the ability to electronically receive supplier ship notice into Purchasing by loading an ASN electronically into Oracle Apps using the Receiving Open Interface.
dgreybarrow Business Flow
Typical Process with company using Oracle EBS would be similar to this:
  1. Supplier sends ASN.
  2. EDI validates the data for EDI standards and inserts data into Receiving Interface tables.
  3. Receiving Open Interface validates ASN data. If accepted shipment lines are populated.
  4. Supply details are maintained.
  5. Application Advice is generated. The supplier can check if there is a rejection of ASN through the advice.
dgreybarrowInbound Shipment Notice Transaction (856)
If you are using EDI Gateway , make sure you have done setup for Trading partner correctly. These are relevant Oracle Purchasing Profiles and Set-ups
The following is a list of the Purchasing set-ups related to the Receiving Open Interface.
  1. RCV: Fail All ASN Lines if One Line Fails:If the profile option is set to 'Yes' and any line failed validation, no further validation is performed for the ship notice.
    If the profile option is set to 'No' and any line failed validation, the process continues with the next line.
  2. ASN Control:In the Receiving Options window in Purchasing, select Warning, Reject, or
    None in the ASN Control field to determine how Purchasing handles the receipt against a purchase order shipment for which a ship notice exists.
  3. PO: Enable SQL Trace for Receiving Processor :If the profile option is set to 'Yes', more detailed error data is provided in the View Log screen of the Submit Request window when you run the Receiving Transaction Processor.
dgreybarrow Data Flow Diagram

Here is data flow looks typically when you are using with EDI gateway.ASN DATAfLOW
Receiving Open Interface tables which got involved in this is:
RCV_HEADERS_INTERFACE
RCV_TRANSACTIONS_INTERFACE
You can use Import Programs to submit ECEASNI.sql (856) to the Concurrent Manager to populate the Receiving Open Interface tables with data from the inbound interface file.This is applicable if you are using EDI Gateway , else you can directly use Receiving Open Interface (RCVTP) program.
Use Import Programs to submit the Receiving Open Interface (RCVTP) program to the Concurrent Manager to validate the data in the Receiving Open Interface tables.
ASN – An Inside View 
dgreybarrow What exactly is an ASN and its types
ASN stands for “Advanced Shipment Notice”.
  • An ASN is a document used to transmit critical shipping information to the receiver.
  • It contains information on the carrier, the items and quantities shipped by Order, packaging information, and (potentially) labeling data from the item, package .
  • An ASN is composed of TWO parts:
    • Serial Shipping Container Code (SSCC) barcode labels on the shipping containers
    • An “856” Electronic Data Interchange (EDI) document
  • There are two types of ASNs:
    • Standard Pack ASNs
    • Pick & Pack ASNs.
  • A Standard Pack ASN is used when the same item is packaged together in one container.
  • A Pick & Pack ASN allows for different items within the same package.
dgreybarrow Levels of ASN 
  • ASN can contain many levels of information.
  • These levels, sometimes referred to as hierarchical levels, or simply "HLs" define the different levels of detail within the ASN. These levels are different from different Trading Partner.
    • Shipment Level: This is the most broad level of detail. There is one Shipment HL allowed in an ASN. It contains data such as the Pro Number, the Bill of Lading Number, etc.
    • Order Level: There may be one or more orders per ASN. Information necessary to reconcile the shipment with the customer's orders is placed here.
    • Tare Level: This HL represents a unique pallet identification. This level is used in some, but not all ASNs, depending on your Trading Partner and the manner in which you ship your goods. It normally contains a number corresponding to a bar-coded label as well as some physical characteristics of the pallet, such as weight and size.
    • Pack Level: This level identifies each carton in the shipment (or on the pallet, if the Tare Level is used). The Pack Level HL also contains a number corresponding to a bar-coded label. Usually, but not always, the pack level is used on an ASN.
    • Item Level: The item level represents an item that is shipped. Quantity and item identification data is stored at this level
dgreybarrowA typical Business senario for Inbound ASN
  1. ABC sends a Purchase Order to the Supplier A.
  2. The supplier picks the order. As the order is picked, the supplier’s warehousing/distribution system (aka “supplier’s system”) keeps track of what items are being picked into particular shipping cartons .
  3. When the carton is closed, the supplier’s system assigns an SSCC to that carton/pallet. Instead of when the carton is closed, this is sometimes done by the supplier’s system during the allocation/cubing process.
  4. The SSCC is encoded into a barcode on a shipping label and placed on the carton/pallet.
  5. Upon shipping the shipment of cartons/pallet to ABC, the supplier’s system generates the 856 EDI and transmits it to ABC so that ABC receives the EDI prior to the shipment arriving. The 856 EDI hierarchy must match the physical shipment (carton SSCC, carton detail, pallet, PO# information, etc.).
  6. ABC receives and processes the 856 EDI and stores it in their system. ABC acts on the ASN by scheduling the receipt, scheduling labor, doing prep work, etc.
  7. The shipment arrives at ABC. The ABC receiver scans the SSCC barcode and the ABC distribution system knows what is in that carton because of the 856 EDI. The distribution software system “guides” the receiver through what is supposed to be received since it knows everything about that carton because of the SSCC and 856 EDI, including what PO it is on, what items and quantities are in it, the lots and expiration dates, pedigree information, etc.

EDI and there prevalent EDI standards:

Electronic Data Interchange (EDI) is the electronic exchange of routine business transactions. These transactions include documents such as purchase orders, invoices, inquiries, payments acknowledgements etc.
EDI is the cross-industry electronic business interchange standard that enables individuals, companies and organizations to participate in global e-commerce.
EDI enables a commonly understood and standardized format of the relevant data to be transmitted from one computer system to another with minimal human intervention.
EDI extracts information from a business process (e.g. purchase order, invoice etc). The data is usually transmitted over a Value Added Network (VAN – which acts as a electronic post offices) and delivered to a trading partner. Once the trading partner receives the information, the EDI systems will automatically translate the standardized EDI data into application data and moved to the appropriate business application.


dgreybarrow EDI Standards
  • United States
    • X12
    • EDIFACT (Multi- Industry)
  • UK
    • TRADACOMS (Retail)
    • ODETTE (Automotive)
    • EDIFACT (Multi- Industry)
  • Germany
    • VDA (Automotive)
    • ODETTE (Automotive)
    • EDIFACT (Multi-industry)
  • France
    • ODETTE (Automotive)
    • GENCODE (Retail)
    • EDIFACT (Multi- Industry)
  • Brazil
    • RND (Automotive)
    • NTC (Transportation)
    • CNAB (Banking)
    • X12 (Multi-industry)
    • EDIFACT (Multi- Industry)
  • Mexico
    • X12
    • EDIFACT (Multi- Industry)
  • Japan
    • CII (Multi-industry)
    • EDIFACT (Multi- Industry)
  • Australia
    • X12 (Multi-industry)
    • EDIFACT (Multi- Industry)