Settings for Transportation Execution Interface (TEI)

This document explains how you define the settings for the Transportation Execution Interface (TEI) function.

TEI provides an interface where transportation and customs information can be exchanged with third-party best of breed applications or external partners using B2B messaging.

Outcome

The following settings for TEI are defined:

The primary goal of M3 TEI is to provide M3 customers with the capability to use third-party Transportation Execution Systems (TES) that manage the following:

For more details, refer to M3 Business Engine Administrator's Guide for Transportation Execution Interface (TEI).

Before you start

Follow these steps

Define basic settings for dispatch flow

  1. Start 'Dispatch Policy. Open' (MWS010). Select auto level 3 (Issue made automatically when picking list reported) for the TEI dispatch policy.

  2. 'Ship-via control' (MWS010/H) indicates if the ship-via address is retrieved automatically and how it is retrieved. The ship-via address is the address the goods are transported through before they arrive at the final address.

    0 = No ship-via address is retrieved automatically when the delivery is created. The ship-via address is maintained manually from 'Delivery. Open Toolbox' (MWS410/F).

    1 = The address is retrieved automatically from the consignee. Either the customer delivery address (OIS002) or the customer (CRS610) is used to propose the ship-via address. Applies only to order category 3 (customer order).

    2 = The address is retrieved automatically from the route. The place of unloading that is connected to the delivery (MWS410) and route (DRS021) is used to propose the ship-via address.

    3 = The address is retrieved automatically from the generic object control. The ship-via address in (CMS016), (CMS017) and (MWS190) is used to propose the ship-via address.

Generate documents and connect documents to partner reference objects

  1. Start 'M3 Document. Open' (CRS928). Press F14= 'Gen standard' to generate all standard documents (for TEI it is document 915 00).

    (CRS928) is a global program involving all companies in M3.

  2. Select document 915 00 and select option 12=Partner reference object. This starts 'Standard Document. Connect Partner Ref Obj' (CRS947). On the E panel you define partner reference settings for this document.

  3. Display (CRS928) again, and select F15= Generate all. This will generate all settings in (CRS928) and (CRS947) for each document.

  4. You can also create variants for document 915 in (CR928) and define partner reference settings for the variants in (CRS947).

    Example:

    Variant 10 sends package information to the external system when the pick list is printed. Variant 20 sends transportation information to the external system when the outbound delivery is reported.

    Because it is two different document variant in this example, the external system will know which information every transfer ID contains.

Generate documents per company

Start 'Standard Document. Open' (CRS027). Press F14='Gen standard' to generate all standard documents for the particular company you are working in.

Define number series for TEI transfer

Start 'Number Series. Open' (CRS165). The following series types are valid for TEI:

Connect document to TEI partner and define settings for TEI partner

  1. Start 'TEI Partner. Open' (MYS015). Define the settings for each partner and document variant. You can define several variants for each partner. Fill in appropriate fields on the E panel.

  2. Start 'Std Document. Connect Media Control Object' (CRS945). You can connect documents to partner for a specific division or for the entire company. The settings for the partner in (MYS015) will also be valid for the connection you make here.

Create object control table for documents/event

  1. Start 'Available Object Control Parameters. Open' (CMS016). Select SCE Event Document and select option 11=Object table detailed lines.

  2. 'Generic Object Control Table. Open' (CMS017/B) is started.

    Set the 'Panel sequence' field to E (T) 1.

  3. Enter program name MWS145 and select Create.

  4. On the (CMS017/E) panel, specify the following:

    • Select the event. Depending on selected event you can select fields from different field groups (EVT01-09 and EVT20). See the parameter table.
    • Select the sequence number. If you leave this field blank, the system uses the next higher number.
    • Set to status 20 (Active).
    • Set the priorities from 0 to 9.

      By default, sequence 10 corresponds to priority 0, sequence 20 to priority 1, and so on up to sequence 100, which corresponds to priority 9.

    • Fill in the 'Field 1(2, 3 and 4)' fields with the selected fields from the field group (EVT01-09 and EVT20). Press F4 to select the valid fields.
  5. Select the fields and display (CMS017/E) again.

    Press Enter until you start 'Delivery Process Document Control. Open' (MWS145).

    Create Values for the Object Control Table

  6. You must define values for the defined control fields. You must repeat this for each priority. To the right of the Priority field you can view all priorities defined for this event/sequence number.

  7. On the (MWS145/B) panel, define values for the fields.

  8. The 'Value 1, (2, 3 and 4)' fields are the first, second, third, and fourth values to be compared to the contents of a control object.

  9. Fill in the 'From date' field.

    Note: F15='Delete old' can be used on the B panel to remove all expired document triggers.
  10. On the (MWS145/E) panel, fill in the following fields:

    • To date - The document trigger applies up to and including this date.
    • Send to ASJ - Select the check box to produce the documents asynchronously (via an auto start job).

      If producing documents via an ASJ, then you must have the ASJ MWS974 running. See Administrator's Guide for Auto Start Jobs and Subsystems.

    • Check CSFDEF – Indicates whether a check should be made ensuring that the output controls for each document are valid when retrieving each document trigger. I they are not valid, an M3 mail message is sent to the responsible person defined in the Responsible field.

    Printer file, Work station, and User settings: This combination points to one or more entries in 'Output Media Selection. Open' (MNS205). See this document,

