SOP FCZ

FREE ZONE-EDI system will enable the Free Zone Authority (FZA) to process Free Zone Declaration and communicate with exporters, importers, port operators and other relevant authorities via Dagang*Net. The main functions of these systems are to expedite the processing of all Free Zone documents submitted by declarants. The implementation of EDI at FZA will help to streamline the business process in line with FZA’s management Information Systems.

With effect from 1 January 2003, the form and data element for ZB1, ZB2 and ZB3 has been integrated to become only a single form that called ZB1. No changes will occur for electronic declaration as it will cater separately for each transaction.

This documents will outline the standard operating procedure to be adopted by all relevant parties when FZA-EDI system is implemented.

2.0 OBJECTIVE

The objective of the FZA-EDI system are:

To improve the response and clearance time of cargo.
To enable the Authority and Port Users to have an accurate update and monitoring of goods movement in the Port Area.
To provide an accurate and timely submission of the forms by the respective agents.
To standardize trade documents and practices.
To solve the problems of manual errors, eliminate excessive paper work, reduce delay in transit, reduce manpower costs etc.
To have a direct link with the Trading Partners through the Dagang* Net network.

3.0 ZB PROCESS FLOW

The following are the process flow for ZB Document:

3.1 ZB Declaration – Process Flow (Original)

3.2 ZB Declaration – Process Flow – Cancellation/Amendment

3.3 ZB4 Declaration – Process Flow

3.4 ZB4 Declaration – Process Flow (Cancellation)

4.0 AGENT REGISTRATION

All declarants/Agents must register with the Free Zone Authority, including those who have already registered with Customs as SMK Dagang Net users. The following are the registration procedures:-

Declarant/Agent must fill-up the registration form as attached in appendix III.
The form can be obtained from Rank Alpha Technologies or Kedai EDI during the installation of ZB front-end software or during registration as Kedai users.
The form must be submitted to FZA for registration and issuance of user’s code.
Declarant/Agent who have registered with the Customs shall use the Customs agent code to submit ZB declarations.
Those agents who are not registered with Customs will be given FZA agents’ code. Agents shall use FZA’s code to submit ZB declarations.

5.0 ZB1 (IMPORT) PROCEDURE

5.1 FZA APPROVAL PROCEDURE

5.1.1 ZB1 (Import) must be declared for all goods imported into Free Commercial Zone for subsequent re-export (sea mode transaction).

5.1.2 The following are additional scenarios by which the agent will put up ZB1 (Import) for their cargo:

For goods or equipment imported for use in Free Zone only.

After 30 days at the Free Commercial Zone.

Partial Delivery of cargo.

Cargo to go through value-added processing at the Free Commercial Zone.

5.1.3 The declarant will prepare and submit the form through EDI. All declarations must carry a valid Ship Call Number (SCN) issued by Northport because SCN is a mandatory field and will be validated by FZA back-end system.

5.1.4 If the declaration covers any item that requires OGA approval, the front-end system will prompt the declarant/agent. The declarant/agent needs to obtain prior OGA approval before submitting the declaration to FZA. The OGA approval must be submitted to FZA officer before the declaration can be approved. Failure to do so will result in the declaration to be put on hold by FZA until the necessary OGA approval has been submitted.

5.1.5 Upon successful validation at PKCS, PKCS will give PKCS response and PKCS Number to the declarant and the form will be routed to FZA.

5.1.6 Further validation will be done automatically by FZA system before the officer can view the form.

5.1.7 If the error is encountered during validation process, FZA system will send out auto rejection message with a proper error code. Upon receiving the rejection message, the declarant must rectify the error and resubmit the form using RESET option at front-end software. (Please refer to Error Code List in the appendix)

5.1.8 Upon successful validation, FZA Officer will view the form and perform an approval process.

5.1.9 If no error found ZB1 (Import) form will be pre-approved by officer without supporting document unless required.

