Sap Tm215 en Col16 Tm 9.3 Wwwerpexamscom

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TM900 SAP Transportation Management - Architecture Fundamen Fundamentals tals an and Enhancement Concepts SAP SCM

Date Training Center Instructors

Education Website


Participant Handbook Course Version: 96 Course Duration: 2 Days Material Number: 50127520

An SAP course - use it to learn, reference it for work

0For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]


Copyright Copyright © SAP SE. All rights reserved.

N o part o f this publication may b e reproduced or transmitte transmitted d in any form or for any purpose without the express permission of SAP SE. The information contained herein may be changed without prior notice.

Some software products marketed by SAP SE and its distributors contain proprietary software components o f other software software vendors.

Trademarks •

Microsoft®, WIND OWS® , NT® , EXCEL®, Word®, Word®, PowerPoint® and SQL Server® are are registered trademarks trademarks o f Microsoft Corporation. Corporation.

•

IBM®, DB2® , OS/2®, DB2/60 00®, Paral Paralle lell Sysplex®, MVS/ESA ®, RS/6000® , AIX®, S/390 ®, AS /400® , OS /390® , and OS/40 0® are registere registered d tradema trademarks rks of IBM Corporati Corporation. on.

•

ORA CLE ® is a registered trademar trademark k o f ORACL E Corporation. Corporation.

•

INFOR MIXK-O nLinc for SAP and INFOR MIX® Dynam ic ScrvcrTM arc registered registered trademarks trademarks of I nformix Software Incorporated. Incorporated.

•

UN IX ®, X/Op en®, OSF /1®, and Motif ® are registered trademarks trademarks o f the Open Group. Group.

•

C'itrix® C'itrix®,, the Citrix Citrix logo , ICA ®, Program Program Neigh borho od®, MetaFrame®, WinFrame®, VidcoFram e®, Multi Win® and other Citrix product names referenced herein arc trademarks trademarks o f Citrix Citrix Systems, Inc. Inc.

•

HTML, DHTM L, XML, XHTML are trademarks trademarks or registered trademarks trademarks o f W3C ®, World World Wide Web Consortium, Massachusetts Institute of Technology.

•

JAVA® is a registered trademark trademark o f Sun Microsy stems , Inc.

•

JAVASCRIPT® is a registered trademark trademark o f Sun Microsy stems , Inc., used under licens e for technology invented and implemented by Netscape.

•

SAP, SAP Logo , R/2, RTVA RTVA,, R/3, SAP ArchiveLink, SAP Busin ess Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademar trademarks ks or registered trademarks trademarks o f SAP SE in Germany and in several other countries all over the world. All other products products men tioned arc trademarks trademarks or registered registered trademarks trademarks of their respective companies.

Disclaimer THESE MATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLY DISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERC HANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE, INFORMATION, TEXT, GRAPHICS, LINKS, OR ANY OTHER MATERIALS AND PRODUCTS CONTAINED HEREIN. IN NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANY KIND WHATSOEVER, INCLUDING WITHOUT LIMITATION LOST REVENUES OR LOST PROFITS, WHICH MAY RESULT FROM THE USE OF THESE MATERIALS OR INCLUDED SOFTWARE COMPONENTS.

g20141119104749



Copyright Copyright © SAP SE. All rights reserved.

N o part o f this publication may b e reproduced or transmitte transmitted d in any form or for any purpose without the express permission of SAP SE. The information contained herein may be changed without prior notice.

Some software products marketed by SAP SE and its distributors contain proprietary software components o f other software software vendors.

Trademarks •

Microsoft®, WIND OWS® , NT® , EXCEL®, Word®, Word®, PowerPoint® and SQL Server® are are registered trademarks trademarks o f Microsoft Corporation. Corporation.

•

IBM®, DB2® , OS/2®, DB2/60 00®, Paral Paralle lell Sysplex®, MVS/ESA ®, RS/6000® , AIX®, S/390 ®, AS /400® , OS /390® , and OS/40 0® are registere registered d tradema trademarks rks of IBM Corporati Corporation. on.

•

ORA CLE ® is a registered trademar trademark k o f ORACL E Corporation. Corporation.

•

INFOR MIXK-O nLinc for SAP and INFOR MIX® Dynam ic ScrvcrTM arc registered registered trademarks trademarks of I nformix Software Incorporated. Incorporated.

•

UN IX ®, X/Op en®, OSF /1®, and Motif ® are registered trademarks trademarks o f the Open Group. Group.

•

C'itrix® C'itrix®,, the Citrix Citrix logo , ICA ®, Program Program Neigh borho od®, MetaFrame®, WinFrame®, VidcoFram e®, Multi Win® and other Citrix product names referenced herein arc trademarks trademarks o f Citrix Citrix Systems, Inc. Inc.

•

HTML, DHTM L, XML, XHTML are trademarks trademarks or registered trademarks trademarks o f W3C ®, World World Wide Web Consortium, Massachusetts Institute of Technology.

•

JAVA® is a registered trademark trademark o f Sun Microsy stems , Inc.

•

JAVASCRIPT® is a registered trademark trademark o f Sun Microsy stems , Inc., used under licens e for technology invented and implemented by Netscape.

•

SAP, SAP Logo , R/2, RTVA RTVA,, R/3, SAP ArchiveLink, SAP Busin ess Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademar trademarks ks or registered trademarks trademarks o f SAP SE in Germany and in several other countries all over the world. All other products products men tioned arc trademarks trademarks or registered registered trademarks trademarks of their respective companies.

Disclaimer THESE MATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLY DISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERC HANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE, INFORMATION, TEXT, GRAPHICS, LINKS, OR ANY OTHER MATERIALS AND PRODUCTS CONTAINED HEREIN. IN NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANY KIND WHATSOEVER, INCLUDING WITHOUT LIMITATION LOST REVENUES OR LOST PROFITS, WHICH MAY RESULT FROM THE USE OF THESE MATERIALS OR INCLUDED SOFTWARE COMPONENTS.

g20141119104749



About This Handbook This handbook is intended to complement the instructor-led presentation of this course, and serve as a source of reference. It is not not suitable for fo r self-study. self-study.

Typographic Conventions American English is the standard standard used in this handbook. The following typographic conventions are also used. Type Style Example text

Description

Words Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths, and options. Also used for cross-references to other documentation both internal and external.

Example text

Emphasized words or phrases in body text, titles of graphics, and tables

EXAMPLE TEXT

Names of elements in the system. system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example SELECT and INCLUDE.

E x am am p le le t e x t

Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, and passages of the source text of a program.

Example t e x t

Exact user ser entry. Th These are words and characters that you enter in the system exactly as they appear in the documentation.

Variab riable le user user entry try. Poin Pointe ted d brac brack kets ets in indica dicate te that that you you replace these words and characters with appropriate entries.



Icons in Body Text The following icons are used in this handbook. Icon

Meaning

P

For more information, tips, or background

Note or further explanation o f previous point

A

Exception or caution

Procedures T 27 \ 3 / Indicates that the item is displayed in the instructor’s presentation.




Contents Course Overview........................................................................ vii Course Goals .................................................................................... vii Course Objectives............................................................................vii

Unit 1: SAP TM Architecture

.........................................................

1

SAP TM Architecture.........................................................................2

Unit 2: Business Object Processing Framework(BOPF)

.........

13

Business Object Processing Framework (BOPF) ....................... 14

Unit 3: Floor Plan Manager (FPM) and BOPF Integration

........

31

Floor Plan Ma nager (F P M ).............................................................32 Floor Plan Manager BOPF Integration (FBI) ................................ 38

Unit 4: Queries and Personal Object Worklists (POWL)

...........

57

Queries and POWLs ........................................................................ 58

Unit 5: Standard Enhancement Techniques inSAP TM

.............

63

Busin ess Ad dins (B A d ls )................................................................64 Implicit Enhancements....................................................................69

Unit 6: Conditions........................................................................ 73 Co nditions..........................................................................................74

Unit 7: Process Controller........................................................... 85 Process C on tro lle r........................................................................... 86

Unit 8: Post Processing Framework (PPF)

.................................

97

Post Processing Framework (PPF)................................................98

Unit 9: Print Forms..................................................................... 113 Print F o rm s ..................................................................................... 114

Unit 10: Integration

....................................................................

121

Integration........................................................................................122






Course Overview This course gives an overview of the architecture and the technical frameworks of the TM solution and focuses on instructor presentations and demonstrations of the thought concepts. There are no hand-on exercises for the participants. In case you want to gain hands-on experience on how to apply the concepts and do enhancements in the system, you might want to take training TM910 instead, which focuses on exercises and covers the same topics. After this training you should be able to provide solution architectural guidance in projects.

Target Audience This course is intended for the following audiences: •

Solution Architects

•

Consultants

Course Prerequisites Required Knowledge •

General (functional) understanding of the TM business documents and processes

Recommended Knowledge •

TM100 Processes in Transportation Management

•

BIT400 SAP Exchange Infrastructure / Process Integration

Course Goals This course will prepare you to: •

Learn about the technical insight on SAP TM

•

Have a more detailed overview of the flow of information and data, decision points and an architectural overview on extensibility and overall understanding of user interface capabilities with the floor plan manager

•

Use the guide to the right points for consistent and powerful extensibility of your overall solution scenario in order to allow faster and more efficient innovation with SAP TM, especially considering business suite scenario and process integration



Course Objectives After completing this course, you will be able to: •

Understand the basic Architecture of SAP TM

•

Get a general understanding about the frameworks used in SAP TM - Business Object Processing Framework (BOPF) - Floor Plan Manager (FPM) and Floor Plan Manager BOPF Integration (FBI) - Process Controller and Strategies, Conditions (based on BRFplus) and Business Addins (BAdls) in SAP TM - Further enhancement options

•

Get a general understanding about how to use the frameworks for enhancing the business logic and User Interface of SAP TM



Unit 1 SAP TM Architecture Unit Overview

Unit Objectives After completing this unit, you will be able to: •

Name the software components that are involved in SAP TM

•

Explain the Integration of SAP TM with other Systems/Components

•

Understand the Business Object Model of SAP TM and the relation between the different Business Objects

•

Describe the basic technology stack used to implement SAP TM

•


Unit Contents Lesson: SAP TM Architecture..........................................................................2



Lesson: SAP TM Architecture Lesson Overview In this unit you will understand the basic architecture of SAP TM.

Lesson Objectives After completing this lesson, you will be able to: •


•


•


•


•


Business Example None

SAP Transportation Management Involved Software Components (listed here for TM 9.0 and TM 9.1) Product Version SAP TM - Components

SAP TM 9.0 - TM Server •

SAP TM 1.10

•

SAP AP 7.00

•

EA-IPPE 400

•

SAP BS Foundation 731

•

SC’MB PLUS 7.02

•

SAP SC'M BASIS 7.02

•

SAPNetWeaver 7.3 EHP1

SAP TM 9.0 - Optimizer and XI Content •

SAP SC'M Optimizer 9.0

•

XI Content SAP TMI C 1.1

•

XI Content SAPTM

•

XI Content SC'MBasis 7.02

•

XI Content SCM Basis IC 7.02

1.1



SAP TM 9.1 - TM Server •

SAP TM 1.20

•

SAP AP 7.00

•

EA-IPPE 400

•

SAP BS Foundation 747

•

SCMB PLUS 7.13

•

SAP SCM BASIS 7.13

•

SAP NetWeaver 7.4

SAP TM 9.1 - Optimizer and XI Content •

SAP SCM Optimizer 11.0

•

XI Content SAPTM1.2

•

XI Content SCM Basis 7.13

SAP TM 9.1 - TM UI Features •

(TV—F

t

SAP TM UI 1.2 (Collaboration Portal)

)1

B u sin es s In fo rm atio n

A d ob e D o cu m en t

W a re h o u s e C o n te n t

S erv er

1 r

RFC

CRM 7.03

RFC

RFC

EM 9.1

TM9.1

Option 1: Web Service (direct)

Option 1: Web Service (direct) ^

Optimizer TM (SCM 11.0)

EWM 9.1 Option 2: Web Service

Option 1: Web Service (direct)

External GIS

PI 7.11 Option 2: RFC

IGS*

Option 2:

(indirect via PI)

RFC

Option 1:

Option 2:

Option 2;

Master

Web Service

Web Service

Web Service

(direct)

(indirect via PI) -SOScreduing

Data

Web Service (indirect via IGS)

-SOSctedjliig -Odef n»3racoi -Oc-tveryntcjraon -Invoice Crcato" /invoice Vfcrfcaocn

- Oder nteqraan -Deliveryrccqraon

- Invoice Creation - - Irwoic; vemcaDo-

ERP V

ERP 6.0 EhP6

GTS 10.1

(indirect via PI) Web Service-IDOC for Shipment Integration .(also supported indirectly)

GTS PI «

RFC

Figure 1: SAP Transportation Management - System Landscape Overview

SAP TM Architecture Business Objects - The “Heart” of the Application Business Objects



Business Objects are the basis of the SAP TM application. Each Business Object represents a type of a uniquely identifiable business entity, described by a structural model, an internal process model as well as one or more Service Interfaces. The business processes provided with SAP TM operate on these Business Objects. Business Documents (Forwarding Order, Freight Order, Freight Unit, ...) are implemented by technical Business Objects (Transportation Request, Transportation Order, ...). Business Object Processing Framework

BOPF controls the application business logic as well as the data retrieval of the buffer and persistency layer. The main design principles are a clear separation of the business logic and the buffering of data as well as a clear structuring of the business logic into small parts with a clear separation of changing and checking business logic. The BOPF approach for implementing business objects breaks down business logic into the following four concepts: •

Actions

•

Determinations

•

Validations

•

Queries



SAP TM Business Object Model

•

Transportation Request (TRQ) Technical Object used to present Forwarding Order, Forwarding Order Quotation

•

Transportation Order (TOR) Technical Object used to represent Freight Unit, Freight Order, Booking, Quotation

•

TRQ and TOR are the “main” Business Objects in TM

•

This design approach is based on the mostsimple processes of the transportation management solution where a transportation demand is directly forwarded to execution. Therefore the corresponding transportation functionality must be available on these two Business Objects.

•

All other (more complex) process variants are extensions of this simple basic process and are handled by additional instances of the two mentioned basic Business Objects.

•

Further Business Objects in TM: Forwarding Settlement (FWSD) - also called C'FIR (Customer Freight Invoice Request). Freight Settlement (FSD) - also called SFIR (Supplier Freight Invoice Request). Master Data Objects to represent entities like Business Partner, Location, Schedule, etc. Planning Transient Business Object (TBO) used in the context of planning functionality. Transportation Charges - Dependent Object to be reused in all objects subject to charge calculation.



SAP TM Business Object Model

•

High overlap of structure and required functionality of business documents: One “technical” BO can have different functional views and roles. No redundant storage of data (“Requested, Active, Confirmed”). Process control according to BO category is ensured. Relation between different BO instances of the same “technical” BO are defined. Same functionality has not to be defined on different BOs. Simple, straight forward processes are not influenced by optional and more complex scenarios. Customer implementations and enhancements are more flexible with less effort.

Performance

•

Significant performance improvements achieved: Better runtime behavior and lower memory consumption of the application by focusing on clear, non-redundant structures and reuse.

•

Continuous performance measurements and analysis during development phase of TM in all layers of the used technology stack. Master Data

Figure 2: SAP TM Architecture - Integration



Booking

Service entry Inc. Invoice

Figure 3: SAP TM Architecture - Integration & relation between TM Business Objects



SAP TM User Interface

•

The UIs are based on intensive feedback from customers. Usability tests were done in cooperation with customers and partners. A UI First approach was followed. The UI is process oriented, following the SAP UI guidelines.

•

Web Dynpro ABAP in combination with Floorplan Manager (FPM) is used to build the UIs. Increased development efficiency for Floorplan UIs Enables configurable UIs based on the processes as well as customers and users needs No programming is required for enhancements. Increased adaptation capabilities for customers and partners Reduced technical barrier for UI adjustments Adaptation by configuration instead of modifying Web Dynpro ABAP coding Increased consistency across all application areas by reusing generic UI building blocks

•

The connection between the FPM UIs and the application backend is realized via the Floorplan Manager BOPF Integration (FBI) layer. The BOPF Framework is used to model, implement and execute the business objects of TM, i.e. the backend functionality with all the business logic for any process step. FBI provides Exit- and Conversion Classes that also allow to influence the UI behavior by coding.

•

Data-sensitive UIs are possible now: Variation of the UI depending on BO data. -

•

Example: TRQ Type 001: Express Packaged Goods, TRQ Type 002: Full Container Load.

Flexibility: SAP TM standard delivers a UI proposal (“general purpose”) Customers and partners can adapt it The adaptation does not overwrite the TM standard UI



Figure 4: SAP TM Architecture - Technology Stack



Lesson Summary You should now be able to: •


•


•


•


•




Unit Summary You should now be able to: •


•


•


•


•










Unit 2 Business Object Processing Framework (BOPF) Unit Overview


