CPu variables overview
Notification variables
In this table you can find all CPu variables used in the notifications and their explanation.
Variable in notification | Explanation | Can be NULL if no information was provided | |
|---|---|---|---|
| 1 |
| APCS code (unique identifier on C-point) of the relevant party indicated by the […]. This can be:
|
|
| 2 |
| DUNS number (https://www.dnb.com/duns-number.html ) of the relevant party indicated by the […]. This can be:
| X |
| 3 |
| EORI number of the relevant party indicated by the […]. This can be:
| X |
| 4 |
| NxtEntityId (or NxtPort ID) of the relevant party indicated by the […]. This can be:
|
|
| 5 |
| TIN (Tax Identification Number) number of the relevant party indicated by the […]. This can be:
For EU countries this is the VAT number as validated through the EU VIES https://ec.europa.eu/taxation_customs/vies/ . |
|
| 6 |
| Registered company name of the relevant party indicated by the […]. This can be:
|
|
| 7 |
| Masked (for privacy & security reasons) Alfapass number of the driver assigned for pick up. e.g. | X |
| 8 |
| Transport document (B/L or SWB) number of the shipment(s) inside the container. |
|
| 9 |
| Alias of the driver assigned for pick up. | X |
| 10 |
| Empty return reference of the container. Not fully implemented in CPu yet. Be sure to ask Shipping Agent if they provide this info. | X |
| 11 |
| Container number. |
|
| 12 |
| Container operator. | X |
| 13 |
|
|
|
| 14 |
| Container owner. | X |
| 15 |
| ISO type of container (e.g. or |
|
| 16 |
|
|
|
| 17 |
| Value & color of the Green Light. See the Green Light table below for all possible combinations and their meaning. | |
| 18 |
| ||
| 19 |
|
|
|
| 20 |
| ISO 8601 timestamp (in UTC) e.g. |
|
| 21 |
| GUID generated by the NxtPort platform to identify the notification. Is equal to the |
|
| 22 |
| UN/Locode of the operational port. For now, this is always Antwerp BEANR. |
|
| 23 |
| Identification code you provided in the original request. |
|
| 24 |
| NxtEntityId (or NxtPort ID) you provided in the original request. |
|
| 25 |
| Reference provided by the Shipping Agent to identify the Commercial Release | X |
| 26 |
| NxtPort standard terminal code (“0” + quay number e.g. |
|
| 27 |
| Identifier provided by the submitting Shipping Agent. Is used together with the equipment number and bl number(s) to uniquely identify a Release Right. |
|
| 28 |
| Self-explanatory. | X |
| 29 |
| Self-explanatory. | X |
| 30 |
| Self-explanatory. | X |
| 31 |
| The External Reference Id submitted as request header in the original request. | X |
| 32 |
| NxtEntityId (or NxtPort ID) of your company, i.e. the company which has received the notification. |
|
| 33 |
| Free text provided by the party which triggered the event. | X |
Green Light table
In this table you can find all combinations of the Green Light name, value & color and their meaning.
Green Light | “greenLightName” | “greenLightValue” | “greenLightColor” | Explanation | |
|---|---|---|---|---|---|
| 1 | Commercial Release |
|
|
| Container has been commercially released. |
| 2 | Commercial Release |
|
|
| Container has been commercially blocked. |
| 3 | Commercial Release |
|
|
| No commercial release information received yet. |
| 4 | Commercial Release |
|
|
| Container has been commercially blocked. |
| 5 | Commercial Release |
|
|
| Commercial release has expired:
|
| 6 | Terminal Discharge |
|
|
| No information on discharge status yet received. |
| 7 | Terminal Discharge |
|
|
| Container is still on board of vessel. |
| 8 | Terminal Discharge |
|
|
| Container has been discharged from vessel (import). |
| 9 | Terminal Discharge |
|
|
| Terminal operator has canceled previous load message. |
| 10 | Terminal Discharge |
|
|
| Terminal operator has canceled previous discharge message. |
| 11 | Terminal Discharge |
|
|
| Container has arrived on terminal (transhipment). |
| 12 | Terminal Release |
|
|
| No information on release status yet received. |
| 13 | Terminal Release |
|
|
| Container has been selected for scan by Terminal Operator. Scanning procedure must be followed. |
| 14 | Terminal Release |
|
|
| Container has been blocked on terminal by Terminal Operator. |
| 15 | Terminal Release |
|
|
| Container has been released on terminal by Terminal Operator. |
| 16 | Terminal Release |
|
|
| Release Right has been archived, meaning:
|
| 17 | Customs Light |
|
|
| No release information received yet. |
| 18 | Customs Light |
|
|
| Container has been selected for scanning by competent customs authority. Scanning procedure must be followed. |
| 19 | Customs Light |
|
|
| Container has been released by competent customs authority. |
| 20 | Customs Light |
|
|
| Container can be released under transhipment |
| 21 | Customs Light |
|
|
| Container can be released under port equalisation |
| 22 | Customs Light |
|
|
| Container can be released under FAVV |
| 23 | Customs Light |
|
|
| Container is subject to documentary control |
| 24 | Customs Progress |
|
|
| No information received from customs |
| 25 | Customs Progress |
|
|
| At least 1 item of at least 1 BL is fully cleared |
| 26 | Gate Operation |
|
|
| Container has not left the terminal yet according to Terminal Operator. |
| 27 | Gate Operation |
|
|
| Container has left the terminal according to Terminal Operator. |
| 28 | Gate Operation |
|
|
| Terminal operator has canceled previous gate out message. |
| 29 | Gate Operation |
|
|
| Terminal operator has canceled previous gate in message. |
| 30 | Pick up |
|
|
| No Pick up Right has been generated yet for the container. |
| 31 | Pick up |
|
|
| Pick up Right has been generated, i.e. a driver has been assigned. |
| 32 | Pick up |
|
|
| The assignment of a driver has been revoked, awaiting new assignment. |
Related pages
Need any further assistance?