5.1.10 The document will be put on hold if supporting document is required and a response message will be sent out with a proper reason for holding. (Please refer to Error Code list in the appendix)

5.1.11 The document will also rejected by officer if the information given is inaccurate or illogical. The reason for rejection will be given out to the declarant and relevant parties as well. If the reject message require resubmission, the declarant must rectify the error and resubmit the form using RESET option at front-end software. (Please refer to Error Code list in the appendix)

5.1.12 No registration number will be given for reject or hold messages.

5.1.13 Upon successful approval process, a response message will be sent out in ZBACK message with FZA Registration Number.

5.2 AMENDMENT/REPLACEMENT PROCEDURE

5.2.1 The declarant is allowed to amend his original message and send out replacement message.

5.2.2 The replacement message are required only after the declarant has previously sent out the original form and received FZA Registration Number.

5.2.3 Replacement messages are not meant for messages that have been rejected by FZA of PKCS due to error in data fields.

5.2.4 The agent will choose the amendment option (5 – Replacement) at the front-end system and choose code “OT – Others” for amendment in the transaction type and amend the necessary field before submitting the form to FZA.

5.2.5 PKCS will validate and send out PKCS response and PKCS number. The PKCS number will be of the same PKCS number assigned to the original message that was sent out earlier.

5.2.6 PKCS will route the replacement message to FZA for approval processing.

5.2.7 The officer will view the replacement message and approve the message if no error found. The previous declaration will be flagged as invalid and the earlier approval is considered void.

5.2.8 A response will be sent out to declarant.

5.3 CANCELLATION PROCEDURE

5.3.1 The user is allowed to cancel his original message and sent out cancellation message for the situations allowed by the authority.

5.3.2 The agent will choose the cancellation option (1 – Cancellation) at the front-end system and choose code “OT – Others” for cancellation in the transaction type and amend the necessary field before submitting the form to FZA.

5.3.3 The cancellation message is required only after the user has previously sent out the original message and received FZA Registration Number.

5.3.4 The FZA system will acknowledge the receival of cancellation message by sending out the response – cancellation received, to the declarant. FZA system will mark the form as cancelled. Further amendment/cancellation to the message won’t be accepted. (Please refer to Error Code list in the appendix)

5.3.5 Any earlier approval given to the declarants now considered as void.

5.4 OTHERS

5.4.1 Return Cargo

For return cargo to be re-exported, the declarant/agents shall declare a ZB1 (Import) and a ZB1 (Export).
While declaring the ZB1 (Import), the declarant/agent must indicate in the transaction type “RC – Return Cargo”.
If the transaction type is not indicated the declaration shall be rejected by FZA.

6.0 ZB1 (EXPORT) PROCEDURE

6.1 FZA APPROVAL PROCEDURE

6.1.1 The following are the scenarios by which the agent will put up ZB1 (Export) for their cargo:

Re-export of cargo from FCZ

6.1.2 For sea mode transaction (Transport Mode – 1 Sea), the ZB1 (Export) form must be accompanied by the corresponding ZB1 (Import) approved form. It is done electronically whereby the declarant must quote the previous PKCS ID of ZB1 (Import) in the ZB1 (Export) declaration. The FZA System will validate and check the existence of ZB1 (Import).

6.1.3 For road mode transaction (Transport Mode – 8 Re-export via Free Zone), the declarant will declare ZB1 (Export) without accompanying ZB1 (Import) because the cargo is coming from PCA through K2/K8 Road Mode. However, the declarant must indicate K2/K8 ref. number in supporting document column and bring the proper supporting document to FZA.

6.1.4 If the cargo to be declared is value added or re-packaged please use “Value Added” transaction code ( see 6.4.4 Value Added).

6.1.5 ZB1 (Export) can be declared as soon as SCN is available and all cargo must be declared before vessel ATD.