Explain what BOPF is and what it is used for

•

Describe the main entities of a BOPF Business Object Model

•

Navigate to and browse through the available SAP TM Business Objects and their entities

•

Test a BOPF Business Object

•

Explain the basic steps how to enhance BOPF Business Objects

Unit Contents Lesson: Business Object Processing Framework (BOPF).........................14 Procedure: Transaction /BOBF/CO NF U I ..............................................19 Procedure: Transaction BO BT ................................................................22 Procedure: Transaction B O B ................................................................. 26



Lesson: Business Object Processing Framework (BOPF) Lesson Overview In this lesson you will understand the concepts of the Framework used for modeling and implementing SAP TM.



•


•


•


•


Business Example None

BOPF - Business Objects Processing Framework What is it?

•

A Framework for modeling and implementing Business Objects (BOs) that interact as an application

•

It is UI independent

•

It is not a “Programming Language” —>Implementation is done in ABAP 0 0

•

Flexible & Model-driven approach to develop Business Objects / Applications



Why BOPF?

•

Rapid development and implementation of running Business Objects

•

Allows modeling of real world Business Objects and their relations between each other (—>Design Time)

•

Allows Execution / Testing of implemented Business Objects (—* Runtime) Handles Transaction Management, Buffering, Data Access and Locking -

Property and Message Handling

•

Provides a unified and consistent programming model

•

Enhancement Concept for Customers and Partners Allows additional, modification free enhancements Field Extensions and additional Business Object Logic

Entities of a BOPF Business Object Model Nodes

•

A Node is a semantically related set of attributes of a business object. Nodes can be used to define and structure your business object. The attributes of a business object node are defined by dictionary data types.

•

Nodes can be hierarchically defined and related. Each business object has only one Root Node. Nodes are defined via compositions in a tree, but nodes can also be related in an arbitrary structure via associations that can be separate from the tree structure.

•

Business Object Representation nodes are placeholders for other business objects and the associations to these. They are only for visualization of the association to other business objects.

Associations

•

An association is a direct, unidirectional, binary relationship between two business object nodes.

•

Associations can be used to relate two nodes in a well-defined direction. The association can be used to navigate from one node (source node) to the related node (target node).

•

The associated nodes can be nodes within one business object or in different business objects (cross business object association).

•

Associations can have parameters to filter the result of the related nodes.

•

They can only be defined between two nodes and in one defined direction.

•

Moreover, they have a defined cardinality which gives information about the existence of an association and the number of associated nodes.



Actions

•

An action is an element of a business object node that describes an operation performed on that node.

•

An action can be used to allow the external triggering of business logic (in contrast to a determination).

•

When the action is performed, you must specify the key for the instances on which it is to be performed (if it is not a static action) and any input parameters that the action requires.

•

An action can only be performed with the number of instances that is configured in the cardinality of the action.

•

It is performed for all instances if an error in the action validation has not occurred. If errors occur, then the behavior depends on the action settings.

Determinations

•

An element of a business object node that describes internal changing business logic on the business object. It can be used to trigger business logic based on internal changes (in contrast to an action). There are two types of determinations: Transient and Persistent. This categorization indicates whether a determination will alter persistent or only transient data.

•

A determination is mostly used to compute data that can be derived from the values of other attributes. Examples: Products (for example, item amount = quantity list price) and ratios Totals of items (for example, invoice amount = S item amounts) -

Statuses

•

The determined attribute and the determining attributes can belong to the same node (example 1) or to different nodes (example 2). There are also values that do not depend on any other value but still have to be determined automatically upon creation or modification of a node instance, for example, IDs, UUIDs, and GUIDs.

•

For each determination, it is necessary to specify which changes (such as create, update, delete or load) on which nodes will trigger the determination at a specific time. A determination is called at different points in time (determination time), depending on the model.



Validations

•

A validation is an element of a business object node that describes some internal checking business logic on the business object.

•

A validation can be used to check if an action is allowed. Action validations can be assigned to object-specific actions and to the framework actions create, update, delete and save. They can be used to check if an action can be carried out. An action validation is carried out when an action is called before it is performed. If some validations fail, the action is not performed for the instances where the validation failed. Depending on the action settings, the action is also not performed those instances that not failed (“all or nothing”).

•

A validation can be used to check the consistency of a business object. Consistency validations can be used to check the consistency of a business object. They can be assigned to the framework action CHECK of each node. Consistency validations are carried out when this action is called or automatically after a change is made if they are triggered via trigger nodes based on the changes. It is only triggered if some of the trigger nodes are assigned and instances of these trigger nodes are changed.

Queries

•

Queries represent a defined set of attributes, such as search parameters, that return the queried IDs of the business object node instances.

•

A query allows you to perform searches on a business object. They provide the initial point of access to business objects. Each query has an associated parameter structure. The result of the query is a set of all the record IDs in a business object that match the query criteria.



Where to start with BOPF?

•

BOPF is part of the S A P B S F N D layer.

•

Business Object Builder: Used by customers and partners creating additional, new BOs, enhancing the content and logic of existing standard BOs. Transaction:

•

BOB

(or /BOBF/CUSTJJI or BOPF EWB)

Extended Business Object Builder: Used by customers and partners for more complex enhancements of existing standard BOs. Transaction:

•

BOBX

Test UI: Allows testing and executing the functionality of implemented BOs in a generic environment. Transaction:

•

BOBF

(or /BOBF/TESTJJI).

Configuration UI: Used by SAP Standard Development to model and implement BOs of an application. Transaction: /BOBF/CONFJJI.



X I7

Transaction /BOBF/CONFJJI

Business Object Processing Framework (for In ternal use only)

Q]

+

•+

0

12

U

’srrets 9 r c « » !» r/w o m * 1 * 1 U u s » « ? > » » * ..— » C W M !U 'J j -< 9 c * 0 3 l S * C W riD c n o i k A fctI k ' tw co o‘ tilM jnjcrf •9 K f U a in S i APfOZnUM . C O A « * * L t jo . u < ; jf c ~ . • 9 i C O O W fl O tf«»tU JIM il O .1 ;C 'l# « u m • 9 nOPMOOKt M O u W l X H / t » A e f u t* I|U J H C T L U 0 W < X r t P V T _ K 3 N tP « TI • 9 b b ihit . R C ji oc •9'b:» ' = e c 3 6 f 'K .S u 'r c • 9 c .hw .£ 5 : .V T » E ,< M 5 T F « I» r -» . i* £ j C-r.tiln -Mt t IreXi R nil ■9 ! •9 J 0 j.lin Tinctrisx r> 'Vtrij -9iw m E I H N •9iS tM T H E -W O P R . E O Tprm c M i T k r f a . r c w E i> T t i/. n o F ' l & l t * fo r n e r tC c c ir w id • 9 s t M T M L 'T * . • 9 V T U Iui kkuIA iU ju •9 tr u « » • * T f lA m i T r x c tw tr .c r iC * S o r •9 T ijrico ljr.cri vto; •9 sxtm [uj M uK lM C ll •9 fflC W H O S W •9fK V ^ K O H O T &S. hs twluw dot. *G t e P ^ r f c 'r tc tr « l)1 9 ) •□ cost C 2 E ) •JS k t jD jT iX u c c J1 2 2 1 •U (:| | •C i»«,»cm *:. jhok I *G \jr.d E t a rm Obw.‘.i ' _ J r > 5 ; e : iC o B jC b < 1 1

f

i t

Business Object Browser: Lists all available BOs, i.e. Business Process Objects, Master Data, Dependent Objects, etc.

3

f Figure 5: Development Environment for Standard BOs (1)

2. D i s p l a y B u t m a n o b j e c t / S C M T M S/ T BQ , A c t i v e V e r n o n

t

t *

I 'S

J t i

; i( -

in

a

11

' Business Object Settings with Con stants Interface, Buffer Class, Data Access Class, Definition of transactional behavior, etc.

Figure 6: Development Environment for Standard BOs (2) 3.

Continued on next page



D i s p l a y B u s i n e s s O b j e c t /S C M T M S / T K Q , A c t t v e V e r s i o n 0 3

*> *

3Of

fr

>

-

i*

a

U

Business Object Node details with all related DDIC structure and the assigned DB Table, etc.

Figure 7: Development Environment for Standard BOs (3) 4, Display Bus iness O bject /SCMTMS/ Tft Q, Active Version

l * a?

y u ;* c*

u

«

u

Figure 8: Development Environment for Standard BOs (4) 5.




Figure 9: Development Environment for Standard BOs (5)



X I7

Transaction BOBT

The BO to be tested

BOPF: Test Business O bject

-------

l/SCMTMS/TOR

0E)i® "

v "

=1

a / 5 CMTM5 /TC R > ROO T TORJD

T 0 R_CA

610 X 00050

TO

10C0

M

400000002

TO

07LD

P

400000353

TO

TT4CC

P

. 76EC5FBC4

300000252

TO

0 F05

9 0 C60563fC 5D l l e D l B E E C 0513 C)0621BC 4 9 0 C60563F05 D 11EO1EEEC66B916057 BC4 9 0050563F05 D 11ED 1BF62002331 CE1BC4

100000050

TO

F001

400000005

TO

TMOO

400000052

TO

TMOO

Q /SCMTMSrTOfi • ©ROOT

BO Node instances found by a Query.

© 005056 X 05011ED

[A 9 9.

TC*_TYPe CR£AT10N _ TYP.. CCNSOt_TYF

BC Node instances can be BO created, deleted, updated. A , Actions can be executed, Associations can be followed for navigating through BO Model, etc.

M

© X 60 % 3f 05 D 21ED084B5 7AA0EA 307324

9 X 60563T05C 21EDCB466EBGC19CB3324 9 0 C50563 FC5D215D 0B4D 36F5607 D 7F 324

Node Instance Edtor

© 0050563 F05021 EOC650 E 707972800324 © X 5 O563F05 D21 ED0BSACCF 72991 EB 324

&D 09D 9M H BO SJHDBCMVODM

© 0C60563f05D2iaxe7D8316fe769F6492 ©

X 6 O563F05O21 ED0B 7E8498 S0B 7DC 492

©

OCG0563F05 D 21EDOB9AGCCADOCAOGOFA

KEY

0050563F05D 11ED 1EF620 Q2331CE1BC4

PARENT _ICEY

OOOOOXIOOOOOOOOOOOOCKKDCOOOOOOOO

ROOT _*EY

0050563F05011 ED 1BF62002331 CE1BC4

TORJD

00000000006100000050

TOR.CAT

TO

TOR.TYPE

1000

a .i.-_DBtan•..._.d onutamvmtu

CREATICN.TYPE

M

9 0050563F05D 21ED069A 6FC0246 EE lCf A

C0 NS0 L_TYPE

© QC60563F05 D21EDOB9 A 7TO6783DOOCFA

aOCK_ft£A 9 CN 1ADO TVT

© OG6O563FO5 D21 EDOB9 A6EC0B 4A04COFA

© 0CSO563R] 5D 21HX ® 9A 3196eP?28 f;C*;A

-

wMi CilhrvWrirtcvi

W

The BOPF Test Tool allows testing the functionality of a Business Object, including creation of new instances, changing and deleting existing instances and using Associations for navigating through the BO Node structure or navigating to oth er related BOs.

Figure 10: Testing Business Objects (1)

•

Start Transaction /BOBF/TESTUI.

•

Enter e.g. BO /SCMTMS/TOR

•

Execute a Query assigned to the ROOT Node — ROOT_ELEMENTS.

•

Enter Search Criteria (e.g. a know TOR_ID) — Execute.

•

Mark found TOR Root Node instance(s) and execute Actions, navigate to Dos or other related BOs (e.g. Location, Cross BO Association)

•

Switch a Node Instance into EDIT mode and adjust the data — Check entries in the Change History.

•

Save Transaction.

ENTER.




Figure 11: Testing Business Objects (2)

•

Start Transaction /BOBF/TESTUI.

•

Enter e.g. BO /SCMTMS/TOR

•

Execute a Query assigned to the ROOT Node — ROOT_ELEMENTS.

•

Enter Search Criteria (e.g. a know TOR_ID) — Execute.

ENTER.

BOPF: Test Business Object

it: l» - iv

,‘SCMTMSjrdR>Boi*

. * .ffi.

bj a |£

B TC

r> BO Node instances found by a Query.

BO Node instances can be created, deleted, updated, Actions can be executed, Associations can be followed for navigating through BO Model, etc.

NcxJoIrtfan m =rtrrr