Create object control table for TEI output control

  1. Start 'Available Object Control Parameters. Open' (CMS016). Select SCE Event Document and select option 11=Object table detailed lines.

  2. 'Generic Object Control Table. Open' (CMS017/B) is started.

    Set the panel sequence to E (T) 1.

  3. Enter program name MWS275 and select Create.

  4. On the (CMS017/E) panel specify the following:

    • Select the event. Depending on the selected event, you can select fields from different field groups (TEI01-09 and TEI20). See the parameter table.
    • Select the sequence number. If you leave this field blank, the system uses the next higher number.
    • Set to status 20 (Active).
    • Set priorities from 0 to 9.

      By default, sequence 10 corresponds to priority 0, sequence 20 to priority 1, and so on up to sequence 100, which corresponds to priority 9.

    • Fill in the 'Field 1(2, 3 and 4)' fields with the selected fields from the field group (TEI01-09 and TEI20). Press F4 to select valid fields.
  5. Select the fields and display (CMS017/E) again.

    Press Enter until you start 'TEI Output Control. Open' (MWS275).

Create values for the object control table

  1. You must define values for the defined control fields. You must repeat this for each priority. To the right of the Priority field you can view all priorities defined for this event/sequence number.

  2. On the (MWS275/B) panel, define values for the fields. See the descriptions in the parameter list.

Parameters to set

Generate Documents and Connect Documents to Partner Reference Objects

Program ID/Panel

Field

The field indicates...

(CRS928/B)

Document number

…the unique ID of a document. 915 – TEI transfer document.

(CRS928/B)

Document variant

…the variants of a standard document as defined.

For TEI, each document variant can contain different information as defined by the user.

Example:

Variant 00 sends package information to the external system when the picking list is printed. The purpose might be to print transportation labels.

Variant 10 sends transportation information to the external system when the outbound delivery is reported. The purpose might be to print freight documents.

In this example, since you use two different document variants the external system will know which information every transfer ID contains.

(CRS928/E)

Media control selection

…whether object selection for media control is used for the current document. This must be defined for document 915.

(CRS928/E)

Printer file

…the name of the file that should be replaced temporarily with data from the definition.

(CRS928/E)

Field 1/ Object value for partner reference

…the object value, which is used for partner reference selection.

For TEI, the object value TETIPI (TEI partner) must be used.

(CRS928/E)

Field 2/

…the object value, which is used for partner reference selection. This field is not used for TEI.

(CRS928/E)

External/internal doc

…whether the document is internal or external.

For TEI, a blank value (External) must be used.

(CRS928/E)

Document category

…a classification that is entered for each standard document.

For TEI, the document category must be 2 (Delivery documents).

(CRS947/B)

Document object

…the object value, which is used for partner reference settings in (CRS928) and (CRS945).

In order to use a non-standard combination of document number and document variant in (CRS947), specific customer modifications must be made in functions that use partner control.

Note:  For a TEI transfer document (document number 915), you can use non-standard combinations if the object is TETIPI without any further modifications in functions that use partner control.

(CRS947/E)

Standard generated doc

…whether the combination of document number, document variant, and document object is generated and used within standard functionality. This value cannot be changed by the user.

The valid alternatives are:

0 = A non-standard combination that must be manually generated.

1 = A standard combination that is generated automatically when option F15 is selected in (CRS928) to generate all standard documents

Generate Documents per Company

Program ID/Panel

Field

The field indicates...

(CRS027/B)

Document number

…the unique ID of a document. 915 – TEI transfer document.

(CRS027/B)

Document variant

…the variants of a standard document as defined.

For TEI, each document variant can contain different information as defined by the user.