6.1.6 After considering the above scenarios, the declarant may prepare and submit the form through PKCS. ZB1 (Export) will use the FZA registration/approval number in place of Booking Reference Number.

6.1.7 Upon successful validation at PKCS, PKCS will give PKCS response and PKCS Number to the declarant and the form will be routed to FZA.

6.1.8 Further validation will be done automatically by FZA system before the officer can view the form.

6.1.9 If any error is encountered during validation process, FZA system will send out an auto rejection message with a proper error code. Upon receiving the rejection message, the agent must rectify the error and resubmit the form using RESET option at front-end software. (Please refer to Error Code List in the appendix)

6.1.10 Upon successful validation, FZA Officer will view the form and perform an approval process.

6.1.11 The document will be put on hold if supporting document is required and a response message will be sent out with a proper reason for holding. (Please refer to Error Code List in the appendix)

6.1.12 The following are the list of supporting documents required for ZB1 (Export):

Invoice/Packing List.
Copy of B/L.
ZB1 (Import)
K2/K8 Form.
Export Permit if applicable.

6.1.13 The declarant may fax the supporting documents or bring the supporting documents to FZA premises for verification. Any delay of sending supporting document may result in delay for approval of electronic declaration. The declarant is advised to send the supporting document to FZA as soon as possible for an early approval on ZB declaration.

6.1.14 The document declaration will also rejected by officer if the information given is inaccurate of illogical. The reason for rejection will be given out to the user as well. If the reject message requires resubmission, the agent must make the necessary correction and resubmit the form using RESET option at front-end software. (Please refer to Error Code List in the appendix)

6.1.15 No registration number will be given for REJECT or HOLD messages.

6.1.16 Upon successful approval process, a response message will be sent out in ZBACK message with FZA Registration Number.

6.2 AMENDMENT/REPLACEMENT PROCEDURE

6.2.1 The user is allowed to amend his original message and send out replacement message under the following circumstances:

Partial Shut-out Cargo (PS).
Others (OT)

6.2.2 The replacement messages are required only after the user has previously sent out the original form.

6.2.3 Replacement messages are not meant for messages that have been rejected by FZA or PKCS.

6.2.4 The agent will choose the amendment option (5 – Replacement) at the front-end system and amend the necessary field and submit the form to FZA.

6.2.5 PKCS will validate and send out PKCS response and PKCS Number. The PKCS Number will be the same PKCS Number sent out for original messages that were sent out earlier.

6.2.6 PKCS will route the replacement message to FZA for approval processing.

6.2.7 The officer will view the replacement message and approve the message if no error is found.

6.2.8 A response will be sent out to declarant.

6.3 CANCELLATION PROCEDURE

6.3.1 The user is allowed to cancel his original message and send out cancellation message (1 – Cancellation) under the following circumstances:

Total Shutout Cargo (TS)
Others (OT).

6.3.2 The cancellation message is required only after the user has previously sent out the original message and received FZA Registration Number.

6.3.3 The FZA system will acknowledge the receival of cancellation message by sending out the response – cancellation received, to the declarant. FZA system will mark the form as cancelled. (Please refer Error Code list in the appendix)

6.4 OTHERS

6.4.1 Declaration Of Resale Cargo.

In the scenario whereby the consignor sell their cargo to another party, the agent must indicate the transaction as “RESALE OF CARGO” under transaction type “RS” and Resale Invoice must be submitted and indicated in supporting document column.

Under normal circumstances the consignee of ZB1 (Import) will become the consignor of ZB1 (Export). However, in the case of Resale Cargo these consignee and consignor will be of different parties.

The transaction type is very important because the officer will always check the consignee and consignor of ZB1 (Export) against ZB1 (Import) . If no indication of Resale of Cargo provided, the declaration will be rejected because the officer will deem that the party’s information is incorrect.

6.4.2 Re-export of Empty Container

For container coming in as Laden (FCL). After unstuffing in terminal, the empty container may be exported out. In this case a ZB1 (Export) declarations has to be made.

