SAP Transportation Management, order to cash for container shipping liners provides numerous functionalities that dedicated to help ocean liners to run their business better. In this blog series, you will learn how to use manifest document to ease the documentation work.
Note that the following information is only for demonstration purpose.
System use it for localization & translation purpose. You may configure the key information as Translatable in IMG: Manifest -> Maintain Manifest Settings -> Key Elements.
System use it for localization and conversion purpose. You may configure the key information as well as conversion rule in IMG: Manifest -> Maintain Manifest Settings -> Key Elements, and Unit of Measure.
The party role options come from the BP role group that is assigned to IMG: Manifest -> Maintain Manifest Settings -> General Settings -> Role Grouping.
You may configure the role group in IMG: Manifest -> Define BP Role Groupings.
You can define the number ranges in IMG: Manifest -> Define Number Ranges for Manifest Profile Documents;
And use it in IMG: Manifest -> Maintain Manifest Settings -> General Settings -> Doc. ID No Internal.
They are configured in IMG: Manifest -> Maintain Manifest Settings -> Document Types.
The customizing table has further characters such as relevant cargo activities (Load/Discharge/Release), activity direction (Inbound/Outbound) and preferred reference validity (ETA/ETD).
They are configured in IMG: Manifest -> Maintain Manifest Settings -> Event References. This is where you control how the document instances are generated at runtime.
Together with Reference Validity system determines relevant documents for each port call.
You can use ETA or ETD of a port call as the time base when determining relevant documents.
After you maintained everything you can set the status to Final so that the document will take effect.
The document items will be consumed by voyages (ocean freight booking) at time of voyage generation; The Document Usage will give you a full list of consumer voyages.
Maintain the communication settings
IMG: Manifest -> Maintain Manifest Settings -> Communication Method; Each should have an ABAP class implementation, which handles all the communication work.
If your communication method requires a printed version, you need to create a PDF form of interface /TMCSL/MAN_SBM_EXAMPLE_IF; The interface is maintained in IMG: Manifest -> Maintain Manifest Settings -> Manifest Settings - Interface. The layout should match with format.
You can maintain EDI format in IMG: Manifest -> Maintain Manifest Settings -> EDI format.
In case B/L changed after document submission, how do you want to handle the amendment.
The prerequisites for document instance generation; and
The rules for including Bookings and B/Ls into the document.
• Advance Document Prerequisites
It is only changeable for which the document activity is Advanced, see Advance Manifest; For other document types, it is Always. The generation still depends on the class implementation, see Event Reference customizing.
• Call Type Relevance
Choose the relevant type of port call, so that document instances are only generated at designated type of port call. Omitting this selection will be treated as relevant to any call type.
• Whether this document should include booking or B/L data
Some document may not need booking or B/L data at all, while others may need them as essential data; use the House B/L option to include House B/L as standard alone entry.
• What kind of booking or B/L
There are different types of trigger you can choose from:
◊ Port Activity
What activity performed to the booking or B/L at this port correspond to what role that this port plays in the booking or B/L; Load - Port of Loading, Unload - Port of Discharge. By giving port activity as a trigger rule, you can filter out the booking or B/L that does not have desired actions.
◊ Method
Name of the class that has interface /TMCSL/IF_MANPRF_TRIGGER; You have to implement your filtering logic inside.
◊ Configured Trigger Type
Any trigger type defined in IMG: Manifest -> Maintain Manifest Settings -> Trigger Types.
• Activity to Be Scheduled
The Activities you configured in IMG: IMG: Manifest -> Maintain Manifest Settings -> Activities are shown in dropdown list; The customizing only define a few properties like Description, Type and Level (at what entity the action will be performed).
• Event Type
The activity scheduled execution time can be determined by:
◊ Event - The time of one of following event (ETA/ETD/ATA/ATD) + Offset; Or
◊ Anther Activity - The scheduled time of another activity + Offset; Or
◊ PPF Condition - Determined by start condition of PPF action.
• Auto/Manual - Is the activity executable by user manually or by system automatically or both.
• Sea Duration - Shortsea or Deepsea; see Shortsea/Deepsea.
• Event - Only available for type Event.
• Previous Activity - Only available for type Activity .
• Time Offset - The offset for calculating scheduled time; for example -72 Hours or +1 Days.
• PPF Action - The actual business logic is implemented in PPF action; The PPF action profile and action definitions should be configured and enabled for Business Object /SCMTMS/TOR Node /TMCSL/MAN_DOC in IMG: Manifest -> Maintain Output Management Adapter Settings.
Note: SAP provides PPF output agent /TMCSL/MANIFEST as a basic setup with limited functionality, you may create your own and replace it.
First you need to maintain the attributes in IMG: Manifest -> Maintain Manifest Settings -> Key Elements as translatable or convertible; then you can add them here, with a target Language or Unit. If you don's specify any Language or Unit, system will take the manifest profile header value as fallback.
First you need to maintain the validations in IMG: Manifest -> Maintain Manifest Settings -> Validations, assign validation level (against what entity it checks at), as well as implement the ABAP class.
The cleanup activity will be scheduled like any other activity; During execution, it will perform the validations maintained here and set status to corresponding entity according to severity level:
Order to cash provides a fixed set of response actions, they can cover scenarios like submission feedback, cargo operations and document diversion. SAP also provides API to consume response code.
You need to implement the communication between SAP system and third-party system, with the help of API.
You can put three different types of amendments:
• Port Activity
• Method
• Any attributes maintained in IMG: Manifest -> Maintain Manifest Settings -> Key Elements as Amendment.
Manifest Document Part 3 – Advance Manifest
Manifest Document Part 4 – Shortsea/Deepsea
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
8 | |
4 | |
4 | |
4 | |
3 | |
3 | |
3 | |
2 | |
2 | |
2 |