Example:

Variant 00 sends package information to the external system when the picking list is printed. The purpose might be to print transportation labels. Variant 10 sends transportation information to the external system when the outbound delivery is reported. The purpose might be to print freight documents.

In this example, since you use two different document variants the external system will know which information every transfer ID contains.

(CRS027/E)

External/internal doc

…whether the document is internal or external.

For TEI, a blank value (External) must be used.

(CRS027/E)

Document category

…a classification that is entered for each standard document.

For TEI, the document category must be 2 (Delivery documents).

Define Number Series for TEI Transfer

Program ID/Panel

Field

The field indicates...

(CRS165/B)

Number series type

…the purpose of each number series. The following number series types are valid for TEI:

T1 = TEI transfer ID (mandatory)

T2 = TEI header alias ID

T3 = TEI detail alias ID

(T4 = Transp. Op. Planning msg, is for transportation operational interface)

(CRS165/B)

Number series

…the number series. The same ID can be used by other number series if they belong to other types. For example, series A might be used for both order numbers and invoice numbers, although they have separate number ranges and start values.

Connect Document to TEI Partner and Define Settings for TEI Partner

Program ID/Panel

Field

The field indicates...

(CRS945/B)

Document number

…the unique ID of a document.

For TEI, you must select 915 and a document variant.

(CRS945/B)

TEI partner

…an external partner, for example with the internal number of the customer. This TEI partner is used within the TEI function to determine who will receive the TEI transfer. TEI partners are defined in 'TEI Partner. Open' (MYS015).

(MYS015/B)

Message direction

…the direction of the message.

For TEI, the valid alternative is O (Outbound)

(MYS015/E)

TEI number series type

…the number series type to use for a TEI transfer. The number series type should be T1. A check is made to ensure that the specified series type exists in (CRS165).

(MYS015/E)

TEI number series

…the number series ID to use for a TEI transfer. Several different series can exist for one series type, but only one series ID for each combination of TEI partner, document number, and document variant can be used. A check is made to ensure that the specified series ID exists in (CRS165).

(MYS015/E)

Send TEI transfer automatically

…whether a created TEI transfer (record in MYS500 in status 10) should automatically trigger an MBM initiator and send the transfer to the message broker immediately or if the MBM initiator should be manually triggered by option 9 in MYS500.

The valid alternatives are:

0 = No automatic trigger when a TEI transfer is created. Manually triggering must be done.

1 = The TEI transfer will automatically trigger an MBM initiator when a new transfer is created.

(MYS015/E)

Allow duplicate details

…whether it is allowed to send the same detail value several times to the same external system.

The valid alternatives are:

0 = No duplicate details allowed. If the detail already exists for a TEI transfer, it will not be created for a new TEI transfer.

1 = Duplicate details allowed. A TEI transfer detail will always be created regardless of whether it already exists for a TEI transfer.

Create Object Control Table for Documents/Event

Program ID/Panel

Field

The field indicates...

(CMS016/B)

Object control parameter

…the available object control parameter, where you can define your objects and values.

Select SCE Event Documents - MWS145.

These values are generated automatically when you first enter CMS016 for the installation. If you have upgraded CMS016 you might need to press F14 to create any new values.

(CMS017/B)

View

…the view. Views are user defined, and determine the fields that are displayed and how the data is calculated. They are defined in (CRS020). See Manage Views.

(CMS017/B)

Program name

…the program that is used for the object control table. In this case it is MWS145.

(CMS017/B)

Event/Start value 1

…an event, which is a defined point in time when an M3 entity (such as a delivery) reaches a certain status. These events are predefined. They are specified in Event. Open (CRS019).

By using event-based document control, you can automatically produce certain documents when a defined event occurs.

Table of Available Events for Documents/Events

Event

Field Group (CRS109)

Description

DELIVERY_CLOSED

EVT04

The delivery is manually closed. No further order lines can be added. All possible backorder delivery lines are moved to a new delivery number. Applies to customer orders, requisition orders, and outbound distribution orders. Can only be used together with TEI.

DELIVERY_INV

EVT06

The delivery is fully invoiced. All included delivery lines are invoiced. The event occurs when the invoicing routine prints the invoice. Applies only to customer orders. Can only be used together with TEI.

DELIVERY_ISSUED

EVT02

The delivery is issued. The delivery is fully issue reported, and all possible backorder lines are moved to a new delivery number. This event occurs when the status of a delivery becomes higher than or equal to 60. Applies to customer orders, requisition orders, and outbound distribution orders. Can be used without or together with TEI.