The declarant must use container type “4 – Empty Container” for empty container declaration.

There is no need to declare a ZB1 (Import) in this scenario.

6.4.3 Shut-out or Short-shipped cargo

For partial shutout cargo, the user must send an amendment on the previous declaration on the correct quantity loaded on original vessel. The procedure is the same as amendment procedure in 5.2 (5.2.1-5.2.8) to be reshipped by another vessel.

Declarant must put up a new declaration on cargo/container a shutout if any.

In the case of total shutout, the declarant must send a cancellation messages with “TS – Total Shutout” indicator. The new declaration need to be submitted as brand new application.

6.4.4 Value Added

If the cargo to be declared in ZB1 (Export) have gone through value added/re-packaging activities, declarant must indicate value added in transaction type “VA – Value Added”. The ZB4 must be submitted to FZA as supporting document.

This is important because the system will compare the ZB1 (Import) and ZB1 (Export) quantity and package type and will automatically reject the declaration if there are inconsistencies in those fields unless value added has taken place.

The FZA officer will then manually check the correctness of the quantity and package type declared against the ZB4.

6.4.5 Return Cargo

For return cargo to be re-exported, the declarant/agent shall declare a ZB1 (Import) and a ZB1 (Export).

While declaring the ZB1 (Export), the declarant/agent must indicate in the transaction type “RC – Return Cargo”.

If the transaction type is not indicated the declaration shall be rejected by FZA.

7.0 ZB1 (TRANSSHIPMENT) PROCEDURE

7.1 FZA APPROVAL PROCEDURE

The following are the scenarios by which the agent will put up ZB1 (Transshipment) for their cargo:

Ø Transshipment of Cargo Through Free Commercial Zone.

ZB1 (Transshipment) can be declared as soon as SCN is available and all cargo must be declared before vessel ATD.
The declarant will prepare and submit the form through EDI. The FZA registration/approval number would be used as Booking Reference Number in the ZB1 (Transshipment).
Upon successful validation at PKCS, PKCS will issue PKCS response and PKCS Number to the declarant and the form will be routed to FZA.
Further validation will be done automatically by FZA system before the officer can view the form.
If any error is encountered during validation process, FZA system will send out an auto rejection message with a proper error code. Upon receiving the rejection message, the agent must rectify the error and resubmit the form using RESET option at front-end software. (Please refer to Error Code List in the appendix)
Upon successful validation, FZA Officer will view the form and perform and approval process.
If no error found all ZB1 (Transshipment) forms will be pre-approved by officer without supporting documents unless specified.
The document will be put on hold if supporting document is required and a response messages will be sent out with a proper reason for holding. (Please refer to Error Code list in the appendix)
Officer will also reject the document if the information given is inaccurate or illogical. The reason for rejection will be given out to the user as well. If the reject message requires resubmission, the agent must do the necessary correction and resubmit the form using RESET option at front-end software. (Please refer to Error Code list in the appendix)
No registration number will be given for reject or hold messages.
Upon successful approval process, a response message will be sent out in ZBACK message with FZA Registration Number.

7.2 AMENDMENT/REPLACEMENT PROCEDURE

The user is allowed to amend his original message and send out replacement message under the following circumstances:

Ø Partial Shutout (PS)

Ø Short landed (SL)

Ø Others (OT)

The replacement message is required only after the user has previously sent out the original form and received FZA Registration Number.
Replacement messages are not meant for messages that have been rejected by FZA or PKCS due to error in data fields.
The agent will choose the amendment option (5 – Replacement) at the front-end system and choose a proper reason for amendment in the transaction type and amend the necessary field before submitting the form to FZA.
PKCS will validate and send out PKCS response and PKCS Number. The PKCS Number will be of the same PKCS Number assigned to the original message that was sent out earlier.
PKCS will route the replacement message to FZA for approval processing.
The officer will view the replacement message and approve the message if no error found.
A response will be sent out to declarant.

