Muftasoft TM

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
[[https://customnews.pk/2015/08/17/pakistan-customs-towards-implementation-of-edi-standards-for-e-manifestation/|
 Pakistan Customs Towards Implementation of EDI Standards for e-manifestation ]]

With the beginning of the 21st century, expansion in the horizon of globalization and trade liberation has transposed itself into a huge volume of trade cargo moving across the borders of the country. As requisites of trade potential, assurance of encouraging environment for safe and reliable supply chains across the countries and/or regions taken together with effective controls and enforcement measures; and harmonization of business procedures are key challenges faced by Pakistan Customs.

Luckily, Customs has developed an indigenous system [i.e. Web based One Customs (WeBOC)] which is paperless, web enabled, and an end-to-end integrated automated system to serve as a modern, efficient, effective and corruption free Customs administration. Gradual development and enhancement of WeBOC is aimed at making the system compliant of trade facilitation agreements, WCO data model and Revised Kyoto Convention with regards to simplification and harmonization of procedures. The vision of the Directorate of Reforms and Automation (Customs) is focused on endeavoring to eliminate divergence between Customs procedures and practices that can hamper international trade, international exchanges and the application of Customs procedures/ practices in a predictable, consistent and transparent manner.

Following the success at sea, the footprints of WeBOC has entered into the air industry. Recently, an air cargo import manifestation module has been deployed smoothly in WeBOC w.e.f. 04th January 2015. Separate clearance lanes for ICG, courier, human remains, unaccompanied baggage, mail, dangerous goods and general import have been introduced in the system.  Air manifestation classifies into home consumption (HC), Into Bond (IB), Transshipment (TP), Inter-port movement (IP) and transit. In an effort to level the roadmap for secure and safe supply chain, Customs is working with external organizations to establish Electronic Data Interchange (EDI) with airlines. For the said purpose, the Directorate has signed a Memorandum of Understanding (MoU) on technical cooperation with International Air Transport Association (IATA) on 17th August 2015 at Karachi. The scope of this MoU is to cooperate with each other in the implementation of –

IATA’s Cargo-XML standards in a new automated manifestation framework for the airlines operating in Pakistan, which is WCO compliant.

IATA’s Advance Passenger Information exchange standards, based on UN/EDIFACT, WCO/ICAO compliant.

The objective is to implement standardized simple set of trade-related data that can make it easier for legitimate traders to meet legal, regulatory and administrative requirements by reducing the amount of time, effort and money needed to gather, collate and submit data. According to a USAID study, the World Bank’s Cost of Doing Business Index has ranked Pakistan at the 91st position out of 189 countries in terms of trade across borders1. In comparison with Central Asian Republics like Singapore, Hong Kong, South Korea, Pakistan’s standing is relatively low. At present, sea terminals (KICT, PICT and QICT), on-the-dock terminals (KPT) and off dock terminals (NLC, Pak Shaheen, AICT and BOML) are EDI based stations under WeBOC for sea cargo clearance. Contrary to sea EDI standards, IATA’s standards are upgraded with high data quality, integrity and more character space. The digital supporting documents such as invoice, packing list and certificate of origin (CoO) are also embedded in the e-manifestation package. Due to multimodal and cross border features of cargo XML standards, Customs authorities like Mexico, Paraguay, Argentina, Abu Dhabi, Qatar, Bahrain, Canada and USA Customs have moved forward for adoption of these standards.

For transition to EDI standards, IATA’s assistance, as per the MoU, will include a review of the technical documentation, a provision of technical guidance, resolution of technical issues, rendering assistance in the testing phase with regards to the development of EDI software until its smooth roll out.

The terms of this MOU are entirely voluntary and will not be deemed to constitute or create any legal binding or enforceable obligations. However, each Party’s rights and interests are reserved with respect to national security, national and public interest or public order, protection of intellectual property rights and confidentiality and secrecy of documents, information and data, to undertake appropriate steps or consultation to ensure that its rights and interests are protected and safeguarded.

IATA has already extended its assistance to Pakistan Customs by sharing the Cargo XML manual and toolkit. In light of the toolkit, the Directorate has developed referential documents and Requirement Specification Documents (RSD) on Cargo XML and API in automated air cargo manifestation frameworks. The same has been duly vetted by IATA’s head office, Geneva. Numerous meetings via video/audio conferencing with Mr. Tahir Syed, (Manager Cargo Electronic Messages-IATA) and Ms. Nathalie Herbelles (Assistant Director, IATA), in the head office, Geneva have been arranged. Out of 22 IATA’s member airlines operating into Pakistan, the Directorate nominated M/s Emirates and M/s PIA for pilot testing of Cargo XML EDI message with Pakistan Customs. After several deliberations with audio conferencing with IATA and the representatives of M/s Emirates, it had been decided that out of 15 components, 5 of the most crucial messages relating to flight manifest message and house manifest messages will be developed and implemented in Phase-I.