DO_GOODS_REC

EVT08

When the entire delivery is reported as goods received based on information provided with the physical delivery. The event occurs when the entire delivery number is reported as goods received. Applies to inbound distribution orders. Can only be used together with TEI.

MANUAL_DEL

EVT01

A manual request to retrieve a subset of shipments, packages and/or deliveries into a TEI transfer. Compared to the previous events, this event is performed without connection to a process activity and a status raise to an entity. It is a separate event that is performed when the user decides. It allows for creating a TEI transfer based on a manual user decision. Applies to customer orders, requisition orders, and outbound distribution orders. Can only be used together with TEI.

MANUAL_PACKAGE

EVT09

A manual request to retrieve a subset of shipments, packages and/or deliveries into a TEI transfer. Compared to the previous events, this event is performed without connection to a process activity and a status raise to an entity. It is a separate event performed when the user decides. It allows for creating a TEI transfer based on a manual user decision. Applies to customer orders, requisition orders, and outbound distribution orders. Can only be used together with TEI.

MANUAL_SHP

EVT02

A manual request to retrieve a subset of shipments, packages and/or deliveries into a TEI transfer. Compared to the previous events, this event is performed without connection to a process activity and a status raise to an entity. It is a separate event performed when the user decides. It allows for creating a TEI transfer based on a manual user decision. Applies to customer orders, requisition orders, and outbound distribution orders. Can only be used together with TEI.

PO_GOODS_REC

EVT20

Each purchase order (PO) line or part of a PO line is reported as goods received based on information provided with the physical delivery. The event occurs when a PO line or a part of a PO line is goods received and a receiving number is created. Applies to inbound distribution orders. Can only be used together with TEI.

RELEASE_PICK

EVT01

A delivery is released, either manually or time triggered, resulting in a new picking list (delivery number and picking list suffix). This event occurs when a picking list or group of picking lists is created after a delivery is released for picking. Depending on the configuration, pack reporting can be performed simultaneously. Applies to customer orders, requisition orders, and outbound distribution orders. Can be used with or without TEI. Note that this event can occur more than once depending on the closing point of the delivery. The event applies to picking lists that attain a status of 40 or higher for the first time. This means that the event is deemed to have occurred for picking lists going through pick resource planning only after release from pick resource planning.

SHIPMENT_CLOSED

EVT05

The shipment is manually closed. No further deliveries can be added. All possible backorder lines are moved to new delivery numbers and possibly a new shipment. Applies to customer orders, requisition orders, and outbound distribution orders. Can only be used together with TEI.

SHIPMENT_INV

EVT07

The shipment is fully invoiced. All included deliveries and delivery lines are invoiced. The event occurs when the invoicing routine creates the invoice. Applies only to customer orders. Can only be used together with TEI.

SHIPMENT_ISSUED

EVT03

The shipment is issued and the deadline has passed. All deliveries included in the shipment are issued, and no more deliveries will be added automatically. This event occurs when a shipment has status 60/60 and the shipment deadline has passed. All possible backorder lines are moved to new delivery numbers and possibly a new shipment. Applies to customer orders, requisition orders, and outbound distribution orders. Can be used with or without TEI.

Note: The SHIPMENT_ISSUED event requires that the auto start jobs DRS900 and DRS901 are running.

(CMS017/E)

Sequence number

The sequence number enables you to specify different sets of controlling objects for the same event. You might, for example, want to control picking lists with one set of objects and address labels with another.

If you do not enter a sequence number, one will be selected for you automatically. The system will take the next higher number for the event.

(CMS017/E)

Status

The status of the object control setting.

10 = Preliminary

20 = Definite

90 = Blocked/expired.

Only status 20 is used in the dispatch flow.

(CMS017/E)

Field sequence number

The order in which each information field should be displayed.

Example:

To move an object control line from priority 2 to 1, assign the sequence number for the line a number between 11 and 19. Press Enter. The line is then placed in the correct order.

(CMS017/E)

Priority

A priority for the selected fields. The object lookup is always performed in priority order. If no qualified objects are found according to priority one, M3 will try to find matching objects according to priority two, and so on.

(CMS017/E)

Field

A field or data element from a specific file. It is used to create keys or search paths for user defined tables and also to create the contents of user defined files.

Note: These fields will be protected if entries are found in (MWS145). That means that you cannot enter these fields if they are in use.

(CRS109/B)

Field group