(§1 A ltitiutn KEY

PAAFNTKFY ROOT.KEY

BO Node instance Editor. In EDIT mode, data of the selected Node Instance can be changed/adjusted.

TCftJt TCR.CAT TCA.TYPE CREATTCN.TYPE COCCI _TYPE eu w .REASON LAKlEXT

Erfwrtenwnt Domo Ounje

PARTNER.PEE_JD PARTNER.M R JC PAATNERJO .JC .STATUS

PARTNERJRR.BCW t«L.ISfO(rXi_DATE

O.J/AEO a.NUV ESt .STATUS a_M.WR_FP<

ajoctiiv

pass* CGO.POCATC* peso

CXj0 _O€ 0 <_RTAQR

Figure 12: Testing Business Objects (3) 4.




•

Mark found TOR Root Node instance(s) and execute Actions, navigate to Dos or other related BOs (e.g. Location, Cross BO Association).

•

Switch a Node Instance into EDIT mode and adjust the data (either directly in the upper list of node instances or in the Node Instance Editor for a selected Instance) — Check entries in the Change History.

•

Save Transaction (CTRL + S).

Transaction BOB BOPF Enhancement Workbench for Customers and Partners



Enhancement Capabilities: •

SAP Standard Development release BOs, Nodes and Actions to be extensible

•

Existing Standard BO Nodes are enhanced via DDIC Enhancement Include available on all released nodes

•

New Subnodes can be added to the BO Model

•

New Determinations can be added to BO Nodes Restriction: Transactional point in time only After Modify & Before Save (Finalize). In case o f transient nodes: After Loading & Before Retrieve. Restriction: They always run only after all standard Validations have been executed.

•

New Actions can be added to BO Nodes.

•

Pre- and Post Action Enhancements can be defined.

•

New Action & Consistency Validations can be defined. Restriction: They always run only after all standard Validations have been executed.

•

As per NW 7.31 it is also possible now to create your own partner/customer specific Business Objects via the Enhancement Workbench.

•

The latest version has added further Enhancement Capabilities: -

Developing complete custom Business Objects. Further Determination Patterns supported (Create Properties).

•

For all types of Enhancements, a Wizard (guided procedure) is used to let users provide the required meta data for an Enhancement.

•

Other required elements of an Enhancement are generated automatically when finalizing the Wizards. Example: The implementing class of an Action gets defined in the Action Wizard and is generated on finalizing it. The developer just needs to implement it.



Transaction BOB

bo pf E nhancement workbench: QpCpen Enhancement

Existing Enhancement Objects

□ CreateEnhancement

n k n#*s ChaprTHrnrrvt I* Enhancement Objects • $ ZENH TOR * Q Business Objects 9 /BORl/PPf _OUTHJ T.CONTENT © /SCMTM5/AVAl_RES_CAPACtTY

nevnntrn Erharcement Objects Demo Enhancement Object for TCft Bushess Objects PPFCutout Men*: Output t-lstory DOAvatabieRp
-

B O P F E n h a n c e m e n t W o r k b e n c h : ZCA

© /SCMTM5/RJP

Creating new 1* ^ Jt'-
© /SCMTMS/I

DaioErtwicemcrl Coact ft»TOO B u k i n s C o. ec t C T t y j K X

• O CC_CH5_T»

-9

© /SCMTMS/FCR © /SCMTMSyHfl

• Q> oowmtu'notMsnc

• •

© /SCMTMS/W © /SCMTMS/LOCATION © /SCMTMS/MA tBRJAL

•

rusTOfi.arTr/Ty

W Q>

Q > l I _•»<»•
© /5CMTMSyOPERATlMjTIMES © /SCMTMS/PLM

Transport*

© /SCMTMS/W-N_EXPE

Enpan ptar

© /SCMITMS/SOCDCLE © /SCKTMS/SUPPFflElGHTltiVREQ

SchecUe

* ts*a - *3 TB«M«*£aceST.-M - 3 IMCRMMQUMt-M S TtutttrotvT OVA »•

Fieagnt se

vSTctCt^rOETC.^ -t

© /SCMTMS/9UW.IER

S (€ TACTrate

© fSCMTMS/TACTJIATES

Enhancement BO with nodes of Standard BO that can be enhanced

Erfity

>2rac€«r«E5rcs*~fc 2i'0P-*WPT lo »d t - vSlttN IH-4000*- • • <2«oo'~aco.*mt*i

•(SHOO'-^cojojrt, •

The List of Standard BOs that can be enhanced by creating a related Enhancement Object

-

2 lT3*.TR-«CJ>. _

3»JXi'~*CCJJJtr • .S u m mi -*oo a. lie

-‘I

Enhancement Options for BO Standard & Enhancement Nodes Enhancement Options for BO Standard & Enhancement Actions

^Mte BCJt

Enhancement Details Section

IUWUM

Standard Actions of the selected BO Node that can be enhanced

Figure 14: Creating Enhancements for existing Standard BOs

Figure 15: Creating Enhancements for existing Standard BOs



Transaction BOB Further Enhancement Examples: •

Start /BOBF/CUST_UI and take a look at the Enhancement Objects ZENH TOR and ZENH TRQ. Both example enhancement objects contain examples for BOPF entities that were added to the standard corresponding Business Object via the Enhancement Workbench. Related implementing classes can be found via the added BOPF Elements or directly via transaction SE80 —> Package ZENH PACKA GE -*• Classes. SE80 —>Package ZENH PAKCAGE —>Programs contains two demo reports that can be executed to get an impression on how BOPF is used in discrete coding. Both reports have hardcoded break-points to stop at interesting places during execution.

ZREP BOPF DEMOl demos different Read Access procedures. ZREP B0PF DEM02 demos how to create new BO instances and handle transactions.





•


•


•


•






•


•


•


•










Unit 3 Floor Plan Manager (FPM) and BOPF Integration Unit Overview


Explain what FPM is and what it is used for

•

Explain the basic entities of a FPM-based UI like GUIBBs, Feeder Classes and Wire Model

•

Understand the basic steps how a FPM-based UI is build

•

Understand what FBI is and what it is used for

•

Understand the basic steps how a FPM UI interacts with a BOPF application via FBI

•

Explain the basic entities of an FBI view and their usage

Unit Contents Lesson: Floor Plan Manager (FPM).............................................................32 Lesson: Floor Plan Manager BOPF Integration (FBI)................................38 Procedure: C onfiguration of a TM User Interface (FPM / FB I) .......... 46



Lesson: Floor Plan Manager (FPM) Lesson Overview In this lesson you will understand the basic concepts of Floor Plan Manager and how the SAP TM User Interface is build.



•


•


Business Example

FPM - Floor Plan Manager What is it?

•

Since SAP Transportation Management 8.0 the Floor Plan Manager (FPM) is used to realize TM User Interfaces.

•

FPM is a Web Dynpro ABAP application that provides a framework for developing new Web Dynpro ABAP application interfaces consistent with the SAP UI guidelines.

•

FPM allows a modification-free composition of discrete User Interface Building Blocks (UIBBs) which are compliant with the mentioned guidelines.

Why FPM?

•

Rapid development and implementation of running User Interfaces that are compliant with UI guidelines.

•

Flexibility to adjust the UI without the need for coding — Configuration. In the Transportation Management Business it is hard to define one unified UI that fulfills all customer requirements —>UIs and the process steps realized with it look different from customer to customer. Enables process-specific configurations of a UI and allows building UIs independent of the representation of content in the backend application.

•

Reuse of UI parts in different application areas.

•

Personalization is supported.



Generic Ul Building Blocks provided by FPM (Generic) Feeder Classes provide the application data to the GUI BBs

Building Blocks developed for a specific , purpose. Ul

Application

Figure 16: FPM - Floor Plan Manager

How to build a FPM Ul?

•

The Web Dynpro ABAP Floorplan Manager (FPM) is a framework which composes application specific views (UIBBs) to an application. This allows a homogeneous high-level application structuring and interaction behavior.

•

Instead of building the User Interface as an individual Web Dynpro Application, FPM centrally provides predefined UIBBs, so called Generic Ul Building Blocks (GUIBBs) that can be reused to create UIBBs.

•

GUIBBs used in the TM User Interface are: Overview Pages (FPM OVP COMPONENT): Defines the general layout of the screens. It displays a title bar, a tool bar as well as one or more UIBBs Form GUIBB (FPM FORM UIBB): A flat collection of input elements which displays the content of a (flat) structure —* must use a form-compliant Feeder Class List GUIBB (FPM_LIST_UIBB): Displays the content of an (internal) table —>must use a list-compliant Feeder Class Tree GUIBB (FPM TREE UIBB): Displays the content of an (internal) table in a hierarchically way — must use a tree-compliant Feeder Class Tabbed GUIBB (FPM TABBED UIBB): Used to display a tab strip including further UIBBs with an optional master UIBB on top of it —>does not require a Feeder Class (sometimes misused for layout purposes which it was not designed for)

•

GUIBBs are design templates for which, at design time, the application defines the data to be displayed along with a configuration



•

The composition (configuration) of those building blocks takes place in a design time application (in this case a Web Application) where all the necessary field attribute, positioning and layout properties are assigned or composed

•

The application only provides the data and a layout configuration to the GUIBBs

•

The rendering is handled by the framework itself

•

GUIBBs provide a comprehensive way of creating or changing User Interface Compositions, without the necessity to change the underlying application code base and thereby offering a concept for modification free customer UI enhancements

•

The concrete display of the data on the user interface is not determined and generated by the GUIBB until runtime. This is done automatically using the configuration provided to the GUIBB.

•

Necessary or mandatory application specific information will be supplied by the application itself via a so called Feeder Class implementation.

•

Feeder Classes are based on a predefined interface definition providing all necessary methods and corresponding signatures for standardizing the communication between the application and the GUIBB.

•

With these Feeder Classes the application Provides a field catalogue to the GUIBB design and runtime -

Provides the data at runtime Accepts UI changes at runtime by calling application middleware Handles user interactions (events) at runtime by calling application middleware Provides field control data to control visibility and changeability of UI elements

•

The UI Administrator or Designer can Create UI layouts as a Web Dynpro Configuration for the standard GUIBBs Put together such discrete GUIBB configurations in an application configuration Important Interface Methods (FPM phase model - Event Loop) INITIALIZE: Called at runtime when the form is created. It is the first feeder method which is called from FPM. GET DEFINITION: Allows the feeder to provide all necessary information for configuring a form: the list of available fields and their properties and the list of actions (FPM events).



FLUSH:

The first feeder method which is called during an event loop. Whenever an FPM event is triggered (this includes all round trips caused by the form itself) this method is called. Use it to forward changed data from the form to other components in the same application. PROCESS EVENT:

Called within the FPM event loop. The FPM PROCESS_EVENT is forwarded to the feeder class. Flere the event processing can take place and this is where the event can be canceled or deferred. GET DATA:

Called within the FPM event loop. The FPM PROCESS BEFORE OUTPUT event is forwarded to the feeder class. Here you specify the form data after the event has been processed.

•

With the FPM approach, it is possible to enhance application user interfaces and fit them to your business needs, based on configuration instead of modifications. Besides the GUIBBs, FPM still allows the implementation and usage of freestyle UIBBs that can be realized individually to serve specific purposes that cannot be handled via GUIBBs.

•

At runtime, user interactions are handled by FPM events that pass an FPM phase model (Event Loop).

•

Within the FPM event loop specific methods are called that are based on a predefined interface definition and corresponding signatures in order to standardize the communication between the application and the GUIBB.

•

A Feeder Class implements such a predefined interface for a specific GUIBB, e.g. the interface IF FPM GUIBB FORM for Form components.

•

Wire Model: The wire model is used to create a running FPM application by pure configuration (or at least with a minimal coding effort). The runtime interdependencies between UIBBs are defined by configuration entities called “wires” which are based on reusable “connector” classes implementing the dependency semantics. The primary use cases for the wire model are object models with generic access interfaces like BOPF. A wire controls the runtime interdependencies between two UIBBs, i.e. they determine the data content of the target UIBB depending on user interaction changing the “outport” of the source UIBB. Outports can be of type lead selection, selection or collection. For example, changing the lead selection in a list of Forwarding Order Items may change the data content of another list displaying the associated Item Details.



Application areas or object models define their own namespaces for which their connector classes, feeder model classes can be reused. Moreover, they typically need to provide a transaction handler class which manages transaction events like “save”, “modify” or “check” and global message handling. Wires are defined on the level of the Floorplan Configuration. For each model UIBB contained in the Floorplan Configuration, a source UIBB with specified outport can be defined. Furthermore, a connector class and, potentially, connector parameters must be maintained. If the Floorplan contains composite components (tabbed components), the model UIBBs contained in the tabbed components can also be wired. However, in order to provide better reusability of composite components, it is also possible to define intrinsic wiring for tabbed components. A tabbed component can define a model UIBB as a “wire plug” (this is usually a master UIBB), which serves as an entry point for the wiring of the tabbed component from the enveloping Floorplan component. If a wire plug is configured for a tabbed UIBB, only the wire plug UIBB can be wired from outside.

Âpplication

Application Configuration

Component Configuration Overview Page (FPM _OVP _COM PONE NT) Initial Page

Main Page

Toolbar

Toolbar

Section 1

Section 1

r

Form UIBB (FPM_FORM_UIBB) Alternative Key Feeder Class Wires Form UIBB (FPM_FORM_UIBB) Bootstrap Feeder Class Class

V J

Form UIBB (FPM_FORM_UIBB) Form Feeder Class

W , _____________

Figure 17: FPM - Application





•


•




Lesson: Floor Plan Manager BOPF Integration (FBI) Lesson Overview In this lesson you will understand the basic concepts of the Integration between the FPM User Interface and the BOPF-bascd TM backend application.



•


•


Business Example

FBI - Floor Plan Manager BOPF Integration What is it?

•

The Floor Plan Manager BOPF Integration (FBI) is used integrate FPM with the BOPF-based Business Objects.

•

FBI provides generic FPM application Feeder Classes together with the relevant application configuration that allows consuming services of Business Objects modeled in BOPF. These BOPF services can be used seamlessly in a modification-free UI environment.



Why FBI?

•

Rapid development and implementation of running User Interfaces by reusing generic Feeder class implementations provided by FBI

•

FBI provides the following functionalities that support the communication and corporation between FPM applications and BOPF-bases Business Objects Editing data of BO node instances in the standard GUIBBs FORM and LIST Accepting action parameter values and invoking corresponding actions on BO node instances Overview Search (OVS) based on BO node queries Input of external IDs on initial screens and subsequent conversion of these external IDs into internal (technical) IDs (Alternative Key Conversion) -

Ul-specific services are supported: Navigation to multiple targets - Calling dialog boxes and editing application data in these dialog boxes - Support of Ul-specific non-BOPF actions

At runtime, user interactions are handled by FPM events that pass an FPM phase model (Event Loop). Within the FPM event loop specific methods are called that are based on a predefined interface definition and corresponding signatures in order



to standardize the communication between the application and the GUIBB. A Feeder Class implements such a predefined interface for a specific GUIBB, e.g. the interface IF FPM GUIBB FORM for Form components. Important methods are: •

INITIALIZE: Called at runtime when the form is created. It is the first feeder method which is called from FPM.

•

GETDEFINITION: Allows the feeder to provide all necessary information for configuring a form: the list of available fields and their properties and the list of actions (FPM events).

•

FLUSH: The first feeder method which is called during an event loop. Whenever an FPM event is triggered (this includes all round trips caused by the form itself) this method is called. Use it to forward changed data from the form to other components in the same application.

•

PROCESS_EVENT: Called within the FPM event loop. The FPM PROCESS EVENT is forwarded to the feeder class. Here the event processing can take place and this is where the event can be canceled or deferred.

•

GETDATA: Called within the FPM event loop. The FPM PROCESS BEFORE OUTPUT event is forwarded to the feeder class. Here you specify the form data after the event has been processed. Note: Note that FBI has an own Buffer for Node Information, Field Properties, etc. to gain performance, i.e. it does not have to read this information from BOPF again every time it needs to access it.

Concepts and Entities of FBI:

•

FBI Views (Design Time): FBI Views are the place where the design time UI structure of a building block is defined Moreover, it contains the classes for conversion/mapping of BOBF BO data to this UI structure An FBI View is closely related to a single BO node But “Related Views” are also supported. They allow extracting data from multiple BO nodes into a single UI structure Actions that are not related to the BO are also defined in the FBI View (FBI views are stored as a configuration of Web Dynpro Component /BOFU/FBIV IEW)



C o m p o n e n t C o n fig u ra t io n /S C M T M S /F R E _ O R D E R _ IT M Freight Orde r Item 1O m m II Mew VWedtw || Checfc]

| Retreeh |

View

Component-Oefrtd

~

Example FBI Vie w for the Freight Order Items screen.

Figure 19: FBI - Floor Plan Manager BOPF Integration (2)

Header:

•

Contains the mandatory part: Business Object and Node.

•

Optional UI Structure (if not specified, then node structure is used).

•

Optional Mapper Class (if not specified, MOVE-CORRESPONDING is used).

•

Optional Exit Interface Implementation Class (details later).

•

Additional settings, like Read-Only, etc.

Related Views (optional):

•

Allows the definition of a chain of Views to read data from more nodes (e.g. when information coming from several nodes shall be combined into on flat UI structure to be displayed in a list).

•

Each related view is included with a mandatory suffix.

Field Descriptions (optional):

•

Can be used to specify additional properties for structure attributes.

•

These settings are passed to the FPM field catalogue.

•

E.g. Sorting Allowed, Allow Filter, Domain Fixed Values, Fixed Values, F4-Values from Code Value List etc.



Actions (optional):

•

Allows definition of new Event IDs.

•

For the new Event IDs, as well as for the existing ones (Standard FBI and BO Actions, which are taken into account automatically), you can specify additional settings: Set specific Name and Tooltip (via OTR aliases) - they will be passed to the FPM action catalogue. Specify another Event ID, whose enable/disable properties are to be inherited. Specify whether the action is allowed to be triggered in read only mode. Specify whether the action is allowed to be executed only when a record is selected. Specify navigation target (in this case, FBI calls Navigation Class instead of Standard handling).

Concepts and Entities of FBI:

•

FBI View Instances (Runtime): The instances of an FBI View hold the keys of the displayed instances (coming from the wires that UIBBs are connected with) An instance e.g. prepares modifications, executes actions and posts change notification to the controller It reacts to the FBI-specific SYNCTJP Event, i.e. it evaluates change notifications and determines which of the keys must be refreshed Moreover it reads the data from node butters or from the BO layer in case of modified keys Where required it also calls conversion classes for the modified records (e.g. to convert a document ID into its corresponding technical key) A view instance calls available Exit methods at the appropriate places

•

FBI Controller: The FBI controller is responsible to do the orchestration between FBI View instances and the BO layer It does not contain any application logic but only provides the technical framework for the orchestration It provides a Modification Butter for changes done on the UI that are then forwarded from there to the BO layer, i.e. it centralizes the BO Layer responses It also collects the change notifications coming from the BO layer that then need to trigger updates on the UI Further buffers hold the information on the nodes read from the BO layer and the properties of nodes and their attributes



The properties determine e.g. whether an attribute is a mandatory field or is ready for input. Moreover, these buffers help to avoid redundant BOPF service calls Conversion Classes: When data is send from the BO layer to the UI, the conversion class is called to convert technical attributes into their clear text representation The same conversion class is also called when data is send from the UI back to the BO layer, i.e. it converts clear text information in to its technical representation Conversions are done immediately after retrieval of data and shortly before sending modifications to the buffer. A conversion class is specified in the FBI View definition Example Conversion: Mapping rule for Date-Time Conversion The conversion rule maps a field of type TIMESTAMP into its Date, Time and Time Zone part A BO node attribute FIELD of type TIMESTAMP is automatically converted with this rule if the UI structure contains the attributes FIELD D (Date), FIELD T (Time) and FIELD TZ (Time Zone) The conversion from the three attributes back into a timestamp is also done when required — bidirectional mapping. When data is send from the BO layer to the UI, the conversion class is called to convert technical attributes into their clear text representation. The same conversion class is also called when data is send from the UI back to the BO layer, i.e. it converts clear text information in to its technical representation. Conversions are done immediately after retrieval of data and shortly before sending modifications to the buffer. A conversion class is specified in the FBI View definition. Implementations of Conversion Classes do always inherit from TM super class /SCMTMS/CL_UI_CONVERSION. Each redefinition of the super class must define its own mapping table in method BUILD JAAPJTABLE. The super class already contains a few generic (bidirectional) mapping rules which are based on field naming conversions: The conversion rule maps a field of type TIMESTAMP into its Date, Time and Time Zone part. A BO node attribute FIELD of type TIMESTAMP is automatically converted with this rule if the UI structure contains the attributes FIELD D (Date), FIELD JT (Time) and FIELD TZ (Time Zone). Mapping rule for Date-Time Conversion:

The conversion rule maps a field of type TIMESTAMP into a String. A BO node attribute FIELD of type TIMESTAMP is automatically converted with this rule if the UI structure contains the attribute FIELD TTT (Formatted Date). Mapping rule for Date-Time Conversion into String:



The conversion rule maps a BO node foreign instance key into its corresponding foreign readable ID. For this, it uses e.g. the BO key, the BO node name and the alternative key for this node defined in the node Meta Data. Mapping Rule for Alternative Key Conversion:

The conversion rule maps a BO code into a readable UI code value. A BO attribute FIELD with its code value X is converted into its readable UI code value if the UI structure contains the attribute FIELD TXT. Mapping Rule for Code List Conversion:

•

Exit Classes: The generic feeder classes provided by FBI usually take care of all communication aspects between the corresponding GUIBB and the application Nevertheless there might be use cases that require a more specific implementation For this, an Exit Class can be specified in the FBI View definition Exit Classes provide many extension options and are the recommended means for adapting the standard FBI processing to customers and partners needs An Exit Class implements a predefined FBI Exit Interface Example Method of an Exit Class: ADAPT EVENT Intercept and process any event that arrives in the underlying FBI view. If custom event IDs were added to the FBI View, this is the place to implement the action handling for them

The generic feeder classes usually take care of all communication aspects between the corresponding GUIBB and the application. Nevertheless there might be use cases that require a more specific implementation. For this, an Exit Class can be specified in the FBI View definition. Exit Classes provide many extension options and are the recommended means for adapting the standard FBI processing to customers and partner’s needs. Exit Class implementations inherit from TM super class /SCMTMS/CL_UI_VIEWEXIT CMN. An Exit Class implements the following FBI Exit Interfaces: Core Interface /B O F U /I F _ F B I_ V IE W _E X IT _IN T F: The

interface does not have any interface methods but the Exit Class implements it for enabling FBI to instantiate an object from this class.



Definition Interface /BO FU /IF

FBI VIEW EX IT IN TF DEF: The methods

of this interface offer the possibility to influence the processing of FPM phases Initialization and Get Definition (“one time” phases). Its implementation is optional. •

Method ADAPT FIELDS: Modify the field catalogue.

•

Method AD APTACT ION S: Modify the action catalogue.

•

Method AD AP TD ND DE FINITON : Modify drag & drop definitions.

Definition Interface /BO FU /IF

FBI VI E W E XI T I N T F RU N : The methods of

this interface offer the possibility to influence the processing of User Interactions (at each round trip). Its implementation is also optional. •

Method ADAPT_CHANGE_LOG: Modify the list of screen changes before converting them into BO modification records.

•

Method ADAPT EVENT: Intercept and process any event that arrives in the underlying FBI view. If custom event IDs were added to the FBI View, this is the place to implement the action handling for them.

•

Method ADAPT MESSAGES'. Modify the returned messages from the Modify and DO ACTION service calls.

Method ADAPT DATA: Modify the data before it is passed to FPM. The data is in the concatenated format (all related views in the chain plus the reference fields). Thus, the component of the UI structure must be accessed with ASSIGN COMPONENT...

Method ADAPT FIELD PROPERTIES'. Modify the field properties of this view (at column level, these values are merged with the properties from the reference fields of the data structure). Method ADAPT ACTION PROPERTIES'. Modify the enabled/disabled properties of this view’s actions. Method ADAPT SELECTION: Modify the selected lines (in list and tree).



Configuration of a TM User Interface (FPM / FBI) l.

2.

<5

P«M OCO *riia:

ni*i

*

3.




RepositoryInfo System: Find Component Configuration

1

_

B

ifiRt|xotc»« -rtctTMtcrS’/acm

.tan k'd CetectM*

*'**»'* I®I

CtrroneTt CtrAgieatKn Web Drrprc CofTpdrert

Tot Oexitron RepositoryInfo System: Component Configurat Find(127 Hits) ^ ^

7

'V

**

SL

o

& 9 Q

Q 7 K

^

S

*

.

j

itr.e Let ►*?« .-deU

Use SE84 to search and navigate to the Component Configurations. Select the required Component Configuration. Example: General Freight Order Ul.

* C j Repeater?trrorm rcn S«>.bh

• LJOrxterrcrt cartkutTi • O Bleren Ergree-rg

• O MAHIktowv • LUf»oo»-iLtr

•

Wet)Djr*TO • (3 Weetyi pro Cotrccoant}

<3

• Q wee L'f'trj apptut.

• GQwee rvw c^ ps • HI Ulll WK I C l/ll v/CK l

•B) M&sKnCor*&mn

O0SPUf*7

•

• dJErtea»»* it w • d)Frtwr<«rwiK • 3 T«t ctr»:ts » i~~Irrtw rfww ____________