The tentative timeline for pilot testing will be planned once software development is completed by the nominated airlines as well as Customs. After successful pilot testing, the rest of the airlines will be brought onboard the same automated manifestation framework for a subsequent roll out of the EDI standards by the end of 2015. Parallel, implementation of API comprising of exchange of passenger data elements by airlines to Customs prior to flight departure or arrival, being visualized for “speedy clearance or prevention to board” of a passenger, at control points is the next goal to achieve.

The main areas of benefits and importance of IATA’s EDI standards are:

Improvement of efficiency, precision, accuracy, security and safety of data/information.

Reduction of errors and dwell time.

Compliance with regulations and facilitation of advocacy.

Facilitation for implementation and adoption of the e-Cargo initiatives such as the electronic Air Waybill (e-AWB).

Real time integration and acknowledgement of data enabling less extra physical controls and requirements.

Prevention of fraud, illegal migration, suspicious travel patterns of passenger under API.

Provision of pre-arrival e-manifestation of cargo and passengers, 4 hours for long haul flights and at wheel-off for short haul flights

Easy monitoring and reconciliation of data

Threat assessment and management of risk profiling of ports from where cargo/passenger is flowing in Pakistan

**Alignment with WCO recommendations regarding dematerialization of paper, thus:**

No hard copies will be required if electronic documents have been submitted

Customs will rely on electronic declarations (automated verification of information)

Digital supporting documents may be stored in repositories

With the tenacious and proactive approach of the Director, the initiative like implementation of WCO compliant EDI standards, has expressed the pledge and promise, competence and capability of Pakistan Customs to take Pakistan forward towards modernization.


[[https://en.wikipedia.org/wiki/XML/EDIFACT|
XML/EDIFACT]]



XML/EDIFACT is an Electronic Data Interchange (EDI) format used in Business-to-business transactions. It allows EDIFACT message types to be used by XML systems.

EDIFACT is a formal machine-readable description of electronic business documents. It uses a syntax close to delimiter separated files. This syntax was invented in the 1980s to keep files as small as possible. Because of the Internet boom around 2000, XML started to become the most widely supported file syntax. But for example, an invoice is still an invoice, containing information about buyer, seller, product, due amount. EDIFACT works perfectly from the content viewpoint, but many software systems struggle to handle its syntax. So combining EDIFACT vocabulary and grammar with XML syntax makes XML/EDIFACT.

The rules for XML/EDIFACT are defined by ISO TS 20625.
Use-cases

XML/EDIFACT is used in B2B scenarios as listed below:

    Newer EAI or B2B systems often cannot handle EDI (Electronic Data Interchange) syntax directly. Simple syntax converters do a 1:1 conversion before. Their input is an EDIFACT transaction file, their output an XML/EDIFACT instance file.
    XML/EDIFACT keeps XML B2B transactions relatively small. XML element names derived from EDIFACT tags are much shorter and more formal than those derived from natural language since they are simply expressions of the EDIFACT syntax.
    A company does not want to invest into new vocabularies from scratch. XML/EDIFACT reuses business content defined in UN/EDIFACT. Since 1987, the UN/EDIFACT library was enriched by global business needs for all sectors of industry, transport and public services.
    Large companies can order goods from small companies via XML/EDIFACT. The small companies use XSLT stylesheets to browse the message content in human readable forms, as shown in Example 3.

[[https://unece.org/trade/documents/2023/10/executive-guide-unedifact|
Executive Guide on UN/EDIFACT]]

United Nations Electronic Data Interchange for Administration, Commerce and Transport (UN/EDIFACT) is the global Electronic Data Interchange (EDI) standard developed and maintained by the United Nations Centre for Trade Facilitation and Electronic Business (UN/CEFACT). EDI is defined as “computer to computer interchange of data according to a message standard with a minimum of human intervention”. Differently said, it allows for business documents such as purchase orders, invoices and customs declarations to be exchanged and processed electronically.

UN/EDIFACT development started at the end of the 1980s and the standard currently contains 209 business messages. Updated versions are published twice a year.
Downloads
  


[[https://unece.org/sites/default/files/2023-10/ExecGuide_UNEDIFACT_Eng.pdf|
Executive Guide
UN/EDIFACT]]


[[https://unece.org/info/events/unece-meetings-and-events?f%5B0%5D=area%3A10&f%5B1%5D=program%3A1|
EDIFACT events]]