A grouping of several fields from different files that regulate matrix entries. In this case, the EVT01, 02, 03, 04, 05, 06, 07, 08, 09, 20 field groups can be selected.

Field groups are system-defined and cannot be changed.

Settings for Document Production

Program ID/Panel

Field

The field indicates...

(MWS145/B)

Priority

…the table priority from the table in (CMS017). When the system searches after document event triggers, it searches object value entries in priority sequence, from 0 to 9, until a matching set of object values is found.

All available priorities are displayed to the right and are separated by a slash, for example 0/1/2.

(MWS145/B)

Value 1, 2, 3, 4

These are the object values that must match for the given event to cause the documents entered in the corresponding MWS145/E panel to be produced.

Example: A setting is defined here for event RELEASE_PICK. If the control objects are warehouse and stock zone, and the values entered here are 001 and AA, then the warehouse and stock zone for the picking list must be 001/AA for the documents in the corresponding MWS145/E panel to be produced.

Example: Start value 1 is Warehouse (OQWHLO). Select a warehouse by pressing F4=Prompt.

Start value 2 is stock zone (PISLTP). Select a stock zone by pressing F4.

(MWS145/B)

From date

…the date from which the document trigger will be active.

(MWS145/E)

To date

…the valid To date. The document trigger applies up to and including this date.

(MWS145/E)

Send to ASJ

…whether the production of the specified documents for this event trigger will be produced synchronously or asynchronously.

If the documents will be produced asynchronously, then the task is sent to an auto start job, which is a batch job. Otherwise, the print program is started and executed. The flow must wait for the print program to finish.

Select the check box to produce the documents asynchronously.

For more information about auto start jobs, see Auto Start Jobs and Subsystems in M3 12 Java Administrator's Guide.

(MWS145/E)

Check CSFDEF

…whether a check should be made ensure that the output controls for each document are valid when retrieving each document trigger.

This check verifies that at least one output media selection entry exists in (MNS205) for this key. If no such entry exists, a message is sent to the M3 mailbox for the responsible person indicated in the trigger definition (MWS145/E).

Select the check box to make this check.

(MWS145/E)

Responsible

…a unique user ID.

The person responsible entered here will receive any M3 mail for errors related to missing media control settings.

(MWS145/E)

Doc number

Doc variant

Doc name

…the document number and document variant together determine a specific variant of a document.

Only documents defined for the event in (CRS019) can be used.

The following documents are valid in EDC:

Picking list (120)

Delivery note (900)

Dispatch advice (901)

Package labels (912)

Address labels (913)

Loading list (909/00)

Unloading list (909/01).

The following documents are valid in TEI:

TEI transfer document (915)

(MWS145/E)

Printer file

Work station

User

…the combination of printer file, work station, and user.

This combination points to one or more entries in 'Output Media Selection. Open' (MNS205).

When the connected document is produced, it will use these output services and media types.

Note: For picking lists, the media control entered here is only used if the printer entered for all relevant stock zones is set to blank.

(MWS145/E)

Log level

…the log level.

If this check box is selected, then delivery documents produced using event-based document control will update the delivery document history and be visible in the connected delivery documents sorting order (MWS260).

Select the check box to update the delivery document history.

This is only valid for certain documents.

Create Object Control Table for TEI Output Control

Program ID/Panel

Field

The field indicates...

(CMS016/B)

Object control parameter

…the available object control parameter, where you can define your objects and values.

Select TEI Output Control- (MWS275).

These values are generated automatically when you first enter (CMS016) for the installation. If you have upgraded (CMS016) you might need to press F14 to create any new values.

(CMS017/B)

View

…the view.

Views are user defined, and determine the fields that are displayed and how the data is calculated. They are defined in (CRS020). See Manage Views.

(CMS017/B)

Program name

…the program that is used for the object control table. In this case it is (MWS275).

(CMS017/B)

Event/Start value 1

…an event, which is a defined point in time when an M3 entity (such as a delivery) reaches a certain status. These events are predefined. They are entered in Event. Open (CRS019).

By using event-based document control, you can automatically product certain documents when a defined event occurs.

(CMS017/E)

Sequence number

…the sequence number.

The sequence number enables you to specify different sets of controlling objects for the same event. You might, for example, want to control picking lists with one set of objects and address labels with another.

If you do not enter a sequence number, one will be selected for you automatically. The system will take the next higher number for the event.

(CMS017/E)

Status

…the status for the object control setting.

10 = Preliminary

20 = Definite

90 = Blocked/expired.

Only status 20 is used in the dispatch flow.

(CMS017/E)

