N4 supports Saudi Load permit order message as per specification document version 3.0 received from Red Sea Gateway Terminals(RSGT) since the feature is primarily developed for RSGT. A new message class "SAUDILDP" has been added in N4 to configure load permit message.
Saudi Load Permit Order is a Flatfile EDI transferred from Shipping Agents to Terminals in Saudi region. Basically, it contains the list of containers to be loaded on particular outbound vessel, especially for Transship containers. Load permit order contains list of BLs, Bl Items, Containers, and Load permission section. It is assumed that all the BLs, BL Items & containers in load permit order message are already created by another message called Saudi Manifest.
Shipping Agent advises the terminal the list of Transship containers to be loaded from an incoming vessel to an another outgoing vessel. N4 grants a permission to those containers referred in load permit order and terminal can/will load only those containers.
A Saudi Load Permit Order may contain following information in same order:
Load Permit Manifest Header - Contains outbound vessel visit & etc.
Replacement Containers
Reference Import Manifest Header
Reference Import Manifest containers
Reference Import Manifest BL & Bl Items
Load Permit Header & Items
This guideline document specifies on how Saudi Load Permit Order EDI message is implemented and how N4 can be configured to process this particular message.
SAUDILDP Inbound Supported Segments
In Replacement Container segment (SAULDPD200), though we have separate message function (N-New/U-Update/D-Delete), in N4 its always assumed as U-update.
The sequence number in Replacement Container segment (SAULDPD200) is not recorded/processed.
All BL, BL containers & Bl items are updated as per Load permit order. Basically the information from Saudi manifest will be overwritten.
SAUDILDP Inbound - Message Functions
Saudi LDP has message function (N-New/U-Update/D-Delete) in following segments:
Replacement container segment - SAULDPD200
Load Permit & Items - SAULDPD400, SAULDPD450
But, in principal as the message meant grant load permission which is received in SAULDPD400 & SAULDPD450 segments, N4 obeys only the message function in SAULDPD450 (this in turn takes care of SAULDPD400 as well).
SAULDPD400(N) - To grant permission to a container.
SAULDPD400(U) - Update other information related to load permit - load permit date etc.
SAULDPD400(D) - Revoke the existing load permission.
Custom Map for Saudi LDP Inbound
Since Saudi LDP is a flat file, it cannot be processed as such in N4. So a new Xml schema (saudildp.xsd) has been defined for SAUDILDP message class and flat file load permit message has to be converted to this particular xml structure.
For this, a new OpenText Output Transformation (formerly Xenos) map(saudildp_30.mgt) has been developed to transform the load permit flat file to N4 standard xml format during runtime.
Note: The custom map is not a built-in map, which means there won’t be a Message Type (in Message Types UI) in N4 with this map & message class SAUDILDP. Customers who want to use Saudi LDP need to get the latest map from PS and maintain it themselves if any customization is done.
Special Cases
Entity Type
As Saudi LDP contains information various entities, such as BL, BL Item & Container etc, a separate attribute is present in Navis standard xml (saudildp.xsd) to specify the type of entity to be processed in N4.
Possible values for entity type field are: REPLACEMENTCTR, BLCTR, BL, BLITEM, LOADPERMIT & LOADPERMITITEM.
This attribute is used for following purpose:
to control the code flow
to validate the integrity of the transformed xml - for example, if entity type is BL the transformed xml should contain BL information.
to resolve the keywords for specific to an entity
Sequence Numbers
Since Saudi LDP is a flat file EDI, it has sequence numbers at each segment level and is used to refer in further update messages for the same entity and same message. The sequence numbers are unique in a particular message but not across messages. So to make it unique across messages, in N4, in addition to sequence number of a particular entity, some more information such as manifest number and date are used as well.
In N4, once the Load permit flat file is transformed to Navis standard xml, the sequence number of various entity will be concatenation of many values.
Hard Coded EDI Trading Partner
In N4, to process an inbound EDI, an EDI Session needs to be created which in turn needs a EDI Trading Partner. According to ANSI & EDIFACT standards, the EDI Trading partner refers to the sender of the EDI message. But the Saudi LDP flat file does not have such information at all.
So, as of now, for the Saudi LDP developed for Saudi EDI, the EDI trading partner name is hard coded as "SAUDIEDI". Customers that want to use a different partner name, the OpenText Output Transformation (formerly Xenos) map (saudildp.mgt) has to be customized with required partner name.
Implication of Posting a Saudi LDP Inbound in N4
Though Saudi LDP message is primarily meant to grant permission for a container, it contains additional information about the BL, BL Item and containers received in Import Manifest. Import Manifest creates all the BL, BL Item and containers with proper sequence numbers. So when a Saudi LDP is posted, all those entities using the same sequence number as marked as received.
Following are the implications of posting a Saudi LDP:
BLs, Bl Items and Containers are updated as received in Saudi LDP.
In addition to the information received in Container segments (SAULDPD200 & SAULDPD310), there is some information in Load Permit segment SAULDPD400 and other noteable updates to the Unit are as follows:
Load Permit Number
Load Permit Date
Category changed as TRANSSHIP
Outbound Visit information are change to the Export vessel visit information from Saudi LDP header.
Load Permission is GRANTED.
In N4, Load Permit Number and Date are named as Export Release Number and Export Release Date respectively. It can be view in the "Units" UI by selecting those fields from the fields group "9-Other". The Export Release Number is also available in Filter options.
The Export Release Number and Date are also made as Reportable fields and can be part of a report generated based on Unit entity.
Saudi LDP Inbound with Replacement Container
Saudi LDP has a separate section called 'Replacement container' which means that the original container in a given BL Item should be replaced with the container specified in this section.
When a Saudi LDP with Replacement Container is posted in N4, following are the implications:
Load Permission is CANCELLED for the Original container, if it's GRANTED already.
Load Permit Number, Date and Load permit sequence number information is removed from the Unit.
Container is detached from the BL Item.
If the same container is not attached with any other BL Items in the same BL, then the container is removed from the BL itself. This means the Unit no longer displays in the Units sub-panel of the BL Inspector.
Replacement container is attached to the BL Item & BL.
Load Permission is GRANTED and Load permission information are updated to it.
Saudi LDP with load permit segments of DELETE message function means to revoke the Load permission.
Implications in N4 are:
Load Permission is CANCELLED for the Unit.
Load Permit Number, Date and Load permit sequence number information are removed from the Unit.
Saudi LDP Inbound For Dray-In Container
In general, Saudi LDP contains information about Containers recieved in Import Manifest. But sometimes it might contain Containers that are not received in Import Manifest at all. In N4 those containers handled as Dray-In containers.
In this case, the BL might not exist in the system, but the container must exist. Container might not have the manifest sequence number since it's not part of import manifest.
Following are the implications:
BL and BL items are created and updated with sequence numbers from Saudi LDP.
Container is attached to BL & load permission is GRANTED.
Load permit Nbr, Date and container sequence numbers are updated.
Saudi LDP Inbound "Single Unit - multiple cargo"
There are situations when a container has multiple cargo of the same BL or different BLs, since in the N4 model, a container can be linked to multiple Cargo Lots. In these cases, the container will be granted with load permission only if the load permit is received for all the BL items, in N4 terms, for all the Cargo lots. To keep track of this, Cargo Lots are updated with the Load permit number as and when the load permit is received for each BL item.
The Load permit number is displayed in Cargo Lot table view under BL Item inspector.
Till the load permit is received for the last BL item of a container, N4 keeps adding a warning to all the EDI Batches while processing the load permit. The warning reports that the container is not granted with load permission since there are more BL items for which load permit is not yet received.
How to Configure N4 for Saudi LDP Inbound?
To process Saudi LDP, the following set up needs to be done:
Message Type should be created with Message Class as "SAUDILDP" and Standard as "FLATFILE".
A Message map should be created under the message type direction as Receive, import the map file "saudildp_30.mgt" and dictionary file "saudildp.fxd".
In Holds/Permissions UI, add a flag type with "Applies To" as Unit, Type as Permission.
Under Settings UI, select the config "SAUDI_LOAD_PERMIT_PERMISSION - ARGOSAUDILDP001-Id of Permission(s) to apply for Saudi Load Permit Order to set the ID(s) for the Permission created above. These can be comma separated values.
In the EDI Configuration UI, create a EDI Trading Partner with an ID similar to the partner hardcoded in the map.
Create an EDI Mailbox with direction as Receive.
Create an EDI Session with the following attributes:
Message Class - SAUDILDP
Direction - Receive
Map - Select Map ID as created under Message Type
N4 has a way of validating some business conditions which might be applicable for some clients and not for others. Therefore, those validations are configurable, so that the user may turn them on or off as needed.
The following table lists such configurable settings applicable for SAUDILDP message:
|
Name |
Description |
Edit UI |
Usage |
|---|---|---|---|
|
|
|
|
SAULDPH100~N~1~1~20090908000001~20090908~EXP196657~ KOTA GUNAWAN~ ~ AE~LL196657~OB196657~SAJED~1~3
SAULDPD300~1~20090908000001~IMP196657~20090908~SAJED~0~11~IB196657~LL197657~MSC GUNAWAN~~20040807132300~20040818173000~428~321
SAULDPD310~108~111~301~DRY~~45~KRKW 1966574~1~1900~9900~~~~~~~
SAULDPD320~210~1~BL196657~KRK196657~SSA~428~USOAK~SAJED~1~SGSIN~~~1~8080~50~1~1~General Remarks~
SAULDPD330~1~108~50~PK~8080~~5~2~0~2~Highly explosive chemicals~Highly explosive chemicals~marks no.711~~~
SAULDPD400~N~LP196657~20060612~428~321~SGSIN~1~SG~2
SAULDPD450~N~1~20090908000002~IMP196657~1~20090908~210~BL196657~1~~~
Saudi Load Permit Order - Replacement Container
SAULDPH100~N~1~1~20090908000001~20090908~EXP196657~ KOTA GUNAWAN~~ AE~LL196657~OB196657~SAJED~1~3
SAULDPD200~N~300~111~301~DRY~~45~BLJU 2345992~7~1900~9900~0~~~~~
SAULDPD300~1~20090908000001~IMP196657~20090908~SAJED~0~11~IB196657~LL197657~MSC GUNAWAN~~20040807132300~20040818173000~428~321
SAULDPD310~108~111~301~DRY~~45~KRKW 1966574~1~1900~9900~~~~~~~
SAULDPD320~210~1~BL196657~KRK196657~SSA~428~USOAK~SAJED~1~SGSIN~~~1~8080~50~1~1~General Remarks~
SAULDPD330~1~108~50~PK~8080~~5~2~0~2~Highly explosive chemicals~Highly explosive chemicals~marks no.711~~~
SAULDPD400~N~LP196657~20060612~428~321~SGSIN~1~SG~2
SAULDPD450~N~1~20090908000002~IMP196657~1~20090908~210~BL196657~1~~BLJU 2345992~
Saudi Load Permit Order - DELETE
SAULDPH100~N~1~1~20090908000001~20090908~EXP196657~ KOTA GUNAWAN~~ AE~LL196657~OB196657~SAJED~1~3
SAULDPD400~D~LP196657~20060612~428~321~SGSIN~1~SG~2
SAULDPD450~D~1~20090908000002~IMP196657~1~20090908~210~BL196657~1~~~
Saudi Load Permit Order - Multiple Import Reference Manifest
SAULDPH100~N~1~1~20090908000001~20090908~EXP196657~ KOTA GUNAWAN~~ AE~LL196657~OB196657~SAJED~1~3
SAULDPD300~1~20090908000001~IMP196657~20090908~SAJED~0~11~IB196657~LL197657~MSC GUNAWAN~20040807132300~20040818173000~428~321
SAULDPD310~108~111~301~DRY~45~KRKW 1966574~1~1900~9900~~~~~~~
SAULDPD320~210~1~BL196657~KRK196657~SSA~428~USOAK~SAJED~1~SGSIN~~~1~8080~50~1~1~General Remarks~
SAULDPD330~1~108~50~PK~8080~~5~2~0~2~Highly explosive chemicals~Highly explosive chemicals~marks no.711~~~
SAULDPD300~1~20090908000001~IMP296657~20090908~SAJED~0~11~IB296657~LL297657~MSC GUNAWAN~20040807132300~20040818173000~428~321
SAULDPD310~208~111~301~DRY~45~KRKW 2966574~1~1900~9900~~~~~~~
SAULDPD320~310~1~BL296657~KRK196657~SSA~428~USOAK~SAJED~1~SGSIN~~~1~8080~50~1~1~General Remarks~
SAULDPD330~1~208~50~PK~8080~~5~2~0~2~Highly explosive chemicals~Highly explosive chemicals~marks no.711~~~
SAULDPD400~N~LP196657~20060612~428~321~SGSIN~1~SG~2
SAULDPD450~N~1~20090908000002~IMP196657~1~20090908~210~BL196657~1~~~
SAULDPD450~N~1~20090908000002~IMP296657~1~20090908~310~BL296657~1~~~