[[https://stackoverflow.com/questions/11295551/is-there-a-really-simple-way-to-process-edifact-for-example-d96a|
Is there a really simple way to process EDIFACT for example D96A?]]

[[https://github.com/EdiFabric/EDIFACT.NET|
EdiFabric C# .NET Examples for EDIFACT D96A, EANCOM D03B, IATA PADIS, and eDIGAS]]

[[https://github.com/mloukili/edi-converter|
X12, HL7 and Edifact Converters were designed to meet the demands of EDI based integration projects as many B2B integration scenarios involve the use of EDI standards like X12, HL7 and Edifact in exchanging business documents.]]

[[https://blog.symtrax.com/edifact-and-xml-a-how-to-conversion-guide/|
EDIFACT and XML: A How-to Conversion Guide]]

[[https://www.seeburger.com/resources/good-to-know/what-is-edifact|

What is EDIFACT?]]

EDIFACT is the abbreviation for Electronic Data Interchange for Administration, Commerce and Transport. This is a global set of rules defined by the UN for the inter-company electronic data exchange (EDI) between two or more business partners via EDI.

[[https://www.cbp.gov/travel/travel-industry-personnel/apis/implement-overview|
Message Implementation
Guideline for Airlines
UN/EDIFACT
PAXLST/CUSRES
Message Sets v4.2 Overview]]




[[https://www.cbp.gov/sites/default/files/assets/documents/2016-Sep/DHS_CUG_v4%202_09-06-2016_Pt%204_EDIFACT.pdf|


[[https://home.messagexchange.com/blog/the-evolution-of-edi-file-formats-from-edifact-to-ansi-x12-xml-and-beyond/|
The evolution of EDI file formats from EDIFACT to ANSI X12, XML and beyond]]

[[https://unece.org/trade/uncefact/mainstandards|

Streamlined presentation of UN/CEFACT standards]]

Welcome to the UN/CEFACT Streamline Presentation of Standards. As a globally recognized body, UN/CEFACT is committed to facilitating international trade and promoting seamless business transactions through the development and implementation of harmonized standards. This page is dedicated to the presentation of the extensive range of standards, ensuring easy access and comprehension for users from diverse sectors and regions. Whether you are an industry professional, a policymaker, or a technology enthusiast, this page serves as a valuable resource to navigate the world of UN/CEFACT standards and unlock new opportunities for efficient and secure global trade

[[https://academy.dovetail.world/docs/components/components_intro|
Introduction

In Dovetail you build your integration flows with a combination of the available components.]]


They are divided into 4 groups:

    Endpoints: components that can send or receive some kind of data.
    Construction: special components that help with creating more advanced flows.
    Routing: components that help with routing your data in different ways.
    Transformations: components that help with transforming data to other formats.

Use the sidebar on the left to navigate to a specific group/component.


[[https://xtranslator.com/|
EDI tools

Translation, validation, processing... it's all here]]

[[https://tech.forums.softwareag.com/t/edifact-d09b-schema-export/110410|

EDIFACT D09B Schema Export]]

[[https://www.odoo.com/forum/help-1/import-and-export-edifact-messages-to-and-from-odoo-edi-in-general-224253|
Import and export EDIFACT messages to and from odoo (EDI in general)]]


[[https://www.odoo.com/forum/help-1/what-format-of-edi-file-require-for-import-export-24723|
What format of EDI file require for Import/Export ?]]

[[https://easyedi.dk/solutions/easyedi-for-odoo/|
easyEDI for Odoo]]

[[https://www.odoo.com/documentation/17.0/applications/essentials/export_import_data.html|
Export and import data Odoo]]

[[https://apps.odoo.com/apps/modules/8.0/edifact|
Edifact

Base module for import / export edifact desadv files.]]

[[https://apps.odoo.com/apps/modules/16.0/base_edifact|
Base EDIFACT

Alpha License: AGPL-3 OCA/edi Translate me on Weblate Try me on Runboat

This module contains methods to generate and parse EDIFACT/D96A files]]



[[https://www.agriculture.gov.au/biosecurity-trade/export/certification/exdoc|
Australia grains EDI]]



[[https://www.agriculture.gov.au/biosecurity-trade/export/certification/exdoc/interface-specs|

EXDOC exporter interface specifications, errata sets]]



[[https://www.stylusstudio.com/edi/EDIFACT-translate.html|
Translating EDIFACT documents to XML]]


[[https://github.com/mloukili/edi-converter|
Parse and Convert EDI files (X12, EDIFACT, HL7) to XML and vice-vers-ca]]