Field sequence order

…the order in which each information field should be displayed.

Example:

To move an object control line from priority 2 to 1, assign the sequence number for the line a number between 11 and 19. Press Enter. The line is then placed in the correct order.

(CMS017/E)

Priority

…a priority for the selected fields.

The object lookup is always performed in priority order. If no qualified objects are found according to priority one, M3 will try to find matching objects according to priority two, and so on.

(CMS017/E)

Field

…a field or data element from a specific file.

It is used to create keys or search paths for user defined tables and also to create the contents of user defined files.

Note: These fields will be protected if entries are found in (MWS145). That means that you cannot enter these fields if they are in use.

(CRS109/B)

Field group

…a grouping of several fields from different files that regulate matrix entries. In this case, the EVT01, 02, 03, 04, 05, 06, 07, 08, 09, 20 field groups can be selected.

Field groups are system-defined and cannot be changed.

Settings for How TEI Output Should Be Processed to an External System

Program ID/Panel

Field

The field indicates...

(MWS275/B)

Priority

…the table priority from the table in (CMS017). When the system searches for document event triggers, it searches object value entries in priority sequence, from 0 to 9, until a matching set of object values is found.

All available priorities are displayed to the right and are separated by a slash, for example 0/1/2.

(MWS275/B)

Value 1, 2, 3, 4

These are the object values that must match for the given event to cause the TEI output, specified in the corresponding (MWS275/E) panel, to be processed to an external system.

Example: A setting is defined here for event RELEASE_PICK. If the control objects are warehouse and stock zone, and the values entered here are 001 and AA, then the warehouse and stock zone for the picking list must be 001/AA for the TEI output in the corresponding (MWS275/E) panel to be processed.

Example: Start value 1 is Warehouse (OQWHLO). Select a warehouse by pressing F4=Prompt.

Start value 2 is stock zone (PISLTP). Select a stock zone by pressing F4.

(MWS275/E)

TEI partner

…an external partner, for example with the internal number of the customer. This TEI partner is used within the TEI function to determine who will receive the TEI transfer.

TEI partners are defined in 'TEI Partner. Open' (MYS015).

(MWS275/E)

TEI header Alias - method

…whether transaction alias is used and how.

The valid alternatives are:

0 = No transaction alias is used.

1 = Transaction alias is used and it is retrieved from a number series type and series ID.

2 = Transaction alias is used and retrieved via a user exit program.

The transaction alias is an ID that is saved on the TEI transfer header. The alias can be used if the receiving system has specific requests on how the TEI transfer number should appear and the TEI transfer ID is insufficient.

(MWS275/E)

TEI header Alias - number series type

…the number series type that should be used for a TEI transfer. The number series type should be T2. A check is made to ensure that the entered series type exists in (CRS165).

(MWS275/E)

TEI header Alias - number series ID

…the number series ID that should be used for a transaction alias. Several different IDs can exists for one series type but only one ID per TEI output control record can be used. A check is made to ensure that the entered series ID exists in (CRS165).

(MWS275/E)

TEI header Alias - user exit program

…a program that will be used to calculate or retrieve a transfer alias. The program in this field will be called when a TEI transfer is created.

The purpose is to enable the user to design the program. If the program name in this field does not exist as a valid program, method 0 is used.

(MWS275/E)

TEI detail Alias - method

…whether a package alias is used and how it is used.

The valid alternatives are:

0 = No package alias is used.

1 = Package alias is used and it is retrieved from a number series type and series ID.

2 = Package alias is used and retrieved via a user exit program.

Note: The user exit program must be designed in each implementation.

The package alias is an ID that is saved on each TEI transfer detail. The alias can be used if the there are specific requests on each TEI detail ID. An example is if each detail is a package and the package label is printed from an external system (TES). Then the package alias can be used as a reference on each package.

(MWS275/E)

TEI detail Alias - number series type

…the number series type that should be used for a TEI transfer. The number series type should be T3. A check is made to ensure that the entered series type exists in (CRS165).

(MWS275/E)

TEI detail Alias - number series ID

…the number series ID that should be used for a package alias. Several different IDs can exists on one series type but only one ID per TEI output control record can be used. A check is made to ensure that the entered series ID exists in (CRS165).

(MWS275/E)

TEI detail Alias - user exit program

…a program that will be used to calculate or retrieve a package alias. The program in this field will be called when a TEI transfer detail is created.

The purpose is to enable the user to design the program. If the program name in this field does not exist as a valid program, method 0 is used.

Related topics