Click here tc start the Configurator or display the Configuration.

Figure 22: Example: Freight Order Ul (3)

4.


5.




Preview with all further components used in the selected Ul -» Navigation to sub components and their configurations

Navigation list with definitions of e g initial screen and the main page of the selected Ul

Attributes of the selected Ul element can be defined / adjusted here

Figure 24: Example: Freight Order Ul (5) 6.

t\« oinAvurwuu fi

wr_

•••

b

4

t »*\

»

n un-iww i Page Schema with all Sections of the Ul and related UlBBs

• •

D« •« T

9*

jms •• <4K>a W (A> tm"*<

"ftn

Navigation list with definitions of e g initial screen and the main page of the selected Ul

In Edit Mode further Sections, UlBBs, etc can be added Navigation to UIBB configurations

Attributes of the selected Ul element can be defined I adjusted here





C o m p o n e n t C o n f i g u r a titi o n / S O I T S & / W D C C _ r R £ _ O R D E R , S t a in in S c r e e n “i“i O T R : / S C M T M S / U I _ 0 * \ l / B O _ \ A ' t C _ F R I G H T O R D £ R "

✓ C«5, HVftoM Kn « 6wwnie*M ees .pt <•>*;H Ptje T IWbir ir M T SO TR .SC M M 5 - frwviwIt at Ulttnt ImBiiMmm i*tSiMni 1 ---T »«ft DuM t* V4 VIMy — fi D . t Ji«biona . girt gi rti i s o w a MjfOo lO AD.TCtfVAlElO n.tSC M TM S • B'JBOIOW A 1 lom Aranws rwrt.fr •nr = • gU6BO IW A C tatogB c* . . - - irt- ioir. _ v_ m inu g u a e t o w A .. c««iqan cs.w .ww >OT«tAxne Tn««ro .ic*» ton.SoVnts •. 5| 5|l*»»IO IOW A rw-^rv rv. cusrcM S.bR OM HUSO tfM S. L»>otk. ATTJJST lOW ACfUW - Buboiowa C *»*)&:: oarw Air to tornsame • “ Toot* • Suestow* cw*tc* oscs.Mcres aom .scw ne Ufeafe* (M i.oo_SE.ipnm wAcxnws 7^MB IO IOW A AIM IM CwttgBct C R B AIl.tTOIoW s Ctoql*. K'TEJV OTJfT_AT.... . Bibwiowa

Too*

l m mj mj

tj

£j

Toolbar Schema with all Elements t appearing on 3 the Toolbar. In Edit Mode, further Toolbar Elements can be added.

» tt UN* tOTR*CMIM&M_CMMIOTCS

Navigation list with definitions ofe.g. initial screen and the main page of the selected Ul.

Cielou. fca r
Attributes of the selected Toolbar element can be defined / adjusted here.

[«!•

8, C o m p o n e n t C o n f i g u r a t io io n /.SC'U'-rS/ i VD VD CC CC ._ H i t _ o n U t > C . f a i n S c r e e n “ t 0 1 1 t l/l/ 9 Q H T M S / U I ^ 0 1 N / B O . \ A M t _ f K I O H t Q P D t l t *

Toolbar Schema with all Elements appearing on the Toolbar. Toolbar.

In Edit Mode, further Wires can be added to connect e g. new UIBBs to the existing Ul. Navigation list with definitions of e g. initial screen and the main page of the selected Ul.

Attributes of the selected Wire be defined / adjusted here.


9.




C om ponen t C on figura tion /S O fTyiS/W O C
0« t:

171 1IQ

ruxtcnsa cnsa

$O TR:/S C »tTM S /U I_C '4H /BO _\AM E_f:fUGH TOBD £R

g|»OTO<9on»*sw.o**«5*vr

x *oi*®c *n«su _:* (scvmûjcvBirtxT txT

»-R -RiJCMT«*|*|_C*** **TOC3Xt» VPTRXlCV
to-o.rev*'.*!* t O T R S C M T M S . ovMCjom CCMaMD_LM_

Q

»^«*ff*M_C***CA tCU»rc_CMa«> £S. • O m ^ O a T V 3U 3U _ O r t i< S C K » X f *3 *3 \ k u _c * * s £ t _ st .»t ' j j 3 a » * * c c w TM T M S A i .c.c tM tM a j K ow ow r st s t ot ot m j * t o n t M M i m u i M t M O . *<: t r v m t \ » 0 ' R C C W T M SA SA » _ C* C* * * 9E 9E T _ TB TB * J ST ST A I US US a *0T R© CH HJU _C»* U!Fv C«_J «me 4T »HJSCMT»64J_C **JW»IT a

csjonr

ir./to i j.ozu

cusrcMS.ifto

10TK.S .SCM TM S. lowmow

M ifl ko

ACTJJST

C«5fl0C<

OGC* Air

(OntSCMIMS

OSCRJKMES

Kim.SCMTMS.

0:<«ixlt Lt* j

l * J <* C l ^ C i T E

Cc/rtju«Sc'.w»ne P_WJTe_TC«"

cHLOojsnjai OWAItJNtl MPTCJV

tO fft ACM1NS. ocru«wr>c-.

jd jd > • «

Navigation list with definitions ofe.g. initial screen and the main page of the selected Ul.

U

C B

l

Click on the icon in the right upper corner to get to the configuration of the selected VÛIBB

«rwje x

t O l f t * C M I M & « . C M M I O T ( S

MCMINB*WCCJX>J«>1£_]0*1

pmM~*

MxaK iOmhuti

Figure 28: Example: Freight Order Ul (9) 10

.

Figure 29: 29: Example: Freight Order Ul Ul (10) (10) 11 .




12.

io n if C o n f i g u r a t io

/ H C ' - II > t S / W [ ) C C f O H _ Gt.V_O A i l \ +

[L □ ’

rv The Feeder Class in this example is the generic Feeder Class for Forms ^ provided by FBI FBI CCWT WT .CIrt .VA

ll*flC N 1 V * .I

CCUflRYj*

h w . ccujt MtCP P..CC CCWJT.

I Espywre.i DU>_S1W_T*’E fE5 w w ( ( EEEC.GWLO [ twc.wiy.c.

General Settings with definition of Feeder Class and Feeder Class Parameters.

The assignment of a FBI View to the Feeder Class of the example Form UIBB. Further Feeder Class Parameters are also specified here.

Figure 31: 31: Example: Freight Frei ght Order Orde r Ul (12) 13.




C om ponent C ustom izing /S O tT?S /W D C C _FO R _G £M _G rvI\f

• ft*0*r*Mn CouMirtt

10 -

u 13 14

i

a

wngrt

ca

VMM. TrMCr

LflJ •TMV

3

AiganiwtartiM

General Settings with definition of Feeder Class and Feeder Class Parameters.

L

3 ;««l Art-•>

.«• *cMf

l

a

[_

Nvrtr**c<-Isli.

— 19v<«t

irm

1*

<

It M » [nhaxpixpnl Croup

l ** 19

Form UIBB Example: List of all fields available to be displayed on the Form -> will also include extension fields added to the related BO Node.

•MM.

* i 21

o cotooxo

73

rj»y

HI

Carpi VMM— 1 Maca—

M

1

~ a l

ai

d FrM‘to*- X

S ------------- N Attributes of the selected Group can be adjusted here -> Position of Header and size of the group.

Cot M Kefir Cl

C«r>triune

An example Enhancement Group with 3 Extension Fields.

v itut


C om ponen t C ustom izin g /SO tJ>tS /W D C C _F O R _G £M _G tvI\f

mg ovh ocwt msmocc _r°E_c«c" > m m _eo o c miw sy o :c j «£ .c« k *_qcm > r» n ic e <5c»m«s»'©:c_*c*»_OQ<_j4M*'

«4 "J

l - m u m s c lOM i rtoTw«

*t

Form UIBB Example: List of all fields available to be displayed on the Form will also include extension fields added to the related BO Node.

Ip CVMI

* n o * ..

>*» Vi’ii 'jx rv n i : —«*** an

► Zie

W * ^C*«rM5*J_Ct*Me'.C4»MCrY

* □<--

&*r« Ef#— M«r «r; 0>«*p

S>

UM t**»

l«M ViiM ,

Cojaavlip*

• ft.

a VMM*

* C-*t* Baj

ft

kVMlM

•

• ft a ®

kVMM

- r-JPtod

* C K*

w*

mt vbj j_r

va*ai!

* 3 «*

JO'S «ECWri64J.CMtCtCiMtU'eÛAJ>A!A

whom

On the Form UIBB Schema Elements can b be added to the form and « related groups

«-*»» !

T > i a example The Enhancement Group with 3 Extension Fields.

«:/ t—lAI-l-Homll

i. m i

upIBP

SM-1PlowC
f nt Bffocf la

»*

en ccis

I*.

StaetCM«»C

Attributes of the selected Group Element can be adjusted here. Example: Attributes of the first field in the group


Further Demos besides Field Extension:

•

Creating and adding a new List UIBB to Freight Order Ul.

•

Adding a Button to the Main Toolbar of the Freight Order Ul.



FPM / FBI - Further Enhancement Examples •

SE80 -> Package ZENH PACKA GE -

Web Dynpro

Run Application Configuration ZENH ZDB UI to see a demo UI that was build from scratch Under ZENH PACKAGE —* Web Dynpro — Component Configurations you can find further UI enhancement examples, e.g. a List UIBB that was added to the Freight Order UI and contains data of a subnode that was added via the BOPF Enhancement Workbench





•


•






•


•


•


•


•










Unit 4 Queries and Personal Object Worklists (POWL) Unit Overview


Understand what BOPF Queries are and how to enhance them

•

Understand the relation between BOPF Queries and POWLs

•

Find implementation and configuration elements of POWLs

Unit Contents Lesson: Querie s and P O W L s.......................................................................58



Lesson: Queries and POWLs Lesson Overview In this lesson you will learn about the Enhancing Queries and how to create and enhance Personal Object Work Lists (POWLs).



•


•


Business Example

Enhancing BOPF Queries and POWLs Enhancing BOPF Queries

•

The BOBF Enhancement Workbench does not support enhancing existing standard BO queries It is for example not possible to assign a query to the ROOT node, which returns instances or the keys of the related ITEM node The only way to extend queries in the standard BOPF environment is to add further query node attributes to the query structure

•

How to enhance standard BOPF Queries?

All queries of SAP TM are derived from a super class: Class /SC MT MS/CLQSU PERC LASS. This super class contains an enhancement mechanism which makes SAP TM queries extensible in a unified way. The mechanism is based on the query enhancement table (“QET”) /SCMTMS/C_QENH. The query super class provides an API for creating an optimized database SELECT statement to execute the query and returning the requested result table. At runtime the super class is creating an optimized database SELECT statement from the content of the query structure and the query enhancement table. The meta data for the query enhancement can be maintained via report /SC'MTMS/MAINTQUERYENH. •

See Enhancement Guide Document for a detailed example.



Enhancing Personal Object Work Lists (POWLs) •

POWLs are used throughout the whole SAP TM Application to access documents and the related data, not only for displaying but also for processing documents.

•

Customers require the POWLs to also contain their custom fields to be included in the search criteria list of a POWL as well as in the result list.

•

How to enhance POWLs? Each POWL gets its data from a BOPF Generic Result Query. The query used for a POWL must be identified and can be enhanced with the introduced enhancement concept for queries. The other steps require coding enhancements to bring the additional fields into the list of search criteria and result displayed by the POWL. Many customers have decided to implement their completely own POWLs with the POWL Framework instead of adjusting the standard POWLs. In case of a newly created POWL, also customizing is required.

•

See Enhancement Guide Document for a detailed example on how to enhance existing POWLs and how to create a new POWL from scratch.

Figure 34: Example: Enhancement POWL for Freight Orders Demo (if required):

•

Show a POWL Feeder Class via SE24.

•

Take a look at the example mentioned in the Enhancement Guide.

•

The example provided in the guide illustrates also the required customizing steps in case of a newly created POWL.



POWLs - Technical Aspects Ho>v is a POWL implemented?

•

Each POWL is associated with a so called POWL Feeder Class that contains the coding for providing the data and the invocation of actions configured to be available on the toolbar of a POWL. Example Class: /SCMTMS/CL_ U I P O W_FD_TRQ. The CONTSRUCTOR method of this class contains the definition of various

POWL elements: -

Name and node of the BO that provides the data. The Generic Result Query (BOPF Query) that is used to query the data. The output structure, i.e. the list of fields that will be displayed in the result table of a POWL. The select structure, i.e. the list of selection criteria that is available to define and execute POWL Query executions. Action Class name: The assigned Action Class contains the coding to execute the functions and logic associated with the POWL toolbar buttons. Example class: /SCMTMS/CL UI ACTION TRQ. You can implement your very own POWLs by implementing a new POWL Feeder Class (should inherit from class /SCMTMS/CL_UIPO W F D B A S E !) or you enhance existing POWLs.

•

The underlying Generic Result Query can be your own implemented or an existing one. In the latter case you can add additional selection criteria and result attributes by the introduced Query Enhancement concept.

•

In case you need to enhance existing Feeder- and Action Classes you need to work with implicit enhancements — there is no explicit enhancement concept.

•

New POWLs also require further customizing to be shown and used via the UI.





•


•






•


•








Unit 5 Standard Enhancement Techniques in SAP TM Unit Overview


Understand what BAdls are and what they are used for

•

Explain how to find BAdls in TM for a specific purpose

•

Understand how to use BAdls to influence the TM business logic

•

Explain the basic steps how to create a BAdl-Implementation

•

Understand what Implicit Enhancements are and what they can be used for

•

Explain the critical aspects of Implicit Enhancements

•

Understand how Implicit Enhancements influence the TM business logic

•

Explain the basic steps how to create an Implicit Enhancement

Unit Contents Lesson: Business Addins (BAdls) ............................................................... 64 Lesson: Implicit Enhancements....................................................................69



Lesson: Business Addins (BAdls) Lesson Overview In this lesson you will understand the Usage of Process Controller Strategies and how they help to adjust the TM application behavior.



•


•


•


Business Example

BAdls - Business Add-Ins in SAP Transportation Management What is it?

•

The Business Add-In (BAdI) concept is SAPs object-oriented plug-in concept for ABAP.

•

BAdls are used to plug in custom behavior either in an additive way or by replacing the standard behavior.

WhvBAdls?

•

BAdls are a mechanism for planned extensibility.

•

Planned means that the developer of the standard software already anticipates that others may want to change or enhance the standard behavior at certain points in the application.

•

BAdl Interfaces represent a “contract” between SAP and customers/partners, i.e. they have to be kept stable for at least 2 years and are not allowed to be changed in an incompatible way.

•

BAdls represent a modification free concept to enhance business logic at predefined points in a process.



Display IMG ^

3

E xi st in g B C S e ts

-

^

Âctivated BCSets for Activity

Structure

Implementaton Guide -a Q/SAPCustomizing tivateBusiness Functions •a Ac SAPNtWraw Cross-Applicabon Components Financial Supply ChamManagement SAPTransportation Management Transportation Management MasterData BasicFunctions The provided BAdls are Forwarding Order Management Freight Order Management subdivided by application and Planning functional areas. Settlement GlobalTradeServices Example: Tendering. Integration Business Add-Ins(BAdls) for Transportation Management Master Data Basic Functions________________________ Forwarding Order Management Freight Order Management (Do uble click to display the

B

_ „ BAdl documentation.

B

($

B A d l C r e a d o n o f P r op o s a l s f o r T e nd e n n g P la n

3

($

B A d l E va l u a bo n o f Q u o t a ti o n s

S (j r- «^ i DeterminationofAddresses and Contact Persons for Tendering fVv^^wtlon of Freignt Requests for Quotation BAdl FHMvg"t>»^^*^,^rcJy'e for Forwarding and Freight RFQs 3r BAdl

B <& r mi s«nk

Double click to star t the BAdl a | ro u'ijmplementation "

BAdl Restart of tender ing Upon Confirmation Rea ction by Assig ned Carrier

d

Planning Olobal Trade Services integration SCMBasrs IntegrationwithOther mySAPcomComponents

Figure 35: Business Add-Ins in SAP Transportation Managemen t (1) How to find TM-related BAdls?

•

The Business Add-Ins (BAdls) can be found in the customizing (SPRO) for each application and functional area.

•

In customizing/SPRO follow path: SAP Transportation Management —* Transportation Management —* Business Add-Ins (BAdls) fo r Transportation Management.

•

The BAdl Documentation can be accessed

•

The Implementation of a BAdl (method) can be started



BAdI Builder: Initia l Screen for Defini tion t &

0C

II

P

Enter /SCMTMS/* , ___ fE

here and press F4. h

tmtaf

Figure 36: Business Add-Ins in SAP Transportation Managemen t (2) How to find TM-related BAdls?

•

Search for TM-related BAdls via transaction SE18

•

Search for BAdI names starting with /SCMTMS/*

•

The result will also contain the BAdls for enhancing service messages (e.g. integration ERP/TM)

•

> 100 BAdls are available for TM

BAdI Work Modes

•

For some of the BAdls provided with SAP TM it is possible to define a “BAdI work mode” that controls whether a BAdI method is executed at runtime and how it interacts with the SAP TM standard business logic. The customer/partner can decide whether a BAdI method bypasses or enhances the standard business logic. The work modes can be set independently for each method within a BAdI. (e.g. a customer wants to execute method A of a BAdI, but not method B).



There are 3 BAdl work modes:

Standard logic only: Standard logic is executed, BAdl method is skipped Standard log ic

BAd l

I >

Customer logic only: Standard logic is skipped, BAdl method is executed Standaid logic

L

BAdl

Modify standard results: Standard logic is executed first, then BAdl method is executed afterwards, allowing the customer to change the results of the standard logic

Figure 37: Business Add-Ins in SAP Transportation M anagem ent (3)





•


•


•




Lesson: Implicit Enhancements Lesson Overview In this lesson you will understand the risks as well as the benefits of implicit enhancements when no other enhancement option helps.



•


•


•


Business Example

Implicit Enhancements - Adjustment of Coding and related implications What is it?

•

For ABAP programs, a number of so called implicit enhancement options exist, for example: At the end of an include At the end of a structure definition (types, data, constants, statics) At the start and at the end of a method or function module At the start and at the end of a method or function module

•

Implicit Enhancements can be created via transaction SE80, etc., i.e. they are fully integrated into the ABAP Workbench.

Why Implicit Enhancements?

•

The mentioned options provide very powerful means to alter standard code.

•

In some cases, there are no other ways to enhance, for example when adding a type or data definition.

•

Can be used to realize coding adjustments in case there is no other enhancement technology available for the given situation (e.g. BAdls, Conditions, etc.).



What must be kept in mind?

•

SAP strongly recommends to use BAdls instead, since they provide a defined interface.

•

Implicit Enhancements should be used with care (!). The following aspects should be kept in mind when making use of this enhancement technique.

•

Detailed knowledge on the application code is required for identifying the objects to be enhanced for a specific purpose.

•

In case of methods that are not part of a stable interface, the signature can potentially change.

•

This can lead to problems in case a pre- or post-method implementation relies on parameters from the methods signature, especially when parameters might have been removed.

•

Enhancement SPAU might become necessary after updates to analyze conflict situations related to your Enhancement Implementations.

•

In case of overwriting methods by copying the code of a standard method and adjusting it within an overwrite method implementation, you will not get the changes / corrections for the standard portion of your implementation.

&

Class | £drt | Goto

ytAties

Envronment

Chooi©

©

F2

System

a©

Help

SUSS

HE

Ctrt+F

Class

L_ ENH_ D_ DEMO_ DET_AM

Insert kne Dglete Row

oa

D

tf j Local Defirttons/ Implementatia ns

Local Test Classes

Create class constructor Class Interl Propt

Implemented / Active

Create Constructor Create Destructor

.ttnbutes

Create subclass o Parar Method /BOBF/I!

Methods

Events

Types

aiAbt.tLaw.|fl|JWi» tL*i ___ ««

Modhcation operations EQhancement Operations

Insert Pre-Method

Cancel

Insert Post-Method

F12

Insert Qverwnte-Methode /BOBF/IF_FFU_DETERUINATION-EXECUTE

Delete Pre-Method

on Relevant Data Changes aues of Relevant Fields Determnation

Delete Post-Method Delete Oyerwnte-Methode

Example: Display a class in transaction SE24 and follow the path: Edit -> Enhancement Operations ... Here the possible enhancement operations for a selected method can be seen.

0 Activity canceled

t> ZMT (1) 800 -

Wdflbmt2290 INS

Figure 38: Adjustment of Coding and Related Implications





•


•


•






•


•


•


•


•


•


•








Unit 6 Conditions Unit Overview


Understand what conditions are and what they are used for

•

Explain the basic customizing settings required to define conditions in SAP TM

•

Explain how to define a condition in SAP TM

•

Understand how to use a condition to influence the TM business logic

Unit Contents Lesson: C on di tio ns ........................................................................................ 74 Procedure: Creating a Condition............................................................79



Lesson: Conditions Lesson Overview In this lesson you will learn how conditions are used to configure specific TM application behavior.



•


•

Explain how to define a condition in SAP TM

•


Business Example

Conditions - BRF+ Usage of BRFplus-based Conditions in TM What is it?

•

TM makes use of the Reuse Component BRFplus to realize condition-based business logic.

•

Conditions use a set of input values which can e.g. come from attributes of the TM Business Objects. These input values are then mapped onto corresponding output values.

•

The output of a condition can be a simple Boolean which indicates to select a business object instance (yes/no), it can be a simple value like an ID of a business partner or it can be a set of output values which are determined by the condition based on the input values.

•

Conditions are called at explicit points in time / coding places during execution of process steps.

Why Conditions & BRFplus?

•

BRFplus is an available reuse component that already provides the required framework to define, configure and execute condition-based business logic.

•

It enables modification free, easy to use and highly flexible adjustments and enhancements of business logic / system behavior.

•

BRFplus UI for condition configuration and maintenance is reused in in the related TM UI.



SAP Transportation Managem ent Transportation M anagement M aster D ata Basic Functions User Interface Q

Create Active Version and Model

Q

Define General Settings for SAP TM

Q

( £ ► D e f in e S LD D a ta o f B u s i n e s s S y s te m s C harge C alculation D ange rou s G oods Type Codes and Role Codes Text C ollection Conditions

’

S

■

&

‘

O ' ^

D e fi ne C o nd it io n T y pe s

■

C i

Assign Condition Type to Data Access Definition

The customizing for condition types and data access definitions (prerequisite for defining conditions).

iData Access Definition] ^

D e f in e T e x t fo r D a t a A c c e ss D e fi n it io n

G eographical M ap Printing ►

Forwarding Order Managem ent

►

Freight Order Managem ent

►

Planning

r

Settlement

►

Olobal Trade

►

Integration

►

Business Add-Ins (BAdls) (or Transportation Managem ent SC M B asis

Figure 39: Usage of BRFPIus-Based Conditions in TM (1)

Customizing (SPRO) •

The TM-related customizing for conditions can be found via transaction SPRO under the following path: SAP Transportation Management —* Transportation Management —* Basic Functions —>Conditions

•

A condition type defines possible input values as well as the output of conditions of that type.

•

Data access definitions define how the content of the input values is read during runtime. This can e.g. be a generic access to a defined BO, BO node and BO node attribute (can be configured in the data access definition) Or it can be a specific class method that will provide the data (implementation required)

•

A condition type gets assigned one or more such data access definitions. When creating a condition of this type, the input can be build up from these assigned data access definitions.



N e w E n t ri es : D e t a i ls o f A d d e d E n t ri es

I Data Access Def.

; e :;k

Descrption

Enhancement DAD for TORCategory

Data Element for F4 helps

/SCMTMS/T0R_CATEG0RY

1) Enter the Data Access Def.

ca t

(L

BOData Name of BO

/SCMTMS/TOR

Name of BO Node

ROOT

BONode Field Name

T0R_CAT

2) Specify the data element for an F4 help

Fiter 1 : BO Field Name F*er l: Field Value

3) Define the BO, the node and the attribute that shall be returned with the Data access Definition.

4) Optionally, two additional attributes with corresponding values can be defined as filters


Creating Data Access Definitions

•

In the customizing/SPRO follow the path: SAP Transportation Management —>Transportation Management —> Basic Functions — Conditions — Data Access Definition.

The Data Access Definition in this example realizes a generic access to the attribute TOR CAT on the Root node of business object /SCMTMS/TOR with a corresponding data element assigned that provides a suitable F4 help during further usage of the Data Access Definition. As indicated in the example, you can also define up to two further attributes of the same specified node to serve as filters (example: only return the value for attribute TOR CAT if attribute CREATED BY = “POLCH"). This type of Data Access Definition does not require further implementation and can be used right away. Access Definitions making use of the Data Crawler or a Data Access Definition class require some more customizing or even some coding.



Change View "M aintenance View for Condition Types": Details

New Ent ries 1 5 E l Condition Type

&

S 3

ZENH_COND_TYPE

Name of Condition Type and description.

Enhancement Condition Type

Maintenance View for Condition Types

Define whether the result of conditions of this type shall be a structure or a single field -> provide DDIC Type.

I DOnly one condtoon alowed for ths condtoon type Condtion Resot Format |C Result Is a Structure Resu t DOICType

/SCMTMS/PRODUCT ID

80 Data Busress Object 80 Node Name


Creating Data Access Definitions •

Just like Data Access definitions, customers and partners can define new Condition types. In customizing/SPRO follow the path: SAP Transportation Management —* Transportation Management — Basic Functions —* Conditions —> Define Condition Types. Change View "Link between the C ondition type a nd the data access defin NewEntries ^

EJ

© © Q

Lrk between the Condition type and the data access d... Conditi on Typ e

Data A cc es s Def int ion .. .

/ SCMTMS/DTR_TYPE

/ SCMTMS/TRQ_SRC_LOC

/SCMTMS/FUBR

/ SCMTMS/ TRQ_ITEM_PRD

/SCMTMS/FUBR

/SCMTMS/TRQ_TYPE

Example: The Data Access Definitions assigned/linked to the Condition Type /SCMTMS/FUBR.

/ SCMTMS/ FU_LOAD_DURA /SCMTMS/PLNG_MTR / SCMTMS/ FU_LOAD_DURA /SCMTMS/PLNG_SRV_SET /SCMIMS/Etj_LO*I)_DCRA p3tIMS/I0 R_IYPE /SCMTMS/FU_PNLT_COST /SCMIMS/TOR_TYPE /SCMTMS/INC_CARRIER / SCMTMS/SUPPLIER_ID

!1_

-

Entry 48 of 352




Assign Data Access Definitions to Condition Type

•

Just like Data Access definitions, customers and partners can define new Condition types. In customizing/SPRO follow the path: SAP Transportation Management — Transportation Management —*Basic Functions — Conditions —> Assign Condition Type to Data Access Definition When defining a condition of a given type, the assigned Data Access Definitions represent the pool of possible input data for the condition Example: The standard Condition Type /SC'MTMS/FUBR has assigned two Data Access Definitions which serve as input and can be used for the definition of conditions o f this type: The Forwarding Order Type and the Item Product.

Further Enhancement Examples:

•

SE80 — Package ZENH PACKAGE —*Programs

You can find here two demo reports that can be executed to get an impression on how Conditions are invoked in discrete coding. Both reports have hardcoded break-points to stop at interesting places during execution. ZREP CONDITION TEST1 demos a condition that makes use of the Data Crawler as a Data Access Definition ZRE PCO ND ITIO NTE ST2 demos a condition that makes use of a Determination Class as a data provider



Creating a Condition l. Business Client

EJ

D

In NWBC Conditions can be maintained under Application Administration

E On the initial screen, the type and origin of the condition are specified along with a name and a v description

Figure 43: Usage of BRFPIus-Based C onditions in TM (5)

Creating Conditions

•

Prerequisite for defining conditions is the proper setup and availability of the before mentioned condition types and data access definitions.

2.

New C ondition Definition ZE\H_FUBR_O EfitO

H>»•*

^

ChK* [*»»

>

Trmpxt

«>

O '

Click here to define which Data Access Definitions shall make up the input for the new condition.

C*K>*Mn lOwioBri W Co diir Tyac . Oiiar u Ctnffwi • Condition Definition

| c tine 0 « w v « w

SoAOr

St*>

V d» ]

Ml

*««•

ca

i

r»v9

TFienWMsrt ip . Q m o r m n r r g . m . w r a i N r ii W n n n n

o — ]t o ; | to

A

©-

O ennereo

~

9 w *

*1

.ecMiwi-TAiirarv* sc*m»sTAo.TYFe

• s o r t e rw a . T v p f

OuuneM MM A<(««M OM0

Mr

01

Mrloi C w ssAtariMrlw

f la

tar

CX=TO»tC OCStapC

00

Example: Both Data Access Definitions assigned to the Condition Type are selected (TRQ Item Weight and TRC Type) -> For pairs of values for these input fields, a FU Building rule will be defined in the Decision Table for th e condition.


3.




N e w C o n d i t i o n D e f i n i t i o n Z E N H _ FU B f ^_ D E M O B Save

Transport

Check I Data Access Oelnhon

&

2j.

j

• ConStoi

Descripti on !Derno Er#i FU Crq n o* ConStwn

Conditions can be simulated to check functional consistency & correctness.

RJ* Cof'cfc or

C o n d b o n B a s e d o n B W p k J ! D e o s i c n T e bt e

to: UMeJTR Kent Wtiytil.TR; Type

A**Kr»l totor* *

Cxrtext Orarvtew I SUr t SMiuWton '

entries for the decision table

labte Contents o t)

a

r '

TRtetfi

|

1 *1000)3

f ]

*5 O0 R

o l

T1

Tfnl

't*4

Prevnus

TR: Type

r ue Role

fWO (Fgrwsrdrg CrOetJQ

07-rueR-ois

FWO (TorwareSnj O aer

07-meR-02R

Any logical expression, value ranges, etc. can be used here to define a decision table entry and under which circumstances it will be the record that returns the result.

Maintaining the entries for the decision table. The co lumns represent the input value s and the related output values for the condition.


4,


5.




Change View "Forwarding Order Types": Details

tew Entries ries £

Q t®> & S 3

import FWO Type Restrict Processng

_n

ZB

DefaiJt Weqht UoM

RJ BukJng Rule Condtcn Reight Uirt BuMng Riie

Defaut Vdume UoM

Id -'

Defaut Pieces UoM

Z E H Hr U B R D E M O

FlanmgProflte Web Dynpro Conflgwation Default Charges View Crganizaton Crgani zatond d Uhrt Determination

The condition is used for this Forwarding Order Type to dynamically determine a FU Building Rule at runtime when vc re ati ng FUs for this docume document nt type type..

1. Sates Sates Orq. Ccndt Ccndt en

2. v Consider User Assortment 3. Sates Orgarwation

Adrrristratrve Data Created By Changed By

Created On/At T E A H 0 4 -0 4

Changed On/At

X 1 2 . 0 7 . 2 0 1 11 8 : 0 1 : 1 8

Figure 47: 47: Usage of BRFPIus-Based Conditions C onditions in TM (9)





•

Explain the basic customizing customizi ng settings required to define conditions in in SAP TM

•

Explain how to define a condition condi tion in SAP TM

•






•


•

Explain Explai n how to define a conditio cond ition n in SAP TM

•










Unit 7 Process Controller Unit Overview


Understand what the Process Controller is and what it is used for

•

Explain the basic customizing settings required to define Process Controller Strategies in SAP TM

•

Explain how to define a Process Controller Strategy in SAP TM

•

Understand how to use a Process Controller Strategy to influence the TM business logic

Unit Contents Lesson: Process C ontroller........................................................................... 86 Procedure: Creating a new Process Controller Strategy .................... 88



Lesson: Process Controller Lesson Overview In this lesson you will understand the Usage of Process Controller Strategies and how they help realizing specific TM business logic.



•


•


•


Business Example

Process Controller - Usage of Process Controller Strategies What is it?

•

The Process Controller Framework (PCF) allows the flexible definition of application processes. This is accomplished by defining a process as a sequence of methods which represent the single process steps. Such a sequence of methods is called a Strategy.

•

Using the PCF means the definition of an application process as a sequence of methods (a Strategy) in customizing by SAP, partners and customers.

Why Process Controller Strategies?

•

Pieces of functionality can be packed into a method, which can then be included and used in a strategy.

•

Partners and Customers can define their own methods and combine them either to completely new strategies or they can include their own methods in SAP standard strategies, i.e. they also can enhance them with their customer specific functionality.

•

Allows modification free enhancements of business logic.



Display IMG ^ 0 1 ? ]

Existing BC Sets

d^BC Sets forActivity

dJy'Actrvated BC Sets for Activity

SAP Transportation Management Transportation Management SCMBasis Integration Master Data Master Data Layer B< 5> Configure Parameters Alert Monitor Alert Notification Engine Proces s Controller Qr Define Service Define Strategy Or Define Methods Assign Methods to a Strategy O ' ® Define Parameters Or (£ Assign Parameters to a Method Assign Method Parameters to a Strategy Logistics Inventory Manag ement Engine (LIME) Physical Inventory Configurable Proces s Scheduling

.

The configuration of the Process Controller and corresponding strategies is located in s the SCM Basis.

Figure 48: Process Controller Usage of Process Controller Strategies Process Controller

•

The Process Controller Framework (PCF) is located in SCM Basis.

•

In customizing it can be found under the following path: SAP Transportation Management —>SCM Basis —*Process Controller



Creating a new Process Controller Strategy l. C h a n g e V i e w " P r o c e s s C o n t r o l le le r S e r v i c e s " : O v e r v i e w

New Entri ntries es © EJ t* t*$> [g ® Q

Define a new service.

Entry 27 of 31

Figure 49: 49: Process Controller Creating a new Process Process Controller Strategy

Defining a new Service •

A service is the definition o f strategies and methods working on the same process.

•

It is used to clearly separate the maintenance (but has actually actuall y no explicit functional meaning).

•

In customizing it it can be found under the following path: SAP Transportation Management — SC M Basis —* Process Proce ss Controller Control ler — SCM Methods —> Define Methods




C h a n g e V i e w " C o n t r o ll ll e r M e t h o d P o o l " : O v e r v i e w

New Entri ntries es 23 S

g. B D

Ccntroler Method Pool Method

Service

Z E H H J 1 E T H 1Z 1Z E N H _ S E R V

Description

MethType

First Enhancement Demo Method Basic

M e th o d

w

Z E W H _ H E T H 2Z E N H _ S E R V First Enhancement Demo Method Basic M e th o d

w

Class/Interface ZCI_ENH_DEH0_HETH0DS ZCL_EMH_DEM0_J!ETH0DS

Interface Co ComporttQ riRSTJETHOD SEC0HD_HETH0D

"

Define a method pool that can be used to build strategies related to a specific Service.

4

4

Entry 140 of 141

Figure 50: 50: Process Controller Creating a New Process Controller Strategy

Defining a Method Pool

•

All methods share the same interface of an object for providing parameters and a list of mutually independent requests.

•

Some methods comprise functionality themselves, whereas others mainly encapsulate existing functionality (like EH&S check within RGE).

•

There is a method pool for each process, and each method pool contains all methods which the application process requires in order to define its strategies.

•

In customizing it it can be found under the following path: SAP Transportation Management — —>SCM Basis — Process Controller —» Define Methods. Methods.




C h a n g e V i e w " P r oc oc e s s C o n t r o l le le r S t r a t e g y " : O v e r v i e w

New Ent ri es [ Q B

^

g

B D

Process Controter Strategy S tr tr at at eg eg y VSS_DEF

-

Service V3S_SCH

Descriptor)

Crea Create ted d by SAP

Crea Create ted d on Change anged d by 27.10.2009 HU HUENE

YT CHANGE TOR CHACO Change Controller notification

C5157913

2 3. 3. 09 09 .2 .2 01 01 1

Z E W H _ S T R A TZ E N H _ S E R V Demo Enhancement Strategy

S C H S U P P O R T

09.10.2012

ZVSRI_DEF VSR_IlniR ZVSRI.STRATEGY

TEAH02-10

21.07.2011

ScheckJng

j !

ChangedQ 2 3.0 9.2 *

1

Define a Strategy that gets methods methods assign assigned ed to it for execut execution. ion.

A

«

<

Entry 66 of 69

Figure 51: 51: Process Con troller Creating a new Process Con troller Strategy Defining a new Strategy

•

A strategy serializes a selection o f methods from the method pool. It brings them in the sequence in which they shall be executed by the Controller.

•

In customizing customizin g it can be found under the following path: path: SAP Transportation Management — —>SCM Basis —>Process Controller —* Define Strategy. Strategy.




Figure 52: Process Controller Creating a new Process Controller Strategy

Assigning Methods to Strategy

•

A strategy serializes a selection of methods from the method pool. It brings them in the sequence in which they shall be executed by the Controller.

•

In customizing it can be found under the following path: SAP Transportation Management —>SCM Basis —>Process Controller — Define Strategy.

Application Clas

•

The methods in the pool of the Controller are provided by so-called application classes.

•

Method execution by the Controller works (dynamically) since the definition of a new method includes the name of the providing application class. The results produced by a method are passed on to all succeeding methods with the corresponding requests.

•

Alternative: Results are stored externally, if the calling application, but not the succeeding methods take advantage of these results.




5. •

Request: The requests represent the various business demands (e.g. determination of a best route) on an application process. The Controller processes the requests by passing them on to the strategy methods through their interfaces. The requests may further allow storing possible solutions.

•

Demo: Execute report ZREPPROC'C'ONTRDEMO in system to show the depicted Demo Process Controller Strategy working.

•

Process Controller Parameters: (last 3 topics in PCF customizing — rarely used) Parameters influence the behavior of the respective methods, but do not change the sequence in which the methods are executed. The Controller passes them on to each method through its interface. A parameter may not only have different values in different methods, but also in the same method as part of different strategies, or even in the same method of the same strategy as part of different requests

6.

Figure 53: Process Controller Creating a new Process Controller Strategy

Example: Process Controller Strategies used in Planning Profile to define behavior of Planning Functionality.



Process Controller - Further Enhancement Examples: •

SE80 -> Package ZENH PACKA GE -

Programs

You can find here a demo report that can be executed to get an impression on how the Process Controller works at runtime. The report has hardcoded break-points to stop at interesting places during execution. ZREP PROC C'ONTR DEMO demos the invocation and execution of a simple demo Process Controller Strategy





•


•


•






•


•


•










Unit 8 Post Processing Framework (PPF) Unit Overview Unit Objectives After completing this unit, you will be able to: •

Explain the purpose of the Post Processing Framework

•

Configure the Post Processing Framework for SAP TM

Unit Contents Lesson: P ost Processing Framewo rk (P P F ).............................................98 Procedure: Post Processing Framework.............................................106



Lesson: Post Processing Framework (PPF) Lesson Overview In this lesson you will learn about configuration PPF for SAP TM.



•


Business Example

Bill of Lading Shippng Instructi

Labels

Tendering Offer

Export Approval

Output Management Adapter Invoice Forwarding cii l y Order 'der^.------ ^ u ii

2 Tendering Offgf

Business

- Intelligence |r

Event inagement Management

Figure 54: Output Management in SAP TM

For external communication, your business can use standard printing, fax, and e-mail with a document preview option. For internal communication, alert management options are available, and workflow can be used to pass requirements from one business process step to another. Communication with B2B systems is also available in situations such as tendering freight orders when a bidding or purchasing activity is present. BI data uploads can be executed to provide management reporting on various documents like freight units, freight orders, and freight bookings. Various order events can trigger communication to event management systems to make cross-system activities transparent. The Output Management Adapter uses the Post Processing Framework (PPF) to generate and process outputs.



Output can be triggered by the PPF either manually from the UI or automatically in the back end depending on the document-specific schedule conditions.

S A P A p p l ic a t io n

Sched ule s p e c i f ic

Start

a c ti o n s

a c ti o n s

c o n d i ti o n s

wh en occur

at

s p e c i f ic t im e s

Print

!>

Workflow

r-.v BAdl

F ax

E-Mail

Figure 55: Overview

The Post Processing Framework (PPF) provides SAP applications with a uniform interface for the condition-dependent generation of actions (for example, printing delivery notes, faxing order confirmations, or triggering approval procedures). The actions are generated if specific conditions are fulfilled for an application document, for example a specific status is set (approval by some person) or a specific date has been reached (two weeks before end of contract). The actions are then processed either directly, in a scheduled report later, or can be deferred via queued Remote Function Call (qRFC). The PPF is part of the SAP NetWeaver Application Server and can be used by applications. It is the successor to message control and offers a wider range of functions, simpler connection to the applications, and greater flexibility. The PPF provides tools for scheduling, starting, and monitoring actions. Actions can be determined, generated, and processed either automatically or with user interaction. With the PPF you can evaluate modifiable conditions for determining actions. The application can be used to select the determination technology with which the conditions are evaluated or use its own determination technology. Processing types are provided by the PPF to execute various actions, as follows: •

Printing, sending e-mails, and faxing with Smart Forms

•

Starting a workflow

•

Starting a Business Add-In



The processing types can be adopted by the application, adapted to meet the requirements of the application, or replaced with the application’s own processing types. The PPF also provides tools for the administration o f actions. It has an action overview with status display, determination logs, and processing logs. The overview can be included in the application as a subscreen. The PPF triggers the main outbound communication and integration steps such as PI outbound messaging, integration to SAP Event Management, BI, and workflow. In addition, printing is triggered via PPF and handled by Adobe Document Services (ADS).

Figure 56: Architecture

Output management automates the output of business documents such as printouts, in response to certain business events. This output management adapter helps you to integrate output management functionality with application business objects (BOs) that are implemented in a business object processing framework (BOPF).



BO Model

Post Processing Framework

Figure 57: Configuration

Depending on how you configure PPF, it generates output actions for particular application data records. The system then processes these actions and sends the output data. An action definition is metadata or a skeleton of a business task and has to be maintained with its individual configuration. While defining an action, it is possible to specify the type of action (external, workflow, method call, or alert). The processing details are taken from the action definition and can be modified. For example, the recipients (email/fax) for external communication can be set. A valid printer has to be set with the PPF conditions for actions which result in printing.



Some important settings for an Action Definition are: •

Processing Time

-

Processing when saving document — processing can be started once the document has been posted. Processing using selection report - actions are initially scheduled only and processing is not started until later using a selection report or by a user in the document. Immediate processing - processing can be started immediately when an action is scheduled.

•

Schedule Automatically - If you select this indicator, the actions are automatically activated for processing as soon as the schedule conditions are met. If the indicator is not selected, the person responsible must manually activate the actions in the application document for processing.

•

Changeable in Dialog - If you do not select this indicator, actions within this action definition cannot be changed manually after automatic determination.

•

Executable in Dialog - If you do not select this indicator, actions within this action definition can only be executed automatically, either immediately after scheduling or later using a selection report.

•

Partner-Dependent - Partners are determined for partner-dependent actions. The specified partner function is compared to the function of the document partner and an action is generated only i f the partner functions match. If you select the Partner-Dependent indicator, you must enter a partner function.

•

Partner Function - The rights and responsibilities of each partner in a business transaction. The relevant partner roles for an application can be communicated to the PPF by implementing the BAdI GETPARTNROLESPPF.

A PPF action profile aggregates the number of PPF action definitions by logically grouping them together. Multiple PPF action profiles can be created for a given application data table (or business object node in BOPF) depending on the actual output requirements. For example, SAP Transportation Management contains one technical business object that serves multiple business uses. The TRQ category determines whether the business object is a request object or quotation object. The output requirements for a request object may differ from those of a quotation object. From a logical perspective, it may therefore be necessary to set up multiple PPF action profiles for each TRQ category. The requirements for output setup may also vary in the different BO nodes. The PPF application is the application that uses the Post Processing Framework (PPF) to generate actions. To trigger PPF actions, start and schedule conditions need to be configured according to business needs/rules, as follows:



The schedule condition decides whether an action should be scheduled for processing. An action is therefore only generated if the schedule condition is met. The filter value is specified in the Schedule condition field. The standard value /BOFU/EVA LSCHEDULECONDITION ensures that the method in the agent class is invoked. The start condition is checked before the action is executed. The action is only executed when the start condition has been fulfilled. The filter value is specified in the Start condition field. The standard value /BOFU/EVAL START C’ONDITION ensures that the method in the agent class is invoked.

Figure 58: Integration of Customizing and Runtime

Action Profile Determination In some cases, multiple action profiles are valid for a use case. In a transportation scenario, for example, you can assign multiple action profiles to a document type. However, the relevant profiles must be communicated to the output management adapter. You can select the action profiles based on the business scenario. All of the business logic and criteria for selecting the relevant action profiles can be implemented in method GET PROFILES. Each of the interface methods can use the ABAP implementation as well as the variant for BRFplus. Implement the appropriate variant depending on the usage, that is, redefine the method with either the suffix ABAP or FDT depending on your scenario.



BO Node

Super Class

/BOFU/CL_PPF_ SERV FOR BO

Implement i i i i j

------- ----------

---------

i i i i i i i i i <

---------

EVAL START COND GET_PROFILES

PERSONALIZE DOC

---------

Figure 59: Agent Class

Any BOPF application implementing output management should create a class for handling the actions according to business needs. This class should be created with /BOFU/C'L PPF SERV FOR BO as the super class. The agent classes can be assigned to the BO node using the O/P adapter settings. All the relevant action-level outputs are hard wired to the corresponding methods in the agent class that is specified in the Output Management Adapter customizing. This enables easy implementation at the customer end. The agent class provides the PPF with the application data relevant for executing outputs. Standard class /BOFU/CL PPF SERV FOR BO must be extended by the application and the relevant methods redefined. The methods enable the logic to be implemented by either ABAP or BRFplus.



r -----------------------------------------------------------------------------------------------------1

PPF Settings

Maintain Action Profiles, Actions, Conditions L __________

_____ j

Output Management Adapter Settings Define Output Agent (with Agent Class) for BO Node Assign Profiles to Output Agent Specify whether Action Profile is critical or uncritical [ TM Document Type Settings

^

r

Assign Action Profile to TM Document Type

Figure 60: Customizing

When associating an agent class to a BO, it is possible to assign an action profile; assign actions to the action profile, and specify if the action is critical or uncritical. Critical outputs must be completed within the logical unit of work (LUW), such as business-to-businees (B2B) method calls or workflows. Non-critical outputs fall into the category of communication methods, such as print, e-mail, and fax.



Post Processing Framework l.

SAP NetWeaver

l> ^7

Cross-Application Components ^7

Processes and Tools for Enterprise Applications t>

Enterprise Services

l>

E n te rp ri se S er vi ce s E r we it er un ge n f ur G e sc ha lt sp ar tn er da

t>

E nte rp ri se Se rv ic es fo r R ec or ds an d C as e M an ag em en t

t>

Key Mapping Extension

r>

R em ote C on trol a nd C om mu nic atio n F ra me wo rk

D

PDF-based Forms for SAP ERP

t>

Settings for BO Framework and Navigation

t>

Object Navigator

t> ^7

Bus iness Context Viewer Reusable Objects and Functions for BOPF Environment t>

Depe ndent Object Attachment Folder

1>

D ep endent Object Text Collection

l>

Adapter for Authonzation Checks

v _ __ —

PPF Adapter for Output Management— —^ Maintain PPF Settings

Q,

Maintain Output Management Adapter Settings

t>

Archiv ing Adap ter

[>

BO Field Control Frame work

l>

Dependent Object for Address Management ^

Maintain BO-sp edfic Change Document Objects

Figure 61: PPF Settings 2.

PPF Applications in Customizing

30 0

0 0 C Q

Position

Entry 1 of 4 Clean Up Inconsistencies Define Action Profile and Actions

Condition Configuration (Transportable Conditions) Q3 __

^

Schedule Conditions

___ |

□

Delete Non-Referenced Customizing Entnes

□

Clean Up Inconsistencies in the Configuration

□

Repair Customizing Assignment for Configuration

□

Clean up Inconsistencies for actions

Startbedmgungen

Wizard for Defining and Scheduling an Action

Check for Inconsistencies

Condition Configuration (Not Transportable)

Clean Up Inconsistencies

Figure 62: Define Action Profiles and Actions




3. Dialog Structure ^ 01 Action Profile Action Definition CDProcessing Types

Application

/SCHTMS/TRANSPORTATION

Descnpton Action Profile Action Profile

Description CFIR ERP integration Profile CFIR Profile for Pnnting Pnnt Profile for Agreement SFIR Profile for Pnnting Actions forB2B Messages Related to Transportation Order SFIR ERP Integration Profile

'SCttTflS/CFIR /SCHTftS/CFIR PRINT /SCtlfflS/FAS PRINT 'sana&SEiR primt /SCHTHS/TOR / s c h t h s / t or in v p r e p /SCglBS/.TQR PRINT AIR /SOUTHS/TOR PRINT ROAD /SCHTHS/TOR PRINT SEA

Actions for Pnnt Documents Air Freight Actions for Pnnt Documents Road Freight

(SCflfflS/TRfl FWQ /SCffTHS/TRQ FWQ PRINT /SCftTHS/TRQ GEN

Actions for Pnnt Documents Sea Freight Send ing of B2B mes s related to node TENDERINGREQUEST Output Profile for Forwarding Order Pnnt Profile for Forwarding Order Output Profile for Forwarding Quotation Pnnt Profile for Forwarding Quotation Common Output Profile

ZPEE .TEST AP ZTfIS

Test data - action profile Test Action Profile for TM

/SOUnS/TQR T£NDR£Q /SCNTMS/TRQ FWO /SCMTHS/TRQ FWO PRINT

Common Profile n n n n n n n n n n n n FI

Figure 63: Action Profile

4. AdionProfile

/ SCfITMS/ T0R_PRINT_R0AD

Description

Actions fo r P rint Documents Road Freight

Action Definition

/SCMTI1S/PRINT_CBR

Description

CMR Road Waybill (Europe) |

f t Action Description

Action Merging

Figure 64: Define Action Definition

5.




Q

Position

Entry 1 of 4

Customizing and Configuration

Clean Up inconsistencies

Define Action Profile and Actions

Delete Non-Referenced Customizing Entries Clean Up Inconsistencie s in the Configuration

Condition Configuration (Transportable Conditions)

j5) |

Repair Customizing Assignment for Configuration Clean up Inconsistencies for actions

[3

Schedule Conditions

£

[T]

Startbedmgungen

Wizard for Defining and Scheduling an Action

Check for Inconsistencies

Condition Configuration (Not Transportable)

Clean Up Inconsistencies

Figure 65: Condition Configuration 6.

Scheduling of Actions Numb ^ Q Action Profile c f ir ERR Integration Profile 2 CFIR Profile for Printing 1 Print Profile for Agreement 1 1 SFIR Profile for Pnnbng % Actions for B2B Messages Related to Tr 12 % SFIR ERP Integration Profile 2 Actions for Print Documents Air Freight 2 §» Actions forPnnt Documents Road Freig 5 $1 Actionsfor Pnnt Documents Sea Freight 1

Actions for Print Documents Road Freight 0 Action Definition a CMRRoad Waybill (Europe) /SCMTMS/PRINT_LAB Shipping Manifest V1CSRoad Waybill (US) Freight Forwarding Instructions

No 1 1 1 1 1

Processing Type External Communication External Communication External Communication External Communication External Communication

GHt

_0êrview^^2| Processi ng Selection ^

ions

Schedule Condition

Start Condition Details of Selected Processing Recipients

Printer

Mail/FaxAltchmt

Mail Settings

Assigned Processings External Communication Form Name Form Type Format Storage Mode

/scirms/Fp_cnR P PDF-Based Forms /BOFUf PPF_STAUMRD 1 SendOnfy

G o & a

«d a

Action Definition I P" Default Settings from Action Definition

Figure 66: Condition Configuration: Processing Details 1 7.




Cross-Application Com ponents Processes and Tools (or Enterprise Applications t>

Enterprtse Services

0

Enterprtse Services Erwelterungen fur Gesctialtspaitnerdaten

0

E nte rp nse S erv ices for Re co rd s an d C as e Ma na ge me nt

t>

Key Mapping Extension

0

Remote Control and Communication Framework

0

P D F -b a s e d Form s for SAP E RP

0

S etting s for B O F ra me wo rk a nd Naviga tion

t>

Object Navigator

t>

B us ines s Context V iew er

S7

Reus able Objects and Functions for BOPF Environment t>

Depend ent Object Attachment Folder

t>

A dapter fo r Authorization Ch ec ks

Dependent Object Text Collection

PPF Adapter for Output Managem ent

cr

R V

Maintain PPF Settings

| $r

Maintain Output Man agem ent Adapter Settings

1>

SIdiMiig Auapiei

t>

BO Field Control Fram ework

----------------------------------------

t>

Depende nt Object for Address Managem ent Q*

<&

Maintain BO-specific Change Document Objects

Figure 67: Output Management Adapter Settings 8. Change View "PPFOutput Agents fo r BO Node s": Overview "17 §

New Enow Q Q t ^ g B

'Blog Structure ’ €5 WF Output Agents for BONodes ' AsagnPPFProfies * D Acton Settrgs • Q ProcessingType Settings • Q Assign Trjnsent Actions 0 Diect Output Agents (w/o PPF& w/o Hstory)

PPFOutput Agents for BONodes BusinessObject

Node Output Agent

/BCBF/DEHO.CUS ROOT / bqf p / c oc :

Agent Classfor 60 Node

BftfpLs Appkat or D for Node Function for Action Profie

/Boro/g roc sotv f r is

/8CBF/DDC_raO.. ROOT /80FU/EC»_1

/BCFO/Cl_PfF_SERV_OD»_ /BOFO/PFFJCA?TER_BRF_EE.

/BCBF/DEMO_SAL-ROOT /B0Ftj/coc_i

/ K n / a jm jm jo jt .

/B0rJ/TEST_CUS-ROOT /BOFU/EOC.1

/BOFTJ/CI_PPF_SERV_FCft_T-

/B0FU/TEST_CUS. ROOT 'BOFU/EOC2

2 a PPF SERV FORBC

/B0FU/TEST_CUS. ROOT A3GR

2 a PPF SEKV FORBO

/BOFtJ/TEST_COS_ROOT TEST1

2 CLPPF SERV FORBO

/BCFTJ/TEST_C0S..ROOT TEST A3ENT

2 a PPF SERV FORBO

/BCF3/TEST_COS_ROOT 2SA.VTEST UtO. ZSA.H CL TEST OP 2SAH_SAL£S_0RD- ROOT 2SAM TEST OOTP- 2SAN CL TEST OP

Figure 68: Output Management Configuration and Setup

9.




Figure 69: Output Management Configuration and Setup - Assign Action Profile to BO Node 10.

D i s p l a y V i e w " F r e i g h tO r d e r T y p e s " : D e t a i l s

*gr tU3 SB Besrc Settngs

Number Range Settng s

F r e i q h t O r d e r Ca n B e S u b c o n t r a c t e d

[Not Rel evant fex Subcui'tr acing

T h e f o r D r aw i n g

S h p p e r / C o n s i g n e e D e t e rm n a U o n

|Dcrnm-aiarvi n Rac ed o n Fret ani

Number Range Interval

* ICS1

I |F» Document When Saving f ~ l F r e ig h t O r d e r C a n B e D e l e t e d

Change Contiolei Settings Default Change Strategy

HO ACTION

Creation strategy

Change Strategy Detormnat

Save Strategy

QueuUty T olerance CoridOun

Oeletion Strategy

Date To lerance Condition

Execution Settings execution Track. Relev.

S e r v ic e L e v e l D e t e r m n a t i o n jFx ecu tk> n Tr ac kn q wit h Fx tem al Fv en t S

”

Check Condition 'Ready for Fxec" t Processng

Default Service Level Service I eve I Coruj.

G j Q P ' o p a g a te E x e c u t i o n I n f o

Event Management Settngs

D e f a u l t M Tr D e t e r m n a t i o n

A p p k c a t io n O b j e c t T y p e

ODT2Q_TO

last Fxp. Fvent

ARRIV OEST

Default MTr for Type Condemn for Def MTr

Tenderng Settngs

Default Units of Measure W eight

1 x S o y r am

Volume

1C u b icm e te r

fi)Usc Default Settngs ^ O u s e C o n d it i on f o r S e t t . D e t e r m . Tend eratg Condition OefaiRiori O U s e T y p e S p e c r i t S e tt i n g s P ro ce ss S e tt ng s C om m u n ic atio n S e ttin g s

________.___ ^

• ' ' O u t p u t O p t i on s /

V \

Ou tpu t Piofte Add. Ou tput Prone

l/SC*cm3/TOR_PRIHT_l«OAJl / S CM T MS / TO R

Text Schema

A

i

D efa ult T ex t T yp e l l Q D y r i a n v D ete rm in a tio n o f O u tp u t

Figure 70: Assignment of Action Profile to TM Document Type





•






•








Unit 9 Print Forms Unit Overview


Understand how Print Forms can be enhanced

•

Explain the basic steps for Print Form Enhancements

•

Find further detailed information about the topics covered with this training

Unit Contents Lesson: Print F or m s..................................................................................... 114



Lesson: Print Forms Lesson Overview None



•


•


Business Example

Print Forms What is it?

•

SAP TM provides a number of standard print forms that can be printed out, e.g. a Pro Forma Invoice Document or different kinds of Bills of Lading.

•

The provided Print Forms take the data of a Business Object (e.g. a Forwarding Order) and places it onto a PDF-based form where a specific layout etc. is defined to represent this data on paper.

Why en hancing Print Forms?

•

The provided standard forms may not contain all information required by customers or the layout might not match the requirements.

•

For example there are extension fields (customer specific) on Business Object level that shall be also printed with a form or the layout needs to be adjusted, e.g. changing the sequence o f fields or adding a company logo.

How is it done?

•

The available forms can be found in transaction SF P (Form Builder) by using the F4-Help in field Form on the initial screen. Search for forms that start with /SCMTMS/*.

•

See Enhancement Guide Document for a detailed example and information on how to enhance existing as well as to create new Print Forms.

Technical aspects



How to enhance or create a Print Form and what to implement? •

You should always copy a standard Print Form before enhancing it or you create your very own new Print Form —* transaction SFP.

•

On the Properties Tab of SFP you can identify the related technical interface for your Print Form which provides the Print Structure that contains all data and attributes that can be used on the form.

•

The Print Structure can be enhanced via an Append-Structure (SE11). These enhancements can be added to the Context of the Print Form and will be available to be placed in the Forms layout. tbENH~FP~FFDOC

LA

Properties

Context

Descnption

Layout TMForwardrg Instructions *

Layout Type

/SCMTMS/FP IF FFDOC

Interface

Doub le click on the Interface to navigate to the und erlying interface of the form

Inbound Handler

POLCH

Created By

f02.01.20l2^

Date

Changed By

POLCH

Date

0 2.0 1 .2 0 1 2

FormBuilder: DisplayInterface /SC M TM S/FP _IF_ FF D O C

c£

* a" £ n D / scmtms/ f p

Properties

ir

rrvoc

navigate to the DD IC editorto enhan ce the structure

Interface

M -

<23 /SCMTM S/FP IF FFDOC " ^

F or m I nt e rf a ce

>6.

Parameter Name /1 BCDWB/DOCP ARAMS IS_PRBI TOUT

Type assortment Type Name J TYPE i& SFPDOCPARAMS / TYPE

Op t o n a l Ft . ..

Pas-

1XJr/SC MTMS/S _PRINT _FFO n T h i s D D I C s t r u c t u r e re p r e s e n t s t h e c o n t e n t o t t h e f o r m I t w i ll h o l d t h e d a t a t o b e p r i n t e d w it h the form an d will be filled with corresponding b a c k e n d d a ta

Figure 71: Interface and Print Structure

Demo (if required): •

Start Transaction SFP and choose an existing Print Form to be displayed.

•

Go to Tab Properties and explain the role of the Interface, i.e. it contains the data structure that will provide the data to the print form.

•

Click on the interface to display its content.

•

Relate to Enhancement Guide Document for a detailed example.



Form Bui lder : Dis play For m ZENH_FP_ TRQ D Heparin*

Contort

4 l w u!

. aycut

ffi(DM Fr.erf.xe

Context

• la.wjsjejrsi.

On Tab Context you can specify the data structures from where the new print form gets its data to be printed.

. Descrotic n

* <5 ZBUJP.TRQ • » TRQJD • TSPJD a 5RCJ.OCJO 3 DE5J.OCJD 3 ORDCP.PA ftryjD 3 SUPPERJD

3 a 3 3 3 3 3

COMSI j NEF ID GRO_W*l_VM. G*0_WEl_UNt GR0 _VOl _V«L GRO_WOl _UNI NET.WH.VAL NPT.WBJJM

D of Furwanfcq O der/Q ujtalin i» T rip. Rcqt

Camw Scmt * locator CostxwdonLocation Ordemg Patty

G»o« w«s ht Ctow w»3hr urn of M&aare Gross Votme GrowVclme ch* a Measue

Kwt wa/it

3 CRE*TED_BV

Not Anrîf LtV of Moature abated By

3 OtEATED.ON

Created or

3 QtMJXOjn

Changed By Charged On

- CMMJ3EO.ON item

Item

Figure 72: Context in Transaction SFP Demo (if required):

•

Start Transaction SFP and choose an existing Print Form to be displayed.

•

Go to Tab Context and explain the role of the context, i.e. it is the data structure that will provide the data to the print form.

•

Switch to Tab Layout to display the Layout of the print form represented in ADOBE Life Cycle Designer.

•

Relate to Enhancement Guide Document for a detailed example. Form Bui lder : Dis play For m ZENH_FP_ TRQ *< *y a

.i

#

&

si

a

iaoi_r?_TOQ Ftcpeftfes

Context

&a a

ûwrt At:**

An example Enhancement Print Form in transaction SFP

Layout

Figure 73: Layout in Transaction SFP



... and what to implement?

•

Each Print Form is associated with a so called Printing Class that contains the coding for providing the actual data to a Form (Example class: /SCMTMS/CLPRINTOUT_FWO). -

Most important method is FILL PRINTSTRUCTURE It contains the code to read and map data to the Print Structure

•

A BO Service class will contain coding to communicate with the Post Processing Framework (PPF)/Output Management. It is assigned to the Form in the related PPF/Output Management Configuration (Example class: /SCMTMS/CL TRQ ROOT PPF SERV). Method PERSONALIZEDOC'BYABAP contains the call of the relevant methods from the Printing Class, i.e. it represents the “connection” between the Print Form-specific implementation and the configuration that is required for the usage of the Print Form.

... and what to configure?

•

With a new or enhanced Print Form and the required backend coding in place you can now configure the required Post Processing Framework (PPF) and Output Management Adapter Settings to get the form displayed in the print preview or printed out on paper.

•

PPF Settings: In transaction SPRO follow the path Cross-Application Components — Reusable Objects and Functions for BOPF Environment —* PPF Adapter fo r Output Management —* Maintain PPF Settings. -

Action Profiles and Actions need to be configured Condition Configuration needs to be set up

•

Output Management Adapter Settings: In transaction SPRO follow the path Cross-Application Components — Reusable Objects and Functions for BOPF Environment —>PPF Adapterfo r Output Management —> Maintain Output Management Adapter Settings. Determines output for a given business object (BO) node Maintain output management settings for the business object (BO) node, using PPF output agents for the BO node Assign PPF profiles to the given BO node Maintain action settings and processing types

•

See SAP TM Enhancement Guide Document for a fully detailed configuration example.



Process Control / Busness Object Mode pB W Relevance

Automatic Block

C Enable Approval Workflow

C Automatic Freght Unk BufcJng

Track Changes

Automatic Transport. Charge Calculation

(y Enable Settlement

Default FWSO Type

[HPFSl

C Automatic Confirmation

Defaufc Conf. Type

M

E M I n t e g r a t e A c ti ve

Event Manager EMW eb In terface Transact**!

C DynartK Determ raton of Output Profie

Out pu t Pro fie

ZENH_TRQ_FWO_PRINT

Add. Output Profie

OG Profie Text Schema

Text Type

Spec ify the Output Profile to be used here (You should find the example profile also in the F4-Help)

Retenton Period Accept Transp. Prop.

Save Route Only

Propagate Changes

Synchronous Propagation of Changes, Fatiack to Asynchronous

Figure 74: Configuration Aspects

In the Document Type Customizing you can then finally assign the Output Profile that will be used for documents of this type to be displayed in the print preview, printing it on paper or sending it e.g. via Email.

Figure 75: Example: Displaying a FWO Document Preview





•


•






•


•








Unit 10 Integration Unit Overview


Understand which enterprise services are available with SAP TM

•

Understand which integration scenarios SAP TM offers

•

Explain how to monitor messages in SAP TM

•

Understand how to enhance a SAP TM web service

Unit Contents Lesson: In te gr ation.......................................................................................122



Lesson: Integration Lesson Overview In this lesson you will understand the Enterprise Services in the context of SAP TM and how to enhance them.



•


•


•


Business Example

Enterprise Services in SAP TM Overview TM provides Enterprise Services in the following areas:

•

Transportation Order Processing

•

Transportation Request Processing

•

Customer Freight Invoice Request Processing

•

Supplier Freight Invoice Request Processing

•

Other Web Services



Transportation Order Processing

Related to Business Object /SCMTMS/TOR, services are provided to: •

Order transportation services from carriers

•

Exchange transportation-relevant data and create, change, or cancel freight orders, freight bookings, or freight requests for quotation

•

Assign transportation demands to transportation capacities

•

Create delivery proposals for further processing in the corresponding logistics execution system (SAP ERP).

•

Request the execution of transportation orders (Shipment creation in SAP ERP)

•

Request the creation, change, or cancellation of business transaction documents that are prerequisites for transportation order invoicing

•

Request the creation or cancellation of business transaction documents that are prerequisites for an export declaration.

•

Request the processing of a trade compliance check

•

Request the creation, change, or cancellation of loading appointments for transportation orders of the category “freight order” or “freight booking”

Transportation Request Processing

Related to Business Object /SC’MTMS/TRQ, services are provided to: •

Processing of requests from an customer / ordering party for the provision of transportation services

•

Receive requests for quotation from a customer and submit a forwarding quotation

•

Create, change, or cancel a forwarding order based on an order received from a customer

•

Query the creditworthiness of business partners

•

Simulate, create, change, or cancel transportation requirements, based on order or delivery data received from a logistics execution system (SAP ERP)

•

Request the update or split of outbound deliveries

•

Request the processing of a trade compliance check

Freight Invoice Request Processing Customer Freight Invoice Request Processing

Related to Forwarding Settlement Documents, services are provided to: •

Request invoicing for transportation services performed for a customer

•

Request sent to billing to create one or more customer freight invoices



Supplier Freight Invoice Request Processing

Related to Freight Settlement Documents, services are provided to: •

Request invoice verification for invoices submitted by a supplier (carrier) for ordered transportation services.

•

Request sent to invoice verification advising that a freight invoice is expected or is to be created through evaluated receipt settlement.

Other Web Services

Other web services are provided to: •

Provide a logistics execution system with information about TM documents and their statuses that relate to a specific business document in the logistics execution system (SAP ERP cross-system document flow).

•

Request the URL to display TM documents in SAP ERP while using invoice verification or agency business processing.

Integration Scenarios

The following integration scenarios are available in the Enterprise Services Repository (ESR) in software component SAPTM IC: •

TMERPInvoicelntegration

•

TMERPOrderlntegration

•

TM_ERPSalesOrderScheduling

•

TMERPShipmentlntegrationOut

•

TMERPShipmentlntegrationln

•

TMGTSExportDeclarationlntegration

•

TMGTSTradeComplianceChecklntegration

•

TM FINC reditManagementlntegration



Integration Scenarios Integration Scenarios - Invoice Integration TMERPInvoicelntegration

•

Transfer settlement documents from SAP TM to SAP ERP to create billing documents or accruals.

•

Forwarding Settlement

•

Freight Settlement

•

Invoice Notification

•

Invoice Simulation

Order & Delivery Integration TMERPOrderlntegration:

•

Transfer orders and deliveries from SAP ERP to SAP TM for transportation planning

•

Propose deliveries in SAP TM that can be created in SAP ERP

•

Send SAP ERP Order to SAP TM

•

Send Delivery Proposal to SAP ERP

•

Send SAP ERP Delivery to SAP TM

•

Split Outbound Delivery

•

Update Outbound Delivery

TM_ERPSalesOrderSeheduling

•

Carry out transportation planning synchronously in SAP TM during sales order processing in SAP ERP to take into account the transportation situation when calculating feasible dates for sales order items.

Shipment Integration TMERPShipmentlntegrationOut

•

Perform transportation execution in SAP ERP based on freight orders or freight bookings after having carried out transportation planning for delivery-based transportation requirements in TM.

•

Create Shipment in SAP ERP.

•

Send Cancellation to SAP ERP.

•

Notify of Status Change.

•

Notify of Changed Delivery Assignment.

•

Notify of Changed Packaging and Item Assignment.



TM_ERPShipmentIntegration_In

•

Send shipments created in SAP ERP to SAP TM to create freight orders or freight bookings and carry out tendering in SAP TM.

•

Send Shipment.

•

Notify of Tendering Result.

Others TMGTSExportDeclarationlntegration

•

Integrate SAP TM with SAP Global Trade Services (GTS) to create an export declaration and handle the required customs processes.

TMGTSTradeComplianceChecklntegration

•

Integrate SAP TM with SAP Global Trade Services (GTS) to perform a trade compliance check in SAP GTS for SAP TM business document.

TM_FINCreditManagementIntegration

•

Perform a credit limit check on a business partner in SAP TM based on credit information provided by SAP Credit Management.

•

Creditworthiness Query (Synchronous Communication).

•

Credit Commitment Notification (Asynchronous Communication).

Other Content

The following interface mappings and message mappings are available in the Enterprise Services Repository (ERP) in software component SAPTM IC •

In the integration scenarios TMERPShipm entln tegration Out and TMERPShipmentlntegrationln, interface mappings are used to map messages from an SAP TM system to IDocs in an SAP ERP system, and vice versa.

A complete documentation can be found on http://hclp.san.com/trn •

SAP Transportation Management 9.0 —> Application Help —* SAP Library —>SAP Transportation Management (SAP TM) — Enterprise Services and ESR Content.



Enterprise Services in SAP TM Enterprise Repository Browser (SPROXY)

Transaction SPROXY can be used in the TM system to review the ESR content •

Service interfaces, message types, and data types can be found in the following namespaces: http://saD.com/xi/TM S/Global http://san.com/xi/TMS/ http: Vsap.com/xi/TMS/UX 188Enterprise Services Browser m

[ i] s i n

m

m

m

m

Local Objects only (No Connec tion to ESR) * http://sap.conrVxi/TMS ► n ”

Messagetypes

(§) Service

Interfaces

• TransportationOrderSCMTenderingResultNotification_Out • TransportationOrderSCMRequest_In • T ransportatk>nOrderSCMExecutionStatusNotification_In •

TransportationOrderSCMExecutionRequest_Out

• TransportationOrderSCMExecutionItmPckgAssgnmtChangedNotification_In • TransportationOrderSCMExecutionDelrveryAssignmentChangedNotific3tion_In • TransportationOrderSCMExecutionConfirmation_In • Transportatk>nOrderSCMExecutionCancel!ationRequest_Out • TransportationOrderSCMCancelationRequest_In iS j Datatypes

* http://sap.conYxj/TMS/Global ► E

Faultmessagetypes

►

Messagetypes

* Op Service Interface s • •

TransportationRequestRequest_In

•

TransportationRequestQuotationCreateRequest_In

• TransportationRequestQuotationConfirmation_Out • TransportationRequestQuotationCancelationRequestJn • TransportationRequestConfrmation_Out • TransportationRequestCancellationRequest_In •

T r a n c n n r ta fm n n r H o r ^ lIT T P T n v n ir in n D r o n a r a tin n P o n iio c f

O u t-

Figure 76: Enterprise Repository Browser (SPROXY) (1)

Enterprise Repository Browser (SPROXY)



SPROXY can also be used to test / debug message processing •

Message processing during implementation phase is difficult to debug, because it is done by a remote user

•

For testing purposes, this can also be done in SPROXY: Set breakpoints -

Download a message from SXI MONITOR

-

In SPROXY, open the service interface definition Press the “Test” button (F8) ^ Check “Debug method” Load the downloaded message Optional: Edit the message tB

-

Execute ^

Test Service Provider: Display Req ues t

ED I2 a & Q

< ? x m l v e rs io n = " 1 .0 ' e n c o d in g = " u tf -8 " -

?>

< n m :T r a n s p o r ta tio n R e q u e s tS U I T E R e q u e s t x m ln s :n m = ' h t t p : / / s a p . c o m / x i / S A P G I o b a l 2 0 / G l o b a r -

< M e s sa g eH e a d er> < ID ; 0 0 5 0 5 6 2 A 0 0 4 F 1 E D 2 A 9 E 6 6 0 5 1 3 5 4 3 A A 7 8 < /I D > < C r e a t io n D a t e T im e > 2 0 1 3 - 0 4 - 1 7 T 0 7 : 4 7 : llZ < /C r e a t io n D a t e T im e > < S e n d e r B u s i n e s s S y s te m ID > H 3 3 < y S e n d e r B u s in e s s S y s t e m I D > -

< B u s in e s s S c o p e > < T y p e C o d e > 6 < /T y p e C o d e > < ID > T M < /ID > < /B u s i n e s s S c o p e >

< /M e s s a g e H e a d e r > -

< T r a n s p o r ta ti o n R e q u e s t a c b o n C o d e = '0 1 " it e m L is tC o m p le te T r a n s m i s s io n In d ic a to r = " tru e '> < ID > 4 0 0 0 0 0 4 0 0 7 < /I D > < C a te g o ry C o d e > 0 1 < /C a t e g o ry C o d e > < D e liv e r y F o llo w U p B u s in e s s T ra n s a c ti o n D o c u m e n tT y p e C o d e > 7 3 < /D e li v e ry F o llo w U p B u s in e s s T ra n 5 < T r a n s p o r ta t io n M a n a g e m e n t In i ti a te d D e l iv e r y R e la te d I n d ic a t o r > fa ls e < /T r a n s p o r ta t io n M a n a g e m r < D a n g e ro u s G o o d s In d i c a to r > fa ls e < /D a n g e r o u s G o o d s In d ic a t o r> < D e liv e r y B lo c k e d In d i c a to r > fa ls e < /D e l iv e r y B lo c k e d In d ic a to r > < R e t u m s In d i c a t o r > f a ls e < /R e t u m s In d i c a t o r >

- ^ShinnerOartv,»

Figure 77: Enterprise Repository Browser (SPROXY) (2)



Message Monitoring First level of message monitoring Technical status of message can be checked: Processed successfully: Overal Status

/V

OutbStatus Status De

I Processed successfully

l

Scheduled: Message is still queued -> Select and Goto Q R F C Monitor via menu or transaction SMQ2. Overall Status / &

OutbS tatus

[ S ch ed uk dJ

System error: In case of dumps: Dump can be found in transaction S T 2 2 . Messages can be reprocessed manually from here or via report RSXMB_R ES TA R T_MESS A G E S . Overal Status

lilt

OutbStatus Status Petals

^Sy5tfmÊrror^ânuanrestartJ>os^b|eJ|

Application error: Message has been forwarded to second level monitor. Only if it has been activated -> see next slide. Don’t reprocess from here! Overal Status so SO

OutbStatus Status Petals

Ac

Ife Transfer to External Applica tion k

L

Figure 78: Level 1: XI Message Monitor (Transaction SXI MONITOR)

Second level of message monitoring

•

Needs to be activated in SPRO\ Cross-Application Components —>Processes and Toolsfor Enterprise Applications —* Enterprise Services —> Activate Error and Conflict Handler.

•

Messages that were not processed due to an application error are forwarded here.

•

In case error has been resolved within TM, message can be reprocessed from here. E.g. missing master data, locked documents. -

•

Reprocessing can also be scheduled using transaction /SAPPO/RESUBMIT.

In case error has been resolved with message update / new message, old message can be confirmed / discarded. E.g. wrong data used in ERP, ERP document was updated. In this case, the new message will be parked in the queue (status “Scheduled” in XI message monitor) until the old one is confirmed/discarded. Afterwards the new message will be processed automatically.



Figure 79: Level 2: Postprocessing Desktop (Transaction /SAP P0 /PP02)

Forward Error Handling

To enable monitoring in the Post Processing Desktop, Forward Error Handling is used. •

Forward Error Handling (FEH) is a concept that enables errors, detected during the execution of asynchronous services to be processed on the provider side.

•

This concept is implemented using the Error and Conflict Handler (ECH ).

•

The resolution process depends on the type of error. An error may be resolved automatically, resolved manually, or rejected and delegated back to the consumer.

•

The ECH Framework classifies errors into error categories. You can define a resolution strategy individually for each error category.

•

More documentation can be found on http://help.sap.com/tm

•

SAP Transportation Management 9.0 —»Application Help —» SAP Library — SAP Transportation Management (SAP TM) — Enterprise Services and ESR Content — Forward Error Handling

Enterprise Services Enhancement Enterprise Services can be enhanced to transfer additional fields:

•

Standard fields which are not transferred in standard service

•

Custom fields

The following steps are necessary to enhance the service:



(Example: Send an additional field from ERP to TM) •

Development in System Landscape Directory (SLD) -

Create a Product and Software Component Define Dependencies Between an EnSWC'V and an Underlying SWC'V

•

Development in Enterprise Service Repository (ESR). Import an EnSWC'V into ESR Create a Namespace in EnSWCV -

Create a Data Type in the SWC Create an Data Type Enhancement for TM and for ERP in the SWC

•

Development in the Backend System (ERP, TM) Generate the Enhancement Proxy Structure in TM and in ERP Enhance the mapping in ERP (BAdI) -

Enhance the BO and UI in TM (BOPF & FBI)

-

Enhance the mapping in TM (BAdI)

BAdls are available to enhance message mappings: In SAP TM, these BAdls can be found in the Customizing Implementation Guide ( SPRO ): SAP TM w

TM-> Business Add-Ins (BAdls) for TM-> Integration.

Integration * Trackrg and Tracrg of Processes and Documents ______ Enttrpriw Sovfcw______________________________ w Forwardng Order Management Freight Order Management Global Trade Settlement » ERPLogistics Integration Other Web Service*______________________________ w Generation of a URI to Depby a Transportation Document Query Busness Document Information

The ERP BAdls are listed in note 1530240: FAQ for ERP-TM Integration (ERP part). Note 1530240 • FAQ for ERP-TM integration Question S: Which enhancement spo ts

or

Business Add-Ins (BAdls) are there for the individual service operations?

Answer Purchase order: POP_T ranspo rtation Request SUITEReques t_Out: Enhancement spot PUR_SPOT_SE_PURCHASE_ORDER BAdI PUR_SE_TRQ_SUITEREQUEST_ASYN Method OUTBOUND_PROCESSING Sales order and customer return:

Figure 80: BAdls for Mapping Enhancements



Display XML Message Versions dVWndowr 1

tJvvrJoA- 1

C^WndOw 2

<*

o

a

Figure 81: Example of Enhanced Service





•


•


•






•


•


•








Course Summary You should now be able to: •

Understand the basic Architecture o f SAP TM

•

Get a general understanding understandi ng about the frameworks used in SAP TM - Business Object Processing Framework (BOPF) (BOPF) - Floor Plan Manager (FPM) (FPM) and Floor Plan Manager BOPF BOPF Integration (FBI) - Process Controller and Strategies, Conditions (based on BRFplus) and Business Addins (BAdls) in SAP TM - Further enhancement enhancement options options

•

Get a general understanding understa nding about how to use the frameworks for enhancing the business logic and User Interface of SAP TM

Related Information Where can I get more detailed information on the presented topics?

•

A detailed description o f all presented topics including coding examples and implementation hints can be found in the SAP TM Enhancement Guide.

•

The document is available in the SAP Community Network (SCN).

•

Blog with link to Enhancement Guide Document: Document: http://scn.sap.com/blous/SAP TM Enhancements




Sap Tm215 en Col16 Tm 9.3 Wwwerpexamscom

Recommend Documents