7.3 CANCELLATION PROCEDURE

The user is allowed to cancel his original message and send out cancellation message (1 – Cancellation) under the following circumstances:

Ø Total Shutout (TS)

Ø Others (OT)

The cancellation messages are required only after the user has previously sent out the original message and message is still valid.
The FZA system will acknowledge the receival of cancellation message by sending out the response – cancellation received, to the declarant. FZA system will mark the form as cancelled. (Please refer to Error Code list in the appendix) Any approval given earlier is now considered void.

7.4 OTHERS

7.4.1 Overlanded

In the scenario whereby the cargo was overlanded, the agent must indicate the transaction type as “FT – Overlanded.

7.5 HIGHLIGHT ON THE PREPARATION OF ZB1 (TRANSSHIPMENT)

7.5.1 How to input Consignee and Consignor information:

The Consignee and Consignor fields for single BL shipment and LCL Cargo must be completed. In the case of direct transshipment to one port of destination with various consignors and consignees the declarant would insert “AS PER MANIFEST” in these fields.

However, the declarant should add port of export and port of destination in consignor and consignee fields after “AS PER MANIFEST”.

7.5.2 How to input Container Information:

If cargo type is containerised, select “2 – CONTAINER”

Select “YES” at Containerised Cargo Field to type container numbers, hit <esc> twice to save and exit.

Should you decide to type only the container quantity, select “NO” at Containerised Cargo fields in order to move the cursor to Container Summary field, select “YES” to get in.

The summary of Container field displays the title, “<Total of Container>”

TOTAL CT      SIZE                            TYPE

      9999          <F1>                           <F1>

                        shows                           shows

            20FT 40FT 45FT;    4-Empty, 5-Full, 7-Less Load

   Example: For 100 20FT FCL

      Type “100” at TOTAL CT, press <F1> and select “20FT” at SIZE, press <F1> and select “5-Full” at TYPE, hit <ESC> to exit.

The Containerised Cargo and Summary of Container fields are mutually exclusively, you may type the container number and saved it, set to “NO” and move cursor to summary of Container Number field, set to “YES” and key in the quantity.

8.0 ZB4 PROCEDURE

8.1 FZA APPROVAL PROCEDURE

8.1.1 ZB4 must be declared for all value adding activities taking place in the Free Commercial Zone, Port Klang.

8.1.2 Value adding activities can presently be carried out within FCZ such as at;

v Northport Distripark (NDSB)

v Westport Distripark (WPDP)

v Diperdana Distripark

v Northport

v Westports

v Southpoint

8.1.3 Categories of value-adding activities:

8.1.3.1 Under normal circumstances (require FZA approval only):-

v Break Bulking

v Grading

v Packaging/Repackaging

v Labeling/Relabelling

v Repair of goods in storage or transit

v Trading

8.1.3.2 More elaborate value adding activities that require prior approval and permit number from FZA before declaring ZB4. The minor activities are :

v Dismantling

v Painting

v Coupling

v Reprocessing works

v Minor Assembly

8.1.4 The declarant shall prepare and submit the form through EDI via PKCS.

8.1.5 For sea mode transaction (Transport Mode – 1 Sea ) at ZB4 must be accompanied by the corresponding ZB1 (Import) approved form. The declarant must quote the PKCS ID Number or the ZB1 (Import) registration number in the ZB4 declaration. The FZA system will validate and check the existence of ZB1 (Import) .

8.1.6 For road mode transaction ( Transport Mode – 8 Re-export via Free Zone), the declarant must indicate K2/K8 ref. no. in the ZB4.

8.1.7 For any activity that requires approval as described in section 8.1.3.2, the permit number must be quoted in the declaration. This permit number is issued by FZA. The declarant must apply to FZA prior to submission of such declarations for the issuance of the permit number.

8.1.8 Upon successful validation at PKCS, PKCS will give PKCS response in the form of a PKCS Number to the declarant and the ZB4 form will be routed to FZA, warehouse operator (and activity doer where possible if EDI Number of activity doer is quoted).

8.1.9 Further validation will be done automatically by FZA system before the officer approves the declaration.

8.1.10 If any errors are encountered during the validation process, the FZA system will send out an auto rejection message with a proper error code. Upon receiving the rejection message, the declarant must rectify the error and resubmit the form. The front-end software may require a new job number for resubmission. Upon successful validation, the FZA Officer will process the declaration and perform an approval process.

8.1.11 If no errors are found, the officer will approve the ZB4 declaration. The officer may also reject the document if the information given is inaccurate. The reason for rejection will be given to the declarant and relevant parties as well. The declarant must rectify the error and resubmit the declaration.

8.1.12 No Registration Number will be given for rejected or on-hold messages. Upon successful approval process, a response message will be sent in a ZBACK message with FZA Registration Number to the declarant, warehouse operator and activity doer.

8.1.13 Parties that are required in the electronic ZB4 submission:

8.1.13.1 Declaring Agent

The name of the declaring agent will be automatically generated by the front-end software. This is a mandatory field. Declaring Agents may be importers or their agents.

8.1.13.2 Applicant

An applicant is the party who is applying to the FZA for permission to carry out value adding activities. This is a mandatory field.

8.1.13.3 Activity Doer

An Activity Doer is the party who will carry out the value adding activities on behalf of the applicant. This is a mandatory field. The Activity Doer shall be located within the Free Commercial Zone area.

8.1.13.4 Notify Party

The Notify Party is the party that may require to be informed of the value adding activity. This is an optional field. An example would be the case of a 3^rd party to whom these value-added goods may be sold to. Presently declarants enter the 3^rd party as a “Sold To” entry the manual system.

8.2 AMENDMENT/REPLACEMENT PROCEDURE

This procedure is not available in the ZB4 system

8.3 CANCELLATION PROCEDURE

8.3.1 The declarant is allowed to cancel his original message and send out cancellation message for such situations that are allowed by the FZA authority.

8.3.2 The declarant will choose the cancellation option (1 – Cancellation) at the front-end system and choose code :OT – Others for cancellation in the transaction type and amend the necessary field before submitting the form to FZA.

8.3.3 The cancellation procedure is only allowed for declarations that were previously sent out as original message and had received FZA Registration Number.

8.3.4 The FZA system will acknowledge the cancellation message by sending out the response – cancellation received, to the declarant, warehouse operator and activity doer.

8.3.5 The FZA system will mark the form as cancelled. Further actions to the message will not be accepted.

9.0 FALLBACK PROCEDURE

The authority has established that the average turn around time for ZB is 2 hours.

If the system is down for 4 hours the manual fallback procedure will take into

effect immediately.

9.1 FZA SYSTEM DOWN

The following are the fallback procedures if FZA System is down:

FZA Officer must inform CARELINE of the breakdown so that the CARELINE can disseminate the information to all parties.
Users will key in the declaration inside their system but do not transmit the form to Dagang*Net. The transaction type for this form is ML. For those who are using KEDAI EDI service they must get KEDAI EDI to key in their declaration and print the declaration on the gazette form.
Bring the form and proper supporting document to FZA for approval.
FZA Registration Number will be manually issued upon approval.
The moment the FZA System is up and running the user must transmit the form through EDI with transaction type ML.
The manual form will carry the identifier “ML” and system will generate the temporary registration number until the FZA officer overrides the temporary registration number that has been given to the user earlier during manual submission.

9.2 PKCS SYSTEM DOWN

The following are the fallback procedure when PKCS is down:

Likewise the person who is in-charge of PKCS will inform CARELINE of the breakdown so that CARELINE can disseminate the information to others.
Users will key in the declaration inside their system but do not transmit the form to DAGANG*Net. The transaction type for this form is ML. For those who are using KEDAI EDI service they must get KEDAI EDI to key in their declaration and print the declaration on the gazette form.
Bring the form and proper supporting document to FZA for approval.
FZA Registration Number will be manually issued upon approval
The moment the PKCS System is up and running the user must transmit the form through EDI with transaction type ML.
The manual form will carry an identifier “ML” and system will generate the temporary registration number until the FZA Officer overrides the temporary registration number with the manual registration number that has been given to the user earlier during manual submission.

9.3 USER SYSTEM DOWN

The following are the fallback procedure when User front-end system is down:

User will come to KEDAI EDI and get KEDAI EDI to key in their declaration Users must bring the proper supporting documents to Kedai for referral.
KEDAI EDI will transmit the form as normal and will inform the user of the responses received from PKCS and FZA.

9.4 KEDAI SYSTEM DOWN

The following are the fallback procedure when KEDAI-EDI system is down:

KEDAI EDI will inform CARELINE of the breakdown and CARELINE will subsequently inform all parties e.g. Associations, Port Operators.
User will manually type in the information onto gazetted form and bring to KEDAI EDI to get endorsement from KEDAI. A copy of the document will be given to KEDAI EDI.
Bring the form and proper supporting documents to FZA for approval.
FZA Registration Number will be manually issued upon approval.
Once KEDAI system is up and running, KEDAI EDI will key in the form and submit the form through EDI. The transaction type for this form is “ML” – manual submission.
The manual form will carry an identifier “ML” and system will generate the temporary registration number until the FZA officer overrides the temporary registration number with the manual registration number that has been given to the user earlier during manual submission.
It is important to transmit the form because FZA officer will subsequently update all the manually issued Registration Number into the system. Thus if the form is not transmitted the agent will be queried by FZA.

10.0 SUPPORT SERVICES

10.1 CARELINE’S SUPPORT

DNT Sdn. Bhd operates an on-line help-desk known as CARELINE. This help-desk will be able to assist users to track message and disseminate information in case of breakdowns at PKCS and Free Zone.

CARELINE’s operational hours

Works 24 hours everyday

CARELINE can be contacted at the following numbers:

Operational Hours:

Tel. No. : 03-2781 3030

Fax No. : 03-2781 3003

Email : * careline@dagangnet.com

Support personnel will log all calls to CARELINE and a log number will be issued to the caller. This log number will be required should the caller need follow-up action.

All callers need to provide the following information to enable CARELINE to assist:

1. Caller’s EDI Number.

2. Interchange Reference Number.

3. PKCS ID

4. Job Number.

5. Agent code.

10.2 RANK ALPHA HELP DESK

Any failures of the front-end software must be reported to Rank Alpha Technologies Sdn. Bhd. Rank Alpha can be contacted at its help-desk at the following numbers:

Tel. No. 03-80709898 Fax. No. 03-80762010

10.3 FREE ZONE SUPPORT

DNT’s CARELINE and the Rank Alpha Support Desk will handle all support on electronic transmissions. However should user have any queries pertaining to business procedures, they can call the Free Zone Authority at the following numbers:

Free Zone Manager

En. Ahmad Rizal Mohd Yusop

Tel. No. : 03-3167 0024

Free Zone Officers – 03-3168 8211

En. Mohd Shah Nas ext 1007

Cik Siti Fazila ext 1006

En. Mohd Nizam ext 1005

Free Zone Counter ext 1017 / 1016 / 03-3167 1262

APPENDIX I – LIST OF CODES

1.0 LIST OF RESPONSE CODES AND ERROR CODES

1.1 LIST OF APPROVAL CODE (ZBACK)

CODE	DESCRIPTION	REMARKS
44	Approved by FZA

1.2 LIST OF ERROR CODES(ZBERR) – VALIDITY CHECK

CODE	DESCRIPTION	REMARKS
V01	Port Of Loading Invalid